similar to: Too much logging from libusb.c (patch supplied)

Sorry about the noise guys. Below a significantly improved patch. The main difference is that all calls to usb_get_string_.. have been wrapped in a new function nut_usb_get_string()  that is implemented in libusb.c This was necessary in order to make the bufflen_fix available in libusb.c where usb_get_string() is called in libusb_open() This wrapper function mops up and hides all the work

I get the following error on r809 (but it looks like the code change happened here). Does HIDDevice_t need to be defined/changed in one of the headers? if gcc -DHAVE_CONFIG_H -I. -I../../drivers -I../include -I../../include -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/hal -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -DINET6 -O2 -D_REENTRANT -DNETSNMP_USE_INLINE -Wall -Dlinux -I.

Hi all, My name is Sergio Penen and I'd like to contribute to the project by developing a new driver for TS SHARA SOHO II usb ups. I'm almost done decoding the protocol and already have some basic functionality working with NUT. However I've some doubts on how to integrate this driver with NUT and I wonder if you could give me some guidance in that sense. To be more specific: In order

I think having this logic buried within libhid/libusb (libusb:libusb_open(), line 179 to 206) is ultimately a mistake, albeit one that I am probably responsible for. Would it make sense to confine libhid to low-level operations, and leave the decision of trying to reopen vs. retrying to open to the high-level driver, in this case usbhid-ups? I envision that the code in usbhid-ups:reconnect_ups()

Peter, I have been doing some more testing and I find that if I modify the libusb.c file to set a report size in libusb_get_report to 16 the error messages go away. This is the code as it currently stands: static int libusb_get_report(usb_dev_handle *udev, int ReportId, unsigned char *raw_buf, int ReportSize ) { int ReportSize_test = 16; unsigned char raw_buf_test[ReportSize_test +

On Dec 11, 2014, at 5:43 AM, janc at telefonica.net wrote: > 0.339329 Entering libusb_get_report > 0.342986 Report[get]: (2 bytes) => 01 00 > 0.343085 Path: 008c0001.008c0003, Type: Feature, ReportID: 0x01, Offset: 0, Size: 8, Value: 0 > 0.343120 Entering libusb_get_report > 0.346953 Report[get]: (2 bytes) => 02 00 > 0.346993 Path: 008c0001.008c0002,

Hi! Charles. This is the output with 'explore' # ./usbhid-ups -DDDD -u root -x explore -x vendorid=06da -a CENER_LA900_usb Network UPS Tools - Generic HID driver 0.37 (2.6.4) USB communication driver 0.32 0.000000 debug level is '4' 0.000676 upsdrv_initups... 0.288980 Checking device (06DA/0002) (008/004) 0.316956 - VendorID: 06da 0.317057 - ProductID: 0002

On Mar 28, 2014, at 1:52 AM, Bill S wrote: > I just noticed what I think is another incorrectly reported value. I > found that on the second screen of upsstats.cgi, the one with bar > graphs, that the reported battery voltage is 16.0V even though the > battery charge is at 100% and the UPS is on AC power. I would have > thought it should be more than 25V. I'll be honest, I

On 3/2/17 10:02 AM, Charles Lepple wrote: > Can you provide a pointer to details on the usbhid-dump tool? Not > familiar with that one. I'm using Ubuntu 14.04 Server on an i686 Dell/Wyse CX0 thin-client - usbhid-dump was available as part of usbhid-utils, if I am not mistaken. https://github.com/DIGImend/usbhid-dump > Depending on how much of the Power Device Class (PDC) HID

On Fri, Mar 28, 2014 at 8:12 AM, Charles Lepple <clepple at gmail.com> wrote: <<Snip>> > > I'll be honest, I haven't really done much with the CGI scripts lately. For debugging values, it is probably better to be closer to the driver. I'd recommend using "upsc" or the driver logs. > > To that end, the .ac.txt and .bat.txt files both show 24.0 V:

Hi all ! I have a little problem using NUT from FreeNAS. Operating system FreeBSD 8.3-RELEASE-p4 (FreeNAS 8.3.0 BETA 2) UPS American Power Conversion/Back-UPS CS 650 FW:817.v7 .I USB FW:v7 NUT Driver Network UPS Tools - Generic HID driver 0.37 (2.6.5) USB communication driver 0.31 Trying to configure the UPS from FreeNAS failed so I try to investigate which is the problem. Running

Hi, I'm running the latest stable nut (2.4.3). It doesn't appear to provide support for the Tripp Lite SmartOnline SU1000XLA. [sups] driver = usbhid-ups port = auto vendorid = 09ae productid = 4004 4337# upsdrvctl start Network UPS Tools - UPS driver controller 2.4.3 Network UPS Tools - Generic HID driver 0.34 (2.4.3) USB communication driver 0.31 Using subdriver:

Hello, I have been trying to get a TrippLite Internet Office 750 UPS to talk to my Linux PBX for a couple of evenings now and I'm getting nowhere... I tried searching the list archives before posting here (I'm sure I'm not the first one to try to get this going) but they seem to be offline... The UPS is unfortunately USB based but I thought I'd give it a try anyway. Here is

Hello, I have found that I need to be able to control a TrippLite SMART2200RMXL2U ups, with an external battery. I found recently after trying to communicate that many of the bits I would care about (the output ports/loads) wheren't exposed in the current driver. I also happen to have the Web/SNMP card, which allows me to change many of the settings via ssh/http interfaces. I'm

On Mar 28, 2014, at 9:08 AM, Bill S wrote: > On Fri, Mar 28, 2014 at 8:12 AM, Charles Lepple <clepple at gmail.com> wrote: > > <<Snip>> >> >> I'll be honest, I haven't really done much with the CGI scripts lately. For debugging values, it is probably better to be closer to the driver. I'd recommend using "upsc" or the driver logs.

I doesn't fix any problems but I think it is nicer code. :-) I don't think we want to call usb_detach_kernel_driver_np unless we claimed the device. $ diff -uw libusb.c.bak libusb.c.new --- libusb.c.bak 2010-05-11 09:35:39.000000000 -0400 +++ libusb.c.new 2010-05-11 09:32:44.000000000 -0400 @@ -206,18 +206,21 @@ upsdebugx(2, "failed to

Have recently purchased a MGE Nova 1100 UPS and am trying to get running on netBSD. Configuration netBSD 3.0 amd64 libusb 0.1.10a nut 2.0.3 Built & installed libusb Built kernel with ugen device and uhid removed Build & install nut-2.0.3 with usb Chmod /dev/ugen1 etc to allow access by nut user. Ups.conf [MGENova] driver = newhidups port = auto

I was getting: "Can't claim USB device [0764:0501]: could not detach kernel driver from interface 0: Operation not permitted" so I manually installed the udev rules the source (I installed the Gentoo ebuild). I am now getting: # upsdrvctl start Network UPS Tools - UPS driver controller 2.4.3 Network UPS Tools - Generic HID driver 0.34 (2.4.3) USB communication driver 0.31 Using

I'm trying to set up nut-2.6 with a SMX1000 ups unit from APC on a CentOS 4.8 server. It's connected via USB, and Linux has detected it as a HID device. Nut was built from source code. T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 21 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=051d ProdID=0003 Rev= 1.06 S: Manufacturer=American Power

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: