similar to: Fwd: Cyberpower usbhid-ups wrong battery voltage

HI all How to setup nut to use and monitor laptop battery on linux? (/proc/acpi/battery/BAT0/state) Emard

HI I would like to connect several Cyberpower Value 800E devices over a USB hub to a single host. Problem is how to distinguish them in order to correctly identify because lsusb -vvvv -d and upsc show the same device name and serial number is 0 Bus 002 Device 012: ID 0764:0501 Cyber Power System, Inc. idVendor 0x0764 Cyber Power System, Inc. idProduct 0x0501 bcdDevice

Hello! I am tracking the Development tree and I am trying to capture the output from newhidups, as such: [root]# newhidups -u root -DD -x generic -x vendorid=0001 auto > UPSdump.txt If I don't redirect the output to the .txt file, everything is printed on the screen. If I add the redirect, the output is again printed on the screen; the .txt file however only contains the first

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

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

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

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

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

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

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

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

Hi, everyone, I've recently bought a UPS from Mecer. This is a South African brand that basically resells Mustek hardware, and this UPS is no exception; it's a Mustek product. It does come with software for Linux, but that is terrible (the background process that monitors the UPS is written in Java and needs a terminal to start properly, so you can't run it from a startup script...

Hi, everyone, I've recently bought a UPS from Mecer. This is a South African brand that basically resells Mustek hardware, and this UPS is no exception; it's a Mustek product. It does come with software for Linux, but that is terrible (the background process that monitors the UPS is written in Java and needs a terminal to start properly, so you can't run it from a startup script...

If you have an FXS port and would like to attach a PSTN analog line to it this device would do the job by converting the FXS port to FXO. It's a small external device. Works well with VOIP FXS and other FXS interfaces. Interface: 2 RJ11 Jacks (one for the FXS port and one for the PSTN outlet.) Cost: $35.00 with USPS regular mail included. Power: 9 to 20V dc power supply (Not

nut 2.7.2 linux 3.18.7 CyberPower CP1350PFCLCD The LCD shows the same for input and output, my multimeter also matches the input voltage. But nut is giving me different numbers. How do I debug this? input.voltage: 122.0 output.voltage: 138.0 I still need to check what it does on battery and what the other readings are. But the voltage stuck out at me.

[please use reply-all to include the list. thanks!] > On Nov 26, 2015, at 9:47 AM, Weedy <weedy2887 at gmail.com> wrote: > > nut 2.7.2 > linux 3.18.7 > CyberPower CP1350PFCLCD > > The LCD shows the same for input and output, my multimeter also > matches the input voltage. > But nut is giving me different numbers. How do I debug this? > > input.voltage:

Hi Thomas, Le mercredi 02 juillet 2008 ? 18:52 +0200, Thomas Backman a ?crit : > Hey! I just bought my first UPS, a Cyberpower Value 600E, and set it > up using NUT 2.2.x (on Gentoo x86_64). Everything is working great, > using the usbhid-ups driver, and the UPS isn't on the compatibility > lists, so I figured I'd post a little heads-up that it works. The > battery

Dear Rod, thanks for writing. Good work! I am no longer an active NUT developer, so I am forwarding your message to the NUT developers list. NUT developers: probably this device can be added permanently. Also, should the MAINTAINERS file perhaps be replaced by a pointer to the mailing lists? It seems fairly outdated anyway. Cheers, -- Peter R. W. Rodolico wrote: > > I think I have the