Skip to content

Configuring the access path

The available access paths and settings for the individual access paths are shown below.

Direct access to an S7 Controller using TCP/IP

Figure: Access to S7 Controller via TCP/IP

  1. Select the access path [0141] > [TCP/IP] > AS.
  2. Enter the IP address of the controller.
  3. Enter the rack and slot of the CPU.

Accessing an S7 controller in Sinumerik 840D (with HMI Advanced)

Figure: Access to S7 Controller in the Sinumerik 840D (with HMI Advanced)

  1. Select the access path [0142] > [TCP/IP] > Network transition > [MPI/Profibus] > AS.
  2. Enter the IP address of the network transition.
  3. Enter 0000-0000 as the S7 Subnet ID.
  4. Configure the routing in the 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

Figure: Access to S7 Controller via a head controller

  1. Select the access path [0142] > [TCP/IP] > Network transition > [MPI/Profibus] > AS.
  2. Enter the IP address of the head controller.
  3. Enter the Subnet ID for the MPI/PROFIBUS network using which the controller can be accessed.
  4. Enter the rack and slot of the CPU.

Access to an S7 Controller in the MPI/PROFIBUS network (accessible using a computer with gateway)

Figure: Access to S7 Controller in the MPI/PROFIBUS network (accessible via a computer with versiondog Gateway)

  1. Select the access path [0142] > [TCP/IP] > Network transition > [MPI/Profibus] > AS.
  2. Enter the IP address of the network transition.
  3. Enter 0000-0000 as the S7 Subnet ID.
  4. Configure the routing in the Gateway to the S7 in the MPI/PROFIBUS network.
  5. Enter the rack and slot of the CPU.

Info

If the network transition to the MPI/PROFIBUS network takes place via the Gateway, the address 0000-0000 must be entered as the S7 Subnet ID. Routing to the S7 in the MPI/PROFIBUS network must be configured in the Gateway.

Figure: Access to S7 Controller in the MPI network (connected to the 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 through which the controller can be accessed.
  4. Enter the rack and slot of the CPU.

Figure: Access to S7 Controller in the PROFIBUS network (connected to the 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 through which the controller can be accessed.
  4. Enter the rack and slot of the CPU.

Accessing an S7 Controller in the ISO Ethernet via a head controller

Figure: Access to S7 Controller in ISO Ethernet via a head controller

  1. Select the access path [0145]PC > [TCP/IP] > Network transition > [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 is to be secured.
  5. Enter the rack and slot of the CPU.

Access to an S7 Controller in the ISO Ethernet via the Gateway

Figure: Access to S7 Controller in ISO-Ethernet via the versiondog gateway

  1. Select the access path [0145]PC > [TCP/IP] > Network transition > [H1] > AS.
  2. Enter the IP address of the network transition.
  3. Enter 0000-0000 as the S7 Subnet ID.
  4. Configure the routing in the Gateway to the ISO Ethernet.
  5. Enter the H1 address with rack and slot of the CPU.

Figure: Access to S7 Controller in an 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 no. to identify the subnet through which the controller can be accessed.
  3. Enter 0000-0000 as the Subnet ID.
  4. Configure the MPI/PROFIBUS address.
  5. Enter the rack and slot of the CPU.

Backup of an unnetworked S7 Controller with the BackupClient via the ISO Ethernet

Figure: Backup of an unnetworked S7 Controller with the BackupClient via the ISO Ethernet

  1. Select the access path [0101] PC > [H1] > AS.
  2. Enter the H1 address with rack and Slot of the CPU.

Info

The H1 driver must be installed on the computer with the BackupClient.

Backup of an unnetworked S7 Controller with the BackupClient via MPI/PROFIBUS

Figure: 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 with rack and slot of the CPU.

Info

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

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

Figure: 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] > Network transition > [MPI/PROFIBUS] > AS.
  2. Enter the MPI/PROFIBUS address of the head controller.
  3. Enter the Subnet ID for the PROFIBUS network through which the controller can be reached using the head controller.
  4. Enter the MPI/PROFIBUS address with rack and slot of the CPU.

Info

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

Backup of an S7 Controller connected to a head controller via the PROFINET network

Figure: Backup of an S7 Controller (connected to a head controller via PROFINET)

  1. Select the access path [0147]PC > [TCP/IP] > Network transition > [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 via the head controller.
  4. Enter the IP address in the subnet.
  5. Enter the rack and slot of the CPU.

Info

If the network transition to the MPI/PROFIBUS network takes place using the Gateway, the address 0000-0000 must be entered as the S7 Subnet ID. Routing to the ISO Ethernet must be configured in the Gateway.

Backup of an S7 Controller via Echochange

Figure: Backup of an S7 Controller 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.

Info

The routing must also be configured in the Echochange.

When using the H1 protocol:

  • The INAT H1 driver is required for connections using the H1 protocol. This is supplied with versiondog and can be used up to and including Windows Server 2008. If the versiondog server is to be installed on a computer, on which the driver is not functional, either

    • another H1 driver must be installed that is functional on the server operating system or
    • the upload via agent must be executed using a computer on which the driver is installed.

  • When using the H1 protocol, it is recommended to deactivate the QoS packet scheduler on the corresponding network card.

  • When using the H1 protocol, the H1 protocols of other manufacturers must be deactivated on the corresponding network card.

Warning

When using an access path through a head controller, the versiondog server cannot communicate with the controller.

Check whether the CP module of your head controller is routable. If the CP module is NOT routable, communication using the head controller in the MPI/Profibus subnet is not possible.

When using IBH-Link:

  • An additional driver is required for the converter (IBH-Link). This is not supplied with versiondog, but must be obtained and installed separately using the website https://www.ibhsoftec.com/DL-IBHNet.
  • Communication does not run directly through the application VDogUpload.exe but instead through IBH_NETPCOM.exe. This is accessible through port 1099 by default. Port 1099 must be enabled in the firewall.

Figure: IBH-NETPCOM.exe Properties

  • Alternatively, another port can be configured using the configuration software of the driver in the IBHLink settings dialog.

Figure: IBH link settings dialog

FAQ

Errors are being displayed when accessing the S7 Controller via IBH-Link

Figure: Event log module, no driver installed via IBH-Link

If this error is displayed, no driver for IBH-Link is installed. The driver is not included in versiondog , but must be obtained and installed separately via the website https://www.ibhsoftec.com/DL-IBHNet.

Figure: Module event log, connection via port not possible

If this error is displayed, no driver for IBH-Link is installed. The driver is not included in versiondog, but must be obtained and installed separately using the website https://www.ibhsoftec.com/DL-IBHNet.

If this error is displayed, the connection using the port is not possible. Enable the port in the firewall or configure another port for IBH-Link.