Differences

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

--- venus-os:remote_ve.bus_firmware_updates [2021-04-07 11:56] – [5. Error codes & trouble shooting] iburger
+++ venus-os:remote_ve.bus_firmware_updates [2024-11-15 10:37] (current) – [1.2 Limitations and requirements] guy_stewart
@@ Line 12: / Line 12: @@
 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.
+It is not required to keep your Victron equipment updated to the latest firmware version. Stable systems should be left with their current firmware. Firmware updates should only be done when it is recommended to fix an issue you are experiencing, or add a new feature that is required by the installation.
 ==== 1.2 Limitations and requirements ====
@@ Line 20: / Line 22: @@
   * In case of another GX Device, ie. a Cerbo, Venus GX, or otherwise, there is no minimum hardware version - they all meet the requirements.
   * Venus OS firmware must be 2.65 or later.
-  * Two Way Communication must be enabled in the VRM menu of the GX device
+  * The ''Full'' access setting, which is on the [[venus-os:start|GX device]] menu -> Settings -> VRM Online Portal -> VRM Portal must be enabled.
 ===== 2. Preparations =====
@@ Line 35: / Line 37: @@
 ==== 2.2 Disconnect VE.Bus BMS and/or Digital Multi Control ====
 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.
+This exception does not apply to a MultiPlus or Quattro with VE.Bus BMS V2. In such systems, a remote firmware update of the VE.Bus inverter or inverter/charger is possible.
 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.
@@ Line 66: / Line 69: @@
 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)
+Not having the latest version of VEConfigure Tools installed will result in an error when opening the file.
-===== 3. Procedure =====
+===== 3. Step by Step Procedure Video =====
 The inverter/charger is the heart of a Victron power system. Before continuing, make sure to fully understand the process.
@@ Line 76: / Line 79: @@
 {{vimeo>519951729?medium}}
-**First stage - retrieving current configuration & doing the update**
+==== 3.1 Checking installed version ====
+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:
+{{ :venus-os:fw_update_device_list2.png?nolink |}}
+==== 3.2 First stage - retrieving current configuration & doing the update ====
 Once the command is given to update the firmware, this is what happens:
@@ Line 83: / Line 92: @@
   - The configuration is retrieved from the VE.Bus system.
   - The inverter is switched off and its firmware is updated. In case the internet router is powered by the inverter, the connection to the installation will now be lost until the update is completed. This is OK: this mechanism has been designed to handle such installation.
-  - After the firmware update is completed, the settings will have been reset to their defaults. Also, to prevent overcharging, the charge current is set to zero amps, and then the inverter is switched on again.
+  - After the firmware update is completed, the inverter is switched on again. The settings will have been reset to their defaults. And, to prevent overcharging, all charge voltages have been set to the nominal battery voltage, being 12V, 24V or 48V. This effectively disables the charger. Note that this works a bit different for systems with a managed battery, usually connected via a CAN-Bus. For such systems, the system will be charging, within limits as provided by the BMS.
-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.
+Now, the inverter is powered up, configured with 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.
-**Second stage - converting and restoring configuration**
+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.
+{{ :venus-os:vrm_remote_update_success_message.png?nolink&600 |}}
-Next, upload it to the system. Use the VRM Device List -> Remote VEConfigure menu. This step will also restore the charge current.
+==== 3.3 Second stage - converting and restoring configuration ====
+Make sure you have the latest version of the [[https://www.victronenergy.com.au/Executables/VEConfig/VECSetup_B.exe|VE.Bus configuration tools]] installed.
+The settings template will need to be converted. It should be a .RVMS file in your download folder (it is saved during the update procedure). Open it by double clicking. If the VE.Bus tools are correctly installed, it will then open in VE.Bus System Configurator, and prompt you about the conversion.
+Close VEConfigure (X on upper right of the window), which will automatically prompt saving that converted file:
+{{ :venus-os:veconfigure_save_remote_file.png?nolink&600 |}}
+Now upload the converted file. On the VRM Portal, go to the Device List -> Remote VEConfigure menu -> 'Upload' the converted file.
+This step will restore the charge voltage and all other configuration settings as they were programmed prior to the firmware update.
 ===== 5. Error codes & trouble shooting =====
+=== Error 733 ===
+This error is generated by the updater logic on the GX device. It show the reason why a firmware update failed. The Error 733 message box will contain an error message with or without a code.
+The most common reasons are:
+^ Message ^ Description ^
+| vbdup failed with exit code 54  | Failed to start Update. The file has an incompatible version number. \\ Please update your Venus OS version to the latest version |
+| vbdup failed with exit code 123 | One or more firmware file(s) supplied do not match the connected device models. |
 === Error 1342 - Not updatable ===
@@ Line 103: / Line 134: @@
 How to check if the CCGX is new enough, see FAQ Q2.
+=== VEConfigure tools File corrupt error ===
+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.
 === mk2vsc-45 - Uploaded file does not contain settings data for the connected unit ===
@@ Line 169: / Line 206: @@
 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. This is because the necessary files are uploaded to the GX Device *before* starting the firmware update.
+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.
@@ Line 175: / Line 212: @@
 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.
 ==== Q2: How to see if a CCGX hardware version matches the required minimal version ====