similar to: adding libusb CFLAGS to generic-hid.c rule

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

Hi All I'm trying to get my Ultra UPS connected. It connects using a standard USB cable I have --with-drivers=hidups in the configure command and I have lsusb showing Bus 001 Device 002: ID 0d9f:0001 Powercom Co., Ltd Bus 001 Device 001: ID 0000:0000 I have /dev/usb/hiddev0 now matter what I try I keep getting upsdrvctl start Network UPS Tools - UPS driver controller 2.0.3 Can't

* I committed into CVS the gendb patch that I sent to the mailing list on September 12. Arnaud, I hope you approve of this patch; it is more reliable than the previous method in tracking the correct dependencies. * This, together with some other minor recent changes on the Development branch, is between the "before_PSE_3" and "after_PSE_3" tags. Arnaud: if you

Dear Andreas, some googling revealed, you created a driver for the xanto series of online-usv.de. In what state it is currently? I've to manage a S2000 and would like to use nut for it, is it usable by now? Do you need another tester? TIA, Pete

make fails at drivers: make[1]: Entering directory `/export/home/zoly/Documents/trunk/drivers' /bin/sh ../libtool --tag=CC --mode=link gcc -I../include -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/hal -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/sfw/include -g -Dsolaris2 -I. -I/usr/sfw/include -O -Wall -Wsign-compare -o al175 al175.o ../common/libcommon.a ../common/upsconf.o

> > The Buildbot has detected a new failure of Ubuntu-maverick-x86 on > Network UPS Tools. > Full details are available at: > http://buildbot.networkupstools.org/public/nut/builders/Ubuntu-maverick-x86/builds/32 > > Buildbot URL: http://buildbot.networkupstools.org/public/nut/ > > Buildslave for this Build: cayenne Fred, I had a few spare cycles and tried building

Hi again, I've succeeded in compiling the svn trunk with the automake tools and wish to say thank you to Charles Lepple for his help. After fixing some parameters in the hotplug script I can now get access to the UPS on /dev/usb/hiddev0 (I added productid and vendorid of my ups to the usermap). I've decided to try the newhidups driver with -x generic parameter and got this response :

NUT developers, I'm looking for a low-tech solution for this linker error: > gcc -I../include -O -Wall -Wsign-compare -g -Dsolaris2 > -I/software/openssl-0.9.7_runtime/include -I. > -I/software/netsnmp-5.3/include -o snmp-ups snmp-ups.o main.o dstate.o \ > ../common/state.o ../common/upsconf.o ../common/parseconf.o \ > ../common/common.o ../common/setenv.o

Network UPS Tools version 2.4.3 has been released. http://www.networkupstools.org/ Note: this is only a bugfix release that only solves the regression on IPv6 activation. Direct access: - Download: http://www.networkupstools.org/source/2.4/nut-2.4.3.tar.gz - News: http://www.networkupstools.org/source/2.4/new-2.4.3.txt - ChangeLog: http://www.networkupstools.org/source/2.4/ChangeLog the NUT

I have been trying to get Nut working on a system with Fedora 8 i86_64 installed and an APC Smart-UPS USB. The 2.2.0 rpm does not seem to like the USB on this UPS. I have tried compiling the 2.2.2 version, from source, but am getting warnings. I have tried building it on my i386 system (f8 as well) and I get no warnings also the 2.2.0 works fine on that one with a TrippLite Omni 900 LCD via

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, I'm having a hard time configuring a Mustek Powermust 600VA ups to work via USB with nut. I read somewhere that nut works OK via the rs232 cable, but unfortunately I don't have a COM port in my computer. The kernel detects the ups as an Xbox pad :) and loads the xpad module. I tried running /lib/nut/megatec with different /dev/ttySx but it displays megatec protocol UPS was not

Hello, after upgrading to a newer distribution (FC8), I found that the driver hp.c (used to work fine for me with nut 2.0.0 on FC6) does not work anymore with 2.2.0. I want to modify it, as it is contains much of the new structure (>1.4.0) already. However, I cannot even get "make" to touch it. I have copied it into the drivers directory. Then I did ./configure make All drivers

Seems to be broken in the current SVN: [...] x86_64-linux-gnu-gcc -I../include -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/hal -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -DINET6 -O2 -D_REENTRANT -DNETSNMP_USE_INLINE -Wall -Dlinux -I. -I/usr/include -O2 -Wall -Wsign-compare -s -o energizerups energizerups.o ../common/upsconf.o ../common/parseconf.o ../common/state.o main.o dstate.o

Ok, I tried this from scratch on a fresh 2.7.2 directory. I followed the web instructions, specifically: + I generated the new subdriver for my UPS (rtd-hid.*) based on PATH info. + I put them in the drivers subdir + I added the include line (#include rtd-hid.h) in usbhid-ups.c (specifically in the #ifndef SHUT_MODE section) + I added &rtd_subdriver, to the subdriver_list in usbhid-ups.c

On Mar 2, 2015, at 12:49 PM, Rob Groner <rgroner at RTD.com> wrote: > Well, having spent a decent amount of time trying to get my driver file added into the Makefile build system (and failing), I've decided that for now, simply adding that one line to the openups-hid.c file and recompiling is the best route to go. When I can no longer live with the limited nature of the openups-hid

Well, having spent a decent amount of time trying to get my driver file added into the Makefile build system (and failing), I've decided that for now, simply adding that one line to the openups-hid.c file and recompiling is the best route to go. When I can no longer live with the limited nature of the openups-hid driver, I'll revisit writing our own. Thanks for the helps. Sincerely,

--- Arjen de Korte <nut+users at de-korte.org> wrote: > > > I also did: > > > > # ./megatec_usb -DDDDD -x vendor=06da -x mfr=OMRON > > /dev/usb/hiddev0 > > Please have a look at 'man 8 megatec_usb' again. > > You probably need to specify the '-x vendorid' and > '-x productid' options > and most likely, the

--- Arjen de Korte <nut+users at de-korte.org> wrote: > > > I also did: > > > > # ./megatec_usb -DDDDD -x vendor=06da -x mfr=OMRON > > /dev/usb/hiddev0 > > Please have a look at 'man 8 megatec_usb' again. > > You probably need to specify the '-x vendorid' and > '-x productid' options > and most likely, the

Hello, I have been trying to get a TrippLite Internet Office 750 UPS to talk to my Linux PBX for a couple of evenings now and I'm getting nowhere... I tried searching the list archives before posting here (I'm sure I'm not the first one to try to get this going) but they seem to be offline... The UPS is unfortunately USB based but I thought I'd give it a try anyway. Here is