Advant® OCS RCOM

with Master software Advant Controller 55

User’s Guide
 Use of DANGER, WARNING, CAUTION, and NOTE
This publication includes, DANGER, WARNING, CAUTION, and NOTE information where appropriate to point out safety
related or other important information.
DANGER Hazards which could result in severe personal injury or death
WARNING Hazards which could result in personal injury
CAUTION Hazards which could result in equipment or property damage
NOTE Alerts user to pertinent facts and conditions
Although DANGER and WARNING hazards are related to personal injury, and CAUTION hazards are associated with
equipment or property damage, it should be understood that operation of damaged equipment could, under certain operational
conditions, result in degraded process performance leading to personal injury or death. Therefore, comply fully with all
DANGER, WARNING, and CAUTION notices.

TRADEMARKS
Advant, AdvaCommand, AdvaInform, and AdvaBuild are registered trademarks of ABB Asea Brown Boveri Ltd, Switzerland.
ABB Master, MasterPiece, MasterView, MasterAid, and SuperView are registered trademarks of ABB Asea Brown Boveri Ltd.
Switzerland
MasterNet, MasterBus, and MasterBatch are trademarks of ABB Asea Brown Boveri Ltd. Switzerland
AdvaControl, AdvaBatch and AdvaTalk are registered trademarks of ABB Process Automation Corp. USA

NOTICE
The information in this document is subject to change without notice and should not be construed as a commitment by ABB
Industrial Systems AB . ABB Industrial Systems AB assumes no responsibility for any errors that may appear in this document.
In no event shall ABB Industrial Systems AB 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 Industrial Systems AB 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 ABB Industrial Systems AB ’s written permission,
and the contents thereof must not be imparted to a third party nor be used for any unauthorized purpose.
The software described in this document is furnished under a license and may be used, copied, or disclosed only in accordance
with the terms of such license.

CE MARKING
This product meets the requirements specified in EMC Directive 89/336/EEC and in Low Voltage Directive 72/23/EEC.

Copyright © ABB Industrial Systems AB 1997

3BSE001264/D

Template: 3BSE001286/E

3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Table of Contents

TABLE OF CONTENTS
Chapter 1 - Introduction
1.1 General Information................................................................................................. 1-1
1.2 Manual Organization ............................................................................................... 1-2
1.3 Conventions ............................................................................................................. 1-3
1.4 Related Documentation............................................................................................ 1-4
1.5 Release History ........................................................................................................ 1-4
1.6 Terminology............................................................................................................. 1-4
1.7 Equipment Requirements......................................................................................... 1-5
1.8 Product Overview .................................................................................................... 1-6
1.8.1 Functionality ......................................................................................... 1-10
1.8.2 Functional Overview............................................................................. 1-11
1.8.3 Initiating a Connection.......................................................................... 1-13
1.8.4 Data Transfer and Commands .............................................................. 1-13
1.8.4.1 Data Flow on the RCOM Link....................................... 1-14
1.8.4.2 Data Flow on the RCOM+ Link .................................... 1-16
1.8.5 Flow Control ......................................................................................... 1-16

Chapter 2 - Installation
2.1 Site Planning Environment ...................................................................................... 2-1
2.2 AC 55 Setup............................................................................................................. 2-1
2.3 Modems and Cables................................................................................................. 2-3
2.4 AC 55 Start-up Procedures ...................................................................................... 2-5
2.5 AC 55 Product Verification ..................................................................................... 2-5

Chapter 3 - Configuration/Application Building

3.1 Design considerations .............................................................................................. 3-1
3.2 Capacity and Performance ....................................................................................... 3-2
3.2.1 Capacity .................................................................................................. 3-2
3.2.2 Total Load on RCOM Link .................................................................... 3-2
3.2.2.1 Transmission Time of MVB Elements ............................ 3-3
3.2.2.2 Load Caused by MVB Elements...................................... 3-4
3.2.2.3 Load Caused by Time-Tagged Events ............................. 3-5
3.2.2.4 Load Caused by Clock Synchronization .......................... 3-5
3.2.3 CPU Load From MVI Data Block Communication ............................... 3-6
3.3 Application Start-up................................................................................................. 3-6
3.4 Tutorial..................................................................................................................... 3-7
3.4.1 Application in Master Node.................................................................... 3-8
3.4.1.1 AC 55 DB Elements in the Master Node ......................... 3-8
3.4.1.2 The PC Program in the Master Node ............................. 3-12

3BSE 006 529R0001 Rev A i

RCOM User’s Guide
Table of Contents

CONTENTS (continued)
3.4.2 Application in Slave Node .................................................................... 3-13
3.4.2.1 DB Elements in the Slave Node ..................................... 3-13
3.4.2.2 PC Program in the Slave Node....................................... 3-15
3.5 Application Procedures .......................................................................................... 3-16
3.5.1 Master Functions................................................................................... 3-17
3.5.2 Slave Functions ..................................................................................... 3-18
3.6 Configuration of RCOM Application DB Elements and PC Program .................. 3-19
3.6.1 DB Elements for RCOM Configuration ............................................... 3-19
3.6.1.1 DBElements for MVI Module Configuration
CT481, CT482................................................................ 3-20
3.6.1.2 DB Element for MVI Channel Characteristics
MVICHAN ..................................................................... 3-21
3.6.1.3 DB Element for Node Configuration and Status
MVINODE ..................................................................... 3-28
3.6.1.4 DB Element for Data Transfer and Command MVB..... 3-35
3.6.2 DB Element MVB for Data Transfer .................................................... 3-40
3.6.2.1 Data Transfer from Master to Slave ............................... 3-42
3.6.2.2 Data Transfer from Slave to Master ............................... 3-44
3.6.3 DB Element MVB for Commands........................................................ 3-47
3.6.3.1 Cold Start a Slave ........................................................... 3-48
3.6.3.2 Warm Start/Block a Slave .............................................. 3-50
3.6.3.3 Normalize/Deblock a Slave............................................ 3-52
3.6.3.4 Clock Synchronization ................................................... 3-53
3.6.3.5 Telephone Commands .................................................... 3-55
3.6.4 PC Program Layout............................................................................... 3-58
3.6.4.1 RCOM Data Flow Control Type Circuits ...................... 3-60
3.6.4.2 RCOM Data Flow Control ............................................. 3-63
3.6.4.3 Transmission of Time-Tagged Events from Event Sets. 3-64
3.6.5 Configuration with MasterPiece 40 ...................................................... 3-66
3.6.5.1 Application in Master Node AC 110 DB Elements ....... 3-68
3.6.5.2 Parameters on the Slave Node (MP 40) ......................... 3-75

Chapter 4 - Runtime Operation

4.1 Product Operation .................................................................................................... 4-1
4.2 Operating Overview ................................................................................................. 4-1
4.3 Runtime Tutorial ...................................................................................................... 4-2
4.4 Operating Instructions.............................................................................................. 4-2
4.5 Runtime Operating Menus ....................................................................................... 4-2

ii 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Table of Contents

CONTENTS (continued)
Chapter 5 - Maintenance
5.1 Hardware Indicators................................................................................................. 5-1
5.2 Software Indicators .................................................................................................. 5-1
5.3 Module Diagnosis .................................................................................................... 5-2
5.4 Fault Finding and User Repair................................................................................. 5-3

INDEX

3BSE 006 529R0001 Rev A iii

RCOM User’s Guide
Table of Contents

iv 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 1.1 General Information

Chapter 1 Introduction

1.1 General Information

This manual describes the asynchronous communication protocol RCOM (Remote COMmu-
nication) in the Advant Controller 55 (AC 55). RCOM provides remote communication capa-
bilities, using multidrop, point-to-point or dial-up connections, e.g. over public telephone
networks.
Traffic on the RCOM link is controlled by a master station. Direct communication is possible
only between the master and the slaves. Stations connected via RCOM appear in the ABB Mater
system as nodes in a MasterNet local control network.
MasterPiece 200/1 (MP 200/1) and Advant Controller 400 Series (AC 400S) are the possible
RCOM master stations with Advant Controller 110 (AC 110) and Advant Controller 55
(AC 55) acting as a slave (see Figure 1-1). AC 55 can also be used as RCOM slave of AC 110.
It is possible to use AC 55 as RCOM master of other AC 55 and MasterPiece 40
(see Figure 1-2).
If AC 55 is directly connected to an AC 400 Series station via RCOM as visible in Figure 1-1, it
is possible to perform engineering station functions remotely on the AC 55 using a matching
Advant Engineering Station connected to the AC 400 Series station. AC 400 release >= 1.3 and
AC 55 release >= 1.1 are reqired.
AC 55 of release >= 1.1 is a possible partner of AdvaSoft for Windows which from its release
>= 1.3 is able to communicate via RCOM.
RCOM is also available in an extended version called RCOM+ with safer CRC checksum calcu-
lation. It allows sending of larger data packages and does not use BREAK characters in the mes-
sage, so standard modems can be used. The transmission speed for all versions of RCOM is up
to 9600 bits/s in AC 55.

MP 200/1 Master
AC 400 S.
RCOM

RCOM

• • • • • • • MP 200/1 AC 55
AC 110 AC 55
slaves AC 400 s. slaves

Figure 1-1. Example of an RCOM configuration with AC 55 as RCOM slaves.

3BSE 006 529R0001 Rev A 1-1

RCOM User’s Guide
Chapter 1 Introduction

Master AC 55

RCOM

AC 55 AC 55 • • • • • • • MP 40
Slaves
Slaves

Figure 1-2. Example of an RCOM configuration with AC 55 as RCOM master

In Advant Controller 55 an RCOM and RCOM+ serial interface is built in, available without
additional hard- or software.
For AC 400 please refer to the manual RCOM - Advant Controller 400 Series User’s Guide.
For AC 110 please refer to the manual RCOM - Advant Controller 100 Series User’s Guide.

1.2 Manual Organization

Figure 1-3 shows the basic structure of the Advant System’s various documentations. Each doc-
ument, describing hardware or software, is built around this one structure. The intent of one
structure is to make it possible for you to easily locate related information in any of the docu-
ments.
Chapter

Configuration/ Runtime
Introduction Installation Application Operation Maintenance Index
Building

General Site Planning Design Product Hardware

Information Environment Considerations Operation Indicators
Manual Setup Capacity & Operating Software
Organization Performance Overview Indicators
Modems and
Conventions Cables Application Runtime Error
Start-up Tutorial Report
Related Start-up
Documentation Procedures Tutorial Operating Fault Finding
Instructions & User Repair
Release Product Application
History Verification Procedures Runtime
Operation
Terminology Configuration Menus
of RCOM Section
Equipment Application DB-
Requirements elements and
PC program
Product
Overview

Figure 1-3. Manual organization diagram

1-2 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 1.3 Conventions

Introduction
In Chapter 1, Introduction, this chapter, you will find a description of the RCOM functions in
Advant Controller 55 system layout, hardware requirements, related documents, release history,
terminology and this manuals organization.

Installation
Chapter 2, Installation, tells you how to setup the RCOM communication hardware in the
AC 55. You will also find a description of the shut-down and start-up procedure and how to ver-
ify correct operation after power up.

Configuration and Application Building

Chapter 3, Configuration/Application Building, describes the programming of the process data
base. How to define commands for data exchange and how to store data. The chapter also
describes how to build the PC program for flow control on the communication link. You will
find capacity and performance figures for the communication and an example of an application
program. The configuration of line characteristics and network configuration is described. Dif-
ferent set-up for RCOM and RCOM+ are shown.

Runtime operation
In Chapter 4, Runtime Operation, you will find information of how to check the link status and
how to activate the application for transmission of commands and data.

Maintenance
Chapter 5, Maintenance, gives assistance for error cases.

1.3 Conventions
All input values to data base elements that require user input are boldfaced.

3BSE 006 529R0001 Rev A 1-3

RCOM User’s Guide
Chapter 1 Introduction

1.4 Related Documentation

Refer to the following documents for further information about application building and RCOM
functionality

ABB Master ABB Master ABB Master

Advant Controller 55 RCOM MasterNet System

RCOM RCOM MasterNet Master System

Advant Controller 55 Description of Protocol User’s Guide Installation Rules
User’s Guide
Advant Controller 55 RCOM
User’s Guide AC 400 series
User’s Guide

AMPL Configuration RCOM

Advant Controller 55 AC 100 series
Reference Manual User’s Guide
PC Elements
Advant Controller 55
Reference Manual

Data Base Elements

Advant Controller 55
Reference Manual

Figure 1-4. RCOM and related documentation tree

1.5 Release History

This is the first release.
RCOM is part of the Base Software.

1.6 Terminology
The following conventions and abbreviations are used throughout this document.
• AC is an abbreviation for the ABB Advant Controller Series of Controllers.
AC 55 is the abbreviation for Advant Controller 55.
• AMPL is an abbreviation for the ABB Master Programming Language. AMPL is used for
application programming in AC 55.
• Command MVB is a MVB DB element defining the command used for control of slaves.
The Command MVB’s are only defined in RCOM master mode, except the telephone
commands that also can be used in RCOM slave mode.
• DAT is a concept of the DB-elements that stores a data value (1 Real-, 1 Integer- or
32 Boolean values). The data values of MVB’s are hold by referenced DAT-elements.

1-4 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 1.7 Equipment Requirements

• Data MVB is the MVB DB element used for data transfer. It is used for transfer of block
of data in an ABB Advant network.
In RCOM a Data MVB is a collection of up to 8 or 24 DAT's depending on the RCOM
protocol type.
• DB elements are used for configuring the AC 55.
• EVS (EVent Set) DB elements are used for configuring the flow of events.
• MS is an abbreviation for the Multi Vendor Data Set, used in AC 400 and MP 200 RCOM
implementations. The concept of data transfer and commands is similar to the MVB
concept.
• MVB is an abbreviation for the MVI Data Block. MVB is a special type of Data Sets used
for data transfer and commands in RCOM.
• MVI channel is a channel of the RCOM interface. AC 55 has one channel.
• RCOM is an abbreviation for Remote COMunication in the Advant Controller family.
• RCOM+ is an RCOM protocol type with 24 DAT’s, saver CRC check, no ’Break’.
• PC program (Process Control program) is a program written in AMPL.
• PS refers to ABB Advant Controller Process Station .
• RTU is an abbreviation for Remote Terminal Unit .

1.7 Equipment Requirements

Basic equipment requirement for RCOM in ABB Master Advant Controller 55 are:
• Communication hardware in the AC 55
– The Basic unit CT 481 or CT482 contains the RCOM interface.
• Communication software in the AC 55
– Advant Controller 55 Base SW contains RCOM and event handling.
• Modems and cables
– The modems and cables recommended are listed in the RCOM AC 400 Series User’s
Guide.
General description see Section 2.3, Modems and Cables.
• Engineering tools
– To build the data base and the PC program in the Advant Controller 55 you need:
– Advant Station 100 Series Engineering Station.

3BSE 006 529R0001 Rev A 1-5

RCOM User’s Guide
Chapter 1 Introduction

1.8 Product Overview

RCOM in Advant Controller 55 consist of 2 parts:
• PC program Process Control program written in ABB Master Program Language
(AMPL) is used to define and control the flow of data and commands on the link in slave
mode a PC Program for data flow control is optional.
• Data Base (DB) elements are used to configure the RCOM interface which is built in the
AC 55 basic unit.

AC 55 AC 55

PC program for PC program for

control control
Data flow Data flow
control control
optional in optional in
slave mode slave mode
DB elements for DB elements for
Configuration Configuration

RCOM Interface RCOM Interface

RCOM RCOM
MP 200 MP 40
AC 400 Master Slave
AC 110 AC 55
AC 55 AC 110

Figure 1-5. AC 55 as RCOM Master or RCOM Slave

AC 55 has one RCOM interface built in. It forms a local control network with the network
numbers 1...9. In master mode it can handle up to 25 slaves (nodes). Since every node on the
RCOM link is a part of the local control network, each node must have a unique node number
(1...254) within the control network concerned.

1-6 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 1.8 Product Overview

An example with the Advant Controller 400 series see below.

C
I
5
3
2
AC 400
C
I
5 Series
3
2

Master Master
Modem Modem

Dial-up telephone line

Modem Modem Modem

Modem
C C
I I
AC 110 5
3
AC 110 5
3
MP 40 AC 55 2 2 MP 40 AC 55

Slave Slave Slave Slave Slave Slave

Figure 1-6. Configuration example with Advant Controller 400 series

AC 400 uses CI532V01 as RCOM interface. See RCOM Advant Controller 400 User’s Guide
and please refer to the related documentation of AC 400.

3BSE 006 529R0001 Rev A 1-7

RCOM User’s Guide
Chapter 1 Introduction

An example with the Advant Controller 110 as master see Figure 1-7:

To superior station
MP 200/1 or AC 400 Series
Zoom:

C
Subposition1
Modem
I Channel1
5
3 Channel2
C 2
I
C
Subposition2
AC 110 5
3 I Channel1
2 5
3 Channel2
Master 2

Modem Modem SC610 carrier

Dial-up telephone line

Modem Modem Modem

Modem
C C
I I
AC 110 5
3
AC 110 5
3
MP 40 AC 55 2 2 MP 40 AC 55

Slave Slave Slave Slave Slave Slave

Figure 1-7. Configuration example with Advant Controller 110 as master

AC 110 with RCOM option needs a CI532V01 RCOM submodule. See RCOM Advant Control-
ler 100 Series User’s Guide.
CI532V01 is equipped with two independent, asynchronous communication channels for
RCOM communication (MVI channel). The channels can be configured either as master or
slave on the RCOM link.

1-8 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 1.8 Product Overview

An example with the Advant Controller 55 as master see Figure 1-8:

Master

AC 55

Modem

Modem Modem Modem

C
AC 55 AC 55 I
AC 110 5
3
2
Slave Slave
Slave
Figure 1-8. Configuration example with AC 55 as master

Since AC 55 has only one RCOM interface in the configuration with AC 55 as Master no
superior station can be accessed.
In the following text the RCOM interface is referred to as “MVI channel“although no other
communication protocols than RCOM and RCOM+ are implemented in AC 55.

3BSE 006 529R0001 Rev A 1-9

RCOM User’s Guide
Chapter 1 Introduction

1.8.1 Functionality
Application = Function controlled from the application program.
System = Function controlled directly by the RCOM interface

The following RCOM functions are performed by a MVI channel in master mode:
• Polling of Data MVB’s and system messages from the slaves (System)
• Polling of Event Sets from AC 55 or AC 110 slaves (System)
• Read command to the slaves (Application)
• Write command to the slaves (Application)
• Reset of the sequence marks in the slaves (System)
• Clearing of the event queues in the slaves (System/Application)
• Setting of the clocks in the slaves (System/Application)
• Deblocking of event-driven transmission from the slaves (Application)
• Blocking of the slaves (Application)
• Dialing up the slaves (Application)
• Cold start of the slaves (Application).

The following RCOM functions are performed by a MVI channel in slave mode:
• Reply to the event polling from the master (System/Application)
• Reply to the read commands from the master (System)
• Execution of write commands from the master (System)
• Execution of Event Set writing to AC 55 or AC 110 master (System)
• Resetting of the sequence marks (System)
• Clearing of the event queue (System)
• Status query communications part (RCOM Status Word, RCSW) (System)
• Setting of the clock (System)
• Deblocking event-driven transmission (System)
• Blocking event-driven transmission (System)
• Dialing up the master (System/Application).

1-10 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 1.8.2 Functional Overview

