20190206 Dev Meeting

Agenda

General:

• Update from previous calls
  • AI @ALL - review RFC in #861 "Local and body frames" for next meeting.
• Tagged: issues, PR. A few choice items:
• Pymavlink#237: message CRC checksum is wrong when a mavlink_message_t is converted to a sending buffer - quick update.

HamishW

• Smart battery messages - additional faults, how does it live in context of BATTERY_STATUS?
• RC RSSI prior art
• Pymavlink mavschema: Add default and restricted attributes to params #258
• Doc Mission partial upload/download
• Add new PWM output message - #926

CHECK Status

• @JamesP and @MichaelS (or Lorenz/Thomas) to engage with Local and body frames and add comments. Discuss next week.
• @WickedShell File format discussion - Attempt to re-engage in next two weeks.

Notes

Call 1

• Discussion about adding a stalebot on issues. Some concerns, but agreed that it is something we can try and then review. see 1076

• Smart battery messages

  • Generally looking good. Add additional faults. Add clarification of when it is used (ie Battery>FC, FC>GCS). Clarify that it is used for smart batteries instead of BATTERY_STATUS.
  • Then get it in.

• RC channels RSSI definition does not match prior art

  • Agreed that changing range from [0-100], 256=not used to [0-255], 256=not used gives the greatest compatibility with existing systems, while still retaining the ability to declare something as not used.
  • Assumption is that real systems using old 0-256 range will never/rarely actually emit 256.
  • Probably the additional range of 0-256 over 0-100 is not in practical terms all that useful. Change is for compatibility reasons, not technical merit.
  • JamesP agreed change will be made to match in ArduPilot.
  • HamishW Action to create PR and then remind all involved after it goes in.

• Pymavlink mavschema: Add default and restricted attributes to params #258

  • discussed how to get it moving
  • Tagged James, and he will push it.

• Mission partial upload/download doc - Lorenz agreed to review.

• MOTOR_TEST service updates to common.xml - needs architectural reword. Discuss with Daniel.

• DISTANCE_SENSOR message: Fix covariance field - needs to be fixed in compatible way. Decision to modify as here

• Radio link information and settings related messages

  • Not sure if scales enough. Alternative to map to parameters.
  • See if they know about RADIO_STATUS
  • Do not need to get AP

• Discussed: Include RUST MAVLink libraries into MAVLink project

  • Suggestions, discuss with Dan Agar about any existing work being done.
  • Coordinate a call with proposers to find out their needs and plans - evaluate if this a path for support (including state of project, validation tools, etc.)

AI:

HamishW

• DONE: Smart battery messages - update as discussed and merge.
• IN PROG: PRS - RADIO_STATUS and 1083: Create PR for RC channels RSSI definition does not match prior art
• IN PROG: Coordinate meeting with Rust MAVLink team
• • IN PROG: Add new PWM output message - #926 - Push this along.
• MOTOR_TEST service updates to common.xml - see if can discuss with Daniel
• DONE: DISTANCE_SENSOR message: Fix covariance field - modify as per here
• DONE: Radio link information and settings related messages - Ask if they know about alternative messages. This is progressing.

Attendees

HamishW, LorenzM, JamesP, JulianO