August-16th-2018, 06:57 AM
Hello Michu,
the Real-Time Ethernet interface can only be activated from a Docker container and not from the control panel.
This is because the RTE interface can be PROFINET or EtherNet/IP or EtherCAT on one hand or in simplest case a plain Ethernet LAN interface on the other. And you as a user decide what the purpose of this interface is. Since we cannot predict your use case ... there is no web interface available for the RTE ports.
There are Docker example container images available for
A.) Using the RTE ports as PROFINET, EtherNet/IP, EtherCAT here: https://hub.docker.com/r/hilschernetpi/n...-examples/
B.) Using the RTE ports as standard Ethernet port here: https://hub.docker.com/r/hilschernetpi/n...ernet-lan/
Thx
Armin
the Real-Time Ethernet interface can only be activated from a Docker container and not from the control panel.
This is because the RTE interface can be PROFINET or EtherNet/IP or EtherCAT on one hand or in simplest case a plain Ethernet LAN interface on the other. And you as a user decide what the purpose of this interface is. Since we cannot predict your use case ... there is no web interface available for the RTE ports.
There are Docker example container images available for
A.) Using the RTE ports as PROFINET, EtherNet/IP, EtherCAT here: https://hub.docker.com/r/hilschernetpi/n...-examples/
B.) Using the RTE ports as standard Ethernet port here: https://hub.docker.com/r/hilschernetpi/n...ernet-lan/
Thx
Armin
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
