What steps will reproduce the problem?
1. Use two arduino leonardo, two arduino xbee shileds v1.1 and two xbee s2
modules xb24-bwit-004 rev C (former xbee znet 2.5, now updated to xbee zb with
firmware version 2*A7).
2. Setup one xbee module to be coordiantor, other to be router.
3. For TX-node with coordinator xbee use code
https://github.com/PIlin/arduino-experiments/blob/master/xbee_api_tx/src/sketch.
ino
It waits till xbee will claim that it's connected to the network. Then, it will
send ZBTxRequest (line 172-212) every time when got ZB_TX_STATUS_RESPONSE from
previos transmission or every 5 seconds if there was no ZB_TX_STATUS_RESPONSE.
4. For RX-node with router xbee use code
https://github.com/PIlin/arduino-experiments/blob/master/xbee_api_rx/src/sketch.
ino It just prints info about every received package.
What is the expected output? What do you see instead?
I expect to get message ZB_RX_RESPONSE on RX-node and ZB_TX_STATUS_RESPONSE
with success status on TX-node. Instead, I got nothing on both nodes.
What version of the product are you using? On what operating system?
xbee-arduino Release 0.4 (beta)
arduino leonardo
arduino ide 1.0.2 with avr-gcc (GCC) 4.3.2
Please provide any additional information below.
1. There is two hardware serials on leonardo, so I use Serial to communicate
with computer and Serial1 to communicate with xbee. If you will try to run my
code, it waits until connection from computer to Serial is established.
2. I know that my code is working because I have tested in next configurations:
1) RX-node is coordinator and TX-node is router, i.e. roles of nodes and xbee's
are opposite.
2) RX-node and TX-node are both routers and there is coordinator node enabled
and located nearby;
In all cases I have changed 64-bit address in tx code on line 203 appropriately.
3. I know that coordinator is alive on TX-node because I send ATAI every 5
seconds (line 315) and I got answer with status 0 (coordinator formed network
network).
Original issue reported on code.google.com by ilin...@gmail.com on 6 Feb 2013 at 2:16
Original issue reported on code.google.com by
ilin...@gmail.com
on 6 Feb 2013 at 2:16