Difference between revisions of "Module/collective tracking control"
(→Usage) |
(→Usage) |
||
| (10 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
<categorytree style="float:right; clear:right; margin-left:1ex; border: 1px solid gray; padding: 0.7ex;" mode=pages>Modules</categorytree> | |||
== Introduction == | == Introduction == | ||
This module/algorithm allows a team of aircraft (they can fly at different speeds) to track a ( | This module/algorithm (paper with the details at https://arxiv.org/abs/1810.00182) allows a team of aircraft (they can fly at different speeds) to track a target. This target can be a fixed waypoint, or a moving target (another vehicle). From the ground station you can fake a moving vehicle in order to have a moving waypoint. In particular, the centroid of the team converges to the target as it is shown in the following screenshots. | ||
[[File:Ctc mission.png|center]] | [[File:Ctc mission.png|center|1400px]] | ||
At t=90 secs, the aircraft are just orbiting around a waypoint before the algorithm starts. At t=420 secs the centroid almost converge to the target's position. The other screenshots show the centroid of the formation tracking the moving target. The velocities of the aircraft were between 10 and 16 m/s. The target was moving between 2 and 4m/s. | |||
== Custom messages == | == Custom messages == | ||
| Line 9: | Line 13: | ||
The module needs all-to-all communication (including the target). The following messages need to be included in your messages.xml. | The module needs all-to-all communication (including the target). The following messages need to be included in your messages.xml. | ||
These messages go in the telemetry section of messages.xml. The CTC_CONTROL message is just for telemetry porpuses. | These messages go in the telemetry section of messages.xml. The CTC_CONTROL message is just for telemetry porpuses, if you want it, do not forget to add the corresponding entry in the telemtry file. | ||
<source lang="html"> | <source lang="html"> | ||
| Line 57: | Line 61: | ||
== Usage == | == Usage == | ||
Add the module in | Add this module in the target's flightplan (if you want to track a fixed waypoint, you can skip this module) | ||
<source lang="html"> | |||
<modules> | |||
<module name="collective_tracking_control_target"/> | |||
</modules> | |||
</source> | |||
Add this module in the flightplan of each aircraft (no the target) | |||
<source lang="html"> | <source lang="html"> | ||
<modules> | <modules> | ||
<module name="collective_tracking_control" | <module name="collective_tracking_control"/> | ||
</modules> | </modules> | ||
</source> | </source> | ||
You need to define the neighboring relations of the aircraft. To do so, after you power up all the autopilots, you need to set an internal table by sending a series of commands with the help of the Python script ./PAPARAZZI_HOME/sw/ground_segment/python/collective_tracking_control/ | You need to define the neighboring relations of the aircraft. To do so, after you power up all the autopilots, you need to set an internal table by sending a series of commands with the help of the Python script ./PAPARAZZI_HOME/sw/ground_segment/python/collective_tracking_control/ctcInitTables.py . You must pass two arguments, the first one is an integer with the ID of the target, the second one a .txt file with the IDs of the rest of the aircraft. This script also resets the algorithm in case you want to start it over during the flight. | ||
The target will be broadcasting its position and velocity all the time. However, the rest of the aircraft will run the algorithm only if we tell them so | The target will be broadcasting its position and velocity all the time. However, the rest of the aircraft will run the algorithm only if we tell them to do so. Hence, you must call the algorithm from the corresponding navigation block. You have three options: | ||
The team will track a moving vehicle. This vehicle can be faked from the ground control station for a moving waypoint. | |||
<source lang="html"> | <source lang="html"> | ||
<block name="Collective tracking control"> | <block name="Collective tracking control"> | ||
<call fun=" | <call fun="collective_tracking_vehicle()"/> | ||
</block> | </block> | ||
</source> | </source> | ||
== Tuning the gains, Python | The team will track a waypoint | ||
<source lang="html"> | |||
<block name="Collective tracking control"> | |||
<call fun="collective_tracking_waypoint(WP_YOUR_WAYPOINT)"/> | |||
</block> | |||
</source> | |||
The team will track a XY point w.r.t. the HOME waypoint | |||
<source lang="html"> | |||
<block name="Collective tracking control"> | |||
<call fun="collective_tracking_point(x, y)"/> | |||
</block> | |||
</source> | |||
== Tuning the gains, Python simulation == | |||
The algorithm needs some parameters and gains to be set. The following Python simulation considers realistic orders of magnitude for distances and ground speeds. So you can try the gains and see the expected behavior of the algorithm before trying it in Paparazzi. | The algorithm needs some parameters and gains to be set. The following Python simulation considers realistic orders of magnitude for distances and ground speeds. So you can try the gains and see the expected behavior of the algorithm before trying it in Paparazzi. | ||
| Line 90: | Line 116: | ||
</exceptions> | </exceptions> | ||
</source> | </source> | ||
[[Category:Modules]] | |||
Latest revision as of 02:49, 12 November 2019
Introduction
This module/algorithm (paper with the details at https://arxiv.org/abs/1810.00182) allows a team of aircraft (they can fly at different speeds) to track a target. This target can be a fixed waypoint, or a moving target (another vehicle). From the ground station you can fake a moving vehicle in order to have a moving waypoint. In particular, the centroid of the team converges to the target as it is shown in the following screenshots.
At t=90 secs, the aircraft are just orbiting around a waypoint before the algorithm starts. At t=420 secs the centroid almost converge to the target's position. The other screenshots show the centroid of the formation tracking the moving target. The velocities of the aircraft were between 10 and 16 m/s. The target was moving between 2 and 4m/s.
Custom messages
The module needs all-to-all communication (including the target). The following messages need to be included in your messages.xml.
These messages go in the telemetry section of messages.xml. The CTC_CONTROL message is just for telemetry porpuses, if you want it, do not forget to add the corresponding entry in the telemtry file.
<message name="CTC" id="37">
<field name="table" type="int16[]"/>
</message>
<message name="CTC_INFO_FROM_TARGET" id="40">
<field name="px" type="float"/>
<field name="py" type="float"/>
<field name="vx" type="float"/>
<field name="vy" type="float"/>
</message>
<message name="CTC_CONTROL" id="211">
<field name="v_centroid_x" type="float" unit="m"/>
<field name="v_centroid_y" type="float" unit="m"/>
<field name="target_vx" type="float" unit="m/s"/>
<field name="target_vy" type="float" unit="m/s"/>
<field name="target_px" type="float" unit="m"/>
<field name="target_py" type="float" unit="m"/>
<field name="ref_px" type="float" unit="m"/>
<field name="ref_py" type="float" unit="m"/>
</message>
<message name="CTC_INFO_TO_NEI" id="255">
<field name="vx" type="float"/>
<field name="vy" type="float"/>
<field name="px" type="float"/>
<field name="py" type="float"/>
</message>
These messages go in the datalink section of messages.xml. They are necessary to init the algorithm from the ground control station.
<message name="CTC_REG_TABLE" id="160" link="forwarded">
<field name="ac_id" type="uint8"/>
<field name="nei_id" type="uint8"/>
</message>
<message name="CTC_CLEAN_TABLE" id="161" link="forwarded">
<field name="ac_id" type="uint8"/>
</message>
Usage
Add this module in the target's flightplan (if you want to track a fixed waypoint, you can skip this module)
<modules>
<module name="collective_tracking_control_target"/>
</modules>
Add this module in the flightplan of each aircraft (no the target)
<modules>
<module name="collective_tracking_control"/>
</modules>
You need to define the neighboring relations of the aircraft. To do so, after you power up all the autopilots, you need to set an internal table by sending a series of commands with the help of the Python script ./PAPARAZZI_HOME/sw/ground_segment/python/collective_tracking_control/ctcInitTables.py . You must pass two arguments, the first one is an integer with the ID of the target, the second one a .txt file with the IDs of the rest of the aircraft. This script also resets the algorithm in case you want to start it over during the flight.
The target will be broadcasting its position and velocity all the time. However, the rest of the aircraft will run the algorithm only if we tell them to do so. Hence, you must call the algorithm from the corresponding navigation block. You have three options:
The team will track a moving vehicle. This vehicle can be faked from the ground control station for a moving waypoint.
<block name="Collective tracking control">
<call fun="collective_tracking_vehicle()"/>
</block>
The team will track a waypoint
<block name="Collective tracking control">
<call fun="collective_tracking_waypoint(WP_YOUR_WAYPOINT)"/>
</block>
The team will track a XY point w.r.t. the HOME waypoint
<block name="Collective tracking control">
<call fun="collective_tracking_point(x, y)"/>
</block>
Tuning the gains, Python simulation
The algorithm needs some parameters and gains to be set. The following Python simulation considers realistic orders of magnitude for distances and ground speeds. So you can try the gains and see the expected behavior of the algorithm before trying it in Paparazzi.
You can find the Python simulation at ./PAPARAZZI_HOME/sw/ground_segment/python/collective_tracking_control/ctc_simulation.py
WARNING
This algorithm commands roll angles for the aircraft and NO waypoints. If one aircraft stops receiving information from the other aircraft, then it will not update its roll angle and it might continue flying straight. Be sure to set safety measurements in your flight plan, for example:
<exceptions>
<exception cond="dist2_to_home > (max_dist_from_home*max_dist_from_home)" deroute="STAND_BY"/>
</exceptions>