-
Notifications
You must be signed in to change notification settings - Fork 1.9k
20221207 Dev Meeting
Hamish Willee edited this page Dec 7, 2022
·
7 revisions
General:
- Update from relevant previous calls
- Tagged: issues, PR.
-
message_definitions: add all_with_development.xml #1924 - how we progress
- Prefer not to modify the XML but use the WIP tag properly.
- AO: JamesP to talk to PeterB.
- AO: HamishW to close issue. Done
- HW added note to https://github.com/ArduPilot/pymavlink/pull/240
-
Proposal for mavlink radio links & receivers: Concept and set of new messages
- Yes, needs to be revisited.
- All the radio systems have quite distinct management information.
- Might not be a popular choice but perhaps they all need their own status messages.
- At least some "generic LQ" indicator for QGC display desirable.
- For configuration, might be worth doing with a parameter configuration UI a'la camera definition files.
-
COMPONENT_INFORMATION_BASIC- software/hardware version as int #1930
- extra serial number - display vs predict
- We see value, but where do you stop.
- Propose formatting value.
- custom name
- Consider it if Ollie willing to upstream to at least QGC and Mission Planner
- extra serial number - display vs predict
FYIs
-
Extend MAV_CMD_NAV_VTOL_TAKEOFF #1875 - FYI closed and asked for new "clean" version.
-
Airspeed message: update #1900 -
- James still needs to talk to Peter.
-
changes to standard flight modes #1915
- How do we handle overrides of standard modes on a companion.
- Note This is possible only if the override is compatible with the "standard mode description".
- Still in discussion.
Did not discuss:
-
Prearm command - what's the risk
- accidentally disarming. So the command definition should specifically be "can only do from disarmed".
- In very first use, motor attached to servo.
Attendees: Hamish, JamesP, JulianO