- FIX: main branch hang at startup when enabling FTMS
- Verify that the speed (duplicate of Keiser/Peloton) is being calculated correctly
- Documentation
- More comprehensive writeup of calibration
- Writeup on power consumption
- Calibration
- Think about approaches to a two-point calibration (without a Keiser computer reference?)
- Keeping more parameters or options in the filesystem, such as
- Gear vs. Res% display
- Filtering
- Consider flashing the gear/resistance display when the lever is at the top (instead of Keiser's "88").
- BLE Services
- Debug FTMS - does note appear to work with Zwift
- Improve the display: larger size with more data?
- Things maybe to add
- Speed
- Accumulated data
- Distance - requires a speed estimate
- Calories - requires a model
- Elapsed time
- Things maybe to add
- Other uses for swings of the resistance lever as a signal
- e.g., reset ride between people, if providing accumulated data
- More comprehensive code cleanup
- Split more code across multiple source files
- Clean up connect callbacks
- Code to include a battery or not is a bit clunky, especially in display_numbers()
- Review for functions that should be inline
- C++ style static consts and inline functions instead of C-style #defines and macros, where appropriate
- Option to power down the crank sensor (total power-down), for those who plan to expose a reset or wakeup switch on the packaged computer. This might not provide any meaningful advantage unless there's also a way to power down the display.
ONE DAY?
- Servo on the resistance for full FTMS function!