I have two Series 1 XBees that won't be in transparent mode because they are in AT command mode when I'm not in X-CTU. I had asked for help elsewhere and no one had the answer except telling me about flow control.

The XBees had been configured properly with the MY and DL settings. I'm thinking maybe I should shorten the timeout so they supposedly get out of AT command mode but they both stay in AT command mode. The only time I can get the two Series 1 XBees to talk is under X-CTU. I need the two Series 1 XBees to automatically be in transparent mode when powered on.


I meant to answer this question months ago, apologies...

AT mode is the same as Transparent mode. The different modes (AT or API) is determined by the type of firmware that your XBees have on them. By default1, they should have the AT firmware.

From XBee and ZigBee basic concepts - Radio module operating modes (you can ignore the API modes):

Radio module operating modes

The operating mode of an XBee radio module establishes the way a user or any microcontroller attached to the XBee communicates with the module through the Universal Asynchronous Receiver/Transmitter (UART) or serial interface.

Depending on the firmware and its configuration, the radio modules can work in three different operating modes:

  • AT (transparent) operating mode
  • API operating mode
  • API escaped operating mode

In some cases, the operating mode of a radio module is established by the firmware version, which determines whether the operating mode is AT or API, and the AP setting of the firmware, which determines if the API mode is escaped (AP=2) or not (AP=1).

In other cases, the operating mode is only determined by the AP setting, which allows you for configure the mode to be AT (AP=0), API (AP=1) or API escaped (AP=2).

Now, where you are getting confused is that within Transparent mode, there is the AT command mode, which can be accessed by typing +++. This is where you say that you are when the XBees are connected to X-CTU. From XBee and ZigBee basic concepts - Application Transparent (AT) operating mode:

Application Transparent (AT) operating mode

In Application Transparent (AT) or transparent operating mode, all serial data received by the radio module is queued up for RF transmission. When RF data is received by the module, the data is sent out though the serial interface.

To configure an XBee module operating in AT, put it in AT Command mode to send the configuration commands.

AT Command mode

When the radio module is working in AT operating mode, settings are configured using the AT Command mode interface.

To enter AT command mode, you must send the 3-character command sequence through the serial interface of the radio module , usually +++, within one second. Once the AT command mode has been established, the module sends the reply OK\r, the command mode timer is started, and the radio module can receive AT commands.

So, in short, your XBees are in Transparent mode. Unless you have uploaded the API firmware on to them, in which case use X-CTU to upload them with the AT version of the firmware.

You may also find this useful, although, the author himself is confused by thinking that there are three modes:

  • Transparent;
  • AT, and;
  • API.

While there are indeed three modes, as I have already clarified, Transparent and AT are one and the same, and the other two modes are:

  • API and;
  • API escaped (also known as API mode 2 (or atap2)).

Nevertheless, the points he makes may still help. From XBEE Series 1

An Xbee module has three communication modes: Transparent mode, Command mode & API mode.

By default, all XBee modules start up in transparent mode. All data received from the DIN pin is transmitted, and when RF data is being received, it is sent out on the DOUT pin. A pair of XBee modules can act Wireless in this mode.

Command mode is where you can configure XBee using AT commands through any Terminal software like TeraTerm or CoolTerm. Built in terminal of XCTU can also be used. To enter Command mode type in 3 consecutive characters +++ and wait a second. Once the XBee enters command mode, it will answer with OK. While in command mode you can change baud rate, PANID, Destination address, etc. If you are not typing anything for 10 seconds the module will return to Transparent mode, or you can issue the ATCN command to exit.

API (Application Programming Interface) mode is a frame-based method for sending and receiving data to and from an XBee. API MODE is powerful & complicated to setup.It is used to send messages to constantly changing targets (other XBee modules).

API mode has some special abilities to change parameters without entering command mode & Receive packet delivery confirmation on every transmitted packet.

You may also find the answer to the question How does coordinator XBee receive data from router? useful (although that answer refers to Series 2 not Series 1 XBee).

1 The XBees from Digi are shipped with AT mode. However, the XBees from Libelium are shipped in API mode. From the section API mode vs AT command mode on Getting started with the XBee 802.15.4 (serie 1) communication module [C. Pham, LIUPPA laboratory, University of Pau, France. http://web.univ-pau.fr/~cpham]

By default, the Digi XBee is in AT command mode (also called transparent mode) while the one shipped by Libelium is in API mode 2 (atap2) where some characters are escaped using the escape character 0x7D. The Libelium API assumes that the XBee module is in API mode 2 anyway.

  • $\begingroup$ Sadly, this question is now too old to migrate, but thanks for the flag. $\endgroup$ – Mark Booth Mar 14 '16 at 1:34

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.