Configuring a routable network transition¶

The gateway can also be used to configure a routable network transition to H1, MPI or PROFIBUS. The network transition to H1, MPI or PROFIBUS can be extended via configuration so that communication with an automation device that can only be reached indirectly via a head controller is possible via the gateway.

Figure: Diagram of routing-capable network transition

Prerequisites¶

The network transition to H1, MPI or PROFIBUS must be possible for the head controller.
The address of the head controller is determined via the SubNetId in the job configuration of the AdminClient ( S7 Subnet ID field under Access path details). If the SubNetId is not found, the configuration of the VDogGateway.ini file can be used to define how the gateway should react.

Configuration of the gateway¶

The settings for the Gateway are configured using the INI file VDogGateway.ini. The file can be found under: {Drive}:\vdoggateway\VD$A\Configuration\

Open the VDogGateway.ini file using a text editor, for example Notepad++.
Implement the desired settings. Possible settings can be found in the following table.
Save the data and close the text editor.

Sections of the VDogGateway.ini file¶

[Rfc1006]¶

This section is used to configure the gateway from TCP/IP to H1, MPI or PROFIBUS.

Key	Description	Value	Default
Enabled	Key for activating communication via RFC 1006	Y/N	Y

[gw2gw]¶

This section is used to configure routing via an S7 head controller.

Key	Description	Value	Default
Adr{n}	Key for configuring a routing path. n n is an integer Id. Mandatory field	{SubnetId},{Gateway address} . The valid format of the SubNetId is: HHHH-HHHH, where H stands for a hexadecimal digit, there is no distinction between upper and lower case. Valid formats for the address of the gateway are: - H1-Address: HH-HH-HH-HH-HH-HH, where H stands for a hexadecimal digit, there is no distinction between upper and lower case letters. - IP-Address: n.n.n.n (n is a number from 0 to 255)
BehaviourSubNetIdNotFound	Key for configuring behavior in the event that the SubNetId is not found.	0 or 1 - 0: The error is ignored, the routing is omitted, the communication for the network transition to H1, MPI or PROFIBUS is applied. - 1: Communication process aborted with error. If a non-valid value is defined here (neither 0, 1 or empty), the connection is terminated and an error is written to the internal event log of the gateway.	0

Example configuration¶

[Rfc1006]
Enabled=Y
[gw2gw]
Adr0=004C-0013,10.0.0.221
BehaviourSubNetIdNotFound=1

AdminClient -> INI files