search for: uspc

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...

...on" to be a bit more safer... I've seen battery.charge.low option in trunk, but it seems it must be implemented in driver, and it's not implemented in blazer. Am I right ? Offcourse, I can workaround this problem: NOTIFYCMD /usr/local/sbin/check_lowbatt /usr/local/sbin/check_lowbatt uspc myups | grep battery.charge res=$? ... But it's an ugly hack... Is there any better solution ? I missed something ? -- Thanks in advance. Pavel Selivanov

I'm running NUT 2.6.3 on Debian wheezy [ with a 3.3.0 i686 kernel ] I've installed NUT via Debian APT [ package nut version 2.6.3-1 ] I have a REDi Blazer 600VA (BLAZER600c) UPS and I want to detect power failures. I have tried the following drivers: * gamatronic: Can't talk to UPS on port /dev/ttyS1! * bestups: Unable to detect a Best/SOLA or Phoenix protocol UPS * blazer_ser: No

Hi, I have the Eaton 5E850iUSBDIN UPS connected via USB to a Raspberry Pi 3B+. It seems that everything but the ondelay parameter works so far. when I test the setup with this command: upsmon -c fsd The NUT server makes the NUT clients shut down properly and the Raspberry Pi running the NUT server shuts down correctly too. The problem is that after UPS shuts down, it immediatelly brings the

...not exist dstate_addenum: base variable (input.sensitivity) does not exist dstate_setflags: base variable (battery.charge.restart) does not exist dstate_addenum: base variable (battery.charge.restart) does not exist Detected Smart-UPS DP 8000 XL [gs9941001285 ] on /dev/ttyS0 after that I can use uspc to get some information, I wonder if the Smart-UPS DP is not working like a standard apc smart-ups. or the driver have to be updated? thanks Shah Mohsin WAHED

On Dec 15, 2018, at 10:32 PM, James <bjlockie at lockie.ca> wrote: > > 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. It is common for an UPS to have different phases of charging, with the charging current tapering off at t...

In the upsc output for my Eaton Elipse ECO 1600 I see ups.delay.shutdown: 30 ups.delay.start: 40 but in the uspc output for your Eaton 5E850iUSBDIN I see only ups.delay.shutdown: 60 Where is ups.delay.start ? Does the command upsrw <UPS> display this variable ? Roger

...UPS does not support it or maybe the driver does not support it? Bartosz sob., 6 kwi 2019 o 15:20 Roger Price <roger at rogerprice.org> napisał(a): > In the upsc output for my Eaton Elipse ECO 1600 I see > > ups.delay.shutdown: 30 > ups.delay.start: 40 > > but in the uspc output for your Eaton 5E850iUSBDIN I see only > > ups.delay.shutdown: 60 > > Where is ups.delay.start ? Does the command upsrw <UPS> display this > variable ? > > Roger > > _______________________________________________ > Nut-upsuser mailing list > Nut-ups...

On 2018-12-16 8:04 a.m., Charles Lepple wrote: > On Dec 15, 2018, at 10:32 PM, James <bjlockie at lockie.ca> wrote: >> >> 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. > > It is common for an UPS to have different phases of charging, with the charging...

I'm having problems creating a UPS connection to my Tripp Lite UPS System: Ubuntu 8.04.2 Nut 2.4.1 freshly compiled from source. When I do upsdrvctl start everything appears to work and I get :Detected a UPS: TRIPP LITE/TRIPP LITE UPS Using OMNIVS 2001 protocol (2001) Unit ID not retrieved (not available on all models) Attached to Tripp Lite UPS But

...e UPS do carry power. I turn off the UPS and back on, which returns power to the connected device. 3. debug_no-prior-shutdown.txt - that's a log I recorded first without running any of the shutdown tests. In addition to the debug logs, I also was curious to see if anything changed in the uspc output after I issued the shutdown command. I attached that as the upsc_output_on_shutdown.txt file. Only on the first command, did I include all the variables. For subsequent commands, I just included the ones that changed over the course of the test. Before cutting the power, you can see the...

...LERT were at 5 and DEADTIME at 15 (defaults) and I started getting these soon after service start.  After a few increases I adjusted them to 30, 30 and 90 and it took about 24 hours for the broadcasts to start.  During my early testing, when communications gots re-established automatically, the uspc command worked, but otherwise I got "stale results" error.  Restarting the services (nut-server and nut-client) resolved the issue, only to have the errors occur again. FWIW, this rPi has an Adafruit Ultimate GPS Hat and is serving as a stratum1 ntp server,  as well as a secondary dn...

An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20090120/ffb91e55/attachment.htm

...ed first without running any of the shutdown tests. Can you do one more log with a higher debug level? "-DDD" should get the report descriptor mentioned above. It doesn't need to run for long. > In addition to the debug logs, I also was curious to see if anything changed in the uspc output after I issued the shutdown command. I attached that as the upsc_output_on_shutdown.txt file. Only on the first command, did I include all the variables. For subsequent commands, I just included the ones that changed over the course of the test. > > Before cutting the power, you can s...

...old to 90 seconds in ups.conf. See below for debug info. If somebody could offer suggestions on how to fix it, I'd be very grateful. Thanks in advance, Graham ups.conf: [maxwell] driver = usbhid-ups port = auto override.battery.runtime.low = 90 uspc output: battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 50 battery.date: 2005/04/07 battery.mfr.date: 2005/04/07 battery.runtime: 165 battery.runtime.low: 90 battery.temperature: 29.2 battery.type: PbAc battery.voltage: 13.5 battery.vo...