[Nut-upsuser] (no subject)

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

[Nut-upsuser] (no subject)

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

[Nut-upsuser] (no subject)

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

Re: [Nut-upsuser] (no subject)

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

[Nut-upsuser] (no subject)

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

Re: [Nut-upsuser] (no subject)

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

[Nut-upsuser] (no subject)

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)

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)

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

[Nut-upsuser] (no subject)

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

[Nut-upsuser] (no subject)

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

[Nut-upsuser] (no subject)

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

Re: [Nut-upsuser] (no subject)

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.

RE: [Nut-upsuser] (no subject)

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

[Nut-upsuser] (no subject)

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?

Re: [Nut-upsuser] (no subject)

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

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: