3820 Tt4 App Principiantes

Technical Training
Turbotronic™ 4 Applied Principles
Student Workbook
Course No. 3820
Turbotronic™ 4 Applied Principles
Student Workbook
3820
Course No. 3820
Technical Training
Technical Training
Turbotronic™ 4 Applied
Principles
Student Workbook
Course No. 3820
Solar Turbines Incorporated

P.O. Box 85376
San Diego, CA 92186–5376
Solar, Saturn, Centaur, Mars, Mercury, Taurus, Titan, SoLoNOx, and Turbotronic are
trademarks of Solar Turbines Incorporated. Cat and Caterpillar are trademarks of Caterpillar Inc.
Specifications subject to change without notice. Printed in the U.S.A.
PUBLICATION NUMBER: TR3820

PROPRIETARY NOTICE
The contents of this technical training instructions manual are proprietary
data of Solar Turbines Incorporated, a subsidiary of Caterpillar Inc. This
material is protected under U.S. copyright law. All reproduction is prohibited
without the express written approval of Solar Turbines Incorporated.
© 2007 Solar Turbines Incorporated. All rights reserved.

Solar Technical Training CONTENTS
CONTENTS
Chapter Page
LIST OF ILLUSTRATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
LIST OF TABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii
1 LESSON 1 - INTRODUCTION TO SOFTWARE APPLICATIONS

AND TOOLS
OBJECTIVES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 1.1
INTRODUCTION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 1.2
ROCKWELL SOFTWARE APPLICATIONS. . . . . . . . . . . . . . . . . . . . . .. . 1.3
RSLogix 5000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 1.4
RSLinx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 1.5
RSNetworx for ControlNet . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 1.6
SOLAR TURBOTRONIC FIELD TOOLS . . . . . . . . . . . . . . . . . . . . . . .. . 1.7
2 LESSON 2 - LOADING A PROGRAM TO THE PROGRAMMING

TERMINAL
OBJECTIVES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 2.1
PROJECT CD AND FOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 2.2
SUBSYSTEM FOLDER CONTENTS. . . . . . . . . . . . . . . . . . . . . .. . 2.3
PROJECT TOOLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 2.5
TT4 Field Distribute Tool . . . . . . . . . . . . . . . . . . . . . . .. . 2.5
Updating the Revision . . . . . . . . . . . . . . . . . . . . . . . .. . 2.6
3 LESSON 3 - OFFLINE PROGRAM MONITORING

OBJECTIVES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 3.1
INTRODUCTION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 3.2
OPENING THE RSLOGIX 5000 PROGRAM . . . . . . . . . . . . . . . . . . . . .. . 3.3
RSLOGIX 5000 DISPLAY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 3.5
Toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 3.5
Controller Organizer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 3.5
Quick Pane Properties View. . . . . . . . . . . . . . . . . . . . . . . . . . .. . 3.5
Ladder/Function Block Window . . . . . . . . . . . . . . . . . . . . . . . . .. . 3.5
Results Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 3.6
Standard Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 3.7
Online Toolbars. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 3.8
Path Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 3.8
New Component Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 3.9
Language Element Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 3.9
Ladder Edit Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 3.10
Language Editor Editing Toolbar . . . . . . . . . . . . . . . . . . . . . . . .. . 3.10
Ladder Common Logic Toolbar . . . . . . . . . . . . . . . . . . . . . . . . .. . 3.10
Help Menu Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 3.11
RSLogix Version 13.xx Features . . . . . . . . . . . . . . . . . . . . . . . .. . 3.13
3820 © 2007 Solar Turbines Incorporated. All rights reserved. v

CONTENTS Solar Technical Training
Chapter Page
4 LESSON 4 RSLOGIX 5000 FAMILIARIZATION

OBJECTIVES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 4.1
INTRODUCTION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 4.1
CONFIGURING SCREEN DISPLAYS . . . . . . . . . . . . . . . . . . . . . . . . .. . 4.2
WINDOW CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 4.2
Font Configuration and Other User Preferences . . . . . . . . . . . . . . . .. . 4.3
STUDENT EXERCISE - CUSTOMIZING THE DISPLAY . . . . . . . . . . . . . .. . 4.5
MENU AND TOOLBAR FUNCTIONS . . . . . . . . . . . . . . . . . . . . . . . . .. . 4.7
File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 4.7
Edit Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 4.8
View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 4.12
Search Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 4.14
Logic Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 4.22
Communications Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 4.23
Going Online Options and Definitions . . . . . . . . . . . . . . . . . . . . .. . 4.24
Controller Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 4.25
Tools Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 4.25
SUMMARY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 4.28
5 LESSON 5 SOLAR PROJECT ORGANIZATION

OBJECTIVES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 5.1
INTRODUCTION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 5.2
PROJECT CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 5.2
Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 5.3
Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 5.4
Unscheduled Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 5.5
Creating New Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 5.5
PROGRAMMING EXERCISE #1 - CREATING NEW PROGRAMS . . . . . . . . .. . 5.7
PROGRAM TYPES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 5.9
I/O Control Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 5.10
Package State Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 5.11
Interface Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 5.12
Framework Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 5.12
ROUTINES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 5.13
Routine Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . .. . 5.13
Main Routine Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 5.14
Routine Comments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 5.15
Routine Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 5.16
Inhibiting a Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 5.17
vi © 2007 Solar Turbines Incorporated. All rights reserved. 3820

Chapter Page
FUNCTION BLOCK ROUTINES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.18
6 LESSON 6 - SOLAR LOGIC FAMILIARIZATION

OBJECTIVES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 6.1
INTRODUCTION TO TAGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 6.2
TAG DEFINITION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 6.3
Tag Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 6.3
Tag Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 6.3
TAG DATA TYPE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 6.5
Pre-Defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 6.5
Module-Defined Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 6.6
User-Defined Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 6.7
CONTROLLER SCOPED TAGS . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 6.8
I/O Interface Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 6.9
Base Tags and Alias Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 6.12
STUDENT EXERCISE – ALIAS AND BASE TAGS . . . . . . . . . . . . . . . . .. . 6.15
PROGRAMMING EXERCISE #3 - CREATING I/O TAGS . . . . . . . . . . . . . .. . 6.17
HMI TAGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 6.18
HMI_Alarm Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 6.19
HMI Shutdown Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 6.21
HMI_Status Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 6.22
HMI_Discrete_Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 6.23
HMI Analog Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 6.24
HMI_Snapshot_Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 6.25
Program-Scoped HMI Tags . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 6.25
HMI ALARM AND SHUTDOWN TAGS . . . . . . . . . . . . . . . . . . . . . . . .. . 6.27
HMI STATUS TAGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 6.30
INTERNAL PROGRAM SCOPED TAGS . . . . . . . . . . . . . . . . . . . . . . .. . 6.31
TIMERS AND COUNTERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 6.32
PROGRAMMING EXERCISE #4 - CREATING HMI TAGS. . . . . . . . . . . . . .. . 6.33
ANALOG DEVICE PROGRAMMING . . . . . . . . . . . . . . . . . . . . . . . . .. . 6.35
Scaling of Analogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 6.35
Analog Input Scaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 6.35
SCALING ANALOGS IN RSLOGIX . . . . . . . . . . . . . . . . . . . . . . . . . .. . 6.41
Tag Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 6.41
UDT Analog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 6.41
Moving Analogs to the Display . . . . . . . . . . . . . . . . . . . . . . . . .. . 6.44
Transmitter Fail Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 6.44
3820 © 2007 Solar Turbines Incorporated. All rights reserved. vii

Chapter Page
PROGRAMMING EXERCISE #5 - CREATING ANALOG TAGS . . . . . . . . . .. . 6.47

PROGRAM CONSTANTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 6.49
PROGRAMMING EXERCISE #6 - CREATING PROGRAM CONSTANTS . . . . .. . 6.51
PROGRAM RESPONSE TAGS . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 6.52
7 LESSON 7 - EDITING A PROJECT OFFLINE

OBJECTIVES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1
INSTRUCTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1
8 LESSON 8 - HARDWARE AND SOFTWARE INTERFACE

/ TROUBLESHOOTING
OBJECTIVES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 8.1
TURBINE LOGIC EXAMPLE - LUBE OIL TANK HEATER . . . . . . . . . . . . .. . 8.2
SYSTEM COMPONENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 8.2
BASIC LOGICAL FUNCTIONS . . . . . . . . . . . . . . . . . . . . . . . . .. . 8.2
viii © 2007 Solar Turbines Incorporated. All rights reserved. 3820

Chapter Page
SAMPLE PROGRAM PURPOSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.6

ROUTINE PURPOSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.7
STUDENT EXERCISE - SAMPLE ROUTINE FUNCTION . . . . . . . . . . . . . . . . 8.8
RUNG FUNCTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.9
STUDENT EXERCISE - ROUTINE FUNCTIONS . . . . . . . . . . . . . . . . . . . . . 8.10
HARDWARE-SOFTWARE INTERFACE. . . . . . . . . . . . . . . . . . . . . . . . . . 8.11
STUDENT EXERCISE - HARDWARE / SOFTWARE INTERFACE . . . . . . . . . . . 8.14
LOGIC FAMILIARIZATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.15
STUDENT EXERCISE - FUEL PROGRAM FAMILIARIZATION . . . . . . . . . . . . 8.16
STUDENT EXERCISE - ANALOG DEVICE PROGRAMMING FAMILIARIZATION. . 8.20
STUDENT EXERCISE - TROUBLESHOOTING . . . . . . . . . . . . . . . . . . . . . 8.23
9 LESSON 9 - RSLOGIX5000 ONLINE FUNCTIONS

OBJECTIVES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 9.1
INTRODUCTION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 9.1
CONFIGURING COMMUNICATION DRIVERS . . . . . . . . . . . . . . . . . . . .. . 9.2
RS232 Serial Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 9.2
ControlNet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 9.2
Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 9.2
STUDENT EXERCISE - CONFIGURING DRIVERS . . . . . . . . . . . . . . . . .. . 9.3
RS232 SERIAL LINK DRIVER CONFIGURATION . . . . . . . . . . . . . . . . . .. . 9.3
CONTROLNET DRIVER CONFIGURATION . . . . . . . . . . . . . . . . . . . . .. . 9.6
ETHERNET DRIVER CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . .. . 9.8
SETTING AN IP ADDRESS USING TT IP CONFIG . . . . . . . . . . . . . . . . .. . 9.10
STUDENT EXERCISE - CHANGING AN ETHERNET MODULE IP ADDRESS . .. . 9.12
GOING ONLINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 9.15
DOWNLOADING. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 9.20
RUN MODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 9.23
UPLOADING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 9.25
RECOMMENDED PROCEDURES . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 9.27
No Project In The Controller. . . . . . . . . . . . . . . . . . . . . . . . . . .. . 9.27
Project In The Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 9.27
3820 © 2007 Solar Turbines Incorporated. All rights reserved. ix

Chapter Page
FORCING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 9.28
BIT FORCING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 9.29
STUDENT EXERCISE - BIT FORCING . . . . . . . . . . . . . . . . . . . . . . . .. . 9.32
FORCING ANALOG INPUT VALUES . . . . . . . . . . . . . . . . . . . . . . . . .. . 9.33
FORCING ANALOG OUTPUT VALUES . . . . . . . . . . . . . . . . . . . . . . .. . 9.34
STUDENT EXERCISE - FORCING ANALOGS. . . . . . . . . . . . . . . . . . . .. . 9.36
TOGGLE FUNCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 9.37
STUDENT EXERCISE - TOGGLING. . . . . . . . . . . . . . . . . . . . . . . . . .. . 9.38
LOCKING THE CONTROLLER . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . 9.39
INTRODUCTION TO ONLINE EDITING . . . . . . . . . . . . . . . . . . . . . . . .. . 9.40
ONLINE EDITS SCREENS FOR RSLOGIX 5000 VERSION 13 . . . . . . . . . .. . 9.44
APPENDIX
A APPENDIX A - PROJECT EDITING EXERCISE
B APPENDIX B - BASIC INSTRUCTION SET
C APPENDIX C - ANALOG MODULE SCALING INFO
D APPENDIX D - COMMON ABBREVIATIONS AND ENGINEERING UNITS
x © 2007 Solar Turbines Incorporated. All rights reserved. 3820

LIST OF ILLUSTRATIONS
Figure Page
1.1 RSLogix 5000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4
1.2 RSLinx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.5
1.3 RSNetworx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.6
1.4 Solar Turbotronic Field Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.7
2.1 Field Employee Support Database . . . . . . . . . . . . . . . . . . . . . . . . 2.2
2.2 Project Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3
2.3 Subsystem Folder Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3
2.4 Project ACD File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4
2.5 TT4 Field Distribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5
2.6 Distributing Job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6
2.7 Updating Revision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.7
2.8 Rolling Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.8
2.9 Comms Available. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.8
2.10 Continue With Roll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.8
2.11 History File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.9
2.12 Controller Tags Reminder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.9
2.13 New Revision. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.10
3.1 Selecting the Project Revision . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3
3.2 RSLogix Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4
3.3 Start RSLogix 5000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4
3.4 RSLogix Main Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6
3.5 Available Toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7
3.6 Standard Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7
3.7 Online Toolbars. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.8
3.8 Path Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.8
3820 © 2007 Solar Turbines Incorporated. All rights reserved. xi

Figure Page
3.9 New Component Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.9
3.10 Language Element Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.9
3.11 Ladder Edit Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.10
3.12 Language Editor Editing (Bookmark) Toolbar . . . . . . . . . . . . . . . . . . 3.10
3.13 Ladder Common Logic Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . 3.10
3.14 Online Books . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.11
3.15 Instruction Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.12
3.16 Version 13.xx Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.13
4.1 Window Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2
4.2 Modifying Fonts & Colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3
4.3 Version 13 Tools Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4
4.4 File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.7
4.5 Generate Report Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.8
4.6 Edit Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.8
4.7 Controller Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.9
4.8 Insert Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.10
4.9 Version 13 Edit Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.11
4.10 Export Rung . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.11
4.11 View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.12
4.12 Output Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.12
4.13 Verification Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.13
4.14 Watch Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.13
4.15 Version 13 Search Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.14
4.16 Version 10 Search Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.14
4.17 Find Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.15
4.18 Find Next Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.16
xii © 2007 Solar Turbines Incorporated. All rights reserved. 3820

Figure Page
4.19 Find All Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.17
4.20 Replace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.18
4.21 Go To Cross Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.19
4.22 Cross Reference Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.19
4.23 Go To Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.20
4.24 Find Icons in Main Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.20
4.25 Browse Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.21
4.26 Logic Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.22
4.27 Communications Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.23
4.28 Select Recent Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.23
4.29 Tools Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.25
4.30 Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.26
4.31 Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.27
5.1 Project Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2
5.2 Task Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3
5.3 Program Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4
5.4 Routines Within the Lube Program . . . . . . . . . . . . . . . . . . . . . . . . 5.13
5.5 Designating the Main Routine. . . . . . . . . . . . . . . . . . . . . . . . . . . 5.14
5.6 Main Routine Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.15
5.7 Routine Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.16
5.8 Inhibiting a Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.17
5.9 Generator Routine Listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.18
5.10 Typical Function Block Routine . . . . . . . . . . . . . . . . . . . . . . . . . . 5.19
6.1 Controller and Program Tag Databases . . . . . . . . . . . . . . . . . . . . . 6.4
6.2 Pre-Defined Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5
6.3 Module Defined Data Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.7
3820 © 2007 Solar Turbines Incorporated. All rights reserved. xiii

Figure Page
6.4 User-Defined Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.8
6.5 ACNR Naming Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.10
6.6 I/O Interface Tags (Discrete Input) . . . . . . . . . . . . . . . . . . . . . . . . 6.11
6.7 I/O Interface tags (Analog Input) . . . . . . . . . . . . . . . . . . . . . . . . . 6.11
6.8 Logic Using Controller Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.13
6.9 Designating Base Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.13
6.10 Logic Using Alias Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.14
6.11 HMI Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.18
6.12 HMI Alarm Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.19
6.13 HMI Alarm Array [0] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.20
6.14 HMI Shutdown Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.21
6.15 HMI_Status Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.22
6.16 HMI_Discrete_Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.23
6.17 HMI Analog Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.24
6.18 HMI Snapshot Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.25
6.19 Alarm Logic Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.27
6.20 Creating a New Alarm Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.28
6.21 Alarm Tag Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.29
6.22 Status Bit Logic Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.30
6.23 Internal Tag Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.31
6.24 Timer Expanded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.32
6.25 Analog Equation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.35
6.26 Analog Equation Using Counts . . . . . . . . . . . . . . . . . . . . . . . . . . 6.37
6.27 UDT_Analog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.42
6.28 Header Pressure UDT Analog . . . . . . . . . . . . . . . . . . . . . . . . . . 6.42
6.29 Transmitter Scaling and Fail Detection Logic . . . . . . . . . . . . . . . . . . 6.43
xiv © 2007 Solar Turbines Incorporated. All rights reserved. 3820

Figure Page
6.30 Header Pressure Val Reference . . . . . . . . . . . . . . . . . . . . . . . . . 6.44
6.31 UDT Analogs Used As KVALS . . . . . . . . . . . . . . . . . . . . . . . . . . 6.49
6.32 KVAL Being Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.50
6.33 Program Response Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.53
6.34 User-Defined Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.53
6.35 UDT Fuel Responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.54
6.36 UDT Fuel Responses in Controller Database . . . . . . . . . . . . . . . . . . 6.55
6.37 Program Response Tag Operation . . . . . . . . . . . . . . . . . . . . . . . . 6.55
6.38 Program Response Data Being Loaded . . . . . . . . . . . . . . . . . . . . . 6.56
6.39 Program Response Tag Being Manipulated . . . . . . . . . . . . . . . . . . . 6.56
8.1 Oil Tank Heater Control Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.3
8.2 Lube Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.6
8.3 Tank Level Switch Routine . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.7
8.4 Rung Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.9
8.5 Base Tag Derivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.11
8.6 Node 08. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.12
9.1 Configure RS232 Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.3
9.3 RS232 Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.4
9.5 Configure PCC Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.6
9.8 Configure Ethernet Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.8
3820 © 2007 Solar Turbines Incorporated. All rights reserved. xv

Figure Page
9.11 TP IP Config Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.10
9.12 TP IP Config Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.11
9.13 Browsing the Ethernet Module Using Controlnet . . . . . . . . . . . . . . . . 9.12
9.14 Ethernet Module Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 9.13
9.15 Ethernet Module Port Configuration . . . . . . . . . . . . . . . . . . . . . . . 9.14
9.16 Communications Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.15
9.17 Going Online RS232 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.16
9.18 Going Online ControlNet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.17
9.19 Going Online Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.18
9.20 Select Recent Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.19
9.21 Connected to Go Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.20
9.22 Download Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.21
9.23 Downloading To The Controller . . . . . . . . . . . . . . . . . . . . . . . . . . 9.22
9.24 Controller In Program Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.23
9.25 Controller In Run Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.24
9.26 Upload Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.25
9.27 Upload Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.26
9.28 Forcing Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.28
9.29 Creating A Force . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.29
9.30 Enabling Forces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.30
9.31 Forces Enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.30
9.32 Enabling Forces RSLogix Version 13. . . . . . . . . . . . . . . . . . . . . . . 9.31
9.33 Forcing Analog Input Values . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.33
9.34 Forced Analog Value. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.34
9.35 Forcing Analog Output Values . . . . . . . . . . . . . . . . . . . . . . . . . . 9.35
9.36 Rung Bookmarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.35
xvi © 2007 Solar Turbines Incorporated. All rights reserved. 3820

Figure Page
9.37 Toggle Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.37
9.38 Locking The Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.39
9.39 Starting a Program Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.40
9.40 Accept Program Edits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.41
9.41 Test Program Edits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.41
9.42 Assemble Program Edits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.42
9.43 Completed Edits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.43
9.44 Starting a Program Edit Version 13. . . . . . . . . . . . . . . . . . . . . . . . 9.44
9.45 Accept Pending Program Edits Version 13. . . . . . . . . . . . . . . . . . . . 9.44
9.46 Test Program Edits Version 13 . . . . . . . . . . . . . . . . . . . . . . . . . . 9.45
9.47 Assemble Program Edits Version 13 . . . . . . . . . . . . . . . . . . . . . . . 9.45
9.48 Edits Complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.46
9.49 Finalize Edits Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.46
B.1 XIC Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.3
B.2 XIO Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.3
B.3 OTE Instruction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.3
B.4 Combining Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.4
B.5 Symbolic Logic AND Example . . . . . . . . . . . . . . . . . . . . . . . . . . B.4
B.6 Branched Logic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.5
B.7 Symbolic Logic OR Example . . . . . . . . . . . . . . . . . . . . . . . . . . . B.5
B.8 Complex Ladder Logic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.6
B.9 Complex Symbolic Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.7
B.10 OTL Ladder Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.7
B.11 OTL Symbolic Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.8
B.12 OTU Ladder Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.8
B.13 Combining OTL and OTU Instructions . . . . . . . . . . . . . . . . . . . . . . B.9
3820 © 2007 Solar Turbines Incorporated. All rights reserved. xvii

Figure Page
B.14 Latch/Unlatch Symbolic Logic. . . . . . . . . . . . . . . . . . . . . . . . . . . B.10
B.15 TON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.11
B.16 TON Timer Element References . . . . . . . . . . . . . . . . . . . . . . . . . B.12
B.17 TOF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.12
B.18 TOF Timer Element References . . . . . . . . . . . . . . . . . . . . . . . . . B.13
B.19 RTO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.13
B.20 RTO Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.14
B.21 RTO Timer Element Reference . . . . . . . . . . . . . . . . . . . . . . . . . . B.14
B.22 CTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.14
B.23 CTU Counter Element References . . . . . . . . . . . . . . . . . . . . . . . . B.15
B.24 CTD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.15
B.25 CTD Counter Element References . . . . . . . . . . . . . . . . . . . . . . . . B.16
B.26 ControlLogix Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.17
B.27 EQU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.18
B.28 EQU in Function Block Routine . . . . . . . . . . . . . . . . . . . . . . . . . . B.18
B.29 GEQ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.19
B.30 LEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.19
B.31 CMP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.20
B.32 LIM Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.21
B.33 ADD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.22
B.34 SUB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.23
B.35 MUL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.23
B.36 DIV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.24
B.37 CPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.24
B.38 MOV Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.25
B.39 JSR Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.26
xviii © 2007 Solar Turbines Incorporated. All rights reserved. 3820

Figure Page
B.40 Step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.36
B.41 Step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.36
B.42 Step 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.37
B.43 Step 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.37
B.44 Step 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.38
B.45 Step 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.39
B.46 Step 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.40
B.47 Step 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.41
B.48 Step 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.42
B.49 Step 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.43
B.50 Step 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.44
B.51 Step 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.45
B.52 Step 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.46
B.53 Step 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.47
B.54 Step 15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.48
3820 © 2007 Solar Turbines Incorporated. All rights reserved. xix

LIST OF TABLES
Table Page
6.1 Pre-Defined Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . 6.6
6.2 HMI Array Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.18

6.3 Program Scoped HMI Tag Prefixes . . . . . . . . . . . . . . . . . . . . 6.26
6.4 Alarm and Shutdown Tag Suffixes . . . . . . . . . . . . . . . . . . . . . 6.27

6.5 Analog Scaling Student Activity . . . . . . . . . . . . . . . . . . . . . . 6.39
6.6 Program Scoped HMI Tag Prefixes . . . . . . . . . . . . . . . . . . . . 6.45
8.1 Base and Alias Tag Exercise . . . . . . . . . . . . . . . . . . . . . . . . 8.8

8.2 Routine Function Summary . . . . . . . . . . . . . . . . . . . . . . . . 8.10
8.3 Routine Function Summary Student Exercise . . . . . . . . . . . . . . 8.10
8.4 I/O Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.13

8.5 I/O Mapping Student Activity . . . . . . . . . . . . . . . . . . . . . . . . 8.14
8.6 Alarm and Shutdown Troubleshooting. . . . . . . . . . . . . . . . . . . 8.23

B.1 Allowable Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.16
B.2 Compare Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.17
B.3 CMP Operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B.21

B.4 Compute/Math Instructions. . . . . . . . . . . . . . . . . . . . . . . . . B.22
3820 © 2007 Solar Turbines Incorporated. All rights reserved. xxi

Solar Technical Training INTRODUCTION
INTRODUCTION
TURBOTRONIC 4 APPLIED PRINCIPLES
COURSE OBJECTIVES
Upon successful completion of this course, the student
will be able to:
1. Describe the use of the various software

applications and tools in a Solar Turbotronic 4
project.
2. Demonstrate the ability to load a project from a

CD to a programming terminal using the correct
software tools and practices.
3. View a Solar project in the offline mode.

4. Demonstrate an understanding of the common
menus and functions of the RSLogix5000
programming software as used in Solar
applications.
5. Describe the organizational structure and
conventions used in a Solar project.
6. Describe the basic programming conventions and

techniques used by Solar to process analogs
and discretes.
7. Relate physical devices installed on the Solar

package to logical elements in the controller
program.
3820 © 2007 Solar Turbines Incorporated. All rights reserved. xxiii

INTRODUCTION Solar Technical Training
8. Edit a control program offline to add simple

analog and discrete functions, in accordance with
correct Solar practices.
9. Perform simple online edits and maintenance
tasks on a Solar project.
METHODOLOGY
This course uses a combination of instructor-directed

discussions and hands-on exercises to enable the
student to gain familiarity with the RSLogix 5000
programming environment, and Solar-specific
controller logic and control processes.
Programming exercises are used throughout the

lessons to apply the knowledge just learned to make
realistic edits to a project. The overall scenario for
these edits is contained in Appendix A. The instructor
may allow the students to complete this exercise
in short sections, when called for in the lessons.
Alternatively the exercise may be completed in full
towards the end of the course.
In addition to the main editing exercise, hands on
exercises are used throughout the lessons to reinforce
the theory.
PRE-REQUISITE TRAINING
The student should have successfully completed the

Turbotronic 4 Control System Principles training
course (computer-based training) or have equivalent
experience. The student should also have basic
computer skills, including a basic knowledge of
Microsoft Windows.
Note that Appendix B contains an explanation of the
Basic Instruction Set. This is for reference purposes,
and is only intended to be used for actual classroom
instruction when the pre-requisite knowledge is
lacking.
xxiv © 2007 Solar Turbines Incorporated. All rights reserved. 3820

MATERIALS
1. Student Workbook
2. Student Programming Terminals with:

• Windows 2000 / XP
• RSLogix 5000 Version 10.xx or Version

13.xx
• RSLinx
• PCC Card and Cable
3. Project CD PD75721 or customer-specific project
4. Project Electrical Schematics PD75721 or

customer-specific project
5. TT4000 CD version 3.5
6. TT4 Simulator or available control system (to be

used during Lesson 9 if possible)
• Serial Cable
• Ethernet Crossover Cable
3820 © 2007 Solar Turbines Incorporated. All rights reserved. xxv

LIST OF LESSONS AND APPENDICES
1. Introduction to Software Applications and Tools
2. Loading a Program to the Programming

Terminal
3. Offline Program Monitoring
4. RSLogix5000 Familiarization
5. Solar Project Organization

6. Solar Logic Familiarization
7. Editing a Project Offline
8. Hardware and Software Interface /

Troubleshooting
9. Online Program Monitoring
Appendix A - Project Editing Exercise Scenario
Appendix B - Basic Instruction Set

Appendix C - Analog Module Scaling Information
Appendix D - Common Abbreviations and Engineering

Units
xxvi © 2007 Solar Turbines Incorporated. All rights reserved. 3820

3820 © 2007 Solar Turbines Incorporated. All rights reserved. xxvii

xxviii © 2007 Solar Turbines Incorporated. All rights reserved. 3820

Solar Technical Training LESSON 1 - Introduction to Software Applications and Tools
LESSON 1 - Introduction to Software

Applications and Tools
OBJECTIVES
On completion of this lesson the student will be able to:
1. Describe the function of the Rockwell software

applications used in a TT4 project.
2. Describe the function of the range of Solar

Turbotronic Field Tools.
3820 © 2007 Solar Turbines Incorporated. All rights reserved. 1.1

LESSON 1 - Introduction to Software Applications and Tools Solar Technical Training
INTRODUCTION
To ensure that the TT4 control system functions
correctly, preserves a correct database and file
structure, and is easily maintained, it is important
to understand the function of the various software
applications and tools that are used on a TT4 control
system project.
This lesson will identify the various software
applications and tools, and briefly describe the
function of each. Many of the applications and tools
will be used in the hands on exercises that are part
of this training course.
The various software applications and tools may

be split into two distinct groups. The first group of
software is the Rockwell Applications group. This
group is comprised of RSLogix 5000, RSLinx, and
RSNetWorx for ControlNet. These applications are
primarily concerned with operation of the control
logic (both function block and ladder); managing
communications between different devices on the
ControlNet network; and scheduling communications
between the physical I/O and the Controller.
The second group of software tools, known as the
Solar Turbotronic Field Tools, are primarily concerned
with compiling the HMI display system tag databases;
maintaining project software structure through
different revisions; and creating reports.
Each of the software applications or tools not only has
a specific role or function, but also must be used in the
correct sequence in order to preserve project structure.
The function and order of use of each of the tools will
be covered in more detail throughout the practical
exercises included in this course.
1.2 © 2007 Solar Turbines Incorporated. All rights reserved. 3820

ROCKWELL SOFTWARE APPLICATIONS

The Rockwell Software applications comprise three
software applications, each of which has its own
specific function in the TT4 control system. These
software applications are:
• RSLogix 5000
• RSLinx
• RSNetworx for ControlNet

RSLogix 5000
RSLogix 5000 is the programming software used with
Turbotronic 4 projects. The software file contains a
Task, which consists of a series of Programs necessary
to allow the turbine package to operate in a safe
manner. Each program is made up of a series of
Routines. The Routines contain the actual control
logic, both ladder and function block, necessary to run
the turbine package. The software file (or ACD file)
resides in the Controller.
Figure 1.1 RSLogix 5000

RSLinx
RSLinx is used to configure the communications
drivers and establish communications between the
Controller and the programming terminal. Multiple
drivers can be configured and used, depending on the
hardware included with the project and the Field
Programming Unit (FPU), including:
• RS232-DF1 Serial Link

• PCC ControlNet
• PCIC ControlNet
• EtherNet
Figure 1.2 RSLinx

RSNetworx for ControlNet

In the TT4 control system all communications between
the Controller and the various package input/output
devices is via the ControlNet communications protocol.
RSNetworx is used to schedule the ControlNet system,
which means establishing the I/O configuration (what
is actually connected to the system), and certain
ControlNet communication parameters (network
update time, number of nodes, number of channels
used).
Figure 1.3 RSNetworx

SOLAR TURBOTRONIC FIELD TOOLS

The Solar Turbotronic Field Tools are packaged with
the Solar TT4000 display software, and are therefore
available to both Solar field service personnel and
also customers. Use of the tools during routine
maintenance of the control system is absolutely
essential to preserve project file structure during
operations including:
• loading software onto a programming terminal;

• creating backup copies of project software;
• compiling the TT4000 display system tag

databases;
• downloading the project software to the TT4000

and TT4000-S display devices;
• revising the project to a new release.
Figure 1.4 Solar Turbotronic Field Tools

The tools are also used to create multiple reports;

compare different ACD files; and to access the project
software via RSLogix 5000. It is very important to
access RSLogix 5000 through this tools interface,
since it will initiate project test tools and prompt
for software revision and documentation of changes,
when necessary.

STUDENT ACTIVITY - Lesson Review
1. Which of the following applications is used to

configure communications drivers?
a. RSLogix 5000
b. RSLinx
c. RSNetworx for ControlNet
d. Solar Turbotronic Field Tools
2. Which of the following applications is used as

the programming software to control the turbine
package?
a. RSLogix 5000
b. RSLinx

3. Which of the following applications is used

to setup the ControlNet system, including
establishing communications with the devices
on the network?
a. RSLogix 5000
b. RSLinx

4. How should the project file be accessed in

RSLogix 5000?
a. Double-click the ACD file in Windows
Explorer
b. Click on the RSLogix 5000 icon on the

Desktop
c. Start RSLogix 5000 fom the Windows Start

Menu
d. Open RSLogix 5000 through the Solar
Turbotronic Field Tools interface

NOTES:

NOTES:

ANSWER KEY
1. Which of the following applications is used to

configure communications drivers?
a. RSLogix 5000
b. RSLinx
2. Which of the following applications is used as

the programming software to control the turbine
package?
a. RSLogix 5000
b. RSLinx

3. Which of the following applications is used

to setup the ControlNet system, including
establishing communications with the devices
on the network?
a. RSLogix 5000
b. RSLinx

4. How should the project file be accessed in

RSLogix 5000?
a. Double-click the ACD file in Windows
Explorer
b. Click on the RSLogix 5000 icon on the

Desktop
c. Start RSLogix 5000 fom the Windows Start

Menu
d. Open RSLogix 5000 through the Solar
Turbotronic Field Tools interface



Solar Technical Training LESSON 2 - Loading a Program to the Programming Terminal
LESSON 2 - Loading a Program to the

Programming Terminal
OBJECTIVES
Upon completion of this lesson the student will be
able to:
1. Describe the standard file directory structure in

the programming terminal for TT4 projects.
2. Demonstrate the ability to load a project to

the programming terminal using the Solar
Turbotronic Field Tools installed on the
programming terminal.
3. Demonstrate the ability to update the project

revision to create a working file using the Solar
Turbotronic Field Tools.

LESSON 2 - Loading a Program to the Programming Terminal Solar Technical Training
PROJECT CD AND FOW

A project is released to the field via the Solar Field
Office Website (FOW). Downloading project software
from the FOW before going to site is the approved
method for Solar personnel. On completion of a site
visit any modified software must be uploaded to the
FOW for archiving. A Project CD should also be left on
site as a backup, and for use by the customer. Use of
the FOW is not covered in this training course, but full
details of this, and other control system processes and
procedures, are contained in the Field is detailed in
other the Field Employee Support Database within
Lotus Notes.
Figure 2.1 Field Employee Support Database
In this lesson we will use a Project CD to transfer the

project software files to the programming terminal.
Figure 2.2 shows the structure of a typical TT4 project,

as can be viewed by browsing the Project CD. The Jobs
folder contains a sub-folder named with the Project
Definition (or PD) number. This in turn contains one
or more folders for each package sold on the same
PD, with this folder named with the Package Serial
Number. Sub-system folders contain the controller
program, the HMI program, and the HMI-S program.

Figure 2.2 Project Structure
SUBSYSTEM FOLDER CONTENTS
Figure 2.3 shows the contents of the various subsystem

folders on a Project CD. When the project software is
distributed from the CD to the programming terminal,
the structure will be identical, other than the root
directory being C:\ rather than D:\.
Figure 2.3 Subsystem Folder Contents
In Figure 2.3 we can see one version of the software

in each subsystem folder signified by the folders
named 0000_999. As the project is installed and
commissioned, multiple versions of the software may
exist inside each of the subsystem folders. This is
covered in a later lesson.

Figure 2.4 Project ACD File
Figure 2.4 shows the project ACD file located in

0000_999 subfolder within the RSLogix folder. The
name of the file includes all of the elements already
mentioned:
Example:
• PD Number - PD75721
• Package Serial Number TG12345
• Revision Number 0000_999

The other file (with BAK included in the filename) is
a backup file. These backup files are automatically
generated by RSLogix when working on a project, but
should not be used for normal operations.

PROJECT TOOLS
Solar have developed a wide range of software tools

to manage a Turbotronic 4 project. Use of these tools
is the approved manner is absolutely essential to
preserve some file structures, and ensure that all of
the subsequent tools will function correctly.
The first tool to be used will take the project files from
the FOW or Project CD and load them correctly onto
the programming terminal.
TT4 Field Distribute Tool

To load the project from the Project CD using the TT4
Field Distribute Tool, use the following procedure:
1. Open the Turbotronic Field Tools, and then click

on the TT4 Field Distribute command.
Figure 2.5 TT4 Field Distribute

2. Referring to Figure 2.6:
a. Select source (CD Drive)
b. Select Job
c. Check Complete Job checkbox
d. Select Desctination (C Drive)
e. Click Distribute command
Figure 2.6 Distributing Job
NOTE
The tools will automatically create the
directory C:\Jobs, if it does not already exist.
Updating the Revision
The project files (RSLogix and Display) copied from

the Project CD will have the revision number as
xxxx_999. This 999 revison indicates that the revision
is RELEASED. Released means that the software is
complete (no temporary logic or edits in progress), in
the sense that this version can be downloaded to the
controller and the package put into normal operation.

Before modifying any software it is mandatory that

the software version is changed (or ROLLED). This
will create a temporary version for the edits, and in
addition will open up the project History files to allow
the changes to be documented.
To use the tool to update the project revision, use
the following procedure.
1. Open the Turbotronic Field Tools.
2. Ensure that the current version of the project is

selected in the dropdown box.
3. Click on Revision Control command.
Figure 2.7 Updating Revision

4. Place a checkmark against each subsystem that

will be modified, and then click on the Roll
Rev command.
Figure 2.8 Rolling Subsystems
5. Click on Yes when prompted by the Comms

Available dialog box.
Figure 2.9 Comms Available

6. The tools will check for confirmation that
the revision is to proceed, even although the
controller revison will not be updated at this
stage. Click Yes to proceed.
Figure 2.10 Continue With Roll

7. The project History File (or Files - depending in

which subsystems are being modified) will open.
Type in as much detail as possible on the edits
about to be completed, and then click OK.
Figure 2.11 History File

8. A final reminder will open on the need to update
the controller revision. Click OK to proceed.
Figure 2.12 Controller Tags Reminder

9. The temporary Working Revision has now been

created (with a Roll number of 000) to allow the
edits to be made. On completion of all edits the
project should be RELEASED using a similar
process.
Figure 2.13 New Revision

1. Which of the following is NOT included in the

TT4 project name?
a. Project Definition Number

b. Customer Name
c. Package Serial Number
d. Four-digit Release Number

e. Three-digit Roll Number
2. What is used to copy the software to a

Programming Terminal?
a. “Copy Jobs” Utility

b. TT4 Field Distribute
c. Revision Control
d. Standard Windows Explorer commands

3. In which directory will project files be placed
when distributing the software to a Programming
Terminal using the Turbotronic Field Tools?
a. C:\Jobs
b. C:\Turbotronic Projects
c. C:\My Documents\Jobs
d. C:\My Documents\Turbotronic Projects
4. When updating a project revision before any

modifications, what will happen to the three
character Roll number?
a. No change
b. Changes from 000 to 999
c. Changes from 999 to 000

NOTES:

ANSWER KEY
1. Which of the following is NOT included in the

TT4 project name?
a. Project Definition Number

b. Customer Name
c. Package Serial Number
d. Four-digit Release Number

e. Three-digit Roll Number
2. What is used to copy the software to a

Programming Terminal?
a. “Copy Jobs” Utility

b. TT4 Field Distribute
c. Revision Control
d. Standard Windows Explorer commands

3. In which directory will project files be placed
when distributing the software to a Programming
Terminal using the Turbotronic Field Tools?
a. C:\Jobs
b. C:\Turbotronic Projects
c. C:\My Documents\Jobs
d. C:\My Documents\Turbotronic Projects
4. When updating a project revision before any

modifications, what will happen to the three
character Roll number?
a. No change
b. Changes from 000 to 999
c. Changes from 999 to 000

NOTES:

STUDENT ACTIVITY - Generating Reports
The I/O Listing Report will be used to identify spare

channels for the programming exercises later in the
course. Generate and I/O Listing Report for either the
generic project PD75721 or the specific project you will
be working with during this course.

(This page intentionally left blank)


Solar Technical Training LESSON 3 - Offline Program Monitoring
LESSON 3 - Offline Program Monitoring
OBJECTIVES
Upon completion of this lesson the student will be
able to:
1. Open RSLogix 5000 on the programming
terminal.
2. Locate and open a project controller program

using RSLogix 5000.
3. Demonstrate familiarity with the screen

elements and menu structure presented on the
RSLogix 5000 display.
4. Demonstrate the ability to navigate through the

controller program as displayed on the RSLogix
5000 display screens.

LESSON 3 - Offline Program Monitoring Solar Technical Training
INTRODUCTION
When RSLogix 5000 is installed, a program icon
(shortcut) is placed in the normal Windows Start
Menu. On Solar-supplied programming terminals a
shortcut may also exist in the Controls Applications
folder on the desktop.
However, the correct method of opening RSLogix 5000

on a TT4 project is via the Solar Turbotronic Field
Tools. This will help ensure that the most recent
version of the software is being used, and will also
allow certain project test tools to execute.
NOTE
Various versions of the RSLogix5000
application are available. The initial release
Solars Turbotronic 4 control system used
version 10.xx, whereas later projects will
require version 13.xx. Although the basic
functionality is either identical or similar,
many of the menus, icons, and keystrokes
may differ slightly. This lesson will primarily
demonstrate the basic functions of version
10.xx, with any deviation due to version
13.xx also being demonstrated as the lesson
progresses.

OPENING THE RSLogix 5000 PROGRAM

1. After launching the Solar Turbotronic Field
Tools, select the correct version of the project
from the dropdown list.
Figure 3.1 Selecting the Project Revision

2. Now click the RSLogix Support command.
Figure 3.2 RSLogix Support
3. Finally click on the Start RSLogix 500 command.

Project test tools will execute, and the project
will open in RSLogix 5000.
Figure 3.3 Start RSLogix 5000

RSLogix 5000 Display

With a program opened, a variety of tools are available
to the user. The following is a discussion of the most
commonly used features. This initial discussion will
cover topics common to both RSLogix 5000 versions
10.xx and 13.xx. Version-dependent functions will
be covered later.
Refer to Figure 3.4 for the following descriptions.
Toolbars
The various tool bars will be described in the next

section.
Controller Organizer
This is the display that shows the organization of the

controller program in tree format. It can be toggled on
and off by clicking the tree icon above the Path Toolbar.
Quick Pane Properties View
This window provides a description and properties of

the item selected in the organizer. May be minimized
by dragging it downwards out of view.
Ladder/Function Block Window

This is the primary viewing area for monitoring and
editing ladder logic and function block files.

Results Window
This window displays the results of search and

verification activities.
Figure 3.4 RSLogix Main Screen

Figure 3.5 shows all of the available tool bars. Note

that some of the toolbars are probably not required
for everyday use, and some duplicate options are
available elsewhere. Therefore, users should establish
the preferred configuration of their own display. The
toolbars can be selecting for viewing or hidden by
using standard Windows commands. They can also
be dragged and resized to a certain extent in order to
maximize the viewing areas.
Figure 3.5 Available Toolbars
Standard Toolbar
This is presented and used in the same manner as

standard Windows toolbars. Clicking on a selection
will produce a pull-down with additional available
selections.
Figure 3.6 Standard Toolbar

Online Toolbars
Two different Online Toolbars are available, and
both are shown in Figure 3.7. The toolbar on the left
displays the controller status when online, and the
controller mode can be selected. Forces can be enabled
and disabled. The toolbar on the right (called the
Classic Online) duplicates the same information in
a different format, and also has the communications
path displayed. There is little need to have both
toolbars displayed.
Figure 3.7 Online Toolbars
Path Toolbar
This shows the current connection path for online

operations. To change the path, click on the pulldown
arrow and select a new device and/or address. The
small network icon at the left side of the toolbar
animates to indicate online activity. The button on the
right side of the toolbar opens up the RSWho function
to allow browsing of communications paths.
Figure 3.8 Path Toolbar

New Component Toolbar

One of these icons can be clicked to add a new element
to the project. These functions are available through
several different methods, and therefore this toolbar
may be a good candidate to remain hidden.
Figure 3.9 New Component Toolbar
Language Element Toolbar

Logic elements to be added can be selected by clicking
on the appropriate icon. Tabs can be clicked to show
additional instruction listings.
Figure 3.10 Language Element Toolbar

Ladder Edit Toolbar

Click one of these icons to modify a logic branch or
add an input or return parameter.
Figure 3.11 Ladder Edit Toolbar
Language Editor Editing Toolbar

Bookmarks can be assigned or accessed with these
buttons.
Figure 3.12 Language Editor Editing (Bookmark) Toolbar
Ladder Common Logic Toolbar
This toolbar allows the addition of some of the most

common ladder logic instructions during editing. Since
these functions are duplicated in the larger Language
Element Toolbar, this would also be a good candidate
to remain hidden.
Figure 3.13 Ladder Common Logic Toolbar

Help Menu Features

A Help menu is available by clicking Help on the
Standard toolbar. The help function is well organized
and provides useful assistance with a variety of topics.
Instructions for using the help features are included.
Figure 3.14 shows access to the Online Books that are
embedded in the program. These books are normally
in PDF format.
Figure 3.14 Online Books

Figure 3.15 illustrates another very useful feature of

the Help menu, the Instruction Help. A full list of
ladder logic instructions appears at the left side, with
function block logic instructions on the right side.
Figure 3.15 Instruction Help

RSLogix Version 13.xx Features

RSLogix version 13.xx has two additional features
over version 10.xx, and both are illustrated in Figure
3.16. The Toolbars View box has a Restore Factory
Toolbar Layout command button.
Figure 3.16 Version 13.xx Features

Selecting Custom Tools will display tools that have
been added by following the instructions that are
available in the main Help menu area. This will
allow opening of different applications from within
RSLogix, and may be useful to add commands to open
other Solar TT4 applications such as the TT4000
Project Tools.

NOTES:

STUDENT EXERCISE - Toolbars
Take a few minutes to select or de-select toolbars, and

then them arrange the toolbars by dragging them with
the mouse, until the toolbars are easily accessible
while still allowing the maximum viewing area for the
other RSLogix features.



Solar Technical Training LESSON 4 RSLogix 5000 Familiarization
LESSON 4 RSLogix 5000 Familiarization
OBJECTIVES
Upon successful completion of this lesson, the student
will be able to:
1. Demonstrate familiarity with the principal
RSLogix 5000 toolbar functions.
2. Demonstrate the ability to configure the screen

displays in the RSLogix 5000 software.
INTRODUCTION
The RSLogix 5000 program features that will normally
be used most often in the field are those relating to
accessing, modifying and saving program files. These
features will be discussed and illustrated in this
lesson. While many of the features and functionality
is either similar or identical between RSLogix 5000
versions 10.xx and 13.xx, any major differences will be
covered as the lesson progresses.

LESSON 4 RSLogix 5000 Familiarization Solar Technical Training
CONFIGURING SCREEN DISPLAYS
Window Configuration
Figure 4.1 Window Settings
The format for the screen can be modified as desired

by clicking the Window option and then any of the
selections. Examples are that the screen can be split
horizontally or vertically, tiled in either plane, or
cascaded, just as in any Windows-based application.
This drop down menu also allows management of the
routines to be closed when multiple routines are open.

Font Configuration and Other User Preferences
To set the preferences for the display appearance, click

Tools, then Options, and expand the categories by
clicking the + sign at the desired category. The desired
change can be made by following the prompts (see
Figure 4.2).
Figure 4.2 Modifying Fonts & Colors
RSLogix 5000 version 10.xx categories are:
• Application allows font and color configuration

and other preferences for the basic application.
• Tag Display configures how the tag databases
are displayed. You may want to select the most
commonly used tag data type as the default to
simplify up the tag creation process (the most
common tag data type will normally be BOOL).

• Ladder Editor allows font and color

configuration and other preferences for the main
ladder logic viewing area.
• FDB Editor allows font and color configuration
and other preferences for the function block
viewing area.
RSLogix 5000 version 13.xx has additional options,

and these are illustrated in Figure 4.3.
Figure 4.3 Version 13 Tools Options
• SFC Editor allows configuration of the

Sequential Flow Chart editor not currently used
by Solar.
• Structured Text Editor allows configuration
of structured text elements not currently used
by Solar.
• Trends allows configuration of the sample
time and data-logging directory for Trends
(stripcharts) that can be created in RSLogix
5000.
• Motion not currently used by Solar.

STUDENT EXERCISE - Customizing the Display

Take approximately 5 to 10 minutes to look through
the configuration options listed above that are
normally used by Solar. Customize your display as
necessary.

NOTES:

MENU AND TOOLBAR FUNCTIONS
File Menu
Clicking on File will give the drop down box as shown
in Figure 4.4.
Figure 4.4 File Menu

Many of the commands are standard Windows
commands (New; Open; Close; Save; Save As; Print;
Print Options; Exit).
Selecting New Component allows the addition

of the same new components available in the New
Component toolbar covered previously (Routine; Tag;
Trend; etc.).
Selecting Compact performs a utility function similar

to the Windows Disk Defrag utility, and enhances
performance. Rockwell recommends running this
utility periodically.

Selecting Generate Report will open the dialog box

shown in Figure 4.5. This allows configuration of
reports that will be sent directly to a printer. Various
options are available, including selecting a report on
tag usage and routine listings. Note that this option is
not available with Version 10.xx.
Figure 4.5 Generate Report Options
Edit Menu
Clicking on Edit will open the drop down menu shown
in Figure 4.6. Many of the commands are standard
Windows commands (Undo; Redo; Cut; Copy; Paste;
Delete).
Figure 4.6 Edit Menu

Selecting Properties will open up the properties

box for whatever element is currently selected (for
example a Program or Routine).
Selecting Controller Properties will open up the box
shown in Figure 4.7. Various tabs can be selected to
perform functions such as configuring communication
parameters; checking and clearing faults; and setting
the controller clock. Note that in a TT4 system the
controller acts as the master clock, with devices such
as the TT4000 display system synchronizing with the
controller to obtain the date and time.
Figure 4.7 Controller Properties

Selecting Insert will open up the options shown in

Figure 4.8. This will be available when monitoring
a ladder routine, and is one method of inserting
elements such as rungs, branches, or instructions.
The elements will be inserted where the cursor is
positioned.
Figure 4.8 Insert Options
Selecting Edit Ladder Element will allow editing

the ladder element where the cursor is positioned.
Functions include toggling discretes on and off;
managing forces; and editing instructions and
descriptions.
RSLogix 5000 version 13.xx has different options in

the Edit menu than version 10.xx. The version 13.xx
menu is shown in Figure 4.9.

Figure 4.9 Version 13 Edit Menu
Selecting Import Rung or Export Rung allows

multiple rungs to be imported or exported from saved
files. Figure 4.10 shows the dialog box that opens
when exporting a rung or rungs. Note that the rung
is saved as a file with an L5X extension. This file
could then be imported to another project using the
Import Rung command.
Figure 4.10 Export Rung
Note that multiple rungs can be selected for copying,

cutting or exporting by holding down the Shift or
Control keys while selecting rungs by clicking with

the mouse. An alternative method to select all rungs

in a routine is to click Select All from the version
13.xx Edit menu.
The other options in the version 13,xx Edit menu
(dealing with Instruction Defaults) are not used
with the types of instructions currently used by Solar.
View Menu
Figure 4.11 shows the View menu for version 13.xx.
This is the same as for version 10.xx, but with the
addition of the Watch command.
Figure 4.11 View Menu

Selecting Toolbars allows configuration of the visible
toolbars, as covered previously.
Selecting Controller Organizer will toggle the

organizer viewing area on and off to allow the routine
or tag database to be viewed on the full width of the
screen. This function is also available by toggling the
icon in the main menu bar (the icon has the same
appearance as the icon shown in Figure 4.11).
At certain times during editing or otherwise working
with RSLogix 5000, a box will open at the bottom
of the window to display results of searching or to
display errors. This box is known as the Output
Window, and is shown in Figure 4.12.
Figure 4.12 Output Window

From the View menu, selection of Errors, Search

Results, or Watch will toggle that portion of the
Output Window.
The other method of viewing that portion of the
Output Window is to simply click on one of the three
tabs at the bottom of the window. The Errors tab has
been selected in Figure 4.12, since the operation just
carried out was Verification of a routine. Verification
checks the selected routine for validity and will report
discrepancies such as invalid tag names or empty
rungs. These discrepancies will be classified as either
Errors or Warnings, and note that a project may not
be downloaded to the controller if Errors or Warnings
exist. Shortcut icons for verification are also available
on the main menu bar, as shown in Figure 4.13. The
left icon will verify the current routine, and the right
icon the entire controller.
Figure 4.13 Verification Icons
The Search Results tab would have been selected to

view the results of a search, and this will be covered
later in this lesson.
The Watch tab is only available in version 13.xx,

and would be selected to view a ladder or function
block routine in the top section of the screen, with the
tags associated with that routine visible in the Watch
window at the bottom of the screen. This is shown in
Figure 4.14. Note that the Watch function has two
main options. Currently selected is Current Routine,
which will display all the tags associated with the
active routine. Selecting Quick Watch will allow only
tags of special interest to be entered for viewing.
Figure 4.14 Watch Function

Search Menu
Figures 4.15 and 4.16 show the Search menus for
the different versions of RSLogix 5000. The basic
functions are similar, and will be covered first.
Figure 4.15 Version 13 Search Menu
Figure 4.16 Version 10 Search Menu
Figure 4.17 shows the dialog box that appears

when Find is selected. Before using this function
ensure that the configuration allows the maximum
opportunity to find the desired element. This involves
the following procedure:
1. Click on the Find Within button. The dialog

box expands to accommodate the configuration
options.

2. Select each of the Components in the left

selection box in turn, and ensure that all of the
checkboxes that appear in the right selection
box are checked.
Note that Figure 4.17 shows the version 13.xx options,
which is the same as version 10.xx, with the added
options for Sequential Function Charts and Structured
Text (neither of which are used by Solar).
Figure 4.17 Find Dialog Box

Once configured, the Find function can be used in
the following ways:
If the cursor was not on a logic element in the ladder

display, a search reference must be entered in the
Find What window. If the cursor was on a logic
element, theFind What window will contain the tag
assigned to the element.
The additional entry windows can be used to configure
the search utility by clicking the pulldown arrows and
selecting the desired settings. Take care to ensure
that the search is not too restricted, by making the
appropriate selections in the Find Where dropdown
box (All Routines in Current Task will normally
provide the most effective search).

Additional features (Wrap on/off, Search Direction,

etc.) are configured by clicking in the relevant check
boxes.
With a reference in the Find What window, select the
desired function by clicking one of the boxes on the
right side of the dialog box.
Selecting Find Next will locate the first occurrence

of the search reference within the ladder logic or
function block logic routine. The Find dialog box
remains visible, and if the location found is not the
desired location, clicking Find Next again advances
the search to successive occurrences of the search
reference.
Figure 4.18 Find Next Results

Figure 4.19 illustrates the effects of selecting Find

All.
Figure 4.19 Find All Results
The output window at the bottom of the screen

shows a listing of the occurrences of the tag:
PGM_Sequence.Ready_To_Load. The output
window can be scrolled to view all occurrences. Double
clicking any of the occurrences of the tag will jump to
the selected occurrence of the tag within the ladder
logic. Note that although not immediately apparent
from the example shown in Figure 4.19, the Find All
function is not always user-friendly, in the sense that
the output window will display all search locations
(both where the search reference exists, and doesn’t
exist). Therefore scrolling all the way through the list
is often required to locate the actual locations where
the search reference was found.

Selecting Replace will open up the dialog box shown

in Figure 4.20. This function will both find occurrences
of the search reference, and replace it with the text
entered in the Replace With box. Ellipsis boxes can
be used to browse and select tags from the databases
for both the Find What and Replace With boxes.
Figure 4.20 Replace
The Cross Reference feature in the Search menu

accesses the cross-reference database to display a
summary of all occurrences of the selected reference.
A cross-reference can also be executed by highlighting
the selected tag and pressing Ctrl+E, or alternatively
right clicking the tag and selecting Go To Cross
Reference from the dialog box. See Figure 4.21.

Figure 4.21 Go To Cross Reference

Figure 4.22 illustrates the cross-reference results for
the tag Header_Pressure.Val, which is the scaled
value of the lube oil header pressure transmitter.
Double clicking any of the results will open up the
ladder logic at that selected occurrence.
Figure 4.22 Cross Reference Results

Selecting Go To from the Search menu opens a dialog

window (see Figure 4.23) to select the desired option.
By positioning the cursor in the Go to What window:
• The Cross Reference database for the referenced
element can be viewed,
• The selected tag can be monitored or edited,
• The properties of the selected element can be

edited,
• The cursor (caret) can be positioned to a specific
rung.
Figure 4.23 Go To Dialog Box
Other functions accessible from the Search menu

differ between version 10.xx and 13.xx.
When using RSLogix 5000 version 10.xx, selecting

Next Error or Prev Error will jump between errors
when viewing the output window, normally after
verification has been completed.
When using RSLogix 5000 version 13.xx, selecting

Find Next or Find Previous allows jumping
between occurrences of the search reference entered in
the text box in the main Menu Bar (see Figure 4.24).
This function can also be executed by clicking on the
icons also highlighted in Figure 4.24.
Figure 4.24 Find Icons in Main Menu Bar

Another feature of the Search menu when using

version 13.xx is Next Result and Prev Result. These
functions can be used to jump between occurrences
of a search reference in the output window, after
executing the Find All function described previously.
The final function of the Search menu (only available
with version 13.xx) is the Browse Logic function
(see Figure 4.25).
Figure 4.25 Browse Logic
This function provides a summary of the overall

function of the Task, Program, Routine or Rung. Note
that the Tag shown next to the rungs are tags that are
being manipulated in that ring (i.e. they have analog
or discrete data being written to them). Since they are
manipulators, the instructions associated with these
tags will be OTEs, OTLs, CPTs, TONs, etc.
The Find box with the associated Find icon also

allows this function to be used to search for elements
within the logic. As with many of the functions, double
clicking on particular occurrences will open up that
section of logic.

Logic Menu
Selecting Logic will produce the menu box shown in

Figure 4.26 (version 10.xx shown). Available functions
include management of forces; verification of logic;
and initiation or finalizing of edits. Since most of these
functions are either not normally used by Solar, or are
more easily executed in another manner, they will not
be described in this section.
Figure 4.26 Logic Menu

Communications Menu
Clicking on Communications will open the drop
down menu shown in Figure 4.27.
Figure 4.27 Communications Menu
Selecting Who Active opens the RSLinx RSWho

function, that allows browsing of communication
paths to establish communications with the controller.
This function is also available by clicking on the icon
in the Path Toolbar.
Clicking on Select Recent Path will open the
window shown in Figure 4.28. The application will
store the most recently used communications paths to
allow selection of the currently valid communications
path, and then clicking on Go Online to establish
communications with the controller.
Figure 4.28 Select Recent Path

Once the valid communications path has been

selected, it can be saved as the default for this project
by selecting the Apply Selected Path to Project
checkbox.
By selecting a valid communications path as the
default, the functions Go Online, Upload and
Download may be used without the need to browse
using RSWho.
Going Online Options and Definitions
• Go Online: connects the programming terminal

to the controller. To use this function the open
Offline project (programming terminal) must
exactly match the Online project (controller),
otherwise an Upload or Download will be
required.
• Upload: the project will be uploaded from the

controller to the programming terminal. Note
that uploading will result in the loss of software
documentation such as tag descriptions and
rung comments. These can be restored using a
procedure that will be covered in a later section
of training.
• Download: the project will be downloaded from
the programming terminal to the controller.
This will place the controller in Program

Mode, resulting in a package shutdown
due to the loss in communications
between the controller and the I/O.
Therefore this should only be selected
when the turbine package is shutdown,
the post-lube sequence is complete, and
the compressor is safely depressurized
with the seal system de-activated (if
applicable).

Controller Modes
Selecting Program Mode, Run Mode or Test Mode

will change the state of the controller (these functions
are only available when the controller keyswitch is
in the Remote position).
• Run Mode: the program executes normally.

• Program Mode: the program does not execute
and all outputs are turned off.
• Test Mode: can be selected when the keyswitch
is in Remote. The program will execute as in
Run Mode, however the output modules will not
update the outputs, or the signals to the field
devices.
Selecting Lock Controller will deny editing
privileges to any other users who are currently
online. Note that the process of coming offline will
automatically unlock the controller.
Selecting Go To Faults or Clear Faults will either
display or clear any major faults in the controller.
Tools Menu
In addition to the configuration Options covered
previously, the following are some of the major
functions of the Tools Menu.
Figure 4.29 Tools Menu

Selecting Export will open the window shown in

Figure 4.30. This allows the software documentation
such as tag descriptions to be exported to a CSV
(Comma Separated Value) file, which can then be
the source for import to another project as shown
in Figure 4.31. This function is especially useful
following an upload from a controller. If the chosen
source project is as close as possible to the destination
project, then using this simple procedure should
restore most of the descriptions
Figure 4.30 Export

Figure 4.31 Import

SUMMARY
Only some of the main functions used by Solar during
normal monitoring and editing of the project have
been covered in this lesson. Additional functions
may be used occasionally, and the RSLogix 5000
Help menus are an excellent source of any additional
explanations that may be required.

STUDENT EXERCISES
ALL RSlogix 5000 Versions
1. Ensure that the Find function is configured to

maximize the search efficiency, as described in
this lesson.
2. Use the Find function to locate the first

occurrence of the tag Header_Pressure.Val.
3. If Header_Pressure.Val does not exist in this

project, use the tag NGP.Val instead.
4. Bookmark this rung.
5. Use the cross-reference function to locate three

more occurrences of this tag.
6. Bookmark each rung.
7. Use the Bookmark toolbar to practice moving

between each bookmark.
8. Remove all of the bookmarks.

ONLY RSLogix Version 13.xx
9. Use the Browse Logic function to write down the

text annotated against the rung in the program
where Header_Pressure.Val (or NGP.Val) is
located. Write the text in the space below.
_____________________________________________
10. Enter the text Ignition in the Find box, and use
the Find button to locate the rung where the
Ignition Timer Preset value is written to the
timer (normally in a MUL instruction).
11. Double click on the tag to open up the logic

where the MUL is located. Write down the
Ignition Timer Preset value (in seconds) in the
space below. Write down any additional values
for different fuel types.
_____________________________________________
_____________________________________________
_____________________________________________



Solar Technical Training LESSON 5 Solar Project Organization
LESSON 5 Solar Project Organization
OBJECTIVES
will be able to:
1. Describe the project configuration used by Solar.
2. Describe project element naming requirements

and conventions.
3. Describe the different types of program used in

a Solar project.

LESSON 5 Solar Project Organization Solar Technical Training
INTRODUCTION
This lesson covers the Turbotronic 4 software
architecture, meaning the aspects of the software that
are not directly used to control the engine and its
driven equipment. There are many ways to accomplish
the tasks that the controller needs to perform to
control the package; this lesson will cover how Solar
Turbines organizes these tasks to do it.
PROJECT CONFIGURATION
Solar projects are organized in three basic levels of
hierarchy:
1. TASK
2. PROGRAM
3. ROUTINE
Figure 5.1 Project Configuration

Tasks
The highest level of logic organization in RSLogix
5000 is the TASK.
Solar intends to only use the continuous task, and

therefore each project will consist of only one task.
This will be named Turbomachinery_Task, as
shown in Figure 5.2. Note the first of the naming
conventions used: each word begins with a capital
letter and is separated by an underscore.
A task can be configured to be either continuous or
periodic. A continuous task executes continuously
while a periodic task would occur at regular timed
intervals. This configuration is achieved by selecting
the Configuration tab shown in Figure 5.2, after
right-clicking on the Turbomachinery_Task and
selecting Properties from the menu.
Figure 5.2 Task Properties

Programs
The next level of logic organization is the PROGRAM.
Programs are used to group together sections of

logic according to functionality, or physically related
devices. For example a different program is used
for each package system (Lube Oil, Fuel, etc.), and
different programs are used for specific functions,
such as the HMI or Serial Interface.
Figure 5.3 below shows an organization of programs
within the Turbomachinary_Task. They are shown in
the order they will execute within the task.
Figure 5.3 Program Schedule
A specific naming convention should be followed

- the programs are named based on the function
they perform followed by four characters to identify
the specific configuration (Taurus 60 PG, Mars 100
CS/MD, etc.), and three digits used to identify the
revision. Also note that as with the task, the program
names should begin with capital letters and be
separated by an underscore. Note that failure to
comply with the program naming conventions will
result in the tag database compiling tool disregarding
any tags within these programs, therefore the tags
will not be transferred to the display system.

The task properties window shown on the right side of

Figure5.3 determines the order of program execution.
By convention the Framework and Sequence program
should execute first, with the Serial Interface and
HMI programs executing last.
Reordering of the programs can be achieved by
highlighting the program and clicking on the move up
or move down arrows.
Unscheduled Programs
Also note the Unscheduled Programs folder in

the controller organizer window at the left side of
Figure 5.3. This folder is outside the structure of the
Turbomachinery_Task, and therefore its contents will
not be executed as part of the task.
As the name suggests it can be used to retain

programs that are not required for normal operation
of the package, such as dedicated troubleshooting
programs for maintenance activities.
The method of moving a program to and from the

Unscheduled Programs folder is to highlight the
program in the Program Schedule window shown at
the right side of Figure5.3 and click Add or Remove,
as required.
Creating New Programs

To create a new program, simply right click on the
Turbomachinery_Task and select New Program
from the list of options. Then type in the program
name, observing the correct naming conventions,
and click OK.

NOTES:

PROGRAMMING EXERCISE #1 - Creating New Programs
1. Refer to the project editing scenario in

Appendix A.
2. Add the new program required by the exercise

scenario. Ensure that the Solar naming
conventions are observed.
3. Move the new program above the Serial Interface

and HMI programs.
4. As a practice, move the new program into the

Unscheduled Programs folder.
5. Move the program back into the

Turbomachinery_Task.
6. Move the program back above the Serial

Interface and HMI programs.

NOTES:

PROGRAM TYPES
In order to describe the function of the various
programs, they can be categorized into four different
types:
1. I/O Control Programs
2. Package State Program

3. Interface Programs
4. Framework Programs

I/O Control Programs
This category includes the majority of the programs

used, and their function is to monitor and control the
package systems. Typical examples are as follows:
Ancillary Monitors and controls all ancillary devices, including the battery charger, air
inlet filters, and water wash.
Cpsr_Monitoring Monitors compressor suction and discharge pressure and temperature.
Cpsr_Seal Monitors and controls the wet or dry seal system.
Enclosure Monitors and controls all enclosure devices, including the fire and gas
system and enclosure ventilation.
Exhaust Controls engine purge and waste heat recovery system.
Fuel Monitors NGP, NPT, PCD, T1, T5, and T7 to control gas and/or liquid fuel
system, bleed valve and guide vane.
Generator Monitors and controls the generator, circuit breaker, and utility breaker.
HPC_Shaft_Brg Monitors the HP compressor vibration and bearing temperature.
LPC_Shaft_Brg Monitors the LP compressor vibration and bearing temperature.
IPC_Shaft_Brg Monitors the IP compressor vibration and bearing temperature.
Load_Shed Monitors generator status and spinning reserve to shed loads on loss of
generator.
Lube Monitors and controls lube oil system components.
Process_Control Performs compressor process control for engine speed setpoint and surge
protection.
Project_Specials Contains logic for all custom features that do not impact logic in other
programs.
Shaft_Bearing Monitors engine vibration and bearing temperature.
Start Controls and monitors all start system functions.
Yard_Valves Monitors and controls yard valves.

Package State Program

There is only one program of the Package State type,
and it is called Sequence. It receives signals from
other programs and updates the operating state or
sequence of the package. This data is then relayed
back to other programs to sequence further events. It
also provides status bits for display purposes.
Example:
1. The Start program sends a signal to the

Sequence program when the purge crank timer
has timed out.
2. The Sequence program clears the state Purge

Crank and sets the state Ignition.
3. This status is sent to other programs to sequence

further events. For example the Start program
will command a high-speed crank, and the Fuel
program will command the ignition exciter, torch
solenoid, etc.
4. Once T5 reaches 400F, the Fuel program reports

back to the Sequence program that ignition has
been successful, and the package state will be
updated to Accelerate.
5. The “Accelerate” bit will be used to sequence

further events in the different programs.

Interface Programs
There are two programs that are classified as Interface

Programs.
1. HMI
2. Serial_Interface
HMI This program processes inputs and outputs

from all operator interfaces including
control panels, TT4000 display system
and remote supervisory controls. The
HMI program also processes alarm and
shutdown summary logic, and functions
necessary to transfer data to the display
system.
Serial_Interface Processes performance calculations from
the display so that they can be read by
customer systems via a serial link. Also
contains logic for other customer interface
systems, such as Modbus, SCADA or DCS.
Framework Program
As with the Package State program type, there is

only one program of the Framework type, and it will
be called Framework. It contains logic for system
diagnostics, including the controller, ControlNet,
and each Flex I/O Node. It also contains logic for
the Backup Overspeed Monitoring system and an
External Watchdog Timer that monitors for controller
scan errors.

ROUTINES
The lowest organization of logic in RSLogix 5000 is
the ROUTINE. Routines generally consist of small
sections of logic dedicated to a package sub-system or
other logic. For example in the Lube program shown
in Figure 5.4 there is a separate routine only for the
Tank Level Switch, and another separate routine only
for the Post Lube logic.
Figure 5.4 Routines Within the Lube Program
Routine Naming Conventions
Routines appear in the program in alphanumerical

order, except the routine that is designated as the
Main Routine. The Main Routine always appears first
after the program tags folder and can be recognized
by the indicator "1" in the icon. Note the naming
convention for the Main Routine: the name of the
program followed by Main_Routine (with no prefix
characters or revision characters).
It is more informative to view the program with the
routines in the order that they will execute. In Figure
5.4 the routines are named with a number prefix. This
puts the routines in the order of execution (set by the
order of JSR instructions within the Main Routine, as
will be explained later).

RSLogix 5000 does not permit a routine name to

start with a number, so the routines start with an
underscore “_”. As with previous naming conventions
use capital letters for the first character in each
word and separate each word with an underscore.
The three-character revision number of the routine
should follow the name.
The routines are number 010, 020, 030 so that routines

can be added in sequence in between existing routines.
If a routine is needed to execute between routines 010
and 020 it could be numbered 015, placing it in the
middle and still allowing further additions.
Main Routine Function

The main routine does not contain any logic other
than JSR instructions to sequence the other routines.
Once designated as a main routine, the controller
will scan it automatically.
Figure 5.5 shows how to designate the Main Routine.
By right-clicking the program name and selecting
Properties and then the Configuration tab, the
Main Routine can be selected from the drop down list.
Also note the Fault routine selection and that this is
not currently used by Solar.
After clicking Apply and OK (or just OK) you would
see that the selected routine has the indication “1”
and has been automatically relocated to the top of the
routine list, below the program tags folder.
Figure 5.5 Designating the Main Routine

The main routine is the only routine within each

program that is automatically scanned. In order to
have the other routines scanned, a JSR (Jump to
Subroutine) instruction should be programmed in the
main routine for each of the other routines in the
program. An example of logic within a main routine
is shown in Figure 5.6.
Figure 5.6 Main Routine Logic
Routine Comments
Figure 5.6 also illustrates the addition of Routine

Comments at the top of every routine. The comments
are actually Rung Comments, and are added by right
clicking above the rung and selecting Edit Rung
Comment from the list of options.
To prevent the loss of the routine comments in the
event that the top rung of the routine is deleted at a
later date, and also to give a tidier appearance, Solar
convention is to add an additional rung at the top
of each routine. Since each rung must have a valid
output instruction, Solar use the NOP instruction (No
OPeration does nothing) on this additional rung.

Routine Descriptions
Routine descriptions should briefly describe routine

function. This description will appear over the JSR in
the Main Routine. Figure 5.7 shows both the method
of adding a routine description (by first right clicking
on the routine and selecting Routine Properties
from the options list), and how that description will
appear above the JSR instruction for that routine.
Figure 5.7 Routine Descriptions

Inhibiting a Program
Figure 5.8 illustrates a function that is only available
is RSLogix Version 13.xx - inhibiting a program from
the Program Properties window. When the check box
was selected and the Apply was clicked, the small
icon appeared next to the program indicating that
it is inhibited, and no longer being scanned by the
controller. This function should only be used with
great care during troubleshooting or testing.
Figure 5.8 Inhibiting a Program

FUNCTION BLOCK ROUTINES

So far we have only mentioned Ladder Logic routines.
These can be identified by the ladder icon in the
directory structure within the task, and although
they are capable of performing relatively complex
calculations, they are more particularly suited to
processing of discrete inputs and outputs, and
sequencing.
Function Block programming will generally be used

to perform more complex calculations than Ladder
Logic is capable of, and therefore will typically be
used within the Fuel, Generator and Surge Control
programs, as applicable to the project.
Figure 5.9 illustrates typical examples of Function

Block routines within the Generator program,
including:
1. _100_kw_Percent_000
2. _110_kw_Setpoint_000
Figure 5.9 Generator Routine Listing

Function block routines should also have a

corresponding JSR instruction in the Main Routine;
otherwise they will not be scanned by the controller.
Function block routines have the same access to the
controller tag database and program tag databases
as ladder routines.
Figure 5.10 Typical Function Block Routine

NOTES:

1. State the three structural levels of a Solar project

starting with the highest level.
_____________________________________________
_____________________________________________
_____________________________________________
2. State the four types of Program.
_____________________________________________
_____________________________________________
_____________________________________________
_____________________________________________
3. Which of these would be a valid Program name?
a. _010_Lube_001
b. Lube_0126_001
c. 010_Lube_001
d. Lube_001_0126
4. Which of these would be a valid Routine name?

a. 030_Tank_Heater_001
b. _030_ Tank_Heater_001
c. Tank_Heater_001
d. 030 Tank Heater 001

5. State the purpose of the Main Routine in each

Program.
_____________________________________________
_____________________________________________
_____________________________________________
_____________________________________________

NOTES:

NOTES:

ANSWER KEY
1. State the three structural levels of a Solar project

starting with the highest level.
TASK (Turbomachinery_Task)
PROGRAM
ROUTINE
2. State the four types of Program.
I/O Control
Package State
Interface
Framework
3. Which of these would be a valid Program name?
b) Lube_0126_001
4. Which of these would be a valid Routine name?
b) 030_ Tank_Heater_001
5. State the purpose of the Main Routine in each

Program.
This routine is automatically scanned

by the controller, and contains a JSR
instruction for each of the other routines
in the program, to tell the controller to
scan these routines.

NOTES:

STUDENT EXERCISE - Sequence Program

Familiarization
1. Open up the Sequence program and locate the

rung where the sequence bit Accelerate is set
Rung Number = _____________________________
2. Other than the Sequence program, name the

three other programs where the Accelerate
bit is used (use the cross-reference function to
find this answer)
_____________________________________________
_____________________________________________
3. What is the next sequence state?
_____________________________________________
4. What is the rung number where this is set?
Rung Number = _____________________________

NOTES:

STUDENT EXERCISE - Interface Program

Familiarization
1. What functions are performed by the Serial

Interface program in this project?
_____________________________________________
_____________________________________________
2. What is the routine and rung where the Skid

Start Button command is set?
_____________________________________________
_____________________________________________
3. Open up the routine that begins with _150_

and list the two devices that will give a remote
stop command
_____________________________________________
_____________________________________________

NOTES:

STUDENT EXERCISE - Framework Program

Familiarization
1. What is the Watchdog Timer preset time?
_____________________________________________
2. What is the routine and rung where the

Microprocessor Fail Relay is latched?
_____________________________________________
_____________________________________________

NOTES:

PROGRAMMING EXERCISE #2 - Creating Routines
1. Refer to the project editing exercise in Appendix

A.
2. Create a Main Routine for the new program

already created. Observe all Solar naming
conventions.
3. Create the other routines called for in the

scenario. Observe all Solar naming conventions.
4. Configure the program to designate the new

Main Routine. Ensure that the 1 appears in the
icon next to the Main Routine.
5. Add an NOP instruction in a rung at the top

of each routine.
6. Add a Routine Description for each of the

routines.
7. Edit the Main Routine to add a JSR for each

of the other routines.
8. Ensure that a description appears above each of

the JSRs. If not, edit the Routine Properties to
add a description (note that this is different from
the Routine Description above Rung 0).



Solar Technical Training LESSON 6 - Solar Logic Familiarization
LESSON 6 - Solar Logic Familiarization
OBJECTIVES
will be able to:
1. Describe the structure of RSLogix 5000 tag
databases.
2. Describe the use of Base Tags and Alias Tags.
3. List common Solar tag naming conventions.

4. Describe how Solar process alarms and
shutdowns.
5. Describe how Solar pass data to the display

system.
6. Describe how Solar process analog data using

the UDT Analog.
7. Describe how Solar process data using Program

Response Tags.
8. Describe how Solar use program constants.

LESSON 6 - Solar Logic Familiarization Solar Technical Training
INTRODUCTION TO TAGS
Some students may already be familiar with control
system programming software that used Data Files to
store data of similar types. Previous control systems
used by Solar used AB6200 programming software.
This program employed data files including the
following common examples:
• I - Discrete Inputs
• O - Discrete Outputs
• B3 - Internal Bits
• F8 - Floating Points
• B10 - Alarm and Shutdown Bits

• N11 - Analogs and discretes for display
• F13 - Program Constants

The Turbotronic 4 control system uses RSLogix 5000
as the programming software. In this program data
files such as those shown above do not exist. RSLogix
5000 uses TAG ADDRESSING.
A tag is just a text-based name for an area of memory
within the controller.
Since Tags are not grouped together in data files, the

organization of Tags is essential both to understand,
and to comply with according to the many conventions
that have been established. Otherwise the project
software would quickly degenerate into a mass of
confusing data and structure.

TAG DEFINITION
To create a new tag, three items need to be defined:
1. Tag Name
2. Tag Scope
3. Data Type
Tag Name
The new tag name must comply of certain RSLogix

5000 requirements. It can be a maximum of 40
characters, and should not contain any spaces
or certain non-standard characters. Pressing the
spacebar when typing a tag name will generally enter
an underscore to separate the parts of the tag name.
The new tag must also comply with many Solar

naming conventions. Some of these conventions are
necessary purely for ease of understanding, while
others are essential to allow certain software tools or
display functions to operate correctly. These Solar
conventions will be explained as various different
types of tags are introduced in the course of this lesson.
Tag Scope
It should have been noted already that several

different databases exist within the structure of an
RSLogix 5000 project. The controller has its own tag
database (automatically created when the project
was created), and each of the programs will have
their own tag database (automatically created when
that program was created). Figure 6.1 illustrates
this point - note the controller tag database and the
Program tag databases within the Framework and
Sequence programs.
Tag Scope simply means the database where that tag
resides. When creating a new tag you can specify if it is
to be Controller Scoped (it will appear in the controller
tag database) or Program Scoped (it will appear in the
tag database of the program you are working in).

The most important factor when defining tag scope is

the following:
• Controller Scoped tags are available to any or
all programs within the Task.
• Program Scoped tags are available only in the

program to which it is assigned.
In view of the above conditions, it would be possible to

create all tags in the controller tag database, however
in practice this would be very difficult to manage.
Figure 6.1 Controller and Program Tag Databases

TAG DATA TYPE

Data Types fall into one of three categories:
1. Pre-Defined
2. Module-Defined
3. User-Defined
Pre-Defined
These are commonly used memory sizes or tag
structures that are already defined in the software.
Figure 6.2 shows where a full list of the pre-defined
data types can be found in RSLogix 5000.
Figure 6.2 Pre-Defined Data Types

Table 6.1 is a listing of the common pre-defined data

types used in a typical Solar application, and their
most common usage:
Table 6.1 Pre-Defined Data Types
Pre-Defined Data Types
BOOL Boolean 1 Bit On/Off Discrete inputs, outputs,
alarms, etc.
SINT Short Integer 8 Bit (± 128) Group together 8 Bools on an
I/O module
INT Integer 16 Bit (+32,768) Unscaled analogs; group
together 16 Bools on an I/O
module
DINT Double Integer 32 Bit (+2,147,483,648) Group together 32 Bools for
data transfer
FLOAT Floating Point 32 Bit floating point numbers Scaled analog values
TIMER Group of multiple data types Time events
COUNTER Group of multiple data types Count rung transitions
Module-Defined Data Types

A data type assigned to a tag that is automatically
generated when a communications or I/O module is
added to the I/O configuration. Typical tags of this
type will perform module or channel diagnostics,
and also will correspond to the input or output data
channels (discrete or analog) for I/O modules.
Figure 6.3 illustrates where the module-defined data

types can be found in RSLogix 5000, with the 1794-IE8
module (eight channel analog input) illustrated. Note
the combination of channel input data and diagnostic
tags.

Figure 6.3 Module Defined Data Type
User-Defined Data Types
RSLogix 5000 allows data types to be created. This

is typically used to group together other data types
to suit a particular purpose. An analogy would be
a condition where the Timer had not already been
created as a Pre-Defined data type. It would be
possible to create a Timer by grouping together
multiple pre-defined data types. In fact the Timer
comprises two DINTs (Preset and Accumulated) and
seven BOOLs (Enable, Timer Timing, Done, etc).
A User-Defined Data Type (UDT) is simply a structure

that is created by the user to group data for a specific
application. Figure 6.4 shows where the User-Defined
Data Types can be viewed (and also created and
modified) in RSLogix 5000. The most common Solar
UDT is shown the UDT_Analog, and this comprises
four members (three Floating Point numbers, and a
text string). Applications of the various UDTs will be
covered later in the lesson.

Figure 6.4 User-Defined Data Types
CONTROLLER SCOPED TAGS

The controller-scoped tags are those tags accessible
by all programs. They are the tags that interface the
controller to the outside world and pass data between
programs. While there are quite a few tags shown in
the controller tag database, they all can be divided
into 5 different categories:
1. I/O Interface default tags for physical inputs and

outputs added by configuring I/O modules.
2. HMI tags that send data to the display.

3. Program Response tags used to transfer data
between programs.
4. Remote Inputs tags that receive commands from

the customer DCS.
5. Comms Modules tags that send and receive data

for communication modules.
The most common example for everyday monitoring,

troubleshooting and basic editing of a Solar project
will be covered in the remainder of this lesson.

I/O Interface Tags

The I/O interface tags make up the largest proportion
of the controller scoped tags. RSLogix 5000
automatically creates I/O Interface Tags whenever the
I/O configuration is completed. They are therefore
really module-defined tags.
During the I/O configuration process when the project
is initially created, or in the event of adding a new
node or modifying a node at a later date, RSLogix 5000
will automatically add the requisite module-defined
tags to the controller tag database for each module
in the I/O configuration. In the case of I/O Interface
Tags the tag name that will be adopted by each tag
follows specific rules:
The first part of the tag name will be the name of the
relevant ACNR for that node. The name chosen for
the ACNR is irrelevant as far as RSLogix 5000 is
concerned, however it should follow Solar naming
conventions.
• ACNRs are given the Reference Designator

prefix of UF.
• The four-digit number that follows should begin

with 2 (indicating the physical location of the
device is in the control console).
• The middle two of the four digits are the
ControlNet Node number.
• The final digit of the four is always 0.
Example:
The ACNR on Node 6 will have the Reference
Designator on Solar drawings of UF2060. This should
be the name allocated to the ACNR during the I/O
configuration process ( see Figure 6.5).

Figure 6.5 ACNR Naming Conventions
The programmer would then proceed and add each

of the I/O modules on that node, selecting the AB
catalog number from the options list to identify each
module to the software. The Solar naming conventions
should also be followed:
In the example of Node 6, the module in the slot

nearest the ACNR (Slot 0) will have the Reference
Designator / name of ZF2060. The next module would
be ZF2061, and so on up to a possible maximum of
ZF2067.
Using ZF2063 (an AB1794-IB16, or 16-channel

discrete input module) as an example, the
module-defined tags (I/O interface tags) for the
sixteen input channels would then take the names
UF2060:3:I.0 thru UF2060:3:I.15.

Figure 6.6 I/O Interface Tags (Discrete Input)
Using Channel 2 as shown in Figure6.6 as an example:

• UF2060 ACNR on Node 6
• 3 Module 3
• 1 Input
• 2 Channel 2
Figure 6.7 I/O Interface tags (Analog Input)

Figure 6.7 illustrates another example of I/O Interface

Tags, this time for an 8-channel analog input module.
Taking the address UF2080:5:I.Ch3Data as an
example, the structure of the address is as follows:
• UF2080 ACNR on Node 8
• 5 Module 5
• 1 Input
• Ch3Data Channel 3
Base Tags and Alias Tags
Tags of this nature in the controller tag database

(directly related to an I/O module input or output
channel) are known as Base Tags.
If we connect a new device to the discrete input

channel used in the above examples, and create logic
in one of the programs to process the data from this
new device, then it would be possible to directly
address (or use) the base tag, since controller-scoped
tags are accessible by all programs.
Let us further consider this simple example of logic.

We have a pushbutton with the reference designator
S123, and it is connected to Channel 2 of the Discrete
Input Module ZF2063. We know that the base tag
that has already been allocated to this physical input
channel is UF2060:3:I.2.
When the pushbutton contacts are closed, we want

to turn on an indicator lamp with the reference
designator DS123. This is physically connected to
Channel 4 of the Discrete Output Module ZF2062.
Again we should be able to work out the tag associated
with this output channel UF2060:2:O.Data.4. Note
that the slightly different appearance of this tag is
due to the way that the discrete output module groups
together the eight Boolean channels as SINT data.

The ladder logic for the above would be as shown

in Figure 6.8.
Figure 6.8 Logic Using Controller Tags
This logic will function perfectly well, however when

monitoring the logic it would be difficult to understand
the actual function of the rung, without constantly
consulting the electrical schematics.
One solution is to use a programming technique called

Base Tags and Alias Tags.
An Alias Tag is simply a second text-based name

for the same area of memory in the controller. It
will therefore reflect the same value as the tag it is
pointing to (the Base Tag).
When we create a tag for the new device, it is good

practice to create that tag in the tag database of the
relevant program. That way all of the tags related to
the Lube program (for example) can be easily found in
the Lube program tag database. Figure 6.9 shows a
new program scoped tag being created. Note that the
tag name being entered (S123 and DS123) are alias
tags, and that the second field from the left enables
the base tag to be selected from the controller tag
database (when appropriate). The base tag will also
appear in the third field from the left.
Figure 6.9 Designating Base Tags

By following certain conventions for naming alias tags

the logic will become easier to understand. The tag
name should be the same as the reference designator,
but dashes should be replaced with underscores. If our
example used above had been switch S123-1, then the
alias tag would have been S123_1.
The reference designator selected for the tag name

should be the ultimate electrical device to be controlled
or monitored in the electrical schematic. For example
if B300-1 is directly controlled by interposing relay
K200-1, which is wired to the I/O channel, the tag
name should be B300_1 not K200_1. Similarly if
RT300 is wired through IS isolator ZS200-25 the tag
should be RT300 not ZS200_25.
Using the new program-scoped alias tags in our simple

logic example, it will now look like Figure 6.10.
Figure 6.10 Logic Using Alias Tags
In summary, using alias tags (and following naming

conventions) makes the logic easier to understand,
and also allows tags to remain in the tag database
related to the program in which they will be used. The
use of alias and base tags is not limited to physical
I/O, as the same technique is used when processing
discrete and analog data for the display system.

STUDENT EXERCISE – Alias and Base Tags

Monitor the Lube Oil tag database, and state the scope
of the tags, the data type, and the Base Tag (if any).
Spare rows have been included to allow the

instructor to add more examples, if required.
TAG SCOPE DATA TYPE BASE TAG
S322-5 Program BOOL UF2080:2:I.2
Pre-Lube Complete
AL_S322_5_Fail
RT390
S324-1

TAG SCOPE DATA TYPE BASE TAG

PROGRAMMING EXERCISE #3 - Creating I/O Tags

1. Refer to the exercise scenario in Appendix A.
2. Use the I/O Listing Report created in an earlier

lesson to identify spare channels for the physical
I/O called for in the scenario:
a. Discrete Input
b. Discrete Output
c. Analog Input
3. Complete the table in Appendix A with the Base

Tags for these spare channels.
4. Complete the table in Appendix A with the Alias
Tags for these spare channels.
5. Edit the new program tag database to add tags
for the Discrete Input.
a. Observe Solar naming conventions

b. Ensure that the correct base tag is allocated
c. Ensure that the description field is

completed.

for the Discrete Output.
a. Observe Solar naming conventions

b. Ensure that the correct base tag is allocated
c. Ensure that the description field is

completed.

HMI TAGS
The HMI tags are used to transfer data to the display
devices. The tags are grouped together within the
controller tag database in a series of Arrays (groups of
similar data). Figure 6.11 illustrates the HMI Arrays
in a typical project.
Figure 6.11 HMI Arrays

These tags can be functionally divided into two groups.
Either they are individually updated every scan in
each of the various programs, or they are updated as a
group at regular intervals to be sent to the display.
Table 6.2 HMI Array Update

HMI Array Update
Updated Each Scan Updated At Regular Intervals
HMI_Alarm X
HMI_FSLO X
HMI_FSNL X
HMI_CDLO X
HMI_CDNL X
HMI_STATUS X
HMI_Analog_Array X
HMI_Discrete_Array X
HMI_Snapshot_Array X
The tags in the first group are the ones that are used
as the base tags for program-scoped alias tags. Their
use will be described in the following sections.

At regular intervals (typically every second) the

HMI program will load the Boolean tags from that
group into the HMI_Discrete_Array, and load the
HMI_Analog_Array into the HMI_Snapshot_Array.
The data is then available for the display and will not
be over-written until the display update is complete.
The following figures illustrate the structure of each

of the HMI Arrays on a sample project. Although
the principle will be the same on all projects, the
exact details may differ slightly between projects
(for example the number of HMI_Alarm arrays may
change according to the complexity of the project).
HMI_Alarm Array
Expanding the HMI_Alarm Array folder reveals seven
arrays of the data type DINT - see Figure 6.12.
Figure 6.12 HMI Alarm Arrays

Expanding each array reveals the 32 bits that

comprise the DINT data type one for each alarm see
Figure 6.13. All HMI tags should be used sequentially,
and when programming a new alarm (for example) the
first spare alarm should be used, and the description
field annotated to indicate that the alarm is now used.
Figure 6.13 HMI Alarm Array [0]

HMI Shutdown Arrays

Figure 6.14 shows the four array groups associated
with the different types of shutdowns used by Solar. A
different number of arrays in each type is dependent
on the project requirements. Expanding each array
would reveal 32 available bits as shown in the
HMI_Alarm array in Figure 6.14.
Figure 6.14 HMI Shutdown Arrays

HMI_Status Array
Figure 6.15 shows the HMI_Status Arrays. On the
sample project it comprises 5 DINTs each consisting
of 32 bits. The Status array is used to pass discrete
status data to the display. For example in the fuel
program logic will be written to energize an OTE when
ignition is successful. This OTE will have an alias tag
that has the base tag HMI_Status [0].17. This tag can
then be used in the display system to highlight text on
the display screen to indicate the state of the package.
Figure 6.15 HMI_Status Array

HMI_Discrete_Array
Figure 6.16 shows the HMI Discrete Arrays on a
sample project. Note the large number of DINTs
(each consisting of 32 bits) used. This is because
the HMI Discrete Array is used to load all of the
discrete data from the other arrays, to be passed to
the display at regular intervals. This function is fully
automatic, so it should never be necessary to edit the
HMI_Discrete_Arrays.
Figure 6.16 HMI_Discrete_Array

HMI Analog Array

The HMI_Analog_Array is used to pass analog data to
the display. On this sample project it comprises 134
REAL numbers see Figure 6.17.
Figure 6.17 HMI Analog Array

HMI_Snapshot_Array
The HMI_Snapshot_Array (shown in Figure 6.18)
performs the same function for analogs that the
HMI_Discrete_Array does for discretes - it loads
up with analog data at regular intervals, and
is then transmitted to the display. As with the
HMI_Discrete_Array this function is automatic, so
editing of the HMI_Snapshot_Array should not be
necessary.
Figure 6.18 HMI Snapshot Array
Program-Scoped HMI Tags
The section above covered the controller-scoped HMI

tags that will be passed to the display system, and
these are also an example of Base Tags.
The logic that generates data for these tags (alarms,

shutdowns, status bits, analogs, etc.) will obviously
be generated in one of the programs in the task. In
a similar way that program-scoped alias tags are
created for the physical I/Os, program-scoped alias
tags are also created for these HMI tags.

These alias tags should all comply with specific

naming conventions. The first convention concerns
a prefix, as shown in Table 6.3. These prefixes are
essential for two reasons:
1. To make the logic easily understandable
2. To comply with TT4000 display system tag

naming conventions
Table 6.3 Program Scoped HMI Tag Prefixes
Tag Prefix Data Type Description
AL BOOL Alarms - Alias of bit in
HMI_ALARM
CN BOOL Cooldown - Non-Lockout Alias of
bit in HMI_CDNL
CL BOOL Cooldown Lockout Alias of bit in
HMI_CDLO
FN BOOL Fast Stop - Non-Lockout Alias of
bit in HMI_FSNL
FL BOOL Fast Stop Lockout - Alias of bit
HMI_FSLO
ST BOOL Discrete display status Alias of
HMI_STATUS
AN REAL HMI analog display
Alias of element in
HMI_ANALOG_ARRAY

HMI Alarm And Shutdown Tags

The alias tag for an alarm or shutdown generated in a
program should consist of three parts:
1. A prefix specifying the type of alarm or shutdown

see table 6.3.
2. The tag name should relate to the field device

where possible.
3. One of the five possible suffixes listed in Table

6.4.
Table 6.4 Alarm and Shutdown Tag Suffixes
Tag Suffix Description
_LL Low level, temperature, pressure etc. Shutdown
_L Low level, temperature, pressure etc. Alarm
_H High level, temperature, pressure etc. Alarm
_HH High level, temperature, pressure etc. Shutdown
_Fall Transmitter failure
Figure 6.19 shows an example of an alarm. Note

the alias tag (AL_TPD397_H) and the base tag
(HMI_ALARM[4].26). Also note that the correct
instruction for an alarm or shutdown is an OTL.
Once activated the alarm or shutdown will remain
active until the rung transitions to false, and the
common malfunction reset logic is initiated (in the
HMI program).
Figure 6.19 Alarm Logic Example

Figure 6.20 illustrates the process of creating an

alarm tag, using the same example. This is very
similar to the process of creating an alias tag for a
physical I/O. Once the first spare member of the HMI
Array has been identified (in this case the HMI_Alarm
Array) and the description entered in the controller
tag database, it is a simple process of typing the new
alias tag name in the first column, and selecting the
base tag in the second column. The final step would
be to enter a description in the description field (not
visible in Figure 6.20).
Figure 6.20 Creating a New Alarm Tag

Also note that the tag description information is

essential. When the TT4 tools generate the TT4000
database, it uses the alias tag name as a short
descriptor, to appear in the banner along the top of
all screens, and the alias tag description as the long
descriptor, to appear in the alarm summary and
discrete event log. An alternative view of the tag
properties is shown in Figure 6.21. This window can
be opened by right clicking the tag in the logic, or in
the tag database, and selecting Edit Tag Properties
from the options list.
Figure 6.21 Alarm Tag Properties
It is also essential to add a tag description in the

controller tag database when selecting a spare HMI
Array element for use as a base tag. This is to ensure
that other personnel know that the tag is now used.
The process to create new shutdowns is identical, with

the added steps of identifying the type of shutdown
required (FN, CN, FL, CL); choosing the first spare
from the correct HMI Array; and using the correct
prefix from Table 6.3.

HMI Status Tags

The HMI_Status_Array is used to transmit status bit
information to the display. As with the other controller
scoped HMI tags the tags in the HMI_Status_Array
are Base Tags. The status information is obviously
generated in one of the programs, and once again a
program-scoped alias tag should be created for the
controller scoped base tag.
An example of logic for a status bit is shown in Figure
6.22. Note the correct prefix (ST_) for the alias tag,
and the base tag (HMI_STATUS[3].19). Also note that
the correct instruction for the status bit is normally an
OTE, since there is no common mechanism to reset
status bits, they are active or inactive dependent
on the rung condition.
Figure 6.22 Status Bit Logic Example

When the TT4000 tag databases have been compiled,
the status bit will be available in the display system,
and will normally be used to activate highlighted
text (in this case when the daily backup lube pump
check is in progress).

Internal Program Scoped Tags

Figure 6.22 also illustrates a type of tag that although
program-scoped, does not have a base tag. Note that
the tag Backup_Pump_Test is a Boolean tag that
has been created in the program tag database as an
internal bit to be used to control or sequence different
parts of the logic. In fact the same tag is used in the
branch shown in Figure 6.22 as a latching mechanism
for the duration of the backup pump test. The naming
convention for this type of tag is simply to give it a
descriptive name, each word beginning with a capital
letter, and separated by an underscore.
Figure 6.23 illustrates this tag in the program tag

database. Note the absence of a base tag in the second
and third columns, and that the data type was defined
as BOOL during the tag creation process.
Figure 6.23 Internal Tag Example

Timers and Counters

Other examples of program-scoped tags that do not
have base tags are Timers and Counters. Figure 6.23
also illustrates a timer. When creating this tag the
base tag fields are again left blank, and the data
type is defined as TIMER. Figure 6.24 illustrates
the expanded timer, where the Preset value can be
entered. This particular timer has a Preset value
of 120000 milliseconds, so would be a 120 second
timer (all timers all in milliseconds). Note the naming
convention for a timer it should have a descriptive
name followed by a suffix of TON (for Timer On Delay
type timers). Timer Off Delay timers would have a
suffix of TOF. The timer - is now available for use in
the logic. Note that the tag creation is identical for a
TON or TOF timer, other than the suffix used. The
designation of whether the timer will function as a
TON or TOF is completed in the ladder logic when
selecting the type of instruction associated with the
new tag.
Figure 6.24 Timer Expanded
The same process would be used to create a counter,

except that COUNTER would be defined as the data
type. The suffix used with a counter will be CTU (for a
Count Up). The Count Down counter is not used by
Solar, but would have a suffix of CTD.

PROGRAMMING EXERCISE #4 - Creating HMI Tags

2. Refer to the controller tag database and identify

the first spare HMI Array elements called for
in the scenario:
a. Filter DP Alarm,
b. Transmitter Fail Alarm,
c. Status Bit.
3. Complete the table in Appendix A with the Base

Tags for these HMI Array elements.
4. Complete the table in Appendix A with the Alias
Tags for these HMI Array elements.
for the HMI Array elements identified.
a. Observe Solar naming conventions,
b. Ensure that a description is entered for

the Alias Tag,
c. Ensure that a description is entered in the
controller tag database.
6. Edit the new program tag database to add a

new tag for the Timer On Delay called for in
the scenario.

b. Ensure that a description is entered,
c. Ensure that the correct Preset value is

entered.

NOTES:

ANALOG DEVICE PROGRAMMING
Scaling of Analogs
Analog input devices (transmitters, thermocouple,
RTDs, speed pickups) provide an electrical signal
to an input module channel. The input module will
convert this electrical signal to data, in the form of
an integer value. The values vary from module to
module, and also depend on the channel configuration
options on any particular module. As an example, a
1794-IEB module for analog input signals will convert
a 4-20mA signal to an integer value ranging between
6240 and 31200 (when the input channel is configured
as 0-20mA).
The algorithms in the control program utilize scaled
values (expressed in Engineering Units) to perform
the necessary calculations to monitor and control the
package. Therefore, input data must be converted
from unscaled counts (raw) values into scaled values
to enable the control algorithms to function correctly.
By the same token analog outputs that are calculated
in the logic will be in engineering units (often %
command), and need to be converted back into an
integer value for the analog output module (normally
0-30840). The module will then convert this integer
value back into an electrical signal (normally 4-20mA).
Analog Input Scaling
Solar employs a Universal Equation to calculate the

analog input conversion factors:
Figure 6.25 Analog Equation
Where:

VEU = Value in Engineering Units

I = Signal current from transmitter = mA
IMIN = Minimum signal from transmitter (typically
4 mA)
IMAX = Maximum signal from transmitter
(typically 20 mA)
RMIN = Minimum value of transmitter range, in
Engineering Units
RMAX = Maximum value of transmitter range, in
Engineering Units
Example:
Most analog inputs are connected to 1794-IE8 Analog

Input modules, set to the 0-20 mA range.
The standard transmitter provides a 4 (IMIN)-20
(IMAX) mA signal, proportional to its range in
engineering units.
In this example, the transmitter range is 0 (RMIN)-100
(RMAX) psig.
In the 0-20 mA range, the 1794-IE8 module will

actually read inputs between 0 and 21 mA, and will
generate corresponding proportional outputs between
0 and 32,760.
Thus, I (signal current from the transmitter) can be

stated as: 32,760/21 = 1560 counts per mA.
NOTE
The 0-20 mA range is used to facilitate
transmitter error detection. If the current
from the transmitter is below 2.0 mA (3120)
or above 20.5 mA (31980), program logic will
annunciate a transmitter failure.

The factors to be used in the Universal Equation

then become:
I = N/1560
N = Raw integer value (ranging between 6240
and 31200)
IMIN = 4 mA, or 6240
IMAX = 20 mA, or 31,200
RMIN = 0 psig
RMAX = 100 psig
With these values, the equation becomes:
Figure 6.26 Analog Equation Using Counts
The equation and the conversion process are applicable

to any analog module or transmitter used by Solar.
However note that slightly different Raw Value ranges
may be used for different types of input modules, and
this should therefore be checked when scaling analogs.
NOTE
Refer to the Analog Scaling handout for more
details on the correct values for different
types of input and output modules.

NOTES:

STUDENT EXERCISE – Analog Scaling
Using the above equations in Figure 6.25 and 6.26,

and a 0-100psig transmitter, complete the following
table for the different values specified.
Table 6.5 Analog Scaling Student Activity

VEU I RAW COUNTS
8mA
12mA
18.5mA
12480
18720
30000

NOTES:

SCALING ANALOGS IN RSLOGIX
Tag Naming Conventions

As with the discrete inputs and outputs, the alias
tag for analog inputs should have the same name as
the reference designator of the ultimate field device,
except with an underscore replacing any dashes.
For example:
• TP363_1
• TPD345_2
• RT380
• TC382_1
UDT Analog
To facilitate the conversion of the integer value from

the input module a User Defined Data Type has been
created - the UDT_Analog.
This data type has 4 members:

• The Val member will store the scaled value of the
analog input and is the only member updated
by the logic.
• The EuMin and EuMax members contain the
input Engineering Unit Minimum and Maximum
values (i.e. the range of the transmitter).
• The Eu member is a string that can hold up to 20
characters. It contains the engineering units that
the scaling will represent. Values such as psig,
and degF can be found here. This information is
not used by RSLogix 5000, but will be used by
the display system.

Figure 6.27 UDT_Analog
Remember the UDT_ANALOG is a data type, not

a tag. In other words it allows multiple tags to be
created that use this data type (just like the creation
of multiple timers or counters). Figure 6.28 illustrates
the tag Header_Pressure that has been defined
as a UDT_ANALOG. After expanding the tag the
programmer would then enter data in the other
fields (EuMin, EuMax and Eu). The Val field should
remain blank, as this will be updated by the logic (the
example shows 37.5, as this was the value when the
program was last saved).
Figure 6.28 Header Pressure UDT Analog
Figure 6.29 is an example of the logic typically used

to accomplish scaling and error detection in RSLogix
5000.

Figure 6.29 Transmitter Scaling and Fail Detection Logic
First we will examine the Compute Instruction that

is used to scale the input signal.
The tag TP380 is an Alias for the raw value (number
of counts) from the transmitter. Firstly the offset of
the transmitter range is subtracted (6240 = 4mA), and
then the value is divided by the span of the transmitter
(24960 = 16mA). The result is a ratio between the
actual input value and the span of the transmitter.
Now look at the part of the expression in the second

set of parentheses. Rather than enter the range
of the transmitter directly, Solar use part of the
UDT_ANALOG to specify the range of the transmitter.
If the transmitter is ranged from zero, then most of
the expression is effectively redundant. However,
Solar convention is to use a standard expression for all
analogs, with the added advantage that this structure
is required to compile the TT4000 tag databases
correctly.
If this is now multiplied by the value obtained
previously we obtain a value of the transmitter input
in Engineering Units.

One final step is required - the EuMin from the

UDT_ANALOG is added to the result, again to account
for a transmitter that is not scaled from zero. This
gives a final value in Engineering Units, and this is
registered as the VAL member of the UDT_ANALOG.
This VAL will now be referenced throughout the
program to generate alarms, shutdowns, etc. Figure
6.30 illustrates Header_Pressure.Val being used
to generate a shutdown.
Figure 6.30 Header Pressure Val Reference
Moving Analogs to the Display
The scaled analog value is also required for display on

the HMI display. It must therefore be transferred to an
element of the HMI_Analog_Array. Referring back to
Figure 6.29 this is completed in the MOV instruction.
Note that the MOV instruction must be located in a
branch around the CPT instruction for the TT4000 tag
database compiling tool to function correctly.
As with the other HMI Array elements a
program-scoped alias tag is created for the first spare
controller-scoped HMI_Analog_Array element. Note
the naming convention used - the alias tag has the
prefix AN_, in order to comply with TT4000 tag
database requirements.
Transmitter Fail Logic
Next we will examine the transmitter fail logic in the

top rung of Figure 6.29.
Solar standard logic requires a transmitter fail alarm
or shutdown to be annunciated if the transmitter
signal exceeds 20.5mA or becomes less than 2mA.
This accounts for the values of raw counts within the
LIM instruction.

Solar use a LIM instruction to monitor for transmitter

failure. In order for the shutdown NOT to be active
(i.e. the transmitter signal is healthy), the rung must
remain false. Table 6.6 uses information extracted
from the RSLogix 5000 Instruction Help file, and
describes the operation of the LIM instruction.
Table 6.6 Program Scoped HMI Tag Prefixes
LOW LIMIT TEST VALUE INSTRUCTION CONDITION
≤HIGH LIMIT EQUAL TO TRUE
OR BETWEEN
THE LIMITS
≤HIGH LIMIT NOT EQUAL TO FALSE
OR OUTSIDE
THE LIMITS
≥HIGH LIMIT EQUAL TO TRUE
OR OUTSIDE
THE LIMITS
≥HIGH LIMIT NOT EQUAL TO FALSE
OR OUTSIDE
THE LIMITS
Referring to Table 6.6 we can see that if we have

the Low Limit as the higher number the rung will
remain false if the signal from the transmitter is
between the two limits.
The decision on whether a transmitter failure should

annunciate an alarm or a shutdown, and the type of
shutdown (i.e. Fast Stop or Cooldown Stop; Lockout
or Non-Lockout) is made by the design engineer,
and is largely based on the actual function of the
transmitter. For example, if data from a transmitter
generates a Fast Stop Lockout shutdown in the logic,
then the failure of the transmitter would normally
also generate a Fast Stop Lockout shutdown. On the
other hand if the data from the transmitter only
generates an Alarm, or is only used for information
purpose, then the failure of that transmitter would
generate an Alarm.
In our example failure of the transmitter will latch

the OTL HMI_FSLO[2].19 with the alias tag:
FL_TP380_Fail.

NOTES:

PROGRAMMING EXERCISE #5 - Creating Analog Tags

2. Refer to the address table in Appendix A.

3. Edit the new program tag database to add a new
tag for the analog input:
b. Ensure that the correct base tag is

allocated,
c. Ensure that the alias tag description field
is completed.
4. Edit the new program tag database to add a tag
to scale the analog input:
b. Ensure that the tag description field is

completed,
c. Ensure that the data type is selected as
UDT_ANALOG,
d. Enter the EuMin, EuMax and Eu, as called

for in the scenario.
5. Refer to the controller tag database and

identify the first spare element in the
HMI_Analog_Array.
6. Complete the table in Appendix A with the base

tag for this HMI_Analog_Array element.

7. Edit the new program tag database to add a new

alias tag for the HMI_Analog_Array element
identified.
b. Ensure that the correct base tag is

allocated,
c. Ensure that a description is entered for

the alias tag,
d. Ensure that a description is entered against
the base tag in the controller tag database.

PROGRAM CONSTANTS
Solar use program constants throughout the logic
to create a formalized structure for setpoints or
tuning parameters. Some of the constants are deemed
suitable to be modifiable from the TT4000 display
Program Constants screen, i.e. without the need for
a programming terminal. These constants can only
be modified within a fixed range, and therefore the
UDT_ANALOG is a suitable data type to manage this
function (due to the EuMin and EuMax elements), as
will be seen.
Program constants that can be modified using the
display will be given the tag prefix KT_ (for Tunable),
and will then be automatically added to the TT4000
display tag database when the compiling tool is
executed. Program constants that are deemed to be
unsuitable to be modified from the display will be
given the tag prefix KF_ (for Fixed), and will then be
ignored by the TT4000 tag database compiling tool.
Figure 6.31 UDT Analogs Used As KVALS

Those familiar with the TT2000 display system used
earlier by Solar may remember the KRG file that was
used to specify the permissible range of the constant.
The TT4000 display does not have a KRG file like the
TT2000 display, therefore the EuMin and EuMax
members of the UDT_Analog are used to perform this
function. The Val member is the actual value of the
constant that is in force.

Figure 6.31 illustrates a KF and a KT from a

sample Lube program. Note the arrangement of the
UDT_Analog members for each type:
• KF EuMin, EuMax and Val all have the same
value. The Val will be referenced in the logic as
the actual constant.
• KT EuMin and EuMax specify the range. The

Val will be referenced in the logic as the actual
value of the constant.
• The use of a KVAL is illustrated in Figure 6.32.

We can confirmation that the Val is used as the
actual constant, and this is true irrespective of
whether a KT or KF is used.
Figure 6.32 KVAL Being Used

PROGRAMMING EXERCISE #6 - Creating Program Constants

2. Edit the new program tag database to add the

tunable constant for the alarm setpoint, as called
for in the scenario.

b. Ensure that the tag description field is
completed,
c. Ensure that the data type is
UDT_ANALOG,
d. Enter the allowable range of the constant

in the EuMin and EuMax fields.
e. Enter the Eu.

PROGRAM RESPONSE TAGS

Each program will produce certain data (both analog
and discrete data) that needs to be used by other
programs.
Typical examples are as follows:
• Fuel Program generates NGP - used by Start

Program for multiple functions. Used by Lube
Program for pressure scheduling and other
functions.
• Lube Program generates “Lube Required” status

- used by Enclosure Program to turn on the
enclosure ventilation fan.
As we know already the tags associated with NGP

and Lube Required will be program-scoped tags,
and therefore only available to the Fuel Program or
Lube Program respectively.
If we need these tags to be used within other programs,

we could create these tags as controller-scoped.
However, since every program will have several tags
like this, it would result in a large number of random
tags throughout the Controller Tag database, and
remove important tags from the applicable Program
Tag databases. While this system would operate
correctly, it would result in poorly organized databases
and would therefore be more difficult to follow.
Each program within the project that needs to pass

data to another program will have a structure created
within the Controller Tag Database that will contain
a member for each piece of data that needs to be
used by another program. These members are called
Program Response Tags.
By using the Program Response Tag structure, we can
allow data to be passed between different programs,
while maintaining more structured databases.
Figure 6.33 shows examples of Program Response
Tags within the Controller Tag Database.

Figure 6.33 Program Response Tags
Note the Data Type column in Figure 6.33 - all of

the Program Response tag structures are of the type
UDT or User- Defined Type. In other words they are
a unique data type that the programmer specifies in
the User Defined folder under the Data Type folder
in RSLogix 5000.
Figure 6.34 illustrates the range of User-Defined Data

Types, including the Program Responses (with the
Fuel_Responses indicated).
Figure 6.34 User-Defined Data Types

By double clicking the Fuel_Responses in the Data

Types folder we can see the members added by the
programmer. This is illustrated in Figure 6.35.
Figure 6.35 UDT Fuel Responses

The UDT Fuel Responses shown in Figure 6.35 is
where the programmer can define the data type. In
this case it consists of three REAL member and eight
BOOL members.
When the data type has been created, the programmer
will add one single tag to the controller tag database,
with the name PGM, followed by the source program
(in this example PGM_Fuel). This is illustrated in
Figure 6.36.

Figure 6.36 UDT Fuel Responses in Controller Database

Note the structure of the tags within the Program
response UDTs. Each tag begins with PGM_, followed
by the name of the program that will write data to it.
The last part is the tag identifier, which is separated
from the preceding part of the name by a period.
Figure 6.37 is a graphical representation of how the
data is transferred to and from a program response
tag.
Figure 6.37 Program Response Tag Operation
Program_A writes the data to the member of the

UDT_Program_A_Response tags. Since this tag is
controller-scoped, it can be read by Program_B, or any
other program in the task.
It should be noted that in many cases there will be two

tags with the same value one will be a program-scoped
tag, and the other will be the program response

tag. Figure 6.38 illustrates an actual example of

an analog value from a sample project Ngp.Val (a
program-scoped tag in the Fuel Program) being moved
to PGM_Fuel.Ngp (a controller-scoped tag in the
UDT_Fuel_Responses tag).
Figure 6.38 Program Response Data Being Loaded

Figure 6.39 illustrates a different method of loading
data into a tag - this time Boolean data. Rather than
copying analog data using a Move instruction, the
conditions on the left side of the rung will affect the
status of two OTE instructions:
• Lube_Required a program-scoped tag that will

be used within the Lube Program.
• PGM_Lube.Lube_Oil_Required a
controller-scoped tag that will be used in other
programs.
Figure 6.39 Program Response Tag Being Manipulated

1. State the three different data type classifications

in a Solar RSLogix 5000 project.
_____________________________________________
_____________________________________________
_____________________________________________
2. State the two possible scopes that can be

specified when creating a tag.
_____________________________________________
_____________________________________________
3. State the scope of the following types of tags:
a. UF2050:2:I.3
________________________________________
b. HMI_Analog_Array [113]
________________________________________
c. HMI_Alarm [2].12
________________________________________
d. S123_1
________________________________________
e. UF2040:3:I.Ch3Data
________________________________________
f. AN_HPC_Suction_Press
________________________________________
g. FL_Lube_Temp_HH
________________________________________

4. What would be the correct alias tag for the input

from a transmitter with the reference designator
TPD357-3?
_____________________________________________
5.
Which of the following tags would be correct for

a Timer On delay instruction?
a. Valve_Check_TON
b. TON_Valve_Check
c. TIMER_ON_Valve_Check
d. Valve_Check_TIMER_ON
6. State the purpose of the Program Response tags.
_____________________________________________
_____________________________________________
_____________________________________________
7. How many alarms or shutdowns can be

accommodated in each HMI array?
_____________________________________________
8. What is the data type for the members of the
HMI_Analog_Array?
_____________________________________________
9. What instruction is normally used to check an

analog input for validity?
_____________________________________________
10. What data type is used for program constants

KT and KF?
_____________________________________________
11. What instruction is used to scale an analog input
in a Solar RSLogix project?
_____________________________________________

12. What are the four member of the UDT_ANALOG?
_____________________________________________
_____________________________________________
_____________________________________________
_____________________________________________
13. Describe how the VAL member of the

UDT_ANALOG is sent to the HMI for display.
_____________________________________________
_____________________________________________
14. Which of the following tags are valid, according
to Solar naming conventions?
a. AL_TP567_1_HH
b. FN_TP345_3_LL
c. KT_Underspeed_Setpoint
d. CTU_Surge Detect_Counter

NOTES:

ANSWER KEY
1. State the three different data type classifications

in a Solar RSLogix 5000 project.
Pre-Defined
Module-Defined
User-Defined
2. State the two possible scopes that can be

specified when creating a tag.
Program-Scoped
Controller-Scoped
3. State the scope of the following types of tags:
a. UF2050:2:I.3
Controller
b. HMI_Analog_Array [113]
Controller
c. HMI_Alarm [2].12
Controller
d. S123_1
Program
e. UF2040:3:I.Ch3Data
Controller
f. AN_HPC_Suction_Press
Program
g. FL_Lube_Temp_HH
Program

4. What would be the correct alias tag for the input

from a transmitter with the reference designator
TPD357-3?
TPD357_3
5.
Which of the following tags would be correct for

a Timer On delay instruction?
a. Valve_Check_TON
6. State the purpose of the Program Response tags.
To transfer data between programs,

without the requirement for a large number
of individual controller-scope tags.
7. How many alarms or shutdowns can be
accommodated in each HMI array?
32
8. What is the data type for the members of the

HMI_Analog_Array?
REAL
9. What instruction is normally used to check an
analog input for validity?
LIM
10. What data type is used for program constants

KT and KF?
UDT_ANALOG
11. What instruction is used to scale an analog input

in a Solar RSLogix project?
CPT (Compute)
12. What are the four member of the UDT_ANALOG?
VAL
EU MAX
EU MIN
EU

13. Describe how the VAL member of the

UDT_ANALOG is sent to the HMI for display.
VAL is moved to a new tag with the prefix

AN. This new tag is an alias to an element
of the HMI_Analog_Array.
14. Which of the following tags are valid, according
to Solar naming conventions?
b. FN_TP345_3_LL
c. KT_Underspeed_Setpoint



Solar Technical Training LESSON 7 - Editing a Project Offline
LESSON 7 - Editing a Project Offline
OBJECTIVES
will be able to:
1. Complete the editing exercise scenario detailed
in Appendix A, using the project elements and
tags created in the previous exercises.
INSTRUCTIONS
Using the project elements and tags created during
the previous lessons, complete the editing scenario
described in Appendix A.
Ensure that all Solar programming conventions are

complied with, and that the project is free from errors
at the end of the exercise.
This exercise may be conducted as an instructor-led

activity, or individually by the students.
NOTE
If the editing has not been completed in
stages during the previous lessons, then jump
to Appendix A now and complete the entire
editing exercise.

Solar Technical Training LESSON 7 - Editing a Project Offline

LESSON 7 - Editing a Project Offline Solar Technical Training

Solar Technical Training LESSON 8 - Hardware and Software Interface / Troubleshooting
LESSON 8 - Hardware and Software Interface

/ Troubleshooting
OBJECTIVES
will be able to:
1. Demonstrate the ability to cross-reference

physical devices on the package to RSLogix 5000
tags, and vice-versa.
2. Demonstrate the ability to trace alarm and

shutdown malfunctions through the logic, to
establish possible root causes.
3. Describe the purpose of sample programs.

4. Describe the basic functions performed by
the each of the routines included in sample
programs.

LESSON 8 - Hardware and Software Interface / Troubleshooting Solar Technical Training
TURBINE LOGIC EXAMPLE - LUBE OIL TANK HEATER

Consider the requirements for controlling a lube oil
tank heater on a turbine package. The objective is to
automatically maintain the temperature of the oil in
the tank within a specific range.
SYSTEM COMPONENTS
An electric heater is installed in the tank for this
purpose. An RTD is installed to measure the oil
temperature.
BASIC LOGICAL FUNCTIONS

The signal from the RTD is routed to the logic through
an RTD Input module, and is scaled by program logic.
This signal will be compared to preset control settings
(setpoints) to establish the desired temperature range.
Under certain conditions, it would be inappropriate
to operate the heater. These conditions include
inadequate level of oil in the tank; a package fire
detected; engine running or in test crank; detected
failure of the oil tank RTD; and a Backup shutdown
initiated.
All of these controls and safeguards can be easily

implemented using ladder logic. Refer to Figure 8.1,
which is the oil tank heater control logic from an
actual turbine package.

Figure 8.1 Oil Tank Heater Control Logic
Top Rung Description

• The scaled value representing oil tank
temperature (Tank_Temp.Val) is
being compared with a setpoint value
(KT_Heater_Imm_On.Val).
• If the measured temperature is less than or
equal to the setpoint (65.0F in this example),
the compare instruction is TRUE.
• The output instruction (OTE) at the right side of

the rung is enabled whenever the rung is TRUE,
so the internal control bit, Heater_Imm_Req is
set to the TRUE state.
• Other instructions in the program can refer to

this bit, for instance, there is an input instruction
(XIC) in the lower branch on the top rung that
refers to Heater_Imm_Req.
• This instruction will now be TRUE, and the

adjacent compare instruction will be scanned.
• The comparison instruction is TRUE because the

oil temperature is below its 70F setpoint.

• This keeps the heater control bit enabled as the

oil temperature rises above the 65F setpoint in
the compare instruction in the top rung.
• Eventually, the oil temperature will rise to
the setpoint in the compare instruction in the
branch, and the instruction will transition to
FALSE, disabling the rung and clearing the
control bit.
• The overall effect of this rung is to turn the
control bit on when oil temperature drops below
65F, and turn the bit off when oil temperature
rises above 70F.
Bottom Rung Description
• The second rung in the illustration contains

the logic required to implement the protective
permissives for the heater command output.
• All instructions in the rung must be TRUE to

enable the output instructions (OTE’s).
• One of the OTE’s activates a channel on a

Discrete Output module, which is connected to a
24 VDC contactor control relay for the heater
circuit.
• The OTE in the lower branch controls a status

bit, which is assigned to the HMI data interface.
• All of the input instructions in the second
rung are referenced to internal control bits.
Heater_Imm_Req is controlled by the logic in
the top rung, and has been discussed.
• The XIO instructions
PGM_Sequence.Start_Run and
PGM_Sequence.Test_Crank are TRUE when
the start and test crank functions are inactive.
• The XIO instruction
PGM_Enclosure.Fire_Detected
will be TRUE if no fire has been detected.
• The XIO instruction Tank_Level_LL will be

TRUE if the oil level in the tank is sufficient to
transfer the low oil level float switch to clear the
shutdown annunciation.

• If the oil tank RTD signal exceeds programmed

range limits, indicating a failure of the RTD,
the RTD monitoring logic will set the bit
RT390_Fail, and the XIO with the same tag will
be FALSE, disabling the rung.
• Finally, the XIO
PGM_Framework.BackupLatchAct will be
TRUE unless a backup shutdown is initiated.
• Any of the input instructions in the rung that
are FALSE will disable the rung and inhibit
the heater.

SAMPLE PROGRAM PURPOSE

The Lube program consists of the tag database and
routines illustrated in Figure 8.2. This includes a
Program Tags folder; Main Routine containing JSR
instructions; and a series of individual Routines for
the various sub-systems.
Figure 8.2 Lube Program
The purpose of the program is to monitor inputs

relevant to the lube oil system; establish the sequence
of operations for control of lube oil system equipment;
generate the outputs required to effect safe and
efficient control of the system; and provide outputs to
the operator interface system. Each of the routines
in the program is dedicated to accomplish specific
components of the monitoring and control process.

ROUTINE PURPOSE
Refer to Figure 8.3 for the following description:
Figure 8.3 Tank Level Switch Routine

The purpose of this routine is to monitor the status
of the oil tank level switches, and to annunciate an
alarm and/or shutdown as appropriate based on
switch status. An additional function is to control a
permissive in the oil tank heater logic.
The first rung (Rung 0) is used to facilitate addition

of the rung comment that appears at the top of the
page. The No Operation (NOP) instruction is used to
complete the rung and performs no function.
Rung 1 contains an XIO instruction and an OTL

instruction.
The XIO is referenced to a physical input and has a
base tag designated by the input channel:
UF2080 - ACNR on Node 8
I - Input Data
Data[1] - Module in Slot 1 (ZF2081)
5 - Channel 5
The XIO is actually referenced to the alias tag

(S388_1) for the above base tag. The alias tag complies
with Solar naming conventions - the Reference
Designator of the electrical end device.
The OTL will generate an alarm when activated. The

alias tag (AL_S388_1_L) complies with Solar naming
conventions. The base tag for the alarm is a member
of the HMI_Alarm Array (HMI_ALARM[4].0).

STUDENT EXERCISE - Sample Routine Function
1. Review Rung 2 in Figure 8.3, and complete the

following table.
Table 8.1 Base and Alias Tag Exercise

Instruction Base Tag Alias Tag
XIO
OTL
OTE
2. Without looking at any electrical schematics,

state whether the input channels for S388-1 and
S388-2 are connected to the switch Normally
Open or Normally Closed contact.
Normally Open / Normally Closed
3. See below for a description of the function of

this logic.

RUNG FUNCTIONS
To evaluate the functional characteristics of the logic
in the sample routine, view Rung 1 in Figure 8.4.
Figure 8.4 Rung Function
We know that the physical discrete input from S388-1

is connected to Input 5 of Module 1 in Node 08 of
the ControlNet network.
We surmise that the Normally Open contacts of the

switch are used, so that when the oil level in the tank
is above the alarm level, the contacts are closed,
connecting 24Vdc to the input terminal. Under these
conditions, the XIO instruction is FALSE, and the
rung is FALSE - no action takes place
Should the oil level in the tank fall below the switch
setpoint, the Normally Open contacts will open; the
XIO instruction will then be TRUE; and the OTL will
be activated. The Alarm bit AL_S388_1_L will be set,
and the base tag HMI_ALARM[4].0 will also be set.
Rung 2 will function in the same manner, except that

a shutdown will be activated, and the internal tag
Tank_Level_LL will be set, to inhibit the tank heater
in another part of the logic.

STUDENT EXERCISE - Routine Functions

Table 8.2 Routine Function Summary
Routine Function
010_Tank_Level_Sw_Lo_000 If S388-1 opens, alarm bit AL_S388_1_L is latched;
HMI alarm is initiated.
If S388-2 opens, shutdown bit CL_S388_2_LL
is latched; HMI CDLO shutdown is initiated, and
Tank_Level_LL is enabled to lock out the tank
heater.
The sample logic description is summarized in Table

8.2. Using this process to evaluate the functions
performed by logic routines or individual rungs as
specified by the instructor. Complete Table 8.3 with
the answers.
Table 8.3 Routine Function Summary Student Exercise
Routine Function

HARDWARE-SOFTWARE INTERFACE
As explained previously, the I/O modules perform the
conversion of digital data to electrical signals (and
vice versa). To see the complete path between an end
device and the logic, both the Electrical Schematic and
the controller program are required. The following is
an example illustrating the relationships:
In the routine discussed above
(010_Tank_Level_Sw_Lo_000), the
hardware inputs to the logic are S388-1 and S388-2.
These devices are located on the electrical schematic
sheet shown in Figure 8.5.
Figure 8.5 Base Tag Derivation

The Discrete Input module is installed in Slot 1 of

Node 08, as seen in Figure 8.6.
Figure 8.6 Node 08

The Base Tags relate to the ControlNet ACNR
reference designator (UF2080); the Discrete Input
module is in Slot 1; and the switch inputs are
connected to Channels 5 and 6. The Alias Tags S388_1
and S388_2 are assigned to these inputs in the tag
database.

The complete path for the input from S388-1 can be

described in tabular form:
Table 8.4 I/O Mapping

I/O Terminal & Wire End Device Reference
Alias Tag Base Tag Number Designator
S388_1 UF2080:1:I.5 TS309-14, S3881 S388-1

STUDENT EXERCISE - Hardware / Software Interface

Using the Electrical Schematic and control program
for your project, complete the following tables. The
first two examples are taken from the Lube Program.
NOTE
The instructor will provide additional
examples from the Lube program, or another
program.
Table 8.5 I/O Mapping Student Activity

I/O Terminal & Wire End Device Reference
Alias Tag Base Tag Number Designator
S324_1
S322-5

LOGIC FAMILIARIZATION
The remainder of this lesson comprises a series of
student exercises. The student will be directed to
navigate through common examples of turbine logic
to answer various questions. This will provide both
a better understanding of common logic functions,
and also some of the search functions necessary to
troubleshoot common system faults.
The process may also have the added benefits of

providing a recap on many of the subjects covered
in this course, and also provoking questions from
the students.
NOTE
Some of the examples may not be applicable
to all projects, and the instructor may elect
to provide other examples.

STUDENT EXERCISE - Fuel Program Familiarization
1. Open up the Fuel Program
2. Open up the Ignition routine
3. What is the Ignition Timer Preset value (in

seconds) when starting on both Gas and Liquid
fuel?
• GAS ___________________________________
• LIQUID ________________________________
4. What is the Torch Pre-Light time allowed? (Use

the cross-reference function)
_____________________________________________
_____________________________________________
_____________________________________________

5. The XIC (PGM_Sequence.Ignition) will

become false when Ignition has been successful,
to de-energize the Ignition Exciter, Torch
Solenoid, etc. Trace back through the Sequence
program to locate the rung where this instruction
is set.
• Routine name and rung number = _______
________________________________________
• The tag PGM_Fuel.Ignition is used in the
same routine. Trace this tag back to the
Fuel program and locate the routine name
and rung number where this is set, and the
basic logic involved.
• Routine name and rung number = _______
________________________________________
• T5 Value for successful ignition = _________
________________________________________
6. What are the Alias Tag and Base Tag for the
Ignition Failure shutdown?
• Alias Tag = ____________________________
• Base Tag = _____________________________

7. G340 is wired to a physical output. Use the

software and drawings to state the following:
• Base Tag = _____________________________
• Node Number = _________________________

• Output Module Reference Designator = ___
________________________________________
• Channel Number = _____________________
• Drawing Sheet Number = _______________

• Relay Reference Designator = ____________
• Relay Contacts Used = __________________

• Wire Numbers = ________________________
• Skid Terminal Strip Terminals Used = ____
________________________________________
8. Locate the Torch Solenoid (normally L340-1)

on the electrical schematic. Use the drawings
ONLY to identify the following:
________________________________________
• Channel Number =______________________
• Alias Tag = ____________________________
• Base Tag = _____________________________

9. Locate the logic that controls L340-1 in the

software by searching for the Alias Tag.
• Routine Name = ________________________
• Rung Number =_________________________
10. What else is activated when L340-1 is energized?
_____________________________________________
_____________________________________________
_____________________________________________

STUDENT EXERCISE - Analog Device Programming Familiarization
1. Use the drawings to identify the input channel

connection for the PCD transmitter.
• Device Reference Designator = ___________

• Drawing Sheet Number =________________
• Device Function = ______________________
• Transmitter Range = ____________________

• Base Tag = _____________________________
• Alias Tag = ____________________________
2. Using the I/O Configuration in RSLogix, state

the channel configuration for the above channel
• Channel Configuration = ________________
3. Why is the channel configuration different from

the range of the signal from the transmitter?
_____________________________________________
_____________________________________________
_____________________________________________
4. Locate the Alias Tag in the software for the

above device
• Program = _____________________________
5. What is the Tag name for the UDT_Analog used

to scale this input?
• Tag name =_____________________________

6. Does the Eu.Min and Eu.Max match the range of

the transmitter?
• YES / NO
7. What are the tags that send the PCD pressure

to the display?
• Alias Tag = _____________________________

• Base Tag = _____________________________
8. What type of alarm or shutdown will be

generated if this transmitter fails?
• Alias Tag = _____________________________
• Base Tag = _____________________________
9. Cross-reference PCD.Val, and identify any basic

functions of this value within the logic
_____________________________________________
_____________________________________________
_____________________________________________
10. Use the drawings to locate the output signal to

the main fuel control valve EGF388
• Sheet Number = ________________________

• Channel Number = ______________________
• Alias Tag = ____________________________

• Base Tag = _____________________________

11. Locate the logic that generates this output signal
• Routine Name = ________________________
• Rung = _________________________________
• Type of Instruction = ____________________
• Source A = _____________________________
12. Why is the tag in Source A is a member of a

UDT_Analog, even though it is not scaled using
the Eu.Max and Eu.Min?
_____________________________________________
_____________________________________________
_____________________________________________

STUDENT EXERCISE - Troubleshooting

In this exercise the student will be given a list of
alarms or shutdowns, as they would appear on the
TT4000 display screen. The student should locate the
alarm in the logic, and complete the table below with
brief details of the conditions necessary to initiate
the alarm or shutdown. In some cases the root cause
of the alarm or shutdown may not be in the same
rung, and this will therefore require some advanced
investigative skills.
NOTE
A sample range of common alarms and
shutdowns have been given, but that these
may not be applicable to all projects. In some
cases the exact tag name may differ slightly,
whilst in other cases the specified alarm or
shutdown may not exist in that project. The
instructor may elect to provide additional
examples.
Table 8.6 Alarm and Shutdown Troubleshooting

Alarm or Shutdown Description of Logic
AL_24Vdc_Supply_L
AL_RT396_H

Table 8.6 Alarm and Shutdown Troubleshooting, Contd

FN_Ignition_Fail
FN_Ngp_Over_Speed
CL_T5_TC_Fail
FN_Crank_Failed
FN_Accel_Failed

Table 8.6 Alarm and Shutdown Troubleshooting, Contd

FN_B322_Fail
FL_T5_TC_Light_Around_Fail



Solar Technical Training LESSON 9 - RSLogix5000 Online Functions
LESSON 9 - RSLogix5000 Online Functions
OBJECTIVES
will be able to:
1. Demonstrate the ability required to go online
with an RSLogix controller.
2. Demonstrate the ability to set, enable and

remove forces in the ladder logic for bit
instructions
3. Demonstrate the ability to set, enable and

remove forces in ladder logic for analog
instructions.
4. Demonstrate the ability to make simple edits to

an RSLogix program when online.
INTRODUCTION
This lesson concludes the course by allowing the
student to go online with an RSLogix 5000 Controller
and perform some simple operations when on line.

LESSON 9 - RSLogix5000 Online Functions Solar Technical Training
CONFIGURING COMMUNICATION DRIVERS

Communications between the RSLogix Controller
and external devices such as a field programming
terminal is achieved using the RSLinx application.
Within this application several different methods of
communication are available these include:
RS232 Serial Port

This is the only communications method that allows
direct communications between an external device
such as a field programming terminal and the
controller. A serial cable is connected between the
programming terminal and the serial port on the front
of the controller. Though always present as an option
for communications, this method offers relatively slow
communications and in practice is not often used.
ControlNet
This method of communications is the standard

method on Solar TT4 packages. ControlNet
communication requires the use of a special PCC
card and cable to allow communications between the
programming terminal and one of the ControlNet
modules (CNBRs) in the Controller chassis. The PCC
cable may also be connected to any of the ACNRs on
the network once the network has been scheduled to
establish communications with each of the nodes.
Desktop PCs may use a PCIC card and cable, rather
than a PCC card.
Ethernet
An Ethernet crossover cable can be connected between
a dedicated Ethernet module installed in the controller
chassis and the network port of the programming
terminal.
Whichever method is chosen for communication, the
first step will always be to set up a suitable driver in
RSLinx.

STUDENT EXERCISE - Configuring Drivers

1. Refer to the procedures outlined below, and
configure communications drivers for:
a. RS232
b. ControlNet
c. Ethernet
2. When the drivers have been configured, establish

communications with the controller through
RSLinx.
RS232 Serial Link Driver Configuration

1. Open up RSLinx.
2. Select Communications.
3. Select Configure Drivers. See Figure 9.1
Figure 9.1 Configure RS232 Driver

4. Select the RS-232 DF1 Devices driver from the

available list of driver types - see Figure 9.2.
Once a driver has been selected the Add New
button will become available.

5. Select Add New – a dialog box will open up
allowing the driver name to be entered - see
Figure 9.3.
6. Accept the default name and select OK.
7. Note that since this driver only needs to be

configured once, and will then be valid for all
projects with the same Controller type and
settings, there should be no reason to specify a
different name from the default.
Figure 9.3 RS232 Driver
8. Ensure that the serial cable is connected between

the programming terminal serial port and the
Controller before completing the next step.

9. Select the Device as Logix 5550 /

CompactLogix - see Figure9.4.

10. Select Auto Configure - see Figure 9.4.
11. RSLinx will poll the controller and automatically

configure the communications parameters.
12. A message should appear in a dialog box next

to the Auto Configure command indicating that
the operation was successful.
13. Configuration of the Serial communications is

now complete, and can be used in the RSLogix
5000 application to download to the controller,
and or go online to view or edit logic.

ControlNet Driver Configuration

1. Open up RSLinx.
3. Select Configure Drivers.
4. Select the 1784-PCC for ControlNet Devices

driver from the available driver types list.
Figure 9.5 Configure PCC Driver
5. The Add New button will become available

when a driver is selected - select Add New.
6. As with the RS232 driver, the PCC driver setup

should only be required once, and should be valid
to communicate with any system. Therefore
accept the default name and select OK. See
Figure 9.6.


7. The simplest method to complete the
configuration is to check the Auto-Address
MAC ID box shown in Figure 9.7, and then
select OK.
8. Configuration of the ControlNet driver is now

complete, and can be used in the RSLogix 5000
application to download to the controller, and or
go online to view or edit logic.

Ethernet Driver Configuration

Ethernet communications uses a system of IP
addressing, with a unique IP address for each station
on the network. Normally this is displayed on the
1756-ENBT module alphanumeric display, and
this module address will be entered in the driver
configuration.
1. Open RSLinx.
3. Select Configure Drivers.
4. Select the Ethernet Devices driver from the

list of available driver types. See Figure 9.8.
Figure 9.8 Configure Ethernet Driver
5. The Add New button will become available when

a driver has been selected - select Add New.
6. Since multiple Ethernet drivers may ultimately
be configured for each Ethernet module with
a unique IP address, at this point an easily
recognizable name can be entered to identify
the driver. For example you may want to enter
the site name and the site identification for
the package (Station_2_GT_1). For classroom
exercises you can simple accept the default name
by pressing Enter.


7. Obtain the IP address from the Ethernet module
in the 1756 chassis. Normally this is displayed
on the module alphanumeric display. Enter this
address in the Host Name entry - see Figure
9.10.
8. Select OK.

This completes the configuration of the Ethernet

driver through RSLinx. However in order to be able
to communicate with the controller, an IP address
must also be assigned to the programming terminal.
There are several ways by which this may be achieved.
The TP IP Config tool has been provided as an easy
means to set the programming terminal address.
Alternatively, a static IP address may be assigned to
the programming terminal using standard Windows
commands.
Setting an IP Address Using TT IP Config

1. Go to Start \ Programs\ Solar Turbines\
TT4000 Utilities.
2. Select and open TP IP Config - see Figure 9.11.
Figure 9.11 TP IP Config Tool
3. Select Static Address - see Figure 9.12.
4. Assign an IP address that is close to (but not

the same as) the target module IP address. For
example if the 1756-ENBT Ethernet Module IP
address was 111.111.111.111 then the IP address
of the programming terminal could be set to
111.111.111.112.
5. Assign the Subnet Mask as 255.255.0.0 (leaving

the last two fields blank will set them to 0).
6. Click the Configure Button.

Figure 9.12 TP IP Config Settings
7. A confirmation dialog box will open - click OK.

8. Minimize TT IP Config (do not close it).
9. The programming terminal should now be able

to communicate with the Ethernet module.
10. On completion of the work on the control

system, remember to reset the IP address of the
programming terminal to DHCP (auto-address)
by clicking DHCP, and then the Configure
button.

STUDENT EXERCISE - Changing an Ethernet Module IP Address

The IP address of a 1756-ENBT Ethernet Module
is typically displayed on the alphanumeric display.
However in certain circumstances it may be necessary
interrogate the module to determine the address. It
may also be necessary to change the IP address of a
new or existing module, if it is the same as another
device on the network. This exercise will cover the
procedures to determine and change an IP address.
To achieve this, communications must be established
by another method, either RS232 or ControlNet. This
exercise will use ControlNet.
1. Open RSLinx.
3. Select Who Active.
4. Browse the active stations and expand the

ControlNet driver by clicking the plus sign until
the Ethernet module is visible - see Figure 9.13.
Figure 9.13 Browsing the Ethernet Module Using Controlnet

5. Highlight the Ethernet Module, then right

mouse click.
6. Select Module Configuration - see Figure 9.14.
Figure 9.14 Ethernet Module Configuration
7. Select Port Configuration.

8. Ensure that Static Address has been selected.
9. In newer versions of RSLinx ensure that the

Obtain IP Address from Boot Server box
has not been checked.

10. Enter the new IP address and Subnet Mask in

the appropriate fields - see Figure 9.15.
Figure 9.15 Ethernet Module Port Configuration

11. Click OK to apply the new settings. Take care to
ensure that the Ethernet module is not in use, as
this will cause communications to be lost.
12. Check that the new IP address appears in the

Ethernet module alphanumeric display.
13. Close RSLinx.

Going Online
Once the communications drivers have been set up
using RSLinx, it is now possible to go online using
RSLogix 5000 to download to the controller or view
and edit the control logic software. The following will
detail the method to establish communications using
the different drivers. Complete the first portion, and
then choose one communications driver and go on to
download to the controller.
NOTE
DOWNLOAD = PROGRAMMING
TERMINAL TO CONTROLLER
UPLOAD = CONTROLLER TO
PROGRAMMING TERMINAL
1. Open up RSLogix 5000.

2. Open up the project you wish to download (or
the same project that is already resident in the
controller).
3. Selecting the Communications options

provides a list of options.
Figure 9.16 Communications Menu

4. If Who Active is clicked, a screen will appear

showing the configured communication paths.
Active nodes will be identified and flashing
symbols will highlight the active paths. Figure
9.17 illustrates the active paths with the RS232,
DF1 Driver only.
Figure 9.17 Going Online RS232
5. The procedure to go online is to simply browse

until a valid path to the controller is found. In
the case of RS232 browsing is limited to the first
level below the DF1 Driver, since the connection
is directly into the controller via the serial port.
See Figure 9.17.
6. Whenever the controller is highlighted using
a valid communications path the Go Online
option, which was previously grayed out, will
become available. Clicking Go Online will then
establish communications.

7. Figure 9.18 illustrates the same procedure

for the ControlNet driver. To connect with
ControlNet a PCC card must be installed in the
programming terminal and the cable attached to
any of the RJ45 ports in the ControlNet system.
Normally this would be in the front of one of the
ControlNet modules (CNBRs) in the chassis.
Once the controller is communicating with all of
the devices on the network, the RJ45 port on any
of the ACNRs can also be used.
Figure 9.18 Going Online ControlNet
8. The valid path this time is more complex. First

the PCC-1 Driver must be expanded and then
the path again takes the same route as the
physical connection. Therefore the next level is
the CNBR (ControlNet module), followed by
the Backplane in the Chassis, and finally the
controller. Connection via an ACNR would follow
a different, and more complex path.
9. As with RS232 when a valid path to the

Controller has been established the Go Online
option will become available.
10. Ethernet communications follows a similar path

to ControlNet, except the first level will be
the Ethernet driver, and the second level the
Ethernet module in the chassis.

11. As with the other methods, when a valid path

to the controller has been established, the Go
Online option will become available. Figure
9.19 illustrates the path to the controller using
Ethernet.
Figure 9.19 Going Online Ethernet

12. If repeatedly going online using the same path,
then the Select Recent Path option may be
useful.
13. If Select Recent Path had been specified from
the Communications options, a list of recently
configured paths would have appeared.

14. Placing the cursor on a selected path that you

know still to be valid and clicking Go Online
would have connected to the controller through
the selected path. See Figure 9.20.
Figure 9.20 Select Recent Path

Downloading
We will assume for the moment that there is currently
no program in the controller. The next step is therefore
to download a program to the controller.
1. After selecting Go Online in any of the above
methods of communication the dialog box shown
in Figure9.21 will appear. If a project is currently
open in RSLogix then this will be the Offline
Project shown in Figure 9.21. If the Offline
Project exactly matches the project in the
controller, then Go Online may be selected.
Figure 9.21 Connected to Go Online

2. If no project is currently open, or the projects do
not match, then another dialog box will appear
prompting for a project selection. Simply browse
for the required RSLogix ACD file, which should
be located in C:\JOBS.
3. Selecting Download will place the Controller in
Program Mode (if the keyswitch is in the REM
position) and download either the open project or
the selected project.

Placing the controller in Program Mode

will cause the controller to lose control
over the turbine package, resulting in a
package shutdown.
4. Figure 9.22 illustrates dialog box that opens to

request confirmation that a download is required.
Figure 9.22 Download Confirmation

5. Figure 9.22 illustrates the project in the process
of being downloaded.

Figure 9.23 Downloading To The Controller

Run Mode
When the project has been downloaded the controller
will remain in the Remote Program Mode. Refer to
Figure 9.24 and observe that:
1. Remote Program is indicated in the Controller
Status,
2. Running is not illuminated in the Controller

Status,
3. Power rails in the routines are not highlighted

green.
Figure 9.24 Controller In Program Mode

Returning the controller to Run Mode will result in

the status shown in Figure 9.25:
1. Rem Run in the Controller Status,
2. Running illuminated in the Controller Status,

3. Power Rails highlighted green.
Figure 9.25 Controller In Run Mode
This is accomplished by various methods:
1. Clicking on one of the controller icons in the

Controller status toolbar, and selecting Run
Mode and then OK in the confirmation dialog
box,
2. Selecting Run Mode from the Communications
menu,
3. Rotating the controller keyswitch to the Run
position (and then back to the Rem position if
Remote Run is desired).

Uploading
If the controller already has a program, and you
wish to go online, then Go Online would be the
option to choose. However if the projects do not match
exactly, then this will not be allowed. In this situation
uploading may be the only option.
Selecting Upload from the Communications menu
will cause the software to use the selected path to
go online, and the screen shown in Figure 9.26 will
appear.
Figure 9.26 Upload Options
If no offline file is open, as in the example in Figure

9.26, then clicking on the Select File option will
allow you to browse the C:\JOBS directory to locate
and select the same file name as the project in the
controller. Even if attempting to upload to this file
location, if the files do match exactly the upload will
abort, to protect against overwriting an existing file.
If the same project does not already exist on the

programming terminal, you can specify a file name
and a location at this point, and RSLogix will
create an offline file as it uploads, according to your
specification.

Figure9.27 illustrates the screen that appears once the

correct offline file has been selected in the C:\JOBS
directory. Note that since both the online (controller)
file and the offline (programming terminal) file are
identical the system does not require an upload so
we can simply go online. If however the files were
different we would upload.
Figure 9.27 Upload Screen
NOTE
The tag and rung descriptions are not resident
in the controller memory, therefore uploading
(other than to a file on the programming
terminal with the same name) will cause the
loss of all descriptions from the project.

Recommended Procedures
In summary, the recommended procedure is:
No Project In The Controller
1. Use the project tools to load the project from the

CD to the programming terminal.
2. Download the RSLogix 5000 ACD file to the

Controller.
Project In The Controller
1. Use the project tools to load the project from the

CD to the programming terminal.
2. Ensure that both revisions of the project software
are the same.
3. Connect to the controller and test to see if it is
possible to Go Online. If the revisions are exactly
the same then this will be possible.
4. If this is not possible then upload the project to a

temporary location.
5. Compare both projects (tools are available for

this).
6. If satisfied with the uploaded version, import

the tag descriptions from the most similar ACD
file available (tools are available for this). Then
replace the old revision in C:\Jobs with the
version uploaded from the controller. It should
now be possible to Go Online directly.

Forcing
Both Bit and Analog values can be forced (online only)
using the following procedures.
Extreme care must be taken when

creating a force. The user must fully
understand the effects of the force.
Determine the current state of forces by observing the

Forces drop-down list and the Force icon shown in
Figure 9.28.
Figure 9.28 Forcing Status

Bit Forcing
Forces are made in the routines by right clicking the
selected instruction and selecting either Force On or
Force Off. The force will not take effect immediately
unless the forces have already been enabled. This
is illustrated in Figure 9.29. Note that the three
options are:
1. Force On
2. Force Off
3. Remove Force
Figure 9.29 Creating A Force

If the drop-down list displays Forces and the icon is

Red, forces have been created but are not enabled. If
forcing is then enabled, the forces will take effect
immediately. See Figure 9.30.
Figure 9.30 Enabling Forces
If the drop-down list displays Forces and the icon

is Yellow and Red, forces are present and enabled.
Any added forces will take effect as soon as they are
created. See Figure 9.31. Note that ON has also
appeared next to the item forced.
Figure 9.31 Forces Enabled

If the drop-down list displays No Forces and the

icon is Yellow, forcing is enabled but no forces are
present. Added forces will take effect as soon as they
are created.
On TT4 projects that use RSLogix version 13 there is
an extra step needed to enable the force. As with older
versions of RSLogix the Force enable button may be
accessed by clicking on the Force Status indictor - see
Figure 9.32. Once the dialog box appears, to enable
I/O forces move the mouse over the I/O Forcing, a
second dialog box will appear allowing the forces to
be enabled, disabled, or removed.
Figure 9.32 Enabling Forces RSLogix Version 13

STUDENT EXERCISE - Bit Forcing

1. Use the project electrical schematic drawings
provided for this class to identify the alias tag for
the Pre/Post Lube Oil Pump command.
2. Use this tag to force the pump on.
3. Identify the routine where S322_5

is used to energize the Status Bit
ST_Backup_Lube_Pump_Press.
4. Force S322_5 ON and monitor the Status Bit.

5. Disable and remove all forces.

Forcing Analog Input Values

The method for setting a force on an analog value
differs from the method described above, in that the
force values are set in the Program Tag Database.
In the case of analog inputs the value to which the
analog is to be forced is entered into the Force Mask
column. The Force Mask column may be accessed
by clicking the Monitor Tags tab. The forced value
entered will not take effect until the forces are
enabled. The forces may be enabled by selecting
the Force Status button displayed on the Controller
Status Pane - see Figure 9.33.
Figure 9.33 Forcing Analog Input Values
With the forces created and enabled, the value for the
analog will display in Red if viewed from the logic
- see Figure 9.34.

Figure 9.34 Forced Analog Value
Extreme care must be taken when

