Most of the software and documentation is written by Connor Bain for the IC2S2 conference. Other code contributions are from Parralx (Badge Libraries). Some code was adapted from Corey Brady's previous work on the badges (see BoozeWizardSerialDump.py) and from gergelyorosz's export_as_csv for GAE.
- Install FTDI Serial Drivers (MacOSX-v2.3)
- Install SimpleIDE
- Open SimpleIDE in order to create workspace (in
~/Documents) - Install Dropbox (user: [email protected])
- Ensure libbadgetools, libdatetime, participant-code.c, participant-code.h, survey.h, eeprom.h, eeprom.c, ID_info.h, and badge-burn.command files are synced and intact.
- Create symlink to dropbox on the desktop using:
ln -s ~/Dropbox/ ~/Desktop/badge-code - Install folder action. You can do this by opening BadgeBurn-AppleScript in the Dropbox folder.
- Enable folder action via applescript
- Disable Safari Auto-fill
- Disable Screen Saver
- (Energy Saver) Make sure display is always on
- MAKE SURE NAMES.CSV IS UPDATED
- Plug in badge
- Navigate to www.ic2s2-badgeregistration.appspot.com
- Fill out form; Click Submit
- Confirm info; Click CONFIRM AND BURN TO BADGE
- Wait for "Burn Successful" Notification
- Hit "DONE" button
- Unplug badge
- In terminal run
/usr/local/google_appengine/remote_api_shell.py -s ic2s2-badgeregistration.appspot.com(Note: this requries*.jsoncredential from GAE (downloaded via the online admin interface) and theexport GOOGLE_APPLICATION_CREDENTIALS="<path_to_*.json>"set in.bash_profile) - From the remote shell, run
import export_as_csv - CSV file will be outputted with timestamped date. (NOTE: no idea how this deals with write ops, so be careful)
- Plug-in server badge via micro-USB to computer with FTDI drivers installed.
- Open up terminal and execute:
screen -L /dev/cu.usbserial. 115200. (115200 is the default baud rate) - Once connected, hit P25 on the badge. (We do this 3 times to have a backup)
- Disconnect from screen using ctrl-a then ctrl-\ and then 'y'.
- In whatever directory you were in, there will be a file called screenlog.0. That's your data file.
- Burn BoozeWizard.c to a new badge.
- Boot up the badge. It will say "ERASING CONTACTS" and then switch to "connecting...".
- Plug the badge into a computer via usb.
- Run either
python BoozeWizardSerialDump-NL.pyorpython BoozeWizardSerialDump.py</code. The first will create a single file for all badges scanned, the latter will create a single file (labeled with BadgeID) for every badge scanned. - Once connected, the badge will display "HOTSPOT!"
- Scan any and all badges by "Checking-in" to the new badge. Please hold it there until you see yellow flashing lights.
- Data will be printed to the appropriate csv file.
- "RAM Verification Failed" - Solved by burning small sample program to badge and then reburning program.
- "RAM Verification\n Check-sum invalid" - This ocurred on the server badges and went away when I removed the sound.h header. I think it might have something to do with recompiling the files (it may be auto-recognizing changes and delta-compiling instead of full-compiling).
- Buttons don't work - We think the solution is to just scrub the buttons with a cloth. This might be due to film from the manufacturing process.
- "No Badge Connected" - The Mac FTDI driver doesn't cooperate sometimes. You can make the driver crash by opening a screen
screen /dev/cu.usbserial. 115200 and then disconnecting violently (e.g. unplug or via ctrl-a,d). It seems like it can't reconcile the open port and doesn't recognize subsequent badges. I tried sudo kextunload /Library/Extension/FTDI.kext but it spits out an error that one instance is still running so you can't unload it. This is fixed by a simple restart. (Note: I've managed to make my personal laptop unable to recognize badges. I've tried unloading the kext, rebuilding the kernel cache, and reinstalling the FTDI drivers. Nothing).