similar to: [Bug 278495] Re: megatec_usb does'nt detect ups

2008/10/27 Artin <admin at artinws.com>: > Arnaud > > I have already posted the debug output of 2.2.1 : > http://launchpadlibrarian.net/18231851/debug2.txt uh, right. I was off doing another update for Lenny... looking a bit at the trunk's changelog, I would guess this is a regression. not dug much for the time being, adding the below line in ups.conf (in the [ups] section)

Hello, I'm working on getting nut using a Powermust Office 650 USB USV. Using today's trunk megatec_usb detects its vendorid 0665 productid 5161 but uses the agiler driver for it which apparently does not work (timeout...). I think this device is using that USB-to-serial chip but a different protocol behind. I got the phoenix subdriver working with the device but I had to extend

Hi! I've (finally) decided to try and make my PowerWalker work with megatec_usb. So far it seems the agiler subdriver is the way to go, but it doesn't work. The initial detection process sometimes succeeds in 1 out of 5 "Q1" commands, but that's about it (which is better than what the krauler subdriver can do... absolutely nothing). So, what needs to be done to obtain more

Looking for ioctl() calls in the drivers, I noticed that the energizerups.c code looks a lot like a megatec protocol over a USB connection. It uses 8 bytes per packet, which makes it look like the agiler subdriver in megatec_usb. Do we know if there are people that use this driver now and that might be able to verify this? Best regards, Arjen -- Eindhoven - The Netherlands Key fingerprint - 66

I recently took over maintenance of a linux computer which is drawing power from a "Maruson Power Net 1500" UPS. However, there is currently no monitoring or control of the UPS by this (or any other) computer. Can nut control this device? There are serial, usb, and EPO connectors on the back of the unit. (There may be a manual but I'm going to have to hunt for it.) Thanks, David

Hello everyone, has anyone ever tried to make this device work with Linux and NUT? This is what udevadm monitor says: UEVENT[1215983089.652345] add /devices/pci0000:00/0000:00:0f.2/usb1/1-1 (usb) UEVENT[1215983089.652427] add /class/usb_endpoint/usbdev1.4_ep00 (usb_endpoint) UEVENT[1215983089.657975] add /devices/pci0000:00/0000:00:0f.2/usb1/1-1/1-1:1.0 (usb) UDEV

I have an UPS, that claims to be IPPon Back Power Pro 700. I'm trying to connect it using USB. lsusb -v says: Bus 1 Device 3: ID 06da:0003 Phoenixtec Power Co., Ltd Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0

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,

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,

> Author: agordeev-guest > Date: Wed Oct 3 00:09:21 2007 > New Revision: 1136 > > Log: > - drivers/megatec_usb.c: added ability to do subdriver-specific > initialization, and moved some shared code to agiler init function > since krauler doesn't need it. [...] I'm not very thrilled about this patch: 1) Down at the subdriver level, one shouldn't use

Folks, I think the present megatec_usb.c deserves to be renamed to serial_usb.c. I think it potentially could serve many more UPS'es with built-in USB-to-serial converters, not limited to the megatec_usb driver (although that was the first one to use this). I also think a more layered approach would be nice, in the same fashion as the usbhid-ups driver with subdrivers. Which would mean that

Hi, I'm new in the list and I'm having a little bit trouble to put the megatec_usb to work. I've been using NUT for a while with the apc and megatec driver (serial), with no problem. The server is a Ubuntu 8.04.2 with NUT version 2.2.1-2.1ubuntu7.2, the default package version in this ubuntu release. I've configured the ups.conf as follows: [sms] driver = megatec_usb

Hi, I'm new in the list and I'm having a little bit trouble to put the megatec_usb to work. I've been using NUT for a while with the apc and megatec driver (serial), with no problem. The server is a Ubuntu 8.04.2 with NUT version 2.2.1-2.1ubuntu7.2, the default package version in this ubuntu release. I've configured the ups.conf as follows: [sms] driver = megatec_usb

# /lib/nut/megatec_usb -a myups Network UPS Tools 2.2.0- - Megatec protocol driver 1.5.4 [megatec_usb] Carlos Rodrigues (c) 2003-2007 Serial-over-USB transport layer for Megatec protocol driver [megatec_usb] No supported devices found. Please check your device availability with 'lsusb' and make sure you have an up-to-date version of NUT. If this does not help, try running the driver with

Hi Bj?rn, 2009/10/9 Bj?rn Torkelsson > Public bug reported: > > Binary package hint: nut > > I have recently upgraded from hardy to intrepid to jaunty. After > upgrading to Intrepid the megatec_usb stopped recognizing my Trust PW- > 4130M ups, it still does not work on Jaunty. It worked without any > problems in hardy. > > I tried the megatec_usb driver from hardy

A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 188 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20071124/3ceb35d2/attachment.pgp

Hi everybody, In a christmas sequel I've been offered one of the units mentioned above. I've tried to connect it to my Fedora 8 workstation but rapidly concluded it's not yet supported by NUT. So far, I've decompiled the Java classes of the manufacturer's application and noticed that it's most probably yet another kind of serial protocol through the USB. Since

Belkin F6C1200-UNV on Ubuntu 7.04, megatec_usb driver, Every few minutes I get a beep and a "UPS not available" message that seems to be bogus; upsc reports real data, not at complaint that it's stale. Is there some timeout I need to lengthen? Also, shouldn't upsc report the poll time associated with the data it displays? -- >>esr>>

I just bought a pair of Belkin USB UPSes -- F6C1200-UNV and F6C550-AVR -- and installed the latest version of nut under Ubuntu 7.04. I'm using the F6C1200-UNV. My system does see the device; dmesg says [ 82.718428] usb 2-2: new low speed USB device using ohci_hcd and address 2 [ 82.941189] usb 2-2: configuration #1 chosen from 1 choice [ 83.036825] usbcore: registered new driver

I just bought a pair of Belkin USB UPSes -- F6C1200-UNV and F6C550-AVR -- and installed the latest version of nut under Ubuntu 7.04. I'm using the F6C1200-UNV. My system does see the device; dmesg says [ 82.718428] usb 2-2: new low speed USB device using ohci_hcd and address 2 [ 82.941189] usb 2-2: configuration #1 chosen from 1 choice [ 83.036825] usbcore: registered new driver