20220330 Dev Meeting
Hamish Willee edited this page Mar 30, 2022
·
6 revisions
General:
- Update from relevant previous calls
- Tagged: issues, PR.
-
RFC 0018 - Improved Battery Status Reporting #19 + WIP smart battery messages #7 (dronecan)
- Sounds good - pretty aligned
- Cell voltages:
- Batteries cells usually iterate/index in sets of 12, so use that rather than 10
- No need to truncate - it's a developer message. Keep it simple and clean.
- BATTERY_STATUS v2 - Looks good.
- No particular way to manage change - leave that to the flight stacks.
-
Add radius to DO_REPOSITION v2 - radius and speed? What do we think about the flag?
- Flag is horrible, as is using negative radius for direction. Keep yaw for direction.
- DONE AO Add comments/suggestions.
-
Option to not reset non-configurable params in preflight storage - slight break - who uses this? OK in principle?
- Its not really a break - the original was weakly specified and the "clear everything" case would actually never be desired.
- But we'd like an option with proper explanations of how this works.
- DONE AO Add not to this effect.
-
MAV_TYPE_VTOL _DUOROTOR and _QUADROTOR renamed to new format #1818 - OK to break to fix
- Yes, but check with JamesP. [Waiting]
-
Seq in message header is useless...
- Whats it for? Duplicate message detection and detecting drops.
- Doesn't detect drops with routing.
- Better way to detect packet drops?
- OK for me to add note that this is to allow duplicates to be dropped and that it can only be used for packet loss on systems where all packets are routed between the endpoints?
- We probably need a register for this kind of stuff - "MAVLink 3 general improvement breaks"
- AO add documentation.
Did not cover:
- From above ... remove wip or/deprecate LINK_NODE_STATUS?
- Marked as WIP and streamed in PX4 here
- Argument to deprecate is that it doesn't work in routed configs as the whole sequence number approach is broken.
- Argument to remove WIP is that it is deployed.
Attendees: JulianO, Hamish, LorenzM