# Why is my XBee PRO S3B giving junk data in XCTU, even after recovery was used?

**URL:** <https://forums.digi.com/t/why-is-my-xbee-pro-s3b-giving-junk-data-in-xctu-even-after-recovery-was-used/16161>\
**Category:** XBee - 802.15.4\
**Tags:** xbee-pro-xsc-s3b, xbee-pro, xbee\
**Created:** [January 27, 2016, 4:34pm UTC](https://forums.digi.com/t/why-is-my-xbee-pro-s3b-giving-junk-data-in-xctu-even-after-recovery-was-used/16161 "2016-01-27T16:34:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jacobjackson1985](https://avatars.discourse-cdn.com/v4/letter/j/e19adc/32.png) [@jacobjackson1985](https://forums.digi.com/u/jacobjackson1985)\
**Post date:** [January 27, 2016, 4:34pm UTC](https://forums.digi.com/t/why-is-my-xbee-pro-s3b-giving-junk-data-in-xctu-even-after-recovery-was-used/16161/1 "2016-01-27T16:34:15Z")

</div>

I recently bought a pair of XBee PRO S3B modules (900Mhz, 9600 baud) and a Sparkfun Xbee dongle (USB). When I run XCTU, it finds the module easily enough, and it’s the correct module type, but when I load the settings into XCTU, they’re mostly junk data (out of range values, etc.) - even after I reset everything to factory settings and wrote the data out, when I read it back in it’s all junk again. I tried using the recovery feature to reload the firmware but the same thing keeps happening. This has happened for both modules I purchased. Did I buy faulty modules? They were bought on [Amazon.com](http://Amazon.com) - do I need to buy from another source to avoid getting bad modules? Or am I missing something? I’m using the Mac OS X version of XCTU. Please help!

---

<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:** [January 28, 2016, 10:44am UTC](https://forums.digi.com/t/why-is-my-xbee-pro-s3b-giving-junk-data-in-xctu-even-after-recovery-was-used/16161/2 "2016-01-28T10:44:34Z")

</div>

No, they are not faulty modules. What you need to do is first optimize the USB ports for low data rate devices as described at [http://knowledge.digi.com/articles/Knowledge\_Base\_Article/Optimizing-USB-to-serial-port-settings/?q=optimizing+usb+drivers&amp;l=en\_US&amp;fs=Search&amp;pn=1](http://knowledge.digi.com/articles/Knowledge_Base_Article/Optimizing-USB-to-serial-port-settings/?q=optimizing+usb+drivers&amp;l=en_US&amp;fs=Search&amp;pn=1).

Next, if you are using the XSC version of the firmware, you will need to remove one of the LED’s from the Explorer board. (Talk to Spark Fun about it).