Created basic script for reading stomp data traffic + stomp bytes explained

1 files changed, 34 insertions, 0 deletions

diff --git a/Stomps/README.md b/Stomps/README.md
new file mode 100644
index 0000000..33e23e1
--- /dev/null
+++ b/Stomps/README.md
@@ -0,0 +1,34 @@
+## Stomp message byte examples:
+
+**Action: button | Value: pressed**
+```
+9a e5 01 65 92 bf 0c 00 01 00 11 01 01 00 00 00 9a e5 01 65 92 bf 0c 00 00 00 00 00 00 00 00 00
+```
+
+**Action: button | Value: released**
+```
+9b e5 01 65 4b 74 0b 00 01 00 11 01 00 00 00 00 9b e5 01 65 4b 74 0b 00 00 00 00 00 00 00 00 00
+```
+
+**Action: rotary | Value: clock wise**
+```
+9d e5 01 65 ac 83 04 00 02 00 08 00 01 00 00 00 9d e5 01 65 ac 83 04 00 00 00 00 00 00 00 00 00
+```
+
+**Action: rotary | Value: counter clock**
+```
+9e e5 01 65 40 e8 05 00 02 00 08 00 ff 00 00 00 9e e5 01 65 40 e8 05 00 00 00 00 00 00 00 00 00
+```
+
+It seems that a 32 bytes message is divided into 2 parts of 16 bytes.
+
+### Part 1 (First 16 bytes)
+| 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10     | 11     | 12    | 13      | 14      | 15      |
+|---|---|---|---|---|---|---|---|---|---|--------|--------|-------|---------|---------|---------|
+| time | time | time | time | time | time | time | padding? | action | action | action | action | value | padding | padding | padding |
+
+### Part 1 (First 16 bytes)
+- 0 -> 6 are duplicates
+- 7 -> 15 are padding
+
+From first sight, this part look quite useless. Not sure why it's even there.
\ No newline at end of file