Digital Excitation Systems

Communication Manual
for HDEC2000 and HDEC1000

R D

R
D

Electro Electric Systems

 Communication Manual Rev. A

Important Notice
The examples and diagrams in this manual are included solely for illustrative purposes. Because of
many variables and requirements associated with any particular installation, Hyundai Heavy
Industries Co., Ltd cannot assume responsibility or liability for actual use based on the examples
and diagrams.

Hyundai Heavy Industries Co., Ltd cannot accept any responsibility for damage incurred as a result
of mishandling the equipment regardless of whether particular reference is made in this instructions
or not.

The availability and design of all features and options are subject to modification without notice.
Should further information be required, contact Hyundai Heavy Industries Co., Ltd.

Reproduction of the contents of this manual, in whole or in part, without permission of Hyundai
Heavy Industries Co., Ltd is prohibited.

Manufacturer’s Address
Electro Electric Systems, Hyundai Heavy Industries Co., Ltd
Internet: http://www.hyundai-elec.co.kr

Headquarters (Rotating Machinery Design Department):

#1, Jeonha-dong, Dong-gu, Ulsan, Korea
Telephone: +82 52 202 6612
Fax : +82 52 202 6995

Seoul Office (Rotating Machinery Sales Department):

Hyundai building, 140-2, Kye-dong, Chongro-gu, Seoul, Korea
Telephone: +82 2 746 7668
Fax : +82 2 746 7646

Service Inquiries: +82 52 202 6671

Hyundai Heavy Industries Co., Ltd 2 Electro Electric Systems
 Communication Manual Rev. A

CONTENTS

INTODUCTION …………………………………………………….…………………………………….3

HARDWARE and CONFIGURATION ……………………..….………………………….……….. 3

MODEBUS PROTOCOL ………………………….……….………………………………….……… 5

MODEBUS MESSAGE STRUCTURE ……………….……….…………………………………… 6

Revision History …………………………….…………………….……………………………..…… 11

Hyundai Heavy Industries Co., Ltd 3 Electro Electric Systems

 Communication Manual Rev. A

INTRODUCTION
This manual describes the remote access via the MODBUSTM protocol over the RS485 communication link
for HDEC2000 and HDEC1000 voltage regulator.

At the present time, the read (monitoring) function for some operating parameters is only supported. However,
the upgrade (expansion of readable parameter and the adding of write function) is planned later.

HARDWARE and CONFIGURATION

Wiring, hardware configuration and communication parameter settings for RS485 communication are
described in the user’s manual of corresponding voltage regulator (HDEC1000 and HDEC2000). See below
parts of user manual of voltage regulator.

Table 1 Reference information for RS485 (HDEC2000 user’s manual – Rev.D)

Page No. Description
z Typical wiring diagram for RS485 communication
22 …23 z Cabling (wiring) guide for RS485 communication
z Terminal block designation for RS485 communication
27 z Hardware (toggle switch) setting for RS485 communication
62 z Setting screen of communication parameter
63 z Configuration of parameter for MODBUS communication
100 z Parameter lists of MODBUS communication

Table 2 Reference information for RS485 (HDEC1000 user’s manual – Rev.A)

Page No. Description
z Typical wiring diagram for RS485 communication
18 …19 z Cabling (wiring) guide for RS485 communication
z Terminal block designation for RS485 communication
22 z Hardware (jumper) setting for RS485 communication
52 z Setting screen of communication parameter
53 z Configuration of parameter for MODBUS communication
81 z Parameter lists of MODBUS communication

The firmware version which supports RS485 communication is V1.20 (or later) for HDEC2000 and V1.0 (or
later) for HDEC1000.

For proper operation (communication), all communication parameter should be configured correctly.
The default value and the programmable range of each communication parameters are listed in Table 3. And
the programmable parameter can be changed by HDCM configuration software. For more information about
HDCM software, see section 4 of HDEC2000 (HDEC1000) user’s manual.

Hyundai Heavy Industries Co., Ltd 4 Electro Electric Systems

 Communication Manual Rev. A

Table 3 Summary of Communication Parameter

Parameter Default Value Programmable Range
Slave address 247 1 …247
Baud rate 9600 2400, 4800, 9600, 19200bps
Data bit 8 fixed value
Parity bit N fixed value (*1)
Stop bit 1 fixed value (*1)
Response delay 10ms 0 …200ms
(*1) marked parameter will be changed with programmable

MODBUS PROTOCOL
The MODBUS serial line protocol is a master-slaves protocol. Only one master can initiate MODBUS
transaction called a query. When a MODBUS master communicates with a slave, information is requested by
the master. When a slave receives a query, the slave responds by supplying the requested data.

Two different serial transmission modes are defined: The RTU mode and the ASCII mode. It defines the bit
contents of message fields transmitted serially on the line. It determines how information is packed into the
message fields and decoded.
HDEC2000 and HDEC1000 support only the RTU mode via RS-485 serial interface.

RTU Transmission Mode

When devices communicate on a MODBUS serial line using the RTU (Remote Terminal Unit) mode, each
8–bit byte in a message contains two 4–bit hexadecimal characters. The main advantage of this mode is that
its greater character density allows better data throughput than ASCII mode for the same baud rate. Each
message must be transmitted in a continuous stream of characters.

Frame 1 Frame 2 Frame 3

T=0

3.5 char
at least 3.5 char at least 3.5 char 4.5 char

MODBUS message
Start Address Function Data CRC Check End
>=3.5 char 8bits 8bits N * 8 bits 16 bits >=3.5 char

Figure 1. RTU mode Message Frame

Hyundai Heavy Industries Co., Ltd 5 Electro Electric Systems

 Communication Manual Rev. A

A MODBUS message is placed by the transmitting device into a frame that has a known beginning and
ending point. This allows devices that receive a new frame to begin at the start of the message, and to know
when the message is completed.
In RTU mode, message frames are separated by a silent interval of at least 3.5 character times.

In actual application, when a query is received from master, HDEC2000 (and HDEC1000) waits a specified
amount of time determined by the Response delay parameter and the default delay setting is 10ms. The term
of character of Figure 1 is depending on the communication rate (board rate parameter setting).

MODBUS MESSAGE STUCTURE

Master initiated queries and voltage regulator (HDEC2000 or HDEC1000) responses share the same
message structure. Each message is comprised of below four message fields.

z Slave Device Address (1 byte)

z Function Code (1 byte)
z Data Block (n bytes)
z Error Check (2 bytes)

Device (Slave) Address

The device address field contains the unique MODBUS address of the slave being queried. The addressed
slave repeats the address in the device address field of the response message. This field is one byte.
MODBUS protocol limits a device address from 1 to 247. The address is user-selectable at installation, and
can be changed by HDCM software.

Function Code
The function code field in the query message defines the action to be taken by the addressed slave. This field
is echoed in the response message and is altered by setting the most significant bit (MSB) of the field to 1 if
the response is an error response. This field is 1 byte.

Only one MODBUS function code 0x04 (Read input Resistor) can be used for HDEC2000 (or HDEC1000)
voltage regulator even if some function codes are defined for MODBUS protocol. Function code 4 is the ability
to read the input status value.

Data Block
The starting address and the data size responded by slave device are depending on the starting address and
the quantity requested by master device.

The query data block contains additional information needed by the slave to perform the requested function.
The response data block contains data collected by the slave for the queried function. The length of this field
varies with each query. See the Floating Data format for interpretation of register data.

Hyundai Heavy Industries Co., Ltd 6 Electro Electric Systems

 Communication Manual Rev. A

Below three tables (table 4 …6) are shows the requested message, response message and the message
example respective. Table 7 shows the information (address, unit, data type) for readable parameter.

Table 4. Requested Message

Message Field Size Range or Value
Slave address 1 Byte 1 …247
Function Code 1 Byte 0x04
Starting Address (High – Low) 1 Byte 0x0001 … 0x000D
Quantity of Input Registers 2 Byte 0x0002 … 0x000E
CRC Check (Low – High) 2 Byte -

Table 5. Response Message

Message Field Size Range or Value
Slave address 1 Byte 1 …247
Function Code 1 Byte 0x04
Byte Count 1 Byte 0x0001 … 0x000D
Input Register Data Value (High – Low) N * 2 Byte (*1) 0x0002 … 0x000E
CRC Check (Low – High) 2 Byte -
(*1) N = Quantity of Input Registers

Table 6. Message Example (Request and Response)

Request of Master Response of Slave
Field Name Value (HEX) Field Name Value (HEX)
Slave address 01 Slave address 01
Function Code 04 Function Code 04
Starting Address High 00 Byte Count 04
Starting Address Low 01 Input Reg. 1 Data High 02
Quantity of Input Registers High 00 Input Reg. 1 Data Low 2B
Quantity of Input Registers Low 02 Input Reg. 2 Data High 01
Error Check CRC(16bit) Input Reg. 2 Data Low 63
- - Error Check CRC(16bit)

Table 7. Input Registers for Data information

Registers (Address) Data Description Unit Access Size (Byte) Format
0x0001 … 0002 averaged generator voltage V Read 4 Float
0x0003 … 0004 generator B phase current A Read 4 Float
0x0005 … 0006 active power kW Read 4 Float
0x0007 … 0008 reactive power kVAR Read 4 Float
0x0009 … 000A power factor pu Read 4 Float
0x000B … 000C excitation voltage V Read 4 Float
0x000D … 000E excitation current A Read 4 Float

Hyundai Heavy Industries Co., Ltd 7 Electro Electric Systems

 Communication Manual Rev. A

Floating Point Data Format

The specific 32 bit floating-point format matches the floating-point format of IEEE754 standard.
The first bit is the sign bit for the floating point value: 1 if negative and 0 if positive, the next 8 bit is the two’s
complement exponent biased by 127 decimal, the remaining is the 23-bit normalized mantissa.
The most-significant bit of the mantissa is always assumed to be 1 and is not explicitly stored yielding an
effective precision of 24 bits.

