similar to: Format of entires in data/driver.list

Citeren Charles Lepple <clepple at gmail.com>: >> Another thing, loosely related to this, is how we are going to deal with the >> 'generic' VID:PID combinations in some of the USB drivers, for example the >> megatec_usb and (new) blazer_usb drivers. At present, in the megatec_usb >> driver we have several VID:PID combinations for USB-to-serial converters

Mr. Selinger, I'm CCing you directly since it appears (insofar as I can tell) that you are one of the delelopers for the newhidups driver. This is the third time I've submitted this (hence the CC this time). Hopefully mailman takes it. I've tweaked my SPF records, and I'm hoping that was the problem. My sincere apologies if this has gone through and I just haven't seen it

Peter, Apparently, some Belkin UPSes still have problems with this. When we receive this report through the interrupt pipeline it is ignored (the special case in usbhid-ups.c) and even after that it looks like there are still some problems with it: http://lists.alioth.debian.org/pipermail/nut-upsuser/2007-July/003014.html Wouldn't it be an option to just to ignore this completely and

Citeren Alexander Gordeev <lasaine op lvk.cs.msu.su>: > I've received the units. Are there any special things I should test or > just the standard NUT setup? They should be detected out of the box (with the latest version from the trunk) through the 'usbhid-ups' driver. Note that I just added some additional commands to enable|disable|mute the beeper of the UPS.

Arjen de Korte wrote: > Author: adkorte-guest > Date: Mon Jun 18 09:03:18 2007 > New Revision: 964 > > Log: > additional debug info in case commands fail > > Modified: > trunk/ChangeLog > trunk/drivers/megatec.c > > Modified: trunk/ChangeLog Arnaud, Carlos, I'd like to backport this change to Testing as well. Intermittent startup problems for

Dear Sirs, First of all I would like to thank you for support PCM product in your project. Kindly please be informed that POWERCOM launch new USB-controller with productID 0X04. Updated USB-controller compatible with previous version which supported by your usbhid-ups driver. There is added some command and changed idProduct. Vendor ID stay the same 0X0d9f without changes. Detailed information

Until the release of nut-2.0.5 it was possible to have a working configuration without configuring anything in 'ups.conf'. Since then, this no longer works, as the server will only look for driver sockets for UPSes that have been configured in 'ups.conf' (since the socket is named after the UPSname). Drivers will use the old naming scheme '<driver>-<port>' if

Dear Sirs, We appreciate your support and cooperation. Can you please kindly add our new USB-controller with productID 0X04 to NUT compatible list. Updated USB-controller compatible with previous version which is supported by your usbhid-ups driver. Detailed information regarding new POWERCOM communication protocol you could download via link

Hi there I have a Mustek PowerMust 1000 USB using serial port /dev/ttyS0. I use nut 2.2.1 with the megatec driver on Debian Lenny (testing), running on an AMD64 X2. (I was using a Debian Etch as slave, but to keep it simple I turned it off) My problem is that sometimes the UPS is running OK, but when the message "UPS is trimming incoming voltage" appears on knutclient (i.e. OL TRIM in

Greetings all; I pulled a Belkin F6C100-4 into the shop this afternoon, deader than a door nail. Out of service for about a year because (I'm assuming here) that the cooling fan stopped and cooked what little remaining life there may have been out of the batteries, which had swelled so badly I had to split its frame to get them out. They are also in the under 1 volt per 12 volt pack

Hi Folks, I just bought two APC UPSes, an EX 1300 and an ES 550 for two different sites and installed NUT for the first time on two machines (one Centos 4.1, the other Ubuntu 7.04). So far I'm well impressed -- excellent work by the dev team! The EX 1300 is working beautifully with NUT on the Centos box, but I'm having a bit of a problem with the ES 550: even while loaded, the ups.load

Are there any plans for using serial PnP in NUT? I tried to implement this on the 'safenet' driver, but the support for this doesn't seem to be widespread among the UPSes compatible with this driver. So far, I have only managed to get one (a Sweex 1000) to output it, but unfortunately, it is probably too generic to be really useful for autodetection: PnP revision : 1.00 PnP EISA ID

My UPS Powercom WOW-1000U does greatly work with NUT, but not auto-cofigurable... This UPS is not usb-hid ups, and works well with this settings in NUT: [powercom] desc = "powercom" driver = powercom port = "/dev/serial/by-id/usb-POWERCOM_CO.__LTD._USB_to_Serial-if00-port0" type = IMP lsusb -v fragment attached. Unlike other UPSes, gnome-power-manager does

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

Hi everybody, we have three MGE UPS'. I've read all the documents I've found, but I haven't got the information I need. All three of them being attached to the same machine I need a way to identify which is wich (all three use the same driver). They power different systems (two of them running windows so that I can't easily setup a network-enabled software on two of them, as

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,

On Mon, Oct 20, 2008 at 1:35 PM, Arjen de Korte <nut+devel at de-korte.org> wrote: > Citeren Carlos Rodrigues <cefrodrigues at gmail.com>: > >> BTW, the patch has a small typo in one of the comments: "applied to >> battery.volage" :) > > I'll leave that up to you to correct. Since it is only a comment, it won't > be visible to innocent users

On Wed, Dec 3, 2008 at 4:05 PM, Arjen de Korte <nut+devel at de-korte.org> wrote: > Citeren Charles Lepple <clepple at gmail.com>: > >> Note that this is the same VID/PID as on this example on the Lakeview >> Research home page: >> >> http://www.lvr.com/usb_on_a_budget.htm >> >> We can include the name "Lakeview Research" in the