6
mMINT—Modbus Translator Module—
installation and use
EATON CORPORATION
www.moeller.net/en/support
05/10 AWB1230-1622
Effective May 2010
Register access configurations
The following parameters can be set as configurations for
register access:
•
Register 42001/425347 (07D0
16
/6300
16
)
Reading a register group with invalid registers
When non-zero (factory default value), any attempt to access a
group of data objects that contain an invalid object will result in
an illegal data object exception code 02 . See Section 6 .
When the register is set to zero, however, the mMINT will respond
to a group of objects with data contained in the valid objects of the
group along with an illegal value that is set to 0000
16
.
•
Register 42002/425346 (07D1
16
/6301
16
)
Configuration of the 32-bit IEEE data format
When non-zero (factory default), the low floating point word is first
in the Modbus register space .
When the register is set to zero, the high floating point word is first
in the Modbus register space .
•
Register 42002/425347 (07D1
16
/6302
16
)
Sequence of the fixed point register
The register is used to configure 32-bit fixed point and 64-bit word
order . When non-zero (factory default), the low 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 space .
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 .
otee:
N
mMINT SW2-1 must be properly set . See Section 5 and
Table 5
.
Control commands
A set of registers is reserved for control commands . They begin
at register 42901/425089 (0B54
16
/6200
16
) and extend through
42903/425091 (0B56
16
/6202
16
) . These three registers include ‘slave
action numbers .’ Their meaning is listed in
Table 6
. The format of
the data is shown in
Figure 5
. These three registers must be written
in one Modbus transaction .
For safety reasons, a 1’s complement must be formed to correspond
with each slave action byte (1 to 0 and 0 to 1) . As illustrated in
Figure 5
. If the slave action request is successfully acknowledged
by the trigger, the mMINT returns a normal function code 16 (10
16
)
response to the Modbus master . The Modbus master may further
determine if the INCOM product completed the slave action function
successfully by interrogating the product, for example, by reading
its status .
If the INCOM product does not acknowledge the slave action
request, the mMINT returns an exception code 04 . If the ‘slave
action number’ and its 1’s complement are invalid, the mMINT
responds to the Modbus master with a data value illegal exception
code 03 .
Figure 5. Control to INCOM Product Data Format
Data format for energy values
Energy objects in the mMINT are supported in two-register fixed
point object format and a four-register power/mantissa format .
These objects do not support IEEE floating point format .
The two-register format is presented in kilowatt hours (kWh)
or in watthours .
The four-register format indicates the energy values in watthours .
These are register 3 through register 0 . Register 3 is of the highest
value and register 0 is of the lowest value .
Register 3 high byte contains a coefficient . Register 3 low byte
contains a Mantissa Multiplier value .
Register 2 through register 0 contains a 48-bit energy mantissa value
in watthours .
The data format of these four registers is illustrated in
Figure 6
.
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Register 42901/425089 (0B54
16
/6200
16
)
Slave Action Byte 1
Slave Action Byte 0
Register 42902/425090 (0B55
16
/6201
16
)
1’s Complement of Slave Action Byte 0
Slave Action Byte 2
Register 42903/425091 (0B56
16
/6202
16
)
1’s Complement of Slave Action Byte 2
1’s Complement of
Slave Action Byte 1
