Hi, it'd be great if you could update the documentation on the website that some models of the Belkin -UNV series will only work with the megatec(_usb) drivers. I wasted a lot of time on trying to get it to work with the wrong drivers, and would like to spare others the pain :-). Thanks, ~David P.S. Some forum post said that the stable megatec drivers don't work 100% with the belkin UPS, but a note on that the stable site that belkin(unv) don't work would still be very useful!
David Mohr wrote:> > Hi, > it'd be great if you could update the documentation on the website > that some models of the Belkin -UNV series will only work with the > megatec(_usb) drivers.Which models, specifically? You mention the F6C1100-UNV in the subject line, but we previously had reports that that model was working with the usbhid-ups (formerly: newhidups) driver. We also have reports that the F6H500ukUNV, F6H650ukUNV, F6H350deUNV, F6H350ukUNV are working with the megatec driver; this information is already contained in the newest NUT sources (although perhaps not on the website). Belkin seems to change its protocol every few years. This latest shift is quite disturbing, considering that the older *UNV models actually implemented a standardized USB protocol, whereas the megatec_usb protocol is a hack.> I wasted a lot of time on trying to get it to > work with the wrong drivers, and would like to spare others the pain > :-).I agree. -- Peter
On Mon, May 21, 2007 at 03:25:42PM -0600, David Mohr wrote:> Hi, > it'd be great if you could update the documentation on the website > that some models of the Belkin -UNV series will only work with the > megatec(_usb) drivers. I wasted a lot of time on trying to get it to > work with the wrong drivers, and would like to spare others the pain > :-). >So, which UPSes are supported by megatec_usb driver? I have to know at least VID:PID pair and subdriver for each to add them to the list of supported devices (well, I suppose these would be the same as for F6C1200-UNV that is already in the list, so please, confirm that!). I've just updated data/driver.list in the SVN trunk with all UPSes considered supported (and F6C1100-UNV which appears in the subject too). At least, 'lsusb' would be useful. -- Alexander
On 5/21/07, David Mohr <damailings at mcbf.net> wrote:> Hi, > it'd be great if you could update the documentation on the website > that some models of the Belkin -UNV series will only work with the > megatec(_usb) drivers. I wasted a lot of time on trying to get it to > work with the wrong drivers, and would like to spare others the pain > :-). > > Thanks, > ~David > > P.S. Some forum post said that the stable megatec drivers don't work > 100% with the belkin UPS, but a note on that the stable site that > belkin(unv) don't work would still be very useful!I have a "F6C1100-UNV" running with the "belkinunv" driver. It has been running for over a year and that configuration, and has been quite stable. (nut-2.0.2 w/ serial connection) Dave
On Tue, May 22, 2007 at 07:35:27AM -0700, Big Wave Dave wrote:> I have a "F6C1100-UNV" running with the "belkinunv" driver. It has > been running for over a year and that configuration, and has been > quite stable. (nut-2.0.2 w/ serial connection) >Sorry, Peter, surely it was too early to claim this UPS supported by megatec_usb.. Dave, does this UPS have a USB interface? have you ever tried megatec_usb driver with this UPS? -- Alexander
On Tue, May 22, 2007 at 10:53:30AM -0300, Peter Selinger wrote:> Alexander and Eric, > > have you confirmed that the F6C1200-UNV works with the megatec_usb > driver? Looking back at the mailing list archive, I can't seem to find > the relevant message. What about Eric's F6C550-AVR? That should work > with the usbhid-ups/newhidups driver. >http://lists.alioth.debian.org/pipermail/nut-upsuser/2007-May/002668.html Some messages went off-list. At least these lines point directly to megatec protocol:> Asking for UPS power ratings ("F" command)... > UPS power ratings: #120.0 008 24.00 60.0-- Alexander
Sorry guys, my message (and various replies) went off-list by mistake. I am putting this back on the mailing list. Eric S. Raymond wrote:> > Peter Selinger <selinger at mathstat.dal.ca>: > > Alexander and Eric, > > > > have you confirmed that the F6C1200-UNV works with the megatec_usb > > driver? Looking back at the mailing list archive, I can't seem to find > > the relevant message. What about Eric's F6C550-AVR? That should work > > with the usbhid-ups/newhidups driver. > > My F6C1200-UNV definitely works with the megatec_usb driver, at least > when the driver is started by hand -- I see the Q1 command succeed > and I see status returns start to come back. > > I cannot yet start up the driver with upsdrvctl, I get the generic > startup-failure message. I have installed the udev rules and they do the > expected thing to device permissions -- I know this because I can start > the driver manually with no -u root option. So something else is going wrong. > > Is there some way for me to get more detail on the startup failure? > The existing message is remarkably unhelpful. > -- > <a href="http://www.catb.org/~esr/">Eric S. Raymond</a> >
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 autoOne 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: exitingThis 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