similar to: Eaton-9130 (usbhid-ups) no battery.voltage parameter!

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

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

On Nov 10, 2014, at 11:00 PM, Valeri Linchevski <lincher at ya.ru> wrote: > So, how can I get this value? You could comment out the switch statements in drivers/mge-hid.c, functions mge_battery_voltage_nominal_fun() and mge_battery_voltage_fun(), and recompile. I logged an issue for fixing this the right way: https://github.com/networkupstools/nut/issues/170 -- Charles Lepple clepple

An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20141111/42cd1a34/attachment.html>

On Nov 10, 2014, at 9:10 AM, ??????? ?????????? <v.linch at icloud.com> wrote: > 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

An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20141111/7dd98eaa/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: usbhid.zip Type: application/zip Size: 5991 bytes Desc: not available URL:

On Nov 10, 2014, at 6:44 PM, Valeri Linchevski <lincher at ya.ru> wrote: > Parameter, "blabla" :-) really is Ups.PowerSummary.Voltage, debug output is in attach. > Apparently some models are missing from the table that is consulted for "mge_type": https://github.com/networkupstools/nut/blob/master/drivers/mge-hid.c#L201 Arnaud or Emilien, Is there any way we

The model should also work with the bcmxcp driver, but maybe that only works with serial, not usb. http://nutwiki.kanonbra.com/wiki/Category:Eaton_Powerware_9130 Alf Sent from my Cat? phone. Valeri Linchevski <lincher at ya.ru>:

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

I would also like to try and track down a possible off-by-10 bug in usbhid-ups (battery voltage on an MGE Pulsar Evolution, seen in the trunk in the last few weeks). If you are testing the shutdown stuff, it might be good to double-check the values you are seeing for voltages. I hadn't raised the issue on the list because I haven't had time to do the testing, but it's something to be

---------- Forwarded message ---------- From: davor emard <davoremard at gmail.com> Date: Tue, 25 Mar 2008 09:09:40 +0100 Subject: Cyberpower usbhid-ups wrong battery voltage To: libusb-devel at lists.sourceforge.net HI I have cyberpower value 800E connected via usb. In the status battery voltage is too high 20V - 21V while measurement at the battery terminals gives 13.6V -------------- next

Device Manufacturer: Eaton Device Name: 5S1500LCD ---------------------------------------------------------- upsc output: battery.charge: 100 battery.charge.low: 20 battery.runtime: 3515 battery.type: PbAc device.mfr: EATON device.model: Ellipse PRO 1500 device.serial: 0000000000 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2

Device Manufacturer: Eaton Device Name: 5S1500LCD ---------------------------------------------------------- upsc output: battery.charge: 100 battery.charge.low: 20 battery.runtime: 3515 battery.type: PbAc device.mfr: EATON device.model: Ellipse PRO 1500 device.serial: 0000000000 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2

Hi! I am not really experienced with UPS devices or UPS control software like NUT but i am enthusiastic and trying to use Eaton-9130 (it has one extra EBM too) as rationally as possible with NUT. I believe in general things are under control and behave, although i have some glitches and i would like to ask for help. I am using Debian v. 7 amd64 and from its packages nut-server and nut-client, v.

Hello, In trying to minimize the margin on the left hand side when using dotchart I found what may be a typo in the code. In the lines below from dotchart.R, should nmai[4L] be nmai[2L]? if (!(is.null(labels) && is.null(glabels))) { nmai <- par("mai") nmai[2L] <- nmai[4L] + max(linch + goffset, ginch) + 0.1 par(mai = nmai) } Thank you, Stephen Weigand --

Hi, I have also posted this on GitHub but it isn?t clear that was the right place: https://github.com/WayneD/rsync/issues/522 iCloud Drive will evict files that are unused or when additional space is needed on the local drive. The evicted files are replace by "bookmark" files that allow MacOS to continue to report the files in the file system as though they were actually present. The

Problem: neither fg or bg nor color work properly in dotchart. version: R-1.7.1 for windows code which shows the errors: x <- matrix(rnorm(16),ncol=2,dimnames=list(paste("a",1:8,sep=""),c("before","afte r"))) dotchart(x,fg="blue",bg="lightgrey") dotchart(x,color=c("red","blue")) Dr Ian J Wilson Lecturer in

Ubuntu 8.04 Nut : Version: 2.2.1-2.1ubuntu7.2 Hello, I choose the megatec driver and I connect through a serial cable. I receive a "This UPS has an unsupported combination of battery voltage/number of batteries" message. I know this is not an error but I don't really what I have to do next. Here is the result of /lib/nut/megatec -a infosec -DDD debug level is '3'

For my Smart 2200, a charged battery string is anywhere between 25.6 and 26.8 volts. I'm seeing nut report 13.0 volts, which seems suspicious. Even if the UPS were reporting half of the actual battery voltage to keep protocol compatibility with models having a 12V battery system, the value of exactly 13.0 seems unlikely. According to the page at

That makes sense to me. The field needs to be split into bytes. The low byte is the integer part of voltags, and the high part is units of 10 mV. And this is per cell. Probably the unit is measuring the total and then dividing by 36. But volts per cell will have the same interpretation for varying cell counts, so it's a nice representation.