Modems/xbee - Revision history

Openuas: /* XBee Pro DigiMesh / 802.15.4 ("Series 1") */

2025-09-16T12:31:22Z

XBee Pro DigiMesh / 802.15.4 ("Series 1")

← Older revision		Revision as of 06:31, 16 September 2025
Line 203:		Line 203:
	<br/>		<br/>

	== XBee Pro ~~DigiMesh /~~ 802.15.4 ~~("Series 1")~~ ==		== XBee S1 (Pro) with 802.15.4 Firmware ==

	=== Flashing the airborne module ===		=== Flashing the airborne module ===

	# Connect your XBee, start X-CTU, click READ		# Connect your XBee, start X-CTU, click READ
	# Leave the function set on '''XBEE PRO 802.15.4'''.		# Leave the function set on '''XBEE PRO 802.15.4'''.
Line 222:		Line 223:
	# Then write the firmware to the module.		# Then write the firmware to the module.

	(~~Tested~~ on ~~XBP24 Firmwareversion 10E6~~)		Successfully tested with XBP24 Firmware version '''10EF''' and Paparazzi-link (PPRZLink)

			== XBee S1 (Pro) with DigiMesh Firmware ==

			Using Digimesh, Paparazzi based UAS inter-communicate via generate a real mesh network, so all aircraft can reach all other aircraft even wen the GCS cannot be reached.
			Also the GCS can reach all aircraft even if not in range directly.

			Advised for a XBee S1 (Pro) module to use Firmware version '''8073''' - XBP24_DM (XBee Pro 2.4 Ghz on DigiMesh )

			This is firmware is the latest, and also the only version, we tested and works well with multiple airborne vehicles.
			The firmware update procedure is almost the same as described above. The settings can be the default of the Firmware.

	== XBee Pro 868 MHZ ==		== XBee Pro 868 MHZ ==

IHaveADrone: ttttttypo

2017-02-08T17:48:51Z

ttttttypo

← Older revision		Revision as of 11:48, 8 February 2017
Line 43:		Line 43:
	Basic approach:		Basic approach:
	# Connect your XBee to your PC. There are several vendors of [[Modems#GCS_Adaptation\|USB boards]].		# Connect your XBee to your PC. There are several vendors of [[Modems#GCS_Adaptation\|USB boards]].
	# Start the X-CTU ~~programm~~ and go to the modem configuration.		# Start the X-CTU program and go to the modem configuration.
	# Click on READ		# Click on READ
	# Select the appropriate function set with AT command set.		# Select the appropriate function set with AT command set.

IHaveADrone: spelling

2016-05-10T16:46:00Z

spelling

← Older revision		Revision as of 10:46, 10 May 2016
Line 32:		Line 32:
	* Click "Test/Query" button. If you get some modem information (like serial, etc.) after a little time, then you have modem link established.		* Click "Test/Query" button. If you get some modem information (like serial, etc.) after a little time, then you have modem link established.

	If X-CTU complains on com port connectivity, try adding ~~theese~~ strings to ~/.wine/system.reg		If X-CTU complains on com port connectivity, try adding these strings to ~/.wine/system.reg
	[hardware\\DEVICEMAP\\SERIALCOMM]		[hardware\\DEVICEMAP\\SERIALCOMM]
	"COM1"="COM1"		"COM1"="COM1"

	If your X-CTU does not update its firmware ~~correctely~~ from the web, follow the steps described in the chapter "Manually Update the X-CTU firmware files" of [http://wiki.openpilot.org/display/Doc/Configure+Xbee+via+Linux this page].		If your X-CTU does not update its firmware correctly from the web, follow the steps described in the chapter "Manually Update the X-CTU firmware files" of [http://wiki.openpilot.org/display/Doc/Configure+Xbee+via+Linux this page].

	=== Configuring XBee AT mode using X-CTU ===		=== Configuring XBee AT mode using X-CTU ===
Line 246:		Line 246:
	== XBee 868LF ==		== XBee 868LF ==

	These ~~relativly~~ new modems use the whole spectrum allowed in your country to avoid Duty Cycle restrictions.		These relatively new modems use the whole spectrum allowed in your country to avoid Duty Cycle restrictions.

	== XBee Pro XSC (900MHZ) ==		== XBee Pro XSC (900MHZ) ==

Flixr: X-CTU 6 is available natively for linux

2016-05-04T18:52:15Z

X-CTU 6 is available natively for linux

← Older revision		Revision as of 12:52, 4 May 2016
Line 7:		Line 7:

	=== Installation of X-CTU ===		=== Installation of X-CTU ===
	The simplest way to configure the XBee modems is to use the [http://www.digi.com/support/productdetail?pid=3352 X-CTU] software from Digi. It runs under MacOS X, Windows~~, under Wine~~ and ~~since version~~ 6 ~~also natively~~ under Linux.		The simplest way to configure the XBee modems is to use the [http://www.digi.com/support/productdetail?pid=3352 X-CTU] software from Digi. It runs natively under MacOS X, Windows and Linux.
			To use versions before X-CTU 6 under Linux, use Wine.

	==== Installation using Wine ====		==== Installation using Wine ====
			'''X-CTU versions 6 and up are available natively for Linux''', so using Wine is only needed for older versions.

	Under Wine make sure you have the USB serial link connecting to XBee mapped to a com port (please consult [[Installation/Linux/udev \| paparazzi linux device naming]]):		Under Wine make sure you have the USB serial link connecting to XBee mapped to a com port (please consult [[Installation/Linux/udev \| paparazzi linux device naming]]):

Cdewagter: fast xbee

2015-12-21T15:44:12Z

fast xbee

← Older revision		Revision as of 09:44, 21 December 2015
Line 75:		Line 75:

	'''Quick, I'm in a rush''':		'''Quick, I'm in a rush''':
	* sudo screen /dev/ttyUSB0 9600		$ sudo screen /dev/ttyUSB0 9600
	* +++		+++
	* ATBD6<enter>		ATBD6<enter>
	* ATAP1<enter>		ATAP1<enter>
	* ATWR<enter>		ATWR<enter>

Cdewagter: quick xbee start

2015-12-21T15:42:37Z

quick xbee start

← Older revision		Revision as of 09:42, 21 December 2015
Line 73:		Line 73:
	\|7\|\|115200\|\|		\|7\|\|115200\|\|
	\|}		\|}

			'''Quick, I'm in a rush''':
			* sudo screen /dev/ttyUSB0 9600
			* +++
			* ATBD6<enter>
			* ATAP1<enter>
			* ATWR<enter>


	'''Minicom Instructions''':		'''Minicom Instructions''':

