Peter Barker

> The benefit is that by separating out the CRCs, we can switch to a common implementation for them. There is a known taxonomy (see section 15 [here](https://www.zlib.net/crc_v3.txt)) and there...

There is scope here differences between how PX4 populates these fields and how ArduPilot populates these fields. We should make sure we're doing something similar, at least. We send a...

On Tue, 21 Oct 2025, Hamish Willee wrote: > OK, I think good to go @peterbarker - let me know if you're happy. Noting that the ArduPilot version will no...

> > Will need to cope with that problem in the autotest, you can add a parameter to wait_heading to send the attitude request through until the condition is met...

Let's not rush this one in. We run the risk of making a whole bunch of things no longer follow the spec, which is a little rude. For example, ArduPilot...

On Wed, 30 Jul 2025, Hamish Willee wrote: > @Davidsastresas agree with you on the RC/manual commands. The justification for having the range was that one computer goes down then...

> On Wed, 30 Jul 2025, Hamish Willee wrote: @Davidsastresas agree with you on the RC/manual commands. The justification for having the range was that one computer goes down then...

> One model I considered, which may be what you are thinking, is that instead of requesting a range each GCS requests for itself for exclusive or shared ownership. Problem...

> This helps preventing other software from attempting to use the serial ports while flashing a new firmware Does this break if MAVProxy currently has that port open?

> So just to be clear, this is to test the appetite for a modified https://mavlink.io/en/messages/common.html#GPS_RAW_INT with an instance number, and some (possible) future proofing? > > Note, I'm very...