[HCL] BlueWalker / PowerWalker VI 650/850 SHL (2018+ Models) supported by usbhid-ups #646
Labels
DDL
HCL
Phoenixtec (USB 0x06DA/0xFFFF)
This USB chip VID/PID is used in many devices, some with different protocols - detection may be hard
PowerWalker
PowerWalker and BlueWalker branded devices
Salicru
Salicru devices
WinPower
Some devices are shipped with WinPower as their vendor's companion software
Comments
|
Thanks for the report, @fionnb. Can you post also the output of Also, have you had a chance to test the shutdown sequence? And... since you mention #475, did you have to apply any of the tweaks listed there to make the driver work as expected? |
|
Pardon me for hijacking this issue. I received a PowerWalker VI 2200 SH today and it seems to use the same USB interface. So far it has been working fine with minimal configuration required. As others have noted in PowerWalker-related issues, the Liebert HID subdriver seems to be lacking certain features. For instance input/output voltage, frequency and configurable options are missing. The VID 0x06da PID 0xffff is also defined in mge-hid subdriver, which seems to have more features than the liebert subdriver, however I have had no luck with tricking the driver into using it by just changing the config. Here's the output in explore-mode: |
|
I noticed that the connection to the UPS is occasionally lost, usually 20-24 hours after starting up (getting Update: did not help, eventually it still stops working. |
|
The same problem for me, configuration details at #483 (comment) |
|
Same here for PowerWalker VI 2200 SH like @Ingramz |
|
I own another UPS (Salicru SPS 650 SOHO+) with the same chipset. Is there any PR with a solution? BTW the software given by the manufacturer (Winpower) shows the missing information and also has the command to disable the buzzer. Thanks! |
|
Same here, struggling with PowerWalker VI 650... |
|
Any update? |
|
Not sure if this helps anyone, but I have the Powerwalker 650 SH and Powerwalker 1200 SH UPS which can only use the usbhid-ups driver. I have these both connected to a raspberry pi 3. Annoying issues at first, is that unless nut driver is installed and active, the default kernel driver will actively probe and spam the kernel log, which is super annoying. It seems in the latest stable debian bullseye is using nut-server 2.7.4 version. Not sure what changes they made, but these ups are now using the MGE HID driver version, previous was the Liberate driver which wasn't stable and missing a load of features, like battery test. Also has the inclusion of the nut-scanner, which helped figure out the dual ups config on the same pc. So far my following config works and is stable sudo cat /etc/nut/ups.conf Make sure to tweak the upsmon.conf And upsd.conf - specifically MAXAGE as that determines the data stale of the driver
Hope this helps anyone? |
|
Output from one of the ups upsc powerwalker-1200 upscmd -l powerwalker-650 |
|
I have |
jimklimov
added
Salicru
|
@ppanagiotis I don't see an apparent entry for your UPS in the |
|
@jimklimov. I don't have a serial converter. It is connected to a raspberry PI through a USB cable. But lsusb sees it like |
|
Also, have you tried building #300, to see if it fixes your issues here, too? |
|
On FreeBSD I see no power / voltage input data: |
|
@vogelfreiheit : Hi, just in case: according to versions, seems you are trying a packaged NUT release (2.7.4) which is rather outdated now compared to master branch (hoping for finalizing 2.7.5 soon). Can you re-test with a recent "master" branch build, and/or libusb-1.0 or libusb-1.0+0.1 branch, please, to see if recent years of codebase evolution added that? Notably, 2.7.4 was tagged in 2016, and this issue is about 2018+ models, so there is a place for discrepancy ;) |
|
Need to try that too, I have a VI 2200 LCD and the blazer drivers weren't working. |
|
This was on Opnsense (FreeBSD), I will check if the a newer port version is available. Thank you for checking in! |
|
I wouldn't count on a newer port, at least if those are based on official releases (which in our case is a baseline sadly too old); but if there are ports more closely tracking the github master branch - it could be an option. The NUT CI farm does regular builds on FreeBSD 12.2 so it should be compatible for builds from scratch; https://github.com/networkupstools/nut/blob/master/docs/config-prereqs.txt#L152 details what you might need to install for a build. |
jimklimov
added
the
WinPower
jimklimov
added a commit
to jimklimov/nut-ddl
that referenced
this issue
Aug 31, 2023
Signed-off-by: Jim Klimov <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I bought a recent BlueWalker / PowerWalker UPS from Amazon.
The exact Product description string from the package is:
"PowerWalker VI 650/850 SHL". I bought the 650VA version
The serial number shows week 43/2018 as manufacturing date.
Syslog says: 06da:ffff Phoenixtec Power Co., Ltd
It identified as a HID device in syslog so I tried usbhid-ups on it - with success:
root@linux[~] upsc powerwalker
Init SSL without certificate database
battery.charge: 96
battery.runtime: 3456
battery.type: PbAc
battery.voltage: 14
device.mfr: PPC
device.model: Offline UPS
device.serial: 000000000
device.type: ups
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.synchronous: no
driver.version: 2.7.4
driver.version.data: Phoenixtec/Liebert HID 0.3
driver.version.internal: 0.41
ups.load: 0
ups.mfr: PPC
ups.model: Offline UPS
ups.productid: ffff
ups.serial: 000000000
ups.status: OL CHRG
ups.vendorid: 06da
Serial Number is shown as zeroes and not edited out, as already discussed in #475.
It is probably the same chipset as in #475 but a slightly different model (with LCD display).
Also the manual and package suggest that this chipset is used for both the 650VA and 850VA models.
The text was updated successfully, but these errors were encountered: