similar to: [HCL] Cyber Power Systems CP1500AVRLCDa supported by usbhid-ups

OpenBSD 6.1/amd64 NUT 2.7.4p0 (from OpenBSD package) Results of upsc: battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 2902 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 26.9 battery.voltage.nominal: 24 device.mfr: CPS device.model: CP1500AVRLCDa device.serial: CTHGN200xxxx device.type: ups driver.name: usbhid-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: >> >>

On 6/4/2017 4:46 PM, Charles Lepple wrote: [snip] >> 4) when I went down to 95 volts, the "AVR" kicked in to boost the >> voltage without going to battery. This was indicated by a "click" from >> the UPS and an indication on the UPS display. > > In non-explore mode, does the driver report the AVR status? (No need to set things back up if you have

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: >> >> Let me know if you're interested in figuring out if the battery.mfr.date value is stored somewhere else. > > Of course. The UPS is in production (ie., powering the servers in my > house), so it may be a few days before I can ~play~.

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: > > battery.charge: 100 > battery.charge.low: 10 > battery.charge.warning: 20 > battery.mfr.date: CPS Let

On Jun 5, 2017, at 11:21 AM, Mike <the.lists at mgm51.com> wrote: > > Result of the command, where "n" is incremented in a loop: > > # usbconfig -u 1 -a 2 dump_string n > STRING_0x00 = 0x04, 0x03, 0x09, 0x04 > STRING_0x01 = <CP1500AVRLCDa> > STRING_0x02 = <CTHGN200xxxx> > STRING_0x03 = <CPS> > STRING_0x04 = <PbAcid> >

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

On Jun 3, 2017, at 2:21 PM, Mike <the.lists at mgm51.com> wrote: > > 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

Cyber Power UPS Model LX1500GU *upsc output:* root at freenas:~ # upsc ups at localhost battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 5670 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 24.0 battery.voltage.nominal: 24 device.mfr: CPS device.model: LX1500GU device.serial: QAKGP2000252 device.type: ups driver.name:

Cyber Power Systems AVRG750U https://www.cyberpowersystems.com/product/ups/avrg750u/ upsc output: battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 15360 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 24.0 battery.voltage.nominal: 24 device.mfr: CPS device.model: AVRG750U device.serial: <REDACTED> device.type: ups

This UPS is already listed in the compatibility list. But I wanted to add the instant commands supported by upscmd: ============================ Instant commands supported on UPS [PW5125]: beeper.disable - Disable the UPS beeper beeper.enable - Enable the UPS beeper beeper.mute - Temporarily mute the UPS beeper load.on - Turn on the load immediately outlet.1.load.off - Turn off the load on

On 2/21/2017 8:34 AM, Charles Lepple wrote: > On Feb 20, 2017, at 11:19 AM, Mike <the.lists at mgm51.com> wrote: >> >> This UPS is already listed in the compatibility list. But I wanted to >> add the instant commands supported by upscmd: >> > ... >> and note that a delayed shutoff command is not available. >> >> (NUT 2.7.4 on OpenBSD 6.0)

I didn't want to sign up for the nut-devs list or create a git account just to provide this information, so I hope posting this info here is OK... I just bought a Cyber Power Systems EC750G UPS for use as a spare. Here are some info for it: ========================= upsc output: battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime:

I'm trying to setup a server controlling 8 ups, 6 APC Smartups 1500 and two 1000. Because of the number of ups, i connected them using usb cables. I'm using Debian Etch AMD64 and nut 2.2.0 from testing (already tried 2.0 from stable, but had problems reading the ups serials and all the following problems of 2.2). This is my ups.conf: [ups2] driver = usbhid-ups port =

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:

Hi, I didn't found an answer for my question in NUT documentation/FAQ or this mailing list archive so I?m posting it here. I want to start a timer only if both of my UPSes remain on battery. Not just one, both. My UPSes are: - ups1@host-a - ups2@host-b Is it possible to use something like this in upssched.conf? AT ONBATT ups1.* && ups2.* START-TIMER onbattwarn 180 Thanks,

CyberPower Battery Backup with Surge Protection, model LE825G Appears to function properly with the driver listed on the HCL for the Cyber Power Systems ups 2 685AVR USB (usbhid-ups). Tested with shutdown mode "UPS Goes On Battery" with a 5 second timer and the system successfully shutdown as expected. upsc output: upsc ups battery.charge: 100 battery.charge.low: 10

Cyber Power Systems CP600LCD https://www.cyberpowersystems.com/product/ups/cp600lcd/ upsc output: battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 2220 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 13.5 battery.voltage.nominal: 12 device.mfr: CPS device.model: UPS CP600 device.type: ups driver.name: usbhid-ups

Hi, I have been running nut successfully for a long time with my Debian 11 server. I upgraded my server to Debian 12 today, which upgraded nut also from 2.7.4-13 to 2.8.0-7. I noticed that after upgrade there was a upssched process running and taking 100% cpu time. I checked if there were any changes to configuration file formats with nut upgrade and only differences I noticed were a terminology

On 12/8/2016 10:37 PM, Charles Lepple wrote: > On Dec 8, 2016, at 1:34 PM, Mike wrote: >> >> I didn't want to sign up for the nut-devs list or create a git account >> just to provide this information, so I hope posting this info here is OK... > > Not a problem. (Both lists go into the same mailbox on my end.) The important part is the "HCL" subject so I