similar to: POWEREX VI 1000 LED

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.

[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

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

Hi Arnaud, I received several replies from technical support. It turned out that according to the UPS serial number it had been manufactured in 2012. So, the device should support the ability to disable the beeper. But still I can not disable the beeper using the latest version of UPSMON Plus in Windows: http://www.pcm.ru/data/download/public/soft/setup_upsmon_v2.9.rar (don't know why; the

Hi ALL, Powercom Imperial IMP-525AP seems to be fully compatible with NUT. Unfortunately, I can not disable beeper. upscmd -u {NUT_USER} -p {NUT_PASSWORD} powercom beeper.toggle returns *OK*, however, ups.beeper.status=enabled Thank you, Sergey ========== Additional info: 1) $ upsc powercom battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 30 battery.date: 2010/01/01

Hi Charles, Yes, it looks like my g++ does contain STL library which might be just my specific case... However, as a temporary solution I disabled nutclient in Makefile (please find the file attached). And nut-2.7.3 can be compiled now. Thanks, Sergey On Wed, Jul 8, 2015 at 4:13 AM, Charles Lepple <clepple at gmail.com> wrote: > On Jul 6, 2015, at 10:32 AM, Sergey Talchuk

Hi Charles, Thanks for the prompt reply! Errors occur when execute make: /bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../include -MT nutclient.lo -MD -MP -MF $depbase.Tpo -c -o nutclient.lo nutclient.cpp &&\ mv -f $depbase.Tpo $depbase.Plo libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../include -MT nutclient.lo -MD -MP -MF .deps/nutclient.Tpo -c

Dear developers, libnutclient has been added as a C++ alternative to libupsclient in 2.7.1. As a result I can't compile nut 2.7.3 with gcc-3.3.6. There wasn't such a problem with nut-2.6.5. Is it possible to add a configuration parameter like '-without-libnutclient' to provide better compatibility with older gcc versions please (since libnutclient is an alternative to

Dear developers, libnutclient has been added as a C++ alternative to libupsclient in 2.7.1. As a result I can't compile nut 2.7.3 with gcc-3.3.6. There wasn't such a problem with nut-2.6.5. Is it possible to add a configuration parameter like '-without-libnutclient' to provide better compatibility with older gcc versions please (since libnutclient is an alternative to

Hello, i have a server which supposed to control three Eaton UPS connected by USB cables. Each UPS is Eaton NV 2000H. (eaton_1, eaton_2, eaton_3) The connection is fine with each UPS, if it is configured alone. If i configure two or all three, the connections broke up. After nut started, tried to start upsdrv manually (eaton_1. The log: Apr 4 00:43:46 mail blazer_usb[10799]: Startup

On Jan 2, 2012, at 10:51 AM, Vladimir Micovic wrote: >> Bus 003 Device 004: ID 0665:5161 Cypress Semiconductor USB to Serial > Unfortunately, this device ID is used by several different vendors. What does "lsusb -vvv -d 0665:5161" show? > Also, what OS and kernel are you using? (I thought certain kernels had USB-to-serial drivers for that chip.) > -- > Charles

Hi Team, I've been experimenting with getting the PowerShield Defender 1200VA UPS working and it appears to be supported by the blazer_usb driver, although it did not have the correct permissions within udev to load the driver as the non-root user after an RPM install on Fedora Core 16. [root at localhost ~]# lsusb ... Bus 006 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial

Hello guys, Please help me to resolve the issue. I bought 'SVEN Power Pro+ 500 USB' UPS few days ago and tried to setup NUT 2.6.0 to work with it. blazer_ups driver doesn't recognize the UPS :( The Manufacturer provides 'PowerD' software for linux with installation instractions on a CD (see example below). --------===------- Welcom to PowerManager System!

Hello, Network UPS Tools - Generic HID driver 0.38 (2.7.2) USB communication driver 0.32 No matching HID UPS found Driver failed to start (exit status=1) I followed a thread with the same title, more or less, having permission problems. I applied that solution. My problem seems different. # lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 010: ID 0665:5161

Hello, i try to setup NUT service to read/control my UPS but without success. Problem is when i try to start "/usr/local/ups/bin/upsdrvctl -DDDD -u root start" i got: /Network UPS Tools - UPS driver controller 2.6.2/ / 0.000000/ /If you're not a NUT core developer, chances are that you're told to enable debugging/ /to see why a driver

Hi all, after a change of UPS (to Atlantis Host Power 851) I began to use the new driver blazer_usb and compared to old one (blazer used with serial connection) I noted more CPU use and errors in dmesg: [...] [256712.584370] usb 4-5: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 [256789.640795] usb 4-5: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8

Hi all! Maybe possible adds something in megatec_usb driver for normal working with ippon 2000? This is output for drivers megatec_usb and blazer_usb: =========================================================== gate# /usr/local/libexec/nut/megatec_usb -DDDD -a IPPON Network UPS Tools - Megatec protocol driver 1.6 (2.4.1) Serial-over-USB transport layer 0.10 debug level is '4' Checking

Hi everyone, I installed latest version of Nut on Debian Wheezy 64bit. This is a virtual server hosted by VMware ESXi. It's a Nagios monitoring server. I configured one Sweex UPS in ups.conf and everything is working. ups.conf: [sweex1] driver = blazer_usb port = auto runtimecal = 1100,100,2200,50 Now I want to connect two more identical UPSes to the same server, total of 3

Ok - before stale data: After stale data: $ lsusb -d 0665: Bus 002 Device 004: ID 0665:5161 Cypress Semiconductor USB to Serial After stale data: And the gzipped log attached: On 2 January 2015 at 21:56, Charles Lepple <clepple at gmail.com> wrote: > On Jan 2, 2015, at 2:43 PM, Mike Raath <raathm at gmail.com> wrote: > > Not sure what other logs I can provide to try

On Jan 2, 2015, at 3:33 PM, Mike Raath <raathm at gmail.com> wrote: > Sorry, I messed up my reply a bit. > > The output of the lsusb command is the same before and after the data goes stale. > > $ lsusb -d 0665: > Bus 002 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial > OK. That usually means that the VM kernel doesn't see that the device is