similar to: nut unable to communicate with new APC SMX100 over USB

OS name and version: FreeBSD 9.0-RELEASE amd64 exact NUT version: 2.6.1 NUT installation method: >From ports collection (cd /usr/ports/sysutils/nut; make install) Exact device name and related information: American Power Conversion/Back-UPS ES 525 FW:851.t2.I USB FW:t2 Complete problem description: /usr/local/etc/rc.d/nut start Network UPS Tools - UPS driver controller 2.6.1 Network UPS

Greetings everyone, Firstly, sorry for the huge length of this message. The support page said send debug traces, and so debug traces shall be sent. OS name and version - Arch Linux - updated today. exact NUT version - 2.7.4 (Network UPS Tools - Generic HID driver 0.41 (2.7.4) USB communication driver 0.33) NUT installation method - Arch User Repository build script updated to use latest NUT

Does the following error message have a specific meaning: usb 1-1: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 2 ret -75 I get two of these messages every time I run the following: /lib/nut/usbhid-ups -u root -DDD -a trippy The following is the output from the above command: debug level is '3' Checking device (0000/0000) (004/001) - VendorID: 0000 - ProductID:

I've just set up a CyberPower Value 2200E-GP on a system running Lucid AMD64, with the current NUT package via apt-get, and it seems to be working fine for me with the usbhid-ups driver, so I guess it can go in the HCL? I'm using the system to host several virtual servers under KVM, and to make things simple I set it up to hibernate rather than shutdown, that way all the guest OS

Hello all, About a month ago Peter and Charles were kind enough to try to help me with getting a Tripp Lite USB UPS to work with NUT. I reported quite a bit of initial success, and then other things here fell apart. Between work, fence building and a week-long out of town business trip, I have had to drop this from my list of things to do lately. I am back at it, and I believe I will have

I wrote a while back about the inability to kill the following command with anything but "kill -9" and the apparent high speed polling rate. # /lib/nut/usbhid-ups -u root -DDD -a trippy The setup I have worked on a previous version of nut, but I have forgotten at what point it stopped working. (I believe it was around Nov, 2007 that I noticed things were not working correctly.) I

Hello, I've recently bought Ippon Smart Winner 3000 New (note the "New" in the model name) and I can't make NUT to work with it. Linux gateway 3.17.8-gentoo-r1 #1 SMP Mon Feb 16 13:46:11 MSK 2015 x86_64 Intel(R) Celeron(R) CPU 1037U @ 1.80GHz GenuineIntel GNU/Linux Network UPS Tools 2.7.2 1) USB connection partially works using usbhid-ups driver, the problem is that I

Hello to All. OS : FreeBSD NAS 9.1-STABLE FreeBSD 9.1-STABLE [uname -a] Version : Network UPS Tools upsd 2.6.5 [upsd -V] Installation method : build into FreeNAS 9 UPS : APC Back-UPS 500 BK500EI USB Today i install FreeNAS and try to connect to it my UPS APC Back-UPS 500 BK500EI via USB with no luck;/ If anyone can try to help me I would be grateful. My configs nut.conf : MODE=standalone

I've acquired and installed NUT 2.4.1 on a D-Link DNS323 NAS. With exception of Load and Battery Temp readings all works well. A upsc ups at localhost command returns; battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 50 battery.date: 2001/09/25 battery.mfr.date: 2008/06/05 battery.runtime: 2122 battery.runtime.low: 120 battery.temperature: 3022999999999998800 battery.type:

> On Sep 11, 2016, at 3:37 PM, Jeff Bowman <jeff.bowman at intexx.com> wrote: > > > > Using subdriver: APC HID 0.95 > > > > ...and then hangs for 45 seconds before returning to a command prompt. No > UPS hardware information is printed. > > It can take about that long to read the descriptors. The non-Windows NUT > drivers will print that message,

Hi - I just installed NUT from source, using the usbhid-ups driver for a tripplite UPS (i compiled with the appropriate flag for the USB device). NUT version is 2.7.3. I UPS is AVR900U System is archlinux - fully up to date, running on an ARM device. Linux <Systemnameomitted > 3.1.10-35-ARCH #1 PREEMPT Fri Jan 23 19:14:18 MST 2015 armv5tel GNU/Linux I can communicate with my UPS - no

Hi, I'm trying to generate a skeleton driver with usbhid-ups and gen-usbhid-subdriver but the output seems to be incorrect. Same behavior with stable 2.6.5, so I guess there is something wrong with data coming out of device. I attached the output of usbhid-ups and gen-usbhid-subdriver from the commands: drivers/usbhid-ups -DD -u root -x explore -x vendorid=04d8 -a openups >&

I recently purchased a CyberPower CP1500PFCLCD UPS as a replacement UPS for a headless server running Slackware 14.1 with the 3.10.7 kernel. I then downloaded the NUT 2.7.1 tarball on the server and following the directions installed the software. The installation went well and the UPS will shutdown the server using the forced down test and then it powers back up as it should. The

On Mon, Jun 8, 2015 at 11:20 PM, Charles Lepple <clepple at gmail.com> wrote: > On Jun 8, 2015, at 8:23 PM, Greg Hersch <hersch.greg at gmail.com> wrote: > >> Hi Charles. I patched, reconfigured, remake'd, remake install'd - but >> no change. however, some more likely helpful information below for >> you. Thank you > > Odd. Are you sure that the

When running 'sudo upsmon -c fsd' UPS turns off then back on after a delay as expected. But when power is disconnected and the command is ran, the UPS turns off but still turns back on again. Changing 'ondelay' to -1 or 0 does not change the behavior. How can I get the UPS load to stay turned off if there is no power? Or am I misunderstanding how to test this functionality?

Thanks for your help. From: Charles Lepple <clepple at gmail.com> Date: Mon, 18 Dec 2017 19:26:56 -0500 This may sound like an apples-to-oranges comparison, but we did uncover an issue with CyberPower UPSes where the delay values needed to be greater than or equal to 60 (seconds), since they were being rounded down to integer numbers of minutes internally: What was the largest

Hi I would like to be able to use this UPS with NUT please ? Product id = 53962KX Network UPS Tools - Generic HID driver 0.38 (2.7.2) USB communication driver 0.32 0.000000 debug level is '2' 0.002761 upsdrv_initups... 0.014996 Checking device (03F0/0024) (001/005) 0.032670 - VendorID: 03f0 0.032790 - ProductID: 0024 0.032955 - Manufacturer:

I have a Tripp-Lite BCPERS450, connected to a system running Ubuntu 16.04.3 LTS and NUT 2.7.2-4ubuntu1.2. I had to make my own /lib/systemd/system-shutdown/nutshutdown, but now everything is working except for powering on and off the UPS. Regardless of the settings of offdelay and ondelay in upsconf, and regardless of whether the AC power is on, when I say "upsdrvctl shutdown" the UPS

Hello, I am hoping someone can point me in the right direction. I am setting up a new UPS, most things seem to be working except the UPS turns off immediately during a test shutdown using///"//upsmon -c fsd".//No delay before the UPS turns itself off leaving no time for the server to shutdown properly. I have attempted to set the delay higher using "upsrw -s

Thanks again for your patience. I'm still learning how to deal with systemctl myself (and starting from, I'm sure, a much lower level of understanding), so if I've neglected to restart or start something, please let me know. I made the change to /etc/nut/upsd.conf. I restarted upsdrvctl, which reported back: Network UPS Tools - UPS driver controller 2.7.4 Network UPS Tools - Generic