search for: cp625hga

...ay 21 January 2020 19:52:01 Charles Lepple wrote: > sudo lsusb -v -d 0764:0501 copious output, containing this: idVendor 0x0764 Cyber Power System, Inc. idProduct 0x0501 CP1500 AVR UPS bcdDevice 0.01 iManufacturer 3 CPS iProduct 1 CP625HGa I take it that this is evidence they don't follow the spec to the letter. Here I get the same output with, or w/o the leading sudo. Thank you. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order."...

...t; > which they had been. Was that incorrect? > > You are correct, with both nut-server and nut-client stopped. > > I should not have been lazy, and I should have just pasted the command > line I was thinking of: > > # /lib/nut/usbhid-ups -a myups -DDD 2>&1 | tee /tmp/CP625HGa.txt > > (I was looking at the hid-subdrivers.txt file in the latest NUT tree, > which has the command line amended to not generate that "too many > non-option arguments" error. Also, I wanted it to use the existing > cps-hid.c tables, not the generic "explore" sub...

On Saturday 11 January 2020 18:43:23 Gene Heskett wrote: > On Saturday 11 January 2020 17:00:19 Charles Lepple wrote: > > On Jan 11, 2020, at 3:50 PM, Gene Heskett wrote: > > >> The problem is further downstream. Even after you map HID names > > >> to NUT names, then you run into the fact that CPS and NUT are > > >> interpreting the HID Report

...gt; completed. > > Cheers, Gene Heskett Now I've got another of those WTF questions. This ups doesn't ID itself the same to an lsusb as it does to upsc. From an lsusb: Bus 001 Device 004: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS From a upsc: device.mfr: CPS device.model: CP625HGa ???? And while its not your problem, its keyboard and mouse goes away at random intervals, and isn't rediscovered by unplugging and replugging the hub the dongles are plugged into requireing a powerdown reboot, but the reboot isn't needed for an ssh -Y login! Its the local usb that f...

...t rpi4:~ $ upsc myups Init SSL without certificate database battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 7650 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 14.5 battery.voltage.nominal: 12 device.mfr: CPS device.model: CP625HGa device.type: ups driver.name: usbhid-ups driver.parameter.offdelay: 120 driver.parameter.ondelay: 0 driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.synchronous: no driver.version: 2.7.4 driver.version.data: CyberPower HID 0.4 driver.versio...

Gene's posting: https://alioth-lists.debian.net/pipermail/nut-upsuser/2020-January/011654.html contains a NUT 2.7.4 update for the APC Smart-UPS_1500 device dump at https://networkupstools.org/ddl/APC/Smart-UPS_1500.html Please note the changes since the 2.7.2 report, e.g. ups.delay.start is no longer supported. Roger

On Jan 9, 2020, at 5:51 PM, Gene Heskett wrote: > > On Thursday 09 January 2020 16:59:12 Charles Lepple wrote: > >> On Jan 9, 2020, at 4:39 PM, Gene Heskett <gheskett at shentel.net> wrote: >>> So for starters, what's the best ./configure command line? >> >> There’s this page for matching the layout of an existing Debian >> install: >>

On Jan 9, 2020, at 4:39 PM, Gene Heskett <gheskett at shentel.net> wrote: > > So for starters, what's the best ./configure command line? There’s this page for matching the layout of an existing Debian install: https://github.com/networkupstools/nut/wiki/Building-NUT-on-Debian,-Raspbian-and-Ubuntu But remind me, what are you hoping to get from the later version of NUT? (We don’t

...orkspace $ upsc myups Init SSL without certificate database battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 4410 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 14.5 battery.voltage.nominal: 12 device.mfr: CPS device.model: CP625HGa device.type: ups driver.name: usbhid-ups driver.parameter.offdelay: 120 driver.parameter.ondelay: 0 driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.synchronous: no driver.version: 2.7.4 driver.version.data: CyberPower HID 0.4 driver.versio...

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

...ver and nut-client, both stopped, which > they had been. Was that incorrect? You are correct, with both nut-server and nut-client stopped. I should not have been lazy, and I should have just pasted the command line I was thinking of: # /lib/nut/usbhid-ups -a myups -DDD 2>&1 | tee /tmp/CP625HGa.txt (I was looking at the hid-subdrivers.txt file in the latest NUT tree, which has the command line amended to not generate that "too many non-option arguments" error. Also, I wanted it to use the existing cps-hid.c tables, not the generic "explore" sub-driver.)

...at incorrect? > > > > You are correct, with both nut-server and nut-client stopped. > > > > I should not have been lazy, and I should have just pasted the > > command line I was thinking of: > > > > # /lib/nut/usbhid-ups -a myups -DDD 2>&1 | tee /tmp/CP625HGa.txt > > > > (I was looking at the hid-subdrivers.txt file in the latest NUT > > tree, which has the command line amended to not generate that "too > > many non-option arguments" error. Also, I wanted it to use the > > existing cps-hid.c tables, not the generi...

...y /usr/share/misc/usb.ids, and concatenates the vendor and product strings in the short output format that you quoted. NUT reports those hex numbers as ups.vendorid and ups.productid, respectively, but doesn't look them up in usb.ids. > From a upsc: > device.mfr: CPS > device.model: CP625HGa > These strings are retrieved from the UPS itself. If you run "lsusb -v -d 0764:0501" as root, you should see output similar to what I got from an APC: $ sudo lsusb -v -d 051d: Bus 006 Device 002: ID 051d:0003 American Power Conversion UPS Device Descriptor: bLength...

...s Lepple wrote: > >> sudo lsusb -v -d 0764:0501 > copious output, containing this: > idVendor 0x0764 Cyber Power System, Inc. > idProduct 0x0501 CP1500 AVR UPS > bcdDevice 0.01 > iManufacturer 3 CPS > iProduct 1 CP625HGa > > I take it that this is evidence they don't follow the spec to the letter. It's one of their lesser transgressions :-) Bear in mind that the usb.ids file is a composite of the official company names (for idVendor, probably grabbed from usb.org documents) and idProduct values obs...

...at incorrect? > > > > You are correct, with both nut-server and nut-client stopped. > > > > I should not have been lazy, and I should have just pasted the > > command line I was thinking of: > > > > # /lib/nut/usbhid-ups -a myups -DDD 2>&1 | tee /tmp/CP625HGa.txt > > > > (I was looking at the hid-subdrivers.txt file in the latest NUT > > tree, which has the command line amended to not generate that "too > > many non-option arguments" error. Also, I wanted it to use the > > existing cps-hid.c tables, not the generi...

Cheers, With https://github.com/networkupstools/nut/pull/1906 and https://github.com/networkupstools/nut/pull/1912 (and probably some more later), I've been enhancing NUT driver framework with support for live reload of configuration, primarily to acknowledge changes to debug_min setting in ups.conf - but made in a generic fashion that specific drivers may take advantage of for their

Cheers, With https://github.com/networkupstools/nut/pull/1906 and https://github.com/networkupstools/nut/pull/1912 (and probably some more later), I've been enhancing NUT driver framework with support for live reload of configuration, primarily to acknowledge changes to debug_min setting in ups.conf - but made in a generic fashion that specific drivers may take advantage of for their

On Jan 13, 2020, at 10:17 PM, Gene Heskett wrote: > >>> (I was looking at the hid-subdrivers.txt file in the latest NUT >>> tree, which has the command line amended to not generate that "too >>> many non-option arguments" error. Also, I wanted it to use the >>> existing cps-hid.c tables, not the generic "explore" sub-driver.) >>