[Nut-upsuser] Belkin F6C1100-UNV

[Peter Selinger]

Hi Eric,

this message fell off the mailing list (my fault), so I am putting
this reply back on the list.

Eric S. Raymond wrote:
> Here's my detailed trouble report on the Belkin F6C1200-UNV under Feisty Fawn.
> 
> root at snark:/home/esr/svn/nut/trunk/drivers# cat /etc/nut/ups.conf
> # Configuration file for NUT
> 
> [myups]
>         driver = megatec_usb
>         port = auto
> 
> Manual driver startup works *without* a "-u root" option
> 
> root at snark:/home/esr/svn/nut/trunk/drivers# ./megatec_usb -DDD -x vendorid=0665 -x subdriver=agiler auto

One potential problem is that you are passing the parameters
vendorid=0665 and subdriver=agiler when you start the driver manually,
but you are passing no such parameters to upsdrvctl. You can put them
into your ups.conf:

[myups]
        driver = megatec_usb
        port = auto
	vendorid = 0665
	subdriver = agiler

> Done setting up the UPS.
> Asking for UPS status ("Q1" command)...
> UPS doesn't return any information about its status.
> dstate_init: sock /var/state/ups/megatec_usb-auto open on fd 5
> Signal 2: exiting

This is another potential problem. Why did the driver exit here? Did
you press Ctrl-C, or did it fail by itself? 

> But upsdrvctl startup fails with a remarkably unhelpful message:
> 
> root at snark:/home/esr/svn/nut/trunk/drivers# upsdrvctl start myups
> Network UPS Tools - UPS driver controller 2.1.0
> Network UPS Tools 2.1.0 - Megatec protocol driver 1.5.3 [megatec_usb]
> Carlos Rodrigues (c) 2003-2007
> 
> Serial-over-USB transport layer for Megatec protocol driver [megatec_usb]
> 
> Driver failed to start (exit status=1)

Indeed, the message is not very helpful. The reason is that it doesn't
happen very often, so nobody has yet cared to improve the output.

You might get more information if you use -DD. At least you'll see
with what command upsdrvctl invokes the driver. For example:

# upsdrvctl -DD start myups
Network UPS Tools - UPS driver controller 2.1.0
Starting UPS: myups
exec: /usr/bin/megatec_usb -a myups
Network UPS Tools 2.1.0 - Megatec protocol driver 1.5.3 [megatec_usb]

The "exec" line will tell you exactly what upsdrvctl is calling. 
You should also try starting the driver manually, but using the config
file, e.g.:

megatec_usb -a myups

Finally, the last thing I can think of that you may check is that the
installed version of megatec_usb works (as opposed to the version in
your working directory). I.e., try if 

./megatec_usb -DDD -x vendorid=0665 -x subdriver=agiler auto

does the same thing as

/usr/bin/megatec_usb -DDD -x vendorid=0665 -x subdriver=agiler auto

If none of the above turn up any leads, then we'll have to dig
deeper. -- Peter