Hello Forum, I’m new here and i added an Multiplus II GX to an existing non-communicating ESS with 16kWh battery (JK-BMS, not Inverter BMS) and two Steca PLI 48-5000 in parallel.
The MP II now communicates via SerialBattery with the battery but he doesn’t know anything of the PV-charging into the battery done by the Stecas.
My question (after watching the 1 year old YouTube-DESS-Webinar) is driven by impatience - the DESS is running for less than 24 hours:
Will the DESS recognice and calculate with periodic DC-input into the battery that isn’t controlled by the Victron-Ssytem?
Thx a lot and I’m glad there is sich a big Community.
And there are also some Hoymiles HM-xxx on the grid and in the AC-output for critical loads and a 4.2kVA Kostal Pico solar inverter on the grid, not communicating with the MP II.
In all fairness.. if you mixed ( mixed use ) products in a Victron Eco System and then expecting the DESS algorithm to work driven by non-integration and impatience … is a recipe for frustration.
Hi Edwin, he knows indirect. Victron knows external battery charge because of it’s communication with the BMS.
The question is: Will the MP II ignore it in it’s calculation or will he lerarn that there are others filling op the battery? As he shows DC-loads in the float diagram when a foreign device discharges the battery.
The JK-BMS communication is very limited. Really. I would. In case you didn’t already. Add a SmartShunt to the batterij. This way load/charge can, somewhat, be registered.
Another thing that I would do. Or at least try to get going, is to get the MPPT data from the two and inject that so that the MultiPlus knows at least that. Look at the GitHub repository of mrmanuel. Italian bloke who make stuff work. Good luck.
What else than charging power does an ESS need to know that a battery gets charged?
“You’ll get frustratet”, “buy some things (ideal after you dumped the things not worth beeing part of our ecosystem)” and “no, i wouldn’t take this harmless try” are answers i know from marketing-guys … not from technicians. Maybe there changed something the last decades. A simple " Idon’t know If that may work" or “sounds interesting, tell us how it ended” were my sentences as support.
So the DynESS is ignoring every solar yield that doesn’t run thru Victron products (and also the one thru itself):
The Multiplus II knows there are inverters on its AC out critical loads because i told him via VE.config. And he knows it because he uses this energy every day to charge the battery. But he ignores it in DynESS.
The Multiplus II knows that there is a grid-inverter because of the feed in he measures thru it’s Victron-Smartmeter. And he knows it because he uses this energy every day to charge the battery. But he ignores it in DynESS.
The Multiplus II knows that there is a charge controller because of the communication with JK BMS. But he ignores it in DynESS.
So it seems the problem isn’t my configuration. Its the ignorance of the software because it could calculate all that.
“Add somme components” sounds easy but i would need:
Two Shunts for the Stecas.
A VE.direct to USB adapter because the MP II GX only has one direct-plug. And an USB-Hub.
A three-phase-smartmeter for the grid inverter.
Several single-phase-smartmeter because the 6 microinvterters on AC1out are connected at different places with 40m in between.
And all that because somebody ignored third-party-solar-yield.
I go for an update-request and do DynESS with my own controls until Victron is able to do so.
