STEP 7 Basic V13 2 enUS

Readme 1
Installation 2
SIMATIC
STEP 7 Basic V13 SP2
System Manual
Printout of the online help
03/2017
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
indicates that minor personal injury can result if proper precautions are not taken.
NOTICE
indicates that property damage can result if proper precautions are not taken.
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 Copyright © Siemens AG 2017.

Division Digital Factory Ⓟ 03/2017 Subject to change All rights reserved
Postfach 48 48
90026 NÜRNBERG
GERMANY
Table of contents
1 Readme........................................................................................................................................................5
1.1 Improvements in V13 SP2.......................................................................................................5
1.1.1 Improvements in STEP 7.........................................................................................................5
1.1.1.1 General information..................................................................................................................5
1.1.1.2 Improvements in Update 9.......................................................................................................6
1.1.1.8 Improvements in Update 3.....................................................................................................13
1.1.2 Improvements in WinCC........................................................................................................16
1.1.2.1 General information................................................................................................................16
1.2 Notes on the TIA Portal..........................................................................................................34
1.2.1 General notes.........................................................................................................................34
1.2.2 Notes on libraries...................................................................................................................36
1.2.3 Notes on memory cards.........................................................................................................37
1.2.4 Notes on the hardware configuration.....................................................................................38
1.2.5 Notes on instructions..............................................................................................................38
1.2.6 Notes on online and diagnostics............................................................................................39
1.3 STEP 7 Basic.........................................................................................................................40
1.3.1 Security information...............................................................................................................40
1.3.2 Notes on use..........................................................................................................................41
1.3.3 Editing devices and networks.................................................................................................42
1.3.3.1 General information on devices and networks.......................................................................42
1.3.3.2 Use of modules on the S7-1200.............................................................................................43
1.3.3.3 Replacing ET 200S positioning modules...............................................................................44
1.3.3.4 CP 343-2 on SIMATIC S7 Embedded Controller EC31-RTX.................................................44
1.3.3.5 F-CM AS-i Safety ST for ET 200SP.......................................................................................44
1.3.3.6 S7 routing via IE/PB Link.......................................................................................................45
1.3.3.7 Notes on online and diagnostics............................................................................................45
1.3.4 Programming a PLC...............................................................................................................46
1.3.4.1 General notes on PLC programming.....................................................................................46
1.3.4.2 Compatibility of PLC programs from V12 SP1 or V13...........................................................48

System Manual, 03/2017 3
Table of contents
1.3.4.3 Instructions.............................................................................................................................51
1.3.4.4 Testing the user program.......................................................................................................54
1.3.5 Inter Project Engineering (IPE)..............................................................................................55
1.3.5.1 Notes on IPE..........................................................................................................................55
1.3.6 Technological functions..........................................................................................................56
1.3.6.1 Notes on technological functions (S7-1200)..........................................................................56
1.4 WinCC Basic..........................................................................................................................58
1.4.1 Security information...............................................................................................................58
1.4.2 News......................................................................................................................................60
1.4.3 Notes on WinCC V13 SP2.....................................................................................................60
1.4.4 Notes on WinCC V13 SP1.....................................................................................................62
1.4.4.1 System-wide functions...........................................................................................................62
1.4.4.2 Compiling and loading............................................................................................................62
1.4.4.3 Notes on use..........................................................................................................................65
1.4.4.4 Migration................................................................................................................................68
1.4.4.5 Engineering System...............................................................................................................71
1.4.4.6 Runtime..................................................................................................................................85
1.4.4.7 HMI devices...........................................................................................................................88
2 Installation..................................................................................................................................................93
2.1 Notes on the installation.........................................................................................................93
2.2 System requirements for installation......................................................................................94
2.2.1 Notes on licenses...................................................................................................................94
2.2.2 Notes on the system requirements........................................................................................95
2.2.3 System requirements STEP 7 Basic......................................................................................96
2.2.3.1 Licensing of STEP 7...............................................................................................................96
2.2.3.2 Handling licenses and license keys.......................................................................................98
2.2.3.3 Software and hardware requirements STEP 7.....................................................................100
2.2.4 System requirement for WinCC Basic..................................................................................104
2.2.4.1 Software and hardware requirements..................................................................................104
2.2.4.2 Parallel installation...............................................................................................................108
2.2.4.3 Licenses and Powerpacks...................................................................................................108
2.3 Installation log......................................................................................................................113
2.4 Starting installation...............................................................................................................114
2.5 Checking availability of updates and support packages and installing them.......................116
2.6 Displaying the installed software..........................................................................................119
2.7 Modifying or updating installed products..............................................................................120
2.8 Repairing installed products.................................................................................................121
2.9 Starting to uninstall...............................................................................................................123
2.10 Installing and uninstalling the migration tool........................................................................125
2.10.1 System requirements...........................................................................................................125
2.10.2 Installing the migration tool..................................................................................................125
2.10.3 Uninstalling the migration tool..............................................................................................126
Index.........................................................................................................................................................127

4 System Manual, 03/2017
Readme 1
1.1 Improvements in V13 SP2
1.1.1 Improvements in STEP 7
1.1.1.1 General information

The information in this readme file supersedes statements made in other documents.
Read the following notes carefully because they include important information for installation
and use. Read these notes prior to installation.
What's new in TIA Portal V13 SP2

The TIA Portal V13 SP2 can be installed on the operating system Windows 10 (64-bit).
Working with the TIA Portal

Stability when working with the TIA Portal has been improved, partly based on the feedback
from returned crash reports.
Instructions "FILL_BLK" and "MUX"

In rare cases, the instructions "FILL_BLK" and "MUX" returned incorrect online values during
runtime. This behavior was changed.
The behavior occurred when, in an optimized block more than 8 tags of the same data type
with a width of 64 bits or more than 32 tags of the same data type with a width of 32 bits were
declared in the section TEMP, and it used input parameter "Count" for "FILL_BLK" or input
parameter "k" for "MUX".
GRAPH programming editor

The runtime behavior of permanent operations with multiple coils and flipflops in GRAPH
(S7-300, S7-400) were corrected.
Parameter type "Block_DB" for entry of the instance DB

In LAD and FBD, you cannot enter the instance DB of an instruction using an input of the data
type "BLOCK_DB". This behavior has been made uniform for all CPU families and all block
types.

Readme
Instructions "READ_BIG", "READ_LITTLE", "WRITE_BIG" and "WRITE_LITTLE"

When using actual parameters with an ARRAY index variable for the SRC_ARRAY and
DEST_VARIABLE, the correct index is now calculated.
Working with negated numbers

The negation of a number with the subsequent subtraction or addition of the same number
now results in the correct result (LAD, FBD and SCL).
Example:
#var1 := - #var1;
#result := #var2 + #var1;
Status display
The status display (e.g. update required) in the title bar of editors is correctly updated.
Copy scenarios for program blocks

Other corrections relating to direct copying and pasting of program blocks or elements between
PLCs. The resolution of the tags when copying in the described objects is made exclusively
with the symbolic names.
1.1.1.2 Improvements in Update 9

Update 9 contains the following improvements and changes:

Adding additional dimensions to an ARRAY within a DB

It is now possible to add additional dimensions to an ARRAY in a global DB, even if the ARRAY
is already used in an SCL block.
Copy scenarios for program blocks

Correct about direct copying and pasting of program blocks or element between PLCs.
The resolution of the tags when copying in the described objects is made exclusively with the
symbolic names.

Readme


"Apply snapshot values as start values" function for fail-safe blocks

The "Apply snapshot values as start values" function no longer affects fail-safe blocks. The
consistency of the fail-safe offline blocks is thus not impaired.
FB with a tag of data type DB_ANY in the "Temp" section

Loading a function block with a tag of data type DB_ANY that was declared in the "Temp"
section no longer results in a firmware exception error.
Possibility of configuring the "IE/AS-i link PN IO" module

The "IE/AS-i link PN IO" module can now only be configured using a GSDML file (Hardware
catalog > Other field devices > PROFINET IO > Gateway > SIEMENS AG > IE/AS-i Link PN
IO).
In existing configurations in which the module from the folder "Network components >
Gateways > IE/AS-i Link > IE/AS-i Link PN IO" of the hardware catalog was used, a
corresponding alarm is output during compilation of the configuration as of Update 8.
Installation of hardware support packages

The installation of HSPs in ASU can be started without restrictions.
Memory requirements for the installation of the TIA Portal or an update

You can find information on this topic on the FAQ page (https://support.industry.siemens.com/
cs/de/en/ps/faq) under the following entry ID: 109482855

Umlauts in setpoints of the STRING data type

Changing setpoints with the STRING data type in online mode is possible also when they have
a higher ASCII character value than ~, e.g. ä, ö, ü.

Readme
Online access
The scanning of accessible devices has been stabilized.
ANY pointers in CPUs of the S7-1500 series

The assignment of a structured Input/Output/InOut to a local ANY pointer is permitted in FCs
also in SCL.


Security information
In addition to the Readme for STEP 7 V13 SP1, please not the following security measures:
Devices connected to an enterprise network or directly to the internet must be appropriately
protected against unauthorized access, e.g. by use of firewalls and network segmentation. For
more information about industrial security, please visithttp://www.siemens.com/
industrialsecurity (http://www.industry.siemens.com/topics/global/en/industrial-security/
Pages/default.aspx)
Know-how protected blocks in libraries:

The use of know-how protected blocks from a library with nested PLC data types does not
require entry of a password for compilation.




Readme
Working with Graph

Fulfilled step enabling conditions in transitions are executed reliably, even in the case of a
transition from STOP to RUN.
Configuration of AS-Interface with ET 200SP CPU

The operation of the CM AS-i Master ST module in an ET 200SP configuration with an ET
200SP CPU instead of an interface module (IM) has been released. The minimum
requirements of the following firmware and software versions apply:
● CM AS-i Master ST with FW V1.1
● ET 200SP CPU with FW V1.8 (CPU 1510SP-1 PN, CPU 1510SP F-1 PN, CPU 1512SP-1
PN, CPU 1512SP F-1 PN, Open Controller CPU 1515SP PC)
● Configuration with STEP 7 V13 SP1 Update 4
Operation of the F-CM AS-i Safety ST module in an ET 200SP configuration with an ET 200SP
F-CPU instead of an interface module (IM) also requires the new version V3.0 of the HSP
0070, i.e. the following minimum requirements apply in addition to those specified above:
● Configuration with STEP 7 Safety V13 SP1 Update 4
● In addition: New HSP 0070 version V3.0 required
Automation Software Update (ASU)

The notification of new updates for software/support packages has been corrected.
Port Configuration Tool (PCT tool)

The start behavior of the PCT tool from STEP 7 has been improved.
Cross-reference list
The call of the "Go to" function in the cross-reference list for instance data blocks has been
corrected.
Monitoring tags
Controlling absolute DB addresses (e.g. %DB1.DBX0.0) in the block is now supported.
Migration of LAD networks

The representation of LAD networks after migration has been improved.


Readme

Instructions "TCON, TSEND_C, TRCV_C" (S7-1200 and S7-1500)

In addition to the causes listed in the online help, the value W#16#80C4 from STATUS
(temporary communications error) can have the following causes:
● The connection cannot be established because firewalls for the required ports situated on
the connection path are not enabled.
Instruction "D_ACT_DP: Enable/disable DP slaves" (S7-1500)

● Contrary to the description in the online help, the following applies to the disabling / enabling
of the IE/PB Link PN IO type of gateway:
You cannot disable/enable an IE/PB Link PN IO type of gateway using the instruction
"D_ACT_DP". If you nevertheless use D_ACT_DP on the said gateway, the CPU returns
the value W#16#8093 "No hardware object that can be activated or deactivated belongs
to the address specified in LADDR."
● As a supplement to the description in the online help, the following applies to firmware as
of version V1.8 of the S7-1500 CPUs:
You can use the "D_ACT_DP" instruction to disable/enable DP slaves that are connected
to an IE/PB Link PN IO type of gateway.
Instruction "GET_IM_Data: Read identification and maintenance data" (S7-1500)

Contrary to the information in the online help, the error code "80C3", rather than the error code
"807F", is shown. The description for the error code "807F" provided in the information system
is also valid for the "80C3" error code.
Keyboard operation in comparing SCL blocks

In the Comparison editor, the following keyboard operations are now also available for SCL
blocks:
Function Keyboard shortcut

Navigate to the next point of use of the selected oper‐ <Ctrl+Shift+G>
and
Navigate to the previous point of use of the selected <Ctrl+Shift+F>
operand

Readme
Parameter transfer
Note the following for parameter transfer between blocks with optimized access and blocks
with standard access:
Note
Parameter transfer between blocks with optimized access and blocks with standard access
If, during a block call, structures are transferred to the called block as in/out parameters (InOut),
they are transferred by default as pointers (Call by reference).
However, this does not apply if the two blocks have different optimization settings: If one of
the blocks has the property "Optimized access" and the other block has the property "Standard
access", all parameters are always transferred as copies (Call by value).
This means that the called block always works with the copied values. During the processing
of the block, these values may possibly be changed and copied back to the original operand
after the processing of the block call.
This can lead to problems if the original operands are changed by asynchronous processes,
such as by HMI access or interrupt OBs. If the copies are copied back again to the original
operands after the block processing, the changes made asynchronously to the original
operands are overwritten.
You can avoid this by setting the same access type for both blocks or by allowing the
asynchronous access to be written only to a separate memory area and then copying this area
synchronously when the time is appropriate.
Know-how protection
The know-how protection has to be removed for blocks that were protected against
unauthorized access by an older version of the TIA Portal and now have to be opened or
changed. This can subsequently be reset.
Testing with program status

The monitoring of code blocks (STL, LAD, FBD, SCL) with a CPU from the S7-400 series has
been improved and no longer results in STOP.
Note in each case that only interconnected opened networks can be monitored. A closed
network interrupts the monitoring.
The shortcut menu commands "Modify > Monitor from here" and "Modify > Monitor selection"
will not be available until firmware of S7-400 is updated.
Programming of NTP servers with the system function block "T_CONFIG"

For a CPU of the S7-1500 module with the firmware version V1.8, up to four NTP servers can
be configured program controlled with the "T_CONFIG" instruction for time synchronization
via the Ethernet / PROFINET interface. For this purpose, the address data of the NTP servers
is stored in the system data type (SDT) "IF_CONF_NTP".
This requires that time synchronization is enabled via NTP in STEP 7 and at least one NTP
server is configured. The NTP server or servers configured in STEP 7 do not have to be

Readme
identical with the NTP servers that were programmed in the SDT "IF_CONF_NTP". The NTP
servers stored in the SDT "IF_CONF_NTP" overwrite the data in the STEP 7 configured NTP
server during runtime.
Die firmware version V1.8 for S7-1500 CPUs is available with STEP 7 V13.0 SP1 Update 4.
New modules
The following new modules are supported:
Article number Description FW version

6AV7 882-0Axxx-xxxx IPC277E, TOUCH 7", 800 x 480
6AV7 882-0Axxx-xxxx IPC277E, TOUCH 7", 480 x 800,
portrait
6AV7 882-0Bxxx-xxxx IPC277E, TOUCH 9", 800 x 480
6AV7 882-0Bxxx-xxxx IPC277E, TOUCH 9", 480 x 800,
portrait
6AV7 882-0Cxxx-xxxx IPC277E, TOUCH 12", 1280 x
800
6AV7 882-0Cxxx-xxxx IPC277E, TOUCH 12", 800 x
1280, portrait
6AV7 882-0Dxxx-xxxx IPC277E, TOUCH 15", 1366 x
768
6AV7 882-0Dxxx-xxxx IPC277E, TOUCH 15", 768 x
1366, portrait
6AV7 882-0Exxx-xxxx IPC277E, TOUCH 19", 1366 x
768
6AV7 882-0Exxx-xxxx IPC277E, TOUCH 19", 768 x
1366, portrait
6ES7 647-8Bxxx-xxxx IPC227E
6ES7 510-1DJ01-0AB0 CPU 1510SP-1 PN V 1.8
6ES7 510-1SJ01-0AB0 CPU 1510SP F-1 PN V 1.8
6ES7 511-1AK01-0AB0 CPU 1511-1 PN V 1.8
6ES7 511-1CK00-0AB0 CPU 1511C-1 PN V 1.8
6ES7 511-1FK01-0AB0 CPU 1511F-1 PN V 1.8
6ES7 512-1CK00-0AB0 CPU 1512C-1 PN V 1.8
6ES7 512-1DK01-0AB0 CPU 1512SP-1 PN V 1.8
6ES7 512-1SK01-0AB0 CPU 1512SP F-1 PN V 1.8
6ES7 513-1AL01-0AB0 CPU 1513-1 PN V 1.8
6ES7 513-1FL01-0AB0 CPU 1513F-1 PN V 1.8
6ES7 515-2AM01-0AB0 CPU1515-2 PN V 1.8
6ES7 515-2FM01-0AB0 CPU1515F-2 PN V 1.8
6ES7 516-3AN01-0AB0 CPU 1516-3 PN/DP V 1.8
6ES7 516-3FN01-0AB0 CPU 1516F-3 PN/DP V 1.8
6ES7 672-7AC00-0YA0 CPU 1507S V 1.8

Readme
The following modules are supported with new firmware:
Article number Description FW version

6ES7 510-1DJ00-0AB0 CPU 1510SP-1 PN V 1.8
6ES7 510-1SJ00-0AB0 CPU 1510SP F-1 PN V 1.8
6ES7 511-1AK00-0AB0 CPU 1511-1 PN V 1.8
6ES7 511-1FK00-0AB0 CPU 1511F-1 PN V 1.8
6ES7 512-1DK00-0AB0 CPU 1512SP-1 PN V 1.8
6ES7 512-1SK00-0AB0 CPU 1512SP F-1 PN V 1.8
6ES7 513-1AL00-0AB0 CPU 1513-1 PN V 1.8
6ES7 513-1FL00-0AB0 CPU 1513F-1 PN V 1.8
6ES7 515-2AM00-0AB0 CPU 1515-2 PN V 1.8
6ES7 515-2FM00-0AB0 CPU 1515F-2 PN V 1.8
6ES7 516-3AN00-0AB0 CPU 1516-3 PN/DP V 1.8
6ES7 516-3FN00-0AB0 CPU 1516F-3 PN/DP V 1.8
6ES7 517-3AP00-0AB0 CPU 1517-3 PN/DP V 1.8
6ES7 517-3FP00-0AB0 CPU 1517F-3 PN/DP V 1.8
6ES7 518-4AP00-0AB0 CPU 1518-4 PN/DP V 1.8
6ES7 518-4FP00-0AB0 CPU 1518F-4 PN/DP V 1.8
6ES7 672-5AC00-0YA0 CPU 1505S V 1.8
6ES7 677-2AAxx-0xB0 CPU 1515SP PC V 1.8
6ES7 677-2AAxx-0xx0 CPU 1515SP PC + HMI V 1.8

Runtime performance of loops in SCL

The runtime performance during loop cycles, particularly for small CPUs (<S7-1516 with FW
1.6 / 1.7) and additionally a small number of instructions within the loop, has been improved.
Assignment list
Tags that are assigned to a non-existent hardware address are displayed with a yellow
background in the assignment list.
Program information
Load memory utilization in the program information is updated when the know-how protection
is activated.
Program information
For the controller 315-2 PN/DP CPU (V2.6 or V3.2), it is also possible to select a memory card
size of 256 KB and 1 MB.

Readme
Task card instructions - Open User Communication

In online mode, the connection of devices when data is sent and received is displayed correctly.
Task card instructions - Open User Communication

If the connection type ISO-on-TCP is selected in the properties of the instruction TSEND_C,
the TSAP addressing is no longer reset to the default value on going offline.

TIA Portal Openness

If the name of a user-defined data type (UDT) contains a period, it is now possible to import
this date type into the TIA Portal using Openness.

Changes to Openness schema

The "EN" and "ENO" attributes were replaced by the shared BooleanAttribute with
Attribute Name = "ENENO".
This change has an effect on the following elements:
● InstructionRef
● CallRef
● Part
It is always written under "InstructionRef". It is only written under "Part" and "CallRef" in case
of ExportFlag WithReadonly with attribute Informative = "true".
When you create import files with your Openness application that use the InstructionRef
element, you must adapt the changes manually.
Upgrading projects from V13 to V13 SP1

Upgrading projects to V13 SP1 has been improved.
Instructions
The behavior of the following library elements ("Instructions" task card) has been corrected:
● Technology / TIO_IOLink_OUT (V1.0)
● Technology / TIO_DQ (V1.0)

Readme
● Technology / TIO_DI (V1.0)

● Technology / TIO_SYNC (V1.0)
● Communication / Modbus_Master (V2.0/V2.1)
● Communication / Modbus_Slave (V2.0/V2.1)
● Communication / Send_P2P (V2.0/V2.1)
● Communication / USS_Port_Scan (V2.0/V2.1)
● Extended instructions / Get_IM_Data (V1.1)
● Extended instructions / PE_WOL (V1.1)
Note
Automatic correction of instructions
TIA Portal corrects the listed instructions automatically during the first compilation and
download to device. The user is informed about the changes through a dialog. The changes
take effect by confirming the dialog with "Yes".
The uses of the corrected instructions can then be found, for example, by using the program
information/dependency structure and adapted as needed.
Structured tags in STL

Components of structured tags with leading "_" (e.g., #Motor._Start) can also be used in STL.
Working with SCL

Stability when working with SCL has been improved.
Compatibility mode V12 SP1

Monitoring of blocks in V12 SP1 compatibility mode is possible without restrictions (created in
V13).


Stability when working with the TIA Portal has been improved.
Open Controller with IO Link and PCT

An IO Link module configured to an Open Controller can also be reached with the PCT tool.

Readme
Status of the online connection in the project tree

The status of the online connection is shown in the project tree, even for grouped CPUs.
Security improvements in the communication from the engineering system to the controller
and the password memory in the project.
For details, see Siemens Security Advisory-315836 (http://www.siemens.com/innovation/pool/
de/forschungsfelder/siemens_security_advisory_ssa-315836.pdf)
1.1.2 Improvements in WinCC
1.1.2.1 General information

What's new in TIA Portal V13 SP2

The TIA Portal V13 SP2 can be installed on the operating system Windows 10 (64-bit).

Migration
When configuring styles at the faceplate type, the property "Use style/design" has to be in the
interface before the property "Style item design" is used in the interface of the faceplate.
Otherwise, the style at the instance of the faceplate is lost when the configuration is updated.
Compiling and loading

The routines for delta compilation have been improved.
Improvements in Runtime Professional

The input in transparent I/O fields has been improved.
Switching languages has been improved in faceplates and in text lists used in alarm texts.
Absolute addressing of the "Counter" and "Timer" data types during communication with an
S7-1500 or an S7-1200 has been improved.

Readme

Faceplates for Runtime Advanced

When configuring styles at the faceplate type, the property "Use style/design" has to be in the
interface before the property "Style item design" is used in the interface of the faceplate.
Otherwise, the style at the instance of the faceplate is lost when the configuration is updated.
Screens and screen objects in Runtime

The functionality of the system diagnostics view and the system diagnostics window has been
improved.
Alarms
The display of diagnostics alarms for GRAPH 7 has been improved
Notes on the Sm@rtServer

The display of Service pages in the integrated Web server has been improved.
Notes on Comfort Panels

Internal memory management has been optimized for the following devices:
● TP700 / KP700
● TP900 / KP900
● TP1200 / KP1200
● TP1500 / KP1500
● TP1900
● TP2200

Screens and screen objects in Runtime Professional

The faceplate functionality has been enhanced.
The display of controller alarms in the alarm view has been improved.
Alarms
The display of diagnostics alarms for GRAPH 7 has been improved

Readme
Libraries
The behavior of global libraries during an update has been improved.
Communication for Runtime Advanced and Panels

Communication via OPC UA has been improved.
Notes on Basic Panels

The trend view has been improved with respect to zoom behavior via function keys.
The behavior of the system functions "ActivateScreen" and "SetTag" has been improved with
respect to use in a function list at an event.

New images for Comfort Panels are made available with the update. Display of texts in Runtime
are improved with these images.
Notes on Runtime Advanced

The information on download to a target device on which a different version of Runtime
Advanced is installed has been improved.
Notes on Runtime Professional

The license check of the USB dongle has been improved with regard to additional connected
USB devices.
Stability on deactivation of Runtime has been improved.
Notes on the Web client

Performance has been improved.

Screens and screen objects in Runtime

The display and operability of screen objects in Runtime has been improved.
● Slide-in screens
● System diagnostics view
The error tolerance has been increased for the PLC code display.

Readme
Alarms
The name of the tag is always displayed correctly in system event 190008, which provides
information on the limit violation of a tag.
Communication
Communication has been improved for Runtime Professional
● With SIMATIC S7-1200
● With SIMATIC S7-1500
● Between OPC server and OPC client

Behavior when a password is changed has been improved in Runtime
The behavior of the alarm view has been improved.
The export and import of recipes has been improved.
The bit-based evaluation of text lists and graphic lists has been improved.
The behavior of the trend view has been improved.

Behavior when a password is changed has been improved in Runtime
Sporadically occurring system time jumps are suppressed.
The "ActivateCleanScreen" system function is always performed correctly.
The restart behavior when a USB stick is used has been improved.
Notes on multi-touch devices

The operability of multi-touch devices has been improved.
Notes on the integrated Web server of Runtime Advanced and Panels

Access to an SD card via the "File Browse" service page is always possible.
Notes on WinCC DataMonitor

The display of Excel workbooks has been improved.


Readme
Screen objects in the Engineering System

The displays of graphics in the graphic view has been improved for Runtime Professional.
Alarms
The import of alarms has been improved.
Tags
The display of changes to HMI-relevant PLC tags in the graphic view has been improved for
Runtime Professional.
Logs
The routines for logging alarms in a database have been improved for Runtime Advanced.
Recipes
The processing of text lists has been improved.
The assignment of numbers on creation of a recipe data record in Runtime have been improved
for Runtime Advanced.
System functions and user-defined functions

The system functions GetPLCMode, SetPLCMode and SetPLCDateTime cannot be used in
user-defined functions.
The behavior of system functions on event "Boundary reached" has been improved.
Compiling, downloading and simulating

The behavior during compilation of projects has been improved for:
● Projects with a very large number of texts
● Hierarchical VB functions
● Alarm sequence reports on line printers
For Runtime Professional, the restart behavior of Runtime after the addition of project
languages has been improved.
On-screen keyboard
The behavior of the on-screen keyboard has been improved.

Readme
Screens and screen objects in Runtime Advanced

● PDF view
● Button
The call behavior of slide-in and pop-up windows has been improved.

Runtime behavior has been improved with respect to quick screen changes.
In faceplates, the behavior of animations when the "Bool" data type is used has been improved.
● Graphic view

The display and operability of screen objects in Runtime have been improved
● PDF view
● Button

● Alarm view
● Trend view
The behavior of the "ScreenObjectCursorDown" system function has been improved.
Notes on multi-touch devices

The display and operability of the alarm view in Runtime have been improved:
Sm@rtClient
The behavior of the Sm@rtClient application (smartclient.exe) in the event of a change to the
size of the application has been improved.

Readme

Upgrading projects
The upgrade of projects to V13 SP1 has been improved.

The evaluation of the z-sequence has been improved for faceplates in Runtime Professional.
Alarms
The copying of message texts containing tags has been improved.
Tags
The configuration of dynamic limits for tags has been improved.
Reports
The configuration options of the text field have been improved with respect to the text
orientation in reports.
Communication
Communication with an S7-1500 has been improved for Comfort Panel, KTP Mobile Panel
and Runtime Advanced.
Time synchronization between the OPC UA server and clients has been improved for Comfort
Panel, KTP Mobile Panel and Runtime Advanced.
Communication between OPC server and OPC client has been improved for Runtime
Professional.
Mobile Panel configuration

The shortcut menus and cross-references have been improved in the editors for configuring
the Mobile Panel.
Adapting the size of objects

The routines for automatically adjusting the sizes of text objects have been improved.

The routines for delta compilations have been improved in terms of connections, tags and
cycles.

Readme
Screens and screen objects in Runtime Advanced

● I/O field, graphic I/O field, symbolic I/O field
● HTML browser
● Trend view
● Alarm view
● PDF view
● Recipe view
● Slider
The display of the mouse cursor on a touch screen has been improved.

The behavior on screen change has been improved.
The animation of the visibility has been improved for faceplates in Runtime Professional.
The display and operability of screen objects in Runtime have been improved:
● PLC code display

The behavior of the Enter key in the Control Panel has been improved.
● I/O field, graphic I/O field, symbolic I/O field
● HTML browser
● Trend view
● Alarm view
● PDF view
● Recipe view
● Slider

Readme
System memory card

The restart behavior has been improved for the following Comfort Panels:
● TP700 Comfort
● KP700 Comfort
● TP900 Comfort
● KP900 Comfort
● TP1200 Comfort
● KP1200 Comfort
● KP1500 Comfort
● TP1500 Comfort
● TP1900 Comfort
● TP2200 Comfort
WebNavigator
The routines for displaying faceplates on the WebNavigator client have been improved.
SIMATIC Logon
For Comfort Panels and Runtime Advanced, the duration of the logon procedure via SIMATIC
Logon has been reduced even when a large number of Windows user groups is configured.
Note
SIMATIC Logon patch
The described improvement only takes effect if the SIMATIC Logon patch is installed.

Configuration of the Mobile Panel 2nd Generation

The configuration of the Mobile Panel 2nd Generation is now completely possible. The devices
are released separately. The following devices are available now:
● KTP700 Mobile
● KTP700F Mobile
● KTP900 Mobile
● KTP900F Mobile

Readme

New images for Basic Panels

With this update, new images are available for the following devices with device version 13.0.1:
● KTP400 PN
● KTP700 PN
● KTP900 PN
● All Comfort Panels
With this update, new images are available for the following devices with device version 13.0.0:
● KTP1200
To update the operating system of the target device, follow these steps:
1. Install the update on the Engineering System.
2. Open the project in the Engineering System.
3. Select the "Update operating system" command from the menu under "Online > HMI Device
maintenance" on the configuration PC in WinCC.
The "SIMATIC ProSave [OS-Update]" dialog opens. The path to the image is preset.
4. If required, you can select a different path for the image that you want to transfer to the HMI
device.
5. Click "Update OS".
6. Compile the device.
7. Load the project to the device.
Upgrading projects
Upgrading projects to V13 SP1 has been improved with respect to the PLC code display.
Sorting in the project navigation

The routines for sorting in online mode have been improved in the project navigation.
The routines for sorting in subdirectories of screens have been improved in the overview
window.
Selection dialog for tags and objects

If you change the column widths for tags and objects in the selection dialog, these widths will
be used for all columns when you next open the dialog.

Readme

The display and configuration of screen objects has been improved:
● Grouped objects
● Faceplates: Improvements in the configuration of languages.
● Screen windows: Improvements in the interaction of borders and scroll bars
Screen objects on Basic Panels

● I/O field
● Trend view
● Alarm view
● Recipe view
Screen objects in Runtime

● Arrows and arrowheads
● HTML browser
● Alarm view
● Pop-up screen
● Recipe view
● Symbolic IO field
Screen objects in Runtime Professional

● PLC code display
Tags
The routines for sorting in the tag tables have been improved.
Behavior with respect to start value and substitute value has been improved for the following
PLC data types:
● Date
● Time_Of_Day
● LTime_Of_Day

Readme
Alarms
The interconnection of multiplex tags has been improved for analog alarms.
System functions and scripts

The behavior of the following system functions has been improved:
● ActivateScreen on event "Boundary reached"
● SetBitWhileKeyPressed pressed at objects with operator authorization
● SetLanguage
● Selection of parameters for SetTag functions
Reports
The layout of the I/O field has been improved.

A delta compilation and download is possible even if a simulation is running.
The simulation of HMI devices has been improved.
Device replacement
The routines for scaling pop-up screens and automatically adjusting the sizes of objects have
been improved.
Logs
The stability of logs has been improved on Comfort Panels.
Communication
When using a VPN tunnel at a customer plant, it is possible to use a temporary, alternative IP
address.
Process Historian
No unnecessary entries are shown in the Windows event display.
Sm@rtServer
With the Sm@rtClient application, connection data can be saved even when the password is
to be saved.
With access via Internet Explorer, the character @ can be entered in an IO field, for example.
The behavior for identifying active access from a client has been improved.

Readme
The functionality of Pack&Go has been improved.
Data exchange with Inter Project Engineering

Data exchange between the controller and the HMI device has been improved with respect to:
● Upgrading projects
● Initialization of device proxy
● Access to communication processors
● Updating a device proxy from a STEP 7 V5.x project

Internal memory management has been optimized for Basic Panels 2nd Generation. In addition,
the counting method of the used recipe tags has been optimized.

The touch screen's sensitivity has been improved on the following devices.
● TP700
● TP900
● TP1200
The behavior of the on-screen keyboard in the Control Panel has been improved on the
Comfort Panel.
Notes on IPCs
The routines for switching the device type have been improved for IPCs.
Mobile Panels 277F IWLAN
Mobile Panels 277F IWLAN are released for use with CPUs of the type S7-1500F with WinCC
V13 SP1 Update 4.
If this connection is not established automatically after the Panel is switched on or after a fail-
safe connection to a CPU S7-1500F is canceled, a STOP/RUN transition needs to be
performed on the CPU.
Affected MLFBs:
● 6AV6645-0EB01-0AX1
● 6AV6645-0EC01-0AX1
● 6AV6645-0EF01-0AX1
● 6AV6645-0GB01-0AX1

Readme
● 6AV6645-0GC01-0AX1
● 6AV6645-0GF01-0AX1
Use of the Mobile Panel 277F IWLAN in the industrial environment

To avoid communication problems between the HMI device and access point, please observe
the following:
IWLAN planning: Wireless connection between the HMI device and access point.
● Wireless field planning needs to be carried out. Radar influences need to be taken into
consideration for channels requiring Dynamic Frequency Selection (DFS).
● Avoid radio frequency interference from other devices, such as hand-held devices with
Bluetooth or WLAN function.
● For adjacent access points, use data channels that are separated by at least one wireless
channel (e.g. 36 and 44 rather than 36 and 40).
● Do not place several access points in the immediately vicinity of one another. Spacing of
at least 5 m is recommended.
● For the Mobile Panel 277F IWLAN, use the "Software retry number" 15 instead of the default
value 3.
Use the "rapid roaming" function with iPCF-MC
● Always use iPCF or iPCF-MC (rapid roaming) for PROFIsafe communication.
● Use the same SSID for all access points.
● The "Background scan" should be switched off on the HMI device (“Background scan
interval” for the HMI device = 1 (default value)).
● Use the same "Management channel" and different, non-overlapping "Data channels" for
all access points.
● Configure the "PN-IO cycle time" greater than the "iPCF scan cycle time".
● Observe the set timeout during the PROFIsafe parameter assignment.

Migrating and updating projects

The migration and updating of projects to version V13 SP1 has been improved.
Screens
The following behavior has been optimized in the "Screens" editor:
● Renaming layers
● Copying and pasting animations, for example

Readme
● Drag-and-drop of objects.
● Pasting text via the clipboard, e.g. into a text box

The display and configuration of screen objects has been improved
● Faceplates
● I/O field
● Grouped objects
Dynamization and animations

The names of screen windows are also dynamized correctly with direct connections.
Tags
Tags with limits for which structure tags are configured are compiled correctly.
When multiplexing symbolic addresses, user data types cannot be used as multiplex tags.

The behavior of the following system functions has been improved:
● ExportDataRecords
● ImportDataRecords
● OpenfileBrowser
Access to a tag takes place correctly even if the name of the tag contains a period.
Tags with the data type UDINT can also be set correctly in VB functions.
The use of SINUMERIK system functions in VB functions has been improved.
Exporting/importing tags
Multiplex tags are also supported during export.
Text lists
Copying texts via the clipboard into a text list has been improved.
GMP-compliant configuration
The behavior when messages are acknowledged has been improved in projects with GMP-
compliant configuration.

Readme
Communication
Communication between OPC server and OPC client has been improved for Runtime
Advanced.

● Trend view
● Recipe view on 2nd generation Basic Panels
● Slider
● Symbolic I/O field
● Objects in templates
2nd generation Basic Panels

● Trend view
● Buttons with transparent graphics
● Buttons with multiple-line entries from text lists.
● Recipe view
Device settings with respect to sound are retained even after a restart.
Data exchange with Inter Project Engineering

Data exchange between the controller and the HMI device has been improved with respect to:
● Alarms
● Initialization of device proxy
● Access to data of a non-initialized device proxy
● Access to faulty data of a device proxy
● Support of the PLC ET 200SP CPU 1512SP
Restrictions regarding direct keys

On replacement of the HMI device or the device version, existing configuration for direct keys
is removed and needs to be reconfigured after the device replacement.


Readme
Security improvements
Security improvements regarding communication of SIMATIC HMI Panels or HMI software to
the controller and password saving in the project
For details, see Advisory: http://www.siemens.com/innovation/pool/de/forschungsfelder/
siemens_security_advisory_ssa-487246.pdf
You can find information on security patches and security updates on the Internet: Industrial
Security News
Migrating and updating projects

The migration and updating of projects to version V13 SP1 has been improved.

The display and configuration of screen objects has been improved
● I/O field
● Grouped objects
Importing tags
The routines for importing tags have been improved.
Limitations for PLC user data types with arrays in faceplates

PLC user data types cannot be used as a property type in the properties of faceplate types
when the PLC user data types include arrays that use user constants as array limits.
Animations
The animation of a property is executed correctly in Runtime Professional even if the
expression includes line breaks.

● Arrows and arrowheads
● I/O field
● Graphic I/O field
● Alarm view
● Recipe view
● Status/force

Readme
Alarms
AlarmS and AlarmD alarms can be acknowledged on the HMI device even if they have been
deleted in the alarm buffer of the PLC.

It is possible to save a recipe data record with the "RecipeViewSaveDataRecord" function even
when the system function is configured on an F-key.
Communication
The communication between OPC server and OPC client has been improved for Runtime
Advanced.
Sm@rtServer
Java version 1.8 is supported for HMI devices that are only available in device version 12.
The behavior of the server when accessing multiple HMI devices has been optimized.
The "Save as" command is available in the shortcut menu in the file browser of the integrated
Web server.

Upgrading projects
The upgrading of a project to V13 SP1 has been improved in connection with faceplates and
the character sets used within them.
Tags
In Runtime Professional, the tag prefix can also be used without restriction for screen windows
after a tag has been renamed.

The maximum nesting depth of scripts has been increased for Comfort Panel and Runtime
Advanced.
In Runtime Professional, routines for interpreting the Boolean parameters have been modified
for system functions which use a Boolean parameter.
In Runtime Professional, screen loading times have been improved in connection with VB
scripts.

Readme
1.2 Notes on the TIA Portal

The display of screen objects has been improved for Comfort Panel and Runtime Advanced.
● Recipe view: Display of the Value column
Communication
Communication with the following controllers has been improved:
● SIMATIC S7 300/400
● PROFIsafe connection between PLC 416F (with CP) and Mobile Panel 277F IWLAN V2
● PROFIsafe connection between PLC 317-2F PN/DP and Mobile Panel 277F 8" IWLAN
(RFID)
Formatting an SD card
SD cards are recognized by a panel, even after formatting of the card.
SINUMERIK PCU
The SINUMERIK PCU devices can be used without restriction, even if WinCC V13 SP1 was
installed as a delta to WinCC V13.
SIMOTION
The interplay of SIMOTION with HMI tags has been improved.
1.2.1 General notes

Display of Asian characters in the TIA Portal

Due to a change in behavior in Microsoft Windows, it may occur that texts are not displayed
correctly in the TIA Portal when a Chinese TIA Portal is installed on another Asian operating
system (e.g. Korean). To view the texts in TIA Portal correctly, open the Windows Control
Panel and select "English" under "Language for non-Unicode programs". Note, however, that
this may cause display problems in other programs.

Readme
Installing new .Net versions or .Net service packs

● Close the TIA Portal before installing a new .Net version or a new .Net service pack on your
programming device/PC.
● Restart the TIA Portal only after successful installation of the new .Net version or the
new .Net service pack.
Notes on handling
● If a project in the list of projects last used is located on a network drive that is not connected,
you may experience delays when opening the "Project" menu.
● When you insert a CPU, you may need to wait for some time if the project editor is open at
the same time. This generally takes longer when you insert the first CPU in a newly created
project. To be able to continue working more quickly, you should close the project editor
before inserting a CPU.
● The alarm "Application is not responding" may appear in Windows 7 with functions that
take a long time to run (loading the CPU for example). If this occurs, wait until the function
has correctly finished.
● If you have installed a Microsoft mouse with IntelliPoint, you may find that it superimposes
components over the buttons of the title bar. If this is the case, uninstall the IntelliPoint
software from Microsoft.
● Enabling the "Virtual Desktop" options with NVIDIA graphics cards can cause problems. In
this case, disable the "nView virtual desktop manager" of your NVIDIA graphics driver.
Using the TIA Portal via a remote desktop

In principle, it is possible to use the TIA Portal via a remote desktop connection. During
configuration, you should, however, avoid disconnecting the connection to the desktop client.
In rare cases, this can lead to the software user interface being blocked.
If you experience this blockage, follow these steps on the desktop client.
1. Open the Windows Task-Manager and close the "rdpclip.exe" process.
2. Type in "rdpclip.exe" in the command prompt to restart the process.
Note that the current content of the clipboard will be lost. You can, however, then continue
configuration as usual. To be on the safe side, you should restart the TIA Portal at the next
opportunity.
Migration of projects with the TIA Portal

After the migration of hardware configurations and program blocks from earlier automation
solutions, first check the functionality of the migrated project before you use it in productive
operation.

Readme
Working with automatically synchronized network drives

Automatic synchronization after a network interruption can result in current (local) project data
being stored as a "backup" on the network drive through user interactions. This could cause
outdated project data to be loaded from the network drive when opening the project. For this
reason, we do not recommend that you store TIA Portal projects on synchronized network
drives.
If, however, you do work on synchronized drives, you can continue working locally in the event
of a network interruption. In this case, you must always ensure that the TIA Portal application
is closed while data is synchronized. The synchronization itself must be implemented in such
a way that the current (local) project data replaces the project data on the network drive.
Entry of decimal places

With certain Windows language settings, it may occur that the entry of values with a comma
as decimal place is not recognized (entering "1,23" leads to an error). Instead, use the
international format ("1.23").
Information on the TIA Portal in online support

Overview of the most important technical information and solutions for the TIA Portal in the
Siemens Industry online support.
Internet link: TIA Portal in Siemens Industry online support (www.siemens.com/industry/
onlinesupport/tiaportal)
All information on service and support in the Siemens Industry online support:
Internet link: Service and support in Siemens Industry online support (http://
support.automation.siemens.com/WW/llisapi.dll?aktprim=99&lang=en&referer=%2fWW
%2f&func=cslib.csinfo2&siteid=csius&extranet=standard&viewreg=WW&groupid=4000002)
Here, you can also subscribe to the newsletter that provides you with latest information relating
to your products.
Starting the TIA Portal

When you start the TIA Portal, Windows attempts to update the Certificate Revocation List
(CRL) of "windowsupdate.com".
If no Internet access is available and there are multiple DNS servers, a timeout may occur and
delay the start of the TIA Portal.
1.2.2 Notes on libraries
Contents
Information that could not be included in the online help and important information about
product characteristics.

Readme
Comparing library elements

If master copies and types have the same name, the corresponding objects in the project are
overwritten when the action "Copy" is used. Please note that this takes place without a prompt.
The same behavior occurs when the name of the master copy is different to the name of the
type, but an object within the master copy has the same name as the type.
1.2.3 Notes on memory cards
Contents
Notes on SIMATIC memory cards

The SIMATIC memory cards have been formatted and set up by Siemens for use with S7-1200
and S7-1500 modules. This format must not be overwritten; otherwise, the card will no longer
be accepted by the modules. Formatting with Windows tools is therefore not permitted.
Behavior in case of open force job

Note that an active force job is retained even after you have loaded a new project to the
SIMATIC memory card. This means you should first delete the active force job before you
remove a SIMATIC memory card from the CPU and before you overwrite the card in the PC
with a new project. If you use a SIMATIC memory card with unknown content, you should
format the SIMATIC memory card before the next download.
Access protection for memory cards in USB card readers

By improving the security mechanisms for online access and engineering of S7-1500 CPUs,
the data storage on memory cards has been changed. For this reason, this version of STEP
7 cannot evaluate the passwords of the configured protection level when reading project data
from memory cards that is accessed via a USB card reader. The changed behavior affects the
memory cards for CPUs of the S7-1200/1500 series. Therefore, use physical safeguards to
protect critical project data on memory cards for these devices.
Note
This restriction is not related to online access to devices or the know-how protection of program
blocks.

Readme
1.2.4 Notes on the hardware configuration
Content
Subnet addressing for CP 1613 and CP 1623

CP 1613 and CP 1623 are communication modules with microprocessor. To ensure secure
management of communication links, these are processed on the module. The protocol stack
in your PC is used for diagnostic purposes (SNMP, DCP). To allow both protocol stacks (i.e.
CP 1613/23 Firmware and CP 1613/23 NDIS access) access to the same partners, is
recommended to place both stacks of a module in the same subnet.
Editing a device IP address

Do not use the address range from 192.168.x.241 to 192.168.x.250 when editing a device IP
address. If necessary, this address range is automatically assigned by the system to a
programming device. Depending on the subnet mask, this applies also for all network classes.
Drivers for the CP 5512 communications processor

The drivers for the CP 5512 are no longer included in this software version. If you want to use
the CP 5512, the following needs to be installed prior to the installation of this software:
http://support.automation.siemens.com/WW/view/78453460 (http://
support.automation.siemens.com/WW/view/en/78453460)
Please note that the CP 5512 can be used with a maximum of Windows 7 32-bit. As of Windows
8 or with 64-bit operating systems, the CP 5512 is not compatible.
Note
Since 2009, the functional successor the USB 2.0 module CP 5711 has been available.
1.2.5 Notes on instructions
Contents

Readme
Instructions not valid for all CPU firmware versions

The firmware version of your CPU determines the following:
● Whether a specific instruction is available for this CPU:
– If you select CPU 1211C DC/DC/DC with firmware version V1.0, for example, the
extended instruction "T_COMBINE" will not be available to you. It is grayed out in the
"Instructions" task card.
– However, if you select CPU 1211C DC/DC/DC with firmware version V3.0, the extended
instruction "T_COMBINE" will be available to you in versions V1.1 and V1.2.
● Which versions of the instruction are available. You can select the different versions in the
"Version" column of the "Instructions" task card.
1.2.6 Notes on online and diagnostics
Contents
Display of interfaces via online access

If the Ethernet interfaces for online access are not displayed sporadically, install hotfix
KB2588507 (for Microsoft Windows) from the Microsoft Support website.
Internet link: http://support.microsoft.com/kb/2588507 (http://support.microsoft.com/kb/
2588507/en-us)
Online operation in hibernate mode

We recommend that you do not use the two options "Hibernate" and "Sleep" in online operation;
if you do, communication problems could occur. If necessary, adapt the computer's energy
options.

Readme
1.3 STEP 7 Basic
1.3 STEP 7 Basic
1.3.1 Security information
Upgrades and updates

Siemens provides products and solutions with industrial security functions that support the
secure operation of plants, solutions, machines, equipment and/or networks. They are
important components in a holistic industrial security concept. With this in mind, Siemens’
products and solutions undergo continuous development. Siemens recommends strongly that
you regularly check for product updates.
For the secure operation of Siemens products and solutions, it is necessary to take suitable
preventive action (e.g. cell protection concept) and integrate each component into a holistic,
state-of-the-art industrial security concept. Third-party products that may be in use should also
be considered. For more information about industrial security, visit
http://www.siemens.com/industrialsecurity (http://www.industry.siemens.com/topics/global/
en/industrial-security/Pages/Default.aspx)
To stay informed about product updates as they occur, sign up for a product-specific
newsletter. For more information, visit
http://support.automation.siemens.com (https://support.industry.siemens.com/cs/de/en/)
Network settings
The following tables show the network settings of each product you need to analyze the
network security and to configure external firewalls:
STEP 7 Basic
Name Port number Transport pro‐ Direction Function Description
tocol
ALM 4410* TCP Inbound/out‐ License serv‐ This service provides the complete function‐
bound ice ality for software licenses and is used by
both the Automation License Manager as
well as all license-related software products.
RFC 1006 102 TCP Outbound S7 communi‐ Communication to the S7 controller via
cation Ethernet/PROFINET for programming and
diagnostic purposes.
DCP --- Ethernet Outbound PROFINET The DCP protocol (Discovery and Basic
Configuration Protocol) is used by PROFI‐
NET and provides the basic functionality for
locating and configuring PROFINET devi‐
ces.
SNMP 161 UDP Outbound PROFINET The SNMP client functionality is used by
STEP 7 to read status information from
PROFINET devices.
* Default port that can be changed by user configuration

Readme
1.3 STEP 7 Basic
WinCC ES Basic (without simulation)

tocol
ALM 4410* TCP Inbound/out‐ License serv‐ This service provides the complete function‐
bound ice ality for software licenses and is used by
both the Automation License Manager as
well as all license-related software products.
HMI Load 1033 TCP Outbound HMI Load (RT This service is used to transmit images and
Basic) configuration data to Basic Panels.
Simulation RT Basic
tocol
HMI Load 1033 TCP Inbound HMI Load (RT This service is used to transmit images and
Basic) configuration data to Basic Panels.
Ethernet/ 44818 TCP Outbound Ethernet/IP The Ethernet/IP protocol is used for connec‐
IP channel tions to Allen Bradley PLCs.
2222 UDP Inbound Ethernet/IP The Ethernet/IP protocol is used for connec‐
channel tions to Allen Bradley PLCs.
Modbus 502 TCP Outbound Modbus TCP The Modbus TCP protocol is used for con‐
TCP channel nections to Schneider PLCs.
RFC 1006 102 TCP Outbound S7 channel Communication to the S7 controller via
Ethernet/PROFINET
Mitsubishi 5002 TCP Outbound Mitsubishi MC The Mitsubishi protocol is used for connec‐
MC channel tions to Mitsubishi PLCs.
1.3.2 Notes on use
Content
Online operation
The simultaneous online operation of STEP 7 V5.5 or earlier and STEP 7 Basic V13 has not
been approved.
Simultaneous online connections on an S7-1200 CPU

It is not possible to establish an online connection from multiple instances of the TIA Portal
simultaneously to the same S7-1200 CPU.

Readme
1.3 STEP 7 Basic
Removing/inserting the memory card

After removing or inserting a memory card, always perform a memory reset on the CPU in
order to restore the CPU to a functional condition.
Removing and inserting Ethernet modules

If Ethernet modules are removed and re-inserted during operation, you must boot the PC;
otherwise, the "Accessible devices" functionality in STEP 7 or NCM PC will not display all
devices. While the PC boots, Ethernet modules must be activated.
Loading project data with TIA Portal V12 and V13 (S7-1200)
If you load the project data of an S7-1200 CPU with the TIA Portal V13, you can no longer use
TIA Portal V12 to access this data. To do this, first restore the factory settings of the CPU.
Read the additional information on this in the online help under "How to reset a CPU to factory
settings".
Using project data of distributed IO-Link master modules from TIA Portal V12 in V13
The following procedure applies if you are using distributed IO-Link master modules in TIA
Portal V12 that are not GSD devices and were configured with PCT: To continue using your
project data from TIA Portal V12.0 in TIA Portal V13.0, you have to export them to PCT before
you upgrade the project. After the upgrade, you must import the project data once again using
the PCT.
Compatibility
The device configuration and program of an S7-1200 CPU must always be configured with the
same STEP 7 version. Usually, the TIA Portal makes sure that no version conflicts occur by
outputting appropriate notifications during loading to the device.
This automatic verification is not possible with S7-1200 CPUs with firmware version V1.x. In
this case, users themselves must ensure that no version conflicts occur.
See also
TIA-Portal_Link (http://support.automation.siemens.com/WW/view/en/28919804/133000)
1.3.3 Editing devices and networks
1.3.3.1 General information on devices and networks
Contents

Readme
1.3 STEP 7 Basic
S7 PCT IO-Link
The S7 Port Configuration Tool is available for free download at the following link.
http://support.automation.siemens.com/WW/view/37936752 (http://
support.automation.siemens.com/WW/llisapi.dll?aktprim=0&lang=en&referer=%2fWW
%2f&func=cslib.csinfo&siteid=csius&groupid=4000002&extranet=standard&viewreg=WW&n
odeid0=33102519&objaction=csopen)
1.3.3.2 Use of modules on the S7-1200
Content
Use of modules on the S7-1200

The modules listed below are not supported on the S7-1200.
Family Module Order number

S7-300 FMs SM 338 6ES7 338-4BC01-0AB0
FM 350-1 6ES7 350-1AH03-0AE0
FM 350-2 6ES7 350-2AH00-0AE0, 6ES7 350-2AH01-0AE0
FM 351 6ES7 351-1AH01-0AE0, 6ES7 351-1AH02-0AE0
FM 352 6ES7 352-1AH02-0AE0
FM 355 S 6ES7 355-1VH10-0AE0
FM 355 C 6ES7 355-0VH10-0AE0
FM 355-2 C 6ES7 355-2CH00-0AE0
FM 355-2 S 6ES7 355-2SH00-0AE0
S7-300 PtP-CP CP 340 6ES7 340-1AH02-0AE0, 6ES7 340-1BH02-0AE0, 6ES7
340-1CH02-0AE0
CP 341 6ES7 341-1AH01-0AE0, 6ES7 341-1AH02-0AE0, 6ES7
341-1BH01-0AE0, 6ES7 341-1BH02-0AE0, 6ES7
341-1CH01-0AE0, 6ES7 341-1CH02-0AE0
Network component Diagnostics repeater 6ES7 972-0AB01-0XA0
ET 200S 1 Count 24 V 6ES7 138-4DA04-0AB0
1 Count 5 V 6ES7 138-4DE02-0AB0
1 Step 5 V 6ES7 138-4DC00-0AB0, 6ES7 138-4DC01-0AB0
2 pulses 6ES7 138-4DD00-0AB0, 6ES7 138-4DD01-0AB0
1 SI 6ES7 138-4DF01-0AB0
1 SI Modbus 6ES7 138-4DF11-0AB0
1 SSI 6ES7 138-4DB02-0AB0, 6ES7 138-4DB03-0AB0
1 Pos Universal 6ES7 138-4DL00-0AB0
SIWAREX 7MH4910-0AA01, 7MH4912-0AA01, 7MH4920-0AA01
ET 200M SIWAREX 7MH4 900-2AA01, 7MH4 900-3AA01, 7MH4 950-1AA01,
7MH4 950-2AA01

Readme
1.3 STEP 7 Basic
Loading S7-1200 module comments to the PG/PC

In central configurations with S7-1200, comments of modules, submodules and signal boards
are not loaded. With CPs/CMs, only the comments of the IE interface or DP interface are
loaded. In distributed configurations with ET 200SP or ET 200MP, only the comment of the
channels is loaded from the I/O modules.
1.3.3.3 Replacing ET 200S positioning modules
Contents
Replacing ET 200S positioning modules

This information relates to the positioning module "1 Step 5V" (6ES7 138-4DC00-0AB0) from
a project which was created with TIA Portal V11.0. When replacing these modules from the
TIA Portal V11.0 with a new version of these modules, the parameter settings are reset to the
default values.
This is the case with one of the following procedures:
● Replace the positioning module 6ES7 138-4DC00-0AB0 with its successor module 6ES7
138-4DC01-0AB0 by means of a device exchange.
● Updating the module version using the appropriate button in the device properties in the
Inspector window.
1.3.3.4 CP 343-2 on SIMATIC S7 Embedded Controller EC31-RTX
Contents
CP 343-2 on SIMATIC S7 Embedded Controller EC31-RTX

The module AS-Interface CP 343-2 (article no.: 6GK7 343-2AH01) can be inserted in an
expansion rack of the SIMATIC S7 Embedded Controller EC31-RTX (article no.: 6ES7
677-1DDxx-0BB0), but the CP 343-2 cannot be operated with the EC31-RTX.
1.3.3.5 F-CM AS-i Safety ST for ET 200SP
Content

Readme
1.3 STEP 7 Basic
F-CM AS-i Safety ST (3RK7 136-6SC00-0BC1) from HSP0070

When using an F-CM AS-i Safety ST (3RK7 136-6SC00-0BC1) using HSP0070 in TIA Portal
V13.0, after updating to Service Pack 1, the HSP0070 (F-CM AS-i Safety ST) must be updated
to version V2.0. This is necessary to allow use of the module in TIA Portal V13 Service Pack
1.
1.3.3.6 S7 routing via IE/PB Link
Content
S7 routing via IE/PB Link

In the following situations, no routing via the IE/PB Link PN IO is possible:
● S7 routing between two CPUs of the S7-1500
● S7 routing of PG connections to CPUs of the S7-1200/1500
● S7 routing of HMI connections to CPUs of the S7-1200/1500
This behavior relates to the IE/PB Link with firmware version V2.1 (6GK1 411-5AB00).
1.3.3.7 Notes on online and diagnostics
Contents
Hardware detection followed by online connection

When the "Online > Hardware detection" command is performed for an unspecified CPU, the
online configuration is not loaded from the CPU. If you do not load the configuration resulting
from the hardware detection to the CPU, the device and network views will always show a
difference between the offline and online configurations. It will appear that there are different
configurations in the online and diagnostic views, although the MLFBs are identical in the actual
CPU and the offline CPU.

Readme
1.3 STEP 7 Basic
1.3.4 Programming a PLC
1.3.4.1 General notes on PLC programming
Content
Information about network security

For communications access between the TIA Portal and CPU or between HMI (except for HMI
access using "GET/PUT communication") and CPU, there are integrated security functions.
These provide greater protection from manipulation and higher access protection. To protect
against unauthorized network access to a CPU with standardized communications access
such as "GET/PUT", "TSEND/TRCV", "Modbus", "FETCH/WRITE", you should also take
suitable additional measures (e.g. cell protection concept).
Renumbering PLC data types

For better performance, the S7 CPUs process PLC data types with numbers. The user is not
aware of these numbers, because the system processes the numbers independently. This
means number conflicts are automatically resolved. When using know-how protected blocks
that use PLC data types, it may be useful to set up your own numbering system (recommended
> 5000) because the automatic resolution of numbering conflicts may result in a password
prompt (compilation required).
To renumber the default number of a PLC data type, follow these steps:
1. Open the project library in the "Libraries" task card.
2. Drag the compilable PLC data type to the "Types" folder.
The "Add type" dialog opens.
3. Enter the properties of the new type.
4. Click "OK" to confirm.
5. Right-click the PLC data type.
The shortcut menu opens.
6. Select "Edit type" in the shortcut menu.
7. Open the "PLC programming" task card once again.
The extension "in testing" is now added to the name of the PLC data type.
8. Right-click the PLC data type.
The shortcut menu opens.
9. Select "Properties" in the shortcut menu.
10.Change the number of the PLC data type in the "General" section.
11.Select "Release version" from the shortcut menu of the library.

Readme
1.3 STEP 7 Basic
The PLC data type now has the new number and can be used. The assigned number is retained
even if the type of the PLC data type is revoked.
Generating external sources from blocks

When generating external sources from blocks, the changes made directly in the block
interface to the default values of PLC data types are not exported to the sources. This means
these values are not available when the sources are imported once again. The default values
are applied instead. To prevent this loss of data for the modified default values, the changes
must be made directly in the PLC data type and not in the block interface. In this case, the
changes are also exported when generating external sources.
Indirect indexing of ARRAY components of data type bit string in SCL

In TIA Portal V13, you can address the components of an ARRAY for a CPU of the S7-1200
series in SCL with a tag of the data type BYTE, WORD or DWORD as index in addition to a
tag of the integer data type if the IEC check is not set.
Explicit data type conversion in SCL

As of TIA Portal V13, the string is displayed with a leading sign during explicit data type
conversion of SINT/INT/DINT/LINT_TO_STRING or WSTRING in SCL and transferred aligned
to the left.
The result is an incompatibility with TIA Portal V12 SP1, in which the string was transferred
aligned to the right during conversion.
Start value behavior during "Upload from device"

The start values that you have changed with the instruction "WRIT_DBL: Write to data block
in the load memory" will be lost during execution of the action "Upload from device".
Online/offline differences in the project tree (S7-1200 FW V2.0 and V2.1)

If you use the instruction "WRIT_DBL: Write to data block in the load memory" to change a
data block, the resulting difference between online and offline block is initially not displayed
correctly by the symbols in the project tree. The difference is only shown when you terminate
an online connection and then go back online.
Loading inconsistent programs to a device

In TIA Portal, it is not possible to download inconsistent programs to a device without a
consistency check. During the loading process, all blocks of the program are implicitly checked
and are compiled again in the event of inconsistencies. If, however, there are programs on
your CPU which were loaded with earlier versions of STEP 7, these programs could
demonstrate inconsistencies.
In this case, note the following:

Readme
1.3 STEP 7 Basic
If you load an inconsistent program from a device, you will not be able to load the program
unchanged to the device afterwards, because a consistency check always takes place during
the loading process and existing inconsistencies are corrected.
Process image of PTO/PWM outputs

Do not use PTO/PWM outputs in the process image (for example, for access in the user
program, for online functions or in HMI). The update rate of the process image is much slower
than the rate of the signal changes. The display in the process image therefore does not reflect
the signal flow.
Monitoring blocks in LAD and FBD

If the start of the current path is outside the visible range, it may not be possible to determine
the input value. In this case, the current path is shown grayed out.
Avoid using PLC data types generated by the system in libraries

Some instructions generate their own PLC data types during instancing which are saved in
the "PLC data types" project folder. However, you should not use these system-generated
PLC data types in any library, because they may be recreated by the system at any time and
may result in an unfavorable system behavior.
Using global data blocks in assignments

It is not possible to assign the contents of a global data block to a structurally identical data
block, e.g. using a move box.
1.3.4.2 Compatibility of PLC programs from V12 SP1 or V13
Content
Compatibility
You can continue to use in V13 SP1 all programs that were created with TIA Portal V12 SP1
or V13. However, because improvements were made to the compiler and errors corrected
there in V13 SP1, it can occur in rare cases that the program reacts differently after the upgrade
or that you have to adjust the program code manually. These cases are described in detail
below.
In addition, you have the option of editing the project in compatibility mode. Compatibility mode
is available for projects that were created with TIA Portal V12 SP1 and V13.
You can find additional information on the compatibility under "Compatibility of projects".

Readme
1.3 STEP 7 Basic
Instruction "S_CONV: Convert character string"

Der EN/ENO mechanism behaves differently in TIA Portal V13 SP1 than in TIA Portal V13.
In version V13, the ENO enable output returns the signal state "0" in case of error, even if you
have deactivated the ENO enable output. If you have switched an additional instruction to the
EN enable output, this is then not executed.
In version V13 SP1, the ENO enable output returns the signal state "1" in case of error, if you
have deactivated the ENO enable output. If you have switched an additional instruction to the
EN enable output, this is then executed as expected.
Instruction "MUX: Multiplex" (SCL)

Up to and including TIA Portal V13, the value of the tag at the input parameter was output
unchanged as a function value, even if the K parameter had a negative integer. This behavior
has changed in TIA Portal V13 SP1.
In TIA Portal V13 SP1, if you use the BOOL, STRING, DT or DTL data types at the input
parameters of the MUX instruction and the K parameter is a negative integer, the value of the
tag is changed.
Instruction "DEMUX: Demultiplex" (SCL)
Up to and including TIA Portal V13, no value was output at the OUTELSE output parameter if
the value of the K parameter was < 0. In contrast, the value of the IN input parameter was
output at the OUTELSE output parameter if the value of the K parameter was > available
outputs. This behavior has changed in TIA Portal V13 SP1.
In the TIA Portal V13 SP1, if you specify at the K parameter a value that is outside the available
outputs (K < 0 or K > available outputs), then the value of the IN input parameter is output at
the OUTELSE output parameter.
Function values (Return)

As of TIA Portal V13 SP1, more stringent syntax rules apply to function call:
It is checked that the function value (Return) is written in any case, even if multiple possible
program paths can be run through in the function. Therefore, there is no longer any risk that
the function values will accidentally not be written during runtime.
However, you may possibly receive syntax errors in functions during compiling, which it was
still possible to compile without errors in V13. In such cases change the program code so that
the function valve is written in all possible program paths.
Example:
SCL
IF #MyIn1 = #MyIn2 THEN
#Block_3 := #MyIn1 + 1;
END_IF;

Readme
1.3 STEP 7 Basic
In this example, the function value of "Block_3" is not written if the condition of the IF instruction
is not fulfilled. The function value then contains an undefined value.
SCL
#Block_3 := #MyIn1;
IF #MyIn1 = #MyIn2 THEN
#Block_3 := #MyIn1 + 1;
END_IF;
In this example the function valve of "Block_3" is definitely written in the program, since "MyIn1"
is set as default before the IF loop is completed.
Comparing the hardware data types HW_IO and HW_DEVICE

As of TIA Portal V13 SP1, there is a stricter syntax rule that is valid for the comparison of the
data types HW_IO and HW_DEVICE:
Up until and including TIA Portal V13 it was possible to compare the data types HW_IO and
HW_DEVICE directly with each other.
If you want to compare these data types in TIA Portal V13 SP1 you have to first create a tag
of the data type HW_ANY in the section "Temp" for the block interface and then copy the
LADDR (from data type HW_DEVICE) to the tag. It is then possible to compare HW_ANY and
HW_IO.
EN/ENO mechanism for STRING conversion
Conversion Description
Strg_TO_Chars: Convert character string to Array The ENO enable output returns the signal state "0"
of CHAR even if you have deactivated the ENO enable out‐
put:
● For an invalid character at the CHARS
parameter
● For an invalid ARRAY index at the PCHARS
parameter
● If the sum of the PCHARS and STRG
parameters exceeds the length of the target
ARRAY.
Chars_TO_Strg: Convert Array of CHAR to char‐ The ENO enable output returns the signal state "0"
acter string even if you have deactivated the ENO enable out‐
put:
● If the sum of the PCHARS and CNT
parameters exceeds the length of the source
ARRAY.

Readme
1.3 STEP 7 Basic
1.3.4.3 Instructions
Content
Instruction "TRCV_C: Receive data via Ethernet"

Contrary to the information provided in the online help, the communication connection is
terminated immediately, and not after sending data, when the CONT parameter is set to the
value "0".
Instruction "T_CONFIG: Configure interface"

