Can someone please point me in the right direction.
This has happened with 2 - XBP9B-XCWT-001 modems and 1 - XB24-AWI-001 modem.
I have the Xbee USB Explorer board (with the RSSI resistor removed since the S3B needs that) and I’m connecting to X-CTU ver. 5.2.8.6. I tested the modems no problem at 9600baud, I read the firmware no problem, then I attempted to write firmware and all 3 modems failed at this. After that point the Xbees will not respond to anything. The closest this I get to comms with the Xbees is at 38400baud and the only this that is returned is the letter ‘U’.
I’ve tried writing firmware while unplugged then plugging in and releasing RST.
I’ve tried every baud, and alot of AT commands on everyone.
I’ve reinstalled X-CTU and punched an old dell.
Since I’ve been away from Xbee stuff for some time I feel like I’m making a really stupid mistake.
Can anyone point me in the right direction for a solution.
I’m getting sh1tf@ced now and blowing off some stress. Don’t expect a response from me until tomorrow aft.
The scenario is not known, but if youre scooting around the carpet in cotton socks (especially the ones with separate toes) then after some scooting, touching the solder beads (in particular the ones connected to the ICs) , you might have an issue…unless of course, you know that ancient mongolian shaman trance verse that negates the effects of lightning strikes
(I cant remember it anymore, but know someone who might still)
A possible scenario might be you have that killer rootkit bug similar to stuxnet the KGB deployed this year to break into CIA networks…
But of course, we need to know stuff like exact (or close) point of the firmware load where it fails, the type or content of the firmware load, and if the hardware used to program the peripherals (PC+ cables, etc) doesnt have a serious electrical fault…can it write firmware to any other similar type devices successfully using the exact setup?
Modem
XBP9B-XC
Function Set
XBEE-PRO XSC (S3B) 9600
Version
300C
I get the exact same results with my series one modem I had from college as well. All of them did this as soon as I attempted to write firmware. The failure seems to happen when attempting to enter command mode.
I’m using the sparkfun usb explorer board with the rssi led resistor removed along with a matching usb cable.
No, I was not wearing my snuggy while zapping my roommate with an ESD gun while working (my excessive drinking began… after my fun with the XBEES).
Let me know if you need anything else to help me.
Again, thanks for your help in this regards, if you can help.
[*EDIT]Apparently not again…
Yea… so I’m defiantly a donkey.
Digi tech support saved me this time.
Hi John
Try to recover your modules using our recovery guide that can be found here:
http://www.digi.com/support/kbase/kbase … tl?id=3402
For most of the steps, you require an interface board like Digi’s XBIB-U-DEV that has DTR and RTS flow control lines enable.
Thanks
Ankur
Tech Support @ Digi
I neglected ALL of the proper com port settings for my driver. http://www.digi.com/support/kbase/kbase … tl?id=3418
I got to the second bullet in the recovery guide then it worked. So simple, once you know.
Working at Siemens a while back, (you know that big company chocked full of freeking brilliant germans)
one of the most revered statements of wisdom was - " The greatest problem solver, is pure determination…"
Sometimes someone determined and not too lazy can be stimulated to achieve solution themselves by just providing something that serves as a catalyst, and not a direct assist itself…
Bravo mate!