ve.bus:ve.bus_error_codes
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
ve.bus:ve.bus_error_codes [2021-03-08 16:54] – [Error 11 - Relay Test Fault - Installation error or possibly relay failure] pba | ve.bus:ve.bus_error_codes [2022-04-29 11:29] – [Error 8 - Ground relay test failed] marmour | ||
---|---|---|---|
Line 5: | Line 5: | ||
Firmware update instructions: | Firmware update instructions: | ||
- [[updating_firmware: | - [[updating_firmware: | ||
- | - [[ccgx: | + | - [[ccgx: |
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. | 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. | + | **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. |
==== Network cable quality ==== | ==== Network cable quality ==== | ||
Line 28: | Line 28: | ||
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. | 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. | + | 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. |
- | ==== Error 2 - New and old types MK2 are mixed in the system ==== | + | __Recovery: |
+ | |||
+ | |||
+ | ==== Error 2 - New and old type MK2 protocol | ||
This should never happen, contact Victron service. | This should never happen, contact Victron service. | ||
+ | |||
+ | __Recovery: | ||
==== Error 3 - Not all, or more than, the expected devices were found in the system ==== | ==== Error 3 - Not all, or more than, the expected devices were found in the system ==== | ||
Line 40: | Line 45: | ||
- 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. | - 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. | ||
- 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. | - 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. | ||
- | - 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 non powered | + | - 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 " |
+ | - When switching off so called " | ||
+ | |||
+ | __Recovery: | ||
- | | ||
==== Error 4 - No other device found ==== | ==== 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. | The master device is configured to run in a parallel-, split- and/or three-phase system, but cannot find other devices on the bus. | ||
Line 55: | Line 62: | ||
Faulty cables. Check the communication cables. Don't use self made cables. | Faulty cables. Check the communication cables. Don't use self made cables. | ||
+ | |||
+ | __Recovery: | ||
==== Error 5 - Overvoltage on AC out ==== | ==== Error 5 - Overvoltage on AC out ==== | ||
Line 60: | Line 69: | ||
Check the AC wiring. | Check the AC wiring. | ||
+ | |||
+ | __Recovery: | ||
==== Error 6 - Error in DDC Program ==== | ==== Error 6 - Error in DDC Program ==== | ||
Line 69: | Line 80: | ||
- re-configure the system | - re-configure the system | ||
- | ==== Error 7 - VE.Bus BMS detected, but not configured ==== | + | This error can also occur in newer firmwares when a VE.Bus BMS is connected |
- | A VE.Bus BMS device | + | |
- | Solution: configure the use of the VE.Bus BMS in one of the Assistants. | + | __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/ | ||
+ | |||
+ | __Recovery: | ||
==== Error 8 - Ground relay test failed ==== | ==== Error 8 - Ground relay test failed ==== | ||
- | Indicates | + | This error indicates |
+ | |||
+ | 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/ | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | 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/ | ||
+ | |||
+ | 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), | ||
+ | |||
+ | 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/ | ||
+ | |||
+ | 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/ | ||
+ | |||
+ | In case bypassing the Neutral | ||
+ | |||
+ | 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. | ||
+ | - Check by first disconnecting all loads: open the circuit breakers. | ||
+ | - Restart system and check if it can switch to the grid without error. | ||
+ | - Then measure with a multi meter that there is no continuity between the neutral and the ground. (Alternatively disconnect all loads or sub-circuits, | ||
+ | |||
+ | While testing this, be aware that: | ||
+ | - 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. | ||
+ | - 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/ | ||
+ | |||
+ | 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. | ||
- | See Error 11 for details & instructions. | + | 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 ==== | ==== Error 10 - System time synchronisation problem ==== | ||
This typically happens during a system restart, and is then not a real error; no need to investigate. | 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 | + | For example this screenshot from the GX device: |
{{ : | {{ : | ||
Line 93: | Line 193: | ||
Other possibility: | 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. | 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: | ||
==== Error 11 - Relay Test Fault - Installation error or possibly relay failure ==== | ==== Error 11 - Relay Test Fault - Installation error or possibly relay failure ==== | ||
Line 99: | Line 201: | ||
If a grid code is selected in VEConfigure, | If a grid code is selected in VEConfigure, | ||
- | |||
- | Ground relays are also tested and can trigger an Error 8. 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. | ||
=== Steps to take: === | === Steps to take: === | ||
Line 112: | Line 212: | ||
Step 4: Check your Neutral-out connection. In most cases there should be no external connection between ACin-Neutral to ACout-Neutral, | Step 4: Check your Neutral-out connection. In most cases there should be no external connection between ACin-Neutral to ACout-Neutral, | ||
- | In Australia, it is possible if required | + | In Australia, using grid code AS4777.2: |
{{: | {{: | ||
Line 133: | Line 233: | ||
* A six digit number; which contains all the details | * A six digit number; which contains all the details | ||
- | * An error ID (#16 for example). Note that this does not count the the number of VE.Bus errors; its just a unique ID that can help recognizing that a new error has occured. | + | * 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 | * Flags | ||
* The failed step; it counts backwards: step 9 -> 8 -> 7 and so forth. | * The failed step; it counts backwards: step 9 -> 8 -> 7 and so forth. | ||
Line 140: | Line 240: | ||
* Failing step #8: check that line and neutral have not been swapped. Unlike non-grid code installations; | * Failing step #8: check that line and neutral have not been swapped. Unlike non-grid code installations; | ||
- | * PE2 closed error or GND Relay Error: check that AC-out Neutral is not wired to ground, or AC-in Neutral + ground. Short circuiting them is not allowed without specific firmware and grid code. Also, check that there is no leakage between Neutral and ground, for example because broken consumer. Start by disconnecting all loads: open all the circuit breakers. Then test to confirm there is no continuity between ACin-Neutral and ACout-Neutral. | ||
* AC0/AC1 mismatch and UMains error: this is fixed in VE.Bus inverter/ | * AC0/AC1 mismatch and UMains error: this is fixed in VE.Bus inverter/ | ||
- | 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. | + | 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, |
* Failing steps #2-7. | * Failing steps #2-7. | ||
Line 151: | Line 250: | ||
* Period Time mismatch. | * Period Time mismatch. | ||
* Drive of BF relay mismatch. | * Drive of BF relay mismatch. | ||
- | * PE2 open error. | ||
=== Unable to solve? === | === 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 [[https:// | 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 [[https:// | ||
+ | |||
+ | __Recovery: | ||
+ | |||
==== Error 12 - Config mismatch with 2nd mcu ==== | ==== Error 12 - Config mismatch with 2nd mcu ==== | ||
Line 166: | Line 267: | ||
Make sure to select the option 'all settings' | Make sure to select the option 'all settings' | ||
+ | |||
+ | __Recovery: | ||
+ | |||
==== Error 14 - Device cannot transmit data ==== | ==== Error 14 - Device cannot transmit data ==== | ||
Line 171: | Line 275: | ||
Another possibility, | Another possibility, | ||
+ | |||
+ | __Recovery: | ||
+ | |||
+ | ==== 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: | ||
==== Error 16 - VE.Bus dongle is missing ==== | ==== Error 16 - VE.Bus dongle is missing ==== | ||
Line 176: | Line 292: | ||
Instructions [[updating_firmware: | Instructions [[updating_firmware: | ||
+ | |||
+ | __Recovery: | ||
==== Error 17 - Phase master missing ==== | ==== Error 17 - Phase master missing ==== | ||
Line 193: | Line 311: | ||
=== Unable to solve it? === | === 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 [[venus-os: | 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 [[venus-os: | ||
+ | |||
+ | __Recovery: | ||
==== Error 18 - AC Over-voltage on the output of a slave while switched off ==== | ==== 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. | 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: | ||
==== Error 19 - Slave does not have AC input! ==== | ==== Error 19 - Slave does not have AC input! ==== | ||
Line 202: | Line 324: | ||
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), | 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), | ||
+ | |||
+ | __Recovery: | ||
+ | |||
+ | ==== Error 20 - Configuration mismatch ==== | ||
+ | |||
+ | Extended VE.Bus options are not allowed when a gridcode is selected. | ||
+ | |||
+ | __Recovery: | ||
==== Error 22 - This device cannot function as a slave ==== | ==== Error 22 - This device cannot function as a slave ==== | ||
This device is an obsolete and unsuitable model. It should be replaced. | This device is an obsolete and unsuitable model. It should be replaced. | ||
+ | |||
+ | __Recovery: | ||
==== Error 24 - Switch-over system protection initiated ==== | ==== Error 24 - Switch-over system protection initiated ==== | ||
Line 212: | Line 344: | ||
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. | 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 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 relay did not open. | ||
- The related current measurement circuit is faulty. | - The related current measurement circuit is faulty. | ||
+ | - A multiplus II is used with an external current sensor connected, but the option ' | ||
Error 24 is a very rare error. Possible causes in order of probability: | Error 24 is a very rare error. Possible causes in order of probability: | ||
+ | * (only on MP II models when using external sensor) the option ' | ||
* 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__: | * 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__: | ||
* 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/ | * 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/ | ||
Line 246: | Line 380: | ||
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. | 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: | ||
==== Error 25 - Firmware incompatibility ==== | ==== Error 25 - Firmware incompatibility ==== | ||
Line 252: | Line 388: | ||
Solution: update all devices to the latest available firmware. Instructions [[updating_firmware: | Solution: update all devices to the latest available firmware. Instructions [[updating_firmware: | ||
+ | __Recovery: | ||
==== Error 26 - Internal error ==== | ==== 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. | Should not occur. Switch all equipment off, and then on again; it will then resume operation. Contact Victron Energy if the problem persists. | ||
+ | __Recovery: | ||
===== DISQUS ===== | ===== DISQUS ===== | ||
~~DISQUS~~ | ~~DISQUS~~ |
ve.bus/ve.bus_error_codes.txt · Last modified: 2023-06-27 09:34 by jpasop