creating a force. The user must fully
understand the effects of the force.
Forcing Analog Output Values

Analog Output values are not Forced, as such. The
output value may be manipulated by typing a value in
the Value field in the tag database.
However to prevent the analog value from being

over-written by the controller during the next scan
of the logic, the output value must be first isolated
from all preceding logic.
The AFI instruction may be used to disable all logic

instructions that it preceded on the rung. Remember
the controller scans left to right, top to bottom.

Figure 9.35 Forcing Analog Output Values
Extreme care must be taken when using

AFI instructions. The user should fully
understand the effect of the instruction.
Whenever instructions of this type are used, it is

always a good idea to Bookmark the rung. Adding the
Bookmark creates an easy reference by which the
instruction may be easily found and removed from the
logic on conclusion of the troubleshooting exercise, or
prior to returning the unit to operation.
Figure 9.36 Rung Bookmarks

STUDENT EXERCISE - Forcing Analogs

1. Identify the tag for the Lube Oil Header Pressure
analog input.
2. Force the analog input to 0%, 50%, and 100% of

the range. This will normally be 6240, 18720,
and 31200 counts.
3. Observe the CPT instruction that scales this

analog input in the ladder logic, and ensure that
the scaled value is registered in the Destination.
4. Identify the logic that scales the analog output

for the Main Fuel Control Valve (normally
EGF344).
5. Edit the ladder logic rung to inhibit the scaling

function.
6. Force the output value by typing in a value in
the Value field of the tag database.
7. Force output to a value corresponding to a

position of 0%, 50%, and 100% of the actuator
range. Note that the output module is normally
scaled 0 to 30840 counts for 4 to 20 mA, so the
required counts will be 0, 15420 and 30840.
8. Observe the ladder logic, and ensure that the
number of counts in the force value appear
against the tag in the logic.

Toggle Function
This function may be used to change the state of
boolean or discrete tag. If the tag is ON it will toggle to
OFF and, likewise if the tag is OFF will toggle to ON.
When Online the toggled bit may be overwritten by

the logic during the next scan. If Offline or Online
in Program mode, the toggled bit will remain in its
togged state until manually changed.
The bit may be toggle from the routine by right

clicking the selected tag and selecting Toggle from the
properties box. Unlike Forcing, Toggling takes effect
immediately. Figure 9.37 depicts an internal tag being
Toggled to verify the Back Up Pump Fail Alarm logic.
Figure 9.37 Toggle Function

STUDENT EXERCISE - Toggling
1. Identify the rung in which the Backup Pump Fail

alarm is set (AL_Backup_Pump_Test_Fail).
2. Toggle the tags necessary to test the alarm.
3. Toggle the tags necessary to energize timer

Backup_Test_TON.

Locking The Controller

One of the effects of the large number of methods to
connect to the controller is that multiple users can use
these methods simultaneously.
In view of this a useful feature of RSLogix is the

ability to lock the controller. Although multiple users
may still view the logic, edits to the program can only
be made by the user who has locked the controller.
The controller will be automatically unlocked if that
user comes offline.
To lock the controller, select the section of the Online

Toolbar with the padlock icon (see Figure 9.38). Note
that the icon shows an unlocked padlock and this
information is also displayed as text.
Simply selecting “Lock Controller” will initiate

the function the padlock icon will change to a locked
indication and the text will also indicate that the
controller is locked. The Lock Controller option will
also change to Unlock Controller.
Figure 9.38 Locking The Controller

Introduction to Online Editing

This short section will give a very brief introduction
to online editing, mainly to demonstrate the toolbars
available. Advanced editing is carried out as part of
the Turbotronic 4 Field Applications course.
Edits take effect immediately when offline editing,
however when editing online additional steps are
required to verify the edits before finally accepting
them.
To start a rung edit double click to the left of the rung
to be edited. Other methods are available using the
toolbars. See Figure 9.39.
Note that a duplicate of the selected rung appears.
The “i” to the left of the first rung signifies that this is
the rung to be inserted (i.e. the new rung). The “r”
to the left of the second rung signifies that this is
the rung to be replaced.
Also note the appearance of an additional toolbar
above the routine window. These are tools to be used
to test and accept the edits.
Note that RSLogix version 13 displays different icons

than those used in RSLogix version 10.
Figure 9.39 Starting a Program Edit
Once an edit has been made the following procedure

should be followed to finalize the edit. Refer to Figure
9.40. Note that for the purposes of the example an

instruction has been added to the rung. The next

action is to Accept the Pending Program Edit by
selecting the icon indicated in Figure 9.40.
Figure 9.40 Accept Program Edits

A dialog box will open requesting confirmation of the
edit. After selecting Yes the screen will change to
that shown in Figure 9.41.
Note that Figure 9.45 illustrates Accepting Pending

Program Edits for RSLogix version 13.
Figure 9.41 Test Program Edits

Note that in Figure 9.41 the lower-case “i” and

“r” have changed to upper-case. Also note that the
Accept Pending Program Edits option is no longer
available, but that the next step is to Test Program
Edits, as illustrated in the Figure 9.41.
Just to the left of the Test Program Edits icon is an
option to Cancel Pending Edits, if this is required.
Note that Figure 9.46 depicts the screen capture for
Test Program Edits in RSLogix version 13.
Figure 9.42 illustrates the screen when the edits are
being tested. Note that the green highlighted power
rail has changed from the original rung to the new
rung, in other words this is the rung that is now being
scanned by the controller.
If the edits are not required then the icon to the right
allows for Untest Program Edits.
If the edits are required then the final step is to
Assemble Program Edits, as indicated in Figure
9.15.
Note that Figure 9.47 illustrates the screen for
Assemble Program Edits in RSLogix version 13.
Figure 9.42 Assemble Program Edits

Figure 9.43 illustrates the routine with the edits

assembled, i.e. fully completed.
Figure 9.43 Completed Edits

The only remaining step would be to use the standard
Windows Save function to save a copy of the edits in
the programming terminal offline file.
The completed edits in RSLogix version 13 are shown

in Figure 9.48.
An additional feature of RSLogix version 13 provides a

Finalize Edits function. When selected this function
automatically, Accepts, Test, and Assembles all edits
in the program eliminating the need to carried out
each step manually. See Figure 9.49.

Online Edits Screens For RSLogix 5000 Version 13
Figure 9.44 Starting a Program Edit Version 13
Figure 9.45 Accept Pending Program Edits Version 13

Figure 9.46 Test Program Edits Version 13
Figure 9.47 Assemble Program Edits Version 13

Figure 9.48 Edits Complete
Figure 9.49 Finalize Edits Function

NOTES:

STUDENT EXERCISE
1. List three methods of communicating RSLogix

controller.
_____________________________________________
_____________________________________________
_____________________________________________
2. What program is used to configure

communication drivers?
_____________________________________________
_____________________________________________
_____________________________________________
3. Loading a project from a programming terminal
to the controller is:
a. Upload
b. Download
4. What action is required following the creation
of a force?
_____________________________________________
_____________________________________________
_____________________________________________
5. What three steps are required to finalize a

pending rung edit when editing online?
_____________________________________________
_____________________________________________
_____________________________________________

NOTES:

ANSWER KEY
1. List three methods of communicating RSLogix

controller.
RS232 Serial Port
ControlNet
Ethernet
2. What program is used to configure

communication drivers?
RSLinx
3. Loading a project from a programming terminal
to the controller is:
Download
4. What action is required following the creation

of a force?
Enable the forces
5. What three steps are required to finalize a

pending rung edit when editing online?
Accept Pending Program Edits
Test Program Edits
Assemble Program Edits



Solar Technical Training APPENDIX A - PROJECT EDITING EXERCISE
APPENDIX A - PROJECT EDITING EXERCISE
INTRODUCTION
These exercises will be completed as an instructor-led
activity as the appropriate subjects are introduced
during the various lessons.
The intent is to reinforce the lessons on software
architecture, tags and programming conventions by
completing edits of a typical Solar project in RSLogix
5000.
The edits are fairly simple, but are typical of normal
site activities, and will use as many of the Solar
programming techniques and conventions as possible.
All standard programming techniques and naming

conventions should be followed in the following steps.
3820 © 2007 Solar Turbines Incorporated. All rights reserved. A.1

APPENDIX A - PROJECT EDITING EXERCISE Solar Technical Training
SCENARIO:
Customer requests the following additions to the

package:
1. New transmitter TPD567-1 to monitor the

off-skid water wash supply filter (FS567)
differential pressure. Transmitter range
0-100psid.
2. Standard transmitter fail protection logic.

3. Filter DP to be sent to the display system.
4. New alarm if the filter DP exceeds 30 psid for

more than 5 seconds (use a tunable constant
for the setpoint, with an allowable range of 20
- 40 psid).
5. Warning lamp DS567 if the alarm is active.
6. Status bit to display when the alarm is active.

7. Bypass switch S567 to inhibit the filter DP
alarm.
EXERCISE ADDRESS TABLE
ALIAS TAG BASE TAG
DEVICE
Analog Input
Discrete Input
Discrete Output
Alarm for Filter DP
Alarm for Transmitter Fail
Status Bit
A.2 © 2007 Solar Turbines Incorporated. All rights reserved. 3820

GENERAL INSTRUCTIONS:
1. Use the I/O Listing Report to identify spare

channels for:
a. Analog Input for the transmitter

b. Discrete Input for the bypass switch
c. Discrete Output for the warning lamp
2. Open up the appropriate project in RSLogix 5000.

3. Create a new program in the
Turbomachinery_Task.
4. Name the new program Off Skid Water Filter.
5. Move the new program up the order to be above

the Serial Interface and HMI programs.
6. Add a Main Routine.
7. Add a routine called New Transmitter.
8. Add a routine called Alarms and Shutdowns.

9. Create logic to have the new routines scanned
by the controller.
10. In the New Transmitter routine create logic to

scale the transmitter.

provide transmitter fail protection.
move the filter DP to the HMI display.
13. In the Alarms and Shutdowns routine create
logic for the requested alarm.

logic for the warning lamp.

logic for the status bit.
logic for the bypass switch to inhibit the alarm.
17. Verify all edits and correct all errors.


APPENDIX A - PROJECT EDITING EXERCISE Solar Technical Training
A.6 © 2007 Solar Turbines Incorporated. All rights reserved. 3820

Solar Technical Training APPENDIX B - BASIC INSTRUCTION SET
APPENDIX B - BASIC INSTRUCTION SET
NOTE
The material in the following lesson was
covered in the Control System Principles
on-line training course, and is therefore only
included here as reference material, to be
used in the event that a refresher is required
prior to completing this course.
OBJECTIVES
Upon completion of this lesson, the student will be

able to:
1. Demonstrate an understanding of the basic
instructions used in the controller in a
Turbotronic 4 control system.
2. Explain the execution sequence utilized by the
controller in a ladder logic program.
3. Create ladder logic to replicate the functions

performed in a sample logic block diagram or
described in the written instructions.
3820 © 2007 Solar Turbines Incorporated. All rights reserved. B.1

APPENDIX B - BASIC INSTRUCTION SET Solar Technical Training
INTRODUCTION
This lesson introduces the student to the basic

instructions used in the microprocessor-based
controller, and the methods by which the instructions
are assembled into a logical sequential program. The
instruction categories discussed include:
• Bit Instructions
• Timer and Counter Instructions

• Compare Instructions
• Compute or Math Instructions
• Move and Logical Instructions

A functional description of each instruction is
provided, and application examples of each are
illustrated.
B.2 © 2007 Solar Turbines Incorporated. All rights reserved. 3820

BIT INSTRUCTIONS
Bit instructions are used to monitor and control the

status of bits.
Examine if Closed (XIC): ---] [--- The XIC instruction

examines a bit (operand) to see if it is set (logic "1").
If the bit is set, the instruction is TRUE, and the
controller proceeds to the next instruction on the
rung. The bit to be tested is a data bit of the Boolean
(BOOL) type, and is identified with a TAG. In the
example in Figure B.1, the XIC instruction has the
tag: First_Pass.
Figure B.1 XIC Instruction
Examine if Open (XIO): ---]/[--- The XIO instruction

examines a bit (operand) to see if it is cleared (logic
"0"). If the bit is cleared, the instruction is TRUE, and
the controller proceeds to the next instruction on the
rung. The bit to be tested is a BOOL type, and is
identified with a TAG.
Figure B.2 XIO Instruction
Output Energize (OTE): The OTE instruction sets or

clears a data bit (operand). When the OTE instruction
is enabled, the controller sets the data bit; when the
OTE instruction is disabled, the controller clears the
data bit. Example:
Figure B.3 OTE Instruction

COMBINING LOGIC
These instructions are assembled in rungs to monitor

and control the status of bits, as illustrated in the
following examples.
Figure B.4 Combining Logic
The logic in the example can also be expressed in

symbolic logic form, as in the example:
Figure B.5 Symbolic Logic AND Example
The logic statement in the AND function is that for

output Q to be TRUE (“1”), both inputs A and B must
be TRUE simultaneously. The truth table in the
illustration lists the status of Q for each condition
status of A and B. In either form, the logic statement
is valid: for AL_799_H to be TRUE, S396_1 must be
CLEARED and First_Pass must be SET.

NOTE
NOTE: Although our industry-standard
representation of the truth table in Figure B.5
(and the remaining symbolic logic examples)
shows 1 or 0 as the inputs, when we transpose
this to ladder logic we MUST think of TRUE
or FALSE status (or SET and CLEARED). As
explained above, input instructions can be in
either condition with a 1 or a 0, depending
on the input state, depending on the type of
instruction used (XIC or XIO).
If the logical objective is to enable either input to
energize the output, branched logic could be utilized,
as in the following example:
Figure B.6 Branched Logic
With this arrangement, either First_Pass must be

set, or S396_1 must be cleared to enable the OTE
instruction and energize AL_799_H.
The symbolic form of this logic would use the OR

function, as:
Figure B.7 Symbolic Logic OR Example

Often, logic will be combined to express more complex

statements; for example:
Figure B.8 Complex Ladder Logic
The logic statement in this example is: for AL_799_H

to be TRUE, PGM_HMI.Start must be SET, and
either First_Pass must be SET or S396_1 must be
CLEARED.
In symbolic logic form, the expression would be as

shown in Figure B.9.

STUDENT ACTIVITY
Complete Figure B.9 with the correct tag addresses

taken from Figure B.8.
Figure B.9 Complex Symbolic Logic
BIT INSTRUCTIONS (CONTINUED)

Derivations of the Output Energize instruction are
used when the control bits conditioning the rung are
only momentarily set (TRUE), but it is desired to
maintain the bit in the output in a specific state; i.e.,
to latch the bit in one condition or the other. These
instructions are called: “Output Latch (OTL)” and
“Output Unlatch (OTU)”.
Output Latch (OTL): Like the OTE, the OTL will

set the data bit identified in the operand when it is
enabled; however, the OTL will not clear the data
bit when it is disabled. In the example illustrated
in Figure B.10, when the rung becomes TRUE (all
conditioning instructions on the rung are TRUE), the
OTL sets AL_799_H. When the rung becomes FALSE,
AL_799_H remains in the TRUE state.
Figure B.10 OTL Ladder Logic

Symbolically, the OTL is represented as illustrated in
Figure B.11.

STUDENT ACTIVITY

from Figure B.10.
Figure B.11 OTL Symbolic Logic
Output Unlatch (OTU): ---( U )--- It may be

desired/necessary to clear a data bit upon transitioning
rung conditions, in this case, the OTU is used. Figure
B.12 illustrates the ladder logic for an OTU:
Figure B.12 OTU Ladder Logic
Since the device related to the tag: PGM_HMI.Start

is a normally closed switch, pressing the switch would
make the XIO instruction TRUE, enabling the OTU
and clearing AL_799_H. When the switch is released,
AL_799_H will remain in the FALSE (cleared) state
until set by another instruction.

The OTL and OTU instructions can be combined, as in

the following example:
Figure B.13 Combining OTL and OTU Instructions
When the OTL is enabled, AL_799_H is set and the

XIC in the second rung sets DS_175. When the OTU
is enabled, AL_799_H is cleared and the XIC clears
DS_175.
Symbolically, the logic becomes the same as Figure

B.14.

STUDENT ACTIVITY

from Figure B.13.
Figure B.14 Latch/Unlatch Symbolic Logic

TIMER AND COUNTER INSTRUCTIONS
Timer and Counter instructions control operations

based either on incremented time or a number of
events.
Timer On Delay (TON):
Figure B.15 TON
This timer begins to accumulate time in millisecond

increments when the rung in which the timer is
programmed goes TRUE. The Accum field in the
instruction reflects the accumulated value. Two entries
are made to complete creation of the instruction: the
name (main operand) assigned to the instruction
is entered in the Timer field, and the desired timer
interval (in milliseconds) is entered in the Preset
field. The timer illustrated in Figure B.15 is named:
Diagnostic_Delay_Timer, and is programmed for a
30 second timer interval.
Elements of the instruction may be used by other
instructions in the project as references. The Enable
(EN), Timing (TT) and Done (DN) status bits are often
used in bit instructions, and the integer values in the
Preset and Accum fields are referenced in arithmetic,
logical and move instructions (see Figure B.16 for
examples). In the TON, and in all timer and counter
instructions, references to status bits are identified
by a two-character mnemonic (.EN, .TT, .DN), and
references to Preset and Accum values are identified
by a three-character mnemonic (.PRE, .ACC).
With the rung false, the instruction clears the status
bits and the accumulated value. When the rung goes
TRUE, the Enable and Timing bits are set, and the
accumulated value begins to collect time. When the
accumulated value is equal to the Preset value, the
Timing bit is cleared, and the Done bit is set. The
timer remains in this state until the rung again goes
FALSE, at which time the Enable and Done bits are

cleared, and the accumulated value is returned to 0. If

the rung goes FALSE while the timer is timing, the
status bits and the accumulated value are cleared. The
Enable bit is a valid indicator of the rung’s status (it is
always TRUE when the rung is TRUE).
Figure B.16 TON Timer Element References

Timer Off Delay (TOF):
Figure B.17 TOF
This timer is reset when the rung is TRUE, and

begins to accumulate time in the Accum field when
the rung goes FALSE. Like the TON, creation
of the instruction requires two entries: a Main
Operand (name), and a Preset value in milliseconds.
The TOF illustrated in Figure B.17 is named:
“Pump_Lag_Delay_Pre_Post_TOF”, and it is set
for a 60 second interval.

With the rung TRUE, the Accum value and status bit
.TT are cleared, and status bits .EN and .DN are set.
When the rung goes FALSE, the EN bit is cleared,
the TT bit is set, and the Accum value begins to
accumulate time. When the .ACC value is equal to the
.PRE value, the .DN and .TT bits are cleared. The
timer is said to be “timed out”. The timer is reset
when the rung goes TRUE (whether the timer has
timed out or not).
Valid elements of the instruction can be referenced by
other instructions, as in the following examples for
Pump_Lag_Delay-Pre_Post_TOF :
Figure B.18 TOF Timer Element References
Retentive Timer On (RTO):
Figure B.19 RTO

The RTO is functionally identical to the TON, with

one exception: when the rung goes FALSE, the RTO
does not clear its Accum value (because of this,
the .DN bit also remains set if the .ACC value is
greater than .PRE.) This instruction requires a
Reset (RES) instruction referencing the RTO to clear
.ACC and .DN. Figure B.20 illustrates the RES for
T5_TC_Max_Temp_RTO:
Figure B.20 RTO Reset

As with the TON and TOF timers, valid instruction
elements of the RTO can be referenced by other
instructions:
Figure B.21 RTO Timer Element Reference
Count Up (CTU):
Figure B.22 CTU

To create this instruction, a tag is entered in the
Counter field, and an integer value is entered in the
Preset field. The CTU increments its .ACC value
when the rung it is in goes TRUE and the Count Up
Enable(.CU) bit is cleared. When the .ACC value
equals .PRE, the Done (.DN) bit is set. Successive
rung transitions will continue to increment the count
in .ACC, and the .DN bit will remain set. To clear the

.DN bit and the accumulated value, a Reset (RES)

instruction referencing the counter’s tag must be
issued, or 0 must be written to the accumulated value.
The .PRE and the .ACC fields are scaled for double
integer (DINT) values; allowing values between
-2,147,483,647(10) and +2,147,483,648(10)). If the count
exceeds the maximum value, the Overflow (.OV)
bit will be set, and the count will wrap around to
the maximum negative value and continue to count
upward from there.
Valid elements of the instruction can be referenced by

other logic, as illustrated in the following example in
Figure B.23:
Figure B.23 CTU Counter Element References
Count Down (CTD):
Figure B.24 CTD
This instruction is functionally similar to the CTU,

except that it decrements the accumulated value when
the .CD bit is cleared and the rung goes TRUE. As
with the CTU instruction, the .DN bit is set when the
accumulated value is equal to or greater than .PRE.
The count will continue to decrement below zero until
the maximum negative value (-2,147,483,648(10)) in
.ACC is reached; then the Underflow (.UN) bit will
be set, and the count will roll over to +2,147,483,247
and continue. Most applications will use this counter
in conjunction with a CTU that references the same

tag, typically as a totalizer in a production control

system. Otherwise, a Reset instruction referencing
the counter’s tag must be issued, or 0 must be written
to .ACC.
Other instructions may be referenced to the CTD’s
elements as shown in Figure B.25:
Figure B.25 CTD Counter Element References
COMPARE INSTRUCTIONS
Compare instructions allow comparison of values by

using an expression or a specific compare instruction.
Compare instructions are used to condition a rung;
if the values in the instruction are such that the
instruction expression is TRUE, the instruction itself
is TRUE. Values of different types can be compared,
such as floating point and integer (an instruction
executes faster and requires less memory if all the
operands of the instruction are of the same type).
Allowable data types are as shown in the following
table:
Table B.1 Allowable Data Types
Data Type: Description: Range:
0=off<
BOOL 1-bit Boolean
1=on
SINT 1-byte integer -128 to +127
INT 2-byte integer -32,768 to 32,767
DINT 4-byte integer -2,147,483,648 to +2,147,483,647
-3.402823E38 to -1.1754944E-38 (negative values)
and
4-byte floating-
REAL 0
point number
and
1.1754944E-38 to 3.402823E38(positive values)

Figure B.26 ControlLogix Data Types
Compare instructions that are commonly used by

Solar are shown in the following table:
Table B.2 Compare Instructions
To Perform This Comparison: Use this instruction:
Test whether two values are equal Equal To (EQU)
Test whether one value is greater than or equal to a second value Greater Than or Equal to (GEQ)
Test whether one value is greater than a second value Greater Than (GRT)
Test whether one value is less than or equal to a second value Less Than or Equal to (LEQ)
Test whether one value is less than a second value Less Than (LES)
Test whether one value is between two other values Limit (LIM)
Test whether one value is not equal to a second value Not Equal to (NEQ)
Compare values based on an expression Compare (CMP)

Equal to: (EQU):
Figure B.27 EQU
The EQU instruction tests whether Source A is

equal to Source B. When A=B, the instruction is
TRUE, enabling the rung through the position of the
instruction.
Some Compare instructions can be used in Function

Block routines. Figure B.28 illustrates an EQU
instruction in a Function Block routine:
Figure B.28 EQU in Function Block Routine

When used in a function block routine, the EQU
functions in the same manner as when used in a
ladder logic routine. The Dest output can be used as an
input to other function block logic, or to set a tag value.

Greater than or Equal to (GEQ):
Figure B.29 GEQ
In the example shown in Figure B.29, the instruction

will be TRUE when Ngp.Val is equal to or greater
than 15.
The GEQ can also be programmed in a Function

Block routine.
Less Than or Equal to (LEQ):
Figure B.30 LEQ

The LEQ instruction is TRUE when A is equal to or
less than B.
The LEQ can also be programmed in a Function

Block routine.

OTHER COMMON COMPARE INSTRUCTIONS
Other common Compare instructions (for example

the GRT, LES or NEQ) operate in a similar manner
to the examples shown above. However two other
examples of the Compare instructions (the CMP and
LIM) are quite different, and are therefore explained
in the following section.
Compare (CMP):
Figure B.31 CMP
The CMP instruction performs a comparison on the

arithmetic operations specified in an expression,
which is entered in the instruction. To create the
instruction, the desired expression is entered, using
operators, tags and immediate values as required.
The example in Figure B.31 compares the

value tagged: GV_Position.Val with the value:
(GV_Command.Val+10). If the Position (feedback)
value is greater than the Command value plus 10, the
instruction is TRUE. This logic is used to generate
a malfunction shutdown annunciation indicating
that there is unacceptable error in the guide vane
positioning system.
This instruction is not available for Function Block
logic.

Table 3 lists the most commonly used operators that

can be entered in CMP expressions:
Table B.3 CMP Operators
Operator Description Optimal Data Type
+ Add DINT, REAL
- Subtract/Negate DINT, REAL
* Multiply DINT, REAL
/ Divide DINT, REAL
= Equal DINT, REAL
< Less Than DINT, REAL
<= Less Than or Equal DINT, REAL
> Greater Than DINT, REAL
>= Greater Than or Equal DINT, REAL
<> Not Equal DINT, REAL
Limit Test (LIM):
The LIM instruction is used to test if the value being

