Driver-specific functions

This driver supports the following functions:

INAT board (optional)

This card can replace an original Siemens CP-443-1/TCP.
The requests are handled via RFC 1006. The definition of the send/receive orders is done in the INAT configurator.
On the zenon side, you have to enter the same own and remote TSAPs have as on the according board.
Several simultaneous and parallel connections are possible.
If several independent zenon servers communicate with one card, a separate connection for each server has to be defined on the INAT-CP.
The card can handle S5 and S7 protocols simultaneously.
The configuration on the PLC is realized by creating a configuration block in OB 100 resp. 101 (for restart), i.e. synchronizing the CPU with the board.
In a cyclically called block the block NET_ALL is called (like in an S5 Send-All/Receive-All), which handles the data communication with the CPU.

F&S (Fischer & Schmidt)

In order to be able to use the datatypes for F&S, they must be activated explicitly. This activation is defined with the following entry in the project.ini file
[S7TCP]
FS=1

Alarm-S channel

With the datatype ALARM_S message bit spontaneously realtime-stamped alarm messages of the S7 can be received (e.g. from PDiag). This variable only has a value, when the S7 sends an ALARM_S telegram. No initial image or similar thing is read. The offset here is the S7 message number.
A variable of type ALARM_S message doubleword always contains the last received message number. The offset is not used here and has to be 0.

Variables of the type 'ALARM_S associated value' contain the associated values received with a message, if they exist. Also here the offset contains the S7 message number. The addressing of the associated value in the associated value record is realized with the bit number. If e.g. 3 associated values of the type Byte are received, the first one has bit number 0, the second has bit number 8 and the third has bit number 16. When transmitting PDiag associated values, a doubleword is always sent . . In the doubleword the low byte and the high byte are permuted; this has to be cared of in the addressing of the bit number.

Example:
Associated value = bit: offset = message number / bit number = 24
associated value = byte offset = message number / bit number = 24
associated value = word offset = message number / bit number = 16
associated value = double word offset = message number / bit number = 0

Limitations

In projects with the S7 TCP driver please be aware, that S7 PLCs only have limited communication resources. This becomes noticeable with the S7 300 types, that particularly for the smaller models allow only a few (6-12) simultaneous communications.

Example:
S7 312C only allows 6 connections, where as a default 4 are reserved, so that only 2 simultaneous connections are possible.
All reserved connections with the exception of the PD communication and an OP communication can be released, so for a S7 312C a maximum of 4 free connections is available.
S7 414-2 allows 32 connections, 4 reserved as a default, and 28 additional possible.

Access to S7-200 via CP243, in S7 200 only DB 1 exists.

project.ini entries

[S7TCP]
BLOCKWRITE=1	Activates blockwrite