1–4 Overview of the Clutch/Brake Control System
Publication
65566.5.1 - October 1996
The clutch/brake control system can control the entire press because
you can add your own ladder logic for other press functions. Factory-
protected logic for control of the clutch/brake mechanism is stored in
locked program files (PF2 and PF16). You store your own clutch/
brake interface logic in an unlocked program file (PF15). Either
processor can use program file (PF3) to call subroutines (PFxx) or to
directly control auxiliary press functions that you program.
Organization of Program Files
We organized selected program files in both PLC-5/x6 processors as
follows to control the clutch/brake and other press functions:
Program File Description (Processor in Chassis A) Description (Processor in Chassis B)
PF2 (Locked) Factoryconfigured Master Control Program Identical to the processor in chassis A
PF3 Used to program or call subroutines to control
auxiliary press functions, such as automation
valve, die protection, etc.
Optional but available for application
programming, independent of the
processor in chassis A
PF15 Used to program the clutch/brake interface
with machine sequencing to customize the
clutch/brake code in PF16
Similar to the processor in chassis A
PF16 (Locked) Factoryconfigured clutch/brake code Identical to the processor in chassis A
PFxx Subroutines to control auxiliary press functions Same as PF3
Scanning Program Files
Both PLC-5/x6 processors scan assigned program files shown in Figure 1.3.
Figure 1.3
Program
Scan for the Processor in Chassis A*
I/O Update
PF3
PF15
PF16
Factoryconfigured
Master Control Program
Your Auxiliary
Control Program
Your Clutch/Brake
Interface Program
Factoryconfigured
Clutch/Brake Code
PF2
The processor in chassis B scans the same
program files. We suggest that you mini
mize PF3 in processor B for a faster scan
time and a faster system response.
*
Subroutine PFs
that you program
to control optional
auxiliary functions
How the Software
Controls Your Press