Eaton mMINT, Инструкция по установке и эксплуатации

Страница: 7 / 24

7
05/10 AWB1230-1622
Effective May 2010
mMINT—Modbus Translator Module—
installation and use
EATON CORPORATION www.moeller.net/en/support
Figure 6. Four-Register Energy Data Format
Supported diagnostic sub-functions
It is possible to obtain diagnostics from the mMINT or an attached
INCOM product using function code 08 . See Table 6 . A single
register is used for each UART counter within the mMINT . Each
INCOM device and the mMINT contain a unique slave counter .
To use mMINT address 247 or 248 in the diagnostic query, SW2-1
must be properly set . See Section 6 and
Table 6
.
Exception codes
•
Under certain circumstances, the mMINT will return an
exception code
•
If the function in the query is not supported by the mMINT,
exception code 01 is returned in the response
•
If the data (object) register is illegal, exception code 02
is returned in the response
•
If the data value in the query is illegal, exception code 03
is returned
•
If the slave INCOM product fails (usually a timeout), exception
code 04 is returned
•
In certain circumstances, an exception code 05 (ACK) is returned .
•
If the mMINT cannot perform the requested function, exception
code 07 (NAK) is returned
•
If only a partial register is used in the query, exception code 84
is returned
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
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Energy Register 0
Byte 1 of Mantissa
Byte 0 of Mantissa
Energy Register 1
Byte 3 of Mantissa
Byte 2 of Mantissa
Energy Register 2
Byte 5 of Mantissa
Byte 4 of Mantissa
Energy Register 3
Coefficient
Mantissa Multiplier
Energy = 2
Mantissa Multiplier
* Mantissa * 10
Coefficient
Table 6. Diagnostic Sub-Function Numbers
Sub-function No.
(Decimal) Name In the Query Use
0 echo query or INCOM addr
1 restart communications mMINT or INCOM addr
4 force listen mMINT or INCOM addr
10 clear slave counters mMINT or INCOM addr
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
14 slave message count mMINT or INCOM addr
15 slave no response count mMINT or INCOM addr
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
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
24 UART noise error count mMINT or INCOM addr
25 UART parity error count mMINT or INCOM addr
26 mMINT firmware version & rev mMINT addr
27 mMINT firmware month & day mMINT addr
28 mMINT firmware year mMINT addr
29 remove INCOM device(s) mMINT or INCOM addr
Section 7: Troubleshooting
The most common issues experienced with the installation of an
mMINT module are addressed below .
Table 7. Troubleshooting Guide
Symptom Possible Solution(s)
Status LED not flashing Verify proper input power to module connector
Modbus Tx LED is flashing, but the
module does not respond to master
command requests
Verify communication cable is connected correctly
from the master to the module (A, B, +, –)
Verify the data transfer rate is correctly set using
baud rate switch (SW2)
INCOM Tx LED is flashing, but the
module does not respond to master
command requests
Verify communication cable is connected correctly
from the slave to the module
Verify the product is set up for 9600 baud
Verify that the load resistance (SW1) is set to ON
at the last module