similar to: NUT namespace: RFC for new variable addition

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, related to ATS (automatic transfer switch) this >time. >> >> in order to track "dephasing" between input sources (1 and 2),

(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 May 24, 2017, at 7:56 AM, Jim Klimov <jimklimov at cos.ru> wrote: > > On May 24, 2017 1:08:09 PM GMT+02:00, Charles Lepple <clepple at gmail.com> wrote: >> I don't think "dephasing" is common usage, but "phase shift" should >> suffice. >> >> Also, how does this apply to 3-phase systems? Is it nominally 120 >> degrees?

On May 24, 2017, at 5:11 AM, Arnaud Quette <arnaud.quette at gmail.com> wrote: > > 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:

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 -

Guess who's here to do an Asterisk demo this week without the power supply for his SPA-841. I have an ATA186 with me. Both phones use a 5v supply. Does anyone know whether the supplies are interchangeable? Thanks in advance; sorry for the noise. B.

Hi, Running a bunch of CentOS servers on 2U supermicro equipment, usually with 8 drives on Adaptec SmartRAID V or LSI Megaraid. In designing a rack in a data center, the question arises as to how to measure the amperage the server uses, prior to investing in power drops that actually do that for you, even remotely, for about $260.00-300USD per unit. This number is the important one these days

I would like to add a sentence to the man page for upssched.conf. After the sentence "Note that any AT that matches both the notifytype and the upsname for the current event will be used." I propose adding the sentence "If more than one AT matches the notifytype and upsname, the AT declarations are executed in the order in which they appear in upssched.conf. This is the

On Tue, 11 Jul 2017, Jim Klimov wrote: > On July 5, 2017 9:55:13 AM GMT+02:00, Roger Price <roger at rogerprice.org> wrote: >> I propose adding the sentence >> >> "If more than one AT matches the notifytype and upsname, the AT >> declarations are executed in the order in which they appear in >> upssched.conf. > > Your proposal and reasoning make

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 all, here is another variable addition, related to iPDU, that I'd like to make: outlet.group.n.color | Color of outlet group (hex code) | #daa520 For the sake of completion, Eaton ePDU outlet groups are identified with a color code on the device itself: http://powerquality.eaton.com/images/product-images/ePDU/more-images/EMA324-10DaisyChainWith2.jpg Here the first group

Hi Devs, do you have an estimate for a new release date? We want to deploy linux boxes which will include support for the newly contributed phoenixcontact_modbus driver. As we would like to create a package for both CentOS and an embedded Linux device we have, we would prefer if the package was based on a official release. If 2.7.5 is not coming soon (say 1 week) do you have a suggestion of a

The ATS community is having trouble with clang. They had been using an older version of clang and upgraded because newer versions give higher quality warning messages. Unfortunately, with 3.5, moving from -O1 to -O2 triggers a crash on startup in the clang-generated executable. I had suggested building with -fsanitize=undefined and -fsanitize=address to weed out any dependencies undefined

Hello, I am trying to insert a certain number of points into a certain position of a vector with this code: x <- seq(1:10909) x1 <- c(13112-10909) spect1 <- rnorm(13112) interpol <- approx(x,spect1,xout=c(seq(from=1, by=((10909 - 1)/(x1 - 1)), length.out=x1))) pos <- round(interpol$x,0) intensities <- interpol$y spect2 <- insert(spect1,ats=pos,values=intensities)

Yes, I have tried that option with no difference in behavior. It seems it ignores that option when provided. Just for reference, I am building it on RedHat 5. I have never had this issue on any previous version of OpenSSH. I use the default configuration with only the changes specified in the RHEL 5 STIG applied. I appreciate the security advice. The root account was indicated simply as an

Hello all! Some days ago we received new UPS?Powercom BNT-2000AP with USB interface to replace an old staff and I've spent four last days trying to connect it with NUT. I have a FreeBSD 8.4 box with NUT 2.7.2. # dmesg|grep -i powercom ugen0.3: <POWERCOM Co.,LTD> at usbus0 uhid0: <POWERCOM Co.,LTD HID UPS Battery, class 0/0, rev 1.10/0.01, addr 3> on usbus0 uhid0: <POWERCOM

the NEWS file for R-devel says * Even data-only packages without *R* code need a namespace and so may need to be installed under *R* 2.14.0 or later. but what should this contain? Can it simply be an empty NAMESPACE file? I assume that data does not have to be exported. -Michael -- Michael Friendly Email: friendly AT yorku DOT ca Professor, Psychology Dept. York University

>What kind of solid state 2 TB drive is this and how is it 'powered'? >It is looking like the drives aren't getting completely written to >before being removed as the ext4 error is a 'oh wait this drive >doesn't have everything I expected too late to give up aaaaaaaaaah' >type oops This is a Samsung 860 EVO 2TB. my connection is a cable that provides both

Dear R-help mailing list, I have a drawing problem with R: I need to draw an horizontal axis with date, here is the test code: > ticks <- c("2004-01-22","2005-01-22","2006-01-22","2007-01- 22","2008-01-22","2009-01-22","2010-01-22","2011-01-22","2012-01-22") > ats <-