Skip to Content

SiePortal

The integrated platform for your product selection, buying and support workflow - bringing together Industry Mall and Online Support.

SiePortalDeutsch

Search

Home
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menu temporary not available
- Menue temporary not available
- {{item.title}}

Products & Services
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
MySiePortal MySiePortal
{{(apiData.MySiePortal | filter:{'rank':1}:true)[0].title}} MySiePortal
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Cart ({{apiData.CartCount}})

Navigation

Remote programming S7-1200 behind PC

Created by: ChrisCV at: 3/21/2013 6:53 PM (5 Replies)

Rating (0)

Thanks 1

6 Entries

3/21/2013 6:53 PM	Rate (0)
ChrisCV Member Joined: 7/11/2012 Last visit: 3/19/2024 Posts: 3 Rating: (0)	Hello, I have a situation with existing automation equipment, where many different sites all have a single S7-1200 CPU. I am trying to connect remotely to them with Portal V11 to update the PLC code. This has been a headache for me for some time, I hope somebody will have advice for me. Here is the arrangement at each site: S7-1200 IP address 169.254.100.3 is networked via Ethernet with Industrial PC running Windows XP Embedded IP address 169.254.100.1 The industrial PC has a second network adapter with outbound internet access. It runs TeamViewer, and I can connect to it and create a TeamViewer VPN connection from my office. This allows me to direct traffic to an IP address for the industrial PC (typically IP 7.x.x.x) but nothing will be forwarded to the PLC. To get access to the PLC I am currently running software called PassPort on the industrial PC. This will take all Portal V11 traffic (on port 102) intercepted at 7.x.x.x:102 and send it to 169.254.100.3:102. It will also do the reverse, intercepting the return traffic addressed to the industrial PC at 169.254.100.1:102 and redirecting it to my work laptop (running Win7) at 7.y.y.y:102. This leaves me with one last problem, as I see it. In my Portal V11 project the PLC address is 169.254.100.3, so that is the address Portal attempts to connect to. If I could possibly redirect the outgoing packets to 7.x.x.x it would all work! My current workaraound is to have another laptop in the office running WindowsXP at the IP address 169.254.100.3. This laptop poses as the PLC, then redirects the outbound traffic (again, using PassPort) from my laptop to the industrial PC at 7.x.x.x, and then redirects the inbound traffic from itself back to Portal V11 on my laptop. Can anyone suggest a better method of doing this? I now have Win7<->WinXP<->WinXPe<->S7-1200, which actually works, but is ridiculous and problematic. It doesn't work for sytems behind VPNs or when I am travelling. I have tried adding netsh ipv4 routing entries, and other port forwarding software, and loopback interfaces, and forwarding through virtual machines, but the networking stuff really isn't my expertise. I also can not justify the cost or travel involved in changing the on-site hardware. If you have some thoughts, I would love to hear them. Thanks in advance, Chris

Suggestion To thank Quote Answer

3/21/2013 9:06 PM	Rate (0)
mark1507 Platinum Member Joined: 6/23/2008 Last visit: 2/9/2025 Posts: 1168 Rating: (283)	Hi, I don't know TIA portal yet and I also don't know S7-1200. But I had a similar task with Step7 and a S7-300 CPU connected via an ethernet CP. Is it possible to configure a router in the project for the ethernet interface of the CPU? If yes, put the public adress of the IPC there (7.x.x.x). If not, try the following: Just put the puplic adress (7.x.x.x) in your project to the place where normally the private one (169.254.100.3) is configured. Do not download the Hardware configuration to the CPU. You should be able to go online and download blocks only (if you would download the hardware configuration the CPU would not be accessible after that). Regards
	"Expert" does not necessarily mean Siemens employee. Please cross-check your requirements always with official Siemens documentation. Also "Experts" are pleased about feedback. Please don't send support requests as PM. Questioners who don't follow up their thread will be put to my list of users to be ignored.
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users Tomy Master

3/26/2013 12:57 AM	Rate (0)
ChrisCV Member Joined: 7/11/2012 Last visit: 3/19/2024 Posts: 3 Rating: (0)	Thank you very much for the advice, Mark! I don't have everything working yet, but I am much further along now. You are right that I can replace the target IP address in my project (169.254.100.3 becomes 7.x.x.x) and then download new software. I now realize that this works as long as I do NOT download the hardware configuration, because that would change the working IP of the PLC and make it inaccessible. I also attempted your other suggestion, there is a field in the PLC h/w config for "IP router". I can put 7.x.x.x in as the IP router, and 169.254.100.3 in as the IP address. That comes close to working, but because of the mismatch in subnets Portal V11 always attempts to grab a new IP address before connecting (presumably in 169.254...). Because my PLCs are always behind a VPN, either with TeamViewer or a customer's company VPN, the additional IP address fails and the connection falls apart. So currently I'm limited to updating software. I would like to update hardware too because at one point I changed the mode of a high speed counter from quadrature to single-phase counting. As a result different sites have different counter configurations, and I don't believe the mode can be set in the software. But I can certainly work around that. Thanks again!

Suggestion To thank Quote Answer

11/5/2013 2:43 PM	Rate (0)
4ntares Advanced Member Joined: 2/7/2011 Last visit: 3/20/2024 Posts: 10 Rating: (0)	Hy. Did you managed to solve the connection to the PLC through VPN? I'm also interested in the solution.

Suggestion To thank Quote Answer

11/5/2013 8:18 PM	Rate (0)
Sprawl Posts: 58 Rating: (10)	This is more like a question for the TeamViewer Forum right? Anyway here's an example how it should work - without any IP changes necessary within Step7. Enable the TeamViewer VPN option on both PCs. PC on Site: (this one got 2 network adapters) Subnet 2 IP x.x.x.x (www connection, does not matter) PLC Subnet IP 192.168.1.1 VPN IP 7.7.7.111 virtual VPN interface PLC: IP: 192.168.1.x Gateway:192.168.1.1 (PCs IP) PG: Real IP: x.x.x.x (not allowed is 192.168.1.x) VPN IP 7.x.x.x virtual VPN interface (does not matter) For the PC on Site: Start > Run > regedit Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\IPEnableRouter Set to 1. Reboot. At your PG, after the VPN is set up: Start > run > cmd route add 192.168.1.0 mask 255.255.255.0 7.7.7.111
Sprawl Posts: 58 Rating: (10)
Suggestion To thank Quote Answer

1/21/2014 7:18 PM	Rate (0)
GrasserF Posts: 340 Rating: (6)	new question is splittet to S7-1200 PLC1214C, connect via over Teamviwer
GrasserF Posts: 340 Rating: (6)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on