similar to: ups.test.result meaning

On Sat, Oct 31, 2020 at 2:42 PM Tim Dawson <tadawson at tpcsvc.com> wrote: > I'm going to guess that since your test runtime of 305 is very close to > the low limit of 300, that's the warning. Not yet a fail, but very, very > close. > I tried setting override.battery.runtime.low = 60 in ups.conf, and waited for the UPS to reach 100% charge, and ups.status to report only

I'm going to guess that since your test runtime of 305 is very close to the low limit of 300, that's the warning. Not yet a fail, but very, very close. On October 31, 2020 11:41:39 AM CDT, Rick Dicaire <kritek at gmail.com> wrote: >Hi folks, new to list... >nut 2.7.2 on Ubuntu 16.04 with Cyberpowersystems CP1350PFCLCD. > >After performing upscmd cp1350 at localhost

On Saturday 31 October 2020 20:13:48 Rick Dicaire wrote: > On Sat, Oct 31, 2020 at 2:42 PM Tim Dawson <tadawson at tpcsvc.com> wrote: > > I'm going to guess that since your test runtime of 305 is very close > > to the low limit of 300, that's the warning. Not yet a fail, but > > very, very close. > > I tried setting > override.battery.runtime.low = 60

On Oct 31, 2020, at 8:30 PM, Gene Heskett <gheskett at shentel.net> wrote: > >> battery.voltage: 16.0 > At that voltage, 5 of the 12 cells are shorted >> battery.voltage.nominal: 24 The 16.0 is a scaled version of the fixed (bogus) 24.0 V reading, similar to this unit: https://networkupstools.org/ddl/Cyber_Power_Systems/CP1500PFCLCD.html I think we even

nut 2.7.2 linux 3.18.7 CyberPower CP1350PFCLCD The LCD shows the same for input and output, my multimeter also matches the input voltage. But nut is giving me different numbers. How do I debug this? input.voltage: 122.0 output.voltage: 138.0 I still need to check what it does on battery and what the other readings are. But the voltage stuck out at me.

Arjen, all, I just built and installed network-ups-tools-git-v2.7.4.r161.g7bf209a on Archlinux for a CyberPower CP1350PFCLCD ups. After hitting the FAQ 29. "My USB UPS is supported but doesn?t work!" udev issue because the UPS was plugged in when nut was installed bug, running upsc I get: battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS

hi ,everyone, I have a script shown as below: > bj2=bjerrdata$tyerr[bjyearnum[2]+1:bjyearnum[3]] > length(bj2) [1] 448 while > b=bjyearnum[3] > a=bjyearnum[2]+1 > bj1=bjerrdata$tyerr[a:b] > length(bj1) [1] 169 it is different with bj2 and bj1 . and the array bjyearnum is [1] 0 279 448 633 1021 1365 1813 2237 2839 3314 3798 4157 12 why bj1 is 169 while bj2 is 448

Hello, I have a CyberPower CP1500PFCLCD and I'm trying to get nut to see it under OpenIndiana. All search online suggested that it basically can't happen, but I decided to ask again, maybe things have changed since then. The UPS can be seen by the system: # /usr/sbin/cfgadm -lv usb9/1.1 Ap_Id Receptacle Occupant Condition Information When Type

Just wanted to report that I have successfully got a Dynex DX-800U UPS functioning with the newhidups driver. This UPS appears to be made by CyberPower Systems and I believe is the same as the CPS 800AVR. --------- # upsc dynex@localhost battery.charge: 66 battery.charge.low: 10 battery.charge.warning: 20 battery.runtime: 399 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 19.7

Hi Patrick, 2010/11/15 Patrick O'Malley > I've confirmed that the CyberPower CP1350AVRLCD works with nut using > the USB port and the usbhid-ups driver. It is not on your list. > Thanks! > have you checked all variables, and most of all that shutdown works as expected? ie http://new.networkupstools.org/user-manual.html#Testing_shutdowns please also send us an upsc output.

On 5/30/2017 10:47 PM, Charles Lepple wrote: > On May 22, 2017, at 11:13 AM, Mike <the.lists at mgm51.com> wrote: >> >> On 5/21/2017 10:39 AM, Charles Lepple wrote: [snip] > Even though the CPS sub-driver has been written already, I would like to take a look at the raw "explore" mode output: > >

[please use reply-all to include the list. thanks!] > On Nov 26, 2015, at 9:47 AM, Weedy <weedy2887 at gmail.com> wrote: > > nut 2.7.2 > linux 3.18.7 > CyberPower CP1350PFCLCD > > The LCD shows the same for input and output, my multimeter also > matches the input voltage. > But nut is giving me different numbers. How do I debug this? > > input.voltage:

UPS - CYBERPOWER CPS DX600E upsc usb at localhost battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 1650 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 4.8 battery.voltage.nominal: 12 device.mfr: CPS device.model: DX600E device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2

i can't seem to get newhidups to detect my UPS.. i'm using nut-2.0.3 (tried both the rpm from fc5-updates and compiling my own) here is the entry for the UPS in /proc/bus/usb/devices T: Bus=04 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0764 ProdID=0501 Rev= 0.01 S: Manufacturer=CPS S: Product=UPS

On 5/21/2017 10:39 AM, Charles Lepple wrote: > Mike, > > Thanks for the info. I have enough to add an entry to the DDL, but I have a few more questions inline. > > On May 14, 2017, at 1:21 PM, Mike wrote: >> >> [updated] >> >> OpenBSD 6.1/amd64 >> NUT 2.7.4p0 (from OpenBSD package) >> >> >> Results of upsc: >> >>

This was very helpful for me, thank you! On Sat, Oct 24, 2020 at 9:06 AM Charles Lepple <clepple at gmail.com> wrote: > The easiest way to tell if upsd is working is to run "upsc -l" on the same > system, which will list the NUT UPS names, and then run e.g. "upsc mge" > (replacing "mge" with the name returned by "upsc -l") > Here was the

NUT 2.8.01 When I pull the USB cable from the UPS, I get two notifications of the nocomm-timer expired. The first notification is in the proper sequence, the second notification occurs after 'commok' occurs. Seems somehow that upssched-cmd is getting a second nocomm-timer expired delayed. Dan -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Aug 7, 2014, at 10:52 PM, Charles Lepple <clepple at gmail.com> wrote: > On Aug 7, 2014, at 10:18 PM, Matthew Stapleton <matthew4196 at gmail.com> wrote: > >> I just got a Cyberpower SOHO Value 1200 ELCD UPS and even with nut 2.7.2, it appears to report battery voltage too low due to the battery scaling function (In drivers/cps-hid.c). Even though the ups has usb id:

> On Dec 3, 2016, at 12:31 PM, Jack McGee <jack at greendesk.net> wrote: >> so this is progress. Thanks! Anything else to check to know it is working as it should? http://networkupstools.org/docs/user-manual.chunked/ar01s06.html#Testing_shutdowns The "FSD" test is more for the NUT logic, which isn't too complicated with only one UPS and one server. If you want to

I need some help here with getting this thing running. Every time I enable NUT on the server, I get a "on battery" status when I know that it is running on house power. This only occurs when I am monitoring it with FreeBSD(NAS4Free) When i plug the same UPS into CentOS 6.7, It works as expected. I am not sure what the difference between the NUT versions other than the base OS would be.