# Why is X-CTU so Flakey?

**URL:** <https://forums.digi.com/t/why-is-x-ctu-so-flakey/955>\
**Category:** XBee - Zigbee\
**Created:** [October 4, 2012, 9:21am UTC](https://forums.digi.com/t/why-is-x-ctu-so-flakey/955 "2012-10-04T09:21:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![whitneyrm](https://avatars.discourse-cdn.com/v4/letter/w/f19dbf/32.png) [@whitneyrm](https://forums.digi.com/u/whitneyrm)\
**Post date:** [October 4, 2012, 9:21am UTC](https://forums.digi.com/t/why-is-x-ctu-so-flakey/955/1 "2012-10-04T09:21:27Z")

</div>

Using latest version of X-CTU I program an XBPRO-S2B as:  
XBP24BZ7 Zigbee End Device API 29A7 and save to a .pro file. Plug it into my rig, and don’t get the expected result via a Coordinator plugged into an Arduino.

Open X-CTU and PC Setting/Test says it’s XBP24BSE 29A7 firmware - which doesn’t exist.

Read in Modem Configuration and now both the module’s SH and DH are reported as 7D33A2 and not the correct 13A200.

---

<div class="post-metadata">

**Author:** ![16ksa23](https://avatars.discourse-cdn.com/v4/letter/1/aeb1de/32.png) [@16ksa23](https://forums.digi.com/u/16ksa23)\
**Post date:** [October 4, 2012, 10:45am UTC](https://forums.digi.com/t/why-is-x-ctu-so-flakey/955/2 "2012-10-04T10:45:03Z")

</div>

Hi,

I think it is because of the DD parameter. Even I’m facing the same issue but it do not affect the module functionality.

Read in Modem Configuration and now both the module’s SH and DH are reported as 7D33A2 and not the correct 13A200

- check whether you have enabled API=2.