Description

This frame type is used to send payload data as an RF packet to a specific destination using application-layer addressing fields. The behavior of this frame is similar to TX Request Message - 0x1A, but with additional fields available for user-defined endpoints, cluster ID, and profile ID.

This frame type is typically used for over-the-air (OTA) updates and serial data transmissions.

Query NP (Max Packet Payload Bytes) to read the maximum number of payload bytes that can be sent.

Format

The following table provides the contents of the frame. For more details on frame structure, see API Frames.

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

0x19

4

8-bit

Frame ID

Identifies the data frame for the host to correlate with a subsequent response (0x89).

If set to 0, the device will not emit a response frame.

5

128-bit

Destination IPv6 Address

Binary representation of 128-bit address. It is always 16 bytes (128 bits) with all zero fields included.

21

16-bit

Cluster ID

Specifies the desired XBee service:

  • 0x0023 - GPM Service

  • 0x0012 - Loopback

23

8-bit

TX options

Reserved for future use (should be set to zero).

24

variable

data

Depends on the service:

  • Using GPM service: data will always begin with an 8-byte GPM header.

  • Using loopback service: raw data, limited in size by ATNP.

EOF

8-bit

Checksum

0xFF minus the 8-bit sum of bytes from offset 3 to this byte (between length and checksum).