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

[please use Reply-All - this list does not modify the reply-to header] > On Nov 23, 2016, at 10:30 AM, Craig STCR <craig.stcr1 at gmail.com> wrote: > > It looks like the CyberPower Cyber Power Systems CP685AVR supported by > usbhid-ups has a favorable device dump linked to the Devices Dumps > Library page here: > >

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

Thank you, looks like the regex idiosyncracy might have been the issue. My current file: [sl] driver = usbhid-ups port = auto desc = "CyberPower UPS SL" product = "SL.*" productid = 0501 vendorid = 0764 #model = "SL Series" [ab] driver = usbhid-ups port = auto desc =

Thanks! FWIW if you do get to test new code, https://github.com/networkupstools/nut/pull/1811 adds warnings for situations like yours. Would be great to check if it works actually, with many "same-serial" devices :) Jim On Sat, Jan 14, 2023, 23:39 Bruce Pleat <bpleat at gmail.com> wrote: > Thank you, looks like the regex idiosyncracy might have been the issue. > > My

Part of what made my life harder is nut-scanner isn't in the package. Once I get a chance, I'll update to 2.8, but that'll be a little while off. (Any clue how to get 2.8 included in the package provider for my Raspberry Pi is presumably beyond the scope of this list, but if someone knows and wants to let me know, I wouldn't complain...) On Sat, Jan 14, 2023 at 3:12 PM Jim

Just a note: recent PRs are naturally not in 2.8.0 release (April 2022), but would be in eventual 2.8.1 Jim On Sun, Jan 15, 2023, 00:51 Bruce Pleat <bpleat at gmail.com> wrote: > Part of what made my life harder is nut-scanner isn't in the package. > > Once I get a chance, I'll update to 2.8, but that'll be a little while off. > (Any clue how to get 2.8 included in

So, regarding wildcards (globs) vs. regular expressions, the latter being used for such matches, I believe (did not check now) the config sections should look like this: [cp] driver = usbhid-ups port = auto desc = "CyberPower UPS CP" model = "CP685AVR-G" vendorid = "0764" product = "CP.*" Note the

I've been using nut with a serial device for a while, but today I tried hooking up this new CyberPower 685 unit via newhidups--since it seemed better supported over USB than serial, based on reading the list archives and cvs logs. Unfortunately, I can't connect to it. My system sees the device: uhid1: CPS UPS BF700, rev 1.10/0.01, addr 2, iclass 3/0 ... and I have chmodded all

Alignment in LLVM is currently represented with an `unsigned`, sometimes an `uint32_t`, `uint64_t` or `uint16_t`. FWIU the value has the following possible semantics: - 0 means alignment is unknown, - 1 means no alignment requirement, - a power of two means a required alignment in bytes. Using `unsigned` throughout the codebase has several disadvantages: - comparing alignments may compare

Trying to configure multiple UPS on one Raspberry Pi 4 (Bullseye). Issue: Whenever more than one is plugged in, one shows as all - as in "upsc x" for all of them shows identical information for one UPS rather distinct for each plugged in. OS: /proc/version = "Linux version 5.10.103-v7l+ (dom at buildbot) (arm-linux-gnueabihf-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GNU ld (GNU

I just got NUT 2.0.1 running on my Debian system at home.? I have a new CPS UPS connected via USB.? Everything is working fine, except the UPS is showing a value of 120% charged.? Any idea what causes this?? Here's the upsc output for my UPS: battery.charge: 120 battery.charge.low: 10 battery.charge.warning: 20 battery.runtime: 1320 battery.runtime.low: 300 battery.type: PbAcid

Thank you both for answering. I tried with and without the "-x" as the manual wasn't clear enough to me. I tried with and without wildcards (e.g., "*SL*", "*SL Series*", "SL Series" for that one). I tried other permutations before asking for help here. ("model" throws an error, "-x model" doesn't, which was confusing) I am not

I regularly use '-DCMAKE_CXX_FLAGS' when configuring CLang/LLVM to distinguish my builds (Alpha/Beta/Final) or to build custom versions, usually by adding additional '-D' flags, but I discovered I had to add the ':STRING' qualifier to it when invoking 'cmake'. With 'gmake' this is equivalent to '--with-extra-options="whatever flags":

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

This is just for compiler-rt. The reason for having -fno-omit-frame-pointer is that tools like https://perf.wiki.kernel.org/index.php/Main_Page would work on ASAN binaries. Adrian On Mon, Jul 20, 2015, at 02:23 PM, adek at adek.io wrote: > Hey, > > Thanks for ideas. I tried them on, but none of them succeeded. > > If I remove this line: >

Woah this is a good idea. I'd ask that alignment come in different bit sizes and endienesses so that we can add an alignment type to ELF types. I would love to review this and add it to llvm-objcopy. We have special functions to handle all of these 'zero' cases. Several other bits of code I've seen/written have to find maximum alignment and I'd imagine the mistake of not

Hi all, Am setting up a internet cyber cafe of roughly 50 or so boxes running on CentOS 5.0. Now the question is. Does someone on the list know of a open source cyber timer/cybermanager which runs on CentOS(LINUX) and where i can download it? All that am getting are M$ based.(grrrh). Thanks. ------------------------------------------------- David Maina. Systems/Network Administrator. PdE-Kenya.

I'm currnetly using NUT 2.4.3 to monitor a Cyber Power 1000AVRLCD UPS. I found the following in the mailing list archive: http://lists.alioth.debian.org/pipermail/nut-upsdev/2010-March/004673.html and I want to inform the list that I had to apply the same patch to libhid.c in order to monitor that UPS. -spc

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