similar to: usbhid-ups bug

> Author: adkorte-guest > Date: Mon Feb 25 20:40:41 2008 > New Revision: 1334 > > Log: > Allocate twice the maximum number of reports we expect (MAX_REPORTS), to > allow for bogus/duplicate reports. Retrospectively, this is gross hack at best and probably only good to fix the problem temporarily. I think I have a better solution available (in a similar way as r1210, that was

I was doing some testing with the 2.6.0-1 beta Windows installer and a Cyber Power CP1350PFCLCD UPS, and ran into an infinite loop in the usbhid-ups driver if the UPS is lost on the UPS bus. This is on a Windows XP SP3 system. USB device access is via libusb 1.2.4.0 (driver mode, not filter) in case that matters. Everything seems to work just fine so far while the UPS is connected (so kudos,

I have a SmartUPS 750 (SUA750) which has the temperature and humidity SmartSlot card installed. When NUT 2.2 communicates with this UPS over /dev/ttyS0 using apcsmart, using the APC Smart cable connected to the SUA750 serial port, and this ups.conf: [su700] driver=apcsmart port = /dev/ttyS0 I can see the ambient temperature and humidity data with "upsc su700 at

On Jan 2, 2008 3:34 PM, Arjen de Korte <adkorte-guest at alioth.debian.org> wrote: > Author: adkorte-guest > Date: Wed Jan 2 20:34:26 2008 > New Revision: 1210 > > Log: > Parsing continues if the HID path for a report ends in 0x00000000 (these will not be made available). Commonly used as placeholders. > > It looks like (but correct me if I'm wrong) that reports

Hi Charles, Sorry for the long email, I feel this deserves a fuller explanation. On Wed, Feb 14, 2018 at 10:30:18PM -0500, Charles Lepple wrote: > On Feb 3, 2018, at 7:19 PM, Russell King wrote: > > > > Input and Output reports are used for interrupt endpoints rather than > > control endpoints. HIDGetItemData() only ever requests feature > > report IDs, and

On Feb 3, 2018, at 7:19 PM, Russell King wrote: > > Input and Output reports are used for interrupt endpoints rather than > control endpoints. HIDGetItemData() only ever requests feature > report IDs, and requesting non-feature report IDs as feature IDs may > lead to undesirable results and errors. This one made me scratch my head a bit. I don't think it's unreasonable

Hi, With recent revision, it's impossible to get upsdrvctl started: [root at teevee nut]# /usr/local/bin/upsdrvctl start Network UPS Tools - UPS driver controller 2.3.0-1352 Network UPS Tools: 0.29 USB communication driver - core 0.33 (2.3.0-1352) Warning: This is an experimental driver. Some features may not function correctly. Using subdriver: TrippLite HID 0.2 (experimental)

Hi, There is many (20 per day on average) messages like: kernel: usb 2-2: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 2 ret -110 usbhid-ups[6768]: HIDGetDataValue: Connection timed out What can be done do correct that problem? best regards, Franck my configuration: debian etch nut 2.2.1 (recompiled source from testing to use latest version before posting here) updated

I would also like to try and track down a possible off-by-10 bug in usbhid-ups (battery voltage on an MGE Pulsar Evolution, seen in the trunk in the last few weeks). If you are testing the shutdown stuff, it might be good to double-check the values you are seeing for voltages. I hadn't raised the issue on the list because I haven't had time to do the testing, but it's something to be

Hello, I would like to know if usbhid-ups is the right and best driver for these devices. I'm confused. The data list mentions only the "APC Back-UPS ES/CyberFort 350" as compatible and does not give more information about the full APC/MGE family devices. Also, I'm not sure that an APC Back-UPS ES 550VA or its equivalent 700VA is the same device as the described Back-UPS ES.

Hello I'm using nut 2.2.0 on FreeBSD 7.0-RC1. I've got two UPSes (Back-UPS RS 1500) connected to the host, and I often see them to go away. All the system logs are full of "Poll UPS [ups1 at upshost] failed - Data stale". What causes this issue? Is this a known issue, is it going to be fixed? What farther investigations should I do to get some more info on this issue? --

---------- Forwarded message ---------- From: davor emard <davoremard at gmail.com> Date: Tue, 25 Mar 2008 09:09:40 +0100 Subject: Cyberpower usbhid-ups wrong battery voltage To: libusb-devel at lists.sourceforge.net HI I have cyberpower value 800E connected via usb. In the status battery voltage is too high 20V - 21V while measurement at the battery terminals gives 13.6V -------------- next

OS: Linux (Linux ares 2.6.22-3-686 #1 SMP) Dist: Debian (testing) UPS: Tripp Lite Omni1000 LCD After updating from 2.2.0 to 2.2.1, the following command seems to go into loop and becomes unresponsive except for a "kill -9": /lib/nut/usbhid-ups -u root -DDD -a trippy It seem that the previous version would pause the output at some polling interval, but with the new version prints to

To people with APC, CyberPower, Belkin and TrippLite UPS'es and using the 'usbhid-ups' driver. There are some concerns that the usbhid-ups driver is not acting as it is supposed to do. Could you run the following command (as root and with the mains plugged) and check if the UPS powers back on automatically? upsmon -c fsd I think we should *not* release nut-2.2.1 if we're not

NUT 2.6.5-4 Eaton 3S550 Windows 7 Pro x64 usbhid-ups is crashing if it is started without debugging. This UPS worked fine on my test system with the same OS, but since moving it to the system where it will be used, it's refusing to function with NUT. Looks like it is working with the Windows built-in drivers though. Thanks. -------------- next part -------------- A non-text attachment was

I've just upgraded NUT from 2.0.2 to 2.2.0 and have read the upgrading file, which led me to submitting this message. I have changed nut.conf to use 'driver = usbhid-ups' and 'productid = ffff', but I still get 'No matching HID UPS found' when I try to start the driver. The UPS (a Liebert PowerSure Personal XT 450VA) was working fine with 2.0.2 and the hidups

Dear Rod, thanks for writing. Good work! I am no longer an active NUT developer, so I am forwarding your message to the NUT developers list. NUT developers: probably this device can be added permanently. Also, should the MAINTAINERS file perhaps be replaced by a pointer to the mailing lists? It seems fairly outdated anyway. Cheers, -- Peter R. W. Rodolico wrote: > > I think I have the

I want to revive an old discussion. Should we use the contents of input reports or not? A while back, we decided not to use the contents of input reports, because there is no guarantee that input report 'n' has the same meaning as feature report 'n'. We have not seen any cases so far where this is not the case, but as far as we could see, there is nothing in the HID PDC

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

Hello I'm new on this list, nice to meet you My configuration : OS : Ubuntu server 10.04.1 LTS NUT : nut 2.4.3-1ubuntu3.1 from Ubuntu package UPS : APC Back-UPS ES 530 My problem : When restarting twice nut in the same time. I can see 2 instance of /lib/nut/usbhid-ups driver when using : ps aux | grep usbhid-ups I know that's not normal to restart nut twice at the same moment but it