Api Types; Rf Module Status - Digi XTend User Manual

To test data integrity, a checksum is calculated and verified on non-escaped data.
To calculate: Not including frame delimiters and length, add all bytes keeping only the lowest 8 bits of the result and
subtract from 0xFF.
To verify: Add all bytes (include checksum, but not the delimiter and length). If the checksum is correct, the sum will
equal 0xFF.

API Types

Frame data of the UART data frame forms an API-specific structure as follows:
Start Delimiter
(Byte 1)
0x7E
The cmdID frame (API-identifier) indicates which API messages will be contained in the cmdData frame (Identifier-
specific data). Refer to the sections that follow for more information regarding the supported API types. Note that
multi-byte values are sent big endian.

RF Module Status

API Identifier: 0x8A
RF module status messages are sent from the module in response to specific conditions.
RF Module Status Frames
Start Delimiter
0x7E
TX (Transmit) Request: 16-bit address
API Identifier Value: 0x01
A TX Request message will cause the module to send RF Data as an RF Packet.
XTend RF Module User Guide
Length Frame Data
(Bytes 2-3) (Bytes 4- n)
MSB LSB API-specific Structure
API Identifier
cmdID
Length Frame Data
MSB LSB API-specific Structure
API Identifier Identifier-specific Data
0x8A
0 = Hardware reset
1 = Watchdog timer reset
Checksum
(Byte n + 1)
1 Byte
Identifier-specific Data
cmdData
Checksum
1 Byte
cmdData
Status (Byte 5)
API operation
59