[REPACK] Download Full Battery Alarm

I have 2 Multiplus 2 in parallel and 2 ZBM flow batteries from Red Flow. A new mode for the batteries 'Stand By Power' or SPS mode works with batteries hibernating at 100% SOC. No charging is needed. The Colour controller sees the SBS mode as 0%SOC and reports Low Battery alarm.

That's because the Low Battery Alarm report is not based on SoC. Instead, it is generated based on DC bus voltage being low. As well as when SPS is enabled, this issue (undesired Low Battery alarms) also occurs on a single-battery Redflow site when that battery is performing its periodic maintenance cycle.

Download Full Battery Alarm

Download Zip 🔥 https://bytlly.com/2y2FcU 🔥

The first place it is evaluated and reported is on the screen of the GX directly. The GX will pop up a Low Battery alarm when the DC voltage falls away. This on-screen GX alarm can be disabled, (and with Redflow batteries, it should be).

Unfortunately the Low Battery alarm reported by VRM is not suppressed when the on-the-GX alarm is turned off... and in general there is no apparent way (that I have found!) to disable the VRM's version of the Low Battery alarm.

Perhaps someone from Victron could comment on whether they might be able to change the VRM portal code so that if the Low Battery Alarm is disabled on the GX, then that alarm is not reported on the VRM portal.

That would seem to be a logical and reasonable way to operate here... i.e. as a general statement about alarms ... if a given alarm is disabled directly on the GX, I would think it would be both logical and useful for that alarm type to not be reported up to the VRM portal.

In this regard (alarm reporting) - I feel that consistency would seem to be a good thing in general -i.e. I think it'd be great if the VRM portal only reported alarms that are enabled on the GX itself, and didn't report alarms that have been directly disabled on the GX.

There's a very good reason you can configure alarms in VRM differently than on the GX device itself, you might not want a loud beeping GX device, but do want to log the alarms or get an email as installer so you can keep an eye on customers systems.

Seconded. I've got a new Redflow installation as of last week, and the alarm logs in VRM currently show 1000+ "Low battery" lines that I will never care about, and somewhere in the middle are seven lines that I do care about (one "Grid lost" and a handful of "Battery voltage too high"s). This is remarkably annoying to sift through :-)

Really confused by this issue. I have 52.7 V at the multiplus positive and negative terminals. 52.75 V at the battery terminals. System is using two 24 V 200ah victron batteries, controlled by a lynx smart BMS.

Low Battery has been the bain of my life for the last 5 months - have a look at the list I created here to check for this type of issue - VE.Bus System [276] Low battery: Alarm - drive me crazy - Victron Community (victronenergy.com)

To be honest, it's not too often for me as on bitmap. My system (3*MP2 48/5000+2*Dyness A48100) lives about a month only, and I got probably 4 cases. Not fatal, but no explanation. Maybe combination of in/out power/SOC/etc, who knows, no idea how to track. The lowest SOC ever - 76%, too far from real "low battery"

The inverter (2 Multiplus 3000 in parallel) works all the time. Since the last two weeks I notice the SOC dips. I had a constante load true the night and no heavy peaks. What is bad with this, is that the Multiplus sometime starts to reload the battery pack and then consume a few what hours from the grid.

The posts above are related to the VE BUS monitoring, so related to the inverter itself. It can still be a battery related issue though, it depends on how the battery protects itself, it could be disconnecting its output terminals, is one theory.

It seems, found source of my problem, but not reason :). It happens when connect Mk3 interface to the system (Cerbo GX), doesn't matter Victron Connect or VE Conf 3 running. After several minutes it says "Low battery voltage" and then "Device switched off"

Now that I think of it the last few Low Batteries has been with MK3 connected. What is also interesting is a real Low battery error you hear the contactor in the inverter. This Low battery with the MK3 plugged in the contactor does not activate, but it does shut the inverters off and show Low Battery error.

This has happened to me after upgrading the cerbo f/w to v3,10. The multi will switch off with low battery error although my battery SOC was 35%. after battling for 2 days looking for the problem I reverted back to f/w v3,01 and the problem went away. It was happening when my battery voltage was 51 volts so I suspect there is a problem/bug with the cerbo f/w 3,10

If you want the inverter to work without turning off on low battery, first disconnect from your GX device/BMS then reboot. Then you can connect the mk3 and it will work based on the programmed shutdown voltages only.

Hi JonPro,

The noise is 2 beeps every 3 secondes and the LED is blinking Red. What does it mean ?

I have power on both side. I did not have fluctuation/brownouts.

So to temporary fix the problem i turned it off and only used the Surge only side to power my PC and monitor.

No more beeps and blinking when it is off.

Yesterday i tried to turn it back on and it was not turning on at all. I unplugged it and i pluged it on another outlet. Still nothing then i tried another outlet, again it was still not turning on. All in different room. I tried a third outlet and finaly it turned on. The LED was green for 3 seconds then the LED turned blinking red again with the same beeps. I turned it off and back on at least 10 times with the same result. Then finally the LED stayed on solid green. I kept it pluged there for 18 hours hoping the battery was charging.

Today, i put it back in place in my room with all my stuff plugged in just like before and now all is working fine. The LED is solid green and no beeps.

I do not know what happened, i do not know if it will happen again.

Thanks

Message was edited by: RedShadow

Based from your description, if the problem happens again the battery is at fault. It would be helpful if you'll contact the APC Customer Care Center and have the model and serial number ready to check the warranty.

Is it possible you have a bad connection, maybe at the battery? I believe the low battery condition is cleared by cycling the power, until the 24 hour test runs next. However, if there is a low battery condition, you will not be able to clear the system. Even though the battery is good, if the connection is bad, it will register as a low battery.

If the battery voltage falls below 11.2 VDC a Low Battery Trouble condition will occur. The communicator can be programmed to report Low Battery to the Central Station. The battery will continue to run the control until its voltage drops below 10.2 VDC, at which time the control will disconnect and shut down to prevent a false alarm and damage to the battery. The AC Fail trouble display will clear if the AC restores. However, the Low Battery Trouble requires a manual or automatic battery load test before it will clear. An automatic battery load test is performed every 24 hours.

I'm not sure I completely follow what you were doing with zone 193 to cause this issue, but if you are trying to monitor your system for a low battery, I think a simple automation rule should handle this task.

Wouldn't you be able to create a rule that checks for a low battery trouble and sets a phantom output to on. Then you can have the Elk system contact you, and/or monitor this phantom output on the ISY?

Your right message 17 confused me. I thought you were speaking about the M1 battery when I replied back to use analog zone definition. When you spoke about the PS212S in message 17, I incorrectly thought you were back on monitoring the PS212S.

I think you might need to compromise and settle for two monitoring methods. For the M1 battery, I think you will need to monitor Low Battery Trouble and AC Power failure and set a phantom output and if you would like to see actual battery voltage, use the analog zone method.

I'm looking for an alarm app or widget that plays the alarm when battery charging reaches a certain percent (say 75%). Don't want it to stop the charging or monitor battery usage or any other function really. Just trigger an alarm but instead of setting a time of day I set a battery percentage.

A friend suggested Accubattery but after using it for a couple of weeks, it actually consumes a lot if battery because it must be open in the background all time to gather and monitor battery usage.

The problem: I have been using it with NUT over USB all the time and NUT even after the replacement still reports ALARM OL RB and "Replace battery!". From what I have gleaned, the UPS needs to be reset in a certain way. I have tried by issuing ups.test.start.quick and ups.test.start.deep command via NUT, but while it executed the test, it did not reset the alarm.

No pressing of buttons had any effect. After a moment of god-no-did-I-brick-it-panic, I checked on my reference documents and followed the instructions in the BL-1-vs-BL2-document, tripped the breaker in front of the UPS, disconnected the battery cable,waited a bit, reconnected everything. and it came back to life (i.e. apparently was pulled out of bootloader mode).

Related question about this, as I'm dealing with the same problem. Why is it that I have to pay for a license for Eaton's IPM monitoring software, only to have it completely ignore this warning? I have 4 devices out of 12 now that are "timed out", yet every single one of them shows green/good in the IPM software. For reference, this is on IPM 1.68. Unless I manually logon to the web interface of each device, I can't tell if the battery is at EOL. ff782bc1db