search for: voltag

Shamelessly reusing the announcement Arnaud sent about three months ago for nut-2.2.1: "We're preparing to release 2.2.1-pre2, so if you have some fixes to backport on Testing, consider announcing it and doing asap. As always, compatibilities update and bugfixes only!" Regards, Arjen -- Eindhoven - The Netherlands Key fingerprint - 66 4E 03 2C 9D B5 CB 9B 7A FE 7E C1

....4 020 49.8 13.6 25.0 00001001 2517.292407 send: Unknown error 2517.292518 Permissions problem: Input/output error # /usr/local/libexec/nut/blazer_usb -DDDDD -a eaton -u root ... 1451.821772 read: (221.5 221.0 221.0 019 49.8 13.6 25.0 00001001 1451.821797 send_to_all: SETINFO input.voltage "221.5" 1451.821805 send_to_all: SETINFO input.voltage.fault "221.0" 1451.821813 send_to_all: SETINFO ups.load "19" 1453.573762 send: Q1 1453.837774 read: (217.1 217.1 217.6 020 49.8 13.6 25.0 00001001 1453.837800 send_to_all: SETINFO input.voltage...

...d by F command. When power is lost, the 2.27V drops very quickly to 2.06V 2.06V x 6 = 12.36V Which seems to be correct for a 12V battery. To top it up, I command returns an empty string, which would help "a lot" to identify it. OK, my questions are: 1) Is 2.27V plausible for battery voltage or should it be 13,62V? 2) Is 240V plausible for battey nominal voltage or should it be 12V? 3) Wich can I consider battery full? 2.27V or 2.06V? 4) Any tips to solve this problem? Divide and multiply inside megatec driver? Is there any chance to some UPS hacks in megatec driver (parameters in co...

John Ackermann N8UR via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> writes: > I am monitoring via the SNMP driver an APC SmartUPS that has split > phase (2L + neutral) 240V input and 120/120 volt outputs. The data > for the voltages is not what I'm expecting, and I am wondering how I > should interpret it. Wow, that sounds kind of industrial. Model? Is the input an L14-20P? Or equivalent non-twistlock? > Here is an example from upsc: > > input.L1-L2.voltage: 121 > input.L2-L3.voltage: 120 > input.v...

Hello, I have just installed nut_2.6.0 from Debian testing, do anyone know the correct driver for this ups? The blazer_usb don't report battery-charge, the bundled software report charge and runtime. root at pluto<~>upsc powerwalker battery.voltage: 40.86 battery.voltage.nominal: 36.0 beeper.status: enabled device.mfr: device.model: HV 1K device.type: ups driver.name: blazer_usb driver.parameter.pollinterval: 2 driver.parameter.port: /dev/bus/usb/007/002 driver.version: 2.6.0 driver.version.internal: 0.03 input.current.nominal: 4.0 input.fre...

...ng serial port /dev/ttyS0. I use nut 2.2.1 with the megatec driver on Debian Lenny (testing), running on an AMD64 X2. (I was using a Debian Etch as slave, but to keep it simple I turned it off) My problem is that sometimes the UPS is running OK, but when the message "UPS is trimming incoming voltage" appears on knutclient (i.e. OL TRIM in nut), I have something like Input Voltage 241.1 Output Voltage 202.0 nominal 220.0 ??? This output voltage is too low! I think power spikes may be better than using this voltage. I don't know if the problem is the UPS or from communication wi...

...Trying to match device 0.561473 Device matches 0.565355 send_to_all: SETINFO ups.vendorid "ffff" 0.565815 send_to_all: SETINFO ups.productid "0000" 0.566137 send: QGS 0.566421 read: QGS 0.566708 qx_process_answer: short reply (input.voltage) 0.567007 send: QGS 0.567377 read: QGS 0.567668 qx_process_answer: short reply (input.voltage) 0.567965 send: QGS 0.568256 read: QGS 0.568609 qx_process_answer: short reply (input.voltage) 0.568952 send: M 0.569310 read: M 0.569498 vol...

...<nut-upsuser at alioth-lists.debian.net> > > Cheers, > > One PR waiting to get into 2.8.1 release timeframe is https://github.com/networkupstools/nut/pull/1652 stemming from issue https://github.com/networkupstools/nut/issues/1279 > > The gist of it is that "battery.voltage" and "battery.charge" were not always reported correctly with nutdrv-qx driver (might be handled better by blazer drivers though), and the overrides tried by issue posters did not help them with original state of NUT codebase. I tried it on three ups: 10kv online, 3kv online, 2kv o...

...<nut-upsuser at alioth-lists.debian.net> > > Cheers, > > One PR waiting to get into 2.8.1 release timeframe is https://github.com/networkupstools/nut/pull/1652 stemming from issue https://github.com/networkupstools/nut/issues/1279 > > The gist of it is that "battery.voltage" and "battery.charge" were not always reported correctly with nutdrv-qx driver (might be handled better by blazer drivers though), and the overrides tried by issue posters did not help them with original state of NUT codebase. I tried it on three ups: 10kv online, 3kv online, 2kv o...

Hello! I left this line uncommented in powercom-hid.c for battery voltage: { "battery.voltage", 0, 0, "UPS.Battery.Voltage", NULL, "%.2f", 0, NULL }, and got some data different from the input voltage values The Powercom support staff gave the following response to my question: Dear Alex, First of all , thank you for purchasing PCM MRT-30...

...eneric driver. It has worked well. Thankyou. I've just installed a new UPS 'INVERTER Atlantic Star T3' and their documentation speaks of megatec. So I tried it. And I get lots of wonderful information I'm not used to seeing. # upsc my_sai at localhost battery.charge: 100.0 battery.voltage: 2.31 battery.voltage.nominal: 96.0 driver.name: megatec driver.parameter.port: /dev/ttyS0 driver.version: 2.0.4 driver.version.internal: 1.4 input.frequency: 49.9 input.voltage: 229.0 input.voltage.fault: 229.0 input.voltage.maximum: 230.4 input.voltage.minimum: 224.9 output.voltage: 220.8 output...

...iver.version.internal "0.09" 0.031250 send_to_all: SETINFO driver.name "blazer_usb" 0.031250 Trying megatec protocol... 0.031250 send: Q1 0.312500 received 96 (96) 0.312500 read: (231.0 165.0 231.0 024 50.0 13.6 00.0 00001000 0.312500 send_to_all: SETINFO input.voltage "231.0" 0.312500 send_to_all: SETINFO input.voltage.fault "165.0" 0.312500 send_to_all: SETINFO output.voltage "231.0" 0.312500 send_to_all: SETINFO ups.load "24" 0.312500 send_to_all: SETINFO input.frequency "50.0" 0.312500 send_to_...

Hi All, I have what is probably a 12 year old (or older) Compaq R3000 UPS plugged into a FreeBSD 8 system running NUT version 2.6.5 This UPS contains a total of 16 batteries in 2 banks of 8, each battery is 6 volts and the bank produces 50 volts. The UPS monitors battery voltage and the battery charger in the UPS works like this. For about 2 days it will apply a charge/float/topping voltage of 55.2 volts to the batteries. During that time the battery voltage measures 55.2 volts both with a voltmeter on the batteries and as reported by upsc, and the "calculated state...

I suspect that the battery is failing on my Pulsar Evolution 500 (it is several years old now) but I can't seem to get a valid battery voltage from the UPS. The following tests were done using NUT 2.2.1, but I first noticed this with the trunk, and reproduced it with the current branches/Testing as well. The only two values I have seen for battery.voltage are 120.0 and 119.0, e.g.: $ upsc evo | grep battery # full upsc output att...

While fundamentally working, I'm having a few issues with the driver... The default voltage quads (for every model) are way off... Showing ~95v when it should be ~117V. I've changed the 4th/final coefficient to +5.0, but haven't tested extensively (with fluctuating voltages). The input/output voltage appears to be swapped _most of the time_. When doing a battery test, or when...

...he UPS from the outlet during that debug or not. Thanks in advance for any help, Justin ------------ ue Mar 29 23:30:39 CDT 2011 battery.charge: 120 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 450 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 16.0 battery.voltage.nominal: 24 device.mfr: CP850PFCLCD device.model: CRDA103.981 device.serial: CPS device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.4.3 driver.version.data: CyberPower HID 0.3 d...

Hi -- I am monitoring via the SNMP driver an APC SmartUPS that has split phase (2L + neutral) 240V input and 120/120 volt outputs. The data for the voltages is not what I'm expecting, and I am wondering how I should interpret it. Here is an example from upsc: input.L1-L2.voltage: 121 input.L2-L3.voltage: 120 input.voltage: 121.20 output.current: 5.90 output.L1-L2.voltage: 119 output.L1.current: 5.90 output.L2-L3.voltage: 119 output.L2.current:...

...form -x type=KP625AP Network UPS Tools - PowerCom and similars protocol UPS driver $ Revision: 0.5 $ (2.0.4) debug level is '2' Values of arguments: manufacturer : 'PowerCom' model name : 'Unknown' serial number : 'Unknown' line voltage : '220' type : 'KP625AP' number of bytes from UPS: '16' method of flow control : 'dtr0rts1' validation sequence: '{{5,0x80},{7,0},{8,0}}' shutdown arguments: '{{1,0},y}' frequency calculation coefficients: '{0...

...to fix it. Now local representative sent me an MGE "Pulsar Extreme 2000 VA" model in order to find an alternative way to poll our two "Galaxy 5000 UPS" units. I started the tests with netxml-ups driver. The very first thing I noticed that upsc reports 1/10th of input/output AC voltages. Raw HTTP stream: [...] <OBJECT name='UPS.PowerConverter.Output.Phase[1].ActivePower'>0</OBJECT> <OBJECT name='UPS.PowerConverter.Output.Phase[1].ApparentPower'>0</OBJECT> <OBJECT name='UPS.PowerConverter.Input[2].Phase[11].Voltage'>0</OBJ...

...eed to get an answer to the following. I find the naming to be little redundant regarding the 'input.transfer.boost.low - hige'. The same goes for input.transfer.trim.low - high. As I find it, there is only one point where the boost or buck (trim) kicks in. Let's say that the nominal voltage is 230 volt, then we have a input.transfer.boost point on say 220 volt. If the voltage drop any more, it reach the 'input.transfer.low', when it would go to battery. The same goes for buck (trim). Like this. input.transfer.high: 255 Volt (Go on battery over that voltage) input.transfer....