Stupid question if this new feature is so advantageous why not have integrated this setting in the official version of the GX, why have to install a Beta?
All good things come to those who wait⊠
Now seriously, the idea appeared during developing of beta 3.50~15 so I believe it will come out with the 3.50 release.
See here: 3.50~15 Modification Pylontech
1 Like
thanks @alexpescaru
1 Like
Hi not sure if it helps but about half a year ago I suddenly had internal error on US3000C
Checking with VRM cell voltage monitoring I saw a 4V spike.
I spliced a cisco console cable rj45 usb and got batteryview.
Downloaded the log of the offending battery and send it to Pylon.
Turns out a rare sampling error on a particular chipset & firmware.
They attached a firmware upgrade. Uploaded via batteryview works perfect ever since.
Advise was to leave all the other batteries on their present firmware.
Regards
3 Likes
@LifeInGalicia, thanks for your advice.
I note what you say but because my system problems are most likely caused by my pv output upgrade.
I need to find out what needs to be done for my system to operate correctly with the increased pv output.
Software upgrade might come after I have completely checked that the system is setup correctly.
Thanks
Patrick
Hi no worries check cell drift / diff on VRM. Mine drift max 0.03
Maybe the batteries want slow balancing again. Try to set max charge voltage to 52.3 or 52.2 then increase back over time / cycles.
Also recheck all connections. As you now have higher availability and higher charging amps it might well trigger. The BMS sets max allowable charge so passing on less is not a problem running at max always is. Best of luck
Thanks again Martin, I did read that the BMS has priority control over the other manual battery settings specifically regarding Limiting Amperage, and for that reason I now have this manual battery amperage control set to zero amps.
Following these types of setting changes, does the system algorithms take some time to settle before the battery system fully operates, as per new settings?
Thanks again
Regards
Patrick McCabe
Hi Patrik, die Software von Victron ist sehr ausgereift aber auch Fehlertolerant programmiert. D.H. manche Einstellungen werden ggf. einfach ignoriert bzw. ueberschrieben. Es ist jedoch wichtig die Basiseinstellungen genau nach Anleitungen vorzunehmen. (VEconfig).
Das BMS von Pytes ist ebenfalls sehr stabil und gut gemacht. Pytes nutzt passive balancing allerdings nur mit etwa 50mA aber auch active balancing. Ausfuehrlich hier - Active Management: Expect More From Your BMS â Intelligent Controls
Auf deine Frage: Eigentlich werden Aenderungen schnell uebernommen sofern diese âpassenâ.
Einige Parameter haben auch Puffer z.B. SOC wenn dieser mehrfach erreicht wird werden 5% draufgeschlagen oder auch abgezogen bis zum Stellwert.
Das BMS hat immer Prioritaet zumindest bei GX und Pytes.
Am besten auf VRM die Widgets z.b. High / low Voltage aktivieren, sowie Netzspannung etc.
Dann kann man gut verfolgen was eigentlich los ist.
Wenn man Pytes als Fehler vermutet dann braucht man ein Spezialkabel RJ45 auf USB und kann mit der frei verfuegbaren Software BatteryView sehen was in den einzelnen Zellen los ist.
Bei Bedarf die Logs an Pytes senden - die Antwaorten eigentlich sehr schnell.
Wie gesagt du hast die Kapazitaet erweitert und jetzt stehen mehr Amp und auch Volt zur Verfuegung das kann zu Alarmen fuehren die du vorher so nicht hattest.
Viel Spass
I sometimes get strange high voltage alarms from the Pylontech-System in the CerboGX like this:
Is the voltage there reliable? I mean ⊠51,07V ⊠High Voltage Alert?
The VRM says for today this:
Is there something which can be done? It also seems that always one module is a little behind when charging (one less blinking light) I observed.
Dear @Sesshoumaru
Try to keep your SOC at 100% for 6-8 hours straight to see if all your US balance out.
HV alert is triggered by an individual cell being too high, not the pack.
Leave it on KBC for a couple of days, it will sort itself out but if a cell is bad, errors will return with normal use and will need PT support to resolve it for you.
1 Like
The pack voltage is OK, but the cell high voltage alarm is raised when a cell is over 3.6V and one of yours was at 3.61V.
The recovery voltage for this alarm is 3.5V and is clearly seen that when that cell hit 3.5V, the charging was resumed, but this time the highest voltage was 3.58V and then slowly going down as the pack balances.
All these events are stored into the battery event log and you can get them from there. Tricky part is that if you will have a problem inside battery warranty, the Pylontech tech dept. will ask you for the events log and when they will see many of these will raise and eyebrowâŠ
You can try to install the Venus OS 3.50 beta for an improved charging algorithm or wait until 3.50 release for the same.
Will try.
The error resolves itself and I noticed it a couple days ago. II donât know how often it happend in the past, but as of now it probably came here and there without me noticing.
@Sesshoumaru
you mean you updated the Venus to 3.5 Beta?
No, keeping the stuff loaded for a while, ⊠but it heading for winter here.
Once 3.50 is released I will update. I am not so much into Betaâs.
ok
Hi @nickdb, I am back againđ.
I upgraded all BMS to ver 3.4
MPPT 250 /100 rev2 to ver 3.15
Multiplus firmware from ver â510â to â552â
I have still got HV Warnings and Alarms.
I also still have VRM disconnect from GX due to GX device overload.
From my downloaded battery History and Event logs the most obvious problems I read is that I Appear to have problems on one battery indicating too many âHV incidencesâ and a different battery has too many âOvervoltage incidencesâ.
My other Two batteries donât appear to have any problems!
Could This likely be the cause of my HV Warnings and Alarms and possibly also causing the GX Disconnect problem???
Advice please gurus, thanksđ