similar to: Re: NUT works with more ActivePower UPSes

Hi there I have a Mustek PowerMust 1000 USB using serial port /dev/ttyS0. I use nut 2.2.1 with the megatec driver on Debian Lenny (testing), running on an AMD64 X2. (I was using a Debian Etch as slave, but to keep it simple I turned it off) My problem is that sometimes the UPS is running OK, but when the message "UPS is trimming incoming voltage" appears on knutclient (i.e. OL TRIM in

Arnaud Quette wrote: > Anyhow, I would more see this as a merge of all these drivers, with > some autodetection or flag/param to switch the mfr/model and maybe > capabilities... Whatever the driver name is, a good thing would be the > name of the protocol or something generic enough, though powermust is > fine. Ok, I made some minor changes to powermust, to make it less

On Feb 11, 2008 5:30 PM, Marcio Gomes <mpg at microlink.com.br> wrote: > I change the if in [OFF] detect state to, in original way, if you send a > reset.watchdog, the UPS goes > to OFF state in clients, but it is not correct, because UPS is OL and > Shutdown are in progress, but > the power is not OFF First of all, thanks for the patch. But I have a few comments: Are you

Hi there, I made a new driver, based on blazer, that should work with most of the UPSes manufactured by Voltronic Power - http://www.voltronicpower.com/oCart2/index.php?route=product/category&path=37- and rebranded as Atlantis Land, Cablematic, EPC, FSP, Mustek, SHT, Tuncmatik and many others (they come with a software called Viewpower - http://www.power-software-download.com/viewpower.html )

Hi, a few days ago, I bought some of those Mustek UPSes that have both a serial and a USB connector. Currently only the serial port is supported by the megatec driver. This works fine so far. Now I have seen there is a megatec_usb driver, which currently only supports 2 other UPSes. How can I help to find out whether the PowerMust might actually work with the megatec_usb driver? -- Regards,

I have found by trial and error that the Activepower 1400VA UPS (uninterruptible power supply) (http://www.activepower.pl/1400.php) is best driven by the powermust driver in NUT (Network UPS Tools), on an RS232 cable. The USB connection does not seem to yield, use the serial RS232 cable. This took me quite a while to find out, so I thought I would share the experience. Regards, Laszlo Kajan

On Jul 23, 2017, at 4:50 AM, Alphonse <alphsteiner at gmail.com> wrote: > > Another point is bugging me: the ups is not repported as a battery in kde nor in the output of 'solid-hardware list'. > Do you have an idea for this problem? > Thanks! > To be honest, most of the NUT development effort is focused on shutting down servers, so there isn't a whole lot of

Hello, I'm trying to get my UPS working with nut-hal-drivers, and it seems be detected correctly with Megatec protocol, but it provides wrong battery level. I read that I can use battvolts option to fix this problem, but HAL version of nut does not come with any config files. So, I'm guess it should be somehow fixed in sources? Parameters of Ippon Back Comfo Pro 800: VA = 800 max

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Good day to all. In one of the offices I'm administering there are about 15 UPS marked with the brand "Ippon BackPro". This brand is widely popular in Russian Federation, while by itself is a 'Made in PRC' megatec clone. Depending on the model this UPSes have got either one standard serial RS-232C interface (cheaper models like

Markus Layr wrote: >Hi, > >thanks for the mustek driver for the nut packages. >It works nearly perfect for my Mustek PowerMust USV 2000VA. > >There is only a little problem concering the battery.charge, perhaps you >can help me to solve it. > >I always get 100.0 as value for the battery.charge, it never changes. > >Regards, >Markus Layr > >

Hi all, Currently, the "megatec" driver only supports UPSes which have a serial (RS232) interface. However, I'm under the impression that most of the models that speak the megatec protocol, and have an USB interface, just have a standard serial-to-USB converter inside. This being the case, there should be a "/dev/ttyUSBx" device which the megatec driver could use just as

Hi all, Currently, the "megatec" driver only supports UPSes which have a serial (RS232) interface. However, I'm under the impression that most of the models that speak the megatec protocol, and have an USB interface, just have a standard serial-to-USB converter inside. This being the case, there should be a "/dev/ttyUSBx" device which the megatec driver could use just as

Hi, I'm not the maintainter for the "megatec_usb" driver (in fact, I'm no longer maintainer for the base "megatec" either), so I don't really know the status for that particular UPS. I'm forwarding this to the NUT mailing-list though. Regards, -- Carlos Rodrigues On Fri, Dec 5, 2008 at 10:30 AM, Adrian Czerniak <adrian.czerniak at becomo.com> wrote:

Hi, I'm not the maintainter for the "megatec_usb" driver (in fact, I'm no longer maintainer for the base "megatec" either), so I don't really know the status for that particular UPS. I'm forwarding this to the NUT mailing-list though. Regards, -- Carlos Rodrigues On Fri, Dec 5, 2008 at 10:30 AM, Adrian Czerniak <adrian.czerniak at becomo.com> wrote:

NUT recently stopped working on my debian. I'm not sure which upgrade broke it. ups.conf: [mustek] driver = megatec port = /dev/ttyS0 desc = "mustek ups" # upsd -DDDD Network UPS Tools upsd 2.4.1 listen_add: added ::1:3493 listen_add: added 127.0.0.1:3493 setuptcp: try to bind to 127.0.0.1 port 3493 listening on 127.0.0.1 port 3493 setuptcp: try to bind

On 1/2/07, Eric A. Hall <ehall@ehsco.com> wrote: > I can hack up a Cacti PHP script to monitor UPS state via the upsc client > in the meantime. I'll have to manually enumerate the UPS names associated > with a host target (is there a way to probe for them with upsc now?), but > otherwise it ought to be pretty straightforward scripting. NUT developers, The NUT protocol

Hi, I've stumbled over a race condition in upssched when using 3 or more UPSes in combination with START-TIMER/CANCEL-TIMER. I have a solution that works but is ugly, so I'm going to describe the bug here in the hope somebody can come up with a better solution. The problem is in upssched.c:629 check_parent() (see https://github.com/networkupstools/nut/blob/master/clients/upssched.c ).

Dears, I have centos 5.5 with kernel 2.6.18 UPS: Mustek PowerMust 2000VA USB I trying to setup monitoring for this ups, I connect ups with server via COM port and USB. But here is the problem (with megatec_usb): [root at optimus ups]# /sbin/upsdrvctl start Network UPS Tools - UPS driver controller 2.2.0- Network UPS Tools 2.2.0- - Megatec protocol driver 1.5.4 [megatec_usb] Carlos

And sorry, I forgot to put log from messages, I always got this: Oct 30 21:06:25 optimus kernel: usb 5-1: usbfs: process 9808 (megatec_usb) did not claim interface 0 before use From: nut-tracker-bounces+vladimir=micovic.com at lists.alioth.debian.org [mailto:nut-tracker-bounces+vladimir=micovic.com at lists.alioth.debian.org] On Behalf Of Vladimir Micovic Sent: Saturday, October 30, 2010 8:00

Hello list, I have the following hardware setup: - HP C7000 enclosure, with 4 blade servers - two power supply modules in the enclosure (one is enough to sustain the 4 blades) - two UPSes, each one feeding one of the enclosure power supplies I would like to configure NUT to initiate an early shutdown of that environment only if *both* UPSes are on battery. I've created the 2