Powerflex 755/755T Integrated Safety Functions Option Module
Powerflex 755/755T Integrated Safety Functions Option Module
Activities including installation, adjustments, putting into service, use, assembly, disassembly, and maintenance are required to
be carried out by suitably trained personnel in accordance with applicable code of practice.
If this equipment is used in a manner not specified by the manufacturer, the protection provided by the equipment may be
impaired.
In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the use
or application of this equipment.
The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and
requirements associated with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or liability for
actual use based on the examples and diagrams.
No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or software
described in this manual.
Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation, Inc., is
prohibited.
Throughout this manual, when necessary, we use notes to make you aware of safety considerations.
WARNING: Identifies information about practices or circumstances that can cause an explosion in a hazardous environment,
which may lead to personal injury or death, property damage, or economic loss.
ATTENTION: Identifies information about practices or circumstances that can lead to personal injury or death, property
damage, or economic loss. Attentions help you identify a hazard, avoid a hazard, and recognize the consequence.
IMPORTANT Identifies information that is critical for successful application and understanding of the product.
SHOCK HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that dangerous
voltage may be present.
BURN HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that surfaces may
reach dangerous temperatures.
ARC FLASH HAZARD: Labels may be on or inside the equipment, for example, a motor control center, to alert people to potential
Arc Flash. Arc Flash will cause severe injury or death. Wear proper Personal Protective Equipment (PPE). Follow ALL Regulatory
requirements for safe work practices and for Personal Protective Equipment (PPE).
Preface
Summary of Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Product Firmware and Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Chapter 1
About Safe Stop and Safe What Is the Integrated Safety Functions Option Module? . . . . . . . . 15
Monitor Functions Compatible Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Compatible Safety Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Safety Application Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Safety Certification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Important Safety Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Stop Category Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Performance Level and Safety Integrity Level (SIL) CL3 . . . . . . 19
Proof Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
PFD and PFH Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
PFD and PFH Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Safety Data for Safe Torque Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Safety Data for Safe Feedback. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Safety Data for Safety I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Spurious Trip Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Safety Reaction Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Considerations for Safety Ratings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Encoder Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Supported Encoders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Encoder Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
General Encoder Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Digital AqB Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Sine/Cosine and Hiperface Diagnostics . . . . . . . . . . . . . . . . . . . . . 27
Contact Information If Safety Option Failure Occurs . . . . . . . . . . . . 28
Chapter 2
Installation Remove Power to the System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Access the Control Pod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Set the SAFETY and Hardware ENABLE Jumpers . . . . . . . . . . . . . . 31
Install the Safety Option Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Feedback Installation Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
I/O Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Power Supply Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Chapter 3
Safety I/O Safety Inputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Safety Input Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Latch Input Error Operation in Single Channel Mode. . . . . . . . 39
Single Channel Safety Input Status Data . . . . . . . . . . . . . . . . . . . . 40
Dual-channel Safety Input Operation . . . . . . . . . . . . . . . . . . . . . . . 41
Equivalent Dual-channel Input Operation. . . . . . . . . . . . . . . . . . . 42
Complementary Dual-channel Input Operation . . . . . . . . . . . . . 43
Standard Input Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Safety Input Safety Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Safety Input Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Determining Safety Input Alarm Type . . . . . . . . . . . . . . . . . . . . . . 48
Safety Input Alarm Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Input Delays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Use With PowerFlex 750-Series ATEX Option Module . . . . . . 50
Safety Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Safety Output with Test Pulse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Single-channel Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Latch Output Error Operation in Single Channel Mode . . . . . . 52
Dual-channel Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Latch Output Error Operation in Dual Channel Mode . . . . . . . 53
Safety Output Safety Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Commanding Safety and Test Outputs. . . . . . . . . . . . . . . . . . . . . . 57
Safety Output Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Determining Safety Output Alarm Type . . . . . . . . . . . . . . . . . . . . 59
Safety Output Alarm Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Test Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Standard Output Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Test Output Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Power Supply Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Test Output Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Test Output Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Test Output Ready . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Chapter 4
Drive-based Safe Stop Safety Output Assembly Safe Stop Function Tags . . . . . . . . . . . . . . . . 65
Functions Safety Input Assembly Safe Stop Function Tags. . . . . . . . . . . . . . . . . . 66
Safety Function in Response to Connection Event . . . . . . . . . . . . . . . 68
Connection Loss Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Connection Idle Action. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Safe Torque Off Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Safe Torque Off Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Safe Torque Off Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Safe Torque Off Delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Safe Torque Off Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Safe Torque Off Stopping Action and Source . . . . . . . . . . . . . . . . 74
Chapter 5
Controller-based Safety Drive Safety Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Functions Before Adding the Safety Instructions . . . . . . . . . . . . . . . . . . . . . . . 95
Drive Safety Instruction Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Pass-through Data Using Standard I/O Mode . . . . . . . . . . . . . . . . . . . 96
Pass-through Data Using Integrated Motion . . . . . . . . . . . . . . . . . . . . 98
SFX Instruction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
SFX Instruction Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Chapter 6
Standard I/O Mode – Safety Assembly Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Configuration, Programming, Configure Safety in the Logix Designer Application . . . . . . . . . . . . . 104
Add a PowerFlex 755 Drive/755T Drive Product to the
and Operation
Safety Controller Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Add an Option Module to a PowerFlex 755 Drive. . . . . . . . . . . 106
Using a 20-750-ENETR Dual-port EtherNet/IP Option
Module with a 20-750-S4 Option Module . . . . . . . . . . . . . . . . . . 124
Safety Configuration Signature and Ownership . . . . . . . . . . . . . 126
Reset Ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Safety Tags in Standard Routines . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Standard Tags in Safety Routines (tag mapping). . . . . . . . . . . . . 126
Standard and Safety Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Safety Function Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Pass-through Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Falling Edge Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Understand Integrated Safety Drive Replacement. . . . . . . . . . . . . . . 130
Replace an Integrated Safety Drive in a GuardLogix System . . 130
PowerFlex 755 IO Mode Using SFX, SS1, and SLS Instructions. . 133
Studio 5000 Logix Designer Application Configuration . . . . . 133
Chapter 7
Integrated Motion – Safety Assembly Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Configuration, Programming, Configure the Integrated Safety Function Option Module in
the Logix Designer Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
and Operation
Add a PowerFlex 755 Drive to the Controller Project. . . . . . . . 144
Understand Module Properties Categories . . . . . . . . . . . . . . . . . . . . . 145
Module Properties>General Category. . . . . . . . . . . . . . . . . . . . . . 146
Module Properties>Connection and Safety Categories . . . . . . 149
Motion Safety>Actions Category . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Motion Safety>Primary Feedback Category . . . . . . . . . . . . . . . . 153
Motion Safety>Secondary Feedback Category . . . . . . . . . . . . . . 155
Motion Safety>Scaling Category. . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Motion Safety>Discrepancy Checking Category . . . . . . . . . . . . 157
Motion Safety>STO Category. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Motion Safety>SS1 Category. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Motion Safety>SBC Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Motion Safety>Input Configuration Category . . . . . . . . . . . . . . 161
Motion Safety>Test Output Category . . . . . . . . . . . . . . . . . . . . . 162
Motion Safety>Output Configuration Category . . . . . . . . . . . . 163
Axis Properties > Actions > Safety Actions . . . . . . . . . . . . . . . . . 164
Module Properties > Associated Axes Motor and Load
Feedback Device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Generate the Safety Network Number (SNN) . . . . . . . . . . . . . . 166
Safety Configuration Signature and Ownership . . . . . . . . . . . . . 167
Reset Ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Replace an Integrated Safety Drive in a GuardLogix System . . 168
Motion Direct Commands in Motion Control Systems. . . . . . 169
Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Motion and Safety Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Motion Safety Instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Safety Function Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Safe Monitor Network Communication. . . . . . . . . . . . . . . . . . . . 179
Explicit Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Application Example - Using SFX, SS1, and SLS Instructions
with Integrated Motion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Studio 5000 Logix Designer Application Configuration . . . . . 185
Programming Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Chapter 8
Monitoring and Monitor Status Using Status Indicators . . . . . . . . . . . . . . . . . . . . . . . . 195
Troubleshooting Module Status Indicator (DS1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Network Status Indicator (DS2) . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Motion Output Status Indicator (DS3) . . . . . . . . . . . . . . . . . . . . 197
Safety Fault Indicator (DS4). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Appendix A
Safety Function Validation Safe Stop 1 (SS1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Checklist Safe Stop 2 (SS2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Safe Operating Speed (SOS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Safely-limited Speed (SLS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Safely-limited Position (SLP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Safe Direction (SDI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Safe Feedback Interface (SFX). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Safe Brake Control (SBC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Appendix B
Specifications, Certifications, Integrated Safety Functions Option Module Specifications . . . . . . 233
and CE Conformity Electrical Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Environmental Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Certifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
CE Conformity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Machinery Directive (2006/42/EC) . . . . . . . . . . . . . . . . . . . . . . . 236
EMC Directive (2014/30/EU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Waste Electrical and Electronic Equipment (WEEE) . . . . . . . . 237
Appendix C
Safety I/O Assemblies and Safety Assembly Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Safety Attributes Safety Feedback Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Safe Stop Function Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Explicit Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Example: Read SS1 Fault Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Appendix D
Parameter Data Parameters and Settings in a Linear List . . . . . . . . . . . . . . . . . . . . . . . . 253
Device Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Host Config Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
This user manual explains how to use PowerFlex® 755 drives and PowerFlex
755T drive products in safety applications up to safety integrity level 3 (SIL 3),
performance level e (PLe), category 4.
This user manual is intended for people that design, install, configure, or
troubleshoot safety applications that use the Integrated Safety Functions
option module (catalog number 20-750-S4).
This user manual covers using network safety with drives in Standard I/O
mode and Integrated Motion mode. All chapters apply to both modes with the
following exceptions:
• Chapter 6 is specific to Standard I/O mode and can be skipped if you are
using Integrated Motion mode.
• Chapter 7 is specific to Integrated Motion mode and can be skipped if
you are using Standard I/O mode.
IMPORTANT You must have a basic understanding of electrical circuitry and familiarity
with PowerFlex 755 drives and PowerFlex 755T drive products. You must also
be trained and experienced in the creation, operation, and maintenance of
safety systems.
Summary of Changes This publication contains new and updated information as indicated in the
following table.
Topic Page
Added attention statement regarding ambient temperature to Environmental Specifications in 235
Appendix B.
Conventions This manual identifies parameter names by listing the parameter number first,
followed by the name in brackets. For example, P7 [STO Fault Type].
Both the Host Config and Device Config parameters exist for this option
module and the parameter numbers overlap. For example, there is a P3 [Device
Config Identity State] and a P3 [Host Config Safety State]. Host Config
parameters reside on the Host (that is, the drive) side of the option module and
are specific to supporting the option module. Device Config parameters reside
on the option module itself.
The PowerFlex 755 drive is used for the examples in this manual.
Terminology Table 1 defines the abbreviations that are used in this manual.
Table 1 - Abbreviations and Definitions
Abbreviation Full Term Definition
Timed SS1 Timed Safe Stop 1 Timed SS1 and Safe Stop 1 time-controlled (SS1-t) are synonymous. Both mean a safe stop where the
motor speed is decelerated to zero and once the maximum stop-time elapses, torque is removed from
SS1-t Safe Stop 1 time-controlled the motor.
• Safe Stop 1 time-controlled (SS1-t) is according to EN/IEC 61800-5-2.
Monitored SS1 Monitored Safe Stop 1 Monitored SS1 and Safe Stop 1 ramp-monitored (SS1-r) are synonymous. Both mean a safe stop where
the motor speed is reduced to standstill within deceleration limits and once standstill speed is reached
SS1-r Safe Stop 1 ramp-monitored or the maximum stop-time elapses, torque is removed from the motor.
• Safe Stop 1 ramp-monitored (SS1-r) is according to EN/IEC 61800-5-2.
1oo2 One out of Two Refers to the behavioral design of a dual-channel safety system.
Classification of the safety-related parts of a control system in respect of their resistance to faults and
CAT Category their subsequent behavior in the fault condition, and which is achieved by the structural arrangement
of the parts, fault detection, and/or by their reliability (source ISO 13849-1).
The maximum SIL rating that can be claimed for a safety-related electrical control system subsystem in
CL Claim Limit relation to architectural constraints and systematic safety integrity (source IEC 62061).
CIP™ Common Industrial Protocol Protocol for industrial automation applications and trademarked by ODVA, Inc.
EN European Norm The official European Standard.
A system, usually independent of the main control system, which is designed to shut down an
ESD Emergency Shutdown Systems operating system safely.
An assembly of devices and/or components working together for protective tripping or presence-
sensing purposes and includes as a minimum:
ESPE Electro-sensitive Protective Equipment • A sensing device.
• Controlling/monitoring devices.
• Output signal-switching devices (OSSD).
The HFT equals n, where n+1 faults could cause the loss of the safety function. An HFT of one means
HFT Hardware Fault Tolerance that two faults are required before safety is lost.
HIM Human Interface Module A module that is used to configure a device.
The International Electrotechnical Commission (IEC) is the organization that prepares and publishes
IEC International Electrotechnical Commission international standards for all electrical, electronic, and related technologies.
IGBT Insulated Gate Bi-polar Transistors Typical power switch that is used to control main current.
The International Organization for Standardization is an international standard-setting body that is
ISO International Organization for Standardization composed of representatives from various national standards organizations.
A set of contacts on a relay or switch that are closed when the relay is de-energized or the switch is de-
NC Normally Closed activated.
A set of contacts on a relay or switch that are open when the relay is de-energized or the switch is de-
NO Normally Open activated.
The component of the electro-sensitive protective equipment (ESPE) connected to the control system
OSSD Output Signal Switching Device of a machine. When the sensing device is actuated during normal operation, the device responds by
going to the OFF-state.
Product Firmware and Product firmware and release notes are available online within the Product
Compatibility and Download Center.
Release Notes
1. From the Search bar on http://www.ab.com, choose Compatibility and
Downloads.
3. On the search results page, find the firmware and release notes for your
product. If no firmware/release notes are available, the module is still
shipping with its original firmware release.
IMPORTANT Both standard connections to the drive and safety connections to the card
must be closed to update the Integrated Safety Functions Module.
See the Product Compatibility and Download Center Quick Start Guide,
publication PCDC-QS001, for instructions on how to find and download
firmware and release notes.
Additional Resources These documents contain additional information concerning related Rockwell
Automation products.
Resource Description
PowerFlex 750-Series Products with TotalFORCE® Control Installation Provides the basic steps to install PowerFlex 755TL low harmonic drives, PowerFlex 755TR
Instructions, publication 750-IN100 regenerative drives, and PowerFlex 755TM drive systems.
PowerFlex 755TM IP00 Open Type Kits Installation Instructions, publication Provides instructions to install IP00 Open Type kits in user-supplied enclosures.
750-IN101
PowerFlex Drives with TotalFORCE Control Programming Manual, publication Provides detailed information on:
750-PM100 • I/O, control, and feedback options
• Parameters and programming
• Faults, alarms, and troubleshooting
Provides information on how to install the Safe Torque Off option module in PowerFlex 750-
PowerFlex 750-Series AC Drive Installation Instructions, publication 750-IN001 Series drive.
PowerFlex 750-Series AC Drives Programming Manual, publication 750-PM001 Provides information on how to mount, install, and configure PowerFlex 750-Series drives.
Enhanced PowerFlex 7-Class Human Interface Module (HIM) User Manual, Provides information for using the 20-HIM-A6 HIM module to configure PowerFlex 750-Series
publication 20HIM-UM001 drives and the Safe Torque Off option module.
GuardLogix Safety Application Instruction Set Reference Manual, Provides information that describes the GuardLogix Safety Application Instruction set.
publication 1756-RM095
EtherNet/IP Network Devices User Manual, publication ENET-UM006 Describes how to configure and use EtherNet/IP devices to communicate on the EtherNet/IP
network.
EtherNet/IP Device Level Ring Application Technique, publication ENET-AT007 Describes Device Level Ring (DLR) topologies, configuration considerations, and diagnostic
methods.
System Design for Control of Electrical Noise Reference Manual, Information, examples, and techniques that are designed to minimize system failures caused by
publication GMC-RM001 electrical noise.
Safety Guidelines for the Application, Installation, and Maintenance of Describes important differences between solid-state control and hardwired electromechanical
Solid-State Control, publication SGI-1.1 devices.
GuardLogix 5580 and Compact GuardLogix 5380 Controller Systems Safety Provides information on safety application requirements for GuardLogix 5580 and Compact
Reference, publication 1756-RM012 GuardLogix 5380 controllers in Studio 5000 Logix Designer® applications.
ControlLogix® 5580 Controllers User Manual, publication 1756-UM543 Provides information on how to use standard ControlLogix 5580 controllers.
CompactLogix™ 5380 Controllers User Manual, publication 5069-UM001 Provides information on how to use standard CompactLogix 5380 controllers.
Product Certification s website, rok.auto/certifications Provides declarations of conformity, certificates, and other certification details.
Notes:
Topic Page
What Is the Integrated Safety Functions Option Module? 15
Compatible Drives 17
Compatible Safety Controllers 17
Safety Application Requirements 18
Safety Certification 18
Proof Tests 20
PFD and PFH Definitions 20
PFD and PFH Data 21
Safety Reaction Time 23
Contact Information If Safety Option Failure Occurs 28
What Is the Integrated The Integrated Safety Functions option module provides a networked STO
(Safe Torque Off ) function via an EtherNet/IP® network. It is also equipped
Safety Functions Option for Integrated (drive-based) Timed SS1, Monitored SS1, and Safe Brake
Module? Control, which operate in the drive and are activated through the network
safety connection.
The Integrated Safety Functions option module also supports select controller-
based EN/IEC 61800-5-2 safety functions operating in GuardLogix® 5580 or
Compact GuardLogix 5380 controllers that use the EtherNet/IP network to
communicate with the safety I/O. This support includes the new safety
function instructions that are provided on the Drive Safety tab in the Logix
Designer application.
When used for safe speed monitoring, the drive can be configured for single- or
dual-feedback to achieve the following safety ratings:
• Single-feedback configurations using safety encoders provide up to SIL
2 PLd capability.
• Dual-feedback configurations provide up to SIL 3 PLe capability when
discrepancy testing (either velocity, position, or both) is enabled. Safety
functions that use position check have up to SIL 2 PLd capability. In this
configuration, at least one encoder (the primary encoder) has to comply
with SIL 2, PL d. The second encoder can be a standard encoder.
IMPORTANT The Integrated Safety Functions option module is suitable for performing
mechanical work on the drive train or affected area of a machine only. It
does not provide electrical safety.
IMPORTANT Multiple safety option modules in a single drive are not allowed. Only one of
these safety option modules can be installed in the drive:
• PowerFlex® 750-Series Safe Torque Off option module
(catalog number 20-750-S)
• PowerFlex 750-Series Safe Speed Monitor option module
(catalog number 20-750-S1)
• PowerFlex 755/755T Integrated Safety - Safe Torque Off option module
(catalog number 20-750-S3)
• PowerFlex 755/755T Integrated Safety Functions option module (catalog
number 20-750-S4)
ATTENTION: If two output IGBTs fail in the drive, when the Integrated Safety
Functions option module has controlled the drive outputs to the Off state, the
drive can provide stored energy for up to 180° of rotation in a 2-pole motor
before torque production in the motor stops.
IMPORTANT Do not use this option module as a control for starting or stopping the drive.
Compatible Drives The Integrated Safety Functions option module is compatible with these
PowerFlex 755 drives and PowerFlex 755T drive products:
• PowerFlex 755 drives (v14.xxx or later)
• PowerFlex 755TL low harmonic drives (v4.xxx or later)
• PowerFlex 755TR regenerative drives (v4.xxx or later)
• PowerFlex 755TM common bus inverters (v4.xxx or later)
IMPORTANT The Integrated Safety Functions option module is not compatible with
PowerFlex 753 drives.
Integrated safety functions are controlled via the embedded Ethernet port on
the drive only. The 20-750-ENETR can still be used, but only in conjunction
with the embedded Ethernet port by being in Tap mode (safety messages must
go through the embedded Ethernet port on drive).
The following Add-on Profiles (AOPs) are needed depending on the drive and
type of control used:
Compatible Safety A GuardLogix safety controller is required for use of the Integrated Safety
Functions option module that is used in Network mode control (‘Safety’,
Controllers ‘Standard and Safety’, or ‘Motion and Safety’ used for Connection type). The
following GuardLogix controllers can be used:
Safety Application Create, record, and verify the safety signature as part of the required safety
application development process. The safety controller creates the safety
Requirements signature, which consists of an identification number, date, and time that
uniquely identifies the safety portion of a project. This signature covers all
safety logic, data, and safety I/O configuration.
If the Drive Safety Function Instructions are used in the safety application,
special consideration must be taken to verify the application. See Appendix A
for guidance on verifying the drive safety function instructions.
Safety Certification The TÜV Rheinland group has approved the PowerFlex 755 Integrated Safety
Functions option module (catalog number 20-750-S4) as suitable for use in
integrated safety applications:
• Up to and including SIL 3 according to IEC 61508
• Up to and including SIL CL3 according to IEC 62061
• Up to and including PLe (Category 4) according to ISO 13849-1.
IMPORTANT Only qualified, authorized personnel that are trained and experienced in
functional safety can plan, implement, and apply functional safety systems.
IMPORTANT When designing the machine application, consider timing and distance for a
coast-to-stop (Stop Category 0 or Safe Torque Off). For more information on
stop categories and Safe Torque Off, see EN 60204-1 and EN/IEC 61800-5-2.
See the ISO 13849-1, IEC 61508, and EN 62061 standards for complete
information on requirements for PL and SIL determination.
Proof Tests IEC 61508 requires you to perform various proof tests of the equipment that is
used in the system. Proof tests are performed at user-defined times. For
example, proof tests can be once a year, once every 15 years, or whatever time
frame is appropriate.
The Integrated Safety Functions option module has a useful life of 20 years, no
proof test required. Other components of the system, such as safety I/O
devices, sensors, and actuators can have different useful life times.
IMPORTANT The time frame for the proof test interval depends on the specific
application.
PFD and PFH Definitions Safety-related systems can be classified as operating in either a Low Demand
mode, or in a High Demand/Continuous mode.
• Low Demand mode: where the frequency of demands for operation,
made on a safety-related system, is no greater than one per year, or no
greater than twice the proof-test frequency.
• High Demand/Continuous mode: where the frequency of demands for
operation, made on a safety-related system, is greater than once per year,
or greater than twice the proof test interval.
PFD and PFH Data These PFDavg and PFH calculations are based on the equations from Part 6 of
EN 61508 and show worst-case values.
Table 2, and Table 3 provide PFDavg and PFH values for the Safe Torque Off
(STO) or Timed Safe Stop 1 functions. These values apply when Safety
Instance is set to ‘Safe Stop Only – No Feedback’.
Table 2 - PFD and PFH for PowerFlex 755 Drives STO and Timed SS1
Table 3 - PFD and PFH for PowerFlex 755T Drive Products STO and Timed SS1
Attribute Frames 5 and 6 Frames 7 and 8 Frame 9 Frame 10 Frame 11 Frame 12 Frame 13 Frame 14 Frame 15
PFD(average) 4.49E-5 2.56E-4 2.82E-4 3.08E-4 3.34E-4 3.60E-4 3.86E-4 4.38E-4 4.90E-4
PFH (1/hour) 5.24E-10 2.96E-9 3.25E-9 3.55E-9 3.85E-9 4.15E-9 4.45E-9 5.05E-9 5.65E-9
SIL 3 3 3 3 3 3 3 3 3
PL e e e e e e e e e
Category 4 4 4 4 4 4 4 4 4
MTTFD years 187.5 (high) 102.6 (high) 87.8 (high) 76.7 (high) 68.1 (high) 61.2 (high) 55.6 (high) 47 (high) 40.7 (high)
DCavg% 97.4% (high) 97.0% (high) 97.0% (high) 97.0% (high) 97.0% (high) 96.9% (high) 96.9% (high) 96.9% (high) 96.9% (high)
HFT 1 (1oo2) 1 (1oo2) 1 (1oo2) 1 (1oo2) 1 (1oo2) 1 (1oo2) 1 (1oo2) 1 (1oo2) 1 (1oo2)
Mission time 20 years 20 years 20 years 20 years 20 years 20 years 20 years 20 years 20 years
Table 4 provides PFDavg and PFH values to add to the PFDavg and PFH values
from Table 2 or Table 3 for safety functions that require safe encoder feedback.
Safety functions using safe encoder feedback include drive based Monitored
Safe Stop 1 and controller-based safety functions SS1, SS2, SOS, SLS, SLP, and
SDI.
In general, the PFDavg and PFH values from Table 4 should be added to
Table 2 and Table 3 when Safety Instance is set to ‘Single Feedback
Monitoring’ or ‘Dual Feedback Monitoring’.
IMPORTANT Achievable safety rating depends on each system component. For Safe
Feedback, the safety rating of the selected encoders may limit the safety
rating of the system.
The Integrated Safety Functions option module provides four safety inputs
and two safety outputs. Table 5 provides PFDavg and PFH values to add for
safety functions that use this Safety I/O.
Table 5 - PFD or PFH to Add When Safety Functions Use Safety I/O
Attribute Single Channel Safety I/O Dual Channel Safety I/O
PFD (average) 3.35E-4 2.49E-4
PFH (1/hour) 3.83E-9 2.84E-9
SIL 2 3
PL d e
Category 2 4
MTTFD years 1064.9 (high) 1998.0 (high)
Table 5 - PFD or PFH to Add When Safety Functions Use Safety I/O
Attribute Single Channel Safety I/O Dual Channel Safety I/O
DCavg% 96.4% (high) 94.2% (high)
HFT 0 (1oo1) 1 (1oo2)
Mission time 20 years 20 years
IMPORTANT Single channel safety I/O is only certified for use in functional safety
applications with process safety times greater than or equal to 300 ms; or
applications with demand rates less than or equal to 1 demand per 30
seconds.
IMPORTANT If single channel safety I/O is used, pulse testing (external pulse testing for
safety inputs, pulse testing for safety outputs) MUST be enabled on the
single channel I/O points.
Table 6 shows the Spurious Trip Rate (STR) and Mean Time to Failure
Spurious (MTTF Spurious) values for the Integrated Safety Functions option
module, calculated according to the ISA TR-84 method.
Table 6 - STR and MTTF Spurious Values
Attribute Value
Spurious Trip Rate 3.00E-6
MTTFSpurious (years) 37.0
Safety Reaction Time The safety reaction time is the length of time from a safety-related event as
input to the system until the system is in the safe state. Table 7 shows the safety
reaction time from an input signal condition that triggers a safe stop, to the
initiation of the configured Stop Type. For details on how to calculate system
reaction times with GuardLogix controllers, see the GuardLogix Controller
Systems Safety Reference Manuals listed in the Additional Resources on
page 13.
IMPORTANT An input signal condition that is present for less than the reaction time may
not result in the safety function being performed. Repeated requests of the
safety function for less than the reaction time can result in a spurious
detection of a fault.
IMPORTANT In network STO Mode, the safety reaction time in Table 7 does not include
the connection reaction time limit. See the GuardLogix Controller Systems
Safety Reference Manuals, listed in the Additional Resources on page 13, for
details.
Considerations for Safety The achievable safety rating of an application that uses the Integrated Safety
Functions option module that is installed in PowerFlex 755/755T drive
Ratings products is dependent upon many factors, drive options, and the type of motor.
A safety rating up to and including SIL 3, PLe, and Category 4 can be achieved.
Encoder Considerations This section describes factors to consider when using an encoder with the
Integrated Safety Functions option module.
Supported Encoders
Table 8 describes the supported encoder types based on the feedback card that
is used and the physical terminal it is connected to. You must determine the
safety capability of a system based on the supported encoder types and the
encoder diagnostics that are described in this chapter.
Table 8 - Supported Feedback Cards and Encoder Types
Primary Channel Secondary Channel
Feedback Option Achievable System Safety Rating
Encoder Type Encoder Motion Axis Encoder Type Encoder Motion Axis
Not Used Not Used SIL 2/PL d with safety rated encoder
20-750-UFB-1 Sine/Cosine
Digital AqB Load Feedback SIL 3/PL e
Motor Feedback
Not Used Not Used SIL 2/PL d with safety rated encoder
20-750-DENC-1 Digital AqB
Digital AqB Load Feedback SIL 3/PL e
Encoder Diagnostics
Depending on the encoder type, the module performs several diagnostic tests
on encoder signals to detect faults in the encoder. You must determine if the
combination of the selected encoder device type and the diagnostics that are
described in this chapter will satisfy the required safety function rating. The
use of non-safety, standard encoders my require further analysis and assessment
activties.
The following encoder diagnostics are available for all supported encoder
types:
• Encoder Voltage Monitoring (Configurable)
• Maximum Speed Limit (Configurable)
• Maximum Acceleration (Configurable)
• Maximum Encoder Input Frequency
• Dual Encoder Velocity and/or Position Discrepancy (Configurable)
IMPORTANT These diagnostics are based on the capability of the chosen encoder and its
rated limits. They do not provide a safety-rated safety function.
The voltage monitoring diagnostic samples the voltage being supplied to the
encoder to confirm that its level is within its configured range. If the voltage
monitoring diagnostic detects a voltage that is out of the configured range, the
safety feedback instance reports a voltage monitoring fault and causes the
module to enter the safe state.
If a voltage range is not specified, then the voltage monitoring diagnostic is not
performed.
The maximum speed limit diagnostic detects when encoder speed is above a
configured limit. If the speed of the encoder is greater than the configured max
speed limit, an exceeded max speed fault is reported by the safety feedback
instance. This causes the module to enter the safe state.
If the encoder being used specifies a maximum speed, set the maximum speed
limit configuration value to this value or lower. If the limit is configured as 0,
this diagnostic is not be performed.
Maximum Acceleration
encoder has exceeded the configured limit, a max acceleration fault is reported
by the safety feedback instance. This causes the module to enter the safe state.
If the encoder being used specifies a maximum acceleration, set the maximum
acceleration configuration value to this value or lower. If the maximum
acceleration is configured as 0, this diagnostic is not performed.
The maximum encoder input frequency diagnostic confirms that the safety
feedback signals do not exceed the maximum frequency (encoder counts per
second) supported by the module. This value is not configurable and has fixed
values based on the encoder type. Table 9 shows the maximum frequency based
on encoder type.
Table 9 - Maximum Frequency of Encoder Types
Encoder Type Max Frequency
Digital AqB 250 kHz
Sine/Cosine and Hiperface 163.8 kHz
If the module detects an encoder input frequency above the limit, a max
frequency fault is reported in the safety feedback instance and the module
enters the safe state.
The dual encoder velocity and position discrepancy diagnostic confirms that
the position and/or velocity of the two encoders match within a configurable
tolerance. The position and velocity discrepancy limits are individually
configurable; setting the limit to a value of 0 disables the diagnostic check. If
the module detects that the difference between the position and/or velocity of
both encoders is outside the configured limit, a discrepancy error is reported in
both safety feedback instances and the module enters the safe state. This
diagnostic is only available when the module is configured in a dual feedback
configuration.
The inverse signal monitoring diagnostic confirms that the inverted and non-
inverted signals are always at opposite signal levels. If the module detects a non-
inverted signal, a feedback signal lost fault is reported in the safety feedback
instance and the module enters the safe state. This diagnostic is meant to detect
encoder wiring errors, such as open, short, or short to power.
The quadrature error detection confirms that the A and B signals from the
digital AqB encoder do not change simultaneously. This diagnostic is also
referred to as an exclusive bit check. If the module detects a quadrature error,
the safety feedback instance reports a quadrature error fault and enters the safe
state. A simultaneous change indicates an error with the encoder wiring or an
issue with the encoder itself.
The Sin2 + Cos2 vector length monitoring diagnostic confirms that the sine
and cosine signals are sinusoidal and 90° apart. This diagnostic is meant to
detect errors in the wiring of the encoder and problems within the encoder
itself. Table 10 describes the tolerance of encoder output signal amplitudes for
this diagnostic. Table 11 describes the phase tolerance of the diagnostic. If the
module detects that the amplitude and or phase of the signals is out of range,
the safety feedback instance reports a Sin2 + Cos2 fault and the module is
placed in the safe state.
Zero-crossing Detection
The zero-crossing detection diagnostic confirms that the sine and cosine
signals have a similar offset to ground. The offset tripping point is ± 50 mV. If
the offset of the sine and cosine signals is greater than the tripping point, the
zero-crossing detection diagnostic will fail, a signal lost fault is reported in the
safety feedback instance, and the module is placed in the safe state.
Signal Offset
Table 12 describes the offset tolerance of the diagnostic. If the offset of the Sine
and or Cosine signals are outside the tolerance range, the safety feedback
instance reports a signal offset fault and the module is placed in the safe state.
Table 12 - Signal Offset Tolerance
Max Min
3.0V 2.0V
Contact Information If Safety If you experience a failure with any safety-certified device, contact your local
Allen-Bradley distributor to request any of these actions:
Option Failure Occurs
• Return the device to Rockwell Automation so the failure is
appropriately logged for the catalog number that is affected and a record
is made of the failure.
• Request a failure analysis (if necessary) to determine the probable cause
of the failure.
For more information about replacing drives, see Replace an Integrated Safety
Drive in a GuardLogix System on page 130 and Replace an Integrated Safety
Drive in a GuardLogix System on page 168.
Installation
This chapter provides installation, jumper settings, and wiring for the
Integrated Safety Functions option module.
Topic Page
Remove Power to the System 30
Access the Control Pod 30
Set the SAFETY and Hardware ENABLE Jumpers 31
Install the Safety Option Module 32
I/O Wiring 34
Cabling 34
IMPORTANT Installation must be in accordance with the instructions in this user manual
and the installation instructions for your drive.
Only qualified, authorized personnel that are trained and experienced in
functional safety can plan, implement, and apply functional safety systems.
IMPORTANT During installation and maintenance, check your drive firmware release
notes for known anomalies and verify that there are not safety-related
anomalies.
A safety analysis is required to determine how often to test the safety function
for proper operation during the life of the machine.
Remove Power to the System Before performing any work on the drive, remove all power to the system.
ATTENTION:
• Electrical Shock Hazard. Verify that all sources of AC and DC power are de-
energized and locked out or tagged out in accordance with the requirements
of ANSI/NFPA 70E, Part II.
• To avoid an electric shock hazard, verify that the voltage on the bus
capacitors has discharged before performing any work on the drive. Measure
the DC bus voltage at the +DC and -DC terminals or test points. The voltage
must be zero. For the location of the terminal block and test point sockets,
see the manual for your drive:
• PowerFlex® 750-Series AC Drive Installation Instructions,
publication 750-IN001
• PowerFlex 750-Series Products with TotalFORCE® Control Installation
Instructions, publication 750-IN100
• PowerFlex 755TM IP00 Open Type Kits Installation Instructions,
publication 750-IN101
• In Safe Torque Off mode, hazardous voltages may still be present at the
motor. To avoid an electric shock hazard, disconnect power to the motor and
verify that the voltage is zero before performing any work on the motor.
Access the Control Pod The option module is installed in the drive control pod. Different drives have
different ways to access the control pod. To access the control pod, follow these
steps.
See the installation instructions for your drive for more information.
Set the SAFETY and Hardware The PowerFlex 755/755T drive products ship with the safety jumper
(SAFETY) installed.
ENABLE Jumpers
If the Integrated Safety Functions option module is installed, the control board
SAFETY jumper must be removed. If the SAFETY jumper is not removed, a
‘Safety Jumper In’ fault occurs.
IMPORTANT PowerFlex 755 drives (frames 8…10) control boards do not have a SAFETY
jumper.
If the Integrated Safety Functions option module is installed, the control board
hardware ENABLE jumper must be installed. If the hardware ENABLE
jumper is not installed, a ‘HW Enbl Jmpr Out’ fault occurs (only frames 1…7
of PowerFlex 755 drives and all frame sizes of PowerFlex 755T drive products).
Figure 3 - PowerFlex 755T Drive Products Jumper Locations (all frame sizes)
SAFETY Jumper
(jumper is removed)
Install the Safety Option To install the Integrated Safety Functions option module in a drive port, follow
these steps:
Module
1. Firmly press the module edge connector into the desired port.
IMPORTANT Only one safety option module can be installed in a drive. Multiple
safety option modules or duplicate safety option module
installations are not supported.
Follow these guidelines for the Integrated Safety Functions option module.
Feedback Devices
The Integrated Safety Functions option module can be used with one of the
following feedback devices when safe feedback monitoring is used:
• Dual-incremental Encoder module, catalog number 20-750-DENC-1
• Universal Feedback module catalog number 20-750-UFB-1
Only one feedback card can be used in conjunction with the Integrated Safety
Functions module. For information on the supported encoder types for a given
feedback device, see Encoder Considerations in Chapter 1.
Port Assignment
Jumper Settings
I/O Wiring This section describes the onboard safety I/O and wiring considerations. A
power supply must be connected between the SP and SC terminals in order for
the safety I/O to be used. See Power Supply Requirements on page 35 for
information on selecting a power supply.
IMPORTANT External 24V power is only required to the module when hardwired safety is
used. It is NOT required when the module is used for networked safety
operation.
NC NC No Connection
So0 So0 Safety Output 0 Safety 24V DC output 0
SC SC Safety Common Safety power common
So1 So1 Safety Output 1 Safety 24V DC output 1
Si0 Safety Input 0 Safety 24V DC input 0
Si0
SC SC Safety Common Safety power common
Si1 Si1 Safety Input 1 Safety 24V DC input 1
SC SC Safety Common Safety power common (required if safety I/O used)
SP SP Safety Power Safety 24V DC power (required if safety I/O used)
For examples of wiring devices to the safety I/O, see the Guard I/O™ EtherNet/
IP Safety Modules User Manual, publication
1791ES-UM001.
For technical specifications of the safety I/O, see Integrated Safety Functions
Option Module Specifications in Appendix B.
For more information, see the guidelines in Industrial Automation Wiring and
Grounding Guidelines, publication 1770-4.1.
Notes:
Safety I/O
This chapter provides information that is related to the embedded safety inputs
and outputs on the Integrated Safety Functions option module.
Topic Page
Safety Inputs 37
Safety Outputs 50
Safety Inputs Read this section for information about safety inputs and their operation
modes. The safety inputs can be used in a single or dual-channel configuration
for monitoring a safety input device. A safety input can also be configured for
external pulse testing with an associated test output.
The safety inputs also support configuring a sample delay time. You can
configure both on→off and off→on sample delay times for each input point. You
can also configure a latch error time, which specifies the minimum amount of
time that a safety input alarm is reported.
A test output can be used in combination with a safety input for short-circuit
detection. Configure the test output as a pulse test source and configure the
safety input as ‘Used with Test Output’. Test Output 0 is associated with safety
inputs 0 and 2. Test Output 1 is associated with safety inputs 1 and 3.
When the external input contact is closed, a test pulse is output from the test
output terminal to diagnose the field wiring and input circuitry. By using this
function, short circuits between input signal lines and the power supply
(positive side), and short circuits between redundant input signal lines of one
external device can be detected. Safe wiring by customer action is required.
ON
Typical Pulse
Typical Pulse
TestPeriod
Test Period OFF
OFF
300 ms
300ms
Typical
Typical
Pulse
Pulse
Width
Width
500 μs
100µs
IMPORTANT When using external pulse testing in single-channel mode, the demand rate
of the input must be greater than 30 seconds.
To1
Si2
SC
Si3
To0 External Contact
NC
So0
SC
External
So1 Contact
External
Si0 Contact
SC
Si1
SC Short Circuit Between Input Signal Lines
SP
Short Circuit Between Input Signal Lines and
Power Supply (positive side)
The safety input subsystem allows for a configurable time for which an alarm
state is held. This is referred to as Input Latch Error Time. In single channel
mode, the input latch error time describes the period between when the alarm
condition is removed and when the safety input stops reporting the alarm.
Figure 7 shows the operation of input latch error time in single channel mode.
See Safety Input Alarm Recovery on page 49 for information on removing an
alarm.
Normal Operation
Pulse Test ON
Output OFF
Pulse Test
Occurs
External Device ON
OFF
Safety Input ON
Terminal OFF
Safety Input ON
Value OFF
Safety Input OK
Status ALARM
Alarm Operation
Pulse Test ON
Output OFF Pulse Test
Occurs
External Device ON
OFF
Safety Input ON
Terminal OFF
Safety Input ON
Value OFF
Figure 8 describes the status and value that is reported by the Safety IO
subsystem for normal and alarm states. In normal operation, the Safety Input
value reported is the value being read on the input terminal. The Safety Input
status is on. When a fault is detected, the Safety Input value and status are
forced off.
Figure 8 - Single Channel Normal Operation and Alarm Detection (not to scale)
Normal Operation
Pulse Test ON
Output OFF
Pulse Test
ON Occurs
External Device
OFF
Safety Input ON
Terminal OFF
Safety Input ON
Value OFF
Safety Input OK
Status ALARM
Alarm Operation
Pulse Test ON
Output OFF Pulse Test
Occurs
External Device ON
OFF
Safety Input ON
Terminal OFF
Safety Input ON
Value OFF
When using either dual-channel input mode, the time from when a
discrepancy is created and when the discrepancy is reported can be configured.
This is referred to as Discrepancy Time. The configured discrepancy time is
0 (deactivated)…65,530 ms in increments of 1 ms.
IMPORTANT The dual-channel function is used with two consecutive inputs that are
paired together, this process starts at an even input number, such as
inputs 0 and 1; 2 and 3; and so on.
IMPORTANT Do not set the discrepancy time longer than necessary. The purpose of
the discrepancy time is to allow for normal differences between contact
switching when demands are placed on safety inputs. For discrepancy
checking to operate correctly, only one demand on the safety input is
expected during the discrepancy time. If the discrepancy time is set too
high, and multiple demands occur during this time, then both safety
input channels will alarm.
Table 15 shows the relation between physical input terminal states and the data
and status reported by the Safety Input subsystem.
Table 15 - Terminal Input Status and Controller I/O Data
Dual-channel Mode Input Terminal Controller Input Data and Status Dual-channel Dual-channel
Si0 Si1 Safety Safety Safety Safety Resultant Input
Input 0 Data Input 1 Data Input 0 Status Input 1 Status Data Status
Dual-channels, Equivalent OFF OFF OFF OFF OK ON OFF OK
OFF ON OFF OFF ALARM OFF OFF Alarm
ON OFF OFF OFF ALARM OFF OFF Alarm
ON ON ON ON OK ON ON OK
Dual-channels, Complementary OFF OFF OFF ON ALARM OFF OFF Alarm
OFF ON OFF ON OK ON OFF OK
ON OFF ON OFF OK ON ON OK
ON ON OFF ON ALARM OFF OFF Alarm
If the second transition does not occur before the discrepancy time elapses, the
channels transition to the alarm state. In the alarm state, the input and status
for both channels are set low (off ). When configured as an equivalent dual
pair, the data bits for both channels are sent to the controller as equivalent,
both high or both low.
Figure 9 shows the operation of dual channel equivalent inputs under normal
and alarm conditions.
Safety Input 1 ON
Terminal OFF
Safety Input 0 ON
Value OFF
Safety Input 1 ON
Value OFF
Dual Channel OK
Status ALARM
Safety Input 1 ON
Terminal OFF
Safety Input 0 ON
Value OFF
Safety Input 1 ON
Value OFF
If the second transition does not occur before the discrepancy time elapses, the
channels transition to the alarm state. The alarm state of complementary
inputs is the even-numbered input turned off and the odd-numbered input
turned on. If in the alarm state, both channel status bits are set low. When
configured as a complementary dual-channel pair, the data bits for both
channels are sent to the controller in complementary, or opposite states.
Safety Input 1 ON
Terminal OFF
Safety Input 0 ON
Value OFF
Safety Input 1 ON
Value OFF
Dual Channel OK
Status ALARM
Alarm Operation
Discrepancy
Time
Safety Input 0 ON
Terminal OFF
Safety Input 1 ON
Terminal OFF
Safety Input 0 ON
Value OFF
Safety Input 1 ON
Value OFF
Alarm Detected
Dual Channel OK
Status ALARM
The Safety Input data of the Integrated Safety Functions module can be
monitored through:
• Safety Input Assembly
• DPI™ Parameters
• CIP™ Messaging
IMPORTANT Only the Safety Input Value and Status in the Safety Input Assembly can be
considered safety data. Input values read through DPI parameters or CIP
messages are not safety data. Do not use standard inputs for safety purposes.
The following Safety Input data is available in the Integrated Safety Functions
Module:
• Safety Input Status
• Safety Input Value
• Safety Input Valid
Each safety input point reports its own status, value, and valid attributes.
IMPORTANT If a safety input is configured for standard input mode, its associated safety
data is forced in the safe state.
The safety input status indicates whether an alarm is present in the safety input
point. The safety input status is provided in the safety input assembly, as shown
in Table 17. Table 18 describes the attributes for reading the safety status via
CIP messaging.
The safety input status is also provided in the first four bits of device parameter
P13 [Safety IO Status].
Table 17 - Safety Input Assembly Tags for Safety Input Status
Safety Input Assembly Tag Name Type/[bit] Description
(safety controller to S4 option)
module:SI.InputStatus SINT A collection of safety input values and status for each
safety input
module:SI.In01Status [4] Status of Safety Input 0
0 = Alarm
1 = OK
module:SI.In01Status [5] Status of Safety Input 1
0 = Alarm
1 = OK
module:SI.In02Status [6] Status of Safety Input 2
0 = Alarm
1 = OK
module:SI.In03Status [7] Status of Safety Input 3
0 = Alarm
1 = OK
The safety input value is the value of the input after safety and on/off delay
evaluations when the safety input is not in the alarm state. If the safety input is
in the alarm state, this value will always be 0.
The safety input value is provided in the safety input assembly, as shown in
Table 19. Table 20 describes the attributes for reading the safety value via CIP
messaging. The safety input value is also provided in the first four bits of device
parameter P12 [Safety IO Values].
When set, the safety input valid attribute indicates that the safety input is
configured for safety use and producing valid data. If this value is not set, the
data that is associated with the safety input is no longer valid safety data.
IMPORTANT The Safety Input Valid attribute should be checked before using safety input
data in a safety application.
The safety input valid attribute is provided in the safety input assembly, as
shown in Table 21. Table 22 describes the attributes for reading the safety value
via CIP messaging.
Configuration Error
Circuit Error
A circuit error occurs in a safety input when a pulse test fails. There are two
types of circuit errors that can be reported:
• Internal Circuit Error
• External Circuit Error
An internal circuit error occurs when an internal pulse test fails. This means
that circuitry inside the module has failed. An internal circuit error may not be
recoverable; replacing the module may be required.
An external circuit error occurs when pulse testing by the safety input’s
associated test output fails. This error indicates the input circuitry external to
the card has failed.
The discrepancy and dual channel errors are related, as a discrepancy can only
occur when the safety input is in dual channel mode. A discrepancy error
occurs when one of the dual channel safety inputs is not reporting the expected
safety input value. The safety input with the unexpected value reports the
discrepancy error. The other associated safety input will also be put in the safe
state and report a dual channel error alarm.
To read an alarm type of safety input with DPI parameters, follow these steps:
1. Set device parameter P14 [Input Alarm Indx] to the integer value i +1,
where i is the number of the safety input.
2. Read device parameter P15 [Input Alarm].
The safety input alarm type can also be read via CIP messaging. See Table 21
for the attributes that are required to read the alarm type.
If an error is detected, the safety input data remains in the off state. Follow this
procedure to activate the safety input data.
TIP If the latch error time has expired, but the safety input is not yet in the safe
state, the alarm will not be cleared. Once the safety input is in the safe state,
the alarm will clear immediately.
Input Delays
Each safety input has a configurable filter time for sampling the input. Both the
onoff and offon filter values can be configured. Unlike other
configuration values, these values can be configured in standard input mode
Off–on Delay
An input signal is treated as logic 0 during the on-delay time (0…126 ms, in
increments of 1 ms) after the rising edge of the input contact. The input only
turns on if the input contact remains on after the on-delay time has elapsed.
This delay helps prevent rapid changes of the input data due to contact bounce.
ON
Input Signal OFF
ON
Safety Input Value
OFF
On-delay
On-off Delay
An input signal is treated as logic 1 during the off-delay time (0…126 ms, in
increments of 1 ms) after the falling edge of the input contact. The input only
turns off if the input contact remains off after the off delay time has elapsed.
This delay helps prevent rapid changes of the input data due to contact bounce.
Input Signal ON
OFF
ON
Safety Input Value
OFF
Off-delay
Safety Outputs Read this section for information about safety outputs. The safety outputs can
operate in single channel mode or dual channel mode. In either mode, the
safety output can also be configured to run pulse test diagnostics.
When the safety output is on, the safety output can be configured to pulse test
the safety output channel. By using this function, you can continuously test the
ability of the safety output to remove power from the output terminals of the
module. If an error is detected, the safety output data and individual safety
output status turn to the safe state.
ON
Typical Pulse
Test Period
300 ms OFF
Typical
Pulse
Width
500 μs
IMPORTANT To help prevent the test pulse from causing the connected device to
malfunction, pay careful attention to the input response time of the device
that is connected to the output.
Single-channel Mode
IMPORTANT When using pulse testing in single channel mode, the demand rate of the
output must be greater than 30 seconds.
In single-channel mode, when the safety output is requested to the on state, the
output will turn on if there is no alarm. If an alarm is detected on the channel,
the safety output data and safety output status turn off, and commanding the
output will have no effect.
Safety Output ON
Value OFF
Safety Output ON
Status OFF
Alarm Operation
Safety Output ON
Terminal OFF
Safety Output ON
Value OFF
Alarm Detected
Safety Output ON
Status OFF
The safety output subsystem allows for a latch error time to be configured. The
latch error time is the minimum time an output alarm will be held before the
alarm can be cleared. This latch error time is used by all safety outputs.
Figure 15 shows the behavior of the safety output latch time in single channel
mode. See Safety Output Alarm Recovery on page 60 for information on
clearing alarms.
Output
Latch Error
Time
Safety Output 0 ON
Value OFF
Safety Output OK
Status ALARM
Alarm
Alarm Detected Condition
Removed and Alarm Cleared
Safety Output
Value in Safe
State
Dual-channel Mode
When the data of both channels is in the on state, and neither channel has an
alarm, the outputs are turned on. The status is normal. If an alarm is detected
on one channel, the safety output data and individual safety output status turn
off for both channels.
Figure 16 shows the operation of dual channel outputs under normal and alarm
conditions.
Safety Output 1 ON
OFF
Dual Channel ON
Output Status OFF
Alarm Operation
Safety Output 0 ON
Value OFF
Safety Output 1 ON
Value OFF
Alarm Detected
Dual Channel ON
Output Status OFF
In dual channel mode, the output latch error time describes the period between
when the alarm condition is removed and when the dual channel safety output
stops reporting the alarm. Figure 17 shows the normal operation of output
latch error time in dual channel mode. When one or both of the associated
output points has an alarm (such as a Pulse Test Failure), and there is a
discrepancy between the two channels, the alarm and discrepancy must be
cleared before the latch error timer begins counting. Figure 18 shows this
special case operation. See Safety Output Alarm Recovery on page 60 for
information on removing an alarm.
Output
Latch Error
Time
Safety Output 0 ON
Value OFF
Safety Output 1 ON
Value OFF
Dual Channel OK
Safety Output ALARM
Status
Dual Channel OK
Safety Output ALARM
Status
Figure 18 - Dual Channel Output Latch Error Behavior With Alarm and Discrepancy (not to scale)
Dual Channel
Equivalent Mode
Output
Latch Error
Safety Output 0 ON Time
Value OFF
Safety Output 1 ON
Value OFF
Dual Channel OK
Safety Output ALARM
Status
Discrepancy
Removed
Alarm Cleared
Alarm Detected
Discrepancy
Detected
The Safety Output data of the Integrated Safety Functions module can be
monitored through:
• Safety Input Assembly
• DPI Parameters
• CIP Messaging
Each safety output point reports its own status, monitor value, and ready
attributes.
The safety output status indicates whether an alarm is present in the safety
output point. The safety output status is provided in the safety input assembly,
as shown in Table 25. Table 26 describes the attributes for reading the safety
status via CIP messaging. The safety output status is also provided in bits 6 and
7 of device parameter P13 [Safety IO Status].
Table 25 - Safety Input Assembly Tags for Safety Output Status
Safety Input Assembly Tag Name Type / [bit] Description
(safety controller to S4 option)
module:SI.OutputStatus SINT A collection of safety output status, safety output
monitor values, and test output status
module:SI.Out00Status [4] Status of Safety Output 0
0 = Alarm
1 = OK
module:SI.Out01Status [5] Status of Safety Output 1
0 = Alarm
1 = OK
When set, the safety output ready attribute indicates that the safety output is
configured for safety use and ready to be commanded.
IMPORTANT Check the Safety Output Ready attribute before commanding the safety
output.
The safety output ready attribute is provided in the safety input assembly, as
shown in Table 27. Table 28 describes the attributes for the Safety Output
Ready attribute via CIP messaging.
Table 27 - Safety Input Assembly Tags for Safety Output Ready
Safety Input Assembly Tag Name Type/[bit] Description
(safety controller to S4 option)
module:SI.IOSupport SINT A collection of bits describing safety IO
functionality
module:SI.Out00Ready [4] Safety Output 0 Ready
0 = Not Ready
1 = Ready
module:SI.Out01Ready [5] Safety Output 1 Ready
0 = Not Ready
1 = Ready
IMPORTANT Safety Output Monitor Value is not safety data and has no defined safe state.
Use Output Monitor Value for diagnostic purposes only.
The output monitor value of a safety output is the value of the output that is
read by module. It is expected that the output monitor value is the same as the
commanded safety output value in normal operation. The output monitor
value can be used to diagnose output alarms.
The output monitor value is provided in the safety input assembly, as shown in
Table 29. Table 30 describes the attributes for reading the output monitor
value via CIP messaging. The output monitor value is also provided in bits 6
and 7 of DPI device parameter P12 [Safety IO Values].
Table 29 - Safety Input Assembly Tags for Safety Output Monitor Value
Safety Input Assembly Tag Name Type/[bit] Description
(safety controller to S4 option)
module:SI.OutputStatus SINT A collection of safety output status, safety output
monitor values, and test output status
module:SI.Out00Monitor [0] Output Monitor Value of Safety Output 0
0 = OFF
1 = ON
module:SI.Out01Monitor [1] Output Monitor Value of Safety Output 1
0 = Not Ready
1 = Ready
The value of a safety and test outputs can be commanded by setting tags in the
safety output assembly. Table 31 shows the output command tags of the
module.
Table 31 - Safety Input Assembly Tags for Safety Output Ready
Safety Input Assembly Tag Name Type/[bit] Description
(safety controller to S4 option)
module:SO.SafetyIOCommands SINT A collection of safety status bits for commanding
IO values
module:SO.Out00Output [0] Commanded Safety Output 0 Value
0 = OFF
1 = ON
module:SO.Out01Output [1] Commanded Safety Output 1 Value
0 = OFF
1 = ON
When an error is detected, the associated safety output data is put into the safe
state and the Alarm Type attribute is set.
Configuration Error
Circuit Error
When a safety output is configured for use with test pulses, a circuit error
occurs when a pulse test fails. There are three types of circuit errors that can be
reported:
• Stuck Low
• Stuck High
• Cross Connection
A stuck low error occurs when the output is expected to be in the on state, but
the feedback indicates the output is in the off state.
A stuck high error occurs when a pulse test expects the output to be in the off
state but the output does not transition to the off state during the pulse test
interval.
A cross connection error occurs when a pulse test of one safety output causes
another safety output to change value. This usually indicates that two outputs
are shorted together.
If a circuit error occurs in a safety output, check the wiring of the safety outputs
for errors.
When the safety outputs are configured for dual channel mode, a dual channel
discrepancy error occurs when there is a mismatch in the commanded output
values of the dual channel outputs. Both outputs will report a Dual Channel
Discrepancy error.
When the safety outputs are configured for dual channel mode, and one of the
safety outputs experiences a circuit or configuration error, the other safety
output will report a Partner Channel error.
TIP The safety output data will still be placed in the safe state when a Partner
Channel error occurs.
To read an alarm type of safety output with DPI parameters, follow these steps.
1. Set device parameter P16 [Output Alarm Indx] to the integer value i +1,
where i is the number of the safety output
2. Read device parameter P17 [Output Alarm].
The safety input alarm type can also be read via CIP messaging. See Table 32
for the attributes that are required to read the alarm type.
Table 32 - MSG Configuration for Safety Output Alarm Type
Parameter Value Description
Service Code 0x0E Get attribute single
Class 0x3B Safety Discrete Output Point Object
Instance i+1 Where i is the number of the safety output
Data Type USINT Unsigned integer value
Attribute 0x6E Safety Output Alarm Type
110 0 = No Alarm
1 =Configuration
3 = Stuck Low
4 = Stuck High
5 = Partner Channel
8 = Dual Channel
9 = Cross Connection
If an alarm is detected, the safety outputs are switched to the safe state and
remain in the safe state. Follow this procedure to activate the safety output data
again.
TIP If the latch error time has expired, but the safety output is not yet
commanded to the safe state, the alarm will not be cleared. Once the safety
output is commanded to the safe state, the alarm will clear immediately.
Test Output The test outputs of the Integrated Safety Function module can be configured
in the following modes:
• Standard Output
• Test Output
• Power Supply Output
ATTENTION: Test Output points that are configured as Pulse Test or Power
Supply become active whenever you apply input power to the module. These
configured functions are independent of the I/O connections to the module.
ATTENTION: Do not use test outputs as safety outputs. Test outputs do not
function as safety outputs.
When a test output is configured for standard output mode, the test output
point operates as a general purpose output. The output can be commanded
through the safety output assembly. Table 33 shows the tags in the safety
output assembly to command test outputs when in standard output mode.
When in test output mode, the test output point operates in conjunction with
a safety input to perform pulse testing on the external safety input circuitry.
Please see the Safety Input with External Pulse Tests Operation section for
information on this mode. Commanding the output point via the safety output
assembly will have no effect in this mode.
Test Output Data The Test Output data of the Integrated Safety Functions module can be
monitored through:
• Safety Input Assembly
• DPI Parameters
• CIP Messaging
The following Test Output data is available in the Integrated Safety Functions
module:
• Test Output Status
• Test Output Ready
Each test output point reports its own status and ready attributes.
IMPORTANT Test Output data is not safety data and cannot be used for safety
applications.
The test output status indicates whether an alarm is present in the test output
point. When in standard output mode, the status will always be OK, unless
there is a critical fault, in that case, the status is forced to Alarm. In all other
modes test output status is set to Alarm.
The test output status is provided in the safety input assembly, as shown in
Table 34. Table 35 describes the attributes for reading the test output status via
CIP messaging. The test output status is also provided in bits 4 and 5 of device
parameter P13 [Safety IO Status].
Table 34 - Safety Input AssemblyTags for Test Output Status
Safety Input Assembly Tag Name Type/[bit] Description
(safety controller to S4 option)
module:SI.OutputStatus SINT A collection of safety output and test output data
module:SI.Test00Status [4] Status of Test Output 0
0 = Alarm
1 = OK
When set, the test output ready attribute indicates that the test output is
configured for standard output mode, and is ready to be commanded. In other
modes, the test output ready attribute is forced to the safe (alarm) state.
IMPORTANT The Test Output Ready attribute should be checked before commanding the
test output.
The test output ready attribute is provided in the safety input assembly, as
shown in Table 36. Table 37 describes the attributes for ready the test output
ready attribute via CIP messaging.
Table 36 - Safety Input Assembly Tags for Test Output Ready
Safety Input Assembly Tag Name Type/ Description
(safety controller to S4 option) [bit]
module:SI.IOSupport SINT A collection of bits describing safety IO functionality
module:SI.Test00Ready [6] Test Output 0 Ready
0 = Not Ready
1 = Ready
Notes:
Use this chapter to learn more about the Safe Torque Off, Timed Safe Stop 1,
Monitored Safe Stop 1, and Safe Brake Control stopping functions that are
built into the Integrated Safety Functions option module.
IMPORTANT The information in this section describes Safety Stop Functions operating in
the drive. For information on using the Drive Safety instructions operating in
the GLX controller, see Chapter 5.
Topic Page
Safety Output Assembly Safe Stop Function Tags 65
Safety Input Assembly Safe Stop Function Tags 66
Connection Action 68
Safe Torque Function 69
Safe Stop 1 Function 76
Connecting a Safety Brake 91
Safety Output Assembly Safe The safety output assembly for Integrated Safe Speed consists of 48 Logix tags:
Stop Function Tags • 35 tags for pass thru status and faults
• 8 tags for safety stop function commands
• 5 tags for safety I/O commands
Table 38 - Safety Output Assembly Tags for Safety Stop Functions
Safety Output Assembly Tag Name Type/[bit] Description
(safety controller to S4 option)
module:SO.SafetyStopFunctions SINT A collection of bits used to activate (request) safety
functions as described in this table.
module:SO.STOOutput [0] Control Safe Torque Off (STO):
0 = Disable Torque
1 = Enable Torque
module:SO.SBCOutput [1] If Safe Brake Control (SBC) is configured:
0 = Engage Brake (So0 and So1 OFF)
1 = Release Brake (So0 and So1 ON)
If Safe Brake Control is not configured, this tag must
be set to 0. If set to 1, will cause SBC fault.
Table 38 - Safety Output Assembly Tags for Safety Stop Functions (Continued)
Safety Output Assembly Tag Name Type/[bit] Description
(safety controller to S4 option)
module:SO.SS1Request [2] If Safe Stop 1 (SS1) is configured:
0 = No Request
1 = Request Safe Stop 1
If Safe Stop 1 is not configured, this tag must be set
to 0. If set to 1, will cause SS1 fault.
module:SO.SS2Request [3] Reserved for future use. This tag must be set to 0; will
cause SS2 fault if set to 1.
module:SO.SOSRequest [4] Reserved for future use. This tag must be set to 0; will
cause SOS fault if set to 1.
module:SO.SMTRequest [5] Reserved for future use. This tag must be set to 0; will
cause SMT fault if set to 1.
module:SO.ResetRequest [7] A 01 transition is required to reset Safety Faults. If
Restart Type is ‘Manual’, a 0 1 transition is
required to restart a Safety Stop Functions.
Safety Input Assembly Safe The safety input assembly for Integrated Safe Speed consists of 56 Logix tags:
Stop Function Tags • 3 tags for connection status
• 28 tags for safety feedback and stop function status
• 25 tags for safety I/O status
Table 39 - Safety Input Assembly Tags for Safety Stop Functions
Safety Input Assembly Tag Name Type/[bit] Description
(S4 option to safety controller)
module:SI.ConnectionStatus SINT A collection of the following bits.
module:SI.RunMode [0] Safety Connection
0= Idle
1 = Run
module:SI.ConnectionFaulted [1] Safety Connection
0=Normal
1= Faulted
module:SI.FeedbackPosition DINT Primary Feedback Position from drive-module safety
instance. Value is in encoder counts.
module:SI.FeedbackVelocity REAL Primary Feedback Velocity from drive-module safety
instance. Value is in Rev/s or Meter/s.
module:SI.SecondaryFeedbackPosition DINT Secondary Feedback Position from drive-module safety
instance. Value is in encoder counts.
Secondary channel may only be used for discrepancy
comparison with primary channel.
module:SI.SecondaryFeedbackVelocity REAL Secondary Feedback Velocity from drive-module safety
instance. Value is in Rev/s or Meter/s.
Secondary channel may only be used for discrepancy
comparison with primary channel.
module:SI.StopStatus SINT A collection of the following bits.
module:SI.STOActive [0] Safe Torque Off (STO) function status
0 = Permit Torque
1 = Disable Torque
IMPORTANT Review the CONNECTION_STATUS Data section of the GuardLogix 5580 and
Compact GuardLogix 5380 Controller Systems Safety Reference Manual,
publication 1756-RM012, for information on how to use the connection
status tags.
Safety Function in Response The module allows for a safety function to be executed when the safety
connection to the module is lost or the connection enters the idle state. This
to Connection Event operation is referred to as the connection action. There are two configurable
connection actions that are defined as follows:
• Connection Loss Action - The safety function to be executed if the
network connection from the module to the safety controller is lost or
closed.
• Connection Idle Action - The safety function to be executed if the safety
controller connected to the module enters program mode.
In both of theses cases, the safety function must be executed by the drive/
module. Therefore, only the drive-based safety functions may be used in these
cases.
When the connection loss event is detected, the following attributes will be set:
• In Standard Control Mode
– Host: P3 [Safety State] = Idle
– Host: P4 [Safety Status] Conn Closed = 1
In standard control mode, change the Comm Flt Action parameter of the
EtherNet/IP® module in the drive from its default value of ‘Fault’ to another
applicable setting in order for the drive to initiate the stopping action. In the
PowerFlex 755 drive, this is done using parameter 54. In the PowerFlex 755T
drive, this done using port 0 parameter 360. If this parameter is not changed,
the safety function that is triggered by the connection loss may fault.
When the connection idle event is detected, the following attributes will be set:
• In Standard Control Mode
– Host: P4 [Safety Status] Conn Idle = 1
In standard control mode, change P55 [Idle Flt Action] of the EtherNet/IP
port in the drive from its default value of ‘Fault’ to another applicable setting in
order for the drive to initiate the stopping action. If this parameter is not
changed, the safety function that is triggered by the connection loss may fault.
Safe Torque Off Function The Safe Torque Off (STO) function provides a method, with sufficiently low
probability of failure, to force the power-transistor control signals to a disabled
state. When the command to execute the STO function is received from the
GuardLogix controller, all drive output-power transistors are released from the
ON-state. This results in a condition where the drive is coasting.
Safe Torque Off (STO) will prevent the motor from applying torque to a
system but in some systems torque is also applied to the mechanical system by a
suspended load, unbalanced load, back pressure, and so on. In such a system,
application of a mechanical brake is required to hold the load while motor
torque is disabled by STO. See Safe Brake Control Function beginning on page
83 for information on using a mechanical brake with the Integrated Safety
Functions Module.
STO Activation
STO Output
STO Output
SS1 Complete
SS1 Complete
Safety Stop Fault
Safety Stop Fault
Safety Limit Fault Logical STO Active STO to Torque Disabled
Safety Limit Fault OR SBC Delay
Safety Limit Active
Safety Limit Active
Connection Loss (1) Connection Loss Negative Value: Delay = |Value|
Connection Idle (2) Positive Value: Delay = 0
Connection Idle Safety Fault: Delay = 0
After torque is disabled due to a STO activation, the STO function must be
reset in order to enable torque. When the STO function must be reset, the
following attribute values are set:
• module:SI.STOActive = 1
• module:SI.RestartRequired = 1
The steps to reset the STO function depend on the cause of STO activation
and the Restart/Cold Start Type configured in the module.
IMPORTANT When the STO function is activated by a Safety Fault, the cause of the safety
fault must be removed before STO can be reset, regardless of the configured
restart type.
If there are no Safety Faults and no safety demands, the STO function can be
reset.
If there are no Safety Faults and no safety demands present in the module, the
STO function can be reset by a 1→0 transition on the module:SO.STOOutput
tag then a 0→1 transition on module:SO.ResetRequest tag.
If Safe Brake Control is being used, the STO delay must be 0. If an STO delay
is desired with the use of the Safe Brake Control function, see Safe Brake
Control Function beginning on page 83 for information on configuring STO
to SBC delay. In the case of STO activation by a safety fault, any configured
delay is ignored, and torque is disabled instantly.
The operation of the STO function and its attributes is dependent on the
configuration of the STO function and the activation reason. For all STO
activations besides safety fault, the operation of STO is dependent on STO
Delay. For STO activations caused by a safety fault, the operation ignores STO
Delay. See the following sections for more information.
(1) Safety Output Assembly (2) Safe Stop Function Attribute (3) Safety Input Assembly
When the STO Delay is configured for a positive non-zero value, the delay is
inserted between STO Active and Torque Disabled. The STO Delay is meant
to serve as a delay between the configured STO drive stopping action and
when torque is disabled. The delay allows the drive to complete the stop before
torque is disabled. This is effectively a Timed Safe Stop 1 function. See Safe
Torque Off Stopping Action and Source on page 74 for information on
configuring a drive stop type in response to a STO activation.
Figure 21 shows the timing of STO status and torque attributes in response to
a STO activation, along with the restart type behavior, when STO Delay is
configured.
IMPORTANT The Safe Brake Control (SBC) Mode must be set to ‘Not Used’ to permit STO
Delay. If Mode is not set to ‘Not Used’, Delay is set to zero.
When a safety fault occurs in the module, the STO function is forced to the
Safe State, which is the Torque Disabled state. In this case, the configured STO
Delay value is bypassed and torque is immediately disabled. Figure 22 shows
the timing of STO and torque attributes in response to STO activation by a
Safety Fault.
Clearing a Safety Fault requires correcting the fault condition, then a 0→1
transition on Request Reset.
(1) Safety Output Assembly (2) Safe Stop Function Attribute (3) Safety Input Assembly
In response to an STO activation, the type of stop and the source responsible
for controlling the stop are configurable. These configuration attributes are
defined as:
• STO Stopping Action – Configures what stopping action to perform in
response to a STO activation.
• STO Stopping Action Source – Configures where the stopping action is
performed (drive-based or controller-based).
When STO is activated, the drive control will initiate the selected stop type if:
• The STO Action Source is configured as Drive or
• There is currently not a Standard I/O connection through the
Embedded EtherNet/IP port to the drive control or
• There is currently a Standard I/O connection through the Embedded
EtherNet/IP port to the drive control but it is in Idle mode (the
controller is in program mode)
Otherwise, the controller that owns the Standard I/O connection is expected
to respond when STO is activated. In this case, the configured STO Stopping
Action is ignored, and the stopping logic must be programmed in the
controller that owns the Standard I/O connection.
If the STO Stopping Action Source is Controller, or the STO Stopping Action
is configured for a non-default value, a STO Delay may need to be specified in
order for the Stopping Action to be completed before torque is disabled.
See the drive's reference manual for information on its supported stop modes.
IMPORTANT You are responsible for providing logic in the controller standard task to
implement a stop action when the STO Action Source is configured as
Controller.
IMPORTANT If STO Delay is zero, there is no time for the drive to complete a stop before
torque is disabled. In that case, the stop action is effectively ‘Coast’ (default).
When the module experiences a STO Fault, the module is placed in the safe
state and the cause of the fault is recorded. If the STO function detects a fault,
it will set the following attributes:
• module:SI.SafetyFault = 1
• module:SI.RestartRequired = 1
• STO Fault Type
For more information on STO Fault Types and troubleshooting methods, see
Understand Safety Faults on page 199.
Safe Stop 1 Function The Safe Stop 1 (SS1) function signals the configured SS1 Stop Action Source
to initiate a stopping action, then the safety module monitors the stop. When
the Safe Stop 1 is complete, STO is activated and torque is disabled. If the drive
does not complete the stop within the limits that are configured in the Safe
Stop 1 function, an SS1 Fault is annunciated.
When SS1 is activated, all sources of activation are stored in an attribute as a bit
mask and the attribute can then be read to determine the causes of an SS1
activation. Figure 23 shows the operation of the SS1 activation attribute. The
SS1 Activation attribute can be read with explicit messaging (see attribute 289
in Table 18 on page 247).
Unlike the STO function, SS1 does not get activated by a safety fault.
SS1 Activation
SS1 Request
SS1 Request
Safety Limit Active
Safety Limit Active Logical SS1 Active
Connection Loss (1) OR
Connection Loss
Connection Idle (2)
Connection Idle
After an SS1 action is complete, the SS1 function must be reset in order to
enable torque. When the STO Function needs to be reset, the following
attribute values are set:
• module:SI.SS1Active = 1
• module:SI.RestartRequired = 1
The steps to reset the SS1 function depend on the cause of SS1 activation and
the Restart/Cold Start Type configured in the module.
If there are no Safety Faults present in the module, the SS1 function can be
reset by a 1→0 transition on the module:SO.SS1Request tag.
If there are no Safety Faults in the module, the SS1 function can be reset by a
1→0 transition on the module:SO. SS1Request tag then a 0→1 transition on
module:SO.ResetRequest tag.
In response to an SS1 activation, the type of stop and the source responsible for
controlling the stop is configurable. These configuration attributes are defined
as:
• SS1 Stopping Action – Configures what stopping action to perform in
response to an SS1 Activation.
• SS1 Stopping Action Source – Configures where the stopping action is
performed (drive-based or controller-based).
When SS1 is activated the drive control will initiate the selected stop type if:
• The SS1 Action Source is configured as Drive
• There is currently not a Standard I/O connection through the
Embedded EtherNet/IP port to the drive control
• There is currently a Standard I/O connection through the Embedded
EtherNet/IP port to the drive control but it is in Idle mode (the
controller is in program mode)
Otherwise, the controller that owns the Standard I/O connection is expected
to respond when SS1 is activated. In this case, the configured SS1 Stopping
Action is ignored, and the stopping logic must be programmed in the
controller that owns the Standard I/O connection.
See the drive's reference manual for information on its supported stop modes.
IMPORTANT You are responsible for providing logic in the controller standard task to
implement a stop action when the SS1 action source is Controller.
A Timed Safe Stop 1 involves initiating motor deceleration and initiating the
STO function after the configured time delay.
When the module is configured for Timed Safe Stop 1 Mode, the Safe Stop 1
function is initiated by setting the module:SO.SS1Request safety output tag.
This sets the ‘SS1 Request’ bit in the SS1 Activation attribute and sets the
module:SI.SS1Active safety input tag. When the SS1 Active bit is set, the SS1
Stop Action will be executed by the source indicated by the SS1 Stop Action
Source. See Safe Stop 1 Stopping Action and Source for more information.
The SS1 function waits for the configured SS1 Max Stop Time, then sets the
SS1 Complete flag in the STO Activation attribute, which sets STO Active to
Disable Torque. In Timed Safe Stop 1 mode, speed and deceleration are not
monitored so this mode does not require Safety Feedback. Figure 24 shows the
SO.SS1Request(1)
SI.SS1Active(3) Active
When the module is configured for Monitored Safe Stop 1 Mode, the Safe
Stop 1 function is initiated by setting the module:SO.SS1Request safety output
tag. This sets the ‘SS1 Request’ bit in the SS1 Activation attribute, and also sets
the module:SI.SS1Active safety input tag. When the SS1 Active bit is set, the
SS1 Stop Action will be executed by the configured SS1 Stop Action Source.
See Safe Stop 1 Stopping Action and Source for more information.
After the SS1 Active bit is set, the configured SS1 Decel Monitor Delay timer
begins. After the configured Decel Monitor Delay expires, an internal speed
ramp value is computed every time that the encoder is sampled. If the
magnitude of module:SI.FeedbackVelocity exceeds the sum of the internal
ramp plus Decel Speed Tolerance, the SS1 Fault Type attribute is set to
‘Deceleration Rate’ and the SS1 Fault attribute is set to Faulted.
Figure 25 describes the equations that are used for computing the deceleration
reference rate and tolerance.
TIP A Configured Decel Reference Rate of 0 disables the ramp check. SS1 will
fault if the drive does not slow to less than the Standstill Speed.
to SBC Delay is negative (and STO Activates SBC = Linked), then the Torque
Disabled attribute is set after the configured time delay. Otherwise, the Torque
Disabled attribute is set immediately.
Figure 27 shows the timing of the Monitored SS1 operation, along with the
restart type behavior.
Standstill Speed
TIP Speed units are configured by the ‘Position Units’ and ‘Time Units’ AOP
Controls on the Scaling page.
TIP A Configured Decel Reference Rate of 0 disables the ramp check. SS1 will
fault if the drive does not slow to less than the Standstill Speed within Max
Stop Time.
When an SS1 Safety Fault occurs, the STO function is activated immediately
and torque is disabled. Figure 27 describes the timing of attributes when an SS1
fault occurs during SS1 execution. Figure 28 describes the operation of SS1
when an SS1 fault is detected.
The ‘Safe State’ of the SS1 function is the Torque Disabled state. If the SS1
function detects a fault, it will set:
• module:SI.SafetyFault = 1
• module:SI.RestartRequired = 1
• SS1 Fault Type
Clearing a Safety Fault requires correcting the fault condition and a 0→1
transition on Request Reset. For more information on SS1 Safety Faults, see
Understand Safety Faults on page 199.
Fault Occurs
(Feedback Velocity > Expected Velocity)
Coast to S
top
Standstill Speed
Safe Brake Control Function The Safe Brake Control function (SBC) function utilizes the module’s safety
outputs to control an electromechanical brake that is attached to the motor.
The SBC function releases the brake to allow motion or engages the brake to
prevent motion.
SBC Activation
SBC Output
SBC Output
(1)
STO Active
STO Active SBC Active STO to Brake Engaged
Logical
Safety Stop Fault OR SBC Delay
Safety Stop Fault
Safety Limit Fault
Safety Limit Fault Positive Value: Delay = |Value|
Negative Value: Delay = 0
(1) STO Activates SBC = Linked Safety Fault: Delay = 0
If the SBC Activation bit mask indicates that only STO Active is the source of
activation, then the STO to SBC Delay is executed. If the activation is not by
STO Active, or other activation bits are also set, the STO to SBC Delay is not
executed and the brake is immediately engaged.
After the brake is engaged due to an SBC activation, the SBC function must be
reset in order to release the brake. When the SBC function must be reset, the
following attribute values are set:
• module:SI.SBCActive = 1
• module:SI.RestartRequired = 1
The steps to reset the SBC function depend on the cause of SBC activation
and the Restart/Cold Start Type configured in the module.
IMPORTANT When the SBC function is activated by a Safety Fault, the cause of the safety
fault must be removed before the SBC function can be reset, regardless of
the configured restart type.
If there are no Safety Faults in the module, the STO function can be reset by a
0→1 transition on the module:SO.SBCOutput tag.
If Restart Type is set to ‘Manual’ and there are no Safety Faults in the module,
the SBC function can be reset by a 0→1 transition on the
module:SO.SBCOutput tag, then a 0→1 transition on
module:SO.ResetRequest tag.
SBC Mode specifies if the SBC functionality is used and how the safety
outputs controlling the brake operate. The mode also changes the instances of
the CIP objects controlling the safety outputs. The following modes are
supported by the module.
Not Used
In ‘Not Used’ mode, the SBC function will not be used by the application. The
associated safety outputs are not under SBC control, and can be configured
independently. The safety outputs are mapped to the following CIP objects:
• So0: Safety Discrete Output Point Object Instance 1
• So1: Safety Discrete Output Point Object Instance 2
• Safety Dual Channel Output Object Instance 1
In ‘Used, No Test Pulses’ mode, the associated safety outputs are not pulse
tested. The associated safety outputs are under SBC control and cannot be
configured independently. The safety outputs are mapped to the following CIP
objects:
• So0: Safety Discrete Output Point Object Instance 3
In ‘Used, Test Pulses’ mode, the associated safety outputs are tested with a
500 µs pulse every 300 ms when the brake is in the released state (outputs
energized). Pulse tests of So0 and So1 outputs are shifted in time, allowing So0
to So1 shorts to be detected. There is no difference in implementation of
Safety Outputs pulse testing in SBC control versus direct control.
In the ‘Used, Test Pluses’ mode, the safety outputs are under SBC control and
cannot be configured independently. The safety outputs are mapped to the
same CIP objects as the ‘Used, No Test Pulses’ mode.
For more information on the pulse testing that is performed by the SBC
function, see Latch Output Error Operation in Single Channel Mode on
page 52.
IMPORTANT If the Safe Brake Mode is set to ‘Not Used’, then setting the Safety Output tag
module:SO.SBCOutput = 1 sets the SBC Fault and sets the SBC Fault Type to
‘Config’.
IMPORTANT If the Safe Brake Mode is set to ‘Not Used’, then the state of the two safety
outputs So0 and So1 are controlled by Safety Output Assembly tags;
otherwise, the two Safety Outputs are controlled by the Safe Brake Function.
IMPORTANT If the Safe Brake Mode is set to ‘Used’, then the Safety Input Assembly tags
associated with safety outputs will be forced to:
module:SI.Out00Monitor = 0
module:SI.Out01Monitor = 0
module:SI.Out00Status = 0
module:SI.Out01Status = 0
module:SI.Out00Ready = 0
module:SI.Out01Ready = 0
Safe Brake Control (SBC) operation can be activated by the safety output
assembly or by STO.
If the SBC function is configured to link STO and SBC activation, any STO
activation will cause the SBC function to be activated as well. The brake is
engaged (deenergized) by the SBC function when torque is disabled by the
STO function.
(1) Safety Output Assembly (3) Safety Input Assembly (5) Safety Output Assembly
(2) Safe Stop Function Attribute (4) 24V DC Safety Output
to the safe state changes. The ‘Safe State’ of the SBC function is the ‘Brake
Engaged’ state.
When a safety fault is detected in the module (and the SBC function is
configured to not be linked to STO activation), the SBC function will be
activated with the SBC activation reason being ‘Safety Stop Fault’. The SBC
function can be reset once the safety fault is cleared. Figure 33 shows the
timing of SBC and torque attributes in response to a safety fault in this
scenario.
Figure 33 - SBC Operation Under Safety Fault Condition (not linked to STO)
SI.SBCActive(3)
(1) Safety Output Assembly (2) Safe Stop Function Attribute (5) Safety Input Assembly
When a safety fault is detected in the module and the SBC function is
configured to link STO and SBC activation, the SBC function will be
activated with the SBC activation reason being ‘STO Active’ and ‘Safety Stop
Fault’. The SBC and STO function can be reset once the safety fault is cleared.
Figure 34 and Figure 35 show the operation of the SBC function under a safety
fault condition when linked to STO.
Figure 34 - SBC Operation under Safety Fault Condition (linked to STO with positive delay)
Figure 35 - SBC Operation under Safety Fault Condition (linked to STO with negative delay)
When the module experiences an SBC Fault, the module is placed in the safe
state and the cause of the fault is recorded.
For more information on SBC fault types and troubleshooting methods, see
the Understand Safety Faults chapter beginning on page 199.
Connecting a Safety Brake The safety brake control function uses the safety outputs So0 and So1 to
control a safety brake.
The safety brake function interfaces to the safety brake through the two safety
outputs So0 and So1. So0 and So1 are 24V DC, 1 A sourcing outputs.
Figure 36 shows a wiring example for connecting a brake to the module.
Usually the voltage and current rating of the safety brake is much higher than
the 24V DC and 1 A that the safety outputs can directly control. To support
brakes with that require higher voltage and higher current, an interposing
safety relay such as the 700S-CF Safety Control Relay is required.
Safety brakes typically require a voltage suppression device. Most safety brakes
provide a suppression device as an option or they specify a diode or MOV to
use. Use the recommended suppression devices.
Topic Page
Drive Safety Instructions 93
Pass-through Data Using Standard I/O Mode 96
Pass-through Data Using Integrated Motion 98
SFX Instruction 99
Drive Safety Instructions The Drive Safety instructions (see Table 40 on page 94) are designed to work
with the 20-750-S4 option module. They are available in the Studio 5000
Logix Designer® application, version 31.00 or later, in the Drive Safety
instruction element group that is enabled when the Safety Program -
MainRoutine is open (see Figure 37 on page 94 ).
Before adding drive safety instructions to your Logix Designer application, you
must have PowerFlex 755/755T drive products with 20-750-S4 options
installed in your project.
Outputs
Configurable
Inputs
Inputs
Pass Through
Outputs
Pass-through Data Using The Drive Safety instructions provide safety function monitoring in the safety
task of a controller. Control of the drive is done in the main program within
Standard I/O Mode the standard (main) task of a controller. For the main program to receive safety
status information from the Drive Safety instruction, tag data in the safety
output assembly for the drive module (safety task) is passed to the drive and
then data linked to tags in the main task.
This is especially useful when the user's program is in a separate controller from
the safety program that is in a safety controller. Figure 39 shows how this works
for the SLS instruction.
IMPORTANT Pass-through data is for status information only and does not impact
configured safety functions.
SLS Active status and safety faults are passed to the standard task via user-
configured datalinks (inputs) to the following host config parameters in the
Integrated Safety Functions option module:
• P4 [Safety Status]
• P5 [Safety Faults]
TIP Other safety parameters may also need to be data linked depending on your
application.
TIP The words module and drive (italic) in these tag names represent the
module and drive name that is assigned in the Logix Designer application.
Pass-through Data Using The Drive Safety instructions provide safety function monitoring in the safety
task of the controller. Control of the drive is done in the motion programming
Integrated Motion within the standard task of the controller. For the main program to receive
status information from the Drive Safety instruction, tag data in the output
assembly for the drive module (safety task) are passed to the drive and then to
the corresponding tag in the axis structure (standard task).
IMPORTANT Pass-through data is for status information only and does not impact
configured safety functions.
TIP The words module and axis (italic) in these tag names represent the module
and axis name that is assigned in the Logix Designer application.
SFX Instruction The Safety Feedback Interface (SFX) instruction scales feedback position into
position units and feedback velocity into speed units per unit of time.
Feedback position and velocity are read from the safety input assembly and
become inputs to the instruction. The SFX instruction also sets a reference
position from a home input and performs position unwind in rotary
applications. Typically, one SFX instruction is used per safety drive. This
instruction provides the position and velocity feedback that is used by other
safety instructions, also used by the same safety drive.
The PowerFlex 755/755T drive provides safe position and velocity feedback.
Up to SIL 3 PLe safety rating can be achieved by using dual feedback with
velocity and/or position discrepancy checking.
The outputs of the SFX instruction are used as inputs to other Drive safety
instructions. For any drive with an Integrated Safety Functions option module
to execute a controller-based safety function, an SFX instruction is required.
Although the SFX instruction is a safety instruction, it alone does not perform
a safety function.
In Figure 41, the SS1 instruction uses the Actual Speed output from the SFX
instruction during execution of the SS1 safety function.
In this SFX example, an encoder has 512 feedback counts per motor revolution
and is scaled for position to have 512 counts per motor revolution.
The SFX instruction scales the applicable safety instructions with feedback
position units from the safety encoder/motor, into position feedback units
used in applicable safety instructions. It also scales feedback velocity units from
the safety encoder/motor into position feedback units per time unit.
Scaling Setup
When configuring the SFX instruction, calculate the value for ‘Position
Scaling’ so that the ‘Actual Position’ and ‘Actual Speed’ output from the
instruction matches the ‘Actual Position’ and ‘Actual Velocity’ in the motion
controller.
The Feedback Resolution is determined based on the feedback device and the
Effective Resolution of the feedback. This information is configured on the
‘Module Properties>Motion Safety>Primary Feedback’ category.
In this example, the motor is used in a rotary application where the unwind is
set to roll over each motor revolution. Therefore, the unwind of ‘512 Counts/
Rev’ was added in the SFX instruction appropriately.
Figure 43 - Scaling
Homing
Setting the ‘Actual Position’ output to the ‘Home Position input’ (homing) of
the instruction is required if using a position-based drive safety instruction like
The data in the Primary Feedback category, Scaling category, and motor
unwind value is used to populate the SFX instruction.
Topic Page
Safety Assembly Tags 103
Configure Safety in the Logix Designer Application 104
Programming 126
Safety Function Operation 128
Pass-through Data 129
Safety Assembly Tags Using network safety, a GuardLogix® 5580 or Compact GuardLogix 5380
safety controller controls the PowerFlex® 755/755T Safe Torque Off function
through the SO.SafeTorqueOff tag in the safety output assembly.
The SO.SafetyStopFunctions tags are sent from the GuardLogix safety output
assembly to the PowerFlex 755 safety output assembly to control the safety
functions.
The SI.StopStatus tags are sent from the PowerFlex 755 to the GuardLogix
safety input assembly and indicate the PowerFlex 755 safety control status.
The SI.OutputStatus, SI.InputStatus, and SI.IOSupport tags are sent from the
PowerFlex 755/755T drive product to the GuardLogix safety input assembly
and indicate the status of the safety inputs, safety outputs, and test outputs.
Configure Safety in the Logix This section provides instructions for how to add and configure an Integrated
Safety Functions option module in a PowerFlex 755/ 755T drive product to an
Designer Application existing project in the Logix Designer application. This chapter is specific to
safety and does not cover all aspects of drive configuration. The PowerFlex 755
drive is used for the examples in this chapter.
Before you can configure your option module in the Logix Designer
application:
• You must have a safety controller project with an EtherNet/IP® network
connection configured. See the documentation for your controller,
drive, and Ethernet adapter for information on configuring those
products (see Additional Resources on page 13).
1. In the Device Definition dialog box, enter the connection type that you
want to use. Select from one of the following types. The ‘Standard and
Safety’ connection is used in this example.
Connection Type Description Requires Controller Firmware Revision
Standard Control is managed by this controller. V31 or later
Safety is managed by another controller.
Standard and Safety Both control and network safety V31.012 or later
connections are managed by this
controller. A Standard and Safety
connection can only be made from a
GuardLogix 5580 or Compact GuardLogix
5380 controller.
Safety Only Network safety connection is managed by V31 or later
this controller. Control is managed by
another controller. A Safety connection can
only be made from a GuardLogix 5580 or
Compact GuardLogix 5380 controller.
4. Scroll down and enter additional Device Definition data for the drive
product being used.
IMPORTANT If you assign an SNN manually, make sure that the system expansion does
not result in duplication of SNN and node address combinations.
A warning appears if your project contains duplicate SNN and node address
combinations. You can still verify the project, but Rockwell Automation
recommends that you resolve the duplicate combinations.
Electronic Keying
The electronic keying options are for the standard connection to the drive.
Electronic Keying
Indicates that all keying attributes must match to establish communication. If any attribute
Exact Match does not match precisely, communication with the device does not occur.
Lets the installed device accept the key of the device that is defined in the project when the
installed device can emulate the defined device. With Compatible Module, you can typically
replace a device with another device that has the following characteristics:
• Same catalog number
Compatible Module
• Same or higher Major Revision
• Minor Revision as follows:
– If the Major Revision is the same, the Minor Revision must be the same or higher.
– If the Major Revision is higher, the Minor Revision can be any number.
Indicates that the keying attributes are not considered when attempting to communicate
with a device. With Disable Keying, communication can occur with a device other than the
type specified in the project.
5. Click Peripherals in the navigation tree and click the arrow in the top
left corner to expand the Network SSM *S4 section. The port location
can be changed if needed (uses ports 4, 5 or 6). The electronic keying
options that are specified here are for the safety connection with the
safety controller. ‘Exact Match’ or ‘Compatible Module’ must be used.
6. Click the Add new peripheral pull-down menu to add any additional
peripherals, such as feedback devices to use with the safety option
module.
The Input and Output tabs are for setting the datalinks between the
drive and the controller that is performing control. Add P4 [Safety
Status] and P5 [Safety Faults] to provide pass-thru data from the safety
task/safety controller to the main task/standard controller. Enter
additional datalinks as desired for your application.
The Safety Output and Safety Input tabs show the fixed safety data
between the drive and safety controller.
8. If Automatic Device Configuration (ADC) will be used, click
Automatic Device Configuration in the navigation tree to open the
Automatic Device Configuration page. The 20-750-S4 option module
has Host configuration parameters that can be set using the ADC
process.
TIP You can click the Device Definition button from the Overview page to reopen
the Device Definition dialog box and make edits to the previous steps.
10. Click Create to create the drive and have it added to the I/O
Configuration folder. Save the project to save any edits and double-click
the drive in the I/O Configuration folder to reopen the drive properties
window.
11. Click Connection in the navigation tree to open the Connection page.
The safety output connection, safety input connection, and standard
connection configuration information is shown on this page. The
Requested Packet Interval (RPI) and Connection Reaction Time
Limit can be set according to the application.
The RPI for the Safety Output connection is fixed based on the period
of the safety task in the controller.
The Connection Reaction Time Limit sets the maximum age of safety
packets on the associated connection. If the age of the data that is used
Reset Ownership resets the ownership of the safety module. If the reset
ownership is confirmed, the module enters its out-of-box state
14. Click STO under Safety Configuration in the navigation tree to open
the STO page. The Delay value is the time delay between the STO
Active condition and Safe Torque Disabled. This allows the drive to
bring the motor to a controlled stop before disabling torque.
15. Click SS1 under Safety Configuration in the navigation tree to open
the SS1 page. Use the settings to configure the drive-based Safe Stop 1
(SS1) function, which decelerates the motor and then initiates a Safe
Torque Off (STO) in the drive.
Property Description
Specifies the mode of the SS1 function. The Mode selection determines which
parameters on the tab are available to configure. The available options are:
• Not Used
• Timed SS1
Mode • Monitored SS1
TIP Monitored SS1 is unavailable when Safety Instance 1 on
the Identity page is set to ‘Safe Stop, No Feedback’.
The delay time before deceleration is monitored. Valid values are 0...65535.
Stop Monitor Delay
This option is not available when ‘Mode’ is ‘Timed SS1’.
Stop Delay The stop delay time used when the SS1 function is initiated by a stop type condition.
Displays the SS1 maximum stop time. This value is the sum of ‘Stop Delay ‘and ‘Stop
Max Stop Time Monitor Delay’.
Specifies the deceleration speed to monitor for SS1.
Decel Reference Speed
This parameter is unavailable when ‘Mode’ is ‘Timed SS1’.
The minimum rate of deceleration while stopping.
TIP Changing the Stop Delay value recalculates the Decel
Decel Reference Rate
Reference Rate.
This parameter is unavailable when ‘Mode’ is ‘Timed SS1’.
Decel Speed Tolerance The speed tolerance that is applied to the deceleration ramp check.
Standstill Speed The speed limit that is used to declare motion as stopped.
Property Description
The physical input points available for configuration (terminals Si0, Si1, Si2,
Point and Si3).
Specifies the type of operation for the input. Available options are:
• Single Channel
Point Operation - Type • Dual Channel Equivalent
• Dual Channel Complementary
The time in milliseconds that a discrepancy must exist before a discrepancy
alarm is raised. Valid values are 0...65535.
Point Operation - Discrepancy Time
This property is unavailable when ‘Point Operation - Type’ is set to ‘Single
Channel’.
Specifies the mode of the input. Available options are:
• Not Used
• Safety Pulse Test- The associated test output point shown in the ‘Test
Source’ field will be used to pulse test the external wiring of the safety
input.
Point Mode • Safety Semiconductor Input - The time in milliseconds that a discrepancy
must exist between two corresponding safety inputs before an alarm is
generated.
• Safety Standard Input - The safety input will be treated as a standard
input. No diagnostics are run. When using a safety input as a standard
input, the ‘Point Operation Type’must be set to ‘Single Channel’.
Specifies the Test Output associated with the input. This property is only
Test Source available when ‘Point Mode’ is set to ‘Used with Test Output’.
Input Delay Time (ms) Specifies the filter time in milliseconds for off to on transition of the input.
Off On Valid values are 0...65535.
Input Delay Time (ms) Specifies the filter time in milliseconds for on to off transition of the input.
On Off Valid values are 0...65535.
Specifies the amount of time in milliseconds an Input error will be latched. If
Input Error Latch Time the error is no longer present after this time, the error condition can be reset.
Property Description
Point The physical output points available for configuration (terminals So0 and So1).
Specifies the type of operation for the output. Available options are:
Point Operation - Type • Single Channel
• Dual Channel
Specifies the mode of the output. Available options are:
• Not Used
Point Mode • Safety
• Safety Pulse Test
Specifies the amount of time in milliseconds an Output error will be latched. If the
Output Error Latch Time error is no longer present after this time, the error condition can be reset.
18. Click Test Output under Safety Configuration in the navigation tree
to open the Actions page. If the test outputs on the 20-750-S4 option
module will be used, configure the test output points to match the
application.
Property Description
Point The physical test output point being configured (Terminals To1 and To0).
Specifies the mode of the test output. Available options are:
• Not Used - test point is not used
Point Mode • Standard Output - used as a standard safety output
• Pulse Test Output - used to test a safety input for short circuit detection
• Power Supply Output - used as a 24V DC power supply for an external input circuit
19. Click SBC under Safety Configuration in the navigation tree to open
the Actions page. If the drive-based Safe Brake Control on the
20-750-S4 option module will be used, configure SBC to match the
application.
Property Description
Specifies the mode of the SBC function. Available options are:
• Not Used
Mode • Safety
• Safety Pulse Test
Identifies if Safe Torque Off (STO) activation triggers the SBC function. Available options
are:
STO Activates SBC • Unselected
• Selected - the brake is engaged during an STO event, based on the ‘STO to SBC Delay’
attribute. Only valid when ‘Mode’ is set to ‘Safety’ or ‘Safety Pulse Test’.
Specifies the time in milliseconds from when the Safe Torque Off function is active to when
STO to SBC Delay (ms) the brake is engaged. For positive values, the brake will engage after the delay has expired.
For negative values, the brake will engage immediately and torque will be disabled after
the delay has expired.
20. Enter the information for the device that is being used for the primary
feedback. Red boxes indicate items that need to be updated if the feature
is used in your application. The properties available on this page are
determined by the safety feedback device selected when the drive
module was created.
21. Enter scaling information to configure the feedback position and time in
terms of counts per position unit in the safe monitoring functions.
22. Enter the information for the device being used for the secondary
feedback. Red boxes indicate items that need to be updated if the feature
is used in your application. The properties available on this page are
determined by the safety feedback device selected when the drive
module was created.
24. Configure the rest of the drive as needed for the application:
• Parameters – Parameters for all ports in the drive.
• DeviceLogix™ – DeviceLogix program editor.
• Wizards – Simplified startup and application configuration.
25. Click OK. The drive will be displayed in the ‘I/O Configuration’ folder
in the Logix Designer application.
4. After selecting Synchronize, select the check box for Use Physical. This
will match the project’s configuration to the physical configuration of
the drive.
TIP If you have already configured parameters offline, you can select the Use
Project check box associated with the Parameters Category so that your
parameters will not be overwritten during the synchronization. Selecting
Use Project sets the parameters in the drive to match the parameter
configuration of the offline project.
5. Select Continue.
6. After the synchronization is completed, verify that the 20-750-ENETR
option module appears as EtherNet/IP *ENETR (TAP), indicating that
the option module is in tap mode.
The connection between the controller and the drive is based on the following
criteria:
• Drive catalog number must be for PowerFlex 755 drives
• Drive Safety Network Number (SNN) (displayed in drive module
General tab)
• GuardLogix slot number
• GuardLogix safety network number
• Path from the GuardLogix 5580 safety controller or Compact
GuardLogix 5380 safety controller to the PowerFlex 755 drive
• Configuration signature (displayed on the Safety tab of the drive
Module Properties dialog box)
If any differences are detected, the safety connection between the safety
controller and the drive is not established (for a new drive/system) or lost (for
an existing drive/system). A yellow icon appears next to the drive in the
controller project tree to indicate a lost or unestablished connection.
Configuration Ownership has to be reset to establish a new connection or to
reestablish an existing connection.
Reset Ownership
To reset ownership, see Restore the Drive to Out-of-Box State on page 214.
Program-scoped safety tags are accessible only by local safety routines. These
routines reside within the safety program.
The PowerFlex 755/755T drive products, with the Integrated Safety Function
option module, provides integrated safety functions. Safety functionality
operates independently of the inverters and feedback that is used for motion.
The Integrated Safety Function option module receives encoder safety
feedback from the feedback option module for use with the integrated safety
functions. The safety feedback is supplied to the controller safety task over the
safety connection for use with controller-based safety functions that may
operate in the controller.
Safety Function Operation The following example describes how a standard and safety control system
operates and how main and safety tasks are coordinated. In typical standard
and safety system applications, an E-stop switch is used to stop the system. In
the example, the switch is used to initiate the process that brings the drive to a
controlled stop before removing power. This type of stop is called Stop
Category 1.
The main task and drive inverter are responsible for bringing the motor to a
Category 1 stop. At the same time, to make sure that the Stop Category 1 is
correctly executed by the control system, the safety task initiates a Monitored
SS1 safety function. The SS1 safety function can be configured to use the
drive-based SS1 function or it can be configured to use the controller-based
SS1 function.
This sequence of events represents the steps required for a Monitored SS1
drive-based safety function.
1. The safety task reads the E-stop input and detects the switch actuation.
2. The safety task communicates an SS1 request by setting the bit:
module:SO.SS1Request tag of the drive. This bit is also present in P4
[Safety Status], which is data linked with the standard controller via the
standard connection.
3. The request is available to the standard controller main task via the
module:I.P4_SafetyStatus_SS1Active tag.
Sa
nio
fet
ink ct
y
tal ne
Co
Da Con
nn
ect
ng rd
usi anda
i on
St
4. The main task controls the drive to bring the motor to a stop within the
Monitored SS1 limits for speed and time.
5. While the drive is stopping, the SS1 function (in the motion-safety
instance) monitors the motor speed to make sure it remains below the
speed limit and maximum stopping time.
6. When the drive reaches standstill speed, the 20-750-S4 activates the Safe
Torque Off function.
This sequence of events represents the steps that are required for a Monitored
SS1 controller-based safety function.
1. The safety task reads the E-stop input and detects the switch actuation.
2. The safety task activates the SS1 safety instruction running in the safety
task.
3. The SS1 instruction communicates an SS1 active by setting the bit:
module:SO.SS1Active tag of the drive (inverter) motion-safety instance.
4. The motion-safety instance in the drive communicates to the drive
motion core of the Axis Safety Status.
5. The motion core communicates with the motion controller running the
motion task by updating the motion axis tag axis.SS1ActiveStatus.
6. The motion task controls the axis to bring the motor to a stop within the
Monitored SS1 limits for speed and time.
7. While all events are occurring, the motion-safety instance updates the
Feedback Velocity tag, module:S1.FeedbackVelocity, in the safety
controller. The SS1 function running in the safety task receives the
speed scaled by the SFX safety instruction and makes sure that the axis
remains below the speed limit and maximum stopping time.
8. When the axis reaches standstill speed the SS1 safety instruction outputs
SS1 complete.
The safety task communicates to the drive motion safety instance to activate
STO by clearing the bit: module:SO.STOOutput tag of the drive.
Pass-through Data Some of the safety data (parameters) in the 20-750-S4 module must be
communicated with the standard controller. The safety controller only
requests safety functions and monitors. If, for example, a controller-based
safety function is to be performed (such as SLS), this request and the status /
fault data that is associated with it must be passed on to the standard controller.
This data comes from 20-750-S4 parameters that are data linked to the
standard controller where the associated tags are used by the main program.
This data is referred to as pass-through data.
ISO 13849-1 stipulates that instruction reset functions must occur on falling
edge signals. To comply with this requirement, a One Shot Falling (OSF)
instruction is used on the reset rung. Then, the OSF instruction Output Bit tag
is used as the reset bit for the STO output or enable rungs.
Understand Integrated GuardLogix controllers retain I/O device configuration onboard and are able
to download the configuration to the replacement device.
Safety Drive Replacement
IMPORTANT If the replacement card/module was used before, clear the existing
configuration before installing the card/module on a safety network by
resetting the card/module to the out-of-box state. See Out-of-Box State
on page 214 for more information.
When the Logix Designer application is online, the Safety tab of the Module
Properties dialog box displays the current configuration ownership. When the
opened project owns the configuration, Local is displayed.
When you replace an integrated safety drive, the replacement device must be
configured properly and the replacement drives operation be user-verified.
Two options for safety drive replacement are available on the Safety tab of the
Controller Properties dialog box in the Logix Designer application:
If the safety task has a safety task signature, the GuardLogix controller
automatically configures the replacement CIP Safety I/O device only if the
following is true:
• The device already has the correct safety network number.
• The device electronic keying is correct.
• The node or IP address is correct.
For detailed information, see the GuardLogix 5580 Controllers User Manual,
publication 1756-UM543 or Compact GuardLogix 5380 Controllers User
Manual, publication 5069-UM001.
Configure Always
PowerFlex 755 IO Mode Using In this example, a PowerFlex 755 drive (equipped with embedded Ethernet)
controls an induction motor with a 1024 PPR incremental encoder. A Dual
SFX, SS1, and SLS Instructions Incremental Encoder option module (catalog number 20-750-DENC-1) and an
Integrated Safety Function option module (catalog number 20-750-S4) are used
to interface to a GuardLogix 5580 safety controller (catalog number 1756-
L84ES).
This example shows the programming and configuration required for three of
the most common safe monitoring functions:
• Safe Feedback (SFX safety instruction)
• Safe Stop 1 (SS1 safety instruction)
• Safe Limited Speed (SLS safety instruction)
A Guard Locking Switch (catalog number TLS-Z GD2) is mapped to one of the
S4 Safety Outputs. This switch can be opened when the Safe Stop 1 is complete
and when the Safe Limited Speed is below the required speed for an operator to
access the machine function.
The Safety Reset and Home Request functions are programmed with the other
two S4 Safety inputs. These do not need to be safety-rated devices. For the
purpose of this example, other inputs and outputs are toggled for simplicity. At
any time, you can implement additional safety or IO devices as required based on
the machine risk assessment.
Studio 5000 Connection is set to ‘Standard and Safety’ since the GuardLogix
controller will provide both in this example.
• Inputs 0 and 1 are used with an OSSD Estop input from the 800FP.
• Input 2 is a standard digital input from a push button to safety reset the
S4 module.
• Input 3 is a standard digital input from a push button to set the SFX
home.
• Output 1 is used with the guard locking switch TLS-Z GD2 to open the
gate door.
Programming Example
This example illustrates configuration of the safety input, logic, and output
routines.
TIP Configure your system based on the required safety level devices and ratings.
Safety Input
The DCS Instruction is responsible for evaluating the dual-input validity into
the GuardLogix safety controller.
Safety Logic
The Safety Logic is used to configure when a safety reset occurs, the home
trigger, and the execution of the SFX instruction (which must have primary
feedback valid for it to execute properly).
Both the Safe Stop 1 and Safe Limited Speed use the SFX instruction for
correct monitoring of feedbacks. The Safe Stop 1 requests when the 800FP
inputs are removed. The Safe Limited Speed requests, in this example, with the
toggling of the Examine On tag.
Safety Output
The Safe Torque Off output must be true in order for any of the preceding safe
monitoring functions (namely SFX, SS1, and SLS) to function.
The PowerFlex 755 S4 safety actions can be configured based on the required
reaction to various machine requirements. In this instance, the STO request is
executed by the PowerFlex 755 in causing a disable and coast reaction.
However, the request to the SS1 (requested by the GuardLogix Safety Task) is
executed by the GuardLogix Standard Task with the use of pass-through tags.
In this case, the Stop command is used to control stop the motor, as shown by
the programming example.
The Safe Limited Speed (and any other safe monitoring instruction requests
besides STO, SS1, and SS2) are handled with the use of pass-through tags in
the GuardLogix Standard Task. The GuardLogix Safety Task uses pass-
through tags to the Standard I/O Routine to change the speed reference for the
SLS request, as shown in the programming example.
Figure 57 - The Use of Datalink is Required to Pass Data from the S4 Safety Function to the
Standard I/O Routine
Figure 58 - Standard I/O Routine That Starts and Stops the PowerFlex 755
Figure 59 - Standard I/O Routine That Runs the Drive at Velocity and Changes to Safe Limited
Speed Velocity When Requested by the Safety Task
Figure 60 - Standard I/O Routine That Commands the Drive to Zero Velocity Once the SS1
Request is Made by the Safety Task
Figure 61 - Standard I/O Routine That Monitors When at Zero Speed and Stops the Drive
Topic Page
Safety Assembly Tags 143
Configure the Integrated Safety Function Option Module in the Logix Designer Application 144
Understand Module Properties Categories 145
Programming 176
Safety Assembly Tags Using network safety, a GuardLogix® 5580 or Compact GuardLogix 5380
safety controller controls the PowerFlex® 755 Safe Torque Off function
through the SO.SafeTorqueOff tag in the safety output assembly.
The SO.SafetyStopFunctions tags are sent from the GuardLogix safety output
assembly to the PowerFlex 755 safety output assembly to control the safety
functions.
The SI.StopStatus tags are sent from the PowerFlex 755 to the GuardLogix
safety input assembly and indicate the PowerFlex 755 safety control status.
The SI.OutputStatus, SI.InputStatus, and SI.IOSupport tags are sent from the
PowerFlex 755/755T drive product to the GuardLogix safety input assembly
and indicate the status of the safety inputs, safety outputs, and test outputs.
Configure the Integrated This section provides instructions for how to add and configure an Integrated
Safety Functions option module in a PowerFlex 755 drive to an existing project
Safety Function Option in the Logix Designer application. This chapter is specific to safety and does
Module in the Logix Designer not cover all aspects of drive configuration.
Application
Before you can configure your option module in the Logix Designer
application:
• You must have a safety controller project with an EtherNet/IP network
connection configured and Time Sync enabled. See the documentation
for your controller, drive, and Ethernet adapter for information on
configuring those products in Additional Resources on page 13.
Understand Module The Integrated Safety Function module and its safe speed monitor functions
are configured in the Studio 5000 Logix Designer® application. Follow these
Properties Categories guidelines when configuring your safety application.
IMPORTANT For access to Motion Safety module properties, the Connection pull-down
menu in the Module Definition dialog box must be configured for Motion
and Safety or Safety Only.
Right-click your safety drive module and choose Properties. The Module
Properties dialog box appears.
Follow these steps to configure the Module Definition dialog box properties.
1. Select the General category and click Change to open the Module
Definition dialog box.
2. From the Revision pull-down menu, choose the drive firmware revision.
3. From the Electronic Keying pull-down menu, choose the type of
electronic keying. See Table 44 for more details.
TIP When ‘Safety’ appears in the Connection mode, integrated safety is implied.
Follow these steps to configure the Safety Output and Safety Input requested
packet interval (RPI) values.
1. Click Connection.
From the Connection category you can observe the status of the Safety
Output and Safety Input RPI values. The default values are shown.
IMPORTANT The Safety Output and Safety Input values, when viewed from the
Connection category, is for status only. To set the Safety Output and
Safety Input values, continue with step 2 through step 6.
2. To set the Safety Output value, right-click Safety Task in the Controller
Organizer and click Properties.
IMPORTANT The ‘Period’ is the interval at which the safety task executes. The
‘Watchdog’ must be less than the period.
For more safety task information, see the GuardLogix 5580 and
Compact GuardLogix 5380 Controller Systems Safety Reference
Manual, publication 1756-RM012.
4. Click OK.
5. To set the Safety Input RPI and other safety connection attributes, select
the Safety category on the module properties page and click
Advanced.... See Table 47 on page 151 for information on other safety
connection attributes.
The default Safety Input RPI value is 10 ms. Edit as appropriate for your
application.
IMPORTANT If the drive is used with an induction motor, there is a general rule of no
repeated (three or more) start/stops with less than 10 seconds between
them (assumes the highest RPI of 500 ms is used). Otherwise a safety
connection loss can occur. If less than 10 seconds is needed, a lower RPI can
be used per the following formula:
RPI (ms) * 19 = Min. Repeated Start/Stop time (seconds)
For example, a 50 ms RPI equates to a minimum of 0.95 seconds required
between repeated start/stops.
6. Click Apply.
The Actions category provides fault behavior options. Determine the preferred
machine function when a connection loss or connection idle condition occurs.
Safe Torque-off (STO) means that the drive immediately disables the motor
power outputs causing a coast condition for the motor and load. Safe Stop 1
(SS1) means that the drive decelerates the load to zero speed before removing
the motor power outputs causing a controlled stop for the motor and load.
Table 48 describes the attributes and the values available on the Actions page.
Follow these steps to configure the Actions to Take Upon Conditions dialog
box. For more information on connection action operation, please see Safety
Function in Response to Connection Event on page 68.
Connection idle is caused by the safety output task Drive-based Safe Stop 1 function is initiated and operates according
SS1
Connection Idle Action becoming disabled because the controller is in Remote to the SS1 configuration.
Program mode. STO Torque is removed according to the STO configuration.
Restart type means that the safety function resets and Restart allowed after safety function completes and function
will be ready for subsequent operation when the reset Automatic request is removed. If restart is required due to a fault, the fault
Restart Type condition must also be removed.
conditions are met. See specific function for more
detail. Manual Restart is allowed after a 01 transition of SO.ResetRequest bit.
Restart allowed after safety function completes and function
Cold start type means that the configured safety Automatic request is removed. If restart is required due to a fault, the fault
Cold Start Type function is ready for operation immediately after the condition must also be removed.
controller enters run mode.
Manual Restart is allowed after a 01 transition of SO.ResetRequest bit.
2. From the Device pull-down menu, choose the feedback device that was
defined as the Safety Feedback device during module configuration.
3. From the Type pull-down menu, choose the feedback type.
Table 49 shows the valid feedback types based on the module
configuration.
4. Set the remaining Primary Feedback attributes. See Table 50 for the
descriptions of these attributes.
5. Click Apply.
Feedback Instance
Primary Digital AqB
Hiperface
The velocity average time attribute is a moving-average window of time for which the
velocity samples are averaged. A small value results in more deviation in the velocity
Velocity Average Time evaluation. A large value results in less deviation in the velocity evaluation, but also
adds more delay to the resulting evaluation. Consider this delay with system
requirements for over-speed response.
The voltage monitor attribute indicates the valid range of the feedback's power
Voltage Monitor supply. If a voltage outside of the range is detected, a Safety Feedback Fault will occur.
See Table 50 to find the correct voltage monitoring range based on feedback device.
This value sets the maximum speed of the encoder. If a speed above the limit is
Maximum Speed(1) detected, a Safety Feedback fault will occur. If set to 0.0, the speed check is disabled.
Used in the safe-monitoring process to indicate to the safety controller that the motor
has stopped rotating. The system is at standstill when the speed detected is less than
Standstill Speed or equal to the configured Standstill Speed. The Standstill Speed parameter defines
the speed limit before the drive determines standstill has been reached.
This value sets the maximum acceleration of the encoder. If an acceleration above the
Maximum Acceleration(1) limit is detected, a Safety Feedback fault will occur. If set to 0.0, the acceleration check
is disabled.
(1) These diagnostics are based on the capability of the chosen encoder and its rated limits. They do not provide a safety-rated
safety function.
Feedback Instance
11.4…12.6V
Not monitored Not monitored
7…12V 4.75…5.25V
Secondary 4.75…5.25V 7…12V
11.4…12.6V
The Primary Feedback category set safety resolution in terms of counts per
encoder unit. The Scaling category configures the position and time to be used
in terms of counts per position unit in the safe monitoring functions.
Use the ‘Dual Velocity Check’ mode to measure the difference between
primary feedback speed and secondary feedback speed. Use ‘Dual Position
Check’ mode to measure the difference between primary feedback position
3. Click Apply.
The STO category provides a disable and coast fault action. However, if a
torque disable delay is needed following a STO Active command, you can enter
a value in the Delay field (see Safe Torque Off With Delay Operation on
page 72 for more information.)
STO becomes active if any of the following inputs to STO are asserted:
• STO Output = 0
• Safety Connection Loss and Connection Loss Action = STO
• Safety Connection is Idle and Connection Idle Action = STO
• Drive-based SS1 Function is Complete (= 1)
• Safety Stop Fault = 1
• Critical Safety fault occurs
STO Output is a tag in the safety output assembly used to activate the STO
function and is written by the GuardLogix controller. When any source for
STO is asserted, STO Active becomes high to indicate that the STO function
is operating.
The ‘Motion Safety > SS1’ category is configured when a Timed or Monitored
Safe Stop 1 condition is desired.
‘Timed SS1’ mode is available when the module is configured with or without
safety feedback monitoring. The ‘Monitored SS1’ mode is only available when
the module is configured for feedback monitoring (for more information on
the drive-based Safe Stop 1 function, see Safe Stop 1 Function on page 76.)
Timed SS1 is a fixed time for the motor to stop before removing
torque. Motor feedback is not monitored. ‘Stop Delay’ is the
only parameter used for ‘Timed SS1’ and determines the ‘Max
Stop Time’.
The ‘Motion Safety > SBC Category’ is configured when Safe Brake Control
functionality is desired in an application.
The default mode for SBC is ‘Not Used’. If the SBC functionality is desired,
setting the mode to ‘Used’, ‘Test Pulses’, or ‘Used, No Test Pulses’, will enable
the SBC function. When configured for ‘Used, Test Pulses mode’, pulse testing
of the physical brake outputs are performed. For more information on the
drive-based SBC function, see Safe Brake Control Function on page 83.
The Point Operation of a safety input configures the type of input operation
and its discrepancy time. See Table 54 for descriptions of these attributes.
The Point Mode configures the mode of the safety input. Table 55 describes
the valid values of this attribute.
The Input Delay Time configures the delay in sample time after a state change
of the input. See Input Delays on page 49 for more information. The Input
Error Latch Time attribute configures the time that a discrepancy must exist
before a Safety Input alarm is generated. See Latch Input Error Operation in
Single Channel Mode on page 39 for more information.
The Test Output category allows for configuration of the Test Outputs of the
device. See Table 56 for descriptions of the attributes. For more information on
test output operation, see Test Output on page 60.
TIP If a safety input’s Point Mode is configured for ‘Used with Test
Output’, the Test Output indicated by the ‘Test Source’ field must
have its ‘Point Mode’ configured as ‘Pulse Test Output’.
The Output Configuration category allows the safety outputs of the device to
be configured. The Point Operation Type of the safety output configures the
type of safety output according to Table 57.
The Point Mode of the safety output configures the mode of the safety output
according to Table 58.
The Output Error Latch Time attribute configures the time that a
discrepancy must exist before a Safety Output alarm is generated (see Safety
Outputs on page 50 for more information).
TIP If SBC mode is set to used, the safety outputs are under control of
the SBC function, and cannot be separately configured.
To set the stop action taken in response to a safety function activation, open the
Axis Properties and select the Actions page. The Safety Actions section of this
page is used to select Safe Torque Off and Safe Stopping actions and sources.
Make sure that these settings will allow the drive to complete a stop without
causing a safety function fault during normal operation. See the Stopping
Action section for the specific safety function in Chapter 4 for more
information.
Figure 68 on page 165 shows the Actions page. Table 59 on page 165 describes
the Safety Action attributes.
Special consideration must be taken when setting Motor and Load feedback
devices on the Associated Axes page. Table 60 on page 166 shows the correct
Motor/Load feedback device selection based on the physical terminal the
encoder is connected to per the supported feedback card.
IMPORTANT If you assign an SNN manually, make sure that the system expansion does
not result in duplication of SNN and node address combinations.
A warning appears if your project contains duplicate SNN and node address
combinations. You can still verify the project, but Rockwell Automation
recommends that you resolve the duplicate combinations.
1. To open the Safety Network Number dialog box, click to the right
of the Safety Network Number.
2. Select either Time-based or Manual.
If you select Manual, enter a value from 1…9999 decimal.
3. Click Generate.
4. Click OK.
If any differences are detected, the safety connection between the safety
controller and the drive is not established (for a new drive/system) or lost (for
an existing drive/system). A yellow icon appears next to the drive in the
controller project tree to indicate a lost or unestablished connection.
Configuration Ownership has to be reset to establish a new connection or to
reestablish an existing connection.
Reset Ownership
To reset ownership, see Restore the Drive to Out-of-Box State on page 214.
When you replace an integrated safety drive, the replacement device must be
configured properly and the replacement drives operation be user-verified.
Two options for safety drive replacement are available on the Safety tab of the
Controller Properties dialog box in the Logix Designer application:
• Configure Only When No Safety Signature Exists
• Configure Always
If the safety task has a safety task signature, the GuardLogix controller
automatically configures the replacement CIP Safety I/O device only if the
following is true:
• The device already has the correct safety network number.
• The device electronic keying is correct.
• The node or IP address is correct.
For detailed information, see the GuardLogix 5580 Controllers User Manual,
publication 1756-UM543 or Compact GuardLogix 5380 Controllers User
Manual, publication 5069-UM001.
Configure Always
You can use the Motion Direct Command (MDC) feature to initiate motion
while the controller is in Program mode, independent of application code that
A typical use might involve a machine integrator testing different parts of the
motion system while the machine is being commissioned or a maintenance
engineer, under certain restricted scenarios in accordance with safe machine
operating procedures, wanting to move an axis (like a conveyor) to clear a jam
before resuming normal operation.
This is because the safety task is not executed while the GuardLogix safety
controller is in Program mode. This applies to applications running in a single-
safety controller (with Motion and Safety connections). When an integrated
safety drive has a Motion connection to a standard controller and a separate
Safety connection to a dual-safety controller, the standard controller can
transition to Program mode while the safety controller stays in Run mode and
continues to execute the safety task.
Figure 70 - Safety State Indications When Controller is in Run Mode (safety task executing)
When the controller transitions to Program mode, the integrated safety drive is
in the safe state (torque is not permitted). The controller reports ‘Safety State
= Not Running’ and ‘Axis State = Start Inhibited’, as shown in Figure 71).
Figure 72 - STO Bypass Prompt When the Safety Controller is in Program Mode
IMPORTANT The warning in Figure 72 is displayed only the first time a motion direct
command is issued.
IMPORTANT Switch the controller to Run mode to exit Motion Direct Command mode
and end the STO function bypass.
IMPORTANT The persistent warning message text ‘Safe Torque Off bypassed’ appears
when a motion direct command is executed.
The warning message persists even after the dialog is closed and
reopened as long as the integrated safety drive is in STO Bypass mode.
The persistent warning message is removed only after the integrated
safety drive's Safety State is restored to the Running state.
Figure 75 - Axis and Safe State Indications on the Hookup Services Dialog Box
Figure 76 - Axis and Safe State Indications on Motion Direct Commands Dialog Box
Figure 77 - Axis and Safe State Indications on the Motion Console Dialog Box
ATTENTION: Motion is allowed and the STO function is not available when
motion direct commands are used in Program mode.
Motion direct commands issued when the controller is in Program mode
cause the drive to bypass the STO Active condition.
It is your responsibility to implement additional preventive measures to
maintain safety integrity of the machinery during execution of motion direct
commands in Program mode.
The PowerFlex 755/755T drive products, with the Integrated Safety Function
option module, contain one Motion Safety instance to provide integrated
safety functions. The safety instance operates independently of the inverters
and feedback used for motion. The drive module safety instance receives
encoder safety feedback for use with the integrated safety functions. The safety
feedback is also supplied to the controller safety task over the safety connection
for use with controller-based safety functions that may operate in the
controller.
A motion and safety system can be configured so that a safety function operates
in the controller. This type of configuration is referred to as a controller-based
safety function. The system can also be configured so that the safety function
operates in the drive module with the initiation and monitoring of the
function in the safety task. This type of safety function is referred to as drive-
based safety. A motion system can have both controller-based and drive-based
safety functions.
In this example we describe how a motion and safety control system operates
and how motion and safety tasks are coordinated. In typical motion and safety
This sequence of events represents the steps required for a Monitored SS1
drive-based safety function.
1. The safety task reads the E-stop input and detects the switch actuation.
2. The safety task communicates an SS1 request by setting the bit:
module:SO.SS1Request tag of the drive (inverter) motion-safety
instance.
3. The motion-safety instance in the drive communicates to the drive
motion core of the Axis Safety Status.
4. The motion core communicates with the motion controller running the
motion task by updating the motion axis tag axis.SS1ActiveStatus.
5. The motion task controls the axis to bring the motor to a stop within the
Monitored SS1 limits for speed and time.
6. While the axis is stopping, the SS1 function (in the motion-safety
instance) monitors the axis speed to make sure it remains below the
speed limit and maximum stopping time.
7. When the axis reaches standstill speed, the motion-safety core activates
the Safe Torque Off function.
This sequence of events represents the steps required for a Monitored SS1
controller-based safety function.
1. The safety task reads the E-stop input and detects the switch actuation.
2. The safety task activates the SS1 safety instruction running in the safety
task.
3. The SS1 instruction communicates an SS1 active by setting the bit:
module:SO.SS1Active tag of the drive (inverter) motion-safety instance.
4. The motion-safety instance in the drive communicates to the drive
motion core of the Axis Safety Status.
5. The motion core communicates with the motion controller running the
motion task by updating the motion axis tag axis.SS1ActiveStatus.
6. The motion task controls the axis to bring the motor to a stop within the
Monitored SS1 limits for speed and time.
7. While all events are occurring, the motion-safety instance updates the
Feedback Velocity tag, module:S1. FeedbackVelocity, in the safety
controller. The SS1 function running in the safety task receives the
speed scaled by the SFX safety instruction and makes sure the axis
remains below the speed limit and maximum stopping time.
8. When the axis reaches standstill speed the SS1 safety instruction outputs
SS1 complete.
The safety task communicates to the drive motion safety instance to activate
STO by clearing the bit: module:SO.STOOutput tag of the drive motion-
safety instance.
This figure shows how the safety task and motion tasks communicate with the
drive.
PowerFlex 755/755T
Drive Product
CIP Motion™ Motion (1)
Control Hardware Protocol Controller
(motion task)
Integrated
Motion Core
Motion
Safety Instance Motion Core Safety (1)
CIP Safety™ Controller
Protocol (safety task)
Power Hardware
Primary
Servo Motor Secondary
Encoder
(SIL 2, PL d) Encoder(2)
(1) Motion and Safety connections can be made from a single Safety controller or two separate Motion and Safety controllers.
(2) The secondary encoder is required to meet a SIL 3 system rating.
The safe monitor network executes motion and safety tasks by using CIP
protocol.
S af sages on
ety it Mes ect
i
Con Explic nn
ne
cti n Co
on tio
Mo
Safety fault and status sent
to motion controller axis tags.
Motion Safety Motion Axis
Instance Motion Core
PowerFlex 755/755T
Drive Product
Motion Connection
The motion connection communicates drive motion and safety status to the
motion task. The motion connection also receives motion commands from the
motion task in the motion controller. Data is exchanged at a periodic rate over
the connection. To configure the drive-module motion connection Axis
Properties in the Logix Designer application, see the PowerFlex 750-Series AC
Drives Programming Manual, publication 750-PM001-EN-P or the
PowerFlex Drives with TotalFORCE® Control Programming Manual,
publication 750-PM100-EN-P.
Some of the axis tags are updated from fault and safety status provided by the
safety instance in the drive module. The safety instance sends this status to the
motion core and then on to the motion controller. Axis tags show the updated
status. See Figure 79 for an illustration on how status is sent to the motion
controller.
IMPORTANT Axis tags are for status only and are not used by the safety function.
Pass-through Data
Some of the Motion Connection axis tags are updated from information that is
received from the Safety Connection. This data originates in the safety
controller as Safety Output assembly tags and are passed through the drive and
on to the motion controller where the corresponding axis tag is updated. These
data are called pass-through data.
The pass-through data includes items such as status and faults for controller-
based safety functions. Two general-purpose 32-bit words are provided in the
output assembly from the safety controller and appear as AxisSafetyDataA and
Axis SafetyDataB in the motion controller associated axis.
Safety Data A and B are provided for the safety and motion application for
additional safety program status. A typical use of Safety Data A and Safety
Data B can be to indicate the value of a safety limit that is currently in effect for
the motion application to control the motion accordingly.
IMPORTANT Axis tags are for status only and are not used by the safety function.
Safety Connection
The safety controller communicates with the safety instance in the drive
module over the safety connection. Cyclic data are passed in each direction
over the safety connection that appears in Safety Controller tag structures
called input and output assembly. The safety connection cyclic rate is
configured in the Logix Designer application.
The Safety Input Assembly tag structure is data from the drive module safety
instance to the safety controller. The Safety Output Assembly tag structure is
data from the safety controller to the drive module safety instance.
Explicit Messages
Use explicit messages to communicate with a drive and obtain additional fault,
status, or configuration information that is not available in the Safety I/O Tag
structure. Attribute data is useful for additional diagnostic information. An
explicit message can be sent by any controller on the network and used to read
any drive module attribute. See Motion Connection on page 179 for the drive-
module safety attribute names and numbers that can be used by an MSG
instruction. See Figure 79 on page 179 to see how explicit messages are part of
motion and safety communication.
IMPORTANT Explicit messages must not be used for any safety-related function.
The safety supervisor state provides information on the state of the integrated
safety connection and the mode of operation. There is only one safety
supervisor object per drive module.
Application Example - Using In this example, a PowerFlex 755 drive (equipped with embedded Ethernet)
controls a servo motor (catalog number MPL-B430P-M). A Universal Feedback
SFX, SS1, and SLS Instructions option module (catalog number 20-750-UFB-1) and an Integrated Safety
with Integrated Motion Function option module (catalog number 20-750-S4) are used to interface to a
GuardLogix 5580 safety controller (catalog number 1756-L84ES).
This example shows the programming and configuration required for three of
the most common safe monitoring functions:
• Safe Feedback
• Safe Stop 1
• Safe Limited Speed
A Guard Locking Switch (catalog number TLS-Z GD2) is mapped to one of the
S4 Safety Outputs. This switch can be opened when the Safe Stop 1 is complete
and when the Safe Limited Speed is below the required speed for an operator to
access the machine function.
The Safety Reset and Home Request functions are programmed with the other
two S4 Safety inputs. These do not need to be safety-rated devices. For the
purpose of this example, other inputs and outputs are toggled for simplicity. At
any time, you can implement additional safety or IO devices as required based on
the machine risk assessment.
Studio 5000 Connection is set to ‘Motion And Safety’ since the GuardLogix
controller will provide both in this example. The Safety Instance is set to ‘Single
Feedback Monitoring’ in order to use Safe Limited Speed, which supports
monitoring Safe Stop 1 and safe feedback.
This PowerFlex 755 drive is configured with the 20-750-UFB-1 in port 4. The
Safe Feedback checkbox must be checked for proper configuration and
agreement with the safety switches on the Universal Feedback option module.
IMPORTANT The 20-750-S4 and 20-750-UFB-1 must reside in the same backplane board.
Since the MPL-B430P-M device is used for the primary safety channel, the
normal cycles per revolution are 1024 and must be configured in the Primary
Feedback tab.
• Inputs 0 and 1 are used with an OSSD Estop input from the 800FP.
• Input 2 is a standard digital input from a push button to safety reset the
S4 module.
• Input 3 is a standard digital input from a push button to set the SFX
home.
Programming Example
This example illustrates configuration of the safety input, logic, and output
routines.
TIP Configure your system based on the required safety level devices and ratings.
Safety Input
The DCS Instruction is responsible for evaluating the dual-input validity into
the GuardLogix safety controller.
Safety Logic
The Safety Logic is used to configure when a safety reset occurs, the home
trigger, and the execution of the SFX instruction (which must have primary
feedback valid for it to execute properly).
Both the Safe Stop 1 and Safe Limited Speed use the SFX instruction for
correct monitoring of feedbacks. The Safe Stop 1 requests when the 800FP
inputs are removed. The Safe Limited Speed requests, in this example, with the
toggling of the Examine On tag.
Safety Output
The Safe Torque Off output must be true in order for any of the preceding safe
monitoring functions (namely SFX, SS1, and SLS) to function.
The PowerFlex 755 S4 safety actions can be configured based on the required
reaction to various machine requirements. In this instance, the STO request is
executed by the PowerFlex 755 in causing a disable and coast reaction.
However, the request to the SS1 (requested by the GuardLogix Safety Task) is
executed by the GuardLogix Motion Controller (not the Safety Controller)
with the use of pass-through tags. In this case, the Motion Axis Stop is used to
control stop the motor, as shown by the programming example.
The Safe Limited Speed (and any other safe monitoring instruction requests
besides STO, SS1, and SS2) are handled with the use of pass-through tags in
the GuardLogix Motion Controller. The GuardLogix Safety Controller uses
pass-through tags to the Motion Controller to use the Motion Change
Dynamics instruction for the SLS request, as shown in the programming
example.
Figure 92 - Motion Instructions Used to Motion Servo On and Motion Servo Off
Figure 94 - Use of the Motion Change Dynamics Instruction to Change from Normal Operating
Speed to Safe Limited Speed and Back based on the Safety Task Request
Figure 95 - Use of the Motion Axis Stop Instruction to Bring the Motor to 0 Speed Once the SS1
Request is Made From the Safety Task
When the stop is complete and 0 speed, the Motion Servo Off is given to open
the position loop and stop modulating the drive. The Safety Task then uses the
STO Output off to put the drive and motor into a Safe Torque Off state.
Topic Page
Monitor Status Using Status Indicators 195
Monitor Status with a HIM or Software 205
Monitor Status Using Status The option module has four status indicators to provide status of the module,
safety network, and motion output of the drive:
Indicators
• Module status (DS1)
• Network status (DS2)
• Motion output status (DS3)
• Safety fault (DS4)
IMPORTANT Status indicators are not reliable for safety functions. Use status indicators
only for general diagnostics during commissioning or troubleshooting. Do
not attempt to use status indicators to determine operational status.
Safety Fault Names The Motion Safety instance in the Integrated Safety Functions option module
reports faults to the drive through the AxisSafetyFaults and
AxisSafetyFaultsRA tags. Each bit in these tags indicates a specific fault. This
information is used by the drive to log and display faults.
The Logix Designer application displays axis faults and status. When an axis is
selected in the Controller Organizer, axis faults and status are displayed in the
QuickView® software window.
The safety faults named in Table 69 appear as Safety Faults when they occur. In
addition, if any of these faults are present, a safety fault appears under the axis
fault. Corresponding axis tags are set with any of the faults.
Understand Safety Faults To obtain more detailed information about any faults that are detected in the
drive, most faults have a corresponding fault-type attribute. These attributes
are read by using an MSG instruction in the ladder program to read the specific
attribute information, or by reading the corresponding DPI™ parameter.
Details of the various fault-type attributes are described in the following
sections.
See Explicit Messages on page 251 on for an example of using the MSG
instruction to read status.
The Safety Supervisor State provides information on the state of the safety
connection and the mode of operation. It can be read in the user's Logix
program using explicit messaging via the MSG instruction.
Table 70 - Safety Supervisor State: MSG
Parameter Value Description
Service Code 0x0E Get Attribute Single
Class 0x39 Safety Supervisor
Instance 1 –
Attribute 0x0B Device Status
Data Type SINT Unsigned Short Integer
If this fault persists through power cycles, return the drive and safety module
for repair. In case of malfunction or damage, no attempts at repair should be
made. Do not dismantle the option module.
The Safe Torque Off (STO) function detected a fault. The safe stop function
records the specific fault type in the STO Fault Type attribute. The STO Fault
Type attribute is also recorded in P7 [STO Fault Type]. Table 71 describes the
parameters for an MSG instruction. Table 72 describes the fault types.
The Safe Stop 1 (SS1) function detected a fault. The safe stop function records
the specific fault type in the Safe Stop Fault attribute. The SS1 Fault Type is
also recorded in P10 [SS1 Fault Type]. Table 74 describes the parameters for an
MSG instruction. The drive immediately disables torque, ignoring STO delay,
if an SS1 fault is detected. If the SS1 Fault Type is reported as 1 (no fault), the
SS1 fault was generated by the connected safety controller and reported to the
drive over the safety connection.
Table 73 - Safe Stop 1 Fault Type: MSG
Parameter Value Description
Service Code 0x0E Get attribute single
Class 0x5A Safety stop functions
Instance 1 Drive-module safety instance
Attribute 0x11c SS1 fault type
Data Type SINT Short integer
The Safe Brake Control (SBC) function detected a fault. The safe stop
function records the specific fault type in the SBC Fault Type attribute. The
SBC fault type is also recorded in P11 [SBC Fault Type]. Table 75 describes
the parameters for an MSG instruction. Table 76 describes the fault types.
The Integrated Safety Functions option module does not support drive-based
SS2, SOS, SLS, SLP, and SDI safe stop/safety limit functions. If the drive
reports one of these faults, then the fault was detected by the safety controller
and reported to the drive over the safety output connection, or the request tag
was set through the safety output assembly. Additional information for these
faults must be obtained from the safety controller that is associated with the
drive. In addition, the safety controller is responsible for issuing a torque
disable request.
When configured for safety feedback, the device performs periodic diagnostics
to make sure that the feedback device is operating correctly. Explicit messaging
can be used to read the fault type information from the drive. For example, if an
error is detected, the Safe Feedback object (class code 0x58) updates the Safe
Feedback Fault Type attribute (attribute ID 0x09) with the reason for the fault.
Table 77 - Safety Feedback Faults
Safe Feedback Safe Feedback Fault
Fault Type Description
Type Name
Value
1 No Fault No Fault is present.
2 Config The encoder's configuration is invalid.
The encoder speed has exceeded the configured maximum
3 Max Speed speed.
The encoder acceleration has exceeded the configured
4 Max Accel maximum acceleration.
5 Sin²+Cos² The encoder has failed the vector length or aspect ratio checks.
The encoder has exceeded the maximum number of quadrature
6 Quadrature signal errors.
The associated dual channel feedback instance has reported a
7 Discrepancy discrepancy.
The associated dual channel feedback instance has detected a
8 Partner fault in the other encoder.
The associated dual channel feedback instance has detected a
9 Voltage fault in the other encoder.
10 SignalNoise The encoder signals have noise that is preventing operation.
11 Signal Lost The encoder signals are not present.
12 Data Lost Stopped receiving data from a Digital Encoder.
13 Device Fail The encoder device has failed.
The frequency of the encoder has exceeded the maximum level
107 Max Freq for this product.
The offset of the Sine/Cosine signal from ground is outside the
108 SinCosOffset required level.
The encoder position count has exceeded the maximum value
109 Pos Rollover that can be represented in this product.
If the drive motion safety instance detects a fault, the input assembly tag
module:SI.SafetyFault is set to 1. The associated axis.SafetyFault tag is also set
to 1.
A Safety Fault can result from the SS1 stopping function, STO function, safety
feedback, SBC function, or other safety diagnostics.
To clear (reset) the Safety Fault, the fault conditions must be removed first and
then a transition from logic 0 to 1 of the module:SO.ResetRequest tag is
required. It is only the 0 to 1 transition that clears the fault.
To clear an axis fault that is associated with a Safety Fault, first clear the Safety
Fault from the safety task of your application, then clear the axis fault using the
MAFR command from the motion application. If the drive is not in integrated
motion, then first clear the safety fault in the safety task and then clear the
drive fault by writing to the O.LogicCommand_ClearFaults bit.
See Figure 97 on page 205 for more information about the Integrated Safety
Functions option module state restart functionality.
A B C D E F
A. Set SO.SafeTorqueOff = 1 C. Set SO.SafeTorqueOff = 0 E. Set SO.SafeTorqueOff = 1
B. Fault Detected D. Set SO.Reset = 1 F. PF 755 Clear Fault (I/O Mode) or MAFR (CIP Motion™)
Monitor Status with a HIM or This section describes safety-related status information available for viewing
with a HIM, Drive Module Properties in the Logix Designer application, or
Software Connected Components Workbench™ software.
The only message that is displayed for any fault originating from the module is
‘SAFETY BRD FAULT’ with a fault code of F211 for PowerFlex 755 drives
and a code of F87 for PowerFlex 755T drives. This fault is displayed by the
HIM, drive module, and Connected Components Workbench software. To
determine the cause of the fault, examine the bits set in P4 [Safety Status] in
Connected Components Workbench, or by examining the
SO.PassThruStopFaults and SO.PassThruLimitFaults in the Logix Designer
application. After determining the fault type, see the Understand Safety Faults
section for more information on the fault.
Safety board faults are also stored in the drive fault queue:
Further information on the cause of the fault is also recorded in the Integrated
Safety Functions module events queue:
ATTENTION: The status data that are described in this section is STANDARD
data (not SAFETY data) and cannot be used as part of a safety function.
For diagnostic purposes, you can also view status attributes by accessing the
following Host Config parameters. These parameters are different than the
‘Device Config’ parameters from a HIM, Connected Components
Workbench software, or the Logix Designer application:
• P3 [Safety State]
• P4 [Safety Status]
• P5 [Safety Faults]
• P6 [Safe Status Mfg]
• P7 [Safe Faults Mfg]
Monitor Status Using This section describes safety-related status information available in the
Integrated Motion Axis tags in the motion controller. These tags can be
Integrated Motion monitored by user programs in the motion controller and they can be
examined when the Logix Designer application is online with the motion
controller.
Axis.CIPStartInhibits 676 DINT A bit map that specifies the current state of all standard conditions that inhibits
starting of the axis.
Axis.SafeTorqueOffActiveInhibit [5] BOOL Indicates if the Safe Torque Off function is inhibiting the axis from starting.
0 = STO is not inhibiting axis
1 = STO is inhibiting axis
Axis.AxisSafetyState 760 DINT Drive module Safety Supervisor state. See Safety Supervisor State on page 199
for more details.
Axis.AxisSafetyStatus 761 DINT Collection of bits indicating the status of the standard safety functions for the
axis as reported by Drive Safety Instance.
Axis.SafetyFaultStatus [0] BOOL Indicates that a fault was detected by a drive-based a safety function.
0 = No Fault
1 = Faulted
Axis.SafetyResetRequestStatus [1] BOOL Indicates the state of the module:SO.ResetRequest controller output tag. A
transition from 0 to 1 resets drive-based safety functions.
Axis.SafetyResetRequiredStatus [2] BOOL Indicates that the drive-module safety instance that is associated with this Axis
requires a reset of the safety function.
0 = Normal
1 = Reset Required
Axis.SafeTorqueOffActiveStatus [3] BOOL Set if the drive-based STO function is active (to disable torque).
Axis.SafeTorqueDisabledStatus [4] BOOL Set if the drive-based STO function has disabled torque.
Axis.SBCActiveStatus [5] BOOL Set if the drive-based SBC instruction is active (to engage brake) or if the
controller-output tag module:SO.SBCBrakeEngaged is set.
Axis.SBCEngagedStatus [6] BOOL Set if the drive-based SBC instruction has engaged the brake OR if the
controller-output tag module:SO.SBCBrakeEngaged is set.
Axis.SS1ActiveStatus [7] BOOL Set if the drive-based SS1 instruction is active OR if the module:SO.SS1Active
controller tag is set.
Axis.SS2ActiveStatus [8] BOOL Indicates the status of the module:SO.SS2Status controller output tag. See the
controller-based SS2 instruction.
Axis.SOSActiveStatus [9] BOOL Indicates the status of the module:SO.SS2Status controller output tag. See the
controller-based SS2 instruction.
Axis.SOSStandstillStatus [10] BOOL Indicates the status of the module:SO.SOSStandstill controller output tag. See
the controller-based SOS instruction.
Axis.SMTActiveStatus [11] BOOL Reserved for future use. Always 0.
Axis.SMTOvertemperatureStatus [12] BOOL Reserved for future use. Always 0.
Axis.SSMActiveStatus [16] BOOL Indicates the state of the module:SO.SSMActive controller output tag.
Axis.SSMStatus [17] BOOL Indicates the state of the module:SO.SSMStatus controller output tag.
Axis.SLSActiveStatus [18] BOOL Indicates the state of the module:SO.SLSActive controller output tag.
Axis.SLSLimitStatus [19] BOOL Indicates the state of the module:SO.SLSLimit controller output tag.
Axis.SLAActiveStatus [20] BOOL Indicates the state of the module:SO.SLAActive controller output tag.
Reserved for future use. Always 0.
Axis.SLALimitStatus [21] BOOL Indicates the state of the module:SO.SLALimit controller output tag.
Reserved for future use. Always 0.
Axis.SDIActiveStatus [22] BOOL Indicates the state of the module:SO.SDIActive controller output tag. See the
controller-based SDI instruction.
Axis.SDILimitStatus [23] BOOL Indicates the state of the module:SO.SDILimit controller output tag. See the
controller-based SDI instruction.
Axis.SafePositiveMotionStatus [24] BOOL Set if the primary feedback velocity is greater than Standstill Speed.
Axis.SafeNegativeMotionStatus [25] BOOL Set if the primary feedback velocity is less than Standstill Speed.
Axis.SCAActiveStatus [26] BOOL Indicates the state of the module:SO.SCAActive controller output tag.
Axis.SCAStatus [27] BOOL Indicates the state of the module:SO.SCAStatus controller output tag.
Axis.SLPActiveStatus [28] BOOL Indicates the state of the module:SO.SLPActive controller output tag. See the
controller-based SLP instruction.
Axis.SLPLimitStatus [29] BOOL Indicates the state of the module:SO.SLPStatus controller output tag. See the
controller-based SLP instruction.
Axis.SafetyOutputConnectionClosedStatus [30] BOOL No active connection of an output assembly from the safety controller exists.
Axis.SafetyOutputConnectionIdleStatus [31] BOOL An active output assembly connection exists but the safety controller is in
Program mode.
Axis.AxisSafetyStatusRA 762 DINT Collection of bits indicating the status of Rockwell Automation specific safety
functions for the axis as reported by Drive Safety Instance.
Axis.SafeBrakeIntegrityStatus [0] BOOL Indicates the state of the module:SO.SBCIntegrity controller output tag. See the
controller-based SBC instruction description.
Axis.SafeFeedbackHomedStatus [1] BOOL Indicates the state of the module:SO.SFHomed controller output tag. See the
controller-based SFX instruction description.
Axis.AxisSafetyFaults 763 BOOL Collection of bits indicating the Safety Fault status of the drive-module safety
instances and integrated safety functions.
Axis.SafetyCoreFault [0] BOOL Internal SSM fault. Cycle drive power to reset. If the fault reoccurs, replace the
option module.
Axis.SafetyFeedbackFault [2] BOOL A feedback fault was detected.
Axis.SafeTorqueOffFault [3] BOOL This bit indicates the fault status of the STO function (0 = no fault, 1 = faulted).
The cause of the fault is recorded in P7 [Device Config STO Fault Type].
Axis.SS1Fault [4] BOOL The drive-based SS1 function has detected a fault OR the controller-output tag
module:SO.SS1Fault is set. Enters ‘Safe Stop 1 (SS1)’ in the Axis Properties
Faults and Alarms Log. Cleared by a Motion Axis Fault Reset (MAFR). For Drive-
based SS1 Fault, see P10 [SS1 Fault Type] for more information. For controller-
based SS1, see the SS1 instruction description.
Axis.SS2Fault [5] BOOL Set if the module:SO.SS2Fault controller output tag is set. Enters ‘Safe Stop 2
(SS2)’ in the Axis Properties Faults and Alarm Log. Cleared by a Motion Axis
Fault Reset (MAFR). See the controller-based SS1 instruction description.
Axis.SOSFault [6] BOOL Set if the module:SO.SOSFault controller output tag is set. Enters ‘Safe
Operating Stop (SOS)’ in the Axis Properties Faults and Alarms Log. Cleared by a
Motion Axis Fault Reset (MAFR). See the controller-based SOS instruction
description.
Axis.SBCFault [7] BOOL Set when the drive-based SBC function has detected a fault or the controller-
output tag module:SO.SBCFault is set. Enters ‘Safe Brake Control (SBC)’ in the
Axis Properties Faults and Alarms Log. Cleared by a Motion Axis Fault Reset
(MAFR). For a drive-based SBC Fault, see P11 [SBC Fault Type] for more
information. For a controller-based SBC Fault, see the SBC instruction
description.
Axis.SMTFault [8] BOOL Reserved for future use. Always 0.
Axis.SSMFault [16] BOOL Set if the module:SO.SSMFault controller output tag is set. Enters ‘Safe Speed
Monitor (SSM)’ in the Axis Properties Faults and Alarms Log. Cleared by a
Motion Axis Fault Reset (MAFR).
Axis.SLSFault [17] BOOL Set if the module:SO.SLSFault controller output tag is set. Enters ‘Safe Limited
Speed (SLS)’ in the Axis Properties Faults and Alarms Log. Cleared by a Motion
Axis Fault Reset (MAFR). See the controller-based SLS instruction description.
Axis.SLAFault [18] BOOL Reserved for future use. Always 0.
Axis.SDIFault [19] BOOL Set if the module:SO.SDIFault controller output tag is set. Enters ‘Safely Limited
Direction (SDI)’ in the Axis Properties Faults and Alarms Log. Cleared by a
Motion Axis Fault Reset (MAFR). See the controller-based SDI instruction
description.
Axis.SCAFault [20] BOOL Set if the module:SO.SCAFault controller output tag is set. Enters ‘Safe Cam
(SCA)’ in P45 [SDI Fault] in the Axis Properties Faults and Alarms Log. Cleared
by a Motion Axis Fault Reset (MAFR).
Axis.SLPFault [21] BOOL Set if the module:SO.SLPFault controller output tag is set. Enters ‘Safely
Limited Position (SLP)’ in P46 [SLP Fault] in the Axis Properties Faults and
Alarms Log. Cleared by a Motion Axis Fault Reset (MAFR). See the controller-
based SLP instruction description.
Axis.SafetyValidatorFault [30] BOOL The Safety Validator Object has detected a fault.
Axis.SafetyUNIDFault [31] BOOL The Safety Validator Object has detected a fault relating to the Unique
Identifier number.
Axis.AxisSafetyFaultsRA 764 DINT Collection of bits indicating the safety fault status of Rockwell Automation
safety functions.
Axis.SFXFault [1] BOOL Set if the module:SO.SFXFault controller output tag is set. Enters ‘SFX’ in the
Axis Properties Faults and Alarms Log. Cleared by a Motion Axis Fault Reset
(MAFR). See the controller-based SFX instruction description.
Axis.AxisSafetyAlarms 753 DINT Reserved for future use.
You can determine if the drive is in the out-of-box state by using a diagnostic
parameter or by using the Logix Designer application.
IMPORTANT Only authorized personnel can reset ownership. The safety connection
must be inhibited before the reset. If any active connection is detected, the
safety reset is rejected.
The safety control state can be read from P3 [Host Config Safety State] via the
HIM or Connected Components Workbench software. You can also use an
MSG command in Logix Designer application to read the Safety Supervisor
Status.
If the state is ‘Waiting’ (8), then the safety control is in the out-of-box state.
Before you can reset the drive to out-of-box state, the value of the Safety Reset
[#14] diagnostic item must be ‘Ready’ (1) or the reset is not allowed. Set the
Safety Reset [#14] diagnostic item to ‘Reset’ (2) by using a HIM or Connected
Components Workbench software.
1. Right-click the PowerFlex 755 drive you created, and choose Properties.
Notes:
Use this appendix to validate your drive safety instructions. Each instruction
has a checklist with test commands and results to verify for normal operation
and abnormal operation scenarios.
Topic Page
Safe Stop 1 (SS1) 218
Safe Stop 2 (SS2) 220
Safe Operating Speed (SOS) 223
Safely-limited Speed (SLS) 225
Safely-limited Position (SLP) 226
Safe Direction (SDI) 228
Safe Feedback Interface (SFX) 229
Safe Brake Control (SBC) 231
Safe Stop 1 (SS1) Use this SS1 instruction checklist to verify normal operation and the abnormal
operation scenarios.
IMPORTANT Perform I/O verification and validation before validating your safety ladder
program. SFX instruction must be verified within your application.
When possible, use immediate operands for instructions to reduce the
possibility of systematic errors in your ladder program.
Instruction operands must be verified for your safety ladder program.
Safe Stop 2 (SS2) Use this SS2 instruction checklist to verify normal operation and the abnormal
operation scenarios.
IMPORTANT Perform I/O verification and validation before validating your safety ladder
program. SFX instruction must be verified within your application.
When possible, use immediate operands for instructions to reduce the
possibility of systematic errors in your ladder program.
Instruction operands must be verified for your safety ladder program.
Safe Operating Speed (SOS) Use this SOS instruction checklist to verify normal operation and the
abnormal operation scenarios.
IMPORTANT Perform I/O verification and validation before validating your safety ladder
program. SFX instruction must be verified within your application.
When possible, use immediate operands for instructions to reduce the
possibility of systematic errors in your ladder program.
Instruction operands must be verified for your safety ladder program.
Safely-limited Speed (SLS) Use this SLS instruction checklist to verify normal operation and the abnormal
operation scenarios.
IMPORTANT Perform I/O verification and validation before validating your safety ladder
program. SFX instruction must be verified within your application.
When possible, use immediate operands for instructions to reduce the
possibility of systematic errors in your ladder program.
Instruction operands must be verified for your safety ladder program.
Safely-limited Position (SLP) Use this SLP instruction checklist to verify normal operation and the abnormal
operation scenarios.
IMPORTANT Perform I/O verification and validation before validating your safety ladder
program. SFX instruction must be verified within your application.
When possible, use immediate operands for instructions to reduce the
possibility of systematic errors in your ladder program.
Instruction operands must be verified for your safety ladder program.
Safe Direction (SDI) Use this SDI instruction checklist to verify normal operation and the abnormal
operation scenarios.
IMPORTANT Perform I/O verification and validation before validating your safety ladder
program. SFX instruction must be verified within your application.
When possible, use immediate operands for instructions to reduce the
possibility of systematic errors in your ladder program.
Instruction operands must be verified for your safety ladder program.
Safe Feedback Interface Use this SFX instruction checklist to verify normal operation and the
abnormal operation scenarios.
(SFX)
IMPORTANT Perform I/O verification and validation before validating your safety ladder
program. SFX instruction must be verified within your application.
When possible, use immediate operands for instructions to reduce the
possibility of systematic errors in your ladder program.
Instruction operands must be verified for your safety ladder program.
Normal Scaling Set up a trend with the expected time scale and the following tags to graphically compare the motion position and speed from the
Operation Main task to the scaled position and speed in the Safety task.
• Axis_Name.ActualPosition
• Axis_Name.ActualSpeed
• SFX_Name.ActualPosition
• SFX_Name.ActualSpeed
Verify that the standard and safety position and speed are correlated as expected.
Initiate a Start command.
Initiate a Homing procedure.
• Verify that the Home Position in the SFX instruction is set
Normal Homing Set up a trend with the expected time scale and the following tags to graphically compare the motion position and speed from the
Operation Main task to the scaled position and speed in the Safety task.
• Axis_Name.ActualPosition
• SFX_Name.ActualPosition
Verify that the standard and safety position are correlated as expected.
Initiate a Start command.
• Verify that the machine is in a normal machine run condition
• Verify proper machine status and safety application program status
Operate the machine within the normal operating range.
Set up a trend with the expected time scale and the following tags to graphically compare the motion position and speed from the
Main task to the scaled position and speed in the Safety task.
• Axis_Name.ActualPosition
• Axis_Name.ActualSpeed
• SFX_Name.ActualPosition
• SFX_Name.ActualSpeed
Abnormal Operation 1
Verify that the standard and safety position and speed are correlated as expected.
Disconnect the feedback between the motor/encoder and drive.
Verify the generation of a Fault Type: 100 Feedback Invalid by checking Device_Name.SI.PrimaryFeedbackValid tag.
Verify that the system fault action takes place as configured.
While the system is stopped with the sensor subsystems in a safe state, initiate a Start command.
• Verify proper machine status and safety application program status
While the system is stopped, initiate a Reset command.
• Verify proper machine status and safety application program status
Safe Brake Control (SBC) Use this SBC instruction checklist to verify normal operation and the
abnormal operation scenarios.
IMPORTANT Perform I/O verification and validation before validating your safety ladder
program.
When possible, use immediate operands for instructions to reduce the
possibility of systematic errors in your ladder program.
Instruction operands must be verified for your safety ladder program.
Notes:
Topic Page
Integrated Safety Functions Option Module Specifications 233
Environmental Specifications 235
Certifications 236
Integrated Safety Functions These specifications apply to the Integrated Safety Functions option module.
For additional specifications, see these publications:
Option Module Specifications
• PowerFlex® 755 AC Drives Technical Data, publication 750-TD001
• PowerFlex 750-Series Products with TotalFORCE® Control Technical
Data, publication 750-TD100
Attribute Value
Standards (when used with IEC 61800-5-2, EN 61800-5-1, EN 61800-3, EN ISO 13849-1, EN 62061,
PowerFlex 755 drives) EN 60204-1, IEC 61508
Safety ratings(when used with SIL 3 according to EN 62061 / IEC 61508
PowerFlex 755 drives) SIL CL 3 according to IEC 61800-5-2 / EN 62061 / IEC 61508
Cat. 4 and PL e according to EN ISO 13849-1
Standards (when used with EN 61800-5-2, EN 61800-5-1, EN 61800-3, EN ISO 13849-1, EN 62061,
PowerFlex 755T drive products) EN 60204-1, IEC 61508
Safety ratings (when used with SIL 3 according to EN 62061 / IEC 61508
PowerFlex 755T drive products) SIL CL 3 according to EN 61800-5-2 / EN 62061 / IEC 61508
Cat. 4 and PL e according to EN ISO 13849-1
Power supply (user I/O) 24V DC ±10%, 0.8…1.1 x rated voltage(2) PELV or SELV
Conductor type Multi-conductor shielded cable
Conductor size (1) 0.3…0.8 mm2 (28…18 AWG)
Strip length 10 mm (0.39 in.)
Recovery time (approximate Network STO mode: 100 ms
time before drive can start after
the torque enable request is
made)
(1) See the Industrial Automation Wiring and Grounding Guidelines, publication 1770-4.1.
(2) Safety outputs need additional fuse for reverse voltage protection of the control circuit. Install a 6 A slow-blow or 10 A fast-
acting fuse.
Electrical Requirements
Table 95 - Safety Input Specifications
Attribute Value
Input type Current sinking
IEC 61131-2 (input type) Type 3
Voltage, on-state 11…30V DC
Voltage, off-state -3…5V DC
Current, on-state, minimum 2 mA
Current, off-state, maximum 1.5 mA
Input reaction time, maximum <10 ms + set values of ON/OFF delays
Environmental Specifications The installation must comply with all environmental, pollution degree, and
drive enclosure rating specifications required for the operating environment.
Category Specification
Ambient temperature
Storage temperature
For detailed information on environmental, pollution degree, and drive
Shock enclosure rating specifications, see the technical data publication for your
Operating drive.
Packaged for shipment • PowerFlex 750-Series AC Drives Technical Data,
publication 750-TD001
Vibration • PowerFlex 750-Series Products with TotalFORCE Control Technical Data,
Operating publication 750-TD100
Packaged for shipment • PowerFlex 755TM IP00 Open Type Kits Technical Data,
publication 750-TD101
Sinusoidal loose load
Random secured
Surrounding environment
At the end of its life, this equipment should be collected separately from any
unsorted municipal waste.
Notes:
Controller axis tags are used by the motion controller motion task to read the
status of safety functions and coordinator motion. This appendix lists the
motion controller tags that are associated with the safety instances and with
safety functions operating in the safety task of the controller.
Topic Page
Safety Assembly Tags 240
Safety Feedback Attributes 245
Safe Stop Function Attributes 247
Safety attributes provide additional information not available through the tag
structure. Attributes are read using explicit messages.
IMPORTANT The controller axis tags and the safety attributes read by using explicit
messages must not be used in the operation of a safety function.
Safety Assembly Tags Safety assembly tags are associated with a safety connection from a safety
controller to a drive module. The data in these tags are communicated at the
configured connection rate.
Safety Input Assembly tags contain the data that is transferred from the drive
to the GuardLogix® using CIP Safety™ protocol over EtherNet/IP®. This is the
network safety status data. Safety Output Assembly tags contain the data that
is transferred from the GuardLogix controller to the drive option module using
CIP Safety protocol over EtherNet/IP. This is the network safety control data.
CIP Safety protocol over EtherNet/IP transfers data with integrity up to SIL 3
and PL e.
TIP The Output and Input designations are relative to the GuardLogix controller.
Safety Feedback Attributes Safety feedback attributes provide configuration and status information for
safety feedback. The module has two safety feedback instances. The safety
feedback instances contain safety feedback attributes and safety feedback
configuration data. The following attributes can be read.
10 (0xA) Reset Feedback Fault Resets a motion feedback fault (read/write access). 0 to 1 transition will reset a safety feedback fault once the
fault condition is removed
11 (0xB) Position Safe State Behavior Defines behavior for value reporting when faulted. 2 = Hold Last Value
13 (0xD) Velocity Safe State Behavior Defines behavior for value reporting when faulted. 0 = Use Velocity Safe State Value (default)
14 (0xE) Velocity Safe State Value Safe Velocity Feedback and Acceleration Feedback value. Default = 0
16 (0x10) Feedback Unit Unit of measure for the feedback device. 0 = Revolution (default)
1 = Meter
Safe Stop Function Safe-stop function attributes provide configuration and status information for
safety feedback.
Attributes
The module has one safe stop function instance. Safe-stop function attributes
provide status and configuration data. All attributes can be read using explicit
messages. Attributes that can be written are indicated in the table.
Configuration attributes can be read but cannot be written using an explicit
message.
Table 103 - Safe Stop Function Attributes (Class 0x5A)
Attribute ID Attribute Name Attribute Description Values
Decimal (Hex)
10 (0xA) Safety Reset Reset all safety functions. 0 to 1 transition required to reset
11 (0xB) Restart Type Selects safety function restart behavior while operating. 0 = Manual
1 = Automatic
12 (0xC) Cold Start Type Selects safety function restart behavior when applying controller power or 0 = Manual
mode change to Run. 1 = Automatic
20 (0x14) Safety Feedback Instance Instance ID of a Safety Feedback instance to provide position, velocity, and 0 = No feedback (default)
acceleration data used by safe stop functions.
21 (0x15) Safety Feedback Fault Copy of feedback status from the Safety Feedback instance. 0 = No Fault
1 = Faulted
30 (0x1E) Safety Function Fault Logical OR of all Fault attributes that reference this instance. 0 = No Fault
1 = Faulted
31 (0x1F) Safety Stop Fault Logical OR of all Stop Fault attributes in this instance. 0 = No Fault
1 = Faulted
32 (0x20) Safety Limit Fault Logical OR of all Limit Fault attributes that reference this instance. 0 = No Fault
No Limit Functions Supported
33 (0x21) Safety Limit Active Logical OR of all Limit Active attributes that reference this instance. 0 = No Limit
No Limit Functions Supported
34 (0x22) Restart Required A stop function has been activated and Restart Type is Manual. 0 = Restart Not Required
1 = Restart Required
40 (0x28) Safety Stop Status Collection of Safety Stop Status bits: Bit:
0 = Safety Function Fault
1 = Safety Reset Request
2 = Restart Required
3 = STO Active
4 = Torque Disabled
5 = SBC Active
6 = Brake Engaged
7 = SS1 Active
8 = SS2 Active
9 = SOS Active
10 = SOS Standstill
11 = SMT Active
12 = SMT OVertemp
41 (0x29) Safety Stop Faults Collection of Safety Stop Fault bits: Bit:
2 = Feedback Fault
3 = STO Fault
4 = SS1 Fault
5 = SS2 Fault
6 = SOS Fault
7 = SBC Fault
8 = SMT Fault
Explicit Messages Use explicit messages to communicate with a drive and obtain additional fault,
status, or configuration information that is not available in the Safety I/O Tag
structure. Attribute data is useful for additional diagnostic information.
IMPORTANT Explicit messages must not be used for any safety related function.
backplane and <port> is the number of the backplane port where the 20-750-
S4 option is installed. This can be port 4, 5, or 6. In CIP Motion applications
the 20-750-S4 must be installed in port 6.
Parameter Data
This appendix provides a description of the device parameters and host config
parameters.
Parameters and Settings in a This section describes the status parameters and their values in numerical
order.
Linear List
Device Parameters
You are not able to create datalinks to these Device parameters. If you need to
read them, you could use a message instruction.
Table 105 - Device Config Parameters
No. Display Name Values Description Data Type
Full Name
Description
1 Identity Status “Owned" (0) Indicates whether the safety option DWORD
Describes the status of module has an owner.
the module. 1 = owned
0 = not owned
“Configured" (1) Indicated whether the safety option
module has a configuration other than
out-of-box.
1 = configured
0 = out of box configuration
“Min Rec Flt" (8) If set (1), the safety option module has
detected a minor recoverable fault. The
device does not enter a faulted state.
“Min Unr Flt" (9) If set (1), the safety option module has
detected a minor unrecoverable fault.
The device does not enter a faulted state.
“Maj Rec Flt" (10) If set (1), the safety option module has
detected a major recoverable fault and is
in the major recoverable fault state.
“Maj Unr Flt" (11) If set (1), the safety option module has
detected a major unrecoverable fault is
in the major unrecoverable fault state.
17 Output Alarm “No Alarm” (0) No alarm reported by the output BYTE
The alarm being instance.
reported by the output
instance specified in “Config” (1) The output instance's configuration is
parameter 16 - invalid.
(Output Alarm Indx). “OverCurrent” (2) Current exceeded maximum on the
output.
“ShortCircuit” (3) The output is stuck low.
“Stuck High” (4) The output is stuck high.
“Partner Err” (5) The Dual Channel function controlling
this instance has detected a fault in the
associated output instance.
“Relay Err” (6) Read back signal error during an
expected high state.
“Relay Fail” (7) The output relay has failed.
“Dual Ch” (8) The output values of the associated dual
channel instance are not the same.
“Cross Conn” (9) The outputs of the associated dual
channel instance are cross-connected.
20 Enc1 Position DWORD
The position count
being reported by the
primary encoder.
21 Enc1 Velocity REAL
Primary encoder
velocity in units/s. The
units of this value are
of the type reported by
parameter 24 - (En1
Unit).
Host Parameters 11…14 configure how the PowerFlex® 755 drive reacts to a
change in the status of the safety functions. These configuration parameters are
not part of the ‘Safety’ configuration, they are part of the PowerFlex 755 drive
configuration.
Read-Write
No. Display Name Values
Data Type
Full Name
Description
1 Reserved
2 Reserved
Read-Write
Data Type
Full Name
Description
Brak Engage
Safety Reset
Trq Disabled
SOS StndStil
Conn Closed
Safety Fault
Neg Motion
Restart Req
Pos Motion
SSM Active
SMT Active
SCA Status
SCA Active
SOS Active
SBS Active
SLA Active
SLP Status
SS2 Active
SS1 Active
SLP Active
SLS Active
SSM Limit
SDI Active
SLA Limit
Conn Idle
STO Activ
SLS Limit
Reserved
Reserved
Reserved
SDI Limit
Default 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Bit 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Bit 0 “Safety Fault” – Indicates the existence of a safety fault, where 0 = no fault and 1 = faulted.
Bit 1 “Safety Reset” – A transition from 0 to 1 resets the safety function.
Bit 2 “Restart Req” – Indicates whether a manual restart is required following a stop function, where 0 = restart not required and 1 = restart required.
Bit 3 “STO Active” – Indicates whether STO control is active, where 0 = Not Active (Permit Torque) and 1 = Active (Disable Torque).
Bit 4 “Trq Disabled” – Displays the status of STO control, where 0 = Torque Permitted and 1 = Torque Disabled.
Bit 5 “SBC Active” – Indicates whether the Safe Brake Control function is active, where 0 = Not Active and 1 = Active.
Bit 6 “Brak Engage” – Indicates whether the Safe Brake Control function has engaged the brake, where 0 = Brake Released and 1 = Brake Engaged.
Bit 7 “SS1 Active” – Indicates whether the Safe Stop 1 function is active, where 0 = Not Active and 1= Active.
Bit 8 “SS2 Active” – Indicates whether the Safe Stop 2 function is active, where 0 = Not Active and 1 = Active.
Bit 9 “SOS Active” – Indicates whether the Safe Operating Stop function is active, where 0 = Not Active and 1 = Active.
Bit 10 “SOS StndStil” – Indicates whether the Safe Operating Stop function is comparing the actual feedback value to the set point, where
0 = Not comparing and 1 = Comparing.
Bit 11 “SMT Active” – Reserved for future use. Always 0.
Bit 12 “SMT Ovr Temp” – Reserved for future use. Always 0.
Bit 16 “SSM Active” – Indicates if the Safe Speed Monitoring function is active, where 0 = Not Active and 1 = Active.
Bit 17 “SSM Limit” – Indicates the status of the Safe Speed Monitoring function, where 0 = Speed is below limit and 1 = Speed is above limit.
Bit 18 “SLS Active” – Indicates if the Safely Limited Speed function is active , where 0 = Not Active and 1 = Active.
Bit 19 “SLS Limit” – Indicates if the speed exceeds the SLS limit, where 0 = Speed within limit and 1 = Speed exceeds limit.
Bit 20 “SLA Active” – Reserved for future use. Always 0.
Bit 21 “SLA Limit” – Reserved for future use. Always 0.
Bit 22 “SDI Active” – Indicates if the Safe Direction function is active, where 0 = Not Active and 1 = Active.
Bit 23 “SDI Limit” – Indicates if the Safe Direction function has detected movement in the prohibited direction, where 0 = Direction OK and
1 = Prohibited Direction.
Bit 24 “Pos Motion” – The feedback device indicates a positive position value.
Bit 25 “Neg Motion” – The feedback device indicates a negative position value.
Bit 26 “SCA Active” – The Safe Cam function is active.
Bit 27 “SCA Status” – The Safe Cam function has detected a motor shaft position outside the specified range.
Bit 28 “SLP Active” – The Safety Limited Position function is active.
Bit 29 “SLP Status” – The Safely Limited Position function has detected a position outside the specified range
Bit 30 “Conn Closed” – No active connection of an output assembly from the safety controller exists.
Bit 31 “Conn Idle” – An active output assembly connection exists but the safety controller is in Program mode.
Read-Write
Data Type
Full Name
Description
Fdbk Fault
Options
Core Fault
SSM Fault
SMT Fault
SCA Fault
SOS Fault
VAL Fault
SBC Fault
SLA Fault
STO Fault
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
Reserved
SS2 Fault
SS1 Fault
SLP Fault
SLS Fault
SDI Fault
Default 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Bit 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Reserved
SFX Fault
Options
Default 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Bit 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Bit 1 “SFX Fault” – The Safety Feedback Interface Add On Instruction has experienced a fault.
Read-Write
Data Type
Full Name
Description
Numerics cycle
20-750-S 16 interpolation 154
resolution 154
20-750-S1 16
20-750-S3 16
D
diagnostic 206
A cosine 27
actions category 152 encoder 25
ADC 112 hiperface 27
additional resources 13 digital AqB encoder 27
assembly tag discrepancy 162
input 240 checking 157
output 242 error 48
attribute testing 22
time 162
feedback 245
automatic device configuration. See ADC documentation
axis tag 180 additional resources 13
DPI parameter 48, 59
drive replacement 130
C integrated safety 130
drive safety instruction 93
certification
drive safety instructions
TÜV Rheinland 93
checklist. See validation checklist adding instruction 95
example 95
CIP messaging 48, 59 homing 101
circuit error 47, 58 pass-through data 98
cold start type 152 SFX instruction 99
Compact GuardLogix 5380 controller 17, 93, tab 94
DS1 195, 196
143, 150, 167, 176
DS2 195, 196
compatible drive 17
DS3 195, 197
complementary mode 43
DS4 195, 197
configuration
dual channel
error 47, 58
ownership 126, 130, 168 discrepancy error 58
configure error 48
mode 51, 53, 164
action 152 dual feedback 22
discrepancy checking 157
general 145 configuration 16
module monitoring 22, 148, 155, 157
definition 146 dual velocity check 157
motion safety instance 149 duplicate device number 130
primary feedback 153
safety connection 147
safety input 149 E
safety output 149
effective resolution 154
scaling 156
secondary feedback 155 electronic keying 110, 146
STO 158 encoder diagnostic 25
configure always feature 169 encoder input frequency diagnostic 26
connection environmental pollution degree 235
idle 69 equivalent mode 42
idle action 68, 152 explicit message 183
loss 68
external pulse test 37
loss action 68, 152
reaction time limit 151 external pulse tests 37
continuous mode 20
controller-based
instruction 93
F
cosine diagnostic 27 failure analysis 28
falling edge K
reset 130 kit catalog number
signal 130
fault 203 dual incremental encoder module (20-750-
DENC-1) 33
actions 152
EMC Core (20-750-EMCSSM1-F8) 34
code 211 205
universal feedback module (20-750-UFB-1)
message 205
name 198 33
recovery 49, 60
safety core 199 L
SS1 201
SS2, SOS, SBC, SLS, SLP, SDI 202 latch error time 52, 53
STO 200 LED
feedback module status 196
attribute 245 motion output status 197
resolution 156 network status 196
firmware revision 12 Logix Designer application 104, 145, 170, 174,
197
Logix 5000 127
G low demand mode 20
gate firing circuit 15
general 145
GuardLogix 5580 controller 17, 93, 103, 143, M
150, 167, 176 mapping
safety tag 126
maximum
H acceleration 154
hardware enable jumper 33 diagnostic 25
hazard prevention 19 encoder input frequency diagnostic 26
speed 154
high demand mode 20 speed limit diagnostic 25
hiperface diagnostic 27 mean time to failure spurious 23
homing 101 mechanical
brake 19
force
I back pressure 16
IGBT 15 suspended load 16
failure 16 mission time 21
input module
assembly tag 45, 46, 47, 55, 56, 57, 62, 63, definition 146
240 status 195
latch error time 39 monitored SS1 79, 159, 160
input valid (safety) 46 definition 10
integrated motion
STO bypass 170 and safety connection 179
STO mode connection 179
drive replacement 130 connection axis tag 180
STO state reset 204 output status 195
ISA TR-84 23 safety instance 149, 176, 178
task 176, 178
motion direct command
J STO bypass 170
warning message 171
jumper location
MSG command 214
Powerflex 755 drive 31
PowerFlex 755T drive product 31
jumper setting 29 N
network delay multiplier 151
network status 195
no test pulse mode 85
not used 85, 162, 163, 164
O release note 12
off state 16 replace 168
PowerFlex 755 drive
off-delay function 50
on an integrated safety network 130
on-delay function 49 requested packet interval. See RPI
one shot falling instruction. See OSF reset ownership 126
instruction resolution unit 154
OSF instruction 130 response time 51
out-of-box state restart type 152
restore 214 risk assessment 18, 19, 29
verify 214
RPI 113, 149, 150, 151
output
assembly tag 61, 65, 70, 76, 83, 86
output assembly tag 242 S
output monitor value 56
Safe Break Control. See SBC
safe direction instruction. See SDI
P safe operating speed. See SOS
diagnostic parameter safe stop function
safety state 207 See also SS1, SS2
safety status 207 safe stopping action source 165
safety fault 209 safe torque off. See STO
parameter safeguarding devices 19
host 259 safely-limited position instruction. See SLP
partner channel error 59 safely-limited speed. See SLS
pass-through data 98, 129, 182, 183 safety
and integrated motion 98 analysis 29
in standard I/O mode 96 brake 91
PFD 20, 21, 22 category 233
PowerFlex 755 drive 21 connection 147, 183
PowerFlex 755T drive product 21 control state 214
PFH 20, 21, 22 core fault 199
definition 11 DeviceID 130
PowerFlex 755 drive 21 digital output 50, 60
PowerFlex 755T drive product 21 enable jumper 33
polarity 154 fault 195
pollution degree 235 feedback 203
feedback fault 203
port 148
function 177, 178
position 156 safety input 37
deadband 158 function operation 128
unit 156 function testing 29
power supply output 163 input 37, 149
mode 61 input alarm 47
primary input alarm recovery 49
encoder 178 input assembly tag 66
feedback 153, 156 input status 45
probability of dangerous failure per hour. input valid 46
input value 45
See PFH jumper 31
probability of failure on demand. See PFD network number
product compatibility and download center
12
proof
test interval 20
testing 18
pulse test output 163
R
ratio 158
redundant channel safety device 41
T
tap mode 17
test output 162
mode 61
ready 63
status 62
test pulse 50, 51
test pulses 164
test pulses mode 86
time 156, 158
timed
SS1 78, 159
SS1 definition 10
timeout multiplier 151
TÜV Rheinland 18
type 162
U
units 154
used
as standard input 162
no test pulse mode 85
test pulses mode 86
with test output 162
with test pulses 164
without pulse test 164
without test output 162
V
validation checklist 218, 220, 223, 225, 226,
228, 229, 231
velocity average time 154
velocity deadband 158
voltage monitor 154
W
Wait w Trq 214
waiting 214
warning icon 174
wiring 29
with test output 162
without test output 162
without test pulse 164
Z
zero crossing detection diagnostic 28
Notes:
Technical Support Center Find help with how-to videos, FAQs, chat, user forums, and product notification updates. rok.auto/support
Knowledgebase Access Knowledgebase articles. rok.auto/knowledgebase
Local Technical Support Phone Numbers Locate the telephone number for your country. rok.auto/phonesupport
Literature Library Find installation instructions, manuals, brochures, and technical data publications. rok.auto/literature
Product Compatibility and Download Center Download firmware, associated files (such as AOP, EDS, and DTM), and access product rok.auto/pcdc
(PCDC) release notes.
Documentation Feedback
Your comments help us serve your documentation needs better. If you have any suggestions on how to improve our
content, complete the form at rok.auto/docfeedback.
At the end of life, this equipment should be collected separately from any unsorted municipal waste.
Rockwell Automation maintains current product environmental compliance information on its website at rok.auto/pec.
Allen-Bradley, Connected Components Workbench, CompactLogix, ControlLogix, DeviceLogix, DPI, Expanding Human Possibilities, Integrated Architecture, Guard I/O, GuardLogix, Logix 5000,
PowerFlex, QuickView, Rockwell Automation, Rockwell Software, Studio 5000, Studio 5000 Logix Designer, and TotalFORCE are trademarks of Rockwell Automation, Inc.
EtherNet/IP is a trademark of ODVA, Inc.
Trademarks not belonging to Rockwell Automation are property of their respective companies.
Rockwell Otomasyon Ticaret A.Ş. Kar Plaza İş Merkezi E Blok Kat:6 34752, İçerenköy, İstanbul, Tel: +90 (216) 5698400 EEE Yönetmeliğine Uygundur