4 years, 5 months ago.

Getting Error

Im setting up a zigbee module on a app board with a lpc1768. But it does not work. Keep getting error no matter want demo I load into the mbed. This is the at command demo:

mbed Digi International Inc., XBeeLib v1.0.0

Reset Timeout

Frame type: 88, id: 06, timeout

software_reset failed!

Reset Timeout

Frame type: 88, id: 07, timeout

software_reset failed!

Reset Timeout

Frame type: 88, id: 08, timeout

software_reset failed!

Frame type: 88, id: 09, timeout

ADDR16: UNKNOWN

Radio protocol does not match, needed a 2 got a 0

Assertion failed: radioProtocol == Raw_802_15_4, file /src/XBeeLib/XBee802/XBee802.cpp, line 52

Question relating to:

Digi's development team! Digi International and Etherios provide the industry’s broadest range of wireless products, a cloud computing platform tailored for devices, and development services to help customers get to …

4 Answers

2 years, 6 months ago.

maybe you are using S2C XBee modules. Unfortunately they do not work with this library. Please check the updated library by Lorenzo Maiorfi. And even with this updated library I still obtain timeout errors when using the "send" program.

4 years, 5 months ago.

It seems that your hardware reset function failed. I guess you are calling to the constructor (XBeeZB) passing a third argument that establish which is the physical pin that the mbed processor will use to reset the XBee. It seems that that pin is not correct. You have to either configure that pin correctly or pass a NC to the constructor so software reset is used instead of hardware reset.

4 years, 5 months ago.

I can reproduce this error when either RX or TX pin are disconnected. Check if there is any data being transferred between the modules with an oscilloscope. If there is no data, check your wiring or change to another USART port. Also, I recommend wiring the reset signal, software reset doesn't work very well.

4 years, 5 months ago.

Gert,

Some versions of the App Board had the TX and RX pins switched, please check the errata and your version number to see if this applies to your piece of kit.