2. EtherCAT protocol is based on IEEE
802.3(Ethernet) which means the lower
hardware cost we need.
Additionally, EtherCAT devices may also
support Ethernet protocols(such as HTTP,
TCP/IP, web server, E-mail, FTP).
3.
4. EtherCAT supports many requirements of
fieldbus, like “Sercos” and “CANopen”. It
also can lower the hardware cost.
Fieldbus is the name of a family of
industrial computer network protocols used
for real-time distributed control,
standardized as IEC 61158.
5. EAP/ADS is a protocol developed and
disclosed by Beckhoff for equal exchange
of information between hardware- or
software-based controllers(master/master
communication) or for interfacing with a
central master computer.
6.
7. The cyclic EAP communication can be
handled directly in the user data of an
Ethernet telegram, without the need for an
additional transport or backup protocol.
Therefore enables very efficient data
exchange without significant protocol
overhead(save cost of headers or packets),
with cycle times down to one millisecond or
even faster.
8.
9. EtherCAT provides several communication profiles to
support many protocols and services. And Mailbox is
responsible for these profiles.
• CAN application protocol over EtherCAT (CoE)
• Servo drive profile, according to IEC 61800-7-204 (SoE)
• Ethernet over EtherCAT (EoE)
• File Access over EtherCAT (FoE)
• Automation Device Protocol over EtherCAT (ADS over EtherCAT,
AoE)
10. Many devices have previously outfitted
CANopen and Sercos, so CoE and SoE
makes it possible to implement EtherCAT
with minimal effort, and large portions of
the firmware are even reusable.
EoE helps EtherCAT environment
implement all internet technologies.
11. EtherCAT can transport EAP telegrams
directly to the other side via AoE(ADS over
EtherCAT), without underlying IP channel.
Communication via AoE must be enabled
on both sides.
