Skip to content

Commit 1af013c

Browse files
Clarify data frame limitations in KISS modem documentation.
1 parent 02ddc05 commit 1af013c

1 file changed

Lines changed: 2 additions & 1 deletion

File tree

docs/kiss_modem_protocol.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,7 @@ Maximum unescaped frame size: 512 bytes.
5656
|------|-------|------|-------------|
5757
| Data | `0x00` | Raw packet | Received packet from radio |
5858

59-
Data frames carry raw packet data only, with no metadata prepended.
59+
Data frames carry raw packet data only, with no metadata prepended. The Data command payload is limited to 255 bytes to match the MeshCore maximum transmission unit (MAX_TRANS_UNIT); frames larger than 255 bytes are silently dropped. The KISS specification recommends at least 1024 bytes for general-purpose TNCs; this modem is intended for MeshCore packets only, whose protocol MTU is 255 bytes.
6060

6161
### CSMA Behavior
6262

@@ -268,6 +268,7 @@ Data returned in CayenneLPP format. See [CayenneLPP documentation](https://docs.
268268

269269
## Notes
270270

271+
- Data payload limit (255 bytes) matches MeshCore MAX_TRANS_UNIT; no change needed for KISS “1024+ recommended” (that applies to general TNCs, not MeshCore)
271272
- Modem generates identity on first boot (stored in flash)
272273
- All multi-byte values are little-endian unless stated otherwise
273274
- SNR values in RxMeta are multiplied by 4 for 0.25 dB precision

0 commit comments

Comments
 (0)