I have noticed that the card10 needs some maintenance; most people carrying a card10 have brought their own tools for maintaining their card10, making it more individual, or adding functionality. In some places, maintenance stations are available, where card10’s can be recharged, and tools and knowledge is shared
According to current research, it is recommended to carry the following:
Optional things that will come in handy: * A Torx T6 screwdriver for assembling card10 * A needle for sewing to the card10 wristband * An android phone or iphone capable of communicating via Bluetooth Low Energy (BLE)
Generally, there is a wide range of contributions that can be made to the firmware, the IOs and Android apps, the various methods of BLE communication, the user interface, the documentation, by reviewing existing work, and of course by creating your own interhacktions!
If you don’t know where to get started you can also have a look at some of the ideas for contributions we outlined here. If you have questions on the issue, please don’t hesitate to comment or get in touch to the creator of the issue through our Matrix:(
You can also be a great help by adding documentation to the card10logix wiki. If you notice some information is missing, but you don’t know the information that needs adding, you can also make us aware by adding an issue. Please make sure to describe in detail what information is missing.
To keep things easier to maintain (the r0ket wiki has been going for 8 years now!), we decided on a git/markdown based wiki for this year. Editing the wiki works as follows: Click ‘edit’ on the top right of a page. Create an account for the gitlab interface that opens. Once you have made your changes, you will be guided through the process of generating a pull request. If you are still working on your edits, please add the flag ‘WIP’ before the summary of your pull request. The pull request will then be ignored until you remove the flag. If you have any questions, don’t hesitate to get in touch via the card10 communication channels.
This year’s badge isn’t only hardware and firmware, it comes with some story telling around it. All work before day0 is performed by ‘researchers’. According to the storytelling, they received some messages from the future, indicating that cccamp19 will have a badge. These reports come from ‘travelers’, which within the story are people at camp, from day 1 onwards. In reality these reports are our means of introducing card10 features and concepts, but wrapped into a nice story.
Whilst at most times #card10 is observed wrist mounted on a very soft, fluffy wrist band, occasionally I spotted a card10 in unusual places, fitted on top of clothing, extended with more LEDs and sometimes also combined with other electronic boards. These boards often have the shape of r0kets, but I also noticed several other creative outlines and colourful blinking patterns.
Yes, a comfortable neoprene wristband comes with every card10. If you want something else, you can of course bring your own, and attach it either with the screw bars that also attach the neoprene wristband, or by sewing your card10 onto your wristband. The latter is also an option with the neoprene wrist band, if you are concerned about an allergic reaction to the metal clamps, however this reduces the EKG functionality. To maintain skin contact and thus EKG function, you can instead attach a piece of conductive silver fabric on the skin side of your wristband and connect it to the EKG (TODO: add more details how to do this). You can even attach your card10 to anything else you can come up with, using the screwbars or needle and thread!
We recommend reinforcing the velcro hook side attachment by adding a seam along the sides of the velcro hook side piece.
The display has a polarizing filter on. With the protective foil stuck on top, this filter is disabled. With some sunglasses this has the unfortionate effect that the card10 is difficult to read on your wrist.
One possible reason for a read-only filesystem is a set “dirty-bit”.
To change this the linux tool fsck can be used.
First the badge needs to be ejected safely, then it needs to be restartet and put back into “USB storage” mode.
The device should not be mounted. Now
lsblk can help with finding the correct blockdevice.
Then you can check the filesystem with
fsck /dev/sdX (replace
sdX with the correct device).
If neccessary the tool will ask if the “dirty bit” should be removed, this needs to be answered with yes.
After this, the problem should be solved.