Siemens Teleperm - M/ME



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 |techsupport@ |

|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 |OSI Software, Ltd |

| |Hauptstra(e 30 |P. O. Box 8256 |

| |D-63674 Altenstadt 1 |Level One, 6-8 Nugent Street |

| |Deutschland |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. HP-UX 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

Table of Contents

Introduction 5

Supported Teleperm Data Types 6

PI Point Configuration 7

More About Point Configuration 10

Module Codes for Teleperm M/ME 13

Interface Files 16

OpenVMS Version 16

Windows NT Version 18

Installing SIEMENS/Teleperm-M/ME 19

Pre-Installation Tasks (PI2) 19

OpenVMS via Special Interface Tape 19

Windows NT via Installation Disk 20

PIPE names for the communication on Windows NT 20

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

Linking Program, OpenVMS Version Only 22

Startup 23

OpenVMS version 23

Windows NT version 23

Command line switches for TCS interface: 23

Shutdown 26

OpenVMS Version 26

Windows NT Version 26

Multiple Links on one PI Node 27

OpenVMS Version 27

Windows NT Version 27

IO Rate Tags 28

TCSCP Control Program, OpenVMS only 30

Error and Information Messages, OpenVMS only 31

How TELEPERM-M/ME Interface Operates 32

Failover 34

Time synchronization 35

Hints for the System Manager 36

Helpfile for TCSCP Control Program, OpenVMS only 37

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 |Unlimited |

|Number of PR, PW Points |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 | |Read Telegrams after successful request of Y Address (Scheduled in scan classes) |

| | |Integer |

| |I |Double Integer |

| |ID |Float |

| |EA, EAV, AA,|Double Float |

| |PA | |

| |EAD, EDV, |Binary (2 bit) |

| |AAD, PAD |String |

| |EB, EBV, AB,| |

| |PB | |

| |S2, S4, S16 | |

|PW | |Write Telegrams after successful request of Y Address (Scheduled in scan classes) |

| | |Integer |

| |I |Double Integer |

| |ID |Float |

| |EA, EAV, AA,|Double Float |

| |PA | |

| |EAD, EDV, |Binary (2 bit) |

| |AAD, PAD |String |

| |EB, EBV, AB,| |

| |PB | |

| |S2, S4, S16 | |

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 TELEPERM-M 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 Y-Address 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 Y-Address 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, |R |AKS, PR, PW |Yes |For Output also Point Type D,I |

|AA, | | | | |

|PA | | | | |

|EAD, |R |PR, PW |Yes |For Output also Point Type D,I |

|EDV, | | | | |

|AAD, | | | | |

|PAD | | | | |

|EB, |D, I |BKS, PR, PW, |Yes | |

|EBV, | | | | |

|AB, | |SB |no | |

|PB | | | | |

|S2 |I |PR |No |Tag switches between 0 and 1 |

|S4 | | | |the string itself gets archived in |

|S16 | | | |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: |

| |--> PISysExe: |

|TCSPIStart- |--> PISysExe: |

|TCSPIStop- |--> 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*).

$ ! 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- 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,

$ ! because all command line arguments are

$ ! converted to upper case.

$ !

$ !====================================================================

$ !

$ ! automatic restart of Interface under special circumstances

$ start:

$ on error then goto start

$ tcs := $pisysexe:tcspi.exe

$ !

$ ! single interface:

$ !

$ tcs /ps=S /in=1 /ec=13 -

/write=2 /ct=10 /os=-238 /deb=3 /tstamp=1 /reset=1

$ !

$ ! failover interfaces:

$ !

$ ! tcs /ps=S -

/in=1 -

/ec=13 -

/write=2 -

/ct=10 -

/os=-238 -

/deb=3 -

/tstamp=1 -

/reset=1 -

/gft="sy:fail" -

/gf1=1 -

/gf2=2 -

/mi=on

$ !

$! TCSPIStop- BB 27-Sep-1996

$!===================================================================

$!

$ run pisysexe:tcscp

shutdown /id=1

$ exit

Windows NT Version

The startup files for the interface are in the PI/interfaces/TCS directory. Listed below are the files required for starting up the interface.

• TCSPI.BAT

• TCSPI.exe

Installing SIEMENS/Teleperm-M/ME

Pre-Installation Tasks (PI2)

To install the interface, use the following procedure:

1. Define a point source code.

2. Select one I/O rate counter (in iorates.dat).

3. Modify the PI startup and shutdown command files. Optionally, you can specify one performance monitoring tag as shown in section "I/O Rate Counter".

In the PI System Point Source Editor set up the following values:

Point Source Code: S Point Source Descriptor: SIEMENS/TELEPERM-M/ME

Location Minimum 1 0 0 0 0

Location Maximum 1 2000 9 65535 65535

OpenVMS via Special Interface Tape

For an update of the SIEMENS/Teleperm-M/ME Interface, backup all TCS files at PIBuild: directory.

For example:

$ create/dir pi$disk:[tcs_old]

$ copy pibuild:*tcs*.* pi$disk:[tcs_old]

$ copy pibuild:*open_cs*.* pi$disk:[tcs_old]

