# Unknow Modem type problem..and API enable **URL:** \ **Category:** XCTU\ **Created:** [January 13, 2009, 5:49am UTC](https://forums.digi.com/t/unknow-modem-type-problem-and-api-enable/3080 "2009-01-13T05:49:49Z")\ **Posts on this page:** 17\ **Page:** 1
**Author:** ![leoren\_tm](https://avatars.discourse-cdn.com/v4/letter/l/13edae/32.png) [@leoren\_tm](https://forums.digi.com/u/leoren_tm)\ **Post date:** [January 13, 2009, 5:49am UTC](https://forums.digi.com/t/unknow-modem-type-problem-and-api-enable/3080/1 "2009-01-13T05:49:49Z")
i run some test by sending and receiving data from XCTU to a standalone MCU-xbee, and it is successful. then suddenly the Xbee at the XCTU stop working, i try reading it but it says unable to connect. then i tried checking the enable api at PC-setting, then it was able to read trough test/query button and the result shows: Communication with modem…OK Modem type=Name unknown(ID=429496724891940) Modem firmware version= also i tried restore button and result to:(API enable) resetting AT Commands… Programmed Non-AT Settable parameters Restore Defaults…complete then when i write result shows:(API enable) Getting modem type…OK programming modem…Lost communication with modem write parameters…failed it cannot connect when its not on API enable, and also on the restore button sometimes the Update Summary keeps popping, and cant close it. please suggest some ways to solve the problem, i think i the non-volatile memory is corrupted,and then unable to enter command mode, i also tried “Always update firmware” i uses a series 2, with ZB firmware(not pro) ---
**Author:** ![leoren\_tm](https://avatars.discourse-cdn.com/v4/letter/l/13edae/32.png) [@leoren\_tm](https://forums.digi.com/u/leoren_tm)\ **Post date:** [January 14, 2009, 1:26am UTC](https://forums.digi.com/t/unknow-modem-type-problem-and-api-enable/3080/2 "2009-01-14T01:26:17Z")
problem solve!!!thanks to DIGI ---
**Author:** ![jc56](https://avatars.discourse-cdn.com/v4/letter/j/35a633/32.png) [@jc56](https://forums.digi.com/u/jc56)\ **Post date:** [February 23, 2009, 4:24pm UTC](https://forums.digi.com/t/unknow-modem-type-problem-and-api-enable/3080/3 "2009-02-23T16:24:08Z")
Hi, I have the same problem with serie 1: I test the solution with RS232 but it doesn’t work ! Getting modem type…OK Programming modem…Detected baud rate difference. Make sure PC and modem baud rate is set correctly Lost communication with modem Write Parameters…Failed thanks for response ---
**Author:** ![fordcf2000](https://avatars.discourse-cdn.com/v4/letter/f/82dd89/32.png) [@fordcf2000](https://forums.digi.com/u/fordcf2000)\ **Post date:** [January 14, 2009, 2:13am UTC](https://forums.digi.com/t/unknow-modem-type-problem-and-api-enable/3080/4 "2009-01-14T02:13:55Z")
If possible please post what you had to do to correct your problem. Others have encounterd the same problem and will also help other individuals in the future. ---
**Author:** ![leoren\_tm](https://avatars.discourse-cdn.com/v4/letter/l/13edae/32.png) [@leoren\_tm](https://forums.digi.com/u/leoren_tm)\ **Post date:** [January 14, 2009, 9:36am UTC](https://forums.digi.com/t/unknow-modem-type-problem-and-api-enable/3080/5 "2009-01-14T09:36:11Z")
i think i was in programming mode, then the module was disconnected(the case), then the non-volatile firmware was corrupted. one solution that was suggested by digi, is that. unplug the power from your RS232 board, set your XCTU to the right settings, set the firmware to default, then write the firmware(POWER UNPLUG source would be the RS232), then the XCTU will response, with some info. then press reset button, plug the power, then let go of the reset button, then the info will disappear and hopefully it will program the xbee…(did many trials before it was completely program) and also if info occur on the programming part, just reset the xbee. i hope it is clear. ---
**Author:** ![fordcf2000](https://avatars.discourse-cdn.com/v4/letter/f/82dd89/32.png) [@fordcf2000](https://forums.digi.com/u/fordcf2000)\ **Post date:** [January 14, 2009, 1:56pm UTC](https://forums.digi.com/t/unknow-modem-type-problem-and-api-enable/3080/6 "2009-01-14T13:56:58Z")
Thanks for the response and this is a good reference for others. ---
**Author:** ![zdavkeos](https://avatars.discourse-cdn.com/v4/letter/z/ea666f/32.png) [@zdavkeos](https://forums.digi.com/u/zdavkeos)\ **Post date:** [January 27, 2009, 2:07am UTC](https://forums.digi.com/t/unknow-modem-type-problem-and-api-enable/3080/7 "2009-01-27T02:07:39Z")
I seem to be having the same problem. I attempted to flash my Xbee2 OEM module with the ZNET 2.5 ROUTER/END DEVICE ANALOG I/O. It seemed to go fine, bet after resetting and trying to identify the device with xctu (with all the possible api settings) all I get as a response is the same error: Communication OK, Name unknown id=429496724800. I tried to do what you said, with all the plugging and unplugging, but I use a ftdi usb to serial module, and I was not sure where to connect/disconnect the power from. Any help would be much appreciated. ---
**Author:** ![leoren\_tm](https://avatars.discourse-cdn.com/v4/letter/l/13edae/32.png) [@leoren\_tm](https://forums.digi.com/u/leoren_tm)\ **Post date:** [January 27, 2009, 6:29am UTC](https://forums.digi.com/t/unknow-modem-type-problem-and-api-enable/3080/8 "2009-01-27T06:29:36Z")
i think you will have some problem on that 😃 if you have serial port, try building a circuit to connect your xbee module using an inverter directly to your PC. [http://www.faludi.com/itp\_coursework/meshnetworking/XBee/XBee\_firmware\_upgrade.html](http://www.faludi.com/itp_coursework/meshnetworking/XBee/XBee_firmware_upgrade.html) ---
**Author:** ![leoren\_tm](https://avatars.discourse-cdn.com/v4/letter/l/13edae/32.png) [@leoren\_tm](https://forums.digi.com/u/leoren_tm)\ **Post date:** [January 27, 2009, 6:31am UTC](https://forums.digi.com/t/unknow-modem-type-problem-and-api-enable/3080/9 "2009-01-27T06:31:12Z")
oh i forgot…add some reset button ---
**Author:** ![Rocker1446](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.digi.com/rocker1446/32/21_2.png) [@Rocker1446](https://forums.digi.com/u/Rocker1446)\ **Post date:** [February 10, 2009, 3:52pm UTC](https://forums.digi.com/t/unknow-modem-type-problem-and-api-enable/3080/10 "2009-02-10T15:52:23Z")
It is possible when using the USB board. You just have to go about it in a different manner. 1. Take the module out of the interface board. 2. Connect the interface board to the computer. 3. Open X-CTU 4. Go to “Modem Configuration” 5. Put a check in the “Always update firmware” box 6. Select proper modem from drop down menu, 7. Select proper function set and firmware version from drop down menus. 8. Click on the “Write” button. After a few seconds of trying to read the modem, you will get an Info box that says Action Needed. At this point, CAREFULLY insert the module into the interface board. 9. You may get the info box again a short while after, just use the reset button on the interface board. This should get you back up and running. ---
**Author:** ![zdavkeos](https://avatars.discourse-cdn.com/v4/letter/z/ea666f/32.png) [@zdavkeos](https://forums.digi.com/u/zdavkeos)\ **Post date:** [February 10, 2009, 1:34am UTC](https://forums.digi.com/t/unknow-modem-type-problem-and-api-enable/3080/11 "2009-02-10T01:34:55Z")
Ok, after building a few different serial circuits I still cannot get the module to start talking. I never get the window that says to restart the module, X-ctu just gives up and says it lost communication with the modem. So unless there is some way to clear the flash or a factory reset, I think it is done for. Thanks for your your help. ---
**Author:** ![zdavkeos](https://avatars.discourse-cdn.com/v4/letter/z/ea666f/32.png) [@zdavkeos](https://forums.digi.com/u/zdavkeos)\ **Post date:** [February 10, 2009, 5:56pm UTC](https://forums.digi.com/t/unknow-modem-type-problem-and-api-enable/3080/12 "2009-02-10T17:56:45Z")
Thanks for the reply. I followed your well written steps, and everything was going great until step 9. Instead of writing new firmware or something, X-ctu informs me that that it detected a baud rate change and that communication was lost. I tried the same procedure with all the possible rates, but none worked. I even tried some of the more common parity and flow control settings. I’m worried that if I keep doing this I am going to bend some pins. ---
**Author:** ![poesi1](https://avatars.discourse-cdn.com/v4/letter/p/aca169/32.png) [@poesi1](https://forums.digi.com/u/poesi1)\ **Post date:** [April 19, 2009, 10:31pm UTC](https://forums.digi.com/t/unknow-modem-type-problem-and-api-enable/3080/13 "2009-04-19T22:31:52Z")
Gracias Rocker1446 …desde Paraguay…funcionó perfecto luego de realizar los 9 pasos!!! Thanks… ---
**Author:** ![tobrew](https://avatars.discourse-cdn.com/v4/letter/t/6f9a4e/32.png) [@tobrew](https://forums.digi.com/u/tobrew)\ **Post date:** [June 7, 2009, 4:19am UTC](https://forums.digi.com/t/unknow-modem-type-problem-and-api-enable/3080/14 "2009-06-07T04:19:00Z")
This solved my problem. I had to do it a couple of times but it worked great. ---
**Author:** ![fordcf2000](https://avatars.discourse-cdn.com/v4/letter/f/82dd89/32.png) [@fordcf2000](https://forums.digi.com/u/fordcf2000)\ **Post date:** [February 10, 2009, 6:28pm UTC](https://forums.digi.com/t/unknow-modem-type-problem-and-api-enable/3080/15 "2009-02-10T18:28:17Z")
Try sending +++ to the module in the terminal window at 9600 baud 8-n-1 and see if it will respond with OK. If it does send ATRE to restore the module. I have better luck restoring the module this way than with the restore button in X-CTU. ---
**Author:** ![leoren\_tm](https://avatars.discourse-cdn.com/v4/letter/l/13edae/32.png) [@leoren\_tm](https://forums.digi.com/u/leoren_tm)\ **Post date:** [March 5, 2009, 6:05am UTC](https://forums.digi.com/t/unknow-modem-type-problem-and-api-enable/3080/16 "2009-03-05T06:05:51Z")
if you have same problem…try building the circuit…it will just use a inverter…then follow the instruction. i did that for many times. ---
**Author:** ![zdavkeos](https://avatars.discourse-cdn.com/v4/letter/z/ea666f/32.png) [@zdavkeos](https://forums.digi.com/u/zdavkeos)\ **Post date:** [May 20, 2009, 8:53pm UTC](https://forums.digi.com/t/unknow-modem-type-problem-and-api-enable/3080/17 "2009-05-20T20:53:45Z")
So, ok a lot of time has passed, but I managed to get mine working again! What the problem was, was that I had ‘use api mode’ checked in the configuration. With this unchecked, the modem programmed by just forcing an install of xb24-zb router api firmware.