advertisement
Simatic S7 to Logix5000
Application Conversion Guide
Application Solution
Important User Information
Solid state equipment has operational characteristics differing from those of electromechanical equipment. Safety Guidelines for the Application, Installation and Maintenance of Solid State Controls (publication SGI-1.1 available from your local Rockwell Automation sales office or online at http://literature.rockwellautomation.com
) describes some important differences between solid state equipment and hard-wired electromechanical devices. Because of this difference, and also because of the wide variety of uses for solid state equipment, all persons responsible for applying this equipment must satisfy themselves that each intended application of this equipment is acceptable.
In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the use or application of this equipment.
The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and requirements associated with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or liability for actual use based on the examples and diagrams.
No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or software described in this manual.
Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation, Inc., is prohibited.
Throughout this manual, when necessary, we use notes to make you aware of safety considerations.
Identifies information about practices or circumstances that can cause an explosion in a hazardous environment, which may lead to personal injury or death, property damage, or economic loss.
Identifies information that is critical for successful application and understanding of the product.
Identifies information about practices or circumstances that can lead to personal injury or death, property damage, or economic loss. Attentions help you identify a hazard, avoid a hazard, and recognize the consequence
Labels may be on or inside the equipment, for example, a drive or motor, to alert people that dangerous voltage may be present.
Labels may be on or inside the equipment, for example, a drive or motor, to alert people that surfaces may reach dangerous temperatures.
Allen-Bradley, Rockwell Automation, and TechConnect are trademarks of Rockwell Automation, Inc.
Trademarks not belonging to Rockwell Automation are property of their respective companies.
Preface
Hardware Conversion
Logix Features that May Not be
Familiar to S7 Users
3 Publication LOGIX-AP008B-EN-P - June 2008
Table of Contents
Conversion versus Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
PLC Logic Conversion Services Provided by Rockwell Automation . . 9
Service Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
One-stop PLC Program Conversion Services . . . . . . . . . . . . . . . . . 9
Service Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Services Offered. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Basic Conversion Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Conversion Plus Initial Clean-up Package . . . . . . . . . . . . . . . . . . . 10
Additional Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Additional Program Conversions Available . . . . . . . . . . . . . . . . . . 11
Chapter 1
S7 Local I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Selection and Configuration of S7 I/O Components . . . . . . . . . . 14
Logix Local I/O. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Selection and Configuration of Logix I/O Components . . . . . . . 18
S7 Remote I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Configuration of S7 Profibus DP Remote I/O . . . . . . . . . . . . . . . 21
Logix Distributed I/O. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Configuration of Logix Distributed I/O . . . . . . . . . . . . . . . . . . . . 22
Networks in S7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Networks in Logix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Conversion of HMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Conversion of Systems Containing Distributed Controllers . . . . . . . . 32
Hardware and Software Implementation . . . . . . . . . . . . . . . . . . . . 32
Connecting Siemens and Rockwell Automation Devices . . . . . . . . . . 34
Distributed Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Chapter 2
S7 Organization Blocks Compared to Logix Tasks . . . . . . . . . . . . . . . 36
Organization Blocks in S7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Tasks in Logix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Task Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Data Areas in S7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Data in Logix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Programming Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
3
Table of Contents
4
Conversion of System Software and Standard Functions
Logix Ladder Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Logix Structured Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Logix Function Block Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Logix Sequential Function Chart . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Conversion of STEP 7 Code to Logix . . . . . . . . . . . . . . . . . . . . . . 55
Arrays not Pointers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Add-On Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Add-On Instruction Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Backing Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
The Common Industrial Protocol (CIP). . . . . . . . . . . . . . . . . . . . . . . . 58
Viewing the Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Data Exchange between Controllers. . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Send / Receive in STEP 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Produced / Consumed Tags in Logix. . . . . . . . . . . . . . . . . . . . . . . 60
User-Defined Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Asynchronous I/O Updating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
The DINT Data Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Phase Management in STEP 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
PhaseManager in Logix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Coordinated System Time (CST). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Timestamped Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
No Temporary Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
No Accumulators or Special Registers needed . . . . . . . . . . . . . . . . . . . 66
Chapter 3
Logix System Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Date and Time Setting and Reading . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Status – for OBs and Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Conversion Routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
String Handling Routines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Examples of System Function Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Setting the Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Disabling Interrupts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Read System Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Module Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Publication LOGIX-AP008B-EN-P - June 2008
Table of Contents
Conversion of Typical Program
Structures
Common Mistakes when
Converting to Logix
Get Scan Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Chapter 4
Conversion Code Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Ladder Logic Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Jumps and Decision Making . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
User Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Pointers and Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
State Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
STEP 7 State Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
STEP 7 Temporary Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Block Copy, COP and CPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Mathematical Expressions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Other Topics Related to Programming. . . . . . . . . . . . . . . . . . . . . . . . 120
Scope of Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
OBs, Tasks, and Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
A Larger Example - Control Module . . . . . . . . . . . . . . . . . . . . . . . . . 121
Components of the CM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
User Data Type Valve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
The Add-On Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Add-On Instruction Local Data . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Chapter 5
Not Selecting Appropriate Hardware . . . . . . . . . . . . . . . . . . . . . . . . . 129
Underestimating Impact of Task Scheduling . . . . . . . . . . . . . . . . . . . 130
Performing Translation Instead of Conversion . . . . . . . . . . . . . . . . . 130
Not Using the Most Appropriate Logix Languages . . . . . . . . . . . . . . 130
Implementation of Incorrect Data Types – DINT versus INT . . . . 131
Add DINTs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Add INTs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Timing Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
User Code Emulating Existing Instructions . . . . . . . . . . . . . . . . . . . . 132
User Code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
COP Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Incorrect Usage of COP, MOV, and CPS . . . . . . . . . . . . . . . . . . . . . 133
Incorrect Usage of CPT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Not Handling Strings in Optimal Way . . . . . . . . . . . . . . . . . . . . . . . . 133
Extensive Usage of Jumps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Not Using Aliased Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Publication LOGIX-AP008B-EN-P - June 2008 5
6
Table of Contents
S7 to Logix Glossary
S7 300 and S7 400 Parts and
RA Equivalents
Siemens HMI Cross
Reference Table
Chapter 6
Hardware Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Software Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Appendix A
Compact S7 300 CPUs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Standard S7 300 CPUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Technology S7 300 CPUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Fail-Safe S7 300 CPUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
S7 300 Digital Input Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
S7 300 Digital Output Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
S7 300 Relay Output Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
S7 300 Digital Combo Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
S7 300 Analog Input Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
S7 300 Analog Output Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
S7 300 Analog Combo Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
S7 400 Standard Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Redundant and Fail Safe Controllers. . . . . . . . . . . . . . . . . . . . . . . . . . 147
Digital Input Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Digital Output Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Analog Input Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Analog Output Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Appendix B
SIMATIC Micro Panels and Rockwell Automation Equivalents . . . 149
SIMATIC Panels - 7x Series and Rockwell Automation
Equivalents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
SIMATIC Panels - 17x Series and Rockwell Automation
Equivalents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
SIMATIC Panels - 27x Series and Rockwell Automation
Equivalents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
SIMATIC Multi Panels - 27x Series and Rockwell Automation
SIMATIC Multi Panels - 37x Series and Rockwell Automation
Publication LOGIX-AP008B-EN-P - June 2008
Purpose
Conversion versus
Translation
Preface
This user manual provides guidance for users and engineers who have used control systems based on one of these two platforms:
• Siemens S7 Controller
• Rockwell Automation Logix Programmable Automation Controller
(PAC)
And in addition:
• have a desire or a need to take advantage of the PAC features, or are in the early stages of migrating a S7 to Logix.
• have specific STEP 7 program code that they wish to convert to effective and efficient RSLogix 5000 code.
Use this manual to help you adopt good practices and to avoid common mistakes when converting the project to Logix.
The theme of conversion versus translation is one that is repeated in this application conversion guide. Simple translation is focusing only on the line of code and finding an equivalent in the Logix languages. To convert an application optimally, you have to do more than just translate. For instance, you may benefit from choosing a different programming language, utilizing different programming techniques, and designing a different scheduling scheme to solve the same task. So, conversion is performed in a context of a higher level design and knowledge of the strengths of the Logix system.
If you have application code to convert, you will need to understand your
STEP 7 program before you start conversion – either by having been involved yourself in its development, or by reading documentation of the program and of the process that it controls. If the program or the process is unfamiliar or poorly documented, proper conversion will be difficult – it will be mere translation and is less likely to succeed. For example, in Logix, there is a global name space, whereas in the Siemens environment there are data blocks that can be loaded/unloaded by application code. Appreciation of this helps you design a strategy for conversion.
In some cases, if the documentation of both the process and program is poor, it may be more efficient in terms of the overall project duration/cost to draw up a new specification and begin your Logix program with minimal time spent on translation from the old program.
7 Publication LOGIX-AP008B-EN-P - June 2008 7
8
Preface
Terminology
Additional Resources
STEP 7 is the programming software environment for Siemens SIMATIC S7 controllers. RSLogix 5000 software is used with Rockwell Automation Logix programmable automation controllers. We refer to Logix as a programmable automation controller because it does so much more than a traditional general-purpose PLC. It provides an excellent control platform for multi-discipline control, a common namespace, Coordinated System Time for truly scalable multi-CPU architectures, user-defined data types, and full
NetLinx connectivity.
The term “Logix” is used to refer to any of the ControlLogix, CompactLogix,
GuardLogix, FlexLogix, DriveLogix or SoftLogix controllers, or the
RSLogix 5000 programming environment where it is clear from the context which is being referred to.
Every section of this application conversion guide references other Rockwell
Automation user manuals, selection guides, and documents in which more information can be found.
Publication Number
1756-SG001
1769-SG001
1768-UM001
1769-SG002
1756-RM094
1756-PM001
1756-RM003
1734-SG001
1738-SG001
1792-SG001
1794-SG002
NETS-SG001
VIEW-SG001
IA-RM001
6873-SG004
1756-PM010
1756-RM087
IASIMP-RM001
Publication Title
ControlLogix Controllers Selection Guide
1769 CompactLogix Controllers Selection Guide
1768 CompactLogix Controllers User Manual
Compact I/O Selection Guide
Logix5000 Controllers Design Considerations Programming
Manual
Logix5000 Controllers Common Procedures Programming
Manual
Logix5000 Controllers General Instructions Reference Manual
POINT I/O Selection Guide
ArmorPoint I/O Selection Guide
ArmorBlock MaXum I/O and ArmorBlock I/O Selection Guide
FLEX I/O and FLEX Ex Selection Guide
NetLinx Selection Guide
Visualization Platforms Selection Guide
Integrated Architecture: Foundations of Modular
Programming
Encompass Program Product Directory
Logix5000 Controllers Add-On Instructions Programming
Manual
Logix5000 Controllers Execution Time and Memory Use
Reference Manual
IA Recommended Literature Reference Manual
Publication LOGIX-AP008B-EN-P - June 2008
PLC Logic Conversion
Services Provided by
Rockwell Automation
Preface
Rockwell Automation provides additional services for PLC logic conversion.
• One-stop PLC Program Conversion Services
• Conversion Plus Initial Clean-up Package
• Additional Program Conversions Available
Service Features
Program Conversion Services will convert your legacy Allen-Bradley brand
PLC or third-party programmable controller program to run on a Logix programmable automation control system, or the SLC 500/MicroLogix or
PLC-5 programmable controllers.
Legacy products are often expensive to support and are difficult to repair, which can increase downtime and decrease production. For this reason,
Rockwell Automation Customer Support now offers Program Conversion
Services. These services are designed to reduce the cost and the time it takes to migrate from a legacy PLC to one of our current PAC or PLC-control platform families.
One-stop PLC Program Conversion Services
Migration to a current Allen-Bradley control platform from a legacy product will improve your manufacturing process, system reliability and flexibility, give you more access to application processing power, and reduce equipment repair costs and spares inventory. With Program Conversion Services from Rockwell
Automation Customer Support, your existing programmable controller program will be expertly and quickly converted to the new controller family.
Rockwell Automation customer support engineers can help in the migration of legacy Allen-Bradley equipment or convert your PLC systems to Rockwell
Automation products while minimizing downtime and maximizing operational success.
Publication LOGIX-AP008B-EN-P - June 2008 9
Preface
10
Service Benefits
Specialists for each of the product platforms will be involved during the program conversion process. There are no hard to find anomalies in the logic caused by typing errors. In most cases, the entire data table is reproduced and no data is lost, as well as the original documentation is preserved, no re-typing of comments and symbols. Original Allen-Bradley brand programs can be in
6200, APS, or AI series format. New programs will be in the appropriate
RSLogix format.
Services Offered
Two program-conversion packages are available as well as project specific custom packages done on a case-by-case basis.
Basic Conversion Package
• The original programmable controller program will be converted to the appropriate ControlLogix, CompactLogix, PLC-5, or
SLC 500/MicroLogix format.
• The package provides an error listing generated during the conversion that includes instructions that are not directly convertible and any addresses that may not have been converted, which could include pointers and indirect addressing.
• The program and error listing would be returned to the customer for manual debugging and correction.
Conversion Plus Initial Clean-up Package
• The original programmable controller program will be converted to the appropriate ControlLogix, PLC-5, or SLC 500/MicroLogix format.
• We will correct and convert any instruction and/or addressing errors to the new processor family.
• The completed program will then be returned to the customer for final startup and debugging.
Publication LOGIX-AP008B-EN-P - June 2008
Preface
Additional Options
Additional options to either of the packages include the following:
• Application-level telephone support during the start-up and debugging phase of the project.
• Consultation on system re-engineering, operator interface, architecture and communication strategies, to take full advantage of the new platform’s control capabilities that are not part of a code translation effort, training, and onsite startup is available as an added value from you local Global Sales and Solutions (GSS) office.
• Complete turn-key migration or upgrades are available from your local
GSS/Engineered Systems Office.
Publication LOGIX-AP008B-EN-P - June 2008
Additional Program Conversions Available
• PLC-2 format to ControlLogix, CompactLogix, PLC-5,
SLC500/MicroLogix format
• PLC-3 format to ControlLogix, CompactLogix, or PLC-5 format
• PLC-5/250 format to ControlLogix or CompactLogix format
• Modicon – Quantum, 984, 584, 380, 381, 480, 485, 780, 785 to
ControlLogix or CompactLogix format
• Siemens – S-5, S-7 to ControlLogix or CompactLogix format
• TI - 520, 520C, 525, 530, 530C, 535, 560, 560/565, 565, 560/560T,
560T, 545, 555, 575 to ControlLogix or CompactLogix format
• GE Series 6 to ControlLogix or CompactLogix format
Program conversions of other third-party programmable controllers to
Allen-Bradley controller programs are also available. Contact technical support for details.
To schedule a conversion project, or learn more about the Program
Conversion Services, contact your local Rockwell Automation sales office or authorized distributor: email us at [email protected], or visit http://support.rockwellautomation.com/ and view KnowledgeBase
Document G19154.
IMPORTANT
Use consultation services for re-engineering, typically to expand the system functionality and not to change out hardware due to obsolete or related reasons. SLC to Logix format and PLC-5 to Logix format conversions and PCE comment generation are built into RSLogix 5000 software.
11
Preface
Notes:
12 Publication LOGIX-AP008B-EN-P - June 2008
Introduction
S7 Controllers
Chapter
1
Hardware Conversion
The objective of this chapter is to provide guidance to a user or engineer who needs to determine the correct Logix hardware as a replacement for the existing S7 equipment.
The chapter describes how to select controllers, local I/O, remote I/O, networks, and HMI, includes a section on distributed controller architecture, and provides HW conversion examples of the most often used S7 modules.
Topic
Conversion of Systems Containing Distributed Controllers
Connecting Siemens and Rockwell Automation Devices
Page
This table lists a relevant sample selection of current Siemens S7 controllers, which are used to cover a wide range of applications.
Sample Selection of Current Siemens S7 Controllers
Controller
313C
314C-DP
315-2 DP
317-2 DP
317T-2 DP
319-3 PN/DP
414-2
414-3
414-3 PN/DP
Part Number
6ES7 313-5BF03-0AB0
Logix Equivalent
L23 Serial
6ES7 314-6CG03-0AB0 L23 EtherNet/IP, L31
6ES7 315-2AG10-0AB0 L32E, L32C
6ES7 317-6TJ10-0AB0 L35CR, L35E
6ES7 317-6TJ10-0AB0
6ES7 318-3EL00-0AB0
6ES7 414-2XK05-0AB0
6ES7 414-3XM05-0AB0
6ES7 414-3EM05-0AB0
L43, L45
L45, L61
L61, L62
L62, L63, L64, L65
13 Publication LOGIX-AP008B-EN-P - June 2008 13
Chapter 1 Hardware Conversion
I/O Systems
14
Sample Selection of Current Siemens S7 Controllers
315F-2 PN/DP (Safety)
414-H (Redundant)
417-H
PCS7 – Uses 417-4 controller
6ES7 315-2FH13-0AB0
6ES7 317-2FK13-0AB0
6ES7 414-4HM14-0AB0
6ES7 417-4HT14-0AB0
GuardLogix L61S, L62S,
L63S
L61-L65 with SRM
L3x, L4x, L6x +
FactoryTalk View,
FactoryTalk Batch software
A guide to the suitability of some of the most commonly used S7 controllers follows:
• S7 315-2DP – Small to medium-sized machines.
• S7 317-2DP – Medium to medium - large sized machines, small to medium process control applications.
• S7 414-2 – Demanding machine control, process control applications.
• S7 414-3 – Demanding machine control, large process control applications.
The complete range of S7 controllers is listed in
.
These sections describe Logix I/O systems to replace existing S7 equipment.
S7 Local I/O
There is a wide range of S7-300 and S7-400 I/O modules. S7-300 modules are mounted to standard DIN rail and connected to adjacent cards by using
U-connectors, which are supplied with the modules. S7-400 modules are mounted to the S7-400 rack.
Selection and Configuration of S7 I/O Components
The screen shots that follow are from the STEP 7 Hardware Configuration program, a separate program in the STEP 7 application collection. In
RSLogix 5000 software, this functionality is fully integrated as you will see later in this user manual.
Publication LOGIX-AP008B-EN-P - June 2008
Publication LOGIX-AP008B-EN-P - June 2008
STEP 7 Hardware Configuration Program
Hardware Conversion Chapter 1
Drag the selected module to the rack configuration screen.
15
Chapter 1 Hardware Conversion
Logix Local I/O
A wide range of ControlLogix and CompactLogix I/O modules is available.
1769 I/O is cost-optimized for just-enough functionality as often requested by
OEMs, while the 1756 I/O family provides high feature/functionality for the most demanding applications, as often requested by end users and sometimes required to meet specific performance levels.
CompactLogix modules are mounted to standard DIN rail and a special coupling system secures electrical and mechanical connection to adjacent modules. Engineers may welcome the mechanical coupling system – with the
S7-300, modules are fixed to a special rail only and not to each other (other than by the electrical U-connector).
ControlLogix modules are mounted in the 1756 racks.
• For 1769-L31, 1769-L32C, 1769-L32E, and 1768-L43 controllers, the maximum number of I/O modules attached to the controller’s rack is
16, in up to 3 banks.
• For 1769-L35CR, 1769-L35E, and 1768-L45 controllers, the maximum number of I/O modules attached to the controller’s rack is 30, also in 3 banks.
• For 1756 controllers, the number of slots in the rack defines the maximum number of local I/O modules. It can be 4, 7, 10, 13, or 17.
On both platforms, further I/O can be networked via CIP networks, where
EtherNet/IP and ControlNet networks provide the tightest, seamless I/O integration.
16 Publication LOGIX-AP008B-EN-P - June 2008
Hardware Conversion Chapter 1
This table lists the Logix equivalents for some popular S7 I/O modules.
Logix Equivalents for S7 I/O Modules
S7 I/O module Description
6ES7 321-1BL00-0AA0 S7-300 32 channel digital input
6ES7 322 - 1BH01-0AA0 S7-300 16 channel digital output
6ES7 421-1BL01-0AA0 S7-400 32 channel digital input
6ES7 422-1BH01-0AA0 S7-400 16 channel digital output
Logix Equivalent Description
1769-IQ32
1769-OB16
CompactLogix 32 channel digital input
CompactLogix 16 channel digital output
1756-IB32
1756-OB16E
ControlLogix 32 channel digital input
ControlLogix 16 channel digital output
Refer to
Appendix A for more detailed conversion tables of I/O modules.
Publication LOGIX-AP008B-EN-P - June 2008 17
Chapter 1 Hardware Conversion
Selection and Configuration of Logix I/O Components
From the I/O Configuration branch of your project tree, the Logix library of device profiles can be accessed. These profiles provide full wizard-driven configuration for complete, easy-to-use integration into the data table and intuitive programmable control over each module’s functionality, such as scaling, alarming, and diagnostics.
18
Select an item and it will appear in the rack in your I/O configuration.
The device profile tags for the new I/O module have been added automatically to the controller scope tag database.
Publication LOGIX-AP008B-EN-P - June 2008
Publication LOGIX-AP008B-EN-P - June 2008
The view below shows the tags partly expanded.
Hardware Conversion Chapter 1
The profile contains configuration and status data as well as I/O data.
Refer to
Chapter 4 for more information.
19
Chapter 1 Hardware Conversion
S7 Remote I/O
It is common to divide I/O between the controller's local rack and remote
I/O stations, with communication under the Profibus DP network. These are the types of Profibus DP nodes:
• S7 remote I/O, in which case standard S7-300 I/O modules are mounted in a remote I/O panel and interface with the Profibus DP bus via a special module. The controller sees this I/O as local I/O and assigns standard I/O addresses. This is called ET200M.
• Other Siemens remote I/O, such as ET200S (similar to the POINT I/O system) and ET200L (similar to the FLEX I/O system).
• Third-party remote I/O. A number of manufacturers of I/O and valves produce an interface to link their systems to the Profibus DP bus in the same way as S7 remote I/O. For these systems, a special integration file
(GSD file) may need to be imported to your STEP 7 installation.
• Some manufacturers of more complex devices, such as, weigh scales and variable speed drives (VSD), produce Profibus DP interfaces for their products. For these systems, a special integration file (GSD file) will need to be imported to your STEP 7 installation. It is often necessary to refer to the manufacturer’s documentation to learn the meaning of the data areas.
Typical S7 I/O Configuration
Controller
S7 remote I/O
Third-party remote I/O
20 Publication LOGIX-AP008B-EN-P - June 2008
Publication LOGIX-AP008B-EN-P - June 2008
Hardware Conversion Chapter 1
Configuration of S7 Profibus DP Remote I/O
A Profibus DP interface module can be installed in the hardware configuration by dragging from the hardware catalogue to the graphic of the Profibus DP bus. Once the interface module is installed, it can be opened and standard
S7-300 modules added as if it were local I/O.
The data table defines the I/O addresses associated with the drive. Symbols for these addresses would be added manually in the Symbol Table. Hardware configuration is now complete.
It is possible to use remote devices on the Profibus DP network along with
Logix, but with the same constraints/usability limitations you experience in the
S7 environment.
21
Chapter 1 Hardware Conversion
Logix Distributed I/O
Rockwell Automation distributed I/O includes remote I/O using 1756 or
1769 I/O modules and various distributed I/O platforms, such as
POINT I/O, FLEX I/O, ArmorPoint, and ArmorBlock systems.
The I/O modules are connected to the network by using a communication module or communication adapter, or directly by using a built-in communication interface.
Configuration of Logix Distributed I/O
All I/O configuration is done in the project tree of RSLogix 5000 software.
From the I/O Configuration branch, insert a communication module for your chosen network type.
The screen shot shows an addition of a remote 1756-IB32 I/O module connected via an EtherNet/IP network.
Notice that tags corresponding to the remote I/O module have been added automatically to the controller scope tag database.
22 Publication LOGIX-AP008B-EN-P - June 2008
Publication LOGIX-AP008B-EN-P - June 2008
Hardware Conversion Chapter 1
A networked variable speed drive, such as PowerFlex drive, can be added in the same way.
Again, RSLogix 5000 software will generate the new tags automatically for any device with a profile in RSLogix 5000 software and connected on an
EtherNet/IP or ControlNet network. For the DeviceNet network,
GuardLogix Safety I/O is integrated in the same way. Other DeviceNet devices need to be set up by using the RSNetWorx configuration software and
EDS files that operate essentially equivalent to the STEP 7 Profibus manager software and GSD files.
23
Chapter 1 Hardware Conversion
Shown below are device profile tags in RSLogix 5000 software, available for hundreds of Rockwell Automation devices.
24 Publication LOGIX-AP008B-EN-P - June 2008
Hardware Conversion Chapter 1
Networks
Refer to these sections for information about the networks.
Publication LOGIX-AP008B-EN-P - June 2008
Networks in S7
Profibus DP Network, DPV1, DPV3
In the S7 world, the principal network type for communication with devices is the Profibus DP network in a variety of implementations. Some higher-range
S7-300 and all S7-400 controllers have built-in Profibus master ports.
Profibus Network - Other
Profibus FMS and FDL are for data communication between controllers. They perform a similar function to the industrial Ethernet network, and the configuration is nearly identical. The differences are that Profibus communication processors are required rather than the Ethernet network, and that Profibus cabling will be used.
Profibus DPv2 can be used to connect to servo drives in the S7-315T and
S7-317T controllers for low end motion control.
Industrial Ethernet Network
Siemens industrial Ethernet network is the Siemens variety of the Ethernet network in an industrial environment. It is used mainly for communication between controllers, and for controller-to-programming computer communication.
Apart from some of recent controllers equipped for Profinet, S7 controllers do not have built-in Ethernet ports. An S7 system using Industrial Ethernet will have communication processors mounted in the racks.
Depending on the communication processor, the following protocols can be used:
• S7 (Proprietary protocol for communication between S7 controllers)
• TCP (Transmission Control Protocol) Raw Sockets
• ISO-on-TCP (Extended TCP with additional checking)
• UDP (User Datagram Protocol) Raw Sockets
Application code is required to manage most aspects of communication on these networks.
In the Rockwell Automation environment, this functionality can be implemented using integrated EtherNet/IP ports, EtherNet/IP Bridge modules and/or EWEB modules.
25
Chapter 1 Hardware Conversion
Profinet
Profinet provides for similar Profibus DP functionality on an Industrial
Ethernet with the same programming overhead requirements. A network using
Profinet is similar to Profibus except for different cable and connectors, and use Ethernet field interface modules rather than Profibus. Controllers with a built-in Profinet interface or a communication processor that is equipped for
Profinet are used to connect to the network.
Alternatively, an existing Profibus DP network can be bridged to Profinet, either with a proxy or by using the Profibus DP port of a Profinet-equipped controller.
Some Profinet field interface modules have multiple RJ45 ports with an integrated switch, to allow a Profibus-type line bus topology, if required.
Profinet provides these three communication possibilities:
• Profinet CBA (Component Based Automation), which is primarily used for controller to controller communication and uses standard Ethernet hardware and the TCP/IP software stack.
• Profinet IO for scheduled transfers such as Drives or I/O modules and uses standard Ethernet hardware, but bypasses the TCP/IP software stack.
• Profinet IRT (Isochronous Real Time) for motion control applications which uses Profinet specific hardware and also bypasses the TCP/IP software stack and must exist on a protected network segment.
If the Profinet CBA framework is used, then Profibus, Profinet and Industrial
Ethernet networks can be integrated by graphical configuration, with reduced need for additional programming. Rockwell Automation EtherNet/IP networks provide this functionality using standard hardware and the standard
TCP/IP software stack utilizing built-in functions like the Message (MSG) instruction and produced/consumed tags.
26 Publication LOGIX-AP008B-EN-P - June 2008
Publication LOGIX-AP008B-EN-P - June 2008
Hardware Conversion Chapter 1
Networks in Logix
NetLinx is the term identifying the Rockwell Automation solution in the area of networking technologies. The following are the primary networks used in
Logix systems:
• EtherNet/IP
• ControlNet
• DeviceNet
These networks have a variety of notable features. All are designed under the
Common Industrial Protocol (CIP), which enables you to control, configure and collect data over any of the NetLinx networks. As a result, data can flow between different networks without any need for protocol translation software or proxies.
An engineer who is becoming familiar with Logix systems may be impressed by the integrated nature and elegance in configuration of Logix networks.
EtherNet/IP Network
The EtherNet/IP network offers a full suite of control, configuration, and data collection services. It uses TCP/IP for general messaging/information exchange and UDP/IP for I/O messaging. It is most often used in these types of configurations:
• General I/O control
• Data exchange among controllers
• Connecting many computers
• Connecting many devices
• Connectivity to enterprise systems
• Integration of Safety devices
• Motion control (future)
27
Chapter 1 Hardware Conversion
Typical Ethernet/IP Example
28 Publication LOGIX-AP008B-EN-P - June 2008
Hardware Conversion Chapter 1
ControlNet Network
ControlNet is a real-time control network that provides transport of both time-critical I/O and interlocking data and messaging data, including upload/download of programming and configuration data on a single physical media link. It is most often used in these types of configurations:
• General I/O control
• Data exchange among controllers
• Backbone to multiple distributed DeviceNet networks
Typical ControlNet Example
Publication LOGIX-AP008B-EN-P - June 2008 29
Chapter 1 Hardware Conversion
DeviceNet Network
The DeviceNet network is a solution for low-level industrial device networking. Designed for devices with a low data volume per device for real time operation. It is most often used in these types of configurations:
• Applications containing distributed devices with a few points
• Network of third-party drives and other “simple” third-party devices
• Systems in which devices need to be connected directly to the network with data and power in the same connection
• When advanced diagnostic information is required
Typical DeviceNet Example
30 Publication LOGIX-AP008B-EN-P - June 2008
Hardware Conversion Chapter 1
Interconnecting NetLinx Networks
There are two common ways to interconnect NetLinx networks.
• Communication backplane, allowing multiple network links at once.
• Communication linking devices, linking two networks together in a seamless fashion.
Neither any controller nor any programming is required in either of these approaches.
Example of a Control System Based on the NetLinx Networks
Conversion of HMI
Refer to
Publication LOGIX-AP008B-EN-P - June 2008 31
Chapter 1 Hardware Conversion
Conversion of Systems
Containing Distributed
Controllers
This section covers:
• how a general discrete control application containing a group of functional units can be built using multiple controllers.
• how a similar method can be applied to a process control application that is designed to the S88 standard.
Hardware and Software Implementation
General Discrete Control
The hardware and software model for distributed logic for general discrete control is shown below. In this case the supervisory role will be played by a controller. EtherNet/IP or ControlNet network can be used to interconnect the controllers. Produce-Consume or explicit messaging can be used to exchange data within the system.
32 Publication LOGIX-AP008B-EN-P - June 2008
Hardware Conversion Chapter 1
Process Control
The diagram below illustrates the hardware and software structure for a S88 process control application. The PC will be running FactoryTalk Batch software, which is a software package for running production batches by means of recipes. FactoryTalk Batch software resides in a PC and communicates with each controller via the EtherNet/IP network.
Equipment phases are configured under PhaseManager as described later on in
Chapter 2 . They execute the phase logic and communicate with the control
system I/O via control modules.
Publication LOGIX-AP008B-EN-P - June 2008 33
Chapter 1 Hardware Conversion
Connecting Siemens and
Rockwell Automation
Devices
There are situations in which you need to interconnect Siemens and Rockwell
Automation equipment. We recommend that you use products from partnering companies grouped in the Encompass program.
Controllers
Logix controllers can be connected to S7 networks by using:
• in-rack modules.
• standalone communication gateways.
Distributed Devices
Some of Rockwell Automation’s range of I/O systems, PowerFlex drives and
HMI terminals connects to Profibus via communication adapters, built-in interfaces or interface modules.
34 Publication LOGIX-AP008B-EN-P - June 2008
Introduction
Chapter
2
Logix Features that May Not be Familiar to S7
Users
This chapter describes Logix features that may not be familiar to S7 users.
Topic
S7 Organization Blocks Compared to Logix Tasks
The Common Industrial Protocol (CIP)
Data Exchange between Controllers
No Accumulators or Special Registers needed
Page
Certain features of the Logix system are easier to use and maintain than S7 – for instance, data is organized into tag databases with no absolute addresses, whereas in S7 data items have absolute addresses that are selected by the programmer in defined memory areas.
In other respects, the structure of Logix is quite similar to S7, but it is presented differently – for instance beneath the surface the Task structure is similar to S7's Organization Blocks.
35 Publication LOGIX-AP008B-EN-P - June 2008 35
Chapter 2 Logix Features that May Not be Familiar to S7 Users
This Chapter contrasts those features that are different (such as tags) and compares those features that have underlying similarities (such as tasks).
The objective is to:
• provide the S7 user converting to Logix with information that will make the design process easier and quicker.
• show what Logix can do so engineers do not attempt to re-create what exists within controller firmware.
S7 Organization Blocks
Compared to Logix Tasks
This comparison of organization blocks and tasks will introduce the structure of a Logix program to the S7 user.
Organization blocks and tasks are similar in that both are called by the controller’s operating system, rather than by the user program. In STEP 7 (and
Logix), there are three types of organization block (task in Logix).
• Program Cycle OB (organization Continuous Task in Logix) where the
OB re-commences from the beginning when it has finished.
• Cyclic Interrupt OB (Periodic Task in Logix) where the OB executes at a pre-configured time period.
• Hardware Interrupt OBs (Event Task in Logix) execute in response to some hardware stimulus.
Many STEP 7 programmers do not use Cyclic Interrupt OBs.
Logix provides a user configurable multi-tasking operating system which allows the CPU power to allocate as required by the application.
Organization Blocks in S7
The type of OB is defined by its number – they are continuously executed
(OB1 only), periodically executed (OB30 – OB38), they can be executed on events (OB40 – OB47) or they can execute on certain faults arising. With
Logix, tasks are not numbered but are identified by a user-defined name.
A meaningful name can be attached to a STEP 7 OB if required.
36 Publication LOGIX-AP008B-EN-P - June 2008
Logix Features that May Not be Familiar to S7 Users Chapter 2
OB1 Program Cycle
OB1 cycles continuously. When it has finished executing, the output image table values are sent to the outputs, the input image table is updated from the outputs and OB1 starts again.
A STEP 7 program doesn't have to include OB1, but if it is included, it will be continuous.
Typical OB1 Fragment:
Publication LOGIX-AP008B-EN-P - June 2008
OB1 is the root of the call hierarchy for all continuously executed code.
OB1 resembles the (only one possible of course) continuous task in Logix.
In S7 terminology, OB1 is described as “Program Cycle”.
For readers who are more familiar with Logix than STEP 7, it may be useful to know that in STEP 7 ladder logic, a network is the same as a Logix rung. In
STEP 7 statement list, the networks are still there but they only serve to improve the code’s appearance. They break up the code into sections and enable comments to be added. All of the code could be placed in one network if desired – it would compile and run perfectly well.
37
Chapter 2 Logix Features that May Not be Familiar to S7 Users
OB30 – OB38 Cyclic Interrupts
These OBs execute at fixed, configurable intervals. Their priority may also be configured. Higher priority OBs will interrupt any lower priority ones that are running.
How Periodically Called OBs are Configured
38 Publication LOGIX-AP008B-EN-P - June 2008
Publication LOGIX-AP008B-EN-P - June 2008
Logix Features that May Not be Familiar to S7 Users Chapter 2
The number of periodic OBs available depends on the type of controller.
Lower priority number represents higher interrupt priority (priority selection is only available with S7 400 controllers). Execution (ms) is the execution period for the OB. Phase offset allows phasing the triggering of periodic interrupts relative to each another. The process image partition selection allows the I/O image table to be partitioned and that partition only updated when the interrupt occurs (this feature is available with S7 400 controllers only). Default is the full table. In Logix, see the task I/O update selection and IOT commands.
The content of a periodic interrupt OB typically resembles the content of
OB1. It will consist of calls to functions and function blocks that are to be executed at the periodicity of the OB.
These OBs resemble periodic tasks in Logix. In S7 terminology OB30 –
OB38 are called Cyclic Interrupt OBs.
OB40 – OB47 Hardware Interrupt OBs
These OBs may be configured to trigger on an input event. Their priority may also be configured.
These are event tasks in Logix. In S7 terminology OB40 – OB47 are called
Hardware Interrupts.
For example, the most simple hardware event that could be handled by a
Hardware Interrupt OB (or Event Task) is a change of state of a digital input.
A Hardware Interrupt (or Event Task) would guarantee a very fast response to the change.
Event tasks are more flexible than Hardware Interrupt OBs, with triggers not only from I/O, but also from network events, program instructions and motion events.
39
Chapter 2 Logix Features that May Not be Familiar to S7 Users
Program Structure in STEP 7
A typical program includes Organization Blocks (OB), Function Blocks (FB),
Functions (FC) and Data Blocks (DB). System Function Blocks (SFB) and
System Functions (SFC) will usually be present.
• From Organization Blocks (Program Cycle or Cyclic Interrupt or both), calls are made to Function Blocks and Functions.
• A Function Block contains code, and is associated with a Data Block that contains the static data the FB requires. In addition to static data, the FB has temporary data. FBs are used when the logic must preserve values between executions.
• A Function contains code but has no static data. It has temporary data.
FCs are used when the logic completes on a single execution – it has no need to preserve values.
• Data Blocks are areas for storage of static data. They will be described in the next section.
• SFBs and SFCs are System Function Blocks and System Functions.
They can be copied from libraries that are included with a STEP 7 installation and placed in a project.
• When this has been done, they can be called from anywhere in the program.
In STEP 7 there isn't an equivalent structure to Logix's Program/Routine. The
OB will be the root of the call chain to FBs and FCs, but how that is done is up to the programmer.
40 Publication LOGIX-AP008B-EN-P - June 2008
Logix Features that May Not be Familiar to S7 Users Chapter 2
Tasks in Logix
Tasks are called by the operating system. A task provides scheduling and priority for one or more programs. Each Program contains a data section and one or more code routines.
The tasks may be periodic, event or continuous. Each task may be assigned a priority. The continuous task, if present, is always of the lowest priority.
A Logix project will have one task whose default name is MainTask. This task can be continuous, periodic of event. You can change its name if you wish.
Task and Program Structure in Logix
This snapshot from a sample RSLogix 5000 project tree helps illustrate how tasks and programs are structured.
Publication LOGIX-AP008B-EN-P - June 2008
In the screen shot above, the icon to the left of “event_task” signifies an event task. The icon to the left of “MainTask” signifies a continuous task and the icon to the left of “task_02s” signifies a periodic task.
41
Chapter 2 Logix Features that May Not be Familiar to S7 Users
Periodic Tasks
Periodic tasks will trigger at a constant configured interval. Configuration of the period and priority is shown below.
Configuration is similar to the OB30 – OB38 configuration page that was described in the section “OB30 – OB38 Cyclic Interrupts”.
42 Publication LOGIX-AP008B-EN-P - June 2008
Logix Features that May Not be Familiar to S7 Users Chapter 2
Scheduling of Periodic Tasks
The purpose of the Task system is:
• to allow the programmer to choose appropriate frequencies for the execution of Programs. By executing code no more frequently than is needed, the controller CPUs power is used more efficiently for application priorities.
• to use the priority system to allow critical tasks to interrupt lower priority ones, therefore giving them a better chance of executing at the intended frequency.
It is easy to check these times from Task Properties /Monitor.
Publication LOGIX-AP008B-EN-P - June 2008 43
Chapter 2 Logix Features that May Not be Familiar to S7 Users
44
What will happen if a trigger occurs while a task is running?
• If the new trigger is for a task with a higher priority than the one running, the running task will be interrupted by the new one, and will resume when the higher priority task is complete.
• If the new trigger is for a task with a lower priority than the one running, the running task will continue, and the new task will wait until no task of a higher priority is running.
• If the new trigger is for a task with a same priority as the one running, the controller will run both tasks by switching between them at 1ms intervals.
• If the new trigger is for the same task as the one that is running, the new trigger will be discarded. This is an overlap condition.
The number of overlaps that occurred since the counter was last reset is shown in the task properties window. A non-zero number indicates that the interrupt period needs to be increased.
TIP
Avoid switching tasks unnecessarily, due to the amount of processing power that is wasted during unnecessary switching.
When you program periodic interrupts in Logix, note these similarities and differences with STEP 7:
• In STEP 7, calls will be made from the OB that is configured to execute at the chosen frequency to the Functions and Function Blocks you wish to execute at this frequency. In Logix, you will insert programs and routines in the project tree under the Task.
• In both STEP 7 and Logix, the actual application code will not differ greatly from the code in a continuous execution task. Note that the constant and known frequency of a periodic task gives programmers the opportunity to turn a simple variable increment into a timer.
• In both systems, you will need to check for overlaps as you develop and test your code. The execution time of the OB or Task must be much less than its execution period.
• Checking the execution time for Logix tasks is easy. Use the task properties screen shown above. In STEP 7 you will need to sample the system clock at the start and end of the OB, subtract the values and store the result in a variable for monitoring.
• In a S7 controller, overlaps will cause the controller to stop unless a fault
OB is added that traps the fault. Logix is less strict and merely counts the number of overlaps.
Publication LOGIX-AP008B-EN-P - June 2008
Logix Features that May Not be Familiar to S7 Users Chapter 2
• In STEP 7, it is possible to phase the execution of periodic OBs relative to one another. This is not available with Logix Tasks.
Event Tasks
Event Tasks will execute when a configured trigger event occurs. Normally they would be given higher priority than periodic tasks.
Publication LOGIX-AP008B-EN-P - June 2008
An event task is configured by opening the task's Task Properties page and selecting Type Event. Different types of event task triggers can be used for different Logix controllers.
45
Chapter 2 Logix Features that May Not be Familiar to S7 Users
Continuous Task
A Logix controller supports one continuous task, but a project doesn’t have to include the continuous task. You can if you wish run your entire program under Periodic and Event Tasks.
You can configure whether the continuous task updates outputs at the end of its execution.
You can if you wish adjust the percentage of your CPU’s time that is spent on unscheduled communication as a percentage of time dedicated to the continuous task.
Task Monitor
RSLogix 5000 software includes a tool called Task Monitor that can help with analyzing scheduled tasks, and much more.
The screen shot below shows how information about your controller’s tasks can be viewed in one table.
46
The other tabs provide a wealth of other system-level information on your controller’s performance. The tool is included as standard on the RSLogix
5000 installation disk.
Publication LOGIX-AP008B-EN-P - June 2008
Tags Not Addresses
Logix Features that May Not be Familiar to S7 Users Chapter 2
One of the first major differences that a S7 user will notice when starting to work with Logix is that data doesn't have addresses. Data items are created in a tag database, and RSLogix 5000 software allocates addresses “behind the scenes”. This makes it unnecessary for users to understand and manage memory addresses. This section describes data allocation in the two systems.
Data Areas in S7
Data Areas in S7 Controllers
Address Area
Process Image Input Table
IW
ID
Process Image Output Table Q
QB
S7 Notation
I
IB
Bit Memory
Timers
Counters
Data Block
T
C
MW
MD
QW
QD
M
MB
DBX
DBB
DBW
Unit Size
Input Bit
Input Byte
Input Word
Input Double Word
Output Bit
Output Byte
Output Word
Output Double Word
Memory Bit
Memory Byte
Memory Word
Memory Double Word
Data Bit
Data Byte
Data Word
The sections below say more about the two most commonly used areas in programming – bit memory and data blocks.
Publication LOGIX-AP008B-EN-P - June 2008 47
Chapter 2 Logix Features that May Not be Familiar to S7 Users
Bit Memory
“Bit Memory” locations are denoted Mx where, for example:
• M5.3 is a bit.
• MB6 is a byte (BYTE).
• MW8 is a 16 bit word (WORD).
• MD10 is a 32 bit word (DWORD).
Bit memory locations can be labelled in the Symbol Table (similar to a PLC-5 or SLC Symbol Table), as shown in the following screen shot.
48 Publication LOGIX-AP008B-EN-P - June 2008
Logix Features that May Not be Familiar to S7 Users Chapter 2
Data Blocks
Data Blocks have similar status to other blocks – Organization Blocks,
Function Blocks and Functions – except that they contain data rather than program code. The memory in Data Blocks is static – the data retains its value until it is changed.
Example of a Data Block
Publication LOGIX-AP008B-EN-P - June 2008
Data Block symbols do not appear in the Symbol Table, but the name of the
Data Block does.
Data Blocks can be assigned to hold the data used by Function Blocks. These are called Instance Data Blocks.
49
Chapter 2 Logix Features that May Not be Familiar to S7 Users
Data in Logix
In the RSLogix 5000 programming environment, data is set up in a tag database. Memory addresses are hidden from the programmer, which makes things easier for the programmer.
Tag Database
Select a Tag from a Pull-down Menu While Programming
50
In Logix, there is a controller-scope tag database and program-scope tag databases associated with each Program.
• Tags in the controller-scope database are global and can be accessed by routines in any part of the program.
• Program-scope tags can only be accessed by routines in that Program.
Publication LOGIX-AP008B-EN-P - June 2008
I/O and Alias Tags
Logix Features that May Not be Familiar to S7 Users Chapter 2
An alias tag lets you represents another tag, while both tags share the same value. One of the purposes of aliases is to reference the I/O tags as described below.
I/O modules can be added to a project by adding the module to the controller backplane in the project folder.
In this case a 32-point input card has been added at slot 3. The slot number is in square brackets at the beginning of the line. “1756-IB32/A” is the part number of the card. “input_1” is a name for the card that is configured when the card is first added to the rack.
Having added the card, RSLogix 5000 software will automatically generate the relevant device profile tags to the Controller-scope tag database. They are the
Local:3:I input and Local:3:C configuration tags below.
Publication LOGIX-AP008B-EN-P - June 2008 51
Chapter 2 Logix Features that May Not be Familiar to S7 Users
You can create a new alias tag with a more descriptive name. For instance, an alias for the first input can be created called Limit_Switch_1, which physically describes this input.
In STEP 7, the hardware configuration tool will assign addresses to an I/O card when it is added to the system. For example, a digital input card might be assigned bytes I16 and I17. Then the programmer will identify the bit address for each input and enter a name against it in the symbol table. Once that is done, the program will automatically make the association I16.5 =
“ZSC2036”.
52 Publication LOGIX-AP008B-EN-P - June 2008
Logix Features that May Not be Familiar to S7 Users Chapter 2
Programming Languages
This section describes the programming languages that are available with
STEP 7 and RSLogix 5000 software. All languages are not standard; it depends upon the version of the software purchased. Selection of the Logix language most suitable to the task will result in easier program design, more rapid coding and a program that is easier to understand.
There is one significant difference between the S7 and Logix languages. In S7,
Statement List is the “native” language of the controller. Other languages are translated to STL. In Logix, all the languages are “native” languages in the controller – each is compiled without reference to any of the others. The benefit of this is that when you upload a program from the controller, you view it in the language it was written in.
STEP 7 has three standard languages:
• Statement List (STL) – could be described as high-level assembler.
• Ladder Logic (LAD)
• Function Block Diagram (FBD)
And some optional languages:
• Structured Text (ST)
• CFC – Continuous Flow Chart for process-type applications
• HiGraph – Sequential control via Graphing software
• ML – Motion Language – similar to GML in the older Rockwell
Automation dedicated 1394 motion controller
A program can consist of Function Blocks and Functions written in different languages.
RSLogix 5000 software has four programming languages:
• Ladder Diagram (LD) – comparable to Siemens LD, with an expanded instruction set.
• Structured Text (ST) - Equivalent to Siemens ST
• Function Block Diagram (FBD) – Equivalent to Siemens CFC
• Sequential Function Chart (SFC) – Comparable to Siemens hiGraph.
Publication LOGIX-AP008B-EN-P - June 2008 53
Chapter 2 Logix Features that May Not be Familiar to S7 Users
A Routine – the basic section of code in Logix – can be in any of these, and a program can be made of routines written in different languages. The following screen shot gives an example.
This is a ladder diagram.
This is structured text.
This is a sequential function chart.
Logix Ladder Diagram
Traditionally, Ladder Diagram is used for implementing Boolean combinational logic. In Logix, it can also be used for sequential logic, motion, data manipulation and mathematical calculations, although other languages may be more convenient for these tasks.
Logix Structured Text
Structured Text is a high level procedural language that will be easy to learn for anyone with experience in Basic, Pascal or one of the ‘C’ family of languages. It is used primarily for data manipulation and mathematical calculations, although motion, combinational, and sequential logic can also be easily programmed in ST.
54 Publication LOGIX-AP008B-EN-P - June 2008
Publication LOGIX-AP008B-EN-P - June 2008
Logix Features that May Not be Familiar to S7 Users Chapter 2
Logix Function Block Diagram
Function Block Diagram describes graphically a function (Boolean or mathematical) relating input variables and output variables. Input and output variables are connected to blocks by connection lines. An output of a block may also be connected to an input of another block.
It is good practice to program PID loops in FBD. It is the most convenient language for process control.
Logix Sequential Function Chart
SFC is a graphical tool for describing sequential logic as a set of states and transitions. Outputs may be assigned to a state, and Boolean conditions for transitions to other states defined.
Conversion of STEP 7 Code to Logix
• If you have STEP 7 ladder logic code that you wish to convert it to
Logix, LD should be your first choice. The meaning of LD is similar in both systems.
• If you have STEP 7 function block diagram code that you wish to convert it to Logix, FBD should be your first choice.
• Note that the standard Logix FBD is more advanced than STEP 7 FBD, and is equivalent to the optional STEP 7 language CFC.
• If you have STEP 7 Statement List code that you wish to convert to
Logix, the most suitable language will depend on the nature of the STL block. If the STL block contains mainly Boolean evaluations, LD would probably be the best Logix language to convert to. If the STL block contains pointers to access and manipulate data, or executes mathematical calculations, ST would probably be the best Logix language to convert to. If the STL block contains sequential logic, SFC should be considered, although sequential logic can also be easily implemented in ST and LD.
55
Chapter 2 Logix Features that May Not be Familiar to S7 Users
Arrays not Pointers
In STEP 7, arrays can be defined exactly as they would be in Pascal or C, but the basic languages (STL, LD and FBD) do not have high-level support for accessing them. Instead, pointer routines must be constructed.
STEP 7 library functions lack support for array access. Programmers who are comfortable with pointers can write their own functions such as FC101
“INDEXED_COPY” (see below) but it requires skill and time.
“INDEXED_COPY” in STEP 7 does the same as the Logix instruction COP for indexed copying.
FC111 below will access an array.
The pointer to the object is returned in parameter #ptr, which can then be dereferenced to get the data.
In Logix, arrays can be both defined and accessed in the usual way of a high-level computer language, as the fragment below illustrates.
56 Publication LOGIX-AP008B-EN-P - June 2008
Add-On Instructions
Logix Features that May Not be Familiar to S7 Users Chapter 2
Add-On Instruction Summary
Add-on Instructions are the equivalent of STEP 7 Function Blocks, with private data and advanced parameter choices. In particular, the INOUT parameter type or “pass by reference” makes it possible to efficiently pass data structures to the code.
Because the Add-On Instruction is so similar to the STEP 7 Function Block, it is likely that the S7 programmer who is converting to Logix will make use of it quite readily.
Comparison between FBs and Add-On Instructions:
• Both can be called as named functions from anywhere in the program.
• Both contain a private data area of static data, although it is not truly private in the case of STEP 7.
• A STEP 7 function block also has a temporary data area.
• In the Add-On Instruction, local static data will do the same.
Both have three types of parameters – input (pass by value), output (pass by value) and in-out (pass by reference). The pass by reference parameter is a considerable benefit, since it allows large data structures to be passed efficiently.
The Add-On Instruction will automatically maintain a change history by recording a timestamp and the Windows user name at the time of the change.
This is not available with STEP 7 Function Blocks
With the Add-On Instruction a pre-scan routine can be configured to run when the controller goes from Program mode to Run mode, or powers up in
Run mode. Under these conditions, the pre-scan routine will run once, and can typically be used to initialise data. In STEP 7 the Organization block OB100 does the same, but the pre-scan code cannot be specifically attached to a FB.
If the Add-On Instruction is called from a SFC step and the SFC is configured for Automatic Reset, a post-scan routine defined in the Add-On Instruction will execute once when the SFC exits that step. It could be used for resetting data. A STEP 7 FB has no built-in equivalent (although it is easy to program).
An Add-On Instruction can have an EnableInFalse routine, which will be called (if present) when the rung condition at the Add-On Instruction call is false. In this case, the input and output parameters will pass values. A STEP 7
FB has no equivalent.
Add-on Instructions are explored further in
.
Publication LOGIX-AP008B-EN-P - June 2008 57
Chapter 2 Logix Features that May Not be Familiar to S7 Users
Backing Tags
Many instructions and data types use backing tags – tags that are created specifically for the instance of the instruction or data types that you are instantiating. Add-On Instructions, timers, counters, messages, and PID control all use backing tags. RSLogix 5000 software will generate the corresponding structure of elements for you anytime you create a tag of that type so you do not have to create the elements on your own.
The Common Industrial
Protocol (CIP)
Logix uses three main networks - Ethernet/IP, ControlNet and DeviceNet.
Each has characteristics suitable for different areas of application. The three network types share a protocol, the ‘Common Industrial Protocol’.
The CIP makes it possible to transfer data via any of the three types of networks supported by Logix with a nearly identical configuration and programming interface for all three. Also, data can be transferred through a network built from more than one of the three network types without any need for the programmer to translate protocols.
In “traditional” S7 the two main protocols are Industrial Ethernet, for networking to IT and to other controllers, and Profibus DP for networking to field systems. These two protocols are separate at the hardware level and the data level. With the latest S7 hardware and software, “Profinet CBA” integrates
Industrial Ethernet, Profinet and Profibus.
58 Publication LOGIX-AP008B-EN-P - June 2008
Logix Features that May Not be Familiar to S7 Users Chapter 2
Viewing the Network
S7 users may find the Logix network configuration and management striking.
As an example, the tree below shows the devices actually connected to the system. This tree was produced by going online – nothing was configured.
Publication LOGIX-AP008B-EN-P - June 2008
Networks are described further in
59
Chapter 2 Logix Features that May Not be Familiar to S7 Users
Data Exchange between Controllers
Send / Receive in STEP 7
To prepare controller to controller communication in STEP 7, these steps are taken.
1.
The remote stations are configured graphically in a STEP 7 component called NetPro.
2.
A connection table is built in NetPro specifying the protocols and parameters for each of the connections.
3.
The library functions FC5 AG_SEND and FC6 AG_RECV are copied into the project.
4.
Calls are made from the user program to AG_SEND and AG_RECV, specifying connection parameters and the data areas that are being used to source and receive the data.
Produced / Consumed Tags in Logix
Produced and consumed tags are the way that critical data is transferred between networked Logix controllers every defined time period. Produced and consumed tags can transmit over Ethernet/IP or ControlNet and on the backplane of ControlLogix controllers.
Produced and consumed tags are tags that are configured as produced or consumed when they are created. If a tag is marked as produced, then its value will be multicast to a EtherNet/IP or ControlNet network that the controller is connected to. If it is marked as consumed, then the controller that the tag requires data from will be identified as part of the configuration, and the consumed tag will receive its value from the equivalent produced tag in that controller.
There are separate channels for send and receive. Changing the value of a consuming tag will have no effect on the producing tag. This resembles controller-to-controller communication in S7 and differs from controller-to-SCADA communication, where any change will be reflected at the other end.
No programming is required to set up produce/consume connections. This contrasts with S7, where some coding is needed for controller-to-controller
(SEND/RECEIVE) communication.
60 Publication LOGIX-AP008B-EN-P - June 2008
Logix Features that May Not be Familiar to S7 Users Chapter 2
User-Defined Data Types
In Logix, User-Defined Data Types can be configured. This allows the structure of a complex data type to be declared as a type. Instances of that type can then be defined in the program.
Logix User-Defined Data Types have very similar configuration and usage to
STEP 7 User-Defined Data Types.
Logix UDT
Publication LOGIX-AP008B-EN-P - June 2008 61
Chapter 2 Logix Features that May Not be Familiar to S7 Users
Asynchronous I/O Updating
In Logix systems, I/O is updated asynchronously with respect to program execution periods, in contrast with the traditional PLC approach as used in S7 where an I/O image table is updated at the start of the cycle and input values do not change during an execution of the program.
The Logix programmer will need to consider whether there is any need to buffer input data, so that its value remains constant during program execution.
It is quite common to “consume” inputs once only by passing them as parameters to a code module. The inputs will not be used anywhere else in the program. This removes any need for buffering. See the Control Module example in
The DINT Data Type
Logix controllers operate on DINT (32 bit integer) tags more efficiently than on INT (16 bit integer) or SINT (8 bit integer). Use DINT whenever possible, even if the range of values you are working with would fit in an INT or a
SINT. These data types are provided for IEC61131-3 compatibility reasons, but are internally converted to DINTS before being used by the program, so code will execute more efficiently in most situations.
62 Publication LOGIX-AP008B-EN-P - June 2008
Phase Manager
Logix Features that May Not be Familiar to S7 Users Chapter 2
Phase Management in STEP 7
STEP 7 possesses no built-in tools to perform phase management. The necessary structures must be programmed in a set of routines, typically referred to as the PLI or Phase Logic Interface. The components for a PLI program based on S88 are:
• A step sequencer whose behavior complies with the S88 state model.
Certain steps or ranges of steps define the S88 state. Sequencer commands are also as specified by S88, and the sequencer will respond only when the state model permits. A sequencer with these properties is called a phase.
• A set of data for each phase that is used to record the status of the phase and to receive incoming commands from the recipe manager. The recipe manager communicates with this data. The format of the data will depend on the recipe manager.
• A logic module that translates the phase status into the format required by the recipe manager, and translates commands from the recipe manager into phase commands.
PhaseManager in Logix
In an S88 Equipment Phase, there are specified states of the phase as well as the transitions between these states. The PhaseManager is a functionality of
RSLogix 5000 software that allows you to do three things:
• Allocate the code for each phase state to a different routine.
• Run a state machine “behind the scenes” that handles the transitions between states of the phase.
• Manage the running of the phase using a set of Logix commands.
It is used in a variety of application spaces, including but not limited to Process
Control and Packaging, because it allows for clean separation of
Device/Equipment control and of Procedural control, hence making code far more modularized and efficient, especially for larger systems where standardization.
Publication LOGIX-AP008B-EN-P - June 2008 63
Chapter 2 Logix Features that May Not be Familiar to S7 Users
Equipment Phase in the Project Tree
The code for each state of the phase can be written in any of the Logix languages.
This is the phase state machine. It is almost identical to the S88 state model.
64
If you have programmed a S88 compliant STEP 7 phase manager / PLI routine and wish to convert it to Logix, it may be possible to avoid translation by using the Logix PhaseManager.
Publication LOGIX-AP008B-EN-P - June 2008
Logix Features that May Not be Familiar to S7 Users Chapter 2
Coordinated System Time
(CST)
S7 has a system clock, which is represented using 32 bits and counts in milliseconds. Its value can be obtained (and stored) by making a call to the operating system, which is useful for accurate measurement of time intervals.
Logix use Coordinated System Time which is a 64 bit number that measures the number of microseconds since the controller was last started. As with S7, intervals can be measured by making calls to the operating system to get the
CST value. It provides the foundation for clock synchronization for multi-CPU systems, accurate motion control functionality, scheduled output switching to 100 µs accurate, input event timestamping, scheduled analog sampling, safety I/O monitoring and communication, motion cam position calculations, and Wall Clock Time.
Timestamped Inputs
Timestamp is a functionality that records a change in input data with a relative time of when that change occurred. With digital input modules, you can configure a time stamp for changes of data. You can use the CST timestamp to compare the relative time between data samples.
This allows the programmer to achieve unparalleled accuracy in linking input signals to time references for applications such as commonly used in motion control, without putting a huge burden on the communication and logic processing systems and related application code.
Scheduled Outputs
With Digital Output Modules, you can configure the module to set the outputs at a scheduled time.
This allows the programmer to achieve unparalleled accuracy in linking outputs to time references for applications such as axis positions in motion control, or process control functions, without putting a huge burden on the communication and logic processing systems and related application code.
Publication LOGIX-AP008B-EN-P - June 2008 65
Chapter 2 Logix Features that May Not be Familiar to S7 Users
No Temporary Variables
S7 has a category of variables called Temporary Variables. Their scope is the program block in which they are defined and their lifetime is the execution of the program block in which they are defined.
Logix does not have an equivalent to the Temporary Variable. All variables are static – they retain their values until changed.
To achieve the functionality typically targeted in S7 applications, use for example one of the following approaches:
• Use program-scope tags.
• If you are programming an Add-On Instruction, use Local Tags (part of the Add-On Instruction data).
No Accumulators or
Special Registers needed
If you program in STEP 7 Statement List, you will be familiar with the accumulators and the AR1 and AR2 pointer registers. There are no equivalents in Logix. All operands are tags.
To achieve the functionality typically targeted in S7 applications, use for example one of the following approaches:
• Use program-scope tags.
• If you are programming an Add-On Instruction, use Local Tags (part of the Add-On Instruction data).
• Consider whether you need Logix equivalents of the S7 accumulators and special registers. They are there because of the low-level nature of
S7 Statement List, and in a language such as Structured Text, it is unlikely that they will be needed.
66 Publication LOGIX-AP008B-EN-P - June 2008
Introduction
Chapter
3
Conversion of System Software and Standard
Functions
This chapter lists the more commonly used S7 System Functions, explains how the equivalent is done in Logix and provides several specific examples.
Topic
Date and Time Setting and Reading
Examples of System Function Calls
Page
The purpose of this chapter is to make you aware of the dedicated instructions available in Logix, so you do not waste time developing solutions that already exist.
67 Publication LOGIX-AP008B-EN-P - June 2008 67
Chapter 3 Conversion of System Software and Standard Functions
Logix System Functions
In Logix, the equivalent of most S7 System Functions will be the GSV (Get
System Value) and the SSV (Set System Value) instructions. These instructions access a hierarchy of objects (Classes, Instances and Attributes) built-in to
Logix controllers. If you program GSV and SSV, drop-down menus will guide you through parameter selection.
SSV Instruction
Once the basics of GSV and SSV have been learned, the new Logix user may find that access to the operating system is easier than with S7 SFCs.
Copy
S7
SFC20 BLKMOV
SFC81 UBLKMOV
SFC14 DPRD_DAT
SFC15 DPWR_DAT
Used for copying complex data structures - arrays of instances of User Data
Types.
Comment Logix
With BLKMOV, the addresses must be defined at compile time.
COP (instruction)
Uninterruptible version – to ensure that source data cannot change during copy.
CPS (instruction)
If Profibus DP device has communications data area > 4 bytes the SFC will ensure consistent reads.
If Profibus DP device has communications data area > 4 bytes the SFC will ensure consistent writes.
CPS (ControlNet and
Ethernet /IP)
CPS (ControlNet and
Ethernet /IP)
Comment
If COP is used to copy between arrays, the start of the block (source or destination) may include an array index to address the element whose value is evaluated at run time.
Uninterruptible version – to ensure that source data cannot change during copy.
Not required for DeviceNet
Not required for DeviceNet
68 Publication LOGIX-AP008B-EN-P - June 2008
Conversion of System Software and Standard Functions Chapter 3
Date and Time Setting and
Reading
The controllers of both systems have a real-time clock, which can be read or set.
S7
SFC0 SET_CLK
SFC1 READ_CLK
Comment
Values passed in an instance of type DT (DateTime)
Logix
SSV
(Set System Value)
Values returned in an instance of type DT (DateTime)
GSV
(Get System Value)
Comment
SSV Class - WallClockTime
SSV Attribute - DateTime
SSV source - specify element[0] of DINT[7]
GSV Class - WallClockTime
GSV Attribute - DateTime
GSV dest – element[0] of DINT[7]
Read System Time
S7
SFC64 TIME_TCK
The controllers of both these systems have a system clock, which starts at the time the controller starts. In the S7 system the time is in milliseconds, in Logix it is microseconds.
Comment
Returns system time in range
0…2.31 ms
Logix
GSV
(Get System Value)
Comment
Returns system time in range 0…2.63 µs
GSV Class - CST
GSV Attribute - CurrentValue
GSV dest - specify element[0] of DINT[2]
DINT[0] - lower 32 bits
DINT[1] - upper 32 bits
Publication LOGIX-AP008B-EN-P - June 2008 69
Chapter 3 Conversion of System Software and Standard Functions
Handling of Interrupts
S7
SFC39 DIS_IRT
SFC39 EN_IRT
SFC41 DIS_AIRT
SFC42 EN_AIRT
Interrupts can be enabled and disabled by the user program making calls to system functions.
Comment Logix
Disables interrupts handled by a specified OB. Interrupt requests are lost.
SSV
Inhibits specified task.
Enables interrupts handled by a specified OB
SSV
Enables specified task.
Disables interrupts handled by a specified OB. Interrupt requests are delayed.
UID
Enables interrupts handled by a specified OB. Any interrupts delayed by SFC41 are executed.
UIE
Comment
SSV Class - Task
SSV Instance - Task name
SSV Attribute - InhibitTask
SSV source - DINT variable set to 1
SSV Class - Task
SSV Instance - Task name
SSV Attribute - InhibitTask
SSV source - DINT variable set to 0
Disables interruption of the current task by a higher priority task
Enables interrupts of the current task.
Errors
S7
SFC38 READ_ERR
These system calls return bit fields in the case of S7, or an integer in the case of
Logix, representing error codes.
Comment
Reads and clears error bits. The type of error to be queried can be selected with a filtering field.
Logix
GSV
(Use SSV to reset counters or faults)
Comment
GSV Class - FaultLog
GSV Attribute:
MajorEvents – No of major events
MinorEvents – No of minor events
MajorFaultBits – current major fault
MinorFaultBits – current minor fault
GSV Target – INT or DINT to receive data
70 Publication LOGIX-AP008B-EN-P - June 2008
Conversion of System Software and Standard Functions Chapter 3
Status – Controller
S7
SFC51 RDSYSST
The SFC (S7) and GSV call (Logix) will return data on the controller. Note –
SFC51 requires some learning before it can be used. GSV in this case is more accessible.
Comment Logix
Input parameters specify the class of information to be read, and possibly an instance number if there are several objects.
Output parameters are a pointer to a list with the returned information, and the number and size of the elements in the list.
GSV
Comment
Modules with a direct connection:
Examine 'Fault' or 'ChannelFault' member, if present. Modules with a rack optimized connection: Examine the 'SlotStatusBits' member of the adapter input data or the
'Fault' member of the card as above. For all other cards: Execute GSV:
Class – Module
Instance – ModuleName
Attribute - Entrystatus
Status – Module
The SFC (S7) and GSV call (Logix) will return data on the installed modules.
S7
SFC51 RDSYSST
Comment
Input parameters specify the class of information to be read, and possibly an instance number if there are several objects.
Output parameters are a pointer to a list with the returned information, and the number and size of the elements in the list.
Logix
GSV
Comment
GSV Class - Module
GSV Attribute:
EntryStatus (relationship of the Module object to the Module)
FaultCode
FaultInfo
ForceStatus
LEDStatus
Mode (SSV also)
GSV Target – depends on attribute chosen
You can monitor fault information in the Logix tags that are created when the module is inserted into the I/O Configuration. Similarly with STEP 7, if you go to the hardware configuration and switch to “Open ONLINE”, fault information for modules will be displayed.
Publication LOGIX-AP008B-EN-P - June 2008 71
Chapter 3 Conversion of System Software and Standard Functions
Status – for OBs and Tasks
S7
OB Header
Comment
Status data for OBs is stored in
Temporary variables that are automatically generated by the OB header. These may be directly accessed by the OB code, and transferred to static data areas if access is required from outside the
OB.
See an example below.
Logix
GSV / SSV
Comment
GSV Class - Task
GSV instance – Task name
GSV attribute:
DisableUpdateOutputs (at the end of the
Task)
EnableTimeOut
InhibitTask
Instance
LastScanTime (microseconds)
MaxIntervaln (between successive executions of Task)
OverlapCount (triggered while executing)
Priority
Rate (period in microseconds)
StartTime (value of WallClockTime when task was last started)
Status (3 status bits)
Watchdog (microseconds)
GSV Source / Target – depends on attribute chosen
Timers
S7
SFB4 TON
SFB5 TOF
SFB3 TP
Comment
On-delay timer
Off-delay timer
Generates a pulse that will run unconditionally
Logix
TON (LD)
TONR (ST & FBD)
RTO (LD)
RTOR (LD & ST)
TOF (LD)
TOFR (ST & FBD)
Bit of the accumulator of a free-running TON
Comment
On-delay timer
Retentive on-delay timer
Off-delay timer
72 Publication LOGIX-AP008B-EN-P - June 2008
Conversion of System Software and Standard Functions Chapter 3
Conversion Routines
Comment S7
Library functions
FC16 I_STRNG
FC5 DI_STRNG
FC30 R_STRG
FC38 STRG_I
FC37 STRG_DI
FC39 STRG_R
Integer to string
Double integer to string
Real to string
String to Integer
String to double integer
String to real
Logix
Instructions
DTOS
DTOS
RTOS
DTOS
STOD
STOR
Comment
INT can be used as a source tag instead of
DINT
DINT to string
Real to String
String to DINT
String to real
String Handling Routines
S7
FC10 EQ_STRNG
FC13 GE_STRNG
FC15 GT_STRNG
FC19 LE_STRNG
FC24 LT_STRNG
FC29
NE_STRNG
FC21 LEN
FC26 MID
FC2 CONCAT
FC17 INSERT
FC31 REPLACE
FC11 FIND
Comment Logix
Library functions
Compare strings for equality compare strings for >= compare strings for > compare strings for <=
EQU
GEQ (LD)
>= (ST)
GRT (LD)
LEQ (LD)
<= (ST) compare strings for <
Compare strings for <>
Length of string returns a middle section of string MID concatenate two strings CONCAT
Can be done with FC31
REPLACE
DELETE
Insert source string in target string
Replace n characters of target string with source string
Find a string in another string
LES (LD)
< (ST)
NEQ (LD)
<> (ST)
.LEN
INSERT
Use DELETE / INSERT
FIND
Comment
Instructions
Compare strings for equality compare strings for >= compare strings for > compare strings for <= compare strings for <
Compare strings for <>
Property of any string instance returns a middle section of string concatenate two strings
Delete a section of a string
Insert source string in target string
Find a string in another string
There is no equivalent in STEP 7 to Logix’s ASCII Serial Port instructions – neither in the instruction set nor in the function library. These would have to be programmed in STL if required.
Publication LOGIX-AP008B-EN-P - June 2008 73
Chapter 3 Conversion of System Software and Standard Functions
Examples of System
Function Calls
These examples are intended primarily to illustrate the use of the GSV/SSV instructions.
Setting the Clock
STEP 7
This call to SFC0 will set the clock. The time and data is entered in
#date_time.
The data and time are stored in 8 bytes following #data_time in BCD format.
74
0 – year
1 – month
2 – day
3 – hour
4 – minute
5 – second
6 – 2 most significant digits of milliseconds
7 – 1 least significant digit of milliseconds and day of week
Publication LOGIX-AP008B-EN-P - June 2008
Publication LOGIX-AP008B-EN-P - June 2008
Conversion of System Software and Standard Functions Chapter 3
Logix
The date and time values are stored in the seven DINTs following #date_time.
0- year
1 – month
2 – day
3 – hour
6 – minute
5 – second
6 - microsecond
The screen shot for Logix shows the data structure associated with GSV and
SSV. Select class from a pull-down menu as follows.
75
Chapter 3 Conversion of System Software and Standard Functions
Select Attribute from the pull-down menu, as follows.
Finally, select the tag that will be the source (SSV) or destination (GSV) of the data.
Disabling Interrupts
STEP 7
76 Publication LOGIX-AP008B-EN-P - June 2008
Publication LOGIX-AP008B-EN-P - June 2008
Conversion of System Software and Standard Functions Chapter 3
Logix
This example shows SSV in Structured Text.
If you type “gsv” then “alt-A” the following parameter selection screen will pop up.
Once the parameters are entered, click “OK” and the actual parameters will be completed.
77
Chapter 3 Conversion of System Software and Standard Functions
Read System Time
STEP 7
Logix
78 Publication LOGIX-AP008B-EN-P - June 2008
Publication LOGIX-AP008B-EN-P - June 2008
Get Faults
STEP 7
Conversion of System Software and Standard Functions Chapter 3
The bit pattern in the input parameters acts as a filter to select the faults that are to be queried. The faults returned are the masked faults – masking prevents them stopping the controller or calling a fault OB.
Logix
79
Chapter 3 Conversion of System Software and Standard Functions
Module Information
The easiest way is to inspect the module device profile tags, which contain fault/diagnostic information.
1756-IT6I2 Thermocouple Analog-input Card Tag
80 Publication LOGIX-AP008B-EN-P - June 2008
Conversion of System Software and Standard Functions Chapter 3
Another way is to use the GSV instruction to read module objects. The screen shot below shows how to use GSV to obtain information regarding the
1756-IB16D digital input module.
Get Scan Time
STEP 7
This is a screen shot of the Temporary Variables header for OB1.
Publication LOGIX-AP008B-EN-P - June 2008
#OB1_PREV_CYCLE is the scan time. As a temporary variable, it ceases to exist when the execution of OB1 is complete. To store the scan time, copy
#OB1_PREV_CYCLE to a static memory location.
81
Chapter 3 Conversion of System Software and Standard Functions
Logix
The execution time can be retrieved for each Logix task.
With S7, you can directly get the scan time for OB1 from
#OB1_PREV_CYCLE. However, for periodic OBs, there is no equivalent to
#OB1_PREV_CYCLE. To get the execution time for periodic OBs, you will need to insert calls to SFC64 TIME_TCK at the start and end of the OB, and subtract the system clock times returned by the SFC.
82 Publication LOGIX-AP008B-EN-P - June 2008
Chapter
4
Conversion of Typical Program Structures
Introduction
The objective of this section is to demonstrate how some typical programming tasks in STEP 7 can be performed in RSLogix 5000 software. The discussion is based mainly on code fragments, but there are also some complete examples.
Topic
Other Topics Related to Programming
A Larger Example - Control Module
Page
There is also some discussion of matters related to programming, such as the scope and visibility of variables, and the scheduling of code sections.
Conversion Code Examples
These examples show conversion code.
Ladder Logic Translation
This section describes a few examples of comparison between STEP 7 LAD and Logix LD.
Writing to a Coil
STEP 7
83 Publication LOGIX-AP008B-EN-P - June 2008
LOGIX
83
Chapter 4 Conversion of Typical Program Structures
Set and Reset
STEP 7
LOGIX
84 Publication LOGIX-AP008B-EN-P - June 2008
Publication LOGIX-AP008B-EN-P - June 2008
Test for Greater Than
STEP 7
Conversion of Typical Program Structures Chapter 4
LOGIX
As before, use the CMP instruction if the expression is more complex than just comparing two numbers.
85
Chapter 4 Conversion of Typical Program Structures
On Timer Delay
STEP 7
LOGIX
86 Publication LOGIX-AP008B-EN-P - June 2008
Call to User Function
STEP 7
Conversion of Typical Program Structures Chapter 4
LOGIX
Publication LOGIX-AP008B-EN-P - June 2008 87
Chapter 4 Conversion of Typical Program Structures
Boolean Network
STEP 7
LOGIX
There is sufficient similarity between STEP 7 LAD and Logix LD to make translation at the level of routines fairly straightforward.
88 Publication LOGIX-AP008B-EN-P - June 2008
Conversion of Typical Program Structures Chapter 4
The Logix LD Editor
There are no less than seven ways to select LD instructions. Two methods which are fairly similar to the way it is done in STEP 7 are described below.
You can select from a palette above the LD worksheet.
If you type Alt+Insert, this selection pop-up will appear.
Publication LOGIX-AP008B-EN-P - June 2008
When configuring instructions, pull-down menus are available to allow you to select the tag to be entered.
89
Chapter 4 Conversion of Typical Program Structures
Jumps and Decision Making
STEP 7 - Conventional Jump Sequence
The following example task is explained in the Network comment. Two S7 versions are shown because both are often used.
90
The value of #input is compared with the set of constants until comparison is found. Then the action is performed, and comparison ceases. A default action is executed if #input does not compare with any value in the set.
Publication LOGIX-AP008B-EN-P - June 2008
Conversion of Typical Program Structures Chapter 4
STEP 7 - Jump List
In this example the task is the same, but a Jump List is used. This is similar to a microprocessor jump table, and transfers execution to a label depending on the value of a variable.
Publication LOGIX-AP008B-EN-P - June 2008
This is more readable than the conventional jump sequence, and is more efficient because only the code at the target label is executed.
91
Chapter 4 Conversion of Typical Program Structures
Logix - Ladder Logic
This shows multi-way choice using LD.
92 Publication LOGIX-AP008B-EN-P - June 2008
Publication LOGIX-AP008B-EN-P - June 2008
Conversion of Typical Program Structures Chapter 4
Logix - Structured Text If…Then…Else
Anyone familiar with a programming language in the Basic/Pascal/C families will understand this without difficulty.
Brackets around the “if ” condition are not compulsory.
Logix Structured Text CASE statement
This is another variant in ST that does the same task. It is sufficiently compact and clean that there is little need for additional comment.
All solutions work but this is the preferred Logix solution. It is compact and sufficiently clear that no further documentation is needed.
93
Chapter 4 Conversion of Typical Program Structures
Arrays
STEP 7 and Logix both allow arrays of simple or complex objects to be created in memory. Logix has high-level support for accessing arrays. In STEP
7 however, low-level programming is needed.
STEP 7 Array Creation
The following screen shot shows two arrays that have been created in an instance data block. Simple_array is an array of 10 elements. UDT_array is an array of 10 structures of type test_UDT1, where test_UDT1 is a user data type containing a few other types, not shown.
Logix Array Creation
This is exactly the same in Logix.
94
Array Declaration Syntax
STEP 7 uses the declaration syntax ARRAY[0…15] OF REAL. Logix uses
REAL[15].
STEP 7 has a special syntax for strings. STRING[32] is a 32 character string in
STEP 7 whereas in Logix STRING[32] is an array of thirty two strings, each one containing 82 characters.
Publication LOGIX-AP008B-EN-P - June 2008
Conversion of Typical Program Structures Chapter 4
Array Access in STEP 7
This example is to execute a simple task on the two arrays simple_array[] and
UDT_array[]. The task is described in the network comment.
In STEP 7, it is not possible to access arrays using the normal array[] notation.
Instead you have to use low-level operations with pointers. In the fragment below, a function “GET_INDEXED_REFERENCE” makes the task much easier by returning a pointer to the array element that is to be accessed.
Publication LOGIX-AP008B-EN-P - June 2008
In this case, the actual Logix Structure Text code was used as the Network comment, demonstrating just how intuitive Logix code is.
95
Chapter 4 Conversion of Typical Program Structures
STEP 7 - Looping Through Array Elements
The objective in this example is to clear the float field in each structure in
UDT_array[]. This is not difficult, but confidence in using pointers is clearly required.
96 Publication LOGIX-AP008B-EN-P - June 2008
Publication LOGIX-AP008B-EN-P - June 2008
Conversion of Typical Program Structures Chapter 4
Logix - Array Operations in Structured Text
The following ST fragment performs the tasks described in the preceding two sections.
No additional comments are needed to describe how this works.
If you find yourself switching Boolean variables with if…then…else statements, consider writing a Boolean equation instead:
Logix -Array Operations in Ladder Diagram
The examples of the previous section can be written in LD using the CMP
(Compare) instruction as follows.
97
Chapter 4 Conversion of Typical Program Structures
The second one (clearing the real field in the array of UDTs) can be done either of these ways.
98
The first approach to clearing the array elements is a translation from While
Loop of the ST code. The second uses the advanced FAL instruction for array operations.
Publication LOGIX-AP008B-EN-P - June 2008
Conversion of Typical Program Structures Chapter 4
User Data Types
Configuring and using User Data Types (UDTs) in STEP 7 and Logix is very similar.
Below is a UDT in STEP 7.
Below is a UDT in Logix.
Publication LOGIX-AP008B-EN-P - June 2008
In both systems, UDTs can be used to declare and define variables.
99
Chapter 4 Conversion of Typical Program Structures
Here is a declaration involving a UDT in STEP 7.
Here is a declaration involving a UDT in Logix.
One minor difference between the two systems is as follows:
In STEP 7 you can declare a variable of type “struct”.
100
Notice the entry “table” of type Struct. Inside “table” can be a collection
(ordered or unordered) of any combination of types.
Publication LOGIX-AP008B-EN-P - June 2008
Conversion of Typical Program Structures Chapter 4
In Logix, this would be done by defining “Struct” as a UDT containing the desired data structure and then declaring “table” as type Struct.
Publication LOGIX-AP008B-EN-P - June 2008 101
Chapter 4 Conversion of Typical Program Structures
Pointers and Arrays
A STEP 7 program can have pointers to any data object. Indirect access to data blocks is also allowed but there are no pointers to functions (except in a restricted way by the JL (Jump List) instruction). The data pointer is unusual in that it is a pointer to a bit. Hence its value is eight times that of a normal pointer to a byte. This reflects the importance of bits in control systems programming.
In Logix there are no pointers. Arrays perform the same function as pointers, but are simpler and safer.
Will the S7 programmer be able to do a full range of tasks in Logix without pointers? In computer programming, pointers to data are used principally for three purposes:
• Operations on sequentially ordered data items (arrays of objects, strings).
• Allocating, accessing and deleting dynamically allocated objects.
• Passing references to objects as parameters in function calls.
In Logix, the first purpose is covered by arrays. The second purpose is not relevant in control software because we do not have dynamically allocated objects. The third is covered by “inout” parameters in both STEP 7 function blocks and Logix Add-On Instructions.
It is concluded therefore that the absence of explicit pointers is not a limitation for Logix programmers. STEP 7 programmers should also discover that coding using arrays can be more quickly performed in Structured Text using arrays than in STL using pointers.
102 Publication LOGIX-AP008B-EN-P - June 2008
Conversion of Typical Program Structures Chapter 4
State Machine
The State Machine is an important construct in control systems software because it greatly simplifies the task of programming sequential control.
Publication LOGIX-AP008B-EN-P - June 2008 103
Chapter 4 Conversion of Typical Program Structures
STEP 7 State Machine
STEP 7 offers a graphical Sequential Function Chart as an optional extra to the basic application. If the graphical SFC is not available, Statement List will do the job.
104 Publication LOGIX-AP008B-EN-P - June 2008
Conversion of Typical Program Structures Chapter 4
The variable #state contains the state number. The Jump List instruction causes execution to jump to the label relevant to the value of #state. If a transition condition from that state is True, the new state value is loaded in the accumulator and execution jumps to label “next”, where the new state number is transferred to variable #state.
Logix State Machine in Structured Text
Here is the same state machine in Structured Text, using the CASE statement.
As with the other ST examples, it would be hard to write a clearer description than the code itself.
Publication LOGIX-AP008B-EN-P - June 2008 105
Chapter 4 Conversion of Typical Program Structures
Logix State Machine in Sequential Function Chart
Logix provides s graphical SFC as one of its standard suite of languages.
Shown below is the state machine in SFC.
Implementation of State Machine Using SFC chart
106 Publication LOGIX-AP008B-EN-P - June 2008
Conversion of Typical Program Structures Chapter 4
State Machine in Ladder Diagram
The screen shot below shows how the state machine can be implemented in
LD.
Publication LOGIX-AP008B-EN-P - June 2008 107
Chapter 4 Conversion of Typical Program Structures
Strings
String Definition in STEP 7
The data header shows how strings are defined. The length of the string is entered in brackets [] after the String data type. The initial value of the string is typed in the “Initial Value” column.
It is possible to create an array of strings, but each could not be given an initial value. An alternative definition to avoid this problem is shown by the entry
“table” in the data header. “Table” is a structure. The contents of the structure, not shown, are five instances of string[46], and each has been given an initial value.
String Definition in Logix
The extract from the tag configuration table below shows how string are defined in Logix.
108 Publication LOGIX-AP008B-EN-P - June 2008
Conversion of Typical Program Structures Chapter 4
If you wish to create a string of a different length than the 82-character default, right-click on “strings” in your project tree (as shown below).
Then configure the properties as below.
Publication LOGIX-AP008B-EN-P - June 2008
Having done this, you can define instances of your new type.
109
Chapter 4 Conversion of Typical Program Structures
With instances of type STRING or STRING_48, there is a LEN field that automatically updates when a string constant is entered or when the string is manipulated by ASCII or STRING instructions.
STEP 7 Temporary Variables
One of the categories of variable in STEP 7 is the Temporary variable. They can be created in any Organization Block, Function or Function Block.
Temporary variables are used for local, temporary storage of intermediate values, and for pointers. They only exist while their block is executing, and their values are lost when the block terminates.
Logix does not have Temporary variables. All storage is static - that is, values are retained between code executions.
If you use Add-On Instructions, you will notice that Local variables can be created for an Add-On Instruction. These variables can be used in the same way as temporary variables.
Functions
If the STEP 7 programmer uses Statement List, he might have to develop low
- level routines that are time consuming to write and require careful testing.
Functions are important because the development of such routines need be done only once, and having been done, both the originator of the function and other programmers can do the same thing in a fraction of the time.
This section discusses how functions can be implemented in Logix.
Function as Add-On Instruction in Logix
STEP 7 Functions and Function Blocks are similar in their structure to the
Logix Add-On Instruction. The Add-On Instruction has the same types of parameters as the FB (Input, Output and InOut) and it has its own data area.
Once coded and tested, an Add-On Instruction can be used from anywhere in a program, and is sufficiently self-contained to be exported to other projects or placed in a code library.
110 Publication LOGIX-AP008B-EN-P - June 2008
Conversion of Typical Program Structures Chapter 4
Example - a Ramp Function
This example takes a real variable and ramps it linearly from its current value to a new value at a specified rate.
Go to the Add-On Instructions branch of your project tree and right-click
Add-On Instruction.
This form appears.
Publication LOGIX-AP008B-EN-P - June 2008
Enter the name of the Add-On Instruction and specify the language its code section will be written in.
111
Chapter 4 Conversion of Typical Program Structures
Choose the Parameters tab.
112
As in STEP 7, Input parameters are values from the program to the Add-On
Instruction, Output parameters are values from the Add-On Instruction to the program and InOut parameters are for variables that will be modified by the
Add-On Instruction. If you have any data structures, choose the InOut type anyway because they are passed by reference and this is more efficient.
Publication LOGIX-AP008B-EN-P - June 2008
Conversion of Typical Program Structures Chapter 4
In the project tree for AOI_RAMPER, there is a logic section.
Open it to see the code for this Add-On Instruction.
Publication LOGIX-AP008B-EN-P - June 2008 113
Chapter 4 Conversion of Typical Program Structures
The Add-On Instruction can be called from any routine.
114
Note that with Add-On Instructions, you will need to create a tag of type
Add-On Instruction in a data area that is visible to the routine. This is called a backing tag.
Before you write an Add-On Instruction, check through the Instruction Help in RSLogix 5000 software. You might find that there is an existing instruction that will do the job. The following section will illustrate this.
Block Copy, COP and CPS
In STEP 7, it is common to use the system function SFC20 “BLKMOV” to copy a block of data between locations.
The instruction copies the string from the fifth location in an array of strings to a destination string.
Often we want to copy the i-th element from an array, where “i” can vary as the program executes. “BLKMOV” cannot do this.
Publication LOGIX-AP008B-EN-P - June 2008
Conversion of Typical Program Structures Chapter 4
The STEP 7 programmer would write a function to meet his requirement.
In this case, the copy is between two arrays and the indexes are defined by indexSource and indexDest.
In Logix, the COP built-in instruction will save all the work.
Because the source and destination specifications can include variable array indexes, COP will do the job. It is the equivalent of “INDEXED_COPY”.
The CPS instruction is the same as COP but with one difference.
Publication LOGIX-AP008B-EN-P - June 2008
The instruction cannot be interrupted. Therefore, the source and destination data will remain constant throughout its execution. If you wish to move data that could change, use CPS.
Examples are:
• copying input data to a buffer, from where the program will operate on the data.
• copying consumed tags to a buffer, from where the program will operate on the data.
115
Chapter 4 Conversion of Typical Program Structures
Mathematical Expressions
This section will describe how the S7 programmer can perform mathematical computations in Logix. An example will be used - the expression “v(cos(x)^2
+ sin(x)^2)”. The result of this expression is always exactly 1, so it's easy to check that you are getting the correct answer.
STEP 7 - STL
Math code in STEP 7 STL is efficient, but perhaps not too clear for someone who is unfamiliar with STL.
116 Publication LOGIX-AP008B-EN-P - June 2008
Conversion of Typical Program Structures Chapter 4
STEP 7 - LAD
Math evaluation in LAD follows a conventional pattern of combining functions.
Publication LOGIX-AP008B-EN-P - June 2008 117
Chapter 4 Conversion of Typical Program Structures
Logix - ST
The expression is entered in the same way as with any other high-level language.
Logix - LD
The CPT instruction enables the expression to be entered in a high-level manner, which most people will understand more easily than a network (rung) of separate instructions.
STEP 7 - User Function
This function block has been written to do much the same as Logix CPT.
118 Publication LOGIX-AP008B-EN-P - June 2008
Publication LOGIX-AP008B-EN-P - June 2008
Conversion of Typical Program Structures Chapter 4
It reads and evaluates an expression string that is stored in a data block. It has a limitation compared with Logix CPT - the expression is written in reverse
Polish notation, which will not suit everyone.
The main problems with writing a function block such as this are that it takes time and is not for beginning programmers. With Logix, the CPT instruction is available for everyone to use as soon as RSLogix 5000 software is installed.
Type Checking
With both STEP 7 and Logix, parameters to Functions, Function Blocks,
Instructions and Add-On Instructions are strictly type-checked by their compilers.
There are differences with mathematical expressions.
Logix distinguishes between Numeric and Boolean values. The compiler will reject expressions that illogically mix numeric and boolean values. When it encounters expressions of mixed numeric type, it will make conversions to produce a result of the type of the declared result variable. Hence it will interpret * as integer multiplication if the result is to be an integer and as real multiplication if the result is to be a real.
In STEP 7 the type of arithmetic operations must be specified. There are for example *I (multiply two 16 bit integers) *D (multiply two 32 bit integer) and
*R (multiply two reals). It is up to the programmer to ensure that the two numbers that are the operands of a *R instruction are reals. If they are not, the compiler will not complain but the result will be nonsense.
Conclusion
The Logix methods of programming mathematical expressions are clearer, and by separating math code from other logic, will simplify testing and validation.
119
Chapter 4 Conversion of Typical Program Structures
Other Topics Related to
Programming
Scope of Variables
This is an area where Logix differs considerably from STEP 7.
Rules for STEP 7
• Temporary variables are invisible outside the block in which they are declared.
• Global static variables are visible throughout the program.
• Static variables that are declared as instance data to a function block have a special status in the FB, but they can be accessed from other parts of the program.
Rules for Logix
Execution in Logix is divided into Tasks. Each Task may have several
Programs and each Program may have several Routines. Each Program may have its own tag section.
• Controller scope tags are visible throughout all Routines in all Programs.
• Program scope tags are visible only in the Routines in the Program in which they are defined. This means that if a routine in one Program is to share data with a routine in another Program, it must use Controller scope data.
• Add-On Instruction Local Tags are only visible to that Add-On
Instruction's logic.
OBs, Tasks, and Scheduling
Organization Blocks, Tasks and Scheduling are described in
120 Publication LOGIX-AP008B-EN-P - June 2008
Conversion of Typical Program Structures Chapter 4
A Larger Example - Control
Module
This example will assemble some of the different topics illustrated in the previous sections. The term “Control Module” (CM) comes from the influential S88 Batch Control standard. S88 has encouraged controller software design to be more “object oriented”. This Control Module is for a binary valve. The Add-On Instruction is suitable for this type of programming.
Components of the CM
These are:
• a UDT called UDT_VALVE.
• an Add-On Instruction called AOI_VALVE_2SENSOR
• a new Program under “task_02s” called “valves_callup”, which contains program tags section and a routine.
Publication LOGIX-AP008B-EN-P - June 2008 121
Chapter 4 Conversion of Typical Program Structures
User Data Type Valve
The UDT is shown below.
122
Building the UDT should be the first step - it includes all the data that is necessary to model the valve.
Publication LOGIX-AP008B-EN-P - June 2008
Conversion of Typical Program Structures Chapter 4
The Add-On Instruction
Add-On Instruction Parameters
The screen shot shows the parameter configuration screen.
Publication LOGIX-AP008B-EN-P - June 2008
The parameters that have been added are the I/O for the valve and an object of type “UDT_VALVE”. “V” must be an InOut parameter.
123
Chapter 4 Conversion of Typical Program Structures
Add-On Instruction Local Data
The screen shot below shows the configuration page for the Add-On
Instruction local data.
124 Publication LOGIX-AP008B-EN-P - June 2008
Conversion of Typical Program Structures Chapter 4
Add-On Instruction Logic
The screen shot below shows the logic for this Add-On Instruction.
Publication LOGIX-AP008B-EN-P - June 2008 125
Chapter 4 Conversion of Typical Program Structures
126
The tags referred to in this logic are all parameters or local tags. This means that the Add-On Instruction could be used in any program (provided the
UDT Valve is also present).
Publication LOGIX-AP008B-EN-P - June 2008
Publication LOGIX-AP008B-EN-P - June 2008
Conversion of Typical Program Structures Chapter 4
Call-up
Both the call-up code and the instances of UDT Valve are located in the program “valves_callup”, which runs under task_02s. The frequency with which the call-up code is executed depends on the application and the size of the valve.
The screen shot below shows the data instances.
Add an instance of type Valve for each physical valve. The first tag is the required “backing tag” for the Add-On Instruction.
The screen shot below shows the call-up code.
127
Chapter 4 Conversion of Typical Program Structures
Call the Add-On Instruction once for each valve. The actual parameters are the actual I/O tags for the valve's sensors and solenoid, and the instance of
UDT “valve”.
The I/O tags will only appear in the call to the Add-On Instruction. They will not be used anywhere else in the program. Apart from being tidier from the software structure point of view, this cancels any risk of problems arising from asynchronous updating of I/O.
Remember that with Logix controllers the I/O are scanned asynchronously.
128 Publication LOGIX-AP008B-EN-P - June 2008
Chapter
5
Common Mistakes when Converting to Logix
Introduction
Not Selecting
Appropriate Hardware
The objective of this section is to point out some of the design and programming mistakes that S7 users often make when converting applications to Logix. These mistakes have been identified by examination of Logix programs that have been converted from STEP 7.
Topic
Not Selecting Appropriate Hardware
Underestimating Impact of Task Scheduling
Performing Translation Instead of Conversion
Not Using the Most Appropriate Logix Languages
Implementation of Incorrect Data Types – DINT versus INT
User Code Emulating Existing Instructions
Incorrect Usage of COP, MOV, and CPS
Not Handling Strings in Optimal Way
Page
Programming mistakes fall into these two categories:
• Programming that leads to reduced controller efficiency.
• Programming that leads to a control system that is difficult to understand, maintain, and develop.
In most cases, coding for efficiency will also improve the readability and modularity of your program. Conversely, improving the program's structure should also make it more efficient.
This chapter is concerned mainly with software. Remember, however, that the correct selection of hardware is a requirement for satisfactory operation. It is possible that the number of controllers and racks may not be the same as for an equivalent S7 system.
Read
for more about hardware. More information can be found in
and
.
129 Publication LOGIX-AP008B-EN-P - June 2008 129
Chapter 5 Common Mistakes when Converting to Logix
Underestimating Impact of
Task Scheduling
In the area of scheduling and interrupts, there isn't much difference in the capability of the two systems. However, in the Logix world, scheduling is more actively encouraged.
It is quite common for STEP 7 programmers to neglect scheduling when working with Logix controllers. Please see
account of scheduling in Logix.
Performing Translation
Instead of Conversion
It is a common mistake to translate line-by-line a STEP 7 program to Logix.
Instead, a more thorough process is needed, which is described as conversion.
This will cover choice of languages, scheduling and choice of code routines.
By converting rather than translating your STEP 7 programs, you will make better use of the capability of your Logix system.
Not Using the Most
Appropriate Logix
Languages
Programmers often neglect Logix languages other than ladder logic.
Read
for a discussion of how to choose a Logix language and
for examples of STEP 7 code translated into Logix.
130 Publication LOGIX-AP008B-EN-P - June 2008
Common Mistakes when Converting to Logix Chapter 5
Implementation of Incorrect
Data Types – DINT versus INT
It is commonly advised to use DINT rather than INT.
The example below shows an addition of two DINTs v. addition of two INTs.
Add DINTs
Add INTs
Publication LOGIX-AP008B-EN-P - June 2008
Timing Results
The table sows relative times (smaller number is faster). The numbers here are only for comparison with other numbers in the table. They should not be compared with entries in other tables.
Method
Add DINTs with ST For Loop
Add INTs with ST For Loop
Relative Times
53
100
For comparison, the same test was done with an S7 controller. In this case, results were identical for DINTs and INTs.
The lesson is to use DINT for all integer work in Logix. Only use INT or
SINT if you are interfacing to an external system that requires the use of INTs or SINTs.
131
Chapter 5 Common Mistakes when Converting to Logix
User Code Emulating
Existing Instructions
Programmers often write user code when an existing instruction will do the job. As an example, compare copying an array with user code and with the
COP instruction.
User Code
COP Instruction
Below are the relative timings for the two methods. Again, the numbers here are only for comparison with other numbers in the table. They should not be compared with entries in other tables.
Method
Copy array of DINTs with structured text
Copy array of DINTs with COP
Relative Timing
100
18
To perform operations like copy arrays, STEP 7 library functions that are written in Statement List are used. If the library function doesn't do what is required, a new one can be written. The functions written can be almost as efficient as the ones that STEP 7 provides.
However in Logix, it is impossible for a programmer to write a copying function that is as efficient as the built-in COP. The lesson for S7 programmers is to check the Instruction Help in RSLogix 5000 software carefully before doing it yourself.
132 Publication LOGIX-AP008B-EN-P - June 2008
Common Mistakes when Converting to Logix Chapter 5
Incorrect Usage of COP,
MOV, and CPS
MOV copies a simple value (immediate or tag) to a simple tag type – DINT,
INT, SINT, or REAL. COP can do the same as MOV (the source cannot be an immediate value), but its more important use is to copy complex data types.
It would be a minor programming mistake to use COP to copy simple data types.
A mistake that is seen often is to use multiple MOVs to copy a data structure when one COP could be used.
If your source data could change during copying due to asynchronous I/O updates, use CPS instead. This instruction cannot be interrupted so source data will remain constant while copying.
Incorrect Usage of CPT
In Logix, the CPT instruction can be used to evaluate expressions. The expression is entered in one of the fields of the instruction. It is very convenient.
However, CPT should only be used if more than one arithmetic instruction would be required to evaluate the expression. If a single instruction is sufficient, it will be faster than CPT.
You can read more about CPT in
Not Handling Strings in
Optimal Way
If you want to define a new String type, for example with a different number of characters than the default 82, it would be a mistake to create a new ‘User
Data Type’. Instead, create a new String data type. The advantage of doing it this way is that the ‘LEN’ field will automatically update as the length of the string changes.
Extensive Usage of Jumps
In Logix, jumps can only occur in Ladder Logic. It is recommended that JMP instruction be used sparingly. Jumps in ladder logic often make the program difficult to read.
Not Using Aliased Tags
Remember to create aliased tags for the I/O tags that RSLogix 5000 software creates for you. They will make your program easier to read. See
.
Publication LOGIX-AP008B-EN-P - June 2008 133
Chapter 5 Common Mistakes when Converting to Logix
Notes:
134 Publication LOGIX-AP008B-EN-P - June 2008
Chapter
6
S7 to Logix Glossary
Introduction
This chapter provides a glossary of S7 terms and their Logix equivalents.
Hardware Terminology
S7 Term
Communications
Processor
Controller
CPU
Failsafe CPU
Industrial Ethernet
Definition
Comms module
The controller
Central Processing Unit
CPU 315F-2 DP Implements PROFISAFE version of DP
Siemens version of Ethernet
MPI
Programmable
Controller
PROFIBUS DP
PROFIBUS PA
PROFINET
PROFISAFE
S7-200
S7-300
S7-400
SIMATIC
Logix Term
Bridge
Controller
CPU or Controller
GuardLogix
Multi-Point Interface – a serial bus
Ethernet /IP
ControlNet
Serial
Controller or PAC
Commonly used field bus
Variety of Profibus specializing in Process
Automation
Profibus over Ethernet
Failsafe version of PROFIBUS DP
Low-end controllers
Mid-range controllers
High-end controllers
Brand name for Siemens automation products
Ethernet /IP
ControlNet
DeviceNet
As Profibus DP
Ethernet /IP
GuardLogix
MicroLogix
CompactLogix
ControlLogix
Logix
Definition
L61S, L62S, L63S
Both of these have the same (or better) functionality as Industrial Ethernet
DF1 or DH485 protocols
135 Publication LOGIX-AP008B-EN-P - June 2008 135
Chapter 6 S7 to Logix Glossary
Software Terminology
S7 Term
Accumulator
AR1, AR2
Array
Bit Memory
Block Transfer
BOOL
BYTE
CFC
CHAR
Cycle_Execution
Data Block
DINT
DWORD
FBD
Function
Function Block
GRAPH
HW Config
INT
Interrupt_Execution
LAD
Library
Definition
Used in STL
Pointer registers
Syntax ARRAY[0…7] OF REAL
Addresses M...
Copy block of data.
SFC20 BLK_MOV
8 bit word
Optional process control language
Byte as character
OB1 – Continuously executed
Unit of static data memory
Double integer
32 bit word
Function Block Diagram
Program Unit with Temporary memory but no Static memory
DINT
DINT
FBD
Program Unit with Temporary memory and Static memory
Optional graphical language
Routine
AOI (Add-On
Instruction)
Routine
AOI (Add-On
Instruction)
Program
Sequential Function
Chart
I/O Configuration Hardware Configuration – component of
STEP 7
Integer
Periodically executing OB
Ladder Logic
System functions
INT
Periodic Task
LD
GSV, SSV
Nearest Logix Term Definition
N/A In Logix languages, there is no need to access low-level structures of the CPU
N/A
Array
In Logix languages, there is no need to access low-level structures of the CPU
Syntax REAL[8]
Indexing always starts at 0
N/A
COP
Use tags
Instruction
(use MOV for a simple variable)
BOOL
SINT Use is deprecated (it’s slower than DINT) except when required (for example, characters of string)
Standard function block language.
FBD
SINT
Continuous Task
Controller-Scope Tag database or Program-scope tag database
Continuously executed
Global visible within the Program that the database is linked to
Double integer
Function Block Diagram
Both of these could correspond to a function
All of these could correspond to a function block
Standard Graphical Language
Branch of Controller Organiser
Use is deprecated (it’s slower than DINT)
Periodically executing Task
Ladder Logic
Instructions –
Get System Value
Set System Value
136 Publication LOGIX-AP008B-EN-P - June 2008
S7 to Logix Glossary Chapter 6
S7 Term
NetPro
Organization Block
Pointer
REAL
SCL
Simatic Manager
STEP 7
STL
STRING
STRUCT
Symbol
Temporary memory
WORD
UDT
Definition
Network Configurator
Nearest Logix Term Definition
N/A Part of I/O Configuration branch of controller organiser.
Program unit called by Operating System Task
Data pointer used in STL N/A
32 bit floating point number
Optional high-level language
REAL
Structured Text
Program unit called by Operating System
Use arrays
32 bit floating point number
Standard Language
Component of STEP 7
Development and monitoring software for
S7
Statement List
Controller Organiser
RSLogix 5000
N/A
Sequence of CHARs. Default Length 254
Untyped collection of data
Name for data memory address
STRING
N/A
Tag
Component of RSLogix 5000
Development and monitoring software for
Logix
Use Structured Text or Ladder Logic or
Sequential Function Chart
Sequence of SINTs. Default length 82.
String object also contains its length as property.LEN
In Logix a structure is an instance of type
(UDT)
Tag defines the structure of the variable
and reserves memory
Use tags Memory created on run-time stack
16 bit word
User Data Type
N/A
INT
UDT User Data Type
Publication LOGIX-AP008B-EN-P - June 2008 137
Chapter 6 S7 to Logix Glossary
Notes:
138 Publication LOGIX-AP008B-EN-P - June 2008
Introduction
Appendix
A
S7 300 and S7 400 Parts and RA Equivalents
This appendix lists Siemens products and their Rockwell Automation equivalents.
Topic
Redundant and Fail Safe Controllers
Page
Publication LOGIX-AP008B-EN-P - June 2008 139
Appendix A S7 300 and S7 400 Parts and RA Equivalents
Compact S7 300 CPUs
Siemens
Catalogue
Number
Siemens
Short
Reference
Memory
6ES7
312-5BE0x-xxxx
S7-312C 32K
MPI
Y
Comms
Ports
DP
N
Max
MMC
Size
Serial
N 4 MB
DI
10
Embedded
I/O
DO
6
AI AO
6ES7
313-5BF0x-xxxx No No
6ES7
313-6BF0x-xxxx
S7-313C-
PtP
64K Y
6ES7
313-6CF0x-xxxx
S7-313C-
DP
64 K Y
6ES7
314-6BG0x-xxx x
S7-314C-
PtP
96K Y
6ES7
314-6CG0x-xxx x
S7-314C-
DP
96K Yes
Yes No 8
MB
Y
N
N
Y
N
Y
N
8 MB 24 16
RS422/
485
8 MB
N 8 MB
RS422/
485
8 MB
N 8 MB
16 16
16 16
24 16
24 16
4
4
4
2
2
2
RA
Solution
1769-L31 +
Compact
I/O
ML1500
1769-L31 +
Compact
I/O
ML1500
1769-L31 +
Compact
I/O
ML1500
1769-L31 +
Compact
I/O
ML1500
1769-L31 +
Compact
I/O
ML1500
1769-L31 +
Compact
I/O
ML1500
Standard S7 300 CPUs
Siemens
Catalogue
Number
Siemens Short
Reference
Memory
6ES7
312-1AE1x-xxxx
S7-312 32K
6ES7
314-1AG1x-xxxx
6ES7
315-2AG1x-xxxx
S7-314
S7-315-2 DP
96K
128K
Y
Y
MPI
Y
140
N
Y
Comms
Ports
DP
N
PN
N
N
N
Max Load
Memory
Size (RAM)
RA Solution
4 MB
8 MB
8 MB
1769-L31
1769-L31
1769-L3xE or
1769-L3xC
Publication LOGIX-AP008B-EN-P - June 2008
Siemens
Catalogue
Number
Siemens Short
Reference
Memory
6ES7
315-2EH1x-xxxx
6ES7
317-2AJ1x-xxxx
6ES7
317-2EK1x-xxxx
6ES7
319-3ELOx-xxxx
S7-315-2 PN/DP 256K
S7-317-2 DP 512K
S7-317-2 PN/DP 1 MB
S7-319-3 PN/DP 1.4 MB
Y
Y
Y
MPI
Y
Technology S7 300 CPUs
Siemens
Catalogue
Number
Siemens Short
Reference
Memory
6ES7
315-6TG1x-xxxx
S7-315T-2 DP 128K
6ES7
317-6TJ1x-xxxx
S7-317T-2 DP 512K
MPI
Y
Y
S7 300 and S7 400 Parts and RA Equivalents Appendix A
Comms
Ports
Y
Y
Y
DP
Y
N
Y
Y
PN
Y
Max Load
Memory
Size (RAM)
8 MB
8 MB
8 MB
8 MB
RA Solution
1769-L3xE or
1769-L3xC
1769-L3xE or
1769-L3xC
1769-L3xE or
1769-L3xC
1769-L3xE or
1769-L3xC
Comms
Ports
DP
Y
PN
Y
Y
Y
Max Load
Memory
Size (RAM)
RA Solution
4 or 8 MB
1768-L43
4 or 8 MB 1768-L43
Publication LOGIX-AP008B-EN-P - June 2008 141
Appendix A S7 300 and S7 400 Parts and RA Equivalents
Fail-Safe S7 300 CPUs
Siemens
Catalogue
Number
Siemens Short
Reference
Memory
6ES7
315-6FF1x-xxxx
S7-315F-2 DP 192K
6ES7
315-2FH1x-xxxx
S7-315F-2
PN/DP
256K
6ES7
317-6FF0x-xxxx
S7-317F-2 DP 1 MB
6ES7
317-2FK1x-xxxx
S7-317F-2
PN/DP
1 MB
MPI
Y
Y
Y
Y
Y
Y
Y
Comms
Ports
DP
Y
PN
N
Y
N
Y
S7 300 Digital Input
Modules
Siemens Catalogue
Number
6ES7 321-1BH0x-xxxx
6ES7 321-1BH5x-xxxx
6ES7 321-1BL0x-xxxx
6ES7 321-1CH0x-xxxx
6ES7 321-1CH2x-xxxx
6ES7 321-1BH1x-xxxx
6ES7 321-7BH0x-xxxx
6ES7 321-1FH0x-xxxx
Front
Connector
20-pin
20-pin
40-pin
40-pin
20-pin
20-pin
20-pin
20-pin
16
16
Points
16
16
32
16
16
16
6ES7 321-1FF0x-xxxx 20-pin 8
Range RA Solution
24 VDC
24 VDC
1769-IQ16
1769-IQ16F
1769-IQ16
1769-IQ16F
24 VDC 1769-IQ32
1769-IQ32T
n/a 24 … 48 V
48 … 125 VDC n/a
24 VDC 1769-IQ16
1769-IQ16F
24 VDC 1769-IQ16
1769-IQ16F
120 … 230 VAC 1769-IA16
120 ... 230 VAC 1769-IM12
Comments
1769-IA16 only admits
120 VAC
1769-IM12 only admits
230 VAC
8 MB
8 MB
8 MB
8 MB
Max Load
Memory
Size (RAM)
RA Solution
ControlLogix
GuardLogix or
SmartGuard
600
GuardLogix or
SmartGuard
600
GuardLogix or
SmartGuard
600
GuardLogix or
SmartGuard
600
142 Publication LOGIX-AP008B-EN-P - June 2008
6ES7 321-1FF1x-xxxx 40-pin
6ES7 321-1EL0x-xxxx n/a
40-pin
8
32
16
S7 300 Digital Output
Modules
Siemens Catalogue
Number
6ES7 332-1FH0x-xxxx
6ES7 332-1FF0x-xxxx
Front Connector Points
20-pin
20-pin
16
8
6ES7 332-5FF0x-xxxx 40-pin 8
6ES7 322-1BH0x-xxxx
6ES7 322-1BH1x-xxxx
6ES7 322-1BL0x-xxxx
6ES7 322-1BF0x-xxxx
6ES7 322-8BF0x-xxxx
6ES7 332-1FL0x-xxxx
6ES7 332-5GH0x-xxxx
6ES7 332-1CF0x-xxxx n/a
20-pin
20-pin
40-pin
20-pin
20-pin
2x20-pin
40-pin
20-pin
16
16
32
8
8
32
16
8
16
S7 300 and S7 400 Parts and RA Equivalents Appendix A
120 ... 230 VAC 1769-IA8I
120 VAC
5 VDC TTL n/a
1769-IG16
1769-IA8I only admits
120 VAC
Range
120/230 VAC
120/230 VAC
Output Current RA Solution
0.5 A
2 A
1769-OA16
1769-OA8
120/230 VAC
24 VDC
24 VDC
24 VDC
2 A
0.5 A
0.5 A
0.5 A
24 VDC
24 VDC
120 VAC
24/48 V
48 … 125 VDC
5 VDC TTL
2 A
0.5 A
1 A
0.5 A
Comments
1769-OA8
S7-300 has fuse per group
S7-300 comes in groups of 1
1769-OB16
1769-OB16P n/a
1769-OB32
1769-OB32T
1769-OB8
1769-OB8 n/a n/a n/a
1769-OG16
High Speed
Publication LOGIX-AP008B-EN-P - June 2008 143
Appendix A S7 300 and S7 400 Parts and RA Equivalents
S7 300 Relay Output
Modules
Siemens Catalogue
Number
6ES7 322-1HH0x-xxxx
6ES7 322-1HF0x-xxxx
6ES7 322-1HF1x-xxxx
6ES7 322-5HF0x-xxxx
Front Connector Points
20-pin
20-pin
40-pin
40-pin
16
8
8
8
S7 300 Analog Input
Modules
Siemens Catalogue
Number
6ES7 331-1KF0x-xxxx
Front
Connector
40
Points
8
6ES7 331-7KF0x-xxxx 20 8
Output Current RA Solution
2 A
5 A
5 A
8 A
1769-OW16
1769-OW8
1769-OW8I
1769-OW8I
Comments
S7-300 module comes with RC filter and overvoltage protecction
S7 300 Digital Combo
Modules
Siemens Catalogue
Number
6ES7 323-1BH0x-xxxx
Front Connector Points
20-pin 8 / 8
6ES7 323-1BL0x-xxxx
6ES7 327-1BH0x-xxxx
40-pin
20-pin
16 / 16
8 / 8
Range Inputs
24 VDC
24 VDC
24 VDC
Output Current RA Solution Comments
24 VDC / 0.5 A 1769-IQ6XOW4 Compact I/O has less I/Os and outputs are relay
24 VDC / 0.5 A n/a
24 VDC / 0.5 A n/a 8 inputs; 8 inputs or outputs
(configurable)
Resolution
(bits)
13
9 / 12 / 14
Type
Voltage,
C,urrent,
Resistance
Temperature
Voltage,
C,urrent,
Resistance
Temperature
Compact
I/O Solution
1769sc-IF8U
1769-IF8U
Comments
1769sc-IF8U
1769-IF8U
144 Publication LOGIX-AP008B-EN-P - June 2008
6ES7 331-7KB0x-xxxx 20
6ES7 331-7NF0x-xxxx
6ES7 331-7NF1x-xxxx
40
40
2
8
8
6ES7 331-7HF0x-xxxx
6ES7 331-7PF0x-xxxx
6ES7 331-7PF1x-xxxx n/a
20
40
40
8
8
8
S7 300 Analog Output
Modules
Siemens Catalogue
Number
6ES7 332-5HD0x-xxxx
6ES7 332-7ND0x-xxxx
Front
Connector
40
20
Points
4
4
6ES7 332-5HB0x-xxxx
6ES7 332-5HF0x-xxxx
20
20
2
8
S7 300 and S7 400 Parts and RA Equivalents Appendix A
16
16
9 / 12 / 14
14
Voltage,
C,urrent,
Resistance
Temperature
Voltage
Voltage
Voltage
Voltage
1769sc-IF8U
1769-IF4
1769-IF8
1769-IF8 Includes hardware interrupt at end of cycle vs 6ES7
331-7NF0x-xxxx
1769-IF8 Voltage
Voltage
RTD
Resistance
1769-IR6
Thermocouple 1769-IT6
1769-IF4I
Resolution
(bits)
12
16
12
12
Type
Voltage
Current
Voltage
Current
Voltage
Current
Voltage
Current
RA Solution
1769-OF4VI
1769-OF4CI
1769-OF4VI
1769-OF4CI
Comments
1769-OF2
1769-OF8V
1769-OF8C
Publication LOGIX-AP008B-EN-P - June 2008 145
Appendix A S7 300 and S7 400 Parts and RA Equivalents
S7 300 Analog Combo
Modules
Siemens Catalogue
Number
6ES7 334-0KE0x-xxxx
Front
Connector
20
Points
4 / 2
6ES7 334-0CE0x-xxxx 20 4 / 2
Resolution
(bits)
12
8
Type RA Solution
Voltage
Current
Pt 100
Voltage and
Current (Inputs
& Outputs)
1769-IF4XOF2
Comments
Outputs only
Voltage
S7 400 Standard Controllers
Siemens
Catalogue
Number
Siemens Short
Reference
Work
Memory
Size
6ES7
412-1XF04-0AB0
6ES7
412-2GX04-0AB0
6ES7
414-2GX04-0AB0
6ES7
414-3XJ04-0AB0
6ES7
414-3EM05-0AB0
6ES7
416-3XK04-0AB0
6ES7
416-3XL04-0AB0
6ES7
416-3ER05-0AB0
6ES7
417-4XL04-0AB0
CPU 412-1
CPU 412-2
CPU 414-2
CPU 414-3
CPU 414-3
PN/DP
CPU 416-2
CPU 416-3
CPU 416-3
PN/DP
CPU 417-4
144KB
256KB
512KB
1.4MB
2.8MB
2.8MB
5.6MB
11.2 MB
20MB
Y
Y
Y
Y
Y
Y
Y
Y
MPI
Y
Comms
Ports
Y
Y
Y
Y
Y
Y
Y
Y
DP
Y
N
N
N
Y
Y
N
N
N
PN
N
Max Load
Memory
Size (RAM)
RA Solution
ControlLogix
64MB
64MB
64MB
64MB
64MB
64MB
64MB
64MB
64MB
1756-L61
1756-L61
1756-L62
1756-L63
1756-L63
1756-L63
1756-L64
1756-L64
1756-L64
146 Publication LOGIX-AP008B-EN-P - June 2008
S7 300 and S7 400 Parts and RA Equivalents Appendix A
Redundant and Fail Safe
Controllers
Siemens
Catalogue
Number
Siemens
Short
Reference
Work
Memory
Size
6ES7
414-4HJ04-0AB0
6ES7
417-4HL04-0AB0
6ES7
416-2FK04-0AB0
CPU 414-4H
CPU 417-4H
CPU-416F-2
1.4MB
20MB
2.6MB
Y
Y
MPI
Y
Y
Y
Comms
Ports
DP
Y
PN
N
N
N
Max Load
Memory
Size (RAM)
RA Solution
ControlLogix
Y
N
Sync ports
Y 64MB
64MB
64MB
1756-L63
1756-L64
1756-L61S
Digital Input Modules
Siemens Catalogue
Number
6ES7 421-7BH01-0AB0
(Interrupt/ diagnostic)
6ES7 421-1BL01-0AA0
6ES7 421-1EL00-0AA0
6ES7 421-1FH20-0AA0
6ES7 421-7DH00 0AB0
(Interrupt/ diagnostic)
Front Connector
48 pin
48 pin
48 pin
48 pin
48 pin
Points
16
32
32
16
32
Range
24V DC
24V DC
120V AC/DC
230V AC/DC
24-60V AC/DC
RA Solution
1756-IB16D
1756-IB32
1756-IA32
1756-IM161
Digital Output Modules
Siemens Catalogue
Number
6ES7 422-1FH00-0AA0
6ES7 422-1HH00-0AA0
6ES7 422 1BH11-0AA0
6ES7 422-1BL00-0AA0
6ES7 422-7BL00-0AB0
(Diagnostic)
Front
Connector
48 pin
48 pin
48 pin
48 pin
48 pin
16
32
32
Points
16
16
Comments
Range Current
230VAC
60V DC230V AC
(relay)
24VDC
24VDC
24VDC
2A
5A
2A
0.5A
0.5A
RA Solution
1756-OA16
1756-OW16I
1756-OB16E
1756-OB32
1756-OB16D
1756-OB32
Comments
Publication LOGIX-AP008B-EN-P - June 2008 147
Appendix A S7 300 and S7 400 Parts and RA Equivalents
Analog Input Modules
Siemens Catalogue
Number
6ES7 431-0HH0-0AB0
Front
Connector
48 pin
6ES7 431-1KF00-0AB0 48 pin
Channels
16
8
6ES7 431-1KF10-0AB0 48 pin
6ES7 431-1FK20-0AB0 48 pin
6ES7 431-7QH00-0AB0
(Interrupt)
48 pin
6ES7 431-7KF00-0AB0 48 pin
6ES7 431-7KF01-0AB0 48 pin
8
8
16
8
8
Resolution
(bits)
13
13
14-16
14
16
16
16
Type RA Solution Comments
16 bits Voltage
Current
Voltage
Current
Impedance
Voltage
Current
Thermocouple
Thermoresistor
Impedance
Voltage
Current
Impedance
1756-IF16
1756-IF8
1756-IR6I
1756-IT6I
1756-IF16
Voltage
Current
Thermocouple
Thermoresistor
Impedance
Voltage
Current
Thermocouple
1756-IR6I
1756-IT6I
1756-IT6I
Thermoresistor 1756-IR6I
16 bits
4 differential inputs
6 RTD
6 Thermocouple
Both 16 bit
16 bit
6 RTD
6 Thermocouple
6 channels
5 channels
Analog Output Modules
Siemens Catalogue
Number
6ES7 432-1HF00-0AB0
Front
Connector
48 pin
Channels
8
Resolution
(bits)
13
Type
Voltage
Current
RA Solution
1756-OF8
Comments
15 bits
148 Publication LOGIX-AP008B-EN-P - June 2008
Appendix
B
Siemens HMI Cross Reference Table
Use this appendix to compare Rockwell Automation panels to specific types of
Siemens panels.
Topic
SIMATIC Micro Panels and Rockwell Automation Equivalents
SIMATIC Panels - 7x Series and Rockwell Automation Equivalents
SIMATIC Panels - 17x Series and Rockwell Automation Equivalents
SIMATIC Panels - 27x Series and Rockwell Automation Equivalents
SIMATIC Multi Panels - 27x Series and Rockwell Automation Equivalents
SIMATIC Multi Panels - 37x Series and Rockwell Automation Equivalents
Page
SIMATIC Micro Panels and
Rockwell Automation
Equivalents
SIMATIC Micro Panels
Siemens
Catalog
Number
Short
Reference
6AV6545-
0AA15-2AX0
SIMATIC
TP070
Phased out in
April 2007
Description
5.7 in. STN display, Blue mode
(4 levels),
320x240 pixels, touch,
24V DC only
Mem.
Comm.
Options
6AV6640-
0BA11-0AX0
SIMATIC OP
73MICRO
3 in. STN monochrome display,
160x48 pixels, keypad,
24V DC only
128 KB 1xRS485,
S7-200 compatible, no printer port
128 KB 1xRS485,
S7-200 compatible, no printer port
Rockwell Automation Solution
Rockwell
Automation
Catalog
Number
2711P-
K4M5D
Name
PanelView
Plus 400 grayscale keypad
Description
3.8 in. STN 32-level grayscale display,
320 x 240 pixels,
RS-232 communication, keypad, 24V DC,
64 MB flash, USB printing capabilities
2711P-
T6M5D
PanelView
Plus 600 grayscale touch
5.5 in. STN 32-level grayscale display,
320 x 240 pixels,
RS-232 communication, touch, 24V DC, USB printing capabilities
Publication LOGIX-AP008B-EN-P - June 2008 149
Appendix B Siemens HMI Cross Reference Table
SIMATIC Micro Panels
Siemens
Catalog
Number
Short
Reference
Description Mem.
Comm.
Options
6AV6640-
0CA01-0AX0
6AV6640-
0CA11-0AX0
SIMATIC TP
170MICRO
Phased out in
April 2007
SIMATIC TP
177MICRO
5.7 in. STN display, Blue mode
(4 levels),
320x240 pixels, touch,
24V DC only, limited application functionality
5.7 in. STN display, Blue mode
(4 levels),
320x240 pixels, touch,
24V DC only
256 KB 1xRS485,
S7-200 compatible, no printer port
256 KB 1xRS485,
S7-200 compatible, no printer port
6AV6610-
0AA01-1CA8
WINCC
FLEXIBLE
MICRO software
Configuration and programming software for
Simatic micro panels only
N/A N/A
Rockwell Automation Solution
Rockwell
Automation
Catalog
Number
2711P-
T6M5D
Name
PanelView
Plus 600 grayscale touch
Description
5.5 in. STN 32-level grayscale display,
320x240 pixels,
RS-232 communication, touch, 24V DC, USB printing capabilities
2711P-
T6M5D
9701-
VWSTMENE
PanelView
Plus 600 grayscale touch
RSView
Studio
Machine
Edition software
5.5 in. STN 32-level grayscale display,
320x240 pixels,
RS-232 communication, touch, 24V DC, USB printing capabilities
RSView Studio for
Machine Edition configuration software for developing and testing machine level HMI applications
150 Publication LOGIX-AP008B-EN-P - June 2008
Siemens HMI Cross Reference Table Appendix B
SIMATIC Panels - 7x Series and Rockwell Automation
Equivalents
SIMATIC Panels - 7x Series
Siemens
Catalog
Number
Short
Reference
6AV6641-
0AA11-0AX0
6AV6641-
0BA11-0AX0
6AV6641-
0CA01-0AX0
6AV6621-
0AA01-0AA0
SIMATIC
OP73
SIMATIC
OP77A
SIMATIC
OP77B
WINCC
FLEXIBLE
COMPACT software
Description
3 in. STN monochrome display,
160x48 pixels, keypad,
24V DC only
4.5 in. STN monochrome display,
160x64 pixels, keypad.
24V DC only
4.5 in. STN monochrome display,
160x64 pixels, keypad,
24V DC only
Configuration and programming software for
Simatic OP77,
OP/TP170, and micro panels
Mem.
256 KB 1x RS485,
256 KB
1 MB
N/A
Comm.
Options
S7-200, S7-
300/400 compatible, no printer port
1xRS422,
1xRS485,
S7-200,
S7-300/400,n o printer port
1xRS232,
1xRS422,
1xRS485,
USB, S7-200,
S7-300/400, printer port available
N/A
Rockwell Automation Solution
Rockwell
Automation
Catalog
Number
2711P-
K4M5D
Name
PanelView
Plus 400 grayscale keypad
Description
3.8 in. STN 32-level grayscale display,
320x240 pixels,
RS-232 communication, keypad, 24V DC,
64 MB flash, USB printing capabilities
2711P-
K4M5D
PanelView
Plus 400 grayscale keypad
2711P-
K4M5D
PanelView
Plus 400 grayscale keypad
3.8 in. STN 32-level grayscale display,
320x240 pixels,
RS-232 communication, keypad, 24V DC,
64 MB flash, USB printing capabilities
3.8 in. STN 32-level grayscale display
320x240 pixels,
RS-232 communication, keypad, 24V DC,
64 MB flash, USB printing capabilities
9701-
VWSTMENE
RSView
Studio for
Machine
Edition software
RSView Studio
Machine Edition configuration software for developing and testing machine level HMI applications
Publication LOGIX-AP008B-EN-P - June 2008 151
Appendix B Siemens HMI Cross Reference Table
SIMATIC Panels - 17x
Series and Rockwell
Automation Equivalents
SIMATIC Panels - 17x Series
Siemens
Catalog
Number
6AV6545-
0BA15-2AX0
6AV6545-
0BB15-2AX0
6AV6545-
0BC15-2AX0
6AV6542-
0BB15-2AX0
6AV6642-
0DC01-1AX0
Short
Reference
Description Mem.
Comm.
Options
SIMATIC
TP170A Blue mode
Phased out in
April 2007
SIMATIC
TP170B Blue mode
Phased out in
April 2007
SIMATIC
TP170B color
Phased out in
April 2007
SIMATIC
OP170B Blue mode
Phased out in
April 2007
SIMATIC
OP177B Blue mode
5.7 in. STN display, Blue mode
(4 levels),
320x240 pixels, touch,
24V DC only
5.7 in. STN display, Blue mode
(4 levels),
320x240 pixels, touch,
24V DC only
5.7 in. STN display, color
(256 colors),
320x240 pixels, touch.
24V DC only
5.7 in. STN display, Blue mode
(4 levels),
320x240 pixels, keypad and touch,
24V DC only
5.7 in. STN display, Blue mode
(4 levels),
320x240 pixels, keypad and touch,
24V DC only
320 KB 1xRS232,
1xRS422,
1xRS485, S5,
S7-200,
S7-300/400, and third-party controllers, no printer port
768 KB 2xRS232,
1xRS422,
1xRS485, S5,
S7-200,
S7-300/400, and third-party controllers, printer port available
768 KB 2xRS232,
1xRS422,
1xRS485, S5,
S7-200,
S7-300/400, and third-party controllers, printer port available
768 KB 2xRS232,
1xRS422,
1xRS485, S5,
S7-200,
S7-300/400, and third-party controllers, printer port available
2 MB 1xRS422,
1xRS485,
USB,
Ethernet, S5,
S7-200,
S7-300/400, and third-party controllers, printer port available
Rockwell Automation Solution
Rockwell
Automation
Catalog
Number
2711P-
T6M20D
Name
PanelView
Plus 600 grayscale touch
Description
5.5 in. STN 32-level grayscale display,
320x240 pixels,
EtherNet/IP,
RS-232 communication, touch, 24V DC,
64 MB flash, USB printing capabilities
2711P-
T6M20D
PanelView
Plus 600 grayscale touch
2711P-
T6C20D
PanelView
Plus 600 color touch
5.5 in. STN 32-level grayscale display,
320x240 pixels,
EtherNet/IP,
RS-232 communication, touch, 24V DC,
64 MB flash, USB printing capabilities
5.5 in. TFT color display, 320x240 pixels, 18-bit color depth, EtherNet/IP,
RS-232 communication, touch, 24V DC,
64 MB flash, USB printing capabilities
2711P-
B6M20D
PanelView
Plus 600 grayscale touch and keypad
5.5 in. STN 32-level grayscale display,
320x240 pixels,
EtherNet/IP,
RS-232 communication, touch and keypad,
24V DC, 64 MB flash, USB printing capabilities
2711P-
B6M20D
PanelView
Plus 600 grayscale touch and keypad
5.5 in. STN 32-level grayscale display,
320x240 pixels,
EtherNet/IP,
RS-232 communication, touch and keypad,
24V DC, 64 MB flash, USB printing capabilities
152 Publication LOGIX-AP008B-EN-P - June 2008
Siemens HMI Cross Reference Table Appendix B
SIMATIC Panels - 17x Series
Siemens
Catalog
Number
Short
Reference
6AV6642-
0AA11-0AX0
6AV6642-
0BA01-1AX0
6AV6642-
0BC01-1AX0
SIMATIC
TP177A Blue mode
SIMATIC
TP177B color
SIMATIC
TP177B Blue mode
Description
5.7 in. STN display, Blue mode
(4 levels),
320x240 pixels, touch,
24V DC only
5.7 in. STN display, color
(256 colors),
320x240 pixels, touch.
24V DC only
5.7 in. STN display, Blue mode
(4 levels),
320x240 pixels, touch,
24V DC only
Mem.
512 KB
2 MB
2 MB
Comm.
Options
1xRS422,
1xRS485,
S7-200,
S7-300/400 compatible, no printer port
1xRS422,
1xRS485,
USB,
Ethernet, S5,
S7-200,
S7-300/400, and third-party controllers, printer port available
1xRS422,
1xRS485,
USB, S5,
S7-200,
S7-300/400, and third-party controllers, printer port available
Rockwell Automation Solution
Rockwell
Automation
Catalog
Number
2711P-T6M20
D
2711P-T6C20
D
Name
PanelView
Plus 600
Grayscale
Touch
PanelView
Plus 600
Color Touch
Description
5.5-inch STN
32-level Grayscale
Display, Display
320 x 240, pixels,
EtherNet/IP,
RS-232
Communications,
Touch, 24VDC, 64
MB Flash, USB
Printing capabilities
5.5-inch TFT Color display; 320 x 240 pixels, 18-bit Color depth, EtherNet/IP,
RS-232
Communications,
Touch, 24VDC, 64
MB Flash, USB
Printing capabilities
2711P-T6M20
D
PanelView
Plus 600
Grayscale
Touch
5.5-inch STN
32-level Grayscale
Display, Display
320 x 240, pixels,
EtherNet/IP,
RS-232
Communications,
Touch, 24VDC, 64
MB Flash, USB
Printing capabilities
Publication LOGIX-AP008B-EN-P - June 2008 153
Appendix B Siemens HMI Cross Reference Table
SIMATIC Panels - 17x Series
Siemens
Catalog
Number
Short
Reference
6AV6642-
6AV6642-
6AV6621-
8BA10-0AA0
0DA01-1AX0
0AA01-0AA0
SIMATIC
TP177B color stainless steel
SIMATIC
OP177B color
WINCC
FLEXIBLE
COMPACT software
Description
5.7 in. STN display, color
(256 colors),
320x240 pixels, touch,
24V DC only, stainless steel bezel
5.7 in. STN display, color
(256 colors),
320x240 pixels, keypad and touch,
24V DC only
Configuration and programming software for
Simatic OP77,
OP/TP170 & micro panels
Mem.
2 MB
2 MB
N/A
Comm.
Options
1xRS422,
1xRS485,
USB,
Ethernet, S5,
S7-200,
S7-300/400, and third-party controllers, printer port available
1xRS422,
1xRS485,
USB,
Ethernet, S5,
S7-200,
S7-300/400, and third-party controllers, printer port available
N/A
2711P-
B6C20D
9701-
VWSTMENE
Rockwell Automation Solution
Rockwell
Automation
Catalog
Number
2711P-
T6C20D
Name
PanelView
Plus 600 color touch
Description
5.5 in. TFT color display, 320x240 pixels, 18-bit color depth, EtherNet/IP,
RS-232 communication, touch, 24V DC,
64 MB flash, USB printing capabilities
PanelView
Plus 600 color touch and keypad
RSView
Studio
Machine
Edition software
5.5 in. TFT color display, 320x240 pixels, 18-bit color depth, EtherNet/IP,
RS-232 communication, touch and keypad,
24V DC, 64 MB flash, USB printing capabilities
RSView Studio
Machine Edition configuration software for developing and testing machine level HMI applications
154 Publication LOGIX-AP008B-EN-P - June 2008
Siemens HMI Cross Reference Table Appendix B
SIMATIC Panels - 27x
Series and Rockwell
Automation Equivalents
SIMATIC Panels - 27x Series
Siemens
Catalog
Number
Short
Reference
6AV6545-
0CA10-0AX0
6AV6545-
0CC10-0AX0
6AV6542-
0CA10-0AX0
6AV6542-
0CC10-0AX0
SIMATIC
TP270 6 in. color
Phased out in
October 2006
SIMATIC
TP270 10 in. color
Phased out in
October 2006
SIMATIC
OP270 6 in. color
Phased out in
October 2006
SIMATIC
OP270 10 in. color
Phased out in
October 2006
Description
5.7 in. STN display, color
(256 colors),
320x240 pixels, touch,
24V DC only
10.4 in. STN display, color
(256 colors),
640x480 pixels, touch,
24V DC only
5.7 in. STN display, color
(256 colors),
320x240 pixels, keypad,
24V DC only
10.4 in. STN display, color
(256 colors),
640x480 pixels, keypad,
24V DC only
Mem.
2 MB
2 MB
2 MB
2 MB
Comm.
Options
2xRS232,
1xRS422,
1xRS485,
USB, S5,
S7-200,
S7-300/400, and third-party controllers, printer port available.
2xRS232,
1xRS422,
1xRS485,
USB, S5,
S7-200,
S7-300/400, and third-party controllers, printer port available
2xRS232,
1xRS422,
1xRS485,
USB, S5,
S7-200,
S7-300/400, and third-party controllers, printer port available
2xRS232,
1xRS422,
1xRS485,
USB, S5,
S7-200,
S7-300/400, and third-party controllers, printer port available
Rockwell Automation solution
Rockwell
Automation
Catalog
Number
2711P-
T6C20D
Name
PanelView
Plus 600 color touch
Description
5.5 in. TFT color display, 320x240 pixels, 18-bit color depth, EtherNet/IP,
RS-232 communication, touch, 24V DC,
64 MB flash, USB printing capabilities
2711P-
T10C4D1
2711P-
K6C20D
2711P-
K10C4D1
PanelView
Plus 1000 color touch
PanelView
Plus 600 color
PanelView
Plus 1000 color keypad
10.4 in. TFT display,
640x480 pixels,
18-bit color,
EtherNet/IP and
RS-232, touch,
24V DC, 64 MB flash, USB printing capabilities
5.5 in. TFT color display, 320x240 pixels, 18-bit color depth, EtherNet/IP,
RS-232 communication, keypad, 24V DC,
64 MB flash, USB printing capabilities
10.4 in. TFT display,
640x480 pixels,
18-bit color,
EtherNet/IP and
RS-232, keypad,
24V DC, 64 MB flash, USB printing capabilities
Publication LOGIX-AP008B-EN-P - June 2008 155
Appendix B Siemens HMI Cross Reference Table
SIMATIC Panels - 27x Series
Siemens
Catalog
Number
Short
Reference
6AV6643-
0AA01-1AX0
6AV6643-
0BA01-1AX0
6AV6622-
0BA01-0AA0
SIMATIC TP
277 6 in. color
SIMATIC OP
277 6 in. color
WINCC
FLEXIBLE
STANDARD software
Description
5.7 in. STN display, color
(256 colors),
320x240 pixels, touch,
24V DC only
5.7 in. STN display, color
(256 colors),
320x240 pixels, keypad,
24V DC only
Configuration and programming software for
Simatic
OP/TP/
MP270,
MP370, OP77,
OP/TP170 and micro panels
Mem.
4 MB
4 MB
N/A
Comm.
Options
1xRS422,
1xRS485,
USB,
Ethernet: S5,
S7-200,
S7-300/400, and third-party controllers, printer port available
1xRS422,
1xRS485,
USB,
Ethernet, S5,
S7-200,
S7-300/400, and third-party controllers, printer port available.
N/A
2711P-
K6C20D
9701-
VWSTMENE
Rockwell Automation solution
Rockwell
Automation
Catalog
Number
2711P-
T6C20D
Name
PanelView
Plus 600 color touch
Description
5.5 in. TFT color display, 320x240 pixels, 18-bit color depth, EtherNet/IP,
RS-232 communication, touch, 24V DC,
64 MB flash, USB printing capabilities
PanelView
Plus 600 color
RSView
Studio
Machine
Edition software
5.5 in. TFT color display, 320x240 pixels, 18-bit color depth, EtherNet/IP,
RS-232 communication, keypad, 24V DC,
64 MB flash, USB printing capabilities
RSView Studio
Machine Edition configuration software for developing and testing machine level HMI applications
156 Publication LOGIX-AP008B-EN-P - June 2008
Siemens HMI Cross Reference Table Appendix B
SIMATIC Multi Panels - 27x
Series and Rockwell
Automation Equivalents
SIMATIC Multi Panels - 27x Series
Siemens
Catalog
Number
6AV6542-
6AV6545-
6AV6545-
6AV6643-
0AG10-0AX0
0AG10-0AX0
0AH10-0AX0
0CB01-1AX0
Short
Reference
SIMATIC
MP270B keypad 10 in.
Phased out in
October 2006
SIMATIC
MP270B touch, 10 in.
Phased out in
October 2006
SIMATIC
MP270B touch, 6 in.
Phased out in
October 2006
SIMATIC MP
277 touch,
8 in.
Description
10.4 in.
TFT display, color (64 k colors),
640x480 pixels, keypad,
24V DC only
10.4 in. TFT display, color
(64 k colors),
640x480 pixels, touch,
24V DC only
5.7 in. TFT display, color
(64 k colors),
320x240 pixels, touch,
24V DC only
7.5 in. TFT display, color
(64 k colors),
640x480 pixels, touch,
24V DC only
Mem.
5 MB
5 MB
5 MB
6 MB
Comm.
Options
2xRS422,
1xRS485,
USB,
Ethernet, S5,
S7-200,
S7-300/400, and third-party controllers, printer port available
2xRS422,
1xRS485,
USB,
Ethernet, S5,
S7-200,
S7-300/400, and third-party controllers, printer port available
2xRS422,
1xRS485,
USB,
Ethernet, S5,
S7-200,
S7-300/400, and third-party controllers, printer port available
1xRS422,
1xRS485,
2xUSB,
Ethernet, S5,
S7-200,
S7-300/400, and third-party controllers, printer port available
Rockwell Automation Solution
Rockwell
Automation
Catalog
Number
2711P-
K10C4D1
Name
PanelView
Plus 1000 color keypad
Description
10.4 in. TFT display,
640x480 pixels,
18-bit color,
EtherNet/IP and
RS-232, keypad,
24V DC, 64 MB flash, USB printing capabilities
2711P-
T10C4D1
2711P-
K6C20D
2711P-
T7C4D1
PanelView
Plus 1000 color touch
PanelView
Plus 600 color
PanelView
Plus 700 color touch
10.4 in. TFT display,
640x480 pixels,
18-bit color,
EtherNet/IP and
RS-232, touch,
24V DC, 64 MB flash, USB printing capabilities
5.5 in. TFT color display, 320x240 pixels, 18-bit color depth, EtherNet/IP,
RS-232 communication, keypad, 24V DC,
64 MB flash, USB printing capabilities
6.5 in.TFT display,
640x480 pixels,
18-bit color,
EtherNet/IP and
RS-232, touch,
24V DC, 64 MB flash, USB printing capabilities
Publication LOGIX-AP008B-EN-P - June 2008 157
Appendix B Siemens HMI Cross Reference Table
SIMATIC Multi Panels - 27x Series
Siemens
Catalog
Number
6AV6643-
0CD01-1AX0
_
6AV6643-
0DB01-1AX0
6AV6643-
0DD01-1AX0
6AV6622-
0BA01-0AA0
Short
Reference
SIMATIC MP
277 touch,
10 in.
SIMATIC MP
277 touch,
10 in., stainless steel
SIMATIC MP
277 keypad,
8 in.
SIMATIC MP
277 keypad,
10 in.
WINCC
FLEXIBLE
STANDARD software
Description
10.4 in. TFT display, color
(64 k colors),
640x480 pixels, touch,
24V DC only
10.4 in. TFT display, color
(64 k colors),
640x480 pixels, touch,
24V DC only, stainless steel bezel,
IP66
7.5 in. TFT display, color
(64 k colors),
640x480 pixels, keypad,
24V DC only
10.5 in. TFT display, color
(64 k colors),
640x480 pixels, keypad,
24V DC only
Configuration and programming software for
Simatic
OP/TP/
MP270,
MP370, OP77,
OP/TP170 and micro panels
Mem.
6 MB
6 MB
6 MB
6 MB
N/A
Comm.
Options
1xRS422,
1xRS485,
2xUSB,
Ethernet, S5,
S7-200,
S7-300/400, and third-party controllers, printer port available
1xRS422,
1xRS485,
2xUSB,
Ethernet, S5,
S7-200,
S7-300/400, and third-party controllers, printer port available
N/A
1xRS422,
1xRS485,
2xUSB,
Ethernet: S5,
S7-200,
S7-300/400, and third-party controllers, printer port available
1xRS422,
1xRS485,
2xUSB,
Ethernet, S5,
S7-200,
S7-300/400, and third-party controllers, printer port available
Rockwell Automation Solution
Rockwell
Automation
Catalog
Number
2711P-
T10C4D1
2711P-
T10C4D1
2711P-
K7C4D1
2711P-
K10C4D1
9701-
VWSTMENE
Name
PanelView
Plus 1000 color touch
PanelView
Plus 1000 color touch
PanelView
Plus 700 color keypad
PanelView
Plus 1000 color keypad
RSView
Studio
Machine
Edition software
Description
10.4 in. TFT display,
640x480 pixels,
18-bit color,
EtherNet/IP and
RS-232, touch,
24V DC, 64 MB flash, USB printing capabilities
10.4 in. TFT display,
640x480 pixels,
18-bit color,
EtherNet/IP and
RS-232, touch,
24V DC, 64 MB flash, USB printing capabilities
6.5 in. TFT display,
640x480 pixels,
18-bit color,
EtherNet/IP and
RS-232, keypad,
24V DC, 64 MB flash, USB printing capabilities
10.4 in. TFT display,
640x480 pixels,
18-bit color,
EtherNet/IP and
RS-232, keypad,
24V DC, 64 MB flash, USB printing capabilities
RSView Studio
Machine Edition configuration software for developing and testing machine level HMI applications
158 Publication LOGIX-AP008B-EN-P - June 2008
Siemens HMI Cross Reference Table Appendix B
SIMATIC Multi Panels - 37x
Series and Rockwell
Automation Equivalents
SIMATIC Multi Panels - 37x Series
Siemens
Catalog
Number
6AV6542-
6AV6545-
6AV6545-
0DA10-0AX0
0DA10-0AX0
0DB10-0AX0
Short
Reference
SIMATIC
MP370 keypad, 12 in.
SIMATIC
MP370 touch,
12 in.
SIMATIC
MP370 touch,
15 in.
Description
12.1 in. TFT display, color
(256 colors),
800x600 pixels, keypad,
24V DC only
12.1 in. TFT display, color
(256 colors),
800x600 pixels, touch,
24V DC only
15.1 in. TFT display, color
(256 colors),
1024x768 pixels, touch,
24V DC only
Mem.
Comm.
Options
12.5 MB 1xTTY,
2xRS232,
1xRS422,
1xRS485,
1xUSB,
Ethernet, S5,
S7-200,
S7-300/400, and third-party controllers, printer port
12.5 MB 1xTTY,
2xRS232,
1xRS422,
1xRS485,
1xUSB,
Ethernet, S5,
S7-200,
S7-300/400, and third-party controllers, printer port
2711P-
T12C4D1
2711P-
T15C4D1
12.5 MB 1xTTY,
2xRS232,
1xRS422,
1xRS485,
1xUSB,
Ethernet, S5,
S7-200,
S7-300/400, and third-party controllers, printer port
Rockwell Automation Solution
Rockwell
Automation
Catalog
Number
2711P-
K12C4D1
Name
PanelView
Plus 1250 color keypad
Description
12.1in. TFT display,
800x600 pixels,
18-bit color,
EtherNet/IP and
RS-232, keypad,
24V DC, 64 MB flash, USB printing capabilities
PanelView
Plus 1250 color touch
PanelView
Plus 1500 color touch
12.1 in. TFT display,
800x600 pixels,
18-bit color,
EtherNet/IP and
RS-232, touch,
24V DC, 64 MB flash, USB printing capabilities
15 in. TFT display,
1024x768 pixels,
18-bit color,
EtherNet/IP and
RS-232, touch,
24V DC, 64 MB flash, USB printing capabilities
6AV6545-
8DB10-0AA0
SIMATIC
MP370 touch,
15 in., stainless steel
15.1 in. TFT display, color
(256 colors),
1024x768 pixels, touch,
24V DC only, stainless steel bezel,
IP66
12.5 MB 1xTTY,
2xRS232,
1xRS422,
1xRS485,
1xUSB,
Ethernet, S5,
S7-200,
S7-300/400, and third -party controllers, printer port
2711P-
T15C4D1
PanelView
Plus 1500 color touch
15 in. TFT display,
1024x768 pixels,
18-bit color,
EtherNet/IP and
RS-232, touch,
24V DC, 64 MB flash, USB printing capabilities
Publication LOGIX-AP008B-EN-P - June 2008 159
Appendix B Siemens HMI Cross Reference Table
SIMATIC Multi Panels - 37x Series
Siemens
Catalog
Number
6AV6 644-
0AA01-2AX0
6AV6 644-
0BA01-2AX0
6AV6 644-
0AB01-2AX0
Short
Reference
SIMATIC
MP377 touch
12.1 in.
SIMATIC
MP377 keypad,
12.1 in.
SIMATIC
MP377 touch,
15 in.
Description Mem.
Comm.
Options
12.1 in. TFT display,
65,536 colors,
800x600 pixels, touch,
24V DC only
12.5 MB 1xTTY,
2xRS232,
1xRS422,
1xRS485,
2xUSB,
2xEthernet, S5,
S7-200,
S7-300/400, and third-party controllers, printer port
12.1 in. TFT display,
65,536 colors,
800x600 pixels, keypad,
24V DC only
12.5 MB 1xTTY,
2xRS232,
1xRS422,
1xRS485,
2xUSB,
2xEthernet, S5,
S7-200,
S7-300/400, and third-party controllers, printer port
2711P-
K12C4D1
15 in. TFT display,
65,536 colors,
1024x768 pixels, touch,
24V DC only
12.5 MB 1xTTY,
2xRS232,
1xRS422,
1xRS485,
2xUSB,
2xEthernet, S5,
S7-200,
S7-300/400, and third-party controllers, printer port
Rockwell Automation Solution
Rockwell
Automation
Catalog
Number
2711P-
T12C4D1
Name
PanelView
Plus 1250 color touch
Description
12.1 in. TFT display,
800x600 pixels,
18-bit color,
EtherNet/IP and
RS-232, touch,
24V DC, 64 MB flash, USB printing capabilities
2711P-
T15C4D1
PanelView
Plus 1250 color keypad
PanelView
Plus 1500 color touch
12.1 in. TFT display,
800x600 pixels,
18-bit color,
EtherNet/IP and
RS-232, keypad,
24V DC, 64 MB flash, USB printing capabilities
15 in. TFT display,
1024x768 pixels,
18-bit color,
EtherNet/IP and
RS-232, touch,
24V DC, 64 MB flash, USB printing capabilities
6AV6 644-
0BA01-2AX0
SIMATIC
MP377 touch,
19 in.
19 in. TFT display,
65,536 colors,
1280x1024 pixels, touch,
24V DC only
12.5 MB 1xTTY,
2xRS232,
1xRS422,
1xRS485,
2xUSB,
2xEthernet, S5,
S7-200,
S7-300/400, and third-party controllers, printer port
2711P-
T15C4D1
PanelView
Plus 1500 color touch
15 in. TFT display,
1024x768 pixels,
18-bit color,
EtherNet/IP and
RS-232, touch,
24V DC, 64 MB flash, USB printing capabilities
6AV6622-
0BA01-0AA0
WINCC
FLEXIBLE
STANDARD software
Configuration and programming software for
Simatic
OP/TP/
MP270,
MP370, OP77,
OP/TP170 and micro panels
N/A N/A 9701-
VWSTMENE
RSView
Studio
Machine
Edition software
RSView Studio
Machine Edition configuration software for developing and testing machine level HMI applications
160 Publication LOGIX-AP008B-EN-P - June 2008
Notes:
Siemens HMI Cross Reference Table Appendix B
Publication LOGIX-AP008B-EN-P - June 2008 161
Appendix B Siemens HMI Cross Reference Table
162 Publication LOGIX-AP008B-EN-P - June 2008
Rockwell Automation
Support
Rockwell Automation provides technical information on the Web to assist you in using its products. At http://support.rockwellautomation.com
, you can find technical manuals, a knowledge base of FAQs, technical and application notes, sample code and links to software service packs, and a MySupport feature that you can customize to make the best use of these tools.
For an additional level of technical phone support for installation, configuration, and troubleshooting, we offer TechConnect support programs. For more information, contact your local distributor or Rockwell Automation representative, or visit http://support.rockwellautomation.com
.
Installation Assistance
If you experience a problem within the first 24 hours of installation, please review the information that's contained in this manual. You can also contact a special Customer
Support number for initial help in getting your product up and running.
United States
Outside United
States
1.440.646.3434
Monday – Friday, 8am – 5pm EST
Please contact your local Rockwell Automation representative for any technical support issues.
New Product Satisfaction Return
Rockwell Automation tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility. However, if your product is not functioning and needs to be returned, follow these procedures.
United States
Outside United
States
Contact your distributor. You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor in order to complete the return process.
Please contact your local Rockwell Automation representative for the return procedure.
Publication LOGIX-AP008B-EN-P - June 2008 164
Supersedes publication LOGIX-AP008B-EN-P Copyright © 2008 Rockwell Automation, Inc. All rights reserved. Printed in the U.S.A.
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Related manuals
advertisement
Table of contents
- 7 Purpose
- 7 Conversion versus Translation
- 8 Terminology
- 8 Additional Resources
- 9 PLC Logic Conversion Services Provided by Rockwell Automation
- 13 Introduction
- 13 S7 Controllers
- 14 I/O Systems
- 25 Networks
- 31 Conversion of HMI
- 32 Conversion of Systems Containing Distributed Controllers
- 34 Connecting Siemens and Rockwell Automation Devices
- 35 Introduction
- 36 S7 Organization Blocks Compared to Logix Tasks
- 47 Tags Not Addresses
- 51 I/O and Alias Tags
- 53 Programming Languages
- 57 Add-On Instructions
- 58 The Common Industrial Protocol (CIP)
- 60 Data Exchange between Controllers
- 61 User-Defined Data Types
- 62 Asynchronous I/O Updating
- 62 The DINT Data Type
- 63 Phase Manager
- 65 Coordinated System Time (CST)
- 65 Timestamped Inputs
- 65 Scheduled Outputs
- 66 No Temporary Variables
- 66 No Accumulators or Special Registers needed
- 67 Introduction
- 68 Logix System Functions
- 68 Copy
- 69 Date and Time Setting and Reading
- 69 Read System Time
- 70 Handling of Interrupts
- 70 Errors
- 71 Status – Controller
- 71 Status – Module
- 72 Status – for OBs and Tasks
- 72 Timers
- 73 Conversion Routines
- 73 String Handling Routines
- 74 Examples of System Function Calls
- 83 Introduction
- 83 Conversion Code Examples
- 120 Other Topics Related to Programming
- 121 A Larger Example - Control Module
- 129 Introduction
- 129 Not Selecting Appropriate Hardware
- 130 Underestimating Impact of Task Scheduling
- 130 Performing Translation Instead of Conversion
- 130 Not Using the Most Appropriate Logix Languages
- 131 Implementation of Incorrect Data Types – DINT versus INT
- 132 User Code Emulating Existing Instructions
- 133 Incorrect Usage of COP, MOV, and CPS
- 133 Incorrect Usage of CPT
- 133 Not Handling Strings in Optimal Way
- 133 Extensive Usage of Jumps
- 133 Not Using Aliased Tags
- 135 Introduction
- 135 Hardware Terminology
- 136 Software Terminology
- 139 Introduction
- 140 Compact S7 300 CPUs
- 140 Standard S7 300 CPUs
- 141 Technology S7 300 CPUs
- 142 Fail-Safe S7 300 CPUs
- 142 S7 300 Digital Input Modules
- 143 S7 300 Digital Output Modules
- 144 S7 300 Relay Output Modules
- 144 S7 300 Digital Combo Modules
- 144 S7 300 Analog Input Modules
- 145 S7 300 Analog Output Modules
- 146 S7 300 Analog Combo Modules
- 146 S7 400 Standard Controllers
- 147 Redundant and Fail Safe Controllers
- 147 Digital Input Modules
- 147 Digital Output Modules
- 148 Analog Input Modules
- 148 Analog Output Modules
- 149 SIMATIC Micro Panels and Rockwell Automation Equivalents
- 151 SIMATIC Panels - 7x Series and Rockwell Automation Equivalents
- 152 SIMATIC Panels - 17x Series and Rockwell Automation Equivalents
- 155 SIMATIC Panels - 27x Series and Rockwell Automation Equivalents
- 157 SIMATIC Multi Panels - 27x Series and Rockwell Automation Equivalents
- 159 SIMATIC Multi Panels - 37x Series and Rockwell Automation Equivalents