On 10/25/2016 10:18 AM, Stephen Dubovsky wrote: > Im fully aware UDP doesn't resend. But there are no collisions on modern > ethernet LANs. No more reason a UDP packet would be corrupted going > through a (shared) switch as a direct connection.
True dat. But why take the chance and not use a direct connection with a cross-over cable? Typical UDP traffic in a switched LAN is fairly fast but not necessarily totally reliable. And over the years I've seen plenty of collisions on a switched network for both TCP and UDP. The difference being TCP has error correction and will resend the packet. The direct connection between the NIC and the Mesa port is a lot better and doesn't have the overhead latency of running through the switch. For real time signaling you'd want the least amount of latency and any possibility of collisions averted. No reason to run it through a switch unless you are planning on running multiple machines from a single computer, which seems unlikely. If you need an additional network connection for file transfer and the like, add a NIC or use wireless. Leave the dedicated machine controller port and connection to machine control and put nothing else in between. A dropped packet from a machine control command is a lot worse than a dropped packet from normal machine to machine communication. Mark Unix System and Network admin for almost 30 years ------------------------------------------------------------------------------ The Command Line: Reinvented for Modern Developers Did the resurgence of CLI tooling catch you by surprise? Reconnect with the command line and become more productive. Learn the new .NET and ASP.NET CLI. Get your free copy! http://sdm.link/telerik _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
