![Mean Well CMU2C Installation Manual Download Page 40](http://html1.mh-extra.com/html/mean-well/cmu2c/cmu2c_installation-manual_1757957040.webp)
73
5
Byte0
Byte0
Byte0
Byte 0 ------------------------------------------------------------------------------ ByteN
Byte6
0xFE
0x31
0x31
Max10 Bytes
Max 0 Bytes
2
Max10 Bytes
Max 18 Bytes
1Byte
1Byte
1Byte
1Byte
Device
Event
date
time
,
,
space
\
n
0x30
0x69
0x38
0x38
0x30
0xFF
0x30
0x30
0x30
0xFF
0x31
0x31
0x30
0xFF
0x30
0x30
0x30
0xFF
0x31
0x31
0x31
Byte1
Byte1
Byte1
Byte7
Byte2
Byte2
Byte2
Byte8
Byte3
Byte3
Byte3
Byte9
Byte4
Byte4
Byte4
Byte10
Byte5
Byte5
Byte5
Byte11
MFR_DATE_B0B5 is manufacture date (ASCII)
EX: MFR_DATE_B0B5 is 180101, meaning 2018/01/01
MFR_SERIAL_B0B5(0x30*N ~0x30*N) and MFR_
SERIAL_B6B11(0x30*N ~ x0229+0x30*N) are defined as
0
manufacture date and manufacture serial number (ASCII)
Event Log(0x6000~0x07F3F) Data structure Definition
EX: The first unit manufactured on 2018/01/01 MFR_SERIAL_B0B5:
;
180101
MFR_SERIAL_B6B11 is 000001
Event data store as ASCII strings. Maximum bytes for a No. resistor is 62
bytes, data length is dependent on its actual content. If no data that exists,
it will display 0x00
.
※
N means data length, maximum length is 27 bytes.
※
0
Byte
sends first
MFR_REVISION_B0B5 (0x30*N ~0x30*N) is the firmware
revision (hexadecimal). A range of 0x00 (R00.0) ~ 0xFE (R25.4) represents
the firmware version of a MCU; 0xFF represents on MCU existed
EX: The supply has two MCUs. The firmware version of the MCU number1 is
version R25.4(0xFE), the MCU number 2 is version R10.5 (0x69)
74
5
Device
(Max 10 Bytes)
System
PSU_00
~
PSU_47
Please refer to 5.11.3.7.3 for an event log query
.
Request:
1、EEPROM Error
2、EEPROM Error
Remove
3、Model Error
4、Model Error
Remove
5、Comm. Error
、Comm. Err
6
Remove
1、OVP
2、OVP Remove
3、OLP
4、OLP Remove
5、Short
6、Short Remove
7、OTP
8、OTP Remove
9、AC Fail
10、AC Fail Remove
11、FAN Lock
1 、FAN Lock Remove
2
HH:MM:SS
20YY/MM/DD
Event
(Max 20 Bytes)
Time
(Max 8 Bytes)
Date
(Max 10 Bytes)
5.3.6 Communication Examples
The following provides examples of request and response for
each function code of the Modbus TCP protocol.
5.3.6.1
Read Holding Registers (FC=03)
The request message specifies the starting register and
quantity of registers to be read.
For example: Client requests the content of analog output
holding registers 0x021C – 0x021E
(MFR_REVISION_B0B5) from the server
0x00020000000601: MBAP Header
0x03: Function code 3 ( ead Analog Output Holding
R
Registers)
0x0
C: The Data Address of the first register requested.
21
0x0003: The total number of registers requested ( ead 3
R
registers from 0x021C to 0x021E)
0x00020000000601
0x03
0x021C
0x
3
000