> By the way, running TCP is probably not useful (since retransmission
> would be bad for timing) but IP/UDP may certainly be beneficial. The
> overhead is small so you might consider if it adds value for your
> case.
I used UDP protocol a few years ago on a realtime system which consisted
of serveral DOS-based data acquisition systems all taking operator
commands via ethernet and UDP packets. I used a UDP broadcast to send
the commands. Network traffice was light and the network was strictly
between the few data-acq. PCs and a Sun workstation.
Loss of command packets was a problem with UDP. It required special
attention and ack packets and re-transmits. For commands and such TCP/IP
would be better. For broadcasting some random data, UDP is fine.
-Wayne
-------------------------------------------------->-+
C.W. Wright,[EMAIL PROTECTED], Ph:757-824-1698
Fax: 757-824-1036,
NASA,Goddard Space Flight Center
Code 972, Wallops Flight Facility
Wallops Island, Va. 23337
-------+-<-------------------------------------------
--- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
----
For more information on Real-Time Linux see:
http://www.rtlinux.org/~rtlinux/
