similar to: newhidups / Solaris 10 / APC RM1500

Folks, while I've got the above combination to compile and run under Solaris 10, it seems that there are still problems in the libusb/ugen driver stack from Sun and or the APC Smart UPS 1500, so things aren't actually working. It seems that the APC Smart UPS 1500RM doesn't return the HID descriptor length information in 0x21 as noted in a previous thread, but in my case, it also

I'm trying to get nut to work with a Cyberpower 900AVR. There are many different products known by this name, but this one has the extra name 'BC900D'. I am told by a cyberpower tech that this one should talk exactly the same USB protocol as the 685AVR, which was recently made to work with newhidups. Unfortunately, when I run the SVN checkout (trunk) of nut-2.1, I get: sstreet

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

While trying to compile newhidups, I get this error... carlos@rhea:~/dev/nut/svn/trunk$ make usb make[1]: Entering directory `/home/carlos/dev/nut/svn/trunk/drivers' gcc -I../include -O -Wall -Wsign-compare -c newhidups.c In file included from newhidups.c:25: libhid.h:46: error: syntax error before "u_int16_t" libhid.h:46: warning: useless keyword or type name in empty declaration

[I'm switching my dev address to @gmail.com instead of @mgeups... please, update your bookmark] Peter Selinger wrote: > > Arnaud Quette wrote: > > > > Here is the status of PSE (Peter Selinger) NUT patches > > for newhidups (hidparser, apc support, ...). > > > > - nut-cvs-patch-REOPEN-2005-08-24: > > approved and applied on Development tree > >

I've been using nut with a serial device for a while, but today I tried hooking up this new CyberPower 685 unit via newhidups--since it seemed better supported over USB than serial, based on reading the list archives and cvs logs. Unfortunately, I can't connect to it. My system sees the device: uhid1: CPS UPS BF700, rev 1.10/0.01, addr 2, iclass 3/0 ... and I have chmodded all

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

Something strange happens when I compile the pre27 SSH: ocal/ssh//include -DETCDIR=\"/usr/local/ssh//etc\" \ -DSSH_PROGRAM=\"/usr/local/ssh//bin/ssh\" \ -DSSH_ASKPASS_DEFAULT=\"/usr/local/ssh//libexec/ssh/ssh-askpass\" \ -DHAVE_CONFIG_H -c atomicio.c In file included from includes.h:106, from atomicio.c:26: fake-socket.h:30: parse error before

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

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

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 message repeated 2 times

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

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

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)

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

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

2006/1/13, Paul Mogren <fkamogee@yahoo.com>: > > This thread is FYI. I don't need any help here. > no, but some details for those who will read it, maybe ;-) I have SUSE 10.0 and an MGE Ellipse. I installed the NUT package from MGE. > > 1) The generated ups.conf pointed to a bad location: > /dev//dev/input/event0 > who generated that ? it seems like an old hiddev

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

Hi Scott, Scott Alfter wrote: > I had a UPS go bad recently (shuts off all by itself for no good reason, >AFAICT), so I bought a CyberPower 685AVR this afternoon. The two CyberPower >drivers in NUT 2.0.2 don't know how to talk to it, but the hidups driver >appears to work properly. This means you have to use USB instead of RS-232 (it >supports both), but at least it works. >