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-03-05 16:07] – guystewart | venus-os:remote_ve.bus_firmware_updates [2023-10-04 11:03] (current) – Add exception for Multi/Quattro with VE.Bus BMS V2 sloges | ||
---|---|---|---|
Line 1: | Line 1: | ||
======= Remote VE.Bus firmware updates ======= | ======= Remote VE.Bus firmware updates ======= | ||
- | This document is a draft version of the new Remote VE.Bus firmware update feature. Once officially released, this must be included into the main [[|https:// | + | ===== 1. Introduction and limitations ===== |
- | ===== 1. Firmware and hardware requirements ===== | + | ==== 1.1 Introduction |
- | * Minimum installed | + | This feature allows remotely updating the firmware of Victron inverter as well as inverter/ |
- | * GX Device minimum hardware | + | |
- | * In case of a CCGX, it must have serial number HQ1707 or newer. | + | |
- | * In case of another | + | |
- | In case either | + | The inverter/ |
+ | |||
+ | This procedure includes migration of the settings. | ||
+ | |||
+ | 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 | ||
+ | |||
+ | ==== 1.2 Limitations and requirements ==== | ||
+ | |||
+ | * Minimum already | ||
+ | * There must be no VE.Bus BMS connected to the VE.Bus network, and also no Digital Multi Control (DMC) panel. See section 2.2 for more information. | ||
+ | * In case of a Color Control GX (CCGX), | ||
+ | * 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 | ||
+ | * Two Way Communication must be enabled in the VRM menu of the GX device | ||
===== 2. Preparations ===== | ===== 2. Preparations ===== | ||
Line 18: | Line 30: | ||
An AC-Coupled PV-Inverter is a PV Inverter connected to the AC out of the Victron Inverter. | 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, | + | 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, |
- | Why? After the firmware update, | + | The reason for having to do this is that the system will start-up while configured |
- | ==== 2.2 Systems with a VE.Bus BMS ==== | + | ==== 2.2 Disconnect |
- | During the firmware | + | It is not possible to update |
+ | 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/ | ||
- | Izak is there more to know? | + | 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 |
+ | |||
+ | 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 | ||
==== 2.3 Systems where the internet connection will be lost while inverters are off ==== | ==== 2.3 Systems where the internet connection will be lost while inverters are off ==== | ||
Line 39: | Line 54: | ||
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. | 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. | ||
+ | |||
==== 2.4 Be 100% sure that the GX Device is not powered by the inverter ==== | ==== 2.4 Be 100% sure that the GX Device is not powered by the inverter ==== | ||
Line 46: | Line 62: | ||
Careful: this is not automatically verified in any way. | 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. | ||
==== 2.5 Have the latest VEConfigure Tools ==== | ==== 2.5 Have the latest VEConfigure Tools ==== | ||
- | For now, they are only available | + | The latest version |
- | Once officially released, this text will be replaced by minimum firmware | + | Not having the latest |
- | Not having the latest file installed will result in an error when opening the file (@Jos please confirm by testing) | + | ===== 3. Step by Step Procedure |
- | + | ||
- | ===== 3. Procedure ===== | + | |
The inverter/ | The inverter/ | ||
- | Here is a video the demonstrates the process: | + | This video demonstrates the process: |
{{vimeo> | {{vimeo> | ||
- | __First stage__ | + | ==== 3.1 Checking installed version ==== |
- | The first stage consists of the following steps: | + | |
- | - Confirm Two Way Communication is enabled in the VRM menu of the GX device | + | 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: |
- | - Open VRM -> Device list for the site you wish to update | + | |
- | - Click the Firmware update button at the bottom of the device list of VRM | + | {{ :venus-os: |
- | - Click the Update Firmware button on the VE.Bus device you wish to update | + | |
- | - The new firmware file is then uploaded to the GX Device. | + | ==== 3.2 First stage - retrieving current configuration & doing the update ==== |
+ | |||
+ | Once the command is given to update | ||
+ | |||
+ | - The new firmware file is uploaded to the GX Device. | ||
- 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. | + | - The inverter is switched off and its firmware is updated. |
- | - After the firmware update is completed, the settings will be reset to defaults | + | - 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, |
- | - The internet connection will be re-established | + | |
+ | 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 | ||
+ | |||
+ | At this point, the web browser shows below message. Note the downloaded settings template on the lower right: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | ==== 3.3 Second stage - converting | ||
+ | |||
+ | Make sure you have the latest version of the [[https:// | ||
+ | |||
+ | 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 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 === | ||
+ | |||
+ | 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. | ||
+ | |||
+ | === 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 === | ||
+ | |||
+ | Each inverter/ | ||
+ | |||
+ | Note that this error should never occur, error 47 or 48 will happen instead. | ||
+ | |||
+ | === mk2vsc-46 - Uploaded file does not match model and/or installed firmware version === | ||
+ | |||
+ | To remotely update a systems settings, the full seven digit number in the file must match the system, worded differently: | ||
+ | |||
+ | * its not possible to take settings from a 3kVA and then upload it to a 5kVA model. | ||
+ | * its not possible to store settings from a system having version 479. Then update that system to 481, and then restore the settings by uploading that earlier saved file. Instead, use the merge function, see elsewhere in this manual. | ||
+ | |||
+ | |||
+ | === mk2vsc-47 - More than one unknown unit detected === | ||
+ | |||
+ | This error applies to systems consisting if multiple units, ie. parallel-, split- or three-phase systems. | ||
+ | |||
+ | Each inverter/ | ||
+ | |||
+ | In case one unit of such a system must be replaced, that can be done. The steps involved are: | ||
+ | |||
+ | - Read the configuration of the whole system (or use an existing Remote VEConfigure file) | ||
+ | - Physically replace the failed unit | ||
+ | - Write the configuration. At this step the system will automatically detect that a previous device is missing, | ||
+ | - (optionally) Read the new configuration file and store in your records. | ||
+ | |||
+ | 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 | ||
+ | |||
+ | === mk2vsc-48 - Updating a single unit with another unit's settings is not possible, even if they are of the same type === | ||
+ | |||
+ | Each inverter/ | ||
+ | |||
+ | 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. | ||
+ | |||
+ | === mk2vsc-55 - File section not found === | ||
+ | |||
+ | Error mk2vsc-55 can happen for two reasons. In case it happens while doing a remote firmware update, it typically | ||
+ | |||
+ | 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. | ||
+ | |||
+ | === mk2vsc-59 - file uploaded before merging in VE.Bus System Configurator === | ||
+ | |||
+ | 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. | ||
+ | |||
+ | Solution: | ||
+ | |||
+ | - instead of uploading the file, open it on your computer with VE.Bus System Configurator. Typically done by simply double clicking the file. | ||
+ | - VE.Bus System Configurator will now process file the, and show a message when completed. | ||
+ | - finally, save it by closing VE.Configure. And upload the resulting file, which name will by _merged.rvms. | ||
+ | |||
+ | ===== 6. FAQ ===== | ||
+ | |||
+ | ==== Q1: What happens if the internet connection goes down during the process? ==== | ||
+ | |||
+ | 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 recover, see FAQ Q3. | ||
- | At this moment the first stage is complete. | + | In case you're wondering how this can work without internet: thats because |
+ | ==== Q2: How to see if a CCGX hardware version matches the required minimal version ==== | ||
- | __Second stage__ | + | There are a few ways. One is by checking the serial number, |
- | Now, you’ll need to open the file that was automatically downloaded for you from VRM in VE.Bus System Configurator | + | |
- | __Third stage__ | + | 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, |
- | On VRM, go to Device List -> Remote VEConfigure and there use the Upload feature | + | |
- | ===== 5. FAQ ===== | + | Here you'll see this menu: |
- | ==== Q1: What happens if the internet connection goes doen during the process? ==== | + | {{ :venus-os: |
- | The firmware update will complete without | + | It needs to say MK3. Above screenshot is from a CCGX which hardware is too old to perform remote VE.Bus |
- | What will go wrong is preparing the .rvms file that contains | + | ==== Q3: Merging files: how to recover |
- | Steps to recover: | ||
- In VRM -> Device List -> Remote VEConfigure, | - In VRM -> Device List -> Remote VEConfigure, | ||
- | - Open that file by double clicking it. In case of a single unit it will open in VEConfigure. For systems consisting of multiple units, it will be opened | + | - Use the merge function |
- | - Click File -> Load settings, and select the first file. Ie the file prompted during the Firmware update process. | + | |
- | - Now, the settings will automatically be converted to the new firmware version; and a popup will show in case anything needs double checking. | + | |
- | - Close the file by exiting the application; | + | |
- | - On VRM, go to Device List -> Remote VEConfigure and there use the Upload feature to upload the settings. | + | |
+ | {{ : |
venus-os/remote_ve.bus_firmware_updates.1614956836.txt.gz · Last modified: 2021-03-05 16:07 by guystewart