Description of formal parameters

Name

Type

Data Type

Description

interfaceId

IN

HW_ANY

HW ID of the used interface

connectionId

IN

CONN_OUC

Unique connection ID of the send block (TSEND_C)

localPort

IN

UINT

Local port number

reset_com

IN

BOOL

FALSE: No reset (default) TRUE: Communication connection reset

DB_PDA

INOUT

DB_ANY

DB for the ibaPDA communication interface ibaREQsym_DB_PDA

state

OUT

STRING[16]

Block status

errorTsend

OUT

WORD

Collective error code for the internally called Tsend blocks

errorTcon

OUT

WORD

Error code for the internally called Tcon block

errorTusend1

OUT

WORD

Error code for the internally called Tusend1 block

errorTusend2

OUT

WORD

Error code for the internally called Tusend2 block

lostSamples

OUT

UNIT

Counter for lost measured values

The following SIMATIC standard blocks are used internally:

  • TCON

  • TUSEND

  • TDISCON
Detailed description

interfaceId

The HW ID of the used interface is a constant in TIA Portal and dependent on the configured hardware.

connectionId

Unambiguous reference to the connection to be established, value range: 1 to 4095.

localPort

Number of the local port used

reset_com

Used to manually reset the communication connection.

DB_PDA

Pointer to the communication data range. This range is used for the data exchange with ibaPDA. For all related Request blocks, configure the identical DB.

state

Block status in plain text

errorTsend

Collective error code for the internally called Tsend blocks

errorTcon

Error code for the internally called Tcon block

errorTusend1

Error code for the internally called 1st Tusend block

errorTusend2

Error code for the internally called 2nd Tusend block

A list of all possible error codes for the Tsend, Tusend, Tcon system blocks can be found in the Siemens documentation.

lostSamples

The counter is incremented each time a block is called if a new UDP telegram cannot be sent to ibaPDA because the preceding send job has not yet been completed. A constantly increasing value indicates a bottleneck in communication performance.
Error codes

errorTcon

Hexadecimal value Status info

Description

W#16#0000

Connection successfully established.

W#16#7000

No job processing is active.

W#16#7001

Start job execution, establish connection.

W#16#7002

Connection is being established (REQ irrelevant).

Hexadecimal value Error

Description

W#16#8085

Connection ID (ID parameter) is already used by a configured connection.

W#16#8086

The ID parameter is outside the valid range.

W#16#8087

Maximum number of connections reached; no additional connection possible.

W#16#8089

The CONNECT parameter does not point to a connection description or the connection description was created manually.

W#16#809A

The structure at the CONNECT parameter is not supported on an integrated interface or the length is invalid.

W#16#809B

The element interfaceld with in the TCON_xxx structure does not reference a hardware identifier of a CPU or CM/CP interface or has the value "0".

W#16#80A1

The specified connection or the port is already used.

W#16#80A2

Local or remote port is used by the system. The following ports are reserved locally: 20, 21, 80, 102, 135, 161, 162, 443, 34962, 34963, 34964 as well as the area 49152 to 65535.

W#16#80A3

ID is used by a connection created by the user program, which uses the same connection description at the CONNECT parameter.

W#16#80A4

IP address of the remote connection endpoint is invalid, or it matches the IP address of the local partner.

W#16#80A7

Communication error: You executed TDISCON before TCON had completed.

W#16#80B4

Only with TCON_IP_RFC: The local T selector was not specified, or the first byte does not contain the value 0x0E (only with a length of T selector = 2) or the local T selector starts with "SIMATIC-".

W#16#80B5

Only passive connection establishment is permitted for connection type 13 = UDP (parameter ActiveEstablished of the structure TCON_IP_v4/TCON_PARAM has the value TRUE).

W#16#80B6

Parameter assignment error in the ConnectionType parameter of the data block for connection description.

  • Only valid with TCON_IP_v4: 0x11, Ox0B and 0x13

  • Only valid with TCON_IP_RFC: 0x0C and 0x12

W#16#80B7

With TCON_IP_v4:

  • TCP (active connection establishment): Remote port is "0".

  • CP (passive connection establishment): Local port is "0".

  • UDP: Local port is "0".

  • IP address of the partner endpoint is set to 0.0.0.0.

With TCON_IP_RFC:

  • For local (LocalTSelector} or remote (RemoteTSelector} T selector, a length greater than 32 bytes is specified.

  • For TSelLength of the T selector (local or remote), a length greater than 32 is specified.

  • Error in the length of the IP address of the specific connection partner.

  • IP address of the partner endpoint is set to 0.0.0.0.

W#16#80B8

Parameter ID in the local connection description (structure at CONNECT parameter) and parameter ID of the instruction are different.

W#16#80C3

All connection resources are assigned, or ports are dynamically used by other applications or connections.

W#16#80C4

Temporary communication error:

  • The connection cannot be established at this time.

  • The connection cannot be established because the firewalls on the connection path are not open for the required ports.

  • The interface is receiving new parameters.

  • The configured connection is being removed by a TDISCON instruction.

W#16#80C5

The connection partner refuses to establish the connection, has terminated the connection or actively ended it.

W#16#80C6

Network error: The connection partner cannot be reached.

W#16#80C7

Execution timeout.

W#16#80C8

Value at the ID parameter is already used by a connection that was created by the user program. The connection uses the identical ID, but different connection settings at the CONNECT parameter.

W#16#80C9

Validation of the connection partner failed. The connection partner that wants to establish the connection does not match the defined partner at the CONNECT parameter.

W#16#80CE

The IP address of the local interface is 0.0.0.0.

W#16#80D0

With TCP and active connection endpoint: The remote_qdn parameter is an empty string. A connection cannot be established.

W#16#80D1

The remote_qdn parameter is not a fully qualified domain name. The period at the end might be missing.

W#16#80D2

No DNS server address is configured.

W#16#80D3

The fully qualified domain name cannot be resolved. Possible causes:

  • The DNS server is not reachable, for example, because it has been shut down or the remote port is not reachable.

  • An error occurred during communication with the DNS server.

  • The DNS server returned a valid DNS answer, but the answer contained no IPv4 address.

W#16#80E0

Unsuitable or poor message was received.

W#16#80E1

Error during handshake. Possible causes:

  • Aborted by the user

  • Security not high enough

  • Renewed negotiation is not supported.

  • SSL/TLS version is not supported.

  • Validation of the host name failed.

W#16#80E2

Certificate is not supported or invalid. Possible cause: The time-of-day of the module concerned is not set or the module is not synchronized.

Example: The default setting for the date of the module is 1/1/2012 and it was not set during commissioning. The validity period of the certificate starts on 20 August 2016 and ends on 20 August 2024. In this case, the date of the module is outside the valid period of the certificate; the certificate is invalid for the module.

W#16#80E3

Certificate was discarded.

W#16#80E4

No valid certification authority found.

W#16#80E5

Certificate expired.

W#16#80E6

Integrity errors in the Transport Layer Security Protocol.

W#16#80E7

Not supported extension in X.509-V3 certificate.

W#16#80E9

TLS server without server certificate is not supported.

W#16#80EA

DTLS (UDP) protocol is not supported.

W#16#80EB

A client cannot request a client certificate.

W#16#80EC

The server cannot perform validation based on subjectAlternateName (only clients can do this).

W#16#80ED

TLSServerCertRef_m-ID is invalid.

errorTusend

Hexadecimal value Status info

Description

W#16#0000

Send job completed without error.

W#16#7000

No job processing is active.

W#16#7001

Start of job processing, data being sent.

Note: During this processing phase, the operating system accesses the data in the DATA send area.

W#16#7002

Intermediate call (REQ irrelevant), job is being processed.

Note: During this processing phase, the operating system accesses the data in the DATA send area.

Hexadecimal value Error

Description

W#16#8085

The LEN parameter has the value "0" or is greater than the highest valid value.

W#16#8086

The ID parameter is outside the valid range.

W#16#8088

The LEN parameter is greater than the memory area specified in DATA.

W#16#8089

The ADDR parameter does not point to a data block with the structure TADDR_Param or TADDR_SEND_QDN.

W#16#80A1

Communication error:

  • The specified connection between user program and communication layer of the operating system has not yet been established.

  • The specified connection between the user program and the communication layer of the operating system is currently being terminated. Transfer over this connection is not possible.

  • The interface is being re-initialized.

W#16#80B1

You changed the DATA parameter before the current job finished.

W#16#80A4

IP address (at the ADDR parameter) of the remote connection endpoint is invalid, or it matches the IP address of the local partner.

W#16#80B3

  • The protocol variant (connection_type parameter in the connection description) is not set to UDP. Please use TSEND.

  • Parameter ADDR: Invalid settings for port number.

W#16#80B7

The length of the structure referenced by the ADDR parameter is not 8 bytes.

W#16#80C3

  • A block with this ID is already being processed in a different priority class.

  • Internal lack of resources.