PowerWalker VFI 1500 CG PF1 - Shows battery.runtime = 0 #2765
Comments
|
What does driver log with debug say? IIRC there should be some "guesstimation" report, so it can evaluate remaining capacity based on voltage and amount of batteries and load. If it can not figure out the battery counts, that's what you need to default/override. |
|
Hi, The battery.packs = 0 so I added it on the ups.conf. [ups] But still nothing change, have reboot system etc. I have installed the ViewPower Software, and there is shows the runtime. Info of my UPS: https://powerwalker.com/product/10122109/ ` NUT Details
|
|
Seems this last test was with NUT v2.8.0; I am thinking about some fixes for CPS that went into 2.8.1 or 2.8.2 - I believe you have a chance to try the newer versions too? |
|
I have now tested both 2.8.1 and 2.8.2 and both give me the same info. Jan 16 07:01:21 Tower plugin-manager: running: 'anonymous' `
|
jimklimov
added
USB
PowerWalker
|
"What a curious case!.." (something you never want to hear from a doctor) Looking back at the post history, noted one more point to clarify:
The point of In the latest report table (apparently from 2.8.2, thanks) I see that The older reports and PRs I had in mind that might have dealt with this logic, now that I've found them, included (probably a lot of these discussions lead to other tickets):
On the logical side, https://github.com/networkupstools/nut/blob/master/drivers/nutdrv_qx.c#L449-L475 in current codebase is responsible for setting the internal variables (or deciding it won't handle the runtime calibration and report that), and under https://github.com/networkupstools/nut/blob/master/drivers/nutdrv_qx.c#L4089 applies them (the Can you log onto your server to run the driver program directly with raised debug verbosity (ideally 2.8.2 or a newer custom build from master branch), to see in better detail what numbers it juggles? |
|
Hi there, After adding this line: (I have changed the password) upsrw -u admin -p passw0rd -s driver.debug=6 ups The I start seeing this in my logs. Not sure if it relevant but I add it here. I have also added the new override line you wrote earlier.
My current ups.conf: [ups] nut details: `
|
|
I was now testing this added this line into ups.conf: override.battery.runtime = 1800 This line gave me an runtime left of 30 minutes. Not sure if that value is the right one. But when i use the override.* like you wrote. |
|
Well, at least that works. Unfortunately this time would also be misleading as it would stay at 30 minutes while the battery is drained (because override). I think it would be helpful to log the driver start-up with debug, e.g. after stopping other driver instances (service or manual), run one data-dumping loop, e.g. (assuming Debian-ish paths): ...to see how it initializes the values it decides to run with. I wonder if that |
|
So... per https://github.com/networkupstools/nut/blob/master/drivers/nutdrv_qx_voltronic.c#L1126-L1137 the The reply of your UPS however is longer: So these 3 bytes are Does 37 min look realistic with your UPS and load in practice? (The driver then goes to call FWIW, the other values are allegedly:
|
|
Ultimately, this promises to be an easy fix, but you would need a custom build of NUT to test and use it :) https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests should help you get started with a build environment... To check out the tested code, |
…er protocol dialect [networkupstools#2765] Signed-off-by: Jim Klimov <[email protected]>
Nice to see that you probably have an fix for this :). Look like I have to wait to NUT release 2.8.3 since i can't run the commands: :; git clone https://github.com/jimklimov/nut -b issue-2765 nut-issue-2765 I'm running unRaid server with the NUT Plugin.
I was also testing the preview (lastest build) But still the same with no runtime.
The time 37 minutes look right I believe. I have to fire up the ViewPower software and check. But I'm sure i have seen that time.
|
|
Maybe @desertwitch can walk you through building a plugin, or would post a binary to try? Although if you have another computer (or can spin up a VM with USB pass-through on, say, your laptop), you can try in that. |
After installing NUT with different versions, like 2.8.2, 2.8.1, 2.8.0 and 2.7.4
I still having problem with the Runtime left always says 00:00:00 (and in the NUT details is says battery.runtime 0.
Because of this I don't know how much runtime left I have if i run on battery.
[ups]
driver = "nutdrv_qx"
port = "auto"
protocol = voltronic
novendor
vendorid = "0665"
productid = "5161"
product = "OLHV1K5"
desc = "PowerWalker VFI 1500 CG PF1"
pollinterval = 15
serial = "XXXXXXXXXXX"
bus = "001"
Even if i try to add this line in the ups.conf
default.battery.runtime = 1800
It goes to 00:00:00 after a few seconds. Everything else seems to work.
The text was updated successfully, but these errors were encountered: