Originally Posted by Mikenat
There is a choice of AGM or Lithium in a Magnum so interesting…why not have a choice in the Vega?
So the Vegatouch communicates with the Magnum (and vice versa) via RV-C which is a CAN based network protocol.
Magnum also has its own more basic network called MagNet that supports the Magnum Remote control, battery monitor kit and other accessories.
The interface for the Magnum that gateways MagNet to RV-C (and vice versa) is a little black box called an ME-RVC. The ME-RVC is built into the MSH models but is a separate box on the older models like my MS2812.
The RV-C spec fully supports a setting for Lithium batteries. Any newer Magnum remote or ME-RVC with an "L" designation supports Lithium settings as well.
So if RV-C supports Lithium and Magnum supports Lithium, what's left? Firefly. The Vegatouch software will need modification to add the Lithium choice and send the proper code to the ME-RVC over the RV-C.
Firefly may not have implemented the Lithium setting yet because the Magnum Lithium support may be fairly recent. What happens if a Lithium command is sent to an ME-RVC that is not an "L" version and doesn't know how to do that?
Also note it is the Remote or ME-RVC that remembers the configuration and constantly transmits the settings to the Inv/Charger over MagNet. Disconnecting the Remote/ME-RVC from MagNet will cause the Inv/Charger to revert to basic default settings.
There is another thread on the Entegra forum discussing bypassing the Vegatouch with a standard Magnum Remote which has more configuration capability than the Vegatouch has implemented.
This would disable configuring the Magnum from the Vegatouch but potentially still allow the Vegatouch to display status info.
I have an ME-RVC-L and ME-RC remote and have tested this on my MS2812 and it works. No I don't have a Vegatouch but I do have an equivalent and have proven the Magnum ME-RC remote will operate normally while an ME-RVC is also present on the MagNet. The ME-RVC continues to broadcast status info about the Magnum to the RV-C network. The configuration comes from the ME-RC Remote.
The question is if the behavior will be the same on the MSH models. The MSH manual states the Remote would take configuration precedence over the ME-RVC. Someone with that setup will need to test it.