The CPU is restarted after you have executed the "Configure interface" instruction in order to
change an IP parameter. The CPU goes to STOP mode, a warm restart is carried out and the
CPU starts up again (RUN mode). Make sure that the control process is in a secure operating
mode after the CPU has been restarted following execution of the "Configure interface"
instruction. Uncontrolled operation can result in serious material damage or personal injury
due to malfunctions or programming errors, for example. Non-retentive data could be lost.
Parameters ERROR and STATUS
ERROR STATUS ERR_LOC Explanation

(DW#16#..)
0 00000000 0 After the instruction has
been executed success‐
fully, the STATUS pa‐
rameter "00000000"
does not return any val‐
ue.
Instruction "DataLogCreate: Create data log"

In addition to the values described in the online help, the RET_VAL parameter can also adopt
the following values:
Error code Explanation

(W#16#...)
8B24 Invalid assignment at parameter HEADER (for example, bit memory used as memory
area).
8C24 Invalid assignment at parameter DATA (for example, bit memory used as memory area).

Readme
1.3 STEP 7 Basic
Instruction "DPSYC_Fr: Synchronize DP slaves / Freeze inputs"

In addition to the values described in the online help, the RET_VAL parameter can also have
the following value:

(W#16#...)
80A4 Communication on central PROFIBUS disrupted.
Instruction "Get_IM_Data: Reading identification and maintenance data"

The explanation for the values of the RET_VAL parameter described in the online help has
been changed as follows:

(W#16#...)
80B1 No valid data available. (The I&M data is either not supported by the (sub)module or you
have not configured I&M data for this device.)
Instruction "T_RESET: Resetting the connection"

In addition to the values described in the online help, the STATUS parameter can also have

(W#16#...)
7000 No job processing active.
Instruction "TCON: Establish communication connection"

In addition to the values described in the online help, the STATUS parameter can also have

(W#16#...)
80A1 The specified connection or the port is already being used.
Instruction "RD_ADDR: Determine the IO addresses from the hardware identifier"

Output of the IO addresses with packed addresses of an ET200
With packed addresses of an ET200. the first module of the pack group returns all addresses.
For the other modules, the following is output with the PIADDR and PQADDR parameters:
● With PROFINET as address "0".
● With PROFIBUS as address "0". The error code 16#8090 (the hardware identifier of the
module at the LADDR parameter is invalid.) is also output.
For the number of bytes of the inputs and outputs (parameters PICOUNT and PQCOUNT),
"0" is output in each case.

Readme
1.3 STEP 7 Basic
Instruction "RD_LGADR: Determine the IO addresses from the hardware identifier"

Output of the IO addresses with packed addresses of an ET200
With packed addresses of an ET200. the first module of the pack group returns all addresses.
For the other modules, the following is output with the PEADDR and PAADDR parameters:
● With PROFINET as address "0".
● With PROFIBUS as address "0". The error code 16#8090 (the hardware identifier of the
module at the LADDR parameter is invalid.) is also output.
For the number of bytes of the inputs and outputs (parameters PECOUNT and PACOUNT),
"0" is output in each case.
Notes on the use of "RecipeExport" and "RecipeImport"

● The instructions RecipeExport and RecipeImport are not suitable for applications in which
special protection is necessary for the recipe data. For higher protection of the data use
the recipe functions of HMI.
● The data block with the recipe data exported with RecipeExport can be located in work or
load memory. If the data block is both in work memory as well as in load memory, the values
from work memory are used.
● You can use different separators for the separators of the row values in the recipe. Note
that if you open the CSV file with the exported recipe data, for example in Excel, commas
can be replaced by periods and vice versa. The reason for this is that different languages
use different decimal separators. This can have effect when importing CSV files. The
following convention applies for RecipeImport; the first detected possible separator is
assumed to be the separator for all values of a table row.
– Example 1: If a semicolon is detected as the first separator, during import it is assumed
that the semicolon is used as the separator for all further values. As the decimal
separator with a value of the type REAL, a comma is then used.
– Example 2: If a comma is detected as the first separator, during import it is assumed
that the comma is used as the separator for all further values. As the decimal separator
with a value of the type REAL, a period is then used.
If the recipe data record contains a character string, make use that the character string
does not contain the separator you are using. With character strings, also make sure that
they do not contain any control characters that specify a line break (with ASCII: LF, CR LF,
CR).
Note: Spaces and tabs cannot be used as separators. The lead to error code 80B2 during
import.
Notes on the use of data logs

Data logs are stored as a CSV file and can be opened using the Web server, for example in
Excel. If you use character strings within a data log, make sure that you do not use any
characters in the character strings that are also used as the separator for the row elements of
the CSV file.

Readme
1.3 STEP 7 Basic
Instructions STRG_VAL and VAL_STRG

The instructions STRG_VAL and VAL_STRG are also available in the SCL programming
language in V13 SP1 in contrast to the restriction in the online help.
Passing parameters to asynchronous executable blocks

Code blocks (FBs/FCs) and data blocks (DBs) can be created with different access types
("standard" and "optimized"). In code blocks, you can call any instructions. Many instructions
(e.g. "WRIT_DBL" and "READ_DBL") are executed asynchronously. These blocks cannot be
supplied with tags from TEMP because the data must not be changed during execution.
Ensure that you do not use these instructions in programs in which code blocks of different
access types are called reciprocally. This could cause the following to occur:
● A structure from a standard data block is directly or indirectly passed to an optimized code
block, which forwards this structure directly or indirectly to one of the blocks mentioned
above.
● The reverse scenario, whereby a structure from an optimized code block is directly or
indirectly passed to a standard data block, which forwards this structure directly or indirectly
to one of the blocks mentioned above.
Otherwise a hidden copy of the passed data is created in TEMP, which leads to the
asynchronous blocks returning a negative acknowledgment.
1.3.4.4 Testing the user program
Testing with the watch table
Content
Multiple access to the same CPU

Access to a CPU from a PG/PC is permitted only when a TIA Portal is open. Multiple access
to the same CPU is not permitted and can lead to errors.
Loading data blocks during an active control job
Note
Loading changed data blocks during an active control job can result in unforeseen operating
states. The control job continues to control the specified address, although the address
assignment may have changed in the data block. Complete active control jobs before loading
data blocks.

Readme
1.3 STEP 7 Basic
Testing programs converted from older STEP 7 versions

To monitor and test a program converted from an older STEP 7 version, you first need to
compile and download the program with the current STEP 7 version.
1.3.5 Inter Project Engineering (IPE)
1.3.5.1 Notes on IPE
Contents
Comment box of the device proxy

Contrary to the description in the information system for the TIA Portal V13, with the "Inter
Project Engineering" functionality, the comment field for a device proxy cannot be edited.
Restricted functionality
In the TIA-Portal V13, the "S7 GRAPH overview" and "PLC code display" functionality cannot
be used in conjunction with the IPE device proxy.
Using system diagnostics in the device proxy

To use the "system diagnostics" function in an IPE device proxy, for example, a system
diagnostics view, insert the PLC alarms as content of a device proxy.

Readme
1.3 STEP 7 Basic
1.3.6 Technological functions
1.3.6.1 Notes on technological functions (S7-1200)
S7-1200 Motion Control - MC_Home

The motion control instruction "MC_Home" has been extended with the absolute value encoder
adjustment:
● Absolute encoder adjustment (relative)
MC_Home.Mode = 6
The current position is shifted by the value of the parameter "MC_Home.Position".
The calculated absolute value offset is stored retentively in the CPU.
(<Axis name>.StatusSensor.AbsEncoderOffset)
● Absolute encoder adjustment (absolute)
MC_Home.Mode = 7
The current position is set to the value of the parameter "MC_Home.Position".
The calculated absolute value offset is stored retentively in the CPU.
(<Axis name>.StatusSensor.AbsEncoderOffset)
S7-1200 Motion Control - MC_WriteParam

Motion control instruction "MC_WriteParam" for drive connection via PROFIdrive/analog
output:
Contrary to the statements in the online help, you cannot write parameters with
"MC_WriteParam" which require a restart of the technology object.
S7-1200 Motion Control - MC_ChangeDynamic

You can only use the motion control instruction "MC_ChangeDynamic" for drive connection
via PTO (Pulse Train Output).
S7-1200 Motion Control - Application cycle MC-Servo [OB91]

To avoid disruptions in the program execution on the CPU, set the application cycle depending
on the number of used axes as follows:
Application cycle = number of axes x 2 ms
Number of axes Application cycle

1 2 ms
2 4 ms
4 8 ms
8 16 ms
The SINAMICS G120 drive updates the drive process image every 4 ms. To improve control,
set the application cycle of the MC-Servo [OB91] to 4 ms or to a multiple of 4 ms.

Readme
1.3 STEP 7 Basic
S7-1200 Motion Control - Overflow MC-Servo [OB91]

Contrary to the online help, the CPU does not go into STOP at overflow of the MC-Servo [OB91].
If necessary, you can set the CPU to STOP at overflow of MC-Servo [OB91] via a time-error
OB (OB80).
S7-1200 Motion Control - Process image partition "OB Servo PIP"

For optimal control of all I/O modules (e.g. hardware limit switches) used by Motion Control,
assign them to the process image partition "OB Servo PIP". The assignment causes the I/O
modules to be processed simultaneously with the technology object.
A high-speed counter (HSC) used by Motion Control is automatically assigned to the process
image partition "OB Servo PIP".
S7-1200 Motion Control - Renaming technology objects

In order to assure the consistency of your project, after you rename the technology objects,
download the project to the CPU while it is in STOP. A name change includes when you delete
a technology object and create a new technology object with a new name and data block
number of the deleted technology object.
S7-1200 Motion Control - ErrorIDs and ErrorInfos

The ErrorInfo 16#003D is also displayed if a drive with an analog drive connection has turned
off.
The ErrorInfo 16#002C has been supplemented for the ErrorID 16#820A:
ErrorID ErrorInfo Description Solution

16#820A It is not possible to restart the axis
16#0013 The axis is enabled in the user program Disable the axis with the "MC_Power" instruction;
restart again
16#0027 The axis is currently being operated in "Manual Exit "Manual control"; restart again
control" (axis control panel)
16#002C The axis is not disabled. Disable the axis; restart the command
16#0047 The technology object is not ready for restart. Download the project again.
16#0048 Condition for restart of the technology object is Disable the technology object.
not satisfied.

Readme
1.4 WinCC Basic
PtP module with CM 1243-5 PROFIBUS Master

You have to make the following settings in the instance DB for the instructions when using the
PtP-Module CM PtP RS232 BA, CM PtP RS422/485 BA, CM PtP RS232 HF, CM PtP
RS422/485 HF and CM PtP with a CM 1243-5 PROFIBUS Master with firmware ≤ V1.3.4:
● Send_P2P
max_record_len = 240
● Modbus_Master
Send_P2P.max_record_len = 240
● Modbus_Slave
Send_P2P.max_record_len = 240
1.4 WinCC Basic
1.4.1 Security information
Siemens provides products and solutions with industrial security functions that support the
secure operation of plants, solutions, machines, equipment and/or networks. They are
important components in a holistic industrial security concept. With this in mind, Siemens’
products and solutions undergo continuous development. Siemens recommends strongly that
you regularly check for product updates.
For the secure operation of Siemens products and solutions, it is necessary to take suitable
preventive action (e.g. cell protection concept) and integrate each component into a holistic,
state-of-the-art industrial security concept. Any third-party products that may be in use must
also be taken into account. For more information about industrial security, visit
http://www.siemens.com/industrialsecurity (http://support.automation.siemens.com)
To stay informed about product updates as they occur, sign up for a product-specific
newsletter. For more information, visit
http://support.automation.siemens.com (http://support.automation.siemens.com)
Passwords
Various passwords are set by default in WinCC. For security reasons, you should change
these passwords.
● For the user "Administrator", the default password is "administrator".
Communication via Ethernet

In Ethernet-based communication, end users themselves are responsible for the security of
their data network. The proper functioning of the device cannot be guaranteed in all
circumstances; targeted attacks, for example, can lead to overload of the device.

Readme
1.4 WinCC Basic
Ending Runtime automatically

If automatic transfer is enabled on the HMI device and a transfer is started on the configuration
PC, the running project is automatically stopped on the HMI device. The HMI device then
switches autonomously to "Transfer" mode. Transfer mode may cause undesired reactions in
the system.
After the commissioning phase, disable the automatic transfer function to prevent the HMI
device from switching inadvertently to transfer mode. To block access to the transfer settings
and thus avoid unauthorized changes, assign a password in the Control Panel.
Network settings
The following tables show the network settings of each product which you need in order to
analyze the network security and for the configuration of external firewalls:
WinCC Basic (without simulation)

Name Port num‐ Transport Direction Function Description
ber protocol
ALM 4410* TCP Inbound, License service This service provides the complete functionali‐
Outbound ty for software licenses and is used by both the
Automation License Manager as well as all li‐
cense-related software products.
HMI Load 1033 TCP Outbound HMI Load This service is used to transmit images and
(RT Basic) configuration data to Basic Panels.
WinCC Simulation for Basic Panels

Name Port num‐ Transport Direction Function Description
ber protocol
HMI Load 1033 TCP Inbound HMI Load This service is used to transmit images and
(RT Basic) configuration data to Basic Panels.
EtherNet/IP 44818 TCP Outbound Ethernet/IP The Ethernet/IP protocol is used for connec‐
2222 UDP Inbound Ethernet/IP The Ethernet/IP protocol is used for connec‐
Modbus TCP 502 TCP Outbound Modbus TCP The Modbus TCP protocol is used for connec‐
channel tions to Schneider PLCs.
RFC 1006 102 TCP Outbound S7 channel Communication with the S7 controller via
Ethernet/PROFINET
Mitsubishi MC 5002 TCP Outbound Mitsubishi MC The Mitsubishi protocol is used for connections
channel to Mitsubishi PLCs.

Readme
1.4 WinCC Basic
1.4.2 News
News about the TIA Portal

You can learn about the latest news about various topic areas of the TIA Portal in Siemens
Industry Online Support.
All news concerning WinCC can be found here: News (http://support.automation.siemens.com/
WW/view/en/88360672)
1.4.3 Notes on WinCC V13 SP2
Contents
Information that could no longer be included in the online help and important information about
product features.
Mass data transfer with USB

If you have installed Windows 10 on the configuration PC, the "USB" transfer channel is not
available.
This restriction applies to the following devices and tools:
● Basic Panels: KP300 Basic, KP400 Basic, TP1500 Basic
● Panels: OP and TP of 70 series, 177 series and 270 series
● Multi Panels: Multi Panels of the170 series, 270 series and 370 series
● Mobile Panels: 170 series and 270 series
● WinCC Engineering System
● "ProSave" service tool
Note
The "USB" transfer channel remains available if Windows 7 or Windows 8 is installed on the
configuration PC.
Solution
Use other transfer channels to transfer the project data, such as the "Industrial Ethernet" or
"PROFIBUS DP" channel.

Readme
1.4 WinCC Basic
Missing fonts (panels)

The following fonts no longer belong to the standard installation pack in Windows 10 and are
not pre-installed:
● MS PGothic (is used as standard for displaying Japanese characters)
● Gulim (is used as standard for displaying Korean characters)
● MingLiU for Chinese (is used as standard for displaying Chinese characters for Taiwan,
Hong Kong and Macao)
If these fonts are not installed they cause problems during compilation in Runtime.
For example, if you open an error-free V13 SP1 project that was created on a configuration
PC with Windows 7 on a configuration PC of V13 SP2 with the Windows 10 operating system,
error messages can be output during compilation because of the fonts that are not installed.
You can find more detailed information on fonts in Windows 10 at https://support.microsoft.com/
en-us/kb/3083806 (https://support.microsoft.com/en-us/kb/3083806)
Solution
Compile the project before you transfer it to your HMI device. How to determine whether the
fonts you require are missing.
To avoid problems in Runtime, you must install these fonts and/or the corresponding Windows
language pack.
Sm@rtServer
A connection can only be established via the Sm@rtClient application if the server is running
on a PC with Windows 7.
Communication via SIMATIC HMI HTTP

No connection can be established from a panel via SIMATIC HMI HTTP if the HTTP server is
running on a PC with Windows 10.
Debugging of user-defined VB functions

You can download the Microsoft Visual Studio 2008 Shell (Integrated Mode) debugger for free
from the Microsoft homepage. In doing so, make sure that you use the English version.
The latest versions from Microsoft are generally recommended for the purpose of debugging.
Communication with S7-1500 Software Controller

If you are using an S7-1500 Software Controller (CPU 1505S, from V1.7; CPU 1507S, from
V1.8) and would either like to install an update for WinCC Runtime Advanced or reinstall WinCC
Runtime Advanced, please take note of the information in FAQ 109481445 (https://
support.industry.siemens.com/cs/ww/en/view/109481445).

Readme
1.4 WinCC Basic
1.4.4 Notes on WinCC V13 SP1
1.4.4.1 System-wide functions
Contents
product features.
Using system diagnostics in the device proxy

To use the system diagnostics function in an IPE device proxy, for example, a system
diagnostics view, insert the PLC alarms as content of a device proxy.
Importing and exporting project texts

In WinCC, you only import the previously exported project texts into the same project. Importing
into a different project is not supported.
Initialize device proxy with data from a V13 project

You cannot initialize a device proxy with data from a V13 project in a project with the version
V13 SP1.
Upgrade the V13 source project to version V13 SP1 to initialize the device proxy in the target
project with the data from the source project.
1.4.4.2 Compiling and loading
Contents
product features.
Compiling and loading

If internal errors or warnings occur during compiling, compile the complete project using the
command "Compile > Software (rebuild all)" in the shortcut menu of the HMI device.
Before you start productive operation with your project, compile the entire project using the
"Compile > Software (rebuild all)" command from the shortcut menu of the HMI device.
If you are using HMI tags that are connected to the control tags in your project, compile all
modified blocks with the command "Compile > Software" in the shortcut menu before you
compile the HMI device.

Readme
1.4 WinCC Basic
Settings for update of operating system

If you select the command "Online > HMI device maintenance > Update operating system"
from WinCC, you cannot change the settings such as the type of PG/PC interface or baud
rate. The settings used during the last download are always used.
To make changes to the settings, open the "Extended download to device" dialog using the
"Online > Extended download to device" command and change the settings. When you click
the "Load" button the changed settings are saved.
Alternatively, you can perform an update of the operating system with changed settings with
ProSave. You start ProSave via the Windows Start menu "Siemens Automation > Options and
Tools > HMI Tools > SIMATIC ProSave".
Incorrect installation of ProSave

If you receive an error message during installation of ProSave when loading data to a target
device or maintenance of an HMI device, then you cannot remedy this error using the repair
function of setup. Remove ProSave via the Control Panel. Then start setup and install the
"ProSave" component again.
Checking the address parameters

During compilation of an HMI device in the project tree with the command "Compile > Software"
in the shortcut menu, the address parameters of the HMI device, such as the IP address, will
not be checked. If you want to ensure that the address parameters are checked as well, you
will have to compile the HMI device using the "Compile" button in the "Devices & Networks"
editor of the toolbar.
Error message when downloading data to the PLC

A panel and a PLC are connected and communicating with other.
If a tag is accessed while downloading data from the panel to the PLC, an error message is
displayed on the panel.
Delayed reaction in the "Extended download to device" dialog

If the settings in the "Extended download to device" dialog for "Type of the PG/PC interface"
and "PG/PC interface" do not match the settings on the HMI device, this can result in the
application not responding for up to a minute.
Extended download with an S7-1200 and a Comfort Panel

An S7-1200 PLC and a Comfort Panel are located in the same physical network as the PG/
PC. You open the "Extended download to device" dialog for the Comfort Panel.
If you enable the option "Show all accessible devices", it may occur that the application stops
responding.

Readme
1.4 WinCC Basic
OP77A, OP73, TP177A: Loading projects

When loading a project to an HMI device, it can happen that Runtime is not automatically
ended, even though "Remote Transfers" is activated in the Panel.
If this happens, stop Runtime and manually set the transfer mode on the HMI device.
Loading a SIMATIC HMI application to a PC station

The following circumstances can lead to an error message during the first load of a SIMATIC
PC station:
● A SIMATIC HMI application is configured in a PC station in the project
– WinCC Runtime Advanced
– WinCC Runtime Professional
– WinCC Standby
– or WinCC Client
● The property "S7RTM is installed" is activated.
Before you load a SIMATIC PC station for the first time, select the configured device HMI_RT
(WinCC...) in the project tree. Open the "Extended download to device" dialog and select the
appropriate interface and parameter settings. Click "Load".
You then load the PC station as normal.
Project transfer via USB

If you have connected more than one HMI device via USB to your configuration PC, project
transfer is only possible to the last connected device.
Opening project files

When you run "HmiIRTm.exe", a dialog opens asking if you want to open the project file (.fwc).
The following options are available to you:
● "Yes": A dialog opens allowing you to select a project file (.fwc).
● "No": The dialog closes.
Tag simulator in WinCC Professional does not start

If the tag simulator does not start in WinCC Professional, it may be because the fm20.dll file
has not been installed in the system yet. The fm20.dll file cannot be distributed and must be
installed as part of a Microsoft application:
http://support.microsoft.com (http://support.microsoft.com/default.aspx?scid=kb;EN-US;
224305)

Readme
1.4 WinCC Basic
You have the following two options for installing the fm20.dll file:
● Install an application, such as Microsoft Office 97, on the destination system. The
installation routine also installs the fm20.dll file.
● You can also download and install the Microsoft ActiveX Control Pad free of charge. The
fm20.dll file is also installed in this case. Additional information on the ActiveX Control Pad
is available on the Microsoft Developer Network website:
http://msdn.microsoft.com/en-us/library/ms968493.aspx (http://support.microsoft.com/
default.aspx?scid=kb;EN-US;224305)
Error message when PLC is loaded with a newer version of the TIA Portal
PLC code display shows the current program status of PLC programs.
An error message is output if the PLC code display from an older version of WinCC accesses
a program on the PLC loaded with a new version. Make sure that the PLC and the HMI are
loaded with the same version of the TIA Portal.
Comfort panels as of device version 13.0: Backing up data while loading projects
If the transfer is interrupted for Comfort Panels with a device version 13.0 or higher, WinCC
automatically ensures that no data is lost and that existing data is only deleted on the HMI
device after complete transmission.
Loading projects to a file

The "Load project to file" functionality is only available in Runtime Advanced devices with
version V13 or older.
Displaying characters in transfer alarms

If characters are not displayed correctly in the transfer alarms during transfers to HMI devices
with the device version V12 or older, please check the region and language settings in
Windows. Set the corresponding language under "Language for non-Unicode programs".
1.4.4.3 Notes on use
Contents
product features.
Copying HMI devices with HMI connections

If you copy an HMI device with HMI connections to a PLC, the HMI connection in the new HMI
device is not automatically connected to an existing PLC with the same name. This applies to
copying within a project as well as copying across projects.

Readme
1.4 WinCC Basic
To access the PLC tag via HMI tag in the new HMI device, you have to complete the
configuration of the HMI connection immediately after copying. Proceed as follows:
1. Open the "Devices & Networks" editor.
2. Connect the new HMI device to the desired network.
3. Open the connection table.
4. Select the HMI connection of the new HMI device.
5. Select the desired PLC under "Partner".
If you compile the new HMI device or connect additional PLC tags in between copying the HMI
device and completing the connection, there may be some instances in which an additional
HMI connection to the same PLC is created. This is especially true if you connect HMI tags
with DB array elements.
Device replacement
After an HMI device has been replaced, you should check the appearance of the configured
screens. Changing the size of the display may result in changes to the position and appearance
of screen objects, e.g. recipe view and alarm view.
Device replacement - communication

If an HMI device is replaced, error messages of the type "... are not supported in the new
configuration. and will therefore be removed" may be generated. These alarms refer to
configured connections of the device and are triggered, for example, if the HMI devices have
a different number of interfaces. These connections are marked red after a device replacement.
If you would like to continue to use these connections, you have change the configuration of
the connection. Proceed as follows:
1. Open the "Devices and Networks" editor.
2. Click "Network" in the toolbar of the network view.
3. Network the interface of the HMI device with the interface of the CPU.
4. Click in the table area of the network view on the "Connections" table.
5. Select the connection marked red.
6. Enter the new interface under "Properties > General > Interface" in the Inspector window.
Specifying the time of modification in the overview window

The times of modification displayed in the overview window only refer to changes to the object
itself. Changes to subordinate objects, e.g. screen objects in a screen, do not cause the time
of the last change to the screen to change in the overview window.

Readme
1.4 WinCC Basic
HMI device wizard

When you create a device with a color display using the HMI device wizard, the graphics of
the navigation buttons may be displayed in black and white. This error only occurs, however,
if the new device is created with the same name as a device with a monochrome display which
has been deleted in the meantime.
You can avoid this error by always deleting the associated graphics in the Graphics collection
whenever you delete a device from the project.
Objects with object references in the project library

Two copying methods can be used in WinCC flexible.
● With "simple copy" a WinCC flexible screen including an IO field, for example is copied.
Only the object name of a tag configured on the IO field is copied, as this is a reference.
● With "copy", a screen, an IO field contained there and a tag configured on the IO field
together with its properties are copied.
These two methods can also be used for storing an object in a library. Project libraries and the
objects contained there are migrated during migration and can be used in WinCC.
In WinCC, however, only one copying method is available. With regard to tags, it functions like
"simple copy" in WinCC flexible. With regard to graphics, graphics lists and text lists, it functions
like "copy" in WinCC flexible.
If you stored objects with references to tags in a library in WinCC flexible, you must reconfigure
the referenced objects when using them in WinCC.
Installing East Asian project languages on a PC without Asian operating system

If you select an East Asian project language on a PC that does not have an Asian operating
system installed, the default font is marked as invalid in the "Runtime settings > Language &
font" editor.
To resolve this problem, open the "Regional and Language Options > Languages" dialog in
the Control Panel and enable the "Install files for East Asian languages" option.
Installation sequence for Startdrive

When you install Startdrive on a PC, adhere to the following installation sequence:
● Install STEP 7 V13.0.
● Install Startdrive.

Readme
1.4 WinCC Basic
Compatibility with V12 and V13

Empty projects are installed in the installation directory under ..\Portal V13\SampleProjects to
allow the TIA Portal to be opened in compatibility mode:
● V12.0.1.4 project with the name "TIA_Portal_Project_V12.0.1.4.ap12", so that TIA Portal
V13 SP1 can be opened in V12 compatibility mode
● V13.0.0.3 project with the name "TIA_Portal_Project_V13.0.0.3.ap13", so that TIA Portal
V13 SP1 can be opened in V13 compatibility mode
This project must be copied to a local directory with full access before it can be used. For more
information on this, refer to FAQ ID 66027369.
File browser on a Windows 8 PC with touch screen

You can only operate the file browser dialog with a mouse, keyboard or on-screen keyboard
(without using the touch function) on a Windows 8 PC with touch screen. We recommend using
the file browser dialog of the Windows operating system with the help of a script on a touch
screen PC with Windows 8.
Making characters available for HMI tags of the type WString/WChar

You define a string with which certain fonts can be displayed in a tag of the type WString or
WChar. All characters used in the project are available to you.
When compiling the project, only the characters of a font that are actually used in the project
are retained. Unused characters are removed when the project is compiled.
To be able to use fonts that are not installed on a panel, make the characters available as
configured texts in a screen.
1. Create a new screen.
2. Insert a text box.
3. In the properties of the text box, set a font that contains characters that you wish to use
later.
4. Insert the characters of the font that you wish to use later into the text box.
After the project is compiled, you can use the characters configured in the text in HMI tags of
the type WString/WChar.
1.4.4.4 Migration
Contents
product features.

Readme
1.4 WinCC Basic
Project languages in WinCC

WinCC V13 does not support all project languages that were available in WinCC flexible, such
as Arabic. If you receive an empty project as the result of your migration, you may want to
check the set editing language. Do not set the project languages that are not supported as
editing language in the source project. Proceed as follows:
1. Open the project with WinCC flexible.
2. Change the editing language to English, for example.
3. Save the project.
4. Restart the migration.
Migrating an integrated project with ProTool objects

The "PROTOOL option package(s) missing in STEP 7" error message output during migration
of a WinCC flexible project that is integrated in STEP 7 indicates that WinCC flexible 2008
SP3 is installed on your system. Moreover, the project still contains objects that were
configured using ProTool. Do not open the project with WinCC flexible 2008 SP3! Proceed as
follows to migrate the project:
1. Copy the project to a computer on which WinCC flexible 2008 SP2 and STEP 7 are installed.
2. Open the project in the SIMATIC Manager.
3. Remove all ProTool objects from the project.
4. Execute the "Save as" command in the "File" menu.
5. Enable the option "With reorganization" in the "Save project as" dialog.
6. Click OK.
7. Copy the project back to the original computer.
8. Restart the migration.
Migrating a WinCC V7 project: Border line of rectangles

In a WinCC V7 project, you have configured a rectangle with the settings "Line weight = 1"
and "Draw insider border = yes".
You then migrate the WinCC V7 project to WinCC V13. To have the rectangle displayed
correctly, follow these steps.
1. Open the Inspector window of the rectangle.
2. Open the property list.
3. Disable "Widen border line inwards".
Progress bar
As long as the progress bar still shows a value of 100%, the software is still busy running
remaining tasks such as the closing of references. The software will not respond to user input
while this status is given.

Readme
1.4 WinCC Basic
Open a project created with WinCC V11

When you open a V11 project with a WinCC V13 version, it is no longer be possible to open
this project with an older version afterwards.
Managing third-party ActiveX controls

The migration also supports third-party ActiveX controls. However, the controls must be
registered in the operating system. If an ActiveX control is not registered, migration is canceled.
If you save a project with the migration tool and perform the migration yourself on another PC,
the controls must also be registered on this PC.
Migrating integrated projects with alarm views

An alarm view is enabled with all alarm classes in an integrated project. The alarm classes are
disabled during migration of the project.
Once the migration of the project is completed, check the settings in the alarm view.
Enable the require alarm classes in the Inspector window of the alarm view if needed under
"Properties > General".
Migrating more extensive projects from WinCC V7

We recommend the use of a 64-bit operating system for the migration of more extensive
projects from WinCC V7.
To use the migration tool on a computer with a 64-bit operating system for large projects, start
the tool via the command line with the parameter 64-bit, as in the following example:
C:\Program Files (x86)\SIEMENS\Automation\MIGTOOL_V13\Bin
\Siemens.Automation.MigrationApplication.exe 64bit
Migrating projects from WinCC V7

In TIA Portal V13, you can continue to use projects from WinCC V7.2 after migration. Projects
from earlier WinCC versions cannot be migrated directly to WinCC TIA Portal version V13. If
you wish to continue using such projects in TIA Portal V13, you must first migrate them to the
WinCC V7.2 Classic page. To do so, use WinCC V7.2 with the latest update.
Migration log
As of TIA Portal V13.0 alarms are sorted into a tree structure in the migration log. This means
all alarms that are part of a specific subsystem are stored in one folder. The result is an increase
in the number of folders in the tree structure. Press the shortcut <NUM+ X> to expand the
currently selected folder and all subfolders in one single step.

Readme
1.4 WinCC Basic
Restrictions for user-specific project data

1. Folders and files you have created in the WinCC V7.2 project directory are not copied to
the new project directory during the migration. You must adapt all scripts that access such
directories and files after the migration.
2. C standard functions of WinCC V7 are not migrated. If you have made changes to the C
standard functions in the WinCC V7 project, you must apply these changes manually to
the TIA Portal after the migration.
Migration of texts in Spanish (international sorting) and Spanish (traditional sorting)

If the WinCC V7 project includes texts in Spanish (traditional sorting), these texts are migrated
as Spanish (Spain) in WinCC V13.
If the WinCC V7 project includes texts in Spanish (international sorting), these texts are
migrated as Spanish (Spain) in WinCC V13.
If the WinCC V7 project includes texts in Spanish (international sorting) as well as Spanish
(traditional sorting), only the texts from Spanish (traditional sorting) are migrated as Spanish
(Spain) in WinCC V13. The texts from Spanish (international sorting) are not taken into
consideration.
1.4.4.5 Engineering System
Screens and Screen Objects
Contents
product features.

Readme
1.4 WinCC Basic
Screen objects after HMI device replacement

If you upgrade a device to the new HMI device versions, you should check the screens
contained in the project. Because of the new appearance and improved operability, texts of
symbolic I/O fields may not be completely legible and may be concealed by operator controls.
Copying display objects between two projects or two devices

In Project_1 configure an alarm window in the Global Screen, for example. You copy the alarm
window and paste it in the Global Screen in Project_2.
The enabled alarm classes are partly not enabled in the alarm window after pasting.
This behavior applies to the following display objects:
● Alarm window
● Alarm indicator
● Alarm view
Display of the cross-references in the Inspector window

The Inspector window displays objects used by a screen object in the "About > Cross-
reference" tab.
A screen is open and an object selected. You are using an HMI tag at the object as process
tag.
The object and the linked HMI tag are displayed in the cross-references. All locations of use
of the object and the HMI tags are listed.
If the HMI tag is interconnected with a PLC tag or a DB tag, the locations of use of the
interconnected PLC tag or DB tag are displayed.
Event names in case of alarms in the "Info" tab of the Inspector window
In some alarms of the Inspector window the event names in the "Info" tab will deviate from the
names in the "Properties" tab.
Name in the "Properties" tab of the Inspector win‐ Name in the "Info" tab of the Inspector window
dow
Cleared ClearScreen
Loaded GenerateScreen
Enable Activate
Change Change
When a dialog is opened ONMODALBEGIN
When a dialog is closed ONMODALEND
User change PASSWORD
Screen change SCREEN
Disable Deactivate
Press Press
Outgoing Going

Readme
1.4 WinCC Basic
Name in the "Properties" tab of the Inspector win‐ Name in the "Info" tab of the Inspector window
dow
Incoming Coming
Limit "high limit error" violated AboveUpperLimit
Limit "low limit error" violated BelowLowerLimit
Click Click
Loop-in alarm LoopInAlarm
Release Release
Alarm buffer overflow OVERFLOW
Acknowledge Acknowledgement
Runtime stop Shutdown
Press key KeyDown
Release key KeyUp
Toggle ON SwitchOn
Toggle OFF SwitchOff
Value change Change value
Faceplates
Faceplates cannot be rotated or mirrored.
Tab sequence in screens with faceplates

If you have configured a tab sequence in screens with faceplates in WinCC V12 or WinCC
V12 SP1, you should check the tab sequence of these screens in WinCC V13. The tab
sequence may have been changed in both the screen and the faceplate.
Tag prefix of a screen window in WinCC Runtime Professional

The objects of the "Controls" palette do not support the tag prefix that can be configured for a
screen window.
I/O field with "decimal" display format and format pattern without "s" prefix
You have linked a process tag to an I/O field. The I/O field is assigned the "decimal" display
format.
You may select a signed or an unsigned display format.
A "Format pattern" setting without "s", e.g., "999" has the following effects:
1. You cannot set negative values using the I/O field in Runtime.
2. If the tag assumes a negative value, the I/O field generates a two's complement and a
corrupted positive value is output.

Readme
1.4 WinCC Basic
Trend view on Basic Panels

The trend view buttons are not displayed on Basic Panels. You can operate the trend view
using the function keys of the HMI device that are assigned corresponding system functions.
Grouping of screen objects

When you group screen objects in WinCC, performance problems can arise in WinCC in the
case of large nesting depths.
ActiveX and .NET controls

ActiveX and .NET controls are always positioned in the foreground in runtime.
The configuration of ActiveX and .NET controls on levels is not supported.
Use of bitmaps as icons

In Windows 8 and Windows 8.1, the use of bitmaps with a size of 48x48 pixels and a color
depth of 32 bits as icons is not supported.
Border line of rectangles

In a WinCC V7 project, you have configured a rectangle with the settings "Line weight = 1"
and "Draw insider border = yes".
You then migrate the WinCC V7 project to WinCC V12. To have the rectangle displayed
correctly, follow these steps.
1. Open the Inspector window of the rectangle.
2. Open the property list.
3. Disable "Widen border line inwards".
Border line of “Graphic I/O field" object

In WinCC V13, the dynamization of the border line of the "Graphic I/O field" object in "Two
states" mode has no effect during runtime.
Dynamization of instances of a faceplate type in a group

You are using the instance of a faceplate type in an object group. The properties of the instance
are also displayed as properties of the group. Any dynamization with tags, scripts or animations
of the group is not displayed in Runtime.
Preview in screen window

You use your own designs with shadows for screen objects. The screen objects can be
displayed in a screen window.
The shadows of the screen objects are not displayed in the preview of the screen window. The
response occurs only in the engineering system. It is displayed correctly in Runtime.

Readme
1.4 WinCC Basic
Assigning graphics to a softkey

A graphic can only be assigned to a softkey if the bottom edge of the permanent window does
not conceal the area of the softkey graphic.
Renaming a PLC in Runtime

If a PLC is connected to the PLC code viewer in WinCC Professional and Runtime is running,
changing the name of the PLC during runtime will trigger a error. Do not change the PLC name,
the IP address, or other properties of the HMI connection during runtime.
Panels and RT Advanced with device version V13: many visually different screen objects
The use of screen objects with very many visually different properties (e.g., very many different
styles) can reduce the performance of the user interface in Runtime and can increase the
amount of available memory space used. Avoid using, for example, very many different corner
radii: 0 pixel, 1 pixel, 2 pixels, 3 pixels, etc.
The use of many differently sized “Gauge” objects can have the same effect. Avoid “Gauge”
of height 48 pixels, 49 pixels, 51 pixels, etc. Instead, use sizes such as: 50 pixels, 70 pixels,
100 pixels.
Dynamization of grouped objects

For groupings with multiple nestings (group in group, faceplate in group, group in faceplate,
etc.), only the events of the outermost group and the innermost objects can be used for
dynamization with system functions. System functions that are configured at events of the
lower-level group or lower-level faceplate are not executed.
Number of characters in text fields, lists and alarm texts

The number of available characters in the text of a screen object is dynamic and depends on
the HMI device and the memory format. Control instructions and formatting are taken into
consideration when entering text data and the maximum number of characters is reduced
accordingly.
Transparency in WinCC V13

Transparent graphics can be displayed without any problems in Runtime. This is true for all
Comfort Panels and WinCC Runtime Advanced with version 13.0.0.0.
To use the transparency in a graphic view or in a graphic I/O field, the "Fill pattern" property
must be set to "Transparent" and the property "Use transparent color" must be disabled.
If the property "Use transparent color" is enabled in a device with version 13.0.0.0, the
transparency of the graphic is lost and the transparent pixels are displayed in black. We
recommend that you check the "Use transparent color" property at the points of use of
transparent graphics after upgrading existing projects to device version 13.0.0.0. If the graphics
are not displayed correctly, disable this property.

Readme
1.4 WinCC Basic
Addressing tags in the "PLC code display" object

The "PLC code display" object only supports symbolic addressing of tags. If the operand is
not addressed symbolically, the network with the operands cannot be displayed and an error
message is generated.
Characters that can be used in the property name of the screen blocks with RT Professional
Note the following rules when entering property names of the faceplates:
● The name must start with a letter.
● The name can contain alphanumeric characters and the underscore.
● The name may not contain more than 255 characters.
● Do not use any UNICODE characters (for example, Chinese characters).
Playing videos on Comfort Panels

You can play video sequences on Comfort Panels in the "Media Player" screen object. You
can find more detailed information on playing videos on the Internet under:
http://support.automation.siemens.com (http://support.automation.siemens.com/WW/view/en/
62101921) (entry ID 62101921)
Selecting the transfer protocol for the camera view

To display the screens of a network camera in the camera view, define the transfer protocol
in the properties of the screen object. Select the TCP or UDP transfer protocol depending on
your network and the type of network camera you are using. In most cases, a TCP connection
has reliable synchronization with the camera view.
Displaying SIMOTION PLC websites in the HTML browser

If the SIMOTION PLC websites are not displayed correctly in the HTML browser, insert "/basic"
after the website URL to display the websites in basic mode.
Using the optional "CamControls" from older TIA Portal versions

If you want to continue using the control "CamControl" from older versions of TIA Portal
configurations in TIA Portal V13 SP1 or newer, we highly recommend an update of the TIA
Portal project version and HMI device version to V13 SP1.
Basic Panels: Animation of object groups

Basic Panels as of device version V13 SP1 support animation of object groups that consist of
individual screen objects. Animation of nested groups is not supported, however.

Readme
1.4 WinCC Basic
RT Professional: Copying screen objects with linked user data types

After copying a screen object from a screen that uses a user data type to a screen that does
not use a user data type, the tag references in the target screen are shown with the prefix
"@NOP::". These tag references do not function during runtime if the target screen is to be
shown in a screen window. If you want the tag references to function, interconnect the target
screen temporarily to a user data type. The interconnection of the target screen to the user
data type can then be deleted afterwards.
RT Professional: User data types linked to screen objects in faceplates

If a faceplate uses an element of a user data type and a faceplate is created from this screen
object, all tag references in the faceplate are shown as "@NOP::". The tag references function
during runtime despite this, however. For the tag references to be shown correctly, no element
of a user data type should be used when creating a faceplate from an existing screen object.
Display differences between the configuration and the display on the HMI device
The display of the text configured in a screen object may be different on the HMI device due
to the display configuration. If you are using the options for automatic size adjustment in the
configuration, check the display on your HMI device in every language.
If texts that were configured with the "Fit object to contents" option cannot be displayed in full,
they are reduced slightly on the HMI device. If this reduction leads to a distorted display of
texts, disable the "Fit object to contents" option and expand the text with additional blanks.
Optionally, you can increase the width of the object or use a shorter formulation for the text.
RT Professional: S7-GRAPH overview

If the name of the S7-GRAPH data block that is interconnected at an S7-GRAPH overview
contains a period, the control does not work during runtime.
Migration and configuration of ActiveX controls

Changes to properties of ActiveX controls are only saved if the control synchronizes the
OCXState property correctly in the case of changes.
For controls such as "Microsoft Date and Time Picker Control" that do not synchronize the
OCXState property correctly, the changes are discarded after the screen is closed, during
compilation or after the migration.
Exporting and importing function keys

Function keys are synchronized during the import. If a function key is created in the global
screen and the key is empty in the screen, the corresponding function key will use the global
definition in all screens.
If you want to disable the global use of function keys after the import, define empty keys in the
screens and import the screen types in the following order: Global screen, templates, screens.
If you want to ensure when exporting the screens that the global definition of a function key is
not used by the template or by the global screen, create an empty function key in the screen.

Readme
1.4 WinCC Basic
Select the required function key in the screen, then enable the "Use global assignment"
property and disable it again.
Tags and connections
Contents
product features.
Display of deleted array elements at location of use of HMI tags

The locations of use of HMI tags, such as the process value of IO fields, are usually indicated
by the tag name. If the element of an array tag is used, then the tag name will be extended by
the index of the array element indicated in brackets.
If a used tag is no longer included in the project, then the tag name will still be displayed at the
location of use. The field will be displayed with a red background to indicate the missing tag.
If a used array element or the array tag is no longer present, then only the index of the array
element will be displayed in brackets. The tag name will not be displayed. The field is
highlighted in red. You can no longer identify the name of the associated array tag based on
the location of use in this instance.
If you do not know which array tag was linked to this location of use, then it may be necessary
to link the array element once again.
If a tag or array tag was created based on a reference, then the selected reference will be
closed automatically.
If an HMI tag is connected with an array element of a PLC tag and the PLC tag does no longer
exist in the project, then the same behavior will take place in the "HMI tags" editor.
Array tags as list entry of multiplex tags

You can use the array tags of the Char data type just like the tags of the String data type.
The use of an array tag of the Char data type as list entry of a multiplex tag in the "HMI
tags" editor is not supported.
Multiplexing tags on a Basic Panel

If you multiplex a tag with an external tag on a Basic Panel, the address is read from the PLC
in runtime during the first read cycle. The value of the address read is not available until the
second read cycle.
Runtime Advanced and Panels: Importing array elements and structure elements
Array tags and structure tags are always imported in full with all elements. The elements of
the array tags and structure tags are not filled further during import.
A new tag is created if the name of a tag corresponds to the name of an array or structure
element in the import file.

Readme
1.4 WinCC Basic
Example:
The import file contains an array tag called "Otto" with 10 array elements. The array elements
are then called Otto[1], Otto[2], for example.
If the import file contains a tag named "Otto[1]", the first element of the array tag will not be
filled. Instead, a new tag will be created in the engineering system.
Local ID of HMI connections

You cannot edit the "Local ID" value in the HMI connection properties. You need the local ID,
for example, for communication by way of AR_SEND. To enable usage of the "Local ID" for
communication, proceed as follows:
1. Open the network view in the "Devices & Networks" editor.
2. Click "Connections".
3. Select an S7 connection.
4. Select the "Add new connection" command in the shortcut menu of the PLC.
5. Click on the interface.
6. Specify the "Local ID (hex)".
7. Click "Add" and then "Close".
8. Select "Properties > General" from the partner area of the Inspector window and enter the
IP address of the HMI device for the new connection.
9. Configure the necessary raw data tags for communication in the HMI device.
Tags with the DTL data type

Tags that use the "DTL" data type element by element, can only be used as read-only.
Tag names in faceplates

Use of the "." or "@" character in names of tags in faceplate types is not permitted. Do not use
these special characters in the tag names in faceplates.
RT Professional: Tags with symbolic addressing and "Char Array" data type
Tags with symbolic addressing and the "Char Array" data type are not released for
communication of RT Professional and SIMATIC S7-1200 V3.
Array elements in WinCC

If you have connected an HMI tag with an array from a STEP 7 data block which does not start
with a low limit of 0, the array elements are mapped in WinCC to the low limit of 0.
To ensure that you do not have to rethink between the STEP 7 indices and the WinCC indices
when accessing the individual array elements, the low limits of arrays should also start at 0 in
STEP 7.

Readme
1.4 WinCC Basic
Duration of the initialization of historical data

Initialization of the archives on some storage media can take up to 5 minutes. The successful
completion of initialization is confirmed by a system message once it has been completed. If
there a lack of any storage medium for archiving when Runtime starts, the appearance of the
system message can also take up to 5 minutes.
Alarm system and alarm displays
Contents
product properties.
Displaying special characters in alarm texts

When configuring alarm texts, a fixed character set is used in the Engineering System. This
character set allows you to use numerous special characters in alarm texts.
Language-dependent fonts are used in runtime to display the texts, for example MS PGothic,
SimSun. The fonts used in runtime do not support all special characters. As a result, some
special characters are not displayed in runtime.
Use of multiplex tags in output boxes with alarm texts

It is also possible to use multiplex tags in the output boxes of alarm texts in the engineering
system. During runtime, this leads to an incorrect display of the alarm, because the use of
multiplex tags is not supported by the basic panels.
Parameters in user alarms

Contrary to the information in the online help, it is not possible to configure parameters for user
alarms.
The menu command "Properties > Properties > Alarm parameters" is not available in the
Inspector window.
Tags in alarm texts of Runtime Advanced

Tags of data type WChar or WString cannot be displayed in the alarm view in Runtime
Advanced.
Boolean tags in alarm logs

Bool type tags are recognized as 0 and -1 in the alarm log. If you use a text list that is controlled
by a tag of the type Bool in an alarm log, then add the entry for the value -1 to the corresponding
text list.

Readme
1.4 WinCC Basic
Duration of the initialization of historical data

Initialization of the archives on some storage media can take up to 5 minutes. The successful
completion of initialization is confirmed by a system message once it has been completed. If
there a lack of any storage medium for archiving when Runtime starts, the appearance of the
system message can also take up to 5 minutes.
Printing alarms in Runtime

In WinCC, only ASCII characters are supported when printing alarms directly in Runtime.
System functions
Content
product properties.
The "SimulateTag" system function on Basic Panels

If you use the system function "SimulateTag" with a short cycle time on a Basic Panel, the HMI
device may be overloaded.
Recipes
Contents
product features.
Arrays in recipe elements

If you have configured both an array as well as the elements of this array for recipe elements
of a recipe, the loading of data records aborts with the following error message: "290055: Import
of data records aborted with error"
Use either the array or just the array elements for recipe elements of a single recipe.
User administration
Contents
product features.

Readme
1.4 WinCC Basic
Encrypted connection with SIMATIC Logon V1.5 SP3

Secure encrypted communication between SIMATIC Logon and HMI operator devices is
supported as of SIMATIC Logon version V1.5 SP3 and the HMI device version V13 SP1 for
Comfort Panels, KTP Mobile Panels and RT Advanced.
HMI devices with a version V13 or earlier can only make an non-secure / non-encrypted
connection to a SIMATIC Logon server.
Authentication and certificate management in SIMATIC Logon

If you want to use a secure encrypted connection, the first time a connection is made the
SIMATIC Logon certificate is compared with the local certificate of the HMI device. Only when
the comparison has been successfully performed can a secure encrypted connection be
successfully established.
When you make a connection the first time, the compared certificate is stored under
"SimaticLogon\rejected". If you trust the certificate of the server, copy the stored certificate into
the local certificate store directory.
The certificate store is located in the following path:
● On the PC under "C:\Program Files\Siemens\CoRtHmiRtm\SimaticLogon\certs"
● On HMI panels under "\flash\simatic\SimaticLogon\certs"
Dynamic logon
In Runtime Professional, an automatic log-off time does not affect users that log on via a logon
tag.
Communication
Contents
product features.
Connection interruptions with Mitsubishi PLCs

After multiple connection interruptions, a situation may arise where all the connection
resources of the Mitsubishi PLC are in use and the connection can no longer be established.
It is recommended to check these connection resources in the PLC program of the PLC and
also to enable them again.
Limited number of possible HMI connections

An error message is displayed during compilation of a device indicating that the configuration
of the HMI connection in the "Devices & Networks" editor is invalid. The reason may be that
the maximum number of possible connections of the HMI device or PLC has been exceeded.

Readme
1.4 WinCC Basic
Check the maximum number of available connections. Consult the device manuals of the
devices you are using.
Communication by means of routing with S7 300/400

Communication of connection partners in different subnets is possible via routing with the
following connections: PROFINET, PROFIBUS, MPI.
Use of PROFINET IO with panel HMI devices

When using PROFINET IO to connect the direct keys and LEDs of HMI devices to the PLC,
you can define an offset for the address area of the inputs and outputs during configuration in
HW Config.
The following restriction applies when a PROFINET IO-capable S7-400 CPU is used with one
of the HMI devices listed below:
The offset for the start of the address area of the inputs must not be greater than the offset for
the start of the address area of the outputs.
The restriction applies to the following HMI devices:
● OP 177B
● OP 277
● Mobile Panel 177
For the configuration of the address parameters, open the PLC with the S7-400 CPU in HW
Config. Select the HMI device connected via PROFINET IO in the station window of HW Config.
A table with the properties of the HMI device is displayed at the bottom of the station window
in the detail view. Select the line containing the addresses of the HMI device in the table and
open the object properties using the shortcut menu.
Enable the "Addresses" tab in the "Object properties" dialog. Configure the offset for the inputs
under "Inputs > Start". Configure the offset for the outputs under "Outputs > Start".
Exceeding value ranges with Mitsubishi MC and Mitsubishi FX

With some data types, the Mitsubishi MC and Mitsubishi FX communication drivers do not
check whether the value of a recipe tag exceeds the value range of the PLC tags. The data
types affected are:
● 4-bit block
● 12-bit block
● 20-bit block
● 24-bit block
● 28-bit block

Readme
1.4 WinCC Basic
Coordination area pointer in an OPC connection

In principle, the coordination area pointer can be used eight times in an OPC connection. If
you have configured an OPC connection and you automatically create another OPC
connection using "Add", the coordination area pointer is only displayed once in the newly
created connection. In this case, you should change the communication driver of the
connection. If you then set OPC again as the communication driver, the coordination area
pointer can again be used eight times.
Changing IP settings and device name of a PLC in the Control Panel of the HMI device
The Control Panel is open in the "Service and Commissoning > IP-Adaptation" menu on the
HMI device. If you want to change the IP settings or the device name of a PLC, note the
following:
In the Engineering System, you need to have activated the following options in the Inspector
window of the PLC under "Properties > General > PROFINET interface > Ethernet addresses"
beforehand:
- "Set IP address using a different method" and
- "Set PROFINET device name using a different method".
HMI connections in WinCC V13

HMI connections to SIMATIC S7-1200 PLCs with firmware versions earlier than V2.0 are not
possible in WinCC V13.
Connections via PROFIBUS DP

When a connection between a PLC and an HMI device via PROFIBUS DP is interrupted and
then re-established, sporadically all other PROFIBUS DP connections in the communication
network are interrupted and re-established.
De-energize the disconnected station before reconnecting it.
"Set the IP suite (address) of the PLC in the Control Panel" with SIMATIC S7-1200 V1
The function "Set the IP suite (address) of the PLC in the Control Panel" has not been approved
for the following PLCs:
● SIMATIC S7-1200 V1
Switching a connection
A connection may be interrupted when it is switched from an HMI device to a SIMATIC
S7-300/400, to a SIMATIC S7-1500 or to a SIMATIC S7-1200 PLC.
Note the following settings in the SIMATIC S7-1500 or SIMATIC S7-1200 controllers:
● Absolute addressing of tags
● The "Disable PUT-GET communication" option must be selected
● The "Complete protection" protection level may not be set

Readme
1.4 WinCC Basic
Raw data communication in redundant projects

Simatic.NET, Named Connections and various communication blocks, such as BSEND/BRCV,
for example, can only be used to a limited extent in a redundantly configured PC station
because the connection parameters for the redundant partner server cannot be configured.
Non-integrated connection to a SIMATIC S7-1500 software controller

A non-integrated connection between an HMI device and a SIMATIC S7-1500 software
controller is not supported in WinCC.
1.4.4.6 Runtime
Notes on operation in Runtime
Contents
product features.
Focus in Runtime
If you have configured a low-contrast combination of focus color and border color in a V12
project, the focus may no longer be identifiable after changing the HMI device version in
Runtime. Change one of the two colors.
Language behavior - Layout of on-screen keyboard

The layout of the on-screen keyboard is not switched when the runtime language changes.
Tag values exceed the maximum length

You enter a character string in a string tag via an I/O field. If the character string exceeds the
configured number of tags, the character string will be shortened to the configured length.
Empty alarm texts

Runtime is running with a project. The project is saved on a network drive.
In the event of interruptions to the network drive connection, Runtime may attempt to load
alarm texts from the network drive.
In the event of disconnection, the alarm window or the alarm view remains empty.
To avoid this, copy the project to a local drive before the starting the project in Runtime.

Readme
1.4 WinCC Basic
Complete download in Service mode

If you need to perform a "complete download" to the OS in Service mode from the engineering
station, Runtime automatically stops and then starts again.
The project is then no longer in Service mode.
In this state, the power supply is interrupted and WinCC Runtime no longer starts automatically
on the OS.
Remedy:
1. Switch the project manually to Service mode after you have performed the "complete
download".
2. Close the project manually.
3. Enable Service mode.
4. Start Runtime again using the surrogate icon in the taskbar.
Slow reaction of SmartServer

The following programs may start and respond very slowly under Windows 7 and Windows
2008 servers:
● HMI TouchInputPC
● SmartServer: <Ctrl+Alt+Del> shortcut in the logon dialog
The delay is caused by the callback for the Internet certificate validation.
Remedy:
You can find the following files
on the product DVD under:
Support\Windows7\CRL_Check or CD_RT\ Support\Windows7\CRL_Check\:
● DisableCRLCheck_LocalSystem.cmd
● DisableCRLCheck_CurrentUser.cmd
1. Run the "DisableCRLCheck_LocalSystem.cmd" file with administrator rights. Select the
command "Run as administrator" from the shortcut menu of the file.
2. Reboot the PC.
If the problem persists, follow these steps:
1. Double-click the file and run the "DisableCRLCheck_CurrentUser.cmd" file with user rights.
2. Reboot the PC.
Note
The callback for the certificate validation is disabled for all users or PCs. To restore the
original state, perform the following files:
● RestoreDefaults_LocalSystem.cmd
● RestoreDefaults_CurrentUser.cmd
You can find the files in the following directory of the product DVD:
● Support\Windows7\CRL_Check or CD_RT\Support\Windows7\CRL_Check\

Readme
1.4 WinCC Basic
Starting Runtime
Only WinCC Runtime V13 can be started in TIA Portal V13. WinCC Runtime V11.02, V12 or
V13 can be simulated in TIA Portal V13.
Avoiding corrupt files during power failure

If a power failure occurs in Windows systems while the WinCC system is active, files may be
corrupt or destroyed. Operation with the NTFS file system provides better security.
Secure, continuous operation is only ensured by using an uninterruptible power supply (UPS).
Blocking task switching on Windows 7 and Windows 8.x

To use the "Block task switching" option on a Runtime PC, disable the Aero theme in Windows
7 and Windows 8.x. To disable the Aero theme, right-click on the Desktop and select
"Personalize". In the "Personalization" menu, select the designs "Windows Basic" or "Windows
- Classic".
Notes on operation of panels in Runtime
Contents
product features.
License transfer via S7USB

You always need to run WinCC to transfer a license to a panel via S7USB.
Transferring licenses to a panel on 64-bit operating systems

If you are running a 64-bit operating system and the "Edit > Connect target systems > Connect
HMI device" menu command is not available in Automation License Manager, open command
line input and run the following command with administrator rights:
"%WINDIR%\system32\RegSvr32.exe" "%CommonProgramFiles%\siemens\AlmPanelPlugin
\ALMPanelParam.dll"
Using the mouse wheel in Runtime

The use of the mouse wheel in Runtime is not supported on all panels.
Basic Panels, OP73, OP77A and TP177A: Displaying texts in runtime

The default font selected in the "Runtime settings > Languages & font" editor has an effect on
the display of texts in runtime.
Text entries may be truncated if you selected an unfavorable font size or style.

Readme
1.4 WinCC Basic
This setting possibly has an effect on the following text entries:

● Tooltips
● long alarm text
● text in the dialogs
Basic Panels: Connections to S7-1200 and S7-1500 with Backup/Restore

If you use the "Backup/Restore" function, a maximum of two connections from Basic Panels
to the controllers are possible at any given time.
● SIMATIC S7-1200
● SIMATIC S7-1500
Basic Panels: Backup on the memory card of the PLC

Create the backup file "A.psb" on the memory card of the PLC. An error, for example a
connection break, occurs when creating the backup.
This will create a corrupt file on the memory card of the PLC. Such a file has "~$" as prefix.
Delete the file with the prefix "~$" if you want to save a backup again under the same name
"A.psb".
Basic Panels: Panel Data Storage and S7-1500F

The "Panel Data Storage" PDS function cannot be used on Basic Panels in conjunction with
S7-1500F when the password for the protection level "Full access incl. fail-safe" is used.
"Panel Data Storage" function on Basic Panels

The "Panel Data Storage" (PDS) function provided by Basic Panels is only supported by
SIMATIC S7-1200 as of firmware V4.0 and SIMATIC S7-1500. For the PDS function, the panel
must be connected directly with the CPU and must not be connected via the CP.
1.4.4.7 HMI devices
Notes on HMI devices
Contents
product features.
If the PC goes into standby or hibernate mode while the transfer is in progress, the panel status
after interruption of the transfer is not defined.

Readme
1.4 WinCC Basic
Multi-key operation
Unintentional actions can be triggered by multi-key operation:
● When you are using a key device, you cannot press more than two function keys at the
same time.
● When you are using a touch device, a standard PC or a panel PC, you can only press one
function key or button at the same time.
TS Adapter with Ethernet interface

If an HMI device is connected via Ethernet and a TS adapter, it can not be reset to factory
settings.
Simulation of the Basic Panels

Use an output field in an alarm text to output an external tag. The content of the output field
will always be displayed with "0" during simulation.
Simulation with real PLC connection

The access point used by the simulation is independent from the settings of the engineering
system and can only be altered in the Control Panel with the "Setting PG/PC Interface" tool.
If the PLC connection is terminated right after the start of the simulation with alarm 140001,
you should check the access point used by the simulation with "Setting PG/PC Interface".
1. Double-click "Setting PG/PC Interface" in the Control Panel. A dialog opens.
2. Select" "S7ONLINE" in the "Access point of application" field as standard for HMI.
3. Select the interface in the "Interface Parameter Assignment Used" area.
4. Exit the dialog "Setting PG/PC Interface" with OK
Loading of projects without recipe data records

You are using recipes in a project. You transfer the project to a Basic Panel without recipe
data records.
You may encounter inconsistencies if you have altered the structure of the recipe in the
engineering system and the device already held recipe data records.
Check the consistency of the data records in this case. The device will not issue a note for all
structural changes.
Floating point numbers on MP 277, MP 377, TP 177B 4'' and CP4

Only floating point numbers in the range from 10-293 ... 10+307 are displayed correctly on the
HMI devices MP 277, MP 377, TP 177B 4'' and CP4. If the tag value is outside this range, it
is displayed as 0.

Readme
1.4 WinCC Basic
Mobile Panels V2
If you use Mobile Panels V2 in a project, it is not possible to open the project with WinCC V11
SP1. This affects projects with the following devices:
● Mobile Panel 277F IWLAN (RFID Tag)
● Mobile Panel 277F IWLAN V2
● Mobile Panel 277 IWLAN V2
"Zone ID/Connection point ID" tag of a Mobile Panel 277 IWLAN V2

The tag used for the "Zone ID/Connection point ID" must be of data type INT for Mobile Panel
277 IWLAN V2 devices. Adapt this data type if necessary when migrating a project.
HMI devices with operating system Windows CE 5.0 or higher

Owing to a modified client-server communication security setting, the time difference between
the HMI device (client) and PC (server) must not exceed 1 day. If you back up recipe data from
the HMI device on a network drive, for example, make sure that the time is set correctly on the
PC (server) and the HMI device (client).
HMI devices with high communication load

S7 Diagnostics should be enabled if a Panel is assigned many connections to PLCs or other
HMI devices. Otherwise, you will risk overload on the Panel.
Device replacement in the engineering system

In the engineering system, you replace a device with configured LED keys with a device without
LED keys. Runtime start fails after you have transferred the project data to the device.
For this reason, delete the LED key configuration before you replace the device.
Restrictions for the HMI device, MP 377 15" Touch daylight readable
The following functions are not supported in WinCC V12 for the MP 377 15" Touch daylight
readable HMI device:
● Option: Sm@rtServer
● System function: SetAndGetBrightness
● Direct keys
Upgrading Basic Panels to WinCC V13

Before you upgrade Basic Panels from version V12 to version V13, transfer the image of the
V12 SP2 Update 5 or higher to the devices.
In the "SIMATIC ProSave [OS Update]" dialog, select the setting "Reset to factory settings".
In this way, you always start a functional update of the image.

Readme
1.4 WinCC Basic
Affected devices:
● KP300 Basic mono PN
● KP400 Basic color PN
● KTP400 Basic color PN
Connection switch in the Control Panel with Basic Panels

If you use the "Override protected connection information" function, the following restriction
applies:
You cannot perform a connection switch in the Control Panel of a Basic Panel from a PLC
without a protection level to a PLC with a "Complete protection" level.
2nd generation Basic Panels: Choosing a USB port

If you are not using a USB hub, select the USB port USB_X60.1 as storage path.
KTP400F Mobile
KTP400F Mobile is available as Hardware Support Package (HSP) for version V13 SP1.
Mobile Panels 277F IWLAN (RFID Tag): F_DB_STATES

The block F_DB_STATES is no longer delivered with WinCC V13 SP1. The block
F_DB_STATES serves only for data exchange. You can configure a block to replicate the
function of the F_DB_STATES, however. Note the description of the F_DB_STATES in the
operating instructions of your HMI device or in the information system.
F_FB_KTP_Mobile and F_FB_KTP_RNG

The fail-safe function blocks F_FB_KTP_Mobile and F_FB_KTP_RNG are not contained in the
software WinCC V13 SP1. The function blocks will be part of the WinCC V13 SP1 Update for
the Mobile Panels 2nd generation.
Mobile Panels 277F IWLAN
Mobile Panels 277F IWLAN are not released for use with CPUs of the type S7-1500F with
WinCC V13 SP1.
Mobile Panels 277F IWLAN are not released for use with CPs in connection with CPUs of the
type S7-400F with WinCC V13 SP1.
Affected MLFBs: 6AV6645-0EB01-0AX1, 6AV6645-0EC01-0AX1, 6AV6645-0EF01-0AX1,

6AV6645-0GB01-0AX1, 6AV6645-0GC01-0AX1, 6AV6645-0GF01-0AX1.

Readme
1.4 WinCC Basic

Installation 2
2.1 Notes on the installation
Contents
Automated Installation
A description of automated installation is available on the product DVD in the directory
"Documents\Readme\<Language directory>".
Use of the same versions of TIA Portal products during installation

When installing different TIA Portal products, make sure that you use the same versions of
service packs and updates for the installation. For example, if you have installed SP1 for STEP
7 V13, you must also install SP1 for WinCC V13. The service packs and updates must be
installed for all products at the same time. Do not start the TIA Portal until all products have
been upgraded.
You can download the service packs from the Internet under Siemens Industry online support
(http://support.automation.siemens.com/WW/llisapi.dll?aktprim=99&lang=en&referer=
%2fWW
%2f&func=cslib.csinfo2&siteid=csius&extranet=standard&viewreg=WW&groupid=4000002).
Target directory of the installation

Do not use any UNICODE characters (for example, Chinese characters) in the installation path.
Use of antivirus programs

During the installation, read and write access to already installed files is necessary. Some
antivirus programs block this access. We therefore recommend that you disable antivirus
programs during installation of the TIA Portal and enable them again afterwards.
Compatibility with V12 SP1 and V13

Empty projects from previous versions are installed in the installation directory under ..
\<INSTALLDIR>\Sample Projects to allow the current TIA Portal to be opened in compatibility
mode. These projects must be copied to a local directory with full access before they can be
used. For more information on this, refer to FAQ ID 82169157.

Installation
2.2 System requirements for installation
FAQs on the TIA Portal

FAQs on the TIA Portal are available under FAQs (http://support.automation.siemens.com/
WW/view/en/28919804/133000).
2.2.1 Notes on licenses
Availability of licenses
The licenses for the products of the TIA Portal are usually supplied on an installation data
medium and transferred automatically by the Automation Licence Manager during the
installation process of the TIA Portal.
Before you uninstall the TIA Portal, you must transfer and back up the licenses still required.
Use the Automation License Manager for this purpose.
Provision of the Automation License Manager

The Automation License Manager is supplied on the installation data medium and is
transferred automatically during the installation process.
If you uninstall the TIA Portal, the Automation License Manager remains installed on your
system.
Working with the Automation License Manager

The Automation License Manager is a product of Siemens AG, which is used for handling
license keys (technical representatives of licenses).
Software products that require license keys for operation, such as the TIA Portal, register the
need for license keys automatically with the Automation License Manager . If the Automation
License Manager finds a valid license key for this software, the software can be used according
to the license usage terms associated with this license key.
Note
For additional information on how to manage your licenses with the Automation License
Manager , refer to the documentation supplied with the Automation License Manager .
See also
Notes on the system requirements (Page 95)
Starting installation (Page 114)

Installation
Displaying the installed software (Page 119)

Modifying or updating installed products (Page 120)
Repairing installed products (Page 121)
Starting to uninstall (Page 123)
Installation log (Page 113)
2.2.2 Notes on the system requirements
System requirements for individual products

The system requirements may differ depending on the products you want to install. You should
therefore check the individual system requirements of your products.
If you want to install several products, make sure that your system meets the demands of the
product with the highest requirements.
Displaying PDF files

To be able to read the supplied PDF files, you require a PDF reader that is compatible with
PDF 1.7 e.g. Adobe (R) Reader version 9.
Displaying the Welcome Tour

You need the Adobe (R) Flash Player Version 9 or higher to start the Welcome Tour for the
TIA Portal.
See also
Notes on licenses (Page 94)

Installation
2.2.3 System requirements STEP 7 Basic
2.2.3.1 Licensing of STEP 7
Introduction
You require a License Key to license the following STEP 7 editions:
● STEP 7 Basic
● STEP 7 Professional
You can install the corresponding License Key when you are installing STEP 7 or transfer it
using the Automation License Manager after the installation has been completed.
Licenses for STEP 7

The following licenses with the corresponding license keys are available:
● STEP 7 Basic
● STEP 7 Professional
● STEP 7 Professional Combo

Installation
Validity of license keys for older versions of STEP 7

With a valid License Key for V13.x of STEP 7 Professional and STEP 7 Professional Combo,
you can also operate older versions of STEP 7 without restrictions. The following table provides
more detailed information about this:
Edition License Valid for

STEP 7 Basic V13.x STEP 7 Basic ● STEP 7 Basic V13.x
● STEP 7 Basic V12.x
● STEP 7 Basic V10.5
STEP 7 Professional STEP 7 Professional ● STEP 7 Professional V13.x
V13.x ● STEP 7 Professional V12.x
● STEP 7 Professional V11.x
STEP 7 Professional STEP 7 Professional Combo ● STEP 7 Professional V13.x
V13.x ● STEP 7 Professional V12.x
● STEP 7 Professional V11.x
● STEP 7 V5.5
● STEP 7 V5.4
● STEP 7 Professional 2010
● STEP 7 Professional 2006
Starting without a valid license key

If you start an edition of STEP 7 without a valid License Key , the system alerts you that you
are working in non-licensed mode. You have the one-time option of activating a Trial License.
However, this license is valid for a limited period only and expires after 21 days.
When the Trial License expires, the following scenarios can occur:
● STEP 7 has never been licensed on the PC in question:
– Operations requiring a license can no longer be performed in STEP 7.
● STEP 7 was already licensed on the PC in question:
– A window requiring acknowledgment presents an alert for non-licensed mode every 10
minutes and for every action requiring a license.

Installation
License requirements for simulation

You do not require additional licenses when you use the menu command "Online > Simulation"
to start the simulation in STEP 7.
If the following conditions are met, the appropriate licenses for the edition of STEP 7 you have
installed are also required for the simulation.
● The engineering station is connected to a PLC.
● The connection to the PLC is configured and active.
See also
Handling licenses and license keys (Page 98)
2.2.3.2 Handling licenses and license keys
Introduction
In each case, you require a valid License Key to use STEP 7 Basic and STEP 7 Professional.
Installing license keys

When you install STEP 7 Basic, the License Key is installed automatically during setup. When
you install STEP 7 Professional you will be prompted at the end of the setup to transfer the
license from the supplied storage medium to your PC.
If you want to install additional License Keys, you have to use the Automation License Manager
to do this.
When you install a license, the associated license key is removed from the license key storage
location.
NOTICE
Destruction of license keys by copying
It is not possible to copy a License Key. The copy protection prevents the license keys from
being copied. If you attempt to copy a License Key this will be destroyed.
Uninstalling license keys

License keys are always uninstalled using the Automation License Manager. You uninstall a
License Key in the following cases:
● When backing up data.
● If you no longer require the license.
You can then use a valid license on another PC or HMI device.

Installation
Data backup
When backing up data on the HMI device or creating a backup during device replacement,
remove the License Keys on the HMI device. To do this, open the Automation License Manager
and back up the uninstalled license key to another storage location.
NOTICE
Destruction of license keys on PCs
Start by removing all license keys in the following situations:
● Before you format the hard disk.
● Before you compress the hard disk.
● Before you restore the hard disk.
● Before you start an optimization program that moves fixed blocks.
● Before you install a new operating system.
Read the description of Automation License Manager ("Start > Siemens Automation >
Documentation"). Observe all warnings and notices.
On PC-based HMI devices and on non-PC-based HMI devices where Automation License
Manager is used, the license key storage location may contain multiple license keys. This
capability means you can store multiple licenses of the same type at one location. Save all
license keys of an HMI device to the same storage location.
NOTICE
Always keep the original storage location of the license keys.
Invalid license after time zone change

The installed license no longer functions in the following case.
● If you change the time zone on a PC as follows:
From a time based on a complete hour to a time not based on a complete hour.
Example: You change the time zone from GMT +3:00 to GMT +3:30.
To avoid this inconvenience, uninstall the license key using the Automation License Manager
under the time zone setting that was set when the license key was installed.
This behavior does not apply to the Trial License.
Defective license
A license is defective in the following cases:
● If the license key is no longer accessible at the storage location.
● If the license key disappears during its transfer to the destination drive.
You can use the Automation License Manager to repair the defective license. To do this, use
the "Restore" function or the "Restore wizard" of the Automation License Manager. To perform
this restore operation you must contact Customer Support.

Installation
You can find more detailed information on the Internet: http://support.automation.siemens.com

(http://support.automation.siemens.com/WW/llisapi.dll?aktprim=99&lang=en&referer=
%2fWW
%2f&func=cslib.csinfo2&siteid=csius&extranet=standard&viewreg=WW&groupid=4000002)
See also
Licensing of STEP 7 (Page 96)
2.2.3.3 Software and hardware requirements STEP 7
System requirements for installation

The following table shows the minimum software and hardware requirements for installation
of the "SIMATIC STEP 7 Basic" software package:
Hardware/software Requirement
Processor Intel® Celeron® Dual Core 2.2 GHz (Ivy/Sandy Bridge)
RAM 4 GB
Available hard disk space 8 GB
Operating systems * Windows 7 (32-bit)
● Windows 7 Home Premium SP1
● Windows 7 Professional SP1
● Windows 7 Enterprise SP1
● Windows 7 Ultimate SP1
Windows 7 (64-bit)
Windows 8.1 (64-bit)
● Windows 8.1
● Windows 8.1 Professional
● Windows 8.1 Enterprise
Windows 10 (64-bit)
● Windows 10 Home Version 1607
● Windows 10 Professional Version 1607
● Windows 10 Enterprise Version 1607
● Windows 10 Enterprise 2016 LTSB
Windows Server (64-bit)
● Windows Server 2012 R2 StdE (full installation)
● Windows Server 2016 Standard (full installation)
Screen resolution 15.6" wide screen display (1024 x 768)

Installation
* For more detailed information on operating systems, refer to the help on Microsoft Windows
or the Microsoft homepage.
Recommended software and hardware requirements

The following table shows the recommended software and hardware for the operation of STEP
7 Basic.
Computer From SIMATIC FIELD PG M4 PREMIUM (or similar PC)
Processor From Intel® Core™ i5-3320M 3.3 GHz
RAM 8 GB or more
Hard disk 300 GB SSD
Monitor 15.6" Wide Screen Display (1920 x 1080)
● Windows 8.1
Windows 10 (64-bit)
● Windows Server 2012 R2 StdE (full installation)
* For more detailed information on operating systems, refer to the help on Microsoft Windows
or the Microsoft homepage
Supported virtualization platforms

You can install the "SIMATIC STEP 7 Basic" software package on a virtual machine. For this
purpose, use one of the following virtualization platforms in the specified version or a newer
version:
● VMware vSphere Hypervisor (ESXi) 6.0
● VMware Workstation 12.5

Installation
● VMware Player 12.5

● Microsoft Hyper-V Server 2016
The following operating systems are recommended as host operating systems for these
virtualization platforms:
Operating system VMware vSphere Hyper‐ VMware Worksta‐ VMware Player Microsoft Hyper-
visor (ESXi) tion V
Windows Server 2016 Standard (full - - - x
installation, 64-bit)
Windows 7 Professional SP1 x x x -
Windows 7 Enterprise SP1 x x x -
Windows 7 Ultimate SP1 x x x -
Windows 10 Professional Version x x x -
1607
Windows 10 Enterprise Version x x x -
1607
Windows 10 Enterprise 2016 LTSB x x x -
x: Can be used as the host operating system

-: Cannot be used as the host operating system
The following guest operating systems are recommended for installing "SIMATIC STEP 7
Basic" within the selected virtualization platform:
Operating system VMware vSphere Hyper‐ VMware Worksta‐ VMware Player Microsoft Hyper-
visor (ESXi) tion V
Windows Server 2008 R2 StdE SP1 - - - x
(full installation, 64-bit)
Windows Server 2012 R2 StdE (full - - - x
Windows Server 2016 Standard (full - - - x
Windows 7 Professional SP1 x x x x
Windows 7 Enterprise SP1 x x x x
Windows 7 Ultimate SP1 x x x x
Windows 10 Professional Version x x x x
1607
Windows 10 Enterprise Version x x x x
1607
Windows 10 Enterprise 2016 LTSB x x x x
x: Can be used as the guest operating system

-: Cannot be used as the guest operating system

Installation
Note
● The same hardware requirements apply to the host operating system as for the respective
TIA products.
● The plant operator must ensure that sufficient system resources are available for the host
operating systems.
● The hardware certified by the manufacturers is recommended for the use of HyperV server
and ESXi.
● When you use Microsoft Hyper-V, accessible stations cannot be displayed.
Supported security programs

The following security programs are compatible with "SIMATIC STEP 7 Basic":
● Antivirus programs:
– Symantec Endpoint Protection 12.1
– Trend Micro Office Scan Corporate Edition 10.6
– McAfee VirusScan Enterprise 8.8
– Kaspersky Anti-Virus 2014
– Windows Defender (as of Windows 8.1)
– Safety Guard 360
Encryption software:
– Microsoft Bitlocker
● Host-based Intrusion Detection System:
– McAfee Application Control 6.0

Installation
2.2.4 System requirement for WinCC Basic
2.2.4.1 Software and hardware requirements
Introduction
Specific requirements for the operating system and software configuration must be met for the
installation.
Note
WinCC is generally authorized for use in a domain or workgroup.
However, be aware that domain group policies and restrictions of the domain may hinder the
installation. If this happens, remove the computer from the domain prior to installing Microsoft
Message Queuing, Microsoft SQL Server and WinCC. Log onto the computer in question
locally with administrative rights. Then perform the installation. After successful installation,
you can enter the WinCC computer back into the domain. If the domain group policies and
restrictions of the domain do not impede the installation, the computer need not be removed
from the domain during the installation.
Be aware that domain group policies and restrictions of the domain may also hinder operation.
If you cannot avoid these restrictions, run the WinCC computer in a workgroup.
Consult with the domain administrator if needed.
Installation requirements
The following table shows the minimum software and hardware requirements that have to be
met for the installation of the "SIMATIC WinCC Basic" software package:
Processor type Intel® Celeron® Dual Core 2.2 GHz (Ivy/Sandy Bridge)
RAM 4 GB
Free hard disk space 8 GB

Installation
Windows 7 (64-bit)
● Windows 8.1
Windows 10 (64-bit)
● Windows Server 2012 R2 Standard Edition (full installation)
Screen resolution 1024 x 768
Network Ethernet 10 Mbps or faster
Optical drive DVD-ROM
Software Microsoft .NET Framework 4.6.2
* For additional information on the operating systems, refer to the Microsoft Windows help or
the Microsoft homepage.
Simultaneously opening multiple instances of WinCC on a configuration PC can also increase
the hardware capacity required.
Note
"Aero Glass Style" of Microsoft Windows 7
A powerful graphics card is required for "Aero Glass Style". It requires DirectX9 capabilities
and 128 MB of dedicated graphics memory.
The performance of the architecture of the graphics system can significantly influence the
performance of WinCC.

Installation
Recommended hardware
The following table shows the recommended hardware for the operation of SIMATIC WinCC.
Hardware Requirement
Computer SIMATIC FIELD PG M4 PREMIUM or higher (or comparable PC)
Processor Intel® Core™ i5-3320M 3.3 GHz or higher
RAM 8 GB or more
Hard disk 300 GB SSD
Monitor 15.6" Wide Screen Display (1024 x 768)
Optical drive DL MULTISTANDARD DVD RW
Supported virtualization platforms

You can install the "SIMATIC WinCC Basic" software package on a virtual machine. To do
this, use one of the following virtualization platforms:
● VMware vSphere Hypervisor (ESXi) 6.0
● VMware Workstation 12.5
● VMware Player 12.5
● Microsoft Hyper-V Server 2016
All released operating systems can be used as host operating systems on a virtualization
platform.
Note
● The same hardware requirements apply to the guest operating system as to the respective
TIA products.
● The plant operator must provide sufficient system resources for the guest operating
systems.
● The hardware certified by the manufacturers is recommended for the use of HyperV server
and ESXi.

Installation
Supported security programs

The following security programs are compatible with "SIMATIC WinCC Basic":
● Virus scanners:
– Symantec Endpoint Protection 12.1
– Trend Micro Office Scan Corporate Edition 10.6
– McAfee VirusScan Enterprise 8.8
– Kaspersky Anti-Virus 2014
– Windows Defender (Windows 8.1 and higher)
– Safety Guard 360
● Encryption software:
– Microsoft Bitlocker
● Host-based Intrusion Detection System:
– McAfee Application Control 6.0
Installing Microsoft .Net Framework

You will be prompted to install the required .Net Framework version if this cannot be performed
by the WinCC installation. A restart may be necessary after installation of .Net Framework.
Security settings during installation

When you install WinCC V13 SP2, security settings are changed in your operating system.
The security settings in question are listed during the installation.
You must confirm the changes to the security settings.
If you make changes to your operating system after the installation, the changes to the security
settings made by the installation of the TIA Portal could be changed.
You can restore the changes to the security settings made by the installation of the TIA Portal:
"Start > All Programs > Siemens Automation > Security Controller > Restore settings".
See also
Licensing of WinCC Engineering System (Page 108)
http://support.microsoft.com/kb/917607 (http://support.microsoft.com/kb/917607)

Installation
2.2.4.2 Parallel installation
Parallel installations in TIA Portal V13

You will be prevented from starting the TIA Portal if you perform a non-permitted parallel
installation of STEP 7 and WinCC. The following parallel installations are permitted in the TIA
Portal:
● STEP 7 V13 and WinCC V13
A dialog opens during installation to inform you of any inconsistencies in your parallel
installation. The following parallel installations are permitted:
● WinCC V13 and RT Advanced V13
● WinCC V13 and RT Professional V13
The engineering system and Runtime must always be of the same version after an installation.
Parallel installation of WinCC V13 and other SIMATIC HMI products

Parallel installation of WinCC V13 and versions of WinCC flexible earlier than WinCC flexible
2008 SP1 is not allowed.
Parallel installation of WinCC V13 with versions of WinCC earlier than WinCC V7.0 SP2 is not
allowed. Parallel installation of WinCC V13 with WinCC V7.0 SP2 or WinCC V7.0 SP3 is not
allowed for:
● WinCC V 13 Professional
● WinCC V 13 Runtime Professional
Parallel use
If the term "Combo" appears in the name or license key of the software after installation, the
use of the following products/versions is permitted in accordance with paragraph 1.6 of the
General Terms and Conditions (see also setup text):
● With license for "WinCC V13 Comfort Combo": WinCC flexible 2008 Standard
● With license for "WinCC V13 Advanced Combo": WinCC flexible 2008 Advanced
2.2.4.3 Licenses and Powerpacks
Licensing of WinCC Engineering System

You require a license key for the following:
● WinCC Engineering System, for example, WinCC Professional
● Add-ons for WinCC Engineering System
You can install the license key during the installation of WinCC. You transfer licenses for the
WinCC add-ons after installation with the Automation License Manager.

Installation
Starting without a valid license key

If you start WinCC without a valid license, the system alerts you that you are working in non-
licensed mode. You have the one-time option of activating a trial license. The trial license for
Engineering editions WinCC Basic, Comfort/Advanced, and Professional expires after 21 days.
When the trial license has expired, the following scenarios may occur:
● WinCC was never licensed on the PC in question.
– Operations requiring a license can no longer be performed in WinCC.
● WinCC was already licensed on the PC in question.
– Non-licensed mode is indicated every 10 minutes and at every action requiring a license
by a window, which you must acknowledge.
License requirements for simulation

When you want to start simulation in WinCC using the "Online > Simulation> With tag simulator"
menu command, you do not need licenses for WinCC Runtime or for add-ons that require a
license.
If the following conditions are met, you will need the appropriate licenses for WinCC Runtime
and add-ons that require a license even for simulation:
● The engineering station is connected to a PLC.
● The connection to the PLC is configured and active.
You start the simulation with the "Online > Simulation > Start" menu command.
Validity of license keys for older versions of WinCC

With a valid license key for WinCC Basic V13.x, you can also operate older versions of WinCC
without restrictions:
Edition License Validity

WinCC Basic V13.x WinCC Basic ● WinCC Basic V11.0 SP2
● WinCC Basic V12.0
● WinCC Basic V13.0
See also
Software and hardware requirements (Page 104)
Licensing of HMI devices (Page 109)
Working with license keys (Page 110)
Licensing of HMI devices

Non-PC-based HMI devices are always equipped with "Runtime licenses". A license key is not
required for runtime operation.

Installation
A license may be required for an add-on for non-PC-based HMI devices. The license key of
the respective license always activates one add-on for use.
License key
In order to license non-PC-based HMI devices with license keys, the
"SIMATIC HMI License Manager Panel Plugin" add-on is needed.
WinCC Setup installs this add-on by default. You open the License Manager Panel Plugin in
the Automation License Manager with the "Edit > Connect Target System > Connect HMI
Device" menu command.
If WinCC is not installed, an installation of ProSave 7.2 or higher is required.
Note
Further information on license handling can be found in the Automation License Manager help.
Note
Verify that the current version of the operating system (or higher) is installed on the HMI device
before you start licensing. If necessary, update the operating system using ProSave.
Non-licensed mode
Runtime add-ons can be used for a short time without restrictions without a valid license. Non-
licensed mode is indicated every 10 minutes by a window, which you must acknowledge.
See also
Working with license keys
Introduction
You transfer a license key to the HMI device in the following cases:
● To use the WinCC engineering system
● To operate WinCC Runtime
● To use add-ons for WinCC Runtime on PC-based HMI devices
● To use add-ons on non-PC-based HMI devices
You transfer a license key from the HMI device in the following cases:
● When backing up data
● If you no longer require the license
You can then use this license on another PC or HMI device.

Installation
When you transfer a license to an HMI device, the associated license key is removed from the
license key storage location.
Note
A license key cannot be copied. The copy protection employed prevents the license keys from
being copied.
Data backup
You transfer the license keys from the HMI device for data backup on the HMI device or as a
backup for device replacement.
You use the Automation License Manager to back up license keys from an HMI device to the
storage area of the license keys.
NOTICE
Destruction of license keys on non-PC-based HMI devices
License keys transferred as a result of backup/restore operations are destroyed in the case
of the following HMI devices.
● 270 series
● 370 series
Carry out the following before beginning restoring:
● Use the Automation License Manager and ProSave to check whether license keys are on
the HMI device.
● Transfer the license keys present on the HMI device to a storage location.
After restoring has been carried out, transfer the license keys back to the HMI device.
NOTICE
Destruction of license keys on PCs
Transfer all license keys to a storage location in the following cases:
● Before you format the hard disk
● Before you compress the hard disk
● Before you restore the hard disk
● Starting an optimization program that moves fixed blocks
● Installing a new operating system
Read the description of Automation License Manager ("Start > Simatic Automation >
Documentation"). Observe all warnings and notices.
The license key storage location on PC-based HMI devices and on non-PC-based HMI devices
where Automation License Manager is used may contain multiple license keys. This capability

Installation
means you can store multiple licenses of the same type at one location. For the backup, use
a single storage location for all license keys present on an HMI device.
Note
Always keep the original storage location of the license keys.
Invalid license after time zone change

The transferred license no longer functions in the following case.
● If you change the time zone on a WinCC PC as follows:
– From a time based on a complete hour to a time not based on a complete hour.
Example: You change the time zone from GMT +3:00 to GMT +3:30.
To work around this, transfer the license key from the HMI device with a time zone setting that
was set when the license key was transferred to the HMI device.
Example:
You transferred the license key to the HMI device with a time zone setting based on a full hour.
Then, also transfer the license key from the HMI device with a time zone setting based on a
full hour.
This behavior does not apply to the trial license.
Defective license
A license is defective in the following cases:
● If the license key is no longer accessible at the storage area.
● If the license key disappears during its transfer to the destination drive.
Note
Resetting of the system date to an earlier time causes all licenses to be become defective.
You can use the Automation License Manager to repair the defective license. Use the "Restore"
function or the "Restore Wizard" of the Automation License Manager for this purpose. You
must contact Customer Support in order to restore the license. For additional information see:
http://support.automation.siemens.com (http://support.automation.siemens.com)
Note
The Runtime software can also be operated without errors if the license is missing or defective.
The system alerts you at brief intervals that you are working in non-licensed mode.

Installation
2.3 Installation log
Note
If you start the WinCC Engineering System without a valid license key, the system alerts you
that you are working in non-licensed mode. You have the one-time option of activating a trial
license. The trial license expires after 21 days.
When the trial license has expired, the following scenarios may occur:
● WinCC was never licensed on the PC in question.
WinCC can no longer be started.
● WinCC was already licensed on the PC in question.
WinCC can be started. Non-licensed mode is indicated every 10 minutes by a window,
which you must acknowledge.
See also
2.3 Installation log
Function of the installation log

The progress during the following installation processes is logged in a file:
● Installing products
● Modifying or updating already installed products
● Repairing an existing installation
● Uninstalling products
If errors occur during the installation process or warnings are issued, these can be evaluated
with the help of the log file. You can do this yourself or contact product support.
Installation logs storage location

The log file is the most recent file with the file extension ".log" and the name of which that starts
with "SIA".
The location of the log file is stored in the environment variable "%autinstlog%". You can enter
this environment variable in the address bar of Windows Explorer to open the folder with the
log files. Alternatively, you can navigate to the corresponding directory by entering "CD
%autinstlog%" in the command line.
The storage location is dependent on the operating system, e.g. "C:\ProgramData\Siemens
\Automation\Logfiles\Setup" in English-language Windows.

Installation
2.4 Starting installation
Setup_Report (CAB file)

To make it easier to provide Product Support with all necessary files, an archive file that
contains the installation log and all other required files is saved in CAB format. This log can
be found at "%autinstlog%\Reports\Setup_report.cab". Send this CAB file to Product Support
if you need assistance with installation. With this information, Product Support can determine
whether the installation was executed properly. CAB files that were generated during earlier
installation processes are saved with a date ID in the "Reports" directory.
See also
Checking availability of updates and support packages and installing them (Page 116)
Introduction
Software packages are installed automatically by the setup program. The setup program starts
once the installation medium has been inserted in the drive.
Requirement
● Hardware and software of the programming device or PC meet the system requirements.
● You have administrator privileges on your computer.
● All running programs are closed.
Procedure
To install the software packages, follow these steps:
1. Insert the installation medium in the relevant drive.
The setup program starts automatically unless you have disabled Autostart on the
programming device or PC.
2. If the setup program does not start up automatically, start it manually by double-clicking
the "Start.exe" file.
The dialog for selecting the setup language opens.
3. Choose the language in which you want the setup program dialogs to be displayed.

Installation
4. To read the information on the product and installation, click the "Read Notes" or
"Installation Notes" button.
The help file containing the notes opens.
5. Once you have read the notes, close the help file and click the "Next" button.
The dialog for selecting the product languages opens.
6. Select the languages for the product user interface, and click the "Next" button.
Note
"English" is always installed as the basic product language.
The dialog for selecting the product configuration opens.
7. Select the products you want to install:
– If you wish to install the program in a minimal configuration, click on the "Minimal" button.
– If you wish to install the program in a typical configuration, click on the "Typical" button.
– If you wish to personally select the products to be installed, click on the "User-defined"
button. Then select the check boxes for the products you wish to install.
8. If you want to create a shortcut on the desktop, select the "Create desktop shortcut" check
box.
9. Click the "Browse" button if you want to change the target directory for the installation. Note
that the length of the installation path must not exceed 89 characters.
10.Click the "Next" button.
The dialog for the license terms opens.
11.To continue the installation, read and accept all license agreements and click "Next".
If changes to the security and permission settings are required in order to install the TIA
Portal, the security settings dialog opens.
12.To continue the installation, accept the changes to the security and permissions settings,
and click the "Next" button.
The next dialog displays an overview of the installation settings.
13.Check the selected installation settings. If you want to make any changes, click the "Back"
button until you reach the point in the dialog where you want to make changes. Once you
have completed the desired changes, return to the overview by clicking on "Next".
14.Click the "Install" button.
Installation is started.
Note
If no license key is found during installation, you have the chance to transfer it to your PC.
If you skip the license transfer, you can register it later with the Automation License
Manager.
Following installation, you will receive a message indicating whether the installation was
successful.
15.It may be necessary to restart the computer. If this is the case, select the "Yes, restart my
computer now." option button. Then click "Restart".
16.If the computer does not reboot, click "Exit".

Installation
2.5 Checking availability of updates and support packages and installing them
Result
The TIA Portal along with the products and licenses you have ordered and the Automation
License Manager have been installed on your computer.
See also
2.5 Checking availability of updates and support packages and installing

them
By default, the TIA Portal checks automatically if new software updates or support packages
are available, for example, Hardware Support Packages (HSPs). The automatic search for
updates takes place after each computer restart and then cyclically every 24 hours. You can
also deactivate the automatic search at any time or reactivate it. You can also search for
updates manually.
If updates are found, you can download and install them.
Note
Updates and support packages from TIA Portal V13 or higher are supported.
Deactivate or activate automatic search for software updates

To deactivate or reactivate the automatic search for software updates, follow these steps:
1. Select the "Settings" command in the "Options" menu.
The "Settings" window is displayed in the work area.
2. Select the "General > Software Updates" group in the area navigation.
3. Deselect the "Look for updates daily" check box if you want to deactivate the automatic
search for software updates.
4. Select the "Look for updates daily" check box if you want to reactivate the automatic search
for software updates.

Installation
Manually searching for software updates

If you want to search for software updates manually, follow these steps:
1. Click "Installed software" in the "Help" menu.
The "Installed software" dialog opens.
2. Click "Look for updates".
The "TIA Updater" opens and the available updates are displayed.
Or:
1. Select the "Settings" command in the "Options" menu.
The "Settings" window is displayed in the work area.
2. Select the "General > Software Updates" group in the area navigation.
3. Click "Search for updates now".
The "TIA Updater" opens and the available updates are displayed.
Or:
1. Open the TIA Updater with "Start > All Programs > Siemens Automation > Automation
Software Updater".
2. Click "Look for updates".
The available updates are displayed.
Downloading and installing software updates separately

To download and install available software updates and support packages, follow these steps:
1. If the TIA Updater is not displayed, open it in one of these ways:
– If the automatic search has found updates, you receive a message in the information
area of the Windows taskbar and the icon for the TIA Update is displayed in the
information area. Click either the message or the icon to open the TIA Updater.
– Click "Installed software" in the "Help" menu and then "Look for updates".
– In the Windows Start menu, click "Start > All Programs > Siemens Automation >
Automation Software Updater".
2. Click "Download" in the line of the update or support package that you want to install.
The update or support package is downloaded. The associated "Install" button becomes
active as soon as the download process has been completed.
Note
Please note the following:
1. You can initiate multiple download processes simultaneously.
2. You can log off or also shut down the computer while the download process is running.
In such cases, the download process continues in the background as soon as you log
on again.
3. In some cases, a link to an external web page is displayed instead of the "Download"
button. In this case, download the software update from this site and install it manually.
3. Close the TIA Portal if it is still open.

Installation
4. In the TIA Updater, click the "Install" button of the software package you want to install.
The installation dialog appears.
Note
Please note the following:
1. It is not possible to install multiple updates simultaneously.
2. Do not log off during an installation and do not shut down the computer. This avoids
inconsistent versions of the software on your computer.
5. Click "Next".
The selected product is installed.
Downloading and installing several support packages in one step

To download and install available support packages in one step, proceed as follows:
1. Activate the required lines. You have several options for this:
– To download and install all displayed support packages, activate the check mark in the
title of the list.
– To download and install several support packages, select the first required support
package, hold down the <Ctrl> key and then select all further required support packages.
Then set the check mark in one of the selected lines.
– To download and install several support packages in a certain order, select the first
required support package, hold down the <Shift> key and then select the last required
support package.
2. Click the "Download and Install" button.
3. After downloading click "Next" in the displayed dialog to start the installation. A dialog box
is then displayed which informs you about the progress of the installation.
Note
Only support packages that are not subject to export restrictions can be downloaded and
installed.

Installation
2.6 Displaying the installed software
Alternative procedures for the installation of support packages

Another procedure is available for the installation of a support package. To do this, follow these
steps:
1. Click "Support packages" in the "Options" menu of the TIA Portal.
The "Detailed information" dialog opens. A table lists all support packages from the directory
that you selected as the storage location for support packages in the settings.
2. If you want to install a support package that is not in the list, you have the following options:
– If the support package is already on your computer, you can add it to the list by selecting
"Add from file system".
– If you add a support package from the "Service & Support" page on the Internet, first
you download it by selecting "Download from the Internet". Then you can add it from
the file system.
3. Select the support package that you want to install.
4. Click "Install".
5. Close and then restart the TIA Portal.
See also
2.6 Displaying the installed software

You can find out which software is installed at any time. In addition, you can display more
information on the installed software.
Procedure
To display an overview of the software installed, follow these steps:
1. Click "Installed software" in the "Help" menu.
The "Installed software" dialog opens. You will see the installed software products in the
dialog. Expand the entries to see which version is installed in each case.
2. If you would like to display additional information on the installed automation software, click
the link on the "Detailed information about installed software" dialog.
The "Detailed information" dialog opens.
3. Chose the topic you want more information about in the area navigation.
See also

Installation
2.7 Modifying or updating installed products

2.7 Modifying or updating installed products

You have the option to modify installed products using the setup program or to update to a
new version.
Requirement
Procedure
To modify or update installed products, follow these steps:
The dialog for selecting the installation variant opens.
6. Select the "Modify/Upgrade" option button and click the "Next" button.
The dialog for selecting the product languages opens.
7. Select the check boxes of the product languages that you want to install. You can remove
previously installed product languages by clearing the corresponding check boxes.
Note
Note that the product language "English" cannot be removed.
8. Click the "Next" button.

The dialog for selecting the product configuration opens.
9. Select the check boxes of the components that you want to install. You can remove
previously installed components by clearing the corresponding check boxes.

Installation
2.8 Repairing installed products
10.Click the "Next" button.

Note
Note that you cannot change the target directory because the existing installation is being
modified.
If changes to the security and permission settings are required in order to install the TIA
Portal, the security settings dialog opens.
11.To continue the installation, accept the changes to the security and permissions settings,
and click the "Next" button.
12.Click the "Modify" button.
This starts the installation of the additional components.
Note
Following installation, you will receive a message indicating whether the existing installation
was successfully changed.
13.It may be necessary to restart the computer. If this is the case, select the "Yes, restart my
14.If the computer does not reboot, click "Exit".
Result
The existing installation has been modified on your computer.
See also

You have the option to repair installed products by completely reinstalling them using the setup
program.

Installation
Requirement
Procedure
To repair installed products, follow these steps:
6. Select the "Repair" option button, and click the "Next" button.
7. Click the "Repair" button.
This starts the repair of the existing installation.
Note
Following installation, you will receive a message indicating whether the existing installation
was successfully repaired.
8. It may be necessary to restart the computer. If this is the case, select the "Yes, restart my
9. If the computer does not reboot, click "Exit".
Result
The installed products have been reinstalled.
See also

Installation
2.9 Starting to uninstall

Introduction
Software packages are removed automatically by the setup program. Once started, the setup
program guides you step-by-step through the entire removal procedure.
You have two options for removing:
● Removing selected components via the Control Panel
● Removing a product using the installation medium
Note
The Automation License Manager will not be removed automatically when you remove the
software packages, because it is used for the administration of several license keys for
products supplied by Siemens AG.
Removing selected components via the Control Panel

To remove selected software packages, follow these steps:
1. Open the Control Panel with "Start > Control Panel".
2. Click "Programs and Features".
The "Uninstall or change a program" dialog opens.
3. Select the software package to be removed and click the "Uninstall" button.
4. Select the language in which you want the dialogs of the setup program to be displayed
and click "Next".
The dialog for selecting the products you want to remove opens.
5. Select the check boxes for the products that you want to remove and click "Next".
6. Check the list with the products to be removed. If you want to make any changes, click the
"Back" button.
7. Click the "Uninstall" button.
Removal begins.

Installation
Removing a product using the installation medium

To remove all software packages, follow these steps:
3. Select the language in which you want the setup program dialogs to be displayed.
4. To read the information on the product and installation, click "Read product information" or
"Read installation notes".
6. Select the "Uninstall" option button and click the "Next" button.
7. Click the "Uninstall" button.
Removal begins.
See also

Installation
2.10 Installing and uninstalling the migration tool
2.10.1 System requirements
System requirements for the migration tool

The following system requirements apply to the use of the migration tool:
● All products used to create the source project must be installed. The following products are
supported:
– STEP 7 V5.5 SP3
– WinCC V7.2 with the latest updates
– WinCC flexible 2008 SP3
– Integrated projects from STEP 7 V5.5 and the WinCC products listed above
– STEP 7 Distributed Safety V5.4
– SINUMERIK STARTER and Startdrives
– SIMOTION SCOUT V4.4
You need the SCOUT Migration Tool PlugIn V4.4 to migrate SIMOTION SCOUT V4.4
projects.
● All optional packages needed to process the STEP 7 project are installed. For example, all
HSPs for the devices used in the source project are required.
2.10.2 Installing the migration tool
Distribution of the migration tool

You can find the migration tool in the "Support" directory on the installation DVD of the TIA
Portal. Alternatively, it is available for download from the Siemens Industry Online Support.
For some products, (such as SIMATIC Failsafe or SIMOTION) additional plug-ins are required
for the migration tool. These plug-ins can also be downloaded from the Siemens Industry
Online Support or installed from the installation DVD of the specific products.
Normally, the migration tool is installed without the TIA Portal. Because the TIA Portal has its
own integrated migration function, a separate installation of the migration tool is not necessary.

Installation
Procedure
To install the migration tool, proceed as follows:
1. Download the installation file from the Siemens Industry Online Support, or use the
installation file from the "Support" directory of the installation DVD of the TIA Portal to
perform the installation.
2. Run the installation file.
The setup program for the migration tool will open.
3. First, select the language in which the setup should be displayed and click the "Next" button.
The page for selecting the software language is displayed.
4. Since the migration tool is provided exclusively in English, you cannot choose any other
language for the installation. Therefore, click "Next" to proceed to the next step.
The page for selecting the product is displayed.
5. The migration tool consists solely of a software component. Therefore, the migration tool
is already selected.
To create a Desktop icon for starting the migration tool, select the check box "Create
Desktop icon". Then click the "Next" button.
The page for confirming the licensing terms is shown.
6. Click on an entry in the list of license terms to read the selected license term. If you agree
with all license terms, select the check box "I accept the terms of the displayed license
agreement". Then click the "Next" button.
An overview of the installation is displayed.
7. Click the "Install" button.
The installation is performed with the displayed settings.
2.10.3 Uninstalling the migration tool

The migration tool can be removed using the Control Panel.
Procedure
To remove the migration tool, follow these steps:
1. Open the Control Panel.
2. Double click on "Add or Remove Programs" in the Control Panel.
The "Add or Remove Programs" dialog opens.
3. Select the entry for the migration tool in the "Add or Remove Programs" dialog, and click
the "Remove" button.
A security prompt appears.
4. Click the "Uninstall" button to confirm this prompt.
The migration tool will be removed.

Index
CP 343-2, 44
CP 5512, 38
. Cross-reference
Inspector window, 72
.Net service packs, 35
.Net versions, 35
D
A Data backup, 111
Data type conversion, 47
Alarm
Deactivate, 50
Decimal places, 36
Alarm indicator, 72
Defective license, 99, 112
Alarm text
DEMUX, 49
Output fields, 80
Destruction of license keys, 98
Special characters, 80
Device
Alarm view, 72
Copying, 65
Alarm window, 72
Display PDF files, 95
Antivirus programs, 93, 103
Display Welcome Tour, 95
Array, 78
Downloading data to the PLC
ARRAY component, 47
Error message, 63
Array element
Location of use of HMI tag, 78
Name, 78
Array tag
E
Char, 78 EC31-RTX, 44
Asian, 34 Encryption software, 103, 107
Assigning global data blocks, 48 ENO, 50
Error message
Downloading data to the PLC, 63
C ET 200S
Positioning module, 44
Char
Ethernet module
Array tag, 78
Removal/insertion, 42
Character string, 49
Event
Characters, 34
Comfort Panel
Extended download to device, 63
S7-1200, 63
External, 47
Comparing library elements, 37
External sources, 47
Compatibility, 42, 48
Compiling
Address parameters, 63
Conversions, 50
F
Convert character string, 49 F-CM AS-i Safety ST, 45
Copying Firmware versions, 39
Alarm indicator, 72 Force job on SD card, 37
Alarm view, 72 Function value, 49
Alarm window, 72
HMI device, 65
CP 1613, 38
CP 1623, 38

Index
IP address, 38
G
Go online
K
Multiple TIA Portal instances, 41 K parameter, 49
H L
Hardware Language behavior
Detection, 45 On-screen keyboard, 85
Hardware requirements, 100, 101 Library, 37
Hardware support package PLC data types generated by the system, 48
Installing, 117 License
HMI device, 109 Defective, 99, 112
HMI device licensing Defective license, 99, 112
Non-PC-based, 109 Starting without a valid license, 109
HMI device replacement, 66 Starting without valid license, 97
HSP, (See support package) License key, 98, 110
Handling license keys, 98
Working with license keys, 110
I License Manager Panel Plugin, 110
Licenses, 94
I/O field
Load
Decimal format, 73
Extended download to device, 63
Format, 73
SIMATIC PC station, 64
IE/PB Link, 45
Loading
IE/PB Link PN IO, 45
from a device, 42, 47
Inspector window
Module comments, 44
Cross-reference, 72
to the device, 42
Event, 72
Install update, 117
Installation
Displaying software, 119
M
Licenses, 94 Maximum length
Log, 113 Tag, 85
Modifying products, 120 Memory card, 37
ProSave, 63 Removal/insertion, 42
Repairing products, 122 Memory reserve, 48
run automatically, 93 Migration, 35
Smartdrive, 67 WinCC V7.0 SP3, 70
Starting, 114 Migration tool
Support package, 117 Distribution and sources, 125
System requirements, 95 Removing, 126
Target directory, 93 System requirements, 125
Updates, 117 Mitsubishi
Updating products, 120 Connection interruption, 82
Installing license keys, 98 Module
Installing support packages, 117 Inserting, 42
Interfaces, 39 Removing, 42
Intrusion Detection System (IDS), 103, 107 Module comments, 44
Invalid license Multi-key operation, 89
With a time zone change, 99, 112 MUX, 49

Index
Restore process
License key, 111
N Return, 49
Runtime
Name
Mouse wheel, 87
Array element, 78
Network, 46
Network drive, 36
Non-licensed mode
S
Engineering System, 109 S_CONV, 49
ES, 97 S7 routing, 45
HMI devices, 110 via IE/PB Link, 45
S7-1200, 43
S7-1200 modules, 43
O SCL, 47
Screen keyboard
Online, 39
Language behavior, 85
Online connection
SD card, 37
Multiple TIA Portal instances, 41
Security, 46
Online operation, 39, 41
Security program, 103, 107
OP73
SIMATIC PC station
Loading a project, 64
Load, 64
OP77A
SIMATIC S7 Embedded Controller, 44
Simulation, 89
Open force job, 37
PLC connection, 89
Operating system, 100
Smartdrive
Operation in runtime
Installation, 67
Multi-key operation, 89
Software requirements, 100
Output fields
Special characters
Multiplex tag, 80
Alarm text, 80
Overview window, 66
Start value, 47
Starting removal, 123
STRING, 50
P System requirement for WinCC Basic, 104
PLC data type System requirements STEP 7 Basic, 100
PLC data types generated by the system in
libraries, 48
PLC data types, 46 T
Project data
T_CONFIG, 51
IO-Link master module, 42
Tag
Project library, 67
Maximum length, 85
ProSave
TP177A
Installation, 63
PTO, 48
Transferring the project
PWM, 48
HMI device, 89
Recipe data record, 89
TRCV_C, 51
R TS adapter, 89
READ_DBL, 54
Recipe data record
Transferring the project, 89 U
Remote desktop, 35
UDT, 46

Index
Uninstalling license keys, 98

USB card readers, 37
V
Virtual Machine (VM)
Supported virtualization platforms, 101, 106
Virus scanners, 107
W
Watch table
Loading data blocks during an active control
job, 54
Multiple access to the same CPU, 54
WinCC V7.0 SP3, 70
Windows, 100
WRIT_DBL, 54


STEP 7 Basic V13 2 enUS

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

STEP 7 Basic V13 2 enUS

Uploaded by

Copyright:

Available Formats

Readme 1

STEP 7 Basic V13 SP2

Printout of the online help

Siemens AG Copyright © Siemens AG 2017.

STEP 7 Basic V13 SP2

STEP 7 Basic V13 SP2

1.1.1 Improvements in STEP 7

1.1.1.1 General information

What's new in TIA Portal V13 SP2

Working with the TIA Portal

Instructions "FILL_BLK" and "MUX"

GRAPH programming editor

Parameter type "Block_DB" for entry of the instance DB

STEP 7 Basic V13 SP2

Instructions "READ_BIG", "READ_LITTLE", "WRITE_BIG" and "WRITE_LITTLE"

Working with negated numbers

Copy scenarios for program blocks

1.1.1.2 Improvements in Update 9

Working with the TIA Portal

Adding additional dimensions to an ARRAY within a DB

Copy scenarios for program blocks

STEP 7 Basic V13 SP2

1.1.1.3 Improvements in Update 8

Working with the TIA Portal

"Apply snapshot values as start values" function for fail-safe blocks

FB with a tag of data type DB_ANY in the "Temp" section

Possibility of configuring the "IE/AS-i link PN IO" module

Installation of hardware support packages

Memory requirements for the installation of the TIA Portal or an update

1.1.1.4 Improvements in Update 7

Umlauts in setpoints of the STRING data type

STEP 7 Basic V13 SP2

ANY pointers in CPUs of the S7-1500 series

Working with the TIA Portal

1.1.1.5 Improvements in Update 6

Know-how protected blocks in libraries:

Working with the TIA Portal

1.1.1.6 Improvements in Update 5

Working with the TIA Portal

STEP 7 Basic V13 SP2

Working with Graph

Configuration of AS-Interface with ET 200SP CPU

Automation Software Update (ASU)

Port Configuration Tool (PCT tool)

Migration of LAD networks

1.1.1.7 Improvements in Update 4

STEP 7 Basic V13 SP2

Working with the TIA Portal

Instructions "TCON, TSEND_C, TRCV_C" (S7-1200 and S7-1500)

Instruction "D_ACT_DP: Enable/disable DP slaves" (S7-1500)

Instruction "GET_IM_Data: Read identification and maintenance data" (S7-1500)

Keyboard operation in comparing SCL blocks

Function Keyboard shortcut

STEP 7 Basic V13 SP2

Testing with program status

Programming of NTP servers with the system function block "T_CONFIG"

STEP 7 Basic V13 SP2

Article number Description FW version

STEP 7 Basic V13 SP2

The following modules are supported with new firmware:

Article number Description FW version

1.1.1.8 Improvements in Update 3

Runtime performance of loops in SCL