0% found this document useful (0 votes)
147 views

CPR04 Modbus Protocol 2v01

This document describes the MODBUS communication protocol used by the CPR04 feeder protection relay. It provides an overview of the physical layer, data link layer, and supported function codes. Key function codes described include reading coil and input statuses, actual values/setpoints, executing operations, and forcing multiple coils. The memory map and data formats are also outlined.

Uploaded by

ing.lunar
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
147 views

CPR04 Modbus Protocol 2v01

This document describes the MODBUS communication protocol used by the CPR04 feeder protection relay. It provides an overview of the physical layer, data link layer, and supported function codes. Key function codes described include reading coil and input statuses, actual values/setpoints, executing operations, and forcing multiple coils. The memory map and data formats are also outlined.

Uploaded by

ing.lunar
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 21

File: CPR04 MODBUS PROTOCOL 2V01 CPR04 22 November, 2010

CPR04 MODBUS Communication protocol

OVERVIEW ....................................................................................... 2

PHYSICAL LAYER ............................................................................ 2

DATA LINK LAYER ............................................................................ 2

SUPPORTED FUNCTION CODES ................................................... 3

FUNCTION CODE 01H - READ COIL STATUS ................................ 4

FUNCTION CODE 02H - READ INPUT STATUS .............................. 5

FUNCTION CODE 03H/04H - READ ACTUAL VALUES OR SETPOINTS


.......................................................................................................... 6

FUNCTION CODE 05H – EXECUTE OPERATION........................... 7

FUNCTION CODE 0FH – FORCE MULTIPLE COILS ....................... 9

EXCEPTION RESPONSES ............................................................ 10

CPR04 MEMORY MAP .................................................................... 11

THG – Trip history group described above MEMORY MAP DATA TYPE
FORMATS ....................................................................................... 18

Page 1 of 21
File: CPR04 MODBUS PROTOCOL 2V01Communication Protocol 22 November, 2010

OVERVIEW
The CPR04 feeder protection relay includes MODBUS protocol for compatibility to most communication systems.
The Windows software for setting up the CPR04 still uses the IEC 870-5-1 format protocol. The data structure is the
same for both cases.

PHYSICAL LAYER
The CPR04 communicates via RS485 or RS232. The transmit format is settable from the relay front panel menu.
The settable parameters include the following:
1. Baud rate – 115200, 57600, 38400, 19200, 9600, 4800, 2400 or 1200 b/s
2. Data bits – 8 bits
3. Start and stop bits fixed to 1
4. Parity – Even, Odd and if 8 bits data selected, None
5. Slave address – (1 – 255)
6. Answer response time – (0.01s – 10.0s) – minimum time to respond to a request
7. Receive dead time – (0.01s – 10.0s) – maximum time before a received character string is terminated

DATA LINK LAYER


Communications takes place in packets, which are groups of asynchronously framed byte data. The master transmits
a packet to the slave and the slave responds with a packet. The end of a packet is marked by 'dead-time' on the
communications line. The following describes general format of both transmit and receive packets. For exact details
on packet formatting refer to subsequent sections describing each function code.
MODBUS Packet Format: SLAVE ADDRESS 1 byte
FUNCTION CODE 1 byte
DATA N bytes
CRC 2 bytes
DEAD TIME Receive dead time setting

SLAVE ADDRESS
This is the address of the slave device that is intended to receive the packet sent by the master and performs the
desired action. Each slave device on a communication bus must have a unique address to prevent bus contention. All
of the relay's ports have the same address, which is programmable from 1 to 255. Only the addressed slave will
respond to a packet that starts with its address.
A master transmit packet with a slave address of 0 indicates a broadcast command. All slaves on the communication
link will take action based on the packet, but none will respond to the master. Broadcast mode is only recognized
when associated with FUNCTION CODE 05h. For any other function code, a packet with broadcast mode slave
address 0 will be ignored.

FUNCTION CODE
This is one of the supported functions codes of the CPR04, which tells the slave what action to perform. The
supported function codes are described later for complete details. Setting the high order bit of the function code in
the response packet indicates an exception response from the slave.

DATA
This will be a variable number of bytes depending on the function code. This may include actual values, setpoints,
or addresses sent by the master to the slave or by the slave to the master.

Page 2 of 21
File: CPR04 MODBUS PROTOCOL 2V01Communication Protocol 22 November, 2010

CRC
This is a two-byte error checking code. The RTU version of Modbus includes a 16-bit cyclic redundancy check
(CRC-16) with every packet, which is an industry standard method used for error detection. If a CPR04 Modbus
slave device receives a packet in which an error is indicated by the CRC, the slave device will not act upon or
respond to the packet thus preventing any erroneous operations.

DEAD TIME
A packet is terminated when no data is received for a period of the “receive dead time setting” (0.01s-10.0s)
Consequently, the transmitting device must not allow gaps between bytes longer than this interval. Once the dead
time has expired without a new byte transmission, all slaves start listening for a new packet from the master except
for the addressed slave.

CRC-16 ALGORITHM
The CRC-16 algorithm essentially treats the entire data stream (data bits only; start, stop and parity ignored) as one
continuous binary number. This number is first shifted left 16 bits and then divided by a characteristic polynomial
(11000000000000101 B). The 16-bit remainder of the division is appended to the end of the packet, most significant
byte first. The resulting packet including CRC, when divided by the same polynomial at the receiver will give a zero
remainder if no transmission errors have occurred. This algorithm requires the characteristic polynomial to be
reverse bit ordered. The most significant bit of the characteristic polynomial is dropped, since it does not affect the
value of the remainder.

Note: A C programming language implementation of the CRC algorithm will be provided upon request.

SUPPORTED FUNCTION CODES


Modbus officially defines function codes from 1 to 127 though only a small subset is generally needed. The CPR04
relays support some of these functions, as summarized in the following table. Subsequent sections describe each
function code in detail.

CPR04 MODBUS FUNCTION CODES


FUNCTION CODE
MODBUS DEFINITION CPR04 DEFINITION
HEX DEC
01 1 Read Coil Status Read Coil Status
02 2 Read Input Status Read Input Status
03 3 Read Holding Registers Read Actual Values or Setpoints or user map
04 4 Read Input Registers Read Actual Values or Setpoints or user map
05 5 Force Single Coil Execute Operation
0F 15 Force multiple coils Force multiple coils

Page 3 of 21
File: CPR04 MODBUS PROTOCOL 2V01Communication Protocol 22 November, 2010

FUNCTION CODE 01H - READ COIL STATUS


This function code allows the master to read one or more of the output relay coil status bits. The status bits are
packed into bytes with the first addressed bit occupying the least significant bit position of the first returned byte.
Enough bytes are returned to contain all requested status bits. The last byte is zero-padded as required. The
maximum number of output relay status bits that can be read in a single request is 5.
The following table shows the format of the master and slave packets. The example shows a master device
requesting 4 status bit values starting at address 01h from slave device 0F; the slave device responds with the bit
values 1, 0, 1, 0 and 1 from binary status addresses 01h through 04h inclusive. Note that one byte is required to
contain the response data. The first byte contains all the data bits stored in the least significant to the most significant
bit position. Note that the rest of the first byte is zero-filled.

Master Transmission Slave Response


Packet Format Example (hex) Packet Format Example (hex)
SLAVE ADDRESS 0F SLAVE ADDRESS 0F
FUNCTION CODE 01 FUNCTION CODE 01
DATA STARTING ADDRESS - hi 00 BYTE COUNT 02
DATA STARTING ADDRESS - lo 01 DATA BYTE hi 00
NUMBER OF DATA BITS - hi 00 DATA BYTE lo 15
NUMBER OF DATA BITS - lo 04 CRC - lo 11
CRC - lo 6D CRC - hi F2
CRC - hi 27

Output bit layout:


ADDR DESCRIPTION BIT POSITION
0000 Output relay #1 0x0001
0001 Output relay #2 0x0002
0002 Output relay #3 0x0004
0003 Output relay #4 0x0008
0004 Output relay #5 0x0010
0005 Alarm LED 0x0020
0006 Power good LED (toggling) 0x0040
0007 Trip LED 0x0080
0008 Operator in menu 0x0100

Page 4 of 21
File: CPR04 MODBUS PROTOCOL 2V01Communication Protocol 22 November, 2010

FUNCTION CODE 02H - READ INPUT STATUS


This function code allows the master to read one or more of the digital input status bits. The status bits are packed
into bytes with the first addressed bit occupying the least significant bit position of the first returned byte. Enough
bytes are returned to contain all requested status bits. The last byte is zero-padded as required. The maximum
number of output relay status bits that can be read in a single request is 3.
The following table shows the format of the master and slave packets. The example shows a master device
requesting 2 status bit values starting at address 01h from slave device 0F; the slave device responds with the bit
values 0 and 1 from binary status addresses 01h through 02h inclusive. Note that one byte is required to contain the
response data. The first byte contains all the data bits stored in the least significant to the most significant bit
position. Note that the rest of the first byte is zero-filled.

Master Transmission Slave Response


Packet Format Example (hex) Packet Format Example (hex)
SLAVE ADDRESS 0F SLAVE ADDRESS 0F
FUNCTION CODE 02 FUNCTION CODE 02
DATA STARTING ADDRESS - hi 00 BYTE COUNT 02
DATA STARTING ADDRESS - lo 01 DATA BYTE hi 00
NUMBER OF DATA BITS - hi 00 DATA BYTE lo 01
NUMBER OF DATA BITS - lo 02 CRC - lo 11
CRC - lo A9 CRC - hi B9
CRC - hi 25

Input bit layout:


ADDR DESCRIPTION BIT MASK POSITION
0000 Digital Input 1 0x0001
0001 Digital Input 2 (Disabled) 0x0002
0002 Digital Input 3 (Disabled) 0x0004

Page 5 of 21
File: CPR04 MODBUS PROTOCOL 2V01Communication Protocol 22 November, 2010

FUNCTION CODE 03H/04H - READ ACTUAL VALUES OR SETPOINTS


This function code allows the master to read one or more consecutive data registers (actual values or setpoints) from
a CPR04. Data registers read are always 16 bit (two byte) values transmitted high order byte first. The maximum
number of registers that can be read in a single packet is 120. Though the data is sent as 16 bits, the different
setpoints or data can be any of 1 to 4 bytes in size. Look at the table layout at the end of the document.
The CPR04 interpret code 3 and 4 in the same way, reading one or more consecutive data registers. The data starting
address will determine the type of data being read.
The following table shows the format of the master and slave packets. The example shows a master devices
requesting 3 register values starting at address 200h from slave device 11; the slave device responds with the values
555, 0, and 100 from registers 200h, 201h, and 202h respectively.

Master Transmission Slave Response


Packet Format Example (hex) Packet Format Example (hex)
SLAVE ADDRESS 11 SLAVE ADDRESS 11
FUNCTION CODE 03 FUNCTION CODE 03
DATA STARTING ADDRESS - hi 02 BYTE COUNT 06
DATA STARTING ADDRESS - lo 00 DATA BYTE #1 02
NUMBER OF VALUES - hi 00 DATA BYTE #2 2B
NUMBER OF VALUES - lo 03 DATA BYTE #3 00
CRC - lo E3 DATA BYTE #4 00
CRC - hi 06 DATA BYTE #5 00
DATA BYTE #6 64
CRC - lo BA
CRC - hi C8

Page 6 of 21
File: CPR04 MODBUS PROTOCOL 2V01Communication Protocol 22 November, 2010

FUNCTION CODE 05H – EXECUTE OPERATION


This function code allows the master to perform various operations in the CPR04. Available operations are in the
table SUMMARY OF OPERATION CODES. The following table shows the format of the master and slave packets.
The example shows a master device requesting the slave device 15 to perform a reset breaker count (12). The hi and
lo CODE VALUE bytes always have the values 'FF' and '00' respectively and are a remnant of the original Modbus
definition of this function code.
Master Transmission Slave Response
Packet Format Example (hex) Packet Format Example (hex)
SLAVE ADDRESS 15 SLAVE ADDRESS 15
FUNCTION CODE 05 FUNCTION CODE 05
OPERATION CODE - hi 00 OPERATION CODE - hi 00
OPERATION CODE - lo 12 OPERATION CODE - lo 12
CODE VALUE - hi FF CODE VALUE - hi FF
CODE VALUE - lo 00 CODE VALUE - lo 00
CRC - lo 2F CRC - lo 2F
CRC - hi 2B CRC - hi 2B

SUMMARY OF OPERATION CODES (for Function Code 05h)

CODE DEFINITION DESCRIPTION

Decimal NORMAL MODE


0000 vc>alarm relay setting active For this function - force the existing output relay setting active
0001 vc>start relay setting active For this function - force the existing output relay setting active
0002 vc>trip relay setting active For this function - force the existing output relay setting active
0003 vc>>trip relay setting active For this function - force the existing output relay setting active
0004 I1>start relay setting active For this function - force the existing output relay setting active
0005 I1>trip relay setting active For this function - force the existing output relay setting active
0006 I1>>trip relay setting active For this function - force the existing output relay setting active
0007 Irms>start relay setting active For this function - force the existing output relay setting active
0008 Irms>trip relay setting active For this function - force the existing output relay setting active
0009 Irms>>trip relay setting active For this function - force the existing output relay setting active
0010 Ith>start relay setting active For this function - force the existing output relay setting active
0011 Ith>alarm/trip relay setting active For this function - force the existing output relay setting active
0012 Ith>>trip relay setting active For this function - force the existing output relay setting active
0013 I1<trip relay setting active For this function - force the existing output relay setting active
0014 Iub>alarm relay setting active For this function - force the existing output relay setting active
0015 Iub>start relay setting active For this function - force the existing output relay setting active
0016 Iub>trip relay setting active For this function - force the existing output relay setting active
0017 Iub>>trip relay setting active For this function - force the existing output relay setting active
0018 Io>start relay setting active For this function - force the existing output relay setting active
0019 Io>trip relay setting active For this function - force the existing output relay setting active
0020 Io>>trip relay setting active For this function - force the existing output relay setting active
0021 Ilub>start relay setting active For this function - force the existing output relay setting active
0022 Ilub>trip relay setting active For this function - force the existing output relay setting active
0023 Ilub>>trip relay setting active For this function - force the existing output relay setting active
0024 Breaker fail 1 relay setting active For this function - force the existing output relay setting active
0025 Breaker fail 2 relay setting active For this function - force the existing output relay setting active
0026 Breaker inhibit relay setting active For this function - force the existing output relay setting active
0027 Event trip relay setting active For this function - force the existing output relay setting active

Page 7 of 21
File: CPR04 MODBUS PROTOCOL 2V01Communication Protocol 22 November, 2010

Decimal H-CONFIGURATION MODE


0028 aIub>alarm relay setting active For this function - force the existing output relay setting active
0029 aIub>start relay setting active For this function - force the existing output relay setting active
0030 aIub>trip relay setting active For this function - force the existing output relay setting active
0031 aIub>>trip relay setting active For this function - force the existing output relay setting active
0032 bIub>alarm relay setting active For this function - force the existing output relay setting active
0033 bIub>start relay setting active For this function - force the existing output relay setting active
0034 bIub>trip relay setting active For this function - force the existing output relay setting active
0035 bIub>>trip relay setting active For this function - force the existing output relay setting active
0036 cIub>alarm relay setting active For this function - force the existing output relay setting active
0037 cIub>start relay setting active For this function - force the existing output relay setting active
0038 cIub>trip relay setting active For this function - force the existing output relay setting active
0039 cIub>>trip relay setting active For this function - force the existing output relay setting active
0040 Event trip relay setting active For this function - force the existing output relay setting active
Decimal NORMAL MODE
0041 Clear vc> alarm counter Clear the stored vc> alarm counter for the installed breaker
0042 Clear vc> trip counter Clear the stored vc> trip counter for the installed breaker
0043 Clear vc>> trip counter Clear the stored vc>> trip counter for the installed breaker
0044 Clear I1> trip counter Clear the stored I1> trip counter for the installed breaker
0045 Clear I1>> trip counter Clear the stored I1>> trip counter for the installed breaker
0046 Clear Irms> trip counter Clear the stored Irms> trip counter for the installed breaker
0047 Clear Irms>> trip counter Clear the stored Irms>> trip counter for the installed breaker
0048 Clear Ith> trip counter Clear the stored Ith> trip counter for the installed breaker
0049 Clear Ith>>trip counter Clear the stored Ith> trip counter for the installed breaker
0050 Clear I1< trip counter Clear the stored I1< trip counter for the installed breaker
0051 Clear Iub> alarm counter Clear the stored Iub> alarm counter for the installed breaker
0052 Clear Iub> trip counter Clear the stored Iub> trip counter for the installed breaker
0053 Clear Iub>> trip counter Clear the stored Iub>> trip counter for the installed breaker
0054 Clear Io> trip counter Clear the stored Io> trip counter for the installed breaker
0055 Clear Io>> trip counter Clear the stored Io>> trip counter for the installed breaker
0056 Clear Ilub> trip counter Clear the stored Ilub> trip counter for the installed breaker
0057 Clear Ilub>> trip counter Clear the stored Ilub>> trip counter for the installed breaker
0058 Clear Breaker fail 1 trip counter Clear the stored Breaker fail 1 trip counter for the installed breaker
0059 Clear Breaker fail 2 trip counter Clear the stored Breaker fail 2 trip counter for the installed breaker
0060 Clear Breaker inhibit counter Clear the stored Breaker inhibit counter for the installed breaker
0061 Clear Event trip counter Clear the stored Event trip counter for the installed breaker
Decimal H-CONFIGURATION MODE
0062 Clear aIub> alarm counter Clear the stored aIub> alarm counter for the installed breaker
0063 Clear aIub> trip counter Clear the stored aIub> trip counter for the installed breaker
0064 Clear aIub>> trip counter Clear the stored aIub>> trip counter for the installed breaker
0065 Clear bIub> alarm counter Clear the stored bIub> alarm counter for the installed breaker
0066 Clear bIub> trip counter Clear the stored bIub> trip counter for the installed breaker
0067 Clear bIub>> trip counter Clear the stored bIub>> trip counter for the installed breaker
0068 Clear cIub> alarm counter Clear the stored cIub> alarm counter for the installed breaker
0069 Clear cIub> trip counter Clear the stored cIub> trip counter for the installed breaker
0070 Clear cIub>> trip counter Clear the stored cIub>> trip counter for the installed breaker
0071 Clear Event trip counter Clear the stored Event trip counter for the installed breaker
Decimal BOTH MODES
0072 Clear all counters Clear all counters above

Page 8 of 21
File: CPR04 MODBUS PROTOCOL 2V01Communication Protocol 22 November, 2010

0073 Clear trip history Clear the trip history


Decimal NORMAL MODE
0074 Compensate Iub Compensate Iub
0075 Uncompensate Iub Uncompensate Iub
Decimal H-CONFIGURATION MODE
0076 Compensate aIub Compensate aIub
0077 Compensate bIub Compensate bIub
0078 Compensate cIub Compensate cIub
0079 Uncompensate aIub Uncompensate aIub
0080 Uncompensate bIub Uncompensate bIub
0081 Uncompensate cIub Uncompensate cIub

FUNCTION CODE 0FH – FORCE MULTIPLE COILS


This function code allows the master to force multiple output relay coils in the CPR04.
IMPORTANT: THIS FUNCTION COULD CAUSE DAMAGE BECAUSE OF THE CONNECTION OF THE
OUTPUT RELAYS (BREAKER TRIP – BREAKER CLOSE). USE FUNCTION 05H FOR FORCING RELAY COILS.
IMPORTANT: THIS FUNCTION USES THE FORCE RELAY TIMER IN THE RELAY SETUP. DURING THE
RELAY FORCE TIME THE RELAY STATE WILL STAY IN THE FORCED STATE. THE NORMAL TRIP
FUNCTIONS WILL NOT BE ABLE TO RESET THE RELAYS UNTIL THE FORCE TIME TERMINATED.
The following table shows the format of the master and slave packets. The example shows a master device
requesting from slave address 15h to force relay coil 1 and 5 to the active state. The start address is 0 with 1 byte of
data. (Maximum relay coils is 5) the data coil register contains 1, 0, 0, 0 and 1 – which translates to 11h. Note that
the rest of the first byte is zero-filled.
Master Transmission Slave Response
Packet Format Example (hex) Packet Format Example (hex)
SLAVE ADDRESS 15 SLAVE ADDRESS 15
FUNCTION CODE 0F FUNCTION CODE 0F
DATA STARTING ADDRESS - hi 00 DATA STARTING ADDRESS - hi 00
DATA STARTING ADDRESS - lo 00 DATA STARTING ADDRESS - lo 00
QUANTITY - hi 00 QUANTITY - hi 00
QUANTITY - lo 05 QUANTITY - lo 05
BYTE COUNT 01 CRC - lo 96
DATA COIL STATUS 11 CRC - hi DC
CRC - lo AF
CRC - hi A5

Page 9 of 21
File: CPR04 MODBUS PROTOCOL 2V01Communication Protocol 22 November, 2010

EXCEPTION RESPONSES
Programming or operation errors happen because of illegal data in a packet, hardware or software problems in the
slave device, etc. These errors result in an exception response from the slave. The CPR04implements the error codes
listed below. The slave detecting one of these errors sends a response packet to the master with the high order bit of
the function code set to 1.
The following table shows the format of the master and slave packets. The example shows a master device sending
the unsupported function code 39h to slave device 11.

Master Transmission Slave Response


Packet Format Example (hex) Packet Format Example (hex)
SLAVE ADDRESS 11 SLAVE ADDRESS 11
FUNCTION CODE 39 FUNCTION CODE B9
CRC - lo F2 ERROR CODE 01
CRC - hi CD CRC - lo 95
CRC - hi 93

EXCEPTION RESPONSE ERROR CODES


ERROR
MODBUS DEFINITION CPR04 IMPLEMENTATION
CODE

The function code of the master query packet is not a function code supported by the
01 ILLEGAL FUNCTION
slave.

The address referenced in the data field of the master query packet is not an address
02 ILLEGAL DATA ADDRESS
supported by the slave.

The value referenced in the data field of the master query packet is not allowable in
03 ILLEGAL DATA VALUE
the addressed slave location.

The packet was received without error, but the slave device is engaged in processing
06 BUSY, REJECTED PACKET
a long duration command. Retransmit later, when the slave device may be free.

NAK - NEGATIVE The packet was received without error, but the request could not be performed,
07
ACKNOWLEDGE because this version of the CPR04 does not have the requested operation available.

NAK – RELAY SETUP The packet was received without error, but the request could not be performed,
08
INCORRECT because the CPR04 setup is incorrect for this function.

Page 10 of 21
File: CPR04 MODBUS PROTOCOL 2V01Communication Protocol 22 November, 2010

CPR04 MEMORY MAP


Information and measurements @ 0001
ADDR DESCRIPTION RANGE UNITS/STEP TYPE FACTORY DEFAULT
Dec PRODUCT ID READ ONLY
0001 CPR04 serial number F5
‘CAP
0003 Product name PROTECTION String 20
RELAY’
0013 Firmware revision number 00.00 to 99.99 F3
0014 Calibration date V2.00 26/07/2001 String 16
0022 Calibration times 0-99 1 F1
Dec PRODUCT INSTALLATION READ/WRITE
0023 Installation information 100 bytes String 100
Dec EVENT TRIP SETUP READ/WRITE
0073 Event trip string 16 bytes String 16
0081 Event active string 16 bytes String 16
0089 Event inactive string 16 bytes String 16
Dec SERIAL PORT SETUP READ ONLY
0097 MODUS Address 1-255 F1
0098 Port type 0,1 RS485/RS232 F1
0099 Baud rate rear port 1..7 Bits/sec F9
0100 Parity rear port Odd, Even, None F10
0101 Baud rate front port 1..7 Bits/sec F9
0102 Parity front port Odd, Even, None F10
0103 Answer response time 0.010-10.000 Seconds F4
0104 Receive dead time 0.010-10.000 Seconds F4
0105 MODBUS force relay time 0.1-60.0 Seconds F2
Dec HARDWARE SETUP READ ONLY
0106 CPR04 relay mode Normal / H-Config F1
0107 CPR04 measurement frequency 50/60 Hz F16
0108 Element 1 In 1A/5A 0,1 F1
0109 Element 2 In 1A/5A 0,1 F1
0110 Element 3 In 1A/5A 0,1 F1
0111 Element 4 In 1A/5A 0,1 F1
0112 Power up restore Clear / Hold 0,1 F1
Dec MEASUREMENT INFORMATION READ ONLY
0113 I1 fundamental X In Float
0115 I2 fundamental X In Float
0117 I3 fundamental X In Float
0119 I4 fundamental X In Float
0121 I1 rms X In Float
0123 I2 rms X In Float
0125 I3 rms X In Float
0127 Earth fault 3Io X In Float
0129 Iub2 X In Float
0131 Iub3 X In Float
0133 Iub4 X In Float
0135 I thermal 1 X In Float
0137 I thermal 2 X In Float

Page 11 of 21
File: CPR04 MODBUS PROTOCOL 2V01Communication Protocol 22 November, 2010

0139 I thermal 3 X In Float


0141 I thermal max X In Float
0143 I rms max X In Float
0145 I fundamental max X In Float
0147 I fundamental min X In Float
0149 Vc max X vcr Float
0151 I line unbalance X In Float
0153 Vc1 X vcr Float
0155 Vc2 X vcr Float
0157 Vc3 X vcr Float
0159 Iub2 Angle X In Float
0161 Iub3 Angle X In Float
0163 Iub4 Angle X In Float
Dec NORMAL MODE READ ONLY
0165 Setup saved counter 0-65535 1 F1
0166 Vc> alarm counter 0-65535 1 F1
0167 Vc> trip counter 0-65535 1 F1
0168 Vc>> trip counter 0-65535 1 F1
0169 I1> trip counter 0-65535 1 F1
0170 I1>> trip counter 0-65535 1 F1
0171 I1< trip counter 0-65535 1 F1
0172 Irms> trip counter 0-65535 1 F1
0173 Irms>> trip counter 0-65535 1 F1
0174 Ith> trip counter 0-65535 1 F1
0175 Ith>> trip counter 0-65535 1 F1
0176 Iub> alarm counter 0-65535 1 F1
0177 Iub> trip counter 0-65535 1 F1
0178 Iub>> trip counter 0-65535 1 F1
0179 Io> trip counter 0-65535 1 F1
0180 Io>> trip counter 0-65535 1 F1
0181 Ilub> trip counter 0-65535 1 F1
0182 Ilub>> trip counter 0-65535 1 F1
0183 Breaker fail 1 trip counter 0-65535 1 F1
0184 Breaker fail 2 trip counter 0-65535 1 F1
0185 Event trip counter 0-65535 1 F1
0186 Breaker enable trip counter 0-65535 1 F1
Dec H-CONFIGURATION MODE READ ONLY
0187 aIub> alarm counter 0-65535 1 F1
0188 aIub> trip counter 0-65535 1 F1
0189 aIub>> trip counter 0-65535 1 F1
0190 bIub> alarm counter 0-65535 1 F1
0191 bIub> trip counter 0-65535 1 F1
0192 bIub>> trip counter 0-65535 1 F1
0193 cIub> alarm counter 0-65535 1 F1
0194 cIub> trip counter 0-65535 1 F1
0195 cIub>> trip counter 0-65535 1 F1
0196 Event trip counter 0-65535 1 F1

Page 12 of 21
File: CPR04 MODBUS PROTOCOL 2V01Communication Protocol 22 November, 2010

Normal CPR04 trip function setup


ADDR DESCRIPTION RANGE STEP TYPE FACTORY DEFAULT
Dec NORMAL MODE TRIP SETUP READ/WRITE
0197 Icr/In 0.25-1.50 0.01 F3 1.10
0198 vc>al/vcr 0.80-1.50 0.01 F3 Disabled – 151
0199 vc>al:xt 0.1-3600 0.1 F2 0.1
0200 vc>/vcr 0.80-1.50 0.01 F3 Disabled – 151
0201 vc>reset 1-3600 1 F1 1
0202 vc>>/vcr 0.80-10.00 0.01 F3 Disabled – 1001
0203 vc>>:xt 0.03-10.00 0.01 F3 0.03
0204 tau 0.5-7200.0 0.1 F6 5
0206 Ith>/In 0.25-1.50 0.01 F3 Disabled – 151
0207 Ith>:xt 0.0-600.0 0.01 F3 Alarm – 6001
0208 Ith>>/In 0.25-1.50 0.01 F3 Disabled – 151
0209 Ith>>:xt 0.00-60.00 0.01 F3 0.01
0210 Irms>/In 0.25-1.50 0.01 F3 Disabled – 151
0211 Irms>:xt 0.1-1200 0.1 F2 0.1
0212 Irms>>/In 0.2-10.0 0.1 F2 Disabled – 101
0213 Irms>>:xt 0.03-10.00 0.01 F3 0.03
0214 I1>/In 0.25-1.5 0.01 F3 Disabled – 151
0215 I1>:xt 0.1-1200 0.1 F2 0.1
0216 I1>>/In 0.2-10.0 0.1 F2 Disabled – 101
0217 I1>>:xt 0.05-10.00 0.01 F3 0.05
0218 I1</In 0.05-1.00 0.01 F3 Disabled – 101
0219 I1<:xt 0.1-10.0 0.1 F2 0.1
0220 Bfail1:xt 0.05-2.00 0.01 F3 Disabled – 201
0221 Bfail1 release options 0-3 1 F13 1
0222 Bfail2:xt 0.05-2.00 0.01 F3 Disabled – 201
0223 Iub_al>/In 0.01-2.00 0.01 F3 Disabled – 201
0224 Iub_al>:xt 0.1-600.0 0.1 F6 0.1
0226 Iub>/In 0.01-2.00 0.01 F3 Disabled – 201
0227 Iub>:xt 0.1-14400 0.1 F6 0.5
0229 Iub>>/In 0.01-2.00 0.01 F3 Disabled – 201
0230 Iub>>:xt 0.05-60.0 0.01 F3 0.05
0231 Io>/In 0.05-1.00 0.01 F3 Disabled – 101
0232 Io>:xt 0.1-60.0 0.1 F2 0.1
0233 Io>>/In 0.05-10.00 0.01 F3 Disabled – 1001
0234 Io>>:xt 0.05-10.00 0.01 F3 0.05
0235 Ilub>/In 0.01-1.00 0.01 F3 Disabled – 101
0236 Ilub>:xt 0.1-60.0 0.1 F2 0.1
0237 Ilub>>/In 0.01-1.00 0.01 F3 Disabled – 101
0238 Ilub>>:xt 0.05-10.00 0.01 F3 0.05
0239 Bena:xt 1-1200 1 F1 Disabled – 1201
0240 Bena trigger options 0-3 1 F13 0
0241 Start/Alarm LED Setup 0-3 1 F22 2
0242 Event:xt 0.03-600.00 0.01 F3 3
Dec H-CONFIGURATION TRIP SETUP READ/WRITE
0243 aIub_al>/In 0.01-2.00 0.01 F3 Disabled – 201
0244 aIub_al>:xt 0.1-600.0 0.1 F6 0.1
0246 aIub>/In 0.01-2.00 0.01 F3 Disabled – 201

