20200819 Dev Meeting

Agenda

General:

Only 2 attendees.

PARAM_EXT_TRIMMED: supported or not, how to know and what to do #1449 and PARAM_EXT_TRIMMED: move fields to even more optimize for zero byte truncation #1447
- Protocol bit for support for EXT/_EXT trimmed makes sense as makes it easy for systems to understand if new messages can be used.
- No real need for second protocol bit for ext vs trimmed; a GCS that supports one must support both. A system can support either, but not sense not to support the trimmed version.
- For same reason no need for specific "TRIMMED" read methods.
- Further reorder looks very sensible.
mavgen.py: correct handling of includes (updated) #436
- James asked again. No progress in review.
Deprecate old camera control and do camera trigger messages and use new API. Comes out of https://github.com/PX4/px4_user_guide/pull/781/files#r469053481 - also discussion from Don on slack: https://px4.slack.com/archives/C52DXKYLV/p1597784756109500
- JamesP. New API does not do everything necessary from old API so can't be deprecated yet.
- General agreement that for new API to replace old API it must be possible to do the same things, and that you should not have to implement the XML to do those same things.

Things we did not discuss:

File-based protocols for params, missions, etc - Next steps Lorenz?
Hamish using with pymavlink with dialects
#1166 Add helper function for routing - Ollie Points
- Incompatibility flags to indicate target address field presence (and remove from payload). - why/costs/benefits?
- Can we separate out CRC somehow into valid message vs corrupt message?

Attendees: HamishW, JamesP