similar to: [HCL] NHS Expert C Online 6000 supported by gamatronic

On Nov 22, 2014, at 5:16 AM, Thiago Wiezbicki <thiagowzb at gmail.com> wrote: > Below , it's a second upsc command using our UPS on battery and with device ID, battery time, battery low time that UPS calcs correctly. Let me remember now, We have the same UPS in 6, 8, 10 and 12 kVA version, and it's names are : Expert C Online 6000 , 8000 , 10000 and 12000 ( or Expert G III

*Q: Quick question: does "battery.runtime" update when the device is on battery, or is this field always zero?* *A: Yes, the UPS battery time starts counting when the device starts on battery.* Q: "battery.runtime.low" should be the number of seconds remaining before switching to "LB" status. This seems large, even for a 6000 VA UPS. Is this configurable? A: I

I wasn't clear. battery.runtime.low is not a counter, but a value estimated in seconds that is decreasing conforming the battery is discharging. It's mean: How much time (in seconds) will be necessary until the battery achieve the depleted status ( http://www.networkupstools.org/protocols/sec.html#Estimated_Minutes ) . If the UPS don't have a load, this value will be higher than the

On Nov 12, 2014, at 5:46 AM, Thiago Wiezbicki <thiagowzb at gmail.com> wrote: > > > Device Manufacturer: NHS > Device Name: Expert C Online 6000 > > upsc output: > > battery.charge: 100 > battery.current: 0.6 > battery.date: 01012014 > battery.runtime: 00000 Quick question: does "battery.runtime" update when the device is on battery, or is this

Device Manufacturer: NHS Device Name: Expert C Online 6000 upsc output: battery.charge: 100 battery.current: 0.6 battery.date: 01012014 battery.runtime: 00000 battery.runtime.low: 59940 battery.temperature: 29 battery.voltage: 210.5 device.mfr: NHS Sistemas de Energia device.model: EXPERT GIII 8kVA device.type: ups driver.name: gamatronic driver.parameter.pollinterval: 20

Below the answers: > This is the same as https://github.com/networkupstools/nut/issues/254 , right? Yes, this UPS is the same. > Does battery.runtime only get updated when on battery power, or is this with a different load? > battery.runtime.low: 59940 > battery.temperature: 00 Yes, this time time is updated on battery power, This is a dynamic counter that changes with a different

Device Manufacturer: NHS Device Name: Laser Senoidal 5000VA upsc output when the UPS is in normal condition: battery.charge: 100 battery.current: 0.4 battery.date: 12292015 battery.runtime: 00000 battery.runtime.low: 59940 battery.temperature: 00 battery.voltage: 163.4 device.mfr: NHS Sistemas de Energia device.model: Laser Senoidal 5000VA device.type: ups driver.name: gamatronic

This is the same as https://github.com/networkupstools/nut/issues/254 , right? (It's on my TODO list. DDL updates take a little longer than HCL updates.) Other comments below. > On Dec 29, 2015, at 1:55 PM, Thiago Wiezbicki - NHS <thiago.wiezbicki at nhs.com.br> wrote: > > Device Manufacturer: NHS > Device Name: Laser Senoidal 5000VA > > upsc output when the UPS is

On Jan 13, 2016, at 6:00 AM, Thiago Wiezbicki - NHS <thiago.wiezbicki at nhs.com.br> wrote: > > The battery.run.low can be higher than battery.runtime, do you agree? I agree with that statement, given what the gamatronic driver is currently reporting. However, I think it should report the elapsed time as battery.runtime.elapsed. I have created a Github issue to clarify the

On Jan 8, 2016, at 7:09 AM, Thiago Wiezbicki - NHS <thiago.wiezbicki at nhs.com.br> wrote: > >>> battery.runtime: 00076 >>> battery.runtime.low: 59940 >> >> This seems rather high. This variable is supposed to represent the runtime [in seconds] below which the UPS will signal "LB", but this capture only shows "OB". > > This value

I'm still working on the interface to the UPS we're selling. USB works great with NUT in Linux, and natively through Windows battery support. Now I'm looking over the serial protocol. I can essentially make it anything I want, and it's VERY tempting to make my own protocol that is intuitive and simple, but I have a feeling every UPS maker does that. So, before I do that...is

Hello Sir/Madam, I have a question related to UPS monitoring by SNMP cards via NUT(Network UPS Tools). We have a few SNMP Cards (MEGATEK) that connecting to a number of UPS`s. We need a centralized program to monitoring of our UPS`s. We want to know that, NUT can help us? Operating System: Windows or Linux SNMP Card type: Netagent model for MEGATEK company (www.megatec.com.tw). Yours

Hello, Currently I have an uninterruptible power supply manufacturer's model which is a sine NHS, it works with the protocol SEC. The SEC is a protocol of compatible systems listed in the NUT .. I would like to Know how to monitor this nobreak Software NUT .. They could send me a tutorial with the exact setup .. (I use Ubuntu Linux 32-bit) No longer required .. -------------- next part

Hi, Recently I got three units of this nobreak [0]: The intention is connect it with some file server and/or web server. I found the NUT via FreeNAS [1] , and the contribuition [2] of Ulisses and Rodrigo about this vendor SMS, in Brazil. But, initially, i'm trying to apply the Ulisses patch (for smsbrasil driver) in a Debian Server, with no success. Can anyone help me about the patch in

Hello I need to check that the NHS numbers in my database are valid. I''m storing them as ten-digit strings: the first nine are the identifier and the tenth is a check digit. There are four steps to calculating the check digit (from http://www.connectingforhealth.nhs.uk/systemsandservices/nsts/docs/tech_nn_check_digit.pdf): 1. multiply each of the first nine digits by a weighting factor

Rob, My suggestion is using the SEC2400 protocol. It's very simple, complete and based in text using using the idea of requesting and responsing. In the NUT software the name of the driver that manage this protocol is "gamatronic". Below the documentation: http://networkupstools.org/protocols/sec.html http://networkupstools.org/protocols/sec-protocol.html

Hi All, I'm trying trying to draw a colour wheel (a slice of hcl space) in R. Running the code below doesn't give me what I expect - there's some oddly bright colours of the wrong hue around c(0, 0) and I see three coloured circles (a small magenta, a medium sized yellow and a large cyan). Am I doing something wrong or is there a bug in the hcl code? (Also any suggestions for

Sds, Paulo Henrique Cardoso Administrador de Redes - T.I. NHS Sistemas Eletr?nicos Ltda Av. Juscelino Kubitschek de Oliveira, 5270 Cidade Industrial, Curitiba - PR Fone/Fax: (41) 2141-9246/9247 www.nhs.com.br IMPORTANTE: Esta mensagem, incluindo quaisquer anexos, ? endere?ada exclusivamente ao seu destinat?rio e poder? conter informa??es confidenciais. A revis?o, distribui??o,

On Feb 18, 2014, at 5:55 PM, Thiago Tiedtke dos Reis wrote: > Hi, > > Recently I got three units of this nobreak [0]: ... > [0] http://www.sms.com.br/produtos/Nobreak-SMS/Manager-III-Senoidal According to the HCL, for the Manager III, you might want to try the blazer_ser (or in 2.7.1, nutdrv_qx): http://www.networkupstools.org/stable-hcl.html -- Charles Lepple clepple at gmail

Hi everyone, I wanted to draw your attention to a new post on the developer.R-project.org blog: https://developer.R-project.org/Blog/public/2019/04/01/hcl-based-color-palettes-in-grdevices/ A new function grDevices::hcl.colors() greatly extends the color palette functionality available in base R. Also, the defaults in the heatmap functions image() and filled.contour() have been adapted