Page 13 of 21
File: CPR04 MODBUS PROTOCOL 2V01Communication Protocol 22 November, 2010

ADDR DESCRIPTION 0.1-14400 1 F6 1


0247 aIub>:xt 0.1-14400 0.1 F6 0.5
0249 aIub>>/In 0.01-2.00 0.01 F3 Disabled – 201
0250 aIub>>:xt 0.05-60.0 0.01 F3 0.05
0251 bIub_al>/In 0.01-2.00 0.01 F3 Disabled – 201
0252 bIub_al>:xt 0.1-600.0 0.1 F6 0.1
0254 bIub>/In 0.01-2.00 0.01 F3 Disabled – 201
0255 bIub>:xt 0.1-14400 0.1 F6 0.5
0257 bIub>>/In 0.01-2.00 0.01 F3 Disabled – 201
0258 bIub>>:xt 0.05-60.0 0.01 F3 0.05
0259 cIub_al>/In 0.01-2.00 0.01 F3 Disabled – 201
0260 cIub_al>:xt 0.1-600.0 0.1 F6 0.1
0262 cIub>/In 0.01-2.00 0.01 F3 Disabled – 201
0263 cIub>:xt 0.1-14400 0.1 F6 0.5
0265 cIub>>/In 0.01-2.00 0.01 F3 Disabled – 201
0266 cIub>>:xt 0.05-60.0 0.01 F3 0.05
0267 Start/Alarm LED Setup 0-3 1 F22 2
0268 Event:xt 0.03-60.00 0.01 F3 3
Dec NORMAL MODE INPUT SETUP READ/WRITE
0269 Digital input 1 function 0-3 1 F12 Disabled – 0
0270 Digital input 2 function 0-3 1 F12 Disabled – 0
0271 Digital input 3 function 0-3 1 F12 Disabled – 0
0272 Digital input 1 active state 0-1 1 F15 High – 0
0273 Digital input 2 active state 0-1 1 F15 High – 0
0274 Digital input 3 active state 0-1 1 F15 High – 0
Dec H-CONFIG MODE INPUT SETUP READ/WRITE
0275 Digital input 1 function 0-2 1 F19 Disabled – 0
0276 Digital input 2 function 0-2 1 F19 Disabled – 0
0277 Digital input 3 function 0-2 1 F19 Disabled – 0
0278 Digital input 1 active state 0-1 1 F15 High – 0
0279 Digital input 2 active state 0-1 1 F15 High – 0
0280 Digital input 3 active state 0-1 1 F15 High – 0
Dec NORMAL MODE COMPENSATION READ ONLY
0281 Compensation vector for Iub - - Float
0283 Compensation angle for Iub - - Float
Dec H-CONFIG COMPENSATION READ ONLY
0285 Compensation vector for aIub - - Float
0287 Compensation angle for aIub - - Float
0289 Compensation vector for bIub - - Float
0291 Compensation angle for bIub - - Float
0293 Compensation vector for cIub - - Float
0295 Compensation angle for cIub - - Float

Page 14 of 21
File: CPR04 MODBUS PROTOCOL 2V01Communication Protocol 22 November, 2010

Output relay function setup


ADDR DESCRIPTION RANGE UNITS/STEP TYPE FACTORY DEFAULT
Dec NORMAL MODE OUTPUT RELAY READ/WRITE
0297 SETUP
Vc>alarm relay 0-31 Bit set F17 Disabled – 0
0298 Vc>start relay 0-31 Bit set F17 Disabled – 0
0299 Vc>trip relay 0-31 Bit set F17 Disabled – 0
0300 Vc>>trip relay 0-31 Bit set F17 Disabled – 0
0301 I1>start relay 0-31 Bit set F17 Disabled – 0
0302 I1>trip relay 0-31 Bit set F17 Disabled – 0
0303 I1>>trip relay 0-31 Bit set F17 Disabled – 0
0304 Irms>start relay 0-31 Bit set F17 Disabled – 0
0305 Irms>trip relay 0-31 Bit set F17 Disabled – 0
0306 Irms>>trip relay 0-31 Bit set F17 Disabled – 0
0307 Ith>start relay 0-31 Bit set F17 Disabled – 0
0308 Ith>alarm relay 0-31 Bit set F17 Disabled – 0
0309 Ith>trip relay 0-31 Bit set F17 Disabled – 0
0310 I1<trip relay 0-31 Bit set F17 Disabled – 0
0311 Iub>alarm relay 0-31 Bit set F17 Disabled – 0
0312 Iub>start relay 0-31 Bit set F17 Disabled – 0
0313 Iub>trip relay 0-31 Bit set F17 Disabled – 0
0314 Iub>>trip relay 0-31 Bit set F17 Disabled – 0
0315 Io>start relay 0-31 Bit set F17 Disabled – 0
0316 Io>trip relay 0-31 Bit set F17 Disabled – 0
0317 Io>>trip relay 0-31 Bit set F17 Disabled – 0
0318 Ilub>start relay 0-31 Bit set F17 Disabled – 0
0319 Ilub>trip relay 0-31 Bit set F17 Disabled – 0
0320 Ilub>>trip relay 0-31 Bit set F17 Disabled – 0
0321 Breaker fail 1 relay 0-31 Bit set F17 Disabled – 0
0322 Breaker fail 2relay 0-31 Bit set F17 Disabled – 0
0323 Breaker inhibit relay 0-31 Bit set F17 Disabled – 0
0324 Event trip relay 0-31 Bit set F17 Disabled – 0
0325 Energize to trip 0-31 Bit set F17 Energise to trip – 31
0326 Latch on trip 0-31 Bit set F17 Disabled – 0
Dec H-CONFIG OUTPUT RELAY READ/WRITE
0327 SETUP
aIub>alarm relay 0-31 Bit set F17 Disabled – 0
0328 aIub>start relay 0-31 Bit set F17 Disabled – 0
0329 aIub>trip relay 0-31 Bit set F17 Disabled – 0
0330 aIub>>trip relay 0-31 Bit set F17 Disabled – 0
0331 bIub>alarm relay 0-31 Bit set F17 Disabled – 0
0332 bIub>start relay 0-31 Bit set F17 Disabled – 0
0333 bIub>trip relay 0-31 Bit set F17 Disabled – 0
0334 bIub>>trip relay 0-31 Bit set F17 Disabled – 0
0335 cIub>alarm relay 0-31 Bit set F17 Disabled – 0
0336 cIub>start relay 0-31 Bit set F17 Disabled – 0
0337 cIub>trip relay 0-31 Bit set F17 Disabled – 0
0338 cIub>>trip relay 0-31 Bit set F17 Disabled – 0
0339 Event trip relay 0-31 Bit set F17 Disabled – 0
0340 Energize to trip 0-31 Bit set F17 Energise to trip – 31
0341 Latch on trip 0-31 Bit set F17 Disabled – 0

