September-23rd-2019, 12:07 PM
(This post was last modified: September-23rd-2019, 03:19 PM by Armin@netPI.)
Today I checked the compatibility of the netPI Codesys basis container https://hub.docker.com/r/hilschernetpi/n...sys-basis/ with the latest runtime version of "Codesys for Raspberry Pi MC/SL" in the version V3.5.15.0 along with the Windows Development System CODESYS V3.5 SP15 Patch 1.
I can confirm that this container is still compatible with these versions and can be still used.
Changes since runtime V3.5.15.x:
Since runtime V3.5.15.x the embedded gateway responsible for communication with the Development System is no longer active. This is stated in a CODESYS forum thread at https://forum.codesys.com/viewtopic.php?f=11&t=9974.So trying to setup a communication to the container using the netPI IP address as gateway will fail.
Instead you have to use the gateway that is coming with the Windows Development System running on localhost at port 1217. A click on "Scan network ..." will identify the netPI and the container then successfully:
Here is picture of my successful project (with PROFINET master):
I can confirm that this container is still compatible with these versions and can be still used.
Changes since runtime V3.5.15.x:
Since runtime V3.5.15.x the embedded gateway responsible for communication with the Development System is no longer active. This is stated in a CODESYS forum thread at https://forum.codesys.com/viewtopic.php?f=11&t=9974.So trying to setup a communication to the container using the netPI IP address as gateway will fail.
Instead you have to use the gateway that is coming with the Windows Development System running on localhost at port 1217. A click on "Scan network ..." will identify the netPI and the container then successfully:
Here is picture of my successful project (with PROFINET master):
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
