Home/Support/Support Forum/Frame starting with 0x80

Frame starting with 0x80

0 votes
Hi

I've got the following problem regarding API mode 2 data transfer.

I got coordinator connected to a linux and router on Arduino Leonardo.

From coordinator using python script I'm sendning the following data to router

data=02000105000103010203000304050404090301081801
xbee.send('tx',dest_addr_long=DEST_ADDR_LONG, dest_addr=DEST_ADDR, data=cmdRow)

In the result the follwing frame is created and send from coordinator:
7e:00:24:10:01:00:7d:33:a2:00:40:b1:91:62:40:2e:00:00:02:00:01:05:00:01:03:01:02:03:00:03:04:05:04:04:09:03:01:08:18:01:93

I'm receiving the following tx response:

{'retries': '\x00', 'frame_id': '\x01', 'deliver_status': '\x00', 'dest_addr': '@.', 'discover_status': '\x00', 'id': 'tx_status'}

Which suggest that the frame was delivered successfully.

Unfortunatelly on router nothing seems to bee received (Neither xbee.getResponse().isAvailable() or xbee.getResponse().isError() is true)

I started to debug Xbee library and if find out that router indeed receives frame but the frame is incorrect as it does not starts with 7e !!! I receive the following frame:
80:80:80:78:78:80:80:80:F8:78:F8:78:F8:F8:F8:78:80:78:78:78:F8:78:80:F8:F8:78:78:F8:78:41

And now is the best part of my problem....

If only I connect to Coordinator using moltosenso (X-CTU like software on Linux) and issue Network Discovery and then I disconnect and try to send the same data from python script again it all works and I receive proper frame on router !!(7E:22:90:7D:A2:40:B1:89:B7:01:2:1:5:1:3:1:2:3:2:8:3:5:9:4:6:1:18:1:37)

And from now till next powering off the arduino device (with router) commincation is working between coordinator and router is working as expeted

Please note that executing ND command from python script on coordinator does not results the same. In the response of ND command I receive router data (so coordinator is discovering the router) but when after that I'm sending data in api mode the frame received on router is still starting with 0x80 so it's wrong.

Is anybody able to help me?
asked Feb 1, 2015 in DigiMesh Proprietary Mesh Networking by mroziken New to the Community (1 point)

Please log in or register to answer this question.

2 Answers

0 votes
Do you have this same issue if you just leave the radio connected to a PC and some sort of terminal emulator that can view Hex data?
answered Feb 2, 2015 by mvut Veteran of the Digi Community (14,807 points)
0 votes
I would like to request you to close the issue. It looks like firmware update solved the issue.
answered Feb 3, 2015 by mroziken New to the Community (1 point)
...