This implements the validation of the operator ID as required for the EU remote ID spec.
The way it works is that:
1. The user enters the operator ID including the checksum and secret.
2. The ID is validated using the secret against the checksum.
3. The secret is removed and the public ID is saved, as well as a flag signalling that the ID has been checked.
This work is sponsored by bluemark.io., https://github.com/BluemarkInnovations.
Signed-off-by: Julian Oes <julian@oes.ch>
* Correct FMUv6x-RT ProductID
Change FMUv6x-RT ProductID to 29 to match PX4 Firmware
* Update src/VehicleSetup/FirmwareUpgradeController.cc
Change the FMU v6xrt Board_ID to 35.
---------
Co-authored-by: David Sidrane <David.Sidrane@Nscdg.com>
when clicking back button screen from any tool, it would go blank and
then it would collapse, because the loader was being emptied before the
drawer containing it closed completely
For some reason in mobile the button would keep as hovered
even if it is not pressed, so it was weird. This way it
makes more sense for mobile, the UI is consistent with
what is happening
For some reason in mobile the button would keep as hovered
even if it is not pressed, so it was weird. This way it
makes more sense for mobile, the UI is consistent with
what is happening
This defaults to the most obvious way to turn (shortest direction) from
commit Mission item: CONDITION_YAW - added shortest direction.
This behaviour when changing directions is what users are familiar with
from any simple mission flight (that RPAS turns the shortest way toward
the target)
This defaults to the most obvious way to turn (shortest direction) from
commit Mission item: CONDITION_YAW - added shortest direction.
This behaviour when changing directions is what users are familiar with
from any simple mission flight (that RPAS turns the shortest way toward
the target)
The map scale width changes when the zoom up/down buttons are clicked.
When buttons are on the right, and when the user quickly clicks a zoom
up/down button several times, the first click change the scale, which
changes the buttons position. Subsequent clicks are most of the time not
where the user wanted to put them.
Putting buttons on the left of the scale will keep them at a fixed
position, fixing this unfortunate behavior.
Signed-off-by: Julien Olivain <ju.o@free.fr>
This points the GPS/Drivers submodule to a commit in the qgc-4.3 branch,
just backporting the fix required to get F9P working.
Signed-off-by: Julian Oes <julian@oes.ch>
Ultimately it sends a MAV_CMD_DO_CHANGE_SPEED in meters
per second, so it is clearer if we have this name for the
function, could help avoiding confusion in the future
Marek S. Łukasiewicz
Don Gagne
Julian Oes
Vincent Poon
davidsastresas
André Kjellstrup
Junwoo Hwang
Julien Olivain
Christian Rauch
jnomikos
Nick Exton
PX4BuildBot