Skip to content
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

usbhid-ups: Output voltage reading showing wrong voltage #2646

Open
Aerol opened this issue Sep 29, 2024 · 1 comment
Open

usbhid-ups: Output voltage reading showing wrong voltage #2646

Aerol opened this issue Sep 29, 2024 · 1 comment
Assignees
Labels
impacts-release-2.8.0 Issues reported against NUT release 2.8.0 (maybe vanilla or with minor packaging tweaks) Incorrect or missing readings On some devices driver-reported values are systemically off (e.g. x10, x0.1, const+Value, etc.) Tripp Lite USB

Comments

@Aerol
Copy link

Aerol commented Sep 29, 2024

I've got a Tripp-Lite SmartLCD to provide power to my rack and desk, got the CGI scripts served up on a raspberry pi and noticed in upsstats.cgi that output voltage was 1162.0v instead of 116.2v.

I ran upsc smartlcd@localhost and the output.voltage says the same thing there

Init SSL without certificate database
battery.charge: 100
battery.runtime: 2112
battery.type: PbAc
battery.voltage: 26.9
battery.voltage.nominal: 24.0
device.mfr: Tripp Lite
device.model: TRIPP LITE UPS
device.serial: FW-2263 E
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.synchronous: auto
driver.version: 2.8.0
driver.version.data: TrippLite HID 0.84
driver.version.internal: 0.47
driver.version.usb: libusb-1.0.26 (API: 0x1000109)
input.frequency: 59.7
input.voltage: 116.2
input.voltage.nominal: 120
output.frequency.nominal: 60
output.voltage: 1162.0
output.voltage.nominal: 120
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.mfr: Tripp Lite
ups.model: TRIPP LITE UPS
ups.power.nominal: 1500
ups.productid: 2007
ups.serial: FW-2263 E
ups.status: OL CHRG
ups.timer.reboot: 65535
ups.timer.shutdown: 65535
ups.vendorid: 09ae
ups.watchdog.status: 0
@jimklimov
Copy link
Member

Looking at drivers/tripplite-hid.c source, it is full of tweaks dependent on model ID. Curiously, here the input.voltage seems OK so it's not that both of them need to be scaled down.

But probably your best bet is to build current NUT configured for in-place upgrade (see wiki), with sources changed to separate "io"_voltage multiplier into two variables, and introduce a new method similar to existing tweaks bound to modelid 0x2007. And post a PR with tested results :D

@jimklimov jimklimov added Tripp Lite USB impacts-release-2.8.0 Issues reported against NUT release 2.8.0 (maybe vanilla or with minor packaging tweaks) Incorrect or missing readings On some devices driver-reported values are systemically off (e.g. x10, x0.1, const+Value, etc.) labels Sep 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
impacts-release-2.8.0 Issues reported against NUT release 2.8.0 (maybe vanilla or with minor packaging tweaks) Incorrect or missing readings On some devices driver-reported values are systemically off (e.g. x10, x0.1, const+Value, etc.) Tripp Lite USB
Projects
Status: Todo
Development

No branches or pull requests

4 participants