20220330 Dev Meeting

Agenda

General:

• Update from relevant previous calls
• Tagged: issues, PR.

Agenda

• RFC 0018 - Improved Battery Status Reporting #19 + WIP smart battery messages #7 (dronecan)

  • General discussion/feeling
  • Cell voltages. Pain point is charging status.

• Add radius to DO_REPOSITION v2 - radius and speed? What do we think about the flag?

• Option to not reset non-configurable params in preflight storage - slight break - who uses this? OK in principle?

• MAV_TYPE_VTOL _DUOROTOR and _QUADROTOR renamed to new format #1818.

  • Break to fix - a good plan?

• common.xml: remove wip from AIS_VESSEL #1817

  • Julian, need comment

• 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"

• 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.

Follow ups

• MAV_WINCH_STATUS_CLUTCH_ENGAGED: clarify definition #1781
  • James to follow up with Randy if this is OK. NOt done yet.
• Document TIMESYNC protocol #433 - use cases - minor things to close this.
• Component information protocol - move into standard #1806
  • FYI only, are keeping the basics and schema component info.
• Rename and document parameter encoding protocol bits (Associated docs update)
  • Julian, did PX4 start emitting the flag?

Attendees: ? JulianO, Hamish, JamesP, Beat.