Skip to content
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

Closed
wants to merge 45 commits into from

Conversation

DonLakeFlyer
Copy link
Contributor

  • PreArm duplicated messages are filtered such that they are spoken only if more than 10 seconds from last time spoken.
  • PreArm messages do not pop up a QGC message box
  • PreArm messages still show up in message dropdown
  • PreArm messages show up in the center of the flight map. If no PreArm message shows up again for 10 second it will be removed from the flight map.

@dagar Can you test this with PX4?

DonLakeFlyer and others added 30 commits May 7, 2018 11:51
Vehicle. Expose sensor status to Qml
…s an autopilot firmware that writes the respective health flags in the SYS_STATUS mavlink message
Ignore old version 1
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.
@DonLakeFlyer
Copy link
Contributor Author

@dagar Can you test?

@dagar
Copy link
Member

dagar commented May 18, 2018

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.

@dagar dagar self-requested a review May 18, 2018 18:33
@dagar
Copy link
Member

dagar commented May 18, 2018

Which MAV_SEVERITY do you think these should be?

@dagar
Copy link
Member

dagar commented May 18, 2018

I'm thinking about treating it differently if the check is done periodically vs as a result of the user requesting to arm.

@DonLakeFlyer
Copy link
Contributor Author

Rebase went bonkers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants