P/N 133487
11
Banner Engineering Corp.
•
Minneapolis, U .S .A .
www .bannerengineering .com • Tel: 763 .544 .3164
SC22-3 Safety Controller
Instruction Manual
Overview
1.7 Internal Logic
The Controller’s internal logic is designed so that a safety output
can turn ON only if all the controlling input device signals are in
the Run state and the Controller’s self-check signals are in the
No-Fault state .
Safety
Input 1
Safety
Input 2
Safety
Controller
Safety
Output 1
Stop
Stop
Run (No Fault)
OFF
Stop
Run
Run (No Fault)
OFF
Run
Stop
Run (No Fault)
OFF
Run
Run
Run (No Fault)
ON
The table above illustrates the logic for two safety input devices
mapped to control Safety Output 1 . If any of the safety input
devices are in the Stop state, then Safety Output 1 is OFF .
When both safety inputs are in the Run state, then Safety
Output 1 will turn ON .
1.7.1 Additional Functions
Other logic functions are slight variations of the general AND
logic rule set .
• Two-Hand Control: The machine initiation signal
incorporating a 0 .5 second actuator simultaneity limit and
anti-tie-down logic, designed to prevent single-actuator
machine cycle operation .
• Safety Device Muting: The automatic suspension of one or
more safety input Stop signals during a portion of a machine
operation when no hazard is present or when access to the
hazard is otherwise safeguarded .
• Safety Device Bypass: The manually activated, temporary
suspension of one or more safety input Stop signals when
the hazard is otherwise safeguarded .
• Enabling Device Control: The actively controlled manual
suspension of a Stop signal during a portion of a machine
operation when a hazard could occur .
The rules that apply to these special cases are explained in
Appendix A .
1.8 Password Overview
To provide security, the Safety Controller requires use of a
password in some cases . For information about changing a
Controller’s password, refer to Sections 4 .2 .1 (PCI) and 5 .3 .4
(OBI) .
NOTE: If the password becomes lost, contact the Factory for
assistance .
Creating a Configuration
• Via computer using the SC22-3 PC Interface (PCI) program
(no password needed)
• Via the Controller Onboard Interface (OBI)
(password needed)
Confirming a Configuration
• Via the PCI, using the PC connected to a powered Controller
(password needed)
• Via the OBI, on a powered Controller (password needed)
Sending a Confirmed Configuration to the Controller
• Via a direct connection between the PC and the Controller,
using the SC-USB1 cable and the PC Interface program
(password needed)
• Via the PC, the XM card programming tool, and the XM card
(password needed)
1.9 Confirming a Configuration
Although a Controller will accept an unconfirmed configuration,
it will only activate it (adopt the configuration and function
according to its parameters) after the configuration is confirmed,
using the OBI .
IMPORTANT: If any modification is made to a confirmed
configuration, or if a configuration is edited during the
confirmation process, the PCI and the Controller will recognize
this modified configuration as being new and will require it to be
confirmed before it can be activated and used .
Once confirmed, a configuration can be stored and reused
without reconfirmation . The configuration code will be validated
automatically each time it is downloaded to a Controller and
whenever the Controller powers up . Configurations, confirmed
or not, can be sent via email . Sending (downloading) a new
confirmed configuration to a Controller requires entry of the
Controller password .
