I have an ethercat configuration with 2 modules connected to the bus (1 phoenix contact AXL F input/output coupler) and an IFM DTE103 to connect RFID readers.
Everything works fine until I try to connect an additional DTE103.
In my opinion the 2 DTE103 have the same Ethercat address. because when I disconnect the first one and connect the new one it works. But when the 2 are connected at the same time the bus crashes, the master displays "topology nicht ok" and I have to restart the ctrlX to be able to communicate again with the slaves.
How does Ethercat addressing work? I have switches to change the address manually on the phoenix module but not on the DTE103 modules.
Thanks for your help
Solved! Go to Solution.
To clarify what you are doing:
In our EtherCat master the addressing is automatically given with "AutoInc" mode:
Thanks for your reply,it works now.
I had some problems, but it must have been due to a poor knowledge of Ethercat.
It is the first time that I work with this bus.
Can you explain the basic best practices to me?
I tried to connect another device to configure it. But it's not possible by disconnecting the rest of the network right?
With other buses, if slaves are missing it does not matter, we can still configure other slaves, but with Ethercat it automatically takes the address of another module? Can you confirm?
Does an industrial switch that works for Profinet also works for Ethercat or do we have to use specific switches for Ethercat?
If I understood correctly each time I want to add a slave, all the slaves must be connected, I must pass the master in Pre-Op, then connect the new slave. Scan device, add slave, load config and go back to OP?
Could you clarify what exactly you mean with configuring a slave? Do you mean setting parameters in a single slave? In Ethercat there are so called "start up parameters" that are automatically written to a slave while boot up. See example in this post.
Like mentioned the EtherCat master in the actual state will give addresses automatically depending on the topology. See online documentation.
I think you will need special EtherCat switches because of the technology used.
You can also switch up the EtherCat partially to Pre-OP and not all modules need to attached. In standard all data is transmitted in one package and as soon as one datum is faulty all data will get invalid. But several data packages can be set up that are checked individually. This is handled via so called "sync units" (see docu). So if a missing slave is another sync unit then the rest, the bus can go up.
Beside the scan function you can of course also add build up your IO project "offline" and then only load it once to the EtherCat master.
See for further information the: