GuardLogix Programming Specification.

DCP 16
Version 0.4 - Draft.

David Green Page 1 of 17 Date Issued: 23.10.2006

GIS1 Item Number: Date Revised: 17.03.2008
GIS2 Classification: Proprietary Retention Start Date:
 Contents.

Revisions. ............................................................................................................................................................... 3
Preface. ................................................................................................................................................................... 4
1. General. .......................................................................................................................................................... 4
2. GuardLogix Configuration ............................................................................................................................. 5
2.1 Naming Conventions................................................................................................................................ 5
2.1.1 Processor Naming ........................................................................................................................... 5
2.1.2 IO Module Naming......................................................................................................................... 5
2.1.2.1 DeviceNet ....................................................................................................................................... 5
2.1.2.2 EtherNet/IP ..................................................................................................................................... 6
2.1.3 Routine Names................................................................................................................................ 6
2.1.4 Device Labelling............................................................................................................................. 7
2.1.4.1 DeviceNet ....................................................................................................................................... 7
2.1.4.2 Ethernet/IP ...................................................................................................................................... 7
2.1.5 Mapped Naming ............................................................................................................................. 7
2.2 Program Configuration............................................................................................................................. 9
2.2.1 A program named 'SafetyProgram' should be configured as a Safety Task................................... 9
2.2.2 Program Flow ............................................................................................................................... 11
3. Safety Function Blocks................................................................................................................................. 14
3.1 Emergency Stop ..................................................................................................................................... 14
3.2 Redundant Output .................................................................................................................................. 14
3.3 Light Curtain .......................................................................................................................................... 14
3.4 Enable Pendant....................................................................................................................................... 14
3.5 Redundant Input ..................................................................................................................................... 14
4. Diagnostics ................................................................................................................................................... 15
4.1 PLC Logic................................................................................................................................................... 15
4.2 HMI ............................................................................................................................................................ 16
Appendix. ............................................................................................................................................................. 17
Reference documents:....................................................................................................................................... 17

David Green Page 2 of 17 Date Issued: 23.10.2006

GIS1 Item Number: Date Revised: 17.03.2008
GIS2 Classification: Proprietary Retention Start Date:
Revisions.
No Chapter Reason Description V Date Revisor
1 Original - Draft 0.1 23/10/2006 David Green
2 Module naming change 0.2 20/12/2006 David Green
3 4 CMZ Faults Modified 0.3 28/02/2007 David Green
4 Graphics changed to represent
DCP16
5 2.1.5 Standard to Safety mapping
6 2.1.2 Introduced Ethernet/IP 17/03/2008 David Green
7 2.1.4 Introduced Ethernet/IP 17/03/2008 David Green

David Green Page 3 of 17 Date Issued: 23.10.2006

GIS1 Item Number: Date Revised: 17.03.2008
GIS2 Classification: Proprietary Retention Start Date:
Preface.
1. General.
Solid state equipment has operational characteristics differing from those of electromechanical equipment.
Safety Guidelines for the Application, Installation and Maintenance of Solid State Controls (Publication SGI-1.1
available from your local Rockwell Automation sales office or online at http://www.ab.com/manuals/gi)
describes some important differences between solid state equipment and hard-wired electromechanical devices.
Because of this difference, and also because of the wide variety of uses for solid state equipment, all persons
responsible for applying this equipment must satisfy themselves that each intended application of this equipment
is acceptable.
In no event will Ford Motor Company 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,
Ford Motor Company cannot assume responsibility or liability for actual use based on the examples and
diagrams.

David Green Page 4 of 17 Date Issued: 23.10.2006

GIS1 Item Number: Date Revised: 17.03.2008
GIS2 Classification: Proprietary Retention Start Date:
2. GuardLogix Configuration
2.1 Naming Conventions
2.1.1 Processor Naming
_ P P N G p

PLC Number
1...9

IE Group
A..Z
e.g
Y = Respot

IE Number
1...9

Project or Plant
i.e.
1M = Mondeo - Genk

UnderScore

2.1.2 IO Module Naming

2.1.2.1 DeviceNet
SafetyNode _ xx

Node Number
00 - 62
UnderScore
Text - SN (SafetyNode)

David Green Page 5 of 17 Date Issued: 23.10.2006

GIS1 Item Number: Date Revised: 17.03.2008
GIS2 Classification: Proprietary Retention Start Date:
 2.1.2.2 EtherNet/IP
SafetyNode _ xxx

Node Number
001-254 (4th Segment Address)
UnderScore
Text - SN (SafetyNode)

2.1.3 Routine Names

S A x x _ Description

EmergencyStops
SafetyDoors
LightCurtains
AxisControl

Under Score

Safety Area Number

00 = Global
01 = Safety Area 01
...
99 = Safety Area 99

SA = Safety Area

David Green Page 6 of 17 Date Issued: 23.10.2006

GIS1 Item Number: Date Revised: 17.03.2008
GIS2 Classification: Proprietary Retention Start Date:
2.1.4 Device Labelling

2.1.4.1 DeviceNet
Each IO Module has to have a label within the direct vicinity, but not attached to the module stating
its NODE address.
e.g.

NODE 01

2.1.4.2 Ethernet/IP
Each IO Module has to have a label within the direct vicinity, but not attached to the module stating
its IP Address address.
e.g.

136.129.20.1

2.1.5 Mapped Naming

When it is required to use a Tag that has been sourced within the 'Standard Part' of the program within the
'Safety Part' then it must be 'mapped'.
By selecting 'Logic' > ''Map safety Tags…' you can define these.
Any tag that is required must use the following naming convention.

Standard Part Safety Part Example {name}

ToSafety_{name} FromStandard_{name} Reset
NoDumpOutput

David Green Page 7 of 17 Date Issued: 23.10.2006

GIS1 Item Number: Date Revised: 17.03.2008
GIS2 Classification: Proprietary Retention Start Date:
Example:
Standard Part

MAP Data

Safety Part

David Green Page 8 of 17 Date Issued: 23.10.2006

GIS1 Item Number: Date Revised: 17.03.2008
GIS2 Classification: Proprietary Retention Start Date:
 2.2 Program Configuration
2.2.1 A program named 'SafetyProgram' should be configured as
a Safety Task.

David Green Page 9 of 17 Date Issued: 23.10.2006

GIS1 Item Number: Date Revised: 17.03.2008
GIS2 Classification: Proprietary Retention Start Date:
David Green Page 10 of 17 Date Issued: 23.10.2006
GIS1 Item Number: Date Revised: 17.03.2008
GIS2 Classification: Proprietary Retention Start Date:
2.2.2 Program Flow
2.2.1.1 The routine named 'MainRoutine' should be configured as the Main Routine from
with the 'Safety Program' Configuration window.

David Green Page 11 of 17 Date Issued: 23.10.2006

GIS1 Item Number: Date Revised: 17.03.2008
GIS2 Classification: Proprietary Retention Start Date:
 2.2.1.2 All routines will be called from within the 'MainRoutine'. E.g.

David Green Page 12 of 17 Date Issued: 23.10.2006

GIS1 Item Number: Date Revised: 17.03.2008
GIS2 Classification: Proprietary Retention Start Date:
 2.2.1.3 Example Contents of an 'Emergency Stop' Routine:

David Green Page 13 of 17 Date Issued: 23.10.2006

GIS1 Item Number: Date Revised: 17.03.2008
GIS2 Classification: Proprietary Retention Start Date:
 3. Safety Function Blocks
The Attacheed documentation has been taken directly from the online Help of RSLOGIX V16.

3.1 Emergency Stop

3.2 Redundant Output

3.3 Light Curtain

3.4 Enable Pendant

3.5 Redundant Input

David Green Page 14 of 17 Date Issued: 23.10.2006

GIS1 Item Number: Date Revised: 17.03.2008
GIS2 Classification: Proprietary Retention Start Date:
 4. Diagnostics
4.1 PLC Logic
Each device will be diagnosed individually within the 'Non-Safety' area of the program.

e.g. CMZ area (Constantly Monitored Critical Faults)

David Green Page 15 of 17 Date Issued: 23.10.2006

GIS1 Item Number: Date Revised: 17.03.2008
GIS2 Classification: Proprietary Retention Start Date:
 4.2 HMI
The position of each device and the 'General Status' of the device should be displayed on an overview screen.
Showing Red when in fault.
e.g.

In addition a screen should show the more detailed data in a matrix format. This screen should be called from
the previous overview screen.
e.g.

David Green Page 16 of 17 Date Issued: 23.10.2006

GIS1 Item Number: Date Revised: 17.03.2008
GIS2 Classification: Proprietary Retention Start Date:
Appendix.
Reference documents:
GuardLogix User Manual Catalog Numbers: 1756-L61S, 1756-L62S, 1756-LSP.
DeviceNet Safety I/O Modules : Catalog Number 1791DS-IB12,1791DS-IB8XOB8, 1791DS-IB4XOW4

David Green Page 17 of 17 Date Issued: 23.10.2006

GIS1 Item Number: Date Revised: 17.03.2008
GIS2 Classification: Proprietary Retention Start Date: