Ignores discharge power to float voltage

That the charge Voltage is raised, when feedin is enabled, is “normal” - Otherwise the battery could not be hold at 100%. If battery and MPPTs would run at the same voltage, the multis would draw power from both, when trying to feedin.

That would be acceptable, but Victron is still moving with this voltage up and down in regione of 0.4V which results in battery charging and discharging and charging and discharging. 55.2V wants BMS, Victron adds 0.4V fine so total is 55.6V. But MPPTs voltage is moving from 55.2 to 55.6…just a 0.1V would cause problems.
By your answer “to keep battery up” i fell like you admit that battery must disable charging mosfets…because that is a “old style” behavior.

So, the MP has to act as “Man in the middle” to grab the power from the mppts, but leave the battery “idle”.

Yeah this is the issue with DC coupling design and I think it is just wrong for these types of BMSes (which there will more and more). If battery wants some voltage, you just cannot move up and down as you like, otherwise = current flows. For MPPTs to output more power, they need to move with voltage → problem. What is a problem and victron could react to is, when battery is discharging power with feeding enabled goes to grid…why? Victron see that so it can increase voltage a bit to hande it.

And to the end, you have on victron community few threads with this issue, I have access to a lot of installations with this issue, it is not about resistances.

The Voltage Up/Down is not by design. My System (2 MPPT, MPPT RS and Pylontech) is not doing that - at least not at the values your graphs show. There are a lot of users using BMS Like the JK with no Issues as well.

I think you should consider it’s an hardware issue, that may cause this. It could be caused by the installation itself (wires, terminals, breakers, fuses), or ofc. by a single defective unit, that has an Issue to keep a constant voltage. (Broken capacitors or sth.)

I would try each MPPT alone, see if the issue is present, if it just happens with multiple mppts, if it just happens with ONE certain mppt, then eventually swap the mppt-connections, see if the problem “moves” to identify whether it is “path” related or device related, etc.

It may not be caused by the mppts, could be caused by the BMS itself or by the multis. Just from voltage curves it’s not really possible to tell that. Hence, starting with the easiest to “remove” parts may be a good idea. If you are lucky, you immediately find a setting without issues, then you know “its one of these 3” in either way.

All JK users with enabled export have this problem. JBD with better settings (charge voltage setpoint) has this issue as well.
It is not about resistances and HW issues. Check video and focus on MP voltage (DC bus voltage) based on solar array power. Less sun → lower voltage → battery discharges but to grid as well. More sun → higher voltage → battery charges.
In this moment BMS wants 54.8V from Victron. It gives maximum 55.2 based on 0.4V addition. But fluctuates between these two values.

Pylontech is not doing that, we need to find out why. My guess is charging mosfets disabled, bad BMS voltage calibration and maybe combination with Victron 52.4V limit.
My next tests will be - control voltage by victron, dvcc used only for SOC.
Set JK to disable charge mosfets when on 100%.

@dognose Have you seen my video? I’m experience similar problems as well. I’m using a JKBMS (V15) (2x = 32kW) latest firmware, Multi RS Solar, 2x MPPT.


MP-II 5000VA, MPPT 250/100, 5kWh Battery, JK Inverter BMS 100A V15.41

OK my first test to encounter charging discharging problem when export is enabled went as predicted. I simulated old fashioned “charge to the limit” BMSes.
BMS settings: RCV set to 3.599V per cell (totall charging voltage 57.5V plus 0.4V from Victron = 57.9V) , OVP to 3.6V to be sure I do not overcharge the cells but still hit OVP alarm and force battery to disable charging mosfets…
And guess what… it works… 0 current flow. Battery is kept charged at 100% while still easily exporting to the grid.


What is a “problem” is that battery in this case battery sends OVP alarm to Victron. If user is informed that it is normal, it can be acceptable.

Maybe I will count with the 0.4V addition and set charging voltage 0.35V lower and still hit OVP. I will send updates.
Next test with DVCC on but voltage by Victron later.

1 Like

Hello Raphael, we tried that settings, but it did not work. I do not know if something was done wrong, but when JK-BMS was taken of control it refuses to discharge battery after. Only removing of communication cable helped. But without comms there is no SOC anymore. Could you help?

