Specifications

ManualsBrandsABB ManualsConsumer electronicsMicroFlex e150

ABB Motion control products 1

www.abb.com/motion

Seamless high speed serial communication

between HMI and motion products

Introduction

IntroductionIntroduction

Introduction

The CP600 range of intelligent HMI panels is able to

communicate with other peripherals (e.g. AC500 PLCs, ABB motion products) via a selection of communication protocols. This

application note details how these HMIs can interface with ABB motion products via Modbus RTU. For general guidance on the use

of Panel Builder 600 please refer to ABB manual 2CDC159007M0201.

To configure a CP600 HMI to communicate with an ABB motion control product via Modbus RTU requires Panel Builder 600

version 1.80.00.34 (or later). Please contact your local Sales office if you need to update your existing version of this software.

Integrated Modbus RTU support is available on the following ABB motion control products:

NextMove ES / ESB-2

NextMove e100

MicroFlex e100

MotiFlex e100

MicroFlex e150

Refer to application note AN00198 for further details on the operation of Modbus RTU on these products.

Modbus RTU uses a serial-based physical medium (either RS232, 2 wire RS485 or 4 wire RS422 depending on product).

Refer also to application note AN00199 for details on connecting CP600 HMIs to ABB motion control products via Modbus TCP.

Motion Control Products

Application note

Connecting CP600 to motion products via Modbus RTU

AN00200-003

Summary of content (13 pages)

PAGE 1
Motion Control Products Application note Connecting CP600 to motion products via Modbus RTU AN00200-003 Seamless high speed serial communication between HMI and motion products Introduction The CP600 range of intelligent HMI panels is able to communicate with other peripherals (e.g. AC500 PLCs, ABB motion products) via a selection of communication protocols. This application note details how these HMIs can interface with ABB motion products via Modbus RTU.
PAGE 2
Application note Connecting CP600 to motion products via Modbus RTU AN00200-003 Motion Product Configuration Integrated Modbus RTU operation is included with the following firmware versions: e100 products - firmware version 5633 (or later) e150 products - firmware version 5707 (or later) NextMove ES / ESB2 - firmware version 5424 or later (compiler Target Format 13) or firmware version 5454 or later (compiler Target Format 14) NextMove ES/ESBES/ESB-2 and e100 Product Configuration As Modbus RTU is a seri
PAGE 3
Application note Connecting CP600 to motion products via Modbus RTU AN00200-003 e150 Product Configuration All Modbus parameters are configured via the ‘Configuration’ menu within Workbench once online to the product (and the resulting settings are stored on the product as part of its Mint Device Configuration (MDC) file). Before enabling Modbus operation it is necessary to set the correct byte and word order to suit the connected Modbus client (master), in this case the CP600 HMI.
PAGE 4
Application note Connecting CP600 to motion products via Modbus RTU AN00200-003 Register Mappings All CP600 Modbus functions target a common data area in the Mint controller (as set by the Mint keyword ModbusParameter (_mpREGISTER_MAPPING) if using a motion product other than e150 or fixed as Net data when using an e150 product).
PAGE 5
Application note Connecting CP600 to motion products via Modbus RTU AN00200-003 A dropdown control appears under the PLC heading, click on this to display the list of available protocols… We need to select the ABB Modbus RTU protocol. This is a client (master) protocol that allows the CP600 HMI to communicate with both ABB PLCs and motion control products. The ABB versions of Modbus protocols differ from the generic Modbus protocols available in two ways: 1. 2.
PAGE 6
Application note Connecting CP600 to motion products via Modbus RTU AN00200-003 The dialog changes slightly and now includes an additional area showing the slave devices that have been added to the Modbus RTU network. Click on the ‘Add’ button…the software now asks the user to enter details about the connected slave device….
PAGE 7
Application note Connecting CP600 to motion products via Modbus RTU AN00200-003 Baudrate should be set to match the connected slave device(s) – e.g. to match SERIALBAUD(_TERM1) of the connected motion product (remember that 9600 is not supported by ABB motion products).
PAGE 8
Application note Connecting CP600 to motion products via Modbus RTU AN00200-003 The field tab lets us program which memory location in the motion controller the Tag relates to. The available ‘Memory Type’ selections are specific to the PLC model selected as shown by the table below: PLC Type Comms Array Net Data NextMove ES/ESB-2 Yes No E100 motion product Yes Yes E150 motion product No Yes You should ensure that all tags used in the HMI project are setup to use a single Memory Type (i.e.
PAGE 9
Application note Connecting CP600 to motion products via Modbus RTU AN00200-003 If we now click OK the software allows us to enter a name for our newly created Tag… We can now click on the “+” button again to continue to add Tags to the project.
PAGE 10
Application note Connecting CP600 to motion products via Modbus RTU AN00200-003 End Bitfield Dim HMIBitData As BitData HMIBitData.DoubleWord = NETINTEGER(2) ‘Read all 32 bits into a bitfield variable OUTX(0) = HMIBitData.Bit19 ‘Set output 0 according to the value written by the HMI …and we could then use the following code to write to this bit… HMIBitData.Bit19 = INSTATEX(1) ‘set bit 19 to reflect the state of input 1 on the controller NETINTEGER(2) = HMIBitData.
PAGE 11
Application note Connecting CP600 to motion products via Modbus RTU AN00200-003 The ‘ArraySize’ field in the dialog determines the number of characters the string Tag can store. In this case 10 characters means the HMI will access COMMSINTEGER(1), COMMSINTEGER(2) and the top 16 bits of COMMSINTEGER(3).
PAGE 12
Application note Connecting CP600 to motion products via Modbus RTU AN00200-003 Physical Connection The table below shows the physical connection possibilities for Mint products supporting integrated Modbus protocols. AC500 and CP600 products are included for reference.
PAGE 13
Application note Notes: 1. 2. 3. 4. 5. 6. Connecting CP600 to motion products via Modbus RTU AN00200-003 The 7v output on MicroFlex / MotiFlex e100 and e150 products should not be connected.