Problem with the test utility

wiability · **Joined:** Fri Jan 13, 2012 8:21 pm **Posts:** 14

I just received my waspmote package and I am trying to test it using the test.pde code.
I am getting a compilation error that complains about something in the waspsensorparking module!
This is the actual error message:

C:\waspmote-ide-v.01-windows\hardware\cores\waspmote-api-v.022\WaspSensorParking.cpp: In member function 'void WaspSensorParking::loadReference()':

C:\waspmote-ide-v.01-windows\hardware\cores\waspmote-api-v.022\WaspSensorParking.cpp:123: error: 'eeprom_read_float' was not declared in this scope

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

Dear wiability,

You are true. We apologize because there is a compilation problem with API version 022.

As is said here, try with version 021 while we fix the issue.

viewtopic.php?f=14&t=8331

Kind regards

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

Dear wiability,

We already have fixed bug on API V022.

Download it from here: http://www.libelium.com/development/waspmote

Sorry for the inconvenience.

Kind regards

wiability · **Joined:** Fri Jan 13, 2012 8:21 pm **Posts:** 14

I still have the same problem. Am I doing something wrong?
I downloaded the IDE again and extracted it to the C:\ and then downloaded the new API v022 and copied it over the old one in the hardware\cores folder.
I open the test.pde file from the buttons menu and press verify at which time I get the previously mentioned error message. Is there any other steps that I am missing?
I am curious about one thing. If the API has been fixed why is it then that no file in that folder has a modification date of Jan 2012?

wiability · **Joined:** Fri Jan 13, 2012 8:21 pm **Posts:** 14

I just compiled successfully using API v021. I don't think the v022 on the download website is fixed yet.

wiability · **Joined:** Fri Jan 13, 2012 8:21 pm **Posts:** 14

Now, I am struggling with uploading.
I think I have a serial comm. synchronization problem. The error message is:

Binary sketch size: 2500 bytes (of a 126976 byte maximum)

avrdude: stk500_getsync(): not in sync: resp=0x7e
avrdude: stk500_disable(): protocol error, expect=0x14, resp=0x7e

The quick start document refers to chapter 14 of a manual for configuring the serial monitor application. Which manual is this? If it is the technical guide, it didn't help me. However, I verified that I am using 38000 baud rate but I cannot set other parameters such as the stop bits and parity.

By the way, I am using the on-board antenna on the waspmote not an external antenna but the gateway has an antenna. They are 2 inches away though.
Your help is appreciated.

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

Wiability,

API 022 bug was related with a function missed on the AVR compiler. That is why you do not see changes in files inside core. Now API 022 works perfectly.

Now, getting into your error, make sure you correctly select your board and your serial port. Also make sure you remove Xbee before uploading the code.

Quote:

I am using the on-board antenna on the waspmote not an external antenna

What do you mean with this? are you referring to Xbee antenna?

Kind regards

wiability · **Joined:** Fri Jan 13, 2012 8:21 pm **Posts:** 14

libelium-dev wrote:

Wiability,

API 022 bug was related with a function missed on the AVR compiler. That is why you do not see changes in files inside core. Now API 022 works perfectly.

Wiability: the only thing that I know is that as soon as I replaced 022 with 021, I was able to compile the test code.

Now, getting into your error, make sure you correctly select your board and your serial port. Also make sure you remove Xbee before uploading the code.

Wiability: I am choosing the usb port where the gateway is connected (COM6 in my case) and I only see one option for the board which is wasp_022. How can I change this? I may have to use wasp_021, right? Also, I did not remove the XBee module before uploading. Isn't that where the antenna is? Besides, what would you do after deployment, when the sensors are in the field and you want to upload to them using OTA?

Quote:

I am using the on-board antenna on the waspmote not an external antenna

What do you mean with this? are you referring to Xbee antenna?

Wiability: I mean I did not buy a SMA antenna (XBee?) for the sensors. Would they still be able to connect to the gateway?

Kind regards

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

Dear Wiability,

Let's go by parts into your problem.

First of all, please check this topic, where the process of including a new API is described.

That process will allow you to select between various API versions.

Secondly, the reason of unplugging Xbee to allow uploading a code to Waspmote is because USB and Xbee shares UART0 of the microcontroller (you can read in this forum a lot of topics regarding this). Therefore if you do not unplug your Xbee, it will interfere with USB port making uploading process impossible.

However, in OTA, communication is only between Xbee and Waspmote and the code is uploaded by the Xbee, not by USB.

Please, we kindly ask you to read carefully check-list post and follow all steps. If you find any issue please let us know.

Also we recommend you to read Waspmote technical guide, where hardware inside Waspmote is described and also the tips for right usages.

Try to upload the test code with API version 21 to see if your hardware is working well.

Waiting your comments.

Best regards.

wiability · **Joined:** Fri Jan 13, 2012 8:21 pm **Posts:** 14

After a long period of recess, I have finally come back to this project. I have been now to communicate with the sensors using the new API.
Now, I have a new problem. Out of the 5 waspmotes, one of them seems to have a problem with Xbee. It does not send anything to the gateway but when I connect it with the USB cable I can see the messages it sends.
I bought this kit back in February but I am only now really testing it.
I switched the XBee module with another waspmote and it was the same situation. It seems that the problem is in the main board.
Thanks for your response in advance.