# problem with connection between xbees

**URL:** <https://forums.digi.com/t/problem-with-connection-between-xbees/12110>\
**Category:** XBee & XBee Gateway\
**Tags:** xbee\
**Created:** [October 28, 2013, 4:30pm UTC](https://forums.digi.com/t/problem-with-connection-between-xbees/12110 "2013-10-28T16:30:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![seyounes01](https://avatars.discourse-cdn.com/v4/letter/s/a587f6/32.png) [@seyounes01](https://forums.digi.com/u/seyounes01)\
**Post date:** [October 28, 2013, 4:30pm UTC](https://forums.digi.com/t/problem-with-connection-between-xbees/12110/1 "2013-10-28T16:30:28Z")

</div>

hey  
i have now two xbees connected each to xbee shield and one of them is connected to an arduino board without the microcontroller and the other to an arduino board with the controller…the one with no microcontroller on it is connected to the pc directly by a usb cable and the xbee module is configured to be the router…and the other with the microcontroller is powered by a battery and the xbee module is configured to be the coordinator  
if i open the xctu and i write something in the terminal window i can see that di led on one xbee shield is blinking and the do led on the other xbee shield is blinking also…  
how can i know that the xbees are connected ? because when i perform range test i receive time out waiting for data but i can see that the di led on one is blinking along with the do led on the other.  
any ideas?

---

<div class="post-metadata">

**Author:** ![kjensen8](https://avatars.discourse-cdn.com/v4/letter/k/8e8cbc/32.png) [@kjensen8](https://forums.digi.com/u/kjensen8)\
**Post date:** [October 30, 2013, 5:40pm UTC](https://forums.digi.com/t/problem-with-connection-between-xbees/12110/2 "2013-10-30T17:40:40Z")

</div>

make sure you’re setting up the test properly:  
[http://www.digi.com/support/kbase/kbaseresultdetl?id=2194](http://www.digi.com/support/kbase/kbaseresultdetl?id=2194)

Also:  
RANGE TEST DIRECTIONS:  
You’ll need to make the following settings on the testing node:  
NJ=0  
Testing node DH = target nodes SH  
Testing node DL = target nodes SL  
Testing node DI = 0x12

Then do a network reset to insure the network end nodes rejoin to the easily seen router. You’ll need to go to: XCTU -\> terminal tab: then enter:  
+++  
atnr1

(doing ‘+++’ puts the node into command mode. From there you can enter the ‘atnr1’ command which will force the entire network to reset. Setting NJ=0 will prevent the end nodes from joining your testing node. We want to avoid this behavior because you will remove it when you’re finished. We want the end nodes to associate with your newly introduced router, not your testing node.)