Request frames:
Description
This frame format is deprecated and should only be used by customers who require compatibility with legacy Digi RF products. |
This frame type is emitted when a transmit request completes. The status field of this frame indicates whether the request succeeded or failed and the reason.
This frame is only emitted if the Frame ID in the request is non-zero.
Broadcast transmissions are not acknowledged and always return a status of 0x00, even if the delivery failed. |
Format
The following table provides the contents of the frame. For details on frame structure, see API frames.
Offset | Size | Field Name | 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 |
Transmit Status - 0X89. |
4 |
8-bit |
Frame ID |
Identifies the data frame for the host to correlate with a prior request. |
5 |
8-bit |
Delivery status |
Complete list of delivery statuses:
Refer to the tables below for a filtered list of status codes that are appropriate for specific devices. |
EOF |
8-bit |
Checksum |
0xFF minus the 8-bit sum of bytes from offset 3 to this byte (between length and checksum). |
Delivery status codes
Protocol-specific status codes follow.
Zigbee
This frame type is only used for indicating errors in sending a User Data Relay request
-
0x7C = Invalid interface. See User Data Relay Input - 0x2D.
-
0x7D = Interface not accepting frames. See User Data Relay Input - 0x2D.