Simatic: STEP 7 V5.6 Programming Software For SIMATIC S7 / C7
Simatic: STEP 7 V5.6 Programming Software For SIMATIC S7 / C7
Simatic: STEP 7 V5.6 Programming Software For SIMATIC S7 / C7
In order to protect plants, systems, machines and networks against cyber threats, it is
necessary to implement - and continuously maintain - a holistic, state-of-the-art industrial
security concept. Siemens' products and solutions only form one element of such a concept.
http://www.siemens.com/industrialsecurity
Siemens' products and solutions undergo continuous development to make them more
secure. Siemens strongly recommends to apply product updates as soon as available and to
always use the latest product versions. Use of product versions that are no longer supported,
and failure to apply latest updates may increase customer's exposure to cyber threats.
To stay informed about product updates, subscribe to the Siemens Industrial Security RSS
Feed under
http://www.siemens.com/industrialsecurity
Folder "_Manuals"
Product information: "What's New"
Product information: "New Modules"
Product information: "Central Installation"
Manual: "Getting Started: Working with STEP 7"
Manual: "Programming with STEP 7"
Manual: "Configuring Hardware and Communication Connections with STEP 7"
Manual: "System Modification in RUN Mode via CiR"
Manual: "Automation System S7-400H - Fault-Tolerant Systems"
Manuals: "NCM S7"
Manual: "From S5 to S7"
Manual: "Ladder Logic (LAD) for S7-300/400"
Manual: "Statement List (STL) for S7-300/400"
Manual: "Function Block Diagram (FBD) for S7-300/400"
Manual: "Standard and System Functions for S7-300/400"
Manual: "Standard and System Functions for S7-300/400 Part 2"
Manual: "PID Control"
Manual: "PID Temperature Control"
Compatibility list
Description of the Command Interface
The manuals are available in an installable form in the folder "_Manuals" and are optionally
available on your computer after STEP 7 has been installed. If you do not install the
manuals, you can also view at any time on the data carrier.
Operating systems
STEP 7 V5.6 can be used with the following operating systems:
MS Windows 7 Ultimate, Professional and Enterprise (64-bit), with SP1
MS Windows 10 Pro and Enterprise (64-bit)
MS Windows Server 2008 R2 (64-bit) with SP1 (Standard Edition as work station
computer)
MS Windows Server 2012 R2 (64-bit) (Standard Edition as work station computer)
MS Windows Server 2016 (64-bit) (Standard Edition as work station computer)
STEP 7 has not been tested on any other operating systems; use at your own risk.
Note
The same hardware requirements as for SIMATIC STEP 7 V5.6 itself apply to the
host operating systems.
The plant operator must ensure that the host operating systems have sufficient
system resources. .
We recommend the use of hardware certified by the manufacturers when using
HyperV-Server and ESX(i).
With respect to the use of communications processors (e.g. CP5711…), please
observe the relevant information in the module documentation and on the
SIMATIC Support pages (http://support.automation.siemens.com).
Internet Explorer
All operating systems must be using MS Internet Explorer 6.0 (or higher).
Hibernation mode
Shifting to hibernation mode is generally permitted in STEP 7. However, hibernation must not
be triggered if online connections are open or projects are being accessed by STEP 7
applications via a network.
In such cases, online connections could be terminated unintentionally and open projects on
networks may experience data loss.
For these reasons, the energy options for the operating system in the Windows Control
Panel should be set so that hibernation is not automatically triggered (by timer). Hibernation
should not be triggered manually by the user in the cases mentioned above.
STEP 7 projects must not be stored on ClearCase drives; that is, drives that are linked to a
ClearCase View (MVFS).
If you are using other software products (for example, mail providers) on a programming
device or PC with STEP 7, observe the additional notes on network settings in the section
"Using Network Drives".
4 Installation
Note
STEP 7 registers itself in the system files of the MS Windows operating system.
You cannot delete, move or rename STEP 7 files or folders using Microsoft
Windows utilities such as the Explorer or modify STEP 7 data in the Microsoft
Windows registry. The program may no longer run properly after such
modifications.
4.1.1 Firewall
Network settings
The table below shows the STEP 7 network settings you need to analyze network security and
configure external firewalls:
ALM 4410* TCP In-/Outbound License This service provides the complete
functionality for software licenses and
service is used by the Automation License
Manager as well as all license-related
software products.
Note
Note that an upgrade may require changing to a different operating system,
because as of STEP 7 V5.3 and STEP 7 V5.4 SP4 older operating systems (for
example Windows 2000) are no longer supported (see 3.1). Additional information
on the upgrade is available in the product information.
Prior to changing the operating system, you will have to backup the existing
authorization / license key with the program AuthorsW / Automation License
Manager on disk / USB Memory Stick.
When installing any components without removing S7DOS V7.1.x first, there may
be a few instances when you will receive the following error message from the
operating system: "s7oiehsx.exe - Error in application." The installation will still be
executed correctly.
Note
As of STEP 7 V5.2, you can install the license key to all local drives.
The Automation License Manger prevents the license keys from being installed on
invalid drives or media such as RAM drives, diskettes or compressed drives (i.e.
DBLSPACE). If the drive in a device is reported as being a "removable medium"
and not, as usual, as a "hard drive", it will be treated as a CD/DVD, which means
that no license key may be installed on it.
In the case of compressed drives, you can install the authorization on the
associated host drive.
Read the notes on the Automation License Manager in the almreadme.rtf file on
the STEP 7 installation DVD under "Automation License Manager\ALM32\" or
"...ALM64\".
Hidden files are stored in the folder "<Drive, on which the license key is
installed>:\AX NF ZZ". These files and the folder must not be deleted, moved, or
copied. They contain data required for the licensing of your software.
If you do not adhere to these guidelines, the license key may be irretrievably lost.
Note
Software products must be uninstalled according to Microsoft Windows
conventions.
Use the Microsoft Windows application "Programs and Features" (for example,
under MS Windows 7 in the taskbar in …> Control Panel > Programs and
Features > Uninstall a program) to remove your software package (for example,
"STEP 7").
As an alternative, you can use the setup program on the STEP 7 DVD to remove
a program.
If you uninstall an older version of STEP 7 in order to install STEP 7 V5.6, you must first
uninstall any existing optional packages for STEP 7 as well.
The following CPs are supported in STEP 7 without additional SIMATIC Net software or
licenses:
CP1612
CP1613/23
CP1616
CP1626
CP1628
CP5511
CP5512
CP5612/22
CP5613
CP5623/24
CP5711
Field PG
DPX2
PG MemoryCard Interface
PC Adapter USB A2
Note
The use of communication processors CP 5611 A2 and CP 5621 in
multi-core/multi-processor systems on PROFIBUS networks has been approved
with a baud rate of up to 1.5 Mbps. You may experience problems if you operate
with higher baud rates.
Hardnet modules
If you use the Industrial Ethernet network card CP 1613/23 or the PROFIBUS cards
CP 5613/14, you require the optional package SIMATIC NET PC additionally in a version
compatible with STEP 7 V5.6 (see Compatibility list S7KOMP_B.PDF in the installation
directory "STEP 7").
General PC/programming device settings
As of STEP 7 V5.5 SP3 there is the possibility of installing the product via a software
distribution system in computer networks. In this case the SYSTEM accounts of the client
computers running under MS Windows Vista or MS Windows 7 must first have the right to
create symbolic links ("SetCreateSymbolicLinkPrivilege"). This is a special administrative
measure for the affected client computers and is not done by the STEP 7 setup program
automatically.
The optional package S7-PDIAG up to and including V5.3 cannot be used with STEP 7
V5.6.
Notes on Usage (Release Notes)
These notes should be considered more up-to-date than the information in manuals and
online helps.
5 New Features and Changes in the New Version
Screen savers
When using a screen saver, you should note that the additional processing required takes up
CPU time and this can lead to a system overload. Some screen savers are known to prevent
the release of main memory components. This leads to a continuous reduction in the
available main memory.
PC and TS adapters
If the connection is interrupted or lost when using PC or TS adapters for communication
connections, check the power management preferences on your computer.
Release of shares
If shares of a NTFS partition are released in MS Windows 7 / MS Windows Server 2010 / MS
Windows Server 2008 / MS Windows Server 2012 as well as MS Windows Server 2016,
then users who are to have access to this share should be entered in two places. Select the
menu command "Sharing and Security", and enter the users in both the "Sharing" tab as well
as the "Security" tab.
Please also observe the notes in the following section on "Multiprojects".
6.5 Multiprojects
Opening of multiprojects on several computers simultaneously is not supported!
In a STEP 7 multiproject, an editor working at Computer 1 ("client") can access information in
a STEP 7 project on Computer 2 ("server"), such as in the case of interproject functions.
When working in this environment, please observe the information in the following notes:
Also observe the requirements and recommendations for working with multiprojects as
described in the online help.
Projects in version 2
You can basically continue to use the project data from STEP 7 V2.1 in STEP 7 V5.6, if
these project data have been imported into a project in the current version.
Caution
If objects with messages are in progress with STEP 7 version <= V5.1, such as
blocks with block-related messages symbol tables with symbol-related messages,
blocks with S7-PDIAG monitoring or programs with user-defined messages, this
project may not be opened by another PG/PC with STEP 7 version V5.2 or later.
This means that the project has to be closed on the computer with the older STEP
7 version - even for read access.
Assigning unique message numbers for the CPU or for the project
Please note that in projects in which messages numbers are assigned for the CPU (new
procedure), that only those programs, blocks or symbols without message configuration
(such as user-defined messages, block messages, scan messages, S7-PDIAG
configurations) can be edited in earlier versions of STEP 7 (such as V5.1). It is not
possible to convert CPU-based message assignment to project-based message
assignment.
When creating a project, you are no longer asked if messages should be created project-
oriented or CPU-oriented. The new standard setting is the CPU-oriented assignment of
message numbers (without a query).
Note
Sample projects and libraries shipped with STEP 7 V5.6 are always copied when
you install STEP 7. If you have edited the standard sample projects, they will be
overwritten with the original examples if you reinstall STEP 7.
You should therefore make a copy of the standard examples before you make
changes to them and then make changes to the copy.
The symbolic name of the blocks FB210 and FB220 has been changed. The existing
functionality will remain the same.
FB210: S5FW_TCP FW_TCP
FB220: S5FW_IOT FW_IOT
Accessible Nodes
The "Accessible Nodes" and "Memory Card" views are not always automatically updated.
You can update both of these windows by pressing the F5 key.
Note
Please note that loading of split projects in ARJ format is no longer supported as
of V5.4 SP4. In older STEP 7 versions, the ARJ2.50a included there can be
installed on Windows XP to unzip older archives. You can then convert the project
with PKZip 14.4 into the standard zip format, which means you can archive and
retrieve files.
Change log
A change log for a project can only be written if SIMATIC Logon is installed on the PC or
PG. Please read the information in the section "Note on the use of SIMATIC Logon."
You should only edit projects with a change log on a PC or PG on which SIMATIC Logon
is installed.
Activities involving the memory card are not contained in the change log. You can find
additional notes on the change log in the online help.
S5 adapter modules
When you use a number of S5 adapter modules in an S7-400 station, no check is made
to determine whether the S5 addresses overlap in the P/Q/IM3/IM4 area across the
modules. You have to ensure that no S5 address that is already occupied is used in the
input dialog box for the S5 adapter module/IM463-2.
No S5-analog input/output modules can be used or addressed in the user program in the
S5 adapter module. S5-analog input/output modules can only be used in SIMATIC-S7
systems in the IM463-2 or via DP interface.
Other issues
Deleting parameter data (SDB>1000): Some FMs and CPs not only store their parameter
data in system data blocks (SDB) > 1000 on the CPU but retain this data themselves. If
the SDBs are then deleted from the CPU, the FMs or CP will continue to have
parameters consisting of the previously valid data. For more information, refer to the
description of your FM or CP.
For reasons having to do with ensuring data consistency, in multi-user operation (several
users working on a project at the same time) only one other station can be used at the
same time.
If your configuration contains module from earlier optional packages, it may happen that
not all data in this modules is acquired ("captured") when using the "Export station"
function. In this case, check whether the module data are complete after the import
process is complete.
If you use the CPU function "Hot Restart", make sure that the module address area does
not exceed the process I/O image range.PLC > PROFIBUS > Diagnose, Monitor/Modify
Node:
For slaves with bit-granular I/O devices (such as ET 200S or ET 200L-SC, DP/AS-i Link),
the bit-granular configuration of the I/O devices may not be interpreted as being bit-
granular when the configuration data are read back in from the slave. For this reason,
these slaves are only displayed with byte-related I/O and cannot be configured again as
bit-granular by using the menu command Options > Specify Module. They cannot be
controlled on a bit-granular basis but only on a byte basis.
When a slave is monitored/modified, all rows are modified, even if all the rows in the list
cannot be viewed at the same time. This behavior is different from the case when
modules are monitored/modified in HW Config.
Cross-reference
Note when configuring direct data exchange (DP cross reference) that both the station at
which the slave is configured as sender and the receiver must be downloaded.
Copying from stations, among which there are communication relationships (for
example, data cross-reference), in other projects must be carried out jointly. Otherwise
these communication relationships will be lost during copying. Therefore, select the other
stations and then begin copying.
On downloading a configuration, the program does not check whether the product
revision of the DP slave supports the function "sender in direct communication link." You
should therefore observe the scope of performance of the DP slave (compare versions, if
this is available in the configuration).
Sync/Freeze:
There should be no FMs or CPs inserted in the ET 200M peripheral I/Os assigned by
STEP 7 Sync/Freeze-Groups.
Switching languages
After you have changed the language, you must restart HW-Config once more before
copying stations with DP configurations.
If the set language differs from the one used during configuration, it may happen that not
all DP slaves modules are imported with the menu command Station > Import. Solution:
Import the configuration in the original language and reset it afterwards.
DP slaves
The SFCs 5 and 49 which are used for converting geographic to logical addresses and
vice versa for slaves which are interconnected via the GSD file supply correct values
only in the following configurations:
The DP slave is connected to a 300 CPU with firmware V2.0 or higher or a
master in the operation mode DPV1.
In case of fault the SSL 0x91 supplies an incorrect parameter "adr 2" (Slot, Interface No.)
in a record for these slaves.
Diagnostic repeater
In DPV0 operating mode (DP alarm mode), diagnostic events will cause OB 82 to be
called. In DPV1 operating mode, OB 82 is only triggered by a diagnostic interrupt. If the
diagnostic interrupt is not offered as a DPV1 interrupt in the slave parameters, then this
is not supported by the given slave.
For this reason, the diagnostic repeater should be used in DPV0 operating mode.
Topology display (PLC > PROFIBUS > Show Network Topology):
Under certain conditions (number of nodes connected to the network, baud rate,
etc.), a "time out" may occur for an online connection and not all the data may be read
from the diagnostic repeater and displayed. In this case, we recommend that the
interface settings for CPxxxx (PROFIBUS) be reset to 10s in the properties dialog.
Note
If there is a PROFIBUS line behind an IE/PB link 6GK1-411-5AB00 (as a PN IO
device), such a network transition is given, however this is not the case behind a
network transition 6GK1-411-5AA or 6GK1-411-5AB00 (as pure network transition)
or for a PROFIBUS line without a link transition.
IM-157
Note that the assignment of parameters on the CPU may be aborted when using the IM 157
as an interface module for PA slaves if the set transmission rate on the PROFIBUS is too low
or if you have configured IM 157 modules that do not exist on the PROFIBUS. In this case,
increase the set monitoring time in the "Startup" tab for the CPU by changing the parameter
"Transfer of parameters to modules." You must also delete the system data in the CPU and
then download the new parameter assignment to the CPU.
Updating the firmware with redundant interface modules (IM 157 and IM 153-2)
are used
If you want to use the IM 157-0AA82-0XA0 or the IM 153-2BAXX-0XB0 redundantly and
update the firmware of the IMs, you will have to do this in two steps.
Caution
If the PG is not directly connected to the PROFIBUS, you will not be able to
determine whether both modules can be addressed via the STEP 7 Routing
mechanisms.
Symbols
Modules whose input or outputs data consist of different data types are currently offered
with byte-oriented symbols. If the number of data amounts to 3 or more bytes, these data
can only be accessed as a whole (by using the SFC 14 and SFC 15) although a symbol
is specified for every byte.
Note: In principle, all blocks with the language of creation “SFM” should be deleted
before generation when changing between the old process and the optimized created of
messages. The blocks in question can be deleted either in the SIMATIC Manager or in
the “Report system error” dialog box using the “Delete” button.
Miscellaneous
PA slaves cannot be operated with the CP 342-5 MLFB 6GK7342-5DA00-XXXX,
6GK7342-5DA01-XXXX, 6GK7342-5DA02-XXXX and CP 342-5 FO MLFB 6GK7342-
5DF00-0XE0
If configuration modifications are made to a DP slave ET200iSP with inserted 8 DI
NAMUR modules, you have to check the configuration of the 8 DI NAMUR modules
following the modification, because their configuration may have also changed.
PN/PN coupler
The device names of the PN/PN coupler can only be saved to the MMC if both interfaces of
the coupler are configured in the same project. The transmission of both device names to the
MMC is not supported if the coupler is configured using GSD.
Shared Device
In a shared device configuration within a project or in separate projects, you may not exceed
the maximum IO configuration of the IO device regardless of the module and submodule
assignment to the individual IO controllers.
CP 1616
If a CP 1616 was configured as a PROFINET IO device with the RT class IRT (high
performance) and modules from the "Isochrone" catalog folder of the corresponding
PROFINET IO device were used for this purpose, without the option "Operate IO
device/application in isochrone mode" being enabled in the "Application" property dialog of
the PN-IO module, then an error will be reported in case of a consistency check. In this case
you will either have to enable the option "Operate IO device/application in isochrone mode"
or update the GSDML file of the PROFINET IO device.
More details as well as an updated GSDML file are available on the web pages of Siemens
Product Support.
Note
No changes to the PN/IO interface
I/O components which are connected to a PN/IO interface cannot be changed
during operation.
FC 450 "RED_INIT"
FC 450 "RED_INIT" deletes all blocks configured in HW Config for the number range in the
work DBs.
Network settings
For MPI and PROFIBUS networks, a "highest MPI address" or "highest PROFIBUS
address" (HSA) must be configured. We recommend that you use the default values
recommended by STEP 7 for new projects.
- If you want to connect to a network using a programming device/PC, you should
ensure that the address of the programming device/PC does not lie above the HSA.
The default value for the highest MPI address was 15 for STEP 7 V2.1 projects.
- The other network settings must also be the same on all stations in a subnet.
- After making changes to network settings, the configuration should be downloaded
to all SIMATIC stations in this network so that the settings are the same for all
stations.
At 19.2 Kbps, no more than 8 nodes should be operated at the MPI interface of a CPU.
If the MPI/DP interface for a CPU318 is operated as a MPI interface at 19.2 Kbps, the
HSA may not be set to 126.
To assign a PROFIBUS address to an ET 200C station, only the programming device/PC
should be the master on the PROFIBUS DP. The address assignment is only possible
with the CP 5512 and CP 5611, CP 5611 Onboard, CP5711 and CP5621 (visualized as
CP 5611), not with PC or TS adapters.
Caution
If you make a setting using the wrong bus parameters when you connect the
programming device/PC to the bus, the bus may be subject to major disturbances
to the point where other bus nodes (such as DP slaves) may fail. You must also
observe the notes on PROFIBUS-DP address assignment in the section
"Hardware Configuration (PROFIBUS DP)".
Older PC and TS adapters (PC/MPI cable for MPI connection via the COM port of the
PC/PG) can only be used for MPI and not for PROFIBUS (DP, universal). PC and TS
adapters from V5.0 can be used with MPI and PROFIBUS up to 1.5 Mbps. The TS
Adapter II can be used with MPI and PROFIBUS up to 12 Mbps.
If your programming device /PC can only reach a module through a gateway, STEP 7 will
always select the shortest path to the module. However, if communication is not possible
through this gateway (line interrupted, etc.), the connection will not be established. If
there is an alternative way of reaching the module through other gateways, STEP 7 will
automatically attempt to establish the connection through these other gateways. The
sequence in which these attempts are made can be set in the properties dialog for the
STEP 7 program.
To do this, proceed as follows:
1. Open the online view of the project.
2. Navigate to the STEP 7 program associated with the CPU.
3. In the properties dialog for the STEP 7 program, open the "Addresses: Module" tab
(menu command "Object Properties").
Here you can set an alternative gateway if one is available.
Address Assignment
The addresses of active PROFIBUS nodes must have a gap of at least one address with
certain modules. In this case, STEP 7 V5.5 SP3 automatically assigns addresses which
take this rule into account. For example, you have configured two CPU 315-2 DP
devices without DP Master systems. These CPUs will automatically receive the
PROFIBUS addresses 2 and 4. You can change these addresses, but you must then
ensure you allow for the PROFIBUS address gap. This also applies to projects which
you have already created with STEP 7 V2.0/2.1.
You must also take the address gap into account when assigning addresses to
other active bus nodes (for example, a programming device/PC to which you assign an
address using the "Setting the PG/PC Interface" application).
Caution
If you do not take into account the address gap between active bus nodes, this
may cause bus nodes to malfunction or to fail completely (for example, DP slave
stations).
You should note that if the address is equal to the "Maximum no. of nodes," the address 0
should not be used.
The station address for a programming device/PC must not be set to the station address
for a station on the PROFIBUS bus, such as for a DP slave
Language elements
Note
The use of high-level language constructions in Statement List, such as the
following, can lead to the contents of the DB register and the address register
AR1 being changed:
- Fully-qualified data block access (for example, DB20.DBW10) as an
actual parameter for a function (FC), FB and multiple instance CALL
- Structure components of a formal parameter as operand within FCs or
FBs
- Structure components of a formal parameter as actual parameters for FC
or FB can change the contents of DB register and address register AR1.
In a function block, function, or multiple-instance CALL, RLO or accumulators
1 and 2 may not be used as additional (implicit) parameters.
The DI register and the address register AR2 are used by the system for the
function block and multiple-instance CALL and must not therefore be changed
within function blocks.
Some of the loadable standard blocks use the address register AR1.
Within a function block, the command "L P#parameter_name" loads the
address offset of the specified parameter, relative to the address register AR2.
To determine the absolute offset in the instance data block of multiple-instance
function blocks, you must add the area-internal pointer (address only) of the
AR2 register to this value.
If you use the above programming methods and the above-mentioned registers
and accumulators at the same time, you must ensure that the contents of the
specified registers and accumulators is restored, otherwise this may lead to
errors.
Refer to the topic "Avoiding Errors when Calling Blocks" in the Help on STEP 7 for
details.
In the instructions AW, OW, XOW, AD, OD, XOD, binary constants (such as OW
2#101010101010101) are not supported. Hexadecimal constants (such as OW
W#16#AAAA) are possible.
As of V5.5.3, data can be correctly transferred to the instance block when copying the
parameter data of a FB call to the instance block of the called FB if this instance block is
passed on as a BLOCK_DB parameter. This change can lead to a difference that can be
detected by a block comparison during recompilation of a block even if no changes were
made by the user. The difference cannot be seen, even in the detail view in the block
comparison, however.
Block parameters
Blocks with Boolean input and in_out parameters should only be called by blocks with the
property "Block Version 2." Otherwise the first Boolean input or in_out parameter may, in
some cases, not be passed correctly.
If you use Boolean output parameters of a call box as the input parameters of a second
call box, the call boxes must be located in different networks or the output parameters of
the first call box may have no effect as the input parameters of the other call box.
If a parameter of the type UDTx is supplied with a data block which also has the type
UDTx (entry in the symbol table: DBx UDTx), your parameter entry is rejected as a type
conflict. You can still, however, transfer a DB component with the type of this UDTx.
In the temporary variable range, only the temporary local data declared by the user can
be used for programming. This should also be noted when using blocks from optional
software packages in Statement List, Function Block Diagram, and Ladder Logic
programs.
Reference data
The time required to display the view selected for reference data depends greatly on the
number of entries to be displayed. For very long programs you can restrict the number of
reference data using the menu command Options > Reference Data > Filter in the
SIMATIC Manager. In the filter for the cross references you should only select the
address and value ranges relevant for your requirements
When the reference data are generated, the following addresses are not included:
Address in the form of a formal parameter, for example: SP / CU <parameter name>
Addresses from register-indirect statements
Addresses from memory-indirect statements
Local data
Data blocks opened with OPN DIx are displayed in the program structure as OPN DBx
After rewiring block calls the reference data may no longer be valid. Therefore, you must
always generate the reference data after rewiring.
In the program editor, (LAD, FBD, STL), a window displays the use locations for the
addresses in the current network in the entire program (menu command View > Details;
"Cross-reference" tab). This section of the cross-reference list (reference data) contains
neither cross-references for partially qualified access to data blocks nor any pointer
accesses.
The "Unused symbols" view for the reference data lists the symbols that are not used in
the S7 program. If you have assigned attributes, such as messages for display devices,
to symbols, be sure to look in the symbol table before deleting unused symbols (column
"M" for "message properties") to verify that these symbols are, in fact, not needed for a
display device. This also applies to the "O" attributes (Operator Control and Monitoring
with WinCC) and "C" attributes (Communication Properties).
Note
The scope of the reference data you want to display has been extended to include
far more information as of STEP 7 V5.0. If you have programs whose reference
data were generated in an older STEP 7 version, generate the reference data
again in the SIMATIC Manager using the menu command Options > Reference
Data > Generate.
A filter determines which data are selected and how they are represented for the
various views of the reference data. If you want to check the default filter settings
and make any changes you require before the reference data are displayed,
select the menu command Options > Reference Data > Filter in the SIMATIC
Manager.
Copying objects
If objects are copied from project to project with configured display texts (for example,
message blocks, symbol tables with assigned messages), you should make sure that the
required display languages are available in the target project (check using the menu
command Options > Language for Display Devices). Not all the display languages which
exist in the source project will be created automatically in the target; instead, only the texts
whose languages have been created in the target object are copied.
Importing display texts (menu command Options > Manage texts in several
languages > Import):
When importing display texts (S7UserTexts, S7SystemTextLibrary and
S7UserTextLibrary) it is possible that an access error is reported in the log file
<import.txt>, because the operating system may still be causing internal process to access
this object. In this case repeat the importing process under observation of the specifications
below. The access error should then no longer occur.
Ensure that no editors or applications are opened with the above-mentioned objects (editors
from the main menu Options > Text Libraries > User Library or System Library for user
texts or system text libraries).
Before importing always close the log file <export.txt>. If <export.txt> is opened, an access
error can occur while display texts are being imported.
For the function "Managing multilingual texts" you can use a Microsoft Office Excel version
as of EXCEL 97 SR2 up to and including version 2007.
When using the function "Delete Project" it is recommended to close the application or if using C#
to encapsulate the calls in separate AppDomains.
When using the command interface, you will have to note the following when installing
older CPs (e. g. 342-5, 443-5):
- For such CPs use a number with the format "XY0" (e.g. "100") instead of the
firmware version "VX.Y" (e. g. "V1.0").
- For CPs with firmware versions of the type "product version X-X" (e. g. "1-5") use the
format "X00" (e. g. "200").
Important:
The command interface is designed for use in 32-bit applications. If you use the command
interface on a 64-bit operating system, only the WOW32 mode is supported.
6.24 TCI – Tool Calling Interface
As of STEP 7 V5.4 SP4, the TCI standard V1.1 is supported. Use a TCP/IP direct connection
to communicate with PROFINET IO devices. You can access DP slaves with the data record
routing.
Note
Do not use the hibernate / standby function as of MS Windows 7.
7 Notes on Documentation
Comprehensive documentation on STEP 7 is available to you in the online help for STEP 7.
The "basic information" on STEP 7 in contained in the HTML-based "Help on STEP 7".
The basic information and the reference information are both available to you as electronic
manuals.
This means that you have the choice between calling information exclusively from the online
help or by printing out individual chapters in order to read this information later on.
Manuals
The manuals for STEP 7 can be accessed for example, under Windows XP, at Start > All
Programs > Siemens Automation > …. They can be displayed and printed with a PDF
reader, which is supplied with the STEP 7 software.
Due to the editorial deadline necessary in the creation of the product manuals, there may be
an occasional slight difference between their content and that of the online help.
Up-to-date information:
When reading references to the Start menu, keep in mind the form of the Start menu differs
under the various operating systems.