[Nut-upsuser] (no subject)

[Andrea de Lutti]

2017-07-05 13:32 GMT+02:00 Charles Lepple :

> On Jul 5, 2017, at 7:05 AM, Andrea de Lutti  wrote:
> >
> > Which are the ups.status I can use with ups in dummy mode?
> > I have seen only OB, LB, OL...
> >
> Those are the ones that upsmon will respond to. The dummy-ups driver
> accepts any string, AFAIK.
>
> Others: http://networkupstools.org/docs/developer-guide.chunked/
> ar01s04.html#_manipulating_the_data
> ___
>

​What if I would like to implement a notification for [OL CAL] status
during battery calibration?​
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

[Nut-upsuser] (no subject)

[Will Sutton]

I am working with a Middle Atlantic IP controllable UPS. I have found that
it is made by CyberPower and is controlled via SNMP. There are some
controls using the auto SNMP driver that do not show up with uspcmd -l
$UPSNAME. Is there a way to use a manufacturer supplied .mib file to
control this piece?
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser

[Nut-upsuser] (no subject)

[ahouse-support]

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-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] (no subject)

[Arjen de Korte]

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 based on other values it  
reports.


And whether further use of the NUT, so that my UPS shut off my  
server connected to it?


Read the documentation. Both the megatec and blazer_ser driver support this.

Best regards, Arjen
--
Please keep list traffic on the list (off-list replies will be rejected)


___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser

[Nut-upsuser] (no subject)

[ahouse-support]

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 calculated (runtimecal not set) 
= !!!

Starting nut.
Network UPS Tools upsd 2.4.1
listening on 172.16.0.220 port 3493
listening on 127.0.0.1 port 3493
Connected to UPS [Powercom]: blazer_ser-Powercom

backup# upsc power...@localhost
battery.voltage: 28.80 = !!! it is a normal? what u thing about 
this value??  iam have 4x7AH battery in Ups

battery.voltage.nominal: 24.0
beeper.status: disabled
driver.name: blazer_ser
driver.parameter.pollinterval: 2
driver.parameter.port: /dev/cuau0
driver.version: 2.4.1
driver.version.internal: 1.51
input.current.nominal: 5.0
input.frequency: 50.0
input.frequency.nominal: 50
input.voltage: 237.0
input.voltage.fault: 237.0
input.voltage.nominal: 220
output.voltage: 237.0
ups.delay.shutdown: 30
ups.delay.start: 180
ups.firmware: LCD  V2.1
ups.load: 74
ups.mfg: POWERCOM
ups.model: RXL-1000
ups.status: OL
ups.temperature: 0.0
ups.type: online

Broadcast Message from ***
   (no tty) at 22:42 EET...

Communications with UPS power...@localhost established

im come back after learning you Tools!! thx! 



___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] (no subject)

[Arjen de Korte]

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 (runtimecal not set)  
= !!!


RTFM - 'man 8 blazer'.


backup# upsc power...@localhost
battery.voltage: 28.80 = !!! it is a normal? what u thing  
about this value??  iam have 4x7AH battery in Ups


This boils down to about 2.4 V / cell, which is fairly high for a PbAc  
battery. But please understand that a UPS is not a measuring  
instrument. More often than not, the reported resolution is much more  
than the accuracy of the measurement justifies. So unless your  
batteries wear out quickly, you can safely ignore this.


Best regards, Arjen
--
Please keep list traffic on the list (off-list replies will be rejected)


___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser

[Nut-upsuser] (no subject)

[ahouse-support]

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

[Nut-upsuser] (no subject)

[terrypowling]

http://vixefidi.t35.com/


  

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser

[Nut-upsuser] (no subject)

[cooleyr]

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser

[Nut-upsuser] (no subject)

[cooleyr]

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser

[Nut-upsuser] (no subject)

[Lelsie Rhorer]

Gentlemen,

    I am running a Tripp Lite OMNISV1500XL under NUT using the
tripplite_usb driver on a Debian Lenny Linux system.  The platform is an
AMD Athlon 64 x 2 processor running kernel 2.6.26.  The driver is up and
running, but there are several issues.

    First, the system drops communications with the UPS regularly -
typically 2 or three times an hour.  I've worked around this by running a
script which checks every few seconds to make sure the UPS driver is
on-line, and if not restarts NUT.  I do not observe this behavior when I
boot Windows XP Pro 64 on the system.

    Secondly, the reported voltages are all incorrect.  I measured
them with an accurate voltmeter, and the Input Voltage is typically around
120V, the Output Voltage is 122V, and the Battery Voltage at full charge is
26V.  Running under Windows, the system confirms these values.  Under the
Linux driver, however, the system is reporting an Input Voltage of around
113V, an Output Voltage of 114V, and a fully charged Battery Voltage of
14.6V.



___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser

[Nut-upsuser] (no subject)

[tanelr]

Hello,

let me first say that I do not have much experience with mailing
lists, so I hope you can overlook any faults I might do in this
process, nor is English my mother language.

Secondly, I would like to thank all the developers of NUT, it truly is
a great package of software and has made life easier for many of us.

As I've understood the upsuser-list is also frequently read by the
devs so I choose to write about the problem on this list.

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. This causes the UPS send the OB
LB flag at - according to NUT - 43% of battery.charge, however the
real charge at this point is closer to ~25%. A powerloss is inevitable
when there is - again, according to NUT - 17% left in the
battery.charge. I haven't tried the dev-tree but since megatec.c in
the dev-tree is identical to the megatec.c in nut-2.2.1-pre1 I assume
the problem is still around.

What I hope to achieve with this mail is to bring forth the existence
of this problem, and if you already know about it, get some
confirmation on if it's being worked on and what I can do to help (my
C is very very limited so I can't really do anything about the code
myself, and as I'm a poor student I don't have any economical
resources to help with either).

Thanks in advance!

All the best,
Tanel Rebane

upsc:
battery.charge: 92.5
battery.voltage: 26.20
battery.voltage.nominal: 12.0
driver.name: megatec
driver.parameter.port: /dev/cuad0
driver.version: 2.0.5
driver.version.internal: 1.5
input.frequency: 50.1
input.voltage: 233.2
input.voltage.fault: 233.2
input.voltage.maximum: 233.3
input.voltage.minimum: 231.2
output.voltage: 227.4
output.voltage.nominal: 230.0
ups.beeper.status: enabled
ups.delay.shutdown: 0
ups.delay.start: 2
ups.load: 27.0
ups.mfr: unknown
ups.model: unknown
ups.serial: unknown
ups.status: OL
ups.temperature: 25.0

ups.log updated every 5 sec (every second line removed for space save):
20071003 152603 100.0 233.2 36.0 [OL] 25.0 50.1
20071003 152613 100.0 233.3 27.0 [OL] 25.0 50.1
20071003 152623 75.0 7.7 42.0 [OB] 25.0 50.1
20071003 152633 72.5 7.7 42.0 [OB] 25.0 50.1
20071003 152643 71.3 7.7 42.0 [OB] 25.0 50.1
20071003 152653 70.0 7.7 42.0 [OB] 25.0 50.1
20071003 152703 70.0 7.7 43.0 [OB] 25.0 50.1
20071003 152713 70.0 7.7 42.0 [OB] 25.0 50.1
20071003 152723 70.0 7.7 42.0 [OB] 25.0 50.1
20071003 152733 68.8 7.7 42.0 [OB] 25.0 50.1
20071003 152743 68.8 7.7 42.0 [OB] 25.0 50.1
20071003 152753 68.8 7.7 42.0 [OB] 25.0 50.1
20071003 152803 67.5 7.7 42.0 [OB] 25.0 50.1
20071003 152813 67.5 7.7 42.0 [OB] 25.0 50.1
20071003 152823 67.5 7.7 43.0 [OB] 25.0 50.1
20071003 152833 66.3 7.7 41.0 [OB] 25.0 50.1
20071003 152843 66.3 7.7 42.0 [OB] 25.0 50.1
20071003 152853 65.0 7.7 43.0 [OB] 25.0 50.1
20071003 152903 65.0 7.7 41.0 [OB] 25.0 50.1
20071003 152913 62.5 7.7 42.0 [OB] 25.0 50.1
20071003 152923 62.5 7.7 44.0 [OB] 25.0 50.1
20071003 152933 61.3 7.7 42.0 [OB] 25.0 50.1
20071003 152943 60.0 7.7 42.0 [OB] 25.0 50.1
20071003 152953 55.0 7.7 42.0 [OB] 25.0 50.1
20071003 153003 53.8 7.7 44.0 [OB] 25.0 50.1
20071003 153013 52.5 7.7 42.0 [OB] 25.0 50.1
20071003 153023 51.3 7.7 42.0 [OB] 25.0 50.1
20071003 153033 50.0 7.8 41.0 [OB] 25.0 50.1
20071003 153043 47.5 7.7 41.0 [OB] 25.0 50.1
20071003 153053 46.3 7.7 44.0 [OB] 25.0 50.1
20071003 153103 46.3 7.7 41.0 [OB] 25.0 50.1
20071003 153113 45.0 7.7 43.0 [OB] 25.0 50.1
20071003 153123 45.0 7.7 39.0 [OB] 25.0 50.1
20071003 153133 41.3 7.7 43.0 [OB] 25.0 50.1
20071003 153143 41.3 7.7 44.0 [OB LB] 25.0 50.1
20071003 153153 37.5 7.7 43.0 [OB LB] 25.0 50.1
20071003 153203 37.5 7.7 42.0 [OB LB] 25.0 50.1
... it continues but the last part is lost due to the shutdowns


