Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
92
A-1
A-2
The operating console PCS 110 is prepared 1 Fluorescent display (2 x 40 char.) informs about all machine and
nearly for all operating enquieries therefore the controller processes
PLC provides you a huge selection of opera-
2 10 user definable LEDs with functions:
ting-, display-, and function elements, tools
which can be individually used from application ON, OFF, FLASH RAPIDLY, FLASH SLOWLY
to application. 3 20 user definable mechanical control keys
PCS 110, a universal operating console
4 Info field with freely selectable labelling for individual designation
useable for simple operating with some of the function keys
function keys up to complex datainput routines
with dialog. Programming control systems and 5 3 LED, which give information on the current PCS function
operating - now it's possible. 6 10-key numeric keyboard for the entry and correction of
norminal values
7 8 control keys for fast operation of the PCS
PROGRAMMING
ACCESSORIES
A-3
PCS 737
PCS 739
▼
PCS 716
Adapting cable, 300 cm
PCS 732
▲ PG-programming cable, 300 cm
PCS 732
PCS 737
PCS 716 PC-programming cable, 300 cm, 25/25pol
PCS 739
PC-programming cable, 300 cm, 25/9pol
MEMORY ORGANISATION
AND
DIL-SWITCH-FUNCTIONS
A-4
■ RAM 1
■ RAM 2
■ EPROM A / EEPROM A
■ EPROM B / EEPROM B
5 no effect
6 no effect
A-5
A-6
A-7
PCS 716
PCS 110
SPECIFICATIONS
A-8
Power consumption 8 VA
character height 7 mm
Protective encl. IP 65
Weight 1400 g
A-9
Front panel
cutout
Rear panel
ASCII CHARACTERS
DISPLAYABLEINTHE
PCS DISPLAY
A-10
l ë " 2 B R b r
2
_
12 22 32 42 52 62 72
3
Ï e
13
#23
3
33
C S
43 53
c
63
s
73
–
à $ 4 D T d t
4
_14 24 34 44 54 64 74
5
a
15
% 5
25 35
E
45
U e
55 65
u
75
6
[ £
16
& 6
26 36
F
46
V
56
f
66
v
76
Å å
7 17
´27
7
37
G W g
47 57 67
w
77
\
8
¥
18
(28
8
38
H X
48 58
h
68
x
78
] 1/2 ) 9 I Y i y
_
9
_19 29 39 49 59 69 79
N n
A 1A
*2A
:
3A
J
4A
Z
5A
j
6A
z
7A
¿
B
{
1B
+2B
;
3B
K Ä k
4B 5B 6B
ä
7B
ç
C
|
1C
,2C
<
3C
L
4C
Ö l
5C 6C
ö
7C
@ }
D 1D
— =
2D 3D
M Ü m ü
4D 5D 6D 7D
¢
E
÷
1E
.
'_n˜n›N˜
2E
>
3E
N ▲ n
4E 5E 6E
ß
7E
F
i 1/4 /
1F 2F
?
3F
O ▼ o
4F 5F 6F
■
7F
LEGENDSTRIPS
FORTHE
PCS-INFOFIELD
A-11
A-12
Example
THEPCS-FAMILIE
THE PCS110 IS FOR THESE
PROGRAMMABLECONTROLLERSYSTEM
A-13
PCS 110 Siemens Programmable controller systems ■ The PCS 100 operating console
SIMATIC S5, 100U...115U
PCS 111 Manual with diskette more information in the
through the programmable controller PCS 100 and 101 manual
PCS 716 Connection cable
■ PCS 100 is bus-compatible.
Up to 31 PCS (and therefore different pro-
PCS 732 2 Programmable cable for PG 685, PG 750 grammable controller systems and ma-
chines can be managed centrally by a com-
PCS 737 2 Programmable cable for PC (MSDOS) 25-pole
puter through a DIN measurement bus.
PCS 739 2 Programmable cable for PC (MSDOS) 9-pole
■ Operating instructions, manual and software are protected by copyright. All rights are reserved.
Copying, reproduction, translation or resetting in whole or in part is forbidden. The proper use of the
software constitutes an exception to the above.
■ This manual describes our PCS 110 products. We reserve the right to make changes to this manual
at any time without giving prior notification.
■ We can accept no liability for any printing errors that may occur. Our liability for damages is limited to
cases where it can be proved that incorrect information was given deliberately.
■ This manual deals with the delivered versions PG 110.302.3. Differences to older versions are not
indicated in all cases.
■ We cannot guarantee that programs and data stored on the diskette in respect of accuracy and
freedom from error. We only guarantee that they are capable of running within the application described
in the manual.
■ Since diskettes constitute data carriers which may be manipulated, we can only guarantee their
physical integrity. Out liability is limited to the supply of a replacement.
■ Suggestions for improvements and information about errors are always welcome.
1 FIRST START-UP 1
1.1 TOPICS COVERED 1
1.2 EQUIPMENT AND ACCESSORIES REQUIRED 1
1.3 PROCEDURE 2
1.4 FAULT ELIMINATION 5
2 FUNCTION 7
2.1 GENERAL SURVEY OF TASKS 7
2.2 OPERATING ELEMENTS 8
2.2.1 DIL SWITCHES 8
2.2.2 LED DISPLAYS 9
2.2.3 DISPLAY 10
2.2.4 KEYS 10
2.2.5 LABELLING FIELD 10
2.3 CONNECTIONS 11
2.3.1 OPERATING VOLTAGE 11
2.3.2 SERIAL INTERFACES 11
2.3.2.1 COMMUNICATIONS INTERFACE 12
2.3.2.2 PROGRAMMING INTERFACE 12
2.3.3 MEMORY PACK PCS 801 / PCS 802 12
2.4 ONLINE OPERATION 13
2.4.1 TEXT / VARIABLES / MENU 13
2.4.1.1 TEXT GROUPS 13
2.4.1.2 VARIABLES 14
2.4.1.3 EXTERNAL VARIABLE TYPES 14
2.4.1.3.1 VARIABLE FORMAT BIT 15
2.4.1.3.2 VARIABLE FORMAT STRING 16
2.4.1.3.3 VARIABLE FORMAT CSTRING 17
2.4.1.3.4 VARIABLE FORMAT BCD-1.2 / BCD0-1.2 18
2.4.1.3.5 VARIABLE FORMAT BIN 19
2.4.1.3.6 VARIABLE FORMAT WORD 21
2.4.1.4 INTERNAL VARIABLES 22
2.4.1.5 VARIABLE REPRESENTATION 23
2.4.2 PRIORITY MANAGEMENT 24
2.4.2.1 DEFAULT TEXTS 25
2.4.2.2 MENU DESIGN 25
2.4.2.2.1 ACTUAL VALUE MENU 26
2.4.2.2.2 SETPOINT VALUE MENU 27
2.4.2.3 MESSAGE PRIORITIES 30
2.4.2.3.1 STORAGE PROCEDURE 30
2.4.2.3.2 DELETION PROCEDURES 31
2.4.2.3.3 DISPLAY PROCEDURE 32
2.4.2.3.4 VARIABLES IN MESSAGE TEXTS 32
2.4.2.4 HELP PRIORITY 32
2.4.2.5 COMMUNICATIONS ERRORS 33
2.4.3 PCS 110 INTERFACING 34
2.4.3.1 BRIEF OVERVIEW OF THE DW/MW RANGE 36
2.4.3.2 SYSTEM RANGE 37
2.4.3.3 FUNCTION RANGE 38
2.4.3.4 MESSAGE RANGE 43
2.4.3.5 VARIABLES RANGE 44
TABLE OF CONTENTS
3 PROGRAMMING 49
3.1 COMMANDS FOR SERIAL PROGRAMMING 50
3.2 SYNTACTICAL DECLARATIONS 51
3.2.1 BEGINNING / END IDENTIFIERS 52
3.2.2 TEXT DEFINITION 52
3.2.3 DELETION PROCEDURE / PRIORITY ASSIGNMENT 53
3.2.4 DETERMINE ROTATION TIME / CYCLE TIME 54
3.2.5 DETERMINE TERMINATION KEY FOR ACTUAL VALUE MENU 54
3.2.6 MENU DEFINITION 55
3.2.7 VARIABLE DEFINITIONS 56
3.2.8 TEXT INSTANCES 57
3.2.9 POSITION STATUS INFORMATION 58
3.3 MEMORY ORGANISATION 58
3.4 ERROR CODES 60
3.5 PROGRAMMING PROCEDURE 61
3.5.1 CREATING A TEXT FILE 61
3.5.2 TRANSCRIBING THE TEXT FILE 61
3.5.3 ERROR ANALYSIS 62
3.6 SETTINGS OF THE PROGRAMMING UNIT 62
3.6.1 PG 675 62
3.6.2 PG 685 62
3.6.3 PG 750 63
3.6.4 PC 63
5. TECHNICAL APPENDIX 75
5.1 TECHNICAL DATA OF THE PCS 110 75
5.2 CABLES 76
5.2.1 COMMUNICATION CABLE PCS 110 / PROG. CONTROLLER L1 76
5.2.2 PROGRAMMING CABLE 77
5.3 DATA TRANSFER PCS 110 / PROG. CONTROLLER L1 79
5.3.1 DATA TRANSFER PROCEDURE 80
5.4 PROGRAM LISTING 82
5.4.1 PROJECT 1 (P11112ST.S5D) 82
5.4.1.1 FB 210, 211, 212 AND 213 82
5.4.1.2 APPLICATION EXAMPLE FOR PROJECT 1 88
5.4.2 PROJECT 2 (P11122ST.S5D) 89
5.4.2.1 FB 210, 211, 212, 213 AND DB1 89
5.4.2.2 APPLICATION EXAMPLE FOR PROJECT 2 94
5.4.3 PROJECT 3 (P11132ST.S5D) 95
5.4.3.1 FB 210, 211, 212 AND 213 95
5.4.3.2 APPLICATION EXAMPLE FOR PROJECT 3 100
5.4.4 PROJECT 4 (P11142ST.S5D) 101
5.4.4.1 FB 210, 211, 212, 213 AND DB1 101
5.4.4.2 APPLICATION EXAMPLE FOR PROJECT 4 106
7. INDEX 109
First start-up
1 FIRST START-UP
The chapter contains information on starting up the system for the first time. Its main purpose is to enable
you to carry out initial tests with the system. All the techniscal details which you require for adapting the
system to your personal requirements are given in Chapters 2 to 6.
The manual refers exclusively to the use of the PCS 110 together with an S5 series controller from Siemens.
It is assumed that the reader is familiar with S5-specific terminology. Other terms such as M+xx.y, MB+xx
and MW+xx are used. Since the PCS 110 can also communicate with a measurement range to which
parameters can be assigned, the initial address of the marker range must be added to the offset xx (eg. 50
if parameters are being assigned to the marker range MW 50 - MW 198).
Caution:
Since the communication interface to the programmable controller is also used by the programming unit,
it is recommended that a CPU with two serial interfaces are used for the program test. However, only the
CPU 943 and 944 in the 115U series are currently available with this equipment.
1
First start-up
1.3 PROCEDURE
First of all the text file »#P110.DOK« and »#P111.DOK« are transferred into the PCS 110. If you are using
a data block as the communication range Project 3 (programmable controller 100 U or over) or Project 4
(programmable controller 95 U) is to be used. Otherwise, if you are using a marker range as the
communication range, Project 1 (programmable controller 100 U or over) or Project 2 (programmable
controller 95 U) is to be used. This ensures that there is a valid parameter set in the PCS 110 regardless
of the condition in which it was delivered. Communication with the programmable controller is then started.
If you are not using a PG 685 please read Section 3.6 first.
1. Connect the printer interface of the programmer with the programming interface (1) of the PCS 110
via the cable PCS 732. Observe the legends on the cable ends!
2. Ensure that DIL switches Nos. 7, 9 and 10 are ON and that DIL switch No. 8 is OFF. Ensure also that
the RS 232 / TTY changeover switches are in the correct position (1: RS232, 2: TTY).
3. Switch on the operating voltage (19...33 V DC) to the PCS 110. At least the ERR LED must now light
up.
4. Press the HLP key and keep it pressed while briefly pressing the <CLR> key. The following message
appears:
»STOP DISPLAY OF MESSAGES?
CONFIRM WITH ENTER«
5. Press the ENTER key. The OFFLINE menu now appears. You can now select the menu option
(underlined) with the <+> and <-> keys.
6. Select the menu option:
»PROGRAMING ON SERIAL PORT«
7. Select »RAM1« and press ENTER. 4 numerals and the »>« sign now appear. The PCS is now in
programming mode.
8. Use the DEVICE command to set the interface of the PG to 7 data bits, 2 stop bits and EVEN parity
(not necessary with the PG 675):
>DEVICE LPT0 <PAR=EVEN>
>DEVICE LPT0 <DAT=7>
>DEVICE LPT0 <STOP=2>
9. In the default on the PG select »TITLE BLOCK NO« and »SYSTEM COMMANDS ON« and copy the
diskette onto your hard disk as a project.
2
First start-up
10. Select:
»Output FD #P110.DOK nach DRU: 1« am PG 685 und PG 750
»Output FD1 #P110.DOK nach DRU: *« am PG 675
Depending on the printer setting, either the contents of the file or (apparently) incoherent characters
with the cursor flashing will appear in the display. In the latter case, it means there is a line which the
PCS 110 does not understand. In this case the <CLR> key must be pressed. Normally it is a sequence
of characters linke »ä1W« or similar. This is the ESC sequence, which the programmer sends to the
printer (in this case to the PCS) for font selection.
11. After a time (approx. 20 seconds .. 2 minutes) the programmer answers. Repeat Point 11 with the
file »P101.DOK«.
12. In the display "##" (the end mark) should now appear. If the line number (...IN:xxx) has not been
counted up, see »DEALING WITH FAULTS«.
13. Programming can now be terminated with the [HLP] key. The main menu appears.
14. Select the menu option:
»STARTUP-PROCEDURE«
Colons must now appear at both line ends. If they do not, a fault analysis must be carried out (see
1.4).
17. Switch off the voltage supply to the PCS 110 and connect the operating console to the same supply
as your programmable controller (assuming that you are supplying your programmable controller with
24 V DC).
18. If you are using a programmable controller of type AG 100 U or 115 U connect an input module as
the 1st module and an output module as the 2nd module.
19. Switch the programmable controller to STOP and supply the programmable controller and the PCS
110 with operating voltage.
20. Check the presetting mask in the programming unit. The »SYSTEM COMMANDS« point must be
preset to »YES«.
21. Transfer FB 210, FB 211, FB 212, FB 213 (also DB1 on the AG 95 U), OB1, OB21 and OB22 from
the diskette to the programmable controller.
22. If you are using a series 100 U programmable controller the parameter "ERROR" in the handling FBs
210 in the OB1 in output 1.0 should be renamed. This assumes that you are using 8-bit input/output
modules.
23. Connection the programming interface of the programmable controller to the PCS 110 using cable
PCS 716, observing the writing on the cable ends.
24. Switch the programmable controller from STOP to RUN. The RUN LED on the programmable
controller must now come on and the ERR LED on the PCS 110 go out. If this happens the following
text appears in the display between the colons:
This already constitutes the display of a variable. Furthermore output A 4.0 (AG 95 U: A 32.0, AG 100 U:
A 1.0) must not be active.
3
First start-up
The interfacing of the PCS can now be simulated at the programmable controller by writing and reading the
appropriate data words of the DB 50 (Projects 3 or 4) or marker words, marker bytes and marker bits
(Projects 1 and 2). If the connection is broken A 4.0 (for the AG 95 U; A 32.0 and for the 100 U: A 1.0) will
be set. The communication can be restarted by pressing a reset button on E 0.0 (for AG 95 U: E 32.0).
In the examples for Projects 1 and 2 there is the marker range from MW 50 up to an including MW 198 (in
other words 75 words) required for communication. This range can be redefined using the parameter "VOBI"
in FB 210. See also 4.2: "Parameter assignment of the FB 210".
All the texts, various variables, all actual and setpoint value menus and all message texts and a HELP text
are now filed in the PCS. This means that all the functions can now be tested (manually using CONTROL
VARIABLE on the programmable controller). However, this is only possible if the CPU has two serial
interfaces which is currently only possible with CPU 943 and 944 in the 115 U series.
16 SETPT. 1 (K1) - - - -
17 SETPT. 1 (K2) AD BIT (SETPOINT) 96.0 104.0
AE BIT (SETPOINT) 96.1 104.1
AF BIT (SETPOINT) 96.2 104.2
AG BIT (SETPOINT) 96.3 104.3
18 SETPT. 2 (K1) - - - -
19 SETPT. 2 (K2) AH STRING (ACT) 0...5 105 100
20 SETPT. 3 (K1) - -
21 SETPT. 3 (K2) AK BIN-1 (SETPOINT) 102 110
0...150 => 0...2048
22 SETPT. 3 (K3) AM BCD 1 (STPT) 0...1 104 112
AN BCD 2 (STPT) 0...59 106 113
23 SETPT. 3 (K4) AQ BIN-1 (STPT) 500...900 108 116
AR BIN-1 (STPT) 500...900 110 117
4
First start-up
The most common faults that may occure at first start-up are listed below:
1. DIL switch No. 8 is ON. If this switch is set, the PCS enters a diagnostic routine that is required only
for test purposes. Remedy: Set the DIL switch to OFF and restart the PCS 110 (by briefly switching
it off or by briefly pressing the RESET buttons above the DIL switch).
2. The cable ends are interchanged, interfaces 1 (programming interface) and 2 (communications
interface) have been confused or the TTY / RS 232 changeover switches are incorrectly set (correct
setting: switch 2 (PCS110-PLC): TTY, switch 1 (PCS110-PG): RS 232).
3. When programming the handshake does not work. This makes itself noticeable through the following
behaviour: during transfer a first fault occurs. Although this is not acknowledged, the programming
unit replies after a while. Remedy: with the help of the utility »Printer« selec
»BUSY : YES«
(normally PRINTER 1 on the PG 685). A further cause of fault is the choice of the wrong data format
at serial programming.
5. The write protection DIL switches Nos. 9 and 10 are OFF. This is signalled in the PCS and can be
reset by means of a key after removal of the fault condition.
6. The menu DIL switch (7) is OFF and there are already valid data in the PCS 110. As a result of this
the OFFLINE menu cannot be selected. Remedy: set DIL switch 7 to ON (can be switched on even
during operation).
7. After programming the PCS does not show the colons of the default text 0. Diagnosis: errors have
occurred during programming (that were acknowledged) or burning the data into the EPROM has
been omitted.
8. The programmable controller goes to STOP after being started. Diagnose: The selected marker range
is too small, the terminal plug from the last plug position is missing, the PCS wants to access a marker
word outside the specified marker range or there is no data block of the correct length in the
programmable controller.
9. Although the programmable controller goes to RUN, the ERR LED on the PCS does not go out. If this
LED does not go out after a 2nd attempt the connection between the programmable controller
interface and the PCS 110 is to be checked (in this case the send and receive cable of the
programmable controller).
10. In DW 3 (= MW + 6) an error is signalled with a value >< KH 0000. In this case the error is to be sought
at the connection of the programmable controller and the PCS 110. It is possible that the cable is
defect.
11. Communication begins, but after a short time the following message appears:
»COMMUNICATION-ERROR«
In this case the PCS 110/PLC has been laid in area with too high an interference level, the cable is
too long for the baud rate or the earthing is not good enough. A variable in the HELP text gives
information on the reliability of communication (see internal variables).
5
First start-up
Possible remedies:
■ Connect the cable shield to the central grounding point of the control cabinet.
■ Ensure that the PCS 110 housing and the programmable controller bus board are well grounded.
Bear in mind that a copper grounding strap, due to its large surface area, is a much better
conductor of high frequencies than normal stranded wire.
■ Avoid as far as possible the generation of high frequency interference as this is very difficult to
suppress. The programmable controller and the PCS are electrically isolated from one another
by means of optocouplers, but with rapid transients this isolation is ineffective, as the optocouplers
possess a certain amount capacitance.
■ Where the supply voltage exhibits a high degree of interference, it is advisable to supply the PCS
110 from a separate power supply (24 V, 10 VA). This should be fitted with interference filters.
The 0 volt conductor can then be connected directly to the ground lead of the PCS 110.
■ The PCS 110 and the communications cable should be located at least 200 mm from sources
of interference. This applies particularly to inductors and frequency converters.
■ Ensure that the serial data cables are as fully surrounded by the screen as possible. Use a
metallised plug housing on both the PCS 110 and on the programmable controller side which
has a good conductive connection to the cable screen. Please note that if earthed at both sides
an equi-potential bond with at least 10 times the screen cross section may be required.
Particularly if the PCS and programmable controller are not connected to the same earthing point
(if, for example, the PCS and programmable controller are housed in different switch cabinets).
Reason: To avoid bonding currents on the cable screen
6
Function
2 FUNCTION
Using the operating console the following tasks can easily be performed:
■ 2. SUPPORTING MACHINE OPERATION WITH 10 FREELY SELECTABLE LED's; These can take on
the states »LIGHTED«, »DARK«, »FLASHING« and »INVERSE FLASHING«.
■ 3. REPRESENTATION OF FIXED TEXT IN CONJUNCTION WITH VARIABLE VALUES; The values can
optionally be represented as numeric values or in words.
■ 7. MONITORING 128 CONSECUTIVE BITS FOR RISING AND FALLING EDGES; Assigment to texts,
management in 3 priority levels, the most extensive possible retention of the sequence in time,
organization of FIRST, LAST and CYCLIC display, individually adjustable deletions and the
representation forms NORMAL, with FLASHING UNDERLINING; FLASHING and COMBINED
FLASHING are tasks which the PCS 110 performs on its own.
7
Function
8
Function
All LED displays have 4 conditions: OFF, ON, FLASHING, INVERSE FLASHING. In FLASHING condition
there is a 75 % lighted phase and a 25 % dark phase. In INVERSE FLASHING condition there is a 75 %
dark phase and a 25 % lighted phase.
The 10 green LED's above the F-keys are freely controllable via the programmable controller. The 3 red
LED's above the control keys show the operating conditions of the PCS:
? ! ERR
LIGHTED: The PCS waits for the actuation of a key (delete messages, close a menu, release the [HLP]
key).
FLASHING: In delete mode 4 this LED flashes as long as the corresponding message bit is at log 1
(the message cannot be cleared). If the message bit is 0, it is constantly lighted and the message can
be cleared with [CLR].
INVERSE FLASHING: There is an invalid data record in the PCS or the selected EPROM is not plugged
in or the STARTUP procedure is unclear.
While communication is in progress this LED is out. If communication is interrupted (after having been
started) the acoustic error alarm sounds briefly and the LED starts flashing.
9
Function
2.2.3 DISPLAY
In ONLINE operation both lines are available with up to 40 characters each without restrictions (no undesired
entries). The character set is restricted to the Latin letters, including the most common special national
characters. As standard characters the German characters are used; other characters and some auxiliary
graphical symbols can be input hexadecimal codes (see "Programming" chapter).
Underlining under an individual character is managed by the PCS itself. In the message operating modes,
however, global underlining with a flashing underline is selectable. In these modes flashing display of the
entire text is also possible. The representation modes described can be selected at any time from the
programmable controller - separately for each MESSAGE PRIORITY.
2.2.4 KEYS
These are divided into function keys, edit keys and control keys. The function keys F1 to F20 are transferred
into the programmable controller only, they have no internal function. As long as a key is pressed, a log. 1
appears at the corresponding bit.
The edit keys are for numeric inputs, they are not transferred into the programmable controller. The [+] and
[-] keys support the input of setpoint values; they are however also available in the programmable controller.
The control keys [ARROWS], [CLR], [ENTER] and [HLP] have control function, i.e. they are evaluated in the
PCS, where they initiate the corresponding functions. They are also transferred into the programmable
controller, but there they must be interpreted with caution. When the PCS 110 is in Priority 0 (DEFAULT
TEXT), only the [HLP] key has an internal function. The acoustic error alarm, which normally sounds when
a non-permissible key is pressed, is suppressed in Priority 0. Machine-specific functions can thus be
assigned to these keys - provided the priority is limited to 0. Within the HELP priority (which can not be
interlocked) the [ARROW UP] and [ARROW DOWN] keys have internal functions!
In the labelling field an individually shaped foil can be inserted for designating the F-keys. The dimensions
of this foil are as follows:
197.5 ± 0.2
39.5 ± 0.2
Thickness excluding covering film: max. 1 mm. At the upper and lower edges 1.2 mm is covered in each case.
10
Function
2.3 CONNECTIONS
The operating voltage connections are made using screw-type terminals for wires of up to 2 mm2. For details
of current consumption and operating voltage limits see 5.1.1.
Attention:
In the unit the protective conductor and 0V are separate. The
protective conductor is connected to Pin 1 of the serial interfaces
(except on the interference filter). The housing should be earthed in
order to ensure the best degree of immunity to interference. In
addition, 0V should be grounded in the vicinity of the power supply (in
accordance with the regulations of the Society of German Engineers).
Both interfaces are RS232/TTY and have the same pin assignment. For TTY a total of 2 current loop sources
(A+B) are available to both interfaces. The communications cable PCS 736 is connected in such a way that
both current loop sources are used for communication and are thus not available for programming.
■ Pinning
JD 25 (female)
(rear side view)
13 TTY-Receiver +
12 20 mA Current source A (B)
0 Volt (GND) 24
10 TTY-Transmitter +
0 Volt (GND) 21
8 RS 232 DCD
RS 232 output DTR 20
7 0 Volt (GND)
TTY-Transmitter - 19
6 RS 232 DSR (free)
5 RS 232 Input CTS
4 RS 232 Output RTS
Courrent source 20 mA B (A) 16
3 RS 232 Input RxD
2 RS 232 Output TxD
TTY-Receiver - 14
1 SHIELD (chassis)
11
Function
Interface 2 (COM) is for communication with the programmable controller. In conjunction with the
programmable controller the TTY/RS 232 switch (No. 2) must be set to the TTY position. Only the data lines
TxD or RxD (4 lines) are required for communication. The cable connections are described in Section 5.2.1.
Interface 1 (PROG) is for programming. It is set unalterably to 9600 baud, 7 data bits, 2 stop bits and EVEN
parity. Switch 1, located beside the interface plugs, is used for switching between TTY and RS 232. For
cable connections see Section 5.2.2.
In addition to the internal RAM, an EPROM or EEPROM cassette can also be plugged into the 48-pin socket
connector. This cassette can be programmed in the OFFLINE MENU. To erase the EPROMs they must be
removed and erased using a commercially available erasing unit. EEPROMs are erased internally and do
not, therefore, need to be removed (they are permanently soldered in place).
In each cassette 2 additional data records of 32 kByte each can be stored (e.g. 2 languages, which can
be selected in the OFFLINE MENU).
ATTENTION !
When inserting or removing the cassette during operation,
the RESET button must be pressed at the same time. If this is
not done, a program crash is unavoidable. This will not
destroy the unit, but it will cause an inevitable loss of date (if
DIL switches 9 and 10 are ON). If the write protection jumper
on the cassette is in the »OFF« position, even EPROMs can be
overwritten!
12
Function
This capter contains information needed for overall planning of the operating concept. This chapter is not,
however, intended as a substitute for the machine-specific documentation. End users will require this as
well.
In principle, all variables must be declared before they are inserted into a text. In the same way, texts that
are to be used in menus must be formulated beforehand.
2.4.1.1 TEXTS
1. 128 OPERATING TEXTS: 2-line texts, used as DEFAULT TEXTS, as ACTUAL VALUE MENU
TEXTS and as SETPOINT VALUE MENU TEXTS.
2. 128 MESSAGE TEXTS: text pages, that can be up to 32 lines long. These texts are unalterably
assigned to the message bits and are displayed as INFORMATION, WARNINGS and
MALFUNCTIONS:
3. 1 HELP TEXT: The HELP TEXT is a (max.) 32-line text page, which can be brought into the display
at any time during ONLINE operation by means of the [HLP] key.
In those texts that take up more than 2 lines the user can at any time switch to the lower pairs of lines with
[ARROW DOWN] and switch back to the first pair of lines with [ARROW UP]. If a text consists only of one
line, the 2nd line is dark.
Inside the texts variable sections are realized using VARIABLE. The conversion of numeric and logical values
into a displayable form is the task of the PCS 110. During programming the PCS 110 thus requires not only
the positioning identification in the text, but also a variable definition. This definition contains, in addition to
the type, the length of a variable. These lengths must be taken into account when formulating the texts.
Excess lengths are signalled during programming. Apart from loading the (usually constant) variable value,
no additional programmable controller program is necessary. In all priorities except FAULT PRIORITY the
variables are cyclically refreshed; all values in the display originate from an inseparable data exchange cycle.
Since variables can also be represented in text form, a knowledge of the STRING variable format is extremely
important for configuring (text distribution).
Each menu is a collection hof from 1 to 128 OPERATING TEXTS. The programmable controller can only
open a menu; further operations and closing of the menu are the responsibility of the operator alone. As
of Version 100.304 the forced closing of menus by the programmable controller by means of a
communications reset is also possible.
13
Function
2.4.1.2 VARIABLES
Variable identifiers can be employed in all texts. They consist of the symbol @ and 2 capital letters. The »@«
represents the first variable position. From this position on, the PCS reserves space for the variable. The
representation form an the length are taken from the variable description. The 3 substitute characters
themselves take up no length. A maximum of 4 variables per text line may be employed. When formulating
texts the additional variable lengths in each line must be taken into account.
A distinction is made between INTERNAL and EXTERNAL variables. The source values of the EXTERNAL
variables are in the programmable controller. An appropriate variable description must be drawn up for these
variables. With some variable types, scaling is possible, i.e. a given range of values in the programmable
cotnroller is displayed in another range of values in the PCS 110 (limitation: the multiplier must be positive!).
With all BIN variables the number of digits before and after the point and the limit are programmable (as
constants).
Caution !
1. BIT: A character string is assigned to each of the two possible states of a bit. The character string is
freely selectable and can be up to 40 characters long. The string itself must not contain any variables. The
amount of space to be reserved is determined by the longer of the two instances.
2. (C)STRING: A character string can be assigned to each value of a data record (exception: Value 255).
The maximum length is 40 characters. The amount of space to be reserved is determined by the longer of
the two instances. The string itself must not contain nay further variables.
3. BCD, BCD-1, BCD-2, BCD0-1, BCD0-2: Numbers with a freely selectable number of digits (BCD,
BCD-1, BCD0-1: 1..4 / BCD-2, BCD0-2: 1..8) are represented. These numbers must already by present
in BCD format. It is not possible to display a decimal point. Die Formate BCD und BCD0 unterscheiden sich
lediglich dadurch, daß bei BCD Vornullen unterdrückt werden, während sie bei BCD0 dargestellt werden.
4. BIN, BIN-1, BIN-A: The 16-bit value of a data word is represented as an unsigned number
(KH0000...KHFFFF) in fixed-point format. Scaling and decimal point representation are possible. BIN-2,
BIN-B: The 32-bit value of two data words (HIGH, LOW) is represented as an unsigned number. Decimal
point representation is possible, but not scaling.
5. VBIN, VBIN-1, VBIN-A: The 16-bit value of a data word is represented as a signed number
(KH8000...KH7FFF) in fixed-point format. Scaling and decimal point representaion are possible. The sign
is input using the [+] and [-] keys. VBIN-2, VBIN-B: The 32-bit value of two data words is represented as
a signed number (8000 0000 ... 7FFF FFFF). Decimal point representation is possible, but not scaling.
6. WORD: The 16-bit value of an MW or DW is shown in bit format. It is possible to position the cursor on
the individual bits using the [+] and [-] keys. An individual bit can be reset by pressing the [0] key and set
by pressing the [1] key. This data format requires a fixed number of 17 characters space in a line.
14
Function
AP, CLOSED
Identifier for instance
AP, OPEN
Text for bit value 1
Variable AB
■ If Bit D30.15 (= M+60.7) = 0, the following default text 0 appears in the display:
■ If Bit D30.15 (= M+60.7) = 1, the following default text 0 appears in the display:
If this variable is used in a setpoint value menu, Bit D30.15 (= M+60.7) can be set using the [+] key and
reset using the [-] key. Alteration is performed immediately after the key is pressed. The remaining bits of
DW 30 (= M+60) are not influenced during writing back.
15
Function
Name of variable
If the variable is used in a setpoint value menu, the value in DW 31 (= MW+62) can be decremented down
to 0 using the [»-«] key and incremented up to KH0002 using the [+] key. An altered value is not written back
into DW 31 (= MW+62) until [ENTER] is pressed or until leaving the variablen.
ATTENTION:
1. The bits in DL DW 31 (= MB+62) are ignored during reading; after writing back they are set to 0. This
is an aid for determining alterations via the programmable controller program.
2. If the old value is not altered, writing back does not take place (not even Bits 8..15).
4. The limitation depends on the number of instances programmed; the minimum value is always 0.
5. At least 3 instances must be indicated, otherwise the variable must be declared as BIT.
16
Function
Name of variable
STATUS DW 2 in DB 5: 0
If the variable is used in a setpoint value menu, the value in DW 32 (= MW144) can be decremented using
the [-] key and incremented up to KH0002 using the [+] key. In contrast to STRING, an altered value is
immediately written back.
ATTENTION:
1. The bits in DL DW 32 (= MB+64) are ignored during reading; after writing back they are set to 0. This
is an aid for determining alterations via the programmable controller program.
2. If the old value is not altered, writing back does not take place (not even Bits 8..15).
4. The limitation depends on the number of instances programmed; the minimum value is always 0.
5. At least 3 instances must be indicated, otherwise the variable must be declared as BIT.
17
Function
Name of variable
Variable format
Lower limit
Upper limit
Length: 10500 mm
123456789012345678901234567
The 3 leading zeros are suppressed because here the vaiable format BCD takes place! If you want to display
the leading zeros just use the variable format BCD0-2 instead of BCD-2!
ATTENTION:
3. Intermediate values are not written back. Writing back does not take place until the [ENTER] key is
pressed or until leaving the variable.
4. Balancing inputs are possible: in the example above [10+] would lead to the intermediate result 10510.
As this is an intermediate result, writing back does not yet take place (although the cursor is no longer
flashing) !
5. Leaving the input field with a value outside the limits is impossible.
6. The sign keys can be used for incrementing and decrementing (with auto repeat).
18
Function
The BIN variable formats are divided into the following subgroups:
1. BIN-1 X X X
2. BIN-A X X
3. BIN-2 X X
4. BIN-B X
5. VBIN-1 X X X X
6. VBIN-A X X X
7. VBIN-2 X X X
8. VBIN-B X X
The difference between (V)BIN-1 and (V)BIN-2 and between (V)BIN-A and (V)BIN-B respectively is the
method of editing:
■ BIN-1, BIN-2: Pocket calculator input with different pre-point and post-point input;
■ BIN-A, BIN-B: Displacement (beyond the decimal point).
Name of variable
Source-DW = DW 35 (= MW+70)
Variable format
19
Function
Text number
ATTENTION:
You should then check the tolerance limits because the inaccuracy becomes larger than half a step
with on the display. Select a larger display area using decimal places before and after the decimal point.
20
Function
Display as default text 15 if the value KHAA55 is in DW 36 (= MW+72; for marker range initial address MW50
= MW 122):
STATUS DW 2 in DB 5: 0
If the variable is used in a setpoint menu the cursor (small cursor) can be moved bit by bit using the [+] and
[-] keys. The bit with a flashing underline can be set to 0 or 1 using the [0] or [1] keys. A changed value is
not written back until [Enter] is pressed or the variable is left in word 36 (MW 122).
CAUTION:
■ The WORD variable format takes up a fixed number 17 character in the display (maximum valency 8
bits are separated from lower valency 8 bits by "SPACE").
21
Function
As well as user-defined variables, there are also 26 internal variables with fixed definitions available (see
following table). At present only the variables from ZA upwards are used (expansion from YZ downwards
is possible!).
Variable type and display length can be taken from the above list. If individual or all internal variables are not
required, the identifiers can also be used for external variables. The internal variables refer in most cases to
the date and time of the built-in real-time clock.
If this real-time clock is used in any form, an operating text for setting the clock, containing the relevant
setpoint variables, must be programmed. Furthermore this text must be integrated into a setpoint value
menu. In order to avoid ambiguities in the case of seconds overflow, the relevant variables should all be used
in one text.
22
Function
ZU, ZV: Here the rotation time in seconds in the message memory can be displayed or changed. A
change is valid only until the next RESET. The cange is not secure against a loss of supply
voltage.
ZX: Here the maximum number of faulty (repeated) packages since RESET can be displayed. It
refers to 100 packages and is a measure of the security of the data transfer. This is in turn
dependent on the cable length, the cable type and the level of electrical and magnetic
interference. A fault figure of 2% is acceptable.
ZW: Here the preset startup procedure can be displayed in symbolic form. This internal variable
can only be changed in the OFFLINE MENU. It is stored in the real-time clock and is secure
against a loss of supply voltage (but not write-protected).
All variables are automatically read out of the given data words by the PCS. This also applies to setpoint
values. With setpoint values the value read out is represented as a preset value (see also 2.4.2.3).
■ In all priority classes except FAULT MESSAGES constant refreshing takes place. The resfreshment
rate is, in the most favourable case, 8 per second. It is however dependent on the programmable
controller cycle time, the baud rate selected and the number of variables (currently) represented.
■ In FAULT PRIORITY refreshing takes place only when a new text or a new pair of lines (help lines 3..32)
is displayed (with limitations the internal clock can be displayed for standstill determination).
■ A priority change alone does not cause refreshing. If the FAULT PRIORIY is temporarily left, the
variable value that was being displayed during the original call appears (in memory mode FIRST
MESSAGE).
■ There is no difference between internal and external variables. Until the variable values have been
transferred, empty fields are displayed (approx. 1 programmable controller cycle long). If the value
read in is outside the limits stored in the PCS 110, inverse fields are displayed in the variable field.
23
Function
In the PCS 110 up to 10 priorities can be switched on or off. The lowest priority (0 = DEFAULT TEXT) is always
switched on. In principle, the highest (acitve) priority class is always displayed. Priorities 5 to 0 can be limited
by the programmable controller (from the highest to the lowest). If a priority is deactivated, the system returns
to the same place as before limiting.
*) These priorities are only activated if they are not locked out by the prog. cont.
24
Function
The operating texts 0...15 are used as default texts (they can, however, also be used in menus). The
programmable cotnroller alone determines which of these default texts is displayed. The numeric and
control keys have no function here. If they are nevertheless pressed, the acoustic error alarm is suppressed,
so that control keys can be used for control purposes. Both setpoint and actual values can be used as
variables. Setpoint variables can, however, not be input. All variables are refreshed cyclically.
DEFAULT TEXT No. 0 has a special position; it appears immediately after the PCS 110 is switched on, even
if communication with the programmable controller has not yet been started. In the standard file supplied
it consists simply of 4 colons; the variable that may be present can not be displayed until communication
has begun.
There are 15 setpoint value menus and 15 actual value menus available. The menus of both levels are
designated with numbers from 1...15. A menu consists of one or more nodes. An operating text (0...127)
can be assigned to each node.
Within a menu further nodes can be reached by means of the arrow keys; the structure is freely
programmable. The first node indicated is the entry node. When the menu is called up, the system jumps
to this entry node.
■ OPENING THE MENUS: The programmable controller program writes a menu number
(1..15) to the DR 14 (= MB+29; here MB 79) of the command word.
■ CLOSING THE MENUS: The menu is closed by the user. They can be closed only in the
menu nodes provided for this purpose. In the setpoint value menu the ENTER key must be pressed,
in the actual value menu the CLR key (alternative in actual value menus: ENTER or CLR/ENTER;
selectable by programming).
Each node can be individually declared as an END NODE or as a NON-END NODE. This declaration can
prevent unintended closing of the menu
As of Version PG110.301 a setpoint value menu can only be closed when the
setpoint value agrees with the value read out of the programmable controller.
Between writing back and repeated reading out, 1 programmable controller
cycle is guaranteed. In this way interlockings or variable min/max comparisons
can be carried out by the programmable controller. If the comparison is
negative, the cursor remains in this input field. In this case an INFORMATION
text can also be triggered in the programmable controller, which may have to
be cleared with [CLR].
25
Function
Each of the up to 30 possible menus can have any structure desired. If complex structures are to be realized,
it is advisable to proceed as follows (separately for each menu):
■ First sketch out the structre on a piece of paper, showing the node connections with lines in various
colours (different colour for each arrow key).
■ Then assign an operating text number to each node. The same operating texts can be used in
different menus (saves memory space).
■ Designate each node from which closing of the menu is to be forbidden with an »N«.
■ Then designate all nodes with the desired numbers (1..255).
■ Formulate a program line for each node, taking all parameters from the sketch. The entry node must
be the first to appear, the sequence of the remaining nodes can be chosen at will (provided they all
belong to one menu).
Programming of the menu nodes is described in Section 3.2.6. During programming the PCS 110 checks
the menu definitions for plausibility. It must be ensured that menus do not distintegrate and that from each
menu point an end node can be reached. Apart from this there are no restrictions, i.e. within each node
any desired target node within the same menu can be assigned to any arrow key.
When formulating the operating texts care should be taken to achieve good user guidance; nodes
WITHOUT variables, which serve simply for user guidance, are quite possible. As the structure of the menus
is later invisible, the special characters ARROW UP, ARROW DOWN, ARROW RIGHT and ARROW LEFT
(see character set) should be used as an aid to clarity (@5E = arrow up, @5F = arrow down, <, >). In each
node it should be clear how, for example, the END node can be reached.
A maximum of 15 of the actual value menus that can be opened by the programmable controller are
available. The variables can be both setpoint values and actual values; they are constantly refreshed (but
they are not alterable). The controller is started when a value > 0 is written to Bits 0...3 of the command word.
As soon as this menu number > 0 is recognised, the PCS sets this number to 0 again in the same data
exchange cycle. If, at this time, a higher (or equal priority) is selected, the menu number is stored in the PCS
(not secure against loss of supply voltage) until the higer (or equal) priority is switched off.
26
Function
The same rules apply for setpoint value menus as for actual value menus; however as setpoint declared
variables they are all alterable. The 1st setpoint value is continuously underlined and frozen. If this setpoint
value lies outside the limits defined, inverse fields are displayed instead of the variable. When an deit key
is pressed once, the permitted value (MINIMUM VALUE or MAXIMUM VALUE) is displayed. If the setpoint
value has been changed, the input field is marked with a flashing underline (in the case of numeric values
this is below the last position, in the case of STRING and BIT variables it is below the 1st position).
For fetching variables the following rule applies: the underlined variables is only fetched once. All other
setpoint and actual values are constantly refreshed. If the underlined variable is quit after an alteration, the
value is read again and compared with the edited value at the earliest one programmable controller cycle
later. Thus even context-sensitive setpoint values can be used within a menu node.
ATTENTION !
If the variables refer to magnitudes smaller than 1 data word (BCD 1...3 digits, STRING), the leading bits
are handled in accordance with the following logic:
■ When preset values are read in, leading bits are ignored (i.e. if they are set, this dies not result in the
display of inverse fields).
■ During writing back they are set to zero.
■ With BIT variables all bits remain unaltered.
On the basis of these bits a programmable controller program can determine whether an alteration has been
made.
27
Function
BIT PLUS Sets a bit that was 0 to 1 and writes back variable;
MINUS Deletes a bit and writes back variable;
ENTER Closes menu, if permitted.
* ARROWS Leaves this variable, if permitted. The next variable or the next
node in the direction of the arrow is searched for.
STRING / * PLUS Increments a variable, provided the value lies within the limits;
CSTRING**) * MINUS decrements a variable, provided the value lies within the
limits;
CLR restores the old value in the display;
ENTER sends off the selected value, provided it has been altered;
* ARROWS sends off value, provided it has been altered and not yet sent
off and seeks for the next variable or the next menu node in
the direction of the arrow.
28
Function
If several setpoints value variables are used in a text, these can be reached with the arrow keys. If there
are several nodes in an activated menu, the arrow keys have a double meaning. If this is not desired, then
only one setpoint variable per node can be declared.
ARROW LEFT / RIGHT: If several variables are used in the text, the two lines are regarded as lying one
next to one another and the next variable is searched for. If the current variable was already the last
or the first, the next node is searched for and repositioning takes place to the 1st variable at the top
left. If there is no node in the direction of the arrow, an acoustic error alarm sounds.
ARROW DOWN / UP: If variables are distributed in both lines, the first variable (left) in the line
corresponding to the direction of the arrow is searched for. If there is no setpoint value variable in this
line, the next node in the direction of the arrow is searched for. If there is no node there, an acoustic
error alarm sounds.
ARROW DOWN in the 2nd line and ARROW UP in the 1st line always search for the next node.
In a new node repositioning always takes place to the 1st setpoint value variable top left !
Each mode can be defined as an END node or as a NON-END node. In an end node the [ENTER] key has
the effect of closing the setpoint value menu. The closing of a menu can be detected in the programmable
controller programm with the following logic:
In the DR of DW 11 (= MB+23) the indicated priority is signalled back. If the indicated priority = 2 and the
current priority is < 2, a menu is closed. The [ENTER] key should not be used as a closing criterion, as the
[ENTER] key signal has a higher priority than the writing back of an altered setpoint value.
As of Version 301 there is an alternative PCS status available: »STATUS-BIT«. If this is used,
the 1-> 0 transition of bit 1 in DW 11 (=M+23.1) can be used as the criterion for determining
whether the user has closed the setpoint value menu.
29
Function
In these priority classes (3,4 and 5) texts are not addressed using a number; the texts are called up by setting
a bit. A MESSAGE TEXT with a maximum of 32 lines is assigned to each of the 128 bits. For each of the
128 texts an individual MESSAGE PRIORITY can be set (determined during programming). The message
priorities are:
These priority classes differ only in priority level, not in function (exception: variable refreshing, see below).
For each priority class individual storage procedure and display procedure can be set by the programmable
controller (and are thus changeable at any time).
30
Function
In principle it is attempted to enter the appearance of the edges in their correct sequence in time. However,
the following limitations exist: as the reading out of the bits has a relatively low priority, with short
programmable controller cycle periods this task would be performed only in every 5th or 6th data exchange.
With cycle periods longer than 50 milliseconds and a baud rate of 19200 baud this task is performed in
each packet, so the term »sequence in time« is identical with the phrase »in successive« programmable
controller cycles« (see Section 5.3).
If several bits are set in a cycle, the lowest text numbers have a higher priority.
The deletion procedure can be set individually for each message bit. They are determined during
programming. There are 4 deletion modes:
1 No manual deletion
The text remains switched on, as long as the corresponding bit = 1. The bit is simply read by the PCS.
The operator prompt LED is out.
The text is switched by a 0 -> 1 transition and must be deleted using <CLR>. In addition, the message
bit in the programmable controller is deleted by the PCS. For this deletion procedure the message
bit in the programmable controller program may only be set once (no constant assignment !).
On pressing <CLR> the operator promt LED goes out at once, the message is output as a result of
the message bit deleted by the PCS.
The text is switched on by a 0 -> 1 transition. It can be switched off at any time with <CLR> key,
regardless of the status of the message bit. The message bit must be reset by the S5 program and
the message does not appear again until there is a 0 -> 1 transition. The message bit itself is not
affected by the PCS.
The text is switched by 0 -> 1 transition. The text can only be switched out with the <CLR> key when
the message bit = 0 again. The state of the message bit is indicated by the OPERATOR PROMPT
LED:
Flashing: Bit = logical 1, deletion not possible.
Constantly on: Bit = logical 0, the message can be deleted.
31
Function
For each of the priorities 3,4 and 5, individual display procedures can be set using 2 bits. 1 bit determines
the flashing of the (overall) text, the 2nd bit determines the depiction of a flashing underline (below the
overall text).
In principle all variables within the INFORMATION and WARNING priorities are constantly refreshed (as
of Version 304).
Out of the avobe the following simplication results: if only 2-line malfunction texts are used and a storage
procedure without manual selection possibility and without automatic rotation are chosen, the otherwise
necessary rotation is not required.
Example: For each malfunction the time of its occurence is to be displayed. For this purpose the internal
variable ZY (time) is used in all malfunction texts. If the 1st malfunction occurs, the variable is fetched once
and displayed. If, however, the text consists of 4 lines, the variable is fetched again after the display has
switched back to the main lines. A priority change caused, for example, by the HELP text described
below, would not trigger the refreshing; after returning the value of the variable is still the same as before
the priority change.
This is the highest priority stage that is normally accessible to the user. It is always switched on as long as
the [HELP] key is pressed. When the key is released, the priority is switched off again. This priority stage
cannot be locked out by the programmable controller and is thus always available to the user (provided a
HLP text is defined). The text required here is an independent text with a maximum of 32 lines. It should
contain all variables that could be of significance for possible error diagnosis (including internal variables !).
If, with the [HELP] key pressed, the [ARROW DOWN] key is used to switch on to the following lines and the
HLP key is released, the line numbers remain stored (not secure against loss of supply voltage). When the
[HELP] key is pressed again, the old pair of lines appears in the display. With [ARROW UP] (and the [HELP]
key pressed), it is possible to switch back to the main lines (1 and 2).
32
Function
The priority stage described here is triggered by 5 possible errors. The corresponding texts cannot be
changed. In Version G these texts consist of abbreviations of English word:
■ CONFIG: The selected startup procedure is stored unprotected in the RAM of the real-time clock
together with a cross-check sum. If this cross-check sum does not agree, it must be assumed that
these data (and also the time and date) have been destroyed by a program crash. This is certain to
happen, if an EPROM cassette is inserted during operation WITHOUT pressing the RESET BUTTON.
■ STARTUP: The selected startup procedure cannot be carried out. This fault always occurs, if the
external data cassette is selected when it is not plugged in.
■ PARAMETER: The selected database contains invalid data. This fault is usually the result of
incorrect programming, i.e. errors indicated during programming were ignored and the database
nevertheless selected.
■ TIME: This refers to time-out at the interface. This can have several causes:
1. The programmable controller program has been stopped.
2. The cable has become discontinous.
3. The handling block is not being called up cyclically.
■ CONNECT: Two successive invalid packets have been received. Even non-recurring procedures
(such as the fetching and setting to zero of a menu number) are not lost as the result of a simple
repetition. If, however, the repetition is also erroneous, this error message is issued. Information on
how to eliminate it is given in Section.
The faults TIME and CONNECT can be reset by the programmable cotnroller. When they occur, the PCS
110 goes to listening standby condition, the PLC signals the interruption of communications in the fault word
and the handling function block is formulated in such a way that in this case it sends no response packet
to the PLC. It awaits the command to resume communication via the programmable controller program.
This should - as with acknowledgement - be given manually using a button in the control cabinet or using
the STOP/RUN switch on the programmable controller (see »DESCRIPTION OF THE HANDLING
FUNCTION BLOCK«).
The faults CONFIG and STARTUP can be eliminated by reselecting in the offline menu.
The fault PARAMETER requires reprogramming of the PCS 110 (or is a consequence of the CONFIG or
STARTUP faults).
As of Version 301 the faults CONFIG, STARTUP and PARAMETER do not lead
an terruption of communication: despite the fault, KEYS, TIME, DATE
and LED's are transferred!
33
Function
The interface to the programmable controller program in Projects 1 and 2 is a marker range in the handling
FB to which parameters can be assigned (parameter VOBI in FB 210). In Projects 3, 4, 5 and 6 a data block
can also be specified with a maximum of 256 words (parameter UBDB in FB 210). In both cases there must
be a minimum length which is required by the maximum variable address (take care with double word
variables). No check is made so that the control system may go to STOP when it attempts to access these
variables for the first time.
Example: DW 40 (= MW+80) is the maximum specified word address during programming. Further
more a double word variable has been declared at DW 40 (= MW+80). This means that the
data block or marker range must have a length of 42 words (DW 0 to DW 41 inclusive), in other
words 84 bytes (for example MW 50 to MW 134).
MW No. (programmable controller) = Word No. (PCS) *2 + Initial MW No. (programmable controller)
Vice versa:
Word No. (PCS) = [MW No. (programmable controller) - Initial MW No. (programmable controller)] / 2
Example: The marker range fixed for communication should go from MW50 up to and inclusing
MW 148, i.e. the parameter VOBI in FB 210 must be assigned the value KY 50, 148.
The MW 126 must be altered in a setpoint menu.
All range values are to be understood as »from ... to ... inclusive«. Figures with an initial KH are to be
understood as Hex figures, numbers without specification are to be understood as decimal. The terms
»write« and »read« are to be understood from the point of view of the programmable controller.
DW0 - DW 2 (= MW+0 - MW+4) are used internally by the handling block FB 210
DW 3 (= MW+6) error word
34
Function
Direction
PCS P/C
Deletion procedure 1 --------->
Deletion procedure 2 <-------->
Deletion procedure 3 <---------
Deletion procedure 4 <---------
The communication between the programmable controller and the PCS should be exclusively performed via the
command word DW 14 (= MW+28) for writing and the PCS status word DW 11 (= MW+22) for reading. As a result of
the higher Priority of the key words DW 4 and DW 5 (= MW+8 and MW+10) the control keys (cursor, +, -, CLR and ENTER)
should be used with care.
In Projects 1 and 2 the variable range can only be used in this size in the market range MW0 to the marker range end
MW 244 (= 122 words).
35
Function
Each byte of the UBDB's bsw or of the parameterisable flag range VOBI is assigned to a defined task. An
offset of 50 is to be added for the example on diskette (projects 1 and 2) (Flag range from MW 50 -> MW
198). Brief overview:
36
Function
DW 1 (= MW+2) DW1 is reserved for string the base address of the PCS 810 base address
(initialized in FB 203 at the 1st cycle).
DR 3 7 6 5 4 3 2 1 0
MB+7 - - - - - - - -
In DL 3 (= MB+6) the faults detected by the PLC are recorded. Only bit 13 may appear:
These faults should result in the termination of communication (as realized in the data handling block). After
COMMUNICATIONS RESET by the programmable controller, the system returns to the old position in the
PCS. Only the start of a menu can (in the most exceptional cases) be lost.
The faults indicated in the older versions in MB+7 are (when communication is in progress) now only
indicated in the PCS STATUS WORD DW 11 (= MB+23 Bit 6).
37
Function
Hre, key depressions, clocktime, date and PCS status are read, the PCS control word, the LED's and the
display and storage modes are written, and menu invocations are read and written.
DR 4 7 6 5 4 3 2 1 0
MB+9 DIL1 DIL2 DIL3 DIL4 F9 F10 F19 F20
DR 5 7 6 5 4 3 2 1 0
MB+11 V ^ > < - + CLR ENTER
These key bits are at logical 1 for as long as the corresponding key is pressed and communication is running
without faults. If a fault appears, they are set to logical 0 via the handling FB. The control keys in DW 5 (=
MB+11) should be used only with caution.
Example: The ENTER key is used exclusively for terminating setpoint value menus, but since key
transmission has a higher priority than the transmission of the setpoint value, it can happen that
the key appears before the edited setpoint value. The key can thus cause false interpretations
in the S5 program. In order to avoid this problem, the PCS status DR 11 (= MB+23) should be
used as end criterion. The ENTER key can however be used, e.g. to call up a subsequent menu
(via the programmable controller).
Section 6.1 contains an example of edge detection (pos. and neg.) for all keys. On pressing and on releasing
each key you obtain a logical 1 for one cycle in each case.
38
DW 6 (= MW+12), DW 7 (= MW+14) DATE
DR 6 7 6 5 4 3 2 1 0
MB+13 Decade Year
DR 7 7 6 5 4 3 2 1 0
MB+15 Day (Day code 101) Day (Day code 100)
The date appears as BCD digits. It is, however, only valid when 1000's of years > 0. When no date has
been indicated, DW 6 = KH0000. If the year < 88, 20xx is assumed
DR 8 7 6 5 4 3 2 1 0
MB+17 Hour (00...23)
DR 9 7 6 5 4 3 2 1 0
MB+19 Second (00...59)
These contents are also valid only when DW 6 <> 0. A seconds clock rate can be derived from the seconds,
but it should be noted that the indication of a new time (especially with a long programmable controller cycle)
can be delayed for up to a second. Apart from this the contents are always valid, since the PCS always
refreshes DW 6... DW 9 in a cycle.
Application: Holding the rest time point of a machine. For this purpose the clock time is transferred (byte
by byte) to the variable range. The corresponding DW's are declared as 2-digit BCD variables
in the message text. After transfer the corresponding message bit is set.
39
Function
These DW's offer the opportunity of reacting to user inputs in the S5 user program.
DR 10 7 6 5 4 3 2 1 0
MB+21 Bit No. (binary) of message bit of displayed message
DR 11 7 6 5 4 3 2 1 0
MB+23 currently displayed priority within PCS (binary)
DW 10 (= MW+20) is valid only when the PCS is in the message priorities (3 4 or 5). A pointer in DW 10
(= MW+20) is then located on message bit field (DW 15...DW 22, = MW+30...MW+44). The value in the
DL 10 = MB+20 runs from KBOF to KB16 and the DR 10 = MB+21 (bit no.) from KB00 to KB0F.
The DR 11 (= MB+23) should always be used as the decision criterion when it is desired that the system
react to user inputs. For example, a priority < 2 (after having been = 2) shows that a setpoint value menu
has been left. Priority 6 (HELP) is not indicated here, priorities 8 and 9 are indicated.
If the PCS is in a message priority, bit 7 of DW 11 (= MB+22) = 0 (corresponding to message text numbers
0...127). If the PCS is in an operating priority, bit 7 of DL 11 (= MB+22) = 1 (operating text number (0...127)
+ 128).
If »STATUS BIT« is indicated when programming or if one of the faults CONFIG, STARTUP or PARAMETER
is active, an alternative status is provided in the DR 11 (= MB+23) (as of Version 304):
DR 11 7 6 5 4 3 2 1 0
MB+23 T/O ERROR HLP MALF. WARN. INFO. STPT. ACT.
Here the priorities 1...8 (beginning with bit 0) are shown. The HLP priority appears in bit 5. The transition and
OFFLINE priorities are both indicated in BIT 7. If one or more priorities are switched on, the corresponding
bits are at logical 1 (priority 0 is always switched on!).
40
DW 12 (= MW+24) LED STATUS AND DISPLAY MODE
DR 12 7 6 5 4 3 2 1 0
MB+25 9 10 Displ mode S Displ mode W Displ mode H
H-Bit L-Bit H-Bit L-Bit H-Bit L-Bit
DISPLAY MODES:
The display modes apply for the malfunction, information and warning priorities and are separately
adjustable.
DR 13 7 6 5 4 3 2 1 0
MB+27 9bl. 10bl. St.proc. malf. St.proc. warning St.proc. info.
H-Bit L-Bit H-Bit L-Bit H-Bit L-Bit
STORAGE PROCEDURE:
The LED bits in DW 12 (= MW+24) determine whether an LED is to light up, the LED bits in DW 13 (=
MW+26) determine whether an LED is to flash. If only »flash« is set, they light up (slightly) out of phase.
Manual switching on to other messages (with arrows left and right) is possible only in mode 01. If the facility
of switching on is desired in other modes, mode 01 should be set here first. At this moment the text currently
being displayed remains in the display and it is possible to page forwards or backwards with [ARROW
RIGHT (or LEFT)] up to the oldest or latest message.
The various deletion procedures and paging to the help lines are described in the Section on »MESSAGE
PRIORITIES«.
41
Interfacing
DR 14 7 6 5 4 3 2 1 0
MB+29 Menu selection (nominal values) Menu selection (actual values)
The DL 14 (= MB+28) must be written in the S5 program, the DR 14 (= MB+29) must be read and written
to.
1. Default text: This is one of the operating texts 0...15. It appears either when there is no higher priority
present or when the priority is locked to 0. This text number can be changed at any time by the
programmable controller. The text can contain both ACTUAL and setpoint values (these cannot
however be edited).
2. Priority limit: Priorities can be locked here. The handling FB sets this limit at restart to $F (enable
all priorities). Priorities 6 (HELP text) and 7 (communications fault) cannto be locked. If the priority limit
is set to 2 for setpoint value input, information, warnings and malfunctions cannot interrupt the menus.
3. Calling up menus: An actual or a setpoint value menu can be started by writing a value > 0 to the
DR 14 (= MB+29). As soon as the menu number is fetched, it is set to 0 by the PCS in the same cycle.
It follows from this, that a new menu should not be called up until there are 0's in the 4 bit positions.
The menu number is not fetched by the PCS while a menu is running (divided according to setpoint
and actual menu). A menu is always terminated by the user (see 2.4.2.2). If a subsequent menu is
then to be started, a new value can be written to DW 14 (= MB+29) while menu is running (as soon
as the 4 bits = 0). The default text is displayed briefly between the end of the old menu and the start
of the new menu. If this is found to be disturbing, a default text containing blanks should be called up
at every menu invocation.
An example for starting setpoint value menu 1 with F1 is described in Section 6.2.
42
Interfacing
DR 15 7 6 5 4 3 2 1 0
MB+31 M.7 M.6 M.5 M.4 M.3 M.2 M.1 M.0
DR 16 7 6 5 4 3 2 1 0
MB+33 M.23 M.22 M.21 M.20 M.19 M.18 M.17 M.16
DR 17 7 6 5 4 3 2 1 0
MB+35 M.39 M.38 M.37 M.36 M.35 M.34 M.33 M.32
DR 18 7 6 5 4 3 2 1 0
MB+37 M.55 M.54 M.53 M.52 M.51 M.50 M.49 M.48
DR 19 7 6 5 4 3 2 1 0
MB+39 M.71 M.70 M.69 M.68 M.67 M.66 M.65 M.64
DR 20 7 6 5 4 3 2 1 0
MB+41 M.87 M.86 M.85 M.84 M.83 M.82 M.81 M.80
DR 21 7 6 5 4 3 2 1 0
MB+43 M.103 M.102 M.101 M.100 M.99 M.98 M.97 M.96
43
Interfacing
DR 22 7 6 5 4 3 2 1 0
MB+45 M.119 M.118 M.117 M.116 M.115 M.114 M.113 M.112
A MESSAGE TEXT (0..127, max. 32 lines each) is assigned to each bit. Each text can have a specific priority
(3...5) and a specific deletion procedure.
ATTENTION:
In malfunctions variables are not constantly refreshed !
Before the exchange of data, all variables (setpoint and actual) must be written into the corresponding DW's/
MW's; after the exchange of data, only the setpoint values must be read back out of the DW's/MW's. It is
thus advisable to address setpoint values concisely.
The assignment of addresses to the individual variables takes place during the programming of the PCS.
The variable formats BCD, BIN and STRING use the data words right-justified, the format BIT can be used
on every individual bit (up to 16 BIT variables per DW). One and the same DW can however also be the
source for several variables (even if of different types). As setpoint value however, only one variable type
should be assigned to a data word (but one or more actual value variables can be simultaneously assigned
to this word).
Leading (unused) bits in setpoint values of the type STRING and BCD (length 1...3) are ignored during
reading, during writing back they are set to 0. The type BIT alters only the bit addressed.
Before restarting, setpoint values should be present in accordance with their MIN/MAX permitted values,
as they are needed as default values for editing. If they are outside the MIN/MAX range, inverse fields are
displayed; these can be exited as setpoint values only when they have been corrected.
With 32-bit variables the DW with the lower number is the higher-value word, the DW with the higher number
is the lower-value word.
Variables of the types BIT and CSTRING are signalled immediately after a change, all others are signalled
only after leaving the variable field or after [ENTER].
44
Interfacing
Communication carries on even during programming, i.e. the keys, LED's, the clock, the 0 -> 1 transitions
of the message bits, the PCS status and communications fields continue to be handled. Only the messages
in the display are not visible. While the EPROM's are being programmed, no communication with the
controller is however possible.
If DIL switch 7 is set (ON) or DATA ERROR is active, it is possible to reach the offline menu using CLR with
the HLP key pressed. If the data record with which it is intended to work is invalid, or if the STARTUP
procedure cannot be carried out, the OFFLINE MENU can be reached at any time. Before it is called up,
there is another security inquiry, which must be confirmed with ENTER. For terminating the OFFLINE MENU
there is a separate menu point.
ATTENTION:
■ if the active data record has been overprogrammed, or if the data source (RAM1, RAM2 etc.) has
been switched over, a partial reset follows. I.e.:
During this time the display is dark (approx. 0,5 s) and a PARTIAL RESET (with communication running) is
performed. This means that a setpoint value menu which may have been started will be terminated without
writing back setpoint values!
■ If the data record was not changed and also not switched over, the system returns to the old position,
i.e. a partial reset is not carried out.
45
Online
After selecting the menu item »EXIT« and pressing [ENTEr] the offline menu is selected (see above).
1. after MAINS ON and after pressing the RESET BUTTON at the rear.
2. after leaving the offline menu, if the parameter set was altered.
■ If the fault »PARAMETER« then appears, there are no valid data in the PCS 110.
■ If the fault »STARTUP« then appears, the selected start procedure cannot be carried out (e.g. no
MEMORY PACK plugged in).
■ If the fault »CONFIG« then appears, the check sum for the start procedure is incorrect. This can
be due to an empty battery and can be eliminated in the offline menu.
After selecting the data memory the PCS can be programmed by transferring an ASCII file. This menu item
must be terminated manually using the [HLP] key. Programmin is described in detail in Section 3.
46
Online
ATTENTION:
After selecting the source and target using the [+] and [-] keys, complete data records can be copied. For
identification the memory capacity occupied is displayed. In addition the first line of the HELP text appears
in the 2nd line. If a version number of the data record is marked here, this can be called up at any time using
the HLP key.
The PCS 110 recognizes the type of memory medium independently. If EPROM's have already been
programmed, they cannot be overprogrammed. EERPOM's are automatically erased.
■ CMOS 32 kBit * 8
■ Access time Tacc = 200 ns
■ Programming voltage Vpp = 12,5 V
■ Programmer algorithm: INTELLIGENT
ATTENTION !
47
Online
48
Online
3 PROGRAMMING
Programming is performed by data transfer from a programming unit or PC. A text file must be created,
containing all texts, variable declarations, group assignments and parameters in the form shown below. If
the file is created on a PC, it must be ensured that it is a pure (7-bit) ASCII file (umlauts ÄÖÜ = </>). The
file can be transferred using the DOS commands MODE and COPY:
On the programming unit you should select output to printer (standard print) without title block and without
margin. In addition, the busy input must be activated and connected to RTS on the PCS.
When this mode has been selected, the serial interface is ready to receive data. Either XON/XOFF protocol
or RTS/CTS protocol is possible. If the PCS is not ready, RTS is at logical LOW and XOFF is
transmitted. When it is ready, RTS is at logical HIGH and XON is transmitted.
After the last programming instruction, you must return to the main menu using HLP. It is possible to abort
at any time using HLP (although this results in the »PARAMETER error« due to an incomplete data record).
It is possible to transfer partial data records: the beginning of the first file must be identified with »AE« and
the beginnings of further files with »AA«. Each file must end with »##« (see AE/## command).
As long as the system is ready for programming, at least the following line appears in the display:
Since the line number is reset at each AE or AA, it is advisable to write these commands into the first line
of the file(s).
ATTENTION:
49
Online
AE RECEIVE ALL
AA APPEND ALL *)
## END PROGRAMMING
ZV ALTER TIME
50
Online
■ Forward references are nto allowed. The following sequence must be adhered to:
1. IDENTIFY BEGINNING OF FILE (AE)
2. DECLARE VARIABLE
3. FORMULATE TEXT This section may be
repeated over and over
4. DEFINE MENU NODES in the sequence !
5. IDENTIFY END OF FILE (#)
■ The first character in a command must be left-justified on the line, otherwise the line will be interpreted
as a comment and ignored (do not select printout »WITH MARGIN«!)
■ The symbol (@) is used as introduction symbol for variables. It is followed by 2 capital letters as variable
identifier. The length of the variable identifier is taken from the variable definition.
■ The symbol (@) is also used as introduction symbol for special characters. It is followed by 2 HEX
numerals (00...7F), that describe the character equivalent (e.g.@61 = small »a«).
■ The symbolic parameters must agree in length, content and case (upper) with the setpoints, e.g. BIN-
1, STRING, etc.
■ A comment can be added after every command line, separated by a comma. This does not, of
course, apply for text parameters!
■ All commands and parameters must be separated by commas (do not confuse with »POINT«!).
■ Before or after a comma a blank can be inserted. This makes the data record clearer.
■ Where parameters are omitted, the separating commas must still be inserted if further parameters or
comments follow.
■ Left-justified blanks in texts are retained, right-justified blanks are ignored (apart from the first blank).
■ Parameters marked with * can be omitted if the standard presets are to be used. If however, further
parameters follow, that do not correspond to the setpoints or which must not be omitted, the commas
must be input.
■ »+« used as a sign must be omitted; »-« may be used only before VBIN parameters.
■ Don't translate the german idioms »SOLL« and »IST«. For setpoints and actual values. If you define
a variable, type them as they are.
51
Online
ATTENTION:
No comment may follow AE, AA and ## in the same line !
* AE-COMMAND *
This command designates the beginning of the 1st program file. Everything up to AE is ignored. The old
parameter record in the PCS is deleted.
* AA-COMMAND *
This command designates the beginning of subsequent files. Everything up to this command is ignored.
The old (valid!) parameter record remains valid.
* ##-COMMAND *
This command designates the end of each program file. After the command comprehensive checks are
performed in the PCS. If programming is interrupted permaturely (with HLP), this results in a invalid parameter
record.
* MV/BV-COMMAND *
Serveral lines on a page have consecutive identical page numbers. Operating texts have a maximum length
of 2 lines. Message texts have a maximum length of 32 lines. Each line (operating text or message text) can
contain up to 4 variables (@ and two letters). The maximum text length (text + length of individual variables)
is 40 characters.
52
Online
* HV-COMMAND *
1 PARAMETER: * TEXT
Here the text lines for the HLP text are input (maximum 32 lines; max. 4 variables per line).
* PV-COMMAND *
SYNTAX: * PV,*from-number,*to-number,value
FROM-number (is 0 if not present)
TO-number (is 127 if not present)
VALUE: »S« or »H« or »W« (malfunction, information or warning)
EXAMPLE: PV,0,126,S => message texts 0...126 (inclusive) have malfunction priority
PV,127,127,H => message text 127 has information priority
* LV-COMMAND *
SYNTAX: * LV,*from-number,*to-number,value
from-number is 0 if not present
to-number is 127 if not present
VALUE: »1« .. »4«
Mit dem LV-Befehl wird festgelegt, welches Löschverhalten eine Meldung besitzt.
53
Online
* ZV-COMMAND *
Z Rotation time in seconds. Value range: 1...60, default value = 10; if several messages are
switched on, the messages are advanced using »CYCLIC« storage procedure with time input
here. The input is made in seconds.
* IMT-COMMAND *
SYNTAX: IMET,key
Using one of the above entries it is possible to change the standard termination key CLR. With CLRENTER
termination is possible with both keys.
EXAMPLE: IMET,CLRENTER
After the command the actual value menus can be closed using CLR or ENTER.
54
Online
* PV-COMMAND *
SYNTAX setpoint or actual value menu: SV,Menu no.,node no., arrow left, arrow right, arrow down,
arrow up, text number, E/N
The default parameters are 0 (for reactions to the arrow keys) or E (definition for an end node).
EXAMPLE:
======================= Declaration of variables AA: =========================
VV,AA,30,SETPOINT,BIT,0
AP,OFF
AP,ON
======================= Declaration of variables AB: =========================
VV,AB,30,SETPOINT,BIT,1
AP,OFF
AP,ON
======================= Operating text (16) for operator guidance: ===============
BV,16, --- SWITCH ON COOLING FAN ---
BV,16, <= COOLER INLET COOLER OUTLET =>
======================= Operating text (17) for editing variable AA: ===============
BV,17, CONTROLLER FOR COOLING FAN INLET
BV,17, ON = + OFF = - STATUS: @AA
======================= Operating text (18) for editing variable AB: ===============
BV,18, CONTROLLER FOR COOLING FAN OUTLET
BV,18, ON = + OFF = - STATUS: @AB
======================= Declaration of setpoint value menu no. 3: ===============
MENU No. / Nodes / LEFT / RIGHT / DOWN / UP / TEXT / END NODES ?
SV, 3, 100, 101, 102, 0, 0, 16, E
SV, 3, 101, 100, 100, 100, 100, 17, E
SV, 3, 102, 100, 100, 100, 100, 18, E
After calling up the operating information, (starting menu no. 3), the operator can select the INLET with arrow
left or the OUTLET with arrow right. From there the pressing of any arrow key results in a return to the
operating information. In the root node (node 100 with text 17) the arrows up and down are locked out.
55
Online
* V V-COMMAND *
Using the command it is possible to define variables. The first 4 parameters are identical in sequence and
meaning for all variable types. Recollection (regards only to the projects 1 and 2; see also chapter 2.4.3):
Flag word no. (PLC) = word no. (PCS)*2 + offset flag word no. (PLC)
Vice versa: word no. (PCS) = [flag word no. (PLC)-offset flag word no. (PLC)] / 2
No further parameters, but at least 3 lines with AP commands must follow (i.e. the text representation of
each permitted value).
* TYPE: BIT *
PARAMETER : ■ Number of digits (1...4 with BCD-1 / BCD0-1, 1...8 with BCD-2 / BCD0-2)
(additional) ■ *Min. value, default = 0
■ *Max. value, default = number of digits with 9
56
Online
* TYPE: WORD *
No other parameter
All inputs msut be decimal values. With VBIN variables the MINUS sign may appear as the leading character
in the values; if there is no MINUS sign, PLUS is assumed.
The MIN and MAX values determine the conversion factor for scaling. The MAX values must always be
greater than the MIN values (i.e. only positive conversions are possible). The PCS calculates the conversion
factors itself. The following limitation applies:
As the PCS works internally with 32-bit integer arithmetic while the representation can also comprise 32
bits, the following strategy is employed: if the differences are not divisible without a remainder, it is attempted
to abbreviate the fraction without a remainder. If this is not possible, a warning is issued and the parameters
must be changed manually. If all scaling values are omitted, a 1:1 representation is assumed. If only
individual parameters are missing, it is attempted to form the parameter from the digit number.
If the number of places after the point > 0, a decimal point is inserted automatically (fixed point). The decimal
point has no influence on the value. The point position must be added to the number of places input when
evaluating the number of places required.
* AP-COMMAND *
The command follows STRING and BIT variable declarations and determines their representation.
EXAMPLE: VV,AB,40,ACT,BIT,3
AP,open
AP,closed
MV,1,valve position of V43 : @AB
If message 1 (information..malfunction) is now displayed, the PCS fetches data word 40 from the
programmable controller and ches bit position 3: if it is 0, »OPEN« is output, otherwise »CLOSED«. Special
characters may be used in the instances, but not variables.
57
Online
* STATUS BIT *
PARAMETER: none
If this instruction is programmed, the priority in DR 11 (= MB+23) is available not as a binary number but
bit-by-bit (see 2.4.3.2 PCS STATUS).
Two RAM's of 32 kByte each are available for programming. The RAM's are backed up by a lithium battery
with a lifetime of 7 years. In addition, 2 EPROM's of 32 kByte each can be inserted (adapter). There are thus
2 (3) databases. It is possible to switch between them in the OFFLINE MENU.
For creating texts, menus and variables the following remarks apply:
1. The total possible number of lines cannot be indicated, as the texts are stored in compressed form
and memories for texts, menu nodes and variable instances are dynamic.
2. Text compression: consecutive blanks take up one byte, each line takes up an additional byte and
for text management a total of approx. 714 bytes is needed. In addition, each text page created takes
up a further byte.
3. Per text line 3 bytes are required (as well as the text itself).
4. Deleted texts take up no space (after »AE« all texts are deleted).
5. If the times ZV,S and ZV,Z are not indicated, the default values apply.
6. The text for communications errors are stored in the program EPROM and cannot be altered. They
are installed in Version G as English abbreviations.
7. Each text line may include a maximum of 4 variables, the maximum length of an individual variable
is 40 characters.
8. Equal variable instances (character strings), even of different variables, are stored only once. If
storage space is restricted, it is possible to save space by using equal instances (on dummy
variables) instead of text.
9. Each variable created occupies 7 bytes in the head, in the rest of the page between 6 and 22 bytes,
depending on type.
10. The identifiers of the internal variables begin with »Z«. If the corresponding variables are not required,
the identifiers can be used for external variables.
11. The variable designators in a text have a length of 0 in the representation of the text. The space
reserved for the variable is automatically calculated from the number of digits before and after the
point; with character strings the length of the longest string applies.
58
Online
12. Variable instances are represented left-justified, blanks are thus relevant only inside or to the left of
the instance.
13. Blanks that may be present to be right of the variable instance are ignored.
14. Texts that have not been located are ignored, i.e. the previously displayed text remains in the display.
Signalling an unlocated text has no effect, the same applies to an unlocated default text (if the default
text 0 has not been located, an empty display appears after power-up).
15. If undefined menus are called up, the invocation is ignored.
16. Texts which are used in menu nodes must have been created, otherwise the node is invalid.
17. Each menu node created occupies 8 bytes.
18. For menus, 60 bytes are reserved (contained in the 714 bytes mentioned above).
Text design:
Each special character that cannot be obtained directly via the programming unit keyboard can be optained
using @ + 2 digits (HEX notation). The symbol @ itself can be obtained with @40. These special characters
can also beused in text instances of variables. A character set table is to be found on the first page of this
manual.
The variable instances are stored at the upper end of the memory, all other parameters at the lower end
of the memory. The memory space occupied during programming is shown in the display (M:xxxxx:yyyyy).
Since equal variable instances are stored once only, it is possible to save memory space by declaring so-
called dummy variables.
59
3.4 ERROR CODES
2 Parameter erroneous/missing
3 Num. parameter too great
4 Relation error with parameter
5 String parameter unknown
6 Num. parameter too small
7 Node number erroneous
8 Text no present
9 Menu no. erroneous
10 No successor must be end node
11 Error with num. parameter
12 String parameter not present
13 Page already created
14 Too many lines
15 Text too long
16 Unknown variable
17 More than 4 variables
19 Text number is greater than 127
22 Successor is itself a node
23 No successor and end node
30 Variable error
31 Variable already present
32 DW missing
33 Not SETPOINT/ACTUAL
34 Variable identifier erroneous
37 Bit indication incorrect (or missing)
41 Illegal AP command
55 @ error
61 Digit number with BCD
62 Max value too great or MIN value too small
63 MIN > MAX
64 DW with double word
65 Places before point
66 Places after point
67 Sum digit number
70 Scaling error
72 Prog. cont. MAX value too great or MIN value too small
73 MIN-MAX relation pogr. cont. value
74 General min-max error BIN-1 or BIN-A
75 Illegal AA command
88 Insufficient memory space
92 Variable is not complete
96 Non-end node does not reach end-node
97 Menu disintegrates
98 Successor error
99 Unknown error
If a fault occurs during programming, the fault number »xx« and the line number »yyyy« are displayed in the
first line (E:xx IN:yyyy).
60
Programming
|
AE |
VV, AB, 60, SETPOINT, BIN-1, 1, 2, 0, 2000, 0, 2048, --> TEMP. 1 (AB) IN DW 60 |
BV, 17, TEMPERATURE 1: @AB |
SV, 15, 1,,,,17 |
## |
|
Start each line at the left margin. The file is saved using <|>.
■ Connect the printer interface of the programming unit to the PCS 110 using programming cable PCS
732 (do not interchange cable ends).
■ Set DIL switch no. 7 to ON, if necessary.
■ Open the OFFLINE MENU by pressing [HLP] and [CLR].
■ Select serial programming using [+] and then [ENTER].
■ Select RAM 1 or RAM 2 using [+] or [-].
■ After concluding with [ENTER] a check is carried out to see whether the corresponding write
protection jumper is open (DIL switch 9 or 10). Follow the instructions given in the display.
■ There now appear 4 numerals (see Section 3) and the character »>«. Start transcription using
■ Briefly press <|>. After a short time error message 3 (Num. parameter too great) appears in the
display. Confirm the error with [CLR]. Error 16 (Unknown variable) now appears.
■ Confirm the error with [CLR]. Error 8 (Text not present) now appears.
■ Confirm the error with [CLR]. The characters ## and the following text now appear:
61
Programming
The representation range for variable AB in the PCS should cover 0 to 2000. However, with the number
of digits (1 place before the point, 2 places after the point) this variable cannot be represented. As the
variable is invalid, error 16 appears. Since the text length cannot now be checked, operating text 17 cannot
be created. As a result, error 8 appears.
■ REMEDY
VV, AB, 60, SETPOINT, BIN-1, 1, 3, 0, 2000, 0, 2048, --> TEMP. 1 (AB) in DW 60 |
You can now immediately output the file again via the printer interface, without leaving serial programming.
After successful transcription, programming is terminated with [HLP] and 2 * [ENTER].
3.6.1 PG 675
1. Create a DOK file:
»INPUT BLOCK INPUT DEVICE:FD1 BLOCK: #NAME«
2. Connect the printer interface to the PCS programming interface using cable PCS 232.
3. Transfer the DOK file:
»OUTPUT OUTPUT DEVICE: FD1 BLOCK: #NAME PRINTER: *«
3.6.2 PG 685
1. Before starting the S5 software the printer interface must be set, at operating level, to 7 data bits,
2 stop bits and EVEN parity.
62
Programming
3.6.3 PG 750
1. Before starting the S5-programming software the serial interface COM2 must be adjusted and
the printer output has to be diverted to this serial interface.
3.6.4 PC
1. In addition to the programming cable (PCS 737: 25 pins or PCS 739: 9 pins) an ASCII text editor
is needed. The text editor EDLIN is part of your operating system software and therefore always
present.
2. Open an ASCII file under any name and transmit the file with the following commands:
MODE COM1: 96,E,7,2,P
COPY Name COM1:
If an error appears the transmission stops until the error is receipt to the PCS 110 by CLR key. If you want
to break off the transmission early, you need to use [CTRL]+[BREAK] keys.
Attention!
In case you use MS-DOS version 4.xx, you need a Terminal Emulation Program
as PROCOMM, VTERM, KERMIT, TELIX or similar, because at that DOS version
the MODE resp. COPY command is not defined any more for the
serial interface !
63
Programming
64
Programming
■ FB 210: Handling FB; controls the data transfer between the send/receive mailbox and a data
block (Projects 3 and 4) or the parameterisable marker range (Projects 1 and 2). This
must be called up in cycles.
■ FB 211: SINEC L1 parameter assignment FB; assigns parameters to the system data range for
the L1 data transfer (only in Projects 1 and 3), resets the marker for the first cycle and
allocates the coordination bytes for the restart. This FB must be called up in OB 21 and
OB 22 (start-up blocks).
■ FB 212: Restart FB; this FB is called up when the control system is restarted or reset after a
communication failure. Client-specific assignments may be added to it.
■ FB 213: Emergency FB; this FB is called up after a communication error has been found. Client-
specific assignments in case an error occurs may be added to it.
■ DB1: This DB is only present in Projects 2 and 4 (AG 95 U). This block assigns parameters
for the system data range for the L1 data transfer. This DB must be stored in the
programmable controller and expanded or rewritten for the client's specifics. Rewriting
is essential if, for example, another data block is to be used for the send and receive
mailbox.
IMPORTANT
1. In addition to the marker range which may be required for communication and the data block for the
send/receive mailbox, the FBs also use scratch marker ranges:
Writing on these MWs does not interfere with FB 210 as long as it is not being used simultaneously
by interrupt programs. If these MWs are required by other FBs the contents must be rewritten when
they enter and saved when they exit. Do not write these MWs in interrupt programs.
65
Programming
2. The FB accesses the data block / marker range by beans of the TIR / LIR command. When
transferring to the control system the selection is to be made in the »WITH SYSTEM COMMANDS«
setting.
3. The DB (parameter SDB in FB 210/211) which among other things contrains the send and receive
mailbox for the communication as well as the communication DB (parameter UBDB in FB 210) must
not be in the programmable controller program EPROM. It should be generated in the start-up OBs
(unfortunately this is not possible in all programmable controllers using a formal operand, therefore
the generation is notart of the handling FB).
4. The FB 210 consists of a single network. Since in many ABs the interrupt processing only takes place
at the network end it may have to be modified if time-critical interrupt programs are used in such
programmable controllers (very theoretical case).
The implementation is restricted (apart form the cyclic call-up of FB 210) to reading and writing the DWs
/ MWs.
A summary error bit (EROR) allows the communication status to be evaluated by contact plan. If this error
bit = 1 the data transfer has been stopped. The communication can be restarted by resetting an RSET
marker. Furthermore, another marker is required for the restart RFLM. This is set after the first successful
run through the FB 210. It is also to be declared as a parameter when calling up the FB 211.
The enclosed FB 211 assigns parameters for the programmable controller for the data transfer with the PCS
110. The PCS takes over the master function for the L1 bus and addresses one programmable controller
as a slave with number 1. The parameter assignments must be made when the programmable controller
is restarted. Therefore the FB 211 must be called up from the OB 21 and OB 22 organisation blocks. The
parameter assignment is made by the block transfer command "TNB 14". This command stores the
parameter data in the system data range of the programmable controller (from address EA72H to EA7FH).
In the system data range it is specified which slave number the programmable controller has to respond
as, in which data range the send and receive mailbox is located and where the coordination bytes (KBS
= send coordination byte, KBS = receive coordination byte) are located. The FB assigns the system data
range so that the following data ranges are assigned for the SINEC L1 bus:
Caution !
The "SEDB" data block which must be assigned parameters in the FB 211 must in
no circumstances be described (at least not in the range from DW 0 and DW 71).
This is responsible for communication between the PCS and the programmable
controller (operating system). The PCS 110 user only has contact to the PCS
through the data block UBDB which has been assigned parameters in FB 210
(Project 3) or marker range VOBI (Project 1). The data exchange between the send/
receive mailbox and the PCS 110 is controlled completely by the FB 210.
66
Programming
The enclosed DB 1 assigns parameters to the programmable controller for data transfer with the PCS 110.
The PCS takes over the master function for the L1 bus and addresses one programmable controller as a
slave with number 1. The parameter assignments are taken from the OB 1 automatically when the
programmable controller is restarted. The parameter assignment itself is performed by modification of the
DB 1. These data are automatically filed in the system data range of the programmable controller. This is
where it is specified which slave number the programmable controller has to respond as, in which data
range the send and receive mailbox is located and where the coordination bytes (KBS = send coordination
byte, KBS = receive coordination byte) are located. The FB assigns the system data range so that the
following data ranges are assigned for the SINEC L1 bus:
Caution:
The "SEDB" data block which must be assigned parameters in the OB 1 must in no
circumstances be described (at least not in the range from DW 0 and DW 71). This is
responsible for communication between the PCS and the programmable controller
(operating system). The PCS 110 user only has contact to the PCS through the data block
UBDB which has been assigned parameters in FB 210 (Project 4) or marker range VOBI
(Project 3). The data exchange between the send/receive mailbox and the PCS 110 is
controlled completely by the FB 210 !
67
Programming
The enclosed FB 210 controls the data transfer between the market range to which the user may assign
parameters (parameter VOBI) and the send and receive mailbox for Projects 1 and 3. For Projects 2 and
4 a data block (parameter UBDB) is used instead of the parameterisable marker range.
Every time the programmable controller receives a "question package" sent by the PCS 110, in other words
a telegram containing utility data from the master, bit 15 in the KBE is reset by the operating system of the
programmable controller. This is a note for the user program, in other words for the FB 210, showing that
data have been received. The FB 210 can now decode the data which has arrived in the receive mailbox
and complete the necessary operations (writing, reading, and/or operations). The data to be read are
entered in the send mailbox whilst the data to be written (including and/or operations) are completely
directily with the parameterised data block or marker range. As soon as the complete package has been
completed the send and receive mailbox is cleared for the operating system of the programmable controller
when the FB 210 is exited.
The master, in other words the PCS 110, now automatically receives the data from the send mailbox of
the programmable controller as an "answer package" when the next data are exchanged (organised by
the operating system of the programmable controller). In other words this is a telegram which contains utility
data for the master. As soon as the answer package has been sent with data bit 15 in the KBE is reset
by the operating system. This is a note for the user program showing that the data have been sent from
the send mailbox.
When the PCS 110 has processed the data is sends another "question package". Bit 15 of the KBE is again
reset by the operating system. If the FB 210 now recognises that both the receive mailbox and the send
mailbox are free for processing by the user program, the whole process starts again from the beginning.
68
Programming
The rund time depends on the number of tasks in a "question package, in other words, data from the PCS
110 to the programmable controller. Normally the cyclic tasks 5, 6, 8 and 9 (see Section 5.3) are contained
in every package, i.e. 12 words data + length of task 5 are exchanged in cycles. Each task also requires
a header with a word. Since the length of task 5 depends on the number of external variables in the display
(0 to 24 words including headers if the data sources are not flush), a maximum of 40 words per data
exchange cycle are transferred. Since, however, the number of transferred data in L1 bus transfers is
restricted to a maximum of 64 bytes (i.e. 32 words), this task is treated in two data exchange cycles after
on another. The transfer of the time is only made every second and costs an additional 3 words. All other
tasks can be neglected for the average calculation since they only occur in some locations. With the aid
of the following table the average rund time of the FB 210 for processors in the 100 U and 115 U series
can be calculated depending on the event case.
The FB is designed such that if an error occurs the communication is aborted and the error signalled
externally. After this the communication must be consciously restarted via an input (parameter RSET). This
does not affect errors which can be repaired by repetition, of course.
■ INIT: Enter the client-specific setting for the restart; (FB 212)
■ COFF: Enter the client-specific setting for an error. (FB 213)
69
Programming
The specified times were measured with the aid of a digital output. This was inverted in each programmable
controller cycle. The processing time (overall reset programmable controller) have been deducted from the
measured time.
AG 95 U
Proj. 2 + 4 1 ms 16 ms 28 ms 21 ms 5 ms
AG 100 U
Proj. 1 + 3 3,7 ms 30 ms 40 ms 35 ms 10 ms
AG 115 U
CPU 942 5,0 ms 27,5 ms 37,5 ms 34 ms 8 ms
Proj. 1 + 3
AG 115 U
CPU 943 SI1 3,0 ms 14 ms 21 ms 20 ms 8 ms
Proj. 1 + 3
AG 115 U
CPU 943 SI2 3,0 ms 9 ms 15 ms 14 ms 1,5 ms
Proj. 2 + 4
70
Programming
UBDB: Projects 3 and 4 only. In this case the necessary DB for the interface between the programmable
controller user and the PCS 110 must be specified. It must either be transferred by the PCS or
generated in the OB 21 and OB 22, as in the case in the example. The length of the block must
be the number of words required by the maximum variable address, but at least 23 words, in other
words from DW 0 to DW 22. If the DB is to be generated by OB 21 and OB 22, the following
command sequence is to be entered:
SEDB: The data block number of the DB is to be specified in this parameter, which contains the send
and receive mailboxes. It must either be transferred by the PCS or generated in the OB 21 and
OB 22, as is the case in the example. The length of the block must be at least 72 words, in other
words from DW 0 to DW 71 (71 words will also be sufficient for Projects 3 and 4). If the DB is to
be generated by OB 21 and OB 22, the following command sequence is to be entered:
L KF+71
E DB xx (xx ... DB number)
RSET: Reset marker. As soon as this marker = 1, a reset is triggered and this marker is reset to zero.
It should be capable of being set by a pos. edge of a key. However, it is only evaluated after the
communication between the programmable controller and the PCS has been interrupted by an
error (eg. cable break or double repeat).
EROR: All-round error message. This bit is set after the communication has been irretrievably lost
(TIMEOUT). This bit is reset again as soon as the first error-free package has been received.
RFLM: Marker for the first cycle. If this is set to log. 0 (it is set to log. 0 automatically by the FB 211) checks
are several values are pre-initialised in the FB. After the first successful run, this marker is set to
log. 1.
VOBI: Projects 1 and 2 only. This is where the marker range required for the interface between the
programmable controller user and the PCS 110. A constant KY is to be specified here. The first
byte determines the first marker word of the marker range and the second byte the last word of
the marker range. Example: KY50,200 fixes the marker range between MW50 and MW200
inclusive.
TIMZ: Timeout time. A constant KF is to be entered here. The calculation of the constant is made as
described in Section 4.8 (500 ms/minimum cycle time of the programmable controller in ms). If
this constant is not adapted it may be that a cable break in the programmable controller will, in
certain circumstances, be recognised too late.
INIT: Restart FB. The FB which is to be called up for a restart and RSET = 1 must be specified here.
This is FB 212 on the diskette. This FB must be modified for the client-specific presetting of
setpoint values.
71
Programming
COFF: Emergency FB. Here, too, an FB must be specified which is run immediately is ther is a
COMMUNICATION ERROR. In general this FB should at least set the key values DW 4 and DW
5 (= MW+8 and MW+10) to zero. On the diskette this is FB 213.
Caution:
The marker range specified in parameter VOBI must have a minimum length of 46 bytes
(word 0 to word 22; MB+0 to MB+45). Parameters may be assigned to a maximum of
MW244. Otherwise the communication will not start; the programmable
controller will switch to STOP.
To do this the SEDB and UBDB should be generated automatically in the OB 21 and OB 22 using the
following instructions:
The DB should only be in the EPROM if the programmable controller copies it into the CPU internal RAM
when it is restarted.
Since the automatic generation of a DB using a formal operand is only possible using self-modifying program
code, it has not be possible to intergrate this in the handling FB. However, restart OBs are stored on the
diskette which generate the DB 50.
72
Programming
If error KH 200 (timeout when the PCS 110 is not connected) appears in DW 3 bit 12 (= M+6.5) and the
markers RFLM and EROR are both log. 1, the implementation has been successfully completed.
An example (OB 1) is contained on the diskette which sends an error message on output 4.0 (on 95 U
programmable controller: A 32.0), waits for a reset key on E 0.0 (on 95 U programmable controller: E 32.0)
which uses markers 20.0 / 20.2. The link following the call up of the FB 200 only serves the following
purpose:
- multiple RESET is prevented (edge formation).
■ The date and the time have been made invalid and are therefore transferred immediately.
■ All message bits are switch off. If several messages are active at the restart, they are re-entered in
the sequence of their numbers (lowest first) in the memory.
■ 0 is selected as the default text.
■ All menus were terminated before the system was switched off.
■ The keys and DIL switches are all transferred after the restart.
This start-up behaviour is to be taken into account when presetting the marker range.
Recommendation:
73
Programming
Both in the PCS 110 and in the programmable controller there is a time monitoring system for the serial data
exchange through the L1 interface.
The monitoring time can be set at the PCS side using the parameter ZV,S,x. Without programming the
parameter ZV,... a monitoring time of 900 ms is obtained, consisting of 500 ms (basic value) plus 400 ms
(default value for ZV,S). This time should always last an adequate period, but should at least be as long as
two to three full data exchange cycles on the serial interface of the L1 normal transfer (slave and master with
64 bytes of data). A cycle of this type lasts approx. 150 ms, therefore a time of approx. 3 * 150 ms = 500
ms is required. This value is achieved in any case by the presetting (900 ms).
The programmable controller time is generated with the aid of a counter in DW 0 (= MW+0). This counter
is cleared after every successful data exchange, in other words the send and receive mailbox for the user
program is cleared and a constant assigned to it. If no valid data are then placed in the receive mailbox for
any length of time, in other words the receive mailbox is blocked for the user program for any length of time,
this counter runs down to the value 0. This event on the one hand sets an error bit in DW 3, bit 12 (= M+6.5)
and on the other also sets the EROR error bit (parameter in FB 210). The presetting of the timeout counter
is calculated using the following method:
This value must be set when the parameters are assigned to FB 210.
Therefore the parameter TIMZ in FB 210 is to be preset to KF+250. This value is set to KF+300 on the
diskette. This time is therefore sufficient for cycle times of greater than 2 ms in any event.
74
Programming
5 TECHNICAL APPENDIX
This part of the manual contains special information which is needed for project planning: cable assignment,
transfer addresses, program lists etc.
Weight: 1400 g
These values cause no irregularities in operation. Exceeding the values results in a controlled error
message; only when the values are exceeded by a factor of 2 is interference to functions likely to occur.
A fine-wire fuse (not replaceable) is soldered in. This will blow before destruction can be caused by high-
energy malfunctions.
Data retention: CMOS static RAM battery-backed up using VARTA CR 1/2 AA (1 Ah)
soldered in
75
Programming
5.2 CABLE
The connection is made using 2 TTY channels. The line current supply is through the PCS 110; this means
that there is only strict potential separation to the programmable controller.
GND <
When using screen standard cable (4 * 0.14, not twisted), the recommended maximum length is 20 metres.
When using low capacity, data cables twisted in pairs, 10 times the length can be projected.
Recommended cable: LiYCY-CY 2 * 2 * 0.252, external diameter 10.2 mm (eg. Metrofunk Berlin).
If the connection is broken this fact is registered in the PCS 110 and noted in the error word (DW 3, bit 13;
= M+6.5) for further evaluation.
76
Programming
■ SCREENING
The screen should be connected on both sides to a metallised plug housing. If non-metallised plug
housings are used the screen can also be connected to Pin 1, but this is not recommended for
interference reasons since the data lines should be covered as far as possible by the screen. The two-
sided earth means, however, that in certain circumstances (as a result of earth potential movements)
an equi-potential bond cable of at least 10 times the cross section of the screen is necessary (Reason:
compensation currents should not, if possible be run through the cable screen), particularly if the PCS
and programmable controller are not connected to the same earthing point (if, for example, the PCS
and programmable controller are housed in different switch cabinets).
24 SCREEN SCREEN
25 SCREEN SCREEN
77
Programming
< RTS 4 7
1 (5)
For connection to the PC a standard ZERO MODEM cable can also be used.
ATTENTION:
78
PCS 810 / Handling FB
Data exchange with the controller takes place in packets. Each packet is provided with a check sum and
its content is checked in the for possible errors. Each packet consists of at least one subpacket which
carries out a clearly outlined task. The tasks to be performed in a packet are determined by the PCS 110
on the basis of the following parameters: programmable controller scan time, baud rate and the priority of
each task. Each task has specific start priority. A priority management system ensures that no task is
forgotten. The packet lengths stated refer to words including the head.
9. Read command word 3 4 **) continually (menu calls only when buffer
is empty)
*) Depends on number of variables on display and on degree of justification of addresses. If the addresses are not justified, one
head is required for each non-justified variable (1 word).
**) Task with 2 heads and one word of data each.
79
PCS 810 / Handling FB
The PCS 110 communicates with an S5 95U, S5 100U (only with CPU 103) or S5 115U via the PG
interface. The master on the bus is the PCS. For communication with the programmable controller (the only
slave on the bus) only a part of the SINEC L1 bus protocol is used. Only the "normal communication"
telegram type is used. The interface to the programmable controller program is a data block which contains
the send and receive mailbox.
The receive mailbox is described by the programmable controller operating system and read by the
programmable controller user program. The reception data "question package" from the PCS 110 are
contained in this mailbox. The handshake is realised by bit 7 in the receive coordination byte KBE.
The send mailbox is described by the programmable controller user program and read by the programmable
controller operating system. The reception data "answer package" for the PCS 110 are contained in this
mailbox. The handshake is realised by bit 7 in the send coordination byte KBS.
The user of the PCS 110 has no contafct to this send and receive mailbox. This handling procedure is carried
out completely by the handling software, which consists of the FB 210 and FB 211. The parameter
assignment of the programmable controller for the SINEC L1 bus (SINEC L1 parameter block) is completed
by the FB 211, which must be called up by OB 21 and Pb 22. In the 95 U programmable controller, these
data are filed in DB 1.
5 ms N ZB L BM QU Data BM ZB Q BM
Break + E 1 max. 64 2 E 1
xxxxxxxxxxxxxxx yyyyyyyyy
N ZB L BS Z Data BS
S 1 max. 64 2
yyyyyyyyyyyyyy
Abbreviations: N+ ... Slave number to be operated
N ... Slave number (answer from the slave)
ZBS ... Status byte send (status information for the master)
ZBE ... Status byte receive (status information for the slave)
L ... Length of the following data block (0 to max. 64 bytes)
BM1 ... Block check 1 by master (control byte)
BM2 ... Block check 2 by master (control byte)
BS1 ... Block check 1 by sender (control byte)
BS2 ... Block check 2 by sender (control byte)
Q ... Acknowledgement byte
xxx ... only if master (PCS 110) has data to send (L <> 0)
yyy ... only if slave (programmable controller) has data to send (L <> 0)
The communication runs as soon as the programmable controller and the PCS 110 are supplied with
voltage and are connected by the PCS 716 communication cable. If the programmable controller is now
switch to RUN the "actual" data transfer begins, i.e. phases xxx and yyy also exist during the bus transfer.
If, during the "actual" data transfer a double repeat "CONNECT error" or a time is exceeded "TIMEOUT error"
(if, for example, phase xxx or yyy fails for too long), the system nevertheless attempts to continue the
communication. In this case the communication runs without phases xxx and yyy, i.e. both the master and
the slave send no data.
80
PCS 810 / Handling FB
11
The PCS is composing a new package. The required time is approximately 2.5 milliseconds in online
and 10 milliseconds in offline mode.
222222222222
The "question package" is transferred in an L1 bus cycle (Phase xxx in the L1 bus procedural diagram).
The time required depends on the package length. Since the package length is not constant, this time
may generally not be fixed.
33333333
The programmable controller operating system checks the data for errors and enters them in the receive
mailbox of the programmable controller. Any errors are entered in the KBS and KBE coordination bytes
for later use. Furthermore, the handling FB 210 is told that the data exchange may be made. This is done
by bit 15 being reset by the KBE, i.e. the programmable controller user program has access to the
received data in the receive mailbox.
4444
Waiting time until the handling FB 210 is processed.
5555555
The handling FB 210 completes the data exchange in both directions. Therefore, data from the receive
mailbox are written into the marker range (including write, AND and OR commands) and data from the
marker range can be written in the send mailbox (reading commands). At the end of the FB both the
send mailbox and the receive mailbox are cleared for the programmable controller operating system (set
bit 15 from the KBE and KBS). The required run time of the FB 210 are given in the description of the
handling FB 210.
6666
Waiting time until the operating system of the programmable controller is ready to transfer the data from
the send mailbox, in other words the answer package.
777777777777
The answer package, in other words data from the send mailbox of the programmable controller, is
transferred (phase yyy in the L1 bus procedural diagram). The length of this package is also variable.
As soon as the package in the PCS 110 has been received in full a new package is composed as
described in 1.
Please note:
There may be several L1 bus cycles between phases 2 and 7. This depends on the
processing speed of the programmable controller CPU.
81
PCS 810 / Handling FB
This project is for the 100 U/115 U programmable controller and communicates through a marker range
to which parameters may be assigned.
82
PCS 810 / Handling FB
83
PCS 810 / Handling FB
84
PCS 810 / Handling FB
85
PCS 810 / Handling FB
86
PCS 810 / Handling FB
000A :L KH0000
000E :L DW69
0010 :I 6 TARGET ADDRESS (=WORD3)
0012 :TIR 2 SET ERROR WORD=0
0014 :I 2
0016 :TIR 2 DECLARE DATE INVALID
0018 :L KH0F00
001C :L DW69
001E :I 28
0020 :TIR 2 CLEAR PRIORITY BLOCK
0022 :BE
000A :L KH0000
000E :L DW69
0010 :I 8
0012 :TIR 2 SET KEY BITS TO ZERO
0014 :I 2
0016 :TIR 2
0018 :I 2
001A :TIR 2 DECLARE CLOCK INVALID
001C :BE
87
PCS 810 / Handling FB
This example shows the parameter assignment as realised on the enclosed diskette.
P R O J E C T: PCS 111
DATE: 01.07.1991
88
Technical appendix
This project is for the 95 U programmable controller and communicates through a marker range to which
parameters may be assigned.
89
Technical appendix
008E :LIR 0
0090 :T DW71 BASIC ADDRESS OF THE DBS = DW71
0092 :L KF+0 TARGET = ENTER MASTER INTO SEND BOX
0096 :T DR33
0098 :SPA =RES1
009A NORM :L KH0000 CHECK TIMEOUT COUNTER
009E :L DW69
00AO :LIR 0
00A2 :><F
00A4 :SPB =NOR1 ->-> IF NO TIMEOUT
00A6 :L DW68 ERROR ADDRESS
00A8 :LIR 0
00AA :L KH2000 ENTER TIMEOUT ERROR
00AE :OW
00B0 :L DW68
00B2 :TIR 2
00B4 :SPA =END1
00B6 NOR1 :L KF-1 DECREMENT TIMEOUT COUNTER
00BA :L DW69
00BC :LIR 0
00BE :+F
00C0 :L DW69
00C2 :TIR 2 AND WRITE BACK
00C4 :L KH8000 KBE: RECEIVE MAILBOX ACCESS ALLOWED ?
00C8 :L DW66
00CA :UW
00CC :><F
00CE :SPB =PKBS
00D0 :BEA ->-> IF RECEIVE MAILBOX BLOCKED !
00D2 PKBS :L KH8000 KBS: SEND MAILBOX ACCESS ALLOWED ?
00D6 :L DW67
00D8 :UW
00DA :><F
00DC :SPB =STAR
00DE :BEA ->-> IF SEND MAILBOX BLOCKED !
00E0 STAR :L KH0100
00E4 :L DW66 KBE: ERROR BIT SET ?
00E6 :UW
00E8 :!=F
00EA :SPB =WDH1 ->-> IF RECEIVE ERROR
00EC :LW =TIMZ RELOAD TIMEOUT COUNTER
00EE :L DW69
00F0 :TIR 2 AND ENTER
00F2 :L DR0 READ SOURCE FROM RECEIVE MAILBOX
00F4 :L KF+0
00F8 :><F
00FA :SPB =WDH1 ->-> IF >< = !
00FC :L DL0 READ LENGTH FROM RECEIVE MAILBOX >64?
00FE :T MB253 LENGTH RECEIVE MAILBOX = MB253
0100 :L KF+64
0104 :>F
0106 :SPB =WDH1 ->-> IF LENGTH > 64 BYTES
0108 :L MB253 LENGTH = 1 ?
010A :L KF+1
010E :!=F
0110 :SPB =ALT1 ->-> IF LENGTH = 1 ! (WDHA.!)
0112 :L KY68,2 START SEND BOX:DW34, RECEIVE BOX:DW1
0116 :T MW254
90
Technical appendix
91
Technical appendix
92
Technical appendix
0016 :B =SEDB
0018 :U =RFLM
001A :RB =RFLM
001C :L KH0000
0020 :T DW67
0022 :L KH8000
0026 :T DW66
0028 :BE
000A :L KH0000
000E :L DW69
0010 :I 6 TARGET ADDRESS (=WORD3)
0012 :TIR 2 SET ERROR WORD=0
0014 :I 2
0016 :TIR 2 DECLARE DATE INVALID
0018 :L KH0F00
001C :L DW69
001E :I 28
0020 :TIR 2 CLEAR PRIORITY BLOCK
0022 :BE
93
Technical appendix
000A :L KH0000
000E :L DW69
0010 :I 8
0012 :TIR 2 SET KEY BITS TO ZERO
0014 :I 2
0016 :TIR 2
0018 :I 2
001A :TIR 2 DECLARE CLOCK INVALID
001C :BE
94
Technical appendix
This example shows the parameter assignment as realised on the enclosed diskette.
P R O J E C T: PCS 111
DATE: 01.07.1991
95
Technical appendix
This project is for the 100 U/115 U programmable controller and communicates through a data block.
96
PCS 810 / Handling FB
0090 :B =SEDB
0092 :L KF+0 TARGET = ENTER MASTER INTO SEND BOX
0096 :T DR33
0098 :SPA =RES1
009A STOP :STS
009C NORM :L KH0000 CHECK TIMEOUT COUNTER
00A0 :L DW69
00A2 :LIR 0
00A4 :><F
00A6 :SPB =NOR1 ->-> IF NO TIMEOUT
00A8 :L DW68 ERROR ADDRESS
00AA :LIR 0
00AC :L KH2000 ENTER TIMEOUT ERROR
00B0 :OW
00B2 :L DW68
00B4 :TIR 2
00B6 :SPA =END1
00B8 NOR1 :L KF-1 DECREMENT TIMEOUT COUNTER
00BC :L DW69
00BE :LIR 0
00C0 :+F
00C2 :L DW69
00C4 :TIR 2 AND WRITE BACK
00C6 :L KH8000 KBE: RECEIVE MAILBOX ACCESS ALLOWED ?
00CA :L DW66
00CC :UW
00CE :><F
00D0 :SPB =PKBS
00D2 :BEA ->-> IF RECEIVE MAILBOX BLOCKED !
00D4 PKBS :L KH8000 KBS: SEND MAILBOX ACCESS ALLOWED ?
00D8 :L DW67
00DA :UW
00DC :><F
00DE :SPB =STAR
00E0 :BEA ->-> IF SEND MAILBOX BLOCKED !
00E2 STAR :L KH0100
00E6 :L DW66 KBE: ERROR BIT SET ?
00E8 :UW
00EA :!=F
00EC :SPB =WDH1 ->-> IF RECEIVE ERROR
00EE :LW =TIMZ RELOAD TIMEOUT COUNTER
00F0 :L DW69
00F2 :TIR 2 AND ENTER
00F4 :L DR0 READ SOURCE FROM RECEIVE MAILBOX
00F6 :L KF+0
00FA :><F
00FC :SPB =WDH1 ->-> IF >< 0 !
00FE :L DL0 READ LENGTH FROM RECEIVE MAILBOX >64?
0100 :T MB253 LENGTH RECEIVE MAILBOX = MB253
0102 :L KF+64
0106 :>F
0108 :SPB =WDH1 ->-> IF LENGTH > 64 BYTES
010A :L MB253 LENGTH=1 ?
010C :L KF+1
0110 :!=F
0112 :SPB =ALT1 ->-> IF LENGTH =1 ! (WDHA.!)
0114 :L KY68,2 START SEND BOX:DW34, RECEIVE BOX:DW1
0118 :T MW254
97
PCS 810 / Handling FB
98
PCS 810 / Handling FB
019E :U M 251.5
01A0 :SPB =WR ->-> JUMP FOR WRITING ! ! ! !
01A2 :LIR 0 READ ACTUAL DATA
01A4 :UN M 251.6
01A6 :SPB =ODER ->-> JUMP IF OR ! ! ! !
01A8 :UW AND COMMAND
01AA :SPA =WEND ->-> CONTINUE THERE
01AC ODER :OW OR COMMAND
01AE WEND :L MW248
01B0 WR :TIR 2 DATE TO TARGET ADDRESS
01B2 :L MB255
01B4 :L KF+2
01B8 :+F
01BA :T MB255 POINTER RECEIVE MAILBOX +2 BYTES
01BC :L MB253
01BE :L KF-2
01C2 :+F
01C4 :T MB253 LENGTH RECEIVE MAILBOX -2 BYTES
01C6 INCR :L MW248
01C8 :L KF+2
01CC :+F
01CE :T MW248 POINTER TARGET ADDRESS +2 BYTES
01D0 :L MB251
01D2 :L KF-1
01D6 :+F
01D8 :T MB251 NUMBER OF WORDS IN SUBPACKAGE - 1
01DA :SPA =INTP ->-> CONTINUE THERE !
01DC ENDE :L DW68
01DE :LIR 0 ERROR WORD
01E0 :L KH0000
01E4 :OW
01E6 :SPN =FEHL ->-> IF ERROR (ERROR WORD <> 0)
01E8 :U =RSET
01EA :SPB =REST ->-> RESET (CONT. COMMUNICATION)
01EC :L KH0000
01F0 :L MB252 LENGTH SEND MAILBOX
01F2 :><F
01F4 :SPB =NLEE ->-> IF SEND MAILBOX NOT EMPTY !
01F6 :L KF+2
01FA :T DL34 EMPTY PACKAGE = 02H
01FC :L KF+1 LENGTH 1 BYTE
0200 NLEE :T DL33 ENTER LENGTH
0202 :RB =EROR
0204 :SPA =SPAK ->-> SEND PACKAGE
0206 WDHA :L KF+1 LENGTH SEND MAILBOX = 1
020A :T DL33
020C :T DL34 REPEAT REQUEST = 01H
020E :SPA =SPAK ->-> SEND PACKAGE
0210 FEHL :S =EROR ERROR MESSAGE ON
0212 :B =UBDB
0214 :B =COFF ---IF ERROR ==> COFF ! ! ! ---
0216 :B +SEBD
0218 :UN +RSET RESET REQUIRED ?
021A :BEB ->-> IF NOT
021C :RB =RFLM
021E REST :RB =RSET
0220 :L KF+1 LENGTH 1 BYTE
0224 :T DL33
99
PCS 810 / Handling FB
100
PCS 810 / Handling FB
000A :L KH0000
000E :T DW3 SET ERRPR WORD=0
0010 :T DW6 DECLARE DATE INVALID
0012 :L KH0F00
0016 :T DW14 CLEAR PRIORITY BLOCK
0018 :BE
000A :L KH0000
000E :T DW4 KEY BITS OFF ! !
0010 :T DW5
0012 :T DW6 DECLARE CLOCK INVALID
0014 :BE
101
Technical appendix
This example shows the parameter assignment as realised on the enclosed diskette.
P R O J E C T: PCS 111
DATE: 01.07.1991
102
Technical appendix
This project is for the 95 U programmable controller and communicates through a data block.
103
PCS 810 / Handling FB
0090 :B =SEDB
0092 :L KF+0 TARGET = ENTER MASTER INTO SEND BOX
0096 :T DR33
0098 :SPA =RES1
009A STOP :STS
009C NORM :L KH0000 CHECK TIMEOUT COUNTER
00A0 :L DW69
00A2 :LIR 0
00A4 :><F
00A6 :SPB =NOR1 ->-> IF NO TIMEOUT
00A8 :L DW68 ERROR ADDRESS
00AA :LIR 0
00AC :L KH2000 ENTER TIMEOUT ERROR
00B0 :OW
00B2 :L DW68
00B4 :TIR 2
00B6 :SPA =END1
00B8 NOR1 :L KF-1 DECREMENT TIMEOUT COUNTER
00BC :L DW69
00BE :LIR 0
00C0 :+F
00C2 :L DW69
00C4 :TIR 2 AND WRITE BACK
00C6 :L KH8000 KBE: RECEIVE MAILBOX ACCESS ALLOWED ?
00CA :L DW66
00CC :UW
00CE :><F
00D0 :SPB =PKBS
00D2 :BEA ->-> IF RECEIVE MAILBOX BLOCKED !
00D4 PKBS :L KH8000 KBS: SEND MAILBOX ACCESS ALLOWED ?
00D8 :L DW67
00DA :UW
00DC :><F
00DE :SPB =STAR
00E0 :BEA ->-> IF SEND MAILBOX BLOCKED !
00E2 STAR :L KH0100
00E6 :L DW66 KBE: ERROR BIT SET ?
00E8 :UW
00EA :!=F
00EC :SPB =WDH1 ->-> IF RECEIVE ERROR
00EE :LW =TIMZ RELOAD TIMEOUT COUNTER
00F0 :L DW69
00F2 :TIR 2 AND ENTER
00F4 :L DR0 READ SOURCE FROM RECEIVE MAILBOX
00F6 :L KF+0
00FA :><F
00FC :SPB =WDH1 ->-> IF >< 0 !
00FE :L DL0 READ LENGTH FROM RECEIVE MAILBOX >64?
0100 :T MB253 LENGTH RECEIVE MAILBOX = MB253
0102 :L KF+64
0106 :>F
0108 :SPB =WDH1 ->-> IF LENGTH > 64 BYTES
010A :L MB253 LENGTH=1 ?
010C :L KF+1
0110 :!=F
0112 :SPB =ALT1 ->-> IF LENGTH =1 ! (WDHA.!)
0114 :L KY68,2 START SEND BOX:DW34, RECEIVE BOX:DW1
0118 :T MW254
104
PCS 810 / Handling FB
105
PCS 810 / Handling FB
019E :U M 251.5
01A0 :SPB =WR ->-> JUMP FOR WRITING ! ! ! !
01A2 :LIR 0 READ ACTUAL DATA
01A4 :UN M 251.6
01A6 :SPB =ODER ->-> JUMP IF OR ! ! ! !
01A8 :UW AND COMMAND
01AA :SPA =WEND ->-> CONTINUE THERE
01AC ODER :OW OR COMMAND
01AE WEND :L MW248
01B0 WR :TIR 2 DATE TO TARGET ADDRESS
01B2 :L MB255
01B4 :L KF+2
01B8 :+F
01BA :T MB255 POINTER RECEIVE MAILBOX +2 BYTES
01BC :L MB253
01BE :L KF-2
01C2 :+F
01C4 :T MB253 LENGTH RECEIVE MAILBOX -2 BYTES
01C6 INCR :L MW248
01C8 :L KF+2
01CC :+F
01CE :T MW248 POINTER TARGET ADDRESS +2 BYTES
01D0 :L MB251
01D2 :L KF-1
01D6 :+F
01D8 :T MB251 NUMBER OF WORDS IN SUBPACKAGE - 1
01DA :SPA =INTP ->-> CONTINUE THERE !
01DC ENDE :L DW68
01DE :LIR 0 ERROR WORD
01E0 :L KH0000
01E4 :OW
01E6 :SPN =FEHL ->-> IF ERROR (ERROR WORD <> 0)
01E8 :U =RSET
01EA :SPB =REST ->-> RESET (CONT. COMMUNICATION)
01EC :L KH0000
01F0 :L MB252 LENGTH SEND MAILBOX
01F2 :><F
01F4 :SPB =NLEE ->-> IF SEND MAILBOX NOT EMPTY !
01F6 :L KF+2
01FA :T DL34 EMPTY PACKAGE = 02H
01FC :L KF+1 LENGTH 1 BYTE
0200 NLEE :T DL33 ENTER LENGTH
0202 :RB =EROR
0204 :SPA =SPAK ->-> SEND PACKAGE
0206 WDHA :L KF+1 LENGTH SEND MAILBOX = 1
020A :T DL33
020C :T DL34 REPEAT REQUEST = 01H
020E :SPA =SPAK ->-> SEND PACKAGE
0210 FEHL :S =EROR ERROR MESSAGE ON
0212 :B =UBDB
0214 :B =COFF ---IF ERROR ==> COFF ! ! ! ---
0216 :B +SEBD
0218 :UN +RSET RESET REQUIRED ?
021A :BEB ->-> IF NOT
021C :RB =RFLM
021E REST :RB =RSET
0220 :L KF+1 LENGTH 1 BYTE
0224 :T DL33
106
PCS 810 / Handling FB
0016 :B =SEDB
0018 :U =RFLM
001A :RB =RFLM
001C :L KH0000
0020 :T DW67
0022 :L KH8000
0026 :T DW66
0028 :BE
000A :L KH0000
000E :T DW3 SET ERRPR WORD=0
0010 :T DW6 DECLARE DATE INVALID
0012 :L KH0F00
0016 :T DW14 CLEAR PRIORITY BLOCK
0018 :BE
107
PCS 810 / Handling FB
000A :L KH0000
000E :T DW4 KEY BITS OFF ! !
0010 :T DW5
0012 :T DW6 DECLARE CLOCK INVALID
0014 :BE
108
PCS 810 / Handling FB
This example shows the parameter assignment as realised on the enclosed diskette.
P R O J E C T: PCS 111
DATE: 01.07.1991
109
Program examples
6 PROGRAM EXAMPLES
The following examples are only intended as guides. They have not been tested and are therefore not stored
on the diskette. Since the marker assignment has been chosen at random, these examples would have
to be adapted anyway
In this example (precondition: Project 1 or 3) the word-by word edge detection is shown on pos. and neg.
edges. If only pos. edges are required, the commands as from TAK can be omitted. MW30 and MW32 have
been used as edge markers in this example. The edge bits are in MW34, MW36, MW38 and MW40. The
marker range required for communication starts as from MW50.
110
Program examples
In this example the setpoint menu No. 1 is opened with F1, whereby the default text number and priority
restriction are retained. The edge formation described above and the use of Projects 1 and 3 are
preconditions. In this example, too, the marker range required for communication starts from MW50.
111
112
Index
10 INDEX
## 49 Writing field 10
#P100.DOK, #P101.DOK 3 Operating PROM A, B and RAM 1.2 46
#P110.DOK, #P111.DOK 3 Operating voltage 75
1:1 representation 57 Operating voltage connections 11
32 bit integer arithmetic 57 Operating statuses of the PCS 9
[CLR] key 2, 61 BIT 13
[CTRL] + [BREAK] 63 Flashing 7
[ENTER] 18 Flashing text with flashing underline 41
[ENTER] key 2, 29 Flashing message text 41
[HLP] key 2, 32 Scrolling on the help line 41
[ARROW UP] 10, 13 SIGUT bus module 1
[ARROW DOWN] 10
CLRENTER 54
AA 49 COFF 72
Abbreviations 33 Communication error 5, 33
Dimensions 75 CONFIG 33, 46
AE 49, 58 CONNECT 33
AG 100 U 1 Cursor 18
AG 115 U 1 CSTRING 13
AG 95 U 1
Switch AG to run 73 Display modes 10
Acousitc error signal 9, 10, 25, 29 Displaying a variable 3
Start-up OB 66 Data errors 33
Connection assignment 11 Mark beginning of file 51
Answer package 81 Mark end of file 51
Display and storage modes 38, 41 Data transfer 23
Display behaviour 30 Data exchange 81
AP commands 56 Data exchange cycle 13
Refreshing the values 23 Data block 2, 65
Calling up a new menu 42 Data range 34
Instances 1, 16, 17, 57 Data receipt 49
Output on a printer 49 Data reception 8, 75
Output module 3 Data transfer with the controller 79
Output board 1 Data loss 8
Selecting the start procedure 46 Data transfer 7, 80, 81
Selecting menu points 45 Date 39
DB 1 3, 65, 67
Battery service life 75 Device LPT0 2, 62
Baud rate 5, 23 Decimal point insertion 14, 18
Rack CR 700.x 1 The transfer of the clock 69
BCD0 14 DIL switches 8
Meaning of DW 0 to DW 22 34 DIL switch 7 5, 45
User guide 26 DIL switches No. 7, 9 and 10 2
Operating text 25 DIL switch No. 8 2, 5
Operating texts 0 - 15 13, 25, 42 DOS commands MODE and COPY 49
Operating text number 26 Print output WITH MARGIN 5, 51
Operating the offline menus 45 Print output WITHOUT MARGIN 62
Operating request 9 Printer setting file 5
Quitting the menu 25, 26 Printer interface of the PG 2
Commands and parameters 51 Dark phase 9
Command line 51 Run time 69
Example 107 DW 3 error word 37
User entries 40 DW 4 F keys 35, 38
Calculation of cycle time extension 69 DW 5 Control keys 35, 38
Writing on cable ends 3 DW 6, DW 7 Date 35, 39
Index
Warning 9
Warning priority 30
Value ranges 20
Word-by-word edge detection 107
XON/XOFF protocol 49