search for: voltages

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

Merry Christmas to you all and best wishes! I ran into exactly the same problem as described. OS: FreeBSD 9.0-Rel UPS: Eaton E-Series NV 600H NUT: from Ports, nut-2.6.5_1 driver: blazer_usb I am sure the problem is not permission-related as it occurs even when the driver runs as root. My tested recipe for USB permissions is: 1. run usbconfig to find where the device is connected. In my case:

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

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

Hi there I have a Mustek PowerMust 1000 USB using 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

Use the name from ups.conf in front of "@localhost". ?The re?sult is quite different ;) root at artu:~# upsc Elit at artu Init SSL without certificate database Error: Driver not connected > What if you try nutdrv_qx without specifying megatec? (It should > autodetect.) > ?Here is the result: ? root at artu:~# upsdrvctl start Network UPS Tools - UPS driver controller

...ar: FAILED max_bypass_volt: 264 max_bypass_volt, settable range: 231..276 min_bypass_volt: 110 min_bypass_volt, settable range: 110..209 max_bypass_freq: 64.0 max_bypass_freq, settable range: 61.0..64.0 min_bypass_freq: 56.0 min_bypass_freq, settable range: 56.0..59.0 No values for battery high/low voltages Using 'guesstimation' (low: 208.000000, high: 300.000000)! setvar(ups.delay.start, 60) setvar: SUCCEED setvar(ups.delay.shutdown, 12) setvar: SUCCEED battery.charge: 100 battery.packs: 1 battery.protection: yes battery.runtime: 600 battery.voltage: 272.9 battery.voltage.high: 300.00 battery...

...ar: FAILED max_bypass_volt: 264 max_bypass_volt, settable range: 231..276 min_bypass_volt: 110 min_bypass_volt, settable range: 110..209 max_bypass_freq: 64.0 max_bypass_freq, settable range: 61.0..64.0 min_bypass_freq: 56.0 min_bypass_freq, settable range: 56.0..59.0 No values for battery high/low voltages Using 'guesstimation' (low: 208.000000, high: 300.000000)! setvar(ups.delay.start, 60) setvar: SUCCEED setvar(ups.delay.shutdown, 12) setvar: SUCCEED battery.charge: 100 battery.packs: 1 battery.protection: yes battery.runtime: 600 battery.voltage: 272.9 battery.voltage.high: 300.00 battery...

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-3000 ups. Regarding of your

Hi, I've been using nut for a while on a UPS with the generic 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:

...VER 1.1 0.625000 send_to_all: SETINFO ups.mfr "ZIGOR" 0.625000 send_to_all: SETINFO ups.model "EBRO 650" 0.625000 send_to_all: SETINFO ups.firmware "VER 1.1" 0.625000 Vendor information read in 1 tries 0.625000 No values provided for battery high/low voltages in ups.conf 0.625000 send_to_all: SETINFO battery.voltage.low "10.40" 0.625000 send_to_all: SETINFO battery.voltage.high "13.00" 0.625000 Using 'guestimation' (low: 10.400000, high: 13.000000)! 0.625000 Battery runtime will not be calculated (runtimecal not...

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

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

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 unplugged, the input stays steady, and the _output_ voltage reports a drop to ~15V. OTOH, when the UPS is shutdown, the ordering appears correct, as the input stays steady, and the output shows...

Hello all, I have a CyberPower Systems CP850PFCLCD that I'm hooking up to NUT 2.4.3 from apt running under Ubuntu 10.04. Using the usbhid-ups driver, things *seem* to work at first glance, but there are some odd issues. The most notable issue is that the battery.charge indicator reads 120 when at full charge. I came across this post here:

Dear Mr Claesson, prepare for quite a long letter from me. I hope you will have time to read it. I bestowed a whole morning on trying to identify the correct upstype. Here are the results: root@marto:/home/marto# /usr/local/ups/bin/powercom -DD -u root -a Inform -x type=KP625AP Network UPS Tools - PowerCom and similars protocol UPS driver $ Revision: 0.5 $ (2.0.4) debug level is '2'

...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</OBJEC...

Hi, Need 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

Hi, One of my APC devices reports: "unacceptable utility voltage rate of change". I believe it has something to do with input voltage fluctuating too fast maybe even beneath or over the input voltage thresholds. Should I worry about this? should I measure input voltage? (I suppose I'd need more than multimeter readings. Maybe an oscilloscope or a multimeter that can record

...er.... ?root at artu:~# upsdrvctl start Network UPS Tools - UPS driver controller 2.7.2 Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2) Supported UPS detected with megatec protocol Rating information unavailable Vendor information unavailable No values provided for battery high/low voltages in ups.conf Using 'guestimation' (low: -0.866667, high: -1.083333)! Battery runtime will not be calculated (runtimecal not set) but root at artu:~# upsc Elit at artu Error: Connection failure: Connection refused Starting the driver with debug level 5 seems happier, but continue to cycle...