What steps will reproduce the problem?
I setup 1 network with XB24-ZB module:
1 Xbee Coordinator API firware 21A7 (PANID=1;OP=1;CH=1A;NT=3C;NC=A) Using XBee
Explorer USB, install the XBee Internet Gateway for window platform as this
link : http://code.google.com/p/xig/wiki/Windows_Installation
*. Then I setup another 4 Routers with AT Firmware 22A7
(PANID=1;OP=1;CH=1A;NT=3C;NJ=FF;JV=1). I also use 4 XBee USB interface boards
to power on these Router for testing.
if I using X-CTU program connect to Coordinator I can discover all the zigbee
router and also can do API remote command to every router without any
problem.(You can see in picture Case1 & Case2 in zip file)
Then I run xig_app.exe to start the XIG application.
After add this gateway to my idigi cloud account successful. I can
commumication and send command to 4 Router by webservice.
I then went to Web Services - Examples - SCI - RCI - XBee - Discover Nodes
example and modified it to have the device id of my gateway. I then posted the
request and in my response I got the respond with only ID adddress with
Gateway. This Node discover command can only work with 3 Routers or less. More
than 4 router it does not work, and the response only have the Address of
Gateway(Coordinator). you can see in the picture Case 3.
And Sometime if I reset the Coordinator and just power on 3 Router I can
discover 3 address of these Routers. But when I continued power the Router
number 4...it comeback to received only Coordinator address.
What is the expected output? What do you see instead?
Suppose to see the address of all the router. But we only can see the address
of gateway xbee module when we power on more than 4 router in the network.
What version of the product are you using?
1.Xbee Coordinator API firware 21A7
2. 4 Routers with AT Firmware 22A7
Please provide any additional information below.
If we using XCTU program from digi we can discover all the routers in the
network.
Original issue reported on code.google.com by johnniet...@gmail.com on 20 Nov 2012 at 6:46
Original issue reported on code.google.com by
johnniet...@gmail.com
on 20 Nov 2012 at 6:46Attachments: