MOVI-PLC® Example Project Axis Control / Manuals ... – MOVI-PLC® AxisControl Application Solution 3 Contents Contents 1 General Information 5 1.1 Structure of the safety notes

Drive Technology \ Drive Automation \ System Integration \ Services

MOVI-PLC®

AxisControlSample Project

ManualEdition 05/200811635428 / EN

SEW-EURODRIVE – Driving the world

Manual – MOVI-PLC® AxisControl Application Solution 3

Contents

Contents1 General Information ............................................................................................ 5

1.1 Structure of the safety notes ....................................................................... 51.2 Rights to claim under warranty ................................................................... 51.3 Exclusion of liability..................................................................................... 61.4 Applicable documents................................................................................. 6

2 Introduction ......................................................................................................... 72.1 Objectives ................................................................................................... 72.2 Functionality of the application solution ...................................................... 72.3 System requirements .................................................................................. 8

3 MOVIDRIVE® Control with AxisControl_MDX_SingleAxis .............................. 93.1 MOVIDRIVE® requirements ....................................................................... 93.2 Startup of MOVIDRIVE® with the DIP11B option...................................... 113.3 Opening and starting the project AxisControl_MDX_SingleAxis.pro ........ 123.4 Adapting the AxisControl_MDX_SingleAxis.pro project............................ 153.5 AxisControl_MDX function block............................................................... 173.6 Controlling MOVIDRIVE® via the Application Builder

"Monitor AxisControl" ................................................................................ 20

4 Adding a MOVIDRIVE® Drive to the Project.................................................... 244.1 Task .......................................................................................................... 244.2 Solution ..................................................................................................... 24

5 Integrating an Automated Sequence............................................................... 305.1 Task .......................................................................................................... 305.2 Solution ..................................................................................................... 30

6 AxisControl_MDX_SingleAxis Sample Project .............................................. 406.1 Operating modes ...................................................................................... 406.2 Function blocks ......................................................................................... 406.3 Processing of the function blocks ............................................................. 416.4 Overview of the AxisControl_MDX function block..................................... 436.5 Input and output assignment of the AxisControl_MDX function block ...... 446.6 Description of operating modes ................................................................ 46

7 Adding an Operating Mode for Torque Control ............................................. 507.1 Task .......................................................................................................... 507.2 Solution ..................................................................................................... 50

8 Synchronous Operation with Virtual Encoder as Master............................. 608.1 Startup and parameterization of MOVIDRIVE® ........................................ 618.2 Startup of MOVIDRIVE® with option DIP11B............................................ 618.3 Opening and starting the project AxisControl_MDX_Technology............. 618.4 Adapting the AxisControl_MDX_Technology.pro project .......................... 628.5 Additional settings for synchronous operation .......................................... 638.6 Compiling and starting the project in the PLC Editor ................................ 648.7 Controlling MOVIDRIVE® + virtual encoder via "Monitor AxisControl" ..... 648.8 AxisControlCam_MDX function block ....................................................... 668.9 AxisControlGear_MDX function block....................................................... 69

4 Manual – MOVI-PLC® AxisControl Application Solution

Contents

9 Synchronous Operation with MOVIDRIVE® as Master .................................. 729.1 Adapting the AxisControl_MDX_Technology.pro project .......................... 729.2 Controlling both MOVIDRIVE® inverters via "Monitor AxisControl" .......... 79

10 AxisControl_MDX_Technology Sample Project............................................. 8110.1 Operating modes ...................................................................................... 8110.2 Function blocks ......................................................................................... 8210.3 Description of operating modes ............................................................... 85

11 Data Backup for Connected Inverters............................................................. 8811.1 General notes on data backup.................................................................. 8811.2 Description of operating modes ................................................................ 8911.3 Data Management using global variable interface.................................... 9011.4 Data Management via Application Builder ................................................ 93

12 Frequently Asked Questions ........................................................................... 9612.1 Communication problems between the PLC Editor and MOVI-PLC®....... 9612.2 Controlling the AxisControl_MDX... sample project via PROFIBUS ......... 9812.3 Features and operating principle of the virtual encoder.......................... 101

13 Address List .................................................................................................... 102

Index................................................................................................................. 111


1 Structure of the safety notesGeneral Information

1 General Information1.1 Structure of the safety notes

The safety notes in these operating instructions are structured as follows:

1.2 Rights to claim under warrantyAs a prerequisite to fault-free operation and fulfillment of warranty claims, you must ad-here to the information in the SEW documentation. Consequently, read the operating in-structions and manuals of the respective inverters before you start working with the unit!

Make sure that the operating instructions and manuals are available to persons respon-sible for the plant and its operation, as well as to person who work independently on theunit. You must also ensure that the documentation is legible.

Symbol SIGNAL WORD!Nature and source of hazard.

Possible consequence(s) if disregarded.• Measure(s) to avoid the hazard.

Symbol Signal word Meaning Consequences if disregarded

Example:

General hazard

Specific hazard,e.g. electric shock

HAZARD! Imminent hazard Severe or fatal injuries

WARNING! Possible hazardous situation Severe or fatal injuries

CAUTION! Possible hazardous situation Minor injuries

STOP! Possible damage to property Damage to the drive system or its environment

NOTE Useful information or tip. Simpli-fies the handling of the drive sys-tem


1 Exclusion of liability General Information

1.3 Exclusion of liabilityYou must comply with the information contained in these operating instructions to en-sure safe operation and to achieve the specified product characteristics and perfor-mance features of the inverters. SEW-EURODRIVE assumes no liability for injury topersons or damage to equipment or property resulting from non-observance of theseoperating instructions. In such cases, any liability for defects is excluded.

1.4 Applicable documents• This manual does not replace the detailed operating instructions and the

corresponding manuals.

• Installation and startup of the inverter only by trained personnel observing therelevant accident prevention regulations and the following documents:

– "MOVI-PLC® Programming in the PLC Editor" system manual,

– "MOVIDRIVE® MDX60B/61B" system manual and corresponding manuals,

– "MPLCTec..._MDX, MPLCTecVirtualEncoder Libraries for MOVI-PLC®" manual,

– "MPLCMotion_MDX and MPLCMotion_MX Libraries for MOVI-PLC®" manual,

– "MOVITRAC® B Basic Unit" operating instructions and corresponding manuals,

– MOVIAXIS® system manual and corresponding manuals.


2 ObjectivesIntroduction

2 Introduction2.1 Objectives

The MOVI-PLC® controller combines motion and logic control to provide the completedrive functionality by means of user-friendly function blocks in an environment that canbe programmed in accordance with IEC 61131.

All function blocks for a wide range of drive functions are already integrated in the Axis-Control program for MOVI-PLC®.

With conventional PLC programming, the drive functionality is only a data interface. TheBus Positioning application module, for example, is addressed via global variables in theI/O range of the PLC.

The AxisControl_MDX_SingleAxis.pro and AxisControl_MDX_Tech-nology.pro programs are sample projects, designed like an application module. How-ever, their advantage is that they can be adjusted by the PLC programmer.

The Visu_Axis_control_MDX.mon ApplicationBuilder interface enables simple star-tup without higher-level PLC program. It can be also used to perform diagnostics.

This manual describes the programs for the MOVIDRIVE® inverter as an example. Theprograms for the MOVIAXIS® and MOVITRAC® 07 B inverters offer similar or reducedfunctions.

2.2 Functionality of the application solutionFunctionality of the program AxisControl_MDX_Single Axis.pro:

• Speed control

• Absolute positioning

• Modulo absolute positioning

• Relative positioning

• Jog mode, speed controlled

• Jog mode, position controlled

• Reference travel

Additional functionality of the program AxisControl_MDX_Technology.pro:

• Synchronous operation (direct engagement/disengagement)

• Electronic cam (direct engagement/disengagement)

• Virtual encoder

These functions are completely based on the MPLCMotion_MDX, MPLCTec..._MDXand MPLCTecVirtualEncoder libraries and offer the required basic functions. You caneasily adapt the sample programs to the required functions using this manual and theother applicable documents.

Pi

fkVA

Hz

n

Pi

fkVA

Hz

n


2 System requirements Introduction

2.3 System requirements2.3.1 Software

The following software must be installed on the engineering PC for programming theAxisControl sample project.

• For MOVI-PLC® basic DHP11B Motion Library version 2010r5 or higher

• For MOVI-PLC® advanced DHx41B Motion Library version 2020r2 or higher

An ApplicationBuilder interface is available for execution, control and monitoring of theAxisControl sample project.

This offers the following advantages:

• You can control and monitor each instance of the AxisControl function blockseparately.

• You can check the electrical connection, hardware and communicationindependently of the application program.

• For executing the AxisControl sample project, no programming experience isrequired.

2.3.2 HardwareThe following units must be available for executing the AxisControl sample project:

• MOVIDRIVE® 60B/61B inverter with firmware version 824 854 1.16 or higher

• MOVITRAC® B inverter with firmware version 1820 230 6.13 or higher

• Synchronous servomotors or asynchronous motors with or without encoderfeedback.

Pi

fkVA

Hz

n

Pi

fkVA

Hz

n


3 MOVIDRIVE® requirementsMOVIDRIVE® Control with AxisControl_MDX_SingleAxis

3 MOVIDRIVE® Control with AxisControl_MDX_SingleAxis3.1 MOVIDRIVE® requirements

In order to control the MOVIDRIVE® inverter with a MOVI-PLC®, you have to start it upfirst with the "DriveStartUp for MOVI-PLC®" startup assistant. Connect theMOVIDRIVE® inverter to the engineering PC via the serial RS-485 interface.

Start the startup assistant as follows:

1. Right-click on [MDX61B0015...].

2. Select [Technology Editors] from the context menu.

3. Select [Drive Startup for MOVI-PLC®] from the submenu.

802992139

00

I


3 MOVIDRIVE® requirements MOVIDRIVE® Control with AxisControl_MDX_SingleAxis

Then perform the 5 startup steps displayed in the figure below:

The MOVIDRIVE® inverter is visible at the respective CAN line if the following applies:

• Startup has been performed successfully with the "DriveStartup for MOVI-PLC®"startup assistant,

• The SBus address has been assigned correctly,

• And the network has been scanned again in MOVITOOLS® MotionStudio.

803406859

NOTES• For detailed information on startup, refer to chapter "MOVIDRIVE® startup with the

DIP11B option" (see page 11) in the "MPLCMotion_MDX and MPLCMotion_MX for MOVI-PLC®" manual.

• Consider the organization of the different SBus addresses of the SBus stations. The SBus address of the drive inverter must be different from the SBus address of the MOVI-PLC® controller (default: 0).

00

I


3 Startup of MOVIDRIVE® with the DIP11B optionMOVIDRIVE® Control with AxisControl_MDX_SingleAxis

The MOVIDRIVE® inverter on the CAN1 line:

3.2 Startup of MOVIDRIVE® with the DIP11B optionIf the drive is to perform positioning task using a SSI absolute encoder, the drive and theDIP11B absolute encoder card must be started up in the MOVITOOLS® via DIP startup.

803469195

[1] MOVI-PLC® at the Ethernet interface [2] MOVIDRIVE® routed through at the CAN1 interface of the MOVI-PLC® controller[3] MOVIDRIVE® at the COM1 interface of the engineering PC via RS-485

[1]

[2]

[3]

NOTEFor detailed information on startup of an SSI absolute encoder, refer to the"MOVIDRIVE® MDX61B Absolute Encoder Card DIP11B" manual.

00

I


3 Opening and starting the project AxisControl_MDX_SingleAxis.pro MOVIDRIVE® Control with AxisControl_MDX_SingleAxis

3.3 Opening and starting the project AxisControl_MDX_SingleAxis.pro3.3.1 Creating a new project in the PLC Editor

Proceed as follows to create a new project:

1. Right-click on MOVI-PLC®.

2. Select [Programming] from the context menu.

3. Select [New PLC Editor project...] from the submenu.

804057739

00

I


3 Opening and starting the project AxisControl_MDX_SingleAxis.proMOVIDRIVE® Control with AxisControl_MDX_SingleAxis

The "Create PLCProject..." window is displayed. It shows a list of the library versionsthat are compatible with the MOVI-PLC® firmware:

1. Select the relevant directory on the hard drive of the engineering PC.

2. Enter a file name for the new PLC Editor project.

3. Select the required motion library.

4. After selecting the relevant directory and assigning a file name, select an AxisControlproject:

• AxisControl_MDX_SingleAxis.pro for simple control of motor axes or

• AxisControl_MDX_Technology.pro for applications with synchronousoperation or cam.

804617739

[1] Directory on the hard drive of the engineering PC[2] File name of the new PLC Editor project[3] Selection of the required motion library

[1]

[2]

[3]

00

I


3 Opening and starting the project AxisControl_MDX_SingleAxis.pro MOVIDRIVE® Control with AxisControl_MDX_SingleAxis

Upon confirming with [OK], the PLC Editor opens a complete PLC Editor project that canbe compiled without errors.

3.3.2 Compiling and starting a new project1. Select the menu command [Project] / [Compile] in the PLC Editor to compile the mod-

ified project.

2. Select the command [Online] / [Login] to load the project into the MOVI-PLC® con-troller.

3. To start the program, press function key <F5> or select the menu command [Online]/ [Start] after downloading the project into the controller.

The MOVIDRIVE® inverter can now be controlled via the global structure variablegAxisInterfaceIn_MDX[x]. This structure variable contains control signals such ascontroller inhibit, enable, reset, operating mode, etc.

For testing purposes, you can also control the motor axis through an Application Builderinterface.

805521803

NOTEFor detailed information, refer to chapter "Controlling MOVIDRIVE® via the ApplicationBuilder Axis Control Monitor" (see page 20).

00

I


3 Adapting the AxisControl_MDX_SingleAxis.pro projectMOVIDRIVE® Control with AxisControl_MDX_SingleAxis

3.4 Adapting the AxisControl_MDX_SingleAxis.pro projectThe sample project has been designed for 3 motor axes. If the number of controlledmotor axes changes, you have to adapt the control configuration:

Deleting motor axes:1. Right-click on [MOVIDRIVE].

2. Select [Delete] from the context menu.

Adding a motor axis:1. Right-click on [Can1 enabled].

2. Select [Append subelement] from the context menu.

3. Select [MOVIDRIVE MDX B].

Adapting the control configuration:Subsequently, adjust the module parameters (SBus address).

If more than 3 motor axes are to be controlled, add corresponding networks by callingup another instance of the AxisControl_MDX function block and parameterizing it.

798772235

NOTEFor non-existent motor axes, no instance of the AxisControl_MDX function blockmay be called up.

Delete the respective networks from the PLC_PRG_SingleAxis main program.

00

I


3 Adapting the AxisControl_MDX_SingleAxis.pro project MOVIDRIVE® Control with AxisControl_MDX_SingleAxis

You also have to adjust the Configuration_MDX function block:

1. Delete the initialization statements for non-existent motor axes.

2. If using more than 3 motor axes, add initialization statements for the respective motoraxes.

NOTEFor detailed information, refer to chapter "Adding a MOVIDRIVE® drive to the project"(see page 24).

805782027

NOTEFor detailed information on the modification of the existingAxisControl_MDX_SingleAxis.pro project, refer to the following chapters.

00

I


3 AxisControl_MDX function blockMOVIDRIVE® Control with AxisControl_MDX_SingleAxis

3.4.1 Compiling and starting a new project

1. Select the menu command [Project] / [Compile] in the PLC Editor to compile theproject.



You can now control the MOVIDRIVE® inverter via the global structure variablegAxisInterfaceIn_MDX[x]. This structure variable contains control signals such ascontroller inhibit, enable, reset, operating mode, etc.

For testing purposes, you can also control the motor axis through an Application Builderinterface (Visu_AxisControl_MDX.mon).

3.5 AxisControl_MDX function blockIn the PLC_PRG_SingleAxis main program, one instance of the AxisControl_MDXfunction block is called up for each motor axis. The input or output signals of the functionblock have the following meaning:

3.5.1 Input signalsThe behavior of the AxisControl_MDX function block is dependent on the followinginput signals:

NOTEFor detailed information, refer to chapter "Controlling MOVIDRIVE® via the ApplicationBuilder Monitor AxisControl" (see page 20).

Input signal Type Meaning

HControl BOOL If this input signal is set to TRUE, the motor axis is con-trolled via H variables from the Application Builder inter-face.

Node CAN_NODE This input signal sets the relevant MOVI-PLC® CAN bus node.

SBUS_Address UNIT This input signal sets the SBus address of the inverter.

InverterInhibit BOOL This input signal INHIBITS the INVERTER (status display 1 at the inverter).

InverterEnable BOOL This input signal enables the inverter. It changes to the state with status display 5 or A.

Reset BOOL A RESET is performed at the respective inverter with a rising edge of this input signal.

AxisMode ENUM_AXIS-MODE

Selecting an operating mode: 0: AM_DEFAULT1: AM_VELOCITY2: AM_POSITIONING3: AM_POSITIONINGMODULO4: AM_POSITIONINGRELATIVE5: AM_JOG_56: AM_JOG_A7: AM_HOMING8: AM_CAMING9: AM_GEARING

00

I


3 AxisControl_MDX function block MOVIDRIVE® Control with AxisControl_MDX_SingleAxis

Start BOOL This input signal starts the movement of the selected operating mode.

JogPos BOOL In the jog operating mode, the motor axis moves in the positive direction (CW).

JogNeg BOOL In the jog operating mode, the motor axis moves in the negative direction (CCW).

Position DINT Target position for the Positioning operating mode

Velocity DINT Setpoint speed for the operating modes speed control, jog and positioning.

Acceleration DINT This input signal sets the acceleration ramp of the respec-tive operating mode (time in [ms] based on a setpoint step change of 3000 min-1).

Deceleration DINT This input signal sets the braking ramp of the respective operating mode (time in [ms] based on a setpoint step change of 3000 min-1).

ModuloMode UNIT Travel strategy for the operating mode AM_POSITIONINGMODULO: 0: Off1: Short distance 2: CW 3: CCW

AxisConfiguration ST_AxisConfigu-ration_MDX

This input variable transfers the configuration parameters set in FB Configuration_MDX to the relevant motor axis.


00

I


3 AxisControl_MDX function blockMOVIDRIVE® Control with AxisControl_MDX_SingleAxis

3.5.2 Output signals

The AxisControl_MDX function block provides the following output signals:

Output signal Type Meaning

Connected BOOL Connection to the motor axis is established; initialization of the MC_ConnectAxis_MDX function block completed

RequestedAxisMode ENUM_AXIS-MODE

Requested axis mode corresponds to the AxisMode input signal

ActualAxisMode ENUM_AXIS-MODE

Actually activated axis mode: If RequestedAxisMode and ActualAxisMode are different, movement in the current operating mode is stopped. After the axis has come to a standstill, it switches to the new operating mode.

Powered BOOL The output signal shows whether the motor axis is enabled.• TRUE: Motor axis is enabled. Inverter status with

status display A or 5. • FALSE: Motor axis is not enabled. Inverter status with

status display 1 or 2.

Done BOOL The output signal Done indicates whether the individual motion function blocks of the selected operating mode have been executed.• TRUE: e.g. target position or setpoint speed reached. • FALSE: Target position or setpoint speed not reached

yet.

Active BOOL The Active output signal shows whether the motor axis is turning to reach the target position or the speed setpoint, for example. • TRUE: Motor axis is turning, but target position or

speed setpoint not reached yet.• FALSE: Motor axis has reached the target position

and is standing still, or turns at setpoint speed.

Stopped BOOL The output signal Stopped indicates that the motor axis has been stopped.

InverterFault BOOL The output signal InverterFault indicates that the inverter has detected a fault.

InverterFaultStatus DWORD The output signal shows the fault code of the inverter of the motor axis

FBError BOOL The output signal indicates an error in a motion function block.

FBErrorID DWORD The output signal shows the error code of the faulty motion function block.Note:For information on the error codes, refer to chapter "Error identifier" in the library manual or to the "MPLCSystem_ErrorCodes.lib" library in the PLC Editor.

Axis AXIS_REF Logical address of the motor axis. Is created by the respective MC_ConnectAxis_MDX function block.

PLCopenState MC_PLCopen-State

The output signal shows the current PLCopenState of the motor axis.

InverterInfos MC_InverterInfos_MDX

The output signal gives information about the inverter.

InverterData MC_InverterData_MDX

The output signal shows the current actual values of the inverter.

00

I


3 Controlling MOVIDRIVE® via the Application Builder "Monitor AxisControl" MOVIDRIVE® Control with AxisControl_MDX_SingleAxis

3.6 Controlling MOVIDRIVE® via the Application Builder "Monitor AxisControl"Monitor AxisControl is an Application Builder user interface integrated inMOVITOOLS® MotionStudio. This user interface is used for controlling a MOVIDRIVE®

inverter.

Open this user interface as follows:

1. Right-click on [MOVI-PLC...].

2. Select [Diagnostics] from the context menu.

3. Select [Monitor AxisControl].

806171275

00

I


3 Controlling MOVIDRIVE® via the Application Builder "Monitor AxisControl"MOVIDRIVE® Control with AxisControl_MDX_SingleAxis

The following window is displayed:

The standard operating mode of this user interface is "monitoring". In this mode, onlymonitoring is possible. Control of the motor axis is not possible.

To switch the user interface to "controlling", set the gAxisInterfaceIn_MDX[1].HControlvariable of the motor axis to TRUE. In this example, this is the axis with LogAdr 1.

806194187

00

I


3 Controlling MOVIDRIVE® via the Application Builder "Monitor AxisControl" MOVIDRIVE® Control with AxisControl_MDX_SingleAxis

Proceed as follows:

1. Double-click on the HControl variable in the PLC_PRG_SinlgeAxis program of thePLC Editor when logged in. The value TRUE is displayed.

2. Use the key combination <Ctrl> + <F7> or the menu command [Online] / [Writevalues] to enter the value. The variable text TRUE is displayed in blue.

In the Monitor AxisControl Application Builder window, the display changes to:

806220427

806392843

00

I


3 Controlling MOVIDRIVE® via the Application Builder "Monitor AxisControl"MOVIDRIVE® Control with AxisControl_MDX_SingleAxis

The operating mode changes to "controlling". The "set point" fields are white for editing.Click on the [send] button to adopt the changes in the project.

3.6.1 Application exampleThe MOVIDRIVE® inverter is controlled with following the drive parameters:

In order to operate the motor axis with the set drive parameters,

1. Click on the [inverter enable] button and then on [send]

2. Click on the [start] button and then on [send]

• Operating mode: Speed control

• Setpoint speed: 500 rpm

• Acceleration ramp: 2000 ms

• Braking ramp: 1000 ms

806495243

NOTEIn an emergency, click on the [stop axis] button to stop the motor axis. It is not neces-sary to click on [send] for this.

00

I


4 Task Adding a MOVIDRIVE® Drive to the Project

4 Adding a MOVIDRIVE® Drive to the Project4.1 Task

3 motor axes are created as standard when creating a newAxisControl_MDX_SingleAxis.pro project in the PLC Editor.

A fourth axis is to be added. The MOVIDRIVE® inverter is to control this motor axis.

4.2 SolutionThe solution includes the following steps:

4.2.1 Starting up and parameterizing the 4 MOVIDRIVE® invertersThe 4 MOVIDRIVE® inverters are started up using the DriveStartup assistant forMOVI-PLC®.

1. Connect the inverters individually via RS-485 with MOVITOOLS® MotionStudio.

2. It is essential that you set different SBus addresses and the same baud rates (e.g.SBus addresses: 1, 2, 3, 4 and baud rate 500 kBaud each).

3. You can now access the 4 inverters connected to the CAN1 node through the routingfunction of MOVI-PLC®.

4.2.2 Creating a new AxisControl_MDX_SingleAxis.pro MOVI-PLC® project 1. Create a new AxisControl_MDX_SingleAxis.pro project as described in

chapter "Opening and starting the project AxisControl_MDX_SingleAxis.pro" (seepage 12).

00

I


4 SolutionAdding a MOVIDRIVE® Drive to the Project

4.2.3 Integrating a 4th MOVIDRIVE® inverter

3 subelements are already attached to the control configuration of the project. Add afourth element as follows:

1. Right-click on [Can1 enabled].


3. Select [MOVIDRIVE MDX B...].

4. In the [Module parameter] tab, set the SBus address to 4.

5. Quit the control configuration.

808728715

808772491

00

I


4 Solution Adding a MOVIDRIVE® Drive to the Project

4.2.4 Adding a new instance of the AxisControl_MDX function block in the main program

Proceed as follows to add another network to PLC_PRG_SingleAxis:

1. Copy network 5 and add it as a new network.

2. Change the following entries to "4" in the sixth network.

808817419

[1]

[2] [3]

[1] SBus address[2] Name of instance[3] ARRAY number

00

I



4.2.5 Changing the Configuration_MDX (FB) configuration module

Change the following in the Configuration_MDX (FB) configuration module for thefourth MOVIDRIVE® inverter:

1. Copy the initialization of the 3rd inverter and paste it to the program.

2. Adjust the configuration for the 4th inverter.

808894219

00

I


4 Solution Adding a MOVIDRIVE® Drive to the Project

4.2.6 Transferring changes to the current MOVI-PLC® program and testing it

1. Press the function key <F11> or select the menu command [Project] / [Compile] tocompile the modified project.

2. Select [Online] / [Login] to load the project into the controller.

You can now control and test the new project via the MonitorAxisControl.monApplication Builder user interface.

3. Use the AxisControl_MDX function block to set the H_Control input to TRUE inthe PLC_PRG_SingleAxis program in the network of the 4th axis.

You can determine the logical address of the 4th axis from the global variablegAxisInterfaceOut_MDX[4].Axis.

1. Use the Monitor AxisControl.mon Application Builder user interface to test thefunction as described in chapter "Controlling MOVIDRIVE® via Application BuilderMonitor AxisControl" (see page 20).

809055499

[1] Logical address of the 4th motor axis

[1]

00

I



809104139

[1]

[1] Selecting the motor axis with logical address 4

00

I


5 Task Integrating an Automated Sequence

5 Integrating an Automated Sequence5.1 Task

An automatic sequence for controlling a MOVIDRIVE® inverter is to be integrated intothe AxisControl_MDX_SingleAxis.pro program.

The automatic sequence is started by setting the input signal at the input terminal (DI07)of the inverter.

The drive is first referenced and then runs through a reversing program as follows:

• Travelling cyclically to a certain EndPosition and

• Travelling back to the StartPosition after a delay.

The global variable gAxisInterfaceIn_MDX[1]...... specifies the drive parameters Posi-tioningSpeed and Ramps.

Local variables in the PLC_PRG_SingleAxis program specify the StartPosition, theEndPosition and the Delay between the movements.


5.2.1 Step 1: Starting up and parameterizing the MOVIDRIVE® drive inverterThe MOVIDRIVE® inverter is started up using the "DriveStartup for MOVI-PLC®" assis-tant.

1. Connect the inverter via RS-485 to MOVITOOLS® MotionStudio.

2. It is essential that you set a SBus address that is different from that of theMOVI-PLC® and a baud rate that is the same as the MOVI-PLC® baud rate.

Example:

• Default setting for CAN1 of MOVI-PLC®: SBus address: 0, baud rate: 500 kBaud

• MOVIDRIVE®: SBus address: 1, baud rate: 500 kBaud

5.2.2 Step 2: Creating a new AxisControl_MDX_SingleAxis.pro MOVI-PLC® project 1. Use the project wizard to create a new AxisControl_MDX_SingleAxis.pro

project, see chapter "Opening and starting AxisControl_MDX_SingleAxis.pro" (seepage 12).

00

I


5 SolutionIntegrating an Automated Sequence

5.2.3 Step 3: Deleting inverters from the control configuration that are not used

Proceed as follows to remove the two unneeded MOVIDRIVE® inverters from the con-trol configuration:

1. Right-click on the two inverters that are not needed and select [Delete] from the con-text menu.

5.2.4 Step 4: Removing both AxisControl_MDX function blocks from the main programYou have to remove the two AxisControl_MDX function blocks of the unneeded in-verters from the PLC_PRG_SingleAxis main program:

1. Right-click on the network number of the network to be removed and select [Delete]from the context menu.

812889611

813031179

[1] Network number

[1]

00

I


5 Solution Integrating an Automated Sequence

5.2.5 Step 5: Deleting the configuration of the inverters that are not needed

You have to remove the configuration of the two unneeded inverters from theConfiguration_MDX function block:

1. Highlight the configuration lines of the two unneeded inverters and delete them.

813966859

[1] Configuration lines

[1]

00

I



5.2.6 Step 6: Adding a program for an automatic sequence in the "Object Organizer"

1. Click in the "Object Organizer" with the right mouse button.

2. Select [Insert object] from the context menu.

3. Select:

• Type of module: "Program"

• Language of module: "SFC"

4. Enter the name of the module: "P_AutomaticSequence".

The automatic sequence is programmed with a sequencer here as an example (SFC:sequential function chart). This programming language is best for realizing step-by-stepprocessing. The individual actions and transitions can be programmed in other program-ming languages. To proceed from one action to the next, the transition in between mustbe logically TRUE.

814084235

00

I



5.2.7 Step 7: Programming the P_AutomaticSequence program

You can program the P_AutomaticSequence program in SFC (sequential functionchart) as follows:

814201995

[1] Exit action[2] Entry action

[1]

[2]

00

I



Program the individual actions as follows:

InitThe "Init" action is programmed in ST (structured text).

Set enable and the start signal to FALSE:

Prepare_for_HomingThis action queries whether the drive is ready for homing:

HOMINGThe action sequence for homing includes:

• Enabling the inverter,

• Setting the operating mode to homing (AM_HOMING).

The start signal for homing is issued if

• The operating mode is set to AM_HOMING and

• The other conditions at the AND gate are fulfilled.

The transition (bDoneHoming) to the next action is set to TRUE for one cycle by theR_TRIG function block if

• The drive is referenced, i.e. the module issues the signal Done, and

• The input for starting the entire sequence is still pending.

Querying the edge change of the gAxisInterface_Out_MDX[1].Done signal is important.The same signal is used in the subsequent actions for the transition conditions of thedrive moments.

Without querying the edge change, the transition condition for the following action wouldalready be fulfilled with the pending gAxisInterface_Out_MDX[1].Done signal.

814359051

814414859

00

I



Action:

In the exit action, the start signal is reset to FALSE:

WaitingTime1_1s_StartPositionThis action ensures that the drive waits for a certain time in the start position. A timer iscalled up for delaying activation.

The waiting time until the next action MOVE_TO_ENDPOS is enabled is set by the Wai-tingTime variable. The timer must be reset with an entry action "E" so that it starts eachtime anew. This is accomplished by calling up the timer with IN := FALSE:

Entry action:

Action:

814470923

814987531

815310603

815043339

00

I



MOVE_TO_ENDPOSWith this action, the drive travels to a specified end position.

The operating mode absolute positioning AM_POSITIONING is used.

The entry action includes the following steps:

• Transferring the travel parameters positioning speed and positioning ramps to therespective variables:

• gAxisInterfaceIn_MDX[1].Velocity,

• gAxisInterfaceIn_MDX[1].Acceleration and

• gAxisInterfaceIn_MDX[1].Deceleration

• Writing the End position variable to the target position gAxisInterface-In_MDX[1].Position of the AM_POSITIONING operating mode.

The operating principle is the same as for the "Homing" action.

The start signal is set if:

• The current operating mode is AM_POSITIONING and

• The state of the AND gate is TRUE.

The transition (bDoneEndPosition) to the next action is set for one cycle if

• The target position (Done) has been reached and

• The input signal for starting the entire sequence is still pending.

In the exit action, the start signal is reset to FALSE.

Entry action:

815383179

00

I



Action:

Exit action:

WaitingTime2_1s_EndPositionThis action keeps the drive in its current position after reaching the end position. Thewaiting time is set with the Waiting Time variable. The operating principle is the sameas for action "WaitingTime1_1s_StartPosition".

MOVE_TO_STARTPOSThe operating principle is the same as for action "MOVE_TO_ENDPOS".The StartPosition variable is transferred in the entry action.

When the drive has reached the start position again,

• The bDoneStartPosition transition is set to TRUE for one cycle

• And the program jumps to the "WaitingTime1_1s_StartPosition" action to run throughagain.

If the signal at the input terminal for starting the entire sequence (DI07) is revoked duringthe automatic sequence,

• The SFC is reset to the Init step,

• The Init step is processed and

• In the Init step, the inverter enable and the start signal are set to FALSE.

818666123

821898635

00

I



5.2.8 Step 8: Calling up the P_AutomaticSequence program in the main program

Network 3 is inserted between the call of the Configuration_MDX function block andthe AxisControl_MDX function block.

In this network, the defined P_AutomaticSequence program is called. The input vari-ables of the program are entered and defined as shown in the screen shot.

5.2.9 Step 9: Testing the functionality of the automatic sequenceIf the project can be compiled without errors, it is transferred to the MOVI-PLC® control-ler and started.

In the PLC_PRG_SingleAxis program, the variables for the travel parameters of theP_AutomaticSequence program are pre-initialized in the variable declaration. If nec-essary, you can change them with the [Write values] function.

You can test the functionality of the automatic sequence by activating theibMDX1_StartSequence input signal (input terminal DI07 on MOVIDRIVE®).

822421387

00

I


6 Operating modes AxisControl_MDX_SingleAxis Sample Project

6 AxisControl_MDX_SingleAxis Sample Project6.1 Operating modes

When opening the AxisControl_MDX_SingleAxis project, the user is offered thebasic functions for controlling several MOVIDRIVE® inverters. The following operatingmodes are available:

• Speed control


• Modulo absolute positioning


• Jog mode, speed controlled

• Jog mode, position controlled

• Reference travel

• Synchronous operation (only with the application version)

• Electronic cam (only with the application version)

6.2 Function blocksThe AxisControl_MDX_SingleAxis project offers the following function blocks:

The task configuration [Resources] / [Task configuration] shows that thePLC_PRG_SingleAxis main program is called cyclically by a free-running task.

1030032267

899402507

Pi

fkVA

Hz

n

Pi

fkVA

Hz

n


6 Processing of the function blocksAxisControl_MDX_SingleAxis Sample Project

In the control configuration [Resources] / [Control configuration], 3 axes are connectedto the CAN1 system bus as standard. Their SBus addresses are 1, 2 and 3.

6.3 Processing of the function blocksIn the 2nd network of the PLC_PRG_SingleAxis main program, the instance of theConfiguration_MDX function block is called.

In this function block, after the first download and the start of the program, differentparameters are set to an initialization value once for each connected axis.

In the following networks, one instance of the AxisControl_MDX function block iscalled up for each axis.

791207947

791838219

Pi

fkVA

Hz

n

Pi

fkVA

Hz

n


6 Processing of the function blocks AxisControl_MDX_SingleAxis Sample Project

In the AxisControl_MDX function block, the CommunicationInSignals_MDXcommunication module is called first. Here is mainly determined whether the input sig-nals of the module are connected with the global structure variablegAxisInterfaceIn_MDX[x].... or with the internal H variables.

In the following networks, other function blocks are called with the following functions:

Subsequently, the individual function blocks are called with the possible operatingmodes:

In the following networks 17 - 24, the output signals of the AxisControl_MDX functionblocks are created:

• Done

• Active

• Stopped

• InverterError

• InverterFaultStatus

• FBError

• FBErrorID

The CommunicationOutSignals_MDX communication module is called in the lastNetwork (25). Here, the output variables of the AxisControl_MDX function block aretransferred to the global structure variable gAxisInterfaceOut_MDX[x] or internal Hvariables.

Function block Function

MC_GetInverterInfo_MDX Reading out settings and information of the inverter

MC_InitialConfig_MDX Activating communication features and functions of the inverter

MC_ConnectAxis_MDX Cyclical communication with the inverter

MC_Power_MDX Enabling the inverter

MC_Reset_MDX Resetting the inverter

MC_SetJerk_MDX Activating jerk limitation and setting the jerk time of the inverter positioning modules

Function block Function

AxisModeDefault_MDX No valid mode selected

AxisModeVelocity_MDX Speed-controlled operation of the motor axis

AxisModePositioning_MDX Absolute positioning of the motor

AxisModePositioningModulo_MDX Modulo positioning of the motor axis

AxisModeJog5_MDX Jog mode, speed controlled

AxisModeJogA_MDX Jog mode, position controlled

AxisModeHoming_MDX Homing the motor axis

AxisModePositioningRelative_MDX Absolute positioning of the motor

NOTEFor information on these output signals, refer to chapter "AxisControl_MDX functionblock" (see page 17).

Pi

fkVA

Hz

n

Pi

fkVA

Hz

n


6 Overview of the AxisControl_MDX function blockAxisControl_MDX_SingleAxis Sample Project

6.4 Overview of the AxisControl_MDX function blockThe following figure shows the functions of the AxisControl_MDX function block:

792333707

PLC_PRG

H_V

AR

GLO

BA

L_VA

R

fbAxisControl_MDX1

Axis_Control_MDX

Configuration_MDX

CommunicationOutSignals_MDX

CommunicationInSignals_MDX

MC_GetInverterInfos_MDX

MC_InitialConfig_MDX

MC_Power_MDXMC_Reset_MDX

MC_ConnectAxis_MDX

AxisModeVelocity_MDX

AxisModePositioning_MDX

AxisModePositioningRelative_MDX

HControlTRUE

FALSE

fbAxisControl_MDX2

Axis_Control_MDX

CommunicationOutSignals_MDX

CommunicationInSignals_MDX

MC_GetInverterInfos_MDX

MC_InitialConfig_MDX

MC_Power_MDXMC_Reset_MDX

MC_ConnectAxis_MDX

AxisModeVelocity_MDX

AxisModePositioning_MDX

AxisModePositioningRelative_MDX

HControlTRUE

FALSE

ApplicationBuilder

Pi

fkVA

Hz

n

Pi

fkVA

Hz

n


6 Input and output assignment of the AxisControl_MDX function block AxisControl_MDX_SingleAxis Sample Project

6.5 Input and output assignment of the AxisControl_MDX function blockThe input and output assignment of the AxisControl_MDX function block is trans-ferred to global structure variables (gAxisInterfaceIn_MDX[x] andgAxisInterfaceOut_MDX[x]). The structure variables are defined as follows:

Open the window as follows:

[Resources] / [Global variables] / [AxisControl_MDX] / [GlobalVar_AxisControl_MDX]

The following figure shows the structure of the function blocks:

• ST_AxisInterfaceInType_MDX and

• ST_AxisInterfaceOutType_MDX.

792371979

792385035

Pi

fkVA

Hz

n

Pi

fkVA

Hz

n


6 Input and output assignment of the AxisControl_MDX function blockAxisControl_MDX_SingleAxis Sample Project

The comment texts describe the variables.

792409611

NOTEFor detailed information on the meaning of the variables, refer to chapter"AxisControl_MDX function block" (see page 17).

Pi

fkVA

Hz

n

Pi

fkVA

Hz

n


6 Description of operating modes AxisControl_MDX_SingleAxis Sample Project

6.6 Description of operating modesThis manual only describes the operating mode AM_POSITIONING as an example forall other operating mode. The other operating modes have the same or a similar struc-ture and differ only in the internally used motion function blocks.

6.6.1 Absolute positioning (AM_POSITIONING)Description This operating mode is used for positioning the motor axes. Position specification is ab-

solute. When the input signal Start = TRUE, the changes at the dynamic inputs areadopted immediately.

Prerequisite The motor axis must be referenced!

Input signals The behavior of the AxisControl_MDX_SingleAxis function block is dependent onthe following input signals:

NOTEFor detailed information on the motion function blocks, refer to the "MPLCMotion_MDXand MPLCMotion_MX Libraries for MOVI-PLC®" manual.


Enable BOOL If this input signal is set to TRUE, the operating mode AM_POSITIONING is enabled and processed.

Start BOOL This input signal starts the movement of the selected motor axis.

Position DINT This input signal specifies the target position.

Velocity DINT This input signal sets the positioning speed [rpm].

Acceleration DINT This input signal sets the positioning ramp UP (time in [ms] based on a setpoint step change of 3000 rpm).

Deceleration DINT This input signal sets the positioning ramp DOWN (time in [ms] based on a setpoint step change of 3000 rpm).


PLCopenState MC_PLCopenState

This input signal transfers the PLCopenState of the inverter to the function block.


Requested axis mode – is required for internal operating mode switching.


Actually active axis mode – is required for internal operat-ing mode switching.

Pi

fkVA

Hz

n

Pi

fkVA

Hz

n


6 Description of operating modesAxisControl_MDX_SingleAxis Sample Project

Output signals The AxisControl_MDX_SingleAxis function block provides the following outputsignals:

If the current operating mode is AM_POSITIONING, the input signal Enable is set toTRUE. The operating mode is changed in the function block of the operating mode thathas been active last. If predefined conditions are fulfilled, the current operating mode isequated there with the requested operating mode. If the Enable input signal is not set toTRUE, the AxisModePositioning_MDX function block is exited with the RETURN pro-gram command.

The movement to a new target position is started with the Start input signal. The SEWmotion module MC_MoveTargetPosition_MDX is enabled.

The logic for changing the operating mode is programmed in network 3:

The operating mode can only be changed if the drive is in STANDSTILL.

The newly selected operating mode (RequestedAxisMode) is adopted as current oper-ating mode (ActualAxisMode) if

• The movement has been started (SetSpeicher bFlagStartet)

• And the SEW motion module has been stopped or the movement has been aborted(output signal Stopped or CommandAborted)

If the movement has not been started yet (ResetSpeicher bFlagStartet), a newly se-lected operating mode (RequestedAxisMode) is adopted directly as current operatingmode (ActualAxisMode).


InPosition BOOL This output signal shows that the motor axis has reached the target position.

Active BOOL This output signal shows that the movement of the motor axis has been started, but the actual position value has not reached the target position yet.


Error BOOL The output signal indicates an error in an internal motion function block.

ErrorID DWORD The output signal shows the error code of the faulty motion function block. Note:For information on the error codes, refer to chapter "Error identifier" in the library manual or to the MPLCSystem_ErrorCodes.lib library in the PLC Editor.

NOTEFor detailed information, refer to the "MPLCMotion_MDX and MPLCMotion_MX Librar-ies for MOVI-PLC®" manual.

Pi

fkVA

Hz

n

Pi

fkVA

Hz

n


6 Description of operating modes AxisControl_MDX_SingleAxis Sample Project

6.6.2 Speed control (AM_VELOCITY)Description In this operating mode, the motor axis is operated in a speed-controlled endless move-

ment. It can also be used for motor axes without encoder feedback.

6.6.3 Absolute modulo positioning (AM_POSITIONINGMODULO)Description This operating mode is used for positioning the motor axes in endless operation. In this

operating mode, drifting of the actual position is avoided even for infinite gear unit ratiofactors. Position specification is absolute.

To realize applications with a cycle distance of 360°, the Start input signal must be tog-gled. A rotation of the motor axis of 360° corresponds to 216 increments.

Prerequisite The motor axis must be referenced!

6.6.4 Relative positioning (AM_POSITIONINGRELATVE)Description This operating mode is used for relative positioning of the motor axis. Position specifi-

cation is relative. When the input signal Start = TRUE, the changes at the dynamic inputsare adopted immediately.

This operating mode requires an edge change of the Start input signal to move the motoraxis over a specified distance.

Prerequisite None

6.6.5 Jog mode, speed controlled (AM_JOG_5)Description This operating mode is used for jogging the motor axis in both directions of rotation. Jog

mode is subject to speed control. The inverter is in n-control operating status (status dis-play 5). Existing software limit switches are not evaluated.

794180875

Pi

fkVA

Hz

n

Pi

fkVA

Hz

n


6 Description of operating modesAxisControl_MDX_SingleAxis Sample Project

6.6.6 Jog mode, position controlled (AM_JOG_A)Description This operating mode is used for jogging the motor axis in both directions of rotation. Jog

mode is subject to position control. The inverter is in Technology option operating status(status display A). Existing software limit switches can be used optionally with the usualmonitoring functions if the motor axis is referenced.

If the software limit switches are used, the travel range is limited to 3 x position windows(P922) before the software limit switches. Endless operation is possible without softwarelimit switches and if the motor axis is not referenced.

6.6.7 Homing (AM_HOMING)Description This operating mode is used for referencing the motor axis. The values set in the param-

eters P900ff are used for this. The module MC_SetHomeParameter_MDX can be usedto change these parameters in the IEC program. This module is not included in the stan-dard version of the AxisControl_MDX_SingleAxis.pro project.

Pi

fkVA

Hz

n

Pi

fkVA

Hz

n


7 Task Adding an Operating Mode for Torque Control

7 Adding an Operating Mode for Torque Control7.1 Task

Another operating mode is to be added to an existingAxisControl_MDX_SingleAxis.pro project.

The following conditions are to apply to this operating mode:

• The drive is subject to torque control, for which the user can specify a limit torquewith a variable.

• The drive is speed-controlled in principle, but it is to be operated permanently at thespecified torque limit. This means the drive must always be assigned a speedsetpoint that is larger than the drive's actual value. The actual value can never reachthe setpoint value, since the drive is always restricted by its torque limit (P304).

• The speed monitoring function (P500) of the inverter must be disabled.


7.2.1 Starting up and parameterizing the MOVIDRIVE® invertersIf additional MOVIDRIVE® inverters are used, you have to start them up using the"DriveStartup for MOVI-PLC®" assistant:

1. To do so, connect the inverters individually via RS-485 with MOVITOOLS®

MotionStudio.

2. It is essential that you set different SBus addresses and the same baud rates (e.g.SBus addresses: 1, 2, 3 and baud rate 500 kBaud).

Only these settings ensure access to the inverters connected to the CAN1 node throughthe routing function of MOVI-PLC®.

7.2.2 Creating a new AxisControl_MDX_SingleAxis.pro MOVI-PLC® project 1. Create a new AxisControl_MDX_SingleAxis.pro project as described in

chapter "Opening and starting the project AxisControl_MDX_SingleAxis.pro" (seepage 12).

NOTEIt is essential that a servo operating mode (CFC or SERVO) is set at the inverter for thisoperating mode, since the torque is to be limited.

Torque control is not possible in VFC-n operating mode!

00

I


7 SolutionAdding an Operating Mode for Torque Control

7.2.3 Adding a new operating mode as a new project

For programming a completely new operating mode, you have to add the new operatingmode as a new object in the Object Organizer of the PLC Editor:

Proceed as follows:

1. Right-click on "AxisControl_SingleAxis".

2. Select [Add object] from the context menu.

3. Make the following settings in the "New POU" window:

The new mode is based on a speed control. This means you can also copy and adaptthe existing POU AxisModeVelocity_MDX to create a new POU:

Proceed as follows:

1. Right-click on "AxisModeVelocity_MDX".

2. Select [Copy object] from the context menu.

3. Enter the name of the new object "AxisModeTorqueControl_MDX" in the "New POU"window that appears now.

4. Click [OK].

824526219

[1] Object Organizer

825699851

00

I


7 Solution Adding an Operating Mode for Torque Control

7.2.4 Adding the new operating mode to the data types

Add the new operating mode to the "ENUM_AXISMODE" enumeration of theAxisControl data types as follows:

1. Select the [Data types] tab in the Object Organizer.

2. Double-click on the "ENUM_AXISMODE (ENUM)" enumeration

3. Add the new AM_TORQUECONTROL operating mode.

7.2.5 Programming the new moduleProgram the new module for the AxisModeTorqueControl_MDX operating mode asfollows:

1. In the [POUs] tab of the Object Organizer, double-click on the new"AxisModeTorqueControl_MDX" POU.

The POU to be edited is opened.

2. Change or amend the networks as follows:

825779723

[1] [Data types] tab in the Object Organizer[2] New operating mode AM_TORQUECONTROL

[2]

[1]

00

I



826261131

00

I



826291211

00

I



Description of the POU

For the new AM_TORQUECONTROL operating mode, the program has to change 2 pa-rameters in the MOVIDRIVE® inverter:

1. The speed monitoring function P500 (index 8557dez) must be set to OFF and

2. The torque limit P304 (index 8688dez) must be adapted continuously during opera-tion.

You can use the parameter writing functions of the MC_WriteParameter_MDXmodule.

The motion of the drive is speed-controlled in principle, and it is performed with theMC_MoveTargetSpeed_MDX motion module.

Reset the original values of the changed parameters in case of a mode change.

Description of the networks

Network 1:If the Enable input variable is not TRUE, the function block is exited immediately withRETURN.

Networks 2 and 3:Resetting the local variables MmaxNormalDone and NmonONDone. These variablesare required when exiting the operating mode.

Network 4:If the drive has not been started up in operating mode CFC or SERVO, errorINVALID_OPERATING_MODE with ErrorID FB0074 is issued.

Network 5:When exiting the mode, the original value of the torque limit (P304) is written back to theinverter.

Network 6:When exiting the mode, speed monitoring (P500) is switched back ON.

Network 7:After selecting the mode, the torque limit (P304) set after the drive startup is read outand stored in a variable.

Network 8:The original value of the torque limit (P304) is copied to the internal auxiliary variablenMmaxOld.

Network 9:After selecting the mode, speed monitoring (P500) is deactivated.

00

I



Network 10:When the user specifies a new value for the torque limit, this value is written to the in-verter (parameter P304). The internal scaling of the parameter is 0.001%. The parame-ter value is entered in thousandths percent. The entered value must be multiplied by1000 so that the user can enter the value in percent.

Network 11:The value for the torque limit specified by the user is copied to the nMmaxOld auxiliaryvariable.

Network 12:Calling up the MC_MoveTargetSpeed_MDX motion module for speed-controlled move-ment of the drive. For the speed setpoint Velocity, a value is entered that is 60 rpm fasterthan the current speed.

This means:

• The speed controller in the MOVIDRIVE® inverter operates at the maximum leveland

• The speed setpoint for the current controller is limited by the torque limit (P304).

Network 13:Creating the Error signal for the AM_TORQUECONTROL operating mode.

Network 14:Creating the ErrorID signal for the AM_TORQUECONTROL operating mode.

Network 15:Logic for adopting the newly requested operating mode.

Each operating mode module must contain this functionality. When a change of the op-erating mode is requested, this logic switches the active mode. The same logic as inAM_VELOCITY mode is used. The mode is only changed when both parameters for thetorque limit and speed monitoring have been assigned their original value (bMmax-NormalDone and bNmonONDone set to TRUE).

00

I



7.2.6 Activating the new operating mode

Activate the new operating mode by calling the AxisModeTorqueControl_MDX func-tion block in the AxisControl_MDX function block.

In the AxisControl_MDX function block, an instance of theAxisModeTorqueControl_MDX function block is called.

The inputs are connected as follows:

7.2.7 Linking the output signals of the new function block to existing structuresThe output signals of the new AxisModeTorqueControl_MDX function block are:

• fbAxisModeTorqueControl.Active and

• fbAxisModeTorqueControl.Stopped.

826563211

00

I



Link the output signals in the AxisControl_MDX function block as follows:

Link the error generation and the error number in the AxisControl_MDX functionblock as follows:

826619403

826650763

00

I



7.2.8 Testing the functionality of the new operating mode

After compiling the project successfully and transferring it to the MOVI-PLC® controller,you can test the function of the new AM_TORQUECONTROL operating mode using theApplication Builder interface MonitorAxisControl.mon.

To select the new operating mode and to specify the limit torque as Mmax in percent,modify the Application Builder interface as follows:

826683659

[5][4]

[2][3] [1]

[1] "Send" button for transferring the set parameters to the program[2] Motor axis control[3] Travel parameter setting [4] Setting the "Torque control" operating mode[5] Selecting the motor axis with logical address 1

00

I


8 Solution Synchronous Operation with Virtual Encoder as Master

8 Synchronous Operation with Virtual Encoder as MasterThree motor axes are created as standard when creating a newAxisControl_MDX_Technology.pro project in the PLC Editor.

• The first drive axis is assigned the AxisControl_MDX_SingleAxis functionality(without technology function), as described in the previous chapters.

• The second drive axis is assigned cam functionality (CAM). An instance of theAxisControlCam_MDX function block is called up.

• The third drive axis is assigned synchronous operation functionality (Gear). Aninstance of the AxisControlGear_MDX function block is called up.

In addition to that, the program VEMain for the virtual encoder is called in the 5 ms taskof the AxisControl_MDX_Technology.pro program.

In this program, an instance of the VEAxisControl function block is called up. The vir-tual encoder can be controlled via a global variable interface in the same way as theother drive axes (gVEInterfaceIn.... and gVEInterfaceOut....).

In standard communication, the virtual encoder transmits its actual position as an object(MDX_VIRTUAL_ENCODER_ID1) via the CAN1 bus. With the standard configurationof the MOVIDRIVE® inverters, you receive this MDX_VIRTUAL_ENCODER_ID1 objectas setpoint position from the CAN1 bus.

If the setpoint position is to be taken from a different source, the respectiveMOVIDRIVE® inverter must be reconfigured in the program. An example will be shownin a subsequent chapter.

The following sections describe how you can operate a MOVIDRIVE® inverter at a syn-chronous angle to a virtual encoder. The virtual encoder offers different operatingmodes, such as speed-controlled, position-controlled, etc. The MOVIDRIVE® inverterengages upon receiving a start signal and then travels along the virtual encoder at a syn-chronous angle.

NOTEThese technology functions can only be used if technology version T1 is activated forthe MOVI-PLC® controller.

For detailed information on technology activations, refer to the respective manuals ofthe MOVI-PLC® controller.

00

I


8 Startup and parameterization of MOVIDRIVE®Synchronous Operation with Virtual Encoder as Master

8.1 Startup and parameterization of MOVIDRIVE®

Start up the MOVIDRIVE® inverter using the "DriveStartup for MOVI-PLC®" tool. Con-nect the inverter directly to MOVITOOLS® MotionStudio via RS-485.

8.2 Startup of MOVIDRIVE® with option DIP11BIf a SSI absolute encoder is to be used for positioning, you have to commission theDIP11B card with DIP startup.

8.3 Opening and starting the project AxisControl_MDX_TechnologyThe procedure for creating a new project is the same as the one described in chapter"Opening and starting the project AxisControl_MDX_SingleAxis.pro " (see page 12).The only difference is that you select AxisControl_MDX_Technology.pro as a newproject.

NOTEFor detailed information on inverter startup, refer to chapter "MOVIDRIVE® require-ments" (see page 9).

826772107

00

I


8 Adapting the AxisControl_MDX_Technology.pro project Synchronous Operation with Virtual Encoder as Master

8.4 Adapting the AxisControl_MDX_Technology.pro projectOnly one MOVIDRIVE® is to be operated in sync with the virtual encoder. This meansyou have to remove all drives from the control configuration that are not used:

Delete the unneeded motor axes as follows:

1. Right-click on MOVIDRIVE®.


Instances of the unneeded drives must not be called in the PLC_PRG_Technologymain program.

Delete the respective networks and adapt the SBus address and array number of theinstance fbAxisControlGear:

826845963

827049867

[2]

[1]

[1] Array number[2] SBus address

00

I


8 Additional settings for synchronous operationSynchronous Operation with Virtual Encoder as Master

You also have to adapt the Configuration_MDX program and delete the unneededconfigurations there.

The following is an example of a complete program:

8.5 Additional settings for synchronous operationThe basic parameters for synchronous operation are set in theAxisControl_MDX_Technology.pro standard project. This is done in theConfiguration_MDX program.

The synchronization of the motor axis is always time-related, since no instance of theMC_PrepareGearIn_MDX function block is called.

If other functions, such as position-related engaging or offset processing in synchronousoperation, are required, you have to program them in the FB AxisModeGear_MDXfunction block.

827086091

NOTEFor a detailed description of how function blocks are integrated and parameterized,refer to the "MPLCTec..._MDX, MPLCTecVirtEncoder Libraries for MOVI-PLC®"manual. This manual also shows simple examples to illustrate the operating principle.

00

I


8 Compiling and starting the project in the PLC Editor Synchronous Operation with Virtual Encoder as Master

8.6 Compiling and starting the project in the PLC Editor1. Select the menu command [Project] / [Compile] in the PLC Editor to compile the

project.



You can now control the MOVIDRIVE® inverter and the VE virtual encoder via the globalstructure variables gAxisInterfaceIn_MDX[x] or gVEInterfaceIn. These structure vari-ables contain control signals such as controller inhibit, enable, reset, operating mode,etc.

For test purposes, you can also control the motor axis and the VE virtual encoder via aninterface of the Application Builder (MonitorAxisControl.mon).

8.7 Controlling MOVIDRIVE® + virtual encoder via "Monitor AxisControl"You can use the Monitor AxisControl.mon diagnostics interface of the ApplicationBuilder to test the functionality. The procedure for opening and configuring the interfaceis described in chapter "Controlling MOVIDRIVE® via Application Builder Monitor Axis-Control" (see page 20).

You have to start 2 user interfaces:

• One interface for controlling the virtual encoder and

• One for controlling the MOVIDRIVE® inverter.

To control the virtual encoder and the inverter, you have to enable control via H vari-ables:

1. In the PLC_PRG_Technology main program, set thegAxisInterfaceIn_MDX[1].HControl variable to TRUE.

2. Set the gVEInterfaceIn.HControl variable to TRUE in the VEMain program.

00

I


8 Controlling MOVIDRIVE® + virtual encoder via "Monitor AxisControl"Synchronous Operation with Virtual Encoder as Master

The user interface of the virtual encoder after selecting [VE]:

You can control the virtual encoder like a normal drive axis.

Proceed as follows:

1. For "axis mode", set the "velocity" operating mode.

2. Enter the travel parameters for "velocity", "acceleration" and "deceleration".

3. Click on [send] to transfer the changes and settings to the controller.

4. Click on [start] and then on [send] to start the virtual movement.

To reset the current position to a defined position, you have to reference the virtual en-coder:

1. To do so, select "homing" under "axis mode".

2. Click on [start] and then on [send].

The current position of the virtual encoder is now set to the value of the reference offsetin the "actual position" display field (default: 0).

828042379

00

I


8 AxisControlCam_MDX function block Synchronous Operation with Virtual Encoder as Master

The user interface of the MOVIDRIVE® after selecting axis [01]:

For the necessary settings, refer to the screen shots of the two Application Builderinterfaces.

If the virtual encoder is in AM_VELOCITY mode, you can engage or disengage theMOVIDRIVE® inverter in AM_GEARING mode with the signal [start].

8.8 AxisControlCam_MDX function blockThe first drive axis has normal AxisControl_MDX functionality.

For the relevant interface description, refer to the previous chapters.

In the PLC_PRG_Technology main program, an instance of theAxisControlCam_MDX function block is called up for the second motor axis. The elec-tronic cam technology function (CAM) can now be used.

The input and output signals of the function block have the following meaning:

828302347

00

I


8 AxisControlCam_MDX function blockSynchronous Operation with Virtual Encoder as Master

8.8.1 Input signals

The behavior of the AxisControlCam_MDX function block is dependent on the follow-ing input signals:


HControl BOOL If this input signal is set to TRUE, the motor axis is con-trolled via H variables.

Node CAN_NODE This input signal sets the relevant CAN bus node.












Acceleration DINT This input signal sets the acceleration ramp (time in [ms] based on a setpoint step change of 3000 min-1).

Deceleration DINT This input signal sets the acceleration ramp (time in [ms] based on a setpoint step change of 3000 min-1).


Table UNIT This input signal selects the curve (5...0).



00

I


8 AxisControlCam_MDX function block Synchronous Operation with Virtual Encoder as Master

8.8.2 Output signals

The AxisControlCam_MDX function block provides the following output signals:











yet.





InverterError BOOL The output signal InverterError indicates that the inverter has detected a fault.

InverterFaultStatus DWORD The output signal shows the fault code of the inverter of the motor axis.


FBErrorID DWORD The output signal shows the error code of the faulty motion function blocks.Note:For information on the error codes, refer to chapter "Error identifier" in the library manual or to the MPLCSystem_ErrorCodes.lib library in the PLC Editor.








LinkState MC_LINKTECSTATE

The output signal indicated the current status of the MC_LINKTECCAM function block:• GEN_TEC_NOTLINKED (no connection) • GEN_TEC_NOTINITIALIZED (not initialized)• GEN_TEC_RESETED (reset service executed)• GEN_TEC_RESTORED (restore service executed)• GEN_TEC_INITIALIZED (cyclical data exchange

successful)

00

I


8 AxisControlGear_MDX function blockSynchronous Operation with Virtual Encoder as Master

8.9 AxisControlGear_MDX function blockIn the PLC_PRG_Technology main program, an instance of theAxisControlGear_MDX function block is called up for the third motor axis.

The input and output signals of the function block have the following meaning:

8.9.1 Input signalsThe behavior of the AxisControlGear_MDX function block is dependent on the fol-lowing input signals:

CamState MC_CAM_-STATE_MDX

