Skip to end of banner
Go to start of banner

Troubleshooting EtherCAT

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »


General

If a slave can´t be detected by a network scan or if it is not present in the Device Catalog, it´s commonly the case of not choosing the correct file type upon importing the ESI file in SyCon.net.

Please make sure to choose EtherCAT DFF whilst importing the salve´s description file:

Master

One of the most crucial parts and often the cause of issues is the cabeling / topology of the EtherCAT network. Our master firmware is really strict about proper topology.

For EtherCAT every slave has an IN and an OUT Port and the master has a Main and a redundancy port.

The cabeling should be done as follows:

The master´s Main port is connected to the first slave´s IN port and the OUT port of the first slave is connected to the IN port of the second slave and so on.

For this document a network with two slaves was chosen:




Slave

Title 3 provides an entry in the table of contents as x.1 + n.1 + m

etc.

  • No labels