November-26th-2019, 06:04 PM
Well Patrick,
it depends on your application. A netPI CORE 3 is like a standard Raspberry Pi 3B. It comes with a single ethernet port named eth0 that is able to drive PROFINET, EtherCAT or Ethernet/IP master with the embedded software protocol stacks of CODESYS. With a single ethernet port it is not possible to divide the PROFINET network segment from the IT network segment. netPI RTE 3 has 3 ethernet ports where the two additional ones are normally used with real-time ethernet slave functionality across the embedded netX industrial controller. But with a special firmware the netX controller can also speak standard TCP/IP ... not as fast as a real ethernet chip ... but fast enough to connect the CODESYS programming system to netPI RTE 3. So the eth0 port of netPI RTE 3 is used for PROFINET master communication and the two other ports as maintenance port to CODESYS windows programming system. In this case you have divided the two network segment.
An alternative that works with both netPIs is to use WIFI as second port. So maintaining CODESYS runtime in netPI across a Wifi router can work as well. eth0 will still be the PROFINET master port in this case. But this setup needs a WIFI access point. It depends if you have any or not.
I think you have recognized that all software with standard HIlscher OS delivered with netPI is deployed using Docker containers. The container to load and its README is located here: https://hub.docker.com/r/hilschernetpi/n...sys-basis/ . It gives you also a link to the youtube video
Thx
Armin
it depends on your application. A netPI CORE 3 is like a standard Raspberry Pi 3B. It comes with a single ethernet port named eth0 that is able to drive PROFINET, EtherCAT or Ethernet/IP master with the embedded software protocol stacks of CODESYS. With a single ethernet port it is not possible to divide the PROFINET network segment from the IT network segment. netPI RTE 3 has 3 ethernet ports where the two additional ones are normally used with real-time ethernet slave functionality across the embedded netX industrial controller. But with a special firmware the netX controller can also speak standard TCP/IP ... not as fast as a real ethernet chip ... but fast enough to connect the CODESYS programming system to netPI RTE 3. So the eth0 port of netPI RTE 3 is used for PROFINET master communication and the two other ports as maintenance port to CODESYS windows programming system. In this case you have divided the two network segment.
An alternative that works with both netPIs is to use WIFI as second port. So maintaining CODESYS runtime in netPI across a Wifi router can work as well. eth0 will still be the PROFINET master port in this case. But this setup needs a WIFI access point. It depends if you have any or not.
I think you have recognized that all software with standard HIlscher OS delivered with netPI is deployed using Docker containers. The container to load and its README is located here: https://hub.docker.com/r/hilschernetpi/n...sys-basis/ . It gives you also a link to the youtube video
Thx
Armin
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
