Scan nodes failure

jcsaez · **Joined:** Wed Feb 09, 2011 5:22 pm **Posts:** 5

Scan nodes doesn't work for me (somewhere in time did but not now). I have XBee modules configured with parameters provided by Libelium support.

Execute: otap -scan_nodes --mode BROADCAST

ZigBee network is ok, i can see RSSI leds flashing in Waspmote. Waspmote UART response this:

Code:

7E 00 2E 10 FE 00 7D 33 A2 00 40 69 02 89 FF FE 00 00 FE 01 23 00 56 78 
7D 31 7D 33 09 93 81 45 17 20 05 01 57 41 53 50 4D 4F 54 45 30 30 30 30 
30 30 30 31 67  

Note: Router is API 2 mode, thus some '7D' escape bytes can be found. Name is WASPMOTE00000001, is OK in this data frame.

But nothing is out on otap console.

Any suggestions??

libelium-dev · **Joined:** Mon Sep 28, 2009 1:06 pm **Posts:** 7440

What version of ota shell are you using?

jcsaez · **Joined:** Wed Feb 09, 2011 5:22 pm **Posts:** 5

shell v0.1.b59

libelium-dev · **Joined:** Mon Sep 28, 2009 1:06 pm **Posts:** 7440

We're going to send you a otap version with debug flags enabled. Use it and post the data showed on the screen.

AmroQuandour · **Posted:** Tue Jun 14, 2011 6:12 pm

Can you send it to me as-well? I am using Ubuntu-OS

jcsaez · **Joined:** Wed Feb 09, 2011 5:22 pm **Posts:** 5

Actually it seems one mote board is failing. In my test I'm using 2 waspmotes and send command 'otap -scan_nodes --mode BROADCAST'. The debug output is:

Code:

panID changed: 102
msg panid: 7e0006085249440102150000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
hex size: 5 expected: 9-4
-
PanID gw: 7e0000885249440098
ch msg: 7e0005085243481307150000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
CH changed: 13
hex size: 5 expected: 9-4
Channel gw: 7e0000885243480199
readFirm: 7e001c1052000000000000fffffffe0000fe01230056784c4942454c49554d5f00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
hex size: 44 expected: 70-4
7e002c900013a20040690290362301fe012300567811130993814517200501574153504d4f5445303030303030303181
hex size: 7 expected: 70-4
7e00078b52fffe00000025
hex size: 66 expected: 70-4
readFirm node: 7e0000900013a200406902891a7601fe01230056785a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a5a574153504d4f54453030303030303031d4
MAC: 0013a20040690289
msg: ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ
msg: WASPMOTE00000001
\
|
/
-
\
|
/
-
\
|
/
-
\
|
/
-
\
|
/
-
\
|
/
-
\
|
 
----------------------------------------------------------------
Total Nodes: 1 - Time elapsed: 14s
0   - Node 0013a20040690289 - WASPMOTE00000001 - ZZZZZZZ - READY
----------------------------------------------------------------

I swap XBees and always fails the same board (not XBee dependent failure?). Even if I use '--mode UNICAST' and its mac is not responding, even thought Waspmote is responding through UART correctly and wireless is working. That board is working OK with other projects. The debug output for 'unicast' scan is:

Code:

panID changed: 102
msg panid: 7e0006085249440102150000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
hex size: 5 expected: 9-4
-
PanID gw: 7e0000885249440098
ch msg: 7e0005085243481307150000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
CH changed: 13
hex size: 5 expected: 9-4
Channel gw: 7e0000885243480199
readFirm: 7e001c10520013a20040690290fffe0000fe01230056784c4942454c49554d6d00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
hex size: 7 expected: 11-4
readFirm gw: 7e00008b523623000000c9
hex size: 44 expected: 70-4
7e002c900013a20040690290362301fe012300567811130993814517200501574153504d4f5445303030303030303181
\
|
/
-
\
|
/
-
\
|
/
-
\
|
/
-
\
|
/
-
\
|
/
-
\
|
 
----------------------------------------------------------------
Total Nodes: 0 - Time elapsed: 15s
----------------------------------------------------------------

libelium-dev · **Joined:** Mon Sep 28, 2009 1:06 pm **Posts:** 7440

We will release a new Waspmote API version during this week with that problem fixed.

HellDrag · **Posted:** Wed Mar 14, 2012 1:41 pm

Hi,

I have tried to scan my 3 waspmotes with

Code:

otap64 -scan_nodes --mode Broadcast

but it doesn't recognize any of waspmotes. I have loaded the example that is on the developement section.

Can anyone tell me what is wrong.

libelium-dev · **Joined:** Mon Sep 28, 2009 1:06 pm **Posts:** 7440

Hi,

Are your XBee modules well configured? Can you check the channel, panid and encryption mode.Is the configuration file: xbee.conf configured with the same parameters?

Best regards

HellDrag · **Posted:** Tue May 08, 2012 4:20 pm

Hello libelium-dev

Sorry for not answering before, but i've had issues with the motes and i am still waiting for them, I will do a thorough check after I get them and let u know