evaluated in Test is inside or outside the limits set by
the Low Limit and High Limit. Note that the LIM
instruction can be configured to operate in different
ways, according to the values placed in the Low Limit
and High Limit. In the example shown in Figure B.32
the Low Limit is actually the higher number, and
in this configuration the instruction will be TRUE
if the Test value is outside the limits. This is the
normal configuration used by Solar for transmitter fail
detection, since the instruction will remain FALSE if
the Test value is inside the limits (meaning that the
transmitter signal is valid).
Figure B.32 LIM Instruction

COMPUTE / MATH INSTRUCTIONS
Compute/Math Instructions (also known as Arithmetic

Instructions) evaluate arithmetic operations using an
expression or a specific arithmetic instruction. Table 4
lists the available Compute/Math instructions:
Table B.4 Compute/Math Instructions
To Perform This Comparison: Use this instruction:
Add two values ADD
Subtract two values SUB
Multiply two values MUL
Divide two values DIV
Determine the remainder after one value is divided by another MOD
Calculate the square root of a value SQR
Take the opposite sign of a value NEG
Take the absolute value of a value ABS
Evaluate an expression CPT
Data types can be mixed, but rounding errors

and/or loss of accuracy may occur. A compute/math
instruction executes faster and requires less memory
if all the operands of the instruction use the same
optimal data type, typically DINT or REAL.
The most commonly used compute/math instructions

will be described in this lesson.
Add (ADD):
Figure B.33 ADD

Three entries are required to create this instruction,

and most of the other compute/math instructions.
Source A and Source B entries may be a valid tagged
data type or an immediate (constant) value. The
destination (Dest) entry must be a valid tag (the
controller must be told where to store the results
of the operation). The instruction adds Source A to
Source B and stores the result in Dest.
Subtract (SUB):
Figure B.34 SUB

The SUB instruction subtracts Source B from Source
A and stores the result in Dest.
Multiply (MUL):
Figure B.35 MUL
The MUL instruction multiplies Source A by Source B

and stores the result in Dest.

Divide (DIV):
Figure B.36 DIV
The DIV instruction divides Source A by Source B and

stores the result in Dest.
Compute (CPT):
Figure B.37 CPT

The CPT instruction performs the arithmetic
operations entered in the expression. When it is
enabled, the instruction evaluates the expression and
stores the result in the Dest. The operands in the
expression can be immediate or tag values, but the
destination must be a valid tag. The CPT illustrated
in Figure B.37 scales the value from the Lube Oil
Header Pressure Transmitter (TP380) and stores the
result in Header_Pressure.Val.

MOVE AND LOGICAL INSTRUCTIONS
There are a number of Move and Logical Instructions

available in RSLogix5000, however only the most
common example used by Solar will be covered here
the Move (MOV).
Move (MOV):
When enabled the MOV instruction will move the

value in the Source to the tag in the Dest. The Source
may be a tag value or an immediate value, however
the Dest must be a valid tag.
Figure B.38 MOV Instruction
Figure B.38 illustrates a typical usage of a MOV

instruction copying one analog value from one tag to
another, in order to move analog values to the display
system. Another usage could be moving different
values to a timer or counter preset, according to
certain other conditions.

PROGRAM CONTROL INSTRUCTIONS
There are a number of Program Control Instructions

available in RSLogix5000, however only the most
common example used by Solar will be covered here
the Jump to Subroutine (JSR).
Jump to Subroutine (JSR):
When enabled the JSR instruction initiates the

execution of the specified routine, which is referred to
as a subroutine. The subroutine executes one time, and
after the subroutine executes, logic execution returns
to the routine that contains the JSR instruction.
Figure B.39 JSR Instruction
Figure B.39 shows the typical usage of a JSR

instruction in Solar logic a series of JSR instructions
are contained in a routine known as the Main Routine.
This is the only routine in each program that will be
scanned automatically by the controller. However
since there will be a JSR instruction that corresponds
to each of the other routines in that program, the
controller will stop scanning the Main Routine and
scan each of the other routines in turn.
The JSR instruction can also be used to pass
individual parameters to and from other routines, but
this facility is not normally used by Solar.

STUDENT ACTIVITY - LOGIC EXERCISES
Introduction
Using the logic instructions learned in this lesson,
create ladder logic to perform the functionality of the
following written descriptions.
Use the names given in the descriptions as the Tag
Addresses for inputs, outputs, and other instructions.
Use the resulting logic from each exercise in

the following exercise.
Sketch the logic in the spaces provided, referring to

the previous lesson for a reminder of the symbols to
be used.

Exercise 1 - Bit Instructions
Step 1
When Input_1 is ON, turn ON Output_1.
Step 2
When Input_1 or Input_2 is ON, turn ON Output_1.

Step 3
When Input_1 or Input_2 is ON, and Input_3 is OFF, turn ON Output_1.
Step 4
Have Output_1 remain ON even if any of the three inputs change state.

Step 5
Turn Output_1 back off when Input_4 is ON.

Exercise 2 - Timers and Counters
Step 6
When Output_1 is ON, turn ON Output_2 after 10 seconds using Timer_1.
Step 7
Turn ON Output_3whenever Timer_1 is timing.

Step 8
Turn OFF Output_2 3 seconds after Timer_1 has timed out. UseTimer_2.
Step 9
Reset Timer_2 when Input_5 is ON.

Step 10
Count the number of times Timer_2 times out, up to a maximum of 5. Use Counter_1.
Step 11
Turn Output 4 ON when Timer_2 has timed out 5 times.

Step 12
When Output_4 is ON, initiate a TOF with a Preset of 15 seconds. Use Timer_3.
Step 13
Reset Counter_1 15 seconds after Output_3 is ON.

Exercise 3 Compare, Move and Logical Instructions

Step 14
When Timer_3 Accumulated value is higher than or equal to 10 seconds, turn ON Output_5.
Step 15
When Output_5 is ON, modify the existing logic for Output_3 to be ON when Timer_2 has timed
out 10 times.
When the exercises have been completed, refer to the answer sheets that follow.

ANSWERS TO LOGIC EXERCISES

Exercise 1 - Bit Instructions
Step 1
When Input_1 is ON, turn ON Output_1.
Figure B.40 Step 1
Step 2
When Input_1 or Input_2 is ON, turn ON Output_1.
This is an example of an OR gate either Input_1 OR Input_2 will turn on the output.
Figure B.41 Step 2

Step 3
When Input_1 or Input_2 is ON, and Input_3 is OFF, turn ON Output_1.
The OR gate has now been combined with an AND gate.
Figure B.42 Step 3
Step 4
Have Output_1 remain ON even if any of the three inputs change state.
By using a latch (OTL) rather than an OTE we can have the output remain on after initial
energizing, even if the rung conditions change. This is commonly used by Solar in Alarm and
Shutdown annunciation, but also has practical uses in logic sequencing.
Figure B.43 Step 4

Step 5
Turn Output_1 back off when Input_4 is ON.
Using an Unlatch (OTU) with the same address resets latches (OTLs).
Figure B.44 Step 5

Exercise 2 - Timers and Counters
Step 6
When Output_1 is ON, turn ON Output_2 after 10 seconds using Timer_1.
Timers are commonly used in Solar logic applications, with the most common being the TON.
The TON will start to increment time when the rung transitions from False to True.
Note the . Since all RSLogix timers increment in milli-seconds, so this is a 10 second timer.
When the ACC = PRE the DN (Done) bit will become true since the timer has timed out.
The DN bit is then used to sequence further actions in this case turning on another output.
Note that although the DN bit is the most commonly used timer element, other elements are also
available the EN (Enable) and TT (Timer Timing).
Figure B.45 Step 6

Step 7
Turn ON Output_3 whenever Timer_1 is timing.
As mentioned in Step 6, various timer elements are available for use in the ladder logic. In this
case we have used the TT (Timer Timing) bit to turn on an output. This has some practical
applications in having lamps flash or ramping an analog output signal up or down.
Figure B.46 Step 7

Step 8
Turn OFF Output_2 3 seconds after Timer_1 has timed out. Use Timer_2.
This illustrates how to have an output cycling on and off, for example a flashing lamp. Output_1
will come on after 10 seconds and remain on for 3 seconds. Logic could be written to restart the
cycle using another timer element to condition the original rung.
Figure B.47 Step 8

Step 9
Reset Timer_2 when Input_5 is ON.
Although the question used the word reset, the RES instruction is normally only used with an
RTO timer or a Counter. The requested logic can easily be accomplished by placing an XIO
instruction on the rung before the timer. When Input_5 is ON, the XIO will be FALSE, and so
the TON will be reset.
Figure B.48 Step 9

Step 10
Count the number of times Timer_2 times out, up to a maximum of 5. Use Counter_1.
The CTU (Count Up) is the most commonly used Counter. It will increment when the rung
transitions from False to True.
Note that the Counter will continue to increment beyond the Preset, therefore logic should be
written to reset the Counter when it has completed its desired function.
When ACC = PRE the DN (Done) bit becomes true, and like the Timers this element can be used
to sequence other events.
The other type of Counter is the CTD (Count Down). This acts in a similar manner to the CTU,
but is rarely used by Solar.
Figure B.49 Step 10

Step 11
Turn Output 4 ON when Timer_2 has timed out 5 times.
The DN bit from the Counter has been used to turn on another output. Practical applications
of this include Solars surge detection system, where a counter registers the number of surge
events (flow pulses) and will shutdown the unit if a certain number are detected in a certain time.
Figure B.50 Step 11

Step 12
When Output_4 is ON, initiate a TOF with a Preset of 15 seconds. Use Timer_3.
The TOF (Timer Off) requires some careful thought before use. The TOF has the DN and EN bits
set when the rung is True. It will start to increment when the rung transitions from True to False.
Hence a XIO instruction has been used in this case to condition the rung.
When the rung is True the DN and EN bits are set. As the rung transitions to False the TT bit
becomes set. When the ACC = PRE all three bits are reset.
Figure B.51 Step 12

Step 13
Reset Counter_1 15 seconds after Output_4 is ON.
This is an example of the use of TOF elements. Again careful though is required. If using the DN
or EN bits remember that these are initially set as the TOF waits for the rung to transition to False.
Hence in order to satisfy our logic requirements we have had to use an XIO instruction again.
To reset a Counter we have used the RES instruction with the same tag address as the entire
Counter.
Figure B.52 Step 13

Exercise 3 Compare, Move and Logical Instructions

Step 14
When Timer_3 Accumulated value is higher than or equal to 10 seconds, turn ON Output_5.
This logic could have been completed by various methods, including a CMP (Compare)
instruction and the GEQ (Greater Than Or Equal), as used in this example.
Note that the fields in the GEQ instruction can either reference other Tags or elements (for
example comparing error signals and selecting which error to use in the fuel signal calculation),
or can be a pre-set value, as in this example. A practical example of the latter method would
be determining the number of active T5 Thermocouples, and initiating an alarm or shutdown
if the number drops.
Figure B.53 Step 14

Step 15
When Output_5 is ON, modify the existing logic for Output_4 to be ON when Timer_2 has timed
out 10 times.
This illustrates moving of values between instructions. In this example we change the preset
value of Counter_1, depending on other conditions. This technique can also be used with Timers
and various Compare instructions.
An example of this is the selection of the Ignition Timer preset dependant on the type of fuel
selected (the ignition time on liquid fuel is longer).
Figure B.54 Step 15



Solar Technical Training APPENDIX C - Analog Module Scaling Info
APPENDIX C - Analog Module Scaling Info
This document describes the scaling and applicability

for Allen Bradley analog modules. The first part of
this document describes the raw data formats and
conversions for a variety of Allen Bradley modules.
ANALOG INPUT MODULES
1771-IFE
(4 - 20mA)
0 - 4095 counts = 4 - 20mA [255.9375 count/mA or

3.907 uA/count]
(0 - 20mA)
0 - 4095 counts = 0 - 20mA [204.75 count/mA or 4.88

uA/count]
1794-IE8
(0 20mA Mode)
0 - 32760 counts = 0 - 21mA [1560 count/mA or 0.641

uA/count]
0 counts = 0mA
3120 counts = 2.0mA (Under-range)
6240 counts = 4mA

31200 counts = 20mA
31980 counts = 20.5mA (Over-range)
3820 © 2007 Solar Turbines Incorporated. All rights reserved. C.1

APPENDIX C - Analog Module Scaling Info Solar Technical Training
32760 counts = 21mA
(4 20mA Mode)

0.519 uA/count]
(0 - 10V Mode)
0 - 32760 counts = 0 - 10.5V [3120 count/V or 320

uV/count]
1794-IF4I
(4-20mA signed 2s complement Mode)
0 30840 counts = 4 - 20mA [1927.5 count/mA or 0.518

uA/count]
-7710 counts = 0mA

-1542 counts = 3.2mA (Use under-range bit)
30840 counts = 20mA

32382 counts = 20.8mA (Use over-range bit)
1794-IF2XOF2I
(Input Mode same as 1794-IF4I)
C.2 © 2007 Solar Turbines Incorporated. All rights reserved. 3820

ANALOG OUTPUT MODULES
1771-OFE1,2
(4 - 20mA)

3.907 uA/count]
(0 - 50mA)
0 - 4095 counts = 0 - 50mA [81.9 count/mA or 12.21
uA/count]
1794-OE4
(4 20mA)

0.4884 uA/count]
1794-OF4I
(4-20mA signed 2s complement Mode)

0 30840 counts = 4 - 20mA [1927.5 count/mA or 0.518
uA/count]
1794-IF2XOF2I
(Output Mode same as 1794-OF4I)
TEMPERATURE INPUT MODULES
1771-IR
(2s complement binary F Mode)
Engineering Units = counts / 10
1794-IR8
(F Mode)
1794-IT8
(F Mode)

1794-IRT8
(F Mode)
MILLIVOLT INPUT MODULES
1771-IFM(S)
(mV Mode)
0 4095 counts = 0 50mV [81.9 count/mV or 12.21
uV/count]
1794-IRT8
(mV Mode)
-4000 10000 counts = -40 100mV [100 count/mV or
10 uV/count]



Solar Technical Training APPENDIX D - COMMON ABBREVIATIONS AND ENGINEERING UNITS
APPENDIX D - COMMON ABBREVIATIONS

AND ENGINEERING UNITS
SOLAR ENGINE STATION NAMES

T1 - Gas Turbine Air Inlet Temperature
P1 - Gas Turbine Air Inlet Pressure
T2 - Gas Turbine Compressor Discharge Temperature
Pcd - Gas Turbine Compressor Discharge Pressure (other names CDP)
T3 - Gas Turbine 1st Stage Nozzle Gas Temperature (Not Measured)
T5 - Gas Turbine 3rd Stage Nozzle Gas Temperature
T7 - Gas Turbine Exhaust Temperature
P7 - Gas Turbine Exhaust Pressure
Ng[ - Gas Turbine Gas Producer Speed in rpm (other names N1, Ngg)
Ngpcorr - Modified Ngp based on Turbine Inlet Temperature (Ngp/v(q))
Npt - Gas Turbine Power Turbine Speed in rpm (other names N2)
IGV - Compressor Inlet Guide Vanes
ALLEN BRADLEY CONTROL LOGIX DATA TYPE

BOOL - 1 Bit No/Off
SINT - 8 Bit Integer (± 128)
INT - 16 Bit Integer (± 32,768)
DINT - 32 Bit Integer (± 2,147,483,648)
FLOAT - 32-bit IEEE 754 floating-point numbers
3820 © 2007 Solar Turbines Incorporated. All rights reserved. D.1

APPENDIX D - COMMON ABBREVIATIONS AND ENGINEERING UNITS Solar Technical Training
PREFIXES
Metric
µ - micro - 10-6 - 0.000001
M - milli - 10-3 - 0.001
C - centi - 10-2 - 0.01
K - kilo - 103 - 1,000
M - miga - 106 - 1,000,000
G - giga - 109 - 1,000,000,000
English
mm - million 106 - 1,000,000
mils - 10-3 - 0.001
D.2 © 2007 Solar Turbines Incorporated. All rights reserved. 3820

SOLAR COMMON ABBREVIATIONS
A
Acceleration Accel, Acc
Acknowledge Ack
Active Act
Actual cubic feet per minute Acfm
Actuator Actr
Alternating Current Ac
Alternator Altntr, Alt
Ambient Amb
Amperage Amps, A
Anti Ant, A
Auto Aut
Auto Voltage Regulation AVR
Auxiliary Aux
Average Avg
Axial Ax
B
BackUp B/U, Bu
Bearing Brg, Bg
Bleed Bl
Bleed Valve Bv
British Thermal Units Btu
Building Bldg
C
Capacity Cap
Cavitation Cav

Celsius C
Check Chk
Closed Close, Cl
Cold Junction Cj
Command Cmd

Communication Comm, Com

Complete Cmplt
Compressor Cprsr, Cpsr, Cp
Compressor Discharge Pressure Pcd
Compressor High Pressure Hpc
Compressor Intermitted Pressure Ipc
Compressor Low Pressure Lpc
Compressor Speed Ncp
Configure Config
Control Cont, Con
Cooler Clr
Corrected Crctd, Cor
Cross Current Control CCCT
Current I
D
Decelerate Decel
Delta Delt, Del
Delta-P DP, 1P
Direct Current Vdc, Dc
Discharge Disch, Dis
Done Dn
Drain Drn
Drive Dt
Drive End DE
E
Elevation Elev
Emission Emiss
Enable Enbl, En
Enclosure Encl, En
Engine Eng
Engine Axial Engax
Engine Contamination Factor Ecf
Engineering Units Eu

Error Err
External Ext
F
Field Current Regulation FCR
Fahrenheit d32100eF
Feedback Fb
Filter Fltr, Flt
Flow Fl
Forward Fwd
Fuel Energy Flow Wf
Full Load Flld
Frequency Freq
G
Gap Voltage GapV
Gas Fuel Gf
Gas Generator Speed NGG
Gas producer Gp
Gas producer Speed NGP
GearBox Grbx, Gb
Generator Gen
Guide Vane Gv
H
High Hi, H
High Pressure Compressor Hpc
Hourly Hr
Hourly Average Hravg, Hrav
Human Machine Interface HMI
I
Inboard Inbd, Ib
Inch In
Increase Incr, Inc
Injection Inj

Intermediate Pressure Compressor Ipc

Initial Init
Interstage Intstg
J
Journal J/brg
Junction Jct
L
Level Lvl
Limit Lim
Liquid Fuel Liq fl, Lf
Liquid Liq
Load Ld
Local Lcl
Low Lo, l
Lower Heating Value LHV
Low Pressure Compressor Lpc
Lubrication Lub
Lubeoil L/oil
M
Manual Mnl
Maximum Max
Middle Mid
Minimum Min
Mode Mod, M
Multiplier Multr, Mult
N
Power turbine speed NPT
Nomimal Nom
Non Drive End Nde
Non Lockout Nl
Normal cubic meter per day Nm3/d, Nm3d

Normal cubic meter per hour Nm3/h, Nm3h

Normal cubic meter per minute Nm3/m, Nm3m
Number No, #
O
Offset Ofs
Ohms Ohm
Open Op
OutBoard Outbd, Ob
Output Out, Op
P
Percent Pcnt, %
Performance Perf
Permanent Magnet Generator PMG
Phase Ph
Pneumatic Pneu
Position Posn, Pos
Power Pwr
Power Factor Pf
Power Turbine Pt
Power Turbine Speed Npt
Pressure Press, Prs, P
Primary Pri
Process Prcs, Pro
Process Variable Pv
Programmable Logic Controller Plc
Proximeters Prox
Pump Speed Npmp
R
Ramp Rmp
Rate Rt
Reactive Power kVAR
Recycle Rcyl

Reference Ref
Regulator Rgltr, Reg
Remote Rem
Reserve Rsv
Request Req
Required Rqd
S
Schedule Sched, Sch
Secondary Sec
Set Point Sp
Shaft Sft
Shut Down Sht Dn, Sd
Side Stream Sdstrm
Specific Gravity SG
Speed Spd, Sp
Standard cubic feet per day Scfd
Standard cubic feet per hour Scfh
Standard cubic feet per minute Scfm
Standard cubic meter per day Scmd
Standard cubic meter per hour Scmr
Standard cubic meter per minute Scmm
Starter Start, Strt
Station Sta
Subsynchronous Subsync
Suction Suct, Suc
Surge Srg
Swirler Inlet Valve SIV
System Sys
T
Temperature Temp
Thermocouple Tc
Throttle Throt
Thrust Thr

Train Tn
Transmitter Xmtr
V
Valve Vlv
Velocity Vel
Variable Frequency Drive VFD
Vibration Vib
Volts Vlts, Vlt, V
Volts Alternating Current Vac, Ac
Volts Direct Current Vdc, Dc
W
Winding Wdg

ENGINEERING UNITS
In order to perform a consistent appearance on all

projects, engineering units should be structured to
appear as shown in the table below.
English Metric SI Metric Std Metric Mexico

psia kPa bara kg/cm2a
psig kPag barg kg/cm2g
psid kPad bard kg/cm2d
inH2O Pad mbar g/cm2
deg F deg C deg C deg C
deg R deg K deg K deg K
Hp kW MW MW
Ft-lbf/lbm J/kg m.kgf/kgm m.kgf/kgm
acfm M3/h M3/h M3/h
MMscfd nm3/h sm3/h sm3/h
rpm rpm rpm Rpm
MMBtu/h MW MW MW
gpm M3/s l/m l/m
kW kW kW kW
V V V V
I I I I
A A A A
kVAR kVAR kVAR kVAR
kVA kVA kVA kVA
mils µm µm µm
mils mm mm mm
in/s mm/s mm/s mm/s
g G G G
% % % %



3820 Tt4 App Principiantes

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3820 Tt4 App Principiantes

Uploaded by

Copyright:

Available Formats

Technical Training

Turbotronic™ 4 Applied Principles

Course No. 3820

Solar Turbines Incorporated

PUBLICATION NUMBER: TR3820

© 2007 Solar Turbines Incorporated. All rights reserved.

1 LESSON 1 - INTRODUCTION TO SOFTWARE APPLICATIONS

2 LESSON 2 - LOADING A PROGRAM TO THE PROGRAMMING

3 LESSON 3 - OFFLINE PROGRAM MONITORING

3820 © 2007 Solar Turbines Incorporated. All rights reserved. v

4 LESSON 4 RSLOGIX 5000 FAMILIARIZATION

5 LESSON 5 SOLAR PROJECT ORGANIZATION

vi © 2007 Solar Turbines Incorporated. All rights reserved. 3820

FUNCTION BLOCK ROUTINES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.18

6 LESSON 6 - SOLAR LOGIC FAMILIARIZATION

3820 © 2007 Solar Turbines Incorporated. All rights reserved. vii

PROGRAMMING EXERCISE #5 - CREATING ANALOG TAGS . . . . . . . . . .. . 6.47

7 LESSON 7 - EDITING A PROJECT OFFLINE

8 LESSON 8 - HARDWARE AND SOFTWARE INTERFACE

viii © 2007 Solar Turbines Incorporated. All rights reserved. 3820

SAMPLE PROGRAM PURPOSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.6

9 LESSON 9 - RSLOGIX5000 ONLINE FUNCTIONS

3820 © 2007 Solar Turbines Incorporated. All rights reserved. ix

x © 2007 Solar Turbines Incorporated. All rights reserved. 3820

1.1 RSLogix 5000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4

1.2 RSLinx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.5

1.3 RSNetworx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.6

1.4 Solar Turbotronic Field Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.7

2.1 Field Employee Support Database . . . . . . . . . . . . . . . . . . . . . . . . 2.2

2.2 Project Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3

2.3 Subsystem Folder Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3

2.4 Project ACD File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4

2.5 TT4 Field Distribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5

2.6 Distributing Job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6

2.7 Updating Revision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.7

2.8 Rolling Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.8

2.9 Comms Available. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.8

2.10 Continue With Roll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.8

2.11 History File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.9

2.12 Controller Tags Reminder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.9

2.13 New Revision. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.10

3.1 Selecting the Project Revision . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3

3.2 RSLogix Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4

3.3 Start RSLogix 5000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4

3.4 RSLogix Main Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6

3.5 Available Toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7

3.6 Standard Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7

3.7 Online Toolbars. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.8

3.8 Path Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.8

3820 © 2007 Solar Turbines Incorporated. All rights reserved. xi

3.9 New Component Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.9

3.10 Language Element Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.9

3.11 Ladder Edit Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.10

3.12 Language Editor Editing (Bookmark) Toolbar . . . . . . . . . . . . . . . . . . 3.10

3.13 Ladder Common Logic Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . 3.10

3.14 Online Books . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.11

3.15 Instruction Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.12

3.16 Version 13.xx Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.13

4.1 Window Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2

4.2 Modifying Fonts & Colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3

4.3 Version 13 Tools Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4

4.4 File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.7

4.5 Generate Report Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.8

4.6 Edit Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.8