TCP/IP Connect Parameters

You can choose any connection name you like. All characters except brackets may be used.

Destination IP Address (or name)

Here, you can specify the IP address of the destination station (IP address of the PLC) or the DNS name of the destination station. If the device was configured for DNS and a DNS server is available in the network, you can also enter the symbolic name of the destination station.

For information on the structure of IP addresses, please refer to the IP Address section.

Port

Port numbers are addresses that are used on the transport layer in order to address applications. Port numbers are required for TCP connections. Ports are similar to the TSAPs used for RFC 1006 and H1 connections. Each port number is a 16-bit number in the range from 1 to 65535. To establish a connection, please note the following:

You can only establish a connection if the port number is identical on both sides.

Type:

Here, you can specify whether your own station will actively initiate the connection attempt or will wait passively for the destination station to establish the connection. Please make sure that different values are selected on both sides of the connection.


Client (Active)	The station will actively initiate the connection attempt.
Server (Passive)	The station will wait for the destination station to establish the connection.

Protocol

The TCP and UDP protocols are available for selection. TCP is a secured protocol.

PLC Header

For details on the structure of the PLC header, refer to the PLC Header section.

Life Data Acks

If you enable this option, payload frames without content (only headers) are transmitted to keep a connection alive that is not used cyclically (heartbeat monitoring). Both communication partners must support this feature. For the OpcPipe communication, it is recommended to enable this option.

RFC1006

If you enable the RFC1006 option, H1 frames will be “wrapped” in a TCP/IP frame for transport. To configure the TSAPs, click the RFC1006 TSAPs button.

TSAPs (Transport Service Access Points) are addresses that are used on the transport layer in order to address applications. TSAPs are required for RFC 1006 connections. To connect, enter the local TSAP into the Own TSAP field and the TSAP of the communication partner into the Dest TSAP field. In this context, please note the following:

In order to be able to establish the connection, the value in the Own TSAP field of one system must match the Dest TSAP value in the other system, i.e. they must match crosswise.