Hi Carlos,<br><br><div><span class="gmail_quote">2005/10/26, Carlos Rodrigues <<a href="mailto:carlos.efr@mail.telepac.pt">carlos.efr@mail.telepac.pt</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I have an MGE Pulsar Evolution 1100 connected to a Debian box, with<br>nut-2.0.1 (the standard "sarge" packages). I have it connected through<br>USB, and I'm using newhidups.<br><br>However, about once a day the driver looses contact with the UPS and I
<br>have to restart NUT to get it to drop the "data stale" nonsense (it<br>happens more often than this, but most times it recovers without user<br>intervention).</blockquote><div><br>
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)<br>
<br>
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/<br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Since this model is supported by mge-utalk, mge-shut and newhidups,</blockquote><div>
<br>
<br>
FYI:<br>
- mge-utalk is for the legacy ASCII protocol<br>
- 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<br>
- newhidups...<br>
<br>
So, the best is between mge-shut and newhidups, knowing that the former will be merged in the latter one day.<br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I'm wondering which is the best one to use with this particular model<br>(I remember having it connected to another box, using nut
1.4.1 and<br>mge-utalk, and something like this used to happen too, with the<br>difference that most of the data stopped appearing in the "upsc<br>ups@localhost" listing, but it could still see the power status -
<br>on-battery, etc.).<br>
</blockquote></div><br clear="all">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).<br>
<br>
thanks for the feedback,<br>
Arnaud Quette<br>-- <br>Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt<br>Network UPS Tools (NUT) Project Leader - <a href="http://www.networkupstools.org/">http://www.networkupstools.org/</a><br>Debian Developer -
<a href="http://people.debian.org/~aquette/">http://people.debian.org/~aquette/</a><br>OpenSource Developer - <a href="http://arnaud.quette.free.fr/">http://arnaud.quette.free.fr/</a>