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.
Table of Contents Preface Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Conversion versus Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 PLC Logic Conversion Services Provided by Rockwell Automation . .
Table of Contents 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 . . . . . . . . . . . . . . .
Table of Contents Get Scan Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Chapter 4 Conversion of Typical Program Structures Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Conversion Code Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Ladder Logic Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Jumps and Decision Making . . . . . . . . . . .
Table of Contents Chapter 6 S7 to Logix Glossary Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Hardware Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Software Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Appendix A S7 300 and S7 400 Parts and RA Equivalents Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preface Purpose 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.
Preface Terminology 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.
Preface PLC Logic Conversion Services Provided by Rockwell Automation Rockwell Automation provides additional services for PLC logic conversion.
Preface 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.
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.
Preface Notes: 12 Publication LOGIX-AP008B-EN-P - June 2008
Chapter 1 Hardware Conversion Introduction 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.
Chapter 1 Hardware Conversion Sample Selection of Current Siemens S7 Controllers 315F-2 PN/DP (Safety) 6ES7 317-2FK13-0AB0 GuardLogix L61S, L62S, L63S 414-H (Redundant) 6ES7 414-4HM14-0AB0 L61-L65 with SRM 417-H 6ES7 417-4HT14-0AB0 PCS7 – Uses 417-4 controller 6ES7 315-2FH13-0AB0 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.
Hardware Conversion Chapter 1 STEP 7 Hardware Configuration Program Drag the selected module to the rack configuration screen.
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.
Hardware Conversion Chapter 1 This table lists the Logix equivalents for some popular S7 I/O modules.
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. Select an item and it will appear in the rack in your I/O configuration.
Hardware Conversion Chapter 1 The view below shows the tags partly expanded. The profile contains configuration and status data as well as I/O data. Refer to Chapter 4 for more information.
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.
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.
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.
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.
Chapter 1 Hardware Conversion Shown below are device profile tags in RSLogix 5000 software, available for hundreds of Rockwell Automation devices.
Hardware Conversion Networks Chapter 1 Refer to these sections for information about the networks. 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.
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.
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.
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.
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.
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 Publication LOGIX-AP008B-EN-P - June 2008 Refer to Appendix B.
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.
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.
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.
Chapter 2 Logix Features that May Not be Familiar to S7 Users Introduction This chapter describes Logix features that may not be familiar to S7 users.
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.
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: OB1 is the root of the call hierarchy for all continuously executed code.
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.
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.
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.
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.
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”.
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.
Chapter 2 Logix Features that May Not be Familiar to S7 Users 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.
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. An event task is configured by opening the task's Task Properties page and selecting Type Event.
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.
Logix Features that May Not be Familiar to S7 Users Tags Not Addresses 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.
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.
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 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.
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 In Logix, there is a controller-scope tag database and program-scope tag databases associated with each Program.
Logix Features that May Not be Familiar to S7 Users I/O and Alias Tags 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.
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.
Logix Features that May Not be Familiar to S7 Users Programming Languages Chapter 2 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.
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.
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.
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.
Logix Features that May Not be Familiar to S7 Users Add-On Instructions 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.
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.
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. Networks are described further in Chapter 1.
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.
Logix Features that May Not be Familiar to S7 Users User-Defined Data Types Chapter 2 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.
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.
Logix Features that May Not be Familiar to S7 Users Phase Manager 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.
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. 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.
Logix Features that May Not be Familiar to S7 Users Coordinated System Time (CST) Chapter 2 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.
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.
Chapter 3 Conversion of System Software and Standard Functions Introduction This chapter lists the more commonly used S7 System Functions, explains how the equivalent is done in Logix and provides several specific examples.
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.
Conversion of System Software and Standard Functions Date and Time Setting and Reading Chapter 3 The controllers of both systems have a real-time clock, which can be read or set.
Chapter 3 Conversion of System Software and Standard Functions Handling of Interrupts Interrupts can be enabled and disabled by the user program making calls to system functions. S7 Comment Logix SFC39 DIS_IRT Disables interrupts handled by a SSV specified OB. Interrupt requests are Inhibits specified task. lost.
Conversion of System Software and Standard Functions Status – Controller Chapter 3 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. S7 Comment Logix SFC51 RDSYSST Input parameters specify the class GSV of information to be read, and possibly an instance number if there are several objects.
Chapter 3 Conversion of System Software and Standard Functions Status – for OBs and Tasks S7 Comment Logix Comment OB Header 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.
Conversion of System Software and Standard Functions Chapter 3 Conversion Routines S7 Comment Logix Library functions Comment Instructions FC16 I_STRNG Integer to string DTOS INT can be used as a source tag instead of DINT FC5 DI_STRNG Double integer to string DTOS DINT to string FC30 R_STRG Real to string RTOS Real to String FC38 STRG_I String to Integer DTOS FC37 STRG_DI String to double integer STOD String to DINT FC39 STRG_R String to real STOR String to real Logix Commen
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.
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.
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.
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.
Chapter 3 Conversion of System Software and Standard Functions Read System Time STEP 7 Logix 78 Publication LOGIX-AP008B-EN-P - June 2008
Conversion of System Software and Standard Functions Chapter 3 Get Faults STEP 7 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.
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.
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. #OB1_PREV_CYCLE is the scan time. As a temporary variable, it ceases to exist when the execution of OB1 is complete.
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.
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.
Chapter 4 Conversion of Typical Program Structures Set and Reset STEP 7 LOGIX 84 Publication LOGIX-AP008B-EN-P - June 2008
Conversion of Typical Program Structures Chapter 4 Test for Greater Than STEP 7 LOGIX As before, use the CMP instruction if the expression is more complex than just comparing two numbers.
Chapter 4 Conversion of Typical Program Structures On Timer Delay STEP 7 LOGIX 86 Publication LOGIX-AP008B-EN-P - June 2008
Conversion of Typical Program Structures Chapter 4 Call to User Function STEP 7 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.
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. When configuring instructions, pull-down menus are available to allow you to select the tag to be entered.
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. 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.
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. This is more readable than the conventional jump sequence, and is more efficient because only the code at the target label is executed.
Chapter 4 Conversion of Typical Program Structures Logix - Ladder Logic This shows multi-way choice using LD.
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.
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.
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.
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.
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.
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. 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.
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. In both systems, UDTs can be used to declare and define variables.
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”. Notice the entry “table” of type Struct. Inside “table” can be a collection (ordered or unordered) of any combination of types.
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.
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.
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.
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.
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.
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.
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.
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.
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. Having done this, you can define instances of your new type.
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.
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. Enter the name of the Add-On Instruction and specify the language its code section will be written in.
Chapter 4 Conversion of Typical Program Structures Choose the Parameters tab. 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.
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.
Chapter 4 Conversion of Typical Program Structures The Add-On Instruction can be called from any routine. 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.
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.
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.
Conversion of Typical Program Structures Chapter 4 STEP 7 - LAD Math evaluation in LAD follows a conventional pattern of combining functions.
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.
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.
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.
Conversion of Typical Program Structures A Larger Example - Control Module Chapter 4 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.
Chapter 4 Conversion of Typical Program Structures User Data Type Valve The UDT is shown below. Building the UDT should be the first step - it includes all the data that is necessary to model the valve.
Conversion of Typical Program Structures Chapter 4 The Add-On Instruction Add-On Instruction Parameters The screen shot shows the parameter configuration screen. 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.
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.
Conversion of Typical Program Structures Chapter 4 Add-On Instruction Logic The screen shot below shows the logic for this Add-On Instruction.
Chapter 4 Conversion of Typical Program Structures 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).
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.
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.
Chapter 5 Common Mistakes when Converting to Logix Introduction 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.
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 Chapter 2 for a more detailed account of scheduling in Logix.
Common Mistakes when Converting to Logix Implementation of Incorrect Data Types – DINT versus INT Chapter 5 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 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.
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.
Common Mistakes when Converting to Logix Incorrect Usage of COP, MOV, and CPS Chapter 5 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.
Chapter 5 Common Mistakes when Converting to Logix Notes: 134 Publication LOGIX-AP008B-EN-P - June 2008
Chapter 6 S7 to Logix Glossary This chapter provides a glossary of S7 terms and their Logix equivalents.
Chapter 6 S7 to Logix Glossary Software Terminology S7 Term Definition Nearest Logix Term Definition Accumulator Used in STL N/A In Logix languages, there is no need to access low-level structures of the CPU AR1, AR2 Pointer registers N/A In Logix languages, there is no need to access low-level structures of the CPU Array Syntax ARRAY[0…7] OF REAL Array Syntax REAL[8] Indexing always starts at 0 Bit Memory Addresses M... N/A Use tags Block Transfer Copy block of data.
S7 to Logix Glossary Chapter 6 S7 Term Definition Nearest Logix Term Definition NetPro Network Configurator N/A Part of I/O Configuration branch of controller organiser.
Chapter 6 S7 to Logix Glossary Notes: 138 Publication LOGIX-AP008B-EN-P - June 2008
Appendix A S7 300 and S7 400 Parts and RA Equivalents Introduction Publication LOGIX-AP008B-EN-P - June 2008 This appendix lists Siemens products and their Rockwell Automation equivalents.
Appendix A S7 300 and S7 400 Parts and RA Equivalents Compact S7 300 CPUs Siemens Catalogue Number Siemens Memory Short Reference Comms Ports Max MMC Size MPI DP Serial 32K Y N N 6ES7 S7-313C 313-5BF0x-xxxx 64K Yes No No Y N 6ES7 S7-313C313-6BF0x-xxxx PtP 64K Y 6ES7 S7-313C313-6CF0x-xxxx DP 64 K 6ES7 314-6BG0x-xxx x S7-314CPtP 6ES7 314-6CG0x-xxx x S7-314CDP 6ES7 312-5BE0x-xxxx S7-312C Embedded I/O RA Solution DI DO AI AO 4 MB 10 6 N 8 MB 24 16 N RS422/ 485 8 MB 16
S7 300 and S7 400 Parts and RA Equivalents Siemens Siemens Short Memory Reference Comms Ports Catalogue Number MPI DP PN Appendix A Max Load Memory Size (RAM) RA Solution 6ES7 315-2EH1x-xxxx S7-315-2 PN/DP 256K Y Y Y 8 MB 1769-L3xE or 1769-L3xC 6ES7 317-2AJ1x-xxxx S7-317-2 DP 512K Y Y N 8 MB 1769-L3xE or 1769-L3xC 6ES7 317-2EK1x-xxxx S7-317-2 PN/DP 1 MB Y Y Y 8 MB 1769-L3xE or 1769-L3xC 6ES7 319-3ELOx-xxxx S7-319-3 PN/DP 1.
Appendix A S7 300 and S7 400 Parts and RA Equivalents Fail-Safe S7 300 CPUs Siemens Siemens Short Memory Reference Comms Ports Catalogue Number MPI DP PN Max Load Memory Size (RAM) RA Solution ControlLogix 6ES7 315-6FF1x-xxxx S7-315F-2 DP 192K Y Y N 8 MB GuardLogix or SmartGuard 600 6ES7 315-2FH1x-xxxx S7-315F-2 PN/DP 256K Y Y Y 8 MB GuardLogix or SmartGuard 600 6ES7 317-6FF0x-xxxx S7-317F-2 DP 1 MB Y Y N 8 MB GuardLogix or SmartGuard 600 6ES7 317-2FK1x-xxxx S7-317F-2 PN/D
S7 300 and S7 400 Parts and RA Equivalents 6ES7 321-1FF1x-xxxx 40-pin 8 120 ... 230 VAC 1769-IA8I 6ES7 321-1EL0x-xxxx 40-pin 32 120 VAC n/a 16 5 VDC TTL 1769-IG16 n/a Appendix A 1769-IA8I only admits 120 VAC S7 300 Digital Output Modules Siemens Catalogue Number Front Connector Points Range Output Current RA Solution 6ES7 332-1FH0x-xxxx 20-pin 16 120/230 VAC 0.
Appendix A S7 300 and S7 400 Parts and RA Equivalents S7 300 Relay Output Modules Siemens Catalogue Number Front Connector Points Output Current RA Solution Comments 6ES7 322-1HH0x-xxxx 20-pin 16 2A 1769-OW16 6ES7 322-1HF0x-xxxx 20-pin 8 5A 1769-OW8 6ES7 322-1HF1x-xxxx 40-pin 8 5A 1769-OW8I 6ES7 322-5HF0x-xxxx 40-pin 8 8A 1769-OW8I S7-300 module comes with RC filter and overvoltage protecction S7 300 Digital Combo Modules Siemens Catalogue Number Front Connector Points Range
S7 300 and S7 400 Parts and RA Equivalents 6ES7 331-7KB0x-xxxx 20 2 9 / 12 / 14 Voltage, C,urrent, Resistance Temperature 1769sc-IF8U 1769-IF4 6ES7 331-7NF0x-xxxx 40 8 16 Voltage Voltage 1769-IF8 6ES7 331-7NF1x-xxxx 40 8 16 Voltage Voltage 1769-IF8 6ES7 331-7HF0x-xxxx 20 8 14 Voltage Voltage 1769-IF8 6ES7 331-7PF0x-xxxx 40 8 RTD Resistance 1769-IR6 6ES7 331-7PF1x-xxxx 40 8 Thermocouple 1769-IT6 n/a Appendix A Includes hardware interrupt at end of cycle vs 6ES7 331-7NF0x-
Appendix A S7 300 and S7 400 Parts and RA Equivalents S7 300 Analog Combo Modules Siemens Catalogue Number Front Connector Points Resolution (bits) Type RA Solution 6ES7 334-0KE0x-xxxx 20 4/2 12 Voltage Current Pt 100 6ES7 334-0CE0x-xxxx 20 4/2 8 Voltage and Current (Inputs & Outputs) Comments Outputs only Voltage 1769-IF4XOF2 S7 400 Standard Controllers Siemens Catalogue Number Siemens Short Work Reference Memory Size Comms Ports MPI DP PN Max Load Memory Size (RAM) RA Solution C
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 Comms Ports MPI DP PN Sync ports Max Load Memory Size (RAM) RA Solution ControlLogix 6ES7 414-4HJ04-0AB0 CPU 414-4H 1.4MB Y Y N Y 64MB 1756-L63 6ES7 417-4HL04-0AB0 CPU 417-4H 20MB Y Y N Y 64MB 1756-L64 6ES7 416-2FK04-0AB0 CPU-416F-2 2.
Appendix A S7 300 and S7 400 Parts and RA Equivalents Analog Input Modules Siemens Catalogue Number Front Connector Channels Resolution (bits) Type RA Solution Comments 6ES7 431-0HH0-0AB0 48 pin 16 13 Voltage Current 1756-IF16 16 bits 6ES7 431-1KF00-0AB0 48 pin 8 13 Voltage Current Impedance 1756-IF8 16 bits 4 differential inputs 6ES7 431-1KF10-0AB0 48 pin 8 14-16 Voltage Current Thermocouple Thermoresistor Impedance 1756-IR6I 1756-IT6I 6 RTD 6 Thermocouple Both 16 bit 6ES7 431-
Appendix Siemens HMI Cross Reference Table Use this appendix to compare Rockwell Automation panels to specific types of Siemens panels.
Appendix B Siemens HMI Cross Reference Table SIMATIC Micro Panels Rockwell Automation Solution Siemens Catalog Number Short Reference Description Mem. Comm. Options Rockwell Automation Catalog Number Name Description 6AV66400CA01-0AX0 SIMATIC TP 170MICRO 5.7 in. STN display, Blue mode (4 levels), 320x240 pixels, touch, 24V DC only, limited application functionality 256 KB 1xRS485, S7-200 compatible, no printer port 2711PT6M5D PanelView Plus 600 grayscale touch 5.5 in.
Siemens HMI Cross Reference Table Appendix B SIMATIC Panels - 7x Series and Rockwell Automation Equivalents SIMATIC Panels - 7x Series Rockwell Automation Solution Siemens Catalog Number Short Reference Description Mem. Comm. Options Rockwell Automation Catalog Number Name Description 6AV66410AA11-0AX0 SIMATIC OP73 3 in.
Appendix B Siemens HMI Cross Reference Table SIMATIC Panels - 17x Series and Rockwell Automation Equivalents SIMATIC Panels - 17x Series Rockwell Automation Solution Siemens Catalog Number Short Reference Description Mem. Comm. Options Rockwell Automation Catalog Number Name Description 6AV65450BA15-2AX0 SIMATIC TP170A Blue mode 5.7 in.
Siemens HMI Cross Reference Table SIMATIC Panels - 17x Series Appendix B Rockwell Automation Solution Siemens Catalog Number Short Reference Description Mem. Comm. Options Rockwell Automation Catalog Number 6AV66420AA11-0AX0 SIMATIC TP177A Blue mode 5.7 in. STN display, Blue mode (4 levels), 320x240 pixels, touch, 24V DC only 512 KB 1xRS422, 1xRS485, S7-200, S7-300/400 compatible, no printer port 2711P-T6M20 PanelView D Plus 600 Grayscale Touch 5.
Appendix B Siemens HMI Cross Reference Table SIMATIC Panels - 17x Series Rockwell Automation Solution Siemens Catalog Number Short Reference Description Mem. Comm. Options Rockwell Automation Catalog Number Name Description 6AV66428BA10-0AA0 SIMATIC TP177B color stainless steel 5.7 in.
Siemens HMI Cross Reference Table Appendix B SIMATIC Panels - 27x Series and Rockwell Automation Equivalents SIMATIC Panels - 27x Series Rockwell Automation solution Siemens Catalog Number Short Reference Description Mem. Comm. Options Rockwell Automation Catalog Number Name Description 6AV65450CA10-0AX0 SIMATIC TP270 6 in. color 5.7 in.
Appendix B Siemens HMI Cross Reference Table SIMATIC Panels - 27x Series Siemens Catalog Number Short Reference 6AV66430AA01-1AX0 Rockwell Automation solution Mem. Comm. Options Rockwell Automation Catalog Number Name Description SIMATIC TP 5.7 in. STN 277 6 in. color display, color (256 colors), 320x240 pixels, touch, 24V DC only 4 MB 1xRS422, 1xRS485, USB, Ethernet: S5, S7-200, S7-300/400, and third-party controllers, printer port available 2711PT6C20D PanelView Plus 600 color touch 5.5 in.
Siemens HMI Cross Reference Table Appendix B SIMATIC Multi Panels - 27x Series and Rockwell Automation Equivalents SIMATIC Multi Panels - 27x Series Rockwell Automation Solution Siemens Catalog Number Short Reference Description Mem. Comm. Options Rockwell Automation Catalog Number Name Description 6AV65420AG10-0AX0 SIMATIC MP270B keypad 10 in. 10.4 in.
Appendix B Siemens HMI Cross Reference Table SIMATIC Multi Panels - 27x Series Rockwell Automation Solution Siemens Catalog Number Short Reference Description Mem. Comm. Options Rockwell Automation Catalog Number Name Description 6AV66430CD01-1AX0 SIMATIC MP 277 touch, 10 in. 10.4 in.
Siemens HMI Cross Reference Table Appendix B SIMATIC Multi Panels - 37x Series and Rockwell Automation Equivalents SIMATIC Multi Panels - 37x Series Rockwell Automation Solution Siemens Catalog Number Short Reference Description Mem. 6AV65420DA10-0AX0 SIMATIC MP370 keypad, 12 in. 12.1 in. TFT display, color (256 colors), 800x600 pixels, keypad, 24V DC only 6AV65450DA10-0AX0 SIMATIC MP370 touch, 12 in.
Appendix B Siemens HMI Cross Reference Table SIMATIC Multi Panels - 37x Series Rockwell Automation Solution Rockwell Automation Catalog Number Name Description 12.5 MB 1xTTY, 2xRS232, 1xRS422, 1xRS485, 2xUSB, 2xEthernet, S5, S7-200, S7-300/400, and third-party controllers, printer port 2711PT12C4D1 PanelView Plus 1250 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 12.1 in.
Siemens HMI Cross Reference Table Appendix B Notes: Publication LOGIX-AP008B-EN-P - June 2008 161
Appendix B 162 Siemens HMI Cross Reference Table 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.
