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-05-27 22:23]
mvader [Error 3 - Not all, or more than, the expected devices were found in the system]
ve.bus:ve.bus_error_codes [2019-06-24 08:08] (current)
mvader [Error 3 - Not all, or more than, the expected devices were found in the system]
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 ==== ==== Network cable quality ====
Line 37: 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 systemWhen 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.+  - DC fuse blown of one or more units in the systemWhen 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 142: Line 145:
 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 slaves. ​You'll see it when its phase-master is no longer communicating ​on the VE.Bus network.+Error 17 will only appear on slaves. ​They report this error when there communication with the phase-master ​has timed out. 
 + 
 +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 [[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. +If after all above steps you are still experiencing ​a VE.Bus ​Error 17contact 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:​start|GX device]] and the inverter/​chargersWe advise ​to replace only the GX device first since that is less work.
-  * 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 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. +
-  *  DC fuse blown of the masterWhen mains is available all units seems to be fine, but as soon as mains fails, ​the non powered units are disconnected from the system.+
  
 ==== 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 ====
Line 170: Line 177:
   * 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 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 back-feed relay has a hardware failure \\ __Solution__:​ Replace faulty unit.
-  * The related current measurement circuit is faulty. \\ __Solution__: ​replace ​faulty unit.+  * The related current measurement circuit is faulty. \\ __Solution__: ​Replace ​faulty unit.
  
 __Diagnosing a parallel, multi or split-phase system?__ __Diagnosing a parallel, multi or split-phase system?__
ve.bus/ve.bus_error_codes.1558988587.txt.gz · Last modified: 2019-05-27 22:23 by mvader