??? 02/02/07 07:55 Read: times |
#131914 - But some things are just not simple! Responding to: ???'s previous message |
And ethernet connectivity is one of them!
Ethernet is designed for large, multi-platform, multi-protocol networks with large numbers of nodes. Anything that can cope reliably with this just isn't going to be simple, I'm afraid. Ganeshprasanna M K said:
... TCP/IP (which is really complicated) where as i m looking for ETHERNET/IP/UDP That doesn't mean to say that ETHERNET/IP/UDP is going to be simple. It still has to co-exist with with everything else on the LAN - which is where (most of) the complication comes. As I've noted before, making something that considers only the "perfect" case is usually only 10% of the effort; the other 99%[1] goes to coping with all the things that could possibly go wrong - packet loss, corruption, timeouts, etc, etc, etc,... IF you want Simple, then you have basically 2 choices: 1. Use a device that makes it simple for you; eg, by providing a simple serial port interface, like the Xport, Nemo, or CD220x 2. Choose an interface that is simple - Ethernet, IP, etc is not simple. [1] Yes, I know that adds up to >100% - but isn't that always the way with development timescales... |