Comunicaciones II
Introduccin
Ethernet originated at Xerox Palo Alto Research Center (PARC) in the mid1970s. The basic philosophy was that any station could send a message at any
time, and the recipient had to acknowledge successful receipt of the
message. It was successful and in 1980 the DIX Consortium (Digital Equipment
Corp., Intel, and Xerox) was formed, issuing a specification, Ethernet Blue
Book 1, followed by Ethernet Blue Book 2. This was offered to the Institute of
Electrical and Electronics Engineers (IEEE, www.ieee.org), who in 1983 issued
the Carrier Sense, Multiple Access/Collision Detect (CSMA/CD) specification
their stamp of approval on the technology.
Ethernet has since evolved under IEEE to encompass a variety of standards for
copper, fiber, and wireless transmission at multiple data rates.
Ethernet is an excellent transmission medium for data, but by itself falls short
of offering a complete solution. A network protocol is also needed to make it
truly useful and what has evolved alongside of Ethernet is TCP/IP.
Introduccin
The big push toward TCP/IP came in the mid-1980s when 20 of the largest U.S.
government departments, including the U.S. Department of Defense, decreed that all
mainframes (read: expensive computers) to be purchased henceforth required a
commercially listed and available implementation of UNIX to be offered. The
department didnt necessarily need to use UNIX for the project at hand, but after the
project was completed, the government wanted the ready option to convert this
expensive computer into a general-purpose computer.
This soon meant that all serious computer systems in the world had relatively
interoperable Ethernet and TCP/IP implementations. So IBM had Systems Network
Architecture (SNA), TCP/IP, and Ethernet on all of its computers. Digital (DEC) had
DECnet, TCP/IP, and Ethernet on all of its computers. Add a few more examples (Cray,
Sun, CDC, Unisys, etc.) and you soon see that the only true standard available on all
computers was a TCP/IP plus Ethernet combination.
Both from a historical view as well as in todays industrial world, the TCP/IP plus
Ethernet marriage is a key combination. Neither would have survived or prospered
without the other.
Ethernet 10Mbps
10Base2 thin wire coaxial cable (6.3 mm/0.25
inch diameter), 10 Mbps baseband operation, bus
topology.
10Base5 thick wire coaxial cable (13 mm/0.5
inch diameter), 10 Mbps baseband operation, bus
topology.
10BaseT unscreened twisted pair cable (0.4 to
0.6 mm conductor diameter), 10 Mbps baseband
operation, hub topology.
10BaseF optical fiber cables, 10 Mbps, 10 Mbps
baseband operation, point-to-point topology.
10base2
10base5
10baseT
Therefore each speaker must talk for more than 6 s every time he or she has something to
say. If two people simultaneously talked for only 2 s each, they would each hear the others
message clearly. The other speakers message would arrive 1 s after he finished speaking and
he could hear it, but others around the table would hear both messages mixed together.
The larger the table is, the longer the messages must be if everyone has equal opportunity to
talk.
In this example, message length was described in seconds, not bits or bytes. There is a direct
relationship between allowable network length and minimum message length. At this table,
if people speak at a rate of 4 words per second, then the minimum message size is 24 words.
Suppose the baud rate goes upextremely talkative speakers appear, who speak 40 words
per second instead of 4. Then the minimum message size is now 240 words! When you move
from 10-Mb Ethernet to 100-Mb or 1-Gb, the minimum required message length grows.
However to maintain compatibility, you cannot do this. So you have to reduce the size of the
table. So from 10 Mbps to 100Mbps the frame stayed at 64 Bytes min, so the collision
domain shrank from 2500 m (51.2 uS) to 250 m (5.12 uS). In Ethernet, a message must be
long enough to reach the other end of the network before the transmitter stops transmitting.
The minimum message length defines a maximum network length, which is called the
collision domain.
Reduciendo colisiones
Reglas de diseo
Longitud de los segmentos de cable
Tiempos de retraso
Tiempos de retraso
Tiempos de retraso
The maximum round-trip delay for 100BaseT systems is the
time to transmit 64 bytes or 512 bits and equals 5.12 s. A
frame has to go from the transmitter to the most remote
node then back to the transmitter for collision detection
within this round trip time. Therefore the one-way time delay
will be half this.
The maximum sized collision domain can then be determined
by the following calculation:
Repeater delays + Cable delays + NIC delays + Safety factor (5 bits
minimum) <2.56 s
Ejemplo de clculo
The following calculation is made to confirm whether it is
possible to connect two fast Ethernet nodes together using
two class II repeaters connected by 50-m fiber. One node is
connected to the first repeater with 50-m UTP while the other
has a 100-m fiber connection.
Class II
repeater
50m UTP
Ethernet
node
50m fiber
Class II
repeater
100m fiber
Ethernet
node
Ejemplo de clculo
Usando los valores de la Tabla anterior el retardo
total en un sentido es:
1.5*0.50+0.5*0.55+2*0.46+2*0.25=2.445s
La mitad del tiempo estipulado es 5.12/2=2.56s.
Se cumple con el factor de seguridad de 5bits?
Ethernet industrial
Early Ethernet was not entirely suitable for control
functions as it was primarily developed for office-type
environments. The Ethernet technology has, however,
made rapid advances over the past few years. It has gained
such widespread acceptance in industry that it is becoming
the de facto field bus technology.
EtherNet/IP is an application layer protocol that is
transferred inside a TCP/IP Packet. That means that
EtherNet/IP is simply the way data is organized in a TCP or
UDP packet.
EtherNet/IP was introduced in 2001 and today is the most
developed, proven and complete industrial Ethernet
network solution available for manufacturing automation.
Conectores y cableado
Most modern industrial Ethernet systems are, however,
based on a 10BaseT/100BaseTX configuration and thus
have to contend with RJ-45 connectors and (typically)
Cat5/Cat5e unshielded twisted pair (UTP) cable.
Despite its inherent resistance to electro-magnetically
induced interference, the UTP cable is not really suited
to industrial applications. The connectors are
problematic as well. The RJ-45 connectors are
everything but rugged and are suspect when subjected
to great temperature extremes, contact with oils and
other fluids, dirt, UV radiation, EMI as well as shock,
vibration and mechanical loading.
RJ-45 standard
Ethernet DB-9
Conectores
Cables
Existe una amplia variedad de cables
dependiendo del ambiente de aplicacin.
Circuitos de interfaz
https://www.odva.org/Portals/0/Library/Publications_Numbe
red/PUB00213R0_EtherNetIP_Developers_Guide.pdf
http://www.ti.com/tool/tidep0003
http://www.ti.com/lit/sl/slyy050b/slyy050b.pdf
https://www.maximintegrated.com/en/appnotes/index.mvp/id/5784
https://www.maximintegrated.com/en/appnotes/index.mvp/id/5821