0% found this document useful (0 votes)

117 views

MODBUS Remote Protocol

Uploaded by

Sarah Frazier

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

117 views

MODBUS Remote Protocol

Uploaded by

Sarah Frazier

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 108

Modbus

Remote Communication Protocol

for REC 523
Technical Description

Industrial IT enabled products from ABB are the building blocks for greater
productivity, featuring all the tools necessary for lifecycle product support in
consistent electronic form.

1MRS 752015-MUM

Remote Communication Protocol for REC 523

Issued:
Version:

Technical Description

29.11.2001
B/02.02.2004

Modbus

Contents
1. Overview of the protocol ..........................................................5
1.1. Transmission frame formats ..........................................................6
1.1.1. ASCII mode ........................................................................6
1.1.2. RTU mode ..........................................................................7
1.2. Masters queries ............................................................................8
1.3. Normal responses .......................................................................10
1.4. Exception responses ...................................................................11

2. REC 523 profile of Modbus ....................................................12

2.1.
2.2.
2.3.
2.4.
2.5.

Supported application functions ..................................................12

Supported diagnostic subfunctions .............................................12
Diagnostic counters .....................................................................13
Possible exception codes ............................................................13
Event reporting ............................................................................14
2.5.1. Event collecting algorithms ..............................................15
2.5.2. Event queue descriptions .................................................17

3. Protocol interface implementation ........................................23

3.1. Application to protocol mapping ..................................................23
3.1.1. POD concept ....................................................................23
3.1.2. POD configuration ............................................................23
3.1.2.1. Database mapping .............................................24
3.1.2.2. Event control objects ..........................................25
3.1.3. Defining POD contents ....................................................25
3.1.3.1. Visible POD entry format ....................................25
3.1.3.2. POD diagnostics ................................................29
3.1.3.3. Examples of mapping application data
into the Modbus protocol ....................................31
3.2. Protocol address map based on the default POD .......................34
3.3. Protocol software version ............................................................92
3.4. Interface configuration .................................................................92
3.4.1. Communication start-up procedure ..................................92
3.4.2. Port assignment ...............................................................93
3.4.3. Link parameters ...............................................................94
3.4.4. Protocol parameters .........................................................97
3.4.4.1. Recommendations for parameter tuning
due to specific medium or link characteristics ....98
3.4.4.2. Communication in the dial-up environment ........99
3.4.4.3. Application mapping review .............................101
3.4.4.4. MODBUS/LON gateway function .....................102

ABB Oy, Distribution Automation, Vaasa, FINLAND

We reserve all rights in this document and in the information contained herein.
Reproduction, use or disclosure to third parties without express authority is strictly forbidden. Copyright 2003 ABB

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

4. Appendix A: Profile checklist .............................................. 104

5. Appendix B: List of used abbreviations ............................. 106

1MRS 752015-MUM

Remote Communication Protocol for REC 523

Modbus

Technical Description

Overview of the protocol

The Modbus protocol was first introduced by Modicon Inc. and is widely accepted
as a communication standard for industrial device controllers and PLCs. The
protocol determines how each controller connected to the Modbus network will
recognize a message addressed to it. It also determines the task to be performed and
extracts any data or other information contained in the message. If a reply is
required, the controller will construct a reply message and send it using the Modbus
protocol.
The connection of the master to the slaves can be established either directly or via
modems by using the compatible serial interface RS-232C. This interface defines
the connector pinouts, the cabling, the signal levels, the transmission baud rates, and
the parity checking.
The communication technique used in the Modbus protocol is a master-slave
technique. This means that only one device can be the master and initiate
transactions, while other devices connected to the network are slaves and can
accordingly not initiate any transactions.
A message sent by the master to the slave is called a query (see Fig. 1.-1). The master
can address a query to an individual slave or to all slaves (that is, to broadcast). If a
query is broadcast, the address code 00 will be used. After the slave has received a
query, it will attempt to perform the requested task. If a query has been sent to an
individual slave, the slave will send a message (called a response) to the master. If
it has been broadcast, however, no response will be sent. The response can be either
a normal response (in case of performing the requested task) or an exception
response (otherwise).

Query from the master

Device Address

Function Code

8-bit
Data Bytes

Error Check

Error Check
Response from the slave
Queryresp

Fig. 1.-1 Query response cycle

The devices in the Modbus protocol are made up of four groups of scan or control
points (Digital Inputs, Input Registers, Coils and Holding Registers). Each group
consists of either scan or control points, which all have separate 16-bit addresses.
Depending on the implementation, it is possible to maintain structures like the First
InFirstOut (FIFO), which is built on a selected set of Holding Registers.
5

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

All data addresses in the Modbus protocol are referenced to zero. The first
occurrence of a data item is addressed as item number zero: for example the coil
known as coil 1 is addressed as coil 0000 in the data address field of a Modbus
message and coil 127 as coil 007E hex (126 in decimal format).

1.1.

Transmission frame formats

The format of a query in the Modbus protocol is as follows. The first byte of the
frame is the address of the slave to which the query is directed. If the query is
broadcast, the address will be 00. The second byte is a function code defining the
requested task to be performed. The following bytes are the data to be sent, and the
last two bytes form an error-checking field. The mode specific frame formats are
presented in Fig. 1.1.1.-2 and Fig. 1.1.2.-2.
The response includes fields containing the id of the slave, confirmation of the
performed task in form of a function code, any data to be returned, and an errorchecking field. If an error occurs in the receipt of the message, or if the slave is
unable to perform the requested task, the slave will construct an error message and
send it as its response.
The Modbus protocol has two serial transmission modes: ASCII and RTU. These
modes define the bit contents of the message fields transmitted in the network. They
also determine how information will be packed into the message fields and decoded.
The selected mode and the serial parameters must be the same for all devices in a
Modbus network.

1.1.1.

ASCII mode
If the Modbus ASCII (American Standard Code for Information Interchange) mode
is used, each 8-bit byte in a message will be sent as two ASCII characters forming a
hexadecimal number. The allowable characters are the hexadecimals 0-9 and A-F.
The advantage of this mode compared to the RTU is that the ASCII mode allows
time intervals of up to one second to occur between the characters without causing
an error. The format of each byte is presented in Table 1.1.1-1. Fig. 1.1.1.-1
describes the bit sequence of the ASCII mode.
Table 1.1.1-1

ASCII byte format

Coding System
Bits per Byte

Error Check Field

8-bit byte sent as two ASCII characters representing a

hexadecimal number
1 start bit
7 data bits, the least significant bit sent first
1 bit for even/odd parity; no bit for no parity
1 stop bit if parity is used; 2 bits if no parity
Longitudinal Redundancy Check (LRC)

1MRS 752015-MUM

Modbus

Remote Communication Protocol for REC 523

Technical Description

With parity checking

START 1
2
3

PARITY STOP

Without parity checking

START 1
2
3

STOP

Fig. 1.1.1.-1

STOP

Description of the bit sequence for the ASCII mode

The message starts with a colon character ( : ), followed by ASCII 3A in

hexadecimal format, and ends with a carriage return - line feed (CRLF) pair, that
is, ASCII 0D and 0A in hexadecimal format. The other fields in the message frame
(see Fig. 1.1.1.-2) are identical in both modes of the Modbus protocol, with the
exception of the error-checking field. In the ASCII mode the LRC (Longitudinal
Redundancy Check) method is applied, whereas the CRC (Cyclical Redundancy
Check) method is applied in the RTU mode.
When a device that has been connected to the network detects a colon character, it
decodes the following field to find out whether it is the device to which the query is
directed. For this reason, each device must continuously monitor the Modbus
network.
If a longer interval than one second occurs between the characters, the receiving
device assumes that an error has occurred. Consequently, it clears the receive buffer
and starts waiting for the colon character. A typical message frame is shown in Fig.
1.1.1.-2.
Start

Address

Function

Data

LRC check

End

1 char

2 chars

2*n chars

2 chars

2 chars (CRLF)

Fig. 1.1.1.-2

1.1.2.

Description of the standard frame format

RTU mode
In the RTU (Remote Terminal Unit) mode each message byte is sent in binary
format. Each byte has one start bit, eight data bits, one even, odd or no parity bit, and
one or two stop bits. The number of stop bits depends on whether a parity bit is used.
If odd or even parity is used, the byte has one stop bit. If parity is not used, however,
there are two stop bits. All together there are eleven bits in one byte. The format of
one byte is presented in Table 1.1.2-1.
Table 1.1.2-1

RTU byte format

Coding system

Bits per byte

Error check field

8-bit binary
1 start bit
8 data bits, the least significant bit sent first
1 bit for even/odd parity; no bit for no parity
1 stop bit if parity is used; 2 bits if no parity
Cyclical redundancy check (CRC)

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

The messages are transmitted in the network from left to right, that is, the Least
Significant Bit (LSB) first and the Most Significant Bit (MSB) last. The description
of the bit sequence for the RTU mode is presented in Fig. 1.1.2.-1.

With parity checking

START 1
2
3

PARITY STOP

Without parity checking

START 1
2
3
4

STOP

Fig. 1.1.2.-1

STOP

Description of the bit sequence for the RTU mode

The beginning of each frame is marked with a silent interval of at least 3.5 character
times. This is implemented as a multiple of character times at the baud rate that is
being used. The end of the frame is also marked with a silent interval of at least 3.5
character times.
The entire message frame must be transmitted continuously. If there is a silent
interval longer than 1.5 character times between the characters, the next byte is
considered as the beginning of a new frame. If a new message begins before the 3.5
character time silent interval, the characters received will be considered as part of
the old message frame.
Start

Address

Function

Data

CRC check

End

T1-T2-T3-T4

8 bits

N x 8 bits

16 bits

T1-T2-T3-T4

Fig. 1.1.2.-2

1.2.

Description of the standard frame format

Masters queries
The format of a masters query depends on the function that is being used.
The format of a read function query (read coil status, read input status, read input
registers, read holding registers) is as follows:

Mode

ASCII

RTU

Start character

Address
Function
Starting data address
Quantity of points
Error check field
End characters

2 characters
2 characters
4 characters
4 characters
LRC 2 characters
CR LF (0x0C 0x0A)

3.5 character time of the silent (idle)

line
1 byte
1 byte
2 bytes
2 bytes
CRC 2 bytes
3.5 character time of the silent (idle)
line

1MRS 752015-MUM

Remote Communication Protocol for REC 523

Modbus

Technical Description

The format of a force single coil or a preset single register function query is as
follows:
Mode

ASCII

RTU

Start character

Address
Function
Data address
Data value
Error check field
End characters

2 characters
2 characters
4 characters
4 characters
LRC 2 characters
CR LF (0x0C 0x0A)

3.5 character time of the silent (idle)

line
1 byte
1 byte
2 bytes
2 bytes
CRC 2 bytes
3.5 character time of the silent (idle)
line

The format of a force multiple coils or preset multiple registers function query is as
follows:
Mode

ASCII

RTU

Start character

Address
Function
Data address
Quantity of points
Byte count
Data values

2 characters
2 characters
4 characters
4 characters
2 characters

3.5 character time of the silent (idle)

line
1 byte
1 byte
2 bytes
2 bytes
1 byte
N bytes

Error check field

End characters

2*N charactersa
LRC 2 characters
CR LF (0x0C 0x0A)

CRC 2 bytes
3.5 character time of the silent (idle)
line

a. N is equal to byte count

The format of a read FIFO query is as follows:

Mode

ASCII

RTU

Start character

Address
Function
FIFO address
Error check field
End characters

2 characters
2 characters
4 characters
LRC 2 characters
CR LF (0x0C 0x0A)

3.5 character time of the silent (idle)

line
1 byte
1 byte
2 bytes
CRC 2 bytes
3.5 character time of the silent (idle)
line

The format of a diagnostics function query is as follows:

Mode

ASCII

RTU

Start character

Address
Function
Subfunction
Data field

2 characters
2 characters
4 characters
4 characters

3.5 character time of the silent (idle)

line
1 byte
1 byte
2 bytes
2 bytes
9

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

1.3.

Mode

ASCII

RTU

Error check field

End characters

LRC 2 characters
CR LF (0x0C 0x0A)

CRC 2 bytes
3.5 character time of the silent (idle)
line

Normal responses
The format of a normal response to a master's query depends on what function is
being used.
The format of a response to a read function query is as follows:
Mode

ASCII

RTU

Start character
Address

:
2 characters (echo of
master's query)
2 characters (echo of
master's query)
2 characters

3.5 character time of the silent line

1 byte (echo of master's query)

Function
Byte count
Data values
Error check field
End characters

2*N charactersa
LRC 2 characters
CR LF (0x0C 0x0A)

1 byte (echo of master's query)

1 byte
N bytes
CRC 2 bytes
3.5 character time of the silent line

a. N is equal to byte count

The format of a response to a force single coil or a preset single register function
query is an echo of the query itself.
Mode

ASCII

RTU

Start character

Address
Function
Data address
Data value
Error check field
End characters

2 characters
2 characters
4 characters
4 characters
LRC 2 characters
CR LF (0x0C 0x0A)

3.5 character time of the silent (idle)

line
1 byte
1 byte
2 bytes
2 bytes
CRC 2 bytes
3.5 character time of the silent (idle)
line

The format of a response to a force multiple coils or a preset multiple registers

function query is as follows:

Mode

ASCII

RTU

Start character

Address
Function
Data address
Quantity of points
Error check field
End characters

2 characters
2 characters
4 characters
4 characters
LRC 2 characters
CR LF (0x0C 0x0A)

3.5 character time of the silent (idle)

line
1 byte
1 byte
2 bytes
2 bytes
CRC 2 bytes
3.5 character time of the silent (idle)
line

1MRS 752015-MUM

Remote Communication Protocol for REC 523

Modbus

Technical Description

The format of a response to a read FIFO query is as follows:

Mode

ASCII

RTU

Start character
Address

:
2 characters (echo of master's
query)
2 characters (echo of master's
query)
4 characters
4 characters

3.5 character time of the silent line

1 byte (echo of master's query)

Function
Byte count
FIFO count
FIFO values
Error check field
End characters

4*N charactersa
LRC 2 characters
CR LF (0x0C 0x0A)

1 byte (echo of master's query)

2 byte
2 byte
2*N bytes
CRC 2 bytes
3.5 character time of the silent line

a. N is equal to FIFO count

The format of a response to a diagnostics function query is an echo of the query

itself. If the request is directed to a counter, however, the slave returns the counters
value in the data field.

1.4.

Exception responses
The format of an exception response to a master's query is as follows:
Mode

ASCII

RTU

Start character
Address

:
2 characters (echo of master's
query)
2 characters (echo of master's
query with MSB set)
2 characters
LRC 2 characters
CR LF (0x0C 0x0A)

3.5 character time of the silent line

1 byte (echo of master's query)

Function
Exception code
Error check field
End characters

1 byte (echo of master's query with

MSB set)
1 byte
CRC 2 bytes
3.5 character time of the silent line

An application program in the master is responsible for handling exception

responses. Typical processes include successive attempts to send a query, sending
diagnostic messages to the slave, and notifying the operators.

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

REC 523 profile of Modbus

2.1.

Supported application functions

Function
Function description
code (HEX)
01
02
03
04
05
06
08
0F
10
18

2.2.

Read Coil Status

Reads the on/off status of discrete outputs
Read Input Status
Reads on/off status of discrete inputs
Read Holding Registers
Reads contents of output registers
Read Input Registers
Reads contents of input registers
Force Single Coil
Sets the status of a discrete output
Preset Single Register
Sets the value of a holding register
Diagnostics
Checks the communication system between the master and the slave
Force Multiple Coils
Sets the status of multiple discrete outputs
Preset Multiple Registers
Sets the value of multiple holding registers
Read FIFO queue
Reads the set of multiple holding registers interpreted as a FIFO queue

Supported diagnostic subfunctions

The implementation of the Modbus protocol in REC 523 supports the following
subfunction codes:
Code
00

02
04
10

Name

Description

Return Query Data The data in the query data field is to be returned (looped
back) in the response. The entire response should be
identical to the query.
Restart
The slaves peripheral port is to be initialized and
Communication
restarted, and all of its communications event counters
Option
are to be cleared. If the port is currently in the Listen Only
Mode, no response will be sent. If the port is not currently
in the Listen Only Mode, a normal response will be sent.
This occurs before the restart is executed.
Return Diagnostic The contents of the slaves diagnostic register is returned
Register
in the response.
Force Listen Only Forces the addressed slave to enter the Listen Only Mode
Mode
for Modbus communications.
Clear Counters
Clears all counters and the diagnostic register.
and Diagnostic
Register
Return Bus
The response data field returns the quantity of messages
Message Count
that the slave has detected in the communications system
since its last restart, clear counters operation, or
power-up.

1MRS 752015-MUM

Remote Communication Protocol for REC 523

Modbus

Technical Description
Code
12

Name

Description

Return Bus
Communication
Error Count
Return Bus
Exception Error
Count
Return Slave
Message Count

The response data field returns the quantity of CRC

errors encountered by the slave since its last restart, clear
counters operation, or power-up.
The response data field returns the quantity of Modbus
exception responses returned by the slave since its last
restart, clear counters operation, or power-up.
The response data field returns the quantity of messages
addressed to the slave, or broadcasted that the slave has
processed since its last restart, clear counters operation,
or power-up.
The response data field returns the quantity of messages
addressed to the slave for which it sent no response
(neither a normal response nor an exception response)
since its last restart, clear counters operation, or
power-up.

Return Slave No
Response Count

Note: Sending other subfunction codes than those listed above will cause an illegal
data value exception response.

2.3.

Diagnostic counters
Name

Meaning

Bus Message Count

The number of messages that REC 523 has detected in

the communications system since its last restart, clear
counters operation, or power-up.
Bus Communication Error Count The number of CRC or LRC errors encountered by REC
523 since its last restart, clear counters operation, or
power-up.
Bus Exception Error Count
The number of Modbus exception responses sent by REC
523 since its last restart, clear counters operation, or
power-up.
Slave Message Count
The number of messages addressed to REC 523 or
broadcasted that REC 523 has processed since its last
restart, clear counters operation, or power-up.
Slave No Response Count
The number of messages addressed to REC 523 for
which it sent no response (neither a normal response nor
an exception response) since its last restart, clear
counters operation, or power-up.

2.4.

Possible exception codes

The following exception codes may be generated by REC 523 Modbus Interface.
Code
01
02

Name

Meaning

ILLEGAL FUNCTION The function code received in the query is not an

allowable action for REC 523.
ILLEGAL DATA
The data address or number of items received in the
ADDRESS
query is not allowable or correct for REC 523.
REC 523 will send this exception response if an attempt to
read or write part of a multiple register database object is
detected. Possible objects are time, strings and counters.

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description
Code
03

Name

Meaning

ILLEGAL DATA
VALUE

A value contained in the query data field is out of range.

The contents of the register or the status of the coil is not
changed.

Note: If an Illegal data value exception response is generated when attempting to

preset multiple registers, the contents of the register to which an illegal value has
been imposed and of the following registers will not be changed. Registers that have
already been preset will not be restored.

2.5.

Event reporting
The event reporting function has been added to the Modbus interface of REC 523 as
a proprietary extension of the protocol specification. There is no defined standard
way of representing and transmitting events in the Modbus protocol. However, some
vendors have introduced such solutions in their systems.
The event support is configurable (See Protocol parameters, section 3.4.4.). There
are two options: either the reporting function can be suppressed or one of six
implemented methods of event handling can be selected.
Method

Description

No events
SACE with a short
time stamp

No events are passed via the MODBUS interface

The head of the event queue is mapped as a set of holding registers.
The master acknowledges a successful read of the event by writing
to the dedicated coil in the slave, which allows the next event to be
submitted. The time stamp contains milliseconds, seconds and
minutes.
SACE with a full time The same as above, but with a full time stamp (containing time and
stamp
date)
MicroScada
The method used by the MicroScada: the events are placed in two
event queues (separate for analog and digital events). The event
queue contains the state (for indicating buffer overflow), the actual
number of events, and an event buffer. There is a special holding
register in the slave (EVCT) that is used for time synchronization and
locking of the event buffers. The time stamps are 16-bit counters
with 10ms resolution. This method requires time synchronization
with cycles shorter than 5min.
MicroScada with a full The same as above but with a full time stamp.
time stamp
The function Read FIFO 24 (18 hex) is used to read the events. The
Modicon FIFO read
method with a short
event format is the same as for the SACE with short time stamp. The
time stamp
master locks the FIFO queue by setting the dedicated coil and
acknowledges a successful read by resetting the coil. This clears the
FIFO and allows the following events to be submitted.
Modicon FIFO read
The function Read FIFO 24 (18 hex) is used to read the events. The
method with a full time event format is the same as for the SACE with a full time stamp. The
stamp
master locks the FIFO queue by setting the dedicated coil and
acknowledges a successful read by resetting the coil. This clears the
FIFO and allows the following events to be submitted.

The dial-up environment has an additional feature: after the Modbus has received an
event from the application, it will try to open the communication channel to indicate
to the master that the event buffer or buffers are not empty. The attempt to open the

1MRS 752015-MUM

Modbus

Remote Communication Protocol for REC 523

Technical Description

channel is made after the configured dial timeout. If the slave fails to connect, the
timeout will be reactivated. When it has expired, another attempt will be made to
establish a connection (see section Configuring dial-up connection for details).

Event collecting algorithms

SACE methods

Read control coil

Is equal to 1?
YES

Read event queue

(n registers*)

Response received?
YES

Clear control coil

SACEmet

2.5.1.

* Note:
For the short time stamp mode n=4
For the full time stamp mode n=5

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

MicroScada methods

Write 2 to control coil

(lock event queue)

Read event queue header

(3 registers)

Are events in queue?

YES

Read events
(n registers*)
NO

Response received?
YES

MSmet

Write 0 (if timesync is

needed) to control register
(unlock and clear queue)

* Note:
For the digital queue and the short time stamp mode n=2 for each event
For the analog queue and the short time stamp mode n=3 for each event
For the digital queue and the full time stamp mode n=4 for each event
For the analog queue and the full time stamp mode n=5 for each event

1MRS 752015-MUM

Remote Communication Protocol for REC 523

Modbus

Technical Description

Modicon methods

Read control coil

Is equal to 1?
YES

Write 0 to control coil

(Lock FIFO)

Read FIFO
(function 24)

Response received?

Write 1 to control coil

(clear FIFO)

MODICmet

YES

Note: The contents of the FIFO queue is sent as a response. There are four registers
for each event with a short time stamp and five registers for each event with a full
time stamp.

2.5.2.

Event queue descriptions

SACE method with a short time stamp
According to this method, the head of the event queue is mapped as a set of holding
registers. The master acknowledges a successful read of the event by writing to the
dedicated coil. This allows the next event to be submitted. The time stamp contains
milliseconds, seconds and minutes.

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

Event structure:
Address

Meaning

Base

The address and the type of the static data Address*2 for digital events
item that triggered the event
Address*2+1 for analog events
The value of the event
0 or 1 for digital events
0...65535 for analog events
Time stamp LO (milliseconds)
0...999
Time stamp HI (seconds and minutes)
0...3599

Base+1
Base+2
Base+3

Values

The use of the coil for event reception acknowledgment and for testing event
availability:
Value

Meaning

Read 0
Read 1
Write 0

Event buffer empty

Event buffer full
Event successfully read submit the next event

SACE method with a full time stamp

According to this method, the head of the event queue is mapped as a set of holding
registers. The master acknowledges a successful read of the event by writing to the
binary output, which allows the next event to be submitted. The time stamp contains
full time counted since January 1, 1970, 00:00 (in milliseconds and seconds).
Event structure:
Address

Meaning

Base

The address and the type of the static data Address*2 for digital events
item that triggered the event
Address*2+1 for analog events
The value of the event
0 or 1 for digital events
0...65535 for analog events
Time stamp (milliseconds)
0...999
Time stamp (seconds since beginning of 0...65535
1970 lower word)
Time stamps (seconds since beginning of 0...65535
1970 higher word)

Base+1
Base+2
Base+3
Base+4

Values

The use of the coil for event reception acknowledgment and for testing event
availability:
Value

Address

Meaning

EventBase
EventBase+1
EventBase+2
EventBase+3
EventBase+4

The address of the input register

The value of the event
0...999
Time stamp (seconds since beginning of 1970 lower word)
Time stamps (seconds since beginning of 1970 higher word)

Event control register structure:

Bit
0
1
2-15

Meaning
Not used
Event buffer lock (rising edge lock, falling edge unlock and clear)
Not used

Note: Unlocking the event buffer causes clearance of all its contents. Both queues
have separate control registers (digital and analog) as well as a common one. When
the common control register is being used, unlocking causes clearance of the
previously read queue only. Separate control registers operate on one queue only.
Modicon method with a short time stamp
According to this method, function 24 is used for reading the events organized in the
FIFO queue. The first holding register contains the number of holding registers in
the FIFO queue (excluding itself), whereas the following ones contain the events.
The time stamp contains milliseconds, seconds and minutes.

1MRS 752015-MUM

Remote Communication Protocol for REC 523

Modbus

static data item that triggered the
event
EventBase+1 The value of the event
EventBase+2 Time stamp (milliseconds)
EventBase+3 Time stamp (seconds since
beginning of 1970 lower word)

Values
Address*2 for digital events
Address*2+1 for analog events
0 or 1 for digital events
0...65535 for analog events
0...999
0...65535

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description
Address

Meaning

EventBase+4 Time stamps (seconds since

beginning of 1970 higher word)

Values
0...65535

The usage of the coil for FIFO locking and a successful read acknowledgment:
Value

Meaning

Read 0
Read 1
Write 0
Write 1

The FIFO empty

The FIFO not empty
Clear and unlock the FIFO
Lock the FIFO

Note: In both Modicon methods, the FIFO count register contains the number of
holding registers in the queue NOT the number of events.

1MRS 752015-MUM

Remote Communication Protocol for REC 523

Modbus

Technical Description

Protocol interface implementation

3.1.

Application to protocol mapping

3.1.1.

POD concept
The Protocol Object Dictionary (POD) is a cross-reference table between the REC
523 application and the Modbus protocol. This table defines what information can
be accessed from the device using the protocol interface. As REC 523 is a
programmable device and may run various application setups (different sets of
function blocks), the POD is also re-configurable. This re-configurable table (called
visible POD) is used during device initialization to create the POD used at runtime
(called operational POD). The visible POD can cover all possible device application
setups. During the start-up all present function blocks will be automatically detected
and only data items of these blocks will be included in the operational POD.

3.1.2.

POD configuration
A default version of the visible POD is provided in the device software. It includes
the mapping of process data and events from all available function blocks, together
with communication interface parameters for the Modbus protocol. Application
settings, parameters, recorded measurement and disturbance data are not included in
this mapping (except for communication parameters and power quality recordings,
which are included).
The default POD contents can be uploaded for review and modified using the
available Protocol Editing Tool available in the CAP 505 Tool Box. Following the
changes the new POD contents can be downloaded to the REC 523 unit and
activated by storing the changes and resetting the device.

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

POD editing
tool on PC
Edited
visible POD

Download of
modified POD
to the device

Upload for
review/modification

Operational
POD

Visible
POD
only at
start-up of
unconfigured
device

initialization of
communication
interface
PODconf

Default
POD
in program
memory

REC 523

Fig. 3.1.2.-1

POD in the REC 523 device

Modification of the POD contents may be required due to the following situations:
A different addressing concept is used in the system because of the requirements
of the primary (controlling) station, or limitations in the protocol data addressing
(readdressing of mapped application objects)
Elimination of obsolete data and events from active function blocks (data items
not required or not processed by the primary station)
Changes in mapping (for example PDU type, conversion of data value, type of
data acquisition (spontaneous or on request), assignment to groups, etc.)

3.1.2.1.

Database mapping
The Modbus protocol interface supports six data types:
Digital inputs - these entries contain read only discrete values (values of the
range from 0 to 1)
Coils (digital outputs) - these entries contain read/write discrete values (values
of the range from 0 to 1)
Input registers - these entries contain read only 16-bit register values (values of
range from 0 to 65535, but is some cases signed values in U2 format will be used)
Holding (output) registers - these entries contain read/write 16-bit register
values (values of the range from 0 to 65535)
Digital events - events associated with a change of the digital input status
Analog events - events associated with a change of the input register status

1MRS 752015-MUM

Remote Communication Protocol for REC 523

Modbus

Technical Description

3.1.2.2.

Event control objects

The use of event control and queue entries in the POD depends on the chosen event
reporting mode. The table below explains which entries are in use for each event
reporting mode.
Mode

Name of entry

Description

SACE

EQCTRLCO
COEVENTQ
ANEVENTQ
DIEVENTQ
CEQCTRLR
AEQCTRLR
DEQCTRLR
EQCTRLCO
FIFOEVTQ

Event queue control coil

Common event queue
Analog event queue
Digital event queue
Common event queue control register
Analog event queue control register
Digital event queue control register
Event queue control coil
FIFO queue pointer

MicroSCADA

MODICON

3.1.3.

Defining POD contents

3.1.3.1.

Visible POD entry format

A visible POD for the Modbus may contain a maximum of 2500 entries. The number
of defined entries is revision dependent, for example, the default POD of revision D
of REC 523 occupies 2203 entries.
The visible POD can be accessed using the Protocol Editing Tool. The attributes in
the POD table can be divided into two main categories: general and protocol
attributes. Protocol attributes of the visible POD can be further divided into two
categories:
Attributes of the application (application object name, data type and operation
type)
Attributes of the communication (object address)
The flag parameter in use can be used to facilitate the removal (masking) of POD
entries from the operational POD. The structure of the Modbus POD is presented in
Fig. 3.1.3.1.-1.

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

MB_POD

Fig. 3.1.3.1.-1 Protocol Editing Tool with the Modbus POD

The meaning of each item of a POD entry and its corresponding index is shown in
the table below:
Index Name
0

1
2
3

Description

Object name The application name of the object, in most cases in SPA format, for
example F031I001 (input 1 from channel 31), F031E000 (event 0 from
channel 31) etc. with some exceptions like for example DEVCLOCK,
that is, one field of the device clock
Data type
The type of item in the database or the type of event
Operation
The type of operation that will be performed when accessing this item
type
Address
The Modbus address of the data item (containing 2 parts: high order
word indicates the type according to the Modbus convention and the
low order word point number, for example 00010001 HEX indicates
the digital input number 1, and 00030005 HEX the input register
number 5). Note that an address sent in Modbus frames is equal to
the point number decreased by 1 (for example point number 1 has the
address 0)
In use flag
0 - not available, 1 available to the master station

In queries and responses addresses are used instead of point numbers, that is, low
order words of addresses placed in the POD decreased by 1.
Data type codes:
Name

Code Description

BOOL
DPBOOL

0
1

SINT

Boolean value - 0 or 1
Double point value:
00 - middle, 01 -closed (earthed), 10 - opened (freed),
11 faulty
16-bit signed integer

1MRS 752015-MUM

Remote Communication Protocol for REC 523

Modbus

Technical Description
Name

Code Description

INT
DINT
USINT
UINT
UDINT
REAL
TIME
TOD

3
4
5
6
7
8
9
10

DATE

CLOCK
STRING
SPA
BYTE
WORD
DWORD
EV_NODAT
EV_1BIT
EV_2BIT
EV_3BIT

12
13
14
15
16
17
18
19
20
21

EV_FLOAT
EV_INT16
EV_INT32
EV_COUNT
EV_32BIT

22
23
24
25
26

16-bit signed integer

32-bit signed integer
16-bit unsigned integer
16-bit unsigned integer
32-bit unsigned integer
32-bit floating point
32-bit unsigned integer containing number of milliseconds
32-bit unsigned integer containing time of the day since
midnight in 100us units
32-bit unsigned integer containing number of days since 0101-1980
Full time type used for time synchronisation (function)
String value
Transparent SPA message (function)
8-bit unsigned integer
16-bit unsigned integer
32-bit unsigned integer
Event without data
Event with 1-bit data
Event with 2-bit data
Event with 3-bit data
(treated as EV_NODAT - phase information will be ignored)
Event with floating point value
Event with 16-bit integer value
Event with 32-bit integer value
Event with counter value
Event with 32-bit value

Modbus data types:

Name

Code Description

EV_CQ

EV_AQ

EV_DQ

FIFO_CQ

TIME_YR
TIME_MON
TIME_DAY
TIME_HR
TIME_MIN
TIME_SEC
TIME_MS

54
55
56
57
58
59
60

A common event queue for analog and digital events (used

by the SACE methods)
An event queue for analog events (used by the MicroSCADA
method)
An event queue for digital events (used by the MicroSCADA
method)
A common event queue for analog and digital events (used
by the MODICON methods)
The year field of the device clock
The month field of the device clock
The day field of the device clock
The hour field of the device clock
The minute field of the device clock
The seconds field of the device clock
The milliseconds field of the device clock

Note:
The set of supported data types can be extended in future releases

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

To enable the required conversion of data items before passing them on to the
master through Modbus or vice versa, a set of operations (conversion routines)
has been defined. Each type of operation is assigned a numeric code used by the
POD.
List of operation types associated with data:
Operation type

Code Description

No operation

Scale by 10
Scale by 100
Scale by 1000
Scale by 0.1
Scale by 0.01
Scale by 0.001
Inverse 1 bit logic
Inverse open/close
Always close

1
2
3
4
5
6
7
8
9

Always open

Always middle

Always faulty

Always off

Always on

Dummy 0
Event ACK

15
16

Analog event
control
Digital event control

Read event queue

Scale by 1 signed
Scale by 10 signed
Scale by 100
signed
Scale by 1000
signed
Scale by 0.1 signed
Scale by 0.01
signed
Scale by 0.001
signed
Timer
Common event
control

19
20
21
22

No special handling all actions according to MODBUS and

database type
The value will be multiplied by 10 and treated as unsigned
The value will be multiplied by 100 and treated as unsigned
The value will be multiplied by 1000 and treated as unsigned
The value will be multiplied by 0.1 and treated as unsigned
The value will be multiplied by 0.01 and treated as unsigned
The value will be multiplied by 0.001 and treated as unsigned
0<->1 conversion
1<->2 conversion
Conversion for events of the type EV_NODAT or EV_3BIT used
to set the analog value 1
Conversion for events of the type EV_NODAT or EV_3BIT used
to set the analog value 2
Conversion for events of the type EV_NODAT or EV_3BIT used
to set the analog value 0
Conversion for events of the type EV_NODAT or EV_3BIT used
to set the analog value 3
Conversion for events of the type EV_NODAT or EV_3BIT used
to set the digital value 0
Conversion for events of the type EV_NODAT or EV_3BIT used
to set the digital value 1
Used for write only items
The coil used to acknowledge the receiving of events and the
lock event queue while reading
The register used to control the analog event queue (used for
both MicroSCADA methods)
The register used to control the digital event queue (used for
both MicroSCADA methods)
This register icomes first in the event queue
The value will be treated as signed
The value will be multiplied by 10 and treated as signed
The value will be multiplied by 100 and treated as signed

The value will be multiplied by 1000 and treated as signed

24
25

The value will be multiplied by 0.1 and treated as signed

The value will be multiplied by 0.01 and treated as signed

The value will be multiplied by 0.001 and treated as signed

27
28

The device clock will be read or written

The register used to control both event queues (used for both
MicroSCADA methods)

Note: The set of supported operation types can be extended in future releases.
28

1MRS 752015-MUM

Remote Communication Protocol for REC 523

Modbus

Technical Description

MODBUS addresses:
Point (hex)

Description

0000XXXX
0001XXXX
0002XXXX
0003XXXX
0004XXXX
0005XXXX

The coil of address XXXX

The digital input of address XXXX
A digital event associated with digital input of XXXX
The input register of address XXXX
The holding register of address XXXX
An analog event associated with input register of address XXXX

Note that digital and analog events are not directly accessible using point numbers.
To access this data, the appropriate queue (according to the chosen event reporting
mode) must be read.

3.1.3.2.

POD diagnostics
Each POD table that has been downloaded to the unit has an identification string.
The identification string is used to check the consistency between the visible POD
stored in REC 523 and the POD opened by Protocol Editing Tool. Refer to the POD
Tool Operators Manual for further information.

Prot_openMB

Fig. 3.1.3.2.-1 Protocol Editing Tool with Open dialog of the Modbus POD
After the POD has been downloaded to and stored in the unit, it is possible to upload
the POD diagnostics from the unit.

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

diagnostics

Fig. 3.1.3.2.-2 Protocol Editing Tool with POD diagnostics

The meaning of each parameter is presented in the table below:
Name

Description

Total number of
entries

The total number of visible POD entries

This value is determined by the POD structure size. Both
used and unused entries are counted.
The number of entries not in use (in use field set to 0)
This number covers both defined and empty POD entries
with the in use field set to 0.
The translation applies only to the entries with the in use
flag set, correct or corrected contents, and referring to
valid objects or events of the function blocks included in
the application project.
This checking applies only to the entries with the in use
flag set.

Number of Not In
Use entries
Number of entries
translated into
operational POD
Number of
uncorrectable
invalid entries (INV)
Number of corrected
entries (COR)
Number of
nonexistent function
block entries (NBL)
Number of entries
referring to invalid
objects (NOB)

SPA
parameter
F503V060

F503V061

F503V066

F503V062

This checking applies only to the entries with the in use F503V063
flag set.
This checking applies only to the entries with the in use F503V064
flag set.
This checking applies only to the entries with the in use F503V065
flag set.

1MRS 752015-MUM

Remote Communication Protocol for REC 523

Modbus

Technical Description

If necessary, the results of the diagnostics can be further analyzed by selecting the
Show data (see Fig. 3.1.3.2.-3). Diagnostic details introduces a list of items
belonging to the selected category. The list is sorted out based on the row number of
the item. By using this information, the required changes and corrections can be
made to the POD.

Diag_Det

Fig. 3.1.3.2.-3 Diagnostic Details

3.1.3.3.

Examples of mapping application data into the Modbus protocol

An application object with a binary data value is accessible at request in the
database (object name given):
Changes are reported as binary events (event codes given)
The same Modbus address should be used for sending object changes (binary
events) and database values at request (binary static data)
Description

Name

Type

Start signal from 3I> stage

Start signal from 3I> stage reset
Start signal from 3I> stage activated

F031O001 UINT
F031E000 EV_3BIT
F031E001 EV_3BIT

Operation

Point (hex)

No operation
Always off
Always on

00011000
00021000
00021000

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

Application object with 2 point information (mapped as input register):

Changes are reported as 2-bit events (event codes given)
The same Modbus address should be used for sending object changes (analogue
events) and database values at request (analogue static data)
Description

Name

Type

Operation

Point (hex)

Disconnector position
Disconnector in position open
Disconnector in position closed
Disconnector in position faulty
Disconnector in position middle

F122V001
F122E000
F122E001
F122E002
F122E003

UINT
EV_2BIT
EV_2BIT
EV_2BIT
EV_2BIT

No operation
Always open
Always close
Always faulty
Always middle

00032500
00052500
00052500
00052500
00052500

Note: When the code of operation is set to 0 (no operation), the data conversion will
be performed according to the database and the Modbus type of the object. Because
there is only single point binary information in the Modbus protocol, 2 point
information is encoded as an input register.
Application object with analog data values accessible at request in the database
(object name given):
The binary data values are not accessible in the database but stored in the internal
protocol tables according to the most recent event reported
Changes are reported as two kinds of events: binary and analog
The same Modbus address should be used for sending object changes (analog
events) and database values at request (analog static data)
The same Modbus address should be used for sending binary object changes
(digital events) and static values accessible at request from the internal protocol
data tables
Description

Name

Type

Operation

Point
(hex)

Uo value
Uo high warning off (analog value)
Uo high warning on (analog value)
Uo high alarm off (analog value)
Uo high alarm on (analog value)
Uo delta
Uo high warning off (digital value
stored)
Uo high warning on (digital value
stored)
Uo high alarm off (digital value stored)
Uo high alarm on (digital value stored)
Uo high warning off (digital event)
Uo high warning on (digital event)
Uo high alarm off (digital event)
Uo high alarm on (digital event)

F205I001
F205E00
F205E01
F205E02
F205E03
F205E05
F205E00

REAL
EV_FLOAT
EV_FLOAT
EV_FLOAT
EV_FLOAT
EV_FLOAT
EV_FLOAT

Scale by 10
Scale by 10
Scale by 10
Scale by 10
Scale by 10
Scale by 10
Always off

00030180
00050180
00050180
00050180
00050180
00050180
00010180

F205E01

EV_FLOAT Always on

00010180

F205E02
F205E03
F205E00
F205E01
F205E02
F205E03

EV_FLOAT
EV_FLOAT
EV_FLOAT
EV_FLOAT
EV_FLOAT
EV_FLOAT

00010181
00010181
00020180
00020180
00020181
00020181

Always off
Always on
Always off
Always on
Always off
Always on

Entries used to control the disconnector:

Device time year

Device time month
Device time day
Device time hour
Device time minute
Device time second
Device time millisecond

DEVCLOCK
DEVCLOCK
DEVCLOCK
DEVCLOCK
DEVCLOCK
DEVCLOCK
DEVCLOCK

TIME_YR
TIME_MON
TIME_DAY
TIME_HR
TIME_MIN
TIME_SEC
TIME_MS

Timer
Timer
Timer
Timer
Timer
Timer
Timer

00040001
00040002
00040003
00040004
00040005
00040006
00040007

Event queue used by both SACE methods

Description

Name

Type

Operation

Point (hex)

Event queue control coil

Common event queue

COEVENTQ

EV_CQ

00048000

Event queue control coil

EQCTRLCO

USINT

Read event
queue
Event ACK

00007FFF

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

change

F213E000
F213E001

Digital event

0800

0 reset
1 activated

Input MEAI1 high alarm change F213E002

F213E003

Digital event

0801

0 reset
1 activated

Input MEAI1 low warning

change

F213E004
F213E005

Digital event

0802

0 reset
1 activated

Input MEAI1 low alarm change

F213E006
F213E007

Digital event

0803

0 reset
1 activated

Input MEAI1

213I001

Input register

0800

-10000...10000

Input MEAI1 change

F213E000
F213E001
F213E002
F213E003
F213E004
F213E005
F213E006
F213E007
F213E011

Analog event

0800

-10000...10000

Input MEAI2 high alarm change

F214E002
F214E003

Digital event

0811

0 reset
1 activated

Description

Name

Values

Function block MEAI2

1MRS 752015-MUM

Remote Communication Protocol for REC 523

Modbus

Technical Description

Type

Point
Values
(hex)

Input MEAI2 low warning change F214E004

F214E005

Digital event

0812

0 reset
1 activated

Input MEAI2 low alarm change

F214E006
F214E007

Digital event

0813

0 reset
1 activated

Input MEAI2

F214I001

Input register

0810

-10000...10000

Input MEAI2 change

F214E000
F214E001
F214E002
F214E003
F214E004
F214E005
F214E006
F214E007
F214E011

Analog event

0810

-10000...10000

Description

change

F215E000
F215E001

Digital event

0820

0 reset
1 activated

Input MEAI3 high alarm change F215E002

F215E003

Digital event

0821

0 reset
1 activated

Input MEAI3 low warning

change

F215E004
F215E005

Digital event

0822

0 reset
1 activated

Input MEAI3 low alarm change F215E006

F215E007

Digital event

0823

0 reset
1 activated

Input MEAI3

F215I001

Input register

0820

-10000...10000

Input MEAI3 change

F215E000
F215E001
F215E002
F215E003
F215E004
F215E005
F215E006
F215E007
F215E011

Analog event

0820

-10000...10000

Name

Type

Point
(hex)

Values

Input MEAI4 high warning state F216E000

F216E001

Digital input

Input MEAI4 change

F216E000
F216E001
F216E002
F216E003
F216E004
F216E005
F216E006
F216E007
F216E011

Analog event

0830

-10000...10000

Input MEAI5 high alarm change F217E002

F217E003

Digital event

0841

0 reset
1 activated

Input MEAI5 low warning

change

F217E004
F217E005

Digital event

0842

0 reset
1 activated

Input MEAI5 low alarm change

F217E006
F217E007

Digital event

0843

0 reset
1 activated

Input MEAI5

F217I001

Input register

0840

-10000...10000

Input MEAI5 change

F217E000
F217E001
F217E002
F217E003
F217E004
F217E005
F217E006
F217E007
F217E011

Analog event

0840

-10000...10000

Values

Function block MEAI5

Description

1MRS 752015-MUM

Remote Communication Protocol for REC 523

Modbus

change

F218E000
F218E001

Digital event

0850

0 reset
1 activated

Input MEAI6 high alarm change F218E002

F218E003

Digital event

0851

0 reset
1 activated

Input MEAI6 low warning

change

F218E004
F218E005

Digital event

0852

0 reset
1 activated

Input MEAI6 low alarm change F218E006

F218E007

Digital event

0853

0 reset
1 activated

Input MEAI6

F218I001

Input register

0850

-10000...10000

Input MEAI6 change

F218E000
F218E001
F218E002
F218E003
F218E004
F218E005
F218E006
F218E007
F218E011

Analog event

0850

-10000...10000

Input MEAI7 high alarm change F219E002

F219E003

Digital event

0861

0 reset
1 activated

Input MEAI7 low warning

change

F219E004
F219E005

Digital event

0862

0 reset
1 activated

Input MEAI7 low alarm change F219E006

F219E007

Digital event

0863

0 reset
1 activated

Input MEAI7

Input register

0860

-10000...10000

Description

Name

Values

Function block MEAI7

Description

F219I001

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

Description

Name

Type

Point
(hex)

Values

Input MEAI7 change

F219E000
F219E001
F219E002
F219E003
F219E004
F219E005
F219E006
F219E007
F219E011

Analog event

0860

-10000...10000

Input MEAI8 high alarm change F220E002

F220E003

Digital event

0871

0 reset
1 activated

Input MEAI8 low warning

change

F220E004
F220E005

Digital event

0872

0 reset
1 activated

Input MEAI8 low alarm change F220E006

F220E007

Digital event

0873

0 reset
1 activated

Input MEAI8

F220I001

Input register

0870

-10000...10000

Input MEAI8 change

F220E000
F220E001
F220E002
F220E003
F220E004
F220E005
F220E006
F220E007
F220E011

Analog event

0870

-10000...10000

Function block MEAI8

Values

1MRS 752015-MUM

Remote Communication Protocol for REC 523

Modbus

Technical Description

Description

Name

Type

Point
(hex)

Io change

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

F200I001

Input register

0300

0...20000
0A...20000A

IL2

F200I002

Input register

0301

0...20000
0A...20000A

IL3

F200I003

Input register

0302

0...20000
0A...20000A

IL1 change

F200E000
F200E001
F200E006
F200E007
F200E012
F200E013
F200E018
F200E019
F200E025

Analog event

0300

0...20000
0A...20000A

IL2 change

F200E002
F200E003
F200E008
F200E009
F200E014
F200E015
F200E020
F200E021
F200E027

Analog event

0301

0...20000
0A...20000A

IL3 change

F200E004
F200E005
F200E010
F200E011
F200E016
F200E017
F200E022
F200E023
F200E029

Analog event

0302

0...20000
0A...20000A

Values

1MRS 752015-MUM

Remote Communication Protocol for REC 523

Modbus

change

F202E016
F202E017

Digital event

038A

0 - reset
1 - activated

IL3 LV side low alarm change

F202E022
F202E023

Digital event

038B

0 - reset
1 - activated

IL1 LV side

F202I001

Input register

0380

0...20000
0A...20000A

IL2 LV side

F202I002

Input register

0381

0...20000
0A...20000A

IL3 LV side

F202I003

Input register

0382

0...20000
0A...20000A

Description

Name

Values

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

Description

Name

Type

Point
(hex)

IL1 LV side change

F202E000
F202E001
F202E006
F202E007
F202E012
F202E013
F202E018
F202E019
F202E025

Analog event

0380

0...20000
0A...20000A

IL2 LV side change

F225E000
F225E001

Digital input

701

0 = OFF
1 = ON

Overwrite of recording

F225E003

Digital input

702

Configuration error

F225E005

Digital input

703

Recording triggered

F225E031

Digital input

704

Reset memory

F225M002

Coil

0700

1 reset

Description

Name

Type

Point
(hex)

Values

Frequency high warning state

F208E000
F208E001

Digital input

0600

0 reset
1 activated

Frequency high alarm state

F208E002
F208E003

Digital input

0601

0 reset
1 activated

Frequency low warning state

F208E004
F208E005

Digital input

0602

F208E003

Digital event

0601

0 reset
1 activated

Frequency low warning

change

F208E004
F208E005

Digital event

0602

0 reset
1 activated

Frequency low alarm change

F208E006
F208E007

Digital event

0603

0 reset
1 activated

Frequency

F208I001

Input register

0600

1000...7500
10.00Hz...75.00Hz

Change of frequency

F208E000
F208E001
F208E002
F208E003
F208E004
F208E005
F208E006
F208E007
F208E009

Analog event

0600

1000...7500
10.00Hz...75.00Hz

Description

Name

Type

Point
(hex)

Reset flag

Name

Values

Function block MEPE7

Values

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

Description

Name

Type

Point
(hex)

Q3 low alarm change

F207E014
F207E015

Digital event

0508

0 reset
1 activated

F207I001

Input register

0500

-9999...9999

999900kW...999900k
W

F207I002

Input register

0501

-9999...9999

999900kW...999900kv
ar

Power factor DPF

F207I003

Input register

0502

-100...100
-1.00...1.00

Power factor PF

F207I004

Input register

0503

-100...100
-1.00...1.00

P3 demand

F207I005

Input register

0504

-9999...9999

999900kW...999900k
W

Q3 demand

F207I006

Input register

0505

-9999...9999

999900kW...999900kv
ar

F207E021

Input register

0506

-9999...9999

999900kW...999900kv
a

Active energy

F207V414

Input register

0507

0...9999
0...999900 kWh

Active reverse energy

F207V415

Input register

0508

0...9999
0...999900 kWh

Reactive energy

F207V416

Input register

0509

0...9999
0...999900 kvarh

Reactive reverse energy

F207V417

Input register

050A

0...9999
0...999900 kvarh

Change of P3

F207E000
F207E001
F207E002
F207E003
F207E008
F207E009
F207E010
F207E011
F207E017

Analog event

0500

-9999...9999

999900kW...999900k
W

Change of Q3

F207E004
F207E005
F207E006
F207E007
F207E012
F207E013
F207E014
F207E015
F207E019

Analog event

0501

-9999...9999

999900kW...999900kv
ar

Change of DPF

F207E023

Analog event

0502

-100...100
-1.00...1.00

Change of S3

F207E021

Analog event

0506

-9999...9999

999900kW...999900kv
a

Values

1MRS 752015-MUM

Remote Communication Protocol for REC 523

Modbus

Technical Description

Description

Name

Type

Point
(hex)

Active energy

F207E025

Analog event

0507

0...9999
0...999900 kWh

Active reverse energy

F207E027

Analog event

0508

0...9999
0...999900 kWh

Reactive energy

F207E029

Analog event

0509

0...9999
0...999900 kvarh

Reactive reverse energy

F207E031

Type

Point
(hex)

Uo LV side high warning state F226E000

F226E001

Digital input

0280

0 reset
1 activated

Uo LV side high alarm state

F226E002
F226E003

Digital input

0281

0 reset
1 activated

Uo LV side high warning

change

F226E000
F226E001

Digital event

0280

0 reset
1 activated

Uo LV side high alarm change F226E002

F226E003

Digital event

0281

0 reset
1 activated

Uo LV side

F226I001

Input register

0280

0...15000
0V...150000V

Uo LV side change

F226E000
F226E001
F226E002
F226E003
F226E005

Analog event

0280

0...15000
0V...150000V

Description

Name

Values

Function block MEVO3A

Description

Name

Type

Point
(hex)

U1 or U12 high warning state

F204E000
F204E001
F204E032
F204E033

Digital input

0400

Values
0 reset
1 activated

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

change

F204E000
F204E001
F204E032
F204E033

Digital event

0400

0 reset
1 activated

U1 or U12 high alarm change

F204E006
F204E007
F204E038
F204E039

Digital event

0401

change

F204E002
F204E003
F204E034
F204E035

Digital event

0404

0 reset
1 activated

U2 or U23 high alarm change

F204E008
F204E009
F204E040
F204E041

Digital event

0405

0 reset
1 activated

U2 or U23 low warning change F204E014

F204E015
F204E046
F204E047

Digital event

0406

0 reset
1 activated

U2 or U23 low alarm change

F204E020
F204E021
F204E052
F204E053

Digital event

0407

0 reset
1 activated

U3 or U31 high warning

change

F204E004
F204E005
F204E036
F204E037

Digital event

0408

0 reset
1 activated

U3 or U31 high alarm change

F204E010
F204E011
F204E042
F204E043

Digital event

0409

0 reset
1 activated

U3 or U31 low warning change F204E016

F204E017
F204E048
F204E049

Digital event

040A

0 reset
1 activated

U3 or U31 low alarm change

F204E022
F204E023
F204E054
F204E055

Digital event

040B

0 reset
1 activated

U1 or U12

F204I001

Input register

0400

0...9999
0.0kV...999.9kV

U2 or U23

F204I002

Input register

0401

0...9999
0.0kV...999.9kV

U3 or U31

F204I003

Input register

0402

0...9999
0.0kV...999.9kV

U1 or U12 change

F204E000
F204E001
F204E006
F204E007
F204E012
F204E013
F204E018
F204E019
F204E025
F204E032
F204E033
F204E038
F204E039
F204E044
F204E045
F204E050
F204E051
F204E057

Analog event

0400

0...9999
0.0kV...999.9kV

Values

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

Description

Name

Type

Point
(hex)

U2 or U23 change

F204E002
F204E003
F204E008
F204E009
F204E014
F204E015
F204E020
F204E021
F204E027
F204E034
F204E035
F204E040
F204E041
F204E046
F204E047
F204E052
F204E053
F204E059

Analog event

0401

0...9999
0.0kV...999.9kV

U3 or U31 change

F204E004
F204E005
F204E010
F204E011
F204E016
F204E017
F204E022
F204E023
F204E029
F204E036
F204E037
F204E042
F204E043
F204E048
F204E049
F204E054
F204E055
F204E061

Analog event

0402

0...9999
0.0kV...999.9kV

Values

Function block MEVO3B

Remote Communication Protocol for REC 523

Modbus

Technical Description

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

Type

Point
(hex)

U3 or U31 LV side high warning F206E004

change
F206E005
F206E036
F206E037

Digital event

0488

0 reset
1 activated

U3 or U31 LV side high alarm

change

F206E010
F206E011
F206E042
F206E043

Digital event

0489

0 reset
1 activated

U3 or U31 LV side low warning F206E016

change
F206E017
F206E048
F206E049

Digital event

048A

0 reset
1 activated

U3 or U31 LV side low alarm

change

F206E022
F206E023
F206E054
F206E055

Digital event

048B

0 reset
1 activated

U1 or U12 LV side

F206I001

Input register

0480

0...9999
0.0kV...999.9kV

U2 or U23 LV side

F206I002

Input register

0481

0...9999
0.0kV...999.9kV

U3 or U31 LV side

F206I003

Input register

0482

0...9999
0.0kV...999.9kV

U1 or U12 LV side change

F206E000
F206E001
F206E006
F206E007
F206E012
F206E013
F206E018
F206E019
F206E025
F206E032
F206E033
F206E038
F206E039
F206E044
F206E045
F206E050
F206E051
F206E057

Analog event

0480

0...9999
0.0kV...999.9kV

U2 or U23 LV side change

F206E002
F206E003
F206E008
F206E009
F206E014
F206E015
F206E020
F206E021
F206E027
F206E034
F206E035
F206E040
F206E041
F206E046
F206E047
F206E052
F206E053
F206E059

Analog event

0481

0...9999
0.0kV...999.9kV

Description

Name

Values

1MRS 752015-MUM

Modbus

Remote Communication Protocol for REC 523

Technical Description

Description

Name

Type

Point
(hex)

U3 or U31 LV side change

F206E004
F206E005
F206E010
F206E011
F206E016
F206E017
F206E022
F206E023
F206E029
F206E036
F206E037
F206E042
F206E043
F206E048
F206E049
F206E054
F206E055
F206E061

Analog event

0482

Values
0...9999
0.0kV...999.9kV

Function block AR5Func, general parameters and events

Name

Type

Point
(hex)

Reset registers

F080V013

Coil

4501

1 - Reset

Status of LOCKOUT signal

F080O014

Digital input

4500

0 reset
1 activated

AR oper. status

F080S004

Digital input

4501

0...1
0 - OFF
1 - ON

Auto-reclosing sequence off

(stored)

successful (stored)

F080E016

Digital input

450A

CB opening failed via autorecloser (stored)

F080E026

Digital input

450B

CB closing failed via autorecloser (stored)

F080E027

Digital input

450C

CB closing inhibited (stored)

F080E028

Digital input

450D

LOCKOUT change

F080E044
F080E045

Digital event

4500

0 - reset
1 - activated

AR in use

F080E034
F080E035

Digital event

4501

0 - in use
1 - not in use

Auto-reclosing sequence
change

F080E000
F080E001

Digital event

4502

0 Ended
1 Started

Description

Values

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

successful

F080E016

Digital event

450A

1 - successful

CB opening failed via autorecloser

F080E026

Digital event

450B

1 - failed

CB closing failed via autorecloser

F080E027

Digital event

450C

1 - failed

CB closing inhibited

F080E028

Digital event

450D

1 inhibited

AR in progress

F080V001

Input register

4500

0...5
0 AR not in
progress;
1 AR shot 1 in
progress;
2 AR shot 2 in
progress;
3 AR shot 3 in
progress;
4 AR shot 4 in
progress;
5 AR shot 5 in
progress

Shot Pointer

F080V002

Input register

4501

1...7

AR operations

(stored)

F081E005

Digital input

4514

AR shot 1 successful (stored)

F081E006

Digital input

4515

Auto-reclose shot 1 change

F081E000
F081E001

Digital event

4510

0 - concluded
1 - in progress

AR shot 1 initiated via AR1

F081E002

Digital event

4511

1 - initiated

1MRS 752015-MUM

Modbus

Remote Communication Protocol for REC 523

Technical Description

Description

Name

Type

Point
Values
(hex)

AR shot 1 initiated via AR2

F081E003

Digital event

4512

1 - initiated

AR shot 1 initiated via AR3

F081E004

Digital event

4513

1 - initiated

AR shot 1 initiated via AR4

F081E005

Digital event

4514

1 - initiated

AR shot 1 successful

F081E006

Digital event

4515

4525

1 - successful

Description

Name

Digital event

4535

1 - successful

Description

Name

Values

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Digital event

4545

1 - successful

Description

Name

Values

Function block AR5Func, shot 5 events

Description

Name

Type

Point
(hex)

Auto-reclose shot 5 off

(stored)

F085E000
F085E001

Digital input

4550

0 - concluded
1 - in progress

AR shot 5 initiated via AR1

(stored)

F085E002

Digital input

4551

AR shot 5 initiated via AR2

(stored)

F085E003

Digital input

4552

AR shot 5 initiated via AR3

(stored)

F085E004

Digital input

4553

AR shot 5 initiated via AR4

(stored)

F085E005

Digital input

4554

AR shot 5 successful (stored) F085E006

4555

1 - successful

Values

Function block AR5Func, final trip events

Description

Name

F086E000

Digital event

4560

1 - trip

1MRS 752015-MUM

Modbus

Remote Communication Protocol for REC 523

Technical Description

Description

change

F051E008
F051E009

F041E006
F041E007

Digital event

1483

0 reset
1 activated

BS2 signal of Io > -> change

F041E008
F041E009

Digital event

1484

0 reset
1 activated

Values

F040I006

Digital input

1404

0 reset
1 activated

START signal from Io > ->

change

F040E000
F040E001

Digital event

1400

0 reset
1 - activated

TRIP signal from Io > ->

change

change

F036E012
F036E013

Digital event

1386

0 reset
1 activated

Values

1MRS 752015-MUM

Remote Communication Protocol for REC 523

Modbus

Technical Description

Function block DOC6LOW

Description

Name

Type

Point
(hex)

START signal from 3I > ->

stage

F035O002

Digital input

1300

0 reset
1 activated

TRIP signal from 3I > -> stage F035O003

Digital input

1301

0 reset
1 activated

CBFP signal from 3I > -> stage F035O004

Digital input

1302

0 reset
1 activated

stage change

F035E000
F035E001

Digital event

1300

0 reset
1 activated

TRIP signal from 3I > -> stage F035E002

change
F035E003

Digital event

1301

0 reset
1 activated

CBFP signal from 3I > -> stage F035E004

change
F035E005

Digital event

1302

0 reset
1 activated

DIR. signal from 3I > -> stage F035E006

change
F035E007

Digital event

1303

0 reset
1 activated

BS1 signal of 3I > -> stage

change

F035E008
F035E009

Digital event

1304

0 reset
1 activated

BS2 signal of 3I > -> stage

change

F035E010
F035E011

Digital event

1305

0 reset
1 activated

Type

Point
(hex)

START signal from Inrush3 stage F034O001

Digital input

1700

0 reset
1 activated

START signal from Inrush3 stage F034E000

change
F034E001

Digital event

1700

0 reset
1 activated

Values

F039I003

Digital input

1184

0 reset
1 activated

START signal from Io >> stage

change

F039E000
F039E001

Digital event

1180

0 reset
1 - activated

TRIP signal from Io >> stage

change

F039E002
F039E003

Digital event

1181

0 reset
1 activated

CBFP signal from Io >> stage

change

F039E004
F039E005

Digital event

1182

0 reset
1 activated

Values

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

Description

Name

Type

Point
(hex)

BS1 signal of Io >> stage

change

F039E006
F039E007

Digital event

1183

0 reset
1 activated

BS2 signal of Io >> stage

change

F039E008
F039E009

change

F038E008
F038E009

Digital event

1104

0 reset
1 activated

Type

Point
(hex)

Digital input

1083

0 reset
1 activated

BS1 signal of 3I >> stage

F032I004

Digital input

1084

0 reset
1 activated

BS2 signal of 3I >> stage

F032I005

Digital input

1085

0 reset
1 activated

change
F032E007

Digital event

1083

0 reset
1 activated

BS1 signal of 3I >> stage

change

Digital event

1084

0 reset
1 activated

Values

Function block NOC3HIGH

Description

Name

F032E008
F032E009

Values

1MRS 752015-MUM

Remote Communication Protocol for REC 523

Modbus

Technical Description

Description

Name

Type

Point
(hex)

BS2 signal of 3I >> stage

change

F031E007

Digital event

1003

0 reset
1 activated

BS2 signal of 3I > stage change F031E008

F031E009

Digital event

1004

0 reset
1 activated

Type

Point
(hex)

change

F065E002
F065E003

Digital event

1681

0 reset

BS1 signal of 3U<< stage

change

F065E004
F065E005

Digital event

1682

0 reset

BS2 signal of 3U<< stage

change

F065E006
F065E007

Digital event

1683

0 reset

Values

Function block UV3HIGH

Description

Name

Values

Function block UV3LOW

Description

Name

Type

Point
Values
(hex)

START signal from 3U< stage

F064O001

Digital input

1600

0 reset
1 activated

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

Description

Name

Type

Point
Values
(hex)

TRIP signal from 3U< stage

F064O002

Digital input

1601

0 reset
1 activated

BS1 signal of 3U< stage

F064I004

Digital input

1602

0 reset
1 activated

F064E005

Digital event

1602

0 reset
1 activated

BS2 signal of 3U< stage change F064E006

F064E007

Digital event

1603

0 reset
1 activated

Function block CO3DC1

Description

F139V021

Coil

2805

1 execute
1 select

status

F139O006

Digital input

2801

0 normal
1 alarm

Earthing time alarm of CO3DC1 F139O007

status

Digital input

2802

0 normal
1 alarm

Freeing time alarm of CO3DC1

status

1MRS 752015-MUM

Remote Communication Protocol for REC 523

Modbus

Technical Description

Type

Point
(hex)

F139E009

Digital event

2808

0 inactive
1 active

Command blocking of CO3DC1 F139E026

change
F139E027

Digital event

2809

0 deactivated
1 activated

Command status of CO3DC1

Digital event

280A

0 NACK
1 ACK

Position open/close of CO3DC1 F139V001

Input register

2800

0 middle
1 closed
2 open
3 faulty

Position earth/free of CO3DC1

F139V002

Input register

2801

0 middle
1 earth
2 free
3 faulty

Position open/close of CO3DC1 F139E000

change
F139E001
F139E002
F139E003

Analog event

2800

0 middle
1 closed
2 open
3 faulty

Position earth/free of CO3DC1

change

Analog event

2801

0 middle
1 earth
2 free
3 faulty

Description

Name

F139E024
F139E025

F139E038
F139E039
F139E040
F139E041

Values

Function block CO3DC2

Description

Coil

2889

1 execute

Alarm ACK of CO3DC2

F140V099

Coil

288A

1 ACK

Opening time alarm of

CO3DC2 status

F140O005

Digital input

2880

0 normal
1 alarm

Closing time alarm of CO3DC2 F140O006

status

Digital input

2881

0 normal
1 alarm

Earthing time alarm of

CO3DC2 status

Digital input

CO3DC2 change

F140E016
F140E017

Digital event

2880

0 normal
1 alarm

Closing time alarm of CO3DC2 F140E018

change
F140E019

Digital event

2881

0 normal
1 alarm

Earthing time alarm of

CO3DC2 change

F140E034
F140E035

Digital event

2882

0 normal
1 alarm

Freeing time alarm of CO3DC2 F140E036

change
F140E037

Digital event

2883

0 normal
1 alarm

Close interlocking of CO3DC2 F140E006

change
F140E007

Digital event

2884

0 disabled
1 enabled

change

F140E008
F140E009

Digital event

2888

0 inactive
1 active

Command blocking of
CO3DC2 change

F140E026
F140E027

Digital event

2889

0 deactivated
1 activated

Command status of CO3DC2

F140E024
F140E025

Digital event

288A

0 NACK
1 ACK

Position open/close of
CO3DC2

F140V001

Input register

2880

0 middle
1 closed
2 open
3 faulty

Position earth/free of CO3DC2 F140V002

Input register

2881

0 middle
1 earth
2 free
3 faulty

Position open/close of
CO3DC2 change

F140E000
F140E001
F140E002
F140E003

Analog event

2880

0 middle
1 closed
2 open
3 faulty

Position earth/free of CO3DC2 F140E038

change
F140E039
F140E040
F140E041

Analog event

2881

0 middle
1 earth
2 free
3 faulty

Description

Name

Values

1MRS 752015-MUM

Modbus

Remote Communication Protocol for REC 523

Technical Description

Function block COCB1

Description

F120E009

Digital event

2406

0 off
1 on

Control blocking of COCB1

change

F120E026
F120E027

Digital event

2407

0 deactivated
1 activated

Command status of COCB1

F120E024
F120E025

Digital event

2408

0 NACK
1 ACK

Position of COCB1

F120V001

Input register

2400

0 middle
1 closed
2 open
3 faulty

Position of COCB1 change

F120E000
F120E001
F120E002
F120E003

Analog event

2400

0 middle
1 closed
2 open
3 faulty

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

Function block COCB2

Description

F121E009

Digital event

2486

0 off
1 on

Control blocking of COCB2

change

F121E026
F121E027

Digital event

2487

0 deactivated
1 activated

Command status of COCB2

F121E024
F121E025

Digital event

2488

0 NACK
1 ACK

Position of COCB2

F121V001

Input register

2480

0 middle
1 closed
2 open
3 faulty

Position of COCB2 change

F121E000
F121E001
F121E002
F121E003

Analog event

2480

0 middle
1 closed
2 open
3 faulty

1MRS 752015-MUM

Modbus

Remote Communication Protocol for REC 523

Technical Description

Function block CODC1

Description

CODC1

F122O003

Digital input

2500

0 normal
1 alarm

Closing time alarm status of

CODC1

F122E009

Digital event

2504

0 off
1 on

Command blocking of CODC1 F122E026

change
F122E027

Digital event

2505

0 deactivated
1 activated

Command status of CODC1

F122E024
F122E025

Digital event

2506

0 NACK
1 ACK

Position of CODC1

F122V001

Input register

2500

0 middle
1 closed
2 open
3 faulty

Position of CODC1 change

F122E000
F122E001
F122E002
F122E003

Analog event

2500

0 middle
1 closed
2 open
3 faulty

Name

Type

F123V011

Coil

2585

1 execute
65

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description
Point
(hex)

Description

Name

Type

Values

Alarm ACK of CODC2

F123V099

Coil

2586

1 ACK

Opening time alarm status of

CODC2

F123O003

Digital input

2580

0 normal
1 alarm

Closing time alarm status of

CODC2

F123E009

F124V004

Coil

2600

1 execute

Direct close of CODC3

F124V005

Coil

2601

1 execute

Select open of CODC3

F124V006

CODC3

F124O003

Digital input

2600

0 normal
1 alarm

Closing time alarm status of

CODC3

F124O004

Digital input

2601

0 normal
1 alarm

Open command of CODC3

F124V031

Digital input

2602

0 enabled
1 interlocked

1MRS 752015-MUM

Modbus

Remote Communication Protocol for REC 523

Technical Description

F124E009

Digital event

2604

0 off
1 on

Command blocking of CODC3 F124E026

change
F124E027

Digital event

2605

0 deactivated
1 activated

Command status of CODC3

F124E024
F124E025

Digital event

2606

0 NACK
1 ACK

Position of CODC3

F124V001

Input register

2600

0 middle
1 closed
2 open
3 faulty

Position of CODC3 change

F124E000
F124E001
F124E002
F124E003

Analog event

2600

0 middle
1 closed
2 open
3 faulty

Name

Type

Point
(hex)

CODC4

F125O003

Digital input

2680

0 normal
1 alarm

Closing time alarm status of

CODC4

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

Type

Point
(hex)

F125E009

Digital event

2684

0 off
1 on

Command blocking of CODC4 F125E026

change
F125E027

Digital event

2685

0 deactivated
1 activated

Command status of CODC4

F125E024
F125E025

Digital event

2686

0 NACK
1 ACK

Position of CODC4

F125V001

Input register

2680

0 middle
1 closed
2 open
3 faulty

Position of CODC4 change

F125E000
F125E001
F125E002
F125E003

Analog event

2680

0 middle
1 closed
2 open
3 faulty

Description

Name

Values

Function block CODC5

Description

CODC5

F126O003

Digital input

2700

0 normal
1 alarm

Closing time alarm status of

CODC5

change

F126E016
F126E017

Digital event

2700

0 normal
1 alarm

Closing time alarm of CODC5

change

F126E018
F126E019

Digital event

2701

0 normal
1 alarm

Open command enable of

CODC5 change

F126E004
F126E005

Digital event

2702

0 enabled
1 interlocked

Close command enable of

CODC5 change

F126E006
F126E007

Digital event

2703

0 enabled
1 interlocked

1MRS 752015-MUM

Modbus

Remote Communication Protocol for REC 523

Technical Description

Description

Name

Type

Point
(hex)

Invalid state of CODC5 change

F126E008
F126E009

Digital event

2704

0 off
1 on

Command blocking of CODC5

change

F126E026
F126E027

Digital event

2705

0 deactivated
1 activated

Command status of CODC5

F126E024
F126E025

Digital event

2706

0 NACK
1 ACK

Position of CODC5

F126V001

Input register

2700

0 middle
1 closed
2 open
3 faulty

Position of CODC5 change

F126E000
F126E001
F126E002
F126E003

Analog event

2700

0 middle
1 closed
2 open
3 faulty

Description

Name

Type

Point
(hex)

Invalid state of COIND1

F127V034

Digital input

2000

0 off
1 on

Invalid state of COIND1 change

F127E008
F127E009

Digital event

2000

0 off
1 on

Position of COIND1

F127V001

Input register

2000

0 middle
1 closed
2 open
3 faulty

Position of COIND1 change

F127E000
F127E001
F127E002
F127E003

Analog event

2000

0 middle
1 closed
2 open
3 faulty

Values

Function block COIND1

Values

Function block COIND2

Description

Name

Type

Point
(hex)

Invalid state of COIND2

F128V034

Digital input

2080

0 off
1 on

Invalid state of COIND2

change

F128E008
F128E009

Digital event

2080

0 off
1 on

Position of COIND2

F128V001

Input register

2080

0 middle
1 closed
2 open
3 faulty

Position of COIND2 change

F128E000
F128E001
F128E002
F128E003

Analog event

2080

0 middle
1 closed
2 open
3 faulty

Description

Name

Type

Point
(hex)

Invalid state of COIND3

F129V034

Digital input

2100

0 off
1 on

Invalid state of COIND3 change F129E008

F129E009

Digital event

2100

0 off
1 on

Values

Function block COIND3

Values

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

Description

Name

Type

Point
(hex)

Position of COIND3

F129V001

Input register

2100

0 middle
1 closed
2 open
3 faulty

Position of COIND3 change

F129E000
F129E001
F129E002
F129E003

Analog event

2100

0 middle
1 closed
2 open
3 faulty

Description

Name

Type

Point
(hex)

Invalid state of COIND4

F130V034

Digital input

2180

0 off
1 on

Invalid state of COIND4

change

F130E008
F130E009

Digital event

2180

0 off
1 on

Position of COIND4

F130V001

Input register

2180

0 middle
1 closed
2 open
3 faulty

Position of COIND4 change

F130E000
F130E001
F130E002
F130E003

Analog event

2180

0 middle
1 closed
2 open
3 faulty

Description

Name

Type

Point
(hex)

Invalid state of COIND5

F131V034

Digital input

2200

0 off
1 on

Invalid state of COIND5 change F131E008

F131E009

Digital event

2200

0 off
1 on

Position of COIND5

F131V001

Input register

2200

0 middle
1 closed
2 open
3 faulty

Position of COIND5 change

F131E000
F131E001
F131E002
F131E003

Analog event

2200

0 middle
1 closed
2 open
3 faulty

Values

Function block COIND4

Values

Function block COIND5

Values

Function block COIND6

Description

Name

Type

Point
Values
(hex)

Invalid state of COIND6

F132V034

Digital input

2280

0 off
1 on

Invalid state of COIND6 change

F132E008
F132E009

Digital event

2280

0 off
1 on

Position of COIND6

F132V001

Input register

2280

0 middle
1 closed
2 open
3 faulty

1MRS 752015-MUM

Modbus

Remote Communication Protocol for REC 523

Technical Description

Description

Name

Type

Point
Values
(hex)

Position of COIND6 change

F132E000
F132E001
F132E002
F132E003

Analog event

2280

Description

Name

Type

Point
Values
(hex)

Invalid state of COIND7

F133V034

Digital input

2300

0 off
1 on

Invalid state of COIND7 change

F133E008
F133E009

Digital event

2300

0 off
1 on

Position of COIND7

F133V001

Input register

2300

0 middle
1 closed
2 open
3 faulty

Position of COIND7 change

F133E000
F133E001
F133E002
F133E003

Analog event

2300

0 middle
1 closed
2 open
3 faulty

Function block COIND7

Function block COIND8

Description

Name

Type

Point
(hex)

Invalid state of COIND8

F134V034

Digital input

2380

0 off
1 on

Invalid state of COIND8 change F134E008

F134E009

Digital event

2380

0 off
1 on

Position of COIND8

F134V001

Input register

2380

0 middle
1 closed
2 open
3 faulty

Position of COIND8 change

F134E000
F134E001
F134E002
F134E003

Analog event

2380

0 middle
1 closed
2 open
3 faulty

Values

Function block COLOCAT

Description

Name

Type

Point
(hex)

Logic position setting

F142V001

Digital input

2900

0 inactive
1 active

Logic position setting inactive/

active

F142E000
F142E001

Digital event

2900

0 inactive
1 active

Name

Type

Point
(hex)

Blocking automatic and manual F143I005

operations

Digital input

4600

0 - not active
1 - active

Day / night cos phi switch

Digital input

4601

0 - day target PF
1 - night target PF

Values

Function block COPFC

Description

F143I006

Values

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

Description

Name

Type

Point
(hex)

Disconnect capacitor banks

simultaneously

F143I007

Digital input

4602

0 - not active
1 - active

Reset

F143I008

Digital input

4603

0 - not active
1 - active

Duration demand time

REQ_UP

F143O001

Digital input

4604

0 - not active
1 - active

Duration demand time

REQ_DOWN

F143O002

Digital input

4605

0 - not active
1 - active

Control operation failure status F143O003

Digital input

4606

0 - not active
1 - active

(stored)

F143E006
F143E007

Digital input

460B

0 - reset
1 - activated

Testing finished, COPFC

(stored)

F143E006
F143E007

Digital event

460B

0 - reset
1 - activated

Testing finished, COPFC

F143E010
F143E011

Digital event

460C

0 - OK
1 - failed

Overvoltage inhibition, COPFC F143E012

F143E013

Digital event

460D

0 - reset
1 - activated

Values

P3 (kW)

F143I001

Input register

4600

-999999...999999

Q3 (kvar)

F143I002

Input register

4601

-999999...999999

Power factor DPF

F143I003

Input register

4602

0.00...1.00

Connected banks

F143I004

Input register

4603

0...65535

Number of switching operations F143V011

per day

Input register

4604

0...65535

Operation mode

F143V001

Holding register

4600

0 - Not in use
1 - Automatic mode
2 - Manual mode
3 - Testing mode

Giving switching commands in F143V006

the manual mode

Holding register

4601

0 - Not activated
1 - Remove one step
2 - Add one step
3 - Disconnect all

1MRS 752015-MUM

Remote Communication Protocol for REC 523

Modbus

Technical Description

Accumulated breaker 1 wear at F187V001

pole 1

Holding register

3300

0...10000

Accumulated breaker 1 wear at F187V002

pole 2

Holding register

3301

0...10000

Accumulated breaker 1 wear at F187V003

pole 3

Holding register

3302

0...10000

Point
(hex)

Values

Function block CMBWEAR2

Description

Name

Type

CMBWEAR2 alarm ACK

F188V099

Coil

3380

1 ACK

CMBWEAR2 alarm state

F188O001

Digital input

3380

0 normal
1 alarm

Breaker 2 electric wear alarm

change

F181E001

Digital event

3000

0 normal
1 alarm

Point
Values
(hex)

Function block CMGAS1

Description

Name

Type

CMGAS1 alarm ACK

F186V099

Coil

3200

1 ACK

Low gas density alarm state

F186O001

Digital input

3200

0 normal
1 alarm

Gas pressure

F186I001

Digital input

3201

0 invalid
1 valid

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

Description

Name

Type

Point
Values
(hex)

Low gas density alarm change

F186E000
F186E001

Digital event

3200

0 normal
1 alarm

Low gas density warning change F186E002

F186E003

Digital event

3201

0 invalid
1 valid

Function block CMGAS3

Description

Name

Type

Point
(hex)

Values

Alarm ACK

F194V099

Coil

0800

1 - ACK

Low gas pressure alarm

F194O001

Digital input

4800

0 - inactive
1 - active

Gas pressure L1

F194I001

Digital input

4801

0 - invalid
1 - valid

Gas pressure L2

F194I002

Digital input

4802

0 - invalid
1 - valid

Gas pressure L3

F194I003

Digital input

4803

0 - invalid
1 - valid

state

F189O001

Digital input

3400

0 normal
1 alarm

Scheduled maintenance alarm

change

F189E000
F189E001

Digital event

3400

0 normal
1 alarm

Type

Point
(hex)

Function block CMSPRC1

Description

Name

Values

Alarm ACK

F190V099

Coil

3600

1 ACK

Spring 1 max. charging alarm

state

F190O002

Digital input

3600

0 inactive
1 active

Spring 1 min. charging alarm

state

F190O003

Digital input

3601

0 inactive
1 active

Spring 1 charge status

F190I002

Digital input

3602

0 uncharged
1 charged

Spring 1 max. charging alarm

change

F190E002
F190E003

Digital event

3600

0 inactive
1 active

Spring 1 min. charging alarm

change

F190E004
F190E005

Digital event

3601

0 inactive
1 active

Spring 1 uncharged/charged

F190E008
F190E009

Digital event

3602

0 uncharged
1 charged

1MRS 752015-MUM

Remote Communication Protocol for REC 523

Modbus

Technical Description

Function block CMTIME1

Description

Name

Time 1 alarm ACK

F184V099

Type

Point
(hex)

Values

Coil

3500

1 ACK

Accumulated time 1 alarm state F184O001

Digital input

3500

0 reset
1 activated

Accumulated time 1
measurement state

F184I001

Digital input

3501

0 inactive
1 active

Accumulated time 1 alarm

change

F184E000
F184E001

Digital event

3500

0 reset
1 activated

Accumulated time 1
measurement change

Accumulated time 2
measurement change

F185E002
F185E003

Digital event

3581

0 inactive
1 active

Function block CMTRAV1

Description

Name

Type

Point
Values
(hex)

Alarm ACK

F193V099

Coil

3800

1 ACK

Breaker 1 open travel alarm

F193O001

Digital input

3800

0 inactive
1 active

Breaker 1 close travel alarm

F193O002

Digital input

3801

0 inactive
1 active

Breaker 1 open travel alarm

deactivated

F193E000
F193E001

Digital event

3800

0 inactive
1 active

Breaker 1 close travel alarm

deactivated

F193E002
F193E003

Digital event

3801

0 inactive
1 active

Description

Name

Type

Point
Values
(hex)

Input voltage circuit alarm

F182O001

Digital input

3100

0 normal
1 alarm

Input voltage circuit alarm off/on F182E000

F182E001

Digital event

3100

0 normal
1 alarm

Function block CMVO3

Function block PQCU3H

Description

Name

Type

Point
Values
(hex)

Reset registers

F512V025

Coil

4900

1 - Reset

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

Description

Name

Type

Point
Values
(hex)

Status of output HAR_HIGH

value

F512I002

Input register

4900

0...10000
0.0...1000.0%

Fundamental component 3s
value

value

F512I024

Input register

4914

0...10000
0.0...1000.0%

1MRS 752015-MUM

Modbus

Remote Communication Protocol for REC 523

Technical Description

Description

Name

Type

Point
Values
(hex)

8th harmonic short time sliding

value

F512I025

Input register

4915

0...10000
0.0...1000.0%

9th harmonic short time sliding

value

F512V306

Input register

491C

0...10000
0.0...1000.0%

THD

F512V404

Input register

491D

0...10000
0.0...1000.0%

Name

Type

Point
Values
(hex)

Function block PQVO3H

Description
Reset registers

F513V024

Coil

4A00

1 Reset

Status of output HAR_HIGH

value

F513I002

Input register

4A00

0...1200
0.0...120.0 %

Fundamental component 3s
value

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

F513V206

Input register

4A1B

0...1200
0.0...120.0 %

Max THD at active obs. period

F513V306

Input register

4A1C

0...1200
0.0...120.0 %

THD

F513V404

Input register

4A1D

0...1200
0.0...120.0 %

Description

Name

Type

Point
Values
(hex)

BIO binary input 1 state

F013I001

Digital input

4300

0 reset
1 activated

BIO binary input 2 state

F013I002

Digital input

4301

0 reset
1 activated

BIO binary input 3 state

F013I003

Digital input

4302

0 reset
1 activated

Function block BIO

1MRS 752015-MUM

Remote Communication Protocol for REC 523

Modbus

Technical Description

activated

F013E000
F013E001

Digital event

4300

0 reset
1 activated

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

start/stop

F013E054
F013E055

Digital event

431B

0 stop
1 start

BIO binary input 11 oscillate

start/stop

F013E056
F013E057

Digital event

431C

0 stop
1 start

1MRS 752015-MUM

Modbus

Remote Communication Protocol for REC 523

Technical Description

Description

Name

Type

Point
Values
(hex)

BIO binary input 12 oscillate

start/stop

F013E058
F013E059

Digital event

431D

Type

Point
Values
(hex)

0 stop
1 start

CH000, CH001 and CH002

Description

Name

Reset device

F000V250

Coil

0001

1 reset

Reset indication

F001V011

Coil

0002

1 reset

Reset outputs

F001V012

Coil

0003

1 reset

Reset registers

change

F002E004
F002E005

Digital event

0002

0 inactive
1 active

Module startup

F000E050

Digital event

0003

1 startup

Event buffer overflow

F000E051

Digital event

0004

1 overflow

Recent control position

F002V005

Input register

0001

0 disable
1 local
2 remote

Store

F000V151

Holding register

0008

0 - store completed
1 - store in progress
2 - error
160 - fast store in
progress

Recent control position change

F002E000
F002E001
F002E002

Analog event

0001

0 disable
1 local
2 remote

Description

Name

Type

Point
(hex)

PSC binary output 1 off/on

status

F017O001

Digital input

4200

0 reset
1 activated

PSC binary output 2 off/on

status

F017O002

Digital input

4201

0 reset
1 activated

PSC binary output 3 off/on

status

F017O003

Digital input

4202

0 reset
1 activated

PSC binary input 1 off/on status F017I001

Digital input

4203

0 reset
1 activated

PSC binary input 2 off/on status F017I002

Digital input

4204

0 reset
1 activated

PSC binary input 3 off/on status F017I003

Digital input

4205

0 reset
1 activated

PSC AC status

F017I004

Digital input

4206

0 OK
1 fail

PSC overheat status

F017I005

Digital input

4207

0 OK
1 overheated

Function block PSC1

Values

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

Description

Name

Type

Point
(hex)

PSC battery status

F017I006

Digital input

4208

0 good
1 low

F017E006
F017E007

Digital event

4206

0 OK
1 fail

PSC overheat temperature

reset/activated

F017E008
F017E009

Digital event

4207

0 OK
1 overheated

PSC battery voltage good/low

F017E022
F017E023

Digital event

4208

0 good
1 low

F017I007

Input register

4200

- 40...70
- 40C...+70C*

PSC battery voltage updated

F017I008

Input register

4201

180...330
18.0Vdc...33.0Vdc

PSC battery voltage reset

F017I011

Holding register

4200

180...330
18.0Vdc...33.0Vdc

PSC temperature change

F017E026

Analog event

4200

-40..70
-40C..+70C*

PSC battery voltage change

F017E027

Analog event

4201

180..330
18.0Vdc..33.0Vdc

Values

* Modbus register values are normally unsigned but will in this case be interpreted
as signed in U2 format.

SWITCH groups

Description

Name

Type

Point
(hex)

Values

Actual settings of SWGRP1

F030S001

Input register

4D01

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

Description

F030S059

Holding register

4D38

0...255

1MRS 752015-MUM

Modbus

Remote Communication Protocol for REC 523

Technical Description

Description

COMM OUT33

F025O017

Coil

4B10#

0...1

COMM OUT34

F025O018

Coil

4B11#

0...1

COMM OUT35

F025O019

Coil

4B12

0...1

COMM OUT36

F025O020

Coil

4B13

0...1

COMM OUT37

F025O021

Coil

4B14

0...1

COMM OUT38

F025O022

Coil

4B15

0...1

COMM OUT39

F025O023

Coil

4B16

0...1

COMM OUT40

F025O024

Coil

4B17

0...1

COMM OUT41

F025O025

Coil

4B18

0...1

COMM OUT42

F025O026

Coil

4B19

0...1

COMM OUT43

F025O027

Coil

4B1A

0...1

COMM OUT44

F025O028

Coil

4B1B

0...1

COMM OUT45

F025O029

Coil

4B1C#

0...1

COMM OUT46

F025O030

Coil

4B1D

0...1

COMM OUT47

F025O031

Coil

4B1E#

0...1

COMM OUT48

F025O032

Coil

4B1F

0...1

COMM IN33

F025I017

Digital input

4B10*

0...1

COMM IN34

F025I018

Digital input

4B11

0...1

COMM IN35

F025I019

Digital input

4B12*

0...1

COMM IN36

F025I020

Digital input

4B13

0...1

COMM IN37

F025I021

Digital input

4B14*

0...1

COMM IN38

F025I022

Digital input

4B15*

0...1

COMM IN39

F025I023

Digital input

4B16

0...1

COMM IN40

F025I024

Digital input

4B17

0...1

COMM IN41

F025I025

Digital input

4B18

0...1

COMM IN42

F025I026

Digital input

4B19*

0...1

COMM IN43

F025I027

Digital input

4B1A

0...1

COMM IN44

F025I028

Digital input

4B1B*

0...1

COMM IN45

F025I029

Digital input

4B1C*

0...1

COMM IN46

F025I030

Digital input

4B1D*

0...1

COMM IN47

F025I031

Digital input

4B1E

0...1

COMM IN48

F025I032

Digital input

4B1F*

0...1

COMM IN33 change

F025I032

Digital event

4B1F*$ 0...1

COMM IN1

F025I001

Input register

4B00

0...65535

COMM IN2

F025I002

Input register

4B01

0...65535

COMM IN3

F025I003

Input register

4B02

0...65535

COMM IN4

F025I004

Input register

4B03

0...65535

COMM IN5

F025I005

Input register

4B04

0...65535

COMM IN6

F025I006

Input register

4B05

0...65535

COMM IN7

F025I007

Input register

4B06

0...65535

COMM IN8

F025I008

Input register

4B07

0...65535

COMM IN9

F025I009

Input register

4B08

0...65535

COMM IN10

F025I010

Input register

4B09

0...65535

COMM IN11

F025I011

Input register

4B0A

0...65535

COMM IN12

F025I012

Input register

4B0B

0...65535

COMM IN13

F025I013

Input register

4B0C

0...65535

COMM IN14

F025I014

Input register

4B0D

0...65535

COMM IN15

F025I015

Input register

4B0E

0...65535

COMM IN16

F025I016

Input register

4B0F

0...65535

COMM OUT1

F025O001

Holding register

4B00

0...65535

COMM OUT2

F025O002

Holding register

4B01

0...65535

COMM OUT3

F025O003

Holding register

4B02

0...65535

COMM OUT4

F025O004

Holding register

4B03

0...65535

COMM OUT5

F025O005

Holding register

4B04

0...65535

COMM OUT6

F025O006

Holding register

4B05

0...65535

COMM OUT7

F025O007

Holding register

4B06

0...65535

COMM OUT8

F025O008

Holding register

4B07

0...65535

COMM OUT9

F025O009

Holding register

4B08

0...65535

COMM OUT10

F025O010

Holding register

4B09

0...65535

COMM OUT11

F025O011

Holding register

4B0A

0...65535

COMM OUT12

F025O012

Holding register

4B0B

0...65535

COMM OUT13

F025O013

Holding register

4B0C

0...65535

COMM OUT14

F025O014

Holding register

4B0D

0...65535

COMM OUT15

F025O015

Holding register

4B0E

0...65535

COMM OUT16

F025O016

Holding register

4B0F

0...65535

COMM IN1 change

F025I001

Analog event

COMM IN2 change

F025I002

Analog event

COMM IN3 change

F025I003

Analog event

COMM IN4 change

F025I004

Analog event

4B00

0...65535

4B01

0...65535

4B02

0...65535

4B03

0...65535

1MRS 752015-MUM

Modbus

Remote Communication Protocol for REC 523

Technical Description

Description

F025I014

Analog event

4B0D$

0...65535

COMM IN15 change

F025I015

Analog event

0...65535

COMM IN16 change

F025I016

Analog event

0...65535

4B0E
4B0F

# Output NVs interpreted as boolean type are implemented as points of coil type
(xxxx). If a change of their interpretation to enum type is required, they should
be implemented as holding registers (xxxx).
* Events associated with input NVs interpreted as boolean type are implemented as
points of digital event type (xxxx). If a change of the interpretation of these NVs
to enum type is required, they should be implemented as analogue events
(0005xxxx). Input NVs interpreted as boolean type are implemented as points of
digital input type (xxxx). If it is required to change their interpretation to enum
type, they should be implemented as input registers (xxxx).
$ Events associated with LON input NVs have time stamps set to not used.

RECCH026 (LON virtual inputs and outputs)

Description

Name

Type

Point
(hex)

Values

COMM OUT49

F026O017

Coil

0C10

0...1

COMM OUT50

F026O018

Coil

0C11

0...1

COMM OUT51

F026O019

Coil

0C12#

0...1

COMM OUT52

F026O020

Coil

0C13

0...1

COMM OUT53

F026O021

Coil

0C14#

0...1

COMM OUT54

F026O022

Coil

0C15#

0...1

COMM OUT55

F026O023

Coil

0C16#

0...1

COMM OUT56

F026O024

Coil

0C17

0...1

COMM OUT57

F026O025

Coil

0C18

0...1

COMM OUT58

F026O026

Coil

0C19

0...1

COMM OUT59

F026O027

Coil

0C1A

0...1

COMM OUT60

F026O028

Coil

0C1B

0...1

COMM OUT61

F026O029

Coil

0C1C

0...1

COMM OUT62

F026O030

Coil

0C1D

0...1

COMM OUT63

F026O031

Coil

0C1E

0...1

COMM OUT64

F026O032

Coil

0C1F#

0...1

COMM IN49

F026I017

Digital input

4C10

0...1

COMM IN50

F026I018

Digital input

4C11*

0...1

COMM IN51

F026I019

Digital input

4C12*

0...1

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

Description

Name

Type

Point
(hex)

Values

COMM IN52

F026I020

Digital input

4C13*

0...1

COMM IN53

F026I021

Digital input

4C14

0...1

COMM IN54

F026I022

Digital input

4C15

0...1

COMM IN55

F026I023

Digital input

4C16*

0...1

COMM IN56

F026I024

Digital input

4C17

0...1

COMM IN57

F026I025

Digital input

4C18*

0...1

COMM IN58

F026I026

Digital input

4C19

0...1

COMM IN59

F026I027

Digital input

4C1A*

0...1

COMM IN60

F026I028

Digital input

4C1B

0...1

COMM IN61

F026I029

Digital input

4C1C*

0...1

COMM IN62

F026I030

Digital input

0...1

COMM IN63

F026I031

Digital input

0...1

COMM IN64

F026I032

Digital input

0...1

COMM IN49 change

F026I017

Digital event

0...1

F026I027

Digital event

0...1

COMM IN60 change

F026I028

Digital event

4C1B

0...1

COMM IN61 change

F026I029

Digital event

4C1C*$ 0...1

COMM IN62 change

F026I030

Digital event

4C1D*$ 0...1

COMM IN63 change

F026I031

Digital event

4C1E*$

0...1

COMM IN64 change

F026I032

Digital event

4C1F*$

0...1

COMM IN17

F026I001

Input register

4C00

0...65535

COMM IN18

F026I002

Input register

4C01

0...65535

COMM IN19

F026I003

Input register

4C02

0...65535

COMM IN20

F026I004

Input register

4C03

0...65535

COMM IN21

F026I005

Input register

4C04

0...65535

COMM IN22

F026I006

Input register

4C05

0...65535

COMM IN23

F026I007

Input register

4C06

0...65535

COMM IN24

F026I008

Input register

4C07

0...65535

COMM IN25

F026I009

Input register

4C08

0...65535

COMM IN26

F026I010

Input register

4C09

0...65535

COMM IN27

F026I011

Input register

4C0A

0...65535

COMM IN28

F026I012

Input register

4C0B

0...65535

COMM IN29

F026I013

Input register

4C0C

0...65535

COMM IN30

F026I014

Input register

4C0D

0...65535

COMM IN31

F026I015

Input register

4C0E

0...65535

COMM IN32

F026I016

Input register

4C0F

0...65535

COMM OUT17

F026O001

Holding register

4C00

0...65535

COMM OUT18

F026O002

Holding register

4C01

0...65535

4C1D
4C1E
4C1F
4C10
4C11

4C1A

1MRS 752015-MUM

Modbus

Remote Communication Protocol for REC 523

Technical Description

Description

Name

Type

Point
(hex)

Values

COMM OUT19

F026O003

Holding register

4C02

0...65535

COMM OUT20

F026O004

Holding register

4C03

0...65535

COMM OUT21

F026O005

Holding register

4C04

0...65535

COMM OUT22

F026O006

Holding register

4C05

0...65535

COMM OUT23

F026O007

Holding register

4C06

0...65535

COMM OUT24

F026O008

Holding register

4C07

0...65535

COMM OUT25

F026O009

Holding register

4C08

0...65535

COMM OUT26

F026O010

Holding register

4C09

0...65535

COMM OUT27

F026O011

Holding register

4C0A

0...65535

COMM OUT28

F026O012

Holding register

4C0B

0...65535

COMM OUT29

F026O013

Holding register

4C0C

0...65535

COMM OUT30

F026O014

Holding register

4C0D

0...65535

COMM OUT31

F026O015

Holding register

4C0E

0...65535

COMM OUT32

F026O016

Holding register

4C0F

0...65535

COMM IN17 change

F026I001

Analog event

COMM IN18 change

F026I002

COMM IN19 change

F026I003

COMM IN20 change

COMM IN21 change

4C00

0...65535

Analog event

4C01

0...65535

Analog event

4C02$

0...65535

F026I004

Analog event

4C03$

0...65535

F026I015

Analog event

0...65535

COMM IN32 change

F026I016

Analog event

0...65535

4C0E
4C0F

# Output NVs interpreted as boolean type are implemented as points of coil type
(xxxx). If a change of their interpretation to enum type is required, they should
be implemented as holding registers (xxxx).
$ Events associated with LON input NVs have time stamps set to not used.
* Events associated with input NVs interpreted as boolean type are implemented as
points of digital event type (xxxx). If a change of their interpretation to enum
type is required, they should be implemented as analogue events (0005xxxx).
Input NVs interpreted as boolean type are implemented as points of digital input
type (xxxx). If a change of their interpretation to enum type is required , they
should be implemented as input registers (xxxx).

Link handler
Description

Name

Type

Point
(hex)

Remote protocol CTS usage

F500V217

Coil

4000

0 not used
1 - in use

Remote protocol RTS usage

F500V218

Coil

4001

0 not used
1 - in use

Values

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

Description

Name

Type

Point
(hex)

Remote protocol connection

mode

timeout

F500V216

Holding register

4005

0 not in use
1...10000
1ms...10000ms

Remote protocol parity

F500V230

Holding register

4006

0...2
0 no parity
1 odd parity
2 even parity

Remote protocol data bits

F500V231

Holding register

4007

5...8

Values

Note: Modem strings are not mapped in the Modbus interface. A reconfiguration
requires the usage of the SPA or the LON interface.
Modbus Protocol data

Description

Name

Type

Point
(hex)

Values

Station address

F504V001

Holding register

4100

1...247

CRC order

F504V002

Coil

4100

0 LO/HI
1 HI/LO

Mode

F504V003

Coil

4101

0 ASCII
1 RTU

Event reporting mode

F504V004

Holding register

4101

0 no events
1 SACE method with
short time stamp
2 SACE method with
full time stamp
3 MicroSCADA
4 MicroSCADA
method with full time
stamp
5 Modicon method
with short time stamp
6 Modicon method
with full time stamp
other reserved

Dial timeout

F504V005

Holding register

4102

0 not in use
1...65535 seconds

Channel idle watchdog timeout

F504V006

Holding register

4103

0 not in use
1...65535 seconds

1MRS 752015-MUM

Modbus

Remote Communication Protocol for REC 523

Technical Description

Modbus queues
Description

Name

Type

Point
(hex)

Event queue control coil

EQCTRLCO

Name

0...999

Values

Time synchronization
Point
(hex)

Values

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

3.3.

Protocol software version

SW_vers

Fig. 3.3.-1 Software version

Name

Description of coding scheme

Software build

A system software version (for example 3.55), followed by a letter

indicating that a certain remote protocol has been included (for
example M for Modbus protocol), and the remote protocol version (for
example 10 for the initial version 1.0)
Software revision A revision letter (for example D)
Software version The number of the CPU card delivered with the Modbus protocol
CPU card number The serial number of the CPU card

3.4.

Interface configuration
This section describes the communication parameters required to configure
REC 523 in order to be able to communicate using the Modbus protocol over a given
link.
These parameters can be uploaded, reviewed and modified using the Relay Setting
Tool from the CAP 501/505 package by choosing the Communication library and
the General, Link Handler or the Modbus pages.

3.4.1.

Communication start-up procedure

Before the start-up of the Modbus based communication with REC 523, the
parameters of the link and the protocol should be verified using the Relay Setting
Tool from the CAP 501/505 package. To properly configure the interface of
REC 523, it is necessary to know the setup of the master and the characteristics of

1MRS 752015-MUM

Remote Communication Protocol for REC 523

Modbus

Technical Description

the utilized communication channel. At the end of the configuration process, the tool
should enforce storing of updated parameters in the non-volatile memory and reset
the REC 523 unit to activate new parameters. In some cases it may also be required
to modify the application mapping in the POD table using the Protocol Editing Tool.

3.4.2.

Port assignment
There are three communication ports in REC 523: two RS 232 and one RS 485. The
Modbus can be assigned to each one of them (but only one at the time). The port
assignment to the protocol can be done by choosing the Communication library and
the General pages in the Relay Setting Tool. The default values for REC 523 ports
are as follows:
Port X5.1

Modbus

Port X5.2

None

Port X5.3

LON

In Relay Setting Tool, parameter Protocol1 refers to REC 523 port X5.1,
Protocol2 to port X5.2, and Protocol 3 to port X5.3.

general

Fig. 3.4.2.-1

General pages

Note that the port assignments for protocols are revision dependent. This product
supports only the following protocols: Modbus, SPA and LON. Refer to the
Technical Reference Manual for a revision history.

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

3.4.3.

Link parameters
The link parameters of REC 523 can be accessed by choosing the Communication
library and the Link Handler pages in the Relay Setting Tool.
Group description

Object
name

Transmission settings

Description

Notes

F500V220

Connection mode
0 fixed line
1 dial-up

F500V211

Communication
speed (in bps)

0 - in case of a fixed line or

leased line connection (with
preconfigured modems)
1 in case of a dial-up
connection (modem
controlled by REC 523)
The same configuration as in
the master (fixed line) or in
the modem (dial-up).

F500V212

F500V230

F500V231
Timeout settings
(frame transmission
delays)

F500V215

F500V216

Handshaking settings
F500V217
(connection to the DCE)

F500V218

F500V219

F500V213
F500V214

Baud rate
The number of stop
bits

The same configuration as in

the master (fixed line) or in
the modem (dial-up).
Parity
The same configuration as in
0 no parity
the master (normally even
1 odd parity
parity for the RTU mode and
2 even parity
odd parity for the ASCII
(standard)
mode, however, some
modems require no parity).
The number of data 7 The ASCII mode
bits
8 The RTU mode
The next character Can be tuned according to
timeout (in ms): the the link characteristics.
maximum allowed
According to the RTU mode
time gap between
in the Modbus protocol, the
received characters next character timeout is 1.5 x
of the same frame; 0 character time.
not in use.
The end of the frame Must be tuned according to
timeout (in ms): the the link characteristics.
minimum idle time
Recommended minimum in
following the frame the ASCII mode: longer than
transmission to REC the character transmission
523
time. In the RTU mode 3.5 x
character time.
CTS usage
In use if required by the DCE
0 not used
(modem in the half duplex
1 in use
mode) and supported by the
connection cable.
RTS usage
In use if required by the DCE
0 not used
(modem in the half duplex
1 in use
mode) and supported by the
connection cable.
DCD usage
Not used not supported by
0 not used
REC 523 hardware.
1 in use
CTS delay value (in In REC 523 controlled by
ms)
hardware, set to 0.
RTS delay value (in In REC 523 controlled by
ms)
hardware, set to 0.

1MRS 752015-MUM

Remote Communication Protocol for REC 523

Modbus

Technical Description
Group description
(Continued)

Object
name

Modem settings
F500V221
(for use only in the dialup connection mode)
F500V222

Modem settings
F500V223
(for use only in the dialup connection mode)

F500V224

F500V225

Description

Notes

1MRS 752015-MUM

Technical Description
Group description
(Continued)

Object
name
F500V226

F500V227

F500V228

F500V229

Description

modem (refer to the modem
manual).
Set to NOTUSED if not in
use.

1MRS 752015-MUM

Remote Communication Protocol for REC 523

Modbus

Technical Description

Linkhandler1

Fig. 3.4.3.-1

3.4.4.

Link Handler

Protocol parameters
The protocol parameters of REC 523 can be accessed by choosing the
Communication library and the Modbus pages in the Relay Setting Tool.
Object
name

Description

F504V001 Unit address

1...247
F504V002 CRC order
F504V003 Mode
F504V004 Event reporting mode

Notes
The same configuration as in the master.
Irrelevant in the ASCI mode. In the RTU mode
the same configuration as in the master.
The same configuration as in the master.
Apply the same method as used by the master.

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description
Object
name

Description

F504V005 Dial timeout

F504V006 Channel idle watchdog

timeout

Notes
Can be set to 0 when fixed line configuration is
used. In the dial-up environment this timeout is
activated after the event has been received. After
the timeout has expired, the channel will be
openedto indicate that the event buffers are not
empty.
The time in seconds after which the protocol will
close the communication channel if there is no
communication with the controlling device.
0 not used

Note: The event mask 1 in the function block parameters should be used to select
events to be reported via the Modbus protocol.

MBparams

Fig. 3.4.4.-1

3.4.4.1.

Relay Setting Tool with Modbus parameters

Recommendations for parameter tuning due to specific medium

or link characteristics
Fixed line (RS-232) 1 to 1 or bus topology connection:
In this case there is no need to set the dial timeout. The fixed line connection mode
is used. It is irrelevant to set the modem parameters. The rest of the parameters must
match the masters configuration.

1MRS 752015-MUM

Remote Communication Protocol for REC 523

Modbus

Technical Description

Fixed line (modem) 1 to 1 or bus topology connection:

For communication over a leased line the connection mode needs to be set to fixed
line. The utilized modem must be set up using the terminal program. For this type of
communication the end of the frame timeout needs to be set according to the channel
characteristics.
Dial up connection requesting a connection to the master not allowed:
In this case only the master can initiate the connection (that is, dial the number). The
dial timeout should be set to 0.
Dial up connection requesting a connection to the master station allowed:
In this case unsolicited reporting can be switched on. The reconnection timeout can
be used to choose the time after which REC 523 will try to connect after it has
received an event.
Note: For communication in the dial-up connection mode the utilized modem is
configured by REC 523. E0 command should be included in the modem
initialization string to prevent sending an echo of the received commands. The
modem initialization string must not include any command that establishes a
connection with the remote modem. For this purpose only the dialing string should
be used.

3.4.4.2.

Communication in the dial-up environment

Establishing a modem connection through the PSN (Public Switched Network)
requires the use of string parameters. There can be a maximum of one default and
four spare dialing strings. The dialing string contains the phone number of the
designated master (with mandatory ATD prefix). The REC 523 unit will open the
channel only if communication with the designated master is necessary and the
channel has been closed. If the default master can not answer the call, the spare
dialing numbers will be used. If all attempts to connect fail, the emergency number
will be dialed and REC 523 will hung up immediately after a connection has been
established. This number can be the operators GSM number, for instance. This
feature allows informing the operator that all attempts to connect to all configured
numbers have failed and that the system therefore has to be reconfigured. After this
REC 523 will only accept incoming calls. The dialing feature of the Modbus
interface will be reactivated only after REC 523 has been reset.
To configure REC 523 so that the dial-up connection can be used, the following
parameters must be set:
The parameter Connection mode must be set to dial-up
The parameter Modem init str must be set to parameterize the modem
(according to the manual of the used modem)
The use of the GSM modem requires that also the GSM PIN code parameter be
set accordingly
Each modem operation is started by hanging-up any active connection. This
includes also the procedure of establishing the connection between the REC 523 and
SCADA system.

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

The modem configuration/initialization will be done every time the link

initialization is performed (this does not apply to entering the GSM modem PINcode).
The use of the GSM modem requires two levels of modem initialization:
Hard initialization after the device start-up - this includes the entering of the PINcode and common modem configuration
Soft initialization that includes only modem reconfiguration
To be able to establish a connection to the master at least the Modem dial str needs
to be set to dial the masters number (note that this string must include the ATD
prefix).
The communication channel will be opened only at the request of the protocol
software. The algorithm of this operation assumes a predefined number of six
attempts made at random and increasing intervals (the intervals are presented
below). It is possible to define more than one telephone number of the SCADA
system by using separate dialing strings as link handler parameters (one primary
number, up to four spare numbers). During each attempt to establish a connection
all configured dialing numbers on the list will be used (without delays).
It is also possible to define an emergency number to be used only when no
connection to any of the configured numbers (primary and spare numbers) can be
established. The emergency number can be the number of the operator, for instance.
The idea of using this number is to inform the operator about traffic problems in the
telephone switching network. No action is expected from the operator after it has
received such a call after a connection has been established, the link will notify the
protocol about the channel error. As a result of this, the protocol will initialize the
link (and hang up the connection) and wait for the master to connect (that is, it will
not try to open the channel by itself).
The detailed behavior of the dialing algorithm is shown below:

100

1MRS 752015-MUM

Remote Communication Protocol for REC 523

Modbus

Technical Description

Request to open channel

Attempt:=1

Dial primary number

Communicate with
master station

YES

Connection succesful?

NO
Is next spare number
configured?

YES

Dial next available

spare number

NO
Attempt:=Attempt+1

All 6 attempts to connect to

configured numbers
executed?

Case Attempt of:

2: wait 0...60 seconds
3: wait 1...4 minutes
4: wait 4...19 minutes
5: wait 19...34 minutes
6: wait 34...64 minutes

YES

Disconnect,
initialize modem
and wait for master
to connect

dial

Dial emergency
number (if in use)

When the master dials the number of the REC 523 unit and successfully manages to
connect between the dialing attempts made by REC 523, the same procedure will be
followed as though REC 523 would successfully connect.
REC 523 is responsible for closing the communication channel when there is no
communication with the master for a predefined time (no valid frame is received,
including also the frames addressed to other units). A watchdog function supervising
the incoming valid frames has been added to the protocol software. The watchdog
timeout is defined by the configurable parameter Watchdog TO in the protocol
parameter group.

3.4.4.3.

Application mapping review

In most of the system configurations the application mapping defined by the default
POD should be acceptable. However, a modification of the visible POD table is
necessary in the following cases:

101

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

When a different addressing concept is used in the system because of the masters
requirements or limitations in the protocol data addressing (that is, the mapped
application objects are readdressed)
To eliminate obsolete data and events from active function blocks (data items not
required or not processed by the master station)
The visible POD table can be uploaded, reviewed, and modified using the dedicated
Protocol Editing Tool. In the default POD the mapped function blocks occupy the
assigned ranges of addresses. Therefore, for a downloaded application the overall
addressing of the data will not be continuous. Some masters, however, may accept
only a continuous address map. In this case the addresses of the data items will have
to be changed.
A detailed description of the contents of the visible POD and examples of mapping
are given in section 3.1.3.
After the contents of the visible POD have been changed, the table can be
downloaded to REC 523. After this the tool enforces storing of the data in the nonvolatile memory followed by the device reset. The updated table will be used to
generate the operational POD.

3.4.4.4.

MODBUS/LON gateway function

It is possible to use REC 523 as a Modbus/LON gateway. There are 32 analogue
inputs, 32 analogue outputs, 32 binary inputs and 32 binary outputs (from the
Modbus point of view) that represent the LON network variables. A change of any
input network variable (by the Modbus seen as an analogue or a binary input) will
be reported as a change event on the Modbus side. Setting a new value to the binary
or the analogue output will result in sending an appropriate output network variable
update message on the LON side.
The Modbus/LON gateway function can be used in two ways:
Directly - by using the LON network variables as data points (data from channels
25 and 26)
As a remote I/O - by connecting the LON network variables to inputs and outputs
of the function blocks in the application
Below an example of the Modbus/LON used as a remote I/O:

102

1MRS 752015-MUM

Modbus

Remote Communication Protocol for REC 523

Technical Description

MEAI1_1

BOOL2INT_1

MEAI1
SysAI
RawAI
IV
RESET

MeasOut

BOOL2INT

HighWarning

HighAlarm

LowWarning

LowAlarm

ERR

PSC_7_LED9_16

COMM_IN1

UINT_TO_REAL

B7
B8
B9
UINT_TO_BOOL

COIND1_1

COMM_IN33

COMM_IN34

COIND1

UINT_TO_BOOL

B10
B11

BINOPEN

B12

BINCLOSE

B13

B14
B15

LED 9: blink - measured signal high warning, on - measured signal high alarm
LED 10: blink - measured signal low warning, on - measured signal high alarm
LED 11: on - remote indication open
LED 12: on - remote indication closed

Remote

Note:
The LON interface must be properly configured in order to be able to use the
Modbus/LON gateway function
The time stamps of the LON events are assigned by REC 523 software, not by the
LON devices providing updates of network variables to REC 523. The time
stamp contains the time when a network variable update has been received.

103

Modbus

Remote Communication Protocol for REC 523

1MRS 752015-MUM

Technical Description

Appendix A: Profile checklist

Modbus
DEVICE PROFILE DOCUMENT
Vendor Name: ABB Oy Distribution Automation
Device Name: REC 523 rev. E
Device Function: Slave
Modes:
RTU
ASCII
Supported function codes
Code
(HEX)
01
02
03
04
05
06
07
08
0B
0C
0F
10
11
14
15
16
17
18

Function
Read coil Status
Read Input Status
Read Holding Register
Read Input Registers
Force Single Coil
Preset Single Register
Read Exception Status
Diagnostics
Fetch Comm Event Counter
Fetch Comm Event Log
Force Multiple Coils
Preset Multiple Registers
Report Slave ID
Read General Reference
Write General Reference
Mask Write 4x Register
Read/Write 4x Registers
Read FIFO queue

Supported
Yes
Yes
Yes
Yes
Yes
Yes
No
Yes
No
No
Yes
Yes
No
No
No
No
No
Yes

Supported diagnostic subfunction codes

Code
(HEX)
00
01
02
03
04
0A
0B

104

Name
Return Query Data
Restart Communication Option
Return Diagnostic Register
Change ASCII Delimiter
Force Listen Only Mode
Clear Counters and Diagnostics Register
Return Bus Message Count

Supported
Yes
Yes
Yes
No
Yes
Yes
Yes

1MRS 752015-MUM

Remote Communication Protocol for REC 523

Modbus

Technical Description
Code
(HEX)
0C
0D
0E
0F
10
11
12
13
14
15

Name
Return Bus Communication Error Count
Return Bus Exception Error Count
Return Slave Message Count
Return Slave No Response Count
Return Slave NAK Count
Return Slave Busy Count
Return Bus Character Overrun Count
Return IOP Overrun Count
Clear Overrun Counter Counter and Flag
Get / Clear Modbus Plus Statisctics

Supported
Yes
Yes
Yes
Yes
No
No
No
No
No
No

Supported exception responses

Code
01
02
03
04
05
06
07
08

Name
ILLEGAL FUNCTION
ILLEGAL DATA ADDRESS
ILLEGAL DATA VALUE
SLAVE DEVICE FAILURE
ACKNOWLEDGE
SLAVE DEVICE BUSY
NEGATIVE ACKNOWLEDGE
MEMORY PARITY ERROR

Supported
Yes
Yes
Yes
No
No
No
No
No

Supported data types

Name
Digital input
Coil
Input register
Holding register
General reference

Supported

Digital eventa

Yes
Yes
Yes
Yes
No
Yes

Analog eventa

Yes

a. Extension of the protocol specification

Supported event reporting methods

Name
SACE with a short time stamp
SACE with a full time stamp
MicroScada
MicroScada with a full time stamp
Modicon FIFO read method with a short time stamp
Modicon FIFO read method with a full time stamp

Supported
Yes
Yes
Yes
Yes
Yes
Yes

105

Modbus

Remote Communication Protocol for REC 523

Technical Description

Appendix B: List of used abbreviations

ASCII
CRC
CTS
DCD
FIFO
LRC
PLC
RTS
RTU

106

American Standard Code for Information Interchange

Cyclic redundancy check
Clear to send
Data carrier detect
First in first out
Longitudinal redundancy check
Programmable logic controller
Request to send
Remote terminal unit

1MRS 752015-MUM

1MRS 752015-MUM EN 02.2004

ABB Oy
Distribution Automation
P.O. Box 699
FI-65101 Vaasa
FINLAND
Tel. +358 10 22 11
Fax. +358 10 224 1094
www.abb.com/substationautomation

Dangote CPP
100% (1)
Dangote CPP
161 pages
Modbus Training
100% (6)
Modbus Training
75 pages
Modbus Training PDF
100% (4)
Modbus Training PDF
75 pages
Smith Meter: Modbus & Modbus/TCP Communications
No ratings yet
Smith Meter: Modbus & Modbus/TCP Communications
32 pages
9200 Serial Communications Protocol and ION / Modbus Register Map
No ratings yet
9200 Serial Communications Protocol and ION / Modbus Register Map
23 pages
Serial Port Complete: COM Ports, USB Virtual COM Ports, and Ports for Embedded Systems
From Everand
Serial Port Complete: COM Ports, USB Virtual COM Ports, and Ports for Embedded Systems
Jan Axelson
3.5/5 (9)
Incident Report
No ratings yet
Incident Report
24 pages
Safety Valve Data Sheet
100% (4)
Safety Valve Data Sheet
3 pages
Export Data From Excel To Table Using Custom Web ADI Integrator
No ratings yet
Export Data From Excel To Table Using Custom Web ADI Integrator
17 pages
Modbus Remote Communication Protocol For REM 54 - : Technical Description
No ratings yet
Modbus Remote Communication Protocol For REM 54 - : Technical Description
28 pages
Modbus Remote Communication Protocol For REX 521: Technical Description
No ratings yet
Modbus Remote Communication Protocol For REX 521: Technical Description
24 pages
Pendahuluan Modbus
No ratings yet
Pendahuluan Modbus
4 pages
Modbus Communication Protocol
No ratings yet
Modbus Communication Protocol
3 pages
Modbus
No ratings yet
Modbus
6 pages
Modbus
No ratings yet
Modbus
5 pages
13. Modbus Protocol
No ratings yet
13. Modbus Protocol
13 pages
Modbus Communication
No ratings yet
Modbus Communication
6 pages
Mod Bus
No ratings yet
Mod Bus
17 pages
Modbus Information
No ratings yet
Modbus Information
37 pages
Modbus Protocol
100% (1)
Modbus Protocol
9 pages
What Is Modbus
No ratings yet
What Is Modbus
7 pages
Modbus Protocol Communication
No ratings yet
Modbus Protocol Communication
16 pages
Modbus - Manual
No ratings yet
Modbus - Manual
25 pages
Modbus RTU Page Refresh 2019 v3
No ratings yet
Modbus RTU Page Refresh 2019 v3
6 pages
s800 Modbus PDF
No ratings yet
s800 Modbus PDF
11 pages
Modbus 101 - Introduction To Modbus: Online Help
No ratings yet
Modbus 101 - Introduction To Modbus: Online Help
4 pages
Communication Protocols 1737636300
No ratings yet
Communication Protocols 1737636300
104 pages
LeDucMinh-Scada
No ratings yet
LeDucMinh-Scada
23 pages
History of The Modbus Protocol
No ratings yet
History of The Modbus Protocol
7 pages
Communication Methods (Protocols, Format & Language) For The Substation Automation & Control by MUHAMMAD UZAIR (Project Report of Course 586 B)
No ratings yet
Communication Methods (Protocols, Format & Language) For The Substation Automation & Control by MUHAMMAD UZAIR (Project Report of Course 586 B)
10 pages
Communication Methods For SAS
100% (1)
Communication Methods For SAS
10 pages
Tran Thien Thuan_SCADA
No ratings yet
Tran Thien Thuan_SCADA
15 pages
Unit 3 Modbus PDF
No ratings yet
Unit 3 Modbus PDF
4 pages
modbus protocol
No ratings yet
modbus protocol
9 pages
CDM Modbus Protocol v004
No ratings yet
CDM Modbus Protocol v004
34 pages
Using MODBUS For Process
No ratings yet
Using MODBUS For Process
7 pages
Using MODBUS For Process Control and Automation PDF
No ratings yet
Using MODBUS For Process Control and Automation PDF
7 pages
Modbus - Definition and Details
No ratings yet
Modbus - Definition and Details
13 pages
Automation Unit - 5
No ratings yet
Automation Unit - 5
23 pages
Modbus
No ratings yet
Modbus
12 pages
Introduction To Mod Bus Protocol: BY S.Sandhya 1703099
No ratings yet
Introduction To Mod Bus Protocol: BY S.Sandhya 1703099
9 pages
Low Modbus Communication Works - Inst Tools
No ratings yet
Low Modbus Communication Works - Inst Tools
12 pages
11 Modbus Protocol
No ratings yet
11 Modbus Protocol
22 pages
Modbus Protocol
No ratings yet
Modbus Protocol
8 pages
Modbus Intoduction: Prem Sanil
No ratings yet
Modbus Intoduction: Prem Sanil
36 pages
Ilovepdf Merged
No ratings yet
Ilovepdf Merged
70 pages
02.modbus Protocol
No ratings yet
02.modbus Protocol
12 pages
Modbus Protocol
No ratings yet
Modbus Protocol
14 pages
3-Modbus
No ratings yet
3-Modbus
27 pages
Modbus
No ratings yet
Modbus
16 pages
Modbus
No ratings yet
Modbus
6 pages
Modbus Communication
No ratings yet
Modbus Communication
24 pages
Modbus TCP Overview
No ratings yet
Modbus TCP Overview
23 pages
Modbus Tutorial Control Solutions
No ratings yet
Modbus Tutorial Control Solutions
4 pages
Modbus Application Protocol v1
No ratings yet
Modbus Application Protocol v1
45 pages
Modbus: Soulimane MAMMAR
No ratings yet
Modbus: Soulimane MAMMAR
19 pages
Module 2 - Industrial Network Protocols
No ratings yet
Module 2 - Industrial Network Protocols
43 pages
PLC: Programmable Logic Controller – Arktika.: EXPERIMENTAL PRODUCT BASED ON CPLD.
From Everand
PLC: Programmable Logic Controller – Arktika.: EXPERIMENTAL PRODUCT BASED ON CPLD.
Franco Mario
No ratings yet
WAN TECHNOLOGY FRAME-RELAY: An Expert's Handbook of Navigating Frame Relay Networks
From Everand
WAN TECHNOLOGY FRAME-RELAY: An Expert's Handbook of Navigating Frame Relay Networks
Mamta Devi
No ratings yet
Practical Reverse Engineering: x86, x64, ARM, Windows Kernel, Reversing Tools, and Obfuscation
From Everand
Practical Reverse Engineering: x86, x64, ARM, Windows Kernel, Reversing Tools, and Obfuscation
Bruce Dang
No ratings yet
CCNA Interview Questions You'll Most Likely Be Asked
From Everand
CCNA Interview Questions You'll Most Likely Be Asked
Vibrant Publishers
No ratings yet
Correct Maintenance - Cognex DataMan 8500
From Everand
Correct Maintenance - Cognex DataMan 8500
Unique Content
No ratings yet
You Press 'Enter' on the Browser: What happens when..., #1
From Everand
You Press 'Enter' on the Browser: What happens when..., #1
Dustin W. Morris
5/5 (1)
Networked Control System: Fundamentals and Applications
From Everand
Networked Control System: Fundamentals and Applications
Fouad Sabry
No ratings yet
210 MW Power Plant
No ratings yet
210 MW Power Plant
3 pages
Health Condition Report of The Fan Bs Fan For Boiler No # 1: Observation
No ratings yet
Health Condition Report of The Fan Bs Fan For Boiler No # 1: Observation
4 pages
M. Syed Amirsha Hakani, B.E
No ratings yet
M. Syed Amirsha Hakani, B.E
29 pages
ABG Presentation
50% (2)
ABG Presentation
28 pages
WTC
No ratings yet
WTC
57 pages
Stoker Firing
50% (2)
Stoker Firing
26 pages
Earthing Practice
No ratings yet
Earthing Practice
52 pages
FAN-SOUND and Vibration, Balancing
100% (1)
FAN-SOUND and Vibration, Balancing
33 pages
Instrumentation
No ratings yet
Instrumentation
21 pages
Air Pre Heater
No ratings yet
Air Pre Heater
22 pages
Valves&Soot Blowers
No ratings yet
Valves&Soot Blowers
29 pages
Roller Mills
No ratings yet
Roller Mills
27 pages
SHUT DOWN - Pps
No ratings yet
SHUT DOWN - Pps
6 pages
Proposed Cs3000System Architecture: Remote Operator Stations-Assumed at 50 Mtrs From The Main CR
No ratings yet
Proposed Cs3000System Architecture: Remote Operator Stations-Assumed at 50 Mtrs From The Main CR
1 page
Adjustable Speed Asynchronous Machine in Hydro Power Plants and Its Advantages For The Electric Grid Stability
No ratings yet
Adjustable Speed Asynchronous Machine in Hydro Power Plants and Its Advantages For The Electric Grid Stability
8 pages
Turbine Rolling
100% (4)
Turbine Rolling
39 pages
3 Nos. 660 MW - Coal Fired Supercritical: Conference - ENERGEX 2008 Date: 26-09-2008
No ratings yet
3 Nos. 660 MW - Coal Fired Supercritical: Conference - ENERGEX 2008 Date: 26-09-2008
19 pages
Trouble Shooting
No ratings yet
Trouble Shooting
20 pages
(WTC) Repair Welding in Power Plants
No ratings yet
(WTC) Repair Welding in Power Plants
23 pages
REM54 ParlistENc
No ratings yet
REM54 ParlistENc
158 pages
Boiler Protection AND Interlocks
100% (2)
Boiler Protection AND Interlocks
54 pages
Argentina Ver2 3
No ratings yet
Argentina Ver2 3
9 pages
OOPS in Python
No ratings yet
OOPS in Python
2 pages
Kinovea For Dummies
No ratings yet
Kinovea For Dummies
28 pages
Editing Worksheets: With Polaris Office, You Can Create New .Xls and .XLSX Sheets or Edit Your Worksheets With Ease
No ratings yet
Editing Worksheets: With Polaris Office, You Can Create New .Xls and .XLSX Sheets or Edit Your Worksheets With Ease
10 pages
Fortran 77 Programmers Guide
100% (3)
Fortran 77 Programmers Guide
168 pages
What Is Co NP
No ratings yet
What Is Co NP
11 pages
CMDh_271_2012_Rev.2_2022_12_clean_-_PP_on_request_of_multiple_APP_during_DCPs
No ratings yet
CMDh_271_2012_Rev.2_2022_12_clean_-_PP_on_request_of_multiple_APP_during_DCPs
3 pages
Syllabus
No ratings yet
Syllabus
5 pages
Overview of C++ Memory Management
No ratings yet
Overview of C++ Memory Management
19 pages
O232E - 06p1 - Control Blocks - 1111041
No ratings yet
O232E - 06p1 - Control Blocks - 1111041
13 pages
Difference Equations 3 PDF
No ratings yet
Difference Equations 3 PDF
24 pages
Getting To Know The Work Area
No ratings yet
Getting To Know The Work Area
24 pages
Symfony CMF Master
No ratings yet
Symfony CMF Master
16 pages
T Rec P.862.2 200711
No ratings yet
T Rec P.862.2 200711
12 pages
Register Renaming: ECEN 6253 Advanced Digital Computer Design
No ratings yet
Register Renaming: ECEN 6253 Advanced Digital Computer Design
7 pages
Quezon City Polytechnic University
No ratings yet
Quezon City Polytechnic University
48 pages
Introduction To Computer Architecture
No ratings yet
Introduction To Computer Architecture
2 pages
Java Package
No ratings yet
Java Package
7 pages
MacOS 10.14 Beta 8 Release Notes
No ratings yet
MacOS 10.14 Beta 8 Release Notes
11 pages
FoRex Trading Using Supervised Machine Learning PDF
No ratings yet
FoRex Trading Using Supervised Machine Learning PDF
5 pages
Python Tutorial
No ratings yet
Python Tutorial
51 pages
An Effective Time Series Analysis For Stock Trend Prediction Using ARIMA Model For Nifty Midcap-50
No ratings yet
An Effective Time Series Analysis For Stock Trend Prediction Using ARIMA Model For Nifty Midcap-50
14 pages
PART A - (10 × 2 20 Marks)
No ratings yet
PART A - (10 × 2 20 Marks)
2 pages
Introduction To GSM
100% (1)
Introduction To GSM
110 pages
Dynamic Sketching:: Simulating The Process of Observational Drawing
No ratings yet
Dynamic Sketching:: Simulating The Process of Observational Drawing
31 pages
GE2230 Peer Review Form (2018)
No ratings yet
GE2230 Peer Review Form (2018)
1 page
INFOCOMP Paper Online
No ratings yet
INFOCOMP Paper Online
103 pages
Deshpande Oracle Wait Interface Keynote
100% (1)
Deshpande Oracle Wait Interface Keynote
34 pages
Template JMMR (English)
No ratings yet
Template JMMR (English)
3 pages
E10-001 Practice Exam: Information Storage and Management Exam Version 2
No ratings yet
E10-001 Practice Exam: Information Storage and Management Exam Version 2
153 pages