search for: desktop_up

My UPS has an LCD that says the battery is 100% and the estimated run time is 12min. The uspc has similar results. The problem is when line power is lost the UPS batter goes to 0% very quickly (seconds). It charged to 85% when power was restored. 86-100% is slower. I did: $ upscmd desktop_ups test.battery.start.deep Username (admin): Password: OK Now the ups.test.result says there is a warning. I suspect this will tell me the error. $ upsc desktop_ups ups.test.result Done and warning How do I get more details about the result? Surely there must be more. Are the symptoms consistent...

I got around to unplugging my UPS and I found it doesn't last nearly as long as estimated. Is the "upsmon[1446]: UPS desktop_ups at localhost battery is low" logged when "battery.runtime:" = "battery.runtime.low: 120"? Does any make better batteries that don't go down faster when they get old? battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 50 battery.date: not set battery...

...er goes to 0% very quickly (seconds). >> >> It charged to 85% when power was restored. >> 86-100% is slower. > > It is common for an UPS to have different phases of charging, with the charging current tapering off at the end. > >> >> I did: >> $ upscmd desktop_ups test.battery.start.deep >> Username (admin): >> Password: >> OK >> >> Now the ups.test.result says there is a warning. >> I suspect this will tell me the error. >> >> $ upsc desktop_ups ups.test.result >> Done and warning >> >> How...

...when line power is lost the UPS batter goes to 0% very quickly (seconds). > > It charged to 85% when power was restored. > 86-100% is slower. It is common for an UPS to have different phases of charging, with the charging current tapering off at the end. > > I did: > $ upscmd desktop_ups test.battery.start.deep > Username (admin): > Password: > OK > > Now the ups.test.result says there is a warning. > I suspect this will tell me the error. > > $ upsc desktop_ups ups.test.result > Done and warning > > How do I get more details about the result? &...

...was (it should be). The battery.runtime is better for my desktop (it's supposed to be worse) and my raspberry pi is worse (I hoped for hours better). What am I seeing? I switched them for longer raspberry pi time and the APC battery is getting old. :-) This is before the switch: /bin/upsc desktop_ups battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 2730 (~ 45 minutes) battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 13.5 battery.voltage.nominal: 12 device.mfr: CPS device.model: UPS CP850AVRLCD device.type: ups driver.na...

On 07/09/2019 08.28, James wrote: > I got around to unplugging my UPS and I found it doesn't last nearly as long as estimated. > > Is the "upsmon[1446]: UPS desktop_ups at localhost battery is low" logged when "battery.runtime:" = "battery.runtime.low: 120"? > > Does any make better batteries that don't go down faster when they get old? In my experience batteries die after about 4 years. No UPS that I owned could tell that th...

...t around to unplugging my UPS and I found it doesn't last nearly as long as estimated. The estimates are typically less accurate when the load is light (output is showing 5%). Also, as Eyal mentioned, five years is getting old for a lead-acid battery. > > Is the "upsmon[1446]: UPS desktop_ups at localhost battery is low" logged when "battery.runtime:" = "battery.runtime.low: 120"? To first approximation, yes. Technically, upsmon is looking for the LB flag in ups.status, which is usually sent in a status bit from the UPS. But "battery.runtime.low" is...

The battery was replaced in December and the output from upsc was: $ upsc desktop_ups battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 1020 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 13.5 battery.voltage.nominal: 12 device.mfr: CPS device.model: UPS CP850AVRLCD device.type: ups driver.name: usbhid-ups d...