Nut upsdev - Aug 2005 - Belkin F6C550-AVR UPS

Hi,
I got a Belkin F6C550-AVR UPS today and was trying to get it working
with NUT, I used the "hidups" driver and got some data out of it,
mainly the 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 showed the ups.status to be OB and
the battery charge started decreasing.

Is there any way I can get more data from the UPS? like the current
voltage, AVR status and such?

I have libusb installed, and I'm using a patched 2.6.11.3 kernel.
Thanks.

hidups will be abandonned, but according to the results you had,
there are good chances that your UPS will be supported by
newhidups...
>
> 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:
> ...
you miss the hotplug file installation and/or completion for
your units.

if you have installed the file from source:
1) copy nut/scripts/hotplug/{libhidups,libhid.usermap}
to /etc/hotplug/usb
2) then chmod a+x /etc/hotplug/usb/libhidups
3) Edit /etc/hotplug/usb/libhid.usermap and add the
following line (on one line!):
libhidups      0x0003      0x050d   0x0551    0x0000       0x0000       0x00    
0x00            0x00            0x00            0x00               0x00         
0x00000000

4) restart hotplug service (distro dependant) and
unplug/replug your UPS USB cord,
5) relaunch newhidups in debug mode (-DD)

Should tell more things.
Then post back the output, and ask for help to
create belkin-hid.h and to add it to newhidups.

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

> hidups will be abandonned, but according to the results you had,
> there are good chances that your UPS will be supported by
> newhidups...
>
> >
> > 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:
> > ...
>
> you miss the hotplug file installation and/or completion for
> your units.
>
> if you have installed the file from source:
> 1) copy nut/scripts/hotplug/{libhidups,libhid.usermap}
> to /etc/hotplug/usb
> 2) then chmod a+x /etc/hotplug/usb/libhidups
> 3) Edit /etc/hotplug/usb/libhid.usermap and add the
> following line (on one line!):
> libhidups      0x0003      0x050d   0x0551    0x0000       0x0000      
0x00         0x00            0x00            0x00            0x00              
0x00     $
>
> 4) restart hotplug service (distro dependant) and
> unplug/replug your UPS USB cord,
> 5) relaunch newhidups in debug mode (-DD)
>
> Should tell more things.
> Then post back the output, and ask for help to
> create belkin-hid.h and to add it to newhidups.
Hi Arnaud,
I have applied those changes, and here's a quick listing of them:

#cat /etc/hotplug/usb/libhid.usermap

libhidups      0x0003      0x050d   0x0551    0x0000       0x0000     
 0x00         0x00            0x00            0x00            0x00    
          0x00               0x00000000

#cat /etc/hotplug/usb/libhidups

if [ "$ACTION" = "add" -a "$TYPE" =
"usb" ]; then
  chown root:nut "$DEVICE"
  chmod 0660 "$DEVICE"
fi

The permissions on libhidups are set to 755.
The entry for my UPS in ups.conf is:

[belkin]
        driver = newhidups
        port = auto
        desc = "Belkin"

and the output from the newhidups driver is:
#newhidups -DD -a belkin
Network UPS Tools: New USB/HID UPS driver 0.23 (2.0.2)

debug level is '2'
Opening new device (0000/0000)
Opening new device (0000/0000)
Opening new device (05D8/4002)
Opening new device (050D/0551)
Opening new device (0000/0000)
Opening new device (0000/0000)
Opening new device (0000/0000)
found 0 (-1)
No USB/HID UPS found

The first device that it tried to open was my scanner, but the second
one is the Belkin UPS.

I guess the next step is adding the ID for this UPS to newhidups.h and
writing belkin-hid.h,
I think I know how to add the entry to newhidups.h but I'm not quiet
sure how to write belkin-hid.h so I'd appreciate any help with that.
 
Thanks,

Zaid

[@Zaid: susbcribe to upsdev ML, as upsuser isn't the
list for such tech topics...]
> ...
> No USB/HID UPS found
belkin wasn't recognised, though I thought I added it before.
It's now done in the Development CVS.

To get it:
cvs -d:pserver:anonymous@cvs.alioth.debian.org:/cvsroot/nut login
+ ENTER
cvs -z3 -d:pserver:anonymous@cvs.alioth.debian.org:/cvsroot/nut co -r
Development nut
> I guess the next step is adding the ID for this UPS to newhidups.h
done, this will allow you to see which data are supported (use
newhidups -DDDDD...). Then post back the output here
>  and writing belkin-hid.h,
> I think I know how to add the entry to newhidups.h but I'm not quiet
> sure how to write belkin-hid.h so I'd appreciate any help with that.
this is not so hard.
with the data list, check the existing mge-hid.h (the more complete ;-)
and try to find equivalence. You might also have to ask belkin
for some help to decode proprietary usage (if there are some).

also look at previous post for APC and others. I've already put
a lot of explanation (but still not written down an "how to extend
newhidups")

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