>We've had previous discussions about using ethernet for real time control.
>In theory, this is NOT difficult stuff. I'll bet I could get something >going in a week or three. >In practice, though, it is a PITA. That's because you would need a real >time driver for each of the zillion or so different ethernet boards, >chips, etc., that people want you to support. >Then, of course, there is the question of what to put on the end of the >ethernet. Something like Jon Elson's boards would be nice. Something >that you could expand with lots of switch and relay interfaces would >make many people happy. >Ken Actually why not create a network loop test much like the interrupt latency test. Measure the Ping time and get a known good "fast" and "Reliable" network. ie Low utilization of the bandwidth. Then run UDP vs TCP/IP and you should be able to run a control system that would be usable. Granted you would not have the high speed parallel port response, but you might get something useful. I think most drivers would provide some usable bandwidth. Maybe a minimum requirement would be a 100Mb network (Wired) for starters. Figure out what that takes to make that work then evaluate and see if something slower would work. That will take you into the wireless 802.11 envelope. Jim Combs Lexmark - Lexington, Ky ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
