Smart Shunt Parameter Question

Greetings,

I have a CerboGX with a MultiPlus II 12/500/20 and 300A Smart Shunt setup.

Current battery bank is 3x DCM0075 Interstate 75AH SLA batteries in parallel.

I am seeing from the Shunt that we have been consistently discharging (until late last night). Currently I am seeing under the MultiPlus battery tab, still a blank SOC but in storage mode with 13.02vdc, 4.8a on current and 64W, with AC in of 120+W and AC out of 38+W.

According to the graph on 9/11 we started with around 12.69vdc at 2pm and as of midnight we were at 12.49vdc. Over the day of the 12th we went from 12.49vdc to 12.15vdc then at 9pm we started to take on a charge. At midnight we were at 13.10vdc and since then, today we peaked at 13.20vdc at 7am and started to decline again as of writing this 1:40pm, we are sitting at 13.02vdc.

I have a VE Direct cable from the shunt to the Cerbo but doesnt seem like I get a ton of information from it. I dont recall 100% of my settings for the shunt but they were per recommendations for a SLA battery bank and should be relative to the following:

Capacity - 225AH
Charged Voltage - 13.1 - 13.2 (I believe)
Discharge Floor - 50%
Tail Current - 4%
Detection Time - 3m
Puekert - 1.25 (I believe)
Efficiency - 95% (I believe)
Threshold 0.10A (I believe)
Time to Go - 3m

When will I see a SOC? Any way of making the SOC show up?

Should I adjust any of the shunt settings from the above?

This is installed 8 hours away, I cant afford for the battery to get so low that something tells the MultiPlus to shut down (any settings I should disable?) or for the DC loads I am pulling from bus bars to die… Is there a need to ever override the MultiPlus to go into “charge mode”?

I have someone that can go out with the app and make changes as needed to shunt parameters, this is my first install and want to ensure its discharging and charging appropriately and allowing for if we lose power to run for a decent amount of time.

TIA !!

keep watching the battery voltage. SOC is a derived (calculated) parameter. However, I would have expected the shunt to have it’s parameters listed under it’s own device tab in the Cerbo, the Soc may not make it to the Multiplus tab.

Unfortunately I dont see a tab for the shunt. I have it showing the basic info less SOC on the overview tab and then if I click that the MultiPlus is providing the info mostly it looks like and thats under the Battery section on the Cerbo. Doesnt make alot of sense… When I look at devices I see Gateway and MultiPlus only. Do you feel the parameters above are fine? I am “charging” or so it claims and im at 13.01 on voltage right now. See attached images.

It is the ‘Battery’ page, under settings>Devices it should show up by Id, and then set the use to battery?. Not had to do this as I don’t use my shunt with a cerbo.

Your settings look fine. As it is a smart shunt, you should also be able to connect to it with VE connect on your phone, Check to see what SOC shows up there…

You also need to check to see that the ‘Charged Voltage’ on the shunt is ~100mV less than the Absorption voltage set on the multiplus, so as it actually get to the ‘charged’ state and resets the soc counter to 100%.

I’ll have to have someone look that can connect by BT to it. Under devices I don’t have the shunt on the VRM see image attached. Is there a way to get it to list there? The last SOC I got on it was 87% by BT detect connect yesterday 6am which was about 36 hours ago. Since then it was charging based on the graphs, also attached.

looks like the ve-direct cable is not connected properly, or is faulty. it should show under the devices.

I guess it doesn’t matter that much, I likely won’t be back there for months and can maybe swap it then. As long as it’s running and charging properly that’s all I care about. Is there a way to scan or detect devices to be sure? I switched to Venus Large and then back but that shouldn’t have affected it I wouldn’t think.

Here is the most recent data that was sent to me from someone who was able to go by and pull the shunts info, settings, and also the latest data from VRM…

As you can see the SOC is lower than before but the voltage is high. Does the SOC percentage even matter and do I need to turn off anything to keep the SOC from shutting something down?

Should we be discharging more than we are? Looks like the lowest it got was 13 volts.

SOC will drift up or down over time, unless it gets reset at 100% by a full charge detect event. For your settings that should occur if the battery stays at over 13.2V for 3 min.

No, you don’t need to do anything in terms of turning something off - the inverter settings will give you the low voltage warning and shutdown battery voltages.

The less that you discharge lead acid batteries, the longer they will last.

So I don’t need to tell the system to disregard the SOC? Also would you suggest that I adjust the voltage from 13.2 to something a little lower so that the SOC hits 100%?

I heard someone mention before that the SOC can actually trigger an event so that systems will shut down. I just wanna make sure that’s not the case.

As far as you’re concerned, everything is looking healthy? Like you mentioned, the battery voltage is staying consistent after the first cycle. I haven’t really seen it drop below 12.0 at all, maybe not even below 12.2.

you seem to be cycling 0.075kWh, or 75Wh - less than 6.25Ah @ 12V. with a 225Ah battery, that is really quite small.

Seems to me that the inverter/charger battery charge parameters need to be viewed together with the shunt parameters (as above) to see whether the SOC reset will work correctly…Charger absorption voltage should be >13.3V (Usually 13.8 to 14.2V depending on battery requirements).

The SOC shut down usually comes from a GX device.

I’m not sure if there are any battery charge perimeter, do you have an idea specifically where to look? I’m more than happy to do that.

You need to access the Charger tab of the Multiplus ii, with Ve connect or Ve configure. The latter should be able to be done Via the Cerbo and VRM. VeConfigure needs to be installed on the device accessing VRM in order to do this remotely.

I will look into it and try and figure it out. Currently, there’s only two connections on the CERBO, that is the Victron cable from the multi plus to the CERBO and a VE direct cable to the shunt.

then you should be able to remotely access the MP2’s settings.

@MikeD can you share a screen of the info you’re talking about not sure if my tabs are different or I’m in a different section. Thanks!

Step 1:

Step 2: click the remote configure button:

Then download,

Remote Ve configure. Need to get the laptop out to go further, as I usually run a unix machine, VE configure don’t run on that :frowning:

I got all that downloaded and setup but looks like when I open the file it just says device not found. Assuming I have to be local for this to work as I can’t even read the file. Unfortunately, today I flashed some firmware on my SHTF relays and out of stupidity I didn’t put the relay on an isolated network port on the modem like I did with its power and after the firmware flashed, and before I could get to upload my settings it was knocked offline because its communicating on a switch that remained on a closed relay. So this being said I have to send someone there and they have the app on their phone so maybe a silver lining.

OK sorry for the delay in responding to this, but was busy on some projects.

With the remote configure from VRM, you end up with a download file. This can be opened from VE configure using “fake target from file” if VE configure does not open automatically. Once you get that opened, you can make any changes you want, then just close Ve configure. The program asks you if you want to save the changes for the remote file. do that, then it can be uploaded to the inverter from VRM. A bit clunky but it works. If you use a different machine to access VRM and run VE configure (like I normally do) then the file will need to be physically moved as well.

I think thats the issue its forcing me to use VE Configure 3 which is Victron Connect now……