Instruction manual

1070 072 163-101 (97.11) GB
Introduction 2-3
Comparison of Diagnostic Concepts, CL200 vs. CL350 / CL400 / CL500
Definition CL200 CL350 / CL400 / CL500
Cascade mana-
gement
For all process sequences, the KETTE200
cascade management module is called up
only in the BTSMADAP function module.
For each process sequence, a separate module
call of the KETTE cascade management mo-
dule must be programmed.
Synchronization Not implemented. All cascades in all steps.
Operating Modes Are written directly into the data modules. Are defined by means of parameters in the
KETTE module.
Diagnostics As the function is integrated in the KET-
TE200, it does not require a specific call-
up.
For all process sequences, the DIAG500E func-
tion module is called once by the BTSMADAP
PM.
BT-MADAP The menu administration is handled by the BT5/BT20 operating terminal. Parameter
processing of standard modules occurs in the PLC program.
Allocation of
KETTE DM's
For the CL200, the binary statuses of both active steps and of command outputs were
omitted.
Marker allocation As the size of the marker address range varies with different controllers, the addresses of
the functionally defined BEFA and WSB markers differ also. The same is true for the scratch
marker range.
Step module
programming
Due to variances between the diagnostics routines of different controllers, in the case of the
CL200 the JPCY jump instruction (never executed) must be entered for non-bit commands.
This is done in order to ensure that, for the purpose of diagnostic functions, such commands
(e.g. default values for monitoring and wait intervals) are ignored. In the case of purely bit
command programming, identical programming routines can be used.
Command output
programming
On the CL200, the command output is enabled solely via an actual vs. setpoint value com-
parison of the active step.
Fig. 2-1 Differences in Diagnostics Concepts
2.4 Menu and Module Structure
As a consequence of differing screen sizes, the utilization of the BT5
and/or BT20 operating terminals results in different menu trees and mo-
dule structures. The menu trees for BT5 and BT20 appear on the follo-
wing pages, providing an overview of screen nesting and the respective
function key assignments. (It should be noted that the term mask still ap-
pearing in some editing programs, for example, is gradually being repla-
ced by the more common screen.)