Installation manual

Application note Getting started with e100 AN00187-002

ABB Motion control products 26

www.abbmotion.com

to define an object variable called “DriveA” to represent the MicroFlex e100 on EPL node 3. The pointer notation -> is used to

access the drives parameters such as HOMESPEED. Note the drive calls itself axis 0. All redirected parameters therefore refer to

axis 0.

Type the following code at the end of the program’s Startup block to set up the drive remotely for homing.

Dim DriveA As Controller= {_busETHERNET, 3} ‘Set redirection to Node3

DriveA->SCALEFACTOR(0) = 10000 ‘There are 10000 Counts/Rev

DriveA->HOMEINPUT(0) = 0 ‘The homing input is DIN0

DriveA->HOMEBACKOFF(0) = 10.0 ‘The back-off speed is 10% of the home speed

DriveA->HOMESPEED(0) = 5.0 ‘The homing speed is 5 Revs/s

DriveA->HOMEACCEL(0) = 10 ‘The home accel is 10 revs/s/s

DriveA->HOMEDECEL(0) = 20 ‘The home decel is 20 revs/s/s

Where to go from here ?

Where to go from here ?Where to go from here ?

Where to go from here ?

If you connected a digital input driven by the Emergency Stop circuit earlier you may now want to add some code to associate

some functionality with this input (before you start connecting loads to the motor for example).

Refer to application note AN00190 – Stop Handler Framework which can be downloaded from the Support area of

www.abbmotion.com for a description of how the stop related code in the Mint samples library can be used.

If you are used to programming Mint on earlier motion products there are differences between the NextMove e100 controller and

the analog NextMove series, commonly referred to as “Nextmove Classic” (e.g. Nextmove ESB-2). These differences are described

in Help file topics and other application notes. This section here is a guide to where to find this information.

Application Note 162

Application Note 162Application Note 162

Application Note 162-

-000 Moving from NextMove Classic to NextMove e100

000 Moving from NextMove Classic to NextMove e100000 Moving from NextMove Classic to NextMove e100

000 Moving from NextMove Classic to NextMove e100

This application note is an overview of the differences between the NextMove e100 and the non EPL NextMove series. The main

differences are:

Hardware: The IO on the NextMove e100 is different to the NextMove ESB2

Axis configuration: On the NextMove e100, this is done via Workbench and stored in a .dcf file. It cannot be changed in the

Mint program.

Axis Reset: This keyword is no longer supported on the NextMove e100.

Auxiliary Encoders: These are no longer supported on the NextMove e100.

Error Handling: This has been re-written for the e100 series. See the help file Contents->Mint Basic Programming->Error

Handling->Error Categories (e100)

Fast Position Capture: This functionality has been re-written on the e100 series to be channel based rather than axis based.

Read the Help file entry Contents->Hardware->Input/Output Handling->Fast Latching e100. Application

notes “AN177 Cut to registration” and “AN180 Product Synchronisation” contain good examples of how

this can be set up on an e100 system.

CAN Bus: The BaldorCAN protocol is not supported on NextMove e100. CANopen is still supported.

Others: A number of other keywords are modified or not supported. This is explained in more detail in AN162-000.