Commit d3d15472 authored by PX4BuildBot's avatar PX4BuildBot

Update PX4 Firmware metadata Wed Oct 17 16:54:59 UTC 2018

parent 800791dd
...@@ -535,6 +535,24 @@ ...@@ -535,6 +535,24 @@
<output name="AUX3">feed-through of RC AUX3 channel</output> <output name="AUX3">feed-through of RC AUX3 channel</output>
</airframe> </airframe>
</airframe_group> </airframe_group>
<airframe_group image="AirframeUnknown" name="Plane V-Tail">
<airframe id="2200" maintainer="Friedrich Beckmann &lt;friedrich.beckmann@hs-augsburg.de&gt;" name="X-UAV Mini Talon">
<class>Plane</class>
<maintainer>Friedrich Beckmann &lt;friedrich.beckmann@hs-augsburg.de&gt;</maintainer>
<type>Plane V-Tail</type>
<output name="MAIN1">aileron right</output>
<output name="MAIN2">aileron left</output>
<output name="MAIN3">v-tail right</output>
<output name="MAIN4">v-tail left</output>
<output name="MAIN5">throttle</output>
<output name="MAIN6">wheel</output>
<output name="MAIN7">flaps right</output>
<output name="MAIN8">flaps left</output>
<output name="AUX1">feed-through of RC AUX1 channel</output>
<output name="AUX2">feed-through of RC AUX2 channel</output>
<output name="AUX3">feed-through of RC AUX3 channel</output>
</airframe>
</airframe_group>
<airframe_group image="AirframeUnknown" name="Simulation (Plane)"> <airframe_group image="AirframeUnknown" name="Simulation (Plane)">
<airframe id="1000" maintainer="Lorenz Meier &lt;lorenz@px4.io&gt;" name="HILStar (XPlane)"> <airframe id="1000" maintainer="Lorenz Meier &lt;lorenz@px4.io&gt;" name="HILStar (XPlane)">
<class>Plane</class> <class>Plane</class>
...@@ -579,27 +597,6 @@ ...@@ -579,27 +597,6 @@
<output name="AUX3">feed-through of RC AUX3 channel</output> <output name="AUX3">feed-through of RC AUX3 channel</output>
</airframe> </airframe>
</airframe_group> </airframe_group>
<airframe_group image="AirframeUnknown" name="Plane V-Tail">
<airframe id="2200" maintainer="Friedrich Beckmann &lt;friedrich.beckmann@hs-augsburg.de&gt;" name="X-UAV Mini Talon">
<class>Plane
The Mini Talon does not have a wheel and
no flaps. I leave them here because the mixer
computes also wheel and flap controls.</class>
<maintainer>Friedrich Beckmann &lt;friedrich.beckmann@hs-augsburg.de&gt;</maintainer>
<type>Plane V-Tail</type>
<output name="MAIN1">aileron right</output>
<output name="MAIN2">aileron left</output>
<output name="MAIN3">v-tail right</output>
<output name="MAIN4">v-tail left</output>
<output name="MAIN5">throttle</output>
<output name="MAIN6">wheel</output>
<output name="MAIN7">flaps right</output>
<output name="MAIN8">flaps left</output>
<output name="AUX1">feed-through of RC AUX1 channel</output>
<output name="AUX2">feed-through of RC AUX2 channel</output>
<output name="AUX3">feed-through of RC AUX3 channel</output>
</airframe>
</airframe_group>
<airframe_group image="Rover" name="Rover"> <airframe_group image="Rover" name="Rover">
<airframe id="50000" maintainer="" name="Generic Ground Vehicle"> <airframe id="50000" maintainer="" name="Generic Ground Vehicle">
<class>Rover</class> <class>Rover</class>
......
...@@ -1033,9 +1033,9 @@ This parameter controls the time constant of the decay</short_desc> ...@@ -1033,9 +1033,9 @@ This parameter controls the time constant of the decay</short_desc>
</parameter> </parameter>
<parameter default="1" name="EKF2_AID_MASK" type="INT32"> <parameter default="1" name="EKF2_AID_MASK" type="INT32">
<short_desc>Integer bitmask controlling data fusion and aiding methods</short_desc> <short_desc>Integer bitmask controlling data fusion and aiding methods</short_desc>
<long_desc>Set bits in the following positions to enable: 0 : Set to true to use GPS data if available 1 : Set to true to use optical flow data if available 2 : Set to true to inhibit IMU bias estimation 3 : Set to true to enable vision position fusion 4 : Set to true to enable vision yaw fusion 5 : Set to true to enable multi-rotor drag specific force fusion 6 : set to true if the EV observations are in a non NED reference frame and need to be rotated before being used</long_desc> <long_desc>Set bits in the following positions to enable: 0 : Set to true to use GPS data if available 1 : Set to true to use optical flow data if available 2 : Set to true to inhibit IMU bias estimation 3 : Set to true to enable vision position fusion 4 : Set to true to enable vision yaw fusion. Cannot be used if bit position 7 is true. 5 : Set to true to enable multi-rotor drag specific force fusion 6 : set to true if the EV observations are in a non NED reference frame and need to be rotated before being used 7 : Set to true to enable GPS yaw fusion. Cannot be used if bit position 4 is true.</long_desc>
<min>0</min> <min>0</min>
<max>127</max> <max>255</max>
<reboot_required>true</reboot_required> <reboot_required>true</reboot_required>
<bitmask> <bitmask>
<bit index="0">use GPS</bit> <bit index="0">use GPS</bit>
...@@ -1045,6 +1045,7 @@ This parameter controls the time constant of the decay</short_desc> ...@@ -1045,6 +1045,7 @@ This parameter controls the time constant of the decay</short_desc>
<bit index="4">vision yaw fusion</bit> <bit index="4">vision yaw fusion</bit>
<bit index="5">multi-rotor drag fusion</bit> <bit index="5">multi-rotor drag fusion</bit>
<bit index="6">rotate external vision</bit> <bit index="6">rotate external vision</bit>
<bit index="7">GPS yaw fusion</bit>
</bitmask> </bitmask>
</parameter> </parameter>
<parameter default="0.1" name="EKF2_ANGERR_INIT" type="FLOAT"> <parameter default="0.1" name="EKF2_ANGERR_INIT" type="FLOAT">
...@@ -1458,7 +1459,7 @@ This parameter is used when the magnetometer fusion method is set automatically ...@@ -1458,7 +1459,7 @@ This parameter is used when the magnetometer fusion method is set automatically
</parameter> </parameter>
<parameter default="0" name="EKF2_MAG_TYPE" type="INT32"> <parameter default="0" name="EKF2_MAG_TYPE" type="INT32">
<short_desc>Type of magnetometer fusion</short_desc> <short_desc>Type of magnetometer fusion</short_desc>
<long_desc>Integer controlling the type of magnetometer fusion used - magnetic heading or 3-component vector. The fuson of magnetomer data as a three component vector enables vehicle body fixed hard iron errors to be learned, but requires a stable earth field. If set to 'Automatic' magnetic heading fusion is used when on-ground and 3-axis magnetic field fusion in-flight with fallback to magnetic heading fusion if there is insufficient motion to make yaw or magnetic field states observable. If set to 'Magnetic heading' magnetic heading fusion is used at all times If set to '3-axis' 3-axis field fusion is used at all times. If set to 'VTOL custom' the behaviour is the same as 'Automatic', but if fusing airspeed, magnetometer fusion is only allowed to modify the magnetic field states. This can be used by VTOL platforms with large magnetic field disturbances to prevent incorrect bias states being learned during forward flight operation which can adversely affect estimation accuracy after transition to hovering flight. If set to 'MC custom' the behaviour is the same as 'Automatic, but if there are no earth frame position or velocity observations being used, the magnetometer will not be used. This enables vehicles to operate with no GPS in environments where the magnetic field cannot be used to provide a heading reference. Prior to flight, the yaw angle is assumed to be constant if movement tests controlled by the EKF2_MOVE_TEST parameter indicate that the vehicle is static. This allows the vehicle to be placed on the ground to learn the yaw gyro bias prior to flight.</long_desc> <long_desc>Integer controlling the type of magnetometer fusion used - magnetic heading or 3-component vector. The fuson of magnetomer data as a three component vector enables vehicle body fixed hard iron errors to be learned, but requires a stable earth field. If set to 'Automatic' magnetic heading fusion is used when on-ground and 3-axis magnetic field fusion in-flight with fallback to magnetic heading fusion if there is insufficient motion to make yaw or magnetic field states observable. If set to 'Magnetic heading' magnetic heading fusion is used at all times If set to '3-axis' 3-axis field fusion is used at all times. If set to 'VTOL custom' the behaviour is the same as 'Automatic', but if fusing airspeed, magnetometer fusion is only allowed to modify the magnetic field states. This can be used by VTOL platforms with large magnetic field disturbances to prevent incorrect bias states being learned during forward flight operation which can adversely affect estimation accuracy after transition to hovering flight. If set to 'MC custom' the behaviour is the same as 'Automatic, but if there are no earth frame position or velocity observations being used, the magnetometer will not be used. This enables vehicles to operate with no GPS in environments where the magnetic field cannot be used to provide a heading reference. Prior to flight, the yaw angle is assumed to be constant if movement tests controlled by the EKF2_MOVE_TEST parameter indicate that the vehicle is static. This allows the vehicle to be placed on the ground to learn the yaw gyro bias prior to flight. If set to 'None' the magnetometer will not be used under any circumstance. Other sources of yaw may be used if selected via the EKF2_AID_MASK parameter.</long_desc>
<reboot_required>true</reboot_required> <reboot_required>true</reboot_required>
<values> <values>
<value code="0">Automatic</value> <value code="0">Automatic</value>
...@@ -1466,6 +1467,7 @@ This parameter is used when the magnetometer fusion method is set automatically ...@@ -1466,6 +1467,7 @@ This parameter is used when the magnetometer fusion method is set automatically
<value code="2">3-axis</value> <value code="2">3-axis</value>
<value code="3">VTOL customn</value> <value code="3">VTOL customn</value>
<value code="4">MC custom</value> <value code="4">MC custom</value>
<value code="5">None</value>
</values> </values>
</parameter> </parameter>
<parameter default="0.25" name="EKF2_MAG_YAWLIM" type="FLOAT"> <parameter default="0.25" name="EKF2_MAG_YAWLIM" type="FLOAT">
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment