similar to: Newpoint 200897 UPS

Hello everyone! If this message was posted twice, my apologies. I'm having issues with my webmail today... I am using the testing version of NUT from SVN at changeset 582. I have successfully created a stub for newhidups driver for my Dynex DX-800U UPS, but I am completely lost on the customization of it. I've followed the hid-subdrivers.txt instructions and I understand I need to

Gentlemen, I just had time to start looking at the latest version of the development tree. I have built the apc-hid part of newhidups from the development tree and I am in the process of testing it with my "Back-UPS ES 650". As of right now I have incorporated the attached changes to apc-hid.c. I have been using the corresponding changes together with some changes from Arnaud with the

Gentlemen, I have now had a chance to run some initial tests of my changes to apc-hid.c of the current development tree. Running newhipups and inspecting the -DDDD output seems to indicate that with the fix below everything seems to work as expected. However, I have not yet shut my system in order to take the UPS out of action so that I can do my various tests with a lightbulb load. I still hope

I just purchased a Newpoint 200894 UPS and I'm interested in getting it going. It seems to use a USB to serial conversion that I'm not sure how to get running. Here's the lsusb -vvv Bus 002 Device 005: ID 0665:5161 Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level)

Gentlemen, I have determined that on my UPS (APC Back-UPS ES 650 FW:818.w1.D USB FW:w1), the variable UPS.PowerSummary.RemainingCapacityLimit is writeable. I am setting this variable to start shutdown a little earlier. Appended is an unconditional patch for apc-hid.h. If, as indicated by the original code, there are APC UPS devices that don't allow setting of this variable, it becomes

Peter, Looking through the usbhid-ups subdrivers, I came across the following function in apc-hid.c, presumably added by you about two years ago (if not, my apologies): 41 /* returns statically allocated string - must not use it again before 42 done with result! */ 43 static char *watts_to_av_conversion_fun(long value) { 44 static char buf[20]; 45 46 snprintf(buf,

Gentlemen, Please note that what follows pre-dates the latest changes from Arnaud (just thought someone might want to look at these before I can test the latest!). When running newhidups with -D -D -D I saw messages that looked like errors, and it took me a while to understand that they were not really errors. I therefore added two new entries in apc-hid.h, and I modified a couple of diagnistic

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()

It's been a while since I tried to use NUT, so I thought I would give it another try. Big trouble. The UPS is a Tripp-Lite AVR 550U. It has only a USB connector. The computer is running Red Hat Enterprise Linux 4. I just installed NUT version 2.2.0. I'm going through the steps in the INSTALL document. # cat ups.conf [igor] driver = usbhid-ups port = auto