Readme

SIMOTION
SIMOTION SCOUT
V4.5 incl. HF1
and SIMOTION Runtime Software for
SIMOTION C V4.5 incl. HF1

SIMOTION D V4.5 incl. HF1
SIMOTION P V4.5 incl. HF1
Readme
11/2016
Unrestricted
Siemens AG Ⓟ 10/2016 Subject to change without prior notice Copyright © Siemens AG 2016.
Digital Factory All rights reserved
Table of contents
TABLE OF CONTENTS........................................................................................................................ 2
1 USAGE NOTES......................................................................................................................... 4
1.1 SIMOTION V4.5.........................................................................................................................4
1.2 GENERAL NOTES...............................................................................................................................4
1.3 SECURITY NOTES...............................................................................................................................5
1.4 SOFTWARE COMPATIBILITY..................................................................................................................5
1.5 TEST CERTIFICATES............................................................................................................................5
2 SCOPE OF DELIVERY................................................................................................................ 6
3 THIRD-PARTY SOFTWARE - LICENSE CONDITIONS AND COPYRIGHT NOTES...............................9
4 SIMOTION SCOUT V4.5 HF1................................................................................................... 10
4.1 INSTALLATION OF SCOUT TIA..........................................................................................................10
4.2 INSTALLATION OF SCOUT................................................................................................................10
4.2.1 Hardware requirements..................................................................................................10
4.2.2 Memory requirement......................................................................................................10
4.2.3 Software requirements....................................................................................................10
4.2.4 Installation of SCOUT.......................................................................................................12
4.2.5 Installation of SINAMICS Support Packages....................................................................15
4.2.6 Authorization of SCOUT...................................................................................................15
4.2.7 Uninstallation..................................................................................................................16
4.3 UPGRADING PROJECTS TO SIMOTION SCOUT V4.5 HF1..................................................................16
4.3.1 Supported versions..........................................................................................................16
4.3.2 Before the upgrade..........................................................................................................16
4.3.3 Converting the project data.............................................................................................17
4.3.4 After the upgrade............................................................................................................17
4.3.5 Download after the upgrade...........................................................................................18
4.4 VIRTUALIZATION PLATFORMS AND VIRUS SCANNERS..............................................................................18
5 SIMOTION D V4.5 HF1........................................................................................................... 19
5.1 UPGRADING THE SIMOTION D.......................................................................................................19
5.2 COMPACTFLASH CARDS WITH FIRMWARE V4.5 HF1............................................................................20
5.3 DEVICE REPLACEMENT TO SIMOTION D4XX-2...................................................................................20
6 SIMOTION C V4.5 HF1........................................................................................................... 21
6.1 UPGRADING THE SIMOTION C.......................................................................................................21
6.2 UPGRADING NOTE..........................................................................................................................21
7 SIMOTION P V4.5 HF1........................................................................................................... 22
7.1 UPGRADING THE SIMOTION P........................................................................................................22
7.2 NOTE CONCERNING THE DOCUMENTATION..........................................................................................22
7.3 NOTE ON THE SYSTEM BEHAVIOR.......................................................................................................22
7.4 NOTE ON THE WEB BROWSER..........................................................................................................22
8 UPGRADING VIA THE DEVICE UPDATE TOOL..........................................................................23
9 PROFINET WITH SIMOTION................................................................................................... 24
10 FURTHER USER NOTES.......................................................................................................... 25
Unrestricted 2
SIMOTION SCOUT V4.5 HF1 Readme
10.1 SOFTWARE PRODUCT CERTIFICATE.................................................................................................25
10.2 INNOVATIONS AND CHANGES COMPARED TO EARLIER VERSIONS..........................................................25
10.3 RUNTIME PERFORMANCE............................................................................................................25
10.4 DOCUMENTATION......................................................................................................................25
10.5 ONLINE HELP............................................................................................................................25
10.6 SAMPLE PROJECTS AND LIBRARIES.................................................................................................26
10.7 SIMOTION EASYPROJECT PROJECTGENERATOR.............................................................................26
10.8 HMI CONFIGURATION................................................................................................................27
10.9 SIMATIC NET.......................................................................................................................27
10.10 SIMOTION IT.......................................................................................................................28
10.11 IMPORTANT USAGE NOTES...........................................................................................................29
10.12 IMPORTANT NOTE FOR USE AS OF STEP7 V5.5 SP3........................................................................31
10.13 NOTES FOR SINAMICS SAFETY INTEGRATED IN CONJUNCTION WITH SIMOTION................................33
11 GENERAL CONDITIONS AND FUNCTION RESTRICTIONS..........................................................34
11.1 GENERAL CONDITIONS AND FUNCTION RESTRICTIONS WITH V4.5 HF1...............................................34
11.2 GENERAL CONDITIONS CORRECTED WITH V4.5 HF1........................................................................34
11.3 SINAMICS GENERAL CONDITIONS................................................................................................34
12 CHANGES IN BEHAVIOR AS A RESULT OF ERROR CORRECTIONS..............................................35
12.1 CHANGES IN BEHAVIOR AS A RESULT OF ERROR CORRECTIONS AS OF V4.5 HF1...................................35
12.2 CHANGES IN BEHAVIOR AS A RESULT OF ERROR CORRECTIONS AS OF V4.4 HF1/2...............................36
12.3 CHANGES IN BEHAVIOR AS A RESULT OF ERROR CORRECTIONS AS OF V4.3 SP1 HF9.........................38
12.6 CHANGES IN BEHAVIOR AS A RESULT OF ERROR CORRECTIONS AS OF V4.2 SP1.................................39
12.7 CHANGES IN BEHAVIOR AS A RESULT OF ERROR CORRECTIONS AS OF V4.1 SP5.................................42
12.8 CHANGES IN BEHAVIOR AS A RESULT OF ERROR CORRECTIONS AS OF V4.1 SP4...................................42
12.11 CHANGES IN BEHAVIOR AS A RESULT OF ERROR CORRECTIONS AS OF V4.0.........................................44
END............................................................................................................................................... 44
Unrestricted 3
2 Usage notes
2.1 SIMOTION V4.5
These notes take priority over statements made in other documents.
Please read the notes carefully since important information for installation and use of the
software is included for you.
Version V4.5 HF1 runtime/firmware is the first release of SIMOTION V4.5.
2.2 General notes

Information about the new functions of version V4.5 can be found
on SCOUT DVD 1 at:
\AddOn\1_Important\English\Features
Please note Section 6.3 for the upgrade of older SIMOTION versions to V4.5 HF1.
Please also observe Important usage notes in Section 17.12 and the Changes in behavior as
a result of error corrections named in Section 21.
Information about SIMOTION in the Online Support

