20180918 Dev Meeting
Hamish Willee edited this page Sep 20, 2018
·
7 revisions
General:
HamishW:
- Redirect mavlink.org to mavlink.io. Maintenance a pain.
- James had quite a lot of things to check with ArduPilot community. Would be good to know the result.
- Would quite like to deprecate mavlink.org and redirect on per-message basis to the new site. Is it to a state where this is acceptable to ArduPilot community?
- Lorenz - per-message versioning follow up.
- MAV_FTP, PLAY_TUNE, PWM_OUTPUT_STATUS message: restructure as array, File Formats - who driving forward?
- Would like to know how ranges are allocated for message and enum entry ids in common vs dialects: https://github.com/mavlink/mavlink-devguide/pull/96
-
Attendees agreed that mavlink.org should redirect to mavlink.io to reduce confusion for end users.
-
Reviewed and mostly closed tagged Dev Call issues
- #967 Proper deprecation of DO_DIGICAM_CONFIGURE and DO_DIGICAM_CONTROL - Update to call "fallback" rather than deprecated (is used in ArduPilot production). Hamish to do.
- #917 Covariance - Not perfect but acceptable to group. OK but needs to be rebased.
- #907 Create BATTERY_INFO to communicate smart battery info. - Closed - not sufficiently "generic"/well thought out.
- #861 Local and body frames - good RFC. Team to review for next meeting.
- @734 common.xml: added message DEBUG_ARRAY - Some suggested improvements.
- #973 Ideas for working out what messages are supported - No easy solutions, but test suites a step in the right direction - especially for future work.
-
File Formats were discussed
- Agreed that file format should include planned simple command info for complex items (so the a system can execute plan even as fallback even if it doesn't understand the complex definition). Complex info needs to be kept to remain as it is useful for visualising even on systems that can't plan.
- Hamish to update this requirement somewhere so it can be discussed. Lorenz to discuss/share with Don.
-
Lorenz and James have open AIs/discussion from previous weeks. Aim to try move some of these along for discussion next meeting.
-
Lorenz interested in people who might have bandwidth to be involved in test suite specification and implementation.
- AI @Lorenz to redirect mavlink.org to mavlink.io
- AI @Hamish to fix up #967 to be "fallback" API. Done: (actually, defined text, but handballed back to Amilicar)
- AI @ALL - review RFC in #861 "Local and body frames" for next meeting.
- AI @Hamish write up requirement for File Formats: Done: #989
- AI @Lorenz to share File format discussion with Don.
Parameter instances Eg: having many estimators running at the same time, all working on the same parameter but different instance Proposed solution: Extension field for parameters
- AI @AlexKlimaj to update #907 based on feedback from group