Differences

This shows you the differences between two versions of the page.

--- vrm_portal:remote-veconfigure [2021-12-08 10:39] – [3. Step by step procedure] mvader
+++ vrm_portal:remote-veconfigure [2023-05-15 14:18] (current) – mvader
@@ Line 23: / Line 23: @@
   * To Remote VEConfigure a system connected to the GX device via a VE.Bus to VE.Can interface, as was done in old Hub-1 systems, this interface cable needs to run firmware version v2.05 or higher. If necessary, first update that interface cable with the [[vrm_portal:remote-firmware-update|Remote firmware update feature]].
   * This (new) way of Remote VEConfigure replaces the previous mechanism, that used VE.Power Setup. See [[ccgx:ccgx_ve_power_setup|here]] for the manual of the old procedure. Note that, once updated to the new Venus version, it is no longer possible to use the old procedure.
+  * The system protects against accidentally sending settings from one system to another. To that purpose, it will compare the serial numbers of the installed inverter/chargers against the serial numbers in the configuration files. There is one exception:
+  *  For systems consisting of multiple inverter/chargers, it is possible to replace a unit without having to do a full reconfiguration: step (1) make sure to, after commissioning a new system, always make and have a .rvsc file on archive. step (2) in case a unit failed, replace that by a new one. step (3) update the new unit to the same firmware version as the rest of the system. A full archive of older firmware versions is [[https://updates.victronenergy.com/feeds/VEBus/firmware-archive/ |available here]]. step (4) open that old .rvsc file and use the VRM Remote VEConfigure write settings feature to send that archived configuration. While writing the settings, the mechanism accepts up to one exchanged serial number and will automatically and silently take care of that. Note that in case you don’t have a file on archive, try to make a backup before taking the failed unit out of the system. In many cases a failed unit can still communicate. This feature requires Venus OS v2.62 or later to be installed on the GX device.
 In some cases the VE.Bus system will momentarily switched off when changing the configuration.