melfely/rnavp
1
1
Fork 0
Code Issues Pull Requests Actions Packages Projects 1 Releases Wiki Activity

Fixed a bit of a syntax issue

Browse Source
This commit is contained in:
melfely
2026-07-31 02:48:59 +00:00
parent 47b67917d3
commit 00ce10e3ab
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+4 -4
View File
@@ -85,11 +85,11 @@ This will then allow for the host to know HOW to send a valid packet to the MCU
| ----- | ----------- | --------- | ------- | ----------------- | ------------------ | ------------------- | --------- |
| Hex | 0x0D 0x00 | 0x00 0x04 | 0x00 | 0x00 | 0x01 | 0x01 0x00 0x00 0x00 | 0x37 0x13 |
| Human | 13 | 1024 | 0 | CommunicationInfo | Postcard (Default) | 1 | 0x1337 |
Explanation of all the numbers
Packet size -> there are 13 total bytes in this packet. Including the header
Port -> Must be above 1023, as 1024 is the first non-privileged port.
Context -> MCU (Server) starts context value, it will pick a random value within the 255 value range, expecting the Host (Client) to start from that, NOT 1 or 0. 0 Is ONLY valid for a CommunicationInfo Packet.
Explanation of all the numbers
- Packet size -> there are 13 total bytes in this packet. Including the header
- Port -> Must be above 1023, as 1024 is the first non-privileged port.
- Context -> MCU (Server) starts context value, it will pick a random value within the 255 value range, expecting the Host (Client) to start from that, NOT 1 or 0. 0 Is ONLY valid for a CommunicationInfo Packet.
## Wire Rules