Cdewagter at 15:24, 21 December 2015

2015-12-21T15:24:46Z

← Older revision		Revision as of 09:24, 21 December 2015
Line 85:		Line 85:
	** you get the current baudrate code: '3'		** you get the current baudrate code: '3'
	* To set another baudrate select one from the above table and type "ATBD <baud code><enter>":		* To set another baudrate select one from the above table and type "ATBD <baud code><enter>":
			* Type "ATAP 0 or 1 for API mode or not<enter>"
	* To store the new baudrate in the rom type "ATWR<enter>"		* To store the new baudrate in the rom type "ATWR<enter>"
	* Now you can close minicom		* Now you can close minicom

Simmis: Pairing makes the the communications error disappear.

2015-10-14T19:46:01Z

Pairing makes the the communications error disappear.

← Older revision		Revision as of 13:46, 14 October 2015
Line 136:		Line 136:
	=== Pairing your Modems ===		=== Pairing your Modems ===

	For maximum performance you can pair the ground modem to the airborne modem. Set the "DH - Destination Address High" and "DL - Destination Address Low" to the unique serial number "SH - Serial Number High" and "SL - Serial Number Low" of the other modem. Do so both on the ground modem and on the airborne modem. Failing to properly pair your modems will likely result in poor throughput and data loss between your airframe and your ground control station.		For maximum performance you can pair the ground modem to the airborne modem. Set the "DH - Destination Address High" and "DL - Destination Address Low" to the unique serial number "SH - Serial Number High" and "SL - Serial Number Low" of the other modem. Do so both on the ground modem and on the airborne modem. Failing to properly pair your modems will likely result in poor throughput and data loss between your airframe and your ground control station. If this is the case you may see errors on the Paparazzi Center console like <tt>Failure("Pprz.values_of_payload, wrong argument: 00 08 ")</tt> or <tt>Failure("Pprz.values_of_payload, too many bytes in message PONG: 00 03 02 2a 00 00 00 00 00 00 00 00 00 00 00 00 ")</tt>. Pairing does help and the error messages will disappear.

	=== Reviving a non-responding Xbee Pro ===		=== Reviving a non-responding Xbee Pro ===

Simmis: /* Installation of X-CTU */

2015-08-30T17:45:52Z

Installation of X-CTU

← Older revision		Revision as of 11:45, 30 August 2015
Line 7:		Line 7:

	=== Installation of X-CTU ===		=== Installation of X-CTU ===
	The simplest way to configure the XBee modems is to use the [http://www.digi.com/support/productdetail?pid=3352 X-CTU] software from Digi. It runs under MacOS X, Windows or under Wine.		The simplest way to configure the XBee modems is to use the [http://www.digi.com/support/productdetail?pid=3352 X-CTU] software from Digi. It runs under MacOS X, Windows, under Wine and since version 6 also natively under Linux.

			==== Installation using Wine ====
	Under Wine make sure you have the USB serial link connecting to XBee mapped to a com port (please consult [[Installation/Linux/udev \| paparazzi linux device naming]]):		Under Wine make sure you have the USB serial link connecting to XBee mapped to a com port (please consult [[Installation/Linux/udev \| paparazzi linux device naming]]):

Openuas at 14:37, 10 December 2014

2014-12-10T14:37:43Z

← Older revision		Revision as of 08:37, 10 December 2014
Line 230:		Line 230:

	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.		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.

			== XBee 868LF ==

			These relativly new modems use the whole spectrum allowed in your country to avoid Duty Cycle restrictions.

	== XBee Pro XSC (900MHZ) ==		== XBee Pro XSC (900MHZ) ==