Quote:
RTFM - 'man 8 blazer'.
Yes, yes!! im undestend and study the man!! snx!!
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
On Thursday, December 02, 2010 04:36:43 pm John Bayly did opine:
> On 02/12/2010 15:28, Gene Heskett wrote:
> > On Thursday, December 02, 2010 10:05:54 am Arjen de Korte did opine:
> >> Citeren Arnaud Quette:
> Thanks for the suggestions, I've added the flush statement as well
> as some
Citeren ahouse-support :
# ./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 (runtimecal not set)
I am have a nice result whith blazer_ser driver! respect!
# ./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 ca
Citeren ahouse-support :
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 based on other values it
There simply is no such functionality, or the driver can not read these
values because of nesovmestimoti / oschibki? Maybe a fix? And whether
further use of the NUT, so that my UPS shut off my server connected to it?
___
Nut-upsuser mailing list
Nut-u
Citeren ahouse-support :
I have a traoble whith my ups, - megatec driver can not calculating
% of charging and voltage on battery:
You UPS doesn't report the battery charge, so that's not unusual. The
megatec driver will guesstimate the battery charge based on the
battery voltage, but thi
On 02/12/2010 15:28, Gene Heskett wrote:
On Thursday, December 02, 2010 10:05:54 am Arjen de Korte did opine:
Citeren Arnaud Quette:
Thanks for the suggestions, I've added the flush statement as well as
some debugging information. As this is a intermittent issue I
decided to try overloading th
Hi All!
I have a traoble whith my ups, - megatec driver can not calculating % of
charging and voltage on battery:
# uname -a
FreeBSD backup.*.*.* 8.1-RELEASE FreeBSD 8.1-RELEASE #0: Wed Sep 22
12:25:01 EEST 2010
ups.conf
[Powercom]
driver = megatec
port = /dev/cuau0
#battvolts=12:24
desc
On Thursday, December 02, 2010 10:05:54 am Arjen de Korte did opine:
> Citeren Arnaud Quette :
> >> Thanks for the suggestions, I've added the flush statement as well as
> >> some debugging information. As this is a intermittent issue I
> >> decided to try overloading the UPS by sending it repeate
On 02/12/2010 10:54, Arjen de Korte wrote:
Citeren John Bayly :
Last but not least, in most drivers, we allow a couple of missed
replies before we call dstate_datastale() so that glitches don't
lead to automatic reconnects.
Can you suggest what driver would be a good template to use?
Take a
Citeren John Bayly :
Last but not least, in most drivers, we allow a couple of missed
replies before we call dstate_datastale() so that glitches don't
lead to automatic reconnects.
Can you suggest what driver would be a good template to use?
Take a look at the upsdrv_updateinfo() function
On 02/12/2010 10:08, Arjen de Korte wrote:
Citeren Arnaud Quette :
Thanks for the suggestions, I've added the flush statement as well
as some
debugging information. As this is a intermittent issue I decided to try
overloading the UPS by sending it repeated beeper commands while
watching
the d
Citeren Arnaud Quette :
Thanks for the suggestions, I've added the flush statement as well as some
debugging information. As this is a intermittent issue I decided to try
overloading the UPS by sending it repeated beeper commands while watching
the debug output. What appears to happen is that th
2010/12/1 John Bayly
> On 01/12/2010 14:17, Arjen de Korte wrote:
>
>> Citeren Charles Lepple :
>>
>> The get_belkin_reply() function looks fragile to me. Three seconds should
>>> be
>>> enough to fill the buffer, but if you put a few upsdebugx() calls around
>>> ser_get_buf_len(), it should be
15 matches
Mail list logo
