Professional Documents
Culture Documents
66A7508H07
Page 1
Figures
Figure 1: The mMINT Module.......................................................1
Figure 2: mMINT in a Communications Network.......................2
Figure 3: Connections ....................................................................3
Figure 4: Indicators .........................................................................4
Figure 5: Switches ...........................................................................4
Figure 6: Pass Through To INCOM Product Query Data
Figure 1: The mMINT Module Format.....................................................................................6
Figure 7: Pass Through To INCOM Product Response Data
Format.....................................................................................7
Figure 8: Control To INCOM Product Data Format...................7
Figure 9: 4-Register Energy Data Format...................................8
CONTENTS
Description
1.0 GENERAL DESCRIPTION........................................................ 2
Tables
2.0 FEATURES ............................................................................... 2
3.0 INSTALLATION......................................................................... 2 Table 1: Power Connector Pin Outs ............................................3
3.1 Module Mounting..............................................................2 Table 2: INCOM Connector Pin Outs ..........................................3
3.2 Simplified Wiring Rules ...................................................2 Table 3: Modbus RS485 Connector Pin Outs ............................3
3.2.1 INCOM Network.....................................................2 Table 4: RS485 Baud Rate Switches (Normal)..........................4
3.2.2 Modbus RS485 Network ......................................3 Table 5: RS485 Baud Rate Switches (Diagnostics)..................5
4.0 mMINT MODULE CONNECTIONS ........................................... 3 Table 6: Diagnostic Sub Function Numbers ...............................8
4.1 Power Connections ..........................................................3 Table 7: Modbus Register Map (in Register Number Order).10
4.2 INCOM Connections ........................................................3 Table 8: Modbus Register Map (in Functional Order).............12
4.3 Modbus Connections .......................................................3 Table 9: Primary Status Code Definitions .................................14
5.0 SWITCHES AND INDICATOR LEDS ........................................ 4 Table 10: Secondary Status Code Definitions .........................14
5.1 Modbus RS485 Network Rx LED [Green]....................4 Table 11: Cause – of – Status Code Definitions .......................15
5.2 Modbus RS485 Network Tx LED [Green].....................4 Table 12: Control 'Slave Action Number' Definitions ..............17
5.3 INCOM Network Rx LED [Green]..................................4 Table 13: mMINT Configuration Registers...............................18
5.4 INCOM Network Tx LED [Green]...................................4
5.5 Status LED [Green]..........................................................4
5.6 INCOM 100 Ω Termination Dip Switch (SW1) ............4
5.7 Modbus RS485 Baud Rate Dip Switch (SW2) ............4
5.8 Unique mMINT Address (SW2) .....................................4
5.9 Modbus 121 Ω Termination Dip Switch (SW3)............5
6.0 NETWORK COMMUNICATION PROTOCOLS......................... 5
6.1 Overview............................................................................5
Effective December 2004
Page 2
I.L. 66A7508H07
The mMINT module is a slave device on the Modbus network 3.1 Module Mounting
and as such requires a master that will exchange register
objects with the mMINT module. When mounting the mMINT verify that an 11mm H x 28mm W
DIN Rail is used and that it is within an enclosed space.
• Handles generic pass though commands (Modbus/IN-
COM/Modbus). 3.2 Simplified Wiring Rules
• Capable of passing Modbus register objects from Cutler- 3.2.1 INCOM Network
Hammer’s existing products and newer PnP (Plug-‘n-Play)
products to a Modbus RTU master. The following simplified rules apply to a given system
consisting of a single daisy chained main cable link between
• Data in IEEE Floating Point format and fixed point. master and slave devices (see Figure 2). For more complex
considerations including star configurations, please refer to the
• Modbus RTU communications data transfer rates of 1200, IMPACC wiring specification T.D. 17513.
9600, or 19200 baud with 1 start bit, 8 data bits, no parity
and either one or two stop bits.
3.0 INSTALLATION
RS485 Network-A is the non-inverting differential connection This indicator will be flashing whenever the module is powered
for the Modbus RTU network. RS485 Network-B is the up and the microcontroller is executing instructions. The
inverting differential connection for the Modbus RTU network. flashing rate is approximately 1 second ON / 1 second OFF.
However, detection of a communications error on either the
Modbus or INCOM network will result in an increased flashing
rate approximately ½ second ON / ½ second OFF. The rate
will return to normal when the network's diagnostic reset
subfunction (clear UART or slave counters, respectively) is
processed by the mMINT. See Section 6.9 and Table 6.
Figure 4: Indicators
Figure 5: Switches
5.0 SWITCHES AND INDICATOR LEDS
Refer to Figure 4 to locate the status LED for the mMINT 5.6 INCOM 100 Ω Termination Dip Switch (SW1)
module. Figure 5 shows the location of the configuration
This switch should be moved to the “ON” position only when it
switches.
is the last unit in a chain of units or if it is a single unit.
5.1 Modbus RS485 Network Rx LED [Green]
5.7 Modbus RS485 Baud Rate Dip Switch (SW2)
The LED will be lighted whenever the module is receiving from
To configure the data transfer rate for the Modbus RTU
the Modbus RTU network.
network, three switches in dip switch SW2 should be moved to
either the “CLOSE” or the “OPEN” position based on the rate
5.2 Modbus RS485 Network Tx LED [Green] required. Refer to Table 4. SW2-1 is for mMINT diagnostics.
The LED will be lighted whenever the module is transmitting on
the Modbus RTU network. Baud SW2-1 SW2-2 SW2-3
1200 X CLOSE CLOSE
5.3 INCOM Network Rx LED [Green] 9600 X OPEN CLOSE
19200 X CLOSE OPEN
The LED will be lighted whenever the module is receiving from
the INCOM network.
Table 4: RS485 Baud Rate Switches (Normal)
5.4 INCOM Network Tx LED [Green]
5.8 Unique mMINT Address (SW2)
The LED will be lighted whenever the module is transmitting on
The mMINT can be assigned address 247 and 248. For the
the INCOM network. mMINT to respond to a diagnostic query related to address
247 or 248 on the Modbus network, move dip switch SW2-1 to
5.5 Status LED [Green] the “OPEN” position. Refer to Table 5. Normally, this switch is
in the “CLOSE” position.
5.9 Modbus 121 Ω Termination Dip Switch (SW3) A block of registers (from the register column of Table 7 or
Table 8) can be established for each INCOM product attached
This switch should be moved to the “ON” position only when it to a mMINT.
is the last unit in a chain of units or if it is a single unit.
Function code 16 (1016) is used to load the object assignments
for the block of registers. The block assignments are stored
6.0 NETWORK COMMUNICATION PROTOCOLS beginning at register 41001/420481 (03E8 16/500016). Only the
first object register address is assigned within the block of
The lower INCOM communication network for the mMINT is registers. For example, although object IA occupies registers
based on a master-slave protocol. The mMINT is a master on 404611 (120216) and 404612 (120316), only register address
the INCOM network. (120216) is loaded into the block of assignment registers.
Verification of this block of assignment registers can be read
In order to satisfy the mMINT communications needs, please from the mMINT by a read function code 03 or 04 from these
see Reference Materials: 41001/420481 (03E816/500016) registers.
IL17384 - Part A: IMPACC Communications Standard, Data pertaining to the objects configured in the block of
EATON, Cutler-Hammer. Specific product profiles are located assignment registers is mapped into registers starting at
in the other Part sections. 41201/420737 (04B016/510016) and continuing in successive
http://www.eatonelectrical.com , then search on 17384. order for each object assigned. The number of objects and
their placement order in this data block of registers is
“Modicon Modbus Protocol”, dependent on the configuration of the block of assignment
http://www.modicon.com/techpubs/toc7.html registers. The total number of data block of registers is limited
to 100. Note that an object can occupy one, two or four
6.1 Overview registers.
The contents of Modbus registers are INCOM product objects The data can be obtained from the data block of registers by a
(e.g. IA – phase A current). The mMINT ensures that unique read function code 03 or 04. The address of the starting object
objects reside in identical registers independent of INCOM must be aligned with a starting address of an object within the
product. Consequently, for all INCOM products there is a data block of registers. The number of registers to obtain must
single register map of objects. See Table 7 or Table 8. align with an ending address of an object within the data block
of registers.
INCOM objects occupy two (2) registers except for certain
energy – real and reactive – objects. These energy objects 6.4 Register Access Configurations
occupy four (4) registers. The mMINT can support a maximum
of 122 registers within a single Modbus transaction. Non-volatile register 42001/425345 (07D016/630016) is used to
configure the mMINT to respond to a group of data objects, of
The mMINT is transparent to the Modbus master and responds which some objects are invalid within that group. When
to every address of INCOM products attached to it. In its non-zero (factory default value), any attempt to access a group
default configured state, INCOM product addresses are of data objects which contain an invalid object will result in an
Modbus network addresses. The mMINT can be configured to illegal data object exception code 02. See Section 6.10.
route the Modbus address to a different INCOM product
address or an INCOM sub-network product address. See When register 42001/425345 (07D016/630016) is set to zero,
Section 6.5. however, the mMINT will respond to a group of objects with
data contained in the valid objects of the group along with an
An upgrade has been incorporated to allow the mMINT to illegal value, if available else 000016, data contained in the
communicate with Modbus masters which can only access to invalid objects.
register 9999. Registers previously assigned above 9999 have
been assigned dual access, both at the original register (to Non-volatile register 42002/425346 (07D116/630116) is used to
provide compatibility) and at a new register assignment below configure 32-bit IEEE floating point word order. When
9999. The format is given as low/high register numbers non-zero (factory default), the floating point low order word is
followed by (low16/high16 Modbus register addresses), for first in the Modbus register space.
example: 4xxxx/4yyyyy (XXXX+116/YYYY+116). See Table 13.
When register 42002/425346 (07D116/630116) is set to zero,
Only the RTU communications mode is recognized by the however, the floating point high order word is first in the
mMINT. Modbus register space.
Configuring any or all registers 42001/425345 through The data format for passing information through the mMINT to
42003/425347 (07D016/630016 through 07D216/630216) is an INCOM product is given in Figure 6.
accomplished using a write function code 16 (10 16) to mMINT
diagnostic address 247 or 248. Note that mMINT SW2-1 must The Modbus master reads the INCOM product response to a
be properly set. See Section 5.8 and Table 5. pass through query using either function code 03 or 04
beginning at register 42701/424833 (0A8C16/610016).
6.5 INCOM Routing Address Configurations The number of points (registers) of the read query is 2*nn –
where nn is the number of INCOM messages in the response.
Non-volatile registers 42101 (083416) through 42592 (0A1F16)
is used to configure the 246 Modbus-to-INCOM Routing The format of the data acquired by the mMINT from the pass
Address registers. Two consecutive INCOM routing registers through INCOM product query's response is given in Figure 7.
correspond to each Modbus address. The first register Note that each INCOM response message contains a status
provides routing to an INCOM main network address while the byte which indicates its validity.
second (first+1) register provides routing to an INCOM sub-
network address. Registers 42101 and 42102 correspond to
Modbus address 1, registers 42103 and 42104 correspond to Register 42601/424577 (0A28 16/6000 16)
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Modbus address 2, etc.
Valid INCOM addresses range from 0001 16 through 0FFF16. nn = Number of Response
Invalid INCOM addresses are 000016 or Yxxx16, where Y is Msgs from
non-zero. Any invalid (default) setting in the INCOM main INCOM Product
network address register will cause the mMINT to access the 0 = Reserved
INCOM product with the Modbus network address. A valid 0 = Data Msg / 1 = Control Msg
INCOM main network address register with an invalid INCOM
sub-network address register will route the Modbus network
INCOMMsg Control Byte
address to the INCOM product at the configured main network
address. Both a valid INCOM main network address register INCOMMsg Byte0
and INCOM sub-network address register will route the
Modbus network address to an INCOM product at the
configured sub-network address accessed through a sub- Register 42602/424578 (0A2916 /600116 )
network master addressed at the INCOM main network 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
address.
INCOM Msg Byte1
All INCOM Routing Address Configuration registers can be INCOM Msg Byte2
reset to their default state using the Diagnostics function code
08, sub-function 30 (1E16). See Section 6.9 and Table 6.
Figure 6: Pass Through To INCOM Product Query
Data Format
6.6 Command/Data Pass Through
6.7 Control of INCOM Product
A feature of the mMINT is its capability to pass INCOM
commands/data directly through to any of 32 attached INCOM Since a control error could result in unwanted actions initiated
products. Thus, with access to IL 17384, Parts A through F, by an INCOM device, the mMINT requires a specific protocol
every INCOM product object and capability is available to the by the Modbus master in order to perform control related
Modbus master. functions within the INCOM product.
A set of registers is reserved for the control protocol. They If the 'slave action number' and its 1's complement are valid,
begin at register 42901/425089 (0B5416/620016) and extend the mMINT issues the 'slave action' control command onto the
through 42903/425091 (0B56 16/620216). These three registers INCOM network. If the slave action request is successfully
are written with a 'slave action number' and its 1's complement acknowledged by the INCOM product, the mMINT returns a
using function code 16 (1016). The current 'slave action normal function code 16 (1016) response to the Modbus
numbers', their support being product dependent, are listed in master. The Modbus master may further determine if the
Table 12. The format of the data is shown in Figure 8. These INCOM product completed the slave action function
three registers, and only these three registers, must be written successfully by interrogating the product, for example, by
in one Modbus transaction. reading its status.
...
Byte2 of INCOM Response Msg 1
Register 2 through registers 0 contains a 48-bit energy If the function in the query is not supported by the mMINT,
mantissa in units of watthours. Net and total energy objects exception code 01 is returned in the response.
are signed values. All other energy objects are unsigned
values. If the data (object) register is illegal, exception code 02 is
returned in the response.
The data format of these 4 registers is given in Figure 9.
If the data value in the query is illegal, exception code 03 is
Energy = 2Mantissa Multiplier x (48-bit energy value) returned.
x 10Engineering Units .
If the slave INCOM product fails (usually a timeout), exception
code 04 is returned.
Energy Register 0
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 In certain circumstances, an exception code 05 (ACK) is
returned.
Byte0 of Mantissa If the mMINT cannot perform the requested function, exception
Byte1 of Mantissa code 07 (NAK) is returned.
Energy Register 1 If only a partial register is used in the query, exception code 84
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 is returned.
Byte2 of Mantissa
Byte3 of Mantissa Sub-
function
Energy Register 2
No. # Name in the query use
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
(decimal)
0 echo query mMINT or INCOM addr
Byte5 of Mantissa
Byte4 of Mantissa 1 restart communications mMINT or INCOM addr
4 force listen mMINT or INCOM addr
Energy Register 3 10 clear slave counters mMINT or INCOM addr
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 11 UART bus message count mMINT or INCOM addr
12 UART communication error count mMINT or INCOM addr
13 slave exception error count mMINT or INCOM addr
Mantissa Multiplier
Engineering Units 14 slave message count mMINT or INCOM addr
15 slave no response count mMINT or INCOM addr
Energy = 2 Mantissa Multiplier * Mantissa * 10 Engineering Units 16 slave NAK count mMINT or INCOM addr
17 slave busy count mMINT or INCOM addr
18 UART over run error count mMINT or INCOM addr
Figure 9: 4-Register Energy Data Format
20 clear UART counters mMINT or INCOM addr
21 slave INCOM BCH error count INCOM device addr
22 slave INCOM over run count INCOM device addr
23 UART framing error count mMINT or INCOM addr
6.9 Supported Diagnostic Sub-Functions 24 UART noise error count mMINT or INCOM addr
25 UART parity error count mMINT or INCOM addr
It is possible to obtain diagnostics from the mMINT or an 26 mMINT firmware version & rev mMINT addr
attached INCOM product using function code 08. See Table 6.
A single register is used for each UART counter within the 27 mMINT firmware month & day mMINT addr
mMINT. Each INCOM device and the mMINT contain a unique 28 mMINT firmware year mMINT addr
slave counter. 29 remove INCOM device(s) mMINT or INCOM addr
30 reset INCOM routing addresses mMINT addr
To use mMINT address 247 or 248 in the diagnostic query
SW2-1 must be properly set. See Section 5.8 and Table 5.
Table 6: Diagnostic Sub Function Numbers
3. Verify that the termination switch (SW1) is set to ‘ON’ 10. Power wiring is any approved 300 volt, 10 Amp, 30-12
at the last module. AWG (stranded or solid).
• Removing an INCOM product and assigning its INCOM 11. The register map for INCOM products is shown in
(Modbus) address to another (different) INCOM register number order in Table 7 and functional order
product., and exception codes are received from the in Table 8. Numeric entries indicated with an asterisk
INCOM product (*) have specific definitions dependent upon the
particular INCOM product. These tables include only
1. Disconnect the reassigned product from the INCOM a partial list of applicable INCOM products; however,
network. it contains a complete list of the INCOM objects
directly supported by the mMINT. Due to the mMINT
2. Verify that the Modbus Master has sent at least two pass through feature all INCOM product objects are
requests to the address of the product that was just accessible by a Modbus Master.
disconnected.
12. The primary and secondary codes are mapped to the
3. Connect the reassigned INCOM product. high and low bytes, respectively, of registers 404609
(120016) and 406145 (1800 16). The primary status
codes are shown in Table 9. The secondary status
codes are shown in Table 10. The cause-of-status
codes are mapped to registers 404610 (120116) and
406146 (180116). The cause-of-status codes are
shown in Table 11.
Objects - (complete list) Register Number Modbus Address INCOM Products - (partial list)
Digitrip 520MC
IQ Data Plus II
IQ Transfer II
DigiTrip 3000
MPCV Relay
Digitrip 1150
Digitrip 810
Digitrip 910
IEEE Fixed IEEE Fixed
IQ Analyzer
DP-4000
MP 3000
FP 5000
IQ Data
float point float point
IQ-200
Name Numeric Units
(FP) (FP)
(hex) (hex)
Objects - (complete list) Register Number Modbus Address INCOM Products - (partial list)
Digitrip 520MC
IQ Data Plus II
IQ Transfer II
MPCV Relay
Digitrip 1150
Digitrip 3000
Digitrip 810
Digitrip 910
IEEE Fixed IEEE Fixed
IQ Analyzer
DP-4000
MP 3000
FP 5000
IQ Data
float point float point
IQ-200
Name Numeric Units
(FP) (FP)
(hex) (hex)
Objects - (complete list) Register Number Modbus Address INCOM Products - (partial list)
Digitrip 520MC
IQ Data Plus II
MPCV Relay
Digitrip 1150
IQ Transfer II
Digitrip 3000
Digitrip 810
Digitrip 910
IEEE Fixed IEEE Fixed
IQ Analyzer
DP-4000
MP 3000
FP 5000
IQ Data
float point float point
IQ-200
Units
Name numeric (FP) (FP)
(hex) (hex)
Objects - (complete list) Register Number Modbus Address INCOM Products - (partial list)
Digitrip 520MC
MPCV Relay
IQ Data Plus
Digitrip 1150
IQ Transfer II
Digitrip 3000
Digitrip 810
Digitrip 910
IEEE Fixed IEEE Fixed
IQ Analyzer
DP-4000
MP 3000
FP 5000
IQ Data
float point float point
IQ-200
Units
Name numeric (FP) (FP)
(hex) (hex)
The sale of the product shown in this literature is subject to the terms
and conditions outlined in appropriate Cutler-Hammer, Inc., selling
policies or other contractual agreements between the parties. This
literature is not intended to and does not enlarge or add to any such
contract. The sole source governing the rights and remedies of any
purchaser of this equipment is the contract between the purchaser and
Cutler-Hammer, Inc.
Cutler-Hammer
Pittsburgh, PA U.S.A.
Printed in U.S.A.