Request frames:
This frame type contains the DigiMesh routing information for a remote device on the network. This route information can be used to diagnose marginal links between devices across multiple hops.
This frame type is emitted in response to a DigiMesh unicast transmission request which has Trace Routing or NACK enabled. See Trace route option and NACK messages for more information.
The following table provides the contents of the frame. For details on frame structure, see API frame specifications.
| Offset | Size | Frame Field | Description |
|---|---|---|---|
| 0 | 8-bit | Start Delimiter | Indicates the start of an API frame. |
| 1 | 16-bit | Length | Number of bytes between the length and checksum. |
| 3 | 8-bit | Frame type |
Route Information - 0x8D |
| 4 | 8-bit | Source event |
Event that caused the route information to be generated: 0x11 = NACK |
| 5 | 8-bit | Data length | The number of bytes that follow, excluding the checksum. If the length increases, new items have been added to the end of the list for future revisions. |
| 6 | 32-bit | Timestamp | System timer value on the node generating the Route Information Packet.The timestamp is in microseconds. Only use this value for relative time measurements because the time stamp count restarts approximately every hour. |
| 10 | 8-bit | ACK timeout count |
The number of MAC ACK timeouts that occur. |
| 11 | 8-bit | TX blocked count | The number of times the transmission was blocked due to reception in progress. |
| 12 | 8-bit | Reserved | Not used. |
| 14 | 64-bit |
Destination address |
The 64-bit IEEE address of the final destination node of this network-level transmission. |
| 21 | 64-bit | Source address | The 64-bit IEEE address of the source node of this network-level transmission. |
| 29 | 64-bit | Responder address | The 64-bit IEEE address of the node that generates this Route Information packet after it sends (or attempts to send) the data packet to the next hop (the Receiver node). |
| 37 | 64-bit | Receiver address | The 64-bit IEEE address of the node that the device sends (or attempts to send) the data packet. |
| EOF | 8-bit | Checksum | 0xFF minus the 8-bit sum of bytes from offset 3 to this byte (between length and checksum). |
Each example is written without escapes (AP = 1) and all bytes are represented in hex format. For brevity, the start delimiter, length, and checksum fields have been excluded.
The following example represents a possible Route Information Packet. A device emits this frame when it performs a trace route enabled transmission from one device—serial number 0x0013A200 4052AAAA—to another—serial number 0x0013A200 4052DDDD—across a DigiMesh network.
This particular frame indicates that the network successfully forwards the transmission from one device—serial number 0x0013A200 4052BBBB—to another device—serial number 0x0013A200 4052CCCC.
7E 00 2A 8D 12 27 6B EB CA 93 00 00 00 00 13 A2 00 40 52 DD DD 00 13 A2 00 40 52 AA AA 00 13 A2 00 40 52 BB BB 00 13 A2 00 40 52 CC CC 4E
| Frame type | Source event | Data length | Timestamp | ACK timeout | TX Blocked | Reserved | Dest address | Source address | Responder address | Receiver address |
|---|---|---|---|---|---|---|---|---|---|---|
| 0x8D | 0x12 | 0x27 | 0x6BEBCA93 | 0x00 | 0x00 | 0x00 |
0x0013A200 |
0x0013A200 4052AAAA |
0x0013A200 4052BBBB |
0x0013A200 4052CCCC |
| Route | Trace Route |
|
~30 minutes | No retries this hop | No error | N/A | Destination | Source | Node that sent this information | Next hop |