First let’s discuss each term between the Ethernet and IP. When most people think of the Ethernet in terms of a physical connection. You may have an Ethernet port on your computer in which you can plugin a cable, they then connects to the router or switch. This type of connection is mostly called a LAN connection. However Ethernet is not connections type but instead an IEEE protocol. In our everyday use of the internet we typically just say you are connected via Ethernet or wireless. It’s much easier to say Ethernet and then get into the actual terms of the connection protocols, stacks, layers etc.
Now that we have said that Ethernet is a protocol Vs a physical connection. Let’s get little deep into some of the terms:
Most communications to computers or devices that may want to send and receive data there has to be some common rules for sending and receiving these packets. This is where the Protocol comes in. The TCP/IP protocol is the most commonly known protocols. This protocol is widely used in internet connections. The term TCP/IP relates to TCP or Transmission Control Protocol whereas the IP stands for Internet Protocol. There are other protocols such as Open System Interconnection or OSI but for simplicity sake.
Let’s learn some more about the TCP/IP now:-
The TCP/IP mode is a layered protocol. The various layers present in this protocol are – Applications, TCP, IP and Network. Basic functions are explained but there are many details in each layer. Each layer has a function that it performs and when complete then passed to the next layer. In terms of the internet transmitting computer data is the applications layer. This layer works with the application software to provide communications that may be required such as HTTP, FTP, DNS, and IMAP etc. That layer will add some data that will identify and direct the data and then passes it to the TCP layer. The TCP layers’ job is to pack and unpack data and do some error checking on to the IP or the Internet Protocol layer where some more identifiers are added. The data is transferred over the network layer, which the data to the Ethernet packets or whatever other protocol is required.
These data move up and down in a stack or layer continuously getting packed, unpacked, headers and info added to lead it etc. So through this TCP/IP protocol layer explanation you learned that the transmission of the data resolves in Ethernet packet.
The device applications layer which can be Facebook, Google etc. will present its data and then layer by layer the data is transferred and it is then transmitted via an Ethernet packet to the network layer which in turn is connected to your computer or TLC.
Now that we have explained the Ethernet packets we can get into the IP part; of the Ethernet/IP or Ethernet/IP description.
IP in this case now correlates to “Industrial Protocol” Vs the Previous description of “Internet Protocol” confused yet? The IP part of the Ethernet infrastructure and junction with the industrial protocol Vs the IP layers to combine with TCP/IP or the User Datagram Protocol (UDP) or UDP layers to create a protocol that can be used to support data exchange and control application we need to break down the TCP/IP or UDP protocols slightly to give an idea which application may use which type. In the TCP/IP protocol there is a somewhat of a data send and receive acknowledge relationship.
The packets go down the stack, received it to the device connected to your network and then receive confirmation goes back of the stack to the up of the stack applications layer. This type of protocol may be used with command to speed. Need to ensure that the vfe receive the message. Conversely with the UDP protocol this continuous transmission not requiring a received acknowledgement. This protocol will be used in something like the Ethernet I/O or protransmitter devices which will constantly send the data. If the packet was not received, it’s not a deal breaker; as the next packet is right around the corner.
CIP uses object Oriented Design to present the things like a device profile. If you have ever used a CIP message instruction within your TLC device, you know that the research types of data you desire such as frequency, speed or false and you add that assembly number to your CIP instruction. The data exchanged is the number of data registers that you in turn map to logs for desired data. This EIP is compatible with many standard Ethernet switch used within the industrial automation arena which makes it easy to implement. Combinations of data speeds depend on 100 MBPS or easily handled with these off the shelf switches. In the simplest words we can say that the Ethernet/IP is the Ethernet packets used with the industrial protocol of CIP, TCP/IP and UDP layers to provide the required data to your controller.