Subsystem/telemetry - Revision history

Flixr: add some extra info on transparent_usb

2015-07-24T09:02:06Z

add some extra info on transparent_usb

@@ Line 40: / Line 40: @@
 </source>
 }}
 == Configuring The Serial Protocol ==

Flixr: syntaxhighlight

2012-03-04T23:06:39Z

syntaxhighlight

← Older revision		Revision as of 17:06, 4 March 2012
Line 9:		Line 9:
	Just specify the appropriate subsystem in your firmware section. You can currently choose between the types '''transparent''', '''transparent_usb''' and '''xbee_api'''.		Just specify the appropriate subsystem in your firmware section. You can currently choose between the types '''transparent''', '''transparent_usb''' and '''xbee_api'''.
	{{Box Code\|conf/airframes/myplane.xml\|		{{Box Code\|conf/airframes/myplane.xml\|
	<~~pre~~>		<source lang="xml">
	<firmware name="fixedwing or rotorcraft">		<firmware name="fixedwing or rotorcraft">
	...		...
	<subsystem name="telemetry" type="transparent"/>		<subsystem name="telemetry" type="transparent"/>
	</firmware>		</firmware>
	</~~pre~~>		</source>
	}}		}}

Line 30:		Line 30:
	If you use different baud rate or Uart set the according parameters, e.g.		If you use different baud rate or Uart set the according parameters, e.g.
	{{Box Code\|conf/airframes/myplane.xml\|		{{Box Code\|conf/airframes/myplane.xml\|
	<~~pre~~>		<source lang="xml">
	<firmware name="fixedwing or rotorcraft">		<firmware name="fixedwing or rotorcraft">
	...		...
Line 38:		Line 38:
	</subsystem>		</subsystem>
	</firmware>		</firmware>
	</~~pre~~>		</source>
	}}		}}

Line 48:		Line 48:

	{{Box Code\|conf/airframes/myplane.xml\|		{{Box Code\|conf/airframes/myplane.xml\|
	<~~nowiki~~>		<source lang="xml">
	<section name="MISC">		<section name="MISC">
	...		...
	<define name="XBEE_INIT" value="\"ATPL2\rATRN1\rATTT80\r\ATBD6\rATWR\r\""/>		<define name="XBEE_INIT" value="\"ATPL2\rATRN1\rATTT80\r\ATBD6\rATWR\r\""/>
	...		...
	</section></~~nowiki~~>		</section>
			</source>
	}}		}}
	The above example will program the Maxstream to API mode, 100mW power (ATPL2), 57600 baud (ATBD6), and permanently store the changes (ATWR). After flashing allow 30 seconds for the modem to store the changes, then disable the init string by adding the line <tt><define name="NO_XBEE_API_INIT" value="TRUE"/></tt> (the parameter "value" has no effect), update the baud rate as needed, and re-flash the autopilot. The modem and autopilot serial port baud rates must match each other at all times.		The above example will program the Maxstream to API mode, 100mW power (ATPL2), 57600 baud (ATBD6), and permanently store the changes (ATWR). After flashing allow 30 seconds for the modem to store the changes, then disable the init string by adding the line <tt><define name="NO_XBEE_API_INIT" value="TRUE"/></tt> (the parameter "value" has no effect), update the baud rate as needed, and re-flash the autopilot. The modem and autopilot serial port baud rates must match each other at all times.
Line 66:		Line 67:
	This is the way it is done in funjet1.xml and has been tested to work by Danstah		This is the way it is done in funjet1.xml and has been tested to work by Danstah
	{{Box Code\|conf/airframes/funjet1.xml\|		{{Box Code\|conf/airframes/funjet1.xml\|
	<~~nowiki~~>		<source lang="xml">
	<section name="MISC">		<section name="MISC">
	...		...
	<define name="XBEE_INIT" value="\"ATPL2\rATRN1\rATTT80\r\""/>		<define name="XBEE_INIT" value="\"ATPL2\rATRN1\rATTT80\r\""/>
	<!-- <define name="NO_XBEE_API_INIT" value="TRUE"/> -->		<!-- <define name="NO_XBEE_API_INIT" value="TRUE"/> -->
	...		...
	</section></~~nowiki~~>		</section>
			</source>
	}}		}}