Page 15 of 21
File: CPR04 MODBUS PROTOCOL 2V01Communication Protocol 22 November, 2010

Time stamp structure and map


The time stamping of counters contains an array of 33 structured blocks of data. The structure is as follow:

Time stamp group (TSG) start address = 400 to 631 (33 time stamp * 7)
16bit – Trip second 0 - 59
16bit – Trip minute 0-59
16bit – Trip hour 0-23
16bit – Trip day 1-31
16bit – Trip day of week 0 – 6 (Sunday = 0)
16bit – Trip month 1-12
16bit – Trip year 2000-2099
(14 bytes data)

Time stamp data map @ 300


ADDR DESCRIPTION RANGE UNITS/STEP TYPE FACTORY DEFAULT
Dec FP04 Counter time stamp READ ONLY
0400 Time stamp last setup saved TSG
0407 Time stamp vc> alarm counter cleared TSG
0414 Time stamp vc> trip counter cleared TSG
0421 Time stamp vc>> trip counter cleared TSG
0428 Time stamp I1> trip counter cleared TSG
0435 Time stamp I1>> trip counter cleared TSG
0442 Time stamp I1<trip counter cleared TSG
0449 Time stamp Irms>trip counter cleared TSG
0456 Time stamp Irms>>trip counter cleared TSG
0463 Time stamp Ith>trip counter cleared TSG
0470 Time stamp Ith>>trip counter cleared TSG
0477 Time stamp Iub>alarm counter cleared TSG
0484 Time stamp Iub>trip counter cleared TSG
0491 Time stamp Iub>>trip counter cleared TSG
0508 Time stamp Io>trip counter cleared TSG
0515 Time stamp Io>>trip counter cleared TSG
0522 Time stamp Ilub> trip counter cleared TSG
0529 Time stamp Ilub>>trip counter cleared TSG
0536 Time stamp Bfail1 trip counter cleared TSG
0543 Time stamp Bfail2 trip counter cleared TSG
0550 Time stamp Breaker enable trip counter cleared TSG
0557 Time stamp Normal mode event counter cleared TSG
0564 Time stamp aIub>alrm counter cleared TSG
0571 Time stamp aIub>trip counter cleared TSG
0578 Time stamp aIub>>trip counter cleared TSG
0585 Time stamp bIub>alarm counter cleared TSG
0592 Time stamp bIub>trip counter cleared TSG
0599 Time stamp bIub>>trip counter cleared TSG
0606 Time stamp cIub>alarm counter cleared TSG
0613 Time stamp cIub>trip counter cleared TSG
0620 Time stamp cIub>>trip counter cleared TSG
0627 Time stamp Trip history cleared TSG

Page 16 of 21
File: CPR04 MODBUS PROTOCOL 2V01Communication Protocol 22 November, 2010

Trip history structure and map


The trip history contains an array of 25 structured blocks of data. The structure is as follow:

Trip history Table start address = 1000 to 1025


16bit – Number of latest history data block 1-25 (Points to the latest history block in time)
16bit – Group number list for history data block 1 0-25 (0 = no history data)

16bit – Group number list for history data block 25 0-25 (0 = no history data)
(52 bytes data)

Trip history group (THG) start address = 1026 to 1626 (25 history * 24)
32bit – First measurement value floating point number (F5)
32bit – Second measurement value floating point number (F5)
32bit – Third measurement value floating point number (F5)
32bit – First angle measurement value floating point number (F5)
32bit – Second angle measurement value floating point number (F5)
32bit – Third angle measurement value floating point number (F5)
32bit – Time it took to trip unsigned integer must be divided by 100 for seconds
16bit – Trip function 0 – 24 (F14)
16bit – Trip second 0 - 59
16bit – Trip minute 0-59
16bit – Trip hour 0-23
16bit – Trip day 1-31
16bit – Trip day of week 0 – 6 (Sunday = 0)
16bit – Trip month 1-12
16bit – Trip year 0-99
16bit – Trip element 0x70 + 1 – 3 (0 = event input, 1-3 = value 1 – 3)
16bit – Trip output relay (bit 1 = output relay 1 … bit 5 = output relay 5)
(48 bytes data)

The three measurement values are used for the extended history display. The bottom four bits of the trip element
value points to the measurement value that caused the trip. The top four bits describe the state of the other elements
at time of trip. If one or two of the element measurements was over the threshold it will be recorded as (bit 0x10 =
element 1; bit 0x20 = element 2; bit 0x40 = element 3). The trip function describes the trip that is in the trip data
block and how it will be displayed. The time it took to trip is a integer number that must be divided with 100 to get
(0.00) seconds. The trip output relay describes the output relays that tripped for this history block.

Trip history data map


ADDR DESCRIPTION RANGE UNITS/STEP TYPE FACTORY DEFAULT
Dec CPR04 HISTORY DATA READ ONLY
1000 Number of latest history data block 0-24 1 F1 0
1001 Group number for History data 1 0-25 1 F1 0
1002 Group number for History data 2 0-25 1 F1 0
1003 Group number for History data 3 0-25 1 F1 0
1004 Group number for History data 4 0-25 1 F1 0
1005 Group number for History data 5 0-25 1 F1 0
1006 Group number for History data 6 0-25 1 F1 0
1007 Group number for History data 7 0-25 1 F1 0
1008 Group number for History data 8 0-25 1 F1 0
1009 Group number for History data 9 0-25 1 F1 0
1010 Group number for History data 10 0-25 1 F1 0
1011 Group number for History data 11 0-25 1 F1 0
1012 Group number for History data 12 0-25 1 F1 0
1013 Group number for History data 13 0-25 1 F1 0
1014 Group number for History data 14 0-25 1 F1 0
1015 Group number for History data 15 0-25 1 F1 0

Page 17 of 21
File: CPR04 MODBUS PROTOCOL 2V01Communication Protocol 22 November, 2010

1016 Group number for History data 16 0-25 1 F1 0


1017 Group number for History data 17 0-25 1 F1 0
1018 Group number for History data 18 0-25 1 F1 0
1019 Group number for History data 19 0-25 1 F1 0
1020 Group number for History data 20 0-25 1 F1 0
1021 Group number for History data 21 0-25 1 F1 0
1022 Group number for History data 22 0-25 1 F1 0
1023 Group number for History data 23 0-25 1 F1 0
1024 Group number for History data 24 0-25 1 F1 0
1025 Group number for History data 25 0-25 1 F1 0
1026 History structure data 1 THG 0
1050 History structure data 2 THG 0
1074 History structure data 3 THG 0
1098 History structure data 4 THG 0
1122 History structure data 5 THG 0
1146 History structure data 6 THG 0
1170 History structure data 7 THG 0
1194 History structure data 8 THG 0
1218 History structure data 9 THG 0
1242 History structure data 10 THG 0
1266 History structure data 11 THG 0
1290 History structure data 12 THG 0
1314 History structure data 13 THG 0
1338 History structure data 14 THG 0
1362 History structure data 15 THG 0
1386 History structure data 16 THG 0
1410 History structure data 17 THG 0
1434 History structure data 18 THG 0
1458 History structure data 19 THG 0
1482 History structure data 20 THG 0
1506 History structure data 21 THG 0
1530 History structure data 22 THG 0
1554 History structure data 23 THG 0
1578 History structure data 24 THG 0
1602 History structure data 25 THG 0

THG – Trip history group described above

Page 18 of 21
File: CPR04 MODBUS PROTOCOL 2V01Communication Protocol 22 November, 2010

MEMORY MAP DATA TYPE FORMATS


TYPE VALUE / BIT MASK DESCRIPTION
F1 UNSIGNED VALUE
Example: 1234 stored as 1234
F2 UNSIGNED VALUE, 1 DECIMAL PLACE
Example: 123.4 stored as 1234
F3 UNSIGNED VALUE, 2 DECIMAL PLACES
Example: 12.34 stored as 1234
F4 UNSIGNED VALUE, 3 DECIMAL PLACES
Example: 1.234 stored as 1234
F5 UNSIGNED LONG VALUE
Example: 12345678 stored as 12345678
F6 UNSIGNED LONG VALUE, 1 DECIMAL PLACE
Example: 1234567.8 stored as 12345678
F7 UNSIGNED LONG VALUE, 2 DECIMAL PLACES
Example: 123456.78 stored as 12345678
F8 UNSIGNED LONG VALUE, 3 DECIMAL PLACES
Example: 12345.678 stored as 12345678
F9 BAUD RATE – LOW BYTE OF INTEGER
1 2400 baud
2 4800 baud
3 9600 baud
4 19200 baud
5 38400 baud
6 57600 baud
7 115200 baud
F10 PARITY TYPE – LOW BYTE OF INTEGER
0 EVEN
1 ODD
2 NONE
F11 HARDWARE SETUP - LOW BYTE OF INTEGER
0 Output relay #5 (for Terminal 17+19) Output relay #4 (for Terminal 13+15)
1 Digital input 2 (for Terminal 17+19) Digital input 3 (for Terminal 13+15)
F12 Normal mode DIGITAL INPUT FUNCTION – LOW BYTE OF INTEGER
0 Disabled
1 Breaker – ON/OFF
2 Remote Reset
3 Event trip
F13 Bfail1 AND Bena OPIONS – LOW BYTE OF INTEGER
0 I(fundamental) < 10% of In
1 Digital input active
2 I(fundamental) < 10% of In – AND - Digital input active
3 I(fundamental) < 10% of In – OR - Digital input active

Page 19 of 21
File: CPR04 MODBUS PROTOCOL 2V01Communication Protocol 22 November, 2010

TYPE VALUE / BIT MASK DESCRIPTION


F14 DIGITAL INPUT FUNCTION – LOW BYTE OF INTEGER
0 Vc> trip
1 Vc>>trip
2 I1>trip
3 I1>>trip
4 Ith>trip
5 Ith>>trip
6 Irms>trip
7 Irms>>trip
8 I1<trip
9 Io>trip
10 Io>>trip
11 Ilub>trip
12 Ilub>>trip
13 Bfail1 trip
14 Bfail2 trip
15 Iub>trip
16 Iub>>trip
17 aIub>trip
18 aIub>>trip
19 bIub>trip
20 bIub>>trip
21 cIub>trip
22 cIub>>trip
23 Event trip (Normal mode)
24 Event trip (H-configuration)
F15 DIGITAL INPUT ACTIVE STATE – LOW BYTE OF INTEGER
0 Active if high on input pin
1 Active if low on input pin
F16 OPERATING FREQUENCY – LOW BYTE OF INTEGER
0 50Hz
1 60Hz
F17 BIT PROGRAMMABLE OUTPUT RELAY SETTING – LOW BYTE OF INTEGER
0x01 Relay 1
0x02 Relay 2
0x04 Relay 3
0x08 Relay 4
0x10 Relay 5
F18 CALIBRATION/MANUFACTURING DATE STRING – STRING 20
V3.11 15/01/2001 Version and date of calibration
F19 H-Config DIGITAL INPUT FUNCTION – LOW BYTE OF INTEGER
0 Disabled
1 Remote Reset
2 Event trip
F20 UNSIGNED VALUE, 4 DECIMAL PLACES
Example: 1.2345 stored as 12345
F21 CPR04 CT used CT used in CPR04
0 1A – CT selected
1 5A – CT selected
F22 Flicker LED ALARM LED FUNCTIONS

Page 20 of 21
File: CPR04 MODBUS PROTOCOL 2V01Communication Protocol 22 November, 2010

0 ONLY TRIP STARTS


1 ONLY ALARMS
2 START + ALARMS
3 ALWAYS OFF

Page 21 of 21

You might also like