EditProtocol

Bidirectional
Byte ASCII Meaning Followed by
112'p'PingNothing
80'P'PongNothing
69'E'Enable/Disable command interpretation'0' to disable / '1' to enable / '2' to toggle
115's'Request settings.TODO
83'S'Send settings.TODO
-
From Arm
Byte ASCII Meaning Followed by
76'L'Single letterByte representing one letter
87'W'Previous letters form a wordNothing (Deprecated since Morse Code is not used as input system anymore)
81'Q'Previous data is wrongNothing (Deprecated since Morse Code is not used as input system anymore)
84'T'Sending plain textNull-terminated string
Sending sensors dataOne character indicating the sensor type and then null-terminated string
100'd'Request date. Client should answer with the current date and timeNothing
-
To Arm
Byte ASCII Meaning Followed by
68'D'Current date is XTwo bytes for YEAR, then MONTH,DAY,HOURS,MINUTES,SECONDS described by one byte each
86'V'Set vibrationVibration level (one byte), 0 - no vibration
114'r'Reset device (like if reset button was pressed)
108'l'Fake actionByte representing one letter

Things to remember

Is it feasible?

Maybe we should switch to some well-known format like JSON or similar?



To save this page you must answer this question:

Type "ProgArm" here: