PmTelepermXU - Driver for communication with Siemens TELEPERM system

The TELEPERM control system from the Siemens company is used mainly in power and heating stations. This driver has been developed for nuclear power station (Topas system, Mochovce Slovakia) and it communicates with external unit (XU=external unit) of the OM690 type of this system.
Before using this driver in the PROMOTIC application it is highly recommended to read the chapter: Communication using the PROMOTIC drivers.
Basic properties of the driver:
- The communication is done via Ethernet.
- The PROMOTIC application is the MASTER (i.e. it initiates the data transfer) from this communication point of view.
- The driver is incorporated into the PROMOTIC system by means of the PmComm object.

The driver supports to usage of PmCommMsg object. The PmCommData object cannot be used.

- The driver can write, but data reading messages has not been implemented

Recommended parameters values:

Recommended values for the Ethernet parameters:
TCP/UDP port number18000
Ethernet transfer typeTCP
Description and recommended values for the Protocol parameters:
Identification number of the clientNumber used by the server in order to identify the PROMOTIC application

The communication description by the PmCommMsg objects

- StateRequest TXP_GET_STATE:

Getting information about server state and server registration.

After a connection with the XU has been established, the client (PROMOTIC application) must request information about the server state of the XU. If the client is not allowed to send other message, then TXP_GET_STATE to the nonleading host.

There are following variables on the Data-received page:
State: Server state. The data type is Long. The meaning:
1=starting up
2=standby - i.e. may become the leading XU at any moment
3=leading - only in this state it is possible to transfer data!
4=soon shutdown
- Write Data TXP_WRITE_POS:

Write data to XU server.

A client only can write its "own" signals. These are all signals, where the client is registered as legitimated to write. A signal can be registered to be writable only for maximum 1 client.

If the client disconnects, or if the client did not send a write order for longer than 1 minute, then the XU supposes the client to be dead. As a consequence of this, the XU sets all affected signals to the invalid state. In order to keep up with this timeout, empty write orders suffice (i.e. to send TXP_WRITE_POS message with number of signals = 0).

There are following variables on the Data-sent page:

The object always contains the "Nmb" item. Other items are added according to message parameters.

Nmb: The current number of sent items. The data type is Long. The value can vary from 0 up to the maximum value set in the message parameters.
vX_ProcId: Variable identifier. The data type is String. Maximum lenght is 24 chars. When this text is sent to the server one space is added at the beginning (i.e. each identifier on the server must begin with a space) and more spaces are added to the end, in order to achieve the total length of 25 chars.
vX_Value: The variable value sent. Single data type (for analog signals) or Long (for binary signals). For binary signals the value sent to the server is always 0 or 1.
vX_Time: Time of the sent value. The data type is Date. This variable is included only if allowed by the message parameters. If not allowed, then the empty variables sent and the current time is added by the server.
vX_Quality: State (quality) of sent value. The data type is Long. This variable is included only if allowed by the message parameters. If not allowed, then 0 is sent. The meaning of the state bits:
0.bit: Not initialized
1.bit: Invalid
2.bit: Replacement Value
3.bit: Simulated
4.bit: Doubtful
5.bit: HW failure
6.bit: In service
7.bit: Time adjusted
There are following variables on the Data-received page:
Code: Successful sending flag. The value less than 0 means indicating a bad transfer.
Module: Internal Teleperm value (confirmed module identification)
Line: Internal Teleperm value (row number in the system)
- Explicit disconnect TXP_DISCONNECT: To say that the client is going to disconnect.
PROMOTIC 8.3.29 SCADA system documentation - MICROSYS, spol. s r.o.

Send page remarkContact responsible person
© MICROSYS, spol. s r. o.Tavičská 845/21 703 00 Ostrava-Vítkovice