Maximum RF payload size
The NP command returns the maximum payload size in bytes. The actual maximum payload is a function of the following:
- message type (broadcast or unicast)
- AP setting
- APS encryption option
- Source-routing
Broadcasts, which cannot be encrypted with APS or fragmented have a maximum payload of 0x54 bytes (84 bytes). Unicasts where AP is 0 also have a maximum payload of 0x54 bytes. A non-zero AP means NP will be 0xFF or 255 bytes.
For broadcast messages and unicast messages when AP==0, the maximum payload is 0x54 bytes.
For unicast messages when AP is nonzero (API mode), the maximum payload is 0xFF (255 bytes) bytes. If the combination of payload and optional APS encryption overhead (EE1, TxOption 0x20) is too high, the message fragments into a maximum of five fragments. The firmware encrypts and transmits each fragment separately. The destination radio reassembles the fragments into a full message.
For Smart Energy firmware revision 5x32 and earlier, NP==0x80. As of 5x56, NP==0xFF.
The maximum payload is calculated to estimate for aggregator source-routing. To reduce the maximum payload, when an aggregator sends a source-routed message it embeds the route into the message as overhead, or into each fragment of the message, if fragmentation is necessary. If you use APS encryption (EE1, Tx Option 0x20), it reduces the number further.
The route overhead is 2 bytes plus 2 bytes per hop. The bytes are:
- One byte is the number of hops
- One byte is an index into the route list that increments in value at each hop
- Other data is a list of the 16-bit network addresses of the routing radios
Firmware revisions before 4x58 support a maximum of 11 aggregator source-routed hops. Firmware revisions 4x58 and following support a maximum of 25 aggregator source-routed hops.
Aggregator source-routed payload maximums do not apply to messages that are sourced by non-aggregator nodes, which send route records ahead of their messages to aggregators. Aggregators are either Coordinators or Routers which have the following:
- Source routing enabled or
- AR setting which is not 0xFF
The following table shows the aggregator source-routed payload maximums as a function of hops and APS encryption:
| Hops | Maximum encrypted payload | Maximum unencrypted payload |
|---|---|---|
| 1 | 255 | 255 |
| 2 | 255 | 255 |
| 3 | 255 | 255 |
| 4 | 255 | 255 |
| 5 | 255 | 255 |
| 6 | 215 | 255 |
| 7 | 205 | 250 |
| 8 | 195 | 240 |
| 9 | 185 | 230 |
| 10 | 175 | 220 |
| 11 | 165 | 210 |
| 12 | 155 | 200 |
| 13 | 145 | 190 |
| 14 | 135 | 180 |
| 15 | 125 | 170 |
| 16 | 115 | 160 |
| 17 | 105 | 150 |
| 18 | 95 | 140 |
| 19 | 85 | 130 |
| 20 | 75 | 120 |
| 21 | 65 | 110 |
| 22 | 55 | 100 |
| 23 | 45 | 90 |
| 24 | 35 | 80 |
| 25 | 25 | 70 |
PDF
