similar to: Using an APC UPS through USB on SuSE 9.2

Hello! I installed NUT with "apt-get install nut" (v2.0.2-1). I hooked the new APC Back-UPS XS BX1500 unit to the Debian (Kernel 2.6.12-1-K7) computer with the provided USB cable (has an ethernet jack on the end connected to UPS) and ran dmesg command: usb 1-2: new low speed USB device using uhci_hcd and address 2 usb 1-2: device descriptor read/64, error -110 usbcore: registered new

Hello everybody, I got tree UPS devices connected to a Debian server, and i am searching for a way to configure them. The server power-cord is only connected to one of the ups devices, and should monitor the other ups systems to sent email status. I got a HP R3000XR UPS with has a RS232 communication port that I have working perfectly. Then I have two APC SmartUPS 750V devices that are

Greetings: I've been following through the instructions on how to connect an APC BackUPS 650 ES to USB, and have it monitored with NUT... I know my system can SEE the UPS, as DMESG shows this: hiddev96: USB HID v1.10 Device [APC Back-UPS ES 650 FW:818.w1.D USB FW:w1] on usb-0000:00:04.2-1 usbcore: registered new driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver I can see

I have a new APC Back-UPS XS 1200. It is detected properly by the Linux kernel (2.6.16): # dmesg usb 5-3.4: new low speed USB device using ehci_hcd and address 9 usb 5-3.4: new device found, idVendor=051d, idProduct=0002 usb 5-3.4: new device strings: Mfr=3, Product=1, SerialNumber=2 usb 5-3.4: Product: Back-UPS XS 1200 FW:8.g1 .D USB FW:g1 usb 5-3.4: Manufacturer: American Power Conversion usb

Maybe a kernel USB issue, but people on this list may have encountered this issue. I am testing a new UPS (EATON 5E 1500iUSB) and am having a problem with the USB connection failing. My old UPS (EATON Ellipse MAX 1500) works just fine with the latest f30. Both devices identify as ID 0463:ffff MGE UPS Systems UPS To narrow the focus I booted recent live CDs on a PC that has no other USB devices

I need direction. I don't know what to google for anymore. I am unable to get my SmartUPS 2200XL to be recognized. My suspicions are that it's UDEV or Kernel related. I've updated the kernel to the highest version I feel comfortable with due to other things that run on the server, and I've updated UDEV a bit too. When I plug in the USB cable from the UPS into the server, I

Charles, > What is the new behavior? The CentOS minimal install had different print statements and a broadcast message whenever the UPS was disconnected. The broadcast isn't really important. Below are the differences I pasted though I'm not sure if they are important, I just noticed they were different. Particularly the bolded parts which I think you alluded to in your email about

I have installed nut 2.0 Var/log/messages: Aug 14 16:37:26 server kernel: hiddev96: USB HID v1.10 Device [American Power Conversion Back-UPS BF500 FW:814.s3.I USB FW:s3] on usb-0000:00:1d.0-1 Aug 14 16:37:26 server kernel: hub 5-0:1.0: USB hub found Aug 14 16:37:26 server kernel: hub 5-0:1.0: 2 ports detected My ups.conf : [APC350] driver = apcsmart port = /dev/usb/hidddev96 desc =

Hey, was wondering if I could get a quick sanity check. We have a SmartUPS 1500 RM2U which we have connected to a box via USB. It seems like every 40-45 seconds it becomes disconnected and reconnected. Though this only happens when we have NUT enabled, otherwise it's fine. When it is disconnecting and reconnecting running lsusb doesn't show it disconnecting. After having it sit like that

On up-to-date f36, with latest kernel 6.1.7-100.fc36.x86_64. After receiving a few of these messages Broadcast message from nut at e7.eyal.emu.id.au (somewhere) UPS ups at ups is unavailable I noticed and ran sudo systemctl restart nut-driver at ups.service which triggered Broadcast message from nut at e7.eyal.emu.id.au (somewhere) Communications with UPS ups at ups established I now added

Some of my messages never went through since I hit a message size limit. I'm resending them in the hopes they are under the limit. Charles, The lsusb command did not trigger a disconnect. The output of that command is below. I ran "usbhid-ups -a upsunit -DDD &> output.log" and I have attached the /var/log/messages and output.log to this email. Before running this test

i can't seem to get newhidups to detect my UPS.. i'm using nut-2.0.3 (tried both the rpm from fc5-updates and compiling my own) here is the entry for the UPS in /proc/bus/usb/devices T: Bus=04 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0764 ProdID=0501 Rev= 0.01 S: Manufacturer=CPS S: Product=UPS

Hi, I'm running Fedora Core 6 and need to monitor a Tripp Lite SMART2200RMXL2U. I've loaded the nut-2.0.3-2.1 RPM. The UPS is connected via the provided USB cable, and that much appears to work: # dmesg | grep -i tripp hiddev96: USB HID v1.10 Device [Tripp Lite TRIPP LITE SMART2200RMXL2U ] on usb-0000:00:1f.4-2 # lspci | grep -i usb 00:1f.4 USB Controller: Intel Corporation 82801BA/BAM

I am experiencing the same kind of disconnects, stale data on Eaton brand UPS (Nova AVR). It keeps doing it probably due to Windows to detect it as a new hardware, until Eaton software is installed. With Eaton Linux IPP http://pqsoftware.eaton.com/explore/eng/ipp/default.htm?lang=en this does not happen. Think what? It disables it somehow. But as soon as you remove this proprietary driver, its

I'm trying to get nut to work with a Cyberpower 900AVR. There are many different products known by this name, but this one has the extra name 'BC900D'. I am told by a cyberpower tech that this one should talk exactly the same USB protocol as the 685AVR, which was recently made to work with newhidups. Unfortunately, when I run the SVN checkout (trunk) of nut-2.1, I get: sstreet

Charles, So I installed a minimal CentOS 6.5 installation on the Fedora box this morning and I got the same issue. Below are the kernel versions used. CentOS 6.5 Minimal - [root at nemo tmp]# uname -a Linux nemo 2.6.32-431.el6.x86_64 #1 SMP Fri Nov 22 03:15:09 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux [root at nemo tmp]# rpm -qa | grep nut nut-2.6.5-2.el6.x86_64 nut-client-2.6.5-2.el6.x86_64

Hi Recently i bought a MicroDoWell BP50, and with it followed a USB 2 serial converter. When i plug it into my 2.6.19 kernel, dmesg shows hiddev96: USB HID v1.10 Device [Cyber Power System CPS RS232 USB BRIDGE for UPS] on usb-0000:00:04.2-2 usbcore: registered new interface driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver So, i figured i should use usbhid-ups,

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

So I just bought one of these fabulous CyberPower UPS devices from BestBuy hoping I could control it with my machine. Luckily, I found NUT! I've got the SVN sources and compiled and installed them but I haven't been able to get it to recognize the usb AE550. When I plug the usb cable in I see this in syslog: Feb 6 22:36:56 mythbox kernel: usb 1-1: new low speed USB device using

Hi there, this is more a comment and a solution rather than a question, but I thought I'd post it since it cost some time to dig down to the issue and maybe someone else could run into this. I'm using the nnet function for a regression task. I'm inputting the following data frame: > 'data.frame': 4970 obs. of 11 variables: $ EC25 : num 67.5 67.6 68 69 69.5 ... $