-
-
Notifications
You must be signed in to change notification settings - Fork 362
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: missing battery.voltage on Powercom RPT-800AP #2766
Comments
Cheers, and thanks for the report. I see some A driver start with high verbosity can help track them down, or generally https://github.com/networkupstools/nut/blob/master/docs/hid-subdrivers.txt procedure. |
@jimklimov Here debug output
|
Also
|
So it does have those readings, although probably not scaled well:
I think a higher debug verbosity, 5 or 6, should report also how it parsed these reports (base values and exponents involved). My current guess is that the results were so wildly out of range that they were ignored. It may be that the vendor/firmware got the USB HID encoding wrong and so the values got shifted, in decimal or binary... |
|
According to https://eleccelerator.com/usbdescreqparser/ these bytes meant:
So the values reported are the LogMin - which are probably passed wrong by the device, or scaled like 100x?.. Not sure how 12V (nominal) and 11V-14V (range) fits into those numbers with any decimal factors. |
Thanks, so in your driver's report it's effectively the same log min/max...
I don't see any reports where they would encode a meaningful For comparison, from another device and ticket (#1208 randomly found in the tracker), reasonable reports for these data points look like this:
|
In NUT drivers, we do have a way to fix-up broken report descriptors, but need a pattern to identify the breakage and confirm a correct value by. Cursorily, it seems they were very lazy writing this firmware's protocol... Alternately, if there were more readings and some other reported the correct value, we could add that into the source mapping (so whichever works - wins). But by quick search through this page's text so far, I did not find any "137", "138", "13.7" or "13.8" values in the debug reports... |
Battery voltage reports by UPSMON PRO, but not NUT.
ups.cof
upsd.conf
upsd.users
upsc powercom
The text was updated successfully, but these errors were encountered: