<br><div class="gmail_quote">2009/1/1 Johan Adler <span dir="ltr"><<a href="mailto:johan.adler@gmail.com">johan.adler@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Arnaud,<br>
</blockquote><div><br>Hi Johan,<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Does the Eaton merger/cooperation mentioned in the Christmas mail mean<br>
that you/we(the NUT team) will get the necessary information about<br>
older (Eaton) Powerware equipment and protocol too? In that case my<br>
suggested protocol forensics might be a waste of time (even if I might<br>
personally learn a thing or two in the process).<br>
</blockquote><div><br>indeed.<br>I'm currently preparing various actions, including the publication of UPSCode II and its cabling.<br>that's what was suggested in my preliminary mail, and the further Christmas mail.<br>
sorry not to have been able to react more explicitly before, end of the year burden...<br><br>the only issue for now is that the 3 authors of the upscode2 drivers have either explicitly or implicitly resigned.<br>so if you're interested in coding a bit to complete this driver, you're very welcome ;-)<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">2008/12/30 Kjell Claesson <<a href="mailto:kjell.claesson@epost.tidanet.se">kjell.claesson@epost.tidanet.se</a>>:<br>
<div class="Ih2E3d">> I think you find them in the nut comaptiblity list also. The difference is<br>
> that we need a report on that it works.<br>
<br>
</div>OK, then let it be noted that my Exide NetUPS SE works just fine with<br>
the upscode2 driver, as far as I can see. I have not actually pulled<br>
the plug on the UPS, letting NUT shut down the system, since I am<br>
quite happy just knowing that my UPS will keep my server running<br>
during the power failures I get here a few times a year.<br>
<div class="Ih2E3d"><br>
> Yes and bcmxcp have been improved in the trunk (going for 2.4.0).<br>
> And I think it would be good if we can get this into the upscode2 also.<br>
<br>
</div>Me too.<br>
<div class="Ih2E3d"><br>
> Are you up for to do some programming?<br>
> In that case I can support you with some doc's on how the loadsegment<br>
> is working in the upscode2. Don't know if the developer of the upscode2<br>
> driver is still active, I know they have this info.<br>
><br>
> Im at the moment on a low level of activity, due to many other things to do,<br>
> but I keep up with the list traffic and try to have the bcmxcp driver working.<br>
> But it need more work.<br>
<br>
</div>It has been a while since I coded in C, but I think I could do it if I<br>
could find the time. Modifying existing source should be easier than<br>
trying to write a new driver from scratch.<br>
</blockquote><div><br>indeed!</div></div><br clear="all">Arnaud<br>-- <br>Linux / Unix Expert R&D - Eaton - <a href="http://www.eaton.com/mgeops">http://www.eaton.com/mgeops</a><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>Free Software Developer - <a href="http://arnaud.quette.free.fr/">http://arnaud.quette.free.fr/</a><br><br>