Siemens Teleperm - M/ME

OSI Software, Inc.

Siemens Teleperm - M/ME
Interface to the PI System

via CS 275 Server and SYTRANS 300 CS Gateway

version 7.12 or greater

How to Contact Us

Phone / (510) 297-5800 (main number)
(510) 297-5828 (technical support)
Fax / (510) 357-8136
Internet /
World Wide Web /
Bulletin Board / (510) 895-9423
Telebit WorldBlazer modem (Hayes, MNP, or PEP compatible)
8 data bits, 1 stop bit, no parity, up to 14400 bps download
protocols: Xmodem, Ymodem, Zmodem, Kermit
Mail / OSI Software, Inc.
P.O. Box 727
San Leandro, CA 94577-0427
USA
OSI Software GmbH
Hauptstrae 30
D-63674 Altenstadt 1
Deutschland /
OSI Software, Ltd
P. O. Box 8256
Level One, 6-8 Nugent Street
Auckland 3, New Zealand

Unpublished -- rights reserved under the copyright laws of the United States.
RESTRICTED RIGHTS LEGEND
Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii)
of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013

Trademark statement—PI is a registered trademark of OSI Software, Inc. Microsoft Windows, Microsoft Windows for Workgroups, and Microsoft NT are registered trademarks of Microsoft Corporation. Solaris is a registered trademark of Sun Microsystems. HPUX is a registered trademark of Hewlett Packard Corp.. IBM AIX RS/6000 is a registered trademark of the IBM Corporation. DUX, DEC VAX and DEC Alpha are registered trademarks of the Digital Equipment Corporation.
ssimaticnet125.doc PI-IN-SI-SIMAT-NT

 1997 OSI Software, Inc. All rights reserved
777 Davis Street, Suite 250, San Leandro, CA 94577

November 19981

OSI Software, Inc.

Table of Contents

Introduction

Supported Teleperm Data Types

PI Point Configuration

More About Point Configuration

Module Codes for Teleperm M/ME

Interface Files

OpenVMS Version

Windows NT Version

Installing SIEMENS/Teleperm-M/ME

Pre-Installation Tasks (PI2)

OpenVMS via Special Interface Tape

Windows NT via Installation Disk

PIPE names for the communication on Windows NT

Running the SIEMENS/TELEPERM-M/ME interface as a service

Linking Program, OpenVMS Version Only

Startup

OpenVMS version

Windows NT version

Command line switches for TCS interface:

Shutdown

OpenVMS Version

Windows NT Version

Multiple Links on one PI Node

OpenVMS Version

Windows NT Version

IO Rate Tags

TCSCP Control Program, OpenVMS only

Error and Information Messages, OpenVMS only

How TELEPERM-M/ME Interface Operates

Failover

Time synchronization

Hints for the System Manager

Helpfile for TCSCP Control Program, OpenVMS only

Introduction

The SIEMENS/TELEPERM-M/ME Interface does the following:

Provides bi-directional transfer of data between a TELEPERM-M/ME process control system and the Plant Information (PI) System.
Communicates to the TELEPERM-M/ME System via CS 275 Server (OPEN_CS) connected to a SYTRANS 300 CS Gateway.

This Version requires OPEN_CS Version 6.1 or later for OpenVMS and Version 7.0 or later for Windows NT.

The SYTRANS 300 CS Gateway is directly connected to the SIEMENS/TELEPERM-M/ME CS 275 Bus and communicates to the Host via TCP/IP protocol. The result is a fast Interface with much higher data throughput than using SIEMENS NV.24 modules. The interface can run on a DEC VAX or ALPHA containing either the PI Home Node or a PINet Node and with version 6.11 the interface can run on a Windows NT node.

Data can be received in scan rates or by request using Parameter Read (PR) function and sent by exception using Parameter Write (PW). For high performance the AKS, BKS and MKS functions are used to receive data in cycles.
Depending on the Teleperm System type used different types of Status Telegrams (SB-Telegrams) are supported. Those telegrams are event driven.

SIEMENS Telegrams other than PR, PW, AKS, BKS, MKS, SB are not supported in this version!
A separate program is provided to control the Interface.

The protocol is described in detail in:

Synotec Systems GmbH
SY-TRANS 300 CS Protocol Converter, and
SY-TRANS 300 CS VMS Interface.

Supported Features
Sign up for Updates / Yes
Exception Reporting / Yes
PI Net Support / Yes
Outputs / Yes
Vendor Software Required / Yes
Failover / Yes
Number of AKS, BKS, MKS, SB Points
Number of PR, PW Points / Unlimited
unlimited

Supported Teleperm Data Types

The Interface does not support all possible Siemens Teleperm Data Types. To be able to check if the data types needed are already supported in this current version the following table gives an overview.

Telegram Type / Data Type /
Comment
AKS / AKS / Up to 28 Analog Values per Telegram
Teleperm M:cyclical transfer
Teleperm ME:cyclical or event controlled transfer
BKS / BKS / Binary field of 128 bit per Telegram
+ 128 status bits
MKS / MKS / 32 binary values per Telegram
Event controlled transfer
SB / BST / Tested only for Teleperm ME!!!
PR /
I
ID
EA, EAV, AA, PA
EAD, EDV, AAD, PAD
EB, EBV, AB, PB
S2, S4, S16 / Read Telegrams after successful request of Y Address (Scheduled in scan classes)
Integer
Double Integer
Float
Double Float
Binary (2 bit)
String
PW /
I
ID
EA, EAV, AA, PA
EAD, EDV, AAD, PAD
EB, EBV, AB, PB
S2, S4, S16 / Write Telegrams after successful request of Y Address (Scheduled in scan classes)
Integer
Double Integer
Float
Double Float
Binary (2 bit)
String

Note System-, Operator- and Text- Telegrams are not supported.
Status Telegrams for Teleperm M and AS220 are not tested yet.
Also Data Types PB, VB and VA cannot be accessed via Parameter Read in this version!

PI Point Configuration

The following database details are necessary for configuring a PI point for use with the TELEPERM-M/ME Interface.

Point Name

The point name is free, according to the normal PI point naming conventions.

Extended Descriptor

The Extended Descriptor is used to identify the value in the TELEPERMM System.
Insert here Bus, Member, Module type, Module number, Parameter type and Parameter number For binary sources, also insert a Bit position value.

The scan rate for the tag is also specified here (default is 60 seconds).

BUS / = / CS275 bus address
TLN / = / Member number
MTP / = / Module type
MNO / = / Module number
PTP / = / Parameter type
PNO / = / Parameter number
BIT / = / Position in bit field (optional)
SCN / = / Scan rate for PW, PR tags
or
maximum timeout period for
AKS, BKS
(optional, default=60)
or
delay for SB Admin Tags
(optional, default=60)

Examples:

BUS=1 TLN=6 MTP=AKS MNO=1 PTP=EA PNO=2

BUS=0 TLN=2 MTP=BKS MNO=22 PTP=EB PNO=18 BIT=18

BUS=0 TLN=2 MTP=SB SCN=20

BUS=1 TLN=1 MTP=MKS MNO=2 PTP=ID PNO=19 BIT=18 SCN=30

For additional hints, see "More About Point Configuration" on page 10.

Point Source

The point source is a single character, for example S (SIEMENS). The point source must be defined in the point source library before point configuration.

Point Type

The Interface supports all PI2 point types (R, I and D). Connected to a PI3 server the interface supports in addition String tags[1].

Engineering Units

Engineering Units must be defined in accordance with the meaning of the measured values.

Scan flag

This is usually ON for all points of this interface. If you edit this Point Attribute as OFF, then the tag is OFFLINE (no values are exchanged for this tag). In this case and if the tag is defined for Input, it automatically gets Scan off value from the Interface.

Source tag

For outputs, the tag you are creating is only a pointer tag. The name of the tag, containing the values to be sent to TELEPERM-M/ME must be entered here. If this field remains empty, the pointer tag itself contains the values to be sent.

Location 1

This is the interface number. If multiple CS275 Gateways are used, group the PI tags together for higher performance. Each single interface number is assigned to a certain session.

There is a limit of 2000 PR and PW tags per session given by the OPEN_CS software when this version was developed.

Location 2

This parameter specifies whether the tag is an input or an output.

0 / Input via Parameter Read (PR) Function
1 / Output via Parameter Write (PW) Function
2 / Input via AKS, BKS, MKS and/or PR
3 / Input via AKS, BKS, MKS
Y-Address is not requested
4 / reserved
5 / Input via SB
Y-Address is not requested
1000 / Batch ID (Events will be produced with event type of 1)
2000 / Product ID (Events will be produced with event type of 2)

To create a BatchID or ProductID with the event log entry, use a line similar to this in the batch configuration file:

BATCHID = EVENTLOG, TE:XTTAG., 83, 1, 'Error in BatchID'

where TE:XTTAG. is the tag connected to the Siemens S16 String.

Once the event is written to the event log, the batch must start within 20 seconds to get the text entry from the event log.

Location 3

Here you specify the AS type:

0 / AS 230, AS 235 modules
1 / AS 220, AS 220H modules
2 / AS 220, AS 220H plus MKS status
(customer specific)
3 / AS 220E, AS 220EA
4 / AS 220EHF
5 / EAK
6 / AS 231, MS 236
7 / AG 150 U
8 / AG 155 U
9 / AS 215

Location 4

While creating the tag, set this value to 0. If Location 2 = 3, then the YAddress is not necessary and therefore not ascertained; Location 4 remains 0.

Location 5

While creating the tag, set this value to 0. If Location 2 = 3, then the YAddress is not necessary and therefore not ascertained; Location 5 remains 0.

The Interface does not use the following tag attributes:

Square root code
Totalization code
Conversion factor

More About Point Configuration

You can define a tag for a certain Interface task by specifying the Location 1 parameter.
The Interface is connected to a CS275 Gateway session via the Interface number.
Example:
The VMS process CS275PI-1

Has the Interface ID number 1 and
Is connected via OPEN_CS to session CS275_SERVER_01.

Now it is possible to

Run the Interface with Interface ID=2 on another PI Node or even the same PI Node and
Connect to a second Gateway (also via OPEN_CS and session CS275_SERVER_02 on that node).

Note: Starting with Version 6.1 of this interface, you can run multiple interface processes connected to the same number of different gateways by specifying Interface ID and Location1 accordingly.

Note One interface process uses one gateway exclusively!

PI Point Type and Data Type

The following table shows how PI tags can be defined according to the telegram data types.
Example: A Siemens point type EA can only be mapped into a PI point type R (real). According to the table, no other conversion is supported.

PTP / PI Point Type / Telegram / Output / Comment
I / D, I, R / PR, PW / Yes
ID / D, I, R / PR, PW, MKS / Yes
EA, EAV,
AA,
PA / R / AKS, PR, PW / Yes / For Output also Point Type D,I
EAD,
EDV,
AAD,
PAD / R / PR, PW / Yes / For Output also Point Type D,I
EB,
EBV,
AB,
PB / D, I / BKS, PR, PW,
SB / Yes
no
S2
S4
S16 / I / PR / No / Tag switches between 0 and 1
the string itself gets archived in the event logger using the same timestamp

BKS tags

Note that in a BKS tag, PNO and BIT are equal for BKS tags. The difference to MKS is caused by different internal Y-Address structures. It is possible to retrieve a value, normally sent via BKS or MKS cyclic telegrams, via Parameter Read functions.
Example:

BUS=1 TLN=1 MTP=BKS MNO=303 PTP=ID PNO=3 BIT=3 SCN=120

This is different for MKS tags.

MKS tags

A tag configured for MKS module must have PNO=BIT+1. In this case PNO is responsible to request the value via Parameter Read (PR) and BIT gives the position of the same value when it is delivered via MKS cyclic telegram.
Example:

BUS=1 TLN=1 MTP=MKS MNO=303 PTP=ID PNO=4 BIT=3 SCN=120

SB tags

The interface can only enable status messages on a per bus-member basis. This means on one hand that even for a single required status message all status messages of a certain module (AS) are transferred to the interface. On the other hand this means bus load!
In order to enable status messages for a bus-member, there must be one administrator tag configured which triggers notification and denotification and will contain information about transfer status.
The administrator tag should be of type ‘I’ or ‘D’
Values for the administrator tags are:
0 = Denotified successfully
1 = Notified successfully
Bad Value = Problem on Notification or Denotification

The required status tags must be defined separately.
After first notification (Interface startup) all status tags will receive the current value to be updated.

Example:

Teleperm-ME:
Administrator tag:
BUS=1 TLN=1 MTP=SB SCN=30
Status tags:
BUS=1 TLN=1 MTP=66 MNO=1 PTP=0 PNO=1 BIT=5
or (same configuration)
BUS=1 TLN=1 MTP=66 MNO=1 PTP=F PNO=1 BIT=5

For a Teleperm-ME System the keywords are coded as follows:

MTP: module type (Baustein) ranges from 1 – 140

MNO: module number

PTP:signal type 0 = Function Error (F)
1 = User Signal (B)
2 = Status Signal (Z)
3 = Project Error (P)
PNO: represent the group (row) number
BIT: specify the signal number (from 5 to 16) in OS notification.

The above example addresses RS module number 1, BST=F1, Signal XDGM. Note that for the keyword BIT we use OS bit counting, even if the SB telegrams have reversed order.

Teleperm-M:
Administrator tag:
BUS=1 TLN=1 MTP=SB SCN=30
Status tags:
BUS=1 TLN=1 MTP=M MNO=1 PTP=SB PNO=3

For a Teleperm-M System MTP represent the module type, MNO represents the module number and PNO specifies the signal number (from 1 to 12).

AS 220:
Administrator tag:
BUS=1 TLN=1 MTP=SB SCN=30
Status tags:
BUS=1 TLN=1 MTP=R MNO=1 PTP=SB PNO=3

For Teleperm AS220 devices (Teleperm-M) the PNO specifies the signal number (from 1 to 12).

Manual read (OpenVMS only)

It is possible to get values for tags - actually configured for AKS, BKS, MKS - using features of the TCSCP Control Program.
It is necessary to have the Y-Address available before scheduling a manual request. Either the Y-Address is automatically requested in configuring the tag with Location 2 parameter = 2 or the Y-Address has to be requested manually using the command "GET YADDRESS tagname" which has to be entered from the TCSCP> prompt.

Note that there is a limit in the number of tags configured for requesting the Y-Address (current limit: 2000). The standard for AKS, BKS and MKS tags should therefore be: Location 2 = 3.

Scan rates

One of the parameters to pass in the Extended Descriptor is SCN.
SCN has two different meanings.

PR,PW: SCN gives the scan rate in seconds.
The default is 60 sec.
AKS,BKS: SCN gives the maximum timeout period. If for SCN seconds no AKS or BKS telegram (related to the tag) arrives, the tag will get an I/O Timeout value.
SB Administrator tags: SCN gives the delay after successful notification before the next SB member will be notified.
SCN is not used for MKS and SB data tags.

The Interface automatically groups tags into lists in order to create PR and PW telegrams.
Only tags with the same BUS, TLN and SCN values can be part of the same PR/PW. A PR telegram has a maximum of 30 tags assigned and a PW telegram can have a maximum of 20 tags.

Module Codes for Teleperm M/ME

Module (Baustein) / Code / Module (Baustein) / Code
AAUS / 10 / MW / 51
ABS / 19 / MX / 92
AE / 109 / NAS / 42
AEIN / 8 / PBE / 89
AET / 116 / PLG / 28
AETE / 117 / PRA / 127
AKE / 9 / PT / 17
AKS / 72 / RAD / 22
AR / 133 / RANG / 90
ARA / 135 / RB / 114
ARE / 134 / REN / 68
ASE / 56 / RG / 34
ASL / 31 / RK / 67
ASR / 130 / RKB / 82
AU / 47 / RS / 66
AUSW / 23 / RSB / 83
BAUS / 13 / RT / 91
BCA / 54 / RTB / 88
BCE / 55 / SAKE / 94
BEI / 128 / SAKS / 93
BEIN / 11 / SB / 49
BKE / 45 / SBKE / 96
BKS / 73 / SBKS / 95
BR / 69 / SBV / 50
BRB / 81 / SM / 61
BS / 6 / SMB / 85
BSA / 126 / SMKE / 98
BSB / 84 / SMKS / 97
BSE / 60 / SR / 121
BSR / 131 / SRB / 122
BSRA / 137 / SRZ / 120
BSRE / 136 / SS / 62
BUS / 115 / SSB / 86
BW / 59 / STRT / 1
DIAG / 132 / SUM / 14
DIF / 16 / SWF / 33
DIV / 21 / SZ / 63
DYN / 119 / SZB / 87
EAV / 104 / T / 39
EM / 105 / TAS / 57
EMB / 106 / TE / 110
ES / 107 / TEB / 111
ESB / 108 / TOB / 32
EXP / 24 / TOZ / 30
FGS / 129 / TS / 48
FSM / 70 / TSAE / 103
GP / 65 / TSB / 76
GS / 46 / TSBA / 102
GSB / 79 / TSBE / 99
GW / 29 / UG / 138
GWM / 4 / UGB / 139
I / 52 / UMA / 74
INKU / 53 / UME / 75
INT / 15 / VL / 112
KO / 3 / VLB / 113
KOB / 80 / VM / 40
KR / 124 / VN / 37
KRB / 125 / VO / 36
KRZ / 123 / VS / 5
LN / 25 / VU / 35
MAX / 26 / VW / 64
MEL / 12 / VWB / 77
MELD / 118 / VZ / 38
MIN / 27 / XAUF / 44
MIT / 7 / XB / 2
MKE / 41 / ZAS / 43
MKS / 71 / ZE / 58
MU / 18 / ZIE / 141
MUB / 78 / xxx / 140
MUL / 20

Interface Files

OpenVMS Version

The startup files for the interface are in the PISysExe: directory.
Listed below are the files required for starting the interface.

TCSCP.hlb / --> PIRESOURCES:
TCSPIDetach.com / --> PISysExe:
TCSPIStart-1.com / --> PISysExe:
TCSPIStop-1.com / --> PISysExe:
TCSPI.exe / --> PISysExe:
TCSCP.exe / --> PISysExe:

The files to link the Interface are in the PIBuild: directory. You can select all of them with wildcard *TCS* .
Example: dir PIBuild:*TCS*).

$ ! TCSPIDetach.com BB 27-Sep-1996

$ ! Run TCSPI-n as a detached process. Parameters are:

$ !

$ ! P1 Interface number

$ !

$ ! @pisysexe:tcspidetach 1

$ !

$ !======

$ !

$ pu/nolog pisysexe:tcspistart-'P1'.com

$ If (F$Search("PISysExe:tcspi-''P1'.out").nes."") then -

Purge/Nolog/Keep=30 PISysExe:tcspi-'P1'.out

$ Run/Detach/UIC=[SYSTEM]/Process="CS275PI-''P1'"/extent=5000 -

/Input=PISysExe:tcspistart-'P1'.com /Output=PISysExe:tcspi-'P1'.out -

/working=2000/page_file=100000/maximum_working=6000/extent=10000-

/buffer=64000/file_limit=128/job_table=4096-

Sys$System:LogInOut

$ exit

$ ! TCSPIStart-1.com BB 27-Sep-1996

$ ! AS 09-Jan-1997

$ !

$ ! /ps=S Point source character

$ ! /in=1 interface number

$ ! /ec=13 I/O rate counter number

$ ! /write=2 output gate flag 0 - enable

$ ! 1 - disable

$ ! 2 - disable everything else than

$ ! writing into AKS area

$ ! /ct=10 minimum timeout in seconds

$ ! /os=238 "Scan Off" number in Digital State Table

$ ! /deb=0 optional debug level (defaultet to 0)

$ ! /tstamp=1 optional vms timestamping (defaultet to 0)

$ ! /reset=1 optional reset of SY-TRANS on startup (0=no, 1=reset)

$ ! /pievgrp=1 optional Event Group for Event Log

$ !

$ ! failover (all optional):

$ ! /gft="sy:fail" failover control tag

$ ! /gf1=1 run if failover tag is /gf1

$ ! /gf2=2 set failover tag to /gf2 when line goes down

$ ! /connect=OFF wait after (ON) or before (OFF) to connect to SY-TRANS

$ ! /gfd=239 failover digital state number

$ ! /gfc=30 seconds between line break checks

$ ! /mi=OFF this is master interface (ON) or not (Off)

$ ! /gftcheck=20 if failover tag doesn't change within /gftcheck

$ ! seconds, take over data collection

$ !

$ ! Windows NT:

$ ! /host=localhost:5450 hostname of PI server

$ ! /output=C:\PIPC.LOG optional output file name

$ ! /pass=password optional password. Use only upper case,