Module/Airspeed ETS - Revision history

Openuas at 14:00, 8 November 2023

2023-11-08T14:00:37Z

← Older revision		Revision as of 08:00, 8 November 2023
Line 82:		Line 82:
	<modules>		<modules>
	...		...
	<~~load~~ name="airspeed_ets~~.xml~~" />		<module name="airspeed_ets">
	...		...
	</modules>		</modules>
Line 105:		Line 105:
	}}		}}
	</div></div>		</div></div>



	== Configuration ==		== Configuration ==
Line 115:		Line 113:
	<source lang="xml">		<source lang="xml">
	<modules>		<modules>
	<~~load~~ name="airspeed_ets~~.xml~~">		<module name="airspeed_ets">
	<!-- Applies if another I2C interface than IC20 is used -->		<!-- Applies if another I2C interface than IC20 is used -->
	<define name="AIRSPEED_ETS_SCALE" value="1.44"/>		<define name="AIRSPEED_ETS_SCALE" value="1.44"/>
	<define name="AIRSPEED_ETS_OFFSET" value="50"/>		<define name="AIRSPEED_ETS_OFFSET" value="50"/>
	<configure name="AIRSPEED_ETS_I2C_DEV" value="i2c1"/>		<configure name="AIRSPEED_ETS_I2C_DEV" value="i2c1"/>
	</~~load~~>		</module>
	</modules>		</modules>
	</source>		</source>
Line 130:		Line 128:
	{{Box Code\|conf/airframes/myplane.xml\|		{{Box Code\|conf/airframes/myplane.xml\|
	<source lang="xml">		<source lang="xml">
	<target name="ap" board="~~twog_1~~.0">		<target name="ap" board="px4fmu_4.0_chibios">
	<define name="AGR_CLIMB"/>		<define name="AGR_CLIMB"/>
	<define name="USE_AIRSPEED"/> <!-- Use the airspeed sensor in the control loop -->		<define name="USE_AIRSPEED"/> <!-- Use the airspeed sensor in the control loop -->
Line 136:		Line 134:
	</source>		</source>
	}}		}}

			Where ofcourse the board value is just an example here, use the name of the hardware you use.

	=== Airframe configuration ===		=== Airframe configuration ===

	Now to use real airspeed values for adjusting your ~~aircrafts~~ autopilot behavior there are several way to accomplish this. A simple classic way is to add the following to the end of the "VERTICAL CONTROL" section of your airframe file:		Now to use real airspeed values for adjusting your aircraft autopilot behavior there are several way to accomplish this. A simple classic way is to add the following to the end of the "VERTICAL CONTROL" section of your airframe file:
	{{Box Code\|conf/airframes/myplane.xml\|		{{Box Code\|conf/airframes/myplane.xml\|
	<source lang="xml">		<source lang="xml">
Line 164:		Line 164:
	Better even is to start using ETECS, '''E'''nhanced '''T'''otal '''E'''nergy '''C'''ontrol '''S'''ystem		Better even is to start using ETECS, '''E'''nhanced '''T'''otal '''E'''nergy '''C'''ontrol '''S'''ystem

	Take a look at See paparazzi/conf/airframes/MentorEnergy.xml for an example airframe configuration.		Take a look at See ~/paparazzi/conf/airframes/examples/MentorEnergy.xml for an example airframe configuration.

	=== Debugging and logging the airspeed values ===		=== Debugging and logging the airspeed values ===
Line 194:		Line 194:
	<source lang="xml">		<source lang="xml">
	<modules>		<modules>

			...

	<module name="airspeed_ets">		<module name="airspeed_ets">
Line 206:		Line 208:
	<define name="AIRSPEED_ETS_SYNC_SEND"/> <!-- Can be disabled after full validation after testflight -->		<define name="AIRSPEED_ETS_SYNC_SEND"/> <!-- Can be disabled after full validation after testflight -->
	</module>		</module>

			...

	</modules>		</modules>
Line 229:		Line 233:
	== Measurement only ==		== Measurement only ==

	To use the sensor for airspeed measurement is also possible. This Measurement only mode does thus not ~~imput~~ to the control loops to have effect to the aircraft ~~behaviour~~.		To use the sensor for airspeed measurement is also possible. This Measurement only mode does thus not input to the control loops to have effect to the aircraft behavior.

	To see the sensors data in the log file set the SENSOR_SYNC_SEND in your airframe file. Every time new data is available it will be sent directly.		To see the sensors data in the log file set the SENSOR_SYNC_SEND in your airframe file. Every time new data is available it will be sent directly.
Line 235:		Line 239:
	<source lang="xml">		<source lang="xml">
	<modules>		<modules>
	<~~load~~ name="airspeed_ets~~.xml~~">		<module name="airspeed_ets">
	<define name="~~SENSOR_SYNC_SEND~~"/>		<define name="AIRSPEED_ETS_SYNC_SEND"/>
	</~~load~~>		</module>
	</modules>		</modules>
	</source>		</source>
	}}		}}

	<span style="color:#FF0000">'''Caution!'''</span> ''Please note: if you are using ~~the master~~ branch ~~and have merged commits on or later than~~ July 16, 2013, please replace SENSOR_SYNC_SEND ~~with AIRSPEED_ETS_SYNC_SEND~~''		<span style="color:#FF0000">'''Caution!'''</span>''Please note: if you are using and old branch of before July 16, 2013, please replace AIRSPEED_ETS_SYNC_SEND with SENSOR_SYNC_SEND''

	===Result message===		===Result message===
Line 269:		Line 273:

	Add the following to your module part in your airframe XML document. Where ''value'' can be anything from 0.01 to 4seconds. Some users report that a value of 1 fixes the issue for them.		Add the following to your module part in your airframe XML document. Where ''value'' can be anything from 0.01 to 4seconds. Some users report that a value of 1 fixes the issue for them.
			<source lang="xml">
	<~~load~~ name="airspeed_ets~~.xml~~">		<module name="airspeed_ets">

	...		...
Line 276:		Line 280:
	...		...

	</~~load~~>		</module>
			</source>


	[[Category:User_Documentation]] [[Category:Modules]]		[[Category:User_Documentation]] [[Category:Modules]]

Openuas: Add explanation on how to add debug message again

2023-11-08T13:39:48Z

Add explanation on how to add debug message again

← Older revision		Revision as of 07:39, 8 November 2023
Line 168:		Line 168:
	=== Debugging and logging the airspeed values ===		=== Debugging and logging the airspeed values ===

	To debug or log the raw values from the ETS airspeed sensor define ~~SENSOR_SYNC_SEND~~ in your airframe file to send the message AIRSPEED_ETS on every sensor reading.		To debug or log the raw values from the ETS airspeed sensor define AIRSPEED_ETS_SYNC_SEND in your airframe file to send the message AIRSPEED_ETS on every sensor reading.
	Note that defining this sends the AIRSPEED_ETS message at the sensor read rate as defined in conf/modules/airspeed_ets.xml.		Note that defining this sends the AIRSPEED_ETS message at the sensor read rate as defined in conf/modules/airspeed_ets.xml.
	This does not have any bearing on the AIRSPEED message (if both ~~SENSOR_SYNC_SEND~~ and USE_AIRSPEED are defined, then both messages are sent).		This does not have any bearing on the AIRSPEED message (if both AIRSPEED_ETS_SYNC_SEND and USE_AIRSPEED are defined, then both messages are sent).

	<span style="color:#FF0000">'''Caution!'''</span> ''Please note: if you are using ~~the master~~ branch ~~and have merged commits on or later than~~ July 16, 2013, please replace SENSOR_SYNC_SEND ~~with AIRSPEED_ETS_SYNC_SEND~~''		<span style="color:#FF0000">'''Caution!'''</span> ''Please note: if you are using and old branch of before July 16, 2013, please replace AIRSPEED_ETS_SYNC_SEND with SENSOR_SYNC_SEND''

			Also note that as of 15 Oct 2023 the default debug message is no longer available in the PPRZlink messages.xml file.
			Therefore to determine your possible sensor offset add this temporary debug message to the ~/paparazzi/sw/ext/pprzlink/message_definitions/v1.0/messages.xml

			<source lang="xml">

			<message name="AIRSPEED_ETS" id="57">
			<field name="adc" type="uint16"/>
			<field name="offset" type="uint16"/>
			<field name="scaled" type="float"/>
			</message>

			</source>

			After adding that don't forget that this is needed before you upload you firmware to the flightcontroller to make sure changes are included:

			make clean && make

	{{Box Code\|conf/airframes/myplane.xml\|		{{Box Code\|conf/airframes/myplane.xml\|
	<source lang="xml">		<source lang="xml">
	<modules>		<modules>
	<~~load~~ name="airspeed_ets.~~xml~~">
	<define name="~~SENSOR_SYNC_SEND~~"/>		<module name="airspeed_ets">
	</~~load~~>		<configure name="AIRSPEED_ETS_I2C_DEV" value="i2c1"/>
			<define name="AIRSPEED_ETS_START_DELAY" value="0.7"/>
			<define name="AIRSPEED_ETS_SCALE" value="1.76"/>
			<!--<define name="AIRSPEED_ETS_OFFSET" value="2"/>-->
			<define name="AIRSPEED_ETS_3RD_PARTY_MODE" value="FALSE"/><!-- The default out of the box is ETS mode-->
			<define name="AIRSPEED_ETS_USE_FILTER" value="TRUE"/>
			<define name="AIRSPEED_ETS_LOWPASS_TAU" value=".20"/>

			<define name="AIRSPEED_ETS_SYNC_SEND"/> <!-- Can be disabled after full validation after testflight -->
			</module>

	</modules>		</modules>
	</source>		</source>
Line 194:		Line 221:
	}}		}}

	The AIRSPEED_ETS message does NOT need to be added to the telemetry configuration since it is sent directly by the module if ~~SENSOR_SYNC_SEND~~ is defined.		The AIRSPEED_ETS message does NOT need to be added to the telemetry configuration since it is sent directly by the module if AIRSPEED_ETS_SYNC_SEND is defined.

	=== NOTES ===		=== NOTES ===

