similar to: NUT vs PowerWalker/BlueWalker SNMP with VFI 1500RM/3000RM LCD models

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

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

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"

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

Folks, while I've got the above combination to compile and run under Solaris 10, it seems that there are still problems in the libusb/ugen driver stack from Sun and or the APC Smart UPS 1500, so things aren't actually working. It seems that the APC Smart UPS 1500RM doesn't return the HID descriptor length information in 0x21 as noted in a previous thread, but in my case, it also

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

Dear Nut-UPSdev Team, First of all I would like to appreciate the great job you are doing. Your work is very important and helpful for all UPS users. I found that you show compatibility with blazer_ser and blazer_usb for six of our models. Please inform me how we can make it happen that all our models become compatible? Who from your team added the compatibility with PowerWalker VI 850 LCD?

I have written a few different summary functions. I want to calculate the statistics by groups and I am having trouble getting the output as a dataframe. I have attached one example with a small dataset that calculates summary stats and percentiles, I have others that calculate upper confidence limits etc. I would like the output to be converted to a dataframe with one of the columns as the

2006/3/27, devzero@web.de <devzero@web.de>: > ... > ps: > Furthermore, there seems some inconsistency between driver.list and website: > > # Network UPS Tools driver.list > # > # This file is used to build the compat.html on the web server. Any line > # with exactly 4 arguments will be turned into an entry on there. > # Naturally, it is read by parseconf, so the

Hi debian jessie, nut 2.7.2-4 APC Smart-UPS 1500 connected through USB, running nut driver usbhid-ups This UPS powers my switches, internet connection and my monitor server that monitors this and my other UPSes + runs smokeping and nagios. But recently a powerloss seemed to have shutdown my monitor PC immediately, so it did not shut down the other servers cleanly. Power seem to be lost

Hi, I have the following data and there is no binary operator contained, however, I still receive the error message when running unitrootTest function, could someone give me a guidance on it?? >readClipboard() [1] "245" "246" "261.5" "275.5" "307" "284.5" "289" "313.5" "323.75"

Hello, I have an NETYS RT 1/1 UPS, which is not fully supported. Starting snmp driver displays: [root at kvm1 ~]# snmp-ups -a local Network UPS Tools - Generic SNMP UPS driver 0.66 (2.6.4) Duplicate driver instance detected! Terminating other driver! No matching MIB found for sysOID '.1.3.6.1.4.1.2254.2.4'! Please report it to NUT developers, with an 'upsc' output for your

Hello, I have an NETYS RT 1/1 UPS, which is not fully supported. Starting snmp driver displays: [root at kvm1 ~]# snmp-ups -a local Network UPS Tools - Generic SNMP UPS driver 0.66 (2.6.4) Duplicate driver instance detected! Terminating other driver! No matching MIB found for sysOID '.1.3.6.1.4.1.2254.2.4'! Please report it to NUT developers, with an 'upsc' output for your

Hello all, I have so far used only Eaton UPSes, but I'm considering buying PowerWalker VFI 3000RT LCD and on NUT compatibility page <https://networkupstools.org/stable-hcl.html> I see that PowerWalker devices are supported by blazer_usb <https://networkupstools.org/docs/man/blazer_usb.html> driver, which is "/based on fragments of publicly available protocol/". Over

Hi, Just started using NUT with a Liebert PSI-XR 3000 with an Intellislot web card. It seems I can't get it to run properly. I am using NUT 2.6.0 built from source on Ubuntu 8.0.4 . My build parameters are : ./configure --enable-strip --with-linux-hiddev=/usr/include/linux/hiddev.h --with-udev-dir=/lib/udev \ --prefix=/usr \ --exec-prefix=/ \ --sysconfdir=/etc/nut \

I have a Smart-UPS RT 3000 XL connected via serial cable to TrueNAS TrueNAS-9.2.1.2-RELEASE-x64 (002022c) which runs on FreeBSD 9.2-RELEASE-p3. When I start the NUT service, I get the message: Oct 20 01:53:50 truenas notifier: very old or unknown APC model, support will be limited Which I interpret as an indicator of less than optimal operating mode. I suspect that the model identifier is not

Hello, I encountered a problem with my APC Smart-UPS 750, connected via USB, using newhidups. Without any reason, nut/upsmon shut down my PC: >>> Oct 13 12:57:08 echo kernel: usb 2-9.1.1: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt 161 rq 1 len 8 ret -71 Oct 13 12:57:12 echo upsmon[5060]: UPS smart750@localhost on battery Oct 13 12:57:12 echo upsmon[5060]: UPS smart750@localhost

Thanks. As mentioned, deadtime can't be set for snmp-ups. You see this in the logs. Mar 31 09:08:30 freenas notifier: Fatal error: 'DEADTIME' is not a valid variable name for this driver. Mar 31 09:08:30 freenas notifier: Look in the man page or call this driver with -h for a list of valid variable names and flags. While looking at /var/log/messages I also see this when starting

it seems like I keep running into a wall. The present raid array...well let me do an fdisk -l: ---------------------------------------- Disk /dev/hda: 250.0 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 13 104391 fd Linux

(Keep the list CCed) 2014/1/4 Eirik Skorstad <eskorsta at hotmail.com>: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > >> Assuming shutdown.return works when issued via upscmd (does it >> work?), the problem seems to be that your UPS doesn't accept a >> shutdown.stop when there's no shutdown pending (or, maybe, the UPS >> doesn't