Trace: • tailcontrol-breaking-changes

Menu

Community Telegram Chats

Special Wiki Pages

Special Thanks!

This Wiki wouldn't be possible without @ToeiRei. Thank you for all of your help and guidance. Another special mention goes out to @Darkgrue, who writes and maintains the technical documentation.

This is an old revision of the document!

TailCoNTROL Breaking Changes

This is a list of breaking changes in the TailCoNTROL Protocol from previous firmware versions.

IMPORTANT NOTICE: TailCoNTROL and the TailCoNTROL Protocol is still under development. Some commands and features described here relate to a future release and are subject to change at this time, especially EarGear 2 features.

  • Most command responses changed to OK and ERR. Move state responses still exist (e.g., <movename> BEGIN upon start, and <movename> END upon completion).
  • OTA responses now BEGIN OTA, OTA ERR, and OTA SUCCESS.
  • BLE MTU changed to 512.
  • EarGear 2 support is currently intended to require a forced update of the application and the firmware so that both can support the significant changes to the EarGear 2:
    • EarGear 2 moves are now internal to the firmware, and called with the same move commands as other products (e.g., TAILFA).
    • DSSP and USERMOVE will operate identically across all products, including the EarGear 2.
    • Listen Mode and Tilt Mode for EarGear 2 runs onboard the firmware, but still emits triggers back to the application.
    • HWVER Returns EG2 x.x for EarGear 2 controller hardware, instead of HWVER B.
  • CONFRD command removed, replaced by READCONF and READNVS.
  • CONFWR command replaced with WRITECONF.
  • Speculative: TailCoNTROL will use a new Service and Characteristics UUIDs going forward, to distinguish it from previous firmwares (and to further enforce the “forklift upgrade” required).
  • Speculative: “VER ” will be removed from the VER response. Both VER and HWVER will return the version number string, and hardware identifier strings only.
Back to top