2. Master architecture has some boxes, like Monitor,
Master Stack, System Configuration Tool, and so
on.
Master Stack is the key box in EtherCAT, and it
also has several sub-boxes.
• API layer
• Master core
• OS layer
• Link layer
.
.
.
3.
4. Process data:
• Deal with the process data cyclicly.
Mailbox:
• In order to configure and diagnose slave devices, it
accesses the variables provided for the network with
the help of acyclic communication. Process several
communication profiles, such as CoE, EoE, and SoE.
XML parser:
• According “ENI(EtherCAT Network Information)” to
configure and initial the slaves.
5. Slave will generate the “ESI(EtherCAT
Slave Information)” and send it to System
Configuration Tool to translate into “ENI”,
then master can understand the EtherCAT
network and configure it.
ENI and ESI are both .xml file.
6.
7. Slave has “ESC(EtherCAT Slave
Controller)” which help master to control
the slave.
ESC also has several boxes, like Mailbox,
Process data, Register and so on.
8. Process data:
• Process the data go through the slave.
Mailbox:
• Help master to configure and diagnose slave
devices. Process the several communication
profiles.
9. Sync Managers
• Sync Managers are responsible for managing data sharing.
That means it handles the memory and buffer.
Fieldbus Memory Management Units (FMMUs)
• The Fieldbus Memory Management Units (FMMUs) are
responsible for mapping memory from the Sync Managers
into the EtherCAT frame, means it places each data from
sync managers into a single EtherCAT packet.
• A FMMU associated with each sync manager so that the
data from that sync manager is placed correctly into the
EtherCAT frame.