Peter Barker

I'm not sure we need this patch; things seem to muddle along. I actually like having these as separate numbers as it makes clear there's something askew. @Ryanf55 did you...

Looks likely. Commit message should be `AP_MSP:`, not `fix:`. Want to fix that or shall I?

They key thing here is that there's an ID field - that's good! If we had an ID field in `GLOBAL_POSITION_INT` we wouldn't need this message :-) Currently ArduPilot uses...

On Wed, 7 May 2025, Hamish Willee wrote: > Can't we add an id to GLOBAL_POSITION_INT? No, as extension fields aren't (a) necessarily transported.... and (b) understood by all clients...

> Anything else? Not that I can think of right now; if you can patch this I can take it to an ArduPilot DevCall to see what other people think.

On Tue, 20 May 2025, Hamish Willee wrote: > Do we want to do this here? Specifically, say we emit both this message and GPS_RAW_INT - should they be mappable?...

> On Tue, 20 May 2025, Hamish Willee wrote: Do we want to do this here? Specifically, say we emit both this message and GPS_RAW_INT - should they be mappable?...

On Wed, 6 Aug 2025, Tim Tuxworth wrote: > eg. is wrong So it seems. Odd, as I thought I'd read something recently which said the way I've always put...

Ping @bugobliterator - review was given on this one

``` Board AP_Periph blimp bootloader copter heli iofirmware plane rover sub CubeOrange-periph-heavy * Durandal * * -8 -8 -8 -8 * Hitec-Airspeed * KakuteH7-bdshot * * 0 0 0 0...