![Eaton Cutler-Hammer Modbus mMINT Installation And Use Manual Download Page 6](http://html1.mh-extra.com/html/eaton/cutler-hammer-modbus-mmint/cutler-hammer-modbus-mmint_installation-and-use-manual_3833798006.webp)
Page 6
I.L. 66A7508H05
Effective September 2003
Non-volatile register 42002/425347 (07D1
16
/6302
16
) is used to
configure 32-bit fixed point and 64-bit energy word order.
When non-zero (factory default), the fixed point and energy low
order word is first in the Modbus register space.
When register 42003/425347 (07D2
16
/6302
16
) is set to zero,
however, the fixed point and energy high order word is first in
the Modbus register.
Registers not containing a 32-bit or 64-bit format such as
Status and Product ID objects, pass through registers, INCOM
control registers and INCOM routing address configuration
registers are not effected by the word order configuration
registers.
Configuring any or all registers 42001/425345 through
42003/425347 (07D0
16
/6300
16
through 07D2
16
/6302
16
) is
accomplished using a write function code 16 (10
16
) to mMINT
diagnostic address 247 or 248. Note that mMINT SW2-1 must
be properly set. See Section 5.8 and
Table 5
.
6.5 INCOM Routing Address Configurations
Non-volatile registers 42101 (0834
16
) through 42592 (0A1F
16
)
is used to configure the 246 Modbus-to-INCOM Routing
Address registers. Two consecutive INCOM routing registers
correspond to each Modbus address. The first register
provides routing to an INCOM main network address while the
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
Modbus address 2, etc.
Valid INCOM addresses range from 0001
16
through 0FFF
16
.
Invalid INCOM addresses are 0000
16
or Yxxx
16
, where Y is
non-zero. Any invalid (default) setting in the INCOM main
network address register will cause the mMINT to access the
INCOM product with the Modbus network address. A valid
INCOM main network address register with an invalid INCOM
sub-network address register will route the Modbus network
address to the INCOM product at the configured main network
address. Both a valid INCOM main network address register
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-
network master addressed at the INCOM main network
address.
All INCOM Routing Address Configuration registers can be
reset to their default state using the Diagnostics function code
08, sub-function 30 (1E
16
). See Section 6.9 and
Table 6
.
6.6 Command/Data Pass Through
A feature of the mMINT is its capability to pass INCOM
commands/data directly through to any of 32 attached INCOM
products. Thus, with access to IL 17384, Parts A through F,
every INCOM product object and capability is available to the
Modbus master.
When passing a command or data through to an INCOM
product, the mMINT acts as a dumb slave. Without
modification, it passes the command or data through to the
INCOM product.
In the event the product responds, the mMINT saves the
response until the Modbus master queries for that response.
The mMINT makes no modification to or interpretation of the
product response data.
The Modbus master writes the INCOM product command/data
using function code 16 (10
16
) beginning at register
42601/424577 (0A28
16
/6000
16
).
The data format for passing information through the mMINT to
an INCOM product is given in
Figure 6
.
The Modbus master reads the INCOM product response to a
pass through query using either function code 03 or 04
beginning at register 42701/424833 (0A8C
16
/6100
16
).
The number of points (registers) of the read query is 2*nn –
where nn is the number of INCOM messages in the response.
The format of the data acquired by the mMINT from the pass
through INCOM product query's response is given in
Figure 7
.
Note that each INCOM response message contains a status
byte which indicates its validity.
Figure 6: Pass Through To INCOM Product Query
Data Format
6.7 Control of INCOM Product
Since a control error could result in unwanted actions initiated
by an INCOM device, the mMINT requires a specific protocol
by the Modbus master in order to perform control related
functions within the INCOM product.
15 14 13 12 11 10
9
8
7
6
5
4
3
2
1
0
Register 42601/424577 (0A28
16
/6000
16
)
Register 42602/424578 (0A29
16
/6001
16
)
nn = Number of Response
Msgs
from
INCOM Product
INCOM Msg Byte0
15 14 13 12 11 10
9
8
7
6
5
4
3
2
1
0
INCOM Msg Byte1
INCOM Msg Byte2
0 = Reserved
0 = Data Msg / 1 = Control Msg
INCOM Msg Control Byte