# XBee Wi-Fi: XCTU - "Error writing AT parameter \> Port configuration not valid **URL:** \ **Category:** XBee & XBee Gateway\ **Tags:** xbee-wifi, xctu\ **Created:** [November 29, 2016, 3:49pm UTC](https://forums.digi.com/t/xbee-wi-fi-xctu-error-writing-at-parameter-port-configuration-not-valid/17696 "2016-11-29T15:49:55Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![jameswhip24](https://avatars.discourse-cdn.com/v4/letter/j/7ea924/32.png) [@jameswhip24](https://forums.digi.com/u/jameswhip24)\ **Post date:** [November 29, 2016, 3:49pm UTC](https://forums.digi.com/t/xbee-wi-fi-xctu-error-writing-at-parameter-port-configuration-not-valid/17696/1 "2016-11-29T15:49:55Z")
I’ve been working on a project using an XBee Wi-Fi module in API Mode and using UART via the USB XBee Explorer board to connect to my computer. Yesterday, I changed the baud rate from 230400 to 460800 attempting to speed up my transmission rate. After the parameter was written, XCTU displayed an error message stating: “Error writing BD parameter \> Port configuration not valid.” The module has now become completely bricked. I tried utilized the Recovery mode, but it keeps saying there is no active bootloader. When I connect the device to my computer, it is recognized by XCTU, but this error is thrown any time I attempt to read or write any parameters from the module. I thought it might be that the baud rate was too high for the FT231x chip on the Explorer board, but the datasheet says it can handle speeds up to 3 Mbaud. Has anyone experienced this or have a potential fix? ---
**Author:** ![DystopianFerret](https://avatars.discourse-cdn.com/v4/letter/d/71e660/32.png) [@DystopianFerret](https://forums.digi.com/u/DystopianFerret)\ **Post date:** [November 29, 2016, 5:37pm UTC](https://forums.digi.com/t/xbee-wi-fi-xctu-error-writing-at-parameter-port-configuration-not-valid/17696/2 "2016-11-29T17:37:12Z")
Please try the legacy version of XCTU: [https://www.digi.com/products/xbee-rf-solutions/xctu-software/xctu#productsupport-utilities](https://www.digi.com/products/xbee-rf-solutions/xctu-software/xctu#productsupport-utilities) Then try the recovery procedures here: [http://knowledge.digi.com/articles/Knowledge\_Base\_Article/Recovery-procedure-for-XBees/?q=xbee+recovery&l=en\_US&fs=Search&pn=1](http://knowledge.digi.com/articles/Knowledge_Base_Article/Recovery-procedure-for-XBees/?q=xbee+recovery&l=en_US&fs=Search&pn=1) at 38400 and 115200 baud. Those are the possible baud rates of the bootloader. ---
**Author:** ![acarrou](https://avatars.discourse-cdn.com/v4/letter/a/8edcca/32.png) [@acarrou](https://forums.digi.com/u/acarrou)\ **Post date:** [December 5, 2023, 4:04am UTC](https://forums.digi.com/t/xbee-wi-fi-xctu-error-writing-at-parameter-port-configuration-not-valid/17696/3 "2023-12-05T04:04:43Z")
Did you find a fix for this? I have the exact same issue right now. ---
**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:** [December 5, 2023, 1:29pm UTC](https://forums.digi.com/t/xbee-wi-fi-xctu-error-writing-at-parameter-port-configuration-not-valid/17696/4 "2023-12-05T13:29:28Z")
How did you set the baud rate? What was the exact command used?