Re: [Nut-upsuser] libusb_get_interrupt: error reading from interrupt endpoint /dev/ugen0.1

2011-03-24 Thread John Bayly
On 24/03/2011 13:01, Charles Lepple wrote: How do things work if you add the pollonly option to the configuration file? I've just tried this, and the USB debug messages stopped on restart. Really appreciate the help. Be sure that the measured values shown in upsc are updating as well. With

Re: [Nut-upsuser] libusb_get_interrupt: error reading from interrupt endpoint /dev/ugen0.1

2011-03-24 Thread Arjen de Korte
Citeren John Bayly freebsd.po...@tipstrade.net: Thanks for pointing that out. Just did some timing and found that with and without the pollonly flag set, the ups.load value was changing when applying and removing additional load. I did however notice that the time taken to register the

[Nut-upsuser] libusb_get_interrupt: error reading from interrupt endpoint /dev/ugen0.1

2011-03-23 Thread John Bayly
Using an Eaton Evolution S 3000 (usbhid-ups) 2.6.0 on FreeBSD 7.3. After checking the debug log for an unrelated reason I saw that it was being swamped by the following message: Mar 23 15:50:57 rack usbhid-ups[65419]: libusb_get_interrupt: error reading from interrupt endpoint /dev/ugen0.1:

Re: [Nut-upsuser] libusb_get_interrupt: error reading from interrupt endpoint /dev/ugen0.1

2011-03-23 Thread Charles Lepple
On Mar 23, 2011, at 12:09 PM, John Bayly wrote: Using an Eaton Evolution S 3000 (usbhid-ups) 2.6.0 on FreeBSD 7.3. After checking the debug log for an unrelated reason I saw that it was being swamped by the following message: The USB stack in FreeBSD prior to 8.0 did not lend itself to