Problem: If the Cerbo GX and Phoenix 24/3000 are connected via the VE.Bus cable, an attempt to power off the Phoenix via the physical Inverter Remote switch will cause the Phoenix to cycle on and off repeatedly forever (when the Phoenix Front Panel switch is on, and the Cerbo is powered).
This makes the Inverter Remote dangerous.
But the Inverter Remote is required to control the Phoenix, should the Cerbo GX fail. (This is on a boat and of course the inverter is buried in a compartment that is a challenge to get to).
Inverter Remote = a switch connected to terminal block “H” (Appendix A)
How can this be fixed? When connected the Phoenix and the Cerbo GX conspire to make both the Phoenix front panel switch and the Cerbo’s virtual switch control the same one and only on/off state. Why can’t the Inverter Remote switch play that same game?
That’s the behaviour I want. When the Cerbo GX is not connected, it works great. The Switch on the Phoenix front panel I leave on (it’s buried in a cabinet that’s hard to get to). The “remote” that is wired to terminal H is how I power it on/off.
But, when the Cerbo GX is connected, there is a dangerous scenario: The Phoenix front panel switch is on, the Cerbo GX is powered. Using the remote to turn it off causes the problem: An infinite loop of power cycling. I suspect it goes like this: The Phoenix sees the “remote” go off and turns itself off. The Cerbo’s “virtual switch” is still on and so it commands the Phoenix to power up. Once up the Phoenix sees that the “remote” says off, and so power itself down. This goes on forever. The connection with the Cerbo seems to be exercising a bug.