Openuas: unintended edit

2020-12-31T14:43:43Z

unintended edit

← Older revision		Revision as of 08:43, 31 December 2020
Line 7:		Line 7:

	NOTE: the sensor has two operating modes which determine what value is sent to the autopilot. In the default mode the pressure diference between the 2 ends of the pitot is sent. Supposedly this could be used to calculate airspeed but in reality temperature must also be taken into account. The rest of this page assumes that a temperature reading is not needed and the usefullness is in question. Do not use it for any serious stuff.<BR>		NOTE: the sensor has two operating modes which determine what value is sent to the autopilot. In the default mode the pressure diference between the 2 ends of the pitot is sent. Supposedly this could be used to calculate airspeed but in reality temperature must also be taken into account. The rest of this page assumes that a temperature reading is not needed and the usefullness is in question. Do not use it for any serious stuff.<BR>
	In the other mode, called "third party mode", the actual speed value is sent as shown in the sensor. The sensor is said by the manufacturer to take temperature into account to arrive at this value so this should be used as the correct speed. To put the sensor in this mode ~~one can use the supplied jumper over the pins as described in the Eagletree Manual~~.		In the other mode, called "third party mode", the actual speed value is sent as shown in the sensor. The sensor is said by the manufacturer to take temperature into account to arrive at this value so this should be used as the correct speed. Unfortunately the Paparazzi code does not work in this mode and additional hardware (an EagleTree elogger) is needed to put the sensor in this mode.

Openuas: Added short explanation on how to set 3rd party mode output

2020-12-31T14:39:01Z

Added short explanation on how to set 3rd party mode output

← Older revision		Revision as of 08:39, 31 December 2020
Line 7:		Line 7:

	NOTE: the sensor has two operating modes which determine what value is sent to the autopilot. In the default mode the pressure diference between the 2 ends of the pitot is sent. Supposedly this could be used to calculate airspeed but in reality temperature must also be taken into account. The rest of this page assumes that a temperature reading is not needed and the usefullness is in question. Do not use it for any serious stuff.<BR>		NOTE: the sensor has two operating modes which determine what value is sent to the autopilot. In the default mode the pressure diference between the 2 ends of the pitot is sent. Supposedly this could be used to calculate airspeed but in reality temperature must also be taken into account. The rest of this page assumes that a temperature reading is not needed and the usefullness is in question. Do not use it for any serious stuff.<BR>
	In the other mode, called "third party mode", the actual speed value is sent as shown in the sensor. The sensor is said by the manufacturer to take temperature into account to arrive at this value so this should be used as the correct speed. ~~Unfortunately~~ the ~~Paparazzi code does not work~~ in this mode ~~and additional hardware (an EagleTree elogger) is needed to put~~ the ~~sensor~~ in ~~this mode~~.		In the other mode, called "third party mode", the actual speed value is sent as shown in the sensor. The sensor is said by the manufacturer to take temperature into account to arrive at this value so this should be used as the correct speed. To put the sensor in this mode one can use the supplied jumper over the pins as described in the Eagletree Manual.

Flixr: use configure for I2C devs... no need to specify USE_I2Cx separately

2015-12-10T20:48:07Z

use configure for I2C devs... no need to specify USE_I2Cx separately

← Older revision		Revision as of 14:48, 10 December 2015
Line 73:		Line 73:

	= Usage =		= Usage =

			'''Please refer to the generated docs for the exact configuration options of the version you are using!'''
			http://docs.paparazziuav.org/latest/module__airspeed_ets.html

	To use it load the ''airspeed_ets'' module:		To use it load the ''airspeed_ets'' module:
Line 85:		Line 88:
	}}		}}

			<div class="toccolours mw-collapsible mw-collapsed" style="width:800px">
			For versions older than v5.8
			<div class="mw-collapsible-content">For versions older than v5.8, also define the used I2C device:
	Depending on your board and the I2C interface you are using, you may need to		Depending on your board and the I2C interface you are using, you may need to
	enable I2CX, where X is 0,1,2,etc., if you are not using it already:		enable I2CX, where X is 0,1,2,etc., if you are not using it already:
Line 98:		Line 104:
	</source>		</source>
	}}		}}
			</div></div>



Line 111:		Line 119:
	<define name="AIRSPEED_ETS_SCALE" value="1.44"/>		<define name="AIRSPEED_ETS_SCALE" value="1.44"/>
	<define name="AIRSPEED_ETS_OFFSET" value="50"/>		<define name="AIRSPEED_ETS_OFFSET" value="50"/>
	<~~define~~ name="AIRSPEED_ETS_I2C_DEV" value="i2c1"/>		<configure name="AIRSPEED_ETS_I2C_DEV" value="i2c1"/>
	</load>		</load>
	</modules>		</modules>
Line 124:		Line 132:
	<target name="ap" board="twog_1.0">		<target name="ap" board="twog_1.0">
	<define name="AGR_CLIMB"/>		<define name="AGR_CLIMB"/>
	~~<define name="USE_I2C0"/> <!-- Details: see above -->~~
	<define name="USE_AIRSPEED"/> <!-- Use the airspeed sensor in the control loop -->		<define name="USE_AIRSPEED"/> <!-- Use the airspeed sensor in the control loop -->
	</target>		</target>

Alonsoac: /* Introduction */

2014-12-21T02:25:46Z

Introduction