So you checked all the settings again and performed all the steps and it still does not work?

I have a new guess: The JK-BMS just shows phantom currents. It might have to do with the way it measures currents. The integration time of the current measuring is likly too short and it shows wrong values with high fluctuation. Also these wrongly measured currents are probably not sent to the GX-Device frequent enough. I would consider that a software bug that will probably not be fixed since V15.41 is officially the last Firmeware for hardware 15 BMS. Can you check with a clamp meter, if there is a actuall current flowing?

There is a current flowing. And by logic of DC coupling it makes sense, if Victron raises voltage on DC bus → power flows where it can and it flows to a battery which still accepts power.

Dear Community

This thread has proven very helpful to me and I would like to say thank you to all who contributed to it.

Not only did it help to get rid of the mysterious hasty discharge events right after reaching a full charge (first I thought it’s some kind of battery life algorithm), now I also know how to tackle nervous charge/discharge behavior at the top end while keeping useful DC feed-in enabled.

To make it easy for anonymous readers, here’s what I did in short that solved the problem:

  • leave float enabled in your BMS (thx @dick ) , but set RCF and RFV to almost identical (3.45 and 3.44 respectively) (*)
  • use VE.configure to set absorption and float voltages in the Multiplus accordingly (*)
  • do not forget the same settings in your MPPT if you have any (*)
  • realize that this is perfectly normal charging behavior for LFP (thx @dognose )
  • be happy not to blow any fuses and keep a few % more in your battery for the night
  • (disabled DC feed-in until updates will solve erratic behavior)

(*): I’m surprised to see that this is not done automatically when selecting the LFP profile

Besides I finally understand why my three JKs were never aligned with their SoC (thx @idobuiter and again @dick ). Calibration maybe also will improve things further (thanks again @idobuiter ).

This community is awesome, including the direct involvement of the manufacturer! Thank you.

Some background:

Our system here in Switzerland in our basement is running to provide nighttime energy to 8 neighbouring houses in total. It’s a new thing that we are allowed to have virtual clusters and act as one customer. (There is even just one bill that we have to split internally. Data of every smartmeter is provided for free by law for this purpose.) External control via grid setpoint, data collected with whatwatt. Peak shaving, dynamic pricing and pooling for grid stabilization are to come, but not a reality for private households just yet.

You might be surprised to hear that just three MP2 3000 (got them used) and 50 kWh are sufficient for this purpose. 95% of the time power is enough and even MP 8000s or much more capacity would just reduce grid draw by a few percent. Why? Because not everybody will cook dinner everyday or at the same time and it’s a delicate balance between enough solar yield in winter (battery fully charged in the evening, three houses with a total of 75 kWp) and limited demand in summer (battery depleted as low as possible in the morning). Both help to improve ressource efficiency and financial numbers.

Room for improvement for @dognose & team:
Oftentimes power is low (even with our cluster!) and one or two MP2 would be sufficient thanks to phase net-metering (using “total of all phases” anyway). Thus system is wasting ~500 kWh/y, even more in private systems. What about a new assistant (“eco-mode”) which sacrifices UPS but increases efficiency a lot (a thing where victron doesn’t really shine yet)?

Oh, and when we’re on it: The fact that I had to dampen the case to get rid of noisy resonances just like a car door, replace lousy fans with Noctuas (in addition to the 40kHz upgrade) and add my own rubber for mounting the multis to the wall is something I’d expect the manufacturer to have an (even better) solution for.

Other than that: Best and most flexible system available. Love the kit approach for puzzling your systems together.

I had the same noise issues and even made a Video on this toppic :rofl:

But I did not go as far as you did with the anti-vibration and sound dampening mat :smirking_face:

Thank you @Raphael_Hofmann . This is probably as nerdy as it gets :wink:

Those both more address the hum of the transformer when close to idle which travels trough the walls of the house.

Fan-wise your video is perfect! Thank you very much for all the effort you put into it including all the measurements. I even went for the Noctua 2000s (3x MP2 3000, only 1 fan each) and thus have an even clearer drop in noise level. No derating so far.

Regarding charging/discharging with DC feed-in enabled and the 0,4 V offset; is there any news on this @k3ivi & @dognose ?

1 Like