MS2−HDS400−2008

[Rel.400/411/412]

RTC Runtime
Function Manual
•• Harmonas-DEO, DOPC, DOFC, DOHS, DOBS, DOGS, DOMS, DOHL, and DOPL are registered trademarks of Azbil
Corporation in Japan.
•• Windows is a registered trademark of Microsoft Corporation in the United States and other countries.
•• Ethernet is a registered trademark of XEROX Corporation.
•• MELSEC is a registered trademark of Mitsubishi Electric Corporation, Ltd.
•• InTouch is a trademark of Invensys plc.
•• Other product names, model nos., and company names may be trademarks of the respective company.

Copyright, Notices and Trademarks

© 2012-2014 Azbil Corporation All Rights Reserved.

While this information is presented in good faith and believed to be accurate, Azbil Corporation disclaims the implied
warranties of merchantability and fitness for a particular purpose and makes no express warranties except as may be
stated in its written agreement with and for its customer.

In no event is Azbil Corporation liable to anyone for any indirect, special or consequential damages. The information
and specifications in this document are subject to change without notice.
 Table of Contents

Table of Contents

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
What is RTC Runtime?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Notations Used in This Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Abbreviations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Minor Version Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
References. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 1. Before Using RTC Runtime. . . . . . . . . . . . . . . . . . . . . . . . . 7

1.1 System Configuration Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.2 Initialization Files Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.3 CSV File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 2. Running RTC Runtime. . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.1 How to Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.2 Points to Keep in Mind When Exiting SE . . . . . . . . . . . . . . . . . . . . . . 11
2.3 Running RTC Runtime and RTC Editor Concurrently . . . . . . . . . . . 12
2.4 Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.4.1 Parameter Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 3. Online Screen Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3.1 Calling up a Screen (Sheet). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.2 Displaying the Parameter Values of Control Parts . . . . . . . . . . . . . . . 17
3.3 Color Change of the Parameter Links. . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.4 Parameter Display When Error Occurs . . . . . . . . . . . . . . . . . . . . . . . . 18
3.5 Extracting a Sheet Using Intersheet Parts. . . . . . . . . . . . . . . . . . . . . . . 19
3.6 Extracting a Sheet Using Job Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Chapter 4. How to Display Parameter Details and Tune

Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4.1 Displaying Parameter Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4.2 How to Tune Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.3 Displaying Capsule Parts Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.4 How to Tune FUNC Block Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

i
Table of Contents

4.5 Listing Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

4.5.1 Query. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.5.2 Search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.5.3 Data View List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.6 Mass Replacing Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
4.6.1 Replace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Chapter 5. Displaying and Changing Various Statuses. . . . . . . . . 33

5.1 Displaying and Setting I/O Debug Status. . . . . . . . . . . . . . . . . . . . . . . 33
5.2 FB Point Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Chapter 6. Sheet Self-Extraction Function from External

Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
6.1 Sheet Self-Extraction Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
6.2 How to Call up from External Applications. . . . . . . . . . . . . . . . . . . . . 36
6.2.1 Call-up from InTouch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
6.2.2 Call-up from User Application. . . . . . . . . . . . . . . . . . . . . . . . 36
6.2.3 Call-up from Face Plate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Chapter 7. Multi-Engineering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
7.1 Multi-Engineering Related Functions. . . . . . . . . . . . . . . . . . . . . . . . . . 37
7.2 Before Using Multi-Engineering Job with RTC Runtime. . . . . . . . . 37
7.3 Points to Keep in Mind in Multi-Engineering. . . . . . . . . . . . . . . . . . . 38

Chapter 8. Log Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

8.1 Log File Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
8.2 Contents of a Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

ii
 What is RTC Runtime?

Introduction
What is RTC Runtime?

RTC Runtime is Windows 7 application software that offers the following capabilities:

•• Enables sharing the jobs created with RTC Editor to provide online monitoring and an
online operating environment
•• Enables using a sheet created with RTC Editor as an operation monitoring screen to reduce
engineering man hours
•• Enables displaying on the sheet the processing values of control parts added to the RTC
sheet as well as choosing a control part to tune the parameters

The descriptions for SS in this manual are also applicable to SSH.

Notations Used in This Manual

This manual is written using the following notations:

Table -1. Notations for Menus, Commands, and Dialogs

Notation Description
[File] menu A menu name is indicated by enclosing it within square brackets ([ ]).
A command name is indicated by the name of the menu containing the
[File]
command enclosed within square brackets ([ ]).
A dialog name is indicated by the caption bar display of the dialog en-
[Sheet Information]
closed within square brackets ([ ]). The same rule applies to property
dialog
sheets.
A group box, text box, dropdown list, check box, or option button in a
[File name:]
dialog is indicated by enclosing it within square brackets ([ ]).
A button in a dialog or on a toolbar is indicated by enclosing it within angle
<OK> button
brackets (< >).

−1−
Introduction

Table -2. Notations for Mouse Operations

Notation Description
To press the mouse button and release it immediately. A mouse has right
Click and left buttons. Unless otherwise specified, “click” indicates the left but-
ton.
Right click To click the right button is called “right click”
To click the left button of a mouse twice quickly without moving the
Double click
mouse.
Drag To move a mouse while holding down the left button of the mouse
Drop To drag a mouse and release the left button on the target position

Table -3. Notations for Key Operations

Notation Description
<Enter> A key is indicated by enclosing it within square brackets (< >).
A plus sign (+) indicates a combination of key operations.
<Shift> + <A> indicates to press the <A> key while holding down the
<Shift> key.
<Shift> +<A> <Ctrl> + <A> indicates to press the <A> key while holding down the
<Ctrl> key.
<Alt> + <A> indicates to press the <A> key while holding down the
<Alt> key.
Arrow keys The collective name for the <→>, <←>, <↑>, and <↓> keys.

−2−
 Abbreviations

Abbreviations

The following describes the abbreviations relating to RTC Runtime and Harmonas-DEO
System used in this manual:

Table -4.

Names Meaning
CL Control Language
CSV Comma Separated Values
EB Exception Build
FB Function Block
DOFC Fieldbus Controller
DOBS Batch Station
DOGS Gateway Station
DOHS History Station
DOPC Process Controller
DOPC II Process Controller II
DOPC III Process Controller III
DOPC IV Process Controller IV
DOPL PLC Linker
DOPL II PLC Linker II
DOSS Supervisory Station
DOSS_H History DEO Supervisory Station
BS DOBS (Node Name)
GS DOGS (Node Name)
FC DOFC (Node Name)
FLC Flex Distributed Controller
HS DOHS (Node Name)
PC4 DOPC IV (Node Name)
PL DOPL (Node Name)
PL2 DOPL II (Node Name)
PRC : DOPC (Node Name)
RTC Real Time CoSEE (Node Name)
SS DOSS (Node Name)
SSH DOSS_H (Node Name)
Extended Process Controller
XPC
DOPC II/DOPC III (Node Name)

−3−
Introduction

Terminology

The following describes the terms relating to RTC Runtime and Harmonas-DEO System used
in this manual:

Table -5.

Notation Description
The part to handle the programs written in CL, which is the control sequence
CL part
language for PRC, XPC, PL2, FLC and FC
Custom view The view which can be defined for individual control parts on a sheet
The icon representing a container (sheet) in the job structure.
Container icon
Sometimes called simply a “container”
Container part The part that iconizes a sheet. Sometimes called simply a “container”
Class view The view which can be defined for each type of control part
One sheet corresponds to one drawing. The parts pasted using RTC Editor
Sheet
can also be displayed using RTC Runtime.
Job The unit of RTC works
The hierarchic structure displayed in the child window of RTC Editor and
Job structure RTC Runtime that describes the inclusion relation of sheets. It consists of the
job tree and job repository.
The part to configure the control of Harmonas-DEO. There are container
Control part
parts, point parts, logical component parts, CL parts, block parts, and others.
Part Displayed on the RTC tool bar to be pasted on sheets
A collection of parts buttons by functionality. There are the picture RTC tool
RTC tool bar
bar, control RTC tool bar, and others.
Port Indicates the start and end points of a parameter link on a control part
Point link A line graphically displaying the reference relation between control parts
Point part The part indicating the points of PRC, PL, XPC, PL2, FLC and FC
Logical The part indicating various functions of the logic points of PRC, PL, XPC,
component part PL2, FLC and FC
FB point A collection of blocks that carry out control processing
Block The control unit finer than a point
Block part The part indicating a block
Job part The part to link control parts across jobs

−4−
 Minor Version Upgrade

Minor Version Upgrade

R411 and R412 are minor version upgrades of R400. Following marks are attached to the
changes after R400.
[R411 or later] : Description about R411 and R412.
[R412] : Description about R412.

References

Table -6.

Document Number Document name

MS2-HDS400-2002 Harmonas-DEO RTC User’s Guide
MS2-DEO300-2003 Harmonas-DEO DOSS User’s Guide
MS2-HDS900-6001 Harmonas-DEO Parameter Reference Manual

−5−
Introduction

MEMO

−6−
 1.1 System Configuration Requirements

Chapter 1. Before Using RTC Runtime

This section describes the necessary settings before using RTC Runtime and what you need to
know when using RTC Runtime.

1.1 System Configuration Requirements

RTC Runtime requires a personal computer running Microsoft Windows 7, Windows Server
2003 ([R412] requires Windows Server 2008) as the operating system.

■ ■Personal computer system required for RTC Runtime

•• Basic software (Operating system)
– Windows 7 ([R412] requires 64bit edition)
– Windows Server 2003 ([R412] requires Windows Server 2008 64bit edition)

•• Recommended system configuration for running RTC Runtime

– CPU : 1 GHz or faster 32-bit (x86) processor
([R412] requires 64-bit (x64) processor)
– Memory : 1 GB or higher
– Display resolution : 1024 × 768 or higher
Medium 125% size is recommended.
– Mouse
– Keyboard
– Monitor : 17-inch monitor or larger recommended
– Hard disk : Minimum of 25 MB free space is required on the hard disk in order
to install RTC Runtime. An additional 100 MB or more is recom-
mended for storing the database.
– Hardware key : Attached to a parallel port of the personal computer

Note When the disk is occupied by other job data or when the media does not have
enough free space, there may be cases where RTC functions as well as file output or
job startup/termination cannot be performed.
Use RTC with enough free space allocation.

Note Physical memory shortage occurs if the size of job data is too large or other applica-
tion programs use large memory. Physical memory shortage make RTC work slower.
Please add more memory if needed.

−7−
Chapter 1. Before Using RTC Runtime

1.2 Initialization Files Settings

Before running RTC Runtime, check to see if the conditions in each entry in Table 1-1 are set
properly. RTC Editor will carry out the setting automatically when RTC Runtime is started
from SS where jobs were edited with RTC Editor. When RTC Runtime is started from any
other nodes, you need to carry out the setting.

These initialization files are located immediately under the installed directory of Windows
(C:\WINDOWS by default).

Table 1-1. Initialization Files Check List

Name of
What to Check
Initialization File
This initialization file is shared with RTC Editor. When RTC Runtime is started
from SS other than the one edited with RTC Editor, copy the rtcedit.ini file from
the SS where editing was performed.

Check if the following items are set properly.

[RTCRUN]

ParamTuningAutoSave=TRUE
Specifies whether or not to automatically reflect the results of parameter tun-
ing on the sheets.

ParamTuningPermit=TRUE
Restricts or allows parameter tuning. When restricted, the <Settings> button
will not be displayed in the Parameter List dialog.

PointQueryParamPerSec=50
Specifies the parameter access speed (parameters/sec) to the controller when
rtcedit.ini
a query is made in the [Point Query] window. The upper limit is 50 and the
lower limit is 10. If the value is invalid or unspecified, the value 50 is set.

EnableSheetControl=TRUE
Specifies whether or not to control the number of sheets that can be opened
concurrently.

NumOfMaxSheets=3
Specifies the maximum number of sheets that can be opened concurrently
when controlling the number of sheets. The upper limit is 10 and the lower
limit is 0. If the value is invalid or unspecified, the value 0 is set.

DisplaySheetControlMsgBox=TRUE
Specifies whether or not to display a message box when the number of sheets
exceeds the maximum number specified when controlling the number of
sheets.
TRUE: A message box is displayed but the result is not output to a log.
FALSE: A message box is not displayed but the result is output to a log.

−8−
 1.3 CSV File

Name of
What to Check
Initialization File
When RTC Runtime is started from some place other than the SS edited with RTC
Editor, copy the udpman.ini file from the SS where editing was performed. (Refer
to Chapter 7 in the case of multi-engineering.)

Check if the following items are set properly.

[DASubsystem]

DASubsystem1=DEODH
udpman.ini Specifies the name of the DA subsystem.

[DEO]
JobDirectory=
Specifies the job directory created using RTC. Copy the specified string in the
JobDirectory in the [Browser] section of the rtcedit.ini file.

Example: JobDirectory=D:\jobdir\sample\
Various CSV files should be created and present in the \it directory under this
directory.
Specifies the settings relating to the log function.

The operating log of RTC Runtime is set to be output to a file by default.

englp.ini
[RTCRUN]
OutputLogFile=TRUE

1.3 CSV File

The CSV file in Table 1-2 is required in the \it directory immediately under the job directory
run by RTC Runtime (Refer to Chapter 7 in the case of multi-engineering).

Table 1-2. CSV File Check List

Name of CSV File What to Check

Check if the node information (node number and IP address) and time stamp
node.csv
are set properly.

−9−
Chapter 1. Before Using RTC Runtime

MEMO

− 10 −
 2.1 How to Start

Chapter 2. Running RTC Runtime

This section describes the startup procedure of RTC Runtime and the points to keep in mind.

2.1 How to Start

The following describes how to start RTC Runtime. Check the conditions described in
Chapter 1 before carrying out the steps below.

Step 1 Start RTC Runtime from the [Start] menu.

Choose [Start] → [Programs] → [DEO] → [RTC Runtime] in the menu.

Step 2 SE starts automatically if SE is not already running. The job specified in the initial-
ization file opens at the same time. Switch to a job that conforms to the job SE is
reading if necessary.

Note If you try to open a job with RTC Runtime that does not conform to the
job SE is reading, data will not be displayed.

Step 3 Read the following chapters on how to operate RTC Runtime after opening a job.

2.2 Points to Keep in Mind When Exiting SE

RTC Runtime uses SE (and data-export server) as its data access engine; therefore, make sure
to do the following when exiting SE.

Step 1 When SE is exited, the message prompting to quit RTCRUN appears.

Click the <OK> button to quit RTCRUN.

Step 2 In Step 1 , you may be prompted to save the sheets. Choose either <Yes> or <No>
button and quit RTCRUN.

Note If you choose <Cancel> in the steps above, make sure to quit RTCRUN before restart-
ing SE. Otherwise SE cannot be restarted.

− 11 −
Chapter 2. Running RTC Runtime

2.3 Running RTC Runtime and RTC Editor Concurrently

There are certain restrictions on concurrently running more than one RTC Runtime and/or
RTC Editor on the same SS as shown in Table 2-1. Table 2-1 describes whether “Process 1” and
“Process 2” are concurrently executable or not for the same job and different jobs.

Even if executable, however, the same sheet cannot be opened concurrently by more than one
process. Close the open sheet, and then open the sheet using another process.

Table 2-1. Running Multiple RTC Runtimes and RTC Editors

Process 1 Process 2 Job(s) Used Executable?

RTC Runtime RTC Runtime Same No
RTC Runtime RTC Runtime Different Yes
RTC Runtime RTC Editor Same Yes *
RTC Runtime RTC Editor Different Yes
RTC Editor RTC Editor Same No
RTC Editor RTC Editor Different Yes

* Try to avoid opening the same file concurrently by RTC Runtime and RTC Editor.
* When the same file is concurrently opened by RTC Runtime and RTC Editor, do not
operate to change job data such as that related to node changes, adding or deleting
parts, or point generation,because such changes may result in data inconsistencies.

2.4 Help

Explanations of the operations and functions can be displayed by executing the [Help] com-
mand from the menu.

■ ■Help
Executing the [Help] → [Help] commands displays RTC Runtime Manual (PDF File).

■ ■Version information
Executing the [Help] → [About RTC Runtime] commands displays the [About RTC Runtime]
dialog box for the RTC Runtime.

− 12 −
 2.4 Help

2.4.1 Parameter Reference

Select [Help] → [Parameter Reference] from the menu to display the [Parameter Reference]
window. In the [Parameter Reference] window, explanations on the parameter of a point can
be displayed. The [Parameter Reference] window can also be displayed by double-clicking
a fixed character string in the tuning sheet for Control Parts where a parameter name is
displayed.

Note No explanation on the parameter of a block will be displayed.

■ ■Search by parameter name

With the [Search the text] check box being off, entering a parameter name in the combo box
in the lower window and then clicking the <Search> button will make the explanations on the
parameter entered by the user appear in the window.
If the search has found more than one Candidate, clicking the <Prev> or <Next> button will
make the Candidates appear sequentially. Uppercase letters and lowercase letters of the pa-
rameter name entered in the combo box are treated as being the same.
If the letters of a parameter name other than its initial letter is unknown, entering the known
letter and then pulling the list in the combo box down will make the Candidates of the pa-
rameter name appear.

Note When searching for a parameter with a subscript (an array-type parameter such as
CIDSTN(1), DODSTN(1), and the like), it is required to enter all of the letters includ-
ing subscripts (typing “CIDSTN(1)” instead of “CIDSTN” is required). In the case of a
search by parameter name, which causes perfect matching retrieval, an omission
of a subscript will make it impossible to find the desired parameter. If you want to
search by specifying a portion of a parameter name, you will need to perform full-
text searching by using the desired character string, as explained below.

■ ■Full-text search by a desired character string

With the [Search the text] check box being on, entering the character string to be searched for
in the combo box and then clicking the <Search> button will perform a search for a parameter
name as well as its explanatory text, resulting in the explanations on the parameter comprising
the character string entered by the user being displayed in the window.
If the search has found more than one Candidate, clicking the <Prev> or <Next> button will
make the Candidates appear sequentially. Uppercase letters and lowercase letters of the pa-
rameter name entered in the combo box are treated as being the same.

− 13 −
Chapter 2. Running RTC Runtime

MEMO

− 14 −
 3.1 Calling up a Screen (Sheet)

Chapter 3. Online Screen Display

On a sheet created with RTC Editor as it is, RTC Runtime displays the current values of the
controller next to the output ports of control parts on the sheet. None of the parts on the
sheet can be edited with RTC Runtime. You may choose control parts on the sheet with RTC
Runtime, but you cannot move parts or edit parts as you did with the RTC Editor.
The following describes how to operate RTC Runtime on a sheet.

3.1 Calling up a Screen (Sheet)

When a job is opened using RTC Runtime, only the job structure is open at startup.
Use one of the following four methods to call up a sheet.

1) Click [Open a sheet...] from the [File] menu. The container selected in the job structure
opens.

2) Click [Open sheet from sheet number] from the [File] menu. The [Sheet Number] dia-
log opens. Enter the sheet number and click <OK> to open the sheet.

The sheet number of every sheet is set to 0 by default. You need to open [File] → [Sheet
Information] with RTC Editor and set the sheet numbers in advance.

Figure 3-1. The [Sheet Number] dialog

− 15 −
Chapter 3. Online Screen Display

3) Double-click the intended container in the job structure. The sheet corresponding to
the container opens.

4) Specify the sheet number in the InTouch script and open the sheet. The detail of this
function is described in 6.2.1.

The access time to a screen (sheet) at startup is typically 2 seconds. The time varies slightly
depending on the number of parts called up on the sheet.

Usually the number of displayable parameters at a time is approximately 400 parameters/

second. A typical sheet contains about 100 control parts, and in this case, the number of dis-
playable parameters at a time is approximately 80 parameters/sheet.
Therefore, the guideline is to display at most 4 to 5 sheets at once. If you set to control the
number of sheets that can be opened concurrently, you cannot open more than the maximum
number of sheets you specified in the initialization file. For how to set the
condition, refer to 1.2.

− 16 −
 3.2 Displaying the Parameter Values of Control Parts

3.2 Displaying the Parameter Values of Control Parts

When a sheet opens, the current parameter values of the controller are displayed next to the
output ports of the control parts as shown in Figure 3-2. Figure 3-2 shows the default view dis-
play of control parts. If the custom view exists for control parts, the custom view is displayed
instead. If the class view exists, the class view is displayed.

Start Signal Pump Output Signal Pump Output

PVFL OP S0
Digital Input Digital Composite Digital Output
1 D1 Start

D1027001 DC027001 D0027001

D2

Stop Signal
PVFL
Digital Input 0

D1027002

Figure 3-2. Sample Sheet Display of Control Parts on RTC Runtime

Table 3-1. Parameter Display Specifications

Item Specification
With respect to an output port in between, a parameter value is displayed on
Position the opposite side (lower right of the output port) of the default position of the
parameter name (upper right of the output port).
Color Green
Only the values of the parameters satisfying the following condition may be
displayed. If a parameter does not satisfy the following condition, the value
Parameters displayed
will not be displayed.
1) An output parameter that is linked to other parameters
The format of the value displayed for each data type is indicated.
1) Numeric data type: The display length is up to 5 digits, including the
decimal point.
A negative number can use up to 6 digits, includ-
ing a minus sign.
If the number of digits in a number exceeds the
Format maximum length, the number is displayed in ex-
ponential form (e.g., 1.23e+004).
Engineering units are not used. A NaN value is
displayed as “----”.
2) Logical data type: Displays “1” for TRUE and “0” for FALSE.
3) Enumerated data type: Displays a string corresponding to an enumerated
value.
1 second The cycle may be longer, depending on the num-
Update cycle
ber of parameters displayed on a sheet.

Note The parameter view displays the values set for job data in RTC. The values displayed
may be different from the actual values in the controller.
If the values for job data in RTC are not the same as the values in the controller, start
the RTC editor and upload the control data to update the job data in RTC, which will
update the display in the parameter view as well.

Note The ports of Logic Component Parts are displayed according to the setting of the
status input reversal function (S1REV(N)-S3REV(N) parameter). It is displayed ac-
cording to the value set for the part in RTC Editor.

− 17 −
Chapter 3. Online Screen Display

3.3 Color Change of the Parameter Links

The colors of logical parameter links change according to output parameter values, as shown
in Table 3-2. The link color of the parameters other than logical parameters is fixed in black.

Table 3-2. Link Colors of Logical Parameters

Value of Output Parameter Value

Parameter Link Color
Parameter Displayed on a Sheet
TRUE 1 Red
FALSE 0 Blue

Note However, the colors will be changed only when any of the following parts is con-
nected to the final connection destination given in the link sheet.
- Point Parts
- Block Parts
- Box Parameter Parts
For example, link colors will not be changed when both ends of the link are
Intrasheet Parts or when one end is Intrasheet Parts and the other end is Frame
Parts.

3.4 Parameter Display When Error Occurs

The parameter display when an error occurs looks like the following:

Table 3-3. Parameter Display When Error Occurs

String Displayed Description

@@@@ Configuration mismatch
#### Parameter value not available due to a cause other than the above

•• The error status description is output in the form of a log/journal.

•• If data access cannot be started, a message box saying “Unable to register a parameter” ap-
pears. The display of the parameter that could not be registered becomes blank.

•• The error displays above are common to both parameters on sheets and parameters on tun-
ing sheets. The point query function is also in common. Refer to Chapter 4.

− 18 −
 3.5 Extracting a Sheet Using Intersheet Parts

3.5 Extracting a Sheet Using Intersheet Parts

An RTC sheet linked to another sheet by Intersheet Parts can be automatically extracted to
the linked sheet by double-clicking the left button of the mouse on the Intersheet Parts. If
Intersheet Parts (output side) are linked to other Intersheet Parts (input side) on different
sheets, the sheets to be extracted are not unique. Therefore you need to choose a sheet from
the dialog to extract it.

Figure 3-3. Dialog Displayed When Intersheet Parts (Output Side) Branches into More Than
One Sheet

When you double-click Intrasheet Parts, the sheet scrolls automatically to display another
Intrasheet Parts linked to it on the middle of the sheet.

− 19 −
Chapter 3. Online Screen Display

3.6 Extracting a Sheet Using Job Parts

When you double-click Job Parts, the corresponding Job Parts linked to it is displayed. The
destination Job Parts are displayed in the selected state on the middle of the sheet. (If a desti-
nation Job Parts are not set or does not exist, nothing is displayed.)
If the job where the destination Job Parts are located is not open, start RTC Run time auto-
matically and open the destination job.
If the sheet where the destination Job Parts are located is not open, the corresponding sheet
opens.

− 20 −
 4.1 Displaying Parameter Details

Chapter 4. How to Display Parameter Details and

Tune Parameters
RTC Runtime can display parameter details and tune parameters for each control part. It can
also list and mass replace parameters. The following describes how to display parameter de-
tails and tune parameters. However detail display for control parts is available only with point
parts, logical component parts, and block parts. Detail display is not available with CL parts.

4.1 Displaying Parameter Details

Double-clicking the left button of the mouse on control parts on a sheet displays the Parameter
List dialog.

The Parameter List dialog displays a logical tag name and NAME (tag name) on top of the
[Page1] tab, followed by other parameters in alphabetical order. The current values of the
parameters are displayed on each line. The parameter description is displayed in parentheses
next to the parameter name, and the current value is displayed in the edit box.

The current values of the parameters displayed are obtained from the controller if the pa-
rameter access lock is Read Only, Operator, Engineer, or RTC. The values held by control
parts are displayed for the other parameters that do not exist in the controller and, as excep-
tions, MODNUM (module number) and SLOTNUM (slot number). If the parameter does
not exist in the controller and does not exist in the part, then the parameter value becomes
blank. For the parameter access lock, refer to “Harmonas- DEO Parameter Reference Manual
(MS2-HDS900-6001)”.

As shown below, the display format differs slightly from the specifications of the parameter
value display on a sheet.

The error display while accessing data has the same specifications as the parameter display on
a sheet. Refer to 3.4.

− 21 −
Chapter 4. How to Display Parameter Details and Tune Parameters

When displaying numeric data in the form of a single-precision real number in the Parameter
List dialog and Parameter Setting dialog, the data is displayed according to the following rules:

•• Because the number of significant digits for floating-type data is 6 or 7, numeric data dis-
play has the form “sign (1 digit) + numeric value (up to 7 digits, not including the decimal
point)”.

•• If a number with more than 7 digits is entered, the 8th digit is rounded to form a 7- digit
number. A number that is 9999999.5 or larger or -9999999.5 or less is displayed in expo-
nential form.
(Example) 1234.5678 → 1234.568
16777.215 → 16777.21
–16777215.0 → –1.677722E+007

•• Anumber that is greater than or equal to 0, and less than or equal to 0.1, is displayed in 0.00
(decimal) form.

•• Ineffective 0s after the decimal point are suppressed.

(Example) 0.1000 → 0.1

•• A NaN value is displayed as “- - - -”.

Figure 4-1. The Parameter List Dialog and Parameter Setting Dialog

Double-clicking a fixed character string where a parameter name is displayed will open the
[Parameter Reference] window and then make the explanations on the parameter appear in
the window. For more details regarding Parameter References, see “2.4.1 Parameter Reference”.

− 22 −
 4.2 How to Tune Parameters

4.2 How to Tune Parameters

The <Write> button to the right of the current value of a parameter in Figure 4-1 indicates that
the parameter can be tuned.

The <Write> button to the right of the current value of a settable parameter is displayed when
both of the following conditions are satisfied:
1) The ParamTuningPermit key in the [RTCRUN] section of the rtcedit.ini file is set to
TRUE (refer to 1.2).
2) The parameter access lock is Operator or Engineer.

Clicking the <Write> button displays the Parameter Setting dialog. Figure 4-1 shows the state
that the current value of alarm priority is being changed from “LOW” to “JOURNAL” by click-
ing the <Write> button of ALPRIOR (alarm priority).

Specify a setting value and click the <OK> button. The value is written in the controller at
this timing (provided the access level is permissible). Click the <Cancel> button to cancel the
setting.

Note The access level to set a parameter is “Operator” by default. To change the access
level, do so from the System Status screen of the Standard DEO screen.

To tune a logical type or enumerated type parameter, choose a setting value from a list of
choices in the combo box prepared in advance to input the value. For a numeric data param-
eter, a value can be entered directly.

If the rate of change of the setting value with respect to the current value of a numeric type
parameter is 1.5 or greater, or 0.5 or less, the confirmation dialog appears (rate of change =
setting value / current value). Data setting becomes effective only when the <OK> button is
clicked. An operator change log is recorded at this time and stored in the history database.

Figure 4-2. The Dialog Shown When the Rate of Change of Setting Value with respect to
Current Value Is ≥1.5 or ≤ 0.5

A parameter value set in the controller is stored simultaneously in the parts on the sheet as
the parts information of the RTC job. A parameter value set is also stored in the parts when
closing the sheet. You can set whether or not to save it automatically using the rtcedit.ini file.
Refer to 1.2.

− 23 −
Chapter 4. How to Display Parameter Details and Tune Parameters

4.3 Displaying Capsule Parts Parameters

Double-clicking the left button of the mouse on a capsule part opens the [Capsule Part]
dialog. Figure 4-3 shows a pump control part where two digital input points and a digital
composite part are encapsulated. The output parameter value of this pump control part is dis-
played on the opposite side of the parameter name with respect to the “Control Signal 1.OP”
port in between, as is the case with the control parts.
The parameter display specifications on a sheet are the same as is the case with the control
parts.

PMP001 Pump Control Control Output1

Control
Signal1.OP S0
Pump Control Digital Output
Start

PMPCTL01 D0027002

Figure 4-3. Sheet and Detail Display of Capsule Parts

Choosing a control part from the list of displayed capsule parts and clicking the <Detail> but-
ton displays the Parameter List dialog for each control part. The operations from this point on
are the same as described in 4.1 and 4.2.

− 24 −
 4.4 How to Tune FUNC Block Parts

4.4 How to Tune FUNC Block Parts

When you open the tuning sheet for FUNC block parts, the [Graph] page is displayed as
shown in Figure 4-4, in addition to the standard properties page.
Using this page, you can tune the FUNC block parts inputs 1 through 12 and outputs 1
through 12.

