The most straight forward is to configure every multi as standalone and check whether it can switch to the grid without error. Since unit X can display the error while the root is in unit Y there is no easy way to find out. This is a hardware defect in the inverter/charger, or in at least one of the inverter/chargers in a system consisting of multiple units. Possible cause #4: Faulty ground relay, or its detection circuit
#Phoenix os error 18 series
Disconnecting all AC-out wires from each individual unit will not work, as doing so will result in a series of other errors. 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. This could be either a defect in the wiring or a defect in one of the loads in the system. Possible cause #3: Leakage or short in the loads of the inverters
In case bypassing the Neutral is mandatory by local regulations, such as in certain regions in Australia, then select the corresponding “Neutral path externally joined” grid-code in the configuration 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/charger. Neutral AC-in is connected to Neutral AC-out while not configured as such in the software. Possible cause #2: Neutral is bypassed intentionally If the neutral-out is connected to GND externally then the unit will always detect that the GND relay fails to open. Possible cause #1: Neutral-out externally tied to GND 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. Recovery: auto-restart once the error is gone.Įrror 2 - New and old type MK2 protocol mixed in the system Note for split- and three-phase systems: VRM as well as the GX device indicate on which phase there is an Overload, Low battery or Temperature alarm. You will see Overload and Temperature alarms occurring at the same time as VE.Bus Error 1. 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.įirst make sure that Automatic alarm monitoring is enabled that is necessary to create the Overload and Temperature errors in the log.
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. The GX Device will indicate the VE.Bus Error #1 as well as the alarm status for each of the phases: The other units will indicate a VE.Bus error, indicating that they miss one unit. 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.
#Phoenix os error 18 code
Look for the failing phase, which will be the phase that is not showing VE.Bus Error Code 1. When this happens, the other phases will show VE.Bus Error Code 1. Commonly because of a Low battery, Overload or High temperature alarm. One of the phases in a multi-phase system has failed.
0 kommentar(er)
