Andrew: Let’s wait for Pete Hall to give another go.
UTC0714
UTC0716
Merged!
UTC0721
Randy: Since the default is going to be zero, users with more than one gimbal will see change in behaviour. Peter: Have we supported multiple gimbals for long? R: We did, then we stopped, then we brought them back.
Merged!
UTC0727
Peter: When would you use GPS_AUTO_CONFIG=3? Sid: It will reset the module to defaults.
Then it will fall back to 1 then.
Peter: It would be nicer if we had a MAVLink command to support this. S: We would also need to support this command over DroneCAN.
Then when we eventually remove it, we can have it convert to 1.
P: How big would we need to make the write buffer to avoid having the parallel valget parser? S: It wouldn’t need to be that big, we probably don’t need to fit all the parameters in it. P: What if we batched those changes and processed only enough to fit in that buffer? And avoid the additional parsing. S: It could be lots of parameters, but typically it’s 5-7. Maybe we could fit 10? Or more?
It’s in the _processing_cfg struct.
A: This feature is quite big. Lots of boards won’t build anymore.
We could have RXM raw logging disabled by default.
S: You could use it for PPK. A: Unfortunately if you turn the feature off the board doesn’t build.
We want this in 4.7, but we could have it disabled by default.
S: We could have it enabled in the boards that can fit it. P: If you can do away with the parallel parser, you’ll probably save several K of flash.
S: We can turn of RXM raw in boards without FPV cards. A: Minimized boards as well. P: When you disable it, the config structure goes from 2.5kB to 280.
A: How do you test these changes? P: I add the updated module on master, build it, etc…
We are double-using also this message to optionally do evil stuff during boot upon sending magic numbers. So we probably need a new message to fit those.