Figure 4-4. [Graph] page for FUNC block parts

Previous values are presented from controller values and input values are entered by the user.
By clicking each <Set> button, the corresponding input value is set to the controller. In addi-
tion, a graph is shown on the right side of this page in which the horizontal axis is for inputs
and the vertical axis is for outputs. Two graph lines will be shown representing previous and
input values. After entering values in the “Input value” boxes, confirm the graph display to
check that the input data are correct before clicking the <Set> button to set the values.

Note Such inputs as those to shift the graph back to the left side (Example: Inputs 1 and
2 are entered as 5 and 4 respectively) will be treated as errors upon setting. The
values should be sequentially increased downwards (Example: Values 1, 2, and 4 are
entered for inputs 1, 2, and 3 respectively).

− 25 −
Chapter 4. How to Display Parameter Details and Tune Parameters

4.5 Listing Parameters

Selecting a job structure with RTC Runtime and choosing [Browser] → [Point Query] menu
displays the [Point Query] window. You can list parameters as well as search, arrange, and file
output the parameters listed in this window.

Figure 4-5. The [Point Query] Window

− 26 −
 4.5 Listing Parameters

4.5.1 Query
Opening the [Point Query] Window, entering the query conditions, and clicking the <Query>
button lists the parameters in the data view list in the lower part of the window. Available
parameters are parameters shown in [Select ParameterName] dialog. Specify the query condi-
tions as follows:

Table 4-1. Specifying Query Conditions

Item to
Description
Specify
Enter the node number to inquire. If not specified, all nodes become the subjects of
query.
When entering more than one node, separate the numbers with commas.
Node Num
Clicking the <Select Node> button displays the Node Selection dialog.
You can select a node number in the dialog. You may select more than one node. The
selected node numbers are added to the edit box.
Specify the point name to inquire.
You may use the wild cards “*” and “?”, for example: FL*, NM00?.
When specifying more than one point name, separate the names with commas.
Point Name
Clicking the <Select Point> button displays the [Load Pointname] dialog. You can
select the point name list file in which the point names are written. The point names
written in the point name list file are added to the edit box.
Specify the parameter name to inquire.
When specifying more than one parameter name, separate the names with commas.
Parameter
Clicking the <Select ParameterName> button displays the [Select ParameterName]
Name
dialog. You can select a parameter in the dialog. The selected parameter is added to
the edit box.
Specify the point type to inquire. If not specified or “ALL” is specified, all point types
become the subjects of query.
Point Type When specifying more than one point type, separate the point types with commas.
Clicking the <Select Point Type> button displays the Point Type Selection dialog. You
can select a point type in the dialog. The selected parameter is added to the edit box.
Condition Specify the conditions to narrow down the result.
You can save query conditions in a file.
Click the button to open the Standard File Selection dialog. Specify the name of the
<Export>
file and the folder to save the conditions to.
button
The data to be saved consists of node numbers, point names, parameter names, point
types, and conditions for query.
You can import query conditions in a file.
<Import> Click the button to open the Standard File Selection dialog. Specify the query condi-
button tions of the file to import. The query conditions in the file are imported to the Query
Group.

− 27 −
Chapter 4. How to Display Parameter Details and Tune Parameters

Condition Expression

Condition Logical operator Condition

( Condition )

NOT Condition

Parameter Comparison
Expression Value
name operator

Logical operation AND

expression

OR

Parameter name Parameter name

Comparison
operator =, &=, <>, >, <, >=, <=

Value Numeric value, string, *, ?, 'string', "String" [R411 or later]

Figure 4-6. Formats for Specifying Conditions

Table 4-2. Specifying Conditions — Operators

Operators Description
AND
Logical operator
OR
< Less than
> Greater than
< = Less than or equal to
Comparison
> = Greater than or equal to
operator
< > Not equal to
= Equal to (i.e., identical)
& = Including (i.e., including the strings of values of specified data)
() Parentheses

•• Specifying Conditions — Priority of operators

The priority of operators is shown in descending order:
1. ( )
2. Comparison operator
3. NOT
4. Logical operator

− 28 −
 4.5 Listing Parameters

4.5.2 Search
You can search the data that matches certain search conditions among the data displayed in
the data view list.
The data found becomes the selected state. Clicking the <Search> button further changes the
data to the selected state one by one in the direction of the search. Specify search conditions
as follows:

Table 4-3. Specifying Search Conditions

Item to Specify Description

String Enter a string to search.
Specify a parameter to search.
Parameter If a parameter is not specified, all parameters listed in the data view list be-
come the subjects of search.
If marked, upper and lower case letters of the string entered are distin-
Distinguish upper
guished, and text strings that accurately match the string are searched. If not
and lower case letters
marked, upper and lower case letters are not distinguished.
<Up> and <Down>
Specify the direction to search.
radio buttons

4.5.3 Data View List

The data view list is located in the lower part of the window and used to display the results of
the query.
You may arrange and file output the result displayed in this list.

Table 4-4. Data View List

Item Description
The header is located in the upper part of the list and indicates parameters.
Clicking the header arranges the data using the parameter displayed in the
Header header as a key. You may drag the line between the column headings to change
the header width. Double-clicking the line between the column headings adjusts
the header width to the maximum data length.
Displays the parameter values with point names on top. The data display formats
of parameters follow the same rules for the Parameter List dialog. Refer to 4.1.
Clicking the entry changes it to the selected state. You may select more than one
Data entry by clicking them while holding down the [Ctrl] key or [Shift] key.
Clicking the <Replace> button when data entries are selected displays the
[Replace] dialog in the state that the point names of the currently selected data
entries are added to the point name list of the [Replace] dialog.
This outputs the data displayed in the data view list to a CSV format file. The data
<Output> button
is output to a file directly under the job directory by default.

Restriction Due to the restrictions inherent in the Windows OS, only up to 224 parameters
can be displayed on the header. When more parameters are specified, no header
is displayed.

− 29 −
Chapter 4. How to Display Parameter Details and Tune Parameters

4.6 Mass Replacing Parameters

Selecting a job structure with RTC Runtime and choosing [Browser] → [Point Query] menu
displays the [Point Query] window. Clicking the <Replace> button in this window displays
the [Replace] dialog with which you can mass replace parameters.
The default RTC Runtime access level for replacing parameters is “Operator,” which is the
same level as in the case with tuning parameters.

Note Because the mass replace feature for parameters does not display the current values
of parameters, make sure to check the current values using the Point Query function
before carrying out mass replacing. In addition, be aware that the current values of
parameters before replacing (i.e., previous values) will not be recorded in a log. For
the details of the log function, refer to Chapter 8.

Note The mass replace feature for parameters can only be used to modify controller val-
ues. Modifications made using this feature will not affect the job data parameters
in RTC, and so the values displayed in the parameter view may be different from the
values in the controller. To update the job data in RTC to reflect the parameter values
in the controller, start the RTC Editor and upload the data from the controller.

Figure 4-7. The [Replace] Dialog

− 30 −
 4.6 Mass Replacing Parameters

4.6.1 Replace
Opening the [Replace] dialog, specifying a point name and parameter, and clicking the
<Replace> button allows you to mass replace the parameter. Available parameters are param-
eter shown in [Select parameterName] dialog.

Table 4-5. Specifying Replacement Conditions

Item Description
Set the point name to replace.
If you click the <Add/Edit> button without selecting a point name in the list box,
the [Specify point name] dialog appears, and you can add a new point to the list
box. Clicking the <Add/Edit> button with a point name selected allows you to
edit the point name that has already been set.
Clicking the <Del> button with a point name selected in the list box allows you
Specify point
to delete the point name from the list box.
name
Clicking the <Import> button opens the File dialog, and you can select the selec-
tion list file. The point names written in the point name list file are added to the
list box.
Opening the [Replace] dialog after selecting data from the data view list in the
[Point Query] window adds the point name of the selected data to the point
name list in the [Replace] dialog.
Set the parameter and its value to replace.
If you click the <Add/Edit> button without selecting a parameter in the list box,
the [Specify parameter] dialog appears, and you can add the parameter and its
value to the list box. Clicking the <Add/Edit> button with a parameter selected
allows you to edit the parameter and its value that has already been set.
Clicking the <Del> button with a parameter selected allows you to delete the pa-
Specify parameter rameter and its value from the list box.
Clicking the <Select Parameters> button displays the Parameter Selection dialog
that allows you to select and specify a parameter from the dialog. This is the same
feature as described for the [Point Query] window.
Clicking the <Import> button opens the File dialog, and you can select the pa-
rameter assignment file. The parameter and its value are written in the form of
“parameter name = value” in the parameter assignment file.
The result of the replace operation is displayed in the list box.
Setting status Clicking the <Save> button opens the File dialog, and you can save the current
display of the setting status in a text file.

Restriction Do not minimize other windows on RTCRUN (The [Point Query] window, the main
RTCRUN window, etc.) while a replacement process is running. If minimized, the
window cannot be restored to its normal size when the task bar button is clicked.
If this happens, restore this condition by using “Switch to” from the [Applications]
tab of the task manager after the process has been completed.

− 31 −
Chapter 4. How to Display Parameter Details and Tune Parameters

MEMO

− 32 −
 5.1 Displaying and Setting I/O Debug Status

Chapter 5. Displaying and Changing Various Statuses

5.1 Displaying and Setting I/O Debug Status

Selecting a job structure with RTC Runtime and choosing [Status] → [Debug Status] menu
displays the [Debug Status] dialog. You can display and set the I/O debug status in this dialog.

Figure 5-1. Debug Status Display

Selecting a node from the node specification list in the [Debug Status] dialog displays the
current debug status of the selected node (“NORMAL” or “DEBUG”). If the status cannot be
displayed, “####” appears.

To change the current debug status, click the <NORMAL> or <DEBUG> button in the Debug
Request section. After the confirmation dialog appears, the value is changed.

Note You cannot change the debug status when the node status of the controller is set to
RUN. Change it to IDLE before carrying out the debug status change.
Also the debug status can be changed only when the access level is “Engineer”.

− 33 −
Chapter 5. Displaying and Changing Various Statuses

5.2 FB Point Status

Selecting a job structure with RTC Runtime and choosing [Status] → [FB Point Status] menu
displays the [FB Point Status] dialog. You can display the FB point parameters and set the
execution state in this dialog.

Figure 5-2. FB Point Status Display

Selecting a node from the node specification list in the [FB Point Status] dialog displays the
current FB point status of the selected node. If the status cannot be displayed, “####” appears.

To change the current execution status, click the <ACTIVE> or <INACTIVE> button in the
Execution State section. After the confirmation dialog appears, the status is changed.

Note To use this dialog, DA subsystem must be accessed as DEODH. If not, status, load
status, and control cycle parameter are all displayed as “####”. For the DA subsystem
settings, refer to “1.2 Initialization Files Settings”

− 34 −
 6.1 Sheet Self-Extraction Function

Chapter 6. Sheet Self-Extraction Function from

External Applications
Sheets of RTC Runtime offer the interface to self-extract from external applications.

6.1 Sheet Self-Extraction Function

Sheets of RTC Runtime can be automatically called up using message call-up from applica-
tions other than RTC Runtime. Automatic sheet call-up is enabled when all of the following
conditions are satisfied:

•• RTC Runtime is running, and the job including the sheet to be called up is selected.
•• The sheet number specified for call-up is set as a sheet number of the RTC job.
If the sheet number specified for call-up is registered for more than one sheet with RTC jobs,
the first sheet found is selected.

If RTC Runtime is iconized, it is automatically de-iconized and displayed. When the condi-
tions above are not satisfied, only the de-iconizing is carried out. When RTC Runtime is de-
iconized, the position and size of the window before iconizing is applied.

When a sheet is called up automatically, RTC Runtime is displayed in the foreground of

the screen. Moving the input focus with your mouse to a window other than RTC Runtime
on the desktop and clicking the screen does not change the display of RTC Runtime in the
foreground.

− 35 −
Chapter 6. Sheet Self-Extraction Function from External Applications

6.2 How to Call up from External Applications

There are two methods available to call up a sheet of RTC Runtime from external applications.

6.2.1 Call-up from InTouch

To call up a RTC Runtime sheet from InTouch, there is the special script used exclusively to
call up an RTC Runtime sheet.

Table 6-1. Script for Sheet Call-up

Function Name Argument Description of Argument

Z$CallupRTCRUN int SheetNo The number of the sheet to be opened
int JobNo The number of the job to be opened
Z$CallupMultiRTCRUN
int SheetNo The number of the sheet to be opened

For the usage of the script, refer to “Harmonas-DEO DOSS User’s Guide” (MS2-DEO300-2003).

6.2.2 Call-up from User Application

To call up an RTC Runtime sheet automatically from an external application, send a message
to RTC Runtime using the Win32 PostMessage function.
Use WM_USER+100 as the message number of the window message for an argument. Specify
the window handle of RTC Runtime in hWnd as another argument and the sheet number in
1Param. Because the window class name of RTC Runtime is “rtcrun”, the window handle of
RTC Runtime can be retrieved using the FindWindow function.

BOOL PostMessage (HWND hWnd, //Window handle of RTC Runtime

UINT Msg, //Message number
WPARAM wParam, //Specify 0
LPARAM lParam //Specify a sheet number);

6.2.3 Call-up from Face Plate

On the Detail Display for the SS Face Plate corresponding to the RTC Frame Parts, you can
click the <Detail Call> button to call up the RTC Runtime sheet where the corresponding
Frame Parts are located.

− 36 −
 7.1 Multi-Engineering Related Functions

Chapter 7. Multi-Engineering
This section describes the operations of RTC Runtime and the points to keep in mind in
multi-engineering.

7.1 Multi-Engineering Related Functions

RTC Runtime offers the following as multi-engineering related functions.

Table 7-1. Multi-Engineering Related Functions

Double-clicking a job part displays the corresponding destination job part.

If the job where the destination job part is located is not open, RTC Runtime
Job part
automatically starts and the destination job
opens. Refer to 3.6.
Parameter inquiry/
You can inquiry/search/replace the point parameter values of different jobs
search/
(targets of system data file integration with RTC Editor). Refer to Chapter 4.
replace functions

7.2 Before Using Multi-Engineering Job with RTC Runtime

Before using a multi-engineering job with RTC Editor, you need to do the following:

•• Open the job to be the master in RTC Editor and carry out [Merge system data files].
•• Set up the job directory for the master job in the “JobDirectory” section of the udpman.ini
file.
You do not need to create the job directory if you start RTC Runtime right after system file
integration because the job directory of the job that carries out integration is automatically
written in when [Merge system data files] is completed.

− 37 −
Chapter 7. Multi-Engineering

7.3 Points to Keep in Mind in Multi-Engineering

The following points should be kept in mind while using a multi-engineering job with RTC
Runtime.

•• You may open each multi-engineering object job in multiple RTC Runtimes.
However, to do so, use the values described in 3.1 as a guideline for the maximum numbers
of parameters and sheets to be displayed at a time

•• In the following situations, the setting of the “JobDirectory” section of the udpman.ini file
may be different from the location of the job to be the master.
Check the setting before starting RTC Runtime.

– [Merge system data files] was carried out in another job before completing [Merge
system data files] and starting RTC Runtime.
– [Create system data files] was carried out in another job before completing [Merge
system data files] and starting RTC Runtime.
– The job to be the master was copied to a different location.

− 38 −
 8.1 Log File Output

Chapter 8. Log Function

The operation history of RTC Runtime is recorded in the history database basically as the
operator change log. As a supplementary function, the operation history may be recorded in
the local machine.
This section describes how to leave a log in the local machine.

8.1 Log File Output

As explained in 1.2, setting the value of the OutputLogFile key in the [RTCRUN] section of
the englp.ini file to “TRUE” enables log file output.

•• Output file name contains the following:

yymmddRR.text
yy : the last 2 digits of the year
mm : month
dd : date
RR : identifier designating RTC Runtime

•• The name of the directory to output a log file to is the path specified in the LogFileDirectory
key in the [LogFile] section of the englp.ini file. If the specified path cannot be found, output
to a log file is not performed.

•• The log file specified above is common to all RTC Runtimes running at the same node.
Therefore, if more than one RTC Runtime is running at the same SS, the logs of other RTC
Runtimes are also output to the same log file.

•• Specify the retention period of a log file (unit = day, significant digits = 3) in the LogSaveTerm
in the [LogFile] section of the englp.ini file. If expired log files exist in the directory to output
a log to, those log files are deleted automatically. If the retention period is not specified or
specified as 0, they are not deleted.

− 39 −
Chapter 8. Log Function

8.2 Contents of a Log

A log outputs one operation history per line. Table 8-1 describes the format of a log.

Table 8-1. Log Format and Descriptions

<Category> <Date> <Time> <Process ID> <Log Type> <Details>

Date yy/mm/dd (yy: the last 2 digits of the year, mm: month, dd: date)
Time hh:mm:ss (hh: hours, mm: minutes, ss: seconds)
Process ID Process ID of RTC Runtime (in hexadecimal notation)
Category, Log Type, Details Refer to Table 8-2

Table 8-2 classifies the contents of the log output of RTC Runtime by category and log type.

Table 8-2. Category of the Log Contents Output of RTC Runtime

Category Log Type Details

Start RTCRUN (None)
Operation Exit RTCRUN (None)
Start a job Job name, job directory
Node name, tag parameter name, previous value,
Parameter setting
setting value
Change
Debug request setting Tag parameter name, setting value
Parameter replace Node name, tag parameter name, setting value
DA registration error Node name, tag parameter name, DA status
DA registration
Node name, tag parameter name, DA status
cancellation error
ERROR Node name, tag parameter name, DA status (PA
Data access error
status)
Node name, tag parameter name, setting value,
Data setting error
DA status (PA status)

− 40 −
 8.2 Contents of a Log

MEMO

− 41 −
Chapter 8. Log Function

MEMO

− 42 −
Document Number: MS2-HDS400-2008 [Rel.400/411/412]

Document Name: Harmonas-DEO

RTC Runtime Function Manual

Date: November, 2011

November, 2014 (Rev.3)

Edited by: Azbil Corporation