for all the pylontech / pytes users. i am curious is the whole capacity of the battery banks automatically set? or manually like the manual says via ve-configure?
im asking because i wish to parallel some dumb batteries with the rack batteries and it would be great if i can manually enter Ah to get accurate SOC%
ok I think I know. that setting above is only if you have multipluses without DC chargers, otherwise it will use bms soc? but I can buy a Lynx Shunt VE.Can and select that as the source for the whole soc%?
For ESS (assistant) to work the internal battery monitor has to be set. And ideally correcy for capacity installed and charge when bulk is finished
While the VE bus then synchronises to the battery SOC if it is connected, the setting is still an essential part.
If the bms disconnects/freezes for any reason there are fall back parameters (or for any reason like for trouble shooting it needs to be disconnected.)
For the most part bms lost would be displayed and the system shuts down.
This will depend on how compliant and how far the batteries are with their integration into the ecosystem. I have seen too many do the bare minimum to send bare minimum stats and instructions to the system.
Prefer the belts and braces approach to set up the system - do both.
The inverter and chargers all need to be manually programmed.
Once operational, DVCC will overrule the internal parameters from what the BMS sends over CAN, but you always want the system to be properly configured if it has to revert for some reason.
The docs are continually maintained, if it wasnât relevant, it wouldnât be in the manual.
in the wholw document i only see sentences like âIn normal operation, the charge parameter limits are set by the Pylontech battery and communicated through the system by the GX device to the inverter/charger and MPPT.â ?
There are cutoff voltages as well.
The doc shows all the manual settings that should be applied.
If the system restarts without BMS control you want default parameters.
There is no benefit to not programming it as advised, it gives all the devices defaults to work to and populates settings that are not configured via DVCC.
It is possible to override some of these automatic settings to provide additional limitations (e.g. reduce the total charge current that would be provided but the MultiPlus). The following information is provided for that purpose, though is not required for the safe operation of the system.
your last picture - what means governed?
So in my understanding Victron-Pylontech should be plug and play?
You are choosing to believe that while ignoring everything else that follows.
Yes, you can just plug it in, but you are losing any control or fallback if DVCC has an issue or the system restarts without a BMS.
Much of the duplication is precautionary, some like cutoffs are necessary.
Plug and play is fine for printers, it is not for electrical systems.
Chosing to not be thorough exposes you and your batteries to risk if something goes wrong.
Not setting shutoffs and restart thresholds means you might not be able to black start the system - we see that from time to time here with users who had the plug and pray mindset.
It is not best practice to just leave it all to the BMS. This is why defaults are listed in the doc.
Pylomtech isnât special, why do you think all other supported batteries list veconfigure settings for the inverter beyond just ESS?
Not opinion. Fact.
DVCC cannot modify any system settings. It can override the AC input limit if enabled, but it sets no cutoff thresholds, nor does it write anything to an mppt or multi. With DVCC everything is under external control so will accept the charge voltage and current limits sent from the BMS and override the presets.
Devices will retain their default settings and if an abnormal event occurs can revert to those.
All DVCC is, is a coordinator, it passes temporary limits and sensor readings.
The CAN spec does not support sending the information you think the battery is capable of sending and DVCC lacks the ability to reprogram any specific device setting in this manner, beyond being a gateway for remote veconfigure.
If the BMS disconnects, after some minutes the system will power off with an error 67 - BMS lost.
please calm down - and read the document i linked with the view of a new client
If what you say is not also only an opinion, Victron should offer documents with sentences like
"5. VEConfigure Settings
When using the latest firmware on all compatible connected devices, and once the battery module has been detected by the GX device, battery charging parameters (e.g. Maximum Charge Current, Target Battery Voltage, etc) are automatically configured by the Pylontech BMU, and communicated to the rest of the Victron components in the system via DVCC."
If i understanding you right:
Somebody buys a used MP2- configured for 16s 55V - connects it to a pylontech battery, MP2 will only deliver 51V because that was read from BMS
One day, there is a problem, system shuts off, BMS error
The User disconnects can cable, restarts the system - then the system is back to 55V setting?
Can assure you I am quite calm, just stating that this not being facebook that we try avoid opinions for something that is defined by physics or programmed logic.
Correct.
Or your GX dies and you want to get your system going in the old-school manner.
Or you leave a load on and run the battery until the BMS cuts out and needs manual intervention.
This is why any good installer will always program everything with the basic foundation the battery manufacturer wants.
Sure you can plug and pray, it works great while everything is working as expected.
We program for the unexpected.
If you cook your batteries the warranty goes out the window, so a conservative approach that covers all scenarios is a good idea.
The docs are produced in conjunction with, or by the manufacturers. Some, especially the older ones like Pylon, could use a cleanup imo.
The newer supported batteries tend to be more concise and clear.
Does anybody else have an opinion - oh sorry, not Facebook - knowledge on this topic?
I can´t believe it is like Nick said
Maybe i find the time next days - we have at the company an unused MP2-GX and a Pylontech 5000 laying somewhere in the storage
It would be a lot of work, so maybe somebody with a Pylontech Battery at home could do a short test, unplug the CAN-Cable- Reboot, and check the values in VE-Configure?