Is your feature request related to a problem? Please describe.
The multimodule permits cloning of FrSky binding which means it is possible to have two transmitters set up for one set of models.
One TX is effectively a backup TX in case there is an issue with the master TX.
Describe the solution you'd like
General adjustments such as trim/rates/expo can be applied to TX models from time to time (normally on the master). What would be really useful would be to have a copy-over tool which allows the model settings from the master TX to be written to model settings of the backup TX so that the changes are aligned.
However - this copy-over must exclude binding details which differ between a normally bound TX (master) and a cloned TX (backup)
The details to be ignored and left intact on the backup TX are:
Subtype (comma separated enum for example 64,4 for FrSkyX2, LBT 8ch, versus 64,3 for FrSkyX2, Cloned)
OptionValue (RF Freq Fine Tune, which is hardware dependant)
Is your feature request related to a problem? Please describe. The multimodule permits cloning of FrSky binding which means it is possible to have two transmitters set up for one set of models. One TX is effectively a backup TX in case there is an issue with the master TX.
Describe the solution you'd like General adjustments such as trim/rates/expo can be applied to TX models from time to time (normally on the master). What would be really useful would be to have a copy-over tool which allows the model settings from the master TX to be written to model settings of the backup TX so that the changes are aligned.
However - this copy-over must exclude binding details which differ between a normally bound TX (master) and a cloned TX (backup)
The details to be ignored and left intact on the backup TX are:
where the module type is TYPE_MULTIMODULE