Error #67 on MPPT RS 450/200 after BMS control already disabled

DIY
, , , , , ,
1

Has anyone got an MPPT RS running without a BMS? I’ve got a three-phase setup: 3x MultiPlus-II 48/10000 on an Ekrano, MPPT RS 450/200, and a Docan bank with CAN BMS, all on VE.Can.

When I wanted to take the BMS out I first set BMS control to “no BMS” on the Ekrano, then disabled BMS control in the MPPT via VictronConnect as well. Looked fine, but as soon as the BMS was actually disconnected I still got error 67 and the whole system went down. Plug the BMS back in and everything runs again, every time.

Does the MPPT need a full factory reset, or is it picking up from VE.Can that a BMS should be there? And why do the Multis go down too when it’s only the MPPT throwing an error?

4

I have done something similar with varied results.

Sometimes there are no issues and there is no control as you want, but other times we get the error. I think the difference is how the BMS interaction is done.

Since yours is not on the official list unexpected behaviours like these, should be expected. One system had to have DVCC completely off.

The error 67 is a system wide one, so will affect everything.

5

Did you also performed the Reset function in the BMS Control section?

1
1383×182 9.32 KB

2
2321×195 16.8 KB

6

To switch from managed to unmanaged needs the devices to all be power cycled. It isn’t dynamic.

7

Thanks. So the Multiplussen need to be cycled as well?

8

Yes, this is how I did it. Sorry, didn’t describe it accurately.

9

Correct they do need to be power cycled after BMS is removed in dvcc

10

Hi all, power cycling didn’t solve it. After setting BMS control to none on the Ekrano, disabling it in the MPPT and power cycling everything, the Multis still throw a low battery alarm and stop charging. Battery is fine at that point, 53.4V and 77% SOC, BMS cable still connected, and the GX logs BMS lost. In island mode that alarm takes the whole system down. Setting BMS control back to the battery clears it instantly, no restart needed. Is ESS on lithium just not meant to run without GX BMS control?

11

Thanks. I didn’t respond to your answer earlier, because I didn’t know what to make of it, but now it seems to make sense. On the system where DVCC had to go off completely, did ESS keep working normally? And how did you handle charge limits then, just the absorption and float settings in the Multis and MPPT?

My batteries have a BMS and contactor per module, so I’m a bit worried that without DVCC the first thing to stop an overcharge is a contactor opening under load. But I am seriously considering turning off DVCC and managing everything through Node-RED.

12

When you remove BMS control, everything has to be restarted. Even the inverter. It is a system wide change. Every component is affected.

Ess works normally without BMS control.

Properly programmed everything works well. I have quite a few times run smart batteries dumb this way.

I have on one system (because the BMS firmware and control is plain stupid) made a virtual battery set that as the default battery in Dvcc - that uses some information from the actual BMS (like the all important high and low cells) and controls the system that way.

13

Yes, I did restart everything, but it seems at least the Multiplusses are still expecting a BMS and throw a low battery alert. My next test will be turning off DVCC entirely.

Wow, making a virtual battery sounds very complicated! How did you go about doing it? Did you need to plug in a cable to simulate a BMS-signal? What external hardware was required? Or could you do it with all software?

14

No external hardware. The BMS is still connected to the GX but it’s not the controlling device.

The virtual battery is created in Node Red. Which you were already talking about

15

Ok, I’ve gone with the virtual battery route and things are looking good so far. No glitches or errors. I combined it with the firmware upgrade of the Mutliplusses to the latest version. Fingers crossed that the whole setup will be stable enough from now on.