2 structure of the script file, 3 creating a script file: defining options, Structure of the script file – Lenze EASY Starter(Application Loader) User Manual
Page 6: Creating a script file: defining options, Danger

"Batch" mode: Download applications automatically to target systems
Structure of the script file
6
Lenze · EASY Starter (Application Loader) - "Batch"-Mode · 1.1 EN - 06/2014
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
3.2
Structure of the script file
[3-1]
Example: Script file for controlling three target systems
3.3
Creating a script file: Defining options
A script file defines the actions to be executed while the applications are downloaded
automatically. A script file has the following properties:
• The script file can be created with any ASCII text editor, for example: Microsoft Editor.
• The script file is divided into different sections where options for processing the script file can
be defined.
• The start of a section is marked by squared brackets. Within a section, the respective keys are
given.
• Each key consists of the key name, followed by an equal sign and the key value.
• Thus, the file structure corresponds to a typical Windows INI file.
• Only one key may be given per line.
• Optionally, you can add a comment which has to be marked by a preceding semicolon.
Example:
[COMMUNICATION]
Baud rate=500 ; setting is optional
[COMMON]
NumberOfDevices=3
ShowProcessing=1 ; 1 = displays progress window
ExitAfterDownload=0 ; 0 = Application loader will be closed after download
[DEVICE001]
NodeAddress=Lenze OPC Ethernet Server.1
IP=172_31_201_79
ApplicationFileSet="D:\Data\9400.lfl"
StartAfterDownload=1 ; 1 = PLC program will start after download
[DEVICE002]
NodeAddress=Lenze OPC Systembus Server.1
SDO=0;
ApplicationFileSet="D:\Data\8400.lfl"
StartAfterDownload=1
[DEVICE003]
NodeAddress=Lenze OPC Diagnostics Server.00001962
ParameterSetFile="D:\Data\8400 TopLine C_00001962_8400 TopLine C~1.gdc"
StartAfterDownload=1
ShowProcessing=1 ; displays progress window
Danger!
The StartAfterDownload=1 option in a system with several axes causes each axis to start
automatically after the application has been downloaded!
• Use the setting StartAfterDownload=0 in order to avoid a dangerous situation!