advertisement
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
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