AeroComm ZB2430 manual A P I R e c e i v e P a c k e t, A P I O P E R A T I O N

Models: ZB2430

1 62
Download 62 pages 17.51 Kb
Page 47
Image 47
A P I O P E R A T I O N

4 2

A P I O P E R A T I O N

*Note: Send Data Complete may report a failure though the packet arrived due to timing issues. It will never report successful though unless the packet absolutely arrived.

F i g u r e 1 3 : S e n d D a t a C o m p l e t e p a c k e t f o r m a t

Start Delimiter

0x82

Request

Data

Data

 

Coordinator/Router

End Device

 

Byte 2; TX Cost

Byte 2; 0xFF

 

Byte 3: RX Cost

Byte 3: 0xFF

 

Byte 4: Success

Byte 4: Success

 

 

0x00: Fail

0x00: Fail

 

 

0x01; Success

0x01: Success

 

 

 

 

 

 

 

 

 

 

 

 

 

A P I R e c e i v e P a c k e t

By default, the source MAC is not included in the received data string sent to the OEM Host. For applications where multiple radios are sending data, it may be necessary to determine the origin of a specific data packet. When API Receive Packet is enabled, all packets received by the transceiver will include the MAC address of the source radio as well as an RSSI indicator which can be used to determine the link quality between the two.

API Receive Packet is enabled when bit-0 of the API Control byte is enabled. Upon receiving a RF packet, the radio sends its OEM Host the data as shown in Figure 14 below.

F i g u r e 1 4 : R e c e i v e A P I p a c k e t f o r m a t

Start Delimiter

0x81

Request

Data

Bytes 2-3: Payload Data Length. PDL Lo then PDL Hi.

Byte 4: RSSI

Byte 5; 0x00

Byte 6-7: 16-bit Network Source Address (Hi, Lo)

Byte 8-n: Payload Data

Page 47
Image 47
AeroComm ZB2430 manual A P I R e c e i v e P a c k e t, F i g u r e 1 4 R e c e i v e A P I p a c k e t f o r m a t