<br><br>
<div class="gmail_quote">On Tue, Sep 1, 2009 at 12:33 PM, Charles Lepple <span dir="ltr"><clepple@ghz.cc></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<div style="WORD-WRAP: break-word">
<div class="im">
<div> </div></div>
<div>I would assume that if the argument to Convert.ToByte() is an integer less than 255, then the C equivalent would be that same integer. I think you would only use 0x35 if you were passing a string "5" to Convert.ToByte(). Someone who actually knows .NET can feel free to correct me, though.</div>
</div></blockquote></div>
<div> </div>
<div><font color="#3333ff">I think you're right Charles, I went back to the working example from LVR and stepped through everything. If I send Hex 0x05 to the device using an Output report it works under windows.. so my data needs to be a single byte of 0x05.</font></div>
<div><font color="#3333ff">Also if I echo back the result of Convert.ToByte(5) it is indeed 5..</font></div>
<div><font color="#3333ff"></font> </div>
<div><font color="#3333ff">Could you advise on how the output usage path is calculated from my lsusb -vv output ? (<a href="http://pastebin.com/m48287552">http://pastebin.com/m48287552</a>)</font></div>
<div><font color="#3333ff">I am going to try and get things working using output reports instead of interrupt_write because I know this works under Windows, but even after reading the example text I don't know how to calculate the PATH_IN / PATH_OUT values.</font></div>
<div><font color="#3333ff">I think if I can get those right then my problems will be solved.</font></div>
<div><font color="#3333ff"></font> </div>
<div><font color="#3333ff">Many Thanks</font></div>
<div><font color="#3333ff">Neil</font></div>
<div><br> </div>