similar to: Submitting patches

I've discovered an issue (which may be unique to my UPS) with this commit. init_communication now returns -1, instead of 0 if it failed to read the manufacturer info, this makes sense after all. With my UPS (Belkin F6C1400-EUR), the response to the Manufacturer command returns only 6 spaces (rather than "BELKIN"), this means that init_communications fails, and the driver fails

Hello, I'm looking for a UPS that the beeper can be silenced with nut via ups.beeper.status variable for a HTPC close to bedrooms. I have googled extensively and there is not a lot of information about which UPS's actually support this feature. There are few references to UPS's that apparently list ups.beeper.status as being available, but without actually being

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:

Hi All, I have got the Belkin F6S600auUSB UPS working with the blazer_usb driver. I pulled the power to the ups last night and it sent a message to the server saying it was on battery then ran for another 10 minutes and then sent a message to the server telling it to shut down, which it did. upswr did not return anything. [root at verity ~]# upsc ups battery.voltage: 13.50

Hi All, I have got the Belkin F6S600auUSB UPS working with the blazer_usb driver. I pulled the power to the ups last night and it sent a message to the server saying it was on battery then ran for another 10 minutes and then sent a message to the server telling it to shut down, which it did. upswr did not return anything. [root at verity ~]# upsc ups battery.voltage: 13.50

After installing NUT, I've noticed that the belkin driver capabilities are rather basic. We have a Belkin Regulator Pro 1400VA (F6C1400-EUR), so I've updated the driver to support control of the buzzer & tests, as well as adding test result reporting. I've attached the following patches. Hopefully they can be added to any upcoming versions. -- John Bayly Systems Administrator

Package: nut Version: 2.0.5-3+b1 Running: Debian Testing Arch: x86_64 BUG: (the battery is relatively new (6mos) and there have been no recent power outages) Jul 28 04:29:44 p34 upsmon[2402]: UPS belkin at localhost battery is low Jul 28 05:13:15 p34 upsmon[2402]: UPS belkin at localhost battery is low Jul 28 05:14:05 p34 upsmon[2402]: UPS belkin at localhost battery is low FIX: (go back to

I've a Belkin Regulator Pro (F6C1400-EUR) connected via serial to a FreeBSD machine using NUT v.2.4.3 Sometimes I get a series of logged messages saying that the data is switching between stale and valid, this in itself isn't an issue, however occasionally when the communication is re-established, upsmon gets a "On battery" message followed quickly by "Battery low"

Hi Peter, I got all your patches and applied them, and I wanted to say kudos for a great job done. This is the output of upsc that I'm getting right now. I had the same issue when using any cvs version (from two weeks ago) that made my UPS go into a state where it wasn't functioning normally (checking the kernel log shows that it cannot be connected and I had around a page of DEVFS_USB

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

On Sun, Mar 1, 2015 at 2:23 PM, Gene Heskett <gheskett at wdtv.com> wrote: > Hi Charles; I hope this finds you well. Hi Gene, > Here is dmesg output: > gene at coyote:~$ dmesg |grep Belkin > [ 3.315667] usb 2-3: Product: Belkin UPS > [ 3.315669] usb 2-3: Manufacturer: Belkin > [ 4.084258] generic-usb 0003:050D:0751.0009: hiddev0,hidraw4: USB HID v1.11 Device

Hi Charles; I hope this finds you well. Here is dmesg output: gene at coyote:~$ dmesg |grep Belkin [ 3.315667] usb 2-3: Product: Belkin UPS [ 3.315669] usb 2-3: Manufacturer: Belkin [ 4.084258] generic-usb 0003:050D:0751.0009: hiddev0,hidraw4: USB HID v1.11 Device [Belkin Belkin UPS] on usb-0000:00:02.0-3/input I have configured it to use this generic-usb, and probably made it less

2010/10/13 Vitaly Lavrov > I found bug in nut/drivers/megatec.c - force shutdown may dont work. > See patch. > could you please give a try to blazer, since it is set to replace megatec with 2.6.0. Arjen will quite probably comment on your patch usefulness within the blazer scope. thanks for your contrib. cheers, Arnaud -- Linux / Unix Expert R&D - Eaton -

On Feb 15, 2014, at 6:46 PM, Greg Vickers wrote: > Thanks! I've attached the file to this email (bcmxcp_usb.output2014160926.gz), it ran for 12 seconds, and looks like it's looping by that time. I'm not sure what to look for, does grepping for 'Yes' show the variables that the driver can pull off this UPS? The boolean variables seem to be indicated by "Yes". I

Hi Andy, I've forwarded your info to the development list, and Carlos Rodrigues (the megatec driver author and maintainer. As a side note, there is a megatec_usb driver underway. You might want to give it a try. @Carlos: I let you update the drivers.list. Thanks for your report, Arnaud Quette -- Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt Network UPS Tools (NUT) Project Leader -

Hello Fabian, > I got my UPS (Belkin F6H350deUNV) to work with the "megatec" driver. > Obviously the de/uk part in the name of these products are > localizations of some sort. So the F6H 350/500/750 UNV Home Office > products should all work with that driver. > > bigone nut # upsc ups@localhost > battery.charge: 95.0 > battery.voltage: 13.50 >

On 16/02/14 00:38, Charles Lepple wrote: > On Feb 15, 2014, at 2:57 AM, Tim Dawson wrote: >> The driver will poll the UPS for what variables it supports when it starts, and then go into a polling loop. Look for a section defining the meter map, and you should see the result, as well as the raw data. > Tim: spot on. > > Greg, > > If you want, you can capture the -DDDD output

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 > >

Greetings! Thanks to all the developers who have made this project so far. Searching for a Linux based Belkin UPS monitor led me straight to the Network UPS Tools. I have bought a Belkin F6C900-UNV (900VA) for use on a Slackware 10.2 server to replace an older APC model that died suddenly. So far I have successfully managed to get NUT 2.0.5 compiled and configured and found that this Belkin

Hello, I was able to get the Vertiv/Liebert UPS (Vertiv Liebert PSA5 1500VA 900W - PSA5-1500MT120) to start working with NUT and "usbhid" driver, but would appreciate help to get it to work properly. Here's the output from the "upsc" command for a Cyberpower UPS I have: battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS