[Nut-upsuser] Re: problem with USB conection

[arnaud.quette at mgeups.com]

> I am installing NUT for the UPS Skate UPS-2200D, the UPS have conection with USB to PC and i have problems to configure  nut
> the ups is conected and Linux report this config
> Aug 19 23:34:56 dakota kernel: [22393.099595] usb 2-2: new low speed USB device using uhci_hcd and address 7
> Aug 19 23:35:06 dakota kernel: [22403.186326] usb 2-2: Product: MEC0002
> Aug 19 23:35:06 dakota kernel: [22403.186333] usb 2-2: Manufacturer: MEC
> Aug 19 23:35:06 dakota kernel: [22403.291219] hiddev96: USB HID v1.00 Device [MEC MEC0002] on usb-0000:00:1d.0-2
> I assume the /dev/usb/hiddev96 for the UPS, is ok?
> i am configured the NUT with this mini How-TO
> http://fedoranews.org/contributors/kazutoshi_morioka/nut/
> but i have two problems
> into /etc/sysconfig/ups

> # UPS device - needed if UPS is locally attached
> DEVICE= -> whta is the correct config?

"auto" should be fine. In fact, this part is redundant with
the ups.conf file. Will be addressed with the NUT Packaging
Standard effort.

IIRC, the sysconfig file was present the allow a central
settings, but putting "upsdrvctl" as the driver and leaving
the rest alone, having the ups/*.conf files configured
should work too.

> into /etc/ups/ups.conf [myups]
> driver = newhidups
> port = auto is correct auto or /dev/usb/hiddev96  ???

"auto" is fine too. Contrarily to hidups, newhidups use
libusb (not linux hid/hiddev specific stack) and has the
hability to auto detect the first local UPS.

But it also need to know how to translate (look up)
between the UPS internal HID data and the NUT
formalism. Have a look at the various mail about
newhidups and other manufacturers, mostly on
the upsdev list archives to see how to get the
supported data and how to create a lookup table
for your UPS.

Arnaud Quette
---
Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt
OpenSource Developer - http://arnaud.quette.free.fr/
Debian Developer - http://people.debian.org/~aquette/
 ... and much more ...