User Tools

Site Tools


ve.bus:ve.bus_error_codes

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
ve.bus:ve.bus_error_codes [2019-02-12 09:42]
simonhackett [Error 24 - Switch-over system protection initiated]
ve.bus:ve.bus_error_codes [2019-09-10 23:08] (current)
mvader [Error 10 - System time synchronisation problem]
Line 1: Line 1:
 ====== VE.Bus Error Codes ====== ====== VE.Bus Error Codes ======
 ===== General ===== ===== 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. +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 [[venus-os:​start|GX device]]
  
 Firmware update instructions:​ Firmware update instructions:​
Line 8: Line 8:
  
 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.
 +
 +==== Network cable quality ====
 +
 +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.
  
 ===== VE.Bus Error Codes ===== ===== VE.Bus Error Codes =====
 ==== Error 1 - Device is switched off because one of the other phases in the system has switched off ==== ==== 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.+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: Trouble shooting:
Line 31: Line 39:
   - 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.   - 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.   - 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.+  - 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 units are disconnected from the system. 
   ​   ​
 ==== Error 4 - No other device found ==== ==== Error 4 - No other device found ====
Line 63: Line 73:
  
 Solution: configure the use of the VE.Bus BMS in one of the Assistants. Solution: configure the use of the VE.Bus BMS in one of the Assistants.
 +
 +==== Error 8 - Ground relay test failed ====
 +
 +Indicates a failed automatic Ground relay self-test on the MultiPlus-II or EasySolar-II relays.
 +
 +See Error 11 for details & instructions.
  
 ==== Error 10 - System time synchronisation problem ==== ==== Error 10 - System time synchronisation problem ====
Line 74: Line 90:
  
 Note: System restarts can also be triggered when using Remote VEConfigure. 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 - Relay Test Fault - Installation error or possibly relay failure ==== ==== Error 11 - Relay Test Fault - Installation error or possibly relay failure ====
  
-This error only applies to the MultiGrid, ​MultiPlus-IIEasySolar-II ​and other inverter/​chargers with a dual backfeed relayAs part of grid-code compliance; the device tests verifies that its internal relays function properly.+Error 11 indicates a failed automatic self-test of the MultiPlus-II ​or EasySolar-II ​relaysIt is often a result ​of an installation or wiring issue, though it can also be triggered by a hardware failure.
  
-The relays are tested when a grid code is selected in VEConfigure. When the grid-code is set to None, the tests are not performed.+If a grid code is selected in VEConfigure, then the backfeed relays are tested every time before connecting ​to the mains.
  
-When VE.Bus error 11 showseither ​the back-feed ​relay test, ground relay test, or measurement redundancy tests has failed. The tests are automatically ​performed ​every time before connecting to mains.+The other tests that raise Error 11 when they fail concern the Ground Relay. 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.
  
-The three root causes of the error can be (from most common ​to least common):+=== Steps to take===
  
-1) In most cases, when you see Error 11, its due to an installation error:\\  +Step 1: Make sure that the units have been [[updating_firmware:​updating_ve.bus_products|updated ​to the latest firmware version]]There have been various VE.Bus error 11 related improvements ​in the firmware.
-  * Please verify ​that the neutral is connected ​to earth on the supply sideIn many countries this is done by the utility ​in the transformer cabinet (a TN network). +
-  * Line should be connected to the corresponding Line input on the inverter/​charger,​ same for Neutral. A swapped connection results in Error 11. +
-  * There should be no external connection between N-out and GND+
  
-2) For Australiacontact ​your distributor.+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 on the unit. This will create a safety hazard and will prevent RCD devices from working. Contact a licensed electrician if in doubt
  
-3) Hardware defect; contact your distributor ​for a replacement.+Step 3: Disconnect the 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 problem with a connected load (e.g. a leakage between load neutral and ground).
  
-=== Detailed diagnosis of Error 11 === +Step 4: Check your Neutral-out connectionThere should be no external connection from Neutral-out ​to Neutral-in ​or to EarthIf your local grid code requires a bypass between Neutral-in and Neutral-outcontact your Victron representative for solution.
-After updating ​your VE.Bus inverter/​charger ​to firmware 454 or higher; and running Venus OS v2.23~3 or later, a detailed VE.Bus Error report becomes available:+
  
-[TODOadd image here]+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. 
 + 
 +=== 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 is most likely faulty. Follow the support procedure. 
 + 
 +Make sure to provide a photo of the error details shown on the GX Device menu. 
 + 
 +=== Detailed diagnosis of Error 11 === 
 +After updating your VE.Bus inverter/​charger to firmware 454 or higherand running Venus OS v2.23 or later, a detailed VE.Bus Error report is available in the GX device menu, under MultiPlus -> Alarm Status -> VE.bus error. The information shown is:
  
-It shows: 
   * A six digit number; which contains all the details   * A six digit number; which contains all the details
-  * A counter+  * 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.
   * 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.
- 
  
 Common causes: 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.   * 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.
-  * PE2 open error: check that AC-out Neutral is not wired to Ground. Short circuiting them is not allowed. 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.+  * PE2 open error or GND Relay Error: check that AC-out Neutral is not wired to Ground. Short circuiting them is not allowed. 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
 +  * AC0/AC1 mismatch and UMains error: there has been a fix for that in VE.Bus inverter/​charger firmware version 455.
  
