XBee configuration

Paparazzi supports the following modem protocols:

• Standard transparent serial (pprz) - this is compatible with all modems and can be used to connect the autopilot directly to a PC for testing without a modem.
• Digi (formerly Maxstream) API protocol (xbee) - compatible with all Digi modems including the 9XTend and Zigbee. This protocol enables hardware addressing through API mode, allowing multiple aircraft to be managed from a single ground modem.

Installation

The simples way to configure the XBee modems is to use the X-CTU software from Digi. It runs under Windows or under Wine.

Under Wine make sure you have the USB serial link connecting to XBee mapped to a com port:

sudo ln -s /dev/ttyUSB0 ~/.wine/dosdevices/com4

Configuring XBee AT mode (for pprz protocol)

This is the recommended way to start. With this firmware the modems basically act as a serial link replacement and don't do any mesh networking.
Basic approach:

1. Connect your XBee, e.g. via a USB XBee Explorer.
2. Start the X-CTU programm and go to the modem configuration.
3. Click on READ
4. Select the appropriate function set with AT command set.
5. set PAN ID, etc... depending on which XBee you use
6. Set the baudrate you want to use. 57600 is the maximum baudrate setting for bidirectional transfers to work correctly. At a higher baudrate setting, transmission can only be done in one direction.
7. Then write the firmware to the module.

XBee Pro ZB (AT command set)

This 2.4GHz modem uses ZigBee PRO Feature Set and is compatible with devices from other vendors using the ZigBee PRO Feature Set.

Flashing the airborne module

1. Connect your XBee, start X-CTU, click READ
2. Select the function set ZIGBEE END DEVICE AT (or ZIGBEE ROUTER AT).
3. Set the PAN ID to any number, must be the same as the pan id of the coordinator (Ground Station).
4. Set the Node Identifier (NI) to your aircraft name or any other appropriate name.
5. Set the baudrate you want to use. 57600 is the maximum baudrate setting for bidirectional transfers to work correctly.
6. Then write the firmware to the module.

Flashing the ground station module

1. Connect your XBee, start X-CTU, click READ
2. Select the function set ZIGBEE COORDINATOR AT.
3. Set the PAN ID to any number, must be the same as the pan id of the end device (aircraft).
4. Set the Node Identifier (NI) to PPRZ_GROUND or any other appropriate name.
5. Set the baudrate you want to use. 57600 is the maximum baudrate setting for bidirectional transfers to work correctly.
6. Then write the firmware to the module.

XBee Pro ZNet 2.5 (AT command set)

These are legacy modems and not recommended/sold by Digi anymore. It is recommended to upgrade these to XBee Pro ZB with the ZNet 2.5 to ZB Conversion Kit from Digi.
If you want to use ZNet 2.5 feature set nevertheless, here is how to configure it:

Flashing the airborne module

1. Connect your XBee, start X-CTU, click READ
2. Select the function set ZNET 2.5 ROUTER/END DEVICE AT.
3. Set the PAN ID to any number, must be the same as the pan id of the coordinator (Ground Station).
4. Set the Node Identifier (NI) to your aircraft name or any other appropriate name.
5. Set the baudrate you want to use. 57600 is the maximum baudrate setting for bidirectional transfers to work correctly.
6. Then write the firmware to the module.

Flashing the ground station module

1. Connect your XBee, start X-CTU, click READ
2. Select the function set ZNET 2.5 COORDINATOR DEVICE AT.
3. Set the Destination Address Low (DL) to FFFF.
4. Set the PAN ID to any number, must be the same as the pan id of the end device (aircraft).
5. Set the Node Identifier (NI) to PPRZ_GROUND or any other appropriate name.
6. Set the baudrate you want to use. 57600 is the maximum baudrate setting for bidirectional transfers to work correctly.
7. Then write the firmware to the module.

Reviving a non-responding Xbee Pro

To bring an apparently dead XBee Pro Series 2 back to life, do the following:

1. Connect the USB device that holds the XBee to your laptop/desktop (without the XBee connected).
2. Open X-CTU.
3. In the tab used to program the device, select the proper modem (normally you would do a READ to get the values).
4. Choose the option you want to program (i.e., "END DEVICE" or "COORDINATOR") as if you were programming it.
5. With the XBee not in the device, click "WRITE". It will hang, timeout, and bring up a dialog box.
6. Before you click OK to the dialog box, plug in the XBee module (carefully).
7. Click OK to clear the message and it should start programming automatically.

Other tutorials

See: PixHawk HowTo configure XBee

XBee Pro 868 MHZ

Getting Them Working

Even with the xbee868.xml telemetry file, XBee868s will not last over 6 minutes. There is a special 868 build flag (in slayer1.xml), and matching option for the datalink but I could not get this to work. Eventually, I got them to work for about 20 minutes, which happily is the flight endurance of a heavily overloaded GWS Formosa.

I did this using a command window, but you could use X-CTU if you are a wuss or have Windows handy.

1. Attach Xbee and start serial comm program (I use screen /dev/ttyUSB0 <baud rate, just a number, no angled brackets>, you can also use pico- or microcom)
2. Type AT and enter. You should get an OK back.
3. ATMT and enter. You should get a number—this represents the number of extra times each packet will be broadcast. We now need to change this to zero.
4. ATMT0 and enter => OK
5. ATRR and enter. This number is the number of retries that will be sent if an ACK is not received. Disabling this will also have the side effect of disabling ACKs, giving us more packets to play with.
6. ATRR0 and enter => OK
7. Type ATWR to store the new stuff in the firmware. You should get an OK.
8. Set the datalink to transparent mode both in your airframe file and on the datalink.

You may also want to drop the power level to 1mW for testing, or it won't actually work - they are just too damn powerful to talk to each other at a range of a couple of feet. I also used 1mW for flying - never lost the link, even after a mile. Didn't get round to range testing them though.

You probably want to do this to both XBees (at least I did). I personally had the baud rate at 57600 for legacy reasons, but it should work just as well at any other baud rate. Thanks to CheBuzz for this info, and for helping me work all this out at 11pm the night before EMAV09.