similar to: Linux and the APC Back-UPS ES

> Here is more informations. I hope this can help. Tell me if you need other > information. > > Version : Network UPS Tools upsd 2.2.0- > Driver : usbhid-ups > Network UPS Tools: 0.28 USB communication driver 0.28 - core > 0.30 (2.2.0-) Many improvements have been made to usbhid-ups since 2.2.0. You may want to upgrade, or at least check the

Hi there, I'm one of the maintainers of the SME Server distro (www.contribs.org) and we've been chasing this one for some time: http://www.contribs.org/bugzilla/show_bug.cgi?id=352 http://lists.alioth.debian.org/pipermail/nut-upsdev/2006-January/000543.html Many thanks to Peter Selinger and everyone else who helped with the debugging and patches. Thanks, Gordon

Okay, now that I've got NUT up and running with the newhidups driver, I can give it a quick shakedown. Most of the values look good, but are few are off. Here's what I get: elrond@foxstar:~$ upsc foxstarups@localhost battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 50 battery.date: 3150/08/01 battery.mfr.date: 2005/03/22 battery.runtime: 1935 battery.runtime.low: 120

Hi Peter, I've forwarded your mail to upsdev as it will be of interest for several people that are working on it. As I'm also on vacation (again) for a week and 1/2 as of this evening, I don't think I'll have the time for it before I get back.... I've not yet audited the patches, but these are queued on the Alioth tracker:

An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20120104/34be491b/attachment.html>

2006/1/27, Peter Selinger <selinger@mathstat.dal.ca>: > > ... > battery.mfr.date, which is probably the more accurate interpretation. > > I think the naming should be changed to propose both: - battery.date.mfr: Battery manufacturing date - battery.date.change: Battery change date Any comments? Arnaud -------------- next part -------------- An HTML attachment was scrubbed...

hi list, im running debian/testing(act. squeeze) with 2.6.26-2-amd64 kernel. first tried apcupsd what flawlessly worked but because i run nagios (needs nut running for 'check_ups'), im trying to run nut. dmesg and syslog show the device: Jul 27 00:08:06 kate kernel: [16001.477941] hiddev96hidraw0: USB HID v1.10 Device [APC Back-UPS ES 700 FW:829.D3 .I USB FW:D3 ] on usb-0000:00:1d.1-1

Hello, My APC Ups uses nut to manage all systems connected to it. But if online power failed until it shutdown, it not restart automatically after the power returned. It stay down until i restart it. When i execute the command: # upsc siUps1 it output me this: battery.alarm.threshold: L battery.charge: 018.0 battery.charge.restart: 15 battery.date: 03/31/07 battery.runtime: 120

Dear Nick, thanks for writing. I no longer work on development of UPS drivers; you will probably get a more up-to-date answer from the nut-upsuser mailing list (cc'd). I don't know if the Back-UPS 550 has similar commands to the Back-UPS ES 650. If it has a USB connection, then the answer is probably yes. The UPS will automatically turn itself back on after a power failure; this is the

Thought I would write some notes about how I got an APC BackUPS XS 1500 working with newhidups under Gentoo 2006.0. The specific issue here is the permissions on the device files used that libusb uses to access the USB hardware. I followed Peter Selinger's instructions at http://www.mscs.dal.ca/~selinger/ups/backups.html on getting newhidups going with an APC device. The sticking point for

Hi there, [ http://www.contribs.org/bugzilla/show_bug.cgi?id=654 ] I just received this: Broadcast message from nut (Sat Feb 4 04:02:45 2006): UPS UPS@localhost battery is low and Feb 4 04:02:45 bigted upsmon[11532]: UPS UPS@localhost battery is low Feb 4 04:02:45 bigted wall[4032]: wall: user nut broadcasted 1 lines (34 chars) but I believe this looks o.k., except for the input voltage

Hello all; I am new to this list. Recently we have been getting these cheap new Tripp-Lite "LCD" style UPS'es around here, and I was surprised to find the lack of Linux support. The model name is OMNI650LCD. Anyway, I tried the tripplite_usb driver and got a message instructing me to contact this mailing list. I might try to fix the problem myself, if I was more familiar with the

I am using the usbhid-ups driver with a Belkin UPS. upsc shows several parameters which I would like to both understand and probably change. In particular the following part of upsc output: battery.charge.low: 30 battery.charge.warning: 30 battery.runtime: 120 My questions are: 1) What is the difference between battery.charge.low and battery.charge.warning? I presume these are %

> Also, I don't think we have any confirmation of the variables that the AP9620 provides. Here is the list of full 'upsc' output for various APC models: > > http://buildbot.networkupstools.org/~buildbot/cayman/docs/latest/ddl/APC/index.html Frantz, Actually, it would be useful if you could send a copy of the output of 'upsc', 'upscmd -l' and

Hello, I'm using the stable amd64 port of Debian Linux. I installed (the latest) nut-2.0.1-4 and nut-usb packages for utilizing an APC Smart-UPS 1500 USB. I tried "apcupsd" first but "nut" makes an even more sophisticated impression on me and has more security options. I had problems with the newhidups driver. It didn't find a device with matching VendorID. And

On Dec 17, 2014, at 3:46 AM, Frantz de Germain <frantz at info.univ-angers.fr> wrote: > This seems to me a little bit complicated :-( Instead, can I use the > apcsmart driver with the provided 940-0625a c?ble (RJ45/DB9 connectors) ? Or > do I need to acquire an AP9620 SmartSlot expansion card, as I've seen in the > Hardware compatibility list page ? It sounds like you might

On Aug 30, 2018, at 6:54 AM, Ong, Kevin wrote: > > I'm very sorry for the delay here, I've been very swamped with work. Here's the relevant information you guys need: > > "upsc APC_BR1500GI" output: https://pastebin.com/rH3W0dbz > "upsrw APC_BR1500GI" output: https://pastebin.com/tEWv8a3d > "upscmd -l APC_BR1500GI" output:

On Nov 8, 2014, at 6:12 PM, Selva Nair <selva.nair at gmail.com> wrote: > Everything works rather well, except that the cgi-interface does not report input/output voltages and load for the C 1500 unit. > upsc also reports these values only for model 1000, not for 1500. Battery charge is and runtime are reported. For the 1000, do the values match this page?

On Jan 7, 2015, at 6:11 PM, DatGingerCat <dat.ginger.cat at gmail.com> wrote: > Hello, > > I have decided to upgrade my home server by turning it into an ESXi host and have also added an APC CS650 UPS. > My plan was to have NUT version 2.6.4 running in a Debian 7.7.0 virtual machine, NUT installed using apt. > I configured NUT to run as a netserver, installed the ESXi nut

I tested your fix (newhidups -DDD /dev/null) using both and APC Back-UPS 350 an APC Smart-UPS RT 2000 XL. No more segmentation fault due to the fixed-size array. ~Jacob -----Original Message----- From: nut-upsdev-bounces@lists.alioth.debian.org [mailto:nut-upsdev-bounces@lists.alioth.debian.org] On Behalf Of Peter Selinger Sent: Monday, October 16, 2006 12:12 PM To: Schmier, Jacob Cc: NUT