When I disconnect my UPS from the wall, I have to wait 15-30 seconds
before the USB drier 'polls' this information and tells me that the UPS is
on battery power (via knutclient or syslog via nut):
[EMAIL PROTECTED] POWER ALERT on Fri Jan 26 12:49:29 EST 2007
With a serial connection, I would
Hi all!
As I'm currently porting the HP PowerTrust driver from nut-1.4.3, I have
a question regarding ups.delay.*.
The PTs can delay the Shutdown/Restart and Kill commands by an arbitrary
number of seconds, i.e. they wait for n seconds and then shutdown or
kill. The delay for the restart after
When I disconnect my UPS from the wall, I have to wait 15-30 seconds
before the USB drier 'polls' this information and tells me that the UPS is
on battery power (via knutclient or syslog via nut):
[EMAIL PROTECTED] POWER ALERT on Fri Jan 26 12:49:29 EST 2007
With a serial connection, I
As I'm currently porting the HP PowerTrust driver from nut-1.4.3, I have
a question regarding ups.delay.*.
The PTs can delay the Shutdown/Restart and Kill commands by an arbitrary
number of seconds, i.e. they wait for n seconds and then shutdown or
kill. The delay for the restart after the
If you are using newhidups/usbhid-ups, the option -x pollfreq=value
can be used to set the polling frequency (or put pollfreq=value
into ups.conf). The default is 30 seconds.
-- Peter
Justin Piszcz wrote:
When I disconnect my UPS from the wall, I have to wait 15-30 seconds
before the USB
If I understood Markus correctly, the problem is not that the data
goes stale (it should do that when disconnecting the UPS
communications line), but that it goes unstale immediately afterwards
(even when the UPS is still disconnected).
This shouldn't really happen. Maybe some debugging is
On Sat, 27 Jan 2007, Peter Selinger wrote:
If you are using newhidups/usbhid-ups, the option -x pollfreq=value
can be used to set the polling frequency (or put pollfreq=value
into ups.conf). The default is 30 seconds.
-- Peter
Justin Piszcz wrote:
When I disconnect my UPS from
On 1/27/07, Arjen de Korte [EMAIL PROTECTED] wrote:
That depends on the driver you're using. If you're using the newhidups
driver (which will be renamed usbhid-ups in the next release), there is
probably not much you can do about this. Many USB protocols are *very*
verbose and don't allow
Peter Selinger wrote:
If I understood Markus correctly, the problem is not that the data
goes stale (it should do that when disconnecting the UPS
communications line), but that it goes unstale immediately afterwards
(even when the UPS is still disconnected).
That's entirely possible if he's
On Sat, 27 Jan 2007, Arjen de Korte wrote:
When I disconnect my UPS from the wall, I have to wait 15-30 seconds
before the USB drier 'polls' this information and tells me that the UPS is
on battery power (via knutclient or syslog via nut):
[EMAIL PROTECTED] POWER ALERT on Fri Jan 26
Yes, but he said 2.0.5 in the subject line. -- Peter
Arjen de Korte wrote:
Peter Selinger wrote:
If I understood Markus correctly, the problem is not that the data
goes stale (it should do that when disconnecting the UPS
communications line), but that it goes unstale immediately
Oooppss. Lets try with less data!
Peter,
Here is the line that I pruned out.
Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.1.0)
When I start the driver with
/usr/local/ups/bin/upsdrvctl -u nut start
I get the following messages
Network UPS Tools - UPS driver
Peter,
Looking at the data further down it has min and max values. These
would seem to make sense for voltage (0 250), frequency (0 60),
so is this data coming from the UPS, or is it just something in the
system that expects these values?
Regards
Jon
At 17:20 28/01/2007, Peter
Hi Jon,
I can't figure out which version of NUT you are running, because you
have pruned that information from your output. Also, which patches, if
any, have you applied?
What you are seeing from lsusb is not data from the UPS; it is
simply a detailed parsing of the report descriptor. For
No, it is all part of the report descriptor. A USB device might define
a variable called Voltage, whose units are Volts (and not, for
example, millivolts, kilovolts, ...) and which can take values in the
range 0...250. At this point, you have not read any actual voltage
from the UPS yet. The only
Peter,
I generated a new subdriver using the suggested method of running
./drivers/usbhid-ups - -u nut -x explore -x vendorid= auto /tmp/info
followed by pumping this into
./scripts/subdriver/path-to-subdriver.sh
Then make all, and make install . I don't get any error messages, I
16 matches
Mail list logo
