Hi,
yes, you need to setup the following steps under Linux:
set up tap0 device - on a Linux system with tuntap support this looks somehow like this:
Example:
/sbin/ip tuntap add tap0 mode tap
/sbin/ip link set tap0 up
/sbin/ip addr add 192.168.2.1/24 dev tap0
BR
Edwin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2019-04-17
Originally created by: OW_RPi
Hello Edwin,
thank you for your quick reply.
I managed to handle EoE with your helpful hints
However, it seems to be very complicated:
- manage IP routing on RPi
- manage IP routing on Engineering PC
- All tap and IP route settings on RPi are gone after a restart of Codesys runtime or system reboot. Is there a possibility to make these settings persistent?
- I am able to ping my EoE device from my Engineering PC. However, it is not possible to use the device's engineering tool on my PC. Timeouts and 'Device is busy' messages are the reasons. Any ideas?
Thank you!
Best regards,
Oleg
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
i have some problems with EoE on EtherCAt devices on linux x64 runtime,
I have configured tap0 and Eoe devices,The first device responds to the ping request but all ather not.
if I remove the EoE configuration of the first node, the second responds but the subsequent ones continue not to respond.
This is a problem in the slaves ethercat stack of the CT drives,
as soon you read a non existing object the communication (EoE) stucks.
There is a workaround available:
read object 0x1000 from each slave after startup then EoE will work on all drives.
Additional this need to be reported to CT.
BR
Edwin
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Originally created by: OW_RPi
Hi,
is RPi3 an EoE capable device?
How to setup EoE correctly in CODESYS?
IP routing needed?
Please help!
Best regards,
Oleg
more posts ...
Hi,
yes, you need to setup the following steps under Linux:
set up tap0 device - on a Linux system with tuntap support this looks somehow like this:
Example:
/sbin/ip tuntap add tap0 mode tap
/sbin/ip link set tap0 up
/sbin/ip addr add 192.168.2.1/24 dev tap0
BR
Edwin
Originally created by: OW_RPi
Hello Edwin,
thank you for your quick reply.
I managed to handle EoE with your helpful hints
However, it seems to be very complicated:
- manage IP routing on RPi
- manage IP routing on Engineering PC
- All tap and IP route settings on RPi are gone after a restart of Codesys runtime or system reboot. Is there a possibility to make these settings persistent?
- I am able to ping my EoE device from my Engineering PC. However, it is not possible to use the device's engineering tool on my PC. Timeouts and 'Device is busy' messages are the reasons. Any ideas?
Thank you!
Best regards,
Oleg
Hi,
i have some problems with EoE on EtherCAt devices on linux x64 runtime,
I have configured tap0 and Eoe devices,The first device responds to the ping request but all ather not.
if I remove the EoE configuration of the first node, the second responds but the subsequent ones continue not to respond.
what could be the reason??
Best regards
Erik Attolini
[img src=attachment.png width=50%]
Which versions are involved?
Hi,
version codesys Enginering and runtime are 3.5.16.20.
But i have same problem also with older versions
which drives are you using, there is a known problem with CT drives..
Hi,
i'm using Controltechniques drive M700 and Digitax HD(M753),other drives in pictures dosn't support EOE.
This is a problem in the slaves ethercat stack of the CT drives,
as soon you read a non existing object the communication (EoE) stucks.
There is a workaround available:
read object 0x1000 from each slave after startup then EoE will work on all drives.
Additional this need to be reported to CT.
BR
Edwin
Thanks a lot!
Hi,
I need to use EoE, do I need some Routing/Tap etc configuration on the device?