I am using the web interface of the meshlium to attempt to configure ZigBee communication with my waspmotes. When I press the "Load MAC" button, the device first displays a popup message saying:

"During this proccess the zigbee frames storage will be stopped.
Do you want to continue?"

After I press OK, the device says:

"Please Wait..."

and after a few minutes a message pops up saying:

"Unexpected error please try again."

Has anyone had a similar issue? If not, can any of the libelium staff direct me on how I should be troubleshooting this issue? Thanks in advance.

Hello Alexy,

Please, try to connect to Zigbee by AT command, for this, you should connect to Meshlium by SSH, once you have connected, please write de follow command.


Next enter


The Zigbee module should respond with "ok", if not so, rewrite "+++", until it respond "ok".

Next step, you should write "at" and module respond "ok".

If you want know MAC address, please enter "atsl" and "atsh". Thus we have verified that the module is working properly and we've got the MAC address.



In this case MAC address is: 13a2004071e9f2. In your case MAC address will be different.

Best regarts.

I have tried the +++ command i after running "capturer S0 38400" but the zigbee module does not respond with the "ok" command:

meshlium:/mnt/lib/cfg# capturer S0 38400
setting speed 38400
ttyS0 chosen
...
Press Ctrl+c to close the program
+++
+++
+++
+++
+++
+++

Hello Alexey

You should keep in mind that 38400 is the baud rate. Try with other baud rate, if you change this baud rate.

And if not answered, please execute "ps -e" and show us the display.

Best regards.

Hi, thank you for a all your quick replies. I have tried different baud rates but there is still no communication. Here is the output for several baud rates and the ps -e command:

meshlium:/# capturer S0 2400
setting speed 2400
ttyS0 chosen
...
Press Ctrl+c to close the program
+++
+++
+++

meshlium:/# capturer S0 4800
setting speed 4800
ttyS0 chosen
...
Press Ctrl+c to close the program
+++
+++
+++

meshlium:/# capturer S0 9600
setting speed 9600
ttyS0 chosen
...
Press Ctrl+c to close the program
+++
+++
+++

meshlium:/# capturer S0 19200
setting speed 19200
ttyS0 chosen
...
Press Ctrl+c to close the program
+++
+++
+++

meshlium:/# capturer S0 38400
setting speed 38400
ttyS0 chosen
...
Press Ctrl+c to close the program
+++
+++
+++

meshlium:/# capturer S0 57600
setting speed 57600
ttyS0 chosen
...
Press Ctrl+c to close the program
+++
+++
+++
meshlium:/# capturer S0 115200
setting speed 115200
ttyS0 chosen
...
Press Ctrl+c to close the program
+++
+++
+++

meshlium:/# ps -e
PID TTY TIME CMD
1 ? 00:00:01 init
2 ? 00:00:00 kthreadd
3 ? 00:00:00 ksoftirqd/0
4 ? 00:00:00 events/0
5 ? 00:00:00 khelper
8 ? 00:00:00 async/mgr
86 ? 00:00:00 kblockd/0
94 ? 00:00:00 kseriod
144 ? 00:00:00 pdflush
145 ? 00:00:00 pdflush
146 ? 00:00:00 kswapd0
147 ? 00:00:00 aio/0
148 ? 00:00:00 nfsiod
149 ? 00:00:00 crypto/0
802 ? 00:00:00 kpsmoused
808 ? 00:00:00 rpciod/0
1558 ? 00:00:00 ata/0
1559 ? 00:00:00 ata_aux
1561 ? 00:00:00 ksuspend_usbd
1562 ? 00:00:00 khubd
1763 ? 00:00:02 udevd
2759 ? 00:00:00 kstriped
2801 ? 00:00:00 kjournald
3471 ? 00:00:00 kdmflush
3472 ? 00:00:00 kcryptd_io
3473 ? 00:00:00 kcryptd
3480 ? 00:00:00 kjournald
3536 ? 00:00:00 pump
3648 ? 00:00:00 portmap
3744 ? 00:00:00 syslogd
3757 ? 00:00:00 dbus-daemon
3768 ? 00:00:00 dnsmasq
3813 ? 00:00:00 sshd
3853 ? 00:00:00 mysqld_safe
3893 ? 00:00:03 mysqld
3894 ? 00:00:00 logger
3975 ? 00:00:00 pptpd
3985 ? 00:00:00 hcid
3997 ? 00:00:00 bluetooth
4007 ? 00:00:00 krfcommd
4053 ? 00:00:00 cron
4061 ? 00:00:00 olsrd
4068 ? 00:00:00 watchdog
4082 ? 00:00:01 apache2
4091 ? 00:00:05 BtScan.sh
4094 ? 00:00:05 GpsScan.sh
4098 ? 00:00:00 zigbeeStorer
4112 ? 00:00:00 apache2
4113 ? 00:00:00 apache2
4114 ? 00:00:00 apache2
4115 ? 00:00:00 apache2
4116 ? 00:00:00 apache2
4127 ? 00:00:00 iperf
11038 ? 00:00:00 sshd
11096 pts/0 00:00:01 bash
19864 ? 00:00:00 sleep
19865 pts/0 00:00:00 ps
meshlium:/#

Let me know what the next step should be in the troubleshooting process.

Thank you!

Alexey

Dear Alexsy,

Thanks for follow all instruction.

It seems that the XBee module is not working and must be replaced. Please fill the RMA form so that we can start a repair process.

Best regards

The shipping time puts a serious strain in my timeline. Does the meshlium use the same XBee module as the waspmotes do? I understand that openning the meshlium voids the warranty, but could you tell me a little bit about the process of replacing the XBee module within the meshlium?

Thanks!

Alexey

Dear Alexey

Our technical service need to test the entire Meshlium components, we can not be sure 100% that what fails is the XBee module and not some other component.

Best regards

Ok I understand, thank you. I have another inquiry. I understand that the XBee PRO S2 module inside the meshlium is configured to work under API coordinator mode. This version of XBee does not have enough memory to support API and AT simoultaneously. As far as I understand, the "+++" command is used for AT configuration. How is it possible for the meshlium XBee to respond with an "ok" response to our AT frame when it is configure for API communication? Am I missing something here?

Alexey

Hello Alexey,

The Meshlium XBee module enter in AT mode with +++ command, also Meshlium use XBee module in AT mode.

Best regards.