similar to: APC Smart-UPS 1000 RM USB problems with newhidups

Does anyone on this list have a CyberFort 350? It's a European model, and should be equivalent to the US BackUPS ES 350 model. What I'm seeing is upsd reporting stale data. While the battery is running down, upsc doesn't see the battery % changing, so I'm assuming the driver isn't collecting data at that point. Unfortunately, the system/UPS is not here (I'm in the

Hi there, I'm one of the maintainers of the SME Server distro (www.contribs.org) and we've been chasing this one for some time: http://www.contribs.org/bugzilla/show_bug.cgi?id=352 http://lists.alioth.debian.org/pipermail/nut-upsdev/2006-January/000543.html Many thanks to Peter Selinger and everyone else who helped with the debugging and patches. Thanks, Gordon

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

Hi. Could anyone please provide info on how nut makes ups restart after power is back? I've configured nut to communicate with APC SmartUPS 750 via 'newhidups' driver and this works w/o probs in case of shutting the system down. The UPS would stay on though. After the power returns, I'd expect UPS to restart so that servers would start either. This would never happen, and I have to

Paolo, Try sudo /lib/nut/newhidups -DDD -u root -a SmartUps1500 newhidups would only run on my computer if I ran it using sudo and as root user. I know this indicates a problem with the USB permissions, but I could not, for the life of me, get the permissions to change when I plugged the UPS in. I know this isn't a true fix, but it worked for me. -- ~Brian Foster

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

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:

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

Greetings: I've been following through the instructions on how to connect an APC BackUPS 650 ES to USB, and have it monitored with NUT... I know my system can SEE the UPS, as DMESG shows this: hiddev96: USB HID v1.10 Device [APC Back-UPS ES 650 FW:818.w1.D USB FW:w1] on usb-0000:00:04.2-1 usbcore: registered new driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver I can see

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

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

Hi all, I have an APC/Smart-UPS 3000 RM that I am trying to connect to nut via the usb port. I have nut running just fine on several other machines using APC ups's via the serial ports but this usb thing is making me crazy. If I do a "/sbin/newhidups -u root -D -a PS1" it recgonizes the ups and dumps a bunch of information like below: (porky pts12) # /sbin/newhidups -u root -D -D

Hello, I'm currently try to get newhidups running with the newhidups driver from nut 2.0.2. After some USB issues (usb_claim_interface() works only as root so far) newhidups is recognizing the device. Though it doesn't detect any state changes, meaning when I run the battery test mode it's not recognized. I wanted to try the CVS version but it seems anonymous CVS is broken. The

'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

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

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

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

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!

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 >

Hi there, I'm trying to track down a problem with said combination. Broadcast message from nut (Thu Jan 26 13:22:06 2006): Communications with UPS UPS@localhost lost Broadcast message from nut (Thu Jan 26 13:22:11 2006): UPS UPS@localhost is unavailable "newhidups -DDD hiddev0" seems happy enough, as does "upsd -DDD -f" - at least until I start upsmon. Then I