-
-
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 maximum at 65535 [Dell; rebranded Eaton?] #731
Comments
ups.test.result: Aborted
NUT gets the size of the variables from the USB HID descriptor. The 65535 is probably intended to be a 16-bit signed value of -1 for "unknown". I would recommend running a battery test, and seeing if the "ups.test.result" variable changes.
|
It does change as i have seen it loading the batteries and reaching the limit.
|
Closing since test seems to have fixed the reported value. |
After i saw you closed the bugfix I tried to investigate a bit more. Result: If the UPS load is below or equal to 10%, it does not calculate the runtime properly. There is also a paragraph in the manual saying, that a battery test can only be done with a load above 10%. However, last time it still started properly. So we can assume it's a Firmware issue. Some data
|
Some addon... Once the UPS is online again, it seems to do some calculations, but I doubt one can trust the values.
|
…rkupstools/nut#731] Signed-off-by: Jim Klimov <[email protected]>
…rkupstools#731, networkupstools#1740 et al] Signed-off-by: Jim Klimov <[email protected]>
Hi!
I'm using a Dell UPS 2700W with an extended Battery Modul (EBM).
As i have a quite low load on the UPS (about 5%) it's easy to reach a very high runtime (in sec)
For now it seems like i reached the max of a 16Bit variable.
Is this limit given by NUT? if so, could you please increase it?
Thanks!,
Rob
PS: Here some more data about the UPS:
The text was updated successfully, but these errors were encountered: