Lenze 9300 User Manual

L

Manual

Global Drive
PLC Developer Studio

Global Drive

Function library

Lenze9300Servo.lib

The function library Lenze9300Servo.lib can be used for the following Lenze PLCs:

Type from hardware version from software version

9300 Servo PLC EVS93XX−xI 2K 10

9300 Servo PLC EVS93XX−xT 2K 10

ECSxA ECSxAxxx 1C 7.0

Important Note:

The software is made available to the user in the currently existing form. All risks with regard to the quality and the results arising from its
use remain the responsibility of the user. The user must implement the appropriate security precautions against possible erroneous
application.

We do not accept any responsibilty for direct or consequential damages, such as loss of profits, loss of orders, or effects on the course of
business of any kind.

 2000 Lenze GmbH & Co KG

No part of this documentation may be copied or made available to third parties without the express written permission of
Lenze GmbH & Co KG.

We have take great care in assembling the information in this documentation, and checked that it corresponds to the hardware and software
that is described. Nevertheless, we cannot guarantee that there are no discrepancies. We do not accept any legal responsibility or liability
for damage that may thereby ensue. Any necessary corrections will be implemented in subsequent versions.

Windows, Windows NT and MS−DOS are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other
countries.
IBM and VGA are registered trademarks of International Business Machines, Inc.
All other designations are trade names of their owners.

Version 1.1 08/2000 − TD22

Function block library Lenze9300Servo.lib

Contents

1 Preface and general information 1−1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.1 About this Manual 1−1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.1.1 Conventions in this Manual 1−1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.1.2 Pictograms in this Manual 1−1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.1.3 Terminology used 1−2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2 Lenze software guidelines for variable names 1−3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2.1 Hungarian Notation 1−3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2.1.1 Recommendation for designating variable types 1−4 . . . . . . . . . . . . . . . . . . . . . . . . . .

1.2.1.2 Designation of the signal type in the variable name 1−5 . . . . . . . . . . . . . . . . . . . . . . . .

1.2.1.3 Special handling of system variables 1−5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.3 Version identifiers of the function library 1−6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2 Function blocks 2−1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1 Special functions 2−1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.1 Holding brake (L_BRK) 2−1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1.2 Supply−failure control (L_MFAIL) 2−6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3 Appendix 3−1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1 Code table 3−1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1.1 L_BRK 3−1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1.2 L_MFAIL 3−1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4 Index 4−1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

l

Lenze9300Servo.lib EN 1.1

i

Function block library Lenze9300Servo.lib

Contents

ii

Lenze9300Servo.lib EN 1.1

l

Function block library Lenze9300Servo.lib

Preface and general information

1 Preface and general information

1.1 About this Manual

This Manual contains information on the function blocks that are included in the function block library
Lenze9300Servo.lib for the Drive PLC Developer Studio .

· These function blocks can be used, for instance, in the 9300 Servo PLC automation system.

· The function blocks are based on the functions that are available in the 9300 servo controller(

V2.0).

In Drive PLC Developer Studio (DDS) you make the basic settings for your drive application offline,
by using variables (in accordance with the IEC1131−3 standard) as aids for parameterizing the
appropriate function blocks.

Using Global Drive Control (GDC) or keypad you can then Online set the parameters for the required
functionality of your drive application, by accessing the code positions for the various instances of
the function blocks.

1.1.1 Conventions in this Manual

This Manual uses the following conventions to distinguish between different types of information:

Variable names

are shown in the explanatory texts in italics:

· The signal at nIn_a ..."

can be recognized by the names. They always begin with L_":

· The FB L_ARIT can ..."

Instances

For function blocks that have one or more first instances, there are tables that describe the
corresponding codes:

Variable name L_ARIT1 L_ARIT2 Setting range Lenze

byFunction C0338 C0600 0 ... 5 1

You can access these codes Online is linked to Global Drive Control (GDC) or keypad .

Tip!

You can use the Parameter Manager to assign the same codes to these instances that are assigned
in the 9300 servo controller( V2.0).

1.1.2 Pictograms in this Manual

Use of
Pictographs

Warning of
material damage

Other notes Tip! This note designates general, useful notes.

l

Lenze9300Servo.lib EN 1.1

Signal words

Stop! Warns of potential damage to material.

Possible consequences if disregarded:
Damage of the controller/drive system or its environment

If you observe it, handling of the controller/drive system is made easier.

.

1−1

Function block library Lenze9300Servo.lib

Preface and general information

1.1.3 Terminology used

Term In the following text used for

FB Function block

SB System block

Parameter codes Codes for setting the functionality of a function block

GDC Global Drive Control (parameterization program from Lenze)

1−2

Lenze9300Servo.lib EN 1.1

l