The signal shows the current status of the cam.• MDX_CAM_RESET (cam reset, free-wheeling with

speed setpoint in H439• MDX_CAM_START (startup cycle state)• MDX_CAM_MAINCURVE (main curve) • MDX_CAM_STOP (stop cycle state)• MDX_CAM_STOP_INVERTERSTART (stop cycle

state with inverted startup cycle curve)• MDX_CAM_NOTLINKED (no connection)

InGear BOOL This output signal shows that the motor axis is in "hard" synchronous operation.



HControl BOOL If this input signal is set to TRUE, the motor axis is con-trolled via H variables.

Node CAN_NODE This input signal sets the relevant CAN bus node.












Acceleration DINT This input signal sets the acceleration ramp (time in [ms] based on a setpoint step change of 3000 min-1).

00

I


8 AxisControlGear_MDX function block Synchronous Operation with Virtual Encoder as Master

8.9.2 Output signalsThe AxisControlGear_MDX function block provides the following output signals:

Deceleration DINT This input signal sets the acceleration ramp (time in [ms] based on a setpoint step change of 3000 min-1).


GearOutLagCountOn BOOL TRUE: The difference counter remains active after disen-gaging.

GearClearLag BOOL A rising edge at this input deletes the difference counter for synchronous operation.














yet.





InverterError BOOL The output signal InverterError indicates that the inverter has detected a fault.

InverterFaultStatus DWORD The output signal shows the fault code of the inverter of the motor axis.


00

I


8 AxisControlGear_MDX function blockSynchronous Operation with Virtual Encoder as Master

FBErrorID DWORD The output signal shows the error code of the faulty motion function block.Note:For information on the error codes, refer to chapter "Error identifier" in the library manual or to the MPLCSystem_ErrorCodes.lib library in the PLC Editor.









The output signal indicated the current status of the MC_LINKTECCAM function block:• GEN_TEC_NOTLINKED (no connection) • GEN_TEC_NOTINITIALIZED (not initialized)• GEN_TEC_RESETED (reset service executed)• GEN_TEC_RESTORED (restore service executed)• GEN_TEC_INITIALIZED (cyclical data exchange

successful)

GearState MC_GEAR_STATE_MDX

The signal shows the current status of synchronous oper-ation:• MDX_GEAR_OUTGEAR_N_CTRL (disengaged,

speed-controlled) • MDX_ GEAR_OUTGEAR_X_CTRL (disengaged,

position-controlled) • MDX_GEAR_ENGAGING_GEAR_IN (startup cycle

state) • MDX_GEAR_IN_GEAR (synchronous operation)• MDX_GEAR_OFFSET (offset operation) • MDX_DISENGAGING_GEAR (disengaged state) • MDX_GEAR_NOTLINKED (no valid gear state, e.g.

when LinkState = NOTLINKED)


LagCleared BOOL The output signal shows that the difference counter has been deleted.


00

I


9 Adapting the AxisControl_MDX_Technology.pro project Synchronous Operation with MOVIDRIVE® as Master

9 Synchronous Operation with MOVIDRIVE® as MasterThe standard setting prepares the AxisControl_MDX_Technology project for syn-chronous operation with the virtual encoder as master. If a MOVIDRIVE® inverter is tobe master, you have to change several settings in theAxisControl_MDX_Technology.pro project.

For detailed information, refer to chapter "Startup and parameterization ofMOVIDRIVE®" (see page 61):

• Basic procedure for preparing the two MOVIDRIVE® inverters and

• Creating a new AxisControl_MDX_Technology.pro project using the projectwizard in MOVITOOLS® MotionStudio.

9.1 Adapting the AxisControl_MDX_Technology.pro projectOne MOVIDRIVE® inverter is controlled with the standard function blockAxisControl_MDX. The second MOVIDRIVE® inverter must be controlled with theAxisControlGear_MDX block because it is intended for synchronous operation. Thesecond motor axis (SBus address = 2) is intended for cam operation as standard and istherefore not needed. You have to delete it from the control configuration:

Delete the unneeded second motor axis as follows:

1. Right-click on [MOVIDRIVE MDX B].


The instance of the unneeded drive must not be called in the PLC_PRG_Technologymain program. You have to delete the relevant network (4).

826845963

00

I


9 Adapting the AxisControl_MDX_Technology.pro projectSynchronous Operation with MOVIDRIVE® as Master

9.1.1 Standard communication settingsIn the standard communication configuration, the slave axis receives its position set-point from the virtual encoder (master source).

The send object of the virtual encoder is defined in the Configuration_MDX programas follows:

• gVirtualEncoderConfiguration.LinkTecAxisVirtual.SendObjectID:= MDX_VIRTUAL_ENCODER_ID1

For the synchronously operated slave axis, the source for the setpoint position is definedas follows for PDO1:

• gAxisConfiguration_MDX[3].SetGearConfig.MasterSource:= MDX_GEAR_RECEIVE_PDO_1

The receive object 1 is initialized outside the Configuration_MDX program in theMC_EXTENDEDCONFIG_MDX structure for the slave drives:

ReceivePDO1: MC_PDO_ID_MDX := MDX_VIRTUAL_ENCODER_ID1

You can find the MC_EXTENDEDCONFIG_MDX structure in [Resources] / [Librarymanager] in the 01_SingleAxisMotion\MPLCDatatypes.lib library:

NOTECalling up the fbAxisControlCam_MDX instance deletes the network. The fbAxisControlGear_MDX synchronous operation axis is assigned the logical address2 ( LogAdr = 2) after initialization even though the SBus address of the axis is 3.

829985419

00

I



837339787

NOTEThe virtual encoder sends the same object as the slave axis receives with PDO1.

You can check the IPOS variable H300 in MOVIDRIVE® as to whether the position set-points are received correctly.

00

I



If the slave axis receives its setpoint position from the motor encoder of the firstMOVIDRIVE® inverter, communication on the CAN_Node1 is configured as follows:

9.1.2 ExampleThe following requirements apply:

• The master axis is to send its current position of the motor encoder as an object viathe CAN1 bus.

• The object ID is MDX_PDO_ID2.

• The slave axis is to receive this object ID on the PDO1.

• The slave axis is to use its own motor encoder to move synchronously to this sentmaster position.

MOVIDRIVE® Master

gAxisConfiguration[1].InitialConfig.ExtendedConfiguration_MDX

.SendID := MDX_PDO_ID2.SendSource := MDX_SEND_X15

gAxisConfiguration[3].SetGearConfig.SlaveSource := MDX_GEAR_SLAVE_X15

.MasterSource := MDX_GEAR_RECEIVE_PDO1

gAxisConfiguration[3].InitialConfig.ExtendedConfiguration_MDX

.ReceivePDO1 := MDX_PDO_ID2

MasterSource

+

SlaveSourceX15X14SSI

-H300

CAN1

MDX_PDO_ID1MDX_PDO_ID2


.......InitialConfig.

ExtendedConfiguration_MDX.ReceivePDO1



.....

MDX_SEND_X15MDX_SEND_X14MDX_SEND_SSI

H301



...

....InitialConfig.ExtendedConfiguration_MDX.

ReceivePDO2

H303



...


ReceivePDO4

H302



...


ReceivePDO3

MOVI-PLC®FB Configuration_MDX-Technology

MOVIDRIVE® Slave

838395019

00

I



The master axis is configured in the Configuration_MDX program as follows:

• gAxisConfiguration_MDX[1].bUseInitialConfig := TRUE;

• gAxisConfiguration_MDX[1].InitialConfig.ExtendedConfiguration_MDX.SendSource:= MDX_SEND_X15;

• gAxisConfiguration_MDX[1].InitialConfig.ExtendedConfiguration_MDX.SendID:= MDX_PDO_ID2;

• gAxisConfiguration_MDX[1].InitialConfig.ExtendedConfiguration_MDX.SendCycle-Time := 5;

The slave axis is configured in the Configuration_MDX program as follows:

• gAxisConfiguration_MDX[3].bUseInitialConfig := TRUE;

• gAxisConfiguration_MDX[3].SetGearConfig.SlaveSource:= MDX_GEAR_SLAVE_X15;

• gAxisConfiguration_MDX[3].SetGearConfig.MasterSource:= MDX_GEAR_RECEIVE_PDO_1;

• gAxisConfiguration_MDX[3].InitialConfig.ExtendedConfiguration_MDX.ReceivePDO1 := MDX_PDO_ID2;

You have to set the variable ….bUseInitialConfig := TRUE for both motor axes, becauseotherwise the MC_InitialConfig_MDX function block is not initialized.

This function block activates special communication interfaces and functions of the in-verters.

NOTEFor more information about this FB, refer to the manual: "MPLCMotion_MDX andMPLCMotion_MX Libraries for MOVI-PLC®".

00

I



The settings for both MOVIDRIVE® inverters must be re-configured in theConfiguration_MDX_Technology program:

For the master axis ..._MDX[1]:

839392907

[1] Communication settings for sending the master position

[1]

00

I



For the slave axis ..._MDX[3]:

The adapted project can now be compiled and loaded into the controller.

839556107

[1] Receive object PDO1 as master source and motor encoder X15 as actual value source[2] Communication settings for receiving the master position

[1]

[2]

00

I


9 Controlling both MOVIDRIVE® inverters via "Monitor AxisControl"Synchronous Operation with MOVIDRIVE® as Master

9.2 Controlling both MOVIDRIVE® inverters via "Monitor AxisControl"You can use the Monitor AxisControl.mon diagnostics interface of the ApplicationBuilder to test the functionality. The procedure for opening and configuring the interfaceis described in chapter "Controlling MOVIDRIVE® via Application Builder Monitor Axis-Control" (see page 20).

You have to start 2 user interfaces: One interface for controlling the master axis and an-other one for controlling the slave axis.

You have to activate control via H variables to control both axes:

• In the PLC_PRG_Technology main program, set thegAxisInterfaceIn_MDX[1].HControl variable to TRUE.

• In the PLC_PRG_Technology main program, set thegAxisInterfaceIn_MDX[3].HControl variable to TRUE.

When selecting Axis [01], the user interface of the master axis looks as follows:

839612683

00

I


9 Controlling both MOVIDRIVE® inverters via "Monitor AxisControl" Synchronous Operation with MOVIDRIVE® as Master

When selecting Axis [02], the user interface of the slave axis looks as follows:

For the necessary settings, refer to the screen shots of the two Application Builder inter-faces.

If the master axis is operated in AM_VELOCITY mode, you can engage or disengagethe slave axis in AM_GEARING mode by clicking on the [start] button.

839771403

00

I


10 Operating modesAxisControl_MDX_Technology Sample Project

10 AxisControl_MDX_Technology Sample Project10.1 Operating modes

The project AxisControl_MDX_Technology offers the user the basic functions of theAxisControl_MDX_SingleAxis sample project. This basic functionality has alreadybeen described in previous chapters:

• Speed control


• Modulo positioning


• Job mode, speed-controlled

• Job mode, position-controlled

• Referencing

In addition to this, the AxisControl_MDX_Technology project offers the functions:

• Synchronous operation

• Electronic cam

Pi

fkVA

Hz

n

Pi

fkVA

Hz

n


10 Function blocks AxisControl_MDX_Technology Sample Project

10.2 Function blocksThe comprises the following function blocks:

The task configuration ([Resources] / [Task configuration]) shows that thePLC_PRG_Technology main program is called cyclically by a free-running task. Theprogram for the virtual VEMain encoder is called every 5 ms in the 5 ms task.

796036491

[1] Additional function blocks in the AxisControl_MDX_Technology.pro project that are not included in the AxisControl_MDX_SingleAxis.pro project.

[1]

[1]

[1]

Pi

fkVA

Hz

n

Pi

fkVA

Hz

n


10 Function blocksAxisControl_MDX_Technology Sample Project

In the control configuration ([Resources] / [Control configuration]), 3 axes are connectedto the CAN1 system bus as standard. Their SBus addresses are 1, 2 and 3.

Example for module parameters of axis 1:

Functionality of the motor axes:

• The first motor axis offers standard functionality (calling the AxisControl_MDXfunction block)

• The second motor axis offers the functions of a cam (callingAxisControlCam_MDX)

• The third motor axis offers synchronous operation functions (callingAxisControlGear_MDX).

797934219

798717835

Pi

fkVA

Hz

n

Pi

fkVA

Hz

n


10 Function blocks AxisControl_MDX_Technology Sample Project

If the number of controlled motor axes changes, you have to adapt the control configu-ration:

Deleting motor axes:1. Right-click on [MOVIDRIVE].


Adding a motor axis:1. Right-click on [Can1 enabled].


3. Select [MOVIDRIVE MDX B].

Adapting the control configuration:Subsequently, adjust the module parameters (SBus address).

798772235

NOTEFor non-existent motor axes, no instance of the AxisControl_MDX,AxisControlCam_MDX or AxisControlGear_MDX function blocks may be calledup.

Delete the respective networks from the PLC_PRG_Technology main program.

NOTEIf the function of the motor axes changes, you have to add and parameterize the re-spective networks by calling the instance of the function blocks in thePLC_PRG_Technology main program (e.g. synchronous operation technology func-tion or electronic cam technology function).

Then integrate the configurations of the respective motor axes in theConfiguration_MDX program at the correct position.

Pi

fkVA

Hz

n

Pi

fkVA

Hz

n


10 Description of operating modesAxisControl_MDX_Technology Sample Project

10.3 Description of operating modes 10.3.1 Electronic cam (AM_CAMING)Description This operating mode provides cam functionality for the motor axes. Engaging or disen-

gaging is possible directly via the Start input signal of the AxisControlCam_MDX func-tion block. This is a standard cam function.

Additional functions are programmed in the AxisControlCam_MDX function blockusing the MPLCTecCamMotion_MDX library.

Prerequisite MOVIDRIVE® has been started up with the Electronic Cam technology function via theMOVITOOLS® MotionStudio technology editor. When using theMC_CamCalcRtoR_MDX or MC_CamCalcSpline_MDX function blocks, this startup isnot necessary.

Input signals The behavior of the AxisControlCam_MDX function block is dependent on the follow-ing input signals:

Output signals The AxisControlCam_MDX function block provides the following output signals:


Enable BOOL If this input signal is set to TRUE, the operating mode AM_CAMMING is enabled and processed.

Start BOOL This input signal starts the movement of the motor axis.

Table UINT This input signal selects the curve number (5...0).

ConfigCamTableSelect ST_CamTable-Select_MDX

If this input signal is TRUE, the setpoint is transferred to the virtual encoder (with FALSE: X14 active)

Axis AXIS_REF Logical address of the motor axis; created by the respec-tive MC_ConnectAxis_MDX function block.


This input signal transfers the current status of the MC_LINKTECCAM function block:• GEN_TEC_NOTLINKED (no connection)• GEN_TEC_NOTINITIALIZED (not initialized)• GEN_TEC_ RESETED (reset service executed)• GEN_TEC_RESTORED (restore service executed)• GEN_TEC_INITIALIZED (cyclical data exchange

successful)

CamState MC_CAM_-STATE_MDX

This input signal transfers the current status of the elec-tronic cam:• MDX_CAM_RESET (cam reset, free-wheeling with

speed setpoint in H439)• MDX_CAM_START (startup cycle state)• MDX_CAM_MAINCURVE (main curve)• MDX_CAM_STOP (stop cycle state)• MDX_CAM_STOP_INVERTERSTART (stop cycle

state with inverted startup cycle curve)• MDX_CAM_NOTLINKED (no connection)




Requested axis mode; required for internal operating mode switching.


Actually active axis mode; required for internal operating mode switching.


Error BOOL The output signal indicates an error in a motion function block.

Pi

fkVA

Hz

n

Pi

fkVA

Hz

n


10 Description of operating modes AxisControl_MDX_Technology Sample Project

10.3.2 Synchronous operation (AM_GEARING)Description This operating mode provides synchronous operation functionality for the motor axes.

Engaging or disengaging is performed directly via the Start input signal of theAxisControlGear_MDX function block. The basis of this operating mode is time-re-lated startup.

Additional synchronous operation functions can be programmed in theAxisControlGear_MDX function block using the MPLCTecGearMotion_MDX li-brary.

Prerequisite None.

Input signals The behavior of the AxisControlGear_MDX function block is dependent on the fol-lowing input signals:

ErrorID DWORD The output signal shows the error code of the faulty motion function block.Note:For information on the error codes, refer to chapter "Error identifier" in the library manual or to the MPLCSystem_ErrorCodes.lib library in the PLC Editor.




Enable BOOL If this input signal is set to TRUE, the operating mode AM_GEARING is enabled and processed.

Start BOOL This input signal starts the movement of the motor axis.

GearOutLagCountOn BOOL If this input signal is set to TRUE, the difference counter remains active in the disengaged state.

GearCleanLag BOOL If this input signal is set to TRUE, the difference counter is deleted.

AxisConfiguration ST_AxisConfigu-ratio_MDX

This input variable transfers the configuration parameters to the relevant motor axis.



This input signal transfers the current status of the MC_LINKTECCAM function block:• GEN_TEC_NOTLINKED (no connection)• GEN_TEC_NOTINITIALIZED (not initialized)• GEN_TEC_ RESETED (reset service executed)• GEN_TEC_RESTORED (restore service executed)• GEN_TEC_INITIALIZED (cyclical data exchange

successful)

GearState MC_GEAR_-STATE_MDX

The signal shows the current status of synchronous oper-ation:• MDX_GEAR_OUTGEAR_N_CTRL (disengaged,

speed-controlled)• MDX_ GEAR_OUTGEAR_X_CTRL (disengaged,

position-controlled)• MDX_GEAR_ENGAGING_GEAR_IN (startup cycle

state)• MDX_GEAR_IN_GEAR (synchronous operation)• MDX_GEAR_OFFSET (offset operation)• MDX_DISENGAGING_GEAR (disengaged state)• MDX_GEAR_NOTLINKED (no valid gear state, e.g.

when LinkState = NOTLINKED)



Pi

fkVA

Hz

n

Pi

fkVA

Hz

n


10 Description of operating modesAxisControl_MDX_Technology Sample Project

Output signals The AxisControlGear_MDX function block provides the following output signals:


Requested axis mode; required for internal operating mode switching.


Actually active axis mode; required for internal operating mode switching.



Error BOOL The output signal indicates an error in a motion function block.

ErrorID DWORD The output signal shows the error code of the faulty motion function block.Note:For information on the error codes, refer to chapter "Error identifier" in the library manual or to the MPLCSystem_ErrorCodes.lib library in the PLC Editor.


LagCleared BOOL The output signal shows that the difference counter has been deleted.

Pi

fkVA

Hz

n

Pi

fkVA

Hz

n


11 General notes on data backup Data Backup for Connected Inverters

11 Data Backup for Connected Inverters

11.1 General notes on data backupIn AxisControl projects, Data Management allows for data of inverters connected toMOVI-PLC® advanced DHx41B to be saved on the integrated SD card. The datarecords can also be re-loaded into the inverters.

In case of an upload in the form of a VarData record, the data records of the connectedinverters are stored on the SD memory card of MOVI-PLC® advanced DHx41B. It is pos-sible to create a data record from one or all connected inverters.

Prerequisites:

• The modules for the Data Management functionality are integrated in the motionlibraries as of version 2030r1.

• The Data Management functionality and the Application Builder user interface areavailable for AxisControl projects as of MOVITOOLS® MotionStudio 5.50.

• Series firmware of MOVI-PLC® advanced DHx41B as of 1031.

• Firmware status of the inverters:

• MOVIDRIVE®: 824 854 0.19 and higher

• MOVIAXIS®: No limitation

• MOVITRAC® B: 1820 230 6.13

• For the MOVIDRIVE® and MOVITRAC® B inverters, a signature must have beenassigned as ID.

NOTEIf a download to a drive axis is performed in any operating mode, the drive axis mustbe in the state 24 V operation, controller inhibit or no enable.

Pi

fkVA

Hz

n

Pi

fkVA

Hz

n


11 Description of operating modesData Backup for Connected Inverters

11.2 Description of operating modesThe Data Management function offers the following operating modes:

• Mode 0: CHECK

• Mode 1: CHECK & DOWNLOAD

• Mode 2: UPLOAD

• Mode 3: DOWNLOAD ALL

CHECKPerformed steps:

• Checking the ID of the connected inverter for possible changes

For MOVIAXIS®, a hardware serial number is the ID, whereas for MOVIDRIVE® andMOVITRAC® B, the signature is used.

• Displaying the result of the check at the "status" output.

If the CHECK operating mode is selected in connection with axis selection 99, all con-nected inverters are checked.

CHECK & DOWNLOADPerformed steps:

• Comparison as in CHECK operating mode.

• Loading the parameter set stored on the SD memory card to those inverters thathave a new ID (e.g. axis replacement).

UPLOADPerformed steps:

• Loading the parameter sets of the connected inverters and storing the data on theSD memory card.

• Storing the inverter IDs in a configuration file.

The CHECK or CHECK & DOWNLOAD operating modes use this ID to recognize areplaced unit.

DOWNLOAD ALLPerformed steps:

• Copying the parameter set stored on the SD memory card to the inverter even if theID is still the same.

00

I


11 Data Management using global variable interface Data Backup for Connected Inverters

11.3 Data Management using global variable interfaceUsually, the Data Management function is addressed via the global variable interface.

For this purpose, the global variables gAxisInterfaceIn_DataManagement andgAxisInterfaceOut_DataManagement are used.

Global input variables for Data Management:

Global output variables for Data Management:

The modules for Data Management are stored in the "AxisDataManagement" directory.

842282763

842481163

842553867

00

I


11 Data Management using global variable interfaceData Backup for Connected Inverters

The AxisDataManagement program is called cyclically in the free-running task"TaskFree":

PRG_AxisDatamanagement program:

The fbAxisDatamananagement_Control function block is started in the AxisData-Management program if

• A connection has been established to all drive axes (gbAllAxisConnected = TRUE)and

• Data Management is started (gAxisInterfaceIn_Datamanagement.Start =TRUE).

The following information is transferred to this function block:

• Number of connected drive axes

(gAxisInterfaceIn_Datamanagement.SelectedAxis) and

• Operating mode for Data Management

(gAxisInterfaceIn_Datamanagement.Mode).

842651659

843699851

00

I


11 Data Management using global variable interface Data Backup for Connected Inverters

The function block outputs:

• Done, after the Data Management function has been executed successfully,

• Busy, while the Data Management function is being executed,

• Error with the respective ErrorID, if an error occurs during the execution, and

• Status with the status display of the respective Data Management task for the driveaxis.

The variable gAxisInterfaceOut_Datamanagement.Status is an ARRAY of theMC_STATUS_DATAMANAGEMENT_DM type and provides the states shown in thefigure below:

In the fb AxisDatamanagement_Control function block, the SelectedAxis entry vari-able determines whether a Data Management task is executed for one drive axis onlyor for all drive axes:

843774347

• For one drive axis (fbMC_SingleAxisDataManagement_CAN): SelectedAxis = 1, 2, ...

• For all drive axes (fbMC_AllAxisDataManagement_CAN): SelectedAxis = 99

00

I


11 Data Management via Application BuilderData Backup for Connected Inverters

11.4 Data Management via Application BuilderIt is also possible to access the Data Management functions via the Monitor Axis-Control visualization interface of the Application Builder.

844083083

[1] Selecting the interface for Data Management

[1]

00

I


11 Data Management via Application Builder Data Backup for Connected Inverters

When selecting the [Data Management] tab, the user interface for Data Managementopens.

Click on [Enable] to enable control of Data Management.

In the [Select Axis] field, you can select the drive axes to be addressed:

• All drive axes or

• Only one drive axis, the logic address of which you have to specify.

In the [Mode] selection field, you an select an operating mode as described in chapter"Description of Operating Modes" (see page 89).

Use the [Start process] function key to start the Data Management function of the se-lected operating mode.

844170123

00

I


11 Data Management via Application BuilderData Backup for Connected Inverters

The following status messages are displayed:

• Done, after the Data Management function has been executed successfully,

• Busy, while the Data Management function is being executed,

• Error with the respective ErrorID, if an error occurs during the execution,

• Status with the status display of the respective Data Management task for the driveaxis, and

• The status of the respective drive axis.

00

I


12 Communication problems between the PLC Editor and MOVI-PLC® Frequently Asked Questions

12 Frequently Asked Questions12.1 Communication problems between the PLC Editor and MOVI-PLC®

Going "online" with a project requires correct communication settings in the PLC Editor.You can monitor these settings under [Online] / [Communication parameters...].

12.1.1 MOVI-PLC® basic DHP11B

1. Click on "Local" in the window on the left to display the selected controller in the graydisplay field.

You have to create the controller as a new channel unless "MOVI-PLC universal" isdisplayed.

2. Click the [New] button.

A new window with selectable controllers appears.

1. Select "MOVI-PLC universal" from the unit list and then click on [OK].

844248203

[1] Display field of the selected controller[2] [New] button for selecting a new channel

844937483

[1] MOVI-PLC universal

[2]

[1]

[1]

00

I


12 Communication problems between the PLC Editor and MOVI-PLC®Frequently Asked Questions

12.1.2 MOVI-PLC® advanced DHE41B

1. Click on "local" in the window on the left to display the selected controller in the graydisplay field.

You have to create the controller as a new channel unless "MOVI-PLC TCP/IP" isdisplayed.

2. Click the [New] button.

A new window with selectable controllers appears.

1. Select "MOVI-PLC TCP/IP" from the unit list and then click on [OK].

2. Check whether the value "yes" is assigned to the name "Motorola byteorder" in thefirst window. Make the appropriate changes, if necessary.

845294987

[1] Display field of the selected controller[2] [New] button for selecting a new channel

846600971

[1] Select new channel

[1]

[2]

[1]


12 Controlling the AxisControl_MDX... sample project via PROFIBUS Frequently Asked Questions

12.2 Controlling the AxisControl_MDX... sample project via PROFIBUS12.2.1 MOVI-PLC® basic DHP11B

The MOVI-PLC® basic DHP11B controller offers a PROFIBUS slave interface. Youhave to perform the following steps to exchange data with the MOVIDRIVE® invertersvia PROFIBUS process data words.

The example only shows parameterization of the process input data of one axis. Theprocedure for parameterizing the process output data of other axes is the same.

Enabling the PROFIBUS interface in the control configuration:

1. Right-click on "Profibus disabled".

2. Select [Replace element] from the context menu.

3. Select [Profibus enabled] from the submenu.

846772363


12 Controlling the AxisControl_MDX... sample project via PROFIBUSFrequently Asked Questions

Assigning global variable designations for the PROFIBUS process data words:

32 process input data words and 32 process output data words are available under[Profibus enabled].

Enter variable names as follows:

1. Select the respective process data word.

2. Right-click on "AT".

3. Enter the required name.

The variable names can now be further processed in the program

You can enter variable names of the individual bits of the process data word in the sameway within the process data word.

846837515

[1] Process input data word[2] AT

[2]

[1]


12 Controlling the AxisControl_MDX... sample project via PROFIBUS Frequently Asked Questions

Connecting the global variables of the AxisControl_MDX function block with thePROFIBUS data:

Several program commands must be programmed for data exchange of the interfacewith the global variables of the AxisControl_MDX function block:

1. Right-click in the Object Organizer and select [Insert object ...] from the contextmenu.

2. Enter "P_InterfaceProfibus" as the name of the module, because the module type isa program.

3. Select "Structured Text (ST)" as language.

Now, you have to call this program in the PLC_PRG main program.

1. It is recommended to call it before calling the instances of the Axis_Control_MDXfunction block in a network.

The program enables cyclical data exchange between PROFIBUS and theAxisControl_MDX_SingleAxis axis driver.

12.2.2 MOVI-PLC® advanced DHE41BThe MOVI-PLC® advanced DHF41B controller also has a PROFIBUS/slave interface.The configuration of this controller is the same as that of MOVI-PLC® basic DHP11B.

Here, too, you first have to enable the PROFIBUS interface and then define the variablenames.

The program for the interface between the PROFIBUS data and the global variables ofthe AxisControl_MDX_SingleAxis axis driver also corresponds to that of the MOVI-PLC® basic DHP11B controller.

You must call this interface program in the PLC_PRG_SingleAxis main program aswell. It enables cyclical data exchange.

846995595


12 Features and operating principle of the virtual encoderFrequently Asked Questions

12.3 Features and operating principle of the virtual encoderIn the AxisControl_MDX_Technology.pro project, the VEMain program for the vir-tual encoder is called in the 5 ms task. This program calls an instance of the VEAxis-Control function block. The virtual encoder can be controlled via a global variable inter-face in the same way as the other drive axes (gVEInterfaceIn.... and gVEInterface-Out....).

In standard communication, the virtual encoder transmits its actual position as an object(MDX_VIRTUAL_ENCODER_ID1) via the CAN1 bus.

As standard, the MOVIDRIVE® inverters are configured to receive thisMDX_VIRTUAL_ENCODER_ID1 object as setpoint position from the CAN1 bus.


13 Features and operating principle of the virtual encoder Address List

13 Address ListGermany

HeadquartersProductionSales

Bruchsal SEW-EURODRIVE GmbH & Co KGErnst-Blickle-Straße 42 D-76646 BruchsalP.O. BoxPostfach 3023 • D-76642 Bruchsal

Tel. +49 7251 75-0Fax +49 7251 75-1970http://[email protected]

Service Compe-tence Center

Central SEW-EURODRIVE GmbH & Co KGErnst-Blickle-Straße 1 D-76676 Graben-Neudorf

Tel. +49 7251 75-1710Fax +49 7251 [email protected]

North SEW-EURODRIVE GmbH & Co KGAlte Ricklinger Straße 40-42 D-30823 Garbsen (near Hannover)


East SEW-EURODRIVE GmbH & Co KGDänkritzer Weg 1D-08393 Meerane (near Zwickau)


South SEW-EURODRIVE GmbH & Co KGDomagkstraße 5D-85551 Kirchheim (near München)


West SEW-EURODRIVE GmbH & Co KGSiemensstraße 1D-40764 Langenfeld (near Düsseldorf)


Electronics SEW-EURODRIVE GmbH & Co KGErnst-Blickle-Straße 42 D-76646 Bruchsal


Drive Service Hotline / 24 Hour Service +49 180 5 SEWHELP+49 180 5 7394357

Additional addresses for service in Germany provided on request!

France

ProductionSalesService

Haguenau SEW-USOCOME 48-54, route de Soufflenheim B. P. 20185F-67506 Haguenau Cedex

Tel. +33 3 88 73 67 00 Fax +33 3 88 73 66 00http://[email protected]

Production Forbach SEW-EUROCOME Zone Industrielle Technopôle Forbach SudB. P. 30269F-57604 Forbach Cedex

Tel. +33 3 87 29 38 00

AssemblySalesService

Bordeaux SEW-USOCOME Parc d'activités de Magellan62, avenue de Magellan - B. P. 182F-33607 Pessac Cedex

Tel. +33 5 57 26 39 00Fax +33 5 57 26 39 09

Lyon SEW-USOCOME Parc d'Affaires RooseveltRue Jacques TatiF-69120 Vaulx en Velin

Tel. +33 4 72 15 37 00Fax +33 4 72 15 37 15

Paris SEW-USOCOME Zone industrielle 2, rue Denis Papin F-77390 Verneuil I'Etang

Tel. +33 1 64 42 40 80Fax +33 1 64 42 40 88

Additional addresses for service in France provided on request!


13 Features and operating principle of the virtual encoderAddress List

Algeria

Sales Alger Réducom 16, rue des Frères ZaghnounBellevue El-Harrach16200 Alger


Argentina


Buenos Aires SEW EURODRIVE ARGENTINA S.A.Centro Industrial Garin, Lote 35Ruta Panamericana Km 37,51619 Garin

Tel. +54 3327 4572-84Fax +54 3327 [email protected]://www.sew-eurodrive.com.ar

Australia


Melbourne SEW-EURODRIVE PTY. LTD.27 Beverage DriveTullamarine, Victoria 3043


Sydney SEW-EURODRIVE PTY. LTD.9, Sleigh Place, Wetherill Park New South Wales, 2164


Austria


Wien SEW-EURODRIVE Ges.m.b.H. Richard-Strauss-Strasse 24A-1230 Wien

Tel. +43 1 617 55 00-0Fax +43 1 617 55 00-30http://[email protected]

Belarus

Sales Minsk SEW-EURODRIVE BYRybalkoStr. 26BY-220033 Minsk

Tel.+375 (17) 298 38 50Fax +375 (17) 29838 [email protected]

Belgium


Brüssel SEW Caron-Vector S.A.Avenue Eiffel 5B-1300 Wavre


Service Compe-tence Center

Industrial Gears SEW Caron-Vector S.A.Rue de Parc Industriel, 31BE-6900 Marche-en-Famenne


Brazil

ProductionSalesService

Sao Paulo SEW-EURODRIVE Brasil Ltda.Avenida Amâncio Gaiolli, 152 - Rodovia Presi-dente Dutra Km 208Guarulhos - 07251-250 - SPSAT - SEW ATENDE - 0800 7700496


Additional addresses for service in Brazil provided on request!

Bulgaria

Sales Sofia BEVER-DRIVE GmbHBogdanovetz Str.1BG-1606 Sofia

Tel. +359 2 9151160Fax +359 2 [email protected]

Cameroon

Sales Douala Electro-ServicesRue Drouot AkwaB.P. 2024Douala

Tel. +237 33 431137Fax +237 33 431137



Canada


Toronto SEW-EURODRIVE CO. OF CANADA LTD. 210 Walker Drive Bramalea, Ontario L6T3W1


Vancouver SEW-EURODRIVE CO. OF CANADA LTD.7188 Honeyman Street Delta. B.C. V4G 1 E2


Montreal SEW-EURODRIVE CO. OF CANADA LTD.2555 Rue Leger LaSalle, Quebec H8N 2V9


Additional addresses for service in Canada provided on request!

Chile


Santiago de Chile

SEW-EURODRIVE CHILE LTDA.Las Encinas 1295Parque Industrial Valle GrandeLAMPARCH-Santiago de ChileP.O. BoxCasilla 23 Correo Quilicura - Santiago - Chile


China

ProductionAssemblySalesService

Tianjin SEW-EURODRIVE (Tianjin) Co., Ltd.No. 46, 7th Avenue, TEDATianjin 300457

Tel. +86 22 25322612Fax +86 22 [email protected]://www.sew-eurodrive.cn


Suzhou SEW-EURODRIVE (Suzhou) Co., Ltd.333, Suhong Middle RoadSuzhou Industrial ParkJiangsu Province, 215021


Guangzhou SEW-EURODRIVE (Guangzhou) Co., Ltd.No. 9, JunDa RoadEast Section of GETDDGuangzhou 510530


Shenyang SEW-EURODRIVE (Shenyang) Co., Ltd.10A-2, 6th RoadShenyang Economic Technological Develop-ment AreaShenyang, 110141


Wuhan SEW-EURODRIVE (Wuhan) Co., Ltd.10A-2, 6th RoadNo. 59, the 4th Quanli Road, WEDA430056 Wuhan

Tel. +86 27 84478398Fax +86 27 84478388

Additional addresses for service in China provided on request!

Colombia


Bogotá SEW-EURODRIVE COLOMBIA LTDA. Calle 22 No. 132-60Bodega 6, Manzana BSantafé de Bogotá


Croatia

SalesService

Zagreb KOMPEKS d. o. o.PIT Erdödy 4 IIHR 10 000 Zagreb




Czech Republic

Sales Praha SEW-EURODRIVE CZ S.R.O.Business Centrum Praha Lužná 591CZ-16000 Praha 6 - Vokovice

Tel. +420 255 709 601Fax +420 220 121 237http://[email protected]

Denmark


Kopenhagen SEW-EURODRIVEA/SGeminivej 28-30DK-2670 Greve


Egypt

SalesService

Cairo Copam Egypt for Engineering & Agencies33 EI Hegaz ST, Heliopolis, Cairo

Tel. +20 2 22566-299 + 1 23143088Fax +20 2 22594-757http://www.copam-egypt.com/ [email protected]

Estonia

Sales Tallin ALAS-KUUL ASReti tee 4EE-75301 Peetri küla, Rae vald, Harjumaa

Tel. +372 6593230Fax +372 [email protected]

Finland


Lahti SEW-EURODRIVE OYVesimäentie 4FIN-15860 Hollola 2

Tel. +358 201 589-300Fax +358 3 [email protected]://www.sew-eurodrive.fi

ProductionAssemblyService

Karkkila SEW Industrial Gears OYValurinkatu 6FIN-03600 Karkkila

Tel. +358 201 589-300Fax +358 201 [email protected]://www.sew-eurodrive.fi

Gabon

Sales Libreville Electro-ServicesB.P. 1889Libreville

Tel. +241 7340-11Fax +241 7340-12

Great Britain


Normanton SEW-EURODRIVE Ltd.Beckbridge Industrial Estate P.O. Box No.1GB-Normanton, West- Yorkshire WF6 1QR


Greece

SalesService

Athen Christ. Boznos & Son S.A.12, Mavromichali StreetP.O. Box 80136, GR-18545 Piraeus

Tel. +30 2 1042 251-34 Fax +30 2 1042 251-59http://[email protected]

Hong Kong


Hong Kong SEW-EURODRIVE LTD.Unit No. 801-806, 8th FloorHong Leong Industrial ComplexNo. 4, Wang Kwong Road Kowloon, Hong Kong

Tel. +852 2 7960477 + 79604654Fax +852 2 [email protected]



Hungary

SalesService

Budapest SEW-EURODRIVE Kft.H-1037 BudapestKunigunda u. 18

Tel. +36 1 437 06-58Fax +36 1 437 [email protected]

India


Vadodara SEW-EURODRIVE India Private LimitedPlot No. 4, GIDCPOR Ramangamdi • Vadodara - 391 243Gujarat

Tel. +91 265 2831086Fax +91 265 2831087http://[email protected]@seweurodriveindia.com

Ireland

SalesService

Dublin Alperton Engineering Ltd. 48 Moyle RoadDublin Industrial EstateGlasnevin, Dublin 11

Tel. +353 1 830-6277Fax +353 1 [email protected]://www.alperton.ie

Israel

Sales Tel-Aviv Liraz Handasa Ltd. Ahofer Str 34B / 22858858 Holon

Tel. +972 3 5599511Fax +972 3 5599512http://[email protected]

Italy


Milano SEW-EURODRIVE di R. Blickle & Co.s.a.s.Via Bernini,14 I-20020 Solaro (Milano)


Ivory Coast

Sales Abidjan SICASte industrielle et commerciale pour l'Afrique165, Bld de MarseilleB.P. 2323, Abidjan 08

Tel. +225 2579-44Fax +225 2584-36

Japan


Iwata SEW-EURODRIVE JAPAN CO., LTD 250-1, Shimoman-no,IwataShizuoka 438-0818


Korea


Ansan-City SEW-EURODRIVE KOREA CO., LTD. B 601-4, Banweol Industrial Estate 1048-4, Shingil-DongAnsan 425-120


Busan SEW-EURODRIVE KOREA Co., Ltd.No. 1720 - 11, Songjeong - dongGangseo-kuBusan 618-270


Latvia

Sales Riga SIA Alas-KuulKatlakalna 11CLV-1073 Riga

Tel. +371 7139253Fax +371 7139386http://[email protected]



Lebanon

Sales Beirut Gabriel Acar & Fils sarlB. P. 80484Bourj Hammoud, Beirut

Tel. +961 1 4947-86 +961 1 4982-72+961 3 2745-39Fax +961 1 4949-71 [email protected]

Lithuania

Sales Alytus UAB IrsevaNaujoji 19LT-62175 Alytus

Tel. +370 315 79204Fax +370 315 [email protected]://www.sew-eurodrive.lt

Luxembourg


Brüssel CARON-VECTOR S.A.Avenue Eiffel 5B-1300 Wavre


Malaysia


Johore SEW-EURODRIVE SDN BHD No. 95, Jalan Seroja 39, Taman Johor Jaya81000 Johor Bahru, JohorWest Malaysia


Mexico


Queretaro SEW-EURODRIVE MEXIKO SA DE CVSEM-981118-M93Tequisquiapan No. 102Parque Industrial QueretaroC.P. 76220Queretaro, Mexico


Morocco

Sales Casablanca Afit5, rue Emir AbdelkaderMA 20300 Casablanca

Tel. +212 22618372Fax +212 [email protected]

Netherlands


Rotterdam VECTOR Aandrijftechniek B.V. Industrieweg 175 NL-3044 AS RotterdamPostbus 10085NL-3004 AB Rotterdam


New Zealand


Auckland SEW-EURODRIVE NEW ZEALAND LTD. P.O. Box 58-428 82 Greenmount driveEast Tamaki Auckland


Christchurch SEW-EURODRIVE NEW ZEALAND LTD. 10 Settlers Crescent, FerrymeadChristchurch


Norway


Moss SEW-EURODRIVE A/SSolgaard skog 71N-1599 Moss

Tel. +47 69 24 10 20Fax +47 69 24 10 40http://[email protected]



Peru


Lima SEW DEL PERU MOTORES REDUCTORES S.A.C.Los Calderos, 120-124Urbanizacion Industrial Vulcano, ATE, Lima


Poland


Lodz SEW-EURODRIVE Polska Sp.z.o.o.ul. Techniczna 5 PL-92-518 Łódź


24 Hour Service Tel. +48 602 739 739(+48 602 SEW SEW)

[email protected]

Portugal


Coimbra SEW-EURODRIVE, LDA.Apartado 15 P-3050-901 Mealhada


Romania

SalesService

Bucureşti Sialco Trading SRL str. Madrid nr.4 011785 Bucuresti

Tel. +40 21 230-1328Fax +40 21 230-7170 [email protected]

Russia


St. Petersburg ZAO SEW-EURODRIVE P.O. Box 36 195220 St. Petersburg Russia

Tel. +7 812 3332522 +7 812 5357142Fax +7 812 3332523http://[email protected]

Senegal

Sales Dakar SENEMECA Mécanique GénéraleKm 8, Route de Rufisque B.P. 3251, Dakar

Tel. +221 338 494 770Fax +221 338 494 [email protected]

Serbia

Sales Beograd DIPAR d.o.o.Ustanicka 128aPC Košum, IV floorSCG-11000 Beograd

Tel. +381 11 347 3244 / +381 11 288 0393Fax +381 11 347 [email protected]

Singapore


Singapore SEW-EURODRIVE PTE. LTD. No 9, Tuas Drive 2 Jurong Industrial Estate Singapore 638644

Tel. +65 68621701Fax +65 68612827http://[email protected]

Slovakia

Sales Bratislava SEW-Eurodrive SK s.r.o.Rybničná 40SK-831 06 Bratislava

Tel. +421 2 33595 202Fax +421 2 33595 [email protected]://www.sew-eurodrive.sk

Žilina SEW-Eurodrive SK s.r.o.Industry Park – PChZulica M.R.Štefánika 71SK-010 01 Žilina




Banská Bystrica

SEW-Eurodrive SK s.r.o.Rudlovská cesta 85SK-974 11 Banská Bystrica


Košice SEW-Eurodrive SK s.r.o.Slovenská ulica 26SK-040 01 Košice


Slovenia

SalesService

Celje Pakman - Pogonska Tehnika d.o.o.UI. XIV. divizije 14SLO - 3000 Celje

Tel. +386 3 490 83-20Fax +386 3 490 [email protected]

South Africa


Johannesburg SEW-EURODRIVE (PROPRIETARY) LIMITEDEurodrive House Cnr. Adcock Ingram and Aerodrome RoadsAeroton Ext. 2Johannesburg 2013P.O.Box 90004Bertsham 2013


Capetown SEW-EURODRIVE (PROPRIETARY) LIMITED Rainbow ParkCnr. Racecourse & Omuramba RoadMontague GardensCape TownP.O.Box 36556Chempet 7442 Cape Town

Tel. +27 21 552-9820Fax +27 21 552-9830Telex 576 [email protected]

Durban SEW-EURODRIVE (PROPRIETARY) LIMITED2 Monaceo PlacePinetownDurbanP.O. Box 10433, Ashwood 3605


Spain


Bilbao SEW-EURODRIVE ESPAÑA, S.L. Parque Tecnológico, Edificio, 302E-48170 Zamudio (Vizcaya)


Sweden


Jönköping SEW-EURODRIVE ABGnejsvägen 6-8S-55303 JönköpingBox 3100 S-55003 Jönköping


Switzerland


Basel Alfred lmhof A.G.Jurastrasse 10 CH-4142 Münchenstein bei Basel


Thailand


Chonburi SEW-EURODRIVE (Thailand) Ltd.700/456, Moo.7, DonhuarohMuang Chonburi 20000


Slovakia



Tunisia

Sales Tunis T. M.S. Technic Marketing Service5, Rue El Houdaibiah 1000 Tunis

Tel. +216 71 4340-64 + 71 4320-29Fax +216 71 [email protected]

Turkey


Istanbul SEW-EURODRIVE Hareket Sistemleri San. ve Tic. Ltd. Sti. Bagdat Cad. Koruma Cikmazi No. 3 TR-34846 Maltepe ISTANBUL

Tel. +90 216 4419164, 3838014, 3738015Fax +90 216 3055867http://[email protected]

Ukraine

SalesService

Dnepropetrovsk SEW-EURODRIVEStr. Rabochaja 23-B, Office 40949008 Dnepropetrovsk


USA

ProductionAssemblySalesServiceCooporate Offices

Southeast Region

SEW-EURODRIVE INC. 1295 Old Spartanburg Highway P.O. Box 518Lyman, S.C. 29365

Tel. +1 864 439-7537Fax Sales +1 864 439-7830Fax Manufacturing +1 864 439-9948Fax Assembly +1 864 439-0566Fax Confidential/HR +1 864 949-5557http://[email protected]


Northeast Region

SEW-EURODRIVE INC. Pureland Ind. Complex 2107 High Hill Road, P.O. Box 481Bridgeport, New Jersey 08014


Midwest Region SEW-EURODRIVE INC.2001 West Main Street Troy, Ohio 45373


Southwest Region

SEW-EURODRIVE INC.3950 Platinum Way Dallas, Texas 75237


Western Region SEW-EURODRIVE INC. 30599 San Antonio St.Hayward, CA 94544


Additional addresses for service in the USA provided on request!

Venezuela


Valencia SEW-EURODRIVE Venezuela S.A.Av. Norte Sur No. 3, Galpon 84-319Zona Industrial Municipal NorteValencia, Estado Carabobo

Tel. +58 241 832-9804Fax +58 241 838-6275http://[email protected]@cantv.net


Index

Index

AAbsolute modulo positioning ..................................48Absolute positioning...............................................46AxisControlCam_MDX

Function block....................................................66AxisControlGear_MDX

Function block....................................................69AxisControl_MDX...................................................17AxisControl_MDX function block............................43AxisControl_MDX_SingleAxis Sample Project.......40AxisControl_MDX_SingleAxis.pro..........................12AxisControl_MDX_Technology ........................72, 81AxisControl_MDX_Technology project

Opening and starting..........................................61AxisControl_MDX_Technology.pro project

Adapting.............................................................62

CCommunication problems ......................................96

DData backup...........................................................88DHE41B .........................................................97, 100DHP11B ...........................................................96, 98

EElectronic cam (AM_CAMING) ..............................85

FFunction blocks ......................................................40Functionality of the application solution ...................7

HHoming...................................................................49

IInput and output assignment..................................44Integrating an automatic sequence........................30

JJog mode, position controlled ................................49Jog mode, speed controlled...................................48

MMOVIDRIVE® as master .......................................72

MOVIDRIVE® control ......................................20, 64MOVIDRIVE® control with

AxisControl_MDX_SingleAxis................................9MOVIDRIVE® requirements ....................................9

OOperating modes ...................................................40

PPLC Editor .............................................................12PROFIBUS ............................................................98Project extension ...................................................24

QQuestions...............................................................96

RRelative positioning................................................48

SSpeed control.........................................................48Startup ...................................................................11Startup of MOVIDRIVE® .......................................61Structure of the safety notes....................................5Synchronous operation

Additional settings..............................................63Synchronous operation of MOVIDRIVE® ..............60Synchronous operation (AM_GEARING) ..............86System requirements...............................................8

TTorque control operating mode..............................50

VVirtual encoder.....................................................101

SEW-EURODRIVE – Driving the world

How we’re driving the world

With people whothink fast anddevelop thefuture with you.

With a worldwide service network that isalways close at hand.

With drives and controlsthat automaticallyimprove your productivity.

With comprehensiveknowledge in virtuallyevery branch ofindustry today.

With uncompromisingquality that reduces thecost and complexity ofdaily operations.

With a global presencethat offers responsive and reliable solutions. Anywhere.

With innovativetechnology that solvestomorrow’s problemstoday.

With online informationand software updates,via the Internet, availablearound the clock.

Drive Technology \ Drive Automation \ System Integration \ Services

SEW-EURODRIVEDriving the world

www.sew-eurodrive.com

SEW-EURODRIVE GmbH & Co KGP.O. Box 3023 · D-76642 Bruchsal / GermanyPhone +49 7251 75-0 · Fax +49 7251 [email protected]

Documents

MOVI-PLC® Example Project Axis Control / Manuals ... – MOVI-PLC® AxisControl Application Solution 3 Contents Contents 1 General Information 5 1.1 Structure of the safety notes