API frame exchanges

Every outgoing API frame has a corresponding response (or ACK) frame that indicates the success or failure of the outgoing API frame. This section details some of the common API exchanges that occur.

You can use the Frame ID field to correlate between the outgoing frames and associated responses.

Note Using a Frame ID of 0 disables responses, which can reduce network congestion for non-critical transmissions.

AT commands

The following image shows the API frame exchange that takes place on the serial interface (UART or SPI) when you send a 0x08 AT Command Request or 0x09 AT Command-Queue Request to read or set a device parameter. To disable the 0x88 AT Command Response, set the frame ID to 0 in the request.

Transmit and Receive RF data

The following image shows the API exchanges that take place on the serial interface when a device sends a 0x10, or 0x11 Transmit Request to another device.

The device sends the 0x8B Transmit Status frame at the end of a data transmission unless you set the frame ID to 0 in the transmit request. If the packet cannot be delivered to the destination, the 0x8B Transmit Status frame indicates the cause of failure.

Use the AO command to choose the type of data frame you want to receive, either a (0x90) RX Indicator frame or a (0x91) Explicit Rx Indicator frame.

Remote AT commands

The following image shows the API frame exchanges that take place on the serial interface when you send a 0x17 Remote AT Command frame The 0x97 Remote AT Command Response is always generated and you can use it to identify if the remote device successfully received and applied the command.

Device Registration

The following image shows the API frame exchanges that take place at the serial interface when registering a joining device to a trust center.