Victron PV inverter or controller displaying a fault code?
Sometimes a problem indicated can be resolved without the need to call anyone out or replace hardware. If not then it might give a clue as to what the root cause could be.
- Check to see if your fault code is in the list below.
- All fault codes shown are manufacturer supplied.
- Follow any manufacturers advice indicated next to your error code.
- Many inverters will show an error indicating an internal failure, this usually means a replacement is required, call us for advice or a quote.
- If your inverter does not have a screen and is off-line you could try our home troubleshooting guide to try to get your solution working again.
- If all else fails we would be happy to take your call on 0330 345 3400
Repairs & Maintenance
- Domestic and Commercial, UK wide
- Grid Tie, Off Grid & Hybrid
- All manufacturers Inverter Errors Diagnosed & Resolved
- Energy Storage Systems
Additional Services
- Cloud & Monitoring faults investigated
- Solar Array Refits
- Bird & pest guard
- Free advice 0330 345 3400
MPPT Solar Charger Error Codes
|
Error |
Explanation |
|
Err 1 – Battery temperature too high
|
This error will auto-reset after the battery temperature has dropped. The charger will stop charging to prevent damaging the battery. The battery temperature can be received by an external sensor (like Smart Battery Sense or BMV), or measured by the charger when this feature is available.
|
|
Err 2 – Battery voltage too high
|
This error will auto-reset after the battery voltage has dropped. This error can be due to other charging equipment connected to the battery or a fault in the charge controller. This error can also occur if the battery voltage (12, 24 48V) is set to a lower voltage than the connected battery.
|
|
Err 3, Err 4 – Remote temperature sensor failure
|
Check if the T-sense connector is properly connected to a remote temperature sensor. Most likely cause: the remote T-sense connector is connected to the BAT+ or BAT- terminal. This error will auto-reset after proper connection.
|
|
Err 5 – Remote temperature sensor failure (connection lost)
|
Check if the T-sense connector is properly connected to a remote temperature sensor. This error will not auto-reset.
|
|
Err 6, Err 7 – Remote battery voltage sense failure
|
Check if the V-sense connector is properly connected to the battery terminals. Most likely cause: the remote V-sense connector is connected in reverse polarity to the BAT+ or BAT- terminals.
|
|
Err 8 – Remote battery voltage sense failure (connection lost)
|
Check if the V-sense connector is properly connected to the battery terminals. |
|
Err 11 – Battery high ripple voltage
|
High DC ripple is usually caused by loose DC cable connections and/or too thin DC wiring. After the inverter has switched off due to high DC ripple voltage, it waits 30 seconds and then restarts.
After three restarts followed by a shutdown due to high DC ripple within 30 seconds of restarting, the inverter will shut down and stop retrying. To restart the inverter, switch it Off and then On.
Continuous high DC ripple reduces the inverter life expectancy |
|
Err 14 – Battery low temperature
|
The charger is stopped to avoid charging LiFePO4 batteries at low temperature as this damages the cells.
|
|
Err 17 – Controller overheated despite reduced output current
|
This error will auto-reset after charger has cooled down. Check the ambient temperature and check for obstructions near the heatsink.
|
|
Err 18 – Controller over-current
|
This error will auto-reset. If the error does not auto-reset disconnect the charge controller from all power-sources, wait 3 minutes, and power up again.
Possible causes for an over-current on the battery terminals:
switching on/off a very large load on the battery side. sudden change in irradiance causing a temporary over-power in the mppt. overloading the inverter ac output. Possible solutions
if possible, provide adequate cooling for the unit, a cooler unit can handle more current. reduce the load on the inverter. charge the battery before using the inverter, at higher battery voltages the same amount of power requires less current.
|
|
Err 20 – Maximum Bulk-time exceeded
|
Solar Chargers The maximum bulk time protection is a feature that was in the chargers when they were just released (2015 or earlier) and later the feature was removed.
If you do see this error, then update to the latest firmware.
If you then still have the error, perform a reset to factory defaults of the configuration, and reconfigure the solar charger.
AC Chargers This protection is default enabled on the Skylla-i and the Skylla IP44.
This error is generated when the battery-absorption-voltage is not reached after 10 hours of charging.
The feature of this safety protection is to detect a shorted cell; and stop charging.
|
|
Err 21 – Current sensor issue
|
The current measurement is out of range.
Disconnect all wires, and then reconnect all wires, to make restart the charger. Also, make sure the minus on the MPPT charge controller (PV minus/Battery minus) is not bypassing the charge controller.
This error will not auto-reset.
If the error remains, please contact your dealer, there might be a hardware defect.
|
|
Err 22, Err 23 – Internal temperature sensor failure
|
The internal temperature measurements are out of range.
Disconnect all wires, and then reconnect all wires, to restart the unit.
This error will not auto-reset.
If the error remains, please contact your dealer, there might be a hardware defect.
|
|
Err 24 – Fan failure
|
This error indicates that the fan is powered on but the circuit does not measure any current draw by the fan. Most likely its either broken or obstructed.
Please contact your dealer, there might be a hardware defect.
Applies to Skylla-IP44 & Skylla-IP65 chargers only.
|
|
Err 26 – Terminal overheated
|
Power terminals overheated, check wiring, including the wiring type and type of strands, and/or fasten bolts if possible.
This error will auto-reset.
|
|
Err 27 – Charger short circuit
|
This condition indicates an over-current condition on the battery side. It can occur when a battery is attached to the unit using a contactor. Or in case the charger starts up without a battery connected but connected to an inverter that has a large input capacitance.
This error will auto-reset. If the error does not auto-reset disconnect the charge controller from all power-sources, wait 3 minutes, and power up again. If the error persists the charge controller is probably faulty.
|
|
Err 28 – Power stage issue
|
This error will not auto-reset.
Disconnect all wires, and then reconnect all wires. If the error persists the charge controller is probably faulty.
Note that this error was introduced in v1.36. So when doing an update, it might look like the firmware update caused this issue; but it doesn’t. The Solar charger was then already not performing 100% before the update; updating to v1.36 or later merely made the issue more visible. The unit needs to be replaced.
|
|
Err 29 – Over-Charge protection
|
This error will auto-reset once the battery voltage drops below the float voltage. To protect the battery from over-charging the battery is disconnected.
Possible causes:
over-sized PV array configuration, if there are too many panels in series the battery voltage cannot be reduced any further. Consider wiring more PV panels in parallel to reduce the voltage. configuration issue, check if the battery settings match with the installation (especially absorption and float voltage settings). another charger in the system raises the battery voltage above the expected level.
|
|
Err 33 – PV over-voltage
|
This error will auto-reset after PV-voltage has dropped to safe limit. This error is an indication that the PV-array configuration with regard to open-circuit voltage is critical for this charger. Check configuration, and if required, re-organise panels.
|
|
Err 34 – PV over-current
|
The current from the solar-panel array has exceeded the rated current limit. This error could be generated due to an internal system fault. Disconnect the charger from all power-sources, wait 3 minutes, and power-up again. If the error persists the controller is probably faulty, contact your dealer.
|
|
Err 35 – PV over-power
|
Applies to the MPPT RS, Inverter RS and Multi RS products.
Please upgrade your firmware to at least v1.08 as the issues causing this error have been addressed.
If you are using firmware v1.08 or newer this error indicates that the internal dc voltage is too high. This error will auto-reset. If the error does not auto-reset disconnect the charge controller from all power-sources, wait 3 minutes, and power up again. If the error persists the charge controller is probably faulty.
|
|
Err 38, Err 39 – PV Input shutdown
|
To protect the battery from over-charging the panel input is shorted.
Possible reasons for this error to occur:
The Battery voltage (12/24/48V) is set, or auto-detected, incorrectly. Use VictronConnect to disable auto-detect and set the Battery Voltage to a fixed voltage. There is another device connected to the battery, which is configured to a higher voltage. For example a MultiPlus, configured to equalise at 17 Volts, while in the MPPT this is not configured. The battery is disconnected using a manual switch. Ideally the charger should be switched off before disconnecting the battery, this avoids a voltage overshoot on the charger output. If necessary the voltage trip-level for the PV Short protection can be increased by raising the Equalization voltage set-point (note: equalization does not have to be enabled in this case). The battery is disconnected using a Lithium charge relay connected to the “allow-to-charge” output of a BMS. Consider wiring this signal to the Remote terminal of the charger instead. This shuts down the charger gracefully without creating a voltage overshoot.
|
|
Error 38 Internal error |
First disconnect the solar panels and disconnect the battery. Wait for 3 minutes, then reconnect the battery first and next the panels. |
|
Error 39 Overvoltage |
The charger will automatically resume operation once the battery voltage drops below its maximum voltage setting (normally Equalisation or Absorption voltages), for 250V versions or float voltage for the other units. It can also takes a minute to reset the fault. If the error persists the charge controller is probably faulty.
|
|
Err 40 – PV Input failed to shutdown
|
If the charger is unable to turn off the PV input, it will go into a safe mode in order to protect the battery from over-charging or having a high voltage on the battery terminals. In order to do that, the charger will stop charging and disconnect its own output. The charger will become faulty.
|
|
Err 41 – Inverter shutdown (PV isolation)
|
PV panel isolation resistance too low. Check the PV array cabling and panel isolation, the inverter restarts automatically once the issue is resolved.
|
|
Err 42 – Inverter shutdown (Ground Fault)
|
The ground leakage current exceeds the allowed 30mA limit. Check the PV array cabling and panel isolation. Check the installation and restart the unit using the power-switch.
|
|
Err 43 – Inverter shutdown (Ground Fault)
|
The voltage difference between Neutral and Ground is too high.
Inverter or Multi (not connected to the grid):
The internal ground relay is activated but the voltage over the relay is too high. The relay might be damaged. Multi (connected to the grid):
The ground wire in the installation is not present or not connected properly. Line and Neutral are swapped in the installation. This error will not auto-reset. Check the installation and restart the unit using the power-switch.
|
|
Err 50, Err 52 – Inverter overload, Inverter peak current
|
Some loads like motors or pumps draw large inrush currents in a start-up situation. In such circumstances, it is possible that the start-up current exceeds the over current trip level of the inverter. In this case the output voltage will quickly decrease to limit the output current of the inverter. If the over current trip level is continuously exceeded, the inverter will shut down: wait 30 seconds and then restart.
The Inverter can supply more power than the nominal power level for a short time. If the time is exceed the inverter stops.
After three restarts followed by another overload within 30 seconds of restarting, the inverter will shutdown and remain off. To restart the inverter, switch it Off, then On.
If the error persists reduce the load on the AC out terminal by switching off or disconnecting appliances.
|
|
Err 51 – Inverter temperature too high
|
A high ambient temperature or enduring high load may result in shut down to over temperature. Reduce load and/or move inverter to better ventilated area and check for obstructions near the fan outlets.
The inverter will restart after 30 seconds. The inverter will not stay off after multiple retries.
|
|
Err 53 – Inverter output voltage
|
If the battery voltage is getting low and a large load is applied to the AC output the inverter is unable to maintain the proper output voltage. Re-charge the battery or reduce the AC loads to continue operation.
|
|
Err 54 – Inverter output voltage
|
If the battery voltage is getting low and a large load is applied to the AC output the inverter is unable to maintain the proper output voltage. Re-charge the battery or reduce the AC loads to continue operation.
If the error immediately pops up when switching on the inverter (without load) on a full battery the cause is most likely a broken internal fuse.
|
|
Err 55, Err 56, Err 58 – Inverter self test failed
|
The inverter performs diagnostic tests before it activates its output. In the case that one of these tests fails an error message is displayed and the inverter does not turn on.
First try to restart the inverter, by switching it Off, and then On. If error persists the inverter is probably faulty.
|
|
Err 57 – Inverter ac voltage on output
|
There is already AC voltage on the AC out terminal before switching on the inverter. Check that the AC out is not connected to a mains outlet or to another inverter.
This error will not auto-reset. Check the installation and restart the unit using the power-switch.
|
|
Information 65 – Communication warning Information 66 – Incompatible device
|
Communication with one of the paralleled controllers was lost. To clear the warning, switch the controller off and back on
The controller is being paralleled to another controller that has different settings and/or a different charge algorithm.
Make sure all settings are the same and update firmware on all chargers to the latest version
|
|
Err 67 – BMS Connection lost
|
The charger is configured to be controlled by a BMS, but it does not receive any control messages from a BMS. The charger stopped charging, as a safety precaution.
Solar Chargers only show this error when there is solar power available and thus the device is ready to initiate charging. It does not show at night. And in case there is a permanent problem, the error will raise in the morning and clear at night, and so forth.
Check the connection between the charger and the BMS.
How to reconfigure the charger to standalone mode
Our Chargers and Solar Chargers automatically configure themselves to be BMS-controlled when they are connected to one; either direct or via a GX Device. And that setting is semi-permanent: power cycling the charger will not reset it.
Here is what needs to be done to make the charger operate in stand-alone mode again, i.e. not controlled by a BMS:
Chargers with LCD display: go into the setup menu and change setting ‘BMS’ from ‘Y’ to ‘N’ (setup item 31). Other chargers: reset the charger to factory defaults with VictronConnect, and then reconfigure it.
|
|
Err 68 – Network misconfigured
|
Applies to SmartSolar/BlueSolar MPPTs VE.Can (FW version v1.04 or higher) and SmartSolar VE.Direct MPPTs (FW version v1.47).
To clear the error on the SmartSolar VE.Direct MPPTs update the FW version to v1.48 or higher.
To clear the error on the SmartSolar/BlueSolar MPPTs VE.Can, update the software. If the error persists, it will be because the charger is connected to both a VE.Direct cable and on VE.Can. That is not supported. Remove one of the two cables. The error will disappear, and the charger will resume normal operation, within a minute.
Error 68 indicates that the charger detects multiple conflicting network sources, with the same priority, trying to send the same information to the charger. VE.Can and VE.Direct interfaces have both the same priority level, and BLE (using VE.Smart Networking) has a lower priority.
Having a higher priority level means that, if the same information (e.g. Battery voltage sense) is being received from both VE.Can and BLE (using VE.Smart Network) by the charger, the information on VE.Can will be used and the one coming from BLE will be ignored.
Now, if the same information is being received from two interfaces that have the same priority level (as VE.Can and VE.Direct), the charger does not know how to prioritize those, causing error 68 to be triggered.
|
|
Err 114 – CPU temperature too high
|
This error will reset after the CPU has cooled down. If the error persists, check the ambient temperature and check for obstructions near the air inlet and outlet holes of the charger cabinet. Check manual for mounting instructions with regard to cooling. If error persists the controller is probably faulty.
|
|
Err 116 – Calibration data lost
|
If the unit does not work and error 116 pops up as the active error the unit is faulty, contact your dealer for a replacement.
If the error is only present in the history data and the unit operates normally this error can be ignored safely. Explanation: when the units power up for the very first time in the factory, it does not have calibration data and an error 116 is logged. Obviously this should have been cleared, but in the beginning units left the factory with this message still in the history data.
SmartSolar models (not the BlueSolar models): upgrading to v1.4x firmware is a one-way trip, you cannot go back to an older firmware version once you upgrade to v1.4x. Reverting to older firmware gives error 116 (calibration data lost), this can be fixed by re-installing the v1.4x firmware.
|
|
Err 117 – Incompatible firmware
|
This error indicates that a firmware update did not complete, so the device is only partially updated. Possible causes are: device out of range when updating over the air, a cable got disconnected or power was lost during the update session.
To fix this the update needs to be retried, download the correct firmware for your device from the Victron Professional Portal
When your Venus GX device is connected to VRM, you can do a remote firmware update using this firmware file. You can do this via the VRM website or using the VRM tab in VictronConnect. VictronConnect can also be used together with the firmware file to update using a Bluetooth connection.
The procedure to add the file to VictronConnect and start the update is described here: 9. Firmware updates
|
|
Err 119 – Settings data lost
|
The charger cannot read its configuration, and stopped.
This error will not auto-reset. To get it working again:
First, restore it to factory defaults. (top right in Victron Connect, click on the three dots) Disconnect the charge controller from all power-sources wait 3 minutes, and power up again. Reconfigure the charger. Please do report this to your Victron dealer and ask him to escalate it to Victron; as this error should never happen. Preferably include firmware version and any other specifics (VRM URL, VictronConnect screenshots or similar).
|
|
Err 121 – Tester fail
|
If the unit does not work and error 121 pops up as the active error the unit is faulty, contact your dealer for a replacement.
If the error is only present in the history data and the unit operates normally this error can be ignored safely. Explanation: when the units powers up for the very first time in the factory, it does not have calibration data and an error 121 is logged. Obviously this should have been cleared, but in the beginning units left the factory with this message still in the history data.
|
|
Err 200 – Internal DC voltage error
|
The unit performs internal diagnostics when activating its internal DC-DC converter. This error indicates that something is wrong with the DC-DC converter.
This error will not auto-reset. Check the installation and restart the unit using the power-switch. If the error persists the unit is probably faulty.
|
|
Err 201 – Internal DC voltage error
|
Applies to the MPPT RS, Inverter RS and Multi RS
Internal DC voltage measurement error, is raised in case an internal (high-) voltage measurement does not match certain criteria. And it means that a measurement circuit inside the unit is broken.
Make sure to update the firmware to at least v1.08, in previous firmwares the limits were too strict. And it could trigger falsely during MPPT start-up in the morning and MPPT shutdown in the evening.
The unit might have seemingly worked fine before the firmware update; but it is really broken, not safe for use, and if it hadn’t stopped working already then it would have stopped working soon. Which is why we added this internal check.
This error will not auto-reset. Check the installation and restart the unit using the power-switch. If the error persists the unit is probably faulty and must be sent in for repair/replacement. |
|
Err 203, Err 205, Err 212, Err 215 – Internal supply voltage error
|
The unit performs internal diagnostics when activating its internal voltage supplies. This error indicates that something is wrong with an internal supply voltage.
This error will not auto-reset. Check the installation and restart the unit using the power-switch. If the error persists the unit is probably faulty. |
VE.Bus Error Codes
Error 1 – Device is switched off because one of the other phases in the system has switched off
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 GX device, 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.
Recovery: auto-restart once the error is gone.
Error 2 – New and old type MK2 protocol mixed in the system
This should never happen, contact Victron service.
Recovery: auto-restart once the error is gone.
Error 3 – Not all, or more than, the expected devices were found in the system
Possible causes and solutions:
1. This error often follows VE.Bus Error 1. Solution: solve the cause for VE.Bus Error 1. Note that when using an older CCGX (version before v1.40), it can be that the first error is not reported on the Alarm log on VRM. So even when it only lists VE.Bus Error 3, it can very well be that that error was preceeded by VE.Bus Error 1.
2. The system is not properly configured: all VE.Bus devices connected to the VE.Bus network must be configured as one parallel, split- and/or three-phase system. Do not connect two separate VE.Bus systems together.
3. Communication cable error: Check the communication cables. Make sure to use commercial patch leads and not hand-crimped cables – VE.Bus cabling is very sensitive to physical wiring faults.
4. 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, or as soon as the system decides to switch to Island mode for any other reason, the units with the blown DC fuse will be without power and switched off – and thus be “missing” from the communication network.
5. When switching off so called “complex systems” where the switch-as-group VE.Bus configuration is disabled and not all phases have AC-in. In some Multi models like the MultiPlus-II the VE.Bus communication remains active when switched off through Venus OS as long as AC in is available. In this case other Multis in the system with no AC input do not communicate. Causing the Multi with AC input to raise error 3. Complex systems are not supported and tested during Venus OS development.
Recovery: auto-restart once the error is gone.
Error 4 – No other device found
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.
Recovery: auto-restart once the error is gone.
Error 5 – Overvoltage on AC out
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.
Recovery: auto-restart once the error is gone.
Error 6 – Error in DDC Program
This means: error in an Assistant. To solve, follow these steps:
1. update VE.Bus firmware in all devices to the latest firmware. Instructions here.
2. download the latest VEConfigure and make sure it has downloaded all the latest Assistants.
3. re-configure the system
This error can also occur in newer firmwares when a VE.Bus BMS is connected (or dis-connected) and the assistant is not configured accordingly.
Recovery: auto-restart once the error is gone.
Error 7 – External device connected, assistant required
An external device (e.g. a VE.Bus BMS) is connected but there is no Assistant loaded which handles that device.
Solution: configure the Multi/Quattro with a suitable Assistant.
Recovery: auto-restart once the error is gone.
Error 8 – Ground relay test failed
This error indicates a failed self-test of the MultiPlus-II or EasySolar-II internal1 ground relays.
During inverter operation, disconnected from mains, the ground relay is continuously tested to be closed. While switching over to mains it is tested to open. The ground relay tests are always performed: in systems with a grid code configured as well as system without a grid code configured. The only exception is systems where the relay is disabled in VEConfigure. See product manual for more information regarding the ground relay.
Using a GX device, the underlying detailed error can be seen for each individual inverter/charger in the system:
Definition of
ground-relay related error types:
§ GND Relay Error: Comes from the secondary controller; and can both mean that
the relay is measured as being open, while it is expected to be closed, and the
other way around.
§ Error: PE2 Open: Comes from the main controller, means that the relay is
measured as being open while expected to be closed.
§ Error: PE2 Closed: Also comes from the main controller, and means that its
measured as being closed while expected to be open.
Note that the pages as shown in above
screenshots show the last error that happened in a unit. The errors are stored
in non-volatile memory in the inverter/charger, and can therefore be something
that was from a long time ago.
Therefore, take care to analyse only the
latest error: make a note of the error counter (#8, #18, #11, and so forth in
the first screenshot), and then switch the system on again. And after the next
shutdown, compare the actual counters with the noted counters. Alternatively,
use the Download feature on the Advanced page of the VRM Portal, and analyse
the data in Excel.
Footnote 1: For the first revision hardware,
the measurement also includes externally connected ground relays. For later
revisions, it only checks the internal relay. See section below about the
different hardware revisions.
Determining used hardware
version
There has been a change (late 2020/early
2021) in the way the Ground relay test mechanism works. Newer units use an
auxiliary contact on the ground relay, while older units measure the voltage
between GND and Neutral.
The advantage of the new version is that the
checking of the ground relay is immune to how the system is wired, and any
possible errors in wiring on the input side and/or the output of the
inverter/charger.
How to diagnose an error strongly depends on
the underlying hardware, therefore as a first step, find out which hardware
version is used, by using this table:
|
Model |
Serial number |
|
MultiPlus-II 48V 3kVA |
≤ HQ2048 |
|
MultiPlus-II 48V 3kVA GX |
≤ HQ2050 |
|
MultiPlus-II 24V 3kVA |
≤ HQ2101 |
|
MultiPlus-II 48V 5kVA |
≤ HQ2116 |
|
MultiPlus-II 48V 5kVA GX |
≤ HQ2122 |
|
EasySolar-II 48V 3kVA MPPT 250-70 GX |
≤ HQ2130 |
|
All other models |
Any serial number |
All non-listed
models have the improvement from their first production, meaning they are
always the new hardware.
Diagnosing GND
relay errors in systems with new hardware:
Conclusion: if any of the units repeatedly
displays a GND relay error, then that specific unit will have an issue with
it’s GND relay and should likely be replaced.
Diagnosing GND
relay errors in systems with old hardware:
Note: With this type of hardware it is very
well possible that the error is raised by unit X while the cause of the error
can be in unit Y.
Possible
cause #1: Neutral-out externally tied to GND
If the neutral-out is connected to GND
externally then the unit will always detect that the GND relay fails to open.
Solution: Correct the wiring.
Possible
cause #2: Neutral is bypassed intentionally
Neutral AC-in is connected to Neutral AC-out
while not configured as such in the software.
The error will show up the moment the system
tries to switch to grid and indicates either a wiring error, or a mismatch
between the wiring and the configuration of the gridcode in the
inverter/charger.
In case bypassing the Neutral is mandatory by
local regulations, such as in certain regions in Australia, then select the
corresponding “Neutral path externally joined” grid-code in the configuration
software.
Otherwise, remove the bypass.
Possible
cause #3: Leakage or short in the loads of the inverters
This could be either a defect in the wiring
or a defect in one of the loads in the system.
1.
Check by first disconnecting all loads: open the circuit breakers.
2.
Restart system and check if it can switch to the grid without
error.
3.
Then measure with a multi meter that there is no continuity
between the neutral and the ground. (Alternatively disconnect all loads or
sub-circuits, and bring them back online one by one. Just like when fault
finding a shorted load that is tripping a circuit breaker.)
While testing this, be aware that:
1.
The test is performed by the units the moment the system
attempts to switch to the grid. So checking this while only in inverting mode
has no effect, since the ground relay is then closed; and a leakage or short in
the system between AC-out neutral and ground will then not be detected.
2.
In case of a multiple units installed in parallel to each other,
the AC outputs need to remain connected to each other: only disconnect the
loads. Disconnecting all AC-out wires from each individual unit will not work,
as doing so will result in a series of other errors.
Possible
cause #4: Faulty ground relay, or its detection circuit
This is a hardware defect in the
inverter/charger, or in at least one of the inverter/chargers in a system
consisting of multiple units.
Since unit X can display the error while the
root is in unit Y there is no easy way to find out. The most straight forward
is to configure every multi as standalone and check whether it can switch to
the grid without error.
Possible
cause #5: Three phase systems only: loads mismatch with ground relay safety
circuit
This will show either as a GND Relay Error or
a PE2 Closed Error.
This issue affects three phase systems only.
For three phase systems (which have the old
hardware!) and where all above steps have been checked carefully, contact your
Victron dealer for next steps: in this case, all units will need to be replaced
with the newer type.
Error 10 – System time
synchronisation problem
This typically happens during a system
restart, and is then not a real error; no need to investigate.
For
example this screenshot from the GX device
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.
Recovery: auto-restart once
the error is gone.
Error 11 – Relay Test Fault – Installation error or possibly relay failure
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.
Steps to take:
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, using grid code AS4777.2:2015, it may be mandatory to make an external connection between Neutral-in and Neutral-out. Select either design configuration in the grid code section while programming the MultiPlus-II with firmware 466 or 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.
Detailed diagnosis of Error 11
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:
§ A six digit number; which contains all the details
§ An error ID (#4 in above screenshot). Note that this does not count the number of VE.Bus errors; its just a unique ID that can help recognizing that a new error has occurred.
§ Flags
§ The failed step; it counts backwards: step 9 → 8 → 7 and so forth.
Common causes:
§ Failing step #8: check that line and neutral have not been swapped. Unlike non-grid code installations; line and neutral need to be wired correctly.
§ AC0/AC1 mismatch and UMains error: this is fixed in VE.Bus inverter/charger firmware version 455.
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, make sure to go through all the above steps for any error 11 issue.
§ Failing steps #2-7.
§ AC0 /AC1 mismatch.
§ Communication error.
§ UMains mismatch.
§ Period Time mismatch.
§ Drive of BF relay mismatch.
Unable to solve?
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.
Recovery: auto-restart once the error is gone.
Error 12 – Config mismatch with 2nd mcu
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’.
Recovery: auto-restart once the error is gone.
Error 14 – Device cannot transmit data
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.
Recovery: auto-restart once the error is gone.
Error 15 – VE.Bus combination error
Any combination error of VE.Bus products, firmware versions or commands has occured
This error can occur for example when:
- an Interface-1140 with old firmware is combined with a new Multi firmware or
- when external BMS commands are send while a VE.Bus BMS is connected or
- the connected VE.Bus product firmware versions are incompatible. (This can in most cases be solved by updating the firmware.)
Recovery: auto-restart once the error is gone.
Error 16 – VE.Bus dongle is missing
Update firmware to latest version: VE.Bus dongles are no longer necessary.
Instructions here.
Recovery: system remains off until restarted.
Error 17 – Phase master missing
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:
- In some cases this error can be seen temporarily while using Remote VEConfigure to write a new configuration.
Solution: ignore the error; the system will recover by itself. - The most likely cause is a cable-related communication issue on the VE.Bus network:
Solution: First check the network cables sockets. If that doesn’t solve it, replace all network cables, including the cable to the GX Device. Make sure to also inspect the female RJ-45 sockets, instead of only the cabling: sometimes badly mounted RJ45 cable connectors prevent the spring-contacts in the female RJ45 connectors on the Multis to properly make contact. Make sure to machine-made cabling. Do not use self-crimped cables. - DC fuse blown. In this case, all units can in some situations seem fine and work well as long as mains is available. And then when there is no longer AC available on the input (mains fails or generator is stopped) the non powered units are disconnected from the system.
Solution: Check the fuse in all units; replace the broken one. - Update firmware and Assistants of the inverter/chargers. And of the GX Device.
Solution: (1) Update the Inverter/charger firmware– (2) Update the Assistants – (3) Update the GX Device firmware.
Systems with multiple slaves per phase
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.
Unable to solve it?
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.
Recovery: auto-restart once the error is gone.
Error 18 – AC Over-voltage on the output of a slave while switched off
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.
Recovery: system remains off until restarted.
Error 19 – Slave does not have AC input!
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.
Recovery: system remains off until restarted.
Error 20 – Configuration mismatch
Extended VE.Bus options are not allowed when a gridcode is selected.
Recovery: system remains off until restarted.
Error 22 – This device cannot function as a slave
This device is an obsolete and unsuitable model. It should be replaced.
Recovery: system remains off until restarted.
Error 24 – Switch-over system protection initiated
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 three things:
- The relay did not open.
- The related current measurement circuit is faulty.
- A multiplus II is used with an external current sensor connected, but the option ‘External current sensor connected’ is not checked in ve.configure.
Error 24 is a very rare error. Possible causes in order of probability:
- (only on MP II models when using external sensor) the option ‘External current sensor connected’ is not checked in ve.configure.
- There is too much AC load connected at the moment the relay needs to switch off. This large current will prevent the relay contacts from opening.
Solution: remove excessive load. See transfer switch capacity in the datasheet for the maximum rating. - The AC input voltage slowly drops before it is being rejected by the Multis. Typically happens in installations with a generator. Especially when combined with AC loads that increase their current draw when the AC voltage drops: by the time that the inverter/charger initiates the disconnect, the current through the relays has increased well beyond the ratings, and is too high to open them.
Solution: Make the Multis or Quattros disconnect earlier: increase lower limit of AC input voltage in VEConfigure3. For example to 210 VAC. The factory setting is 180 VAC. - The back-feed relay has a hardware failure
Solution: Replace faulty unit. - The related current measurement circuit is faulty.
Solution: Replace faulty unit.
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.
Recovery: system remains off until restarted.
Error 25 – Firmware incompatibility
Make sure to use the same firmware in all devices.
Solution: update all devices to the latest available firmware. Instructions here.
Recovery: system remains off until restarted.
Error 26 – Internal error
Should not occur. Switch all equipment off, and then on again; it will then resume operation. Contact Victron Energy if the problem persists.
Recovery: system remains off until restarted.
Remember, our engineering staff are never more than an hour away and can have you back up and running in no time
Give us a call, we will take your details, arrange an engineer, and aim to resolve your solar problem as soon as possible.
Photos are always an effective way to show us your problem too.
Call Bolido Solar on 0330 345 3400 or use the inquiry form and we will call you back
★★★★★
4 weeks ago Read More
Scott designed and carried out a PV cell installation recently. The quote was competitive and the correspondence quick and concise. The fitting was arranged within a week, once the specification was agreed. On site, assisted by Mike, they were helpful and friendly and despite a difficult routing for the cable they came up with a successful solution. The end result is a very tidy, externally & internally, solar fit for the property. Great job and communication throughout, overall I'm very satisfied with their service and would recommend them.
★★★★★
3 weeks ago Read More
Thank you for your outstanding service we received with regards to our solar panels which needed a new inverter. In next to no time, the problem was identified, a replacement ordered, delivered and fitted and the solar panels immediately started to record our readings. I have 100% confidence in recommending Bolido!
★★★★★
2 weeks ago Read More
Very refreshing to get such a thorough and decent service. My company, a solar installations company needed technical assistance on-site for two projects. We also needed help with some of our own IT systems particularly with providing secure internet and network access between us and our clients, primarily for sharing power generation data but also increasingly alongside power usage data. Scott and his team were great with our clients and we just left to it. They were also quick to understand exactly what we wanted to achieve. They carried out all of the work, quickly, cleanly and with the minimum of fuss. We are now in a great position network and IT wise, moving forward we are confident in being able to service bigger clients with however sophisticated a network solution they might require. Highly recommend this company.
★★★★★
1 week ago Read More
Fantastic and thorough service from these guys following birds nesting and ruining the connections on our solar installation. Great communications throughout, and friendly professional service.