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 revision | ||
ve.bus:ve.bus_error_codes [2019-02-11 14:09] – [Error 11 - Relay Test Fault - Installation error or possibly relay failure] mvader | ve.bus:ve.bus_error_codes [2024-07-03 17:09] (current) – [Error 25 - Incompatible VE.Bus configuration] pba | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== VE.Bus Error Codes ====== | ====== VE.Bus Error Codes ====== | ||
===== General ===== | ===== General ===== | ||
- | During first installation, | + | During first installation, |
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**: | ||
+ | |||
+ | ==== 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, |
Trouble shooting: | 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 by LEDs__ | ||
+ | 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; which is typically Overload, Low battery or Temperature. The other units will indicate a VE.Bus error, indicating that they miss one unit. | ||
+ | |||
+ | Note that, due to the automatic restart, it is required to look at the LEDs while the issue is still present and the system is switched off. | ||
+ | |||
+ | __Diagnosing on a GX Device__ | ||
+ | The GX Device will indicate the VE.Bus Error #1 as well as the alarm status for each of the phases: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | Note that, due to the automatic restart, it is required to look at the LEDs while the issue is still present and the system is switched off. Uploading the data to VRM will show a log; see GX manual, section VRM for details; both for systems with internet connection and systems without. | ||
__Diagnosing on VRM__ | __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. | 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 | + | Note for split- and three-phase systems: VRM as well as the GX device |
- | ==== 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 31: | Line 55: | ||
- 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), | - 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), | ||
- 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: | + | - Communication cable error: |
- | | + | |
+ | - 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 45: | Line 73: | ||
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 50: | Line 80: | ||
Check the AC wiring. | Check the AC wiring. | ||
+ | |||
+ | __Recovery: | ||
==== Error 6 - Error in DDC Program ==== | ==== Error 6 - Error in DDC Program ==== | ||
Line 59: | Line 91: | ||
- 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 | + | __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 ==== | ||
+ | |||
+ | This error indicates a failed self-test of the MultiPlus-II or EasySolar-II internal< | ||
+ | |||
+ | 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. | ||
+ | |||
+ | 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 74: | Line 201: | ||
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. | ||
+ | |||
+ | __Recovery: | ||
==== 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, | + | Error 11 indicates a failed automatic self-test of the MultiPlus-II |
- | 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 |
- | When VE.Bus error 11 shows, either the back-feed relay test, ground relay test, or measurement redundancy tests has failed. The tests are automatically performed every time before connecting | + | === Steps to take: === |
- | The three root causes of the error can be (from most common | + | Step 1: Make sure that the units have been [[updating_firmware: |
- | 1) In most cases, when you see Error 11, its due to an installation error:\\ | + | Step 2: Verify |
- | * Please verify | + | |
- | * Line should be connected | + | |
- | * There should be no external connection between N-out and GND | + | |
- | 2) For Australia: contact your distributor. | + | Step 3: Disconnect the L and N wiring from the ACout terminals on each inverter/ |
- | 3) Hardware defect; contact | + | Step 4: Check your Neutral-out connection. In most cases there should be no external connection between ACin-Neutral to ACout-Neutral, |
+ | |||
+ | In Australia, using grid code AS4777.2: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | After configuration, | ||
+ | |||
+ | Step 5: Neutral and line input might be inverted. Check the input connections, | ||
=== Detailed diagnosis of Error 11 === | === Detailed diagnosis of Error 11 === | ||
- | After updating your VE.Bus inverter/ | ||
- | [TODO; add image here] | + | After updating your VE.Bus inverter/ |
+ | |||
+ | Examples of information in the GX Device menus: | ||
+ | |||
+ | {{: | ||
+ | {{: | ||
+ | |||
+ | |||
+ | 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 (#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. | ||
- | |||
Common causes: | Common causes: | ||
* 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 open error: | + | * AC0/AC1 mismatch and UMains |
+ | |||
+ | Other shown error details, listed below, are not related | ||
+ | |||
+ | * 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 [[https:// | ||
+ | |||
+ | __Recovery: | ||
+ | |||
+ | ==== Error 12 - Config mismatch with 2nd mcu ==== | ||
+ | |||
+ | Some Multi models (e.g. MultiPlus-II) have two microcontrollers. | ||
+ | |||
+ | Certain configuration settings, as done with VEConfigure, | ||
+ | In very rare situations it can happen | ||
+ | |||
+ | To solve this error, connect the device to VEConfigure 3, verify/ | ||
+ | |||
+ | Make sure to select the option 'all settings' | ||
+ | |||
+ | __Recovery:__ auto-restart once the error is gone. | ||
- | In all other cases, contact your Victron representative for support. Please provide a photo of the error; and otherwise the 6 digit number at the top. | ||
==== Error 14 - Device cannot transmit data ==== | ==== Error 14 - Device cannot transmit data ==== | ||
Line 117: | Line 286: | ||
Another possibility, | Another possibility, | ||
+ | |||
+ | __Recovery: | ||
+ | |||
+ | ==== Error 15 - VE.Bus combination error ==== | ||
+ | A combination error of VE.Bus products, firmware versions or commands has occurred | ||
+ | |||
+ | This error can occur for example when: | ||
+ | * An Interface-1140 with old firmware is combined with a new Multi firmware | ||
+ | * When external BMS commands are send while a VE.Bus BMS is connected | ||
+ | * 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 123: | Line 304: | ||
Instructions [[updating_firmware: | Instructions [[updating_firmware: | ||
- | ==== Error 17 - Original Master Missing | + | __Recovery: |
+ | |||
+ | ==== 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 | + | Steps to take: |
+ | - In some cases this error can be seen temporarily while using Remote VEConfigure to write a new configuration. \\ __Solution__: | ||
+ | - The most likely cause is a cable-related communication issue on the VE.Bus network: \\ __Solution__: | ||
+ | - 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 | ||
+ | - Update firmware and Assistants of the inverter/ | ||
- | * In some cases this error can be seen temporarily while using Remote VEConfigure to write a new configuration. | + | === Systems with multiple slaves per phase === |
- | * Otherwise, the most likely cause is bad cabling/ | + | 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 | ||
+ | |||
+ | __Recovery: | ||
- | If nothing can be found and the failure persists a hardware error might be the cause. Contact your distributor, | ||
==== 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! ==== | ||
+ | |||
+ | Common cause - System is configured with multiple synchronised inverter/ | ||
+ | |||
+ | 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 ==== | ||
- | There is a back-feed (or ' | ||
- | Error 24 is raised when a Multi or Quattro detects | + | This error indicates that one or more units report feeding back a significant |
- | This should not occur in a correctly installed and sized system. Possible causes | + | 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. |
- | - 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. \\ \\ | + | Error 24 is raised when a Multi or Quattro detects |
- | - 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 | + | |
- | - The back-feed relay has a hardware failure (and is stuck ' | + | |
- | __Diagnostic notes for multi-unit clusters showing error 24__ | + | |
+ | - The related current measurement circuit is faulty. | ||
+ | - A multiplus II is used with an external current sensor connected, but the option ' | ||
- | With all Multis or Quattros set to ' | + | Error 24 is a very rare error. Possible causes in order of probability: |
- | If AC //is// present | + | * (only on MP II models when using external sensor) |
+ | * There is too much AC load connected at the moment the relay needs to switch | ||
+ | * 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 back-feed relay has a hardware failure \\ __Solution__: | ||
+ | * The related current measurement circuit is faulty. \\ __Solution__: | ||
- | 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. | + | __Diagnosing |
- | ==== Error 25 - Firmware incompatibility ==== | + | 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 |
- | Make sure to use the same firmware in all devices. | + | |
- | Solution: update all devices | + | Do make sure to first, always double check option 1 and 2 in above list. Those are the common causes. In case that doesn' |
+ | 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: | ||
+ | |||
+ | ==== Error 25 - Incompatible VE.Bus configuration ==== | ||
+ | The VE.Bus configuration as configured is not allowed. This can be due to the fact that: | ||
+ | - Devices with different firmware versions are used.\\ Solution: Make sure to use the same firmware version in all devices. Update all devices to the latest available firmware. Instructions [[updating_firmware: | ||
+ | - Devices are not compatible with this configuration.\\ Check the **compatibility ID**'s which can be found on the stickers of the units.< | ||
+ | * Make sure that the 4-digit number in the compatibility ID of all units in the VE.Bus system is identical . | ||
+ | * Make sure that units in a single phase (so parallel units) have an identical letter in the compatibility ID. | ||
+ | |||
+ | __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: | ||
+ | |||
+ | ==== Error 30 and 31 - Ghost errors ==== | ||
+ | |||
+ | Both these are non-listed VE.Bus errors. They are caused by a corrupted message on the VE.Bus. | ||
+ | There may be an issue with the RJ45 UTP cable(s) or their connections. | ||
+ | To try to resolve it, make the changes suggested in the “Troubleshooting VE.Bus Network interference” guide. | ||
+ | |||
+ | ==== Error 128 - Connect prevented by failing relay test ==== | ||
+ | |||
+ | Relay test that keeps failing for more than 5 minutes, | ||
+ | |||
+ | If a grid code is selected in VEConfigure, | ||
+ | Error 128 indicates that the relay test keeps failing for more than 5 minutes, and the Quattro-II there for cannot connect to grid. | ||
- | ===== DISQUS ===== | ||
- | ~~DISQUS~~ | ||
ve.bus/ve.bus_error_codes.1549890585.txt.gz · Last modified: 2019-02-11 14:09 by mvader