similar to: Power Walker VI 2000 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

Hi NUT developers! Are there in progress development of NUT driver that supports AIPTEK PowerWalker VI 2000 LCD - Art-No 310064 (http://www.powerwalker.com/line-interactive.html)? Thank you in advance! Regards, Dimitar Angelov

[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

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.

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

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

Was anybody able to read the logs and come up with an error? -------- Original Message -------- Subject: Re: [Nut-upsuser] Powerwalker VI 2200VA LCD Local Time: October 16, 2016 11:47 PM UTC Time: October 16, 2016 9:47 PM From: hyouko at gmail.com To: Lars de Bruin <lars at larsdebruin.net> nut-upsuser <nut-upsuser at lists.alioth.debian.org> 2016-10-10 15:28 GMT+02:00 Lars de

The UPS seems to disconnect totally, i need to physically disconnect the cable to get the UPS connected again. A reboot is not enough. Also tried 2 different cables, the one i use now is shielded + 2 ferrite chokes to limit interference. But i want to use NUT since i dont have enough resources to run X.. -------- Original Message -------- Subject: Re: [Nut-upsuser] Powerwalker VI 2200VA LCD

Hi, - The device never re-connects to the system, i have to physically remove the USB plug and insert it again for the device to come back. - This does not happen when running the driver from the supplier. (java process) - When i poll every 60s it works for about 3 days, anything lower or higher causes it to disconnect faster - The big log i sent is not the output of the driver? if not how can i

> [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?

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

Hi. I'm from Russia. I try to use NUT with PowerWalker vi 400 se (usb). I use FreeBSD 7.0 (amd64) and megatec_usb driver. Settingup the NUT with FreeBSD installation procedure (Thierry Thomas, from FreeBSD). PowerWalker connect to the computer by usb cable on port usb0 (uhib0). NUT don't starting, and talk to me that supporting device not found. Please, help me. Thank's! With best

Hi, I have a small home-use UPS for my home server from powerwalker (http://powerwalker.com/de/index.php?option=com_content&task=blogcategory&id=63&Itemid=106 sorry I only found a german version). It has a USB and a serial connector. lsusb lists it as "06da:0003 Phoenixtec Power Co., Ltd", in /proc/bus/usb/devices it sais "Manufacturer=OMRON" and

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

I dont think the logs ends to early. The UPS had been offline for 1 day at least before i stopped the process. Could the issue be that NUT driver does not see the USB device disconnect? -------- Original Message -------- Subject: Re: [Nut-upsuser] Powerwalker VI 2200VA LCD Local Time: 11 November 2016 1:12 AM UTC Time: 11 November 2016 00:12 From: hyouko at gmail.com To: Lars de Bruin

Hello, I'm having problems when trying to execute an deep battery test. UPS Model: PowerWalker VI 1000. root at HP-Opreon:/# upscmd PowerWalker at localhost test.battery.start.deep Username (root): admin Password: Unexpected response from upsd: ERR ACCESS-DENIED /etc/hosts.allow: <code> # /etc/hosts.allow: list of hosts that are allowed to access the system. # See

On Dec 2, 2013, at 11:01 AM, Danijel ?ili wrote: > Since the permission change helped, I can now continue with the > configuration. Thanks for the help :) What are the final permissions? If possible, we would like to fix the NUT package so that it works out of the box. Removing the MODE= line seems like it should either fail due to more restrictive default permissions, or it would work

On Dec 3, 2013, at 12:06 PM, Danijel ?ili wrote: > OK, but since I moved the cable around its now 3/2: > > crw-rw-r-- 1 root nut 189, 257 Dec 3 18:04 /dev/bus/usb/003/002 ... which is what the MODE=664 udev rule set. Is there by chance some other udev rule which might match your ups? (There are a number of devices out there which use Cypress chips - maybe another package changed the

[please keep the list CC'd for future reference.] On Dec 4, 2013, at 1:10 AM, Danijel ?ili wrote: > Even if there is, I just checked and all of the rules have MODE=664. I had concerns that the MODE parameter might need an explicit leading "0" for octal, but at least in the latest code, it is being parsed with strtol(..., 8). > Also, I don't know how to check which rules

2016-10-03 14:56 GMT+02:00 Lars de Bruin <lars at larsdebruin.net>: > Hi, > > The UPS is now connected via HID-USB, but seems to randomly disconnect. > Sometimes after a few hours, other times days... > Any suggestions? A log would help, but, in general, if the device disconnects and, after a short time, the connection is restored, it could be a cable problem, or the UPS not