Provide an option for a sequential parameter fetching or caching in a multi-vehicle configuration to avoid network saturation at the startup

[slovak194]

Feature Description

What problem does it solve?

For a multiple-vehicle configuration, if all of them advert to QGC simultaneously (connecto to mavlink-router, which already has all of them connected) - parameter fetching overwhelms the network. Some vehicles may not be recognized at all, as the process of fetching params times out.

What does it do?

Fetch parameters one by one. If one fetching is already in progress, put the other into the queue, or postpone with the use of some kind of mutex.

Are there other systems that have this feature?

Pretty much every real-world multi-vehicle system with a limited bandwidth links is affected by this.

What communication/integration standards does the feature rely on (e.g. MAVLink commands etc)

Standard MAVlink 2.

To be noted:

• Links are NOT high latency. They are of a low latency and relatively low bandwidth.
• This issue could also be solved by providing a caching (or preloading) mechanism for parameters if the vehicles to be connected are all the same every time.

Flight Stacks

IFlight Blitz H7 Pro

Vehicle Types

Multicopter