similar to: Using 'dummy.ups' for a real application, not just testing...

Tom via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> writes: >>That makes sense. So you'll have input voltage, output voltage, and >>output current I would guess. You might consider a nodemcu (ESP8266) >>publishing via MQTT to reduce power and use of unobtainium. > > Yes, that is exactly what I was planning to instrument. Maybe battery > voltage too

My $0.02: LB is baked in to nut behavior. So if a UPS doesn't report LB, then it makes sense to synthesize it. Synthetic LB is the cleanest fix at the earlier processing point. One could have a config that is basically synthetic-lowbatt-percent that generates LB if (as Jim says) on battery, not calibrating, and batt% <= that. One could have a similar config

Hi I have just purchased a Cyberpower CP1300EPFCLCD UPS. It is not listed in your Compatibility List http://networkupstools.org/stable-hcl.html I am very new to all this but do have a background in IT. I have been retired for 18 years so am a bit out of touch so please excuse if I am a bit fuzzy. I will try my best to explain my issue below. When I plug my UPS into my Synology NAS

People, A couple of decades before I was retired and was still working for other people I had cause to install UPSs and they usually had RS232 ports to allow the setting up of shutdown scripts to UNIX / Linux servers. Now, after not having to be concerned by those issues for some time - most of my little web sites have been on Digital Ocean or other suppliers VMs for a long time - I am

People, A couple of decades before I was retired and was still working for other people I had cause to install UPSs and they usually had RS232 ports to allow the setting up of shutdown scripts to UNIX / Linux servers. Now, after not having to be concerned by those issues for some time - most of my little web sites have been on Digital Ocean or other suppliers VMs for a long time - I am

Hello Nut List! I have 2 "Lacerda 10KVA" UPS that returns strange values for Q1 and F commands: Q1 (215.0 215.0 219.0 004 60.0 2.27 39.0 00000001 F #220.0 045 240.0 60.0 At least what I know about Megatec, It seems to say that it has a 240.0 V battery with currently 2.27V. Quite strange. I contacted Lacerda to help me interpret this values and they said that 2.27 is just 1 element

On Fri, Mar 28, 2014 at 8:12 AM, Charles Lepple <clepple at gmail.com> wrote: <<Snip>> > > I'll be honest, I haven't really done much with the CGI scripts lately. For debugging values, it is probably better to be closer to the driver. I'd recommend using "upsc" or the driver logs. > > To that end, the .ac.txt and .bat.txt files both show 24.0 V:

On Mar 28, 2014, at 9:08 AM, Bill S wrote: > On Fri, Mar 28, 2014 at 8:12 AM, Charles Lepple <clepple at gmail.com> wrote: > > <<Snip>> >> >> I'll be honest, I haven't really done much with the CGI scripts lately. For debugging values, it is probably better to be closer to the driver. I'd recommend using "upsc" or the driver logs.

Hello, First of all thank you so much for the information. At 22:43 -0400 on 2014-5-15 Charles Lepple wrote: > > On May 15, 2014, at 9:39 PM, Stefan Bruda wrote: > > > What bugs be though is that I cannot seem to be able to read the > > remaining run time on battery. The battery charge is also widely > > inaccurate (it drops to zero really fast and stays

Hello Jeff, `upsstats` by itself only relays and renders the information provided by a NUT data server (upsd) and the NUT driver for the device. So you can revise the specific reported values with e.g. `upsc` command-line client to be sure. What I think happens here is that the driver uses a `battery.voltage.low/nominal/high` group of readings which does not match the hardware circumstances

Slightly OT, but I think this is of possible interest to many of you, I need to get a UPS for my asterisk box. They are rated in VA but I can't quite figure out how that converts to real life. I have a PIII-800 box with two X100P and one TDM400P plus graphics adapter, an IDE hard drive etc. Will a small 400VA box be enough for this? tia

On Oct 31, 2020, at 8:30 PM, Gene Heskett <gheskett at shentel.net> wrote: > >> battery.voltage: 16.0 > At that voltage, 5 of the 12 cells are shorted >> battery.voltage.nominal: 24 The 16.0 is a scaled version of the fixed (bogus) 24.0 V reading, similar to this unit: https://networkupstools.org/ddl/Cyber_Power_Systems/CP1500PFCLCD.html I think we even

Hi, Charles, On Wed, 2 May 2007 07:58:08 -0400, you wrote: > > Will that be enough to make it useable as a contribution? I believe > > the more sensible values for 36V UPS'es will be useful to other models > > than the one I have, too. > > Sounds good, but I don't think I saw it hit the list yet... I now have the following in megatec.c: static BatteryVolts

Hello, I am using Nut 2.8.0 (2.8.0-7 packages) Debian 'Bookworm' in it's Devuan form 'Daedalus'. When I look at my Eaton (ex-MGE Powerware) E5115 UPS boxes in NUT 'upsstats" I am confused by the battery readings. Under the 'System' column I can click on the link and obtain a GUI with a few meters. The NUT 'upsstats' battery voltage meter for these

On 16/02/14 00:38, Charles Lepple wrote: > On Feb 15, 2014, at 2:57 AM, Tim Dawson wrote: >> The driver will poll the UPS for what variables it supports when it starts, and then go into a polling loop. Look for a section defining the meter map, and you should see the result, as well as the raw data. > Tim: spot on. > > Greg, > > If you want, you can capture the -DDDD output

Hello, I own some Ablerex MARS 3000 (MS3000RT) UPS. Following the thread here : http://osdir.com/ml/monitoring.nut.user/2006-04/msg00091.html I would have the following issues : 1. The battery charge displayed seems wrong : It always shows 100.0 - even when the battery is disconnected for replacement. 2. Battery voltage 2.29 is also static ...and wrong. The initial assumption of being the voltage

I just got NUT 2.0.1 running on my Debian system at home.? I have a new CPS UPS connected via USB.? Everything is working fine, except the UPS is showing a value of 120% charged.? Any idea what causes this?? Here's the upsc output for my UPS: battery.charge: 120 battery.charge.low: 10 battery.charge.warning: 20 battery.runtime: 1320 battery.runtime.low: 300 battery.type: PbAcid

On May 15, 2014, at 9:39 PM, Stefan Bruda wrote: > What bugs be though is that I cannot seem to be able to read the > remaining run time on battery. The battery charge is also widely > inaccurate (it drops to zero really fast and stays there). I read > somewhere that the usb.debug numbers may hold the key to this (at > least to the running time that is), but I don't know what

On Feb 15, 2014, at 6:46 PM, Greg Vickers wrote: > Thanks! I've attached the file to this email (bcmxcp_usb.output2014160926.gz), it ran for 12 seconds, and looks like it's looping by that time. I'm not sure what to look for, does grepping for 'Yes' show the variables that the driver can pull off this UPS? The boolean variables seem to be indicated by "Yes". I

Hello, I own an older Tripp Lite SMART3000RM2U (protocol 3003). It does not work with usbhid-ups but it mostly works with the tripplite_usb driver (nut 2.7.1, the latest in the Gentoo tree), in the sense that the status (on line, on battery, etc.) is detected correctly, the machine is shut down on critical battery, and I can even get some information from the UPS. This is how it all looks: