Description
A TX request message causes the device to transmit data in IPv6 format. A TX request frame for a new destination creates a network socket. After the network socket is established, data from the network that is received on the socket is sent out the device’s serial port in the form of a Receive (RX) Packet frame.
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 |
0x1A |
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 |
Destination Port |
UDP or TCP port on which to send data. (To use the transmission options, destination port must be 0xBEE.) |
23 |
16-bit |
Source Port |
UDP or TCP port. |
25 |
8-bit |
Protocol |
Supported protocols:
|
26 |
8-bit |
Transmit Options |
Bit field (if destination port is 0xBEE). Bit field Reserved Default: 0 |
27 |
Variable |
Payload |
Data to be transferred to the destination. |
EOF |
8-bit |
Checksum |
0xFF minus the 8-bit sum of bytes from offset 3 to this byte (between length and checksum). |
