LAUER PCS 091 User manual

Reg 5049/0996ss
Appendix to the PCS 091/PCS 925/PCS 991/PCS 9091
manuals
PLC systems (1) A120 (ALU 200, 201, or 202), A250
PLC interfacing (2) with PCS 859 EPROM for KOS 201
or KOS 202 with PCS 776 adapter
cable (only for A120)
(2) direct driver with the PCS 778
adapter cable
(2) expander driver with the PCS 778
adapter cable (only for A250)
PLC systems (1) Modicon 984 series with CPU 120,
130, 145, 380, 381, 385, 480, 485,
680, 685, 780, 785, X, A, and B
PLC interfacing (2) via MODBUS 1 interface with the
PCS 780 adapter cable
PCS/VPC 91. AEG
Vers. 1/09.96
© Systeme Lauer GmbH
PCS/VPC 91.AEG
AEG

2
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
© Systeme Lauer GmbHLauer-driver
○○○○○○○
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
○○
A
EDITION
SEPTEMBER
1996
Lauer driver
Fast A120 communication with the PCS micro/mini/midi and maxi. Requires
programmable controller program and KOS module
Operating unit: PCS 009/PCS 090/PCS 095/PCS 900/PCS 920
/PCS 950
Programmable controller system: AEG A120
Interface: KOS 201/202 module + PCS 859 (EPROM
firmware)
Protocol: Lauer
Adapter cable: PCS 776
Driver type: expander driver
"AEG120DR" driver
'Plug and Play' communication using the PG interface without programmable
controller program. Less fast than the expander driver.
Operating unit: PCS 009/PCS 090/PCS 095/PCS 900/PCS 920
/PCS 950
Programmable controller system: AEG A120 / A250
Interface: PG interface
Protocol: BKOS
Adapter cable: PCS 778
Driver type: direct driver
Information for the driver selection

3
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
© Systeme Lauer GmbH Lauer-driver
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
○○○○○○○
○○
A
Information for the driver selection
"MODBUSPS" driver
'Plug and Play' communication between Modicon programmable controllers and
PCS
Operating unit: PCS 009/PCS 090/PCS 095/PCS 900/PCS 920
/PCS 950
Programmable controller systems: Modicon 984-120, - 380, -381, -385, -480, -485,
-680, -685, -780, -785, -X, -A, -B
Interface: Modbus interface
Protocol: MODBUS 1 SLAVE
Adapter cable: PCS 780
Driver type: direct driver
"AEG250PX" driver
Fast A250 communication with the PCS midi and maxi. Requires programmable
controller program. Uses PG interface.
Operating unit: PCS 009/PCS 090/PCS 095/PCS 900/PCS 920
/PCS 950
Programmable controller system: AEG A250
Interface: PG interface
Protocol: BKOS
Adapter cable: PCS 778
Driver type: expander driver

4
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
© Systeme Lauer GmbHLauer-driver
○○○○○○○
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
○○
A. Lauer driver
A1. Description of KOS 201/201 ............................. 8
A1.1 Settings at the board .................................. 8
A1.1.1 Addressing of the board .................................. 8
A1.1.2 Baud rate settings .................................. 8
A1.2 Description of the handling software .................................. 8
A1.3 Parameterization of FB 200 .................................. 9
A1.4 Implementation of the handling FB ................................ 10
A1.5 Program integration ................................ 11
A2.Program listing ............................ 12
A3. Communication ............................19
A3.1 Communication cable programming UNIT/KOS ................................ 19
A3.1.1 Screening of the communication cable ................................ 19
A3.2 Programming cable PCS 733 ................................ 20
B. AEG120DR driver
B1. First Commisioning ........................... 22
B1.1Delimitation ................................ 22
B1.2Loading the AEG 120 DR driver into the PCS ................................ 22
B1.3PCS connection to the programmable controller ................................ 23
B1.4Trouble-shooting ................................ 24
B2.Programmable controller handling software .......................... 26
B2.1Asynchronous Communication ................................ 27
B2.2Synchronous communication ................................ 27
B2.2.1 Procedure ................................ 28
B2.2.2 Description of the handling software ................................ 28
B3. Communication .......................... 30
B3.1Adapter cable PCS 778 ................................ 30
B3.1.1 Screening ................................ 30
B3.2Programming cable PCS 733 ................................ 31
B4. Listing ...........................32
Table of contents

5
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
© Systeme Lauer GmbH Lauer-driver
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
○○○○○○○
○○
Table of contents
C. MODBUSPS driver
C.1.First commissioning .......................... 36
C.1.1 Delimitation ................................ 36
C.1.2 Loading of the MODBUSPS driver to the PCS ................................ 36
C.1.3 Connection of the PCS to the programmable controller ......................... 37
C.1.4 Trouble-shooting ................................ 38
C.2. PLC handling software .......................... 40
C.2.1 Asynchronous communication ................................ 41
C.2.2 Synchromous communication ................................ 42
C2.2.1 Procedure ................................ 42
C2.3 Description of the handling software ................................ 43
C3.Cables ...........................44
C3.1 PCS 780 adapter cable ................................ 44
C3.2 Screening ................................ 44
C3.2 Programming cable PCS 733 ................................ 45
C3.3 Data transfer sequences ................................ 46
C4.Listing ........................... 47
D. AEG250PX driver
D1. First commissioning ...........................54
D1.1 Delimitation ................................ 54
D1.2 Loading of the AEG250PX driver into the THE PCS ................................ 54
D1.2.1 PCS midi driver variables ................................ 55
D1.2.2 The PCS maxi driver variables ................................ 56
D.1.3 Connection of the PCS to the PLC ................................ 56
D1.4 Trouble-shooting ................................ 57
D1.5 Offlinemenu ................................ 57
D1.7 References for the connection of the PCS to a PLC ................................ 58
D2.PLC handling software ...........................59
D2.1 AEG250PX Expander block ................................ 59
D2.1.1 Expander block parameters ................................ 59
D2.1.2 PB1 ................................ 60
D2.1.4 FB201 ................................ 60
D2.1.5 FB202 ................................ 60
D2.1.6 FB205 ................................ 60
D2.1.7 FB210 ................................ 61
D2.1.8 FB211 ................................ 61
D2.1.9 FB212 ................................ 61
D2.1.10 FB213 ................................ 61
D2.2 Loading of the handling software ................................ 61

6
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
© Systeme Lauer GmbHLauer-driver
○○○○○○○
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
○○
A
D3. Communication .......................... 62
D3.1 PCS 778 adapter cable ................................ 62
D3.1.1 Screening ................................ 62
D3.2 Programming cable PCS 733 ................................ 63
D3.3 Data transfer PCS - PLC ................................ 63
D3.4 PCS - PLC effective response times ................................ 64
D3.5 Speed optimization ................................ 65
D3.6 Communication error ................................ 68
D4.Printout of the AEG250PX handlingsoftware ....................... 69
D5.1 Ideograms and symbols ................................ 76
D5.2 Safty related information ................................ 76
D5.3 Quality and Support ................................ 76
D5.Important user information ...........................76
Who for what to task? ............................77
Index ...........................78
Table of contents

7
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
© Systeme Lauer GmbH Lauer-driver
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
○○○○○○○
○○
Description of the loadable AEG120DR/AEGBKOS driver for the PCS 009/
090/095/900 operating consoles. For communication with an AEG 120/
250 PLC.
Functionality: Selective direct driver for KOS 201/202 PLCs.
Required devices and accessories:
1. The PCS operating console itself (already parameterized).
2. The PCS 776 connecting cable for the PCS - programmable controller connection
via the PU interface.
3. This manual
4. Firmware EPROM PCS 859
Furthermore are necessary (AEG company):
5. An A120 programmable controller with rack, power supply and I/O boards.
.... as well as power supplies for all components.
A

8
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
© Systeme Lauer GmbHLauer-driver
○○○○○○○
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
○○
A1.1 Settings at the board
A1.1.1Addressing of the board
The KOS 201/202 board is only pluggable in the base magazine, i.e. DTA 200
(slots 1, 2 and 3). Slot 1 however, is required by the DNP 205 power supply board,
at least when using the ALU 201 or 202. Thus, slot 2 or 3 remains in the DTA 200
rack. The communication with the ALU is performed via a dual port RAM and
the PAB1 parallel equipment bus of the system. In addition, 128 IBs and 128
OBs are used. The programmable controller user however, has only contact to
the PCS via 128 OBs (64 words altogether).
 Slot selection
Slot 2: use handling software from the 9002 programming unit directory.
Slot 3: use handling software from the 9003 programming unit directory.
Basically, slot 1 can also be used since the DNP 205 power supply board can be
operated on slot 2 or 3. In addition, all function blocks belonging to the handling
software would have to be rewritten however (replace EBx.y and ABx.y with
EB1.y and AB1.y).
A1.1.2 Baud rate settings
The baud rate setting for the communication between the PCS and the KOS 201
board is made by the software in OB1. The position (first line; instruction: L
KHxx) is mark by a comment! This constant is assigned a flag byte which in
turn submits an FB 200 parameter (BAUD). The following baud rates are possible:
1200 baud (L KH00), 4800 baud (L KH01), 9600 baud (L KH02) and 19200 baud (L
KH03).
A1.2 Description of the handling software
The enclosed FB 200 manages the data traffic between a transfer area (ABx.1 -
ABx.128) and the KOS board.
PB 200 is selected by the FB 200. This is used to copy all Ebx.y (data from the
PCS 200) onto ABx.y.
PB 201 and PB 202 are used to offer the user the possibility to install customer
specific presettings at restart (PB 201) or fault situations (PB 202) without
intervening in FB 200.
Apart from the cyclical call of FB 200 at the beginning of the programmable
controller cycle, incl. setting the baud rate with the BAUD parameter, the
implementation limits itself to reading and writing ABx.1 - ABx.128. A summary
fault bit (ERROR) enables the communication status to be evaluated via the
ladder diagram program. If this fault bit is = 1, then the data transfer has been
stopped. It can be restarted by presetting a flag (RESET). A further flag (TOGGLM)
is required for short/long cycles. This will be toggled and indicates in each
programmable controller cycle whether the programmable controller cycle can be
terminated after calling FB 200 (short cycle), or whether it is useful to process
further statement list commands (long cycle).
Description of KOS 201/202
A1. Description of KOS 201/201
A

9
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
© Systeme Lauer GmbH Lauer-driver
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
○○○○○○○
○○
A1.3 Parameterization of FB 200
 RESET
Switch for resetting after faults (input: bit)
If a communication fault appears, then the communication can be restarted
with this bit. The faults indicated in ABx.6 and ABx.7 are then automatically
reset! It is to be noted that no edge evaluation is made, i.e. when the bit is set
RESET starts the communication automatically again after the appearance of
a fault! This mechanism can also be realized by applying the fault output ERROR
directly to RESET.
 ERROR
Global error message (output: bit)
If a fault appears anywhere in the connection between PLC and PCS 200, then
the ERROR global fault bit is set. ABx.6 and ABx.7 can be procured to determine
the exact cause of the fault. This bit is reset as soon as communication runs
correctly again.
 BAUD
Baud rate (input: flag byte)
This flag byte is preset with the desired baud rate before calling FB 200. Possible
values are KH00 (1200 baud), KH01 (4800 baud), KH02 (9600 baud) and KH03
(19200 baud).
 TOGGL
Short / long cycle indication (output: bit)
Since the ALU reads first of all the input bytes at the cycle end, and subsequently
writes output bytes and not conversely, is it necessary to insert a short cycle
(for each second programmable controller cycle). The short cycle is marked
thereby, that this bit is = 0. If this is the case, then the programmable controller
cycle can be terminated after calling FB 200 as is realized in the example.
PB201: customer-specific presetting for the restart
PB202: customer-specific assignment for the fault case
Description of KOS 201/202 A

10
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
© Systeme Lauer GmbHLauer-driver
○○○○○○○
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
○○
A1.4 Implementation of the handling FB
1. Turn off the programmable controller
2. Plug the 201/202 KOS board into slot 2 or 3 of the DTA 200
3. Switch the programmable controller to stop and supply voltage
4. Depending on the used slot, add the PB200, PB201, PB202 function blocks
from the PCS 9002 or PCS 9003 to each own project. Modify perhaps PB201
and PB202 for your own demands.
5. Expand OB1 corresponding to the example on the floppy disk:
- load the baud rate in a flag byte
- call FB 200
- if TOGGLM = 0 →function block end, otherwise process your own pro
gram.
6. Determine the momentary reset pushbutton and set with positive edge
(RESET)
7. Bind all function blocks and load these into the controller
8. Switch the programmable controller to RUN
If the KH20H fault appears in ABx.6 (time-out, i.e. the PCS is not connected) and
the global error message (ERROR) is logical 1, then the implementation is
successfully completed. See the trouble-shooting section 1.4 if this is not the
case!
An example (OB1) is contained on the floppy disk which indicates faults on
output 5.1, and awaits a momentary reset pushbutton at I 4.1. The baud rate
submitted in MB1 is set as the baud rate, and must be identical with the baud
rate set via the DILs on the PCS 200.
Description of KOS 201/202
A

11
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
© Systeme Lauer GmbH Lauer-driver
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
○○○○○○○
○○
A1.5 Program integration
Regarding the integration into your program, the following transfer operations
must be executed (non-required functions can be skipped):
 All values read by the PCS must be copied to the corresponding ABx.y. This
affects:
 word 15 to word 19 (ABx.30 to ABx.39)
 all used message bits
 all variables
 All values modified by the PCS must be written back into the corresponding
flags/flag bytes/flag words. This affects:
 word 4 to word 14 (ABx.8 to ABx.29)
 all message bits with erase behavior 2
 all message bits for concealed logging with erase behaviors 2 -4
 all preset values
After restart, the PCS proceeds with the following assumptions:
 Date and time as well as the timer have become invalid and will therefore be
transferred immediately.
 All message bits are in the same state as before switching off.
 0 is selected as idle text.
 All menus have been terminated before switching off, otherwise they must
be restarted.
 After restart, the momentary pushbuttons and DIL switches will all be
transferred once.
This run-up behavior is to be noted when presetting the transfer area.
Description of KOS 201/202 A

12
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
© Systeme Lauer GmbHLauer-driver
○○○○○○○
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
○○
Only the listing for slot 2 (9002 programming unit) is printed! The listing for slot 3
is identical with the slot 2 except for the EBx/ABx numbers (EB2.Y and AB2.Y are
replaced with EB3.Y and AB3.Y).
9002 PCS9002\FB200
NETWORK: 0001
NAME: HANT_PCS
BEZ: RESET (E/Ex/A/Ax/M/Mx/SM/SMx/T/Z/TN/B2/B8/B16/ANZ) (I/O) M
I
BEZ: ERROR (E/Ex/A/Ax/M/Mx/SM/SMx/T/Z/TN/B2/B8/B16/ANZ) (I/O) M O
BEZ: BAUD (E/Ex/A/Ax/M/Mx/SM/SMx/T/Z/TN/B2/B8/B16/ANZ) (I/O) MB I
BEZ: TOGGLM (E/Ex/A/Ax/M/Mx/SM/SMx/T/Z/TN/B2/B8/B16/ANZ) (I/O) M O
:***
NETWORK: 0002
:L =BAUD
:U KH 3
:= AB 2.1 BAUD RATE -> COMMAND BYTE
:U SM 2 ^ activating flag
:SPZ =NORM FIRST CYCLE?
:L AB 2.1
:O KH C0
:= AB 2.1 THEN RESET COMMAND -> COMMAND B.
:BA PB 201 AND MACHINE SPEC. PRESETTINGS
:SP =END
NORM :UN =TOGGLM
:= =TOGGLM
:SPZ =END SHORT CYCLE?, IF YES -> END
:L AB 2.1
:O KH 40
:= AB 2.1 LONG CYCLE -> COMMAND B.
:BA PB 200 COPIES ALL EB2.X -> AB2.X
:L AB 2.6
:O AB 2.7
:<> KH 0 FAULT FOUND?
:= =ERROR THEN SET FAULT BIT AND
:BAB PB 202 CALL EMERGENCY SETTINGS!
:U =ERROR
:U =RESET
:SPZ =END IF FAULT AND RESET, THEN
:BA PB 201 MACH. SPEC. PRESETTING AND COMM.START
END:***
A2.Program listing
AProgram listing

13
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
© Systeme Lauer GmbH Lauer-driver
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
○○○○○○○
○○
NETWORK: 0003
:BE
PCS 9002\PB200
NETWORK: 0001
:L EB 2.6
:= AB 2.6
:L EB 2.7
:= AB 2.7
:L EB 2.8
:= AB 2.8
:L EB 2.9
:= AB 2.9
:L EB 2.10
:= AB 2.10
:L EB 2.11
:= AB 2.11
:L EB 2.12
:= AB 2.12
:L EB 2.13
:= AB 2.13
:L EB 2.14
:= AB 2.14
:L EB 2.15
:= AB 2.15
:L EB 2.16
:= AB 2.16
:L EB 2.17
:= AB 2.17
:L EB 2.18
:= AB 2.18
:L EB 2.19
:= AB 2.19
:L EB 2.20
:= AB 2.20
:L EB 2.21
:= AB 2.21
:L EB 2.22
:= AB 2.22
:L EB 2.23
:= AB 2.23
:L EB 2.24
:= AB 2.24
:L EB 2.25
:= AB 2.25
:L EB 2.26
:= AB 2.26
:L EB 2.27
:= AB 2.27
:L EB 2.28
:= AB 2.28
:L EB 2.29
:= AB 2.29
:L EB 2.30
:= AB 2.30
:L EB 2.31
:= AB 2.31
:L EB 2.32
:= AB 2.32
:L EB 2.33
:= AB 2.33
Program listing A

14
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
© Systeme Lauer GmbHLauer-driver
○○○○○○○
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
○○
:L EB 2.34
:= AB 2.34
:L EB 2.35
:= AB 2.35
:L EB 2.36
:= AB 2.36
:L EB 2.37
:= AB 2.37
:L EB 2.38
:= AB 2.38
:L EB 2.39
:= AB 2.39
:L EB 2.40
:= AB 2.40
:L EB 2.41
:= AB 2.41
:L EB 2.42
:= AB 2.42
:L EB 2.43
:= AB 2.43
:L EB 2.44
:= AB 2.44
:L EB 2.45
:= AB 2.45
:L EB 2.46
:= AB 2.46
:L EB 2.47
:= AB 2.47
:L EB 2.48
:= AB 2.48
:L EB 2.49
:= AB 2.49
:L EB 2.50
:= AB 2.50
:L EB 2.51
:= AB 2.51
:L EB 2.52
:= AB 2.52
:L EB 2.53
:= AB 2.53
:L EB 2.54
:= AB 2.54
:L EB 2.55
:= AB 2.55
:L EB 2.56
:= AB 2.56
:L EB 2.57
:= AB 2.57
:L EB 2.58
:= AB 2.58
:L EB 2.59
:= AB 2.59
:L EB 2.60
:= AB 2.60
:L EB 2.61
:= AB 2.61
:L EB 2.62
:= AB 2.62
:L EB 2.63
:= AB 2.63
:L EB 2.64
:= AB 2.64
:L EB 2.65
:= AB 2.65
:L EB 2.66
AProgram listing

15
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
© Systeme Lauer GmbH Lauer-driver
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
○○○○○○○
○○
:= AB 2.66
:L EB 2.67
:= AB 2.67
:L EB 2.68
:= AB 2.68
:L EB 2.69
:= AB 2.69
:L EB 2.70
:= AB 2.70
:L EB 2.71
:= AB 2.71
:L EB 2.72
:= AB 2.72
:L EB 2.73
:= AB 2.73
:L EB 2.74
:= AB 2.74
:L EB 2.75
:= AB 2.75
:L EB 2.76
:= AB 2.76
:L EB 2.77
:= AB 2.77
:L EB 2.78
:= AB 2.78
:L EB 2.79
:= AB 2.79
:L EB 2.80
:= AB 2.80
:L EB 2.81
:= AB 2.81
:L EB 2.82
:= AB 2.82
:L EB 2.83
:= AB 2.83
:L EB 2.84
:= AB 2.84
:L EB 2.85
:= AB 2.85
:L EB 2.86
:= AB 2.86
:L EB 2.87
:= AB 2.87
:L EB 2.88
:= AB 2.88
:L EB 2.89
:= AB 2.89
:L EB 2.90
:= AB 2.90
:L EB 2.91
:= AB 2.91
:L EB 2.92
:= AB 2.92
:L EB 2.93
:= AB 2.93
:L EB 2.94
:= AB 2.94
:L EB 2.95
:= AB 2.95
:L EB 2.96
:= AB 2.96
:L EB 2.97
:= AB 2.97
:L EB 2.98
A
Program listing

16
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
© Systeme Lauer GmbHLauer-driver
○○○○○○○
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
○○
:= AB 2.98
:L EB 2.99
:= AB 2.99
:L EB 2.100
:= AB 2.100
:L EB 2.101
:= AB 2.101
:L EB 2.102
:= AB 2.102
:L EB 2.103
:= AB 2.103
:L EB 2.104
:= AB 2.104
:L EB 2.105
:= AB 2.105
:L EB 2.106
:= AB 2.106
:L EB 2.107
:= AB 2.107
:L EB 2.108
:= AB 2.108
:L EB 2.109
:= AB 2.109
:L EB 2.110
:= AB 2.110
:L EB 2.111
:= AB 2.111
:L EB 2.112
:= AB 2.112
:L EB 2.113
:= AB 2.113
:L EB 2.114
:= AB 2.114
:L EB 2.115
:= AB 2.115
:L EB 2.116
:= AB 2.116
:L EB 2.117
:= AB 2.117
:L EB 2.118
:= AB 2.118
:L EB 2.119
:= AB 2.119
:L EB 2.120
:= AB 2.120
:L EB 2.121
:= AB 2.121
:L EB 2.122
:= AB 2.122
:L EB 2.123
:= AB 2.123
:L EB 2.124
:= AB 2.124
:L EB 2.125
:= AB 2.125
:L EB 2.126
:= AB 2.126
:L EB 2.127
:= AB 2.127
:***
NETWORK: 0002
:BE
AProgram listing

17
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
© Systeme Lauer GmbH Lauer-driver
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
○○○○○○○
○○
 RESTART-PB
9002 PROGRAMMING UNIT \ PB201
NETWORK: 0001
:L KH 0
:= AB 2.6 FAULT WORD RESET
:= AB 2.7
:= AB 2.8 SET KEY BITS TO 0
:= AB 2.9
:= AB 2.10
:= AB 2.11
:= AB 2.12
:= AB 2.13
:= AB 2.14 DATE/TIME INVALID 1
:= AB 2.15
:= AB 2.35
:= AB 2.36 COMMAND WORD A (KH 0F00)
:= AB 2.38 COMMAND WORD B (KH 0800)
:= AB 2.39 COMMAND WORD C (KH 0000)
:L KH F
:= AB 2.34
:L KH 80
:= AB 2.37
:***
NETWORK: 0002
:BE
 PB FOR COMMUNICATION LOSS
