Citeren ahouse-support supp...@ahouse.mine.nu:
There simply is no such functionality, or the driver can not read
these values because of nesovmestimoti / oschibki? Maybe a fix?
Read my reply again. The *UPS* doesn't report battery charge, so the
only thing NUT can do is guesstimate this
Citeren ahouse-support supp...@ahouse.mine.nu:
# ./nut start
Network UPS Tools - UPS driver controller 2.4.1
Network UPS Tools - Megatec/Q1 protocol serial driver 1.51 (2.4.1)
Supported UPS detected with megatec protocol
Vendor information read in 1 tries
Battery runtime will not be calculated
On 10/3/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I have in my possession a PowerWalker VI 1400, the big brother to the
NUT-supported VI 1000. It seems to work fairly well with the
megatec-driver, however there is one bigger problem and that is the
incorrect detection of battery.charge.
not
that familiar with the USB system.
Thanks
Michael Hill
[EMAIL PROTECTED]
-Original Message-
From: Charles Lepple [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 15, 2006 5:41 PM
To: Mike Hill
Cc: nut-upsuser@lists.alioth.debian.org
Subject: Re: [Nut-upsuser] (no subject)
On 11
Mike Hill wrote:
I have installed the NUT 2.0.3 RPM for Fedora Core 4 and I have it working
with an MGE Pulsar Evolution 500, but I cannot get the USB interface to
work.
When I plug in the USB cable I get the following message in my system log:
kernel: usbhid: probe of 2-1:1.0 failed
On 11/15/06, Mike Hill [EMAIL PROTECTED] wrote:
I have installed the NUT 2.0.3 RPM for Fedora Core 4 and I have it working
with an MGE Pulsar Evolution 500, but I cannot get the USB interface to
work.
When I plug in the USB cable I get the following message in my system log:
kernel: usbhid:
6 matches
Mail list logo