-In all other casescontact your Victron representative ​for supportPlease provide ​photo of the error; and otherwise ​the 6 digit number at the top.+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 casealso when one of below errors shows, 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. 
 +  * PE2 open error. 
 + 
 +The report is found by navigating to the Device list (top level menu), then going in to the Multi or Quattro inverter/​charger page, then to the bottom, Alarm Status, then to the bottom again, in to the menu VE.Bus Error 11 report. 
 + 
 +Now you will see list of all devices in the system; and their latest VE.Bus Error 11 details. Enter the menu for an explanation of the code. 
 + 
 +Examples of information in the GX Device menus: 
 + 
 +{{ :​ve.bus:​error11-ccgx3.jpg?​nolink |}} 
 +{{ :​ve.bus:​error11-ccgx4.jpg?​nolink |}} 
 +==== 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'​.
 ==== Error 14 - Device cannot transmit data ==== ==== Error 14 - Device cannot transmit data ====
  
Line 123: Line 172:
 Instructions [[updating_firmware:​updating_ve.bus_products|here]]. Instructions [[updating_firmware:​updating_ve.bus_products|here]].
  
-==== Error 17 - Original Master Missing ​====+==== 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. ​ 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 slavesYou'll see it when its phase-master ​is no longer ​communicating ​on the VE.Bus network.+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 socketsIf that doesn't solve it, replace all network cables, including the cable to the [[venus-os:start|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__:​ [[updating_firmware:​updating_ve.bus_products|Update the Inverter/​charger firmware]] - [[assistants:​how_to_update_an_assistant|Update the Assistants]] - [[ccgx:​firmware_updating|Update the GX Device firmware]].
  
-  * In some cases this error can be seen temporarily while using Remote VEConfigure to write new configuration. +=== Systems with multiple slaves per phase === 
-  * Otherwise, the most likely cause is bad cabling/​contacts ​on the VE.Bus: Check cabling ​and contactsMake sure to also inspect ​the female RJ-45 socketsinstead 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.+Error 17 can show on one or more slaves in phase (visible by looking at the LEDsnot 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 cablingDepending on the situation, they might advice ​to replace ​the [[venus-os:start|GX device]] and the inverter/​chargers. We advise to first replace cablesand if that doesn'​t help then thereafter ​only the GX device at first, since that is less work than replacing ​the inverter/​chargers.
  
-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 ==== ==== 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. 
Line 139: Line 196:
  
 ==== Error 24 - Switch-over system protection initiated ==== ==== 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 the back-feed relay during a period when the relay should be open - which means that the relay did not open when it should.+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: 
 + 
 +  ​The relay did not open
 +  - The related current measurement circuit is faulty. 
 + 
 +Error 24 is a very rare error. 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. 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
  
-This should not occur in a correctly installed and sized system. Possible causes in order of probability:​+__Step 1__
  
-  - 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. \\ \\ +Start with making ​video of all units and their LED codeDo not first reset the system; ​and do not reset it after making the video either.
-  - 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 systems showing error 24 where a stuck '​on'​ relay is suspected__+__Step 2__
  
-In a single unit systemturn the unit '​off' ​on the front panel rocker switch and apply AC input powerMeasure ​the AC output. If AC voltage ​is present, the unit is faulty (stuck relay).+Completely disconnect all AC wiring, both in- and out, on all unitsMake 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.
  
-In a three-unitthree-phase cluster (only one unit per phase), the faulty unit can be identified in the same way. As for the single unit caseany unit presenting ​AC output ​voltage when the rocker switch is set to '​off'​ is faulty.+__Step 3__ 
 +Nowwith an ohm-metermeasure ​the resistance between ​the neutral terminals on AC-input and the AC-outputA working ​unit will show no connection between these terminals. And also measure the resistance between the Line terminals of AC-input and AC-output.
  
-You can also determine the faulty unit(s) by just listening for units that are //audibly humming// while their front panel rocker switch is set '​off'​. The humming is because AC power is being applied ​to the internal circuitry when it should not be.+faulty unit will measure zero or close to zero resistance.
  
-Where there are multiple ​units hardwired ​in parallel (multi-unit/​single phase system, or a three-phase cluster with 6 or more units), then there is an additional diagnostic challenge. ​In these systems, the faulty unit will be feeding energy out from its AC output ​and this energy will then flow into to the other (good) units via their respective ​AC output ​terminals. This results in //all// units that are parallel-wired appearing to be faulty, and all units concerned humming while set to '​off'​.+Good units will measure discontinuity between the Line in and out terminals. And measure ​few hundred ohms between the neutral ​In and Out AC terminals.
  
-The most conclusive way to determine which unit is faulty in this case is to un-wire the AC outputs of all the units concerned to prevent the cross-feeding of AC energy via the AC outputs. Then apply AC power with all units still set to '​off'​ on their front panel rocker switches. The faulty unit is the one that is still humming and that is still presenting AC voltage on its output terminals. 
 ==== Error 25 - Firmware incompatibility ==== ==== Error 25 - Firmware incompatibility ====
 Make sure to use the same firmware in all devices. ​ Make sure to use the same firmware in all devices. ​
ve.bus/ve.bus_error_codes.1549960928.txt.gz · Last modified: 2019-02-12 09:42 by simonhackett