___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] (no subject)

[Carlos Rodrigues]

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. This causes the UPS send the OB
 LB flag at - according to NUT - 43% of battery.charge, however the
 real charge at this point is closer to ~25%. A powerloss is inevitable
 when there is - again, according to NUT - 17% left in the
 battery.charge. I haven't tried the dev-tree but since megatec.c in
 the dev-tree is identical to the megatec.c in nut-2.2.1-pre1 I assume
 the problem is still around.

From NUT 2.2.0 onwards, the megatec driver supports an option named
battvolts in ups.conf, in which one specified the battery.voltage
reported by the UPS when discharged (just before it turns itself off,
not when it triggers a low battery event), and the voltage when the
UPS is full. For example...

battvolts = 20:26.2

...would mean battery.voltage: 20 when almost completely discharged
and battery.voltage: 26.2 when fully charged.

The value you are obtaining for battery.charge is just a best effort
value based on data obtained from other models. If that value is
incorrect, the only way to set it straight is to use the battvolts
option.

-- 
Carlos Rodrigues

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser

RE: [Nut-upsuser] (no subject)

[Mike Hill]

I tried to run newhidups myself with the debugging messages turned on and I
got the following response:

debug level is '4'
Checking device (/) (003/001)
- VendorID: 
- ProductID: 
- Manufacturer: unknown
- Product: unknown
- Serial Number: unknown
- Bus: 003
Trying to match device
Device does not match - skipping
Checking device (0463/) (002/002)
- VendorID: 0463
- ProductID: 
- Manufacturer: unknown
- Product: unknown
- Serial Number: unknown
- Bus: 002
Trying to match device
Device matches
failed to claim USB device, trying 2 more time(s)...
detaching kernel driver from USB device...
failed to detach kernel driver from USB device...
trying again to claim USB device...
failed to claim USB device, trying 1 more time(s)...
detaching kernel driver from USB device...
failed to detach kernel driver from USB device...
trying again to claim USB device...
failed to claim USB device, trying 0 more time(s)...
detaching kernel driver from USB device...
failed to detach kernel driver from USB device...
trying again to claim USB device...
Unable to get HID descriptor (error sending control message: Operation not
permitted)
Checking device (/) (002/001)
- VendorID: 
- ProductID: 
- Manufacturer: unknown
- Product: unknown
- Serial Number: unknown
- Bus: 002
Trying to match device
Device does not match - skipping
Checking device (/) (001/001)
- VendorID: 
- ProductID: 
- Manufacturer: unknown
- Product: unknown
- Serial Number: unknown
- Bus: 001
Trying to match device
Device does not match - skipping
No appropriate HID device found
Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.3)

No matching USB/HID UPS found



It seems like the kernel might already have a driver loaded, but I am 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/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: probe of 2-1:1.0 failed with error -5

actually, this part is normal. The device is blacklisted from the kernel
usbhid driver so that it can be claimed in userspace by newhidups.

Did you see any error messages from the driver or other NUT components?

-- 
- Charles Lepple


___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser

[Nut-upsuser] (no subject)

[Mike Hill]

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 with error -5

Any ideas?

Thanks

Mike


___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] (no subject)

[Arjen de Korte]

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 with error -5
 
 Any ideas?

If you want to use USB with NUT, you need to install the latest
development version. The newhidups driver is very much 'work in
progress' and a lot of problems from earlier versions have been fixed by
now. Having said that, your UPS should be supported through the USB port
then.

Kind regards, Arjen

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser

Re: [Nut-upsuser] (no subject)

[Charles Lepple]

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: probe of 2-1:1.0 failed with error -5


actually, this part is normal. The device is blacklisted from the
kernel usbhid driver so that it can be claimed in userspace by
newhidups.

Did you see any error messages from the driver or other NUT components?

--
- Charles Lepple

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser