20210721 Dev Meeting
Hamish Willee edited this page Jul 22, 2021
·
6 revisions
General:
- Update from relevant previous calls
- Tagged: issues, PR.
-
Fence Altitude and Entry / Exit Times -
- Yes we like the idea, but current idea for implementation is overly constrained. Floor and ceiling should be considered. Perhaps consider the new fence action approach. Also "corridors", cones, etc.
- DONE AO HamishW to capture discussion in the issue.
-
Is COMPONENT_INFORMATION still WIP ? #1656 - what is outstanding?
- Translation discussion is ongoing. Should remain WIP for now.
-
Fix up enum generation - reminder. James still considering best way forward for this, but understands its importance.
-
- We don't love the name. However as long as the fields are updated to be bigger we can merge into development.xml.
- Done AO: HamishW to update requirement (and merge once changes are made)
-
commom.xml: add FUEL_TANK #1659 - anything else we can add?
- ArduPilot addressed this use case with a fuel level sensor that mapped to a battery message: https://github.com/ArduPilot/ardupilot/pull/11951. It was recognised that this wasn't as intuitive for users as a FUEL message but made the code a whole lot easier.
- More discussion required in PX4 community to see if this is desired - might be similar workaround would be better.
- DONE AO hamish to follow up.
Not discussed:
-
VTOL Safe Area - RomanB
- Check romanB created issue. Also JamesP was to follow up with ArduPilot to get more feedback.
- MAV_CMD_PAYLOAD_CONTROL_DEPLOY, MAV_CMD_PAYLOAD_PREPARE_DEPLOY, MAV_CMD_NAV_PAYLOAD_PLACE confirm whether https://github.com/mavlink/mavlink/pull/1648 can go in.
- TIMESYNC - Follow up with Julian - Old PR closed - did you plan on opening new one to follow up?
Attendees: JulianOes, JamesP, Seb, HamishW,