-
-
Notifications
You must be signed in to change notification settings - Fork 368
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cyber Power LX1500GU incorrect output voltage reading #982
Comments
Also noticed that ups_upslog values are not reporting properly: cat /var/log/nut/ups.log20210228 174727 NA NA NA [NA] NA NA |
Configuration files: grep -v "^#" ups.conf[cyberups] grep -v "^#" upsd.conf |grep -v '^$'LISTEN 127.0.0.1 3493 grep -v "^#" nut.conf | grep -v '^$'MODE=standalone grep -v "^#" upsmon.conf | grep -v '^$'RUN_AS_USER root |
Did a /usr/local/libexec/nut/usbhid-ups -DDDDD -a cyberups 2> /tmp/ouput Found the lines which the UPS was reporting: 1.455619 Entering libusb_get_report Yet Hex 0x74 is 116 not 140 8.350308 Report[buf]: (3 bytes) => 12 74 00 |
see #581 and other issues tagged CyberPower. The HID report descriptors are broken. |
What Vendorid and Poductid does your UPS report? |
Unfortunately I disconnected the UPS from the server as I wasn't getting any response a while back. Sorry I can't give you much information on it now. |
I have simmilar issue The input voltage is 226v not 21.6v and the battery is 40.1v not 400v battery.charge: 100 |
Can you please run the driver with higher debug verbosity (3 or more) so it dumps content of the USB Report Descriptors (lots of hex) and interpretation (Path lines) annd copy that log here? Are you in position to build and run current NUT from github master? @flashydave proposed some fixes for broken CPS descriptors, maybe your issue is already resolved. |
Hi, Here is the debug log from the Debian package driver.
I've compiled nut from the source but it does not work, do I need some lib or parameter in configure call ?
|
Thanks, the latter looks like a message from upsd while the driver is not started? |
I have same issue. I wanted to share my information just so this issue is well documented. Everything works properly except the output voltage, as far as I can tell. Version: Generic HID driver 0.41 (2.7.4) Excerpt from usbhid-ups: 0.653344 Entering libusb_get_report Hex 7c = 124 but the value reported is 140. Attached is the complete log of my |
PR #2718 is presumed to fix the broken CPS input/output voltage reports discussed in this issue (although it did not focus on cases of "voltage too high" like most of the reports here). That might have been or not been addressed collaterally. |
Working on FreeBSD 11.4, managed to configure ups.conf, so that my Cyberpower 1500 UPS was reporting but unfortunately some of the values are a bit off:
upsc cyberups
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: 24.0
battery.voltage.nominal: 24
device.mfr: CPS
device.model: LX1500GU
device.serial: QARGU2000275
device.type: ups
driver.name: usbhid-ups
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.version.internal: 0.41
input.voltage: 116.0
input.voltage.nominal: 120
output.voltage: 140.0
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.delay.start: 30
ups.load: 30
ups.mfr: CPS
ups.model: LX1500GU
ups.productid: 0501
ups.realpower.nominal: 900
ups.serial: QARGU2000275
ups.status: OL
ups.test.result: No test initiated
ups.timer.shutdown: -60
ups.timer.start: -60
ups.vendorid: 0764
My, I'm sure the output voltage is 120 not 140.
The text was updated successfully, but these errors were encountered: