This feature allows remotely updating the firmware of Victron inverter as well as inverter/charger. Applicable to systems that have a GX device installed, and being internet-connected to the VRM Portal.
The inverter/charger is the heart of a Victron power system. Also, certain types of installations require extra preparations. Therefore, before continuing, make sure to fully understand the process.
This procedure includes migration of the settings.
There is no limitation on the type of system: single unit systems, parallel, split-phase, three-phase and also large systems of 6, 9 and more inverters can all be updated remotely using this feature.
An AC-Coupled PV-Inverter is a PV Inverter connected to the AC out of the Victron Inverter.
To make sure no overcharging occurs, disable AC-Coupled PV Inverters. For example by having someone local to the system disconnect its solar input, or if it has an on/off switch: switch it off. Alternatively, perform the firmware update when the sun is down, in the evening or night.
The reason for having to do this is that the system will start-up while configured in factory defaults, and then doesn’t regulate PV Inverter output to manage the charging.
It is not possible to update a VE.Bus inverter, or inverter/charger in case there is also a VE.Bus BMS or Digital Multi Control (DMC) connected to the VE.Bus network.
Error 734, “Cannot update with DMC or VE.Bus BMS connected” will be shown during the process when attempting to update such system. No settings or firmware is altered at the time, the system will remain operational.
To update such system remotely, first get someone local to temporarily unplug the RJ-45 connection on the VE.Bus BMS and/or the DMC. Note that the inverter will switch off when doing that. And that it then might be necessary to provide an alternate power supply for the GX device as it will lose power.
During the firmware update, the Victron inverters will be off. This is OK, as this remote firmware update process is designed to perform all critical steps without requiring an internet connection:
It might be necessary to perform a few additional steps after the update, see FAQ below.
NOTE: we're currently still improving this use case. Once completed, the VRM Portal will keep trying to connect for a reasonable time compared to the number of devices that need updating. Which it will do in a manner where its clear for the user that there is no reason (yet) to worry. All this will be completed before official release. The FAQ entry will stay in case something does go wrong.
Though normally not recommended, and also rather unusual, some systems have their GX Device powered on the output of the Victron inverter, with an AC Adapter.
Such system cannot be firmware updated remotely. Attempting to do so will leave the inverter off in bootloader mode with all LEDs flashing. And the system unreachable, since the GX Device is powered down.
Careful: this is not automatically verified in any way.
Testing this on site is easy: switch the inverter off. In case the GX Device remains powered: OK. If not, not OK.
The latest version available on our website includes the necessary features. If you start VEConfigure or VE.Bus System Configurator while connected to the internet, it will automatically check and update itself when necessary.
Not having the latest file installed will result in an error when opening the file (@Jos please confirm by testing)
The inverter/charger is the heart of a Victron power system. Before continuing, make sure to fully understand the process.
This video demonstrates the process:
In the VRM Portal, go to the Device List page, and click the Firmware update button at the bottom of the page. The system will now search for connected devices and once completed show the result:
Once the command is given to update the firmware, this is what happens:
Now, the inverter is on, on its default settings. In case the internet was lost, it will recover which might take a while to fully reconnect all systems. Once restored, the new settings template is retrieved from the system and will be available for download in your web browser.
At this point, the web browser shows below message. Note the downloaded settings template on the lower right:
Convert the settings template by opening it in VE.Bus System Configurator. Do make sure you have the latest version installed.
Next, upload it to the system. Use the VRM Device List → Remote VEConfigure menu. This step will also restore the charge voltages.
This errors shows in case either the minimum installed firmware is from before 426, or there is a CCGX installed which has too old hardware.
The already installed firmware version can be see here, the encircled number must be above 426.
How to check if the CCGX is new enough, see FAQ Q2.
Most likely you are opening the file in the wrong way: double click the file to open it.
Or, the installed version is too old. See above for minimum required VEConfigure / VE.Bus System Configurator tools version.
Each inverter/charger has a unique numeric (serial) number; installed during production. This error shows in case the file sent was made for a different unit.
Note that this error should never occur, error 47 or 48 will happen instead.
To remotely update a systems settings, the full seven digit number in the file must match the system, worded differently:
This error applies to systems consisting if multiple units, ie. parallel-, split- or three-phase systems.
Each inverter/charger has a unique numeric (serial) number installed during production. This error shows in case two or more units in the system have serial number different from the file sent.
In case one unit of such a system must be replaced, that can be done. The steps involved are:
Note that before starting above, make sure to update the new unit to the same version of VE.Bus firmware, which unfortunately can’t be done remotely.
Solution: go onsite and use VE.Bus Quick Configure or VE.Bus System Configurator to reconfigure the system.
Each inverter/charger has a unique numeric (serial) number; installed during production. This error shows in case the file sent was made or a different unit.
There is a way: for the system that you want to configure, first do a Remote VEConfigure download, then open that file by double clicking it. Now in the menu of VEConfigure use Load settings option, and select the file of the system whose settings you want to copy.
Error mk2vsc-55 can happen for two reasons. In case it happens while doing a remote firmware update, it typically the first one:
1) After the firmware update, but still during stage 1, something went wrong. For example VRM lost connection to the site for too long because of bad internet. The firmware update will have completed, but an extra step is necessary to migrate the configuration from before the firmware update. See FAQ Q3 for details.
2) The uploaded file is for a different product type. The model number, for example 2659, does not match.
Note that from Venus OS v2.66 onwards, this error will not occur. Errors 45, 46, 47 and 48 have replaced it.
This error can show after uploading a settings file to the system using Remote VEConfigure. The error shows when the settings template made during a Remote firmware update was uploaded without first opening that in VE.Bus System Configurator.
That depends. If it goes down only for a while; and then recovers within a few minutes after the Inverters are started up again; all will be fine.
In case the internet outage is for another reason and/or takes too long, then this is what happens:
The firmware update will complete without a problem. And the system will start-up again in the mode as described in chapter 3.
What will go wrong is the process in which the old settings are converted and then made available for upload to the system.
To recover, see FAQ Q3.
In case you're wondering how this can work without internet: thats because first the current configuration is retrieve from the system, then the new firmware file is being uploaded to the system. And only once thats done and checked for file integrity, the actual firmware update starts.
There are a few ways. One is by checking the serial number, it must be HQ1707 or newer. 17 is for 2017, and the 07 is the week number. The serial number is printed on a label on the back of the GX Device, and in some cases also visible on the VRM Portal, in the Device List.
The other way is in the UI (either on the CCGX itself, or through Remote Console). Go to the Device List, then into the Multi or Quattro menu, then to the bottom, Device submenu, and scroll all the way to the bottom.
Here you'll see this menu:
It needs to say MK3. Above screenshot is from a CCGX which hardware is too old to perform remote VE.Bus firmware updates.