similar to: Problems with APC Smart-UPS 1500 USB and, newhidups driver

Whenever I try to use the newhidups driver with my new UPS I get the following message: #/lib/nut/newhidups -DDD -a SmartUps1500 Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4) debug level is '3' [...skip unrelevant device...] Checking device (051D/0002) (001/005) - VendorID: 051d - ProductID: 0002 - Manufacturer: American Power Conversion - Product: Smart-UPS 1500 FW:601.3.I USB

Great! Please let the mailing list know if you run into any further problems. -- Peter Paolo Pedroni wrote: > > Alle 16:38, venerd=EC 25 agosto 2006, hai scritto: > > Paolo, > > > > I recently fixed some bugs regarding the report descriptor retrieval. > > Please try it with the newest development version from SVN. You can > > follow the instructions at >

2007/3/14, R.J. Baart <R.J.Baart@prompt.nl>: > Hello, I know you are the nut guru: you helped me before with a > udev problem. That's why I write you again. > > I use the debian package of nut. With some googling I found out > that I am not the only one with this problem. However, does the > latest release of nut solves my problem? I try to figure out, but it > was

Hello, I'm using the stable amd64 port of Debian Linux. I installed (the latest) nut-2.0.1-4 and nut-usb packages for utilizing an APC Smart-UPS 1500 USB. I tried "apcupsd" first but "nut" makes an even more sophisticated impression on me and has more security options. I had problems with the newhidups driver. It didn't find a device with matching VendorID. And

Well, after our first real extended power outage, I found out that even though the UPS 1000 RM is recognized okay, it does not work properly. It never seems to see any change in UPS status. It looks very similar to the other issue I reported with the APC CyberFort 350. I never was able to get to the bottom of the CyberFort issue, but I'll bet it's the same issue as we have with the

I'm trying to use a rackmount Smart-UPS from APC with the USB connector, and I'm running into some issues. They seem to stem from the fact that the Report Descriptor is much larger than any other UPS I've seen (61939 bytes). Here is the quick fix that I put in libusb.c after getting the HID descriptor, and before getting the Report descriptor, which seems to work okay:

Hi. I had a problem recently with %subj, and I've solved it. Sent a letter with solution to maintainers, but it seems like I've lost it somewhere. May be just simply forgot to write it.. But anyway. I've noticed that I'm not the only one who had it. So I post the workaround. The problem is similar to the one mentioned in letter with alike subject at Oct. 5. When the UPS

Hello, I encountered a problem with my APC Smart-UPS 750, connected via USB, using newhidups. Without any reason, nut/upsmon shut down my PC: >>> Oct 13 12:57:08 echo kernel: usb 2-9.1.1: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt 161 rq 1 len 8 ret -71 Oct 13 12:57:12 echo upsmon[5060]: UPS smart750@localhost on battery Oct 13 12:57:12 echo upsmon[5060]: UPS smart750@localhost

Peter, if you're back, I was wondering if you might have a chance to look into the issues I reported last month. I'm back to using hidups right now, but I would prefer to use a current, maintained driver. Thanks!

I tested your fix (newhidups -DDD /dev/null) using both and APC Back-UPS 350 an APC Smart-UPS RT 2000 XL. No more segmentation fault due to the fixed-size array. ~Jacob -----Original Message----- From: nut-upsdev-bounces@lists.alioth.debian.org [mailto:nut-upsdev-bounces@lists.alioth.debian.org] On Behalf Of Peter Selinger Sent: Monday, October 16, 2006 12:12 PM To: Schmier, Jacob Cc: NUT

Hello world; been using nut atop Debian GNU/Linux (sid) for about two years by now, my configuration broke as I upgraded the machine this morning (headin' for kernel 2.6 to have full support for the new GBE NIC included). I read through the UPGRADE.gz instructions provided with the Debian packages and tried to fix things according to the instructions pointed out there, but things still just

I was testing out newhidups with an APC UPS, and I noticed that I needed '-x vendor=American.Power.*' instead of '-x vendor=APC.*' as indicated in the man page. Do other APC USB UPSes use 'APC' in the vendor string? Should we sidestep any such problems and just go with the hex vendor ID for APC examples? This was tested with a snapshot from the development branch, but the

Hi, Can't get newhidups (2.0.5) or usbhid-ups (SVN trunk) to work 2.0.5 hidups seems to work, but I was hoping for more information... like temperature, etc. Tried newhidups and usbhid-ups, but they don't seem to detect my UPS... should I switch back to serial? Will I get more information? (trying not to move back to apcupsd, since i have a mixed environment) Here is some debug

Thought I would write some notes about how I got an APC BackUPS XS 1500 working with newhidups under Gentoo 2006.0. The specific issue here is the permissions on the device files used that libusb uses to access the USB hardware. I followed Peter Selinger's instructions at http://www.mscs.dal.ca/~selinger/ups/backups.html on getting newhidups going with an APC device. The sticking point for

'lo, UPS model: APC Back-UPS BR 800 (supplied by Dell) My USB connection: Bus 001 Device 002: ID 051d:0002 American Power Conversion Back-UPS Pro 500/1000/1500 # upsc desk@localhost|grep load ups.load: 0.0 This UPS has 2 pc's and some minor other gear connected, yet the load stays at 0.0 when checking with nut. driver.version: 2.0.5 driver.version.data: APC/CyberPower HID 0.9

The C backend can currently (recent head) produce code with such patterns: /* Global Declarations */ /* Structure forward decls */ struct l_structtype_s; /* Typedefs */ typedef struct l_structtype_s l_fixarray_array3[3]; /* problematic declaration */ typedef struct l_structtype_s l_structtype_s; /* Structure contents */ struct l_structtype_s { int field0; }; gcc 4.0.1 will reject this with

I just installed NUT and my UPS is an APC Back-UPS ES 500. I looked in the list of drivers and found APC Back-UPS ES 350 listed in "drivers.txt" -- that list said I should use either the newhidups or hidups driver. I looked in the installation and I found headers and c files to create these drivers (I think), but in /usr/local/ups/bin there is no driver named, "newhidups or

Has anyone gotten the newhidups driver to work w/ the Powerware 9120 series? Here's what I get for debug info (It's the Phoenixtec device): $ sudo lsusb Bus 002 Device 002: ID 0846:1040 NetGear, Inc. Bus 002 Device 001: ID 0000:0000 Bus 001 Device 002: ID 06da:0002 Phoenixtec Power Co., Ltd Bus 001 Device 001: ID 0000:0000 $sudo /lib/nut/newhidups -DDDDD auto Network UPS Tools: New

Hi there, been using NUT for ages and recently upgraded to a new server; while I'm waiting for a USB->Serial adapter for Solaris to arrive, I thought I'd play with the newhidups, as the APC UPS I have has a USB port and the new server doesn't have a serial port.... I've got Solaris 10 & newhidups working with the ugen driver up to a point, and that is a read

I'm using an APC Back-UPS XS with nut 2.0.3. I've recompiled/reinstalled the source, and switched over to the newhidups driver (instead of the old hidups driver). I modified by ups.conf to use newhidups. The hotplug files were not automatically installed, I had to copy those from the scripts directory to my hotplug/usb directory. The newhidups driver loads find and then works for a