• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Siemens PLC -Uploading and downloading using netPI & VPN
#20
I see you setup a "tbnet" network of 192.168.0.0. It might be bad if your eth0 is set to IP address 192.168.251.1 at the same time which is in the same subnetk. I don't know exactly since I am no IT expert, but it might be possible.

Here is what I recommend to you and to your customer always: do not use an extra network like "tbnet" at all. For customers and you it is easier to use standard "brigde" network always that comes with Docker by default. It is not needed to define extra network even if the documentation tells it. I am doing it the same always. In this case Docker automatically assigns the TOSIBOX container automatically a network and IP address and range. It is easier to setup.

So stop and remove your current container and redeploy it and during deployment use standard "bridge" mode instead of "tbnet". This is how I tested it with my S7-1200 PLC as well. After that setup a static route to 192.168.253.0 at subnetmask 255.255.255.0. This is all you need to do.

I see you setup also a NL50MPI extra. This is also not necessary. Once you setup the routing and restart netPI again then automatically the network 192.168.253.0 - 255 is available on your remote machine and you can ping your PLC over netLINK MPI at 192.168.253.5 immediately.
You never fail until you stop trying.“, Albert Einstein (1879 - 1955)

  Reply


Messages In This Thread
RE: Siemens PLC -Uploading and downloading using netPI & VPN - by Armin@netPI - July-20th-2020, 09:03 AM

Possibly Related Threads…
Thread Author Replies Views Last Post
  Profinet to Siemens PLC j.langlois 4 3,758 January-26th-2021, 06:11 PM
Last Post: j.langlois
  Detecting NetPI in Siemens TIA via Profinet andrewc 3 4,042 April-11th-2019, 06:42 PM
Last Post: Armin@netPI

Forum Jump:


Users browsing this thread: 1 Guest(s)