User Tools

Site Tools


remote_service_access

Remote service access

Remote service access allows you to implement programming, configuration or diagnostics of automation equipment connected to WebHMI, for example, controllers or frequency drives remotely with the help of standard utilities and development tools of the equipment manufacturer.

The scheme of work is given below. To implement remote service access, VPN technology is used. Both WebHMI and the developer's computer must be connected to the same VPN network, and in the WebHMI network settings, the appropriate rules have to be set for translating network addresses from the VPN network to the target equipment network.

In case the equipment uses a serial port instead of Ethernet, it is enough to install the virtual COM port driver on the computer and use the built-in WebHMI function Virtual COM port. The user can either setup his own VPN network or use the network provided by the Level2 system (recommended).

Connection example

The steps required to implement remote service access are:

  1. Connect the PC you going to use as an access point to the VPN where WebHMI and connected equipment resides
  2. Setup virtual IPs for the equipment to be accessed via TCP/IP, or
  3. Setup virtual COM port function on a WebHMI for the equipment with serial port

Connecting the PC to VPN

Creating a node in Level2 for service PC

First you need to create an account (node) for service PC in Level2 system:

and make (and then check) its settings:

  • mark the VPN checkbox in Services tab
  • Remember VPN login / password in the Information tab - for further PC VPN connectoin
  • In the Routing tab, set the node(s) this service PC can access and add Virtual IP if you want to access equimpent “behind” the WebHMI using Ethernet interface (System with S7-1200 PLC)

Adding a VPN connection in service PC's OS

In Windows 10, press Win key and type 'VPN':

Press 'Add a VPN connection':

Edit its settings according to Level2 settings:

And check adapter properties:

After checking adapter settings try to connect and then check the connection status:

After connecting the PC to the VPN, “ping” the remote WebHMI node(s), which were allowed to access to in Routing tab:

You can check its IP in the node's (System with S7-1200 PLC) Information tab:

Establishing communication with remote devices behind the gateway via TCP / IP

The application structure is given below:

You must enable the Virtual IP address function for the specified WebHMI node. Go the WebHMI's Setup / Level2 menu and switch Virtual IPs lever on:

  1. input the remote PLC's IP address it was assigned in that local network (192.168.0.210)
  2. save the changes, after that a new VPN IP address for the PLC will be created (10.0.0.206).

Now when you want to access the remote PLC (in the example we use Siemens S7-1200 PLC), connect your PC to VPN and you should be able to connect your PLCs via these Virtual IPs.

Here is example how to connect to PLC S7 1200 from TIA Portal.

Connect your PC to VPN and type in your Virtual IP in the advanced download/online access dialog box, as the access Address (in our example, it is 10.0.0.157):

Before this step, check you have a subnet configured for the PLC in its HW Config:

Establishing communication with remote devices behind the gateway via a virtual COM port

The application structure is given below:

Suppose you have some PLC connected to the WebHMI RS-485 port. Go to the connection properties and switch its mode to Virtual UART. Remember the TCP port that was assigned to the connection (8001) and VPN IP address of this WebHMI (10.0.0.204).

Download and setup the driver Perle TruePort for your OS.

Setup new virtual COM port in your system with the TruePort Management Tool:

Check this virtual port settings in the Device Manager:

Connect your PC to the VPN, and use “virtual” COM2 as a communication port in the PLC programming software.

Troubleshooting VPN connection for PC with Windows 10

VPN connection problems were reported sometimes from the Windows 8/10 users. These problems were caused mainly by the following reasons:

  • Firewall settings.
  • Security policy for certain types of VPN traffic in corporate networks.
  • Windows policy for L2TP connections withoun encryption. This one can be fixed with the following registre keys:

remote_service_access.txt · Last modified: 2022/07/14 13:24 by emozolyak

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki