User Tools

Site Tools


ve.bus:ve.bus_error_codes

Differences

This shows you the differences between two versions of the page.


Previous revision
ve.bus:ve.bus_error_codes [2019-02-08 23:09] – external edit 127.0.0.1
Line 1: Line 1:
-====== VE.Bus Error Codes ====== 
-===== General ===== 
-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 Color Control GX.  
- 
-Firmware update instructions: 
-  - [[updating_firmware:updating_ve.bus_products|for VE.Bus products]] 
-  - [[ccgx:firmware_updating|for Color Control GX]] 
- 
-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. 
- 
-===== 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 an 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. 
- 
-==== Error 2 - New and old types MK2 are mixed in the system ==== 
- 
-This should never happen, contact Victron service. 
- 
-==== Error 3 - Not all, or more than, the expected devices were found in the system ==== 
- 
-Possible causes and solutions: 
-  - 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. 
-  - 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. 
-   
-==== 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. 
- 
-==== 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. 
- 
-==== Error 6 - Error in DDC Program ==== 
- 
-This means: error in an Assistant. To solve, follow these steps: 
- 
-  - update VE.Bus firmware in all devices to the latest firmware. Instructions [[updating_firmware:updating_ve.bus_products|here]]. 
-  - download the latest VEConfigure and make sure it has downloaded all the latest Assistants.  
-  - re-configure the system 
- 
-==== Error 7 - VE.Bus BMS detected, but not configured ==== 
-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. 
- 
-==== 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 Color Control GX: 
-{{ :vebus:vebus_error_1_3_10.png?nolink |}} 
- 
-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. 
- 
-==== Error 11 - Relay Test Fault - Installation error or possibly relay failure ==== 
- 
-This error only applies to the MultiGrid, MultiPlus-II, EasySolar-II and other inverter/chargers with a dual backfeed relay. As part of grid-code compliance; the device tests verifies that its internal relays function properly. 
- 
-This error will show when the back-feed relay test of the inverter/charger fails. The relays are automatically self-tested every time before the inverter/charger connects to mains. 
- 
-The three root causes of the error can be (from most common to least common): 
- 
-1) In most cases, when you see Error 11, its due to an installation error:\\  
-  * Please verify whether the incoming AC is a TN network 
-  * Line and Neutral should be connected to the corresponding L and N input on the inverter/charger. A swapped connection results in Error 11 
-  * There should be no external connection between N-out and GND 
- 
-2) For Australia: contact your distributor. 
- 
-3) Once of the relays in the unit is broken; contact your distributor for a replacement. 
- 
-==== 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. 
- 
-==== Error 16 - VE.Bus dongle is missing ==== 
-Update firmware to latest version: VE.Bus dongles are no longer necessary. 
- 
-Instructions [[updating_firmware:updating_ve.bus_products|here]]. 
- 
-==== Error 17 - Original Master Missing ==== 
-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.  
- 
-Error 17 will only appear on slaves. You'll see it when its phase-master is no longer communicating on the VE.Bus network. 
- 
-  * In some cases this error can be seen temporarily while using Remote VEConfigure to write a new configuration. 
-  * Otherwise, the most likely cause is bad cabling/contacts on the VE.Bus: Check cabling and contacts. 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. 
- 
-If nothing can be found and the failure persists a hardware error might be the cause. Contact your distributor, and also report the exact LED indication of the Master and all slaves in that phase. 
-==== 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.  
- 
-==== Error 22 - This device cannot function as a slave ==== 
-This device is an obsolete and unsuitable model. It should be replaced. 
- 
-==== Error 24 - Switch-over system protection initiated ==== 
-There is a back-feed (or 'anti-islanding') relay present on the AC input of each unit. This relay is automatically opened during periods of AC input loss (e.g. grid or generator failure) as a safety mechanism to avoid the back-feeding of AC energy 'upstream'.   
- 
-Error 24 is raised when a Multi or Quattro detects current flowing through a back-feed relay during a period when the relay should be open - which means that the relay did not open when it should. 
- 
-This should not occur in a correctly installed and sized system. Possible causes in order of probability: 
- 
-  - 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. \\ \\ 
-  - The AC input voltage slowly drops before it is being rejected by the Multis. Typically happens in installations with a genset. Especially when combined with AC loads that increase their current draw when the AC voltage drops: at the moment the Multis or Quattros decide to switch off, the current through the relays 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 (and is stuck 'on')\\ \\ Solution: Replace faulty unit. 
- 
-__Diagnostic notes for multi-unit clusters showing error 24__ 
- 
-With all Multis or Quattros set to 'off' on their front panel rocker switches and with AC power presented to the input of the system, there should be no AC present on the AC-1 output terminals. 
- 
-If AC //is// present on the output side while the units are switched off, this energy is flowing via the stuck back-feed relay. AC is also being back-fed into the inverter output circuitry as a result, and this may result in all units audibly 'humming' (even though they are set to be 'off'). 
- 
-In a parallel-wired cluster, one faulty relay will make it appear that all units wired in parallel are faulty. To determine which unit is really at fault, power the cluster down and un-wire all AC inputs and all AC outputs. Then apply DC battery power and configure each unit into standalone mode so that it starts to invert and present power to its AC output. Any unit where there is //also// AC energy present on the //input// terminals has a stuck back-feed relay and needs to be replaced. 
- 
-==== Error 25 - Firmware incompatibility ==== 
-Make sure to use the same firmware in all devices.  
- 
-Solution: update all devices to the latest available firmware. Instructions [[updating_firmware:updating_ve.bus_products|here]]. 
- 
- 
-==== 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. 
- 
- 
-===== DISQUS ===== 
-~~DISQUS~~ 
  
ve.bus/ve.bus_error_codes.txt · Last modified: 2024-02-05 07:37 by mvader

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki