search for: sx650g

...faster as time goes by. root at odroid-u2:~# upsc serverups battery.charge: 84 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 5355 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 8.7 battery.voltage.nominal: 12 device.mfr: CPS device.model: SX650G device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.6.4 driver.version.data: CyberPower HID 0.3 driver.version.internal: 0.37 input.transfer.high: 0 input.transfer.low: 0 input.voltage: 0.0 input.volta...

...> > 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: 9.5 > battery.voltage.nominal: 12 > device.mfr: CPS > device.model: SX650G > device.type: ups > driver.name: usbhid-ups > driver.parameter.pollfreq: 30 > driver.parameter.pollinterval: 2 > driver.parameter.port: auto > driver.version: 2.6.4 > driver.version.data: CyberPower HID 0.3 > driver.version.internal: 0.37 > input.transfer.high: 0 > in...

Hi. I have this this on a Odroid-u2 backing it up. Have the USB from the CyberPower SX650G plug in the Odroid-u2 and when I do a lsusb it looks like this: Bus 001 Device 008: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS The User's Manual list SE450G and SX650G. So I guess they would take the same driver. CyberPower web page has a driver but it's for i386 not ARM like...

(please use Reply-All to keep the list CC'd, thanks) > On Oct 18, 2016, at 8:53 AM, Raymond Day <raymondday at hotmail.com> wrote: > > Wow that was fast thank you Charles. > > Put "upsc" in the /etc/nut/ups.conf and then went to start it with > "upsdrvctl start" but I get this then: No, sorry, I didn't mean to change ups.conf - I meant that

On Oct 18, 2016, at 9:35 AM, Raymond Day <raymondday at hotmail.com> wrote: > > How do I run the git one? I guess it's up to date. Don't, for now. There have been a few posts on the mailing list explaining what to pass to ./configure (or ./autogen.sh, which calls configure) to get the Git version to install over the Debian one, but I would recommend getting the .deb version

I forgot how I ask this. But I just found out. It's a list here: http://lists.alioth.debian.org/pipermail/nut-upsdev/2016-October/007229.html Thanks again. Seems like it's working real good. Is there a way to test if it will turn off my server when the battery power goes to low? -Raymond Day On 10/27/2016 8:37 AM, Charles Lepple wrote: >> On Oct 27, 2016, at 6:43 AM, Raymond

I did just copy and paste on the command line like this: root at odroid-u2:/etc/nut# Shutdown UPS: serverups -bash: Shutdown: command not found root at odroid-u2:/etc/nut# /lib/nut/usbhid-ups -a serverups -k Network UPS Tools - Generic HID driver 0.37 (2.6.4) USB communication driver 0.31 Using subdriver: CyberPower HID 0.3 Initiating UPS shutdown root at odroid-u2:/etc/nut# Don't know why

28 ??????? 2016??. 4:18:06 CEST, Raymond Day <raymondday at hotmail.com> ?????: >I forgot how I ask this. But I just found out. It's a list here: > >http://lists.alioth.debian.org/pipermail/nut-upsdev/2016-October/007229.html > >Thanks again. Seems like it's working real good. > >Is there a way to test if it will turn off my server when the battery >power

I went to the link to test the power off if the battery gets to low. Here is what I got on the command line. root at odroid-u2:/etc/nut# /usr/local/ups/bin/upsdrvctl -t shutdown -bash: /usr/local/ups/bin/upsdrvctl: No such file or directory root at odroid-u2:/etc/nut# find / -name upsdrvctl /sbin/upsdrvctl ^C root at odroid-u2:/etc/nut# /sbin/upsdrvctl -t shutdown Network UPS Tools - UPS driver

Got the: git clone git://github.com/networkupstools/nut.git To work. Had to all so do this: apt-get install autoconf apt-get install libtool Did put driver = usbhid-ups in the /etc/nut/ups.conf file like you said. Here is what I got for it all: root at odroid-u2:~/nut# ./autogen.sh Calling autoreconf... libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `.'. libtoolize: copying

...nearly 30 seconds' worth of "Quick update..." lines, but because the 30-second timer doesn't start until after everything is initialized (takes a few seconds at USB 1.1 speeds...), the "Full update..." line isn't there. But no matter, it is quite similar to the CPS SX650g dump - the HID report is byte-for-byte the same. Notably, the "hidrd-convert" tool fails part of the way through parsing it, which is why I suspect that CPS is not following the HID spec. (That's more applicable for the high/low transfer voltages.) It does seem to be reporting 0% loa...

...t probably gets clamped to zero if it's close enough.) If you stop all of the NUT components, and run the driver manually in debug mode ("/lib/nut/usbhid-ups -a myups -DDD" as root), the raw values before and after scaling are printed. For instance, on issue #482 (attached file "sx650g.txt"), this is what gets mapped to "ups.load": 0.070141 Report[get]: (3 bytes) => 13 14 00 0.070177 Path: UPS.Output.PercentLoad, Type: Feature, ReportID: 0x13, Offset: 0, Size: 8, Value: 20 There are instructions in docs/hid-subdrivers.txt about capturing the debug output...

...worth of "Quick update..." lines, but > because the 30-second timer doesn't start until after everything is > initialized (takes a few seconds at USB 1.1 speeds...), the "Full > update..." line isn't there. > > But no matter, it is quite similar to the CPS SX650g dump - the HID > report is byte-for-byte the same. Notably, the "hidrd-convert" tool > fails part of the way through parsing it, which is why I suspect that > CPS is not following the HID spec. (That's more applicable for the > high/low transfer voltages.) > > It doe...

...to zero if it's close enough.) > > If you stop all of the NUT components, and run the driver manually in > debug mode ("/lib/nut/usbhid-ups -a myups -DDD" as root), the raw > values before and after scaling are printed. For instance, on issue > #482 (attached file "sx650g.txt"), this is what gets mapped to > "ups.load": > > 0.070141 Report[get]: (3 bytes) => 13 14 00 > 0.070177 Path: UPS.Output.PercentLoad, Type: Feature, ReportID: > 0x13, Offset: 0, Size: 8, Value: 20 > > There are instructions in docs/hid-subdrivers.txt...

On Friday 10 January 2020 19:04:11 Charles Lepple wrote: > On Jan 10, 2020, at 5:29 PM, Gene Heskett wrote: > > input.transfer.high: 0 ???? Shouldn't these two be something real > > ???? input.transfer.low: 0 ???? ditto > > Known issue, but only cosmetic: > https://github.com/networkupstools/nut/issues/482 I wonder if the same basic problem is causeing the zero

...te..." lines, but > > because the 30-second timer doesn't start until after everything is > > initialized (takes a few seconds at USB 1.1 speeds...), the "Full > > update..." line isn't there. > > > > But no matter, it is quite similar to the CPS SX650g dump - the HID > > report is byte-for-byte the same. Notably, the "hidrd-convert" tool > > fails part of the way through parsing it, which is why I suspect > > that CPS is not following the HID spec. (That's more applicable for > > the high/low transfer voltage...

On Sunday 12 January 2020 11:14:13 Charles Lepple wrote: > On Jan 12, 2020, at 9:56 AM, Gene Heskett wrote: > >> Instant return, logging this: > > > > in /tmp/info > > > >> 0.000000 Error: too many non-option arguments. Try -h for > >> help. Network UPS Tools - Generic HID driver 0.41 (2.7.4) > >> USB communication driver 0.33 >