No subject

handler path is a bit too longto handle 115200 (~80us per byte).

I have seen 57600 work reliably.

eric

On Wed, Sep 3, 2008 at 3:40 PM, Razvan Musaloiu-E. <razvanm at cs.jhu.edu>wrote:

> Hi!
>
> I attached a small application and a Python testing script that shows that
> 115200 doesn't work reliably for telos. The nesC application is sending
> packets back to back while the script will accept all the incoming packets
> and tried from time to time to send some (one at a time). Using the 57600
> (enabled by default in the application) the acks work properly. When the
> 115200 is enabled the acks stop working (or they come very infrequently).
>
> This issue was discussed before [1] but no solution surface from that. In
> this context I think it would be good to switch to safer 57600 rate for now.
> Is anybody against this? :P
>
> Note: I don't have a Windows TinyOS installation so I only tested on Linux
> on real machines and VMWare.
>
> [1]
> http://mail.millennium.berkeley.edu/pipermail/tinyos-devel/2008-April/thread.html#2651
>
> --
> Razvan ME
> _______________________________________________
> Tinyos-devel mailing list
> Tinyos-devel at millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-devel
>
>


-- 
Eric B. Decker
Senior (over 50 :-) Researcher
Autonomous Systems Lab
Jack Baskin School of Engineering
UCSC

------=_Part_25829_12992763.1220482622315
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div dir="ltr">From what I&#39;ve seen using 115200 with the MSP430 platforms, the interrupt handler path is a bit too long<div>to handle 115200 (~80us per byte).</div><div><br></div><div>I have seen 57600 work reliably.</div>
<div><br></div><div>eric<br><br><div class="gmail_quote">On Wed, Sep 3, 2008 at 3:40 PM, Razvan Musaloiu-E. <span dir="ltr">&lt;<a href="mailto:razvanm at cs.jhu.edu">razvanm at cs.jhu.edu</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi!<br>
<br>
I attached a small application and a Python testing script that shows that 115200 doesn&#39;t work reliably for telos. The nesC application is sending packets back to back while the script will accept all the incoming packets and tried from time to time to send some (one at a time). Using the 57600 (enabled by default in the application) the acks work properly. When the 115200 is enabled the acks stop working (or they come very infrequently).<br>

<br>
This issue was discussed before [1] but no solution surface from that. In this context I think it would be good to switch to safer 57600 rate for now. Is anybody against this? :P<br>
<br>
Note: I don&#39;t have a Windows TinyOS installation so I only tested on Linux on real machines and VMWare.<br>
<br>
[1] <a href="http://mail.millennium.berkeley.edu/pipermail/tinyos-devel/2008-April/thread.html#2651" target="_blank">http://mail.millennium.berkeley.edu/pipermail/tinyos-devel/2008-April/thread.html#2651</a><br><font color="#888888">
<br>
--<br>
Razvan ME</font><br>_______________________________________________<br>
Tinyos-devel mailing list<br>
<a href="mailto:Tinyos-devel at millennium.berkeley.edu">Tinyos-devel at millennium.berkeley.edu</a><br>
<a href="https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-devel" target="_blank">https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-devel</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Eric B. Decker<br>Senior (over 50 :-) Researcher<br>Autonomous Systems Lab<br>Jack Baskin School of Engineering<br>UCSC<br><br>
</div></div>

------=_Part_25829_12992763.1220482622315--