EOE-Routing /How it works
EOE-Routing /How it works
Related Products
SIG350-0006AP100 IOL-MASTER,ECAT
Table of Contents
EOE-Routing /How it works
Ethernet over Ethercat (EoE), which settings are important
Due to the fact we have some EtherCAT devices (DL100, MLG, SIG350) which have Ethernet functionalities it is mandatory to understand the principle over EoE (Ethernet over EtherCAT).
With this feature you are able to reach the devices as example with REST-API, OPC UA or SOPAS ET.
So how does the main principle look like:
/msdyn_blobfile/$value)
'
As you see without the EoE feature we are not able to reach anything behind PLC. After the PLC the devices are “speaking” EtherCAT.
What happens now if you activate this feature on your PLC?
/msdyn_blobfile/$value)
As you see the PLC build up a small Ethernet within in the EtherCAT environment.
It is mandatory that the IP addresses are not in the same Subnet, because it could influence the real-time capabilities from EtherCAT.
Here are the settings inside of an engineering tool as example:
/msdyn_blobfile/$value)
As you see the SIG350 has like in the sketch above the IP address 192.168.100.1 and the Master 192.168.100.254.
All addresses within this network are giving here, any other preset IP address will be away.
Now it is important if you want to access the Devices behind the PLC with the EOE feature is important to add a route. Therefore, you have to
open the command line (with admin rights) or PowerShell (with admin rights) and write following:
/msdyn_blobfile/$value)
I will translate in a very simple way:
Create a bridge starting from 192.168.136.20 (the PLC), that I am able to see everything from 192.168.100.0 - 192.168.100.254 with the Subnet 255.255.255.0 (EoE).
And here is the example the SIG350 Webserver:
/msdyn_blobfile/$value)
Ethernet over Ethercat (EoE), which settings are important
Due to the fact we have some EtherCAT devices (DL100, MLG, SIG350) which have Ethernet functionalities it is mandatory to understand the principle over EoE (Ethernet over EtherCAT).
With this feature you are able to reach the devices as example with REST-API, OPC UA or SOPAS ET.
So how does the main principle look like:
As you see without the EoE feature we are not able to reach anything behind PLC. After the PLC the devices are “speaking” EtherCAT.
What happens now if you activate this feature on your PLC?
As you see the PLC build up a small Ethernet within in the EtherCAT environment.
It is mandatory that the IP addresses are not in the same Subnet, because it could influence the real-time capabilities from EtherCAT.
Here are the settings inside of an engineering tool as example:
As you see the SIG350 has like in the sketch above the IP address 192.168.100.1 and the Master 192.168.100.254.
All addresses within this network are giving here, any other preset IP address will be away.
Now it is important if you want to access the Devices behind the PLC with the EOE feature is important to add a route. Therefore, you have to
open the command line (with admin rights) or PowerShell (with admin rights) and write following:
I will translate in a very simple way:
Create a bridge starting from 192.168.136.20 (the PLC), that I am able to see everything from 192.168.100.0 - 192.168.100.254 with the Subnet 255.255.255.0 (EoE).
And here is the example the SIG350 Webserver:
Keywords:
EOE, Ethercat ,CtrlX, Beckhoff
EOE, Ethercat ,CtrlX, Beckhoff