Simatic Shell Configuration
Hi there,
We have two SCADAs attatched to Ewon Flexy VPN and are trying to configure the system for us to do remote downloads.
When we connect to the system on the VPN we can access the machines and the shared folders where the SCADA software is kept. But in order to do the downloads we need to be able to be visible on Simatic Shell (we are using TIA V16 Proffesional). We are selecting the TAPV9 Connection to broadcast on but it shows an I.P of 10.29.6.4 but our LAN on the ecatcher is 140.80.50.XXX, how can we get this connection to work?
-
Hello,
THe VPN IP is the IP assigned by the server for your eCatcher connection. It does route the traffic to the LAN ip of the Flexy.
Are you able to ping both IP's?
0 -
Hi,
Yes we are able to ping the servers when we are on the VPN but unable to get into the network folder and see on Simatic Shell
0 -
Apologies,
just to confirm we can get onto the network folder of the SCADA and see all shared folders.
But when it comes to doing a download of the TIA Portal project the error that comes up is the following
0 -
Hello,
Try adding the LAN device in eCatcher. It may require all port communications to be enabled.
Have you tried using both IP's? VPN IP and the LAN IP?
If you are able to ping the devices, you should be able to communicate with them.
0 -
Hi both servers can be seen in the ecatcher vpn setup and we can ping/access network files.
The issue is something to do with Simatic Shell and how that communicates through the SCADA.
This is what is shown in Ecatcher when we remote in
But when we try and connect the Simatic Shell we cannot see the servers, and out I.P is not 140.80.50.xxx, instead it shows it as 10.26.6.4
0 -
Hello.
The 10.29.6.4 is the IP of that specific adapter. So it will be different from the device LAN IP and VPN IP.
Have you reached out to Simatic for assitance for configuring the connection?
0 -
Hi,
not as of yet, was hoping this was something seen before by yourselves. Will raise a support request with them now see if they have come across this before.
0 -
Hello,
I have not seen this kind of issue before, but i will look more in to the issue. Please let me know what Simatic says regarding the configuration of their software.
0 -
Hi Kevin,
after talking with Siemens we have managed to get the simatic shell software to work. The remedy was to add the PC we wanted to connect to as a multicast proxy as shown in the image bellow.
Once this is done it allowed us to connect and download the file through TIA Portal.
Regards,
Vinny0 -
Excellent.
I am glad that you able to resolve the issue.
0 -
Hi Vicent,
I am facing the same problem.
I followed the steps you mentioned. However, the message continues "Check whether the SCS network adapter:"
What do you think it could be?
Regards
0 -
Hello,
You may need to reach out to Siemens regarding the setup of the proxy.
DId you add the device in eCatcher?
0 -
Hi Kevin,
Yes, I've added the device (Scada using WinCC Pro V16) in the eCatcher.
Also, I did like Vicente, in the simatic shell, I added the address as a multicast proxy.
I can ping the address and even put it online. I just can't download the project.
Thank you,
Regards.
0 -
Hello,
You will need to reach out to Siemens to get the correct connection running for Simantic. That is their software. Our device is communicating, and functioning as it should.
0 -
Has anybody actually solved this issue as Siemens class it as an HMS issue and obviously HMS as above are saying its a Siemens issue ?
0 -
Could you submit a ticket to our support portal at https://support.hms-networks.com/ so we can investigate? When you do, please describe your issue in detail as well as the involved devices.
0
Por favor, entrar para comentar.
Comentários
16 comentários