PCS 9002\PB202
NETWORK: 0001
:L KH 0
:= AB 2.8 ZERO KEY BITS!!
:= AB 2.9
:= AB 2.10
:= AB 2.11
:= AB 2.12
:= AB 2.13
:= AB 2.14 DATE/TIME INVALID!!
:= AB 2.15
:***
NETWORK: 0002
:BE
A
Program listing

18
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
© Systeme Lauer GmbHLauer-driver
○○○○○○○
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
○○
 CALL EXAMPLE
This example shows how the parameterization on the enclosed floppy disk is
realized.
PS9002 \ OB1
NETWORK: 0001
:L KH 3 * * ENTER BAUD RATE HERE
:= MB 1 * * 0: 1200 BAUD, 1: 4800 BAUD
:BA FB 200 * * 2: 9600 BAUD, 3: 19200 BAUD
NAME :HANT_PROGRAMMING UNIT
RESET : M 1.1
ERROR : M 1.2
BAUD : MB 1
TOGGLM: M 1.3
:UN M 1.3 IF = 0 => SHORT CYCLE!!
:BEB
:NOP ********************************
:NOP ** !!!! WARNING !!!! **
:NOP ** ONLY OWN PLC PROGRAM **
:NOP ** FROM HERE ONWARDS!!!! **
:NOP ********************************
:U M 1.2
:= A 5.1 GLOBAL ERROR MESSAGE
:U E 4.1
:FLP M 1.4
:= M 1.1 RESET ONLY ON POSITIVE EDGE
:***
NETWORK: 0002
:BE
1 Rev. 0 31.07.91 SYSTEME Date 31.07.1991
LAUER Off. Ran. PCS200 (KOS201 STECKPL.2)
Check PCS300 (KOS201 STECKPL.2)
No.Change Date Name Stand AEG
AProgram listing

19
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
© Systeme Lauer GmbH Lauer-driver
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
○○○○○○○
○○
A3.1 Communication cable programming UNIT/KOS
The connection is made with one 3-wire cable (TXD, RXD, GND)
When using shielded standard cable (3 * 0.14, not twisted in pairs) a maximum
length of 15 meters is recommended. A connection interruption is registered in
both the PCS 200 and 850 and noted in the fault word (ABx.6/ABx.7) for further
evaluation.
A3.1.1 Screening of the communication cable
The screen should be connected on both sides to a metal coated connector case.
The screen can also be connected to pin 1 when using non-metal coated connector
cases. However, this is not recommended for error-technical reasons. There, the
data lines should be covered as completely as possible by the screen! With
grounding at both sides is to be noted however that possibly (because of ground
potential shifts) a potential compensation wire is required having at least 10 times
the screen cross section (reason: compensation currents should not flow through
the cable screen if possible!). This applies particularly if PCS and programmable
controller are not connected to the same earthing point. This is for example valid
where the PCS and programmable controller are not housed in one switching
cabinet! For double sided earthing, use a cable earthing bar, type CER 001, AEGS
E-NR. 424 244 739 on the PCS side. Install according to AEG instructions!
Communication
A3. Communication
A

20
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
© Systeme Lauer GmbHLauer-driver
○○○○○○○
○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○○
○○
Sketch KOS boards (top view)
°- LED
- screw-type terminal
A3.2Programming cable PCS 733
1°gn 1
22
3°yel 3
4°yel←TXD →4
5°yel←RXD →5
66
77
8GND→8
99
10  10
11  11
12 ° yel ←Ready  12
13  13
14  14
15  15
16  16
17  17
18  18
19  19
20  20
21 ° red  21
22 ° red  22
ACommunication