- 53 -
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.
– 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 AC-in-Neutral and AC-
out-Neutral.
– AC0/AC1 mismatch and UMains error: this is
fixed in VE.Bus inverter/charger firmware
version 455.
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.
– Failing steps #2-7.
– AC0 /AC1 mismatch.
– Communication error.
–UMains mismatch.
– Period Time mismatch.
– Drive of BF relay mismatch.
– PE2 open error.
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 support
procedure and contact your dealer. Make sure to
document full system wiring in a diagram, all steps
and tests taken to diagnose and rule out installation
error, and provide a photo of the error details shown
on the CCGX menu.
6.1.2.11 Error 12 - Config mismatch with 2nd
mcu
Some Multi models (e.g. MultiPlus-II) have two
micro-controllers.
Certain configuration settings, as done with
VEConfigure, have to be stored in both micro-
controllers. 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 VEConfig-
ure 3, verify/correct the settings and press 'Send Set-
tings'.
Make sure to select the option 'all settings' instead of
'modified settings’.
6.1.2.12 Error 14 - Device cannot transmit
data
Most probably is 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.
6.1.2.13 Error 16 - VE.Bus dongle is missing
Update firmware to latest version. VE.Bus dongles
are no longer necessary.
6.1.2.14 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.
Steps to take
1. 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.
2. 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 CCGX. 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 Multi’s to
properly make contact. Make sure to machine-
made cabling. Do not use self-crimped cables.
00_00_ZBP45_EN.book Page 53 Monday, October 19, 2020 9:52 AM
To Next Page
Loading...