hi i bought a ultra ULT31502 ups someone seem able to run this ups with nut just see Dean thread on: tigerdirect.com/applications/searchtools/item-details.asp?EdpNo=770423&Tab=11&NoMapp=0 i use suse 10.1, i installed nut the ups is connected directely to my computer with an usb cable lsusb return Bus 001 Device 004: ID 0d9f:0001 Powercom Co., Ltd with lsmod, i can see usbhid 43296 0 /etc/ups/ups.conf i tried powercom and newhidups driver = newhidups port = /dev/hiddev0 desc = "Local UPS" /etc/ups/upsd.conf ACL all 0.0.0.0/0 ACL localhost 127.0.0.1/32 ACCEPT localhost REJECT all /etc/ups/upsmon.conf MONITOR myups@localhost 1 upsmaster okeefe master MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h now" NOTIFYCMD /usr/lib/powersave/powersave-notify POLLFREQ 5 POLLFREQALERT 5 DEADTIME 15 POWERDOWNFLAG /etc/killpower NOTIFYFLAG ONLINE SYSLOG NOTIFYFLAG COMMOK SYSLOG NOTIFYFLAG SHUTDOWN SYSLOG NOTIFYFLAG ONBATT SYSLOG+WALL+EXEC NOTIFYFLAG LOWBATT SYSLOG+WALL+EXEC NOTIFYFLAG FSD SYSLOG+WALL+EXEC NOTIFYFLAG NOCOMM SYSLOG+WALL+EXEC NOTIFYFLAG COMMBAD SYSLOG+WALL+EXEC RBWARNTIME 43200 NOCOMMWARNTIME 300 FINALDELAY 5 /etc/ups/upsd.users [upsmaster] password = okeefe allowfrom = localhost upsmon master [upsslave] password = okeefe allowfrom = localhost upsmon slave i tried: /usr/lib/ups/driver/powercom -DD -u root -x vendorid=0d9f /dev/hiddev0 and i get: Network UPS Tools - PowerCom and similars protocol UPS driver $ Revision: 0.5 $ (2.0.3) Fatal error: 'vendorid' is not a valid variable name for this driver. with /usr/lib/ups/driver/newhidups -DD -u root -x vendorid=0d9f /dev/hiddev0 Trying to match device Device does not match - skipping No appropriate HID device found No matching USB/HID UPS found if i start directely nut i get: for powercom and newhidups driver Starting NUT UPS drivers failed any idea? thanks
Dear Marc, first, the 'powercom' driver is a serial driver, so it will not work for USB. Second, newhidups does not currently support Powercom. The reason is simple: this is (as far as I remember) the first time we are seeing a Powercom USB device. It might not be too difficult to add support for it to NUT (or it might be very difficult - too early to know). To find out requires some effort on your part: * get the latest development version of NUT from SVN. You can follow the instructions at networkupstools.org/source.html under "Development tree" to get it. * send the output of drivers/newhidups -DD -u root -x generic -x vendorid=0d9f auto from this newest NUT version. This will help us determine whether your device is a HID device, and if yes, how to support it. Thanks, -- Peter Marc Collin wrote:> > hi > > i bought a ultra ULT31502 ups > > someone seem able to run this ups with nut > just see Dean thread on: > tigerdirect.com/applications/searchtools/item-details.asp?EdpNo=770423&Tab=11&NoMapp=0 > > i use suse 10.1, i installed nut > > the ups is connected directely to my computer with an usb cable > > lsusb return > Bus 001 Device 004: ID 0d9f:0001 Powercom Co., Ltd > > with lsmod, i can see > usbhid 43296 0 > > /etc/ups/ups.conf > i tried powercom and newhidups > > driver = newhidups > port = /dev/hiddev0 > desc = "Local UPS" > > > /etc/ups/upsd.conf > ACL all 0.0.0.0/0 > ACL localhost 127.0.0.1/32 > > ACCEPT localhost > REJECT all > > > > /etc/ups/upsmon.conf > MONITOR myups@localhost 1 upsmaster okeefe master > MINSUPPLIES 1 > SHUTDOWNCMD "/sbin/shutdown -h now" > NOTIFYCMD /usr/lib/powersave/powersave-notify > POLLFREQ 5 > POLLFREQALERT 5 > DEADTIME 15 > POWERDOWNFLAG /etc/killpower > NOTIFYFLAG ONLINE SYSLOG > NOTIFYFLAG COMMOK SYSLOG > NOTIFYFLAG SHUTDOWN SYSLOG > NOTIFYFLAG ONBATT SYSLOG+WALL+EXEC > NOTIFYFLAG LOWBATT SYSLOG+WALL+EXEC > NOTIFYFLAG FSD SYSLOG+WALL+EXEC > NOTIFYFLAG NOCOMM SYSLOG+WALL+EXEC > NOTIFYFLAG COMMBAD SYSLOG+WALL+EXEC > RBWARNTIME 43200 > NOCOMMWARNTIME 300 > FINALDELAY 5 > > > /etc/ups/upsd.users > [upsmaster] > password = okeefe > allowfrom = localhost > upsmon master > > [upsslave] > password = okeefe > allowfrom = localhost > upsmon slave > > > i tried: > /usr/lib/ups/driver/powercom -DD -u root -x vendorid=0d9f /dev/hiddev0 > and i get: > Network UPS Tools - PowerCom and similars protocol UPS driver $ Revision: 0.5 > $ (2.0.3) > > Fatal error: 'vendorid' is not a valid variable name for this driver. > > with > /usr/lib/ups/driver/newhidups -DD -u root -x vendorid=0d9f /dev/hiddev0 > Trying to match device > Device does not match - skipping > No appropriate HID device found > No matching USB/HID UPS found > > > if i start directely nut i get: for powercom and newhidups driver > Starting NUT UPS drivers failed > > any idea? > > thanks > > _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser@lists.alioth.debian.org > lists.alioth.debian.org/mailman/listinfo/nut-upsuser >
Marc Collin wrote:> > Le vendredi 25 ao=C3=BBt 2006 21:51, vous avez =C3=A9crit=C2=A0: > > Marc, > > > > interesting, actually, we have seen this device before; see the posts > > by Barry Fawthrop around August 1. It is a HID device, but it does not > > follow the USB HID standard for power devices. So decoding it might be > > tricky. > > > > I am attaching a patch that adds a rudimentary subdriver for this > > device. It should be sufficient to drop the "-x generic", attach the > > driver to the device, and observe some variables with upsc. > > > > Apply the patch to the SVN version (don't forget to re-run > > ./configure). See if the driver works, and try to run upsd and to read > > the values of the variables with upsc. If this works, please observe > > how the values of the variables change in response to events (loss of > > power, on battery, low battery, battery charging, battery full, etc). > > If successful, this will give clues as to how to interpret the > > different variables. The "low battery" condition is especially > > important, as it is used by upsmon. > > > > -- Peter > > hi > > ====== ups.conf =====> [myups] > driver = powercom > port = /dev/hiddev0 > desc = "Ultra ULT31502"As mentioned before, you should not use the "powercom" driver. It is for serial. You should use "newhidups". -- Peter P.S. please reply to the mailing list, not to me personally. Thanks!