← Older revision		Revision as of 20:25, 20 December 2014
Line 5:		Line 5:

	The EagleTree Airspeed Sensor is a low cost module and comes with a good [http://en.wikipedia.org/wiki/Pitot_tube pitot tube] (Prandtl style, pitot-static tube) that includes static and dynamic ports. It has an I²C interface that connects directly to the Autopilot I²C port.		The EagleTree Airspeed Sensor is a low cost module and comes with a good [http://en.wikipedia.org/wiki/Pitot_tube pitot tube] (Prandtl style, pitot-static tube) that includes static and dynamic ports. It has an I²C interface that connects directly to the Autopilot I²C port.

			NOTE: the sensor has two operating modes which determine what value is sent to the autopilot. In the default mode the pressure diference between the 2 ends of the pitot is sent. Supposedly this could be used to calculate airspeed but in reality temperature must also be taken into account. The rest of this page assumes that a temperature reading is not needed and the usefullness is in question. Do not use it for any serious stuff.<BR>
			In the other mode, called "third party mode", the actual speed value is sent as shown in the sensor. The sensor is said by the manufacturer to take temperature into account to arrive at this value so this should be used as the correct speed. Unfortunately the Paparazzi code does not work in this mode and additional hardware (an EagleTree elogger) is needed to put the sensor in this mode.


	{\|border="1"		{\|border="1"

Openuas: /* Issues */

2014-05-21T16:44:43Z

Issues

← Older revision		Revision as of 10:44, 21 May 2014
Line 228:		Line 228:
	=Issues=		=Issues=

	Some people report that the sensor only works after a fresh upload ~~in the filed~~, not after a regular power on. ~~It could be that adding~~ a AIRSPEED_ETS_START_DELAY setting could help. For this to work ~~you likly~~ need ~~the master branch~~ of Paparazzi ~~sourcecode (git checkout master)~~.		Some people report that the sensor only works after a fresh upload, not after a regular power on. Adding a AIRSPEED_ETS_START_DELAY setting could help getting it to work. For this to work need at least version 5.2 of Paparazzi.

	Add the following to your module part in your airframe XML document. Where ''value'' can be anything from 0.01 to 4seconds. Some users report that a value of 1 ~~works well~~ for them.		Add the following to your module part in your airframe XML document. Where ''value'' can be anything from 0.01 to 4seconds. Some users report that a value of 1 fixes the issue for them.

	<load name="airspeed_ets.xml">		<load name="airspeed_ets.xml">

Openuas: /* Airframe configuration */

2014-05-21T16:42:21Z

Airframe configuration

← Older revision		Revision as of 10:42, 21 May 2014
Line 128:		Line 128:
	=== Airframe configuration ===		=== Airframe configuration ===

	Now to use real airspeed values for adjusting your aircrafts autopilot behavior, add the following to the end of the "VERTICAL CONTROL" section of your airframe file:		Now to use real airspeed values for adjusting your aircrafts autopilot behavior there are several way to accomplish this. A simple classic way is to add the following to the end of the "VERTICAL CONTROL" section of your airframe file:
	{{Box Code\|conf/airframes/myplane.xml\|		{{Box Code\|conf/airframes/myplane.xml\|
	<source lang="xml">		<source lang="xml">
Line 150:		Line 150:

	See paparazzi/conf/airframes/easystar_ets_example.xml for an example airframe configuration.		See paparazzi/conf/airframes/easystar_ets_example.xml for an example airframe configuration.

			Better even is to start using ETECS, '''E'''nhanced '''T'''otal '''E'''nergy '''C'''ontrol '''S'''ystem

			Take a look at See paparazzi/conf/airframes/MentorEnergy.xml for an example airframe configuration.

	=== Debugging and logging the airspeed values ===		=== Debugging and logging the airspeed values ===

Openuas: /* Configuration */

2014-05-21T16:39:33Z

Configuration

← Older revision		Revision as of 10:39, 21 May 2014
Line 99:		Line 99:

	You can also set some '''optional parameters to change the default configuration'''.		You can also set some '''optional parameters to change the default configuration'''.
	For example to use I2C1 instead of I2C0, a scale of 2 (default is 1.8) and offset of 50 (default is 0) is needed:		For example to use I2C1 instead of I2C0, a scale of 1.44 (default is 1.8) and offset of 50 (default is 0) is needed:
	{{Box Code\|conf/airframes/myplane.xml\|		{{Box Code\|conf/airframes/myplane.xml\|
	<source lang="xml">		<source lang="xml">
Line 105:		Line 105:
	<load name="airspeed_ets.xml">		<load name="airspeed_ets.xml">
	<!-- Applies if another I2C interface than IC20 is used -->		<!-- Applies if another I2C interface than IC20 is used -->
	<define name="AIRSPEED_ETS_SCALE" value="2"/>		<define name="AIRSPEED_ETS_SCALE" value="1.44"/>
	<define name="AIRSPEED_ETS_OFFSET" value="50"/>		<define name="AIRSPEED_ETS_OFFSET" value="50"/>
	<define name="AIRSPEED_ETS_I2C_DEV" value="i2c1"/>		<define name="AIRSPEED_ETS_I2C_DEV" value="i2c1"/>
Line 112:		Line 112:
	</source>		</source>
	}}		}}


	== Usage as sensor for speed control ==		== Usage as sensor for speed control ==

Openuas: /* Issues */

2013-12-29T17:17:09Z

Issues

← Older revision		Revision as of 11:17, 29 December 2013
Line 227:		Line 227:
	Some people report that the sensor only works after a fresh upload in the filed, not after a regular power on. It could be that adding a AIRSPEED_ETS_START_DELAY setting could help. For this to work you likly need the master branch of Paparazzi sourcecode (git checkout master).		Some people report that the sensor only works after a fresh upload in the filed, not after a regular power on. It could be that adding a AIRSPEED_ETS_START_DELAY setting could help. For this to work you likly need the master branch of Paparazzi sourcecode (git checkout master).

	Add the following to your module part in your airframe XML document		Add the following to your module part in your airframe XML document. Where ''value'' can be anything from 0.01 to 4seconds. Some users report that a value of 1 works well for them.

	<load name="airspeed_ets.xml">		<load name="airspeed_ets.xml">

	...		...
	<define name="AIRSPEED_ETS_START_DELAY" value="2"/>		<define name="AIRSPEED_ETS_START_DELAY" value="1"/>
	...		...