similar to: choosing a UPS (in the United States)

a customer of mine needs a UPS capable of supporting a small server in his office. Obviously, nut is a good thing for him for clean shutdown etc. especially with the crappy quality power in his office condo. I wanted to purchase an MGE UPS but it looks like they purchased APC and are now flogging that product line. Now, I've never been happy with APC. I have an APC 3000 (sans

I think the time for me to get involved in NUT documentation has come again. Late last week I had to buy a UPS under time pressure. The Eaton unit that thus project gifted me with in 2006(?) died during a severe thunderstorm watch, so it was off to MicroCenter to get a replacement pronto. I wound up buying an APC BN700MC. It was what they had in the performance range I needed. The removable

Peter, attached is a proposed patch to fix compilation of generic-hid.c when libusb's usb.h is not in /usr/include (but the -I flag is provided by "libusb-config --cflags"). It fixes the build under OS X, where Fink installs libusb with --prefix=/sw. I changed "usb.h" to <usb.h> so that 'make depend' wouldn't generate a dependency on 'usb.h' with

Hi there, been using NUT for ages and recently upgraded to a new server; while I'm waiting for a USB->Serial adapter for Solaris to arrive, I thought I'd play with the newhidups, as the APC UPS I have has a USB port and the new server doesn't have a serial port.... I've got Solaris 10 & newhidups working with the ugen driver up to a point, and that is a read

Hi, I got a Belkin F6C550-AVR UPS today and was trying to get it working with NUT, I used the "hidups" driver and got some data out of it, mainly the following: battery.charge: 100 battery.runtime: 120 driver.name: hidups driver.parameter.port: /dev/usb/hiddev0 driver.version: 2.0.0 ups.mfr: Unknown ups.model: Unknown ups.serial: Unknown ups.status: OL the versions of NUT that I tried

Hi, I got a Belkin F6C550-AVR UPS today and was trying to get it working with NUT, I used the "hidups" driver and got some data out of it, mainly the following: battery.charge: 100 battery.runtime: 120 driver.name: hidups driver.parameter.port: /dev/usb/hiddev0 driver.version: 2.0.0 ups.mfr: Unknown ups.model: Unknown ups.serial: Unknown ups.status: OL the versions of NUT that I tried

I would have to buy a new UPS that have to function for a simple desktop PC. I would the best about NUT compatibilty. The class of UPS must be 600-800 VA. What do you recommend me? Best regards Hello to all. -- Email.it, the professional e-mail, gratis per te: http://www.email.it/f Sponsor: Natsabe.it la più grande erboristeria online italiana * prezzi bassi tutto l'anno !

Hi All I'm trying to get my Ultra UPS connected. It connects using a standard USB cable I have --with-drivers=hidups in the configure command and I have lsusb showing Bus 001 Device 002: ID 0d9f:0001 Powercom Co., Ltd Bus 001 Device 001: ID 0000:0000 I have /dev/usb/hiddev0 now matter what I try I keep getting upsdrvctl start Network UPS Tools - UPS driver controller 2.0.3 Can't

Here is a summary of the changes I made to newhidups today (between the tags after_PSE_6 and after_PSE_9, roughly). * all the vendor-specific code that was in various "switch" statements has now been moved to the individual subdriver (apc-hid, mge-hid, belkin-hid) files. This also includes the vendor-specific Usage tables. In future, it should be quite easy to add new

To people with APC, CyberPower, Belkin and TrippLite UPS'es and using the 'usbhid-ups' driver. There are some concerns that the usbhid-ups driver is not acting as it is supposed to do. Could you run the following command (as root and with the mains plugged) and check if the UPS powers back on automatically? upsmon -c fsd I think we should *not* release nut-2.2.1 if we're not

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:

Hello, Problem: When I migrated from a DG965WH -> DP55KG motherboard, there were quite a bit of issues, host still does not reboot without special flags, e.g. reboot=a, the NIC driver is broken with the in-kernel version (the one on e1000.sourceforge) fixes that and finally my UPS USB has driver stale problems, with two issues already relating to the HW/drivers themselves it would not be

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

On Mar 2, 2015, at 12:49 PM, Rob Groner <rgroner at RTD.com> wrote: > Well, having spent a decent amount of time trying to get my driver file added into the Makefile build system (and failing), I've decided that for now, simply adding that one line to the openups-hid.c file and recompiling is the best route to go. When I can no longer live with the limited nature of the openups-hid

Ok, I tried this from scratch on a fresh 2.7.2 directory. I followed the web instructions, specifically: + I generated the new subdriver for my UPS (rtd-hid.*) based on PATH info. + I put them in the drivers subdir + I added the include line (#include rtd-hid.h) in usbhid-ups.c (specifically in the #ifndef SHUT_MODE section) + I added &rtd_subdriver, to the subdriver_list in usbhid-ups.c

Hi, I need to get a USB based UPS for a system which is running NUT 2.0.4 (a Debian Etch system). Does anyone know of a UPS that I can buy today that is supported by 2.0.4? Unfortunately upgrading the OS (and NUT) isn't an option. Previously, we used the Powerware 5110 (which used the bcmxcp_usb driver) and that worked fine, however that UPS has been discontinued and is no longer

Well, having spent a decent amount of time trying to get my driver file added into the Makefile build system (and failing), I've decided that for now, simply adding that one line to the openups-hid.c file and recompiling is the best route to go. When I can no longer live with the limited nature of the openups-hid driver, I'll revisit writing our own. Thanks for the helps. Sincerely,

Hello there, I don't think that's working,? I have done all your repo but i don't know how it's supposed to work. I have a idea, change vendor id and product id? to make the driver try to connect to the ups, what do you think of that ? With this driver maybe : usbhid-ups FatGear Le 16/09/2023 ? 20:40, Jim Klimov a ?crit?: > It seems the `libmodbus` library or headers were

It seems the `libmodbus` library or headers were not found, or something similar - so the driver against it was not built. Did you install `libmodbus-dev` before the build? What does `config.log` in the build root say (and.or the summary shown after you run the `configure` script)? On Sat, Sep 16, 2023 at 7:46?PM FatGear <fatgear1 at free.fr> wrote: > Hi, > > I don't know what

Hi Eric, sorry for the lag, summer time... I'm first seconding Charles comments 2014-07-09 12:31 GMT+02:00 Eric S. Raymond <esr at thyrsus.com>: > I think the time for me to get involved in NUT documentation has come > again. > welcome back > Late last week I had to buy a UPS under time pressure. The Eaton unit > that thus project gifted me with in 2006(?) died