similar to: preventing automatic reboot

I have a new APC Smart-UPS SUA2200RM2U. I've had no success with the manufacturer's PowerChute software and smart signaling, so I have decided to try NUT. The smartups driver can't make contact through the serial port. Since this is rack-mounted, it comes with a 940-1524 serial cable. As far as I can tell, this is supposed to work with smart signaling. Here's my ups.conf:

Le Tue, 16 Dec 2014 20:38:50 -0500 Charles Lepple <clepple at gmail.com> ?crivait: > On Dec 16, 2014, at 9:45 AM, Frantz de Germain <frantz at info.univ-angers.fr> wrote: > > > Bye the way I just realize that I can't retrieve the ups.load, among other > > thing :-( > > To the best of my knowledge, Microlink is not supported by any third-party tools

On Dec 16, 2014, at 9:45 AM, Frantz de Germain <frantz at info.univ-angers.fr> wrote: > Bye the way I just realize that I can't retrieve the ups.load, among other > thing :-( To the best of my knowledge, Microlink is not supported by any third-party tools (including NUT), but some variables are exposed via standard USB HID. Apparently, ups.load is not one of them. Your UPS might

Le Thu, 4 Dec 2014 08:42:37 -0500 Charles Lepple <clepple at gmail.com> ?crivait: > On Dec 4, 2014, at 5:30 AM, Frantz de Germain <frantz at info.univ-angers.fr> > wrote: > > > Hello, > > > > does any one know how to change the date of the self tests on APC UPSes ? > > I'd like to be able to choose the day and the hour so that it happens at >

On Dec 18, 2014, at 9:16 AM, Frantz de Germain <frantz at info.univ-angers.fr> wrote: > What is the difference between "test.battery.start.deep" and > "test.battery.start.quick" command (upscmd) ? The intent for the quick test is to only discharge the battery a little bit, whereas the deep test would discharge until the low battery threshold is reached (or the

Le Tue, 16 Dec 2014 15:36:29 +0100 Frantz de Germain <frantz at info.univ-angers.fr> ?crivait: > Hello, > > I'm testing an APC SMT3000RMI2U connected to an USB port with Nut 2.7.2. I've > got the message : > > "interrupt pipe disabled (add 'pollonly' flag to 'ups.conf' to get rid of this message)" > > I've been looking for

Le Fri, 5 Dec 2014 10:07:33 +0100 Frantz de Germain <frantz at info.univ-angers.fr> ?crivait: > Le Thu, 4 Dec 2014 08:42:37 -0500 > Charles Lepple <clepple at gmail.com> ?crivait: [...] > > This forum post from 2013 suggests that an easy way is to change the UPS > > setting to "test at power on", then use a script (with NUT, you would run > >

On Dec 4, 2014, at 5:30 AM, Frantz de Germain <frantz at info.univ-angers.fr> wrote: > Hello, > > does any one know how to change the date of the self tests on APC UPSes ? I'd > like to be able to choose the day and the hour so that it happens at office > hours, in case of any problem... > > I've tried to do this by launching a test at a convenient time, but

I have a network with two older systems protected by APC UPSs. Both systems run OS/2 and will continue to do so. Both systems have APC PowerChute Plus 4.2.3 installed and I can use that software to monitor and control both systems. I am also now running several linux systems, in fact I spend almost all my time on the linux systems and these OS/2 systems are servers running in the

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

Hello, does any one know how to change the date of the self tests on APC UPSes ? I'd like to be able to choose the day and the hour so that it happens at office hours, in case of any problem... I've tried to do this by launching a test at a convenient time, but the self tests still occurs at the previous date and hour :-( Regards. -- Frantz de Germain D?partement Informatique UFR

Hello, I'm testing an APC SMT3000RMI2U connected to an USB port with Nut 2.7.2. I've got the message : "interrupt pipe disabled (add 'pollonly' flag to 'ups.conf' to get rid of this message)" I've been looking for "pollonly" in the usbhid-ups man page, but it didn't help me. Could someone explain me what does this means exactly ? What are

This patch introduces a handful of new options, I mentioned earlier in: http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02088.html See the large commit message in the follow-up for the details and rationale. I realize it's a bit larger diff - so if it's required I can split it into few smaller ones. Michal Soltys (1): APC smart driver update and new features.

This is 2nd version of the earlier patch featuring a few new features and fixes to the apcsmart driver, following the remarks in: http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02294.html Major changes from v1: - handle battery.charge and battery.runtime checks at main.c level - handle "immutable but writable" conflict gracefully at driver level -

Sorry for a bit longer delay than I anticipated, I was stuffed with the work. This is the next iteration of the patch adding some functionality to apcsmart driver, and relying on 'ignorelb' recently added. Follow up from previous thread: http://www.mail-archive.com/nut-upsdev at lists.alioth.debian.org/msg02331.html Main differences is that V3 is split into many small patches, so the

Michal, I ran across this Debian bug today: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707223 It's a bit of a corner case, and it's for NUT 2.6.4 (apcsmart driver v3.04), but I was wondering if it was still applicable for the latest code? "nut reports 100% battery charge after unplugging the battery on a Smart-UPS 2200 RM (SUA2200RMI2U) using apcsmart. Powerchute correctly

Hi All, I've got two APC SmartUPS's that behave differently with nut, I have a SmartUPS1400 & a SmartUPS1250. I'm fairly sure this isn't a nut problem but more likely a problem with the age of the SmartUPS1250 and the apcsmart driver not being able to identify it. Under the APC Powerchute software the same monitoring & command parameters are available for both

Hi, I run os x yosemite and found out about NUT tonight. I messed around with fink and macports but get stuck very soon. I dont know how to install anything that doesnt have a .dmg or .pkg installer. Does anyone have a step by step (written in "for dummies" format on how to get this all to work? Just looking for a PowerChute alternative that actually lets me control and monitor my

'lo, UPS model: APC Back-UPS BR 800 (supplied by Dell) My USB connection: Bus 001 Device 002: ID 051d:0002 American Power Conversion Back-UPS Pro 500/1000/1500 # upsc desk@localhost|grep load ups.load: 0.0 This UPS has 2 pc's and some minor other gear connected, yet the load stays at 0.0 when checking with nut. driver.version: 2.0.5 driver.version.data: APC/CyberPower HID 0.9

tisdagen den 16 december 2014 15.36.29 skrev Frantz de Germain: > Hello, Hi Frantz, > > I'm testing an APC SMT3000RMI2U connected to an USB port with Nut 2.7.2. > I've got the message : > > "interrupt pipe disabled (add 'pollonly' flag to 'ups.conf' to get rid of > this message)" > > I've been looking for "pollonly" in