Hi,

We are using waspmote with ZB-PRO 2.4 module and we connecting X-CTU to the waspmote as explained in the tutorial (http://www.libelium.com/development/waspmote/tutorial0003 )

However when press Test/Query button on X-CTU, we dont get the correct modem type and we get no firmware version no.

The message box shows this
"Communication with Modem" OK
"Modem Type"=Name unknown (ID=429496724866984)
"Modem firmware version= "

So the Modem shows as UNKNOWN in Modem Configuration tab, and if we Read the Modem Parameters and Firmware, then we get the error "Failed to enter command mode, unable to read version ATVR, Read parameters failed". Even if we select manually the modem to XBP24-ZB, the read will fail.

Any help would be much appreciated.

p/s - In the PC settings ->Host setup, we ticked Enable API and set the baud rate to 38400,8N1 and hardware flow control. Also we can see some program output in the Terminal window of X-CTU.


Thanks in advance..

Hi,

You have to select the COM port in the tab 'PC Settings/User Com Ports', adding the port where you have connected your Waspmote Gateway.

You also have to tick 'Use escape characters' because XBee modules are configured in API mode 2.

Best regards

Thank you for the quick reply.

Yes, we have configured the COM ports and ticked " used escape characters" too with no difference.

Just wondering if this has anything to do with the same hardware problem mentioned in the thread http://www.libelium.com/forum/viewtopic.php?f=17&t=71&start=0

Regards

Hi,

Sorry, but I guess you are trying to use Waspmote and X-CTU. The problem is that you have to use Waspmote Gateway.

Regards

Yes. You are correct. Thank you.

If we use waspgateway, Test/Query button does return the result. In this case it returns Modem Type as "XBP24-B" and firmware version "2164"

Even with the waspgateway, reading the Modem Parameters and Firmware still fails as X-CTU complains like "Unable to find configuration file for modem (firmware version 2164). Use 'Download new versions' button to check the web for newer versions". However X-CTU fails to download new versions.

Currently the X-CTU version we are using is 5.4.1.1 dated March 18,2008 downloaded from digi website.

Do you know where we can find the later versions of the X-CTU

Regards

Hi,

You must download the firmware versions from their FTP or website.

http://www.digi.com/support/productdetl.jsp?pid=3430&osvid=0&s=365&tp=1

Download the firmware version from that website and read the several documents you may find there explaining how to do the process.

Regards

Thank You Libelium team !!

We were trying to upgrade the X-CTU version !! without realizing that what we need to upgrade is the digi module software ;)

After upgrading the digi module firmware, it works fine and shows all the values

Great support. We appreciate it

Regards

Hi,

When we try to change the digi module from a router API to an end device API, the XCTU program hangs and write process failed.

However we try to follow the process mentioned here http://www.libelium.com/development/waspmote/tutorial0003to reset/recover with no luck. The message box shown in Figure 13 in the above link didnt appear. We tried to use the Rst button on the waspgateway as explained with no difference.

The Test/Query continue to give
"Communication with Modem" OK
"Modem Type"=Name unknown (ID=429496724866984)
"Modem firmware version= "

Do you know how to reset the digi module back to factory settings or default ?

Regards

After changing the firmware, have you tried at 9600bps and API mode 1?

Although the process seems to fail, sometimes it is not true, the process has been completed but the error message appears. So please, try with 9600bps and if it doesn't work, change to AP=1.

Regards

Thank you for the quick response

We tried with settings you mentioned. The XCTU still gives modem type as unknown and firmware version nothing. We untick "use escape characters" and "enable API" and use 9600. If we dont enable API, we get "unable to communicate with modem" message

When we reset we can see 7E 00 02 8A 00 75 in the terminal window in red which we believe corresponds to Modem Status API packet frame type and its for hardware reset.

Is there any other way to bring the module back to factory state.

Regards