Nut upsdev - Oct 2005 - Best driver for MGE Pulsar Evolution 1100

I have an MGE Pulsar Evolution 1100 connected to a Debian box, with
nut-2.0.1 (the standard "sarge" packages). I have it connected through
USB, and I'm using newhidups.

However, about once a day the driver looses contact with the UPS and I
have to restart NUT to get it to drop the "data stale" nonsense (it
happens more often than this, but most times it recovers without user
intervention).

Since this model is supported by mge-utalk, mge-shut and newhidups,
I'm wondering which is the best one to use with this particular model
(I remember having it connected to another box, using nut 1.4.1 and
mge-utalk, and something like this used to happen too, with the
difference that most of the data stopped appearing in the "upsc
ups@localhost" listing, but it could still see the power status -
on-battery, etc.).

--
Carlos Rodrigues

Hi Carlos,

2005/10/26, Carlos Rodrigues
<carlos.efr@mail.telepac.pt>:
>
> I have an MGE Pulsar Evolution 1100 connected to a Debian box, with
> nut-2.0.1 (the standard "sarge" packages). I have it connected
through
> USB, and I'm using newhidups.
>
> However, about once a day the driver looses contact with the UPS and I
> have to restart NUT to get it to drop the "data stale" nonsense
(it
> happens more often than this, but most times it recovers without user
> intervention).

this problem is the "well known" (TM) EMI disconnexion problem
I've solved
in 2.0.2. Note that I've made a proposed-update for sarge, but it won't
solve your pb. Only a backport of the last package I've uploaded (2.0.2-2,
uploaded on 2005-10-19)

If you need help, please tell me back as I've not yet had time to setup back
my personal pool on d.o/~aquette/

Since this model is supported by mge-utalk, mge-shut and newhidups,



FYI:
- mge-utalk is for the legacy ASCII protocol
- mge-shut is for the new binary SHUT protocol (Serial HID UPS Transfer),
which is only the same HID data as on the USB bus, but marshalled on a
serial line
- newhidups...

So, the best is between mge-shut and newhidups, knowing that the former will
be merged in the latter one day.

I'm wondering which is the best one to use with this particular
model
> (I remember having it connected to another box, using nut 1.4.1 and
> mge-utalk, and something like this used to happen too, with the
> difference that most of the data stopped appearing in the "upsc
> ups@localhost" listing, but it could still see the power status -
> on-battery, etc.).
>
Yep, I've got to check mge-utalk. Seems there has been a huge regression
between 2.0.1 and 2.0.2 (a bug is logged on alioth).

thanks for the feedback,
Arnaud Quette
--
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/
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20051026/76967d9c/attachment.html

On 10/26/05, Arnaud Quette <aquette.dev@gmail.com>
wrote:
>  So, the best is between mge-shut and newhidups, knowing that the former
> will be merged in the latter one day.
Hmmm, so with these packages I may have better luck using mge-shut? I
have no problem going back to using the serial port...

--
Carlos Rodrigues