20230201 Dev Meeting

General:

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

Notes

• Extend cellular_status msg and add new nic_info msg for static fields #1945

  • Discussion broadly captured in https://github.com/mavlink/mavlink/pull/1945#issuecomment-1412784579

• Extend landing target msg and MAV_FRAME support #1943

  • Need to change the addition to MAV_FRAME - it is inconsistent and that enum is a pain point.
  • We need more review from domain experts - requested.
  • This cannot wait on the MAVLink process because it will delay your project.
    • Please fork and start development
    • Continue discussion on PR to get best possible messages.
  • Added comment in https://github.com/mavlink/mavlink/pull/1943#issuecomment-1412803889

• mavlink_msg_xxx_decode by mavgen_c does not handle extensions of message properly #684 - pymavlink bug fix

  • AO JamesP to see if we can get review from PeterB.

• COMPONENT_INFORMATION_BASIC- software/hardware version as int #1930

  • Could format the field. We think this is over complicating. Accept PR with the enum value.

• message_definitions: add all_with_development.xml #1924

  • AO: JamesP to talk to PeterB to get movement on https://github.com/ArduPilot/pymavlink/pull/240

Not discussed

• 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, JonasPerolini, Mo akkawimo,