[Nut-upsuser] MGE Pulsar M 3000 communication problems

Arnaud Quette aquette.dev at gmail.com
Fri Oct 6 07:21:50 UTC 2006

Hi Ingo,

2006/10/6, Ingo Schaefer <ingo at ingo-schaefer.de>:
> Hello Arnaud,
> Am Donnerstag, den 05.10.2006, 18:18 +0200 schrieb Arnaud Quette:
> > please, add "pollinterval=15" into your ups.conf definition, at the
> > end of the [mge3000-1] section, and then relaunch the above test and
> > send me the output.
>  http://zeus.fh-brandenburg.de/~schaefei/nut_output2.log

ok, it's a bit better.
can you now make an integration test (mge-shut, not in debug mode +
upsd + upsmon) and report back.
Note that you will need to adjust MAXAGE and DEADTIME to 20/25 seconds.

Also note that the mge-shut rewritte for 2.2 (merge with newhidups,
which shares the same HID core) will greatly improve such kind of
problems, since the hardware is polled too much, even for constant
data. And I've already addressed this in newhidups. So we're more
about finding a temporary solution to your problem, while waiting for
the real good solution.

> > but we'll follow on
> > nut and find a solution to your problem.
> Thats the way I know OSS projects. Especially if supported by hardware
> vendors or distributors. Great!

right, but what MGE does is still more an exception than the standard!

Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
OpenSource Developer - http://arnaud.quette.free.fr/

More information about the Nut-upsuser mailing list