The value of the floating-point number is obtained by multiplying the binary mantissa times two raised to the
power of the unbiased exponent. The assumed bit of the binary mantissa has the value of 1.0 with the
remaining 23 bits providing a fractional value. The floating-point bit format is shows in below table.

Floating-point bit Format

Sign 2’s Complement of (exponent + 127) Mantissa
1 bit 8 bit 23 bit

The floating point format allows a maximum value of 3.38 x 1038.

Note that bytes 0 and 1 of the floating-point value are stored in the lower numbered register and bytes 2 and 3
are contained in the higher numbered register.

Sample Floating Point format for number 123

Register 45005 45006
Hexadecimal 0000 42F6
Binary 0000 0000 0000 0000 0100 0010 1111 0110

For example: Number 123 in floating point format is mapped to two Holding registers (such as 45005 and
45006) are shown in above table

For HDEC2000 (or HDEC1000) MODBUS, two consecutive holding registers which are
mapped to any of the 4-byte generic data types, are considered to be linked together as
IMPORTANT one atomic, indivisible unit of information which can be read or written by MODBUS
message only as one entity (that is, one cannot be read or written without the other).

Error Check
The error check field provides a method for the slave to validate the integrity of the query message contents
and allows the master to confirm there validity. This field is 2 bytes.

CRC Generation
The Cyclical Redundancy Checking (CRC) field is two bytes, containing a 16–bit binary value. The CRC value
is calculated by the transmitting device, which appends the CRC to the message. The device that receives
recalculates a CRC during receipt of the message, and compares the calculated value to the actual value it
received in the CRC field. If the two values are not equal, an error results.

Hyundai Heavy Industries Co., Ltd 8 Electro Electric Systems

 Communication Manual Rev. A

The CRC is started by first preloading a 16–bit register to all 1’s. Then a process begins of applying
successive 8–bit bytes of the message to the current contents of the register. Only the eight bits of data in
each character are used for generating the CRC. Start and stop bits and the parity bit, do not apply to the
CRC.

During generation of the CRC, each 8–bit character is exclusive ORed with the register contents. Then the
result is shifted in the direction of the least significant bit (LSB), with a zero filled into the most significant bit
(MSB) position. The LSB is extracted and examined. If the LSB was a 1, the register is then exclusive ORed
with a preset, fixed value. If the LSB was a 0, no exclusive OR takes place.

This process is repeated until eight shifts have been performed. After the last (eighth) shift, the next 8–bit
character is exclusive ORed with the register’s current value, and the process repeats for eight more shifts as
described above. The final content of the register, after all the characters of the message have been applied,
is the CRC value.

A procedure for generating a CRC is:

1. Load a 16–bit register with FFFF hex (all 1’s). Call this the CRC register.
2. Exclusive OR the first 8–bit byte of the message with the low–order byte of the 16–bit CRC register,
putting the result in the CRC register.
3. Shift the CRC register one bit to the right (toward the LSB), zero–filling the MSB. Extract and
examine the LSB.
4. (If the LSB was 0): Repeat Step 3 (another shift).
(If the LSB was 1): Exclusive OR the CRC register with the polynomial value 0xA001 (1010 0000
0000 0001).
5. Repeat Steps 3 and 4 until 8 shifts have been performed. When this is done, a complete 8–bit byte
will have been processed.
6. Repeat Steps 2 through 5 for the next 8–bit byte of the message. Continue doing this until all bytes
have been processed.
7. The final content of the CRC register is the CRC value.
8. When the CRC is placed into the message, its upper and lower bytes must be swapped as
described below.

Placing the CRC into the Message

When the 16–bit CRC (two 8–bit bytes) is transmitted in the message, the low-order byte will be transmitted
first, followed by the high order byte. Figure 2 shows the CRC Byte Sequence, and Figure 3 shows the
calculation algorithm of CRC.

z For example, if the CRC value is 1241 hex (0001 0010 0100 0001):
CRC CRC
Addr Func Data Data Data Data Data Lo Lo
0x41 0x12

Figure 2. CRC Byte Sequence

Hyundai Heavy Industries Co., Ltd 9 Electro Electric Systems

 Communication Manual Rev. A

OxFFF CRC16

CRC16 XOR BYTE CRC16

N=0

Move to the right CRC16

No Yes
Carry over

CRC16 XOR POLY CRC16

N=N+1

No Yes
N>7

No Yes
End of message
Following (second) BYTE
XOR = exclusive OR
N = number of information bits END
POLY = calculation polynomial of the CRC16 = 1010 0000 0000 0001
(Generating polynomial = 1 + X2 + X15 + X16)
In the CRC16, the 1’st byte transmitted is the least significant one.

Figure 3. Calculation algorithm of the CRC16

Hyundai Heavy Industries Co., Ltd 10 Electro Electric Systems

 Communication Manual Rev. A

Revision History
Version Date Description
• Initial release
• Supported firmware version of voltage regulator
A Jun 15, 2012
- V1.20 (or later) for HDEC2000
- V1.00 (or later) for HDEC1000

Hyundai Heavy Industries Co., Ltd 11 Electro Electric Systems