Line 83:		Line 85:
	You can also manually write a session:		You can also manually write a session:
	{{Box Code\|conf/control_panel.xml\|		{{Box Code\|conf/control_panel.xml\|
	<~~nowiki~~>		<source lang="xml">
	<session name="USB">		<session name="USB">
	<program name="link">		<program name="link">
Line 92:		Line 94:
	...		...
	</session>		</session>
	</~~nowiki~~>		</source>
	}}		}}

Flixr at 22:06, 4 March 2012

2012-03-04T22:06:17Z

← Older revision		Revision as of 16:06, 4 March 2012
Line 1:		Line 1:
			<categorytree style="float:right; clear:right; margin-left:1ex; border: 1px solid gray; padding: 0.7ex;" mode=pages hideprefix=always>Subsystems</categorytree>
	== Telemetry (Modem) ==		== Telemetry (Modem) ==
	The modem protocol and baud rate must be set in both the airframe file and ground station. Any standard baud rate can be used, with 9600 being adequate and 57600 recommended for most users to allow high speed telemetry for more detailed flight data analysis. The actual data rate is determined by the number of messages being sent and the period of each message as defined in your [[Telemetry\|telemetry file]], e.g. <tt>conf/telemetry/default.xml</tt>. Those wishing to experiment with "alternative" modems can reduce the number and period of each telemetry message to fit within most any bandwidth constraint.		The modem protocol and baud rate must be set in both the airframe file and ground station. Any standard baud rate can be used, with 9600 being adequate and 57600 recommended for most users to allow high speed telemetry for more detailed flight data analysis. The actual data rate is determined by the number of messages being sent and the period of each message as defined in your [[Telemetry\|telemetry file]], e.g. <tt>conf/telemetry/default.xml</tt>. Those wishing to experiment with "alternative" modems can reduce the number and period of each telemetry message to fit within most any bandwidth constraint.

Flixr: removed software category, as Subsystems is a subcategory of Software

2012-03-01T22:31:30Z

removed software category, as Subsystems is a subcategory of Software

← Older revision		Revision as of 16:31, 1 March 2012
Line 96:		Line 96:
	Use this constant /dev/paparazzi/ttyUSB0 when using either the ftdi cable or a Maxstream USB ground modem.. Otherwise use /dev/ttyUSB0 (the ttyUSB0 being the device that you are using. Note: it might not always be ttyUSB0). This paparazzi directory in the dev folder is created when setting the udev rules. [http://paparazzi.enac.fr/wiki/Installation#Setting_access_rights_for_USB_download Setting Udev rules]		Use this constant /dev/paparazzi/ttyUSB0 when using either the ftdi cable or a Maxstream USB ground modem.. Otherwise use /dev/ttyUSB0 (the ttyUSB0 being the device that you are using. Note: it might not always be ttyUSB0). This paparazzi directory in the dev folder is created when setting the udev rules. [http://paparazzi.enac.fr/wiki/Installation#Setting_access_rights_for_USB_download Setting Udev rules]

	~~[[Category:Software]]~~ [[Category:User_Documentation]] [[Category:Subsystems]]		[[Category:User_Documentation]] [[Category:Subsystems]]

Flixr at 20:06, 5 December 2011

2011-12-05T20:06:16Z

← Older revision		Revision as of 14:06, 5 December 2011
Line 18:		Line 18:
	The correct UART is already defined by default according to your board.		The correct UART is already defined by default according to your board.
	The default modem baudrate is 57600baud.		The default modem baudrate is 57600baud.

			=== Configure Options ===
			If a configure option is not specified the default is used.

			* '''MODEM_PORT''': ''UART0'', ''UART1'', etc.
			** default: The correct UART is already defined according to your board.
			* '''MODEM_BAUD''': ''B4800'', ''B9600'', ''B38400'', ''B57600'', ''B115200''
			** default: ''B57600''

	If you use different baud rate or Uart set the according parameters, e.g.		If you use different baud rate or Uart set the according parameters, e.g.
Line 25:		Line 33:
	...		...
	<subsystem name="telemetry" type="transparent">		<subsystem name="telemetry" type="transparent">
	<configure name="MODEM_BAUD" value="B9600"/>		<configure name="MODEM_BAUD" value="B9600"/>
	<configure name="MODEM_PORT" value="UART1"/>		<configure name="MODEM_PORT" value="UART1"/>
	</subsystem>		</subsystem>
	</firmware>		</firmware>
Line 32:		Line 40:
	}}		}}

			== Configuring The Serial Protocol ==
	=== Configuring The Serial Protocol ===
	New users are advised to start with the standard serial protocol before attempting to setup an addressed API link. There are no real reasons for the novice user to use the xbee protocol over the standard PPRZTransport. Even if you are using a Maxstream modem you should still start out with the standard. Lastly it should be pointed out that using a single UAS there is no disadvantage and that the [http://www.engr.usu.edu/wiki/index.php/OSAM OSAM] Paparazzi Team at UAS 2008 took second place using the STANDARD protocol. The serial protocol works with virtually any modem as well as direct cable connections. The baud rates of the airborne modem, autopilot, ground modem, and PC must be configured correctly. The PC and autopilot serial ports do not need to be set to the same baud rate, i.e. when running multiple aircraft from a single ground modem, the ground modem may require a higher baud rate than any of the airborne modems in order to stream the data from multiple simultaneous sources (Warning, this may not be correct for all modems, especially Radiotronix modems that require to have the same baudrate on both side).		New users are advised to start with the standard serial protocol before attempting to setup an addressed API link. There are no real reasons for the novice user to use the xbee protocol over the standard PPRZTransport. Even if you are using a Maxstream modem you should still start out with the standard. Lastly it should be pointed out that using a single UAS there is no disadvantage and that the [http://www.engr.usu.edu/wiki/index.php/OSAM OSAM] Paparazzi Team at UAS 2008 took second place using the STANDARD protocol. The serial protocol works with virtually any modem as well as direct cable connections. The baud rates of the airborne modem, autopilot, ground modem, and PC must be configured correctly. The PC and autopilot serial ports do not need to be set to the same baud rate, i.e. when running multiple aircraft from a single ground modem, the ground modem may require a higher baud rate than any of the airborne modems in order to stream the data from multiple simultaneous sources (Warning, this may not be correct for all modems, especially Radiotronix modems that require to have the same baudrate on both side).

	=== Configuring The Maxstream API Protocol ===		== Configuring The Maxstream API Protocol ==
	The optional API protocol enables hardware addressing so that multiple aircraft can be managed from a single ground modem, or multiple aircraft and multiple ground stations can work simultaneously without interference from one another. API mode is enabled by sending an escape sequence (+++) followed by AT commands, this can be done automatically at each boot or can be permanently configured with the "ATWR" command for greater reliability.		The optional API protocol enables hardware addressing so that multiple aircraft can be managed from a single ground modem, or multiple aircraft and multiple ground stations can work simultaneously without interference from one another. API mode is enabled by sending an escape sequence (+++) followed by AT commands, this can be done automatically at each boot or can be permanently configured with the "ATWR" command for greater reliability.

Line 55:		Line 62:
	* Upgrade your Maxstream firmware to the latest version before attempting API mode operation.		* Upgrade your Maxstream firmware to the latest version before attempting API mode operation.

	==== Alternate Method ====		=== Alternate Method ===
	This is the way it is done in funjet1.xml and has been tested to work by Danstah		This is the way it is done in funjet1.xml and has been tested to work by Danstah
	{{Box Code\|conf/airframes/funjet1.xml\|		{{Box Code\|conf/airframes/funjet1.xml\|
Line 70:		Line 77:
	Also for multiple UAS, a good way to configure them is to use 9600Baud for the Autopilot board and use a ground modem configured to 57600Baud. After your aircrafts are working well, set your configuration to use minimal telemetry.		Also for multiple UAS, a good way to configure them is to use 9600Baud for the Autopilot board and use a ground modem configured to 57600Baud. After your aircrafts are working well, set your configuration to use minimal telemetry.

	=== Set GCS baud rate ===		== Set GCS baud rate ==
	Set can set the baudrate for the link in the GCS by specifying ''-s 57600'' as a parameter to link. Then just save your session so you won't have to change it again next time.		Set can set the baudrate for the link in the GCS by specifying ''-s 57600'' as a parameter to link. Then just save your session so you won't have to change it again next time.

Flixr: Subsystems/telemetry moved to Subsystem/telemetry

2011-11-23T14:16:06Z

Subsystems/telemetry moved to Subsystem/telemetry

← Older revision	Revision as of 08:16, 23 November 2011
(No difference)

Flixr at 13:45, 23 November 2011

2011-11-23T13:45:09Z

← Older revision		Revision as of 07:45, 23 November 2011
Line 88:		Line 88:

	Use this constant /dev/paparazzi/ttyUSB0 when using either the ftdi cable or a Maxstream USB ground modem.. Otherwise use /dev/ttyUSB0 (the ttyUSB0 being the device that you are using. Note: it might not always be ttyUSB0). This paparazzi directory in the dev folder is created when setting the udev rules. [http://paparazzi.enac.fr/wiki/Installation#Setting_access_rights_for_USB_download Setting Udev rules]		Use this constant /dev/paparazzi/ttyUSB0 when using either the ftdi cable or a Maxstream USB ground modem.. Otherwise use /dev/ttyUSB0 (the ttyUSB0 being the device that you are using. Note: it might not always be ttyUSB0). This paparazzi directory in the dev folder is created when setting the udev rules. [http://paparazzi.enac.fr/wiki/Installation#Setting_access_rights_for_USB_download Setting Udev rules]

			[[Category:Software]] [[Category:User_Documentation]] [[Category:Subsystems]]

Flixr: /* Alternate Method */

2011-11-23T11:34:27Z

Alternate Method

← Older revision		Revision as of 05:34, 23 November 2011
Line 57:		Line 57:
	==== Alternate Method ====		==== Alternate Method ====
	This is the way it is done in funjet1.xml and has been tested to work by Danstah		This is the way it is done in funjet1.xml and has been tested to work by Danstah

	{{Box Code\|conf/airframes/funjet1.xml\|		{{Box Code\|conf/airframes/funjet1.xml\|
	<nowiki>		<nowiki>

Flixr: /* Alternate Method */ section DATALINK not needed anymore

2011-11-23T11:34:16Z

Alternate Method: section DATALINK not needed anymore

@@ Line 66: / Line 66: @@
      ...
   </section></nowiki>
 }}

Ghattenb: section DATALINK not needed anymore

2011-11-22T13:35:22Z

section DATALINK not needed anymore

← Older revision		Revision as of 07:35, 22 November 2011
Line 34:		Line 34:

	=== Configuring The Serial Protocol ===		=== Configuring The Serial Protocol ===
	New users are advised to start with the standard serial protocol before attempting to setup an addressed API link. There are no real reasons for the novice user to use the xbee protocol over the standard PPRZTransport. Even if you are using a Maxstream modem you should still start out with the standard. Lastly it should be pointed out that using a single UAS there is no disadvantage and that the [http://www.engr.usu.edu/wiki/index.php/OSAM OSAM] Paparazzi Team at UAS 2008 took second place using the STANDARD protocol. The serial protocol works with virtually any modem as well as direct cable connections. The baud rates of the airborne modem, autopilot, ground modem, and PC must be configured correctly. The PC and autopilot serial ports do not need to be set to the same baud rate, i.e. when running multiple aircraft from a single ground modem, the ground modem may require a higher baud rate than any of the airborne modems in order to stream the data from multiple simultaneous sources.		New users are advised to start with the standard serial protocol before attempting to setup an addressed API link. There are no real reasons for the novice user to use the xbee protocol over the standard PPRZTransport. Even if you are using a Maxstream modem you should still start out with the standard. Lastly it should be pointed out that using a single UAS there is no disadvantage and that the [http://www.engr.usu.edu/wiki/index.php/OSAM OSAM] Paparazzi Team at UAS 2008 took second place using the STANDARD protocol. The serial protocol works with virtually any modem as well as direct cable connections. The baud rates of the airborne modem, autopilot, ground modem, and PC must be configured correctly. The PC and autopilot serial ports do not need to be set to the same baud rate, i.e. when running multiple aircraft from a single ground modem, the ground modem may require a higher baud rate than any of the airborne modems in order to stream the data from multiple simultaneous sources (Warning, this may not be correct for all modems, especially Radiotronix modems that require to have the same baudrate on both side).

	~~{{Box Code\|conf/airframes/myplane.xml\|~~
	~~<nowiki>~~
	~~<section name="DATALINK" prefix="DATALINK_">~~
	~~<define name="DEVICE_TYPE" value="PPRZ"/>~~
	~~<define name="DEVICE_ADDRESS" value="...."/>~~
	~~</section>~~
	~~</nowiki>~~
	}}
	~~The above example tells~~ the ~~autopilot to send and receive data in standard serial form~~.

	=== Configuring The Maxstream API Protocol ===		=== Configuring The Maxstream API Protocol ===