similar to: CyberPower CP1200AVR/BC1200D problems

On Aug 8, 2014, at 9:15 AM, Charles Lepple <clepple at gmail.com> wrote: > On Aug 7, 2014, at 10:52 PM, Charles Lepple <clepple at gmail.com> wrote: > >> On Aug 7, 2014, at 10:18 PM, Matthew Stapleton <matthew4196 at gmail.com> wrote: >> >>> I just got a Cyberpower SOHO Value 1200 ELCD UPS and even with nut 2.7.2, it appears to report battery voltage

On Aug 7, 2014, at 10:52 PM, Charles Lepple <clepple at gmail.com> wrote: > On Aug 7, 2014, at 10:18 PM, Matthew Stapleton <matthew4196 at gmail.com> wrote: > >> I just got a Cyberpower SOHO Value 1200 ELCD UPS and even with nut 2.7.2, it appears to report battery voltage too low due to the battery scaling function (In drivers/cps-hid.c). Even though the ups has usb id:

Attached is the first 32 seconds of the driver output after applying the patch which fixes the battery scaling problem for this UPS. Matthew Stapleton Email: matthew4196 at gmail.com On 10/08/14 01:27, Charles Lepple wrote: > On Aug 8, 2014, at 9:15 AM, Charles Lepple <clepple at gmail.com> wrote: > >> On Aug 7, 2014, at 10:52 PM, Charles Lepple <clepple at gmail.com>

I have a ups that doesn't always (sometimes it does) load NUT right. I use Gentoo: * sys-power/nut Latest version available: 2.6.0-r1 Latest version installed: 2.6.0-r1 Size of files: 1,663 kB Homepage: http://www.networkupstools.org/ Description: Network-UPS Tools License: GPL-2 The kernel is 3.0.4. Here is the dmesg output:

I took the modifications from doug reynolds, ported them to 2.0.4, and tried to make it more generic such that it would work for all old devices as well as the new CP1200AVR. I don't necessarily like the implementation because I don't like global vars, but it was what I could come up with without knowing the architecture better. Hopefully this will get included into the next version

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

Hi, I keep getting the following messages (or similar) in my syslog: Nov 23 11:38:08 io kernel: [763936.921566] usb 3-2: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 5 ret -110 Nov 23 11:38:08 io kernel: [763936.972569] usb 3-2: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 5 ret -75 Nov 23 11:38:08 io kernel: [763936.976568] usb 3-2: usbfs: USBDEVFS_CONTROL

Hello, I have a Salicru UPS in a Debian Wheezy connected with a USB HUB: # lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ... Bus 001 Device 003: ID 1a40:0201 Terminus Technology Inc. FE 2.1 7-port Hub Bus 001 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial The problem is that I have some failed messages: # dmesg ... [90941.136274] usb 1-3.7: usbfs:

On Mar 7, 2014, at 4:12 PM, Josu Lazkano <josu.lazkano at gmail.com> wrote: > Are the messages a problem? Or could I ignore? Since they aren't happening on each poll interval, they are not a big problem. The driver should recognize -110 as a timeout, and retry the query.

I have nut 2.6.4-2.3+deb7u1 on debian 7 32bit, with UPS Eaton Nova AVR 1250 connected via USB. It happens several times a day that I get a message about Apr 3 16:41:49 kernel: [422581.049671] usb 5-1: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 4 ret -110 Apr 3 16:41:54 kernel: [422586.041057] usb 5-1: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 3 ret

Hello, I'm a new to NUT and I'm having some setup problems. Here's my setup: Nut 2.0.2 Gentoo Linux 2.6.13-r3 CyberPower AVR900 According to the hardware compatibility guide this setup should work. Here's what I get: root@gentoo (0) [552] % upsdrvctl start Network UPS Tools - UPS driver controller 2.0.2 Network UPS Tools - CyberPower driver 1.00 (2.0.2)

The UPS is connected to the following environment: OS: Debian GNU/Linux 9.6 (stretch) NUT version: 2.7.4-5 Device output from lsusb: 0463:ffff MGE UPS Systems UPS Model name: MGE EllipseMAX 1500 URLs: http://powerquality.eaton.com/Products-services/Backup-Power-UPS/Ellipse-MAX-eol.aspx?cx=97&GUID=7BB6CD53-9F6D-4D62-B326-1099F137BF8D http://powerquality.eaton.com/68558.aspx?cx=97 The problem

On Apr 3, 2014, at 3:40 PM, Adam Pribyl wrote: > I have nut 2.6.4-2.3+deb7u1 on debian 7 32bit, with UPS Eaton Nova AVR 1250 connected via USB. Which kernel version? > It happens several times a day that I get a message about > > Apr 3 16:41:49 kernel: [422581.049671] usb 5-1: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 4 ret -110 > Apr 3 16:41:54 kernel:

> If there is no message to NUT, I would consider opening a trouble > ticket with Eaton. It is possible that there is a known issue and/or > a firmware upgrade. What kind of message to NUT? In the log (syslog) there is no other message registered. In nut.log only this appears: > Dec 1 08:10:54 openmediavault upsd[5284]: Data for UPS [ellipsemax] > is stale - check driver >

Hello, I encounter a problem using the UPS MGE Evolution 850 VA USB with Debian Etch and the nut package available for this version. I got this error: ==syslog== Can't connect to UPS [MGE850VA] (usbhid-ups-auto): No such file or directory upsd[2767]: Startup successful upsmon[2769]: Startup successful upsd[2767]: Connection from 127.0.0.1 upsd[2767]: Client MGE at 127.0.0.1 logged

Hi there First a big thank you to all nut developers. I tried the 2.0.4 as well as the 2.0.5-pre1 versions with my CyberPower OP1000E connected to a serial to USB converter. All I got was the following: # /usr/local/ups/bin/upsdrvctl start Network UPS Tools - UPS driver controller 2.0.5-pre1 Network UPS Tools - CyberPower text protocol UPS driver .05 (2.0.5-pre1) Warning: This is an

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

Hello, I'm using NUT to manage a MGE Ellipse ASR UPS, with the newhidups driver. It works fine, except that after a few hours, I get a few errors from the kernel and the driver dies. Here's the output from the syslog: Apr 26 02:00:41 ezquiel kernel: usb 1-1: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt 128 rq 6 len 255 ret -110 Apr 26 02:00:43 ezquiel last message repeated 2 times

Folks, I have been working on a problem with the usbhid-ups driver and the MGE / Eaton Ellipse series UPS. There seems to be light at the end of the tunnel. For whatever reason, these devices seem to trigger error 'EPIPE' randomly. So far, the response to this of the usbhid-ups (and previously, newhidups) driver is to reconnect. Most of the time this will succeed on the first

Dear List, I thought it might be useful if I wrote up my notes on getting an MGE UPS to work with NUT and openSUSE. The MGE UPS (an Ellipse 1500 USB) will work well with NUT and openSUSE 10.2, but not "out-of-the-box": there are some things you need to do: Intro. MGE have built rpms of NUT which greatly simplify installation. Merci MGE. I used the rpm's for nut-2.0.5 and the