# Have to reflash S3B firmware every time before connecting to xctu

**URL:** <https://forums.digi.com/t/have-to-reflash-s3b-firmware-every-time-before-connecting-to-xctu/22992>\
**Category:** XBee & XBee Gateway\
**Tags:** xbee-900hp, s3b, xbee-pro, xctu, xsc\
**Created:** [March 14, 2022, 8:51am UTC](https://forums.digi.com/t/have-to-reflash-s3b-firmware-every-time-before-connecting-to-xctu/22992 "2022-03-14T08:51:58Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![PWN-GH](https://avatars.discourse-cdn.com/v4/letter/p/f14d63/32.png) [@PWN-GH](https://forums.digi.com/u/PWN-GH)\
**Post date:** [March 14, 2022, 8:51am UTC](https://forums.digi.com/t/have-to-reflash-s3b-firmware-every-time-before-connecting-to-xctu/22992/1 "2022-03-14T08:51:58Z")

</div>

Every time I unplug and replug the module into the computer and try to configure it via XCTU, I get module not found message and have to use the recovery tool to reflash the firmware to XSC function, then back to 10K/200K which I actually want to use. Tried using 2 sets of 3 different USB-to-serial adapter/programmers on different USB ports on 2 computers and 3 OS-es without success.  
This only happens if the modules are in XBP9B-DP 10K or XBP9P-DM 200K mode. The XBP9B-XC works perfectly fine every time.

Detailed: 2x(1 CH340G-based boards, 2 CP2102-based boards), Different usb ports, 2 laptops running Windows 10 with one running MacOS Monterey.

---

<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:** [March 14, 2022, 10:31am UTC](https://forums.digi.com/t/have-to-reflash-s3b-firmware-every-time-before-connecting-to-xctu/22992/2 "2022-03-14T10:31:32Z")

</div>

Try using a Digi Certified interface board such as an XBIB-U-DEV.