[time-nuts] clock-block any need ?

Bob Camp lists at rtty.us
Fri Dec 28 17:36:06 UTC 2012


It's still an encapsulated stack that just coughs up the information after it's done this and that to it. How long the this and that takes is dependent on how busy the network is. It's going to watch packets on the net first and push data to the Arduino second. 

I'm beating on a similar part between posts. It *really* lags out as the traffic goes from near nothing to just a bit more than nothing. I'm not far enough into it to be able to put numbers on either measure. Looks like the units are in the thousands of bits per second range though. 


On Dec 28, 2012, at 11:18 AM, Jim Lux <jimlux at earthlink.net> wrote:

> On 12/28/12 7:56 AM, Bob Camp wrote:
>> Hi
>> Everything I've seen on the Adruino are "single chip wonders". They encapsulate the entire TCP/IP stack on the external chip. That will make getting at anything pretty tough.
> Well, they also do UDP..(at least the Wiznet 5100 does)..
> I was wondering if the timing from "UDP datagram received" to "some signal that Arduino sees" was deterministic at a useful level...
> The Arduino code I've looked at seems to be at a "sockets" kind of interface and there is an interrupt from the hardware when something arrives.
> _______________________________________________
> time-nuts mailing list -- time-nuts at febo.com
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.

More information about the time-nuts mailing list