ES-Alexander

> a PR to generate the page would be good Initial files are now available for the ≥ 4.0 tags in the [parameters repository](https://github.com/ArduPilot/ParameterRepository/) :-) They'll still need some re-jigging...

> sorry its taken me so long to get back to this I get it - unfortunately the list of interesting/useful things to do seems to grow much faster than...

Just got around to this. > 4.6 is about to drop...so master only will be fine Here ya go 🙂 [MultiVehicle_master_MAVLink_Messages_Nov-5.zip](https://github.com/user-attachments/files/17621527/MultiVehicle_master_MAVLink_Messages_Nov-5.zip) > the params repo does not even have files...

> PR for wiki inclusion...[ArduPilot/ardupilot_wiki#6379](https://github.com/ArduPilot/ardupilot_wiki/pull/6379) Nice! Thanks for adding those in :-) > ... had to reformat a few things in the files. The generated files? If so, do you...

I have a vague recollection I made those the same on purpose, with the idea they'd be replaced automatically as part of the version selection support. That said, I may...

In general that probably makes sense :-) I was thinking of this mostly as versions where we can say "this is broken enough that people will almost certainly not want...

Ahh, I was forgetting that because it's a new device type it'll need a `generate/templates/omniscan450.py.in` file, so it's a bit more work than just running the generation process.

We'd need to add an API endpoint for loading an image (like we do [in version-chooser](https://github.com/bluerobotics/BlueOS/blob/master/core/services/versionchooser/utils/chooser.py#L79)), which then `import`s it into docker, before doing the normal custom extension registration process....

It may also be worth exploring custom theming via vuetify, rather than the current CSS overrides approach.

@Williangalvani said (internally) > It smells like MAVLink routing to me. > I think a good start is to set up 3 streams and check if the heartbeat rate in...