1.8.2 Functional Overview

The application programming required to use RCOM consists of two main parts,
PC program and DB elements, see Figure 1-11.
PC program
The PC program is used for control of the data flow, the status and the commands of the Slave.
In general the commands from master to Slave (see below) are activated from the PC program.
Some commands may be executed automatically (e.g. Clock synchronization with dial-up,
or cyclic data transfer).
If a MVI channel is used as a slave and all data transfer is controlled from the master
no PC program for flow control needs to be used in the slave.
PC program in slave mode is needed if a MVI channel is used with controlled data transfer
to the master. (e.g. data flow control in case of a dial-up slave).
DB elements
The necessary configuration data hardware modules and for the RCOM link is built with special
DB elements.
These DB elements are divided into four parts:
• DB Elements for Configuration
DB elements for Module Configuration (CT481, CT482 in AC 55)
DB elements for Channel Characteristics (Defines transmission speed, time-outs etc.),
DB elements for Node Configuration including Node Status (Defines one node on
the RCOM link and status information for flow control and error indication).
• DB Elements for Commands
Commands used to control slaves when the MVI channel is used in master mode
(cold-start, warm-start, clock synchronization etc.).
• DB Elements for Data Transfer
Handles the actual data transfer. (read, write, polling of data and events)
• DB Elements for Event Handling (optional)
The AC 55 supports the transfer of time-tagged events between a slave and
a superior (master) station.

3BSE 006 529R0001 Rev A 1-11

RCOM User’s Guide
Chapter 1 Introduction

AC 55

User Input PC program

Configuration Status Command Data

Module Channel Node Send Receive

Config. Char. Config. Data +Polling
+ Status Data
+Events
. . .
. . .

. . .
. . .

Master mode MVI channel Slave mode

CHANNEL2

MP 200/1
AC 400
AC 110 Master
AC 55
AC 55 AC 55 AC 110
Slaves
Figure 1-9. Functional overview in the AC 55 acting as master or slave for RCOM networks.

1-12 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 1.8.3 Initiating a Connection

1.8.3 Initiating a Connection

Before start-up the configuration of the MVI channel is entered by the user. The basic unit will
report configuration errors after application download, if the needed configuration is incom-
plete.
If the MVI channel is configured as master it will start to send poll messages on the link when
the configuration is complete and the communication cable is connected to the slave (to the
modem). When the slave sends a response on the poll message the communication link is estab-
lished and ready for data transfer.
The RCOM interface will always restart when the AC 55 is restarted.

1.8.4 Data Transfer and Commands

Transfer Data
Every data transfer is initiated by the master. In master mode the Data is transferred (Send and
Receive) when the link is free for transmission. In slave mode the Data is transferred when the
master sends a poll message. In master mode the MVI channel always sends poll messages
every 50 ms when nothing else is transferred on the link. (e.g. no commands).
Commands
Commands are used for control of the slaves. Commands are only used in RCOM master mode,
except for the telephone commands.
The following commands can be used:
• Cold start
• Warm start/Block
• Normalize/Deblock
• Clock Synchronization
• Dial-up
• Hang-up.

3BSE 006 529R0001 Rev A 1-13

RCOM User’s Guide
Chapter 1 Introduction

1.8.4.1 Data Flow on the RCOM Link

Master Poll Request to Slave (Poll Message)

*
Break Pr A F L S P
Master No data in reply

Slave
Pr A F L S P

Time

Master Poll Request to Slave (Poll Message)

*
Break Pr A F L S P
Master Data in reply

Pr A F L B B Fi Data S P
Slave <32 bytes
-

Time

Commands to Slave (Cold Start, Warm Start/Block, Normalize/Deblock,

and Clock Synchronization)
*Break Pr A F L DATA
1)
S P
Master
Pr A F L DATA1) S P
Slave

Time

Figure 1-10. Data flow on the link during polling and commands

1) Not always included. In case of RCOM+ <100 bytes,

see Section 1.8.4.2, Data Flow on the RCOM+ Link
* Not for RCOM+ (PROTTYPE=2 in DB element MVICHAN)

1-14 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 1.8.4 Data Transfer and Commands

Master Transmitt Data to Slave (Send Data)

* DATA
Break Pr A F L B B Fi <32 bytes
S P
Master

Slave
Pr A F L S P

Time

Master Read Request to Slave (Receive Data)

*
Break Pr A F L B B Fi S P
Master

Slave Pr A F L B B Fi DATA S P
<32 bytes

Time
Figure 1-11. Data flow on the link during read command and data transmission

BREAK(*) Optional: Start element sent by the master to the Slave to synchronize the
communication. Only for RCOM not extended (PROTTYPE=1
in MVICHAN). Character time-out (CHARTOUT parameter in
MVICHAN) is used for synchronization of the communication
in the case of RCOM+ (PROTTYPE=2 in MVICHAN)
Pr: Preamble (HEX 00). Number of Preambles is selected in DB element
MVICHAN.
A: Address = The node number to the slave.
(The slave answers with its own node number.)
F: Function code = Type of telegram.
L: Length code = A unique code identifying the numbers of bytes in the message.
DATA: Data elements.
B B Fi: Identifies the Data elements.
First B = 0
Second B = IDENT (REGADDR in AC 55) on the slave
Fi = Number of DAT’s
S: Checksum (BCC), CRC Check(2 bytes) for RCOM+
P: Postamble (HEX 00)

3BSE 006 529R0001 Rev A 1-15

RCOM User’s Guide
Chapter 1 Introduction

1.8.4.2 Data Flow on the RCOM+ Link

The difference between RCOM and RCOM+ is the Length of the Data part (Maximum 24 DAT
elements and a Time stamp for RCOM+), the type of Checksum (CRC-16 for RCOM+) and
RCOM+ does not start a message with a Break signal (character time-out is used instead.

Master Poll Request to Slave (poll)

Master Pr A F L S S P
Data in reply

Pr A F L B DATA
B Fi <100
Slave bytes S S P
-

Character timeout
Time
Figure 1-12. RCOM+ data flow on the link during polling and data transmission

DATA: Data elements. Maximum 24 DAT elements and a Time stamp.

S: Checksum (CRC-16).

1.8.5 Flow Control

After successful Initialization the master MVI channel automatically starts polling of all slave
nodes that are specified in the DB elements for configuration. If in the reply telegrams data are
received, the AC 55 system automatically writes the data to the internal addresses as configured
in the DB elements. No PC program is needed for that.
Dependent on the chosen application commands can be sent to the slave, initiated by a PC
program. E.g. cold start, warm start, normalization as a single execution at the beginning, clock
synchronization with cyclic execution.
A PC program and the system software supervise the user defined part of the data flow through
the asynchronous port by means of status information automatically received from the MVI
channel.
If the link to the corresponding node is free Send and Receive Data transfers are operated.

1-16 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 2.1 Site Planning Environment

Chapter 2 Installation

2.1 Site Planning Environment

You find guide lines for earth connection, power supply etc. in the manual ABB Master System
Installation Rules. 7650 203-203

2.2 AC 55 Setup
For RCOM the AC 55 basic unit CT 481 or CT482 is equipped with a CCITT V.24 (RS232-C)
asynchronous communication channel CHANNEL 2.
Standard Modems can be connected with standard cables. Modems and cables must be correctly
installed. Figure 2-3 and Figure 2-2 show an example of necessary modems and cables in
RCOM point-to-point and multidrop connections.
The interface is used for RCOM communication with other units in a local control network.
Valid network numbers for a local network are 1 to 9. The AC 55 and every RTU (slave)
connected to RCOM must have a node number 1 to 254 which is unique within the control
network. The setup for each channel is made with the DB element MVICHAN using the AS 100
Series ES Engineering Station.
You don’t have to setup any jumpers or switches for RCOM.
You must check or fill in correct values on the following terminals on the DB elements
MVICHAN (see tables below and figures below).

Table 2-1. Terminals for setup at the DB elements MVICHAN

DB elements
Recommend
where to fill
Terminal ed Description
in
Value
the values
NET MVICHAN (1-9) Own NETwork number of MVI-channel
NODE MVICHAN (1-254) * Own NODE number of MVI-channel

* For usage together with AdvaSoft for Windows only node numbers 1-99 are possible.

3BSE 006 529R0001 Rev A 2-1

RCOM User’s Guide
Chapter 2 Installation

Table 2-2. Description of CI532V01 connections according to CCITT V.24

Direction
No. in 9 Pin No. in 25 Pin
Description Signal CCITT V.24 IN
Connector Connector
OUT
Data Carrier DCD 1 8 109
Detect
Receive Data RD 2 3 104
Transmit Data TD 3 2 103
Data Terminal DTR 4 20 108/2
Ready
Signal Ground SG 5 7 102
Data Set Ready DSR 6 6 107
Request To Send RTS 7 4 105
Clear To Send CTS 8 5 106
Ring Indicator RI 9 22 125

When modems for point-to-point connections are used without control signals the modem cable
must be wired for full duplex handling of modem signals as shown in the Figure 2-1. When
standard modems are used no extra wiring is necessary.

No. in
Description Signal 25 Pin CCITT V.24
Connector
Request To Send RTS 4 105
Clear To Send CTS 5 106
Data Set Ready DSR 6 107
Data Carrier Detect DCD 8 109
Data Terminal Ready DTR 20 108/2

Figure 2-1. Necessary wiring in the cable when a modem without control signals is used.

2-2 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 2.3 Modems and Cables

The following modems and telecontrol cables are recommended, see Table 2-3.

Table 2-3. Modems and telecontrol cable

Version Description
Modems for High speed communication For communication to MP200/1, (1)
9600 bit/s, point to point and multidrop AC 400 series or other AC 110 or 55
Modems for low speed communication CCITT Dito. but longer distances up to 22/
V.23 1200 bit/s, point to point or multidrop 35 km, and/or MasterPiece 40 (2).
Modems for dial-up lines 1200/2400/9600 bit/s 1200 bit/s for MasterPiece 40 (2).
(Hayes-compatible instruction set, direct asyn- For RCOM (not extended)
chronous mode, no break detect).
Telecontrol cable One or two twisted pairs, each pair
Communication cable for RCOM individually shielded.
Conductor diameter up to 0.8(0.6)
(1) See RCOM AC 55 User’s Guide
(2) See MP 40 User’s Guide

2.3 Modems and Cables

Shield 1)
Twisted pairs
Transmitter/ Transmitter/
Receiver Receiver

Slaves parallel
Master connected for Slave
multidrop.
1) Connect shield only at one end (RCOM Master) to avoid loop currents.

Figure 2-2. Cables and modems in a RCOM 2 wire point to point or multi-drop connection

3BSE 006 529R0001 Rev A 2-3

RCOM User’s Guide
Chapter 2 Installation

Channel 2
AC 55
Channe1 1

Modem cable

Modem

Modem

RTU

Modem Modem
Shield 1)
Twisted pairs
Receiver Transmitter

Transmitter Receiver

Shield 1)
1)
Connect shield only at one end (Transmitter) to avoid loop currents.

Figure 2-3. Cables and modems in a RCOM 4 wire full duplex point-to-point connection

2-4 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 2.4 AC 55 Start-up Procedures

2.4 AC 55 Start-up Procedures

To start-up the communication link you must set-up the hardware and the data base elements as
described in Section 2.2, AC 55 Setup.
The RCOM is restarted after power-up, after download of an application and after on-line
changes automatically.
In master mode the RCOM interface sends poll messages every 50 ms automatically when noth-
ing else is transferred on the link. The poll messages can be seen at the modems LED indicators.
(TXD in case of full duplex or TXD and RTS in case of half-duplex)
Check the Error Report. If there are no errors reported the RCOM link should be OK.

2.5 AC 55 Product Verification

The DB element MVICHAN must show the following outputs when the link is connected:
• DSR = 1
• CTS = 1 (full duplex) or toggling between 1and 0 (half duplex)
• DCD= 1 (full duplex) or toggling between 1 and 0 (half duplex)
• CTRLERR= 0
When the link to an RTU is connected and transferring data the following applies for the
terminal STATUS1of the DB element MVINODE for the corresponding slave node:
• Link Status (bit 0) = 1
• Line Status (bit1) = 1 in telephone mode
For more information regarding the RTU Status information, see Section 3.6.1.3, DB Element
for Node Configuration and Status MVINODE.

3BSE 006 529R0001 Rev A 2-5

RCOM User’s Guide
Chapter 2 Installation

2-6 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.1 Design considerations

Chapter 3 Configuration/Application Building

3.1 Design considerations

To be able to setup the DB elements for the Configuration of the RCOM link you must define
the following:
• The network structure.
– Local control network numbers.
– Node numbers for all stations on the RCOM lines.
– Point-to-point, multidrop or dial-up telephone lines.
– The master and the slaves on the line.
• The characteristics for the line.
– Transmission speed.
– Character length, number of stop bits, parity and duplex mode.
– Turnaround time in the RTU (Response time for a message).
Before you build the Command MVB’s and the PC program for the control of the data flow on
the link you have to decide the following:
• How will the data be transferred from slave to master node?
– Master node reads data with a Read Request. See Section 3.6.2.2, Data Transfer from
Slave to Master.
– Master receives data by polling the Slave.
• Is it necessary to set the clock in the slave nodes from the master?
– Clock synchronization is described in Section 3.6.3.4, Clock Synchronization.
• Is it necessary to initiate and block the slaves?
– Cold start, warm start/block and normalize/de-block are described in
Section 3.6.3.1, Cold Start a Slave,
Section 3.6.3.2, Warm Start/Block a Slave,
Section 3.6.3.3, Normalize/Deblock a Slave.
• How will the telephone commands be used?
– Telephone commands are described in Section 3.6.3.5, Telephone Commands.

NOTE
To select the cycle time for the PC program you must know how fast data must be
transferred.

3BSE 006 529R0001 Rev A 3-1

RCOM User’s Guide
Chapter 3 Configuration/Application Building

3.2 Capacity and Performance

3.2.1 Capacity
The RCOM channel is able to handle up to 340 MVB totally. Each MVB may contain up to
8 DAT (7 for event-driven transmission)1. Each DAT element contains 1 real value, 1 integer
(2 or 4 bytes) or 32 booleans. Due to performance and capacity reasons, data which can change
simultaneously should be collected into the same MVB.
RCOM+ can have up to 24 DAT elements referenced by each MVB. (24 DAT’s can also be used
for event driven transmission when RCOM+ is used.)

3.2.2 Total Load on RCOM Link

The total load LR on the RCOM link (in %) can be calculated by following formula:

LR = LR MVB + LR event + LR clock

where
LRMVB = load caused by transmission of MVB elements (in %)
LRevent = load caused by transmission of time-tagged events from Event Sets (in %)
LRclock = load caused by cyclic transmission of clock synchronizations (in %)
The load on the RCOM link must be less than 100%. Otherwise MVBs are transmitted with a
cycle time higher than configured by the terminal CYCLETIM and the transmission of event-
driven MVBs and time-tagged events is partly or fully suppressed.
The maximum performance of an RCOM link can be calculated for different configurations
assuming a total load of 100%. If there are disturbances on the RCOM link the real performance
can be less than the calculated one.
Below the calculation of the load portions is explained. Note that in every equation the values of
the variables are inserted without units.

1. For MP 40: 2 DAT’s for digital values(DI), 6 DAT’s for analog values(AI).

3-2 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.2.2 Total Load on RCOM Link

3.2.2.1 Transmission Time of MVB Elements

The minimum transmission time of one MVB element (in ms) on the RCOM link can be
calculated by following formula:

T MVB = 10000 ⋅(4 ⋅ N + 30 )- +T

--------------------------------------------
S respSlave +T respMaster

where
N = number of DATs in MVB
S = communication speed (bit/s), see terminal SPEED at DB element MVICHAN
T resp = response time of RCOM slave or master (ms), see table below
The response time is the time the operating system needs to generate a telegram after having
received a telegram from the partner node and depends on the communication speed. Table 3-1
contains the minimum response time of an AC 55 RCOM slave or master for every allowed
communication speed. It shows minimum times at small system load. The response time can be
prolonged by high system load or very long pieces of application program. In the AC 55 system
software RCOM’s priority is lower than the priority of executing application program.

Table 3-1. Minimum response time of AC 55 RCOM slave or master

Communication Response time Response time

speed S (bit/s) T respSlave (ms) T respMaster (ms)
150 50 100
300 40 90
600 40 90
1200 20 70
2400 18 68
4800 18 68
9600 15 65

The transmission time of a MVB element is independent from the RCOM command by which
the MVB is transmitted (write command, read command or polling).

3BSE 006 529R0001 Rev A 3-3

RCOM User’s Guide
Chapter 3 Configuration/Application Building

3.2.2.2 Load Caused by MVB Elements

The load of the RCOM link caused by the transmission of MVB elements (by read command,
write command or polling) LR MVB (in %) can be calculated by following formula:

M
T MVB_i
LR MVB = ∑ ----------------- ⋅ 100
C
i = 1 MVB_i

where
M = number of MVB elements
T MVB_i = transmission time of MVB element (ms)
C MVB_i = cycle time of MVB element i (ms), i.e. terminal CYCLETIM multiplied by 100
If a MVB is transmitted in an event-driven way from a slave to the master (using the terminal
EXECUTE) the cycle time from the terminal CYCLETIM can not be applied. In this case the
cycle time C MVB_i can be derived from the average execution number of the MVB by
following formula:

60000-
C MVB_i = ---------------
A exec_i

where
A exec_i = average execution number of MVB i per minute
In Table 3-4 the transmission time and the load for some MVB elements is shown.

Table 3-2. Minimum transmission time and RCOM link load of MVB elements (examples)

Communi- MVB MVB cycle Transmission Load

Number
cation speed terminal time C MVB_ time T MVB_i LR MVB
of DATs
S (bit/s) CYCLETIM (ms) (ms) (%)
1200 1 16 1600 373 23,3
1200 8 128 12800 607 4,8
1200 24 512 51200 1140 2,3
9600 1 16 1600 115 7,2
9600 8 128 12800 145 1,2
9600 24 512 51200 211 0,4

The load L MVB can be reduced by increasing the cycle time (terminal CYCLETIM) of the
MVB elements.

3-4 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.2.2 Total Load on RCOM Link

3.2.2.3 Load Caused by Time-Tagged Events

The load of the RCOM link caused by the transmission of time-tagged events between Event
Sets elements LR event (in %) can be calculated by following formula:
K
500 ⋅( K + 3 )- + 0,5 ⋅ K ⋅
= ------------------------------  ∑ A event_i
LRevent
S
i=1

where
K = number of slave nodes
S = communication speed (bit/s)
A event_i = average number of time-tagged events per minute from slave i
In Table 3-26 the load on the RCOM link caused by time-tagged events in different
configurations is shown as an example.

Table 3-3. RCOM link load caused by time-tagged events (examples)

Communi- Number of events

Number of Load
cation speed per minute and
slaves LRevent (%)
S (bit/s) slave A tt_event_i
1200 4 1 20
2400 4 2 28
9600 8 1 36
9600 16 0,2 29

3.2.2.4 Load Caused by Clock Synchronization

The load of the RCOM link caused by the cyclic transmission of clock synchronization
LR clock (in %) can be calculated by following formula:
( 600000 )
LR clock = ----------------------
S ⋅ C clock

where
S = communication speed (bit/s)
C clock = cycle time of time distribution (s), see terminal PARAM6 at MVICHAN element

3BSE 006 529R0001 Rev A 3-5

RCOM User’s Guide
Chapter 3 Configuration/Application Building

3.2.3 CPU Load From MVI Data Block Communication

The CPU load caused by MVI Data Block communication L MVB (in %) can be calculated by
following formula:
M
L MVB = ∑ 0, 15 + ----------------
C
10 ⋅ N- 

i=1 MVB_i

where
M = number of MVB elements
N = number of DATs in MVB
C MVB_i = cycle time of MVB element i (ms), i.e. terminal CYCLETIM multiplied by 100
The CPU load caused by a MVB element is independent from the RCOM command, the line
characteristics etc. Table 3-4 shows the CPU load for some MVB elements.

Table 3-4. CPU load caused by MVB elements (examples)

MVB MVB cycle

Number of Load L MVB
terminal time C MVB_i
DATs (%)
CYCLETIM (ms)
1 4 400 0,175
8 4 400 0,35
24 4 400 0,75
1 16 1600 0,156
8 128 12800 0,156
24 512 51200 0,155

How to calculate the total CPU load is described in the manual AMPL Configuration Advant
Controller 55 Reference Manual.

3.3 Application Start-up

See Section 2.4, AC 55 Start-up Procedures.

3-6 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.4 Tutorial

3.4 Tutorial
This example describes the necessary application programming for sending DAT’s from a
master node to a slave node and receive DAT’s from the same slave.
The configuration is a dial-up telephone line (one slave).
Configuration on the master node:
• Own node number =5
• Network number =5
• Own telephone number = 1625 (no switchboard)
• Node number =2
• Network number =5
• Telephone number = 1651 (no switchboard).

Configuration on the Modems:

• Transmission speed 9600 bits/s, full duplex
• Direct asynchronous mode
• Hayes without id
• No pause for dial tone after command
• DCD active
• DTR for modem reset.

Node 5 Master

AC 55

Modem Tel. 1625

Network 5

Modem Tel. 1651

Node 2 Slave

AC 55

Figure 3-1. AC 55 Configuration example

3BSE 006 529R0001 Rev A 3-7

RCOM User’s Guide
Chapter 3 Configuration/Application Building

3.4.1 Application in Master Node

3.4.1.1 AC 55 DB Elements in the Master Node

Four Configuration DB elements must be build.Device configuration CT481 or CT482
channel characteristics MVICHAN, Node configuration and node Status MVINODE.
Two Command MVB’s are used - Dial-up and Normalize the slave.
Four Command MVB’s are standard - Cold Start, Warm Start, Dial-up and Normalize the
slave, we only use Dial-up and Normalize. Time synchronization is optional.
Two Data MVB are used for the actual data transfer.One MVB for Sending Data to the slave
(cyclic and PC program initialized) and one MVB for Receiving Data from the slave.

3-8 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.4.1 Application in Master Node

BASIC UNIT
CT1 NAME
0 UNIT-ADR
1 IMPL
CT481______________ TYPE
50 Hz AI GFREQ
CHANNEL1_________ MVI-CHAN

MVICHAN
CHANNEL1 ________ NAME
5 _________________ NET
5 _________________ NODE
1 _________________ MASTER
MASTER__________ TIMESYNC

MVINODE
2 _________________ PROTTYPE
FULL _____________ DUPLEX SLAVE_NODE1_____ NAME
1 _________________ DIAL 1 _________________ ACT
9600 ______________ SPEED 5 _________________ NET
8 _________________ CHLEN 2 _________________ REMNODE
1 _________________ STOPBITS ATDT_____________ DIALSTR1
EVEN_____________ PARITY 1651 ______________ PHONE_NO1
0 _________________ LINESTAB _________________ DIALSTR2
0 _________________ CARRDEL _________________ PHONE_NO2
2 _________________ MAXRETR _________________ DIALSTR3
2 _________________ CHARTOUT _________________ PHONE_NO3
200 _______________ TURNTIME _________________ DIALSTR4
0 _________________ UARTOUT _________________ PHONE_NO4
10 ________________ POLLCYCL

3 (No. of preambles)
. PARAM1 One MVINODE for every remote node on the line
30 (Hang-up time) PARAM2
5 (Disconnect time) PARAM3
3 (Max.no.of polls) PARAM4
3 (Clock set mode) PARAM5
0 (Clock cycle time) PARAM6
2 (Max. no. recalls) PARAM7
10 (Poll data timeout) PARAM8

Figure 3-2. Configuration DB elements and RTU Status DB elements on the master

3BSE 006 529R0001 Rev A 3-9

RCOM User’s Guide
Chapter 3 Configuration/Application Building

Cold Start-MVB Warm Start-MVB

COLD1 ___________ NAME WARM1 __________ NAME

1 _________________ ACT 1 _________________ ACT
1 _________________ REGADDR 1 _________________ REGADDR
301 _______________ CMDCODE 302 _______________ CMDCODE
0 _________________ AUXINFO1 -1_________________ AUXINFO1
0 _________________ AUXINFO2 0 _________________ AUXINFO2
0 _________________ NO_BREC 0 _________________ NO_BREC
0 _________________ NO_INT 0 _________________ NO_INT
0 _________________ NO_INTL 0 _________________ NO_INTL
0 _________________ NO_REAL 0 _________________ NO_REAL
SEND _____________ SOURCE SEND _____________ SOURCE
1 _________________ BLOCKED 1 _________________ BLOCKED
5 _________________ NET 5_________________ NET
2 _________________ REMNODE 2 _________________ REMNODE
0 _________________ CYCLETIM 0 _________________ CYCLETIM
YES ______________ SORT_REF YES_______________ SORT_REF

Normalization-MVB Clock Synch.MVB

NORMALIZE1______ NAME CLOCK1__________ NAME

1 _________________ ACT 1 _________________ ACT
1 _________________ REGADDR 1 _________________ REGADDR
305 _______________ CMDCODE 308 _______________ CMDCODE
-1_________________ AUXINFO1 0 _________________ AUXINFO1
-1_________________ AUXINFO2 0 _________________ AUXINFO2
0 _________________ NO_BREC 0 _________________ NO_BREC
0 _________________ NO_INT 0 _________________ NO_INT
0 _________________ NO_INTL 0 _________________ NO_INTL
0 _________________ NO_REAL 0 _________________ NO_REAL
SEND _____________ SOURCE SEND _____________ SOURCE
1 _________________ BLOCKED 1 _________________ BLOCKED
5 _________________ NET 5 _________________ NET
2 _________________ REMNODE 255 _______________ REMNODE
0 _________________ CYCLETIM 0 _________________ CYCLETIM
YES ______________ SORT_REF YES ______________ SORT_REF

Figure 3-3. Command MVB DB elements on the master

3-10 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.4.1 Application in Master Node

DIAL-UP MVB HANG-UP MVB

DIAL1_____________ NAME HANGUP1_________ NAME

1 _________________ ACT 1 _________________ ACT
1 _________________ REGADDR 1 _________________ REGADDR
3 _________________ CMDCODE 4 _________________ CMDCODE
0 _________________ AUXINFO1 0 _________________ AUXINFO1
0 _________________ AUXINFO2 0 _________________ AUXINFO2
0 _________________ NO_BREC 0 _________________ NO_BREC
0 _________________ NO_INT 0 _________________ NO_INT
0 _________________ NO_INTL 0 _________________ NO_INTL
0 _________________ NO_REAL 0 _________________ NO_REAL
SEND _____________ SOURCE SEND _____________ SOURCE
1 _________________ BLOCKED 1 _________________ BLOCKED
5 _________________ NET 5 _________________ NET
2 _________________ REMNODE 2 _________________ REMNODE
0 _________________ CYCLETIM 0 _________________ CYCLETIM
YES ______________ SORT_REF YES ______________ SORT_REF

READ MVB WRITE MVB

READ1____________ NAME WRITE1 __________ NAME

1 _________________ ACT 1 _________________ ACT
1 _________________ REGADDR 2 _________________ REGADDR
110 _______________ CMDCODE 210 _______________ CMDCODE
0 _________________ AUXINFO1 0 _________________ AUXINFO1
0 _________________ AUXINFO2 0 _________________ AUXINFO2
0 _________________ NO_BREC 2 _________________ NO_BREC
0 _________________ NO_INT 4 _________________ NO_INT
4 _________________ NO_INTL 0 _________________ NO_INTL
0 _________________ NO_REAL 0 _________________ NO_REAL
RECEIVE__________ SOURCE SEND _____________ SOURCE
0 _________________ BLOCKED 1 _________________ BLOCKED
5 _________________ NET 5 _________________ NET
2 _________________ REMNODE 2 _________________ REMNODE
0 _________________ CYCLETIM 8 _________________ CYCLETIM
YES ______________ SORT_REF YES ______________ SORT_REF

Figure 3-4. Command MVB DB elements on the master

3BSE 006 529R0001 Rev A 3-11

RCOM User’s Guide
Chapter 3 Configuration/Application Building

3.4.1.2 The PC Program in the Master Node

.

CONV-IB
CONTRM
D=1 S ERR
D=0 >L SIGN
D=0 R ZERO
SLAVE_NODE1:STATUS1 I O1 STATUS1:LINK
O2 STATUS1:LINE
O3 DIALING-UP
....

RUN & DIAL1:EXECUTE

CHANNEL1:DCD
DIALING-UP

STATUS1:LINK &
STATUS1:LINE

NORMALIZE1:ERR &
NORMALIZE1:EXECDONE
OR & NORMALIZE1:EXECUTE
D=0 S
D=1 D
>C
R

READ1:ERR &
READ1:EXECDONE
OR & READ1:EXECUTE
D=0 S
D=1 D
>C
R

OR WRITE1:BLOCKED
S
R

Figure 3-5. PC program for telephone command, normalizing the slave and sending data

3-12 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.4.2 Application in Slave Node

3.4.2 Application in Slave Node

3.4.2.1 DB Elements in the Slave Node

Four Configuration DB elements must be built in the Slave node SC610 and CI532
configuration, channel characteristics MVICHAN, node configuration and Status MVINODE.
No Command MVB’s are used.
Two Data MVB’s are used for the actual data transfer:
• One for Sending Data to the master
• one for Receiving Data from the master.

READ MVB WRITE MVB

READ1 ___________ NAME WRITE1 __________ NAME

1 _________________ ACT 1 _________________ ACT
2 _________________ REGADDR 1 _________________ REGADDR
110 _______________ CMDCODE 210 _______________ CMDCODE
0 _________________ AUXINFO1 0 _________________ AUXINFO1
0 _________________ AUXINFO2 0 _________________ AUXINFO2
2 _________________ NO_BREC 1 _________________ NO_BREC
4 _________________ NO_INT 0 _________________ NO_INT
0 _________________ NO_INTL 0 _________________ NO_INTL
0 _________________ NO_REAL 0 _________________ NO_REAL
RECEIVE__________ SOURCE SEND _____________ SOURCE
0 _________________ BLOCKED 1 _________________ BLOCKED
5 _________________ NET 5 _________________ NET
5 _________________ REMNODE 5 _________________ REMNODE
8 _________________ CYCLETIM 32 ________________ CYCLETIM
YES_______________ SORT_REF YES ______________ SORT_REF

Figure 3-6. Data MVB’s on the slave

3BSE 006 529R0001 Rev A 3-13

RCOM User’s Guide
Chapter 3 Configuration/Application Building

BASIC UNIT

CT1 ______________ NAME

0_________________ UNIT-ADR
1_________________ IMPL
CT481____________ TYPE
50 Hz _____________ AI-GFREQ
CHANNEL1 _______ MVI-CHAN

MVICHAN
CHANNEL1 _______ NAME
5 _________________ NET
2 _________________ NODE
0 _________________ MASTER
SLAVE____________ TIMESYNC
MVINODE

2 _________________ PROTTYPE MASTER_NODE___ NAME

FULL_____________ 1 _________________ ACT
DUPLEX
1 _________________ 5 _________________ NET
DIAL
9600 ______________ 5_________________ REMNODE
SPEED
ATDT_____________ DIALSTR1
8 _________________ CHLEN
1 _________________ STOPBITS 1625 ______________ PHONE_NO1
EVEN_____________ PARITY _________________ DIALSTR2
0 _________________ LINESTAB _________________ PHONE_NO2
0 _________________ CARRDEL _________________ DIALSTR3
0 _________________ MAXRETR _________________ PHONE_NO3
CHARTOUT _________________ DIALSTR4
2 _________________
TURNTIME _________________ PHONE_NO4
200 _______________
0 _________________ UARTOUT
10 ________________ POLLCYCL

3 (No. of preambles) PARAM1

30 (Hang-up.time) PARAM2 One MVINODE for the remote master node
5 (Disconnect time) PARAM3
0 (Max.no.of polls) PARAM4
0 (Clock set mode) PARAM5
3600(Clock cycle time) PARAM6
2 (Max. no. recalls) PARAM7
0 (Poll data timeout) PARAM8

Figure 3-7. Configuration and RCOM status DB elements on the slave

3-14 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.4.2 Application in Slave Node

3.4.2.2 PC Program in the Slave Node

CONTRM CONV-IB
D=1 S ERR
D=0 >L SIGN
D=0 R ZERO
MASTER_NODE1:STATUS1 I O1 STATUS1:LINK
O2 STATUS1:LINE

D=0 S
DI1.1 D =1 &
>C
D=0 R

STATUS1:LINK
STATUS1:LINE

WRITE1:ERR &
WRITE1:EXECDONE

& WRITE1:EXECUTE
S
R

MOVE
(B,1) DAT1/WRITE1.B1

Figure 3-8. PC program for event driven transmission of digital input data to the master node

3BSE 006 529R0001 Rev A 3-15

RCOM User’s Guide
Chapter 3 Configuration/Application Building

3.5 Application Procedures

Configuration
The configuration of the basic unit CT 481 or CT 482, of the MVI channel, line and nodes is
built with special DB elements.
DB elements for Configuration
DB element for configuration of the AC 55 Basic Unit ’CT 481’ or ’CT 482’. The DB Elements
are described in Section 3.6.1.1, DBElements for MVI Module Configuration CT481, CT482
DB elements for Channel Characteristics of the MVI channels ’MVICHAN’ (Defines
transmission speed, time-outs etc.), The DB Element MVICHAN is described in
Section 3.6.1.2, DB Element for MVI Channel Characteristics MVICHAN.
DB elements for Node Configuration ’MVINODE’ (defines one node on the RCOM link and
the node status with information for flow control and error indication). The DB Element
MVINODE is described in Section 3.6.1.3, DB Element for Node Configuration and Status
MVINODE.
The DB Elements for configuration of the carrier module and the MVI device and channel
characteristics and node configuration must always be defined.
If they are not built at start-up of the MVI channel, application errors will be reported.

Application building
DB elements for Commands
The ’MVB’ DB elements are used for commands to control slaves when the MVI channel is
used in master mode and for the dial-up/hang-up (telephone) command. The DB Element MVB
is described in Section 3.6.3, DB Element MVB for Commands.
DB elements for Data
The ’MVB’ DB elements handle the actual data transfer (read, write, polled data/ MP 40-events
in master and slave mode). The DB Element MVB for data transfer is described in
Section 3.6.2, DB Element MVB for Data Transfer.
PC program
The PC program controls the commands and controls and checks the data flow through the
asynchronous port by means of the status information received from the MVI channel.
The PC program activates the execution of Command MVB and the Data MVB
(see Figure 3-9). The PC program is described in Section 3.6.4, PC Program Layout.

3-16 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.5.1 Master Functions

The application programming required to use RCOM consists of two main parts, PC program
and DB elements see figure below.

User Input PC program

Configuration Status Command Data

Module Channel Node Send Receive

Config. Char. Config. Data +Polling
+ Status Data
CT481, CT482 MVICHAN MVINODE MVB..MVB MVB...MVB +Events
.. .. ..

.. .. ..

MVI channel

Figure 3-9. Overview of the application for RCOM

3.5.1 Master Functions

The functions mentioned below can be defined/controlled at application level in master mode:
• Data (event) polling of MVB from the slaves.
See Section 3.6.2.2, Data Transfer from Slave to Master for further information.
• Writing of MVB to the slaves.
See Section 3.6.2.1, Data Transfer from Master to Slave for further information.
• Reading of MVB from the slaves.
See Section 3.6.2.2, Data Transfer from Slave to Master for further information.
• Cold start of the slaves.
See Section 3.6.3.1, Cold Start a Slave for further information.
• Warm start/blocking of the slaves.

3BSE 006 529R0001 Rev A 3-17

RCOM User’s Guide
Chapter 3 Configuration/Application Building

See Section 3.6.3.2, Warm Start/Block a Slave for further information.

• Normalization/deblocking of the slaves.
See Section 3.6.3.3, Normalize/Deblock a Slave for further information.
• Setting the clocks in the slaves.
See Section 3.6.3.4, Clock Synchronization for further information.
• Dialling-up of the slaves.
See Section 3.6.3.5, Telephone Commands for further information.

3.5.2 Slave Functions

The functions mentioned below can be defined/controlled at application level in slave mode:
• Reception of MVB from the master
See Section 3.6.2.1, Data Transfer from Master to Slave for further information.
• Transmission of MVB to the master (read by the master).
See Section 3.6.2.2, Data Transfer from Slave to Master for further information.
• Transmission of polled MVB to the master
See Section 3.6.2.2, Data Transfer from Slave to Master for further information.
• Dialling-up of the master.
See Section 3.6.3.5, Telephone Commands for further information.

3-18 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.6 Configuration of RCOM Application DB Elements and PC Program

3.6 Configuration of RCOM Application DB Elements and PC Program

3.6.1 DB Elements for RCOM Configuration

This chapter describes the configuration DB elements, used to configure the CT481, CT482
basic units and the MVI channel. These DB elements contain setup information for the
hardware and software. The Status information received from the MVI channel can be used by
the application program for control.
In an AC 55 one RCOM+ communication channel is included.
In the figure below the hierarchy of these DB elements is shown.

CT481/CT482
reference

MVICHAN

same net number

- up to 25 DB elements MVINODE
for remote nodes at the channel
MVINODE

same net number

same remote
node number
- up to 340 DB elements MVB
for commands and data transfer
MVB

Figure 3-10. Hierarchy of DB elements in AC 55

3BSE 006 529R0001 Rev A 3-19

RCOM User’s Guide
Chapter 3 Configuration/Application Building

3.6.1.1 DBElements for MVI Module Configuration CT481, CT482

The DB element CT481/CT482 represents an AC 55 basic unit CT481 or CT482. See AC 55
Technical Description and DB Elements Manual. The built in MVI channel is referenced by the
(REF) terminal MVI_CHAN referencing to the terminal name of a DB element MVICHAN.
Call name: CT481 or CT 482
Element type: Basic unit
Item designation: CTx

CT481

CT1 NAME ERR

0 UNIT_ADR PVOLTERR
1 IMPL CHECKERR
CT481 TYPE
50 Hz AI_GRFREQ
MVC1 MVI_CHAN

Figure 3-11. Example of a DB element CT481

Table 3-5. Description of the DB element CT481

Allowed Recommended
Terminal Description
Values Value
NAME max. 20 characters CTx Unique module NAME
UNIT_ADR 0 0 UNIT_ADDRess number.
IMPL 0,1 1 IMPLemented
0 = the element is spare
1 = the module is implemented
TYPE CT481,CT482 CT481,CT482 module TYPE
SC610
AI_GFREQ 50 Hz, 60 Hz 50 Hz, 60 Hz Analog Input GRID FREQuency
MVI_CHAN max. 20 characters MVC1 REF of DB element MVICHAN defining MVI CHANNEL
ERR ERRor
PVOLTERR Process Voltage ERRor (DI or AI)
CHECKERR CHECKsum ERRor