Overview of the most relevant technical information and solutions for SIMOTION in the
Industry Online Support.
Internet link: SIMOTION in the Industry Online Support
(http://support.automation.siemens.com/WW/view/en/10805436/130000)
All information on service and support in the Industry Online Support:
Internet link: Service and support in the Industry Online Support
(http://support.automation.siemens.com)
You can also subscribe to the newsletter here which constantly provides you with the latest
information about your products.
Further technical support and information about the SIMOTION product can be found
 in the Internet at http://www.siemens.com/simotion
 as well as in the SIMOTION Utilities & Applications (DVD2 of the SCOUT
software package)
2.3
Unrestricted 4
2.4 Security notes
Industrial security notes
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 form only one element of such a concept.
You will find more information about industrial security at:
http://www.siemens.com/industrialsecurity.
Security updates
To protect your engineering computer, it is recommended that you activate the automatic
update services (if available) for the operating system and the programs installed thereon
(e.g. Adobe Acrobat, Flash, Internet Browser or Oracle). Information on how to activate the
update services is available on the manufacturers' home pages.
In this way, the latest updates are installed automatically on your computer so that known
security gaps are corrected as quickly as possible and without you intervening.
This recommendation does not apply to the SIMOTION P.
2.5 Software compatibility

The combination possibilities of all the relevant software products that can be used with
SIMOTION are contained in a compatibility list. The list shows which versions of the individual
products (engineering tools, HMI tools, SIMOTION runtime and drive firmware versions) have
been released for use together. The list can be found on SCOUT DVD 1 as well as
(at \AddOn\1_Important\English\Compatibility\Compatibility_SIMOTION_V4501.pdf)
and in the Internet at: http://support.automation.siemens.com/WW/view/en/18857317.
2.6 Test certificates

The Safety Integrated functions of SINAMICS/SIMOTION are generally certified by
independent institutes.
An up-to-date list of certified components is available on request from your local Siemens
office.
If you have any questions relating to certifications that have not been completed, please ask
your Siemens contact.
The current status of the available certificates with regard to international standards and
machine safety (TÜV, IFA) can be found at:
http://support.automation.siemens.com/WW/view/en/13305690/134200
Unrestricted 5
3 Scope of delivery
This software package contains version V4.5 HF1 for SIMOTION SCOUT and the SIMOTION
devices.
The software package consists of various parts that are represented by individual directories
on four DVDs.
DVD name Directory on the DVD Contents
SCOUT V4.5+ HF1 InstData SIMOTION complete setup

DVD 1 HELP SIMOTION SCOUT V4.5 HF1
Addon SIMOTION AddOn V4.5 HF1

CamTool SIMOTION Extensions CamTool
HSP..TM_Timer_DIDQ_10x24V Hardware Support Package
ET200SP Timer DIDQ
SSP_... SINAMICS Support Packages
SCOUT V4.5 + HF1 Documentation V4.5 HF1 documentation

Documentation Utilities_Applications V4.5 HF1 Utilities&Applications
Utilities_Applications STEP7_V55_SP4_HF11 STEP7 V5.5 SP4 HF11
DVD 2 WCF_2008_SP3_UPD WinCC flexible 2008 SP3 Upd
SCOUT TIA V4.5 + SIMOTION complete setup

HF1 ScoutTia SIMOTION SCOUT TIA V4.5 HF1
MigTool SIMOTION SCOUT Migration
Tool Plug-In V4.5 HF1
SCOUT V4.5 HF1 DVD 1
Root directory, SCOUT complete setup

The root directory contains the complete setup to install the components of the SCOUT V4.5
HF1 software package.
The SIMOTION SCOUT V4.5 HF1 version is a complete installation of SCOUT.
InstData, HELP SIMOTION SCOUT V4.5 HF1

SIMOTION SCOUT V4.5 HF1, incl. online help
AddOn V4.5 HF1

The AddOn directory contains important information on V4.5 HF1 as well as all the
information on SIMOTION IT (at 4_Accessories).
Note
As of SIMOTION V4.5, the SIMOTION firmware for all platforms and the Firmware Support
Package (installation of the FWSP in SCOUT for the device update tool) are no longer
Unrestricted 6
contained on the SCOUT DVDs.
The current firmware versions can be found on the SIMOTION product support Internet
pages:
SIMOTION D Firmware http://support.automation.siemens.com/WW/view/en/31045047
SIMOTION C Firmware http://support.automation.siemens.com/WW/view/en/31263919
SIMOTION P Setup Please get in touch with your local Siemens contact person.
Firmware Support Package http://support.automation.siemens.com/WW/view/en/33119786
SIMOTION Extensions CamTool V3.0 SP3 HF2

The CamTool software simplifies the creation of cams. CamTool is an optional package for
SIMOTION SCOUT.
The installation files are required only for the installation with SCOUT.
For SCOUT TIA, CamTool can be installed as part of the SCOUT TIA installation (optional).
In both cases, CamTool must be licensed separately.

A new upgrade license is required for CamTool V3.0 SP3 HF2 compared to versions older
than V3.0.
ET 200SP HSP0240_V2.2_TM_Timer_DIDQ_10x24V
Hardware Support Package for Step7 V5.5 for ET 200SP Timer DIDQ
SSP_... SINAMICS Support Package

Additional SINAMICS firmware versions are stored as SINAMICS Support Packages (SSPs).
The contents of SSP_... can be selected individually for installation via the SCOUT setup. It is
also possible to install individual SSPs later by calling the SCOUT setup again.
For detailed information, see Section 6.2.5, Installation of SINAMICS Support Packages.
SCOUT Documentation and Utilities DVD 2

V4.5 HF1 documentation
The Documentation directory contains the SIMOTION documentation in German, English,
Italian and French in PDF format.
STEP7 V5.5 SP4 HF11

Hotfix 11 for STEP 7 V5.5 SP4 programming software for SIMATIC
WCF 2008 SP3 Upd

Update (Hotfix) for WinCC flexible 2008 Service Pack 3
Unrestricted 7
Utilities & Applications V4.5 HF1
The free-of-charge Utilities & Applications provide important background information about
SIMOTION, tools, special functions, blocks and SIMOTION project examples as well as
ready-to-use standard applications (e.g. handling, cross cutter, etc.) for demonstration
purposes or use in your projects. You can also find detailed information there about scripting
and many sample scripts that facilitate working with SIMOTION.
Of particular interest here is the "SIMOTION easyProject" section with which projects can be
generated very easily with standard blocks. Further information can be found in the flyer
accompanying this SCOUT DVD and in Section 17.7 SIMOTION easyProject Project
Generator.
An HTML user interface enables easy navigation through the comprehensive contents of the
Utilities & Applications.
You start the navigation by opening the "index.html" file in the Utilities_Applications directory.
The software on Utilities & Applications may be used, changed and extended by SIMOTION
customers in applications free-of-charge, and executed in SIMOTION runtime systems. Any
required runtime licenses for the execution of the software are not included in this free use
and must be ordered separately. The type of use of this software means that it is subject to
the following limited liability.
Limitation of liability for Utilities & Applications

The application examples and the associated documentation on Utilities & Applications are
provided free-of-charge. With the software, the customer receives the non-exclusive, non-
transferable right to use the software without charge; this includes the right to modify the
software, to reproduce it in modified or non-modified form and to link it to the customer's own
software.
The software has not been tested with the normal system test by Siemens AG.
We do not assume any liability - irrespective of the legal grounds - especially for faults in the
software or associated documentation or damage on account of consulting unless the same is
to be attributed to us, for example, for willful damage, gross negligence, damage to life, body
or health, taking over of a procurement guarantee, willful concealment of defects or violation
of important contractual liability. This does not entail a change in the burden of proof to the
disadvantage of the customer.
German law applies. The Erlangen courts have exclusive jurisdiction.
SCOUT TIA V4.5 HF1
Root directory, SCOUT TIA complete setup

The root directory contains the complete setup to install the components of the SCOUT TIA
V4.5 HF1 software package (internal identifier: 04.50.29.18).
Prerequisite is the installation of a TIA Portal Framework V14. This also applies similarly for
the Migration Tool Plug-in.
Microsoft.NET Framework 3.5 must be installed for the installation under Windows 8.1.
Licenses
Licenses contains the license conditions.
Unrestricted 8
SCOUT TIA
SIMOTION SCOUT TIA V4.5 HF1, incl. CamTool (without license) and online help.
MigTool
SIMOTION SCOUT Migration Tool Plug-In V4.5 HF1.
4 Third-party software - License conditions

and copyright notes
Copyright notes for the third-party software contained in this product, in particular the open
source software, as well as the applicable license conditions, can be found in the Read_OSS
file in the \OSS_Information directory on the SCOUT DVD. This file is also displayed during
the setup by clicking the "Open source license agreement" button.
Special note for resellers:

The notes and the license conditions contained in the Read_OSS file must be passed on to
the purchaser in order to avoid the reseller and purchaser from violating the licensing
conditions.
Unrestricted 9
6 SIMOTION SCOUT V4.5 HF1
The installation notes contain important information which you require for the installation of
the software. Please read these notes before you start the installation.
6.1 Installation of SCOUT TIA

!!! !!! Please note the separate Readme on the SCOUT TIA DVD!!!
This contains the installation notes and usage notes for SCOUT TIA that are also
integrated during the setup.
Supplementary notes:
An upgrade to TIA Portal V14 is made only based on TIA Portal V13 SP1 projects (the last
update is recommended). Compatibility mode is not supported in TIA Portal V14.
No new Engineering license is required for an upgrade to SIMOTION SCOUT TIA V4.5.
SCOUT V4.5 still functions with a V4.4 license key.
6.2 Installation of SCOUT
6.2.1 Hardware requirements

The following minimum hardware requirements must be fulfilled for installation of the
"SIMOTION SCOUT" software package:
Processor: Intel® Celeron® Dual Core 2.2 GHz (Ivy / Sandy Bridge)
RAM: 4 GB
Screen resolution: 1024x768
Recommended hardware requirements:

Processor: Intel® Core™ i5-3320M 3.3 GHz or faster
RAM: 8 GB or more
Screen: 15.6" full HD display (1920 x 1080 or higher)
6.2.2 Memory requirement

For a complete installation, SIMOTION SCOUT V4.5 HF1 requires approx. 9 GB of memory
space on your hard disk.
You should reserve at least another 200 MB for your projects.
An important requirement for the installation is that there is at least 3 GB of temporary

memory available on drive C:\. This is also required when the installation is to be performed
on a drive other than C:\.
6.2.3 Software requirements

6.2.3.1 Operating system
The software requirements for SIMOTION SCOUT V4.5 HF1 are:
Microsoft Windows 7 SP1 Professional 32-bit and 64-bit or
Microsoft Windows 7 SP1 Ultimate 32-bit and 64-bit
Microsoft Windows 7 SP1 Enterprise 32-bit and 64-bit
Unrestricted 10
Microsoft Internet Explorer as of V8.0
You must have administration rights to install SIMOTION software packages. You may be
reminded of this during the installation.
Because of the access rights under Microsoft Windows 7, the user must be entered and
registered in the "SIMOTION TIA Engineer" group. Without this authorization certain
functions, such as "Set PG/PC interface", cannot be used.
We recommend that the task bar be left switched on so that requirements of other
applications can be identified.
The installation on an operating system that does not use the western character set is
possible only with an operating system in the MUI (Multilanguage User Interface) version.
6.2.3.2 Runtime environment

SIMATIC STEP 7 V5.5 SP4 must be installed on the PC.
The installation requires the deployment of STEP 7 V5.5 SP4 HF11.
STEP 7 V5.5 SP4 HF11 is stored on DVD 2.
Please note the important note in

Section 17.13 Important note for use as of STEP7 V5.5 SP3.
WinCC flexible 2008 SP3 Upd7 is available for the visualization and has also been released
for integrated use in SCOUT V4.5 HF1.
More detailed information can be found in Section 17.8, HMI configuration.
The software requirements for the deployment of PROFIsafe in conjunction with

SIMATIC F-CPUs and SIMOTION/SINAMICS are:
 S7 F ConfigurationPack V5.5 SP11
Distributed Safety V5.4 SP5 Upd1.
S7 F ConfigurationPack V5.5 SP11 can be found as download in the Siemens Industry Online
Support at http://support.automation.siemens.com/WW/view/en/15208817
The deployment of S7 F-ConfigurationPack V5.5 SP12 has not been released.
There is no guarantee of executability in a SW configuration other than that specified above.
Compatibility list
Detailed information on the combination of software products can be found in the
Compatibility list on SCOUT DVD 1
and also in the Internet at: http://support.automation.siemens.com/WW/view/en/18857317.
A detailed, regularly updated list of I/O modules released for SIMOTION as well as notes on
their deployment can be found on SCOUT DVD 1 at:
\AddOn\1_Important\English\Compatibility
The list is also available on the Internet at:
http://support.automation.siemens.com/WW/view/en/11886029.
The SINAMICS commissioning tool STARTER V4.5 SP1 as well as SIMATIC S7-Technology
(STEP 7 option for the configuration of the CPU 31XT-2 PN/DP) are integrated in SIMOTION
SCOUT V4.5.
Caution:
A simultaneous operation of the SIMOTION SCOUT, STARTER, SIMATIC S7-Technology,
SIMATIC NCM PC and STEP 7-Micro/WIN variants on a PC/PG is not supported.
Unrestricted 11
6.2.4 Installation of SCOUT
A setup can only be performed with administrator rights. Make sure that the login after the
reboot is performed with the same login (with administrator rights) as for the setup.
For the upgrade of a STEP 7 environment to STEP 7 V5.5 SP4, it is recommended that first
all option packages be uninstalled, then STEP 7 upgraded and then the required option
packages installed.
You can remove your authorization for older versions first, but existing authorizations are
retained during an installation.
No new Engineering license is required for an upgrade to SIMOTION SCOUT V4.5. SCOUT
V4.5 still functions with a V4.4 license key.
The SCOUT installation must not be interrupted by a computer restart.
Installation of WinCC flexible

If WinCC flexible is installed on your computer in one of the following versions, it does not
have to be uninstalled.
WinCC flexible 2008 SP3 Upd7
If you have installed WinCC flexible on your computer in another version, it has to be
uninstalled before starting the SCOUT installation, and the installation sequence
described below followed.
Install the software in the following sequence. Problem-free operation will only be ensured
when you observe this installation sequence.
1. SIMATIC STEP 7
2. SIMOTION SCOUT (optional CamTool)
3. WinCC flexible
Installation of SIMOTION SCOUT

Insert DVD 1 SIMOTION SCOUT V4.5 + HF1 in the drive. SIMOTION SCOUT V4.5 HF1 is
installed by a prompted setup started by double-clicking the SETUP.EXE program in the
Microsoft Windows Explorer.
It consists of the following products:

 Automation License Manager V5.3 SP3 Update 1
 SIMATIC CFC V8.2
 SIMOTION SCOUT V4.5 HF1
consisting of the components:
SIMOTION SCOUT V4.5.0.1 (internal identifier: 04.50.29.18)
SIMOTION technology packages V4.5.0.1 (internal identifier: 04.50.29.18)
SIMOTION OM V4.5.0.1 (internal identifier V04.05.00.01_04.50.29.18)
DriveES Slave OM V05.10.01.01_04.50.42.01
DriveES Drive OM V05.08.00.00_00.00.00.95
DCBLIB SIMOTION/SINAMICS
DCC Editor SIMOTION V2.4.0.1 (internal identifier V02.04.00.01_04.50.29.18)
DCC Editor SINAMICS V2.4.1.0 (internal identifier V02.04.01.00_04.50.41.00)
DCC Help System V2.4.1.0 (internal identifier V02.04.01.00_04.50.41.00)
SSPs …
SIMOTION Task Profiler V4.5.0.1
The first step (check SIMOTION SCOUT requirements) checks whether the requirements
placed on the operating system are met.
During the setup, you can select which SSPs of the SINAMICS families together with their
Unrestricted 12
firmware versions are to be installed.
The SSP SIMOTION SINAMICS Integrated is always installed.
For detailed information, see Section 6.2.5, Installation of SINAMICS Support Packages.
If you want to install SIMOTION SCOUT from the hard disk, copy the contents of DVD 1 and
DVD 2 to the appropriate directories VOL1 and VOL2, and start the SETUP.EXE program
from VOL1.
Installation of Automation License Manager (ALM) V5.3 SP3 Update 1

For the installation of SCOUT V4.5 HF1, Automation License Manager V5.3 Update 1 is
selected in the installation settings if an earlier version or no ALM is installed on the computer.
ALM V5.3 Update 1 is installed when the Automation License Manager V5.3 Update 1 is
selected. When deselected, ALM V5.3 Update 1 is not installed and the already installed ALM
is retained. For security reasons, it is strongly recommended that you upgrade to Automation
License Manager V5.3 Update 1. ALM V5.3 Update 1 can also manage old licenses.
Authorizations are no longer supported on 64-bit operating systems.
If the ALM V5.3 Update 1 is installed, the following must be taken into account when
connecting to a license server:
With the ALM V5.3 Update 1, communication to a license server is via a port communication.
This means that when the SCOUT software is started, a connection to an already existing
license server no longer functions. The connection to the license server has to be established
again. Port number 4110 is then automatically entered for this connection. This port number
may have to be entered in firewalls as an exception.
If an Automation License Manager version older than V4.0 is installed on the license server,
the call/assignment of the licenses from the client computer with ALM V5.3 Update 1 does not
function. The license server must then also be upgraded to ALM V5.3 Update 1, or the
installation of the ALM V5.3 Update 1 deselected before installing SCOUT.
Further information on the Automation License Manager V5.3 Update 1 can be found in the
ALM online help.
Installation of Drive Control Chart (DCC)

DCC SIMOTION V2.4 contains the CFC editor V8.2 and the DCB libraries (block
libraries) for SIMOTION and SINAMICS.
DCC SIMOTION V2.4 can be installed in SIMOTION SCOUT V4.5 HF1. When
installed in SCOUT V4.5 HF1, the libraries for SIMOTION and SINAMICS are
installed in addition to the editor.
With SCOUT V4.5 HF1, DCC SIMOTION/SINAMICS is installed automatically with

SCOUT provided the installation of the CFC editor is also selected during
the setup.
Note on the CFC editor:
DCC charts that have been converted to a later version and DCC charts that have
been created with the new CFC version cannot be opened with an older CFC
version.
- A backward conversion of DCC charts to an older CFC version is not
supported by CFC.
- Saving in the old project format does not result in a reconversion of the
charts to an earlier CFC version.
- A reconversion can be forced via an XML export / XML import of the DCC
charts: XML export with a current CFC version and XML import on a computer with
an earlier CFC version.
- The CFC version is not relevant when uploading DCC chart sources from
the target device.
Engineering licenses are required to use the DCC SIMOTION/SINAMICS functions.

They are contained in the DCC SIMOTION software package as floating licenses.
Only the software that can be installed is included in the SIMOTION V4.5 HF1
scope of delivery.
Any existing licenses for DCC V2.1, V2.2 SP1 and V2.3 remain valid for DCC V2.4.
Unrestricted 13
A new ordering is not required and DCC V2.4 is installed with the SCOUT
installation as described above.
If DCC SIMOTION/SINAMICS is to be installed in a STEP 7 environment with CFC for

STEP 7, note that the CFC editor in version V8.2 is also required for STEP 7. When
the CFC editor V8.2 is installed, a floating license for V8.2 is required for SIMATIC
CFC.
Installation of the SIMOTION Task Profiler

The SIMOTION Task Profiler is also installed with the SCOUT setup.
The SIMOTION Task Profiler is an application for displaying the data recorded from
the SIMOTION Task Trace.
The Java Runtime Environment is required to execute this program.
Information on user entries required during setup

The drive on which you install SIMOTION SCOUT V4.5 HF1 cannot be selected. It is always
installed in the STEP 7 directory!
Sufficient disk memory space must be available.
Interruption of the installation through a restart

The computer may have to be restarted while performing the setup of SIMOTION SCOUT.
The setup automatically continues with the installation after the restart. The data medium from
which the setup was started may not be removed during the restart.
If you have started the setup from a network drive, the setup may be aborted with an error
message after the restart. In this case, check whether the network drive was connected
correctly at the restart. If not, please reconnect the network drive. When the network drive is
available again, restart the setup, which then continues with the installation.
Before you can use SIMOTION SCOUT V4.5 HF1, Microsoft Windows must be restarted (a
prompt appears at the end of the installation). This step will activate all Microsoft Windows
entries.
If you do not restart Microsoft Windows, SIMOTION SCOUT V4.5 HF1 will have only limited
functionality and there may be data loss.
Silent installation
With version V4.5 HF1, SCOUT and its additional option packages can be installed via a
silent mode. This means that on the PC where the installation is to be performed, no keyboard
entries are required during the setup. The entire installation can be performed without any
user entries.
A SetupMode.ini control file is available to the user for control of the setup via silent mode.
This file is stored on the Installation DVD. This file must be manipulated to control the silent
setup. The appropriate control parameters are described in the file in German and English.
The SetupMode.ini can be copied locally and changed accordingly for the installation of the
supplied DVD. To accept the changed file, the changed SetupMode.ini must now be
transferred to the setup as parameters.
For example:
If a changed SetupMode.ini has been stored on drive C:\ in the \temp directory, the setup is
started with the following command:
DVD drive: Setup.exe C:\temp\SetupMode.ini
Note: Under Windows 7, a Windows message must be confirmed after the restart. Therefore,
a complete silent setup is not possible.
Unrestricted 14
Unrestricted 15
6.2.5 Installation of SINAMICS Support Packages
Additional SINAMICS firmware versions are provided as SINAMICS Support Packages
(SSPs).
The contents of SSP_... can be selected individually for installation via the SCOUT setup. It is
also possible to install individual SSPs later by calling the SCOUT setup again (does not
apply to SCOUT TIA).
The selection of the SSPs to be installed is made in the SCOUT setup in an initial step as
preselection for the SINAMICS families.
The individual firmware versions can then be selected specifically.
6.2.6 Authorization of SCOUT

Follow these notes carefully to ensure error-free authorization:
Before you can start working with SCOUT, you must transfer the license key for SCOUT (user
authorization) from the authorization data medium to the computer.
SCOUT V4.5 requires a license key for SCOUT V4.4.
The license key for SCOUT V4.4 licenses the continued use of SCOUT and SCOUT TIA
V4.5.
The license key for SCOUT Stand-alone V4.4 licenses the continued use of SCOUT
Stand-alone and SCOUT TIA V4.5.
There are two ways to perform the authorization:
During the setup:

After the installation of the Automation License Manager (ALM), you are prompted to perform
the authorization for SIMOTION SCOUT V4.5. SCOUT V4.5 still functions with the SCOUT
V4.4 license key.
After the setup:

If the authorization cannot or should not be installed during the setup, continue with the setup
without installing the authorization. Then restart the computer and install the authorization
later via the start menu item Simatic\License Management\Automation License Manager.
In Windows 7, the call is in the Start menu at "All Programs > Siemens Automation >
Automation License Manager".
Detailed information on the upgrade of the authorization to Version 4.4 can be found in an
FAQ of the SIMOTION Utilities & Applications. The SIMOTION Utilities & Applications are on
the SCOUT Documentation DVD.
You can find the FAQ at "FAQs" > „Upgrade / Downgrade“ > "Upgrade".
Unrestricted 16
6.2.7 Uninstallation
All software products must be uninstalled in the usual Microsoft Windows way.
To do this, remove the individual software components via the Microsoft Windows application
"Software" (in the Microsoft Windows task bar via Start > Settings > Control Panel >
Software).
Sequence of the uninstallation:
1. WinCC flexible
2. SIMOTION SCOUT (if required, CamTool first)
3. SIMATIC STEP 7
Dynamically created files from SIMOTION SCOUT may remain after the uninstallation. This is
detected by the uninstall tool and the following message displayed,
"Some elements could not be removed. Please check the individual objects manually". These
dynamically created files can, but do not need to be deleted.
6.3 Upgrading projects to

SIMOTION SCOUT V4.5 HF1
The upgrade procedure is described in detail in an FAQ of the SIMOTION Utilities &
Applications. The SIMOTION Utilities & Applications are on the SCOUT Documentation
DVD.
You start the navigation by opening the "index.html" file in the Utilities_Applications
directory. You can find the FAQ at "FAQs" > „Upgrade / Downgrade“ > "Upgrade".
6.3.1 Supported versions

As of SCOUT V4.5, SIMOTION Versions V3.2 and V4.0 are no longer supported. If a
SIMOTION CPU older than V4.1 should be upgraded, the project must first be opened with
SCOUT V4.1 – V4.4 and the CPU upgraded to a later version. The project can then be
upgraded to Version V4.5 with SCOUT V4.5 HF1.
Note:
Please note that the discontinued SIMOTION C230-2, D410, D4x5, P320-3 and P350-3
modules no longer support the kernel/runtime version as of V4.4.
6.3.2 Before the upgrade

Before the upgrade, you can back up your project with Save and export (XML export) in a
version-neutral format.
The upgrade of the hardware and the technology packages to the new version is described in
the SCOUT Configuration Manual (on SCOUT Documentation at:
\Documentation\English\1_Engineering_System_Handling\SCOUT_configuration.pdf, Section
8) as well as in detail in an "Upgrade" FAQ on Utilities & Applications.
Before upgrading a SIMOTION platform to a new kernel version, you can back up the current
machine data (retain data and user data sets).
The SCOUT functions "Save variables" and "Restore variables" are available for this. The
backup must be performed ONLINE before the upgrade of the SCOUT project. This is
possible for a version upgrade with the "old" SCOUT version or the "new" SCOUT version.
Unrestricted 17
6.3.3 Converting the project data
When first opening a project created with an older SIMOTION SCOUT version, an automatic
conversion of the engineering project to SIMOTION SCOUT V4.5 HF1 is performed.
However, this conversion only applies to the format of the data storage.
The Kernel versions of the configured devices (e.g. SIMOTION C240) remain unchanged.
Older projects can only be converted when they can be written. If, for example, you have
copied the project from a CD-R to your hard disk, all files are automatically assigned the
"write-protected" attribute by Windows.
Proceed as follows to remove the write protection:
 Open an MS DOS prompt
 Switch to the directory containing your project data, e.g.
CD C:\SIEMENS\STEP7\S7PROJ
 Reset the write protection for all project files (including all subdirectories)
ATTRIB -R *.* /s
If required, the upgraded project can be subsequently converted back to the project format of
the older version (for re-editing with an older SCOUT).
However, if you want to deploy new kernel versions on the SIMOTION devices, they must
also be upgraded in your project. A detailed description can be found in the SIMOTION
SCOUT Operating Instructions (on SCOUT Documentation at:
\Documentation\English\1_Engineering_System_Handling\SCOUT_configuration.pdf, Section
4.17).
6.3.4 After the upgrade

The following adaptations may be required after upgrading the SIMOTION devices:
 Adapting the SIMOTION devices supported by libraries

Please check and adapt the specifications for the SIMOTION devices supported by libraries
to the current device versions. These changes must be made manually via the Properties
context menu of the library.
Then save and compile the libraries.
Note that devices older than Version 4.1 are no longer supported as of SCOUT V4.5.
Note:
If devices with versions older than V3.2 are selected in the library, the error message
"Unknown devices" is issued during compilation.
In this case, deselect the appropriate device versions.
 Adaptation of address overlaps

If for diagnostic purposes, you have declared the output addresses of TOs at the same time
again in your I/O addresses, you must assign them the attribute "read-only" there (if not
already so declared).
 Correction of error messages

During the technology package upgrade, sporadically messages such as "Not up-to-date" or
"The setting of property ... has failed" appear. In this case, you must save and compile the
project again at the end of the upgrade.
 Possible structure extension of system variables

It is possible that system variable structures are extended for new SIMOTION versions (for
example for V4.2, the extension of the systemLoad device variable structure with additional
Unrestricted 18
task components). When using such extended structures in the user program, compiler errors
may be signaled after the upgrade.
6.3.5 Download after the upgrade

After the upgrade of the project and the firmware of the SIMOTION device, the project must
be downloaded again to the target device.
6.4 Virtualization platforms and virus scanners

Virus scanners should be deactivated during the installation of SIMOTION SCOUT.
Current information about the supported virtualization platforms and virus scanners can be
found on the SIMOTION product support Internet pages:
http://support.automation.siemens.com/WW/view/en/109743477
Unrestricted 19
8 SIMOTION D V4.5 HF1
8.1 Upgrading the SIMOTION D
Upgrading to V4.5 HF1 via the device update tool
The device update tool can be used for the upgrade to V4.5 HF1.
Details on the use of the update tool can be found in Section 13, "Upgrading via the device
update tool".
Installation notes
The firmware for the SIMOTION D Control Units is supplied on CF Cards:
 CF Card for D410-2 Control Units: Article number 6AU1400-1PA23-0AA0
 CF Card for D4x5-2 Control Units: Article number 6AU1400-2PA23-0AA0
 CF Card for D4xx Control Units: Article number 6AU1400-2PA02-0AA0
pages. Detailed version information about the associated firmware versions can also be found
there.
Note
As of SIMOTION V4.5, the firmware is no longer contained on the SCOUT DVDs.
DVD.
Further information on upgrading and downgrading can also be found in the Commissioning
and Hardware Installation Manuals for SIMOTION D on the SCOUT Documentation DVD
at \Documentation\English\5_SIMOTION_D\
SIMOTION D410 and D4x5

As already announced with SIMOTION V4.3, as of V4.4, no firmware is available for the
SIMOTION D410 and D4x5 Control Units being phased-out.
The previous firmware versions can be found on the SIMOTION product support Internet
pages.
Until further notice, SCOUT versions V4.4 will support the configuration of the
SIMOTION D410, D425, D435 and D445-1 with SIMOTION V4.3 functionality and the
SIMOTION D445 with SIMOTION V4.2 functionality.
The Engineering Framework Totally Integrated Automation Portal (SCOUT in the TIA Portal)
supports only the newer SIMOTION D410-2 and D4x5-2 Control Units. It is not possible to
configure SIMOTION D410 and D4x5 Control Units in the TIA Portal.
Unrestricted 20
8.2 CompactFlash cards with firmware V4.5 HF1
Detailed notes on the "CompactFlash card Boot loader version SIMOTION D hardware
SIMOTION firmware version" compatibility relationships can be found in the software
compatibility list.
The list can be found on SCOUT DVD 1 as well as
and in the Internet at: http://support.automation.siemens.com/WW/view/en/18857317.
Boot loader
We recommend that the latest boot loader is used.
The current boot loader can be loaded with SIMOTION SCOUT and is contained in the scope
of delivery of SIMOTION SCOUT.
Information on how to upgrade the boot loader of a CF card or how to load the firmware to a
CF card can be found in the Commissioning and Hardware Installation Manuals for
SIMOTION D on the SCOUT Documentation DVD at:
\Documentation\English\5_SIMOTION_D\
8.3 Device replacement to SIMOTION D4xx-2
For the changeover from SIMOTION D4x5 to D4x5-2 and D410 to D410-2, see the
Commissioning and Hardware Installation Manuals for SIMOTION D4x5-2 or D410-2,
Migration section.
Components that can be used with SIMOTION D4x5-2

A CBE30-2 can only be used with SIMOTION D4x5-2 DP/PN, and a CBE30 can only be used
with SIMOTION D4x5!
In addition to the onboard PROFINET interface, the CBE30-2 provides a second PROFINET
interface for the D4x5-2 DP/PN. The CBE30-2 cannot be used with the D4x5-2 DP or D4x5.
A CX32-2 controller extension can only be used with SIMOTION D4x5-2, and a CX32
controller extension can only be used with SIMOTION D4x5!
Some "older" DRIVE-CLiQ components can no longer be used with the SIMOTION D4x5-
2/CX32-2 and D410-2. (For details, see the SIMOTION D4x5-2 or D410-2 Commissioning
and Hardware Installation Manual, Section Migration)
Unrestricted 21
10 SIMOTION C V4.5 HF1
10.1 Upgrading the SIMOTION C
Upgrading as of V4.1 SP2 to V4.5 HF1 via the device update tool
The device update tool can be used for the upgrade as of V4.1 SP2 to V4.5 HF1.
A card size of 64 MB is available for the C240. Transfer of the upgrade data via SIMOTION IT
is possible up to a project size of approx. 16 MB.
With immediate effect, newly ordered MMC cards for SIMOTION C240 and C240PN will be
supplied with firmware version V4.5 HF1.
Details on the use of the update tool can be found in Section 13Error: Reference source not
found".
The following installation notes are then not relevant for this.
Installation notes
SIMOTION C240 and C240 PN

Version of the SIMOTION C240 firmware: V4.5 HF1
Revision level V4.5.0.1
The firmware for the SIMOTION C Motion Controller is supplied on MMC cards:
MMC card for C240 / C240 PN Motion Controller: Article number 6AU1720-1KA00-0AA0
pages. Detailed version information about the associated firmware versions can also be found
there.
https://support.industry.siemens.com/cs/ww/en/view/31263919
Note
As of SIMOTION V4.5, the firmware is no longer contained on the SCOUT DVDs.
DVD.
Further information on upgrading and downgrading can also be found in the SIMOTION C
Operating Instructions. The manual can be found on the SCOUT Documentation DVD at:
\Documentation\English\5_SIMOTION_C\
The C230-2 with order no. "6AU1230-2AA01-0AA0" is no longer supported as of the

V4.2 runtime system. However, it can still be configured with SCOUT V4.5 HF1 with a
runtime system < V4.2.
10.2 Upgrading note

Firmware version V4.5 of the production version FS "G" is required for SIMOTION C240/C240
PN to be upgraded. All lower revision levels can be operated only up to firmware version
V4.4.
A special FAQ is provided for version V4.4:

Unrestricted 22
11
Unrestricted 23
12 SIMOTION P V4.5 HF1
12.1 Upgrading the SIMOTION P
SIMOTION P350-3 and P320-3 are supported only by firmware versions ≤ 4.3 and
so no V4.5 HF1 firmware is available. An upgrade to the current version (V4.5
firmware) is not possible.
For SIMOTION V4.5 HF1, the two platforms

 SIMOTION P320-4 Embedded (6AU1320-4DE65-3AF0) and
 SIMOTION P320-4 Standard (6AU1320-4DS66-3AF0)
are released with firmware V4.5.
SIMOTION P320-4
Version of the SIMOTION P320-4 firmware: V4.5 HF1
Revision level V4.5.0.1
The firmware for the P320-4 can be upgraded as follows:
1. Terminate SIMOTION P V4.4 (P State)

2. Start SIMOTION P V4.5 Setup
The SIMOTION P320-4 must be rebooted after a successful upgrade.
12.2 Note concerning the documentation

In the "Operating" Manual of the P320-4, the possible states of the LED L3 are described in
Section 4.4, "Status indicators".
Change:
The function of LED L3 has been omitted. The PROFINET state can be checked via SP state
under Windows.
12.3 Note on the system behavior

The operating system behavior of the P320-4 during the logoff command corresponds to that
during shutdown.
12.4 Note on the Web browser

The current revision level of the Internet Explorer (IE11) is installed for the delivered
SIMOTION P320-4 E/S.
IE11 must be installed explicitly for upgrading the firmware version from V4.4 to V4.5 (V4.4
Image + V4.5 Setup). This means all Web browser functions are supported.
Unrestricted 24
13 Upgrading via the device update tool
The device update tool can be used for the upgrade of SIMOTION devices to V4.5 HF1 as of
V4.1 SP2.
The Firmware Support Package V4.5 HF1 for SCOUT V4.5 HF1 is required for this.
The current Firmware Support Package can be found on the SIMOTION product support
Internet pages.
Please observe the Readme included with the Firmware Support Package.
Note
As of SIMOTION V4.5, the Firmware Support Package is no longer contained on the SCOUT
DVDs.
Note regarding SIMOTION C240:

With the SIMOTION C240 / C240 PN, the function is partly limited due to the memory space
available on the MMC (not with large projects).
14
Unrestricted 25
15 PROFINET with SIMOTION
Important note on the configuration of isochronous I/O devices

As of SIMOTION V4.4, an additional configuration step has been added for the configuration
of PROFINET IO with IRT. In the HW Config of the controller CPU, at the "Object properties"
in the "Isochronous tasks" tab, the setting is made as to whether the servo task is to be
assigned to the PROFINET interface as application level for the processing of isochronous
data:
- If PROFINET I/O devices with isochronous data are to be configured on PROFINET,
the PROFINET interface must first be assigned to the servo at the Object properties of the
SIMOTION CPU in the Isochronous tasks tab (activate the "I/O data isochronously to the
servo" checkbox). Only then can servo be assigned to the device in the "Object properties" of
the PROFINET interface in the "I/O cycle" tab ("Assign I/O device isochronous" list box).
- If no devices are configured with isochronous data on the PROFINET interface, the
PROFINET interface must also not be assigned to the SERVO.
As of SIMOTION V4.4, it is therefore also possible to configure the PROFINET interface of

SIMOTION devices with IRT without the data being transferred isochronously. This means
that the data is transferred synchronously via IRT on the bus, but the applications in
SIMOTION and in the device do not accept the data isochronously. For example, an
ET200HF can be configured with IRT, but the I/O data is not transferred isochronously to the
physical input or output. Or a SIMOTION I-device can be connected via IRT to a higher-level
controller, but the input and output data of the I-device interface is not processed
isochronously by the CPU.
Up to and including V4.3, SIMOTION always performed the communication with PROFINET
IO with IRT isochronously to the servo, even if isochronous mode was not configured on any
PROFINET I/O device.
Odd PN cycle is not possible for an RT I-device

With projects that have been created with a STEP 7 version < V5.5 or opened in STEP 7 as of
V5.5, the following compilation error can occur during processing in HW Config:
"Check consistency (13:5594): The use of odd send cycles is permitted only for configuring
a pure I-device".
Remedy: Open the "PROFINET" tab. The send cycle is then automatically corrected to 1000
µs.
(Note: Even when a send cycle not equal to 250, 500, 1000, 2000, 4000 µs was set in the old
project in the PROFINET tab, the project was processed internally with 1000 µs, i.e. the
project of the higher-level controller does not have to be adapted.)
Compilation error because of bandwidth violation

With projects that have been created with a STEP 7 version < V5.5 or opened in STEP 7 as of
V5.5, a compilation error can occur because of bandwidth violation during processing in HW
Config.
In IRT projects with send cycles not equal to 250, 500, 1000, 2000, 4000 µs, STEP 7 as of
V5.5 reserves a large additional bandwidth for RT in addition to the bandwidth for the IRT
(compared to STEP 7 V5.4). For this reason, it may not be possible to compile the project
because the maximum cyclic bandwidth has been exceeded.
Remedy: Activate the "Permit bandwidth violation" checkbox at Domain management ->
Details.
16
Unrestricted 26
17 Further user notes
17.1 Software product certificate

The software product certificate is part of the general conditions belonging to the scope of
delivery regarding the use of the SIMOTION software.
Please quote the identification number of the software product certificate in all
correspondence.
17.2 Innovations and changes compared to earlier versions

What's new in SIMOTION V4.5 compared to version 4.4?
Information about the new functions of version V4.5 can be found
on SCOUT DVD 1 at: \AddOn\1_Important\English\Features
17.3 Runtime performance

Like every new version, the additional functionality of SIMOTION V4.5 requires a certain
degree of performance. Depending on the constellation and device type, the functions of the
CAM, PATH and CAM_EXT version V4.5 technology packages require approx. 7% greater
performance on average.
For a more accurate performance estimate, use the

SIZER for Siemens Drives configuration tool.
To prevent CPU stops at load peaks (IPO overflows), we recommend that a toleration of level
overflows be set in the IPO cycle. Up to five IPO overflows in succession can be tolerated.
This can be set in the execution system for the IPOSynchronousTask.
17.4 Documentation
The documentation for SIMOTION can be found on the Documentation DVD at
\Documentation.
You require Acrobat Reader to display and print the PDF documents.
After installing SIMOTION SCOUT, the documentation is also available in the SCOUT online
help.
17.5 Online help

Getting Started
The Getting Started provides a brief overview of how you can work with SIMOTION SCOUT. A
typical example shows you the different steps required to create a project, and introduces the
configuration, programming, and diagnostic tools.
You can load the completed SIMOTION SCOUT V4.5 HF1 projects directly from Utilities &
Application for Getting Started (see Section 17.6). Please also take note of the Tutorials on
Utilities & Applications.
Full text search

Enclose the search terms with * in the full text search (e.g. *variable*) to also display results
that contain the search term (system variable, variable assignment, etc.).
Unrestricted 27
A better overview of the titles found is obtained when you click the "Position" column header.
This sorts the titles found according to topic or document.
Context-sensitive online help

You can access context-sensitive help for dialog boxes and windows by clicking the Help
button of the dialog box / window or by pressing the SHIFT+F1 key combination or the "?"
icon in the menu bar and moving the mouse pointer that has changed to a question mark to
the individual parameter or click in the window for which you require help. The F1 key always
opens the entire help of the application. Notes on how to use the context-sensitive online help
can be found on the start page of the entire help (via F1).
FAQ Going online

With the installation of SCOUT, an FAQ Online is also stored on the hard disk of the PG/PC.
You can find this FAQ via Programs > SIMATIC > Documentation > English > SIMOTION
SCOUT manuals. This FAQ can also be opened directly via the SCOUT online help.
The updated version of the FAQ Online can be found in the Utilities & Applications at FAQs >
Engineering > Setting up online connections.
17.6 Sample projects and libraries

The free-of-charge Utilities & Applications provide numerous SIMOTION sample projects,
libraries and a wealth of important information and tools for SIMOTION.
Getting Started
For Getting Started, which is described in the online help, you can load the ready SIMOTION
SCOUT V4.5 HF1 projects directly from Utilities & Applications. You start the navigation by
opening the "index.html" file in the Utilities_Applications directory. The projects can be found
via the main menu "Samples" and submenu "SIMOTION Getting Started".
First copy the appropriate project (ZIP file) to your hard disk (right-click "Destination Save
as..."). Use the sample_c project for the SIMOTION C240 platform, the sample_d project for
the D435 and the sample_p project for the P320-4.
Then use the "Dearchive" function in SCOUT so that the project can be edited in SCOUT.
Note: The trace parameterization is not included in the project. When recording with the trace
function, the parameterization must be performed as described in the online help.
17.7 SIMOTION easyProject ProjectGenerator

The free-of-charge Utilities & Applications also provide the SIMOTION easyProject
ProjectGenerator.
Basic functions required in practically every application can be integrated quickly and easily in
a new or existing project with the aid of SIMOTION easyProject. This saves much
programming time and at the same time creates the preconditions for a uniform and therefore
standardized project structure.
The required functions (standard blocks) are selected and configured via dialog boxes. This
configuration also contains the automatic creation of an HTML page for the diagnostics and
operation of the standard block (option).
The result is a loadable, executable basic project with the basic machine functions that can
already be visualized and operated using a Web browser - without any programming.
An executable project can therefore be created much quicker. The SIMOTION easyProject is
also designed so that you can integrate your own blocks in this generic workflow of the
automatic application creation.
As of SCOUT V4.4, the ProjectGenerator can be called directly via the SCOUT menu.
The SIMOTION easyProject ProjectGenerator cannot currently be deployed with SCOUT TIA.
Unrestricted 28
17.8 HMI configuration
WinCC flexible 2008 SP3 Upd7 has been released for integrated/non-integrated use in
SCOUT V4.5 HF1.
You can find a link to the setup for WinCC flexible 2008 SP3 Upd7 on the SCOUT
Documentation DVD in the WCF_2008_SP3_UPD directory.
Please observe the notes on the installation/uninstallation as described in Section 5.

Before projects that contain a WinCC flexible HMI component (variant integrated in SCOUT)
are downloaded to the target devices, "Save and recompile all" must be performed.
If SIMOTION projects are edited in WinCC flexible standalone, "Regenerate all" must be
triggered.
WinCC flexible
In order to be able to configure a connection to an HMI station in a STEP 7 project with at
least one SIMATIC and one SIMOTION controller in NetPro, WinCC flexible must be closed.
17.9 SIMATIC NET

SIMATIC NET V14 has been released for Microsoft Windows 7 32-/64-bit.
OPC export
The default setting as of SCOUT V4.3 SP1 for the OPC export is the new ".ati" format.
If a project of version V4.1 or V4.2 is to be exported, the format must first be changed
manually to ".sti" so that this project can be imported again with SCOUT V4.1/V4.2.
The OPC export must be performed in the following directory:

Windows 7:
C:\ProgramData\Siemens\SIMATIC.NET\opc2\binS7\simotion\xml\
17.10
Unrestricted 29
17.11 SIMOTION IT
SIMOTION IT functions are included in the standard firmware of the SIMOTION devices.
Associated information and configuration files are stored on SCOUT DVD 1 at
\AddOn\4_Accessories and on Utilities & Applications.
The runtime licenses for SIMOTION IT and OPC XML-DA are required only for
SIMOTION Kernel < V4.2.
Important note:
Some significant changes regarding security have been introduced with the transition from
V4.3 to V4.4. They are described below.
Standard Web pages / FTP / Telnet (TCI)

 There is no longer a standard password for HTTP(S), FTP and Telnet. If users and
passwords have not been created, authentication via these services is not possible.
 The UserDataBase.xml file no longer contains any plain text passwords after ramp-
up.
 The UserDataBase.xml files and the SSL key files are available as separate files.
 The "FTPUser" user group has been replaced by "Administrator".
User-defined pages / JavaScript

 Standard pages have the file extension .mwsl
o Old: "INDEX.MBS" (up to version 4.3)
o New "INDEX.MWSL" (as of version 4.4)
 The HTTP authentication method is "Form-based authentication". The "Basic
authentication" method is only used for downwards compatibility reasons.
o For all *.mbs and *.mcs files
o For OPC XML-DA
 As of version 4.5, downwards compatibility for user-defined Web pages in the old
MBS format can no longer be guaranteed. HTML files must be stored with the *.mwsl file
extension on the memory card.
 The applications for access to the file system via GET and POST requests (e.g. GET
http://<IP>/FILES/myfiles.mwsl) and SERVERPAGES react to unauthorized access with the
HTTP response "302 Object Moved" + login page instead of "401 Unauthorized".
 Changes in the WebCfg.xml file
o Attribute "LOCALLINK" has been replaced by "ALIAS"
o Complete files can no longer be stored in the WebCfg.xml in the form of the
XML file system.
o The "FILTER" attribute has been removed at the MIME_TYPES node.
 During the HTTP communication, an automatically selected BOUNDARY header
must not contain any semicolon. The "945637143527273; charset=UTF-8" boundary used in
the standard pages must be changed if it is used in user pages.
 As of version 4.4, the BROWSEABLE and MODIFY attributes no longer have any
effect on file directories.
Web browser support

SIMOTION IT V4.5 supports current popular Web browsers, such as Mozilla Firefox as of
version 3 and Microsoft Internet Explorer 11 / Edge.
Note for Microsoft Internet Explorer 8 and 9:
In order to be able to use the full functional scope of SIMOTION IT with the Microsoft Internet
Explorer 8 and Microsoft Internet Explorer 9 (transfer of upgrade data), the following setting
Unrestricted 30
must be DEACTIVATED in the browser:
"Options -> Internet Options -> Extended -> Activate original XMLHTTP support"
Upgrade and project update via SIMOTION IT

After an upgrade of the controller, the SIMOTION IT display in the browser must be updated.
To do this, press the F5 key, click the "Reload" button in the toolbar of the browser or close
the browser and open it again.
During a device or project update via SIMOTION IT (Send new update data), the message
"SIMOTION successfully loaded" appears after a successful download of the update package.
If the available memory on the module has been largely used up by the download of the
update package, the memory may not be sufficient for the subsequent unpacking of the
package. This is shown by the associated error message in the system log (ERROR: Could
not decompress archive).
A device (firmware) update via SIMOTION IT is not possible for SIMOTION P.
Upgrading via IT DIAG from V4.1 SP1 to V4.5 HF1

The direct firmware upgrade via SIMOTION IT from V4.1 SP1 to V4.5 HF1 is not possible.
The upgrade from V4.1 SP1 to V4.5 HF1 must be performed via V4.1 SP2 or V4.1 SP4.
WebTraceViewer
The WebTraceViewer has been updated to version V2.4 and is contained in the SIMOTION D
card image as well as in the SIMOTION P firmware. The WebTraceViewer can be installed via
the Trace standard page of SIMOTION IT.
For SIMOTION C, because of the memory size, the WebTraceViewer is not contained on the
MMC card.
The WebTraceViewer is also contained in the SIMOTION Utilities & Applications at:
"SIMOTION IT > Tools and Information > WebTraceViewer".
The SIMOTION Utilities & Applications are on the SCOUT Documentation DVD.
For SIMOTION Runtime V4.5, the new HTML5-based trace visualization embedded in the
standard Web pages of the SIMOTION Web server can now also be used directly.
17.12 Important usage notes

Windows 7
In Windows 7, fonts may be entered in the Registry that are not suitable for the set display
enlargement. This can cause layout errors in the dialog boxes that use these fonts.
Details can be found in the following link:
http://support.microsoft.com/kb/2396756
Online operation
In online operation, SCOUT attempts to conduct online operation with all hardware
components contained in the project. This means that the time needed for going online
increases. We recommend that you make settings for SCOUT so that online operation is
made only with those components currently needed. The setting can be found at "Target
system > Select target devices..." in the menu. The selection and deselection of the devices in
the online state can be made via the context menu on the device.
This procedure (deselection of the online connection to SINAMICS Integrated) is also
advantageous for SIMOTION D when the configuration of the integrated SINAMICS is
completed.
Important note on the use of the axis and drive control panel
Axis control panel in RUN mode
As of V4.4, it is also possible to assume control priority on the axis control panel in RUN
Unrestricted 31
mode.
The user program remains active during the control of the axis.
Please observe the notes provided in the documentation / online help.
The response time from the pressing of the spacebar until the stopping of the axis depends
on the specific project and the system utilization.
The activation of the application monitoring ensures that the axis stops within the set time
even in a system operating at full capacity. If the application monitoring is deactivated, the
stopping of the axis cannot be guaranteed!
Apart from application monitoring, SIMOTION and MICROMASTER also have the so-called
connection monitoring, i.e. the axis is stopped immediately by unplugging the bus connector.
Caution:
SINAMICS drives do not support connection monitoring!
Connection monitoring is only performed based on the technology objects. Only a failure of
the cable is detected in the drive control panel.
Caution:
Neither connection monitoring nor application monitoring are sufficient for safety-critical
scenarios, i.e. in the case of potential dangers for humans and the machine if an axis
continues to turn.
The control panel must not be used in such scenarios.
There must be an EMERGENCY STOP circuit in the hardware.
As of V4.0, abort with "Escape" (Esc) is no longer supported for reasons of harmonization
between the axis and the drive control panel as well as for a uniform procedure for safety
reasons.
Caution:
When using the CP5711 USB PROFIBUS adapter and the axis control panel, SCOUT
sporadically no longer responds to user entries (e.g. update of alarms, switching modes to
traverse the axis). Any potential rotating axis can, however, still be stopped using the space
bar.
This behavior is possible when using the CP5711 USB PROFIBUS adapter.
System variables changed online:

If system variables changed online are to be saved in the project, they must be entered again
in the offline view.
After a project download and "Copy RAM to ROM", the changed values are also stored as
non-volatile data in the device (on the memory card).
MCC - single step for know-how-protected subprograms

If a know-how-protected subprogram is called in single step mode without entry of the
password to cancel the know-how protection, the commands contained in the subprogram are
automatically advanced by the system. This requires a certain execution time, depending on
the scope of the subprogram, during which you have to wait.
The MCC function Stepping is also available as of V4.4; the wait time is omitted here.
Pragmas in MCC and LAD/FBD declaration tables

As of SIMOTION SCOUT V4.2 SP1, pragmas are possible in MCC LAD/FBD declaration
tables. These pragmas are only copied when entire UNITS are copied.
When individual lines are copied from a declaration table, the pragmas must subsequently be
created again manually.
Distance-coded measuring systems

In contrast to SINAMICS, distance-coded measuring systems cannot be used on the linear
motor.
"High-priority ramp-up" for GSD files
Unrestricted 32
The "High-priority ramp-up" setting can be activated in GSD files.
This mode, however, is not supported as controller or I-device for SIMOTION.
Use of the ET200SP and ET200MP timer DIDQ module

Requirements for use:
SIMOTION SCOUT/ FIRMWARE as of V4.4 HF6
o SIMATIC ET 200SP Interface Module as of V 3.1 in version HF
o SIMATIC Step7 as of V5.5 SP4 and installation of the corresponding HSP file
as of HSP240_V2.2
SIMOTION SCOUT TIA/ FIRMWARE as of V4.4 HF6
o SIMATIC ET 200SP Interface Module as of V 3.1 in version HF or
SIMATIC ET 200MP Interface Module in version Standard/HF
o TIA Portal as of V13 SP1 as of Update 2
Attached are the latest Hardware Support Packages for STEP 7 ready for downloading:
17.13 Important note for use as of STEP7 V5.5 SP3

SIMATIC STEP 7 V5.5 SP4 must be installed on the PC as the runtime environment for
SIMOTION SCOUT.
As of STEP7 V5.5 SP3, any configured access address is evaluated when you go
online.
This address takes precedence over the configuration in HW Config/Netpro.
Where is the access address set?

The following dialog is opened via the shortcut menu of the CPU "Target device > Online
access...":
Any selection of an entry with subsequent confirmation of the dialog with "OK" is stored as
access address in the STEP7 project database. This applies to all previous SIMOTION and
STEP7 versions. As of STEP7 V5.5 SP3, this data is evaluated for the first time by STEP7
itself.
If an access address is defined, this takes precedence as of STEP7 V5.5 SP3 over the
configuration in HW Config/Netpro, and an online connection might not be established.
As of SIMOTION SCOUT V4.3 SP1 HF12, the following sentence is displayed in the output
Unrestricted 33
window for improved transparency in the event of a fault (if an access address is configured):
"Access address <192.168.213.1> has been used to establish the connection"
As of V4.3 SP1 HF12, SCOUT provides a new function for deleting the access address. You
can access this via the shortcut menu of the CPU "Target device > Delete access address".
After deleting the access address, going online then takes place in accordance with the
configuration in HW Config/Netpro.
17.14
Unrestricted 34
17.15 Notes for SINAMICS Safety Integrated in
conjunction with SIMOTION
The software requirements for the use of PROFIsafe in conjunction with SIMATIC F-CPUs
and SIMOTION/SINAMICS are:
S7 F ConfigurationPack V5.5 SP11 and Distributed Safety V5.4 SP5 Upd1.
S7 F ConfigurationPack V5.5 SP11 can be found as download in the Siemens Industry Online
Support at http://support.automation.siemens.com/WW/view/en/15208817
Important notes for the upgrade
SINAMICS Safety Integrated functionality for basic functions via PROFIsafe

If a SIMOTION D4xx module is replaced by a SIMOTION D4xx-2 module and therefore the
SINAMICS firmware upgraded from V2.x to V4.x, a zero in the delay time of SS1 is now
evaluated as "Shutdown of the function".
Consequently, no safety function is executed!
With V2.x, the secondary function "STO" (analog to the terminal functionality) is selected
directly with a delay time of "zero".
Memory cards with several configurations and Safety configurations

Note the information in the SIMOTION Basic Functions for Modular Machines Manual in
Section 6.1 Activating a configuration
18
Unrestricted 35
19 General conditions and function
restrictions
19.1 General conditions and function restrictions with
V4.5 HF1
The complete general conditions for V4.5 HF1 can be found on SCOUT DVD 1 at:
\AddOn\1_Important\English\General conditions
Note
The SINAMICS commissioning tool STARTER V4.5 SP1 is integrated in SIMOTION SCOUT
V4.5. For further information concerning the deployment conditions, see the Readme and the
general conditions list for STARTER V4.5 SP1.
19.2 General conditions corrected with V4.5 HF1

The general conditions corrected with V4.5 HF1 are contained in the list of corrected general
conditions at: \AddOn\1_Important\English\General conditions
19.3 SINAMICS general conditions

A SINAMICS drive control is integrated in the SIMOTION D Control Units. For this reason, the
SINAMICS general conditions always apply to SIMOTION D.
This means:
 CU310-2 general conditions always apply to D410-2
 CU320-2 general conditions always apply to D4x5-2/CX32-2
 General conditions for further components such as TMs, SMCs, etc. also
apply for the connection to SIMOTION D
The SINAMICS general conditions are described in the associated SINAMICS publications,
e.g. on the Internet product support pages:
https://support.industry.siemens.com/cs/ww/en/ps/13229/dl
20
Unrestricted 36
21 Changes in behavior as a result of error
corrections
21.1 Changes in behavior as a result of error

corrections
as of V4.5 HF1
DRIVE-CLiQ communication time with TM31 and TM15 DI/DO

As from SINAMICS V4.8, the value of p4099 is considered for the DRIVE-CLiQ
communication time with TM31 and TM15 DI/DO.
In case of p4099 values > 250 µs, it may occur that delay times are extended compared to the
previous version.
We recommend that you reduce the value entered in p4099.
SCOUT TIA: Display of PROFINET ports of S120 CU320-2 PN modified into HWCN
As from SCOUT TIA V4.5 (TIA Portal V14), the PROFINET port P1 is displayed below and the
port P2 above in the device and topology view. This corresponds to the actual arrangement
on the CU.
The modified sequence must be considered when graphically switching the topology.
Acknowledgement of Alarm 50007

As from SIMOTION V4.5, the function _resetTechnologicalErrors() acknowledges the already
reported alarm 50007.
Up to and including SIMOTION V4.4, the alarm could not be acknowledged.
Alarm 40201 - Synchronization tolerance exceeded at gearbox axis

In rare cases, no alarm was output up to Version V4.5 when calculating the synchronization
tolerance with exceeded values.
Upwards synchronization with dynamic default with gearing

In rare cases, the device was synchronized upwards up to V4.5 although the preset dynamic
values have been exceeded.
In V4.5, the values are checked more exactly with regard to violation of the dynamic
response, and if the dynamic response does not suffice for the upwards synchronization, the
device is not synchronized upwards until the next cycle.
Unrestricted 37
21.2
Unrestricted 38
corrections
as of V4.4 HF1/2
Changed behavior of the TO status variables at the removal of the axis enable
As of V4.4, the system support for brake control is activated for newly created axes.
Therefore, at the removal of all axis enables (_disableAxis, RELEASE_DISABLE), first the
brake is closed and then the power disconnected. This results in a changed chronological
behavior of the "actormonitoring.power" and "actormonitoring.drivestate" system variables.
During the transition to state S5 (Switching off), the "actormonitoring.power" system variable
is set to INACTIVE, and only after the closing of the brake in the S1 or S2 (Ready for
switching on) state are the remaining enables removed and therefore the
"actormonitoring.drivestate" system variable set to INACTIVE.
Up to and including V4.3, "actormonitoring.drivestate" was set first to INACTIVE and then
"actormonitoring.power".
Save as
When executing the SCOUT function "Save as", the project is saved directly with the new
specified project name.
Previously, the open project was first saved, and then copied under the new specified project
name.
Temporary IP address
For the IP address assignment on a PROFINET device (via DCP), the PROFINET standard
offers the following options:
 Permanent IP: The device retains the IP address after Power OFF/ON.
 Temporary IP: The device has "forgotten" the IP address after Power OFF/ON
and no longer has an IP address.
Previously, with the "Temporary IP" option, the old IP address that was present before setting
the temporary IP would be activated again after Power OFF/ON.
As of V4.4, the PROFINET controller always assigns a temporary IP during ramp-up with the
"Temporary IP" option. This ensures that when a device is removed and installed at a different
location, it no longer has an IP address and no IP address conflicts occur in the factory.
totalOffsetValue for absolute adjustment

totalOffsetValue is no longer summed up.
Minimum factor for the ratio of Servo_fast to Servo increased from 2 to 4

Servo_fast must be at least 4-times faster than Servo at 125 µs and 250 µs.
For the cycle clocks >250 µs, the minimum factor remains 2.
Upgrade from V4.3 to V4.4 for applicative use of DSC spline

If DSC spline is activated on the drive, but the TO configuration data enableDSCSpline =
BY_APPLICATION is not set, SIMOTION generates a PROFIdrive telegram 125 for the axis
as of V4.4 when "Symbolic assignment" is activated in the project. This may cause errors in
the consistency check and you must adapt the configuration (e.g. set the telegram
configuration to "user-defined").
Weighting factor for analog sensors

The scaling or conversion in the value of the configuration data ConversionData>factor for the
position of the analog sensor has changed in V4.4.
Unrestricted 39
As of V4.4, the values are entered directly in INCH and no longer converted from MM to INCH
for the configured INCH unit system.
This can result in a higher velocity being detected (by a factor of 25) if it is an axis that works
in INCH.
Up to V4.3, the values were entered in MM and then converted to INCH (1 INCH corresponds
to 25 MM).
Please check the values entered for "factor" in older projects and correct them when
necessary.
Change of the condition for starting a UserInterruptTask

Unit variables from the interface section of a program source can be specified as condition for
starting a UserInterruptTask (via formulas).
When upgrading the device to a SIMOTION Kernel version as of V4.4, you may have to adapt
the syntax of the start condition.
 Up to and including SIMOTION Kernel V4.3:
Only specification of the variable name <VariableName>.
 As of SIMOTION Kernel V4.4:
The program source must also be specified in the form _device\<UnitName>.<VariableName>
(example _device\mySourceFile.myVar).
As previously, global device variables can only be specified directly via the variable names.
Measurement job with _enableMeasuringInput temporarily in the WAITING status

Previously, a measurement job issued with _enableMeasuringInput was immediately set to
the ACTIVE status.
As of V4.4, the command status is set to WAITING between the issuing and processing of the
command. As soon as the command is processed by the TO, the status is ACTIVE.
The status can be determined with the _getStateOfMeasuringInputCommand command.
The measuring input command now behaves identically to all other commands.
False polarity of the HW limit switches only returns alarm 50007

When a HW limit switch is overtraveled, false polarity of the HW limit switch wiring may be
detected.
Alarm 50007 "False polarity of the limit switch (can only be cleared with a new technology
object configuration or Power On)" which is issued, can longer be acknowledged as of V4.4.
The error state must be corrected before the axis can be traversed again.
Results of the (L)REAL <-> STRING conversions standardized

(L)REAL_TO_STRING:
Change of the output decimal places:
REALs 10 significant decimal places, LREALs 17 significant decimal places.
This results in a longer output string than previously for most values. Fewer positions than
previously are only output for the LREAL values between 1.0e11 and 1.0e16.
During the conversion with REAL_TO_STRING of positive integers in the range 1.0e00 ..
1.0e06, the result string contained no decimal places. These numbers are now also output
with 10 significant places, i.e. with the corresponding number of zeros after the decimal point.
REAL_TO_STRING:
Values in the range -1.0e10 .. -1.0e-04 and 1.0e06 .. 1.0e10 are now converted to decimal
representation (as previously also values in the range 1.0e-04 .. 1.0e06).
Exponential representation uniformly with lower-case e (previously for positive numbers up to
1.0e16 with upper-case E).
LREAL_TO_STRING:
Values in the range -1.0e16 .. -1.0e-04 are now converted to decimal representation (as
previously also values in the range 1.0e-04 .. 1.0e16).
STRING_TO_LREAL:
If the string contains invalid characters or has an invalid format, TSI#ERRNO is no longer set
to 3 when a valid number is detected at the start of the string.
Unrestricted 40
Differences (to older versions) are possible as of the 16th decimal place.
21.4 Changes in behavior as a result of error corrections

as of V4.3 SP1 HF9
Following value for absolute camming with slaveMode:=ABSOLUTE

Up to and including V4.3 SP1 HF3, a random offset could occur for the absolute position of
the following axis.
As of V4.3 SP1 HF9, the following axis takes up the exact absolute position after the
synchronization.
Absolute synchronous operation in the case of previously speed-controlled traversing

of the following axis
Up to and including V4.3 SP1 HF3, only a relative synchronous operation has been activated
in the case of a substituted absolute synchronous operation command to a following axis
moved with _move(SPEED_CONTROLLED). The consequence of this was, for example, that
the following axis remained in its last position with a stationary master value.
As of V4.3 SP1 HF9, an absolute synchronous operation is activated according to the
programmed synchronous operation command. As a consequence of this, for example, with a
stationary master value, the following axis now positions itself at the absolute position of the
master value.

as of V4.3 SP1 HF3
Dynamic response adaptation for path interpolation

The command for dynamic response adaptation of the path interpolation results in a greater
load in the interpolator cycle clock. Previously, the dynamic response adaptation had no
effect.
Display of the dynamic path response adaptations

The system variable on the path object path.dynamicAdaption (specifies whether path
dynamic response adaptations are active/inactive) displayed the programmed behavior up to
now and was therefore not very useful.
As of V4.3 SP1 HF3, only the effective behavior is displayed.

as of V4.3 SP1 HF1
Function of the mode selector switch in SCOUT

The "MRES" function of the mode selector switch in SCOUT only functions when the "STOP"
operating state has been selected first. The "MRES" button is grayed-out in the "RUN" and
"STOP U" operating states and therefore has no effect.
In previous software versions, a message was output that "MRES" is only possible in the
"STOP" operating state when the "MRES" button was clicked in the "RUN" and "STOP U"
operating states. This message is omitted in V4.3.
Search via "Accessible nodes"

If a SIMOTION device is found via "Accessible nodes", the IP address of the device is
Unrestricted 41
displayed twice in the "Assign Target Devices" dialog box in certain situations. This is always
displayed in V4.3 when the networking allows access to the device via two different paths
(direct and routing). In V4.2 only direct accessible nodes were found. Nodes that could be
accessed via routing were not displayed. The search algorithm has been improved in V4.3
and nodes can now also be found via routing.
Changed return values of the system functions

_getStateOfSingleDPSlave and _getStateOfAllDPStations
Concerns the querying of the interface status of your own I-device configuration (not the
placeholder via GSDML) which has not yet established a connection to a master.
_getStateOfSingleDpSlave:
Old behavior: NOT_PRESENT
New behavior: IN_OPERATION
Reason: Communications interface is ready to establish a connection. Therefore
IN_OPERATION.
_getStateOfAllDpStations:
Old behavior: IN_OPERATION
New behavior: DISTURBED
Reason: Communications interface is ready to establish a connection, but as the peer
is not connected yet, the configured I/Os are disturbed.
The cumulative status is therefore DISTURBED.
Please also note the FAQ at
http://support.automation.siemens.com/WW/view/en/10805457/133000

as of V4.2 SP1
Project-wide unique logical addresses of the PROFIsafe slots
As of SIMOTION SCOUT V4.3 SP1 HF1 in conjunction with the versions of the F-
Configuration Pack released for this, the behavior is the same again as before version V4.2
SP1.
This means that PROFIsafe slots of the SIMOTION devices (SINAMICS Integrated) can have
the same logical addresses again.
PLCopen block _MC_POWER

Previously the Mode=Drive could not be used usefully.
As a result of the error correction, Mode=Drive now switches on the drive (incl. power) STW1
Bit0-Bit6 (previously STW1 Bit4-Bit6 was set / no power).
A more precise description of the input and output parameters can be found in the document
for the new functions of version V4.2 SP1 (on SCOUT Add-ons at
\AddOn\1_Important\English\Features).
PLCopen block for external encoder

When the enables of an external encoder are removed, the system variable
motionstate.velocity is also set to 0 as soon as control = INACTIVE.
PLCopen block _ MC_CamOut

Previously, desynchronization was performed immediately, irrespective of the specified
desynchronization position of the master value.
Torque limiting B+/B- is limited to the maximum reference torque

As of V4.2, with activated torque limiting B+/B- (_enableAxisTorqueLimitPositive() /
_enableAxisTorqueLimitNegative()), the maximum value set in ~.DriveData.MaxTorque or
MaxForce is transferred to the drive with the setting
TypeOfAxis.SetPointDriverInfo.DriveData.torqueReference = MAX_VALUE.
In the versions <V4.2, up to 200% of this value was possible with activated torque limiting.
Unrestricted 42
If the torque limiting function B+/B- is not activated, the maximum value set in ~.MaxTorque is
transferred in V4.2 as well as in versions <V4.2.
As the 100% reference value must be set in ~.MaxTorque for the torque transfer to the drive
with the setting ~.torqueReference = MAX_VALUE, i.e. the value corresponding to P2003
(reference torque), a larger maximum torque may be possible in the drive, corresponding to
the value in P1520 (maximum torque).
The separation between reference and maximum torque was introduced in the reference
variables with V4.2.
For projects that are converted up to V4.2, the new configuration data item
~.torqueReference is set to MAX_VALUE. In this way, only the reference torque value can be
set as maximum torque limiting without changing the project.
Workaround:
If, with activated torque limiting, a value greater than the reference value in P2003 is to be
transferred to the drive, ~.torqueReference = NOMINAL_VALUE must be set, the value
corresponding to P2003 entered in ~.NominalTorque and the value corresponding to P1520
entered in ~.MaxTorque.
If the torque limiting function B+/B- is deactivated, the value set in MaxTorque is transferred to
the drive.
For new TOs created in V4.2, ~.torqueReference = NOMINAL_VALUE is set as well as the
reference values for ~.NominalTorque and ~.MaxTorque transferred from the drive during
runtime, for the adaptation set per default.
CASE statements with floating-point values

Previously it was possible to compile the following construct error-free, even though the
selector must be of the ANY_INT or enumeration data type:
CASE real_var OF
1: ;
ELSE
;
END_CASE;
An alarm is issued with V4.2 SP1. However, if the value is also specified as a floating-point
value in the value list (e.g. 1.0: ;), an error message is issued.
Faulty reference to an FB from an MCC chart

If a chart that has previously been used as a subprogram is moved to a library, the calling
blocks are then no longer correct (also applies when a library block is moved to a chart).
The compiler cannot detect the error during compilation, because the entered block call
commands are correct.
After moving, the calling blocks must be modified.
To do this, open the appropriate calling block in each chart with the FB call.
The previous configuration is now visible.
Change the entries as follows:
- Instead of "Function" -> "Library function"
- Instead of "Function block" -> "Library function block"
- Instead of "Program" -> "Library program"
Then select the relevant library in the combo box that appears.
Click the "Update" button.
The declaration locations of the data types are still in the fields as comments for the data
types. If required, these entries can be changed manually.
Close the dialog box with "OK".
Changing MCC units through compiler settings in the debug mode

Editing can also be performed in the debug mode in the ES with Version 4.2. To do this, the
debug mode is first deactivated in the RT after a prompt for the user, and stopped tasks
continued.
It is also possible however to change the source text of a unit through compiler settings, such
as program status, single step or trace. The unit becomes inconsistent online after 'Save and
compile' and cannot be loaded during RUN mode.
The debug mode must be exited before compiler settings are changed. To do this, the
Unrestricted 43
operating mode must be changed on the CPU.
MCC units with distributed synchronous operation for V3.2

Projects of Version 3.2.x that contain a distributed synchronous operation and reset the
master value of a master controller in MCC commands, cause errors when opened as of
SCOUT V4.2.1. The corresponding commands must be adapted manually (commands are
displayed for a consistency check and when saving and compiling the relevant unit).
If the project is then to be processed further in V3.2, the synchronous operation commands
have to be adapted again with SCOUT V3.2 after the "Save in old project format".
Upgrade project from SCOUT V3.2 with distributed synchronous operation - MCC
sources
Projects of Version 3.2.x that contain a distributed synchronous operation and reset the
master value of a master controller in MCC commands, cause errors when opened as of
SCOUT V4.2.1. For this reason, the corresponding commands must be adapted manually
before upgrading (commands are displayed for a consistency check and when saving and
compiling the relevant source).
Compilation behavior between ST and MCC/LAD/FBD has been aligned

The compilation behavior has changed from V4.1 to V4.2. In V4.1, a smart compile was
performed to make the variables known to the system when saving a unit in MCC and
LAD/FBD. The result was that the unit became inconsistent online without compilation. The
behavior in V4.1 was therefore different between ST and the graphic languages.
In V4.2, the behavior between ST and the graphic languages has been aligned. Newly
created variables only become visible in the symbol browser when the unit has been
compiled.
Maximum size of script files in SCOUT

Because of a change in the Windows mechanisms of Microsoft, the maximum size of script
files has been limited to 1 MB. This means that scripts with a file size greater than 1 MB
cannot be opened or saved in SCOUT V4.2. Therefore, before upgrading in SCOUT versions
before V4.2, check whether this size has been exceeded by script files. In normal script files,
this size is reached at approx. 10,000 lines of code (with 100 characters per line).
Checksums of the safety program must be regenerated

Because of an error correction of STEP 7, the safety program must be regenerated after the
upgrade of a V4.1.x project with PROFIsafe communication to V4.2.1.
Project-wide unique logical addresses of the PROFIsafe slots

Only the F-Configuration Pack V5.5 SP8 has been released with SIMOTION V4.2.1.
If several intelligent DP slave couplings are made on an F-CPU with this F-Configuration Pack
in V4.2.1, FMS couplings cannot be created for either V4.1 devices or V4.2 devices, when the
PROFIsafe slots of SIMOTION devices (SINAMICS Integrated) have the same logical
addresses (e.g. as is the case with: SIMOTION D is configured completely and an additional
SIMOTION D is inserted in the project using Copy/Paste).
This was possible in V4.1 with the F-Configuration Pack V5.5 SP5.
For this reason, project-wide, unique logical addresses must be assigned for the PROFIsafe
slots in SIMOTION SCOUT V4.2.1 when new PROFIsafe slots are created or added,
irrespective of the used device version.
Upgrade of ET200HS from V2.0 to V3.0

A SIMOTION CPU V4.2 can only be used with an ET200HS of Version 3.0. During a module
replacement of the ET200HS in HW Config (to upgrade the ET200HS from V2.0 to V3.0), HW
Config closes without a message.
The ET200HS cannot be upgraded through a module replacement. The module must be
deleted manually in HW Config and then created again with the desired version.
Unrestricted 44
as of V4.1 SP5
"Opening of a command block that is no longer up-to-date" message in MCC libraries
The above message can appear when opening an MCC command in an MCC library, which
indicates that the technology object used therein has been changed.
Background:
The contents of the MCC screen forms for the technology commands depends on the
properties of the technology objects used therein. For example, the screen form for the MCC
command "Output cam on" is totally different depending on whether the output cam is
assigned to a linear or a rotary axis.
When using technology commands in libraries, technology objects are not specified directly,
but only via variables (variables of the data type of the technology object). A technology object
is only assigned to variables during the runtime of a program.
For this reason, it is sufficient for some commands, e.g. for "Output cam on" or "Synchronous
operation on", to only enter "<Reference>" in the "Axis" or "Following Axis" dialog box,
because a variable of the output cam type is only linked to a real axis during runtime and an
axis variable does not have to be entered specifically for the command parameterization (see
also MCC Programming Manual, Section 4.4.3.2 Using variables of the technology object
data type).
Previously in MCC commands, a variable of this technology object data type could also be
entered here instead of "<Reference>", even though this was not relevant in the libraries and
had no effect.
As of V4.1 SP5, the <Reference> is automatically entered in the input field instead of the
name when a command is opened. However, with some commands, the above message
appears.
Procedure:
With "Yes", there is an update with the entry of <Reference>.
With "No", there is no update in the screen form. The "Update" button is then displayed in the
opened MCC command, and can be used for the subsequent update to <Reference>.

corrections
as of V4.1 SP4
Changed behavior for output variables and error analysis of the PLCopen blocks
As part of the error correction, the behavior of some output variables and the error outputs of
the PLCopen blocks has been changed (applies to the InVelocity, InGear, InSync, Error, Error
ID and Command Aborted). Previously the behavior of the error outputs was not clear and not
adequately documented.
With SCOUT V4.4 HF1, you can directly specify the behavior of the PLCopen blocks for
devices of version V4.1 by specifying the TP product version of the CAM/PATH/CAM_EXT
technology packages.
All SIMOTION devices of version V4.3 have this new behavior.
For more detailed information, refer to the FAQ PLCopen in the SIMOTION Utilities &
Applications or at http://support.automation.siemens.com/WW/view/en/37865127
Changed behavior for PLCopen block _MC_STOP

The output bit "Active" remains TRUE as long as the block is being processed (the disable for
motion commands is active). The block is only terminated when "Execute" = FALSE. The
outputs "Done" and "Active" are then set for one cycle.
The changed behavior corresponds to the documentation.
Unrestricted 45
Linear measuring system with configuration of 25-bit message length and 24-bit data,
right-justified
Up to V4.1 SP4, the value was calculated twice on the TO with a configuration of 25-bit
message length and 24-bit data, right-justified, as the offset of one bit (25 - 24 =1) was not
taken into account. Twice the traversing distance is then shown in the display.
Upgrade from V4.1.x.x to V4.1.4.1 or higher:
The offset is now taken into account. The grid line spacing value on the encoder should be set
to that on the data sheet. The grid line spacing is now calculated correctly.

corrections
as of V4.1 SP2
Calculation results with constant expressions
As of SIMOTION SCOUT V4.1 SP2, there is a different behavior as a result of an error
correction on the compiler.
The old behavior was not correct for calculation results with constant expressions and also
did not comply with the IEC. This was corrected with SIMOTION SCOUT V4.1 SP2.
For more detailed information, see the FAQ at
Changed behavior with "global measuring inputs"

As part of an error correction, the measuring position for global measuring inputs was applied
to the value before the filter of the actual position. The actual position belonging to the
measuring event is now measured exactly.
If a position measuring value in relation to the filtered actual position is still required, see FAQ
at http://support.automation.siemens.com/WW/view/en/37945244

corrections
as of V4.1 SP1
Changed comparison operator in V4.1 SP1
In versions < V4.1, the operator notations ">=" and "=>" could be used for the "greater than or
equal to" comparison function. In V4.1, the notation "=>" is no longer permitted for the
comparison. If a SIMOTION CPU is used in the project with a firmware version lower than
V4.1, SIMOTION SCOUT issues an alarm at the places where "=>" is found during the
compilation. The project can be used as such and loaded.
If a SIMOTION CPU is used in the project with firmware version V4.1, SIMOTION SCOUT
issues an error at the places where "=>" is found during the compilation. The assignment
operator must then be changed from "=>" to ">=" so that the project can be loaded to the
SIMOTION CPU.
When version-neutral libraries are used, the syntax check remains as for CPUs with V4.0 and
lower. The operator with the "=>" notation can be retained. An alarm is issued during
compilation.
Behavior of OFF2/Bit1 in CTW1

Previously, when the controller was already in closed-loop control, explicit/exclusive setting of
OFF2/Bit1 and/or OFF3/Bit2 and subsequent removal of the signals again without
cancellation of the switch-on inhibit (edge change at CTW1 OFF1/Bit0), there was an
immediate return to closed-loop control.
As of V4.1 SP1, the switch-on inhibit must be cancelled explicitly, i.e. an edge change created
at STW1.Bit0 by the user. Therefore, a _disableAxis (disableMode=ALL or
disableMode=POWER) or an explicit cancellation is required, before STW1.Bit0 is set again
with _enableAaxis (enableMode=ALL or enableMode=POWER) or explicitly.
Unrestricted 46
Programs/FBs and global device variables with same name
If in programs or FBs (e.g. with name FOO) a global device variable with the same name (e.g.
FOO) was accessed, the V4.0 compiler issued a warning in this case (program name hides
global variable). This is illegal programming in ST, but could still be retained in V4.0.
This name assignment is not permitted as of V4.1 SP1 and the compiler issues an error
message.
Error message 6003: ''%s'' is not a variable identifier
Checking of the max. speed at project upgrade from V4.0 to V4.1 SP1 and higher
Maximum speed greater than 2 x reference speed:
In V4.0, a value greater than 2 x reference speed could be specified for the maximum speed
in the motor data during the configuration of an axis. However, the transfer of a higher value
(than 2 x reference speed) to the drive was not possible in V4.0 because of the PROFIdrive
profile.
As of V4.1 SP1, an error (20006) is output in this case (maximum speed is greater than 2 x
reference speed) at a download or restart. The value of the maximum speed must be
corrected when this error occurs.
MCC: Effect of activation of "Reset master value"

Up to and including V4.0, a synchronization command (synchronous operation / cam on) with
new master caused an immediate switchover to the new master.
As of V4.1 SP1, this switchover is only after the synchronization command has taken effect.
Torque limiting B+/B-

If the manipulated variable is inverted on the Axis technology object, then B+/B- are also
reversed on the Axis technology object.
You must take this into account when specifying the torque limits B+/B-.
Configuration data for extrapolation filter

The default setting of the configuration data for the extrapolation filter of the actual velocity
value (TypeOfAxis.Extrapolation.Filter.mode = default_mode) has been changed.
For V4.0: Averaging (ratio of interpolator cycle clock to position control cycle clock relevant)
For V4.1: No filter (actual velocity not smoothed)
Background to the change: A filter setting should not be determined depending on other
variables (IPO/servo ratio in this case).

corrections
as of V4.0
Clear, uniform behavior of INT_TO_TIME with negative numbers:
INT_TO_TIME(-1) = T#49d_17h_2m_47s_295ms (and not T#1m5s535ms as previously)
Therefore equivalent to:
INT_TO_TIME(-1) = T#1ms - T#2ms = T#49d_17h_2m_47s_295ms
Uniform behavior at abort of technological functions

The technological functions for torque reduction, additive torque and torque limits (B+/B-) are
not aborted when the axis controller enable is removed (_disableAxis). These are then still
effective after a renewed axis enable (_enableAxis). Abort however through the appropriate
_disableTorque… commands, _resetAxis, _restartAxis, … and at transition to STOP.
Cam track with start mode "With next track cycle"

The behavior of the TO camTrack has been changed as follows with V3.2 SP1 / V4.0:
The TO camTrack with start mode "With next track cycle" is started
- From the axis reference position (with positive traversing direction) or
Unrestricted 47
- From the end position of the cam track (with negative traversing direction)
and executed once or continued cyclically depending on the activation mode.
This can result in a different system behavior for certain scenarios.
If the original behavior is to be restored, this must be performed in the application.
End
Unrestricted 48

Readme

Uploaded by

Copyright:

Available Formats

Readme

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

Readme

Uploaded by

Copyright:

Available Formats

SIMOTION

and SIMOTION Runtime Software for

SIMOTION C V4.5 incl. HF1

Version V4.5 HF1 runtime/firmware is the first release of SIMOTION V4.5.

2.2 General notes

Information about SIMOTION in the Online Support

This recommendation does not apply to the SIMOTION P.

2.5 Software compatibility

2.6 Test certificates

DVD name Directory on the DVD Contents

SCOUT V4.5+ HF1 InstData SIMOTION complete setup

Addon SIMOTION AddOn V4.5 HF1

SCOUT V4.5 + HF1 Documentation V4.5 HF1 documentation

SCOUT TIA V4.5 + SIMOTION complete setup

SCOUT V4.5 HF1 DVD 1

Root directory, SCOUT complete setup

InstData, HELP SIMOTION SCOUT V4.5 HF1

AddOn V4.5 HF1

SIMOTION Extensions CamTool V3.0 SP3 HF2

In both cases, CamTool must be licensed separately.

SSP_... SINAMICS Support Package

SCOUT Documentation and Utilities DVD 2

STEP7 V5.5 SP4 HF11

WCF 2008 SP3 Upd

Limitation of liability for Utilities & Applications

German law applies. The Erlangen courts have exclusive jurisdiction.

SCOUT TIA V4.5 HF1

Root directory, SCOUT TIA complete setup

4 Third-party software - License conditions

Special note for resellers:

6.1 Installation of SCOUT TIA

6.2 Installation of SCOUT

6.2.1 Hardware requirements

Recommended hardware requirements:

6.2.2 Memory requirement

An important requirement for the installation is that there is at least 3 GB of temporary

6.2.3 Software requirements

6.2.3.2 Runtime environment

Please note the important note in

The software requirements for the deployment of PROFIsafe in conjunction with

There is no guarantee of executability in a SW configuration other than that specified above.

The SCOUT installation must not be interrupted by a computer restart.

Installation of WinCC flexible

Installation of SIMOTION SCOUT

It consists of the following products:

Installation of Automation License Manager (ALM) V5.3 SP3 Update 1

Installation of Drive Control Chart (DCC)

With SCOUT V4.5 HF1, DCC SIMOTION/SINAMICS is installed automatically with

Engineering licenses are required to use the DCC SIMOTION/SINAMICS functions.

If DCC SIMOTION/SINAMICS is to be installed in a STEP 7 environment with CFC for

Installation of the SIMOTION Task Profiler

Information on user entries required during setup

Interruption of the installation through a restart

6.2.6 Authorization of SCOUT

There are two ways to perform the authorization:

During the setup:

After the setup:

6.3 Upgrading projects to

6.3.1 Supported versions