similar to: NOBREAK

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

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

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

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

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

I use Centos 7.6.1810 in my server with nut-2.7.2-4.el7.x86_64 which contains Solis version 0.60 08/18/2005, my last version. My hardware related by upsc is Microsol Solis 1.5, the same used to develop the driver. It's an ancient nobreak, but i still works, by the way, an excellent hardware, using the third set of batteries. If you need more information, please let me know. Greeting, Silvino.

*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

On Jun 19, 2019, at 11:56 AM, Silvino Benevides Magalhaes wrote: > > Unfortunately I do not use the latest versions of NUT, the driver I created, solis, was changed, not by me, and now does not work on my nobreak, which I used to create the driver. > > greetings > > Silvino B. Magalhaes Silvino, We have had several changes to solis over the years to add new models

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

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

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 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, I've seen posts (but no answers) about clearing a file lock on a Samba share. Presumably this kind of thing happens when the program abnormally terminates and doesn't close its open files. I've got a file that smbstatus reports as: 1216 DENY_WRITE 0x20089 RDONLY NONE /shares/share1/Files/december.xls Fri Jan 12 12:51:30 2007 Trying to open this in Excel

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

Hi Tomas, Can you share the full code for your benchmark, compiler options, and performance results so that I can try to reproduce them? There are a lot of variables that can affect the results. Private email is fine if it is too much for the mailing list. I am measuring on Knight's Landing (KNL) that was released in November. KNL is not a co-processor so no offload is necessary. R executes

What information Do I need to provide more, beyond upsc and shutdown tests for add these devices on HCL ? Thanks, ------------------------------ Thiago Wiezbicki -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20141125/07793b94/attachment-0001.html>

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

Hi I am a newbie to R but have tried a number of ways in R to do this and can't find a good solution. (I could do it out of R in perl or awk but would like to know how to do this in R). I have a large data frame 49 variables and 7000 observations however for simplicity I can express it in the following data frame Base, Image, LVEF, ES_Time A, 1, 4.32, 0.89 A, 2, 4.98, 0.67 A, 3, 3.7, 0.5

Hi Marcio, first, please subscribe to the NUT mailing list prior to sending any further mail: http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser next, most (if not all) people you mailed to are either retired from the project, or not active anymore. 2012/5/8 Marcio - NHS <marcio at nhs.com.br>: > Dear

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,