SIMATIC S7: Configuring the access path

The available access paths and settings for each access path are displayed below.

Direct access to an S7 controller via TCP/IP

Zugriff auf S7 Steuerung über TCP/IP


Image:Access to S7 controller via TCP/IP

  1. Select the access path [0141] PC > [TCP/IP] > AS.

  2. Enter the IP address of the controller.

  3. Enter the rack and slot of the CPU.

 

Access to an S7 controller in the SINUMERIK 840D (with HMI Advanced)

Zugriff auf S7 Steuerung in der Sinumerik 840D (mit HMI Advanced)


Image: Access to S7 control in Sinumerik 840D (with HMI Advanced)

  1. Select the access path [0142] > [TCP/IP] >Gateway> [MPI/Profibus] > AS.

  2. Enter the IP address of the gateway.

  3. Enter 0000-0000 as the S7 subnet ID.

  4. Configure the routing in the versiondog Gateway to the S7 in the MPI/PROFIBUS network.

  5. Enter the rack and slot of the CPU.

 

Access to an S7 controller via a head controller

Zugriff auf S7 Steuerung über eine Kopfsteuerung


Image: Access to S7 control via head control

  1. Select the access path [0142] > [TCP/IP] > Gateway> [MPI/Profibus] > AS.

  2. Enter the IP address of the head controller.

  3. Enter the subnet ID for the MPI/PROFIBUS network using the accessible head controller

  4. Enter the rack and slot of the CPU.

 

Access to an S7 controller in the MPI/PROFIBUS network (accessible via a computer with versiondog Gateway)

Zugriff auf S7 Steuerung im MPI/PROFIBUS-Netzwerk (über einen Rechner mit versiondog Gateway erreichbar)


Image: Access to S7 controller in MPI/PROFIBUS network (accessible via a computer with versiondog gateway)

  1. Select the access path [0142] > [TCP/IP] > Gateway> [MPI/Profibus] > AS.

  2. Enter the IP address of the gateway.

  3. Enter 0000-0000 as the S7 subnet ID.

  4. In the versiondog Gateway, configure the routing to match up with the S7 in the MPI/PROFIBUS network.

  5. Enter the rack and slot of the CPU.

If the gateway to the MPI/PROFIBUS network is done using the versiondog Gateway, the address 0000-0000 must be entered as the S7 subnet ID. In the versiondog Gateway, the routing to the S7 in the MPI/PROFIBUS network must be configured.

 

Access to a S7 controller in a MPI network (connected to the TCP/IP network via a converter (e.g. IBH-Link))


Image: Access to S7 control in MPI network (connected to TCP/IP network via a converter (e.g. IBH-Link)

  1. Select the access path [0143]PC > [TCP/IP] > Converter > [MPI] > AS.

  2. Enter the IP address of the converter.

  3. Enter the subnet ID for the MPI network via which the controller is accessible.

  4. Enter the rack and slot of the CPU.

 

Access to a S7 controller in a PROFIBUS network (connected to the TCP/IP network via a converter (e.g. IBH-Link)).

Zugriff auf S7-Steuerung im PROFIBUS-Netzwerk (über einen Konverter (z.B. IBH-Link) mit dem TCP/IP-Netzwerk verbunden)


Image: Access to S7 control in MPI network (connected to TCP/IP network via a converter (e.g. IBH-Link)

  1. Select the access path [0144]PC > [TCP/IP] > Converter > [PROFIBUS] > AS.

  2. Enter the IP address of the converter.

  3. Enter the subnet ID for the PROFIBUS network via which the controller is accessible.

  4. Enter the rack and slot of the CPU.

 

Access to an S7 controller in ISO Ethernet via a head controller

Zugriff auf S7 Steuerung im ISO-Ethernet über eine Kopfsteuerung


Image: Access to S7 controller in ISO-Ethernet via a head controller

  1. Select the access path [0145]PC > [TCP/IP] > Gateway> [H1] > AS.

  2. Enter the IP address of the head controller.

  3. Enter the subnet ID for the ISO Ethernet.

  4. Enter the H1 address of the controller that you want to be backed up.

  5. Enter the rack and slot of the CPU.

 

Access to a S7 controller in ISO-Ethernet via the versiondog Gateway

Zugriff auf S7 Steuerung im ISO-Ethernet über das versiondog Gateway


Image: Access to S7 controller in ISO-Ethernet via versiondog gateway

  1. Select the access path [0145]PC > [TCP/IP] > Gateway> [H1] > AS.

  2. Enter the IP address of the gateway.

  3. Enter 0000-0000 as the S7 subnet ID.

  4. Configure the routing in the versiondog Gateway to the ISO Ethernet.

  5. Enter the H1 address and the rack and slot of the CPU.

 

Access to a S7 controller in a MPI/PROFIBUS network via Echolink

Zugriff auf S7 Steuerung in einem MPI/PROFIBUS-Netzwerk über Echolink


Image: Access to S7 controller in a MPI/PROFIBUS network via Echolink

  1. Select the access path [0146] > [TCP/IP] > Echolink > [MPI/PROFIBUS] > AS.

  2. Enter the IP address of the Echolink hardware and the interface number to identify the subnet via which the controller can be reached.

  3. Enter 0000-0000 as the subnet ID.

  4. Configure the MPI/PROFIBUS address.

  5. Enter the rack and slot of the CPU.

 

Backing up an non-networked S7 controller with the BackupClient via the ISO Ethernet

Sicherung einer unvernetzten S7 Steuerung mit dem BackupClient über das ISO-Ethernet


Image: Backup of an unnetworked S7 controller with the BackupClient via ISO-Ethernet

  1. Select the access path [0101] PC > [H1] > AS.

  2. Enter the H1 address with rack and slot of the CPU.

The H1 driver must be installed on the computer on which the BackupClient is installed.

 

Backing up an non-networked S7 controller with the BackupClient via MPI/PROFIBUS

Sicherung einer unvernetzten S7-Steuerung mit dem BackupClient über MPI/PROFIBUS


Image: Backup of an unnetworked S7 controller with the BackupClient via MPI/PROFIBUS

  1. Select the access path [0181]PC > [MPI/PROFIBUS]> AS.

  2. Enter the MPI/PROFIBUS address and the rack and slot of the CPU.

 

The MPI/PROFIBUS driver must be installed on the computer on which the BackupClient is installed.

 

Backing up a S7 controller in the MPI/PROFIBUS network with the BackupClient via an non-networked head controller

Sicherung einer S7 Steuerung im MPI/PROFIBUS-Netzwerk mit dem BackupClient über eine unvernetzte Kopfsteuerung


Image: Backup of an S7 controller in the MPI/PROFIBUS network with the BackupClient via an unnetworked head controller

  1. Select the access path [0182]PC > [MPI/PROFIBUS] > Gateway> [MPI/PROFIBUS] > AS.

  2. Enter the MPI/PROFIBUS address of the head controller.

  3. Enter the subnet ID for the PROFIBUS network via which the controller can be reached using the head controller.

  4. Enter the MPI/PROFIBUS address and the rack and slot of the CPU.

The MPI/PROFIBUS driver must be installed on the computer on which the BackupClient is installed.

 

Backing up an S7 controller connected to a head controller via the PROFINET network

Sicherung einer S7-Steuerung (über das PROFINET mit einer Kopfsteuerung verbunden)


Image: Backup of a S7 controller (connected to a head controller via PROFINET)

  1. Select the access path [0147]PC > [TCP/IP] > Gateway> [TCP/IP] > AS.

  2. Enter the IP address of the head controller.

  3. Enter the subnet ID for the PROFINET network via which the controller can be reached using the head controller.

  4. Enter the IP address in the subnet.

  5. Enter the rack and slot of the CPU.

If the gateway to the MPI/PROFIBUS network is done using the versiondog Gateway, the address 0000-0000 must be entered as the S7 subnet ID. In the versiondog Gateway, the routing to the ISO-Ethernet must be configured.

 

Backing up an S7 controller via Echochange

Sicherung einer S7-Steuerung über Echochange


Image: Backup of a S7 control via Echochange

  1. Select the access path [0148] > [TCP/IP] > Echochange > [H1][TCP/IP] > AS.

  2. Enter the IP address of the Echochange hardware.

  3. Enter the rack and slot of the CPU.

The routing must also be configured in the Echochange.

When using the H1 protocol:

The versiondog server cannot communicate with an access path via a main device.
Please check if your type of device is routing compatable. If the CP device is not suitable for routing, you will not be able to communicate with the MPI/Profbius subnet via the main device.

 

When using a IBH-Link:

Image: Dialog IBH-Link settings

FAQ:: When accessing the S7 controller via the IBH-Link, one of the following two errors is produced. Can these errors be corrected?


Image: Eventlog module, no driver installed via IBH-Link

If this error is issued, no driver for IBH-Link has been installed. This driver is not supplied with versiondog , but must instead be obtained and installed separately via the website https://www.ibhsoftec.com/DL-IBHNet.


Image: Module Eventlog, connection via port not possible

If this error is issued, the connection via the port is not possible. Unlock the port in the firewall or configure another port for the IBH-Link.

 

To FAQ list

 

Related topics:
Upload & Compare Agents