Currently, the largest hurdle in usability is flashing the firmware to the device after calibration. Short of making an interface for calibrating, we have to at least document thoroughly all the steps in:
Calibration
Placing all LEDs in the device so they're consistently oriented.
Imaging the device in a gel imager to acquire calibration data. Note ensuring a correct GS setting is used to avoid saturation.
How to use the Matlab software to create calibration settings. Also indicate how to iterate using previous calibration settings.
Flashing new firmware
How to use Amtel studio. How to set up file structure and configure compiler correctly.
Incorporating the calibration settings into the config.h file correctly. Difference between setting DC & GS (64 vs 255 settings).
(Re)building the code.
Flashing to the device. Specify all required flash/interface settings.
Ideally, all these steps will include images and extensive descriptions of all steps in order to limit the number of support requests we get. In the 'beta' phase, this was the single most difficult and troublesome series of issues people encountered.
Currently, the largest hurdle in usability is flashing the firmware to the device after calibration. Short of making an interface for calibrating, we have to at least document thoroughly all the steps in:
Calibration
Flashing new firmware
Ideally, all these steps will include images and extensive descriptions of all steps in order to limit the number of support requests we get. In the 'beta' phase, this was the single most difficult and troublesome series of issues people encountered.