January-8th-2020, 03:24 PM
Hello Carsten,
configuring netPI Fieldbus Ethernet Interface as standard TCP/IP interface is done in some minutes.
Just load the container "hilschernetpi/netpi-netx-ethernet-lan" on your netPI and configure it in "Host" mode and then you have next to the LAN interface "eth0" another LAN interface "cifX0".
Then you can use the netPI Control Panel to set up IP address or DHCP for "cifX0" first of all.
From now every container you deploy afterwards has two independent LAN interface. One interface you can use then for configuration, and the other for Modbus TCP communication to your Mitsubishi PLC.
Since the "cifx0" interface is not as fast as the "eth0" interface I would connect the Mitsubishi PLC to "eth0" and configure netPI through "cifx0" since no permanent LAN connection and high traffic rate is needed here.
Thx
Armin
configuring netPI Fieldbus Ethernet Interface as standard TCP/IP interface is done in some minutes.
Just load the container "hilschernetpi/netpi-netx-ethernet-lan" on your netPI and configure it in "Host" mode and then you have next to the LAN interface "eth0" another LAN interface "cifX0".
Then you can use the netPI Control Panel to set up IP address or DHCP for "cifX0" first of all.
From now every container you deploy afterwards has two independent LAN interface. One interface you can use then for configuration, and the other for Modbus TCP communication to your Mitsubishi PLC.
Since the "cifx0" interface is not as fast as the "eth0" interface I would connect the Mitsubishi PLC to "eth0" and configure netPI through "cifx0" since no permanent LAN connection and high traffic rate is needed here.
Thx
Armin
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
