similar to: NUT namespace: RFC for new variable addition

Hi all, here is another variable addition, related to iPDU, that I'd like to make: outlet.n.name | Outlet name (opaque string) | A1 For the sake of completion, we already have "outlet.n.desc" which is more of a description, as per its name. At Eaton, we implement: * outlet.n.name as the physical name of the outlet, related to the group of the outlet. For example,

Hi all, in order to track which phase (L1, L2, L3) feeds a physical outlet groups on a rack PDU, I'd like to extend the NUT namespace to add a new variable: outlet.group.n.phase Details and implementation can be found on: https://github.com/networkupstools/nut/pull/422 Comments and feedback warmly welcome. cheers, Arno -- Eaton Data Center Automation Solutions - Opensource Leader -

I've recently been working a bit on adding PDU (http://en.wikipedia.org/wiki/Power_distribution_unit) support in NUT. Some of you might have seen the Powerman thread, which also deals with adding more PDUs support: http://powerman.sourceforge.net/supported.html The result is that we now have support for 2 Eaton | Powerware ePDUs (Managed and Monitored iirc, check http://www.epdu.com). I plan

On Aug 4, 2017, at 3:00 AM, Arnaud Quette <arnaud.quette at gmail.com> wrote: > > Comments and feedback warmly welcome. > Please however note that I'll be pushing the related commit, since it seem trivial. It does sound trivial, but do we have that sort of information for other PDUs, and if not, how should names be represented in a GUI if outlet.n.name isn't present?

Hi Charles and the list here is an update on 2.7.3 2015-03-20 3:33 GMT+01:00 Charles Lepple <clepple at gmail.com>: > On Mar 19, 2015, at 2:00 PM, Arnaud Quette <arnaud.quette at gmail.com> > wrote: > > * #158: the branch has been collapsed into one commit, but additional >> documentation (nut-names.txt) is needed: >>

Hi all, I just acquired a new UPS and have been trying to get it to work with NUT. It's an Eaton/Powerware 9120 700i with both USB and RS-232 interfaces. I first tried the USB interface (using bcmxcp_usb) and found that the UPS worked fine for a few minutes but then NUT lost communication and didn't get it back. In addition the UPS itself seemed to lock up at one point such that the

List: I have an Eaton (Powerware) Model 5115 and am using the bcmxcp_usb driver on a OpenBSD 4.9 system. The upsdrvctl start appears to work and I get a message in my daemon log stating that it successfully started. I can successfully start the upsd daemon. I get a successful start messaage from the upsmon program, but it soon complains of 'stale' data. It looks like the driver

Hi, I'm a MGE Evolution 650 owner and, after putting in place a basic configuration for controlling my UPS, I'm going to tune a little bit better NUT for my needs. First of all let me describe my little (SOHO) scenario: I have the ISP modem/switch (providing VoIP too, so it's important to keep it running as much as possible), a small low power home server and a much hungrier PC.

I think I'm going to have the slightly rejigger the tripplite-hid.c driver to 'properly' support all of the data I know about it's outlets. A given UPS may have 'n' output loads. I could have 5, I could have 10, I won't know until I actually ask the UPS. But in order to use the hid to nut struct, I'm actually going to have to modify that struct dynamically, or

Hi all, here is another one, related to ATS (automatic transfer switch) this time. in order to track "dephasing" between input sources (1 and 2), I'd like to add a new variable: "input.phase.shift" Details and implementation can be found on: https://github.com/networkupstools/nut/pull/433 Comments and feedback warmly welcome. cheers, Arno -- Eaton Data Center

l?rdagen den 29 juni 2013 15.22.44 skrev Mike.: 8<-------------snip----------------- Sorry for the delay. > Here is the console output of bcmxcp with -DDD specified: > > > [snip] > 13.721204 Auto delay on: 2 > > 13.721243 send_command: (4 bytes) => ab 01 35 1f > 13.821127 send_command: (4 bytes) => ab 01 33 21 > 13.920982

Hi, I have several Linux machines at home and I'm considering buying a UPS for them. I see that many models are supported by NUT (great!) but since I'm new to the UPS world I have some questions about UPS features and NUT support of them I couldn't find an answer for: 1/ are there UPS models who report/meter power usage through USB? per UPS socket or globally? 2/ are there UPS models

(hmmm, finally hitting the Sent button...) 2017-05-24 13:56 GMT+02:00 Jim Klimov <jimklimov at cos.ru>: > On May 24, 2017 1:08:09 PM GMT+02:00, Charles Lepple <clepple at gmail.com> > wrote: > >On May 24, 2017, at 5:11 AM, Arnaud Quette <arnaud.quette at gmail.com> > >wrote: > >> > >> Hi all, > >> > >> here is another one,

On 6/29/2013 at 6:16 PM Kjell Claesson wrote: |l??rdagen den 29 juni 2013 11.28.14 skrev Mike.: |8<------------------snip--------------------- |Hi Mike, |> |> Thanks for the quick reply. |> |> I checked the log file (which, admittedly, I should have done before I |> posted about the problem :) ). |> |> Here's the command and the corresponding log message: |>

Device Manufacturer: Eaton Device Name: 5S1500LCD ---------------------------------------------------------- upsc output: battery.charge: 100 battery.charge.low: 20 battery.runtime: 3515 battery.type: PbAc device.mfr: EATON device.model: Ellipse PRO 1500 device.serial: 0000000000 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2

Device Manufacturer: Eaton Device Name: 5S1500LCD ---------------------------------------------------------- upsc output: battery.charge: 100 battery.charge.low: 20 battery.runtime: 3515 battery.type: PbAc device.mfr: EATON device.model: Ellipse PRO 1500 device.serial: 0000000000 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2

I am running NUT 2.2.0 compiled from the FreeBSD ports tree. [inchoate 14:50] ~ >upsc ups1 at localhost battery.charge: 59 battery.charge.low: 20 battery.charge.restart: 0 battery.runtime: 6350 battery.type: PbAc battery.voltage: 43.0 driver.name: usbhid-ups driver.parameter.offdelay: 120 driver.parameter.ondelay: 13 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version:

Hi! We have two MGE Evolution 1100 here, and I want to make use of the powershare outlets to force a particular boot sequence on the machines powered by them. However I'm not sure how to set those variables upon NUT starting, without having to change the init scripts to call "upsrw". Is there some place where I can set them, where they can be read automatically on startup? One of

Thanks again, Great to see confirmations of more and more things working! > I wonder what's the fastest method to test the function (previously I setup the ups and unplug the utility from the ups for testing). > is "upsrw driver.flag.allow_killpower=1" then "upscmd driver.killpower" the correct testing procedure? At least by intent of this new feature -- yes.

Thanks again, Great to see confirmations of more and more things working! > I wonder what's the fastest method to test the function (previously I setup the ups and unplug the utility from the ups for testing). > is "upsrw driver.flag.allow_killpower=1" then "upscmd driver.killpower" the correct testing procedure? At least by intent of this new feature -- yes.