Internal data points of the IEC driver

_Iec

This is the internal DPT containing the data points _Iec_1, _Iec_2 and _Iec_3. The commands (general query, counter request, etc.) are sent to all connections. For each IEC driver there must be one of these DPs that the user must create, if it does not exist by default.

Element Type Meaning
Control.GQ dyn_string

Writes GQ (general queries) to the specified addresses (1 per line). Format: <Common Address>.0.0.0

The parts of the format are filled with the desired addresses, e.g. 1.111.0.0.0 sends the GQ to Common Address (HB=1, LB=111), Information Object Address (HB=0, MB=0, LB=0)

Control.CounterRequest dyn_string

Writes counter requests to the specified addresses.

Format: <Common Address>.0.0.0

Control.EOI dyn_string

Writes "End of Initialization" to the specified addresses.

Format: <Common Address>.0.0.0

Control.ClockSync dyn_string

Writes clock-sync telegrams to the specified addresses.

Format: <Common Address>.0.0.0

Control.Test dyn_string

Writes test telegrams to the specified addresses.

Format: <Common Address>.0.0.0

Control.Reset dyn_string

Writes reset telegrams to the specified addresses.

Format: <Common Address>.0.0.0

Monitor.GQ string

Monitor direction. Stores incoming GQs.

Format: 100.<Common Address>.0.0.0 (or 100).

100 corresponds to the standards for the general query in monitor direction.

Monitor.CounterRequest string

Received counter requests,

format: 101.<Common Address>.0.0.0

Monitor.EOI string

Received End-of-Init,

format: 70.<Common Address>.0.0.0

Monitor.ClockSync string

Received clock-sync.

Format: 103.<Common Address>.0.0.0

Monitor.Test string

Received test TG.

Format: 107.<Common Address>.0.0.0

Monitor.Reset string

Reset (string): Received reset TG.

Format: 105.<Common Address>.0.0.0

FileTransfer.Command string File transfer command (see section IEC file transfer).
FileTransfer.Status string File transfer status (see section IEC file transfer).
Connections.All dyn_string Names of connections which are started at driver start-up.
Connections.Add string Name of connection which is loaded at runtime.

_IecConnection

The user must create a data point (type: _IecConnections) for each connection. This is done automatically on the IEC panel (see Panel for connections). Elements that only apply to IEC101 are on a white background:

Element Type Meaning
LocalList dyn_string

Addresses of all stations from the local list only accessible via this connection.

Format: "Common Address.Information Object Address".

A value of "*" means "all values between 0 and 255". Use this option sparingly as it causes the driver to send the system telegrams to all possible stations that match this search pattern.

GlobalList dyn_string Addresses of all stations from the global list only accessible via this and other connections (redundant connections). Format etc. see "LocalList".
State bool

TRUE if the driver has a connection to the host, else FALSE.

This internal DPE has been enhanced to a separate node States. with the WinCC OA version 3.10, however, it remains for compatibility reasons.

SendNoReply bool

Only for IEC 101:

Specifies whether the driver should send an acknowledge to a reply (FALSE) or not (TRUE).

ConnectionType bool Not used
ConnectError bool Not used
Control.GQ unsigned

Sends GQ to all nodes of this connection. Value is quality info*), 0 or 20 means "all groups".

If the GQ should not be sent to all nodes of this connection, the GQ must be triggered using the _Iec.Control.GQ data point (the address of the related node is written on the DPE) or via a data point with the peripheral address 100.x.y.0.0.0.

Control.CounterRequest unsigned Sends counter request to all stations on this connection. Value is quality info, 0 or 20 means "all groups".
Control.EOI unsigned

Sends EOI telegram to all stations on this connection.

Value is the quality info.

Control.ClockSync time Sends clock-sync to all stations. Value is time, default 0: system time of sending.
Control.Test unsigned Test telegram to all stations on this connection. Value is quality info.
Control.Reset unsigned

Reset telegram to all stations on this connection.

Value is quality info.

Config.ConnInfo dyn_string

Defines an IEC connection on a device.

Replaces the config entries “connection” and “connection_101”.

This entry (if available) has a higher weight than this from the config file (if available).

  • Format for 104 (1 or more entries):

    104 <host> <port> <timeout> <active>

  • <active>

    Setting per connection

    0 = connection inactive

    1 = connection active

  • Format for 101 (1 entry):

    101 <devName> <101 link address>

Config.Active bool

Indicates whether a connection is (not) active.

FALSE = generally connection not active

TRUE = generally connection active

Config.Flags bit32 Defines whether the connection shall be encrypted (bit0 = 1) or not (bit0 = 0).
Config.ForceActive uint

Defines the selection of the connection in case of a redundancy switch.

0 = connection selection in the event of redundancy automatically

>0 = connection with index X is used fixed for communication

Note: Only relevant for IEC 104.

Config.SetInvalidBit uint

If the connection to the corresponding device is lost or cannot be established, it is possible to automatically set invalid bits for input addresses. This is only possible if an explicit connection name is configured for the peripheral addresses. If the optional connection name is empty, no invalid bit is set.

The following values are possible:

0...do not set invalid bits

1...set invalid bit with current timestamp

2...set invalid bit without changing the source timestamp

States.ConnState uint

State of the connection.

0 = Communication error

1 = Communication OK and started

2 = Communication OK but not started yet

3 = Connection deactivated

States.AllConnStates dyn_uint

State per connection from Config.ConnInfo.

0 = Error

1 = OK, active

2 = OK, inactive

3 = Deactivated

*) In this kind of system telegram, the quality info is not invalid, blocked, etc., but also controls. In a GQ, for example, the quality info is also the "GQ group". You can split the DPs in the PLC into groups and send a GQ to query either all groups (i.e. all values) or only specific groups, e.g. all traffic lights.

This information is sent along with the telegram as quality information. The GQ data point allows you, for example, to send an unsigned int, and defines the GQ group to query, i.e. the quality info. This works exactly the same way for the other system telegrams, counter request, reset, etc.