search for: newhidups

I just noticed the following curious behavior when using newhidups with upsdrvctl and two different USB devices: My ups.conf contains two devices, both using newhidups: [belkinusb] driver = newhidups port = auto desc = "Belkin UPS, USB interface" vendorid=050d [mgeusb] driver = newhidups port = auto...

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 hidups" -- what have I messed up? thanks for your help!!! steve

...ottom of the CyberFort issue, but I'll bet it's the same issue as we have with the APC 1000 RM. Here's what I have done so far: * Machine is a AMD Athlon, running current Debian stable, 2.4.27 stock Debian kernel * Machine has been verified working with a few APC BackUPS models with newhidups 1) Tested by unplugging the power, right after a fresh boot. -- Newhidups didn't see any change at all 2) Restarted the driver without rebooting. -- Still said the UPS was online 3) Stopped the driver, un/replugged the USB cable, restarted driver. -- Newhidups saw that it was OB 4)...

I Seem to have made some progress in getting nut-2.0.5 installed, but hidups still has a version number of 0.13. First is hidups 0.13 the correct version? if not how do I find the correct version. Second if my Geek Squad GS1285U UPS is not supported how do I proceed. I have been a programmer for 35 years(mostly high level computer aided design), written code in 20 some languages, am retired

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 overrun while probing the UPS itself. It seems this has been spotted before and there was a post...

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 poin...

Peter, attached is a proposed patch to fix compilation of generic-hid.c when libusb's usb.h is not in /usr/include (but the -I flag is provided by "libusb-config --cflags"). It fixes the build under OS X, where Fink installs libusb with --prefix=/sw. I changed "usb.h" to <usb.h> so that 'make depend' wouldn't generate a dependency on 'usb.h' with

...999 usb 5-3.4: configuration #1 chosen from 1 choice hiddev96: USB HID v1.10 Device [American Power Conversion Back-UPS XS 1200 FW:8.g1 .D USB FW:g1 ] on usb-0000:00:1d.7-3.4 This UPS works properly with apcupsd, but I'd rather use NUT. :-) Here's my ups.conf: [xs1200] driver = newhidups port = auto user = upsd desc = "Back-UPS XS 1200" I receive this error when I run newhidups manually: # /usr/lib/ups/driver/newhidups xs1200 Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.3) No matching USB/HID UPS found Forcing it to use the "root&quo...

...e following: battery.charge: 100 battery.runtime: 120 driver.name: hidups driver.parameter.port: /dev/usb/hiddev0 driver.version: 2.0.0 ups.mfr: Unknown ups.model: Unknown ups.serial: Unknown ups.status: OL the versions of NUT that I tried were 2.0.0, 2.0.1-rc4 and 2.0.2, I tried using the "newhidups" driver but it didn't detect the UPS, so I tried with "hidups" which gave me that output. When doing "lsusb" I get: Bus 003 Device 002: ID 050d:0551 Belkin Components and when I tried to put the UPS in OB mode it worked fine and when I checked its status using upsc it...

...e following: battery.charge: 100 battery.runtime: 120 driver.name: hidups driver.parameter.port: /dev/usb/hiddev0 driver.version: 2.0.0 ups.mfr: Unknown ups.model: Unknown ups.serial: Unknown ups.status: OL the versions of NUT that I tried were 2.0.0, 2.0.1-rc4 and 2.0.2, I tried using the "newhidups" driver but it didn't detect the UPS, so I tried with "hidups" which gave me that output. When doing "lsusb" I get: Bus 003 Device 002: ID 050d:0551 Belkin Components and when I tried to put the UPS in OB mode it worked fine and when I checked its status using upsc it...

2005/9/25, Peter Selinger <selinger@mathstat.dal.ca>: > > Arnaud Quette wrote: > > > > Some more points while you're at it: > > - newhidups will have to be renamed. My aimed was to let the name until > we > > can superceed hidups. Then remove hidups, and rename newhidups to > usbhid-ups > > (name proposition welcomed, but should match the fact that it's for > USB/HID > > compliant devices, not USB only)....

I ran into the following issue today and would like some feedback from the group. Setup: I am using a MGE Pulsar Evolution 2200 UPS connected through a Belkin (F5U218-MOB) 4-Port USB Hub. Scenario: The newhidups subdriver_matcher function calls belkin_subdriver->belkin_claim. The belkin_claim function in belkin-hid.c matches the VendorID of the hub to Belkin's VendorID (0x050d), causing the hub to be recognized as a UPS. The newhidups driver (libusb.c) then attempts to claim the device and detatches...

Hello, I'm facing problems as I'm installing NUT to monitor a MGE Ellipse ASR600USBS on a FreeBSD 6.1 box. UPS is recognized as : ugen0: MGE UPS SYSTEMS ELLIPSE, rev 1.10/42.41, addr 2 I'm temporarily using root profile (devfs/devd scripts not modified atm). newhidups starts & runs fine (unplugging mains makes newhidups outputs lots of data when started with -DDDD flags) When I launch upsd, it barfs vith : emss@box:~> /usr/local/sbin/upsd -u root Password: Network UPS Tools upsd 2.0.4 Connected to UPS [mge]: newhidups-auto Synchronizing........ giving u...

Hi, I'm running nut 2.0.3 on Gentoo connected to an MGE ProtectionCenter 675. newhidups intermittently crashes. Any ideas? N. # /usr/lib/nut/newhidups -a mgeups Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.3) Detected a UPS: MGE UPS SYSTEMS/PROTECTIONCENTER Using subdriver: MGE HID 0.8 This is the error I'm getting *** glibc detected *** /usr/lib/nut/newhidups: double...

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 moment to a few minutes. I...

There is a memory leak in newhidups. After 23 days uptime it used 138M memory. Apart from the memory leak, the system works ok. Is there anything I can do to help fix this problem? Tor. [root@tophat init.d]# ps -unut v PID TTY STAT TIME MAJFL TRS DRS RSS %MEM COMMAND 21122 ? Ss 1:35 0 69 137934 1...

...mit that past days im having the syslog with a lil more activity from the new usb attached unit (ellipse ASR 1000 VA) Network UPS Tools: New USB/HID UPS driver 0.23 (2.0.2-pre2) Detected an UPS: MGE UPS SYSTEMS/ELLIPSE usb 3-1: control timeout on ep0in usb 3-1: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt 161 rq 1 len 10 ret -110 usb 3-1: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt 161 rq 1 len 10 ret -32 usb 3-1: usbfs: process 3225 (newhidups) did not claim interface 0 before use usb 3-1: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt 161 rq 1 len 10 ret -32 usb 3-1: usbfs: process 3225...

Hello, I am having trouble getting upsd to start. I am using the Debian NUT packages version 2.0.3 (current in Debian/sid). I am using the newhidups driver with an APC Back-UPS BR 800. The init.d script wasn't functioning, so I backtracked to running upsd manually and I get: foxstar:/etc/nut# upsd -u root Network UPS Tools upsd 2.0.3 Can't connect to UPS [foxstarups] (newhidups-auto): No such file or directory Synchronizing..... <C...

Mr. Selinger, I'm CCing you directly since it appears (insofar as I can tell) that you are one of the delelopers for the newhidups driver. This is the third time I've submitted this (hence the CC this time). Hopefully mailman takes it. I've tweaked my SPF records, and I'm hoping that was the problem. My sincere apologies if this has gone through and I just haven't seen it (could someone mail me if they are...

Hello, I'm using NUT to manage a MGE Ellipse ASR UPS, with the newhidups driver. It works fine, except that after a few hours, I get a few errors from the kernel and the driver dies. Here's the output from the syslog: Apr 26 02:00:41 ezquiel kernel: usb 1-1: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt 128 rq 6 len 255 ret -110 Apr 26 02:00:43 ezquiel last mess...