Hi Libelium!!

I want to include OTAP programming inside the code of a Waspmote, which periodically sends frames (with sensors measures) to a Meshlium, in order to allow the Meshlium update that code once a day. Before entering this programming to my code, I'm doing some tests to the OTAP tool in Meshlium and I've found what I believe is a bug.

First of all, I have stopped the zigbee storer: "# /etc/init.d/ZigbeeScanD.sh stop". Then, I have loaded the example code "WaspOTA_DM_1" in the Waspmote, and I've sent a new program to the Waspmote from the Meshlium: "./otap -send --file Test_Transmision.cpp.hex --mode UNICAST --mac 0013A20040779154 --pid test001". After a couple of minutes, the Waspmote answers "PROGRAM RECEIVED OK".

After that, I launched the zigbee storer: "# /etc/init.d/ZigbeeScanD.sh start" and the answer was: "# (null)". And the process zigbeeStorer was interrupted, because there was no process zigbee running in the Meshlium. So I stopped the storer again and I downloaded the code zigbeeStorer.c from your website. After compiling this code I launched it, and the answer was:

"# /etc/init.d/ZigbeeScanD.sh start
ERROR - Unable to parse received frame: ·························································"

I checked the zigbeeStorer.c code and, in the function parseFrame I found:
if (error){
fprintf(stderr, "ERROR - Unable to parse received frame: %s\n",aux);
exit(-1);
}

so I I've figured that the Meshlium was receiving strange frames after doing the OTAP sending. And no matter how many times you launch the storer because the answer is always the same.

Any idea?

Thanks a lot.

Looks like there was a problem with my post:

Hi Libelium!!

I want to include OTAP programming inside the code of a Waspmote, which periodically sends frames (with sensors measures) to a Meshlium, in order to allow the Meshlium update that code once a day. Before entering this programming to my code, I'm doing some tests to the OTAP tool in Meshlium and I've found what I believe is a bug.

First of all, I have stopped the zigbee storer: "# /etc/init.d/ZigbeeScanD.sh stop". Then, I have loaded the example code "WaspOTA_DM_1" in the Waspmote, and I've sent a new program to the Waspmote from the Meshlium: "./otap -send --file Test_Transmision.cpp.hex --mode UNICAST --mac 0013A20040779154 --pid test001". After a couple of minutes, the Waspmote answers "PROGRAM RECEIVED OK".

After that, I launched the zigbee storer: "# /etc/init.d/ZigbeeScanD.sh start" and the answer was: "# (null)". And the process zigbeeStorer was interrupted, because there was no process zigbee running in the Meshlium. So I stopped the storer again and I downloaded the code zigbeeStorer.c from your website. After compiling this code I launched it, and the answer was:

"# /etc/init.d/ZigbeeScanD.sh start
ERROR - Unable to parse received frame: ········································"

I checked the zigbeeStorer.c code and, in the function parseFrame I found:
if (error){
fprintf(stderr, "ERROR - Unable to parse received frame: %s\n",aux);
exit(-1);
}

so I I've gathered that the Meshlium was receiving strange frames after doing the OTAP sending. And no matter how many times you launch the storer because the answer is always the same.

Any idea?

Thanks a lot.

Well, I don`t know what is happening, but my posts can't be read properly. Please, copy the post into your clipboard and then paste it in other place.

Thank you in advance

Dear myself,

Our original Zigbee storer daemon only can parse the default Waspmote frames, if you send your custom frames you also need to modify the daemon code.

You can also view the data you are receiving from the console with the capturer comand:



and then enter , XBee module will reply "ok"

Best regards.

Dear libelium-dev,

I think you haven't understood me. What I tried to explain was that your zigbee Storer is incompatible with your OTAP process. I only used your own programs, of course I have my own code which generates my custom frames, but I detected the bug using your codes.

And, as I said in my post, the problem is not related to the sensor frames. First, I stop the daemon. Then, I send a program via OTAP to the waspmote. Finally, I launch the daemon and it shows a strange behavior.

It is a very simple process, and you can check what I'm saying.

Regards

Dear myself, we will do some tests as soon as possible, just for info and to be sure Test_Transmision.cpp.hex is the program that send your custom frames or send the factory frames?

Best regards.

Dear libelium-dev,

Thank you for your reply. Don't worry about Test_Transmision.cpp.hex, because I have only sent this code, but I have not launched it. I mean, I didn't send the start_new_program command.

Regards.

Dear libelium-dev,

I have checked that when I launch the zigbee storer after sending a program via OTAP, it fails. But if I launch the capturer (#capturer S0 38400), it works properly and no strange frames are received.
Would you tell me which are the differences between both programs? Could you please send me the source code of this "capturer"?

Thanks in advance.

Regards

Dear myself, capturer program just only open the serial port and prints all data that receives the serial port.

If the capturer does not show unusual characters is that the storer is processing bad frames.

Best regards.

Dear myself,

You can download the capturer and storer source codes from:
http://www.libelium.com/forum/libelium_files/meshlium_capturer.tar.gz
http://www.libelium.com/forum/libelium_files/meshlium_zigbeestorer.tar.bz2

Best regards.