Balancerator: Bluetooth message reference
Bluetooth crib: 1=current angle, 2=average, 3=run mechanism
missing bits: delimiter? ack? reconnect mid-command? don't let a half-packet turn into a real angle
Updated protocol from the app notes:
| Request | Purpose | Response / behavior |
|---|---|---|
1 |
Current inclination; table says every 3 s | c + sign (n/p) + three digits |
2 |
Average inclination since last transmission | a + sign (n/p) + three digits |
3 |
Model reports an unbalanced position | Device begins prevention mechanism for 1 minute; app suspends other requests for that minute |
Fall counts are tracked locally in the revised app, rather than sent as a second response to request 2. The table leaves average-request timing as alternatives—manual update, 1 minute or 3 seconds—so this is not a single finalized scheduler.
Review questions: specify message delimiters and malformed-packet handling; whether angles are integers or scaled values; what acknowledgment confirms 3; and what happens on disconnect/reconnect during the suspended interval. None of those behaviors is defined by the table. The one-minute mechanism behavior is a recorded design choice, not a newly validated control recommendation.
App and Bluetooth control flow.