SIMATIC S7-1200 Manual PDF

Easy Book ___________________
Preface
Introducing the powerful and

___________________
flexible S7-1200 1
STEP 7 makes the work
___________________
easy 2
SIMATIC
___________________
Getting started 3
S7-1200
Easy Book ___________________
PLC concepts made easy 4
___________________
Easy to create the device
configuration 5
Manual
___________________
Programming made easy 6
___________________
Easy to communicate
between devices 7
___________________
PID is easy 8
___________________
Web server for easy Internet
connectivity 9
___________________
Motion control is easy 10
___________________
Easy to use the online tools 11
___________________
Technical specifications A
04/2012
A5E02486774-05
Legal information
Legal information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are
graded according to the degree of danger.
DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.
CAUTION
with a safety alert symbol, indicates that minor personal injury can result if proper precautions are not taken.
CAUTION
without a safety alert symbol, indicates that property damage can result if proper precautions are not taken.
NOTICE
indicates that an unintended result or situation can occur if the relevant information is not taken into account.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will
be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to
property damage.
Qualified Personnel
The product/system described in this documentation may be operated only by personnel qualified for the specific
task in accordance with the relevant documentation, in particular its warning notices and safety instructions.
Qualified personnel are those who, based on their training and experience, are capable of identifying risks and
avoiding potential hazards when working with these products/systems.
Proper use of Siemens products
Note the following:
WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended
or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and
maintenance are required to ensure that the products operate safely and without any problems. The permissible
ambient conditions must be complied with. The information in the relevant documentation must be observed.
Trademarks
All names identified by are registered trademarks of Siemens AG. The remaining trademarks in this publication
may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software
described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the
information in this publication is reviewed regularly and any necessary corrections are included in subsequent
editions.
Siemens AG Order number: 6ES7298-8FA30-8BQ0 Copyright Siemens AG 2012.

Industry Sector 05/2012 Technical data subject to change All rights reserved
Postfach 48 48
90026 NRNBERG
GERMANY
Preface
Welcome to the world of S7-1200, the latest in a line of the Siemens SIMATIC controllers.
The SIMATIC S7-1200 compact controller is the modular, space-saving controller for small
automation systems that require either simple or advanced functionality for logic, HMI and
networking. The compact design, low cost, and powerful features make the S7-1200 a
perfect solution for controlling small applications.
As part of the SIMATIC commitment to "totally integrated automation" (TIA), the S7-1200
product family and the STEP 7 programming tool give you the flexibility you need to solve
your automation needs.
The S7-1200 helps to make the most challenging tasks easy!
The SIMATIC S7-1200 controller solution, designed for the "compact" controller class, is
comprised of the SIMATIC S7-1200 controller and SIMATIC HMI Basic panels that can both
be programmed with SIMATIC STEP 7 engineering software. The ability to program both
devices using the same engineering software significantly reduces development costs.
The S7-1200 compact controller includes:

Built-in PROFINET
High-speed I/O capable of motion control, onboard
analog inputs to minimize space requirements and
the need for additional I/O, 2 pulse generators for
pulse-train and pulse-width applications (Page 66) ,
and up to 6 high-speed counters (Page 113)
On-board I/O points built into the CPU modules
provide from 6 to 14 input points and from 4 to 10
output points.
Signal modules for DC, relay, or analog I/O
expand the number of I/O points, and
innovative signal boards snap onto the front
of the CPU to provide additional I/O
(Page 16).
The SIMATIC HMI Basic panels (Page 19)
were designed specifically for the S7-1200.
This Easy Book provides an introduction to
the S7-1200 PLC. The following pages offer
an overview of the many features and
capabilities of the devices.
For additional information, refer to the S7-1200 programmable controller system manual. For
information about UL and FM certification, CE labeling, C-Tick and other standards, refer to
the Technical specifications (Page 239).
Easy Book
Manual, 04/2012, A5E02486774-05 3
Preface
This manual describes the following products:

STEP 7 V11 Basic and Professional
S7-1200 CPU firmware release V3.0
Documentation and information

S7-1200 and STEP 7 provide a variety of documentation and other resources for finding the
technical information that you require.
The S7-1200 system manual provides specific information about the operation,
programming and the specifications for the complete S7-1200 product family. In addition
to the system manual, the S7-1200 Easy Book provides a more general overview to the
capabilities of the S7-1200 family.
Both the system manual and the Easy Book are available as electronic (PDF) and printed
manuals. The electronic manuals can be downloaded from the customer support web site
and can also be found on the companion disk that ships with every S7-1200 CPU.
The online information system of STEP 7 provides immediate access to the conceptual
information and specific instructions that describe the operation and functionality of the
programming package and basic operation of SIMATIC CPUs.
My Documentation Manager accesses the electronic (PDF) versions of the SIMATIC
documentation set, including the system manual, the Easy Book and the information
system of STEP 7. With My Documentation Manager, you can drag and drop topics from
various documents to create your own custom manual.
The customer support entry portal (http://support.automation.siemens.com) provides a
link to My Documentation Manager under mySupport.
The customer support web site also provides podcasts, FAQs, and other helpful
documents for S7-1200 and STEP 7. The podcasts utilize short educational video
presentations that focus on specific features or scenarios in order to demonstrate the
interactions, convenience and efficiency provided by STEP 7. Visit the following web sites
to access the collection of podcasts:
STEP 7 Basic web page (http://www.automation.siemens.com/mcms/simatic-
controller-software/en/step7/step7-basic/Pages/Default.aspx)
STEP 7 Professional web page (http://www.automation.siemens.com/mcms/simatic-
controller-software/en/step7/step7-professional/Pages/Default.aspx)
You can also follow or join product discussions on the Service & Support technical forum
(https://www.automation.siemens.com/WW/forum/guests/Conferences.aspx?Language=e
n&siteid=csius&treeLang=en&groupid=4000002&extranet=standard&viewreg=WW&nodei
d0=34612486). These forums allow you to interact with various product experts.
Forum for S7-1200
(https://www.automation.siemens.com/WW/forum/guests/Conference.aspx?SortField=
LastPostDate&SortOrder=Descending&ForumID=258&Language=en&onlyInternet=Fa
lse)
Forum for STEP 7 Basic
(https://www.automation.siemens.com/WW/forum/guests/Conference.aspx?SortField=
LastPostDate&SortOrder=Descending&ForumID=265&Language=en&onlyInternet=Fa
lse)
Easy Book
4 Manual, 04/2012, A5E02486774-05
Preface
Service and support

In addition to our documentation, we offer our technical expertise on the Internet on the
customer support web site (http://www.siemens.com/automation/).
Contact your Siemens distributor or sales office for assistance in answering any technical
questions, for training, or for ordering S7 products. Because your sales representatives are
technically trained and have the most specific knowledge about your operations, process
and industry, as well as about the individual Siemens products that you are using, they can
provide the fastest and most efficient answers to any problems you might encounter.
Easy Book
Manual, 04/2012, A5E02486774-05 5
Preface
Easy Book
6 Manual, 04/2012, A5E02486774-05
Table of contents
Preface ...................................................................................................................................................... 3
1 Introducing the powerful and flexible S7-1200 ......................................................................................... 13
1.1 Introducing the S7-1200 PLC.......................................................................................................13
1.2 Expansion capability of the CPU..................................................................................................16
1.3 S7-1200 modules.........................................................................................................................18
1.4 Basic HMI panels .........................................................................................................................19
1.5 Mounting dimensions and clearance requirements .....................................................................21
1.6 New features ................................................................................................................................24
2 STEP 7 makes the work easy.................................................................................................................. 25
2.1 Easy to insert instructions into your user program.......................................................................26
2.2 Easy access to your favorite instructions from a toolbar .............................................................26
2.3 Easy to add inputs or outputs to LAD and FBD instructions........................................................27
2.4 Expandable instructions...............................................................................................................27
2.5 Easy to change the operating mode of the CPU .........................................................................28
2.6 Easy to modify the appearance and configuration of STEP 7 .....................................................29
2.7 Project and global libraries for easy access ................................................................................29
2.8 Easy to select a version of an instruction ....................................................................................30
2.9 Easy to drag and drop between editors .......................................................................................30
2.10 Changing the call type for a DB ...................................................................................................31
2.11 Temporarily disconnecting devices from a network.....................................................................32
2.12 Easy to virtually "unplug" modules without losing the configuration ............................................33
3 Getting started ......................................................................................................................................... 35
3.1 Create a project............................................................................................................................35
3.2 Create tags for the I/O of the CPU...............................................................................................36
3.3 Create a simple network in your user program............................................................................37
3.4 Use the PLC tags in the tag table for addressing the instructions...............................................39
3.5 Add a "box" instruction.................................................................................................................40
3.6 Use the CALCULATE instruction for a complex mathematical equation.....................................41
3.7 Add an HMI device to the project.................................................................................................43
3.8 Create a network connection between the CPU and HMI device................................................44
3.9 Create an HMI connection to share tags .....................................................................................44
Easy Book
Manual, 04/2012, A5E02486774-05 7
Table of contents
3.10 Create an HMI screen ................................................................................................................. 45

3.11 Select a PLC tag for the HMI element ........................................................................................ 46
4 PLC concepts made easy ........................................................................................................................ 47
4.1 Tasks performed every scan cycle ............................................................................................. 47
4.2 Operating modes of the CPU ...................................................................................................... 48
4.3 Execution of the user program .................................................................................................... 50
4.3.1 Processing the scan cycle in RUN mode.................................................................................... 50
4.3.2 OBs help you structure your user program ................................................................................. 51
4.3.3 Event execution priorities and queuing ....................................................................................... 52
4.4 Memory areas, addressing and data types................................................................................. 57
4.4.1 Data types supported by the S7-1200 ........................................................................................ 58
4.4.2 Addressing memory areas .......................................................................................................... 60
4.4.3 Accessing a "slice" of a tagged data type ................................................................................... 62
4.4.4 Accessing a tag with an AT overlay ............................................................................................ 63
4.5 Pulse outputs .............................................................................................................................. 66
5 Easy to create the device configuration ................................................................................................... 69
5.1 Detecting the configuration for an unspecified CPU ................................................................... 70
5.2 Adding a CPU to the configuration.............................................................................................. 71
5.3 Adding modules to the configuration........................................................................................... 72
5.4 Configuring the operation of the CPU and modules ................................................................... 73
5.4.1 System memory and clock memory provide standard functionality............................................ 75
5.5 Configuring the IP address of the CPU....................................................................................... 77
5.6 Protecting access to the CPU or code block is easy .................................................................. 79
5.6.1 Know-how protection................................................................................................................... 80
5.6.2 Copy protection ........................................................................................................................... 81
6 Programming made easy......................................................................................................................... 83
6.1 Easy to design your user program .............................................................................................. 83
6.1.1 Use OBs for organizing your user program ................................................................................ 85
6.1.2 FBs and FCs make programming the modular tasks easy......................................................... 86
6.1.3 Data blocks provide easy storage for program data ................................................................... 87
6.1.4 Creating a new code block.......................................................................................................... 88
6.1.5 Calling a code block from another code block ............................................................................ 88
6.2 Easy-to-use programming languages ......................................................................................... 89
6.2.1 Ladder logic (LAD) ...................................................................................................................... 89
6.2.2 Function Block Diagram (FBD) ................................................................................................... 90
6.2.3 SCL overview .............................................................................................................................. 90
6.2.4 SCL program editor..................................................................................................................... 91
6.3 Powerful instructions make programming easy .......................................................................... 93
6.3.1 Providing the basic instructions you expect ................................................................................ 93
6.3.2 Compare and Move instructions ................................................................................................. 95
6.3.3 Conversion instructions............................................................................................................... 96
6.3.4 Math made easy with the Calculate instruction........................................................................... 98
6.3.5 Timers ......................................................................................................................................... 99
Easy Book
8 Manual, 04/2012, A5E02486774-05
Table of contents
6.3.6 Counters.....................................................................................................................................103
6.3.7 Pulse-width modulation (PWM)..................................................................................................105
6.4 Easy to create data logs ............................................................................................................106
6.5 Easy to monitor and test your user program..............................................................................108
6.5.1 Watch tables and force tables....................................................................................................108
6.5.2 Cross reference to show usage .................................................................................................109
6.5.3 Call structure to examine the calling hierarchy ..........................................................................109
6.5.4 Diagnostic instructions to monitor the hardware........................................................................110
6.5.4.1 Reading the states of the LEDs on the CPU .............................................................................110
6.5.4.2 Instructions for reading the diagnostic status of the devices .....................................................111
6.6 High-speed counter (HSC).........................................................................................................111
6.6.1 Operation of the HSC.................................................................................................................113
6.6.2 Configuration of the HSC ...........................................................................................................116
7 Easy to communicate between devices ................................................................................................. 119
7.1 Creating a network connection ..................................................................................................120
7.2 Communication options .............................................................................................................121
7.3 Number of asynchronous communication connections .............................................................122
7.4 PROFINET and PROFIBUS instructions ...................................................................................123
7.5 PROFINET .................................................................................................................................124
7.5.1 Open user communication .........................................................................................................124
7.5.1.1 Ad hoc mode ..............................................................................................................................125
7.5.1.2 Connection IDs for the PROFINET instructions.........................................................................126
7.5.1.3 Parameters for the PROFINET connection ...............................................................................128
7.5.2 Configuring the Local/Partner connection path..........................................................................131
7.6 PROFIBUS.................................................................................................................................133
7.6.1 Configuration examples for PROFIBUS ....................................................................................135
7.6.2 Adding the CM 1243-5 (DP master) module and a DP slave ....................................................138
7.6.3 Assigning PROFIBUS addresses to the CM 1243-5 module and DP slave..............................139
7.7 AS-i ............................................................................................................................................141
7.7.1 Adding the AS-i master CM 1243-2 and AS-i slave...................................................................141
7.7.2 Assigning an AS-i address to an AS-i slave ..............................................................................142
7.8 S7 communication .....................................................................................................................143
7.8.1 GET and PUT instructions .........................................................................................................143
7.8.2 Creating an S7 connection.........................................................................................................144
7.8.3 GET/PUT connection parameter assignment ............................................................................144
7.9 GPRS .........................................................................................................................................145
7.9.1 Connection to a GSM network ...................................................................................................145
7.10 PtP, USS, and Modbus communication protocols .....................................................................153
7.10.1 Using the serial communication interfaces ................................................................................153
7.10.2 PtP instructions ..........................................................................................................................154
7.10.3 USS instructions ........................................................................................................................155
7.10.4 Modbus instructions ...................................................................................................................156
Easy Book
Manual, 04/2012, A5E02486774-05 9
Table of contents
8 PID is easy ............................................................................................................................................ 159

8.1 Inserting the PID instruction and technological object .............................................................. 161
8.2 PID_Compact instruction........................................................................................................... 163
8.3 PID_Compact instruction ErrorBit parameters .......................................................................... 168
8.4 PID_3STEP instruction.............................................................................................................. 169
8.5 PID_3STEP instruction ErrorBit parameters ............................................................................. 175
8.6 Configuring the PID controller ................................................................................................... 177
8.7 Commissioning the PID controller............................................................................................. 179
9 Web server for easy Internet connectivity .............................................................................................. 181
9.1 Easy to use the standard Web pages ....................................................................................... 181
9.2 Constraints that can affect the use of the Web server.............................................................. 183
9.2.1 Constraints when JavaScript is disabled .................................................................................. 184
9.2.2 Features restricted when cookies are not allowed.................................................................... 185
9.3 Easy to create user-defined web pages.................................................................................... 185
9.3.1 Easy to create custom "user-defined" web pages .................................................................... 185
9.3.2 Constraints specific to user-defined Web pages ...................................................................... 187
9.3.3 Configuration of a user-defined Web page ............................................................................... 188
9.3.4 Using the WWW instruction ...................................................................................................... 189
10 Motion control is easy ............................................................................................................................ 191
10.1 Configuring the axis .................................................................................................................. 194
10.2 Configuring the TO_CommandTable_PTO ............................................................................... 197
10.3 MC_Power instruction ............................................................................................................... 200
10.4 MC_Reset instruction ................................................................................................................ 203
10.5 MC_Home instruction................................................................................................................ 204
10.6 MC_Halt instruction ................................................................................................................... 208
10.7 MC_MoveAbsolute instruction .................................................................................................. 210
10.8 MC_MoveRelative instruction.................................................................................................... 212
10.9 MC_MoveVelocity instruction .................................................................................................... 214
10.10 MC_MoveJog instruction........................................................................................................... 216
10.11 MC_CommandTable instruction................................................................................................ 218
10.12 MC_ChangeDynamic ................................................................................................................ 221
11 Easy to use the online tools ................................................................................................................... 223
11.1 Going online and connecting to a CPU..................................................................................... 223
11.2 Interacting with the online CPU................................................................................................. 224
11.3 Going online to monitor the values in the CPU ......................................................................... 225
11.4 Displaying status of the user program is easy .......................................................................... 226
11.5 Using a watch table for monitoring the CPU ............................................................................. 226
Easy Book
10 Manual, 04/2012, A5E02486774-05
Table of contents
11.6 Using the force table ..................................................................................................................227

11.7 Capturing the online values of a DB to reset the start values....................................................230
11.8 Copying elements of the project ................................................................................................231
11.9 Comparing offline and online CPUs...........................................................................................232
11.10 Displaying the diagnostic events................................................................................................233
11.11 Setting the IP address and time of day......................................................................................233
11.12 Resetting to factory settings.......................................................................................................234
11.13 Downloading an IP address to an online CPU...........................................................................235
11.14 Using the "unspecified CPU" to upload the hardware configuration..........................................236
11.15 Downloading in RUN mode........................................................................................................237
11.15.1 Changing your program in RUN mode ......................................................................................238
A Technical specifications......................................................................................................................... 239
A.1 General Technical Specifications ..............................................................................................239
A.2 CPU modules .............................................................................................................................245
A.3 Digital I/O modules.....................................................................................................................249
A.3.1 SB 1221, SB 1222, and SB 1223 digital input/output (DI, DQ, and DI/DQ) ..............................249
A.3.2 SM 1221 digital input (DI) ..........................................................................................................251
A.3.3 SM 1222 digital output (DQ) ......................................................................................................252
A.3.4 SM 1223 VDC digital input/output (DI / DQ) ..............................................................................254
A.3.5 SM 1223 120/230 VAC input / Relay output ..............................................................................255
A.4 Specifications for the digital inputs and outputs.........................................................................256
A.4.1 24 VDC digital inputs (DI) ..........................................................................................................256
A.4.2 120/230 VAC digital AC inputs...................................................................................................257
A.4.3 Digital outputs (DQ) ...................................................................................................................258
A.5 Analog I/O modules ...................................................................................................................260
A.5.1 SB 1231 and SB 1232 analog input (AI) and output (AQ) .........................................................260
A.5.2 SM 1231 analog input (AI) .........................................................................................................261
A.5.3 SM 1232 analog output (AQ) .....................................................................................................261
A.5.4 SM 1234 analog input/output (AI/AQ)........................................................................................262
A.5.5 Wiring diagrams for SM 1231 (AI), SM 1232 (AQ), and SM 1234 (AI/AQ)................................263
A.6 BB 1297 Battery Board ..............................................................................................................263
A.7 Specifications for the analog I/O ................................................................................................264
A.7.1 Specifications for the analog inputs (CPU, SM, and SB)...........................................................264
A.7.2 Input (AI) measurement ranges for voltage and current............................................................266
A.7.3 Step response for the analog inputs (AI) ...................................................................................267
A.7.4 Sample time and update times for the analog inputs ................................................................267
A.7.5 Specifications for the analog outputs (SB and SM) ...................................................................268
A.7.6 Output (AQ) measurement ranges for voltage and current .......................................................269
A.8 RTD and Thermocouple modules ..............................................................................................270
A.8.1 SB 1231 RTD and SB 1231 TC specifications ..........................................................................270
A.8.2 SM 1231 RTD specifications......................................................................................................272
A.8.3 SM 1231 TC specifications ........................................................................................................273
A.8.4 Analog input specifications for RTD and TC (SM and SB) ........................................................274
Easy Book
Manual, 04/2012, A5E02486774-05 11
Table of contents
A.8.5 Thermocouple type ................................................................................................................... 275

A.8.6 Thermocouple filter selection and update times ....................................................................... 276
A.8.7 RTD sensor type selection table ............................................................................................... 276
A.8.8 RTD filter selection and update times ....................................................................................... 278
A.9 Communication interfaces......................................................................................................... 278
A.9.1 PROFIBUS master/slave .......................................................................................................... 278
A.9.1.1 CM 1242-5 PROFIBUS slave.................................................................................................... 278
A.9.1.2 CM 1243-5 PROFIBUS master................................................................................................. 280
A.9.2 GPRS CP .................................................................................................................................. 281
A.9.2.1 Technical specifications of the CP 1242-7................................................................................ 282
A.9.3 Teleservice (TS)........................................................................................................................ 284
A.9.4 RS485, RS232 and RS422 communication.............................................................................. 285
A.9.4.1 CB 1241 RS485 Specifications................................................................................................. 285
A.9.4.2 CM 1241 RS232........................................................................................................................ 287
A.9.4.3 CM 1241 RS422/485 Specifications ......................................................................................... 288
A.10 Companion products ................................................................................................................. 289
A.10.1 PM 1207 power module ............................................................................................................ 289
A.10.2 CSM 1277 compact switch module........................................................................................... 290
Index...................................................................................................................................................... 291
Easy Book
12 Manual, 04/2012, A5E02486774-05
Introducing the powerful and flexible S7-1200 1
1.1 Introducing the S7-1200 PLC
The S7-1200 controller provides the flexibility and power to control a wide variety of devices
in support of your automation needs. The compact design, flexible configuration, and
powerful instruction set combine to make the S7-1200 a perfect solution for controlling a
wide variety of applications.
The CPU combines a microprocessor, an integrated power supply, input and output circuits,
built-in PROFINET, high-speed motion control I/O, and on-board analog inputs in a compact
housing to create a powerful controller. After you download your program, the CPU contains
the logic required to monitor and control the devices in your application. The CPU monitors
the inputs and changes the outputs according to the logic of your user program, which can
include Boolean logic, counting, timing, complex math operations, and communications with
other intelligent devices.
The CPU provides a PROFINET port for communication over a PROFINET network.
Additional modules are available for communicating over PROFIBUS, GPRS, RS485 or
RS232 networks.
Power connector
Memory card slot under top door

Removable user wiring connectors
(behind the doors)

Status LEDs for the on-board I/O
PROFINET connector (on the bottom of
the CPU)
Several security features help protect access to both the CPU and the control program:
Every CPU provides password protection (Page 79) that allows you to configure access
to the CPU functions.
You can use "know-how protection" (Page 80) to hide the code within a specific block.
You can use copy protection (Page 81) to bind your program to a specific memory card or
CPU.
Easy Book
Manual, 04/2012, A5E02486774-05 13
Introducing the powerful and flexible S7-1200
Table 1- 1 Comparing the CPU models
Feature CPU 1211C CPU 1212C CPU 1214C CPU 1215C

Physical size (mm) 90 x 100 x 75 90 x 100 x 75 110 x 100 x 75 130 x 100 x 75
User memory Work 30 Kbytes 50 Kbytes 75 Kbytes 100 Kbytes
Load 1 Mbyte 1 Mbyte 4 Mbytes 4 Mbytes
Retentive 10 Kbytes 10 Kbytes 10 Kbytes 10 Kbytes
Local on-board Digital 6 inputs/4 outputs 8 inputs/6 outputs 14 inputs/10 outputs 14 inputs/10 outputs
I/O Analog 2 inputs 2 inputs 2 inputs 2 inputs / 2 outputs
Process image Inputs (I) 1024 bytes 1024 bytes 1024 bytes 1024 bytes
size Outputs (Q) 1024 bytes 1024 bytes 1024 bytes 1024 bytes
Bit memory (M) 4096 bytes 4096 bytes 8192 bytes 8192 bytes
Signal module (SM) expansion None 2 8 8
Signal board (SB), Battery board 1 1 1 1
(BB), or communication board (CB)
Communication module (CM) 3 3 3 3
(left-side expansion)
High-speed Total 3 built-in I/O, 5 4 built-in I/O, 6 6 6
counters with SB with SB
Single phase 3 at 100 kHz 3 at 100 kHz 3 at 100 kHz 3 at 100 kHz
SB: 2 at 30 kHz 1 at 30 kHz 3 at 30 kHz 3 at 30 kHz
SB: 2 at 30 kHz
Quadrature phase 3 at 80 kHz 3 at 80 kHz 3 at 80 kHz 3 at 80 kHz
SB: 2 at 20 kHz 1 at 20 kHz 3 at 20 kHz 3 at 20 kHz
SB: 2 at 20 kHz
Pulse outputs1 4 4 4 4
Memory card SIMATIC Memory card (optional)
Real time clock retention time 20 days, typ. / 12 day min. at 40 degrees C (maintenance-free Super Capicator)
PROFINET 1 Ethernet communication port 2 Ethernet
communication ports
Real math execution speed 2.3 s/instruction
Boolean execution speed 0.08 s/instruction
1 For CPU models with relay outputs, you must install a digital signal board (SB) to use the pulse outputs.
Each CPU provides dedicated HMI connections to support up to 3 HMI devices. The total
number of HMI is affected by the types of HMI panels in your configuration. For example,
you could have up to three SIMATIC Basic panels connected to your CPU, or you could
have up to two SIMATIC Comfort panels with one additional Basic panel.
The different CPU models provide a diversity of features and capabilities that help you create
effective solutions for your varied applications. For detailed information about a specific
CPU, see the technical specifications (Page 239).
Easy Book
14 Manual, 04/2012, A5E02486774-05
Table 1- 2 Blocks, timers and counters supported by S7-1200
Element Description
Blocks Type OB, FB, FC, DB
Size 30 Kbytes (CPU 1211C)
50 Kbytes (CPU 1212C)
64 Kbytes (CPU 1214C and CPU 1215C)
Quantity Up to 1024 blocks total (OBs + FBs + FCs + DBs)
Address range for FBs, FCs, 1 to 65535 (such as FB 1 to FB 65535)
and DBs
Nesting depth 16 from the program cycle or start up OB; 4 from the time delay
interrupt, time-of-day interrupt, cyclic interrupt, hardware interrupt,
time error interrupt, or diagnostic error interrupt OB
Monitoring Status of 2 code blocks can be monitored simultaneously
OBs Program cycle Multiple: OB 1, OB 200 to OB 65535
Startup Multiple: OB 100, OB 200 to OB 65535
Time-delay interrupts and 41 (1 per event): OB 200 to OB 65535
cyclic interrupts
Hardware interrupts (edges 50 (1 per event): OB 200 to OB 65535
and HSC)
Time error interrupts 1: OB 80
Diagnostic error interrupts 1: OB 82
Timers Type IEC
Quantity Limited only by memory size
Storage Structure in DB, 16 bytes per timer
Counters Type IEC
Quantity Limited only by memory size
Storage Structure in DB, size dependent upon count type
SInt, USInt: 3 bytes
Int, UInt: 6 bytes
DInt, UDInt: 12 bytes
1 Time-delay and cyclic interrupts use the same resources in the CPU. You can have only a total of 4 of these interrupts
(time-delay plus cyclic interrupts). You cannot have 4 time-delay interrupts and 4 cyclic interrupts.
Easy Book
Manual, 04/2012, A5E02486774-05 15
1.2 Expansion capability of the CPU

The S7-1200 family provides a variety of modules and plug-in boards for expanding the
capabilities of the CPU with additional I/O or other communication protocols. For detailed
information about a specific module, see the technical specifications (Page 239).
Communication module (CM), communcation processor (CP), or TS Adapter

CPU
Signal board (SB), communication board (CB), or Battery Board (BB)
Signal module (SM)
Table 1- 3 Digital signal modules and signal boards
Type Input only Output only Combination In/Out

digital SB 4 x 24VDC In, 4 x 24VDC Out, 2 x 24VDC In / 2 x 24VDC Out
200 kHz 200 kHz 2 x 24VDC In / 2 x 24VDC Out,
4 x 5VDC In, 4 x 5VDC Out, 200 kHz
200 kHz 200 kHz 2 x 5VDC In / 2 x 5VDC Out,
200 kHz
digital SM 8 x 24VDC In 8 x 24VDC Out 8 x 24VDC In / 8 x 24VDC Out

8 x Relay Out 8 x 24VDC In / 8 x Relay Out
8 x Relay Out 8 x 120/230VAC In / 8 x Relay Out
(Changeover)
16 x 24VDC In 16 x 24VDC Out 16 x 24VDC In / 16 x 24VDC Out

16 x Relay Out 16 x 24VDC In / 16 x Relay Out
Easy Book
16 Manual, 04/2012, A5E02486774-05
Table 1- 4 Analog signal modules and signal boards
Type Input only Output only Combination In/Out

analog SB 1 x 12 bit Analog In 1 x Analog Out -
1 x 16 bit RTD
1 x 16 bit Thermocouple
analog SM 4 x Analog In 2 x Analog Out 4 x Analog In / 2 x Analog Out

4 x Analog In x 16 bit 4 x Analog Out
8 x Analog In
Thermocouple:
4 x 16 bit TC
8 x 16 bit TC
RTD:
4 x 16 bit RTD
8 x 16 bit RTD
Table 1- 5 Communication interfaces
Module Type Description

Communication module (CM) RS232 Full-duplex
RS422/485 Full-duplex (RS422)
Half-duplex (RS485)
PROFIBUS Master DPV1
PROFIBUS Slave DPV1
AS-i Master (CM 1243-2) AS-Interface
Communication processor (CP) Modem connectivity GPRS
Communication board (CB) RS485 Half-duplex
TeleService TS Adapter IE Basic1 Connection to CPU

TS Adapter GSM GSM/GPRS
TS Adapter Modem Modem
TS Adapter ISDN ISDN
TS Adapter RS232 RS232
1 The TS Adapter allows you to connect various communication interfaces to the PROFINET port of the CPU. You install
the TS Adapter on the left side of the CPU and connect the TS Adapter modular (up to 3) onto the TS Adapter.
Table 1- 6 Other boards
Module Description
Battery board Plugs into expansion board interface on front of CPU. Provides long term
backup of realtime clock
Easy Book
Manual, 04/2012, A5E02486774-05 17
1.3 S7-1200 modules
1.3 S7-1200 modules
Table 1- 7 S7-1200 expansion modules
Type of module Description

The CPU supports one plug-in Status LEDs on
expansion board: the SB

A signal board (SB) provides Removable user
additional I/O for your CPU. wiring connector
The SB connects on the front of
the CPU.
A communication board (CB)
allows you to add another
communication port to your
CPU.
A battery board (BB) allows you
to provide long term backup of
the realtime clock.
Signal modules (SMs) add Status LEDs
additional functionality to the CPU.
SMs connect to the right side of the Bus connector
CPU.
Removable user
Digital I/O wiring connector

Analog I/O
RTD and thermocouple

Communication modules (CMs) Status LEDs

and communications processors
(CPs) add communication options Communication
to the CPU, such as for connector
PROFIBUS or RS232 / RS485
connectivity (for PtP, Modbus or
USS), or the AS-i master. A CP
provides capabilities for other types
of communication, such as to
connect the CPU over a GPRS
network.
The CPU supports up to 3 CMs
or CPs
Each CM or CP connects to the
left side of the CPU (or to the
left side of another CM or CP)
Easy Book
18 Manual, 04/2012, A5E02486774-05
1.4 Basic HMI panels

Because visualization is becoming a standard component for most machine designs, the
SIMATIC HMI Basic Panels provide touch-screen devices for basic operator control and
monitoring tasks. All panels have a protection rating for IP65 and have CE, UL, cULus, and
NEMA 4x certification.
Basic HMI Panel Description Technical data

3.6" membrane keyboard with 10 freely 250 tags
configurable tactile keys
50 process screens
Mono (STN, black/white)
200 alarms
KP 300 Basic PN 87 mm x 31 mm (3.6")
25 curves
Backlight color programmed (white,
40 KB recipe memory
green, yellow or red)
5 recipes, 20 data records, 20 entries
Resolution: 240 x 80
4" touch screen with 4 tactile keys 250 tags
Mono (STN, gray scale) 50 process screens
76.79 mm x 57.59 mm (3.8") 200 alarms
Portrait or landscape 25 curves
Resolution: 320 x 240 40 KB recipe memory
KTP 400 Basic PN
Color (TFT, 256 colors) or Mono 50 process screens
(STN, gray scales) 200 alarms
115.2 mm x 86.4 mm (5.7") 25 curves
Portrait or landscape
40 KB recipe memory
Resolution: 320 x 240
KTP 600 Basic PN
Easy Book
Manual, 04/2012, A5E02486774-05 19
Basic HMI Panel Description Technical data

Color (TFT, 256 colors) 50 process screens
211.2 mm x 158.4 mm (10.4") 200 alarms
Resolution: 640 x 480 25 curves
40 KB recipe memory
KTP 1000 Basic PN

15" touch screen 500 tags
Color (TFT, 256 colors) 50 process screens
304.1 mm x 228.1 mm (15.1") 200 alarms
Resolution: 1024 x 768 25 curves
40 KB recipe memory (integrated
flash)
TP 1500 Basic PN
Easy Book
20 Manual, 04/2012, A5E02486774-05
1.5 Mounting dimensions and clearance requirements

The S7-1200 PLC is designed to be easy to install. Whether mounted on a panel or on a
standard DIN rail, the compact size makes efficient use of space.
Each CPU, SM, CM, and CP supports mounting on either a DIN rail or on a panel. Use the
DIN rail clips on the module to secure the device on the rail. These clips also snap into an
extended position to provide screw mounting positions to mount the unit directly on a panel.
The interior dimension of the hole for the DIN clips on the device is 4.3 mm.
&38&&38&&38&
% % % %

$ $ $ $
&38&
Easy Book
Manual, 04/2012, A5E02486774-05 21
Table 1- 8 Mounting dimensions (mm)
S7-1200 Devices Width A (mm) Width B (mm) Width C (mm)

CPU CPU 1211C and CPU 1212C 90 45 --
CPU 1214C 110 55 --
CPU 1215C 130 65 (top) Bottom:
C1: 32.5
C2: 65
C3: 32.5
Signal modules Digital 8 and 16 point 45 22.5 --
Analog 2, 4, and 8 point
Thermocouple 4 and 8 point
RTD 4 point
Digital DQ 8 x Relay (Changeover) 70 22.5 --
Analog 16 point 70 35 --
RTD 8 point
Communication CM 1241 RS232, CM 1241 RS485 and CM 30 15 --
interfaces 1241 RS422/485
CM 1243-5 PROFIBUS master and
CM 1242-5 PROFIBUS slave
CM 1242-2 AS-i Master
CP 1242-7 GPRS
TS AdapterIE Basic 60 1 15 --
1 Because you must install a TS Adapter modular with the TS Adapter, the total width ("width A") is 60 mm.
Each CPU, SM, CM, and CP supports mounting on either a DIN rail or on a panel. Use the
DIN rail clips on the module to secure the device on the rail. These clips also snap into an
extended position to provide screw mounting positions to mount the unit directly on a panel.
The interior dimension of the hole for the DIN clips on the device is 4.3 mm.
A 25 mm thermal zone must be provided above and below the unit for free air circulation.
Always consider the following guidelines when planning your installation:
Separate the devices from heat, high voltage, and electrical noise.
Provide adequate clearance for cooling and wiring. A 25 mm thermal zone must be
provided above and below the unit for free air circulation.
Refer to the S7-1200 System Manual for specific requirements and guidelines for installation.
Easy Book
22 Manual, 04/2012, A5E02486774-05
PP

PP
PP

PP
Side view Vertical installation

Horizontal installation Clearance area
A 25 mm thermal zone must be provided above and below the unit for free air circulation.
WARNING
Installation or removal of S7-1200 or related equipment with the power applied could cause
electric shock or unexpected operation of equipment.
Failure to disable all power to the S7-1200 and related equipment during installation or
removal procedures could result in death, severe personal injury and/or property damage
due to electric shock or unexpected equipment operation.
Always follow appropriate safety precautions and ensure that power to the S7-1200 is
disabled before attempting to install or remove S7-1200 CPUs or related equipment.
Always ensure that whenever you replace or install an S7-1200 device you use the correct
module or equivalent device.
WARNING
Incorrect installation of an S7-1200 module may cause the program in the S7-1200 to
function unpredictably.
Failure to replace an S7-1200 device with the same model, orientation, or order could result
in death, severe personal injury and/or property damage due to unexpected equipment
operation.
Replace an S7-1200 device with the same model, and be sure to orient and position it
correctly.
Easy Book
Manual, 04/2012, A5E02486774-05 23
1.6 New features
1.6 New features

The following features are new in this release:
A standard Web server page for performing a CPU firmware update
The ability to use three PROFIBUS DP CM 1243-5 master modules or three AS-i CM
1243-2 master modules
Note
To use three AS-i modules as masters, you must update the firmware of the AS-i
modules.
New modules for the S7-1200

A variety of new modules expand the power of the S7-1200 CPU and provide the flexibility to
meet your automation needs:
New and improved CPUs:
New CPU 1215C DC/DC/DC, CPU 1215C DC/DC/Relay, and CPU 1215C
AC/DC/Relay offer 100 Kbytes of work memory, dual Ethernet, and analog outputs.
New and improved CPU 1211Cs, CPU 1212Cs, and CPU 1214Cs have faster
processing time, the possibility of 4 PTOs (the CPU 1211C requires a signal board),
increased retentive memory (10 Kbytes), and increased time-of-day hold up time (20
days).
New I/O signal module: SM 1231 AI 4 x 16 bit provides higher sample rate and increased
number of bits.
New battery board (BB 1297) offers long term backup of the realtime clock. The BB 1297
is pluggable in the signal board slot of the S7-1200 CPU (firmware 3.0 and later
versions).
To use the new modules you must use STEP 7 V11 SP2 Update 3 or later (Basic or
Professional) and you must download the hardware support package (HSP) for new modules
from the STEP 7 Options > Support Packages menu command. Follow the instructions for
adding modules to the hardware catalog for STEP 7 (TIA Portal) from the Siemens Service
and Support Site.
See also
Customer_support_entry_portal (http://support.automation.siemens.com)
Easy Book
24 Manual, 04/2012, A5E02486774-05
STEP 7 makes the work easy 2
STEP 7 provides a user-friendly environment to develop controller logic, configure HMI
visualization, and setup network communication. To help increase your productivity, STEP 7
provides two different views of the project: a task-oriented set of portals that are organized
on the functionality of the tools (Portal view), or a project-oriented view of the elements within
the project (Project view). Choose which view helps you work most efficiently. With a single
click, you can toggle between the Portal view and the Project view.
Portal view
Portals for the different tasks
Tasks for the selected portal
Selection panel for the selected
action
Changes to the Project view
Project view

Menus and toolbar

Project navigator

Work area
Task cards
Inspector window
Changes to the Portal view

Editor bar

With all of these components in one place, you have easy access to every aspect of your
project. For example, the inspector window shows the properties and information for the
object that you have selected in the work area. As you select different objects, the inspector
window displays the properties that you can configure. The inspector window includes tabs
that allow you to see diagnostic information and other messages.
By showing all of the editors that are open, the editor bar helps you work more quickly and
efficiently. To toggle between the open editors, simply click the different editor. You can also
arrange two editors to appear together, arranged either vertically or horizontally. This feature
allows you to drag and drop between editors.
Easy Book
Manual, 04/2012, A5E02486774-05 25
STEP 7 makes the work easy
2.1 Easy to insert instructions into your user program
2.1 Easy to insert instructions into your user program
STEP 7 provides task cards that contain the instructions for your
program. The instructions are grouped according to function.
To create your program, you drag instructions from the task card
onto a network.
2.2 Easy access to your favorite instructions from a toolbar
STEP 7 provides a "Favorites" toolbar to give you quick access to the instructions that you
frequently use. Simply click the icon for the instruction to insert it into your network!
(For the "Favorites" in the instruction tree, double-
click the icon.)
You can easily customize the

"Favorites" by adding new
instructions.
Simply drag and drop an
instruction to the "Favorites".
The instruction is now just a click
away!
Easy Book
26 Manual, 04/2012, A5E02486774-05
2.3 Easy to add inputs or outputs to LAD and FBD instructions
2.3 Easy to add inputs or outputs to LAD and FBD instructions
Some of the instructions allow you to create additional inputs or outputs.
To add an input or output, click the "Create" icon or right-click on an input stub for one of
the existing IN or OUT parameters and select the "Insert input" command.
To remove an input or output, right-click on the stub for one of the existing IN or OUT
parameters (when there are more than the original two inputs) and select the "Delete"
command.
2.4 Expandable instructions
Some of the more complex instructions are expandable, displaying only the key inputs and
outputs. To display the inputs and outputs, click the arrow at the bottom of the instruction.
Easy Book
Manual, 04/2012, A5E02486774-05 27
2.5 Easy to change the operating mode of the CPU
2.5 Easy to change the operating mode of the CPU

Refer to
The CPU does not have a physical switch for changing the operating mode (STOP or RUN).
Use the "Start CPU" and "Stop CPU" toolbar buttons to change the operating
mode of the CPU.
When you configure the CPU in the device configuration, you configure the start-up behavior
in the properties of the CPU (Page 73).
The "Online and diagnostics" portal also provides an operator panel for changing the
operating mode of the online CPU. To use the CPU operator panel, you must be connected
online to the CPU. The "Online tools" task card displays an operator panel that shows the
operating mode of the online CPU. The operator panel also allows you to change the
operating mode of the online CPU.
Use the button on the operator panel to change the operating mode
(STOP or RUN). The operator panel also provides an MRES button for
resetting the memory.
The color of the RUN/STOP indicator shows the current operating mode of the CPU. Yellow
indicates STOP mode, and green indicates RUN mode.
Refer to Operating Modes of the CPU in the S7-1200 System Manual for configuring the
default operating mode on power up.
Easy Book
28 Manual, 04/2012, A5E02486774-05
2.6 Easy to modify the appearance and configuration of STEP 7
2.6 Easy to modify the appearance and configuration of STEP 7
You can select a variety of settings,

such as the appearance of the
interface, language, or the folder for
saving your work.
Select the "Settings" command from
the "Options" menu to change these
settings.
2.7 Project and global libraries for easy access

The global and project libraries allow you to reuse the stored objects throughout a project or
across projects. For example, you can create block templates for use in different projects
and adapt them to the particular requirements of your automation task. You can store a
variety of objects in the libraries, such as FCs, FBs, DBs, device configuration, data types,
watch tables, process screens, and faceplates. You can also save the components of the
HMI devices in your project.
Each project has a project library for storing the objects to be

used more than once within the project. This project library is
part of the project. Opening or closing the project opens or
closes the project library, and saving the project saves any
changes in the project library.
You can create your own global library to store the objects you want to make available for
other projects to use. When you create a new global library, you save this library to a
location on your computer or network.
Easy Book
Manual, 04/2012, A5E02486774-05 29
2.8 Easy to select a version of an instruction
2.8 Easy to select a version of an instruction

The development and release cycles for certain sets of instructions (such as Modbus, PID
and motion) have created multiple released versions for these instructions. To help ensure
compatibility and migration with older projects, STEP 7 allows you to choose which version
of instruction to insert into your user program.
Click the icon on the instruction tree task card to enable the
headers and columns of the instruction tree.
To change the version of the instruction, select the

appropriate version from the drop-down list.
2.9 Easy to drag and drop between editors
To help you perform tasks quickly and easily,

STEP 7 allows you to drag and drop elements
from one editor to another. For example, you
can drag an input from the CPU to the address
of an instruction in your user program.
You must zoom in at least 200% to select the
inputs or outputs of the CPU.
Notice that the tag names are displayed not
only in the PLC tag table, but also are
displayed on the CPU.
To display two editors at one time, use the

"Split editor" menu commands or buttons in
the toolbar.
Easy Book
30 Manual, 04/2012, A5E02486774-05
2.10 Changing the call type for a DB
To toggle between the editors that have been opened, click the icons in the editor bar.
2.10 Changing the call type for a DB
STEP 7 allows you to easily create or change the

association of a DB for an instruction or an FB that is in
an FB.
You can switch the association between different DBs.
You can switch the association between a single-
instance DB and a multi-instance DB.
You can create an instance DB (if an instance DB is
missing or not available).
You can access the "Change call type" command either
by right-clicking the instruction or FB in the program
editor or by selecting the "Block call" command from the
"Options" menu.
The "Call options" dialog allows

you to select a single-instance
or multi-instance DB. You can
also select specific DBs from a
drop-down list of available DBs.
Easy Book
Manual, 04/2012, A5E02486774-05 31
2.11 Temporarily disconnecting devices from a network
2.11 Temporarily disconnecting devices from a network

You can disconnect individual network devices from the subnet. Because the configuration of
the device is not removed from the project, you can easily restore the connection to the
device.
Right-click the interface port of the network

device and select the "Disconnect from
subnet" command from the context menu.
STEP 7 reconfigures the network connections, but does not remove the disconnected device
from the project. While the network connection is deleted, the interface addresses are not
changed.
When you download the new network connections, the CPU must be set to STOP mode.
To reconnect the device, simply create a new network connection to the port of the device.
Easy Book
32 Manual, 04/2012, A5E02486774-05
2.12 Easy to virtually "unplug" modules without losing the configuration
STEP 7 provides a storage area for

"unplugged" modules. You can drag a
module from the rack to save the
configuration of that module. These
unplugged modules are saved with your
project, allowing you to reinsert the
module in the future without having to
reconfigure the parameters.
One use of this feature is for temporary
maintenance. Consider a scenario where
you might be waiting for a replacement
module and plan to temporarily use a
different module as a short-term
replacement. You could drag the
configured module from the rack to the
"Unplugged modules" and then insert the
temporary module.
Easy Book
Manual, 04/2012, A5E02486774-05 33
Easy Book
34 Manual, 04/2012, A5E02486774-05
Getting started 3
3.1 Create a project
Working with STEP 7 is easy! See how quickly you can get started with creating a project.
In the Start portal, click the

"Create new project" task.
Enter a project name and click
the "Create" button.
After creating the project, select the Devices &

Networks portal.
Click the "Add new device" task.
Select the CPU to add to the project:

1. In the "Add new device" dialog, click the
"SIMATIC PLC" button.
2. Select a CPU from the list.
3. To add the selected CPU to the project, click
the "Add" button.
Note that the "Open device view" option is
selected. Clicking "Add" with this option selected
opens the "Device configuration" of the Project
view.
The Device view displays the

CPU that you added.
Easy Book
Manual, 04/2012, A5E02486774-05 35
Getting started
3.2 Create tags for the I/O of the CPU
3.2 Create tags for the I/O of the CPU

"PLC tags" are the symbolic names for I/O and addresses. After you create a PLC tag,
STEP 7 stores the tag in a tag table. All of the editors in your project (such as the program
editor, the device editor, the visualization editor, and the watch table editor) can access the
tag table.
With the device editor open, open a tag table.

You can see the open editors displayed in the editor bar.
In the tool bar, click the "Split editor space horizontally" button.
STEP 7 displays both the tag table and the

device editor together.
Zoom the device configuration to over 200% so that the I/O points of the CPU are legible and
selectable. Drag the inputs and outputs from the CPU to the tag table:
1. Select I0.0 and drag it to the first row of the tag table.
2. Change the tag name from "I0.0" to "Start".
3. Drag I0.1 to the tag table and change the name to "Stop".
4. Drag Q0.0 (on the bottom of the CPU) to the tag table and change the name to
"Running".
Easy Book
36 Manual, 04/2012, A5E02486774-05
Getting started
3.3 Create a simple network in your user program
With the tags entered into the PLC tag table, the tags are available to your user program.

Your program code consists of instructions that the CPU executes in sequence. For this
example, use ladder logic (LAD) to create the program code. The LAD program is a
sequence of networks that resemble the rungs of a ladder.
To open the program editor, follow these steps:

1. Expand the "Program blocks" folder in the Project tree to
display the "Main [OB1]" block.
2. Double-click the "Main [OB1]" block.
The program editor opens the program block (OB1).
Easy Book
Manual, 04/2012, A5E02486774-05 37
Getting started
Use the buttons on the "Favorites" to insert contacts and coils onto the network.
1. Click the "Normally open contact"

button on the "Favorites" to add a
contact to the network.
2. For this example, add second
contact.
3. Click the "Output coil" button to
insert a coil.
The "Favorites" also provides a button for creating a branch
1. Select the left rail to select the rail

for the branch.
2. Click the "Open branch" icon to
add a branch to the rail of the
network.
3. Insert another normally open
contact to the open branch.
4. Drag the double-headed arrow to a
connection point (the green square
on the rung) between the two
contacts on the first rung.
To save the project, click the "Save project" button in the toolbar. Notice that you do not have
to finish editing the rung before saving. You can now associate the tag names with these
instructions.
Easy Book
38 Manual, 04/2012, A5E02486774-05
Getting started
3.4 Use the PLC tags in the tag table for addressing the instructions
3.4 Use the PLC tags in the tag table for addressing the instructions
Using the tag table, you can quickly enter the PLC tags for the addresses of the contacts and
coils.
1. Double-click the default address

<??.?> above the first normally
open contact.
2. Click the selector icon to the right
of the address to open the tags in
the tag table.
3. From the drop-down list, select
"Start" for the first contact.
4. For the second contact, repeat the
preceding steps and select the tag
"Stop".
5. For the coil and the latching
contact, select the tag "Running".
You can also drag the I/O addresses directly

from the CPU. Simply split the work area of the
Project view (Page 30).
You must zoom the CPU to over 200% in order
to select the I/O points.
You can drag the I/O on the CPU in the "Device
configuration" to the LAD instruction in the
program editor to create not only the address for
the instruction, but also to create an entry in the
PLC tag table.
Easy Book
Manual, 04/2012, A5E02486774-05 39
Getting started
3.5 Add a "box" instruction
3.5 Add a "box" instruction

The program editor features a generic "box" instruction. After inserting this box instruction,
you then select the type of instruction, such as an ADD instruction, from a drop-down list.
Click the generic "box" instruction in

the "Favorites" tool bar.
The generic "box" instruction supports

a variety of instructions. For this
example, create an ADD instruction:
1. Click the yellow corner of the box
instruction to display the drop-
down list of instructions.
2. Scroll down the list and select the
ADD instruction.
3. Click the yellow corner by the "?"
to select the data type for the
inputs and output.
You can now enter the tags (or

memory addresses) for the values to
use with the ADD instruction.
You can also create additional inputs for certain instructions:

1. Click one of the inputs inside the box.
2. Right-click to display the context menu and select the "Insert
input" command.
The ADD instruction now uses three inputs.
Easy Book
40 Manual, 04/2012, A5E02486774-05
Getting started
3.6 Use the CALCULATE instruction for a complex mathematical equation
3.6 Use the CALCULATE instruction for a complex mathematical

equation
The Calculate instruction lets you create a math function that operates on multiple input
parameters to produce the result, according to the equation that you define.
In the Basic instruction tree, expand the Math functions folder.
Double-click the Calculate instruction to insert the instruction
into your user program.
The unconfigured Calculate

instruction provides two input
parameters and an output
parameter.
Click the "???" and select the data types for the input and output
parameters. (The input and output parameters must all be the same
data type.)
For this example, select the "Real" data type.
Click the "Edit equation" icon to enter the equation.
Easy Book
Manual, 04/2012, A5E02486774-05 41
Getting started
3.6 Use the CALCULATE instruction for a complex mathematical equation
For this example, enter the following equation for scaling a raw analog value. (The "In" and
"Out" designations correspond to the parameters of the Calculate instruction.)
Out value = ((Out high - Out low) / (In high - In low)) * (In value - In low) + Out low
Out = ((in4 - in5) / (in2 - in3)) * (in1 - in3) + in5
Where: Out value (Out) Scaled output value
In value (in1) Analog input value
In high (in2) Upper limit for the scaled input value
In low (in3) Lower limit for the scaled input value
Out high (in4) Upper limit for the scaled output value
Out low (in5) Lower limit for the scaled ouput value
In the "Edit Calculate" box, enter the equation with the parameter names:
OUT = ((in4 - in5) / (in2 - in3)) * (in1 - in3) + in5
When you click "OK", the Calculate

instruction creates the inputs
required for the instruction.
Enter the tag names for the values

that correspond to the parameters.
Easy Book
42 Manual, 04/2012, A5E02486774-05
Getting started
3.7 Add an HMI device to the project
3.7 Add an HMI device to the project
Adding an HMI device to your project is

easy!
1. Double-click the "Add new device" icon.

2. Click the "SIMATIC HMI" button in the
Add new device" dialog.
3. Select the specific HMI device from the
list.
You can choose to run the HMI wizard
to help you configure the screens for
the HMI device.
4. Click "OK" to add the HMI device to
your project.
The HMI device is added to the project.

STEP 7 provides an HMI wizard that helps you configure
all of the screens and structure for your HMI device.
If you do not run the HMI wizard, STEP 7 creates a simple default HMI screen.
Easy Book
Manual, 04/2012, A5E02486774-05 43
Getting started
3.8 Create a network connection between the CPU and HMI device
3.8 Create a network connection between the CPU and HMI device
Creating a network is easy!

Go to "Devices and Networks" and select the
Network view to display the CPU and HMI
device.
To create a PROFINET network, drag a line
from the green box (Ethernet port) on one
device to the green box on the other device.
A network connection is created for the two
devices.
3.9 Create an HMI connection to share tags
By creating an HMI connection between the

two devices, you can easily share the tags
between the two devices.
With the network connection selected, click
the "Connections" button and select "HMI
connection" from the drop-down list.
The HMI connection turns the two devices
blue.
Select the CPU device and drag the line to
the HMI device.
The HMI connection allows you to
configure the HMI tags by selecting a list of
PLC tags.
Easy Book
44 Manual, 04/2012, A5E02486774-05
Getting started
3.10 Create an HMI screen
You can use other options for creating an HMI connection:

Dragging a PLC tag from the PLC tag table, the program editor or the device
configuration editor to the HMI screen editor automatically creates an HMI connection.
Using the HMI wizard to browse for the PLC automatically creates the HMI connection.
3.10 Create an HMI screen

Even if you do not utilize the HMI wizard, configuring an HMI screen is easy.
STEP 7 provides a standard set of

libraries for inserting basic shapes,
interactive elements, and even standard
graphics.
To add an element, simply drag and drop one of the elements onto the screen. Use the
properties for the element (in the Inspector window) to configure the appearance and
behavior of the element.
You can also create elements on your screen by dragging and dropping PLC tags either
from the Project tree or the program editor to the HMI screen. The PLC tag becomes an
element on the screen. You can then use the properties to change the parameters for this
element.
Easy Book
Manual, 04/2012, A5E02486774-05 45
Getting started
3.11 Select a PLC tag for the HMI element
3.11 Select a PLC tag for the HMI element

After you create the element on your screen, use the properties of the element to assign a
PLC tag to the element. Click the selector button by the tag field to display the PLC tags of
the CPU.
You can also drag and drop PLC tags from the Project tree to the HMI screen. Display the
PLC tags in the "Details" view of the project tree and then drag the tag to the HMI screen.
Easy Book
46 Manual, 04/2012, A5E02486774-05
PLC concepts made easy 4
4.1 Tasks performed every scan cycle
Each scan cycle includes writing the outputs, reading the inputs, executing the user program
instructions, and performing system maintenance or background processing.
The cycle is referred to as a scan cycle or scan. Under

default conditions, all digital and analog I/O points are
updated synchronously with the scan cycle using an
internal memory area called the process image. The
process image contains a snapshot of the physical inputs
and outputs on the CPU, signal board, and signal
modules.
The CPU reads the physical inputs just prior to the execution of the user program and
stores the input values in the process image input area. This ensures that these values
remain consistent throughout the execution of the user instructions.
The CPU executes the logic of the user instructions and updates the output values in the
process image output area instead of writing to the actual physical outputs.
After executing the user program, the CPU writes the resulting outputs from the process
image output area to the physical outputs.
This process provides consistent logic through the execution of the user instructions for a
given cycle and prevents the flickering of physical output points that might change state
multiple times in the process image output area.
Easy Book
Manual, 04/2012, A5E02486774-05 47
PLC concepts made easy
4.2 Operating modes of the CPU
$ % & ' )
STARTUP RUN
A Clears the input (or "I") memory Writes Q memory to the physical outputs
B Initializes the outputs with either the last Copies the state of the physical inputs to I
value or the substitute value memory
C Executes the startup OBs Executes the program cycle OBs
D Copies the state of the physical inputs to I Performs self-test diagnostics
memory
E Stores any interrupt events into the queue to Processes interrupts and communications
be processed in RUN mode during any part of the scan cycle
F Enables the writing of the output (or "Q")
memory to the physical outputs
You can change the default behavior for a module by removing it from this automatic update
of I/O. You can also immediately read and write digital and analog I/O values to the modules
when an instruction executes. Immediate reads of physical inputs do not update the process
image input area. Immediate writes to physical outputs update both the process image
output area and the physical output point.

The CPU has three modes of operation: STOP mode, STARTUP mode, and RUN mode.
Status LEDs on the front of the CPU indicate the current mode of operation.
In STOP mode, the CPU is not executing the program, and you can download a project.
In STARTUP mode, the CPU executes any startup logic (if present). Interrupt events are
not processed during the startup mode.
In RUN mode, the scan cycle is executed repeatedly. Interrupt events can occur and be
processed at any point within the program cycle phase. Some parts of a project can be
downloaded in RUN mode.
The CPU supports the warm restart method for entering the RUN mode. Warm restart does
not include a memory reset, but a memory reset can be commanded from the programming
software. A memory reset clears all work memory, clears retentive and non-retentive
memory areas, and copies load memory to work memory. A memory reset does not clear the
diagnostics buffer or the permanently saved IP address. All non-retentive system and user
data are initialized at warm restart.
Easy Book
48 Manual, 04/2012, A5E02486774-05
You can configure the "startup after POWER ON" setting of the CPU complete with restart
method using the programming software. This configuration item appears under the Device
Configuration for the CPU under Startup. When power is applied, the CPU performs a
sequence of power-up diagnostic checks and system initialization. During system
initialization, the CPU deletes all non-retentive bit memory and resets all non-retentive DB
contents to initial values. The CPU then enters the appropriate power-up mode. Certain
detected errors will prevent the CPU from entering the RUN mode. The CPU supports the
following power-up modes: STOP mode, "Go to RUN mode after warm restart", and "Go to
previous mode after warm restart".
CAUTION
The CPU can enter STOP mode due to repairable faults, such as failure of a replaceable
signal module, or temporary faults, such as power line disturbance or erratic power up
event.
If the CPU has been configured to "Warm restart mode prior to POWER OFF", it will not
return to RUN mode when the fault is repaired or removed until it receives a new command
from STEP 7 to go to RUN. Without a new command, the STOP mode is retained as the
mode prior to POWER OFF.
CPUs that are intended to operate independently of a STEP 7 connection should typically
be configured to "Warm restart - RUN" so that the CPU can be returned to RUN mode by a
power cycle following the removal of fault conditions.
The CPU does not provide a physical switch for changing the
operating mode. To change the operating mode of the CPU, STEP 7
provides the following tools:
"Stop" and "Run" buttons on the STEP 7 toolbar
CPU operator panel in the online tools
You can also include a STP instruction in your program to change the CPU to STOP mode.
This allows you to stop the execution of your program based on the program logic.
Easy Book
Manual, 04/2012, A5E02486774-05 49
4.3 Execution of the user program

The CPU supports the following types of code blocks that allow you to create an efficient
structure for your user program:
Organization blocks (OBs) define the structure of the program. Some OBs have
predefined behavior and start events, but you can also create OBs with custom start
events (Page 52).
Functions (FCs) and function blocks (FBs) contain the program code that corresponds to
specific tasks or combinations of parameters. Each FC or FB provides a set of input and
output parameters for sharing data with the calling block. An FB also uses an associated
data block (called an instance DB) to maintain state of values between execution that can
be used by other blocks in the program. Valid FC and FB numbers range from 1 to
65535.
Data blocks (DBs) store data that can be used by the program blocks. Valid DB numbers
range from 1 to 65535.
The size of the user program, data, and configuration is limited by the available load memory
and work memory in the CPU (Page 13). There is no specific limit to the number of each
individual OB, FC, FB and DB block. However, the total number of blocks is limited to 1024.
4.3.1 Processing the scan cycle in RUN mode

For each scan cycle, the CPU writes the outputs, reads the inputs, executes the user
program, updates communication modules, and responds to user interrupt events and
communication requests. Communication requests are handled periodically throughout the
scan.
These actions (except for user interrupt events) are serviced regularly and in sequential
order. User interrupt events which are enabled are serviced according to priority in the order
in which they occur.
The system guarantees that the scan cycle will be completed in a time period called the
maximum cycle time; otherwise a time error event is generated.
Each scan cycle begins by retrieving the current values of the digital and analog outputs
from the process image and then writing them to the physical outputs of the CPU, SB,
and SM modules configured for automatic I/O update (default configuration). When a
physical output is accessed by an instruction, both the output process image and the
physical output itself are updated.
The scan cycle continues by reading the current values of the digital and analog inputs
from the CPU, SB, and SMs configured for automatic I/O update (default configuration),
and then writing these values to the process image. When a physical input is accessed
by an instruction, the value of the physical input is accessed by the instruction, but the
input process image is not updated.
After reading the inputs, the user program is executed from the first instruction through
the end instruction. This includes all the program cycle OBs plus all their associated FCs
and FBs. The program cycle OBs are executed in order according to the OB number with
the lowest OB number executing first.
Easy Book
50 Manual, 04/2012, A5E02486774-05
Communications processing occurs periodically throughout the scan, possibly interrupting

user program execution.
Self-diagnostic checks include periodic checks of the system and the I/O module status
checks.
Interrupts can occur during any part of the scan cycle, and are event-driven. When an event
occurs, the CPU interrupts the scan cycle and calls the OB that was configured to process
that event. After the OB finishes processing the event, the CPU resumes execution of the
user program at the point of interruption.
4.3.2 OBs help you structure your user program

OBs control the execution of the user program. Each OB must have a unique OB number.
The default OB numbers are reserved below 200. Other OBs must be numbered 200 or
greater.
Specific events in the CPU trigger the execution of an organization block. OBs cannot call
each other or be called from an FC or FB. Only a start event, such as a diagnostic interrupt
or a time interval, can start the execution of an OB. The CPU handles OBs according to their
respective priority classes, with higher priority OBs executed before lower priority OBs. The
lowest priority class is 1 (for the main program cycle), and the highest priority class is 26 (for
the time-error interrupts).
OBs control the following operations:
Program cycle OBs execute cyclically while the CPU is in RUN mode. The main block of
the program is a program cycle OB. This is where you place the instructions that control
your program and where you call additional user blocks. Multiple program cycle OBs are
allowed and are executed in numerical order. OB 1 is the default. Other program cycle
OBs must be identified as OB 200 or greater.
Startup OBs execute one time when the operating mode of the CPU changes from STOP
to RUN, including powering up in the RUN mode and in commanded STOP-to-RUN
transitions. After completion, the main "Program cycle" OB will begin executing. Multiple
startup OBs are allowed. OB 100 is the default. Others must be OB 200 or greater.
Cyclic interrupt OBs execute at a specified interval. A cyclic interrupt OB will interrupt
cyclic program execution at user defined intervals, such as every 2 seconds. You can
configure up to a total of 4 for both the time-delay and cyclic events at any given time,
with one OB allowed for each configured time-delay and cyclic event. The OB must be
OB 200 or greater.
Hardware interrupt OBs execute when the relevant hardware event occurs, including
rising and falling edges on built-in digital inputs and HSC events. A hardware interrupt OB
will interrupt normal cyclic program execution in reaction to a signal from a hardware
event. You define the events in the properties of the hardware configuration. One OB is
allowed for each configured hardware event. The OB must be OB 200 or greater.
Easy Book
Manual, 04/2012, A5E02486774-05 51
A time error interrupt OB executes when either the maximum cycle time is exceeded or a
time error event occurs. The OB for processing the time error interrupt is OB 80. If
triggered, it executes, interrupting normal cyclic program execution or any other event
OB. The events that trigger the time error interrupt and the reaction of the CPU to those
events are described below:
Exceeding the maximum cycle time: You configure the maximum cycle time in the
properties of the CPU. If OB 80 does not exist, the reaction of the CPU for exceeding
the maximum time is to change to STOP.
Time errors: If OB 80 does not exist, the reaction of the CPU is to stay in RUN. Time
errors occur if the time of day event is missed or repeated, the queue overflows, or an
event OB (time delay event, time of day event, or cyclic interrupt) starts before the
CPU finishes the execution of the first.
The occurrence of either of these events generates a diagnostic buffer entry describing
the event. The diagnostic buffer entry is generated regardless of the existence of OB 80.
Diagnostic error interrupt OBs execute when a diagnostic error is detected and reported.
A diagnostic OB interrupts the normal cyclic program execution if a diagnostics-capable
module recognizes an error (if the diagnostic error interrupt has been enabled for the
module). OB 82 is the only OB number supported for the diagnostic error event. You can
include an STP instruction (put CPU in STOP mode) inside your OB 82 if you desire your
CPU to enter STOP mode upon receiving this type of error. If there is no diagnostic OB in
the program, the CPU ignores the error (stays in RUN).
4.3.3 Event execution priorities and queuing

The CPU processing is controlled by events. An event triggers an interrupt OB to be
executed. You can specify the interrupt OB for an event during the creation of the block,
during the device configuration, or with an ATTACH or DETACH instruction. Some events
happen on a regular basis like the program cycle or cyclic events. Other events happen only
a single time, like the startup event and time delay events. Some events happen when there
is a change triggered by the hardware, such as an edge event on an input point or a high
speed counter event. There are also events like the diagnostic error and time error event
which only happen when there is an error. The event priorities and queues are used to
determine the processing order for the event interrupt OBs.
The program cycle event happens once during each program cycle (or scan). During the
program cycle, the CPU writes the outputs, reads the inputs and executes program cycle
OBs. The program cycle event is required and is always enabled. You may have no program
cycle OBs, or you may have multiple OBs selected for the program cycle event. After the
program cycle event is triggered, the lowest numbered program cycle OB (usually OB 1) is
executed. The other program cycle OBs are executed sequentially (in numerical order) within
the program cycle.
The cyclic interrupt events allow you to configure the execution of an interrupt OB at a
configured scan time. The initial scan time is configured when the OB is created and
selected to be a cyclic interrupt OB. A cyclic event will interrupt the program cycle and
execute the cyclic interrupt OB (the cyclic event is at a higher priority class than the program
cycle event).
Only one cyclic interrupt OB can be attached to a cyclic event.
Easy Book
52 Manual, 04/2012, A5E02486774-05
Each cyclic event can be assigned a phase shift so that the execution of cyclic interrupts with
the same scan time can be offset from one another by the phase shift amount. The default
phase shift is 0. To change the initial phase shift, or to change the initial scan time for a
cyclic event, right click on the cyclic interrupt OB in the project tree, click "Properties", then
click "Cyclic interrupt", and enter the new initial values. You can also query and change the
scan time and the phase shift from your program using the Query cyclic interrupt
(QRY_CINT) and Set cyclic interrupt (SET_CINT) instructions. Scan time and phase shift
values set by the SET_CINT instruction do not persist through a power cycle or a transition
to STOP mode; scan time and phase shift values will return to the initial values following a
power cycle or a transition to STOP. The CPU supports a total of four cyclic and time-delay
interrupt events.
The startup event happens one time on a STOP to RUN transition and causes the startup
OBs to be executed. Multiple OBs can be selected for the startup event. The startup OBs are
executed in numerical order.
The time delay interrupt events allow you to configure the execution of an interrupt OB after
a specified delay time has expired. The delay time is specified with the SRT_DINT
instruction. The time delay events will interrupt the program cycle to execute the time delay
interrupt OB. Only one time delay interrupt OB can be attached to a time delay event. The
CPU supports four time delay events.
The hardware interrupt events are triggered by a change in the hardware, such as a rising or
falling edge on an input point, or a HSC (High Speed Counter) event. There can be one
interrupt OB selected for each hardware interrupt event. The hardware events are enabled in
Device configuration. The OBs are specified for the event in the Device configuration or with
an ATTACH instruction in the user program. The CPU supports several hardware interrupt
events. The exact events are based on the CPU model and the number of input points.
The time and diagnostic error interrupt events are triggered when the CPU detects an error.
These events are at a higher priority class that the other interrupt events and can interrupt
the execution of the time delay, cyclic and hardware interrupt events. One interrupt OB can
be specified for each of the time error and diagnostic error interrupt events.
Understanding event execution priorities and queuing

The number of pending (queued) events from a single source is limited, using a different
queue for each event type. Upon reaching the limit of pending events for a given event type,
the next event is lost. Refer to the following section on "Understanding time error events" for
more information regarding queue overflows.
Each CPU event has an associated priority. You cannot change the priority of an OB. In
general, events are serviced in order of priority (highest priority first). Events of the same
priority are serviced on a "first-come, first-served" basis.
Easy Book
Manual, 04/2012, A5E02486774-05 53
Table 4- 1 OB events
Event OB number Quantity allowed Start event OB priority

Program cycle OB 1, OB 200 to 1 program cycle event Startup OB ends 1
OB 65535 Multiple OBs allowed Last program cycle OB ends
Startup OB 100, OB 200 to 1 startup event 1, 2 STOP-to-RUN transition 1
OB 65535 Multiple OBs allowed
Time OB 200 to OB 65535 Up to 4 time events3 Time-delay OB event is scheduled 3
1 OB per event Cyclic OB event is scheduled 7
Process OB 200 to OB 65535 Up to 50 process events4 Edges: 5
1 OB per event Rising edge events: 16 max.
Falling edge events: 16 max.
For HSC: 6
CV=PV: 6 max.
Direction changed: 6 max.
External reset: 6 max.
Diagnostic error OB 82 1 event (only if OB 82 was Module transmits an error 9
loaded)
Time error OB 80 1 event (only if OB 80 was Maximum cycle time was 26
loaded)5 exceeded
A second time interrupt (cyclic or
time-delay) started before the
CPU had finished execution of
the first interrupt
1 The startup event and the program cycle event will never occur at the same time because the startup event will run to
completion before the program cycle event will be started (controlled by the operating system).
2 Only the diagnostic error event (OB 82) interrupts the startup event. All other events are queued to be processed after
the startup event has finished.
3 The CPU provides a total of 4 time events that are shared by the time-delay OBs and the cyclic OBs. The number of
time-delay and cyclic OBs in your user program cannot exceed 4.
4 You can have more than 50 process events if you use the DETACH and ATTACH instructions.
5 You can configure the CPU to stay in RUN if the maximum scan cycle time was exceeded or you can use the
RE_TRIGR instruction to reset the cycle time. However, the CPU goes to STOP mode the second time that the
maximum scan cycle time was exceeded in one scan cycle.
After the execution of an OB with a priority of 2 to 25 has started, processing of that OB

cannot be interrupted by the occurrence of another event, except for by OB 80 (time-error
event, which has a priority of 26). All other events are queued for later processing, allowing
the current OB to finish.
Interrupt latency
The interrupt event latency (the time from notification of the CPU that an event has occurred
until the CPU begins execution of the first instruction in the OB that services the event) is
approximately 175 sec, provided that a program cycle OB is the only event service routine
active at the time of the interrupt event.
Easy Book
54 Manual, 04/2012, A5E02486774-05
Understanding time error events

The occurrence of any of several different time error conditions results in a time error event.
The following time errors are supported:
Maximum cycle time exceeded
Requested OB cannot be started
Queue overflow occurred
The maximum cycle time exceeded condition results if the program cycle does not complete
within the specified maximum scan cycle time. See the section on "Monitoring the cycle time
in the S7-1200 System Manual" for more information regarding the maximum cycle time
condition, how to configure the maximum scan cycle time, and how to reset the cycle timer.
The requested OB cannot be started condition results if an OB is requested by a cyclic
interrupt, a time-delay interrupt, or a time-of-day interrupt, but the requested OB is already
being executed.
The queue overflow occurred condition results if the interrupts are occurring faster than they
can be processed. The number of pending (queued) events is limited using a different queue
for each event type. If an event occurs when the corresponding queue is full, a time error
event is generated.
All time error events trigger the execution of OB 80 if it exists. If an OB 80 is not included in
the user program, then the device configuration of the CPU determines the CPU reaction to
the time error:
The default configuration for time errors, such as starting a second cyclic interrupt before
the CPU has finished the execution of the first, is for the CPU to stay in RUN.
The default configuration for exceeding the maximum time is for the CPU to change to
STOP.
You can use the RE_TRIGR instruction to reset the maximum cycle time. However, if two
"maximum cycle time exceeded" conditions occur within the same program cycle without
resetting the cycle timer, then the CPU transitions to STOP, regardless of whether OB 80
exists. See the section on "Monitoring the cycle time in the S7-1200 System Manual".
OB 80 includes startup information that helps you determine which event and OB generated
the time error. You can program instructions inside OB 80 to examine these startup values
and to take appropriate action.
Table 4- 2 Startup information for OB 80
Input Data type Description

fault_id BYTE 16#01 - maximum cycle time exceeded
16#02 - requested OB cannot be started
16#07 and 16#09 - queue overflow occurred
csg_OBnr OB_ANY Number of the OB which was being executed when the error
occurred
csg_prio UINT Priority of the OB causing the error
No time error interrupt OB 80 is present when you create a new project. If desired, you add a
time error interrupt OB 80 to your project by double-clicking "Add new block" under "Program
blocks" in the tree, then choose "Organization block", and then "Time error interrupt".
Easy Book
Manual, 04/2012, A5E02486774-05 55
Understanding diagnostic error events

Analog (local), PROFINET, and PROFIBUS devices are capable of detecting and reporting
diagnostic errors. The occurrence or removal of any of several different diagnostic error
conditions results in a diagnostic error event. The following diagnostic errors are supported:
No user power
High limit exceeded
Low limit exceeded
Wire break
Short circuit
Diagnostic error events trigger the execution of OB 82 if it exists. If OB 82 does not exist,
then the CPU ignores the error. No diagnostic error interrupt OB 82 is present when you
create a new project. If desired, you add a diagnostic error interrupt OB 82 to your project by
double-clicking "Add new block" under "Program blocks" in the tree, then choose
"Organization block", and then "Diagnostic error interrupt".
Note
Diagnostic errors for multi-channel local analog devices (I/O, RTD, and Thermocouple)
The OB 82 diagnostic error interrupt can report only one channel's diagnostic error at a time.
If two channels of a multi-channel device have an error, then the second error only triggers
OB 82 under the following conditions: the first channel error clears, the execution of OB 82
triggered by the first error is complete, and the second error still exists.
OB 82 includes startup information that helps you determine whether the event is due to the
occurrence or removal of an error, and the device and channel which reported the error. You
can program instructions inside OB 82 to examine these startup values and to take
appropriate action.
Table 4- 3 Startup information for OB 82

IOstate WORD IO state of the device:
Bit 0 = 1 if the configuration is correct, and = 0 if the configuration is
no longer correct.
Bit 4 = 1 if an error is present (such as a wire break). (Bit 4 = 0 if
there is no error.)
Bit 5 = 1 if the configuration is not correct, and = 0 if the configuration
is correct again.
Bit 6 = 1 if an I/O access error has occurred. Refer to laddr for the
hardware identifier of the I/O with the access error. (Bit 6 = 0 if there
is no error.)
laddr HW_ANY Hardware identifier of the device or functional unit that reported the
error1
Easy Book
56 Manual, 04/2012, A5E02486774-05
4.4 Memory areas, addressing and data types

channel UINT Channel number
multierror BOOL TRUE if more than one error is present
1 The laddr input contains the hardware identifier of the device or functional unit which returned the error. The hardware
identifier is assigned automatically when components are inserted in the device or network view and appears in the
Constants tab of PLC tags. A name is also assigned automatically for the hardware identifier. These entries in the
Constants tab of the PLC tags cannot be changed.
See also
Going online to monitor the values in the CPU (Page 225)

The CPU provides the following memory areas to store the user program, data, and
configuration:
Load memory is non-volatile storage for the user program, data and configuration. When
a project is downloaded to the CPU, it is first stored in the Load memory area. This area
is located either in a memory card (if present) or in the CPU. This non-volatile memory
area is maintained through a power loss. You can increase the amount of load memory
available for data logs by installing a memory card.
Work memory is volatile storage for some elements of the user project while executing
the user program. The CPU copies some elements of the project from load memory into
work memory. This volatile area is lost when power is removed, and is restored by the
CPU when power is restored.
Retentive memory is non-volatile storage for a limited quantity of work memory values.
The retentive memory area is used to store the values of selected user memory locations
during power loss. When a power down or power loss occurs, the CPU restores these
retentive values upon power up.
An optional SIMATIC memory card provides an alternative memory for

storing your user program or a means for transferring your program. If you
use the memory card, the CPU runs the program from the memory card
and not from the memory in the CPU.
Check that the memory card is not write-protected. Slide the protection
switch away from the "Lock" position.
Easy Book
Manual, 04/2012, A5E02486774-05 57
Use the optional SIMATIC memory card either as a program card or as a transfer card.
Use the transfer card to copy your project to multiple CPUs without using STEP 7. The
transfer card copies a stored project from the card to the memory of the CPU. You must
remove the transfer card after copying the program to the CPU.
The program card takes the place of CPU memory; all of your CPU functions are
controlled by the program card. Inserting the program card erases all of the internal load
memory of the CPU (including the user program and any forced I/O). The CPU then
executes the user program from the program card.
You can also use the program card for collecting data log files (Page 106). The program
card provides more memory than the internal memory of the CPU. The Web server
function (Page 181) of the CPU allows you to download the data log files to a computer.
Note
The program card must remain in the CPU. If you remove the program card, the CPU goes
to STOP mode.
4.4.1 Data types supported by the S7-1200

Data types are used to specify both the size of a data element as well as how the data are to
be interpreted. Each instruction parameter supports at least one data type, and some
parameters support multiple data types. Hold the cursor over the parameter field of an
instruction to see which data types are supported for a given parameter.
Table 4- 4 Data types supported by the S7-1200
Data types Description

Bit and bit-sequence Bool is a Boolean or bit value.
data types
Byte is an 8-bit byte value.
Word is a 16-bit value.
DWord is a 32-bit double-word value.
Integer data types USInt (unsigned 8-bit integer) and SInt (signed 8-bit integer) are "short" integers (8 bits or 1
byte of memory) that can be signed or unsigned.
UInt (unsigned 16-bit integer) and Int (signed 16-bit integer) are integers (16 bits or 1 word of
memory) that can be signed or unsigned.
UDInt (unsigned 32-bit integer) and DInt (signed 32-bit integer) are double integers (32 bits or
1 double-word of memory) that can be signed or unsigned.
Real number data Real is a 32-bit Real number or floating-point value.
types
LReal is a 64-bit Real number or floating-point value.
Easy Book
58 Manual, 04/2012, A5E02486774-05
Data types Description

Date and time data Date is a 16-bit date value (similar to a UInt) that contains the number of days since January
types 1, 1990. The maximum date value is 65378 (16#FF62), which corresponds to December 31,
2168. All possible Date values are valid.
DTL (date and time long) is a structure of 12 bytes that saves information on date and time in
a predefined structure.
Year (UInt): 1970 to 2554
Month (USInt): 1 to 12
Day (USInt): 1 to 31
Weekday (USInt): 1 (Sunday) to 7 (Saturday)
Hours (USInt): 0 to 23
Minutes (USInt): 0 to 59
Seconds (USInt): 0 to 59
Nanoseconds (UDInt): 0 to 999999999
Time is a 32-bit IEC time value (similar to a Dint) that stores the number of milliseconds (from
0 to 24 days 20 hours 31 minutes 23 seconds and 647 ms). All possible Time values are
valid. Time values can be used for calculations, and negative times are possible.
TOD (time of day) is a 32-bit time-of-day value (similar to a Dint) that contains the number of
milliseconds since midnight (from 0 to 86399999).
Character and string Char is an 8-bit single character.
data types
String is a variable-length string of up to 254 characters.
Array and structure Array contains multiple elements of the same data type. Arrays can be created in the block
data types interface editors for OB, FC, FB, and DB. You cannot create an array in the PLC tags editor.
Struct defines a structure of data consisting of other data types. The Struct data type can be
used to handle a group of related process data as a single data unit. You declare the name
and internal data structure for the Struct data type in the data block editor or a block interface
editor.
Arrays and structures can also be assembled into a larger structure. A structure can be nested
up to eight levels deep. For example, you can create a structure of structures that contain arrays.
PLC data types PLC Data type is a user-defined data structure that defines a custom data structure that you can
use multiple times in your program. When you create a PLC Data type, the new PLC Data type
appears in the data type selector drop drop-lists in the DB editor and code block interface editor.
PLC Data types can be used directly as a data type in a code block interface or in data blocks.
PLC Data types can be used as a template for the creation of multiple global data blocks that use
the same data structure.
Pointer data types Pointer provides an indirect reference to the address of a tag. It occupies 6 bytes (48 bits) in
memory and can include the following information to a variable: DB number (or 0 if the data is
not stored in a DB), memory area in the CPU, and the memory address.
Any provides an indirect reference to the beginning of a data area and identifies its length.
The Any pointer uses 10 bytes in memory and can include the following information: Data
type of the data elements, number of data elements, memory area or DB number, and the
"Byte.Bit" starting address of the data.
Variant provides an indirect reference to tags of different data types or parameters. The
Variant pointer recognizes structures and individual structural components. The Variant does
not occupy any space in memory.
Easy Book
Manual, 04/2012, A5E02486774-05 59
Although not available as data types, the following BCD (binary coded decimal) numeric
formats are supported by the conversion instructions.
BCD16 is a 16-bit value (-999 to 999).
BCD32 is a 32-bit value (-9999999 to 9999999).
4.4.2 Addressing memory areas

STEP 7 facilitates symbolic programming. You create symbolic names or "tags" for the
addresses of the data, whether as PLC tags relating to memory addresses and I/O points or
as local variables used within a code block. To use these tags in your user program, simply
enter the tag name for the instruction parameter. For a better understanding of how the CPU
structures and addresses the memory areas, the following paragraphs explain the "absolute"
addressing that is referenced by the PLC tags. The CPU provides several options for storing
data during the execution of the user program:
Global memory: The CPU provides a variety of specialized memory areas, including
inputs (I), outputs (Q) and bit memory (M). This memory is accessible by all code blocks
without restriction.
Data block (DB): You can include DBs in your user program to store data for the code
blocks. The data stored persists when the execution of the associated code block comes
to an end. A "global" DB stores data that can be used by all code blocks, while an
instance DB stores data for a specific FB and is structured by the parameters for the FB.
Temp memory: Whenever a code block is called, the operating system of the CPU
allocates the temporary, or local, memory (L) to be used during the execution of the
block. When the execution of the code block finishes, the CPU reallocates the local
memory for the execution of other code blocks.
Each different memory location has a unique address. Your user program uses these
addresses to access the information in the memory location.
References to the input (I) or output (Q) memory areas, such as I0.3 or Q1.7, access the
process image. To immediately access the physical input or output, append the reference
with ":P" (such as I0.3:P, Q1.7:P, or "Stop:P").
Forcing writes a value to a physical input (Ix.y:P) or a physical output (Qx.y:P) only. To force
an input or output, append a ":P" to the PLC tag or the address. For more information, see
"Forcing variables in the CPU" (Page 227).
Table 4- 5 Memory areas
Memory area Description Force Retentive

I Copied from physical inputs at the beginning of the scan No No
Process image input cycle
I_:P1 Immediate read of the physical input points on the CPU, Yes No
(Physical input) SB, and SM
Q Copied to physical outputs at the beginning of the scan No No
Process image output cycle
Q_:P1 Immediate write to the physical output points on the Yes No
(Physical output) CPU, SB, and SM
Easy Book
60 Manual, 04/2012, A5E02486774-05
Memory area Description Force Retentive

M Control and data memory No Yes
Bit memory (optional)
L Temporary data for a block local to that block No No
Temp memory
DB Data memory and also parameter memory for FBs No Yes
Data block (optional)
1 To immediately access (or to force) the physical inputs and physical outputs, append a ":P" to the address or tag (such
as I0.3:P, Q1.7:P, or "Stop:P").
Each different memory location has a unique address. Your user program uses these
addresses to access the information in the memory location. The absolute address consists
of the following elements:
Memory area (such as I, Q, or M)
Size of the data to be accessed (such as "B" for Byte or "W" for Word)
Address of the data (such as Byte 3 or Word 3)
When accessing a bit in the address for a Boolean value, you do not enter a mnemonic for
the size. You enter only the memory area, the byte location, and the bit location for the data
(such as I0.0, Q0.1, or M3.4).
Absolute address of a memory area:

0
A Memory area identifier

B Byte address: byte 3

C Separator ("byte.bit")
D Bit location of the byte (bit 4 of 8)
E Bytes of the memory area
F Bits of the selected byte

In the example, the memory area and byte address (M = bit memory area, and 3 = Byte 3)
are followed by a period (".") to separate the bit address (bit 4).
Easy Book
Manual, 04/2012, A5E02486774-05 61
Configuring the I/O in the CPU and I/O modules
When you add a CPU and I/O modules to your

configuration screen, I and Q addresses are
automatically assigned. You can change the
default addressing by selecting the address field in
the configuration screen and typing new numbers.
Digital inputs and outputs are assigned in
groups of 8 points (1 byte), whether the module
uses all the points or not.
Analog inputs and outputs are assigned in
groups of 2 points (4 bytes).
The figure shows an example of a CPU 1214C with two SMs and one SB. In this example,
you could change the address of the DI8 module to 2 instead of 8. The tool will assist you by
changing address ranges that are the wrong size or conflict with other addresses.
4.4.3 Accessing a "slice" of a tagged data type

PLC tags and data block tags can be accessed at the bit, byte, or word level depending on
their size. The syntax for accessing such a data slice is as follows:
"<PLC tag name>".xn (bit access)
"<PLC tag name>".bn (byte access)
"<PLC tag name>".wn (word access)
"<Data block name>".<tag name>.xn (bit access)
"<Data block name>".<tag name>.bn (byte access)
"<Data block name>".<tag name>.wn (word access)
A double word-sized tag can be accessed by bits 0 - 31, bytes 0 - 3, or word 0 - 1. A word-
sized tag can be accessed by bits 0 - 15, bytes 0 - 2, or word 0. A byte-sized tag can be
accessed by bits 0 - 8, or byte 0. Bit, byte, and word slices can be used anywhere that bits,
bytes, or words are expected operands.
Easy Book
62 Manual, 04/2012, A5E02486774-05
Note
Valid data types that can be accessed by slice are Byte, Char, Conn_Any, Date, DInt,
DWord, Event_Any, Event_Att, Hw_Any, Hw_Device, HW_Interface, Hw_Io, Hw_Pwm,
Hw_SubModule, Int, OB_Any, OB_Att, OB_Cyclic, OB_Delay, OB_WHINT, OB_PCYCLE,
OB_STARTUP, OB_TIMEERROR, OB_Tod, Port, Rtm, SInt, Time, Time_Of_Day, UDInt,
UInt, USInt, and Word. PLC Tags of type Real can be accessed by slice, but data block tags
of type Real cannot.
Examples
In the PLC tag table, "DW" is a declared tag of type DWORD. The examples show bit, byte,
and word slice access:
LAD FBD SCL

Bit access IF "DW".x11 THEN
...
END_IF;
Byte access IF "DW".b2 = "DW".b3

THEN
...
END_IF;
Word access out:= "DW".w0 AND

"DW".w1;
4.4.4 Accessing a tag with an AT overlay

The AT tag overlay allows you to access an already-declared tag of a standard access block
with an overlaid declaration of a different data type. You can, for example, address the
individual bits of a tag of a Byte, Word, or DWord data type with an Array of Bool.
Easy Book
Manual, 04/2012, A5E02486774-05 63
Declaration
To overlay a parameter, declare an additional parameter directly after the parameter that is
to be overlaid and select the data type "AT". The editor creates the overlay, and you can
then choose the data type, struct, or array that you wish to use for the overlay.
Example
This example shows the input parameters of a standard-access FB. The byte tag B1 is
overlaid with an array of Booleans:
Table 4- 6 Overlay of a byte with a Boolean array
7 6 5 4 3 2 1 0
AT[0] AT[1] AT[2] AT[3] AT[4] AT[5] AT[6] AT[7]
Another example is a DWord tag overlaid with a Struct:
Easy Book
64 Manual, 04/2012, A5E02486774-05
The overlay types can be addressed directly in the program logic:
LAD FBD SCL

IF #AT[1] THEN
...
END_IF;
IF (#DW1_Struct.S1 =
W#16#000C) THEN
...
END_IF;
out1 := #DW1_Struct.S2;
Rules
Overlaying of tags is only possible in FB and FC blocks with standard access.
You can overlay parameters for all block types and all declaration sections.
An overlaid parameter can be used like any other block parameter.
You cannot overlay parameters of type VARIANT.
The size of the overlaying parameter must be less than or equal to the size of the overlaid
parameter.
The overlaying variable must be declared immediately after the variable that it overlays
and identified with the keyword "AT".
Easy Book
Manual, 04/2012, A5E02486774-05 65
4.5 Pulse outputs
4.5 Pulse outputs

The CPU or signal board (SB) can be configured to provide two pulse generators for
controlling high-speed pulse output functions, either as pulse-width modulation (PWM) or as
pulse-train output (PTO). The basic motion instructions use PTO outputs. You can assign
each pulse generator to either PWM or PTO, but not both at the same time.
Pulse outputs cannot be used by other instructions in the

user program. When you configure the outputs of the
CPU or SB as pulse generators, the corresponding
output addresses (Q0.0 to Q0.3, and Q4.0 to Q4.3) are
removed from the Q memory and cannot be used for
other purposes in your user program. If your user
program writes a value to an output used as a pulse
generator, the CPU does not write that value to the
physical output.
NOTICE
Do not exceed the maximum pulse frequency.
As described in the S7-1200 System Manual, the maximum pulse frequency of the pulse
output generators is 100 KHz for the digital outputs of the CPU, 20 KHz for the digital
outputs of the standard SB, and 200 KHz for the digital outputs of the high speed SBs.
When configuring the basic motion instructions, be aware that STEP 7 does not alert you if
you configure an axis with a maximum speed or frequency that exceeds this hardware
limitation. This could cause problems with your application, so always ensure that you do
not exceed the maximum pulse frequency of the hardware.
The two pulse generators are mapped to specific digital outputs as shown in the following
table. You can use onboard CPU outputs, or you can use the optional signal board outputs.
The output point numbers are shown in the following table (assuming the default output
configuration). If you have changed the output point numbering, then the output point
numbers will be those you assigned. Regardless, PTO1/PWM1 uses the first two digital
outputs, and PTO2/PWM2 uses the next two digital outputs, either on the CPU or on the
attached signal board. Note that PWM requires only one output, while PTO can optionally
use two outputs per channel. If an output is not required for a pulse function, it is available
for other uses.
Easy Book
66 Manual, 04/2012, A5E02486774-05
4.5 Pulse outputs
Table 4- 7 Output assignments for the pulse generators
Description Default output assignment Pulse Direction

PTO 1 Onboard CPU Q0.0 Q0.1
Signal board Q4.0 Q4.1
PWM 1 Onboard CPU Q0.0 --
Signal board Q4.0 --
PTO 2 Onboard CPU Q0.2 Q0.3
Signal board Q4.2 Q4.3
PWM 2 Onboard CPU Q0.2 --
Signal board Q4.2 --
Easy Book
Manual, 04/2012, A5E02486774-05 67
4.5 Pulse outputs
Easy Book
68 Manual, 04/2012, A5E02486774-05
Easy to create the device configuration 5
You create the device configuration for your PLC by adding a CPU and additional modules to
your project.

Communications module (CM) or communication processor (CP): Up to 3, inserted in slots

101, 102, and 103
CPU: Slot 1
Ethernet port of CPU
Signal board (SB), communication board (CB) or battery board (BB): up to 1, inserted in the
CPU
Signal module (SM) for digital or analog I/O: up to 8, inserted in slots 2 through 9
CPU 1214C and CPU 1215C allow 8, CPU 1212C allows 2, CPU 1211C does not allow any
To create the device configuration, add a

device to your project.
In the Portal view, select "Devices &
Networks" and click "Add device".
In the Project view, under the project

name, double-click "Add new device".
Easy Book
Manual, 04/2012, A5E02486774-05 69
Easy to create the device configuration
5.1 Detecting the configuration for an unspecified CPU
5.1 Detecting the configuration for an unspecified CPU
If you are connected to a CPU, you can upload the

configuration of that CPU, including any modules, to your
project. Simply create a new project and select the "unspecified
CPU" instead of selecting a specific CPU. (You can also skip
the device configuration entirely by selecting the "Create a PLC
program" from the "First steps". STEP 7 then automatically
creates an unspecified CPU.)
From the program editor, you select the "Hardware detection"
command from the "Online" menu.
From the device configuration editor, you select the option for detecting the configuration of
the connected device.
After you select the CPU from the online dialog and click the Load button, STEP 7 uploads
the hardware configuration from the CPU, including any modules (SM, SB, or CM). You can
then configure the parameters for the CPU and the modules (Page 73).
Easy Book
70 Manual, 04/2012, A5E02486774-05
5.2 Adding a CPU to the configuration
5.2 Adding a CPU to the configuration
You create your device configuration by inserting

a CPU into your project. Select the CPU in the
"Add a new device" dialog and click "OK" to add
the CPU to the project.
The Device view shows the

CPU and rack.
Selecting the CPU in the Device view

displays the CPU properties in the
inspector window. Use these properties
to configure the operational parameters
of the CPU (Page 73).
Note
The CPU does not have a pre-configured IP address. You must manually assign an IP
address for the CPU during the device configuration. If your CPU is connected to a router on
the network, you also enter the IP address for a router.
Easy Book
Manual, 04/2012, A5E02486774-05 71
5.3 Adding modules to the configuration
5.3 Adding modules to the configuration

Use the hardware catalog to add modules to the CPU:
Signal module (SM) provides additional digital or analog I/O points. These modules are
connected to the right side of the CPU.
Signal board (SB) provides just a few additional I/O points for the CPU. The SB is
installed on the front of the CPU.
Battery Board 1297 (BB) provides long-term backup of the realtime clock. The BB is
installed on the front of the CPU.
Communication board (CB) provides an additional communication port (such as RS485).
The CB is installed on the front of the CPU.
Communication module (CM) and communication processor (CP) provide an additional
communication port, such as for PROFIBUS or GPRS. These modules are connected to
the left side of the CPU.
To insert a module into the device configuration, select the module in the hardware catalog
and either double-click or drag the module to the highlighted slot. You must add the modules
to the device configuration and download the hardware configuration to the CPU for the
modules to be functional.
Table 5- 1 Adding a module to the device configuration
Module Select the module Insert the module Result

SM
SB, BB or
CB
CM or CP
Easy Book
72 Manual, 04/2012, A5E02486774-05
5.4 Configuring the operation of the CPU and modules

To configure the operational parameters for the CPU, select the CPU in the Device view and
use the "Properties" tab of the inspector window.
PROFINET IP address and time synchronization

for the CPU
Startup behavior of the CPU following an OFF-to-
ON power transition
Local (on-board) digital and analog I/O, high-
speed counters (HSC), and pulse generators
System clock (time, time zone and daylight saving
time)
Read/write protection and password for accessing
the CPU
Maximum cycle time or a fixed minimum cycle
time and communications load
Configuring the STOP-to-RUN operation of the CPU

Whenever the operating state changes from STOP to RUN, the CPU clears the process
image inputs, initializes the process image outputs, and processes the startup OBs.
(Therefore, any read accesses to the process-image inputs by instructions in the startup OBs
will read zero rather than the current physical input value.) To read the current state of a
physical input during startup, you must perform an immediate read. The startup OBs and any
associated FCs and FBs are executed next. If more than one startup OB exists, each is
executed in order according to the OB number, with the lowest OB number executing first.
The CPU also performs the following tasks during the startup processing.
Interrupts are queued but not processed during the startup phase
No cycle time monitoring is performed during the startup phase
Configuration changes to HSC (high-speed counter), PWM (pulse-width modulation), and
PtP (point-to-point communication) modules can be made in startup
Actual operation of HSC, PWM, and point-to-point communication modules only occurs in
RUN
After the execution of the startup OBs finishes, the CPU goes to RUN mode and processes
the control tasks in a continuous scan cycle.
Easy Book
Manual, 04/2012, A5E02486774-05 73
Use the CPU properties to configure how the CPU starts up after a power cycle.
In STOP mode
In RUN mode
In the previous
mode (prior to the
power cycle)
The CPU performs a warm restart before going to RUN mode. Warm restart resets all non-
retentive memory to the default start values, but the CPU retains the current values stored in
the retentive memory.
Note
The CPU always performs a restart after a download
Whenever you download an element of your project (such as a program block, data block, or
hardware configuration), the CPU performs a restart on the next transition to RUN mode. In
addition to clearing the inputs, initializing the outputs and initializing the non-retentive
memory, the restart also initializes the retentive memory areas.
After the restart that follows a download, all subsequent STOP-to-RUN transitions perform a
warm restart (that does not initialize the retentive memory).
Easy Book
74 Manual, 04/2012, A5E02486774-05
5.4.1 System memory and clock memory provide standard functionality

You use the CPU properties to enable bytes for "system memory" and "clock memory". Your
program logic can reference the individual bits of these functions by their tag names.
You can assign one byte in M memory for system memory. The byte of system memory
provides the following four bits that can be referenced by your user program by the
following tag names:
First cycle: (Tag name "FirstScan") bit is set to1 for the duration of the first scan after
the startup OB finishes. (After the execution of the first scan, the "first scan" bit is set
to 0.)
Diagnostics status changed (Tag name: "DiagStatusUpdate") is set to 1 for one scan
after the CPU logs a diagnostic event. Because the CPU does not set the "diagnostic
graph changed" bit until the end of the first execution of the program cycle OBs, your
user program cannot detect if there has been a diagnostic change either during the
execution of the startup OBs or the first execution of the program cycle OBs.
Always 1 (high): (Tag name "AlwaysTRUE") bit is always set to 1.
Always 0 (low): (Tag name "AlwaysFALSE") bit is always set to 0.
You can assign one byte in M memory for clock memory. Each bit of the byte configured
as clock memory generates a square wave pulse. The byte of clock memory provides 8
different frequencies, from 0.5 Hz (slow) to 10 Hz (fast). You can use these bits as control
bits, especially when combined with edge instructions, to trigger actions in the user
program on a cyclic basis.
The CPU initializes these bytes on the transition from STOP mode to STARTUP mode. The
bits of the clock memory change synchronously to the CPU clock throughout the STARTUP
and RUN modes.
CAUTION
Overwriting the system memory or clock memory bits can corrupt the data in these
functions and cause your user program to operate incorrectly, which can cause damage to
equipment and injury to personnel.
Because both the clock memory and system memory are unreserved in M memory,
instructions or communications can write to these locations and corrupt the data.
Avoid writing data to these locations to ensure the proper operation of these functions, and
always implement an emergency stop circuit for your process or machine.
Easy Book
Manual, 04/2012, A5E02486774-05 75
System memory configures a byte with bits that turn on (value = 1) for a specific event.
Table 5- 2 System memory
7 6 5 4 3 2 1 0
Reserved Always off Always on Diagnostic status First scan indicator
Value 0 Value 0 Value 1 indicator
1: First scan after
1: Change startup
0: No change 0: Not first scan
Clock memory configures a byte that cycles the individual bits on and off at fixed intervals.
Each clock bit generates a square wave pulse on the corresponding M memory bit. These
bits can be used as control bits, especially when combined with edge instructions, to trigger
actions in the user code on a cyclic basis.
Table 5- 3 Clock memory
Bit number 7 6 5 4 3 2 1 0
Tag name
Period (s) 2.0 1.6 1.0 0.8 0.5 0.4 0.2 0.1
Frequency (Hz) 0.5 0.625 1 1.25 2 2.5 5 10
Because clock memory runs asynchronously to the CPU cycle, the status of the clock memory can change several times
during a long cycle.
Easy Book
76 Manual, 04/2012, A5E02486774-05
5.5 Configuring the IP address of the CPU
Configuring the operation of the I/O and communication modules

To configure the operational parameters for the signal module (SM), signal board (SB), or
communication module (CM), select the module in the Device view and use the "Properties"
tab of the inspector window.
Signal module (SM) and signal board (SB)

Digital I/O: Configure the individual inputs, such as
for Edge detection and "pulse catch" (to stay on or
off for one scan after a momentary high- or low
pulse). Configure the outputs to use a freeze or
substitute value on a transition from RUN mode to
STOP mode.
Analog I/O: Configure the parameters for individual inputs (such as voltage / current,
range and smoothing) and also enable underflow or overflow diagnostics. Configure the
parameters for individual analog outputs and enables diagnostics, such as short-circuit
(for voltage outputs) or overflow values.
I/O addresses: Configure the start address for the set of inputs and outputs of the
module.
Communication module (CM) and communication

board (CB)
Port configuration: Configure the communication
parameters, such as baud rate, parity, data bits,
stop bits, and wait time.
Transmit and receive message: Configure options related to transmitting and receiving
data (such as the message-start and message-end parameters)
You can also change these configuration parameters with your user program.

Because the CPU does not have a pre-configured IP address, you must manually assign an
IP address. You configure the IP address and the other parameters for the PROFINET
interface when you configure the properties for the CPU.
In a PROFINET network, each device is assigned a unique Media Access Control
address (MAC address) by the manufacturer for identification. Each device must also
have an IP address.
A subnet is a logical grouping of connected network devices. A mask (also known as the
subnet mask or network mask) defines the boundaries of a subnet. The only connection
between different subnets is via a router. Routers are the link between LANs and rely on
IP addresses to deliver and receive data packets.
Before you can download an IP address to the CPU, you must ensure that the IP address for
your CPU is compatible with the IP address of your programming device.
Easy Book
Manual, 04/2012, A5E02486774-05 77
You can use STEP 7 to determine the IP address of your programming device:
1. Expand the "Online access" folder in the Project tree to display your networks.
2. Select the network that connects to the CPU.
3. Right-click the specific network to display the context menu.
4. Select the "Properties" command.
Note
The IP address for the CPU must be compatible with the IP address and subnet mask for
the programming device. Consult your network specialist for a suitable IP address and
subnet mask for your CPU.
The "Properties" window displays

the settings for the programming
device.
After determining the IP address

and subnet mask for the CPU,
enter the IP address for the CPU
and for the router (if applicable).
Refer to the S7-1200 System
Manual for more information.
Easy Book
78 Manual, 04/2012, A5E02486774-05
5.6 Protecting access to the CPU or code block is easy
After completing the configuration,

download the project to the CPU.
The IP addresses for the CPU and
for the router (if applicable) are
configured when you download the
project.

The CPU provides three levels of security for restricting access to specific functions. When
you configure the security level and password for a CPU, you limit the functions and memory
areas that can be accessed without entering a password.
The password is case-sensitive.
To configure the password,

follow these steps:
1. In the "Device configuration",
select the CPU.
2. In the inspector window,
select the "Properties" tab.
3. Select the "Protection"
property to select the
protection level and to enter a
password.
Each level allows certain functions to be accessible without a password. The default
condition for the CPU is to have no restriction and no password-protection. To restrict access
to a CPU, you configure the properties of the CPU and enter the password.
Entering the password over a network does not compromise the password protection for the
CPU. Password protection does not apply to the execution of user program instructions
including communication functions. Entering the correct password provides access to all of
the functions.
PLC-to-PLC communications (using communication instructions in the code blocks) are not
restricted by the security level in the CPU. HMI functionality is also not restricted.
Easy Book
Manual, 04/2012, A5E02486774-05 79
Table 5- 4 Security levels for the CPU
Security level Access restrictions

No protection Allows full access without password-protection.
Write protection Allows HMI access and all forms of PLC-to-PLC communications without password-protection.
Password is required for modifying (writing to) the CPU and for changing the CPU mode
(RUN/STOP).
Read/write protection Allows HMI access and all forms of PLC-to-PLC communications without password-protection.
Password is required for reading the data in the CPU, for modifying (writing to) the CPU, and for
changing the CPU mode (RUN/STOP).
5.6.1 Know-how protection

Know-how protection allows you to prevent one or more code blocks (OB, FB, FC, or DB) in
your program from unauthorized access. You create a password to limit access to the code
block. The password-protection prevents unauthorized reading or modification of the code
block. Without the password, you can read only the following information about the code
block:
Block title, block comment, and block properties
Transfer parameters (IN, OUT, IN_OUT, Return)
Call structure of the program
Global tags in the cross references (without information on the point of use), but local
tags are hidden
When you configure a block for "know-how" protection, the code within the block cannot be
accessed except after entering the password.
Easy Book
80 Manual, 04/2012, A5E02486774-05
Use the "Properties" task card of the code block to configure the know-how protection for
that block. After opening the code block, select "Protection" from Properties.
1. In the Properties for the code block, click

the "Protection" button to display the
"Know-how protection" dialog.
2. Click the "Define" button to enter the
password.
After entering and confirming the password,

click "OK".
5.6.2 Copy protection

An additional security feature allows you to bind the program or code blocks for use with a
specific memory card or CPU. This feature is especially useful for protecting your intellectual
property. When you bind a program or block to a specific device, you restrict the program or
code block for use only with a specific memory card or CPU. This feature allows you to
distribute a program or code block electronically (such as over the Internet or through email)
or by sending a memory cartridge.
Easy Book
Manual, 04/2012, A5E02486774-05 81
Use the "Properties" task card of the code block to bind the block to a specific CPU or
memory card.
1. After opening the code block, select "Protection".
2. From the drop-down list under "Copy protection" task, select the option to bind the code
block either to a memory card or to a specific CPU.
3. Select the type of copy protection and enter the serial number for the memory card or
CPU.
Note
The serial number is case-sensitive.
Easy Book
82 Manual, 04/2012, A5E02486774-05
Programming made easy 6
6.1 Easy to design your user program
When you create a user program for the automation tasks, you insert the instructions for the
program into code blocks (OB, FB, or FC).
Choosing the type of structure for your user program

Based on the requirements of your application, you can choose either a linear structure or a
modular structure for creating your user program.
A linear program executes all of the instructions for your automation tasks in sequence,
one after the other. Typically, the linear program puts all of the program instructions into
one program cycle OB (such as OB 1) for cyclic execution of the program.
A modular program calls specific code blocks that perform specific tasks. To create a
modular structure, you divide the complex automation task into smaller subordinate tasks
that correspond to the functional tasks being performed by the process. Each code block
provides the program segment for each subordinate task. You structure your program by
calling one of the code blocks from another block.
Linear structure: Modular structure:
2% 2% )%
)&
By designing FBs and FCs to perform generic tasks, you create modular code blocks. You
then structure your user program by having other code blocks call these reusable modules.
The calling block passes device-specific parameters to the called block. When a code block
calls another code block, the CPU executes the program code in the called block. After
execution of the called block is complete, the CPU resumes the execution of the calling
block. Processing continues with execution of the instruction that follows after the block call.
You can also assign an OB to an interrupting event. When the event occurs, the CPU
executes the program code in the associated OB. After the execution of the OB is complete,
the CPU resumes the execution at the point in the user program when the interrupting event
occurred, which could be any point in the scan.
Easy Book
Manual, 04/2012, A5E02486774-05 83
Programming made easy
A Calling block (or interrupted block)

2%)%)& 2%)%)&
B Called FB or BC (or interrupting OB)

Program execution
Instruction (or interrupting event) that initiates
the execution of another block

Program execution
Block end (returns to calling block)

You can nest the block calls for a more modular structure. In the following example, the
nesting depth is 3: the program cycle OB plus 3 layers of calls to code blocks.
Start of cycle
Nesting depth
2% )% )&
'%
)% )% )&
'% '%
'%
)&
By creating generic code blocks that can be reused within the user program, you can simplify
the design and implementation of the user program.
You can create reusable blocks of code for standard tasks, such as for controlling a pump
or a motor. You can also store these generic code blocks in a library that can be used by
different applications or solutions.
When you structure the user program into modular components that relate to functional
tasks, the design of your program can be easier to understand and to manage. The
modular components not only help to standardize the program design but can also help
to make updating or modifying the program code quicker and easier.
Creating modular components simplifies the debugging of your program. By structuring
the complete program as a set of modular program segments, you can test the
functionality of each code block as it is developed.
Utilizing a modular design that relates to specific functional tasks can reduce the time
required for the commissioning of the completed application.
Easy Book
84 Manual, 04/2012, A5E02486774-05
6.1.1 Use OBs for organizing your user program

Organization blocks provide the structure for your program. They serve as the interface
between the operating system and the user program. OBs are event-driven. An event, such
as a diagnostic interrupt or a time interval, will cause the CPU to execute an OB. Some OBs
have predefined start events and behavior.
The program cycle OB contains your main program. You can include more than one program
cycle OB in your user program. During RUN mode, the program cycle OBs execute at the
lowest priority level and can be interrupted by all other types of program processing. (The
startup OBs do not interrupt the program cycle OBs because the CPU executes the startup
OBs before going to RUN mode.) After finishing the processing of the program cycle OBs,
the CPU immediately executes the program cycle OBs again. This cyclic processing is the
"normal" type of processing used for PLCs. For many applications, the entire user program is
located in a single OB, such as the default program cycle OB 1.
You can create other OBs to

perform specific functions, such
as startup tasks, for handling
interrupts and errors, or for
executing specific program code
at specific time intervals.
Use the "Add new block" dialog to
create a new OB in your user
program.
The CPU determines the order for handling interrupt events by a priority assigned to each
OB (Page 52).
Easy Book
Manual, 04/2012, A5E02486774-05 85
You can modify the operational

parameters for an OB. For example, you
can configure the time parameter for a
time-delay OB or for a cyclic interrupt OB.
Creating an additional OB within a class of OB: You can create multiple OBs for your user
program, even for the program cycle and startup OB classes. Use the "Add new block"
dialog to create an OB. Enter the name for your OB and provide an OB number of 200 or
greater.
If you create multiple program cycle OBs for your user program, the CPU executes each
program cycle OB in numerical sequence, starting with the lowest numbered OB, typically
OB 1. For example, after the first program cycle OB (OB 1) finishes, the CPU executes the
second program cycle OB (such as OB 200).
6.1.2 FBs and FCs make programming the modular tasks easy
A function (FC) is like a subroutine. An FC is a code block that typically performs a specific
operation on a set of input values. The FC stores the results of this operation in memory
locations. Use FCs to perform the following tasks:
To perform standard and reusable operations, such as for mathematical calculations.
To perform functional tasks, such as for individual controls using bit logic operations.
An FC can also be called several times at different points in a program. This reuse simplifies
the programming of frequently recurring tasks.
Unlike an FB, an FC does not have an associated instance DB. The FC uses its temp
memory (L) for the data used to calculate the operation. The temporary data is not saved. To
store data for use after the execution of the FC has finished, assign the output value to a
global memory location, such as M memory or to a global DB.
A function block (FB) is like a subroutine with memory. An FB is a code block whose calls
can be programmed with block parameters. The FB stores the input (IN), output (OUT), and
in/out (IN_OUT) parameters in variable memory that is located in a data block (DB), or
"instance" DB. The instance DB provides a block of memory that is associated with that
instance (or call) of the FB and stores data after the FB finishes.
You typically use an FB to control the operation for tasks or devices that do not finish their
operation within one scan cycle. To store the operating parameters so that they can be
quickly accessed from one scan to the next, each FB in your user program has one or more
instance DBs. When you call an FB, you also open an instance DB that stores the values of
the block parameters and the static local data for that call or "instance" of the FB. These
values are stored in the instance DB after the FB finishes.
Easy Book
86 Manual, 04/2012, A5E02486774-05
You can assign start values to the parameters in the FB interface. These values are
transferred to the associated instance DB. If you do not assign parameters, the values
currently stored in the instance DB will be used. In some cases, you must assign
parameters.
You can associate different instance DBs with different calls of the FB. The instance DBs
allow you to use one generic FB to control multiple devices. You structure your program by
having one code block make a call to an FB and an instance DB. The CPU then executes
the program code in that FB and stores the block parameters and the static local data in the
instance DB. When the execution of the FB finishes, the CPU returns to the code block that
called the FB. The instance DB retains the values for that instance of the FB. By designing
the FB for generic control tasks, you can reuse the FB for multiple devices by selecting
different instance DBs for different calls of the FB.
The following figure shows an OB that calls one FB three times, using a different data block
for each call. This structure allows one generic FB to control several similar devices, such as
motors, by assigning a different instance data block for each call for the different devices.
'%
2%
)%
'%
)%'%
)%'%
)%'%
'%
Each instance DB stores the data (such as speed, ramp-up time, and total operating time)
for an individual device. In this example, FB 22 controls three separate devices, with DB 201
storing the operational data for the first device, DB 202 storing the operational data for the
second device, and DB 203 storing the operational data for the third device.
6.1.3 Data blocks provide easy storage for program data

You create data blocks (DB) in your user program to store data for the code blocks. All of the
program blocks in the user program can access the data in a global DB, but an instance DB
stores data for a specific function block (FB).
Your user program can store data in the specialized memory areas of the CPU, such as for
the inputs (I), outputs (Q), and bit memory (M). In addition, you can use a data block (DB) for
fast access to data stored within the program itself.
Easy Book
Manual, 04/2012, A5E02486774-05 87
The data stored in a DB is not deleted when the data block is closed or the execution of the
associated code block comes to an end. There are two types of DBs:
A global DB stores data for the code blocks in your program. Any OB, FB, or FC can
access the data in a global DB.
An instance DB stores the data for a specific FB. The structure of the data in an instance
DB reflects the parameters (Input, Output, and InOut) and the static data for the FB. The
Temp memory for the FB is not stored in the instance DB.
Although the instance DB reflects the data for a specific FB, any code block can access the
data in an instance DB.
6.1.4 Creating a new code block
1. Open "Program blocks" folder.

2. Double-click "Add new block".
3. In the "Add new block" dialog,
click the type of block to add.
For example, click the
"Function (FC)" icon to add an
FC.
4. Specify the programming
language for the code block by
selecting "LAD" from the drop-
down menu.
5. Click "OK" to add the block to
the project.
Selecting the "Add new and open" option (default) opens the code block in the Project view.
6.1.5 Calling a code block from another code block
You can easily have any code block (OB,

FB, or FC) in your user program call an FB
or FC in your CPU.
1. Open the code block that will call the other block.
Easy Book
88 Manual, 04/2012, A5E02486774-05
6.2 Easy-to-use programming languages
2. In the project tree, select the code block to be called.

3. Drag the block to the selected network to create a Call instruction.
Note
Your user program cannot call an OB because OBs are event-driven (Page 52). The CPU
starts the execution of the OB in response to receiving an event.

STEP 7 provides the following standard programming languages for S7-1200:
LAD (ladder logic) is a graphical programming language. The representation is based on
circuit diagrams.
FBD (Function Block Diagram) is a programming language that is based on the graphical
logic symbols used in Boolean algebra.
SCL (structured control language) is a text-based, high-level programming language.
When you create a code block, you select the programming language to be used by that
block.
Your user program can utilize code blocks created in any or all of the programming
languages.
6.2.1 Ladder logic (LAD)

The elements of a circuit diagram, such as normally closed and normally open contacts, and
coils are linked to form networks.
To create the logic for complex operations, you can insert branches to create the logic for
parallel circuits. Parallel branches are opened downwards or are connected directly to the
power rail. You terminate the branches upwards.
LAD provides "box" instructions for a variety of functions, such as math, timer, counter, and
move.
STEP 7 does not limit the number of instructions (rows and columns) in a LAD network.
Note
Every LAD network must terminate with a coil or a box instruction.
Easy Book
Manual, 04/2012, A5E02486774-05 89
Consider the following rules when creating a LAD network:

You cannot create a branch that could result in a power flow in the reverse direction.
$ % & ' =
( )
+ *
You cannot create a branch that would cause a short circuit.

$ % & =
6.2.2 Function Block Diagram (FBD)

Like LAD, FBD is also a graphical programming language. The representation of the logic is
based on the graphical logic symbols used in Boolean algebra.
To create the logic for complex operations,

insert parallel branches between the boxes.
Mathematical functions and other complex functions can be represented directly in

conjunction with the logic boxes.
STEP 7 does not limit the number of instructions (rows and columns) in an FBD network.
6.2.3 SCL overview

Structured Control Language (SCL) is a high-level, PASCAL-based programming language
for the SIMATIC S7 CPUs. SCL supports the block structure of STEP 7. You can also
include program blocks written in SCL with program blocks written in LAD and FBD.
SCL instructions use standard programming operators, such as for assignment (:=),
mathematical functions (+ for addition, - for subtraction, * for multiplication, and / for division).
SCL uses standard PASCAL program control operations, such as IF-THEN-ELSE, CASE,
REPEAT-UNTIL, GOTO and RETURN. You can use any PASCAL reference for syntactical
elements of the SCL programming language. Many of the other instructions for SCL, such as
timers and counters, match the LAD and FBD instructions.
Easy Book
90 Manual, 04/2012, A5E02486774-05
Because SCL, like PASCAL, offers conditional processing, looping, and nesting control
structures, you can implement complex algorithms in SCL more easily than in LAD or FBD.
The following examples show different expressions for different uses:

"C" := #A+#B; Assigns two local variables to a tag
"Data_block_1".Tag := #A; Assignment to a data block tag
IF #A > #B THEN "C" := #A; Condition for the IF-THEN statement
"C" := SQRT (SQR (#A) + SQR (#B)); Parameters for the SQRT instruction
As a high-level programming language, SCL uses standard statements for basic tasks:
Assignment statement: :=
Mathematical functions: +, -, *, and /
Addressing of global variables (tags): "<tag name>" (Tag name or data block name
enclosed in double quotes)
Addressing of local variables: #<variable name> (Variable name preceded by "#" symbol)
Arithmetic operators can process various numeric data types. The data type of the result is
determined by the data type of the most-significant operands. For example, a multiplication
operation that uses an INT operand and a REAL operand yields a REAL value for the result.
6.2.4 SCL program editor

You can designate any type of block (OB, FB, or FC) to use the SCL programming language
at the time you create the block. STEP 7 provides an SCL program editor that includes the
following elements:
Interface section for defining the parameters of the code block
Code section for the program code
Instruction tree that contains the SCL instructions supported by the CPU
You enter the SCL code for your instruction directly in the code section. For more complex
instructions, simply drag the SCL instructions from the instruction tree and drop them into
your program. You can also use any text editor to create an SCL program and then import
that file into STEP 7.
Easy Book
Manual, 04/2012, A5E02486774-05 91
In the section of the SCL code block you can declare the following types of parameters:
Input, Output, InOut, and Ret_Val: These parameters define the input tags, output tags,
and return value for the code block. The tag name that you enter here is used locally
during the execution of the code block. You typically would not use the global tag name in
the tag table.
Static (FBs only; the illustration above is for an FC): Static tags are used for storage of
static intermediate results in the instance data block. Static data is retained until
overwritten, which may be after several cycles. The names of the blocks, which are called
in this code block as multi-instance, are also stored in the static local data.
Temp: These parameters are the temporary tags that are used during the execution of
the code block.
If you call the SCL code block from another code block, the parameters of the SCL code
block appear as inputs or outputs.
In this example, the tags for "Start" and "On" (from the project tag table) correspond to
"StartStopSwitch" and "RunYesNo" in the declaration table of the SCL program.
Easy Book
92 Manual, 04/2012, A5E02486774-05
6.3 Powerful instructions make programming easy
6.3.1 Providing the basic instructions you expect
Bit logic instructions

The basis of bit logic instruction is contacts and coils. Contacts read the status of a bit, while
the coils write the status of the operation to a bit.
Contacts test the binary status of

the bit, with the result being "power
flow" if on (1) or "no power flow" if
off (0).
The state of the coil reflects the
status of the preceding logic.
If you use a coil with the same address in more than one program location, the result of the
last calculation in the user program determines the status of the value that is written to the
physical output during the updating of the outputs.
Normally Open Normally Closed The Normally Open contact is closed (ON) when
Contact Contact the assigned bit value is equal to 1.
The Normally Closed contact is closed (ON) when
the assigned bit value is equal to 0.
The basic structure of a bit logic operation is either AND logic or OR logic. Contacts
connected in series create AND logic networks. Contacts connected in parallel create OR
logic networks.
You can connect contacts to other contacts and create your own combination logic. If the
input bit you specify uses memory identifier I (input) or Q (output), then the bit value is read
from the process-image register. The physical contact signals in your control process are
wired to input terminals on the PLC. The CPU scans the wired input signals and updates the
corresponding state values in the process-image input register.
You can specify an immediate read of a physical input using ":P" following the tag for an
input (such as "Motor_Start:P" or "I3.4:P"). For an immediate read, the bit data values are
read directly from the physical input instead of the process image. An immediate read does
not update the process image.
Easy Book
Manual, 04/2012, A5E02486774-05 93
Output coil Inverted output coil
If there is power flow through an output coil, then the output bit is set to 1.
If there is no power flow through an output coil, then the output coil bit is set to 0.
If there is power flow through an inverted output coil, then the output bit is set to 0.
If there is no power flow through an inverted output coil, then the output bit is set to 1.
The coil output instruction writes a value for an output bit. If the output bit you specify uses
memory identifier Q, then the CPU turns the output bit in the process-image register on or
off, setting the specified bit equal to power flow status. The output signals for your control
actuators are wired to the output terminals on the PLC. In RUN mode, the CPU system
scans your input signals, processes the input states according to your program logic, and
then reacts by setting new output state values in the process-image output register. After
each program execution cycle, the CPU transfers the new output state reaction stored in the
process-image register to the wired output terminals.
You can specify an immediate write of a physical output using ":P" following the tag for an
output (such as "Motor_On:P" or "Q3.4:P"). For an immediate write, the bit data values are
written to the process image output and directly to the physical output.
Coils are not restricted to the end of a network. You can insert a coil in the middle of a rung
of the LAD network, in between contacts or other instructions.
NOT contact inverter AND box with one inverted AND box with inverted logic input and
(LAD) logic input (FBD) output (FBD)
The LAD NOT contact inverts the logical state of power flow input.
If there is no power flow into the NOT contact, then there is power flow out.
If there is power flow into the NOT contact, then there is no power flow out.
For FBD programming, you can drag the "Negate binary input" tool from the "Favorites"
toolbar or instruction tree and then drop it on an input or output to create a logic inverter on
that box connector.
AND box (FBD) OR box (FBD) XOR box (FBD)
Easy Book
94 Manual, 04/2012, A5E02486774-05
All inputs of an AND box must be TRUE for the output to be TRUE.
Any input of an OR box must be TRUE for the output to be TRUE.
An odd number of the inputs of an XOR box must be TRUE for the output to be TRUE.
In FBD programming, the contact networks of LAD are represented by AND (&), OR (>=1),
and exclusive OR (x) box networks where you can specify bit values for the box inputs and
outputs. You may also connect to other logic boxes and create your own logic combinations.
After the box is placed in your network, you can drag the "Insert binary input" tool from the
"Favorites" toolbar or instruction tree and then drop it onto the input side of the box to add
more inputs. You can also right-click on the box input connector and select "Insert input".
Box inputs and output can be connected to another logic box, or you can enter a bit address
or bit symbol name for an unconnected input. When the box instruction is executed, the
current input states are applied to the binary box logic and, if true, the box output will be true.
6.3.2 Compare and Move instructions

The Compare instructions perform a comparison of two values with the same data type.
Table 6- 1 Compare instructions
Instruction SCL Description

LAD: out := in1 = in2; Equals (==):The comparison is true if IN1 is equal to
out := in1 <> in2; IN2
out := in1 >= in2;
Not equal (<>):The comparison is true if IN1 is not
out := in1 <= in2;
equal to IN2
out := in1 > in2;
Greater than or equal to (>=):The comparison is true if
FBD: out := in1 < in2;
IN1 is greater than or equal to IN2
Less than or equal to (<=):The comparison is true if
IN1 is less than or equal to IN2
Greater than (>):The comparison is true if IN1 is
greater than IN2
Less than (<):The comparison is true if IN1 is less
than IN2
1 For LAD and FBD: The contact is activated (LAD) or the box output is TRUE (FBD) if the comparison is TRUE,
The Move instructions copy data elements to a new memory address and can convert from
one data type to another. The source data is not changed by the move process.
MOVE copies a data element stored at a specified address to a new address. To add
another output, click the icon next to the OUT1 parameter.
MOVE_BLK (interruptible move) and UMOVE_BLK (uninterruptible move) copy a block of
data elements to a new address. The MOVE_BLK and UMOVE_BLK instructions have an
additional COUNT parameter. The COUNT specifies how many data elements are
copied. The number of bytes per element copied depends on the data type assigned to
the IN and OUT parameter tag names in the PLC tag table.
Easy Book
Manual, 04/2012, A5E02486774-05 95
Table 6- 2 MOVE, MOVE_BLK and UMOVE_BLK instructions
LAD / FBD SCL Description

out1 := in; Copies a data element stored at a specified
address to a new address or multiple
addresses. To add another output in LAD or
FBD, click the icon by the output parameter.
For SCL, use multiple assignment statements.
You might also use one of the loop
constructions.
MOVE_BLK(in:=_variant_in, Interruptible move that copies a block of data
count:=_uint_in, elements to a new address.
out=>_variant_out);
UMOVE_BLK(in:=_variant_in, Uninterruptible move that copies a block of

count:=_uint_in data elements to a new address.
out=>_variant_out);
6.3.3 Conversion instructions
Table 6- 3 Conversion instructions

out := <data type in>_TO_<data type Converts a data element from one data type to
out>(in); another data type.
1 For LAD and FBD: Click below the box name and select the data types from the drop-down menu. After you select the
(convert from) data type, a list of possible conversions is shown in the (convert to) dropdown list.
2 For SCL: Construct the conversion instruction by identifying the data type for the input parameter (in) and output
parameter (out). For example, DWORD_TO_REAL converts a DWord value to an Real value.
Easy Book
96 Manual, 04/2012, A5E02486774-05
Table 6- 4 Round and Truncate instructions

out := ROUND (in); Converts a real number (Real or LReal) to an integer. The real number
fraction is rounded to the nearest integer value (IEEE - round to
nearest). If the number is exactly one-half the span between two
integers (for example, 10.5), then the number is rounded to the even
integer. For example:
ROUND (10.5) = 10
ROUND (11.5) = 12
out := TRUNC(in); Converts a real number (Real or LReal) to an integer. The fractional
part of the real number is truncated to zero (IEEE - round to zero).
Table 6- 5 Ceiling (CEIL) and Floor instructions

out := CEIL(in); Converts a real number (Real or LReal) to the closest integer greater
than or equal to the selected real number (IEEE "round to +infinity").
out := FLOOR(in); Converts a real number (Real or LReal) to the closest integer smaller
than or equal to the selected real number (IEEE "round to -infinity").
Table 6- 6 SCALE_X and NORM_X instructions

out := SCALE_X( Scales the normalized real parameter VALUE where ( 0.0
min,:=_undef_in_ <= VALUE <= 1.0 ) in the data type and value range
value:=_real_in_, specified by the MIN and MAX parameters:
max:=undef_in_); OUT = VALUE (MAX - MIN) + MIN
out := NORM_X( Normalizes the parameter VALUE inside the value range
min:=_,undef_in_ specified by the MIN and MAX parameters:
value:=_undef_in_, OUT = (VALUE - MIN) / (MAX - MIN),
max:=_undef_in_); where ( 0.0 <= OUT <= 1.0 )
1 Equivalent SCL: out := value (max-min) + min;2 Equivalent SCL: out := (value-min)/(max-min);
Easy Book
Manual, 04/2012, A5E02486774-05 97
6.3.4 Math made easy with the Calculate instruction
Table 6- 7 CALCULATE instruction

Use the The CALCULATE instruction lets you create a math function that
standard SCL operates on inputs (IN1, IN2, .. INn) and produces the result at OUT,
math according to the equation that you define.
expressions to
Select a data type first. All inputs and the output must be the same
create the
data type.
equation.
To add another input, click the icon at the last input.
Table 6- 8 Data types for the parameters
Parameter Data type1

IN1, IN2, ..INn SInt, Int, DInt, USInt, UInt, UDInt, Real, LReal, Byte, Word, DWord
OUT SInt, Int, DInt, USInt, UInt, UDInt, Real, LReal, Byte, Word, DWord
1 The IN and OUT parameters must be the same data type (with implicit conversions of the input parameters). For
example: A SINT value for an input would be converted to an INT or a REAL value if OUT is an INT or REAL
Click the calculator icon to open the dialog and define your math function. You enter your
equation as inputs (such as IN1 and IN2) and operations. When you click "OK" to save the
function, the dialog automatically creates the inputs for the CALCULATE instruction.
An example and a list of possible math operations you can include is shown at the bottom of
the editor.
Note
You also must create an input for any constants in your function. The constant value would
then be entered in the associated input for the CALCULATE instruction.
By entering constants as inputs, you can copy the CALCULATE instruction to other locations
in your user program without having to change the function. You then can change the values
or tags of the inputs for the instruction without modifying the function.
When CALCULATE is executed and all the individual operations in the calculation complete
successfully, then the ENO = 1. Otherwise, ENO = 0.
Easy Book
98 Manual, 04/2012, A5E02486774-05
6.3.5 Timers
The S7-1200 supports the following timers

The TP timer generates a pulse with a preset width time.
The TON timer sets the output (Q) to ON after a preset time delay.
The TOF timer sets the output (Q) to ON and then resets the output to OFF after a preset
time delay.
The TONR timer sets the output (Q) to ON after a preset time delay. The elapsed time is
accumulated over multiple timing periods until the reset (R) input is used to reset the
elapsed time.
For LAD and FBD, these instructions are available as either a box instruction or an output
coil. STEP 7 also provides the following timer coils for LAD and FBD:
The PT (preset timer) coil loads a new preset time value in the specified timer.
The RT (reset timer) coil resets the specified timer.
The number of timers that you can use in your user program is limited only by the amount of
memory in the CPU. Each timer uses 16 bytes of memory.
Each timer uses a structure stored in a data block to maintain timer data. For SCL, you must
first create the DB for the individual timer instruction before you can reference it. For LAD
and FBD, STEP 7 automatically creates the DB when you insert the instruction.
When you create the DB, you can also use a multi-instance DB. Because the timer data is
contained in a single DB and does not require a separate DB for each timer, the processing
time for handling the timers is reduced. There is no interaction between the timer data
structures in the shared multi-instance DB.
Table 6- 9 TP (Pulse timer)
LAD / FBD SCL Timing diagram

"timer_db".TP( ,1
IN:=_bool_in_,
PT:=_undef_in_,
Q=>_bool_out_,
(7
ET=>_undef_out_); 37
37 37 37
Easy Book
Manual, 04/2012, A5E02486774-05 99
Table 6- 10 TON (ON-delay timer)

"timer_db".TON( ,1
IN:=_bool_in_,
PT:=_undef_in_,
Q=>_bool_out_, (7
4 37 37
Table 6- 11 TOF (OFF-delay timer)

"timer_db".TOF(
,1
IN:=_bool_in_,
PT:=_undef_in_,
Q=>_bool_out_,
(7
4
37 37
Table 6- 12 TONR (ON-delay Retentive timer)

"timer_db".TONR(
,1
IN:=_bool_in_,
R:=_bool_in_
PT:=_undef_in_,
(7 37
Q=>_bool_out_,
ET=>_undef_out_);
Easy Book
100 Manual, 04/2012, A5E02486774-05
Table 6- 13 Preset timer -(PT)- and Reset timer -(RT)- coil instructions
LAD Description
Use the Preset timer -(PT)- and Reset timer -(RT)- coil instructions with either box or coil timers. These
coil instructions can be placed in a mid-line position. The coil output power flow status is always the same
as the coil input status.
When the -(PT)- coil is activated, the PRESET time element of the specified IEC_Timer DB data is
reset to 0.
When the -(RT)- coil is activated, the ELAPSED time element of the specified IEC_Timer DB data is
reset to 0.
Parameter Data type Description

Box: IN Bool TP, TON, and TONR:
Coil: Power flow Box: 0=Disable timer, 1=Enable timer
Coil: No power flow=Disable timer, Power flow=Enable timer
TOF:
Box: 0=Enable timer, 1=Disable timer
Coil: No power flow=Enable timer, Power flow=Disable timer
R Bool TONR box only:
0=No reset
1= Reset elapsed time and Q bit to 0
Box: PT Time Timer box or coil: Preset time input
Coil: "PRESET_Tag"
Box: Q Bool Timer box: Q box output or Q bit in the timer DB data
Coil: DBdata.Q Timer coil: you can only address the Q bit in the timer DB data
Box: ET Time Timer box: ET (elapsed time) box output or ET time value in the timer DB
Coil: DBdata.ET data
Timer coil: you can only address the ET time value in the timer DB data.
Table 6- 15 Effect of value changes in the PT and IN parameters
Timer Changes in the PT and IN box parameters and the corresponding coil parameters
TP Changing PT has no effect while the timer runs.
Changing IN has no effect while the timer runs.
TON Changing PT has no effect while the timer runs.
Changing IN to FALSE, while the timer runs, resets and stops the timer.
TOF Changing PT has no effect while the timer runs.
Changing IN to TRUE, while the timer runs, resets and stops the timer.
TONR Changing PT has no effect while the timer runs, but has an effect when the timer resumes.
Changing IN to FALSE, while the timer runs, stops the timer but does not reset the timer. Changing IN
back to TRUE will cause the timer to start timing from the accumulated time value.
Easy Book
Manual, 04/2012, A5E02486774-05 101
PT (preset time) and ET (elapsed time) values are stored in the specified IEC_TIMER DB
data as signed double integers that represent milliseconds of time. TIME data uses the T#
identifier and can be entered as a simple time unit (T#200ms or 200) and as compound time
units like T#2s_200ms.
Table 6- 16 Size and range of the TIME data type
Data type Size Valid number ranges1

TIME 32 bits, stored as T#-24d_20h_31m_23s_648ms to T#24d_20h_31m_23s_647ms
DInt data Stored as -2,147,483,648 ms to +2,147,483,647 ms
1 The negative range of the TIMEdata type shown above cannot be used with the timer instructions. Negative PT(preset
time) values are set to zero when the timer instruction is executed. ET(elapsed time) is always a positive value.
Timer programming
The following consequences of timer operation should be considered when planning and
creating your user program:
You can have multiple updates of a timer in the same scan. The timer is updated each
time the timer instruction (TP, TON, TOF, TONR) is executed and each time the
ELAPSED or Q member of the timer structure is used as a parameter of another
executed instruction. This is an advantage if you want the latest time data (essentially an
immediate read of the timer). However, if you desire to have consistent values throughout
a program scan, then place your timer instruction prior to all other instructions that need
these values, and use tags from the Q and ET outputs of the timer instruction instead of
the ELAPSED and Q members of the timer DB structure.
You can have scans during which no update of a timer occurs. It is possible to start your
timer in a function, and then cease to call that function again for one or more scans. If no
other instructions are executed which reference the ELAPSED or Q members of the timer
structure, then the timer will not be updated. A new update will not occur until either the
timer instruction is executed again or some other instruction is executed using ELAPSED
or Q from the timer structure as a parameter.
Although not typical, you can assign the same DB timer structure to multiple timer
instructions. In general, to avoid unexpected interaction, you should only use one timer
instruction (TP, TON, TOF, TONR) per DB timer structure.
Easy Book
102 Manual, 04/2012, A5E02486774-05
Self-resetting timers are useful to trigger actions that need to occur periodically. Typically,
self-resetting timers are created by placing a normally-closed contact which references the
timer bit in front of the timer instruction. This timer network is typically located above one or
more dependent networks that use the timer bit to trigger actions. When the timer expires
(elapsed time reaches preset value), the timer bit is ON for one scan, allowing the dependent
network logic controlled by the timer bit to execute. Upon the next execution of the timer
network, the normally closed contact is OFF, thus resetting the timer and clearing the timer
bit. The next scan, the normally closed contact is ON, thus restarting the timer. When
creating self-resetting timers such as this, do not use the "Q" member of the timer DB
structure as the parameter for the normally-closed contact in front of the timer instruction.
Instead, use the tag connected to the "Q" output of the timer instruction for this purpose. The
reason to avoid accessing the Q member of the timer DB structure is because this causes an
update to the timer and if the timer is updated due to the normally closed contact, then the
contact will reset the timer instruction immediately. The Q output of the timer instruction will
not be ON for the one scan and the dependent networks will not execute.
The -(TP)-, -(TON)-, -(TOF)-, and -(TONR)- timer coils must be the last instruction in a
network. As shown in the timer example, a contact instruction in a subsequent network
evaluates the Q bit in a timer coil's IEC_Timer DB data. Likewise, you must address the
ELAPSED element in the IEC_timer DB data if you want to use the elapsed time value in
your program.
The pulse timer is started on a 0 to 1 transition of the Tag_Input bit value. The timer runs for
the time specified by Tag_Time time value.
As long as the timer runs, the state of DB1.MyIEC_Timer.Q=1 and the Tag_Output value=1.
When the Tag_Time value has elapsed, then DB1.MyIEC_Timer.Q=0 and the Tag_Output
value=0.
6.3.6 Counters
You use the counter instructions to count internal program events and external process
events.
The "count up" counter (CTU) counts up by 1 when the value of the input parameter CU
changes from 0 to 1.
The "count down" counter (CTD) counts down by 1 when the value of input parameter CD
changes from 0 to 1.
The "count up and down" counter (CTUD) counts up or down by 1 on the 0 to 1 transition
of the count up (CU) or count down (CD) inputs.
S7-1200 also provides high-speed counters (Page 111) (HSC) for counting events that occur
faster than the OB execution rate.
Easy Book
Manual, 04/2012, A5E02486774-05 103
The CU, CD, and CTUD instructions use software counters whose maximum counting rate is
limited by the execution rate of the OB they are placed in.
Note
If the events to be counted occur within the execution rate of the OB, use CTU, CTD, or
CTUD counter instructions. If the events occur faster than the OB execution rate, then use
the HSC.
Each counter uses a structure stored in a data block to maintain counter data. For SCL, you
must first create the DB for the individual counter instruction before you can reference it. For
LAD and FBD, STEP 7 automatically creates the DB when you insert the instruction.
The number of counters that you can use in your user program is limited only by the amount
of memory in the CPU. Individual counters use 3 bytes (for SInt or USInt), 6 bytes (for Int or
UInt), or 12 bytes(for DInt or UDInt).
Table 6- 17 CTU (count up) counter
LAD / FBD SCL Operation

"ctu_db".CTU(
CU:=_bool_in, &8
R:=_bool_in,
PV:=_undef_in, 5
Q=>_bool_out,
CV=>_undef_out);

&9
The timing diagram shows the operation of a CTU counter with an unsigned integer count
value (where PV = 3).
If the value of parameter CV (current count value) is greater than or equal to the value of
parameter PV (preset count value), then the counter output parameter Q = 1.
If the value of the reset parameter R changes from 0 to 1, then CV is reset to 0.
Table 6- 18 CTD (count down) counter

"ctd_db".CTU(
CD:=_bool_in, &'
LOAD:=_bool_in,
/2$'
PV:=_undef_in,
Q=>_bool_out,

CV=>_undef_out);
&9
Easy Book
104 Manual, 04/2012, A5E02486774-05
The timing diagram shows the operation of a CTD counter with an unsigned integer count
If the value of parameter CV (current count value) is equal to or less than 0, the counter
output parameter Q = 1.
If the value of parameter LOAD changes from 0 to 1, the value at parameter PV (preset
value) is loaded to the counter as the new CV.
Table 6- 19 CTUD (count up and down) counter

"ctud_db".CTUD(
&8
CU:=_bool_in,
CD:=_bool_in, &'
R:=_bool_in, 5
LOAD:=_bool_in,
PV:=_undef_in, /2$'

QU=>_bool_out,

QD=>_bool_out,

CV=>_undef_out); &9
48
4'
The timing diagram shows the operation of a CTUD counter with an unsigned integer count
If the value of parameter CV (current count value) is equal to or greater than the value of
parameter PV (preset value), then the counter output parameter QU = 1.
If the value of parameter CV is less than or equal to zero, then the counter output
parameter QD = 1.
If the value of parameter LOAD changes from 0 to 1, then the value at parameter PV is
loaded to the counter as the new CV.
If the value of the reset parameter R is changes from 0 to 1, CV is reset to 0.
6.3.7 Pulse-width modulation (PWM)
Table 6- 20 CTRL_PWM instruction
LAD / FBD SCL Desciption

"ctrl_pwm_db"( The CTRL_PWM instruction provides a fixed cycle
PWM:=_hw_pwm_in_, time output with a variable duty cycle. The PWM
enable:=_bool_in_, output runs continuously after being started at the
busy=>_bool_out_, specified frequency (cycle time). The pulse width is
status=>_word_out_); varied as required to affect the desired control.
Easy Book
Manual, 04/2012, A5E02486774-05 105
6.4 Easy to create data logs
The CTRL_PWM instruction stores the parameter information in the DB. For SCL, you must
first create the DB for the instruction before you can reference it. For LAD and FBD, STEP 7
automatically creates the DB when you insert the instruction. The data block parameters are
controlled by the CTRL_PWM instruction.
The pulse width will be set to the initial value configured in device configuration when the
CPU first enters the RUN mode. You write values to the word-length output (Q) address that
was specified in device configuration ("Output addresses" / "Start address") as needed to
change the pulse width. Use an instruction (such as Move, Convert, Math, or PID) to write
the specified pulse width to the appropriate word-length output (Q). You must use the valid
range for the output value (percent, thousandths, ten-thousandths, or S7 analog format).
Duty cycle can be expressed, for example, as a

percentage of the cycle time or as a relative quantity
(such as 0 to 1000 or 0 to 10000). The pulse width can
vary from 0 (no pulse, always off) to full scale (no
pulse, always on).
Cycle time
Pulse width time
The PWM output can be varied from 0 to full scale, providing a digital output that in many
ways is the same as an analog output. For example, the PWM output can be used to control
the speed of a motor from stop to full speed, or it can be used to control position of a valve
from closed to fully opened.

Your control program can use the Data log instructions to store run-time data values in
persistent log files. The data log files are stored in flash memory (CPU or memory card). Log
file data is stored in standard CSV (Comma Separated Value) format. The data records are
organized as a circular log file of a pre-determined size.
The Data log instructions are used in your program to create, open, write a record, and close
the log files. You decide which program values will be logged by creating a data buffer that
defines a single log record. Your data buffer is used as temporary storage for a new log
record. New current values must be programmatically moved into the buffer during run-time.
When all of the current data values are updated, you can execute the DataLogWrite
instruction to transfer data from the buffer to a data log record.
Use the built-in PLC Web server to manage your data log files. Download recent records, all
records, clear records, or delete log files with the "Data Logs" standard web page. After a
data log file is transferred to your PC, then you can analyze the data with standard
spreadsheet tools like Excel.
Easy Book
106 Manual, 04/2012, A5E02486774-05
Use the DataLog instructions to programmatically store run-time process data in flash
memory of the CPU. The data records are organized as a circular log file of a pre-
determined size. New records are appended to the data log file. After the data log file has
stored the maximum number of records, the next record written overwrites the oldest record.
To prevent overwriting any data records, use the DataLogNewFile instruction. New data
records are stored in the new data log file, while the old data log file remains in the CPU.
Table 6- 21 DataLogWrite instruction
LAD/FBD SCL Description

"DataLogWrite_DB"( DataLogWrite writes a data record into the specified data log.
req:=_bool_in_, The pre-existing target data log must be open.
done=>_bool_out_, You must programmatically load the record buffer with current
busy=>_bool_out_, run-time data values and then execute the DataLogWrite
error=>_bool_out_, instruction to move new record data from the buffer to the data
status=>_word_out_, log.
ID:=_dword_inout_); If there is a power failure during an incomplete DataLogWrite
operation, then the data record being transferred to the data log
could be lost.
Table 6- 22 DataLogCreate and DataLogNewFile instructions

"DataLogCreate_DB"( DataLogCreate1 creates and initializes a
req:=_bool_in_, data log file stored in the \DataLogs
records:=_udint_in_, directory of the CPU. The data log file is
format:=_uint_in_, created with a pre-determined fixed size.
timestamp:=_uint_in_,
done=>_bool_out_,
busy=>_bool_out_,
error=>_bool_out_,
status=>_word_out_,
name:=_string_inout_,
ID:=_dword_inout_,
header:=_variant_inout_,
data:=_variant_inout_);
"DataLogNewFile_DB"( DataLogNewFile1 allows your program to
req:=_bool_in_, create a new data log file based upon an
records=:_udint_in_, existing data log file. A new data log will be
done=>_bool_out_, created and implicitly opened based with
busy=>_bool_out_, the specified NAME. The header record will
error=>_bool_out_, be duplicated from the original data log
along with the original data log properties.
status=>_word_out_,
The original data log file will be implicitly
name=:_DataLog_out_,
closed.
ID:=_dword_inout_);
1 The DataLogCreate and DataLogNewFile operations extend over many program scan cycles. The actual time required
for the log file creation depends on the record structure and number of records. Before the new data log can be used for
other data log operations, your program logic must monitor the transition of the DONE bit to TRUE.
Easy Book
Manual, 04/2012, A5E02486774-05 107
6.5 Easy to monitor and test your user program
Table 6- 23 DataLogOpen and DataLogClose instructions

"DataLogOpen_DB"( The DataLogOpen instruction opens a pre-existing data log
req:=_bool_in_, file. A data log must be opened before you can write new
mode:=_uint_in_, records to the log. Data logs can be opened and closed
done=>_bool_out_, individually. Eight data logs can be open at the same time.
busy=>_bool_out_,
error=>_bool_out_,
status=>_word_out_,
name:=_string_inout_,
ID:=_dword_inout_);
"DataLogClose_DB"( The DataLogClose instruction closes an open data log file.
req:=_bool_in_, DataLogWrite operations to a closed data log result in an error.
done=>_bool_out_, No write operations are allowed to this data log until another
busy=>_bool_out_, DataLogOpen operation is performed.
error=>_bool_out_, A transition to STOP mode closes all open data log files.
status=>_word_out_,
ID:=_dword_inout_);
6.5.1 Watch tables and force tables

You use "watch tables" for monitoring and modifying the values of a user program being
executed by the online CPU. You can create and save different watch tables in your project
to support a variety of test environments. This allows you to reproduce tests during
commissioning or for service and maintenance purposes.
With a watch table, you can monitor and interact with the CPU as it executes the user
program. You can display or change values not only for the tags of the code blocks and data
blocks, but also for the memory areas of the CPU, including the inputs and outputs (I and Q),
peripheral inputs (I:P), bit memory (M), and data blocks (DB).
With the watch table, you can enable the physical outputs (Q:P) of a CPU in STOP mode.
For example, you can assign specific values to the outputs when testing the wiring for the
CPU.
STEP 7 also provides a force table for "forcing" a tag to a specific value. For more
information about forcing, see the section on forcing values in the CPU (Page 227) in the
"Online and Diagnostics" chapter.
Note
The force values are stored in the CPU and not in the watch table.
You cannot force an input (or "I" address). However, you can force a peripheral input. To
force a peripheral input, append a ":P" to the address (for example: "On:P").
Easy Book
108 Manual, 04/2012, A5E02486774-05
6.5.2 Cross reference to show usage

The Inspector window displays cross-reference information about how a selected object is
used throughout the complete project, such as the user program, the CPU and any HMI
devices. The "Cross-reference" tab displays the instances where a selected object is being
used and the other objects using it. The Inspector window also includes blocks which are
only available online in the cross-references. To display the cross-references, select the
"Show cross-references" command. (In the Project view, find the cross references in the
"Tools" menu.)
Note
You do not have to close the editor to see the cross-reference information.
You can sort the entries in the cross-reference. The cross-reference list provides an
overview of the use of memory addresses and tags within the user program.
When creating and changing a program, you retain an overview of the operands, tags
and block calls you have used.
From the cross-references, you can jump directly to the point of use of operands and
tags.
During a program test or when troubleshooting, you are notified about which memory
location is being processed by which command in which block, which tag is being used in
which screen, and which block is called by which other block.
Table 6- 24 Elements of the cross reference
Column Description
Object Name of the object that uses the lower-level objects or that is being used by the
lower-level objects
Quantity Number of uses
Location Each location of use, for example, network
Property Special properties of referenced objects, for example, the tag names in multi-instance
declarations
as Shows additional information about the object, such as whether an instance DB is
used as template or as a multiple instance
Access Type of access, whether access to the operand is read access (R) and/or write
access (W)
Address Address of the operand
Type Information on the type and language used to create the object
Path Path of object in project tree
6.5.3 Call structure to examine the calling hierarchy

The call structure describes the call hierarchy of the block within your user program. It
provides an overview of the blocks used, calls to other blocks, the relationships between
blocks, the data requirements for each block, and the status of the blocks. You can open the
program editor and edit blocks from the call structure.
Easy Book
Manual, 04/2012, A5E02486774-05 109
Displaying the call structure provides you with a list of the blocks used in the user program.
STEP 7 highlights the first level of the call structure and displays any blocks that are not
called by any other block in the program. The first level of the call structure displays the OBs
and any FCs, FBs, and DBs that are not called by an OB. If a code block calls another block,
the called block is shown as an indentation under the calling block. The call structure only
displays those blocks that are called by a code block.
You can selectively display only the blocks causing conflicts within the call structure. The
following conditions cause conflicts:
Blocks that execute any calls with older or newer code time stamps
Blocks that call a block with modified interface
Blocks that use a tag with modified address and/or data type
Blocks that are called neither directly nor indirectly by an OB
Blocks that call a non-existent or missing block
You can group several block calls and data blocks as a group. You use a drop-down list to
see the links to the various call locations.
You can also perform a consistency check to show time stamp conflicts. Changing the time
stamp of a block during or after the program is generated can lead to time stamp conflicts,
which in turn cause inconsistencies among the blocks that are calling and being called.
Most time stamp and interface conflicts can be corrected by recompiling the code blocks.
If compilation fails to clear up inconsistencies, use the link in the "Details" column to go to
the source of the problem in the program editor. You can then manually eliminate any
inconsistencies.
Any blocks marked in red must be recompiled.
6.5.4 Diagnostic instructions to monitor the hardware
6.5.4.1 Reading the states of the LEDs on the CPU

The LED instruction allows your user program to determine the state of the LEDs on the
CPU. You can use this information for programming a tag for your HMI device.
Table 6- 25 LED instruction

ret_val := #LED( RET_VAL returns the following LED states for the CPU
laddr:=_hw_io_in_,
RUN/STOP: green or red
LED:=_uint_in_);
Error: red
MAINT (maintenance): yellow
Link: green
Tx/Rx (transmit/receive): yellow
Easy Book
110 Manual, 04/2012, A5E02486774-05
6.6 High-speed counter (HSC)
6.5.4.2 Instructions for reading the diagnostic status of the devices

STEP 7 also includes instructions for reading the status information that is provided by the
hardware devices on your network.
Table 6- 26 Diagnostic instructions

ret_val := #GET_DIAG( The GET_DIAG instruction reads the diagnostic
mode:=_uint_in_, information from a specified hardware device.
laddr:=_hw_any_in_,
channel:=_uint_in_,
cnt_diag=>_uint_out_,
diag:=_uint_inout_,
detail:=_variant_inout_);
ret_val := DeviceStates( The DeviceStates instruction reads the status of
laddr:=hw_io_in_, the PROFINET IO or PROFIBUS DP devices.
mode:=_uint_in_,
state:=_variant_inout_);
ret_val := ModuleStates( The ModuleStates instruction reads the status of

laddr:=_hw_io_in_, the PROFINET IO devices.
mode:=_uint_in,
state:=_variant_inout);

Use the high-speed counters (HSC) for counting events that occur faster than the OB
execution rate. The CTRL_HSC instruction controls the operation of the HSC.
Note
If the events to be counted occur within the execution rate of the OB, use CTU, CTD, or
CTUD counter instructions. If the events occur faster than the OB execution rate, then use
the HSC.
You configure the parameters for each HSC in the device configuration for the CPU:
counting mode, I/O connections, interrupt assignment, and operation as a high-speed
counter or as a device to measure pulse frequency.
Easy Book
Manual, 04/2012, A5E02486774-05 111
Table 6- 27 CTRL_HSC instruction

"counter_name"( Each CTRL_HSC instruction uses a structure stored
hsc:=_hw_hsc_in_, in a DB to maintain data.
HSC:= , The HSC uses a structure stored in a data block to
DIR:=_bool_in_, maintain counter data. For SCL, you must first create
CV:=_bool_in_, the DB for the individual counter instruction before
RV:=_bool_in_, you can reference it. For LAD and FBD, STEP 7
Period:=_bool_in_, automatically creates the DB when you insert the
New_DIR:=_int_in_, instruction.
New_CV:=_int_in_,
New_RV:=_dint_in_,
New_Period:=_int_in_,
Busy:=_bool_out_,
Status:=_word_out_);
The CTRL_HSC instruction is typically placed in a hardware interrupt OB that is executed

when the counter hardware interrupt event is triggered. For example, if a CV=RV event
triggers the counter interrupt, then a hardware interrupt OB code block executes the
CTRL_HSC instruction and can change the reference value by loading a NEW_RV value.
Note
The current count value is not available in the CTRL_HSC parameters. The process image
address that stores the current count value is assigned during the hardware configuration of
the high-speed counter. You may use program logic to directly read the count value. The
value returned to your program will be a correct count for the instant in which the counter
was read. The counter will continue to count high-speed events. Therefore, the actual count
value could change before your program completes a process using an old count value.
Some of the parameters for the HSC can be modified by your user program to provide
program control of the counting process:
Set the counting direction to a NEW_DIR value
Set the current count value to a NEW_CV value
Set the reference value to a NEW_RV value
Set the period value (for frequency measurement mode) to a NEW_PERIOD value
If the following Boolean flag values are set to 1 when the CTRL_HSC instruction is executed,
the corresponding NEW_xxx value is loaded to the counter. Multiple requests (more than
one flag is set at the same time) are processed in a single execution of the CTRL_HSC
instruction.
Setting DIR = 1 loads a NEW_DIR value.
Setting CV = 1 loads a NEW_CV value.
Setting RV = 1 loads a NEW_RV value
Setting PERIOD = 1 loads a NEW_PERIOD value.
Easy Book
112 Manual, 04/2012, A5E02486774-05
6.6.1 Operation of the HSC

The high-speed counter (HSC) counts events that occur faster than the OB execution rate. If
the events to be counted occur within the execution rate of the OB, you can use CTU, CTD,
or CTUD counter instructions. If the events occur faster than the OB execution rate, then use
the HSC. The CTRL_HSC instruction allows your user program to programmatically change
some of the HSC parameters.
For example: You can use the HSC as an input for an incremental shaft encoder. The shaft
encoder provides a specified number of counts per revolution and a reset pulse that occurs
once per revolution. The clock(s) and the reset pulse from the shaft encoder provide the
inputs to the HSC.
The HSC is loaded by the user program with the first of several presets, and the outputs are
activated by the user program for the time period where the current count is less than the
current preset. The user program configures the HSC to provide an interrupt when the
counter value is equal to the reference value (or CV = RV), when a reset occurs, and also
when there is a direction change.
As each CV = RV interrupt event occurs, the user program loads a new reference value and
sets the next state for the outputs inside the CV = RV interrupt OB. When the reset interrupt
event occurs, the user program loads the first reference value and sets the first output states
in the reset-interrupt OB, and the cycle is repeated.
Since the interrupts occur at a much lower rate than the counting rate of the HSC, precise
control of high-speed operations can be implemented with relatively minor impact to the scan
cycle of the CPU. The method of interrupt attachment allows each load of a new preset to be
performed in a separate interrupt routine for easy state control. (Alternatively, all interrupt
events can be processed in a single interrupt routine.)
Table 6- 28 Maximum frequency (KHz)
HSC Single phase Two phase and

AB quadrature
HSC1 CPU 100 KHz 80 KHz
High-speed SB 200 KHz 160 KHz
SB 30 KHz 20 KHz
SB 30 KHz 20 KHz
SB 30 KHz 20 KHz
SB 30 KHz 20 KHz
Easy Book
Manual, 04/2012, A5E02486774-05 113
Selecting the functionality for the HSC

All HSCs function the same way for the same counter mode of operation. There are four
basic types of HSC:
Single-phase counter with internal direction control
Single-phase counter with external direction control
Two-phase counter with 2 clock inputs
A/B phase quadrature counter
You can use each HSC type with or without a reset input. When you activate the reset input
(with some restrictions, see the following table), the current value is cleared and held clear
until you deactivate the reset input.
Frequency function: Some HSC modes allow the HSC to be configured (Type of
counting) to report the frequency instead of a current count of pulses. Three different
frequency measuring periods are available: 0.01, 0.1, or 1.0 seconds.
The frequency measuring period determines how often the HSC calculates and reports a
new frequency value. The reported frequency is an average value determined by the total
number of counts in the last measuring period. If the frequency is rapidly changing, the
reported value will be an intermediate between the highest and lowest frequency
occurring during the measuring period. The frequency is always reported in Hertz (pulses
per second) regardless of the frequency-measuring-period setting.
Counter modes and inputs: The following table shows the inputs used for the clock,
direction control, and reset functions associated with the HSC.
The same input cannot be used for two different functions, but any input not being used
by the present mode of its HSC can be used for another purpose. For example, if HSC1
is in a mode that uses built-in inputs but does not use the external reset (I0.3), then I0.3
can be used for edge interrupts or for HSC2.
Table 6- 29 Counting modes for HSC
Type Input 1 Input 2 Input 3 Function

Single-phase counter with Clock (Optional: - Count or frequency
internal direction control direction) Reset Count
Single-phase counter with Clock Direction - Count or frequency
external direction control Reset Count
Two-phase counter with 2 Clock up Clock down - Count or frequency
clock inputs Reset Count
A/B-phase quadrature Phase A Phase B - Count or frequency
counter Phase Z Count
Easy Book
114 Manual, 04/2012, A5E02486774-05
Input addresses for the HSC
Note
The digital I/O points used by high-speed counter devices are assigned during device
configuration. When digital I/O point addresses are assigned to these devices, the values of
the assigned I/O point addresses cannot be modified by the force function in a watch table.
When you configure the CPU, you have the option to enable and configure each HSC. The
CPU automatically assigns the input addresses for each HSC according to its configuration.
(Some of the HSCs allow you to select whether to use either the on-board inputs of the CPU
or the inputs of an SB.)
NOTICE
As shown in the following tables, the default assignments for the optional signals for the
different HSCs overlap. For example, the optional external reset for HSC 1 uses the same
input as one of the inputs for HSC 2.
Always ensure that you have configured your HSCs so that any one input is not being used
by two HSCs.
For example, the following table shows the HSC input assignments for both the on-board I/O
of the CPU 1212C and an SB. (If the SB has only 2 inputs, only 4.0 and 4.1 inputs are
available.)
For single-phase: C is the Clock input, [d] is the optional direction input, and [R] is an
optional external reset input. (Reset is available only for "Counting" mode.)
For two-phase: CU is the Clock Up input, CD is the Clock Down input, and [R] is an
For AB-phase quadrature: A is the Clock A input, B is the Clock B input, and [R] is an
Table 6- 30 HSC input assignments for CPU 1212C
HSC CPU on-board input (0.x) SB input (4.x) 3

0 1 2 3 4 5 6 7 0 1 2 3
HSC 1 1 1-phase C [d] [R] C [d] [R]
2-phase CU CD [R] CU CD [R]
AB-phase A B [R] A B [R]
HSC 2 1 1-phase [R] C [d] [R] C [d]
2-phase [R] CU CD [R] CU CD
AB-phase [R] A B [R] A B
HSC 3 1-phase C [d] [R]
2-phase CU CD [R]
AB-phase A B [R]
HSC 4 1-phase [R] C [d]
2-phase [R] CU CD
Easy Book
Manual, 04/2012, A5E02486774-05 115
HSC CPU on-board input (0.x) SB input (4.x) 3

0 1 2 3 4 5 6 7 0 1 2 3
AB-phase [R] A B
HSC 5 2 1-phase C [d] [R]
2-phase CU CD [R]
AB-phase A B [R]
HSC 6 2 1-phase [R] C [d]
2-phase [R] CU CD
AB-phase [R] A B
1 HSC 1 and HSC 2 can be configured for either the on-board inputs or for an SB.
2 HSC 5 and HSC 6 are available only with an SB. HSC 6 is available only with a 4-input SB.
3 An SB with only 2 digital inputs provides only the 4.0 and 4.1 inputs.
Accessing the current value for the HSC

When you enable a pulse generator for use as a PTO, a corresponding HSC is assigned to
this PTO. HSC1 is assigned for PTO1, and HSC2 is assigned for PTO2. The assigned HSC
belongs completely to the PTO channel, and the ordinary output of the HSC is disabled. The
HSC value is only used for the internal functionality. You cannot monitor the current value
(for example, in ID1000) when pulses are occurring.
6.6.2 Configuration of the HSC
The CPU allows you to configure up to 6 high-speed

counters. You edit the "Properties" of the CPU to
configure the parameters of each individual HSC.
Use the CTRL_HSC instruction in your user program to
control the operation of the HSC.
Enable the specific HSC by selecting the "Enable" option
for that HSC.
Easy Book
116 Manual, 04/2012, A5E02486774-05
Note
When you enable the high speed counter and select input points for it, the input filter settings
for these points are configured to 800 ns. Each input point has a single filter configuration
that applies to all uses: process inputs, interrupts, pulse catch, and HSC inputs.
WARNING
If the filter time for a digital input channel is changed from a previous setting, a new "0"
level input value may need to be presented for up to 20.0 ms accumulated duration before
the filter becomes fully responsive to new inputs. During this time, short "0" pulse events of
duration less than 20.0 ms may not be detected or counted.
This changing of filter times can result in unexpected machine or process operation, which
may cause death or serious injury to personnel, and/or damage to equipment.
To ensure that a new filter time goes immediately into effect, a power cycle of the CPU
must be applied.
After enabling the HSC, configure the other parameters, such as counter function, initial
values, reset options and interrupt events.
For information about configuring the HSC, refer to the section on configuring the CPU
(Page 73).
Easy Book
Manual, 04/2012, A5E02486774-05 117
Easy Book
118 Manual, 04/2012, A5E02486774-05
Easy to communicate between devices 7
For a direct connection between the
programming device and a CPU:
The project must include the CPU.
The programming device is not part of the
project, but must be running STEP 7.
For a direct connection between an HMI

panel and a CPU, the project must include
both the CPU and the HMI.
For a direct connection between two CPUs:

The project must include both CPUs.
You must configure a network connection
between the two CPUs.
The S7-1200 CPU is a PROFINET IO controller and communicates with STEP 7 on a

programming device, with HMI devices, and with other CPUs or non-Siemens devices. An
Ethernet switch is not required for a direct connection between a programming device or HMI
and a CPU. An Ethernet switch is required for a network with more than two CPUs or HMI
devices.
By adding a PROFIBUS CM, your CPU can also function as either a master or a slave on a
PROFIBUS network.
Other communication interfaces (CM, CP or CB) support a variety of protocols, such as
Point-to-Point (PTP), Modbus, USS, and GPRS (modem).
Easy Book
Manual, 04/2012, A5E02486774-05 119
Easy to communicate between devices
7.1 Creating a network connection
7.1 Creating a network connection

Use the "Network view" of Device configuration to create the network connections between
the devices in your project. After creating the network connection, use the "Properties" tab of
the inspector window to configure the parameters of the network.
Table 7- 1 Creating a network connection
Action Result
Select "Network view" to display the
devices to be connected.
Select the port on one device and

drag the connection to the port on
the second device.
Release the mouse button to create

the network connection.
Easy Book
120 Manual, 04/2012, A5E02486774-05
7.2 Communication options
7.2 Communication options

The S7-1200 offers several types of communication between CPUs and programming
devices, HMIs, and other CPUs.
PROFINET
PROFINET is used for exchanging data through the user program with other
communications partners through Ethernet:
The CPU provides the following PROFINET and PROFIBUS support:
In V3.0, PROFINET supports 16 IO devices with a maximum of 256 submodules.
PROFIBUS allows 3 independent PROFIBUS DP Masters, supporting 32 IO devices
with a maximum of 512 submodules per IO device.
In V2.2. PROFINET supports 8 IO devices with a maximum of 128 submodules (if
eight or less PROFIBUS slaves or submodules are configured). PROFIBUS supports
a maximum of 16 PROFIBUS IO devices on a single master with a maximum of 256
submodules per IO device.
S7 communication
User Datagram Protocol (UDP) protocol
ISO on TCP (RFC 1006)
Transport Control Protocol (TCP)
PROFINET RT IO controller
As an IO controller using PROFINET RT, the CPU provides the following support on the
local PN network or through a PN/PN coupler (link). Refer to PROFIBUS and PROFINET
International, PI (www.us.profinet.com) for more information:
In V3.0, the S7-1200 communicates with up to 16 PN devices.
In V2.2, the S7-1200 communicates with up to 8 PN devices.
PROFIBUS
PROFIBUS is used for exchanging data through the user program with other
communications partners through the PROFIBUS network:
With CM 1242-5, the CPU operates as a PROFIBUS DP slave.
With CM 1243-5, the CPU operates as a PROFIBUS DP master class1.
In V3.0, PROFIBUS DP Slaves, PROFIBUS DP Masters, and ASi (the 3 left-side
communication modules) and PROFINET are separate.
Easy Book
Manual, 04/2012, A5E02486774-05 121
7.3 Number of asynchronous communication connections
In V2.2, The CPU provides the following PROFINET and PROFIBUS support:
A total of 16 devices and 256 submodules, with a maximum of 16 PROFIBUS DP
slave devices and 256 submodules (if no PROFINET IO devices or submodules are
configured).
Note
In V2.2, the total of 16 PROFINET and PROFIBUS devices includes the following:
The PROFIBUS DP slave modules attached by the PROFIBUS DP master
(CM 1243-5)
Any PROFIBUS DP slave module (CM 1242-5) connected to the CPU
Any PROFINET device connected to the CPU over the PROFINET port
For example, a configuration with three PROFIBUS CMs (one CM 1243-5 master and
two CM 1242-5 slave modules) will reduce the maximum number of slave modules
that can be accessed by the PROFIBUS DP Master (CM 1243-5) to 14.
AS-i: The S7-1200 CM 1243-2 AS-i Master allows the attachment of an AS-i network to
an S7-1200 CPU.
CPU-to-CPU S7 communication
Teleservice communication
In TeleService via GPRS, an engineering station on which STEP 7 is installed communicates
via the GSM network and the Internet with a SIMATIC S7-1200 station with a CP 1242-7.
The connection runs via a telecontrol server that serves as an intermediary and is connected
to the Internet.
7.3 Number of asynchronous communication connections

The CPU supports the following maximum number of simultaneous, asynchronous
communication connections for PROFINET and PROFIBUS:
8 connections for Open User Communications (active or passive): TSEND_C, TRCV_C,
TCON, TDISCON, TSEND, and TRCV.
3 CPU-to-CPU S7 connections for server GET/PUT data
8 CPU-to-CPU S7 connections for client GET/PUT data
Note
S7-1200, S7-300, and S7-400 CPUs use the GET and PUT instructions for CPU-to-CPU
S7 communication. An S7-200 CPU uses ETHx_XFER instructions for CPU-to-CPU
S7 communication.
Easy Book
122 Manual, 04/2012, A5E02486774-05
7.4 PROFINET and PROFIBUS instructions
HMI connections: The CPU provides dedicated HMI connections to support up to 3 HMI
devices. (You can have up to 2 SIMATIC Comfort panels.) The total number of HMI is
affected by the types of HMI panels in your configuration. For example, you could have
up to three SIMATIC Basic panels connected to your CPU, or you could have up to two
SIMATIC Comfort panels with one additional Basic panel.
PG connections: The CPU provides connections to support 1 programming device (PG).
Webserver (HTTP) connections: The CPU provides connections for the Webserver.
7.4 PROFINET and PROFIBUS instructions
PROFINET instructions
The TSEND_C and TRCV_C instructions make PROFINET communications simpler by
combining the functionality of the TCON and TDISCON instructions with the TSEND or
TRCV instruction.
TSEND_C establishes a TCP or ISO on TCP communication connection to a partner
station, sends data, and can terminate the connection. After the connection is set up and
established, it is automatically maintained and monitored by the CPU. TSEND_C
combines the functions of the TCON, TDISCON and TSEND instructions into one
instruction.
TRCV_C establishes a TCP or ISO-on-TCP communication connection to a partner CPU,
receives data, and can terminate the connection. After the connection is set up and
established, it is automatically maintained and monitored by the CPU. The TRCV_C
instruction combines the functions of the TCON, TDISCON, and TRCV instructions into
one instruction.
The TCON, TDISCON, TSEND and TRCV instructions are also supported.
Use the TUSEND and the TURCV instructions to transmit or receive data via UDP. TUSEND
and TURCV (as well as TSEND, TRCV, TCON, TDISCON) function asynchronously, which
means that the processing of the job extends over several instruction calls.
Use the IP_CONF instruction to change the IP configuration parameters from your user
program. IP_CONF works asynchronously. The execution extends over multiple calls.
PROFIBUS instructions
The DPNRM_DG (read diagnostics) instruction reads the current diagnostic data of a DP
slave in the format specified by EN 50 170 Volume 2, PROFIBUS.
Easy Book
Manual, 04/2012, A5E02486774-05 123
7.5 PROFINET
Distributed I/O instructions for PROFINET, PROFIBUS and AS-i

You can use the following instructions with PROFINET, PROFIBUS, and GPRS.
Use the RDREC (read record) and WRREC (write record) instructions to transfer a
specified data record between a component, such as a module in a central rack or a
distributed component (PROFIBUS DP or PROFINET IO).
Use the RALRM (read alarm) instruction to read an interrupt and its information from a
DP slave or PROFINET IO device component. The information in the output parameters
contains the start information of the called OB as well as information of the interrupt
source.
Use the DPRD_DAT (read consistent data) and DPWR_DAT (write consistent data)
instructions to transfer consistent data areas greater than 64 bytes from or to a DP
standard slave.
For PROFIBUS only, use the DPNRM_DG instruction to read the current diagnostic data
of a DP slave in the format specified by EN 50 170 Volume 2, PROFIBUS.
7.5 PROFINET
7.5.1 Open user communication

The integrated PROFINET port of the CPU supports multiple communications standards
over an Ethernet network:
Transport Control Protocol (TCP)
ISO on TCP (RFC 1006)
User Datagram Protocol (UDP)
Table 7- 2 Protocols and communication instructions for each
Protocol Usage examples Entering data in the Communication Addressing type

receive area instructions
TCP CPU-to-CPU Ad hoc mode Only TRCV_C and Assigns port numbers to
communication TRCV the Local (active) and
Transport of frames Data reception with TSEND_C, TRCV_C, Partner (passive)
specified length TCON, TDISCON, devices
TSEND, and TRCV
ISO on TCP CPU-to-CPU Ad hoc mode Only TRCV_C and Assigns TSAPs to the
communication TRCV Local (active) and
Message Protocol-controlled TSEND_C, TRCV_C, Partner (passive)
fragmentation and re- TCON, TDISCON, devices
assembly TSEND, and TRCV
Easy Book
124 Manual, 04/2012, A5E02486774-05
7.5 PROFINET
Protocol Usage examples Entering data in the Communication Addressing type

receive area instructions
UDP CPU-to-CPU User Datagram Protocol TUSEND and TURCV Assigns port numbers to
communication the Local (active) and
User program Partner (passive)
communications devices, but is not a
dedicated connection
S7 communication CPU-to-CPU Data transmission and GET and PUT Assigns TSAPs to the
communication reception with specified Local (active) and
Read/write data length Partner (passive)
from/to a CPU devices
PROFINET RT CPU-to-PROFINET Data transmission and Built-in Built-in
IO device reception with specified
communication length
7.5.1.1 Ad hoc mode

Typically, TCP and ISO-on-TCP receive data packets of a specified length, ranging from 1 to
8192 bytes. However, the TRCV_C and TRCV communication instructions also provide an
"ad hoc" communications mode that can receive data packets of a variable length from 1 to
1472 bytes.
Note
If you store the data in an "optimized" DB (symbolic only), you can receive data only in
arrays of Byte, Char, USInt, and SInt data types.
To configure the TRCV_C or TRCV instruction for ad hoc mode, set the LEN parameter to
65535 (0xFFFF).
If you do not call the TRCV_C or TRCV instruction in ad hoc mode frequently, you could
receive more than one packet in one call. For example: If you were to receive five 100-byte
packets with one call, TCP would deliver these five packets as one 500-byte packet, while
ISO-on-TCP would restructure the packets into five 100-byte packets.
Easy Book
Manual, 04/2012, A5E02486774-05 125
7.5 PROFINET
7.5.1.2 Connection IDs for the PROFINET instructions

When you insert the TSEND_C, TRCV_C or TCON PROFINET instructions into your user
program, STEP 7 creates an instance DB to configure the communications channel (or
connection) between the devices. Use the "Properties" of the instruction to configure the
parameters for the connection. Among the parameters is the connection ID for that
connection.
The connection ID must be unique for the CPU. Each connection that you create must
have a different DB and connection ID.
Both the local CPU and the partner CPU can use the same connection ID number for the
same connection, but the connection ID numbers are not required to match. The
connection ID number is relevant only for the PROFINET instructions within the user
program of the individual CPU.
You can use any number for the connection ID of the CPU. However, configuring the
connection IDs sequentially from "1" provides an easy method for tracking the number of
connections in use for a specific CPU.
Note
Each TSEND_C, TRCV_C or TCON instruction in your user program creates a new
connection. It is important to use the correct connection ID for each connection.
The following example shows the communication between two CPUs that utilize 2 separate
connections for sending and receiving the data.
The TSEND_C instruction in CPU_1 links to the TRCV_V in CPU_2 over the first
connection ("connection ID 1" on both CPU_1 and CPU_2).
The TRCV_C instruction in CPU_1 links to the TSEND_C in CPU_2 over the second
connection ("connection ID 2" on both CPU_1 and CPU_2).
&38B &38B TSEND_C on CPU_1 creates a

connection and assigns a connection
ID to that connection (connection ID 1
for CPU_1).
TRCV_C on CPU_2 creates the
connection for CPU_2 and assigns the
connection ID (connection ID 1 for
CPU_2).
TRCV_C on CPU_1 creates a second
76(1'B&
75&9B&
connection for CPU_1 and assigns a
different connection ID for that
connection (connection ID 2 for
CPU_1).
75&9B&
76(1'B& TSEND_C on CPU_2 creates a
second connection and assigns a
different connection ID for that
connection (connection ID 2 for
CPU_2).
Easy Book
126 Manual, 04/2012, A5E02486774-05
7.5 PROFINET
The following example shows the communication between two CPUs that utilize 1
connection for both sending and receiving the data.
Each CPU uses a TCON instruction to configure the connection between the two CPUs.
The TSEND instruction in CPU_1 links to the TRCV instruction in CPU_2 by using the
connection ID ("connection ID 1") that was configured by the TCON instruction in CPU_1.
The TRCV instruction in CPU_2 links to the TSEND instruction in CPU_1 by using the
The TSEND instruction in CPU_2 links to the TRCV instruction in CPU_1 by using the
The TRCV instruction in CPU_1 links to the TSEND instruction in CPU_2 by using the
&38B &38B TCON on CPU_1 creates a

ID for that connection on CPU_1
(ID=1).
TCON on CPU_2 creates a
ID for that connection on CPU_2
(ID=1).
7&21
7&21 TSEND and TRCV on CPU_1 use the
connection ID created by the TCON
on CPU_1 (ID=1).
TSEND and TRCV on CPU_2 use the
76(1' 75&9 connection ID created by the TCON
on CPU_2 (ID=1).
75&9 76(1'
Easy Book
Manual, 04/2012, A5E02486774-05 127
7.5 PROFINET
As shown in the following example, you can also use individual TSEND and TRCV
instruction to communication over a connection created by a TSEND_C or TRCV_C
instruction. The TSEND and TRCV instructions do not themselves create a new connection,
so must use the DB and connection ID that was created by a TSEND_C, TRCV_C or TCON
instruction.
&38B &38B TSEND_C on CPU_1 creates a

ID to that connection (ID=1).
TRCV_C on CPU_2 creates a
connection and assigns the
connection ID to that connection on
CPU_2 (ID=1).
connection ID created by the
76(1'B&
75&9B& TSEND_C on CPU_1 (ID=1).
connection ID created by the TRCV_C
on CPU_2 (ID=1).
75&9 76(1'
76(1' 75&9
7.5.1.3 Parameters for the PROFINET connection

The TSEND_C, TRCV_C and TCON instructions require that connection-related parameters
be specified in order to connect to the partner device. These parameters are specified by the
TCON_Param structure for the TCP, ISO-on-TCP and UDP protocols. Typically, you use the
"Configuration" tab of the "Properties" of the instruction to specify these parameters. If the
"Configuration" tab is not accessible, then you must specify the TCON_Param structure
programmatically.
Table 7- 3 Structure of the connection description (TCON_Param)
Byte Parameter and data type Description

01 block_length UInt Length: 64 bytes (fixed)
23 id CONN_OUC Reference to this connection: Range of values: 1 (default) to 4095.
(Word) Specify the value of this parameter for the TSEND_C, TRCV_C or
TCON instruction under ID.
4 connection_type USInt Connection type:
17: TCP (default)
18: ISO-on-TCP
19: UDP
Easy Book
128 Manual, 04/2012, A5E02486774-05
7.5 PROFINET

5 active_est Bool ID for the type of connection:
TCP and ISO-on-TCP:
FALSE: Passive connection
TRUE: Active connection (default)
UDP: FALSE
6 local_device_id USInt ID for the local PROFINET or Industrial Ethernet interface:
1 (default)
7 local_tsap_id_len USInt Length of parameter local_tsap_id used, in bytes; possible values:
TCP: 0 (active, default) or 2 (passive)
ISO-on-TCP: 2 to 16
UDP: 2
8 rem_subnet_id_len USInt This parameter is not used.
9 rem_staddr_len USInt Length of address of partner end point, in bytes:
0: unspecified (parameter rem_staddr is irrelevant)
4 (default): Valid IP address in parameter rem_staddr (only for
TCP and ISO-on-TCP)
10 rem_tsap_id_len USInt Length of parameter rem_tsap_id used, in bytes; possible values:
TCP: 0 (passive) or 2 (active, default)
ISO-on-TCP: 2 to 16
UDP: 0
11 next_staddr_len USInt This parameter is not used.
12 27 local_tsap_id Array [1..16] of Local address component of connection:
Byte
TCP and ISO-on-TCP: local port no. (possible values: 1 to
49151; recommended values: 2000...5000):
local_tsap_id[1] = high byte of port number in hexadecimal
notation;
local_tsap_id[2] = low byte of port number in hexadecimal
notation;
local_tsap_id[3-16] = irrelevant
ISO-on-TCP: local TSAP-ID:
local_tsap_id[1] = B#16#E0;
local_tsap_id[2] = rack and slot of local end points (bits 0 to
4: slot number, bits 5 to 7: rack number);
local_tsap_id[3-16] = TSAP extension, optional
UDP: This parameter is not used.
Note: Make sure that every value of local_tsap_id is unique within
the CPU.
28 33 rem_subnet_id Array [1..6] of This parameter is not used.
USInt
Easy Book
Manual, 04/2012, A5E02486774-05 129
7.5 PROFINET

34 39 rem_staddr Array [1..6] of TCP and ISO-on-TCP only: IP address of the partner end point.
USInt (Not relevant for passive connections.) For example, IP address
192.168.002.003 is stored in the following elements of the array:
rem_staddr[1] = 192
rem_staddr[2] = 168
rem_staddr[3] = 002
rem_staddr[4] = 003
rem_staddr[5-6]= irrelevant
40 55 rem_tsap_id Array [1..16] of Partner address component of connection
Byte
TCP: partner port number. Range: 1 to 49151; Recommended
values: 2000 to 5000):
rem_tsap_id[1] = high byte of the port number in
hexadecimal notation
rem_tsap_id[2] = low byte of the port number in
hexadecimal notation;
rem_tsap_id[3-16] = irrelevant
ISO-on-TCP: partner TSAP-ID:
rem_tsap_id[1] = B#16#E0
rem_tsap_id[2] = rack and slot of partner end point (bits 0 to
4: Slot number, bits 5 to 7: rack number)
rem_tsap_id[3-16] = TSAP extension, optional
UDP: This parameter is not used.
56 61 next_staddr Array [1..6] of This parameter is not used.
Byte
62 63 spare Word Reserved: W#16#0000
Easy Book
130 Manual, 04/2012, A5E02486774-05
7.5 PROFINET
7.5.2 Configuring the Local/Partner connection path

The inspector window displays the properties of the connection whenever you have selected
any part of the instruction. Specify the communication parameters in the "Configuration" tab
of the "Properties" for the communication instruction.
Table 7- 4 Configuring the connection path (using the properties of the instruction)
TCP, ISO-on-TCP, and UDP Connection properties

For the TCP, ISO-on-TCP, and UDP Ethernet
protocols, use the "Properties" of the instruction
(TSEND_C, TRCV_C, or TCON) to configure the
"Local/Partner" connections.
The illustration shows the "Connection
properties" of the "Configuration tab" for an ISO-
on-TCP connection.
Note
When you configure the connection properties for one CPU, STEP 7 allows you either to
select a specific connection DB in the partner CPU (if one exists), or to create the connection
DB for the partner CPU. The partner CPU must already have been created for the project
and cannot be an "unspecified" CPU.
You must still insert a TSEND_C, TRCV_C or TCON instruction into the user program of the
partner CPU. When you insert the instruction, select the connection DB that was created by
the configuration.
Easy Book
Manual, 04/2012, A5E02486774-05 131
7.5 PROFINET
Table 7- 5 Configuring the connection path for S7 communication (Device configuration)
S7 communication (GET and PUT) Connection properties

For S7 communication, use the "Devices &
networks" editor of the network to configure the
Local/Partner connections. You can click the
"Highlighted: Connection" button to access the
"Properties".
The "General" tab provides several properties:
"General" (shown)
"Local ID"
"Special connection properties"
"Address details" (shown)
Refer to "Protocols" (Page 124) in the "PROFINET" section or to "Creating an S7

connection" (Page 144) in the "S7 communication" section for more information and a list of
available communication instructions.
Table 7- 6 Parameters for the multiple CPU connection
Parameter Definition
Address Assigned IP addresses
General End point Name assigned to the partner (receiving) CPU
Interface Name assigned to the interfaces
Subnet Name assigned to the subnets
Interface type S7 communication only: Type of interface
Connection type Type of Ethernet protocol
Connection ID ID number
Connection data Local and Partner CPU data storage location
Establish active Radio button to select Local or Partner CPU as the active connection
connection
Address End point S7 communication only: Name assigned to the partner (receiving) CPU
details Rack/slot S7 communication only: Rack and slot location
Connection resource S7 communication only: Component of the TSAP used when configuring an
S7 connection with an S7-300 or S7-400 CPU
Port (decimal): TCP and UPD: Partner CPU port in decimal format
Easy Book
132 Manual, 04/2012, A5E02486774-05
7.6 PROFIBUS
Parameter Definition
TSAP 1 and Subnet ID: ISO on TCP (RFC 1006) and S7 communication: Local and partner CPU
TSAPs in ASCII and hexadecimal formats
1 When configuring a connection with an S7-1200 CPU for ISO-on-TCP, use only ASCII characters in the TSAP extension
for the passive communication partners.
Transport Service Access Points (TSAPs)

Using TSAPs, ISO on TCP protocol and S7 communication allows multiple connections to a
single IP address (up to 64K connections). TSAPs uniquely identify these communication
end point connections to an IP address.
In the "Address Details" section of the Connection Parameters dialog, you define the TSAPs
to be used. The TSAP of a connection in the CPU is entered in the "Local TSAP" field. The
TSAP assigned for the connection in your partner CPU is entered under the "Partner TSAP"
field.
Port Numbers
With TCP and UDP protocols, the connection parameter configuration of the Local (active)
connection CPU must specify the remote IP address and port number of the Partner
(passive) connection CPU.
In the "Address Details" section of the Connection Parameters dialog, you define the ports to
be used. The port of a connection in the CPU is entered in the "Local Port" field. The port
assigned for the connection in your partner CPU is entered under the "Partner Port" field.
7.6 PROFIBUS
A PROFIBUS system uses a bus master to poll slave devices distributed in a multi-drop
fashion on an RS485 serial bus. A PROFIBUS slave is any peripheral device (I/O
transducer, valve, motor drive, or other measuring device) which processes information and
sends its output to the master. The slave forms a passive station on the network since it
does not have bus access rights, and can only acknowledge received messages, or send
response messages to the master upon request. All PROFIBUS slaves have the same
priority, and all network communication originates from the master.
A PROFIBUS master forms an "active station" on the network. PROFIBUS DP defines two
classes of masters. A class 1 master (normally a central programmable controller (PLC) or a
PC running special software) handles the normal communication or exchange of data with
the slaves assigned to it. A class 2 master (usually a configuration device, such as a laptop
or programming console used for commissioning, maintenance, or diagnostics purposes) is
a special device primarily used for commissioning slaves and for diagnostic purposes.
Easy Book
Manual, 04/2012, A5E02486774-05 133
7.6 PROFIBUS
The S7-1200 is connected to a PROFIBUS network as a DP slave with the CM 1242-5

communication module. The CM 1242-5 (DP slave) module can be the communications
partner of DP V0/V1 masters. In the figure below, the S7-1200 is a DP slave to an S7-300
controller.
The S7-1200 is connected to a PROFIBUS network as a DP master with the CM 1243-5

communication module. The CM 1243-5 (DP master) module can be the communications
partner of DP V0/V1 slaves. In the figure below, the S7-1200 is a master controlling an
ET200S DP slave.
If a CM 1242-5 and a CM 1243-5 are installed together, an S7-1200 can perform as both a
slave of a higher-level DP master system and a master of a lower-level DP master system,
simultaneously.
For V3.0, you can configure a maximum of three PROFIBUS CMs per station, in which there
can be any combination of DP master or DP slave CMs. DP masters in a V3.0
implementation can each control a maximum of 32 slaves.
For V2.2, you can configure a maximum of three PROFIBUS CMs per station, of which only
one may be a DP master. A DP master in a V2.2 implementation can control a maximum of
16 slaves.
Easy Book
134 Manual, 04/2012, A5E02486774-05
7.6 PROFIBUS
7.6.1 Configuration examples for PROFIBUS

Below, you will find examples of configurations in which the CM 1242-5 is used as a
PROFIBUS slave and the CM 1243-5 is used as a PROFIBUS master.
PG/PC/IPC
SIMATIC S7-300 Operator control &
monitoring
PROFIBUS
SIMATIC S7-1200 OLM OLM

with CM 1242-5
PROFINET/
Industrial Ethernet
Operator control & PROFIBUS SIMATIC S7-1200
monitoring (LWL) with CM 1242-5
Figure 7-1 Configuration example with a CM 1242-5 as PROFIBUS slave
SIMATIC S7-1200
with CM 1243-5 Operator control &
monitoring
PROFIBUS
PG/PC/IPC SINAMICS ET 200S
Figure 7-2 Configuration example with a CM 1243-5 as PROFIBUS master
Connecting the S7-1200 to PROFIBUS DP

The S7-1200 can be connected to a PROFIBUS fieldbus system with the following
communications modules:
CM 1242-5
Operates as DP slave
CM 1243-5
Operates as DP master class 1
Easy Book
Manual, 04/2012, A5E02486774-05 135
7.6 PROFIBUS
If a CM 1242-5 and a CM 1243-5 are installed together, an S7-1200 can perform the
following tasks simultaneously:
Slave of a higher-level DP master system
and
Master of a lower-level DP master system
Bus protocol
The PROFIBUS CMs use the PROFIBUS DP-V1 protocol.
PROFIBUS communications partners of the S7-1200

The two PROFIBUS CMs allow the S7-1200 to exchange data with the following
communications partners.
CM 1242-5
The CM 1242-5 (DP slave) can be the communications partner of the following DP V0/V1
masters:
SIMATIC S7-1200, S7-300, S7-400, S7 Modular Embedded Controller
DP master modules and the distributed IO SIMATIC ET200
SIMATIC PC stations
SIMATIC NET IE/PB Link
Programmable controllers of various vendors
CM 1243-5
The CM 1243-5 (DP master) can be the communications partner of the following DP
V0/V1 slaves:
Distributed I/O SIMATIC ET200
S7-1200 CPUs with CM 1242-5
S7-200 CPUs with PROFIBUS DP module EM 277
SINAMICS converter
Drives and actuators from various vendors
Sensors of various vendors
S7-300/400 CPU with PROFIBUS interface
S7-300/400 CPU with PROFIBUS CP (for example CP 342-5)
SIMATIC PC stations with PROFIBUS CP
Easy Book
136 Manual, 04/2012, A5E02486774-05
7.6 PROFIBUS
Types of communication with DP-V1

The following types of communication are available with DP-V1:
Cyclic communication (CM 1242-5 and CM 1243-5)
Both PROFIBUS modules support cyclic communication for the transfer of process data
between DP slave and DP master.
Cyclic communication is handled by the operating system of the CPU. No software blocks
are required for this. The I/O data is read or written directly from/to the process image of
the CPU.
Acyclic communication (CM 1243-5 only)
The DP master module also supports acyclic communication using software blocks:
The "RALRM" instruction is available for interrupt handling.
The "RDREC" and "WRREC" instructions are available for transferring configuration
and diagnostics data.
Functions not supported by the CM 1243-5:
SYNC/FREEZE
Get_Master_Diag
Other communications services of the CM 1243-5

The CM 1243-5 DP master module supports the following additional communications
services:
S7 communication
PUT/GET services
The DP master functions as a client and server for queries from other S7 controllers or
PCs via PROFIBUS.
PG/OP communication
The PG functions allow the downloading of configuration data and user programs from
a PG and the transfer of diagnostics data to a PG.
Possible communications partners for OP communication are HMI panels, SIMATIC
panel PCs with WinCC flexible or SCADA systems that support S7 communication.
Configuration and module replacement

You configure the modules, networks and connections in STEP 7 as of version V11.0.
If you want to configure the module in a third-party system, there is a GSD file available for
the CM 1242-5 (DP slave) on the CD that ships with the module and on Siemens Automation
Customer Support pages on the Internet.
The configuration data of the PROFIBUS CMs is stored on the local CPU. This allows simple
replacement of these communications modules when necessary.
You can configure a maximum of three PROFIBUS CMs per station, of which only one may
be a DP master.
Easy Book
Manual, 04/2012, A5E02486774-05 137
7.6 PROFIBUS
Electrical connections
Power supply
The CM 1242-5 is supplied with power via the backplane bus of the SIMATIC station.
The CM 1243-5 has a separate connector for the 24 VDC power supply.
PROFIBUS
The RS-485 interface of the PROFIBUS connector is a 9-pin D-sub female connector.
You also have the option of connecting to optical PROFIBUS networks via an Optical Bus
Terminal OBT or an Optical Link Module OLM.
7.6.2 Adding the CM 1243-5 (DP master) module and a DP slave

In the "Devices and networks" portal, use the hardware catalog to add PROFIBUS modules
to the CPU. These modules are connected to the left side of the CPU. To insert a module
into the hardware configuration, select the module in the hardware catalog and either
double-click or drag the module to the highlighted slot.
Table 7- 7 Adding a PROFIBUS CM 1243-5 (DP master) module to the device configuration

CM 1243-5
(DP
master)
Use the hardware catalog to add DP slaves as well. For example, to add an ET200 S DP
slave, in the Hardware Catalog, expand the following containers:
Distributed I/O
ET200 S
Interface modules
PROFIBUS
Easy Book
138 Manual, 04/2012, A5E02486774-05
7.6 PROFIBUS
Next, select "6ES7 151-1BA02-0AB0" (IM151-1 HF) from the list of part numbers, and add
the ET200 S DP slave as shown in the figure below.
Table 7- 8 Adding an ET200 S DP slave to the device configuration
Insert the DP slave Result
7.6.3 Assigning PROFIBUS addresses to the CM 1243-5 module and DP slave
Configuring the PROFIBUS interface

After you configure logical network connections between two PROFIBUS devices, you can
configure parameters for the PROFIBUS interfaces. To do so, click the purple PROFIBUS
box on the CM 1243-5 module, and the "Properties" tab in the inspector window displays the
PROFIBUS interface. The DP slave PROFIBUS interface is configured in the same manner.
Table 7- 9 Configuring the CM 1243-5 (DP master) module and ET200 S DP slave PROFIBUS
interfaces
CM 1243-5 (DP master) module ET200 S DP slave

PROFIBUS port
Assigning the PROFIBUS address

In a PROFIBUS network, each device is assigned a PROFIBUS address. This address can
range from 0 through 127, with the following exceptions:
Address 0: Reserved for network configuration and/or programming tools attached to the
bus
Address 1: Reserved by Siemens for the first master
Easy Book
Manual, 04/2012, A5E02486774-05 139
7.6 PROFIBUS
Address 126: Reserved for devices from the factory that do not have a switch setting and
must be re-addressed through the network
Address 127: Reserved for broadcast messages to all devices on the network and may
not be assigned to operational devices
Thus, the addresses that may be used for PROFIBUS operational devices are 2 through
125.
In the Properties window, select the "PROFIBUS address" configuration entry. STEP 7
displays the PROFIBUS address configuration dialog, which is used to assign the
PROFIBUS address of the device.
Table 7- 10 Parameters for the PROFIBUS address
Parameter Description
Subnet Name of the Subnet to which the device is connected. Click the "Add new subnet" button to create a
new subnet. "Not connected" is the default. Two connection types are possible:
The "Not connected" default provides a local connection.
A subnet is required when your network has two or more devices.
Parameters Address Assigned PROFIBUS address for the device
Highest address The highest PROFIBUS address is based on the active stations on the
PROFIBUS (for example, DP master). Passive DP slaves independently
have PROFIBUS addresses from 1 to 125 even if the highest PROFIBUS
address is set to 15, for example. The highest PROFIBUS address is
relevant for token forwarding (forwarding of the send rights), and the token
is only forwarded to active stations. Specifying the highest PROFIBUS
address optimizes the bus.
Transmission rate Transmission rate of the configured PROFIBUS network: The PROFIBUS
transmission rates range from 9.6 Kbits/sec to 12 Mbits/sec. The
transmission rate setting depends on the properties of the PROFIBUS
nodes being used. The transmission rate should not be greater than the
rate supported by the slowest node.
The transmission rate is normally set for the master on the PROFIBUS
network, with all DP slaves automatically using that same transmission rate
(auto-baud).
Easy Book
140 Manual, 04/2012, A5E02486774-05
7.7 AS-i
7.7 AS-i
The S7-1200 AS-i master CM 1243-2 allows the attachment of an AS-i network to an S7-
1200 CPU.
The actuator/sensor interface, or AS-i, is a single master network connection system for the
lowest level in automation systems. The CM 1243-2 serves as the AS-i master for the
network. Using a single AS-i cable, sensors and actuators (AS-i slave devices) can be
connected to the CPU through the CM 1243-2. The CM 1243-2 handles all AS-i network
coordination and relays data and status information from the actuators and sensors to the
CPU through the I/O addresses assigned to the CM 1243-2. You can access binary or
analog values depending on the slave type. The AS-i slaves are the input and output
channels of the AS-i system and are only active when called by the CM 1243-2.
In the figure below, the S7-1200 is an AS-i master controlling AS-i operator panel and I/O
module digital/analog slave devices.
7.7.1 Adding the AS-i master CM 1243-2 and AS-i slave

Use the hardware catalog to add AS-i master CM1243-2 modules to the CPU. These
modules are connected to the left side of the CPU, and a maximum of three AS-i master
CM1243-2 modules can be used. To insert a module into the hardware configuration, select
the module in the hardware catalog and either double-click or drag the module to the
highlighted slot.
Table 7- 11 Adding an AS-i master CM1243-2 module to the device configuration

CM 1243-2
AS-i
Master
Easy Book
Manual, 04/2012, A5E02486774-05 141
7.7 AS-i
Use the hardware catalog to add AS-i slaves as well. For example, to add an "I/O module,
compact, digital, input" slave, in the Hardware Catalog, expand the following containers:
Field devices
AS-Interface slaves
Next, select "3RG9 001-0AA00" (AS-i SM-U, 4DI) from the list of part numbers, and add the
"I/O module, compact, digital, input" slave as shown in the figure below.
Table 7- 12 Adding an AS-i slave to the device configuration
Insert the AS-i slave Result
7.7.2 Assigning an AS-i address to an AS-i slave
Configuring the AS-i slave interface

To configure parameters for the AS-i interface, click the yellow AS-i box on the AS-i slave,
and the "Properties" tab in the inspector window displays the AS-i interface.
AS-i port
Assigning the AS-i slave address

In an AS-i network, each device is assigned an AS-i slave address. This address can range
from 0 through 31; however, address 0 is reserved only for new slave devices.
The slave addresses are 1(A or B) to 31(A or B) for a total of up to 62 slave devices. Any
address in the range of 1 - 31 can be assigned to an AS-i slave device; in other words, it
does not matter whether the slaves begin with address 21 or whether the first slave is
actually given the address 1.
Easy Book
142 Manual, 04/2012, A5E02486774-05
7.8 S7 communication
Enter the AS-i slave address here.
Table 7- 13 Parameters for the AS-i interface
Parameter Description
Network Name of the network to which the device is connected
Address(es) Assigned AS-i address for the slave device in range of 1(A or B) to 31(A or B) for a total of up to 62
slave devices
7.8.1 GET and PUT instructions

You can use the GET and PUT instructions to communicate with S7 CPUs through
PROFINET and PROFIBUS connections:
Accessing data in a remote CPU: An S7-1200 CPU can only use absolute addresses in
the ADDR_x input field to address variables of remote CPUs (S7-200/300/400/1200).
Accessing data in a standard DB: An S7-1200 CPU can only use absolute addresses in
the ADDR_x input field to address DB variables in a standard DB of a remote S7 CPU.
Accessing data in an optimized DB: An S7-1200 CPU cannot access DB variables in an
optimized DB of a remote S7-1200 CPU.
Accessing data in a local CPU: An S7-1200 CPU can use either absolute or symbolic
addresses as inputs to the RD_x or SD_x input fields of the GET or PUT instruction,
respectively.
Easy Book
Manual, 04/2012, A5E02486774-05 143
STEP 7 automatically creates the DB when you insert the instruction.
Note
To ensure data consistency, always evaluate when the operation has been completed
(NDR = 1 for GET, or DONE = 1 for PUT) before accessing the data or initiating another
read or write operation.
7.8.2 Creating an S7 connection

The connection type that you select creates a communication connection to a partner
station. The connection is set up, established, and automatically monitored.
In the Devices and Networks portal, use the "Network view" to create the network
connections between the devices in your project. First, click the "Connections" tab, and then
select the connection type with the dropdown, just to the right (for example, an S7
connection). Click the green (PROFINET) box on the first device, and drag a line to the
PROFINET box on the second device. Release the mouse button and your PROFINET
connection is joined.
Refer to "Creating a network connection" (Page 120) for more information.
Click the "Highlighted: Connection" button to access the "Properties" configuration dialog of
the communication instruction.
7.8.3 GET/PUT connection parameter assignment

The GET/PUT instructions connection parameter assignment is a user aid for configuring S7
CPU-CPU communication connections.
Easy Book
144 Manual, 04/2012, A5E02486774-05
7.9 GPRS
After inserting a GET or PUT block, the GET/PUT instructions connection parameter
assignment is started:
The inspector window displays the properties of the connection whenever you have selected
any part of the instruction. Specify the communication parameters in the "Configuration" tab
of the "Properties" for the communication instruction.
After inserting a GET or PUT block, the "Configuration" tab automatically appears and the
"Connection parameters" page is immediately shown. This page allows the user to configure
the necessary S7 connection and to configure the parameter "Connection ID" that is
referenced by the block parameter "ID". A "Block parameters" page allows the user to
configure additional block parameters.
7.9 GPRS
7.9.1 Connection to a GSM network
IP-based WAN communication via GPRS

Using the CP 1242-7 communications processor, the S7-1200 can be connected to GSM
networks. The CP 1242-7 allows WAN communication from remote stations with a control
center and inter-station communication.
Inter-station communication is possible only via a GSM network. For communication
between a remote station and a control room, the control center must have a PC with
Internet access.
Easy Book
Manual, 04/2012, A5E02486774-05 145
7.9 GPRS
The CP 1242-7 supports the following services for communication via the GSM network:
GPRS (General Packet Radio Service)
The packet-oriented service for data transmission "GPRS" is handled via the GSM
network.
SMS (Short Message Service)
The CP 1242-7 can receive and send SMS messages. The communications partner can
be a mobile phone or an S7-1200.
The CP 1242-7 is suitable for use in industry worldwide and supports the following frequency
bands:
850 MHz
900 MHz
1 800 MHz
1 900 MHz
Requirements
The equipment used in the stations or the control center depends on the particular
application.
For communication with or via a central control room, the control center requires a PC
with Internet access.
Apart from the station equipment, a remote S7-1200 station with a CP 1242-7 must meet
the following requirements to be able to communicate via the GSM network:
A contract with a suitable GSM network provider
If GPRS is used, the contract must allow the use of the GPRS service.
If there is to be direct communication between stations only via the GSM network, the
GSM network provider must assign a fixed IP address to the CPs. In this case,
communication between stations is not via the control center.
The SIM card belonging to the contract
The SIM card is inserted in the CP 1242-7.
Local availability of a GSM network in the range of the station
Below, you will find several configuration examples for stations with a CP 1242-7.
Easy Book
146 Manual, 04/2012, A5E02486774-05
7.9 GPRS
Sending messages by SMS
0RELOHSKRQH
*356 RU6VWDWLRQ
6ZLWK
6WDWLRQ &3"
Figure 7-3 Sending messages by SMS from an S7-1200 station
A SIMATIC S7-1200 with a CP 1242-7 can send messages by SMS to a configured mobile
phone or a configured S7-1200 station.
Telecontrol by a control center
7HOHFRQWUROVHUYHUZLWK
DSSOLFDWLRQ
7(/(&21752/
6(59(5%$6,&
&RQWUROFHQWHU '6/URXWHU
,QWHUQHW
,QGXVWULDO(WKHUQHW
*356
6ZLWK 6ZLWK 6ZLWK

6WDWLRQ &3 6WDWLRQ 0' 6WDWLRQ &3
Figure 7-4 Communication between S7-1200 stations and a control center
Easy Book
Manual, 04/2012, A5E02486774-05 147
7.9 GPRS
In telecontrol applications, SIMATIC S7-1200 stations with a CP 1242-7 communicate with a

control center via the GSM network and the Internet. The TELECONTROL SERVER BASIC
application is installed on the telecontrol server in the master station. This results in the
following use cases:
Telecontrol communication between station and control center
In this use case, data from the field is sent by the stations to the telecontrol server in the
master station via the GSM network and Internet. The telecontrol server is used to control
and monitor remote stations.
Communication between a station and a control center PC with OPC client
As in the first case, the stations communicate with the telecontrol server. Using the OPC
server of TELECONTROL SERVER BASIC, the telecontrol server exchanges data with a
master station PC. The control center PC could, for example, have WinCC and an
integrated OPC client installed on it.
Inter-station communication via a control center
To allow inter-station communication, the telecontrol server forwards the messages of the
sending station to the receiving station.
Direct communication between stations
1HWZRUNSURYLGHUDVVLJQVIL[HG
,3DGGUHVVHV
*356
&3ZLWKIL[HG &3ZLWKIL[HG
,3DGGUHVV ,3DGGUHVV
6ZLWK 6ZLWK
6WDWLRQ &3" 6WDWLRQ &3"
Figure 7-5 Direct communication between two S7-1200 stations
In this configuration, two SIMATIC S7-1200 stations communicate directly with each other
using the CP 1242-7 via the GSM network. Each CP 1242-7 has a fixed IP address. The
relevant service of the GSM network provider must allow this.
Easy Book
148 Manual, 04/2012, A5E02486774-05
7.9 GPRS
TeleService via GPRS
(QJLQHHULQJVWDWLRQ 7HOHFRQWUROVHUYHUZLWKDSSOLFDWLRQ
ZLWK67(3 7(/(&21752/6(59(5%$6,& ,QWHUQHW
'6/URXWHU
*356
,QGXVWULDO(WKHUQHW
6ZLWK
6WDWLRQ &3
Figure 7-6 TeleService via GPRS
In TeleService via GPRS, an engineering station on which STEP 7 is installed communicates

via the GSM network and the Internet with a SIMATIC S7-1200 station with a CP 1242-7.
The connection runs via a telecontrol server that serves as an intermediary and is connected
to the Internet.
Easy Book
Manual, 04/2012, A5E02486774-05 149
7.9 GPRS
The CP 1242-7 can be used for the following applications:
Telecontrol applications
Sending messages by SMS
Via the CP 1242-7, the CPU of a remote S7-1200 station can receive SMS messages
from the GSM network or send messages by SMS to a configured mobile phone or an
S7-1200.
Communication with a control center
Remote S7-1200 stations communicate via the GSM network and the Internet with a
telecontrol server in the master station. For data transfer using GPRS, the
"TELECONTROL SERVER BASIC" application is installed on the telecontrol server in the
master station. The telecontrol server communicates with a higher-level central control
system using the integrated OPC server function.
Inter-station communication between S7-1200 stations via a GSM network
Inter-station communication between remote stations with a CP 1242-7 can be handled in
two different ways:
Indirect communication via a master station
In this configuration, a permanent secure connection between S7-1200 stations that
communicate with each other and the telecontrol server is established in the master
station. Communication between the stations is via the telecontrol server. The
CP 1242-7 operates in "Telecontrol" mode.
Direct communication between the stations
For direct communication between stations without the detour via the master station,
SIM cards with a fixed IP address are used that allow the stations to address each
other directly. The possible communications services and security functions (for
example VPN) depend on what is offered by the network provider. The CP 1242-7
operates in "GPRS direct" mode.
TeleService via GPRS

A TeleService connection can be established between an engineering station with STEP 7
and a remote S7-1200 station with a CP 1242-7 via the GSM network and the Internet. The
connection runs from the engineering station via a telecontrol server or a TeleService
gateway that acts as an intermediary forwarding frames and establishing the authorization.
These PCs use the functions of the "TELECONTROL SERVER BASIC" application.
You can use the TeleService connection for the following purposes:
Downloading configuration or program data from the STEP 7 project to the station
Querying diagnostics data on the station
Easy Book
150 Manual, 04/2012, A5E02486774-05
7.9 GPRS
Other services and functions of the CP 1242-7

Time-of-day synchronization of the CP via the Internet
You can set the time on the CP as follows:
In "Telecontrol" mode, the time of day is transferred by the telecontrol server. The CP
uses this to set its time.
In "GPRS direct" mode, the CP can request the time using SNTP.
To synchronize the CPU time, you can read out the current time from the CP using a
block.
Interim buffering of messages to be sent if there are connection problems
Logging the volume of data
The volumes of data transferred are logged and can be evaluated for specific purposes.
Configuration and module replacement

To configure the module, the following configuration tool is required:
STEP 7 version V11.0 SP1 or higher
For STEP 7 V11.0 SP1, you also require support package "CP 1242-7" (HSP0003001).
For process data transfer using GPRS, use the telecontrol communications instructions in
the user program of the station.
The configuration data of the CP 1242-7 is stored on the local CPU. This allows simple
replacement of the CP when necessary.
You can insert up to three modules of the CP 1242-7 type per S7-1200. This, for example,
allows redundant communications paths to be established.
Electrical connections
Power supply of the CP 1242-7
The CP has a separate connection for the external 24 VDC power supply.
Wireless interface for the GSM network
An extra antenna is required for GSM communication. This is connected via the SMA
socket of the CP.
Easy Book
Manual, 04/2012, A5E02486774-05 151
7.9 GPRS
The ANT794-4MR GSM/GPRS antenna

The following antennas are available for use in GSM/GPRS networks and can be installed
both indoors and outdoors:
Quadband antenna ANT794-4MR
Figure 7-7 ANT794-4MR GSM/GPRS antenna
Short name Order no. Explanation

ANT794-4MR 6NH9 860-1AA00 Quadband antenna (900, 1800/1900 MHz, UMTS);
weatherproof for indoor and outdoor areas; 5 m
connecting cable connected permanently to the
antenna; SMA connector, including installation
bracket, screws, wall plugs
Flat antenna ANT794-3M
Figure 7-8 Flat antenna ANT794-3M
Short name Order no. Explanation

ANT794-3M 6NH9 870-1AA00 Flat antenna (900, 1800/1900 MHz); weatherproof
for indoor and outdoor areas; 1.2 m connecting cable
connected permanently to the antenna; SMA
connector, including adhesive pad, screws mounting
possible
The antennas must be ordered separately.
Easy Book
152 Manual, 04/2012, A5E02486774-05
7.10 PtP, USS, and Modbus communication protocols

The CPU supports the PtP protocol for character-based serial communication, in which the
user application completely defines and implements the protocol of choice.
PtP enables a wide variety of possibilities:

Sending information directly to an external
device such as a printer
Receiving information from devices such as
barcode readers, RFID readers, third-party
camera or vision systems, and many other
types of devices
Sending and receiving data with devices such
as GPS devices, third-party camera or vision
systems, or radio modems
PtP is serial communication that supports a variety of baud rates and parity options. STEP 7
provides instructions for the USS drive protocol (RS485 only) and Modbus RTU Master and
RTU Slave protocols.
7.10.1 Using the serial communication interfaces

Two communication modules (CMs) and one communication board (CB) provide the
interface for PtP communications:
CM 1241 RS232
CM 1241 RS422/485
CB 1241 RS485
You can connect up to three CMs (of any type) plus a CB for a total of four communication
interfaces. Install the CM to the left of the CPU or another CM. Install the CB on the front of
the CPU. Refer to the "Installation" chapter in the S7-1200 System Manual for detailed
instructions on module installation and removal.
The serial communication interfaces have the following characteristics:
Have an isolated port
Support Point-to-Point protocols
Are configured and programmed through extended instructions and library functions
Display transmit and receive activity by means of LEDs
Display a diagnostic LED (CMs only)
Are powered by the CPU: No external power connection is needed.
Refer to the technical specifications for communication interfaces.
Easy Book
Manual, 04/2012, A5E02486774-05 153
LED indicators
The communication modules have three LED indicators:
Diagnostic LED (DIAG): This LED flashes red until it is addressed by the CPU. After the
CPU powers up, it checks for CMs and addresses them. The diagnostic LED begins to
flash green. This means that the CPU has addressed the CM, but has not yet provided
the configuration to it. The CPU downloads the configuration to the configured CMs when
the program is downloaded to the CPU. After a download to the CPU, the diagnostic LED
on the communication module should be a steady green.
Transmit LED (Tx): The transmit LED illuminates when data is being transmitted out the
communication port.
Receive LED (Rx): This LED illuminates when data is being received by the
communication port.
The communication board provides transmit (TxD) and receive (RxD) LEDs. It has no
diagnostic LED.
7.10.2 PtP instructions

The PORT_CFG, SEND_CFG, and RCV_CFG instructions allow you to change the
configuration from your user program.
PORT_CFG changes the port parameters such as baud rate.
SEND_CFG changes the configuration of serial transmission parameters.
RCV_CFG changes the configuration of serial receiver parameters in a communication
port. This instruction configures the conditions that signal the start and end of a received
message. Messages that satisfy these conditions will be received by the RCV_PTP
instruction.
The dynamic configuration changes are not permanently stored in the CPU. After a power
cycle, the initial static configuration from the device configuration will be used.
The SEND_PTP, RCV_PTP, and RCV_RST instructions control the PtP communication:
SEND_PTP transfers the specified buffer to the CM or CB. The CPU continues to execute
the user program while the module sends the data at the specified baud rate.
RCV_PTP checks for messages that have been received in the CM or CB. If a message
is available, it will be transferred to the CPU.
The RCV_RST resets the receive buffer.
Each CM or CB can buffer up to a maximum of 1K bytes. This buffer can be allocated across
multiple received messages.
The SGN_SET and SGN_GET are valid only for the RS232 CM. Use these instructions to
read or set the RS232 communication signals.
Easy Book
154 Manual, 04/2012, A5E02486774-05
7.10.3 USS instructions

S7-1200 supports the USS protocol and provides instructions that are specifically designed
for communicating with drives over the RS485 port of a CM or a CB. You can control the
physical drive and the read/write drive parameters with the USS instructions. Each RS485
CM or CB supports a maximum of 16 drives.
The USS_PORT instruction handles actual communication between the CPU and all the
drives attached to one CM or CB. Insert a different USS_PORT instruction for each CM or
CB in your application. Ensure that the user program executes the USS_PORT
instruction fast enough to prevent a communication timeout by the drive. Use the
USS_PORT instruction in a program cycle or any interrupt OB.
The USS_DRV instruction accesses a specified drive on the USS network. The input and
output parameters of the USS_DRV instruction are the status and controls for the drive. If
there are 16 drives on the network, your program must have at least 16 USS_DRV
instructions, with one instruction for each drive.
Ensure that the CPU executes the USS_DRV instruction at the rate that is required to
control the functions of the drive. Use the USS_DRV instruction only in a program cycle
OB.
The USS_RPM and USS_WPM instructions read and write the operating parameters of
the remote drive. These parameters control the internal operation of the drive. See the
drive manual for the definition of these parameters.
Your program can contain as many of these instructions as necessary. However, only
one read or write request can be active for any one drive at any given time. Use the
USS_RPM and USS_WPM instructions only in a program cycle OB.
An instance DB contains temporary storage and buffers for all of the drives on the USS
network connected to each CM or CB. The USS instructions for a drive use the instance DB
to share the information.
Calculating the time required for communicating with the drive

Communications with the drive are asynchronous to the CPU scan. The CPU typically
completes several scans before one drive communications transaction is completed.
The USS_PORT interval is the time required for one drive transaction. The table below
shows the minimum USS_PORT interval for each communication baud rate. Calling the
USS_PORT function more frequently than the USS_PORT interval will not increase the
number of transactions. The drive timeout interval is the amount of time that might be taken
for a transaction, if communications errors caused 3 tries to complete the transaction. By
default, the USS protocol library automatically does up to 2 retries on each transaction.
Table 7- 14 Calculating the time requirements
Baud rate Calculated minimum USS_PORT call Drive message interval timeout per
Interval ( milliseconds ) drive ( milliseconds )
1200 790 2370
2400 405 1215
4800 212.5 638
9600 116.3 349
Easy Book
Manual, 04/2012, A5E02486774-05 155
Baud rate Calculated minimum USS_PORT call Drive message interval timeout per
Interval ( milliseconds ) drive ( milliseconds )
19200 68.2 205
38400 44.1 133
57600 36.1 109
115200 28.1 85
7.10.4 Modbus instructions

The CPU supports Modbus communication over different networks:
Modbus RTU (Remote Terminal Unit) is a standard network communication protocol that
uses the RS232 or RS485 electrical connection for serial data transfer between Modbus
network devices. You can add PtP (Point to Point) network ports to a CPU with a RS232
or RS485 CM or a RS485 CB.
Modbus RTU uses a master/slave network where all communications are initiated by a
single Master device and slaves can only respond to a masters request. The master
sends a request to one slave address and only that slave address responds to the
command.
Modbus TCP (Transmission Control Protocol) is a standard network communication
protocol that uses the PROFINET connector on the CPU for TCP/IP communication. No
additional communication hardware module is required.
Modbus TCP uses client-server connections as a Modbus communication path. Multiple
client-server connections may exist, in addition to the connection between STEP 7 and
the CPU. Mixed client and server connections are supported up to the maximum number
of connections allowed by the CPU. Each MB_SERVER connection must use a unique
instance DB and IP port number. Only 1 connection per IP port is supported. Each
MB_SERVER (with its unique instance DB and IP port) must be executed individually for
each connection.
Note
Modbus TCP will only operate correctly with CPU firmware release V1.02 or later. An
attempt to execute the Modbus instructions on an earlier firmware version will result in an
error.
Table 7- 15 Modbus instructions
Type of communication Instruction

Modbus RTU (RS232 or RS485) MB_COMM_LOAD: One execution of MB_COMM_LOAD is used to set up PtP port
parameters like baud rate, parity, and flow control. After the CPU port is configured
for the Modbus RTU protocol, it can only be used by either the MB_MASTER or
MB_SLAVE instructions.
MB_MASTER: The Modbus master instruction enables the CPU to act as a Modbus
RTU master device and communicate with one or more Modbus slave devices.
MB_SLAVE: The Modbus slave instruction enables the CPU to act as a Modbus RTU
slave device and communicate with a Modbus master device.
Easy Book
156 Manual, 04/2012, A5E02486774-05
Type of communication Instruction

Modbus TCP (PROFINET) MB_CLIENT: Make client-server TCP connection, send command message, receive
response, and control the disconnection from the server.
MB_SERVER: Connect to a Modbus TCP client upon request, receive Modbus
message, and send response.
The Modbus instructions do not use communication interrupt events to control the
communication process. Your program must poll the MB_MASTER / MB_SLAVE or
MB_Client / MB_Server instructions for transmit and receive complete conditions.
A Modbus TCP client (master) must control the client-server connection with the
DISCONNECT parameter. The basic Modbus client actions are shown below.
1. Initiate a connection to a particular server (slave) IP address and IP port number
2. Initiate client transmission of a Modbus messages and receive the server responses
3. When required, initiate the disconnection of client and server to enable connection with a
different server.
Easy Book
Manual, 04/2012, A5E02486774-05 157
Easy Book
158 Manual, 04/2012, A5E02486774-05
PID is easy 8
STEP 7 provides the following PID instructions for the S7-1200 CPU:
The PID_Compact instruction is used to control technical processes with continuous
input- and output variables.
The PID_3Step instruction is used to control motor-actuated devices, such as valves that
require discrete signals for open- and close actuation.
Note
Changes that you make to the PID configuration and download in RUN mode do not take
effect until the CPU transitions from STOP to RUN mode.
Both PID instructions (PID_3Step and PID_Compact) can calculate the P-, I-, and D-
components during startup (if configured for "pretuning"). You can also configure the
instruction for "fine tuning" to allow you to optimize the parameters. You do not need to
manually determine the parameters.
Note
Execute the PID instruction at constant intervals of the sampling time (preferably in a cyclic
OB).
Because the PID loop needs a certain time to respond to changes of the control value, do
not calculate the output value in every cycle. Do not execute the PID instruction in the main
program cycle OB (such as OB 1).
The sampling time of the PID algorithm represents the time between two calculations of the
output value (control value). The output value is calculated during self-tuning and rounded to
a multiple of the cycle time. All other functions of PID instruction are executed at every call.
PID algorithm
The PID (Proportional/Integral/Derivative) controller measures the time interval between two
calls and then evaluates the results for monitoring the sampling time. A mean value of the
sampling time is generated at each mode changeover and during initial startup. This value is
used as reference for the monitoring function and is used for calculation. Monitoring includes
the current measuring time between two calls and the mean value of the defined controller
sampling time.
Easy Book
Manual, 04/2012, A5E02486774-05 159
PID is easy
The output value for the PID controller consists of three components:
P (proportional): When calculated with the "P" component, the output value is proportional
to the difference between the setpoint and the process value (input value).
I (integral): When calculated with the "I" component, the output value increases in
proportion to the duration of the difference between the setpoint and the process value
(input value) to finally correct the difference.
D (derivative): When calculated with the "D" component, the output value increases as a
function of the increasing rate of change of the difference between the setpoint and the
process value (input value). The output value is corrected to the setpoint as quickly as
possible.
The PID controller uses the following formula to calculate the output value for the
PID_Compact instruction.
1 TD s
y = Kp [ (b w - x) + T s
I
(w - x) +
a TD s + 1
(c w - x) ]
y Output value x Process value
w Setpoint value s Laplace operator
Kp Proportional gain a Derivative delay coefficient
(P component) (D component)
T1 Integral action time b Proportional action weighting
(I component) (P component)
TD Derivative action time c Derivative action weighting
(D component) (D component)
The PID controller uses the following formula to calculate the output value for the PID_3Step
instruction.
1 TD s
[
y = K p s (b w - x) +
TI s
(w - x) +
a TD s + 1
(c w - x) ]
Easy Book
160 Manual, 04/2012, A5E02486774-05
PID is easy
8.1 Inserting the PID instruction and technological object

STEP 7 provides two instructions for PID control:
The PID_Compact instruction and its associated technological object provide a universal
PID controller with tuning. The technological object contains all of the settings for the
control loop.
The PID_3Step instruction and its associated technological object provide a PID
controller with specific settings for motor-activated valves. The technological object
contains all of the settings for the control loop. The PID_3Step controller provides two
additional Boolean outputs.
After creating the technological object, you must configure the parameters (Page 177). You
also adjust the autotuning parameters ("pretuning" during startup or manual "fine tuning") to
commission the operation of the PID controller (Page 179).
Table 8- 1 Inserting the PID instruction and the technological object
When you insert a PID instruction into your user program,

STEP 7 automatically creates a technology object and an
instance DB for the instruction. The instance DB contains
all of the parameters that are used by the PID instruction.
Each PID instruction must have its own unique instance
DB to operate properly.
After inserting the PID instruction and creating the
technological object and instance DB, you configure the
parameters for the technological object (Page 177).
Easy Book
Manual, 04/2012, A5E02486774-05 161
PID is easy
Table 8- 2 (Optional) Creating a technological object from the project navigator
You can also create technological objects for your

project before inserting the PID instruction. By
creating the technological object before inserting a
PID instruction into your user program, you can
then select the technological object when you insert
the PID instruction.
To create a technological object, double-click the

"Add new object" icon in the project navigator.
Click the "Control" icon and select the technological

object for the type of PID controller (PID_Compact
or PID_3Step). You can create an optional name
for the technological object.
Click "OK" to create the technological object.
Easy Book
162 Manual, 04/2012, A5E02486774-05
PID is easy
8.2 PID_Compact instruction

The PID controller uses the following formula to calculate the output value for the
PID_Compact instruction.
1 TD s
y = Kp [ (b w - x) + T s
I
(w - x) +
a TD s + 1
(c w - x) ]
Table 8- 3 PID_Compact instruction

"PID_Compact_1"( PID_Compact provides a PID controller with
Setpoint:=_real_in_, self-tuning for automatic and manual mode.
Input:=_real_in_, PID_Compact is a PIDT1 controller with
Input_PER:=_word_in_, anti-windup and weighting of the P- and D-
ManualEnable:=_bool_in_, component.
ManualValue:=_real_in_,
Reset:=_bool_in_,
ScaledInput=>_real_out_,
Output=>_real_out_,
Output_PER=>_word_out_,
Output_PWM=>_bool_out_,
SetpointLimit_H=>_bool_out_,
SetpointLimit_L=>_bool_out_,
InputWarning_H=>_bool_out_,
InputWarning_L=>_bool_out_,
State=>_int_out_,
Error=>_dword_out_);
1 STEP 7 automatically creates the technological object and instance DB when you insert the instruction. The instance
DB contains the parameters of the technological object.
2 In the SCL example, "PID_Compact_1" is the name of the instance DB.
Parameter and type Data type Description

Setpoint IN Real Setpoint of the PID controller in automatic mode. Default value: 0.0
Input IN Real Process value. Default value: 0.0
You must also set sPid_Cmpt.b_Input_PER_On = FALSE.
Easy Book
Manual, 04/2012, A5E02486774-05 163
PID is easy

Input_PER IN Word Analog process value (optional). Default value: W#16#0
You must also set sPid_Cmpt.b_Input_PER_On = TRUE.
ManualEnable IN Bool Enables or disables the manual operation mode. Default value: FALSE:
PID_Compact V1.0 and V1.2: When the CPU transitions to RUN, if
the ManualEnable = TRUE, PID_Compact starts in manual mode. It
is not necessary for a FALSE to TRUE transition to place the
PID_Compact into manual mode.
PID_Compact V1.1: When the CPU transitions to RUN and the
ManualEnable = TRUE, the PID Compact starts in the last state. A
transition from TRUE to FALSE to TRUE is required to place the
PID_Compact in manual mode.
ManualValue IN Real Process value for manual operation. Default value: 0.0
Reset IN Bool The Reset parameter restarts the controller. Default value: FALSE
See the "Response to Reset" section below for PID_Compact V1.1 and
V1.0 Reset response diagrams.
ScaledInput OUT Real Scaled process value. Default value: 0.0
Output1 OUT Real Output value. Default value: 0.0
Output_PER1 OUT Word Analog output value. Default value: W#16#0
Output_PWM1 OUT Bool Output value for pulse width modulation. Default value: FALSE
SetpointLimit_H OUT Bool Setpoint high limit. Default value: FALSE
If SetpointLimit_H = TRUE, the absolute upper limit of the setpoint is
reached. Default value: FALSE
SetpointLimit_L OUT Bool Setpoint low limit. Default value: FALSE
If SetpointLimit_L = TRUE, the absolute lower limit of the setpoint is
reached. Default value: FALSE
InputWarning_H OUT Bool If InputWarning_H = TRUE, the process value reached or exceeded the
upper warning limit. Default value: FALSE
InputWarning_L OUT Bool If InputWarning_L = TRUE, the process value reached the lower
warning limit. Default value: FALSE
State OUT Int Current operating mode of the PID controller. Default value: 0
Use sRet.i_Mode to change the mode.
State = 0: Inactive
State = 1: Pretuning
State = 2: Manual fine tuning
State = 3: Automatic mode
State = 4: Manual mode
ErrorBits OUT DWord The PID_Compact instruction ErrorBits parameters table (Page 168)
defines the error messages. Default value: DW#16#0000 (no error)
1 The outputs of the Output, Output_PER, and Output_PWM parameters can be used in parallel.
Easy Book
164 Manual, 04/2012, A5E02486774-05
PID is easy
Response to Reset
The response to Reset = TRUE depends on the version of the PID_Compact instruction.
Reset response PID_Compact V1.1
A rising edge at Reset resets the errors and warnings and clears the integral action. A falling
edge at Reset triggers a change to the most recently active operating mode.
5HVHW

WPV
LB0RGH

WPV
6WDWH

WPV

Activation
Error
Reset
Easy Book
Manual, 04/2012, A5E02486774-05 165
PID is easy
Reset response PID_Compact V1.0

A rising edge at Reset resets the errors and warnings and clears the integral action. The
controller is not reactivated until the next edge at i_Mode.
5HVHW

WPV
LB0RGH

WPV
6WDWH

WPV
Activation
Error
Reset
Easy Book
166 Manual, 04/2012, A5E02486774-05
PID is easy
Operation of the PID_Compact controller

EB,QSXWB3(5B2Q
&53B,1 6FDOH 39B$/50 ,QSXW:DUQLQJB+
,QSXWB3(5
,QSXW:DUQLQJB/

,QSXW
3,'7
$QWL:LQGXS
/LPLW
6HWSRLQW X
2XWSXW
0DQXDO(QDEOH ,19 EB,QY&WUO

/LPLW
&53B287
2XWSXWB3(5
0DQXDO9DOXH

3:0
2XWSXWB3:0
Figure 8-1 Operation of the PID_Compact controller
6HWSRLQWZ E
$QWL:LQGXS
.3
/,0,7 , \
6FDOHG,QSXW[ '7

Figure 8-2 Operation of the PID_Compact controller as a PIDT1 controller with anti-windup
Easy Book
Manual, 04/2012, A5E02486774-05 167
PID is easy
8.3 PID_Compact instruction ErrorBit parameters
8.3 PID_Compact instruction ErrorBit parameters

If several errors are pending, the values of the error codes are displayed by means of binary
addition. The display of error code 0003, for example, indicates that the errors 0001 and
0002 are also pending.
Table 8- 5 PID_Compact instruction ErrorBit parameters
ErrorBit (DW#16#...) Description

0000 No error
0001 The "Input" parameter is outside the process value limits.
Input > sPid_Cmpt.r_Pv_Hlmor
Input < sPid_Cmpt.r_Pv_Llm
You cannot start the actuator again until you eliminate the error.
0002 Invalid value at parameter "Input_PER". Check whether an error is pending
at the analog input.
0004 Error during fine tuning Oscillation of the process value could not be
maintained.
0008 Error while starting pre-tuning. The process value is too close to the
setpoint. Start fine tuning.
0010 The setpoint was changed during controller tuning.
0020 Pre-tuning may not be carried out in automatic mode or during fine tuning.
0040 Error in fine tuning The setpoint is too close to the setpoint limits.
0080 Incorrect configuration of output value limits.
Check to see if the limits of the output value are configured correctly and
match the direction in which the control is operating.
0100 Error during controller tuning has resulted in invalid parameters.
0200 Invalid value at parameter "Input": Numerical format of value is invalid.
0400 Calculating the output value failed. Check the PID parameters.
0800 Sampling time error: PID_Compact is not called within the sampling time of
the cyclic interrupt OB.
1000 Invalid value at parameter "Setpoint": Numerical format of value is invalid.
Easy Book
168 Manual, 04/2012, A5E02486774-05
PID is easy
8.4 PID_3STEP instruction

The PID controller uses the following formula to calculate the output value for the PID_3Step
instruction.
1 TD s
[
y = K p s (b w - x) +
TI s
(w - x) +
a TD s + 1
(c w - x) ]
Table 8- 6 PID_3Step instruction

"PID_3Step_1"( PID_3Step configures a PID controller with
SetpoInt:=_real_in_, self-tuning capabilities that has been
Input:=_real_in_, optimized for motor-controlled valves and
ManualValue:=_real_in_, actuators. It provides two Boolean outputs.
Feedback:=_real_in_, PID_3Step is a PIDT1controller with anti-
InputPer:=_word_in_, windup and weighting of the P- and D-
FeedbackPer:=_word_in_, components.
ManualEnable:=_bool_in_,
ManualUP:=_bool_in_,
ManualDN:=_bool_in_,
ActuatorH:=_bool_in_,
ActuatorL:=_bool_in_,
Reset:=_bool_in_,
ScaledInput=>_real_out_,
ScaledFeedback=>_real_out_,
ErrorBits=>_dword_out_,
OutputPer=>_word_out_,
State=>_int_out_,
OutputUP=>_bool_out_,
OutputDN=>_bool_out_,
SetpoIntLimitH=>_bool_out_,
SetpoIntLimitL=>_bool_out_,
InputWarningH=>_bool_out_,
InputWarningL=>_bool_out_,
Error=>_bool_out_);
1 STEP 7 automatically creates the technological object and instance DB when you insert the instruction. The instance
DB contains the parameters of the technological object.
2 In the SCL example, "PID_3Step_1" is the name of the instance DB.
Easy Book
Manual, 04/2012, A5E02486774-05 169
PID is easy

Setpoint IN Real Setpoint of the PID controller in automatic mode. Default value: 0.0
Input IN Real Process value. Default value: 0.0
You must also set Config.InputPEROn = FALSE.
Input_PER IN Word Analog process value (optional). Default value: W#16#0
You must also set Config.InputPEROn = TRUE.
ManualEnable IN Bool Enables or disables the manual operation mode. Default value: FALSE
On the edge of the change from FALSE to TRUE, the PID controller
switches to manual mode, State = 4, and Retain.Mode remains
unchanged.
On the edge of the change from TRUE to FALSE, the PID controller
switches to the last active operating mode and
State = Retain.Mode.
ManualUP IN Bool In manual mode, every rising edge opens the valve by 5% of the total
actuating range, or for the duration of the minimum motor actuation
time. ManualUP is evaluated only if you are not using Output_PER and
there is no position feedback. Default value: FALSE
If Output_PER is FALSE, the manual input turns Output_UP on for
the time that corresponds to a movement of 5% of the device.
If Config.ActuatorEndStopOn is TRUE, then Output_UP does not
come on if Actuator_H is TRUE.
ManualDN IN Bool In manual mode, every rising edge closes the valve by 5% of the total
actuating range, or for the duration of the minimum motor actuation
time. ManualDN is evaluated only if you are not using Output_PER and
there is no position feedback. Default value: FALSE
If Output_PER is FALSE, the manual input turns Output_DN on for
the time that corresponds to a movement of 5% of the device.
If Config.ActuatorEndStopOn is TRUE, then Output_DN does not
turn on if Actuator_L is TRUE.
ManualValue IN Real Process value for manual operation. Default value: 0.0
In manual mode, you specify the absolute position of the valve.
ManualValue is evaluated only if you are using OutputPer, or if position
feedback is available. Default value: 0.0
Feedback IN Real Position feedback of the valve. Default value: 0.0
To use Feedback, then set Config.FeedbackPerOn = FALSE.
Feedback_PER IN Word Analog feedback of the valve position. Default value: W#16#0
To use Feedback_PER, set Config.FeedbackPerOn = TRUE.
Feedback_PER is scaled, using the following parameters:
Config.FeedbackScaling.LowerPointIn
Config.FeedbackScaling.UpperPointIn
Config.FeedbackScaling.LowerPointOut
Config.FeedbackScaling.UpperPointOut
Actuator_H IN Bool If Actuator_H = TRUE, the valve is at the upper end stop and is no
longer moved in this direction. Default value: FALSE
Easy Book
170 Manual, 04/2012, A5E02486774-05
PID is easy

Actuator_L IN Bool If Actuator_L = TRUE, the valve is at the lower end stop and is no
longer moved in this direction. Default value: FALSE
Reset IN Bool Restarts the PID controller. Default value: FALSE
If FALSE to TRUE edge:
"Inactive" operating mode
Input value = 0
Interim values of the controller are reset. (PID parameters are
retained.)
If TRUE to FALSE edge, change to the most recent active mode.
ScaledInput OUT Real Scaled process value
ScaledFeedback OUT Real Scaled valve position
Output_PER OUT Word Analog output value. If Config.OutputPerOn = TRUE, the parameter
Output_PER is used.
Output_UP OUT Bool Digital output value for opening the valve. Default value: FALSE
If Config.OutputPerOn = FALSE, the parameter Output_UP is used.
Output_DN OUT Bool Digital output value for closing the valve. Default value: FALSE
If Config.OutputPerOn = FALSE, the parameter Output_DN is used.
SetpointLimitH OUT Bool Setpoint high limit. Default value: FALSE
If SetpointLimitH = TRUE, the absolute upper limit of the setpoint is
reached. In the CPU, the setpoint is limited to the configured absolute
upper limit of the actual value.
SetpointLimitL OUT Bool Setpoint low limit. Default value: FALSE
If SetpointLimitL = TRUE, the absolute lower limit of the setpoint is
reached. In the CPU the setpoint is limited to the configured absolute
lower limit of the actual value.
InputWarningH OUT Bool If InputWarningH = TRUE, the input value has reached or exceeded the
upper warning limit. Default value: FALSE
InputWarningL OUT Bool If InputWarningL = TRUE, the input value has reached or exceeded the
lower warning limit. Default value: FALSE
State OUT Int Current operating mode of the PID controller. Default value: 0
Use Retain.Mode to change the operating mode:
State = 0: Inactive
State = 1: Pretuning
State = 2: Manual fine tuning
State = 3: Automatic mode
State = 4: Manual mode
State = 5: Substitute output value approach
State = 6: Transition time measurement
State = 7: Substitute output value approach with error monitoring
State = 8: Error monitoring
Error OUT Bool If Error = TRUE, at least one error message is pending. Default value:
FALSE
ErrorBits OUT DWord The PID_3STEP instruction ErrorBits parameters table (Page 175)
defines the error messages. Default value: DW#16#0000 (no error)
Easy Book
Manual, 04/2012, A5E02486774-05 171
PID is easy
E
6HWSRLQWZ
'7 ' .
F 3
\
'HDGB%

7L ,
6FDOHG,QSXW[
)DF7W $QWLZLQGXS
Figure 8-3 Operation of the PID_3Step controller as a PIDT1 controller with anti-windup
Easy Book
172 Manual, 04/2012, A5E02486774-05
PID is easy
39B$/50 ,QSXW:DUQLQJB+
,QSXW:DUQLQJB/
,QSXW3HU2Q
$QWL:LQGXS
&53B,1 6FDOH
,QSXWB3(5
)DF
,QW

,QSXW 3,'7 Y
$QWL:LQGXS

/LPLW
6HWSRLQW
2XWSXW3HU2Q

5RFB/LP
/LPLW
0DQXDO(QDEOH
&53B287 2XWSXWB3(5
0DQXDO9DOXH
)$&

0DQXDO(QDEOH
0DQXDOB83
3XOVH2XW 2XWSXWB83
$GHDGB% 7KU6WS 2XWSXWB'1
0DQXDOB'1

Figure 8-4 Operation of the PID_3Step controller without position feedback
Easy Book
Manual, 04/2012, A5E02486774-05 173
PID is easy
39B$/50 ,QSXW:DUQLQJB+
,QSXW:DUQLQJB/

,QSXW3HU2Q
&53B,1 6FDOH $QWL:LQGXS
,QSXWB3(5

,QW /LPLW )DF

,QSXW 3,'7
;
$QWL:LQGXS
9
/LPLW
6HWSRLQW
)HHGEDFN3HU2Q
&53B,1 6FDOH
)HHGEDFNB3(5

)HHGEDFN
0DQXDO(QDEOH
2XWSXW3HU2Q &53B287 2XWSXWB3(5

0DQXDO9DOXH

0DQXDO(QDEOH
0DQXDOB83 2XWSXWB83
3XOVH2XW
$GHDGB% 7KU6WS

0DQXDOB'1 2XWSXWB'1

Figure 8-5 Operation of the PID_3Step controller the position feedback enabled
Easy Book
174 Manual, 04/2012, A5E02486774-05
PID is easy
8.5 PID_3STEP instruction ErrorBit parameters

If several errors are pending, the values of the error codes are displayed by means of binary
addition. The display of error code 0003, for example, indicates that the errors 0001 and
0002 are also pending.
Table 8- 8 PID_3STEP instruction ErrorBit parameters

0000 No error
0001 The "Input" parameter is outside the process value limits:
Input > Config.InputUpperLimit or
Input < Config.InputLowerLimit
If ActivateRecoverMode = TRUE and ErrorBehaviour = 1, the actuator
moves to the substitute output value. If ActivateRecoverMode = TRUE and
ErrorBehaviour = 0, the actuator stops in its current position. If
ActivateRecoverMode = FALSE, the actuator stops in its current position.
PID_3STEP V1.1: You can move the actuator in manual mode.
PID_3STEP V1.0: Manual mode is not possible in this state. You cannot
start the actuator again until you eliminate the error.
0002 Invalid value at parameter "Input_PER". Check whether an error is pending
at the analog input.
If automatic mode was active before the error occurred,
ActivateRecoverMode = TRUE and the error is no longer pending,
PID_3STEP switches back to automatic mode.
0004 Error during fine tuning Oscillation of the process value could not be
maintained.
0008 Error while starting pre-tuning. The process value is too close to the
setpoint. Start fine tuning.
0010 The setpoint may not be changed during fine tuning.
0020 Pre-tuning may not be carried out in automatic mode or during fine tuning.
0040 Error in fine tuning The setpoint is too close to the setpoint limits.
0080 Error in pre-tuning. Incorrect configuration of output value limits.
Check to see if the limits of the output value are configured correctly and
match the direction in which the control is operating.
0100 Error during fine tuning has resulted in invalid parameters.
0200 Invalid value at parameter "Input": Numerical format of value is invalid.
0400 Calculating the output value failed. Check the PID parameters.
0800 Sampling time error: PID_3STEP is not called within the sampling time of
the cyclic interrupt OB.
Easy Book
Manual, 04/2012, A5E02486774-05 175
PID is easy

1000 Invalid value at parameter "Setpoint": Numerical format of value is invalid.
2000 Invalid value at parameter Feedback_PER.
Check whether an error is pending at the analog input.
The actuator cannot be moved to the substitute output value and does not
move from the current position. Manual mode is not possible in this state.
You have to disable position feedback (Config. FeedbackOn = FALSE) to
move the actuator from this state.
4000 Invalid value at parameter Feedback. Numerical format of value is invalid.
You have to disable position feedback (Config. FeedbackOn = FALSE) to
move the actuator from this state.
8000 Error in digital position feedback. Actuator_H = TRUE and Actuator_L =
TRUE.
You have to disable "Endstop signals actuator" (Config.ActuatorEndStopOn
= FALSE) to move the actuator from this state.
Easy Book
176 Manual, 04/2012, A5E02486774-05
PID is easy
8.6 Configuring the PID controller
The parameters of the technological object determine the operation of the PID
controller. Use the icon to open the configuration editor.
Figure 8-6 Configuration editor for PID_Compact (Basic settings)
Table 8- 9 Sample configuration settings for the PID_Compact instruction
Settings Description
Basic Controller type Selects the engineering units.
Invert the control logic Allows selection of a reverse-acting PID loop.
If not selected, the PID loop is in direct-acting mode and the output of PID loop
increases if input value < setpoint.
If selected, the output of the PID loop increases if the input value > setpoint.
Enable last mode after Restarts the PID loop after it is reset or if an input limit has been exceeded and
CPU restart returned to the valid range.
Input Selects either the Input parameter or the Input_PER parameter (for analog) for the
process value. Input_PER can come directly from an analog input module.
Output Selects either the Output parameter or the Output_PER parameter (for analog) for
the output value. Output_PER can go directly to an analog output module.
Process Scales both the range and the limits for the process value. If the process value goes below the low limit or
value above the high limit, the PID loop goes to inactive mode and sets the output value to 0.
To use Input_PER, you must scale the analog process value (input value).
Easy Book
Manual, 04/2012, A5E02486774-05 177
PID is easy
Figure 8-7 Configuration editor for PID_3Step (Basic settings)
Table 8- 10 Sample configuration settings for the PID_3Step instruction
Basic Controller type Selects the engineering units.
Invert the control logic Allows selection of a reverse-acting PID loop.
If not selected, the PID loop is in direct-acting mode, and the output of PID loop
increases if the input value < setpoint).
If selected, the output of the PID loop increases if the input value > setpoint.
Enable last mode after Restarts the PID loop after it is reset or if an input limit has been exceeded and
CPU restart returned to the valid range.
Input Selects either the Input parameter or the Input_PER parameter (for analog) for the
process value. Input_PER can come directly from an analog input module.
Output Selects either to use the digital outputs (Output_UP and Output_DN) or to use the
analog output (Output_PER) for the output value.
Feedback Selects the type of device status returned to the PID loop:
No feedback (default)
Feedback
Feedback_PER
Process Scales both the range and the limits for the process value. If the process value goes below the low limit or
value above the high limit, the PID loop goes to inactive mode and sets the output value to 0.
To use Input_PER, you must scale the analog process value (input value).
Actuator Motor transition Sets the time from open to close for the valve. (Locate this value on the data sheet or
time the faceplate of the valve.)
Minimum ON time Sets the minimum movement time for the valve. (Locate this value on the data sheet or
the faceplate of the valve.)
Minimum OFF Sets the minimum pause time for the valve. (Locate this value on the data sheet or the
time faceplate of the valve.)
Error behavior Defines the behavior of the valve when an error is detected or when the PID loop is
reset. If you select to use a substitute position, enter the "Safety position". For analog
feedback or analog output, select a value between the upper or lower limit for the
output. For digital outputs, you can choose only 0% (off) or 100% (on).
Easy Book
178 Manual, 04/2012, A5E02486774-05
PID is easy
8.7 Commissioning the PID controller
Scale Position "High stop" and "Lower limit stop" define the maximum positive position (full-open)
Feedback1 and the maximum negative position (full-closed). "High stop" must be greater than
"Lower limit stop".
"High limit process value" and "Low limit process value" define the upper and lower
positions of the valve during tuning and automatic mode.
"FeedbackPER" ("Low" and "High") defines the analog feedback of the valve
position. "FeedbackPER High" must be greater than "FeedbackPER Low".
1 "Scale Position Feedback" is editable only if you enabled "Feedback" in the "Basic" settings.
Use the commissioning editor to configure the PID controller for autotuning at startup
and for autotuning during operation. To open the commissioning editor, click the icon
on either the instruction or the project navigator.
Table 8- 11 Sample configuration screen (PID_3Step)
Measurement: To display the setpoint, the

process value (input value) and the output value in a
real-time trend, enter the sample time and click the
"Start" button.
Tuning mode: To tune the PID loop, select either
"Pretuning" or "Fine tuning" (manual) and click the
"Start" button. The PID controller runs through
multiple phases to calculate system response and
update times. The appropriate tuning parameters are
calculated from these values.
After the completion of the tuning process, you can

store the new parameters by clicking the "Upload PID
parameters" button in the "PID Parameters" section of
the commissioning editor.
If an error occurs during tuning, the output value of the
PID goes to 0. The PID mode then is set to "inactive"
mode. The status indicates the error.
Easy Book
Manual, 04/2012, A5E02486774-05 179
PID is easy
Easy Book
180 Manual, 04/2012, A5E02486774-05
Web server for easy Internet connectivity 9
The Web server provides Web page access to data about your CPU and to the process data
within the CPU. A set of standard Web pages are integrated into the firmware of the CPU.
With these Web pages, you access the CPU with the Web browser of your PC. The standard
web pages allow you to perform a variety of functions:
You can change the operating mode (STOP and RUN) of the CPU.
You can monitor and modify the status of the PLC tags.
You can view and download any data logs being collected by the CPU.
You can view the diagnostic buffer of the CPU.
You can update the firmware of the CPU.
The Web server also allows you to create user-defined Web pages that can access CPU
data. You can develop these pages with the HTML authoring software of your choice. You
insert pre-defined "AWP" (Automation Web Programming) commands in your HTML code to
access the data in the CPU.
You can use any Web browser that supports HTTP version 1.1.
9.1 Easy to use the standard Web pages

Using the standard Web pages is easy! You only have to enable the Web server when
configuring the CPU.
The Start page displays a representation of

the CPU to which you are connected and lists
general information about the CPU.
If you log in as the "admin" user, you can
change the operating mode of the CPU
(STOP and RUN) or flash the LEDs.
The Variable Status page allows you to

monitor or modify any of the I/O or memory
data in your CPU. You can enter a direct
address (such as I0.0), a PLC tag name, or a
tag from a specific program block. The data
values automatically refresh until you disable
the automatic refresh option.
Easy Book
Manual, 04/2012, A5E02486774-05 181
Web server for easy Internet connectivity
9.1 Easy to use the standard Web pages
The Diagnostic Buffer page displays the

diagnostic buffer. You can select the range of
diagnostic entries to be displayed.
The diagnostic entries list the events that
occurred and the CPU time and date of when
the event occurred. Select the individual event
to display detailed information about that
event.
The Data Logs page allows you to view or

download a specified number of data log
entries. The Web server downloads data logs
to your PC in U.S. comma-separated-value
file format (.csv). For more information, see
the section on data logs (Page 106).
The Update Firmware page allows you to

update the version of firmware in your CPU.
Easy Book
182 Manual, 04/2012, A5E02486774-05
9.2 Constraints that can affect the use of the Web server
Other standard web pages display information about the CPU (such as the serial number,
the version and the order number), about the communication parameters (such as network
addresses, physical properties of the communication interfaces, and communication
statistics), and about the modules in the local rack.
WARNING
Unauthorized access to the CPU or changing PLC variables to invalid values could disrupt
process operation and could result in death, severe personal injury and/or property
damage.
Because enabling the Web server allows "admin" users to perform operating mode
changes, writes to PLC data, and firmware updates, Siemens recommends that you
observe the following security practices:
Enable access to the Web server only with the HTTPS protocol.
Password-protect the CPU (Page 79) with a strong password. Strong passwords are at
least eight characters in length, mix letters, numbers, and special characters, are not
words that can be found in a dictionary, and are not names or identifiers that can be
derived from personal information. Keep the password secret and change it frequently.
Perform error-checking and range-checking on your variables in your program logic
because Web page users can change PLC variables to invalid values.
The following IT considerations can affect your use of the Web server:
Typically, you must use the IP address of the CPU to access the standard Web pages or
user-defined Web pages. If your Web browser does not allow connecting directly to an IP
address, see your IT administrator. If your local policies support DNS, you can connect to
the IP address through a DNS entry to that address.
Firewalls, proxy settings, and other site-specific restrictions can also restrict access to the
CPU. See your IT administrator to resolve these issues.
The standard Web pages use JavaScripts and cookies. If JavaScripts or cookies are
disabled in your Web browser, enable them. If you cannot enable them, some features
will be restricted. Use of JavaScripts and cookies in user-defined Web pages is optional.
If used, they must be enabled in your browser.
Secure Sockets Layer (SSL) is supported by the Web server. You can access the
standard Web pages and user-defined Web pages with an URL of either
http://ww.xx.yy.zz or https://ww.xx.yy.zz, where "ww.xx.yy.zz" represents the IP address
of the CPU.
Siemens provides a security certificate for secure access to the Web server. From the
Introduction standard Web page, you can download and import the certificate into the
Internet options of your Web browser. If you choose to not import the certificate, you will
get a security verification prompt every time you access the Web server with https://.
Easy Book
Manual, 04/2012, A5E02486774-05 183
Number of connections
The Web server supports a maximum of 30 active HTTP connections. These 30 connections
can be consumed in various ways, depending on the Web browser that you use and the
number of different objects per page (.css files, images, additional .html files). Some
connections persist while the page is being displayed; others are released after the initial
connection.
If, for example, you are using Mozilla Firefox 8, which supports a maximum of six persistent
connections, you could use five browser or browser tab instances before the Web server
starts dropping connections. In the case where a page is not using all six connections, you
could have additional browser or browser tab instances.
Also be aware that page performance can be affected by the number of active connections.
9.2.1 Constraints when JavaScript is disabled
Disabling JavaScript restricts some features

The standard Web pages are implemented using HTML, JavaScripts, and cookies. Unless
your site restricts the use of JavaScripts and cookies, enable them for the pages to function
properly. If you cannot enable JavaScripts for your Web browser, the features controlled by
JavaScripts cannot run.
Table 9- 1 Web pages affected when JavaScript is disabled
Standard Web page Effect

General Data on the pages does not update dynamically. You must
manually refresh the page with the refresh icon to view fresh
data.
You cannot log in as the "admin" user.
Module information You cannot filter the data.
You cannot sort fields.
Diagnostic Displaying the event details: Without JavaScript, you must click
the event field hyperlink of a diagnostic buffer entry to see the
event data in the bottom section.
Changing the range of diagnostic buffer entries to view: Without
JavaScript, you use the drop-down list at the top to select the
range of diagnostic buffer entries to view, but you must then click
the "Go" link to update the diagnostic buffer page with the range
you selected from the drop down list.
Easy Book
184 Manual, 04/2012, A5E02486774-05
9.3 Easy to create user-defined web pages
Standard Web page Effect

Variable After you enter each variable, you must manually set the focus to
the "New variable" row to enter a new variable.
Selecting a display format does not automatically change the data
value display to the selected format. You must click the "Monitor
value" button to refresh the display with the new format.
Data Logs You cannot click a file name under "Recent entries" to open or
save a log file. You can, however, use the Download icon for the
same functionality.
The Data Logs page does not refresh.
The "+" and "-" buttons to increment and decrement the number
of entries have no effect.
Note that you can leave the Data Logs page and reenter to get
the most recent 25 entries.
9.2.2 Features restricted when cookies are not allowed

If your Web browser does not allow cookies you cannot log in with the "admin" user name.
9.3.1 Easy to create custom "user-defined" web pages

The S7-1200 Web server also provides the means for you to create your own application-
specific HTML pages that incorporate data from the PLC. Use the HTML editor of your
choice to create these pages, and then download them to the CPU from where they are
accessible from the standard Web pages.
HTML files with embedded AWP commands
Easy Book
Manual, 04/2012, A5E02486774-05 185
This process involves several tasks:

Create the HTML pages with an HTML editor, such as Microsoft Frontpage
Include AWP commands in HTML comments in the HTML code: The AWP commands
are a fixed set of commands for accessing CPU information.
Configure STEP 7 to read and process the HTML pages.
Generate the program blocks from the HTML pages.
Program STEP 7 to control the use of the HTML pages.
Compile and download the program blocks to the CPU.
Access the user-defined Web pages from your PC.
You can use the software package of your choice to create your own HTML pages for use
with the Web server. Be sure that your HTML code is compliant to the HTML standards of
the W3C (World Wide Web Consortium). STEP 7 does not perform any verification of your
HTML syntax.
You can use a software package that lets you design in WYSIWYG or design layout mode,
but you need to be able to edit your HTML code in pure HTML form. Most Web authoring
tools provide this type of editing; otherwise, you can always use a simple text editor to edit
the HTML code. Include the following line in your HTML page to set the charset for the page
to UTF-8:
<meta http-equiv="content-type" content="text/html; charset=utf-8">
Also be sure to save the file from the editor in UTF-8 character encoding:
You use STEP 7 to compile everything in your HTML pages into STEP 7 data blocks. These
data blocks consist of one control data block that directs the display of the Web pages and
one or more fragment data blocks that contain the compiled Web pages. Be aware that
extensive sets of HTML pages, particularly those with lots of images, require a significant
amount of load memory space for the fragment DBs. If the internal load memory of your CPU
is not sufficient for your user-defined Web pages, use a memory card to provide external
load memory.
To program your HTML code to use data from the S7-1200, you include AWP commands as
HTML comments. When finished, save your HTML pages to your PC and note the folder
path where you save them.
Refreshing user-defined Web pages

User-defined Web pages do not automatically refresh. It is your choice whether to program
the HTML to refresh the page or not. For pages that display PLC data, refreshing periodically
keeps the data current. For HTML pages that serve as forms for data entry, refreshing can
interfere with the user entering data. If you want your entire page to automatically refresh,
you can add this line to your HTML header, where "10" is the number of seconds between
refreshes:
<meta http-equiv="Refresh" content="10">
You can also use JavaScripts or other HTML techniques to control page or data refreshing.
For this, refer to documentation on HTML and JavaScript.
Easy Book
186 Manual, 04/2012, A5E02486774-05
9.3.2 Constraints specific to user-defined Web pages

The constraints for standard Web pages also apply to user-defined Web pages. In addition,
user-defined Web pages have some specific considerations.
Load memory space

Your user-defined Web pages become data blocks when you click "Generate blocks", which
require load memory space. If you have a memory card installed, you have up to the
capacity of your memory card as external load memory space for the user-defined Web
pages.
If you do not have a memory card installed, these blocks take up internal load memory
space, which is limited according to your CPU model.
You can check the amount of load memory space that is used and the amount that is
available from the Online and Diagnostic tools in STEP 7. You can also look at the properties
for the individual blocks that STEP 7 generates from your user-defined Web pages and see
the load memory consumption.
Note
If you need to reduce the space required for your user-defined Web pages, reduce your use
of images if applicable.
Easy Book
Manual, 04/2012, A5E02486774-05 187
9.3.3 Configuration of a user-defined Web page

To configure the user-defined Web pages, edit the "Web server" properties of the CPU.
After you enable the Web server functionality, enter the following information:
Name and the current location of the HTML default start page to generate the DBs for the
user-defined Web pages.
Name for your application (optional). The application name is used to further
subcategorize or group web pages. When an application name exists, the URL will
appear in the following format:
http://ww.xx.yy.zz/awp/<application name>/<pagename>.html
Filename extensions to be examined for the presence of AWP commands. By default,
STEP 7 analyzes files with .htm, .html, or .js extensions. If you have additional file
extensions, append them.
Identification numbers for the control DB number and the initial fragment DB.
After configuring the Web server, click the "Create blocks" button to generate the DBs from
the HTML pages. After you generate the DBs, your Web pages are a part of your user
program. The control data block for the operation of your Web pages, and the "fragment"
DBs contain all of the HTML pages.
Easy Book
188 Manual, 04/2012, A5E02486774-05
9.3.4 Using the WWW instruction

The WWW instruction allows your user-defined Web pages to be accessible from the
standard Web pages. Your user program only has to execute the WWW instruction once to
enable access to the user-defined Web pages. You might, however, choose to make the
user-defined Web pages available only under certain circumstances. Your user program
could then call the WWW instruction according to your application requirements.
Table 9- 2 WWW instruction

ret_val := #WWW( Identifies the control DB to be used for the user-
defined Web pages.
ctrl_db:=_uint_in_); The control data block is the input parameter to
the WWW instruction and specifies the content of
the pages as represented in the fragment data
blocks, as well as state and control information.
Your user program typically uses the control DB directly as created by the "Create blocks"
process, with no additional manipulation. However, the user program can set global
commands in the control DB to deactivate the web server, or to subsequently reactivate it.
Also, for user-defined pages that you create as manual fragment DBs, the user program
must control the behavior of these pages through a request table in the control DB.
Easy Book
Manual, 04/2012, A5E02486774-05 189
Easy Book
190 Manual, 04/2012, A5E02486774-05
Motion control is easy 10
The CPU provides motion control functionality for the operation of stepper motors and servo
motors with pulse interface. The motion control functionality takes over the control and
monitoring of the drives.
The "Axis" technology object configures the mechanical drive data, drive interface,
dynamic parameters, and other drive properties.
You configure the pulse and direction outputs of the CPU for controlling the drive.
Your user program uses the motion control instructions to control the axis and to initiate
motion tasks.
Use the PROFINET interface to establish the online connection between the CPU and
the programming device. In addition to the online functions of the CPU, additional
commissioning and diagnostic functions are available for motion control.
Note
Changes that you make to the motion control configuration and download in RUN mode
do not take effect until the CPU transitions from STOP to RUN mode.
S 6,0$7,&6
PROFINET
Pulse and direction outputs
,
,
,
,
,
,
,
,
,
,
,
,
,
,
',
Power section for stepper motor

5816723
(5525
0$,17
&38&
'&'&'&
Power section for servo motor

'

The DC/DC/DC variants of the CPU S7-1200 have onboard

;31/$1
outputs for direct control of drives. The relay variants of the

CPU require the signal board with DC outputs for drive
control.
A signal board (SB) expands the onboard I/O to include a few additional I/O points. An SB
with 2 digital outputs can be used as pulse and direction outputs to control one motor. An SB
with 4 digital outputs can be used as pulse and direction outputs to control two motors. Built-
in relay outputs cannot be used as pulse outputs to control motors.
Easy Book
Manual, 04/2012, A5E02486774-05 191
Motion control is easy
Note
Pulse-train outputs cannot be used by other instructions in the user program
When you configure the outputs of the CPU or signal board as pulse generators (for use with
the PWM or motion control instructions), the corresponding output addresses (Q0.0 to Q0.3,
Q4.0 to Q4.3) are removed from the Q memory and cannot be used for other purposes in
your user program. If your user program writes a value to an output used as a pulse
generator, the CPU does not write that value to the physical output.
Table 10- 1 Maximum number of controllable drives
Type of CPU No SB installed With an SB With an SB

(2 x DC outputs) (4 x DC outputs)
CPU 1211C DC/DC/DC 2 2 2
AC/DC/RLY 0 1 2
DC/DC/RLY 0 1 2
AC/DC/RLY 0 1 2
DC/DC/RLY 0 1 2
AC/DC/RLY 0 1 2
DC/DC/RLY 0 1 2
AC/DC/RLY 0 1 2
DC/DC/RLY 0 1 2
Table 10- 2 Limit frequencies of pulse outputs
Pulse output Frequency

Onboard 2 PTO: 2 Hz f 100 KHz
2 PTO: 2 Hz f 20 KHz
Standard SB 2 Hz f 20 KHz
High-speed (200 KHz) SBs MC V2 instructions: 2 Hz f 200 KHz
MC V1 instructions: 2 Hz f 100 KHz 1
1 MC V1 instructions support a maximum frequency of 100 KHz.
NOTICE
The maximum pulse frequency of the pulse output generators is 100 KHz for the digital
outputs of the CPU, 20 KHz for the digital outputs of the standard SB, and 200 KHz for the
digital outputs of the high-speed SBs (or 100 KHz for MC V1 instructions).
Easy Book
192 Manual, 04/2012, A5E02486774-05
Configuring a pulse generator

1. Add a Technological object:
In the Project tree, expand the node "Technological Objects" and select "Add new
object".
Select the "Axis" icon (rename if required) and click "OK" to open the configuration
editor for the axis object.
Display the "Select PTO for Axis Control" properties under the "Basic parameters" and
select the desired pulse. Note the two Q outputs assigned for pulse and direction.
Note
If the PTO has not been previously configured in the CPU Properties, the PTO is
configured to use one of the onboard outputs.
If you use an output signal board, then select the "Device configuration" button to go
to the CPU Properties. Under "Parameter assignment", in the "Pulse options",
configure the output source to a signal board output. "Pulse_1" and "Pulse_3"are the
only pulse outputs available on the signal board.
Configure the remaining Basic and Extended parameters.

2. Program your application: Insert the MC_Power instruction in a code block.
For the Axis input, select the axis technology object that you created and configured.
Setting the Enable input to TRUE allows the other motion instructions to function.
Setting the Enable input FALSE cancels the other motion instructions.
Note
Include only one MC_Power instruction per axis.
3. Insert the other motion instructions to produce the required motion.
Note
Configuring a pulse generator to signal board outputs: Select the "Pulse generators
(PTO/PWM)" properties for a CPU (in Device configuration) and enable a pulse generator.
Two pulse generators are available for each S7-1200 CPU V1.0, V2.0, V2.1, and V2.2.
S7-1200 CPU V3.0 CPUs have four pulse generators available. In this same configuration
area under "Pulse options", select Pulse generator used as: "PTO".
Easy Book
Manual, 04/2012, A5E02486774-05 193
10.1 Configuring the axis
Note
The CPU calculates motion tasks in "slices" or segments of 10 ms. As one slice is being
executed, the next slice is waiting in the queue to be executed. If you interrupt the motion
task on an axis (by executing another new motion task for that axis), the new motion task
may not be executed for a maximum of 20 ms (the remainder of the current slice plus the
queued slice).

STEP 7 provides the configuration tools, the commissioning tools, and the diagnostic tools
for the "Axis" technological object.

Drive Commissioning
Technological object Diagnostics
Configuration
Note
The PTO requires the internal functionality of a high-speed counter (HSC). This means the
corresponding high-speed counter cannot be used elsewhere.
The assignment between PTO and HSC is fixed. When PTO1 is activated, it will be
connected to HSC1. If PTO2 is activated, it will be connected to HSC2. This is only true for
S7-1200 V1.0, V2.0, V2.1, and V2.2 CPUs. S7-1200 V3.0 CPUs do not have this restriction.
You cannot monitor the current value (for example, in ID 1000) when pulses are occurring.
Easy Book
194 Manual, 04/2012, A5E02486774-05
Table 10- 3 STEP 7 tools for motion control
Tool Description
Configuration Configures the following properties of the "Axis" technology object:
Selection of the PTO to be used and configuration of the drive interface
Properties of the mechanics and the transmission ratio of the drive (or machine or system)
Properties for position limits, dynamics, and homing
Save the configuration in the data block of the technology object.
Commissioning Tests the function of your axis without having to create a user program. When the tool is started,
the control panel will be displayed. The following commands are available on the control panel:
Enable and disable axis
Move axis in jog mode
Position axis in absolute and relative terms
Home axis
Acknowledge errors
The velocity and the acceleration / deceleration can be specified for the motion commands. The
control panel also shows the current axis status.
Diagnostics Monitors of the current status and error information for the axis and drive.
After you create the technological object for the

axis, you configure the axis by defining the basic
parameters, such as the PTO and the configuration
of the drive interface. You also configure the other
properties of the axis, such as position limits,
dynamics, and homing.
NOTICE
You may have to adapt the values of the input parameters of motion control instructions to
the new dimension unit in the user program.
Easy Book
Manual, 04/2012, A5E02486774-05 195
Configure the properties for the drive signals, drive

mechanics, and position monitoring (hardware and
software limit switches).
You configure the motion dynamics and the

behavior of the emergency stop command.
You also configure the homing behavior (passive and active).
Use the "Commissioning" control panel to test the functionality independently from your user
program.
Click the "Startup" icon to commission the axis.
The control panel shows the current status of the axis. Not only can you enable and disable
the axis, but you can also test the positioning of the axis (both in absolute and relative terms)
and can specify the velocity, acceleration and deceleration. You can also test the homing
and jogging tasks. The control panel also allows you to acknowledge errors.
Easy Book
196 Manual, 04/2012, A5E02486774-05
10.2 Configuring the TO_CommandTable_PTO

You can configure a CommandTable instruction using the Technological objects.
Adding a Technological object

1. In the Project tree, expand the node "Technological Objects" and select "Add new object".
2. Select the "CommandTable" icon (rename if required), and click "OK" to open the
configuration editor for the CommandTable object.
Planning the steps for your application

You can create the desired movement sequence in the "Command Table" configuration
window, and check the result against the graphic view in the trend diagram.
You can select the command types that are to be used for processing the command table.
Up to 32 steps can be entered. The commands are processed in sequence, easily producing
a complex motion profile.
Table 10- 4 MC_CommandTable command types
Command type Description

Empty The empty serves as a placeholder for any commands to be added. The empty entry is
ignored when the command table is processed
Halt Pause axis.
Note: The command only takes place after a "Velocity setpoint" command.
Positioning Relative Positions the axis based upon distance. The command moves the axis by the given
distance and velocity.
Positioning Absolute Positions the axis based upon location. The command moves the axis to the given
location, using the velocity specified.
Velocity setpoint Moves the axis at the given velocity.
Easy Book
Manual, 04/2012, A5E02486774-05 197

Wait Waits until the given period is over. "Wait" does not stop an active traversing motion.
Separator Adds a "Separator" line above the selected line. The separator line allows more than one
profile to be defined in a single command table.
In the figure below, "Command complete" is used as the transition to the next step. This type
of transition allows your device to decelerate to the start/stop speed and then accelerate
once again at the start of the next step.
Axis decelerates to the start/stop speed between steps.

In the figure below, "Blending motion" is used as the transition to the next step. This type of
transition allows your device to maintain its velocity into the start of the next step, resulting in
a smooth transition for the device from one step to the next. Using blending can shorten the
total time required for a profile to execute completely. Without blending, the example takes
seven seconds to run. With blending, the execution time is reduced by one second to a total
of six seconds.
Easy Book
198 Manual, 04/2012, A5E02486774-05
Axis continues to move and accelerates or decelerates to the next step velocity, saving time and
mechanical wear.
The operation of your CommandTable is controlled by an MC_CommandTable instruction,

as shown below:
Easy Book
Manual, 04/2012, A5E02486774-05 199
10.3 MC_Power instruction
NOTICE
If the axis is switched off due to an error, it will be enabled again automatically after the
error has been eliminated and acknowledged. This requires that the Enable input
parameter has retained the value TRUE during this process.
Table 10- 5 MC_Power instruction

"MC_Power_DB"( The MC_Power motion control instruction enables
Axis:=_multi_fb_in_, or disables an axis. Before you can enable or
Enable:=_bool_in_, disable the axis, ensure the following conditions:
StopMode:=_int_in_, The technology object has been configured
Status=>_bool_out_, correctly.
Busy=>_bool_out_,
There is no pending enable-inhibiting error.
Error=>_bool_out_,
The execution of MC_Power cannot be aborted by
ErrorID=>_word_out_,
a motion control task. Disabling the axis (input
ErrorInfo=>_word_out_);
parameter Enable = FALSE ) aborts all motion
control tasks for the associated technology object.
1 STEP 7 automatically creates the DB when you insert the instruction.
2 In the SCL example, "MC_Power_DB" is the name of the instance DB.
Table 10- 6 Parameters for the MC_Power instruction

Axis IN TO_Axis_1 Axis technology object
Enable IN Bool FALSE (default): All active tasks are aborted according to the
parameterized "StopMode" and the axis is stopped.
TRUE: Motion Control attempts to enable the axis.
StopMode IN Int 0: Emergency stop: If a request to disable the axis is pending, the
axis brakes at the configured emergency deceleration. The axis is
disabled after reaching standstill.
1: Immediate stop: If a request to disable the axis is pending, this
axis is disabled without deceleration. Pulse output is stopped
immediately.
2: Emergency stop with jerk control: If a request to disable the axis is
pending, the axis brakes at the configured emergency stop
deceleration. If the jerk control is activated, the configured jerk is
taken into account. The axis is disabled after reaching standstill.
Easy Book
200 Manual, 04/2012, A5E02486774-05

Status OUT Bool Status of axis enable:
FALSE: The axis is disabled:
The axis does not execute motion control tasks and does not
accept any new tasks (exception: MC_Reset task).
The axis is not homed.
Upon disabling, the status does not change to FALSE until the
axis reaches a standstill.
TRUE: The axis is enabled:
The axis is ready to execute motion control tasks.
Upon axis enabling, the status does not change to TRUE until
the signal "Drive ready" is pending. If the "Drive ready" drive
interface was not configured in the axis configuration, the status
changes to TRUE immediately.
Busy OUT Bool FALSE: MC_Power is not active.
TRUE: MC_Power is active.
Error OUT Bool FALSE: No error
TRUE: An error has occurred in motion control instruction "MC_Power"
or in the associated technology object. The cause of the error can be
found in parameters "ErrorID" and "ErrorInfo".
ErrorID OUT Word Error ID for parameter "Error""
ErrorInfo OUT Word Error info ID for parameter "ErrorID"

0&B3RZHU 0&B3RZHU

$[LVB $[LV 6WDWXV 6WDWXVB (QDB W
(QDB (QDEOH %XV\ %XV\B
6WRS0RGH (UURU (UURUB
6WDWXVB W
(UURU,'
(UURU,QIR
%XV\B W

(UURUB W
0&B5HVHW
0&B5HVHW
([HB W
$[LVB $[LV 'RQH 'RQHB
([HB ([HFXWH %XV\ %XV\B
'RQHB W
(UURU
(UURU,'
(UURU,QIR %XV\B W
'ULYH,QWHUIDFH

'ULYH(QDEOHG W

'ULYH5HDG\ W
An axis is enabled and then disabled again. After the drive has signaled "Drive ready" back to the CPU, the
successful enable can be read out via "Status_1".
Following an axis enable, an error has occurred that caused the axis to be disabled. The error is eliminated and
acknowledged with "MC_Reset". The axis is then enabled again.
Easy Book
Manual, 04/2012, A5E02486774-05 201
To enable an axis with configured drive interface, follow these steps:

1. Check the requirements indicated above.
2. Initialize input parameter "StopMode" with the desired value. Set input parameter
"Enable" to TRUE.
The enable output for "Drive enabled" changes to TRUE to enable the power to the drive.
The CPU waits for the "Drive ready" signal of the drive.
When the "Drive ready" signal is available at the configured ready input of the CPU, the
axis becomes enabled. Output parameter "Status" and technology object tag <Axis
name>.StatusBits.Enable indicates the value TRUE.
To enable an axis without configured drive interface, follow these steps:
2. Initialize input parameter "StopMode" with the desired value. Set input parameter
"Enable" to TRUE. The axis is enabled. Output parameter "Status" and technology object
tag <Axis name>.StatusBits.Enable indicate the value TRUE.
To disable an axis, follow these steps:
1. Bring the axis to a standstill.
You can identify when the axis is at a standstill in technology object tag <Axis
name>.StatusBits.StandStill.
2. Set input parameter "Enable" to FALSE after standstill is reached.
3. If output parameters "Busy" and "Status" and technology object tag <Axis
name>.StatusBits.Enable indicate the value FALSE, disabling of the axis is complete.
Easy Book
202 Manual, 04/2012, A5E02486774-05
10.4 MC_Reset instruction
10.4 MC_Reset instruction
Table 10- 7 MC_Reset instruction

"MC_Reset_DB"( Use the MC_Reset instruction to acknowledge
Axis:=_multi_fb_in_, "Operating error with axis stop" and
Execute:=_bool_in_, "Configuration error". The errors that require
Restart:=_bool_in_, acknowledgement can be found in the "List of
Done=>_bool_out_, ErrorIDs and ErrorInfos" under "Remedy".
Busy=>_bool_out_, Before using the MC_Reset instruction, you
Error=>_bool_out_, must have eliminated the cause of a pending
ErrorID=>_word_out_, configuration error requiring acknowledgement
ErrorInfo=>_word_out_); (for example, by changing an invalid
acceleration value in "Axis" technology object
to a valid value).
As of V3.0 and later, the Restart command
allows the axis configuration to be downloaded
to the work memory in the RUN operating
mode.
2 In the SCL example, "MC_Reset_DB" is the name of the instance DB.
The MC_Reset task cannot be aborted by any other motion control task. The new MC_Reset
task does not abort any other active motion control tasks.
Table 10- 8 Parameters of the MC_Reset instruction

Execute IN Bool Start of the task with a positive edge
Restart IN Bool TRUE = Download the axis configuration from the load memory to the
work memory. The command can only be executed when the axis is
disabled.
FALSE = Acknowledges pending errors
Done OUT Bool TRUE = Error has been acknowledged.
Busy OUT Bool TRUE = The task is being executed.
Error OUT Bool TRUE = An error has occurred during execution of the task. The
cause of the error can be found in parameters "ErrorID" and
"ErrorInfo".
ErrorID OUTP Word Error ID for parameter "Error""
To acknowledge an error with MC_Reset, follow these steps:

2. Start the acknowledgement of the error with a rising edge at the Execute input parameter.
3. The error has been acknowledged when Done equals TRUE and the technology object
tag <Axis name>.StatusBits.Error equals FALSE.
Easy Book
Manual, 04/2012, A5E02486774-05 203
10.5 MC_Home instruction
Table 10- 9 MC_Home instruction

"MC_Home_DB"( Use the MC_Home instruction to match
Axis:=_multi_fb_in_, the axis coordinates to the real, physical
Execute:=_bool_in_, drive position. Homing is required for
Position:=_real_in_, absolute positioning of the axis:
Mode:=_int_in_, In order to use the MC_Home instruction,
Done=>_bool_out_, the axis must first be enabled.
Busy=>_bool_out_,
CommandAborted=>_bool_out_,
Error=>_bool_out_,
2 In the SCL example, "MC_Home_DB" is the name of the instance DB.
The following types of homing are available:

Direct homing absolute (Mode = 0): The current axis position is set to the value of
parameter "Position".
Direct homing relative (Mode = 1): The current axis position is offset by the value of
parameter "Position".
Passive homing (Mode = 2): During passive homing, the MC_Home instruction does not
carry out any homing motion. The traversing motion required for this step must be
implemented by the user via other motion control instructions. When the reference point
switch is detected, the axis is homed.
Active homing (Mode = 3): The homing procedure is executed automatically.
Table 10- 10 Parameters for the MC_Home instruction

Axis IN TO_Axis_PTO Axis technology object
Position IN Real Mode = 0, 2, and 3 (Absolute position of axis after
completion of the homing operation)
Mode = 1 (Correction value for the current axis position)
Limit values: -1.0e12 Position 1.0e12
Easy Book
204 Manual, 04/2012, A5E02486774-05

Mode IN Int Homing mode
0: Direct homing absolute
New axis position is the position value of parameter

"Position".
1: Direct homing relative
New axis position is the current axis position + position

value of parameter "Position".
2: Passive homing
Homing according to the axis configuration. Following

homing, the value of parameter "Position" is set as the
new axis position.
3: Active homing
Reference point approach in accordance with the axis

configuration. Following homing, the value of parameter
"Position" is set as the new axis position.
Done OUT Bool TRUE = Task completed
CommandAborted OUT Bool TRUE = During execution the task was aborted by another
task.
Error OUT Bool TRUE = An error has occurred during execution of the task.
The cause of the error can be found in parameters "ErrorID"
and "ErrorInfo".
ErrorID OUT Word Error ID for parameter "Error""
Note
Axis homing is lost under the following conditions
Disabling of axis by the MC_Power instruction
Switchover between automatic control and manual control
Upon start of active homing (After successful completion of the homing operation, axis
homing is available again.)
After power-cycling the CPU
After CPU restart (RUN-to-STOP or STOP-to-RUN)
To home the axis, follow these steps:

2. Initialize the necessary input parameters with values, and start the homing operation with
a rising edge at input parameter "Execute".
3. If output parameter "Done" and technology object tag <Axis
name>.StatusBits.HomingDone indicate the value TRUE, homing is complete.
Easy Book
Manual, 04/2012, A5E02486774-05 205
Table 10- 11 Override response
Mode Description
0 or 1 The MC_Home task cannot be aborted by any other motion control task. The new MC_Home task does not
abort any active motion control tasks. Position-related motion tasks are resumed after homing according to
the new homing position (value at the Position input parameter).
2 The MC_Home task can be aborted by the following motion control tasks:
MC_Home task Mode = 2, 3: The new MC_Home task aborts the following active motion control task.
MC_Home task Mode = 2: Position-related motion tasks are resumed after homing according to the new
homing position (value at the Position input parameter).
3 The MC_Home task can be aborted by the following The new MC_Home task aborts the following active
motion control tasks: motion control tasks:
MC_Home Mode = 3 MC_Home Mode = 2, 3
MC_Halt MC_Halt
MC_MoveAbsolute MC_MoveAbsolute
MC_MoveRelative MC_MoveRelative
MC_MoveVelocity MC_MoveVelocity
MC_MoveJog MC_MoveJog
Homing refers to the matching of the axis coordinates to the real, physical drive position. (If
the drive is currently at position x, the axis will be adjusted to be in position x.) For position-
controlled axes, the entries and displays for the position refer exactly to these axis
coordinates.
Note
The agreement between the axis coordinates and the real situation is extremely important.
This step is necessary to ensure that the absolute target position of the axis is also achieved
exactly with the drive.
The MC_Home instruction initiates the homing of the axis.
Easy Book
206 Manual, 04/2012, A5E02486774-05
There are 4 different homing functions. The first two functions allow the user to set the
current position of the axis and the second two position the axis with respect to a Home
reference Sensor.
Mode 0 - Direct Referencing Absolute: When executed this mode tells the axis exactly
where it is. It sets the internal position variable to the value of the Position input of the
Homing instruction. This is used for machine calibration and setup.
The axis position is set regardless of the reference point switch. Active traversing motions
are not aborted. The value of the Position input parameter of the MC_Home instruction is
set immediately as the reference point of the axis. To assign the reference point to an
exact mechanical position, the axis must be at a standstill at this position at the time of
the homing operation.
Mode 1 - Direct Referencing Relative: When executed this mode uses the internal
position variable and adds the value of the Position input on the Homing instruction to it.
This is typically used to account for machine offset.
The axis position is set regardless of the reference point switch. Active traversing motions
are not aborted. The following statement applies to the axis position after homing: New
axis position = current axis position + value of the Position parameter of the MC_Home
instruction.
Mode 2 - Passive Referencing: When the axis is moving and passes the Reference Point
Switch the current position is set as the home position. This feature will help account for
normal machine wear and gear backlash and prevent the need for manual compensation
for wear. The Position input on the Homing instruction, as before, adds to the location
indicated by the Reference Point Switch allowing easy offset of the Home position.
During passive homing, the MC_Home instruction does not carry out any homing motion.
The traversing motion required for this step must be implemented by the user via other
motion control instructions. When the reference point switch is detected, the axis is
homed according to the configuration. Active traversing motions are not aborted upon
start of passive homing.
Mode 3 - Active Referencing: This mode is the most precise method of Homing the Axis.
The initial direction and velocity of movement is configured in the Technology Object
Configuration Extended Parameters-Homing. This is dependent upon machine
configuration. There is also the ability to determine if the leading edge or falling edge of
the Reference Point Switch signal is the Home position. Virtually all sensors have an
active range and if the Steady State On position was used as the Home signal then there
would be a possibility for error in the Homing position since the On signal active range
would cover a range of distance. By using either the leading or falling edge of that signal
a much more precise Home position results. As with all other modes the value of the
Position input on the Homing instruction is added to the Hardware referenced position.
In active homing mode, the MC_Home instruction performs the required reference point
approach. When the reference point switch is detected, the axis is homed according to
the configuration. Active traversing motions are aborted.
Modes 0 and 1 do not require that the axis be moved at all. They are typically used in setup
and calibration. Modes 2 and 3 require that the axis move and pass a sensor that is
configured in the "Axis" technology object as the Reference Point Switch. The reference
point which can be placed in the work area of the axis or outside of the normal work area but
within movement range.
Easy Book
Manual, 04/2012, A5E02486774-05 207
10.6 MC_Halt instruction
Table 10- 12 MC_Halt instruction

"MC_Halt_DB"( Use the MC_Halt instruction to stop all
Axis:=_multi_fb_in_, motion and to brings the axis to a stand-
Execute:=_bool_in_, still. The stand-still position is not defined.
Done=>_bool_out_, In order to use the MC_Halt instruction,
Busy=>_bool_out_, the axis must first be enabled.
Error=>_bool_out_,

2 In the SCL example, "MC_Halt_DB" is the name of the instance DB.
Table 10- 13 Parameters for the MC_Halt instruction

Done OUT Bool TRUE = Zero velocity reached
CommandAborted OUT Bool TRUE = During execution the task was aborted by another
task.
Error OUT Bool TRUE = An error has occurred during execution of the task.
The cause of the error can be found in parameters "ErrorID"
and "ErrorInfo".
ErrorID OUT Word Error ID for parameter "Error"
Easy Book
208 Manual, 04/2012, A5E02486774-05

0&B0RYH9HORFLW\ 9HORFLW\
$[LVB $[LV ,Q9HORFLW\ ,Q9HOB
([HB ([HB W
([HFXWH %XV\ %XV\B
9HORFLW\ &RPPDQG$ERUWHG $ERUWB
,Q9HOB W
'LUHFWLRQ (UURU
&XUUHQW (UURU,'
(UURU,QIR %XV\B W

$ERUWB W
0&B+DOW
0&B+DOW
$[LVB $[LV 'RQH 'RQHB ([HB W
&RPPDQG$ERUWHG $ERUWB 'RQHB W
(UURU

(UURU,' %XV\B W
(UURU,QIR

$ERUWB W

9HORFLW\
$[LVB W
The following values were configured in the "Dynamics > General" configuration window: Acceleration = 10.0 and
Deceleration = 5.0
The axis is braked by an MC_Halt task until it comes to a standstill. The axis standstill is signaled via "Done_2".
While an MC_Halt task is braking the axis, this task is aborted by another motion task. The abort is signaled via
"Abort_2".
Override response
The MC_Halt task can be aborted by the The new MC_Halt task aborts the following
following motion control tasks: active motion control tasks:
MC_Home Mode = 3 MC_Home Mode = 3
MC_Halt MC_Halt
Easy Book
Manual, 04/2012, A5E02486774-05 209
10.7 MC_MoveAbsolute instruction
Table 10- 14 MC_MoveAbsolute instruction

"MC_MoveAbsolute_DB"( Use the MC_MoveAbsolute
Axis:=_multi_fb_in_, instruction to start a positioning
Execute:=_bool_in_, motion of the axis to an absolute
Position:=_real_in_, position.
Velocity:=_real_in_, In order to use the
Done=>_bool_out_, MC_MoveAbsolute instruction, the
Busy=>_bool_out_, axis must first be enabled and also
CommandAborted=>_bool_out_, must be homed.
Error=>_bool_out_,

2 In the SCL example, "MC_MoveAbsolute_DB" is the name of the instance DB.
Table 10- 15 Parameters for the MC_MoveAbsolute instruction

Execute IN Bool Start of the task with a positive edge (Default value: False)
Position IN Real Absolute target position (Default value: 0.0)
Limit values: -1.0e12 Position 1.0e12
Velocity IN Real Velocity of axis (Default value: 10.0)
This velocity is not always reached because of the configured
acceleration and deceleration and the target position to be
approached.
Limit values: Start/stop velocity Velocity maximum velocity
Done OUT Bool TRUE = Absolute target position reached
CommandAborted OUT Bool TRUE = During execution the task was aborted by another task.
"ErrorInfo".
ErrorID OUT Word Error ID for parameter "Error" (Default value: 0000)
ErrorInfo OUT Word Error info ID for parameter "ErrorID" (Default value: 0000)
Easy Book
210 Manual, 04/2012, A5E02486774-05

0&B0RYH$EVROXWH 0RYH

3RVLWLRQ &RPPDQG$ERUWHG $ERUWB 'RQHB W
9HORFLW\ (UURU

(UURU,'
(UURU,QIR %XV\B W

$ERUWB W
0&B0RYH$EVROXWH 0RYH


3RVLWLRQ &RPPDQG$ERUWHG
'RQHB W
9HORFLW\ (UURU
(UURU,'
(UURU,QIR %XV\B W

9HORFLW\
$[LVB W

3RVLWLRQ
$[LVB W
Deceleration = 10.0
An axis is moved to absolute position 1000.0 with a MC_MoveAbsolute task. When the axis reaches the target
position, this is signaled via "Done_1". When "Done_1" = TRUE, another MC_MoveAbsolute task, with target
position 1500.0, is started. Because of the response times (e.g., cycle time of user program, etc.), the axis comes
to a standstill briefly (see zoomed-in detail). When the axis reaches the new target position, this is signaled via
"Done_2".
An active MC_MoveAbsolute task is aborted by another MC_MoveAbsolute task. The abort is signaled via
"Abort_1". The axis is then moved at the new velocity to the new target position 1500.0. When the new target
position is reached, this is signaled via "Done_2".
Override response
The MC_MoveAbsolute task can be The new MC_MoveAbsolute task aborts
aborted by the following motion control the following active motion control tasks:
tasks: MC_Home Mode = 3
MC_Home Mode = 3 MC_Halt
MC_Halt MC_MoveAbsolute
MC_MoveAbsolute MC_MoveRelative
MC_MoveRelative MC_MoveVelocity
MC_MoveVelocity MC_MoveJog
MC_MoveJog
Easy Book
Manual, 04/2012, A5E02486774-05 211
10.8 MC_MoveRelative instruction
Table 10- 16 MC_MoveRelative instruction

"MC_MoveRelative_DB"( Use the MC_MoveRelative
Axis:=_multi_fb_in_, instruction to start a positioning
Execute:=_bool_in_, motion relative to the start position.
Distance:=_real_in_, In order to use the
Velocity:=_real_in_, MC_MoveRelative instruction, the
Done=>_bool_out_, axis must first be enabled.
Busy=>_bool_out_,
Error=>_bool_out_,

2 In the SCL example, "MC_MoveRelative_DB" is the name of the instance DB.
Table 10- 17 Parameters for the MC_MoveRelative instruction

Distance IN Real Travel distance for the positioning operation (Default value: 0.0)
Limit values: -1.0e12 Distance 1.0e12
Velocity IN Real Velocity of axis (Default value: 10.0)
This velocity is not always reached on account of the configured
acceleration and deceleration and the distance to be traveled.
Limit values: Start/stop velocity Velocity maximum velocity
Done OUT Bool TRUE = Target position reached
"ErrorInfo".
Easy Book
212 Manual, 04/2012, A5E02486774-05

0&B0RYH5HODWLYH 0RYH


'LVWDQFH &RPPDQG$ERUWHG $ERUWB
%XV\B W
9HORFLW\ (UURU
(UURU,'
(UURU,QIR 'RQHB W

$ERUWB W
0&B0RYH5HODWLYH 0RYH

'LVWDQFH &RPPDQG$ERUWHG
%XV\B W
9HORFLW\ (UURU
(UURU,'
(UURU,QIR 'RQHB W

9HORFLW\
$[LVB W

3RVLWLRQ
$[LVB W
Deceleration = 10.0
The axis is moved by an MC_MoveRelative task by the distance ("Distance") 1000.0. When the axis reaches the
target position, this is signaled via "Done_1". When "Done_1" = TRUE, another MC_MoveRelative task, with travel
distance 500.0, is started. Because of the response times (for example, cycle time of user program), the axis
comes to a standstill briefly (see zoomed-in detail). When the axis reaches the new target position, this is signaled
via "Done_2".
An active MC_MoveRelative task is aborted by another MC_MoveRelative task. The abort is signaled via
"Abort_1". The axis is then moved at the new velocity by the new distance ("Distance") 500.0. When the new target
position is reached, this is signaled via "Done_2".
Override response
The MC_MoveRelative task can be aborted The new MC_MoveRelative task aborts the
by the following motion control tasks: following active motion control tasks:
MC_Halt MC_Halt
Easy Book
Manual, 04/2012, A5E02486774-05 213
10.9 MC_MoveVelocity instruction
Table 10- 18 MC_MoveVelocity instruction

"MC_MoveVelocity_DB"( Use the MC_MoveVelocity
Axis:=_multi_fb_in_, instruction to move the axis
Execute:=_bool_in_, constantly at the specified velocity.
Velocity:=_real_in_, In order to use the
Direction:=_int_in_, MC_MoveVelocity instruction, the
Current:=_bool_in_, axis must first be enabled.
InVelocity=>_bool_out_,
Busy=>_bool_out_,
Error=>_bool_out_,
2 In the SCL example, "MC_MoveVelocity_DB" is the name of the instance DB.
Table 10- 19 Parameters for the MC_MoveVelocity instruction

Velocity IN Real Velocity specification for axis motion (Default value: 10.0)
Limit values: Start/stop velocity |Velocity| maximum velocity
(Velocity = 0.0 is allowed)
Direction IN Int Direction specification:
0: Direction of rotation corresponds to the sign of the value in
parameter "Velocity" (Default value)
1: Positive direction of rotation (The sign of the value in
parameter "Velocity" is ignored.)
2: Negative direction of rotation (The sign of the value in
parameter "Velocity" is ignored.)
Current IN Bool Maintain current velocity:
FALSE: "Maintain current velocity" is deactivated. The values
of parameters "Velocity" and "Direction" are used. (Default
value)
TRUE: "Maintain current velocity" is activated. The values in
parameters "Velocity" and "Direction" are not taken into
account.
When the axis resumes motion at the current velocity, the

"InVelocity" parameter returns the value TRUE.
Easy Book
214 Manual, 04/2012, A5E02486774-05

InVelocity OUT Bool TRUE:
If "Current" = FALSE: The velocity specified in parameter
"Velocity" was reached.
If "Current" = TRUE: The axis travels at the current velocity at
the start time.
"ErrorInfo".

0&B0RYH9HORFLW\ 0RYH
$[LVB $[LV ,Q9HORFLW\ ,Q9HOB ([HB W
9HORFLW\ &RPPDQG$ERUWHG $ERUWB
%XV\B W
'LUHFWLRQ (UURU
&XUUHQW (UURU,'
,Q9HOB W
(UURU,QIR

$ERUWB W
0&B0RYH9HORFLW\ 0RYH

$[LVB $[LV ,Q9HORFLW\ ,Q9HOB ([HB W
9HORFLW\ &RPPDQG$ERUWHG %XV\B
W
'LUHFWLRQ (UURU
&XUUHQW (UURU,'
(UURU,QIR ,Q9HOB W

9HORFLW\
$[LVB W
Deceleration = 10.0
An active MC_MoveVelocity task signals via "InVel_1" that its target velocity has been reached. It is then aborted
by another MC_MoveVelocity task. The abort is signaled via "Abort_1". When the new target velocity 15.0 is
reached, this is signaled via "InVel_2". The axis then continues moving at the new constant velocity.
An active MC_MoveVelocity task is aborted by another MC_MoveVelocity task prior to reaching its target velocity.
The abort is signaled via "Abort_1". When the new target velocity 15.0 is reached, this is signaled via "InVel_2".
The axis then continues moving at the new constant velocity.
Easy Book
Manual, 04/2012, A5E02486774-05 215
10.10 MC_MoveJog instruction
Override response
The MC_MoveVelocity task can be aborted The new MC_MoveVelocity task aborts the
by the following motion control tasks: following active motion control tasks:
MC_Halt MC_Halt
Note
Behavior with zero set velocity (Velocity = 0.0)
An MC_MoveVelocity task with "Velocity" = 0.0 (such as an MC_Halt task) aborts active
motion tasks and stops the axis with the configured deceleration. When the axis comes to a
standstill, output parameter "InVelocity" indicates TRUE for at least one program cycle.
"Busy" indicates the value TRUE during the deceleration operation and changes to FALSE
together with "InVelocity". If parameter "Execute" = TRUE is set, "InVelocity" and "Busy" are
latched.
When the MC_MoveVelocity task is started, status bit "SpeedCommand" is set in the
technology object. Status bit "ConstantVelocity" is set upon axis standstill. Both bits are
adapted to the new situation when a new motion task is started.
Table 10- 20 MC_MoveJog instruction

"MC_MoveJog_DB"( Use the MC_MoveJog instruction to move
Axis:=_multi_fb_in_, the axis constantly at the specified
JogForward:=_bool_in_, velocity in jog mode. This instruction is
JogBackward:=_bool_in_, typically used for testing and
Velocity:=_real_in_, commissioning purposes.
InVelocity=>_bool_out_, In order to use the MC_MoveJog
Busy=>_bool_out_, instruction, the axis must first be enabled.
Error=>_bool_out_,

2 In the SCL example, "MC_MoveJog_DB" is the name of the instance DB.
Easy Book
216 Manual, 04/2012, A5E02486774-05
Table 10- 21 Parameters for the MC_MoveJog instruction

JogForward1 IN Bool As long as the parameter is TRUE, the axis moves in the positive
direction at the velocity specified in parameter "Velocity". The sign of
the value in parameter "Velocity" is ignored. (Default value: False)
JogBackward1 IN Bool As long as the parameter is TRUE, the axis moves in the negative
direction at the velocity specified in parameter "Velocity". The sign of
the value in parameter "Velocity" is ignored. (Default value: False)
Velocity IN Real Preset velocity for jog mode (Default value: 10.0)
Limit values: Start/stop velocity |Velocity| maximum velocity
InVelocity OUT Bool TRUE = The velocity specified in parameter "Velocity" was reached.
"ErrorInfo".
1 If both the JogForward and JogBackward parameters are simultaneously TRUE, the axis stops with the configured
deceleration. An error is indicated in parameters "Error", "ErrorID", and "ErrorInfo".

0RYH-RJ
0&B0RYH-RJ

$[LVB $[LV ,Q9HORFLW\ ,Q9HOB -RJB) W
-RJB) -RJ)RUZDUG %XV\ %XV\B

-RJB% -RJ%DFNZDUG &RPPDQG$ERUWHG -RJB% W
9HORFLW\ (UURU

(UURU,'
,Q9HOB W
(UURU,QIR

%XV\B W

9HORFLW\
$[LVB W

Deceleration = 5.0
The axis is moved in the positive direction in jog mode via "Jog_F". When the target velocity 50.0 is reached, this is
signaled via "InVelo_1". The axis brakes to a standstill again after Jog_F is reset.
The axis is moved in the negative direction in jog mode via "Jog_B". When the target velocity 50.0 is reached, this
is signaled via "InVelo_1". The axis brakes to a standstill again after Jog_B is reset.
Easy Book
Manual, 04/2012, A5E02486774-05 217
10.11 MC_CommandTable instruction
Override response
The MC_MoveJog task can be aborted by The new MC_MoveJog task aborts the
the following motion control tasks: following active motion control tasks:
MC_Halt MC_Halt
Table 10- 22 MC_CommandTable instruction

"MC_CommandTable_DB"( Executes a series of individual
Axis:=_multi_fb_in_, motions for a motor control axis
CommandTable:=_multi_fb_in_, that can combine into a
Execute:=_bool_in_, movement sequence.
StartIndex:=_uint_in_, Individual motions are configured
EndIndex:=_uint_in_, in a technology object command
Done=>_bool_out_, table for pulse train output
Busy=>_bool_out_, (TO_CommandTable_PTO).
Error=>_bool_out_,
ErrorInfo=>_word_out_,
CurrentIndex=>_uint_out_,
Code=>_word_out_);
2 In the SCL example, "MC_CommandTable_DB" is the name of the instance DB.
Table 10- 23 Parameters for the MC_CommandTable instruction
Parameter and type Data type Initial value Description

Axis IN TO_Axis_1 - Axis technology object
Table IN TO_CommandTable_1 - Command table technology object
Execute IN Booll FALSE Start job with rising edge
StartIndex IN Int 1 Start command table processing with this step
Limits: 1 StartIndex EndIndex
EndIndex IN Int 32 End command table processing with this step
Limits: StartIndex EndIndex 32
Easy Book
218 Manual, 04/2012, A5E02486774-05
Parameter and type Data type Initial value Description

Done OUT Bool FALSE MC_CommandTable processing completed
successfully
Busy OUT Bool FALSE Operation in progress
CommandAborted OUT Bool FALSE The task was aborted during processing by
another task.
Error OUT Bool FALSE An error ocurred during processing. The cause is
indicated by the parameters ErrorID and ErrorInfo.
ErrorID OUT Word 16#0000 Error identifier
ErrorInfo OUT Word 16#0000 Error information
Step OUT Int 0 Step currently in process
Code OUT Word 16#0000 User defined identifier of the step currently in
process
You can create the desired movement sequence in the "Command Table" configuration
window and check the result against the graphic view in the trend diagram.
You can select the command types that are to be used for processing the command table.
Up to 32 jobs can be entered. The commands are processed in sequence.
Table 10- 24 MC_CommandTable command types

Empty The empty serves as a placeholder for any commands to be added. The empty entry is
ignored when the command table is processed
Halt Pause axis.
Note: The command only takes place after a "Velocity setpoint" command.
Positioning Relative Positions the axis based upon distance. The command moves the axis by the given
distance and velocity.
Easy Book
Manual, 04/2012, A5E02486774-05 219

Positioning Absolute Positions the axis based upon location. The command moves the axis to the given
location, using the velocity specified.
Velocity setpoint Moves the axis at the given velocity.
Wait Waits until the given period is over. "Wait" does not stop an active traversing motion.
Separator Adds a "Separator" line above the selected line. The separator line allows more than one
profile to be defined in a single command table.
Prerequisites for MC_CommandTable execution:

The technology object TO_Axis_PTO V2.0 must be correctly configured.
The technology object TO_CommandTable_PTO must be correctly configured.
The axis must be released.
Override response
The MC_CommandTable task can be The new MC_CommandTable task aborts the
aborted by the following motion control following active motion control tasks:
tasks: MC_Home Mode = 3
MC_Home Mode = 3 MC_Halt
MC_Halt MC_MoveAbsolute
MC_MoveAbsolute MC_MoveRelative
MC_MoveRelative MC_MoveVelocity
MC_MoveVelocity MC_MoveJog
MC_MoveJog MC_CommandTable
MC_CommandTable The current motion control job with the
launch of the first "Positioning Relative",
"Positioning Absolute", "Velocity setpoint"
or "Halt" command
Easy Book
220 Manual, 04/2012, A5E02486774-05
10.12 MC_ChangeDynamic
Table 10- 25 MC_ChangeDynamic instruction

"MC_ChangeDynamic_DB"( Changes the dynamic settings of
Execute:=_bool_in_, a motion control axis:
ChangeRampUp:=_bool_in_, Change the ramp-up time
RampUpTime:=_real_in_, (acceleration) value
ChangeRampDown:=_bool_in_,
Change the ramp-down time
RampDownTime:=_real_in_,
(deceleration) value
ChangeEmergency:=_bool_in_,
EmergencyRampTime:=_real_in_, Change the emergency stop
ChangeJerkTime:=_bool_in_, ramp-down time (emergency
JerkTime:=_real_in_, stop deceleration) value
Done=>_bool_out_, Change the smoothing time
Error=>_bool_out_, (jerk) value

2 In the SCL example, "MC_ChangeDynamic_DB" is the name of the instance DB.
Table 10- 26 Parameters for the MC_ChangeDynamic instruction

Execute IN Bool Start of the command with a positive edge. Default value:
FALSE
ChangeRampUp IN Bool TRUE = Change ramp-up time in line with input parameter
"RampUpTime". Default value: FALSE
RampUpTime IN Real Time (in seconds) to accelerate from standstill to the configured
maximum velocity without jerk limit. Default value: 5.00
The change will influence the tag <Axis name>.
Config.DynamicDefaults.Acceleration. The effectiveness of the
change is shown in the description of this tag.
ChangeRampDown IN Bool TRUE = Change ramp-down time in line with input parameter
"RampDownTime". Default value: FALSE
RampDownTime IN Real Time (in seconds) to decelerate axis from the configured
maximum velocity to standstill without jerk limiter. Default value:
5.00
Config.DynamicDefaults.Deceleration. The effectiveness of the
change is shown in the description of this tag.
ChangeEmergency IN Bool TRUE = Change emergency stop ramp-down time in line with
input parameter "EmergencyRampTime" Default value: FALSE
Easy Book
Manual, 04/2012, A5E02486774-05 221

EmergencyRampTime IN Real Time (in seconds) to decelerate the axis from configured
maximum velocity to standstill without jerk limiter in emergency
stop mode. Default value: 2.00
Config.DynamicDefaults.EmergencyDeceleration. The
effectiveness of the change is shown in the description of this
tag.
ChangeJerkTime IN Bool TRUE = Change smoothing time according to the input
parameter "JerkTime". Default value: FALSE
JerkTime IN Real Smoothing time (in seconds) used for the axis acceleration and
deceleration ramps. Default value: 0.25
Config.DynamicDefaults.Jerk. The effectiveness of the change is
shown in the description of this tag.
Done OUT Bool TRUE = The changed values have been written to the
technology data block. The description of the tags will show
when the change becomes effective. Default value: FALSE
Error OUT Bool TRUE = An error occurred during execution of the command.
The cause of the error can be found in parameters "ErrorID" and
"ErrorInfo". Default value: FALSE
ErrorID OUT Word Error identifier. Default value: 16#0000
ErrorInfo IN Word Error information. Default value: 16#0000
Prerequisites for MC_ ChangeDynamic execution:

The technology object TO_Axis_PTO V2.0 must be correctly configured.
The axis must be released.
Override response
An MC_ChangeDynamic command cannot be aborted by any other Motion Control
command.
A new MC_ChangeDynamic command does not abort any active Motion Control jobs.
Note
The input parameters "RampUpTime", "RampDownTime", "EmergencyRampTime" and
"RoundingOffTime" can be specified with values that makes the resultant axis parameters
"acceleration", "delay", "emergency stop-delay" and "jerk" outside the permissible limits.
Make sure you keep the MC_ChangeDynamic parameters within the limits of the dynamic
configuration settings for the axis technological object.
Easy Book
222 Manual, 04/2012, A5E02486774-05
Easy to use the online tools 11
11.1 Going online and connecting to a CPU
An online connection between the programming device and CPU is required for loading
programs and project engineering data as well as for activities such as the following:
Testing user programs
Displaying and changing the operating mode of the CPU (Page 224)
Displaying and setting the date and time of day of the CPU (Page 233)
Displaying the module information
Comparing and synchronizing (Page 232) offline to online program blocks
Uploading and downloading program blocks
Displaying diagnostics and the diagnostics buffer (Page 233)
Using a watch table (Page 226) to test the user program by monitoring and modifying
values
Using a force table to force values in the CPU (Page 227)
To establish an online connection to a configured CPU, click

the CPU from the Project Navigation tree and click the "Go
online" button from the Project View:
If this is the first time to go
online with this CPU, you
must select the type of PG/PC
interface and the specific
PG/PC interface from the Go
Online dialog before
establishing an online
connection to a CPU found on
that interface.
Your programming device is now connected to the CPU. The orange color frames indicate
an online connection. You can now use the Online & diagnostics tools from the Project tree
and the Online tools task card.
Easy Book
Manual, 04/2012, A5E02486774-05 223
Easy to use the online tools
11.2 Interacting with the online CPU
11.2 Interacting with the online CPU

The Online and Diagnostics portal provides an operator panel for changing the operating
mode of the online CPU. The "Online tools" task card displays an operator panel that shows
the operating mode of the online CPU. The operator panel also allows you to change the
operating mode of the online CPU. Use the button on the operator panel to change the
operating mode (STOP or RUN). The operator panel also provides an MRES button for
resetting the memory.
The color of the RUN/STOP indicator shows the current operating

mode of the CPU: yellow indicates STOP mode, and green indicates
RUN mode.
To use the operator panel, you must be connected online to the CPU. After you select the
CPU in the device configuration or display a code block in the online CPU, you can display
the operator panel from the "Online tools" task card.
You can monitor the cycle time of an online CPU.
You can also view the memory usage of the CPU.
Easy Book
224 Manual, 04/2012, A5E02486774-05
11.3 Going online to monitor the values in the CPU
11.3 Going online to monitor the values in the CPU
To monitor the tags, you must have an online connection to the CPU. Simply click the "Go
online" button in the toolbar.
When you have connected to the CPU, STEP 7 turns the headers of
the work areas orange.
The project tree displays a comparison of the offline project and the
online CPU. A green circle means that the CPU and the project are
synchronized, meaning that both have the same configuration and
user program.
Tag tables show the tags. Watch tables can also show the tags, as
well as direct addresses.
To monitor the execution of the user program and to display the values of the tags,
click the "Monitor all" button in the toolbar.
The "Monitor value" field shows the value for each tag.
Easy Book
Manual, 04/2012, A5E02486774-05 225
11.4 Displaying status of the user program is easy
11.4 Displaying status of the user program is easy

You can monitor the status of the tags in the LAD and FBD program editors. Use the editor
bar to display the LAD editor. The editor bar allows you to change the view between the
open editors without having to open or close the editors.
In the toolbar of the program editor, click the "Monitoring on/off" button to display the status
of your user program.
The network in the program editor displays power flow in green.

You can also right-click on the instruction or parameter to modify the value for the instruction.
11.5 Using a watch table for monitoring the CPU

A watch table allows you to monitor or modify data points while the CPU executes your user
program. These data points can be inputs (I), outputs (Q), M memory, a DB, or peripheral
inputs (such as "On:P" or "I 3.4:P"). You cannot accurately monitor the physical outputs
(such as Q0.0:P) because the monitor function can only display the last value written from Q
memory and does not read the actual value from the physical outputs.
The monitoring function does not change the program sequence. It presents you with
information about the program sequence and the data of the program in the CPU. You can
also use the "Modify value" function to test the execution of your user program.
Note
The digital I/O points used by the high-speed counter (HSC), pulse-width modulation (PWM),
and pulse-train output (PTO) devices are assigned during device configuration. When digital
I/O point addresses are assigned to these devices, the values of the assigned I/O point
addresses cannot be modified by the "Force" function of the watch table.
With a watch table, you can monitor or modify the values of the individual tags, choosing
from the following options:
At the beginning or the end of the scan cycle
When the CPU changes to STOP mode
"Permanently" (with the value not being reset after a STOP to RUN transition)
Easy Book
226 Manual, 04/2012, A5E02486774-05
11.6 Using the force table
To create a watch table:

1. Double-click "Add new watch table" to open a new
watch table.
2. Enter the tag name to add a tag to the watch
table.
To monitor the tags, you must have an online connection to the CPU. The following options
are available for modifying tags:
"Modify now" immediately changes the value for the selected addresses for one scan
cycle.
"Modify with trigger" changes the values for the selected addresses.
This function does not provide feedback to indicate that the selected addresses were
actually modified. If feedback of the change is required, use the "Modify now" function.
"Enable peripheral outputs" allows you to turn on the peripheral outputs when the CPU is
in STOP mode. This feature is useful for testing the wiring of the output modules.
The various functions can be selected using the buttons at the top of a watch table. Enter the
tag name to monitor and select a display format from the dropdown selection. With an online
connection to the CPU, clicking the "Monitor" button displays the actual value of the data
point in the "Monitor value" field.

A force table provides a "force" function that overwrites the value for an input or output point
to a specified value for the peripheral input or peripheral output address. The CPU applies
this forced value to the input process image prior to the execution of the user program and to
the output process image before the outputs are written to the modules.
Note
The force values are stored in the CPU and not in the force table.
You cannot force an input (or "I" address) or an output (or "Q" address). However, you can
force a peripheral input or peripheral output. The force table automatically appends a ":P" to
the address (for example: "On":P or "Run":P).
Easy Book
Manual, 04/2012, A5E02486774-05 227
In the "Force value" cell, enter the value for the input or output to be forced. You can then
use the check box in the "Force" column to enable forcing of the input or output.
Use the "Start or replace forcing" button to force the value of the tags in the force
table. Click the "Stop forcing" button to reset the value of the tags.
In the force table, you can monitor the status of the forced value for an input. However, you
cannot monitor the forced value of an output.
You can also view the status of the forced value in the program editor.
NOTICE
When an input or output is forced in a force table, the force actions become part of the
project configuration. If you close STEP 7, the forced elements remain active in the CPU
program until they are cleared. To clear these forced elements, you must use STEP 7 to
connect with the online CPU and then use the force table to turn off or stop the force
function for those elements.
The CPU allows you to force input and output point(s) by specifying the physical input or
output address (I_:P or Q_:P) in the force table and then starting the force function.
In the program, reads of physical inputs are overwritten by the forced value. The program
uses the forced value in processing. When the program writes a physical output, the output
value is overwritten by the force value. The forced value appears at the physical output and
is used by the process.
When an input or output is forced in the force table, the force actions become part of the
user program. Even though the programming software has been closed, the force selections
remain active in the operating CPU program until they are cleared by going online with the
programming software and stopping the force function. Programs with forced points loaded
on another CPU from a memory card will continue to force the points selected in the
program.
Easy Book
228 Manual, 04/2012, A5E02486774-05
If the CPU is executing the user program from a write-protected memory card, you cannot
initiate or change the forcing of I/O from a watch table because you cannot override the
values in the write-protected user program. Any attempt to force the write-protected values
generates an error. If you use a memory card to transfer a user program, any forced
elements on that memory card will be transferred to the CPU.
Note
Digital I/O points assigned to HSC, PWM, and PTO cannot be forced
The digital I/O points used by the high-speed counter (HSC), pulse-width modulation (PWM),
and pulse-train output (PTO) devices are assigned during device configuration. When digital
I/O point addresses are assigned to these devices, the values of the assigned I/O point
addresses cannot be modified by the force function of the watch table.
$ % & ' )
Startup RUN
A The clearing of the I memory area is not While writing Q memory to the physical
affected by the Force function. outputs, the CPU applies the force value as
the outputs are updated.
B The initialization of the outputs values is When reading the physical inputs, the CPU
not affected by the Force function. applies the force values just prior to copying
the inputs into I memory.
C During the execution of the startup OBs, During the execution of the user program
the CPU applies the force value when (program cycle OBs), the CPU applies the
the user program accesses the physical force value when the user program accesses
input. the physical input or writes the physical
output.
D The storing of interrupt events into the Handling of communication requests and self-
queue is not affected. test diagnostics are not affected by the Force
function.
E The enabling of the writing to the The processing of interrupts during any part of
outputs is not affected. the scan cycle is not affected.
Easy Book
Manual, 04/2012, A5E02486774-05 229
11.7 Capturing the online values of a DB to reset the start values
11.7 Capturing the online values of a DB to reset the start values

You can capture the current values being monitored in an online CPU to become the start
values for a global DB.
You must have an online connection to the CPU.
The CPU must be in RUN mode.
You must have opened the DB in STEP 7.
Use the "Show a snapshot of the monitored values" button to capture the current
values of the selected tags in the DB. You can then copy these values into the "Start
value" column of the DB.
1. In the DB editor, click the "Monitor all tags" button. The "Monitor value" column displays
the current data values.
2. Click the "Show a snapshot of the monitored values" button to display the current values
in the "Snapshot" column.
3. Click the "Monitor all" button to stop monitoring the data in the CPU.
4. Copy a value in the "Snapshot" column for a tag.
Select a value to be copied.
Right-click the selected value to display the context menu.
Select the "Copy" command.
5. Paste the copied value into the corresponding "Start value" column for the tag. (Right-
click the cell and select "Paste" from the context menu.)
6. Save the project to configure the copied values as the new start values for the DB.
7. Compile and download the DB to the CPU. The DB uses the new start values after the
CPU goes to RUN mode.
Note
The values that are shown in the "Monitor value" column are always copied from the
CPU. STEP 7 does not check whether all values come from the same scan cycle of the
CPU.
Easy Book
230 Manual, 04/2012, A5E02486774-05
11.8 Copying elements of the project
11.8 Copying elements of the project

You can also copy the program blocks from an online CPU or a memory card attached to
your programming device.
Prepare the offline project for the copied program blocks:

1. Add a CPU device that matches the online CPU.
2. Expand the CPU node once so that the "Program
blocks" folder is visible.
To upload the program blocks from the online CPU to the

offline project, follow these steps:
1. Click the "Program blocks" folder in the offline project.
2. Click the "Go online" button.
3. Click the "Upload" button.
4. Confirm your decision from the Upload dialog.
As an alternative to the previous method, follow these
steps:
1. From the project navigator, expand the node for
"Online access" to select the program blocks in the
online CPU:
2. Expand the node for the network, and double click
"Update accessible devices".
3. Expand the node for the CPU.
4. Drag the "Program blocks" folder from the online CPU
and drop the folder into the "Program blocks" folder of
your offline project.
5. In the "Upload preview" dialog, select the box for
"Continue", and then click the "Upload from device"
button.
When the upload is complete, all of the program blocks,
technology blocks, and tags will be displayed in the offline
area.
Note
You can copy the program blocks from the online CPU to an existing program. The
"Program-blocks" folder of the offline project does not have to be empty. However, the
existing program will be deleted and replaced by the user program from the online CPU.
Easy Book
Manual, 04/2012, A5E02486774-05 231
11.9 Comparing offline and online CPUs
11.9 Comparing offline and online CPUs

You can compare the code blocks in an online CPU with the code blocks in your project. If
the code blocks of your project do not match the code blocks of the online CPU, the
"Compare" editor allows you to synchronize your project with the online CPU by downloading
the code blocks of your project to the CPU, or by deleting blocks from the project that do not
exist in the online CPU.
Select the CPU in your project.

Use the "Compare Offline/online" command to open the
"Compare" editor. (Access the command either from the "Tools"
menu or by right-clicking the CPU in your project.)
Click in the "Action" column for an object to

select whether to delete the object, take no
action, or download the object to the device.
Click the "Synchronize" button to load the code
blocks.
Right-click an object in the "Compare to" column and

select "Start detailed comparison" button to show the
code blocks side-by-side.
The detailed comparison highlights the differences
between the code blocks of online CPU and the code
blocks of the CPU in your project.
Easy Book
232 Manual, 04/2012, A5E02486774-05
11.10 Displaying the diagnostic events
11.10 Displaying the diagnostic events

The CPU provides a diagnostic buffer which contains an entry for each diagnostic event,
such as transition of the CPU operating mode or errors detected by the CPU or modules. To
access the diagnostic buffer, you must be online.
Each entry includes a date and time the event occurred, an event category, and an event
description. The entries are displayed in chronological order, with the most recent event at
the top.
While the CPU maintains power, up to

50 most recent events are available in
this log. When the log is full, a new
event replaces the oldest event in the
log.
When power is lost, the ten most
recent events are saved.
11.11 Setting the IP address and time of day
You can set the IP address and time of day in the online CPU. After accessing "Online &
diagnostics" from the Project tree for an online CPU, you can display or change the IP
address. You can also display or set the time and date parameters of the online CPU.
Note
This feature is available only for a CPU that either has only a MAC address (has not yet
been assigned an IP address) or has been reset to factory settings.
Easy Book
Manual, 04/2012, A5E02486774-05 233
11.12 Resetting to factory settings
11.12 Resetting to factory settings

You can reset an S7-1200 to its original factory settings under the following conditions:
No memory card is inserted in the CPU.
The CPU has an online connection.
The CPU is in STOP mode.
Note
If the CPU is in RUN mode and you start the reset operation, you can place it in STOP
mode after acknowledging a confirmation prompt.
Procedure
To reset a CPU to its factory settings, follow these steps:
1. Open the Online and Diagnostics view of the CPU.
2. Select "Reset to factory settings" from the "Functions" folder.
3. Select the "Keep IP address" check box if you want to retain the IP address or the "Reset
IP address" check box if you want to delete the IP address.
4. Click the "Reset" button.
5. Acknowledge the confirmation prompt with "OK".
Result
The module is switched to STOP mode if necessary, and it is reset to the factory settings:
The work memory and internal load memory and all operand areas are cleared.
All parameters are reset to their defaults.
The diagnostics buffer is cleared.
The time of day is reset.
The IP address is retained or deleted based on the setting you made. (The MAC address
is fixed and is never changed.)
Easy Book
234 Manual, 04/2012, A5E02486774-05
11.13 Downloading an IP address to an online CPU
11.13 Downloading an IP address to an online CPU

To assign an IP address, you must perform the following tasks:
Configure the IP
address for the CPU
(Page 77).
Save and download the
configuration to the
CPU.
The IP address and subnet mask for the CPU must be compatible with the IP address and
subnet mask of the programming device. Consult your network specialist for the IP address
and subnet mask for your CPU.
If the CPU has not been previously configured, you can also
use "Online access" to set the IP address.
An IP address that has been downloaded as part of the device
configuration will not be lost on a power cycle of the PLC.
After you have downloaded the device configuration with the IP address, you can see the IP
address under the "Online access" folder.
Easy Book
Manual, 04/2012, A5E02486774-05 235
11.14 Using the "unspecified CPU" to upload the hardware configuration
11.14 Using the "unspecified CPU" to upload the hardware configuration

If you have a physical CPU that you can connect to the programming device, it is easy to
upload the configuration of the hardware.
You must first connect the CPU to your programming device, and you must create a new
project.
In the device configuration (Project view or Portal view),

add a new device, but select the "unspecified CPU"
instead of selecting a specific CPU. STEP 7 creates an
unspecified CPU.
After creating the unspecified CPU, you can upload the

hardware configuration for the online CPU.
From the program editor, you select the "Hardware
detection" command from the "Online" menu.
From the device configuration editor, you select the option
for detecting the configuration of the connected device
After you select the CPU from the online dialog, STEP 7 uploads the hardware configuration
from the CPU, including any modules (SM, SB, or CM). The IP address is not uploaded. You
must go to "Device configuration" to manually configure the IP address.
Easy Book
236 Manual, 04/2012, A5E02486774-05
11.15 Downloading in RUN mode

The CPU supports "Download in RUN mode". This capability is intended to allow you to
make small changes to a user program with minimal disturbance to the process being
controlled by the program. However, implementing this capability also allows massive
program changes that could be disruptive or even dangerous.
WARNING
When you download changes to the CPU in RUN mode, the changes immediately affect
process operation. Changing the program in RUN mode can result in unexpected system
operation, which could cause death or serious injury to personnel, and/or damage to
equipment.
Only authorized personnel who understand the effects of RUN mode changes on system
operation should perform a download in RUN mode.
The "Download in RUN mode" feature allows you to make changes to a program and
download them to your CPU without switching to STOP mode:
You can make minor changes to your current process without having to shut down (for
example, change a parameter value).
You can debug a program more quickly with this feature (for example, invert the logic for
a normally open or normally closed switch).
You can make the following program block and tag changes and download them in RUN
mode:
Create, overwrite, and delete Functions (FC), Function Blocks (FB), and Tag tables.
Create and delete Data Blocks (DB); however, DB structure changes cannot be
overwritten. Initial DB values can be overwritten. You cannot download a web server DB
(control or fragment) in RUN mode.
Overwrite Organization Blocks (OB); however, you cannot create or delete OBs.
A maximum number of ten blocks can be downloaded in RUN mode at one time. If more
than ten blocks are downloaded, the CPU must be placed into STOP mode.
If you download changes to a real process (as opposed to a simulated process, which you
might do in the course of debugging a program), it is vital to think through the possible safety
consequences to machines and machine operators before you download.
Note
If the CPU is in RUN mode and program changes have been made, STEP 7 always try to
download in RUN first. If you do not want this to happen, you must put the CPU into STOP.
If the changes made are not supported in "Download in RUN", STEP 7 prompts the user that
the CPU must go to STOP.
Easy Book
Manual, 04/2012, A5E02486774-05 237
11.15.1 Changing your program in RUN mode

To change the program in RUN mode, your must first ensure that the CPU supports
"Download in RUN mode" and that the CPU is in RUN mode:
1. To download your program in RUN mode, select one of the following methods:
"Download to device" command from the "Online" menu
"Download to device" button in the toolbar
In the "Project tree", right-click "Program blocks" and select the "Download to device >
Software" command.
2. If the program compiles successfully, STEP 7 downloads the program to the CPU.
3. STEP 7 prompts you to load your program or cancel the operation.
4. If you click "Load", STEP 7 downloads the program to the CPU.
Easy Book
238 Manual, 04/2012, A5E02486774-05
Technical specifications A
A.1 General Technical Specifications
Standards compliance
The S7-1200 automation system design conforms with the following standards and test
specifications. The test criteria for the S7-1200 automation system are based on these
standards and test specifications.
Note that not all S7-1200 models may be certified to these standards, and certification status
may change without notification. It is the user's responsibility to determine applicable
certifications by referring to the ratings marked on the product. Consult your local Siemens
representative if you need additional information related to the latest listing of exact
approvals by part number.
CE approval
The S7-1200 Automation System satisfies requirements and safety related objectives
according to the EC directives listed below, and conforms to the harmonized European
standards (EN) for the programmable controllers listed in the Official Journals of the
European Community.
EC Directive 2006/95/EC (Low Voltage Directive) "Electrical Equipment Designed for Use
within Certain Voltage Limits"
EN 61131-2:2007 Programmable controllers - Equipment requirements and tests
EC Directive 2004/108/EC (EMC Directive) "Electromagnetic Compatibility"
Emission standard
EN 61000-6-4:2007: Industrial Environment
Immunity standard
EN 61000-6-2:2005: Industrial Environment
EC Directive 94/9/EC (ATEX) "Equipment and Protective Systems Intended for Use in
Potentially Explosive Atmosphere"
EN 60079-15:2005: Type of Protection 'n'
The CE Declaration of Conformity is held on file available to competent authorities at:
Siemens AG
IA AS RD ST PLC Amberg
Werner-von-Siemens-Str. 50
D92224 Amberg
Germany
Easy Book
Manual, 04/2012, A5E02486774-05 239
Technical specifications
cULus approval
Underwriters Laboratories Inc. complying with:
Underwriters Laboratories, Inc.: UL 508 Listed (Industrial Control Equipment)
Canadian Standards Association: CSA C22.2 Number 142 (Process Control Equipment)
NOTICE
The SIMATIC S7-1200 series meets the CSA standard.

The cULus logo indicates that the S7-1200 has been examined and certified by
Underwriters Laboratories (UL) to standards UL 508 and CSA 22.2 No. 142.
FM approval
Factory Mutual Research (FM)
Approval Standard Class Number 3600 and 3611
Approved for use in:
Class I, Division 2, Gas Group A, B, C, D, Temperature Class T3C Ta = 60 C
Class I, Zone 2, IIC, Temperature Class T3 Ta = 60 C
Canadian Class I, Zone 2 Installation per CEC 18-150
IMPORTANT EXCEPTION: See Technical Specifications for the number of inputs or outputs
allowed on simultaneously. Some models are de-rated for Ta = 60 C.
WARNING
Substitution of components may impair the suitability for Class I, Division 2 and Zone 2.
Repair of units should only be performed by an authorized Siemens Service Center.
ATEX approval
ATEX approval applies to DC models only. ATEX approval does not apply to AC and Relay
models.
EN 60079-0:2006: Explosive Atmospheres - General Requirements
EN 60079-15:2005: Electrical Apparatus for Potentially Explosive Atmospheres;
Type of protection 'nA'
II 3 G Ex nA II T3
IMPORTANT EXCEPTION: See Technical Specifications for the number of inputs or outputs
allowed on simultaneously. Some models are de-rated for Ta = 60 C.
Install modules in a suitable enclosure providing a minimum degree of protection of IP54
according to EN 60529 and take into account the environmental conditions under which the
equipment will be used.
When the temperature under rated conditions exceed 70 C at the cable entry point, or 80 C
at the branching point of the conductors, the temperature specification of the selected cable
should be in compliance with the actual measured temperature.
Easy Book
240 Manual, 04/2012, A5E02486774-05
Provisions should be made to prevent the rated voltage from being exceeded by transient
disturbances of more than 40%.
C-Tick approval
The S7-1200 automation system satisfies requirements of standards to AS/NZS 2064
(Class A).
Korea Certification
The S7-1200 automation system satisfies the requirements of the Korean Certification (KC
Mark). It has been defined as Class A Equipment and is intended for industrial applications
and has not been considered for home use.
Maritime approval
The S7-1200 products are periodically submitted for special agency approvals related to
specific markets and applications. Consult your local Siemens representative if you need
additional information related to the latest listing of exact approvals by part number.
Classification societies:
ABS (American Bureau of Shipping)
BV (Bureau Veritas)
DNV (Det Norske Veritas)
GL (Germanischer Lloyd)
LRS (Lloyds Register of Shipping)
Class NK (Nippon Kaiji Kyokai)
Industrial environments
The S7-1200 automation system is designed for use in industrial environments.
Table A- 1 Industrial environments
Application field Noise emission requirements Noise immunity requirements

Industrial EN 61000-6-4:2007 EN 61000-6-2:2005
Easy Book
Manual, 04/2012, A5E02486774-05 241
Electromagnetic compatibility
Electromagnetic Compatibility (EMC) is the ability of an electrical device to operate as
intended in an electromagnetic environment and to operate without emitting levels of
electromagnetic interference (EMI) that may disturb other electrical devices in the vicinity.
Table A- 2 Immunity per EN 61000-6-2
Electromagnetic compatibility - Immunity per EN 61000-6-2

EN 61000-4-2 8 kV air discharge to all surfaces
Electrostatic discharge 6 kV contact discharge to exposed conductive surfaces
EN 61000-4-3 80 to 1000 MHz, 10 V/m, 80% AM at 1 kHz
Radiated, radio-frequency, 1.4 to 2.0 GHz, 3 V/m, 80% AM at 1 kHz
electromagnetic field immunity test 2.0 to 2.7 GHz, 1 V/m, 80% AM at 1 kHz
EN 61000-4-4 2 kV, 5 kHz with coupling network to AC and DC system power
Fast transient bursts 2 kV, 5 kHz with coupling clamp to I/O
EN 6100-4-5 AC systems - 2 kV common mode, 1kV differential mode
Surge immunity DC systems - 2 kV common mode, 1kV differential mode
For DC systems (I/O signals, DC power systems) external protection is
required.
EN 61000-4-6 150 kHz to 80 MHz, 10 V RMS, 80% AM at 1kHz
Conducted disturbances
EN 61000-4-11 AC systems
Voltage dips 0% for 1 cycle, 40% for 12 cycles and 70% for 30 cycles at 60 Hz
Table A- 3 Conducted and radiated emissions per EN 61000-6-4
Electromagnetic compatibility - Conducted and radiated emissions per EN 61000-6-4

Conducted Emissions 0.15 MHz to 0.5 MHz <79dB (V) quasi-peak; <66 dB (V) average
EN 55011, Class A, Group 1 0.5 MHz to 5 MHz <73dB (V) quasi-peak; <60 dB (V) average
5 MHz to 30 MHz <73dB (V) quasi-peak; <60 dB (V) average
Radiated Emissions 30 MHz to 230 MHz <40dB (V/m) quasi-peak; measured at 10m
EN 55011, Class A, Group 1 230 MHz to 1 GHz <47dB (V/m) quasi-peak; measured at 10m
Environmental conditions
Table A- 4 Transport and storage
Environmental conditions - Transport and storage

EN 60068-2-2, Test Bb, Dry heat and -40 C to +70 C
EN 60068-2-1, Test Ab, Cold
EN 60068-2-30, Test Db, Damp heat 25 C to 55 C, 95% humidity
EN 60068-2-14, Test Na, temperature shock -40 C to +70 C, dwell time 3 hours, 5 cycles
EN 60068-2-32, Free fall 0.3 m, 5 times, product packaging
Atmospheric pressure 1080 to 660h Pa (corresponding to an altitude of -1000 to 3500m)
Easy Book
242 Manual, 04/2012, A5E02486774-05
Table A- 5 Operating conditions
Environmental conditions - Operating

Ambient temperature range -20 C to 60 C horizontal mounting
(Inlet Air 25 mm below unit) -20 C to 50 C vertical mounting
95% non-condensing humidity
Unless otherwise specified
Atmospheric pressure 1080 to 795 hPa (corresponding to an altitude of -1000 to 2000m)
Concentration of contaminants S02: < 0.5 ppm; H2S: < 0.1 ppm; RH < 60% non-condensing
EN 60068-2-14, Test Nb, temperature change 5 C to 55 C, 3 C/minute
EN 60068-2-27 Mechanical shock 15 G, 11 ms pulse, 6 shocks in each of 3 axis
EN 60068-2-6 Sinusoidal vibration DIN rail mount: 3.5 mm from 5-9 Hz, 1G from 9 - 150 Hz
Panel Mount: 7.0 mm from 5-9 Hz, 2G from 9 to 150 Hz
10 sweeps each axis, 1 octave per minute
NOTICE
For systems that must start up in the range of -20 C to 0 C, the user program should
delay energizing outputs for 10 seconds following startup.
Table A- 6 High potential isolation test
High potential isolation test

24 V/5 V nominal circuits 520 VDC (type test of optical isolation boundaries)
115/230 V circuits to ground 1500 VAC
115/230 V circuits to 115/230 V circuits 1500 VAC
115 V/230V circuits to 24 V/5 V circuits 1500 VAC (3000 VAC / 4242 VDC type test)
Ethernet port to 24V/5V circuits and ground1 1500 VAC (type test only)
1 Ethernet port isolation is designed to limit hazard during short term network faults to hazardous voltages. It does not
conform to safety requirements for routine AC line voltage isolation.
Protection class
Protection Class II according to EN 61131-2 (Protective conductor not required)
Degree of protection
IP20 Mechanical Protection, EN 60529
Protects against finger contact with high voltage as tested by standard probe. External
protection required for dust, dirt, water and foreign objects of < 12.5mm in diameter.
Easy Book
Manual, 04/2012, A5E02486774-05 243
Rated voltages
Table A- 7 Rated voltages
Rated voltage Tolerance

24 VDC 20.4 VDC to 28.8 VDC
22.0 VDC to 28.8 VDC for ambient temperature -20 C to 0 C
120/230 VAC 85 VAC to 264 VAC, 47 to 63 Hz
NOTICE
When a mechanical contact turns on output power to the S7-1200 CPU, or any digital
signal module, it sends a "1" signal to the digital outputs for approximately 50
microseconds. This could cause unexpected machine or process operation which could
result in death or serious injury to personnel and/or damage to equipment. You must plan
for this, especially if you are using devices which respond to short duration pulses.
Reverse voltage protection

Reverse voltage protection circuitry is provided on each terminal pair of +24 VDC power or
user input power for CPUs, signal modules (SMs), and signal boards (SBs). It is still possible
to damage the system by wiring different terminal pairs in opposite polarities.
Some of the 24 VDC power input ports in the S7-1200 system are interconnected, with a
common logic circuit connecting multiple M terminals. For example, the following circuits are
interconnected when designated as "not isolated" in the data sheets: the 24 VDC power
supply of the CPU, the power input for the relay coil of an SM, or the power supply for a non-
isolated analog input. All non-isolated M terminals must connect to the same external
reference potential.
WARNING
Connecting non-isolated M terminals to different reference potentials will cause unintended

current flows that may cause damage or unpredictable operation in the PLC and any
connected equipment.
Failure to comply with these guidelines could cause damage or unpredictable operation
which could result in death or serve personal injury and/or property damage.
Always ensure that all non-isolated M terminals in an S7-1200 system are connected to the
same reference potential.
DC Outputs
Short circuit protection circuitry is not provided for DC outputs on CPUs, signal modules
(SMs) and signal boards (SBs).
Easy Book
244 Manual, 04/2012, A5E02486774-05
A.2 CPU modules
Relay electrical service life

The typical performance data supplied by relay vendors is shown below. Actual performance
may vary depending upon your specific application. An external protection circuit that is
adapted to the load will enhance the service life of the contacts.
Service life (x 103 operations)

250 VAC resistive load
30 VDC resistive load

250 VAC inductive load (p.f=0.4)

30 VDC inductive load (L/R=7ms)

Rated Operating Current (A)

A.2 CPU modules

For a more complete list of modules available for S7-1200, refer to the S7-1200 System
Manual or to the customer support web site (http://www.siemens.com/automation/).
Table A- 8 General specifications
General specifications CPU 1211C CPU 1212C CPU 1214C CPU 1215C
Dimensions W x H x D (mm) 90 x 100 x 75 90 x 100 x 75 110 x 100 x 75 130 x 100 x 75
Weight AC/DC/Relay 420 grams 425 grams 475 grams 530 grams
DC/DC/Relay 380 grams 385 grams 435 grams 585 grams
DC/DC/DC 370 grams 370 grams 415 grams 520 grams
Power AC/DC/Relay 10 W 11 W 14 W 14 W
dissipation
DC/DC/Relay 8W 9W 12 W 12 W
DC/DC/DC 8W 9W 12 W 12 W
Current available (5 VDC) for SM 750 mA max. 1000 mA max. 1600 mA max. 1600 mA max.
and CM bus
Current available (24 VDC) sensor 300 mA max. 300 mA max. 400 mA max. 400 mA max.
power
Digital input current consumption 4 mA/input used 4 mA/input used 4 mA/input used 4 mA/inputs used
(24VDC)
Easy Book
Manual, 04/2012, A5E02486774-05 245
A.2 CPU modules
Table A- 9 CPU features
CPU features CPU 1211C CPU 1212C CPU 1214C CPU 1215C
User memory
Work memory 30 Kbytes 50 Kbytes 75 Kbytes 100 Kbytes
Load memory 1 Mbyte 1 Mbyte 4 Mbytes 4 Mbytes
Retentive memory 10 Kbytes 10 Kbytes 10 Kbytes 10 Kbytes
On-board digital I/O 6 inputs 8 inputs 14 inputs 14 inputs
See specifications 4 outputs 6 outputs 10 outputs 10 outputs
(Page 256).
On-board analog I/O 2 inputs 2 inputs 2 inputs 2 inputs
See specifications 2 outputs
(Page 264).
Process image size
Inputs 1024 bytes 1024 bytes 1024 bytes 1024 bytes
Outputs 1024 bytes 1024 bytes 1024 bytes 1024 bytes
Bit memory (M) 4096 bytes 4096 bytes 8192 bytes 8192 bytes
Temporary (local) 16 Kbytes for startup and program cycle (including associated FBs and FCs)
memory
4 Kbytes for standard interrupt events including FBs and FCs
4 Kbytes for error interrupt events including FBs and FCs
SM modules expansion None 2 SMs max. 8 SMs max. 8 SMs max.
SB, CB or BB 1 max. 1 max. 1 max. 1 max.
expansion
CM expansion 3 max. 3 max. 3 max. 3 max.
High-speed counters 3 built-in I/O, 5 with 4 built-in I/O, 6 with 6 total 6 total
SB SB
Single phase 3 at 100 kHz 3 at 100 kHz and 3 at 100 kHz and 3 at 100 kHz and
(clock rate) SB: 2 at 30 kHz 1 at 30 kHz 3 at 30 kHz 3 at 30 kHz
SB: 2 at 30 kHz
Quadrature phase 3 at 80 kHz 3 at 80 kHz and 3 at 80 kHz and 3 at 80 kHz and

(clock rate) SB: 2 at 20 kHz 1 at 20 kHz 3 at 20 kHz 3 at 20 kHz
SB: 2 at 20 kHz
Pulse outputs 1 4 4 4 4
Pulse catch inputs 6 8 14 14
Time delay / cyclic 4 total 4 total 4 total 4 total
interrupts with 1 ms resolution with 1 ms resolution with 1 ms resolution with 1 ms resolution
Edge interrupts 6 rising and 6 falling 8 rising and 8 falling 12 rising and 12 falling 12 rising and 12 falling
With optional SB 10 rising and 10 falling 12 rising and 12 falling 16 rising and 16 falling 16 rising and 16 falling
Easy Book
246 Manual, 04/2012, A5E02486774-05
A.2 CPU modules
CPU features CPU 1211C CPU 1212C CPU 1214C CPU 1215C
Real time clock
Accuracy +/- 60 +/- 60 +/- 60 +/- 60
seconds/month seconds/month seconds/month seconds/month
Retention time 20 days typ./12 20 days typ./12 20 days typ./12 20 days typ./12
(maintenance-free days min. at 40C days min. at 40C days min. at 40C days min. at 40C
Super Capacitor)
Execution speed
Boolean 0.08 s/ instruction 0.08 s/ instruction 0.08 s /instruction 0.08 s/ instruction
Move Word 12 s/instruction 12 s/instruction 12 s/instruction 12 s/instruction
Real Math 18 s/instruction 18 s/instruction 18 s/instruction 18 s/instruction
Table A- 10 Communication
Technical data CPU 1211C, CPU 1212C, CPU 1214C CPU 1215C
Communication 1 Ethernet port 2 Ethernet ports
Data rates 10/100 Mb/s 10/100 Mb/s
Isolation (external signal to PLC logic) Transformer isolated, 1500 VDC Transformer isolated,
Cable type CAT5e shielded 1500 VDC
CAT5e shielded
Devices 3 HMI1 3 HMI1
1 PG 1 PG
Ethernet connections2 8 (active or passive) 8 (active or passive)
CPU-to-CPU S7 connections (GET/PUT) 8 (client) 8 (client)
3 (server) 3 (server)
1 The CPU provides dedicated HMI connections to support up to 3 HMI devices. (You can have up to 2 SIMATIC Comfort
panels.) The total number of HMI is affected by the types of HMI panels in your configuration. For example, you could
have up to three SIMATIC Basic panels connected to your CPU, or you could have up to two SIMATIC Comfort panels
with one additional Basic panel.
2 Open User Communication connections (active or passive): TSEND_C, TRCV_C, TCON, TDISCON, TSEND, and
TRCV.
Easy Book
Manual, 04/2012, A5E02486774-05 247
A.2 CPU modules
Table A- 11 Wiring diagram for CPU 1214C AC/DC/Relay
CPU 1214C AC/DC/Relay

X10
X11
X12
24 VDC Sensor Power Out. For additional noise immunity, connect "M" to chassis ground
even if not using sensor supply.
For sinking inputs, connect "-" to "M" (shown). For sourcing inputs, connect "+" to "M".
Table A- 12 Wiring diagram for CPU 1214C DC/DC/DC
CPU 1214C DC/DC/DC

X11
X10
X12
24 VDC Sensor Power Out. For additional noise immunity, connect "M" to chassis ground
even if not using sensor supply.
Easy Book
248 Manual, 04/2012, A5E02486774-05
A.3 Digital I/O modules

A.3.1 SB 1221, SB 1222, and SB 1223 digital input/output (DI, DQ, and DI/DQ)
Table A- 13 SB 1221 digital input (DI) and SB 1222 digital output (DQ) modules
General SB 1221 4 DI (200 kHz) SB 1222 4 DQ (200 kHz)

Order number 24 VDC: 6ES7 221-3BD30-0XB0 24 VDC: 6ES7 222-1BD30-0XB0
5 VDC: 6ES7 221-3AD30-0XB0 5 VDC: 6ES7 222-1AD30-0XB0
Dimensions W x H x D (mm) 38 x 62 x 21 38 x 62 x 21
Weight 35 grams 35 grams
Power dissipation 24 VDC: 1.5 W 0.5 W
5 VDC: 1.0 W
Current SM Bus 40 mA 35 mA
consumption 24 VDC 15 mA
24 VDC: 7 mA / input + 20 mA
Inputs/outputs 4 inputs (source) 4 outputs (solid state - MOSFET)
Table A- 14 SB 1223 combination digital input/output (DI / DQ) modules
General SB 1223 DI / DQ (200 kHz) SB 1223 2 DI / 2 DQ

Order number 24 VDC: 6ES7 223-3BD30-0XB0 6ES7 223-0BD30-0XB0
5 VDC: 6ES7 223-3AD30-0XB0
Power dissipation 24 VDC: 1.0 W 24VDC: 1.0 W
5 VDC: 0.5 W
Current SM Bus 35 mA 50 mA
consumption 24 VDC 4 mA / input used
Inputs/outputs 2 inputs (source) 2 inputs (IEC Type 1 sink)
2 outputs (solid state - MOSFET) 2 outputs (solid state - MOSFET)
Easy Book
Manual, 04/2012, A5E02486774-05 249
Note
The high-speed (200 kHz) SBs utilize "sourcing" inputs. The standard SB (20 kHz) utilizes
"sinking" inputs. Refer to the specifications for the digital inputs and outputs (Page 256).
The high-speed (200 kHz) outputs (SB 1222 and SB 1223) can be either sourcing or sinking.
For sourcing outputs, connect "Load" to "-" (shown). For sinking outputs, connect "Load" to
"+". Because both sinking and sourcing configurations are supported by the same circuitry,
the active state of a sourcing load is opposite that of a sinking load. A source output exhibits
positive logic (Q bit and LED are ON when the load has current flow), while a sink output
exhibits negative logic (Q bit and LED are OFF when the load has current flow). If the
module is plugged in with no user program, the default for this module is 0V, which means
that a sinking load will be turned ON.
Table A- 15 Wiring diagrams for digital SBs
SB 1221 input module SB 1222 output module SB 1223 input/output module

SB 1221 DI 4 (200 kHz) SB 1222 DQ 4 (200 kHz) SB 1223 DI 2 / DQ2 (200 kHz)
X19 X19
Supports sourcing inputs only. For sourcing outputs, connect Supports sourcing inputs only.
"Load" to "-" (shown). For sinking
outputs, connect "Load" to "+".
For sourcing outputs, connect
"Load" to "-" (shown). For sinking
outputs, connect "Load" to "+".
Easy Book
250 Manual, 04/2012, A5E02486774-05
Note
The high-speed (200 kHz) SBs (SB 1221 and SB 1223) support only sinking inputs. The
standard SB 1223 supports only sourcing inputs.
The high-speed (200 kHz) outputs (SB 1222 and SB 1223) can be either sourcing or sinking.
For sourcing outputs, connect "Load" to "-" (shown). For sinking outputs, connect "Load" to
"+". Because both sinking and sourcing configurations are supported by the same circuitry,
the active state of a sourcing load is opposite that of a sinking load. A source output exhibits
positive logic (Q bit and LED are ON when the load has current flow), while a sink output
exhibits negative logic (Q bit and LED are OFF when the load has current flow). If the
module is plugged in with no user program, the default for this module is 0V, which means
that a sinking load will be turned ON.
A.3.2 SM 1221 digital input (DI)
Table A- 16 SM 1221 digital input (DI)
Technical data SM 1221 DI 8 (24VDC) SM 1221 DI 16 (24VDC)

Order number 6ES7 221-1BF30-0XB0 6ES7 221-1BH30-0XB0
Number of inputs (DI) 8 16
See specifications (Page 256).
Power dissipation 1.5 W 2.5 W
Current consumption SM Bus 105 mA 130 mA
24 VDC 4 mA / input used 4 mA / input used
Easy Book
Manual, 04/2012, A5E02486774-05 251
Table A- 17 Wiring diagram for SM 1221 digital input (DI) modules
SM 1221 DI 8 (24 VDC) SM 1221 DI 16 (24 VDC)
X10 X10
X11
X11
X12
X13
For sinking inputs, connect "-" to "M" (shown). For sourcing inputs connect "+" to "M".
A.3.3 SM 1222 digital output (DQ)
Table A- 18 SM 1222 digital output (DQ)
Technical data SM 1222 DQ (Relay) SM 1222 DQ (24VDC)

Order number DQ 8: 6ES7 222-1HF30-0XB0 DQ 8: 6ES7 222-1BF30-0XB0
DQ 8 Changeover: 6ES7 222- DQ 16: 6ES7 222-1BH30-0XB0
1XF30-0XB0
DQ 16: 6ES7 222-1HH30-0XB0
Number of outputs (DQ) 8 (DQ 8 and DQ 8 Changeover) 8 (DQ 8)
See specifications (Page 256). 16 (DQ 16) 16 (DQ 16)
Dimensions W x H x D (mm) DQ 8and DQ 16: 45 x 100 x 75 45 x 100 x 75
DQ 8 Changeover: 70 x 100 x 75
Weight DQ 8: 190 grams DQ 8: 180 grams
DQ 8 Changeover: 310 grams DQ 16: 220 grams
DQ 16: 260 grams
Easy Book
252 Manual, 04/2012, A5E02486774-05
Technical data SM 1222 DQ (Relay) SM 1222 DQ (24VDC)

Power dissipation DQ 8: 4.5 W DQ 8: 1.5 W
DQ 8 Changeover: 5 W DQ 16: 2.5 W
DQ 16: 8.5 W
Current consumption SM Bus DQ 8: 120 mA DQ 8: 120 mA
DQ 8 Changeover: 140 mA DQ 16: 140 mA
DQ 16: 135 mA
24 VDC DQ 8 and DQ 16:11 mA / Relay coil DQ 8: --
used DQ 16: --
DQ 8 Changeover: 16.7 mA Relay
coil used
Table A- 19 Wiring diagram for SM 1222 digital output (DQ) modules
SM 1222 DQ 16 (24 VDC output) SM 1222 DQ 16 (Relay output)
X10 X10
X11
X11
X12 X12
X13 X13
Easy Book
Manual, 04/2012, A5E02486774-05 253
A.3.4 SM 1223 VDC digital input/output (DI / DQ)
Table A- 20 SM 1223 combination digital input / output (DI / DQ)
Technical data SM 1223 DI (24 VDC) / DQ (Relay) SM 1223 DI (24 VDC) / DQ (24 VDC)
Order number DI 8 / DQ 8: 6ES7 223-1PH30-0XB0 DI 8 / DQ 8: 6ES7 223-1BH30-0XB0
DI 16 / DQ 16: 6ES7 223-1PL30-0XB0 DI 8 / DQ 8: 6ES7 223-1BL30-0XB0
Number of inputs / outputs (DI Inputs: 8 or 16 (24 VDC) Inputs: 8 or 16 (24 VDC)
/ DQ)
Outputs: 8 or 16 (relay) Outputs: 8 or 16 (24 VDC)
See specifications (Page 256).
Dimensions W x H x D DI 8 / DQ 8: 45 x 100 x 75 DI 8 / DQ 8: 45 x 100 x 75
(mm)
DI 16 / DQ 16: 70 x 100 x 75 DI 16 / DQ 16: 70 x 100 x 75
Weight DI 8 / DQ 8: 230 grams DI 8 / DQ 8: 210 grams
DI 16 / DQ 16: 350 grams DI 16 / DQ 16: 310 grams
Power dissipation DI 8 / DQ 8: 5.5 W DI 8 / DQ 8: 2.5 W
DI 16 / DQ 16: 10 W DI 16 / DQ 16: 4.5 W
Current SM Bus DI 8 / DQ 8: 145 mA DI 8 / DQ 8: 145 mA
consumption
DI 16 / DQ 16: 180 mA DI 16 / DQ 16: 185 mA
24 VDC 4 mA / input used 4 mA / input used
11 mA / Relay coil used
Table A- 21 Wiring diagram for SM 1223 combination DI / DQ modules
SM 1223 DI 16 (24 VDC) / DQ 16 (24 VDC) SM 1223 DI 16 (24 VDC) / DQ 16 (Relay)

X10
X10
X10 X11
X12 X12
X13 X13
Easy Book
254 Manual, 04/2012, A5E02486774-05
A.3.5 SM 1223 120/230 VAC input / Relay output
Table A- 22 SM 1223 combination VAC digital input / output (DI / DQ)
Technical data SM 1223 DI (120/230 VAC) / DQ (Relay)

Order number DI 8 / DQ 8: 6ES7 223-1QH30-0XB0
Number of inputs / outputs (DI / DQ) Inputs: 8 (120/230 VAC)
See the specifications for 120/230 VAC inputs (Page 257).
Outputs: 8 (relay)
See the specifications for the digital outputs (Page 258).
Dimensions W x H x D (mm) 45 x 100 x 75
Weight 190 grams
Power dissipation 7.5 W
Current SM Bus 120 mA
consumption 24 VDC 11 mA / relay coil used
Note
The SM 1223 DI 8 x 120/230 VAC, DQ 8 x Relay signal module (6ES7 223-1QH30-0XB0) is
approved for use in Class 1, Division 2, Gas Group A, B, C, D, Temperature
Class T4 Ta = 40 C.
Table A- 23 Wiring diagram for SM 1223 DI 8 (120/230 VAC) / DQ 8 (Relay)
SM 1223 DI 8 (120/230 VAC) / DQ 8 (Relay)
X10
X11
X12
X13
Easy Book
Manual, 04/2012, A5E02486774-05 255
A.4 Specifications for the digital inputs and outputs
A.4.1 24 VDC digital inputs (DI)
Table A- 24 Specifications for the digital inputs (DI)
Technical data CPU, SM and SB High-speed SB (200 KHz)

Type CPU and SM: IEC Type 1 sink SB 1221 200 KHz and SB 1223200 KHz:
(Sink/Source) Source
SB 1223: IEC Type 1 sink
(Sink only)
Rated voltage 24 VDC at 4 mA, nominal 24 VDC SB: 24 VDC at 7 mA, nominal
5 VDC SB: 5 VDC at 15 mA, nominal
Continuous permissible 30 VDC, max. 24 VDC SB: 28.8 VDC
voltage 5 VDC SB: 6 VDC
Surge voltage 35 VDC for 0.5 sec. 24 VDC SB: 35 VDC for 0.5 sec
5 VDC SB: 6 V
Logic 1 signal (min.) 15 VDC at 2.5 mA 24 VDC SB: L+ minus 10 VDC at 2.9 mA
5 VDC SB: L+ minus 2.0 VDC at 5.1 mA
Logic 0 signal (max.) 5 VDC at 1 mA 24 VDC SB: L+ minus 5 VDC at 1.4 mA
5 VDC SB: L+ minus 1.0 VDC at 2.2 mA
Isolation (field side to logic) 500 VAC for 1 minute 500 VAC for 1 minute
Isolation groups CPU: 1 SB 1221 DI 4: 1
SM 1221 DI 8: 2 SB 1223 DI 2: 1
SM 1221 DI 16: 4
SB 1223 DI 2: 1
SM 1223: 2
Filter times 0.2, 0.4, 0.8, 1.6, 3.2, 6.4, and 12.8 ms 0.2, 0.4, 0.8, 1.6, 3.2, 6.4, and 12.8 ms
(selectable in groups of 4) (selectable in groups of 4)
Number of inputs on SM 1221 and SM 1223 DI 8: 8 SB 1221 DI 4: 4
simultaneously
SM 1221 and SM 1223 DI 16: 16 SB 1223 DI 2: 2
SB 1223 DI 2: 2
Cable length (meters) 500 m shielded, 300 m unshielded 50 m shielded twisted pair
CPU: 50 m shielded for HSC
Easy Book
256 Manual, 04/2012, A5E02486774-05
NOTICE
When switching frequencies above 20 KHz, it is important that the digital inputs receive a
square wave. Consider the following options to improve the signal quality to the inputs:
Minimize the cable length
Change a driver from a sink only driver to a sinking and sourcing driver
Change to a higher quality cable
Reduce the circuit/components from 24 V to 5 V
Add an external load at the input
Table A- 25 HSC clock input rates (max.)
Technical data Single phase Quadrature phase

CPU 1211C 100 KHz 80 KHz
CPU 1212C 100 KHz (Ia.0 to Ia.5) and 80 KHz (Ia.0 to Ia.5) and
30 KHz (Ia.6 to Ia.7) 20 KHz (Ia.6 to Ia.7)
CPU 1214C, CPU 1215C 100 KHz (Ia.0 to Ia.5) and 80 KHz (Ia.0 to Ia.5) and
30 KHz (Ia.6 to Ib.5) 20 KHz (Ia.6 to Ib.5)
High-speed (200 KHz) SB 200 kHz 160 kHz
Standard-speed (20 KHz) SB 30 kHz 20 kHz
1 Logic 1 level = 15 to 26 VDC
A.4.2 120/230 VAC digital AC inputs
Table A- 26 120/230 VAC digital inputs
Technical data SM
Type IEC Type 1
Rated voltage 120 VAC at 6 mA, 230 VAC at 9 mA
Continuous permissible voltage 264 VAC
Surge voltage N/A
Logic 1 signal (min.) 79 VAC at 2.5 mA
Logic 0 signal (max.) 20 VAC at 1 mA
Leakage current (max.) 1 mA
Isolation (field side to logic) 1500 VAC for 1 minute
Isolation groups1 4
Input delay times Typical: 0.2 to 12.8 ms, user selectable
Maximum: --
Connection of 2 wire proximity sensor (Bero) (max.) 1 mA
Easy Book
Manual, 04/2012, A5E02486774-05 257
Technical data SM
Cable length Unshielded 300 meters
Shielded 500 meters
Number of inputs on simultaneously 8
1 Channels within a group must be of the same phase.
A.4.3 Digital outputs (DQ)
Table A- 27 Specifications for the digital outputs (DQ)
Technical data Relay 24V DC 200 KHZ 24V DC

(CPU and SM) (CPU, SM, and SB) (SB)
Type Relay, dry contact Solid state - MOSFET Solid state - MOSFET
(Source) (Sink/Source)
Voltage range 5 to 30 VDC or 20.4 to 28.8 VDC 20.4 to 28.8 VDC 1
5 to 250 VAC 4.25 to 6.0 VDC 2
Logic 1 signal at max. current N/A 20 VDC min. L+ minus 1.5 V 1
L+ minus 0.7 V 2
Logic 0 signal with 10 K load N/A CPU: 20 VDC min., 1.0 VDC, max. 1
0.1 VDC max. 0.2 VDC, max. 2
SB: 0.1 VDC max.
SM DC: 0.1 VDC max.
Current (max.) 2.0 A 0.5 A 0.1 A
Lamp load 30 W DC / 200 W AC SB: 5 W N/A
ON state resistance 0.2 max. when new 0.6 max. 11 max. 1 or 7 max. 2
OFF state resistance N/A N/A 6 max. 1 or 0.2 max. 2
Leakage current per point N/A 10 A max. N/A
Pulse Train Output rate CPU: N/A3 CPU: 100 KHz max.,2 Hz 200 kHz max., 2 Hz min.
min.4
SB: 20 KHz max., 2 Hz min.5
Surge current 7 A with contacts closed CPU: 8 A for 100 ms max. 0.11 A
SB: 5 A for 100 ms max.
SM: 8 A for 100 ms max.
Overload protection No No No
Isolation (field side to logic) Coil to contact: 1500 VAC 500 VAC for 1 minute 500 VAC for 1 minute
for 1 minute
Coil to logic: None
Easy Book
258 Manual, 04/2012, A5E02486774-05

Isolation groups CPU 1211C: 1 CPU: 1 16
CPU 1212C: 2 SB: 1
CPU 1214C: 2 SM (DQ 8): 1
CPU 1215C: 2 SM (DQ 16): 1
SM DQ 8: 2
SM DQ 8 Changeover:8
SM DQ 16: 4
Isolation resistance 100 M min. when new N/A N/A
Isolation between open 750 VAC for 1 minute N/A N/A
contacts
Current per common CPU: CPU: 0.4 A
SM Relay: SB: 1 A
SM 1222: 10 A (DQ 8 SM DQ 8: 4 A
and DQ 16) SM DQ 16: 8 A
SM 1223 DI 8 / DQ 8
Relay: 10 A
SM 1223 DI 16 / DQ 16
Relay: 8 A
Inductive clamp voltage N/A L+ minus 48 V, None
1 W dissipation
Maximum relay switching 1 Hz N/A N/A
frequency
Switching delay 10 ms max. CPU: 1.5 s + 300 s rise 1
1.5 s + 300 ns fall 1
Qa.0 to Qa.3: 1.0 s
max., off-to-on 3.0 s 200 ns + 300 ns rise 2
max., on-to-off 200 ns + 300 ns fall 2
Qa.4 to Qb.1: 50 s
max., off-to-on
200 s max., on-to-off
SB: 2 s max. off-to-on;
10 s max. on-to-off
SM: 50 s max. off-to-on
200 s max. on-to-off
Lifetime mechanical (no load) Relay: 10,000,000 N/A N/A
open/close cycles
Lifetime contacts at rated load Relay: 100,000 open/close N/A N/A
cycles
Easy Book
Manual, 04/2012, A5E02486774-05 259
A.5 Analog I/O modules

Behavior on RUN to STOP Last value or substitute Last value or substitute Last value or substitute
value (default value 0) value (default value 0) value (default value 0)
Cable length (meters) 500 m shielded, 500 m shielded, 50 m shielded twisted pair
150 m unshielded 150 m unshielded
1 24 VDC 200 KHz SB
2 5 VDC 200 KHz SB
4 Depending on your pulse receiver and cable, an additional load resistor (at least 10% of rated current) may improve
pulse signal quality and noise immunity.
5 Depending on your pulse receiver and cable, an additional load resistor (at least 10% of rated current) may improve
pulse signal quality and noise immunity.
6 SB 1223 200 KHz DI 2 / DQ 2: No isolation to inputs

A.5.1 SB 1231 and SB 1232 analog input (AI) and output (AQ)
Technical data SB 1231 AI 1 (12 bit) 1 SB 1232 AQ 1 (12bit)

Order number 6ES7 231-4HA30-0XB0 6ES7 232-4HA30-0XB0
Dimensions W x H x D (mm) 38 x 62 x 21 mm 38 x 62 x 21 mm
Current consumption (SM Bus) 55 mA 15 mA
Current consumption (24 VDC) None 40 mA (no load)
Number of inputs / outputs 1 1
Type Voltage or current (differential) Voltage or current
1 To use the SB 1231 AI 1 x analog input, your CPU firmware must be V2.0 or higher.
Easy Book
260 Manual, 04/2012, A5E02486774-05
Table A- 29 Wiring diagrams for the analog SBs
SB 1231 AI 1 (12 bit) SB 1232 AQ 1 (12 bit)
X19
X19
Connect "R" and "0+" for current.
A.5.2 SM 1231 analog input (AI)
Table A- 30 SM 1231 analog inputs (AI)
Technical data SM 1231 AI 4 (13 bit) SM 1231 AI 8 (13 bit) SM 1231 AI 4 x 16 bit
Order number (MLFB) 6ES7 231-4HD30-0XB0 6ES7 231-4HF30-0XB0 6ES7 231-5ND30-0XB0
Number of inputs 4 inputs (AI) 8 inputs (AI) 4 inputs
Type Voltage or current Voltage or current Voltage or current
(differential), selectable in (differential), selectable in (differential)
groups of 2 groups of 2
Dimensions W x H x D (mm) 45 x 100 x 75 45 x 100 x 75 45 x 100 x 75
Weight 180 grams 180 grams 180 grams
Power dissipation 1.5 W 1.5 W 1.8 W
Current consumption (SM Bus) 80 mA 90 mA 80 mA
Current consumption (24 VDC) 45 mA 45 mA 65 mA
A.5.3 SM 1232 analog output (AQ)
Table A- 31 SM 1232 analog outputs (AQ)
Technical data SM 1232 AQ 2 (14bit) SM 1232 AQ 4 (14bit)

Order number (MLFB) 6ES7 232-4HB30-0XB0 6ES7 232-4HD30-0XB0
Number and type of outputs 2 outputs (AQ) 4 outputs (AQ)
Easy Book
Manual, 04/2012, A5E02486774-05 261
Technical data SM 1232 AQ 2 (14bit) SM 1232 AQ 4 (14bit)

Current consumption (24 VDC) 45 mA (no load) 45 mA (no load)
A.5.4 SM 1234 analog input/output (AI/AQ)
Table A- 32 SM 1234 combination analog input / output (AI / AQ)
Technical data SM 1234 AI 4 (13 bit) / AQ 2 (14 bit)

Order number (MLFB) 6ES7 234-4HE30-0XB0
Number of inputs 4 inputs (AI)
Type Voltage or current (differential), selectable in groups of 2
Number of outputs 2 outputs (AQ)
Type Voltage or current (differential)
Weight 220 grams
Power dissipation 2.0 W
Current consumption (SM Bus) 80 mA
Current consumption (24 VDC) 60 mA (no load)
Easy Book
262 Manual, 04/2012, A5E02486774-05
A.6 BB 1297 Battery Board
A.5.5 Wiring diagrams for SM 1231 (AI), SM 1232 (AQ), and SM 1234 (AI/AQ)
Table A- 33 Wiring diagrams for the analog SMs
SM 1231 AI 8 (13 bit) SM 1232 AQ 4 (13 bit) SM 1234 AI 4 (13bit) / AQ2 (14 bit)
X10
X10 X10
X11 X11
X11
X12
X12 X12
X13
X13 X13
Note
Unused analog inputs should be inserted.
When the inputs are configured for "current" mode, no current will flow through the input
unless you supply external power to the module.
A.6 BB 1297 Battery Board
BB 1297 Battery Board
Technical data BB 1297 Battery

Order number 6ES7 297-1AX30-0XA0
Weight
Easy Book
Manual, 04/2012, A5E02486774-05 263
A.7 Specifications for the analog I/O
Technical data BB 1297 Battery

Hold up time real time clock Up to about 1 year
Type of battery TBD / "off the shelf battery"
Tool free customer replaceable
"Maint" LED of the CPU Indicating a battery replacement is needed
User program Application / system can evaluate battery status
The BB 1297 Battery board is used for applications where the real time clock retention time
is beyond one month. Features of the BB 1297 Battery board are shown below:
Supports time of day clock during PLC power off. The S7-1200 CPU, in combination with
the BB 1297 Battery board, supports the Time of Day clock retention during a power off
period of the application for up to one year.
Only one BB 1297 Battery board or other SB can be used at a time.
Hot plugging / hot swapping is not allowed. The BB 1297 Battery board is only
exchangeable or pluggable while the CPU is powered off. While the CPU is powered off,
and the BB 1297 is removed to exchange the actual battery, the internal super cap will
hold the time of day while the user replaces the battery.
The CPU "Maint" LED indicates when a replacement battery is needed.
The user program allows you to monitor or check on the status of the battery, and battery
board and allows a user message to be displayed on an HMI or web server.
A.7.1 Specifications for the analog inputs (CPU, SM, and SB)
Table A- 35 Specifications for analog inputs (AI)
Technical data CPU SB SM

Type Voltage (single-ended) Voltage or current Voltage or current
(differential) (differential), selectable in
groups of 2
Range 0 to 10 V 10 V, 5 V, 2.5, or 10 V, 5 V, 2.5 V, or
0 to 20 mA 0 to 20 mA
Resolution 10 bits 11 bits + sign bit 12 bits + sign bit
Full scale range 0 to 27648 -27,648 to 27,648 -27,648 to 27,648
(data word)
Accuracy 3.0% / 3.5% of full-scale 0.3% / 0.6% of full scale 0.1% / 0.2% of full scale
(25C / -20 to 60C)
Overshoot / undershoot range Voltage: Voltage: Voltage:
(data word) 27,649 to 32,511 32,511 to 27,649 / 32,511 to 27,649 /
-27,649 to -32,512 -27,649 to -32,512
Easy Book
264 Manual, 04/2012, A5E02486774-05
Technical data CPU SB SM

(See note 1) Current: N/A Current: Current:
32,511 to 27,649 / 32,511 to 27,649 /
0 to -4864 0 to -4864
Overflow / underflow (data Voltage: Voltage: Voltage:
word) 32,512 to 32,767 32,767 to 32,512 / 32,767 to 32,512 /
(See note 1) -32,513 to -32,768 -32,513 to -32,768
Current: N/A Current: Current:
32,767 to 32,512 / 32,767 to 32,512 /
-4865 to -32,768 -4865 to -32,768
Maximum withstand voltage / 35 VDC (voltage) 35 V / 40 mA 35 V / 40 mA
current
Smoothing None, weak, medium, or None, weak, medium, or None, weak, medium, or
(See note 2) strong strong strong
Noise rejection 10, 50, or 60 Hz 400, 60, 50, or 10 Hz 400, 60, 50, or 10 Hz
(See note 2)
Measuring principle Actual value conversion Actual value conversion Actual value conversion
Common mode rejection 40 dB, DC to 60 Hz 40 dB, DC to 60 Hz 40 dB, DC to 60 Hz
Operational signal range Less than +12 V and Less than +35 V and Less than +12 V and greater
(signal plus common mode greater than -12 V greater than -35 V than -12 V
voltage)
Load impedance Differential: 100 K Differential: Differential:
220 K (voltage), 9 M (voltage),
250 (current) 250 (current)
Common mode: Common mode:
55 K (voltage), 4.5 M (voltage),
55 K (current) 4.5 M (current)
Isolation (field side to logic) None None None
Cable length (meters) 100 m, shielded twisted pair 100 m, twisted and shielded 100 m twisted and shielded
Diagnostics Overflow / underflow Overflow / underflow Overflow / underflow
(see note 3)
24 VDC low voltage
Note 1: Refer to the analog input measurement ranges for voltage and current (Page 266) to determine the
overshoot/undershoot and overflow/underflow ranges.
Note 2: Refer to the step response times (Page 267) to determine the smoothing and noise rejection values.
Note 3: For SM 1231 AI 4 (13 bit): If a voltage greater than +30 VDC or less than -15 VDC is applied to the input, the
resulting value will be unknown and the corresponding overflow or underflow may not be active.
Easy Book
Manual, 04/2012, A5E02486774-05 265
A.7.2 Input (AI) measurement ranges for voltage and current
Table A- 36 Analog input representation for voltage
System Voltage Measuring Range

Decimal Hexadecimal 10 V 5 V 2.5 V 1.25V 0 to 10 V
32767 7FFF 11.851 V 5.926 V 2.963 V 1.481 V Overflow 11.851 V Overflow
32512 7F00
32511 7EFF 11.759 V 5.879 V 2.940 V 1.470 V Overshoot 11.759 V Overshoot
27649 6C01 range range
27648 6C00 10 V 5V 2.5 V 1.250 V Rated range 10 V Rated
20736 5100 7.5 V 3.75 V 1.875 V 0.938 V 7.5 V range
1 1 361.7 V 180.8 V 90.4 V 45.2 V 361.7 V

0 0 0V 0V 0V 0V 0V
-1 FFFF Negative
-20736 AF00 -7.5 V -3.75 V -1.875 V -0.938 V values are
not
-27648 9400 -10 V -5 V -2.5 V -1.250 V supported
-27649 93FF Undershoot
-32512 8100 -11.759 V -5.879 V -2.940 V -1.470 V range
-32513 80FF Underflow

-32768 8000 -11.851 V -5.926 V -2.963 V -1.481 V
Table A- 37 Analog input representation for current
System Current measuring range

Decimal Hexidecimal 0 mA to 20 mA 4 mA to 20 mA
32767 7FFF 23.70 mA 22.96 mA Overflow
32512 7F00
32511 7EFF 23.52 mA 22.81 mA Overshoot range
27649 6C01
27648 6C00 20 mA 20 mA Nominal range
20736 5100 15 mA 16 mA
1 1 723.4 nA 4 mA + 578.7 nA
0 0 0 mA 4 mA
-1 FFFF Undershoot range
-4864 ED00 -3.52 mA 1.185 mA
-4865 ECFF Underflow
-32768 8000
Easy Book
266 Manual, 04/2012, A5E02486774-05
A.7.3 Step response for the analog inputs (AI)

The following table shows the step response times for the analog inputs (AI) of the CPU, SB
and SM.
Table A- 38 Step response (ms) for the analog inputs
Smoothing selection (sample averaging) Integration time selection 1

400 Hz (2.5 ms) 60 Hz (16.6 ms) 50 Hz (20 ms) 10 Hz (100 ms)
None (1 cycle): CPU N/A 63 65 130
No averaging SB 4.5 18.7 22.0 102
SM 4 18 22 100
Weak (4 cycles): CPU N/A 84 93 340
4 samples SB 10.6 59.3 70.8 346
SM 9 52 63 320
Medium (16 cycles): CPU N/A 221 258 1210
16 samples SB 33.0 208 250 1240
SM 32 203 241 1200
Strong (32 cycles): CPU N/A 424 499 2410
32 samples SB 63.0 408 490 2440
SM 61 400 483 2410
Sample rate CPU N/A 4.17 5 25
SB 0.156 1.042 1.250 6.250
SM
(4 channels) 0.625 4.17 5 25
(8 channels) 1.25 4.17 5 25
1 0V to 10V, measured at 95% (CPU and SB), 0 to full-scale, measured at 95% (SM),
A.7.4 Sample time and update times for the analog inputs
Table A- 39 Sample time and update time for SM and CPU
Rejection frequency Sample time Update time for all channels

(Integration time)
4-channel SM 8-channel SM CPU AI
400 Hz (2.5 ms) 0.625 ms 1 2.5 ms 10 ms N/A ms
60 Hz (16.6 ms) 4.170 ms 4.17 ms 4.17 ms 4.17 ms
50 Hz (20 ms) 5.000 ms 5 ms 5 ms 5 ms
10 Hz (100 ms) 25.000 ms 25 ms 25 ms 25 ms
1 Sample rate for 8-channel SM is 1.250 ms.
Easy Book
Manual, 04/2012, A5E02486774-05 267
Table A- 40 Sample time and update time for SB
Rejection frequency (Integration Sample time SB update time

time)
400 Hz (2.5 ms) 0.156 ms 0.156 ms
60 Hz (16.6 ms) 1.042 ms 1.042 ms
50 Hz (20 ms) 1.250 ms 1.25 ms
10 Hz (100 ms) 6.250 ms 6.25 ms
A.7.5 Specifications for the analog outputs (SB and SM)
Table A- 41 Specifications for the analog outputs (AQ)
Technical data SB SM
Type Voltage or current Voltage or current
Range 10 V or 0 to 20 mA 10 V or 0 to 20 mA
Resolution Voltage: 12 bits Voltage: 14 bits
Current: 11 bits Current: 13 bits
Full scale range Voltage: -27,648 to 27,648 Voltage: -27,648 to 27,648
(data word) Current: 0 to 27,648 Current: 0 to 27,648
(See note 1)
Accuracy 0.5% / 1% of full scale 0.3% / 0.6% of full scale
(25C / -20 to 60C)
Settling time Voltage: 300 S (R), 750 S (1 uF) Voltage: 300 S (R), 750 S (1 uF)
(95% of new value) Current: 600 S (1 mH), 2 ms (10 mH) Current: 600 S (1 mH), 2 ms (10 mH)
Load impedance Voltage: 1000 Voltage: 1000
Current: 600 Current: 600
Behavior on RUN to STOP Last value or substitute value (default Last value or substitute value (default
value 0) value 0)
Isolation None None
(field side to logic)
Cable length (meters) 100 m, twisted and shielded 100 m, twisted and shielded
Diagnostics Overflow / underflow Overflow / underflow
Short to ground (voltage mode only) Short to ground (voltage mode only)
Wire break (current mode only) Wire break (current mode only)
24 VDC low voltage
Note 1: Refer to the output ranges for voltage and current (Page 269) for the full-scale range.
Easy Book
268 Manual, 04/2012, A5E02486774-05
A.7.6 Output (AQ) measurement ranges for voltage and current
Table A- 42 Analog output representation for voltage
System Voltage Output Range

Decimal Hexadecimal 10 V
32767 7FFF See note 1 Overflow
32512 7F00 See note 1
32511 7EFF 11.76 V Overshoot range
27649 6C01
27648 6C00 10 V Rated range
20736 5100 7.5 V
1 1 361.7 V
0 0 0V
-1 FFFF -361.7 V
-20736 AF00 -7.5 V
-27648 9400 -10 V
-27649 93FF Undershoot range
-32512 8100 -11.76 V
-32513 80FF See note 1 Underflow
-32768 8000 See note 1
1 In an overflow or underflow condition, analog outputs will behave according to the device configuration properties set for
the analog signal module. In the "Reaction to CPU STOP" parameter, select either: Use substitute value or Keep last
value.
Table A- 43 Analog output representation for current
System Current Output Range

Decimal Hexadecimal 0 mA to 20 mA
32767 7FFF See note 1 Overflow
32512 7F00 See note 1
32511 7EFF 23.52 mA Overshoot range
27649 6C01
27648 6C00 20 mA Rated range
20736 5100 15 mA
1 1 723.4 nA
0 0 0 mA
1 In an overflow or underflow condition, analog outputs will behave according to the device configuration properties set for
the analog signal module. In the "Reaction to CPU STOP" parameter, select either: Use substitute value or Keep last
value.
Easy Book
Manual, 04/2012, A5E02486774-05 269
A.8 RTD and Thermocouple modules

The thermocouple (TC) modules (SB 1231 TC and SM 1231 TC) measure the value of
voltage connected to the analog inputs. This value can be either temperature from a TC or
volts.
If voltage, the nominal range full scale value will be decimal 27648.
If temperature, the value will be reported in degrees multiplied by ten (for example, 25.3
degrees will be reported as decimal 253).
The RTD modules (SB 1231 RTD and SM 1231 RTD) measure the value of resistance
connected to the analog inputs. This value can be either temperature or resistance.
If resistance, the nominal range full scale value will be decimal 27648.
If temperature, the value will be reported in degrees multiplied by ten (for example, 25.3
degrees will be reported as decimal 253).
The RTD modules support measurements with 2-wire, 3-wire and 4-wire connections to the
sensor resistor.
Note
The RTD and TC modules report 32767 on any activated channel with no sensor connected.
If open wire detection is also enabled, the module flashes the appropriate red LEDs.
When 500 and 1000 RTD ranges are used with other lower value resistors, the error
may increase to two times the specified error. Best accuracy will be achieved for the 10
RTD ranges if 4 wire connections are used.
The resistance of the connection wires in 2 wire mode will cause an error in the sensor
reading, and therefore accuracy is not guaranteed.
NOTICE
After power is applied, the module performs internal calibration for the analog-to-digital
converter. During this time the module reports a value of 32767 on each channel until valid
data is available on that channel. Your user program may need to allow for this initialization
time. Because the configuration of the module can vary the length of the initialization time,
you should verify the behavior of the module in your configuration. If required, you can
include logic in your user program to accommodate the initialization time of the module.
A.8.1 SB 1231 RTD and SB 1231 TC specifications
Note
To use these TC and RTD SBs, your CPU firmware must be V2.0 or higher.
Easy Book
270 Manual, 04/2012, A5E02486774-05
Technical data SB 1231 AI 1 (16 bit) TC SB 1231 AI 1 (16 bit) RTD

Order number 6ES7 231-5QA30-0XB0 6ES7 231-5PA30-0XB0
Dimensions W x H x D (mm) 38 x 62 x 21 mm 38 x 62 x 21 mm
Current consumption (24 VDC) 20 mA 25 mA
Number of inputs (Page 274) 1 1
Type Floating TC and mV Module-referenced RTD and
Diagnostics Overflow / underflow1, 2 Overflow / underflow1, 2
Wire break3 Wire break3
1 The overflow and underflow diagnostic alarm information will be reported in the analog data values even if the alarms
are disabled in the module configuration.
2 RTD: For resistance ranges, underflow detection is never enabled.
3 When wire break alarm is disabled and an open wire condition exists in the sensor wiring, the module may report
random values.
Table A- 45 Wiring diagrams for SB 1231 TC and RTD
SB 1231 231-5QA30 AI 1 (16 bit) TC SB 1231 231-5PA30 AI 1 (16 bit) RTD
AI0 -
X19 X19
Loop-back unused RTD input

2-wire RTD 3-wire RTD 4-wire RTD
Easy Book
Manual, 04/2012, A5E02486774-05 271
A.8.2 SM 1231 RTD specifications
Technical data SM 1231 AI 4 x RTD x 16 bit SM 1231 AI 8 x RTD x16 bit

Order number 6ES7 231-5PD30-0XB0 6ES7 231-5PF30-0XB0
Dimensions 45 x 100 x 75 70 x 100 x 75
W x H x D (mm)
Current consumption 80 mA 90 mA
(SM Bus)
Current consumption 1 40 mA 40 mA
(24 VDC)
Type Module-referenced RTD and Module-referenced RTD and
Diagnostics Overflow / underflow 2,3 Overflow / underflow 2,3
24 VDC low voltage 2 24 VDC low voltage 2
Wire break (current mode only) 4 Wire break (current mode only) 4
1 20.4 to 28.8 VDC (Class 2, Limited Power, or sensor power from CPU)
2 The overflow, underflow and low voltage diagnostic alarm information will be reported in the analog data values even if
the alarms are disabled in the module configuration.
3 For resistance ranges underflow detection is never enabled.
random values.
Table A- 47 Wiring diagrams for the RTD SMs
SM 1231 RTD 4 (16 bit) SM 1231 RTD 8 (16 bit) References

Loop-back unused
RTD inputs
2-wire RTD
X10 3-wire RTD
X10
X11 4-wire RTD

X11
X12
X12
X13
X13
Easy Book
272 Manual, 04/2012, A5E02486774-05
A.8.3 SM 1231 TC specifications
Model SM 1231 AI4 x 16 bit TC SM 1231 AI8 x 16 bit TC

Order number 6ES7 231-5QD30-0XB0 6ES7 231-5QF30-0XB0
Dimensions 45 x 100 x 75 45 x 100 x 75
W x H x D (mm)
Weight 180 grams xxx grams
Current consumption 80 mA 80 mA
(SM Bus)
Current consumption 1 40 mA 40 mA
(24 VDC)
Type Floating TC and mV Floating TC and mV
Diagnostics Overflow / underflow 2 Overflow / underflow 2
24 VDC low voltage 2 24 VDC low voltage 2
Wire break (current mode only) 3 Wire break (current mode only) 3
1 20.4 to 28.8 VDC (Class 2, Limited Power, or sensor power from CPU)
2 The overflow, underflow and low voltage diagnostic alarm information will be reported in the analog data values even if
the alarms are disabled in the module configuration.
random values.
Easy Book
Manual, 04/2012, A5E02486774-05 273
Table A- 49 Wiring diagrams for the TC SMs
SM 1231 AI 4 TC (16 bit) SM 1231 AI 8 TC (16 bit) Notes

SM 1231 AI 8 TC: For
clarity, TC 2, 3, 4, and 5 are not
shown connected.
X10 X10
X11
X12
X11
X13
A.8.4 Analog input specifications for RTD and TC (SM and SB)
Table A- 50 Analog inputs for the RTD and TC modules (SB and SM)
Technical data RTD and Thermocouple (TC)

Number of inputs 1 (SB), 4 or 8 (SM)
Type RTD: Module referenced RTD and
TC: Floating TC and mV
Range See the RTD/TC type tables:
Nominal range (data word) RTD (Page 276)
Overshoot/undershoot range (data word) TC (Page 275)
Overflow/underflow (data word)
Resolution Temperature 0.1 C / 0.1 F
Resistance / voltage 15 bits plus sign
Maximum withstand voltage 35 V
Noise rejection 85 dB for the selected filter setting
(10 Hz, 50 Hz, 60 Hz or 400 Hz)
Common mode rejection > 120 dB at 120 VAC
Impedance 10 M
Isolation Field side to logic 500 VAC
Easy Book
274 Manual, 04/2012, A5E02486774-05
Technical data RTD and Thermocouple (TC)

Field to 24 VDC SM RTD and SM TC: 500 VAC
(Not applicable for SB RTD and SB TC)
24 VDC to logic SM RTD and SM TC: 500 VAC
(Not applicable for SB RTD and SB TC)
Channel to channel isolation SM RTD: None
(Not applicable for SB RTD)
SM TC: 120 VAC
(Not applicable for SB TC)
Accuracy (25C / -20 to 60C) See the RTD/TC type tables:
RTD (Page 276)
TC (Page 275)
Repeatability 0.05% FS
Maximum sensor dissipation RTD: 0.5 mW
TC: Not applicable
Measuring principle Integrating
Module update time See the RTD/TC filter selection tables:
RTD (Page 278)
TC (Page 276)
Cold junction error RTD: Not applicable
TC: 1.5 C
Cable length (meters) 100 meters to sensor max.
Wire resistance RTD: 20 , 2.7 for 10 RTD max.
TC: 100 max.
A.8.5 Thermocouple type
Table A- 51 Thermocouple type (ranges and accuracy)
Type Under range Nominal Nominal Over range Normal range 3, 4 Normal range 3, 4
minimum1 range low limit range high maximum2 accuracy @ 25C accuracy
limit -20C to 60C
J -210.0C -150.0C 1200.0C 1450.0C 0.3C 0.6C
K -270.0C -200.0C 1372.0C 1622.0C 0.4C 1.0C
T -270.0C -200.0C 400.0C 540.0C 0.5C 1.0C
E -270.0C -200.0C 1000.0C 1200.0C 0.3C 0.6C
R&S -50.0C 100.0C 1768.0C 2019.0C 1.0C 2.5C
N -270.0C -200.0C 1300.0C 1550.0C 1.0C 1.6C
C 0.0C 100.0C 2315.0C 2500.0C 0.7C 2.7C
Easy Book
Manual, 04/2012, A5E02486774-05 275
Type Under range Nominal Nominal Over range Normal range 3, 4 Normal range 3, 4
minimum1 range low limit range high maximum2 accuracy @ 25C accuracy
limit -20C to 60C
TXK / XK(L) -200.0C -150.0C 800.0C 1050.0C 0.6C 1.2C
Voltage -32512 -27648 27648 32511 0.05% 0.1%
-80 mV 80 mV
1 Thermocouple values below the under-range minimum value are reported as -32768.
2 Thermocouple values above the over-range minimum value are reported as 32767.
3 Internal cold junction error is 1.5C for all ranges. This adds to the error in this table. The module requires at least 30
minutes of warmup time to meet this specification.
4 For the 4-channel SM TC only: In the presence of radiated radio frequency of 970 MHz to 990 MHz, the accuracy may
be degraded.
A.8.6 Thermocouple filter selection and update times

For measuring thermocouples, it is recommended that a 100 ms integration time be used.
The use of smaller integration times will increase the repeatability error of the temperature
readings.
Table A- 52 Thermocouple filter selection and update times
Rejection frequency Integration time Update time (seconds)

(Hz) (ms) 1-channel SB 4-channel SM 8-channel SM
10 100 0.301 1.225 2.450
50 20 0.061 0.263 0.525
60 16.67 0.051 0.223 0.445
4001 10 0.031 0.143 0.285
1 To maintain module resolution and accuracy when 400 Hz rejection is selected, the integration time is 10 ms. This
selection also rejects 100 Hz and 200 Hz noise.
A.8.7 RTD sensor type selection table
Table A- 53 Ranges and accuracy for the different sensors supported by the RTD modules
Temperature RTD type Under range Nominal Nominal Over range Normal Normal
coefficient minimum1 range range maximum2 range range
low limit high limit accuracy @ accuracy
25C -20C to
60C
Pt 0.003850 Pt 10 -243.0C -200.0C 850.0C 1000.0C 1.0C 2.0C
ITS90 Pt 50 -243.0C -200.0C 850.0C 1000.0C 0.5C 1.0C
DIN EN 60751 Pt 100
Pt 200
Easy Book
276 Manual, 04/2012, A5E02486774-05
Temperature RTD type Under range Nominal Nominal Over range Normal Normal
coefficient minimum1 range range maximum2 range range
low limit high limit accuracy @ accuracy
25C -20C to
60C
Pt 500
Pt 1000
Pt 0.003902 Pt 100 -243.0C -200.0C 850.0C 1000.0C 0.5C 1.0C
Pt 0.003916 Pt 200 -243.0C -200.0C 850.0C 1000.0C 0.5C 1.0C
Pt 0.003920
Pt 500
Pt 1000
Pt 0.003910 Pt 10 -273.2C -240.0C 1100.0C 1295C 1.0C 2.0C
Pt 50 -273.2C -240.0C 1100.0C 1295C 0.8C 1.6C
Pt 100
Pt 500
Ni 0.006720 Ni 100 -105.0C -60.0C 250.0C 295.0C 0.5C 1.0C
Ni 0.006180 Ni 120
Ni 200
Ni 500
Ni 1000
LG-Ni 0.005000 LG-Ni 1000 -105.0C -60.0C 250.0C 295.0C 0.5C 1.0C
Ni 0.006170 Ni 100 -105.0C -60.0C 180.0C 212.4C 0.5C 1.0C
Cu 0.004270 Cu 10 -240.0C -200.0C 260.0C 312.0C 1.0C 2.0C
Cu 0.004260 Cu 10 -60.0C -50.0C 200.0C 240.0C 1.0C 2.0C
Cu 50 -60.0C -50.0C 200.0C 240.0C 0.6C 1.2C
Cu 100
Cu 0.004280 Cu 10 -240.0C -200.0C 200.0C 240.0C 1.0C 2.0C
Cu 50 -240.0C -200.0C 200.0C 240.0C 0.7C 1.4C
Cu 100
1 RTD values below the under-range minimum value are reported as -32768.
2 RTD values above the over-range maximum value are reported as +32767.
Table A- 54 Resistance
Range Under range Nominal range Nominal range Over range Normal range Normal range
minimum low limit high limit maximum1 accuracy accuracy
@ 25C -20C to 60C
150 n/a 0 (0 ) 27648 (150 ) 176.383 0.05% 0.1%
300 n/a 0 (0 ) 27648 (300 ) 352.767 0.05% 0.1%
600 n/a 0 (0 ) 27648 (600 ) 705.534 0.05% 0.1%
1 Resistance values above the over-range maximum value are reported as 32767.
Easy Book
Manual, 04/2012, A5E02486774-05 277
A.9 Communication interfaces
A.8.8 RTD filter selection and update times
Table A- 55 Filter selection and update times
Noise rejection Integration time Update time (seconds)

frequency (Hz) (ms) 1-channel SB 4-channel SM 8-channel SM
10 100 4-/2-wire: 0.301 4-/2-wire: 1.222 4-/2-wire: 2.445
3-wire: 0.601 3-wire: 2.445 3-wire: 4.845
50 20 4-/2-wire: 0.061 4-/2-wire: 0.262 4-/2-wire: 0.525
3-wire: 0.121 3-wire: .505 3-wire: 1.015
60 16.67 4-/2-wire: 0.051 4-/2-wire: 0.222 4-/2-wire: 0.445
3-wire: 0.101 3-wire: 0.424 3-wire: 0.845
4001 10 4-/2-wire: 0.031 4-/2-wire: 0.142 4-/2-wire: 0.285
3-wire: 0.061 3-wire: 0.264 3-wire: 0.525
1 To maintain module resolution and accuracy when the 400 Hz filter is selected, the integration time is 10 ms. This
selection also rejects 100 Hz and 200 Hz noise.

A.9.1 PROFIBUS master/slave
A.9.1.1 CM 1242-5 PROFIBUS slave
Table A- 56 Technical specifications of the CM 1242-5
Order number 6GK7 242-5DX30-0XE0
Interfaces
Connection to PROFIBUS 9-pin D-sub female connector
Maximum current consumption on the PROFIBUS interface 15 mA at 5 V (only for bus termination) *)
when network components are connected (for example
optical network components)
Easy Book
278 Manual, 04/2012, A5E02486774-05
Permitted ambient conditions
Ambient temperature
during storage -40 C to 70 C
during transportation -40 C to 70 C
during operation with a vertical installation (DIN rail 0 C to 55 C
horizontal)
during operation with a horizontal installation (DIN rail 0 C to 45 C
vertical)
Relative humidity at 25 C during operation, without 95 %
condensation, maximum
Degree of protection IP20
Power supply, current consumption and power loss
Type of power supply DC
Power supply from the backplane bus 5V
Current consumption (typical) 150 mA
Effective power loss (typical) 0.75 W
Dimensions and weights
Width 30 mm
Height 100 mm
Depth 75 mm
Weight
Net weight 115 g
Weight including packaging 152 g
*)The current load of an external consumer connected between VP (pin 6) and DGND (pin 5) must not exceed a maximum
of 15 mA (short-circuit proof) for bus termination.
PROFIBUS interface
Table A- 57 Pinout of the D-sub socket
Pin Description Pin Description

1 - not used - 6 P5V2: +5V power supply

2 - not used - 7 - not used -

3 RxD/TxD-P: Data line B 8 RxD/TxD-N: Data line A

4 RTS 9 - not used -

5 M5V2: Data reference potential Housing Ground connector
(ground DGND)
Easy Book
Manual, 04/2012, A5E02486774-05 279
A.9.1.2 CM 1243-5 PROFIBUS master
Table A- 58 Technical specifications of the CM 1243-5
Order number 6GK7 243-5DX30-0XE0
Interfaces
Connection to PROFIBUS 9-pin D-sub female connector
Maximum current consumption on the PROFIBUS interface 15 mA at 5 V (only for bus termination) *)
when network components are connected (for example
optical network components)
Ambient temperature
horizontal)
vertical)
Power supply / external 24 V
minimum 19.2 V
maximum 28.8 V
Current consumption (typical)
from 24 V DC 100 mA
from the S7-1200 backplane bus 0 mA
Effective power loss (typical)
from 24 V DC 2.4 W
from the S7-1200 backplane bus 0W
Power supply 24 VDC / external
Min. cable cross section min.: 0.14 mm2 (AWG 25)
Max. cable cross section max.: 1.5 mm2 (AWG 15)
Tightening torque of the screw terminals 0.45 Nm (4 lb-in)
Width 30 mm
Height 100 mm
Depth 75 mm
Easy Book
280 Manual, 04/2012, A5E02486774-05
Weight
Net weight 134 g
*)The current load of an external consumer connected between VP (pin 6) and DGND (pin 5) must not exceed a maximum
of 15 mA (short-circuit proof) for bus termination.
PROFIBUS interface
Table A- 59 Pinout of the D-sub socket
Pin Description Pin Description

1 - not used - 6 VP: Power supply +5 V only for bus

terminating resistors;

not for supplying external devices

2 - not used - 7 - not used -

3 RxD/TxD-P: Data line B 8 RxD/TxD-N: Data line A
4 CNTR-P: RTS 9 - not used -
5 DGND: Ground for data signals Housing Ground connector
and VP
PROFIBUS cable
NOTICE
Contacting the shield of the PROFIBUS cable
The shield of the PROFIBUS cable must be contacted.
To do this, strip the insulation from the end of the PROFIBUS cable and connect the shield
to functional earth.
A.9.2 GPRS CP
Note
The GPRS CP is not approved for Maritime applications
The following module does not have Maritime approval:
CP 1242-7 GPRS module
Note
To use these modules, your CPU firmware must be V2.0 or higher.
Easy Book
Manual, 04/2012, A5E02486774-05 281
A.9.2.1 Technical specifications of the CP 1242-7
Table A- 60 Technical specifications of the CP 1242-7
Order number 6GK7 242-7KX30-0XE0
Wireless interface
Antenna connector SMA socket
Nominal impedance 50 ohms
Wireless connection
Maximum transmit power GSM 850, class 4: +33 dBm 2dBm
GSM 900, class 4: +33 dBm 2dBm
GPRS Multislot class 10
device class B
coding scheme 1...4 (GMSK)
SMS Mode outgoing: MO
service: point-to-point
Ambient temperature
horizontal)
vertical)
Power supply / external 24 V
minimum 19.2 V
maximum 28.8 V
Current consumption (typical)
from 24 V DC 100 mA
from the S7-1200 backplane bus 0 mA
Effective power loss (typical)
from 24 V DC 2.4 W
from the S7-1200 backplane bus 0W
Easy Book
282 Manual, 04/2012, A5E02486774-05
24 V DC power supply
Min. cable cross section min.: 0.14 mm2 (AWG 25)
Max. cable cross section max.: 1.5 mm2 (AWG 15)
Tightening torque of the screw terminals 0.45 Nm (4 lb-in)
Width 30 mm
Height 100 mm
Depth 75 mm
Weight
Net weight 133 g
Technical specifications of the ANT794-4MR GSM/GPRS antenna
ANT794-4MR
Order number 6NH9860-1AA00
Mobile wireless networks GSM/GPRS
Frequency ranges 824 to 960 MHz (GSM 850, 900)
1 710 to 1 880 MHz (GSM 1 800)
1 900 to 2 200 MHz (GSM / UMTS)
Characteristics omnidirectional
Antenna gain 0 dB
Impedance 50 ohms
Standing wave ratio (SWR) < 2,0
Max. power 20 W
Polarity linear vertical
Connector SMA
Length of antenna cable 5m
External material Hard PVC, UV-resistant
Operating temperature -40 C through +70 C
Transport/storage temperature -40 C through +70 C
Relative humidity 100 %
External material Hard PVC, UV-resistant
Construction Antenna with 5 m fixed cable and SMA male
connector
Dimensions (D x H) in mm 25 x 193
Easy Book
Manual, 04/2012, A5E02486774-05 283
ANT794-4MR
Weight
Antenna incl. cable 310 g
Fittings 54 g
Installation With supplied bracket
Technical specifications of the flat antenna ANT794-3M
Order number 6NH9870-1AA00

Mobile wireless networks GSM 900 GSM 1800/1900
Frequency ranges 890 - 960 MHz 1710 - 1990 MHz
Standing wave ratio (VSWR) 2:1 1,5:1
Return loss (Tx) 10 dB 14 dB
Antenna gain 0 dB
Impedance 50 ohms
Max. power 10 W
Antenna cable HF cable RG 174 (fixed) with SMA male connector
Cable length 1.2 m
Permitted temperature range -40C to +75C
Flammability UL 94 V2
External material ABS Polylac PA-765, light gray (RAL 7035)
Dimensions (W x L x H) in mm 70.5 x 146.5 x 20.5
Weight 130 g
A.9.3 Teleservice (TS)

The following manuals contain the technical specification for the TS Adapter IE Basic and
the TS Adapter modular:
Industrial Software Engineering Tools
Modular TS Adapter
Industrial Software Engineering Tools
TS Adapter IE Basic
Easy Book
284 Manual, 04/2012, A5E02486774-05
A.9.4 RS485, RS232 and RS422 communication
A.9.4.1 CB 1241 RS485 Specifications
Note
To use this CB, your CPU firmware must be V2.0 or higher.
Technical data CB 1241 RS485

Order number 6ES7 241-1CH30-1XB0
Weight 40 grams
Table A- 62 Transmitter and receiver

Type RS485 (2-wire half-duplex)
Common mode voltage range -7 V to +12 V, 1 second, 3 VRMS continuous
Transmitter differential output voltage 2 V min. at RL = 100
1.5 V min. at RL = 54
Termination and bias 10K to +5 V on B, RS485 Pin 3
10K to GND on A, RS485 Pin 4
Optional termination Short Pin TB to Pin T/RB, effective termination impedance is 127 ,
connects to RS485 Pin 3
Short Pin TA to Pin T/RA, effective termination impedance is 127 ,
connects to RS485 Pin 4
Receiver input impedance 5.4K min. including termination
Receiver threshold/sensitivity +/- 0.2 V min., 60 mV typical hysteresis
Isolation 500 VAC, 1 minute
RS485 signal to chassis ground
RS485 signal to CPU logic common
Cable length, shielded 1000 m max.
Baud rate 300 baud, 600 baud, 1.2 kbits, 2.4 kbits, 4.8 kbits, 9.6 kbits (default),
19.2 kbits, 38.4 kbits, 57.6 kbits, 76.8 kbits, 115.2 kbits,
Parity No parity (default), even, odd, Mark (parity bit always set to 1),
Space (parity bit always set to 0)
Number of stop bits 1 (default), 2
Flow control Not supported
Wait time 0 to 65535 ms
Easy Book
Manual, 04/2012, A5E02486774-05 285
Table A- 63 Power supply

Power loss (dissipation) 1.5 W
Current consumption (SM Bus), max. 50 mA
Current consumption (24 VDC) max. 80 mA
CB 1241 RS485 (6ES7 241-1CH30-1XB0)
Connect "TA" and TB" as shown to terminate the network. (Terminate only the end
devices on the RS485 network.)
Use shielded twisted pair cable and connect the cable shield to ground.
You terminate only the two ends of the RS485 network. The devices in between the two end
devices are not terminated or biased. See the S7-1200 System Manual section on "Biasing
and terminating an RS485 network connector"
Table A- 64 Connector pin locations for CB 1241 RS485 (6ES7 241-1CH30-1XB0)
Pin 9-Pin connector X20

1 RS485 / Logic GND --
2 RS485 / Not Used --
3 RS485 / TxD+ 3 - T/RB
4 RS485 / RTS 1 - RTS
5 RS485 / Logic GND --
6 RS485 / 5V Power --
7 RS485 / Not used --
8 RS485 / TxD- 4 - T/RA
Easy Book
286 Manual, 04/2012, A5E02486774-05
Pin 9-Pin connector X20

9 RS485 / Not Used --
Shell 7-M
A.9.4.2 CM 1241 RS232
Technical data CM 1241 RS232

Weight 150 grams
From +5 VDC 220 mA
Table A- 66 Transmitter and Receiver
Technical data Description

Type RS232 (full-duplex).
Transmitter Common mode voltage range -7 V to +12 V, 1 second, 3 VRMS continuous
(RS485) Transmitter differential output voltage 2 V min. at RL = 100
1.5 V min. at RL = 54
Termination and bias 10K to +5 V on B, PROFIBUS Pin 3
10K to GND on A, PROFIBUS Pin 8
Transmitter Transmitter output voltage +/- 5 V min. at RL = 3K
(RS232) Transmit output voltage +/- 15 VDC max.
Receiver Receiver input impedance RS232: 3 K min.
Receiver threshold/sensitivity RS232: 0.8 V min. low, 2.4 max. high 0.5 V typical hysteresis
Receiver input voltage +/- 30VDC max.
(RS232 only)
Isolation Signal to chassis ground 500 VAC, 1 minute
Signal to CPU logic common
Cable length, shielded (max.) RS232: 10 m.
Baud rate 300 baud, 600 baud, 1.2 kbits, 2.4 kbits, 4.8 kbits, 9.6 kbits
(default), 19.2 kbits, 38.4 kbits, 57.6 kbits, 76.8 kbits, 115.2
kbits,
Flow control (RS232) Not supported
Easy Book
Manual, 04/2012, A5E02486774-05 287
Table A- 67 CM 1241 RS232 connector and wiring
Pin Description Connector Pin Description

(male)
1 DCD Data carrier detect: Input 6 DSR Data set ready: Input

2 RxD Received data from DCE: Input 7 RTS Request to send: Output

3 TxD Transmitted data to DCE: Output 8 CTS Clear to send: Input

4 DTR Data terminal ready: Output 9 RI Ring indicator (not used)

5 GND Logic ground

SHELL Chassis ground
A.9.4.3 CM 1241 RS422/485 Specifications
CM 1241 RS422/485 Specifications
Technical data CM 1241 RS422/485

Order number 6ES7 241-1CH31-0XB0
Dimensions W x H x H (mm) 30 x 100 x 75
Weight 155 grams
Table A- 69 Transmitter and receiver

Type RS422 or RS485, 9-pin sub D female connector
Common mode voltage range -7 V to +12 V, 1 second, 3 VRMS continuous
Transmitter differential output voltage 2 V min. at RL = 100
1.5 V min. at RL = 54
Termination and bias 10K to +5 V on B, PROFIBUS Pin 3
10K to GND on A, PROFIBUS Pin 8
Internal bias options provided, or no internal bias. In all cases,
external termination is required, see Biasing and terminating an
RS485 network connector and Configuring the RS422 and RS485 in
the S7-1200 System Manual
Receiver input impedance 5.4K min. including termination
Receiver threshold/sensitivity +/- 0.2 V min., 60 mV typical hysteresis
Isolation 500 VAC, 1 minute
RS485 signal to chassis ground
RS485 signal to CPU logic common
Cable length, shielded 1000 m max. (baud rate dependent)
Baud rate 300 baud, 600 baud, 1.2 kbits, 2.4 kbits, 4.8 kbits, 9.6 kbits (default),
19.2 kbits, 38.4 kbits, 57.6 kbits, 76.8 kbits, 115.2 kbits,
Easy Book
288 Manual, 04/2012, A5E02486774-05
A.10 Companion products

Flow control XON/XOFF supported for the RS422 mode
Table A- 70 Power supply

From +5 VDC 240 mA
Table A- 71 RS485 or RS422 connector (female)
Pin Description Connector Pin Description

(female)
1 Logic or communication ground 6 PWR +5V with 100 ohm series resistor: Output

2 TxD+ 1 Connected for RS422

7 Not connected
Not used for RS485: Output

3 TxD+ Signal B (RxD/TxD+): Input/Output 8 TXD- Signal A (RxD/TxD-): Input/Output

4 RTS 2 Request to send (TTL level) Output

9 TXD- 1 Connected for RS422
Not used for RS485: Output
5 GND Logic or communication ground SHELL Chassis ground
1 Pins 2 and 9 are only used as transmit signals for RS422.
2 The RTS is a TTL level signal and can be used to control another half duplex device based on this signal. It is active
when you transmit and is inactive all other times.
A.10.1 PM 1207 power module

The PM 1207 is a power supply module for the SIMATIC S7-1200. It provides the following
features:
Input 120/230 VAC, output 24 VDC/2.5A
Order number 6ESP 332-1SH71
For more information about this product and for the product documentation, refer to the
Easy Book
Manual, 04/2012, A5E02486774-05 289
A.10.2 CSM 1277 compact switch module

The CSM1277 is an Industrial Ethernet compact switch module. It can be used to multiply
the Ethernet interface of the S7-1200 to allow simultaneous communication with operator
panels, programming devices, or other controllers. It provides the following features:
4 x RJ45 sockets for connecting to Industrial Ethernet
3 pole plug in terminal strip for connection of the external 24 VDC supply on top
LEDs for diagnostics and status display of Industrial Ethernet ports
Order number 6GK7 277-1AA00-0AA0
For more information about this product and for the product documentation, refer to the
Easy Book
290 Manual, 04/2012, A5E02486774-05
Index
FM approval, 240
maritime approval, 241
AS-i
A add AS-i master CM1243-2 module, 141
add AS-i slave, 142
Access protection AS-i address, 142
CPU, 79 AS-i address properties, 143
Active/passive communication AS-i address, 142, 143
configuring the partners, 131, 145 configuring, 142
connection IDs, 126 AS-i master CM 1243-2, 141
parameters, 128 module features, 141
Ad hoc mode ATEX approval, 240
ISO on TCP, 125
TCP, 125
Add new device B
detect existing hardware, 70
unspecific CPU, 70 Basic panels (HMI), 19
Adding a device Binding to a CPU or memory card, 81
unspecific CPU, 236 Bit logic, 93
Adding inputs or outputs to LAD or FBD Block
instructions, 27 calling another code block, 88
Addressing consistency check, 109
Boolean or bit values, 61 getting started, 88
data block, 60 Types, 50
global memory, 60 Block call
individual inputs (I) or outputs (Q), 61 Basics, 50
memory areas, 60 Block move (MOVE_BLK) instruction, 95
process image, 60 Blocks
temp memory, 60 copying blocks from an online CPU, 231
Analog I/O counters (quantity and memory requirements), 15
conversion to engineering units, 42 data blocks (DBs), 50
input representation (current), 266 events, 52
input representation (voltage), 266 function blocks (FBs), 50
output representation (current), 269 functions (FCs), 50
output representation (voltage), 269 interrupts, 15, 52
step response times for inputs, 267 monitoring, 15
Analog signal board (SB) specifications nesting depth, 15
SB 1231 AI 1x12 bit, 260 number of code blocks, 15
SB 1232 AQ 1x12 bit, 260 number of OBs, 15, 52
Analog signal module specifications organization blocks (OBs), 15, 50, 51, 52
SM 1231 AI 8 x 13 bit, 261 password protection, 80
SM 1232 AQ 2 x 14 bit, 261 size of the user program, 15
SM 1232 AQ 4 x 14 bit, 261 start-up OBs, 52
SM 1234 AI 4 x 13 bit / AQ 2 x 14 bit, 262 timers (quantity and memory requirements), 15
Approvals Boolean or bit values, 61
ATEX approval, 240 Box instruction
CE approval, 239 Getting started, 40
C-Tick approval, 241 Bus connector, 18
cULus approval, 240
Easy Book
Manual, 04/2012, A5E02486774-05 291
Index
C comparison chart, 16
LED indicators, 154
CALCULATE, 41, 98
overview, 18
scaling analogs, 42
RS485, 153
Call structure, 109
Communication interfaces
Capturing values from an online DB, 230
add modules, 72
CB 1241 RS485 specifications, 286
CB 1241 RS485, 286
CE approval, 239
comparison chart of the modules, 16
CEIL (ceiling), 97
RS232 and RS485, 153
Changing settings for STEP 7, 29
Communication module
Clock
Add new device, 71
memory byte, 76
CM 1241 RS422/RS485 specifications, 288
CM 1241
Device configuration, 69
RS422/RS485 specifications, 288
Communication module (CM)
CM 1241 RS232 specifications, 288
add AS-i master CM1243-2 module, 141
Code block
add CM 1243-5 (DP master) module, 138
binding to a CPU or memory card, 81
add modules, 72
calling a block, 88
comparison chart, 16
copy protection, 81
LED indicators, 154
counters (quantity and memory requirements), 15
overview, 18
DB (data block), 87
RS232 and RS485, 153
FB (function block), 86
Communication processor (CP)
FC (function), 86
add modules, 72
interrupts, 15
comparison chart, 16
know-how protection, 80
overview, 18
monitoring, 15
Communications module (CM), USS library, 155
nesting depth, 15
Compare instructions, 95
number of code blocks, 15
Comparing and synchronizing online/offline CPUs, 232
number of OBs, 15
Comparing code blocks, 232
organization blocks (OBs), 15
Comparison chart
size of the user program, 15
CPU models, 14
timers (quantity and memory requirements), 15
HMI devices, 19
Code blocks, 83
modules, 16
Columns and headers in task cards, 30
Configuration
Communication
add modules, 72
active/passive, 128, 131, 145
AS-i, 142
AS-i address, 142
AS-i address, 142
configuration, 128, 131, 145
discover, 70, 236
connection IDs, 126
HSC (high-speed counter), 117
IP address, 77
Industrial Ethernet port, 77
Modbus, 153
IP address, 77
network, 119
network connection, 120
PROFIBUS, 139
number of connections (PROFINET), 122
PROFIBUS address, 139
parameters, 128
PROFIBUS port, 139
PROFIBUS address, 139
PROFINET, 77
PROFINET and PROFIBUS, 121
Startup parameters, 73
PtP, 153
user-defined Web pages, 188
TCON_Param, 128
Configuring parameters
USS, 153
CPU, 73, 77
Communication board (CB)
Ethernet port, 77
add modules, 72
modules, 73, 77
CB 1241 RS485, 286
Easy Book
292 Manual, 04/2012, A5E02486774-05
Index
PROFINET, 77 diagnostics buffer, 233

Connections Ethernet port, 77
configuration, 128 force, 227, 228
connection IDs, 126 Getting started, 35
Ethernet protocols, 144 going online, 223
HMI connection, 44 HMI devices, 19
network connection, 44 HSC configuration, 117
number of connections (PROFINET), 122 IP address, 77
partners, 131, 145 know-how protection, 80
S7 connection, 144 monitoring, 225
types of communication, 121 network connection, 120
types, multi-node connections, 144 number of communication connections, 122
Connections, Web server, 184 online, 225, 233
Consistency check, 109 Operating modes, 48
Constraints operator panel, 28, 49, 224
user-defined Web pages, 187 organization block (OB), 85
Web server, 183 overview, 13
Contact information, 5 password protection, 79
Contacts PROFIBUS, 139
Getting started, 37 PROFIBUS address, 139
Control DB for user-defined Web pages PROFIBUS port, 139
parameter to WWW instruction, 189 PROFINET, 77
CONV (convert), 96 Program execution, 47
Cookie restrictions, standard Web pages, 185 reset to factory settings, 234
Copy protection resetting the start values of a DB, 230
binding to a CPU or memory card, 81 RUN/STOP buttons, 28
Copying blocks from an online CPU, 231 Security levels, 79
Counter instructions, 103 signal board (SB), 18
Counters Startup parameters, 73
HSC (high-speed counter), 112 Startup processing, 73
HSC configuration, 117 step response times for analog inputs, 267
HSC operation, 113 thermal zone, 21
quantity, 15 types of communication, 121
size, 15 unspecific CPU, 70, 236
CPU watch tables, 226
access protection, 79 CPU properties, user-defined Web pages, 188
add modules, 72 Creating a network connection, 120
Add new device, 71 Creating a network connection, 120
analog input representation (voltage), 266 Creating an HMI connection, 44
AS-i address, 142 Creating user-defined Web page DBs, 188
calling a block, 88 Creating user-defined Web pages, 186
capturing values of a DB, 230 Cross-references, 109
communication board (CB), 18 Introduction, 109
comparing and synchronizing blocks, 232 Uses, 109
comparison chart, 14 C-Tick approval, 241
configuring communication to HMI, 119 CTRL_PWM instruction, 105
Configuring parameters, 73, 77 cULus approval, 240
copying blocks from an online CPU, 231 Customer support, 5
CPU 1211C specifications, 245 Cycle time monitoring, 224
CPU 1212C specifications, 245 Cyclic-interrupt OB, 51
CPU 1214C specifications, 245
Easy Book
Manual, 04/2012, A5E02486774-05 293
Index
D E
Data block Electromagnetic compatibility (EMC), 242
capturing values, 230 Environmental
global data block, 60, 87 industrial environments, 241
instance data block, 60 operating conditions, 242
resetting the start values, 230 transport and storage conditions, 242
Data block (DB), 87 Errors
Data handling block (DHB), 88 diagnostic errors, 56
Data log time errors, 55
Data log overview, 106 Ethernet
Data types, 58 ad hoc mode, 125
DTL, 59 connection IDs, 126
Date and Time Long data type, 59 GET, 143
DB (data block), 87 IP address, 77
capturing values, 230 network connection, 120
resetting the start values, 230 number of communication connections, 122
Debugging overview, 124
downloading in RUN mode, 237 PUT, 143
Designing a PLC system, 50, 83 types of communication, 121
Device configuration, 69 Ethernet communication, 119
add modules, 72 Ethernet instructions
Add new device, 71 TRCV_C, 123
AS-i, 142 TSEND_C, 123
AS-i port, 142 Ethernet protocols, 124
Configuring the CPU, 73, 77 multi-node connections, 144
Configuring the modules, 73, 77 Event execution, 52
discover, 70, 236 Events, 233
Ethernet port, 77 organization block (OB), 85
network connection, 120 Expandable instructions, 27
PROFIBUS, 139 Expanding the capabilities of the S7-1200, 16
PROFIBUS port, 139
PROFINET, 77
unplugged modules, 33 F
DeviceStates, 111
Factory settings reset, 234
Diagnostic error interrupt OB, 52
FAQs, 4
Diagnostics
Favorites toolbar, 26
DeviceStates, 111
FB (function block), 86
GET_DIAG, 111
FBD (function block diagram), 90
LED instruction, 110
FC (function), 86
ModuleStates, 111
First scan indicator, 76
status indicator, 76
FLOOR, 97
Diagnostics buffer, 233
FM approval, 240
Digital signal module (SM)
Force, 227, 228
Input and output specifications, 256
I memory, 227, 228
SM 1221, 251
inputs and outputs, 228
SM 1222, 252
peripheral inputs, 227, 228
SM 1223, 254, 255
scan cycle, 228
Discover, 236
Force table
Discover to upload an online CPU, 70
addressing peripheral inputs, 227
Documentation, 4
force, 227
Drag and drop between editors, 30
force operation, 228
DTL data type, 59
Easy Book
294 Manual, 04/2012, A5E02486774-05
Index
Fragment DBs (user-defined Web pages) AS-i port, 142

generating, 188 Configuring the CPU, 73, 77
Frequency, clock bits, 76 Configuring the modules, 73, 77
Function (FC), 86 discover, 70, 236
know-how protection, 80 Ethernet port, 77
Function block (FB) network connection, 120
Initial value, 86 PROFIBUS, 139
Instance data block, 86 PROFIBUS port, 139
know-how protection, 80 PROFINET, 77
Output parameters, 86 Hardware-interrupt OB, 51
High-speed counter
configuration, 117
G HSC, 112
operation, 113
General technical specifications, 239
High-speed counter (HSC)
Generating user-defined Web page DBs, 188
cannot be forced, 229
GET, 143
HMI
configuring the connection, 132
configuring PROFINET communication, 119
Get LED status, 110
Getting started, 43, 45
GET_DIAG, 111
HMI connection, 44
Getting started
addressing, 39
screen, 45
box instruction, 40
HMI connection, 44
code block, 88
HMI devices
contacts, 37
CPU, 35
overview, 19
HMI, 43, 45
Hotline, 5
HMI connection, 44
HSC (high-speed counter)
instructions, 39
configuration, 117
LAD program, 37, 40
operation, 112, 113
Math instruction, 40
HTML pages, user-defined, 186
network, 37
developing, 186
page locations, 188
new PLC, 35
refreshing, 186
PLC tags, 36, 39
HTTP connections, Web server, 184
program block, 88
Project, 35
split editors, 36, 39
I
tags, 36, 39
Global data block, 60, 87 I memory
Global library force, 227
USS, 155 force operation, 228
Global memory, 60 force table, 227
monitor, 225
H monitor LAD, 226
peripheral input addresses (force table), 227
Handling interrupt events
watch table, 225
organization block (OB), 85
I/O
Hardware configuration, 69
addressing, 62
add modules, 72
analog input representation (current), 266
Add new device, 71
analog input representation (voltage), 266
AS-i, 142
analog output representation (current), 269
Easy Book
Manual, 04/2012, A5E02486774-05 295
Index
analog output representation (voltage), 269 MC_Halt, 208

force, 227 MC_Home, 204
force operation, 228 MC_MoveAbsolute, 210
monitoring status in LAD, 226 MC_MoveJog, 216
step response times for analog inputs, 267 MC_MoveRelative, 212
I/O modules MC_MoveVelocity, 214
watch tables, 226 MC_Power, 200
Information resources, 4 MC_Reset, 203
Initial values ModuleStates, 111
capturing and resetting the start values of a DB, 230 monitor, 225, 226
Inputs and outputs move, 95
monitoring, 225 NORM_X (normalize), 97
Inserting a device PID_Compact, 163
unspecific CPU, 70, 236 PUT, 143
Inserting instructions ROUND, 97
drag and drop, 26 SCALE_X (scale), 97
drag and drop between editors, 30 scaling analog values, 42
favorites, 26 status, 225, 226
Installation TRCV_C, 123
mounting dimensions, 21 TRUNC (truncate), 97
signal module (SM), 18 TSEND_C, 123
thermal zone, 21 uninterruptible move (UMOVE_BLK), 95
Instance data block, 60 versions of instructions, 30
Instructions WWW, 189
adding a parameter, 40 Interrupts
adding inputs or outputs to LAD or FBD interrupt latency, 52
instructions, 27 organization block (OB), 85
bit logic, 93 overview, 51
block move (MOVE_BLK), 95 IP address, 77
CALCULATE, 41, 98 configuring the online CPU, 233
CEIL (ceiling), 97 IP router, 77
columns and headers, 30 ISO on TCP
compare, 95 ad hoc mode, 125
CONV (convert), 96 ISO on TCP protocol, 124
counter, 103 ISO-on-TCP
CTRL_PWM), 105 connection configuration, 131
DeviceStates, 111 connection IDs, 126
drag and drop, 26 parameters, 128
drag and drop between editors, 30
expandable instructions, 27
favorites, 26 J
FLOOR, 97
JavaScript restrictions, standard Web pages, 184
force, 227
GET, 143
K
GET_DIAG, 111
Getting started, 39, 40 Know-how protection
HSC (high-speed counter), 112, 113 password protection, 80
inserting, 26
LED status, 110
MC_ChangeDynamic, 221 L
MC_CommandTable, 218
LAD (ladder logic)
Easy Book
296 Manual, 04/2012, A5E02486774-05
Index
monitor, 225, 226 program editor status, 226

overview, 89 Modules
program editor, 226 CB 1241 RS485, 286
status, 225, 226, 227 communication board (CB), 18
Latency, 52 communication module (CM), 18
LED (Get LED status), 110 communication processor (CP), 18
LED indicators comparison chart, 16
communication interface, 154 Configuring parameters, 73, 77
LED instruction, 110 SB 1231 AI 1x12 bit, 260
Linear programming, 83 SB 1232 AQ 1x12 bit, 260
Load memory, 14, 57 signal board (SB), 18
Load memory, user-defined Web pages, 187 signal module (SM), 18
SM 1221, 251
SM 1222, 252
M SM 1223, 254, 255
SM 1231 AI 8 x 13 bit, 261
MAC address, 77
SM 1232 AQ 2 x 14 bit, 261
Manuals, 4
SM 1232 AQ 4 x 14 bit, 261
Maritime approval, 241
SM 1234 AI 4 x 13 bit / AQ 2 x 14 bit, 262
Math, 41, 98
thermal zone, 21
Maximum Web server connections, 184
ModuleStates, 111
MC_ChangeDynamic, 221
Monitor
capturing values of a DB, 230
MC_Halt, 208
resetting the start values of a DB, 230
MC_Home, 204
Monitoring
MC_MoveAbsolute, 210
MC_MoveJog, 216
force table, 227
MC_MoveRelative, 212
LAD status, 225, 226
MC_MoveVelocity, 214
MC_Power, 200
watch table, 225
MC_Reset, 203
Monitoring the program, 108
Memory
Motion control
clock memory, 75
configuring the axis, 194
load memory, 57
homing the axis, 206
peripheral input addresses (force table), 227
MC_ChangeDynamic, 221
retentive memory, 57
system memory, 75
MC_Halt, 208
Temp memory (L), 60
MC_Home, 204
work memory, 57
MC_MoveAbsolute, 210
Memory areas
MC_MoveJog, 216
addressing Boolean or bit values, 61
MC_MoveRelative, 212
data block, 60
MC_MoveVelocity, 214
global memory, 60
MC_Power, 200
immediate access, 60
MC_Reset, 203
process image, 60
overview, 191
temp memory, 60
Mounting
Memory card
dimensions, 21
load memory, 57
thermal zone, 21
Memory usage monitoring, online, 224
Move instruction, 95
Modbus, 153
MRES
MODBUS
operator panel, 28, 49, 224
versions, 30
Multi-node connections
Modifying
Easy Book
Manual, 04/2012, A5E02486774-05 297
Index
connection types, 144 multiple program cycle OBs, 86

Ethernet protocols, 144 priority classes, 51
My Documentation Manager, 4 processing, 85
Output parameters, 86
N
P
Network
getting started, 37, 40 Panels (HMI), 19
network connection, 44 Parameter assignment, 86
Network communication, 119 Passive/active communication
Network connection configuring the partners, 131, 145
configuration, 120 connection IDs, 126
New project parameters, 128
adding an HMI device, 43 Password protection
Getting started, 35 access to the CPU, 79
HMI connection, 44 binding to a CPU or memory card, 81
HMI screen, 45 code block, 80
network connection, 44 copy protection, 81
NORM_X (normalize), 97 CPU, 79
PID
overview, 159
O PID_3STEP, 169
PID_3Step algorithm, 160, 169
Online
PID_Compact, 163
PID_Compact algorithm, 160, 163
comparing and synchronizing, 232
PLC
cycle time monitoring, 224
add modules, 72
discover, 236
calling a block, 88
force, 227
copying blocks from an online CPU, 231
going online, 223
force, 227
IP address, 233
memory usage monitoring, 224
Getting started, 35
monitor, 225
HSC configuration, 117
instructions, 39
RUN/STOP buttons, 28
monitoring, 225
status, 225, 226
overview of the CPU, 13
time of day, 233
tags, 36, 39
watch table, 225, 226
using blocks, 50, 83
Online and diagnostic tools
PLC tags
downloading in RUN mode, 237
OPC, 148
Podcasts, 4
Operating mode, 28, 49, 224
Point-to-point communication, 153
Operator panel, 28, 49, 224
Port number, 124
Operator panels, 19
Portal view, 25
Organization block
Add new device, 71
call, 51
Configuring the CPU, 73, 77
configuring operation, 86
Configuring the Ethernet port, 77
creating, 86
Configuring the modules, 73, 77
function, 51
PROFINET, 77
Priority
Easy Book
298 Manual, 04/2012, A5E02486774-05
Index
priority class, 51 Program card, 57

priority in processing, 52 Program editor
Priority class, 51 capturing values of a DB, 230
Process image monitor, 226
force, 227 resetting the start values of a DB, 230
force operation, 228 status, 226
monitor, 225, 226 Program execution, 47, 50
status, 225, 226, 227 Program information
PROFIBUS In the call structure, 109
add CM 1243-5 (DP master) module, 138 Program structure, 83
add DP slave, 138 Programming
CM 1242-5 (DP slave) module, 134 adding inputs or outputs to LAD or FBD
CM 1243-5 (DP master) module, 134 instructions, 27
GET, 143 binding to a CPU or memory card, 81
master, 133 comparing and synchronizing code blocks, 232
network connection, 120 drag and drop between editors, 30
PROFIBUS address, 139 expandable instructions, 27
PROFIBUS address properties, 140 favorites, 26
PUT, 143 FBD (function block diagram), 90
S7 connection, 144 Getting started, 39
slave, 133 inserting instructions, 26
PROFIBUS address, 139, 140 LAD (ladder), 89
configuring, 139 Linear, 83
PROFINET, 119 PID overview, 159
ad hoc mode, 125 PID_3STEP, 169
connection IDs, 126 PID_3Step algorithm, 160, 169
GET, 143 PID_Compact, 163
IP address, 77 PID_Compact algorithm, 160, 163
network connection, 120 priority class, 51
number of communication connections, 122 SCL (Structured Control Language), 90
overview, 124 Structured, 83
PUT, 143 unplugged modules, 33
S7 connection, 144 unspecific CPU, 70, 236
testing a network, 79 Project
types of communication, 121 access protection, 79
PROFINET interface adding an HMI device, 43
Ethernet address properties, 77 binding to a CPU or memory card, 81
PROFINET RT, 124 comparing and synchronizing, 232
Program Getting started, 35
binding to a CPU or memory card, 81 HMI connection, 44
calling a block, 88 HMI screen, 45
capturing values of a DB, 230 network connection, 44
copying blocks from an online CPU, 231 program, 39
Getting started, 37, 40 protecting a code block, 80
Math instruction, 40 restricting access to a CPU, 79
password protection, 80 tags, 36, 39
priority class, 51 Project view, 25
resetting the start values of a DB, 230 Add new device, 71
sample network, 37, 40 Configuring the CPU parameters, 73, 77
Program block Configuring the Ethernet port, 77
getting started, 88 Configuring the modules, 73, 77
Getting started, 35 Device configuration, 69
Easy Book
Manual, 04/2012, A5E02486774-05 299
Index
PROFINET, 77 add modules, 72

Protection class, 243 Add new device, 71
Protection level AS-i, 142
binding to a CPU or memory card, 81 AS-i address, 142
code block, 80 calling a block, 88
CPU, 79 capturing values of a DB, 230
Protocol communication board (CB), 18
ISO on TCP, 124 communication module (CM), 18
PROFINET RT, 124 communication processor (CP), 18
TCP, 124 compare code blocks, 232
UDP, 124 comparison chart of CPU models, 14
PTO (pulse train output), 105 Configuring the CPU parameters, 73, 77
cannot be forced, 229 Configuring the modules, 73, 77
PtP communication, 153 Device configuration, 69
Pulse train output (PTO), 105 diagnostics buffer, 233
PUT, 143 Ethernet port, 77
configuring the connection, 132 force, 227
PWM force operation, 228
CTRL_PWM instruction, 105 HMI devices, 19
PWM (pulse width modulation) HSC configuration, 117
cannot be forced, 229 IP address, 77
modules, 16
Q monitoring, 225
mounting dimensions, 21
Queuing, 52
organization block (OB), 85
R
overview of the CPU, 13
Rated voltages, 244 password protection, 79
Refreshing user-defined Web pages, 186 PROFIBUS, 139
Relay electrical service life, 245 PROFIBUS address, 139
Replacing modules, 33 PROFIBUS port, 139
Reset to factory settings, 234 PROFINET, 77
Resetting the start values of a DB, 230 Program execution, 47
Retentive memory, 14, 57 resetting the start values of a DB, 230
ROUND, 97 RUN/STOP buttons, 28
Router IP address, 77 signal board (SB), 18
RS232 and RS485 communication modules, 153 signal module (SM), 18
RUN mode, 48, 50 Startup parameters, 73
force operation, 228 thermal zone, 21
operator panel, 28, 49, 224 TS Adapter, 16
Program execution, 47 SCALE_X (scale), 97
toolbar buttons, 28 Scaling analogs, 42
RUN/STOP buttons, 28 Scan cycle
force, 227
S SCL (Structured Control Language)
CEIL (ceiling), 97
S7 communication
CONV (convert), 96
configuring the connection, 132
DeviceStates, 111
S7-1200
FLOOR, 97
access protection, 79
Easy Book
300 Manual, 04/2012, A5E02486774-05
Index
GET_DIAG, 111 analog input representation (current), 266

LED status, 110 analog input representation (voltage), 266
MC_ChangeDynamic, 221 analog output representation (current), 269
MC_CommandTable, 218 analog output representation (voltage), 269
MC_Halt, 208 Device configuration, 69
MC_Home, 204 overview, 18
MC_MoveAbsolute, 210 SM 1221, 251
MC_MoveJog, 216 SM 1222, 252
MC_MoveRelative, 212 SM 1223, 254, 255
MC_MoveVelocity, 214 SM 1231 AI 4 x 13 bit, 261
MC_Power, 200 SM 1232 AQ 2 x 14 bit, 261
MC_Reset, 203 SM 1232 AQ 4 x 14 bit, 261
ModuleStates, 111 SM 1234 AI 4 x 13 bit / AQ 2 x 14 bit, 262
NORM_X (normalize), 97 step response times for analog inputs, 267
overview, 90 SM and SB
PID overview, 159 comparison chart, 16
PID_3STEP, 169 SMS, 147
PID_3Step algorithm, 160, 169 Specifications
PID_Compact, 163 analog input representation (current), 266
PID_Compact algorithm, 160, 163 analog input representation (voltage), 266
program editor, 91 analog output representation (current), 269
round, 97 analog output representation (voltage), 269
SCALE_X (scale), 97 ATEX approval, 240
truncate, 97 CB 1241 RS485, 286
Var section, 91 CE approval, 239
Security communication module CM 1241 RS232, 288
access protection, 79 CPU 1211C, 245
binding to a CPU or memory card, 81 CPU 1212C, 245
copy protection, 81 CPU 1214C, 245
CPU, 79 C-Tick approval, 241
know-how protectionf for a code block, 80 cULus approval, 240
Send parameters configuration, 131, 145 Digital inputs and outputs (SM), 256
Serial communication, 153 electromagnetic compatibility (EMC), 242
Service and support, 5 environmental conditions, 242
Settings, 29 FM approval, 240
Siemens technical support, 5 general technical specifications, 239
Signal board (SB) industrial environments, 241
add modules, 72 maritime approval, 241
analog output representation (current), 269 protection, 243
analog output representation (voltage), 269 rated voltages, 244
Device configuration, 69 relay electrical service life, 245
input representation (current), 266 SB 1231 AI 1x12 bit, 260
input representation (voltage), 266 SB 1232 AQ 1x12 bit, 260
overview, 18 SM 1221 signal module, 251
SB 1231 AI 1x12 bit, 260 SM 1222 signal module, 252
SB 1232 AQ 1x12 bit, 260 SM 1223 signal module, 254, 255
step response times for analog inputs, 267 SM 1231 AI 4 x 13 bit, 261
Signal board (SM) SM 1232 AQ 2 x 14 bit, 261
Add new device, 71 SM 1232 AQ 4 x 14 bit, 261
Signal module (SM) SM 1234 AI 4 x 13 bit / AQ 2 x 14 bit, 262
add modules, 72 step response times for inputs, 267
Add new device, 71 Split editors
Easy Book
Manual, 04/2012, A5E02486774-05 301
Index
Getting started, 36, 39 operator panel, 28, 49, 224

Standard Web pages, 181 toolbar buttons, 28
cookie restrictions, 185 Structured programming, 83
JavaScript restrictions, 184 Subnet mask, 77
STARTUP mode Support, 5
force operation, 228 System memory byte, 76
Program execution, 47
Startup OB, 51
Startup parameters, 73 T
Status
Tags
LED indicators (communication interface), 154
force, 227
STEP 7
add modules, 72
monitor, 225
Add new device, 71
status, 225
adding inputs or outputs to a LAD or FBD
Task cards
instruction, 27
columns and headers, 30
AS-i, 142
TCON
configuration, 131
changing the settings, 29
connection IDs, 126
connection parameters, 128
TCON_Param, 128
Configuring the modules, 73, 77
TCP
ad hoc mode, 125
connection configuration, 131
diagnostics buffer, 233
connection IDs, 126
parameters, 128
Ethernet port, 77
protocol, 124
expandable inputs or outputs, 27
TCP/IP communication, 119, 124
favorites, 26
Technical specifications, 239
force, 227
Technical support, 5
Technological objects
HSC configuration, 117
inserting instructions, 26
Telecontrol, 150
monitoring, 225, 226
TeleService via GPRS, 149, 150
Temp memory (L), 60
Testing the program, 108
password protection, 80
Thermal zone, 21
Portal view, 25
TIA Portal
priority class (OB), 51
Add new device, 71
PROFIBUS, 139
PROFIBUS port, 139
Configuring the modules, 77
PROFINET, 77
Project view, 25
Portal view, 25
PROFINET, 77
RUN/STOP buttons, 28
Project view, 25
unplugged modules, 33
Time of day
STEP 7 programming
configuring the online CPU, 233
user-defined Web pages, 189
Time-error interrupt OB, 52
STEP 7 web pages, 4
Timers
STOP mode, 48
quantity, 15
size, 15
Easy Book
302 Manual, 04/2012, A5E02486774-05
Index
TRCV favorites, 26
ad hoc mode, 125 inserting instructions, 26
connection IDs, 126 password protection, 80
TRCV_C User-defined Web pages, 181, 186
ad hoc mode, 125 configuring, 188
configuration, 131 creating with HTML editor, 186
connection IDs, 126 enabling with WWW instruction, 189
connection parameters, 128 generating program blocks, 188
TRCV_C instruction, 123 load memory constraints, 187
TRUNC (truncate), 97 programming in STEP 7, 189
TS Adapter, 16 refreshing, 186
TSAP, 124 USS protocol, 153
TSAP (transport service access points), 133 USS protocol library, 155
TSEND
connection IDs, 126
TSEND_C V
configuration, 131
Versions of instructions, 30
connection IDs, 126
Visualization
HMI devices, 19
TSEND_C instruction, 123
TURCV
configuration, 131
W
TUSEND Watch table
configuration, 131 force, 108
parameters, 128 monitor, 225
Watch tables, 226
Web pages
U STEP 7, 4
Web pages, user-defined, 186
UDP
Web server, 181
connection configuration, 131
constraints, 183
parameters, 128
maximum HTTP connections, 184
UDP protocol, 124
Work memory, 14, 57
Uninterruptible move (UMOVE_BLK) instruction, 95
WWW, 189
Unplugged modules, 33
Unspecific CPU, 70, 236
Updating user-defined Web pages, 186
Upload
discover, 236
Uploading
user program, 231
User interface
Portal view, 25
Project view, 25
User program
adding inputs or outputs to LAD or FBD
instructions, 27
binding to a CPU or memory card, 81
expandable instructions, 27
Easy Book
Manual, 04/2012, A5E02486774-05 303
Index
Easy Book
304 Manual, 04/2012, A5E02486774-05

SIMATIC S7-1200 Manual PDF

Uploaded by

Copyright:

Available Formats

SIMATIC S7-1200 Manual PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SIMATIC S7-1200 Manual PDF

Uploaded by

Copyright:

Available Formats

 Easy Book ___________________

Introducing the powerful and

Siemens AG Order number: 6ES7298-8FA30-8BQ0 Copyright Siemens AG 2012.

The S7-1200 compact controller includes:

This manual describes the following products:

Documentation and information

Service and support

3.10 Create an HMI screen ................................................................................................................. 45

8 PID is easy ............................................................................................................................................ 159

11.6 Using the force table ..................................................................................................................227

A.8.5 Thermocouple type ................................................................................................................... 275

Table 1- 1 Comparing the CPU models

Feature CPU 1211C CPU 1212C CPU 1214C CPU 1215C

Table 1- 2 Blocks, timers and counters supported by S7-1200

1.2 Expansion capability of the CPU

Communication module (CM), communcation processor (CP), or TS Adapter

Table 1- 3 Digital signal modules and signal boards

Type Input only Output only Combination In/Out

digital SM 8 x 24VDC In 8 x 24VDC Out 8 x 24VDC In / 8 x 24VDC Out

16 x 24VDC In 16 x 24VDC Out 16 x 24VDC In / 16 x 24VDC Out

Table 1- 4 Analog signal modules and signal boards

Type Input only Output only Combination In/Out

analog SM 4 x Analog In 2 x Analog Out 4 x Analog In / 2 x Analog Out

Table 1- 5 Communication interfaces

Module Type Description

Communication board (CB) RS485 Half-duplex

TeleService TS Adapter IE Basic1 Connection to CPU

Table 1- 6 Other boards

1.3 S7-1200 modules

Table 1- 7 S7-1200 expansion modules

Type of module Description

Communication modules (CMs) Status LEDs

1.4 Basic HMI panels

Basic HMI Panel Description Technical data

Basic HMI Panel Description Technical data

KTP 1000 Basic PN

1.5 Mounting dimensions and clearance requirements

Table 1- 8 Mounting dimensions (mm)

S7-1200 Devices Width A (mm) Width B (mm) Width C (mm)

Side view Vertical installation

1.6 New features

New modules for the S7-1200

2.1 Easy to insert instructions into your user program

2.2 Easy access to your favorite instructions from a toolbar

You can easily customize the

2.3 Easy to add inputs or outputs to LAD and FBD instructions

Some of the instructions allow you to create additional inputs or outputs.

2.4 Expandable instructions

2.5 Easy to change the operating mode of the CPU

2.6 Easy to modify the appearance and configuration of STEP 7

You can select a variety of settings,

2.7 Project and global libraries for easy access

Each project has a project library for storing the objects to be

2.8 Easy to select a version of an instruction

To change the version of the instruction, select the

2.9 Easy to drag and drop between editors

To help you perform tasks quickly and easily,

To display two editors at one time, use the

2.10 Changing the call type for a DB

Easy Book ___________________