On 2/1/07, <b class="gmail_sendername">Jon Gough</b> <<a href="mailto:jon.gough@eclipsesystems.com.au">jon.gough@eclipsesystems.com.au</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<font size="3">Peter,<br>
I understand that the real functionality should be elsewhere
than the driver. But the commands for the serial interface allow for
sending parameters to the UPS, ie S<n>R<m>, S<n>,
T<n>, so I just wanted to be able to do that as well. This would
then make the driver issue all the commands that are possible.<br></font></div></blockquote></div><br>Maybe it's just because it's 4am, or because I skipped too much of the previous posts, but I'm not getting...
<br><br>The "megatec" driver already does it. If we're talking about a simple layer to communicate with the UPS over USB instead of serial (something that has been talked about), then it's just that, a simple layer under the unmodified megatec driver. Or are we talking about more than just a simple encapsulation of the megatec protocol, something like a mix of megatec strings and USB specific stuff?
<br><br>I went back a few posts, but since I haven't had much time to read everything thoroughly, I'm starting to get confused with all this (and starting to think that there isn't much hope of concentrating all things megatec under a single driver).
<br clear="all"><br>-- <br>Carlos Rodrigues