similar to: NUT: Belkin Universal driver - modification to -k behaviour (diff attached)

Hi Sorry about this 2nd message... I forgot to say, the diff is based on the 2.0.3 tarball from www.networkupstools.org. Jo Turner -xx- -- jT | mail to: hyvan_trant@hotmail.com ** | website: http://www.chiark.greenend.org.uk/~jsturner/

Hi Peter Now I can get subdrivers to have ups.conf/command-line options, I've started looking at making the newhidups belkin-hid subdriver have the wait and wait-on-shutdown behaviour in the same was as belkinunv, and having just gone back and gone "yuck!" at my huge comments in my revised belkinunv source, I decided to clear out all the extraneous commentary in my

All, I just bought a Belkin F6C1100-UNV and am trying to get it to work with NUT. I have tried many drivers ( "belkin", "belkinunv", "genericups upstype=4", and "genericups upstype=7", "bestups", "fentonups"). None of them seem to work. Does anyone have any experience with this device? If there is some utility that you all use to

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

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 Arjen My apologies fro drifting off topic in the other mailing list...:-) On the bottom of the Belkin UPS unit - is the model number: F6C120auUNV The "au" is for Australia I think. "man belkinunv" states that F6C120-UNV is supported - and I assumed that the "au" would not prevent this. I plugged in the USB to gather the information you requested. My intention

I'm trying to set up a belkin f6c1100-unv UPS to work with nuts. From reading the mailing list, it sounds like the belkinunv serial driver should work and that the USB driver is potentially troublesome. Is this a correct impression? Also I may have missed this but if I do go with the serial (or USB port) is there any simple command line method for verifying basic connectivity? The

Hi, I've been fighting with trying to get a Belkin Universal model F6C800-UNV to work with NUT. The error I am getting is as follows: ---------------------------------------------- * Starting UPS drivers ... Network UPS Tools - UPS driver controller 2.0.0 Network UPS Tools - Belkin 'Universal UPS' driver 0.06 (2.0.0) tcgetattr(/dev/ups): Inappropriate ioctl for device Driver failed

I recently installed NUT 2.2.1 and set it up with a Belkin F6C100-UNV. I can monitor it via serial (belkinunv) or USB (usbhid-ups) cable, and both do seem to work fine, but I would prefer USB to avoid having to add a PCI serial card to the machine. I had to unplug something else to try it with a serial cable. Using 'belkinunv', there's a "-x wait" option: [ from

Hi, I bought a Belkin Active Battery Backup UPS (http://www.belkin.com/uk/activebattery/) yesterday with a USB port and hoped it would work with nut. The device will show up in /proc/bus/usb/devices as a Cypress Semiconductor USB to Serial. It creates /dev/hiddev0 (and this disappears when the UPS is unplugged). I've tried using belkin, belkinunv, usbhid-ups and megatec_usb. I've tried

This will sound a bit odd. I have a current server running with a UPS. I'm in the process of replacing that server with another and obviously want Nut to monitor the new server. The new/old servers are in different locations, so I don't have access to the UPS while configuring the replacement server. I think I have the config ok, but what errors would you expect to see? Typically I'm

I looked through the faq, but couldn't find an answer to this. I'm trying to configure nut-2.0.4-26 on SuSE linux 10.2. In ups.conf, I have [myups] driver = belkinunv port = /dev/undefined desc = "Local UPS" I'm trying to find out what the port should be set to. lsusb shows: Bus 001 Device 005: ID 050d:0980 Belkin Components Device Descriptor: bLength

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,

Hallo, i'v bought a Belkin F6C230. The CD which is shiped with this UPS has a totally useless installation part for linux. So I'v tried to use nut instead of the Belkin software. I've tried both belkin drivers (belkin and belkinunv) and also the generic driver (genericups) with all available upstypes. None of these drivers did actually work. Has anybody experiences with this UPS

For the record, I was able to get the following working: Device: Belkin F6C1500-TW-RK Driver: belkin I tried the "belkinunv", which I use for my F6C1100-UNV, but it didn't work. At least there was a driver that worked! :-) Feel free to add it to the list of "tested" configs. Thanks, Dave ---------------------------------------------------------- Are Your Friends

Philipp Leusmann wrote: > > Ok, I tried this and my results seem to bet he same as reported. Then I > think I=B4ll have to stick with the windows-driver at least on my main > machine.=20 > Or is there anything I can help to fix this driver? I don't know why we can't read anything from this device. There are many ways in which one could make a buggy device that works with

On Sunday 08 December 2019 21:48:03 Charles Lepple wrote: > On Dec 7, 2019, at 7:01 PM, Gene Heskett <gheskett at shentel.net> wrote: > > What driver do I now put in /etc/nut/ups.conf? hid-generic doesn't > > seem to want to talk to it, and the original name _(usbhid-ups) > > doesn't work from new mobo. Oh wait, I can't spell. But that didn't > >

I upgraded from V2.2 to V2.4. I use the "upslog" command to log the values of my belkin ups (belkinunv via serial port). It would occasionally start to record garbage, but it would always go back to normal in V2.2 if I restarted. In V2.4 it would not record the values, and the process would fail after the next interval had passed. I had set if for 300 seconds. I walked through the

While working on the mge-hid subdriver, I wanted to add the 'beeper.mute' command. Unfortunately, the description I intended to use was used already by the 'beeper.off' instcmd: CMDDESC beeper.off "Temporarily mute the UPS beeper" Now of course we could add another instcmd 'beeper.reallyoff', but instead I would prefer to bite the buller and do the following: