MicroSCADA Pro SYS 600 9.

3
Modbus Master Protocol
1MRS756641 MicroSCADA Pro SYS 600 9.3
Issued: 31.3.2010 Modbus Master Protocol
Version: A/31.3.2010
Configuration Manual

Contents
Copyrights .....................................................................................5
1. Introduction ...............................................................................7
1.1. This manual ...................................................................................7
1.2. Use of symbols ..............................................................................8
1.3. Related documents .......................................................................9
1.4. Document revisions .......................................................................9
2. Safety information ...................................................................11
2.1. Backup copies .............................................................................11
2.2. Fatal errors ..................................................................................11
3. Communication system configuration ..................................13
3.1. Modbus line configuration ...........................................................14
3.2. Modbus PLC device configuration ..............................................29
3.3. Topics of a PLC device ...............................................................36
3.3.1. Topic parameters .............................................................36
3.3.2. Address conversion between RTU and Modbus ..............41
3.3.3. REF 542plus event reading and time synchronization .....43
4. Using the Modbus Master Protocol .......................................45
4.1. Accessing Modbus data using process objects ..........................45
4.2. Configuring the device attribute interface ....................................47
4.2.1. Attribute interface of a PLC device ..................................47
4.2.2. Example of using device interface commands .................52
4.2.3. Configuration examples ...................................................54
4.2.4. Modbus TCP/IP protocol configuration examples ............56
5. Appendix: Serial cable wiring diagram .................................61
6. Index .........................................................................................63

3
4
1MRS756641 MicroSCADA Pro SYS 600 9.3
Modbus Master Protocol
Configuration Manual

Copyrights
The information in this document is subject to change without notice and should not
be construed as a commitment by ABB Oy. ABB Oy assumes no responsibility for
any errors that may appear in this document.
In no event shall ABB Oy be liable for direct, indirect, special, incidental or
consequential damages of any nature or kind arising from the use of this document,
nor shall ABB Oy be liable for incidental or consequential damages arising from use
of any software or hardware described in this document.
This document and parts thereof must not be reproduced or copied without written
permission from ABB Oy, and the contents thereof must not be imparted to a third
party nor used for any unauthorized purpose.
The software or hardware described in this document is furnished under alicense and
may be used, copied, or disclosed only in accordance with the terms of such license.
Copyright © 2010 ABB Oy
All rights reserved.

Trademarks
ABB is a registered trademark of ABB Group. All other brand or product names
mentioned in this document may be trademarks or registered trademarks of their
respective holders.

Guarantee
Please inquire about the terms of guarantee from your nearest ABB representative.

5
6
1MRS756641 MicroSCADA Pro SYS 600 9.3
Modbus Master Protocol
Configuration Manual

1. Introduction
1.1. This manual
This manual is a programming manual. It describes the principles of interfacing
SYS 600 to an external device using the Modbus protocol.
In order to fully understand the concepts outlined here, the reader should be familiar
with the SCIL programming language and general SYS 600 application techniques.
General knowledge about the Modbus protocol and PLC programming is also
needed.

Modbus master protocol

The Modbus master protocol is mainly used for a master-slave connection between
intelligent devices. This means, in our case, connecting Programmable Logic
Controllers (PLCs) to SYS 600.

General principles of the Modbus protocol

The Modbus Communications Protocol is an asynchronous, byte packaged protocol
used for communications between the master stations and Intelligent Electronic
Devices (IEDs) or Remote Terminal Units (RTUs). It provides a transport
mechanism for the master’s requests and RTU response messages. It supports one
single master station and up to 247 RTUs on a multi-drop line. The Modbus protocol
functions as a true serial line or Transmission Control Protocol (TCP) network.
The Modbus protocol has two distinct modes: ASCII Modbus, which uses ASCII-
encoded hexadecimal messages and binary Modbus, which uses raw binary
messages, see SYS 600 Modbus Slave Protocol for more information.
All transactions are initiated by transmission of a request from the master station, an
RTU may not transmit unsolicited information. Every master station request must
be addressed to a specific RTU and some implementations of Modbus do not support
the broadcast message request type. A transaction consists of a single master station
request, followed by an RTU response or exception frame or a master station
timeout if no RTU response is generated.
There are many different kinds of devices, which use the Modbus protocol for
communication. Therefore, the SYS 600 Modbus protocol emulation is somewhat
restricted. All the features that are available in external devices are not necessarily
available in the NET implementation.
The general strategy that is used in this implementation can be summarized as
follows:
• PC-NET contains necessary protocol conversion features, which enable it to send
and receive Modbus telegrams.
• The SCIL application program in the base system sees the Modbus
implementation in the PC_NET as a PLC type device.
• The PLC type device uses the SYS 600 process database like a RTU device.
• Cross-reference information of correlation between the RTU addresses and
Modbus addresses is stored in the topic configuration data of the PLC device

7
SYS 600 9.3 MicroSCADA Pro 1MRS756641

Modbus Master Protocol

Configuration Manual

• A SYS 600 application program can refer to an external device data through the
SYS 600 process database, or it can use direct communication attributes to read
from or write data to an external device.
• PC-NET is the protocol master. The communication with external devices is done
by using the Modbus RTU protocol mode.
• The current version of the Modbus implementation in the PC_NET supports
functions 1, 2, 3, 4, 5, 6, 16.
• There is also a limited support for functions 20 and 21. These functions are used
for event table transmission and time-synchronization for the REF 542plus
protection relay.

Modbus TCP master protocol

The Modbus TCP master protocol is used in LAN and WAN networks to connect central
stations and outstations to each other. Since the stations use an open TCP/IP interface as
a connection to the network, the structure and the characteristics of the network will be
invisible to the SYS 600 communication software. The overall performance of Modbus/
TCP is higher compared to serial line Modbus due to the faster transmission speed.
The SYS 600 implementation of Modbus TCP operates as a master. The protocol
numbers that are used are equal to the current ones. The SD attribute of the line
defines if the line uses serial port or TCP. The SD attribute must be set before the
line is taken into use for the first time.
Examples
#SET NET'NET':SSD'LINE' = "COM5";line uses serial port 5
#SET NET'NET':SSD'LINE' = "TCP";line uses TCP connection

SYS 600 is able to keep several connections open to the controlled stations at the
same time. Multiple Modbus/TCP lines may be created in the same computer.
The transferred data messages are close to the messages used in serial line based
Modbus protocol. Compared with serial line implementation, a seven byte MBAP
header is added to the beginning of each message. The Modbus master operates
always as a TCP client.
For more information on Modbus TCP, see the following web site:
www.modbus.org: Modbus messaging on TCP/IP.

1.2. Use of symbols

This publication includes information and caution symbols where it is appropriate
to point out safety related or other important information. It also points out useful
hints for the reader. The corresponding symbols should be interpreted as follows:
Caution icon indicates important information or warning related to
the concept discussed in the text. It might indicate the presence of a
hazard, which could result in corruption of software or damage to
equipment/property.
Information icon alerts the reader to pertinent facts and conditions.

8
1MRS756641 MicroSCADA Pro SYS 600 9.3
Modbus Master Protocol
Configuration Manual

1.3. Related documents

The following SYS 600 manuals should be available for reference during the use of
this manual:

Name of the manual MRS number

SYS 600 9.3 System Configuration 1MRS756646
SYS 600 9.3 System Objects 1MRS756662
SYS 600 9.3 Application Objects 1MRS756660
SYS 600 9.3 Status Codes 1MRS756663

Other related documents:

• Product documentation of the used modem

1.4. Document revisions

Version Revision number Date History

A 9.3 31.3.2010 New document

9
10
1MRS756641 MicroSCADA Pro SYS 600 9.3
Modbus Master Protocol
Configuration Manual

2. Safety information
This chapter gives information about the prevention of hazards.

2.1. Backup copies

We suggest that you take backup copies before making any changes, especially the
ones that might have side effects. Software and data need to be copied to another
place, usually to a CD or a backup tape. A writable CD and DAT tape are commonly
used.
Backup copies make it easier to restore application software in case of a disk crash
or any other serious failure when stored data is lost. It is therefore recommended that
backup copies are taken regularly.
There should be at least two system backup copies and two application copies. A
new backup is copied over the oldest backup. This way the latest version is always
available, even if the backup procedure fails.
Detailed information on how to take backup copies should be delivered to the
customer with the application.
System backup
Usually a system backup is taken after the application is made. A backup should be
taken again when changes are made to the SYS 600 system. For example, if the
driver configuration or the network set-up is changed.
Application backup
An application backup is taken simultaneously with the system backup after the
application is made. A backup should be taken again when changes are made to the
application. For example, if pictures or databases are edited or new pictures are
added.

2.2. Fatal errors

A fatal error is an error that causes a break-down or a locked situation in the
SYS 600 program execution.
Handling
In case of a fatal error:
1. Write down the possible SYS 600 error messages.
2. Shut down the SYS 600 main program. If this cannot be done in the SYS 600
Control Panel, try to end the task in Windows Task Manager.

Shutting down the base system computers by switching off the

power might damage the files.

11
SYS 600 9.3 MicroSCADA Pro 1MRS756641

Modbus Master Protocol

Configuration Manual

3. In Windows, the data kept in the main memory at the moment of a fatal error is
placed in the drwtsn32.log file. It is placed in a system folder, for example
WINNT. Analyze and copy the data in this file.
4. Restart the system.
Report the program break-down together with possible SYS 600 error messages and
the information from the drwtsn32.log file to the SYS 600 supplier.
Status codes
Error messages in SCIL are called status codes. For a list of status codes with short
explanations, see SYS 600 Status Codes.

12
1MRS756641 MicroSCADA Pro SYS 600 9.3
Modbus Master Protocol
Configuration Manual

3. Communication system configuration

Each NET unit contains a set of system objects, which specify line properties,
connected devices etc. These objects can be created, modified and deleted by SCIL,
and setting the attributes of the objects can change the properties.
Access to the attributes can be one of the following:
• Read-only: The attribute can only be read. There are still a few exceptions in
which the values can be reset.
• Write-only: The attribute can only be written (set).
• Read, conditional write: The attribute can be both read and written, but the
object must be set out of use (IU = 0) before writing.
• No limitations: The attribute can be both read and written without limitations.
The implementation of the Modbus master protocol in SYS 600 can be divided into
two layers: link layer and application layer. Both of these layers have a specific
functionality and a set of attributes of their own. The link layer corresponds to a line
of a NET unit and the application layer corresponds to a station configured to the
line.
The purpose of the communication system configuration is to:
• Create all the system objects needed to establish communication between the
master and the slave.
• Adjust the values of the system object attributes to match the physical
communication channel and the properties of the slave station.
Setting the attribute values
All line and station attributes have sensible default values but the value of each
attribute must be checked against the requirements of the real communication
system. The attribute values depend on:
• The physical communication media (for example leased telephone line, radio
link, and power line carrier). This affects particularly the attributes of the line, for
example baud rate and parity.
• The network topology used (point-to-point, multidrop). This affects, for example,
the link type.
• The size (number of stations) of the system. This affects especially the timeout
parameters: the slower the media and bigger the system, the longer timeouts are
needed.

Network topologies
The implementation of the Modbus master protocol in SYS 600 supports direct and
serial bus topologies. The direct topology (point-to-point) can be a direct physical
cable from point-to-point or a two-node radio, or modem network. The serial bus
topology (multi-drop) is commonly made up of many modems with their outputs
and inputs tied together, or by using a star-coupler.

13
SYS 600 9.3 MicroSCADA Pro 1MRS756641

Modbus Master Protocol

Configuration Manual

The Modbus protocol supports one master on a line. The following figure illustrates
the network topologies:

topologies

Fig. 3.-1 Network topologies

3.1. Modbus line configuration

The line process of a NET unit performs the functions of the link layer. The purpose
of the link layer is to send and receive messages with external devices using the
Modbus protocol. The link layer provides also frame synchronization and link
control.

Line attributes
The following attributes can be used to configure the Modbus master lines in
SYS 600.

IU In Use
Indicates whether the line is in use (value 1) or not in use (value 0).
Data type: Integer
Value: 0, 1
Index range: 1... 8 (NET line numbering)
Default value: 0
Access: No limitations

14
1MRS756641 MicroSCADA Pro SYS 600 9.3
Modbus Master Protocol
Configuration Manual

PO Protocol
The data transfer protocol used on the line. The line is defined to the NET by setting
this attribute. By setting the attribute to 0 the line definition including all the line
attributes is deleted.
Data type: Integer
Value: 0... 35
Value with Modbus master protocol: 25
Index range: 1... 8 (NET line numbering)
Access: Read, conditional write

SD System Device Name

Associates the NET line numbers of PC-NET with the device names of the physical
channels of serial ports.
By default, line number 1 is connected to COM1, line 2 to COM2 and so on. By
using the SD attribute it is possible to override these default values. This may be
necessary if COM ports are used as NET lines or if, for example, a RocketPort card
is used. If the line should use Modbus TCP/IP, string "TCP" must be given. See also
Section Modbus TCP/IP master attribute under Chapter 3.2.
Data type: Text
Value: See above
Index range: 1...8 (NET line numbering)
Access: Read, conditional write
Example:
#SET NET'NET':SSD'LINE' = "COM5";line uses serial port 5
#SET NET'NET':SSD'LINE' = "TCP";line uses TCP connection

PS Buffer Pool Size

Specifies the number of message buffers reserved for the line. Each buffer can
contain one message. The maximum data content length of a message is 228 bytes.
Data type: Integer
Value: 1... 250
Index range: 1... 8 (NET line numbering)
Default value: 12
Access: Read, conditional write

15
SYS 600 9.3 MicroSCADA Pro 1MRS756641

Modbus Master Protocol

Configuration Manual

BR Baud Rate
Transmission rate used on the line. The attribute is meaningless if the line operates
in the TCP/IP mode.
Data type: Integer
Value: (384 = 38400 bauds, 576 = 57600 bauds)
Unit: Bits/s
Index range: 1...8 (NET line numbering)
Default value: 9600
Access: Read, conditional write

PY Parity
Specifies the parity check (if any) used for the characters transferred on the line. The
attribute is meaningless if the line operates in the TCP/IP mode.
Data type: Integer
Value: 0 = no parity check
1 = odd parity
2 = even parity
Index range: 1...8 (NET line numbering)
Default value: 0
Access: Read, conditional write

RD Receiver Data Bit Count

Specifies the number of data bits in each received character. The attribute is
meaningless if the line operates in the TCP/IP mode.
Data type: Integer
Value: 5, 6, 7 or 8
Unit: Data bits
Index range: 1...8 (NET line numbering)
Default value: 8
Access: Read, conditional write

SB Stop Bits
Specifies the number of stop bits attached to each transmitted character. The
attribute is meaningless if the line operates in the TCP/IP mode.
Data type: Integer
Value: 1 or 2
Unit: Stop bits
Index range: 1...8 (NET line numbering)
Default value: 1
Access: Read, conditional write

16
1MRS756641 MicroSCADA Pro SYS 600 9.3
Modbus Master Protocol
Configuration Manual

TD Transmitter Data Bit Count

Specifies the number of data bits in each transmitted character. The attribute is
meaningless if the line operates in the TCP/IP mode.
Data type: Integer
Value: 5, 6, 7 or 8
Unit: Data bits
Index range: 1...8 (NET line numbering)
Default value: 8
Access: Read, conditional write

PD Polling Delay
Delay between polling messages. The master sends the request with an interval
defined by this attribute.
Data type: Integer
Value: 0...65535
Unit: Milliseconds
Index range: 1...8 (NET line numbering)
Default value: 40
Access: Read, conditional write

DE CTS Delay
Time delay (in milliseconds) between the activation of the RTS signal (Request to
Send) and the start of a new transmission.With the value 0, the transmission starts
immediately when the CTS signal is detected to be signalled. With Modbus TCP/IP,
each message transmission is delayed with DE milliseconds.
Data type: Integer
Value: 0...65535
Unit: Milliseconds
Index range: 1...8 (NET line numbering)
Default value 0
Access: Read, conditional write

HT Header Timeout
Specifies the maximum waiting time in milliseconds within which the first byte of
a link layer response should have been received after the transmission of a message.
If no response has been received within this time, new attempts are performed the
number of times specified by the Enquiry Limit. If no response is still obtained, the
station is be suspended.
Data type: Integer
Value: 0...65535

17
SYS 600 9.3 MicroSCADA Pro 1MRS756641

Modbus Master Protocol

Configuration Manual

Unit: Milliseconds
Index range: 1...8 (NET line numbering)
Default value: 700
Access: Read, conditional write

TI Response Timeout
The time in seconds that the Modbus link layer waits for the end of the response
message. This timeout is internally limited to 32 seconds.
Data type: Integer
Value: 0...255
Unit: Seconds
Index range: 1...8 (NET line numbering)
Default value: 2
Access: No limitations

RI Receive Interrupt Enable Delay

Defines the delay in milliseconds after which the receiver of a NET line is enabled
when a message has been issued.
Data type: Integer
Value: 0...255
0 = receiver enabled all the time
1…9 = receiver enabled right after transmission
10… = receiver enabled as stated by the value
Unit: Milliseconds
Index range: 1...8 (NET line numbering)
Default value: 5
Access: Read, conditional write

EN Enquiry Limit
Specifies the maximum number of times that a message is retransmitted after a
timeout.
Data type: Integer
Value: 1...255
Index range: 1...8 (NET line numbering)
Default value: 6
Access: Read, conditional write

18
1MRS756641 MicroSCADA Pro SYS 600 9.3
Modbus Master Protocol
Configuration Manual

SG Modem Signal
An attribute for direct supervision and control of the state of the modem signal. This
attribute applies to all protocols. It is used for diagnostics and testing.
Data type: Integer
Value: 0 ,1
0 = Passive signal
1 = Active signal
Index range: 100 * line nr + signal no. Signal no. 5 = CTS, 8 = DCD, 20 =
DTR
Access: No limitations
Writing this attribute may cause erroneous operation of the protocol.

MI Message Identification
Object address of system messages.
Data type: Integer
Value: 1... 32760
Index range: 1... 8 (NET line numbering)
Default value: 6000 + (100 * NET number) + line number
Access: Read, conditional write

MS Message Application
The number of the application that is the receiver of the system messages generated
by the line.
Data type: Integer
Value: 1... 250
Default value: 1
Index range: 1... 8 (NET line numbering)
Access: Read, conditional write

PM Protocol Mode
The type of the used Modbus protocol.
Data type: Integer
Value: 0, 1
0: RTU
1: ASCII
Index range: 1...8 (NET line numbering)
Default value: 0
Access: Read, conditional write

19
SYS 600 9.3 MicroSCADA Pro 1MRS756641

Modbus Master Protocol

Configuration Manual

OM Operating mode
A bit pattern which defines the operating mode of the line.
Data type: Integer
Value: 0..65535 (see below)
Index range: 1..8 (NET line numbering)
Default: 0
Access: Read, conditional write
Bit 0: By default, this bit is 0. This enables checking of the transaction
identification number of the responses. The devices copy the
transaction identification from the request to the corresponding
response.
When this bit is set to 1, checking of the transaction
identification number of the responses is disabled. The checking
has to be disabled if some of the Modbus TCP devices connected
to the line do not support transaction identification copying from
the request to the response. In this configuration, there is a risk
that a delayed response is interpreted incorrectly. Therefore, the
usage of the link layer retries defined with line EN is not
recommended.

LK Link Type
The type of the data link connection on the line.
Data type: Integer
Value: 1 = Modem line. A normal RTS-CTS modem signal
handshaking is applied
16 = No RTS-CTS handshaking
Other values are accepted as well but the behaviour is similar to
value 1.
Default value: 1
Index range: 1...8 (NET line numbering)
Access: Read, conditional write

CB Carrier Blocking
This attribute determines whether the Carrier Detect (DCD) signal of the serial port
must be set in order for the Modbus line to receive messages. The DCD pin of the
serial port is used for this attribute.
Data type: Integer
Value: 0 = Carrier blocking not used, Carrier Detect ignored
1 = Carrier blocking not used, Carrier Detect must be set
Default value: 1
Index range: 1...8 (NET line numbering)
Access: Read, conditional write

20
1MRS756641 MicroSCADA Pro SYS 600 9.3
Modbus Master Protocol
Configuration Manual

PP Polling Period
The polling frequency of suspended stations. The attribute specifies how often
suspended stations on the line are polled. Normally, the NET unit is continuously
polling the stations according to the configuration of the topics in PLC device objects.
In case some of the stations are in suspended state, using PP attribute it is possible to
improve the overall performance of the communication line. If PP>1, the Modbus line
skips all other polls to the suspended station but the every PP'th poll. On the other
hand, the communication is re-established more slowly when the PP has a big value.
Data type: Integer
Value: 1 ... 255
Indexing: Line number
Suggested value: 1 ... 10
Default value: 3
Access: Read, conditional write
Example:
#SET NET3:SPP1=5; only every 5th poll to the suspended station is made

DC Diagnostic Counters
The line protocols gather statistical information about the events on the lines by
incrementing a number of diagnostic counters. All the major events and error
situations of the communication have their own counters.
When accessing diagnostic counters, the attribute is indexed according to the formula:
100 * (line number) + (diagnostic counter number)
Modbus master protocol supports the following counters:
1. Transmitted telegrams
2. Failed transmissions
4. Transmitted commands
5. Transmitted replies
11. Received messages
12. Parity errors
13. Overrun errors
14. Check sum errors
15. Framing errors
16. Buffer overflow errors
Data type: Integer
Value: 0...30000
Index range: See above
Access: Read-only, the values can be reset

21
SYS 600 9.3 MicroSCADA Pro 1MRS756641

Modbus Master Protocol

Configuration Manual

Example configuration of Modbus Serial line

The following example shows the Modbus serial line configuration:

Modbus_M_Line_Conf

Fig. 3.1.-1 Example of Modbus serial line configuration

Modbus TCP/IP master attribute

The following attributes can be used for configuring the Modbus master/TCP lines
in SYS 600. The LD attribute is meaningful only if there are multiple IP addresses
in the computer.

22
1MRS756641 MicroSCADA Pro SYS 600 9.3
Modbus Master Protocol
Configuration Manual

LD Local Address
IP address, which is used locally. The setting of this attribute is necessary when the
computer has multiple IP addresses. The addresses, which Modbus master line must
use, are defined. The setting of this attribute must be done before the line is taken
into use for the first time. Empty string in LD means that the default IP address of
the computer is used.
Value: String containing a valid IP address, max 29 characters
Default: Empty string
Access: Read/write
This attribute accepts the IP address in the following form:
#SET NET1:SLD1="10.0.0.1.144.120"

ModbusTCPline_Conf

Fig. 3.1.-2 Example of Modbus TCP line configuration

23
SYS 600 9.3 MicroSCADA Pro 1MRS756641

Modbus Master Protocol

Configuration Manual

There is an internal limitation which prohibits the use of the same

local IP address and the same line number multiple times. This
applies to all PC_NET protocols using LAN.
Example:
It is not possible to have
IEC104 master in Line 1 in PC_NET 1 with LD="192.168.1.1"
and
DNP3.0 slave in Line 1 in PC_NET 2 with LD="192.168.1.1"
the configuration must be changed to
IEC104 master in Line 2 in PC_NET 1 with LD="192.168.1.1"
and
DNP3.0 slave in Line 1 in PC_NET 2 with LD="192.168.1.1"
or to
IEC104 master in Line 1 in PC_NET 1 with LD="192.168.1.1"
and
DNP3.0 slave in Line 1 in PC_NET 2 with LD="192.168.1.2"

DC Diagnostic Counters
The line protocols gather statistical information about the events on the lines by
incrementing a number of diagnostic counters. All the major events and error
situations of the communication have their own counters.
When accessing diagnostic counters, the attribute is indexed according to the
formula:
100 * (line number) + (diagnostic counter number)
Modbus master protocol supports the following counters:
1. Transmitted telegrams
2. Failed transmissions
4. Transmitted commands
5. Transmitted replies
11. Received messages
12. Parity errors
13. Overrun errors
14. Check sum errors
15. Framing errors
16. Buffer overflow errors
20. TCP connect
21. TCP accept
22. TCP close

24
1MRS756641 MicroSCADA Pro SYS 600 9.3
Modbus Master Protocol
Configuration Manual

Data type: Integer

Value: 0...30000
Index range: See above
Access: Read-only, the values can be reset

Autodialing attributes
SYS 600 supports the autocaller functionality for Modbus Master Protocol. An
autocaller is a modem, which contains automatic dial-up functions. Modbus Master
Protocol or Modbus Slave Protocol can call up.
The autocaller uses the AT (Hayes) command set. When using odd or even parity,
the modem has to support 11-bit word length. In some cases, the autocaller is
enabled with the AT commands. For more information about the used modem, refer
to its manual.
The following autocaller attributes are valid for the Modbus Master Protocol dial-up
lines:

AC Autocaller Enabled
States whether an autocaller is connected to the line (value 1) or not (value 0).
Data type: Integer
Value: 0 or 1
Default value: 0
Access: No limitations

AS Autocaller State
Indicates the state of the autocaller.
Data type: Integer
Value: 0...4
0 = IDLE, ready to call up
1 = CONNECTED, transmission is activated
2 = BUSY, autocaller is dialing
3 = INITIAL, autocaller is uninitialized
4 = CONFIGURE, the IU attribute of the line is set to 0
Default value: 0
Access: Read-only

25
SYS 600 9.3 MicroSCADA Pro 1MRS756641

Modbus Master Protocol

Configuration Manual

CL Connection Time Limited

Determines whether a time limit has been set to the connection (value 1) or not
(value 0). The CT attributes determines the connection’s maximum duration.
Data type: Integer
Value: 0 = no time limit
1 = time limit
Default value: 1
Suggested value: A time limit is necessary on certain radio telephone lines.
Limiting the connection time may be good practice also in other
cases, if there is a risk that the connection is not otherwise
broken.
Access: No limitations

CT Connection Time
The maximum time that a connection is allowed to last (in seconds). This attribute
is significant only when the time limiting is activated (CL = 1).
Data type: Integer
Value: 0...600
Unit: Seconds
Default value: 120
Access: No limitations

CN Connection
Dials the devices from the NET and breaks the telephone connections. A telephone
call to a station or workplace is initiated by writing the telephone number to the CN
attribute. The NET unit commands the autodialing modem to dial the telephone
number. The succesful dial is reported as a system message. To break the
connection, write an empty string to the CN attribute.
When dialing a station, the station’s link address is given at the end of the telephone
number string. Type the letter S between the telephone number and the link address.
This option is normally used to increase the communication performance on the
multidrop lines.
Data type: Text
Value: Text string; maximum 25 characters
Default value: Empty text string
Access: No limitations
Example:
#SET NET1:SCN5 = "123456789S11"

26
1MRS756641 MicroSCADA Pro SYS 600 9.3
Modbus Master Protocol
Configuration Manual

CS Connected Station
The station’s link address is communicating with NET.
Data type: Integer
Value: 0...65535
0 = autocaller is not defined or no communication
Default value: 0
Access: Read-only

DD Radio Disconnection Delay

Delay between the last data transfer and the line disconnection.
Data type: Integer
Value: 0...32767
Unit: Seconds
Default value: 0
Access: No limitations

MC Modem Command
A modem can be controlled directly from SCIL with the AT (Hayes) commands.
When an AT command is written to the MC attribute, the attribute is transmitted to
the modem on a line. The MC attribute also reads the modem’s response.
Data type: Text
Value: Text string, an AT/Hayes command
Default value: 0
Access: No limitations
Example:
#SET NET1:SMC3 = ("AS0?")’

PU Pulse Dialing
Determines which dialing principle is used.
Data type: Integer
Value: 0 = tone dialing
1 = pulse dialing
Default value: 0
Access: No limitations

27
SYS 600 9.3 MicroSCADA Pro 1MRS756641

Modbus Master Protocol

Configuration Manual

RC Remote Calls Enabled

States whether the remote calls are enabled on a line. For example the NET unit can
be called from the stations and connected to the line. The attribute applies to lines
with autocaller (AC = 1).
Data type: Integer
Value: 0 = remote calls not enabled
1 = remote calls enabled
Default value: 0
Access: No limitations

RW Radio Connection Wait Time

Normally, the DCD (Data Carrier Detect) signal indicates an active connection.
There are cases, where this is not possible, for example, on the radiotelephone lines
which use the half-duplex links. The RW attribute defines the waiting time in these
cases, from the finishing of the dialing until the transmission is started.
Data type: Integer
Value: 0...32767
Unit: Seconds
Default value: 0
Access: No limitations

SR Autocaller AT S Register
The autocallers’ S registers follows the AT (Hayes) standard. Each autocaller, that
uses the AT command set, has several S registers. The number of the used S registers
and the meaning of the individual S register varies depending on the autocaller
model. Therefore, the contents of the S registers are not described in this manual.
For more information about the S registers, refer to the manual of the used modem.
When using the SR attribute, the folowing numbers of the S registers are accessed:
2, 6, 7, 8, 9, 10, 11 and 12. Other S registers can also be accessed by using the MC
attribute. The S registers 11 and 12 cannot be set.
Data type: Integer
Value: See the modem manuals
Indexing: Seconds
Access: 100 * line number + register number
Example:
The S register number 6 of line 2 in NET1 is set = 4:
#SET NET1:SSR206 = 4

28
1MRS756641 MicroSCADA Pro SYS 600 9.3
Modbus Master Protocol
Configuration Manual

3.2. Modbus PLC device configuration

The PLC station device is the heart of the SYS 600 Modbus protocol converter. It
converts communication messages from SYS 600’s internal protocol to the Modbus
protocol and vice versa. The PLC device stores necessary information of protocol
and address conversion in topic data. The PLC device also stores data which is
scanned from an external device to an internal PC-NET database. The purpose of
this storing is to minimise the amount of messages between the base system and PC-
NET (PC-NET only sends changed data to the base system). Changed data is sent to
the base system process database as RTU process data.

IU In Use
Indicates whether the line is in use (value 1) or not in use (value 0).
Data type: Integer
Value: 0 or 1
Default value: 0
Access: No limitations

LI Line Number
The number of the NET line the station is connected to.
Data type: Integer
Value: 1...8
Access: Read, conditional write

Setting this attribute is not needed when the station is created by

using the DV attribute.

SA Station Address
The station address of the Modbus master station (ID of the slave).
Data type: Integer
Value: 0...255
Default value: 1
Access: Read, conditional write.

AL Allocation
Allocates the station to an application. When the AL attribute has the value 1, the
station is reserved by the application specified by the AS attribute. All the
spontaneous messages from the station are sent to this application.
Data type: Integer
Value: 0 or 1
Access: No limitations

29
SYS 600 9.3 MicroSCADA Pro 1MRS756641

Modbus Master Protocol

Configuration Manual

AS Allocating Application
Specifies the allocating application of the station (see the AL attribute). The
allocating application gets all the spontaneous process data from the station. This
application is also the only one that is allowed to set the device communication
attributes.
Data type: Integer
Value: 0...250
0 = no application
Access: Read-only

MI Message Identification
Object address of the system messages.
Data type: Integer
Value: 1...32760
Default value: 28000 + station number
Access: Read, conditional write

MS Message Application
The number of the application that is the receiver of the system messages generated
by the line.
Data type: Integer
Value: 1...250
Default value: 1
Access: Read, conditional write

DC Diagnostic Counters
The values of the diagnostic counters which the NET unit keeps for the station. The
counters have the following meaning:
1. Suspension information (0 = OK, 1 = suspended)
2. Suspension counter
3. Transmitted data messages
4. Transmitted command messages
5. Transmitted confirmation messages
6. Received data messages
7. Received command messages
8. Received confirmation messages
9. Received unknown messages

30
1MRS756641 MicroSCADA Pro SYS 600 9.3
Modbus Master Protocol
Configuration Manual

Data type: Integer

Value: 1...65535
Index range: 1...20
Access: Read-only

ML Maximum Length
Defines the maximum amount of words requested in each poll. This attribute can be
tuned to get better performance and also if the Modbus slave device requires that
certain blocks in its memory must be polled with a single poll.
Data type Integer
Value: 2..75
Default value: 31
Access: Read, conditional write

RM Running mode
Consists of a set flags that control the behavior and the functionality of the Modbus
master station. Each flag is one bit of this attribute.
Bit 0 If this bit is 0, the topics that are configured to have polling
interval = 0, are not requested in any situation. This is the default
mode. If this bit is 1, the topics that are configured to have
polling interval = 0, are requested in communication startup
situation and when the GI command is issued.
Bit 1 If this bit is 0, the database update operation similar to
communication startup or the GI command is made
automatically after a detected event buffer overflow situation in
the device. This is the default mode. If this bit is 1, no automatic
actions are made.
Data type: Integer
Value: 0..65535, see above
Default value: 0
Access: Read, conditional write

31
SYS 600 9.3 MicroSCADA Pro 1MRS756641

Modbus Master Protocol

Configuration Manual

An example configuration of a PLC device

The 8.4.3 (or newer) System Configuration Tool may be used for configuration
since it supports the Modbus master protocol. The following figure shows an
example configuration of a PLC device.

Modbus_confPLC_Basesys

Fig. 3.2.-1 Example configuration of PLC device

The PLC device object is created by using the Base System Configuration Picture,
as described below.
1. Create a PLC station type:
CREATE_OBJECT > STATION_TYPES >
STY NR: 28
TYPE NAME: PLC
DATABASE TYPE: RTU

32
1MRS756641 MicroSCADA Pro SYS 600 9.3
Modbus Master Protocol
Configuration Manual

2. Create a PLC Station object:

CREATE_OBJECT > STATIONS >
STA NR: 1
TRANS.TYPE: EXTERNAL
NODE NUMBER: 1
TRANSL. OBJ. NUM: 1
STATION TYPE: PLC

CE Communication enabled
Enables/disables the communication of the station object. Using CE attribute, the
SCIL application may disable the communication but the status of the station object
stays unchanged. In TCP/IP mode, the TCP connection to the IED is closed if no
other station object is communicating to the same IP-address. This attribute is useful
if the data reading is made irregularly or in a session-oriented manner.
Data type: Integer
Value: 0 = communication disabled
1 = communication enabled
Default: 1
Access: No limitations
Example:
#SET STA2:SCE=1 ;open a read session
#PAUSE 1
@AV_VECTOR = STA2:SAV(1..4);read analog values
@BI_VECTOR = STA2:SBV(16..31);read binary values

#SET STA2:SNP(3) = (1,0);demand scan for topic 3

#PAUSE 1
#SET STA2:SCE=0;close a read session

33
SYS 600 9.3 MicroSCADA Pro 1MRS756641

Modbus Master Protocol

Configuration Manual

EA Exception Address
Defines the information object address of an analog input process object which is
used to indicate the reception of an exception to a poll message to the remote device.
The value of the process object is the exception code received from the device. The
meaning of each exception is listed in a table below.
If the EA attribute has a value of 0, no process object is updated. The default value
is 0. If the exception is received to a SCIL command, a corresponding error code is
returned, but the process object is not updated.
Value: 0..4095
Default: 0
Access: Read/Write
Table 3.2.-1 Modbus exception codes

Code Description
1 ILLEGAL FUNCTION
2 LLEGAL DATA ADDRESS
3 ILLEGAL DATA VALUE
4 SLAVE DEVICE FAILURE
5 ACKNOWLEDGE
6 SLAVE DEVICE BUSY
8 MEMORY PARITY ERROR
10 GATEWAY PATH UNAVAILABLE
11 GATEWAY TARGET DEVICE FAILED TO RESPOND

Modbus TCP/IP attributes

IA Internet Address
The IP address or the host name of the remote host. The connection is established
with a device in this address by using port number 502. The line must be taken into
use at least once before writing to this attribute.
Value: Any string, max 29 characters
Access: Read/write
This attribute accepts the IP address in the following form:
#SET STA1:SIA="10.0.0.1"

or as an alias name
#SET STA1:SIA="GRACE"

When an alias name is used, it must be defined in the TCP host file
%windir\system32\drivers\etc\hosts.

34
1MRS756641 MicroSCADA Pro SYS 600 9.3
Modbus Master Protocol
Configuration Manual

Multiple station objects may have a same IA, this configuration may be necessary if
the system contains, for example:
Modbus/TCP vs Modbus serial converters. IA-addresses may be entered with a
colon:
STA1:SIA="10.0.0.1"
STA2:SIA="10.0.0.1:2"
STA3:SIA="10.0.0.1:3",

With this configuration a separate TCP session is created for each station object.
If the IA-addresses are entered without a colon
STA1:SIA="10.0.0.1"
STA2:SIA="10.0.0.1"
STA3:SIA="10.0.0.1",

only one TCP session is created for the station objects having same IA. All
communication takes place through this session.
See the example in Modbus TCP/IP protocol configuration examples.

CT Connecting Timeout
The maximum time of the TCP connect operation. The value of this attribute
depends on the speed of LAN, remote station and the possible routers between
SYS 600 and the substation. The value should be lower than the HT attribute of the
line, but high enough to enable reliable reconnecting of the substation. In a
multidrop configuration, a value that is too high may cause communication
disturbances, if some of the stations are not available.
Value: 0..60000
Unit: Milliseconds
Access: Read/Write
Default: 500 ms

ET rEconnecting Timeout
The interval of reconnecting attempt while communication is not established.
Value: 1..255
Unit: Seconds
Access: Read/Write
Default: 30

35
SYS 600 9.3 MicroSCADA Pro 1MRS756641

Modbus Master Protocol

Configuration Manual

Modbus_confPLC2

Fig. 3.2.-2 Example configuration of PLC device

3.3. Topics of a PLC device

The scanning of external device data is controlled by the PLC device topics. Since
the PLC device can contain several different topics (max. 100), it is possible to
divide the memory and IO (input/output) into separate external device areas. These
areas can contain different types of data and they can have individual scanning
intervals.

3.3.1. Topic parameters

The topic parameters are stored in the PLC station topic parameter table. The
memory needed by the topic is dynamically reserved, based on the address and
format parameters. The parameter table is filled in by writing a vector to the TP
attribute, which is also possible to read.

36
1MRS756641 MicroSCADA Pro SYS 600 9.3
Modbus Master Protocol
Configuration Manual

Syntax of a topic configuration command:

STA'n':STP'index'=(Allocation, FirstObjectAddress, LastObjectAddress, Type,
BaseAddress, Format, Interval, delta, [Bitcount])

The 8.4.3 (or newer) System Configuration Tool may be used for configuration,
since it supports the Modbus master protocol. The following figure shows an
example of the topic configuration under the PLC station type.

topic

Fig. 3.3.1.-1 Topic configuration with System Configuration Tool

The topic configuration vector contains the parameters below:

Allocation
This item specifies whether the topic is in use or not. The memory needed for the
topic is reserved, when the topic is taken into use.

FirstObjectAddress
This parameter specifies the First SYS 600 Process Object Address used with this
topic. The object address and object type parameters specify together the actual
process object address (OA), where the first item in the topic is stored. See below:
OA = 4096 * Object_Type + FirstObjectAddress
This calculation is also done automatically in the process object tool. The user has
to add the same address parameters as with the topic. When the actual object address
is read, the calculated object address is shown instead of the parameter value.
If the topic type is SPA_EVENT (101), the given value is the address of the
bitstream process object which is updated with the contents of the event table (RCE
file). If the topic type is REF 542plus time synchronization (102), the given value is
not used.

37
SYS 600 9.3 MicroSCADA Pro 1MRS756641

Modbus Master Protocol

Configuration Manual

LastObjectAddress
This parameter is the object address of the last topic item. The number of items
reserved by the topic is calculated as shown below:
Number of items = LastObjectAddress - FirstObjectAddress
If the topic type is SPA_EVENT (101) or REF 542plus time synchronization (102),
the given value is not used.

Type
This parameter specifies the data type of the process objects. The following table
shows the possible data types of a PLC device.

Table 3.3.1-1 Possible data types of a PLC device

Type Type of process object Possible data formats
1: Object command IO_BIT, M_BIT
3: Digital set-point INT, WORD
4: Analog set-point CHAR, INT, WORD, LONG, FLOAT
6: Analog value CHAR, INT, WORD, LONG, FLOAT
7: Indication (single or double) IO_BIT, M_BIT
8: Pulse counter LONG
9: Digital value INT, WORD
101: SPA_EVENT for REF 542plus Format not used
102: Time sync for REF 542plus Format not used

With the process object type “indication”, one object address (OA)
contains 16 bits.

Base Address
This Modbus address is the first item address of the topic in the PLC memory. With
binary indications the address space is 1 - 65536. With 16 bits registers it is 1 - 4096.
If the topic type is SPA_EVENT (101), the given value refers to the event table
number in the REF 542plus relay and must have some of the following values:

Value Description
2: RCE Table (REF 542plus historical register of events)
5: RCE extended Table (REF 542plus historical register of events in extended
form)
11: (RCE table): as File 2 - Read and Clear of Events
12: (RCE extended table): as File 5 - Read and Clear of Extended Events

If the topic type is REF 542plus time synchronization (102), the given value must be
7 (Time and Date).

38
1MRS756641 MicroSCADA Pro SYS 600 9.3
Modbus Master Protocol
Configuration Manual

Format
This parameter specifies how data is stored in external devices. Possible formats are
shown in the following table.

Table 3.3.1-2 Possible save formats for external devices

Format Code Description
IO_BIT 1 Bit in PLC’s input or output.
M_BIT 2 Memory bit in PLC’s working memory.
CHAR 3 Unsigned 8 type object in PLC’s registers.
A register can allocate two CHAR.
INT 4 One register in PLC’s memory. The MSB bit is used as a
sign bit.
WORD 5 One register in PLC’s memory. The object is used in an
unsigned form.
LONG 6 Signed 32-bit object, which needs two registers from
PLC’s memoy in msw-lsw order.a
MSB_LONG 7 Signed 32-bit object, which needs two registers from
PLC's memory in lsw-msw order.
F32_TYPE 8 Floating point type which needs two registers from PLC’s
memory.
MSB_F32_TYPE 9 Floating point type which allocates two registers in PLC’s
memory. The registers are in reversed order compared
with format 8.
IN_WORD 10 Input register of PLC (3x references).
IN_CHAR 11 Unsigned 8 type object PLC's input registers.
A register can allocate two IN_CHAR.
IN_INT 12 Input register of PLC. The MSB bit is used as a sign bit.
IN_LONG 13 Signed 32-bit object which needs two input registers from
PLC in msw-lsw order.
IN_FLOAT 14 Floating point type which needs two input registers from
PLC.
IN_MSB_LONG 15 Signed 32-bit object which needs two input registers from
PLC in lsw-msw order.
IN_MSB_FLOAT 16 Floating point type which needs two input registers from
PLC.The registers are in reversed order compared with
format 14.
MSB_INT 17 One register in PLC's memory, bytes are in reversed order.
The MSB bit of the first byte of the register is used as a
sign bit.
MSB_WORD 18 One register in PLC's memory. bytes are in reversed order.
The object is used in an unsigned form.
IN_MSB_INT 19 Input register of PLC, bytes are in reversed order. The
MSB bit of the first byte of the register is used as a sign bit
IN_MSB_WORD 20 Input register of PLC (3x references), bytes are in reversed
order. The object is used in an unsigned form.
a. The most significant word - the least significant word (and vice versa)

If the topic type is SPA_EVENT (101) or REF 542plus time synchronization (102),
the given format value is not used.

39
SYS 600 9.3 MicroSCADA Pro 1MRS756641

Modbus Master Protocol

Configuration Manual

Formats WORD and IN_WORD can be used with type 7=Indication. With this
setting, the binary and double binary input process objects can be updated with
values requested using modbus functions 03 (Read Holding registers) and 04 (Read
Input register).

Interval
This is the frequency with which topic data is read from an external device. The
interval units are milliseconds. If the interval is 0, the topic is not polled. The
maximum polling interval is 2147483647 milliseconds (> 24 days). See the
description of the attribute NP Next Poll for on-line changing of the polling interval.

Delta
If the topic type is an analog value (type=4), the delta value is used to minimize the
amount of updating messages from the NET to the base system. The new analog
value is sent to the base system, when the change or the sum (integral) of changes is
bigger than the delta value.
If the topic type is SPA_EVENT (101), the given value is not used. If the topic type
is REF 542plus time synchronization (102), the given value is a constant correction
offset in milliseconds. A non-zero value can be used if the communication hardware
causes a predictable delay in message transmission.

Bitcount
Bitcount is an optional parameter which defines the count of the requested indication
bits in the input word referred to with parameter LastObjectAddress. If the Bitcount
parameter is not defined, the whole 16-bit word is requested and all objects having
OA equal to LastObjectAddress are updated. The value range of the Bitcount
parameter is 1..16. This parameter is meaningful only when the topic type is
indication.
An example configuration of data topics
The following example shows how to configure data topics of a PLC device.
#SET STA1:SIU=0
#SET NET1:SIU4=0

; INIDICATION BLOCK
; OA 28673..28673, IO_BIT, SINGLE INDICATION, BASE ADDRESS 1
#SET STA1:STP(1)=( 1,1,1,7,000,1,1000,0)

;DIGITAL VALUE BLOCK

; OA 36865..36866, WORD_TYPE, DIGITAL VALUE, BASE ADDRESS 400
#SET STA1:STP(2)=(1,1,2,9,399,4,1000,000)

;DIGITAL VALUE BLOCK

; OA 36867..36868, INPUT REGISTER TYPE, DIGITAL VALUE, BASE 400
#SET STA1:STP(2)=(1,3,4,9,399,10,1000,000)

;ANALOG VALUE BLOCK

; OA 24576..24577, INT_TYPE, ANALOG VALUE, BASE ADDRESS 200
#SET STA1:STP(3)=(1,1,2,6,199,4,10000,10)

40
1MRS756641 MicroSCADA Pro SYS 600 9.3
Modbus Master Protocol
Configuration Manual

;ANALOG VALUE BLOCK

; OA 24578..24578, LONG TYPE, ANALOG VALUE, BASE ADDRESS 400
#SET STA1:STP(4)=(1,3,3,6,399,6,1000,00)

;OBJCET COMMAND BLOCK

; OA 4097..4126, IO_BIT, OBJECT COMMAND, BASE ADDRESS 1
#SET STA1:STP(5)=(1,1 ,30,1,0000,1,0,0)

;DIGITAL SETPOINT
; OA 12288..12288, WORD TYPE, DIGITAL SETPOINT, BASE ADDRESS 254
#SET STA1:STP(6)=(1,1,3,3,253,5,0,0)

;ANALOGL SETPOINT
; OA 16384..16387, INT TYPE, ANALOGL SETPOINT, BASE ADDRESS 314
#SET STA1:STP(7)=(1,1,3,4,313,4,0,0)

#SET NET1:SIU4=1
#SET STA1:SIU=1

Example of a topic using function 04:

; OA 24578..24578, IN_LONG TYPE, ANALOG VALUE, BASE ADDRESS 400 #SET
STA'STA':STP(1)=(1,3,3,6,399,13,1000,0 )

Examples of a topic using the Bitcount parameter:

; INDICATION BLOCK
; OA 28673..28673, IO_BIT, SINGLE INDICATION, BASE ADDRESS 1 (12 bits
requested)
#SET STA1:STP(1)=( 1,1,1,7,0,1,1000,0, 12)

; INDICATION BLOCK
; OA 28673..28674, IO_BIT, SINGLE INDICATION, BASE ADDRESS 1 (28 bits
requested)
#SET STA1:STP(1)=( 1,1,2,7,0,1,1000,0, 12)

3.3.2. Address conversion between RTU and Modbus

Addressing system of Modbus protocol

The Modbus protocol and Modicon PLCs divide addressable memory into four
different areas as shown below.

Address: Description:
0xxxx Discrete outputs and discrete coils
1xxxx Discrete inputs
3xxxx Input registers
4xxxx Holding registers

The external communication unit refers to these address areas by using different
message functions as shown below.

Function: Description:
01 Read coil status (0xxxx)
02 Read input status (1xxxx)
03 Read holding registers (4xxxx)

41
SYS 600 9.3 MicroSCADA Pro 1MRS756641

Modbus Master Protocol

Configuration Manual

04 Read input registers (3xxxx)

05 Force single coil (0xxxx)
06 Write single register (4xxxx)
15 Force multiple coils (0xxxx)
16 Write multiple registers (4xxxx)

Many third party Modbus protocol converters (for example Siemens

CP525) do not separate input and memory areas, which means that
functions 01 and 02, as well as 03 and 04 point to the same address
area.
A REF 542plus-related function uses the following Modbus function codes:

20 Read General Reference

21 Write General Reference

See Section 3.3.3. REF 542plus event reading and time synchronization for more
information about the REF 542plus-related functions.
Addressing systems of RTU process objects in SYS 600
These rules apply to topic types 1...9 only. For topic type SPA_EVENT (101), see
3.3.3. REF 542plus event reading and time synchronization.
The object address (OA) of the RTU type process objects is a packed 16 bit value,
which contains the actual address and also the type of data as shown below:
OA = 4096*Object_Type + Object_Address
Object_Type is one of the object types described in the table below.

Table 3.3.2-1 Object type codes and their process object types
Object_Type Code Process object type
1: Object command
3: Digital set-point
4: Analog set-point
6: Analog value
7: Indication (single or double)
8: Pulse counter
9: Digital value
101: SPA Event
102: REF 542plus Time Synchronization

42
1MRS756641 MicroSCADA Pro SYS 600 9.3
Modbus Master Protocol
Configuration Manual

Addressing Modbus objects from SYS 600

This section describes the addressing of Modbus objects from SYS 600. The
following table shows the relationship between the Modbus message functions and
topic parameters.

Table 3.3.2-2 Modbus message functions and topic parameters

Function Topic type Topic format
01 7 M_BIT
02 7 IO_BIT
03 6, 8, 9 CHAR, WORD, INT, LONG, FLOAT
04 6, 9 IN_WORD, IN_CHAR, IN_INT, IN_LONG, IN_FLOAT,
IN_MSB_LONG, IN_MSB_FLOAT
05 1 IO BIT or M BIT
06 3, 4 CHAR, WORD, LONG, FLOAT
15 1 M BIT (only when writing to the DI attribute
16 3, 4 CHAR, WORD, LONG, FLOAT (when vector written)

Topic type = Process object type

3.3.3. REF 542plus event reading and time synchronization

The topic type SPA_EVENT 101 is used to read the event table contents from the
REF 542plus relay. The events are stored in four alternative tables, that is, RCE files.
The selected event table is defined using the Base Address parameter of the topic.
No more than one topic of type 101 can be configured to each STA object.
If the topic of type 101 is configured, the number of available events is continuously
polled with the interval given with the topic parameter Interval. If the event count is
bigger than zero, the event table reading sequence starts and the contents of the event
table is transmitted to a bitstream process object having OA= FirstObjectAddress.
The events are read in blocks of max. 8 events.
If the configured event table number is 2 or 5 (no clear operation made by
the REF 542plus relay), an automatic event clearing command is sent to the relay
when the events have been transmitted successfully to the bitstream process object.
A SCIL application is needed to process the contents of the bitstream process object.
If an event buffer overflow situation occurs in the REF 542plus device, the device
status point is updated with status PLCP_EVENT_BUFFER_OVERFLOW =
13829 and a GI is issued automatically, if it is enabled with the RM attribute bit 1.
The process database is kept in a valid state in the overflow situation.
The topic type REF 542plus time synchronization 102 is used to send the time
synchronization to a REF 542plus relay. The synchronization is made cyclically if
the Interval parameter of the topic is bigger than 0. If the Interval parameter is 0, the
synchronization can be made from the SCIL application using the station attribute
SY. Synchronization is needed to have the correct timestamps for the events.

43
44
1MRS756641 MicroSCADA Pro SYS 600 9.3
Modbus Master Protocol
Configuration Manual

4. Using the Modbus Master Protocol

This chapter describes how to transfer data between SYS 600 and an external device
by using the Modbus protocol serial line or TCP network.

Requirements
The following software is required:
• SYS 600
• Operating system - Windows
You also need general knowledge about the Modbus protocols and PLC
programming.
Install the software as described in their respective manuals. The installation of
SYS 600 is described in SYS 600 Installation and Administration Manual.

4.1. Accessing Modbus data using process objects

The most straightforward way to read data from a PLC device is to use tools in the
SYS 600 package. The first step is to create topics to PC-NET, for example in the
System Configuration Tool and then request data from the device. Creating topics is
explained in Section 3.3.1.
Below is an example of a topic for indication data:

topic

Fig. 4.1.-1 Example of topic configuration

45
SYS 600 9.3 MicroSCADA Pro 1MRS756641

Modbus Master Protocol

Configuration Manual

The requested data can be used by the SYS 600 database, if the RTU type of the
process objects are created. The Object Navigator Tool can be used to create these
objects. The next example shows a process object suitable for the topic above.

Modm_bi

Fig. 4.1.-2 Example of process object

The used topic requests data in the Modbus address space from bit address 1 to 32
(2*16). One SYS 600 block object address contains 16 bits. The process object in
the example uses the first bit in the second block and the Modbus address is 17. For
the rest of the binary data in the same topic, one process object must be created for
every bit. With double binary, two consecutive bits are used and the process object
type is the douple binary RTU object.

46
1MRS756641 MicroSCADA Pro SYS 600 9.3
Modbus Master Protocol
Configuration Manual

Analog format data handling is similar, except that no bit handling is used. The used
process object refers to the defined Modbus register address. For instance, the topic
for analog input is defined in the object addresses 100-101 and the Modbus base
address is 10. In that case, the process object with the address 100 shows data from
the Modbus register address 10.

4.2. Configuring the device attribute interface

Another way to read data from a PLC device is to use the NET attribute interface.
A PLC station contains own database based on the created topics. This database can
be accessed via the attributes described below.

4.2.1. Attribute interface of a PLC device

The attribute interface of a PLC device is described in the following section.

Communication attributes
The base system communicates with the PLC by using communication attributes.
The object of a communication attribute is the NET topic. When the base system
writes (or reads) the communication attribute, the station process changes the read
or written data to the PLC message. The PLC message is created by using the type
of topic and attribute parameters. The written data is sent forward from the NET
without storing the data in the internal database of the NET. The value which comes
from the PLC by reading communication attributes is not stored in the NET
database. The index for the communication attribute must fit some of the topics with
the right topic type. The index must be between IndexFirst and IndexLast.
The communication attributes are the following:

BV Bit Value
This attribute refers to a vector of bits in the PLC memory or IO. When this attribute
is written, a command function 15hex (Force multiple coils) is issued to Modbus
line. When this attribute is read, a single indication or a vector of single indications
is returned. The BV attribute can be used only with topics in which the type is 7 =
Indication. With format = 1 (IO_BIT) the used modbus function in the request is 02
(Read input status) and with format=2 (M_Bit) the function is 01 (Read coil status).
If the format of the topic is WORD or IN_WORD, the used function in the request
is 03 (Read Holding registers) or 04 (Read Input register). With formats WORD or
IN_WORD, it is possible to read full words only.
The indices for BV attribute are calculated as follows:
index = Object_Address * 16 + bit number (when reading from the BV attribute)
index = Object_Address (when writing to the BV attribute)
Access: R/W
Index range: 0..65535
Value range 0..1

47
SYS 600 9.3 MicroSCADA Pro 1MRS756641

Modbus Master Protocol

Configuration Manual

Example of writing
#SET STA1:SBV(1..3)=(1,1,1)
; issues a 'Force multiple coils' command to addresses 1..3
(requires object command topic)

Example of reading
@RET=STA1:SBV(16..31)
; returns a vector of single indications from address 1, bits 0..15
(requires indication topic)

SI Single Indication
This attribute refers to a single bit in the PLC memory or IO. Writing to this
attribute changes the status of one bit in the PLC. The SI attribute is possible to use
only with topics whose type is bit. The index for the SI attribute is calculated as
follows:
index = Object_Address * 16 + bit number (when reading from the SI attribute)
index = Object_Address (when writing to the SI attribute)
Access: R/W
Index range: 0...65535
Value range: 0...1

DI Double Indication
This attribute refers also to the PLC bit memory or bit IO. Double indication has (as
single indication) two logical states (0 and 1), but in the double indication both
directions have their own bits ( 0 -> 01, 1->10). It is possible to use the DI attribute
only with topics whose type is bit. The index for the DI attribute is calculated as
follows:
index = Object_Address * 16 + bit number, when reading from the DI attribute
index = Object_Address, when writing to the DI attribute
The use of double indication needs support from the PLC application program,
because the PLC program language does not directly support double indication data
type.
Access: R/W
Index range: 0..65535
Value range: 0... 3

AV Analog Value
This attribute refers to the register data in the PLC memory. The register is always a
16-bit word in the PLC memory, but the PLC program can use registers in 1, 2 or 4
byte format. The PLC program can also use successive registers in different
formats. For technical reasons, this is not allowed for those register areas which are
transferred to SYS 600. The whole register area, which is referred by one topic
must have equal format (type parameter) as topic.

48
1MRS756641 MicroSCADA Pro SYS 600 9.3
Modbus Master Protocol
Configuration Manual

index = Object_Address
Access: R/W
Index range: 0..65535
Value range: 0...0xFFFFFFFF

DV Digital Value
This attribute refers to the register data of the PLC memory. The register is used as
a 16-bit word.
index = Object_Address
Access: R/W
Index range: 0...65535
Value range: 0...65535

GD General Request of Data

This attribute is not exactly a communication attribute. It is a request to send all the
internal PLC NET database data to SYS 600. It does not perform any
communication between the NET and a remote PLC. When data is sent, the PLC
station sends the system’s status message to SYS 600. When reading, the value of
GD is 1 until the updating is ready.
Access: R/W
Index range: none
Value range: 0...1

SY Synchronize
The SY attribute is used to accurately time-synchronize the Modbus device.
Currently REF 542plus is supported. The sent time is taken from the internal clock
of the MicroSCADA Pro computer controlling the Modbus line. A topic of type 102
(REF 542plus time sync) must be configured before this function can be used.
Data type: Integer
Value: 1 = time sync for REF 542plus (no other values supported)
Access: Write-only
When events are polled using topic type 101 from the REF 542plus device, also the
corresponding static data needs to be requested in order to ensure that the database
is in a consistent state. The maximum value for the static data polling of a input data
is currently 65 seconds which can be too small in some situations and result to
useless traffic in the serial line. A new attribute is presented to give an alternate way
to initiate the static data transmission.

49
SYS 600 9.3 MicroSCADA Pro 1MRS756641

Modbus Master Protocol

Configuration Manual

GI General Interrogation
This attribute can be used to request all configured input topics in a following way:
If the topic is normally polled, that is, its interval is > 0, the polling is speeded up.
If the topic is not polled, that is, its interval is = 0, it is requested if the bit 0 of the
RM attribute is 1.
Data type: Integer
Value: 1 = (no other values supported)
Access: Write-only
The response data updates the process database although no changes have occurred.
This attribute can be used also when event polling is not used.
It is possible that the interval parameter of the input topics is set to 0 for some topics
and the data is requested using SI, DI, AV and DV attributes. These topics are not
included to the GI sequence if not explicitly configured with an RM attribute bit 0.

MM Transparent Modbus Message

Modbus messages can be sent using this attribute. The responses can be accessed by
reading the attribute. The reading can only be done once, therefore it is worth to store
it into a variable in SCIL.
Access: R/W
Index range: Not used
Value: Byte array without checksum, max length 200 bytes
#SET STA1:SMM=(10,1,12,22,23)
@RESPONSE = STA1:SMM
The first byte in the vectors is always the modbus function code but the meaning of
the rest of the bytes depend on the used function code. The detailed structure of the
each message is specified in the Modbus protocol available from www.modbus.org.
The structure of the most common reading message (Function Codes 01,02,03 and
04) is:
(Function Code, Start Address high byte, Start Address low byte, Quantity high
byte, Quantity low byte)
and the corresponding response vector is (Function Code, Byte Count, First data
high, First data low, Second data high, Second data low, ...)

AD Additional Data
This attribute should be read when the response vector to the previous reading of the
AV, DV, DI or SI attributes is shorter than expected.
The response to the AD attribute can be a vector of items of the same type as the
previous response to the reading of the AV, DV, SI or DI attributes.
The response to the AD reading is formed, if the answer from the device does not fit
into one internal message. No new request is made to the device when AD is read.

50
1MRS756641 MicroSCADA Pro SYS 600 9.3
Modbus Master Protocol
Configuration Manual

If a new AV, DV, DI or SI request is made or AD is read, the stored AD response is

cleared.
Error 13832 PLCC_NO_ADDITIONAL_DATA_AVAILABLE is returned to
SCIL, if no data is stored.
Indexing: No
Access: Read only
Value range 0..0xFFFFFFFF, range depends on the preceding request
Example:
Attribute read STA5:SDV(3001..3125) returns a vector of 114 words. Because this
is less than expected, the SCIL application should branch to make an additional read
of the AD attribute (STA5:SAD, no indexing). This returns a vector of 11 words.
These two vectors may be concatenated by the SCIL application if needed.
The application should not make a new read of DV, AV, SI or DI before the AD
attribute is read, otherwise the data for AD is lost. This can be a problem in a rare
occasion of multiple SCIL instances accessing the same STA object at the same
time.

NP Next Poll
This attribute can be used to speed up or slow down polling interval of a topic,
generate demand scans, and enable or disable the polling of a single topic. This
attribute is useful if there is a need to control the polling of the IED from the SCIL
application. The given interval can be configured to be permanent. The given index
of the NP attribute must be the same as the one given in topic definition using
attribute TP.
Data type: Integer or a vector of two integers
Value: Vector (INTERVAL, [PERMANENT])
Index: Topic index
Access: Write only

INTERVAL
Defines the time in milliseconds to the next poll of the topic
defined with topic index.
Value = 1 generates an immediate poll also if the permanent
interval is 0 (=polling disabled).
Delayed polling is not possible if the polling is disabled.

PERMANENT
A non-zero (use 1) value defines the given interval to be
permanent for the topic.
If interval = 0 is set as permanent, the topic is not polled
anymore.

51
SYS 600 9.3 MicroSCADA Pro 1MRS756641

Modbus Master Protocol

Configuration Manual

Examples
#SET STA'n':SNP'index' = (0,1);disable the polling of the topic
#SET STA'n':SNP'index' = 1;poll the topic once (demand scan)
#SET STA'n':SNP'index' = (20000,1);enable the polling of the topic
using 20 second interval
#SET STA'n':SNP'index' = (3000,0);speed up the polling for one poll
#SET STA'n':SNP'index' = (3000,1);redefine the polling interval to
be 3 seconds

4.2.2. Example of using device interface commands

The SYS 600 application program can write data to an external device through the
process database (SYS 600 generates a process message automatically, when the
output type of an RTU process object is updated). Another method to send
commands from SYS 600 is to use communication attributes as described in the
following section.
Writing object commands
Object commands (e.g. switching device open/close commands) are sent as control
relay output block messages. This message is a multi-purpose command. This
section gives an example on how to write object commands.

Topic configuration
#SET STA1:STP(5)=(1,1,30,1,0,1,0,0)

Process object configuration

Name: PLC_1_OC Station: 1
Index: 2 OA: 2
Type: Object command
The following commands set the same binary output (OUT_BIT1) in the PLC.
#SET PLC_1_OC:P2 = 1
#SET STA1:SSI(2) =1 ;-> index = object_address

Writing analog setpoints

Process object configuration

Name: PLC_1_AS Station: 1
Index: 1 OA: 1
Type: Analog setpoint

52
1MRS756641 MicroSCADA Pro SYS 600 9.3
Modbus Master Protocol
Configuration Manual

If 16-bit values are used:

Topic Configuration
#SET STA1:STP(7)=(1,1,3,4,313,4,0,0)

The following commands set the register value 314 to 1234 in the PLC:
#SET PLC_1_AS:P1 = 1234
#SET STA1:SAV(1) = 1234

The following command updates a vector in the PLC (reg 314 = 1234, reg 315 = 1,
reg 316=2)
#SET STA1:SAV(1..3) = (1234,1,2)

If 32-bit values are used:

Configuration
#SET STA1:STP(7)=(1,1,3,4,313,6,0,0)

The following commands sets the register value 314 to 1 and the register value 315
to 57920 in the PLC:
#SET PLC_1_AS:P1 = 123456
#SET STA1:SAV(1) =123456

If the topic format is 7 (MSB_LONG), the values in the registers are

used in opposite order.

If float values are used, the configuration is:

#SET STA1:STP(7)=(1,1,3,4,313,8,0,0)

The following command sets the value 3.21 to registers 314, 315
#SET STA1:SAV(1)=3.21

Writing digital setpoints

Process object configuration:
Name: PLC_1_DS Station: 1
Index: 1 OA: 1
Type: Digital setpoint

Topic configuration
#SET STA1:STP(6)=(1,1,3,3,253,5,0,0)

The following commands set the register value 254 to 1234 in the PLC:
#SET PLC_1_DS:P1 = 1234
#SET STA1:SDV(1) =1234

Updating a vector (reg 254 = 1234, reg 255 = 1, reg 256=2)

#SET STA1:SDV(1..3) = (1234,1,2)

53
SYS 600 9.3 MicroSCADA Pro 1MRS756641

Modbus Master Protocol

Configuration Manual

4.2.3. Configuration examples

As previously described, the NET continously scans the PLC memory. Only data
changes are sent to SYS 600. The PLC station sends data to the SYS 600 process
database.
The process database object address is calculated as:
OA = ((PLC_address - Topic_Base_Address) + StartOA)+4096*Topic_Type
It is also possible to read data from the PLC by using communication attributes as
described in the next section.

Reading indications
Process object configuration:
Name: PLC_1_SI Station: 1
Index: 1 OA: 1
Type: Indication OB: 0

Topic configuration
#SET STA1:STP(1)=( 1,1,1,7,0,1,1000,0)

Scanning
The NET reads the state of 16 input bits starting from BIT0 with the interval of 1
second. The process value PLC_1_SI:P1 is updated, if the state of BIT0 of PLC is
changed.
The direct reading of the INPUT BIT0 state is possible with the following SCIL
command:
@BIT = STA1:SSI(16) ;-> index = 16*objcet_address + bit_address

and reading vector (16 values):

@BIT_V = STA1:SSI(16..31)

Reading analog values

Process object configuration
Name: PLC_1_AV Station: 1
Index: 1 OA: 1
Type: Analog value

54
1MRS756641 MicroSCADA Pro SYS 600 9.3
Modbus Master Protocol
Configuration Manual

Topic configuration
#SET STA1:STP(3)=(1,1,20,6,199,4,10000,10)

Scanning
The NET unit reads 20 registers from the PLC starting from register 200 with the
interval of 10 seconds.The process value PLC_1_AV:P1 will be updated, if the
register 200 value is changed.
The direct reading of the register 200 value is possible with the following SCIL
command:
@VALUE = STA1:SAV(1)

and reading a vector:

@VALUE = STA1:SAV(1..20)

Reading digital values

Process object configuration

Name: PLC_1_DV Station: 1
Index: 1 OA: 1
Type: Digital value

Configuration
#SET STA1:STP(2)=(1,1,2,9,399,4,1000,000)

Scanning
The NET reads two registers from the PLC memory starting from register 400 with
the interval of 1 second.
The process value PLC_1_DV:P1 is updated, if the register 400 is changed. The
following SCIL command reads the value of register 400 from the PLC:
@VALUE = STA1:SDV(1)

and reading a vector:

@VALUE = STA1:SAV(1..2)

55
SYS 600 9.3 MicroSCADA Pro 1MRS756641

Modbus Master Protocol

Configuration Manual

Reading digital values from input registers

Process object configuration

Name: PLC_1_IR Station: 1
Index: 1 OA: 1
Type: Digital value

Configuration
#SET STA1:STP(2)=(1,1,2,9,399,10,1000,0)

Scanning
The NET reads two input registers from the PLC memory starting from register 400
with the interval of 1 second.
The process value PLC_1_DV:P1 is updated, if the register 400 is changed. The
following SCIL command reads the value of input register 400 from the PLC:
@VALUE = STA1:SDV(1)

4.2.4. Modbus TCP/IP protocol configuration examples

A setup of one station:
@NET=2

@STA = 1
@LINE = 1

#SET NET'NET':SPO'LINE'=25
#SET NET'NET':SDV(28)=('STA','LINE')
#SET NET'NET':SSD'LINE'="TCP"
#SET NET'NET':SEN'LINE'=3
#SET NET'NET':SLD'LINE'="10.0.0.1.144.119"
#SET NET'NET':SMS'LINE'='NET'
#SET NET'NET':SPM'LINE'=0
#SET NET'NET':SIU'LINE'=1
#SET NET'NET':SIU'LINE'=0

#SET STA'STA':SAL=1
#SET STA'STA':SSA=1
#SET STA'STA':SIA="GRACE"
#SET STA'STA':SET=3
#SET STA'STA':SIU=1

#SET NET'NET':SIU'LINE'=1

A setup of three stations:

@NET=2
@LINE = 1

#SET NET'NET':SPO'LINE'=25
#SET NET'NET':SDV(28)=(1,'LINE')
#SET NET'NET':SDV(28)=(2,'LINE')
#SET NET'NET':SDV(28)=(3,'LINE')
#SET NET'NET':SSD'LINE'="TCP"
#SET NET'NET':SEN'LINE'=3

56
1MRS756641 MicroSCADA Pro SYS 600 9.3
Modbus Master Protocol
Configuration Manual

#SET NET'NET':SMS'LINE'='NET'
#SET NET'NET':SPM'LINE'=0
#SET NET'NET':SIU'LINE'=1
#SET NET'NET':SIU'LINE'=0

@STA = 1

#SET STA'STA':SAL=1
#SET STA'STA':SSA='STA'
#SET STA'STA':SIA="GINA"
#SET STA'STA':SIU=1

@STA = 2

#SET STA'STA':SAL=1
#SET STA'STA':SSA='STA'
#SET STA'STA':SIA="LIZ"
#SET STA'STA':SIU=1
@STA = 3

#SET STA'STA':SAL=1
#SET STA'STA':SSA='STA'
#SET STA'STA':SIA="GRACE"
#SET STA'STA':SIU=1

#SET NET'NET':SIU'LINE'=1

TCP additions for LAN/WAN network

SYS 600 Modbus TCP uses the default IP address provided by the operating system.
The created Modbus TCP line reserves a port number

2501+linenumber
for its internal use.
In TCP/IP mode (connection-oriented), the connection is established to port

502
of the slave device. The slave device must accept connections from this port. If not
explicitly specified, only one connection to each Modbus TCP server is established
at the same time. The second example below describes the gateway configuration.
The IP address of the slave is configured with IA-attribute of the station object.

57
SYS 600 9.3 MicroSCADA Pro 1MRS756641

Modbus Master Protocol

Configuration Manual

Example topologies:

Modbus TCP Line ; Line SD = "TCP"; connection oriented mode

STA1 ; connection made to port 502 of each IP-address
STA2 Station 1 IA = "62.236.145.119"
STA3 Station 2 IA = "62.236.145.120"
IP 62.236.145.130 Station 3 IA = "62.236.145.121"

MicroSCADA LAN/WAN

Station 1 (IED, RTU...) Station 2 (IED, RTU...) Station 3 (IED, RTU...)

IP-address IP-address IP-address
62.236.145.119 62.236.145.120 62.236.145.121
Listens to port 502 Listens to port 502 Listens port 502

modbus TCP_b

Fig. 4.2.-1 SYS 600 as Modbus TCP master in multidrop environment

modbus TCP2_c

Fig. 4.2.-2 SYS 600 as Modbus TCP master in multidrop environment with gateway

58
1MRS756641 MicroSCADA Pro SYS 600 9.3
Modbus Master Protocol
Configuration Manual

Example 1
Line SD="TCP";connection oriented mode
;connection made to port 502 of each IP-address
;three concurrent TCP session established to address 62.236.145.119
Station 1 IA="62.236.145.119"
Station 2 IA="62.236.145.119:2"
Station 3 IA="62.236.145.119:3"
Station 4 IA="62.236.145.120"

Example 2
Line SD="TCP";connection oriented mode
;connection made to port 502 of each IP-address
;one TCP session established to address 62.236.145.119
Station 1 IA="62.236.145.119"
Station 2 IA="62.236.145.119"
Station 3 IA="62.236.145.119"
Station 4 IA="62.236.145.120"

59
60
1MRS756641 MicroSCADA Pro SYS 600 9.3
Modbus Master Protocol
Configuration Manual

5. Appendix: Serial cable wiring diagram

When connecting the Modbus master to a SYS 600 slave using a direct serial cable,
the wiring illustrated by the following figure can be used:

Fig. 5.-1 Serial cable wiring diagram

61
62
1MRS756641 MicroSCADA Pro SYS 600 9.3
Modbus Master Protocol
Configuration Manual

6. Index
A
AC ............................................................................................................. 25
Accessing Modbus data ............................................................................ 45
AD ...................................................................................................... 30, 50
Additonal Data .......................................................................................... 50
Address conversion ............................................................................ 29, 41
AL ............................................................................................................. 29
Allocating Application ............................................................................. 30
Allocation ........................................................................................... 29, 37
Analog format ........................................................................................... 47
Analog values ..................................................................................... 40, 54
Application Backup .................................................................................. 11
AS ....................................................................................................... 25, 30
Autocaller AT S Register ......................................................................... 28
Autocaller Enabled ................................................................................... 25
Autocaller State ........................................................................................ 25
B
Backup copies ........................................................................................... 11
Base Address ............................................................................................ 38
Basic line attributes .................................................................................. 14
Baud Rate ................................................................................................. 16
Binary output ............................................................................................ 52
Bit handling .............................................................................................. 47
Bit Value ................................................................................................... 47
Block object address ................................................................................. 46
BR ............................................................................................................. 16
Buffer Pool Size ....................................................................................... 15
BV ............................................................................................................. 47
C
CL ............................................................................................................. 26
CN ............................................................................................................. 26
Communication attributes ........................................................................ 47
Connected Station ..................................................................................... 27
connecting Timeout .................................................................................. 35
Connection ................................................................................................ 26
Connection Time ...................................................................................... 26
Connection Time Limited ......................................................................... 26
CS ............................................................................................................. 27
CT ....................................................................................................... 26, 35
CTS ........................................................................................................... 17

63
SYS 600 9.3 MicroSCADA Pro 1MRS756641

Modbus Master Protocol

Configuration Manual

D
Data transmission attributes ..................................................................... 15
DC ................................................................................................ 21, 24, 30
DD ............................................................................................................ 27
DE ............................................................................................................ 17
Delta ......................................................................................................... 40
Device attribute interface ......................................................................... 47
DI ........................................................................................................ 43, 48
Diagnostic Counters ..................................................................... 21, 24, 30
Digital Value ............................................................................................ 49
Double Indication ..................................................................................... 48
DV ...................................................................................................... 29, 49
E
EA ............................................................................................................ 34
EN ............................................................................................................ 18
Enquiry Limit ........................................................................................... 18
ET ............................................................................................................. 35
Exception Address .................................................................................... 34
F
FirstObjectAddress ................................................................................... 37
Float values .............................................................................................. 53
Format ...................................................................................................... 39
G
GD ............................................................................................................ 49
General Request of Data .......................................................................... 49
General strategy .......................................................................................... 7
H
Header Timeout ........................................................................................ 17
HT ............................................................................................................ 17
I
IA .............................................................................................................. 34
In Use ................................................................................................. 14, 29
Indication data .......................................................................................... 45
Intelligent Electronic Devices (IEDs) ........................................................ 7
Internet Address ....................................................................................... 34
Interval ..................................................................................................... 40
IU ........................................................................................................ 14, 29
L
LastObjectAddress ................................................................................... 38
LD ............................................................................................................ 23
LI .............................................................................................................. 29
Line attributes ........................................................................................... 14
Line Number ............................................................................................ 29
Local Address ........................................................................................... 23
64
1MRS756641 MicroSCADA Pro SYS 600 9.3
Modbus Master Protocol
Configuration Manual

M
MC ............................................................................................................ 27
Message Application .......................................................................... 19, 30
Message Identification ........................................................................ 19, 30
MI ....................................................................................................... 19, 30
Modbus TCP master attribute ................................................................... 22
Modbus TCP master protocol ..................................................................... 8
Modbus TCP/IP attributes ........................................................................ 34
Modem Command .................................................................................... 27
Modem Signal .......................................................................................... 19
Modicon .................................................................................................... 41
MS ...................................................................................................... 19, 30
Multi-drop network topology ................................................................... 13
N
NET attribute interface ............................................................................. 47
Next Poll ................................................................................................... 51
NP ............................................................................................................. 51
O
OA ...................................................................................................... 37, 42
Object commands ..................................................................................... 52
Object Navigator Tool .............................................................................. 46
P
Parity ......................................................................................................... 16
PC ............................................................................................................. 27
PC-NET ................................................................................................ 7, 45
PD ............................................................................................................. 17
PLC ....................................................................................................... 7, 48
PLC device ............................................................................................... 45
PLC station ............................................................................................... 47
PM ............................................................................................................ 19
PO ............................................................................................................. 15
Point-to-point network topology .............................................................. 13
Polling Delay ............................................................................................ 17
Polling Period ........................................................................................... 21
PP .............................................................................................................. 21
Process object ........................................................................................... 46
Protocol ..................................................................................................... 15
Protocol master ........................................................................................... 8
Protocol Mode .......................................................................................... 19
PS .............................................................................................................. 15
Pulse Dialing ............................................................................................ 27
PY ............................................................................................................. 16

65
SYS 600 9.3 MicroSCADA Pro 1MRS756641

Modbus Master Protocol

Configuration Manual

R
Radio Connection Wait Time ................................................................... 28
Radio Disconnection Delay ...................................................................... 27
RC ............................................................................................................ 28
RD ............................................................................................................ 16
Read data .................................................................................................. 45
Receive Interrupt Enable Delay ............................................................... 18
Receiver Data Bit Count .......................................................................... 16
rEconnecting Timeout .............................................................................. 35
Register address ........................................................................................ 47
Remote Calls Enabled .............................................................................. 28
Remote Terminal Units (RTUs) ................................................................. 7
Request data ............................................................................................. 45
Response Timeout .................................................................................... 18
RI .............................................................................................................. 18
RTS signal ................................................................................................ 17
RTU .......................................................................................................... 46
RTU addresses ............................................................................................ 7
RW ........................................................................................................... 28
S
SA ............................................................................................................. 29
SB ............................................................................................................. 16
SD ............................................................................................................. 15
SG ............................................................................................................. 19
SI .............................................................................................................. 48
Single
Bit ....................................................................................................... 48
Indication ............................................................................................ 48
SR ............................................................................................................. 28
Station Address ........................................................................................ 29
Status codes .............................................................................................. 12
Stop Bits ................................................................................................... 16
SYS 600 database ..................................................................................... 46
System
Backup ................................................................................................ 11
Messages ............................................................................................ 19
System Configuration Tool ................................................................ 37, 45
System Device Name ............................................................................... 15
T
TD ............................................................................................................ 17
TI .............................................................................................................. 18
Topic
Configuration ..................................................................................... 37
Parameters .......................................................................................... 36
TP ............................................................................................................. 36

66
1MRS756641 MicroSCADA Pro SYS 600 9.3
Modbus Master Protocol
Configuration Manual

Transmitter Data Bit Count ...................................................................... 17

Type .......................................................................................................... 38
W
Wiring ....................................................................................................... 61
Writing object commands ......................................................................... 52

67
Contact us

© Copyright 2010 ABB. All rights reserved.

ABB Oy
Substation Automation Products
P.O. Box 699
FI-65101 Vaasa
FINLAND
Tel. +358 10 22 11
Fax. +358 10 224 1094

www.abb.com/substationautomation

1MRS756641 A/31.3.2010