-
-
Notifications
You must be signed in to change notification settings - Fork 351
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
Battery Runtime does not match the data from the UPS #1740
Comments
It does look like either max uint16 or a cast'ed "-1" int16, so indeed a
likely limitation. Not at a computer now to investigate sources in more
detail. Might even be a protocol limit if they post a 16-bit value in a
report. In that case it might stay reported at 65535 sec until battery is
depleted under the ~18 hours.
However if possible - please do try checking how current NUT (master or at
least 2.8.0 release) behaves - there were quite a few fixes to usb support
that could help or backfire...
Jim
…On Fri, Dec 23, 2022, 16:55 man55 ***@***.***> wrote:
The Battery Runtime data does not match the data from the APC UPS.
This looks like some kind of variable limitation, since the upsc shows
65535, which is equal to 18 hours 12 minutes and 15 seconds.
But in fact, the APC UPS shows the remaining time as 34 hours 1 min.
How can this be fixed?
upsc output:
***@***.***:~# upsc ***@***.***
Init SSL without certificate database
battery.charge: 93
battery.charge.low: 10
battery.charge.warning: 50
battery.mfr.date: 2022/10/25
battery.runtime: 65535
battery.runtime.low: 1200
battery.temperature: 16.6
battery.type: PbAc
battery.voltage: 52.4
battery.voltage.nominal: 48.0
device.mfr: American Power Conversion
device.model: Smart-UPS 2200
device.serial: AS1250244567
device.type: upsdriver.name: usbhid-ups
driver.parameter.pollfreq: 10
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.synchronous: no
driver.version: 2.7.4
driver.version.data: APC HID 0.96
driver.version.internal: 0.41
input.sensitivity: medium
input.transfer.high: 253
input.transfer.low: 200
input.voltage: 0.0
output.current: 0.50
output.frequency: 50.0
output.voltage: 220.4
output.voltage.nominal: 220.0
ups.beeper.status: disabled
ups.delay.shutdown: 20
ups.delay.start: 30
ups.firmware: 654.19.I
ups.firmware.aux: 7.4
ups.load: 5.2
ups.mfr: American Power Conversion
ups.mfr.date: 2012/12/11
ups.model: Smart-UPS 2200
ups.productid: 0002
ups.serial: AS1250244567
ups.status: OB DISCHRG
ups.test.result: No test initiated
ups.timer.reboot: -1
ups.timer.shutdown: -1
ups.timer.start: -1
ups.vendorid: 051d
[image: Screenshot 2022-12-23 174738]
<https://user-images.githubusercontent.com/30772900/209363376-e90987d4-2ff8-4cdb-979a-8ea4e73ec9d7.png>
[image: Screenshot 2022-12-23 174707]
<https://user-images.githubusercontent.com/30772900/209363404-fc3cd06a-7088-4528-a361-64fb49765ede.png>
—
Reply to this email directly, view it on GitHub
<#1740>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAMPTFACREDLWQ2MCYLQDLTWOXDOPANCNFSM6AAAAAATH376LI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Thanks for the quick response.
|
For a test, NUT is easy to build and run in-place to see how your device fares. Building a replacement for your package, if it does fare better, may be a bit more complicated - find distro recipes and their |
FWIW NUT 2.8.0 is out for more than half a year, apparently distros need time to move forward... |
Too complicated for me and nothing is clear. Couldn't find anything on google search. Need step by step instructions. I am not a programmer and not a sysadmin ( |
Never late to become one ;) I've posted the instructions a few times in the past year, should be in issues. Now in mountains, can't type another on phone. Try the older and maybe easier overvoew at https://github.com/networkupstools/nut/wiki/Building-NUT-on-Debian,-Raspbian-and-Ubuntu |
I should clarify that another UPS APC SUA1000 connected via snmp v1 and does not have this problem, Battery Runtime matches on UPS and NUT monitoring and equals 70680.00
|
Thanks for this data point - so at least not a limitation in NUT data structures. Might still be one in USB-HID protocols or APC's implementation (known buggy in certain other cases - some addressed for NUT v2.8.0 release and later codebase). |
I can't do anything. I did everything as per the link and the NUT broke completely. The driver was not updated and still showed the old version, but the UPS could no longer be found. I re-formatted the SD card, then installed NUT from github according to the instructions in the link, everything compiled without errors, but something went wrong again.
I can do something like this, that is, the files are in place .. but I don’t understand how to make NUT work.
|
That's odd - instructions had lots of paths in |
OK, I have create nut dir manualy (/var/run/nut),
but libusb.so is in place. hm.... |
So, i don't know why the nut-scanner is not working, but in general i got NUT to work.
|
Curious - is Thanks for the note about Per other nuances, it may have been better relevant to older NUT releases that did not have advanced modern-OS integration out of the box. Primary docs are the hordes of text files in the source which try to march along with codebase changes. As for I am surprised that the services did not start - NUT systemd unit files (services, targets and possibly paths) should have got installed - but maybe were not "enabled" effectively to create symlinks from under run-time |
Updated the wiki article |
But after reboot again
I needed to restart the And I found out about the main problem of the topic - [Battery Runtime does not match the data from the UPS]. |
…orkupstools/nut#1740] Signed-off-by: Jim Klimov <[email protected]>
…upstools#1740] Signed-off-by: Jim Klimov <[email protected]>
…upstools#1740] Signed-off-by: Jim Klimov <[email protected]> Signed-off-by: Alex W Baulé <[email protected]>
We have several reports of such situation, often linked with Eaton branded or OEM USB-capable devices. Here's a saved search for opened and closed issues that mention "65535" generally; got ~50 hits and some are about this situation: https://github.com/networkupstools/nut/issues?q=is%3Aissue+65535 Cross-linking to #731 |
…rkupstools#731, networkupstools#1740 et al] Signed-off-by: Jim Klimov <[email protected]>
On Eaton 9E I have no problem with the time left, But seems I have same ups.status= |
The Battery Runtime data does not match the data from the APC UPS.
This looks like some kind of variable limitation, since the upsc shows 65535, which is equal to 18 hours 12 minutes and 15 seconds.
But in fact, the APC UPS shows the remaining time as 34 hours 1 min.
How can this be fixed?
upsc output:
The text was updated successfully, but these errors were encountered: