similar to: AW: AW: Belkin F6H650 on USB port

I think someone tried this recently, although I cannot find the post any more. It may be helpful, but it is not guaranteed that we will find anything. Could you please keep the discussion on the mailing list? Thanks, -- Peter Philipp Leusmann wrote: > > Wouldn't it help to sniff usb-communication with the windows driver? > > Philipp > > > -----Urspr=FCngliche

Hi, is there a way to use my Belkin F6H650 on the USB port? I already installed usbhid-support, but neither the hidups worked (reports "/dev/usb/hiddev0 is not a UPS") nor genericups with upstype=7 and the hiddev set as device ("ioctl TIOCMSET: Invalid argument") worked. I have installed the debian sarge package of nut 2.0.1 (2.0.1-4) Regards, Philipp

I have checked in a cleaned-up version of patch #302111 (Belkin support) into CVS. See cvs diff -uN -r before_PSE_2 -r after_PSE_2 to check the difference. Here is the CHANGES entry: Tue Sep 13 20:50:14 UTC 2005 / Peter Selinger <selinger@users.sourceforge.net> - newhidups: added Belkin support. Also added some new variables and instant commands (some of these were already used by

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

Oh oops, I see you already did. -- Peter selinger wrote: > > You could send it without "submitting" it. That's the advantage of > patches - they can be discussed. There are lots of eyeballs here that > might see what's wrong. Thanks, -- Peter > > Eric S. Raymond wrote: > > > > Peter Selinger <selinger at mathstat.dal.ca>: > > > I

Dean K. Gibson wrote: > > My Belkin UPS 1000 failed about a month ago; all of a sudden it > reported a battery failure. Since the Belkin logs showed this as in > instant transition from 99% to 22%, I assume a circuit board failure, > not a battery failure. Similarly, one Belkin UPS 500 circuit board > failed after I used my 100W amateur radio transmitter (not connected to

hi i have a belkin ups here some setting chmod 0600 /dev/hiddev0 chown nut:root /dev/hiddev0 linux:/home/sonia # /usr/lib/ups/driver/upsdrvctl start Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4) No matching USB/HID UPS found Driver failed to start (exit status=1) linux:/home/sonia # /usr/lib/ups/driver/upsdrvctl -u root start

2005/9/25, Peter Selinger <selinger@mathstat.dal.ca>: > > Arnaud Quette wrote: > > > > Some more points while you're at it: > > - newhidups will have to be renamed. My aimed was to let the name until > we > > can superceed hidups. Then remove hidups, and rename newhidups to > usbhid-ups > > (name proposition welcomed, but should match the fact

Zaid, I have a Belkin F6C800-UNV which has both a serial and USB connector. The serial connection is already working with the Belkinunv driver. I will connect via the USB and then compare both sets of variables. This should allow me to correlate and shed some light on the meaning of many of Belkin's non-standard "Usage" descriptors. With this information, it should be very easy

Hi Shane, please try the instructions at http://www.mathstat.dal.ca/~selinger/ups/backups.html (with appropriate modifications for FreeBSD). If you can't get it to work, please get help from the nut-upsuser mailing list (cc'd above), as I am no longer actively involved in NUT development. Good luck, -- Peter Shane Roberts wrote: > > Hi Peter, > > I am running the NUT

Marc Collin wrote: > > Le mercredi 27 d=E9cembre 2006 00:29, vous avez =E9crit=A0: > > Hi Marc, > > > > the answer to your question is contained in the file INSTALL, > > distributed with NUT, section 6 "Set ownership data and permissions on > > your serial or USB ports that go to your UPS hardware." > > > > Quote: > > > >

Have had no issue until I ran apt-get dist-upgrade this morning: # /lib/nut/newhidups -u nut -DDDDDD auto Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5) debug level is '6' Checking device (0000/0000) (001/001) - VendorID: 0000 - ProductID: 0000 - Manufacturer: unknown - Product: unknown - Serial Number: unknown - Bus: 001 Trying to match device Device does not

I just noticed the following curious behavior when using newhidups with upsdrvctl and two different USB devices: My ups.conf contains two devices, both using newhidups: [belkinusb] driver = newhidups port = auto desc = "Belkin UPS, USB interface" vendorid=050d [mgeusb] driver = newhidups port = auto desc = "MGE UPS, USB

Hi I'm sending this to you as it appears that you are the person who looks after and/or supervises the code for NUT's Belkin drivers. I'm using the address you use for the Nut-upsdev mailing list ( selinger at mathstat.dal.ca ). Anyway... I have a Belkin Universal UPS and, having just upgraded my Fedora Core system from 4 to 5 and had to go back through the system RC files

Dear Ashley, I have no personal experience with the Tower-Rack series, but someone reported on the Nut-upsuser mailing list on 29 Nov 2005 that these models work with the "belkin" driver of the NUT software (http://www.networkupstools.org/). This is for the serial port. For USB, the NUT "newhidups" driver should work (or if it does not, we can fix it). The software that

Hi James, thanks for the feedback. The output you get seems generally fine, except for battery.voltage: 0.0 and output.voltage: 164.0; these values are consistent with what Phil DeBoest reported. Upsmon normally executes the shutdown command when you reach the "low battery" threshold, as decided by the UPS and/or driver. It does so by looking at ups.status, not battery.charge. --

Hi Patrick, I didn't get further bug reports from you, so I have now listed your device as "supported" by newhidups. Last I saw as of your below message, the driver was working as expected. If there are any future problems, let me know! -- Peter Patrick Nolan wrote: > > Remember me? Back in May we exchanged some messages about my Tripp-Lite > UPS. My boss has gone on

Jochen Bern wrote: > > Peter Selinger wrote: > > have you been able to get your Liebert UPS to work? If I am correct, > > it should work with the newhidups Belkin subdriver. Could you please > > post your results? I am curious to know if this works or doesn't - and > > if yes, we should add permanent support for Liebert into NUT. > > I'm sorry, but

# /lib/nut/newhidups -DDDDD -u nut /dev/usb/hiddev0 Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4) debug level is '5' Checking device (0665/5161) (001/003) - VendorID: 0665 - ProductID: 5161 - Manufacturer: unknown - Product: unknown - Serial Number: unknown - Bus: 001 BELKIN 550VA UPS BATTERY BACKUP Should I be using a different driver?

2006/10/2, Peter Selinger <selinger@mathstat.dal.ca>: > Arnaud Quette wrote: > > > > 2006/9/29, Peter Selinger <selinger@mathstat.dal.ca>: > > > > > I don't really understand the purpose of the "Testing" branch. It has > > > not been touched since July, as far as I can see. I also don't > > > understand NUT's release