3-20 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.6.1 DB Elements for RCOM Configuration

3.6.1.2 DB Element for MVI Channel Characteristics MVICHAN

The channel characteristics of MVI channel are specified in one MVICHAN DB element.
DB element MVICHAN
The DB element MVICHAN specifies the configuration of a MVI channel and access of status
of modem control signals.
Configuration of:
• Master or slave mode.
• Protocol type RCOM or RCOM+.
• Standard communication parameters (speed, no. of bits, parity, duplex mode, timing etc.).
• RCOM specific communication parameters (No. of retransmissions, time-outs etc.).
• Automatic control of slaves.
Status indication of modem control signals, errors.
The layout of the DB element MVICHAN is shown in Figure 3-12.

3BSE 006 529R0001 Rev A 3-21

RCOM User’s Guide
Chapter 3 Configuration/Application Building

MVI channel MVICHAN

______________________________________________________________________________________________________
Call name: MVICHAN
Element type: MVI channel
Item designation: MVCx
______________________________________________________________________________________________________
Base part
MVC1 NAME
1 NET
1 NODE
0 MASTER
SLAVE TIMESYNC

Communication

1 PROTTYPE CTRLERR
FULL DUPLEX
0 DIAL DSR
2400 SPEED DCD
8 CHLEN CTS
1 STOPBITS RI
EVEN PARITY
2 LINESTAB
1 CARRDEL
2 MAXRETR
2 CHARTOUT
80 TURNTIME
1 UARTOUT
80 POLLCYCL

Parameters

PARAM1
PARAM2
PARAM3
PARAM4
PARAM5
PARAM6
PARAM7
PARAM8

Figure 3-12. Example of a DB element MVICHAN

3-22 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.6.1 DB Elements for RCOM Configuration

Terminals Base Part of the DB element MVICHAN

Table 3-6. Description of the DB element MVICHAN, base part

Allowed Recommended
Terminal Description
Values Value
NAME max. 20 characters MVC1 Unique module NAME
NET 1-9 Own NETwork number of MVI-channel
NET number is unique in the control network. The on-line
change is denied for this terminal.
NODE 1-254 Own NODE number of MVI-channel. If AC 55 is used
together with AdvaSoft for Windows only node numbers 1-99
are possible. The on-line change is denied for this terminal.
MASTER 0/1 MVI channel in
1 = MASTER mode
0 = slave mode
TIMESYNC NONE MASTER MVI TIME SYNChronization
MASTER SLAVE In MVI master mode (terminal MASTER=1)
SLAVE MASTER = time synchronization according to PARAM5.
In MVI slave mode (terminal MASTER=0)
SLAVE = time synchronization slave
NONE = no time synchronization.
ERR ERRor
0=no error
1=channel error ERR is always 0 in AC 55.
The terminal ERR is available for compatibility reasons with
AC 100 Series.

Terminals Communication part of the DB element MVICHAN

Table 3-7. Description of the DB element MVICHAN, communication part

Allowed Recommended
Terminal Description
Value Value
PROTTYPE 1/2 2 PROTocol TYPE
(1 with MP 40 or 1 = RCOM. RCOM with ’break’, max 8 DAT’s
MP 200/1) 2 = RCOM+. RCOM without ’break’, max. 24 DAT’s

DUPLEX FULL or HALF, FULL or HALF DUPLEX (concerns modem signals between MVI and the
HALF (DCD modem)
IGNORED) (FULL, HALF, HALF (DCD IGNORED))
For dial-up lines only full duplex is supported.
Half duplex is provided for multi-drop or 2-wire private lines

3BSE 006 529R0001 Rev A 3-23

RCOM User’s Guide
Chapter 3 Configuration/Application Building

Table 3-7. Description of the DB element MVICHAN, communication part (Continued)

Allowed Recommended
Terminal Description
Value Value
DIAL 0/1 0 or 1 DIALing
1= enabled. For dial-up lines
0= disabled. For dedicated lines (private/leased)
SPEED 150, 300, 600, 1200/9600 Transmission SPEED of communication in bits/s
1200, 2400, 4800, 150, 300, 600, 1200, 2400, 4800 or 9600
or 9600 (1200= standard for MP 40 slaves)
CHLEN 7-8 8 CHaracter LENgth in bits, must be 8 for RCOM
STOPBITS 1, 1.5, 2 1 STOP BITS
PARITY NONE, ODD, ODD PARITY (ODD= standard for MP 40 slaves)
EVEN (NONE, ODD, EVEN)
LINESTAB 0-15 2 for half duplex LINE STABilization time. (Pre idle time)
1 for full duplex The number of characters times to allow the carrier wave to
stabilize before transmission of the first character. If half
duplex is used, a check of DCD will be made by the send rou-
tine before activating RTS. If DCD is activated, in half duplex
mode a delay up to this number of characters or until DCD is
deactivated will be made.
Restrictions: Own pre idle time >= (opposite side) post idle
time. See also figure below.
For PROTTYPE = 1 and DIAL = 1 LINESTAB = 6 is
recommended.
CARRDEL 0-15 1 for half duplex CARRier DELay (Post idle time)
0 for full duplex Number of characters to wait after the transmission of the last
character before deactivating RTS. This delay is used to avoid
destruction of the last character in the message, due to lost car-
rier.
See also figure below.
MAXRETR 0-20 2 MAXimum number or RETRansmissions
4 with MP 40 before line is considered broken
CHARTOUT 0-15 2 CHARacter Time-OUT (in number of characters)

3-24 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.6.1 DB Elements for RCOM Configuration

Table 3-7. Description of the DB element MVICHAN, communication part (Continued)

Allowed Recommended
Terminal Description
Value Value
TURNTIME 10-20000 ms in >= 200ms * TURNaround TIME. Time in ms to wait as from the last
steps of 10 ms 9600/SPEED character in the command until the first character in the reply
i.e. the time-out time, the master waits for a response from the
slave.
Note that this time is dependent on the pre idle time and post
idle time in the slave and must be adjusted accordingly.
You must also include delays that may occur in the slave units.
See also Figure 3-14.
Since in AC 55 the same microprocessor serves for RCOM
and execution of application program, RCOM may be delayed
if the application produces high system load or application
programs are very big. If so the delay time has to be consid-
ered in the RCOM partner’s TURNTIME.
UARTTOUT 0-15 0 Not used in AC 55

POLLCYCL 0-255 s 96000/SPEED maximum time between two POLLing CYCLes in seconds.
CTRLERR B(r) Indicating any ERRors in the modem ConTRoL signals
CTS, DCD, DSR, RI
DSR B(r) modem signal "Data Set Ready" (DSR)
DCD B(r) modem signal "Data Carrier Detect" (DCD)
CTS B(r) modem signal "Clear To Send" (CTS)
RI B(r) modem signal "Ring Indicator" (RI)

3BSE 006 529R0001 Rev A 3-25

RCOM User’s Guide
Chapter 3 Configuration/Application Building

Terminals Parameter part of the DB element MVICHAN

Table 3-8. Description of the DB element MVICHAN, parameter part

Allowed Recommended
Terminal Description
Values Value
PARAM1 - PARAM8 are protocol dependent parameters.
PARAM1 1-15 1 for multidrop No. of preambles.
and point to point See Section describing Data Flow on the RCOM Link.
3 for dial-up lines
PARAM2 10s-200 s 30 s Hang-up time for dial-up lines.
Time in seconds before hang-up in case no data is transmitted.
This time is also used for dial-up waiting for answer.
PARAM3 1-100 s 5s Disconnect time for dial-up lines. Hang-up time in seconds.
The time DTR is deactivated during hang-up
PARAM4 -1 - (IL) 3, (-1) Max. no. of polls per cycle and slave. Is set to -1 if polling
until the event queue in the slave (MP 40) is empty is desired.
PARAM5 0-4 2 for private lines Clock setting mode (used only for MASTER=1
3 for dial-up lines 0 = clock synchronization only on execute command from
0,1,3,4 for MP 40 application (Clock synchronization command)
1 = cyclic clock synchronization
Cycle time specified in PARAM6. Only for private lines.
2 = cyclic clock synch. and after restart of a slave node.
Cycle time specified in PARAM6. Only for private lines.
3 = clock synchronization after connect of a dial-up line.
4 = clock synchronization before hang-up of a dial-up line.
PARAM6 0-100000s 120s or less. Protocol dependent parameter for RCOM:
Master mode:
In case of clock setting modes (PARAM 5) 1 and 2:
Cycle time of clock setting.
Slave mode:
Interval between time synchronization from master.
PARAM7 0-12 2 Max. no. of recalls before trying with next phone number.
Depends on national Post requirements.Limit for German Post
12 recalls with delay 60 s (PARAM3)between the dial tries.
or 2 recalls with delay 5 s (PARAM3). Some modems are
allowed to have unlimited recalls with delay 30 s (PARAM3).
PARAM8 0-100000s 10s Poll data reception time-out in seconds only for MASTER=1.
Used for hang-up in master. This time-out relates to bit 14 in
the RTU status 1

Some recommendations for using the half duplex mode

3-26 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.6.1 DB Elements for RCOM Configuration

LINESTAB (pre idle time)

The number of characters to allow the carrier wave to stabilize before transmission. If half
duplex is used, a check of DCD will be made by the send routine before activating RTS. If DCD
is activated, a delay up to this number of characters or until DCD is deactivated will be made.
This delay will also always be made in half duplex mode, before the message is transmitted,
after the activation of RTS.
Restrictions:
(own) pre idle time >= (opposite side) post idle time.
CARRDEL (post idle time)
Number of characters to wait after transmission of the last character before deactivating RTS.
This delay is used to avoid destruction of the last character in the message, due to lost
carrier.

DCD =
Data Carrier Detect

RTS =
Request To Send

Carrier

CTS =
Clear To Send
Data

Wait max. LINSTAB Pre idle time(LINSTAB) Post idle time(CARRDEL)

time until DCD input
signal goes low
Figure 3-13. Line stabilization time and carrier delay in AC 55

TURNTIME Adjustment:
Time in milliseconds to wait as from the last character in the command until the first character
in the reply i.e. the time-out time, the master waits for a response from the slave. This time is
dependent on the times defined in the slave and must be adjusted accordingly. You must also
include delays that may occur in the slave units.

Message from master T1

Master Slave
Answer from slave
T2
Turnaround time = T2 - T1
Figure 3-14. Turnaround time.

3BSE 006 529R0001 Rev A 3-27

RCOM User’s Guide
Chapter 3 Configuration/Application Building

3.6.1.3 DB Element for Node Configuration and Status MVINODE

Each slave node included into a MVI network link is represented by a DB element
MVINODE on the master. On the slave the master node number must be defined.
One DB element MVINODE specifies for a MVI channel configured:
• in master mode
– one slave node connected to the MVI channel
– the status words 1-3 for this slave node
– one phone number and one dial string for this slave node (optional).
• in slave mode
– node number of the master node
– the own status in status word 1
– up to 4 phone numbers and dial strings for the master(optional).
The phone numbers are used only when the master and the slaves are connected via dial-up
lines. In this case at the corresponding MVICHAN the DIAL terminal must be 1.
At the slave the master phone number is used in case of alarm to dial-up the master.
For redundancy up to 4 phone numbers for the master can be specified.
The layout of the DB element MVINODE is shown in Figure 3-15:

DB Element MVINODE
Call name: MVINODE
Element type: MVINODE
Item designation: MVNx
_

MVNx

MVN1 NAME STATUS1

1 ACT STATUS2
1 NET STATUS3
1 REMNODE ERR
DIALSTR1
PHONENO1
DIALSTR2
PHONENO2
DIALSTR3
PHONENO3
DIALSTR4
PHONENO4

Figure 3-15. Example of a DB element MVINODE

3-28 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.6.1 DB Elements for RCOM Configuration

The Terminals of the DB element MVINODE are explained in the table below.

Table 3-9. Description of the DB element MVINODE

Allowed Recommended
Terminal Description
Values Value
NAME max. 20 characters MVNx Unique module NAME
ACT 0/1 1 The DB element is ACTIVE
0 = The element is spare.
1 = The element is active.
REMNODE (1-254) 1 REMote NODE number
in master mode: node number of slave
in slave mode: node number of master
NET (1-9) 1 NETwork number of remote node
DIALSTR1 max. 20 characters ATDT or ATDP DIAL STRing 1 for modem (Hayes commands)
e.g. ATDT = Tone dialling
ATDP = Pulse dialling
PHONENO1 max. 20 characters PHONE number 1 (max. 20 characters) for
remote node master/slave including area number and
including Hayes commands for wait for dial tones etc.
DIALSTR2 max. 20 characters ATDT or ATDP DIAL STRing2 for modem (max. 20 characters) (see above)
PHONENO2 max. 20 characters PHONE number2 for remote node master/slave (see above)
including area number
DIALSTR3 max. 20 characters ATDT or ATDP DIAL STRing3 for modem (max. 20 characters) (see above)
PHONENO3 max. 20 characters PHONE number3 for remote node master/slave (see above)
including area number
DIALSTR4 max. 20 characters ATDT or ATDP DIAL STRing4 for modem (max. 20 characters) (see above)
PHONENO4 max. 20 characters PHONE number4 for remote node master/slave (see above)
including area number
STATUS1 IL(r) MVI STATUS word 1 (RCOM)Status of the remote node
STATUS2 IL(r) MVI STATUS word 2 (RCOM)Status of the remote node
STATUS3 IL(r) MVI STATUS word 3 (RCOM)Status of the remote node
ERR B(r) ERRor. ERR is always 0 in AC 55.

3BSE 006 529R0001 Rev A 3-29

RCOM User’s Guide
Chapter 3 Configuration/Application Building

MVI STATUS 1, 2 and 3 (RTU STATUS)

The status of every RCOM slave (RTU) is accessible by a PC program at the terminals
STATUS1, STATUS2, STATUS3 of the corresponding MVINODE.
The status information is used for error indication, supervision and exception handling in PC
programs. Status information can be used for enabling flow control (e.g. in case of dial-up lines)
besides error indication and supervision.
Examples: LINK STATUS is used for supervision of connection of nodes via private lines
LINE STATUS is used for supervision of dial-up lines
CALL FAILED is used for supervision of the establishing of dial-up lines
POLLING BLOCKED for supervision of data (event) polling.
... etc. see Table 3-10.
The status words are of format IL (integer long). The 32 bit values are extracted using a
CONV-IB PC element in the PC program. (See figure below).

CONV-IB
(IL,1,32)
D=1 S ERR
D=0 >L SIGN
D=0 R ZERO
MVNn:STATUS1/2 I O1 Status bit 0
O2 Status bit 1
O3 Status bit 2
O4 Status bit 3
O5 Status bit 4
O6 Status bit 5
O7 Status bit 6
...
...

...
O32 Status bit 31

Figure 3-16. Example of a PC element CONV-IB used to get RTU status values.

Status1
Contains information required for supervision and flow control among other things.
When AC 55 operates in master mode, the status 1 bits 16-31 describe the RCSW (RCOM
Status Word) of the corresponding slave node. When AC 55 operates in slave mode,
the bits 16-31 describe the own RCSW. (RTU corresponds to remote slave node.)

3-30 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.6.1 DB Elements for RCOM Configuration

Table 3-10. Status1 Supervision and flow control

Status1 Description Valid modes

Bit 0 Link status Slave and Master
The corresponding RTU reachable, see Figure 3-14.
Set to ‘1’ when the remote node is reachable, i.e. when the first correct telegram
from the remote node has arrived,
Set to ’0’ when the remote node is not reachable, i.e. when the telegram inclusive
retries failed.
The Link status is normally not set to ‘0’ when the telephone line is disconnected
with the Telephone command (See line status below). The master considers the
contact lost after max number of retransmissions of a signal without an answer.
The slave node considers the contact lost when the times between messages from the
master exceed the poll cycle time.
Bit 1 Line status Slave and Master (only in
Set to ‘1’ when the telephone line is connected. telephone mode)
Set to ‘0’ when the telephone line is disconnected
(also when ‘Link status’ is set to ‘0’).
Bit 2 Dialling-up is performed Slave and Master
Set to ‘1’ when dial-up is performed.
Set to ‘0’ when telephone line is up or when node fails to dial up the opposite node.
See bit 13.
Bit 3 Illegal MS number received Slave and Master
Set to ‘1’ when illegal MVB REGADDR is received from an RTU.
Set to ‘0’ when receiving a valid MVB.
Bit 4 Illegal function code received Slave and Master
Set to ‘1’ when illegal functions code is received from an RTU.
Set to ‘0’ when receiving valid MVB
Bit 5 Ready for Message Slave and Master
Set to ‘1’ when no command is pending, from the application to the RTU.
Set to ‘0’ when a command is pending, from the application to the RTU.
Bit 6 Started Slave and Master
Set to ‘1’ when the own node has started.
Set to ‘0’ in a slave node after transmission of system message ‘Restarted’ to the
master. Always set to ‘1’ after start-up in a master node.
Bit 7 Time in Status 3 is valid Master
Set to ‘1’ when a poll answer with time stamped event from a slave node is received.
Set to ‘0’ at restart of the AC 55 basic unit.
Bit 8 Application part not ready in the slave node Master
Set to ‘1’ when master receives an answer with the function code ‘Application part
not ready’, i.e., MVB not built in slave node, slave not Normalized, etc.
Set to ‘0’ when master receives a valid answer from the slave node.

3BSE 006 529R0001 Rev A 3-31

RCOM User’s Guide
Chapter 3 Configuration/Application Building

Table 3-10. Status1 (Continued)Supervision and flow control (Continued)

Status1 Description Valid modes

Bit 9 Uncertain time Master
Set to ‘1’ when master receives a time-stamped event (poll answer) with the function
code for Uncertain time. The function code is normally not set in a slave node.
Set to ‘0’ when master receives a time-stamped event without this function code.
Bit 10 Unknown system message Master
Set to ‘1’ when the master receives a system message that cannot be mapped to
Status2 (code <0 or >31).
Set to ‘0’ at restart of the link.
See Status2 below for description of valid system messages.
Bit 11 Poll time-out Slave and Master (not in
Set to ‘1’ when the poll supervision timer expires, i.e., the master is unable to send a telephone mode)
poll request message to slave node within the specified time-out time. This is caused
by too many command MVB’s. The slave node also resets link status bit when the
poll supervision expires.
Set to ‘0’ when polling is performed.
Bit 12 Not used Slave and Master(DIAL=0
PARAM5 =1,2)
Bit 13 Call failed (dial-up) Slave and Master (only in
Set to ‘1’ when node fails to dial up the opposite node. telephone mode)
Set to ‘0’ when the dial-up is successful.
Bit 14 Poll data reception time-out Master (only in telephone
Set to ‘1’ if no MVB is received by polling within the time-out specified by mode)
PARAM8 at DB element MVICHAN.
Set to ‘0’ when a MVB is received by polling without time-out.
Bit 15 Not used
Bit 16 Not used
Bit 17 Not used
Bit 18 Watch dog alarm Not used
Set to ‘1’ when the watchdog alarm is set.
Set to ‘0’ when the node receives Cold Start or Warm Start.
Bit 19 Illegal command Not used
Bit 20 Not used Not used
Bit 21 Not used Not used
Bit 22 Not used Not used
Bit 23 Not used Not used
Bit 24 Not used Not used

3-32 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.6.1 DB Elements for RCOM Configuration

Table 3-10. Status1 (Continued)Supervision and flow control (Continued)

Status1 Description Valid modes

Bit 25 Sequence mark, read Slave and Master (See
note below)
Bit 26 Sequence mark, write Slave and Master (See
note below)
Bit 27 Polling blocked Slave and Master (See
Set to ‘1’ when the slave node must receive a Normalization command note below)
Set to ‘0’ when the user part in the slave node is Normalized
Bit 28 Not used Not used
Bit 29 Not used Not used
Bit 30 Not used Not used
Bit 31 Not used Not used

NOTE
Status 1 bits 16-31 describe the RCSW (RCOM Status Word) of the
corresponding slave node. When the MVI channel operates in slave mode,
the bits 16-31 describe the own status RCSW.

Status2:
Contains information on system messages from the slave when AC 55 is the master.
Status2 is reset at Cold Start, Warm Start and Normalization.

Table 3-11. Status2 System messages from the slave

Status2 Description Valid modes

Bit 0 Slave node restarted Master
Bit 1 I/O unit error Master.
Received only from
MP 40.
Bit 2 Check sum error, application Master.
Bit 3 Check sum error, system 1 Not used
Bit 4 Check sum error, system 2 Not used
Bit 5 Check sum error, EEPROM Not used
Bit 6 ADC error Master. Received only
from MP 40.

3BSE 006 529R0001 Rev A 3-33

RCOM User’s Guide
Chapter 3 Configuration/Application Building

Table 3-11. Status2 (Continued)System messages from the slave (Continued)

Status2 Description Valid modes

Bit 7 Event queue full Master. Received from
In AC 55 and AC 110: At least one queue for time-tagged events is 80% AC 110, AC 55, MP40
filled. and MP 100.
In MP 40: The queue for event-transmitted data is 80% filled.
Bit 8 Local parameter change Master. Received only
from MP 40.
Bit 9 Power failure Master. Received only
from AC 110 and AC 55.
Bit 10 I/O module error Master. Received only
from AC 110 and AC 55.
Bit 11 Processor exception Master. Received only
The processor has executed an exception (zero divide, address error, from AC 110 and AC 55.
etc.)
Bit 12 System overload Master. Received only
from AC 110 and AC 55.
Bit 13 Battery not OK Master. Received only
from AC 110.
Bit 14, 15 Not used Not used
Bit 16 Watch dog alarm Master. Received only
System software stalled from AC 110.

Bit 17 New status word Not used.

Bit 18 Compilation error Not used.
Bit 19 Local parameter error Master. Received only
from MP 40.
Bit 20 Parameter error Not used.
Bit 21 -31 Not used Not used.

Status3 (integer long):

Time tag of last MVB or system message received by polling from a slave. The time is stored in
the format: number of 0.1 ms since midnight.
The time in Status3 can be used together with the changed status of the updated MVB to
activate Application a PC program for reporting of events from MP 40 slaves.
For event handling please refer to AMPL Configuration Advant Controller 55 Reference
Manual. Chapter: Event Handling.

3-34 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.6.1 DB Elements for RCOM Configuration

3.6.1.4 DB Element for Data Transfer and Command MVB

This chapter describes the data transfer MVB DB element, the chapter following describes the
command MVB’s. The data transfer MVB’s contain the data to be transferred via RCOM lines:
• A data transfer MVB references to a collection of up to 128 DAT's of any type.
• For RCOM only 8 DAT’s are used. (MVICHAN, PROTTYPE = 1)
• For RCOM+ 24 DAT’s are possible. (MVICHAN, PROTTYPE = 2).
The DB element MVB specifies one MVI Data Block. An MVB configures either data
transmission or commands for the MVI protocol handler (in our case the RCOM protocol
handler).
The layout of the DB element MVB is shown in Figure 3-17.
_____________________________________________________________
Call name: MVB
Element type: MVI Data Block
Item designation: MVBx
_____________________________________________________________
Base Part

MVBx

MVBx NAME EXECUTE

1 ACT EXECDONE
1 REGADDR VALID
110 CMDCODE ERR
0 AUXINFO1
0 AUXINFO2
0 NO_BREC
0 NO_INT
0 NO_INTL
0 NO_REAL
RECEIVE SOURCE
0 BLOCKED
1 NET
1 REMNODE
512 CYCLETIM
YES SORT_REF

Figure 3-17. Example of a DB element MVB, base part

3BSE 006 529R0001 Rev A 3-35

RCOM User’s Guide
Chapter 3 Configuration/Application Building

Value references 1-16

REF1
REF2
REF3
REF4
REF5
REF6
REF7
REF8
REF9
REF10
REF11
REF12
REF13
REF14
REF15
REF16

Value references 113-128

REF113
REF114
REF115
REF116
REF117
REF118
REF119
REF120
REF121
REF122
REF123
REF124
REF125
REF126
REF127
REF128

Figure 3-18. Example of a DB element MVB, value references

3-36 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.6.1 DB Elements for RCOM Configuration

Terminals Base part (part 1)

Table 3-12. Description of the DB element MVB, base part

Allowed Recommended
Terminal Description
Values Value
NAME (max.12 charac- MVBx Unique module NAME
ters)
ACT 0/1 1 Element is ACTive
0 = The element is spare, 1 = The element is active
REGADDR 1-240 REGister start ADDRess in RCOM identity(IDENT) of the
MVB.
CMDCODE 3,4,110,210,301, CoMmanD CODE to be executed
302,305,308 for RCOM: 3, 4, 110, 210, 301, 302, 305, 308
AUXINFO1 0/1/-1 AUXiliary INFOrmation 1,
= 0 for CMDCODE 4, 110, 210, 301, 308
=-1 for CMDCODE 302, 305
= 0/1 for CMDCODE 3
AUXINFO2 0/-1 AUXiliary INFOrmation 2,
=-1 for CMDCODE 305, else =0.
NO_BREC (0-8/24) Number of Boolean RECords DAT(B) (protocol dependent)
(0-8) for RCOM, (0-24) for RCOM+
NO_INT (0-8/24) Number of INTeger records DAT(I) (prot. dependent)
(0-8) for RCOM, (0-24) for RCOM+
NO_INTL (0-8/24) Number of INTeger Long records DAT(IL) (prot. dependent)
(0-8) for RCOM, (0-24) for RCOM+
NO_REAL (0-8/24) Number of REAL records DAT(R) (prot. dependent)
(0-8) for RCOM, (0-24) for RCOM+
SOURCE RECEIVE/SEND SOURCE. Direction of the data transmission
RECEIVE = Receiving, SEND = Sending
BLOCKED 0,1 BLOCKED. Cyclic execution of the specified RCOM com-
mand is
0 = not BLOCKED, 1 = BLOCKED.
The cycle time is defined by the terminal CYCLETIM.
For MVB’s with SOURCE=RECEIVE: BLOCKED=1 blocks
the reception of MVB’s by polling.
NET 1-9 NETwork number of slave or master with REMNODE.
The network number must be the same as in the corresponding
MVINODE.

3BSE 006 529R0001 Rev A 3-37

RCOM User’s Guide
Chapter 3 Configuration/Application Building

Table 3-12. Description of the DB element MVB, base part (Continued)

Allowed Recommended
Terminal Description
Values Value
REMNODE (1-255) REMote NODE number)
Master mode: node number of slave (255-> Global command)
Slave mode: node number of master
REMNODE must be the same as in the corresponding
MVINODE
CYCLETIME (0, 4, 8 ... 512 ... 512 CYCLE TIME.
32768) 1. Defines the cycle time of the protocol command execution
for BLOCKED = 0 in multiples of 100ms. (0 -> no cyclic exe-
cution).
2. For MVB’s with SOURCE=RECEIVE: Supervision time
for system reset of the terminal VALID (see terminal VALID).
SORT_REF NO/YES YES SORT REFerences
NO (MP 40) YES = references sorted in the order B, I, IL, R
EXECUTE B(r/w) EXECUTE command.
1. Invokes the single execution of the specified protocol han-
dler command when changing from 0 to 1.(The completion of
the command execution is indicated by the terminal EXEC-
DONE and the result status by the terminals ERR and
VALID.)
2. Setting EXECUTE to 0 the terminal EXECDONE is reset.
EXECDONE B(r/w) Command EXECUTION is DONE.
1 = The command execution requested by EXECUTE is com-
pleted. (The result status is indicated by the terminals ERR
and VALID.).
0 = MVB is ready for next command execution.
VALID B(r/w) VALID 1 after successful execution of the RCOM command.
For MVB’s with SOURCE=RECEIVE: The terminal will be
reset by system if no DAT’s are received within the supervi-
sion time of 3*CYCLETIM
(for CYCLETIM>0 and EXECUTE=0).
ERR B(r) ERRor
ERR is set if BLOCKED=0, CYCLETIM>0 and no data
within 3*CYCLETIM received

3-38 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.6.1 DB Elements for RCOM Configuration

Terminals Value references (part 4)

Table 3-13. Description of the DB element MVB, value references

Recommended
Terminal Parameter Name Description
Value
REF1 REFerence: Name of connected DAT element
REF2 REFerence: Name of connected DAT element
REF3 REFerence: Name of connected DAT element
REF4 REFerence: Name of connected DAT element
REF5 REFerence: Name of connected DAT element
REF6 REFerence: Name of connected DAT element
REF7 REFerence: Name of connected DAT element
REF8 REFerence: Name of connected DAT element
Max. 8 REF for RCOM (not RCOM+.)
.... ....
REF24 REFerence: Name of connected DAT element
Max.24 REF for RCOM+
.... -- ....
REF128 -- REFerence: Name of connected DAT element
Not used for RCOM

NOTE
[REGADDR, NET,NODE, SOURCE, CMDCODE] must be unique in the control
netw (1-9).

EXECUTE Execute Handshake

* for next command
*
EXECDONE

VALID or
ERR * User (PC program)

System execution System execution time

time for command for reset of EXECDONE

Figure 3-19. Handshake between EXECUTE, EXECDONE, VALID, and ERR

3BSE 006 529R0001 Rev A 3-39

RCOM User’s Guide
Chapter 3 Configuration/Application Building

3.6.2 DB Element MVB for Data Transfer

MVB’s are used to transfer data between a master and slave node. A pair of MVB’s with the
same identity (terminal REGADDR) is created on each node. The sending MVB is configured
with terminals SOURCE = SEND, CMDCODE = 210 and the receiving with
SOURCE = RECEIVE, CMDCODE = 110. Both MVB’s must have the same number, type and
reference order of DAT’s. See figure below.
Up to 8 (or 24) DAT’s can be referenced by one MVB using RCOM (or RCOM+).
Setting the terminal BLOCKED of both MVB’s to 0 the DAT’s of the sending MVB on one
node are cyclically transmitted to the DAT’s of the MVB on the other node. The cycle time is
configured by the terminal CYCLETIM which have to be the same value at both MVB.
Using the terminal EXECUTE data can be transferred in a single shot manner. The terminal
EXECUTE is controlled by a PC program.
PC program for flow control in slave mode is only needed if AC 55 RCOM link is used with
polled data transmission to the master. PC program is always necessary if AC 55 is used in
master mode.
Connecting AC 55 with a MP 200/1, MP 40 or AC 400 series of controllers, DB elements MS
are used instead of MVB. In this case the terminal IDENT of the MS corresponds to the
terminal REGADDR of the MVB.

3-40 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.6.2 DB Element MVB for Data Transfer

MVBx

MVBx NAME EXECUTE

1 ACT EXECDONE
x REGADDR VALID
210/110 CMDCODE ERR
0 AUXINFO1
0 AUXINFO2
x NO_BREC
x NO_INT
x NO_INTL
x NO_REAL
SEND/RECEIVE SOURCE
0 BLOCKED
1 NET
1 REMNODE
512 CYCLETIM
YES SORT_REF

Value references

DAT1 REF1
DAT2 REF2
DAT3 REF3
DAT4 REF4
DAT5 REF5
DAT6 REF6
DAT7 REF7
DAT8 REF8
.... .....
.... .....
DAT24 REF24

Figure 3-20. Example of a Data MVB for Data transfer

3BSE 006 529R0001 Rev A 3-41

RCOM User’s Guide
Chapter 3 Configuration/Application Building

3.6.2.1 Data Transfer from Master to Slave

To transfer data from a master to a slave the MVB on the master is configured with command
code 210 (’write’) and the corresponding MVB on the slave with command code 110 (’read’).
Executing the MVB on the master a RCOM command ’write’ with the DAT’s of the executed
MVB is sent to the slave. The sent DAT’s are stored in the MVB with same identity (terminal
REGADDR) on the slave.
The MVB’s are configured in following manner:

Table 3-14. Configuration of the DB element MVB for data transfer on the master node

Master Node
Terminal Value Description
NAME MVBx Unique name of the MVI Data Block (max. 12 characters)
ACT 1 The element is active
0 The element is spare.
REGADDR 1-240 Register address. In RCOM represents the identity (IDENT) of the MVI Data
Block.
CMDCODE 210 Command code ’write’. Transmits the DAT’s of this MVB to the corresponding
MVB (same REGADDR) on the specified slave node (terminals NET,REMNODE)
AUXINFO1 0 Must be 0.
AUXINFO2 0 Must be 0.
NO_BREC (0-8/24) Number of boolean DAT’s referenced by the MVI Data Block
NO_INT (0-8/24) Number of integer DAT’s referenced by the MVI Data Block
NO_INTL (0-8/24) Number of long integer DAT’s referenced by the MVI Data Block
NO_REAL (0-8/24) Number of real DAT’s referenced by the MVI Data Block
SOURCE SEND SEND = Sending
BLOCKED 0 Cyclic data transmission deblocked
1 Cyclic data transmission blocked
NET 1-9 Network number of the line
REMNODE 1-254 Node number of the remote receiving RTU
CYCLETIM Defines the cycle time of the MVB transmission (only for BLOCKED =0). Ensure
that the receiving MVB on the slave node is configured with the same CYCLETIM
value.
SORT_REF YES/NO All DAT references are sorted in the order B, I, IL, R
EXECUTE When changing from 0 to 1 the transmission of the MVB is requested. The comple-
tion of the MVB transmission is indicated by the terminal EXECDONE.
Setting the terminal EXECUTE to 0 the terminal EXECDONE is reset.

3-42 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.6.2 DB Element MVB for Data Transfer

Table 3-14. Configuration of the DB element MVB for data transfer on the master node (Continued)

Master Node
Terminal Value Description
EXECDONE 0 1 after MVB transmission if requested by terminal EXECUTE.
The terminal ERR indicates wether the MVB transmission failed or not.
VALID 1 after successful transmission of the MVB.
ERR 1 in case of error in transmission of the MVB. In this case the terminal is reset
after the next successful transmission of the MVB.
REF1-REF8 Names of DAT’s to be sent or received. Max. 8 DAT’s for RCOM,
REF1-REF24 max. 24 DAT’s for RCOM+

Table 3-15. Configuration of the DB element MVB for data transfer

on the slave node

Slave Node
Terminal Value Description
NAME MVBx Unique name of the MVI Data Block (max. 12 characters)
ACT 1 The element is active
0 The element is spare.
REGADDR 1-240 Register address. In RCOM it represents the identity (IDENT) of the MVI Data
Block.
CMDCODE 110 Command code ’read’.Receives the DAT’s from the corresponding MVB (same
REGADDR) from the specified master node (terminals NET,REMNODE)
AUXINFO1 0 Not used.
AUXINFO2 0 Not used.
NO_BREC (0-8/24) Number of boolean DAT’s referenced by the MVI Data Block
NO_INT (0-8/24) Number of integer DAT’s referenced by the MVI Data Block
NO_INTL (0-8/24) Number of long integer DAT’s referenced by the MVI Data Block
NO_REAL (0-8/24) Number of real DAT’s referenced by the MVI Data Block
SOURCE RECEIVE RECEIVE= Receiving
BLOCKED 0 The DAT’s of this MVB are updated when a MVB is received from the master node
1 The DAT’s of this MVB are not updated when a MVB is received from the master.
NET 1-9 Network number of the RCOM line
REMNODE 1-254 Node number of the PLC/RTU the MVB is received from.

3BSE 006 529R0001 Rev A 3-43

RCOM User’s Guide
Chapter 3 Configuration/Application Building

Table 3-15. Configuration of the DB element MVB for data transfer

on the slave node (Continued)

Slave Node
Terminal Value Description
CYCLETIM Supervision time for reset of the VALID terminal (see terminal VALID)
SORT_REF YES/NO All DAT references are sorted in the order B, I, IL, R
EXECUTE Not used
EXECDONE 0 Not used
VALID 1 after successful transmission of the MVB. The terminal is reset if no DAT’s have
been received from the master node within the supervision time of 3*CYCLETIM
(only for CYCLETIM>0)
ERR 1 in case of error in reception of the MVB. In this case the terminal is reset
after the next successful reception of the MVB.
REF1-REF8 Names of DAT’s storing the received data. Max. 8 DAT’s for RCOM,
REF1-REF24 max. 24 DAT’s for RCOM+

3.6.2.2 Data Transfer from Slave to Master

To transfer data from a master to a slave the MVB on the master is configured with command
code 110 (’read’) and the corresponding MVB on the slave with command code 210 (’write’).
Up to 8 or 24 DAT’s depending on the protocol type can be received by one MVB from the
slave:
• By read command. Executing the MVB on the master a RCOM command ’read’ is sent to
the slave. The replied DAT’s from the MVB on the slave with the same identity (terminal
REGADDR) are stored in the executed MVB on the master.
• By polling.Executing the MVB on the slave the DAT’s of the MVB are sent to the master
by polling response. On the master the received DAT’s are stored in the MVB with the
same identity (terminal REGADDR).
If the protocol type is RCOM (terminal PROTTYPE=1 at MVICHAN) then only 7 DAT’s are
allowed.
In both cases the MVB’s are configured in following manner:

3-44 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.6.2 DB Element MVB for Data Transfer

Table 3-16. Configuration of the DB element MVB for data transfer on the master node

Master Node
Terminal Value Description
NAME MVBx Unique name of the MVI Data Block (max. 12 characters)
ACT 1 The element is active
0 The element is spare.
REGADDR 1-240 Register address. In RCOM it represents the identity (IDENT) of the MVI Data
Block.
CMDCODE 110 Command code ’read’. Reads the DAT’s of the corresponding MVB (same
REGADDR) from the specified slave node (terminals NET,REMNODE)
In addition the DAT’s of the MVB can be received by polling
AUXINFO1 0 Must be 0.
AUXINFO2 0 Must be 0.
NO_BREC (0-8/24) Number of boolean DAT’s referenced by the MVI Data Block
NO_INT (0-8/24) Number of integer DAT’s referenced by the MVI Data Block
NO_INTL (0-8/24) Number of long integer DAT’s referenced by the MVI Data Block
NO_REAL (0-8/24) Number of real DAT’s referenced by the MVI Data Block
SOURCE RECEIVE RECEIVE = Receiving
BLOCKED 0 Cyclic execution of read command is deblocked
1 Cyclic execution of read command is blocked
NET 1-9 Network number of the RCOM line
REMNODE 1-254 Node number of the remote PLC/RTU the MVB is read from.
CYCLETIM Defines the cycle time of the read command execution (only for BLOCKED =0)
and the supervision time for reset of the VALID terminal.
SORT_REF YES/NO All DAT references are sorted in the order B, I, IL, R
EXECUTE When changing from 0 to 1 the read command is executed. EXECDONE indicates
the completion of the command. Setting the terminal EXECUTE to 0 the terminal
EXECDONE is reset.
EXECDONE 0 1 after the read command has been completed.The terminal ERR indicates wether
an error has occurred or not.
VALID 1 after successful reception of the MVB. If the MVB has been received by read
command the terminal is reset by system if no DAT’s have been received from the
master node within the supervision time of 3*CYCLETIM
(only for CYCLETIM>0 and EXECUTE=0)
ERR 1 in case of error. In this case the terminal is reset after the next successful reception
of the MVB from the slave node.
REF1- Names of DAT’s to be sent or received. Max. 8 (24) DAT’s for RCOM (Extended).
REF8(24)