If it is the first installation of the Interface, the backup is not necessary.

If the PI System is not installed, create a directory [PIBuild].

For example:

$ create/dir [PIBUILD]

Now define a logical name PIBuild, which points to the directory.

Example:

$ Define/System PIBuild DKA100:[PIBUILD]

If PI is installed, the PIBuild: logical name already exists.

Now run the VMSInstal procedure:

Example:

$ @sys$update:vmsinstal TCS070 mkb500

In order to link automatically, the PI system must be running!

If installation failed, the files are in any case now at PIBuild: directory and it is possible to link manually according to the Interface manual.

Example:

$ set def pibuild:

$ @tcspilink

Windows NT via Installation Disk

For an update of the SIEMENS/Teleperm-M/ME Interface make a backup of all TCS files at PIPC/interfaces/tcspi directory.

Example:

c:> md /PIPC/interfaces/tcspi/tcs_old

c:> copy /PIPC/interfaces/tcspi/*.* /PIPC/interfaces/tcspi/tcs_old/*.*

If it is the first installation of the Interface, the backup is not necessary.

Now insert the TCS interface diskette in the floppy disk drive and run the file TCS70.EXE.

Example:

c:> a:tcspi707.exe

PIPE names for the communication on Windows NT

For communication with the OPEN_CS server the interfaces uses named pipes. Attaching the interface ID to a fixed string creates the pipe names the interface expects. See the table below for an example of the pipe names the interface with ID=1 (default) will expect.

|Pipename |Description |

|CS_IN01 |Input - Messagequeue - Name |

|CS_OUT01 |Output - Messagequeue - Name |

|CS_ASYNC01 |Async - Messagequeue - Name |

The names of this named pipes can not be changed within the interface, therefor it may be necessary to change the default configuration of the OPEN_CS server to reflect the pipe names required by the interface.

In this case (ID=1) the startup file for the OPEN_CS server would look similar to:

@echo off

csserver 1 1 HP1 CS_IN01 CS_OUT01 CS_ASYNC01

Rem 1. Parameter: Verbindungsnummer

Rem 2. Parameter: Select-Timeout (Millisekunden)

Rem 3. Parameter: SYNO(R)gate 300 IP Hostname

Rem 4. Parameter: Input - Messagequeue - Name

Rem 5. Parameter: Output - Messagequeue - Name

Rem 6. Parameter: Async - Messagequeue - Name

pause

csserver 1 status

pause

If you plan to run an interface with an ID different from 1 you will have to change the named pipes to reflect the different pipe name (e.g. for ID=2: csserver 2 1 HP1 CS_IN02 CS_OUT02 CS_ASYNC02) accordingly.

Please refer to the installation instructions of the Synotec CS-Server for further information on installing multiple copies of the OPEN_CS server.

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

The SIEMENS/TELEPERM-M/ME interface can be installed as a Windows NT service thus the interface can start on system startup without the need for someone to be logged in.

To run the SIEMENS/TELEPERM-M/ME as a Windows NT service the batch file starting the interface interactively and the name of the interface executable must be identical except the extension (e.g. TCSPI.EXE and TCSPI.BAT) and they must reside in the same directory. To install the interface as a Windows NT service open a MS-DOS prompt and change the current directory to the directory holding the interface files. Execute the command

TCSPI –install –name=“PI SIEMENS TELEPERM INTERFACE”

This will install the SIEMENS/TELEPERM-M/ME interface as a service with the name PI SIEMENS TELEPERM INTERFACE. Now you can start the interface by executing

TCSPI –start

And stopping with

TCSPI –stop

To remove the service from the Windows NT service list you can execute

TCSPI –remove

Additional parameter for the service configuration are –auto to start the service automatically on system startup and –depend=“TCPIP” to avoid startup of the service before a different service is running.

The interface will retrieve the necessary command line switches from the batch file (see above for naming conventions).

Linking Program, OpenVMS Version Only

The interface program will be relinked whenever executing PIBuild: relinks the PI System.

To relink just the TELEPERM-M/ME Interface, execute PIBuild:.

The link procedure checks for the existence of the required vendor software.

The link will fail:

• If open_cs.olb is not available.

• If the library is not installed in the default directory sys$common:(sy_300cs(.

In this case the file must be edited accordingly.

All Files will be moved to the right directories. If there are already Interface command files at PISysExe: directory, they are not overwritten to keep site-specific information (scan rates, point source,...).

Startup

OpenVMS version

To start the interface, run a command file called . You must give this file the Interface ID number.

To start the interface manually, log in as SYSTEM and enter this command:

@PISysExe:TCSPIDetach 1

In this case the file TCSPIStart- is called and runs in detached mode.

The TCSPIStart- file contains several site-specific switches that you may want to modify.

Windows NT version

To start the interface, run the TCSPISTART.BAT batch file.

Command line switches for TCS interface:

|Command line switch |Description |

|/ps=S |point source (S) |For Point Source see also Chapter “Installation” |

|/in=1 |Interface number |The interface number corresponds to Location 1 of a tag. |

| | |All tags with Location 1 = (interface number) will be serviced by that |

| | |Interface. |

|/ec=23 |input rate counter number (1-34) |For Input Rate Counter see also Chapter “IO rate counter” |

| | |You need one free number in iorates.dat. |

|/write=0 |Disable write data (output) into |Parameter can cause the Interface to be of type Read Only. If write = 1, there|

| |TELEPERM-M/ME |is no way to write data into SIEMENS/Teleperm-M as long as the Interface is |

| |Enable |not stopped and started with write != 1. |

| |Disable |Another security level for writing data is given with write = 2. All other PW |

| |Disable everything else than writing |tags, not configured to write into AKS areas will be rejected on Interface |

| |into AKS area |startup. This can be of use, if additional tests should be performed at |

| | |SIEMENS side, before the value is sent to the original address. |

|/ct=5 |minimum timeout (in seconds) |Parameter makes the internal timeout period (waiting to an answer from SYTRANS|

| | |300-CS) configurable. This parameter should be adjusted, depending on the |

| | |site-specific CS275 bus load. The Interface was tested with ct = 5. |

|/os=238 |"Scan Off" number in Digital State |A Scan Off digital state should be defined in the Digital State Table. |

| |Table |Parameter inform the Interface about the corresponding number in the Digital |

| | |State Table so that the Interface could make use of it. The recommended value |

| | |(fits with other interfaces) is 238. |

|/shutdown=shutdown |optional digital state written to PI |With the shutdown switch one can specify an optional digital state written to |

| |on shutdown |all tags on interface shutdown. If the digital state contains spaces it is |

| | |necessary to use double quotes. e.g. /shutdown="i/o timeout". |

|/deb=0 |optional debug level (defaulted to 0) |Gives the opportunity to start the Interface in a debug level. A value of 0 is|

| | |standard and only error messages will be logged. Debug levels range from |

| | |1...4. As higher the number as more information you get. Especially in case of|

| | |problems in the startup phases (for example YRun) this option can help |

| | |analyzing problems. The only other way to switch debug level is from within |

| | |TCSCP Control Program. |

|/tstamp=0 |optional VMS timestamping (defaulted |If 1, then VMS timestamps are used. |

| |to 0) | |

|/reset=0 |optional Restart of SY-TRANS |If 1, initialize communication hardware of SY-TRANS while getting mastership. |

|/pievgrp=1 |optional Event Group for Event Log |Eventgroup for interface events in Event Log. Defaulted to (interface number) |

| | |+ 82. |

| |Failover (all optional): |The interface is able to run in two processes, one for normal operation and |

| | |one for failover. Each process can talk to a separate SY-TRANS If |

| | |/gft="tagname" is specified, where tagname is an integer PI tag, defined as |

| | |Lab Value (Point Source = L), the interface runs in failover mode. To be able |

| | |to start the interface, parameter /gf1 specifies the snapshot value this |

| | |failover tag must have. |

|/gft="sy:fail" |failover control tag |If the snapshot value of the Failover Tag /gft is /gf1, the interface process |

| | |should start collecting data. |

|/gf1=1 |run if failover tag is /gf1 |If the interface is unable to collect data, it changes the value of /gf1 to |

| | |/gf2 to start the second interface. |

|/gf2=2 |set failover tag to /gf2 when line | |

| |goes down | |

|/connect=OFF |wait after (ON) or before (OFF) to |The interface can wait before (OFF) or after (ON) connection to the SY-TRANS |

| |connect to SYTRANS |for activation by /gft. |

|/gfd=239 |failover digital state number |If failover occurs, the active interface passes this value to all tags |

| | |configured for this interface. |

|/gfc=30 |seconds between line break checks |The interface check regularly for line breaks. The parameter /gfc is the |

| | |period in seconds to perform a line break check. |

|/mi=OFF |this is master interface (ON) or not |If /mi=ON this interface takes control of collecting data whenever it starts.|

| |(Off) |The Interface on PI Netnode should be the master interface. |

|/gftcheck=2 |if failover tag doesn't change within | |

| |/gftcheck seconds, take over data | |

| |collection | |

|Windows NT: |

|/host=localhost:5450 |hostname of PI server |The name of the PI Server to connect to. If this interface runs on a PI3 |

| | |Server, this should be /host=localhost:5450. |

|/output=C:\PIPC.LOG |optional output file name |The name of the interface logfile, all messages will be written to that file. |

|/pass=password |optional password for PIADMIN account.|The password for connecting to the PI Server. Use only upper case, because all|

| | |command line arguments are converted to upper case. |

On VMS systems, calling TCSPIStart- directly, the Interface is started in interactive mode. Instead of sending log information into a file, the Interface will display all messages on the screen. This could be used for debug sessions as well.

Note:

The OPEN_CS software also provides a Demo program (CSDEMO). Do not make use of it during Interface run. The Interface will not automatically take mastership for getting data if CSDEMO has it. The Interface only gets mastership at startup or after being restarted (TCSCP> restart).

To automate startup, you may add the line above to PISysMgr: on OpenVMS or to C:\PI\ADM\PiSiteStart.bat on Windows NT.

Shutdown

OpenVMS Version

To shutdown the interface, add the following line to PISysMgr::

$ @PISysExe:TCSPIStop-1

The shutdown procedure may take a while in order to leave the CS275_SERVER_xx modules in a correct status.

A manual shutdown can be performed from within the Control Program:

$ run PISysExe:TCSCP

TCSCP> shutdown/id=1

TCSCP> exit

or just call:

$ @PISysExe:TCSPIStop-1

The Interface will mark all Input tags with the digital state value Shutdown.

Windows NT Version

Pressing CTRL-C will stop the interface.

The Interface will mark all Input tags with the digital state value Shutdown.

If you are running the Interface as a NT service you can stop the Interface by running

Tcspi –stop

From the directory holding the Interface files. you may add this line to the PISrvSitestop.bat file.

Multiple Links on one PI Node

The Interface uses one Gateway exclusively but if more than one Gateway is available, the Interface can start multiple times.

To support a second Gateway, follow the guidelines below:

OpenVMS Version

1. Modify the OPEN_CS command files to support mailboxes MBX$CS275_INPUT_02, …

2. Copy tcspistart- to tcspistart-

3. Edit tcspistart- in the way that /in=2

4. Copy tcspistop- to

5. Edit tcspistop- in the way that /id=2

Tags for the second interface must have Location1 = 2

Windows NT Version

1. Modify the OPEN_CS command files to support named Pipes CS_IN02, ...

2. Create multiple directories TCSPI01, TCSPI02, …

3. Rename tcspi.exe and tcspi.bat to tcspi01.exe, tcspi02.exe, …

4. Follow the instructions to install the services for tcspi01, tcspi02 …

1. Edit tcspi02.bat … to reflect the interface number (/id=2) and to reflect the appropriate output file /output=…/tcspi01.log

Tags for the second interface must have Location1 = 2

IO Rate Tags

An IO Rate point can be configured to receive 10-minute averages of the total number of exceptions per minute that are sent to PI by the interface. An exception is a value that has passed the exception specifications for a given PI point. Since 10-minute averages are taken, the first average is not written to PI until 10 minutes after the interface has started. One IO Rate tag can be configured for each copy of the interface that is in use.

There are two configuration steps.

Step 1 – PI Point configuration on the PI Server

For step 1 and 2, it is assumed that the name of the PI tag is inf001.

PI 3 Server Nodes:

Create an IO Rate Tag with the following point attribute values.

|Attribute |Value |

|PointSource |L |

|PointType |float32 |

|Compressing |0 |

|ExcDev |0 |

The default settings can be used for the remaining PI Point attributes. When Compressing is set to Zero the IO Rate Tag acts like a heartbeat tag for the interface, which can be examined easily in ProcessBook with markers turned on. If a value is not written to the IO Rate Tag every 10 minutes, then there is problem with the interface communication.

Step 2 – Configuration on the Interface Node

For step 2, it is assumed that the name of the IO Rate point on the home node is inf001.

1. Edit/Create a file called iorates.dat in the PIHOME\dat directory. The PIHOME directory is defined either by the PIPCSHARE entry or the PHOME entry in the pipc.ini file, which is located in the \WinNT directory. If both are specified, the PIPCSHARE entry takes precedence.

Since the PIHOME directory is typically C: \PIPC, the full name of the iorates.dat file will typically be C:\PIPC\dat\iorates.dat.

Add a line in the iorates.dat file of the form:

inf001, x

where inf001 is the name of the IO Rate Tag and x corresponds to the first instance of the /ec=x flag in the startup command file. x can be any number between 1 and 34 or between 51 and 200, inclusive. However, it is best to use an event counter, x, that is not equal to 1 because 1 is the default event counter for Uniint-based interfaces. To specify additional rate counters for additional copies of the interface, create additional IO Rate tags and additional entries in the iorates.dat file. The event counter, /ec=x, should be unique for each copy of the interface.

2. Set the /ec=x flag on the startup command file of the interface to match the event counter in the iorates.dat file.

3. The interface must be stopped and restarted in order for the IO Rate tag to take effect. IORates will not be written to the tag until 10 minutes after the interface is started.

The 10-minute rate averages (in events/minute) can be monitored with a client application such as Processbook.

TCSCP Control Program, OpenVMS only

To run the TCSCP Control Program, enter RUN PISysExe:TCSCP at the DCL prompt.

The TCSCP prompt will then appear:

TCSCP>

TCSCP works like other VMS control programs such as LATCP or NCP. TCSCP allows you to:

• See the status of the interface and also

• Force the interface to exchange data independent of the scanning rates.

The procedure makes special use of this utility, since it is necessary to end all current conversations before being able to shutdown the interface.

Some powerful commands are:

|YRUN |Rescan all Y-Addresses of tags (only tags that are part of the Interface lists; not |

| |applicable to rejected tags) |

|MONITOR |Display full screen statistical information |

|GET YADDRESS |Display internal Y-Address in hex format for a specific tag |

|GET VALUE |Creates a special PR telegram for a single tag and requests the value from SIEMENS |

|WRITE ALL |Send all available Output values via PW independent of exception and scan rate |

|RESTART |Causes a complete Interface restart; especially all rejected tags will be tested again |

Note If the tag for which you want to call GET VALUE has Location 2 = 3, make sure to request the Y-Address before. If the Y-Address is not available, a wrong result would appear (and written in the Archive).

For a summary of all commands, see "Helpfile for TCSCP Control Program, OpenVMS only" on page 37.

Error and Information Messages, OpenVMS only

You can find messages from the interface in two places:

• The PI message log, PISysMgr:PIMessLog.txt. The interface puts its error and information messages in this file except for messages from fatal errors that prevented the interface from starting up.

• The interfaces output file, PISysExe:TCSPI-n.out. All fatal error messages are copied to this file. This includes VMS tracebacks. The interface also copies selected messages to this file and debug information (if debug is on).

A way to display Interface error messages could also be the usage of Event Logger displays. A simple selection could be done in searching for the string "TCS-1:".

An advantage is that

• The messages will appear in real-time while the logfile TCSPI-1.out is assigned to the VMS Interface process and

• New messages can be shared with other users only after a certain amount of time (a DCL type of TCSPI-1.out would not display messages from the last few seconds).

Errors related to tag values will also be reported in giving the tag a BAD INPUT state. This happens, if the status of a value derived from SIEMENS side is BAD or a Parameter Read (PR) request cannot be performed.

Input tags can also get a status of I/O Timeout if the Interface detects line or connection problems. Line checks will be performed every 30 seconds.

There is an extra timeout check for AKS and BKS tags. The minimum time period between new values must be less than SCN in order to avoid timeout status.

Note:

Each tag can have a different SCN value, but only the lowest one out of a group of tags will be used.

How TELEPERM-M/ME Interface Operates

At startup, the Interface checks all command line parameters.

If one of them is out of range, the interface generates an error message and stops.

If the parameters are all right, the interface runs the initialization part. Here it assigns the specified OPEN_CS session.

If a connection is not established immediately, the interface will terminate itself. Once connection is made, a list of all the tags with the interface point source and configured for this special interface number is collected. A mailbox for use with the TCSCP Control Program is created. Now the interface proceeds with the so called YRun.

Here are external addresses converted to internal Y-addresses. All tags with Location 2 != 3 are involved.

Data acquisition:

Input:

Values are exchanged on different ways. The best way to receive data is in using the AKS/BKS/MKS functions. Here the Interface applies for the TELEPERM-M/ME modules. Thereafter the TELEPERM-M/ME System automatically sends data to the Interface on a cycle basis. To stop this, the Interface must give notice of its departure. This is normally done when the Interface has to be shutdown via the TCSCP Control Program. Notification and denotification can also be made manually in using Control Program commands.

Special care needs to be taken to SB (Status, Module and Central-Part) Telegrams. The interface needs to notify itself for SB reception at interface start. In order to not overload the bus system (after notification all status information of a bus member is transferred to update the application), the interface should not notify many bus members at the same time. That is why the configuration parameter SCN=nn (in the Extended Descriptor of the SB Administrator tag) gives a delay for nn seconds before the next bus member is notified. The process of SB notification runs in parallel to already performed data scans! Start of SB notification and end of SB notification (last module was notified) will be reported in the log file.

Another way to receive data is the Parameter Read Function. Here the internal Y-addresses are used to identify the values in the TELEPERM-M/ME System. In earlier versions CS275_SERVER did not allow to request data using direct Y-Addresses, instead own indices are used. AKS, BKS MKS and SB tags are retrieved asynchronously and do not have that limitation!

Tags configured for PR and PW data acquisitions are grouped together and periodically scanned with the rate passed in the Extended Descriptor (SCN=nn). All values for data types real, integer and discrete are saved in the PI Archive by using the function PISendExceptions (Exception Reporting).

A PI tag that is configured to read a character string (S2, S4, S16), will be put in the Event Logger preceded with TCSEvent > and the PI tag name. A 1 will be put into the PI tag for a new string and a 0 if the string is the same as the previous scan. The Value of the tag goes back to 0 after one additional scan. This means (if used for the Batch Monitor) that changes to the string must be less frequent than the scantime to receive step stair lines for the tag!

If for any reason (wrong configuration, bus problems...) the Y-Address of a PR tag cannot be requested, the Interface will, after a number of retries, reject and delete the tag from the internal list. The only way to get this tag back to the Interface list is in restarting the Interface or editing the tags database so that the "Sign-up for Updates" functionality of the Interface catches it.

If an error marked value is transferred by the TELEPERM-M/ME System, this value will be marked as BAD INPUT in the PI System.

Output:

If the Output-Gate flag is enabled (command line parameter P4), then writing data works the same way as reading data, but using Parameter Write functions instead. Snapshot values are sent to the TELEPERM-M/ME System, if at least one output tag changes value (Exception Reporting). But the time between send conversations is in any case at least SCN seconds, where SCN is specified in the Extended Descriptor.

Scan rates for Parameter Read and Write cycles are by default 60 seconds.

A special situation occurs direct after Interface startup. Normally a value will be sent only, if it changes since startup. In other words the Interface behaves like if it was never stopped. This is important for automatic DCL restart (line failure, restart,...) and manual control. But anyhow, the SIEMENS system can be updated with all values, using the Control Program command: WRITE ALL (OpenVMS only).

Messages:

The Interface can be enhanced to support reception of Messages in a later Version (already supported by OPEN_CS).

Time-outs:

Different time-outs are realized.

If a ´total´ timeout between CS275-SERVER and the TELEPERM-M/ME Interface occurs, a message is written and all TELEPERM-M/ME tags with the according interface number will get an I/O Timeout value. The reestablishment of the communication will be reported too.

The Timeout value is automatically adjusted to the minimum scan rate, but not to be above 180 seconds. After a timeout the Interface performs an internal restart using the OPEN_CS function "delete_buffer_contents". After a number of retries and fails the Interface restarts completely including a new YRun.

If the line is not back again the Interface wait and try to get mastership in one minute cycles.

AKS and BKS tags are observed to get at least one value per SCN period. If not, a timeout will be reported to the tags.

Failover

Starting with version 6.11 the interface is able to run in two modes, as master interface and as failover interface on another PI node. The failover interface is ready-to-run and waits till the master interface fails, then it starts data collection to provide continuous data even if one PI node fails.

The communication between the two interfaces is managed by one PI tag. By this way the interfaces can run on different systems (for example the master interface runs on an NT node collecting data while the failover interface runs on a PI2 server on OpenVMS).

To configure the interface in failover mode first you have to create a PI tag (for example SY:FAIL, use SY:SNP001 as template) and a digital state (for example 239:FAILOVER) for proper operation of the failover mechanism.

You must have the ability to connect two systems to the SYNOTEC gateway and you must have two PI nodes to run the interface in failover mode.

The best way of taking advantage of the failover capabilities of the interface is to run the master interface with switch /mi=1 on a PINet node and the failover interface on the PIHome node. In this case the home node takes over data collection if the net node fails or the communication between home and net nodes disappear. If the net node reconnects to the home node it stops the failover interface and takes over data collection. This mechanism involves the problem that if the communication between PIHome node and PINet node stops while both PI systems are running proper, both interfaces will collect data.

If this happens you should execute the following steps to avoid corruption of your archive data:

Stop the PINet node.

1. Delete the file pisysexe:eventq.dat. This step deletes all data collected by the PINet node since communication with PIHome node stops!

2. Reconnect the PINet node.

3. Start the PINet node. The master interface on the PINet node stops the failover interface and starts data collection.

If you do not delete the pisysexe:eventq.dat many error messages will be created by pisn_sendexceptions while flushing pisysexe:eventq.dat to the archive.

It is not possible to provide an automatic reaction for the case that only the communication between the PIHome node and the PINet node fails. For this case a user action is always recommended.

To avoid data loss by deleting pisysexe:eventq.dat in case of connection failure between PIHome node and PINetnode it is recommended that you only run interfaces with failover processes running on a second PI Node on the PINet node.

Time synchronization

The SIEMENS/TELEPERM-M/ME Interface is capable of syncing the time between the PI home or PI API node hosting the interface and the TELEPERM-M/ME system. The interface supports the following two scenarios:

The SIEMENS/TELEPERM-M/ME interface is sending periodically a time synchronization telegram to the TELEPERM-M/ME system to set the TELEPERM-M/ME time according to the current PI time.

The SIEMENS/TELEPERM-M/ME interface is receiving periodically a time synchronization telegram from the TELEPERM-M/ME system and sets the current system time according to the TELEPERM-M/ME time.

If none of the Command line switches for time synchronization is used, time synchronization will be disabled.

|Command line switch |Description |

|/TSP |If present, the SIEMENS/TELEPERM-M/ME interfaces will periodically send a time |

|/TSP=3600 |synchronization telegram to the TELEPERM-M/ME system. The period will be every seconds. |

| |The default is 3600s. Minimum value 60s, maximum value 86400s. |

|/TS1 |This is the minimum time the PI time and the TELEPERM-M/ME time must differ before the |

|/TS1=5 |interface will change the system time of the interface node. The default is 5 seconds. |

| |Minimum value 2 seconds, maximum value 60s. |

|/TS2 |This is the maximum time the PI time and the TELEPERM-M/ME are allowed to differ for the |

|/TS2=600 |interface to correct the system time. If the time difference is more the interface will not |

| |try to change the system time but will write warning in the log file. The default is 60s. |

| |Minimum value 10 s, maximum value 600s. |

Hints for the System Manager

• The AKS/BKS/MKS modules hold a list of where to send parameter telegrams automatically (not only PI-Interfaces). The maximum number of entries in those lists is 6. Ask your TELEPERM-M/ME System Manager for your special configuration and how many entries are free to use for PI-Interfaces (tags defined for a certain AKS/BKS/MKS module and having the same interface session number counts as one entry).

• Output is not buffered, what means only Snapshot-Values are reported to the TELEPERM-M/ME System.

• If the scheme of the TELEPERM-M/ME System will be reconfigured, stop the concerned interfaces and restart. Or run TCSCP, disable send and receive, call YRun after TELEPERM-M/ME changes and reset the previous constellation.

• A change for S16 tags if used for Batch Monitor interface must be stable for at least 2 scan cycles.

• The Interface was last tested under the following configuration:

OpenVMS on ALPHA 6.2

PI 2.1.0

Teleperm ME

AS 220 EA, AS 220 E

Gateway SY-TRANS 300CS 7.1

OPEN_CS 6.1

One session (CS275_SERVER_01)

Windows NT 4.0 on HP Netserver 5/166LS (Pentium 166/ 128MB)

PI 3.0 Build 1.76

TelepermM AS 235

Gateway SY-TRANS 300CS 7.1

OPEN_CS 7.0

One session

Helpfile for TCSCP Control Program, OpenVMS only

TCSCP>help *...

CONNECT

The TCSCP Control Program communicates to the Interface subprocesses

via mailbox. To prohibit multiple access to one subprocess, every

TCSCP is connected to an ID.

CONNECT

Command_Qualifiers

/ID

The Interface with the specified ID will be selected for most of

the other commands.

DISABLE

To be able to prohibit Parameter Read and/or Parameter Write

telegrams, use DISABLE.

DISABLE

RECEIVE

The Parameter Read cycles are disabled.

DISABLE

SEND

The Parameter Write cycles are disabled. In addition to the

output gate flag in the Interface start parameters, this is

a way to protect the SIEMENS/Teleperm-M modules from new

configurations.

DISABLE SEND, configure output tags, double check the internal

Y-Address via GET YADDRESS, ENABLE SEND.

ENABLE

This command enables Parameter Read or Parameter Write cycles.

ENABLE

RECEIVE

If RECEIVE is enabled, all tags configured for Parameter Read

request their current value in 'scan' seconds time steps.

ENABLE

SEND

If SEND is enabled, the configured output tags send their current

value via Parameter Write telegrams in 'scan' seconds time steps.

If the value did not change since last download, no telegram

will be sent for this tag (output is exception based).

EXIT

This command resets the selected Interface mailbox and exits

the TCSCP Control Program.

GET

The GET command is always connected with a complete telegram

exchange between the current Interface (-ID) and the according

OPEN-CS Server module.

GET

YADDRESS

Using this command, it is possible to distinguish the internal

Y-Address of a certain tag. If a tag is defined for AKS/BKS/MKS

read only, it is not necessary to hold the internal Y-Address of

such a tag. But, if the Control Program asks for the actual value

via Parameter Read, it is necessary to have the internal adderess.

For AKS/BKS/MKS-only tags, the Y-Address is requested, but not

saved into the PI tag database, but is now possible to call

GET VALUE for such tags.

After Interface restart, the Y-Address is set back to 0.

The GET YADDRESS is also of use for control purposes.

Format:

GET YADDRESS tagname

GET

VALUE

If the internal Y-Address is available, the current value is

requested from the SIEMENS/Teleperm-M system via Parameter Read

telegrams. The value and the status are displayed, if the

communication was successfull.

Format:

GET VALUE tagname

GET

VALUE

Command_Qualifiers

/TIMEOUT

If the CS275 bus is very bussy, it can take a while to get the

asyncronious Parameter Read return telegram.

To be able to return to the command prompt TCSCP>, it is

possible to specify a timeout period.

The minimum timeout value depends on the sleep value. The evaluation

of an arrived telegram is delayed for a maximum of 'sleep' seconds.

The default for TIMEOUT is preset to 30 seconds.

The passed value is in seconds.

Format:

GET VALUE tagname /TIMEOUT=20

MONITOR

A lot of important Interface parameters are displayed on a

permanent basis. The following key words are used:

Configuration:

Input tags: number of input tags configured

Output tags: number of output tags

AKS: number of notified AKS telegrams

BKS: number of notified BKS telegrams

MKS: number of notified MKS telegrams

SBA: number of status notifications

PR : number of Parameter Read telegrams

PW : number of Parameter Write telegrams

Status:

Send : min. scan rate for Parameter Write

Receive : min. scan rate for Parameter Read

Output Gate: Interface status for writing values

Debug Level: actual debug status

Sleep: time between evaluation cycles

Queues:

Y requests (total) : Y-Addr. calls since startup

OPEN-CS errors/time : errors per fixed time unit (120sec)

OPEN-CS errors (total): errors since startup

Resets: number of reset functions

Reference Counter:

TX: number of OK sent telegrams

RX: number of OK received telegrams

SB: number of status telegrams received

MONITOR

Command_Qualifiers

/ID

The Interface with the specified ID will be selected for MONITOR.

Format:

MONITOR /ID=2

/REFRESH

The screen is updated every n seconds. Default is 15 seconds.

Format:

MONITOR /ID=2 /REFRESH=5

NOTIFY

This command manually notifys the automatic send procedure within

a certain SIEMENS/Teleperm-M module, for example AKS telegrams.

If the notify telegram was successful, the Interface receives

values on a permanent basis.

Format:

NOTIFY tagname

Tagname can be any tag configured for the desired AKS, BKS, MKS.

RESTART

Restarts the complete Interface, including a new YRun

with all tags configured for the Interface.

SET

The SET command will allow you to set various parameters that

are able to influence the behavior of the SIEMENS/Teleperm-M to PI

Interface. There are several according SHOW commands.

SET

DEBUG

Using this command, it is possible to set the SIEMENS/Teleperm-M

to PI Interface into debug mode. This means, that more messages

are printed out. If the Interface runs in detached mode,

additional messages are written into the file TCSPI-n.OUT

(this is the normal situation).

If the Interface runs interactively (someone has started it from

the command prompt), all additional messages are displayed

directly on the screen.

SET

DEBUG

Command_Qualifiers

/OFF

The off qualifier is active by default. All debug informations

are disabled.

/ON

Additional Interface messages are enabled. It is so possible to

see what actions the Interface performes at the moment.

/LEVEL

Different debug levels are available. As higher the level is, as

more information will be displayed. Maximum level is 4.

Format:

SET DEBUG /ON /LEVEL=n

SET

SLEEP

The Interface contains lib$wait functions to lower the CPU load

and to overcome the time between communication. If the Interface

sleeps, only mailbox communication and reception of telegrams

by interrupt is enabled. So, be careful to set this value.

The default is 1 second.

Format:

SET SLEEP 5

SET

SIGNUP

The Interface is able to handle changes within the PI tag

database.

This function is called SignupForUpdates. The update of internal

Interface lists happens every n seconds. The default value is

60 seconds.

Format:

SET SIGNUP 5

SET

IDACT

This command is for OSI SOFTWARE personnel only!

SHOW

The SHOW command will allow you to show the various parameters

that are able to influence the behavior of the SIEMENS/Teleperm-M

to PI Interface. There are several according SET commands.

SHOW

INTERFACES

This command will type out the available Interface subprocesses.

SHOW

TAG_COUNTER

This will display the number of configured input and output tags,

configured for the connected Interface subprocess.

SHOW

SCAN

The SHOW SCAN command displays the lowest configured scan rate.

The Interface sends telegrams to the OPEN-CS Server module for

PR and PW type telegrams depending on the scan rates.

SHOW

SCAN

Command_Qualifiers

/RECEIVE

Using the RECEIVE qualifier, the lowest scan rate to ask for

values will be displayed. This qualifier is active by default.

/SEND

Using the SEND qualifier, the lowest scan rate for downloading

values will be displayed. If values are really transferred,

depends on the Output Gate Flag

(see command line parameters for TCSPI-n).

SHOW

ERRORS

The number of errors per time unit and the total number of

errors are displayed. Also the number of reset functions will

be shown.

SHOW

VALUE

The current values (value, istat) will be displayed for a specific

tag. This works only, if the tag is configured for the connected

Interface subprocess (TCSPI-n).

Format:

SHOW VALUE tagname

SHOW

SLEEP

This command will type out the sleep parameter, the Interface uses

to give other VMS processes more CPU time (the Interface calls

internally a lib$wait command).

The passed value is in seconds and should be smaller than the

lowest scanrates (see SHOW SCAN).

SHOW

SIGNUP

The Signup_For_Updates period will be displayed. This is, when the

Interface retrieves changes, within existing PI tags or newly

defined PI tags.

SHUTDOWN

The main task of the Control Program is, to be able to shutdown the

active Interfaces properly.

Attention! Do not use the VMS STOP command instead.

SHUTDOWN

Command_Qualifiers

/ID

The Interface with the specified ID will be selected for the

shutdown procedure.

Format:

SHUTDOWN /ID=2

/ALL

All Interface subprocesses between 1 and IDMAX will be shutdown.

/ALL is active by default.

/FORCE

If not all denotify telegrams were answered (TX != 0) after a

timeout period, the Interface stops albeit.

Otherwise it remains active.

/TIMEOUT

You can specify the period of time, waiting for correct response.

The defaulted value is set to 30 seconds.

Format:

SHUTDOWN /ID=2 /TIMEOUT=20

TERMINATE

This command denotifies the automatic send procedure within a

a certain SIEMENS/Teleperm-M module, for example AKS telegrams.

This gives manual control over the Interface. But, remember

the AKS,... to notify again. Otherwise the Interface must be

shutdown and restarted.

Format:

TERMINATE tagname

Tagname can be any tag configured for the desired AKS, BKS, MKS.

WRITE

Force to write all available output tags.

WRITE

ALL

Send all tag values which are online and within their ranges.

Shutdown, I/O timeout... states will not be sent.

Format:

WRITE ALL

YRUN

A complete new run to request the internal Y-Address for all

configured tags (with the same according interface number)

will be done. This is important, if the scheme of the

SIEMENS/Teleperm-M system changed.

If the Interface runs on the PI home node, Y-addresses will

be logged in Location 4 and 5 for control purposes.

All tags receive their Y-Address on Interface startup.

Revision History

|Date |Author |Comments |

|21-Oct-1999 |AS |added chapter talking about pipe names |

|30-Dec-1999 |AS |added /shutdown parameter |

|09-Jun-2000 |AS |added String tag support |

| | | |

-----------------------

[1] String tags can not be displayed in the current version of PI-ProcessBook (2.12), however, PI-PB comes with an ActiveX control capable of displaying the value of String tags.

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download