IP Realtime Ethernet

[michu252]

Hello

How can I change the IP-adress from the realtime-ethernet? In the control Panel under Network isn't it.

Thanks for help

Michu

[Armin@netPI]

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

[Armin@netPI]

Well Michu,

if you want netPI to be a PROFINET IO device then this Docker container is the right one for you: https://hub.docker.com/r/hilschernetpi/n...-examples/

You can start a test application with it immediately and there is also a GSDML file in the source code of this conainer that you can import to TIA.

This container https://hub.docker.com/r/hilschernetpi/n...ernet-lan/ is only if you want netX to be a standarc TCP/IP port. It has no PROFINET functionality activated.

Regards
Armin

[michu252]

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

Hello Armin

I don't understand the instruction of  https://hub.docker.com/r/hilschernetpi/n...-examples/ excactly. I started the excample programm after the installation from the packages, then  it came the errorcode: Error CIFX_HOST_STATE_NOT_READY, state 1, error 0x800C0025 what means there is no physical connection, but it is I checked it manytimes... Is there any parametrization of a file who declarate the master device?

Thanks for help

Michu

[Armin@netPI]

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

Hello Armin

I don't understand the instruction of  https://hub.docker.com/r/hilschernetpi/n...-examples/ excactly. I started the excample programm after the installation from the packages, then  it came the errorcode: Error CIFX_HOST_STATE_NOT_READY, state 1, error 0x800C0025 what means there is no physical connection, but it is I checked it manytimes... Is there any parametrization of a file who declarate the master device?

Thanks for help

Michu

Ok I got your point. After setting the firmware to PROFINET IO Device and after the proper configuration the test program sets its state to what we call "Host ready" to signal the firmware to be ready to exchange IO. The firmware will then be ready to wait for PROFINET master communication. Now the master has to start communication with the firmware ... and this is what the program is waiting for that the PROFINET master exchanges IO data with the netPI. Ín your case this does not happen and this is why an error is reported.

But in order to let a PROFINET master communicate with a fresh IO device properly you have to assign a name to a PROFINET IO device like described here http://profinews.us/2014/04/whats-in-a-p...vice-name/. Have you done this to netPI?

[Armin@netPI]

Is there any parametrization of a file who declarate the master device?

I don't know how familiar you are with PROFINET. Each PROFINET device needs a GSDML file to get recognized by a master/engineering software. Have you imported the Example GSDML file https://github.com/Hilscher/netPI-netx-p...s/PROFINET of netPI to your TIA portal? This is necessary, else TIA don't know netPI at all.

[michu252]

Hello Armin

Thanks for your support. The configuration works and I can send Data from Nod-RED to the Master PLC.

Michu

[Armin@netPI]

Thank you for letting me know. I am happy that it is working now. I am closing this thread then.