-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move ArduPilot PreArm handling to generic #6436
Conversation
Vehicle. Expose sensor status to Qml
Fix altitude change signalling
…s an autopilot firmware that writes the respective health flags in the SYS_STATUS mavlink message
Ignore old version 1
Implement GeoFence persistence
Automated preflight checklists
The LinkIndicator shows the connected links and lets the user select the priority link,
This setting enables/disables the LinkIndicator toolbar in which the primary link can be chosen.
Each link updates the active property based on incoming bytes. The vehicle tracks the active property of each link and in case of an inactive priority link it updates the priority link.
Add the HeartbeatTimer class to track a single heartbeat for a single link. For every new received heartbeat an instance of the class is created. Every instance emits a signal if it timed out or the timer is restarted. Each vehicle then decides based on all different signals which link is the priority link.
- Improve function names - For notifications of an active link change only show the priority keyword if multiple links are connected - Use QMap instead of QList for the HeartbeatTimers - Style improvements - Simplify sending the MAV_CMD_CONTROL_HIGH_LATENCY command
Show the link indicator in the tool bar if two or more links are connected and at least one of them is a high latency link. Show in the link indicator if a link is inactive.
minor typo fix
FactValueSlider: Fix crash when empty
Appveyor only has Qt 5.9.5
@dagar Can you test? |
Support for multiple links to a single vehicle
Great! I'll give it a try. Could we also do this for anything that contains "PREFLIGHT"? https://github.com/PX4/Firmware/blob/master/src/modules/commander/PreflightCheck.cpp#L131 On the PX4 side I'd still like to change them eventually, but that would get us through the transition. |
Which MAV_SEVERITY do you think these should be? |
I'm thinking about treating it differently if the check is done periodically vs as a result of the user requesting to arm. |
Allow DropPanel dynamic sizing
Show indicator for mission terrain data
Single bool to debug guided actions
Rebase went bonkers. |
@dagar Can you test this with PX4?