3BSE 006 529R0001 Rev A 3-45

RCOM User’s Guide
Chapter 3 Configuration/Application Building

Table 3-17. Configuration of the DB element MVB for data transfer on the slave node

Slave Node
Terminal Value Description
NAME MVBx Unique name of the MVI Data Block (max. 12 characters)
ACT 1 The element is active
0 The element is spare.
REGADDR 1-240 Register address. In RCOM it represents the identity (IDENT) of the MVI Data
Block.
CMDCODE 210 Command code’write’.The transmission of the DAT’s of this MVB to the corre-
sponding MVB (same REGADDR) on the specified master node (NET,REMN-
ODE) is requested.
The MVB is transmitted to the master node:
when the RCOM command ’read’ for this MVB (REGADDR) is received from
the master node providing the terminal Blocked=0 on the slave or
when a polling request is received from the master node providing the terminal
EXECUTE on the slave node has been changed from 0 to 1 before.
AUXINFO1 0 Must be 0.
AUXINFO2 0 Must be 0.
NO_BREC (0-8/24) Number of boolean DAT’s referenced by the MVI Data Block
NO_INT (0-8/24) Number of integer DAT’s referenced by the MVI Data Block
NO_INTL (0-8/24) Number of long integer DAT’s referenced by the MVI Data Block
NO_REAL (0-8/24) Number of real DAT’s referenced by the MVI Data Block
SOURCE SEND SEND = Sending
BLOCKED 0 Cyclic data transmission deblocked
1 Cyclic data transmission blocked
NET 1-9 Network number of the line
REMNODE 1-254 Node number of the remote receiving RTU
CYCLETIM Defines the cycle time of the MVB transmission is requested
(only for BLOCKED =0)
SORT_REF YES/NO All DAT references are sorted in the order B, I, IL, R
EXECUTE When changing from 0 to 1 the MVB’s transmission is requested. The completion
of the MVB transmission is indicated by the terminal EXECDONE. Setting the ter-
minal EXECUTE to 0 the terminal EXECDONE is reset.
EXECDONE 0 1 after the MVB has been sent as polling response telegram. The terminal ERR
indicates whether an error occurred or in case of time-out (3*CYCLETIM).
VALID 1 after successful transmission of the MVB.
ERR 1 in case of error or time-out (3*CYCLETIM). In this case the terminal is reset after
next successful execution of the RCOM command.
REF1-REF8 Names of DAT’s to be sent or received. Max. 8 DAT’s for RCOM,
REF1-REF24 max. 24 DAT’s for RCOM+.

3-46 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.6.3 DB Element MVB for Commands

3.6.3 DB Element MVB for Commands

This chapter describes the Command MVB’s used for control of slaves. The Command MVB’s
are only defined in the RCOM master node, except for the Telephone Command MVB’s.
The execution of any RCOM command for control of slaves is programmed by a DB element
MVB. The command code is specified at the terminal CMDCODE. Several commands require
auxiliary information (command parameters) which are specified by the terminals AUXINFO1
and AUXINFO2. For every command code the value of the MVB terminal SOURCE is ’SEND.
The terminal CMDCODE can have following values for RCOM according to table 3-18
and table 3-19

Table 3-18. Command codes in master mode

Command Code RCOM command

301 cold start
302 warm start
305 normalization
308 clock setting
3 dial-up
4 hang-up

Table 3-19. Command codes in slave mode

Command Code RCOM command

3 dial-up
4 hang-up

3BSE 006 529R0001 Rev A 3-47

RCOM User’s Guide
Chapter 3 Configuration/Application Building

MVBx

MVBx NAME EXECUTE

1 ACT EXECDONE
1.255 REGADDR VALID
301/302/305/3/4 CMDCODE ERR
0/1/-1 AUXINFO1
0/-1 AUXINFO2
0 NO_BREC
0 NO_INT
0 NO_INTL
0 NO_REAL
SEND SOURCE
0/1 BLOCKED
1..9 NET
1..255 REMNODE
0 CYCLETIM
YES SORT_REF

Value references not used

Figure 3-21. Example of a command MVB

There is no partner MVB on the slave for commands

3.6.3.1 Cold Start a Slave

One cold start command MVB for each remote node are necessary for executing cold start
commands.
Executing a MVB with command code ’cold start’ the CI532V01 transmits the RCOM
command ’cold start’ to the slave node specified by the terminals NET and REMNODE.
Cold start of an AC 55 slave means a full system restart. The RCOM status word (RCSW) and
the RTU status 2 is reset. Executing the cold start command an AC 55 slave deletes pending
system messages to the master. System messages are not blocked for polling by the master. All
MVB’s are blocked for event transmission. The events stored in the event queues of the Event
Sets (DB elements EVS(S) are cleared. Cold start must be always followed by a normalization
of the slave to deblock the event transmission of MVB’s and the transmission of time-tagged
events between Event Sets (EVS(S)).

3-48 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.6.3 DB Element MVB for Commands

Table 3-20. Configuration of the DB element MVB for cold start on the master node

Master Node
Terminal Value Description
NAME MVBx Unique name of the MVI Data Block (max. 12 characters)
ACT 1 The element is active
0 The element is spare.
REGADDR 1-240 Register address. In RCOM represents the identity (IDENT) of the MVI Data
Block.
CMDCODE 301 RCOM command ’cold start’. Requests the transmission of the RCOM command
’cold start’ to the slave node.
AUXINFO1 0 Must be 0.
AUXINFO2 0 Must be 0.
NO_BREC 0 Not used.
NO_INT 0 Not used.
NO_INTL 0 Not used.
NO_REAL 0 Not used.
SOURCE SEND SEND = Sending
BLOCKED 0 Not recommended.
1 Recommended value. (Cyclic data transmission blocked).
NET 1-9 Network number of the RCOM line.
REMNODE 1-254 Node number of the remote PLC/RTU.
CYCLETIM 0 Not used.
SORT_REF YES Not used.
EXECUTE When changing from 0 to 1 the transmission of the RCOM command is requested.
The completion of the command transmission is indicated by the terminal EXEC-
DONE.
EXECDONE 0 1 after command transmission if requested by terminal EXECUTE.
The terminal ERR indicates wether the command transmission failed or not.
EXECDONE is reset by setting the Terminal EXECUTE to 0.
VALID 1 after successful command execution.
ERR 1 in case of error in command transmission. In this case the terminal is reset
after the next successful transmission of the RCOM command.
REF1- Not used.
REF8(24)

3BSE 006 529R0001 Rev A 3-49

RCOM User’s Guide
Chapter 3 Configuration/Application Building

3.6.3.2 Warm Start/Block a Slave

One warm start command MVB for each remote node can be used for executing warm start
commands.
Executing a MVB with command code ’warm start’ the RCOM link transmits the RCOM
command ’warm start’ to the slave node specified by the terminals NET and REMNODE.
Warm start of an AC 55 slave means that all MVB’s are blocked for event transmission. Any
MVB waiting in the event queue of the RCOM link to be transmitted is deleted. In addition, the
RCOM status word (RCSW) and the RTU status 2 is reset. Executing the warm start command
an AC 55 slave deletes pending system messages to the master. System messages are not
blocked for polling by the master.
Warm start must be always followed by a normalization of the slave to deblock the event
transmission of MVB’s, system messages and the transmission of time-tagged events between
Event Sets (EVS(S) and EVS(T)) (Event option).

The MVB for the RCOM command "Warm start" is configured on the master in following
manner.

Table 3-21. Configuration of the DB element MVB for warm start on the master node

Master Node
Terminal Value Description
NAME MVBx Unique name of the MVI Data Block (max. 12 characters)
ACT 1 The element is active
0 The element is spare.
REGADDR 1-240 Register address. In RCOM represents the identity (IDENT) of the MVI Data
Block.
CMDCODE 302 RCOM command ’warm start’.Requests the transmission of the RCOM command
’warm start’ to the slave node.
AUXINFO1 -1 Must be -1.
AUXINFO2 0 Must be 0.
NO_BREC 0 Not used.
NO_INT 0 Not used.
NO_INTL 0 Not used.
NO_REAL 0 Not used.
SOURCE SEND SEND = Sending
BLOCKED 0 Not recommended.
1 Recommended value.(Cyclic data transmission blocked)
NET 1-9 Network number of the RCOM line

3-50 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.6.3 DB Element MVB for Commands

Table 3-21. Configuration of the DB element MVB for warm start on the master node (Continued)

Master Node
Terminal Value Description
REMNODE 1-254 Node number of the remote PLC/RTU
CYCLETIM 0 Not used.
SORT_REF YES Not used.
EXECUTE When changing from 0 to 1 the transmission of the RCOM command is requested.
The completion of the command transmission is indicated by the terminal EXEC-
DONE.
EXECDONE 0 1 after command transmission if requested by terminal EXECUTE.
The terminal ERR indicates whether the command transmission failed or not.
EXECDONE is reset by setting the Terminal EXECUTE to 0.
VALID 1 after successful command execution.
ERR 1 in case of error in command transmission. In this case the terminal is reset
after the next successful transmission of the RCOM command.
REF1- Not used.
REF8(24)

3BSE 006 529R0001 Rev A 3-51

RCOM User’s Guide
Chapter 3 Configuration/Application Building

3.6.3.3 Normalize/Deblock a Slave

One normalization command MVB for each remote node are necessary for executing
normalization commands.
Executing a MVB with command code ’normalization’ the RCOM link transmits the RCOM
command ’normalization’ to the slave node specified by the terminals NET and REMNODE.
Normalization of an AC 55 slave means that all MVB’s are deblocked for event transmission.
In addition, the RCOM status word (RCSW) and the RTU status 2 are reset.
A slave must be normalized after power-up and after the execution of the RCOM commands
’cold start’ and ’warm start’. The bit 27 in RTU status 1 ’polling blocked’ is set if the slave must
be normalized.

Table 3-22. Configuration of the DB element MVB for normalization/deblocking on the master node

Master Node
Terminal Value Description
NAME MVBx Unique name of the MVI Data Block (max. 12 characters).
ACT 1 The element is active
0 The element is spare.
REGADDR 1-240 Register address. In RCOM represents the identity (IDENT) of the MVI Data
Block.
CMDCODE 305 RCOM command ’normalization’.Requests the transmission of the RCOM com-
mand ’normalization’ to the slave node.
AUXINFO1 -1 Must be -1
AUXINFO2 -1 Must be -1
NO_BREC 0 Not used.
NO_INT 0 Not used.
NO_INTL 0 Not used.
NO_REAL 0 Not used.
SOURCE SEND S = Sending
BLOCKED 0 Not recommended.
1 Recommended value. (Cyclic data transmission blocked)
NET 1-9 Network number of the RCOM line
REMNODE 1-254 Node number of the remote PLC/RTU
CYCLETIM 0 Not used.
SORT_REF YES Not used.

3-52 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.6.3 DB Element MVB for Commands

Table 3-22. Configuration of the DB element MVB for normalization/deblocking on the master node (Continued)

Master Node
Terminal Value Description
EXECUTE When changing from 0 to 1 the transmission of the RCOM command is requested.
The completion of the command transmission is indicated by the terminal EXEC-
DONE.
EXECDONE 0 1 after command transmission if requested by terminal EXECUTE.
The terminal ERR indicates whether the command transmission failed or not.
EXECDONE is reset by setting the Terminal EXECUTE to 0.
VALID 1 after successful command execution.
ERR 1 in case of error in command transmission. In this case the terminal is reset
after the next successful transmission of the RCOM command.
REF1- Not used.
REF8(24)

3.6.3.4 Clock Synchronization

One MVB for each communication channel may be used in the RCOM master node for
execution of the Clock Synchronization function.
Executing the command ’clock synchronization’ the RCOM link transmits the RCOM
command ’clock synchronization’ including the actual time and date to all slave nodes of the
channel.
This command can be executed only by a MVI channel operating in master mode. It should
always be sent as a global command to the slave nodes.
Another way to send clock synchronization to the slave is the configuration of the clock setting
mode at the DB element MVICHAN (see terminals PARAM5, PARAM6).

Table 3-23. Configuration of the DB element MVB for clock synchronization on the master node

Master Node
Terminal Value Description
NAME MVBx Unique name of the MVI Data Block (max. 12 characters)
ACT 1 The element is active
0 The element is spare.
REGADDR 1-240 Register address. In RCOM represents the identity (IDENT) of the MVI Data
Block.
CMDCODE 308 RCOM command ’clock synchronization’. Requests the transmission of the RCOM
command ’clock synchronization’ to all slave nodes (global command).

3BSE 006 529R0001 Rev A 3-53

RCOM User’s Guide
Chapter 3 Configuration/Application Building

Table 3-23. Configuration of the DB element MVB for clock synchronization on the master node (Continued)

Master Node
Terminal Value Description
AUXINFO1 0 Must be 0.
AUXINFO2 0 Must be 0.
NO_BREC 0 Not used.
NO_INT 0 Not used.
NO_INTL 0 Not used.
NO_REAL 0 Not used.
SOURCE SEND SEND = Sending
BLOCKED 0 Not recommended.
1 Recommended value. (Cyclic data transmission blocked).
NET 1-9 Network number of the RCOM line.
REMNODE 255 Must be 255 because the clock synchronization is sent to all slave nodes.
CYCLETIM 0 Not used.
SORT_REF YES Not used.
EXECUTE When changing from 0 to 1 the transmission of the RCOM command is requested.
The completion of the command transmission is indicated by the terminal EXEC-
DONE.
EXECDONE 0 1 after command transmission if requested by terminal EXECUTE.
The terminal ERR indicates whether the command transmission failed or not.
EXECDONE is reset by setting the Terminal EXECUTE to 0.
VALID 1 after successful command execution.
ERR 1 in case of error in command transmission. In this case the terminal is reset
after the next successful transmission of the clock synchronization.
REF1- Not used.
REF8(24)

3-54 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.6.3 DB Element MVB for Commands

3.6.3.5 Telephone Commands

Two telephone command MVB’s for each remote node may be used for dial-up the remote node
and hang-up of telephone connections.
Generally one dial-up MVB is used on the master to dial-up the slave.
On the slave a dial-up MVB has to be configured for programmed dial-up (optional).
No command MVB has to be configured on the slave for alarm dial-up.
Generally one hang-up MVB is used on the master to disconnect the line.
On the slave a hang up MVB has to be configured for programmed hang-up (optional).

NOTE
Note that for telephone handling only full duplex is valid.

Dial-up
Executing the command ’dial-up’ the MVI channel requests the connected modem to dial-up the
remote node specified by the terminals REMNODE and NET. The dial string and the phone
number are taken from the DB element MVINODE with the same terminal values of NET and
REMNODE.

Table 3-24. Configuration of the DB element MVB for dial-up on the master node

Master Node
Terminal Value Description
NAME MVBx Unique name of the MVI Data Block (max. 12 characters)
ACT 1 The element is active
0 The element is spare.
REGADDR 1-240 Register address. In RCOM it represents the identity (IDENT) of the MVI Data
Block.
CMDCODE 3 RCOM command ’dial-up’.The MVI channel requests the modem to dial-up the
remote node.
AUXINFO1 0 Used only in master mode: Requests normalization of communication part and
starts polling after acknowledgment from the slave node.
1 Used only in master mode: Requests only normalization of communication part
after acknowledgment from the slave node. Polling is commenced after the RCOM
command ’Normalization’ has been sent to the slave node.
AUXINFO2 0 Must be 0.
NO_BREC 0 Not used.
NO_INT 0 Not used.
NO_INTL 0 Not used.

3BSE 006 529R0001 Rev A 3-55

RCOM User’s Guide
Chapter 3 Configuration/Application Building

Table 3-24. Configuration of the DB element MVB for dial-up on the master node (Continued)

Master Node
Terminal Value Description
NO_REAL 0 Not used.
SOURCE SEND SEND = Sending
BLOCKED 0 Not recommended.
1 Recommended value. (Cyclic data transmission blocked).
NET 1-9 Network number of the RCOM line.
REMNODE 1-254 Node number of the remote PLC/RTU.
CYCLETIM 0 Not used.
SORT_REF YES Not used.
EXECUTE When changing from 0 to 1 the transmission of the RCOM command is requested.
The completion of the command transmission is indicated by the terminal
EXECDONE.
EXECDONE 0 1 after completion of dialling. The terminal ERR indicates whether the dialling
failed or not. EXECDONE is reset by setting the Terminal EXECUTE to 0.
VALID 1 after successful command execution.
ERR 1 in case of error in dialling. In this case the terminal is reset
after the next successful dial-up.
REF1- Not used.
REF8(24)

Hang-up
Executing the command ’hang-up’ the MVI channel requests the modem to go on hook by
resetting the DTR signal after hang-up time. The hang-up time can be configured by the
terminal PARAM2 at the DB element MVICHAN.

Table 3-25. Configuration of the DB element MVB for hang-up on the master node

Master Node
Terminal Value Description
NAME MVBx Unique name of the MVI Data Block (max. 12 characters)
ACT 1 The element is active
0 The element is spare.
REGADDR 1-240 Not used.
CMDCODE 4 RCOM command ’hang-up’. The MVI channel requests the modem to go on hook.

3-56 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.6.3 DB Element MVB for Commands

Table 3-25. Configuration of the DB element MVB for hang-up on the master node (Continued)

Master Node
Terminal Value Description
AUXINFO1 0 Must be 0.
AUXINFO2 0 Must be 0.
NO_BREC 0 Not used.
NO_INT 0 Not used.
NO_INTL 0 Not used.
NO_REAL 0 Not used.
SOURCE SEND SEND = Sending
BLOCKED 0 Not recommended.
1 Recommended value. (Cyclic data transmission blocked).
NET 1-9 Network number of the RCOM line.
REMNODE 1-254 Node number of the remote PLC/RTU.
CYCLETIM 0 Not used.
SORT_REF YES Not used.
EXECUTE When changing from 0 to 1 the MVI channel requests the modem to go on hook.
The completion of the hang-up execution is indicated by the terminal EXECDONE.
EXECDONE 0 1 after completion of the hang-up execution.
The terminal ERR indicates whether the hang-up failed or not.
EXECDONE is reset by setting the Terminal EXECUTE to 0.
VALID 1 after successful command execution.
ERR 1 in case of error in command transmission. In this case the terminal is reset
after the next successful transmission of the RCOM command.
REF1- Not used.
REF8(24)

Alarm Dial-up
On a slave dial-up is performed by system (without configuring a MVB) in following cases:
• system error occurred which caused a system message
• time-tagged event has been generated by a DB element DIC, AIC, DIMVB, AIMVB and
alarm dial-up is enabled for this event source (terminal AL_DIAL).
Executing the alarm dial-up the MVI takes the dial strings and the phone numbers from the
terminals DIALSTR1-DIALSTR4 and PHONENO1-PHONENO4 at the DB element
MVINODE. If the dial-up fails for a phone number after a certain number of retries the next

3BSE 006 529R0001 Rev A 3-57

RCOM User’s Guide
Chapter 3 Configuration/Application Building

phone number is dialed. A maximum of 4 phone numbers are provided. The number of retries
for every phone number is specified by the terminal PARAM7 at the DB element MVICHAN.
It is recommended to execute the hang-up command on the master. A criteria for hang-up is the
bit 15 (’poll data reception time-out’) in RTU status 1. This bit is set on the master when no data
have been received by polling within a specified time and is reset after receiving the next MVB
or time-tagged event by polling. Thus this status bit can be used to determine when the slave has
sent all events and system messages up to the master. The time-out can be configured by the
terminal PARAM8 at the DB element MVICHAN. The recommended value is 100 seconds.
Note that polling has lower priority than MVB transmission. So this time-out will be useful only
if polling is not fully suppressed by MVB transmission.

3.6.4 PC Program Layout

To control the data flow on the asynchronous communication link a PC program is necessary in
the AC 55.
Normally a PC program is used only for a MVI channel in master mode. The PC program
evaluates the status information about the slave nodes and the RCOM link from the DB
elements MVICHAN and MVINODE and controls the slaves by DB elements MVB (see
Figure 3-22).

3-58 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.6.4 PC Program Layout

PC-Program DB elements

CONTRM MVICHAN

Application DSR
PC-Program DCD
driven CTS
logic RI
for
control
of
MVINODE
slave node

STATUS1
STATUS2
STATUS3

MVB

EXECUTE
EXECDONE
VALID
ERR
BLOCKED
: :
: :

Figure 3-22. PC program layout for control of an RCOM node

It is recommended to include the PC program part for every slave node in an own CONTRM
The cycle time of the CONTRM should be approximately 100 ms.
In slave mode a PC program is only necessary for RCOM if data should be transmitted to the
master in an event driven way (e.g. to inform the master about I/O signal changes on the slave).

3BSE 006 529R0001 Rev A 3-59

RCOM User’s Guide
Chapter 3 Configuration/Application Building

3.6.4.1 RCOM Data Flow Control Type Circuits

CONV-IB
D=1 S ERR
D=0 >L SIGN
D=0 R ZERO
NODE1:STATUS1 I O1 STATUS1:LINK READ1:BLOCKED
OR
O2 STATUS1:LINE

DEBLOCK

Figure 3-23. Function block for control of cyclic data transfer

The design on the PC function block designed for the execution depends on whether the MVB is
executed cyclically or not.
For cyclic data transfer the Data MVB’s are just deblocked setting the terminal BLOCKED to 0.
It is recommended to connect the deblock signal with the link status (see figure above).
For dial-up lines the line status should be included in this action.
In this section 3 type circuits are proposed to easy the handling of MVB’s in the case of single
execution.
Type circuit EXECMVB1 (see Figure 3-24) has the aim to automate the reset of a MVB after
its execution.

Type Circuit EXECMVB1

TC EXECMVB1
1 >ACTIVATE FINISHED 2
ERROR 3
4 EXECDONE EXECUTE 6
5 ERR

* *+1

S & T=<EXECUTE>
D=0
D=1 D
T=<ACTIVATE> >C
T=<EXECDONE> R

*+2
S T=<FINISHED>
R

*+3
MOVE
(B,1)
T=<ERR> T=<ERROR>

Figure 3-24. Type circuit EXECMVB1

3-60 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.6.4 PC Program Layout

The terminals EXECDONE, ERR and EXECUTE of the type circuit must be connected to the
identical terminals of the MVB.
Setting the input terminal ACTIVATE of the type circuit EXECMVB1 the execution of the
connected MVB is requested. The output terminal FINISHED becomes 1 after completion of
the MVB execution. Reading the terminal ERROR as long as READY is set it can be defined
whether the command execution has succeeded or not. The next MVB execution can be
requested by the terminal ACTIVATE as soon as the terminal FINISHED is 1.
To understand the function of the type circuit it has to be remembered that the execution of a
MVB is requested by terminal EXECUTE. The terminal EXECDONE becomes 1 after
completion of the MVB execution. At the same time the terminal ERR indicates whether the
MVB execution failed or not. In this type circuit the terminal EXECUTE is forced through the
PC element *+1 to 0 as long as the terminal EXECDONE is 1. As a result the terminal
EXECDONE is reset by the MVI. So the type circuit returns into the initial state.

Type Circuit EXECMVB2

TC EXECMVB2
1 >ACTIVATE READY 2
3 EXECDONE EXECUTE 5
4 ERR

*+1

D=0 S
* D=1 D
T=<ERR> & >C T=<READY>
T=<EXECDONE> R

*+2 *+3 *+4

OR S & T=<EXECUTE>
T=<ACTIVATE> D=0
D=1 D
>C
R

Figure 3-25. Type circuit EXECMVB2

The type circuit EXECMVB2 in the figure above includes an additional functionality - an
automatic retry mechanism in case of the execution of the MVB failed. The MVB is executed
until it succeeds or the terminal ACTIVATE is reset. The successful MVB execution is indicated
by terminal READY.
The automatic retry of command execution in case of failure is realized by the feedback
between the terminals EXECUTE and EXECDONE. This feedback is active until the
combination EXECDONE=1 and ERR=0 (successful execution) occurs.

3BSE 006 529R0001 Rev A 3-61

RCOM User’s Guide
Chapter 3 Configuration/Application Building

Type Circuit EXECMVB3

TC EXECMVB3
1 >ACTIVATE READY 3
2 LINE_UP
4 EXECDONE EXECUTE 6
5 ERR

*+1

D=0 S
* D
D=1
T=<ERR> & >C T=<READY>
T=<EXECDONE> R

*+2
OR
T=<ACTIVATE>
*+3 *+4 *+5 *+6
& S S & T=<EXECUTE>
D=0
T=<LINE_UP> R D=1 D
>C
R

Figure 3-26. Type circuit EXECMVB3

The type circuit in the figure above includes the automatic retry mechanism as in type circuit
EXECMVB2. In addition, the line status is taken into account, i.e. the execution of the MVB is
only started if the line is up.
To execute several MVB’s in a sequence these type circuits can be connected in a sequence.
See next section (RCOM data flow control).

3-62 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.6.4 PC Program Layout

3.6.4.2 RCOM Data Flow Control

CONTRM CONV-IB
D=1 S ERR
D=0 >L SIGN
D=0 R ZERO
NODE1:STATUS1 I O1 STATUS1:LINK
O2 STATUS1:LINE
....

TC EXECMVB3
START 1 >ACTIVATE READY 3
2 LINE_UP
NORM1:EXECDONE 4 EXECDONE EXECUTE 6 NORM1:EXECUTE
NORM1:ERR 5 ERR

TC EXECMVB3
1 >ACTIVATE READY 3
2 LINE_UP
SEND:EXECDONE 4 EXECDONE EXECUTE 6 SEND:EXECUTE
SEND:ERR 5 ERR

TC EXECMVB3
1 >ACTIVATE READY 3
2 LINE_UP
READ1:EXECDONE 4 EXECDONE EXECUTE 6 READ1:EXECUTE
READ1:ERR 5 ERR

OR READ2:BLOCKED
S
R

Figure 3-27. MVB sequence for read/write data transfer initiated by PC program on the master side.

3BSE 006 529R0001 Rev A 3-63

RCOM User’s Guide
Chapter 3 Configuration/Application Building

3.6.4.3 Transmission of Time-Tagged Events from Event Sets

Time-tagged events can be transmitted from an Event Sets element on a RCOM slave node to
another Event Set element on a master node. (For more information about Event Sets see the
AMPL Configuration Advant Controller 100 Series Reference Manual.)
Before events can be received on the master from a certain slave the normalization
command has to be sent to this slave.
Besides, it has to be taken into account that time-tagged events are transmitted by polling which
is performed by the MVI channel module when no MVI Data Blocks are transmitted. Thus, the
transmission of MVBs has a higher priority than the transmission of time-tagged events.
Therefore the application has to be built in a way that the MVB transmission does not fully
suppress polling and, hence, the transmission of time-tagged events.
This requirement can be fulfilled by taking following two measures:
1. Keep the load on the RCOM link (including the load from the time-tagged events) less
than 100% (for load calculation see Section 3.2.2, Total Load on RCOM Link).
2. Build an application which controls the execution of MVBs in a way that the transmission
of time-tagged events is covered.
The second point can be realized by two variants of application building.

Variant 1
The basic idea is to set a certain poll cycle time in the master MVI channel (terminal
POLLCYCL at DB element MVICHAN) and to control the deblocking of all cyclically
executed MVBs by the MVI status bit “poll time-out“ from all slave nodes (terminal STATUS1
at DB elements MVINODE). This approach guarantees that within a certain period every slave
is polled at least once and, hence, time-tagged events are received from the slave.
In the figure below an application example for the realization of this approach is shown.
The status bit “poll time-out“ from all slave nodes is connected to a PC element OR. The output
of this PC element controls the deblocking of all cyclically executed MVBs (read or write
commands).
As long as the master MVI channel manages to poll all slave nodes within the poll cycle time all
status bits “poll time-out“ are 0 and the MVB elements are deblocked. As soon as the master
MVI channel has not managed to poll at least one slave within the poll cycle time due to a heavy
MVB traffic on the link the corresponding status bits “poll time-out“ goes up. In the result all
MVB elements are blocked as long as the slave with poll time-out has been polled. So you get a
simple “regulator“ which provides the transmission of time-tagged events and MVBs
simultaneously.

3-64 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.6.4 PC Program Layout

The MVI channel parameter configuring the maximum number of polls per cycle and slave
(terminal PARAM4 at DB element MVICHAN) must be set to 1.

CONV-IB
D=1 S ERR
D=0 >L SIGN
D=0 R ZERO
NODE1:STATUS1 I ....
O12 POLL_TM01-5
....

CONV-IB
D=1 S ERR
D=0 >L SIGN
D=0 R ZERO
NODE2:STATUS1 I ....
O12 POLL_TM02-5
....

CONV-IB
D=1 S ERR
D=0 >L SIGN
D=0 R ZERO
NODE3:STATUS1 I ....
O12 POLL_TM03-5
....

POLL_TM01-5 READ_NODE1:BLOCKED
POLL_TM02-5 OR
READ_NODE1:BLOCKED
POLL_TM03-5 READ_NODE1:BLOCKED
WRITE_NODE1:BLOCKED
WRITE_NODE1:BLOCKED

Figure 3-28. Control of MVBs by poll time-out

The poll cycle time T poll_cycle (terminal PARAM4) on the master MVI channel and on all
slave MVI channels within the same RCOM network must be configured with the value
calculated by following formula:

T poll_cycle = N ⋅ 1200
------------ + 0,2
 S 

3BSE 006 529R0001 Rev A 3-65

RCOM User’s Guide
Chapter 3 Configuration/Application Building

where
N = number of slave nodes
S = communication speed (bit/s)
In Table 3-26 the MVI poll cycle time (terminal PARAM4) for some RCOM network
configurations is shown.

Table 3-26. MVI poll cycle time for some network configurations (examples)

Communi- MVI poll

Number of
cation speed cycle time
slaves
S (bit/s) T poll_cycle (s)
1200 8 10
2400 16 12
9600 8 3
9600 16 6

It is recommended not to send MVBs in an event-driven manner from a slave which is prepared
to send time-tagged events to the master.
This variant of application building can not be applied for dial line connections because in this
case the status flag “poll time-out“ is not handled.

Variant 2
The basic idea in this variant is to block the cyclic MVB transmission as soon as an time-tagged
event on a slave is generated. The generation of an event can be realized on the master by
reading the terminals Q_EMPTY of all EVS elements via a MVB. Note that the transmission of
the MVB transmitting the value of the Q_EMPTY terminals must never been blocked because
otherwise the actual queue state is not available in the MVB on the master! It is recommended
to specify a cycle time of more than 5 seconds for this MVB because the reading of the
Q_EMPTY terminals should brake the event transmission.
In the case of dial line it is proposed to block the MVB transmission before the hang-up is made
and then to allow the transmission of time-tagged events until all EVS event queues become
empty.
The poll cycle time (PARAM4) on the master MVI channel and on all slave MVI channels
within the same RCOM network must be configured with the value calculated by the formula
described above.

3.6.5 Configuration with MasterPiece 40

This example describes the necessary application programming for one slave node
MasterPiece 40.
The configuration is a dial-up telephone line (one slave).

3-66 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.6.5 Configuration with MasterPiece 40

Configuration on the master node (AC 55):

• Network number = 1
• Own node number = 4
• Own telephone number = 1625 (no switchboard).
Configuration on the Modem:
• Transmission speed 1200 bits/s, full duplex, V.22
• Direct asynchronous mode
• Hayes without id
• No pause for dial tone after command
• DCD active
• DTR for modem reset.
Configurations on the slave node (MP 40):
• Own node number = 21
• Own telephone number = 1651 (no switchboard)
• Transmission speed 1200 bits/s, full duplex, V.22.

Master
AC 55
Node 5
Tel. 1625
Modem

Network 1
Tel. 1651

Slave
MP 40
Node 21

Figure 3-29. AC 55 Configuration example

3BSE 006 529R0001 Rev A 3-67

RCOM User’s Guide
Chapter 3 Configuration/Application Building

3.6.5.1 Application in Master Node AC 110 DB Elements

Three Configuration DB elements must be build. Device configuration CT481 or CT482, the
channel characteristics MVICHAN, Node configuration and node Status MVINODE
Four Command MVB’s are used. Cold Start, Normalize, Dial-up the slave and Hang-up.
Two Command MVB are optional: Warm Start, Clock Synch.
Several Data MVB are used for the actual data transfer. MVB’s for Sending Data to the slave
and MVB’s for Receiving Data (Events) from the salve.

3-68 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.6.5 Configuration with MasterPiece 40

BASIC UNIT
CT1_______________ NAME
0 _________________ UNIT-ADR
1 _________________ IMPL
CT481_____________ TYPE
50 Hz _____________ AI GFREQ
CHANNEL1 _______ MVI-CHAN

MVICHAN

CHANNEL1 _______ NAME

1 _________________ NET
4 _________________ NODE
1 _________________ MASTER
SLAVE____________ TIMESYNC
MVINODE

MVN1 ____________ NAME

1 _________________ PROTTYPE
1 _________________ ACT
FULL_____________ DUPLEX
1 _________________ NET
1 _________________ DIAL
21 ________________ REMNODE
1200 ______________ SPEED
ATDT_____________ DIALSTR1
8 _________________ CHLEN
1651 ______________ PHONE_NO1
1 _________________ STOPBITS
_________________ DIALSTR2
ODD______________ PARITY
_________________ PHONE_NO2
2 _________________ LINESTAB
_________________ DIALSTR3
2 _________________ CARRDEL
_________________ PHONE_NO3
2 _________________ MAXRETR
_________________ DIALSTR4
2 _________________ CHARTOUT
_________________ PHONE_NO4
80 ________________ TURNTIME
2 _________________ UARTOUT
80 ________________ POLLCYCL
One MVINODE for every NODE on the line
.
3 (No. of preambles) PARAM1
30 (Hang-up time) PARAM2
5 (Disconnect time) PARAM3
3 (Max.no.of polls) PARAM4
3 (Clock set mode) PARAM5
0 (Clock cycle time) PARAM6
2 (Max. no. recalls) PARAM7
30 (Event timeout) PARAM8

Figure 3-30. Configuration and RCOM status DB elements

3BSE 006 529R0001 Rev A 3-69

RCOM User’s Guide
Chapter 3 Configuration/Application Building

Cold Start-MVB Warm Start-MVB

COLD21___________ NAME WARM21__________ NAME

1 _________________ ACT 1 _________________ ACT
1 _________________ REGADDR 1 _________________ REGADDR
301 _______________ CMDCODE 302 _______________ CMDCODE
0 _________________ AUXINFO1 -1_________________ AUXINFO1
0 _________________ AUXINFO2 0 _________________ AUXINFO2
0 _________________ NO_BREC 0 _________________ NO_BREC
0 _________________ NO_INT 0 _________________ NO_INT
0 _________________ NO_INTL 0 _________________ NO_INTL
0 _________________ NO_REAL 0 _________________ NO_REAL
SEND _____________ SOURCE SEND _____________ SOURCE
0 _________________ BLOCKED 0 _________________ BLOCKED
1 _________________ NET 1 _________________ NET
21 ________________ REMNODE 21 ________________ REMNODE
0 _________________ CYCLETIM 0 _________________ CYCLETIM
YES ______________ SORT_REF YES ______________ SORT_REF

Normalization-MVB Clock Synch.MVB

NORM21 __________ NAME CLOCK21_________ NAME

1 _________________ ACT 1 _________________ ACT
1 _________________ REGADDR 1 _________________ REGADDR
305 _______________ CMDCODE 308 _______________ CMDCODE
-1_________________ AUXINFO1 0 _________________ AUXINFO1
-1_________________ AUXINFO2 0 _________________ AUXINFO2
0 _________________ NO_BREC 0 _________________ NO_BREC
0 _________________ NO_INT 0 _________________ NO_INT
0 _________________ NO_INTL 0 _________________ NO_INTL
0 _________________ NO_REAL 0 _________________ NO_REAL
SEND _____________ SOURCE SEND _____________ SOURCE
0 _________________ BLOCKED 0 _________________ BLOCKED
1 _________________ NET 1 _________________ NET
21 ________________ REMNODE 255 _______________ REMNODE
0 _________________ CYCLETIM 0 _________________ CYCLETIM
YES ______________ SORT_REF YES ______________ SORT_REF

Figure 3-31. Command MVB DB elements

3-70 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.6.5 Configuration with MasterPiece 40

DIAL-UP MVB HANG-UP MVB

DIAL21____________ NAME HANGUP21________ NAME

1 _________________ ACT 1 _________________ ACT
1 _________________ REGADDR 1 _________________ REGADDR
3 _________________ CMDCODE 4 _________________ CMDCODE
0 _________________ AUXINFO1 0 _________________ AUXINFO1
0 _________________ AUXINFO2 0 _________________ AUXINFO2
0 _________________ NO_BREC 0 _________________ NO_BREC
0 _________________ NO_INT 0 _________________ NO_INT
0 _________________ NO_INTL 0 _________________ NO_INTL
0 _________________ NO_REAL 0 _________________ NO_REAL
SEND _____________ SOURCE SEND _____________ SOURCE
1 _________________ BLOCKED 1 _________________ BLOCKED
1 _________________ NET 1 _________________ NET
21 ________________ REMNODE 21 ________________ REMNODE
0 _________________ CYCLETIM 0 _________________ CYCLETIM
YES ______________ SORT_REF YES ______________ SORT_REF

STATUS-MVB STATUS- MVB

MP40UNISTAT_____ NAME MP40SYSTAT______ NAME

1 _________________ ACT 1 _________________ ACT
232 _______________ REGADDR 237 _______________ REGADDR
110 _______________ CMDCODE 110 _______________ CMDCODE
0 _________________ AUXINFO1 0 _________________ AUXINFO1
0 _________________ AUXINFO2 0 _________________ AUXINFO2
6 _________________ NO_BREC 2 _________________ NO_BREC
0 _________________ NO_INT 0 _________________ NO_INT
0 _________________ NO_INTL 3 _________________ NO_INTL
0 _________________ NO_REAL 0 _________________ NO_REAL
RECEIVE_________ SOURCE RECEIVE _________ SOURCE
1 _________________ BLOCKED 1 _________________ BLOCKED
1 _________________ NET 1 _________________ NET
21 ________________ REMNODE 21 ________________ REMNODE
0 _________________ CYCLETIM 0 _________________ CYCLETIM
YES ______________ SORT_REF YES ______________ SORT_REF

Figure 3-32. Telephone command MVB DB elements and optional MP 40 status MVB’s.

Note: 2 further optional Data MVB’s are recommended for diagnosis, with REGADDR (= ’Ident’) =232 or 237.
See MP 40 User’s Manual

3BSE 006 529R0001 Rev A 3-71

RCOM User’s Guide
Chapter 3 Configuration/Application Building

DI-MVB DO-MVB

DI21U1 ____________ NAME DO21U1 ___________ NAME

1 _________________ ACT 1 _________________ ACT
1 _________________ REGADDR 3 _________________ REGADDR
110 _______________ CMDCODE 210 _______________ CMDCODE
0 _________________ AUXINFO1 0 _________________ AUXINFO1
0 _________________ AUXINFO2 0 _________________ AUXINFO2
1 _________________ NO_BREC 1 _________________ NO_BREC
0 _________________ NO_INT 0 _________________ NO_INT
1 _________________ NO_INTL 0 _________________ NO_INTL
0 _________________ NO_REAL 0 _________________ NO_REAL
RECEIVE _________ SOURCE SEND _____________ SOURCE
0 _________________ BLOCKED 0 _________________ BLOCKED
1 _________________ NET 1 _________________ NET
21 ________________ REMNODE 21 ________________ REMNODE
0 _________________ CYCLETIM 16 ________________ CYCLETIM
YES ______________ SORT_REF YES_______________ SORT_REF

Value references 1-16 Value references 1-16

DIB21U1 __________ REF1 DOB21U1 _________ REF1
TDI21U1 __________ REF2 0 _________________ REF2
0 _________________ REF3 0 _________________ REF3
0 _________________ REF4 0 _________________ REF4
0 _________________ REF5 0 _________________ REF5
0 _________________ REF6 0 _________________ REF6
0 _________________ REF7 0 _________________ REF7
0 _________________ REF8 0 _________________ REF8
0 _________________ REF9 0 _________________ REF9
0 _________________ REF10 0 _________________ REF10
0 _________________ REF11 0 _________________ REF11
0 _________________ REF12 0 _________________ REF12
0 _________________ REF13 0 _________________ REF13
0 _________________ REF14 0 _________________ REF14
0 _________________ REF15 0 _________________ REF15
0 _________________ REF16 0 _________________ REF16

Figure 3-33. Data MVB DB elements for Digital Inputs and Digital Outputs

3-72 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.6.5 Configuration with MasterPiece 40

AI-MVB AI-MVB

AI1_21U1 _________ NAME AI2_21U1 _________ NAME

1 _________________ ACT 1 _________________ ACT
4 _________________ REGADDR 5 _________________ REGADDR
110 _______________ CMDCODE 110 _______________ CMDCODE
0 _________________ AUXINFO1 0 _________________ AUXINFO1
0 _________________ AUXINFO2 0 _________________ AUXINFO2
1 _________________ NO_BREC 1 _________________ NO_BREC
0 _________________ NO_INT 0 _________________ NO_INT
1 _________________ NO_INTL 1 _________________ NO_INTL
4 _________________ NO_REAL 4 _________________ NO_REAL
RECEIVE _________ SOURCE RECEIVE_________ SOURCE
0 _________________ BLOCKED 0 _________________ BLOCKED
1 _________________ NET 1 _________________ NET
21 ________________ REMNODE 21 ________________ REMNODE
0 _________________ CYCLETIM 0 _________________ CYCLETIM
NO _______________ SORT_REF NO _______________ SORT_REF

Value references 1-16 Value references 1-16

AI21ST1U1 ________ REF1 AI21ST2U1 ________ REF1
AI21V1U1 _________ REF2 AI21V5U1 _________ REF2
AI21V2U1 _________ REF3 AI21V6U1 _________ REF3
AI21V3U1 _________ REF4 AI21V7U1 _________ REF4
AI21V4U1 _________ REF5 AI21V8U1 _________ REF5
T1AI21U1 _________ REF6 T2AI21U1 _________ REF6
0 _________________ REF7 0 _________________ REF7
0 _________________ REF8 0 _________________ REF8
0 _________________ REF9 0 _________________ REF9
0 _________________ REF10 0 _________________ REF10
0 _________________ REF11 0 _________________ REF11
0 _________________ REF12 0 _________________ REF12
0 _________________ REF13 0 _________________ REF13
0 _________________ REF14 0 _________________ REF14
0 _________________ REF15 0 _________________ REF15
0 _________________ REF16 0 _________________ REF16

Figure 3-34. Data MVB DB elements for Analog Inputs

3BSE 006 529R0001 Rev A 3-73

RCOM User’s Guide
Chapter 3 Configuration/Application Building

CN-MVB(DI-Counter) AO-MVB

CN21U1 ___________ NAME AO21U1 ___________ NAME

1 _________________ ACT 1 _________________ ACT
2 _________________ REGADDR 6 _________________ REGADDR
301 _______________ CMDCODE 302 _______________ CMDCODE
0 _________________ AUXINFO1 0 _________________ AUXINFO1
0 _________________ AUXINFO2 0 _________________ AUXINFO2
1 _________________ NO_BREC 0_________________ NO_BREC
0 _________________ NO_INT 0 _________________ NO_INT
7 _________________ NO_INTL 1 _________________ NO_INTL
0 _________________ NO_REAL 2_________________ NO_REAL
RECEIVE _________ SOURCE SEND _____________ SOURCE
0 _________________ BLOCKED 0 _________________ BLOCKED
1 _________________ NET 1 _________________ NET
21 ________________ REMNODE 21 ________________ REMNODE
0 _________________ CYCLETIM 16 ________________ CYCLETIM
YES ______________ SORT_REF YES ______________ SORT_REF

Value references 1-16 Value references 1-16

CNST21U1 _________ REF1 AO21STU1 ________ REF1
CN1_21U1 _________ REF2 AO21V1U1 ________ REF2
CN2_21U1 _________ REF3 AO21V2U1 ________ REF3
CN3_21U1 _________ REF4 0 _________________ REF4
CN4_21U1 _________ REF5 0 _________________ REF5
CN5_21U1 _________ REF6 0 _________________ REF6
CN6_21U1 _________ REF7 0 _________________ REF7
TCN21U1__________ REF8 0 _________________ REF8
0 _________________ REF9 0 _________________ REF9
0 _________________ REF10 0 _________________ REF10
0 _________________ REF11 0 _________________ REF11
0 _________________ REF12 0 _________________ REF12
0 _________________ REF13 0 _________________ REF13
0 _________________ REF14 0 _________________ REF14
0 _________________ REF15 0 _________________ REF15
0 _________________ REF16 0 _________________ REF16

Figure 3-35. Data MVB DB elements for Counter Inputs and Analog Outputs optional

Note 1: Further optional Data MVB’s are needed for the MP 40’s expansion units. See MP 40 User’s Guide.
Note 2: Further optional Data MVB’s are needed for the MP 40’s parameters if they shall be read or written.
REGADDR (=’Ident’) in the range of 33 to 238. The answer of Read MVB’s (33 to 238) is on ’Ident’ = 239/240.

3-74 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 3.6.5 Configuration with MasterPiece 40

PC Program in the Master (AC 55)

The PC program is the master node designed as described in the chapter PC Program Layout.
The use of type circuits is recommended. See chapter PC program layout.
The necessary function for MP 40 are:
• Cold start
• Normalization
• Clock synchronization
• Deblock of MVB for data polling
• Control of EXECUTE of MVB’s.

3.6.5.2 Parameters on the Slave Node (MP 40)

Parameters on the slave node (MP 40):
• Node number = 21
• Own telephone number = 1651 (no switchboard)
• Line type= Dial-up
• Duplex = Full
• Transmission speed = 1200 bit/s
• Number of bits = 8
• Stopbits = 1
• Parity = odd
• No. of preambles = 3
• Linestab = 2
• Carrdel = 2
• Chartout = 2
• Hang up time = 30
• Disconnect time = 10
• Polltimeout = 15.
No Application program is needed and no DB-elements for configuration.
For Parametrization see MP 40 User’s manual.

3BSE 006 529R0001 Rev A 3-75

RCOM User’s Guide
Chapter 3 Configuration/Application Building

3-76 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 4.1 Product Operation

Chapter 4 Runtime Operation

4.1 Product Operation

The AC 55 must be started (mode P1) to be able to communicate on the RCOM link:
• For starting the please see the documents Advant Controller 55 User’s Guide, AMPL
Configuration Advant Controller 100 Series and the Function Chart Builder
documentation.
• In case of a successful start-up the diagnostic display of AC 55 will show the following
display codes. See table below:

Table 4-1. Display Codes

Display
code
Significance
(LED)

P- Start-up

P1 normal operation

4.2 Operating Overview

After start-up of the AC 55 the following operations concerning RCOM can be controlled:
• From the PC program for activation of Command and Flow control
– Activate/stop sending of Data MVB’s (Read/Write).
– Activate/stop sending of Command MVB’s (Cold start, Warm start, Normalize,
Clock synchronization and Telephone commands).
• The configuration at the DB elements can be changed on line.
• The status information for the RCOM link in the RTU Status words can be displayed.

3BSE 006 529R0001 Rev A 4-1

RCOM User’s Guide
Chapter 4 Runtime Operation

4.3 Runtime Tutorial

A Runtime Tutorial is not included in this manual. The reader must be familiar with application
commands in the engineering station AS 100 Series ES. Please refer to the Function Chart
Builder documentation.

4.4 Operating Instructions

For description of commands for control of PC program and data base please refer to the
document AMPL Configuration Advant Controller 100 Series Reference Manual.

4.5 Runtime Operating Menus

Runtime operating menus are provided in the AS 100 Series ES Engineering Station. The reader
should be familiar with application commands in the engineering station AS 100 Series ES.
Please refer to the Function Chart Bilder documentation.

4-2 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 5.1 Hardware Indicators

Chapter 5 Maintenance

5.1 Hardware Indicators

The RCOM channel is built in the basic unit and does not need extra hardware and diagnosis.

5.2 Software Indicators

Software Indicators
The status of the control signals of each of the channels is available as an output of the related
DB element MVICHAN: The status may be observed with an AS 100 ES, e.g. if the outputs are
connected to any PC element (e.g. for connection to a Digital Output).
DSR Data Set Ready
DCD Data Carrier Detect
CTS Clear To Send
RI Ring Indicator.

RCOM Status
The RCOM Status is provided at AC 55 stations with the MVI channel in slave mode.
System errors related to the RCOM option are converted in RCOM system messages. Receiving
a system message a MVI in master mode sets the corresponding bit in RCOM status word 2.
The Status Word 2 is available at the terminal STATUS2 of the DB element MVINODE
in the master station.
Below the meaning of the bits of the Status Word 2 for AC 55 are explained.
Status Word 2 for AC 55 and corresponding Error Codes for CPU Diagnostic Display.

Table 5-1. Status Word 2 and Error Codes

Error
Status bit Description Significance
codes
Value bit 0 Slave restarted The slave has carried out a system cold start. 49,58
Value bit 1 Not used by AC 55
Value bit 2 Checksum error, application The CRC checksum of the RAM containing the 47
configuration data and the application program
was wrong.
Value bit 3 Not used by AC 55

3BSE 006 529R0001 Rev A 5-1

RCOM User’s Guide
Chapter 5 Maintenance

Table 5-1. Status Word 2 and Error Codes (Continued)

Error
Status bit Description Significance
codes
Value bit 4 Not used by AC 55
Value bit 5 Not used by AC 55
Value bit 6 Not used by AC 55
Value bit 7 Event queue full(1) At least one EQ is filled by 80%. 59
Value bit 8 Not used by AC 55
Value bit 9 Power failure A power failure has occurred. 4A
Value bit 10 I/O module error An analog or digital I/O error was detected 53
Value bit 11 Processor exception The processor executed an exception 05,2F,
(zero divide, address error etc.). 4C,4D,4E
Value bit 12 System overload A 3. or 4. activation of a task was executed by 41,42
the system software. This is caused by system
overload.
Value bit 13 Not used by AC 55
Value bit 14 Not used by AC 55
Value bit 15 Not used by AC 55
Value bit 16 Watchdog alarm The watchdog was not handled by the system 09,54
software, i.e. the system software is stalled.
Value bit17-31 Not used by AC 55
(1) ’Event queue full’ means that at least the event queue of one Event Set (DB element EVS(S), EVS (T))
is filled by 80%. For description of Event Sets see document. AMPL Configuration. Advant Controller 100
Reference Manual
The above mentioned errors cause RCOM system messages from slave to master
and the corresponding bits in status word 2 of the master are set.

5.3 Module Diagnosis

In case the system does not work, first check the status LEDs on the basic unit’s front. In case
the red FAULT LED is set or the green RUN LED is not set, restart the system by pressing INIT
with the start mode selector in CLEAR or AUTO position, after saving your application
program to PROM.
If the basic unit is working but only the RCOM connection does not work, check the cable and
connection of the modem as well as the application program, see next chapter.

5-2 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 5.4 Fault Finding and User Repair

The tool, e.g. AS 100 Series ES , delivers detailed error information in FCB’s ERROR REPORT
and MODULE DIAGNOSIS.
The AC 55 basic unit has unit address 0. The expansion units have unit addresses 1..4 in the
order they are connected to the basic unit. Problems with the RCOM line are in AC 55 always
reported in the basic unit with unit address 0.
Using the module diagnosis for unit address 0 you can mouse-click on the objects ’Device’,
’MVI channel’, ’MVI node’ and ’MVI data block’ in order to see detailed error information
about the RCOM line.
For further information please refer to the Advant Controller 55 User’s Guide
Chapter Fault Tracing and the Function Chart Builder documentation.

5.4 Fault Finding and User Repair

If you have followed the instruction in the preceding chapters, and still does not have a correct
working communication link after commissioning, please check the following, using the
AS 100 Series ES engineering station:
1. Are modems and cables correctly set-up?
The correct modem signals must be received by the MVI channel. When full duplex mode
for the modem signals is selected the signal Data Set Ready DSR, Data carrier detect DCD
and Clear to Send CTS must be set (also in telephony mode). In half duplex mode the DSR
must be set and DCD and CTS must toggle between 0 and 1. See Section 3.6.1.2, DB
Element for MVI Channel Characteristics MVICHAN.
Current values of DSR, DCD and CTS are available at the DB element MVICHAN. Note
that displayed values from the MVICHAN element on the AS 100 Series ES are not
synchronized to the actual value change of the signals, short pulses may not be displayed.
The modem signals are set-up by the modem or in full duplex mode they can be wired in
the 25 position connector on the modem cable (See Section 2.3, Modems and Cables).
2. Check the data base and PC application:
– Check that the remote node numbers (REMNODE) of the DB elements MVINODE
and MVB’s correspond to the (own) node numbers of all the slaves at the line. Check
the NET numbers also.
– In Master mode the Command MVB for Normalize/deblock must be built and sent to
the corresponding slave to get polled data/events from the slave.
– Data MVB for the actual data transfer must be defined. A SEND MVB in a slave
must have a corresponding RECEIVE MVB with the same NET and REGADDR
(IDENT) in the master and vice versa.
– The PC program for the flow control must be built and started (Not always necessary
in slave mode, see Section 3.4.2.2, PC Program in the Slave Node).
3. Are there any errors reported in the Error Report of the AC 55?
Error Reports are checked by connecting an Advant Station 100 Series ES to the AC 55.
see preceding section. Note that some errors are only reported once. Include a listing in
your answer.

3BSE 006 529R0001 Rev A 5-3

RCOM User’s Guide
Chapter 5 Maintenance

4. What Status Bits are set in the RTU Status Word?

Status bit 0 is set when the AC 55 has established connection to the RTU, see Section
3.6.1.3, DB Element for Node Configuration and Status MVINODE.
If you also know the answer to the following questions it will be easier to make further
analysis:
a. Is the installation of modems and cables made according to the description in the
manual ABB Master System Installation Rules. Note specially power supply and
connection to signal ground.
b. How is your control system configured? A block diagram with all node- and network
numbers is useful. Note also type of RTU, the master and the slaves on the link and
type of modem you are using.
c. Were there any significant changes (e.g. new communication board(s) added, new
modems) made in your configuration?
d. Is it possible to repeat your problem?
e. Have you found any way to circumvent the problem?
f. Are there any other observations, related to the problem, made?
A test tool for monitoring the status of the V.24 leads is useful for further analyze. The test tool
shows the status, with LED indicators, of the modem signals, data transmission (TD) and
reception (RD). In cases where an analyze of the data flow on the RCOM link is necessary, you
need a Data Link Analyzer that monitors and stores the signals sent on the link.

5-4 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Section 5.4 Fault Finding and User Repair

.
Start
AC 55

AS 100 Ser.ES:
Check the Module Diagnosis
Error Report?
concerning the unit address 0.
Yes Check the DB Elements
MVICHAN and MVINODE
No Parameters and ERR Output

Check the connected Modem

MVICHAN: - Power Supply
CTS= 0? - Cable
Yes
- Parameters (Backup/reset)
- Replace Hardware
No

Check the line (Loop Test, etc.)

MVICHAN Check the remote node
DCD= 0? - Power supply
Yes - Configuration (DB elements)
- Replace Hardware
No
Check the Status Words 1,2
Check Error Report

Figure 5-1. Fault-finding procedure

3BSE 006 529R0001 Rev A 5-5

RCOM User’s Guide
Chapter 5 Maintenance

5-6 3BSE 006 529R0001 Rev A

 RCOM User’s Guide
Index

INDEX
A P
AC 110 1-1 to 1-2 PC Program 1-11, 3-12, 3-15, 3-58
AC 400 1-1 to 1-2, 1-7 Point to point 2-3
AC 55 1-1, 1-12
Advant Controller 110 1-1 R
Advant Controller 400 series 1-1 RCOM 1-1, 1-14
Advant Controller 55 1-1 RCOM+ 1-1, 1-16
RTU Status 3-30
C
Cables 1-5 S
CCITT V.24 2-2 Status1 3-30
Clock Synchronization 3-53
Cold Start a Slave 3-48 T
Command MVB 3-47 Telephone Commands 3-55
Configuration 3-1, 3-19 Test tool 5-4

D W
Data MVB 3-40 Warm Start a Slave 3-50
DB Element CT 482 3-20
DB Element MVB 3-35
DB Element MVICHAN 3-21
DB Element MVINODE 3-28
DB Elements 1-11, 3-8, 3-13, 3-19

E
Engineering Tools 1-5
Event 3-34

H
Hardware
Cables 1-5
Modems 1-5

M
MasterPiece 200/1 1-1
MasterPiece 40 1-1
Modem 1-5
MP 200/1 1-1
MP 40 3-66
Multi-drop 2-3
MVB for Commands 3-47
MVB for Data Transfer 3-40
MVI Status 3-30

N
Normalize a Slave 3-52

3BSE 006 529R0001 Rev A i

RCOM User’s Guide
Index

ii 3BSE 006 529R0001 Rev A

3BSE 006 529R0001 Rev A
March, 1997