Displaying 20 results from an estimated 2000 matches similar to: "Please share experience with PowerWalker UPSes"
2014 Mar 06
1
PowerWalker VFI 3000RT LCD: Device or resource busy
UPS: PowerWalker VFI 3000RT LCD
CentOS 6.5, nut installed from RPM package:
nut-2.6.5-2.el6.x86_64
nut-client-2.6.5-2.el6.x86_64
Driver: blazer_usb
Problem description:
USB device "loops" when starting blazer_usb. USB device permissions are ok.
Receives some information.
Error messages:
"failed to claim USB device: could not claim interface 0: Device or
resource busy"
2015 Mar 12
0
NUT vs PowerWalker/BlueWalker SNMP with VFI 1500RM/3000RM LCD models
Hello,
I have two UPS from PowerWalker: VFI 1500RM LCD and VFI 3000RM LCD both
equiped with SNMP card, but NUT with snmp-ups does not support them.
PowerWalker declare support RFC1213, RFC162 but there is a problem with
some snmp values:
# upsdrvctl start
Network UPS Tools - UPS driver controller 2.6.4
Network UPS Tools - Generic SNMP UPS driver 0.66 (2.6.4)
Detected 3K on host 10.0.0.236
2011 Mar 26
1
Help with Aiptek PowerWalker VFI 1000 LCD and Konig CMP1200
Hello,
I have just installed nut_2.6.0 from Debian testing, do anyone know the
correct driver for this ups? The blazer_usb don't report
battery-charge, the bundled software report charge and runtime.
root at pluto<~>upsc powerwalker
battery.voltage: 40.86
battery.voltage.nominal: 36.0
beeper.status: enabled
device.mfr:
device.model: HV 1K
device.type: ups
driver.name: blazer_usb
2020 Jan 24
0
System with MGE UPS shuts down too early
OK, my UPS turned out to be older that I thought. I apparently bought
and installed it in September 2016 (not 2017 as I initially wrote). That
makes for over 3 years of work, which is over the life expectancy of the
batteries, so I ordered new battery pack.
However, how could I make a full charge/discharge test? Should I disable
SHUTDOWNCMD in upsmon.conf? Or is there any other way to ignore
2020 Jan 11
0
System with MGE UPS shuts down too early
On January 11, 2020 1:18:27 PM GMT+02:00, "Georgi D. Sotirov" <gdsotirov at gmail.com> wrote:
>Hello,
>
>I'm experiencing a strange early shutdown behavior with the following
>system:
>
> * */OS/*: Slackware Linux 14.2 x86_64
> * */NUT/*: 2.7.4 (from my own package
> <https://sotirov-bg.net/slackpack/pack.cgi?id=4083>)
> * */UPS/*: MGE
2015 Jul 04
0
upsd: ERR ACCESS-DENIED with PowerWalker UPS
[please keep the list CC'd]
On Jul 4, 2015, at 8:09 AM, Sami M?ntysaari <sm at sami-mantysaari.com> wrote:
> I have reloaded it, but still the same result.
>
> Any ideas?
Not sure. Can you provide any additional details about the OS and version of NUT?
> snip from syslog:
> <code>
> Jul 4 15:04:25 HP-Opreon kernel: [66083.548290] usb 2-1: usbfs:
>
2017 Jan 19
1
PowerWalker VFI 2000 RT LCD
Hi all,
I have problem with UPS from PowerWalker model VFI 2000 RT LCD over USB
(didn't try serial yet).
UPS should work via HID driver but ups.status is not rendered properly.
Specification of UPS says USB HID compatible.
HID driver is the only one which talks with UPS as i try a few from
/lib/nut.
I use driver usbhid-ups (which communicate with ups), but subdriver
resolving is
2020 Jan 11
4
System with MGE UPS shuts down too early
Hello,
I'm experiencing a strange early shutdown behavior with the following
system:
* */OS/*: Slackware Linux 14.2 x86_64
* */NUT/*: 2.7.4 (from my own package
<https://sotirov-bg.net/slackpack/pack.cgi?id=4083>)
* */UPS/*: MGE Ellipse PRO 1600
<powerquality.eaton.com/Products-services/Backup-Power-UPS/Ellipse-PRO.aspx>
(bought in September 2017)
*/Problem
2016 Sep 27
2
Powerwalker VI 2200VA LCD
Hi,
I am unable to get my UPS working with NUT.
Information:
lsb_release -a:
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 8.0 (jessie)
Release: 8.0
Codename: jessie
apt-cache policy nut-server:
nut-server:
Installed: 2.7.2-4
Candidate: 2.7.2-4
Version table:
*** 2.7.2-4 0
500 http://mirrordirector.raspbian.org/raspbian/ jessie/main armhf
Packages
2020 Jan 27
1
Nut-upsuser Digest, Vol 175, Issue 30
Roger,
here is my output of ps -elf |grep upssched
root at nutpi:~# ps -elf |grep upssched
0 S root 1242 1191 0 80 0 - 1834 pipe_w 05:23 pts/0 00:00:00
grep upssched
No timer, just the grep of upssched..
On Mon, Jan 27, 2020 at 4:27 AM <nut-upsuser-request at alioth-lists.debian.net>
wrote:
> Send Nut-upsuser mailing list submissions to
>
2013 Dec 02
0
Installing NUT for PowerWalker VI 1500 LCD
[Please subscribe to the mailing list: http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser ]
On Nov 28, 2013, at 4:10 PM, Danijel ?ili wrote:
> Since the provided drivers come with absolutely no installation instructions, I turned to NUT.
>
> The compatibility list says "blazer_usb" should be used for PowerWalker's devices, so that's what I put in my
2016 Oct 03
2
Powerwalker VI 2200VA LCD
Hi,
The UPS is now connected via HID-USB, but seems to randomly disconnect.
Sometimes after a few hours, other times days...
Any suggestions?
-------- Original Message --------
Subject: Re: [Nut-upsuser] Powerwalker VI 2200VA LCD
Local Time: October 2, 2016 11:50 PM
UTC Time: October 2, 2016 9:50 PM
From: hyouko at gmail.com
To: Lars de Bruin <lars at larsdebruin.net>
nut-upsuser
2018 Apr 12
0
PowerWalker VI 1500 LCD NUT problem detecting device
Hi all,
can anybody sugggest a proper solution to the problem described here:
http://nut-upsuser.alioth.debian.narkive.com/wIMnftV0/installing-nut-for-
powerwalker-vi-1500-lcd
Righet now I am trying to make it go and running on version:
root at raspberrypi:/home/pi/deb# apt-cache policy nut
nut:
Installed: 2.7.2-4
Candidate: 2.7.2-4
Version table:
*** 2.7.2-4 0
500
2013 Nov 28
2
Installing NUT for PowerWalker VI 1500 LCD
Since the provided drivers come with absolutely no installation
instructions, I turned to NUT.
The compatibility list says "blazer_usb" should be used for PowerWalker's
devices, so that's what I put in my conf:
[pwvi]
driver = blazer_usb
port = auto
desc = "PowerWalker VI 1500 LCD"
Since I use Ubuntu Server 13.10 so I installed nut from apt.
2013 Dec 02
5
Installing NUT for PowerWalker VI 1500 LCD
On Mon, Dec 2, 2013 at 2:25 PM, Charles Lepple <clepple at gmail.com> wrote:
>
> [Please subscribe to the mailing list: http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser ]
>
> On Nov 28, 2013, at 4:10 PM, Danijel ?ili wrote:
>
> > Since the provided drivers come with absolutely no installation instructions, I turned to NUT.
> >
> > The
2016 Oct 02
0
Powerwalker VI 2200VA LCD
> [powerwalker]
> driver = blazer_usb
> vendorid = 06da
> port = auto
> desc = "Powerwalker VI 2200VA LCD"
> productid = ffff
> bus = "001"
The VID/PID combo 06da/ffff is used by some devices supported by the
'usbhid-ups' driver: did you have a chance to try it?
2023 Jan 13
1
Support of PowerWalker CSW / GXB series
Hello,
can anyone comment on how well these ups work with NUT and which is the
preferred driver?
I haven't found much information in the mailing list, seems blazer_usb,
nutdrv_qx etc work (sometimes)?
Specifically I am looking at Powerwalker VI 1200 CSW and Powerwalker VI
1500 GXB models.
2011 Jun 02
2
[HCL] Hardware Compatibility List - PowerWalker VI 850 LCD
Hello list,
just a quick email to report that the following UPS was supported (mostly)
out of the box:
Model: PowerWalker VI 850 LCD
Driver: blazer_usb
upsc Output (please note I have manually populated the high and low
voltages):
battery.charge: 100
battery.voltage: 13.50
battery.voltage.high: 13.5
battery.voltage.low: 10
battery.voltage.nominal: 12.0
beeper.status: enabled
device.type: ups
2014 Jan 03
3
Problems with blazer_usb. Driver will not shut down my UPS
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi there!
I don't know if you are able to help me. Have tried almost everything
at this point..
I recently switched from a BlueWalker(Powerwalker?) PW UPS VI2000 LCD
2000VA offline UPS to a BlueWalker(Powerwalker?) PW UPS VFI 1500 LCD
1500VA Online UPS.
Seems like the driver is accepting both, however, the shutdown command
wont work. And this
2020 Jan 11
4
System with MGE UPS shuts down too early
OK. I'll try it, but it really puzzles me how the battery could have
gone bad for just 15 months. The online power is pretty stable, so the
battery hasn't gone through many charge/discharge cycles...
Regards,
--
Georgi
On 11.1.2020 at 14:24, Manuel Wolfshant wrote:
>
> indicates that the UPS thought that battery was close to depleted and decided to shutdown. I suggest to fully