VISONIK® DCS Functions and System Messages VVS 18 Siemens Building Technologies Landis & Staefa Division
Siemens Building Technologies AG Landis & Staefa Division Gubelstrasse 22 CH-6301 Zug Tel. +41 41 - 724 24 24 Fax. +41 41 - 724 35 22 © 1999 Siemens Building Technologies AG Quality approved ISO 9001 EN 9001 http://www.landisstaefa.com CM2U8567E / 04.
Table of Contents Siemens Building Technologies Landis & Staefa Division 1 Quick Guide..................................................................................................1-1 1.1 1.1.1 1.1.2 Introduction ....................................................................................................1-1 Read this first.................................................................................................1-1 Terminal operation and Ctrl modes.....................................
CM2U8567E / 04.1999 II 2.7 2.7.1 2.7.2 2.7.3 2.7.4 2.7.5 2.7.6 2.7.7 CMB Circular Message Buffer.................................................................... 2-39 Initial Access and Handling ......................................................................... 2-39 LIST, Print Message Buffer ......................................................................... 2-39 LDAT, Review of Messages by Date...........................................................
Siemens Building Technologies Landis & Staefa Division 2.13 2.13.1 2.13.2 2.13.3 2.13.4 2.13.5 2.13.6 2.13.7 DRR Date/Time Reaction Register ...........................................................2-125 Initial Access and Handling........................................................................2-125 CH, Enter/Change Data .............................................................................2-127 LI, List Data Registers ......................................................................
CM2U8567E / 04.1999 IV 2.21 2.21.1 2.21.2 2.21.3 2.21.4 2.21.5 2.21.6 MXD Maximum Demand Register Entries................................................ 2-187 Initial Access and Handling ....................................................................... 2-189 CH, Enter Sheddable Loads or Generators .............................................. 2-190 LI, List Entries............................................................................................ 2-194 L8, List Entries in Octal ..........
Siemens Building Technologies Landis & Staefa Division 2.28 2.28.1 2.28.2 2.28.3 2.28.4 2.28.5 2.28.6 2.28.7 2.28.8 2.28.9 2.28.10 2.28.11 2.28.12 2.28.13 2.28.14 2.28.15 2.28.16 2.28.17 2.28.18 2.28.19 2.28.20 2.28.21 2.28.22 2.28.23 2.28.24 2.28.25 2.28.26 RPT Reports .............................................................................................2-249 Initial Access and Handling........................................................................2-249 Entering the Address Range.........
CM2U8567E / 04.1999 VI 2.32 2.32.1 2.32.2 2.32.3 2.32.4 2.32.5 2.32.6 2.32.7 2.32.8 TRR Time Reaction Register ................................................................... 2-325 Initial Access and Handling ....................................................................... 2-325 CH, Enter/Change Data ............................................................................ 2-327 LI, List Data Registers ...............................................................................
1 Quick Guide 1.1 Introduction These short instructions are for users who are not very familiar with the VISONIK systems. In the following chapters, addressing of data points, terminal operation and working with the Ctrl-P, Ctrl-D and Ctrl-V modes are described briefly. The 'Introduction' chapter provides information on this quick guide. For system knowledge and technical notes, the related documents are referenced.
Which simplifiers have been used? Reference documentation 1.1.2 This quick guide uses the following simplifiers: Simplifier Meaning ENTER, CTRL, ... Actuate the respective key CTRL+P Actuate the CTRL and P-key simultaneously Confirm Confirm entries or close entries, messages or details (by actuating the ENTER or↵ keys). pro Text entries are generally indicated in bold print. Ex.: Enter function PRO (reports). Example Examples for entries within procedures are generally printed in Courier font.
1.1 System access Establishing communications :T7 In order to work with the system (e.g. change parameter values and list reports), a connection must have been established between the VISONIK system and the terminal. Establishment of a connection is indicated as follows on-screen: v18.01.001 VISONIK PC050 09.02.1999/Tu 12:13 ____________________________ V I S O N I K Version 18 Building Management and Supervisory System Ctrl/P = Function 1.1.
A list of all available functions is displayed. Refer to the overall documentation (VISONIK Functions and System Messages, V18) for further information on functions.
1.3 Address entries VISONIK uses: 1.3.1 • technical addresses (octal or decimal addressing) and • user addresses. This chapter briefly explains the meaning of technical addresses and user addresses. Additionally, the manner in which address ranges are entered for both addresses is also explained. Refer to the overall documentation (VISONIK Point Types and Parameters, V18) for further information on addresses.
How to enter an address range If you want to include all existing data points of the DCS, enter the following: $* If you want to include all data points of process station 52 from address range 020 to 030, enter the following: $52’020..$52’030 IF you want to include all data points of process station 52, beginning at point 010 to process station 54, ending at point 030, enter the following: $52’010..$54’030 Specify a filter function for the following entry (three periods ‘...
1.4 Working in Ctrl-P mode (DCS dialogue) Important entries: Note the following important keyboard entries: CTRL+P Entering CTRL+P opens function PNT (change and list point parameters). It is the main function of the DCS dialogue and allows for checking and changing individual parameter values. CTRL+H By entering CTRL+H, the next higher entry hierarchy is opened. CTRL+E When Ctrl-P mode (DCS dialogue) is active, CTRL+E enables the terminal so that messages can be displayed on-screen.
For advanced users: If you know which function, address and parameter you want to change, you can use the direct entry option. Direct entry for hiwl (steps 1, 2, 3, 5, i.e.
1.1 Working in Ctrl-D mode The Ctrl-V mode is the same as the older version of the Ctrl-V mode. In Ctrl-D mode, only data points of the local system can be displayed. Within a linked system, Ctrl-V mode must be selected to select points from other systems. Proceed as follows to start the Ctrl-D mode: How do I proceed ? Step Procedure Comment 1 CTRL+D Start Ctrl-D mode 2 Enter and confirm data point address Technical or user address permitted.
Commands and functions PageDown, PageUp, These keys can be used to select another parameter group in Ctrl-D mode. The following parameter groups are possible: • Main parameter • Operating parameter • Configuration parameter • Service parameter CTRL+P Entering CTRL+P starts the DCS dialogue parallel to Ctrl-D mode in the bottom half of the screen. CTRL+H Entering CTRL+H allows for moving to the next higher entry hierarchy.
1.6 Working in Ctrl-V mode How do I proceed ? The Ctrl-V mode is the same as the new version of the Ctrl-D mode. In Ctrl-V mode, all data points of a linked system can be displayed. Proceed as follows to start the Ctrl-V mode: Step Procedure Comment 1 CTRL+V Start Ctrl-V mode 2 Enter and confirm data point address Technical or user address permitted. Delete individual characters using the backspace key or delete the entire address through direct entry.
CTRL+P Entering CTRL+P starts the DCS dialogue parallel to Ctrl-V mode in the bottom half of the screen. CTRL+K Entering CTRL+K closes Ctrl-V mode and provides the entire screen to the DCS dialogue. Example 1 Change and observe warning limits of a measured value Parameter HIWL indicates the upper and LOWL the lower warning limit. If one of these two limits is violated, a message appears on the terminal.
Terminal operation after entering >TRR and the new time is as follows: Time =08:00:08:30 (hh:mm, . ), > . On DO A'01'SB23 PSe DOK-Server TRR: DO | Set Digital Output: Priority=0 Week 49 30.11.
CM2Z8567E / 04.
2 Function Description 2.1 ACKN Alarm Acknowledgement 2.1.1 Initial Access and Handling Function call-up CTRL/P ACKN General Function ACKN provides the following facilities: – Individual or general acknowledgement of alarms. – Individual alarm acknowledgement with an associated message or additional clear text. – Listing of the last three status change messages associated with the displayed point.
2.1.2 Alarm Handling The following drawing shows which parameters are set upon appearance and acknowledgement of a basic alarm (ALconf=1). Required : ALconf = 1 ALsta= Normal acknowledged ALsta= Alarm acknowledged Acknowledge: ALvis = User code ALack = actual time ALwhen = actual time Alarm appears: ERSTA > 0 ALbeg = actual time ALend = undef. ALack = undef. ALcnt = 1 ALvis = -ALdist = 1 ALwhen = akt.
Select Alarm Status There is a choice of alarm states, as follows: – UAA: Point faulty, alarm unacknowledged. – AA faulty, alarm acknowledged. – UAIA: Point normal, alarm unacknowledged. – AIA: Point normal, alarm acknowledged. Select Priority Selection according to the alarm point's message priority, MSGP. PST NAME, TXI MV / ERSTA Table: Alarm point's Peripheral status, address and information text. Alarm point's main value or fault condition.
Display of acknowledged alarms in Function ACKN. STAP NAME,TXI MV/ERSTA | ALbeg | ALend | ALack |ALvi -------------------------+-------+-------+----------+----... rt'z PSST=Normal | |02.08.1996| Ron Training Department | |13:08:12 | 1 ---------------------------------+ ------+----------+-Acknowledge =Next_No : ? 0 Next_No =No, Go to Next Point 1 Prev_No =No, Go to Previous Point 2 Yes =Acknowledge, Go to Next Point 3 All =Ackn.
2.2 BCKP Shadow Backup 2.2.1 Initial Access and Handling Function call-up CTRL/P BCKP T8 15?42:37 Function=PNT : BCKP To=DU1: : ? To=SYS:,SY0:,SY1:,DU0:,DU1:,DU2:,DU3:,DU4:,DU5:,DU6:,DU7:DM0:,DM1:,DM2:,MM0: General Function BCKP allows on-line copying of a 'Shadow' version to a backup device which may be a tape unit or a VISONIK structured disk.
Example of a Shadow Backup on Tape MAN:T5 08:35:14 Function=PNT : BCKP To=MM0:: please wait! ..
Explanations .. SY Bsy School hall Zug A:Master 100000: Shadow Updating The Shadow version is re-structured, since the old one is more than one hour old MM0: Initialisation Tape is initialised. MM0: ;*** 08:35:03 Cmd-file-specifier: MMSAVE.COM Save code from disc to magnetic tape V002 4-Jan-96 *** The tape is first re-spooled then the Shadow version is copied.
CM2U8567E / 04.
2.3 BOOT System BOOT Function "BOOT" is an abbreviation for "Bootstrap" to describe the operation of pulling up (starting up) a system from scratch. "BOOT" is a small program held in non-volatile memory, protected against power failure. 2.3.1 Initial Access and Handling Function BOOT is opened through Ctrl/P followed by input of the name "BOOT" After "BOOT" a separating comma must be entered followed by a specifier for the type of 'Boot' (if necessary). Function BOOT is reserved for System Managers only.
2.3.1.2 System Halt All process data from VISONIK are continuously written on hard disk. This means that loss of data is kept to a minimum if there is a power supply failure. However, data traffic with hard disk is not possible in byte units, rather in packets of 1000 bytes (octal). This method of packet transfer has the disadvantage that it must not be interrupted. For this reason a VISONIK system must N O T be stopped with the computer console's HALT keyswitch or through switching off power.
2.4 BYE Exit from Terminal Entry into dialogue with the VISONIK DCS is through a personal 'User Code' and a 'Password'. The 'Password' and "Extra Device(s)" (for dialogue) are defined with Function KEY. To exit from the system requires no password, simply the Function BYE. With this action an exit is made from all those "Extra Device(s)" at which log-in took place using the same respective password. Any further access is blocked until a user again logs-in with his 'User Code' and 'Password'. 2.4.
CM2U8567E / 04.
2.5 CAL Calendar Operations 2.5.
Example with two standard calendars A company's schedule for 1st May is as follows: Administration: Normal working day Production: Holiday ==> special day schedule DCS Administration Production Special day class 1 (SDCL = 1) Special day class 2 (SDCL = 2) 8563Z01E Example with two std. and two individual calendars Individual special day programs are scheduled in the two substations connected via modems.
2.5.2.1 Special Days What is a special day ? There are some days on which a timeswitch program associated with another day of the week should run instead of that for the particular day. If, for example, a holiday falls on a Thursday and the DCS should automatically execute time reactions as if it were a Sunday, then the user can declare the date of this holiday as a special day in the special day register, i.e. in the above example entered as "Sunday".
7 standard Calendar Special day class 1..7 Individual calendar per PS Calendar 7 Entries ... $ 4'PS $ 2'PS Calendar 1 Entries .... .... .... $ 33`PS Entries .... .... .... .... .... .... .... .... .... Original DCS File 33 File 4 SDC SDC Backup (in File) 8563Z03E SDC File 2 BPS $ 33'PS 2.5.4 $ 2'PS $ 4'PS Operations 2.5.4.1 CH, Enter/Change Data The user can enter or change individual special days, where the following cases may exist: 1. 2. 3. CM2U8567E / 04.
1st case: No entry found --> New entry T8 15:29:42 Function=PNT : CAL Mode=SCAL : Operation=LIST : CHNG Calendar/PS=. : ? Individual Group 1..7 (e.g. 1, 2, 5, etc.) Group combination 1..7 (e.g. 2&3&5, -5&6, *, etc.) Technical Station Address (e.g. $23'PS) or User Address (Combination of Groups and Station Addresses not possible!) Calendar/PS=. : 1 Date=24.07.1996 : ? Date (e.g. 21-Dec-93) Date Range (e.g. 21-Dec-93..31-Dec-93) Holidays (e.g. Easter) Holiday + No.of Days (e.g.
2nd case: Entry found --> New entry T8 15:45:27 Function=PNT : CAL Mode=SCAL : Operation=LIST : CH Calendar/PS=. : * Date=24.07.1996 : 1-Jan..1-Sep No. Calendar/PS Date Special Day ------------------------------------------------------------1) 1 24.07.1996/We =Sd1 2) 2 01.05.1996/We =Sd2 3) 3 01.08.1996/Th =SuNumber=. : In this case a printout is given showing the found entry plus an entry number. If a date range is involved several entries may be found with consecutive entry numbers as illustrated above.
2.5.4.3 LALL, List All Data Operation LALL lists all existing entries. T8 16:01:41 Function=PNT : CAL Mode=SCAL : Operation=LIST : LALL Calendar/PS Date Special Day -------------------------------------------------------1 24.07.1996/We =Sd1 1 27.07.1996/Sa =Sd3 1 26.12.1996/Th =Su 1 31.12.1996/Tu =Su 2 01.05.1996/We =Sd2 2 22.09.1996/Su =Sd1 3 01.08.1996/Th =Su Operation=LIST : 2.5.4.
2.5.4.6 INFO, Information This section provides the following information for existing Standard Calendars: – current signature value – date and time of the last change – associated user password – date and time of last distribution 2.5.5 Link System The special day group, SDGP, of the DC Server is entered in its system point $SY. The special day group of a partner DCS is entered in the corresponding PS point. All partner DCS stations in a 'Link System' have the same special day calendars, SCAL (i.e.
2.5.6.1 CH, Change Entry Using operation CH the summer and winter start times can be newly entered or changed. ctrl/P T8 16:12:32 Mode=SCAL Operation=LIST Changeover=EC Norm 0 Off 1 On Man.
2.5.6.4 SEND, Send Summer / Winter Time The DCS sends the "Summer / Winter Time" to all process stations under the following conditions: • Through manual operator order using the CAL,SOWI,SEND function • Always automatically at midnight if the entry has changed and was not manually passed to the PS. T8 16:20:27 Function=PNT : CAL Mode=SCAL : SUWI Operation=LIST : SEND >>o.k.! Operation=LIST : CM2U8567E / 04.
2.6 CB Central COLBAS Tasks Depending on specific project disk structuring there is a pre-defined number of up to 40 VISONIK COLBAS Tasks (TSK1 to TSK40) in the Server. The individual Tasks (called TASK or TSK in the following text) can be called up through Function CB. – VISONIK Tasks (TSK1 to TSK40) and PRV/BPS/EKL COLBAS Tasks (TSK1 to Note – – 2.6.1 TSK199) can be programmed by the user.
2.6.3 Edit and Control Commands 2.6.3.1 Description of the Commands Command ? ACT m,n CLEAR COPY DEL m,n CM2U8567E / 04.1999 2-24 Meaning HELP = Printout of all COLBAS language elements. Lists status of all opened Tasks. - Task running (active). - Task stopped (inactive). - Task waiting (e.g. until timeout of a delay). - Task is currently printing a message. - Task is being edited. ACT may be input with or without Task numbers m,n: ACT = Lists status of all opened Tasks.
LOAD Loads a Task from Dump File to the currently selected Task. After LOAD and the System requests (if the File is not yet defined) the file number and Task number, i.e. the Task to be loaded from the Dump file to a selected Task is then specified. The "old" lines in the selected Task are overwritten. Lines with errors (from Dump File) are printed out and tagged, but are otherwise ignored.
Syntax for TASK-# In the following commands a Task designator may be entered, where commands EDIT, LOAD, SAVE are only effective in TSK1 to TSK40. DIR DIR [task] ---> e.g. DIR [33] or DIR TSK33 DIR VAR [task] EDIT #file,[task] ---> e.g. EDIT #35,[33] LIST [task] LOAD #file,[task] SAVE #file,[task] SCR task ---> e.g. SCR 35 or SCR35 TSK task Input of ranges is permitted as illustrated in the following examples: [1..3] [..6] [4..] [*] [..] [] TSK12..
2.6.3.3 Examples of Edit and Control Commands TSK1 : TSK4 TSK4 : TSK1 : DEL , TSK1 : LIST ,20 Change Task 1 to Task 4 Response of new Task Delete all lines in Task 1 Print all lines from start, up to and including line 20 TSK1 : ACT 4,10 --> Print status of Tasks 4..1 TSK5 : SAVE --> Save Task 5 File#=1: 2 --> Number of an available File. ---> End of SAVE in file! TSK6 : LOAD File#=1: 2 Task#=6: 6 --> --> --> --> > > > Load file to Task 6. Number of desired File. Number of desire Task.
Every line in a COLBAS Task begins with a line number followed by one or more statements: TSK11 : 300 C=A+B; PRINT C --- ----- ------| | | | | +---> | +-----------> +----------------> 2nd statement 1st statement Line number Line numbers must lie in the range 1..32767. After terminating a line entry with an analysis of the syntax begins. A line containing errors must be re-entered. Syntax error-free COLBAS statements are deposited in the relative Task according to line numbers in ascending order.
Format Numerical quantities can have the following formats: Integer: 1, 2, 12, -345 etc Real: 0.345, -45.4, 12E+5, etc. Date: 1-FEB-88, 1.2.88, 1.2.1988, 01-02-88 etc. Time: 12:00, 8:01:30 etc. Text/String All characters which are enclosed in double apostrophes (") are interpreted as clear text. e.g.: "A=5", "Comment", "How are you?" etc. Rules for COLBAS – COLBAS syntax does not depend on [BLANK] and [TAB] as long as the input is unambiguous.
LET LINE INPUT yes no Assign value to a variable Input of a complete line MSG yes Send message for printout via system.
FLT$ FREE s n Format conversion Binary->ASCII Remaining memory space in a Task HYS n Hysteresis function INSTR INT n n String search Round up to whole number LCASE$ LEN LOC LOG s n n n Change all upper case to lower case letters Gives the length of string Gives the number of bytes used in a file Natural logarithm MAX MIN MOD MONTH n n n n Maximum of all arguments Minimum of all arguments Modulo division Month of a given date PI POS n n 3.14159...
Note – Expressions with highest priority are enclosed in round brackets. 3*5+1 = 16 3*(5+1) = 18 – Signs "+" and "-" are accepted but have the same priorities as addition and subtraction. – Multiplication must always be indicated by the sign "*". – A power exponent is described with "**". – A negative number with a fractional power exponent (e.g. (-2)**0.5), gives a result which cannot be recognised by COLBAS. Therefore an error message is given.
Task variables are pre-defined variables with fixed names and are designed for specific Task control actions for inputs (INPUT) and outputs (PRINT, PLOT). TSKPRP TSKTAB TSKTTY controls the presentation of Task prompt defines the tabulator field length of an output line. defines a Task's input/output terminal Task variables can be used as normal variables in Statements, Functions or Expressions. The only exception is in FOR statements.
2.6.4.7 Review of all SYSTEM Variables Name of SYSTEM Variable Action SYSDAFO SYSDIAG SYSNR SYSNSYS SYSUS SYSVER Change date format On/off control for DIAG messages PS number, same as SYSNUS ("read only") System number PS number Version number 2.6.4.
Point parameter access in COLBAS is programmed using the general syntax: @ADDRESS.PARAMETER This method allows direct or indirect parameter access. Direct Addressing "Direct" in this case means that the relative point address follows after the "@" address designator. Technical Address (with "$") or User Address may be used. Examples 100 200 300 400 Assume a measurement point with address $1'000 or C7K8'01"ME.
2.6.6 COLBAS Access to Statistics Each statistics message is made up of various elements. A part of these elements is always present in every message (e.g. actual time or point address) the rest depends mainly on the point or message type. A COLBAS Task can access the Statistics Register through pre-defined variable, STA. This variable has some specific attributes.
Explanation: The above program searches the Statistics Register STA for point messages (defined by MTYP=0) related to address $177'020, covering the last two days and prints the various messages found. Remarks: Variable STA together with an attribute is to be regarded as a "normal" variable. However, it cannot be used in an INPUT statement but can only be read or printed with a PRINT statement. 2.6.
If the contents of an error message is insufficient for finding an error it is advisable to insert "break points" at critical points in the relative program in order to check variables of interest. This is done by writing a STOP statement at a suitable point in the Task. Whenever STOP is reached the program will halt. Now, in IMMEDIATE MODE any current variable value can be listed with instruction LIST VAR or other operations can be started.
2.7 CMB Circular Message Buffer 2.7.1 Initial Access and Handling Function call-up CTRL/P CMB General The circular message buffer is a reserved hard disk memory area of the VISONIK DCS. As opposed to the Statistic Register, ALL SPONTANEOUS MESSAGES from the VISONIK system are fed to the CMB before they are processed internally (e.g. output to a printer, deposited in Statistic Register, etc.). Post Box The circular message buffer can be compared to a post box.
T8 09:07:55 Function=PNT : CMB Operation=LIST : from 09.08.1996/Fr 02:13: -1Mon upto 12.08.1996/Mo 09:11: ? 12.08.1996/Mo 09:11=(dd.mm.yyyy) (hh:mm), (hh:mm), (dd.mm.yyyy), += (-100..100)(Min.,Hour,Day,Mnth), -=( 100..100)(Min.,Hour,Day,Mnth), (-100..100) (Min.,Hour,Day,Mnth), (-100..100), -(Mo,Tu,We,Th,Fr,Sa,Su), (Mo,Tu,We,Th,Fr,Sa, Su), -* , * , . : 12:05 12.08.1996/Mo 12:05 Message Category=ADDR: ? 0 * = All Messages 1 .
Message Type=PNT&PCH&Ackn&SLV&REST: ? 0 PNT = Point Messages 1 PCH = Param. Changes 2 Ackn = ACKN Messages 3 SLV = Statistic Slaves 4 CB = COLBAS Messages 5 REST = All other Mess. Message Type=PNT&PCH&Ackn&SLV&REST: CMB 09:51:10 Start of D A T A - L I S T 12.08.1996/Mo T8 from: 09.08.1996/Fr 03:44 upto: 12.08.1996/Mo 09:50 Message Category = Messages with Point Addresses Selected Address Range = $d100'PS Message Type = PNT&PCH&Ackn&SLV&REST (Oldest Entry : 09.08.
(-100..100) If a positive or negative (-) number is entered without units the system then automatically calculates in days. (.) (*) (-*) Present time Time interval ending at the maximum possible time of 31-Dec-2027 22:53. Time interval starting from the past possible time of 01-Jan-00/Su at 00:00 Examples Input: ) Hour, O Day or 0 Mnth Input of 0 Hour, 0 Day, or 0 Mnth. If a zero is entered together with a unit (e.g.
=== 12.08.1996 09:20:01 63.5 Deg. C ERSTA=?SST === 12.08.1996 09:20:01 CMB 10:02:55 End of D A T A - L I S T 12.08.1996/Mo- 2.7.2.2 Message Category With "Message Category" a further condition for selection of buffer messages may be specified. The system lists messages according to the following categories: Message Category=ADDR: ? 0 * = All Messages 1 .
SYSM Messages from other systems: If two or more VISONIK systems are linked together (by Ring, Telephone or V.24), messages can be exchanged between the systems. Such messages are transferred to partners in the language of the sending message channel and buffered accordingly in the destination's CMB.By using search text, messages with specific contents can be called. "Txt.Search=*" "Txt.Search=H'*" "Txt.Search=*" lists messages from partner systems. "Txt.Search=H'*" lists messages from partner 'H'.
2.7.3 LDAT, Review of Messages by Date Operation LDAT provides a review of the number of messages in the circular buffer. The subtotals are arranged according to date and a grand total is given at the end of the summary. Special Features: The CMB can also store data blocks specific to output devices and programs. Such entries cannot be directly accessed by a user but are summarised at the end of a "LDAT" listing.
2.7.4 LFCO, Fault Condition Summary Operation LFCO provides a listing on the user's terminal or printer which gives a review of 'fault condition' messages held in the CMB. These messages are tabulated together with the current warning condition (WCON) state marker, related address (ADDR, TA) and the number of related fault condition states (Normal: FCON=0, Fault: FCON=1) during the specified interval, listed in a table.
T8 10:58:23 Function=PNT : CMB Operation=LIST : LIRO Address=RO'OM'TEMP"01: ctrl/h Message Type=PNT&PCH&Ackn&SLV&REST: ? 0 PNT = Point Messages 1 PCH = Parameter Changes 2 Ackn = ACKN Messages 3 SLV = Statistic Slaves 4 CB = COLBAS Messages 5 REST = All Other Messages Message Category=ADDR: Address=RO'OM'TEMP"01: * Message Type=PNT&PCH&Ackn&SLV&REST: Recorded Date : 12.08.1996/Mo + AI 10:56:21 RO'OM'TEMP"01 Training Departement ALsta=Alarm 12.08.
2.7.6 LOCT, List Message Buffer in Octal Operation LOCT provides an octal code listing of messages held in the CMB. As in Operation LIST messages may also be selected according to Time Interval or Message Category. Operation LOCT is mainly for diagnostic purposes. T8 11:43:23 Function=PNT : CMB Operation=LIST : LOCT from 09.08.1996/Fr 06:17: -1 11.08.1996/Su 00:00 upto 12.08.1996/Mo 11:43: 12.08.
The system also stops the output of messages whose Message Priority MSGP is equal to, or less than that specified by the user. VISONIK deletes messages in 'Others' category irrespective of the entered Message Priority (MSGP). The following example illustrates that for Message Channel 1, there are, 123 messages with MSGP=0 No messages with MSGP=1 45 messages with MSGP=2 32 messages with MSGP=3 1 "Other" message By specifying "Message Channel=1" and "MSGP=3" a message flood to terminal T1 is stopped.
CM2U8567E / 04.
2.8 COS Dialogue for VISONIK Insight 2.8.1 Summary This chapter contains information on: • Picture management in the DCS. • Management of dynamic channels in the DCS • Assignment of pictures to address ranges The "UNIGYR VISONIK Insight" describes the entire functionality of the PC software. 2.8.2 Procedure "UNIGYR VISONIK Insight" is a PC software package. A PC running with 'Insight' is incorporated as a peripheral unit to a VISONIK Communication Server.
2.8.4 UTIL, Picture Management This provides the means for management and documentation of pictures. T8 13:51:10 Function=PNT : COS Dialogue Range=UTIL : Operation=DIR : ? 0 DIR = List COS Picture Directory 1 EDI = Edit COS Picture Directory 2 COPY = Copy one COS Picture to another 3 DEL = Delete COS Picture 4 VE = Verify COS Pictures Operation=DIR : Note: Operation VE is identical to Function VE,COS. 2.8.4.
B.Length Net length (bytes) required for picture program code not including channel entries. Free Memory space available for picture extension or further channel entries. Memory demands for a picture compete with those for channel entries. Version Picture version number. This number indicates the status of the internal picture revision and is used for diagnostic purposes. Level See OPERATION EDI Status See OPERATION EDI Entry EntrTime Date of last change. Time of last picture change.
2.8.4.3 UTIL,COPY, Copy Picture This enables copying of pictures within the system disk, i.e. duplication or saving. Only one picture may be copied per operation. Any defined dynamic channels are also copied. from Pict.No [a picture number in the range (1..max)] specifies the picture to be saved. to Pict.No. [a picture number in the range (1..max)] destination picture number.
2.8.5 ACT, Active Channel Dialogue By defining active channels a "live" up-to-date relationship between an Insight or COS picture and VISONIK system data points or process is established. T8 14:17:02 Function=PNT : COS Dialogue Range=UTIL : ACT Operation=CH : ? 0 CH = Change Data Entry 1 LI = List Data Registers 2 DEL = Delete Register Entry(ies) Operation=CH : 2.8.5.1 ACT,CH, Enter or Change Active Channels. The extensive dialogue COS,ACT,CH can be split into three sections.
Act.Type [Point..OperName] Active Point Type. This explains what should be updated and how.
Second Dialogue Section: Active Point Type "Macro - Start Macrotexts (TXCM)" This allows for running any macro from the macro library 'TXCM' of the DCS. Text No. [0..340] Input any required legal macro number. Colour [Black..LghtGrey, No Change, Transparent] This allows colour selection, from the 18 possibilities, for the object which the active channel represents. No change: The object colour(s) from the Insight Picture Editor are accepted. Transparent: The object is invisible.
Second Dialogue Section: Active Point Type "OperName - Name and Level of Operators" Show operator's name. This enable the currently logged on operator's name together with access level for Functions and parameters to be displayed. Colour [Black..LghtGrey, No Change, Transparent] This allows colour selection, from the 18 possibilities, for the object which the active channel represents. No change: The object colour(s) from the Insight Picture Editor are accepted. Transparent: Not meaningful for OperName.
Act.Form Start of Bar (for 'Bar' only) End of Bar (for 'Bar' only) Colour (for 'Bar only) Flashing Start Range (not for 'Bar') [Colour..Val.Only] Active Channel Mode. Colour Display value in colour. – Foreground colour for active text, - Fore and/or background for Object (Insight) – Background for rectangles (COS) Symbol (For 'Point' only). Display value with symbols. The actively updated value corresponds to a symbol from the symbol library.
Explanation One COS,ACT entry has space for a maximum of 5 possible parameter states. But, certain parameters can have up to 20 discrete states (values). Therefore, an entered parameter value is taken as the START of a parameter value range. This range then includes the following sequential possible parameter values up to the next specified "Start Range", or to the last value which the relative parameter can have. All parameter values within a range take the attributes of their respective start value.
Input possibilities + Move forwards to next parameter value or to the next start range. '+' at the fifth range or at the last parameter value causes a jump to the prompt for "Textlnth". Textlnth Text Type Siemens Building Technologies Landis & Staefa Division - Move backwards to previous parameter value or to the previous start range. '-' at the first range or first parameter value causes a jump to the prompt for "Textlnth". ^K Clear start range entry. (To make place for another start range).
Example: with parameter text: ME=21.3 Deg.C Example with extra text: 21.3 Deg.C Outside temperature Text [RightMar., Left Mar.] Display of actively updated text. RightMar. Arrange text - right justified. The units of a parameter and/or any extra text are written at the right hand margin of 'Textlnth'. Right justified displays are suitable for displaying tables. WCON|<---- Textlnth ---->| | | *** |FAULT | |ST= FAULT | |ME= 1000 DEG. C |EXTRA TEXT | |cut off. |ME= 1209.25 DEG. C | +++ |ME= 1.
Long Name [NO/YES] This prompt only appears if "withName" has been answered with 'YES'. The actively updated parameter's name shall be displayed in long format together with the associated parameter value. This extends the number of characters required for the parameter to be updated and must be taken into account when defining 'TextLnth'. The same examples as above with long names: 0 ME/Measurement value= 16.4 Deg.C 0 3 PS/Position command= 45 percent TASK/COLBAS Task No.= 10 POOL/COLBAS Pool No.
Pict.No.= 1 Pict.No.= 1 Pict.No.= 1 Pict.No.= 1 Pict.No.= 1 Chan.No. = 1 Act.Type = Point Par.Name = SC with WCON= NO TextLnth = 62 Act.Form = Colour SC 0..... SC 1..... SC 2..... SC 3..... ChanType= Addr.Des= Address = Text = withName= ExtraTer= Colour = Colour = Colour = Colour = Chan.No. = 2 Act.Type = CB Pool TextLnth = 0 Act.Form = Bar Start of Bar End of Bar POOL ChanType=Fix I/O Pool No.= 100 withName= NO ExtraTer= NO POOL 0 POOL 1000 Colour = Yellow Cursor P= Down Chan.No. Act.
2.8.6 PICT, Allocation of Pictures to Address Ranges A picture register is necessary whenever the following functions are used: – Ctrl/D (for COS) – Picture select - Address in Insight, Such a register forms the link between partial addresses of a building, area or plant and the associated picture, i.e. the picture register contains all picture numbers together with their reference addresses or reference address masks.
Change Picture Number VISONIK accepts only one picture number per address/address mask. Picture numbers can be changed by entering the address or address mask involved. Tha system now gives a response showing the picture number associated with the entered address or address mask. This picture number can now be changed: A successful entry in the picture register is confirmed with “ok!”. 2.8.6.
2.8.6.4 PICT,DEL, delete Picture Entries This allows picture entries to be deleted either according to address or picture number. Operation=CH: DEL Delete Mode=Address : ? 0 Address =Search Criterion is an Address 1 Pict.No. =Search Criterion is a Pict.No. Delete Mode=Address: Delete Mode=Address Explanation Pictures are deleted according to address.
CM2U8567E / 04.
2.9 DATE Set Date and Time For various Functions (e.g. TRR, DRR, MXD, etc.) to work correctly, VISONIK requires to know the actual time, date and day. If the system time is undefined then anywhere throughout the whole VISONIK system where time is displayed (outputs), two question marks are given in place of hours (e.g.: ??:34:27). But the printed minutes and hours do not agree with the correct time. Function DATE is used to manually set up the date, time and day through a VISONIK system.
Parameter BKPS Parameter BKPS acts as a "switch", i.e.: BKPS=No On start-up, the Server takes the last time saved on its hard disk as the system time. BKPS=Yes The Server takes the first valid time from any suitable system partner. (It does not take the time from any defined process station, e.g. BKPS=6 means the time from PS $6). MASTER Clock Function MASTER clock function means the system time is synchronised to the clock of a process station (declared as MASTER clock PS, see parameter MCPS).
Date On entering a new date the Server will accept various formats provided the input is unambiguous. The associated day is automatically set by the Server after this answer is terminated with . Date =3-1-96/We: 3-Jan 3-Jan-1996 3-1-96 3.1.
CM2U8567E / 04.
2.10 DPC Data Processing Communication DPO, DPP, DPC The name DATA PROCESSING refers to a VISONIK software package which allows the following functions: • Data collection and storing • Data presentation (using tables and graphs) There are three main Functions associated with DATA PROCESSING: • DPO Data Processing Operations • DPC Data Processing Communication • DPP Data Processing Presentation These main functions display to some degree the same fundamental structure.
T8 13:33:16 Function=PNT : dpc Operation=EXP : Export Format=ASCII2 : Address Mask=$d100'041: $d100'041 Recording Type=INST : Parameter Name=RDO : Interval=I05m : I05 Buffer Type=LIN : CIRC Buffer Type=CIRC : Buffer Type=CIRC : ? 0 * = All (DEL,LDAT) 1 LIN = Fixed (Linear) 2 CIRC = Rollover (Circ.) Buffer Type=CIRC : 2 Buffer Type=CIRC : CIRC Buffer Type=CIRC : LIN Rounding Setting for Par.Values=-1: from 19.07.1996/Fr 10:00: 19.07.1996/Fr 10:00 upto 21.07.1996/Su 18:05: 21.07.1996/Su 18:05 V4.
2.11 DPO Data Processing Operations DPO, DPP, DAPC The name DATA PROCESSING refers to a VISONIK DCS software package which allows the following functions: • Data collection and storing • Data transfer (e.g. to PCs) • Data presentation (using tables and graphs) There are three main Functions associated with DATA PROCESSING: • DPO Data Processing Operations • DPC Data Processing Communication • DPP Data Processing Presentation These main functions have, to a large extent, the same basic structure.
2.11.2 GEN, Generate Value Log Operation GEN is used to generate a DP Value Log. A Value Log can only be generated if the related point exists in the process image. A DP Value Log is dimensioned automatically by VISONIK DCS based on the responses as requested in the dialogue procedure. Starting and stopping data logging VISONIK DCS automatically starts to record data immediately after a Value Log has been generated. No special start or stop instructions are necessary for the processing of data.
Note Example for Generating a DP Value Log Before starting generation make sure that the involved point's parameter OPMO is not set to either PSe or PSfe. ctrl/P T8 19:18:45 Function=PNT : DPO Operation=LI : GEN Memory: total / free 148 / 148 Value Segments 99900 MOM 27232 eMIT Address=$d100'PS : $100'040 Recording Type=INST : INST Parameter Name=RDO : RDO Interval=I60m : I05 Buffer Type=CIRC : CIRD Flag=. : How long ..=56Hour : 70Hour 19:20:03 Generation running ... Please wait ! 19:20:03 ...
2.11.2.
2.11.2.4 Logging Interval Any logging interval is accepted for instantaneous values, but only intervals of 1 hour and 24 hours are permitted for mean values. Interval=I01m: 0 * 1 I01m 2 I05m 3 I10m 4 I30m 5 I60m 6 I24h Interval=I01m: = = = = = = = ? All (LI and DEL only) 1 min Interval 5 min Interval 10 min Interval 30 min Interval 1 hr Interval 24 hr Interval * 2.11.2.
Example Example for a flag value as a quality attribute on listing the values: 25.6 ,NEv) 1 | ----> flag value 1 Application: – For flagging a room temperature value during occupancy times. – For flagging a flow temperature measurement while the circulating pump is running. 2.11.2.7 Acquisition time This is where the acquisition time is entered in hours, days, or months. How long ..=53Hrs : ? How long ..=(1..255)(Hrs,Day,Mon): 50Std 2.11.
In the preceding example, inputs of Address mask "$*" and a "*" operator against the following dialogue prompts: All Generated DP Value Logs All Recording types All Values with parameter name ME All Logging intervals All buffer types (since version 16, only the buffer type ZIRK can be generated!), will delete all entries for ME Points $4'020. For deleting addresses, VISONIK DCS prompts for "Address mask=.
Address mask Operation DIR accepts address masks. To list all addresses there are two possible user inputs to the VISONIK DCS prompt for "Address Mask=.
2.11.5.1 TFRM, Tabular Format Example of a TFRM Tabular Format Listing T8 12:24:10 Function=PNT : DPO Operation=LI : LI Display Format=TFRM : ? 0 TFRM = List Data in Tabular Format 1 LFRM = List Data in Long Format Display Format=TFRM : TFRM 1. Series --------Address=. : $100'041 # Address Flag PAR TYP INT ORG from upto ----------------------------------------------------------------1 $d100'041 INST I60m CIRC 20.06.1996 28 Day $d100'041 RDO 12:00 >>o.k.! 2. Series --------Address=.
2.11.5.2 LFRM Long Format Example Listing in Long Format, LFRM T8 12:39:30 Function=PNT : DPO Operation=LI : LI Display Format=TFRM : ? 0 TFRM = List Data in Tabular Format 1 LFRM = List Data in Long Format Display Format=TFRM : LFRM Address Mask=$d100'041: $100'040 $d100'040 # Address Flag PAR TYP INT ORG from upto ----------------------------------------------------------------1 $d100'040 INST I05m ZIRK 17.07.1996 53 Hour $d100'040 RDO 19:00 >>o.k.! Rounding Setting for Par.
INFO text Under the address (TA, UA) the information text as entered in point parameter TXI or TXI2 is printed. Rounding off parameter values: 4..7 This allows fixing the decimal point by entering the number of digits before or after the point i.e. the value is rounded up or down to the number of decimal places defined. • A negative entry determines the number of places after the point • A positive entry defines the number of places before the point.
2.11.6 MOD, Modify Data Application: In recording values for statistics it may be that certain individual scattered values lie well outside tolerance levels (caused by external influences, for example, by sensors) These can completely distort the relative statistics (e.g. in a daily log). Using Operation MOD it is possible to align such values to the other recorded values. Important A modified value is flagged in the validity marker with "Hnd".
After modifying a value, the value can be listed with Operation LI. FZ T8 14:47:11 Function=PNT : DPO Operation=LI : LI Dis10 play Format=TFRM : 1 Address Mask=$d100'040: $d100'040 # Address Flag PAR TYP INT ORG from upto -----------------------------------------------------------------1 $d100'040 INST I60m CIRC 20.06.1996 28 Day $d100'040 RDO 15:00 >>o.k.! Rounding Setting for Par.Values=-1: from 20.06.1996/Th 15:00: 20.06.1996/Th 15:00 upto 18.07.1996/Th 15:00: 18.07.
2.11.7 SERV, Select Service Function This information is for internal use only; for analysis, more system information is needed. Short profile summary T8 15:11:10 Function=PNT : DPO Operation=LI : SERV Function=SDIR : ? 0 SDIR = Short Layout Summary 1 LDIR = Long Layout Summary 2 RACT = Reactivate Value Log 3 TRC1 = Enable Profile Trace 4 TRC0 = Disable Profile Trace Function=SDIR : Address Mask=$d100'040: $d100'040 DM-SEGMENT 0004 0032/ $d100'040 RDO INST CIRC I60m 20.06.
2.11.9 Validity Marker Every stored value is complemented with a 'Validity Marker'. Upon listing in tabular format, Validity Markers are shown as hexadecimal numbers enclosed in brackets and in long format as an abbreviation with three letters. Tabular Format -------------22.8 (94) ! Long Format ----------22.8 (?HW) 0 Validity Marker Structure Validity Markers are dimensioned with 8 bits (1 Byte).
B4 --> Evt (No Event) B4 --> NEv If a parameter status change occurs (Event) within a logging interval, the 'Validity Marker' is recalculated. The relative NEv marker for No Event is reset to "0" and the message "Evt" is output. If there is no event in the respective interval the marker remains at "1" and message "NEv" is given. B5 --> OSV (OSV Out of Service) This marker appears if parameter OSV for the related point has been set to YES.
Example of instantaneous Value (Interval = 1 Minute) TIME: | -1| ----------------------------------16-Feb-90 08:00| 22.8 ( 11) | 08:01| 22.8 ( 11) | 08:02| 22.8 ( 11) | 08:03| 23.0 ( 0) | 08:04| 23.0 ( 11) | 08:05| 23.0 ( 11) | 08:06| 23.0 ( 11) | 08:07| 23.2 ( 0) | --> --> --> --> --> --> --> --> No-Event No-Event No-Event Event No-Event No-Event No-Event Event If more than one Event occurs within a 1 minute interval only the Validity Marker associated with the last Event is stored.
CM2U8567E / 04.
2.12 DPP Data Processing Presentation DPO, DPP, DAPC The name DATA PROCESSING refers to a VISONIK DCS software package which allows the following functions: • Data collection and storing • Data transfer (e.g. to PCs) • Data presentation (using tables and graphs) There are three main Functions associated with DATA PROCESSING: • DPO Data Processing Operations • DPC Data Processing Communication • DPP Data Processing Presentation These main functions have, to a large extent, the same basic structure.
Max. 6 colours The software involved provides six-colour graphs. One graph printout takes up the space of an A4 page. Simultaneous graphs Simultaneous output of several graphs to different terminals in a VISONIK Server is not possible. They are automatically queued in VISONIK and output in a called sequence. Processing time The processing time for a graph is approx. 30 seconds to 5 minutes. 2.12.3 LDAT, List Data Numerically TFRM LFRM Tabular format Long format START of DATA-LIST 1.$4'020 2.
2.12.3.1 TFRM, Tabular Format Example of listing in the TAB tabular format T8 15:48:32 Function=PNT : DPP Operation=LDAT : Display Format=TFRM : ? 0 TFRM = List Data in Tabular Format 1 LFRM = List Data in Long Format Display Format=TFRM : 1. Series --------Address=. : $100'040 # Address Flag PAR TYP INT ORG from upto -----------------------------------------------------------------1 $d100'040 INST I60m CIRC 20.06.1996 28 Day $d100'040 RDO 16:00 >>o.k.! 2. Series --------Address=.
2.12.3.2 LFRM Long Format Example for listing in long format SFRM T8 08:19:26 Function=PNT : DPP Operation=GCH : LDAT Display Format=TFRM : ? 0 TFRM = List Data in Tabular Format 1 LFRM = List Data in Long Format Display Format=TFRM : LFRM Address=$d100'041 : # Address Flag PAR TYP INT ORG from upto -----------------------------------------------------------------1 $d100'041 INST I60m CIRC 21.06.1996 28 Day $d100'041 RDO 09:00 >>o.k.! Rounding Setting for Par.Values=-1: ? Rounding Setting for Par.
Address mask Unlike TAB format, address masks and "*" operator entries are accepted in Long Format, LFRM. This allows listing of logged values from specific, or all, DP Value Logs covering a certain time span. INFO text Under the address (TA, UA) the information text as entered in point parameter TXI or TXI2 appears. Rounding off parameter values: 4..7 This allows fixing the decimal point by entering the number of digits before or after the point i.e.
2.12.4 Validity Marker Every stored value is complemented with a 'Validity Marker'. Upon listing in tabular format, Validity Markers are shown as hexadecimal numbers enclosed in brackets and in a long format listing as an abbreviation with three letters. In long format only the worst condition is shown in each case. Tabular Format -------------22.8 (94) ! Long Format ----------22.8 (?HW) 0 Validity Marker Structure Validity Markers are dimensioned with 8 bits (1 Byte).
B4 --> Evt (No Event) If a parameter status change occurs (Event) within a logging interval, the 'Validity Marker' is recalculated. The relative NEv marker for No Event is reset to "0" and the message "Evt" is output. B4 --> NEv If there is no event in the respective interval the marker remains at "1" and message "NEv" is given. B5 --> OSV (OSV Out of Service) This marker appears if parameter OSV for the related point has been set to YES.
Example of Instantaneous Value (Interval = 1 Minute) TIME: | -1| ----------------------------------21-Feb-90 10:00| 21.7 ( 10) | 10:01| 21.8 ( 0) | 10:02| 21.8 ( 10) | 10:03| 21.8 ( 10) | 10:04| 21.7 ( 0) | 10:05| 21.8 ( 0) | 10:06| 21.8 ( 10) | 10:07| 21.8 ( 10) | 10:08| 21.8 ( 10) | 10:09| 21.8 ( 10) | 10:10| 21.
2.12.5 ADIR, Directory of Generated Addresses Operation ADIR provides a listing of information held in DP Value Logs by specifying a relative address or address mask. The directory output for Function DPO is identical to that of Function DPP.
2.12.6 GDIR, Contents of Graphic Layout Operation GDIR provides the facility for listing a directory of all generated graphic layouts. T5 09:20:00 Function=PNT : DPP Operation=GCH : GDIR Graph Number=* : * 1. Entry : 22.07.1996 Operator: Title : Bab Al-Omra West 2. Entry : 22.07.1996 Operator: Title : Bab Al-Omra East 3. Entry : 23.07.1996 Operator: Title : Bab Al-Omra North 6. Entry : 22.07.1996 Operator: Title : Bab Al-Fateh Operation=GCH : Graph number=* Graph nubmer=(2..
T5 09:20:00 Function=PNT : DPP Operation=GCH : GCH Range=Graph : ? 0 GRAF = Change Complete Graph 1 AXES = Change Axis System 2 CHAN = Change DP Channels 3 TEXT = Change Texts 2.12.7.1 GRAF, Change Whole Graphic Layout First, the required graphic number is selected (No. 1..128). On selecting GRAF, a pass is made through all layout sections (AXES, CHAN and TEXT). The individual layout sections are explained at the end of the next example.
Example for Generating a New Graphic Layout T8 11:00:24 Function=PNT : DPP Operation=GCH : Graph Number=1 : 1 Range=GRAF : GRAF Co-ordinate System -----------------Co-ordinate System=Default : ? Co-ordinate System=(Default,Slct'ble): SLCT'BLE Length of X-Axis [mm]=100: 150 Length of Y-Axis [mm]=100: 100 X Co-ordinate for Origin [mm]=35: 35 Y Co-ordinate for Origin [mm]=35: 25 Scaling of the Axes ------------------X-Axis .. Minimum=19.07.1996 11:02: -3Std : 1E+30 Units per cm.=10 : ? : 1E+30 Y-Axis ..
Channel(Data Processing) ---------------------------Chan.No.=. : 1 Address=$d100'040 : $100'041 # Address Flag PAR TYP INT ORG from upto -----------------------------------------------------------------$d100'041 INST I05m CIRC 19.07.1996 56 Hour $d100'041 RDO 10:00 2 $d100'041 INST I60m CIRC 21.06.1996 28 Day $d100'041 RDO 12:00 Entry=1 : >>o.k.! Chan.No. = 1. Format = Even Symbol = Address = $d100'041 Par.Name = RDO Log Type = INST Interval = I05m Buffer = CIRC Colour = Black Pattern = 0 = (...............
y Coordinates 100 [mm] (50..150) 35 [mm] Origin (0..50) x 100 [mm] 35 [mm] (50..200) (0..50) 9370Z08E Axes Scaling in User Units A temperature measurement (in the "Y" axis) can be represented in an X,Y co-ordinate system as a function of time ("X" axis). Several measurements made at distinct time intervals and entered in the co-ordinate system will produce a temperature curve. Example In the following dialogue the co-ordinate system is scaled and lettered in user units.
Relative time units X-Axis At the prompt "Minimum" it is possible to set either absolute or relative time units not only for the x axis, but also for the y-axis. For relative time units, an absolute point in time is calculated upon the output of the graphic (GRAF,PLOT) that is taken relative to the current time. .. Minimum=19.07.1996 14:36: ? (-100..-1) (Min.,Hour,Day) (dd.mm.yyyy) (hh:mm) (dd.mm.yyyy) (hh:mm) (-1E+30..1E+30): Units per cm.=10 : ? (1..100)(Min.,Hour,Day) (.001..
9370Z10E Y axis Scaling the y-axis 17.5 2.5 units/cm 12.5 Minimum (origin) Scaling of the Axes ------------------X-Axis .. 10 Minimum=19.07.1996 14:50: 3 Units per cm.=10 : 10 Y-Axis .. Minimum=0 : 10 Units per cm.=10 : The Y-axis is scaled to suit the relative measured value's magnitude. The user must define a minimum value for the graph's origin using the given measurement value's range. At the prompt for "Minimum" it is possible to set either absolute or relative units for both the x and y axes. 2.
DP Channel (Data Processing) ---------------------------Chan.No.=.: 3 Chan.No. = 3. OUTSIDE TEMP Address = AA1'ME Log Type = INST Interval = I05m Colour = Black Mult. Factor = 1 Option=CHCH: 0 DECH = 1 CHCH = 2 DEVPCH = 3 GPCH = Format Par.Name Buffer Pattern Offset = = = = Even Symbol = ME CIRC 0 = (................) = 0 ? Delete Complete Channel Change Complete Channel Change DP Parameter only Change Graphic Parameter only By entering a period = full stop (".") at Channel No.=.
Enter entry number At this point a prompt for an "Entry number" appears. By entering the required number all the DP parameters specific to that entry are fetched and then, when in dialogue DEVPCH, are saved in the relative graph entry. In option CHCH saving of the complete channel in the graph entry is only made after entering the graphics parameters. As a check, the entry related to the specified number is listed once again. Chan.No. = 1.
Format=Even : 0 Symbol 1 Stepped 2 Even 3 Bar 4 Pos.Sawt 5 Neg.
Symbol=*: ? Character : SPACE ! " $ % & ' ( ) * + , - . / @ : ; < = > Capital Letters : A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Numbers : 0 1 2 3 4 5 6 7 8 9 Symbol=*: Dot pattern=0 Dot Pattern=0: 0 = 1 = 2 = 3 = 4 = 5 = 6 = 7 = 8 = Dot Pattern=0: Mult.Factor=1 The list of dot patterns is the same as for Trend Plot: ? (................) (. . . . . . . . ) (........ ) (.... .... ) (.. .. .. .. ) (.. .. ) (.... .. .... .. ) (.. . .. . ) (. . . .
Shading Pattern=0: 0 = 1 = 2 = 3 = 4 = 5 = 6 = 7 = 8 = Shading Pattern=0: ? Light Shading Mid-tone Shading Dark Shading Horizontal Stripes Vertical Stripes Stripes with Pos. Gradient Stripes with Neg. Gradient Horizont. Herringbone Vert. Herringbone 0 1 2 3 4 5 6 7 8 0 1 2 3 4 5 6 7 8 = = = = = = = = = 9370Z12E Shading Pattern= 2: ? Light Shading Mid-tone Shading Dark Shading Horizontal Stripes Vertical Stripes Stripes with Pos. Gradient Stripes with Neg.
Option=TICH: 0 TICH = 1 AXCH = 2 ATCH = Option=TICH: ? Change Title Change Axis Text Change Addit. Text Option=TICH The title can be centred or left justified. • For the selection (Position=centre) the title appears centred over the co-ordinate system • For (Position=left jus.)the title appears left justified over the co-ordinate system. There is a maximum of 32 characters per text. Option=TICH : Title ----Title : WEST WING OFFICES Position=Centred : ? Position=(Centred ,L.
Option=ATCH Additional text (32 characters) can be placed anywhere in the co-ordinate system. Texts are numbered from 1..10 and can be deleted or changed at will. Option=TICH : ATCH Text ---Number=. : ? Number=(1..10), . : 1 1.Text : Information 1 Directn.=Horiz. : ? Directn.=(Horiz.,Vertical): Position=Centred : ? Position=(Centred,L.Justfd): X-Coordinate[mm]=0 : X-Coordinate[mm]=0 : 25 Y-Coordinate[mm]=0 : 100 Entry in Graph Number=.
Example Listing in LONG Mode T5 10:11:17 Function=PNT : DPP Operation=GCH : GLI List Mode=LONG: Graph Number=1: ----------------------------------------------------------------------------1.
2.12.9 GDEL, Delete Graphic Layout Under Operation GDEL the following actions are open to the User: T8 15:18:56 Function=PNT : DPP Operation=GCH : GDEL Range=GRAF : ? 0 GRAF = Delete Complete Graph 1 CHAN = Delete DP Channels 2 TEXT = Delete Text Range=GRAF : Example for Deleting a Complete Graph T8 15:10:33 Function=PNT : DPP Operation=GCH : GDEL Range=GRAF : ? 0 GRAF = Delete Complete Graph 1 CHAN = Delete DP Channels 2 TEXT = Delete Text Range=GRAF : Graph Number=* : 4 Accept Every Entry=Yes : Y 4.
After entering a graph number a specific DP channel may be selected or exit from dialogue with ("."). If a specific DP channel is chosen it is first printed out then the system requests acknowledgment of "Delete Entry" before deletion. The same procedure applies to section TEXT. Example for Deleting an Axis Text Entry Range=GRAF: TEXT Graph Number=5: Option=TICH: AXCH X-Axis : TIME (HOUR,MIN) Position = Centred (15 char.
Output of several graphs simultaneously When two or more graphs are simultaneously requested on different terminals using DPP,PLOT or RPT,DPR,GRAF a delayed graph output is given the message "Bitmap busy! Please wait" T5 10:17:04 Function=PNT : DPP Operation=GCH : PL Graph Number=10: Output Device=$TT: Bitmap busy! Please wait. The delayed graphs are transferred to a queue (see DPP,JOBS).
Notes on Associated Report DPR 11:11:08 5: 18-Feb-90 11:11 After the report start line a line is printed showing the relative graph number, date and time. A table then follows containing the DP channels which have been plotted in the graph. R E P O R T - S T A R T 18-Feb-90/So (T8) T5 NAME PAR TYPE INT * Format SY Dot ---------------------------------------------------------------------------3 A01'H1'MW"0401 ME INST I30m 1 Even * 0 4 A01'H1'MW"0401 ME INST I05m 1 Symbol .
2.12.11.1 JOBS, Initialise Bitmap When a graphic DP report is requested with RPT,DPR,GRAF or DPP,PLOT the entry is placed in a queue with up to five "Jobs". T5 10:18:41 Function=PNT : DPP Operation=GCH : JOBS Bitmap Status : Busy Job in Progress Last Job No. Next Job No.
2.12.12 Output Terminal Configuration The terminal involved must have full graphics capability. This covers printers, video terminals or PCs with 'Terminal emulation'.
The following list shows the currently supported terminals and the possible (and recommended) graphic modes: Device GraphicMode(s) GRMO recommended LA12 LA50 LA75 LA100 SIXEL SIXEL SIXEL SIXEL SIXEL SIXEL SIXEL SIXEL Visual 603 SIXEL Tektr. 4014 SIXEL VT240 b/w REGIS Tektr. 4014 SIXEL REGIS (R4) 4 grey levels REGIS Tektr. 4014 SIXEL REGIS (R4) 4 colours REGIS Tektr. 4014 SIXEL REGIS (R16) 16 colours VT241 col VT340 col DPL24 E8 E24 E24Q E8 * E24 24 dot printer Epson Emul.
CM2U8567E / 04.1999 2-124 VISONIK DCS Functions and System Messages VVS18 Funktion ...
2.13 DRR Date/Time Reaction Register 2.13.1 Initial Access and Handling Function call-up CTRL/P DRR General A general introduction to the subject of VISONIK reactions can be found under "Reactions in General" in section R of this manual. The process reaction DRR is one of six reaction types provided by the VISONIK DCS. The reaction types are named after the "reason" that is to activate the reaction in each case.
Example: Date/Time Reaction Register entry T8 09:54:55 Function=PNT : DRR Operation =CH : Start Date =24.07.1996: ? Start Date =(dd.mm.yyyy): Entry =1 : ? Entry =(1..255): 1 Start Time =09:55 : 10:00 End Date =24.07.1996: 25.07.1996 End Time =23:59 : 23:58 Period =1Hour : ? Period =(1..255)(Min.,Hour,Day,Mnth), (1..255): 3 Period =3Hour Blocking Flag=.
2.13.2 CH, Enter/Change Data 2.13.2.1 Changing an existing DRR entry In order to change data in a reaction entry it must first be selected via its "reason" and entry number. If the entry exists, it is listed completely for checking at the operating terminal. The edit mode then becomes active, so that the user can modify or confirm each part of the reaction entry step by step. Important: A reaction entry is not changed (and re-saved) in the system until every step of this dialogue has been completed, i.e.
Start of DRR 9370Z16E Time span, in which the Reactions should take place End of DRR Start date, start time End date, end time 1st. period Last period time First DRR Variation 2 Second DRR Last DRR Delete message only appears if the entry is manually deleted The reaction should be executed: • starting from a specific date • over a specified period • with a specified number of repetitions. This requires the following entries: Start date / time Beginning of the first reaction Stop date ".
Variation 3 The reaction should be executed: • starting from a specific date • over a specified period, repeatable as desired. The last reaction is undefined (How often = endlessly). The reaction is executed until it is manually stopped. This requires the following entries: Start date / time Beginning of the first reaction Stop date ".
In the above example, the reaction entry is executed only if the "reason" is fulfilled and flag $F10 has the value 1,Step or 2,Step at that time. In all other cases the reaction entry is blocked, and the reaction is not executed. Definition of the reaction to be executed The following reactions can be triggered via a date / time reaction register entry: Reaction UA/TA CT MC SLVM CB .
Reaction MC Macrotext number Language Output device When the reaction is triggered, the VISONIK-DCS executes a specific macro command from the macro text register (TXCM,M) ??? of the selected language at ONE defined device. ??? Number of the macro text. Language of the macro text register. Output device (STA, M1..M15) at which the text is to be printed. Reaction SLVM Print slave messages.
1. further address The VISONIK DCS executes the same reaction with the further addresses as with the address defined under "Reaction =". This feature allows for reaction entries to be economised. n. further address The user can assign up to four different further addresses to each reaction entry, provided the reaction is one that modifies point parameters (Reaction =UA/TA) or prints slave messages (Reaction =SLV).
T8 10:29:08 Function=PNT : DRR Operation =CH : LI Start Date =* : ? Start Date =* , (dd.mm.yyyy)..(dd.mm.yyyy), (dd.mm.yyyy): * Entry =* : ? Entry =* , (1..255): * Reaction =.. : ? UA/TA = Change Point Parameter CT = Printout Cleartext MC = Issue MACRO Command SLVM = Output Slave Message CB = Start/Stop COLBAS Task . = No Reaction (for MRR & GRR) PICT = Auto Picture/Point Selection Reaction =.. : DRR 10:29:45 Start of D A T A 24.07.
2.13.4 DEL, Delete Register Entry(ies) The DEL operation can be used to selectively delete reaction entries. The entries to be deleted can be filtered according to the following criteria: • by start date • by entry numbers • by reactions If the reaction type CT, MC or CB is entered at the prompt "Reaction=?:", the user can make a finer selection according to text or task number. T8 14:03:53 Function=PNT : DRR Operation =CH : DEL Start Date =* : Entry =* : Reaction =.. : .. Accept Every Entry=Yes : Yes 14.
T8 14:46:35 Function=PNT : DRR Operation =CH : LSTA Register Total Entries -------------------------------------------------Group Reactions GRR 1 Process Reactions PRR 1 Maintenance Reactions MRR 1 Time Reactions TRR 1 Date Reactions DRR 1 Total 5 Operation =LSTA : 2.13.6 LOCT, List Reaction Entries in Octal The LOCT operation can be used to selectively list the reaction entries according to the same criteria as the LI operation. The normal list is followed by a printout of the same data in octal code.
2.13.7 Special Features Next Date Reaction After every Date Reaction, VISONIK automatically calculates the time of the next Reaction based on the period as defined in the relative Reaction entry and updates the Reaction Register. Such a calculation can be seen in any listing of a Date Reaction entry where it is printed in brackets alongside the specified data, i.e. when the next Date Reaction will take place or how often the Reaction will be executed.
2.14 DSS Dialogue with Process Station Function DSS allows direct dialogue between centralised VISONIK terminals and remote PRV/BPS/EKL Controllers in the process stations. DSS means "Dialogue with Process Station". Process stations in a VISONIK DCS system which are fitted with PRV/BPS and EKL-X Controllers can be contacted through function DSS as though the dialogue terminal were connected through the local PRV/BPS/EKL interface.
2.14.1.1 Connection with a Process Station When the connection to a chosen process station is established, a prompt is output on the Server's operating terminal. This prompt shows the relative process station's Technical Address (e.g. $177). This EKL can now be operated as though the terminal were connected directly to the EKL through its local V.24 interface.
2.14.1.2 Ctrl/E - Terminate Connection The connection to a process station (PRV/BPS/EKL-X) may be broken off with Ctrl/E. This also makes an exit from function DSS. With input of Ctrl/E an exit is also made from the EKL's own dialogue. If Ctrl/E is entered during CONF dialogue or in TSK Editor an exit from the operation and a return to 'Immediate Mode' is made. Only then can Function DSS be interrupted by a second Ctrl/E.
The following example illustrates how a file (whose File No. has been defined by PS point parameter FILE) is listed on VISONIK terminal T6: T6 12:57:04 Function =PNT : DSS Partner address (UA/TA)=$306: $177 $177> COPY DK:"" TO TT6: 12:58:11 S T A R T O F C O P Y .TSK1 10 PRINT DATE, TIME 20 ... 30 ... .TSK2 10 -- TEST/ZA 20 ... 30 ... .TSK12 10 -- Measurement Acquisition/GI 20 ... 30 ... EXIT 12:58:13 E N D O F C O P Y (189.
2.15 EDI Edit COLBAS Program Files 2.15.1 Full Screen Editor The Function "EDI", as described in the following text, works only with Visual Display Units such as VT100, VT220, VT320, GDT, Visual V603, etc. Operating terminals without screens (e.g. printers with keyboards) are supported only by a Line Editor. VISONIK Server filescan be efficiently processed using this Full Screen Editor. The Editor is a utility program contained in VISONIK software and can be called up directly from function CB.
2.15.2.1 CH, Change File A new file can be opened or an existing file can be edited with operation CH. ctrl/P T4 09:50:37 Function =PNT : EDI Operation =CH : File Number =(1..40): 13 If an empty file is selected, after the system's header line the "End of File" (EOF) message and file information. is displayed. [EOF Segment number 24520 File Number 13 0 bytes (20356 free) If the selected file has been previously edited the first 20 lines are listed (or less if the file is shorter). 2.15.2.
ctrl/P T4 09:56:41 Function =PNT : EDI Operation =CH : LTRC File Number =(1..250): 14 13:13:00 Start of trace into dump no. 14 --$R1 13:13:00 17105. EMPTY POLLS ......... ......... ......... ......... --> Operation =CH The complete File is listed, i.e. to marker. : A text file, i.e. a file in which only text has been edited may also be listed with LTRC. There is no difference in listing text files by either LIST or LTRC.
2.15.2.5 DIR, Directory of all Files In Operation DIR the first five lines of all files are listed. T8 11:57:00 Function=PNT : EDI,DIR File Number=1..250: === File 1: 19.12.1995 19:24 ##### File 1 ist reserviert fuer Tim Walsh ##### === File 2: 08.07.1996 15:08 ;###################################################### ;###### VISONIK V12/V14.04 .. V12/V14.04.
2.15.2.8 LINK, Join Adjacent Files With Operation LINK only adjacent files can be linked together. T8 13:42:46 Function=PNT : EDI,LINK File Number=1: 5 Anzahl=0 : 3 >>okay! === File 5: 17.12.1998/Do 13:18:08 0 bytes (+ 3 Linkfiles!) Files 5, 6, 7 and 8 are now linked together, i.e. file 5's length has been extended by that of files 6, 7 and 8. Remark: Linked files (in the above example, 6, 7 and 8) cannot be listed with LI.
2.15.4 Key Functions For file text handling, the cursor shift (arrow) keys and keypad function keys are used. Arrow Keys The cursor is positioned to the required text location using the four arrow keys. 9370Z23 On terminals similar to VT200 keys 'Previous screen' and 'Next screen' can also be used. Keypad keys on VTxxx Keyboards To provide a user with a comfortable method of working with the Full Screen Editor all keypad keys are fully supported.
Key (VTxxx) / Key (PC) The most important key is (HELP) key. After call up of the Editor (either through EDI or CB) pressing brings up a display which explains the functions of the keypad.
Chngcase +<1> Change case of selected character Command Key(s) Meaning EOL <2> Move cursor to end of line. Del EOL +<2> Delete all characters up to end of line. BOL <3> Position cursor at start of line. DEL BOL +<3> Delete all characters to start of line. Mark At Mark + Set transparent character. Position cursor at set transparent character. Line <0> Position cursor at new line. Open Line +<0> Open new line. Select Reset <.> +< .
After input of "File Number" the Block No. and number of free bytes plus the first line in the relative File are listed. Editor command format The 'Line Editor' instructions are now effective. Such instructions are made up of four parts: +/- nnn Xz...z ^ ^ ^ ^ 1 2 3 4 The individual parts have the following meanings: 1) "+"/"-" indicates the direction in which the associated command will operate. This is always with reference to the actual cursor position.
3Pzzz Searches three times for character sequence zzz. The "_" waits at the third zzz sequence -3Pzzz As above but backwards. T Sets ("_") at start of COLBAS file. Sets ("_") at start of next line. The "_" mark is not printed. \ Sets ("_") to start of previous line. The "_" mark is not printed. Czzz C(hange) = Replace character in the current line: Replaces a character after the ("_") with zzz. -Czzz As above but backwards.
2.16 GRR Group Reaction Register 2.16.1 Initial Access and Handling Function call-up CTRL/P GRR General A general introduction to the subject of VISONIK reactions can be found under "Reactions in General" in section R of this manual. The group reaction register GRR is one of six reaction types provided by the VISONIK DCS. The reaction types are named after the "reason" that is to activate the reaction in each case.
Example: Group reaction entry T8 Operation 0 1 2 3 4 Operation 10:34:40 Function=PNT : GRR =CH : ? CH = Change Data Entry LI = List Data Registers DEL = Delete Register Entry(ies) LSTA = List Reaction Register State LOCT = List Reaction Entries in Octal =CH : ctrl/P T8 10:36:20 Function=PNT : GRR Operation =CH : Address Mask =. : ? Address Mask UA = TA = ... = .. = * = =., (UA,TA,...,..
2.16.2.2 Creating a new group reaction entry Depending on the type of reaction program, the following prompts must be answered in order to create a new reaction entry: Definition of the "reason" Reason for the group reaction can be given as a single address or an address range. Address mask Entry Number of the reaction entry. GRR entries are not sorted by addresses, rather by address masks. Message priority This prompt only appears if the address mask is specified.
Reaction UA/TA Address of the data point on which the reaction is to act. The following inputs are permissible: • Technical address or $* masks • User address or $* masks • All addresses, including CT to PICT, by entering '..' (???) Parameter Specify the parameter to be modified. Parameter value In the example "Set Digital Output: Priority=0 :" The following possibilities are available for entering the parameter value: • A fixed value is assigned to the selected parameter.
Reaction CB CB Task Mode COLBAS Line No. The VISONIK DCS starts/stops one of the available DCS COLBAS tasks. Number of the COLBAS task whose operation mode is to be modified. Requested operation modes: RUN Stops the COLBAS task if it is active, and starts it at the line number entered. RESTART Starts a COLBAS task only if it is inactive. If the task is active, the instruction is ignored. STOP Stops the task and prints a STOP message. END Stops the task without a message.
Message mask For each reaction entry, the user can use the message mask to define which output devices of the VISONIK DCS are to register the reaction: Message Mask MSGDEV: M1 MM00: M1&M2 : MM15: M1&M2 Message Mask =MSGDEV : ? =MSGDEV : Message Mask =MSGDEV means that the reaction will be registered on the message devices that are listed according to message priority in the parameters DSM0..DSM3 (point type SY) of the point specified under "Reaction=".
T8 15:44:47 Function=PNT : GRR Operation =CH : LI Address Mask =* : $100* Entry =* : Reaction =.. : $100* GRR 15:45:00 Start of D A T A $d100'040 / 5 Edge Reaction Address Parameter Value Reporting - L I S T 13.08.1996/Tu T8 1 PACH_Change Point Parameter DO $d100'041 DO___Set Digital Output: Priority=0 0=Off MSGDEV M1 $d100'000...$d100'377 / 6 MSGP Edge Blocking Flag 0 (=Message Priority) 1 BL'OC'KING"01 Off ?FL_____GRR Blocked!________(BL'OC'KING"01.
Example for ?FL $d100'000...$d100'377 / 7 MSGP Edge Blocking Flag 1 (=Message Priority) 1 BL'OC'KING"01 Off ?FL_____GRR Blocked!________(BL'OC'KING"01.RFL=Step 1) Reaction PACH_Change Point Parameter Address DO $d100'041 Parameter DO___Set Digital Output: Priority=0 Value 0=Off Reporting MSGDEV M1 2.16.4 DEL, Delete Register Entry(ies) The DEL operation can be used to selectively delete reaction entries.
2.16.5 LSTA, List Reaction Register State This provides an overview of all Reaction Registers. T8 12:13:36 Function=PNT : GRR Operation =CH : LSTA Register Total Entries -------------------------------------------------Group Reactions GRR 1 Process Reactions PRR 7 Maintenance Reactions MRR 1 Time Reactions TRR 1 Step Reactions SRR 1 Date Reactions DRR 1 Total 12 Operation =LSTA : 2.16.
2.16.7 Special Features Edge The "Edge" here refers to the change in direction of FCON for any point within the related Address mask. A change of any fault condition from FCON=0 (normal) to FCON=1 (fault) corresponds to "Edge=1, and vice versa. "Edge=." has a special significance. If option "Enable SRK (GRR) by every Event" has been incorporated by Landis & Gyr through Function SYS,PROJ then every relevant Event (=main value change) coming from points which have their "Edge=.
2.17 KER KERMIT Protocol To transfer ASCII files between two computer systems a standard transmission protocol is necessary. This means that the computers involved must be able to communicate in a standard understandable "language". This is not always easy because of different Operating Systems. For this reason KERMIT was developed for American universities to meet the requirements of the most widely-used Operating Systems.
"EXIT" from the KERMIT program is the next step for an automatic return to the PC operating system. Kermit-MS>EXIT C:\ >_ 2.17.2 Establish Transparent Mode with VISONIK DCS After starting KERMIT at the PC, a "Transparent Mode" must be established with the partner VISONIK DCS. This means that, from the operator point-of-view, the PC looks as if it is a directly connected VISONIK DCS terminal from which the system can be operated.
2.17.4 Terminate Transparent Mode with VISONIK DCS After starting KERMIT in VISONIK DCS, transparent mode must be terminated from the PC. This means that further action to transfer EKP files is carried out from the PC. Re-entry into KERMIT operation at the PC is by simultaneously pressing "Ctrl" "]" followed by "Ctrl C". This is acknowledged by the PC "KERMIT" prompt: Kermit-MS>_ 2.17.
CM2U8567E / 04.
2.1 KEY Operator Key & Password Entries To have access to a VISONIK system a user requires certain authorisation. Among other conditions, this right of access is related mainly to the "reading" (list only) or "writing" (list and/or change) parameters via "Functions". This access authorisation may be compared to the ABILITY of clearing a hurdle of a certain height (Access Level) in order to reach a defined goal (Read, Write).
Following this, the listing continues showing those functions to which the user (John Brown) has access. These levels are numbers placed in front of the relative abbreviated Function's name. The left and right hand numbers refer to the "read/write" levels respectively. To each entry in the "KEY" register (see operation LI), VISONIK DCS automatically adds the following data: – The terminals at which the user is logged in. – Date of entry – The second last/last date of access to the system. 2.1.
2.1.2.1 New Entry To make a new "KEY" entry an authorised user has to specify the following conditions: Operation =CH User Code: : JB New Entry: ---------User Name=: John Brown User Code=JB: Expiry Date=31-Dec-99 ? Expiry Date-(dd-mm-yy): Delete Key after expiry=No: ? Delete Key after expiry=(No ,Yes ): YES Address Range=***'**'**"****: ? Address Range=(UA,TA,EKL,...,...,*) A00'A1'22"AAAA $eee'mm'p, $eee'VPn, $eee'RGn, $eee'PLn $eee ..=range ...=special range *=all : a01'b* Flag =$0'000: ? Flag =(UA,TA),.
Expiry Date The relative user's access expires on the specified date. In a KEY register listing this is noted by "Access Expired ! If an attempt is made to log in after an expiry date the message "?Access Expired !" is given together with the actual time and terminal number. Delete Key after expiry The answer (NO/YES) says whether or not the System shall automatically delete the "KEY" entry after expiry. The text "Delete Key after expiry" always appears in the listing until deletion.
Parameter Parameter 1 1 1 1 2 2 Level=0: ? Level=(0..7), ??: ?? 1 FL Flag Position 1 FLI1 FL Influence 1 1 RVAL Resultant Value 1 XX Message Language 2 PAGE Page Number 2 TY Terminal Status . . VISONIK DCS automatically reports any illegal parameter access. ctrl/P T1 00:42:46 Function =PNT : a01'b2'ST ST a01'b2'ST Status OFF Parameter =ST : 10:56:29 No Parameter Access! 3 3 TERS /Term.
RECOMMENDATION At any time a user can change his own password without using Function KEY. This is carried out by entering a question mark "?" directly after logging on with the current password. This question mark is terminated with and a new password may be specified (without echo).
The access authority of a user who is currently operating on the system cannot be changed and on listing the associated entry the following message is output. Only the specified language, the "Extra Device(s)" and password can be redefined: 13:49:12 ?Operator using System T1 Such a changed entry is only valid after the related active user is logged out from the System (either with Function BYE or timeout of ATMO).
Operation=LI : User Code: John Brown /JB DEL JB Function Level Parameter Level Operating Range Working Language Address Range Flag Address Active Devices Extra Device(s) Created by Date of Entry Last Access Expiry Date Delete Entry=No : = = = = = = = = = = = = 4 3 Local 1 a01'b*'** $FL77 . T3&T4 L&G System Manager 05-Dec-95 12-Dec-95 / 15-Dec-95 31-Dec-99 Delete Key after expiry YES * * E N T R Y E R A S E D * * The 'KEY' entry of an active user cannot be deleted.
2.19 MEMO Message to Terminals Using the MEMO function, • any kind of text, or • a specific clear text from the (TXCM,C) text register may be directed to one or several message channels. Output device Depending on what is connected to the specific message channel, the text will either be output as a composite message directly on an output terminal (printer, display terminal, etc.) or the messages may be transmitted onward to other VISONIK systems (in VISONIK Link System).
Message at printer T1: MEMO 13:21:04 Message from T4 to T1 Please call maintenance department! Transmitting Text from Clear Text Register: ctrl/P T4 10:58:27 Function =PNT : MEMO Message Channel=M4: M1 Message: #244 okay #244 is the line number in the clear text register Message at printer T1: MEMO 13:21:04 Message from T4 to T1 Please call maintenance department! Tel. No.
2.20 MRR Maintenance Reaction Register 2.20.1 Initial Access and Handling Function call-up CTRL/P MRR General A general introduction to the subject of VISONIK reactions can be found under "Reactions in General" in section R of this manual. The maintenance reaction register MRR is one of six reaction types provided by the VISONIK DCS. The reaction types are named after the "reason" that is to activate the reaction in each case.
Example: Maintenance reaction entry T8 11:48:12 Function=PNT : MRR Operation =CH : Reason =(UA,TA): $100'041 Entry =(1) 4 : Status =. : 1 Accumulated Tot. =0 : Maint. Hours =. : 1000 Maint. Date =. : . Automatic Reset =No : Yes Blocking Flag=. : No Blocking Flag=. : $F10 Flag Value =Off : ? Flag Value =(&,.,*,-,+=,-=,Off,Step 1,Step 2,Step 3): Step 1 Reaction =(UA,TA): ? UA/TA = Change Point Parameter CT = Printout Cleartext MC = Issue MACRO Command SLVM = Output Slave Message CB = Start/Stop COLBAS Task .
2.20.2.2 Creating a new maintenance reaction entry For a new maintenance entry, the following prompts must be answered: Reason Definition of the "reason" User or technical address of the point triggering the reaction. Points of all types may be used as "reasons". Entry The VISONIK DCS sorts the reaction entries according to their "reasons" and automatically allocates a number to each entry per "reason". A reaction entry can only be identified unambiguously with its entry number.
Definition of the reaction to be executed The following reactions can be triggered via a maintenance reaction entry: Reaction UA/TA CT MC SLVM CB . PICT = = = = = = = Reaction =(UA,TA): ? Change Point Parameter Printout Cleartext Issue MACRO Command Output Slave Message Start/Stop COLBAS Task No Reaction (for MRR & GRR) Auto Picture/Point Selection =(UA,TA): Reaction UA/TA Address of the data point on which the reaction is to act.
Reaction SLVM Print slave messages. The VISONIK DCS normally only prints spontaneous messages if the status of a point changes in the peripheral equipment (). An SLVM reaction is required in order to force point messages (e.g. cyclic polling of a temperature using a date reaction). When the reaction is triggered, the VISONIK DCS reports the main value of the point in the defined message mask, without the point status having changed.
Message mask For each reaction entry, the user can use the message mask to define which output devices of the VISONIK DCS are to register the reaction: Message Mask MSGDEV: M1 MM00: M1&M2 : MM15: M1&M2 Message Mask =MSGDEV : ? =MSGDEV : Message Mask =MSGDEV means that the reaction will be registered on the message devices that are listed according to message priority in the parameters DSM0..DSM3 (point type SY) of the point specified under "Reaction=".
2.20.3 LI, List Data Registers The LI operation can be used to selectively list the reaction entries. The contents of the list can be filtered according to the following criteria: • by reason address • by entry numbers • by reactions If the reaction type CT, MC or CB is entered at the prompt "Reaction=?:", the user can make a finer selection according to text or task number. FZT8 Operation Reason Ent10ry Reaction MRR 11:31:29 DO DO 11:31:16 Function=PNT : MRR =CH : LI =.. : .. =* : * =.. : ..
?REAR This system-internal tag ("Reason for Reaction") denotes that the "reason" for a process or maintenance reaction has not been set although a reaction entry exists. The VISONIK DCS manages this "REAR" tag in the reaction programs, ensuring optimum and fast reaction access. If this tag is not present, no process reactions will be executed as a result of this "reason". Errors of this kind are corrected automatically when the register is printed or when the function VE (verify data file) is executed.
2.20.4 DEL, Delete Register Entry(ies) The DEL operation can be used to selectively delete reaction entries. The entries to be deleted can be filtered according to the following criteria: • by reason address • by entry numbers • by reactions If the reaction type CT, MC or CB is entered at the prompt "Reaction=?:", the user can make a finer selection according to text or task number. T8 08:52:45 Function=PNT : MRR Operation =CH : DEL Reason =.. : $100'041 Entry =* : 3 Reaction =.. : ..
2.20.5 LSTA, List Reaction Register State This provides an overview of all Reaction Registers. T8 08:55:48 Function=PNT : MRR Operation =CH : LSTA Register Total Entries -----------------------------------------------Group Reactions GRR 5 Process Reactions PRR 6 Maintenance Reactions MRR 1 Time Reactions TRR 1 Step Reactions SRR 1 Total 14 Operation =LSTA : 2.20.
2.20.7 Special Features Reaction=:." If no reaction ("Reaction=.") is defined in a maintenance reaction register, then this entry is • taken as a pure operating-hours counter automatically supplemented by: – an error counter – a daily counter – if required, a reference to the COLBAS Pool. Reaction COLBAS pool no. Message mask =(UA,TA,*): =(0..10000000), .: 100 =0 :. Error Counter During a system breakdown the Maintenance Reaction program cannot clock the time.
COLBAS Pool Number If a COLBAS Pool number is given in a Maintenance Reaction entry the respective measured operating hours are added to the specified Pool value approximately every 5 minutes. There, the accumulated total is always available to any COLBAS program for further processing (Statement: DIM #k= v(x,y), where k=COLBAS Pool number as per the Maintenance Reaction entry).
2.21 MXD Maximum Demand Register Entries Energy costs are dependent on maximum demand Contracts with energy utilities often contractually fix how high the maximum energy consumption may be within a defined integrating period (e.g., 15 minutes). If this maximum consumption is exceeded once within an billing period, this can increase energy charges considerably. In order to measure this ongoing energy consumption, the energy utility transmits a synchronisation pulse at the end of each integrating period.
MD [kWh] ESTM for T1 EMAX TTOL LM OF LM ON = = F OF ON Lim Lim it ESTM for T2 it STOL 9370Z53E Tolerance band T1 Shed load T2 Connect load Time TPER (e.g. 15 mins.
Activating the MXD program The maximum demand programs running in the background can be switched on or off with their respective "TGRP Tariff group" MD parameters. TGRP = 0 The maximum demand program of the associated MD point is switched off. TGRP = 1 to 7 The maximum demand program is active for maximum demand points having TGRP<>0. The regulation output variable however is only newly calculated after receipt of a change in counter values or synchronisation pulses.
2.21.2 CH, Enter Sheddable Loads or Generators For: • each sheddable load (positive load), or for • each connectable generator (negative load) the user has to enter in the maximum demand register the required data such as, for example, their priorities. Each load (positive or negative) must be assigned to a tariff or meter group.
Entry =1 Several entries may be made for each address in the MXD register. Application: The same load can, for example, be assigned to both a high tariff grup and to a low tariff group. If a number is entered which is already used, the VISONIK DCS lists the contents of the entry and returns to CHange mode. Tariff/Meter Grp=1 All loads that belong to the same tariff are collected into one tariff group.
Shedded value Example: The shedded value is that value of switched step from which loads (positive loads) are connected, or generators (negative loads) are disconnected. After being switched both positive and negative type loads are in then in a state equal to the 'threshold value' (= larger load).
Blocking flag Size of the switchable load Each command step (0 to 3) of a programmed DO point is assigned to a corresponding load through parameters PN1 to PN3 (positive for real loads, negative for generators). All DO entries can be blocked by appropriate setting of the relative 'Blocking flag'. Blocking flags must be given "$" addresses (i.e. $FLn). Flag value This defines that flag value at which the entry will be blocked.
2.21.3 LI, List Entries Operation LI provides a listing of MXD Registers. The listing can be restricted to the following criteria: – Address – Tariff/Meter Group – Priority The content and format of the list is identical to the RPT,MXD MD report. The report is described in detail under this function.
2.21.4 L8, List Entries in Octal This provides a listing of MXD Registers in octal code and can be restricted by the following criteria: • Address With exception of the octal information, the contents and format of the list are identical to the RPT,MXD MD report. The report is described in detail under this function.
Supporting Actions $000'000 $000'000 If the sheddable loads entered in the MXD Register are insufficient to maintain a fixed average load (EMAX), this will be reported by the program (error condition k.o.). Automatic shed insufficient Additional manual shedding - (..) KW MD program demand per 15 min. MD= (..) kWh FCON= k.o. There is the possibility of manually shedding a required load at a certain time in order to avoid exceeding the maximum demand for the current integrating period. 2.21.
New consecutive numbering of the entry numbers Siemens Building Technologies Landis & Staefa Division Old structure New structure Entry : Priority: Entry : Priority: Entry : Priority: Entry : Priority: Entry : 1 Priority: 11 d e l e t e d 1 11 2 12 3 13 4 14 ---> Entry : Priority: Entry : Priority: VISONIK DCS Functions and System Messages VVS18 Function MXD 2 !! 13 3 !! 14 CM2U8567E / 04.
CM2U8567E / 04.
2.22 PG Point Generation What does PG do? On point generation, a memory area is reserved in the DCS for the point that is to be generated. This memory area, whose structure depends on the respective point type (CTYP), is called the Process Image. The process image determines the appropriate parameter set for each point that is generated. The process image is the software prerequisite for point operation via the DCS.
Point generation when hardware is not present. As a general rule, the following points can be generated in the DCS within the allowable PS address range: – modules per process station, with – points per module. Therefore, depending on the type of process station connected, the address range of the DCS goes beyond the physically connected hardware. Points that are generated in the DCS but are outside the address range of the connected hardware can be operated in the DCS with OPMO=DSf (fictitious in DCS).
Technical address, permissible address range Each data point can be generated within the permissible address range only. Process Stations $PS'mm'p A DCS's process image is basically dimensioned for 255 (377 octal) process stations. Certain PS addresses, however, are reserved internally in VISONIK systems and must never be allocated to process stations. To provide uniform system addressing it is recommended to use the following address range sectors: Decimal Octal $001 $002 . . $127 $128 . . $144 $002 .
EKL Bus and P-Bus module points $PS'mm'p A DCS process image supports a maximum of 8 points per module of a BPS, PRV1 or EKL. The actual maximum possible number of points per module depends on the PS type and also the respective module type. Point type ML MW SB1 SBR1 SBR2 SBR3 STP ST3P STU ZW P-Bus modules and module points CM2U8567E / 04.
Point types not addressed through EKL Bus or P-Bus Siemens Building Technologies Landis & Staefa Division $PS'TYPn Example for BPS = $50, in alphabetical order. Pnt type Addr.ranges Remarks / limitations AI AO BLN CI CVP DI DO FLN MBUS $50'AI1 . . 255 $50'AO1. . 255 $50'BLN $50'CI1 . . 255 $50'CVP1 . . 255 $50'DI1 . . 255 $50'DO1 . . 255 $50'FLN $50'MBUS The following applies to AI, AO, CI, DI and DO -------------------------------------------------The range 250..
Point types which relate only to DCS $TYPn in alphabetical order Pnt type Addr.ranges Remarks / limitations FL $FL1 . . 510 MD $LS1 . . 7 MC $MC1 . . 15 OZ $OZ1 . . 127 RI $RI1 . . 6 SY $SY TY $TY1 . . 18 Terminals with fixed connections to DCS identical to $d193'TY . . $d211'TY identical to $o301'TY . . $o323'TY $d225'TY . . $d247'TY Teleterminals identical to $o341'TY . . $o367'TY $d168'TY . . $d183'TY Teleprinter identical to $o250'TY . .
Point type Most data points must be generated using the function PG as described here. There are, however, certain exceptions. The following table is sorted by point types. It shows whether and how each point type can be generated. Pnt type CTYP Text Notes on generation ML 0 Status input Generate with PG. MW 1 Measurement input Generate with PG. ZW 2 Counter value Generate with PG. SB1 3 Switch command 1-step Generate with PG.
VIP 27 Virtual point Generate with PG. ZON 28 Process station OSTP zone Generate with PG. PLT 29 Plant point Generate with PG. PBUS 30 Process bus The process image of a PBUS is automatically generated by the VISONIK DCS as soon as the first data point of the FLN 31 Floor Level Network P-Bus is generated. The process image of an FLN is automatically generated by the VISONIK DCS as soon as a card of type PVC2.1F is installed at COM2 in the BPS and is detected by the DCS.
TCR 48 TEC room Generate with PG. Important: TCR and MGR points are mutually exclusive because of the BPS card. TCG 49 TEC group Generate with PG. Important: TCG and MGG points are mutually exclusive because of the BPS card. RWI 50 RWI Controller Generate with PG MX 51 Multiple status input The MX point is generated in the VISONIK DCS using the function PG in the same way as for an DI point. However, the type MX must be entered at the 'Point Type' prompt, instead of DI.
Consequences for point generation The correct CTYP must be entered at point generation. If the I/O point to be generated is located on the EKL Bus or P-Bus, the appropriate CTYP for ME, PS, ST, SC or CG must be selected. The appropriate CTYP for AI, AO, DI, DO or CI must be entered in all other cases. Notes on TEC room configuration After point generation, up to 10 TEC controllers can be allocated to a TEC room via the parameters TEC(1)..TEC(10).
Note All permissible characters (active, delimiter, dummy delimiter characters) can be displayed/listed via the function UAX,LCHR. Delimiters and dummy delimiters can always be specified, although they are only mandatory when required for unambiguous interpretation of an address input.
Example with EKL process station: ctrl/P T4 15:14:03 Function =PNT : PG Operation =PPG : LI TA TA / Technical Addr. =$66'PS: ? / Technical Addr. =(EKL) $eee ,$deee ,$oeee : $77'PS $77'US Version = 472 EKX SDLC / RING . 0 1 2 3 4 5 6 7 10 11 12 13 14 15 16 17 20 21 22 23 PNT /INB=YES ----------------------------------------------------------------------------SW:ST . . ST MX ME CG SC PS CP . . . . . . . . . . 46 / 36 HW:. . . 10 10 38 14 20 39 . . . . . . . . . . .
Example with BPS process station: T8 16:36:10 Function=PNT : PG Operation=PPG : LI TA / Technical Address=$d100'PS : $d100 = $o144__________BPS_________________.___________________ Version v13.50 NAME rt'z RITA $RI1 Cards TMBD/VMBD=PRV2.128 TMEM/VMEM=PVC1.1S /1 TCM1/VCM1=PVC1.1ST/1 TCM2/VCM2=-TPSP=128 Points/STAC=.
2.22.5 DEL, Delete Points in a PS Points in a process station can be deleted by defining them at the "Address Mask=" prompt. ctrl/P T4 15:15:37 Function =PNT : PG Operation =PPG : DEL Address Mask =$66'US: ? Address Mask =+, -, (UA,TA,EKL,..,.,*) A00'A1'22"AAAA $eee'mm'p, $eee'PLTn, $eee'RGBn,$eee'VIPn, $eee'ZONn, $eeeMxxpyy $eee , $deee , $oeee ..=range ...=special range *=all : $66'000..
2.22.
CM2U8567E / 04.
2.23 PMD Post Mortem Dump The PMD report is used for system diagnostics. The report's contents can be analysed by L&G specialists only. Related functions The PMD report can be accessed in two different ways: • via the function PMD • via RPT, PMD This makes it possible to define a special access level for the PMD report. The reports produced are identical in both cases.
2.23.1 Initial Access and Handling Function call-up CTRL/P PMD As the following example shows, the content of the report can only be analysed by L&G specialists. T8 15:43:35 Function=PNT : PMD Output Device =$TT: 342 = Trap 250: MM-Abort v14.04.012 23.07.1996/Tu 12:17:12 Bclock=30764.
Stack: 60736/100576 = MEM1 + 576 BGD1 <----- (CSC#=206 BL=0) (33150. = 201|176) CSL-Data -------csbu= 10 C.ta=$d100'041 CxAD=60000,0,0,2400,402,0,2163,41,62052,4 C.ad=$d2'000...$d254'377 P.u1=$d0'000 C.xpn=0/0.= C.mst=0 C.act=0 C.sld=17426 COMMON-Data ----------DPblkp=41,3000,22040,0,10000,25200,0,0,0 Current Process (LTMP): ----------------------DLG = Dialog Status=100000=ACT Adr/T.flg T.tic pnr dest pri T.par T.alo T.pad T.csll T.csc T.dsw1 T.
Remark: If the hard disk contains no usable data, whether this is because no major error has occurred to date or because the memory dump to the hard disk was not executed correctly, the following message will be printed when a PMD report is called: *** Sorry, inconsistent data *** CM2U8567E / 04.
2.24 PNT Change/List Point Parameters A current copy of the data associated with all information points is stored on the mass storage media of the VISONIK DCS in the form of parameters in the process image. By calling the function PNT and entering the respective point address (technical or user address) a user can read or change any associated parameter values (depending on proper access authority and parameter type).
Operator's Address Range = *01'**'**"**** Legend: This represents a range of addresses to which the current operator has access. UA A00'A1'22"AAAA Point selection through User Address. On input of "*", the first address in the system is prompted according to alphabetical structure. TA $eee'mop, $Rn, $S, $Tn, ... Technical Address selection. + Next UA/TA By entering a "+" the next User or Technical Address can be called up in ascending alphabetical order.
ctrl/P T8 + AI 11:24:56 Function=PNT : $100'001 RO'OM'TEMP"01 Training Department 65.2 Deg. C ERSTA= >HIL=20.
Parameter listing with "**" The display is basically the same as above. If two asterisks "**" are entered, however, the complete range of indexed parameters is listed (MSGT in the example). Important: Such lists can be very long. Parameter=AI : ** MAIN Parameter - AI | Analogue Input (Measurement) | CONFIGURATION Parameters | MSGT(1) | Message Type MSGT(2) | Message Type | Parameter listing with "*.*" =65.3 Deg. C = = =0. =0. = Some parameters have additional attributes.
2.24.4 Modifying parameters By entering a parameter's abbreviated name, the user has direct access to the corresponding parameter value, which can be modified within its range, depending on the user's write privileges. Data types Every parameter is associated with a particular data type. The VISONIK DCS supports the following data types: • Numerical parameters • Text parameters • Bitset parameters • Other data types Numerical parameters Example for CHPL: [ 80..
Bitset Parameters (with texts) Example for DYBE: [ &, ., *, -, +=, -=, Mo, Tu, We, Th, Fr, Sa, Su ] With bitset parameters any desired combination of options can be specified from a defined selection. Bitset parameters are recognizable by the permissible operators, which are always displayed [ &, ., *, -, +=, -=, ].
2.25 PNX Change/List Multiple Point Parameters What does PNX do? The function PNX provides the user with highly flexible means to • change parameters and/or • list parameters of a large number of points in great detail and according to complex constraints. The function PNX is a useful extension to the functions PG, PNT and RPT. It is related to RPT,PNX, except that it allows parameters to be changed. 2.25.
Parameter Value = 0: 2. Masking Param.=.: MSGP Parameter Value = 1: 2 3. Masking Param.=.: 1. Operating Param.=.: ? Parameters allowed: All 1. Operating Param.=.: OSV Operating Mode=CHA: ? 0 LIST = List Parameter 1 CHA = Change Parameter (Fixed Value) 2 CHP = Change Parameter(Point by Point) 3 INSP = Inspect before Parameter Change 4 RPDV = Param.
Operating Mode Selection of the change or list mode. Any combination of the following possibilities can be selected. Example: CHP&INSP, etc. – LIST – CHA – CHP – INSP – RPDV – RPCH – LICR – LISE List Parameter Change Parameter (Fixed Value) Change Parameter (Point by Point) Inspect before Parameter Change Parameter Change Messages (MSGDEV) Parameter Change Messages (DEVPCH) CRLF before Listing Parameter Printout with Separator with Status Rpt.=No Is a status report required, "Yes/No".
2.25.2 Parameter Change/List Operating Mode Automatic or manual parameter change The function PNX allows parameters to be changed in two different ways: – Allow the VISONIK DCS to automatically change the complete selected point set to a specified value. – Manually change each value, point by point, to a new, freely selectable value. The system carries out each parameter change in the sequence of entered operating parameters.
LICR CRLF before Listing Parameters The VISONIK DCS lists the specified parameters for each point address. In contrast to the LIST option, each parameter is listed on a new line. LISE Printout with Separator The VISONIK DCS lists the specified parameters for each point address. In contrast to the LIST option, a separator ";" is inserted between each element. This option is especially intended for use with loader programs.
CM2U8567E / 04.
2.26 PRR Process Reaction Register 2.26.1 Initial Access and Handling Function call-up CTRL/P PRR General A general introduction to the subject of VISONIK reactions can be found under "Reactions in General" in section R of this manual. The process reaction PRR is one of six reaction types provided by the VISONIK DCS. The reaction types are named after the "reason" that is to activate the reaction in each case.
Example: Process reaction entry T8 16:53:04 Function=PNT : PRR Operation =CH : Reason =(UA,TA): $100'001 Entry =1 : 2 Positive Edge =. : ? .: No Reaction 0: Normal 1: Normal ---> >HIL 11: ... ---> OPSTA 12: ... ---> ERSTA 13: ... ---> Main Value 14: For Every Event Positive Edge =. : 1 Negative Edge =. : ? .: No Reaction 0: >HIL ---> Normal 2: Normal ---> ... 12: ERSTA ---> ... Negative Edge =. : 2 Lower Limit =. : 15 WARNING : OPMO!! OPMO! Limit without Function High Limit =.
Acknowledgement of the above reaction entry FL $FL77 = PR'OC'ESSR"01 / 3 Positive Edge 1: FL=0 ---> FL=1 Negative Edge 2: FL=3 ---> FL=2 Blocking Flag BL'OC'KING"01 Off ?FL_____PRR Blocked!________(BL'OC'KING"01.RFL=Step 1) Reaction PACH_Change Point Parameter Address DO $d100'041 Parameter DO___Set Digital Output: Priority=0 Value 0=Off Reporting MSGDEV M1 2.26.2 CH, Enter/Change Data 2.26.2.
Using the help function with’?’ Positive Edge .: 1: 2: 3: 5: 14: The permissible "edge" types differ according to point type, and they are not listed completely in this document. During programming, therefore, it is advisable to display the possibilities that are permissible in each case using the Help '?' function. =. No Reaction rDO=0 ---> rDO=1 ---> rDO=2 ---> Auto ---> ... ---> Three dots ‘...
The explanations for 'Positive Edge' equally apply. The line with edge 12 thus stands for: ERSTA ---> ... ERSTA Triggering of a response, if the error status ERSTA changes from any value to a predefined value. The previously mentioned predefined value (OPSTA, ERSTA, Main value) must be entered upon a prompt. Note Positive and negative edges must be combined following rules: – When choosing positive edge 13 ( ---> Main value), no negative edge is available.
Reaction UA/TA CT MC SLVM CB . PICT = = = = = = = Reaction =(UA,TA): ? Change Point Parameter Printout Cleartext Issue MACRO Command Output Slave Message Start/Stop COLBAS Task No Reaction (for MRR & GRR) Auto Picture/Point Selection =(UA,TA): Reaction UA/TA Address of the data point on which the reaction is to act. The following inputs are permissible: • Technical address or $* masks • User address or $* masks • All addresses, including CT to PICT, by entering '..
Reaction SLVM Print slave messages. The VISONIK DCS normally only prints spontaneous messages if the status of a point changes in the peripheral equipment. An SLVM reaction is required in order to force point messages (e.g. cyclic polling of a temperature using a date reaction). When the reaction is triggered, the VISONIK DCS reports the main value of the point in the defined message mask, without the point status having changed.
Message mask For each reaction entry, the user can use the message mask to define which output devices of the VISONIK DCS are to register the reaction: Message Mask MSGDEV: M1 MM00: M1&M2 : MM15: M1&M2 Message Mask =MSGDEV : ? =MSGDEV : Message Mask =MSGDEV means that the reaction will be registered on the message devices that are listed according to message priority in the parameters DSM0..DSM3 (point type SY) of the point specified under "Reaction=".
?REAR This system-internal tag ("Reason for Reaction") denotes that the "reason" for a process or maintenance reaction has not been set although a reaction entry exists. The VISONIK DCS manages this "REAR" tag in the reaction programs, ensuring optimum and fast reaction access. If this tag is not present, no process reactions will be executed as a result of this "reason". Errors of this kind are corrected automatically when the register is printed or when the function VE (verify data file) is executed.
2.26.4 DEL, Delete Register Entry(ies) The DEL operation can be used to selectively delete reaction entries. The entries to be deleted can be filtered according to the following criteria: • by "reasons" • by entry numbers • by reactions If the reaction type CT, MC or CB is entered at the prompt "Reaction=?:", the user can make a finer selection according to text or task number. T8 12:36:31 Function=PNT : PRR Operation =CH : DEL Reason =.. : ? Reason =(UA,TA,...,..
2.26.5 LSTA, List Reaction Register State This provides an overview of all Reaction Registers.
2.26.6 LOCT, List Reaction Entries in Octal The LOCT operation can be used to selectively list the reaction entries according to the same criteria as the LI operation. The normal list is followed by a printout of the same data in octal code. T8 12:17:08 Function=PNT : PRR Operation =CH : LOCT Reason =.. : ? Reason =(UA,TA,...,..,*) UA = AA'AA'A111"dd TA = $sss'mm'p, $sss'CTYPn, $CTYPn, $sssMxxPyy ... = digitwise range .. = range * = all points with UA, $*=all points , .. : $* Entry =* : ? Entry =* , (1..
2.27 Reactions 2.27.1 Reaction Programs in General Reaction programs are programmed operations that can be initiated through particular conditions (known as 'reasons'). If a defined condition arises during plant operation, all of the associated commands are executed in sequence. Reaction programs are named after the type of 'reason' with which they are associated (e.g. process reaction, time reaction, maintenance reaction, etc.). 2.27.1.
Reason N Blocking flag set? N Reaction No reaction 9370F05E Flag value valid? 2.27.1.3 Change Resultant Setpoint (RDO/RFL) according to Priority The RVAL output values (parameter RDO/RFL) of digital points DO and FL are prioritized. A reaction can be used in conjunction with the parameters DO1ACT/FL1ACT and DO2ACT/FL2ACT to determine which of the following parameter values is output as the setpoint for the respective point: DO/FL (Prio=0, DO1ACT/FL1ACT=. and DO2ACT/FL2ACT=.
METHOD 1 When the reaction is triggered, both the main value (DO1 or DO2) and the respective bit influence (DO1ACT or DO2ACT) are modified according to the reaction entry. In order to achieve this, parameter DO1 or DO2 is set to the appropriate value. The respective influence bit number is set to either 0 or 1 as required. The above statement applies analogously to flag points.
2.27.2 Special Features of Digital Output Points 2.27.2.1 Change Setpoint to the Last Valid Value When the reaction is triggered, the most recently valid setpoint (RDO/RFL) of a switch command point is restored (e.g. after a power failure). The parameter FBX of the DO point must at least have the value NO. This type of reaction is especially efficient when it is used in a step reaction chain.
Example A 3-step switch command should be switched to coincide (SAME) with an analogue value: Function Address Parameter Reaction Address Parameter AI = 21.4 Deg.C AI = -9.1 Deg.C DO = 21 ---> DO = 3 DO = -9 ---> DO = 0 2.27.2.3 Change of Parameter to the INVERSE of any Main Value When the reaction is triggered, the parameter value of the reaction address is set to the INVERSE of the main value of any chosen point (so-called function address).
CM2U8567E / 04.
2.28 RPT Reports A report contains information on individual data points, groups of points (external plant) or the complete DCS. Starting a report A report can be started manually by an operator, or automatically by reaction programs using macro commands. 2.28.1 Initial Access and Handling Function Call-up CTRL/P RPT The VISONIK DCS opens a list of possible report options, as follows: T8 12:49:01 Function=PNT : RPT Rpt.
Entering an address mask The following rules apply to the analysis of the address input in address masks: • The characters that are entered are inserted in the address sections from left to right. • Missing characters are normally substituted with asterisks "*". However, if the input is terminated with a space, the missing characters are substituted with spaces.
... Range With this method of range definition each character of the first address limit is compared with the corresponding character of the second. The resultant address range includes every address that fulfils all conditions. C7A1 ... U9K8 --> AND AND AND All user addresses whose first character is between C and U All user addresses whose second character is between 7 and 9 All user addresses whose third character is between A and K All user addresses whose fourth character is between 1 and 8 2.28.
Par.Val. Permissible input: Value of the masking parameter specified above. The system only prompts for "Par.Val.:" if an entry has been made for the preceding "Masking Param:". Result: The report contains only those data points for which the specified parameter has the value "Par.Val." Output Device Specifies the report output terminal. Any terminal device configured in the DCS (T1..T18) can be entered.
Examples Masking Param. Par.Val.= 42= =.: CTYP : DI This input limits the report to the "DI" point type. Masking Param. Par.Val.= 1 =.: MSGP : 2 This input limits the report to data points with message priority = 2. Masking Param. Par.Val.= 1 =.: MSGP : <2 This input limits the report to data points with message priority < 2. Masking Param. =.: TYX Par.Val.= ITER&XoXf : not ITTY&XoXoff This input limits the report to data points whose bits ITER and XoXf in parameter TYX are NOT set. 2.28.
2.28.5 Graphical presentation of reports Report Start and End Lines FRPT 14:42:10 R E P O R T Selected Address Range Defined Parameter FRPT 14:42:11 R E P O R T ^ ^ | | a b = : - S T A R T $Ty1...$Ty18 OSVL ="Yes" E N D 30.07.1996/Tu (T1) T4 30.07.1996/Tu ^ | c (T1) ^ | d T4 ^ | e Explanation: a) Report type b) Time of report start (or end). c) Date and day of report printout. d) Terminal from which the report was started. e) Report output terminal.
Information Fields P (4) T (4) U (1) STAP TYPE Tag N (26) D (32) NAME TXI+TXI2 M (24) S (20) I (10) Pt type dependent Pt type dependent Pt type dependent The peripheral state STAP is displayed according to the message priority. Point type. A space is normally displayed at this location. A dash "-" means that the point's spontaneous event messages are suppressed (parameter MSGSUP<>.) and are, therefore, not printed. User/technical address. Point name as per parameters TXI and TXI2 (with no space).
I/O points Point type Analogue Input For TYPE=AI: Analogue Output For TYPE=AO: Counter Input For TYP=CI: Digital Input For TYP=DI: Digital Output For TYPE=DO: or: 'M' Main value 'S' Status 'I' Additional information AI TXU (ERSTA<>0 | OPSTA<>0) {OPMO} AO TXU (ERSTA<>0 | OPSTA<>0) {OPMO} CI TXU (ERSTA<>0 | OPSTA<>0) {OPMO} DI=(TXU) (ERSTA<>0 | OPSTA<>0) {OPMO} DO=(TXU) "("Prio")" FBV=(TXU) "("Prio")" (ERSTA<>0 | OPSTA<>0) (ERSTA<>0 | OPSTA<>0) {OPMO} Function points Point type Virtual poin
MONOGYR Points Point type 'M' Main value 'S' Status 'I' Additional information MBDIAG (ERSTA<>0 | OPSTA<>0) MPNT For CTYP=MGG: (SOPST | MOPST) 3) AVRT "°C" (ERSTA<>0 | OPSTA<>0) {OPMO} or: (SOPST | MOPST) AVRT "°C" {SPCC SPCH} {SPEH} additionally: "MGR"MGR(i)<>0":" AOPST=(TXU) ARTP "°C" For CTYP=MGR: AOPST(1)=(TXU) ARTP "°C" (ERSTA<>0 | OPSTA<>0) or: AOPST(1)=(TXU) ARTP "°C" {ASPH ASPC} additionally: "SEZ"SEZ(i)<>0":" ADOsez ADIsez ADOsez ADIsez (ERSTA<>0 | OPSTA<>0) {OPMO} 'S'
FLN and PBN Points Point type 'M' Main value For TYPE=FLN: INR For TYPE=PBN: BD"Bd"NSTA 'S' Status 'I' Additional information (ERSTA<>0 | OPSTA<>0) {OPMO} 2.28.6 FRPT, Fault Report Generally only points that fulfil the specified address, parameter name and parameter value conditions are reported. The parameter name and parameter value can be optionally specified as constraints. An FRPT lists all points that are in a fault state. "fault" in this case means that: • the error status is ERSTA<>0.
2.28.7 SRPT, Status Report In the SRPT the current status of all points that fulfil the specified address, parameter name and parameter value conditions is reported. T8 15:58:18 Function=PNT : RPT,SRPT Address=$Ty10 : $100'000..$100'012 Masking Param. =.: Output Device =$TT: Insert Form Feed =.: >>o.k.! SRPT 15:59:39 R E P O R T - S T A R T 30.07.1996/Tu T8 Selected Address Range = $100'000..$100'012 + AI RO'OM'TEMP"01 Training Department 64.8 Deg. C ERSTA= >HIL=25.
T8 16:25:27 Function=PNT : RPT,MRPT Address=$Ty10 : $* Due Date=. : FR Output Device =$TT: Insert Form Feed =.: >>o.k.! MRPT 16:25:39 R E P O R T - S T A R T 30.07.1996/Tu T8 Selected Address Range = $2'000...$254'377 Due Date: 72h ... DO $100'040 (m17p1) Training Department RDO=Off OPMO=5=PS Entry 2: from 30.07.1996 Status 1 0h In Serv. Maintnce : 34h *** Check light *** . DO $100'041 (m17p2) Training Department RDO=Off OPMO=5=PS Entry 3: from 30.07.1996 Status 1 0h In Serv.
T8 16:32:54 Function=PNT : RPT,TRPT Set=* : 1 Trend Channel=* : 1 Output Device =$TT: Insert Form Feed =.: >>o.k.! TRPT 16:33:14 R E P O R T-S T A R T Set = 1 ======= 1. Trend Point = Parameter = Value - Left Mar = Value- Right Mar = a) b) c) d) e) Siemens Building Technologies Landis & Staefa Division T8 a) RO'OM'TEMP"01b AI Symbol 0 Deg. C Colour 100 Deg. C Pattern Total Entries = 1 TRPT 16:33:15 R E P O R T-E N D Explanations: 30.07.1996/Tu 30.07.1996/Tu = A = Red = 0 = (..
2.28.10 ERPT, Extended Point Report The following information is displayed in the extended point report ERPT: • The current status of the selected point. • All parameters of the point with their respective values. • A reference table that indicates in which reaction registers the point is referenced (including COLBAS). These are one process reaction and one maintenance reaction in the following example. T8 16:37:57 Function=PNT : RPT,ERPT Address=RO'OM'TEMP"01: $100'040 Masking Param. =.
2.28.11 SCR, Short Configuration Report In the short configuration report SCR all configured parameters of a point are displayed, i.e. those parameters whose value does not correspond to the default value of the DCS. FZT8 09:12:04 Function=PNT : RPT,SCR Address=$d100'041 : $* Masking Param. =.: Out10 put Device =$TT: Insert Form Feed =.: >>o.k.! SCR 09:12:05 R E P O R T - S T A R T 31.07.1996/We T8 Selected Address Range = $2'000...
2.28.12 LCR, Long Configuration Report In the long configuration report LCR all parameters of a point are displayed. In contrast to the SCR report all parameters of the selected point are printed out, regardless of whether the value corresponds to the default of the DCS or not. This means that the LCR corresponds almost exactly to the extended point report ERPT, except that it contains no reference list. T8 09:38:12 Function=PNT : RPT,LCR Address=$Ty1 : $* Masking Param. =.
The printout of a SYSR report can be flexibly controlled depending on the way in which the system prompt "ADDRESS" is answered. Address selection: or: Hardware, software Shadow information System loading Reaction Registers Teletypes Ring configuration Process stn descr. * $* yes yes yes yes all all all $xx $xx..$yy ------x $Rx $Rx..
SHADOW Information This information gives an overview of any shadow function in the system. It shows whether the shadow function is on or off, on which disk the shadow is saved, when the last shadow was saved (with date and time) and how many data blocks are occupied on the disk (octal). SHADOW Informations: ==================== Shadow on Unit 1, Offset (octal): 0 Shadow is OFF. Last update: 25.09.
Reaction registers Overview of the free entries and occupied entries in the various reaction registers.
Explanations: HW.Addr Every SDLC ring connected to the VISONIK DCS is identified by a ring number (Rn) and a ring controller hardware address (HW.Addr). TA Technical address (TA) of the ring. RIST Current ring status (see parameter RIST). BD Ring transmission speed. PS Sequence The electrical connection sequence of all process stations is displayed in the second line. Status display The process station numbers include an additional status display ("." in example).
PS Description The report contains different information depending on process station type. The following example refers to a PRV process station. PS Description: =============== $d100 = $o144___________BPS_________________________________.____________ ______ Version v13.50 NAME rt'z RITA $RI1 Cards TMBD/VMBD=PRV2.128 TMEM/VMEM=PVC1.1S /1 TCM1/VCM1=PVC1.1ST/1 TCM2/VCM2=-TPSP=128 Points/STAC=.
The five principal sections of the PS description are: • Hardware information • Configured I/O module points • Configured data points without I/O modules • Variable section, depending on the displayed process station type • Statistics Hardware information Header $d100 = $o144___________BPS_______________.___________________ Version v13.
Cards Cards TMBD/VMBD=PRV2.128 TMEM/VMEM=PVC1.1S /1 TCM1/VCM1=PVC1.1ST/1 TCM2/VCM2=-TPSP=128 Points/STAC=. 20 / 0 • • • • • TMBD/VMBD: Motherboard type and version TMEM/VMEM: Program card type and version TCM1/VCM1: COM1 card type and version TCM2/VCM2: COM2 card type and version TPSP: Power supply type Punkte/STAC • Number of generated data points, and number of points that have been commissioned Configured I/O module points This section gives an overview of all configured I/O data points.
Configured data points without I/O modules This section gives an overview of all configured data points that are not associated with the I/O modules. _____CTYP_______|_DCS____PS_____|_DCS-Number__________________ PBUS | 1 1 | 1 TTY | 3 3 | 1..3 RING | 1 1 | 1 PHON | 1 1 | 1 MC | 15 . | 1..15 SY | 1 . | 1 FL | 6 . | 10, 70, 74..77 RI | 6 . | 1..
• LPS: List of all process stations belonging to this ECU that are configured in the DCS. • ECU: List of all process stations actually detected on the ECU ring. The two lines should normally agree. If, however, process stations are configured in the DCS that are not reported by the ECU, these process stations are automatically tagged as OSV=Yes in the DCS.
2.28.15 MDR, Maximum Demand Load Report The maximum demand load report (MDR) gives the user an overview of: • the major parameters of the respective maximum demand point • all sheddable loads and all connectable energy generators that are assigned to the maximum demand point via the tariff group. • Important: All data displayed are instantaneous values (current values at the time of printing, NOT at the report start time).
Explanation Each entry in the maximum demand program register for the selected tariff group (maximum demand point) is printed out on five lines in the report. Status indication TGRP 1st line Each switch command point is displayed as follows: • Address and system text, possibly suffixed by a status indication. !MD indicates that the corresponding RDO is determined by the maximum demand program. • Parameter RDO; resultant switching command • Parameter ERSTA (if <> .), e.g.
Threshold value 4th line The threshold value is the switch value starting from which (positive) loads are taken offline or energy generators (negative loads) are brought on-line. Both kinds of loads then have the status shed value (= reduced load). Min.Time Threshold=. Explanation: see below. • Marker: !DA indicates that the minimum threshold time has not yet elapsed. Max.Time Threshold=. Explanation: see below. • Marker: !DA indicates that the maximum threshold time has not yet elapsed.
2.28.16 OSR, Optimum Start/Stop Report This report includes all major data of an air-conditioning zone under OSTP control. The data reported by the VISONIK DCS are instantaneous values. During OSTP operation the data is always updated at the start of a heating/cooling phase. The VISONIK DCS indicates old data by an "!". T8 14:59:58 Function=PNT : RPT Rpt.Type=SRPT : OSR Address=ZO'NE'RON1"03: * Masking Param. =.: Output Device =$TT: Insert Form Feed =.: >>o.k.! OSR 15:00:44 R E P O R T - S T A R T 31.07.
Line d) Line e) This line includes; – Time when "Comfort" level was reached. – Effective room temperature. – Room setpoint temperature. This line includes; – Stop time at which the heating plant was switched off. – Room temperature at stop time. – Outside temperature at stop time. 2.28.17 DPR, Data Processing Tables/Graphs Report type DPR provides an operator with a listing of values logged (recorded) in DATA PROCESSING (DPO,GEN) in either tabular or graphic form.
9370Z14E The delayed graphs are transferred to a queue (see DPP,JOBS). Example of a Graph Output on an Operating Terminal The above example illustrates a graph of room and outside temperatures covering the last 15 hours. Siemens Building Technologies Landis & Staefa Division VISONIK DCS Functions and System Messages VVS18 Function RPT CM2U8567E / 04.
Notes on Associated Report DPR 11:11:08 5: 18-Feb-90 11:11 After the report start line a line is printed showing the relative graph number, date and time. A table then follows containing the DP channels which have been plotted in the graph. R E P O R T - S T A R T 18-Feb-90/So (T8) T5 NAME PAR TYPE INT * Format SY Dot ---------------------------------------------------------------------------3 A01'H1'MW"0401 ME INST I30m 1 Even * 0 4 A01'H1'MW"0401 ME INST I05m 1 Symbol .
2.28.18.1 TAB, Display table Example of Table Output on an Operating Terminal T8 14:55:54 Function=PNT : RPT Rpt.Type=SRPT : DPR Format=GRAF : ? 0 GRAF = Graph 1 TAB = Table Format=GRAF : TAB Graph Number=1 : Rounding Setting for Par.Values=-1: from 01.01.1980/Tu 00:00: 01.01.1980/Tu 00:00 upto 14.08.1996/We 14:56: 14.08.1996/We 14:56 Output Device =$TT: Insert Form Feed =.: >>o.k.! DPR 14:57:30 R E P O R T S T A R T 14-Aug-96/We T8 17:15 17:20 17:25 23.07.1996 18:00 18:05 18:10 | | | | | | | 23.07.
Start and Stop Times from 20.06.1996/Th 14:00: ? 20.06.1996/Th 14:00=(dd.mm.yyyy) (hh:mm), (hh:mm), (dd.mm.yyyy), += (-100..100)(Min.,Hour,Day,Mnth), -=( 100..100)(Min.,Hour,Day,Mnth), (-100..100) (Min.,Hour,Day,Mnth), (-100..100), -(Mo,Tu,We,Th,Fr,Sa,Su), (Mo,Tu,We,Th,Fr,Sa,Su), -* , * , . : 20.06.1996/Th 14:00 upto 18.07.1996/Th 14:00: ? 18.07.1996/Th 14:00=(dd.mm.yyyy) (hh:mm), (hh:mm), (dd.mm.yyyy), +=(-100..100)(Min.,Hour,Day,Mnth), -=(-100..100)(Min.,Hour,Day,Mnth), (100..100)(Min.
T8 09:09:07 Function=PNT : RPT,PNX 1. Address Mask=. : $100'000..$100'177 2. Address Mask=. : $100'200..$100'377 3. Address Mask=. : 1. Masking Param.=.: Parameter Value = 2. Masking Param.=.: Parameter Value = 3. Masking Param.=.: CTYP 42=: MW ERSTA 0=O.k.: 1. 2. 3. 4. Operating Param.=.: NAME Operating Param.=.: ERSTA Operating Param.=.: OSV Operating Param.=.: with Status Rpt.=No : with Statistics=Yes : Output Device =$TT: Insert Form Feed =.: >>o.k.! PNX 09:12:43 R E P O R T - S T A R T 1.
Parameter Value Permissible values for the parameter specified immediately above. In the example: CTYP=MW Instead of a fixed parameter value, range definitions and comparison operators as per the following table are permissible: General: Operation and Value or Only Value Operations for Numerical Values (x,y): x(..y) Equals x or within x..y (default) <>x(..y) Does not equal x or outside x..
with Statistics =Yes Example T8 Is a statistics report required, "Yes/No". In the following example a PNX report is requested which will include a status report on the selected Point addresses (with Status Rpt.=Yes). The status indication is displayed at the beginning of the line each case (***, .. etc.). 09:46:35 Function=PNT : RPT,PNX 1. Address Mask=$d2'000...$d254'377: $* 2. Address Mask=$d100'200..$d100'377: . 1. Masking Param.=.: . 1. Operating Param.=.: . with Status Rpt.
OR with ! T8 For an OR operation, enter an exclamation mark "!" before the parameter name. This condition is NOT OBLIGATORY for all of the selected points. 10:01:18 Function=PNT : RPT,PNX " " " " 1. Masking Param.=.: RSUP Parameter Value = No: 2. Masking Param.=.: !OSV Parameter Value = 0: Yes 3. Masking Param.=.: " " " " Explanation The exclamation mark (!) before the parameter OSV indicates that this is an "OR" operation between two or more masking parameters, i.e.
2.28.21 DRPT, Dialogue Report This report type is used internally by the system but is not available to the user. 2.28.22 PMD, Post Mortem Dump The PMD report is used for system diagnostics. The report's contents can be analysed by L&G specialists only. Related functions The PMD report can be accessed in two different ways: • via the function PMD • via RPT, PMD This makes it possible to define a special access level for the PMD report. The reports produced are identical in both cases.
2.28.22.1 Initial Access and Handling Function call-up CTRL/P RPT, PMD As the following example shows, the content of the report can only be analysed by L&G specialists. Excerpt from a report printout; see function PMD for a complete listing. T8 10:49:06 Function=PNT : RPT,PMD Output Device =$TT: Insert Form Feed =.: >>o.k.! PMD 10:49:28 R E P O R T - S T A R T 02.08.1996/Fr T8 344 = Trap 4: odd/non-existent address-reference v14.04.012 01.08.1996/Th 12:44:51 Bclock=31000.
2.28.23 ARPT, Alarm Report In an alarm report, all selected points whose parameter ALconf=Yes are listed in a table.
Selected priority Specification of the selection criterion "message priority", see parameter MSGp. Masking param. A single parameter with its respective value or range of values can be specified as an additional selection criterion. The same rules apply as for the PNX report. General: Operation and Value or Only Value Operations for Numerical Values (x,y): x(..y) Equals x or within x..y (default) <>x(..y) Does not equal x or outside x..
2.28.25 CMB, Message Buffer Report Refer to function CMB,LIST Advantages over CMB function • Output to any terminal (display, printer terminals). • Output to Vtxx terminal with form feed. • Simultaneous STA outputs from several DCS servers. 2.28.26 RRPT, Room Report The room report RRPT covers all TEC rooms, together with the respective TEC devices, which comply with the defined conditions regarding address, parameter name and parameter value.
CM2U8567E / 04.
2.29 SRR Step Reaction Register 2.29.1 Initial Access and Handling Function call-up CTRL/P SRR General A general introduction to the subject of VISONIK reactions can be found under "Reactions in General" in section R of this manual. The step reaction register function (SRR) is one of six reaction types provided by the VISONIK DCS. The reaction types are named after the reason (cause) that activates the reaction in each case.
Example: Step reaction register entry T8 08:50:46 Function=PNT : SRR Operation =CH : Step Flag Addr. =(UA,TA): $F70 Entry =1 : ? Entry =(1..255): Delays after SRR =. : ? Delays after SRR =(1..65000), .: 30 Blocking Flag=. : $F10 Flag Value =Off : ? Flag Value =(&,.,*,-,+=,-=,Off,Step 1,Step 2,Step 3): Off Reaction =(UA,TA): ? UA/TA = Change Point Parameter CT = Printout Cleartext MC = Issue MACRO Command SLVM = Output Slave Message CB = Start/Stop COLBAS Task .
2.29.2.2 Creating a new step reaction register entry Depending on the type of reaction program, the following prompts must be answered in order to create a new reaction register entry: Definition of the "reason" The reason for a step reaction is the Step Flag Addr. All SRR entries having this flag as a reason form steps that will be processed one after another. Step flag addr.
Reaction UA/TA Address of the data point on which the reaction is to act. The following inputs are permissible: • Technical address or $* masks • User address or $* masks • All addresses, including CT to PICT, by entering '..' (???) Parameter Specify the parameter to be modified. Parameter value In the example "Set Digital Output: Priority=0 :" The following possibilities are available for entering the parameter value: • A fixed value is assigned to the selected parameter.
Reaction CB The VISONIK DCS starts/stops one of the available DCS COLBAS tasks. CB Task Mode Number of the COLBAS task whose operation mode is to be modified. Requested operation modes: RUN Stops the COLBAS task if it is active, and starts it at the line number entered. RESTART Starts a COLBAS task only if it is inactive. If the task is active, the instruction is ignored. STOP Stops the task and prints a STOP message. END Stops the task without a message.
Message mask For each reaction entry, the user can use the message mask to define which output devices of the VISONIK DCS are to register the reaction: Message Mask MSGDEV: M1 MM00: M1&M2 : MM15: M1&M2 Message Mask =MSGDEV : ? =MSGDEV : Message Mask =MSGDEV means that the reaction will be registered on the message devices that are listed according to message priority in the parameters DevP0...DevP3 (point type SY) of the point specified under "Reaction=".
Questionable status markers The list of reaction entries can contain so-called "questionable status markers", which have the following meanings: ?FL The blocking flag's value in the reaction entry does not correspond to the flag's current value, i.e. the entry is currently blocked. ?OSV In the Step Flag Addr.(which is responsible for the reaction reason), the OSV parameter is set to "Yes" (out of service). 2.29.3.
2.29.4 DEL, Delete Register Entry(ies) The DEL operation can be used to selectively delete reaction entries. The entries to be deleted can be filtered according to the following criteria: • by Step Flag Addr. • by entry numbers • by reactions If the reaction type CT, MC or CB is entered at the prompt "Reaction=?:", the user can make a finer selection according to text or task number. T8 12:36:31 Function=PNT : SRR Operation =CH : DEL Reason =.. : ? Reason =(UA,TA,...,..
2.29.5 LSTA, List Reaction Register State This provides an overview of all Reaction Registers. T8 12:13:36 Function=PNT : SRR Operation =CH : LSTA Register Total Entries -------------------------------------------------Group Reactions GRR 1 Step Reactions SRR 7 Maintenance Reactions MRR 1 Time Reactions TRR 1 Step Reactions SRR 1 Date Reactions DRR 1 Total 12 Operation =LSTA : 2.29.
Value Reporting 0=Off MSGDEV DSW/Offset = REA. 3 / 0/ 100 76 404 20/ 4 41160 41260 40/ 41 62052 1622 60/ 0 0 0 SRR 12:18:01 End of D A T A - M1 332 25000 10144 41601 131463 0 0 0 0 L I S T 4 12 2 0 1400 100000 0 0 0 0 0 0 30.07.1996/Tu The list may be required by Landis & Staefa for diagnostic purposes. CM2U8567E / 04.
2.30 STAT Statistic Register The Statistic Register is a reserved area in disk memory for depositing any messages from the VISONIK system. This Register's capacity is variable and is sufficient to store specified events, either from the external plant equipment or from VISONIK itself, for a relatively long period. The system is advised in advance which events are to be kept for statistics.
2.30.2 LIST, List Statistic Entries Operation LIST outputs a listing of messages held in the 'Statistics Register' to the operator's terminal or printer. All messages are arranged according to date. Should the system date be set back (with Function DATE) all new buffer messages which overlap other existing entries, because of this set back in time are tagged in the listing with "Retrospective!", placed next to the date.
Message Type =PNT&PCH&ACPT&SLV&REST: ? PNT = Point Messages PCH = Param. Changes ACPT= ACPT Messages SLV = Statistic Slaves CB = COLBAS Message REST= All other Mess. Message Type =PNT&PCH&ACPT&SLV&REST: STA 13:42:43 from: 05-11-95/Su upto: 06-11-95/Mo (Oldest Entry R E P O R T - S T A R T 00:00 13:41 06-11-95/Mo T1 : 31-10-95/Th 05:56) Recorded Date : 05-11-95/Tu .. ST 06:09:03 A02'B5'02"MXD Group 3 lighting ..
Entry without units Operation =LIST : from 31-10-95/Tu 00:00 : ? 31-10-95/Tu 00:00 =(dd-mm-yy) (hh:mm), (hh:mm), (dd-mm-yy), (-100..100) (Min.,Hour ,Day ,Mnth), (-100..100),-(Mo,Tu,We,Th,Fr,Sa,Su),(Mo,Tu,We,Th,Fr,Sa,Su, -*, *, .):-1 from 30-10-95/Mo 00:00 upto 31-10-95/Tu 13:41 : In the above example the system searches the Statistic Register for messages from 30.10.95, 00:00 hours up to the actual present time (31.10.95, 13:41 hours).
2.30.2.2 Message Category With "Message Category" a further condition for selection of statistic messages may be specified. The system lists messages according to the following categories: Message Category=ADDR: ? 0 * = All Messages 1 . = Messages without Addr. or ID No. 2 ADDR = Messages with Addresses Message Category=ADDR: _ "*" '.' NAME Address Mask Description of Message Categories All messages in Statistic Register.
Example with CB Message Category=NAME: Address Mask=$0'000: $177'PS Message Type=PNT&PA&ACPT&SLV&REST: CB Txt.Search (*/%)=: * The search text can be a word segment together with "wild cards" (*/%). Refer to TXIZ/TXCM descriptions. L&S Messages concerning manual (keyboard) parameter changes at L&S Level (8/8 L&S Systems Manager). MSG Only messages with certain MSG numbers. All system messages have an internal octal number, called MSG (Message) number.
2.30.3 LDAT, Review of Messages by Date Operation LDAT provides a review of the number of messages in the Statistic Register. The subtotals are arranged according to date and a grand total is given at the summary end.
2.30.4 LFCO, Review of Fault Condition Messages Operation LFCO provides a listing on the user's terminal or printer which gives a review of 'fault condition' messages held in the statistics register. These messages are tabulated together with the current warning condition (WCON) state marker, related address (ADDR, TA) and the number of related fault condition states (Normal: FCON=0, Fault: FCON=1) during the specified interval, listed in a table.
2.30.5 LIRO, List Messages in Reverse Order Operation LIRO lists the requested number of messages in reverse order, i.e. the most recent message appears at the beginning and the oldest at the end. See Operation LIST for selection of message types. Example The 15 most recent messages shall be listed in groups of five messages in reverse order. Note: Pressing each time at "Number=5:" gives the required required number of five messages per group.
2.30.6 LOCT, List Message Buffer in Octal Operation LOCT provides an octal code listing of messages held in the statistics register. As in Operation LIST messages may also be selected according to Time Interval or Category. Operation LOCT is mainly for diagnostic purposes.
The following example illustrates that for Message Channel 1, there are, 123 messages with MSGP=0 No messages with MSGP=1 45 messages with MSGP=2 32 messages with MSGP=3 1 "Other" message By specifying "Message Channel=1" and "MSGP=3" a message flood to terminal T1 is stopped. Operation =LIST : DEL Message Channel =4: 1 Message Channel =(1..15): 1 (Oldest entry: 19-Feb-95/We 07:41 MSGP : 0 1 2 3 Number : 123 . 45 32 MSGP =0 ? MSGP =(0..
CM2U8567E / 04.
2.31 TRND Trend Plot Dialogue 2.31.1 Initial Access and Handling Function call-up CTRL/P, TRND Function TRND allows parameter values to be graphically plotted as a function of time. The relative parameters are polled and plotted on-line. Parameter values are plotted on the horizontal axis, time is the vertical axis. Scale On colour printers the plot width is always 100 mm. Plot scaling is according to defined values for the left and right margins.
2.31.2 CH, Change Data Entry Operation CH allows new entries to be made or existing ones may be changed. 2.31.2.1 To Specify a New Trend Entry To enter new data the required plot channel is first called up and the relative data specified. T8 09:01:38 Function=PNT : TRND Operation=CH : ? 0 CH = Change Data Entry 1 LI = List Data Registers 2 DEL = Delete Register Entry(ies) Operation=CH : Set=1 : ? Set=(1..16) : 2 Trend Channel=1 : ? Trend Channel=(1..
2.31.2.2 Explanation A user can define up to 16 Trendplot Sets. With parameter $Tn.TSET the required 'Set' is output to the recorder. Sets can be freely exchanged whilst a recorder is active. Trend Channel=1 : 1 Up to 10 channels can be defined per Trendplot Set. Address= $1'04'01: E01'L2'11 At this point, VISONIK prompts for an address. Any point address in the system can be declared as a "Trend point". This prompt is answered by entering either a User (UA) or Technical Address (TA).
Example To plot 3 room temperatures. Desired Trend ranges 15..40, 15..30, 10..30. Plot Channel 1 = 2,5 Deg.C/Cm. Channel 2 = 1,5 Deg.C/Cm. Channel 3 = 2,0 Deg.C/Cm. Entry Channel 1 Value - Left Mar = 15 Value- Right Mar = 40 Channel 2 Value - Left Mar = 15 Value- Right Mar = 30 Channel 3 Value - Left Mar = 10 Value - Right Mar = 30 # 1 1 1 1 2 3 (2.5 Deg.c/cm) (1.5 Deg.c/cm) (2 Deg.c/cm) Deg.c Deg.c Deg.c Deg.c Deg.c Dot Pattern =0 Dot Pattern 0 1 2 3 4 5 6 7 8 Dot Pattern 9370Z28E Deg.
Colour =Black : Red Colour =Black 0 = 1 = 2 = 3 = 4 = Colour =Black There are five colours to choose from for plotting parameters: : : ? Black Red Green Blue Magenta _ Symbol =* A "Dot Pattern" can be overlaid with a symbol. This adds to the clarity in showing and distinguishing between various plotted parameters and overlapping curves. All characters which exist on the terminal keyboard are accepted as plot symbols (numbers, letters, etc.). 2.31.2.
2.31.4 DEL, Delete Register Entry(ies) Operation DEL allows entries to be cleared as follows: ctrl/P T4 15:20:17 Function =PNT : TRND Operation =CH : DEL Set=1: 2 Trend Channel =1: 2 Accept Every Entry =Yes : Set # SY Dot Colour Left Right Unit PAR NAME -------------------------------------------------------------------1 2 A 1 Black 10 Delete Entry =No : YES * * E N T R Y 1 Entries Cleared Description: 100 Deg.
5 5 TICM /Time/cm. =0 MIN: 10 Time scale definition with which the Trend Device shall make the plot. The number of minutes correspond to one centimetre on the paper. This time scale (in minutes) is different according to type of printer (see following remarks). 5 5 TICM /Time/cm. =10 MIN System confirmation of declared time scale. Remark: With the colour option of full graphic printer Fujitsu DX-2100 there is a restricted limit to parameter TICM.
9370Z29E 2.31.5.1 Trend Plot Labelling Set # SY Dot Colour Left Right Unit PAR ADDR = = = = = = = = = = Set Channel number Symbol (overlays the dot pattern) Dot pattern Colour of dot pattern Value of left margin Value of right margin Unit for recorded parameter value Parameter type Address / Point A Trendplot page has 24 lines and is headed with date at the right margin. Then follows, scaling ("Val - Left Mar." and "Val - Right Mar.") once per channel and per page in the relative colour.
Terminal Devices Full graphic plotter DX 2100, DPL-24 (DX 2100 with colour option) Pseudo-graphic plotters LA12/50/100 VT100, VT220 Trend plot with FUJITSU DL1100 GRMO = E8; epson 8-pin GRMO = E24; Epson 24-pin GRMO = . , non-graphic Remarks: – After a power interruption any active Trend Plot on a full graphic terminal must be restarted by setting its parameter $Tn.TICM=0 and again to $Tn.TICM>0.
CM2U8567E / 04.
2.32 TRR Time Reaction Register 2.32.1 Initial Access and Handling Function call-up CTRL/P TRR General A general introduction to the subject of VISONIK reactions can be found under "Reactions in General" in section R of this manual. The time reaction TRR is one of six reaction types provided by the VISONIK DCS. The reaction types are named after the "reason" that activates the reaction in each case.
Example: Time reaction entry T8 Operation 0 1 2 3 4 5 Operation 11:55:17 Function=PNT : TRR =CH : ? CH = Change Data Entry LI = List Data Registers DEL = Delete Register Entry(ies) LSTA = List Reaction Register State LOCT = List Reaction Entries in Octal LDAY = List Daily Entries =CH : Time =00:00 : ? Time =(hh:mm), .: 11:29 Entry =1 : ? Entry =(1..255): 1 Day(s) of Week =-Sa&Su : ? Day(s) of Week =(&,.,*,-,+=,-=,Mo,Tu,We,Th,Fr,Sa,Su): -Sa&Su Special Day =. : ? Special Day =(&,.
2.32.2 CH, Enter/Change Data 2.32.2.1 Changing an existing TRR entry In order to change data in a reaction entry it must first be selected via its "reason" and entry number. If the entry exists, it is listed completely for checking at the operating terminal. The edit mode then becomes active, so that the user can modify or confirm each part of the reaction entry step by step. Important: A reaction entry is not changed (and re-saved) in the system until every step of this dialogue has been completed, i.e.
Special day On of the seven special days (Sd1 to Sd7) can be specified instead of a weekday. See also the "CAL" calendar function. Definition of additional conditions (blocking flag) Blocking flag A flag point with address and value(s) can be assigned to each reaction entry. This blocking flag constitutes an additional condition that must be fulfilled before the reaction is executed.
• RVAL: The resultant setpoint of a switch command RDO or of a flag point RFL is set to the last effective value, e.g. after a power failure. • SAME: When the reaction is triggered, the parameter value of the reaction address is set the SAME as the main value of a selectable data point. The data point can be specified at the "FNT /Address" (???) prompt. • INV: When the reaction is triggered, the parameter value of the reaction address is set to the INVERSE of the main value of a selectable data point.
Reaction PICT Picture number Automatic picture/point selection When the reaction PICT is triggered, the VISONIK DCS automatically displays the selected picture in VISONIK-Insight. The picture is only displayed if VISONIK Insight is free. Otherwise, it is saved until it is opened manually. Specification of the picture to be displayed. In the case of reaction programs whose "reason" is a point change (TRR/SRR), the user can enter an "F" in the reaction entry instead of a fixed picture number.
T8 14:24:32 Function=PNT : TRR Operation =CH : LI Time =* : ? Time =* , (hh:mm)..(hh:mm), (hh:mm), .: * Entry =* : ? Entry =* , (1..255): * Reaction =.. : ? UA/TA = Change Point Parameter CT = Printout Cleartext MC = Issue MACRO Command SLVM = Output Slave Message CB = Start/Stop COLBAS Task . = No Reaction (for MRR & GRR) PICT = Auto Picture/Point Selection Reaction =.. : .. TRR 14:25:15 Start of D A T A 11:00 / 1 Reaction Address Parameter Value Reporting TRR 14:25:15 End of - L I S T 12.08.
2.32.4 DEL, Delete Register Entry(ies) The DEL operation can be used to selectively delete reaction entries. The entries to be deleted can be filtered according to the following criteria: • by a specific time • by a specific time period • by entry numbers • by reactions If the reaction type CT, MC or CB is entered at the prompt "Reaction=?:", the user can make a finer selection according to text or task number. T8 14:36:37 Function=PNT : TRR Operation =CH : DEL Time =* : ? Time =* , (hh:mm)..
2.32.5 LSTA, List Reaction Register State This provides an overview of all Reaction Registers. T8 12:13:36 Function=PNT : TRR Operation =CH : LSTA Register Total Entries -------------------------------------------------Group Reactions GRR 1 Process Reactions PRR 7 Maintenance Reactions MRR 1 Time Reactions TRR 1 Step Reactions SRR 1 Date Reactions DRR 1 Total 12 Operation =LSTA : 2.32.
2.32.7 LDAY, List Daily Entries This provides a listing of Reaction entries referenced to a defined day of the week: T8 14:43:26 Function=PNT : TRR Operation =CH : LTAG Operation =(CH,LI,DEL,LSTA,LOCT,LDAY): LDAY Day(s) of Week =Mo : ? Day(s) of Week =(&,.,*,+=, =,Mo,Tu,We,Th,Fr,Sa,Su,Sd1,Sd2,Sd3,Sd4,Sd5 TRR 14:44:01 Start of D A T A - L I S T 12.08.
An updated Time Reaction is marked in a listing by an exclamation mark ("!"). The time given in this message is the actual time and not the time at which the Reaction should have taken place: !TRR SC 16:40:09 a01'b2'SC SC =OFF--->ON RVAL=ON(1) Summertime/Wintertime Changeover On changeover from summertime to wintertime a double pass is made through the hour between 02:00 a.m. and 03:00 a.m. In this case Time Reactions are only executed during the first pass and suppressed during the second pass.
CM2U8567E / 04.
2.33 TXCM Macro and Cleartext Register 2.33.1 Introduction to the Text Registers Texts are used, for example, in VISONIK-DCS for point indications, system messages, for reports or for operator dialogues. All texts can be configured and can thus be optimally modified to the requirements of a specific project. The texts are stored in the VISONIK-DCS in 16 different text registers Each of these text registers is available in three different languages. 2.33.1.
The following table specifies: • which text registers are available • who is responsible for the maintenance of the associated text register or authorised to make changes. Text catalogue responsibilities Text class L & G, Zug TX,V TX,L TX,Q System text TX,N P: S: N: Q: L: V: Par. short text Sys. short text Sys. normal text Par. long text Sys. long text Very long text Point text TXI, TXI2, TXI3 Units TXU, TXU2, TXU3 Help text TX,S TX,P TX, Ig g1 .. g2031 32 Characters TX, Ug g1 ..
2.33.1.2 Relationship between Text Entries and Parameters The following example of a VISONIK data point indicates which parameters are responsible for the text of the status display. TXIU, Ip TX P S N Q L TXIU, Up TX,Im V System text TX,Um TX,Ig TX,Ug TXCM,C Point text Units Clear text Clear text Reactions and/or parameters TXCR Defined with parameter NAME TXI ME 14:33:21 B2'E1'MW TXU TXI2 Room temp. TXC Room 04 26.3 Deg. C >25 Temp. too high Call service dept. immediately: Tel.
Operations Type of Text=C : C Last Text Change : 18.01.1999 17:15:43 Alfred Gisler Operation=CHNG : ? 0 CHNG = Change in Active Language 1 ALAN = Change in all Languages 2 LCTX = List Changed Text Entries 3 LDIF = List Language Discrepancies 4 COPY = Copy or Move a Textblock 5 LABC = List Entries Alphabetically 6 LIST = List Text Operation=CHNG : 2.33.2.1 Characteristics and Use of the Text Registers Macrotext register TXCM,M No text 'in the normal sense' is entered or edited in the Macro Text Register.
2.33.4 CH, Change in Active Language Operation CH allows new text to be entered and other text to be changed or deleted. Last text change in the clear text register: The last change in the clear text register is marked with a time stamp, which corresponds to the parameters WhenC and WhyC of system point $Sy. 2.33.4.1 Enter New Text To enter new text the required text number is first selected and the desired text entered.
Audible tone The following key combinations can be entered while entering text: – : If this entry is made at the end of a text, the next time the text is called up (e.g., callup of a plant point by a process reaction), a tone will be heard. – : Tabs are set if the key is pressed whereby the value of the tab is fixed at TAB = 8. Note: When using and , the line editor cannot be used.
2.34 TXIU Status & Point Text Registers 2.34.1 Introduction to the Text Registers Texts are used, for example, in VISONIK-DCS for point indications, system messages, for reports or for operator dialogues. All texts can be configured and can thus be optimally modified to the requirements of a specific project. The texts are stored in the VISONIK-DCS in 16 different text registers Each of these text registers is available in three different languages. 2.34.1.
The following table specifies: • which text registers are available • who is responsible for the maintenance of the associated text register or authorised to make changes. Text catalogue responsibilities Text class L & G, Zug TX,V TX,L TX,Q System text TX,N P: S: N: Q: L: V: Par. short text Sys. short text Sys. normal text Par. long text Sys. long text Very long text Point text TXI, TXI2, TXI3 Units TXU, TXU2, TXU3 Help text TX,S TX,P TX, Ig g1 .. g2031 32 Characters TX, Ug g1 ..
2.34.1.2 Identifying the Text Registers In order to be able to unambiguously identify the relation to a specific version or to a specific project, the following rules hold: • Texts 1 to 9 in the TX,lg TX,Im and TXIU,Ip are reserved for the identification of the associated text register. • The identification in TX,lg also holds for TX,Ug TX,Im also holds for TX,Um TXIU,Ip also holds for TXIU,Upand TXCM,C • The text number "0" (g0, m0, p0) does not exist.
Load text disable with XX If Process Station parameter OS.XX=7 is set the DCS cannot load text to the BPS. Associated language Before executing 'LoTx' the associated language should be checked in parameter OS.XX to avoid inadvertently loading text in the wrong language. Text elements which are loaded The following text elements are copied when down loading from a DCS to a BPS.: • All TXI and TXI2 texts which are referenced by the associated BPS.
TXI3 TXU The following is defined in parameter TXI3: – the first text number of the associated TXI catalogue's text value set which relates to the respective main parameters of point classes VIP, AI and AO (FMT=I-array) or – the first text number of the associated TXI catalogue's application-related parameter long text set for PAR1..PAR8 of point type PLT.
Operations Type of Text=Ip Last Text Change Operation=CHNG 0 CHNG = 1 ALAN = 2 LCTX = 3 LDIF = 4 COPY = 5 LABC = 6 LIST = Operation=CHNG : : 19.01.1999 15:38:34 Alfred Gisler : ? Change in Active Language Change in all Languages List Changed Text Entries List Language Discrepancies Copy or Move a Textblock List Entries Alphabetically List Text : 2.34.3 Select or Search for a Specific Text 2.34.3.
Enable with "?" Text search in the Text Register is enabled if a question mark "?" is input against the prompt "Number =1:". It may only necessary to specify a text fragment for searching. The System searches the register for any text which contains the specified text fragment. No difference is made between large or small characters during a search.
Entering status designations Number=157 Up0043= Off : Up0044= 1.Stage : Up0045= 2.Stage : Up0046= 3.Stage : Up0047= ########: : 43 Text entries which indicate various possible states of one point are entered as follows: Such texts which describe the different status of a point must be entered immediately after the other in ascending number order. A group of related status text belonging to a point must be terminated by ######## entered at the next text number following the text sequence.
2.34.5.2 Change Text There are two possibilities for changing an existing text: a) Change the complete text entry. b) Change a text using "Line Editor". Change the Complete Text Entry T8 11:03:22 Function=PNT : TXIU Type of Text=Ip : UP Last Text Change : 19.01.1999 15:38:34 Operation=CHNG : Number=1 : 156 Up0156: Up0157: Explanation Up0156 = kWh: Up0156 = kWh:mA = mA Alfred Gisler After selecting the status text number 156, VISONIK DCS outputs the text associated with this number.
Edit Commands Key / Combination Reaction on Pressing Key(s) Ctrl/B Call up Editor Arrow right Shift 1 character right Arrow left Shift 1 character left Arrow up Shift 1 word right Arrow down Shift 1 word left Delete key
2.34.6 AL, Change in All Languages Operation AL allows text in all languages incorporated in the system to be changed in one single step. Here, the 'Line Editor' can be used as explained in chapter "Change Text". Operation AL simplifies generating the text of a several-language DC Server. In the following example a status text is entered in language 0 (German fixed language, XX=0), in additional language 1 (XX=1, English) and in additional language 2 (XX=2, French).
2.34.8 LD, List Language Discrepancies This Operation enables comparisons to be made between entries in language 0 and those in languages 1 and 2 (if existing). The DC Server merely makes a comparison to see if text actually exists or not. The system makes comparisons to see if, under an entry number (n) in language 0, entries are also filed in 1 and 2. If an empty line is found in an entry number (irrespective of language) the whole entry in all languages are printed out.
ctrl/P 1:T4 15:54:31 Function=PNT: Type of Text=Ip : Last Text change : dd.mm.
2.34.10 LABC, List Entries Alphabetically VISONIK DCS lists the selected text register according to the ASCII alphabetic arrangement (numbers first, then capital letters and finally small letters). Blank entries are suppressed. Example from the TX,lg register: T8 11:35:40 Function=PNT : TXSY Type of Text=P : Ig Operation=CHNG : LABC Ig0019= SPECIAL DAY CATALOGUE SDC Ig0258= Activation Ig0280= Address ($/@) Ig0215= Alarm Report ALR : : : : 2.34.
2.35 VE Verification of Data Files It is practically unavoidable that, at some stage during the operation of a VISONIK System, inconsistent data will occur in the process image and in various program Registers or in the internal memory. The causes of 'corrupted' data can be: – Faulty hardware – Software errors – Unexpected or illegal events of any kind. Inconsistent data as a result of event handling is ignored by the system and, in most cases, can be reconstructed by repetition.
FSG Legend This is identical to Function COS,UTIL,VE (Verify COS pictures). The system verifies COS pictures and Macro libraries for their structural completeness. If an error in structure is found a printout is given containing the relative picture or Macro number and the associated disk block. Wherever possible faulty pictures/Macro libraries are corrected. Finally, illegal entries are reported and cleared.
2.36 XX Change Active Language In VISONIK there are two meanings for "Language". – Message language – Working language Parameter XX The "Message Language" is defined individually for each 'message channel'. All spontaneous messages (e.g. Events, limit violations, etc.) are output to such terminals in the relative message language, irrespective if a user is logged-in or not. Function KEY "Working Language" is defined for each operator in their related Function "KEY" entries.
CM2U8567E / 04.
3 System Messages 3.1 General Notes Each computer system generates SYSTEM MESSAGES which may be generally categorised as follows: 1. Messages concerning the plant's relative operational state, that is messages from the external process. 2. Messages from the Data Communication Server (DCS) about the computer hardware and software, connected peripherals, and other VISONIK components (rings, controllers, modules).
CM2U8567E / 04.
3.2 Event Messages 3.2.1 Structure of a report line All report lines are formatted following the same concept. With the exception of the event time, all the following compilations hold for the point messages also. Scale 0....!....1....!....2....!....3....!....4....!....5....!....6....!....7....!....
Point type dependent information 'M', 'S', 'I' 3.2.2 The following table specifies, dependent on the point type, which parameters are displayed in these fields. Using message suppression $SY,MSGS+=PaNa, the report lines at these positions can be supplemented with the associated parameter names. Using $SY,MSGS-=PaNa the parameter names can be hidden from the report lines.
3.2.2.1 I/O points Point type 'M' Main value 'S' Status 'I' Add'l AI TXU (ERSTA<>0 | OPSTA<>0) {OPMO} AO TXU (ERSTA<>0 | OPSTA<>0) {OPMO} CI TXU (ERSTA<>0 | OPSTA<>0) {OPMO} DI=(TXU) (ERSTA<>0 | OPSTA<>0) {OPMO} For TYP=DO: DO=(TXU) "("Prio")" (ERSTA<>0 | OPSTA<>0) {OPMO} or: FBV=(TXU) "("Prio")" (ERSTA<>0 | OPSTA<>0) lnfoAnalog input For TYP=AI: Analog output For TYP=AO: Counter input For TYP=CI: Digital input For TYP=DI: Digital output 3.2.2.
3.2.2.3 System points Point type 'M' Main value 'S' Status 'I' Add'l info USZU {"(" INR/ABO ")"} (ERSTA<>0 | OPSTA<>0) "Ri"USRI "-"IDC VERS Process Station For TYP=PS: or: " " "T"TY# "-"IDC VERS 1) or: " " "K"MK#"/" 2) Operating system For TYP=OS: CB (ERSTA<>0 | OPSTA<>0) {OPMO} INR AWAY {NOIS} PBDIAG (ERSTA<>0 | OPSTA<>0) {OPMO} NSTA (ERSTA<>0 | OPSTA<>0) {OPMO} Build.
3.2.2.5 DCS points Point type 'M' Main value 'S' Status 'I' Add'l info Multi-level message For TYP=MX: MX {MX2} {MX3} {OPMO} Flag point For TYP=FL: FL=(TXU) {"("FL1act")"} (ERSTA<>0 | OPSTA<>0) {OPMO} or: FL=(TXU) {"("FL2act")"} (ERSTA<>0 | OPSTA<>0) {OPMO} OZ TI "°C" (ERSTA<>0 | OPSTA<>0) {OPMO} For TYP=TY: TY GTYP MK or: TY "K"MCAT ("?"|"O"|"I"|"X"|"f") TA "noise/Rx'ed="m/n OSTP zone For CTYP=OZ: TERM-interface {(ABO)} x("Sec"|"Min") Data Comm.
CM2U8567E / 04.
3.3 Parameter Change Messages Point parameter changes are always reported along with information about the cause of the change. Elements of parameter change messages: HAND ML 10:23:04 C7K8'F13 OSV =JA -->NEIN PRK SC 10:23:04 C7K8'B01 SC =AUS -->EIN1 | v A | v B | v C | v D | v E | v F L&G A.T2 RDO=EIN2(1) | v G | v H | v I | v J | v K | | v v L M where ----> Parameter changes caused by COLBAS do not generate any change messages.
3.3.1 Causes for parameter change reports and terminal assignment HAND Hand: Operator change using a terminal (refer to $S, parameter DEVPCH). PRK Process reaction: Programmable device mask (refer to $S, parameters MM00..MM15 or MSGDEV), or also no message for reaction initiation. DRK Date reaction: Identical to PRK. !DRK Date reaction to "updating": Identical to PRK. KRK Chain reaction: Identical to PRK. SRK Collective reaction: Identical to PRK. WRK Maintenance reaction: Identical to PRK.
FICT Reason for a change in other parameters after a change in the FICT/ Fiktiv parameter. Messages are output on MSGDEV terminals (as for event messages). (Messages are suppressed when the $Sy,MSGS parameter is sent to PaX.) CNC This means a new, general interrogation of a process station (PS) has been started automatically via telephone when the CNC bit (= central not connected) of the PS = 0.
CM2U8567E / 04.
3.4 Sequence and Classification of (Error) Messages Note: The messages described in this handbook are arranged in alphabetical order of the clear text. Generally, messages are split into four format groups. The first five characters of a message line (including spaces) determine the format or group.
There are some messages where a variable value (number or text) may be printed at position "H". Please note the following for all Format A messages: – The messages in this document are in alphabetical order according to the message text. – The notations of "STAP" and "TYP" as well as "NAME" are symbolic placeholders. This means, for example, for STAP the current value of the STAP parameter is displayed; for TYPE, the point type of the address NAME.
3.4.3 Format C : Messages with Short Text Format C messages begin with a short text consisting of 2 to 5 characters. The general structure of the format C messages is as follows: sTXT [PTYP][t]00:00:00 [NAME] [TXI] [TXI2] | | | | | | | v v v v v v v A B C D E F G A .. def, keine .. | v H Short text, dependent on the actual message (possible short texts in place of STXT are e.g., PRK, ZRK, DRK etc.).
CM2U8567E / 04.
3.5 DCS Messages (in alphabetical order) ADDP-checksum-error! OVC=xxx RFC=yyy STAP TYP 00:00:00 NAME ->DEVINI (M.TTAD) ADDP-checksum-error! OVC=xxx RFC=yyy Explanation One of the two system components connected on an ADDP basis (e.g., DCS<-->Insight, DCS<-->Telephony PS, DCS<-->DCS, etc.) breaks off because the transferred data package has not been correctly received. 'xxx' and 'yyy' are counters for correctly (RFC) and incorrectly received data packages (OVC).
ADDP-framing-error! OVC=xxx RFC=yyy STAP TYP 00:00:00 NAME ->DEVINI (M.TTAD) ADDP-framing-error! OVC=xxx RFC=yyy Explanation One of the two system components connected on an ADDP basis (e.g., DCS<-->Insight, DCS<-->Telephony PS, DCS<-->DCS, etc.) breaks off because the transferred data package has not been correctly received. 'xxx' and 'yyy' are counters for correctly (RFC) and incorrectly received data packages (OVC).
ARC=xxx To many Events! (ARCL=yyy/h) STAP TYP 00:00:00 NAME ->DEVINI (M.ARCL) Explanation ARC=xxx To many Events! (ARCL=yyy/h) The meaning of this message is dependent on the TYPE: For TYPE=LS,DI,AI,MX,OZ,PLT,RGB,DO,AO,VIP,CI this message means that, since the last hour change, a larger number of data packages than specified in $S,ARCL=yyy have been received from the process station, namely xxx.
Autogen xxx not yet generated STAP TYP 00:00:00 NAME ->DEVINI Autogen xxx not yet generated (M.AUTOG1) Explanation During the 'SaPa' backup operation, points that are not yet stored in the point database of the DC Server are automatically generated. It is possible that the automatic generation of a point is unsuccessful, e.g., because the database is full. In such cases the message appears and with 'xxx' indicates the point that could not be correctly generated.
autogeneration! PNAM TYP ->DEVINI autogeneration! 00:00:00 TA (M.UGEN) Explanation Points have signalled from a PS that have not yet been generated in the DCS point database. Certain points, however, are automatically generated by the DCS and acknowledged with this message. Action None. Siemens Building Technologies Landis & Staefa Division VISONIK DCS Functions and System Messages VVS18 System Messages --- DCS Messages CM2U8567E / 04.
Backup switch abnormal DIAG TYP 00:00:00 NAME ->MSGDEV Backup switch abnormal (M.MAB) Explanation The test for automatic back-up changeover (initiated through the SHAD=mABA parameter in system point $S) has been interrupted because of a changeover failure. Action Check the front control panel switch and ensure it is in the "Automatic" position. CM2U8567E / 04.
Bad Application Sequence by xxx 00:00:00 NAME ->DEVINI (M.APER) Explanation Bad Application Sequence by xxx y.zzz) (By= bb rxF= rr txF= tt) (Err= There is a special transfer tool available for exchanging data between a VISONIK DC Server and process stations and partly between partner DC Servers (link systems). This message should assist in localising application errors in this transport tool. As a rule, an application related message is also generated, which shows the behaviour of the error.
bad DISC transfer on unit xx and by block yyyy STAP TYP 00:00:00 NAME ->DEVINI (M.DISC) bad DISC transfer on unit block yyyy xx and by Explanation A disk operation (read or write) cannot be carried out. "xx" indicates the disk unit (0 = system disk, 1 = shadow disk) and "yyy" indicates the corrupted disk block (in octal). Action Upon repeated occurrence of this error, the disk must be reformatted or even exchanged. Note: VISONIK programs require a fault-free hard drive.
CBIF/CER1=vv/xx Beacon PS=yy NOIS=zz STAP TYP 00:00:00 NAME ->MSGDEV CBIF/CER1=vv/xx Beacon PS=yy NOIS=zz (M.COC) Explanation A PRV/BPS/EKL-X controller has the capability of detecting and counting "noise". All noisy data frames originating on the ring BEFORE the location of this process station causes its noise counter to increment. Should an EKL receive "Beacon" signals from the process station preceding it on the ring, it can store the number of this process station.
CB Task xx status AT LINE yy STXT 00:00:00 ->MSGDEV (M.RXCB) CB Task xx status AT LINE yy Explanation This message is generated by that reaction program printed at message position KTXT. The message shows that COLBAS Task "xx" has either been started or stopped (indicated by "status" by the associated reason). When the task is started, the relevant line number is printed at position "yy". Action None. This is a normal task message. CM2U8567E / 04.
Change of Port A: x---> y STAP TYP 00:00:00 NAME ->MSGDEV Change of Port A: x---> y (M.RPOA) Explanation The status of SDLC Ring Controller's port A has changed. This is normal during the phase of connecting an EKL process station to the ring after a system start or, more generally, after initialising a ring. The message appears only in severe diagnostics mode ($S,TRBI=200). Action None. However, should the message appear frequently, then the ring must be checked.
Chip loop at xxx ,contact L & S STAP TYP 00:00:00 NAME ->MSGDEV Chip loop at xxx ,contact L & S (M.RDCL) Explanation Data exchange with the SDLC chip of ring NAME cannot be terminated within the maximum allowed number of attempts. (100 attempts is approximately equal to 2 msec depending on computer type.) The chip is reset automatically and a functional check on the SKLC ring controller is carried out. If the controller is defective, the associated status change of ring NAME is reported.
Communication Error while xxx DIAG 00:00:00 NAME ->DEVINI (M.COER) Explanation Communication Error while xxx (Err= y.zzz) (By= bb rxF= rr txF= tt) A special transfer tool is available for exchanging data between a VISONIK server and process stations and partly between partner systems (link system). This message should assist in localising communications problems between partners. As a rule, a related message is simultaneously generated which shows the behaviour of the error.
CONTAINS 2 MASTERS, A/C=xxx STAP TYP 00:00:00 NAME ->MSGDEV CONTAINS 2 MASTERS, A/C=xxx (M.RD2M) Explanation Ring NAME is in "Master" mode and has received a control telegram xxx to all process stations which was not previously sent by this master. Control telegrams can only be sent by master stations. Thus the above message is an indication that there must be another master somewhere on the same ring.
content destroyed: xxx/yyy zzz STAP TYP 00:00:00 NAME ->MSGDEV content destroyed: xxx/yyy zzz (M.CODE) Message example *** Content destroyed *** Content destroyed *** Content destroyed Explanation 352/ 347 3400/ 4767 12700/ 13737 163400 < 12372 < 341 < Bad content Bad content Bad content A part of the VISONIK DC Server, the PRINCESS Operating System, is main memory resident and cyclically checked.
Controller bad IR result=xx STAP TYP 00:00:00 NAME ->MSGDEV Controller bad IR result=xx (M.RDUI) Explanation The SDLC chip of the ring NAME has generated an interrupt on the receive side, but this type of interrupt "xx" is unknown or totally inappropriate at the moment. Another possible cause may be that there are two SDLC controllers with the same hardware address in the computer. This message is also output if the bus is incorrectly structured, e.g., with the expansion box (xx=16=DMA underrun).
CTR.TEST: RL/Offset=xxx RDO/RFL=yyy IT=zzz STAP TYP 00:00:00 NAME ->MSGDEV (M.RDLB) Explanation CTR.TEST: RL/Offset=xxx RDO/RFL=yyy IT=zzz A ring controller test consists of first transmitting a telegram. Then before the test telegram is transmitted, the output of the controller is looped back to its input. This means that the transmitted data will be again received by the controller. This looping takes place within the SDLC chip itself.
CTYP=ctype ---> Wrong Point Type PTYP 00:00:00 NAME ->DEVINI (M.TYF) CTYP=ctype ---> Wrong Point Type Explanation The point with NAME (or rather, where available, the point with a TA) transmits an event to the system. If, in the DC Server, a point with another type is generated at this address, a message occurs. If, as yet, no point has been generated in the DC Server at this address, then this message is output if the $S,TRBI=200 diagnostic is switched on.
CTYP/PAR: ComReset started PKG TYP 00:00:00 NAME ->DEVINI CTYP/PAR: ComReset started (M.PSRS) Explanation After loading a new point configuration in a BPS, especially points having interface definitions like, e.g., FLN point, CO point, TERM point, etc., you have to possibly carry out a station RESET in order to actively set the configuration.
CTYP/PAR: ComReset started PACH TYP 00:00:00 NAME ->DEVINI CTYP/PAR: ComReset started (M.PSRS) Explanation After loading a new point configuration in a BPS, especially points having interface definitions like, e.g., FLN point, CO point, TERM point, etc., you have to possibly carry out a station RESET in order to actively set the configuration.
CTYP=xxx autogeneration! PNAM TYP 00:00:00 TA ->DEVINI (M.UGEN) CTYP=xxx autogeneration! Explanation Points have signalled from a PS that have not yet been generated in the DCS point database. Certain points, however, are automatically generated by the DCS and acknowledged with this message. Action None. Siemens Building Technologies Landis & Staefa Division VISONIK DCS Functions and System Messages VVS18 System Messages --- DCS Messages CM2U8567E / 04.
CYX: SP guard raised the alarm SP=.. SP+2=.. SP+4=.. ERR TYP 00:00:00 NAME ->MSGDEV (M.SPGA) CYX: SP guard raised the alarm SP+2=.. SP+4=.. Explanation Stack overflow. Action Please send a copy of the message to Landis & Staefa FS&PM. CM2U8567E / 04.1999 3-38 VISONIK DCS Functions and System Messages VVS18 System Messages --- DCS Messages SP=..
CYX xxx seconds sleeping!! TIX 00:00:00 ->DEVINI (M.CYX) CYX xxx seconds sleeping!! Explanation The program CYX (CYclic eXecutive), which controls and checks all cyclic actions has stopped for more than xxx seconds or is running in a never-ending program loop. Action If this occurs repeatedly, please contact Landis & Staefa Service. Notes for L & S: – Print the status of all procedures with SER, LPROC.
Defective 'Set OS' Sequence STAP TYP 00:00:00 NAME ->MSGDEV Defective 'Set OS' Sequence (M.SQER) Explanation The main parameter OS in a VISONIK DC Server can be changed from PRV/BPS/EKL X, in that a command string is written to TSKTTY=255. The syntax of the string must correspond to that used in Ctrl/V mode. Example O=Gacq&Eacq The VISONIK DC Server analyses this command string. If a syntax error is found, the above error message is output. Action Check the command string in the EKL.
Diag xx = yy [at line zz] TSKx 00:00:00 ->MSGDEV (M.CBDG) Diag xx = yy [at line zz] Explanation [at line zz] does not always appear. An active COLBAS task has made an illegal process image access (e.g., due to incorrect programming). Illegal process image accesses could be: – Access to unknown (e.g., not generated) points – Access to an unknown parameter. If the system variable SYSDIAG=1, a diagnostic message is output where TSLx is the COLBAS task no.
DMA@:WRITE/READ dismatch xx yy zz aa STAP TYP 00:00:00 NAME ->MSGDEV DMA@:WRITE/READ dismatch xx yy zz aa (M.RDMA) Explanation If there are any irregularities in data traffic with an SDLC ring controller, its DMA register is checked by writing the value xx to the register and then reading value yy from the register. If xx and yy are not the same, the DMA chip is faulty. Action Replace the SDLC ring controller even if the message only appears intermittently.
Ennn=vvvv! uuuu.xxxx, box@=zzzz PNAM 00:00:00 ->MSGDEV (M.xMER) Ennn=vvvv! Explanation uuuu nnn vvvv xxxx zzzz uuuu.xxxx, box@=zzzz represents one of the following file names: uuuu=IM Process image uuuu=DM Data processing uuuu=REA Reaction register is an error number. is one of the error number's related texts. specifies the segment number of the uuuu file in which the error occurred. specifies the relative offset in the segment xxxx where the error has been detected.
Action In all cases contact Landis & Staefa FS&PM, providing as much information as possible about the system behaviour during the ten minutes before this error message appeared. If this error repeats, try VE,IM or VE,REA or VE,DM. Group B These messages appear whenever the reserved disk space has been fully used up by the process image, and further data points still have to be generated. This message can also be falsely printed if the DC Server is heavily overloaded.
Entry Date/Entry: xxx > yyy End reached - Entry Erased DRK 00:00:00 ->MSGDEV (M.REND) Entry Date/Entry: xxx > yyy End reached Entry Erased Explanation Date reaction (DRK) entries can be limited in time either by specifying a definite end time (yyy) or by the number of times (zzz) the associated entry is to be executed. On reaching such an end time, the entry is automatically deleted. The message appears as a note and indicates the DRK entry with "DATE/ENTRY". Action None.
Entry Date/Entry: zzz mal okay End reached - ....... DRK 00:00:00 ->MSGDEV (M.REND) Entry Date/Entry: zzz mal okay End reached - Entry Erased (datum/xx) Explanation Date reaction (DRK) entries can be limited in time either by specifying a definite end time (yyy) or by the number of times (zzz) the associated entry is to be executed. On reaching such an end time, the entry is automatically deleted. The message appears as a note and indicates the DRK entry with "DATE/ENTRY". Action None.
Err=.. / CSC=.. / Call@=.. /Msg Spec=.. TYPE ->Tn 00:00:00 (M.TYER) Explanation Err=.. / CSC=.. / Call@=.. /Msg Spec=.. This message can have two sources, namely: – Incorrectly formatted message – Printout of old statistic entries that are no longer supported by the VISONIK DCS Software. Action To be rectified by Landis & Staefa Central Systems.
Fault msg. fr. PS yyy PNAM PTYP 00:00:00 NAME ->DEVINI (M.ATR4) Explanation and Action Fault msg fr. PS yyy If the EKL X/PRV/BPS receives faulty data from the VISONIK DC server, it can inform the Server of this by sending the above message with a specific text yyy (cause of the error). If the severe diagnostics is run at the DC Server ($S,TRBI=200 or 1000), the following messages are output to terminals as specified in the DEVINI mask. Cause Action 0: Attribute Error 0 --Should never occur.
from Date xxh (+yyh) in Serv. WRR PTYP 00:00:00 NAME [TXI] [TXI2] ->MSGDEV from Date xxh (+yyh) in Serv. (M.WRT) Explanation An entry in the Service Reaction Catalogue WRK either has reached the previously entered date or the previously entered number of operating hours of the point 'NAME'. From now on, the message is always repeated after a date change (midnight) insofar that the counter is not reset, and indicates with 'xx' the operating hours since 'DATE'.
FSG data overflow: space= xxx length= yyy STAP TYP 00:00:00 NAME ->DEVINI (M.FSX1) Explanation FSG data overflow: space= xxx length= yyy The picture (or MACRO library) edited with VISONIK Insight cannot be saved to the DC Server, because it, along with possibly defined dynamic channels, is too large. "SPACE" indicates the available memory, while "LENGTH" is the file length to be saved. Using the FSG,FSG operation "DIR", the space required by all pictures can be printed out.
FSG sequence or link error: PIC/MAC # xxx list ..... STAP TYP 00:00:00 NAME ->DEVINI (M.FSX2) FSG sequence or link error: PIC/MAC # xxx list #= yyy block #= zzz Explanation The data sequence of a picture transferred from Insight to VISONIK has been interrupted; the system cannot save the picture. xxx indicates the picture/macro number, yyy the list number and zzz the block number. Action Save the picture again. If unsuccessful, consult the Landis & Staefa project manager or Service.
GRAF: xxx [Error Text] STAP TYP 00:00:00 NAME ->MSGDEV GRAF: xxx [Error Text] (M.FSX3) Explanation Cause Action Cause Action Cause Action Cause Action Cause Action Cause Action This error message appears with a different error text if an error occurs during the output of a DPP graph (xxx) on a display terminal with the address NAME or upon accessing a DPP graph.
Cause Action Cause Action Cause Action [10] Sys.: DAP entry not OK (DC Server link) The DAPRO channel with a third-party address is not defined in the third-party system. Check DAPRO channel and adapt accordingly. [11] Sys.: Compare DAP time range (DC Server link) The x-axis time range defined for the current graph is questionable for the DAPRO channel in the third-party system. Adjust time range accordingly. [12] Sys.
IDC = vvv --> xx => zz STAP TYP 00:00:00 NAME ->MSGDEV (M.MDCH) IDC = vvv --> xx => zz Explanation Module change detected at the PS. The old module (IDC=vv) was replaced by the new module (IDC=xx). The following holds for 'zz': 0: In operation 1: No hardware 2: No module 3: SW change 4: Module error 5: HW IDC = ?? Action Plug in the correct module type or delete the old module points and then generate the appropriate new module type. Note Ensure the wiring is correct.
(IDC=xx) not allowed PS as MCUS! ERR TYP 00:00:00 NAME ->DEVINI (IDC=xx) not allowed PS as MCUS! (M.MACL) Explanation A process station (PS) can be identified as a "Master Clock" in the $Sy system point using the MCPS parameter. This PS is then checks and, if necessary, corrects the clock of the VISONIK DC Servers and thus the system time via its internal quartz clock.
Illegal frame,RO=xxx DL,... = y01 y02 y03 y04 ....... PNAM PTYP 00:00:00 NAME ->DEVINI (M.IFMT) Explanation Illegal frame,RO=xxx DL,... = y01 y02 y03 y04 y05 y06 07 y08 y09 y10 A telegram has been received by the VISONIK DC Server via a ring or V.24 that cannot be processed and is therefore ignored. The cause of such telegrams may be classified according to the RO value xxx: RO=100..177 Problems with link system or FBS RO=200..277 Illegal addresses RO=300..377 Problems with v300 data RO=400..
Incorrect receiver address. This can occur, for example if a process station reports with address $377. This case can arise if an EKL's address matrix card is incorrectly programmed. It should be noted that for all the messages described, additional diagnostics data will be printed out if severe diagnostic is enabled with $S,TRBI=200/1000. In the example where RO=104, the following additional diagnostics data would be printed out: TCR3 hh:mm:ss ER31: illegal frame Actual SECCNT= 14713 BB.FG BB.FG2 BB.BL BB.
illegal LIST /PIC # xxx/yyy STAP TYP 00:00:00 NAME ->DEVINI illegal LIST /PIC # xxx/yyy (M.FSX4) Explanation A picture request from VISONIK Insight to the system does not function. The VISONIK DC Server cannot form a picture number from the list number received. xxx indicates the list number, and yyy the picture number. Action Restart Insight Should this fault occur repeatedly, please consult the Landis & Staefa Service Department. CM2U8567E / 04.
Illegal RESET of the SDLC chip, DMA=xx STAP TYP 00:00:00 NAME ->MSGDEV (M.RDRS) Illegal RESET of the SDLC chip, DMA=xx Explanation Although no SDLC chip reset has been received from NAME Ring, the "Request to send" signal no longer exists. This would indicate a reset produced by faulty hardware. The message is quite normal after a computer changeover from A -> B. It appears only under severe diagnostics ($S,TRBI=1000).
Invalid MXD Entry! Start “VE” PNAM TYP 00:00:00 NAME ->DEVINI Invalid MXD Entry! Start “VE” (M.ILSP) Explanation As a result of some manipulation on the DC Server, e.g., deleting a data point, an entry in the LSP (peak demand limiting) catalogue was rendered "incorrect" or meaningless. Action The "VE,LSP" operation verifies all entries in the LSP catalogue and automatically removes any "incorrect" blocks. CM2U8567E / 04.
LoTx working with Language xx=n LoTx working with Language xx=n (M.ACXX) STAP TYP 00:00:00 NAME ->DEVINI Explanation When the backup operation is started, LoTx is notified in which language 'n' the text was loaded. On a PS basis, the language can be configured in the relevant OS point via the XX parameter. This message only appears if the PS diagnostic (parameter DIAG in the PS point) is switched on. Action None.
LS=vv[TXU]; ERSTA xx Min; ONLM/OFLM ....... LSP TYP 00:00:00 NAME -> (M.LIMT) Explanation LS=vv[TXU]; ERSTA xx Min; ONLM/OFLM : xx/yy[ TXU]; GLAS=zz[TXLSU]; EABS=aa The messages appear at the terminals that are defined in the DEVLS parameter of the LS point. This (calculation) message is a diagnostic message and allows monitoring the peak demand program for a specified time at the end of each period. The messages only appear if the parameter LSCM <> 0 (i.e., is unequal to zero) in the LS Point NAME.
LS=vv [TXU] (xx[TXLSU]) ; GLAS= yy[TXLSU];..... STAP LS 00:00:00 NAME -> (M.SYM) Explanation LS=vv [TXU] (xx[TXLSU]) ; GLAS= yy[TXLSU];EMAX= zz[TXU][?STN] The messages appear on the terminals that are defined in the DEVLS parameter of the LS point. This concluding message is printed following conclusion of a period of the peak demand program. If the message ends with ?SYN, then this event is absent and, after a delay, the peak demand program has simulated the missing synchronisation event.
*Macq* Mtxx: DATE TIME text STAP TYP 00:00:00 NAME ->MSGDEV *Macq* Mtxx: DATE TIME text (M.MTxx) Explanation Messages in the message buffer of a PS can be transferred to the DCS and stored in the ZMS cyclic message memory using the MACQ backup operation (= message acquisition). (For more detailed information about the PS message buffer, see the "System Handbook EKL X and PRV" or "System Handbook BPS"). The time point of message acquisition is indicated in the PS with 'DATUM UHRZEIT' (date-time).
MODEM "Clear To Send" missing STAP TYP 00:00:00 NAME ->MSGDEV MODEM "Clear To Send" missing (M.RDCS) Explanation In Ring NAME the "Clear to send" signal is missing in the modem section of the SDLC controller. We distinguish between two different types of Ring controllers: FSK Here the cause may be a fault in the Ring controller's transmitter section, or a short circuit at the controller's transmit output line. V.
MODEM "Data Set Ready" missing STAP TYP 00:00:00 NAME ->MSGDEV MODEM "Data Set Ready" missing (M.RDMD) Explanation In Ring NAME there is no "Data set ready" signal from the modem to the controller (this is a V.24 signal only). Either the modem is really busy or the associated jumper on the Connection Unit is missing. Action Check and correctly set the jumper on the Ring Connection Unit. Otherwise, replace the controller. CM2U8567E / 04.
Modemklasse $xx'PS activ for more than ....... DIAG TYP 00:00:00 NAME ->MSGDEV (M.TYML) Modemklasse $xx'PS activ for more than y Min R0=z Explanation This warning message appears cyclically if a connection exceeds a certain time. 'y' indicates the time of the connection in minutes, while the number 'z' indicates the reason for making the connection. Action If a status is desired, none. Otherwise abort the connection using the $x.O = DISC command.
multiple PS# xx STAP TYP 00:00:00 NAME ->MSGDEV multiple PS# xx (M.RWUD) Explanation The "RING" program has received two successive telegrams from Ring NAME containing the same process station number. This means that either a PS has illegally sent two successive telegrams (PS fault), or two process stations are transmitting with the same number xx. (Incorrect coding or bad contacts in the relative address matrix card.) Action If this occurs only occasionally in a DC Server link, ignore it.
No Access to File No. #xxx STAP TYP 00:00:00 NAME ->DEVINI (M.FMIS) Explanation No Access to File No. #xxx The 'SaFi', 'LoFi', 'SaTi', 'LoTi', etc. backup operations need a backup file. This backup file (i.e., the file number) is entered with the FILE parameter (FILE parameter in point type PS). This message appears if nothing can be accessed from the file xxx. Action Enter file number or check.
noise after PS x and before PS y STAP TYP 00:00:00 NAME ->MSGDEV (M.RNOI) Explanation noise after PS x and before PS y Transmissions on the NAME Ring have interference. The interference source can lie between PS x and y, i.e., the fault either lies with the transmitter of PS x, along the intermediate communications path or with the receiver of PS y. "Master" appears instead of PS x or PS y if the system includes the master section.
noise after master and before master STAP TYP 00:00:00 NAME ->MSGDEV (M.RNOI) Explanation noise after master and before master Transmissions on the NAME Ring have interference. The interference source can lie between PS x and y, i.e., the fault either lies with the transmitter of PS x, along the intermediate communications path or with the receiver of PS y. "Master" appears instead of PS x or PS y if the system includes the master section.
no more dataprocessing point! DP3 TYP 00:00:00 NAME ->DEVINI no more dataprocessing point! (M.DPEND) Explanation The memory location of the 'NAME' point was deleted and, as a result, data logging automatically deleted the internal identification within the point. This action is reported. Action None. CM2U8567E / 04.
NOT EXISTENT! R1=xx R2=yy PNAM 00:00:00 NAME ->DEVINI (M.TAF) NOT EXISTENT! R1=xx R2=yy Explanation On accessing the process image, the given program cannot find the ADDR point. Further possible details can be found by checking the contents of registers R1 and R2. Depending on the program (PNAM), the following two causes are possibilities: – An event has occurred at a remote point which has not yet been generated in the DC Server. – A point address has been entered in a catalogue (e.g.
Nr(RX) Ns(TX), USDA=.. Rx C=.. Tx C=.. STAP TYP 00:00:00 NAME ->MSGDEV Nr(RX) Ns(TX), USDA=.. Rx C=.. Tx C=.. (M.RUST) Explanation Normal telegrams that are transmitted between the DC Server and each process station on the ring are provided with two sequence number, Ns and Nr. These numbers are the main components of telegram acknowledgement between "receiver" and "sender". Due to these numbers a distinction can be made between real repetition in cases of corrupted data and simply duplicated data.
Nr(USDA) Ns(Rx), USDA=yy Rx C=zz STAP TYP 00:00:00 NAME ->MSGDEV Nr(USDA) Ns(Rx), USDA=yy Rx C=zz (M.RUSE) Explanation Normal telegrams that are transmitted between the DC Server and each process station on the ring are provided with two sequence number, Ns and Nr. These numbers are the main components of telegram acknowledgement between "receiver" and "sender". Due to these numbers a distinction can be made between real repetition in cases of corrupted data and simply duplicated data.
operator NAME Patch# xx Disk Device: ...... PAT operator NAME Patch# xx Disk Device: (M.PACO) file NAME/disc block: yy Corr. -> checksum SYSA# 00:00:00 ->DEVLOG+STA! Explanation This message shows when, where and who made a "patch" using the PAT function. – operator name is the name of the person who made the patch – yy is the number of changed values – SYSA is the terminal address from where the patch was made (e.g., S1:B.T1) Action None. For information only. CM2U8567E / 04.
OSTP: exp. period to OCC xx>=yyh DIAG TYP 00:00:00 NAME ->MSGDEV OSTP: exp. period to OCC xx>=yyh (M.OTHT) Explanation The pre-heating or pre-cooling time calculated by OSTP for the NAME zone, displayed in xx hours, exceeds yy hours. Such an excessive action time is interpreted by OSTP as "impossible", i.e., it must have occurred as a result of either a defect in the plant or in the measured values (see possible reasons below). The heating and cooling zone constants are constantly being optimised.
Overflow in File No. #xx yyy STAP TYP 00:00:00 NAME ->DEVINI Overflow in File No. #xx yyy (M.DXEF) Explanation While saving PS data during a 'SaFi', 'SaTi', etc. backup operation, it was determined that the backup file 'xx' of the PS 'NAME' was too small. Additional diagnostic data are possibly added with 'yyy' (By, rxF, txF). Action Link file 'xx' with the xxx+1 file (EDI,LINK,...) and restart the backup operation. CM2U8567E / 04.
PAR MOM/WITH/eMIT LIN/ZIRK Interval text DP3 TYP 00:00:00 NAME ->DEVINI PAR MOM/WITH/eMIT LIN/ZIRK Interval text (M.DPER) Explanation This message appears upon time jumps of the system time and warns of possible data loss in the data memory. Reading 'text' provides a more detailed explanation of the causes. Depending on the size of the time jump, the following texts can appear: Forward/Backward time jump: Small time jumps (< 2 hours) are marked with this 'text'.
PBus Modul : mxx text STAP TYP 00:00:00 NAME ->DEVINI PBus Modul : mxx text (M.PBER) Explanation The PS 'NAME" reports an error on the PBus module 'xx'. The cause of the error is described with 'text': No module Hardware error Address error No module in place is handled like an error. Action Check the associated module (contacts, address-key, etc.), and replace if necessary. CM2U8567E / 04.
PBus Module : mxx yyy Operational STAP TYP 00:00:00 NAME ->DEVINI PBus Module : mxx yyy Operational (M.PBOK) Explanation The PS 'NAME" reports which 'yyy' module is inserted and operational at address 'xx'. Action None Siemens Building Technologies Landis & Staefa Division VISONIK DCS Functions and System Messages VVS18 System Messages --- DCS Messages CM2U8567E / 04.
PHONE: partner couldn't reach me: NAME STAP TYP 00:00:00 NAME ->MSGDEV (M.LOCK) PHONE: partner couldn't reach me: NAME Explanation The given Tele PS has attempted to call the system without success. Action Check the modem link with a test call (Tele PS to DC Server). CM2U8567E / 04.
PSER1..3=vv/ww/xx INR=y.Ori=z STAP TYP 00:00:00 NAME ->MSGDEV PSER1..3=vv/ww/xx INR=y.Ori=z (M.USE) Explanation This message is normal under severe diagnostics ($SY,TRBI=...) and intended for L & S use. For questionable PS status change messages, this auxiliary message allows deciding whether an error exists at the DC Server or at the PS. Action None. Message is normal under severe diagnostics.
PS# xxx DMAL=yyy RL=zzz Frame: www ...... STAP TYP 00:00:00 NAME ->MSGDEV (M.RUDL) Explanation PS# xxx DMAL=yyy RL=zzz Frame: www .. RC=vvv The system identifies the length of received telegrams using three sources: 1) The number of bytes that were transferred by DMA (yyy). 2) The number of bytes that were received by the SDLC chip (zzz). 3) Through the first byte transmitted www. (Only meaningful if yyy and zzz are greater than zero.
[Error Text] R1=xxx STAP TYP 00:00:00 $Tx ->MSGDEV [Error Text] R1=xxx (M.TTER) Explanation (Error Text: a,b,c,d,e and f) These messages are generated by the COM driver. The error text is taken from the V0900 array. a) "Receiver Buffer Overflowed" – An escape sequence could no longer be received because the receive buffer was full. ---> The receive buffer contents were deleted. With "TYX+=Diag" the entire receive buffer is first printed out. b) "Illegal Escape Sequence" – Can happen for V.
REAK=xxx -> RDO/RFL=yyy (z) $FLn/c KTXT PTYP 00:00:00 NAME ->MSGDEV REAK=xxx -> RDO/RFL=yyy (z) $FLn/c (M.RXSO) Explanation These messages appear during execution of switch-on sequences when mains power returns. The sequences are programmed as KRK chain reactions and mainly hold switching commands needed to reinstate drop outs resulting from a mains failure. Upon return of the mains, orderly switch-ons have to be carried out, perhaps with delays in order to avoid undesirable peaks in demand.
Reason/Entry: xxx/yyy zzz KTXT 00:00:00 ->DEVINI (M.RDEF) Reason/Entry: xxx/yyy zzz Initiated by: All reaction programs, that is: SRK, PRK, ZRK, DRK, KRK, WRK, Explanation Through some action the reaction entries have been rendered meaningless (e.g., points which are causes of PRKs have been deleted, but the associated reaction entries still exist, etc.) Such reactions can no longer be executed.
receiver carrier disappeared STAP TYP 00:00:00 NAME ->MSGDEV receiver carrier disappeared (M.RDRC) Explanation The receiver of the NAME ring suddenly no longer receives a carrier signal. Possible causes are: – Sudden Ring break between the last process station and the DC Server. – Loose contact along the link (e.g., EKL base terminals). – Faulty Ring relay in the last process station (contact problem). – Faulty address key (hardware) in the last process station on the ring or contact problem.
receiver DMA overrun STAP TYP 00:00:00 NAME ->MSGDEV receiver DMA overrun (M.RDOV) Explanation The data received from the SDLC controller of the Ring NAME has not been fetched fast enough from the DMA chip. Action If this situation occurs repeatedly, either the DMA chip or the entire SDLC controller must be replaced. Siemens Building Technologies Landis & Staefa Division VISONIK DCS Functions and System Messages VVS18 System Messages --- DCS Messages CM2U8567E / 04.
receiver interrupt overrun STAP TYP 00:00:00 NAME ->MSGDEV receiver interrupt overrun (M.RIOV) Explanation Before the VISONIK CPU can process an existing interrupt, a new interrupt from the Ring Controller NAME has appeared. This message is normal if using the ODT (Online Debugging Trace) utility program. The analogue situation in a substation is reported with the additional information "Rx slow". Action If this occurs repeatedly, please send the printout to Landis & Staefa FS&PM. CM2U8567E / 04.
RING# a-->b ;$vvv->$xxx->$nnn RING# a-->b STAP TYP 00:00:00 NAME ->DEVINI (M.RNER) Explanation ;$vvv->$xxx->$nnn The system "sees" a process station xxx, which is not defined in any Ring (see Pro,GPR). The "a" stands for "old Ring" (usually 0), while "b" is the "new Ring" (usually >0). After the semicolon there follows an extract from the Ring sequence. vvv is the PS BEFORE xxx, and nnn is the PS AFTER xxx. Process stations having the illegal numbers 0 or 377 are shown with number 377.
Rx DMA overflow after xxx bytes, DL= yyy STAP TYP 00:00:00 NAME ->MSGDEV (M.ROFL) Rx DMA overflow after xxx bytes, DL= yyy Explanation The Ring NAME has received a telegram of length xxx. This length, however, exceeds the available memory space yyy. The telegram sender, in this case a process station, cannot, however, be determined. Action Ignore if this occurs only occasionally. If it appears continuously, the data from a Ring Trace must be examined by L & S Project Management Service.
Rx Interrupt missed, xx STAP TYP 00:00:00 NAME ->MSGDEV yy zz Rx Interrupt missed, xx yy zz (M.RWIT) Explanation The controller of the Ring NAME has not generated an expected interrupt within the permissible time limit. Values xx, yy and zz can be used (by L & S) to determine the Ring state at the time. This a normal message for a Ring break and is printed out under severe diagnostics ($SY,TRBI=...). Action No action if the Ring is disturbed.
$x Rx: y STAP TYP ->MSGDEV z 00:00:00 NAME $x Rx: y z (M.TYMA) Explanation This message appears if the given modem NAME cannot immediately make a connection to the Tele PS=x. Here, y contains the received character sequence and z the value of the signal in accordance with the description of the DHV11 or DHQ11 or CQ1620 card. Action If this message appears often, the modem should be checked. CM2U8567E / 04.
SaTx Invalid Text ID=xx STAP TYP 00:00:00 NAME ->DEVINI (M.PSTX) SaTx Invalid Text ID=xx Explanation During execution of the 'SaTx' backup operation, an unknown text identifier 'xx' was received. The text was not saved. Action Locate the unknown text identifier in the point image (TXSY* parameter) and correct. Then restart the operation. Siemens Building Technologies Landis & Staefa Division VISONIK DCS Functions and System Messages VVS18 System Messages --- DCS Messages CM2U8567E / 04.
SDC Distribution still running STAP TYP 00:00:00 NAME ->DEVINI (M.ASDC) SDC Distribution still running Explanation A restarted load operation of a special day calendar SDC for the PS 'NAME' has been ignored because a previously started identical operation is still in progress. Action Wait until the current operation is completely over. Then restart the operation. CM2U8567E / 04.
SDLC-Controller Reset incomplete, R1=xxx STAP TYP 00:00:00 NAME ->MSGDEV (M.RCRI) Explanation SDLC-Controller Reset incomplete, R1=xxx A reset was carried out on the SDLC chip of the Ring controller NAME. The then occurring functional check of the Ring controller determined that a register contained a value unequal to zero. For registers it can be either the SDLC status register (if xxx=177777) or the PORT B register (if xxx<>17777).
SECCNT(TIX)=xxx SECCNT(SYSL)=yyy PNAM 00:00:00 ->DEVINI (M.SECC) SECCNT(TIX)=xxx SECCNT(SYSL)=yyy Explanation SECCNT = Seconds counter This message can only appear with a system boot. The content of the TIX seconds counter is compared with the contents of the SYSL seconds counter. If the deviation is too large, the message is given. The message mainly appears when starting old backups. Action If the message appears frequently, please inform Landis & Staefa FS&PM. CM2U8567E / 04.
shadow too old: (old date/ today: new date) STAP TYP 00:00:00 NAME ->MSGDEV (M.SHOF) shadow too old: (old date/ today: date) new Explanation A shadow's age is tested once per day. In this case the last shadow is too old (older than one day), which can endanger the functional capabilities of the DC Server.
SYSIVN=xxx Centrale_IVN=yyy ==> OSV ET41 PS 00:00:00 NAME ->DEVINI (M.IVN) Explanation SYSIVN=xxx Centrale_IVN=yyy ==> OSV During manufacturing, L & S provides each process station PS (PRV/BPS/EKL X) with an individual number. This number is accessible via the system variable SYSIVN and is also marked on the housing of the PS. When the PS is connected to a VISONIK DC Server for the first time, the system takes this number and saves it under the PS parameter IVN.
SYSIVN=xxx bitte in PS definieren ET41 PS 00:00:00 NAME ->DEVINI (M.IVN) Explanation SYSIVN=xxx bitte in PS definieren During manufacturing, L & S provides each process station PS (PRV/BPS/EKL X) with an individual number. This number is accessible via the system variable SYSIVN and is also marked on the housing of the PS. When the PS is connected to a VISONIK DC Server for the first time, the system takes this number and saves it under the PS parameter IVN.
System Updated! (xx Reaction(S) carried out!) KTXT 00:00:00 ->MSGDEV (M.RXE) Explanation System Updated! (xx Reaction(S) carried out!) If, for some reason, the system time is changed (either manually through the DA function or through transferring an EKL time after a system outage), the programs for handling the ZRK and DRK entries are started automatically.
TA :CTYP=ctyp Please Generate PTYP 00:00:00 NAME ->DEVINI (M.TYF) TA :CTYP=ctyp Please Generate Explanation The point with NAME (or rather, where available, the point with a TA) transmits an event to the system. If, in the DC Server, a point with another type is generated at this address, a message occurs. If, as yet, no point has been generated in the DC Server at this address, then this message is output if the $S,TRBI=200 diagnostic is switched on.
TA :IDC=DI Please Generate PTYP 00:00:00 NAME ->DEVINI (M.TYF) TA :IDC=DI Please Generate Explanation The point with NAME (or rather, where available, the point with a TA) transmits an event to the system. If, in the DC Server, a point with another type is generated at this address, a message occurs. If, as yet, no point has been generated in the DC Server at this address, then this message is output if the $S,TRBI=200 diagnostic is switched on.
TA :TYP=typ Please Generate PTYP 00:00:00 NAME ->DEVINI (M.TYF) TA :TYP=typ Please Generate Explanation The point with NAME (or rather, where available, the point with a TA) transmits an event to the system. If, in the DC Server, a point with another type is generated at this address, a message occurs. If, as yet, no point has been generated in the DC Server at this address, then this message is output if the $S,TRBI=200 diagnostic is switched on.
temperature > 65 GradC (ventilator down?) DIAG TYP 00:00:00 NAME ->DEVINI (M.HEAT) Explanation temperature > 65 GradC (ventilator down?) A VISONIK computer's Q BUS SDLC controller has an integrated temperature detector that is checked every minute by the VISONIK DCS operating system.
TERM bad: process xxx aborted! STAP TYP 00:00:00 NAME ->MSGDEV TERM bad: process xxx aborted! (M.TTAB) Explanation A process xxx (function, dialogue, report, update) has been aborted by the operating system because the related I/O terminal was reported as "faulty". This message is purely informative and appears only under severe diagnostics $SY,TRBI=...). Action None. Possibly switch the terminal involved off and then on again (--> initialisation).
text (Ch#=xx) DP3 TYP 00:00:00 NAME ->DEVINI (M.DEVPCH) Explanation text (Ch#=xx) This message signals problems with the data channel 'xx' when loading locally logged data in a remote PS using operation 'DACQ'. 'text' details the circumstances of the problem: Faulty data channel syntax: The data of the logging profile (e.g., technical address, parameter, interval, etc.) received from the DC Server cannot be interpreted.
text (CH# = yy) DP3 TYP 00:00:00 NAME ->MSGDEV (M.DEVPCH) Explanation text (CH# = yy) This message signals problems when loading locally logged data in a remote PS using the DACQ backup operation. 'text' details the circumstances of the problem: The following holds: 'text'= faulty data channel syntax: The data of the logging profile (point address, parameter, etc.) received from the DCS cannot be interpreted.
Text transfer switched off (OS.XX=7) STAP TYP 00:00:00 NAME ->DEVINI (M.NOXX) Text transfer switched off (OS.XX=7) Explanation The LoTX or SaTX backup operations cannot be started because the BPS language is not defined (parameter XX of the OS point). Action Define the language and restart the operation. CM2U8567E / 04.
TIX xxxxxx seconds sleeping!! CYX 00:00:00 ->DEVINI (M.TIX) TIX xxxxxx seconds sleeping!! Explanation The TIX (=TIme eXecutive) program, which controls all time-dependent actions such as feedback supervision for switch commands or delays for status points, has stopped for xxxxxx seconds or is running in an endless program loop. Action If this message occurs frequently, please inform the Landis & Staefa Service department immediately.
too many PS, ignored PS=xx DIAG TYP 00:00:00 NAME ->MSGDEV too many PS, ignored PS=xx (M.RWMU) Explanation In interrogating the substation sequence in Ring NAME, too many process stations PS have reported. All excess PS, including PS xx are ignored. Action Keep to the maximum permissible number of PS per Ring. In exceptional circumstances the limit may be increased using the L & S System Manager Function SYS,PROJ. CM2U8567E / 04.
transport failure: NW@=NAME ........ PNAM transport failure: NW@=NAME DC rsn=v usta=w tsap=x cmd=y totc=z 00:00:00 ->MSGDEV (M.TPER) Explanation This type of message appears, for example, when malfunctions and interruptions occur in the network (e.g., break in a telephone line). NW@: Network Address of transport partner DC rsn: disconnect reason DR.nrm=200 ;normal disconnect initiated by session control DR.ncf=201 ;no connection free DR.cnf=202 ;connection negotiation failed DR.
[Error Text] "tus="NAME axl=... ASX 00:00:00 ->MSGDEV (M.AXER) [Error Text] "tus="NAME axl=... Explanation "Partner does not answer" tus=partner@ axl=ASX level – ASX levels: MSG (remote message) DLG (remote dialogue) REP (remote report) SER (remote service) – This message almost always indicates a break in the connections. The associated transfer is aborted immediately. A repetition is not possible for ASX because the transport layer is missing. Action Check the connection.
TXI/2 ALSTA ALVIS STAP TYP 00:00:00 NAME ->DEVAL (M.QUITT) TXI/2 ALSTA ALVIS Explanation Each change in the ALSTA alarm status generates this message. Additionally, the alarm status "acknowledged" is supplied with the signature of the operator who acknowledged the alarm. Action None. Siemens Building Technologies Landis & Staefa Division VISONIK DCS Functions and System Messages VVS18 System Messages --- DCS Messages CM2U8567E / 04.
Tx interrupt missed, xx yy zz STAP TYP 00:00:00 NAME ->MSGDEV Tx interrupt missed, xx yy zz (M.RDZT) Explanation The controller of Ring NAME generated no interrupt after transmitting a telegram. Values xx, yy and zz indicate in which status the Ring was and, in particular, if a transmit or receive interrupt was expected. The message is normal for Ring breaks. It appears only under severe diagnostics ($S,TRBI=1000).
TYP=xxx , IDC=yyy => Operational STAP TYP 00:00:00 NAME ->DEVINI (M.INB1) TYP=xxx , IDC=yyy => Operational Explanation If the identification (IDC) changes and with it the TYP of a point, then this change is reported. This message is normal for the first switch-on of modules or a PS. Action None. Siemens Building Technologies Landis & Staefa Division VISONIK DCS Functions and System Messages VVS18 System Messages --- DCS Messages CM2U8567E / 04.
UA lost, reference cleared! PNAM 00:00:00 NAME ->DEVINI (M.UASF) UA lost, reference cleared! Explanation User addresses of points are not stored in the process image, but in an auxiliary list called UAL (UAL=User Address List). The IPSU search program has optimum access to the UAL through a reference. The message is a result of some unclear malfunction (e.g., defective disk, power loss at an inopportune moment, etc.) which has caused the loss of a user address of point NAME from the UAL.
unexpected timeout! step=xxx=text STAP TYP ->DEVINI 00:00:00 NAME unexpected timeout! step=xxx=text (M.UTIO) Explanation During the multi-step initialisation phase of a PS, the PS no longer answers. After expiration of a specified time (timeout), the message appears. The initialisation step in progress is aborted. The initialisation, among other things, continues on with the next step. Action Repeat the aborted initialisation step.
unit switch abnormal DIAG TYP 00:00:00 NAME ->MSGDEV unit switch abnormal (M.1AB) Explanation In backup DC Servers with a disk changeover unit, the automatic function can be checked. The procedure is, however, not always a smooth one: Changeover takes place with associated initialisation (system boot). The procedure is started on computer A at point $SY with parameter SHAD=mABA. If the automatic function fails, the above message appears.
Unit=xx; yy/zz Bad Disk transfers ......... DIAG TYP 00:00:00 NAME ->DEVINI (M.TRFF) Explanation Unit=xx; yy/zz Bad Disk transfers (call maintenance!) During transfers to and from the disk unit xx, yy of zz (zz=1000) data transfers have to be repeated. With an active severe Ring diagnostic ($S,TRBI=200), the error rate is reported as yy/10000. The causes for bad data traffic with a disk include the following: – Disk having bad sectors. – Contact problems between disk unit and controller.
Unknown Identification: xxx STAP TYP 00:00:00 NAME ->MSGDEV Unknown Identification: xxx (M.UNID) Explanation Terminal NAME has reported an unknown self identification. xxx represents the unknown identification sequence without the preceding [ (octal). This message is caused by connecting a terminal that is not yet supported by the VISONIK DC Server. Action Check the identification with trace. If unknown, then please inform Landis & Staefa FS&PM. If the terminal is a display unit, parameter TYX=.
user NAME. twice in UAL, verify with ........ PNAM ->DEVINI 00:00:00 NAME (M.UAD) user NAME. twice in UAL, verify with UAX,VE or BOO,V Explanation As a result of some malfunction (e.g., faulty disk, power failure at an inopportune moment, etc.), a user address has been entered twice in the UAL (User Address List). This user address causes the message to appear upon later access to the associated point.
uuu,vvv wwww : xxx,yyy error=zzz TA=.... PNAM 00:00:00 ->MSGDEV (M.AAER) Explanation uuu,vvv wwww : xxx,yyy error=zzz TA=... R0=aa R1=bb R2=cc uuu=PC program counter vvv=Stack@ www=Program name (Typ) see below Type AAA2 messages Explanation Action Explanation Action Explanation Action Explanation Action error=1 R0=TA, R1=C.xpn=par# G.ptm: TA not found SW Error (Application) Please collect these messages and forward them to Landis & Staefa FS&PM.
Type IOX4 messages Explanation Action error=1 R0=x #$Tx: ADDP channel, Partner PS missing (SL.lus) Check the software configuration of the connecting channel. Explanation Action error=2 R0=x #$Tx: ADDP channel, rx buffer too small. Check the software configuration of the connecting channel. Explanation Action error=3 #same as error=1, detected in AD$IDO Check the software configuration of the connecting channel.
Type TIX messages Action error=1 R0=PS #X$PS fails to start application ---> pending loop Please collect these messages and forward them to Landis & Staefa FS&PM. Explanation Action error=2 R0=PS #rnr timeout detected! Please collect these messages and forward them to Landis & Staefa FS&PM. Explanation Action error=3 R0=fail PS, R1=delta time [sec] #Background Poll Timeout between 2 PS Please collect these messages and forward them to Landis & Staefa FS&PM.
value=xxx par#=zz DP3 TYP 00:00:00 NAME ->MSGDEV (M.STRC) value=xxx par#=zz Explanation Data of a trace message in conjunction with data processing. This trace message can be activated via the HITA,TALO (in $S) parameter. It is used for diagnostics and shows the events that write data in the DM FILE. Action This message can be activated or deactivated using $S,TALO and HITA.
vv[TXU]; OFLM: xx[TXU]; yy NAME ..... LSP LS -> 00:00:00 NAME (M.LIM2) vv[TXU]; OFLM: xx[TXU]; yy NAME Automatic switching Insufficient Additional Switch-off by Hand zz[TXLSU] Example LSP LS 00:00:00 $1'000 131 kWh; OFLM: 129 kWh; k.o. $1'000 Automatic switching Insufficient Additional switch-off by Hand 31 kWh Explanation The peak demand program has difficulties. vv = Parameter LS (with units) xx = Currently valid switch-off limit yy = ERSTA (as text: 'k.o.
vvv File # xxx zzz STAP TYP 00:00:00 NAME ->DEVINI vvv File # xxx zzz (M.DXSA) Explanation This message only appears if $SY,TRBI=20000. It documents the data packet zzz which is currently being transferred in 'SaFi' or 'LoFi' (vvv) file transfer mode. The following data packets are transferred by 'SaFi' and 'LoFi' and stored in or fetched from file xxx: zzz stands for the following texts: TSK1..199 -> all user tasks 1 to 199 TSK252..
WRK: BAD TIMING!! SECCNT=xx ........ DIAG TYP ->DEVINI 00:00:00 NAME (M.WFE) Explanation WRK: BAD TIMING!! SECCNT=xx WSECC=yy WSBLK=zz Measuring all operating hours in all maintenance reaction entries is derived from an internal seconds counter. Because of some malfunction, the seconds counter is out of synchronism with the clock.
Xxx Aborted STAP TYP 00:00:00 NAME ->DEVINI (M.DXAB) xxx Aborted Explanation No transport connection to the PS 'NAME' can be made for carrying out the 'xxx" backup operation, e.g., because the PS is busy with another user or the data line (telephone) being used is poor. After five attempts the operation is considered as failed and is aborted. The message only appears with switched on diagnostics (DIAG parameter in the PS point). Action Check the data connection to the PS or check the PS itself.
Xxx Bad Application Sequence by STAP TYP 00:00:00 NAME ->DEVINI (M.DXEE) xxx Bad Application Sequence by Explanation The data of the 'xxx' backup operation were not received in the correct sequence. Action Check configuration and possibly notify Landis & Staefa FS&PM. CM2U8567E / 04.
xxx Cannot be set ERR TYP 00:00:00 NAME ->DEVINI xxx Cannot be set (M.DXBR) Explanation The 'xxx' backup operation cannot be set at the 'NAME'PS. Action Check configuration. Possibly send a copy of the message to Landis & Staefa FS&PM. Siemens Building Technologies Landis & Staefa Division VISONIK DCS Functions and System Messages VVS18 System Messages --- DCS Messages CM2U8567E / 04.
Xxx ended STAP TYP 00:00:00 NAME ->DEVINI xxx ended (M.DXED) Explanation This message only appears if $SY,TRBI=20000. It is output if one of the following data transfer programs xxx (which are managed through the O or OPLS parameters) has completed processing: – Macq -> Message Acquisition – Dacq -> Data Acquisition – SaFi -> Save PS Configuration in its backup file – LoFi -> Load PS Configuration from its Backup File Action None. CM2U8567E / 04.
Xxx breaks down because RAM is full STAP TYP 00:00:00 NAME ->DEVINI (M.MFUL) xxx breaks down because RAM is full Explanation The currently running 'xxx' backup operation cannot load further because the RAM of the 'NAME' PS has become full. Action Reduce data quantity and restart the operation. Siemens Building Technologies Landis & Staefa Division VISONIK DCS Functions and System Messages VVS18 System Messages --- DCS Messages CM2U8567E / 04.
Xxx Events per hour STAP TYP 00:00:00 NAME [TXI] [TXI2] ->MSGDEV xxx Events per hour (M.EVOV) Explanation A event limit of 5000 events per hour is set in the process stations. If this event limit is exceeded by a process station, then it will be indicated with this message, where NAME specifies the process station and xxx the number of events. The limit can be changed by Landis & Staefa only. Action Use ARC,ARCM to help determine the cause of the event overflow and eliminate. Example ...
xxx fff, eee at zz PNAM 00:00:00 ->DEVINI (M.FPMP) xxx fff, eee at zz Initiated by: This message is part of the FPMP Mathematics Package and can be started by programs that carry out calculations, such as, e.g., LSP, OSTP, COLBAS etc. Explanation When calculating expressions, illegal results were obtained or computer operations could not be executed. The zz value of the PC (program counter) indicates the relevant location within the program that is running.
Xxx fff, eee CB task tt,nn PNAM 00:00:00 ->DEVINI (M.FPMP) xxx fff, eee CB task tt,nn Initiated by: This message is part of the FPMP Mathematics Package and can be started by programs that carry out calculations, such as, e.g., LSP, OSTP, COLBAS etc. Explanation When calculating expressions, illegal results were obtained or computer operations could not be executed. The zz value of the PC (program counter) indicates the relevant location within the program that is running.
xxx Jumped over 'yyy' STAP TYP ->DEVINI 00:00:00 NAME (M.SKIP) xxx Jumped over 'yyy' Explanation Depending on the type of PS (EKL X, PRV1 or BPS), the 'xxx' backup operation jumps over specific commands 'yyy' or command areas 'yyy zzz'. This happens because, while the control table for loading holds all commands, not all PS types need all data The message appears only for activated diagnostics (parameter DIAG in the PS point). Action None.
xxx Out of Order STAP TYP 00:00:00 NAME [TXI] [TXI2] ->MSGDEV xxx Out of Order (M.OST1) Explanation Measurements from address NAME, which is assigned as an input reference value of an OSTP zone (parameter SIDTO), are wrong. As a result, OSTP cannot smoothly follow the inside or outside temperature. Nevertheless, in order to run the zone involved in a seemingly functional way, the following rules apply: Incorrect inside temperature values are ignored and replaced by the zone setpoint value.
xxx started STAP TYP 00:00:00 NAME ->DEVINI xxx started (M.DXBE) Explanation This message only appears if $SY,TRBI=20000. It is output when one of the following data transfer programs xxx, as managed by parameter O or OPLS, has started its transfer: – Macq -> Message acquisition – Dacq -> Data acquisition – SaFi -> Save PS configuration in its backup file – LoFi -> Load PS configuration from its backup file Action None.
xxx Invalid! STAP TYP 00:00:00 NAME [TXI] [TXI2] ->DSMn xxx Invalid! (M.OIMW) Explanation Parameters xxx (SIDTO) of the OSTP Zone NAME have no legal point address. Either the point, which provides the inside or outside temperature, is not configured or it is an illegal type of point (e.g., switch command). The message is printed out upon every OSTP program pass as a warning. Action Assign legal addresses to the SIDTO parameters. CM2U8567E / 04.
xxx Jumped over 'yyy zzz' STAP TYP 00:00:00 NAME ->DEVINI (M.SKIP) xxx Jumped over 'yyy zzz' Explanation Depending on the type of PS (EKL X, PRV1 or BPS), the 'xxx' backup operation jumps over specific commands 'yyy' or command areas 'yyy zzz'. This happens because, while the control table for loading holds all commands, not all PS types need all data The message appears only for activated diagnostics (parameter DIAG in the PS point). Action None.
Xxx will be repeated due Error No. #yyy STAP TYP 00:00:00 NAME ->DEVINI (M.REPT) xxx will be repeated due Error No. #yyy Explanation A backup operation 'xxx' cannot be executed because no connection can be made to the PS (e.g., modem busy with a telephone connection). The message can also appear during execution of the 'xxx' backup operation if a 'yyy' error occurs. Action None. The 'xxx' operation is automatically repeated. CM2U8567E / 04.
xxx will be repeated because BPS Busy STAP TYP 00:00:00 NAME ->DEVINI (M.REPT) xxx will be repeated because BPS Busy Explanation A backup operation 'xxx' cannot be executed because no connection can be made to the PS (e.g., modem busy with a telephone connection). The message can also appear during execution of the 'xxx' backup operation if a 'yyy' error occurs. Action None. The 'xxx' operation is automatically repeated.
xxx/yyy noise NOLI = zzz STAP TYP 00:00:00 NAME ->MSGDEV xxx/yyy noise NOLI = zzz (M.RPER) Explanation More than xxx/yyy telegrams have been corrupted on the Ring NAME, i.e., – The CRC sum of a telegram is incorrect. – The telegram length was shorter than 32 bits. – A telegram has been received whose length was not a multiple of 8 bits. – An interrupted telegram was received (telegram contains an abort character).
xx(yy) No Output possible after zz STAP TYP 00:00:00 NAME ->MSGDEV (M.FSX9) xx(yy) No Output possible after zz Explanation System yy of a link system attempts to make an output (e.g., reaction picture) using function xx (e.g., FSG) to the terminal. The terminal is not accessible, but the system has not (yet) recognised it as defective. Action Switch on/check the terminal. It may have happened that the terminal was switched off without cleanly quitting the application.
xx=yy Suppressed ! KTXT 00:00:00 ->MSGDEV (M.MACS) xx=yy Suppressed ! Initiated by: Reaction programs ZRK and DRK Explanation During a system time jump forwards, reactions ZRK and DRK, that were to be executed during the time jumped over, are belatedly updated (the so-called catch-up logic). For catch-ups of macro commands in reaction entries, the length of the time jump is additionally checked. If the time jump exceeds two hours, then the execution of the macro command is suppressed.
yyy with unauthorized Backup Version STAP TYP 00:00:00 NAME ->DEVINI (M.BILV) yyy with unauthorized Backup Version Explanation During the 'yyy' backup operation it was determined that the version of the data backup in the file of the PS 'NAME' was not compatible with the version of the associated PS. A data backup of an EKL X, e.g., cannot be loaded in a BPS. Action Delete the backup file (function EDI,DEL). Then newly create the data backup of the PS 'NAME' using the 'SaFi'operation.
z: a,b x:c,d R0..R4: PNAM 00:00:00 ->DEVINI (M.FAT3) e,f,g,h,i z: a,b x:c,d R0..R4: e,f,g,h,i Initiated by: Any program can initiate this message. z: --> Program name a,b --> Offset x: --> Additional information to the c,d --> program names R0..R4 --> Register e,f,g,h,i --> Register contents Explanation This message is "a dogsbody". It indicates the occurrence of an unexpected, but not serious condition within a program.
