SAT UserGuide en-US
SAT UserGuide en-US
Supported devices
7
Advanced features
9
Additional features
10
Reference information
12
DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.
CAUTION
indicates that minor personal injury can result if proper precautions are not taken.
NOTICE
indicates that property damage can result if proper precautions are not taken.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will
be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to
property damage.
Qualified Personnel
The product/system described in this documentation may be operated only by personnel qualified for the specific
task in accordance with the relevant documentation, in particular its warning notices and safety instructions.
Qualified personnel are those who, based on their training and experience, are capable of identifying risks and
avoiding potential hazards when working with these products/systems.
Proper use of Siemens products
Note the following:
WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended or
approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and
maintenance are required to ensure that the products operate safely and without any problems. The permissible
ambient conditions must be complied with. The information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of Siemens AG. The remaining trademarks in this publication
may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software
described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the
information in this publication is reviewed regularly and any necessary corrections are included in subsequent
editions.
4 Device operations............................................................................................................................... 15
4.1 Scanning a network.......................................................................................................... 15
4.2 Pinging devices for a network connection.......................................................................... 20
4.3 Inserting one or more devices........................................................................................... 20
4.4 Trusting CPUs with certificates for secure communication.................................................. 25
4.5 Identifying devices............................................................................................................ 26
4.6 Showing device diagnostics.............................................................................................. 27
4.7 Reading a device's service data.......................................................................................... 29
4.8 Setting a CPU's operating mode......................................................................................... 30
4.9 Setting a CPU's time.......................................................................................................... 31
4.10 Setting an IP address......................................................................................................... 31
4.11 Setting a PROFINET name.................................................................................................. 33
4.12 Resetting a device............................................................................................................. 35
4.12.1 Resetting communication parameters............................................................................... 35
4.12.2 Resetting devices to factory defaults................................................................................. 36
4.12.3 Performing a memory reset on CPUs................................................................................. 39
4.13 Formatting a memory card................................................................................................ 40
4.14 Updating device firmware................................................................................................. 42
4.14.1 Updating device firmware by two-step method................................................................. 48
4.15 Updating a device's program............................................................................................. 49
4.16 Reading and deleting Data Logs........................................................................................ 56
4.17 Backing up and restoring device data................................................................................ 58
4.17.1 Backing up a CPU or HMI................................................................................................... 58
4.17.2 Backing up HMI recipes..................................................................................................... 59
7 Supported devices.............................................................................................................................. 99
7.1 Device catalog.................................................................................................................. 99
7.2 Fail-Safe CPU support........................................................................................................ 100
Index................................................................................................................................................... 171
Advanced topics: Using NAT routers and limitations (Page 123), Troubleshooting (Page 137)
Device operations
When you scan the network (Page 15), you see the devices on the network.
Using the SIMATIC Automation Tool, you can perform many useful operations:
• Identify devices (Page 26)
• Insert devices (Page 20)
• Show device diagnostics (Page 27)
• Read Service Data from devices (Page 29)
• Set the CPU operating mode (Page 30)
• Set the CPU time (Page 31)
• Set the IP address (Page 31)
• Set the PROFINET name (Page 33)
• Reset communication parameters (Page 35)
• Reset devices to factory defaults (Page 36)
• Reset device memory (Page 39)
• Format memory card in a CPU (Page 40)
• Update device firmware (Page 42)
• Update the device program (Page 49)
• Read or delete Data Logs from a CPU's memory card (Page 56)
• Back up and restore a CPU or HMI (Page 58)
• Schedule device operations (Page 115)
• Browse the memory card of a CPU to perform the following: (Page 112)
– Add, replace, or delete recipes
– Add, replace, or delete user files
• Format a CPU's memory card (Page 40)
• Assign PROFIsafe addresses (Page 124)
• Configure data protection (Page 63) for CPUs that support it
• Comparison of hardware configuration to actual hardware (Page 15)
• Display of the F-Signature for F-CPUs (Page 49)
Some device operations require an Advanced license (Page 110).
Status bar
At the bottom of the SIMATIC Automation Tool is a status bar. This status bar shows you the
number of devices in the device table, the types of those devices, how many are not present
on the network, and how many you have selected in the device table. When operations are in
progress, the status bar shows the number of operations yet to complete for each type of
operation.
4. Click the Set Time button or select the Operations > Set Time menu command.
The Event Log shows you the result of the operation.
For help with understanding the Event Log messages, refer to Troubleshooting Event Log
messages (Page 137)
NOTE
Temporary (Emergency) IP addresses
For more information on temporary (emergency) IP addresses, refer to this FAQ
(https://support.industry.siemens.com/cs/ww/en/view/97649773).
NOTE
The SIMATIC Automation Tool is an offline tool
The SIMATIC Automation Tool does not update device data continuously. The SIMATIC
Automation Tool displays device information at the point of time that you scanned or
refreshed (Page 134) your communications network or at the point of time when you
inserted devices. The TIA Portal or Web server, for example, could change device data since
your last scan.
When you scan the network, the SIMATIC Automation Tool retains the device data from the
last scan until it updates the device data from the new scan. If a scan fails for a device, the
device displays the data from the previous scan and the Event Log displays an error.
NOTE
TIA Portal online connections to devices
If a device has an online connection in the TIA Portal, the SIMATIC Automation Tool might not
be able to read information from the device. The SIMATIC Automation Tool reports an error in
the Event Log. (Page 137)
To be able to read the device, go offline in the TIA Portal.
Click the check box next to a device to select it. The SIMATIC Automation Tool displays device
text in black for devices you have not selected and in bold when you have selected them.
You can enter text in cells with a light gray background. You cannot enter text in cells with a
dark gray background. A dark gray cell indicates that the SIMATIC Automation Tool does not
support the operation for that device type/firmware version.
You can find handy tips for working with the Device table in Device table power features
(Page 128).
Device identities
A device identity problem can occur, for example, if the TIA Portal makes modifications to a
device since the last network scan. A device identity problem can also occur when a device
fails.
The SIMATIC Automation Tool does not perform any device operations on a device with an
identity problem.
You must scan the network to resolve the device identity problem.
If you replace a failed device with a new device and assign the same IP address, you must
scan the network to resolve the device identity problem.
Fail-Safe devices
When you change the identity of a device or safety program status from the SIMATIC
Automation Tool, the tool makes the changes without a new network scan. For example, if
you download a new firmware version from the SIMATIC Automation Tool, the SIMATIC
Automation Tool updates the device variables to the new values. The SIMATIC Automation
Tool is an approved tool for operating safety devices and can handle safety state changes.
If you have a fail-safe CPU in your network, but you have not downloaded a safety program
(Page 169) to it, the device row cells appear in the color gray:
If you have downloaded a safety program to a fail-safe CPU, the information fields for the
device appear in yellow:
Yellow cell coloring in the following fields mean that the password is the safety password:
• CPU Password
• Password in Program File
Yellow cell coloring in the following fields mean that the selection is a safety program (Page
169):
• Program Update Folder
• Backup File
You can display the F-signature column in the Device table to see the collective F-signatures
for F-CPUs.
Password identification
If the device is protected at any protection level, then the SIMATIC Automation Tool enables
the password field. Until you enter a valid password with write access, the SIMATIC
Automation Tool displays the lock icon beside the device name.
PROFINET I/O
PROFINET I/O devices can appear twice in the Device table:
• As a root device if the SIMATIC Automation Tool finds the device on a network scan
• As distributed I/O if the CPU is configured to use this device as remote I/O
You can perform a firmware update from either location in the Device tree.
Example: IM 155‑6 PN HF
2. From the "Insert Device" dialog, select the type of address to enter:
– Device IP Address
– Device MAC address: Use a ":" as the separator, not a "-".
– NAT Router IP Address
3. Enter the address for the device, or the address for the NAT (Network Address Translation)
router and the device to insert behind the router. For a selection of "NAT Router IP
Address", the dialog changes to allow you to enter the following information:
– IP address of the NAT router
– IP address of the device
– CPU password
If the device behind the router is a protected S7-1X00 CPU, you must enter the device
password to enable insertion into the Device table.
The SIMATIC Automation Tool validates the device data. The device address or router and
device address pair must be unique on the network. The CPU password must be correct for a
protected device. If successful, the SIMATIC Automation Tool inserts the device into the
Device table. If unsuccessful, the Event Log displays an error message.
2. From the "Insert Multiple Devices" dialog, use these tabs to enter one or more devices:
– Device IP Address: Enter device IP addresses for one to many devices in the rows of this
tab. If the device is password-protected, you can also enter the device password. You
can also leave the password field empty and enter the password later in the Device
table.
– Device MAC Address: Enter device MAC addresses for one to many devices in the rows
of this tab
– NAT Router IP Address: Enter a NAT router IP address and device IP address for each
device behind a NAT router that you want to add. If the device is password-protected,
you must enter the device password to insert the device into the device table.
The NAT router address depends upon the type of router you are using. See the
information above under "NAT router IP addresses".
3. Optionally use the convenient editing features or Excel features to enter devices, routers,
and passwords into the dialog.
4. Click Insert to add the devices.
<Device IP Address>
<Device IP Address> <Device password>
<Device IP Address> <Device password>
Example: CSV file columns for Device MAC address tab
After the insert operation completes, the Event Log displays the total number of devices
inserted into the Device table.
Trusting a certificate
When you scan the network or insert devices into the Device table, the "Trust TLS Certificate"
field for each CPU indicates the certificate status. If the "Trust TLS Certificate" field is dark
gray, you have no action. The CPU does not have a certificate.
The certificate icon indicates the status of the certificate:
(blac The SIMATIC Automation Tool detected a self-signed certificate or a self-signed certificate
k) chain in the CPU.
(red) The SIMATIC Automation Tool detected a certificate with one or more errors. The CPU's Trust
TLS Certificate tooltip displays the most severe error. You can resolve the errors if possible or
accept the risk.
The three states of the "Trust TLS Certificate" are as follows:
• Selection needed
If the CPU has a certificate, the SIMATIC Automation Tool displays a certificate icon and
initially displays "Selection needed". The SIMATIC Automation Tool contains the certificate
information, which corresponds to the certificate information in the STEP 7 project that
you downloaded to the CPU. If you click the certificate icon, you can display the certificate
and related information. You can then decide whether to always trust the certificate or
never trust the certificate. Also, you can set the state back to "Selection needed" from
another state if you choose. You also see "Selection needed" under situations that require
you to choose a trust level for the certificate, for example when someone downloads a
new project to the CPU from the TIA Portal.
• Always
Choose "Always" to trust the certificate for the CPU and thus enable secure
communication and device operations with this CPU.
• Never
Choose "Never" if you do not trust the CPU certificate. Choosing "Never" blocks
communication to the CPU, except for the following:
– Discovering the CPU on a network scan
– Refreshing the CPU and validating the password, if applicable
– Displaying the CPU certificate
The SIMATIC Automation Tool provides tooltips for CPU certificate information.
NOTE
The SIMATIC Automation Tool displays the diagnostic events in the order they occurred,
regardless of the date and time of the event. Setting the CPU time to a time in the past has no
effect on the event order.
NOTE
You cannot read service data from redundant CPUs when the CPU operating mode is RUN-
Redundant.
WARNING
Service Data is clear text
A malicious user could read the service data files to obtain status and configuration details
about the control system. The service data files are in clear text, and are unencrypted. You
can use a CPU password to control access to this information.
Operating a process or machine with compromised data could affect the operation of an
online process or machine. Unexpected operation of a process or machine could result in
death or injury to personnel and/or property damage.
Use the TIA Portal device configuration to set up CPU protection with a strong password.
Strong passwords are at least ten characters in length, mix letters, numbers, and special
characters, are not words that can be found in a dictionary, and are not names or identifiers
that can be derived from personal information. Keep the password secret and change it
frequently.
You must confirm a prompt to change the operating mode. After you confirm the prompt,
the SIMATIC Automation Tool sets the selected CPUs to RUN or STOP mode.
The SIMATIC Automation Tool does not change the operating mode without confirmation.
The Mode and Operating state columns in the Device table indicate the current CPU state:
• Yellow: STOP mode
• Green: RUN mode
• Red: CPU fault
In addition, S7-1500 R/H CPUs have the following indicators:
• [P] indicates Primary
• [B] indicates Backup
• indicates RUN-Redundant mode for the two CPUs
The Event Log below the Device table shows the results of the operation.
WARNING
Changing the CPU time of day could disrupt process operation
Changing the CPU time of day could cause process disruption to STEP 7 programs that
execute program logic based on the time of day.
Unexpected operation of a process or machine could result in death or injury to personnel
and/or property damage.
Ensure that changing the time of day does not cause unwanted effects in the STEP 7
program.
You must have write access to a CPU to set the CPU time.
To set the CPU time to the programming device time, follow these steps:
1. Select one or more devices to include in the operation. You can use the Devices check box
at the top of the Device table to select or deselect all devices. Alternatively, you can use
the right-click shortcut menu or the "View > Select" menu command to access the "Select
Row(s)" and "Deselect Row(s)" commands.
2. For each selected CPU, enter a password, if used, in the "CPU Password" column of the
currently open tab.
3. Select the "Operations > Set Time" menu command or click the "Set the selected devices
time" toolbar button:
4. Click the "Continue" button on the "Set Time" dialog box.
The SIMATIC Automation Tool sets the system time on the selected devices to your current
programming device time. The Event Log shows the results of the operation.
If you enter invalid syntax, the SIMATIC Automation Tool displays the field in red. Correct
any errors if necessary.
4. Select Update from the Operations menu or click the Update button on the toolbar and
select "Set IP address" from the drop-down menu.
The Update operation sets the IP, subnet, and gateway addresses in the selected devices.
The Event Log below the Device table shows the results of this operation.
Duplicate IP addresses
When two or more devices have the same IP address, the IP Address cells appear in red as
shown in the following image:
You can select devices with duplicate IP addresses, update the IP addresses, and correct the
network problem. Only the following operations on devices with duplicate IP addresses are
possible:
• Delete
• Set IP address
• Set PROFINET name
• Identify devices
• Reset communication parameters
No other device operations are possible for devices that have duplicate IP addresses.
NOTE
Temporary (Emergency) IP addresses
For more information on temporary (emergency) IP addresses, refer to this FAQ
(https://support.industry.siemens.com/cs/ww/en/view/97649773).
The Update operation sets new PROFINET names in the selected devices. If you enter an
invalid PROFINET name according to the PROFINET name rules, the SIMATIC Automation Tool
corrects the name to a valid name. The column "PROFINET Converted Name" shows the
converted name.
The Event Log below the Device table shows the results of this operation.
Duplicate PROFINET names
When two or more devices have duplicate PROFINET names, the SIMATIC Automation Tool
indicates the duplicates with red cells. The SIMATIC Automation Tool supports full
functionality for these devices and displays all other information:
Parameter Value
NameOfStation "" (empty string)
IP suite parameters 0.0.0.0
DHCP parameters, if available Factory values
P Dev parameters: Factory values
• PD IR Data
• PD Port Data Adjust
• PD Interface
• MRP Data Adjust
• others
Parameters from MIB-II adjusted by SNMP, for Factory values
example:
• sysContact
• sysName
• sysLocation
To reset communication parameters for PROFINET devices, follow these steps:
1. Select the devices in the Device table that you want to reset.
2. Select the "Operations > Reset > Reset Communication Parameters" menu command.
The SIMATIC Automation Tool sends the "Reset Communication Parameters" DCP command to
the devices. The Event Log displays a message for devices that do not support the DCP reset
command. The Event Log also displays error messages for devices that return errors.
NOTE
You must configure CPUs as IO devices in the STEP 7 device configuration to enable the CPU
to reset communication parameters. The IO device settings are in the Operating mode group
of the PROFINET interface settings in the STEP 7 device configuration.
NOTE
Fail-Safe devices
If a fail-safe CPU is protected, you must enter the safety password in the "CPU Password"
column to reset a fail-safe device to factory defaults.
You must confirm an additional prompt and reselect your device if the program in the F-CPU
is a safety program (Page 169).
Reset to factory defaults requests for fail-safe devices are placed in the safety-relevant
operation queue and only single-thread sequential processing is allowed.
WARNING
Verify that the device is not actively running a process before you reset the device to
factory defaults
A Reset to factory defaults operation causes the CPU to go to STOP mode, which could affect
the operation of an online process or machine. Unexpected operation of a process or
machine could result in death or injury to personnel and/or property damage.
2. Select the "Operations > Reset > Reset to Factory Defaults" menu command to start the
operation. Alternatively, click the "Reset" toolbar button and select "Reset to Factory
Defaults" from the drop-down menu.
For fail-safe CPUs, the SIMATIC Automation Tool displays a dialog for additional
confirmation. Select the device, devices, or all devices that you want to reset to factory
defaults.
3. Optionally select "Delete IP address" if your device firmware supports this option.
4. Optionally select "Delete configuration data password" if your device firmware supports
this option.
5. Click the "Continue" button on the "Reset to Factory" dialog.
The SIMATIC Automation Tool resets the selected devices to factory defaults.
NOTE
Reset to Factory operation does not clear SIMATIC memory card
If you have a SIMATIC memory card in a CPU, a "Reset to Factory" operation does not clear the
contents. If you do not have a SIMATIC memory card in a CPU, "Reset to Factory" clears the
program in the internal load memory of the CPU.
The Event Log below the Device table shows the results of the operation.
The Event Log below the Device table shows the results of this operation.
NOTE
Use only Siemens software to format SIMATIC memory cards
If you use a SIMATIC memory card for non-SIMATIC purposes or you format it incorrectly, the
internal structure of the SIMATIC memory card is overwritten. The structure is not recoverable
and the SIMATIC memory card becomes unusable for SIMATIC devices.
Do not use SIMATIC memory cards for non-SIMATIC-related purposes and do not format
SIMATIC memory cards with third-party devices or Windows tools.
If you have a chain communication topology and the Communications settings (Page 85)
enable multi-threading, be aware of the risk of communication disruption with this operation.
WARNING
Verify that the device is not actively running a process before formatting a memory
card
Formatting a SIMATIC memory card causes a CPU to go to STOP mode, which could affect
the operation of an online process or machine. Unexpected operation of a process or
machine could result in death or injury to personnel and/or property damage.
4. Select the "Operations > Reset > Format Memory Card" command to start the operation.
Alternatively, click the "Reset" toolbar button and select "Format Memory Card" from the
button drop-down menu.
5. Optionally select "Delete IP address" if your device firmware supports deletion of the IP
address.
6. Optionally select "Delete configuration data password" if your device firmware supports
deletion of this password.
7. Click the "Continue" button on the "Format Memory Card" dialog box.
The SIMATIC Automation Tool performs the operation for each selected device. Check the
Event Log for the results of the operations. Check the CPU diagnostics following the format
operation. For device-specific questions, refer to the documentation for the device.
After you have formatted the memory card for an S7-1200 CPU, power cycle the CPU.
NOTE
Fail-Safe devices
If a fail-safe CPU is protected, you must enter the safety password in the "CPU Password"
column to format a SIMATIC memory card in a fail-safe device.
You must confirm an additional prompt and reselect your device if the program in the F-CPU
is a safety program (Page 169).
For fail-safe devices, the SIMATIC Automation Tool places requests to format a SIMATIC
memory card in the safety-relevant operation queue and only allows single-thread sequential
processing.
NOTE
Configuration of S7-1200 CM communication modules
For an S7-1200 CM module, you must configure the CM module in STEP 7 and download the
configuration to the module. You can then use the SIMATIC Automation Tool to update the
CM firmware.
NOTE
Dependencies for local modules of CPUs
You cannot update the firmware for local modules if the CPU does not support firmware
update. For example, S7-1200 CPUs with a firmware version earlier than V4.0 do not support
firmware update over Ethernet. You cannot use the SIMATIC Automation Tool to update the
firmware for local modules connected to these CPUs.
Preparing CPU and module firmware update files for use with the SIMATIC Automation Tool
You can obtain CPU and module firmware update files from the Siemens product support
(https://support.industry.siemens.com/cs/us/en/ps) web site.
You can also select a device row and then select "Check for Firmware Updates" from either
the Tools menu or the Tools toolbar icon. The SIMATIC Automation Tool launches the device's
customer support web page. The Siemens support web page selection corresponds to the
article number displayed in a Device table row. For example, a "Check for updates" command
on article number 6ES7 215‑1HG31‑0XB0 links to the corresponding CPU 1215C web support
page (https://support.industry.siemens.com/cs/products/6es7215-1hg31-0xb0/cpu-1215c-
dcdcrly-14di10do2ai2ao?pid=79072&dtp=Download&mlfb=6ES7215-1HG31-0XB0&lc=en-
WW).
For a CPU example, the firmware update file named "6ES7 211-1AE40-0XB0_V04.00.02.exe"
is only for the CPU 1211C DC/DC/DC model. If you use the .upd file within this package for any
other S7‑1200 CPU model, the update process will fail.
When you execute the update file and extract the files, you see the following set of files and
folders.
• File: S7-JOB.S7S
• Folder: FWUPDATE.S7S contains the .upd file.
– file: 6ES7 211-1AE40-0XB0 V04.00.02.upd (.upd file used by the SIMATIC Automation
Tool)
For an I/O module example, the firmware update file named "232‑4HD32‑0XB0_V203.exe" is
only for the SM 1232 ANALOG OUTPUT 4AO module. The self-extracting .exe file contains the
file "6ES7 232‑4HD32‑0XB0 V02.00.03_00.00.00.00.upd" that is used by the SIMATIC
Automation Tool.
NOTE
New format firmware update files
• The self-extracting .exe update package name must refer to the article number of the
device that you want to update.
• The extracted .upd file name must match the article number of the device and the
firmware version that you want to load.
NOTE
Old format firmware update files
• The self-extracting .exe update package name must refer to the article number of the
device that you want to update.
• Contains three or more files depending on the firmware size.
• Create a folder with any name in the Firmware Update folder (Page 88). You can name
the folder with the article number and version number so it will be easier to identify, but
you can use any name. The SIMATIC Automation Tool parses all firmware files at startup to
confirm exact firmware version numbers.
WARNING
Verify that the CPU is not actively running a process before installing firmware updates
Installing a firmware update for a CPU or module causes the CPU to go to STOP mode, which
could affect the operation of an online process or machine. Unexpected operation of a
process or machine could result in death or injury to personnel and/or property damage.
Preparing HMI firmware update files for use with the SIMATIC Automation Tool
A firmware update file for an HMI file has an .fwf file extension. This file is part of the HMI
runtime and operating system that you can copy from the TIA Portal project. See the topic
Updating a device's program (Page 49) for instructions on transferring the SIMATIC.HMI file
structure from the TIA Portal to a storage medium such as a SIMATIC memory card. After you
copy the SIMATIC.HMI file structure to your storage medium, follow these steps to update the
firmware for an HMI device:
1. From the SIMATIC.HMI folder on your SIMATIC memory card or other device, start at the
"Firmware" subfolder and navigate until you see the file with an .fwf file extension.
2. Copy the .fwf file to your Firmware Update (Page 88) folder.
You can store multiple .fwf files for multiple HMI devices and multiple firmware versions in
the Firmware Update folder.
NOTE
Transfer Settings for an HMI device (SIMATIC Panel)
To communicate with an HMI, you must set the Transfer Settings on the HMI device to PN/IE
or Ethernet.
5. For each selected SCALANCE device, select the SNMP profile (Page 93) for your device. An
icon next to the SNMP profile indicates whether the SNMP profile name corresponds to a
profile name in the profile file in the SNMP Profiles folder (Page 93):
SNMP profile does correspond to an SNMP profile in the profile file in the SNMP
Profiles folder.
SNMP profile does not correspond to an SNMP profile in the profile file in the SNMP
Profiles folder.
NOTE
You need to provide a TFTP (Trivial File Transfer Protocol) server to install firmware in
SCALANCE devices.
6. Select the "Operations > Update > Firmware Update" menu command to start the
operation. Alternatively, click the Update toolbar button and the "Firmware Update"
command from the button drop-down menu.
The Event Log below the Device table shows the results of the operation. After a successful
firmware update operation, the SIMATIC Automation Tool clears the "New Firmware Version"
field.
NOTE
Fail-Safe devices
You must confirm an additional prompt and reselect your device if the program in the F-CPU
is a safety program.
For fail-safe devices, the SIMATIC Automation Tool places firmware update requests in the
safety-relevant operation queue and only allows single-thread sequential processing.
Timeout error message due to slow communication with .upd file storage device
If you see the following error message box, then more than ten seconds have elapsed. The
SIMATIC Automation Tool has not completed processing all of the .upd files. The time
required to open and scan all the .upd files depends on data access time and the number of
.upd files in the folder.
This timeout error can occur when communication with a remote storage device is too slow.
To prevent this problem, copy the firmware update files to a local storage device that
provides faster access. Assign this path as the firmware update folder (Page 88) and try the
operation again.
3. Select the "Operations > Update > Firmware Update" menu command to start the
operation. Alternatively, click the Update toolbar button followed by the Firmware Update
menu command from the drop-down menu.
NOTE
You cannot update the firmware of some S7-1200 modules with the SIMATIC
Automation Tool
Some CPUs do not support firmware update. If a CPU does not support firmware update, you
can only update the device with a SIMATIC memory card. You also cannot update the
firmware of modules connected to this CPU with the SIMATIC Automation Tool.
Methods for updating firmware other than the SIMATIC Automation Tool
Alternative firmware update methods include the following:
• SIMATIC memory card in applicable devices
• TIA Portal online and diagnostic functions
• Module Information page of a CPU's Web server
NOTE
HMI operating system and runtime software updates
You can use the SIMATIC Automation Tool program update operation (Page 49) to update the
HMI operating system and runtime software. The program update operation updates all data
components as necessary for a consistent download.
You can update the HMI operating system (firmware) without updating the runtime
software. In versions prior to V3.1 SP2, you could not update just the operating system
firmware. You had to perform a program update.
Prerequisites
Before you can transfer a program to a CPU or HMI using the SIMATIC Automation Tool, you
must have access to the program on one of the following forms of media:
• SIMATIC memory card
• USB flash drive
• Hard drive of your programming device
Example: Preparing a CPU program for use with the SIMATIC Automation Tool
This example uses a SIMATIC memory card for the transfer. You can also transfer to a USB
flash drive or Windows folder on your programming device.
To transfer a STEP 7 CPU project to a SIMATIC memory card, follow these steps:
1. Insert a SIMATIC memory card into the card reader for your programming device
2. From STEP 7, select the CPU in the Project tree
3. Select the "Project > Card Reader/USB memory > Write to memory card" menu command:
STEP 7 saves a SIMATIC.S7S folder on your SIMATIC memory card that contains your CPU
project. You can also copy the STEP 7 project to the memory card by dragging the project to
the memory card in the project tree.
Refer to the STEP 7 Information System (online help) for additional information.
After STEP 7 transfers program data to a storage device, you can use the Windows File
Explorer to transfer the program to the folder that is used by the SIMATIC Automation Tool.
Copy the "SIMATIC.S7S" folder for each CPU program
To make a CPU program accessible to the SIMATIC Automation Tool, follow these steps:
1. Create subfolders under the Program Update folder (Page 88). Create one folder for each
program and create a folder name that identifies the program. The folder names that you
create will appear in the SIMATIC Automation Tool program drop-down list.
2. Use the Windows File Explorer to copy the "SIMATIC.S7S" folder (including all subfolders
and files) to each subfolder for each program. You can put a TIA Portal program (a
"SIMATIC.S7S" folder) in a zip file archive and extract it to your subfolder location. Note
that you update recipes in a separate recipe operation (Page 112).
See the "Example CPU program update" section later in this topic.
NOTE
STEP 7 program data
The program data is protected. You cannot discover details like the project name or target
CPU of a STEP 7 program from the data that is stored in a SIMATIC.S7S folder. You cannot
identify one program's SIMATIC.S7S folder from another program's SIMATIC.S7S folder.
You must create and name subfolders under the SIMATIC Automation Tool Program Update
folder (Page 88) that identify a program's function or target CPU. Copy a program's
SIMATIC.S7S folder into the subfolder that you named. The subfolder names that you create
appear in the SIMATIC Automation Tool "Program" column drop-down list and provide the
path to the correct SIMATIC.S7S folder.
Example: Preparing an HMI operating system and runtime software for use with the SIMATIC
Automation Tool
This example uses a SIMATIC memory card for the transfer. You can also transfer to a USB
flash drive or Windows folder on your programming device.
HMI devices v14 and higher support saving the operating system and runtime from STEP 7.
To copy the operating system and runtime files for an HMI to a SIMATIC memory card, follow
these steps:
1. Insert a SIMATIC memory card into the card reader for your programming device.
2. Expand "Card Reader/USB memory" in the Project tree to show the drive corresponding to
your card reader.
3. Select your HMI in the Project tree and drag it to the drive letter of your card reader.
STEP 7 saves a SIMATIC.HMI folder on your SIMATIC memory card that contains your HMI
runtime and HMI operating system. HMI updates include the operating system and runtime
data. You do not have the option to select a partial update.
After the TIA Portal transfers the SIMATIC.HMI folder to a storage device, use the Windows
File Explorer to make the SIMATIC.HMI folder accessible to the SIMATIC Automation Tool:
1. Create a subfolder for the HMI program in the Program Update (Page 88) folder.
2. Copy the SIMATIC.HMI folder to the subfolder.
If you want to use the firmware (operating system) portion of the SIMATIC.HMI folder to
update the firmware of an HMI device (Page 42), follow these steps:
1. Navigate through the "Firmware" folder of the SIMATIC.HMI folder until you see an .fwf
file.
2. Copy the .fwf file to the Firmware Update (Page 88) folder.
NOTE
Fail-Safe devices
If the fail-safe CPU is protected, you must enter the safety password in the "CPU Password"
column to update the program in a fail-safe device.
You must confirm an additional prompt for program updates to F-CPUs and reselect your
device under the following conditions:
• You are updating a safety program (Page 169) with another safety program
• You are updating a safety program with a standard program
• You are loading a safety program for the first time
• You are updating a standard program that requires the safety password
The SIMATIC Automation Tool places program update requests for fail-safe devices in the F-
CPU safety-relevant operation queue. The SIMATIC Automation Tool uses only single-thread
sequential processing for the safety-relevant operation queue.
The destination device for a safety program must be a fail-safe CPU.
You can display the F-signature column in the Device table to see the collective F-signatures
for F-CPUs.
WARNING
Verify that the device is not actively running a process before updating the program
Installing a new program causes CPUs to go to STOP mode, which could affect the operation
of an online process or machine. Unexpected operation of a process or machine could result
in death or injury to personnel and/or property damage.
NOTE
Transfer Settings for an HMI device (SIMATIC Panel)
To communicate with an HMI, you must set the Transfer Settings on the HMI device to PN/IE
or Ethernet. You must set the Communications settings (Page 85) for the HMI Transfer
Channel to the same setting.
After you have stored programs in the Program Update folder, you can use the SIMATIC
Automation Tool to load new programs in one or more devices. To perform a program
update, follow these steps:
1. Click the "Program Update" tab.
2. Select one or more devices to include in the operation. You can use the Devices check box
at the top of the Device table to select or deselect all devices. Alternatively, you can use
the right-click shortcut menu or the "View > Select" menu command to access the "Select
Row(s)" and "Deselect Row(s)" commands.
3. For each selected device, use the "Program Update Folder" column drop-down list to select
a folder name. The drop-down list shows the folders that you created in the program
update path.
You can also use the browse button and navigate to the folder where you have stored
a program on your programming device. When you select a program, the SIMATIC
Automation Tool adds it to the drop-down list. If the selected file has the same name as
one of the files already listed, the SIMATIC Automation Tool adds a number to the new file
name to make the names unique. To help you identify files, when you hover over the
program name in the Program Update field, a tooltip displays the device interface and IP
information, for example:
If the program file does not contain an IP address, the tooltip displays "Set directly at
device" for all IP address fields.
If you selected a safety program, the SIMATIC Automation Tool displays the Program
Update Folder cell in yellow. If it is not yellow, it is a standard program.
4. Enter passwords, if used, in the "CPU Password" and "Password in Program File" columns.
Program update is a safety-relevant operation. If the device is a fail‑safe device, you must
enter the safety password.
5. Select the "Operations > Update > Program Update" menu command to start the
operation. Alternatively, select the Update toolbar button and select "Program Update"
from the drop-down menu.
The Event Log below the Device table shows the results of this operation.
Program validation
The SIMATIC Automation Tool verifies the program data before updating the program in a
CPU.
If there is an error in the program data, the SIMATIC Automation Tool displays a red "X" icon
in the "Program Update Folder" cell. Additional error information is available in a tooltip when
you hover over the cell.
in Program File" cell to perform a program update. The program password becomes the CPU
password after the program update operation completes.
After a successful program update operation, the SIMATIC Automation Tool automatically
copies the Password in Program File to the CPU password field and attempts a connection
using the new password. The SIMATIC Automation Tool then clears the Password in Program
File field and the Program Update Folder field.
If the password you enter in the "Password in Program File" column is not the password
configured for the project in STEP 7, the Event Log shows a warning after the operation
completes. In this case, the CPU password shows a red ‘X’ icon that indicates an invalid
password.
F-signature validation
A STEP 7 project that contains a safety program has an F-signature that is used to verify the
data in a copied program. The F-signature provides an additional level of security for safety
programs. After a program update operation, the SIMATIC Automation Tool performs a CRC
comparison of the F-signature in the project to the F-Signature now loaded in the CPU device.
An Event Log message (Page 137) shows the result of the CRC comparison. You can view the
F-signature in the F-CPU in the Device table.
If the CRC comparison fails, reset the device to factory defaults (Page 36) and repeat the
program update.
WARNING
Be sure you load the correct safety program.
Running the wrong program on an F-CPU can affect the operation of a process or machine.
Unexpected operation of a process or machine could result in death or injury to personnel
and/or property damage.
Do not attempt to go to RUN mode if you are not sure that you have loaded the correct
safety program.
updated the device IP address (Page 31) with the SIMATIC Automation Tool. In that case, the
user-updated device address is currently in the CPU.
The IP address of the device after a program update and after a subsequent CPU power cycle
depends on the setting in the new program and the current IP address. The following table
describes various possibilities for the IP address of the device.
Device configuration in new program IP address after program update IP address after next CPU power cycle
for update after program update
Set IP address in project IP address is the IP address from the IP address is the IP address from the
newly-updated program. newly-updated program.
IP address is set directly at the device IP address is the IP address of the device IP address is the IP address of the device
before the program update. before the program update.
The following image shows the SIMATIC Automation Tool Program Update tab with the
example folder names in the "New Program Update" column drop‑down list. You must use
the drop-down list in the "New Program Update" column to assign which program to use. If
you select more than one CPU row, then you must repeat the process and assign the correct
program for each CPU that you selected.
Select the "Operations > Update > Program Update" menu command to start the program
update. Alternatively, click the toolbar Update button and select "Program Update" from the
drop-down menu.
The process is similar for HMI data. The folder name within a project folder is "SIMATIC.HMI"
instead of "SIMATIC.S7S". The procedure is the same.
WARNING
Protect access to Data Log files
Operating a process or machine with compromised data could affect the operation of an
online process or machine. Unexpected operation of a process or machine could result in
death or injury to personnel and/or property damage.
Take steps to protect Data Log .csv files from being compromised, for example, by limiting
network access and by using firewalls.
NOTE
Fail-Safe devices
If a fail-safe CPU is protected, you must enter the safety password in the "CPU Password"
column to restore a backup file to a fail-safe device.
You must confirm an additional prompt and reselect your device if the program in an F-CPU is
a safety program (Page 169).
The SIMATIC Automation Tool places "Restore from backup" requests for fail-safe devices in
the F-CPU safety-relevant operation queue. The SIMATIC Automation Tool uses only single-
thread sequential processing for the safety-relevant operation queue.
The destination device for a safety program must be a fail-safe CPU.
WARNING
Verify that the device is not actively running a process before restoring a device from a
backup file
Restoring a CPU causes the CPU to go to STOP mode, which could affect the operation of an
online process or machine. Restoring an HMI disrupts operator actions from operator
screens, which could also cause process disruption.
Unexpected operation of a process or machine could result in death or injury to personnel
and/or property damage.
Verify that your process can handle a disruption before restoring a device from a backup file.
NOTE
Transfer Settings for an HMI device (SIMATIC HMI Panel)
To communicate with an HMI, you must set the Transfer Settings on the HMI device to PN/IE
or Ethernet. You must set the Communications settings (Page 85) for the HMI Transfer
Channel to the same setting.
3. For each device, select a backup file name from the "Backup File" drop-down list. The drop-
down list shows the names of the .s7pbkp files that exist in the backup and restore folder
(Page 89).
You can also use the browse button and navigate to the folder on your programming
device that contains backup files. Select a file to add it to the drop-down list. If the file that
you selected has the same name as an existing file, the SIMATIC Automation Tool adds a
number to the new file name to make the names unique.
For valid files, a tooltip displays the path and filename. You also see a green check mark by
the file name.
For invalid files, the tooltip displays the file error, which the Event Log also displays. You
see a red X by the file name.
4. Enter passwords, if used, in the "CPU Password" and "Password in Backup File" columns.
"Restore from backup" is a safety-relevant operation. You must enter the safety password
for a protected fail-safe device.
5. Select the "Operations > Backup/Restore > Restore Device" menu command to start the
operation. Alternatively, click the Backup/Restore toolbar button and select "Restore
Device" from the button drop-down menu.
If the CPU password that you entered in the "Password in Backup File" column is incorrect and
is not actually a CPU password configured in the restored CPU data, then the Event Log shows
a warning after the operation completes. In this case the CPU password shows a red ‘X’ icon
to indicate an invalid CPU password.
F-signature validation
A STEP 7 project that contains a safety program has an F-signature. The SIMATIC Automation
Tool uses the F-signature to verify the data in a program file, which provides an additional
level of security for safety programs. You can display the F-signature column in the Device
table to see the collective F-signatures for F-CPUs. After a Restore from backup operation, the
SIMATIC Automation Tool compares the F-Signature in the project file to the F-Signature that
is now in the CPU device program.
The Event Log reports a successful comparison as: "Result of CRC comparison: Online and
offline F-signatures match."
The SIMATIC Automation Tool reports an unsuccessful comparison in the Event Log as: "Result
of CRC comparison: Online and offline F-signatures do not match." In the event of an
unsuccessful comparison, reset the device to factory defaults (Page 36) and repeat the
program update. Do not attempt to go to RUN mode if you are not sure that you have loaded
the correct safety program.
In such a situation, you must update your NAT router configuration. You must then insert the
device (Page 20) into the SIMATIC Automation Tool using the new IP address. After you insert
the device at the new IP address, delete the entry in the Device table at the old IP address.
After executing the "Restore Device" operation, the Event Log shows the results of the
operation.
NOTE
Setting or deleting a configuration data protection password requires that the CPU be in STOP
mode. You must confirm placing the CPU in STOP mode for any configuration data protection
action.
Special considerations
Take note of the effect of the configuration data password on the following operations.
Program update The SIMATIC Automation Tool does not allow a program update if both of the following conditions
are true:
• The device configuration in the program update file is a firmware version that supports config
uration data protection
• The configuration data password in the CPU does not match the configuration data password
in the program
Restore from Backup The SIMATIC Automation Tool cannot determine the configuration data protection password inside
the backup file. The SIMATIC Automation Tool proceeds with the restore operation. The CPU is
responsible for allowing or prohibiting the restore from backup. Refer to CPU manuals and the
TIA Portal Information System for further information.
NOTE
Do NOT delete the hidden file "crdinfo.bin" from the memory card. The SIMATIC Automation
Tool and the CPU require the "crdinfo.bin" file
If you use a SIMATIC memory card for non-SIMATIC purposes or you format it incorrectly, the
internal structure of the SIMATIC memory card is overwritten. The structure is not recoverable
and the SIMATIC memory card becomes unusable for SIMATIC devices.
Do not use SIMATIC memory cards for non-SIMATIC-related purposes and do not format
SIMATIC memory cards with third-party devices or Windows tools.
The SIMATIC Automation Tool attempts to create a configuration data protection memory
card.
The Event Log reports the results of the operation.
NOTE
Transferring files from one programming device to another
Create an archive file (Page 70) to restore SIMATIC Automation Tool project and related files
from one programming device to another.
Password validation
When you create a project password, the SIMATIC Automation Tool indicates that it is a weak
password if it does not meet the criteria for a strong password.
Creating an archive
To create an archive file, follow these steps:
1. Select the File > Create Archive menu command. The SIMATIC Automation Tool opens the
Windows File explorer to the default location for Projects (Page 87).
2. Provide a file name and save the file in the default folder or to any other folder on you
programming device.
3. Provide a password for the archive file.
The SIMATIC Automation Tool saves the compressed archive file with extension .satz.
Opening an archive
To open an archive file, follow these steps:
1. Select the File > Open Archive menu command.
2. Select an archive file from your programming device.
3. If you agree, click "Yes" to acknowledge the prompt that informs you that the files in the
archive will overwrite files of the same name on your programming device. If not, click
"No".
4. Enter the password for the archive file.
The SIMATIC Automation Tool fills the Device table with the devices in the archived .sat
project file and restores the archived files selected for these categories:
• Firmware update (Page 42)
• SNMP Profiles (Page 42)
• Program update (Page 49)
• Backup File (Page 60)
NOTE
CPU protection and passwords
For protected CPUs in the Device table, the SIMATIC Automation Tool only exports the local
module and distributed I/O information if the Device table includes a CPU password that is at
the read access level or higher.
• Device row: Each device in the Device table appears in a row of the .csv file with its device
data in each column. All SIMATIC Automation Tool Device table columns are in the
exported .csv file. If you hide columns in the SIMATIC Automation Tool, the data
corresponding to the hidden columns still appears in the .csv file. Hiding columns in the
SIMATIC Automation Tool has no effect on the .csv file contents.
• Local modules folder row: If a device has local modules, the .csv includes a Local Module
row with the following column headers:
– Device
– Slot
– Device Type
– Article Number
– Serial Number
– Firmware Version
– Hardware
• Local modules row: Each local module appears in the .csv file with its module data in
each column. Module data is available in the file when the SIMATIC Automation Tool can
read the module data and the data is visible in the Device table.
• Distributed I/O header: A row with the label "Distributed I/O" indicates that the rows that
follow represent distributed I/O modules.
• Distributed I/O system folder header: A row for a distributed I/O system contains the
name of the distributed I/O system and the following column header names:
– Device
– Slot
– Device Type
– Article Number
– Serial Number
– Firmware Version
– Hardware
• Distributed I/O device row header: Each device in the distributed I/O system appears on
a row with the device data in the corresponding columns. Distributed I/O device data is
available in the file when the SIMATIC Automation Tool can read the device data and the
data is visible in the Device table.
• Distributed I/O module row: Each module for each distributed I/O device appears on a
row with the device data in the corresponding columns. Module data is available in the file
when the SIMATIC Automation Tool can read the module data and the data is visible in the
Device table.
NOTE
Copying between the Device table and Microsoft Excel
You can copy and paste selected cells from the Device table to a Microsoft Excel file:
1. Expand all rows in the Device table with the "Edit > Expand > All Devices" menu command.
2. Select Ctrl+A to highlight all rows and columns or drag to select a range of cells.
3. Select Ctrl+C to copy the Device table data to the Windows clipboard.
4. Select Ctrl+V to paste the clipboard data into a Microsoft Excel worksheet.
The Export function allows you to copy all or selected devices in a readable format. Copying
from the Device table is not typically necessary but is possible. You can, for example, use
copy and paste to modify user-entered device information.
You can edit data in the Microsoft Excel file. You can also zoom to make the content more
readable. If you add or delete rows, be sure to maintain the format and hierarchy.
If you copy cells to editable fields in the SIMATIC Automation Tool Device table, follow these
steps to update the device table:
1. Copy and paste the cell range that you need from Microsoft Excel to editable fields in the
Device table, for example, "New IP address" or "New PROFINET name".
2. In the SIMATIC Automation Tool, re-enter passwords for protected CPUs.
3. Perform the command for the devices that correspond to your pasted data, for example,
"Set IP Address" or "Set PROFINET Name" from either the "Operations > Update" menu or
the toolbar buttons.
4. Refresh the Device table using the "Operations > Scan Network" menu command or select
devices and run the "View > Refresh > All Selected Devices" menu command. You can also
run either command from the corresponding toolbar button.
Similarly, you could paste edited IP addresses or MAC addresses into the "Insert Device" dialog
or the "Insert Multiple Devices" dialog. For the insert operation to succeed, the IP addresses or
MAC addresses must be unique from exisiting addresses in the device table.
NOTE
Displaying .csv files in Microsoft Notepad or Microsoft Excel
Due to differing character sets, Microsoft Notepad and Microsoft Excel might not correctly
display characters in your .csv file. Open the file using the Unicode (UTF-8) character set to
see characters in your language that might not be visible otherwise. Regardless of the
appearance of header texts, you can export project files and copy content from the exported
files to the SIMATIC Automation Tool.
The XML tags structure the information in the same way as the .csv file organization. Device
information, local modules, and distributed I/O contain the same information in the XML file
as in the .csv file.
NOTE
Exporting device diagnostics from a large Device table can take a long time. The SIMATIC
Automation Tool displays a progress bar during the export. You can cancel an export
operation that is in progress.
Open Display an "Open" dialog where you can browse to a folder, select an
.sat project file, and provide a password to open a protected project
file. The "Open" dialog displays the projects folder (Page 87), but you
can browse to any location for a project.
Save Save (Page 68) the Device table data in an .sat file. If there is no file
name, then this operation uses the "Save As" command. The projects
folder (Page 87) is the default folder for saving projects.
Save As Save the Device table data in an .sat file. You can browse to a folder,
provide an .sat project filename, and assign a password to protect
the project file.
Project Password Set or change the password for the project (Page 69)
Create Archive Create an archive file (Page 70) (requires an advanced license)
Open Archive Open an archive file (Page 70) (requires an advanced license)
Export (Page 72)
• Device Information Save the Device table for the selected devices, including local mod
– All Selected ules and distributed I/O, to a .csv file and an .xml file.
Devices
• Device Information Save the Device table for all devices, including local modules and dis
– All Devices tributed I/O, to a .csv file.
Quick Ping Test whether devices are connected to the network (Page 20)
Update
• Set IP Address Update the CPU with the IP Address information for the selected
device(s). (Page 31)
• Set PROFINET Update the CPU with the PROFINET Name for the selected device(s).
Name (Page 33)
• Program Update Update the CPU program or HMI operating system and runtime soft
ware for the selected device(s). (Page 49)
• Firmware Update the firmware for the selected device(s). (Page 42)
Update
• Two Step Update the firmware for the selected device(s) in two steps. (Page
Firmware 48)
Update
• Firmware Down Download firmware update file to selected
load device(s).
• Activate Firmware Activate the downloaded firmware on the
selected device(s).
Identify Flash the LEDs on devices or flash HMI screens. (Page 26)
Use this feature to identify the physical location of a device.
Reset
• Reset Reset DCP communication parameters (Page 35) for devices that
Communication support the DCP reset command.
Parameters
• Memory Reset Perform a memory reset on selected devices. (Page 39)
• Reset to Factory Reset selected devices to factory defaults. (Page 36)
Defaults
• Format Memory Format memory card in selected devices. (Page 40)
Card
Diagnostics
• Full Backup Back up all data for all selected devices. (Page 58) The SIMATIC Auto
mation Tool saves a backup file for each selected device.
• HMI
• Recipes Back up HMI recipes. (Page 59)
• User Back up HMI user administration data. (Page
Administration 59)
Restore Device Restore data from backup file(s) to the corresponding device(s).
(Page 58)
Data Logs Note: Data Log operations apply only to CPUs with SIMATIC memory
cards.
• Read Data Logs Read selected Data Log files to your programming device. (Page 56)
• Delete Data Logs Delete selected Data Log files. (Page 56)
If you use the browse function from the Device table to locate a file such as a firmware
update file or program update file, you do not see your user ID as a folder under "Users". You
see the folder "Documents". Expand this folder to find the "SIMATIC Automation Tool" folder.
Navigation from Windows also shows a different navigation path than the pathname in the
Settings dialog. From File Explorer, the Documents folder under Quick Access is equivalent to
the "Documents" folder under your "MyAccount" folder.
NOTE
Scan the network to update folder names
If you change the user interface language, folder names in the Device table remain in the
previous user interface language. Scan the network to update folder names to the new user
interface language.
When you have enabled a scan filter, the SIMATIC Automation Tool displays the filtered scan
icon .
6,0$7,&
$XWRPDWLRQ
7RRO
NOTE
You can add up to 25 SNMP profiles.
If you enable the operations, then when you launch the Scheduler application all operations
default to the enabled state.
If schedule operations for a CPU require the CPU to be in STOP mode, the second setting
allows the Scheduler application to change the operating mode to STOP.
These scheduler settings are included in the scheduler configuration file.
Tools menu
The Tools menu is also accessible from the toolbar icon.
Open: Display an "Open" dialog that can browse to a folder, select a project file, and provide a password to open the
encrypted project file.
Save the opened project data to a file. If no filename and password are assigned, then the "Save As" dialog is dis
played.
Cut the selected data and copy the data to the clipboard. Clipboard data are compatible with Microsoft Excel so data
can be shared between the two applications.
Copy the selected data to the clipboard.
Scan the device network using the defined filter (Page 85)
Ping devices to check whether they are on the network (Page 20)
Insert one or more devices into the Device table (Page 20)
Update device(s) with data from the SIMATIC Automation Tool from one of the following choices:
• Set IP Address (Page 31)
• Set PROFINET Name (Page 33)
• Program Update (Page 49)
• Firmware Update (Page 42)
You must select the corresponding Device table tabs to enter the data to update.
Identify devices (Page 26) by flashing device LEDs or HMI screens on selected devices. Use this feature to identify the
physical location of a device.
Reset functions for selected devices:
• Memory Reset (Page 39)
• Reset to Factory Defaults (Page 36)
• Format Memory Card (Page 40)
Access diagnostic information:
• Show Diagnostics (Page 27)
• Read Service Data from selected devices (Page 29)
Set time: Set the system time in selected CPUs to current programming device time (Page 31)
Backup and restore functions: (Page 58)
• Create Backup file(s) for selected CPUs and HMI devices.
• Restore selected device(s) from backup file(s)
File operations:
• Read or delete Data Logs (Page 56)
Delete operations require that the CPU be in STOP mode.
Check for firmware updates or preload firmware update files (Page 42)
icon Description
Download the scheduler configuration file (Page 115)
Open the Settings dialog (Page 84)
Network interface drop-down list: (Page 167) Select the
PROFINET network interface that is connected to the device net
work.
Unsupported devices
The SIMATIC Automation Tool handles unsupported devices as follows:
• Displays the device in a Device table row with partial information
• Displays the unsupported device question mark icon in the row
• Supports only the following DCP operations when the device is connected to the same
subnet as the programming device that is running the SIMATIC Automation Tool:
– Identify
– Update IP address
– Update PROFINET name
– Reset communication parameters
Unsupported firmware
You might have a device on your network that has a newer firmware version than the latest
firmware version that the SIMATIC Automation Tool supports. You can only perform device
operations for the latest firmware version listed in the device catalog for the device.
NOTE
For owners of a previous license
If you have a license for the SIMATIC Automation Tool prior to V5.0, you must upgrade to a
V5.0 or higher license. Contact your salesperson for the correct upgrade license for your
product.
The memory cards can have the following folders for specific uses:
• DataLogs
• Recipes
• UserFiles
• ODK1500S
You can create these folders if they do not exist, but you cannot delete, cut, or rename these
folders. You can copy them to another location, but you cannot move them to another
location. The SIMATIC Automation Tool prevents you from performing an invalid action. You
cannot write to a SIMATIC memory Card that is physically write-protected.
To create folders at the root level, right-click in the gray area of the root level in the file list
pane and select New > Folder.
SIMATIC memory cards might also contain other custom files and folders. Using the file list
pane, you can delete and rename these other folders and their contents.
For Data Logs, you can copy a Data Log file to your programming device, but you cannot
delete, rename, or change any files in a DataLogs folder. You perform Data Log file operations
(Page 56) from the Device table.
You can copy and paste multiple files in a single operation.
The panes of the Card Browser support the following display features:
• Resizing of the panes and columns in either pane
• Navigation pane sort on Device or IP Address
• File list sort by any of the columns
• Ability to show or hide some columns
• Typical Windows mouse and keyboard operations
Transferring files or folders from one SIMATIC memory card to one or more CPUs
You can copy files from the file list pane for one memory card and paste the selection to the
file list pane of another memory card.
The SIMATIC Automation Tool provides "Copy Special" and "Paste Special" commands in the
navigation pane to simplify copying all of the recipe files or user files from one memory card
to another.
To transfer recipe files, user files, or both from one memory card to another, follow these
steps:
1. Right-click the memory card in the navigation pane from which you want to copy recipe
files or user files.
2. Select "Copy Special" from the shortcut menu.
3. From the dialog, select the file types (recipe files, user files, or both) that you want to copy
to the clipboard.
4. Right-click the memory card in the navigation pane where you want to paste the recipe
files or user files.
5. Select "Paste Special" from the shortcut menu.
6. Make your selections on the "Paste Special" dialog and click OK. The dialog displays what
you selected from the "Copy special" dialog and gives you options for the paste operation.
The SIMATIC Automation Tool ignores any folders in the selection and only pastes files to the
destination CPU or CPUs.
Restrictions
You cannot delete the following folders from the root level of a SIMATIC memory card:
• DataLogs
• Recipes
• UserFiles
• ODK1500S
Operation results
For each operation, the Event Log below the Device table shows the results of the operation.
Select the check boxes for the operations that you want to run for the devices in the Device
table. Depending on the device type, you can only select operations that are applicable for
each device. Note that you can select multiple cells and use the space bar to toggle the
selection state for the cell range.
For each type of operation that you select, click the calendar symbol to configure the
following schedule settings:
• Date
• Time
• Frequency
The drop-down list for Frequency shows you the valid frequency choices:
• Run Once
• Every Day
• Every Week
• Every 2 Weeks
• Every Month
• Every Year
The combination of date, time, and frequency must be valid. For example, you cannot
schedule a yearly operation for February 29th or a monthly operation for the 30th or 31st of
a month.
For a firmware update operation, you must select a valid firmware update file. If the device is
a SCALANCE device, you must also select a valid SNMP profile in addition to a valid firmware
update file.
When you have finished configuring your scheduled operations, click the button. The
SIMATIC Automation Tool validates that you have selected at least one operation for one
device at a valid frequency setting. The SIMATIC Automation Tool then prompts you to set a
scheduler configuration file password.
You must enter this password when you first launch the scheduler application (Page 117) and
under either of the following conditions:
• You downloaded a new scheduler configuration file
• Another user has logged in to Windows since your last login
NOTE
Downloading a schedule while scheduled operations are running
If scheduled operations are running when you the click the button, the scheduler
application performs these actions:
• Cancels queued device operations that have not yet started
• Logs an error event for each canceled operation
• Allows device operations that are currently running to finish
• Logs success or failure message for running operations
• Terminates future scheduled operation
If you change device information for a device with a scheduled operation, download the
scheduler configuration file. The scheduler application then has the current information for
the device.
NOTE
Canceling running operations
When an operation is running, the scheduler application displays a Cancel button for the
operation. Click the Cancel button to cancel the running operation.
The scheduler application cancels operations that are queued but not running. The scheduler
displays "Canceling" in the Status column while it is canceling a queued operation. It displays
"Completed" when it finishes canceling the operation.
The scheduler application does not cancel operations that are actively running. These
operations must run to completion because they have already started. The scheduler Event
Log includes the result of the operation.
The state of each operation, enabled or disabled, remains in effect until you change it. In the
Scheduler settings of the Options menu (Page 95), you can select whether to enable all
operations by default.
If you do not automatically launch the scheduler when you log in to Windows, then you must
launch the scheduler application as described previously.
In minimized operation, the Scheduler operation runs operations in the background.
NOTE
Considerations when viewing the Scheduler Event Log
Close the scheduler Event Log after you view it. If you leave the file open on your
programming device, the scheduler cannot write new event entries to this file. If the
scheduler cannot access the file because the file is open, the scheduler will create a new file
with the new event entries.
If you have left the scheduler Event Log open and select "View Event Log", you might not see
the latest event entries. In this case, browse to the folder on your programming device that
currently contains the Scheduler Event Log files. Open the file that corresponds to the events
you want to view.
You can find the folder path in for the Scheduler Event Log in the Scheduler Event Log
Settings. If you have changed the path in the Scheduler Event Log Settings, old Scheduler
Event Log files might be on your programming device in their former location.
NOTE
Exiting the scheduler application
Do not use the Windows Task Manager to end the scheduler application. Forcing the
scheduler to terminate unexpectedly while device operations are in progress could leave
devices in an indeterminate state. You might have to power cycle devices to restore
communication with the SIMATIC Automation Tool.
Use only the SIMATIC Automation Tool Scheduler shortcut menu to exit the scheduler
application.
If you click the X in the top right corner of the SIMATIC Automation Tool Scheduler window,
the scheduler application user interface closes, but the scheduler application continues
running in the background.
Limitations
The SIMATIC Automation Tool prohibits the following device operations to CPUs connected
through a CM or CP:
• Program Update (Page 49)
• Firmware Update (Page 42)
• Full Backup (Page 58)
• Restore Device (Page 60)
• Reset to Factory Defaults (Page 36)
• Format Memory Card (Page 40)
Also, you cannot schedule (Page 115) a firmware update or backup for a CPU connected
through a CM or CP.
Procedure
To assign PROFIsafe addresses to fail-safe devices, follow these steps:
1. From the Device table, right-click an F-I/O module with the PROFIsafe icon .
2. Be sure that you have met these preconditions, as applicable:
– You entered the safety password. (Page 166)
– You have trusted the TLS certificate (Page 25).
– The device configuration for the module matches the hardware.
– The corresponding F-CPU has a safety program (Page 169).
– Device communicates using PROFINET and not PROFIBUS.
3. Select "Assign PROFIsafe address" from the shortcut menu.
The SIMATIC Automation Tool displays the "Assign PROFIsafe address" dialog. For a local
module, the dialog displays the F-CPU that controls the F-I/O module and other local
modules.
For distributed I/O, the dialog displays the interface module that connects to the F-I/O
module and other modules on the device.
An empty orange outline box indicates a connection to the device. If this orange outline
box is missing, the SIMATIC Automation Tool could not make a connection to the device.
4. Select the device or devices for which you want to assign PROFIsafe addresses.
Initially, the dialog selects the F-I/O module that you selected from the Device table. You
can also select other F-I/O modules or the device (F-CPU or interface module) that
connects to the F-I/O modules. For ET 200AL modules, you can only select one module.
You can select or deselect check boxes at any time during this procedure prior to assigning
PROFIsafe addresses.
5. Select how you want to identify modules:
– By LED flashing: The LEDs on the selected modules flash. Use this option when you
want to visually note that the modules with flashing LEDs are the ones for which you
want to assign PROFIsafe addresses.
– By serial number: The dialog displays the serial number of the device that connects to
the F-I/O, either an F-CPU or interface module. Use this option when you have checked
the serial number of an F-CPU or interface module and you want to assign PROFIsafe
addresses to F-I/O for that device. In addition, the LEDs on the F-I/O flash.
Note that ET 200AL modules do not support identification by serial number.
6. Click the Identification button.
The "Assign PROFIsafe address" dialog displays the serial number of the F-CPU or interface
module if you selected "By serial number". For both identification methods, the LEDs on
the F-I/O module flash. The dialog also changes the orange outline box around the module
to a solid orange box during identification.
7. Confirm the F-I/O either by serial number or by LED flashing. When you are satisfied that
you have identified the correct F-I/O select the "Confirm" check box for the F-CPU, the
interface module, or for individual F-I/O modules.
8. Click the "Assign PROFIsafe address" to assign the PROFIsafe addresses to the selections
that you confirmed. You have 60 seconds to confirm that you want to assign the
PROFIsafe addresses.
If you do not confirm PROFIsafe address assignment within 60 seconds, or if you select
"No" on the confirmation dialog, the SIMATIC Automation Tool assigns no PROFIsafe
addresses. The identification remains in progress.
If you click "Yes" within 60 seconds to confirm PROFIsafe address assignment, the
SIMATIC Automation Tool assigns the F-source address and F-destination address.
NOTE
You can assign PROFIsafe addresses for ET200MP F modules that are connected through
either the active backplane or a U-Connector.
LED meanings
The LEDs on F‑I/O modules have the following meanings when you are using the "Assign
PROFIsafe address" dialog:
• On and not flashing: PROFIsafe address is not assigned
• Flashing: F-I/O module has been identified
• Off: PROFIsafe address is assigned
If you filter by the Device Type or Article Number, the Device table shows all devices at the
root level. With devices filtered, the Device table does not show a tree structure with modules
beneath CPUs. Without such a tree structure representation, the SIMATIC Automation Tool
disables all safety-relevant operations. You cannot perform safety-relevant operations if you
have filtered the Device table on the Device Type or Article Number.
You can use the General settings (Page 84) to enable/disable the display of unsupported
devices.
3. Drag the bottom right corner of the focus rectangle through the New Firmware Version
column. Like Microsoft Excel, the SIMATIC Automation Tool shows you which cells you are
including in your new focus rectangle. You can select the entire column if you choose, or
just a few cells:
4. Release the left mouse button to copy your selection into all of the cells in the new focus
rectangle for which the original selection is valid. In this example, the SIMATIC
Automation Tool copies the New Firmware Version V04.02.00 cell into cells that
correspond to S7-1200 1215C DC/DC/DC CPUs. The SIMATIC Automation Tool only copies
to CPUs that are of the same CPU type and for which the firmware update is valid:
You can use the rapid copy and paste technique for any user-editable column in the Device
table. The technique can save time for many operations where you want to copy one
selection to many places, for example:
• Device selection
• Backup files
• Comments
• Firmware updates
• Gateway
• Passwords (CPU and Program file)
• Program updates
• Recipes
• Subnet
NOTE
Hidden cells
If you have collapsed one or more expandable cell rows, the paste operation pastes into the
hidden cells. When you expand the collapsed rows, you can see the pasted content.
NOTE
Refreshing selected devices
You can only refresh top level selected devices. If a device is connected beneath another
device in the Device table, you cannot refresh that device alone.
For example, if you have an interface module (IM) that is distributed I/O to a CPU, you cannot
refresh only the interface module. If you select this interface module and refresh it, the
SIMATIC Automation Tool refreshes the CPU and all modules connected through it.
Refer to the Event Log settings (Page 91) for configuration settings for the Event Log.
Operation is successful
Operation has failed. The Result column describes the reason for failure. If you save the Event
Log, these entries begin with "FAILED:".
Operation is successful but includes a warning message. The Result column describes the
warning information. If you save the Event Log, these entries begin with "WARNING:".
Information only
The specified firmware update file is not compat The device hardware requires that the firmware
ible with the device because the hardware requires update file (Page 42) must have a newer version
a firmware version that is newer. than the version in the device. Select a newer firm
ware update version.
The specified firmware update file is not compat The device hardware requires that the firmware
ible with the device because the hardware requires update file (Page 42) must have an older version
a firmware version that is older. than the version in the device. Select an older firm
ware update version.
The module ID is not valid. The API FirmwareUpdate method received a value
for the hardwareID parameter that does not corres
pond to a module. When calling the FirmwareUp
date update method, provide the correct ID for the
module.
The firmware update file was not accepted by the Select a firmware update (Page 42) file that is com
module. patible with the module you are updating.
If the module is a distributed I/O module in a
PROFINET IO-System for a CPU, place the con
trolling CPU in STOP mode, power cycle the I/O
module, and reattempt the firwmare update.
The module is not reachable. Download a valid The SIMATIC Automation Tool cannot communic
hardware configuration to the CPU or connect dir ate with the device. Download a valid device con
ectly to the device. figuration from the TIA Portal to the device. Altern
atively use the SIMATIC Automation Tool to update
the CPU program (Page 49).
Firmware update of this module is not supported The SIMATIC Automation Tool does not support
by this tool. firmware update (Page 42) for this type of module.
You cannot update the firmware for this module
with the SIMATIC Automation Tool.
The firmware update file has the same firmware The firmware update (Page 42) file has the same
version as the device. firmware version as the device. No firmware
update performed and no further action required.
Format memory card is not supported on this You cannot format the memory card for this
device. device.
The gateway address is not valid. The gateway address is not valid with the subnet
mask and IP address. Verify that your IP address,
subnet mask, and gateway (Page 31) are correct
for your device and network.
An internal error has occurred. Internal error within the SIMATIC Automation Tool.
Contact your Siemens representative.
Target server address is invalid. The SIMATIC Automation Tool could not connect to
the CPU or HMI device. Verify the MAC address or
IP address of the device.
The project cannot be opened with this version of The project is from an older release of the SIMATIC
the SIMATIC Automation Tool. Automation Tool. The SIMATIC Automation Tool
cannot open a project from this release. See the
topic "Saving and opening .sat project files (Page
68)".
Invalid signature detected. Repair the installation. The SIMATIC Automation Tool installation is incom
plete or corrupted. Reinstall the SIMATIC Automa
tion Tool.
The IP address is not valid. The IP address does not follow requirements for IP
addresses. Enter a valid IP address (Page 31).
The MAC address is not valid. The MAC address does not follow requirements for
MAC addresses. Enter a valid MAC address.
This operation is not permitted because another Only one software tool can connect to a device.
configuration tool such as the TIA Portal is connec Close the other connection to the device, for
ted. example, by going offline in the TIA Portal. Then
reattempt the operation from the SIMATIC Automa
tion Tool.
An already active ES instance does not support This device does not support more than one online
MultiES. connection from the SIMATIC Automation Tool, the
TIA Portal, or another tool at the same time. Go off
line in the TIA Portal or other tool and then reat
tempt the SIMATIC Automation Tool operation.
The maximum number of CPU connections has This device supports a limited number of online
been exceeded. connections from the SIMATIC Automation Tool,
the TIA Portal, or another tool at the same time.
The limit has been exceeded. Go offline in the TIA
Portal or other tool and then reattempt the SIMAT
IC Automation Tool operation.
Connections to this CPU from multiple tools are not This device supports a limited number of online
supported. connections from the SIMATIC Automation Tool,
the TIA Portal, or another tool at the same time.
Connections from multiple tools is not supported.
Go offline in the TIA Portal or other tool and then
reattempt the SIMATIC Automation Tool operation.
Client wants to make write operation on object The CPU cannot perform this operation in RUN
variable or link which cannot be changed in CPU mode. Change the CPU to STOP mode (Page 30).
RUN Mode.
The operation completed successfully. Information only
The operation was canceled by the user. Information only
The device does not support the requested opera The Event column shows the operation that did not
tion. succeed for the device in the Device column. Check
the Device catalog (Page 99) for the operations
that the device supports for the current firmware
version.
Parameter is out of range. An application called the API method SetOperating
State with an invalid value. You must call this
method with either "Stop" or "Run" for the operat
ing mode state.
The PROFINET name is not valid. The PROFINET name (Page 33) is not valid. Enter a
valid PROFINET name that is unique from all other
devices.
Could not establish a connection to the device The SIMATIC Automation Tool could not connect to
the device. Check your network connections. Verify
that another software tool, such as the TIA Portal,
does not have an online connection to the device.
If so, go offline from the other tool. Verify that the
device is on the subnet (Page 31) you specified.
Check your routing if applicable. Set your network
interface (Page 6) to the "Auto" selection if you
haven't already.
The operation has timed out. The CPU did not complete the operation. Reat
tempt the operation. If the operation continues to
time out, check your device and network commu
nications.
Connection is de-legitimated because CPU pass The CPU password has timed out due to inactivity.
word timeout. Enter the CPU password and try the operation
again.
Failed to set IP address The SIMATIC Automation Tool could not set the IP
address (Page 31). Check that the IP address is val
id and that it is unique. Verify that the device con
figuration in the STEP 7 project permits setting the
IP address directly at the device.
Failed to set PROFINET name The SIMATIC Automation Tool could not set the
PROFINET name (Page 33). Check that the
PROFINET name is valid and that it is unique. Verify
that the device configuration in the STEP 7 project
permits setting the IP address directly at the device.
The subnet mask is not valid. The subnet mask (Page 31) does not follow
requirements for a valid subnet mask. Enter a valid
subnet mask.
The device is not supported or could not be initial The SIMATIC Automation Tool does not support
ized. this device, or could not initialize the device. Check
the Device catalog (Page 99) for supported devices
and versions.
The device did not accept the firmware update file. The device rejected the firmware update (Page 42).
Verify that the firmware update file is valid for your
device. If updating from the old format, ensure
that you select the header .upd file for the "New
Firmware Version" field.
Some modules require external power sources. If
the module has dual processors, verify that power
is applied to both processors. If the module has a
power LED indicator, verify that the LED is green.
Test that the device is functioning properly.
Failed to zip contents of folder The SIMATIC Automation Tool could not zip the
contents of the folder. Check for sufficient file sys
tem space for the zip file. Also, check for file folder
permissions. Either condition could be the source
of the problem.
Error writing to file The SIMATIC Automation Tool could not save the
file to the programming device. Check your file
space and file permissions.
Error creating file The SIMATIC Automation Tool could not create the
file on the programming device. Check your file
space and file permissions.
Error deleting file The SIMATIC Automation Tool could not delete the
file from the programming device. Check your file
permissions.
Error deleting folder The SIMATIC Automation Tool could not delete the
folder from the programming device. Check the
folder permissions on your programming device.
Be sure the folder is not open.
Error creating folder The SIMATIC Automation Tool could not create a
temporary folder for saving service data. Check file
space on your programming device.
You must purchase a license to use the API. You do not have a valid license to use the API. You
can use the 21-day free trial license for 21 days.
Otherwise, purchase a license for the SIMATIC
Automation Tool or purchase the Software
Developers Kit (SDK) to use the API.
Invalid timeout value. Valid values are 180-999 In the Communications options (Page 85), the
seconds. timeout value for communications operations is
out of range. Set the value to a number from 180
to 999 seconds.
No data in device to backup The SIMATIC Automation Tool cannot create a
backup (Page 58) if the device does not have a user
program. Download your project from STEP 7 to
the device, or update the program (Page 49) from
the SIMATIC Automation Tool. If you have a previ
ous backup file for this device, you can restore
(Page 60) it from the SIMATIC Automation Tool.
Error reading from stream The SIMATIC Automation Tool could not read from
a previously-saved project file (Page 68). Verify that
the project file is from a compatible version of the
SIMATIC Automation Tool. Open a valid project if
one is available.
Error writing to stream The SIMATIC Automation Tool could not write and
save a project file (Page 68) for the current project.
Check file space on your programming device.
The HMI project file is invalid or incomplete. You are attempting to perform an HMI program
update (Page 49). The program update file is cor
rupt. You cannot restore this file.
The HMI project is not compatible with the device. You are attempting perform a program update
(Page 49) to an HMI device that is not compatible
with the HMI device. You can only perform a pro
gram update that corresponds to your HMI device
hardware.
A file operation could not be completed because of The location for the file operation is write-protec
write protection. ted. Choose a folder location on your programming
device that is not write-protected.
Failed to change the IP address of this device The SIMATIC Automation Tool could not set the IP
address (Page 31). Enter a valid IP address. Check
your network communication connections.
Failed to change the PROFINET name of this device The SIMATIC Automation Tool could not set the
PROFINET name (Page 33). Enter a valid PROFINET
name. Check your network communication con
nections.
Failed to identify the device The identify operation could not find the device.
Check that the device is on your network.
Request aborted Information only
The device does not yet support device addon The program update (Page 49) file includes
transfer. addons. The HMI device you are trying to update
does not support addons. You can only update this
HMI device with a program that does not have
addons.
Not enough resources to run requested operation The requested operation requires more system
resources than are available. Close some applica
tions on your programming device and try again.
Insufficient space in file system The file system does not have enough space for the
requested operation. Delete files to create some
space on the file system or choose a different file
system that has more space.
Remote transfer disabled Internal error in the HMI device. Contact customer
support for your HMI device.
Rescue backup not possible, for example due to Internal error in the HMI device. Contact customer
wrong device state or wrong firmware file support for your HMI device.
Rescue restore not possible, for example due to Internal error in the HMI device. Contact customer
wrong device state support for your HMI device.
Runtime installation is broken. Internal error in the HMI device. Contact customer
support for your HMI device.
Runtime is not installed. Internal error in the HMI device. Contact customer
support for your HMI device.
General problem with security library handling Internal error in the HMI device. Contact customer
support for your HMI device.
Another service is already active. Internal error in the HMI device. Contact customer
support for your HMI device.
General failure on checking file signature Internal error in the HMI device. Contact customer
support for your HMI device.
File signature is invalid. Internal error in the HMI device. Contact customer
support for your HMI device.
File is not signed. Internal error in the HMI device. Contact customer
support for your HMI device.
A store read operation failed. Internal error in the HMI device. Contact customer
support for your HMI device.
A store write operation failed. Internal error in the HMI device. Contact customer
support for your HMI device.
Type conversion failed Internal error in the HMI device. Contact customer
support for your HMI device.
An unexpected operating system error occurred. Internal error in the HMI device. Contact customer
support for your HMI device.
An addon with the given name is not installed. Internal error in the HMI device. Contact customer
support for your HMI device.
An application with the given id is not installed. Internal error in the HMI device. Contact customer
support for your HMI device.
An application addon with the given id is not Internal error in the HMI device. Contact customer
installed. support for your HMI device.
An application addon references an application Internal error in the HMI device. Contact customer
that is not installed. support for your HMI device.
The recipe filename or path is not valid. Verify that the filename exists and that the name is
valid.
Not enough storage space to perform this opera The SIMATIC memory card in the CPU does not
tion have enough space to store the file. Delete
extraneous content from the memory card or use a
memory card with a higher capacity.
A more recent incompatible firmware image exists The firmware on the device is more recent than the
on the target device. If you update the operating firmware update (Page 42) you have chosen. If you
system, then recipe data, user data, and some sys proceed with this firmware update, you risk delet
tem settings could be permanently deleted. ing recipe data, user data, and some system set
tings. Verify that you want to update to this firm
ware before proceeding.
An older incompatible firmware image exists on Internal error in the HMI device. Contact customer
the target device. If you update the operating sys support for your HMI device.
tem update recipe data user data and some system
settings could be deleted permanently.
A more recent incompatible Runtime exists on the Internal error in the HMI device. Contact customer
target device. support for your HMI device.
An older incompatible Runtime exists on the target Internal error in the HMI device. Contact customer
device. support for your HMI device.
No Runtime is installed on the target device. Internal error in the HMI device. Contact customer
support for your HMI device.
Not enough memory on the target device. Internal error in the HMI device. Contact customer
support for your HMI device.
Incorrect display orientation (Portrait configured Internal error in the HMI device. Contact customer
Landscape on the HMI device). support for your HMI device.
Incorrect display orientation (Landscape configured Internal error in the HMI device. Contact customer
Portrait on the HMI device). support for your HMI device.
General error. Compile the project again and Internal error in the HMI device. Contact customer
repeat the download. support for your HMI device.
General error. Repeat the download. Internal error in the HMI device. Contact customer
support for your HMI device.
No Runtime is installed on the target device. Internal error in the HMI device. Contact customer
support for your HMI device.
The configured device does not match the target Internal error in the HMI device. Contact customer
device. support for your HMI device.
A non-compatible Runtime is installed on the tar Internal error in the HMI device. Contact customer
get device. support for your HMI device.
An incorrect runtime version is installed. The Internal error in the HMI device. Contact customer
installed runtime cannot process the project. Install support for your HMI device.
the runtime manually on the target device.
An error occurred and the device identity could not The SIMATIC Automation Tool could not determine
be determined. the identify of this CPU.
The device identity was changed. Scan the network The CPU device identity has changed from when
again. the SIMATIC Automation Tool connected to the
CPU. Rescan the network (Page 15) to establish the
actual device identity for the SIMATIC Automation
Tool.
The connected interface was not found. The selected Network Interface no longer exists.
Check the connections of your network interface
and test that it is working. When you know that the
network interface is valid, select this network inter
face (Page 167) from the SIMATIC Automation
Tool.
Device is not selected. No device is selected. You must select a device
from the Device table.
Safety-relevant operations require the safety pass You must provide the safety password to perform
word. the safety-relevant operation.
Internal application error An internal error occurred when setting a CPU pass
word. Set a valid CPU password and check whether
the device is protected.
The CPU password entered is invalid. Enter a valid CPU password.
The IP address of the device is a duplicate on the The SIMATIC Automation Tool found a duplicate IP
network. address on the network, perhaps from an external
change. Sort your Device table (Page 128) by the IP
address to find the duplicate. Correct one of the
addresses to eliminate the duplicate.
The IP address entered is a duplicate on the net You entered an IP address that is a duplicate of
work. another IP address. Enter an IP address that is
unique on the network. Sort your Device table
(Page 128) by the IP address to find the duplicate.
Duplicate PROFINET name Enter a PROFINET name that is unique on the net
work.
Safety-relevant operations must be confirmed. To perform any of the following operations for an
F-CPU, you must confirm the operation:
- Reset to factory defaults (Page 36)
- Restore (Page 60)
- Program update (Page 49)
- Format memory card (Page 40)
If you reached this message from an application
using the API, you must set the SelectedConfirmed
property for the CPU.
There is no SD card present or the SD card is Formatting a memory card (Page 40) requires the
already empty. presence of a SIMATIC memory card. Insert a
SIMATIC memory card in the CPU. If the card is
present, but has no file contents, you can ignore
this message.
The program file is invalid or cannot be opened by The SIMATIC Automation Tool cannot access the
this version of the SIMATIC Automation Tool. program update file (Page 49) at the path specified
in the Options dialog. Verify the path name in the
Program Update settings of the Options dialog.
Result of CRC comparison: Online and offline col The program update (Page 49) failed. The program
lective F-signatures do not match. update file does not match the program in the CPU
after the program update operation. Try these
steps:
1. Reset the CPU to factory defaults
2. Format the memory card if you are using one.
3. Reattempt the program update.
If the error persists, you cannot use this program
update file.
The program file cannot be downloaded to an The device version of the target device is older
older device. than the version in the program file. Upgrade the
device to a newer version or choose a program
update file (Page 49) that is compatible for the
older device.
Project's IP suite is not reachable Verify the IP address, subnet mask, and gateway
(Page 31). Correct any values that are incorrect for
your network.
IP suite is not reachable. Verify the IP address, subnet mask, and gateway
(Page 31). Correct any values that are incorrect for
your network.
The backup file contained an IP suite that is not After the restore (Page 60) operation, the SIMATIC
reachable via PROFINET communications. Automation Tool cannot access the device. The IP
suite (Page 31) in the restored project (IP address,
subnet mask, gateway) does not correspond to the
actual device and subnet. Correct and set the IP
suite values for the device. Set the Network Inter
face Card to the "Auto" selection if you haven't
already.
The IP address in the new program file is not Resolve the conflict in IP addresses. Set one of the
unique to the network. devices to a different IP address.
A safety program cannot be loaded to a standard You cannot download a safety program to a stand
CPU. ard CPU. You can download only a standard pro
gram to a standard CPU.
The diversity check on the CPU password entered The SIMATIC Automation Tool cannot connect to
failed. the CPU. Device identification data such as the
MAC address or serial number is different between
the SIMATIC Automation Tool Device table and the
actual device. Scan the network (Page 15).
The backup file is not valid for this device. The backup file (Page 58) you selected is not valid
for this CPU. Select a backup file that corresponds
to your CPU device type.
The backup file extension is not valid for this The file extension of the file is invalid. Select a
device. backup file (Page 58) with the .s7pbkp file exten
sion.
The operation failed. One of the following operations failed:
- Reset to factory defaults (Page 36)
- Memory reset (Page 39)
- Format memory card (Page 40)
As applicable, set the device to STOP mode or
ensure that a SIMATIC memory card is in the CPU.
Reattempt the operation.
The firmware file is not valid for this device. Select a firmware update file (Page 42) that corres
ponds to the device.
The program file password could not be validated. The "Password in Program File" that you entered for
a program update file (Page 49) does not corres
pond to any of the passwords in the program file.
To update a program, you must enter a valid pro
gram file password.
The program file contains an IP address that The SIMATIC Automation Tool does not allow you
already exists on the network. to restore (Page 60) a program file that causes a
duplicate IP address. Change the IP address of the
device that is the same or restore a different pro
gram file.
Missing program file password You must enter a valid password for the program.
Invalid program file password You must enter a valid password for the program.
The program file is not valid for this device. Select a program update file (Page 49) that corres
ponds to the device.
The program file password entered is invalid or not Enter a password for the program file that has a
sufficient to complete the operation. sufficient access level for the operation.
The requested device was not found on the net The SIMATIC Automation Tool could not find the
work. device on the network. Check network interface,
network connection, and IP address. Close
S7‑PLCSIM, simulated PLC instances, or other simu
lation software if running.
You cannot insert a device that already exists. You attempted to insert a device (Page 20) that is
already in the Device table. You can only insert a
device that is not yet in the Device table.
The IP address cannot be changed because it is You attempted to set an IP address (Page 31) to an
already on the network. IP address that is already in use. Set the device IP
address to a unique address.
The PROFINET name cannot be changed because it You attempted to set the PROFINET name (Page
is already on the network 33) to a PROFINET name that is already in use.
Select a unique PROFINET name.
Could not establish a connection to the device The SIMATIC Automation Tool could not establish a
connection to the device. Check network interface,
network connection, and IP address.
The device could not be fully initialized. The SIMATIC Automation Tool could not initialize
the device. Ensure that the device is on the same
network as your programming device.
The SIMATIC Automation Tool does not support You are attempting to use a program that has a
CPU with newer programs. newer version than The SIMATIC Automation Tool
supports. Check the Device catalog (Page 99) to
determine the version support for your device.
IP suite is not valid. The IP address, gateway, and subnet (Page 31)
combination is not valid. Enter a valid IP suite.
The selected backup file is not compatible with this The backup file (Page 58) that you chose is not
device compatible for your device. Check that the backup
file is for the correct device, and that it is for the
correct version of the device.
The IP address changed or there is a duplicate IP The IP address for this device has been changed
address on the network. since the last network scan, or another device has
the same IP address. Scan the network (Page 15)
and resolve any IP address conflicts.
No devices were found on the scan. Check your The SIMATIC Automation Tool did not find any
network interface and turn off simulation software. devices on the network scan. Check network inter
face and network connections. Check the subnet
for the devices. Close S7‑PLCSIM, simulated PLC
instances, or other simulation software if running.
Result of CRC comparison: Online and offline col Information only: Your operation with an F-CPU
lective F-signatures match. was successful. You do not need to perform any
additional action.
The device could not be inserted into the Device The SIMATIC Automation Tool could not insert the
table. device you entered into the Device table (Page 20).
Check that the IP address is unique and that the
data you entered corresponds to a device on your
network.
You cannot insert a device that has an IP address You attempted to insert a device (Page 20) with an
that is already on the network. IP address that belongs to another device. You
must enter a unique IP address when you enter a
device.
The new gateway address is not valid. You entered an invalid gateway address (Page 31).
Enter a gateway address that is valid for your net
work.
The new IP address is not valid. You entered an invalid new IP address (Page 31).
Enter a valid IP address that.
The new PROFINET name is not valid. You entered an invalid new PROFINET name (Page
33). Enter a valid PROFINET name.
The new subnet mask is not valid. You entered an invalid subnet mask (Page 31).
Enter a subnet mask that is valid for your device
and network.
Could not read the F-signatures F-CPUs include a fail-safe signature. The SIMATIC
Automation Tool could not read the fail-safe signa
ture from the device. Your operation cannot pro
ceed with this error.
Format the memory card (Page 40) if you are using
one. Reset the device to factory settings (Page 36).
Then repeat the operation.
Invalid or not specified network interface Select a valid network interface (Page 167) from
the dropdown list for your communication setup.
The CPU password entered is not sufficient to com You need a higher access level to perform the oper
plete the operation. ation. Enter a CPU password with a sufficient
access level for the operation you want to perform.
There are no passwords in the program file. The program file contains no passwords. This mes
sage is informational and requires no action.
The project contains a file format that is no longer The project is from an older release of the SIMATIC
supported. Automation Tool. The SIMATIC Automation Tool
cannot open a project from this release. See the
topic "Saving and opening .sat project files (Page
68)".
Project open has been canceled. You started to open a project (Page 68) and can
celed the action. No further action is necessary.
A program file password is needed You must enter the password for the program file.
Could not open, read, or process the backup file. The SIMATIC Automation Tool could not open,
read, or process the backup file (Page 58). Use a
backup file that corresponds to your device and
version,
Incompatible program file for this device. The program file is not compatible for your device.
Use a program file that corresponds to your device
and version.
The SIMATIC Automation Tool does not support the The SIMATIC Automation Tool does not support the
project file. project file in the device. Check the device config
uration in the STEP 7 project and check the device
support in the Device catalog.
The program's hardware configuration is not valid The hardware configuration of the STEP 7 program
for the attached device. is not valid for the actual device on the network.
Check the device configuration in the STEP 7
project and check the device support in the Device
catalog.
The file system cannot be loaded. Try power cyc The SIMATIC Automation Tool could not load the
ling the CPU. files from the CPU. CPU files are possibly corrupt.
Power cycle the CPU. If the problem persists, reset
the CPU to factory defaults.
SNMP: An invalid password was entered. You entered an invalid password in the SNMP Ver
sion 3 profile (Page 93). Enter a valid password for
the device.
SNMP: The value does not exist An SNMP value is invalid. Verify your SNMP profile
(Page 93) settings.
SNMP: The value cannot be changed In an SNMP profile (Page 93), you attempted to
change a value to an invalid value. Enter a valid
value.
SNMP: The value is read only and cannot be You attempted to change a read-only value in an
changed. SNMP profile (Page 93). You cannot change this
value.
Invalid authentication algorithm The authentication algorithm in the SNMP Version
3 profile is invalid. Select a valid authentication
algorithm from the dropdown list on the SNMP
profile (Page 93) "Add" dialog.
Invalid authentication password The authentication password in the SNMP Version
3 profile is invalid. Enter a valid authentication
password on the SNMP profile (Page 93) "Add" dia
log.
Invalid context name The context name in the SNMP Version 3 profile is
invalid. Enter a valid context name on the SNMP
profile (Page 93) "Add" dialog.
Invalid privacy algorithm The privacy algorithm in the SNMP Version 3 profile
is invalid. Enter a valid privacy algorithm on the
SNMP profile (Page 93) "Add" dialog.
Invalid privacy password The privacy password in the SNMP Version 3 profile
is invalid. Enter a valid privacy password on the
SNMP profile (Page 93) "Add" dialog.
Invalid profile name The profile name in the SNMP Version 1, 2, or 3
profile is invalid. Enter a valid profile name on the
SNMP profile (Page 93) "Add" dialog.
Invalid read community The read community in the SNMP Version 1 or 2
profile is invalid. Enter a valid read community on
the SNMP profile (Page 93) "Add" dialog.
Invalid security level The security level in the SNMP Version 3 profile is
invalid. Enter a valid security level on the SNMP
profile (Page 93) "Add" dialog.
Invalid server IP address The server IP address in the SNMP Version 1, 2, or 3
profile is invalid. Enter a valid server IP address on
the SNMP profile (Page 93) "Add" dialog.
Invalid server port The server port in the SNMP Version 1, 2, or 3 pro
file is invalid. Enter a valid server port on the SNMP
profile (Page 93) "Add" dialog.
Invalid SNMP version The SNMP version is invalid. Select 1, 2, or 3 for the
SNMP version number on the SNMP profile (Page
93) "Add" dialog.
Invalid user name The user name in the SNMP Version 3 profile is
invalid. Enter a valid user name on the SNMP pro
file (Page 93) "Add" dialog.
Invalid backup type The HMI backup (Page 58) type is invalid. Valid
backup types for an HMI are full, recipe, or user
administration data. Provide a valid backup type.
One or more device diagnostic buffers could not be When exporting device diagnostics (Page 76), the
accessed SIMATIC Automation Tool could not access the dia
gnostics for one or more devices. Check that the
devices in the Device table are connected to the
communications network. Check the Event Log for
additional messages about inaccessible devices. If
necessary, correct network connections and scan
the network (Page 15).
Automation License Manager error - connection The Automation License Manager had an error as
failed, check network access to ALM server described. Follow the advice in the message.
Automation License Manager error - internal error, The Automation License Manager had an error as
task has been aborted, contact Siemens support described. Follow the advice in the message.
Automation License Manager error - internal error, The Automation License Manager had an error as
Wrong function arguments, contact Siemens sup described. Follow the advice in the message.
port
Automation License Manager error - internal error, The Automation License Manager had an error as
bad result, contact Siemens support described. Follow the advice in the message.
Automation License Manager error - Check user The Automation License Manager had an error as
access privileges to folder described. Follow the advice in the message.
Automation License Manager error - internal error, The Automation License Manager had an error as
Batch API, contact Siemens support described. Follow the advice in the message.
Automation License Manager error - internal error, The Automation License Manager had an error as
Batch API Output file couldn't be created, contact described. Follow the advice in the message.
Siemens support
Automation License Manager error - internal error, The Automation License Manager had an error as
Batch API output file already exists, contact described. Follow the advice in the message.
Siemens support
Automation License Manager error - internal error, The Automation License Manager had an error as
Batch API wrong argument, contact Siemens sup described. Follow the advice in the message.
port
Automation License Manager error - internal error, The Automation License Manager had an error as
Batch API wrong argument number, contact described. Follow the advice in the message.
Siemens support
Automation License Manager error - internal error, The Automation License Manager had an error as
Batch API wrong input file, contact Siemens sup described. Follow the advice in the message.
port
Automation License Manager error - internal error, The Automation License Manager had an error as
Batch API wrong input xml stream, contact described. Follow the advice in the message.
Siemens support
Automation License Manager error - internal error, The Automation License Manager had an error as
Batch API wrong output parameter, contact described. Follow the advice in the message.
Siemens support
Automation License Manager error - connection The Automation License Manager had an error as
failed, check network access to ALM server described. Follow the advice in the message.
Automation License Manager error - internal error, The Automation License Manager had an error as
cryptography failed, contact Siemens support described. Follow the advice in the message.
Automation License Manager error - internal error, The Automation License Manager had an error as
global cleanup failed, attempt ALM restart described. Follow the advice in the message.
Automation License Manager error - Initialization The Automation License Manager had an error as
Error, attempt ALM restart described. Follow the advice in the message.
Automation License Manager error - internal error, The Automation License Manager had an error as
session cleanup failed, attempt ALM restart described. Follow the advice in the message.
Automation License Manager error - internal error, The Automation License Manager had an error as
session initialization failed, attempt ALM restart described. Follow the advice in the message.
Automation License Manager error - internal error, The Automation License Manager had an error as
function not found, contact Siemens support described. Follow the advice in the message.
Automation License Manager error - internal error, The Automation License Manager had an error as
bad pointer, contact Siemens support described. Follow the advice in the message.
Automation License Manager error - No connection The Automation License Manager had an error as
available, check the network connection described. Follow the advice in the message.
Automation License Manager error - internal error, The Automation License Manager had an error as
open session failed, contact Siemens support described. Follow the advice in the message.
Automation License Manager error - the timeout The Automation License Manager had an error as
time was reached, restart the system or contact described. Follow the advice in the message.
Siemens support
Automation License Manager error - internal error, The Automation License Manager had an error as
not enough memory, restart the system or contact described. Follow the advice in the message.
Siemens support
Automation License Manager error - Failure in The Automation License Manager had an error as
receiving network data, check the network connec described. Follow the advice in the message.
tion
Automation License Manager error - internal error, The Automation License Manager had an error as
resources missing, contact Siemens support described. Follow the advice in the message.
Automation License Manager error - internal error, The Automation License Manager had an error as
result mismatch, contact Siemens support described. Follow the advice in the message.
Automation License Manager error - Failed sending The Automation License Manager had an error as
network data, check the network connection described. Follow the advice in the message.
Automation License Manager error - service not The Automation License Manager had an error as
running, restart the ALM service described. Follow the advice in the message.
Automation License Manager error - internal error, The Automation License Manager had an error as
session ID missing, contact Siemens support described. Follow the advice in the message.
Automation License Manager error - internal error, The Automation License Manager had an error as
session ID doesn't exist, contact Siemens support described. Follow the advice in the message.
Automation License Manager error - internal error, The Automation License Manager had an error as
task is already running, contact Siemens support described. Follow the advice in the message.
Automation License Manager error - internal error, The Automation License Manager had an error as
unknown error, contact Siemens support described. Follow the advice in the message.
Automation License Manager error - internal error, The Automation License Manager had an error as
User specified an unknown option, contact described. Follow the advice in the message.
Siemens support
The maximum number of PC connections has been This device supports a limited number of online
exceeded connections from the SIMATIC Automation Tool,
the TIA Portal, or another tool at the same time.
The limit has been exceeded. Go offline in the TIA
Portal or other tool and then reattempt the SIMAT
IC Automation Tool operation.
The filename or path is not valid Check the full path name in the Options Settings
(Page 82) dialog. Verify that the file exists at the
location. Recreate or rename the file or folder if
necessary.
The running service request has been aborted by The Automation License Manager had an error as
the client described. Follow the advice in the message.
SNMP version is invalid The SNMP version (Page 93) is invalid. Select 1, 2,
or 3 for the SNMP version number.
You must power cycle the CPU before performing This operation requires a power cycle of the CPU.
this operation. Power cycle the CPU and try the operation again.
Duplicate folder names with a different folder path When you create an archive file, you cannot use a
is not allowed. duplicate folder name in a different folder path.
Use a unique folder name or use the same path.
Duplicate file names with a different folder path is When you create an archive file, you cannot use a
not allowed. duplicate file name in a different folder path. Use a
unique file name or use the same path.
Feature not supported under current licensing The SIMATIC Automation Tool supports a Basic and
model. Upgrade your license to perform this opera Advanced license. Purchase the license (Page 110)
tion. you need for your operations.
This feature is not supported for third party API The SIMATIC Automation Tool user interface
users. requires this feature but it is not available for
developers using the API to create custom applica
tions.
The advanced parameter is not supported for third A parameter in an API method call is reserved for
party API users. the SIMATIC Automation Tool. The parameter is not
for use in application development using the API.
The CPU now contains a protection level that is After a program update or restore from backup, the
weaker than what previously existed. CPU password is at an access level that is at a lower
protection level than before the operation. For
example, a CPU with full access (write) protection
might have only read access protection after the
operation.
Could not read protection level to check access The CPU password is not sufficient to check the
level. access level to the CPU. Enter a password with at
least read access.
Changing the IP address is not allowed in NAT You cannot change the IP address for a device in a
router configurations. network with a NAT router configuration.
IP address and Router IP address cannot be the The IP address of the device and the IP address of
same the router must be unique.
The operation is not allowed through a CM / CP You can only perform this operation though the
CPU Ethernet interface. You cannot perform this
operation through a CM/CP interface.
Requested item does not exist on memory card. The requested file does not exist on the SIMATIC
memory card of the device.
DCP operations are not possible to devices behind Devices behind routers do not support DCP opera
routers. tions (Page 123). You can only perform operations
through the IP address.
The operation is not supported through a CM/CP The SIMATIC Automation Tool cannot perform the
communication module. named operation through a CM or CP. Check the
specific device operation (Page 122) for restric
tions.
An unknown communication error occurred or the The API could not communicate with the HMI or
operation is not supported by the HMI. the HMI did not support the attempted operation.
Check the connection to the device. Check the
operations that the device supports.
You must trust the TLS certificate before a connec Verify the certificate and select "Always" for the
tion to the device is allowed. Trust TLS Certificate choice for this device.
Secure communication has been disabled on the To communicate with the device, verify the certific
CPU. Future connections to the device will not be ate and select "Always" for the Trust TLS Certificate
allowed. choice for this device.
Secure communication has been enabled. You This CPU has enabled secure communication.
must trust the TLS certificate before a connection Select "Always" for the Trust TLS Certificate choice
to the device is allowed. for this device.
Secure communication has changed and the boot The configuration for secure communication is
strap certificate is now being used on the CPU, now the initial state for the CPU. You can commu
future connections to the device will be allowed. nicate with the CPU.
The configuration data protection password in the You must enter a matching configuration data pro
program does not match the password in the CPU. tection password or delete the protection of con
fidential PLC configuration data. Then repeat the
program update operation.
This is not a valid Siemens SD-Card. You must use a valid SIMATIC memory card. Refer
to Creating a memory card (Page 65) for the
requirements.
The program folder path is not valid. Enter a valid program folder path. Refer to Creating
a memory card (Page 65) for the requirements.
Filter scan configuration is invalid. Configure a valid filter for scanning the device net
work (Page 85).
The CPU does not contain a program; therefore, a Information only
CPU-generated certificate is being used for secure
communications.
This device has more than one interface connected The device has more than one interface connected
to SIMATIC Automation Tool. to the SIMATIC Automation Tool, for example, X1
and X2. Only use one interface connection.
The device's firmware does not support the new The device firmware does not support these
delete options. options:
• Delete IP address
• Delete configuration data password
Online hardware does not match the offline hard The SIMATIC Automation Tool cannot assign a
ware. PROFIsafe address if the offline configuration does
not correspond to the hardware. Check the device
configuration in the TIA Portal and download to the
device. Reattempt the operation.
Preconditions for F-address assignment were not Refer to the topic Assigning a PROFIsafe address (F-
met. address) for fail-safe I/O (Page 124) for precondi
tions for PROFIsafe address assignment.
F-address parameterization CRC failed. The SIMATIC Automation Tool encountered a prob
lem with the parameterization of the module. Use
the TIA Portal and download a new configuration
for this module. Then reattempt the PROFIsafe
address assignment.
A connection to the F-CPU could not be made. You Follow the instructions in the message.
must close the Assign PROFIsafe Address dialog, fix
the F-CPU connection, and start again.
A connection to the F-CPU could not be made via Follow the instructions in the message.
SNMP. You must close the Assign PROFIsafe
Address dialog, fix the F-CPU connection, and start
again.
No longer connected to F-CPU. The SIMATIC Automation Tool is no longer connec
ted to the F-CPU. Check your network connections.
.Close the Assign PROFIsafe Address dialog and try
again.
You cannot read service data from redundant CPUs When the CPU is in RUN-Redundant mode, you can
when the CPU operating mode is RUN-Redundant. not read the service data. Change the CPU to RUN-
Solo mode if you want to read the service data.
Comparison of actual hardware to configured hard The hardware configuration for the device does not
ware failed. match its actual hardware. Download the correct
device configuration from STEP 7.
IP address and Router IP address cannot be the For each router, the IP address of each device on
same when inserting a device. the router must be different from the IP address of
the router. Change the IP address of the device or
the router so they are unique.
The device could not be replaced. The SIMATIC Automation Tool encountered a prob
lem with the device's MAC address or serial number
and could not replace the device. Verify your
device replacement, make corrections, and try
again.
You cannot replace a device with the same device The replace device operation only applies to repla
cing a device with a different device. You cannot
replace the same device.
You can only use the API through the SIMATIC API objects are not available directly with a SIMATIC
Automation Tool Software Development Kit (SDK). Automation Tool installation. You must have the
SIMATIC Automation Tools Software Development
Kit (SDK) to use the API.
The backup file already exists. You have chosen to You chose not to overwrite backup files that
prevent overwriting of backup files. already exist. No action necessary.
Comparison of actual hardware to configured hard The actual hardware does not match the configura
ware failed. tion. Download the correct hardware configuration
from the TIA Portal.
IP address and Router IP address cannot be the For a device behind a router, verify that the IP suite
same when inserting a device. (IP address, subnet mask, and gateway (Page 31))
of the device is different from that of the router.
The firmware version for this device is not suppor The SIMATIC Automation Tool does not support
ted. this firmware version for this device. View the
Device Catalog to determine firmware version and
device support.
The router IP address is not valid. Enter a router IP address that follows the correct
syntax for an IP address.
The CPU returned an error. Try power cycling the The CPU returned and error to the SIMATIC Auto
CPU and retry the operation. mation Tool. Attempt to determine and correct the
cause of the error in the CPU. After power cycling
the CPU, retry the operation.
The CPU is not protected. Information only.
The NAT Router IP address and the device IP You must have a unique address pair. The NAT
address must be different. Router IP address and device IP address must be
different. Correct one of the addresses.
The export type is not valid. API only.
The export file already exists. You have chosen to Information only.
prevent overwriting of export files.
Project file was not opened because the Cancel Information only: You canceled the browser for
button was clicked. opening a project file (Page 68).
Project file <filename> was opened successfully. Information only: The SIMATIC Automation Tool
opened the named project file (Page 68).
Project file <filename> failed to open. <exception The SIMATIC Automation Tool could not open the
error> named project file (Page 68). Verify that the file is a
valid .sat project and that is compatible with your
version.
The password entered is incorrect. You entered an invalid project file (Page 68) pass
word. You must enter the correct password for this
project file.
Project file was not saved because the Cancel but Information only: You canceled the browser for
ton was selected. saving a project file (Page 68).
Export of PC Data failed. The export PC data operation (Page 77) could not
create the export file. Check for adequate disk
space and permissions for the Export folder (Page
92).
Project file <filename> failed to save. <exception The SIMATIC Automation Tool could not save the
error> project file (Page 68). Check folder permissions and
disk space on your programming device.
Export was not performed because the Cancel but Information only: You started an export (Page 71)
ton was clicked. and canceled the export.
Insert device was not performed because the Can Information only: You started to insert a device
cel button was clicked. (Page 20) and canceled the device insert.
A valid product license was not found; some You do not have a valid product license. You can
product features are disabled. only perform tasks that the SIMATIC Automation
Tool supports for an unlicensed version (Page 110).
To access all features, purchase a license as
described in the Installation Notes.
A valid product license was found. All product fea Information only: With a valid product license, you
tures are enabled. can perform all SIMATIC Automation Tool tasks
(Page 110).
Windows Administrative privileges are required to Run the export PC data operation (Page 77) with
access some PC Export data. Restart the SIMATIC Windows Administrative privileges to access some
Automation Tool using “Run as Administrator” to of the data. Restart the SIMATIC Automation Tool
export this data. using “Run as Administrator” to export this data.
The export acquired all of the requested data. The Information only: The export PC data operation
log file contains a detailed list of the exported data. (Page 77) was successful. The log file in the export
.zip file lists the exported data.
The export could not acquire all of the data. The The export PC data operation (Page 77) did not
log file contains details about the data that the export all of the data. Check the log file for the
export successfully acquired and the reasons why it reason. The log file in the export .zip file contains
could not obtain the other data. the following information:
• Information about the data that the export
operation successfully acquired and exported
• Reasons why the export operation could not
acquire the other data
Project file <filename> was saved successfully. Information only: The SIMATIC Automation Tool
successfully saved the named project file (Page
68).
The operation was canceled because the Cancel Information only
button was selected.
Changes to the project file were not saved because Information only
the No button was selected.
The project password was changed. Information only
Project password was not changed because the Information only
Cancel button was selected.
Caps Lock is on Information only
The project is already opened. Information only
Archive file <filename> was opened successfully. Information only
Archive file <filename> failed to open. <exception The SIMATIC Automation Tool could not open this
error> archive file and returned the listed error.
Archive file was not opened because the operation Information only
was canceled.
Archive file <filename> was created successfully. Information only
Archive file <filename> was not created due to The SIMATIC Automation Tool could not create this
errors. <exception error> archive file and returned the listed error.
The archive file was not created because there are The SIMATIC Automation Tool could not create the
data input errors within the Device table. archive file. Correct all invalid user data fields in
the Device table and try again.
Archive file was not created because the Cancel Information only
button was selected.
Failed to delete the Scheduler configuration file. The SIMATIC Automation Tool could not delete the
scheduler configuration file. Perhaps it is in use.
Wait until no scheduled operations are running and
try again.
The Scheduler configuration file was successfully Information only
created.
At least one operation must be configured before You must schedule at least one operation for one
the configuration file can be created. device to create a Scheduler configuration file.
Scheduler file was not created because the Cancel Information only
button was selected.
An error occurred creating the Scheduler configura The SIMATIC Automation Tool could not create the
tion file. The operation has been canceled. scheduler configuration file. Perhaps it is in use.
Wait until no scheduled operations are running and
try again.
The date or time is not valid because it is in the You can only schedule operations based on a time
past. in the future.
No devices were selected for Device Diagnostics. You must select one or more devices for the sched
The operation will not be scheduled. uled operation.
No devices were selected for Firmware Update. The You must select one or more devices for the sched
operation will not be scheduled. uled operation.
No devices were selected for Full Backup. The oper You must select one or more devices for the sched
ation will not be scheduled. uled operation.
No devices were selected for Read Data Logs. The You must select one or more devices for the sched
operation will not be scheduled. uled operation.
No devices were selected for Read Service Data. You must select one or more devices for the sched
The operation will not be scheduled. uled operation.
No devices were selected for Set Time. The opera You must select one or more devices for the sched
tion will not be scheduled. uled operation.
The CPU password entered is not sufficient to read You must enter a CPU password with read access or
Device Diagnostics. The operation will not be higher to schedule an operation to read device dia
scheduled. gnostics.
The CPU password entered is not sufficient to per You must enter a CPU password that is sufficient
form a Firmware Update. The operation will not be for a firmware update operation (Page 42). The
scheduled. CPU password access level depends on your device
model and firmware version.
The CPU password entered is not sufficient to per You must enter a CPU with at least read access to
form a Full Backup. The operation will not be schedule this operation.
scheduled.
The CPU password entered is not sufficient to Read You must enter a CPU with at least read access to
Data Logs. The operation will not be scheduled. schedule this operation.
The CPU password entered is not sufficient to Read You must enter a CPU with at least read access to
Service Data. The operation will not be scheduled. schedule this operation.
The CPU password entered is not sufficient to Set You must enter a CPU with at least read access to
Time. The operation will not be scheduled. schedule this operation.
The firmware version file is not valid for the device. You cannot use this firmware version for this
The operation will not be scheduled. device. Select a firmware update files that is com
patible with the device to schedule this operation.
The SNMP profile name is either not valid or not The SNMP profile name you selected In the sched
specified for device: <device name> uler tab (Page 115) is invalid for this device. The
red X indicates an invalid profile.
Enter the password in the Scheduler application to Enter the password in the Scheduler application to
open the configuration file. open the configuration file.
Use the Scheduler application to open the configur Use the Scheduler application to open the configur
ation file. ation file.
The start date and time is invalid for Device Dia Enter a start date and time that is in the future.
gnostics. The operation will not be scheduled. Then schedule the operation.
A start date and time was not specified for Device Enter a start date and time that is in the future.
Diagnostics. The operation will not be scheduled. Then schedule the operation.
The start date and time is invalid for Firmware Enter a start date and time that is in the future.
Update. The operation will not be scheduled. Then schedule the operation.
A start date and time was not specified for Firm Enter a start date and time that is in the future.
ware Update. The operation will not be scheduled. Then schedule the operation.
The start date and time is invalid for Full Backup. Enter a start date and time that is in the future.
The operation will not be scheduled. Then schedule the operation.
A start date and time was not specified for Full Enter a start date and time that is in the future.
Backup. The operation will not be scheduled. Then schedule the operation.
The start date and time is invalid for Read Data Enter a start date and time that is in the future.
Logs. The operation will not be scheduled. Then schedule the operation.
A start date and time was not specified for Read Enter a start date and time that is in the future.
Data Logs. The operation will not be scheduled. Then schedule the operation.
The start date and time is invalid for Read Service Enter a start date and time that is in the future.
Data. The operation will not be scheduled. Then schedule the operation.
A start date and time was not specified for Read Enter a start date and time that is in the future.
Service Data. The operation will not be scheduled. Then schedule the operation.
The start date and time is invalid for Set Time. The Enter a start date and time that is in the future.
operation will not be scheduled. Then schedule the operation.
A start date and time was not specified for Set Enter a start date and time that is in the future.
Time. The operation will not be scheduled. Then schedule the operation.
The project file contained within the archive is You cannot open this archive file because it is
already opened. already open.
The recurrence setting is not valid for the start date The frequency setting must be a valid calendar
specified for Device Diagnostics. The operation will date for every recurrence. For example, the 31st of
not be scheduled. the month does not occur every month. Enter a
valid start date and frequency setting for every
scheduled operation. Then save the scheduler con
figuration file.
The recurrence setting is not valid for the start date The frequency setting must be a valid calendar
specified for Firmware Update. The operation will date for every recurrence. For example, the 31st of
not be scheduled. the month does not occur every month. Enter a
valid start date and frequency setting for every
scheduled operation. Then save the scheduler con
figuration file.
The recurrence setting is not valid for the start date The frequency setting must be a valid calendar
specified for Full Backup. The operation will not be date for every recurrence. For example, the 31st of
scheduled. the month does not occur every month. Enter a
valid start date and frequency setting for every
scheduled operation. Then save the scheduler con
figuration file.
The recurrence setting is not valid for the start date The frequency setting must be a valid calendar
specified for Read Data Logs. The operation will not date for every recurrence. For example, the 31st of
be scheduled. the month does not occur every month. Enter a
valid start date and frequency setting for every
scheduled operation. Then save the scheduler con
figuration file.
The recurrence setting is not valid for the start date The frequency setting must be a valid calendar
specified for Read Service Data. The operation will date for every recurrence. For example, the 31st of
not be scheduled. the month does not occur every month. Enter a
valid start date and frequency setting for every
scheduled operation. Then save the scheduler con
figuration file.
The recurrence setting is not valid for the start date The frequency setting must be a valid calendar
specified for Set Time. The operation will not be date for every recurrence. For example, the 31st of
scheduled. the month does not occur every month. Enter a
valid start date and frequency setting for every
scheduled operation. Then save the scheduler con
figuration file.
This device has a duplicate IP address on the net The SIMATIC Automation Tool cannot schedule
work and Device Diagnostics cannot be performed. operations for devices with duplicate IP addresses.
The operation will not be scheduled. Set unique IP addresses (Page 31) for the devices.
Then schedule the operation and save the sched
uler configuration file.
This device has a duplicate IP address on the net The SIMATIC Automation Tool cannot schedule
work and Firmware Update cannot be performed. operations for devices with duplicate IP addresses.
The operation will not be scheduled. Set unique IP addresses (Page 31) for the devices.
Then schedule the operation and save the sched
uler configuration file.
This device has a duplicate IP address on the net The SIMATIC Automation Tool cannot schedule
work and Full Backup cannot be performed. The operations for devices with duplicate IP addresses.
operation will not be scheduled. Set unique IP addresses (Page 31) for the devices.
Then schedule the operation and save the sched
uler configuration file.
This device has a duplicate IP address on the net The SIMATIC Automation Tool cannot schedule
work and Read Data Logs cannot be performed. operations for devices with duplicate IP addresses.
The operation will not be scheduled. Set unique IP addresses (Page 31) for the devices.
Then schedule the operation and save the sched
uler configuration file.
This device has a duplicate IP address on the net The SIMATIC Automation Tool cannot schedule
work and Read Service Data cannot be performed. operations for devices with duplicate IP addresses.
The operation will not be scheduled. Set unique IP addresses (Page 31) for the devices.
Then schedule the operation and save the sched
uler configuration file.
This device has a duplicate IP address on the net The SIMATIC Automation Tool cannot schedule
work and Set Time cannot be performed. The oper operations for devices with duplicate IP addresses.
ation will not be scheduled. Set unique IP addresses (Page 31) for the devices.
Then schedule the operation and save the sched
uler configuration file.
The Scheduler application did not launch. Close The Scheduler application did not launch. Check for
other instances or restart the computer. a running instance of the Scheduler application
and close it if running. If the error persists, reboot
your programming device.
New Scheduler configuration was not created Information only
because the Cancel button was selected.
The file <filename> was not replaced because it Information only
was skipped by the user.
The file <filename> was not replaced because it is The SIMATIC Automation Tool cannot replace a
write protected. write-protected file. Select a different filename or
change the permissions.
The folder <folder name> was not replaced The SIMATIC Automation Tool cannot replace a
because it is write protected. write-protected folder. Select a different folder
name or change the permissions.
Opening a project archive requires an advanced Purchase an advanced license (Page 110) to open a
license. project archive.
Recipes files cannot be pasted because the Recipes The SIMATIC memory card must have a "Recipes"
folder is missing. folder for this paste to succeed. Create the folder.
User files cannot be pasted because the User Files The SIMATIC memory card must have a "UserFiles"
folder is missing. folder for this paste to succeed. Create the folder.
Filtered network scan is enabled. Information only
The paste operation was stopped on row <row The SIMATIC Automation Tool has encountered an
number> due to an invalid IP address or MAC invalid IP address or MAC address and the paste
address. operation has been halted.
The clipboard cannot contain more than two Check to ensure that your clipboard contains no
columns. Column 1 can contain either an optional more than two columns. Also check to ensure that
NAT router’s IP address or a device’s IP address. If each column contains the proper addresses.
column 1 contains a NAT router’s IP address then
column 2 must contain the device’s IP address that
is connected to the NAT router.
You have exceeded the maximum number of rows The SIMATIC Automation Tool dialog can only
that can be pasted into the dialog. The dialog can insert 1,000 devices at a time. Check to ensure that
only insert 1,000 devices at a time. you have pasted 1,000 or fewer rows into the dia
log.
You have exceeded the maximum number of rows The SIMATIC Automation Tool dialog can only
that can be entered into the dialog. The dialog can insert 1,000 devices at a time. Check to ensure that
only insert 1,000 devices at a time. you have entered 1,000 or fewer rows into the dia
log.
No files were copied to the clipboard. Information only
F-Address Assignment identification process was Make sure the module is seated correctly. Check
aborted. The F-Module was unreachable. Rack the cable connection between the module and the
<rack number> Slot <slot number> CPU or interface module. Repeat the identification
process.
F-Address Assignment identification process was Insert the eCoding plug. Make sure the module is
aborted. The eCoding plug is not present or some seated correctly. Check the cable connection
other issue occurred. Rack <rack number> Slot between the module and the CPU or interface
<slot number> module and try again.
F-Address Assignment identification process was The device configuration in the CPU is corrupt. Use
aborted. The F-Module was in an incorrect state. the TIA Portal and download the STEP 7 project to
Rack <rack number> Slot <slot number> the CPU.
F-Address Assignment identification process was The module’s parameterization in the CPU is cor
aborted. The F-Address has invalid CRC. Rack <rack rupt. Use the TIA Portal and download a new con
number> Slot <slot number> figuration for this module.
F-Address Assignment identification process was The module already has a valid PROFIsafe address
aborted. The F-Address is already assigned. Rack that corresponds to the configuration in the mod
<rack number> Slot <slot number> ule and the CPU. The SIMATIC Automation Tool
aborted the identification process.
F-Address Assignment identification process was Make sure the module is seated correctly. Check
aborted. The F-Module was unreachable. Rack the cable connection between the module and the
<rack number> Slot <slot number> CPU or interface module. Repeat the identification
process.
F-Address Assignment identification process was Insert the eCoding plug. Make sure the module is
aborted. The eCoding plug is not present or some seated correctly. Check the cable connection
other issue occurred. Rack <rack number> Slot between the module and the CPU or interface
<slot number> module and try again.
F-Address Assignment identification process was The module’s parameterization in the CPU is cor
aborted. The F-Address has invalid CRC. Rack <rack rupt. Use the TIA Portal and download a new con
number> Slot <slot number> figuration for this module.
F-Address Assignment identification process was The module already has a valid PROFIsafe address
aborted. The F-Address is already assigned. Rack that corresponds to the configuration in the mod
<rack number> Slot <slot number> ule and the CPU. The SIMATIC Automation Tool
aborted the identification process.
F-Address Assignment identification process was Try again. If the error recurs, power cycle the F‑I/O
aborted. The F-Module did not respond to the module. If still in error, power cycle the CPU or the
AddrFlash command as expected. Rack <rack num interface module to which the F‑I/O module is con
ber> Slot <slot number> nected.
The PROFIsafe address could not be assigned. The Make sure the module is seated correctly. Check
F-Module was unreachable. Rack <rack number> the cable connection between the module and the
Slot <slot number> CPU or interface module. Repeat the identification
process.
The PROFIsafe address could not be assigned. The Insert the eCoding plug. Make sure the module is
eCoding plug is not present or some other issue seated correctly. Check the cable connection
occurred. Rack <rack number> Slot <slot number> between the module and the CPU or interface
module and try again.
The PROFIsafe address could not be assigned. The The module’s parameterization in the CPU is cor
F-Address has invalid CRC. Rack <rack number> Slot rupt. Use the TIA Portal and download a new con
<slot number> figuration for this module.
The PROFIsafe address could not be assigned. The The module already has a valid PROFIsafe address
F-Address is already assigned. Rack <rack number> that corresponds to the configuration in the mod
Slot <slot number> ule and the CPU. The SIMATIC Automation Tool
aborted the identification process.
The PROFIsafe address could not be assigned. The Try again. If the error recurs, power cycle the F‑I/O
F-Module did not respond to the SetTimer com module. If still in error, power cycle the CPU or the
mand as expected. Rack <rack number> Slot <slot interface module to which the F‑I/O module is con
number> nected.
The PROFIsafe address could not be assigned. The Make sure the module is seated correctly. Check
F-Module was unreachable. Rack <rack number> the cable connection between the module and the
Slot <slot number> CPU or interface module. Repeat the identification
process.
The PROFIsafe address could not be assigned. The Insert the eCoding plug. Make sure the module is
eCoding plug is not present or some other issue seated correctly. Check the cable connection
occurred. Rack <rack number> Slot <slot number> between the module and the CPU or interface
module and try again.
The PROFIsafe address could not be assigned. The Try again. If the error recurs, power cycle the F‑I/O
F-Module did not respond to the AddrSetValid com module. If still in error, power cycle the CPU or the
mand as expected. Rack <rack number> Slot <slot interface module to which the F‑I/O module is con
number> nected.
The PROFIsafe address could not be assigned. The The module’s parameterization in the CPU is cor
F-Address has invalid CRC. Rack <rack number> Slot rupt. Use the TIA Portal and download a new con
<slot number> figuration for this module.
The PROFIsafe address was assigned successfully. Information only
Rack <rack number> Slot <slot number>
The PROFIsafe address could not be assigned. The Try again. If the error recurs, power cycle the F‑I/O
F-Module did not respond to the AddrSetValid com module. If still in error, power cycle the CPU or the
mand as expected. Rack <rack number> Slot <slot interface module to which the F‑I/O module is con
number> nected.
F-Address Assignment identification process was Information only
aborted by the user. Rack <rack number> Slot <slot
number>
The PROFIsafe address could not be assigned. Rack The SIMATIC Automation Tool could not assign the
<rack number> Slot <slot number> PROFIsafe address. Check the CPU, module, net
work connection, and device configuration.
The PROFIsafe address was assigned successfully. Information only
Rack <rack number> Slot <slot number>
Device-specific messages
Devices can also return device-specific messages. These messages are not in the list above. If
a device-specific message is not self-explanatory, contact your device manufacturer.
Canceling operations
From the Device table, you can perform a device operation on one or many devices. When
the operation is in progress, you can cancel the operation. The SIMATIC Automation Tool
cancels the operation as quickly as possible on devices that have not yet completed the
operation.
Scheduled operations
The SIMATIC Automation Tool ensures that a scheduled operation runs at the date and time
specified. It prevents an operation from running at an unscheduled time.
If you use the Scheduler application to disable a scheduled operation, the
SIMATIC Automation Tool will not enable the disabled operation. You must enable the
operation through the SIMATIC Automation Tool and the Scheduler application.
Refer to Executing scheduled operations (Page 117) for specific information on canceling
running operations in the Scheduler application.
Using passwords
The SIMATIC Automation Tool handles passwords in the following ways:
• If a CPU is protected, the SIMATIC Automation Tool enforces the CPU password
requirements according to the operation and the access level. For protected operations,
you must enter a valid password in the "CPU Password" cell.
• If a CPU password entry is valid, you can hover your mouse cursor over the password field
to display a tool tip that shows the access level.
• The SIMATIC Automation Tool displays a device's password cell in yellow when you enter a
safety password.
Password icons
The SIMATIC Automation Tool provides three password status icons:
Password is valid
Password is invalid
The SIMATIC Automation Tool cannot yet validate the device password in a backup file
When you enter a password, the SIMATIC Automation Tool validates it. When you initiate a
device operation, the access level of the password must be sufficient for that operation. The
Event Log displays a message if you have an insufficient password for an operation.
6. In the SIMATIC Automation Tool, choose the network interface that corresponds to this
network connection. If you are not using a router, select the network interface with
".Auto" in the name. This selection enables the SIMATIC Automation Tool to find all
devices on the network.
NOTE
Communication problems with the SIMATIC Automation Tool
The SIMATIC Automation Tool requires communication to your device network. If S7-PLCSIM
is running, close S7‑PLCSIM and any simulation instances before using the
SIMATIC Automation Tool.
You might also send a device operation to multiple devices, but one device does not
complete the operation. You see a communication error in the Event Log. Other devices,
however, process the device operation as you expect. If you have this problem, follow these
steps:
1. Reduce the number of simultaneous operations that you allow in the Communications
settings (Page 85).
2. Close and restart the SIMATIC Automation Tool.
3. Try the operation again to one or more devices.
If you execute a device operation and the connection to the device has a very slow data
transfer rate, you might get a communication timeout error. If you have this problem,
increase the timeout for communications operations in the Communications settings (Page
85).
See also
Getting started with the SIMATIC Automation Tool (Page 6)
To stay informed about product updates, subscribe to the Siemens Industrial Security RSS
Feed visit (https://www.siemens.com/cert).
D
Data Logs (read or delete), 56
Default pathnames, 82
F Memory reset, 39
Factory defaults, 36 Menu
file, 78
F-address, 124 edit, 79
Fail-Safe CPU support, 100 operations, 81
Filtering table rows, 130 options (general), 84
options (communication), 86
Firmware
options (projects), 87
preloading update files, 45
options (firmware update), 88
update, 48
options (program update), 88
two-step update, 49
options (service data), 89
Firmware update card, 65 options (backup/restore), 89
Format memory card, 40 options (data log), 90
options (event log), 91
options (export), 92
G options (SNMP profiles), 93
Getting started, 6 tools, 96
help, 96
H Mode change, 30
Hotline, 169
N
I Network interface, 167
Icons, toolbar, 97
O
Identify device, 27
Operating mode change, 30
Inserting a device, 20
behind a router, 20 Options, 82
from tables, 23 Options, pathnames for files, 83
IP address Overview, 9
configuration requirement, 13
NAT router, 21
device setting, 32 P
duplicate, 32 Password
.sat project file, 68
K CPU, 166
Pathnames for files, 83
Key shortcuts, 168
PC-based controllers, 19
L PC data, 77
Ping, 20
License types, 110
Preloading firmware update files, 45
R T
Reading Data Logs , 56 Technical support, 169
U
S
Updating a device program, 49
Safe device operations, 165
Safety program, 169
V
SAT project file, 68
Versions of SNMP profiles, 93
SCALANCE devices, SNMP profile configuration, 93
Scan a network, 15
Scheduling operations, 115
Send report, 98
Service and support, 169
Service data, read, 29
Set time, 31
Settings, 82
Settings, pathnames for files, 83
Shortcut keys, 168
Showing device references, 134
Siemens technical support, 169