Function block library Lenze9300Servo.lib

Preface and general information

1.2 Lenze software guidelines for variable names

The previous concepts for Lenze controllers were based on codes that represented the input and
output signals, and the parameters of function blocks.

· For the sake of clarity, names were defined for the codes in the documentation.

· In addition, the signal types were defined by graphical symbols.

The user could see at a glance which kind of signal (analog, phase−angle etc.) had to be present at
the particular interface.

The concept for the new automation system does not use direct codes in the
programming. The IEC 61131−3 standard is used instead.

· This standard is based on a structure of variable names.

· If the user applies variables in his project, then he can name the variables as he chooses.

In order to avoid the growth of a multitude of different conventions for naming variables in existing
and future projects and function libraries that are programmed by Lenze personnel, we have set up
software guidelines that must be followed by all Lenze staff.

In this convention for creating variable names, Lenze keeps to the Hungarian Notation that has been
specifically expanded by Lenze.

If you make use of Lenze−specific functions or function blocks, you will immediately be able to see,
for instance, which data type you must transfer to a function block, and which type of data you will
receive as an output value.

1.2.1 Hungarian Notation

These conventions are used so that the most significant characteristics of a program variable can
instantly be recognized from its name.

Variable names

consist of

· a prefix (optional)

· a data−type entry

· and an identifier

The prefix and data−type entry are usually formed by one or two characters. The identifier (the
"proper" name) should indicate the application, and is therefore usually somewhat longer.

Prefix examples

prefix Meaning

a Array (combined type), field

p Pointer

l

Lenze9300Servo.lib EN 1.1

1−3

Function block library Lenze9300Servo.lib

Preface and general information

Examples of the data−type entry

Examples of a data−type Meaning

b Bool

by Byte

n Integer

w Word

dn Double integer

dw Double word

s String

f Real (float)

sn Short integer

t Time

un Unsigned integer

udn Unsigned double integer

usn Unsigned short integer

Identifier (the proper variable name)

· An identifier begins with a capital letter.

· If an identifier is assembled from several "words", then each "word" must start with a capital

letter.

· All other letters are written in lower case.

Examples:

Array of integers anJogValue[10] ;

Bool bIsEmpty ;

Word wNumberOfValues ;

Integer nLoop ;

Byte byCurrentSelectedJogValue ;

1.2.1.1 Recommendation for designating variable types

In order to be able to recognize the type of variable in a program according to the name, it makes
sense to use the following designations, which are placed in front of the proper variable name and
separated from it by an underline stroke:

I_<Variablename> VAR_INPUT

Q_<Variablename> VAR_OUTPUT

IQ_<Variablename> VAR_IN_OUT

R_<Variablename> VAR RETAIN

C_<Variablename> VAR CONSTANT

CR_<Variablename> VAR CONSTANT RETAIN

g_<Variablename> VAR_GLOBAL

gR_<Variablename> VAR_GLOBAL RETAIN

gC_<Variablename> VAR_GLOBAL CONSTANT

gCR_<Variablename> VAR_GLOBAL CONSTANT RETAIN

1−4

Example

for a global array of type integer that includes fixed setpoints (analog) for a speed setting:

g_anFixSetSpeedValue_a

Lenze9300Servo.lib EN 1.1

l

Function block library Lenze9300Servo.lib

Preface and general information

1.2.1.2 Designation of the signal type in the variable name

The inputs and outputs of the Lenze function blocks each have a specific signal type assigned. These
may be: digital, analog, position, or speed signals.

For this reason, each variable name has an ending attached that provides information on the type of
signal.

Signal type Ending Previous designation

analog _a (analog)

digital _b (binary)

Phase−angle difference or speed _v (velocity)

Phase−angle or position _p (position)

Tip!

Normalizing to signal type phase−angle difference/speed: 16384 (INT) ¢ 15000 rpm

Normalizing to signal type analog: 16384 ¢ 100 % ¢ value under [C0011] = n

Normalizing to signal type angle or position: 65536 ¢ 1 motor revolution

H
G
F
E

max

Examples:

Variable name Signal type Type of variable

nIn_a Analog input value Integer

dnPhiSet_p Phase signals Double integer

bLoad_b Binary value (TRUE/FALSE) Bool

nDigitalFrequencyIn_v Speed input value Integer

1.2.1.3 Special handling of system variables

System variables require special handling, since the system functions are only available for the user
as I/O connections in the control configuration.

In order to be able to access a system variable quickly during programming, the variable name must
include a label for the system function.

For this reason, the name of the corresponding system block is placed before the name of the
variable.

Examples:

AIN1_nIn_a

CAN1_bCtrlTripSet_b

DIGIN_bIn3_b

l

Lenze9300Servo.lib EN 1.1

1−5