Home/Support/Support Forum/Packetization in API mode (Xbee S2)

Packetization in API mode (Xbee S2)

0 votes
The packetization rules (entering command mode, 100 bytes in buffer and RO timeout) for Xbee S2 (for example) also apply when operating in API mode? I think that API packets are never splited as long as it does not exceed the maximum applicable packet length, even occuring a pause when sending a packet to the module. I'm correct?
asked Feb 10 in RF Solutions and XBee by Curl New to the Community (2 points)

Please log in or register to answer this question.

2 Answers

0 votes
Curl, No. It is the API frame that determines the packet length. One the full frame is received, it is processed.

Eric
Digi Support
answered Feb 12 by mvut Veteran of the Digi Community (11,751 points)
0 votes
"...Curl, No. It is the API frame that determines the packet length. One the full frame is received, it is processed..."

Eric, thank you for your response, but I don't ask about the packet length itself, but the packetization rules (if any) in API mode. My question refers to the possibility (or not) of a frame being transmitted fragmented. I do not think so. For example. what happens if I try to send 60 bytes with pause (30 bytes, 1 second pause and 30 more bytes)?
Or to send the module 500 bytes before the checksum (module's input buffer size here)?
answered Feb 13 by Curl New to the Community (2 points)
Curl,

When using the API code or API mode, the RO command is not used.
...