Specifications

Application note Connecting CP600 to motion products via Modbus RTU AN00200-003
ABB Motion control products 2
www.abb.com/motion
Motion Product Configuration
Motion Product ConfigurationMotion Product Configuration
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/ESB
NextMove ES/ESBNextMove ES/ESB
NextMove ES/ESB-
--
-2 and e100 Product Configuration
2 and e100 Product Configuration2 and e100 Product Configuration
2 and e100 Product Configuration
As Modbus RTU is a serial-based protocol it is vital to ensure the motion product’s serial node address is set using either
BUSNODE(_busSERIAL1) in a Mint program or via the “Connectivity” screen within Mint Workbench, Address 0 should be avoided
as this is reserved for broadcast functions.
It is also necessary to set the required baud rate either using SERIALBAUD(_TERM1) in a Mint program or via the “Connectivity”
screen within Mint Workbench, The motion products do not support operation of Modbus RTU at 9600 baud and there are limited
selections of baud rate for the CP600 HMIs. Therefore the selection of baud rate is restricted to one of the following:
19200
38400
57600
All Modbus parameters are configured via the MODBUSPARAMETER Mint keyword.
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, and to configure how Modbus registers in the received data packets are mapped to internal
data areas in the Mint controller (see also application note AN00198).
As ABB PLC products use big endian byte order and big endian word order the Mint program needs to ensure the relevant Modbus
parameters are set accordingly (via the MODBUSPARAMETER keyword, typically as part of the Mint startup module) to ensure
connectivity between the CP600 HMI and any other networked ABB Modbus RTU devices (e.g. an AC500 PLC):
Example Mint code – Mint Modbus RTU slave connected to CP600 using Comms array
BUSNODE (_busSERIAL1) = 3 ‘Mint controller is node 3
SERIALBAUD (_TERM1) = 57600 ‘Using 57600 baud
MODBUSPARAMETER (_busSERIAL1, _mpBYTE_ORDER) = 0 ‘Use big endian byte order
MODBUSPARAMETER (_busSERIAL1, _mpWORD_ORDER) = 0 ‘Use big endian word order
MODBUSPARAMETER (_busSERIAL1, _mpREGISTER_MAPPING) = _rmCOMMS_ARRAY
MODBUSPARAMETER (_busSERIAL1, _mpENABLE) = 1
NextMove ES / ESB-2 only supports mapping of the Comms array to Modbus registers. When using e100 products, as an
alternative to the Comms array, it is also possible to map Net Data locations to Modbus registers by setting the
_mpREGISTER_MAPPING parameter to _rmNET_DATA.
Most new applications using e100 products are likely to utilise NetData as there are 1000 of these (as opposed to 99 Comms
locations) and 32 NetData events (as opposed to only 10 Comms events).
Applications using NextMove ES / ESB-2 are restricted to 5 Comms events (1 to 5). The operation of Mint events is detailed later in
this document.