Recieved API frame is DIFFERENT from the sent one!!

XBee & XBee Gateway XBee - Zigbee
1

Hi,
I’m facing an odd comunication problem.
I have one XBee “ZNET 2.5 ROUTER/END DEVICE API” which sends API frames to its XBee “ZNET 2.COORDINATOR API”, and monitoring the communication with X-CTU utility: everything is working ok, BUT the recieved data is NOT what I’d expect.
Here is one communication loop:

Sent by ZNET 2.5 ROUTER/END DEVICE API (30 bytes):

Start byte: 7E
Length: 00 1A
API ID: 10
Frame ID: 65
Addr64: 00 00 00 00 00 00 00 00
Addr16: FF FE
Radius: 00
Options: 00
MyData: 78 48 48 48 79 48 48 48 7A 48 48 48 (12 ASCII bytes = “x000y000z000”)
CRC: 8D

Recieved by ZNET 2.COORDINATOR API (only 28 bytes??!!):

7E (Start byte)
00 18 90 00 (???)
13 A2 00 (TX’s SH)
40 30 33 CB (TX’s SL)
22 11 (TX’s MY)
01 (???)
78 48 48 48 79 48 48 48 7A 48 48 48 (My 12 ASCII bytes = “x000y000z000”)
E2 (CRC? Of what??)

My questions are (for which I counldn’t find a response in the XB24-BPDK.pdf doc):

  1. Why isn’t the recieved frame equal to the transmitted one? And if this is correct, what is the RX frame structure?
  2. What is the meaning of the bytes with the “(???)” comment?
  3. Where is my frame ID, which is absoloulty necessary to me to identify the frame type in my application?
  4. How is the recieved CRC (0xE2) calculated?

Thank you very much in advance.

Best Regards,
G

Message was edited by: gianni

SORRY: never mind, got my response at pag 52 of the doc.
Thank you anyway!