Arbitration¶
The arbitration algorithm in Autopilot 4x is based on a scoring system. Each autopilot must send continuously a set of arbitration variables that will be used by the arbiter in order to calculate the score for each unit. Then, based on the scores and the current arbitration mode, the arbiter will choose to keep the current selected autopilot, or switching to one of the other units.
A Score is a 32 bit, single precission, floating-point value with a range between 0 and 0xFFFFFFFF, where 0 is a perfect score. That is, the lower the value, the better the score.
Scores are calculated using the arbitration variables received from each autopilot at their dedicated addresses. After receiving the value, each variable is multiplied by their respective arbitration weight, and then it is used to compute the score for their respective unit.
Tip
The Arbitration weights should be used to increase or decrease the relevance that a certain arbitration variable has over the calculation of the score.
Any variable in Veronte can be used as an arbitration variable. Depending on the platform, operation, application etc. the more relevant variables can be selected for its use as arbitration references.
Config¶
Absolute Arbitration Variables¶
Absolute arbitration variables are indicators that are inherently good or bad, and so they are added directly to the score.
Examples of absolute arbitration variables are Link Quality, GNSS accuracy or warnings such as Sensors error or Position not fixed.
Relative Arbitration Variables¶
Relative arbitration variables are not inherently good or bad, and hence need to be compared against the other autopilots in order to calculate its score contribution.
The contribution to the score from a relative arbitration variable will be its Deviation from the Average of the same variable from each autopilot.
Examples of relative arbitration variables are Attitude, Position, measurements from sensors, etc.
Arbitration Example¶
Autopilot |
Var. Nº |
Veronte Variable |
Type |
Value |
Mean |
Deviation |
Weight |
Score |
Total Score |
---|---|---|---|---|---|---|---|---|---|
1 |
1 |
Roll |
Relative |
0.12 |
0.096 |
0.024 |
1 |
0.024 |
0.058 |
2 |
Pitch |
Relative |
0.30 |
0.283 |
0.017 |
1 |
0.017 |
||
3 |
GNSS 1 Accuracy |
Absolute |
1.7 |
0.01 |
0.017 |
||||
2 |
1 |
Roll |
Relative |
0.10 |
0.096 |
0.004 |
1 |
0.004 |
0.026 |
2 |
Pitch |
Relative |
0.28 |
0.283 |
0.003 |
1 |
0.003 |
||
3 |
GNSS 1 Accuracy |
Absolute |
1.9 |
0.01 |
0.019 |
||||
3 |
1 |
Roll |
Relative |
0.07 |
0.096 |
0.026 |
1 |
0.026 |
0.054 |
2 |
Pitch |
Relative |
0.27 |
0.283 |
0.013 |
1 |
0.013 |
||
3 |
GNSS 1 Accuracy |
Absolute |
1.5 |
0.01 |
0.015 |
In the above example, AP2 is considered to be the best, since it has the lowest score. Even though its GNSS accuracy is the worst of all 3, its values for pitch and roll are the ones with the lower deviation from the mean.
CAN Setup¶
Here users can configure the received CAN Ids for each one of the 3 possible Autopilots 1x that are sending data to Arbiter. Therefore, to send data from any of them to the Arbiter, these Ids must be specified.
Send status. The user can enable status sending and set a status message period.
Send score. Score sending can be enabled and a period of scoring messages can be set.
Status message ID. CAN ID to which Status and Score messages.
Extended. If enabled, the frame format will be this, ‘Extended’, i.e. with a 29-bit identifier. Otherwise, the frame format ‘Standard’ (11-bit identifier) is set by default.
CAN IDs used for the reception of autopilot 4x arbitration messages for each AP.
Extended. If enabled, the frame format will be this, ‘Extended’, i.e. with a 29-bit identifier. Otherwise, the frame format ‘Standard’ (11-bit identifier) is set by default.