June-20th-2018, 02:01 PM
Hello Florian,
yes this is possible. You have to turn the two ethernet ports of netX chip into standard ethernet ports away from their real-time ethernet capability. This requires to load a different firmware into the netX network controlle chip.
How you do this is available as ready to load container located here https://hub.docker.com/r/hilschernetpi/n...ernet-lan/. Read the page for more details.
When you start the container it creates next to the existing eth0 port (standard raspberry port) another LAN port named cifx0 in the container you can assign an IP address to. Then you can add your modbus tcp client app afterwards and set the modbus tcp/ip server (same subnet) in accordance to the ip address set up for cifx0 interface and all the TCP/IP frames will leave the two extra RJ45 port right away to your modbus server.
yes this is possible. You have to turn the two ethernet ports of netX chip into standard ethernet ports away from their real-time ethernet capability. This requires to load a different firmware into the netX network controlle chip.
How you do this is available as ready to load container located here https://hub.docker.com/r/hilschernetpi/n...ernet-lan/. Read the page for more details.
When you start the container it creates next to the existing eth0 port (standard raspberry port) another LAN port named cifx0 in the container you can assign an IP address to. Then you can add your modbus tcp client app afterwards and set the modbus tcp/ip server (same subnet) in accordance to the ip address set up for cifx0 interface and all the TCP/IP frames will leave the two extra RJ45 port right away to your modbus server.
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
