901112 - MBTS; Android data logger : Tasks This page last changed on Aug 29, 2013 by oreilly. Outstanding tasks 15. If instrument bluetooth socket can't be created, get NullPointerException 16. If instrument serial port can't be created, get NullPointerException 17. If configuration requires IOIO but it is not physically connected, 'Refresh' button never gets reenabled. 18. Need to ensure that Wakey is awake for first sample, to properly synchronize app sampling schedule and Wakey sleep schedule. 23. IOIO seems to get some current from phone; red IOIO LED glows faint red when connected only to phone. 24. Phone power sometimes runs out in non-test conditions - not clear why. WiFi? 26. Configure option to start server at boot time, not just on auto-reboot. ESPECIALLY IMPORTANT IN CASE OF SPONTANEOUS REBOOT, WHICH HAS BEEN OBSERVED 27. check the relative drift of the Android phone and Wakey clocks before we deploy. 28. DrifterService should assert 20-minute sleep onset delay for Wakey comm port, since user may inadvertently leave some test value instead. 29. If the coms delay time is greater than the sleep time, causing the coms power to be already on when Wakey awakes, then the action of electronically pushing the SPOT power button to turn SPOT on may instead turn it off. To prevent this, the Wakey code should check to see if the coms power is already on before pushing the SPOT power button. 31. Wakey RX, TX pins default to 0. Should default to 6, 7 Done 1. GUI to stop service 5. Fix rx/tx pin property bug (DrifterService reads property as string, should be int) Appears to work if rx/tx pin properties are stored as strings 9. Do not try to send message to SPOT while SPOT is in transmit state 12. Check into version control 6. If SPOT selected, check that Bluetooth is enabled before starting run 10. Warn user of unneeded power use (e.g. Wifi, cell radio) when starting a run 11. Enable log-only run, i.e. no telemetry specified 8. Implement Wakey control, Wakey test 7. If GPS selected, check that GPS enabled before starting run 14. Log debug/info/error messages to a file.. File would be accessed after recovery. 13. If ioio connection fails, no data is telemetered (e.g. not even phone sensor which doesn't require ioio) 4. Log engineering data. Telemeter engineering data; phone battery state, Wakey battery state, etc 19. Implement compass acquisition 20. Design/implement succinct SPOT message format. Each message can probably include both science and engineering data 21. Sample schedule does not run when no telemetry channel selected (bug) 22. App and wiring on amplifier board do not agree on analog pin number. Compared app analog readout to IOIODiagnostic app (from market); IOIODiagnostic shows expected voltages on pins, so datalogger must be improperly reading analog channels. 25. Consider occasional programmatic reboot of phone to improve reliability - this requires 'rooting' the phone. 2. Data log format 3. Log science data

Document generated by Confluence on Feb 03, 2026 15:53