April-16th-2019, 02:23 PM
(This post was last modified: April-16th-2019, 02:24 PM by Armin@netPI.)
Thank you for clarifying.
With CODESYS there is nothing else that needs to be done with the eth0 interface. Docker automatically maps this interface into any container you deploy. What you could additional try is to enable also WIFI of your netPI and try to get in touch with codesys runtime so that the eth0 interface is completely “free” to be used by codesys.
Unfortunately I have not made any experiences with codesys and Ethercat Master but with PROFINET only.
With CODESYS there is nothing else that needs to be done with the eth0 interface. Docker automatically maps this interface into any container you deploy. What you could additional try is to enable also WIFI of your netPI and try to get in touch with codesys runtime so that the eth0 interface is completely “free” to be used by codesys.
Unfortunately I have not made any experiences with codesys and Ethercat Master but with PROFINET only.
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
