Making a case for Victron to consider the new "Pylon Feature" for all

No issue with DIY option. Bigger and better quality cell I guess.

But I still stand by the BMS having THE primary management role to play.
And - I would strongly suggest getting more then 1 bank to negate the issue of totally battery shutdown and the knock on effects. Smaller cells maybe.

Victron: I’m sure they have a long list of projects and to be distracted by a BMS project. I think they could add value elsewhere (for the time and effort)

This is inherently an argument about whose job it is. I insist that it is the job of the BMS to come up with a suitable charge voltage. A lot of them do it already.

From a technical perspective, there is also no way to know how this would interact with other banks (the filter, for example, is tuned towards the update frequency of a specific battery right now). This could lead to endless tinkering and developer hours, with someone constantly claiming it doesn’t quite work for him. Ask how I know… no good deed every goes unpunished in this domain.

The functionality should be in the battery itself, or in the driver for the DIY banks.

But… if it does turn out that the wheel squeaks enough, then @PierreJ 's suggestion of a max cell voltage feature is probably how it will be. Another setting for people to get wrong… to cause warranty issues.

This is going to be far simpler to implement in dbus-serialbattery anyway. Remember that some of those batteries gives you detailed information about per cell voltages… it can be done very nicely!

3 Likes

I think I made the point on the timeframe of the problem, and warranty claims, could be around for.

Understand, I don’t have any horse in this race, I control my own … all I need to do, and I’ve dunnit before, ask a question, get knocked, then sit back and be patient.

Also, it is not for us to decide if Victron has the time for it or not, nor when to do it if decided.
That is Victron management prerogative.

Then why don’t we, and by we I mean you, speak to the right people?
Pylontech, done. What about other forumites with FreedomWon banks?

The issue is there in the market as I indicated to @mmaritz.

DVCC has Max charge current already, add the option based on a cell volt, to reduce the charge current. It has been done. Just add a option for the rest.

Where a developer is needed, to do it in a downwards loop till the cell volt does not increase anymore.
Then HODL.
Once stable for X-time, slowly increase amps again.
Rinse repeat.

There will be a ripple effect on the system … tough, it is what it is, or does the client prefer a new bank?

To eliminate the problem “children” (clients), make the option PW protected.
You ask for and get the PW as a client/installer, don’t phone us.
Just like Victron states clearly on other things like NodeRed, addons etc, don’t phone us. Contact XYZ instead.

Just spit balling solutions.

@TheTerribleTriplet Start here boet :wink:

Then on that high note, this then concludes my contribution on this matter. :+1:

In all seriousness though… I don’t think we can pin @plonkster to raise this issue… We already push the limits (at least I do) of his involvement (2 hats, etc).

It needs to start through an official channel.

I concur. (was tongue in cheek … prompting him a bit as he sometimes appear to know what he is talking about. :slight_smile:)

Reading it all again, the aim was for a more deliberate debate, understanding the problem, discussing it. Learn from each other.

Also hoped installers on here would also add their thoughts.

My side is done … I’m just waiting on a later model BMS that ticks all my latest new boxes.

1 Like

The ultimate solution is for the battery to instruct the GX to switch the system to Keep Batteries Charged until the delta is small enough. At that point the GX can revert the ESS mode.

The new “Pylon algorithm” is only half the solution. As alluded to above; it must be used in combination with KBC to have a hope of recovering a battery with at least one very low cell.

In most of the examples I tried to recover, the cell imbalance was resolved on KBC but returned quickly with cycling.

If it’s too far gone, it’s too far gone.

3 Likes

Now that is interesting.

Doing KBS daily weather permitting, but for other reasons.

NodeRED increase my banks SOC during the day by 10% SOC increments.
BMV SOC hits 98% early afternoon, ESS is set to Keep Charged the rest of the day.
Evening, the SOC is lowered again for spreading the draw from the batts over 24h.

Accidental benefit for me then, that the balancer has ample time daily to keep the bank well balanced.

Cause I can see when there are bad weather weeks, the SOC never reaching >80%, my balancing set to start at 3.45v, that after a while it does take a wee bit longer to “settle” again when the weather clears.

Or I just give it some TLC using Eskom, during bad weather weeks.

Read a case being made for balancing, to use Eskom charging, more constant vs MPPT’s charging, more inconsistent.

I tested that.

Well, for one, I am no longer lead on that project. So you have no choice but to try and shoehorn this through the correct channels.

And besides, serialbattery already does something like this. Which makes this the far better place to start tinkering. As a support person, the last thing I want is MORE diy batteries :slight_smile: