# XBEE PRO worked for two years, but has now UART errors

**URL:** <https://forums.digi.com/t/xbee-pro-worked-for-two-years-but-has-now-uart-errors/17272>\
**Category:** XBee & XBee Gateway\
**Tags:** point-to-point, xbee-pro\
**Created:** [August 19, 2016, 12:10pm UTC](https://forums.digi.com/t/xbee-pro-worked-for-two-years-but-has-now-uart-errors/17272 "2016-08-19T12:10:29Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nick\_Morley](https://avatars.discourse-cdn.com/v4/letter/n/8e7dd6/32.png) [@Nick\_Morley](https://forums.digi.com/u/Nick_Morley)\
**Post date:** [August 19, 2016, 12:10pm UTC](https://forums.digi.com/t/xbee-pro-worked-for-two-years-but-has-now-uart-errors/17272/1 "2016-08-19T12:10:29Z")

</div>

My XBEE worked fine and has been in the field for two years, but now the communication is intermittent at best. For simple operations like reading the serial number through ATSH and ATSL, they sometimes work, but there are often errors like a ‘"’ instead of a ‘3’ (they are one bit off in ASCII code) or sometime it is complete garbage (Z\<ÇRLM n !). Trying enough times will eventually cause the command to go through, but it is extremely flaky. Sometimes the XBEE doesn’t respond at all when testing the “+++” command. Monitoring the RX/TX pins on the oscilloscope showed that the ‘+’ made it to the XBEE, but there was no respond back to the microcontroller. Replacing the XBEE restored all communications. Did I just get a bad XBEE? Is this common? Is there a work around?

---

<div class="post-metadata">

**Author:** ![mvut](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.digi.com/mvut/32/31_2.png) [@mvut](https://forums.digi.com/u/mvut)\
**Post date:** [August 19, 2016, 1:01pm UTC](https://forums.digi.com/t/xbee-pro-worked-for-two-years-but-has-now-uart-errors/17272/2 "2016-08-19T13:01:46Z")

</div>

What exactly is the XBee module mounted to? Is it connected direct to a micro processor? If so, what voltage level is that processor running at? What is the part number of the xbee module you are working with?

---

<div class="post-metadata">

**Author:** ![Nick\_Morley](https://avatars.discourse-cdn.com/v4/letter/n/8e7dd6/32.png) [@Nick\_Morley](https://forums.digi.com/u/Nick_Morley)\
**Post date:** [August 19, 2016, 1:50pm UTC](https://forums.digi.com/t/xbee-pro-worked-for-two-years-but-has-now-uart-errors/17272/3 "2016-08-19T13:50:14Z")

</div>

It is connected directly to a PIC32MX (logic levels/VDD = 3.3V). I’m using a pair of XBP9B-DMWT-002

---

<div class="post-metadata">

**Author:** ![mvut](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.digi.com/mvut/32/31_2.png) [@mvut](https://forums.digi.com/u/mvut)\
**Post date:** [August 19, 2016, 1:54pm UTC](https://forums.digi.com/t/xbee-pro-worked-for-two-years-but-has-now-uart-errors/17272/4 "2016-08-19T13:54:38Z")

</div>

Try forcing a new copy of the firmware onto the radio using XCTU.

---

<div class="post-metadata">

**Author:** ![Nick\_Morley](https://avatars.discourse-cdn.com/v4/letter/n/8e7dd6/32.png) [@Nick\_Morley](https://forums.digi.com/u/Nick_Morley)\
**Post date:** [August 19, 2016, 4:26pm UTC](https://forums.digi.com/t/xbee-pro-worked-for-two-years-but-has-now-uart-errors/17272/5 "2016-08-19T16:26:09Z")

</div>

I opened the XBEE in XCTU, but it wouldn’t let me update the firmware (unable to reset device). Comparing the config and firmware to my working XBEE, I saw that the only difference in the config was the good one had DH = 1 and PD = 7f7f while the bad one had DH = 0 and PD = 7FFF. Changing those values on the bad XBEE to match the good XBEE locked me out of the device. I can’t get a response over AT commands and XCTU fails to connect

---

<div class="post-metadata">

**Author:** ![mvut](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.digi.com/mvut/32/31_2.png) [@mvut](https://forums.digi.com/u/mvut)\
**Post date:** [August 19, 2016, 4:27pm UTC](https://forums.digi.com/t/xbee-pro-worked-for-two-years-but-has-now-uart-errors/17272/6 "2016-08-19T16:27:47Z")

</div>

Try communicating over the air with the API function and remote AT commands. If that does not work, time to replace it.

---

<div class="post-metadata">

**Author:** ![Nick\_Morley](https://avatars.discourse-cdn.com/v4/letter/n/8e7dd6/32.png) [@Nick\_Morley](https://forums.digi.com/u/Nick_Morley)\
**Post date:** [August 19, 2016, 8:22pm UTC](https://forums.digi.com/t/xbee-pro-worked-for-two-years-but-has-now-uart-errors/17272/7 "2016-08-19T20:22:11Z")

</div>

How do I enable the API function to connect remotely?

---

<div class="post-metadata">

**Author:** ![mvut](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.digi.com/mvut/32/31_2.png) [@mvut](https://forums.digi.com/u/mvut)\
**Post date:** [August 22, 2016, 9:58am UTC](https://forums.digi.com/t/xbee-pro-worked-for-two-years-but-has-now-uart-errors/17272/8 "2016-08-22T09:58:35Z")

</div>

That depends on which XBee module you are working with. Some versions you have to change the firmware on a node to the API version (S2 and S2B), others it is nothing more than enabling the ATAP command to a value of 1. Then properly formatting and sending the API frame.

---

<div class="post-metadata">

**Author:** ![Nick\_Morley](https://avatars.discourse-cdn.com/v4/letter/n/8e7dd6/32.png) [@Nick\_Morley](https://forums.digi.com/u/Nick_Morley)\
**Post date:** [August 22, 2016, 8:31pm UTC](https://forums.digi.com/t/xbee-pro-worked-for-two-years-but-has-now-uart-errors/17272/9 "2016-08-22T20:31:12Z")

</div>

I couldn’t get the XBEE to respond to any more AT commands so I used XCTU to recover the firmware and it fixed the issue. Thanks for your help!

---

<div class="post-metadata">

**Author:** ![ChetManly](https://avatars.discourse-cdn.com/v4/letter/c/ce7236/32.png) [@ChetManly](https://forums.digi.com/u/ChetManly)\
**Post date:** [October 13, 2016, 2:30pm UTC](https://forums.digi.com/t/xbee-pro-worked-for-two-years-but-has-now-uart-errors/17272/10 "2016-10-13T14:30:32Z")

</div>

What firmware were you using? I have had similar problems with products in the field for 2 years (10ec firmware) and all the sudden I am having connection issues on sites with high wifi and audio streaming traffic.

Let me know what you found.
