similar to: Where are usbhid-ups driver parameters defined - and what do some of them mean?

For various reasons - I have been trying to get my Desktops and/or servers to shut-down a fixed time after a power fail - or better still a fixed time - or a low battery whichever comes first. I note in my upsc: *> upsc belkinusb* battery.charge: 100 battery.charge.low: 30 battery.charge.warning: 30 battery.runtime: 120 battery.type: PbAc battery.voltage: 27.3 battery.voltage.nominal: 24

[updated] OpenBSD 6.1/amd64 NUT 2.7.4p0 (from OpenBSD package) Results of upsc: battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 2902 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 26.9 battery.voltage.nominal: 24 device.mfr: CPS device.model: CP1500AVRLCDa device.serial: CTHGN200xxxx device.type: ups driver.name:

Hi, thanks for your helpful reply. I've added the productid in the ups.conf and it seems to work (better) now. > After starting the driver and upsd, what does "upsc ups" return? If you can also include "upsrw ups" and "upscmd -l ups" output, we can update the DDL. #upsc ups Init SSL without certificate database battery.charge: 100 battery.charge.low: 20

I have just installed Centos 5.0 from DVD. I have also run the software updates and I think everything is up to date. The motherboard is a Gigabyte GA945GM-S2 with an Intel E2140 processor. At boot time if I select show details - there is one error shown "in red", Like this: Applying Intel CPU microcode update. FATAL: Module microcode not found. ERROR: Module microcode does not exist

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

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

CyberPower OR700LCDRM1U (http://www.cyberpowersystems.com/products/ups-systems/smart-app-ups/rackmount-lcd/OR700LCDRM1U.html) upsc output: battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 6000 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 14.5 battery.voltage.nominal: 12 device.mfr: CPS device.model: UPS OR700

Hi all. I've installed latest NUT under Windows XP, all works fine, but when I run "upsc ups" command I don't see the battery.voltage parameter, which I most need. Please help, where am I wrong? --- Valeri Linchevski

CyberPower Systems PR6000LCDRTXL5U http://www.cyberpowersystems.com/products/ups-systems/smart-app-ups/pp-series/PR6000LCDRTXL5U.html I had to create the following udev rule (on RHEL6): ATTR{idVendor}=="0764", ATTR{idProduct}=="0601", MODE="664", GROUP="dialout" Shutdown testing successful. UPS comes back online after turning off. # upsc battery.charge:

On Nov 9, 2014, at 9:35 AM, ??????? ?????????? <v.linch at icloud.com> wrote: > I've installed latest NUT under Windows XP, all works fine, but when I run "upsc ups" command I don't see the battery.voltage parameter, which I most need. Can you provide a few more details? The latest version of NUT (2.7.2 at the moment) has not been ported to Windows. Also, what does

The meter map is basically a bitmap that indicates what variables are output (and in what format) by the UPS. You will likely see a variable, 'not mapped' or nothing. The variables and 'not mapped' items are output by the UPS in the measurement block, and the map tells nut how to read it. 'Unmapped' means that there is a variable there that nut is ignoring, and the xcp

Hi all, I've finally gotten around to setting up the netbook that controls my UPS and I would like to make sure that I've got the metacode correct before configuring nut :) Here's what I've got: Belkin UPS F6C120auUNV * Batteries recently replaced * On battery: 24 port switch, PoE AP, antenna power booster, ADSL modem, MythTV server, 19" monitor * On surge

Hello, we have a Emerson Liebert GXT4, that we like to connect to our servers to shut them down if there is a power failure (which happens quite often in our area). I couldn't get the GXT4 working with usbhid-ups driver. So I need some advise to continue to get this device working. The GXT3 seems to be working ok with NUT (http://networkupstools.org/ddl/Liebert/GXT3.html). Here is my

Hello Charles, Thank you so much for your help. Just run upsc and it is possible that input.transfer.low is the one because we used power regulator to bring down the power around 84v and then the ups sent the power loss message to PC. Do you think some others may take effect for the low voltage? Just have the upsc result attached. Then I retried input.transfer.low, default.input.transfer.low,

My windows version is 2.6.5-3, latest on NUT site. "upsc ups" shows many ups parameters such as ups.load, battery.charge etc. but there is no battery.voltage, which I need (ups - is the name of my device in config). If I load driver usbhid-ups in debug mode (-DD), I see something like Ups.summary.bla-bla (sorry, don't remember exactly it's name) parameter with the value, which

UPS - CYBERPOWER CPS DX600E upsc usb at localhost battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 1650 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 4.8 battery.voltage.nominal: 12 device.mfr: CPS device.model: DX600E device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2

Hello Charles, Thank you so much for your reply. Yes. 40v was too low. In windows, those range started from 76v, 85v, and 96v. Just tried upsrw command to modify input.transfer.low and input.transfer.boost.low. There were some error messages returned. Tried another one battery.charge.low and it returns ok. $ sudo upsrw -s input.transfer.low=70 -u * -p * ups Unexpected response from upsd: ERR

is there a way to override the productid (like -x productid=1234) when using newhidups? just thought i'd try it with the F6C1500-TW-RK over usb. i was able to get hidups to work using the below settings, but it provides limited information. my ups.conf entry: [belkin] driver = hidups port = /dev/usb/hiddev0 and the output of upsc: gateway:/etc/nut# upsc

Tripp Lite SMART1300LCDT # upsc ups battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 30 battery.runtime: 2951 battery.type: PbAC battery.voltage: 0.0 battery.voltage.nominal: 24.0 device.mfr: Tripp Lite device.model: TRIPP LITE UPS device.serial: 2250AVLSM872100251 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2

Hi there, my HP R1500 G3 UPS doesn't apply my battery.charge.low value i set via upsrw. Is this a common problem with this model in nut 2.6.4? Any ideas how to force the UPS to accept this value? Regards Jan % upsc hp1500 battery.charge: 100 battery.charge.low: 20 battery.charge.warning: 20 battery.runtime: 23917 battery.temperature: 49.0 battery.type: PbAc battery.voltage: 39.0