venus-os:remote_ve.bus_firmware_updates
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
venus-os:remote_ve.bus_firmware_updates [2021-04-07 20:53] – [Q1: What happens if the internet connection goes down during the process?] mvader | 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, | There is no limitation on the type of system: single unit systems, parallel, split-phase, | ||
+ | |||
+ | 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, | ||
==== 1.2 Limitations and requirements ==== | ==== 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. | * 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. | * Venus OS firmware must be 2.65 or later. | ||
- | * Two Way Communication must be enabled in the VRM menu of the GX device | + | * The '' |
===== 2. Preparations ===== | ===== 2. Preparations ===== | ||
Line 35: | Line 37: | ||
==== 2.2 Disconnect VE.Bus BMS and/or Digital Multi Control ==== | ==== 2.2 Disconnect VE.Bus BMS and/or Digital Multi Control ==== | ||
- | It is not possible to update a VE.Bus inverter, or inverter/ | + | It is not possible to update a VE.Bus inverter, or inverter/ |
+ | 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/ | ||
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. | 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. | 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 | + | Not having the latest |
- | ===== 3. Procedure ===== | + | ===== 3. Step by Step Procedure |
The inverter/ | The inverter/ | ||
Line 89: | Line 92: | ||
- The configuration is retrieved from the VE.Bus system. | - 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. | - 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. | + | - After the firmware update is completed, the inverter is switched on again. The settings will have been reset to their defaults. |
- | 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. |
At this point, the web browser shows below message. Note the downloaded settings template on the lower right: | At this point, the web browser shows below message. Note the downloaded settings template on the lower right: | ||
Line 99: | Line 102: | ||
==== 3.3 Second stage - converting and restoring configuration ==== | ==== 3.3 Second stage - converting and restoring configuration ==== | ||
- | Convert the settings template by opening it in VE.Bus System Configurator. Do make sure you have the latest version installed. | + | Make sure you have the latest version |
- | Next, upload | + | 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, |
+ | |||
+ | Close VEConfigure (X on upper right of the window), which will automatically prompt saving that converted file: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | Now upload the converted file. On the VRM Portal, go to the Device List -> Remote VEConfigure menu -> ' | ||
+ | |||
+ | This step will restore the charge | ||
===== 5. Error codes & trouble shooting ===== | ===== 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 === | === Error 1342 - Not updatable === | ||
Line 113: | Line 134: | ||
How to check if the CCGX is new enough, see FAQ Q2. | 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 === | === mk2vsc-45 - Uploaded file does not contain settings data for the connected unit === |
venus-os/remote_ve.bus_firmware_updates.1617821587.txt.gz · Last modified: 2021-04-07 20:53 by mvader