>Global Drive Loader as of version 3. No part of this documentation may be copied or made available to third parties without the explicit written approval of Lenze Drive systems GmbH.">>Global Drive Loader as of version 3. No part of this documentation may be copied or made available to third parties without the explicit written approval of Lenze Drive systems GmbH.">
Nothing Special   »   [go: up one dir, main page]

SW GDLoader GettingStarted v3-0 en

Download as pdf or txt
Download as pdf or txt
You are on page 1of 41

L

Software Manual
Global Drive Loader
2 DMS-Version 3.0 - 02/2005 - TD05/TD11 L
This Manual is valid for the Global Drive Loader as of version 3.0
Copyright
2005 Lenze Drive Systems GmbH. All rights reserved.
Imprint
Lenze Drive Systems GmbH
Postfach 10 13 52, D-31763 Hameln, Germany
Phone: ++49 (0)5154 / 82-0
Fax: ++49 (0)5154 / 82-2111
E-mail: Lenze@Lenze.de
Copyright information
All texts, photos and graphics contained in this documentation are subject to
copyright protection. No part of this documentation may be copied or made
available to third parties without the explicit written approval of Lenze Drive
Systems GmbH.
Liability
All information given in this documentation has been selected carefully and
tested for compliance with the described hardware and software.
Nevertheless, discrepancies cannot be ruled out. We do not accept any
responsibility or liability for any damage that may occur. Required corrections
will be included in updates of this documentation.
Trademarks
Microsoft, Windows and Windows NT are either registered trademarks or
trademarks of Microsoft Corporation in the U.S.A. and/or other countries.
Adobe and Reader are either registered trademarks or trademarks of Adobe
Systems Incorporated in the U.S.A. and/or other countries.
All other product names contained in this documentation are trademarks of
the corresponding owners.
Global Drive Loader
Contents
L 3.0 EN 3
Contents
1 About this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1 Conventions used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2 Layout of the safety information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2 System requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.1 Supported target systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2 Connection with the target system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3 Software installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4 User interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.1 Language selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
4.2 Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4.3 Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.4 Function area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.5 Dialog area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.6 Status bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
5 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.1 How to configure the communication settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.1.1 Example: Configuring a point-to-point connection via LECOM. . . . . . . . . . . . . . 15
5.2 How to select a target system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
5.3 How to build up a connection with the target system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.4 How to select files for the download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
5.4.1 How to open a DDS binary file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
5.4.2 How to open application data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.4.3 How to open a GDC parameter set file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.5 How to download data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.5.1 Parameter set transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.6 How to end the connection with the target system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5.7 How to exit Global Drive Loader. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
6 Control via script files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.1 Script files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.2 Example for a script file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
6.3 Syntax of the command line call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
6.4 Batch mode commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Global Drive Loader
Contents
4 3.0 EN L
7 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
7.1 Error numbers, causes & remedies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
7.2 Log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
7.3 File headers for application data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
8 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Your opinion is important to us. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
L 3.0 EN 5
Global Drive Loader
About this Manual
Conventions used
1 About this Manual
This Manual contains information about the Global Drive Loader.
The Global Drive Loader is a software to transfer PLC programs, parameter sets and
application data from a PC to Lenze target systems.
Special features of the Global Drive Loader:
> Intuitive program operation via an easy-to-use PC user interface.
> Program control by means of script files for automated downloads to several target
systems without the necessity of additional inputs.
> Download of DDS binary files, application data (e.g. *.lc9 files created with Cam
Designer or *.lc7 files created with GDC) and GDC parameter set files via the system bus
(CAN).
> Recording of all important events.
1.1 Conventions used
This Manual uses the following conventions to distinguish between different types of
information:
Type of information Writing Examples/notes
Variable identifier italics Set bEnable to TRUE to...
Window pane The message window... / The Options dialog box...
Control element bold The OK button... / The Copy command... / The Properties tab... / The
Name input field...
Sequence of
menu commands
If several commands must be used in sequence to carry out a function,
then the individual commands are separated by an arrow: Select
FileOpen to...
Keyboard command <bold> Press <F1> to open the Online Help.
If a command requires a combination of keys, a "+" is placed between
the key symbols:
With <Shift>+<ESC> you can...
Program listings Cour i er
IF var 1 < var 2 THEN
a = a + 1
END IF
Keyword Courier
bold
Hyperlink underline Hyperinks are highlighted references which are activated by means of a
mouse click.
Step-by-step
instructions

Step-by-step instructions are indicated by a pictograph.
Global Drive Loader
About this Manual
Layout of the safety information
6 3.0 EN L
1.2 Layout of the safety information
The following pictographs and signal words are used in this documentation to indicate
dangers and important information:
Safety information
Layout of the safety information:
Application notes
@Pictograph and signal word!
(characterise the type and severity of danger)
Note
(describes the danger and suggests how to avoid the danger)
Pictograph Signal word Meaning
@
Danger! Danger of personal injury through dangerous electrical voltage
Indicates an impending danger that may lead to death or severe personal injury if
the corresponding measures are not taken.
@
Danger! Danger of personal injury through a general source of danger
Indicates an impending danger that may lead to death or severe personal injury if
the corresponding measures are not taken.
_
Stop! Danger of material damage
Indicates a potential danger that may lead to material damage if the corresponding
measures are not taken.
Pictograph Signal word Meaning
@
Note! Important note for trouble-free operation

Tip! Useful tip for easy handling


L 3.0 EN 7
Global Drive Loader
System requirements
Supported target systems
2 System requirements
The following minimum requirements on hardware and software must be met in order to
use the Global Drive Loader:
> Microsoft Windows 98/Me, Windows NT 4.0 (as of Service Pack 5),
Windows 2000 (as of Service Pack 2) or Windows XP
> Microsoft Internet Explorer as of version 5.0
> IBM compatible PC with Intel Pentium-333 processor
> 128 MB RAM
> 60 MB free hard disk capacity
> Pointer device (mouse, track ball, etc.)
> Free interfaces according to the requirements of the fieldbus connection module used.
2.1 Supported target systems
The Global Drive Loader supports the following target systems:
Target system as of version
8200 motec/vector 1.4
9300 hoist 0.4
9300 Servo PLC 0.2
9300 Servo cam profiler 1.0
9300 Servo positioning controller 1.0
9300 Servo register controller 1.0
9300 Servo inverter 1.0
9300 vector 1.0
9374 Terminal extension 1.0
9391 Drive PLC 0.4
ECS Axis controller 1.3
ECS Supply module 1.2
EthernetCAN 2180 1.0
I/O system 1.0
ModemCAN 2181 1.0
starttec 1.0
Global Drive Loader
System requirements
Connection with the target system
8 3.0 EN L
2.2 Connection with the target system
The communication with the target system (controller, Drive PLC, etc.) requires a fieldbus-
specific interface module for the PC and the corresponding fieldbus modules for the target
systems to be connected.
> For system bus (CAN) communication, Lenze offers the following components as
interface module for the PC:
Communication accessories PC port
PC system bus adapter 2173
incl. connection cable and voltage supply adapter
for DIN keyboard connection (EMF2173IB)
for PS/2 keyboard connection (EMF2173IBV002)
for PS/2 keyboard connection with electrical isolation (EMF2173IBV003)
Parallel port
(LPT port)
PC system bus adapter 2177
incl. connection cable (EMF2177IB)
USB
(Universal Serial Bus)
@ Note!
Detailed information on the PC system bus adapter can be found in the "CAN
Communication Manual".
Please note the documentation for the PC system bus adapter!
L 3.0 EN 9
Global Drive Loader
Software installation
3 Software installation
Double-click the file "GDLoader.exe" in Windows Explorer and follow the
instructions of the installation program to install the Global Drive Loader on your
computer!
@ Note!
With Windows NT/2000/XP the installation requires administrator rights!
Global Drive Loader
User interface
Language selection
10 3.0 EN L
4 User interface
Select
ProgramsLenzeGlobal Drive Loader - 3.0Global Drive Loader
from the start menu to start the Global Drive Loader with user interface.
The user interface contains the following control and function elements:
Tip!
The Global Drive Loader can also be script-controlled to automatically download
data to several target systems without the necessity of additional inputs. For more
information, please see the chapter "Control via script files". (L 27)
4.1 Language selection
It is possible to change the language for the menu, dialog and help texts of the user
interface.
> You can choose between German, English and French.
For changing to another language, select Options Language and choose the
desired language.
A Menu bar Toolbar Function area Dialog area 1 Status bar
L 3.0 EN 11
Global Drive Loader
User interface
Menu bar
4.2 Menu bar
The menu bar is used to access the menu commands for the Global Drive Loader.
> A click on an item of the main menu opens the corresponding menu and lists the menu
items contained in it.
> Click a menu item to execute the corresponding function.
Menu items which are displayed in light gray are currently deactivated because the
execution of the corresponding function would not make any sense in the current
program state.
"Options" menu
The Options menu provides commands for the configuration of Global Drive Loader:
"Online" menu
The Online menu provides commands which can only be activated when the Global Drive
Loader is in online mode:
Command Function
System bus configurator... Starts the Lenze system bus configuration tool
Use the system bus configuration tool to easily configure the communication
parameters of the Lenze PC system bus adapters connected to your PC.
For safety reasons, all Global Drive Loader functions/menu commands are
deactivated while the system bus configuration tool is running.
For detailed information on the system bus configuration tool, please see the
Online Help for the system bus configuration tool.
LECOM configurator... Starts the Lenze LECOM configuration tool
For safety reasons, all Global Drive Loader functions/menu commands are
deactivated while the LECOM configuration tool is running.
For detailed information on the LECOM configuration tool, please see the
DriveServer documentation.
DriveServer configurator... Starts the Lenze DriveServer configuration tool
For safety reasons, all Global Drive Loader functions/menu commands are
deactivated while the DriveServer configuration tool is running.
For detailed information on the DriveServer configuration tool, please see the
DriveServer documentation.
Safety check activation A safety check is made before every action.
If this option is activated, a tick appears next to the menu command.
Activation of all notes Repeated note display can be stopped by activating the control box Do not display
this note again in the note dialog box.
Use the command Activation of all notes to reset all settings made, i.e. all notes will
be displayed again.
Language Selection of the language for the user interface.
Command Function
PLC start Starts the PLC program in the PLC
Only with controllers with PLC functionality
(e.g. 9300 Servo PLC, Drive PLC).
PLC stop Stops the PLC program in the PLC
Only with controllers with PLC functionality
(e.g. 9300 Servo PLC, Drive PLC).
Global Drive Loader
User interface
Toolbar
12 3.0 EN L
"?" menu
The ? menu provides commands for the activation of the Online Help and the display of
program information:
4.3 Toolbar
Via the icons of the toolbar you can directly execute some of the most frequently used
menu commands without making a detour via the Menu bar.
> Simply click an icon to activate the corresponding command.
Tip!
If you position the mouse pointer for a short time over an icon, a "tool tip" will be
indicated with information about the corresponding function.
4.4 Function area
The function area shows all presently available functions in form of symbols. The functions
can be activated by a double-click.
4.5 Dialog area
The dialog area displays input dialogs, buttons and text fields with additional information
about the active function.
4.6 Status bar
The status bar indicates the communication status (online/offline), controller address and
PLC program status.
Command Function
Help topics Opens the Online Help for the Global Drive Loader
About... Displays information about the Global Drive Loader (e.g. version and copyright)
Icon Function
Starts the PLC program
Stops the PLC program
Displays help topics
L 3.0 EN 13
Global Drive Loader
Operation
How to configure the communication settings
5 Operation
5.1 How to configure the communication settings
The Lenze DriveServer and the OPC bus server for the corresponding fieldbus are used to
build up the connection with the target system.
DriveServer
Use the DriveServer configuration tool to configure the DriveServer. With Global Drive
Loader, the configuration tool can be activated via the menu commands
OptionsDriveServer configurator....
Tip!
For detailed information on the DriveServer, please see the DriveServer
documentation.
OPC bus server for system bus (CAN)
Use the system bus configuration tool to configure the communication settings for the
system bus (CAN). With Global Drive Loader, the configuration tool can be activated via
the menu commands OptionsSystem bus configurator....
Tip!
Using the diagnostics function of the system bus configuration tool, you can check
if the PC system bus adapter is working properly.
For detailed information on the system bus configuration tool, please see the CAN
Communication Manual and the Online Help for the system bus configuration
tool.
@ Note!
For the configuration of the communication settings, the DriveServer must be
closed.
The DriveServer is default set to the OPC bus server for system bus (CAN).
If you want to use a different OPC bus server for communication, use the
DriveServer configuration tool to add the bus server to the DriveServer.
Global Drive Loader
Operation
How to configure the communication settings
14 3.0 EN L
OPC bus server for LECOM
Instead of the system bus (CAN), you can also use LECOM to communicate with the target
system. Use the LECOM configuration tool to configure the corresponding communication
settings. With Global Drive Loader, the configuration tool can be activated via the menu
commands OptionsLECOM configurator....
Example: Configuring a point-to-point connection via LECOM (L 15)
Tip!
Use the default configuration file "Default_COM1.lccfg" of the LECOM
configuration tool for communication via the serial interface COM1.
For detailed information on the LECOM configuration tool, please see the
DriveServer documentation.
Use of other OPC bus servers
For communication with the target system, you can also install other bus servers for the
DriveServer. For detailed information, please see the DriveServer documentation.
@ Note!
LECOM does not support the parameter set transfer variant "Replacement unit".
@ Note!
Please note that some fieldbuses or OPC bus servers do not support all download
options. Programs and *.lc9 files can, for instance, only be downloaded with the
Lenze OPC system bus bus server or other CANopen bus servers.
L 3.0 EN 15
Global Drive Loader
Operation
How to configure the communication settings
5.1.1 Example: Configuring a point-to-point connection via LECOM
How to configure a point-to-point connection via LECOM:
1. Select ProgramsLenzeGlobal Drive Loader - 3.0Global Drive Loader from the
start menu to start the Global Drive Loader.
In the Global Drive Loader:
2. Select the commands OptionsDriveServer configurator to open the DriveServer
configuration tool.
In the DriveServer configuration tool:
3. Select FileConnect to to build up a connection with the selected DriveServer.
Wait until the Please wait dialog disappears and the connection has been built
up.
4. Select the commands ConfigurationBus server to open the Bus server
configuration dialog box.
The right list field lists all bus servers which have been assigned to the
DriveServer.
To remove an assignment, select the corresponding bus server from the right
list field and click the Delete button.
5. Click Refresh to list all bus servers available on the PC in the left list field.
6. For LECOM, select "Lenze OPC Lecom Server" from the left list field and click Add to
assign the bus server to the DriveServer.
If necessary, repeat the above steps to assign further bus servers to the
DriveServer.
7. Click OK to accept the settings and close the Bus server configuration dialog box.
The bus servers assigned to the DriveServer will be listed in the name area under
the online element.
8. Select FileDisconnect to end the connection with the DriveServer.
9. Select FileExit to exit the DriveServer configuration tool.
Global Drive Loader
Operation
How to configure the communication settings
16 3.0 EN L
In the Global Drive Loader:
10. Select the commands OptionsLECOM configurator to open the LECOM
configuration tool.
In the LECOM configuration tool:
11. Click OK to confirm the Lenze OPC Server LECOM info dialog box.
The configuration saved last will be loaded automatically.
12. Select the configuration entry for the interface (COMx) from the tree/list on the
left.
Check the interface settings in the Communication Port tab (particularly, COM
number and baud rate) and adjust the settings, if necessary.
For a point-to-point connection via LECOM, mark the Scan at the servers start
option with a tick.
13. Select FileSave to save the configuration.
14. Select FileExit to exit the LECOM configuration tool.
The configuration is now complete and you can start searching for connected
devices in the Global Drive Loader.
L 3.0 EN 17
Global Drive Loader
Operation
How to select a target system
5.2 How to select a target system
For selecting a target system, it is possible to automatically find the controllers connected
to the bus system.
Proceed as follows:
1. Click Device find to find the controllers connected to the bus system.
The progress of scanning will be indicated in a bar diagram.
At the end of scanning, the Select target system dialog box will appear:
2. Select the desired target system from the tree.
3. Click OK to confirm your selection.
The selection is accepted and the dialog box closed.
The selected target system is listed in the dialog area:
Next steps:
How to build up a connection with the target system (L 18)
Global Drive Loader
Operation
How to build up a connection with the target system
18 3.0 EN L
5.3 How to build up a connection with the target system
Click Log in in the function area to create a connection with the selected target
system.
> If the connection could be built up successfully, the Global Drive Loader changes from
offline to online mode and the status bar indicates the communication status "Online",
controller address and PLC program status.
> If question marks (???) appear in the dialog area after log in, the target system is not
supported by the Global Drive Loader.
> If it is not possible to build up a connection, an error message and an error number will
be displayed. A list of all error numbers and their meaning can be found in the
appendix. Error numbers, causes & remedies (L 33)
Next steps:
How to select files for the download (L 19)
L 3.0 EN 19
Global Drive Loader
Operation
How to select files for the download
5.4 How to select files for the download
After you have created a connection with the target system and Global Drive Loader is in
online mode, you can select the files to be downloaded to the target system.
A difference is made between
> DDS binary files created with the Drive PLC Developer Studio.
> Application data created with Cam Designer.
> GDC parameter set files created with Global Drive Control.
After opening a file, click Download... to download the file to the target system or
(depending on the target system) open further files to be downloaded and download them
one after another to the target system by clicking Download....
> Detailed information about the download can be found in the chapter "How to
download data". (L 23)
@ Note!
The target system determines which files can be selected (opened) for the
download in Global Drive Loader.
A DDS binary file can only be opened if the target system has PLC
functionality (e.g. 9300 Servo PLC).
Global Drive Loader
Operation
How to select files for the download
20 3.0 EN L
5.4.1 How to open a DDS binary file
If the target system has PLC functionality (e.g. 9300 Servo PLC and Drive PLC), this function
can be used to open a DDS binary file for the download.
> All binary formats as of Drive PLC Developer Studio (DDS) version 1.0 are supported.
How to open a DDS binary file...
1. Select DDS binary file... in the function area.
2. Select the desired file in the Open DDS binary file dialog box.
3. Click OK to confirm your selection.
The selection is accepted and the dialog box closed.
> If the binary file could be opened properly,
the Close DDS binary file... function will be available instead of the DDS binary file
function. Use this function to close the binary file.
the Download... function will be provided to download the file(s) to the target
system.
the dialog area will display information about the binary file in the Binary file tab.
> If it is not possible to open the binary file properly, an error message and an error
number will be displayed. Error numbers, causes & remedies (L 33)
Next steps:
How to open application data (L 21) / How to open a GDC parameter set file (L 22)
or
How to download data (L 23)
L 3.0 EN 21
Global Drive Loader
Operation
How to select files for the download
5.4.2 How to open application data
If the target system supports the download of application data, click Application data... to
open an application data file for the download.
> After this, you can download *.lc9 files containing motion profiles & cam data created
with Cam Designer or *.lc7 files created with GDC to the target system.
> Apart from *.lc9/*.lc7 files, you can open any other files for the download, provided that
they have the file header specified by Lenze.
Detailed information about the file headers can be found in the Manual for the
9300 Servo PLC (6.x), chapter "Appendix / Memory / Download of any data".
How to open an application data file...
1. Select Application data... in the function area.
2. Select the desired file in the Open application data dialog box.
3. Click OK to confirm your selection.
The selection is accepted and the dialog box closed.
> If the application data could be opened properly,
the Close application data... function will be available instead of the Application
data function. Use this function to close the application data.
the Download... function will be provided to download the file(s) to the target
system.
the dialog area will display information about the application data in the Application
data tab.
> If it is not possible to open the application data properly, an error message and an error
number will be displayed.Error numbers, causes & remedies (L 33)
Next steps:
How to open a DDS binary file (L 20) / How to open a GDC parameter set file (L 22)
or
How to download data (L 23)
Global Drive Loader
Operation
How to select files for the download
22 3.0 EN L
5.4.3 How to open a GDC parameter set file
Click GDC parameter set file... to open a parameter set file created with Global Drive
Control (GDC) for the download.
How to open a GDC parameter set file...
1. Select the GDC parameter set file... function in the function area.
2. Select the desired file in the Open GDC parameter set file dialog box.
3. Click OK to confirm your selection.
The selection is accepted and the dialog box closed.
> If the parameter set file could be opened properly,
the Close GDC parameter set file... function will be available instead of the GDC
parameter set file... function. Use this function to close the parameter set file.
the Download... function will be provided to download the file(s) to the target
system.
the dialog area will display information about the parameter set file in the
Parameter set file tab.
> If it is not possible to open the parameter set file properly, an error message and an
error number will be displayed.Error numbers, causes & remedies (L 33)
Next steps:
How to open a DDS binary file (L 20) / How to open application data (L 21)
or
How to download data (L 23)
L 3.0 EN 23
Global Drive Loader
Operation
How to download data
5.5 How to download data
As long as at least one file has been opened for the download, the Download... function will
be available in online mode. Use this function to download the selected file(s).
Download sequence
Please observe the following download sequence:
1. DDS binary files will always be downloaded first.
2. Application data will be downloaded next.
3. GDC parameter set files will be downloaded last.
Before downloading a file
The results of the safety checks carried out before a download are listed in a log in the
dialog area.
> The download can only be carried out if all safety checks have been passed successfully.
> If one of the safety checks is not passed, an error number will be displayed in the log.
> Before the download of DDS binary files and application data, it is checked whether the
data in the target system are newer than or identical with the data to be downloaded.
If necessary, a corresponding message will be indicated and you can select if the
download shall be continued or stopped.
> Parameter sets can be transferred in two different ways.
Parameter set transfer (L 25)
During the download
The name of the file being downloaded is displayed in the status bar. The progress of the
download is indicated in form of a bar.
> If an error occurs during the download, an error message and error number will be
displayed.Error numbers, causes & remedies (L 33)
@ Note!
After selecting the Download... function, Global Drive Loader changes from
online mode to the so-called download mode. For safety reasons, the program
cannot be closed in download mode.
Please note that the controller must be inhibited in the target system for the
download and that the PLC program must be stopped with target systems with
PLC functionality. If this is not the case, a corresponding message will be
indicated.
Global Drive Loader
Operation
How to download data
24 3.0 EN L
After the download
After the download of a DDS binary file, a dialog box appears in which you are asked if the
PLC program is to be started in the target system.
> If the Always start the PLC program checkbox is activated, the PLC program will always
be started after a download and the query will no longer be displayed. The option can
be reset via the menu commands OptionsActivation of all notes.
The number of transferred bytes and parameters and the check test results are listed in a
log.
> Press Next >> to download the next file or Cancel to stop the download process and
change back to the online mode.
After all downloads have been completed successfully, click Main menu>> to change from
download mode to online mode.
After a faulty download
The number of transferred bytes and parameters and an error number are listed in a
log.Error numbers, causes & remedies (L 33)
> Click Main menu >> to change from download mode to online mode and close the
program or start a new download.
@ Note!
Please note that the data transferred to the target system will be invalid if the
download could not have been completed successfully!
L 3.0 EN 25
Global Drive Loader
Operation
How to download data
5.5.1 Parameter set transfer
The function area provides the following functions for the download of GDC parameter set
files:
Assignment of controller descriptions
The GDC parameter set file includes the codes to be transferred with the corresponding
initialisation values. The parameter set transfer however requires additional information
about the code type. These information are generated from the corresponding controller
description.
The Global Drive Loader tries to assign these controller descriptions automatically by
searching the directory which has been the source for the parameter set file for the
corresponding controller description.
> If a directory does not include the corresponding controller description, the search will
be continued in the directories configured via the DriveServer menu commands
ConfigurationPDB path....
Command Function
Duplication of parameter set The following codes of the parameter set are not transferred to the target system:
C0009 - AIF controller address
C0125 - AIF baud rate
C0058 - Rotor position
All codes not transferred to the target system are listed in a note dialog before the
parameter set transfer starts.
Replacement unit Code C0009, C0125 and C0058 are also transferred to the target system.
Note: LECOM does not support the "Replacement unit" function!
Global Drive Loader
Operation
How to end the connection with the target system
26 3.0 EN L
5.6 How to end the connection with the target system
After you have logged in and changed from offline to online mode, the Log out function
will be indicated instead of the Log in function. Use this function to end the online
connection with the target system.
After you have logged out, Global Drive Loader will be in offline mode again and you can
build up a connection with another target system.
5.7 How to exit Global Drive Loader
Click Exit to exit the Global Drive Loader.
@ Note!
For safety reasons, the Global Drive Loader cannot be exited while downloading
data to the target system!
L 3.0 EN 27
Global Drive Loader
Control via script files
Script files
6 Control via script files
Data can be automatically downloaded to several target systems if the Global Drive
Loader has been started in the so-called batch mode.
> The batch mode processes a script without the need of additional user data input.
> All Global Drive Loader activities including possibly occurring error messages are
listed in a log file.
6.1 Script files
Automatic processing is only possible with a script file which determines the actions to be
carried out.
Script files can be created with any ASCII text editor (e.g. Notepad). A script file is divided
into sections. Different keys can be entered for the sections. Therefore they are very similar
to typical Windows INI files.
> Sections are put into square brackets. The following lines list the keys for a specific
section.
> A key consists of a key name followed by an equal sign and a key value.
Comments can be added, the comment must however be separated from the key
value by a semicolon.
It is not possible to enter more than one key per line.
Example:
@ Note!
Please note the following special features in batch mode:
"Notes" and "information" messages are not displayed.
The target system inhibits the controller automatically!
A PLC program running on the target system is stopped automatically!
ShowPr ocessi ng=1; di spl ays pr ogr ess wi ndow
@Warning!
If the machine includes several axes, every axis is started directly after download
if StartAfterDownload = 1 is set. This can lead to dangerous situations!
Global Drive Loader
Control via script files
Script files
28 3.0 EN L
Tip!
The script is not tested for correctness before it is being processed, i.e. script
processing does not stop before an error occurs. The error can be analysed and
eliminated using the log file.
Communication settings - [COMMUNICATION] section
General settings - [COMMON] section
Target system-dependent settings - [DEVICE...] sections
Every target system must have a [DEVICE???] section. The question marks must be replaced
by a serial number (001 ... NumberOfDevices).
> If you have defined the key NumberOfDevices=3 in the [COMMON] section, the
following three sections must be available:
[DEVICE001], [DEVICE002], [DEVICE003].
> The target systems are processed subsequently, starting with [DEVICE001].
The following settings can be made for every section:
Key Parameter
Baudrate Baud rate of system bus in kBaud.
The baud rate selection in the script is optional.
If the baud rate is not defined in the script, the value set in the system bus
configuration tool will be used.
Key Parameter
NumberOfDevices Number of target systems to be programmed (max. 63).
ShowProcessing Status window display:
0 = Status window not displayed (standard setting).
1 = Status window displayed.
MaxNumberOfErrors The latest version no longer supports this entry and ignores it, if necessary (e.g. in older
script files).
ExitAfterDownload Automatic stop of Global Drive Loader after the script has been processed:
0 = Global Drive Loader does not stop after processing is completed (standard
setting).
1 = Global Drive Loader stops after processing is completed.
Key Parameter
NodeAddress Node address of the target system.
Examples:
"Lenze OPC Systembus Server.11" (with CAN node address "11"; only for
communication via system bus; check also key "SDO")
"Lenze OPC Lecom Server.1-5" (with LECOM node address "5")
Node address is shown in dialog area in the field Busserver.
SDO Parameter channel (1 or 2) for communication.
Only required for system bus (CAN) communication.
For a better performance, select the same parameter channel for all devices in the
script file.
L 3.0 EN 29
Global Drive Loader
Control via script files
Script files
BinFile Path and file name of the DDS binary file for the download.
Not indicated for target systems without PLC functionality.
File indication is optional (only indicated files will be transferred to the target
system).
AddDataFile Path and file name of the application data for the download.
Not indicated for target systems which do not support the download of
application data.
File indication is optional (only indicated files will be transferred to the target
system).
ParameterSetFile Path and file name of the GDC parameter set file for the download.
File indication is optional (only indicated files will be transferred to the target
system).
DuplicateParameterSet Determines whether a parameter set is to be duplicated or whether the target
system is a replacement unit:
0 = Target system is a replacement unit (standard setting).
1 = Parameter set is duplicated.
Note: LECOM does not support the "Replacement unit" function!
StartAfterDownload Determines whether the PLC program is to be started after download and parameter
set transfer have been completed:
0 = PLC program not started (standard setting).
1 = PLC program started.
Key Parameter
Global Drive Loader
Control via script files
Example for a script file
30 3.0 EN L
6.2 Example for a script file
The following example shows a script file for two target systems:
[ COMMUNI CATI ON]
Baudr at e=500 ; opt i onal set t i ng

[ COMMON]
Number Of Devi ces=2

ShowPr ocessi ng=1 ; 0 = no pr ogr ess wi ndow
; 1 = di spl ays pr ogr ess wi ndow

Exi t Af t er Downl oad=0 ; 0 = Gl obal Dr i ve Loader
; wi l l not exi t
; 1 = Gl obal Dr i ve Loader
; wi l l exi t af t er j ob i s done

[ DEVI CE001]
NodeAddr ess=Lenze OPC Syst embus Ser ver . 6
SDO=1
Bi nFi l e=D: \ Pr oj ect s\ Ser voPLC10. BI N
AddDat aFi l e=D: \ Pr oj ect s\ CamDat a10. l c9
Par amet er Set Fi l e=D: \ Pr oj ect s\ Par Set 10. GDC

Dupl i cat ePar amet er Set =0 ; 0 = t o r epl ace a devi ce
; 1 = t o dupl i cat e a devi ce

St ar t Af t er Downl oad=1 ; 0 = pl c pr ogr amwi l l not st ar t
; 1 = pl c pr ogr amwi l l st ar t
; af t er downl oad

[ DEVI CE002]
NodeAddr ess=Lenze OPC LecomSer ver . 1- 1
Bi nFi l e= ; no pr ogr amt r ansf er
AddDat aFi l e=
Par amet er Set Fi l e=D: \ Pr oj ect s\ Par Set 14. GDC
Dupl i cat ePar amet er Set =1
St ar t Af t er Downl oad=0
L 3.0 EN 31
Global Drive Loader
Control via script files
Syntax of the command line call
6.3 Syntax of the command line call
Use the following syntax to start Global Drive Loader in batch mode:
> The /batch parameter determines that all program functions will be script-controlled.
> The script file parameter indicates the script file to be used.
It is possible to use absolute and relative path names. A relative path always refers
to the current directory.
> The log file parameter is optional. It contains the name of the log file in which all
activities and possibly occurring error messages are recorded. Log files (L 37)
If you do not enter a path for the log file, the log file will be saved in the same
directory as the script file.
If you skip the log file parameter, Global Drive Loader does not create a log file.
Example:
GDLoader . exe / bat ch scr i pt f i l e [ l og f i l e]
GDLoader . exe / bat ch MyScr i pt . cmd MyLogf i l e. t xt
Global Drive Loader
Control via script files
Batch mode commands
32 3.0 EN L
6.4 Batch mode commands
After Global Drive Loader has been started in batch mode, the task bar displays the
following symbol :
> Right-click the symbol to open a pop-up menu which provides the following
commands:
Tip!
If you position the mouse pointer over the symbol in the task bar, you will get
information about the program status (application name, currently processed
target system, number of errors, name of the file currently transferred) in form
of a tool tip.
The icon in the task bar is animated as long as data are downloaded.
Menu command Function
Indicate processing Window providing information about the progress of script processing.
The status window corresponds to the log file except for the Id" column.
Activated options are marked with a tick in front of the menu command.
About... Information about the Global Drive Loader (e.g. version and copyright).
Close application Close Global Drive Loader.
This command is not available in download mode.
Cancel Stop download.
This command is only available in download mode.
L 3.0 EN 33
Global Drive Loader
Appendix
Error numbers, causes & remedies
7 Appendix
7.1 Error numbers, causes & remedies
Error number Cause Remedy
0001h ...
BFFFh
Information about the error numbers can be found in the Online Help for the system bus
configuration tool.
C000h Error during opening or closing a file. Close the program and restart it. If the
problem cannot be eliminated, check path
and name of the file which creates the error.
C001h Internal program error (invalid handling). Restart the program. if the problem cannot
be eliminated, contact the Lenze Hotline.
C100h An error occurred during reading the GDC
parameter set file.
Try to reload the file. If the problem cannot
be eliminated, the parameter set file is not
valid. Create a new file with GDC.
Faulty GDC parameter set file:
C101h Error in section "ParamSet". Create a new GDC parameter set file with
GDC.
C102h Section "ParamSet" missing.
C103h UserInfo cannot be read.
C104h PDB-ID cannot be read.
C105h Target system name cannot be read.
C106h Variable version cannot be read.
C200h A code indicated in the parameter set file
could not be found in the controller
description.
If the controller description has been
manually assigned, ensure that the
controller description matches the
parameter set file.
Faulty GDC controller description:
C201h Error in section "DefaultParamTypes". If the controller description has been created
with DDS, create the file again. If the problem
cannot be eliminated, contact the Lenze
Hotline.
C202h Section "ParamSet" missing.
C203h PDB cannot be read.
C204h PDB-ID cannot be read.
C205h Name of ParamSet cannot be read.
C206h SWID_B cannot be read.
C207h Name of ParamSet is unknown.
Global Drive Loader
Appendix
Error numbers, causes & remedies
34 3.0 EN L
C300h Error during download of DDS binary file. Restart the download.
If the problem cannot be eliminated, contact
the Lenze Hotline.
C301h The target system connected to the bus is not
the same as the target system for which the
DDS binary file has been created.
Check the controller address or select a
different DDS binary file.
C302h The project in the target system is a later
version than the project to be loaded.
C303h The download of the DDS binary file has been
cancelled.
Restart the download.
If the problem cannot be eliminated, contact
the Lenze Hotline.
C304h Internal program error
PLC program buffer cannot be created.)
Restart the program.
If the problem cannot be eliminated, contact
the Lenze Hotline.
C400h The controller description assigned to the
GDC parameter set file cannot be found.
Check the settings of the GDC find path in
the initialisation file (key "SearchPathPDB").
If the problem cannot be eliminated, contact
the person who created the GDC parameter
set file.
C401h Internal program error
(transfer list not created yet).
Restart the program.
If the problem cannot be eliminated, contact
the Lenze Hotline.
C402h The max. permissible number of errors
during a parameter transfer has been
exceeded.
Restart the parameter transfer.
If necessary, increase the number of
permissible errors in the initialisation file
(key "MaxTransferErrors").
C403h The preparations for the parameter transfer
have not been successful.
Restart the program.
If the problem cannot be eliminated, contact
the Lenze Hotline.
C404h The controller description does not match
the target system connected to the bus.
Check the controller address. If the controller
description has been manually loaded, select
a different controller description. If the error
cannot be eliminated, select a different GDC
parameter set file.
C405h Internal program error
(transfer list cannot be created).
Restart the program.
If the problem cannot be eliminated, contact
the Lenze Hotline.
C406h The file "pdb.ini" cannot be read. Check whether the file "pdb.ini" is included in
the program schedule of the Global Drive
Loader. If not, re-install the Global Drive
Loader.
C407h The GDC parameter set file was created for a
newer controller version than connected to
the bus.
Create a new GDC parameter set file for the
controller version connected to the bus.
C500h Faulty script file (communication parameters
cannot be read).
Check the script file, especially the
[Communication] section.
C501h Error during creation of a log file. Check the log file name entered in the
command line and try again.
C502h Error during opening a script file. Check the script file name entered in the
command line and try again.
C503h Error during opening a DDS binary file. Check the target system name in the log file
which created the error (e.g. "DEVICE001")
and check the script file.
C504h Error during opening a GDC parameter set
file.
C600h No connection with the target system. Check the wiring between PC and target
system.
Restart the program.
C601h The target system cannot be identified. Please contact the Lenze Hotline.
Error number Cause Remedy
L 3.0 EN 35
Global Drive Loader
Appendix
Error numbers, causes & remedies
C602h Error during identification of the FIF.
(product code cannot be read.)
Check the communication parameters.
If the problem cannot be eliminated, contact
the Lenze Hotline.
C603h Error during identification of the FIF.
(ID cannot be read.)
C604h Error during copying application data. Check the target system name in the log file
which created the error (e.g. "DEVICE001")
and check the script file.
C605h Application data in file and target system are
identical.
Status message, no remedy required.
C606h Application data cannot be transferred. Restart the download.
If the problem cannot be eliminated, contact
the Lenze Hotline.
C607h Error during opening application data. Check the target system name in the log file
which created the error (e.g. "DEVICE001")
and check the script file.
C608h No target system selected. Check whether a target system has been
selected.
C60Ah Internal program error: OPC item cannot be
created.
Restart Global Drive Loader.
If necessary, restart PC.
C60Bh Internal program error: OPC item cannot be
read
Restart Global Drive Loader.
Check whether the target system can be
addressed.
C60Ch Internal program error: OPC item cannot be
written.
Re-install Global Drive Loader.
If the problem cannot be eliminated, contact
Lenze.
C60Dh Internal program error: OPC-Control. Restart PC.
Re-install Global Drive Loader.
C60Eh Error during reading a file. Check the path of the parameter file.
Communication and download errors
D100h Error during activation of "OPCCtl".
"OPCCtl" has not been installed or has not
been registered correctly.
Re-install Global Drive Loader.
D101h No connection with OPC server. Check whether the OPC server has been
installed correctly.
Re-install Global Drive Loader.
D102h OPC server is not in the status "Running". Restart PC.
D103h Error during creation of an OPC item. Re-install Global Drive Loader.
D104h Error during download. The message includes causes and remedies.
D105h Error during creation of connection with OPC
server.
Restart the PC or re-install Global Drive
Loader.
D106h Error during disconnection from OPC server. Restart the PC or re-install Global Drive
Loader.
Errors within the DriveServer
E7C18000 Error during the download preparations. Restart the download.
E7C18001 PLC has not stopped. Stop PLC program in the target system.
E7C18002 Controller inhibit is not set. Set controller inhibit in the target system.
E7C18003 Incorrect file type (no LC9 file). Create LC9 file.
E7C18004 Check sum test is negative (incorrect check
sum).
Restart the download.
Increase the time-out time in the system bus
configuration tool (e.g. to 3 seconds).
E7C18005 Item cannot be accessed due to download. Restart the download after a few minutes or
restart the PC.
Error number Cause Remedy
Global Drive Loader
Appendix
Error numbers, causes & remedies
36 3.0 EN L
E7C18006 Target system is copying RAM blocks. Start PLC program in the target system.
E7C18007 Error after the download. Restart the download.
E7C18008 Error after version comparison during the
download of an LC7 file.
Different versions in the LC7 file and the
target system.
Update the operating system for 9300 EK.
E7C18009 Template "Cam" is not available in the target
system.
Create a DDS project based on Template Cam
and transfer it to the target system.
Error number Cause Remedy
L 3.0 EN 37
Global Drive Loader
Appendix
Log files
7.2 Log files
Log files list all important events for documentation and diagnostics purposes. These
events are for instance:
> Program start
> Communication parameters for connection with the target system
> Target system (name, version, software product code, etc.)
> Information about the download
> Disconnection
> Program end
Tip!
The "GDLoader.txt" log file is automatically created by the Global Drive Loader
and filled with entries until the value indicated in the initialisation file by the key
"SizeLogFile" is exceeded.
If the value is exceeded, the system asks whether a log file back-up is wanted
before all existing entries are deleted.
Global Drive Loader
Appendix
Log files
38 3.0 EN L
Every event saved in a log file contains the following information:
Column Meaning
Id Function index identifying the event:
0001h Program start
0002h Program end
0003h Log in
0004h Log out
0005h Opening of a DDS binary file
0006h Preparation of DDS binary file for the download
0007h Download of the DDS binary file
0008h PLC program start
0009h PLC program stop
000Ah Opening of a GDC parameter set file
000Bh Opening of a GDC controller description
000Ch Reading of the code list from the GDC controller description
000Dh Reading of the code initialisation values from the GDC parameter set file
000Eh Parameter set transfer
000Fh Status line update
0010h Opening of a script for the batch mode
0011h Script processing
0012h Opening of application data
0013h Preparation of application data for the download
0014h Download of application data
Category The following categories are available:
Error
Warning
Note
Info
Date and time Time when the event occurred.
Message text Short event description.
Error code Error number which indicates an error.
L 3.0 EN 39
Global Drive Loader
Appendix
File headers for application data
7.3 File headers for application data
For the interpretation of the header information applies: least significant byte first:
@ Note!
The file header is not valid for *.lc7 files. *.lc7 files can only be transferred to the
9300 Servo cam profiler.
Name Data type Data length
in bytes
Contents
wSizeHeader Word 2 Length of the header in bytes
wDataType Word 2 Specification identification of data
After the download, these information will be available
under C2131.
0 ... 10000 Lenze-specific data
> 10000 User data
dwVersion DWORD 4 Data version
After the download, these information will be available
under C2132.
dwRealSize DWORD 4 Length of user data in bytes (without header)
dwTimeStamp DWORD 4 Time stamp of last data change
After the download, these information will be available
under C2133.
wLicenseInfo Word 2 Reserved for extensions
wSizeSymbolicName Word 2 Length of the symbolic file name
achSymbolicName ACH wSize
Symbolic
Name
Character array including the symbolic file name
After the download, these information will be available
under C2130.
wCopyToRam Word 2 Determines whether the data will be automatically copied to
the application RAM of the PLC after the download.
Max. data length = 128 kbytes (RAM blocks 1 & 2)
0 Data are not copied to the application RAM.
1 Data are copied to the application RAM.
2 ... 65535 reserved
dwReserved DWORD 4 Reserved for extensions
awSizeAddInfo DWORD 190
E4 00 0A 00 01 00 00 00 1C FF 00 00
wSizeHeader = 00 E4 = 228 Byte hex
wDataType = 00 0A = 10 (Cam data) hex
dwVersion = 00 00 00 01 hex
dwRealSize = 00 00 FF 1C = 65308 Byte hex
Global Drive Loader
Index
40 3.0 EN L
8 Index
Symbols
"?" menu 12
"Online" menu 11
"Options" menu 11
A
After the download 24
Application notes 6
Assignment of controller descriptions 25
Automatic scanning 17
B
Batch mode 27
Before downloading a file 23
C
Command line call 31
Communication settings 13, 28
Connection with the target system 8
Controller description 25
Conventions used 5
Copyright 2
Copyright information 2
D
Download sequence 23
DriveServer 13
During the download 23
E
E-mail to Lenze 41
F
Feedback to Lenze 41
Function area 12
G
General settings 28
H
How to select a target system 17
I
Imprint 2
Installation 9
L
Language 10
Language selection 10
Layout of the safety information 6
LECOM 14
Liability 2
M
Menu bar 11
O
OPC bus server for LECOM 14
OPC bus server for system bus (CAN) 13
P
PC system bus adapter 8
S
Safety information 6
Script file 27
Software installation 9
Status bar 12
Supported target systems 7
System bus (CAN) 13
T
Target system-dependent settings 28
Target systems 7
Toolbar 12
Trademarks 2
U
Use of other OPC bus servers 14
User interface 7, 10
L 41
Your opinion is important to us
These Instructions were created to the best of our knowledge
and belief to give you the best possible support for handling
our product.
If you have suggestions for improvement, please e-mail us to:
feedback-docu@Lenze.de
Thank you for your support.
Your Lenze documentation team

You might also like