This is an old revision of the document!
During first installation, and in case of problems, update all devices to the latest firmware. This includes the latest VE.Bus firmware and also the latest firmware in the GX device.
Firmware update instructions:
To restart a system, first switch all units off, one by one. And then switch all units on again. Do this with the On / Off / Charger-only rocker-switch on the front of the device.
*WARNING*: The steps and instructions explained here, are intended to be carried to be carried out by trained professionals. AC (and also DC) Voltages can be lethal. And certain settings and firmware updates require experience and training as well.
Make sure to use industrially made network cabling. Using self crimped RJ45 cables is a known cause of various of below list of errors.
This applies to network cables for split-, three phase and parallel systems as well as connecting a GX Device or other accessory on the VE.Bus network.
One of the phases in a multi-phase system has failed. Commonly because of a Low battery, Overload or High temperature alarm. When this happens, the other phases will show VE.Bus Error Code 1.
Trouble shooting: Look for the failing phase, which will be the phase that is not showing VE.Bus Error Code 1. And check the LEDs on that phase to find out what the reason was for the shut down.
Diagnosing on VRM First make sure that Automatic alarm monitoring is enabled; that is necessary to create the Overload and Temperature errors in the log. You will see Overload and Temperature alarms occurring at the same time as VE.Bus Error 1.
Note for split- and three-phase systems: VRM, nor the CCGX, will indicate on which phase the overload or the temperature alarm occured. To find out on which unit the error occurs, go to system after it has switched off. And look on the LEDs. The unit with the overload or temperature alarm, will have the corresponding alarm LED lit continuously. The other units will indicate a VE.Bus error, indicating that they miss one unit.
This should never happen, contact Victron service.
Possible causes and solutions:
The master device is configured to run in a parallel-, split- and/or three-phase system, but cannot find other devices on the bus.
Multiple possible causes:
1. During a system restart
Error 4 can be seen temporarily while the system restarts after an error. Not a real error in that case, no need to investigate.
2. Because of issues in cabling
Faulty cables. Check the communication cables. Don't use self made cables.
This problem can occur when the AC wiring of one of the slave units is not connected properly, or not connected at all.
Check the AC wiring.
This means: error in an Assistant. To solve, follow these steps:
A VE.Bus BMS device is connected but there is no Assistant loaded which handles the VE.Bus BMS.
Solution: configure the use of the VE.Bus BMS in one of the Assistants.
Indicates a failed automatic Ground relay self-test on the MultiPlus-II or EasySolar-II relays.
See Error 11 for details & instructions.
This typically happens during a system restart, and is then not a real error; no need to investigate.
For example this screenshot from the Color Control GX:
The real problem is Error 1. In this example it was caused by switching device L2 off with the front toggle switch. It was then quickly followed by Error 3. And when switching device L2 back on, briefly Error 10 is visible, followed by full recovery.
Note: System restarts can also be triggered when using Remote VEConfigure.
Other possibility: DC fuse blown of one or more units in the system. When mains is available all units seems to work correctly, but as soon as mains fails, the non powered units are disconnected from the system.
Error 11 indicates a failed automatic self-test of the MultiPlus-II or EasySolar-II relays. It is often a result of an installation or wiring issue, though it can also be triggered by a hardware failure (eg inoperable relays).
If a grid code is selected in VEConfigure, then the backfeed relays are tested every time before connecting to the mains.
Ground relays are also tested and can trigger an Error 11. During inverter operation, disconnected from mains, the relay is continuously tested to be closed. And it is tested to open properly during switchover to mains. The ground relay tests are always performed: with or without a configured grid code. Unless the relay is disabled in VEConfigure. See product manual for more information regarding the ground relay.
Step 1: Make sure that the units have been updated to the latest firmware version. There have been various VE.Bus error 11 related improvements in the firmware. This may correct the error, and if it does not, it will provide additional information to assist troubleshooting.
Step 2: Verify that system is properly wired to your installation and your local codes. Remember to check the earth connection on the unit AC input. Earth should be grounded according to your local grid rules. Do not connect Earth to Neutral in the unit itself. This will create a safety hazard and may prevent RCD devices from working. Contact another licensed electrician if in doubt.
Step 3: Disconnect the L and N wiring from the ACout terminals on each inverter/charger. Which, in case of a parallel or three phase system, isolates the ACout connections for each unit. If the system then starts normally there might be a problem with a connected load (e.g. a leakage between load, neutral and ground).
Step 4: Check your Neutral-out connection. In most cases there should be no external connection between ACin-Neutral to ACout-Neutral, or to Earth.
In Australia, it is possible if required to install with a connection between Neutral-in and Neutral-out using AS4777.2:2015. Select either design configuration in the grid code section while programming the MultiPlus-II with firmware 466 and above.
After configuration, always confirm that the system is safe with routine electrical safety checks in both modes (eg test RCD operation with AC input connected and disconnected).
Step 5: Neutral and line input might be inverted. Check the input connections, swap them if needed and retry. In this case, “Failing step: 8” will show.
After updating your VE.Bus inverter/charger to firmware 454 or higher; and running Venus OS v2.23 or later, a detailed VE.Bus Error 11 report is available in the GX device menu, under MultiPlus → Alarm Status → VE.Bus Error 11 report.
Examples of information in the GX Device menus:
The information shown is:
Common causes:
Other shown error details, listed below, are not related to any known installation issue and can be caused by a faulty unit or configuration issue. In any case, also when one of below errors shows, to go through all the above steps for any error 11 issue.
When the error persists after the all above steps, or when any other Failed step or extra explanation shows, then the unit may be faulty. Follow the support procedure and contact your dealer. Make sure to document full system wiring in a diagram, all steps and tests taken to diagnose and rule out installation error, and provide a photo of the error details shown on the GX Device menu.
Some Multi models (e.g. MultiPlus-II) have two microcontrollers.
Certain configuration settings, as done with VEConfigure, have to be stored in both microcontrollers. In very rare situations it can happen that the stored configurations do not match and that the mismatch cannot be handled automatically. In this case error E12 will be generated.
To solve this error, connect the device to VEConfigure 3, verify/correct the settings and press 'Send Settings'.
Make sure to select the option 'all settings' instead of 'modified settings'.
Most probably a short circuit in the communication cables.
Another possibility, very rare though, is a broken component on the board. Return the device to the nearest service point for repair.
Update firmware to latest version: VE.Bus dongles are no longer necessary.
Instructions here.
Error 17 shows on slaves (only). The slaves in a system will report this error when the communication with the phase-master has timed out.
This error can only occur on systems with multiple devices installed per phase. For example a single phase installation with two or more devices in parallel, or a three-phase installation with six or more devices.
Steps to take:
Error 17 can show on one or more slaves in a phase (visible by looking at the LEDs, not on VRM or GX Device). If the slaves can still communicate with each other; then the error will only show on one slave: all slaves that can see on the network that another slave is already showing Error 17 will not show the error as well.
If after all above steps you are still experiencing a VE.Bus Error 17, contact your dealer whom will contact Victron repairs; please provide photos of the installation and network cabling. Depending on the situation, they might advice to replace the GX device and the inverter/chargers. We advise to first replace cables, and if that doesn't help then thereafter only the GX device at first, since that is less work than replacing the inverter/chargers.
Solution: check if AC wires are not swapped by accident. There can never be voltage on the AC out when a unit is switched off.
Common cause - System is configured with multiple synchronised inverter/chargers but AC input (e.g. from a generator) is only connected to one of the Inverter/Chargers.
Solution: Either connect the AC input to all units, or change the configuration of the synchronised units in VE.Bus System Configurator (note not VEConfigure), and disable the 'Switch as Group' Function. This setting will allow only a single Inverter/Charger to charge without error. Note this setting is not adjustable in an ESS system.
This device is an obsolete and unsuitable model. It should be replaced.
This error indicates that one or more units report feeding back a significant current through its back-feed relay, while those relay are supposed to be open, and -obviously- no current can flow through an open circuit.
What is the back-feed relay? It is the relay that closes when connecting to the grid or generator. And which opens when there is no power available, ie when the system is in island- or invert-mode.
Error 24 is raised when a Multi or Quattro detects current flowing through the back-feed relay during a period when the relay should be open. This can mean one of two things:
Error 24 is a very rare error. Possible causes in order of probability:
Diagnosing a parallel, multi or split-phase system?
Error 24 will always appear on all units at the same time. There is unfortunately no indication, not on LEDs, nor on a GX device, VRM, or any other manner, to see which of the devices caused the error. Below procedures outlines how to manually determine which unit has a faulty relay.
Do make sure to first, always double check option 1 and 2 in above list. Those are the common causes. In case that doesn't lead to a solution, follow this procedure to find out if its a relay issue, and then which unit.
Execute this procedure right after the error occurred; do not first reset the system.
Step 1
Start with making a video of all units and their LED code. Do not first reset the system; and do not reset it after making the video either.
Step 2
Completely disconnect all AC wiring, both in- and out, on all units. Make pictures of the terminals; to make sure when discussing this with an engineer; there is no misunderstanding on what has been meant by this instruction.
Step 3 Now, with an ohm-meter, measure the resistance between the neutral terminals on AC-input and the AC-output, A working unit will show no connection between these terminals. And also measure the resistance between the Line terminals of AC-input and AC-output.
A faulty unit will measure zero or close to zero resistance.
Good units will measure discontinuity between the Line in and out terminals. And measure a few hundred ohms between the neutral In and Out AC terminals.
Make sure to use the same firmware in all devices.
Solution: update all devices to the latest available firmware. Instructions here.
Should not occur. Switch all equipment off, and then on again; it will then resume operation. Contact Victron Energy if the problem persists.