Stober Drive Based Synchronous User manual

Type
User manual
Drive Based Synchronous
Operating manual
en-US
02/2021
ID 443046.02
Table of contents STOBER
ii
02/2021 | ID 443046.02
Table of contents
1 Foreword .................................................................................................................................................................. 5
2 User information ....................................................................................................................................................... 6
2.1 Note on gender........................................................................................................................................................ 6
2.2 Storage and transfer ................................................................................................................................................ 6
2.3 Described product.................................................................................................................................................... 6
2.4 Timeliness ................................................................................................................................................................ 6
2.5 Original language ..................................................................................................................................................... 6
2.6 Limitation of liability ................................................................................................................................................ 6
2.7 Formatting conventions........................................................................................................................................... 7
2.7.1 Use of symbols........................................................................................................................................ 7
2.7.2 Markup of text elements ........................................................................................................................ 8
2.7.3 Mathematics and formulas..................................................................................................................... 8
2.8 Trademarks .............................................................................................................................................................. 9
3 What you should know before commissioning ........................................................................................................ 10
3.1 Structure of the program interface........................................................................................................................ 10
3.1.1 Individualized workspace...................................................................................................................... 12
3.1.2 Navigation using sensitive circuit diagrams.......................................................................................... 12
3.2 Meaning of parameters .........................................................................................................................................13
3.2.1 Parameter groups ................................................................................................................................. 13
3.2.2 Parameter types and data types........................................................................................................... 14
3.2.3 Parameter types ................................................................................................................................... 15
3.2.4 Parameter structure ............................................................................................................................. 15
3.2.5 Parameter visibility ............................................................................................................................... 16
3.3 Signal transmission and fieldbus mapping.............................................................................................................17
3.4 Power-loss protected storage................................................................................................................................ 18
4 Commissioning ........................................................................................................................................................ 19
4.1 Initiating the project .............................................................................................................................................. 20
4.1.1 Projecting the drive controller and axis................................................................................................ 20
4.1.2 Configuring safety technology .............................................................................................................. 21
4.1.3 Creating other modules and drive controllers...................................................................................... 21
4.1.4 Specifying a module.............................................................................................................................. 22
4.1.5 Specifying the project ........................................................................................................................... 22
4.2 Mapping the mechanical axis model ..................................................................................................................... 23
4.2.1 Parameterizing a STOBER motor .......................................................................................................... 23
4.2.2 Parameterizing the axis model ............................................................................................................. 23
4.3 Referencing absolute position ............................................................................................................................... 27
4.3.1 Defining the referencing method ......................................................................................................... 27
4.3.2 Parameterizing the reference switch.................................................................................................... 27
STOBER Table of contents
02/2021 | ID 443046.02
iii
4.3.3 Setting the reference............................................................................................................................ 28
4.3.4 Parameterizing the limit switch ............................................................................................................ 28
4.4 Parameterizing Drive Based device control ...........................................................................................................29
4.4.1 Parameterizing transition conditions.................................................................................................... 29
4.5 Configuring synchronous operation....................................................................................................................... 30
4.5.1 Model 1: Virtual master or master encoder, multiple slave axes......................................................... 31
4.5.2 Model 2: Master encoder, individual slave axis.................................................................................... 38
4.5.3 Model 3: Master axis, one or more slave axes ..................................................................................... 42
4.6 Configuring the IGB motion bus network .............................................................................................................. 45
4.6.1 Projecting the IGB motion bus network ............................................................................................... 45
4.6.2 Assigning master and slave axes........................................................................................................... 46
4.6.3 Monitoring synchronous operation...................................................................................................... 47
4.7 Transmitting a configuration to drive controllers.................................................................................................. 48
4.7.1 Transmitting and saving the configuration........................................................................................... 48
4.8 Testing the configuration....................................................................................................................................... 50
4.8.1 Testing jog mode .................................................................................................................................. 50
4.8.2 Testing the motion commands ............................................................................................................. 52
4.8.3 Testing synchronous operation ............................................................................................................ 53
4.9 Parameterizing the Drive Based synchronous application..................................................................................... 58
4.9.1 General motion variables and signal sources ....................................................................................... 59
4.9.2 Parameterizing motion block operating mode ..................................................................................... 62
4.9.3 Parameterizing command operating mode.......................................................................................... 80
5 More on Drive Based synchronous?......................................................................................................................... 85
5.1 Drive Based synchronous – Concept......................................................................................................................85
5.1.1 Operating modes .................................................................................................................................. 86
5.1.2 Jog mode............................................................................................................................................... 86
5.1.3 Control panels....................................................................................................................................... 87
5.1.4 Data sources ......................................................................................................................................... 87
5.1.5 Additional functions.............................................................................................................................. 87
5.1.6 Motion core .......................................................................................................................................... 87
5.2 IGB motion bus network ........................................................................................................................................ 88
5.3 Mechanical axis model........................................................................................................................................... 89
5.3.1 Rotational drives................................................................................................................................... 89
5.3.2 Translational drives............................................................................................................................... 90
5.4 Limit switches ........................................................................................................................................................ 92
5.4.1 Real axes ............................................................................................................................................... 92
5.4.2 Virtual master ....................................................................................................................................... 97
5.4.3 Special cases ......................................................................................................................................... 98
5.5 Referencing............................................................................................................................................................ 99
5.5.1 Referencing methods.......................................................................................................................... 100
5.5.2 Reference position.............................................................................................................................. 125
5.6 Drive Based device control .................................................................................................................................. 126
Table of contents STOBER
iv
02/2021 | ID 443046.02
5.6.1 Drive Based device state machine ...................................................................................................... 126
5.6.2 States, transitions and conditions....................................................................................................... 127
5.7 Motion commands...............................................................................................................................................131
5.8 Electronic nameplate ........................................................................................................................................... 132
5.9 Operating modes – Block diagrams .....................................................................................................................133
5.9.1 Motion block....................................................................................................................................... 133
5.9.2 Command ........................................................................................................................................... 137
5.10 Cycle times...........................................................................................................................................................139
6 Appendix............................................................................................................................................................... 140
6.1 Standard mapping of PROFINET and Drive Based synchronous ..........................................................................140
6.1.1 SC6, SI6: RxPZD ................................................................................................................................... 140
6.1.2 SC6, SI6: TxPZD ................................................................................................................................... 141
6.1.3 SD6: RxPZD.......................................................................................................................................... 142
6.1.4 SD6: TxPZD.......................................................................................................................................... 142
6.2 Detailed information............................................................................................................................................ 143
6.3 Abbreviations....................................................................................................................................................... 144
7 Contact.................................................................................................................................................................. 145
7.1 Consultation, service and address ....................................................................................................................... 145
7.2 Your opinion is important to us ........................................................................................................................... 145
7.3 Close to customers around the world..................................................................................................................146
Glossary ................................................................................................................................................................ 149
STOBER 1 | Foreword
02/2021 | ID 443046.02
5
1 Foreword
The DriveControlSuite software of the 6th STOBER drive controller generation offers convenient functions for efficient
project configuration and commissioning for synchronous operation of multi-axis systems or single-axis applications.
The Drive Based synchronous application package contained in the software provides universal solutions for drive-based
motion control of SD6, SC6 and SI6 series single-axis and double-axis controllers using position, velocity and torque/force
control types. The standard commands associated with these control types are categorized into two operating modes:
command and motion block.
Additional functions for monitoring process variables such as positions or velocities offer added convenience in monitoring.
This documentation describes the general functions of the Drive Based synchronous application and guides you step by step
through the setup and project configuration of your drive project in the individual operating modes.
2 | User information STOBER
6
02/2021 | ID 443046.02
2 User information
This documentation supports you in the setup and project configuration of your drive system with the Drive Based
synchronous application in conjunction with Drive Based device control.
Technical knowledge
In order to be able to commission one or more drive controllers—in combination with a controller, where applicable—using
Drive Based synchronous, you should have experience in project configuration for drive-based motion profiles.
Technical requirements
Before you begin operating your drive system, you need to have wired the drive controllers involved and initially check that
they are functioning correctly. To do so, follow the instructions in the respective commissioning instructions.
2.1 Note on gender
Note on gender
For reasons of improved readability, gendered differentiation is not used. In the sense of equal treatment, the
corresponding terms apply equally to all genders. The shortened form does not imply any value judgment, but is purely for
editorial reasons.
2.2 Storage and transfer
As this documentation contains important information for handling the product safely and efficiently, it must be stored in
the immediate vicinity of the product until product disposal and be accessible to qualified personnel at all times.
Also pass on this documentation if the product is transferred or sold to a third party.
2.3 Described product
This documentation is binding for:
SD6, SC6 or SI6 series drive controllers in conjunction with the DriveControlSuite software (DS6) in V 6.5-A or higher and
associated firmware in V 6.5-A or higher.
2.4 Timeliness
Check whether this document is the latest version of the documentation. We make the latest document versions for our
products available for download on our website:
http://www.stoeber.de/en/downloads/.
2.5 Original language
The original language of this documentation is German; all other language versions are derived from the original language.
2.6 Limitation of liability
This documentation was created taking into account the applicable standards and regulations as well as the current state of
technology.
No warranty or liability claims for damage shall result from failure to comply with the documentation or from use that
deviates from the intended use of the product. This is especially true for damage caused by individual technical
modifications to the product or the project configuration and operation of the product by unqualified personnel.
STOBER 2 | User information
02/2021 | ID 443046.02
7
2.7 Formatting conventions
Orientation guides in the form of signal words, symbols and special text markups are used to emphasize specific
information so that you are able identify it in this documentation quickly.
2.7.1 Use of symbols
Safety instructions are identified with the following symbols. They indicate special risks when handling the product and are
accompanied by relevant signal words that express the extent of the risk. Furthermore, useful tips and recommendations
for efficient, error-free operation are specially highlighted.
ATTENTION!
Attention
This indicates that damage to property may occur
â–ª if the stated precautionary measures are not taken.
CAUTION!
Caution
This word with a warning triangle indicates that minor personal injury may occur
â–ª if the stated precautionary measures are not taken.
WARNING!
Warning
This word with a warning triangle means there may be a considerable risk of fatal injury
â–ª if the stated precautionary measures are not taken.
DANGER!
Danger
This word with a warning triangle indicates that there is a considerable risk of fatal injury
â–ª if the stated precautionary measures are not taken.
Information
Information indicates important information about the product or serves to emphasize a section in the documentation that
deserves special attention from the reader.
2 | User information STOBER
8
02/2021 | ID 443046.02
2.7.2 Markup of text elements
Certain elements of the continuous text are distinguished as follows.
Important information Words or expressions with a special meaning
Interpolated position mode Optional: File or product name or other name
Detailed information Internal cross-reference
http://www.samplelink.com External cross-reference
Software and other displays
The following formatting is used to identify the various information content of elements referenced by the software
interface or a drive controller display, as well as any user entries.
Main menu
Settings
Window names, dialog box names, page names or buttons, combined
proper nouns, functions referenced by the interface
Select
Referencing method A
Predefined entry
Save your
<own IP address>
User-defined entry
EVENT 52:
COMMUNICATION
Displays (status, messages, warnings, faults) for status information
referenced by the interface
Keyboard shortcuts and command sequences or paths are represented as follows.
[CTRL], [CTRL] + [S]
Key, shortcut
Table > Insert table Navigation to menus/submenus (path specification)
2.7.3 Mathematics and formulas
The following signs are used to represent mathematical relationships and formulas.
- Subtraction
+ Addition
× Multiplication
÷ Division
| | Amount
STOBER 2 | User information
02/2021 | ID 443046.02
9
2.8 Trademarks
The following names used in connection with the device, its optional equipment and its accessories are trademarks or
registered trademarks of other companies:
CANopen®,
CiA®
CANopen® and CiA® are registered European Union trademarks of CAN in
AUTOMATION e.V., Nuremberg, Germany.
EnDat®EnDat® and the EnDat® logo are registered trademarks of Dr. Johannes Heidenhain
GmbH, Traunreut, Germany.
EtherCAT®,
Safety over EtherCAT®,
TwinCAT®
EtherCAT®, Safety over EtherCAT® and TwinCAT® are registered trademarks of
patented technologies licensed by Beckhoff Automation GmbH, Verl, Germany.
HIPERFACE®HIPERFACE® and the HIPERFACE DSL® logo are registered trademarks of SICK
STEGMANN GmbH, Donaueschingen, Germany.
PLCopen®PLCopen® is a registered trademark of the PLCopen Organisation, Gorinchem,
Netherlands.
PROFIBUS®,
PROFINET®
The PROFIBUS and the PROFINET logo are registered trademarks of PROFIBUS
Nutzerorganisation e.V., Karlsruhe, Germany.
All other trademarks not listed here are the property of their respective owners.
Products that are registered as trademarks are not specially indicated in this documentation. Existing property rights
(patents, trademarks, protection of utility models) are to be observed.
3 | What you should know before commissioning STOBER
10
02/2021 | ID 443046.02
3 What you should know before commissioning
The following chapters provide a quick introduction to the structure of the program interface and accompanying window
designations as well as relevant information about parameters and generally saving your project configuration.
3.1 Structure of the program interface
The DriveControlSuite commissioning software (DS6) offers a graphic interface that you can use to project, parameterize
and start up your axis model quickly and efficiently.
1
2
3
4
5 7
8
6
Fig.1: DS6: Program interface
1 Project tree
2 Project menu
3 Workspace
4 Parameter description
5 Parameter check
6 Messages
7 Variable parameter lists
8 Status bar
STOBER 3 | What you should know before commissioning
02/2021 | ID 443046.02
11
Menus and toolbars
Using the main menus File, View, Settings and Window, you can open and save your projects, display and hide program
windows, define the interface language and various access levels, or switch between different areas of the program
interface.
1: Project tree
All of the drive controllers of your drive project are collected in the project tree under a project and organized into
modules.
One project, one module and one drive controller are created in the project tree by default and can be configured
individually; all additional elements must be added manually. If you would like to edit an element of the project tree, mark
the element and switch over to the project menu.
2: Project menu
You can edit the elements of the project tree in the project menu. The project menu consists of the project, module and
drive controller views.
Highlighting one of the project, module or drive controller elements in the project tree automatically activates the
corresponding project menu view.
3: Workspace
The workspace is only active while configuring a drive controller (project tree: drive controller). Depending on the projected
device control and application, the workspace allows quick access to the wizards and parameter list, the graphical
programming as well as the scope function of the drive controller view in the project menu.
4: Parameter description
Each parameter on a wizard page of the workspace has a short description, with possible selection values where applicable.
By clicking on a parameter, the associated information is displayed in the parameter description.
5: Parameter check
Generally, your parameter values, if calculable, are checked by the software against each other for plausibility.
Abnormalities or discrepancies are output and weighted in this view.
6: Messages
The software logs the connection and communication state of the active drive components, incorrect inputs received on
the system side and errors in the messages.
7: Variable parameter lists
You can use variable parameter lists to compile the parameters currently required for a quick overview in individual
parameter lists.
8: Status bar
In the status bar, you can find the specification of the software version. When loading projects, it also offers additional
information on the project file, the devices and the progress of loading or updating projects.
3 | What you should know before commissioning STOBER
12
02/2021 | ID 443046.02
3.1.1 Individualized workspace
The project tree (1) and project menu (2) are connected and, like the parameter check and messages (5, 6), can also be
docked at the left, right or bottom edge of the screen. This program window can also be displayed or hidden using the View
menu.
The workspace (3) and parameter description (4) are also connected to each other and always positioned in the middle.
Both areas can be minimized or maximized.
3.1.2 Navigation using sensitive circuit diagrams
Fig.2: DriveControlSuite: Navigation using text links and symbols
In order to illustrate graphically the processing sequence of actual and set values, the use of signals or certain drive
component arrangements and to make configuring the accompanying parameters easier, they are displayed on the
respective wizard pages of the workspace in the form of circuit diagrams.
Blue text links or clickable icons indicate links within the program. These refer to the corresponding wizard pages and, as a
result, allow you to reach additional helpful detail pages with just a click.
STOBER 3 | What you should know before commissioning
02/2021 | ID 443046.02
13
3.2 Meaning of parameters
You can adapt the function of the drive controller to your individual application using parameters. In addition, parameters
visualize the current actual values (actual velocity, actual torque, etc.) and trigger general actions like Save values, Test
phase, etc.
Interpretation of parameter identification
Parameter identification consists of the following elements, where short forms are also possible, i.e. only specifying a
coordinate or the combination of coordinate and name.
E50 V0
Coordinate Name Version
Drive controller G6
Drive controller
generation/series
3.2.1 Parameter groups
Parameters are assigned to individual groups by topic. The 6th generation of STOBER drive controllers differentiates
between the following parameter groups.
Group Topic
A Drive controllers, communication, cycle times
B Motor
C Machine, velocity, torque/force, comparators
D Set value
E Display
F Terminals, analog and digital inputs and outputs, brake
G Technology – Part 1 (application-dependent)
H Encoders
I Motion (all motion settings)
J Motion blocks
K Control panel
L Technology – Part 2 (application-dependent)
M Profiles (application-dependent)
N Additional functions (application-dependent; extended cam control unit)
P Customer-specific parameters (programming)
Q Customer-specific parameters, instance-dependent (programming)
R Production data for the drive controller, motor, brakes, motor adapter, gear unit and geared motor
S Safety (safety technology)
T Scope
U Protection functions
Z Fault counter
Tab. 1: Parameter groups
3 | What you should know before commissioning STOBER
14
02/2021 | ID 443046.02
3.2.2 Parameter types and data types
In addition to topic-based sorting in individual groups, all parameters belong to a certain data type and parameter type. The
data type of a parameter is displayed in the parameter list, properties table. The connections between parameter types,
data types and their value range can be found in the following table.
Type Style Length Value range (decimal)
INT8 Integer or selection 1 byte (signed) -128 – 127
INT16 Integer 2 bytes (1 word, signed) -32768 – 32767
INT32 Integer or position 4 bytes (1 double word,
signed)
-2147483648 – 2147483647
BOOL Binary number 1 bit (internal:
LSB in 1 byte)
0, 1
BYTE Binary number 1 byte (unsigned) 0 – 255
WORD Binary number 2 bytes (1 word, unsigned) 0 – 65535
DWORD Binary number or parameter
address
4 bytes (1 double word,
unsigned)
0 – 4294967295
REAL32
(single type according to
IEE754)
Floating-point number 4 bytes (1 double word,
signed)
-3.40282 × 1038 – 3.40282 ×
1038
STR8 Text 8 characters —
STR16 Text 16 characters —
STR80 Text 80 characters —
Tab. 2: Parameters – Data types, styles, possible values
Parameter types – Use
§Integer, floating-point number
For general computing processes
Example: Set and actual values
§Selection
Numeric value to which a direct meaning is assigned
Example: Sources for signals or set values
§Binary number
Bit-oriented parameter information that is collected in binary
Example: Control and status words
§Position
Integer combined with associated units and decimal places
Example: Actual and set values of positions
§Velocity, acceleration, deceleration, jerk
Floating-point number combined with the associated units and decimal places
Example: Actual and set values for velocity, acceleration, deceleration, jerk
§Parameter address
Corresponds to the storage location of another parameter
Example: Indirect read sources for analog and digital outputs and for fieldbus mapping
§Text
Outputs or messages
STOBER 3 | What you should know before commissioning
02/2021 | ID 443046.02
15
3.2.3 Parameter types
The following types of parameters are differentiated.
Parameter type Description Example
Simple parameters Consist of one group and one line with a
defined value.
A21Brake resistor R: Value = 100ohms
Array parameters Consist of a group, a line and multiple
sequential (listed) elements, which have the
same properties but different values.
A10Access level
§A10[0] access level: Value = Access level
via operating unit
§A10[2] access level: Value = Access level
via CANopen and EtherCAT
§A10[4] access level: Value = Access level
via PROFINET
Structure parameters Consist of a group, a line and multiple
sequential (listed) elements, which can have
different properties and different values.
A00Save values
§A00[0] Start: Value = Start action
§A00[1] Progress: Value = Display action
progress
§A00[2] Result: Value = Display action
result
Tab. 3: Parameter types
3.2.4 Parameter structure
Every parameter has specific coordinates with the following pattern.
E250 [2] .3
Axis
Group
Line
1.
Element
Bit
§Axis
The axis to which a parameter is assigned in the case of multiple axes (optional).
§Group
The thematic group to which a parameter belongs.
§Line
Distinguishes the parameters within a parameter group.
§Element
Elements of an array or structure parameter (optional).
§Bit
Selection of an individual bit for complete data addressing (optional).
3 | What you should know before commissioning STOBER
16
02/2021 | ID 443046.02
3.2.5 Parameter visibility
The visibility of a parameter depends on the access level defined in the software, the dependency of other parameters, the
selected application and the version of the associated firmware.
Access level
The access options for the individual software parameters are ranked hierarchically and divided into individual levels. This
means that parameters can be hidden for a specific purpose and, relatedly, their configuration options can be locked
starting from a specific level. The following levels are present:
§Level 0
Elementary parameters
§Level 1
Important parameters of an application
§Level 2
Important parameters for service with extensive diagnostic options
§Level 3
All parameters needed for commissioning and optimizing an application
Parameter A10 Access level controls general access to parameters:
§Over the SD6 drive controller display (A10[0])
§Over CANopen or EtherCAT (A10[2])
§Over PROFINET (A10[3])
Hiding functions
Hiding functions are used to hide parameters with regard to their logical relationships to other option modules or
parameters.
For example, a drive controller can evaluate an encoder using terminal X120, provided that terminal module XI6 has been
installed. The accompanying evaluation is activated using parameter H120. However, this parameter is visible only if
terminal module XI6 was initially selected during the drive project configuration.
Applications
Applications generally differ in terms of functions and their activation. For this reason, different parameters are available
with each application.
Firmware
A newer version of the firmware may introduce new parameters. Parameters that have been configured for files of an older
firmware function may not be visible in newer versions. In such cases, the respective parameter description includes a
corresponding note.
STOBER 3 | What you should know before commissioning
02/2021 | ID 443046.02
17
3.3 Signal transmission and fieldbus mapping
The transmission of control signals and set values in DriveControlSuite meets the following principles.
Signal transmission
Drive controllers are either controlled over a fieldbus, using mixed operation consisting of a fieldbus system and terminals
or exclusively using terminals.
You can use the corresponding selection parameters, referred to as data sources, to configure whether the signals and set
values are obtained over a fieldbus or using terminals.
In case of activation over a fieldbus, parameters that are selected as data sources for control signals or set values must be
part of the subsequent fieldbus mapping; in the case of activation using terminals, the respective analog or digital inputs
are specified directly.
Fieldbus mapping
If you are working with a fieldbus system and have selected the source parameters for signals and set values, configure the
fieldbus-specific settings, e.g. the layout of process data channels for transmitting receive and transmit process data, as the
last step.
The respective procedure can be found in the accompanying STOBER fieldbus manuals.
3 | What you should know before commissioning STOBER
18
02/2021 | ID 443046.02
3.4 Power-loss protected storage
All project configurations, parameterizations and related changes to parameter values are in effect after transmission to the
drive controller, but are not yet stored in non-volatile memory.
Saving to a drive controller
You have the following options for saving the configuration to a drive controller in non-volatile memory:
§Saving the configuration using the Save values wizard:
Project menu > Wizards area > Projected axis > Save values wizard: Select the Save values action
§Saving the configuration using the parameter list:
Project menu > Parameter list area > Projected axis > Group A: Drive controller > A00 Save values: Set the parameter
A00[0] to the value 1: Active
§Saving the configuration using the operating unit:
SD6 drive controller > Operating unit: Press the save button for 3 seconds
Saving to all drive controllers within a project
You have the following options for saving the configuration to multiple drive controllers in non-volatile memory:
§Saving the configuration using the toolbar:
Toolbar > Save values symbol: Click on the Save values symbol
§Saving the configuration using the Assignment and live firmware update window:
Project menu > Assignment and live firmware update area > Projected axis > Assignment and live firmware update
window: Click on Save values (A00)
Information
Do not shut off the drive controller while saving. If the supply voltage to the control unit is interrupted while saving, the
drive controller starts without an executable configuration when it is next switched on. In this case, the configuration must
be transferred to the drive controller again and saved in non-volatile memory.
STOBER 4 | Commissioning
02/2021 | ID 443046.02
19
4 Commissioning
This chapter describes how to commission your drive system using the DriveControlSuite DS6 software.
For the commissioning, we require that you use a motor in one of the following designs corresponding to your drive
controller:
Drive controller SD6 SC6 SI6
Motor STOBER synchronous servo
motor with optional brake
STOBER synchronous servo
motor with optional brake,
STOBER Lean motor
STOBER synchronous servo
motor with optional brake,
STOBER Lean motor
Encoders EnDat 2.1/2.2 digital
encoder,
HIPERFACE DSL encoder
EnDat 2.2 digital encoder,
HIPERFACE DSL encoder
EnDat 2.2 digital encoder,
HIPERFACE DSL encoder
These motors together with all relevant data for the project configuration are saved in the motor database of
DriveControlSuite as well as in the electronic nameplate. By selecting a corresponding motor, all data is automatically
transmitted to the corresponding parameters. There is no need for complex parameterization of the motor, brake or
encoder.
If you use a different motor type, you must parameterize it manually.
Before you begin commissioning, make sure that the system nodes are hooked up and supplied with control voltage.
You can find more information about installing and commissioning your drive controllers in the corresponding
commissioning instructions.
Information
Always perform the steps included in the following chapters in the specified order!
Some parameters of the DriveControlSuite are interdependent and do not become accessible to you until you have first
configured certain settings. Follow the steps in the specified sequence so that you can finish the parameterization
completely.
4 | Commissioning STOBER
20
02/2021 | ID 443046.02
4.1 Initiating the project
Referencing
Mapping the
axis model
Initiating the
project
To be able to use the functions of the Drive Based synchronous application, you need at least one drive controller of the
SC6, SD6 or SI6 series. Record all drive controllers and axes of your drive system in a project to configure it using
DriveControlSuite.
4.1.1 Projecting the drive controller and axis
Create a new project and project the first drive controller along with the accompanying axis.
Creating a new project
1. Start DriveControlSuite.
2. Click Create new project.
ðThe project configuration window opens and the Drive controller button is active.
Projecting the drive controller
1. Properties tab:
Establish the relationship between your circuit diagram and the drive controller to be projected in DriveControlSuite.
Reference: Specify the reference code (equipment code) of the drive controller.
Designation: Give the drive controller a unique name.
Version: Version your project configuration.
Description: If necessary, specify additional supporting information, such as the change history of the project
configuration.
2. Drive controller tab:
Select the series, device type and firmware version of the drive controller.
3. Option modules tab:
Depending on the drive controller series, various option modules are available for you to select.
Communication module: If the drive controller communicates with a controller over a fieldbus, select the
corresponding communication module.
Terminal module: If you are controlling the drive controller using analog and digital inputs, select the corresponding
terminal module (in addition to the communication module in mixed operation).
Safety module: If the drive controller is part of a safety circuit, select the corresponding safety module.
4. Device control tab:
Device control: Select Drive Based.
Receive process data (Rx), transmit process data (Tx): If you control the drive controller using a fieldbus, select the
fieldbus-specific receive and transmit process data.
  • Page 1 1
  • Page 2 2
  • Page 3 3
  • Page 4 4
  • Page 5 5
  • Page 6 6
  • Page 7 7
  • Page 8 8
  • Page 9 9
  • Page 10 10
  • Page 11 11
  • Page 12 12
  • Page 13 13
  • Page 14 14
  • Page 15 15
  • Page 16 16
  • Page 17 17
  • Page 18 18
  • Page 19 19
  • Page 20 20
  • Page 21 21
  • Page 22 22
  • Page 23 23
  • Page 24 24
  • Page 25 25
  • Page 26 26
  • Page 27 27
  • Page 28 28
  • Page 29 29
  • Page 30 30
  • Page 31 31
  • Page 32 32
  • Page 33 33
  • Page 34 34
  • Page 35 35
  • Page 36 36
  • Page 37 37
  • Page 38 38
  • Page 39 39
  • Page 40 40
  • Page 41 41
  • Page 42 42
  • Page 43 43
  • Page 44 44
  • Page 45 45
  • Page 46 46
  • Page 47 47
  • Page 48 48
  • Page 49 49
  • Page 50 50
  • Page 51 51
  • Page 52 52
  • Page 53 53
  • Page 54 54
  • Page 55 55
  • Page 56 56
  • Page 57 57
  • Page 58 58
  • Page 59 59
  • Page 60 60
  • Page 61 61
  • Page 62 62
  • Page 63 63
  • Page 64 64
  • Page 65 65
  • Page 66 66
  • Page 67 67
  • Page 68 68
  • Page 69 69
  • Page 70 70
  • Page 71 71
  • Page 72 72
  • Page 73 73
  • Page 74 74
  • Page 75 75
  • Page 76 76
  • Page 77 77
  • Page 78 78
  • Page 79 79
  • Page 80 80
  • Page 81 81
  • Page 82 82
  • Page 83 83
  • Page 84 84
  • Page 85 85
  • Page 86 86
  • Page 87 87
  • Page 88 88
  • Page 89 89
  • Page 90 90
  • Page 91 91
  • Page 92 92
  • Page 93 93
  • Page 94 94
  • Page 95 95
  • Page 96 96
  • Page 97 97
  • Page 98 98
  • Page 99 99
  • Page 100 100
  • Page 101 101
  • Page 102 102
  • Page 103 103
  • Page 104 104
  • Page 105 105
  • Page 106 106
  • Page 107 107
  • Page 108 108
  • Page 109 109
  • Page 110 110
  • Page 111 111
  • Page 112 112
  • Page 113 113
  • Page 114 114
  • Page 115 115
  • Page 116 116
  • Page 117 117
  • Page 118 118
  • Page 119 119
  • Page 120 120
  • Page 121 121
  • Page 122 122
  • Page 123 123
  • Page 124 124
  • Page 125 125
  • Page 126 126
  • Page 127 127
  • Page 128 128
  • Page 129 129
  • Page 130 130
  • Page 131 131
  • Page 132 132
  • Page 133 133
  • Page 134 134
  • Page 135 135
  • Page 136 136
  • Page 137 137
  • Page 138 138
  • Page 139 139
  • Page 140 140
  • Page 141 141
  • Page 142 142
  • Page 143 143
  • Page 144 144
  • Page 145 145
  • Page 146 146
  • Page 147 147
  • Page 148 148
  • Page 149 149
  • Page 150 150

Stober Drive Based Synchronous User manual

Type
User manual

Ask a question and I''ll find the answer in the document

Finding information in a document is now easier with AI