-
Notifications
You must be signed in to change notification settings - Fork 1.9k
20200429 Dev Meeting
General:
- Update from relevant previous calls
- Tagged: issues, PR.
-
DONE Set and Get WiFi configuration, adding new fields and enums in the pr… #1362
- We're OK with changes, but need to make sure that extensions default to 0, and that 0 is a valid entry meaning do nothing if sent by a system that does not understand the new message and received by one that does. Also sending password in plaintext. Commented
-
Apologies to Joe - Lorenz not present. Joe will need to proceed with hacky solution on the large number of vehicles.
-
XML Schema Issue
- Thanks to Joe for fixing
- AO James to follow up on fixes to CI to prevent this in future.
-
Component Id for a companion computer #1344
- Component IDs belong to the process. So each ROS node should emit its own. Some inconsistencies.
- DONE AO HamishW to (add comments](https://github.com/mavlink/mavlink/issues/1344)
-
Proposal for ultimate and fully backwards compatible solution to protocol pain points
- Added note for Tridge who had lots to do with MAVLink 2 spec. JamesP to follow up.
- Rest of team said TL;DR (for now)
-
Stalebot - general complaints that not necessary with small number of issues. Request from Hamish for team to review older ones and see if any can be closed - " Share the load"
-
Using Component Information to query autopilot support
- Status update HamishW
- Need to add hash to query message, and support per-metadata query.
- Need to assess if the info in the query message is useful, or should be metadata as well.
- Cannot direct replace camera info query message because it has defaults that are useful. But we can use the component info as well.
- Either XML and Json can be supported on a per-metadata basis. We should standardise on Json to make Don happy but allow camera API to query and get back XML. NOte that we can't drop the old message for camera API entirely, as that gets the default set of information that any camera supports.
- Don is looking into parameter metadata standard. Still working on best way to support localisation.
- Julian going to submit proposal PR for the component message changes by next meeting. Also the mission JSON.
- Status update HamishW
-
James P noted that we can change the meeting time for Lorenz if he needs us to, in order to attend. Hamish to let Lorenz know.
Attendees: HamishW, JulianO, JonasV, Bazooka Joe, JamesP