MS2–HDS400–2002

[Rel.400/411/412]

RTC User's Guide

•• 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

© 2011-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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
What is RTC?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Structure of This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Notation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Acronyms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Minor Version Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
References. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Chapter 1. Before Using RTC Editor . . . . . . . . . . . . . . . . . . . . . . . . . . 17

1.1 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.1.1 Personal Computer System Required for RTC Editor. . . . 17
1.2 Basic Knowledge Required for Using RTC Editor . . . . . . . . . . . . . . . 19
1.2.1 Keywords in Operating Windows 7. . . . . . . . . . . . . . . . . . . . 19
1.3 System Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
1.4 Roles of RTC Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
1.5 Planning Your Harmonas-DEO System Development. . . . . . . . . . . . 21

Chapter 2. Elements of RTC Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2.1 Install RTC Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.2 How to execute RTC Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.3 RTC Editor’s Work Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.3.1 Child Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.3.2 Tool Bars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.3.3 Parts Bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.3.4 Status Bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.3.5 Contents Displayed When the RTC Editor is Invoked. . . . 31
2.4 Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
2.4.1 Parameter Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Chapter 3. RTC Job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

3.1 The Job Structure Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.1.1 Display in the Job Structure Window . . . . . . . . . . . . . . . . . . 35
3.1.2 Job Structure Window Operation . . . . . . . . . . . . . . . . . . . . . 37

i
Table of Contents

3.2 Creating Jobs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

3.2.1 Creating a New Job. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3.2.2 Opening another Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3.2.3 Delete or Copy a Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
3.3 Job Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.3.1 Job Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.3.2 Sheet List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
3.3.3 Find a Sheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
3.3.4 Control Part List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.3.5 Intersheet Link List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
3.3.6 FB Point List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
3.3.7 Tagname List/Replacement Function . . . . . . . . . . . . . . . . . . 52
3.3.8 Find Parameter Value Function. . . . . . . . . . . . . . . . . . . . . . . 62
3.3.9 Output/Print Point Conf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Chapter 4. About Sheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

4.1 Management of Sheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
4.1.1 What is Sheet?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
4.1.2 Creating and Saving Sheets. . . . . . . . . . . . . . . . . . . . . . . . . . . 71
4.1.3 Opening and Closing Sheets. . . . . . . . . . . . . . . . . . . . . . . . . . 74
4.1.4 Sheet Information Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . 75
4.1.5 Export/Import Sheet Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
4.1.5.1 Export Sheet Info. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
4.1.5.2 Import Sheet Info. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
4.1.6 Printing Sheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
4.2 Applications of Sheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
4.2.1 Operations on RTC Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
4.2.2 Drawing Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
4.2.3 Embedding and Linking Objects. . . . . . . . . . . . . . . . . . . . . . 85
4.2.4 Drawing Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
4.2.5 Gridlines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4.2.6 Zoom In and Out. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
4.3 Sheet Editing Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
4.3.1 View Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
4.3.2 Custom View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
4.3.3 Class View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
4.3.4 Template Edit Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

ii
 Table of Contents

Chapter 5. RTC Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

5.1 Picture Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
5.1.1 How to Use Picture Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
5.1.1.1 Text Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
5.1.1.2 Title Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
5.1.1.3 Line Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
5.1.1.4 Polyline Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
5.1.1.5 Arrow Parts and Double Headed Arrow Parts. . . . . . . 108
5.1.1.6 Rectangle Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
5.1.1.7 Round-rectangle Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . 109
5.1.1.8 Oval Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
5.1.1.9 Arc Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
5.1.1.10 Polygon Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
5.1.1.11 Bitmap Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
5.1.1.12 Sheet Number Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
5.1.1.13 Sheet Title Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
5.1.1.14 Version Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
5.2 Control Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
5.2.1 Control Parts Tool Bar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
5.2.2 Types of Control Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
5.2.3 Behavior of Control Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
5.2.3.1 Parameter Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
5.2.3.2 Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
5.2.3.3 Parts View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
5.2.4 Container Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
5.2.5 Point Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
5.2.5.1 Tips On Point Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
5.2.5.2 FFFB Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
5.2.5.3 Point Parameter Name Format. . . . . . . . . . . . . . . . . . . . 143
5.2.6 Logic Component Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
5.2.6.1 How To Design and Implement Logic . . . . . . . . . . . . . 144
5.2.6.2 Logic made into Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
5.2.6.3 Logic Point Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
5.2.6.4 Logic Component Parts. . . . . . . . . . . . . . . . . . . . . . . . . . 146
5.2.7 Block Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
5.2.8 Block Secondary Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
5.2.8.1 BOX Parameter Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
5.2.8.2 Frame Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

iii
Table of Contents

5.2.9 CL Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

5.2.9.1 Advantages of Managing CL Parts with RTC Editor. . 166
5.2.9.2 Procedure for Creating CL Programs . . . . . . . . . . . . . . 167
5.2.9.3 Process Module Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
5.2.9.4 CL Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
5.2.9.5 CL Source File Creation . . . . . . . . . . . . . . . . . . . . . . . . . 174
5.2.9.6 How to Write Template CL Files (Replace page). . . . . 175
5.2.9.7 How to Write Template CL Files (Merge page) . . . . . . 179
5.2.9.8 Compiling CL Programs. . . . . . . . . . . . . . . . . . . . . . . . . 183
5.2.9.9 Loading CL Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . 184
5.2.10 Reference Point Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
5.2.10.1 Using Reference Parts to Display the Same Point in
Multiple Locations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
5.2.10.2 Point Reference to Container Parts. . . . . . . . . . . . . . . . 187
5.2.10.3 Reference Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
5.2.10.4 Reference Port. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
5.2.10.5 Point Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
5.2.10.6 Make Reference Links. . . . . . . . . . . . . . . . . . . . . . . . . . . 197
5.2.11 Utility Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
5.2.11.1 Intersheet Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
5.2.11.2 Intrasheet Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
5.2.11.3 Divergence Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
5.3 Parameter View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
5.3.1 Operation OverView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
5.3.1.1 Displaying. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
5.3.1.2 View Mismatching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
5.3.2 How to Set Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
5.3.2.1 Add/Modify/Copy Pattern . . . . . . . . . . . . . . . . . . . . . . . 207
5.3.2.2 Apply Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
5.3.2.3 Delete Mismatch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
5.3.2.4 Exporting/Importing Patterns . . . . . . . . . . . . . . . . . . . . 212
5.3.3 Setting Pattern for Individual Control Parts. . . . . . . . . . . 214
5.3.4 Displaying/Not-displaying . . . . . . . . . . . . . . . . . . . . . . . . . . 215

Chapter 6. Implementing Harmonas-DEO System. . . . . . . . . . . . 217

6.1 Creating Data to Be Loaded to the Controller. . . . . . . . . . . . . . . . . . 220
6.1.1 Creating the EB Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

iv
 Table of Contents

6.1.2 Reading EB Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

6.1.2.1 Reading EB Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
6.1.2.2 Automatic Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
6.1.3 Configuration of Block Information. . . . . . . . . . . . . . . . . . 232
6.1.4 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
6.1.4.1 System Conf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
6.1.4.2 Unit ID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
6.1.4.3 Set FB Point. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
6.1.4.4 I/O List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
6.1.4.5 Control List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
6.1.4.6 PU/MU Value. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
6.1.5 Point Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
6.1.6 Box Variable Edit Display . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
6.1.7 PMDP Local Value Edit Display. . . . . . . . . . . . . . . . . . . . . . 259
6.1.8 Create Controller Data Files. . . . . . . . . . . . . . . . . . . . . . . . . 260
6.1.9 Export Parameter/Import Parameter . . . . . . . . . . . . . . . . . 262
6.1.9.1 Engineering procedures . . . . . . . . . . . . . . . . . . . . . . . . . 263
6.1.9.2 Excel file formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
6.1.9.3 Export Parameter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
6.1.9.4 Import Parameter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
6.2 Configuration of Operation Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . 278
6.2.1 Specify PMDP Local Variable. . . . . . . . . . . . . . . . . . . . . . . . 278
6.2.2 Configuration of History Function . . . . . . . . . . . . . . . . . . . 280
6.2.3 Configuration of Alarm Function . . . . . . . . . . . . . . . . . . . . 283
6.2.4 Managing Screen Information. . . . . . . . . . . . . . . . . . . . . . . 283
6.2.5 Creating System Data File. . . . . . . . . . . . . . . . . . . . . . . . . . . 283
6.3 Operation Leading Up to Operation Screen Startup . . . . . . . . . . . . 285
6.3.1 Loading Controller Program Files. . . . . . . . . . . . . . . . . . . . 286
6.3.2 Loading Controller Data Files . . . . . . . . . . . . . . . . . . . . . . . 287
6.3.2.1 Loading FB Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
6.3.2.2 Loading Module Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
6.3.3 Activate Operation Screen . . . . . . . . . . . . . . . . . . . . . . . . . . 295
6.3.4 Save Check Point File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
6.3.5 Loading Checkpoint Files. . . . . . . . . . . . . . . . . . . . . . . . . . . 295
6.3.6 Uploading Control Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
6.3.7 Deleting Controller Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
6.3.7.1 Deleting Module Data. . . . . . . . . . . . . . . . . . . . . . . . . . . 300

v
Table of Contents

Chapter 7. Multiengineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303

7.1 Operation Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
7.2 Job Number. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
7.3 Job Part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
7.3.1 Methods of Defining the Remote Side of the Connection. . . . 309
7.3.2 Rules for Connecting Job Part . . . . . . . . . . . . . . . . . . . . . . . 311
7.3.3 Job Part List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
7.4 Integration of System Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
7.5 Job Information List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315

Chapter 8. Reusing Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

8.1 Reusable Parts Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
8.2 preparation for Using hasNASBe Browser. . . . . . . . . . . . . . . . . . . . . 319
8.3 hasNASBe Directory Management. . . . . . . . . . . . . . . . . . . . . . . . . . . 319
8.3.1 Defining a Category. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
8.3.2 Collecting Reusable Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
8.4 Registering Reusable Parts under hasNASBe. . . . . . . . . . . . . . . . . . . 322
8.4.1 Assigning a Category to a Container. . . . . . . . . . . . . . . . . . 322
8.4.2 Registering Reusable Parts under hasNASBe. . . . . . . . . . . 323
8.5 Reusable Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
8.5.1 Starting hasNASBe Browser . . . . . . . . . . . . . . . . . . . . . . . . . 327
8.5.2 Setting Search Conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . 330
8.5.3 Horizontal Browse function. . . . . . . . . . . . . . . . . . . . . . . . . 331
8.5.4 Vertical Browse function. . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
8.5.5 Capsule Parts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334

Chapter 9. Log Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337

9.1 Function Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
9.2 Contents of Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338

Appendix A. The setting parameter of the node. . . . . . . . . . . . . . 341

A.1 Case of SS/HS/GS/SSH/MS/HL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
A.1.1 [Network Conf1] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
A.1.2 [Network Conf2] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
A.1.3 [Network Conf3] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
A.1.4 CSV format for import/export. . . . . . . . . . . . . . . . . . . . . . . 342

vi
 Table of Contents

A.2 Case of PRC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343

A.2.1 [Network Conf1] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
A.2.2 [Network Conf3] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
A.2.3 [Node Conf1] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
A.2.4 [Node Conf2] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
A.2.5 [Unit Conf1-2] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
A.2.6 [IOM Conf1-4] Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
A.2.7 CSV format for import/export. . . . . . . . . . . . . . . . . . . . . . . 347
A.3 Case of XPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
A.3.1 [Network Conf1] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
A.3.2 [Network Conf3] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
A.3.3 [Node Conf1] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
A.3.4 [Node Conf2] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
A.3.5 [Unit Conf1-5] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
A.3.6 [IOM Conf1-12] Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
A.3.7 CSV format for import/export. . . . . . . . . . . . . . . . . . . . . . . 353
A.4 Case of FLC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
A.4.1 [Network Conf1] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
A.4.2 [Network Conf3] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
A.4.3 [Node Conf1] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
A.4.4 [Node Conf2] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
A.4.5 [Unit Conf1-5] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
A.4.6 [IOM Conf1-3] Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
A.4.7 CSV format for import/export. . . . . . . . . . . . . . . . . . . . . . . 357
A.5 Case of PL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
A.5.1 [Network Conf1] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
A.5.2 [Network Conf3] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
A.5.3 [Node Conf1] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
A.5.4 [Node Conf2] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
A.5.5 [Node Conf3] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
A.5.6 [Unit Conf1-4] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
A.5.7 [IOM Conf1-8] Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
A.5.8 CSV format for import/export. . . . . . . . . . . . . . . . . . . . . . . 361

vii
Table of Contents

A.6 Case of PL2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362

A.6.1 [Network Conf1] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
A.6.2 [Network Conf3] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
A.6.3 [Node Conf1] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
A.6.4 [Node Conf2] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
A.6.5 [Node Conf3] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
A.6.6 [Unit Conf1-5] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
A.6.7 [IOM Conf1-24] Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
A.6.8 CSV format for import/export. . . . . . . . . . . . . . . . . . . . . . . 367
A.7 Case of FC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
A.7.1 [Network Conf1] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
A.7.2 [Network Conf3] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
A.7.3 [Node Conf1] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
A.7.4 [Node Conf2] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
A.7.5 [Node Conf3] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
A.7.6 [Node Conf4] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
A.7.7 [Unit Conf1-5] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
A.7.8 [IOM Conf1-12] Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
A.7.9 CSV format for import/export. . . . . . . . . . . . . . . . . . . . . . . 373
A.8 Case of PC4 [R411 or later] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
A.8.1 [Network Conf1] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
A.8.2 [Network Conf3] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
A.8.3 [Node Conf1] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
A.8.4 [Node Conf2] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
A.8.5 [Unit Conf1-5] Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
A.8.6 [IOM Conf1-12] Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
A.8.7 CSV format for import/export. . . . . . . . . . . . . . . . . . . . . . . 380

viii
 What is RTC?

Introduction
What is RTC?

RTC is a Windows 7 software application. It is a CASE tool in helping you to design the control
strategy and create engineering database of Harmonas-DEO systems, in a graphical, intuitive
environment. RTC produces controller database, which is loaded directly to controllers.

RTC is a generic name of software including RTC editor and hasNASBe browser.

Structure of This Document

This document is a guide for you to learn the function and use of RTC Editor.
The instructions in this manual are substantially based on a single engineering explanation.
The structure of this manual is shown below. The contents describing SS in this manual also
apply to SSH.

Table -1.

Chapter Description
Introduction Describes the concept of RTC Editor and its use.
Introduces system requirements and role of RTC Editor in the
Chapter 1
Harmonas-DEO system.
Chapter 2 Describes the elements of RTC Editor.
Chapter 3 Describes the RTC Job and its structure.
Chapter 4 Describes the Sheet, and its use.
Chapter 5 Describes RTC parts and their uses.
Chapter 6 Describes relations with the operation display.
Chapter 7 Describes multi-engineering.
Chapter 8 Describes reuse of parts using the hasNASBe browser package.
Chapter 9 Describes the log output function of the RTC Editor.

−9−
Introduction

Notation

This guide uses the following conventions:

Table -2. Menu, Command, Dialog

Notation Shows
[File] menu A menu name is enclosed in square brackets ([ ]).
A command name is enclosed in square brackets ([ ]), preceded by
[File]
the name of the menu that contains the command.
A dialog box name, displayed on the caption bar of the dialog box,
[Sheet Information] dialog box is enclosed in square brackets ([ ]). This convention also applies to
property sheets.
A group box, text box, drop-down list, check box, option button,
[File Name:]
or the like in a dialog box is enclosed in square brackets ([ ]).
A button in a dialog box or on the tool bar is enclosed in angle
<OK> button
brackets (< >).

Table -3. Mouse Operation

Notation Shows
Press and release mouse button. Mouse has left button and right
Click
button, but unless specified click left mouse button.
Right Click Click with right button of the mouse.
Double Click Click left mouse button in rapid succession.
Drag Move mouse while holding left mouse button pressed.
Drop Release left mouse button at the desired target.

Table -4. Key Operation

Notation Shows
<Enter> Keys are indicated enclosed in square brackets (< >).
The plus (+) symbol indicates a combination of key operations.
<Shift> + <A> indicates that the <A> key should be pressed while
the <Shift> key is held down.
<Shift> + <A> <Ctrl> + <A> indicates that the <A> key should be pressed while
the <Ctrl> key is held down.
<Alt> + <A> indicates that the <A> key should be pressed while
the <Alt> key is held down.
Arrow keys General term for the < → >, < ← >, < ↑ > and < ↓ > keys.

− 10 −
 Acronyms

Acronyms

The abbreviations used in this guide with reference to RTC and the Harmonas-DEO System
are as follows:

Table -5. Acronyms

Names Meaning
CL Control Language
CSV Comma Separated Value
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 Supervisory Station
DOMS DEO Maintenance Station
DOHL DEO HART Linker
BS DOBS (Node Name)
FC DOFC (Node Name)
GS DOGS (Node Name)
FLC Harmonas-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
RTC_FB RTC Fieldbus Tool
RTC_HT RTC HART Tool
SS DOSS (Node Name)
SSH DOSS_H (Node Name)
Extended Process Controller
XPC
DOPC II/DOPC III (Node Name)
MS DOMS (Node Name)
HL DOHL (Node Name)

− 11 −
Introduction

Terminology

The terms used in this guide with reference to RTC and the Harmonas-DEO System are de-
fined below.

Table -6. Terminology

Term Definition
A type of Control Part that manages programs written in CL, a control
CL Part
sequence language
EB Source A text file that contains point information defined by RTC
Picture Parts A set of Parts representing graphical objects, text, etc
Custom View A view that can be defined for each Control Part on a Sheet
Logical Tag Name A Control Part identifier not dependent on implementation
An icon representing a Container (Sheet) in the Job Window
Container Icon
Also simply called a “Container”
Container Parts A Part iconizing a Sheet. Also simply called a “Container”
Configuration View A view that can be defined for each type of Control Part
A mechanism to display a Point Part on multiple Sheets or to reuse a Point
Point Reference
Part
Reference Part A Part for which a Point Part can be referred to
A Port on a Control Part that indicates the starting and finishing points of
Reference Port
a Point Link
Sheet The equivalent of a sheet of drawing. RTC Editor parts are pasted to Sheets
Job A unit of work of RTC
The hierarchical structure displayed in a child window of RTC Editor,
Job Window showing the inclusion relations of the Sheets in a Job. A Job Window con-
sists of the Root Layer and the Job Repository
Parts for the configuration of Harmonas-DEO control. Control Parts are
Control Parts Container Parts, Point Parts, Logic Component Parts, CL Parts, and Block
Parts
Selection List A text file containing tag names with parameter changes
Template Sheet A mechanism to have a common format in the background
Parts Displayed in the Parts Bar and pasted to Sheets
A collection of Parts Buttons by function. Parts Bars include the Picture
Parts Bar
Parts Bar and the Control Parts Bar
Parts Button A button in the Parts Bar representing each Part
Parameter Link A line representing an I/O connection between Control Parts
Component A Container Part intended for reuse
FOUNDATION Fieldbus
FF
The FF protocol is a communication technology for the fieldbus network.
Highway Addressable Remote Transducer
HART The HART protocol is a communication technology that superimposes
digital signals over 4-20 mA analog instrumental signals.
A software application that supports the engineering work for the
RTC_FB
FOUNDATION Fieldbus in the Harmonas-DEO System.
A software application that supports the engineering work for the HART
RTC_HT
in the Harmonas-DEO System.

− 12 −
 Minor Version Upgrade

Term Definition
Job Repository The layer at which a Container for the reuse of Jobs is placed.
A Terminal on Control Parts that indicates the starting and finishing
Port
points of a Parameter Link.
Point Link A line representing a reference relationship between Control Parts.
Point Parts A set of Parts representing points.
Root Layer A collection of containers constituting a Job.
Root Sheet The Sheet at the top of a job layer.
Logic Component Parts Parts representing the functions of logic points.

Minor Version Upgrade

R411 and R412 are minor version upgrades of ‘R400’. There are following changes.

■
■New Features on R411
•• PC4 controller is supported
•• Numeric Array point is supported
•• String point is supported
•• Datetime point is supported
•• Slot number of PMDP on PC4 is extended to 572
•• String / Datetime parameter of PMDP Local Value on PC4 is supported
•• PVFORMAT of numeric point on PC4 is supported
•• Box data point on another node is supported
•• OPEXT parameter of AO point on PL2 is supported
•• [Add Link] dialog for Reference point parts, Intersheet parts and Intrasheet parts is
improved
•• Support for MS node and HL node stopped

■
■New Features on R412
•• System requirements are changed to 64-bit system.

Following marks are attached to the changes after R400.

[R411 or later]: Description about R411 and R412.
[R412]: Description about R412.

− 13 −
Introduction

References

For details or information not described in this document, refer to the following publications:

Table -7. References

Document Number Document Name

1 MS2-HDS900-1010 Harmonas-DEO Distributed Serial Interface Module Instruction Manual
2 MS2-HDS900-1011 Harmonas-DEO Serial Interface Module Instruction Manual
3 MS2-HDS900-1012 Harmonas-DEO DOPL II Software Simulator Setup Manual
Harmonas-DEO Distributed Extended Serial Interface Module
4 MS2-HDS900-1013
Instruction Manual
5 MS2-HDS900-1021 Harmonas-DEO PLC Linker II Function Manual
6 MS2-HDS900-1023 Harmonas-DEO DOFC Software Simulator Setup Manual (Rel.400)
7 MS2-DEO300-2001 Harmonas-DEO Introduction to Engineering
8 MS2-HDS400-2002 Harmonas-DEO RTC User's Guide
9 MS2-DEO300-2003 Harmonas-DEO DOSS User's Guide
10 MS2-HDS320-2004 Harmonas-DEO Restrictions
11 MS2-HDS320-2005 Harmonas-DEO Picture Parts Function Manual
12 MS2-HDS320-2006 Harmonas-DEO Event History Reference Manual (Rel.400)
13 MS2-HDS411-2006 Harmonas-DEO Event History Reference Manual (Rel.411)
14 MS2-HDS412-2006 Harmonas-DEO Event History Reference Manual
15 MS2-HDS320-2007 Harmonas-DEO Continuous History Function Manual (Rel.400/411)
16 MS2-HDS412-2007 Harmonas-DEO Continuous History Function Manual
17 MS2-HDS400-2008 Harmonas-DEO RTC Runtime Function Manual
18 MS2-HDS300-2009 Harmonas-DEO Gateway Station (DOGS) Engineering Manual
Harmonas-DEO DOPC II/DOPC III/DOPC IV Software Simulator Setup
19 MS2-HDS900-2010
Manual
Harmonas-DEO DEO Process Controller Function Manual (Distributed
20 MS2-DEO300-2011
Type I/O) (Rel.400/411)
Harmonas-DEO DEO Process Controller Function Manual (Base Unit
21 MS2-DEO300-2012
Type I/O) (Rel.400/411)
22 MS2-HDS900-2013 Harmonas-DEO Control Parts Function Manual
23 MS2-HDS900-2014 Harmonas-DEO DOPC II/DOPC III/DOPC IV Reference Manual
24 MS2-HDS320-2015 Harmonas-DEO Report Formatter Function Manual
25 MS2-HDS320-2017 Harmonas-DEO Online Graphic Synchronization Reference Manual
26 MS2-HDS320-2018 Harmonas-DEO Thin Client Supervisory Server (TSS) Function Manual
27 MS2-DEO300-2019 Harmonas-DEO Digital Faceplate Function Manual
28 MS2-HDS400-2025 Harmonas-DEO RTC HART Tool (RTC_HT) Function Manual (Rel.400)
29 MS2-HDS300-2027 Harmonas-DEO Open Report Engineering Manual
30 MS2-HDS320-2028 Harmonas-DEO Lot History Management Reference Manual (Rel.400/411)
31 MS2-HDS412-2028 Harmonas-DEO Lot History Management Reference Manual
32 MS2-HDS320-2030 Harmonas-DEO IT Function Manual (Rel.400)
33 MS2-HDS320-2031 Harmonas-DEO TrendWindow Function Manual

− 14 −
 References

Document Number Document Name

34 MS2-DEO300-2032 Harmonas-DEO Recipe Manager Function Manual
35 MS2-DEO300-2034 Harmonas-DEO External Alarm Output Function Manual
36 MS2-HDS300-2036 Harmonas-DEO Smart ID Handler User Security Function Manual
37 MS2-HDS400-2037 Harmonas-DEO Directory/File Security Function Manual (Rel.400/411)
38 MS2-HDS412-2037 Harmonas-DEO Directory/File Security Function Manual
39 MS2-HDS320-2038 Harmonas-DEO Client Setup Manual (Rel.400)
40 MS2-HDS320-2039 Harmonas-DEO Local Trend Configuration Manual
41 MS2-HDS310-2040 Harmonas-DEO Classic Report Function Manual
42 MS2-HDS400-2051 Harmonas-DEO BatchSuite Function Manual
43 MS2-HDS400-2053 Harmonas-DEO BatchSuite Unit Sequence Function Manual
44 MS2-HDS400-2054 Harmonas-DEO BatchSuite Operation Manual
Harmonas-DEO Fieldbus Controller (DOFC) Function and Installation
45 MS2-HDS400-2060
Manual (Rel.400)
46 MS2-HDS400-2062 Harmonas-DEO RTC Fieldbus Tool Function Manual (Rel.400)
47 MS2-DEO300-3001 Harmonas-DEO Installation Manual
48 MS2-HDS900-3001 Signal Unit I/O Installation Manual
49 MS2-HDS400-4001 Harmonas-DEO Maintenance Manual
50 MS2-DEO300-5501 Harmonas-DEO Operation Guide
51 MS2-HDS300-5502 Harmonas-DEO Open Report Operation Guide
52 MS2-HDS900-6001 Harmonas-DEO Parameter Reference Manual
53 MS2-HDS900-6002 Harmonas-DEO CL Reference Manual
54 MS2-SYS100-3001 Process Controller Installation Manual
DOPC IV/DOPC III/PM-EX/DOPC II/DOPC Main Unit Installation
55 MS2-SYS100-3002
Manual
56 MS2-SYS100-3003 DEO-NET Site Planning Guide
57 MS2-SYS100-3004 FX-bus Input/Output Equipment Hardware Manual
58 MS2-SYS100-3005 X-bus Input/Output Equipment Hardware Manual
59 MS2-SYS100-3010 Noise Suppression and Lightning Protection Guideline

* For detailed functions related to InTouch, refer to the reference material of the
manufacturer.

− 15 −
Introduction

MEMO

− 16 −
 1.1 System Requirements

Chapter 1. Before Using RTC Editor

This section explains how to set up RTC Editor for use and presents the knowledge required
for using RTC Editor.

1.1 System Requirements

RTC Editor requires a personal computer on which Microsoft Windows 7, Windows Server
2003 ([R412] requires Windows Server 2008) runs as an operating system.

1.1.1 Personal Computer System Required for RTC Editor

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

•• Recommended system configuration for RTC Editor

− CPU: 1 GHz or faster 32-bit (x86) processor
([R412] requires 64-bit (x64) processor)
− Memory: 1 GB or higher
− Display resolution: 1024 x 768 dots or over
Medium 125% size is recommended.
− Mouse
− Keyboard

•• Monitor
− 17-inch or larger monitor recommended

•• Hard disk
− Installation of RTC Editor requires at least 25 Mbytes of free space.
− At least 100 Mbytes of free space is recommended for storing the database.

•• External storage
− External storage is used to back up RTC Editor job data.

•• Printer
− A model ready for Windows 7, Windows Server 2003
([R412] requires Windows Server 2008)

•• Hardware key
− This key is connected to a parallel or USB port of the personal computer.

− 17 −
Chapter 1. Before Using RTC Editor

Note If there is not enough free space in a hard disk or other medium containing job data,
RTC Editor may not function properly, a file may not be produced, or a Job may not
be ended or started. While using RTC Editor, secure sufficient free space.

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

− 18 −
 1.2 Basic Knowledge Required for Using RTC Editor

1.2 Basic Knowledge Required for Using RTC Editor

RTC is application software that runs on Microsoft Windows 7 and is compatible with stan-
dard Windows 7 application user interfaces.
For personal computer and Windows 7 setup and basic operations, refer to their respective
manuals. Before using RTC Editor, familiarize yourself with basic Windows 7 operations,
such as how to use the mouse and menus. In particular, make sure you fully understand the
keywords shown below.

1.2.1 Keywords in Operating Windows 7

•• GUI (Graphical User Interface) elements:
Window, Active Window, Icon, Mouse Pointer, and Tool Bar
•• Basic window operations:
Menu, Caption Bar, Scroll Bar, and Button
•• Menu operations
•• Dialog boxes
•• Command Button, Check Box, Option Button, and Text Box

Note Turning off the PC while RTC is running may corrupt files or management data struc-
tures. Make sure to exit RTC before turning off your PC.

Note When handling a file generated by RTC Editor with Explorer do not perform opera-
tions other than those described in this guide.

Note If the Hardware key is not connected to the personal computer’s parallel or USB
port, RTC Editor does not function. Be sure to keep the Hardware key connected to
the parallel or USB port.

− 19 −
Chapter 1. Before Using RTC Editor

1.3 System Specifications

Table 1-1.

Maximum
1,000 Parts/Sheet (approximate). The number of
Number of RTC Parts/System
Parts is depend on the point type
Number of Sheets/System 5,000 Sheets/Job (approximate)
Number of Points/System 100,000 Points/Job (approximate)

1.4 Roles of RTC Editor

InTouch and RTC Editor are used for engineering of the Harmonas-DEO operation screen.
Table 1-2 shows the roles performed by RTC Editor. InTouch is used to perform the points
marked as “InTouch.”

Table 1-2. Roles of RTC Editor

Data Required for Operation Role of RTC Editor

Defining point data; loading into controllers; defining
Point Data
enumeration data
Controller Box Data Defining box information; loading into controllers
Graphic Displays --
History configuration Selecting tags for history collection, and deciding cycles
Trend Group Configuration --
Alarm Configuration Setting alarms (at the time of setting point data)
Group Displays Configuration --

− 20 −
 1.5 Planning Your Harmonas-DEO System Development

1.5 Planning Your Harmonas-DEO System Development

Here is a useful scenario to follow when building an Harmonas-DEO System from scratch,
showing how RTC Editor contributes to the total engineering scenario. Operations not di-
rectly related to RTC Editor are preceded by arrows ( ).

Step 1 Create a new Job.

Step 2 Perform system configuration, such as assigning controller node numbers, units,
and slots.

Step 3 Put Parts on Sheets, and describe control.

Place Control Parts, and configure Points and Blocks. You can also configure I/O
connections by connecting Parameter Links between Parts.
Using Containers, establish hierarchical relationships among the Sheets.
Make the Sheets easy to see by using Picture Parts, Templates, Custom View, and
others.

Step 4 Generate Points, and based on Point Parts and the data set in System Configuration,
create a Point Database.

Step 5 Based on the Point Database, perform History Configuration. Perform this con-
figuration before creating a System Data File.

Step 6 Based on the Point Database, Create Controller Data Files.

Step 7 Based on the Point Database, Create System Data Files.

Make sure the network is connected between controller and DOSS.

Step 8 Load Controller Program Files into Controllers.

by selecting [DEO] from the [Start] menu.

− 21 −
Chapter 1. Before Using RTC Editor

MEMO

− 22 −
 2.1 Install RTC Editor

Chapter 2. Elements of RTC Editor

This section describes the basic operation of the RTC Editor.

2.1 Install RTC Editor

Currently, Azbil Corporation ships out an Engineering-purpose-PC with the RTC Editor
pre-installed.

2.2 How to execute RTC Editor

Use any of the following procedures to start the RTC Editor.

■
■Starting from the taskbar
Click [Start] in the taskbar, point to [Programs] and then select [DEO] → [RTC Editor].

■
■Starting from Explorer
Use either of the following methods.
•• Select rtcedit.exe, and then execute the [File] → [Run] command. Or double-click the file
name.
•• Select a sheet file created with the RTC Editor, and then execute the [File] → [Run] com-
mand. Or double-click the file name.

It is possible to invoke multiple RTC Editors at the same time. However, do not open the same
job in multiple RTC Editors at the same time.

− 23 −
Chapter 2. Elements of RTC Editor

2.3 RTC Editor’s Work Environment

Figure 2-1.

When RTC Editor is started:

•• One RTC Editor window opens. The caption bar of the RTC Editor window displays “RTC
Editor-Job Name.”
•• The RTC Editor window displays the Job Window and two types of child window of Sheet.
•• The tool bar and the Parts Bar are displayed.

− 24 −
 2.3 RTC Editor’s Work Environment

2.3.1 Child Windows

■
■Job Structure and Sheets
As child windows of RTC Editor, you can open one Job Window and multiple Sheets.

Table 2-1.

Window Function
A child window that displays a Job Structure showing
Job Structure
the hierarchical structure of the whole Job.
Sheet A child window that displays the contents of a Sheet.

Because the Job Structure and Sheets have different objectives of operation, they have differ-
ent menu structures. When the Job Structure Window is active, the Parts Bar is not displayed.

•• Job Structure Window

Only one Job Structure Window exists in the RTC Editor, and the caption bar of the Job
Structure Window displays “Job Structure.”
When the Job Structure Window is closed, the [Job Selection] dialog box is displayed,
enabling you to switch to another Job.

•• Sheet window
The caption bar of the Sheet window shows the sheet file name.
A Sheet is of the size of one A3 landscape sheet of paper (420 mm x 297 mm). Because of
the upper and lower and right and left margins, its actual area usable for editing (“Sheet
Area”) is 406 mm x 284 mm.
In the window, the Sheet Area is displayed in white, and out-of-bounds areas are dis-
played in gray. You cannot perform sheet operations, such as adding Parts, in out-of-
bounds areas.

■
■Changing the way of displaying child windows
•• Displaying a single Sheet in multiple windows
By choosing the [New Window] command from the [Window] menu, you can simultane-
ously open the same Sheet in multiple windows. This function will be helpful when you
want to simultaneously open different parts of the same Sheet. With respect to the Job
Window, you cannot open multiple windows.

•• Choosing the way of arranging multiple child windows

By choosing the [Cascade] command from the [Window] menu, you can display the
Job Window and multiple child windows in a way such that one window is overlapping
another, leaving visible only a portion of its upper left corner as wide as the caption bar.
By choosing the [Tile] command from the [Window] menu, you can display the Job
Window and multiple child windows arranged in equal sizes, not overlapping one
another.

− 25 −
Chapter 2. Elements of RTC Editor

•• Iconizing child windows

By choosing the [Iconize] command from the [Control] menu, you can reduce child
windows to icons.
You can also reduce a child window to an icon by clicking the <Iconize> button in the
upper right corner of the child window.
Icons are successively arranged from the lower left corner of the RTC Editor window, in
the right direction. It does not happen that when the RTC Editor window is reduced in
size in the upper direction or in the right direction, icons move accordingly and become
hidden.
You can move icons to any point in the RTC Editor window. By choosing the [Arrange
Icons] command from the [Window] menu, you can arrange icons in the lower left corner
of the RTC Editor window.

•• Maximizing a window
By choosing the [Maximize] command from the [Control] menu, you can enlarge the
active window to its maximum size. When maximized, a child window covers the whole
RTC Editor window. When the RTC Editor window is maximized, it covers the whole
screen.

You can also maximize a window by clicking the <Maximize> button in the upper right
corner of the window.

− 26 −
 2.3 RTC Editor’s Work Environment

2.3.2 Tool Bars

There are two types of tool bars: the standard tool bar and the drawing tool bar.

Table 2-2.

Tool bar Function

Contains buttons for basic operations, such as
Standard
New File, Print, Open, Copy, and Paste
Contains buttons for drawing and editing pic-
Drawing
tures, such as Group, Reverse, and Rotate

Tool buttons are provided for quicker menu command operations. When not usable, tool but-
tons are dimmed (as in the menu display).

■
■Display of tool bars
When a Sheet is active, both the standard tool bar and the drawing tool bar are displayed.
When the Job Window is active, only the standard tool bar is displayed.
When a tool bar is displayed, the corresponding menu item is checked.

The tool bars can be dragged to float and can be docked to one of the four corners of the RTC
Editor window.
For how to switch between foreground and background when a floating tool bar overlaps with
the other tool bar, see 2.3.3, “Parts Bar.”

You can make the tool bars visible or invisible by choosing the [View] → [Standard Tool Bar]
(in the Job Window, [View] → [Tool Bar]) and [View] → [Drawing Tool Bar] commands.

− 27 −
Chapter 2. Elements of RTC Editor

■
■Standard Tool bar contents
Roll the mouse over the button, and its name appears under the cursor plus a description of
what it does in the status bar.

Table 2-3. Standard Tool bar contents

Buttons Description
New Create a new Sheet
Open Open an existing Sheet
Save Save an active Sheet
Cut Cut selected Parts and store in Clipboard
Copy Copy selected Parts and store in Clipboard
Paste Paste from Clipboard into Sheet
Erase Erase the selection
Undo Cancel the last operation
Redo Do the canceled operation again
RTC Tool Bars Show RTC Tool Bars dialog box
Drawing Mode Show or hide Drawing Mode dialog box
Horizontal/Vertical Links Links kept paralleling
Preview Start or Stop Preview
Print Print an active Sheet
Zoom In Zoom in current window
Zoom Out Zoom out current window
Help Open RTC Manual (PDF File)

■
■Drawing Tool Bar Contents
Roll the mouse over the button and its name appears under the cursor plus a description of
what it does in the status bar.

Table 2-4. Drawing Tool Bar Contents

Buttons Description
Group Group the selected Parts
Ungroup Ungroup the selected Parts
Move Front Move the selected Parts to top
Move Back Move the selected Parts to back
Move Forward Move the selected Parts forward by one
Move Backward Move the selected Parts backward by one
Flip Horizontal Flip the selected Parts horizontally
Flip Vertical Flip the selected Parts vertically
Rotate Right Rotate the selected Parts 90 degrees clockwise
Rotate Left Rotate the selected Parts 90 degrees counter-clockwise

− 28 −
 2.3 RTC Editor’s Work Environment

2.3.3 Parts Bar

The following three types of parts bar are provided. For details, refer to Chapter 5, “RTC Parts.”

•• Picture PARTS
•• Control PARTS (Point)
•• Control PARTS (Block)
•• RVinfo PARTS

■
■How to Change the Parts Bar Settings
Select [View] → [Parts Bar] to show the [Parts Bar] dialog.

Table 2-5. Parts Bar Dialog Contents

Item Contents
Display the Parts Bar that can be used in the RTC Editor. Use the following
Parts Bar
procedure to select the Parts Bar to be used
Decides whether the selected Parts Bar should be shown or hidden.
<Invisible> is operative when the Parts Bar is currently displayed, and
Visible/Invisible <Visible> is operative when the Parts Bar is currently hidden.
After being operated, the button becomes inoperative, and the opposite but-
ton becomes operative.
Several buttons can be arranged horizontally in the Parts Bar. The height of
the bar depends on the number of buttons lined up and the width of the bar.
Clicking this button displays the [Change Bar Width] dialog.
Bar Width This can be used to set the horizontal size. The minimum bar width value
that can be set is 2. When set to maximum value, the bar will span the entire
screen width. If values outside this range are input, the 'Invalid Size' error
message appears.

■
■Displaying the Parts Bar
•• The Parts Bar can only be shown when the sheet is active. The Parts Bar cannot be shown
when the Job Window is active.
•• The Parts Bar is always shown floating. Unlike the Tool Bars, the Parts Bar cannot be
docked in the window.
•• When multiple Parts Bars are shown partly overlapping, a hidden Parts Bar can be
brought to the front by right-clicking in its Caption Bar or border areas. This also applies
to toolbars in the floating state.

■
■Buttons in the Parts Bar
•• Parts buttons that cannot be executed appear grayed out. When this is the case, the parts
button cannot be clicked. In the case of a part that does not allow reshaping, for example,
the <Reshape> button will be grayed out.
•• When the mouse cursor is placed on a parts button, the parts name is displayed under
the cursor and a description of the Control Part is shown in the status bar in the lower
part of the window.

− 29 −
Chapter 2. Elements of RTC Editor

2.3.4 Status Bar

Status Bar can be made visible or invisible by choosing [Status Bar] command from [View]
menu. If the Status Bar is already visible, a check mark appears at the head of the menu
command.

■
■Sheet Window Status Bar
In the status bar, user guidance, mouse location, display ratio, NumLock key and CapsLock
key are shown.

Table 2-6.

Item Description
User Guidance A text message suggesting what to do
(x, y) location with left top corner as (0, 0). The values
Mouse Location
are in millimeters
Zoom Ratio Zoom ratio as a percentage of full screen
CapsLock CAP is shown when CapsLock’ed
NumLock NUM is shown when NumLock'ed

■
■Job Structure Window Status Bar
When the Job Window is active, nothing is shown in the status bar.

− 30 −
 2.3 RTC Editor’s Work Environment

2.3.5 Contents Displayed When the RTC Editor is Invoked

■
■Appearance of the RTC Editor at the Time of Start Up
•• New startup
When the RTC Editor is invoked with the rtcedit.ini in the initialized state:
– the Job Structure Window and Root Sheet are shown.
– the Standard Toolbar is docked at the top of the window.
– the Drawing Toolbar is docked at the bottom of the window.
– the Job Structure Window is active, and the Parts Bar is not displayed when the RTC
Editor is invoked.
– the Parts Bar is displayed in the default size when the Sheet is made active.
– the Status Bar is displayed in the lower part of the window (above the Drawing Toolbar).
– the Drawing Mode dialog box is not displayed.

•• Restart
When the RTC Editor is restarted, the RTC Editor basically appears as when it was closed
down the last time.

– As shown following Table 2-7, the appearance of Child Windows differs depending
both on whether or not a Child Window was maximized when the RTC Editor was
closed down the last time and on the way in which the RTC Editor is started up this
time.

Table 2-7. Child Window Appearance

Invoking Method State When Closed Last Time Child Window Appearance
The Child Window that was
maximized at the time that the RTC
Maximized Child Window
Editor was closed down the last
time is displayed
Running RTCEDIT.exe
All the Child Windows existing the
time that the RTC Editor was closed
No maximized Child Window
down the last time are displayed.
The Job Window is at the front.
Double-clicking the sheet Only the Job Window and the se-
(not applicable)
file .sht lected sheet are displayed

– The Toolbar’s shown/hidden state, docked/floating state, and its display position are
inherited from when the RTC Editor was closed down the last time. If it was located at a
position outside the Desktop, the display position is automatically adjusted to bring the
Toolbar into the Desktop area.
– The Parts Bar’s shown/hidden state, the dimensions of the Parts Bar, and its display po-
sition are inherited from when the RTC Editor was closed down the last time. If it was
located at a position outside the Desktop, the display position is automatically adjusted to
bring the Parts Bar into the Desktop area.
– The Status Bar’s shown/hidden state is inherited from when the RTC Editor was closed
down the last time.

− 31 −
Chapter 2. Elements of RTC Editor

■
■Response to Modification of the Screen Display Mode
Even if the Desktop area is made smaller by using the [Display Setting] dialog box in the
Control Panel, the RTC Editor Window, Toolbar and Parts Bar will not become invisible.

•• RTC Editor Window

If the size of the window cannot be accommodated in the new Desktop area, the window
will fill the entire area (though this is not the same as the window’s being maximized).

•• Toolbar, Parts Bar

If these are placed in a position in which they are not shown in the new Desktop area, the
display position is automatically adjusted to bring the bar into the Desktop area.

− 32 −
 2.4 Help

2.4 Help

Explanations on operations and functions can be displayed by executing the [Help] command
from the menu.

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

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

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 property 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
parameter name entered in the combo box are treated as being the same. If the letters of a pa-
rameter name other than its initial letter is unknown, entering the known letter and then pull-
ing the list in the combo box down will make the Candidates of the parameter 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.

− 33 −
Chapter 2. Elements of RTC Editor

■
■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 parameter name entered in the combo box are
treated as being the same.

− 34 −
 3.1 The Job Structure Window

Chapter 3. RTC Job

The RTC Job, or simply Job, is a set of related engineering data.

3.1 The Job Structure Window

3.1.1 Display in the Job Structure Window

■
■Sheet and Container
With RTC Editor, one Sheet is displayed:
•• as a Container Parts on other Sheets, and
•• as a Container Icon in the Job Structure Window.

A Container Parts provides the means of nesting a Sheet in another Sheet as a Part. One
Container Parts always contains one Sheet. By putting a Container Parts in a Sheet, you can
show the parent-child relationship between the Sheets.
In the Job Structure Window, the Container Parts and the Sheet are represented as a pair by
a single Container Icon.

Note Unless it is necessary to distinguish between them, both Container Parts and
Container Icon will hereinafter be simply called “Container.”

Sheet A
Job Structure Window
Container B Sheet B
A
B Sheet C
Container C
C

Job Tree

Job Repository Job Repository

D

Figure 3-1. Sheet and Container

− 35 −
Chapter 3. RTC Job

■
■Structure of the Job Structure Window
The Job Structure Window depicts the layers of Sheets in a Job. The Job Structure Window is
divided into the Job Tree and the Job Repository. The Job Tree and the Job Repository are
separated by a border line.

The Job Tree is a set of Sheets that collectively constitute a Job. Sheets in the Job Tree are the
targets of point generation and retrieval functions. The Job Repository is a place where Sheets
(Components) that may be reusable in a Job are placed. You can freely move and copy icons
representing Containers between the Job Repository and the Job Tree.

Information to identify Sheets, such as Container names and Sheet numbers, can be displayed
at the right of icons representing Containers.
Containers are displayed from up to down in the order they have been added to the tree by
creation, copying, and other operations. You can change the order of display.

■
■Job Tree
The top of the Job Tree is called the “Root Sheet.” It represents the whole Job. When a new Job
is created, a Root Sheet is created with the same name as the Job name.

■
■Job Repository
A Container is placed in the Job Repository:
•• When the container is moved or copied into the Job Repository from the Job Tree in an
operation in the Job Structure Window;
•• When the Sheet is saved under an alias by choosing the [Save As...] command from the
[File] menu;
•• When a Sheet has been added by clicking the <New File> button or choosing the [New]
command from the [File] menu; or
•• When the Container has been deleted from the Job Tree.

− 36 −
 3.1 The Job Structure Window

3.1.2 Job Structure Window Operation

■
■Display Container Information
In the Job Structure Window, Container information can be displayed in the right- hand side
of the Container icon.
Display any combination of items are shown in the following table.

You can see what items to display from [View] menu in the Job Structure Window. When an
item is already displayed, a check mark is shown in the menu command.

Table 3-1. Display Container Information

Item Menu Command Description

[Sheet Number] command in Sheet Number set in the [Sheet
Sheet Number
[View] menu Information] dialog box
Logical Tag Name (Container Name)
[Logical Tag Name] command in set in the [Set Property] Property Sheet
Logical Tag Name
[View] menu of the Container In the Root Sheet, the
Job Name is displayed
[File Name] command in [View]
File Name Sheet File Name
menu

■
■Deleting Containers from the Job Repository
When a Container is deleted from the Job Tree, it is temporarily moved into the Job
Repository (because it may be used again). If the Container is deleted from the Job Repository,
the Container, the corresponding Sheet, and the offspring Containers (Sheets) are eradicated
from the Job Directory. You cannot undo this operation.

Step 1 Click the Container in the Job Repository.

Step 2 Choose the [Eradicate] command from the [Job] menu, and a message box will
appear for confirmation. Click <OK> to carry out the deletion.

− 37 −
Chapter 3. RTC Job

■
■Moving and Copying Containers
By dragging a Container in the Job Structure Window with the mouse, you can move or copy
it to under any Sheet or into the Job Repository. The object that is moved or copied is the
whole subtree including and under the Container.

To copy a Container, choose the Container icon, drag it to another Container to which you
want to copy it, and drop it there.
The operation to move a Container is the same as copying, except you hold down the [Shift]
key while you drag and drop.

For more details of moving and copying Containers, see 5.2.4, “Container Parts.”

Note If you move or copy a Container to the Job Tree, the Container Name (Logical Tag
Name) changes to the default name. When you move or copy a Container into the
Job Repository, the Container Name (Logical Tag Name) remains unchanged.

Note When you move or copy a Container into the Job Repository, it is attached directly
below the Job Repository icon. In the Job Repository, you cannot move or copy a
Container into another Container.

■
■Opening Sheet from Job Structure Window
You can open Sheet from the Job Structure Window in the following ways.

Step 1 Double-click a Container Information field under Job Structure Window.

Step 2 Select a Container icon and choose [Open Sheet] command from [File] menu of
the Job Structure Window.

Step 3 Choose [Open Sheet] command from the pop-up menu, which is displayed by
clicking the right mouse button.

■
■Display Sheet Information from Job Structure Window
You can invoke [Sheet Information] dialog box from the Job Structure Window in the follow-
ing two ways:

Step Select a Container icon and choose [Sheet Info] command from [File] menu of the
Job Structure Window.

Step Choose [Sheet Info] command from the pop-up menu (click the right mouse
button).

− 38 −
 3.1 The Job Structure Window

■
■Change the Order of Container
The order of container displays can be changed in either of the following two ways:

Step Select the container you want to move, and execute the [View] → [Ctrl+Up] com-
mands or [View] → [Ctrl+Down] commands.

Step Select the container you want to move, and while holding the [Ctrl] key down,
press the up or down arrow key. This command is also valid for containers in the
Job Repository.

If you have selected multiple containers to be moved, the results are as follows:
•• If all these containers belong to the same hierarchical level, those directly above or below
the selected containers are displayed instead.

•• If these containers belong to different hierarchical levels, the rule mentioned above applies
to each of the hierarchical levels. However, the parent-child relationship is not changed.

■
■Restore Container Original Order
To restore the original order of containers after moving containers a number of times, execute
the [View] → [Container Original Order] commands. In the case of containers in the Parts
Repository, this rearranges only those below the highest level, leaving those at the highest
level unchanged.

■
■Registration in Repository
The Container(s) selected in the Job Structure Window can be registered in the Repository
Database.

− 39 −
Chapter 3. RTC Job

■
■Print Job Structure Window
To print a job hierarchical chart, activate the chart and then perform either of the following
two operations:

Step Execute the [File] → [Print] commands.

Step Open [Sheet List] by executing [Browser] → [Sheet List] from the menu, then select
the job hierarchical chart and click the <Print Sheet> button.

Whichever operation is selected, the [Print] dialog box appears. In this dialog box, specify
the printing scope, number of copies, printing quality, etc. and click the <OK> button. Then
printing will start. You can check the printing contents using the [File] → [Print Preview]
commands.
To set the printer, use the [Set Printer] dialog box that appears on execution of the [File] →
[Set Printer] commands. In this dialog box, you can specify the printer to be used, paper, and
paper orientation (portrait or landscape). By clicking the [Detail] tab, you can specify further
details, including resolution and replacement of True Type fonts.

Restriction Job hierarchical charts may not be properly printed on some printers. To print a
list of sheets, cause a CSV format file created using a sheet list function (described
later) to be read into an application such as Microsoft Excel.

− 40 −
 3.2 Creating Jobs

3.2 Creating Jobs

When activated, RTC Editor opens the Job which was last edited in the previous session.
If there was no previous Job, RTC Editor displays [Job Selection] dialog box, where you can
either open an existing Job or create a new Job.
[Job Selection] dialog box also appears when you activate the second RTC Editor while the
first RTC Editor is already running. In this case, you can either create a new Job or open a Job
except, the one opened by the first RTC Editor.

3.2.1 Creating a New Job

■ create a new job:
■To

Step 1 If you start RTC Editor with no Jobs saved, the [Job Selection] dialog box appears.
Click the <New Job> button. If there is a Job saved, RTC Editor starts with the Job
open. In this case, activate the Job Structure Window, and choose the [New Job]
command from [Job].

Step 2 The above operation opens the [New Job] dialog box.
In the [New] dialog box, set as follows:
•• In the [Directory] list box, choose the directory in which to place a Job directory.
•• Enter a Job name in the [Job Name] box. The Job name is subject to the same
restrictions as Container names. For more details, see 5.2.4, “Container Parts.”

Step 3 Click the <Create> button. When a Job has already been opened by RTC Editor, a
confirmation message appears to ask you: “Close all Sheets now open?” Click the
<OK> button.

Step 4 When a new Job has been created, a job directory of the same name as the Job name
is created under the directory shown in the [Directory] list box.
Directories, a Root Sheet file, a Job Information file, etc. used in the Job are created
under the job directory. The name of the Job Information file is “job name.job” and
the file name of the Root Sheet file is “job name_1.sht.”

Note When a directory specified is on an NTFS drive, you cannot create a Job
unless you have the right to access the directory to write.

− 41 −
Chapter 3. RTC Job

3.2.2 Opening another Job

When a Job is open, follow these steps to open another Job.

■ open another Job (to specify a Job to be opened when RTC Editor is started):
■To

Step 1 When RTC Editor is started, the Job saved last is opened automatically. If RTC
Editor cannot be started with the Job saved last (because the Job directory cannot
be found, the rtcedit.ini file that records the Job name edited last has been initial-
ized, or the like), the [Job Selection] dialog box appears. In the dialog box, click the
<Open Job> button, and the [Switch Job] dialog box is displayed.

Step 2 In the [Open Job] dialog box, specify the drive and the directory, and open the Job
directory of the target Job. The Job directory always has a Job Information file (a file
with the extension .job), and set it in the [File Name] box. Click the <OK> button
to open the Job.

Step 3 By double-clicking a Sheet file (a file with a .sht extension) in the Job directory in
Explorer, you can open the Job to which the Sheet belongs. At this time, the Sheet
selected is displayed.

■ change Jobs (To close the active Job and open another Job):
■To
•• Either double-click the control menu bar of the Job Structure Window or execute the
[Close] command from the control menu, and the [Select Job] dialog box is displayed. The
subsequent operations are the same as those for opening a Job.

•• Activate the Job Structure Window, and execute the [Open Job] command from the [Job]
menu. The [Open Job] dialog box is displayed. The operation in the [Open Job] dialog box
is the same as the one in the [Open Job] dialog box described above.

Note In cases in which there is not a directory, such as a case in which a MO disk in which
a Job directory has been saved is not mounted, you cannot open a Job.

Note You cannot open a single Job in more than one RTC Editor.

− 42 −
 3.2 Creating Jobs

■
■Job-data-adjusting operation
•• If a job is opened after the version of RTC Editor is updated, a job-data-adjusting operation
may be automatically performed.

•• The job-data-adjusting operation is an operation within RTC and is used for converting the
format of job data into the correct one that matches with the new version of RTC.

•• When the adjusting operation is performed, it may take some time before the job is opened.

•• When the job is opened a second time or thereafter, the job-data-adjusting operation is not
performed. (The job-data-adjusting operation is performed only once, when the job is to be
opened the first time after the version of RTC Editor is updated.)

3.2.3 Delete or Copy a Job

To delete a Job, select the Job directory using Explorer, and delete the whole directory by
choosing the [Delete] key.
Explorer is also used to copy a Job. Copy the whole Job to another personal computer via a
floppy disk or a network, or make a backup copy of the whole Job.

Note When you use Explorer, be sure to handle the Job directory as a whole. If you delete
or rename a portion of the files in the Job directory, subsequent operation of RTC
Editor is not guaranteed.

You can change the Job directory name itself using Explorer. However, when RTC
Editor is in operation, do not perform such operations as deleting or renaming the
Job directory.

Note You can compress the whole Job directory and move it to another personal com-
puter. Some tools, however, forcefully change the file name to 8.3 format. In this
case, the Sheet file name displayed in the Job Structure Window differs from the file
name displayed in Explorer, and you cannot open the Sheet.

− 43 −
Chapter 3. RTC Job

3.3 Job Management

3.3.1 Job Information

[Job Information] dialog box contains various information about the Job.

■
■Open the [Job Information] dialog box

Step 1 Choose the [Job Info] command from the [Job] menu.

Step 2 The [Job Information] dialog box opens.

Step 3 Job Information contains the information shown in Table 3-2.

Table 3-2. [Job InInformation] dialog box

Box Description
Job name is given when a Job is created. If you change the Job
Job Name name in this box, the name of the Job Information file and sheet
file for the Root Container is renamed accordingly.
When multi-engineering is performed, a unique number (1-99)
Job Number
is entered for each job
Customer 1, Customer 2 The name of the users
Equipment Name The name of the equipment to which this Job is applies
The name of the organization where designers of this Job and
Supplier
implementers belong
Designer, Sub-Designer The name of designers and implementers of this Job
Revision The version of the Job
Project Start Date Date when the Job starts and finishes
Project Finish Date Enter the finish date The format can be freely selected
Note Any information which are not covered by above boxes

− 44 −
 3.3 Job Management

3.3.2 Sheet List

Sheet List Window shows all the Sheets within a Job. By default, it shows all the Sheets in the
Job Tree. Specify a Container in the Job Tree to list its child Sheets.

■ Display Sheet List

■To
Choose [Sheet List] command from [Browser] menu of the Job Structure Window.
Sheet List shows the following items.

Table 3-3. Display in Sheet List

Box Description
Sheet Number is defined in the [Sheet Information] dialog box.
Sheet Number
For Sheet Info dialog box, see later section.
Container Name is used to identify Containers, or for that matter,
corresponding Sheets.
Container Name
Container Name is assigned to each Container in Container
Name box in Properties property sheet for the Container Part.
Version is defined in the [Sheet Information] dialog box.
Version
For Sheet Info dialog box, see later section.
Last Modified Date Date when the Sheet is last saved
Sheet File Name Absolute path name of the Sheet file

■
■Export Sheet List
You can directly export the contents of Sheet List to a file in CSV format. You can export the
file to spreadsheet software such as Microsoft Excel. To export Sheet List, click the <Export>
button in the Sheet List window, and the [Export Sheet List] dialog box is displayed.
The Sheet List is exported with a .csv extension directly under the Job directory by default.
Give it a file name. You can also export Sheet List to any other directory with any other
extension.

■
■Sort Sheet List
Sheet List can be presented in order of Sheet Number, Logical Tag Name, Time Stamp, or
Hierarchy Diagram, as you choose. When Sheets have the same Sheet Number, they are pre-
sented in the order in which they have been sorted so far. When Sheet List is sorted by Sheet
Number, Sheets whose Sheet Number is zero (that is, Sheets with no Sheet Numbers set) ap-
pear at the bottom of the list.

■
■Open Sheet from Sheet List Dialog box
Open Sheet from Sheet List dialog box.

Step Double-click on any individual line in the Sheet List box, or select a line from the
Sheet List box, and choose <Open Sheet> button. The selected Sheet is opened in a
new Sheet Window.

− 45 −
Chapter 3. RTC Job

■
■Finding a Sheet
The <Current Selection> and <Search> buttons can be used to search for sheets that match
the given criteria.
The <Current Selection> button is for searching the sheets in the currently displayed list, and
the <Search> button is for searching all the sheets within the specified search scope. Details
on sheet retrieval are explained in the following.

■
■Printing Sheets
The <Print Sheet> button can be used to print a sheet selected in a list. If multiple sheets are
selected, pressing the button will display the [Print] dialog box that allows all the sheets to be
printed consecutively.

■
■Batch Modification of the Sheet Information
Sheet information can be batch modified by using the <Change>, <ChangeRev.>, and
<Update> buttons located in the <Sheet Information> group box. The procedure is as follows:

Step 1 When a single sheet is selected in the Sheet List box, the <Change> button becomes
operative.

Step 2 When the <Change> button is pressed, the [Sheet Information] dialog box appears,
and the Sheet Number, Sheet Title, Version, and Note items can be set.

Step 3 When the <OK> button is pressed, the [Sheet Information] dialog box closes, and
only the Sheet Number and Version are updated and indicated in the Sheet List list
box.

Step 4 When two or more sheets are selected in the Sheet List list box, the <ChangeRev.>
button becomes inoperative.

Step 5 When the <ChangeRev.> button is pressed, the [Sheet Information] dialog box ap-
pears, but all other items than the Version item become invalid. At this point, enter
the Version that you want to set.

Step 6 When the <OK> button is pressed, the [Sheet Information] dialog box closes, and
the Version is updated and indicated in the Sheet List list box.

Step 7 When one or more items is modified, the <Update> button becomes operative.
When the <Update> button is clicked, the contents of the modifications performed
up to that point are saved.

Step 8 If you attempt to close the [Sheet List] dialog without clicking the <Update> button
even if modifications have been performed, a dialog asking whether the modified
contents should be saved is displayed. When <Yes> is selected, all the modified
contents are saved. If <No> is selected, the modified contents are not reflected.

− 46 −
 3.3 Job Management

3.3.3 Find a Sheet

Setting search conditions, RTC editor can search for desired sheets.

■
■Procedure for setting sheet search conditions
Set sheet search conditions in the [Find Sheet] dialog displayed by either of the following
operations.

Step Activate Job Structure Window, select [Browser] from the menu, and then execute
the [Find Sheet] command.

Step In the state where the [Sheet List] window appears, click the <Current Selection>
button or <Search> button.

■
■Sheet search conditions
Sheet search conditions are as follows.

•• Scope of Search
Choose Job Tree or Subtree from the Scope of Search box in the Find Sheet dialog box.
If <Job Tree> is chosen, the scope of search is the whole Job Tree.
If Subtree is chosen, the scope of search is the child <Subtree> of the selected Container,
selecting the Root Container in the Job Structure Window, and choosing Subtree is the
same as selecting the <Job Tree> button.
Sheets located in the Job Repository are out of the search scope.

•• Search by Sheet Name

Type Sheet Name in the Sheet Name box in the [Find Sheet] dialog box.
You may use asterisk ‘*’ as a “wild card” character. Insert one asterisk anywhere in the
Sheet Name. For example, “*Control”, “Flow*” and “Fl*trol” are all valid search names.
Sheet Name box is blank by default.

•• Search by Date
Type in the year, the month and the day in the Last Modified Date group box and
choose either <The Date Or Later>, <The Date>, <The Date Or Earlier> button from the
[Modified On] group box.
Choosing <Any Date> button from the [Modified On] group box makes they date irrel-
evant and whatever was typed in the [Last Modified Date] group box is ignored.

Note Search criteria other than Sheet Name are initialized whenever the [Find Sheet]
dialog box is invoked.

− 47 −
Chapter 3. RTC Job

3.3.4 Control Part List

The Control Part List is a function for showing the Control Parts belonging to a job as a list.

Table 3-4.

Parts Shown in the Control Part List Parts Not Shown in the Control Part List
Point Parts
Block Parts
Container Parts Picture Parts
CL Parts
Logical Component Parts

■
■Displaying the Control Part List

Step 1 Make the Job Structure Window active.

Step 2 Execute the [Browser] → [Control Part List] commands from the menu to open the
[Control Part List] dialog box.

Table 3-5. Contents Displayed in the Control Part List

Item Description
Indicates the Sheet name (the Logical Tag Name of the corresponding
Sheet Name
Contents Part) in which the Control Part is located
Indicates the Logical Tag Name set in the Control Parts [Properties]
Logical Tag Name
property sheet
Indicates the Tag Name set for the Control Part
•• In the case of Block Parts, the set block name is indicated
•• Nothing is indicated in the case of a Container
•• In the case of CL Parts, the Tag Name of the corresponding Process
Tag Name Module Data Part is indicated
•• In the case of Logical Component Parts, the Tag Name of the corre-
sponding Logic Point Part is indicated
•• In the case of Reference Parts, an asterisk “*” is attached to the Tag
Name of Reference Original Parts
Node Number: Module Number: Slot Number
Hardware Address
Only assigned to Point Parts, otherwise nothing is indicated

If a line in the list is placed in the selected state, the Container in the Job Structure Window
corresponding to the [Sheet Name] of that line is placed in the selected state.

■
■Sorting the Control Part List
By default, a list is displayed with the tags arranged according to the sheets to which they be-
long, but the items can also be displayed in the order of Logical Tag Names or Tag Names. To
perform sorting, click the button <Hierarchy Sort>, <Logical Tag Name Sort> or <Tag Name
Sort> corresponding to the desired sort mode.

− 48 −
 3.3 Job Management

■
■Exporting the Control Part List
The contents of a list can be exported in Comma Separated Value (CSV) format. The exported
file can be accessed using Microsoft Excel or similar spreadsheet software.

To export the list, click the <Export> button in the list dialog. The [Export Control List Part]
dialog appears.

By default, the exported file is saved with the .csv extension in the Job directory. Specify the
file name as required. It is possible to save the file with another extension in another directory.

■
■Opening a Sheet from the Control Part List Dialog Box
The sheet in which the corresponding Control Part is located can be opened by selecting a
line in the List and clicking the <Open> button. Control Parts appear in the selected state in
the Sheet.

Note Control Parts in a Sheet located in the Job Repository cannot be shown in the
Control Part List.

3.3.5 Intersheet Link List

Intersheet Link List is the function of listing the intersheet links contained in a Job. For inter-
sheet links, see 5.2.10, “Reference Point Parts.”

■ display Intersheet Link List:

■To

Step 1 Activate a Job Structure Window.

Step 2 From the [Browser] menu in the Job Structure Window, execute the [Intersheet
Link List] command, and the [Intersheet Link List] window opens.

Step 3 From the [List:] drop-down list in the [Intersheet Link List] window, choose the
type of Intersheet Links to be listed. The types of Intersheet Links are as follows:

•• Intersheet Parameter Link

This is a parameter link that links Sheets.

•• Intersheet Point Link

This is a point link that links Sheets.

− 49 −
Chapter 3. RTC Job

Table 3-6. Display in Parameter Link List

Item Description
Out Sheets, Out Terminal #, The Sheet Number of the Sheet where intersheet balloons on the out-
Out Terminal Descriptor put side are located, and the numbers of the intersheet balloons
In Sheets, In Terminal The Sheet Number of the Sheet where intersheet balloons on the
Descriptor input side are located, and the numbers of the intersheet balloons

Table 3-7. Display in Intersheet Point Link List

Item Description
The Sheet Number of the Sheet where the referenced Parts (indicated
Original Sheets, Original by blue ports) of a reference link are located, Logical Tag Names of
Parts, Original Ports the Parts, and the Reference Port identifier “REFn” (n: Reference Port
number).
The Sheet Number of the Sheet where the referencing Parts (indi-
Clone Sheets, Clone Parts,
cated by red ports) of a reference link are located, Logical Tag Names
Clone Ports
of the Parts, and the Reference Port identifier.

■
■New search of Intersheet Link List
Clicking the <Search> button in the [Intersheet Link List] window executes a function for
redisplaying a list of the Intersheet Links belonging to the newest Job.

■
■Export Intersheet Link List
Clicking the <Save> button in the [Intersheet Link List] window opens a file dialog box. By
specifying a directory and a file name in this dialog box, you can export Intersheet Link List
in CSV format (extension: .csv).
By having the file read by Microsoft Excel, you can separately edit and print it.

− 50 −
 3.3 Job Management

3.3.6 FB Point List

The FB Point List is a function for displaying a list showing the FB points assigned to a Sheet.

■
■Displaying the FB Point List

Step 1 Make the Job Structure Window active.

Step 2 Execute the [Browser] → [FB Point List (P)] commands from the menu to open the
[FB Point List] window that shows a list with information on the FB Points assigned
to the current sheet.

Note •• A sheet located in the Job Repository cannot be shown in the FB Point
List.
•• FB Points not assigned to any sheet are not shown in the list. To refer-
ence the FB Point list information, use the Tag Name List/Replacement
Function (Section 3.3.7).

■
■Displaying the Contents of the FB Point List

Table 3-8. Display in the FB Point List

Item Description
Sheet # Sheet number defined in the Sheet
Sheet Name Sheet name defined in the Sheet
Node # Node number defined in the Sheet
Slot # Slot number of FB Point defined in the Sheet
Tag Name Tag name of FB Point defined in the Sheet
Unit ID Unit ID of FB Point defined in the Sheet
ExecRate Execution Rate of FB Point defined in the Sheet
Description Description of FB Point defined in the Sheet

■
■Sorting the FB Point List (Sorting Function)
All the items displayed in the FB Point List can be shown in ascending or descending order.
Clicking the title part of any of the display items will toggle the listing of the items between
ascending and descending order.

Note No sorting is performed at the time that the FB Point List window is opened.

− 51 −
Chapter 3. RTC Job

■
■Opening a Sheet from the FB Point List Window
Select any individual line in the list, and then click the <Open Sheet> button to open the sheet
to which the FB Point is assigned. A desired sheet can also be opened by double-clicking on
the desired line.

■
■Exporting the FB Point List
The contents of a list can be exported in Comma Separated Value (CSV) format. The exported
file can be accessed using Microsoft Excel or similar spreadsheet software.
To export the list, click the <Export> button in the list dialog to show the [Save Information]
dialog. By default, the exported file is saved with the fbpntlst.csv extension in the Job directory.
Specify the file name as required.

3.3.7 Tagname List/Replacement Function

The Tag Name List is a function for listing the Control Parts belonging to the Job.

Table 3-9.

Parts Shown in the Tag Name List Parts Not Shown in the Tag Name List
Point Parts
Block Parts CL Parts
FB Parts Container Parts
Logical Component Parts Capsule Parts
Reference Parts

− 52 −
 3.3 Job Management

■
■Display the TagName List

Step 1 Choose [Tag Name List/Search...] List command from [Browser] menu of the Job
Structure Window.

Step 2 In the TagName List the following items are shown.

■
■Displayed contents of list

Table 3-10. Displayed Contents of Tag Name List

Item Description
TagName Displays tag names set in control parts or at FB points
Pnt Type Displays the point type of control parts or FB points
Displays the module type (for I/O), algorithm type (except
M / A Type for I/O and except for block parts), and algorithm type (for
block parts) of control parts.
Node # Displays node numbers set in control parts or at FB points
Unit # Displays unit ID set in control parts or at FB points
F/C Displays point forms set in control parts
Displays module numbers (except for block parts) and
Module/Block #
block numbers (for block parts) set in control parts
Displays slot numbers (for I/O), index (for FL/NM), and
Slot # block numbers (for block parts) set in control parts. Also
displays FB slot numbers set at FB points.
Sheet # Displays sheet numbers to which control parts belong
Pnt Desc Displays point descriptors set in control parts

Note •• In the case of Tag Names, an asterisk “*” is attached to the Tag Name of Reference
Parts.
•• In the case of M/A Types, AO parts are fixed to be displayed as AO16, and DI and
DO Parts are shown as DITYPE and DOTYPE, respectively. Logic Component Parts
are indicated according to logic type.

− 53 −
Chapter 3. RTC Job

Note •• In the case of Slot #, for Logic Component Parts the algorithm index is indicated
when the logic type is BlockAlgo, and the parameter index is indicated when the
logic type is Numeric and Flag.

Table 3-11. Display in Logic Component Parts

Item Description
Tag Name Indicates the Tag Name
Pnt Type LOGIC is always indicated
Block algorithm parts: (See *1)
Numeric Parts: “NUMERIC”
M/A Type Flag Parts: “FLAG”
Connection Parts: “CONNECT”
Gateway Parts: “GATEWAY”
If logic parts of the same tag name exist, displays
Node #
the node numbers of the logic parts (See *2)
Unit # Always “- -”
F/C Always “-”
Module/Block # Always “- - - -”
Block algorithm parts: Algorithm Index
Numeric Parts: Parameter Index
Slot# Flag Parts: Parameter Index
Connection Parts: Always “- - -”
Gateway Parts: Always “- - -”
Sheet # Indicates the Sheet Number
Pnt Desc Indicates the Point Descriptor

*1 In the case of block algorithm parts, their respective algorithm

types (LOGALGID(N)) are indicated. When (LOGALGID(N)) is “NULL,”
“(BLKALG)” is indicated.
*2 If there is no Logic Part of the same Tag Name, “---“ is indicated. If there
are multiple Logic Parts of the same Tag Name and if different node
numbers are set for them, “---” is also indicated.

■
■Collection of data
When the [Tag Name List/Search] window is opened, nothing is shown in the Tag Name List.
It is necessary to collect the data to be displayed.
At the point in time when an operation has been performed, collect all Tag Information in all
nodes, and display it after filtering it through the [Node Select], [Search], [Detail], or [Sort]
criteria.
To collect data, click the <Collect Data> button.

Note •• If [Node] is selected but no node has been selected yet or if [Search] or [Sort] cri-
teria are not set, the <Collect Data> button cannot be pressed.
•• The Control Parts on the Sheets in the Job Repository are not displayed in the list.

− 54 −
 3.3 Job Management

■
■Update of display
By choosing [Node Select], [Search], and [Sort] and pressing the <Update Display> button,
you can update the display of the list under the selected conditions.

Note •• Even if [Node Select], [Search], and [Sort] criteria are set when no data has been
collected, the <Update Display> button cannot be pressed.
•• The <Update Display> button displays the data at the point in time when
the <Collect Data> button is pressed. Therefore, if a Sheet is edited or if Parts
Information has been altered, it is necessary to collect data again.

■
■Searching Tag Names (filtering function)
In addition to showing all the Tag Names in it, the list can display only the Parts for which the
node numbers selected by executing [Node Select] are set. [Node Select] allows the selection
of multiple nodes.

In the [Search] item, you can select not only the display of “All Tags” but also “Some Tags
(I/O),” “Some Tags (Type),” “Some Tags (BlkType),” “Some Tags (Node),” and “Input Tag
Name.” Tags are listed after filtering through these criteria.

Note •• If “Some Tags (Type),“ “Some Tags (BlkType),” or “Some Tags (Node)” is set in the
[Search] item, it is necessary to set [Detail] criteria.
•• If “Input Tag Name” is set in the [Search] item, it is necessary that a character string
of one or more characters be entered in [Tag Name] of [Tag Name Search].

■
■Sorting the Tag Name List (Sorting Function)
The list can be presented in the order of Tag Name, Point Type, Sheet Number, Node Number,
Slot Number, or Module Number/Block Number. By selecting the desired sorting criteria and
clicking the <Update Display> button, the display of the Tag Name List is updated.

■
■Search by entering a Tag Name
This function allows you to directly enter a Tag Name to search for a Tag that agrees with the
character string. In Tag Names, you can use wild cards (“*” representing a character string of
0 or more characters and “?” representing one character).
If you choose the <Enter> key or the <Open Sheet from Tag Name> button when a Tag Name
has been entered, the search starts. If there is only one search result, the Sheet where the Part
is located is opened, with the Part displayed in the center of the Sheet in the selected condition.
If there are multiple search results, they are listed by the order set in the sort criteria.

− 55 −
Chapter 3. RTC Job

Note •• If no character is set in [Tag Name], the <Open Sheet from Tag Name> key cannot
be pressed.
•• When “Input Tag Name” is entered in the [Search] item, the <Collect Data> or
<Update Display> button cannot be pressed unless [Sort] and [Tag Name] are set.
•• If [Tag Name] is entered and if the <Enter> key or the <Open Sheet from Tag
Name> button is pressed, the [Search] item automatically changes to “Input Tag
Name.”
•• If a Part has been added, edited, or deleted on a Sheet, Parts Information may not
be properly displayed even if the <Open Sheet from Tag Name> button is pressed.
If you have edited a Sheet, collect data.

■
■Opening a Sheet from the Tag Name List
If you select a line in the list and click the <Open Sheet> button, the Sheet where the Part is
located is opened, with the Part displayed in the center of the Sheet in the selected condition.
You can also open a Sheet by double-clicking a line.
Because unlike Control Parts, FB Points are not Parts located on Sheets, Sheets are not opened.

■
■Exporting the Tag Name List
You can directly export the contents of a list in CSV format. You can export the file to spread-
sheet software such as Microsoft Excel.
To export a list, click the <Export> button in the list dialog box, and the [Save Information]
dialog box is displayed. By default the list is exported, with a .csv extension, directly under
the Job directory. Give it a file name. You can also export a list to any other directory with any
other extension.

■
■Replacing Tag Names
When a line in the list is clicked, it is selected (all lines are regarded as selected when no spe-
cific line is selected). Clicking the [Replace Tagname] button displays the [Replace Tagname]
dialog box to allow the Tag Name of the relevant tag to be replaced.
The [Replace Tagname] dialog box is described in detail in the following. (FB Points are not
subject to the described contents.)

a) Displayed Contents When the Dialog is Invoked

When the dialog is invoked, the Tag Name selected in the Tag Name List is shown in the
Replacement Candidate List (when no name is selected, all the tags displayed in the list are
shown in the Replacement Candidate List).
Note: Logic Component Parts, Reference Parts and FB Points are not shown.

− 56 −
 3.3 Job Management

b) Filtering of Replacement Candidate (Tags Subject to Replacement)

Performs filtering of the Tag names Subject to replacement. The sampling characters for the
character string for the Tag Names to be replaced are also specified. “*” (any string consisting
of more than 0 characters), “?” (any character), _ (underline), digits, and alphabetic letters can
be used for the character string.
By default, “(NO SETTING)” is specified. Also, “(NO SETTING)” is also used to display the
information selected in the Tag Name List again in the Replacement Candidate List.
To execute the filter, click the <Check> button. When this operation is performed consecu-
tively, multiple filtering modes can be applied.

Table 3-12. Description of the Format of Search Conditions

Search Subject Operator Example (Description)

Character strings that match the
Character string AI0001 can be retrieved by specifying AI0001
specified string
AI0001 or “AO0001” can be retrieved by
One single desired character ?
specifying A?0001
AI0001 or “AI0002” can be retrieved by speci-
A desired character string *
fying AI*

c) Definition of the Character String Resulting From Replacement

Used to specify the character string with which you want to replace the strings that are sam-
pled in b) as candidates for tag name replacement.
“*” (any string consisting of more than 0 characters, the character string corresponding to
the “*” specified in the character string to be retrieved is inherited), “?” (any single character,
the single character corresponding to the “?” specified in the character string to be retrieved
is inherited), _ (underline), digits, and alphabetic letters can be used for the character string.
Basically, this becomes as follows.
•• “*” behaves as a variable having multiple character strings.
•• “?” behaves as a variable having a single character string.(for items in which “?” appears
several times, the value is inherited.)

d) Creating the Replacement Image

When the <Check> button is clicked, the character string to be searched and the image of
the Tag Name resulting from replacement in accordance with the character string following
replacement are shown in the box for replacement candidates following replacement. The fol-
lowing table shows examples of character strings for searching the Tag Name together with
the character strings resulting from the replacement.

− 57 −
Chapter 3. RTC Job

Table 3-13. Tag Name Replacement Images (Examples)

Example Result of
Example of
of String Replacement
String to be Description
Following
Searched before after
Replacement
[Replacement of character string]
AI0001 DI01 AI0001 DI01
The string as such is replaced
[Replacement of the first character in the
string]
A* D* AI0001 DI0001
The first character is replaced by a different
character
[Replacement of the first character in the
string]
AI* DO* AI0001 DO0001 Replaced by a string with the same number
of initial characters, but with a different ini-
tial character string
[Replacement of the first character in the
A* H7A* AI0001 H7AI0001 string]
First character replaced by a character string
[Replacement of the first character in the
AI* I* AI0001 I0001 string]
The initial string is replaced by a character
[Replacement of final string]
*1 *2 AI0001 AI0002 The final character is replaced by a different
character
[Replacement of final string]
*01 *12 AI0001 AI0002 The final character string is replaced by a dif-
ferent character string
[Replacement of final string]
*001 *1 AI0001 AI01 The final character string is replaced by a
single character
[Replacement of final string]
*1 *123 AI0001 AI000123 The final character is replaced by a character
string
[Replacement of the initial and final strings]
AI*1 FIC*123 AI0001 FIC000123 The initial and final strings are replaced by
different strings
[Replacement of an intermediate character
string (*1)]
*0* *9* AI0001 AI9001
A character in the middle is replaced by a
different character
[Replacement of an intermediate character
string (*1)]
*00* *9* AI0001 AI901
A character string in the middle is replaced
by a character
[Character string added at the beginning]
* H7* AI0001 H7AI0001
A character string is added at the beginning

− 58 −
 3.3 Job Management

Example Result of
Example of
of String Replacement
String to be Description
Following
Searched before after
Replacement
[Character string appended to the end]
* *PS AI0001 AI0001PS
A character string is appended to the end
[Character at the beginning is deleted]
A* * AI0001 I0001
A character is deleted at the beginning
[Combination of deletion of beginning and
appending to the end]
AI* *PS AI0001 I0001PS
A character is deleted at the beginning, and a
character string is appended to the end
[Replacement of a desired initial character
AI0001 DI0001
string]
?* D*
A desired initial character is replaced by a
RC0001 DC0001
character
[Replacement of a desired initial character
AI0001 DO0001
string]

??* DO* A desired fixed-length initial character

string is replaced by a character string with
RC0001 DO0001
the same string length as the string being
replaced.
[Replacement of a desired initial character
AI0001 DO0001
string]
The initial character is retained in
A?* DO* [Replacement of a desired initial character
AO0001 DO0001 string], and the second character is replaced
by a character string with the same string
length as the string being replaced.
[Inheritance of the character string]
The initial and final characters are replaced
A????1 D????2 AI0001 DI0002 by the relevant characters, while the char-
acter string between these two characters
remains at fixed length
[Extraction of character string]

A?000? ?? AI0001 I1 A desired part of the characters are ex-

tracted, and the remaining characters are
linked to create the new string
[Extraction of character string (*2)]

*0* * AI0001 AI001 A desired character string is extracted, and

the remaining characters are linked to create
the new string

*1 When replacing intermediate characters, only the first encountered character string is
replaced.
*2 When only a single “*” is appended to the character string following replacement, the “*” of
the first and second character string to be searched are extracted.

− 59 −
Chapter 3. RTC Job

e) Deletion from Replacement Candidate List

By selecting a Tag Name (selection of multiple names is possible) in the Replacement
Candidate List and clicking the <Delete> button, the relevant Tag Name can be removed from
the Replacement Candidate List.
The Tag Name that will be excluded from replacement is deleted in the list.

f ) Editing the Tag Name Resulting From Replacement

This is a function for direct specification of the Tag Name following replacement.
Selecting one Tag Name in the Replacement Candidate List and clicking the selected line dis-
plays the Edit Box. This allows the Tag Name to be set or modifying by inputting a Tag Name
consisting of up to 16 characters.

g) Execution of Replacement
Clicking the <Replace> button executes the actual Tag Name replacement, in which the tags
for which the tag name following replacement has been set in the Replacement Candidate List
are replaced.
For Logic Component Parts, the replacement tracks the Tag Name replacement of the Logic
Part (the item having the same Tag Name as the one for which the replacement was carried
out) that is the source of the Logic Component Part. Also, in the same manner, for Reference
Parts the replacement tracks the Tag Name of the Part that is the source of the Reference Part.

− 60 −
 3.3 Job Management

Note •• The operation that executes the replacement of tag names cannot be reversed.
Carefully check and consider the Replacement Candidate List before executing
the function.
•• Only the parts that are sampled in the Tag Name List are subject to the tracking of
Tag Names of Logic Component Parts and Reference Parts.
•• In the case of Logic Component Parts and Reference Parts, if the source part’s tag
name is replaced, tracking and replacement of the Tag Names take place regard-
less of whether or not these are selected in the Tag Name List.
•• If the Tag Name of parts subject to tag name replacement is set in a parameter
(input destination/output destination parameter names) for connection to an-
other part, the parameter information of the connection destination is also
modified.
•• If Tag Name replacement is executed for encapsulated parts, only the tag name
information for each encapsulated part is replaced.
− A list of the tag names and parameters is displayed on the [Parameter] page of
the [Capsule Part] property sheet, but these tag names remain the tag names
at the time of encapsulation.
− Depending on the selected state of Tag Name .name on the [Parameter] page
of the [Capsule Part] property sheet, the contents of the replacement are not
reflected immediately after replacement is executed. The contents are reflected
when the property sheet is opened again.
Example: Even if AI0001 is replaced by H7AI0001 on the [Parameter] page of the
[Capsule Part] property sheet, the AI0001.name parameter does not
become H7AI0001.name, but remains AI0001.name. When the prop-
erty sheet is opened again, the value of the AI0001.name is changed
from “AI0001” to “H7AI0001”.

h) Exporting Replacement Results

The status of the replacement result can be saved as text format by clicking the <Save> button.

Restriction While Tag Name replacement is being processed, do not minimize other windows
(such as the [Tag Name List/Search] window or the main window of RTC Editor)
on RTC Editor. Otherwise, they will not return to their original sizes even if you
click the task bar. If you have minimized a window, return it to its original size by
performing “Switch To (S)” from the [Application] tab in Task Manager after the
replacement processing has been completed.

− 61 −
Chapter 3. RTC Job

3.3.8 Find Parameter Value Function

The Find Parameter Value function is a function of searching for tag and parameter settings in
Parts. This function is used to check tag and parameter reference relationships and to search
for Parts that have specific values.

■ display the Find Parameter Value window:

■To

Step 1 Activate the Job Structure Window.

Step 2 From the menu, execute the [Browser] → [Find Parameter Value] commands, and
the [Find Parameter Value] window opens.

■
■Executing searches
After specifying a character string and a scope of search, click the <Start> button, and the
values corresponding to the specifications are displayed. The types of character string specifi-
cation and scope specification are shown below.

Table 3-14.

Item Description
Specify a set value to be searched for.
Value Mandatory. (However, the edit box can be left blank to search for parameters
for which no values are set.) Wild cards can be used.
Specify the “hit” conditions for set values and parameter values.
Select from among “equal to” (=), “different from” (!=), “include” (&=),
Condition
“greater than” (>), “less than” (<), “equal to or greater than” (=>), and “equal
to or less than” (=<).
Exact searches are made, distinguishing between upper and lower cases of set
values and considering significant figures.
When the check box is off, no distinction is made between upper and lower
Match Full
cases, and significant figures are not considered. (Example: When the check
box is off, if a search is made subject to Set Value =”100” and Conditions =
“equal to,” “100.00” is also a hit.)
Specify a parameter name to be searched for.
Optional. If this is omitted, all parameters are searched. Multiple parameter
names can be specified by separating them with commas.
Parameter Name
When the <Select Parameter Name> button is pressed, the [Select Parameter
Name] dialog box opens, from which parameter names can be selected and
specified.
Specify a point type to be searched for.
Optional. If this is omitted, all point types are searched. Multiple point types
Point Type can be specified by separating them with commas.
When the <Select Point Type> button is pressed, the [Select Point Type] dia-
log box opens, from which parameter names can be selected and specified.
Specify a Sheet Name to be searched for.
Optional. If this is omitted, all Sheets are searched. Multiple Sheet Names can
be specified by separating them with commas.
As a Sheet Name, either a Sheet Name only or an absolute Sheet Name (a
Sheet Name including the path from the Root Sheet) can be specified. In
an absolute Sheet Name, the path from the Root Sheet must be separated
Sheet Name
by”\”(example:\UnitA\FB\AX01). Because an absolute Sheet Name uniquely
specifies a Sheet, it is necessary to specify an absolute Sheet Name to exactly
specify a Sheet.
When the <Select Sheet Name> button is pressed, the [Select Sheet] dialog
box opens, from which a Sheet Name can be selected and specified. The abso-
lute Sheet Name of a selected Sheet is added to the edit box.

− 62 −
 3.3 Job Management

Item Description
When the <Search Subsheet> check box is on, the Sheet specified by a Sheet
Search Subsheet
Name and all the layers in it are searched.
A search is narrowed from the previous search results.
When search results are displayed, the check box becomes valid. When a
Search within result
search is made with the check box turned on, the search results currently dis-
played, not the Parts of the Job, are searched for the set value.

■
■Display of search results
Upon completion of a search, search results are shown in the result display list at the bottom of
the window. When a search has been completed properly, search results consist of Tag Names
(“*” attached to parameters of Reference Parts and “@” attached to Logic Component Parts),
parameter names, set value, Sheet Names and Point Type. If there is any error in a search, an
error is displayed in the search results.

■
■Sorting search results (sorting function)
When search results include Tag parameters, the results can be sorted in order of Tag Names,
parameter names, set value, Sheet Names or Point Type.
Click the header of the line you want to sort, and the displayed results are sorted.

■
■Exporting search results
You can directly export search results in CSV format. You can export the file to spreadsheet
software such as Microsoft Excel.
To export search results, click the <Save> button, and the [Save Search Results] dialog box
is displayed. By default the results are exported, with a .csv extension, directly under the Job
directory. Give it a file name.

■
■Opening a Sheet from search results
When search results include Tag parameters, you can open the Sheet where the Part corre-
sponding to the Tag is located by selecting an item and clicking the <Open Sheet> button. On
the Sheet, the Control Part is displayed in the center. You can also open a Sheet by double-
clicking an item.
Because unlike Control Parts, FB Points are not Parts located on Sheets, Sheets are not opened.

− 63 −
Chapter 3. RTC Job

3.3.9 Output/Print Point Conf.

The Output/Print Point Conf. function is the function of either exporting the information on
a node or a point, as a document, to an Excel file or printing out such information. This func-
tion allows Point Generation results to be output.

■ perform Output/Print Point Conf.

■To
An Excel application is required to be installed. The following Excel versions are supported:
•• Excel 2000 (Office 2000)
•• Excel 2002 (Office XP)
•• Excel 2003 (Office 2003)
•• Excel 2007 (Office 2007)
•• Excel 2010 (Office 2010)

Note Using any version other than the above may cause improper operation of functions.

■■The following documents can be exported to an Excel file or printed out.

Table 3-15.

No. Document Name

- COVER
- CONTENTS
1. NODE ASSIGNMENT
2. COVER (NODE SPECIFIC ASSIGNMENT)
2.1 CONTROL SLOT MIX ASSIGNMENT
2.2 I/O MODULE ASSIGNMENT (Software)
2.3 I/O MODULE ASSIGNMENT (Hardware)
2.4 POINT MIX PU/MU CALCULATION
3. COVER ( SLOT ASSIGNMENT )
3.1 SLOT ASSIGNMENT ( I/O POINT )
3.2 SLOT ASSIGNMENT ( I/O POINT [WITH DESCRIPTOR] )
3.3 SLOT ASSIGNMENT ( REGULATORY CONTROL POINT )
3.4 SLOT ASSIGNMENT ( REGULATORY PV POINT )
3.5 SLOT ASSIGNMENT ( DIGITAL COMPOSITE POINT )
3.6 SLOT ASSIGNMENT ( LOGIC POINT )
3.7 SLOT ASSIGNMENT ( FLAG POINT )
3.8 SLOT ASSIGNMENT ( NUMERIC POINT )
3.9 SLOT ASSIGNMENT ( NMARRAY POINT ) [R411 or later]
3.10 SLOT ASSIGNMENT ( STRING POINT ) [R411 or later]
3.11 SLOT ASSIGNMENT ( DATETIME POINT ) [R411 or later]
3.12 SLOT ASSIGNMENT ( TIMER POINT )
3.13 SLOT ASSIGNMENT ( PROCESS MODULE POINT )
3.14 SLOT ASSIGNMENT ( FUNCTION BLOCK POINT )

− 64 −
 3.3 Job Management

No. Document Name

4. COVER ( POINT CONNECTION ASSIGNMENT )
4.1 CONNECTION ASSIGNMENT ( REGULATORY CONTROL POINT )
4.2 CONNECTION ASSIGNMENT ( REGULATORY PV POINT )
4.3 CONNECTION ASSIGNMENT ( DIGITAL COMPOSITE POINT )
4.4 CONNECTION ASSIGNMENT ( LOGIC POINT )
5. COVER ( TAG NO. LIST )
5.1 TAG NO. LIST ( ANALOG INPUT POINT )
5.2 TAG NO. LIST ( ANALOG OUTPUT POINT )
5.3 TAG NO. LIST ( DIGITAL INPUT POINT )
5.4 TAG NO. LIST ( DIGITAL OUTPUT POINT )
5.5 TAG NO. LIST ( VALUE IN POINT )
5.6 TAG NO. LIST ( VALUE OUT POINT )
5.7 TAG NO. LIST ( DIGITAL COMPOSITE POINT )
5.8 TAG NO. LIST ( REGULATORY PV POINT )
5.9 TAG NO. LIST ( REGULATORY CONTROL POINT )
5.10 TAG NO. LIST ( LOGIC POINT )
5.11 TAG NO. LIST ( FLAG POINT )
5.12 TAG NO. LIST ( NUMERIC POINT )
5.13 TAG NO. LIST ( NMARRAY POINT ) [R411 or later]
5.14 TAG NO. LIST ( NMARRAY POINT [WITH VALUE]) [R411 or later]
5.15 TAG NO. LIST ( STRING POINT ) [R411 or later]
5.16 TAG NO. LIST ( DATETIME POINT ) [R411 or later]
5.17 TAG NO. LIST ( TIMER POINT )
5.18 TAG NO. LIST ( PROCESS MODULE POINT )
5.19 TAG NO. LIST ( FUNCTION BLOCK POINT )
5.20 TAG NO. LIST ( FFFB POINT )

*1 For the I/O MODULE ASSIGNMENT, SLOT ASSIGNMENT, CONNECTION ASSIGNMENT, and
TAG NO. LIST (except the COVER), documents (files) are separated in directories which are
created for each node.
*2 The unused modules in the I/O MODULE ASSIGNMENT are not output in the documents
(the module numbers are omitted).
*3 The unused slots in the SLOT ASSIGNMENT, CONNECTION ASSIGNMENT, and TAG NO. LIST
(except the COVER) are not output in the documents (the slot numbers are omitted).
*4 The documents of some point types that do not exist for each node type are not output.

− 65 −
Chapter 3. RTC Job

■
■Displaying the [Output/Print Point Conf] Dialog Box
Activate the Job Structure Window and execute the [Job(J)] → [Output/Print Point Conf (P)]
command to open the [Output/Print Point Conf] dialog box.

Figure 3-2. [Output/Print Point Conf] Dialog Box

■
■Outputting a Document to a File

Step 1 Specify a node to be output to a document.

[All node]: Outputs all the nodes in the job to a target.
[Select node]: Outputs the selected node to a target.

Step 2 Specify a document to which the node is output.

Move the document to [Output list].
Use the <←> and <→> buttons to switch between [None output list] and [Output
list].

Step 3 Click the <Execute...> button.

Step 4 Specify a document output destination.

The [Setup Directory] dialog box appears; specify the output destination in it.
The default directory is “[job directory]\pnfdef.”

Note When documents (Excel files) exist in the specified output destination,
they are overwritten in sequence.

− 66 −
 3.3 Job Management

■
■Printing a Document
Before printing a document, set up the printer.

Step 1 Specify the node to be output to the document.

[All node]: Outputs all the nodes in the job.
[Select node]: Outputs the selected node.

Step 2 Specify the document to which the nodes are output.

Move the document to [Output list].
Use the <←> and <→> buttons to switch between [None output list] and [Output
list].

Step 3 Select the [Output print] check box.

Step 4 Specify the printer for printing.

Select it from the [Printer:] list.
When multiple printers are set up, the document is output to the default printer.

Step 5 Specify an Order print.

[List]: Prints the documents specified in [Output list] from top to bottom.
[Node]: Prints the documents with the same node number in batch.

•• Example of the Order print:

Print conditions:
Specified nodes: Node11, Node12
Documents to which the nodes are output:
(1) COVER ( SLOT ASSIGNMENT )
(2) SLOT ASSIGNMENT ( REGULATORY CONTROL POINT ) for Node11
(3) SLOT ASSIGNMENT ( REGULATORY CONTROL POINT ) for Node12
(4) SLOT ASSIGNMENT ( REGULATORY PV POINT ) for Node11
(5) SLOT ASSIGNMENT ( REGULATORY PV POINT ) for Node12
(6) COVER ( TAG NO. LIST )
(7) TAG NO. LIST ( REGULATORY CONTROL POINT ) for Node11
(8) TAG NO. LIST ( REGULATORY CONTROL POINT ) for Node12
(9) TAG NO. LIST ( REGULATORY PV POINT ) for Node11
(10) TAG NO. LIST ( REGULATORY PV POINT ) for Node12
Order print:
When [List] is selected:
(1) → (2) → (3) → (4) → (5) → (6) → (7) → (8) → (9) → (10)
When [Node] is selected:
(1) → (2) → (4) → (3) → (5) → (6) → (7) → (9) → (8) → (10)

Step 6 Click the <Execute...> button.

Step 7 Specify a document output destination.

The [Setup Directory] dialog box appears; specify the output destination in it.
The default directory is “[job directory]/pnfdef.”

− 67 −
Chapter 3. RTC Job

■
■Canceling the Execution

Step 1 Click the <Stop> button.

You can stop the process at any time but it may take some time.

■
■Saving the Results of Status

Step 1 Click the <Save...> button.

Step 2 Specify a save destination.

The [Save the result of output point configuration status] dialog box appears. By
default, the results are saved as the “pntdef_status.txt” file right under the job direc-
tory. Provide any file name as required.

■
■“SLOT ASSIGNMENT ( I/O POINT )”
The tag names registered in each slot are output to the “SLOT ASSIGNMENT ( I/O POINT ).”
When the I/O point is used only by Hardware address reference with no tags registered, the
control point tag name that refers to that I/O point is output in brackets. This is the same pro-
cedure as the “SLOT ASSIGNMENT ( I/O POINT [WITH DESCRIPTOR] ).”

■
■Information to Be Output on the COVER
When various information about a job has been entered in the [Job Information] dialog box,
they are output on the COVER. For the [Job Information] dialog box, refer to 3.3.1, “Job
Information.”
The following shows the correspondence table of the items between the COVER and the [Job
Information] dialog box.

Table 3-16. Correspondence table of items between the cover and the [Job Information] dialog box

Cover [Job Information] dialog box

Customer (1st line) Customer 1
Customer (2nd line) Customer 2
Plant Equipment Name
Project (No corresponding item exists)
System job No. (No corresponding item exists)
Section Supplier
Design Designer 1
Date Project Finish Date
Revision Revision
Note Note

− 68 −
 3.3 Job Management

■
■Regarding performing RTC while executing the Output/Print Point Conf. function
If a node or point information registered for a job is large in quantity, it takes a long time to
output a file. Even in such a case, however, RTC work, such as a search for a Tag Name or the
addition of a Part, can be performed.

Note Although the addition of a Control Part or Point Generation can be performed while
executing the Output/Print Point Conf. function, the document being output will
not reflect any data resulting from such operation.

Note When document is not output all 10 min, printer may have some problem. So RTC
Editor shows error message. Please confirm the Printer Status.
User can change this error detection interval. In rtcedit.ini file, change value (de-
fault=10) of MaxRetryCounts key under [OutputPointList] section.

Restriction •• During the online operation, do not execute the Output/Print Point Conf.
function.
•• During the execution of the Output/Print Point Conf. function, do not use any
application program that uses the Clipboard. The use of such application pro-
grams will cause the data being stored in the Clipboard, which has been used
since the creation of a document by the Output/Print Point Conf. function, to be
replaced.

− 69 −
Chapter 3. RTC Job

MEMO

− 70 −
 4.1 Management of Sheets

Chapter 4. About Sheets

On Sheets, you can graphically edit process control applications by using Control Parts and
Picture Parts. The major functions of Sheets are mentioned below.

■
■Major functions of Sheets
•• Process control can be designed using Control Parts.
•• Comments and graphics can be entered using Picture Parts.
•• Using Containers, a Sheet can be given hierarchical relationships with other Sheets.

4.1 Management of Sheets

4.1.1 What is Sheet?

A Sheet is described as a Container Part that belongs in a parent Sheet. For this reason, the
words “Container” and “Sheet” are used interchangeably in this document. One individual
Sheet may be displayed in or more in a Sheet Windows.

■
■Sheet Name
Sheet Name is the same as the Logical Tag Name assigned to its corresponding Container Part.
Refer to 5.2.4, “Container Parts” about how to set Logical Tag Name.

■
■Sheet File
With RTC Editor, a Sheet is saved as a Sheet file. Each Sheet file has a unique name based on
the Sheet Name.

4.1.2 Creating and Saving Sheets

■ create a new Sheet:
■To
A new Sheet can be created by one of the following three methods:
•• Locating Container Parts on a Sheet.
•• Executing the [New] command from the [File] menu.
•• Clicking the <New> button in the tool bar.

■ create a Sheet by creating a new Container:

■To
See 5.2.4, “Container Parts.”

− 71 −
Chapter 4. About Sheets

■ create a new Sheet from the menu and tool bars:

■To
Sheets created by these methods are added to the Job Repository in the Job Window.

Step 1 Activate a Sheet, and execute the [New] command from [File] in the menu.
Alternatively, click the <New> button in the tool bar.

Step 2 A new Sheet is opened. The Sheet file name “Container?_n.sht” (both ? and n rep-
resenting numbers managed by RTC Editor) is displayed as the title of the Sheet.

Step 3 The Job Window displays a Container corresponding to the Sheet newly added to
the Job Repository.

■ overwrite and save a Sheet:

■To
When newly created, a Sheet is saved once with a default file name. When you have performed
an operation such as locating a Part on the Sheet, be sure to overwrite and save it. To overwrite
and save a Sheet, use either of the following ways:

Step Activate the Sheet, and execute the [Save] command from the [File] menu.

Step Click the <Save> button in the tool bar.

If you add a change to a Sheet and try to close it or exit the Job without overwriting and saving
the Sheet, a message is displayed to ask you whether the Sheet should be saved. If you click
<Yes>, the Sheet is overwritten and saved.

■ change a Sheet Name:

■To
To change a Sheet Name, change the Container Name. For details, see 5.2.4, “Container Parts.”

− 72 −
 4.1 Management of Sheets

■ add a name to a Sheet and save it:

■To
The [Save As ...] operation does not simply mean to change the Sheet Name. When the [Save
As ...] operation is performed, the Sheet is saved in the Job Repository with a new Sheet Name
specified in the open Sheet. The original Sheet remains in the state in which it was overwritten
and saved last time. Follow the procedure described below.

Step 1 From [File] in the menu, execute the [Save As ...] command, and the [Save As]
dialog box appears.

Step 2 In the [Save As] dialog box, choose the Job directory as the directory. (Because the
default is the Job directory, no operation is actually necessary.)

Step 3 Enter the Sheet Name in the [File name:] box. You can directly enter the Sheet
Name. No extension is necessary.

Step 4 RTC Editor deletes the extension (if entered) from the entered Sheet Name and
adds “_?.sht” to the end of the character string to set a new Sheet file name. (The
“?” represents a number managed by RTC Editor.)

Step 5 Lastly, click the <Save> button.

When a Sheet containing lower layers is named and saved, each of the lower layers is saved.

− 73 −
Chapter 4. About Sheets

4.1.3 Opening and Closing Sheets

This subsection explains how to keep a Sheet active and open another Sheet, and how to close
an open Sheet. Sheets can also be opened from the Job Window. For the method of opening a
Sheet from the Job Window, see 3.1, “The Job Structure Window.”

■ open a Sheet:
■To
•• Double-click a Container on a Sheet or choose [Properties] in the [Edit] menu to open
the property sheet of the Container. On the property sheet, click the <Open Sheet> but-
ton, and the Sheet corresponding to the Container opens.

•• Activate the Sheet, and invoke the [Open] dialog box by executing the [Open] command
from [File] in the menu. In the [Open] dialog box, choose the Sheet from the [File name]
box, and click the <Open> button.

•• From the menu, execute the [n-File Name] command in [File] to open the Sheet file
indicated by the file name.

Note You cannot open a Sheet of another Job. If you want to display and edit a Sheet of
another Job, start RTC Editor separately.

■
■Close a Sheet

Step 1 Choose the [Close] command from [File] menu of Sheet Window.

Step 2 If the content of a Sheet has been modified, a message appears, prompting you to
save it.

− 74 −
 4.1 Management of Sheets

4.1.4 Sheet Information Dialog Box

Sheet Information is a dialog box in which you can set the Equipment Name and Version
Number for each Sheet. Because Sheet Information provides very effective data when the
Sheet is used again, be sure to enter information as accurately as possible.

■ invoke the [Sheet Information] dialog box:

■To
•• Activate a Sheet, and execute the [Sheet Info] command from the [File] menu.

•• Click a Container in the Job Window, and execute the [Sheet Info] command from the
[File] menu.

•• Right-click in the Job Window, and a pop-up menu appears. From the menu, execute the
[Sheet Info] command.

Table 4-1. [Sheet Information] dialog box

Item Description
Sheet Name Type in Container Part's [Properties] property sheet
Full path name of Sheet File Sheet File Name is given by RTC Editor based on
Sheet File Name
Sheet Name
Last Modified Date when the Sheet was last saved
Enter the integer for the sheet number (the default setting is 0).
Leading zeroes (0) placed before a numerical value are suppressed (for example,
an input 053 is recognized as 53).
Sheet Number Input must be an integer from 0 to 999999999 (9 digits).
This number can be displayed on the sheet using the Sheet Number Parts.
In addition, this number can also be displayed on the side of the container in the
Job Structure Window.
Sheet Title Sheet Title can be any text and it appears on the surface of the Sheet Title Part
Version Version can be any text and it appears on the surface of the Version Part
Note You can use this box for any notations or comments

4.1.5 Export/Import Sheet Info

Using [Export Sheet Info], information of sheet can be exported to a file. Using [Import
Sheet Info], a file in the [Export Sheet Info] format can be imported, and configure the Sheet
Information as a batch. In addition, hierarchy of sheets can be created as a batch.

− 75 −
Chapter 4. About Sheets

4.1.5.1 Export Sheet Info

Select the sheet to be exported in the Job Structure Window, and select [Job] → [Export Sheet
Info] from the menu to display the [Export Sheet Info] dialog box.
The following sheet information can be exported in the form of an Excel or CSV format file:
•• Sheet Path Name
•• Sheet Name
•• Sheet Number
•• Sheet Title
•• Revision
•• Template File (headline only)
•• Last Modified (export only)
•• Sheet Path Name of copy (headline only)

Table 4-2. Export Format

Sheet Path
Sheet Last
#Sheet Path Name Sheet Name Sheet Title Revision Template File Name of
Number Modified
copy
&SHEETPATHNAME SHEETNAME SHEETNUM SHEETTITLE REVISION TEMPLATEFILE TIMESTAMP COPYSHEET
2005/06/05
\JOB JOB 0 JOB 1
16:00:00
2005/06/05
\JOB\Unit1 Unit1 1 Unit1Loop 2
16:00:00
2005/06/05
\JOB\Unit2 Unit2 2 Unit2Loop 3
16:00:00
2005/06/05
\JOB\Unit3 Unit3 3 Unit3Loop 4
16:00:00

Note You cannot export template information using [Export Sheet Info], even if a tem-
plate is set in the sheet.

4.1.5.2 Import Sheet Info

Select [Job] → [Import Sheet Info] from the menu in the Job Structure Window to display the
[Import Sheet Info] dialog box.

■ Sheet Information
■Set
[Set Sheet Information] is used to import an Excel or CSV file, which is written in the [Export
Sheet Info] format, and configure the Sheet Information (the columns “Last Modified” and
“Sheet Path Name of copy” are ignored).

■
■Create Sheet
[Create Sheet] is used to create a sheet hierarchy which is specified in the column “Sheet Path
Name.” This can also be used to configure the Sheet Information (the columns “Sheet Name,”
“Last Modified,” and “Sheet Path Name of copy” are ignored).

− 76 −
 4.1 Management of Sheets

■
■Copy Sheet (including parts)
[Copy Sheet (including parts)] is used to create a sheet hierarchy by copying the sheet speci-
fied in the column “Sheet Path Name of copy” to the hierarchy specified in the column “Sheet
Path Name.” This can also be used to configure the Sheet Information (the columns “Sheet
Name” and “Last Modified” are ignored).

Table 4-3. Excel File Setting Items

Column Description
Specify the full path of a sheet which starts with the
Root Sheet or “\Job Repository”

•• For [Set Sheet Information]

Specify a sheet to which the Sheet Information is to
be configured.
#Sheet Path Name &SHEETPATHNAME If no jobs exist on the sheet, an error occurs.
“\Job Repository” cannot be specified.

•• For [Create Sheet] and [Copy Sheet (Including

parts)]
Create a specified sheet hierarchy.
If a job sheet already exists, an error occurs.
Set Sheet Name (Container Name)

•• For [Set Sheet Information]

Change the Sheet Name of “Sheet Path Name.”
Sheet Name SHEETNAME If a job sheet already exists, an error occurs.

•• For [Create Sheet] and [Copy Sheet (Including

parts)]
The setting is ignored.
Set Sheet Number.
Sheet Number SHEETNUM
Set an integer between 0 and 999,999,999.
Set Sheet Title.
To start a new line, enter “\n”
Sheet Title SHEETTITLE
To empty the settings, enter “” (2 double quotation
marks)
Set Revision.
Revision REVISION To empty the settings, enter “” (2 double quotation
marks)
Specify Template File.
Specify the file name for a file under “Job Directory\tpl”
You can also specify the full path of a file (eg c:\temp\
Template File TEMPLATEFILE
custom1tpl)
To clear a sheet template, enter “” (2 double quotation
marks)
This setting is exported with [Export Sheet Info] but
Last Modified TIMESTAMP
ignored with [Import Sheet Info]
Specify the full path of a sheet which exists in the job
and starts with the Root Sheet or “\Job Repository”

•• For [Set Sheet Information] and [Create Sheet]

Sheet Path Name
COPYSHEET This setting is ignored
of copy
•• For [Copy Sheet (Including parts)]
Specify a sheet to be copied
If no jobs exist on the sheet, an error occurs

− 77 −
Chapter 4. About Sheets

■
■Examples of Copy Sheet (Including parts)
•• As the upper level sheet is copied, the lower level sheets are also copied
#Sheet Path Name Sheet Path Name of copy
&SHEETPATHNAME COPYSHEET
\ABReactor\UnitA \Job Repository\Preparation
\ABReactor\UnitB \Job Repository\HeatTreatment
\ABReactor\UnitC \Job Repository\Extract

Figure 4-1.

•• As the upper sheet above is copied, the Sheet Names of the lower level sheets are changed
#Sheet Path Name Sheet Path Name of copy
&SHEETPATHNAME COPYSHEET
\ABReactor\UnitA \Job Repository\Preparation
\ABReactor\UnitB \Job Repository\HeatTreatment
\ABReactor\UnitB\Interlock \Job Repository\HeatTreatment\TempInterlock
\ABReactor\UnitB\Program \Job Repository\HeatTreatment\TempProgram
\ABReactor\UnitC \Job Repository\Extract

Figure 4-2.

− 78 −
 4.1 Management of Sheets

4.1.6 Printing Sheets

Sheets can be printed, enabling the compilation of printouts to make drawing documents.

■
■Print a Sheet
You can print a sheet in either of the following two ways:

Step Activate a sheet and execute the [File] → [Print] commands.

Step Activate a job hierarchical sheet, open the [Sheet List] dialog box by executing
[Browser] → [Sheet List] from the menu, select the sheet you want to print, and then
click the <Print Sheet> button. This method allows continuous printing of multiple
sheets.

Whichever operation is selected, the [Print] dialog box appears. In this dialog box,
specify the printing scope, number of copies, printing quality, etc. and click the <OK> button.
Then printing will start. If you click the <Properties> button, a [Properties] property sheet
(described later) appears.

Restriction In some cases, the contents of a sheet may not be printed out correctly, depending
on the printer.

Note When multiple sheets are printed out, items set up in the [Print] dialog apply to all
sheets. Settings made for specific sheets are the same as those for other sheets.

■
■Print Preview
Choose the [Print Preview] command from the [File] menu of Sheet Window.
Print Preview is displayed.

■
■Printer Settings
Printer to be used, print sheet paper, and print direction (vertical or horizontal) can be
specified.
When setting the printer, select [File] to execute the [Print Setup] command. In the [Print
Setup] dialog, click the <Properties> button to display the [Properties] property sheet.
When the [Properties] property sheet, set the appearance (resolution, scaling (%), etc.) and
True Type Font alternatives.

A3 paper is available for printout at full size. To use A4 sheet paper, select the horizontal direc-
tion with the scale set to 70%.

Note To print or use print preview, set the printer in advance. When the printer is not set,
the print preview may not be displayed correctly.

■
■Print Scale Setup
This new operation is provide as a fix in case the printer driver does not support reduction or
enlargement of printed elements. Enables specifying a percentage in a new dialog box (Print
Scale) which is selected from the [File] Menu.

− 79 −
Chapter 4. About Sheets

4.2 Applications of Sheet

4.2.1 Operations on RTC Parts

■
■Create RTC Parts in a Sheet
Assign parts onto sheets in accordance with the following procedure.

Step 1 Choose a button in RTC tool bar.

Step 2 Click anywhere in a Sheet, to create RTC Part.

Step 3 The location of the mouse click will become the bottom-left corner of the rectangle
surrounding created the RTC Part.

Step 4 Parts will not be created if mouse click is outside the sheet. A part of Parts may be
outside the sheet if mouse click is near a border of the sheet.
All the data out of the sheet are not printed therefore move them are inside it.

Step 5 The size of the Parts that are created with mouse drag are specified by rubber-band
box. The Window will be scrolled, if the mouse drag is continued at the edge of it. If
the end point of the mouse drag is outside the sheet, it is regarded as on the border
of the sheet.

Step 6 When a Part is created, the corresponding button is deselected in the RTC tool bar.

Step 7 If you keep pressing the [Shift] key while creating a RTC Part, the selected buttons
are kept active, thus enable to create multiple RTC Parts of the same type.

■
■Selecting RTC Parts
Parts on the sheet can be selected in accordance with the following procedure.

Step Click the <Select> button on the RTC tool bar.

Move the mouse over RTC Part and click there.
When you select an RTC Part, all previously-selected RTC Parts are deselected.

Step If you keep pressing the [Shift] key during the select operation, you can select an
additional RTC Part along with previously-selected Parts.
If you select previously selected Parts with pressing the [Shift] key, you can deselect
them.

Step By dragging the mouse, you can select multiple RTC Parts within the rubber-band
box.

Step By pressing the [Shift] key during the mouse drag, select the RTC Parts within the
rubber-band box range and at the same time deselects the already selected Parts.

Step By choosing the [Select All] command from the [Edit] menu, all RTC Parts on the
Sheet are selected.

− 80 −
 4.2 Applications of Sheet

■
■Moving Parts
Once RTC Parts are selected, you can move them anywhere within the Sheet by dragging the
mouse or pressing the keyboard arrow keys.
If the RTC Part gets to the Window’s boundary and you continue to move it, the Window
starts scrolling. It scrolls until the Part reaches the Sheet boundary. You cannot move the Parts
to out of Sheet. They stay edge of sheet. When moving a Control Parts, any connected links,
move accordingly. When moving an RTC Part by pressing arrow keys, how much it moves by
a single key-press depends on the Gridline settings.
If [Snap To Grid] command is selected from [View] menu, a single arrow key moves Parts to
the next Gridlines. If not, it moves Parts by one screen pixel.

■
■Resizing Parts
Some RTC Parts can be resized.
When a resizeable Part is selected, block handles () appear on its bounding rectangle. When
the mouse runs over moved on the handles, the cursor appears as an arrow, and you can resize
the Part.
With grouped Parts, the resize operation affects only resizeable Parts within the group.

■
■Changing the Shape of RTC Parts
You can change the shape or contents of some RTC Parts using <Reshape> button.
•• With Line Parts and Polyline Parts, <Reshape> button enables you to add or move joints.
Select a Line or Polyline Parts and choose <Reshape> button. Joints appear as handles
(), which you can drag and move. If you click anywhere on the line and move the cursor,
you can add another joint. If you move a joint so two lines meeting at the joint becomes
straight, the joint disappears.

•• For Title Parts pressing <Reshape> button enables you to edit text within the Parts.

■
■Deleting or Cutting RTC Parts
Select RTC Part on a Sheet and choose [Cut] command from [Edit] menu of Sheet Window
or click <Cut> button from the standard tool bar.
The cut Parts are moved to the Clipboard, and disappear from the Sheet.

■
■Copying RTC Parts
Select RTC Parts on the Sheet and choose [Copy] command from [Edit] menu of Sheet
Window or click <Copy> button from the standard tool bar.
The Parts are copied to the Clipboard.

− 81 −
Chapter 4. About Sheets

■
■Pasting RTC Parts
Choose the [Paste] command from [Edit] menu of Sheet Window or click the <Paste> button
from the standard tool bar. The Parts in the Clipboard are copied at the upper left-hand corner
of the active Sheet.

Note When executing a paste command several times successively, pasted Parts are
placed one on top of the other and so may appear as only one Part. Be sure to check
beneath the top part for other pasted Parts.

■
■Deleting RTC Parts
Select RTC Parts on the Sheet and choose the [Delete] command from the [Edit] menu of
Sheet Window. The Parts disappears from the Sheet.

■
■Undo and Redo
Some operations on the Sheet can be undone. Up to 20 such operations are recorded and can
be undone. Also, you can redo up to 20 previously undone operations.
To undo operations, choose the [Undo] command from the [Edit] menu of Sheet Window, or
choose the <Undo> button from standard toolbar.
To redo undone operations, choose the [Redo] command from the [Edit] menu of Sheet
Window, or choose the <Redo> button from standard toolbar.

•• Undo-able Operations
Following operations can be undone, and redone:
− Create, Delete, Cut, Copy, Paste, Move RTC Parts
− Set Drawing Mode or Fonts of RTC Parts
− Object Linking and Embedding

•• Recording of Undo and Redo Operations

Up to 20 Undo and Redo operations can be recorded per sheet.

•• View Editing and [Undo]/[Redo]

The RTC Editor allows editing of the view of parts and sheet. For details, refer to the de-
scriptions in the sections 4.3.2, “Custom View” 4.3.3, “Class View”, and 4.3.4, “Template
Edit Mode.”

Operations in the view edit modes are recorded for each editing mode individually. When
a view editing is completed and you return to sheet editing, the operation subject to Undo
and Redo operations will be the operation performed on the sheet immediately before view
editing was started. Once view editing is completed, the record of operations in the view
editing mode is deleted. Accordingly, there will be no operations subject to Undo and Redo
at the time that you move to the view editing mode.

− 82 −
 4.2 Applications of Sheet

Note Recorded operations are automatically voided by either of following operations:

•• Creating Container Parts
•• Setting Properties of Control Parts
•• Connecting or deleting Parameter Links between two Control Parts.

Note Container Parts deleted cannot be restored exactly. If you [Undo] the deletion of a
Container Part, the Container Part, which remains deleted in the Sheet window, is
displayed in the Job Repository in the Job window. If you [Redo] the addition in this
state, the Container Part is displayed not in its original location in the Sheet window
but in the upper left corner of the Sheet.

Note Undo or Redo cannot be performed for the operation in Job Structure Window. For
example, undo for moving container in Job Structure Window cannot be performed.

− 83 −
Chapter 4. About Sheets

4.2.2 Drawing Mode

■
■Display of the [Drawing Mode] dialog box
The [Drawing Mode] dialog box can be displayed by choosing the [Drawing Mode] command
from the [View] menu or by choosing the <Drawing Mode> button in the tool bar.
Because the [Drawing Mode] dialog box is a floating dialog box, you can select Parts and
change their drawing attributes with the dialog box kept open.
Once the [Drawing Mode] dialog box is displayed, it continues to be displayed until the
<Close> button in the dialog box, the <Drawing Mode> button in the tool bar, or the
[Drawing Mode] command in the [View] menu is chosen. While the dialog box is displayed,
a check mark appears at the top of the menu item.
The [Drawing Mode] dialog box is always displayed on top of the Job Window and Sheets.
When the tool bar overlaps with the Parts Bar, you can cause the hidden one to come forward
by right-clicking it.
The [Drawing Mode] dialog box is displayed only when a Sheet is active. It is not displayed
when the Job Window is active.

■
■Changing the settings for drawing Parts
For some types of Parts, you can change the line width, line color, background color, fill pat-
terns, and so on. You can do the resetting in the [Drawing Mode] dialog box.
Select a Part or Parts on a Sheet, and do the resetting in the [Drawing Mode] dialog box to
change the drawing settings for the Part or Parts. This resetting also changes the default set-
tings for the type or types of Parts to be created thereafter.

If you make drawing settings without selecting a Part, it changes the default drawing settings
for Parts to be created thereafter.
After clicking the <Line/Text> button, choose the line color and line width.
After clicking the <Fill> button, set the line color and type.

Note From the time when RTC Editor is started until the drawing settings are changed for
the first time, the drawing settings are default settings.
•• Default settings
- Lines and text: color = black, line width = 0.1 mm
- Fill: color = white, pattern = solid
Once drawing settings are changed, the settings apply to Parts to be created
thereafter.

Note The settings displayed in the [Drawing Mode] dialog box are currently valid settings.
Even if you select a Part created in the past and open the [Drawing Mode] dialog
box, it does not display the drawing attributes of the Part.

Note When you have chosen Transparent (no pattern) as [Pattern:] of [Fill] in the drawing
mode, you cannot choose Parts without clicking their border lines.

Restriction In the [Drawing Mode] dialog box, you cannot create colors other than those pro-
vided. The <Set Color> button is always invalid.

− 84 −
 4.2 Applications of Sheet

4.2.3 Embedding and Linking Objects

A Sheet can be used as an OLE server, and OLE objects can be embedded or linked in Sheets.
For example, pictures from a painting program, text from Microsoft Word, or spreadsheets
from Microsoft Excel can be pasted into a Sheet.
Embedded objects are represented by icons and are surrounded by a solid line. When you
link to objects in the Sheet, the objects are represented by icons surrounded by a dotted line.

Note After embedding or linking objects in a Sheet and copying the Sheet to another
PC, you must make sure that the application exists in the new environment. Also,
with linked objects, you must also make sure that the source file exists in the new
environment. Otherwise, you cannot edit the embedded or linked objects in the
new environment.

■
■Embedding Objects
Executing the [Edit] → [Insert New Object] commands displays the [Insert Object] dialog box.
You can select whether to create a new object or imbed an existing object by using the option
buttons in the dialog. Creation of a new object is selected by default.

•• Creating a New Object

Step 1 Click the [Create New] option button in the [Insert Object] dialog box.

Step 2 Application names appear in the [Object Type] list box. Select the appropriate ap-
plication and then click the <OK> button to invoke the application.

Step 3 When you execute the [Exit] or [Save As] command after the task has been com-
pleted in the application, a confirmation dialog appears, asking you whether you
want to update the object at the embedding destination. When the <OK> button is
clicked, the contents are embedded in the sheet.

•• Inserting Already Created Objects

Step 1 Click the [Create From File] option button in the [Insert Object] dialog box. The
display changes to allow the file name of the object to be input.

Step 2 Specify the file by entering the file name in the [File] text box, or select it from the
files that are shown in the file dialog when you click the <Browse> button.

Step 3 When you leave the [Link] checkbox in the default state, i.e., not selected state, the
object is embedded (linking is described later).

•• Inserting Objects Via the Clipboard

Objects can be embedded in sheets by copying and pasting contents created with other
applications.

− 85 −
Chapter 4. About Sheets

■
■Linking Objects
In the state in which the [Create From File] option button in the [Insert Object] dialog is se-
lected, select the [Link] checkbox. This will link the object specified for insertion to the sheet.

Note The RTC Editor does not support linking via the Clipboard.

■
■Selecting How the Object Is Displayed
You can select whether the contents of the object or an icon should be shown on the sheet.

•• Whether to Select Icon Display

When the <Display As Icon> checkbox is selected in the following dialogs, the object is
shown as an icon. When the checkbox is not selected, the contents of the object are shown.
− The [Insert Object] dialog box displayed by executing the [Edit] → [Insert New Object]
commands.
− The [Convert] dialog box displayed by executing the [Edit] → [(Application name)
Object] → [Convert] commands after selecting the object in the sheet.

•• Changing the Icon

The icon representing the embedded object can be changed as desired. When the <Display
As Icon> checkbox in the dialogs described above is selected, the <Change Icon> button
is displayed. Click this button to display the [Change Icon] dialog box.

In the [Change Icon] dialog box select any of the option buttons in accordance with how
you want to display the icon.

Table 4-4.

Icon Meaning
Current The icon currently used in the sheet.
Default The default icon for the application.
The icon stored in the file specified by file name.
From File Specify the file by entering the file name directly, or specify the file
after displaying the file dialog by clicking the <Browse> button.

− 86 −
 4.2 Applications of Sheet

■
■Operations On Objects
The appearance of the menu’s [Edit] → [Object] commands differ according to whether or not
something is selected in the sheet.

Table 4-5.

Select Object Menu [Edit] → [Object] Display

Other than object [Object]
[<Application name> Object]
Embedded object
Displays a cascade menu, and [Edit] and [Convert] are shown as
(before file format
submenus. The [Edit] command invokes the application, and the
conversion)
[Convert] command displays the [Convert] dialog box.
Embedded object
[Convert <Application name> Object]
(following file format
The [Convert] dialog box appears when this command is executed.
conversion)
[Package Object]
Displays a cascade menu, and [Activate Contents] and [Convert]
Linked object are shown as submenus. The [Activate Contents] command invokes
the application, and the [Convert] command displays the [Convert]
dialog box.

■
■Editing an Object
An object embedded in a sheet can invoke the application in the following ways:

Step Click the object and then execute the [Edit] → [Object] → [Edit] commands.

Step Double-click the object.

Step Click the <Open Source> button in the [Links] dialog displayed by executing the
[Edit] → [Links] commands (only in the case of linked objects).

■
■Changing the File Format of the Embedded Object
This is a function for changing the file format by specifying another application different from
the one in which the object was created originally.

− 87 −
Chapter 4. About Sheets

■
■Operations of Linked Objects
The menu’s [Edit] → [Links] commands are valid when a linked object is found in a sheet. The
[Links] dialog appears when these commands are executed.
The [Links] list box in the [Links] dialog shows the path name, etc., of files linked and defined
in the sheet. This dialog box allows the following operations to be performed:

•• Specification of the Update Method

The update method is selected by the option buttons <Automatic> and <Manual>.
When <Automatic> is selected, the linked object is automatically updated whenever the
link source file is changed.
When <Manual> is selected, the linked object is updated only when the <Update Now>
button in the [Links] dialog box is clicked.

•• Updating an Object
This makes the contents of the object in the sheet match the contents of the link source
file.

•• Opening an Object
It is possible to invoke the application in which the object was created and then edit the
link source object.
If the application is closed without saving the file after the object is edited, the contents
will differ from those of the link source file, and later changes to the link source file will
no longer be reflected. In order to match the contents with that of the link source file
again, click the <Update Now> button. To sever the relation to the link source file, click
the <Break Link> button.

•• Switching the Link Source File

When the <Change Source> button is clicked for a selected link, the [Change Source]
dialog box appears. This allows you to specify a new link source file for the link.
The display in the sheet is not switched until the <Update Now> button is clicked (even if
<Automatic> is selected as the update method).

•• Canceling the Link

Releases the selected link. The object remains embedded in the sheet. In the sheet, the
contour of the object changes from a broken line to a solid line.
When a link is released, the link is removed from the [Links] list box. Following this, the
menu’s [Edit] → [Links] commands will not become valid even if the object is selected.

Note When copying a Job containing sheets linked to another PC, etc., be sure also to
copy the link source.

− 88 −
 4.2 Applications of Sheet

4.2.4 Drawing Tools

RTC Editor has powerful graphic tools for drawing comprehensive and effective control
designs.

■
■Grouping RTC Parts
With the Group tool, combine several RTC Parts into a single, easy-to handle group.
Once grouped, you can keep the topological relationships among multiple RTC Parts.

Step 1 Select RTC Parts which you wish to combine.

Step 2 Choose the [Group] command from the [Draw] menu of Sheet Window or choose
the <Group> button from Drawing tool bar.

Note Control Parts and Container Part cannot be included in the group.

Note The following precaution should be observed for commands for grouped parts.
•• The drawing settings will affect all the grouped parts that can be subject to the
drawing settings.
An error is generated if the group does not contain at least one part that can ac-
cept a drawing setting.

■
■Ungrouping RTC Parts
Ungrouping is breaking a group into its component RTC Parts. You can select multiple groups
and ungroup together.

Step 1 Select one or more groups to ungroup, if required.

Step 2 Choose the [Ungroup] command from [Draw] menu of Sheet Window or choose
the <Ungroup> button from Drawing tool bar.

When a group is composed of multiple layers of groups, the ungroup operation disassembles
one layer at a time.

■
■Moving Back and Forth
Each RTC Part has its own place on the invisible Z-axis of the Sheet. Move Parts to the front
or to the back in multi-object Sheets. This axis is called the Z-axis.
[Forward] and [Backward] commands of [Draw] menu moves RTC Part along the Z-axis for
one notch. When two Parts are not adjacent in the Z-axis, it may appear these commands have
no immediate effect. [To Front] command of [Draw] menu moves RTC Part along the Z-axis
to the front, and [To Back] command to the back.

− 89 −
Chapter 4. About Sheets

■
■Rotating RTC Parts
You can rotate some RTC Parts. The command rotate by 90 degrees (clockwise or counter-
clockwise) around the center point of the rectangle surrounding the selected RTC Part.

Step 1 Select one or more RTC Parts to rotate.

Step 2 Choose [Rotate Right] or [Rotate Left] command from [Draw] menu of Sheet
Window. By [Rotate Right], Parts rotate clockwise, and by [Rotate Left],
counter-clockwise.

When not-rotatable Parts are in a group, Rotate commands will not work.

■
■Flipping RTC Parts
You can flip some RTC Parts, either vertically or horizontally.

Step 1 Select one or more RTC Parts to flip.

Step 2 Choose [Flip Vertical] or [Flip Horizontal] commands from [Draw] menu of Sheet
Window.

When not-rotatable Parts are in a group, Flip commands will not work.

Note By Rotate or Flip commands, RTC Parts may be placed over a Sheet’s boundary.
You should move them inside the boundary before printing a Sheet.

− 90 −
 4.2 Applications of Sheet

4.2.5 Gridlines
Gridlines are equally-distanced lines drawn horizontally and vertically across the Sheet. RTC
Parts are aligned to the gridlines when are moved or created.
To enable or disable Gridlines choose [Snap To Grid] command from [View] menu of Sheet
Window. If gridlines are enabled, a check mark appears in the menu.
When an RTC Part is created or moved while Snap To Grid is enabled, it moves so the left-
bottom corner of the surrounding rectangle of the Part is always on an intersection of the
gridlines. Note that other three corners of the Part many not be on the gridlines. When RTC
Editor is started, Snap To Grid is enabled by default.

Note When a Part is located or moved, the lower left corner of the rectangle enclosing the
Part is aligned to a gridline. Unless the length and height of the Part are multiples of
a gridline, the other three corners are not aligned to gridlines.

Note When RTC Editor is started, grid settings (visible/invisible, grid interval, and visible
interval) return to the defaults.

■
■Changing grid settings

Step 1 Select [View] and then execute the [Gridlines] command.

Step 2 The [Gridlines] dialog box will appear.

Step 3 To make settings effective in the dialog, click the <OK> button. The <Cancel> but-
ton is used to not change grids.

Note When visible interval of gridlines on the display is less than 5 dots, gridlines are not
shown, otherwise the display becomes too messy. In such a case, if you zoom in,
gridlines will appear.

Table 4-6. [Gridlines] dialog box

Contents
This checkbox has the same effect as [Snap To Grid] command of
Align to Grid
[View] menu
You can set the interval of the horizontal gridlines and vertical grid-
lines, respectively.
Actual Interval
Interval may range from 1 mm to 30 mm.
Default interval is 2 mm.
Show Gridlines Click this check box to show, gridlines
Visible Interval determines how the gridlines are shown on the Sheet,
and is specified as one out of how many gridlines are shown.
Visible Interval The number ranges from 1 to 30, with default number 5.
For example, when Actual Gridlines is 2 mm, and Visible Interval is
10 Gridlines, each gridline appears 20 mm apart on the Sheet.

− 91 −
Chapter 4. About Sheets

4.2.6 Zoom In and Out

By default, Sheet is displayed at the standard resolution. You can ZoomIn to a higher or
ZoomOut to a lower resolution if necessary. The zoom factor is displayed in the status bar of
the Sheet Window.
The zoom factor you choose is valid until you close the Sheet. When you reopen the Sheet, the
zoom size is at the default.

■
■Zoom In
You can zoom in on the display by a factor of 20% by clicking [Zoom In] command from
[View] menu of Sheet Window, or clicking <Zoom In> button. Keep selecting this command
up to 200%.

■
■Zoom Out
You can zoom out on the display by a factor of 20% by choosing [Zoom Out] command from
[View] menu of Sheet Window, or clicking <Zoom Out> button.
Keep selecting this command down to 20% of the default resolution.

■
■Zoom Dialog Box
You can invoke [Zoom] dialog box by clicking [Zoom] command from [View] menu of Sheet
Window, or clicking <Zoom> button.
From [Zoom] dialog box, you can choose the zoom size as 30%, 50%, 70%, 100% or 200%, or
you can type in any zoom size between 20 and 200 in the [Size] text box.

− 92 −
 4.3 Sheet Editing Modes

4.3 Sheet Editing Modes

Sheet have several editing modes.

[Edit] [Class View] [Edit]

Sheet Editing Mode Class View Editing Mode

[Edit] [Template] [Edit] [Edit] [Edit Custom View]

Template Editing Mode Custom View Editing Mode

Figure 4-3.

•• The current editing mode remains valid until you choose another mode or close the Sheet.

•• In the caption bar, the name of the editing mode is displayed along with the Sheet file
name.

4.3.1 View Parts

You can assign new views to Control Parts by setting Class View and Custom View in addition
to the default view configured in advance.

Class View is set for individual types of Parts on a Job basis. For example, if Class View is set
for a single AI Part on a Sheet, all the AI Parts contained in the Job are displayed in that view.
Class View is useful when the market or the customer requires special appearances of specific
types of control elements.

Custom View is set for individual Parts. For example, if Custom View is set for an AI Part on
a Sheet, the view is assigned only to that Part. It does not affect the display of other AI Parts.
In Custom View, you can improve the visibility of Parts by assigning Pictures representing
actual pieces of equipment.

− 93 −
Chapter 4. About Sheets

■
■Which View To Show
You can assign Custom view to Parts even if Class views are already assigned.
The order of priority of view is shown below.

Default View < Class View < Custom View

•• Show Custom View

You can see or hide Custom view by choosing [Show Custom View] command from
[View] menu of Sheet window. [Show Custom View] is enable until you close the Sheet.
When you reopen the Sheet, Custom Views are not shown.

•• Show Class View

Once Class view is assigned, you cannot hide it. You may clear the Class View.

•• Class View And Custom View

When both Class View and Custom View are assigned, the appearance of the Part is de-
termined as shown in the following table.

Table 4-7. When [Show Custom View] is chosen

Class View Custom View Appearance

Not Assigned Default View
Not Assigned
Assigned Custom View
Not Assigned Class View
Assigned
Assigned Custom View

Table 4-8. When [Show Custom View] is NOT chosen

Class View Custom View Appearance

Not Assigned
Not Assigned Default View
Assigned
Not Assigned
Assigned Class View
Assigned

Note Neither Class View nor Custom View can be assigned to Picture Parts or grouped
Parts.

Note Only Picture Parts can be used in Class View and Custom View Editing. In the View
editing mode, buttons other than those for Picture Parts are invalid.
In the editing mode, an error message is displayed if an attempt is made to paste
something from the Clipboard that contains other items than Picture Parts.

− 94 −
 4.3 Sheet Editing Modes

4.3.2 Custom View

■
■Editing Custom View
You can create or edit Custom Views as follows:

Step 1 Select a Part to which you wish to assign Custom View.

Step 2 Choose [Edit Custom View] from [Edit] menu of Sheet Window.
The caption bar of the Sheet Window shows “Editing Custom View” along with the
Sheet file name.

Step 3 A center mark appears at the center of the Part. You can place Picture Parts around
the center mark.

Step 4 While editing Custom View, rectangle surrounding the Custom View is visible.
If you place another Picture Part outside this surrounding rectangle, the rectangle
will be enlarged to enclose the newly added Part.

Step 5 To exit Custom View Edit mode, choose [Edit Custom View] command from
[Edit] menu.
Custom View is saved when the Sheet itself is saved.

Step 6 To delete the Custom View, change to Edit Custom View mode and delete all
Picture Parts.

− 95 −
Chapter 4. About Sheets

4.3.3 Class View

Class View is created, saved and managed for each Job.

■
■Editing Class View
To create new Class View or edit existing Class View:

Step 1 Select a Part which belongs to the Class to which you wish to assign Class View.
Choose [Class View] → [Edit] command from [Edit] menu of Sheet Window.

Step 2 The caption bar of the Sheet Window shows “Editing Class View” along with the
Sheet file name.

Step 3 A center mark appears at the center of the Part. You can place Picture Parts around
the center mark.

Step 4 While editing Class View, rectangle surrounding the Class View is visible. Placing
another Picture Part outside this surrounding rectangle enlarges the rectangle to
enclose the newly added Part.

Step 5 To finish editing Class View, choose [Class View] → [Edit] command from [Edit]
menu again.

Step 6 Once you edit the Class View, all Parts of the same class within the Job are shown
under the new view.

■
■Save Class View
Class View is saved as a file. This file is called Class View File. To save the Class View File:

Step 1 Choose [Class View] → [Save] command from [Edit] menu of Sheet Window. The
Class View as shown will be saved in the currently- open Class View File.

Step 2 If Class View File has not yet saved, following operations cause a message to appear
to prompt you to save:
•• Exiting Class View Edit mode
•• Exiting the Job
When the first attempt to save the file by overwriting is made, and there is no file to be over-
written, the [Save As] dialog appears.

− 96 −
 4.3 Sheet Editing Modes

■
■Save Class View File As
You can save Class View with any file name. Class View File has extension .PIC. If Class View
File is not specified, the Save command invokes [Save As] dialog box.

Step 1 Select [Class View] → [Save As] command from [Edit] menu of Sheet Window.

Step 2 Enter file name in the File Name box of the [Save As] dialog box. By default, Job
Directory is shown in the Directory box. The File name is the same as Job name,
with extension .PIC.

Step 3 Click the <Save> button from the dialog box and save the Class View in the speci-
fied file. From then, the Class View File is opened whenever a Job is opened, until
another File is specified.

■
■Loading A Class View File
When a Job is opened, the Class View File saved last is loaded. When the specified Class View
File cannot be loaded, the Template View is shown.
Another Class View File can be loaded and set by executing the [Edit] → [Class View] → [Read]
commands.
Once a Class View File has been specified and loaded, this file remains the Class View File of
the Job until another file is loaded or it is saved in a separate file.

Note The Class View for all Parts in all Parts Libraries is stored in a single Class View File.
There is no separate file corresponding to each Part.
The RTC Editor selectively loads only the necessary parts of the Class View File. For
example, for a Job that does not use RVinfo, it is not necessary to use a Class View
File that contains the view definitions for RVinfo Parts.
Accordingly, it is possible to prepare files that define the Class View for all the Parts
and use these files for several jobs.

■ Clear Class View

■To
You can clear Class View by selecting [Class View] → [Clear] command from [Edit] menu.
Once you clear the Class View, you cannot undo it. If you erroneously select [Clear] com-
mand, do not execute [Save] command, and read Class View File to restore what was cleared.

− 97 −
Chapter 4. About Sheets

4.3.4 Template Edit Mode

Template is the Sheet background, and the Sheet becomes an overlay. On the Template, place
Picture Parts to create common formats or insert the Company logo, and share it among mul-
tiple Sheets. Each Sheet can have its own Template or share it with other Sheets.

■
■Editing Templates
To Create a new Template, or to edit an existing Template:

Step 1 Open a Sheet and Choose [Template] → [Edit] command from [Edit] menu of Sheet
Window. The caption bar of the Sheet Window shows “Editing Template” along
with the Sheet file name.

Step 2 During Edit Template mode, Parts in the Template are shown, while Parts in the
Sheet are not. You can place Picture Parts on the Template.

Step 3 During Edit Sheet mode, both Parts on the Sheet and Parts on the Template are
shown. However, you cannot select or operate Parts on the Template. Thus, ele-
ments in the Template are safe from erroneous operations in Edit Sheet mode.

Step 4 Choose [Template] → [Edit] command again to exit Edit Template Mode.

■
■Clear Templates
While in Edit Template mode, choose [Template] → [Clear] command from [Edit] menu of
Sheet Window. This operation can be undo.

■
■Reuse Templates
Template will be saved along with the attached Sheet. To reuse the Template, save the Template
as a named file.

Step 1 Choose [Template] → [Edit] command from [Edit] menu of Sheet Window and
enter Edit Template Mode.

Step 2 Choose [Template] → [Save As] command from [Edit] menu of Sheet Window.
When the file name has not been specified yet, [Save As] dialog box appears.

Step 3 Type in file name in [Save As] dialog box. Default directory is TPL under Job di-
rectory. Default file name is “custom?.tpl”, where ? is determined by RTC Editor.
When the specified file already exists, a message appears to confirm if the file can
be over-written.

− 98 −
 4.3 Sheet Editing Modes

When you reuse a Template, you read the Template saved earlier.

Step 1 Open a Sheet from which you wish to read Template file.

Step 2 Choose [Template] → [Edit] command from [Edit] menu of Sheet Window and
enter Edit Template Mode.

Step 3 Choose [Template] → [Read] command from [Edit] menu of Sheet Window.
If you have already read a Template, a message appears to confirm whether you
wish to discard the current Template.

Step 4 [Open] dialog box appears. From this dialog box specify the Template file.

Note Only Picture Parts can be used to edit templates. In the View editing mode, buttons
other than those for Picture Parts are invalid.
In the editing mode, an error message is displayed if an attempt is made to paste
something from the clipboard that contains items other than Picture Parts.

− 99 −
Chapter 4. About Sheets

MEMO

− 100 −
 5.1 Picture Parts

Chapter 5. RTC Parts

RTC Parts can be chosen from the RTC Tool Bars.

■
■RTC Tool Bars
Table below shows the following RTC Tool Bars.

Table 5-1. RTC Tool Bars

Tool Bars Function

Picture PARTS To draw pictures
Control PARTS
To design and implement database using Point Parts
(Point)
Control PARTS
To design and implement a database using blocks
(Block)
Rvinfo PARTS Used for coding-less programming

Each RTC Tool Bar is described in detail below.

Restriction In SS in which some specific graphic cards (such as Riva TNT2) are used, spectrums
of graphics may be generated during the creation of Parts. This is merely an ap-
pearance problem and does not affect the data being engineered. These spec-
trums disappear when the Sheet is reopened, scrolled, etc.

5.1 Picture Parts

Picture Parts have drawing capabilities such as text, lines, rectangles and other typical draw-
ing tools.

■
■Display Picture Parts tool bar

Step 1 Choose [RTC Tool Bars] from [View] menu. The [RTC Tool Bars] dialog box
appears.

Step 2 Choose Picture Parts from the list box in the [RTC Tool Bars] dialog box and click
the <Visible> button.

Step 3 Click the <Close> button and close the dialog box.

− 101 −
Chapter 5. RTC Parts

■
■Parts contained in the Picture PARTS tool bar
The Picture PARTS tool bar contains the following Parts:
•• Text and Title
•• Line and Polyline
•• Arrow and Double Headed Arrow
•• Rectangle and Round-rectangle
•• Polygon
•• Oval and Arc
•• Bitmap
•• Sheet Number, Sheet Title, and Version

■
■Picture Parts Tool Bar
The Figure below shows the Picture Parts Tool Bar:

Figure 5-1.

Run the mouse over each button, and a button name appears beside a mouse pointer, with a
description displayed in the status bar. The button name and description for each Picture Part
is shown in the following table:

Table 5-2. Picture Parts tool bar contains the following Parts

Button Name Description

Select Select RTC Parts on the Sheet
Reshape Change shape of the selected Parts
Rectangle Create Rectangle Parts
Polyline Create Polyline Parts
Line Create Line Parts
Arrow Create Arrow Parts
Double Headed Arrow Create Double Headed Arrow Parts
Title Create Title Parts
Bitmap Create Bitmap Parts
Oval Create Oval Parts
Polygon Create Polygon Parts
Arc Create Arc Parts
Text Create Text Parts
Round-rectangle Create Round-rectangle Parts
Sheet Number Create Sheet Number Parts
Sheet Title Create Sheet Title Parts
Version Create Version Parts

− 102 −
 5.1 Picture Parts

■
■Guiding Messages For Picture Parts Operations
When you choose a button from the Picture Parts tool bar, or select one or more Picture Parts
on the Sheet, a guidance message appears in the status bar, to help your work.

Table 5-3. Guiding Messages For Picture Parts Operations

Operation Message in the status bar

Click to select a RTC Part, or drag to select multiple
Choose Select button
RTC Parts
Choose one or more Picture Parts on the
Drag to move or resize
Sheet
Choose buttons such as Rectangle, Bitmap,
Click at the starting point, and drag to the end point
Oval, Arc, Text, Round-rectangle
Choose buttons such as Line, Polyline, Arrow,
Left-click at the starting point
Double Headed Arrow and Sheet Title
Choose Line button and click at the starting
Click at the end point
point on the Sheet
Choose button such as Polyline, Arrow,
Double Headed Arrow and click at the start- Click at the joints, double-click at the end point
ing point on the Sheet

■
■Editing Picture Parts
The edit functions applicable to Picture Parts are shown in the following table.

Table 5-4. Editing Picture Parts

Drawing Style
Re-Shape
Items Move Resize Line/Text Fill
(Meaning)
Color LineWidth Pattern Color Pattern
Text ✓ ✓ – ✓ – – ✓ –
Title ✓ ✓ Change text ✓ – – ✓ –
Line ✓ ✓ Add joints ✓ ✓ ✓ – –
Polyline ✓ ✓ Move/add joints ✓ ✓ ✓ – –
Arrow ✓ ✓ Move/add joints ✓ ✓ ✓ – –
Double Headed Arrow ✓ ✓ Move/add joints ✓ ✓ ✓ – –
Rectangle ✓ ✓ – ✓ ✓ ✓ ✓ ✓
Round-rectangle ✓ ✓ Change round-ness ✓ ✓ ✓ ✓ ✓
Oval ✓ ✓ – ✓ ✓ ✓ ✓ ✓
Arc ✓ ✓ – ✓ ✓ ✓ ✓ ✓
Polygon ✓ ✓ Move/add joints ✓ ✓ ✓ ✓ ✓
Bitmap ✓ ✓ – – – – – –
Sheet Number ✓ ✓ – ✓ – – – –
Sheet Title ✓ ✓ – ✓ – – – –
Version ✓ ✓ – ✓ – – – –

− 103 −
Chapter 5. RTC Parts

5.1.1 How to Use Picture Parts

The following sections describes the behavior and functions of Picture Parts.

5.1.1.1 Text Parts

Picture Parts contain two types of character-based Parts; Text Parts and Title Parts.
When you resize Text Parts, the size of the text area is resized while the size of each character
stays the same, and the word content per line changes.

■
■Add Text Parts to a Sheet

Step 1 Click the <Text> button in the Picture Parts tool bar.

Step 2 Specify the position and size of the Text Part by dragging it on the Sheet.
The upper edge and the right and left edges of the area specified by dragging be-
come the upper edge and the right and left edges of the Text Part. The lower edge
is expanded as text is entered. At this point in time, therefore, it is not necessary to
specify its exact position.

Step 3 A character box and a caret are displayed, allowing you to type in text. Type in text.
The text is left-justified, and you can start a new line by pressing the [Enter] key. In
addition, when you reach the end of the last line, the next line automatically begins.

Step 4 To finish typing in text, click outside the character box. The lower edge of the text
area is adjusted to the status of the text typed in by this time.

■
■Edit Text Part

Step 1 Double-click a Text Part on the Sheet.

Step 2 The caret appears at the position where you double-clicked, allowing you to edit
text. By moving the caret, you can insert and delete characters into and from any
positions in the character string.
In this status, you can select consecutive character strings by dragging the mouse.
From the menu displayed by a right-click, you can [Cut], [Copy], [Paste], or
[Delete] the selected character strings.

Step 3 To finish editing text, click outside the character box.

− 104 −
 5.1 Picture Parts

■ Font
■Set

Step 1 Select Text Part on the Sheet.

Step 2 Choose the [Font] command from the [View] menu of Sheet Window.
Font dialog box appears.

Step 3 Choose a font and a size from list boxes in the [Font] dialog box.
If a larger font size is chosen and the whole text cannot be confined in the initial
text area, the text area extends downward.

Step 4 Click outside Text Part to finish editing.

■
■Resize Text Part
When resizing Text Part, the size of the text area changes, but font size is not affected.

■ Drawing Mode
■Set
Set the color of the text by choosing a Color from the [Drawing Mode] dialog box where the
<Line/Text> button is chosen. Set background color by choosing a Color from the [Drawing
Mode] dialog box where the <Fill> button is chosen.

Note Some Text Parts may be outside the Sheet boundary after enlarging Text Parts or
choosing a larger font size. You should move these Parts inside the Sheet boundary
before printing the sheet.

− 105 −
Chapter 5. RTC Parts

5.1.1.2 Title Parts

Title Parts display characters on the Sheet. When resizing a Title Part, the text area size and
the size of each character, change. It is suitable when treating text as a picture.

■
■Create a Title Part

Step 1 Click the <Title> button from Picture Parts tool bar.

Step 2 Click on the Sheet. The mouse click location is the top left-hand corner of the text
area. The caret appears at the head within the text area.

Step 3 Type in any characters. When you reach the end of a line and type in more text, the
box extends to the right, automatically.

■
■Edit Title Part

Step 1 Choose a Title Part on the Sheet.

Step 2 From the Picture Parts tool bar, click the <Reshape> button.

Step 3 Click inside the Title Part, and the caret appears at the top. In this state, you can add
a character string to the top.

Step 4 After the cursor has changed to the caret, you can insert and delete characters into
and from any positions in the character string by moving the mouse. You can also
select multiple consecutive characters by dragging the mouse.

Step 5 To finish editing the Title Part, click outside the character box.

■ Font for Title Part

■Set
Choose a Font and a Size from the [Font] dialog box, just as with Text Parts.
When enlarged, Title Part text extends right and bottom, with the top left-hand corner of the
text area fixed. When reduced, its links in the opposite directions.

■
■Resize Title Part
When you resize a Title Part, the height and width of the font changes, and the proportion of
height to width does not necessarily follow that of the standard font.
Restore the correct text proportions using the Font dialog box. Select a Title Part to invoke
Font dialog box. In the Size list box of [Font] dialog box, the proportionate text size is calcu-
lated from the current text height. If you choose <OK> button, the text width will be restored
to the standard proportions.

■ Drawing Mode
■Set
Same as for Text Part.

Note For Title Parts, Parts are located so that the click location is the top left-hand corner
(bottom left-hand corner for other parts).

Note Title Parts can be consecutively created by simultaneously holding down the [Shift] key.

− 106 −
 5.1 Picture Parts

5.1.1.3 Line Parts

Line Part draw a line.

■
■Create a Line Part

Step 1 Click the <Line> button from Picture Parts tool bar.

Step 2 Click at the start point, then click at the end point on the Sheet. Keep moving, and
the screen scrolls until you reach the Sheet border.

■
■Reshape a Line Part

Step 1 Choose a Line Part on the Sheet.

Step 2 Click the <Reshape> button from Picture Parts tool bar.

Step 3 Move the mouse anywhere on the Line Part, and the cursor becomes a Cross-beam.

Step 4 Drag the mouse and you can add a joint.

■
■Resize a Line Part

Step 1 Choose a Line Part on the Sheet. Handles appear at each end of the Line.

Step 2 Move the mouse on a handle, and the cursor becomes an arrow.

Step 3 Drag the mouse and the line is resized. Resizing operation affects the length, but
not the width, of the line.

■ Drawing Mode
■Set
You can choose Color and Line Size for the Line Part from [Drawing Mode] dialog box. Fill
options are not applicable to Line Part.

Restriction Even if the Fill option is invalid in the [Drawing Mode] dialog, the button does not
become inoperative.

− 107 −
Chapter 5. RTC Parts

5.1.1.4 Polyline Parts

Polyline draws a set of lines which are connected at their joints.

■
■Create a Polyline Part

Step 1 Click the <Polyline> button from Picture Parts tool bar.

Step 2 Click at the starting point. Move the mouse to another location, and click. A new
joint is added whenever the mouse is clicked. Cancel the last joint by clicking the
right mouse button.

Step 3 Keep moving the mouse, and the screen scrolls until you reach the Sheet border. If
you click out of the Sheet, joint stays on the Sheet border.

Step 4 Double click, to create the Polyline Part is created.

■
■Reshape a Polyline Part

Step 1 Choose a Polyline Part on the Sheet.

Step 2 Click the <Reshape> button from the Picture Parts tool bar. The joints are indicated
by handles.

Step 3 Move the mouse to any point on the lines, and the cursor becomes a Crossbeam.
Drag the mouse to add a joint. Move the mouse over the handles, and the cursor
becomes a cross beam. Drag the mouse to move the joint.

■
■Resize a Polyline Part
Same as for Line Part.

■ Drawing Mode
■Set
Same as for Line Part.

5.1.1.5 Arrow Parts and Double Headed Arrow Parts

Arrow Part draws an arrow, and Double Headed Arrow part draws a double arrow.

■
■Create an Arrow Part or a Double Headed Arrow Part
Same as for Polyline Part.

■
■Reshape an Arrow Part or a Double Headed Arrow Part
Same as for Polyline Part.

■ Drawing Mode
■Set
Same as for Line Part.

− 108 −
 5.1 Picture Parts

5.1.1.6 Rectangle Parts

Rectangle Part draws rectangles.

■
■Create a Rectangle Part

Step 1 Click the <Rectangle> button from Picture Parts tool bar.

Step 2 Click at one corner of the rectangle and drag to the opposite corner.
Press <Shift> key while dragging to draw a square.
If you drag to out of the Sheet, the opposite corner stay on the Sheet border.

■
■Resize a Rectangle Part

Step 1 Choose a Rectangle Part on the Sheet. Handles appear along the Rectangle.

Step 2 Move the mouse on one of these handles, and the cursor becomes an arrow.

Step 3 Drag the mouse to resize the rectangle. Note that you cannot resize a rectangle to a
square just by pressing <Shift> key while dragging the handles.

■ Drawing Mode
■Set
From Drawing Mode dialog box, choose the <Line/Text> button, then choose a Color and
a Line Size for the border. From Drawing Mode dialog box, choose the <Fill> button, then
choose Color and Pattern inside the Rectangle Part.

5.1.1.7 Round-rectangle Parts

Round-rectangle Part draws rectangles with rounded corners. You can change the degree of
roundness of the corners.

■
■Create a Round-rectangle Part

Step 1 Click the <Round-rectangle> button from Picture Parts tool bar.

Step 2 Click at one corner of the rectangle and drag to the opposite corner.
Press <Shift> key while dragging draw a round-square.
If you drag to out of the Sheet, the opposite corner stay on the Sheet border.

■
■Reshape a Round-rectangle Part

Step 1 Select a Round-rectangle Part, and click the <Reshape> button from Picture Parts
tool bar. Handles appear inside the top left-hand corner of the Roundrectangle
Part.

Step 2 Move the mouse over the handle, and the cursor becomes a cross-beam.

Step 3 Drag the mouse, and the roundness of the Round-rectangle Part changes.

− 109 −
Chapter 5. RTC Parts

■
■Resize a Rectangle Part
Same as for Rectangle Part.

■ Drawing Mode
■Set
Same as for Rectangle Part.

5.1.1.8 Oval Parts

Oval Part draws ovals.

■
■Create an Oval Part

Step 1 Click the <Oval> button from Picture Parts tool bar.

Step 2 Click at one corner of the rectangle surrounding the <Oval> Part and drag to the
opposite corner.
Press <Shift> key while dragging to draw a circle.
If you drag to out of the Sheet, the opposite corner stay on the Sheet border.

■ Resize an Oval Part

■To

Step 1 Choose an Oval Part on the Sheet.

Handles appear along the rectangle surrounding the Oval Part.

Step 2 Move the mouse over one of these handles, and the cursor becomes an arrow.

Step 3 Drag the mouse and the oval is resized.

Note that you cannot reshape an oval to a circle just by pressing <Shift> key while
dragging the handles.

■ Drawing Mode
■Set
Same as for Rectangle Part.

5.1.1.9 Arc Parts

Arc Part draws quarter ovals.

■
■Create an Arc Part

Step 1 Click the <Arc> button from Picture Parts tool bar.

Step 2 Click at one corner of the rectangle surrounding the Arc Part and drag to the op-
posite corner.
The arc is the top-left quarter of the oval adjacent to the surrounding rectangle.
Press <Shift> key while dragging to draw a quarter circle.

− 110 −
 5.1 Picture Parts

■
■Resize an Arc Part

Step 1 Choose an Arc Part on the Sheet. Handles appear along the rectangle surrounding
the Arc Part.

Step 2 Move the mouse over one of these handles, and the cursor becomes an arrow.

Step 3 Drag the mouse and the arc is resized.

Note that you cannot reshape an arc to a quarter circle just by pressing <Shift> key
while dragging the handles.

■ Drawing Mode
■Set
Same as for Rectangle Part.

5.1.1.10 Polygon Parts

Polygon Part draws a shape bordered by a set of lines.

■
■Create a Polygon Part

Step 1 Click the <Polygon> button from Picture Parts tool bar.

Step 2 Click at the starting point. Move the mouse, and click. A new joint is added when-
ever the mouse is clicked. You can cancel the last joint by clicking the right button
of the mouse.

Step 3 Double click, Polygon Part. The area bordered by the lines becomes a polygon.

■
■Reshape a Polygon Part

Step 1 Choose a Polygon Part on the Sheet.

Step 2 Click the <Reshape> button from Picture Parts tool bar.
Joints are indicated by handles ().

Step 3 Move the mouse anywhere on the lines, and the cursor becomes a crossbeam.
Drag the mouse and you can add a joint.

Step 4 Move the mouse over the handles, and the cursor becomes a cross-beam.
Drag the mouse to move the joint.

■
■Resize Polygon Part
Same as for Rectangle Part.

■ Drawing Mode
■Set
Same as for Rectangle Part.

− 111 −
Chapter 5. RTC Parts

5.1.1.11 Bitmap Parts

Bitmap Part is used to paste bitmap.

■
■Create a Bitmap Part

Step 1 Click the <Bitmap> button from Picture Parts tool bar. The <Bitmap> button is
valid only when a bitmap is stored in the clipboard. Otherwise, the <Bitmap> but-
ton is disabled.

Step 2 Click at one corner and drag to the opposite corner. Keep dragging, and the screen
scrolls until you reach the Sheet border. Release the mouse button, and the bitmap
in the clipboard appears inside the Bitmap Part. The picture in the clipboard is
enlarged or reduced to the size of the Bitmap Part.

■ Resize a Bitmap Part

■To
Same as for Rectangle Part.

Note You cannot edit Bitmap Part.

5.1.1.12 Sheet Number Parts

Sheet Number Part shows the Sheet Number which is set in the [Sheet Information] dialog
box.

■
■Create a Sheet Number Part

Step 1 Click the <Sheet Number> button from the Picture Parts tool bar.

Step 2 Click on the Sheet.

■
■Font Setting for Sheet Number Parts

Step 1 Select the Sheet Number Parts on the Sheet.

Step 2 Select [View] → [Font] from the menu. The [Font] dialog box appears.

Step 3 Select a font. If a large font size is chosen and the whole text cannot be accom-
modated in the Sheet Number Part area, the text area extends downward while the
width remains the same.

■
■Resizing Sheet Number Parts
When resizing Sheet Number Parts, the text area changes, but the font size is not affected.
It is not possible to reduce the size to the extent that the character strings can no longer be
displayed.

− 112 −
 5.1 Picture Parts

■
■Setting the Drawing Mode for Sheet Number Parts
The color of the text can be changed by using the <Line/Text> button in the [Drawing Mode]
dialog box. The [Fill] option is inoperative.

Note For Sheet Number Parts, Parts are located so that the click location is the top left-
hand corner (bottom left-hand corner for other parts).

5.1.1.13 Sheet Title Parts

Sheet Title Part shows the Sheet Title which is set in the [Sheet Information] dialog box.
Behavior of Sheet Title Parts is the same as for Sheet Number Parts.

■
■Font Setting for Sheet Title Parts

Step 1 Select the Sheet Title Part on the Sheet.

Step 2 Select [View] → [Font] from the menu. The [Font] dialog box appears.

Step 3 Select a font. If a large font size is chosen and the whole text cannot be accommo-
dated in the Sheet Title Part area, the text area extends downward while the width
remains the same.

■
■Resizing Sheet Title Parts
When resizing Sheet Title Parts, the text area changes, but the font size is not affected.
It is not possible to reduce the size to the extent that the character strings can no longer be
displayed.

■
■Setting the Drawing Mode for Sheet Title Parts
The color of the text can be changed by using the <Line/Text> button in the [Drawing Mode]
dialog box. The [Fill] option is inoperative.

5.1.1.14 Version Parts

Version Parts show the Version information which is set in the [Sheet Information] dialog
box. Behavior of Version Part is the same as for Sheet Title Parts.

− 113 −
Chapter 5. RTC Parts

5.2 Control Parts

Control Parts are used to design control strategies and create the point database.
Control Parts have the following features:

•• Control Parts are independent of the controller types. Their output can be used in
Harmonas-DEO Systems.

•• “Logic Component Parts” provide a common logical access step and also offer an ac-
cess method to the control bodies (Control Points) on the PC and the physical control-
ler through the “Tag Name”. However, Logic Tag Names only exist for Point Parts, Logic
Component Parts and CL Parts.

5.2.1 Control Parts Tool Bar

■
■Display Control Parts tool bar

Step 1 Choose the [RTC Tool Bars] from the [View] menu of Sheet Window. RTC Tool
Bars dialog box appears.

Step 2 Choose Control Parts(Point or Block) from the list box in the [RTC Tool Bars]
dialog box and click the <Visible> button.

Step 3 Click the <Close> button.

■
■Control Parts Tool Bar Types
The Control Parts Tool Bar consists of the following two Parts Tool Bars:

•• “Control PARTS (Point)”

Provides Parts for configuration by Point Parts.

•• “Control PARTS (Block)”

Provides Parts for configuration by Point Parts.

− 114 −
 5.2 Control Parts

■
■Control Parts Tool Bar
The figure below shows the Control Parts (Point) Tool Bar:

Figure 5-2.

The figure below shows the Control Parts (Block) Tool Bar:

Figure 5-3.
Move the mouse over a button, the button name appears beside the mouse pointer, with a de-
scription in the status bar. The button name and description for each Control Part are shown
in the following table. The order of the table corresponds in order of the button of Figures.

− 115 −
Chapter 5. RTC Parts

Table 5-5. Button Name of Control Parts (Point)

Button Name Description

Select Select RTC Parts on the Sheet
Reshape Change shape of the selected Parts
Container Create Container Parts
Link Connect Parameter/Point Link
Divergence Parts Create Divergence Parts
Job Part (OUT) Create Job Part (OUT)
Job Part (IN) Create Job Part (IN)
Intersheet Parts (Output) Create Intersheet Parts (Output)
Intersheet Parts (Input) Create Intersheet Parts (Input)
Intrasheet Parts (Output) Create Intrasheet Parts (Output)
Intrasheet Parts (Input) Create Intrasheet Parts (Input)
AI Create Analog Input Parts
AO Create Analog Output Parts
DI Create Digital Input Parts
DO Create Digital Output Parts
VALIN Create VALIN Parts
VALOUT Create VALOUT Parts
DIGCOMP Create Digital Composite Parts
REGPV Create Regulatory PV Parts
REGCTL Create Regulatory Control Parts
LOGIC Create Logic Parts
FLAG Create Flag Parts
NUMERIC Create Numeric Parts
NMARRAY [R411 or later] Create Numeric Array Parts
STRING [R411 or later] Create String Parts
DATETIME [R411 or later] Create Datetime Parts
TIMER Create Timer Parts
PROCMOD Create Process Module Parts
CL Create CL Parts
ALGO(LOG) Create ALGO(LOG) Parts
NUMERIC(LOG) Create NUMERIC(LOG) Parts
FLAG(LOG) Create FLAG(LOG) Parts
CONNECT(LOG) Create CONNECT(LOG) Parts
GATEWAY(LOG) Create GATEWAY(LOG) Parts

− 116 −
 5.2 Control Parts

Table 5-6. Button Name of Control Parts (Block)

Button Name Description

Select Select RTC Parts on the Sheet
Reshape Change shape of the selected Parts
Container Create Container Parts
Link Connect Parameter/Point Link
Thick Link Connect Parameter/Point Link with Thick Link
Divergence Parts Create Divergence Parts
Job Part (OUT) Create Job Part (OUT)
Job Part (IN) Create Job Part (IN)
Intersheet Parts (Output) Create Intersheet Parts (Output)
Intersheet Parts (Input) Create Intersheet Parts (Input)
Intrasheet Parts (Output) Create Intrasheet Parts (Output)
Intrasheet Parts (Input) Create Intrasheet Parts (Input)
Frame Create Frame Parts
BOX Parameter Create BOX Parameter Parts
ADD Create Addition Block Parts
SUB Create Subtraction Block Parts
MUL Create Multiplication Block Parts
DIV Create Division Block Parts
MOD Create Module Block Parts
SUM Create 4-Point Addition Block Parts
DADD Create Digital Addition Block Parts
ABS Create Absolute Value Block Parts
SQR Create Square Block Parts
SQRT Create Square Root Block Parts
LN Create Natural Logarithm Block Parts
LOG Create Common Logarithm Block Parts
EXP Create Exponent eX Block Parts
EXPT Create Exponent Xy Block Parts
SIN Create Sine Block Parts
COS Create Cosine Block Parts
TAN Create Tangent Block Parts
ATAN Create Anti-tangent Block Parts
TRUNC Create Truncate Block Parts
ROUND Create Round Off Block Parts
MAX Create Maximum Value Block Parts
MIN Create Minimum Value Block Parts
AVD Create Average Value Block Parts
HSE Create High Selector Block Parts
LSE Create Low Selector Block Parts
MID3 Create Middle-of-three Block Parts
SW Create Switch Block Parts

− 117 −
Chapter 5. RTC Parts

Button Name Description

SFT Create Soft Switch Block Parts
ALSW Create Alternate Switch Block Parts
HLM Create High Limit Block Parts
LLM Create Low Limit Block Parts
DRL Create Deviation Rate Limiter Block Parts
HMS Create High Monitor Block Parts
LMS Create Low Monitor Block Parts
DRM Create Deviation Rate Monitor Block Parts
DMS Create Deviation Monitor Block Parts
NUMCHK Create Normal Detection Block Parts
BADCHK Create Abnormality Detection Block Parts
INFCHK Create Infinity Detection Block Parts
QLTCHK Create Change Detection 1 Block Parts
CHGCHK Create Change Detection 2 Block Parts
PTE Create EU Value Conversion Block Parts
ETP Create % Conversion Block Parts
FUNC Create Function Conversion Block Parts
AND Create Logical Product Block Parts
OR Create Logical Sum Block Parts
NOT Create Reversal Block Parts
NAND Create Inverted AND Block Parts
NOR Create Inverted OR Block Parts
QOR Create Exclusive OR Block Parts
QOR2 Create Qualified OR With 2 Inputs ON Block Parts
SR Create Set Block Parts
RS Create Reset Block Parts
EQ Create Compare Equal With Deadband Block Parts
NE Create Compare Not Equal With Deadband Block Parts
GT Create Compare Greater Than With Deadband Block Parts
Create Compare Greater Than or Equal To With Deadband
GE
Block Parts
LT Create Compare Less Than With Deadband Block Parts
Create Compare Less Than or Equal To With Deadband
LE
Block Parts
FIXPLS Create Fixed-length Pulse Block Parts
MAXPLS Create Pulse With Maximum Time Limit Block Parts
MINPLS Create Pulse With Minimum Time Limit Block Parts
CYCPLS Create Timer Block Parts
WDT Create Watchdog Timer Block Parts
DELAY Create Delay Block Parts
ONDLY Create On Delay Block Parts
OFFDLY Create Off Delay Block Parts

− 118 −
 5.2 Control Parts

Button Name Description

UCNT Create Up-counter Block Parts
DCNT Create Down-counter Block Parts
AAV Create Analog Integration Block Parts
PAV Create Pulse Addition Block Parts
PID Create PID Calculation Block Parts
PRO Create Comparison Block Parts
INT Create Integration Block Parts
DIF Create Differentiation Block Parts
LDLG Create Lead Lag Block Parts
DED Create Deadtime Block Parts
TF Create Filtering Time Block Parts
RMP Create Ramp Block Parts
MAV Create Moving-average Block Parts
ANMA Create Analog Memory Block Parts
GW Create Gateway Block Parts
CONV Create Data Conversion Block Parts
SG Create Signal Block Parts
FL Create Flag Signal Block Parts
DLTPV Create Acceleration PV Block Parts
TIMFL Create One-shot FL Block Parts
ANDIN4 Create 4-input AND Operation Block Parts
ORIN4 Create 4-input OR Operation Block Parts
PSQRT Create % Square Block Parts
REDTAG Create Read TagBlock Parts

− 119 −
Chapter 5. RTC Parts

■
■Guidance Messages For Control Part Operations
Choose a button from the Control Parts tool bar, or choose one or more Control Parts on the
Sheet, and guidance messages appear in the status bar to help your work.

Table 5-7. Appear in the status bar of Control Parts (Point)

Operation Message in the status bar

Click to select a RTC Part, or drag to
Choose Select button
select multiple RTC Parts
Select Container Parts on the Sheet Drag to move or resize
Select Point Parts on the Sheet Drag to move
Click a port on the Sheet Drag to move
Click the left mouse button on the
Choose Container button
sheet
Click the left mouse button on the
Choose Link button
start port
Click at the joints, double-click at the
Choose Link button, and select a starting Port
end Port
Choose buttons such as Divergence Parts, Job Parts(Output),
Job Parts(Input), Intersheet Parts(Output), Intersheet
Parts(Input), Intrasheet Parts(Output), Intrasheet
Parts(Input), AI, AO, DI, DIGCOMP, REGPV, REGCTL, Left-click on the sheet to create Parts
LOGIC, FLAG, NUMERIC, NMARRAY [R411 or later],
STRING [R411 or later], DATETIME [R411 or later],
TIMER, PROCMOD.
Able to create CL parts to be loaded
Choose CL button
to the process module point
Choose buttons such as ALGO(LOG), NUMERIC(LOG) , Create Logic-component Parts to
FLAG(LOG) , CONNECT(LOG) , GATEWAY(LOG) draw Logic diagram

− 120 −
 5.2 Control Parts

Table 5-8. Appear in the status bar of Control Parts (Block)

Operation Message in the status bar

Click to select a RTC Part, or drag to
Choose Select button
select multiple RTC Parts
Select Container Parts on the Sheet Drag to move or resize
Select Point Parts on the Sheet Drag to move
Click a port on the Sheet Drag to move
Click the left mouse button on the
Choose Container button
sheet
Click the left mouse button on the
Choose Link button, Bold Link button
start port
Choose Link button, Bold Link button and select a starting Click at the joints, double-click at the
Port end Port
Choose buttons such as Divergence Parts, Job Parts(Output),
Job Parts(Input), Intersheet Parts(Output), Intersheet
Parts(Input), Intrasheet Parts(Output), Intrasheet
Parts(Input), Frame, BOX Parameter, ADD, SUB, MUL,
DIV, MOD, SUM, DADD, ABS, SQR, SQRT, LN, LOG, EXP,
EXPT, SIN, COS, TAN, ATAN, TRUNC, ROUND, MAX,
MIN, AVG, HSE, LSE, MID3, SW, SFT, ALSW, HLM, LLM,
DRL, HMS, LMS, DRM, DMS, NUMCHK, BADCHK, Left-click on the sheet to create Parts
INFCHK, QLTCHK, CHGCHK, PTE, ETP, FUNC, AND,
OR, NOT, NAND, NOR, XOR, QOR2, SR, RS, EQ, NE, GT,
GE, LT, LE, FIXPLS, MAXPLS, MINPLS, CYCPLS, WDT,
DELAY, ONDLY, OFFDLY, UCNT, DCNT, AAV, PAV, PID,
PRO, INT, DIF, LDLG, DED, TF, RMP, MAV, ANMA, GW,
CONV, SG, FL, DLTPV, TIMFL, ANDIN4, ORIN4, PSQRT,
REDTAG

− 121 −
Chapter 5. RTC Parts

5.2.2 Types of Control Parts

■
■Control Parts Tool Bar contains the following Parts

Table 5-9. Control Parts Tool Bar (Point)

Types of Parts Parts

Editing Parts Select, Reshape
Container Parts Container
Utility Parts Intersheet, Intrasheet, Divergence, Job, Link
AI, AO, DI, DO, VALIN, VALOUT, DIGCOMP, REGPV,
REGCTL, LOGIC, FLAG, NUMERIC, NMARRAY [R411 or
Point Parts
later], STRING [R411 or later], DATETIME [R411 or later],
TIMER, PROCMOD
CL Parts A CL Part holds a CL program inside
Logic Component Part is a collective name for the following
Parts This type of Control Parts are combined and bound
Logic Component Parts
to a LOGIC datapoint ALGO(LOG) , NUMERIC(LOG) ,
FLAG(LOG), CONNECT(LOG) , GATEWAY(LOG)

Table 5-10. Control Parts Tool Bar (Block)

Types of Parts Parts

Editing Parts Select, Reshape
Container Parts Container
Utility Parts Intersheet, Intrasheet, Divergence, Job, Link, Bold Link
ADD, SUB, MUL, DIV, MOD, SUM, DADD, ABS, SQR,
SQRT, LN, LOG, EXP, EXPT, SIN, COS, TAN, ATAN,
TRUNC, ROUND, MAX, MIN, AVG, HSE, LSE, MID3, SW,
SFT, ALSW, HLM, LLM, DRL, HMS, LMS, DRM, DMS,
NUMCHK, BADCHK, INFCHK, QLTCHK, CHGCHK,
Block Parts PTE, ETP, FUNC, AND, OR, NOT, NAND, NOR, XOR,
QOR2, SR, RS, EQ, NE, GT, GE, LT, LE, FIXPLS, MAXPLS,
MINPLS, CYCPLS, WDT, DELAY, ONDLY, OFFDLY, UCNT,
DCNT, AAV, PAV, PID, PRO, INT, DIF, LDLG, DED, TF,
RMP, MAV, ANMA, GW, CONV, SG, FL, DLTPV, TIMFL,
ANDIN4, ORIN4, PSQRT, REDTAG
Block Auxiliary Parts Frame, BOX Parameter

In addition to indicating control designs on sheets, Control Parts also have functions for creat-
ing Controller Databases.
Container Parts provide a structure for managing multiple sheets in a tree structure.
Efficient design information can be summarized as Container Parts that can be reused.
Point Parts are parts where one Part corresponds one-to-one to a Controller Part.
CL Parts are parts for managing CL Programs.
Logic Component Parts are Parts for expressing logical algorithms. Multiple Logic Component
Parts correspond to the Logic Point of one single Controller.
Connecting these Parts by means of parameterization allows automatic definition of the set-
tings of input connections and output connections.
In the case of Bold Link Parts, the thickness of the link line is shown thicker than that of the
normal Link (Link Parts). The operation methods and functions are exactly the same as for
Link Parts. Block Parts are parts where one Part corresponds one-to-one to an Controller.
− 122 −
 5.2 Control Parts

Frame Parts are the parts for the operation screen (face plate) on the RTC sheet.
BOX Parameter Parts are parts for referencing the BOX parameters of XPC, PL2, FC, PC4
[411] and HL Controllers.

■
■Work Flow Related to Control Parts
The following provides an overview of the procedure for loading Control Parts information
to a Controller.

Step 1 Assign the Control Part to the Sheet, and move it if required.

Step 2 Define the I/O connections between Control Parts using the Link.
The properties of Control Parts should be set, and other parameters should be
configured.

Step 3 Execute the [Implementation] → [System Conf] commands from the Job Structure
menu and configure the network and nodes.

Step 4 Execute the [Implementation] → [Create PDB] commands from the Job Structure
menu to build the Point Database.

Step 5 Based on the Point Database, create the EB source file and the Controller Data File
(IDB file).

Step 6 Load the Controller Data File to the Controller. Refer to Chapter 6, “Implementing
Harmonas-DEO System.”

− 123 −
Chapter 5. RTC Parts

5.2.3 Behavior of Control Parts

In this section, the basic behavior of Control Parts is described.

■
■Creating Control Part

Step 1 Click any button from Control Parts tool bar.

Step 2 Click anywhere on the Sheet. A Control Part is created, and the location of mouse
click becomes the left-bottom corner of the Part.

Note The creation operations for Control Parts cannot be repeated by the [Edit] → [Redo]
commands.

■
■Editing Control Parts
The edit functions applicable to Control Parts are shown in the following table:

Table 5-11. Editing Control Parts

Drawing Style
Re- Move
Move Resize Line/Text Fill
Shape Port
Color LineSize Color Pattern
Link ✓ – ✓ – – – – –
Container Part ✓ ✓ – ✓ ✓ ✓ ✓ ✓

Point Part ✓ ✓* – ✓ – – – –

CL Part ✓ ✓* – ✓ – – – –
Logic Component
✓ ✓* – ✓ – – – –
Part
Block Part ✓ ✓* – ✓ – – – –

* The size of the appearance can be changed using the [Control Properties] → [View] com-
mands. See Section 5.2.3.3, “Parts View.”

■
■Setting Properties
Properties are a set of configurable characteristics of Control Parts includes parameters for
each data point in the Controller. The Configuration Sheet may differ from one Control Part
to the other. To call up the Configuration Sheet:

Step Double-click on a Control Parts on the Sheet

Step Select a Control Part and choose the [Properties] command from the [Edit] menu.

Step Move cursor to a Control Part and click the right button of the mouse.
Choose [Properties] command from pop-up menu.
Set parameter values in Configuration Sheet.
Parameters related to input-output connections can be set in the Configuration
Sheet and also when connecting the parameter link. Validity of set values is
checked automatically. Errors found in the current page of the property sheet must
be corrected
before further changes are made.
− 124 −
 5.2 Control Parts

■
■Logical Tag Name
Every Control Part (except Block Parts) has an entry called Logical Tag Name, which uniquely
identifies the Control Part, and is unique within individual Sheet.
Tag Names are usually determined after the design phase, so Logical Tag Names are good
identifiers for Control Parts in the design phase. Also, while the Tag Name is by nature Job-
specific, the Logical Tag Name can be generic. This promotes the reuse of Control Parts.
When creating a Control Part on the Sheet, the Control Part will have the default Logical Tag
Name “UnNamed???” ,where ??? is a three-digit number assigned by RTC Editor. This default
name does not appear on the default view of the Control Part and you can change the Logical
Tag Name later in the Configuration Sheet. The Logical Tag Name should be less than 16 alpha
numeric characters in length.

Note The following characters are not available for Logical Tag Names:
comma (,) “at”mark (@) sharp mark (#)
period (.) colon (:) semi-colon (;)
slash (/) parentheses (()) space ( )
The default Logical Tag Name for the Container Part is different from that of other
Control Parts. Refer to 5.2.4, “Container Parts” for more information.

Note Since the Logical Tag Name should be unique within a Sheet, any attempt to give
already-existing names will cause an error. Also, when a Control Part is pasted in the
Sheet, its Logical Tag Name is automatically set to default.

■
■Setting Control Properties
Control Properties provides to set Reference Parts. Add/Delete Ports and Intersheet Link.
To call up the Control Properties of each Control Part:

Step Double-click Control Parts on the Sheet while pressing the <Shift> key.

Step Move cursor to a Control Part and click the right mouse button.
Choose the [Control Properties] command from pop-up menu.

− 125 −
Chapter 5. RTC Parts

5.2.3.1 Parameter Links

There are two kinds of links; Parameter Links for defining the data transfer between Control
Parts and Point Links for mapping points. Which link should be used is determined by
whether the port is a [Port] or a [Reference Port] at the time that the link is established.
Parameter Links are described in the following.

■
■Appearance of Parameter Links
Parameter Link is shown as a purple thin polyline.

■
■Link horizontal/vertical mode
By making the link horizontal/vertical mode valid, you can efficiently:
•• Draw a link constituting of horizontal and vertical lines.
•• Move Parts while maintaining the link horizontality and verticality.
To make the link horizontal/vertical mode valid or invalid, use the <Horizontal/Vertical
Links> button in the standard tool bar.

Table 5-12. Button Status and Mode

Button Status Link Horizontal/Vertical Mode

Pressed Enable
Not pressed Disable

The results of the operations on links to be explained below vary depending on whether the
link horizontal/vertical mode is valid or invalid. For the method of each operation, see the
corresponding item described below.

Table 5-13. Different Results of Link Operations

Setting Link Horizontal/Vertical Mode

Operation on Link Shape of Link
Valid Invalid
The position of an added inflection point is
adjusted from time to time so that the link
Link has an inflec-
becomes horizontal/vertical. You can prevent Link shape is not ad-
tion point
Create a Parameter such adjustment by adding an inflection justed. Link is shaped
Link point while holding down the [Ctrl] key. according to the inflec-
When the input port is clicked, an inflection tion point added.
Link has no inflec-
point is automatically added to reshape the
tion point
link to be horizontal/vertical.
Horizontal/vertical
Link moves in parallel
Reshape a parts of link An inflection point is
Parameter Link Obliquely shaded added
Link cannot be moved
part of link
Move an inflection
point of a Parameter Position of the inflection point moves
Link

Note When an inflection point is automatically added, its position may be improper if the
distance between the output and input ports is short.
In such a case, move the inflection point to an appropriate position.

− 126 −
 5.2 Control Parts

■
■Creating Parameter Links

Step 1 From the Control Parts tool bar, click the <Link> button.

Step 2 First, click the output port of the Control Part.

Step 3 As necessary, click on the Sheet in a way to draw a polyline, in order to add inflec-
tion points to the link.
•• To add an inflection point to a point at which the link does not become horizon-
tal/vertical when the Link Horizontal/Vertical Mode is valid, click on the Sheet
while holding down the [Ctrl] key.
•• If you click outside the Sheet area, an inflection point is placed on the border of
the Sheet area.
•• If you perform operations while holding down the [Shift] key, lines from the
port/inflection point form eight directions: horizontal and vertical directions
and directions making 45 degrees.
•• Aright-click cancels the last inflection point. If you reach the port on the start-
ing side while repeating right-clicks, the operation to connect the link itself is
canceled.

Step 4 Lastly, click the input port of the Control Part that becomes the destination of data
transfer.
•• If the Parameter Link between the Control Parts is incorrect, a message appears
and the link is canceled.

For operations at the time of creation, see Table 5-13, “Different Results of Link
Operations.”

Note A Parameter Link between ports must be complete within a Sheet. To link
a Parameter Link with the point of a Control Part in another Sheet, use an
Intersheet Parts described in 5.2.11.1.

■
■Reshaping Parameter Links
Reshaping procedure is as follows:

Step 1 Choose a Parameter Link.

Step 2 Drag the Parameter Link with the mouse.

For operations at the time of reshaping, see Table 5-13, “Different Results of Link
Operations.”

− 127 −
Chapter 5. RTC Parts

■
■Moving inflection points of Parameter Links
The reshaping procedure is as follows:

Step 1 Choose a Parameter Link.

Step 2 Drag the inflection point () of a Parameter Link with the mouse.
•• If you move an inflection point while holding down the [Shift] key, the angle of
one of the two ends of the link with the inflection point is aligned to the closest
of the eight directions: horizontal and vertical directions and directions making
45 degrees.
•• If you try to move the position of the inflection point at which the 45- degree link
crosses the horizontal and the vertical directions while holding down the [Shift]
key, the inflection point moves along the link.
(The 45-degree link angle is retained, so the other end does not necessarily align
with the eight directions.) At this time, if you press the [Ctrl] key while holding
down the [Shift] key, the direction-fixed parts are inverted.

For operations at the time of moving inflection points, see Table 5-13, “Different
Results of Link Operations.”

Restriction You cannot change the color and width of Parameter Links by altering the Drawing
Mode. The format of the data (analog, digital, etc.) to be passed by Parameter Links
is not distinguished by color or line type.

5.2.3.2 Port
Port represents parameter which is eligible for input/output connection. Different types of
Control Parts may have different sets of Ports, some are visible by default, and others are vis-
ible only if specified in [Control Properties] property sheet.
The Port where the Parameter Link starts is called the Output Port, and the Port where the
Parameter Link ends is called the Input Port.

■
■Appearance of Port
Port is shown as a small square () on the borders of Control Parts. The color of Port is blue
(for output Port), red (for input Port), and pink (when undecided).
When the Class View or Custom View is assigned to the Control Part, the Port will appear on
the rectangle surrounding the Part.

■
■Changing Visibility or Location of Port Name
Double-click on Port and [Set Port Name] dialog box is invoked. From this dialog box, you
can set visibility and location of Port Name.

− 128 −
 5.2 Control Parts

Table 5-14. [Set Port Name] dialog box

Control Description
Parameter Parameter which the Port represents
Choose either of [Visible] or [Invisible]
Visible/Invisible When [Visible] is chosen, the Port Name is shown, and when
[Invisible] is chosen, the Port Name disappears
Choose either of [Inside] or [Outside]
When [Outside] is chosen, Port Name is shown near the Port
In/Out
When Inside is chosen, Port Name is shown inside the Port,
which becomes hollow
Location is important if [Outside] is selected as for [In/Out]
group box since it determines where the Port Name is dis-
Location played
Choose either Upper-Left, Upper-Right, Lower-Left or
Lower-Right

You can cancel the display by clicking the Parameter Name shown beside Port, choosing only
the Parameter Name, and pressing the [Delete] key. You can also change the location of the
display by dragging only the Parameter Name.

Once you delete the Parameter Name, it does not become visible until you set <Visible> in the
[Edit Port] dialog box or in the [Set Port Name] dialog box.
You cannot perform operations such as Cut and Copy by choosing only a Parameter Name.

Note Because Port is small, it looks as if it were filled when a Parameter Name is shown in
Port. You can read the Parameter Name by scaling up the window.

Restriction Even if you open the [Set Port Name] dialog box for Control Parts, none of the four
option buttons indicating outside-Port locations is chosen, and the current loca-
tion is not shown.

− 129 −
Chapter 5. RTC Parts

■
■Moving Ports
You can move Port to any point on the boundary of the Control Part. However, when [Snap to
Grid] is checked, you can move Port only to the intersection of the boundary and the gridlines.

The procedure for moving Port is as follows:

Step 1 Click the Port to be moved.

Step 2 Drag the Port to any position. The Port moves along the boundary nearest to the
mouse position.
•• You can move the Port even when the link is connected.

For operations at the time of moving the Port, see Table 5-15, “Different Results of Moving
the Port.”

Table 5-15. Different Results of Moving the Port

Link Shape between Link Horizontal/Vertical Mode

Port and Inflection Point Valid Invalid
The position of the inflection point
next to the Port is adjusted to keep
Positions of inflection points are
Horizontal/vertical the link horizontal/vertical.
not changed
Positions of other inflection points
remain unchanged
Positions of inflection points are Positions of inflection points are
Oblique line
not changed not changed

Note When a Port is moved, Port text may be hidden behind a Part. In such a case, bring
the Port text in front of the Part by changing the location of the Port or by using a
command in the [Draw] menu. (For these operations, it is necessary to change the
location of the Port text once so that it can be handled.)

■
■Automatic adjustment of Port location
When a Part is moved under the following settings, the Port location is automatically adjusted
on the gridlines:
•• Snap to Grid : valid
•• Actual Interval : default (2 mm)
•• Horizontal/Vertical Links : valid

Note When Ports are close to each other, they may overlap as a result of automatic ad-
justment of the Port locations. If this happens, separate them so that they do not
overlap with each other.

− 130 −
 5.2 Control Parts

■
■Adding or Deleting Port
For Control Parts, only the most typical parameters are shown as the default Ports for selec-
tion. To show more parameters, add Ports at <Parameter/Port> page of [Control Properties]
property sheet.

Table 5-16. <Parameter/Port> page of [Control Properties] property sheet

Control Description
List box shows the names of parameters capable of connec-
Port(s) Candidates
tion, and not shown yet
List box shows the names of parameters already selected and
Port(s) Used
used as Ports
Add a Port by moving a parameter name from Port
Add >>
Candidates Candidates list box to Ports Used list box
Delete Port by moving a parameter name from Ports Used
<< Delete
Used list box to Port Candidates list box

5.2.3.3 Parts View

The appearance of the Control Parts can be set by the Parts View.

■
■Resizing the Appearance of Control Parts
The appearance of the Control Parts can be resized. Open the <View> page on the [Control
Properties] sheet. The setting is made in the [Displaying scale of default view] group box.

Table 5-17. [Displaying scale of default view] group box

Control Description
Size of appearance in the X-direction Can be set in integers
X
from 1 to 3
Size of appearance in the Y-direction Can be set in integers
Y
from 1 to 3

Custom View and Class View cannot be changed here.

− 131 −
Chapter 5. RTC Parts

5.2.4 Container Parts

The Container Part represents a Sheet. Job Tree structure is formed using Container Part. This
nested structure is displayed in the Job Structure Window.

■
■Appearance of Container Part
Container Part may have Class View and Custom View. Since Container Part usually repre-
sents some functions, you may assign Custom View more frequently than other types of Parts.
Default View of the Control Part is shown as follows.

Container1 Logical Tag Name

Figure 5-4.

■
■Creating Container Part

Step 1 Click the <Container> button from Control Parts tool bar.

Step 2 Click or drag the mouse on the Sheet.

Click the mouse on the Sheet and a Container Part is created at the default size,
with its left-lower corner at the location of the mouse click.
Drag the mouse on the Sheet to create a Container Part of a customized size.

Step 3 When a Container Part is created, its Sheet is also created at the same time, and
opens as a blank Sheet Window.
In the Job Structure Window a new Container is added below the parent Container,
which corresponds to the Sheet on which you just created the Container Part.

Step 4 You cannot undo of Container Part creation. Delete the part to remove.

Step 5 When a Container Part is deleted on the sheet, the Container is moved to the Job
Repository in the Job Structure Window, in which the Container is shown in gray,
so that the item is not removed by the [Undo] operation.
Thus, operation on the item while it is in the Job Repository is prohibited.
•• The Container is shown again at the original position if the [Edit] → [Undo]
commands are executed under these circumstances. However, the Sheet remains
closed.
•• If the Sheet is saved under these circumstances (depending on the Control Parts
settings, saving may be performed automatically), the Container will be recog-
nized as having in fact been deleted, and it will be shown in the normal fashion
in the Job Repository and can therefore be operated.
This also applies to other container creations that have become exempted from
the [Undo] processing due to other operations.

Note When a Container is placed on the Sheet, the Sheet will be saved by overwriting in
this condition. Simultaneously with the Sheet being saved, the operations recorded
for the Sheet prior to when the Container was placed on the Sheet are deleted, and
these operations will no longer be restorable by the [Undo] operation.
− 132 −
 5.2 Control Parts

■
■Container Name (Logical Tag Name of Container Part)
In this document, the Logical Tag Name of Container Parts is also called the Container Name.
Default Container Name is “Container?”, where ? is Job-unique number given by RTC Editor
(Note)
.

Note Although the Container Part is categorized as the Control Part, the default Logical
Tag Name is named differently from other types of Control Parts.

Sheet File Name is also named after the Container Name as {Container Name}_?.SHT,
where ? is Job-unique number given by RTC Editor.
For example, when you create a Container Part, its default name may be Container_3,
whose Sheet File Name is Container3_4.sht. When you change the Container Name
to “Furnace”, the Sheet File Name will be “Furnace_4.sht”.

Note You should close the corresponding Sheet Window when you wish to change
Container Name. Container Name, as with Logical Tag Name, is less than 16 alpha
numeric characters, and excludes the following:
. / \ * | : ; , = [ ] < > “ space

■
■Change Container Name
The operation to change the Container Name depends on where the Container resides in the
Job Window.
•• Root Container
Since the name of the Root Container derives from the Job Name, you must change the
Job Name at the Job Info dialog box.

•• Child Containers
For the Containers located on a different Sheet, change the Container Name at the prop-
erty sheet of the Container Part.

•• Top Containers in Job Repository

Since top Containers in Job Repository do not belong to any Sheets, you cannot change
their names from property sheet. For these Containers, in the Job Window click the right
button on the Container, and choose [Rename Container] command from the pop-up
menu.

Note When moving or copying Containers, the name of the top Container is changed to
the default name to avoid duplication.

■
■Resizing Container Part
Same as for Rectangle Part.

■ Drawing Mode
■Set
Same as for Rectangle Part.

− 133 −
Chapter 5. RTC Parts

■ Properties
■Set
Invoke property sheet by double-clicking on a Container Part on the Sheet. Container Name
will be shown in the caption bar of the Properties property sheet.

Table 5-18. Container page in property sheet

Control Description
Type the Container Name in this box To change the
Container Name Container Name, make sure that the corresponding Sheet
Window is closed
Document -
Description You can type any text
Open Sheet Choose this button to open the corresponding Sheet Window

Note Edit Param page and RVinfo page of Container Parts’ Properties property sheet are
reserved for used by the RV info software package. Do not use these pages unless
so instructed.

■
■Adding internal Ports
An internal Port is used for the parameter link of the Port of a Part on the Sheet on which a
Container Part is located and the Port of a Part inside the Container.

The procedure for adding an internal Port is as follows:

Step 1 Right-click a Container Part, and from the menu displayed, choose [Control
Properties].

Step 2 From the [Setting] dialog box displayed, choose the [Parameter/Port] tab.

Step 3 Click the <Add Parameter> button.

Step 4 Set [Name] in the [Set Parameter/Port] dialog box displayed, and then change the
toggle button in [Port] to “Yes.” These operations add an “internal Port” to the Sheet
corresponding to the Container to which a parameter has been added.

■
■Deleting Container Parts
Select a Container Part on the Sheet, and Click the <Delete> key.
This operation erases the Container Part from the Sheet. In the Job Window, the deleted
Container moves from Job Tree to Job Repository. As long as you are allowed to undo this
Delete operation, the deleted Container in the Job Repository is displayed in gray and does
not accept any operations.

When deleting a Container Part, all offspring Containers descending from the target
Container will be deleted too.

− 134 −
 5.2 Control Parts

■
■Cutting Container Parts
Select a Container Part and select [Cut] command from [Edit] menu, the Container Part will
be erased from the Sheet. Except that the Container Part is stored in the clipboard, the behav-
ior of the Container Part is the same as for the Delete operation.

■
■Copying or Moving Container Parts
In the Job Window, move or copy any Container by dragging and dropping.
In the Sheet Window, you can move or copy by selecting [Cut], [Copy] and [Paste] commands
from [Edit] menu.
All offspring Container Parts descending from the target Container are moved or copied too.

5.2.5 Point Parts

Point parts are a generic name of control parts corresponding to points on the controller. This
section summarizes the common contents of basic operation and operation procedure.

■
■Display example of point parts
In addition to default view, point parts can provide two views: custom view and configuration
view. For custom view and configuration view, refer to Sections 4.3.2 and 4.3.3.
The default view of the point parts is displayed as follows.

FlowControl Logical Tag Name

PID Part type
TIC 101 Tag Name

Figure 5-5.

Where, the default values are shown below.

Logical tag name : none
Parts type : analog input, analog output, etc. See Table 5-19.
Tag name : none

■
■Point Parts List
Following Table lists the Point Parts, the Part Type shown in the default view and Ports shown
by default:

− 135 −
Chapter 5. RTC Parts

Table 5-19. Point Parts, Type in the default

Point Object Part Type Input Port Output Port

Analog Input Analog Input PV
Analog Output Analog Output OP
Digital Input Digital Input PVFL
Digital Output Digital Output SO
Value Input Value Input PV
Value Output Value Output OP
Digital Composite Digital Composite
RegPV*
DATAACQ P1
FLOWCOMP F, G
MIDOF3 P1, P2, P3
HILOAVG P1, P2
Regulatory PV
SUMMER P1
CALCUTR P1, P2
VDLLDLAG P1
TOTALIZR P1
GENLIN P1
RegCtl**
PID PV OP
PIDERFB PV, RFB, TRFB OP
PIDFF PV, FF,OP OP
OP, LOWRDSTN,
POSPROP PV, SP
RAISDSTN
Regulatory Control
INCRSUM X1 OP
AUTOMAN X1 OP
RATIOCTL PV, X2 OP
ORSEL X1, X2 OP
SWITCH X1, X2 OP
RAMPSOAK PV OP
Logic LOGIC
Flag FLAG PVFL
Numeric NUMERIC PV
Nmarray [R411 or later] NMARRAY
String [R411 or later] STRING
Datetime [R411 or later] DATETIME
Timer TIMER PV
Process Module PROCMOD

* Part Type of Regulatory PV Point Parts:

With Regulatory PV Parts, the name of PV ALGORITHM is shown as the Part Type. When
NONE is chosen, “REGPV” is shown.
** Part Type of Regulatory Control Point Parts With Regulatory Control Parts, the name of
ALGORITHM is shown as the Part Type. When NONE is chosen, “REGCTL” is shown.

− 136 −
 5.2 Control Parts

Note Even if you change the number of input connections or output connections in the
[Configuration Sheet] property sheet, the Port is not automatically deleted from
the Sheet. For example, even if you set the number of input connections to 2 in
the setting of Control Parts properties to display SP and PV Ports and then change
the number to 1, the Ports remain visible. To make the Ports invisible, delete the
parameter from the “Port (s) Used” list on the [Parameter/Port] page of the [Control
Properties] property sheet.

■ Properties for Point Parts

■Set
From [Properties] property sheet, set Logical Tag Name and parameters specific to the cor-
responding data point. For more information on parameters, see “Control Parts Function
Manual”.
•• The Part Type is shown in the caption bar of [Properties] property sheet.
Contents of [Properties] property sheet of Point Parts.

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

Table 5-20. [Properties] property sheet of Point Parts

Control Description
LOGICAL TAG NAME is shown or changed.
LOGICAL TAG NAME
UnNamed??? by default
TAG NAME is shown or changed.
Must be within 16 characters and should start with an alpha-
numeric character. Alphanumeric and underscore characters
can be used from the second character onward.
However, the following cannot be used as a tag name:
•• A character string consisting of only numerical characters
TAG NAME •• A character string including consecutive underscore char-
acters
•• A character string ending with an underscore character
•• A character string starting with “Z#” or “Z$”
•• “xxxBOXyyy” (xxx:Node Type, yyy:Node Number)”
Even when lower-case letters are entered, the corresponding
uppercase letters will appear when they are displayed.
Choose from among PRC, PL, XPC, PL2, FLC, FC and PC4
NODE TYPE *
[R411 or later]
This descriptor is shown in faceplate.
POINT DESCRIPTOR First 12 characters are shown in the upper half in the first
plate and second 12 characters in lower half.
Should be equal to or less than 6 characters, because only first
E.U. DESCRIPTOR
6 characters in Alarm Summary
UNIT ID * Enter two alpha numeric characters for UNITID.2
Number of Node from 1 to 126. System connected devices
NODE NUMBER * such as SS, PRC, PL, HS, GS are assigned within this node
limit
For other parameters See “Parameter Reference Manual”

− 137 −
Chapter 5. RTC Parts

* On the [System Configuration] property sheet displayed by clicking the [System Conf]
command in [Implementation], you can make these settings at the same time on a
Container by Container basis in the Job Window.
By checking the <Apply Node> button on the [System Conf] page, you can specify node
type and node number, and by clicking the <Apply Unit> button on the [Unit ID] page, you
can specify all necessary unit identifiers.

Note If you set NaN (Not a Number) for the parameter value, type in as follows.
•• Real ......................................... “- - -” (three hyphens)
•• Integer ................................... “- - -” (three hyphens)
•• Entity_id ................................ “- -” (two hyphens)
•• Parameter_id ........................ “- -” (two hyphens)
•• Entity_id.Parameter_id ....... “- -.- -” (sets of two hyphens separated by a period)

For only these parameters, procedures for making values undefined or setting
NaN values are defined. As to whether or not parameters are available to make a
value undefined or to set a NaN value, refer to the “MS2-DEO300-6001 Parameter
Reference Manual.”

Restriction If the controller value is infinite (larger than 3.4E+38 or smaller than 3.8E-38 in
the real type value range), “1.#INF00” or “-1.#INF00” indicating an infinite value is
set to the part when this value is uploaded. When the [Properties] property sheet
for this part is opened in this state, the message, “Please enter a real value in the
parameter,” appears. However, there is no problem with the value set to the part,
and an infinite value has been set for the part.
•• To make this message not to be displayed, enter real values using only numeri-
cal characters in the [Properties] property sheet. To set an infinite value, enter
a value larger than 3.4E+38 or smaller than 3.8E-38 again (for example, 39 con-
secutive nine (9) characters as a positive infinite value).
•• If the [Properties] property sheet is closed with the <Cancel> button or the
[Properties] property sheet itself is not opened, the operation for point genera-
tion/ controller data file generation outputs an infinite value to the controller
data file.
When the loading operation is executed in this state, the infinite value is loaded
into the controller.

Note Once you choose <Apply> button at the Point Part’s Properties property sheet, all
inputs up to that point in time are reflected in the property sheet.

− 138 −
 5.2 Control Parts

Restriction When entering parameter values consecutively in the [Properties] property sheet,
parameters that should be able to be configured may not be displayed.
In such a situation, update the display by clicking the <Apply> button or reopen
the property sheet by clicking the <OK> button. Then the display is updated and
correct parameters will be displayed.
If the user changes two or more parameters in the [Properties] property sheet, the
feature that checks range of parameter may not work properly. In this case, please
enter one parameter and click the <Apply> button. Then, please enter another
parameter.

5.2.5.1 Tips On Point Parts

■
■Analog Input Point Part
•• For Pulse Input (PI), set “PI” for PNTMODTY parameter.

•• For RTD Sensor Type Point, CHARACTERIZATION (PVCHAR) has three types of ranges:
DINRTD (-200..800), JISRTD (-200..650), and NickIRTD (-45..315).
However, these ranges are not checked against PV RANGE HIGH (PVEUHI) or PV
RANGE LOW (PVEULO).

Note DINRTD corresponds to Pt100 (new JIS), and JISRTD, JPt100 (old JIS).

•• Since all PV-related range parameters cannot be shown in one page, and range check is
activated on a per-page basis, RTC Editor limits its range-check algorithm to avoid errors.
RTC Editor checks the following parameters only:
– PVEXEULO <= PVEXEUHI
– PVEULO <= PVEUHI
– PVLLTP <= PVLOTP <= PVHITP <= PVHHTP
Therefore, even if you set higher value for PVEUHI than for PV EXEUHI, such an error will
not be detected by RTC editor.

•• When, for signal unit I/O, you use the high-level input unit, thermocouple (TC) input unit,
or resistance temperature detector (RTD) input unit, set the module type to HLAI and use
the 1 to 5 V sensor type. Note that you cannot use 0 to 5 V.

•• When, for signal unit I/O, you use the thermocouple (TC) input unit or resistance tem-
perature detector (RTD) input unit for high-level input, set the temperature range set for
the thermocouple (TC) input unit or resistance temperature detector (RTD) input unit as
PVEULO/HI at the high-level input point. Set PVEXEULO/HI to temperature values cor-
responding to the -6.9% to 0% and 100% to 106.9% ranges.

•• When, for signal unit I/O, you use the thermocouple (TC) input unit or resistance tem-
perature detector (RTD) input unit, set the sensor type, temperature range, and open wire
detection direction (TC only) on the input unit side.

− 139 −
Chapter 5. RTC Parts

■
■Digital Output Point Part
•• The default output type for digital Output Parts is “Status.” SO is the only Port shown in the
default view.

•• When you wish to connect a Parameter Link with the LOWRDSTN parameter or the
RAISDSTN parameter of the ON-OFF control algorithm (PosProp) for regulatory con-
trol Points, configure the ONPULSE or OFFPULSE parameter, not SO, as a Port on the
[Parameter/Port] page of the [Control Parts Properties] property sheet before making the
connection.

•• To set the Output type to Pulse, set the [DOTYPE] parameter to “PWM” (pulse).
On the [Parameter/Port] page of the [Control Parts Properties] property, specify “Visible”
for the OP Parameter Port.

■
■Regulatory PV Point Part
•• With algorithm (GenLin), the parameters range check such as PVHHTP <= PVEXEUHI or
PVLLTP >= PVEXEULO are not performed.

•• PV-related range parameters are not set on the same page. The range check is implemented
when the page is changed, or the <OK> button is pressed, and then the RTC Editor per-
forms only the next range check. Consequently, an error is not generated, even if the
PVEUHI value is made larger than PVEXEUHI.
– PVEXEULO <= PVEXEUHI
– PVEULO <= PVEUHI
– PVLLTP <= PVLOTP <= PVHITP <= PVHHTP
With Totalizr algorithm, the P2 port is not displayed for parts even when ACCTYP=PULSE.
Even when ACCTYP=PULSE, define the pulse input source PISRC (1) parameter (the port is
P1) to be the PV parameter of the pulse input point.

■
■Regulatory Control Point Part
•• Up to four output connections can be made from OP Port of Regulatory Control Point Part.
Since input connections can be made to this OP Port, it may look like more than four output
connections are made.

•• There are two types of connections: the “pull” connection and the “push” connection. With
the “pull” connection, the input Port specifies the source Point.Parameter, while with the
“push” connection, the output Port specifies the destination Point.Parameter. With some
combinations of output Port and input Port, it is possible to establish both “pull” and “push”
connections. For example, when connecting OP Port of one Regulatory Control Point Part
to SP Port of another. Connect a Parameter Link between these Ports, and a dialog box ap-
pears for you to choose one. You must then reset the other using NOCINPTS/NOCOPTS
parameters. If you choose the “pull” connection, reset the “push” connection by setting zero
for NOCOPTS parameter (for the Point Parts with output Port). If you choose the “push”
connection, reset “pull” connection by setting zero for NOCINPTS parameter (for the Point
Parts with input Port).

− 140 −
 5.2 Control Parts

•• The OP Port of the Regulatory Control Point Part can fan out to 4 parameters at maximum.
However, when the connection destination of the output port is the Analog Output Point
Part, the Digital Output Point Part, the FFFB (FF_AO) Point Part, or the FFFB (FF_DO)
Point Part, the number of connectable link is only “1” (However, PIDERFB is excluded from
this rule).
•• Since all PV-related range parameters cannot be shown in one page, and range check is
activated on a per-page basis, RTC Editor limits its range-check algorithm to avoid errors.
RTC Editor checks the following parameters only:
– PVEXEULO <= PVEXEUHI
– PVEULO <= PVEUHI
– PVLLTP <= PVLOTP <= PVHITP <= PVHHTP
Therefore, even if you set higher value for PVEUHI than for PV EXEUHI, such an error will
not be detected by RTC editor.

■
■Logic Point Parts
•• Delay time can be set for some types of algorithms. The delay time can be set with a real
value; however, it will be regarded as an integer (rounded to the nearest integer) in the
controller.

•• If the loading operation is executed with the L(1) to L(12) parameters at logic points of
another node set to the input connection destination, an Invalid_Destination_Parameter
error is generated.
In such a case, do not make settings for the L(1) to L(12) parameters at the input connec-
tion destination, but set “tag.parameter name” at the input connection destination directly.
For example, if the following setting has been made at the LG01 logic point at node 1,
LG01.LISRC(1) = A100.PV
do not make the following setting for the LG02 logic point at node 2 via this setting
LG02.LISRC(5) = LG01.L(1)
but make the following setting directly
LG02.LISRC(5) = A100.PV.

− 141 −
Chapter 5. RTC Parts

5.2.5.2 FFFB Parts

FFFB parts are point parts a generic name of control parts corresponding to points on the
controller. This paragraph explains a point different from Point Parts.

■
■Display example of FFFB parts
The shape of FFFB parts is equal to ordinary point parts. The color of line is green.
(Default view)

FlowControl Logical Tag Name

FF_PID Part type
FF_TIC_ 101 Tag Name

Figure 5-6.
FFBLKTYP is displayed in Part Type area.

■
■Creating FFFB Parts
Control Parts tool bar doesn’t have a button for FFFB parts. FFFB parts are created by im-
porting csv files from RTC_FB on [Import Parameter] window. Refer to 6.1.9.4, “Import
Parameter” for more information.
When you want to create Reference Parts of FFFB point, copy the FFFB part and paste into
another sheet. And connect a point link.

■ Properties for FFFB Parts

■Set
From [Properties] property sheet, set parameters specific to the corresponding data point.
Parameters from RTC_FB are read-only parameter. When you want to change parameters
from RTC_FB, change the value on RTC_FB and import csv files again.
Refer to “MS2-HDS900-6001 Parameter Reference Manual” for more information.

■
■Referring to RTC_FB
Some parameters in FFFB parts are configured by RTC_FB. RTC_FB data can be referred eas-
ily from FFFB parts by this function.
Right-click a FFFB parts and select following command. RTC_FB data which is associated
with FFFB parts can be opened directly.

Table 5-21.

Command Description
Refer to control loop of Call RTC_FB and open control loop which is associated with
RTC_FB the FFFB parts.
Refer to block of Call RTC_FB and open block which is associated with the
RTC_FB FFFB parts.

− 142 −
 5.2 Control Parts

5.2.5.3 Point Parameter Name Format

Point parameter name can be specified in control connection parameter.
Syntax of the point parameter name is as following.

■
■Tagname
The format of point parameter name on the point which has tagname is “Tagname.Parameter
Name”.
Tagname is following format.
•• Up to 16 characters
•• A to Z, 0 to 9 and underscore character
•• Following tagnames are not available
– numbers-only tagname
– underscore cannot follow another underscore
– Begining or end of the tagname is underscore character
– ‘xxxBOXyyy’ (xxx:Node yype, yyy:Node number) format tagname
•• Not case sensitive

■
■Hardware reference address
The format of point parameter names that is on the controller which has the connected point
is “Hardware reference address.Parameter name”.
Hardware reference address is following format.
!TTmmmSss
TT : AI/AO/DI/DO/VI/VO/FF
mmm : Module number
S : Fixed string
ss : Slot number

■
■Box data point
The format of point parameter names that is in the BOX variable is “Box data point.Parameter
name”.
Box data point is following format.
•• !BOX (point on the same controller)
•• $DNyyy or $HNyyy (point on another controller) [R411 or later]
– yyy:Node number
And following parameters are available.
•• FL(ffff)
•• NN(ffff)
•• TMCMD(ttt), TMPV(ttt), TMRV(ttt), TMSO(ttt), TMSP(ttt), TMSP(ttt), TMTB(ttt)
•• TMFORMAT(ddd) [R411 or later]

− 143 −
Chapter 5. RTC Parts

5.2.6 Logic Component Parts

5.2.6.1 How To Design and Implement Logic
RTC provides logic function by using Logic Component Parts.
Logic engineering consists of two phases: a phase for designing logic designs and a phase for
defining the points for implementing this logic. “Logic Parts” and “Point Parts” that comply
with each of these phases are provided.

•• “Logic Component Parts” are provided to support block algorithms. Logic Component
Parts are provided to graphically represent logical operations on the sheet.
•• Logic Point Parts correspond to the Logic Points of Controllers and comprise the step for
executing Logic Component Parts.

■
■Types of Logic Component Part

Table 5-22. Logic Component Parts

Type of Logic Component Parts Contents

Logic Algorithm Part 26 algorithms including AND, OR, Flipflop, WDT, etc.
Logic Numeric Part Up to four Real-type variables
Logic Flag Part Up to 12 Boolean-type variables.
Logic Connection Part Logic input/output connection
Logic Gateway Part Logic gateway

Logic is defined using the following procedure.

Step 1 Allocate the Logic Component Parts to the Sheet and configure the logic.

Step 2 Allocate the Logic Point Parts to the Sheet.

Step 3 In order to specify at which Logic Point the logic action described with the Logic
Component Parts should be executed, the Tag Name of the Logic Point should be
set (mapping) in the Logic Component Parts.

Step 4 When the [Implementation] → [Create PDB...] commands are executed, the logic
design information used in the Logic Component Parts is reflected in the param-
eter setting of the mapped Logic Point Parts.

− 144 −
 5.2 Control Parts

5.2.6.2 Logic made into Parts

When logic functions are designed, the RTC Editor allows you to separately consider the
design from the logical aspect of how the logic should appear and from the physical aspect
of at which Logic Point it should be realized. In other words, the former is indicated by Logic
Component Parts, and the latter by Logic Point Parts.

Logic is made into Parts by combining it with Logic Component Parts and other Control
Parts (Point Parts, CL Parts). These Control Parts will make the logic into Parts by the use of
Containers.
When Control Functions using these Parts should be realized, parts can be installed by speci-
fying appropriate Logic Point Parts as the mapping destinations of the Logic Component Parts
in the Parts.

Specify TAGNAME of hosting Logic

Container of a Point Object
Logic Strategy LOGIC
LG101

Open

LOGIC(XOR)
LG101

LOGIC(AND)
LG101

LOGIC(OR)
LG101

Figure 5-7.

5.2.6.3 Logic Point Parts

Logic Point Parts correspond to Logic Points. The two methods of registering algorithms for
these Points are described below.

Step Select Logic Component Parts, specify Mapping.

Step Select the [Properties] property sheet for Logic Point Parts, set parameters.

Note •• Logic Point Parts do not have Ports.

•• Even if you enter the destination of parameter connection in [Properties] for a
Logic Point Part, the entered value is overwritten at the time of Point generation
if the Logic Point Part is specified for mapping from a Logic Component Part.

− 145 −
Chapter 5. RTC Parts

5.2.6.4 Logic Component Parts

The RTC Editor is provided with Logic Component Parts corresponding to the algorithms
that Logic Points have.
Logic Component Parts must be mapped in Logic Points. When multiple Logic Component
Parts should be executed as the same Logic Point, the same Tag Name should be set as the
mapping destination.

Interlock1
Specify the same Logic
LOGIC(GT)
Point Object
LG101 Interlock Interlock
LOGIC(OR) LOGIC
LG101 LG101
Interlock2
LOGIC(LE)
LG101

Figure 5-8.

■
■Appearance of Logic Component Part
In addition to the Default View, Logic Component Parts can also have Custom View for each
Part type (not for each algorithm) and Class View.
The default view of the Logic Component Part is shown below.

Interlock Logical Tag Name

LOGIC(AND) Object Type
LOG101 TAG NAME of the host Logic Point Object

Figure 5-9.

− 146 −
 5.2 Control Parts

■
■Logic Component Parts List
The Table are lists of Part Type and Ports.

Table 5-23. Logic Component Parts List

Logic Connection Part Type on default

Part Type Input Port Output Port
Part view
NULL LOGIC(ALGO)
AND LOGIC(AND) S1, S2, S3 SO
OR LOGIC(OR) S1, S2, S3 SO
NOT LOGIC(NOT) S1 SO
NAND LOGIC(NAND) S1, S2, S3 SO
NOR LOGIC(NOR) S1, S2, S3 SO
XOR LOGIC(XOR) S1, S2 SO
QOR2 LOGIC(QOR2) S1, S2, S3, S4 SO
QOR3 LOGIC(QOR3) S1, S2, S3, S4 SO
SWITCH LOGIC(SWITCH) S1, S2, S3 SO
EQ LOGIC(EQ) R1, R2 SO
NE LOGIC(NE) R1, R2 SO
GT LOGIC(GT) R1, R2 SO
Logic Algorithm Part
GE LOGIC(GE) R1, R2 SO
LT LOGIC(LT) R1, R2 SO
LE LOGIC(LE) R1, R2 SO
CHECKBAD LOGIC(CHECKBAD) R1 SO
PULSE LOGIC(PULSE) S1 SO
MAXPULSE LOGIC(MAXPULSE) S1 SO
MINPULSE LOGIC(MINPULSE) S1 SO
DELAY LOGIC(DELAY) S1 SO
ONDLY LOGIC(ONDLY) S1 SO
OFFDLY LOGIC(OFFDLY) S1 SO
WATCHDOG LOGIC(WATCHDOG) S1 SO
FLIPFLOP LOGIC(FLIPFLOP) S1, S2, S3 SO
CHDETECT LOGIC(CHDETECT) S1, S2, S3 SO
Before specifying index
Logic Numeric Part LOGIC(NUMERIC) NN
After specifying index n (can be either of input or output)
LOGIC:NN(n)
Before specifying index
LOGIC(FLAG) FL
Logic Flag Part
After specifying index n (can be either of input or output)
LOGIC:FL(n)
Logic Component Part LOGIC(CONNECT) LISRC LODSTN
Logic Gateway Part LOGIC(GATEWAY) LISRC, LOENBL LODSTN

Note You cannot add or delete Ports for Logic Component Parts.

− 147 −
Chapter 5. RTC Parts

■
■Logic Algorithm Part
Logic Algorithm Part represent 26 algorithms of the Logic data point. See “Control Parts
Function Manual” for more information on algorithms.
If you leave Ports unconnected, default values are set for the corresponding parameters.

Default inputs are set for input ports that are not connected to other Parts. When two Logic
Algorithm Parts are linked with each other, and both Parts specify the same Logic Point, the
link connection will be made inside the same Logic Point.
In other cases (when two Logic Algorithm Parts are connected with each other, but they
specify different points, and when linked to different Point Parts), the link connection will be
outside the Point.
Logic Algorithm Parts provide the following setting items on the Properties sheet.

Double-clicking a fixed character string in the Properties sheet concerning a Logic Algorithm
Part where a parameter name is displayed will open the [Parameter Reference] window, where
the explanations on the parameter will be displayed. For more details of Parameter References,
see 2.4.1, “Parameter Reference.”

Table 5-24. Items on the Properties sheet

Control Description
Logical Tag Name UnNamed??? by default
TAG NAME Specify the TAG NAME of the host Logic Point Part
Choose one from following algorithms
NULL, AND, OR, NOT, NAND, NOR, XOR, QOR2,
Block Algorithm QOR3,SWITCH, EQ, NE, GT, GE, LT, LE, CHECKBAD,
PULSE, MAXPULSE, MINPULSE, DELAY, ONDLY,
OFFDLY, WATCHDOG, FLIPFLOP, CHDETECT
Logic Block Number Specify the setting method (AUTO/MANUAL) of a Logic
Indication Block Number
Logic Block Number Specify/display a Logic Block Number
Deadband is valid only when EQ, NE, GT, GE, LT or LE is
Deadband
chosen for the Algorithm
Delay Time is valid only when PULSE, MAXPULSE,
MINPULSE, ONDLY, OFFDLY or WATCHDOG is chosen
Delay Time for Algorithm
(A real value can be set, however, it will be regarded as an in-
teger (rounded to the nearest integer) in the controller)
Function for inverting the
Displayed only in the case of AND, OR, NOR, NAND
status input

− 148 −
 5.2 Control Parts

■
■How to Set Logic Block Numbers
•• First, “Logic Block Number” corresponds to “N” in the “LOGALGID(N)” parameter of
Logic Points. On the property sheets of Logic Algorithm Parts, you can set a Logic Block
Number for each Part.

•• Whether Logic Block Numbers should be set manually or automatically is specified by the
“Logic Block Number Indication” parameter. You can choose between the two:

AUTO : You do not set Logic Block Numbers. At the time of Point generation, RTC auto-
matically sets Logic Block Numbers. (Default)
MANUAL : To manually set Logic Block Numbers, specify MANUAL. As Logic Block
Numbers, set numbers 1 to 16.

•• It is all right if there are both AUTO-specified Parts and MANUAL-specified Parts between
Logic Component Parts of the same Tag Name.

•• You can enter discrete numbers as Logic Block Numbers.

•• Logic Block Numbers set in MANUAL in point generation processing are treated as re-
served numbers (fixed numbers) and are not altered. Parts specified in AUTO are assigned
Logic Block Numbers beginning with “1.” If such a number coincides with a number already
set in MANUAL, the next number is assigned.

LG01 LG01 LG01

AUTO AUTO AUTO
No.0 No.0 LG01 LG01 No.0
MANUAL MANUAL
No.1 No.2

after point generation processing

LG01 LG01 LG01

AUTO AUTO AUTO
No.3 No.4 LG01 LG01 No.5
MANUAL MANUAL
No.1 No.2

Figure 5-10.

•• The order in which Logic Block Numbers are assigned to Parts specified in AUTO is the
order in which the Parts have been placed on the Sheets.

•• When Jobs of RTC before the addition of the function for manually setting Logic Block
Numbers are read, they are all treated as “AUTO.” As their Logic Block Numbers, the values
set for the previous Jobs are used as they are. Therefore, when a Job has been read, it can be
used as it is, and you do not need to do anything in particular.

− 149 −
Chapter 5. RTC Parts

■
■Reversal display of the port
•• The ports are displayed according to the setting of the status input reversal function
(S1REV(N) _ S3REV(N) parameter) as shown in below figure.
Figure 5-11 shows the case that the value of S2REV(N) is “ON”. In this case, the inside of
the S2 port is displayed with white.

•• Reversal display is done even in RTC runtime, but it is displayed according to the value of
the part which is set in RTC Editor.
S1
S2 LOGIC(AND) SO
S3
LG01

Figure 5-11.

■
■Logic Numeric Part
Logic Numeric Part represent local numeric variables inside the Logic data point. Up to four
numeric variables are allowed; NN(1) - NN(4).
Logic Numeric Part provide the following setting items on the Properties sheet.

Table 5-25. Items on the Properties sheet

Control Description
Logical Tag Name UnNamed??? by default
TAG NAME Specify the TAG NAME of the host Logic Point Part
Index number of the numeric variable Type a number rang-
Index
ing from 1 to 4
Value Type any real-type value

Link connection of numeric variable parts within the same logic point needs to satisfy the
condition that parameter types are the same. Connection with a parameter at a point except
for the logic points requires the parameter to be linked to have a connection attribute.

■
■Logic Flag Part
Logic Flag Part represent local Boolean variables inside the logic data point. There are 12 flags
within a Logic data point. First six flags, FL(1) - FL(6), are used by the system, and second six
flags, FL(7) - FL(12), are for use by system developers.
Logic Flag Part provide the following setting items on the Properties sheet.

Table 5-26. Items on the Properties sheet

Control Description
Logical Tag Name UnNamed??? by default
TAG NAME Specify the TAG NAME of the host Logic Point Part
Index Type in number ranging from 1 to 12
Value Choose On or Off Valid only when the value of Index is 7-12

− 150 −
 5.2 Control Parts

Link connection of flag variable parts within the same logic point needs to satisfy the condi-
tion that parameter types are the same. Connection with a parameter at a point except for the
logic points requires the parameter to be linked to have a connection attribute.

Note In cases in which Logic Numeric Parts and Logic Flag Parts are linkconnected to pa-
rameters at other points and in which parameters for the connection of Logic Points
are used, the I/O attribute of the link destination parameter is checked to decide
which to use: LISRC(n) or LODSTN(n).
If the attribute is such that the link destination parameter can be both input and
output, the input connection (LISRC(n)) is used by default.
To use the output connection for linking, perform link connection via a Connection
Part of the same logic in-between.

■
■Logic Connection Part
Logic Connection Part represent input/output connection function of the Logic data point.

LOSRC(n) ="L(m)"
LISRC(m) LODSTN(n)
L(m)

LOENBL(n) ="FL(2)" (Always ON)

Figure 5-12.
Logic Connection Part provide the following setting items on the Properties sheet.

Table 5-27. Items on the Properties sheet

Control Description
Logical Tag Name UnNamed??? by default
TAG NAME Specify the TAG NAME of the host Logic Point Part

■
■Logic Gateway Part
Logic Gateway Part represent Contact Cutout function of the Logic data point..

LOSRC(n) ="L(m)"
LISRC(m) LODSTN(n)
L(m)

LOENBL(n)

Figure 5-13.

− 151 −
Chapter 5. RTC Parts

Logic Gateway Part provide the following setting items on the Properties sheet.

Table 5-28. Items on the Properties sheet

Control Description
Logical Tag Name UnNamed??? by default
TAG NAME Specify the TAG NAME of the host Logic Point Part

When Input Port LOENBL is connected within a Logic data point, the Port on the other end
must be FL1..FL12 of Logic Flag Part or SO Port of the Logic Algorithm Part.
Logic Gateway Part uses L1..L12 parameters of the Logic Point Part to express connection.

5.2.7 Block Parts

Block Parts are parts corresponding to the XPC, PL2, FLC, FC and PC4 [R411 or later] control-
ler’s blocks. Specifications and operations of Block Parts are explained in the following.

■
■When Block Parts Only Are Applied
In addition to the Default View, Block Parts can have the Class View and Customer View. See
the separate sections for description of Class View and Customer View.
The appearance of the Default View of Block Parts is as follows.

Block Type

0003 Low-order 4 characters of

Block Name

Figure 5-14.

After activating the sheet, the display of the lower section can be switched by selecting [View]
[Block Display Change] from the menu and then selecting the [Block Name], [Block Number]
and [Calculate Order].

− 152 −
 5.2 Control Parts

■
■Block Part Types
Following Table shows the Blocks available in the Control Parts Bar (Block).

Table 5-29. Block Parts Types

Block Identifier Algorithm

ADD Addition
SUB Subtraction
MUL Multiplication
DIV Division
MOD Modulo
SUM 4-point addition
DADD Digital addition
ABS Absolute value
SQR Square
SQRT Square root
LN Natural logarithm
LOG Common logarithm
EXP Exponent eX
EXPT Exponent Xy
SIN Sine
COS Cosine
TAN Tangent
ATAN Anti-tangent
TRUNC Truncate
ROUND Round off
MAX Maximum value
MIN Minimum value
AVG Average value
HSE High selector
LSE Low selector
MID3 Middle-of-three
SW Switch
SFT Soft Switch
ALSW Alternate switch
HLM High limit
LLM Low limit
DRL Deviation rate limiter
HMS High monitor
LMS Low monitor
DRM Deviation rate monitor
DMS Deviation monitor
NUMCHK Normal detection
BADCHK Abnormality detection

− 153 −
Chapter 5. RTC Parts

Block Identifier Algorithm

INFCHK Infinity detection
QLTCHK Change detection 1
CHGCHK Change detection 2
PTE EU value conversion
ETP % change
FUNC Function conversion
AND Logical product
OR Logical sum
NOT Reversal
NAND Inverted AND
NOR Inverted OR
XOR Exclusive OR
QOR2 Qualified OR with 2 inputs ON
SR Set
RS Reset
EQ Compare equal with deadband
NE Compare not equal with deadband
GT Compare greater than with deadband
GE Compare greater than or equal to with deadband
LT Compare less than with deadband
LE Compare less than or equal to with deadband
FIXPLS Fixed-length pulse
MAXPLS Pulse with maximum time limit
MINPLS Pulse with minimum time limit
CYCPLS Timer
WDT Watchdog timer
DELAY Delay
ONDLY On delay
OFFDLY Off delay
UCNT Up-counter
DCNT Down-counter
AAV Analog integration
PAV Pulse addition
PID PID calculation
PRO Comparison
INT Integration
DIF Differentiation
LDLG Lead lag
DED Deadtime
TF Filtering time
RMP Ramp

− 154 −
 5.2 Control Parts

Block Identifier Algorithm

MAV Moving-average
ANMA Analog memory
GW Gateway
CONV Data conversion
SG Acceleration PV
FL Flag signal
DLTPV delta PV
TIMFL One-shot FL
ANDIN4 4-input AND operation
ORIN4 4-input OR operation
PSQRT % Square
REDTAG Read Tag

■
■Block Parts [Properties] Property Sheet
On the Block Parts [Properties] property sheet you can set various parameter values under
the block name. For the parameter types and setting ranges, see the Controller specifications.
The caption of the Block Parts [Properties] property sheet is “Block Identifier- Configuration
Sheet”.

− 155 −
Chapter 5. RTC Parts

■
■Contents of the Block Parts [Properties] Property Sheet

Table 5-30. Contents of the Block Parts [Properties] Property Sheet

Controller Contents
For display and modification of the Block Name.
At the time when the Part is placed on the Sheet, the Block Name is
automatically set to a default name so that it will be unique within
the system.
However, if you want to change the default Block Name, or if the
Block Name is duplicated by copy and paste of Parts, etc., the Block
Name must be changed from the property settings, etc.
The Block Name, including the Tag Name, must be unique within the
system. Set the Block Name adhering to the following rules, as in the
case of Point Tag Name:
Must be within 16 characters and should start with an alphanumeric
Block Name
character. Alphanumeric and underscore characters can be used from
the second character onward.

However, the following cannot be used as a block name:

•• A character string consisting of only numerical characters
•• A character string including consecutive underscore characters
•• A character string ending with an underscore character
•• A character string starting with “Z#” or “Z$”
•• “xxxBOXyyy” (xxx:Node Type, yyy:Node Number)
Even when lower-case letters are entered, the corresponding upper-
case letters will appear when they are displayed.
Node Type Only selectable for XPC, PL2, FLC, FC and PC4 [R411 or later]
Node Number Set as an integer between 1 and 126
Set the slot number of the FB Point that the Block belongs to. Also,
if specification of [System Configuration] FB Point is performed, the
FB Slot Number slot number of the specified FB Point is set.
1-511 : XPC/PL2/FC/PC4 [R411 or later]
1-128 : FLC
Mode for setting the Block Number and operation sequence in point
Function Block Indication
generation. For details, refer to 6.1.5, “Point Generation.”
A “Block Number” for identifying the block inside the FB Point.
1-8191 : XPC/PL2/FC/PC4 [R411 or later]
Function Block Number 1-2048 : FLC
(The indication on the Properties sheet is “Function Block Number.”
It is described under the term “Block Number” in the User’s Guide)
The Block Number of the Block to be processed next inside the
Next Processing Block
Controller. The number is decided from the value of the “Order of
Number
Block” parameter at the time the point is created.
Indicates the order of the block for processing inside the FB Point of
the Controller.
1-8191 : XPC/PL2/FC/PC4 [R411 or later]
1-2048 : FLC
Order of Block
However, if “Auto Order Option” is enabled at the time when the
point is created, the order of block is automatically decided in accor-
dance with the connection relations between blocks.
For details, refer to 6.1.5, “Point Generation.”

Other parameters than those described above become Block Type-specific parameters. For
details, see the parameter references for each block.

− 156 −
 5.2 Control Parts

■
■Block Names
• When a Block Part is placed on the Sheet from the Parts Bar, it is given a default Block Name.
To ensure that the Block Name is unique within the system, the name is decided according to
the following rules:

ttttttjjssssbbbb
tttttt : Identifier indicating the Block Type.
jj : Job Number. 00 – 99.
ssss : ID for identifying the Sheet inside the Job. 0001 - .
bbbb : ID for identifying the Part inside the Job. 0001 - .

•• However, if the Block Name is later modified by the property settings and copy & paste of
Parts, the default Block Name set at the time the part was placed on the sheet may no longer
necessarily be unique within the system.

•• In the following sections of the rtcedit.ini file, you can switch whether, when a Block Part
has been pasted, a new Block Name should be set for the pasted Block Part or the Block
Name should be kept unchanged. The new setup in rtcedit.ini file becomes valid after the
RTC Editor is started up again.

[Block]
RenameBlockAtPaste = TRUE
; TRUE: A new Block Name is set as the Block Name of the pasted Block Part.
This is the default value.
; FALSE: The copy source Block Name is set as the Block Name of the pasted Block Part.

•• The Block Name, including the Tag Name of the Point, must be unique within the system.

■
■Rules For Linking Block Parts
•• The rules for linking between Block Parts are as follows:

Rule 1 Connection between data types with different parameters is not possible.(However,
CONV Blocks are excluded from this rule.)
• Following Table shows connection rules related to I/O types.

Table 5-31.

Parameter 1 Parameter 2 Linkable (Unlinkable)

Input (Port color: Red) –
Input (Port color: Red) Input and output (Port color: Pink) ✓
Output (Port color: Blue) ✓
Input (Port color: Red) ✓
Input and output (Port color: Pink) Input and output (Port color: Pink) –
Output (Port color: Blue) ✓
Input (Port color: Red) ✓
Output (Port color: Blue) Input and output (Port color: Pink) ✓
Output (Port color: Blue) –

Rule 2 Multiple links cannot be drawn to Input Ports.

− 157 −
Chapter 5. RTC Parts

Table 5-32. Rules for Linking Between Block Parts and Point Parts

Block Parameters Connectable Point Parts Parameters

Port Other DI/DO/ Parameter
Block Type Point Type Data Type
Name Conditions FFFB Type Name
BOXNM -- PV Float
AI -- PV Float
VALIN -- PV Float
FFFB FF_AI PV Float
LNKDTTYP =
FFFB FF_AO SP Float
S_P_REAL
FFFB FF_AO OP Float
FFFB FF_AO PV Float
FFFB FF_MAI MPV(1)~(8) Float
FFFB FF_MAO MOP(1)~(8) Float
C1
BOXFL -- PVFL Boolean
DI -- PVFL Boolean
DO STATUS SO Boolean
FFFB FF_DI PVFL Boolean
LNKDTTYP =
FFFB FF_DO DSP Boolean
BOOLEAN
FFFB FF_DO PVFL Boolean
GW
FFFB FF_DO SO Boolean
FFFB FF_MDI MPVFL(1)~(8) Boolean
FFFB FF_MDO MSO(1)~(8) Boolean
BOXNM -- PV Float
AO -- OP Float
DO STATUS ONPULSE Float

LNKDTTYP = DO STATUS OFFPULSE Float

S_P_REAL DO PWM OP Float
VALOUT -- OP Float
OP
FFFB FF_AO SP Float
FFFB FF_MAO MOP(1)~(8) Float
BOXFL -- PVFL Boolean

LNKDTTYP = DO STATUS SO Boolean

BOOLEAN FFFB FF_DO DSP Boolean
FFFB FF_MDO MSO(1)~(8) Boolean

− 158 −
 5.2 Control Parts

Block Parameters Connectable Point Parts Parameters

Port Other DI/DO/ Parameter
Block Type Point Type Data Type
Name Conditions FFFB Type Name
BOXNM -- PV Float
BOXFL -- PVFL Boolean
AI -- PV Float
DI -- PVFL Boolean
DI ACCUM AV Int
DO STATUS SO Boolean
VALIN -- PV Float
FFFB FF_AI PV Float
FFFB FF_AO SP Float
C1 -- FFFB FF_AO OP Float
FFFB FF_AO PV Float
FFFB FF_DI PVFL Boolean
FFFB FF_DO DSP Boolean
FFFB FF_DO PVFL Boolean
FFFB FF_DO SO Boolean
CONV FFFB FF_MAI MPV(1)~(8) Float
FFFB FF_MDI MPVFL(1)~(8) Boolean
FFFB FF_MDO MSO(1)~(8) Boolean
FFFB FF_MAO MOP(1)~(8) Float
BOXNM -- PV Float
BOXFL -- PVFL Boolean
AO -- OP Float
DO STATUS SO Boolean
DO STATUS ONPULSE Float
DO STATUS OFFPULSE Float
OP --
DO PWM OP Float
VALOUT -- OP Float
FFFB FF_AO SP Float
FFFB FF_DO DSP Boolean
FFFB FF_MAO MOP(1)~(8) Float
FFFB FF_MDO MSO(1)~(8) Boolean

− 159 −
Chapter 5. RTC Parts

Block Parameters Connectable Point Parts Parameters

Port Other DI/DO/ Parameter
Block Type Point Type Data Type
Name Conditions FFFB Type Name
BOXNM -- PV Float
AI -- PV Float
VALIN -- PV Float
FFFB FF_AI PV Float
P1 - P4 -- FFFB FF_AO SP Float
FFFB FF_AO OP Float
FFFB FF_AO PV Float
FFFB FF_MAI MPV(1)~(8) Float
FFFB FF_MAO MOP(1)~(8) Float
BOXFL -- PVFL Boolean
DI -- PVFL Boolean
DO STATUS SO Boolean
FFFB FF_DI PVFL Boolean
S1 - S4 -- FFFB FF_DO DSP Boolean

Other Block FFFB FF_DO PVFL Boolean

Type FFFB FF_DO SO Boolean
FFFB FF_MDI MPVFL(1)~(8) Boolean
FFFB FF_MDO MSO(1)~(8) Boolean
BOXNM -- PV Float
AO -- OP Float
DO STATUS ONPULSE Float
DO STATUS OFFPULSE Float
OP --
DO PWM OP Float
VALOUT -- OP Float
FFFB FF_AO SP Float
FFFB FF_MAO MOP(1)~(8) Float
BOXFL -- PVFL Boolean
DO STATUS SO Boolean
SO --
FFFB FF_DO DSP Boolean
FFFB FF_MDO MSO(1)~(8) Boolean

Note: “--” in the diagram indicates “not specified”.

Rule 3 Connection is mandatory for parameters of which Ports are displayed by default, ex-
cept the following:
• Connection is not mandatory for parameters of the SG, FL, and REDTAG Blocks.
• Connection is not mandatory for input parameters of the ANDIN4, ORIN4, and TIMFL
Blocks.
If a parameter for which connection is mandatory is not connected, it is checked as an
error in point generation.

Rule 4 Block Parts cannot be connected with Parts at other nodes.

− 160 −
 5.2 Control Parts

■
■CONV Parts
•• CONV Blocks are for converting the Data Type of input parameters to another Data Type.

•• CONV Blocks can input the following Data Types:

Boolean, Real, Integer, Enumeration

•• If a CONV Block is directly connected to another CONV Block, the type of parameteriza-
tion between CONV and CONV automatically becomes Float.

5.2.8 Block Secondary Parts

5.2.8.1 BOX Parameter Parts
•• BOX Parameter Parts are parts for referencing the XPC, PL2, FLC, FC, PC4 [R411 or later]
and HL BOX parameters as block diagrams.

•• BOX Parameter Parts appear in the parts format shown to the left in the following diagram.
BADIOMRD(34)
XPCBOX010.BADIOMRD(34)
AND
BOX Parameter Parts
0003

Figure 5-15.

•• In the property settings dialog displayed by double-clicking the Parts you can specify the
“Node Number”, “Parameter Name”, and Index in the case of array types, of the parameter
of the BOX that you want to reference.

•• The parameters that can be specified are the following XPC, PL2, FLC, FC, PC4 [R411 or
later] and HL parameters.

Table 5-33.

Parameter Name Data Type Node Type Index Range Meaning

XPC 1 - 120
PL2 1 - 240
BADIOMST Boolean FLC 1 - 24 Abnormal IOM state
FC 1 - 120
PC4 [R411 or later] 1 - 120
XPC 1 - 120
PL2 1 - 240
Abnormal redundancy
BADIOMRD Boolean FLC 1 - 24
IOM state
FC 1 - 120
PC4 [R411 or later] 1 - 120
XPC
PL2
None Time-
TSAVAIL Boolean FLC
synchronized status
FC
PC4 [R411 or later]

− 161 −
Chapter 5. RTC Parts

Parameter Name Data Type Node Type Index Range Meaning

XPC
PL2
YEAR Float FLC Internal time year
FC
PC4 [R411 or later]
XPC
PL2
MONTH Float FLC Internal time month
FC
PC4 [R411 or later]
XPC
PL2
DAY Float FLC Internal time day
FC
PC4 [R411 or later]
XPC
PL2
HOUR Float FLC Internal time hour
FC
PC4 [R411 or later]
XPC
PL2
MINUTE Float FLC Internal time minute
FC
PC4 [R411 or later]
XPC
PL2
SECOND Float FLC Internal time second
FC
PC4 [R411 or later]
NN_0 Float HL 1 - 5120 Status of process values
NN_1 Float HL 1 - 5120 Process value
NN_2 Float HL 1 - 5120 Process value
NN_3 Float HL 1 - 5120 Process value
NN_4 Float HL 1 - 5120 Process value
NN_5 Float HL 1 - 5120 Process value
NN_6 Float HL 1 - 5120 Process value
NN_7 Float HL 1 - 5120 Process value
NN_8 Float HL 1 - 5120 Process value

− 162 −
 5.2 Control Parts

•• Link connection with Box Parameter Parts can be made only with the following parameters.

Table 5-34.

Node Type Connectable Parameter

XPC •• C1 and OP parameters of GW/CONV blocks
PL2 •• P1 ~ P4, S1 ~ S4, OP, SO parameters of blocks except GW/
FLC CONV blocks
FC The data type of the parameter must match the data type of BOX
PC4 [R411 or later] parameter.
HL •• Paramters of Logic point on XPC/PL2/FC/PC4 [R411 or later]

5.2.8.2 Frame Parts

Frame Parts are the parts for the operation screen (frame) on the RTC sheet. When using
frames on the RTC sheet, create the frame parts of frame types for the operation screen created
in the screen creation environment (InTouch) and then input the data.

■
■Definition of Frame Type
For the Frame Type definition, there are parameter definitions specified for the operation
screen created in the screen creation environment (InTouch) and definitions specified regard-
ing the CSV file output. The Frame Type definition is stored in the Frame Type Definition
Data File (frametyp.dat).

Note If frame types other than “Undefined” cannot be selected in the Property Sheet or
“?” is displayed for the Frame Parts, confirm the following:
•• frametyp.dat is copied to the directory “C:\Sysdir\RTC\frmdata\.”
•• “Frame TypeDirectory = C:\Sysdir\RTC\frmdata\” is written to the [Frame Part] of
rtcedit.ini.

■
■Creation of Frame Parts
Frame Parts are created in the same manner as the creation of ordinary RTC Parts by clicking
the [Frame Parts] button on the Control Parts Bar (Block) and then clicking the target sheet.
The Frame Type Name (when the name of Frame Type for the display of Frame Parts is de-
fined) and the value of the Parts Name parameter defined for the Frame Type are displayed on
the upper and lower sections of the Frame Parts respectively.

Note For Frame Parts, the Configuration View or Custom View cannot be set.

− 163 −
Chapter 5. RTC Parts

■
■Specification of Frame Type
Select a Frame Part and select [Property Setting] or double click the Frame Part. Then the
[Frame Parts] property sheet appears. Select a Frame Type from the <Frame Type> selection
list displayed at the beginning of the property sheet. All of the defined Frame Types are dis-
played on the <Frame Type> selection list.
As Frame Types are selected, defined parameters are displayed on the property sheet.
When ports are defined, clicking the <OK> button displays the ports on the parts of the sheet.
It is also possible to change the already defined Frame Types. However, “No Specification”
cannot be selected for that. Also, when ports and the links already exist, reconfiguration is
needed if necessary since all of the links are deleted by the change.

■
■Setting of Parameters
Select a Frame Part, right-click the mouse and select [Property Setting] from the menu, or
double click a Frame Part. Then the [Frame Parts] property sheet appears. Set the parameters
for the Frame Parts on the property sheet. The same name cannot be applied for the Parts
Name parameters twice or more in the same job, and different names must be applied for
each Part. Duplication of Parts Name parameters can be checked by using [Frame Parts Name
Integrity Check].
If the configuration of Frame Parts is changed, run the [Create System Data Files] before start-
ing the Harmonas-DEO system.

■
■Parameter Connection
There are two kinds of Frame Parts parameter port: Input and Output. The following param-
eters can be connected to each type of the port.

Table 5-35.

Input/Output Connectable parameters

Block Parts parameter (Input or Input/Output)
PV parameter of BOXNM point
PVFL parameter of BOXFL point
Input PV parameter of AI point
PVFL parameter of DI point
AV parameter of DI point (ACCUM)
SO parameter of DO point (STATUS)
FP parameter of SG block
FS parameter of FL block

Output FS parameter of TIMFL block

FP parameter of REDTAG block
(Connectable only when the Frame Parts parameter
is “With Read Tag Specification”)

•• Connection is not possible when the destination parameter has a different data type.
•• Connection through the Intersheet Parts or Intrasheet Parts is possible. However, connec-
tion to the Job Parts is not possible.

− 164 −
 5.2 Control Parts

■
■Frame Parts Name Integrity Check
Selecting [Create System Data File] will execute the integrity check for Frame Parts names.
Error will report as following case:
•• Frame Type not define.
•• Frame Type definition read error.
•• Frame Parts name is empty.
•• Frame Parts name is not unique.
Frame Parts name is a value of Name Parameter on the Frame Type.
Frame Parts name appears on Frame Parts.

5.2.9 CL Programs
CL Parts are not always necessary for handling CL programs. CL Parts have following
functions.
•• CL replacement
•• Synthesizing CL
•• Generic CL

■
■Terminology
•• CL parts and Process Module Data Point parts
These are included in the control parts and can be added to the sheets.

•• CL source files
These are text files containing source CL programs. “CL source” may be used instead of “CL
source file.” CL parts to be used can be generated from the template CL source provided for
the CL parts.

•• Template CL files
These are the CL source files that contain macros and aliases generated by text editors,
PADET/CL, etc. These CL source files cannot be compiled. Therefore, import them to the
CL parts when using them.

•• Template CL sources
These are data stored in the CL parts. When a template CL file is imported, the data is dis-
played in the property sheet for the CL parts.

− 165 −
Chapter 5. RTC Parts

5.2.9.1 Advantages of Managing CL Parts with RTC Editor

Management of CL programs with RTC Editor has the following characteristics:

■ sources for the same logic can be generated efficiently by performing CL replace-
■CL
ment operations.
When generating two or more CL sources for the same logic whose data is only partially dif-
ferent with each other, for example, only the point names being different, describe the logic as
a template CL source and provide Replace lists for the portions of the CL sources where they
differ with each other. Then the CL sources can be generated collectively, reducing the amount
of work for generating the CL sources and for testing the programs.

■
■Sequence slots can be used efficiently by synthesizing multiple CL sources.
There are cases in which multiple CL sources of the same type should be combined and run at
a single process module data point in order to efficiently use sequence slots.
To meet this need, a function is provided for combining CL sources when CL source files are
to be created from CL Parts. When, in one Job, multiple CL Parts specify the same process
module data point as a binding destination, the CL source file created from those CL Parts is
a combination of the CL sources created from the CL Parts.
For example, when Sheet A and Sheet B in the same Job each have one CL Part that has the
same process module data point tag name as a binding destination, the CL sources created
from the CL Parts are combined into a single CL source file. The CL Program combining
method can be specified by using the CL source editing macro (refer to 5.2.9.6).
Sheet A
SEQUENCE FlowControl (HC; POINT @)
TankLevel A Flow Control 1
AI CL EXTERNAL @TankLevelA
EXTERNAL @TankLevelB
AI_101 PMDP001 STEP1 :
IF @TankLevelA.PV = 100 THEN
:
Sheet B :
IF @TankLevelB.PV = 100 THEN
TankLevel B Flow Control 2 :
:
AI CL GOTO STEP1
AI_201 PMDP001 END

CL Programs are merged together if their

CL Parts share the same host Process
Module Part.

Figure 5-16.

− 166 −
 5.2 Control Parts

■
■Generic CL Program
Generic CL Programs promote reuse of CL code. CL editing macros, enable you to write tem-
plate CL files without any specific tag names, which are given later by connecting Point Links
or by setting CL Parts’ Properties in property sheet.
Unusing specific tag names makes it easy to reuse CL Parts in another Job, so you need not
rewrite the template CL files. Simply copy the CL Part to your current Job and connect the
Point Link and Set Properties.

■
■Documentation
Prepare usage notes or other descriptive notes in the Description box in property sheet of CL
Part. You can write more detailed information using other applications programs, and embed
this in the Sheet, and so creating portable documentation that is carried around with in the
CL Program.

Note CL Programs can be created by compiling with a text editor instead of using the
RTC Editor, but in this case the created CL Program will become Job-specific. If you
intend to reuse the CL Program, use the RTC Editor.

5.2.9.2 Procedure for Creating CL Programs

■
■Procedure for using CL replacement operations

Step 1 Create a template CL file by using PADET/CL, a text editor or the like.
Place the created template CL file in the “tpl” folder in the job directory.
When PADET/CL 20.3 or its later version is installed to create CL programs,
[Execute PADET] will be displayed as a subcommand of [Implementation] of the
RTC editor.

Step 2 Lay out the process module data point parts in the sheet in the job and assign a tag
name to each of them.

Step 3 Specify the sequence slot size (SEQSLTSZ) parameter value depending on the CL
size. When the value is not enough to load, the CL program cannot be loaded.

Step 4 Place the CL parts in the sheet.

Step 5 Import the template CL file into for the CL parts. On the [Replace] page for CL
parts, click the <Import> button and select the template CL file.

Step 6 Specify a Replace list using one of the following methods. The [Copy All] and
[Paste All] pop-up menus when the right mouse button is clicked on the Replace
list.
•• Enter the list name in [Replacement String] dialog box.
•• Import the list from the CSV file.
•• Copy the list from the Excel sheet and perform a [Paste All] operation.
•• Copy the CSV file from Explorer and perform a [Paste All] operation.

− 167 −
Chapter 5. RTC Parts

Step 7 Create a CL source file. Select from the Replace list the name of the CL file to be
created and click the <CL source creation> button. Then the CL file is created in
the directory, “\{job directory}\CL\.”

Step 8 Compile the CL source file. To make the compilation, activate the “cldo.exe” CL
compiler by the operations of [Implementation] → [Compile/ Load CL]. The ob-
ject, provided with a “.co” extension, is created in the directory where the source is
stored. For CL objects, the “\{job directory}\CO\” directory is provided. When the
compilation is completed normally, the compiled object is copied into this direc-
tory. For compiling CL programs, refer to 5.2.9.8, “Compiling CL Programs.”

Note •• If a large number of alias names and Replacement Strings are registered in the
CL Replace list, some of them may not be displayed. However, all of them are
registered correctly.
•• When a CL Replace list is obtained by loading the exported CSV file into Excel or
by pasting copied CL Replace list data in the Excel sheet, values may be converted
automatically by Excel (for examples: 1.500 → 1.5, 2/3 → February 3). To prevent
these conversions from being made, load the data as character strings.
(For example: Change the cell format for character strings and use “Paste”
operations.)
•• If a large number of alias names are defined, Excel may not be able to load CSV file
data. In such a situation, exchanging the row and column of the CSV file format
can avoid the restriction of Excel.
Specify TRUE for the [CLReplaceListTransposition] key in the [CL] section of the
“rtcedit.ini” file to import/export a Replace list CSV file in the format in which the
Row and column are exchanged.
•• If a large number of CL file or alias names are defined, the performance of the RTC
editor may be degraded significantly.
•• When using the Sequence Execution Status function, all data in long rows may
not be displayed because the CL source display width is fixed. In such a situation,
specify Replacement Strings to reduce row lengths of the CL source after the
replacement operation. For the display width of the Sequence Execution Status
function, refer to the manual concerned.

− 168 −
 5.2 Control Parts

■
■Procedure to use CL-merging operations, external reference of macro and Generic Tag

Step 1 Create a template CL file using PADET/CL or a text editor. Use CL sourceediting
macros instead of job-specific tag names to make the re-using of the file easier.
Place the created template CL file in the “tpl” folder in the job directory. When
PADET/CL 20.3 or a later version is installed to create CL programs, [Execute
PADET] will be displayed as a subcommand of [Implementation] of the RTC
editor.

Step 2 Assign a process module data point part onto a sheet in the job and give it a tag
name.

Step 3 Set a sequence slot size (SEQSLTSZ) parameter value in accordance with the size of
CL. If this parameter value is not enough to load, the CL program cannot be loaded.

Step 4 Place CL part on the sheet.

Step 5 Import the template CL file created in the CL parts.

Click the <Import> button in [Merge page] in the CL parts and select a template
CL file.

Step 6 Bind the process module data point to execute the CL program.
Specify the tag name of the created process module data point part in the [Bound
ProcMod Part] text box in [Merge page] in the CL parts.

Step 7 If the external reference macro &REFn (REFn is an identifier of reference port) or
@logical tag name (logical tag name of port part is linked with reference port) ex-
ists in the template CL source, define the reference port with the CL part and then
make a connection between an appropriate point part and point link.

Step 8 Generate a CL source file. In the [CL Parts Property] properties sheet of the CL
part, click the <Create> button, and then set a CL source file name in the file dialog.
The default storage directory is “\(Job Directory)\CL\.”
This will develop the macro in the template CL source.

Step 9 Compile the CL source file. Select [Implementation], and then click [Compile/
Load CL] to start CL compiler cldo.exe for compilation. The object is created, given
a .co extension, in the directory where the source exists. A directory called “\(Job
Directory)\CO\” is prepared for the CL object. Normal completion of the compila-
tion makes a copy to this directory.
For CL compilation, see Section 5.2.9.8, “Compiling CL Programs.”

Note The CL Part cannot import text files that have been saved in Unicode.
If you write a template CL file using a Note Pad application, save it as a Text File (*.txt)
in the File Type drop-down list (Save As dialog box).
Do not choose Unicode File (*.txt).

− 169 −
Chapter 5. RTC Parts

■
■Reusing CL Programs
•• To reuse a CL program, you must keep the following notes. Gather all necessary Parts in
a single Container Part. Provide Reference Ports on the Container Part to explicitly show
parametric interface. The Container should include:
– One CL Part corresponding to the CL program.
– Point Parts referenced by the CL program
– Point Links between above Point Parts and the CL Part
– Documents

•• Try to create the CL Part in the same Sheet as the referenced Point Parts. Connect Point
Links between them.

•• Make use of Description box in property sheet of the CL Part, and write interface, usage
and function in that box.

Reuse this Container

Measurer Adv Totalizr

Totalizr

Measurer RollOver

Totalizr CL

Figure 5-17.

− 170 −
 5.2 Control Parts

5.2.9.3 Process Module Parts

A Process Module Part represents a sequence slot where one CL program is loaded and exe-
cuted. Each CL program must have its own sequence slot, namely bound Process Module Part.
Process Module Parts can be placed in any Sheet under Job Directory.
Appearance and the behavior of Process Module Part are the same as those of Point Parts. See
previous section for more information.

5.2.9.4 CL Parts
A CL Part makes the engineering task easier, and holds template CL sources.

■
■Appearance of CL Parts
The default view of the CL Part is shown below:

FlowControl Logical Tag Name

CL
PM0001 TAG NAME of the bound Process Module

Figure 5-18.

The CL Part itself does not have TAG NAME parameter on its surface. In the Tag Name slot
of the default view, the TAG NAME of bound Process Module Part will be shown, instead.

■
■Reference Ports on the CL Part
One Reference Port on a CL Part represents one external point reference made by the template
CL source within the CL Part.
In the template CL source, you use CL editing macros to express external points by a Reference
Port Name (&REFn), or by the Logical Tag Name on the other end of the Point Link(@Logical
Tag Name). For example, in the template CL source within PressureCtrl, you need not specify
AI_101, rather specify either “&REF1” or “@Increments”.

Increment s PressureCtrl
Point Link
Analog Inpu t CL

AI_101 PMDP001

Reference Port

Figure 5-19.

− 171 −
Chapter 5. RTC Parts

■
■Procedure to Specify bound Process Module Part

Step 1 Invoke property sheet of CL Part.

Step 2 Type TAG NAME of bound Process Module Part in the bound ProcMod Part box.
Close the property sheet, and the specified TAG NAME will appear in the Tag
Name slot of the CL Part’s default view.
•• The Process Module Part may not exist when you specify its TAG NAME in the
property sheet, but it must be present by the time you preprocess the CL source
file.
•• More than one CL Part can specify the same bound Process Module Part.
If so these specified, CL programs can be merged executed in a single sequence
slot.

■ Properties for a CL Part

■Set
The string “CL Parts property” is shown in the caption bar.

The following pages are provided for the property sheet for the CL parts.
For more information about their functions, refer to 5.2.9.6, “How to Write Template CL Files
(Replace page)” and 5.2.9.7, “How to Write Template CL Files (Merge page).”

Table 5-36. Pages in the [CL Parts Property] property sheet

Page Functions
General Information Specifying logical tag names and descriptions
Replacing character strings with alias names
Replace page
Specifying conditions for output to CL sources using #IFDEF
Generic Tag names (tag name determination using linkage)
Merge page Referencing Parameter Values
Merging CL sources

− 172 −
 5.2 Control Parts

The following contents are provided for each of the pages:

Table 5-37. Contents of the [CL Parts Property] property sheet

Control Contents
The box in which a logical tag name is to be displayed
Logical Tag Name
General and modified
Information Specifications of, restrictions on and use methods of CL
Description
are to be described
Replacement operations are performed for template CL
Replace page Create
sources to be retained and the result is written in a file
Path The path to the template CL file is displayed
The date and time when the template CL file was updated
Modified
is displayed
Contents of the template CL source are displayed in the
Replace page
Contents text format. Here, the template CL source cannot be ed-
(Template CL)
ited directly
The template CL source that has been loaded into the CL
Export
parts is written in a file
Import The template CL file is loaded into the CL parts
CL file names, alias names and replacement strings are
Replace list
displayed in a table format
[Replacement String] dialog (to be described later) is dis-
Add
played, where new items are added to the Replace list
[Replacement String] dialog (to be described later) is dis-
Edit
played, where existing items in the Replace list are edited
Delete Items in the Replace list are deleted
Export The settings made for the Replace list are written in a file
Replace page
(Replace list) Import The settings made for the Replace list are loaded
Select All All items in the Replace list are selected
This is a menu item that pops up when the right mouse
Copy All button is clicked on the Replace list. The contents of the
Replace list are copied onto the clipboard as a text.
This is a menu item that pops up when the right mouse
button is clicked on the Replace list. The text or CSV file
Paste All
that has been copied onto the clipboard is loaded into the
Replace list.
Bound ProcMod Part Enter process module point tag names
The macros of the template CL source to be retained are
Create
Merge page edited and the result is written in a file
An operation to merge CL sources is performed when
Merge
creating a CL source
Path The path to the template CL file is displayed
The date and time when the template CL file was updated
Modified
is displayed
Contents of the template CL source are displayed in the
Merge page
Contents text format Here, the template CL source cannot be ed-
(Template CL)
ited directly
The template CL source that has been loaded into the CL
Export
parts is written in a file
Import The template CL file is loaded into the CL parts

− 173 −
Chapter 5. RTC Parts

■
■Replacement String setting dialog box
This dialog box is for specifying Replace list items.
The box is displayed when the <Add> button on [Replace page] is clicked or when an item
in the Replace list is selected and the <Edit> button is clicked. The following functions are
provided for this dialog box:

Table 5-38. Contents of the [Replacement String] dialog box.

Control Contents
When this box is displayed using the <Add> button, specify a name
for the source file that is to be created from the template CL source.
CL filename
When it is displayed using the <Edit> button, the defined CL file
names are displayed but cannot be edited.
The area for entering an alias name. Enter an alias name to be set in
Alias Name
the alias list.
The area for entering a replacement character string. Enter a replace-
Replacement String
ment character string to be set in the alias list.
The list of alias names and that of replacement character strings are
Alias list
displayed.
The character strings that have been entered in the areas for Alias
Input Name and Replacement String are added to the Alias list, updating
the list.
The replacement character strings for the items selected from the
Delete
Alias list are deleted, being replaced with blanks
Alias Name and Replacement Strings for the items selected from the
Delete Alias Alias list are deleted. The alias names deleted here are also deleted
from the Replace list in [Replace Page].
The CL file name and alias list data are reflected in the Replace list on
OK
[Replace page] and the dialog box is closed
Cancel The data is cancelled and the dialog box is closed

5.2.9.5 CL Source File Creation

■
■Replace page
When an item in the Replace list is selected on the [Replace page] and [Create] is specified,
a replacement operation is performed based on the loaded template CL source and the CL
source file is generated in the CL folder in the job directory.

■
■Merge page
When [Create] is specified on [Merge page], the [Saving with a File Name] dialog box is dis-
played. Specify a path name in the dialog box and click the <OK> button. Then, the CL source
is created in the specified directory. If editing macros (to be described later) are included in
the template CL sources kept in the CL parts, semantic analysis is conducted for the CL source
editing macros to convert them to texts that the CL compiler can recognize.

When the [Merge] check box is clicked and [Create] is specified, all CL sources bound to the
same process module data point are merged.

Note Be sure to specify .cl for CL source extension.

− 174 −
 5.2 Control Parts

5.2.9.6 How to Write Template CL Files (Replace page)

A template CL file is created by a text editor or PADET/CL. The following structure is pro-
vided for enhancing its reusability and for increasing resource use efficiency:

■
■Character string replacement using alias names
•• For a portion in a Replace list for which replacement is to be made, describe a character
string headed by “#” (hereinafter referred to as “alias name”).
•• Use the following rules to give an alias name.
– Use up to 24 characters excluding the “#”.
– The use-prohibited characters and reserved words cannot be used. Refer to Table 5-39,
“Use-prohibited characters and reserved words for alias names.”
– Each of the alias names must not be a subset of another alias name. For example, if
#PARAM1 is defined, #PARAM11 cannot be defined newly. This is because, if the charac-
ter string “#PARAM11” is provided in a template CL source, it is matched with #PARAM1
as well, disabling the judgment of which of the two is to be used for the replacement. In
such a case, use the definition of “#PARAM001” or “#PARAM011” to prevent an alias
name from being duplicated in another alias name.
•• To enter “#” in a template CL source, enter “##” instead. After the replacement is made, “#”
is restored from “##”.
•• Uppercase letters and lowercase letters are recognized as different letters.
Therefore, #POINT and #point are handled as different alias names.

Table 5-39. Use-prohibited characters and reserved words for alias names

Use-prohibited
character/reserved Descriptions
word
, Comma
. Period
+-*/ Addition, subtraction, multiply and division
() Brackets
! Exclamation mark
& Ampersand (and)
$ Dollar sign
% Percent sign
“ Double quotation mark
IFDEF The reserved word for #IFDEF (to be described later)
ENDIF The reserved word for #IFDEF (to be described later)

− 175 −
Chapter 5. RTC Parts

■
■Specifying output-to-CL-source conditions using #IFDEF
•• When #IFDEF and #ENDIF are used in a template CL source, the CL statement line output
is enabled or disabled depending on the condition.
•• Use the following format. Insert a CL statement line between #IFDEF and #ENDIF, with
TRUE or FALSE placed immediately following #IFDEF.
#IFDEF TRUE | FALSE
(CL statement)
#ENDIF
•• When using the format in a template CL file, describe a condition using an alias name
(“#equipment NO1” in the example below) as in the following example and replace it with
TRUE or FALSE using the replacement function:
#IFDEF #equipment NO1
(CL statement)
#ENDIF
•• Write each of #IFDEF and #ENDIF on a separate line. Neither of these words can be written
on any line of the CL statement. After the replacement operation is completed, the #IFDEF
and #ENDIF lines are deleted.
•• In #IFDEF, #ENDIF, TRUE and FALSE, the uppercase or lowercase letters are not recog-
nized as different letters. Therefore, “#ifdef ” and “#Ifdef ” are handled as #IFDEF.
•• If any of the following conditions is met, an error is generated, a message is output and the
operation to output the CL file is stopped.
– #IFDEF and #ENDIF don’t match.
– No condition (TRUE/FALSE) is provided immediately following #IFDEF.
– A character string other than #IFDEF and a condition is provided on the line for #IFDEF.
– A character string other than #ENDIF is provided on the line for #ENDIF.

Note When using PAD for describing template CL source utilizing #IFDEF and #ENDIF, de-
scribe each of the #IFDEF lines and the #ENDIF lines in a separate processing box and
do not describe other CL statements in these boxes. Neither the #IFDEF-processing
box nor the #ENDIF-processing box can be placed immediately before or immedi-
ately after a PAD box, such as a PAD selection box, beforejudgment repetition box,
after-judgment repetition box, box with branch-processing functions, or standby
box with branch-processing functions, which is used for assigning a label for a CL
statement. For more information about PAD boxes, refer to “MS2-PAD200-2001:
Engineering Tool PADET/CL CL Writing Procedure Using PAD.”

■
■Comment output
For a CL source that is output by a replacement operation, comments on the information are
added to the end of the file.

− 176 −
 5.2 Control Parts

Table 5-40. Comments to be added

Characters Contents
TEMPLATE CL FILE The name of the template CL file
TEMPLATE DATE/TIME The date and time when the template CL file was updated
CONVERT DATE/TIME The date and time that the replacement operation was executed
Alias names used for the replacements and their values A pair
Alias names
of an alias name and its value is output on a line

■
■SAMPLE PROGRAM
TEMPLATE CL FILE: sample.cl

-- HEADER
SEQUENCE FLOW (PRC: POINT #PMDPTAG)

-- VARIABLE DEFINITION
LOCAL COUNTER1: NUMBER AT NN(1) -- LOCAL VARIABLE NN(1)
EXTERNAL #AITAG -- EXTERNAL REFFERENCE AI
EXTERNAL #REGTAG -- EXTERNAL REFFERENCE REG

-- INITIALIZATION
PHASE ONE
STEP INITIAL
#IFDEF #ECHOBACK
SEND: “INITIALIZATION”
#ENDIF
SET COUNTER1 = 0

-- MAIN LOGIC
STEP ST1
SET COUNTER1 = COUNTER1 + 1
STEP ST2
IF #AITAG.PV < 50 THEN SET #REGTAG.SP = 75
IF COUNTER1 < 100 THEN GOTO STEP ST1

-- TERMINATION
GOTO STEP INITIAL

END FLOW

------------------------------------------------------
REPLACE LIST DEFINITION
CL FILENAME : a.cl
#PMDPTAG : PM_SMPL
#AITAG : AI_SMPL
#REGTAG : RC_SMPL
#ECHOBACK : FALSE
------------------------------------------------------

− 177 −
Chapter 5. RTC Parts

When a replacement operation is performed for this template CL source, the following CL
source is created:

The CL file after the replacement operation : a.cl

-- HEADER
SEQUENCE FLOW (DOPC; POINT PM_SMPL)

-- VARIABLE DEFINITION
LOCAL COUNTER1: NUMBER AT NN(1) -- LOCAL VARIABLE NN(1)
EXTERNAL AI_SMPL -- EXTERNAL REFFERENCE AI
EXTERNAL RC_SMPL -- EXTERNAL REFFERENCE REG

-- INITIALIZATION
PHASE ONE
STEP INITIAL
SET COUNTER1 = 0

-- MAIN LOGIC
STEP ST1
SET COUNTER1 = COUNTER1 + 1

STEP ST2
IF AI_SMPL.PV < 50 THEN SET RC_SMPL.SP = 75
IF COUNTER1 < 100 THEN GOTO STEP ST1

-- TERMINATION
GOTO STEP INITIAL

END FLOW

-- TEMPLATE CL FILE : sample.cl

-- TEMPLATE DATE/TIME : 2005/01/01 00:00:00
-- CONVERT DATE/TIME : 2005/01/03 12:00:00
-- #PMDPTAG : PM_SMPL
-- #AITAG : AI_SMPL
-- #REGTAG : RC_SMPL
-- #ECHOBACK : FALSE

− 178 −
 5.2 Control Parts

5.2.9.7 How to Write Template CL Files (Merge page)

A template CL file is created by a text editor or PADET/CL. The following structure is pro-
vided for enhancing its reusability and for increasing resource use efficiency:

■
■Generic Tag (tag name determination using linkage)
To make reuse easier, HEADER and VARIABLE DEFINITION of a template CL file can be
generalized as shown in the following using CL source-editing macros.

•• In the header section, write “@” for the bound Process Module Data Point. When prepro-
cessed, it replaced by the TAG NAME of the host Process Module Part, as specified in the
CL Part.

•• In place of actual Tag Names, you can specify the corresponding Reference Port or the
Logical Tag Name of the Point Part. Reference Port is expressed as &REFn, where “n” is
the PORT identifier given by RTC Editor. Logical Tag Name, in the CL source program, is
preceded by “@”.

<BEFORE Generalization>
-- SAMPLE PROGRAM
SEQUENCE RLMT (DOPC; POINT PMDP001)
-- VARIABLES
LOCAL A AT NN(1) --INPUT A
EXTERNAL AI01 --EXTERNAL REFERECE : AI001
EXTERNAL REG_101 --EXTERNAL REFERENCE:REG_101

<AFTER Generalization>
-- SAMPLE PROGRAM
SEQUENCE RLMT (DOPC; POINT @)
-- VARIABLES
LOCAL A# AT NN(#) -- INPUT A
EXTERNAL &REF1 -- EXTERNAL REFERENCE:AI001
EXTERNAL @FLOWCTRL -- EXTERNAL REFERECE:REG_101

■
■Referencing Parameter Values
When using input connections or output connections from other Point Parts to CL Parts, the
Process Module Data Points’ internal parameters (NN or FL) are used as the I/O parameter.

− 179 −
Chapter 5. RTC Parts

■
■Merging CL Sources
If two or more parts in the same job are specified so that they are bound to the same process
module data point, all of them are output to a CL source when [Merge] is specified on [Merge
page]:
•• All CL Programs to be merged must have identical variable and program sections.

•• The header section and the footer section are merged into one in the CL source file.
Other parts of the CL Program repeat N times in the CL source file, where N is the number
of CL Parts specified by the same bound Process Module Data Point.
However, statements marked by a pair of CL-editing macro “%%” do not repeat in the CL
source file. Also, the comment line appears only once.

•• Another CL editing macro “#” is used in the label names and variable names.
The “#” is replaced by a sequential number when preprocessed. The sequential number is
assigned by RTC Editor according to its position in the Job Tree and its seniority within the
Sheet. For example, when three CL Parts have the same template CL source with the step
name “ST#”, it become three step names “ST1”, “ST2” and “ ST3”.

Here is an example of Merged CL source.

There are two CL Parts CL1 and CL2. They both share the same template CL source, have
Merge check box checked, and specify PMDP001 for the bound Process Module Part. CL1
refers to AI_101 and REG_101, CL2 refers to AI_201 and REG_201.

Note In merging CL source, the same template CL source must be defined for the CL Parts
for which the bind specification is done for the same process module data point. The
merging CL source can be executed even when the template CL sources are differ-
ent; however, the merge will not be carried out correctly.

AI 1 PM
Analog Input REF1 PROMOD
AI_101 CL 1 PMDP001

CL

Control1 PMDP001

PID REF2

REG_101

AI 2
Analog Input REF1
AI_201 CL 2
CL

Control2 PMDP001

PID REF2
REG_201

Figure 5-20.
− 180 −
 5.2 Control Parts

The template CL source within the CL Parts CL1 and CL2:

-- HEADER
SEQUENCE FLOW (DOPC; POINT @)

-- VARIABLE DEFINITION
LOCAL A# AT NN(#) -- LOCAL VARIABLE NN(N)
LOCAL B# AT NN(#) -- LOCAL VARIABLE NN(N+1)
EXTERNAL &REF1 -- EXTERNAL REFERENCE AI
EXTERNAL &REF2 -- EXTERNAL REFERENCE REG

-- INITIALIZATION
%%
PHASE ONE
STEP INITIAL:
%%
-- MAIN LOGIC
STEP ST#:
IF &REF1.PV < 50 THEN
& SET &REF2.SP = 75
IF A# > 25 THEN
GOTO ST#
%%
GOTO INITIAL
%%
END FLOW

When preprocessed using the Merge option, above template CL source are merged into the
following CL source:

-- HEADER
SEQUENCE FLOW (HC; POINT PMDP001)

-- VARIABLE DEFINITION
LOCAL A1 AT NN(1) -- LOCAL VARIABLE NN(N)
LOCAL B1 AT NN(2) -- LOCAL VARIABLE NN(N+1)
EXTERNAL AI_101 -- EXTERNAL REFERENCE AI
EXTERNAL REG_101 -- EXTERNAL REFERENCE REG
LOCAL A2 AT NN(3) -- LOCAL VARIABLE NN(N)
LOCAL B2 AT NN(4) -- LOCAL VARIABLE NN(N+1)
EXTERNAL AI_201 -- EXTERNAL REFERENCE AI
EXTERNAL REG_201 -- EXTERNAL REFERENCE REG

-- INITIALIZATION
PHASE ONE
STEP INITIAL:

− 181 −
Chapter 5. RTC Parts

-- MAIN LOGIC
STEP ST1:
IF AI_101.PV < 50 THEN
& SET REG_101.SP = 75
IF A1 > 25 THEN
GOTO ST1
STEP ST2:
IF AI_201.PV < 50 THEN
& SET REG_201.SP = 75
IF A2 > 25 THEN
GOTO ST2
GOTO INITIAL
END FLOW

■ Editing Macro List

■CL
Following Table shows CL editing macros supplied with RTC Editor:

Table 5-41. CL Editing Macro List

CL Editing Macros Description

Used in the SEQUENCE statement. It represents the TAG
@
NAME of the Process Module data point.
It is the logical identifier of the EXTERNAL referenced point,
&REFn
as expressed by the Reference Port. It is substitued by the ac-
(n is a positive integer from 1 to 99.)
tual TAG NAME when preprocessed.
It is the logical identifier of the EXTERNAL referenced point,
@Logical Tag Name as expressed by the Logical Tag Name. It is substitued by the
actual TAG NAME when preprocessed.
It specifies the range which do not repeat in the CL source file.
Example: %%
%%
GOTO INITIAL
%%
When preprocessed, this macro is substituted by the sequential
number from 1 to N, where N is the number of CL Parts to be
merged. It is used in
(1) Step Name, with # as the last character, such as “ST#”
(2) Phase Name, with # as the last character, such as “PH#”
#
(3) Local Variable Name, with # as the last character, such as “A#”
(4) Index for NN and FL, such as NN(#) or FL(#)
In (1), (2) and (3), for each CL part, the same number will be
attached to # used in template CL source. In (4), indexing will
be carried out to avoid duplication with the declared numbers.

− 182 −
 5.2 Control Parts

5.2.9.8 Compiling CL Programs

CL Programs can be compiled from RTC Editor.
SE program should be activated before compiling CL programs.

■
■Compiling CL Programs

Step 1 Choose the [Compile/Load CL...] command from [Implementation] menu of

the Job Window. Compile & CL dialog box appears. In the dialog box, the upper
[Compile] group box is the part to be set during compilation.

Step 2 Choose the <Compiler> button to invoke a file dialog to specify the path name of
the CL compiler “CLDO.EXE”. Once defined, you may omit this operation as long
as the path name remains valid. Normally, this becomes the default setting, and
new setting is not required.

Step 3 Choose the <Program> button to invoke invoke a Set CL file dialog box and specify
the path name of the CL program.You can specify multiple files simultaneously by
selecting them while holding the [Shift] key down or by square selection using the
mouse. After the selection, click the <Open> button to view all the selected files in
the [File Name] combo box in the [Compile/Load CL] dialog box.

Step 4 Select Compile Options as shown in the following table.

See “CL Reference Manual” for more information.

Table 5-42.

Compile Option Description

DEBUG Compile %DEBUG lines
NOLIST Output erred lines only
NOWARN Do not output Warning messages
NOXREF Do not output Cross Reference Table

Step 5 Choose the <Compile> button.

The result of execution appears in the central box. Click the <Help> button to show
the Help file on compiling. Refer to this for help on how to use the options for com-
piling.You can save the displayed result by clicking the <Save> button and specify
the directory and the file name.

Step 6 If the program is compiled successfully, the object file and program list file are cre-
ated in the same directory of the CL program (i.e.\CL). The object file has extension
.CO, and program list file has extension .LS. Moreover, the object file is automati-
cally created in the same job directory under folder \CO.

Note The CL Compiler can be used only while SE Program is running (to invoke SE
Program, the System Data File must have been created). If SE Program is not in-
voked, the result of the execution will not be shown correctly.

Note After CL compilation, RTC editor checks .co files that they are loadable to same
PMDP point. If .co files which are loadable to same PMDP point are found, warning
dialog is displayed.
− 183 −
Chapter 5. RTC Parts

5.2.9.9 Loading CL Programs

A compiled CL program is loaded from RTC Editor. The procedures are described below.

Step 1 Execute the [Implementation] → [Compile/Load CL...] commands, and the

[Compile/Load CL] dialog box appears. In the dialog box, the middle [Load] group
box is the part to be set at the time of loading.

Step 2 In the [Compile/Load CL] dialog box, specify the CL loader execution file.
Once this is specified, the following procedure is not necessary:
In the file dialog box click the <Loader> button, specify the path name of the loader
“hdseqdll.exe.” Normally, this becomes the default setting, and new setting is not
required.

Step 3 In the [Compile/Load CL] dialog box, specify the file to be loaded. Click the <File>
button to invoke [Set Load Files] dialog box, and select the file (with extension .co)
to be loaded.
You can specify multiple files simultaneously by selecting them while holding the
[Shift] key down or by square selection using the mouse.
After the selection, click the <Open> button to see all the selected files in the [File
Name] combo box in the [Compile/Load CL] dialog box.

Step 4 In the [Compile/Load CL] dialog box, click the <Load> button to execute loading.
The result of execution appears in the central box. You can save the displayed result
by clicking the <Save> button and specify the directory and the file name.

Note Like CL Compiler, CL Loader can be used only when SE Program is activated.

Note Before loading, RTC editor checks .co files that they are loadable to same PMDP
point. If .co files which are loadable to same PMDP point are found, loading is
aborted. Please try again after deleting unnecessary .co files.
[R411 or later] If .co files which are loadable to same PMDP point are in the same di-
rectory, warning dialog is displayed before loading. If you want to continue loading,
click the <Yes> button. If you want to abort loading, click the <No> button.

− 184 −
 5.2 Control Parts

5.2.10 Reference Point Parts

This section first describes the use of Reference Parts, followed by a description of the various
elements related to Reference Parts.

■
■Uses of Reference Parts
The RTC Editor provides Reference Parts to cope with the following conditions:
•• Display of the same point in multiple places
For displaying a point created on a given sheet on other sheets.

•• At the stage of part creation

For handling parts by Container units as in the case of subroutines in programming.
Point Parts in Containers are treated as dummy arguments, and are related to the actual
Point Parts when the part is established.

■
■Terminology Related to Reference Parts
The “Copy” of Point Parts is referred to as “Input Reference Part” or “Input Reference Side”.
The Point Part that becomes the Original (referenced part) is called the “Original” or “Output
Reference Side”. Reference Parts can be used to show the contents of other Point Parts, but
they are not subject to Point Creation.
By making Point Parts “Referenceable”, the Reference Parts can be modified.
Reference Parts can be restored to Point Parts by “Normalizing”.
“Reference Ports” can be defined for Point Parts, Container Parts, and CL Parts.
“Point Links” can be established between Reference Ports.

5.2.10.1 Using Reference Parts to Display the Same Point in Multiple Locations
By using Reference Parts
•• One original Point Part will have multiple copies.
•• The Original and Copy can be distinguished visually, and their interrelations can be
shown.
•• The Copy can appear on multiple sheets, and the Copy will have the same contents as the
Original.
•• Connection by Parameters of Copies is reflected in the I/O definitions of the Originals.

■
■Making Reference Point Parts

Step 1 Create a Point Part in a Sheet (SheetA).

Step 2 Copy the Point Part and paste into another Sheet (SheetB).

Step 3 When pasted, the Logical Tag Name resets to default. If necessary, set Logical Tag
Name.

− 185 −
Chapter 5. RTC Parts

Step 4 With the Point Part in Sheet B, invoke [Control Properties] property sheet, Select
<Reference Part> page and choose <Reference Part> button. Then, it becomes the
Reference Point Part. At this point, it is not yet determined whose clone it is. Such
Reference Point Part appears is shown below:

Logical Tag Name

Part Type PID
Tag Name TIC101
Reference Point Part
-before original is designated

Figure 5-21.

Step 5 To relate the original and the Reference Point Part, add a Reference Port to each
Part.
Even if multiple Reference Point Part exist, add only one Reference Port to theorigi-
nal, since Point Links can fan out from the output Reference Port.

Step 6 Connect a Point Link between Reference Ports of the Original and the Reference
Point Parts. Double-click a Reference Port and invoke the Set Reference Port prop-
erty sheet. From the property sheet, choose the other end of the Reference Port.
When the original-reference relation is established, the color of the Reference Port
on both ends turns green, and the appearance of the Reference Point Parts appear
as shown below.
After the relation has been established between the Original and the Reference
Point Part, we define that part as “Reference Point Part”. The [Properties] property
sheet of “Reference Point Part” is “View only”. Note that a different type of dashed
line is used, and the Tag Name of the original Point Part is shown.
REF1
Logical Tag Name FlowControl
Part Type PID
Tag Name from Original TIC_101
Reference Point Part
-after original is designated

Figure 5-22.

Note •• Once the original-reference relation is established, connect Parameter Links

to both reference and original Point Parts. Any input-output connection to the
Reference Point Part is reflected in the original.
•• Find the original to Set Properties. Intersheet Link List described in earlier section
may be helpful for this purpose.

− 186 −
 5.2 Control Parts

Note •• You cannot make Point Parts reference, or back to the original, as long as the Part
has Reference Ports. You must delete Reference Ports before doing the operation.
•• When the Point Link is connected to a Reference Point Part, all Parameter values
of the Reference Point Part (except Logical Tag Name) are the same as that of
the original Point Part. These values remain even after the Part is no longer the
reference.
•• Not copying and pasting the Original Point Part, but just creating a new Point Part
in another Sheet, necessitates confirmation that both Point Parts have common
values, for some key Parameters.

Note Point Links between Parts will be disconnected when changing the value of
Parameters and consequently satisfying the following conditions,
•• When the algorithms of the Original and the Reference Part cease to coincide for
Regulatory Control (RC), Regulatory PV (RP) and FFFB Parts.
•• When the data format and input/output attributes of Ports cease to coincide.
•• When Parameters that are not found in the Original exist in the Reference Part.

5.2.10.2 Point Reference to Container Parts

The Container Part contains multiple Parts which define the control strategy and promotes
the reuse of design elements.
However, to promote Container Part reuse, it is necessary to use it as a “black box*”, and set
some Parameters from the outside. RTC Editor’s “Point Reference” function enables you to
do this.
The Container Part can pass the Point Reference to Point Parts within. It is done via the
Reference Port. A “relation” is established to this Port using a (reference) Point Part located
in the Container Part.

* For CL Parts, reuse is facilitated if you avoid embedding Job-specific Tag Names in CL
sources. In this case, the Tag Name should be set to be referenced from outside and set
from outside using Point Links.

Reference
Temp 1
Reusable Part
Analog Input REF1 REF2
Temp Control
Point Link

Original
Part Related

Sheet Window
Temp
Analog Input Clone Part

Figure 5-23.

− 187 −
Chapter 5. RTC Parts

■
■Making a Container Part Reusable Using Point Reference

Step 1 First, identify the Point Parts to be used. This will be done within the sheet window
of Reusable Container Part. This Part will be the Reference Point Part.

Step 2 Open the sheet where Reusable Container Part is located. From that sheet copy the
Point Parts that was created in Step1. This part will be the Original Part.

Step 3 Add Reference Port to the Original Part, and Reusable Container Part (the number
of ports to be added is equal to the number of parts to be link and created on its
Sheet Window).

Step 4 On the sheet window of the Reusable Container Part set referring relation for the
Reference Point Part and the Original Part.
To do this, invoke [Control Properties] property sheet for the Reference Point
Part. Then, in <Reference Part> page, click the <Set> button from [Corresponding
reference part on upper container] group box, and [Set Referring-Relation] dialog
box appears.

Step 5 In the central list box, free Reference Ports on the Container Part are listed.
The information in the list includes ID and the position of the Port.

Step 6 Choose one Reference Port from the list box, and click the <OK> button.
The selected Reference Port is shown in the Related Reference Port group box in
Reference page.

Step 7 When the relation is established, the Reference Port ID is displayed in the Tag
Name slot of Reference Point Part’s default View.

Logical Tag Name FlowControl

Part Type PID
Tag Name (REF1)
Relation is established,
but Point Link is not yet connected.

Figure 5-24.

Step 8 Connect a Point Link between the Original Point Part and the Port of the Reusable
Container Part.
Then, in the Tag Name slot of the clone Point Part’s default View, TAG NAME of
the original Point Part is shown.

− 188 −
 5.2 Control Parts

Flow Control

PI D Boiler
TIC001
REF1 REF1

Logical Tag Name FlowControl

Part Type PID

Tag Name TIC001(REF1)

Relation is established,
and Point Link is connected.

Figure 5-25.
To clear the correspondence, take the following step:

Step In the [Corresponding reference part on upper container] group box on the
[Reference Parts] page, click the <Clear> button.
Note When a point link has been connected to the Reference Possible of a container,
correspondence can no longer be established with it. The step of establishing cor-
respondence must precede the step of connecting a point link.

Note When an upper Container is copied/moved as a whole to the Job Repository, the
Reference Port with which correspondence has been established is eliminated, and
the Reference Port identifier is no longer displayed in the Tag Name space of the
Reference Part.

■
■Reuse of Reusable Parts

Step 1 Paste the Reusable Container Part into the Sheet.

Step 2 Copy the Reference Parts corresponding to the Container’s Reference Ports from
the Container and arrange the Parts around the Container.

Step 3 Delete the Reference Port from these Reference Parts, and change these to Point
Parts by the [Normal Part] option on the [Control Properties] property sheet.

Step 4 Set the Logical Tag Name, Tag Name, Hardware Address, and Unit ID, etc., for the
Point Parts.

Step 5 Click the link button in the Parts Bar to establish the Point Link between the Point
Parts and the Container’s Reference Port. The Reference Parts inside the Container
are as shown in the following diagram.
Logical Tag Name FlowControl
Part Type PID
Tag Name
TIC_101(REF1)
Relation is established,
and Point Link is connected.

Figure 5-26.
− 189 −
Chapter 5. RTC Parts

5.2.10.3 Reference Parts

Point Parts that have been made referenceable are called Reference Parts.

■
■How To Make Point Parts Referenceable
The procedure for making Point Parts referenceable is described in the following.

Step 1 Select the Point Part and open the [Control Properties] property sheet.

Step 2 Display the [Reference Part] page of the [Control Properties] property sheet.
In the [Set Reference Part] group box on this page, select the [Reference Part] op-
tion button to make the Point Part referenceable.

Note After a Reference Port has been added, a Part cannot be made referenceable (nor
normalized). To make such a Part referenceable, or to normalize it, first delete the
Reference Port.

Note At the time a Point Part is made referenceable and a Point Link is established, the
Parameter information (excluding the Logical Tag Name) held by the Point Part is
programmed in the value of the Output reference side. The Logical Tag Name (in-
dependent of the Output Reference Side) has the Parameter held on the Reference
Part side and can be changed by the Reference Part side.

Note If the [Normal Part] option is selected in the [Set Reference Part] group box on the
[Control Properties] property sheet, the Reference Part can be restored to a normal
Point Part, but a once referenced Point Part connected by a Point Link will retain the
Parameter information of the Output reference side. It should be noted that a point
duplication error would be generated at the time of point creation if left as it is.

− 190 −
 5.2 Control Parts

5.2.10.4 Reference Port

Reference Ports are defined on the [Control Properties] property sheet.

■
■Port attributes
Reference Ports are classified into “Input,” “Output,” and “Neutral” (not yet decided whether
it will be used on the input or output side).

■
■Types of Reference Ports
Reference Ports can be categorized as Input, Output or Neutral.

PID PID Container 1

REF 1 Neutral REF 1 Output REF 1 Input

Figure 5-27.

■
■Number of Reference Ports that each Part can have
Table 5-43 shows the number of Reference Ports, both input and output, that can be defined
for each Part.
In this table, “n” means that any number of Reference Ports can be added. The maximum
number of Reference Ports that can be set for Parts is 99.

Table 5-43. the number of Reference Ports

Items Input Reference Port Output Reference Port Type Default

Point Parts 0 1 Output reference port
Container Parts multiple (less than 100) 0 Input reference port
CL Parts multiple (less than 100) 0 Input reference port
Reference Parts 1 1 Neutral

•• Reference Parts can have not only input but also output Reference Ports. This function is
used for such purposes as designating a Reference Part as an external reference destination.
Input Port of
REF2 Reference Part

PID REF1 REF1 CL

Output Port of
Reference Part

Figure 5-28.

•• Containers can have input Reference Ports. Reference Ports of a Container can be made
to correspond to the Reference Port of a Reference Part placed on the Sheet where the
Container is opened.

− 191 −
Chapter 5. RTC Parts

■
■Appearance of Reference Ports
•• AReference Port appears as a small, hollow rectangle in which a Reference Port ID is dis-
played. A Reference Port ID is expressed like “REF1.” That is, “REF” is followed by a Part-
unique number.
•• Reference Port colors, which depend on the category of Reference Port and the connected
point link, are as shown in Table 5-44.

Table 5-44. The Type and color of the Reference Port

Color of Port
State Of Reference Port Type Color of Port Text
boundary
Neutral Purple
Point Link is not connected
or Output Blue Black
Intersheet Link is connected
Input Red
Output Blue
Point Link is connected Green
Input Red

•• When the Port attribute is undefined, the color of the Port frame is purple. The color
changes when the point link is connected and when input or output is decided.

■
■Adding Reference Ports
Add Reference Ports in Original and Clone Point Parts.

Sheet X Sheet Y
B:REF1:Y
A C:REF1:Z A:REF1:X B
CL REF1 REF1 PID
Invisible Point Link

Sheet Z
C
REF1 PID
A:REF1:X

Figure 5-29.

− 192 −
 5.2 Control Parts

Step 1 Invoke [Control Properties] for a Point Part.

Step 2 At [Reference Port] page:

•• Set Port’s position on the Part. Type X position and Y position in the appropri-
ate boxes inside the Position of Reference Port group box. The upper-left corner
position is (0.00, 0.00) and the bottom-right corner position is (1.00, 1.00). The
value for X and Y should be between 0.00 and 1.00. Since the Port is placed on
the boundary of the Part, either X or Y should be 0.00 or 1.00.

•• Click the <Add> button. Then, the newly-added Reference Port appears in the
Reference Port List box. This list box has the following entries:

Table 5-45. Reference Port List Box

Item Description
NEWn n is Reference Port ID (n=1 to 99).
Type N = Neutral, I = Input, O = Output
X, Y Position of Reference port; each has value 0.00-1.00.
Descriptor Descriptor, if any

■
■Deleting Reference Ports

Step 1 Invoke [Control Properties] property sheet for a Point Part.

Step 2 Select the Reference Port to delete, from Reference Port List box at Reference Port
page.

Step 3 Make sure <Delete> button is enabled, and click the <Delete> button.

Step 4 Click the <OK> button, and the selected Reference Port is deleted. When a Point
Link is connected to the deleted Reference Port, the Point Link is also deleted.

■
■Input Descriptor of Reference Port
Descriptor of Reference Port, once entered, will be displayed in the Reference Port List box at
Reference Port page of Control Properties property sheet. This makes it easy to identify the
correct Reference Port to connect.

Step 1 Double-click on a Reference Port, and invoke [Set Reference Port] property sheet.

Step 2 Type text in Descriptor box.

− 193 −
Chapter 5. RTC Parts

5.2.10.5 Point Link

Point Links define the relations between the Input and Output of Point Parts. When the Parts
(and algorithms) are not of the same type, Point Links cannot be connected.
Point Links are indicated by bold yellow lines between the Reference Ports on the Sheet, with
arrows pointing from the Output side to the Input side.
Point Links (Intersheet Links) between Reference Ports on different sheets do not appear
on the sheet. However, how the link is connected can be learned by issuing the [Browser] →
[Intersheet Link List] commands.

■
■Connecting Point Links Between Reference Ports On the Same Sheet
The procedure for connecting Point Links between Reference Ports on the same Sheet is de-
scribed in the following:

Step 1 Confirm that the Reference Ports have been added on both the Input side and the
Output side Parts.

Step 2 Click the <Link> button in the Control Parts Bar.

Step 3 The following operations are the same as in the case of Parameterization.
The operation for reshaping the Point Link is also the same as in the case of
Parameterization. For details, refer to Section 5.2.3.1, “Parameter Links.”
Drawing of the Point Link can be started at either end of the link.

Step 4 A message appears if the Point Link between Control Parts is inappropriate, and
the Point link is cancelled.

■
■Deleting Point Links Between Reference Ports On the Same Sheet
The procedure for deleting Point Links between Reference Ports on the same Sheet is de-
scribed in the following:

Step 1 Click the Point Link to be deleted and issue the [Edit] → [Delete] commands or
press the [Delete] key.

Step 2 Also delete the Reference Port (for the procedure, refer to the “Procedure for
Deleting Reference Ports” later in this manual).

■
■Point Links to CL Parts
CL Parts can be placed outside Parts as Reference Ports for external reference definitions on
the Input side. By Point Linking these Reference Ports with the Point Parts’ Reference Ports
on the Output side, the external referencing of CL Parts can be solved. For details, refer to
Section 5.2.9.4, “CL Parts.”

− 194 −
 5.2 Control Parts

■
■Adding Intersheet Links
Intersheet Links are Point Links connecting Input Reference Parts on one sheet with Output
Reference Parts on another sheet.
Intersheet Links are connected using the following method:

Step 1 Double-click one of the Reference Ports to be connected by the Intersheet Link to
open the [Set Reference Port] property sheet.

Step 2 Click the <Add Link> on the [Set Reference Port] property sheet to display the
[Add Link] dialog.

Step 3 In the list box of the [Add Link] dialog, the Reference Ports that become subject
to linking are shown in the “Logical Tag Name: REFn: Sheet Name: Descriptor”
format.

Table 5-46. [Add Link] Dialog List Box

Item Description
Logical Tag Name of the Control Part to which this Reference
Logical Tag Name
Port belongs
REFn n is Reference Port ID (n is 1 to 99)
Container Name Container Name to which the Control Part belongs
Descriptor Any text

Step 4 The [Add Link] dialog box is closed by double-clicking or by clicking the Reference
Port for setting the Link and the <OK> button.
Because the Reference Port on the Output side can fan-out the output destination,
it is possible to select multiple destinations when setting the link. Only one des-
tination for the link setting can be made for the Reference Port on the Input side.

Step 5 Reference Ports specified above appear in the [Intersheet Links] list box on the [Set
Reference Port] property sheet. Clicking the <OK> button completes definition of
the Intersheet Link. The color of the frames around the Reference Ports in both
ends turns green.

− 195 −
Chapter 5. RTC Parts

■
■Deleting Intersheet Links
The following procedure is used to delete Intersheet Links.

Step 1 Double-click one of the end Reference Ports to which the Intersheet Link is con-
nected to open the [Set Reference Port] property sheet.

Step 2 Select the Reference Port from which the relation should be disconnected in the list
box showing the Reference Ports in the [Set Reference Port] property sheet. This
deletes the Reference Port from the list box.

Step 3 When the <OK> button is clicked to confirm the indicated contents of the list box,
the Intersheet Link is deleted. The color of the frames around the Reference Ports
in both ends turns from green to the original color.

Note Make sure not to make Point Links between Reference Parts and Containers that
correspond to the Sheet on which the Reference Parts are located. Those kinds of
Intersheet Links are deleted if the Container is moved, and in connection with has
NASBe registration, etc.

Note When the Link destination is changed for Reference Ports to which an Intersheet
Link is already established, the following procedure should be used. If the Point
Link is simply deleted, all the link candidates that can be connected may not be
displayed.
Step 1 : On the property sheet appearing when the Reference Port is double-
clicked, use the <OK> button to confirm the link to be deleted, and then
close the property sheet.
Step 2 : Again double-click the Reference Port to open the property sheet, and then
set the new link.

Note If a point link has not yet been set in the reference port of reference parts, generat-
ing a point displays a Warning.

− 196 −
 5.2 Control Parts

5.2.10.6 Make Reference Links

[Make Reference Links] facilitates the creation of Reference Parts. Either select [Job] → [Make
Reference Links] from the menu in the Job Structure Window or [Edit] → [Make Reference
Links] from the Sheet menu to display the [Make Reference Links] dialog box.

■
■Procedure for Make Reference Links

Step 1 Place a Point Part to be made referenceable in the sheet, and set the Point Part with
the same tag name as the Referred Part.

Step 2 Display the [Make Reference Links] window. Specify Referred and Referring
sheets.
The setting items vary depending on the selection in the [Select Sheet] combo box.

Table 5-47.

Selection in the [Select

Settings Description
Sheet] combo box
Specify Referred sheets. Specify Referred sheets.Referring
Other sheets are Referring [Referred] sheets only sheets are all sheets under the Root
sheets Sheet except Referred sheets
Specify Referring sheets. Specify Referring sheets.Referred
[Referring] sheets
Other sheets are Referred sheets are all sheets under the Root
only
sheets Sheet except Referring sheets
Specify Referred and Both [Referred] and Target all Referred and Referring
Referring sheets [Referring] sheets sheets under the specified sheet

When both [Referred] sheets and [Referring] sheets are selected, clicking the
<Select Sheet Name> button opens the [Select Sheet] dialog box, where a sheet can
be easily selected.

Step 3 Click the <Execute> button in the [Make Reference Links] window to set the
Reference Link for the part that is judged to be identical, both in the [Referred] and
[Referring] sheets set in Step 2 . The criteria to judge whether they are identical are
whether they have the same Point Type and the same tag name.

Note that, if the <Check> button is clicked instead of the <Execute> button in Step
3 , only an error check is performed. In this case, neither the Point Reference nor
the Reference Link will be executed.
The settings made in the [Make Reference Links] window are saved as they are
when the <Execute> or <Check> buttons are clicked for the last time in a session.
When the [Make Reference Links] window is opened next time, the previous set-
tings will be displayed.

− 197 −
Chapter 5. RTC Parts

Make Reference Links may or may not be executed, depending on the states of the Referred
and Referring parts, as shown below.

Table 5-48.

Referred Normal Point Reference Only Point Reference +Referring Port Referring Linked Referred Port Referred Linked

Referring
Normal

✓ -- -- -- ✓ ✓

Point Reference Only

✓ -- -- -- ✓ ✓

Point Reference +Referring Port

✓ -- -- -- ✓ ✓

Referring Linked

-- -- -- -- -- --

Referred Port

✓ -- -- -- ✓ ✓

Referred Linked

-- -- -- -- -- --

Note After the <Execute> button is clicked, the reference settings of the parts cannot be
undone. To undo the settings, change the reference settings of each part separately.

Note When “Specify Referred and Referring sheets” is selected in the [Select Sheet]
combo box, an error occurs if an identical sheet exists in both [Referred] and
[Referring] sheet hierarchy. Set carefully so that there is no duplicate between the
[Referred] and [Referring] sheets.

Note A Reference Part of a Reference Part cannot be created with this function.

Note As for Regulatory Control (RC), Regulatory PV (RP) and FFFB parts, an error occurs if
the tag names of the Referring and Referred parts are identical but their algorithm
types are different. However, if the algorithm type of the Referring side is NULL, the
algorithm type of the Referred side is used to create a Reference Link.

− 198 −
 5.2 Control Parts

■
■Display Execution Results
When the execution starts, the results appear in the [Status] in the [Make Reference Links]
window.
If an error occurs during the execution, when you click the <Next Error> or <Prev Error>
button, the error in the list is highlighted.
If the <Open Sheet> button is operative on any Referred and Referring parts information line
displayed below “ERROR>,” “OK>” or “INFO>,” when you doubleclick the line or click the
<Open Sheet> button, the sheet where the part is placed is opened with the part shown in the
selected condition in the center of the sheet.
The execution results can be saved in text format by clicking the <Save> button.

Note If an error occurs during execution, the operation will not be executed for the part
in which an error occurred. However, the operation will be executed for other parts
where no error occurred.

5.2.11 Utility Parts

The Utility Parts does not produce point database, but they do help to draw relatively compre-
hensive diagrams. RTC Editor provides the following Utility Parts:
•• Intersheet Parts
•• Intrasheet Parts
•• Divergence Parts
Both Intersheet Parts and Intrasheet Parts connect invisible Parameter Links, which are iden-
tified by Invisible Link IDs.

5.2.11.1 Intersheet Parts

With the help of Intersheet Part, connect a Parameter Link over the Sheet boundary.
There are two kinds of Intersheet Parts: Intersheet Part (Output) and Intersheet Part (Input).
One or more Intersheet Parts (Input) can be connected to one Intersheet Part (Output).
Part’s ID is shown on the surface of the Intersheet Part (Input), you can see the other end of
the connection.
Double click Intersheet Parts with [Ctrl]+[Shift]key, the other end of the connection is shown.
Sheet #1 Sheet #2

Point Part "X" Point Part "Y"

Invisible Parameter

Intersheet Part (Output) Intersheet Part (Input)

Figure 5-30.

− 199 −
Chapter 5. RTC Parts

■
■Operation procedure

Step 1 An Intersheet Part (Output) is displayed as a blue-bordered rounded rectangle with

an input Port. When the connection destination of the output Port is outside the
Sheet, the Intersheet Part (Output) is placed on the output Port side, and the output
Port and the input Port of the Intersheet Part (Output) are interconnected.

Step 2 An Intersheet Part (Input) is displayed as a red-bordered rounded rectangle with

an output Port. When the connection destination of the input Port is outside the
Sheet, the Intersheet Part (Input) is placed on the output Port side, and the input
Port and the output Port of the Intersheet Part (Input) are interconnected.

Step 3 Shown on the surface of the Intersheet Part (Output) is the identifier “mmmmm-
mmmm-kk,” of which mmmmmmmmm is a Sheet Number (9- digit integer) set
in Sheet Information and kk is an Intersheet Part (Output) number on the Sheet.
Serial numbers beginning with 1 are assigned as Intersheet Part numbers.
After 99, unused numbers are used in ascending order. Shown on the surface of the
Intersheet Part (Input) is the identifier “ID:nnnn,” of which nnnn is an Intersheet
Part ID (internal ID for identification), different from an Intersheet Part number,
on the Sheet. Serial numbers are automatically assigned as Intersheet Part IDs,
making no distinction between input and output and between inside and outside
a Sheet.

Step 4 To associate an Intersheet Part (Output) and an Intersheet Part (Input), open the
[Intersheet Part] dialog box by double-clicking either the input or output Part or
by executing the [Properties] command.

Step 5 In the [Intersheet Part] dialog box, type in a descriptor as necessary.

Descriptors set for output Parts are displayed in the Intersheet Parts list.

Step 6 Click the <Add Link> button, and the [Add Link] dialog box opens. The [Add
Link] dialog box lists possible partners defined on other Sheets, in the format
“Sheet Number: Intersheet Part Number: Descriptor.” After choosing a partner,
click the <OK> button. The [Intersheet Links:] list box in the [Intersheet Part] dia-
log box displays the chosen partner Part in the format “Sheet Number: Intersheet
Part Number.”
Upon determination of the partner, the color of the Intersheet Part frame changes
to yellow-green, and the partner’s identifier is displayed as the identifier of the
Intersheet Part (Input).

Step 7 To delete connection with the partner, choose the partner Part in the [Intersheet
Links:] list box and click the <Delete> button.

− 200 −
 5.2 Control Parts

5.2.11.2 Intrasheet Parts

If many Parameter Links are drawn in a Sheet, it may be hard to arrange Parts and also keep
the Sheet comprehensive. Intrasheet Parts are useful in such situation. You need not draw a
Parameter Link from one end to the other, but instead use Intrasheet.
There are two kinds of Intrasheet Parts: Intrasheet (Output) and Intrasheet (Input).

01

01

Figure 5-31.

The behavior of Intrasheet Parts are similar to that of Intersheet Parts, except:

•• Both Intrasheet Part (Output) and Intrasheet Part (Input) are placed in the same Sheet.
Possible Partners shown in the list box of [Add Link] dialog box are limited to those in the
same Sheet.

•• Intrasheet Parts are expressed as circles, rather than round-rectangles.

•• On the surface of Intrasheet Parts (Output), a two-digit Intrasheet Part (Output) ID is

shown. Numbers are assigned as serial numbers beginning with 1. After the balloon number
99 is assigned, vacant numbers are used in ascending order. On the surface of Intrasheet
Parts (Input), “IDnn” is shown where nn is a system-defined ID.

•• Parameter Links connected via Intrasheet Parts are not listed in the Intersheet Link list.

Double click Intrasheet Parts with [Ctrl] + [Shift] key, the other end of the connection is
shown.

− 201 −
Chapter 5. RTC Parts

5.2.11.3 Divergence Parts

You are often required to draw diagrams that clearly show if two crossing lines are connected
or not. Divergence Parts enables you to draw an explicit connection point for a Parameter
Link.
You can fan-out from Divergence Parts as many lines as there are connected output Ports.
If connected output Port has up to four Parameter links, you can draw up to four Parameter
Links from the Divergence Part. Divergence Part looks like a small circle, and consists of a tiny
input port and a tiny output port.

Figure 5-32.

■
■Using Divergence Parts
•• Create a Divergence Part by choosing Divergence button from Control Parts tool bar and
click at the Sheet.

•• Connect a Parameter Link between the output Port of a Point Part and the input side of a
Divergence Part.

•• Connect Parameter Links between the output side of a Divergence Part and the input Ports
of other Point Parts.

Note Because Divergence Parts are small, it is recommended to scale up a Sheet when
performing such operations as connecting Parameter links and moving Divergence
Parts. For scaling up Sheets, refer to 4.2.6, “Zoom In and Out.”

Note Whether signals can be fanned out from a Divergence Part depends on the connec-
tion attributes of the I/O Parameters linked.
For example, when it is possible to fan out up to four I/O Parameters connected to
the input side of a Divergence Part, up to four can also be fanned out from the out-
put side of the Divergence Part.

− 202 −
 5.3 Parameter View

5.3 Parameter View

A Parameter View is the part for displaying parameter values set for a Control Part (Point and
Block) on a sheet.
The following figure shows an image of a sheet where Parameter Views are displayed:

Figure 5-33.

•• A Parameter View can be generated for a Control Part.

•• For a Parameter View pattern, the parameters to be displayed, display format, font and
display position can be specified.

•• Display details of the Parameter View for a Control Part (Point) can be specified for each
point type (each algorithm if the point types are the Regulatory PV (RP), Regulatory
Control (RC), FFFB and algorithmic parts of Logic Component Parts) can be specified, and
those of the Parameter View for a Control Part (Block), for each block type.

•• For Control Parts (Point and Block) on a sheet, their Parameter View patterns can be speci-
fied collectively.

•• More than one Parameter View pattern to be displayed can be specified in advance.
A different pattern can be specified for each Control Part.

•• AParameter View display position can be changed with the mouse through a dragand- drop
operation freely by user.

•• The Parameter View image being displayed on a sheet can be printed.

•• When a Control Part is copied and pasted, the Parameter View settings associated with the
original Control Part are also copied.

− 203 −
Chapter 5. RTC Parts

Note •• CL Parts, Frame Parts and BOX Parameter Parts are provided with no Parameter
Views.
•• On Parameter Views, the parameter values set for Control Parts in RTC Job are
displayed. Online controller data in RTC runtime cannot be displayed.
•• The rectangular Parameter View size is automatically adjusted depending on the
character string length and cannot be altered with the mouse.
•• Each Parameter View can be deleted independently but cannot be copied and
pasted independently.
•• When a Control Part whose Parameter View is being displayed is encapsulated,
the Parameter View will disappear.

5.3.1 Operation OverView

5.3.1.1 Displaying

Step 1 Generate a pattern for the Parameter View to be displayed beside a Control Part on
a sheet. Refer to 5.3.2, “How to Set Patterns.”
•• To generate a Parameter View pattern for a Control Part (Point), specify param-
eters to be displayed and their display format for each point type (each algorithm
if the point types are the Regulatory PV (RP), Regulatory Control (RC), FFFB
and algorithmic parts of Logic Component Parts), and to generate a Parameter
View pattern for a Control Part (Block), for each block type. Also specify a font
for the display and display position for each pattern. Refer to 5.3.2.1, “Add/
Modify/Copy Pattern.”

Step 2 Select the pattern generated in Step1 on the sheet, which was selected from the job
structure window. Then click the <Apply Pattern> button. Refer to 5.3.2.2, “Apply
Pattern.”
•• This operation generates the Parameter View with the user-specified pattern
beside the Control Part on the sheet.

Note When a pattern specification (the parameters to be displayed, the format, font or
display position) is modified, the modification is reflected in each of the Parameter
View for which the pattern is set.
However, if a Parameter View on a sheet has been moved with the mouse or when
the (Fix) checkbox in 5.3.3, “Setting Pattern for Individual Control Parts” has been
checked, the display positions of the Parameter View on the sheet are not changed
even when the specification of the pattern display position is altered.

− 204 −
 5.3 Parameter View

5.3.1.2 View Mismatching

If a pattern set for Parameter Views on a sheet is deleted or a point type set for a pattern is de-
leted, a red character string stating “View Mismatching” will appear on the Parameter Views
where the pattern is set.
In such a situation, select the sheet from the job structure window and click the <Delete
Mismatch> button in 5.3.2, “How to Set Patterns” Then the displays for the invalidity on the
sheet can be deleted collectively.
When the deleted pattern or deleted point type is restored by an import operation in the state
where “View Mismatching” is displayed (refer to 5.3.2.4, “Exporting/Importing Patterns”), the
former Parameter Views will be displayed again.

5.3.2 How to Set Patterns

Select [View] → [Parameter View] → [Configuration] from the job structure window menu or
the sheet menu. Then the [Parameter View Configuration] dialog box is displayed.

Figure 5-34.

− 205 −
Chapter 5. RTC Parts

•• Explanations of control

Table 5-49.

Control Description
•• The pattern list of registered Parameter View patterns is displayed
[Pattern] list box
•• More than one Parameter View pattern can be selected
•• Click this button to add a pattern
<Add Pattern> button •• When this button is clicked, the [Pattern Configuration] property
sheet is displayed
•• Click this button to modify registered pattern settings
<Modify Pattern> button •• When this button is clicked, the [Pattern Configuration] property
sheet is displayed
•• Click this button to copy registered pattern settings to add a new
pattern
<Copy Pattern> button
•• When this button is clicked, the [Pattern Configuration] property
sheet is displayed
•• Click this button to delete the patterns that have been selected in
the [Pattern] list box
•• A red character string stating “View Mismatching” will be dis-
<Delete Pattern> button
played on the Parameter Views where the deleted pattern has been
set To restore the former state, import the patterns that have been
deleted and register them again
•• Click this button to set a registered Parameter View pattern for a
Control Part on a sheet
•• When no sheet has been selected from the job structure window,
<Apply Pattern> button
no pattern can be specified Click this button when a sheet has been
selected from the job structure window Then the [Sheet Select]
dialog box is displayed
•• When a Parameter View pattern set for Control Parts on a sheet is
deleted or a point type corresponding to a pattern is not set, a red
character string stating “View Mismatching” is displayed on the
Parameter Views to indicate the existence of an invalidity. Click
<Delete Mismatch> button this button to delete the Parameter Views in this state.
•• When the sheet has not been selected from the job structure win-
dow, the invalidity cannot be deleted.
•• Click this button when the sheet has been selected from the job
structure window. Then the [Sheet Select] dialog box appears.
•• Click this button to import files storing settings for each Parameter
<Import> button View pattern and to make the settings
•• Click this button Then the [Import] dialog box appears
•• Click this button to export files storing settings for each Parameter
<Export> button View pattern
•• Click this button Then the [Export] dialog box appears
•• Click this button to close the [Parameter View Configuration] dia-
<Close> button
log box

− 206 −
 5.3 Parameter View

5.3.2.1 Add/Modify/Copy Pattern

Click the <Add Pattern>, <Modify pattern> or <Copy Pattern> button in the [Parameter View
Configuration] dialog box. Then the [Pattern Configuration] property sheet appears.

Figure 5-35.

Figure 5-36.

Figure 5-37.

− 207 −
Chapter 5. RTC Parts

•• Explanations of each item

Table 5-50.

Control Description
•• The Pattern ID can be changed only while a new pattern
is being generated It cannot be changed after the <OK> or
<Apply> button is clicked
•• Specify a Pattern ID
•• Only alphanumeric and _ (underscore) characters can be
[Pattern ID] edit box
used
•• Up to 16 characters can be used
•• Specify a Pattern ID that is unique within a job
•• The characters of each Pattern ID are converted to the cor-
responding upper-case characters when registered
•• Set a pattern descriptor
•• Any characters can be used
[Description] edit box
•• Up to 40 characters can be used
•• The same descriptor can be used for two or more patterns
•• The point types to be set in this pattern are displayed under
“Point” and “Block”
•• The point types are displayed for each algorithm if they are
the Regulatory PV (RP), Regulatory Control (RC), FFFB
and algorithmic parts of Logic Component Parts Logic
[PointType] tree View Component Parts are displayed under LG_Component
•• Select a point type Then the currently set display format
appears in the [Format String] editing box
•• Click the <PointType Select> button Then a point type can
be added or deleted in the [PointType Select] dialog box
that will appear
•• Click this button to add/delete a point type to be set for the
<PointType Select> but- current pattern
ton •• When the button is clicked, the [PointType Select] dialog
box will appear
•• Specify a display format for the point type selected in the
[PointType] tree view
•• To display the value of a parameter, enclose the parameter
name with square brackets, [ ] (example: [EUDESC]) If
no parameter is provided for the Control Part, the entered
[Format String] edit box character string including brackets [ ] is displayed as it is
•• When clicking the <OK> button without making any set-
ting in the [Format String] edit box, the point type is not
registered and will not be displayed in the [PointType] tree
view on the next time and thereafter
•• Only up to 30,000 characters can be entered in the edit box
[Name] edit box •• The currently set font name is displayed
[Style] edit box •• The currently set font style is displayed
[Size] edit box •• The currently set font size is displayed
•• Used for changing the font to be used for the pattern
<Font> button
•• Click this button Then the [Font] dialog box will appear

− 208 −
 5.3 Parameter View

Control Description
•• Used for specifying the position where the Parameter View
with this pattern are to be displayed
•• Specify one from among the following eight positions:

[Position] radio buttons

Figure 5-38.
[Note]
Even if the specification of this display position is changed,
the position of the Parameter View moved with the mouse is
not changed To move this Parameter View to the newly spec-
ified position as well, check the [It follows this pattern] check
box in 5.3.3, “Setting Pattern for Individual Control Parts.”
•• Click this button to reflect current settings in the pattern
•• When this button is clicked, the settings are reflected in
the pattern and the [Pattern Configuration] dialog box is
<OK> button
closed
•• If a View invalidity might be caused, a confirmation mes-
sage box will appear before the dialog box is closed
•• Click this button to cancel current settings and close the
[Pattern Configuration] dialog box
<Cancel> button
•• When this button is clicked, the settings are not reflected
in the pattern and the dialog box is closed
•• Click this button to reflect current settings in the pattern
•• If a View invalidity might be caused, a confirmation mes-
<Apply> button sage box will appear before the dialog box is closed
•• When this button is clicked, modification in the [Pattern
ID] edition box will be disabled

■
■[PointType Select] dialog box
When the <PointType Select> button is clicked in the [Pattern Configuration] dialog box, the
[PointType Select] dialog box is displayed.

Figure 5-39.

− 209 −
Chapter 5. RTC Parts

•• Explanations of control

Table 5-51.

Control Description
•• Specify either Control Parts (Point) = “Point” or Control
Parts (Block) = “Block”
[Point/Block] combo box •• Depending on either of which is selected, the contents dis-
played in the [Not Show PointType] list box and the [Show
PointType] list box will vary
•• The point types not to be set in Parameter View patterns
are displayed
•• More than one point type can be selected
•• For each of the Regulatory Control (RC), Regulatory PV
[Not Show PointType] (RP) and FFFB Parts, the algorithm type is displayed
list box within brackets
•• For the Logic Component Parts, the display is made in the
format exemplified by LG (NUMERIC), and for algorith-
mic parts of the Logic Component Parts, by LG (ALGO
(AND))
•• The point types to be set in Parameter View patterns are
displayed
•• More than one point type can be selected
•• For each of the Regulatory Control (RC), Regulatory PV
(RP) and FFFB Parts, the algorithm type is displayed
[Show PointType] list box
within brackets
•• For the Logic Component Parts, the display is made in the
format exemplified by LG (NUMERIC), and for algorith-
mic parts of the Logic Component Parts, by LG (ALGO
(AND))
•• Used for adding the point types selected in the [Not Show
PointType] list box to the [Show PointType] list box
< >> button •• When this button is clicked, the point types selected in
the [Not Show PointType] list box are moved to the [Show
PointType] list box
•• Used for adding the point types selected in the [Show
PointType] list box to the [Not Show PointType] list box
<< > button •• When this button is clicked, the point types selected in
the [Show PointType] list box are moved to the [Not Show
PointType] list box
•• Click this button to register current settings in the pattern
<OK> button •• When this button is clicked, the settings are registered and
the [PointType Select] dialog box is closed
•• Click this button to cancel current settings and close the
[PointType Select] dialog box
<Cancel> button
•• When this button is clicked, the settings are not registered
and the [PointType Select] dialog box is closed

Note If a point type of an existing Parameter View pattern is set to [Not Show PointType] in
the [PointType Select] dialog box, a red character string stating “View Mismatching”
will be displayed.

■
■[Font] dialog box
Click the <Font> button in the [Pattern Configuration] dialog box. Then the [Font] dialog
box is displayed.
Specify a font for each pattern.

− 210 −
 5.3 Parameter View

5.3.2.2 Apply Pattern

Select a sheet from the job structure window, select a pattern to be specified and click the
<Apply Pattern> button in the [Parameter View Configuration] dialog box. Then the [Sheet
Select] dialog box is displayed.

Figure 5-40.

Table 5-52. Explanations of control

Control Description
•• When this box is checked, the Parameter View patterns for
the Control Parts on the selected sheet from the job struc-
[Parameter View is as-
ture window and all sheets under it are targeted
signed to the Part on the
•• When this box is not checked, the Parameter View patterns
selected sheet] check box
for the Control Parts only on the selected sheet from the
job structure window are targeted
•• Registered Parameter View patterns are set for the Control
Parts on the sheet
<OK> button
•• When the operation is completed, the corresponding mes-
sage box will be displayed
•• The [Sheet Select] dialog box is closed without anything
<Cancel> button
done

5.3.2.3 Delete Mismatch

Select a sheet from the job structure window, and click the <Delete Mismatch> button in the
[Parameter View Configuration] dialog box. Then the [Sheet Select] dialog box is displayed.

Figure 5-41.

Table 5-53. Explanations of control

Control Description
•• When this box is checked, the Parameter Views with in-
consistencies for the Control Parts on the selected sheet
[Mismatching Parameter
from the job structure window and all sheets under it are
View on the selected
targeted
sheet is deleted] check
•• When this box is not checked, the Parameter Views with
box
inconsistencies for the Control Parts only on the selected
sheet from the job structure window are targeted
•• Used for deleting Parameter Views with inconsistencies
<OK> button •• When the operation is completed, the corresponding mes-
sage box will be displayed
•• The [Sheet Select] dialog box is closed without anything
<Cancel> button
done

− 211 −
Chapter 5. RTC Parts

5.3.2.4 Exporting/Importing Patterns

■
■Exporting
Click the <Export> button in the [Parameter View Configuration] dialog box. Then the
[Export] dialog box is displayed.
The default path is set immediately under the job directory.
Select the necessary folder from the tree in the [Export] dialog box and click the <OK> button.
Then all currently registered Parameter View patterns are exported through the “ParamView_
PatternID.txt” files, each of which stores a corresponding registered Parameter View pattern.
When a file with the same name exists, a message box to confirm the execution of an overwrit-
ing operation is displayed.
When the exporting operation is completed successfully, the corresponding message box
appears.
If an error is generated during the exporting operation, the corresponding error message box
appears.
The exported files can be imported.

■
■Importing
Click the <Import> button in the [Parameter View Configuration] dialog box. Then the
[Import] dialog box is displayed.
The default path is set immediately under the job directory.
Select one or more files to be imported in the [Import] dialog box and click the <Open> but-
ton. Then the corresponding Parameter View patterns are imported.
* More than one file can be selected.
When the importing operation is completed successfully, the corresponding message box
appears.
If an error is generated during the exporting operation, the corresponding error message box
appears. In this situation, the settings in the pattern file that has generated the error are not
reflected in the corresponding pattern. In addition, a file named “ParamView.err” is generated
at the same path as that for the file that was to be imported and is output.
When a Parameter View pattern with the same pattern ID already exists in the job, the mes-
sage box to confirm the execution of an overwriting operation is displayed.
Click the <OK> button in this message box to overwrite the settings.

− 212 −
 5.3 Parameter View

Table 5-54. File formats for exporting/importing

Details of a “ParamView_
Description
PatternIDtxt” file
A line starting with a pound character (#) is considered a
# Pattern
comment
PatternID = default A pattern ID (essential)
PatternDesc = default A pattern descriptor
Blank lines are ignored
# Font
Font name
Any character string, provided it has 32 characters or less,
can be entered on the right side of “= (equal),” causing no
FontName = Courier New
error, and is set as is However, if the specified font is not in-
stalled on the PC, the OS (Windows) will use the font that it
judges to resemble that specified most closely for the display
FontBold = OFF Specify ON for upper-case letters Otherwise specify OFF
FontItalic = OFF Specify ON for italic letters Otherwise specify OFF
FontSize = 9 Specify a font size between 8 and 20

# Position
Specify a display position from among Upper Left, Upper
Position = Upper
Upper Right, Left, Right, Lower Left, Lower and Lower Right

# Settings for each point type

The settings made between curly braces { and } are consid-
{
ered as those for one point type
Specify a point type
“P:” is used for indicating Point and “B:” for Block For
each of the Regulatory PV (RP) parts, Regulatory Control
(RC) parts, FFFB parts and algorithmic parts of the Logic
PointType =P:RC(PID) Component Parts, the algorithm type is described within
brackets For the Logic Component Parts, the description
is made in the format exemplified by LG (NUMERIC), and
for algorithmic parts of the Logic Component Parts, by LG
(ALGO (AND))
Make a setting for each String item one by one in the orde
String = [PTDESC]
described on the top
String = range: [PVEULO] to
[PVEUHI], and [EUDESC]
String = gain: [K]
String = integration time: [T1] (min)
String = differential time: [T2] (min)
Used for indicating the end of a point type setting operation
}
by }
Hereafter describe settings for other point types in the same
…
way

− 213 −
Chapter 5. RTC Parts

Note •• Aspecification for PatternID is essential. If no settings are made for other items,
their respective default data is set.
•• If an unnecessary space or tab is included in the description following “= (equal),”
an error is caused.
•• If more than one description is made for settings for the same point type in a file,
the settings described below are used.
•• The point types that are not described in the imported files correspond to [Not
Show PointType] in [PointType Select] in 5.3.2.1, “Add/Modify/Copy Pattern.”

5.3.3 Setting Pattern for Individual Control Parts

Double-click a Control Part while pressing the [Shift] key, or right-click the Control Part and
select [Control Properties] from the pop-up menu that appears. Then the property sheet as
shown in Figure 5-43 is displayed.
When a Parameter View on a sheet is double-clicked, the property sheet as shown in Figure
5-44 is displayed.

Figure 5-42.

Figure 5-43.

− 214 −
 5.3 Parameter View

Figure 5-44.

•• Explanations of each item

Table 5-55.

Control Description
•• Currently set Parameter View patterns are displayed
•• For the Control Parts for which no Parameter View pattern
is set, “Invisible” is displayed
•• It is possible to set to registered patterns, or changed to
“Invisible” for them
[Pattern ID : Descriptor] •• Specify “Invisible” for a pattern and click the <OK> button
combo box Then the corresponding Parameter Views are deleted
•• Set a pattern where display details for the point types are
not set and click the <OK> button Then an error message
box is displayed
•• If patterns that have been set are deleted, “Invisible” is au-
tomatically set for these patterns when this page is opened
•• Check this box to follow Parameter View display positions
[Position]
to the one specified for the corresponding pattern
[It follows this pattern]
•• When a Parameter View is moved with the mouse, the box
check box
is automatically unchecked
•• Check this box to fix the display positions of the Parameter
[Position] Views on the sheet
[It is fixed on this sheet] •• Check this box Then even when Control Parts are moved,
check box the corresponding Parameter Views are not moved at the
same time
•• The settings made are saved and the corresponding
<OK> button
Parameter Views are updated
<Cancel> button •• The Parameter sheet is closed without anything done

5.3.4 Displaying/Not-displaying
Select [View] → [Parameter View] → [Show] from the job structure window or the sheet menu.
Then displaying and not-displaying Parameter Views can be switched.
When the menu is checked, they are displayed, and they are not displayed on any sheet when
the menu is not checked. Even when the menu is not checked, the Parameter View settings are
not deleted. When the menu is checked again, the former undeleted settings will be displayed.
If “Not Displayed” is set, no Parameter View will be displayed, even in RTC runtime.

− 215 −
Chapter 5. RTC Parts

MEMO

− 216 −
 Chapter 6. Implementing Harmonas-DEO System

Chapter 6. Implementing Harmonas-DEO System

Configuration information for operation screens can be created based on point parts that have
been arranged, wire-connected and configured on a sheet. A flow of operations is as shown
below.

Node Definition Imp History Definition explanatory notes

ort
(csv file) step 1 (csv file)
Input and Output of Files :
refer to "6.1.4.1" Exp
Node Setting refer to "6.2.2" work flow :
ort
refer to "6.1.4.1"
Import Export
step 6
step 2 History Setting History Items
Unit Definition
(csv file) Unit Setting
RTC_FB refer to "6.2.2" Definition Files
refer to "6.1.4.2" refer to "6.1.4.2"
step 7
step 3
Setting PMDP Local HS
Point Setting Variable
Export Parameter Entirely Install
Import Parameter refer to "5.2.5"/"5.2.6" refer to "6.2.1"
refer to "6.1.9"
step 4
Block Setting
EB Source Files refer to "5.2.7"/"5.2.8"
refer to "6.1.1" refer to "6.1.3"
refer to "6.1.2"
step 14
step 5 DB Load
step 8 Point Generation
Create Control Box refer to "2.7.2"
Date Files refer to "6.1.5"

refer to "6.1.8"
step 9 step 14
Create Control Point
Date Files step 13 Create Graphic Display
Loading Control Box
refer to "6.1.8" Create System refer to "2.7.3"
Date Files
Date Files
refer to "6.3.2" Create Group Display
refer to "6.2.5"
Loading Control Point refer to "3.4.1"
Date Files step 14
Create Trend Display
refer to "6.3.2" Starting up SE Program
refer to "3.13"
refer to "3.2.1"

step 10 step 11 step 15

CL Programs Compiling CL Programs Starting up Viewer
refer to "5.2.9" refer to "5.2.9.8" refer to "3.1"

step 15
step 12
Starting up Display
Loading CL Programs
Controller refer to "3.1"
refer to "5.2.9.9"

note : For , Refer to "DOSS Use's Guide (MS2-DEO300-2003)"

Figure 6-1. Engineering Flow

− 217 −
Chapter 6. Implementing Harmonas-DEO System

■
■Create System Definition Information

Step 1 Node configuration should be set for the node definition information of the entire
system. In addition the FB point is also defined for the XPC, PL2, FLC, FC and
PC4 [R411 or later] Controller. In this case, importing node definition information
from the CSV file can also make a batch setting possible.

Step 2 Unit configuration should be set for the unit definition information of the entire
system. In this case, importing unit definition information from the CSV file can
also make a batch setting possible.

■
■Create Point Information

Step 3 Point information is created based on the contents of the definition information
of point parts that have been arranged, wire-connected and configured on a sheet.
When this is the case, points can be created in a batch based on point information
created in CSV format as a point file and EB files created in EB source format.
Creating points based on information on created point parts then creates a point
database within RTC.

Step 4 XPC, PL2, FLC, FC and PC4 [R411 or later] Controller block information is cre-
ated based on the contents of the definition information of block parts that have
been arranged, wire-connected and configured on a sheet. Block information is
also to be used for EB source creation/reading. FB points are defined at Step1 to
manage multiple blocks.

Step 5 A point database is created within RTC by creating points based on information on
the point parts and block parts created.

Step 6 For history definition information, history collection cycles can be set per point pa-
rameter of created points. If a CSV file has been created as a history definition file,
the contents of history definition can be set as a batch. Created history information
can be collectively installed in the HS by outputting the history item definition file
(history.csv).

Step 7 PMDP local variables need to be set to display and change local variables (numeric
variables and flag variables) on a screen.

■
■Create and Load Controller Data Files

Step 8 Create control box data files from controller definition information created at
Step1 . This data file includes control function definitions, such as control points
for the controller, and I/O definitions such as I/O assignments. Loading this
box data file into a controller sets the controller’s control specifications and I/O
specifications.

Step 9 Create a controller point data file according to the point data base created at Step5 ,
and create setting data for each point. Loading this point data file into a controller
sets the specification of the control points and I/O points.
− 218 −
 Chapter 6. Implementing Harmonas-DEO System

■
■Create, Compile and Load CL File

Step10 A text editor such as notepad is used to create CL files. Using CL parts can reuse or
efficiently create CL files.

Step11 When created CL files are compiled, they are converted to a file format that can be
loaded to the controller.
If an error occurs during compilation, go back to Step10 and edit the CL file.

Step12 Load a load image of the created CL file into the controller by using a loader.

■
■Create System Data File

Step13 A system data file is created from the point database created at Step5 . The system
data file includes all information (node information, unit information, point in-
formation, alarm information, etc.) necessary for the SE program (HDSE.EXE) to
start with SS, HS, GS, and MS, and the point information necessary for monitoring
and operating data on the operation screen.

■
■Activate Operation Screen

Step14 Perform a DBLoad of the db.csv created as a system data file to InTouch, and then
read into InTouch the point information and history information to be referred to
on the operation screen. After this, on InTouch, create the graphic screen, the group
screen, and the trend screen needed for the operation screen.

Step15 When the screens have been created, start the SE program (HDSE.EXE) and then
activate the operation screen.

− 219 −
Chapter 6. Implementing Harmonas-DEO System

6.1 Creating Data to Be Loaded to the Controller

6.1.1 Creating the EB Source

EB source outputs the contents of parts configuration in text format. Since the EB source is a
text format file, it can easily be edited and read to RTC. This section describes how to create
an EB source. For how to read EB source, see 6.1.2.1, “Reading EB Source.”

In addition to EB source, the following files are created in EB source creation.

•• Backup File
If an EB source having the same name is found, save a file whose extension has been
changed to “bak”. This file is called the backup file.

•• Selection List
A selection list adds the extension “sl” to a specified file name. A selection list is a file that
compares the contents of the EB source (file whose extension is “eb”) and the contents of
the backup file (file whose extension is “bak”), and writes out only the Tag Name that have
a difference in their parameter settings. A selection list cannot be created alone. In order
to output a selection list, it is necessary to set “OutputSelectionList = TRUE” for [Browser]
section in the rtcedit.ini file. “OutputSelectionList = FALSE” is the default setting. In this
case, selection lists cannot be output.

■
■Target Parts for EB source creation
Target Parts for EB source creation are as follows:
•• Control Parts (Point)
•• Control Parts (Block)

Of these Parts, the following are not target Parts for EB source creation:
•• Container Parts
•• Link Parts
•• Divergence Parts
•• Job Parts, Intersheet Parts, and Intrasheet Parts
•• CL Parts
•• Logic Component Parts
•• Reference Parts
•• Frame Parts
•• Box Parameter Parts

Note Although Logic Component Parts and Reference Parts are not target Parts for EB
source creation, the configurations of these Parts are produced in the EB sources of
Logic Parts and Reference Parts, respectively.

− 220 −
 6.1 Creating Data to Be Loaded to the Controller

■ Source Creation Procedure

■EB

Step 1 Make the Job Structure Window active, choose [Implementation], and execute the
[Export EB Source] command.
The [Export EB Source] dialog then appears.

Figure 6-2.

Step 2 Select EB source output unit from the [Output Unit].

•• To create an EB source per sheet, select [Sheet Unit].
•• To create an EB source per point type or in FB slot units, choose [Point Type
Unit/FB Slot Unit].

The following steps are described divided into [Sheet Unit] and [Point Type Unit/
FB Slot Unit].

■
■Procedure for Creating EB Source in Sheet Units

Step 1 Select [Sheet Unit] and then select a sheet to be output from the Job Structure
Window. Sheets following the selected sheet are used for EB source creation.

Step 2 From [Sheet Information Output], select information added to the EB source.
•• When [Parts Coordinate Information] is selected
Add parts coordinate information on a sheet. The formats are as follows:

&X xxx
&Y yyy

Where xxx is the X coordinate of the upper left portion of the part (integer value
with a range of 0 to 380), and yyy is the Y coordinate of the upper left portion of
the part (integer value with a range of 0 to 272).

− 221 −
Chapter 6. Implementing Harmonas-DEO System

•• When [Sheet Hierarchy Information] is selected

Add sheet hierarchy information on the Job Structure Window. The following
format is used.

&S \SheetInfo

Where SheetInfo means sheet hierarchy information. This uses “\” to connect a
sheet name from the root sheet. However, the root sheet name is represented as
“root”. This always makes sheet hierarchy information start with “&S \root”.

Note To create an EB source to be used for reading the EB source in sheet

unit (for details, see 6.1.2.1, “Reading EB Source”), be sure to select both
[PartsCoordinate Information] and [Sheet Hierarchy Information]. An EB
source without that information cannot be read in sheet unit.

Step 3 Select the <Export> button and select an output destination. The output source is
the “eb” directory at the lower portion of the job directory by default. The file name
is determined as follows.
•• Sheet Name_?.eb

Where each character string has the following meaning.

•• Sheet Name : Sheet name
•• ? : Number that manages sheets by RTC editor.

■
■Point Type Unit/FB Slot Unit EB Source Creating Procedures

Step 1 Select [Point Type Unit/FB Slot Unit] and then select a node to be output from
[Node List].

Step 2 From [Point Type], select point types to be output. Multiple point types can be
selected at this time. A case where “FB” is selected as a point type has a meaning
different from that where other point types are selected.
•• When selecting a point type other than “FB”
This creates an EB source of the selected point type within the node.

•• When selecting an “FB” point type

This creates an EB source of block parts within the node. Selecting an “FB” point
type allows you furthermore to select on “FB Slot”. In this case, an FB slot number
defined within the node is displayed for “FB Slot”. Selecting a specific FB slot No.
from that display allows you to create only an EB source of block parts defined as
a specific FB slot.

− 222 −
 6.1 Creating Data to Be Loaded to the Controller

Step 3 Select the <Export> button and choose an output destination. The output destina-
tion is the “eb” directory at the bottom of the job directory by default. File names
are defined as follows.
•• NNNnnnPP.eb (point type unit)
•• NNNnnnFBsss.eb (FB slot unit)

Where character strings have the following meanings.

•• NNN : Node type
•• nnn : 3-digit node number
•• PP : Point type (Table 6-1)
•• sss : 3-digit FB slot number

Table 6-1.

PP Point Type PP Point Type

AI Analog Input NN Numeric
AO Analog Output TM Timer
DI Digital Input PM Process Module
DO Digital Output VI VALIN
DC Digital Composite VO VALOUT
CT Regulatory Control FFFB FFFB
Numeric Array
PV Regulatory PV NAR
[R411 or later]
FB Function Block STR String [R411 or later]
LB Logic DT Datetime [R411 or later]
FL Flag

− 223 −
Chapter 6. Implementing Harmonas-DEO System

6.1.2 Reading EB Source

This section describes reading in an EB source and the automatic wiring performed when an
EB source is read.

6.1.2.1 Reading EB Source

The EB source reading function creates parts and sets parameter values by reading EB source
given in text format. This function can read not only EB sources created by the EB source
creation function of RTC (for details, see 6.1.1, “Creating the EB Source”), but also edited EB
sources.

■ Source Reading Procedure

■EB

Step 1 Make the Job Structure Window active and execute the [Import EB Source] com-
mand from [Implementation]. The [Import EB Source] dialog will appear.

Figure 6-3.

Step 2 Select EB sources to be read from [File Name]. Multiple EB sources can be speci-
fied. To read an EB source for a specific sheet (read EB source in sheet units), select
[Sheet Unit]. EB sources specified here need to be an EB source including sheet
hierarchy information and parts coordinate information.

Note In EB sources, definition of each part needs to start with “&T”. Even if the
definition of only one part does not start with “&T”, the EB source cannot
be read correctly.

Note

− 224 −
 6.1 Creating Data to Be Loaded to the Controller

Note Reading EB sources in sheet unit requires sheet hierarchy information

and parts coordinate information to have been specified in the EB
sources. Files with their sheet hierarchy information and parts coordi-
nate information not specified cannot be read in sheet unit.

Step 3 Click the <Import> button to start reading EB sources.

Step 4 This process sets EB source data in parts. If the parts are not found, they are newly
created. If inter-part information has been set in EB /urces, a link is automatically
connected between parts according to the connection information (see 6.1.2.2,
“Automatic Wiring”).

Step 5 The results of the read are displayed in [Status:].

■
■Checking to read EB source
If EB sources have incorrect contents, an error or warning will appear. For a part where an
error occurs, the EB source is not read. However, if an error occurs when automatic wiring
cannot be done, parts are created but no link is connected. When a warning occurs, the EB
reading continues.

<In case of error>

•• When no definition can be read normally
•• When the point type/block type (&T) cannot be read or is not supported

Table 6-2.

Part Type Supported Point Type/Block Type

Point Parts (PRC / XPC / FLC) AI / AO / DI / DO / DC / RP / RC / LG / FL / NM / TM / PM
Point Parts (PL) AI / AO / DI / DO / VI / VO/ DC / LG / FL / NM / VI / VO
AI / AO / DI / DO / VI / VO / DC / RP / RC / LG / FL / NM
Point Parts (PL2)
/ TM / PM
AI / AO / DI / DO / VI / VO / DC / RP / RC / LG / FL / NM /
Point Parts (FC)
TM / PM / FFFB
AI / AO / DI / DO / DC / RP / RC / LG / FL / NM / NAR /
Point Parts (PC4) [R411 or later]
STR / DT / TM / PM
ADD / SUB / MUL / DIV / MOD / SUM / DADD / ABS /
SQR / SQRT / LN / LOG / EXP / EXPT / SIN / COS / TAN
/ ATAN / TRUNC / ROUND / MAX / MIN / AVG / HSE /
LSE / MID3 / SW / SFT / ALSW / HLM / LLM / DRL / HMS
/ LMS / DRM / DMS / NUMCHK / BADCHK / INFCHK /
Block Parts (XPC / PL2 / FLC / QLTCHK / CHGCHK / PTE / ETP / FUNC / AND / OR /
FC) / PC4 [R411 or later] NOT / NAND / NOR / XOR / QOR2 / SR / RS / EQ / NE /
GT / GE / LT / LE / FIXPLS / MAXPLS / MINPLS / CYCPLS
/ WDT / DELAY / ONDLY / OFFDLY / UCNT / DCNT /
AAV / PAV / PID / PRO / INT / DIF / LDLG / DED / TF /
RMP / MAV / ANMA / GW / CONV / SG / FL / DLTPV /
TIMFL / ANDIN4 / ORIN4 / PSQRT / REDTAG

− 225 −
Chapter 6. Implementing Harmonas-DEO System

•• When the tag name (&N) cannot be read or is out of the set range

Table 6-3.

Part type Number of characters in tag name

Point part 1- 16 characters
Block part 1 - 16 characters

•• When the node type (NODETYPE) cannot be read or is not supported

Table 6-4.

Part type Node type supported

Point part PRC/PL/XPC/PL2/FLC/FC/PC4 [R411 or later]
Block part XPC/PL2/FLC/FC/PC4 [R411 or later]

•• When the node number (NODENUM) cannot be read or is out of the set range

Table 6-5.

Part type Node number setting range

Point part 1 - 126
Block part 1 - 126

•• When slot number (SLOTNUM) cannot be read or is out of the set range

Table 6-6.

Point type / Block type Slot number setting range

1 - 16 (PRC/PL/XPC/PL2/PC4 [R411 or later]), 1 - 8 (FLC), 1 -
AI
127 (FC)
1 - 16 (PRC/PL/XPC/PL2/PC4 [R411 or later]), 1 - 8 (FLC), 1 -
AO
127 (FC)
1 - 32 (PRC/PL/XPC/PL2/PC4 [R411 or later]), 1 - 16 (FLC),
DI
1 - 127 (FC)
1 - 32 (PRC/PL/XPC/PL2/PC4 [R411 or later]), 1 - 16 (FLC),
DO
1 - 127 (FC)
VI 1 - 8 (PL/PL2), 1 - 64 (FC)
VO 1 - 8 (PL/PL2), 1 - 64 (FC)
1 - 255 (PRC), 1 - 512 (PL), 1 - 1024 (XPC/PC4 [R411 or later]),
DC
1 - 1600 (PL2/FC), 1 - 256 (FLC)
1 - 80 (PRC), 1 - 320 (XPC/PC4 [R411 or later]), 1 - 480 (PL2/
RP
FC), 1 - 32 (FLC)
1 - 160 (PRC), 1 - 640 (XPC/PL2/FC/PC4 [R411 or later]), 1 - 32
RC
(FLC)
1 - 80 (PRC), 1 - 128 (PL), 1 - 320 (XPC/PC4 [R411 or later]),
LG
1 - 480 (PL2/FC), 1 - 64 (FLC)
1 - 1023 (PRC), 1 - 3072 (PL),
FL
1 - 8192 (XPC/PL2/FC/PC4 [R411 or later]), 1 - 3000 (FLC)

− 226 −
 6.1 Creating Data to Be Loaded to the Controller

Point type / Block type Slot number setting range

1 - 2047 (PRC), 1 - 3072 (PL), 1 - 8192 (XPC/PL2/FC),
NM
1 - 3000 (FLC), 1 - 9999 (PC4) [R411 or later]
NAR [R411 or later] 1 - 240 (PC4)
STR [R411 or later] 1 - 128 (PC4)
DT [R411 or later] 1 - 128 (PC4)
1 - 64 (PRC), 1 - 256 (XPC/PL2/FC), 1 - 32 (FLC), 1 - 768 (PC4
TM
[R411 or later])
1 - 160 (PRC), 1 - 512 (XPC/PL2/FC), 1 - 572 (PC4) [R411 or
PM
later], 1 - 128 (FLC)
FFFB 1 - 127
All block type 1 - 511 (XPC/PL2/FC/PC4 [R411 or later]), 1 - 128 (FLC)

•• When the module number (MODNUM) cannot be read or is out of the set range

Table 6-7.

Part type Module number setting range

1- 40 (PRC), 1 - 80 (PL), 1 - 120 (XPC/FC/PC4 [R411 or later]),
Point part
1 - 240 (PL2), 1 - 24 (FLC)
Block part Parameter is not found

•• When the block number (FBNO) cannot be read or is out of the set range

Table 6-8.

Part type Block number setting range

Point part Parameter is not found
Block part 1 - 8192 (XPC/PL2/FC/PC4 [R411 or later]), 1 - 2048 (FLC)

•• When the PTDESC parameter contains more than 24 characters

•• When the EUDESC parameter contains more than 8 characters
•• When any of the STATETXT (0) to STATETXT (2) parameters contains more than 8
characters
•• When data other than RED, GREEN, WHITE, BLACK, CYAN, YELLOW, BLUE or
MAGENTA is set for any of the BOXCLR (0) to BOXCLR (2) parameters
•• When automatic wiring cannot be done

The following cases will also cause error while reading in sheet unit.
•• When sheet hierarchy information (&S) cannot be read
•• Parts coordinate information (&X and &Y) cannot be read or is out of the range

Table 6-9.

Position information setting range

Part type
(X coordinate and Y coordinate)
Point part (0,0) - (380,272)
Block part (0,0) - (380,272)

− 227 −
Chapter 6. Implementing Harmonas-DEO System

■
■Setting EB Source in Parts
Data of read EB source is reflected to parts. Reflection to EB sources differs depending on
whether or not reading is specified in sheet unit.

<When reading is specified in sheet unit>

Data is reflected to only the sheet specified by the sheet hierarchy information. If the same
parts are found in a specified sheet, the sheet is overwritten. If the same parts are not found in
a specified sheet, parts are newly created and then the EB source is reflected to them.

<When reading is not specified in sheet unit>

Data is reflected to all sheets in a job. If the same parts have already been found within a job,
sheets are overwritten. If the same parts are not found in a job, new parts are created, and then
the EB source is set in the parts.
The following criteria are applied to a judgment on whether or not the parts are the same.
•• Point parts
When the tag name and the point type are the same

•• Block parts
When the tag name and the algorithm type are the same

Note For logic points, an EB source that has been read is reflected to the logic parts as
in the case of other point types. However, the following warning applies to Logic
Component Parts (AND, OR, etc.):
•• If the corresponding Logic Component Part has already been found on the Sheet,
the EB source of the Logic Part is also set for the Logic Component Part.
•• If the corresponding Logic Component Part is not found on the Sheet, no new
Logic Component Part is created.

■
■Arrangement of New Parts on Sheet
When new parts are created, a new sheet is generated for arranging new parts. Sheet creation
and parts arrangement are automatically carried out according to the following rules.

Note While reading in sheet units, if a sheet to be read already exists, a new sheet is not
generated. If that sheet to be read does not already exist, a new sheet is generated
according to the sheet hierarchy information. In this case, container parts are cre-
ated at equal intervals on the sheet. Point parts and block parts are created on a
sheet specified by the sheet hierarchy information according to the parts coordi-
nate information. The following rules are therefore not applied to them.

− 228 −
 6.1 Creating Data to Be Loaded to the Controller

•• New parts created are divided into the following two types, each of which is arranged on a
different sheet.
– Parts for which automatic wiring does not need to be done
– Parts for which automatic wiring needs to be done

Therefore, there is no case where new parts of the above two types are arranged on the same
sheet.

•• All sheets are to be created directly under the root sheet. The names of sheets to be created
share the same sheet name format [EBReadXX], regardless of whether or not wiring is
needed, where “XX” is assigned from “01” in the order of sheets created. If the same sheet
name already exists, a default name determined by RTC is assigned.

•• Parts are arranged on a sheet in the order shown below. The order in which parts are ar-
ranged is the order in which they are written on the EB source. A maximum of 100 parts are
arranged on a sheet. If the number of parts created exceeds the maximum number, a new
sheet is created to arrange the succeeding parts.

EBRead01
Newly Created Parts
1 2 3 ••• 9 10

11 12 13 ••• 19 20

21 22 ••• Newly Created Sheet

Figure 6-4.

Note If EB sources are to be read in sheet units, a sheet may take a different position in
a created sheet layer before and after it is read. In such a case, select a sheet to be
moved, and move the sheet up or down for position alignment by choosing [View]
→ [Move Container Up] menu or [Move Container Down] menu.

− 229 −
Chapter 6. Implementing Harmonas-DEO System

6.1.2.2 Automatic Wiring

Automatic wiring refers to the function that links parts automatically based on parameter
information regarding the EB source link (e.g. CISRC(1) = A100.PV, etc.). Automatic wiring
will be performed automatically through the EB source reading process (see 6.1.2.1, “Reading
EB Source”).

■
■Automatic Wiring Procedure
Parts subject to automatic wiring are arranged according to the following rules.

Note Selecting [Sheet Unit] creates parts on a sheet specified by sheet hierarchy informa-
tion according to the parts position information. The following rules are therefore
not applied in that case.

•• “Parts newly created and subject to automatic wiring” by reading in the EB source will be
arranged on a sheet as follows. Linked parts are considered as a group and arranged together
on a sheet.

EBRead02
Linked parts are
1 2 3 ••• 9 10
grouped and arranged.
11 12 13 ••• 19 20

21 22 The next group is put

in a new line.
1 2 3 ••• 9 10

11 12

Figure 6-5.

•• There are no strict rules for sequencing groups on a sheet or parts in a group. Basically, how-
ever, a sequence in a group will follow the sequence of parts written in the EB source and the
parts will be arranged on a sheet so that link lines are not unduly complicated.

•• Up to ten lines of parts will be arranged on a single sheet (ten parts per line at maximum).
When the number of lines exceeds the limit, a new sheet will be created to arrange the rest of
the parts. In this case, parts in a group will not be divided; the entire group will be arranged
on the next sheet. However, if the number of parts in a group exceeds 100, the excess parts
will be arranged on another sheet.

− 230 −
 6.1 Creating Data to Be Loaded to the Controller

Even when [Sheet Unit] is selected, automatic wiring will be performed according to the fol-
lowing rules.

•• Automatic wiring will be performed for both newly created and existing parts.

•• In the following cases, automatic wiring will not be performed. In those cases, error status
will appear with parameter names on both sides of a link in the [Status:] list of the [Read EB
Source] dialog. Causes of the error will not be displayed.
– There are no parts or parameters to be wired.
– Parts are arranged on separate sheets. The RTC does not support wiring that requires a
Intrasheet Parts between sheets.
– Parameter values of the parts cannot be linked (e.g., their data type are different).

Restriction The RTC does not support automatic wiring of logic points. (However, you can set
parameters of link information for logic parts as well as for other parts.)

Note Even if parameter links are not used for linkage on an original sheet when EB is read,
and points to be linked by a parameter link after EB is read exist on the same sheet,
the parameter link is automatically wired.

Note The configurations of Logic Component Parts and Reference Parts are not produced
in the EB sources. Therefore, these Parts are not targets of automatic wiring.

■
■Shapes of links
The shapes of links drawn in automatic wiring vary depending on the status of the horizontal/
vertical button.

Table 6-10. Status of Horizontal/Vertical Button and Shapes of Links

Horizontal/Vertical Button Shapes of Links

Not pressed Linear links with no deflection points
Pressed Links consisting of horizontal/vertical lines

Note No information on the shapes of links is produced in the EB source.

Therefore, the shapes of links drawn in automatic wiring are not the same as those
of the links drawn at the time of creation of the EB source.

− 231 −
Chapter 6. Implementing Harmonas-DEO System

6.1.3 Configuration of Block Information

In addition to points, the XPC, PL2, FLC, FC and PC4 [R411 or later] controller can make
configurations in control units furthermore divided, called “blocks”.
Configuration procedures and notes on block information are described here. For details, see
each relevant section.

■
■Concept of FB Point and Block
•• A “Block” is a more detailed control unit than a point. The types of parts prepared are de-
scribed in Section 5.2.7, “Block Parts.”

•• Because the number of Blocks has increased, a “Function Block Point” (FB Point) has been
added to manage multiple Blocks as a single unit. It is required that each Block be included
in one FB Point or another.

•• The control cycle can be set for each of the FB points. In each controller, the blocks are pro-
cessed in FB point units according to the control cycle that has been set.

Controler (Node#001)

AI Point Type

AO Point Type
.
.
.

RegPV Point Type

RegCTL Point Type

FB Point Type

FB Point (Slot#001)

FB Point (Slot#002)

Block (Block#001)

Block (Block#002)
.
.
.

FB Point (Slot#123)
.
.
.

Figure 6-6.

− 232 −
 6.1 Creating Data to Be Loaded to the Controller

■
■Block Configuration Procedure

Step 1 Define the XPC, PL2, FLC, FC and PC4 [R411 or later] nodes. The nodes are de-
fined from the [System Configuration] property sheet. The definition method is
basically the same as that of PRC and PL. For details, see Section 6.1.4

Step 2 Define FB points. There are no parts equivalent to the FB point in RTC. FB points
are all defined from the [System Configuration] property sheet. For the definition
procedures, see Section 6.1.4.3

Step 3 Create a logic diagram using block parts. Arrange the block parts onto a sheet from
“Control Parts (block)” in the parts bar and link the parts. Block parts and point
parts can also be linked. For parameters that can be linked with blocks, see Section
5.2.7, “Block Parts.” Block parameters are set from property settings of parts. Basic
operations for block parts are basically same as those for point parts. For details on
block parts, see Section 5.2.7.

Step 4 Assign blocks to FB points. Individual blocks need to be included in one of the FB
points to be managed. To assign blocks arranged on a sheet to specific FB points,
choose “Apply FB Point” from [FB Point Configuration] property page of [System
Configuration]. If an FB point is defined, slot numbers of all blocks belonging to
the specified page are changed to the slot numbers for the specified FB point. Since
the following “relationship between FB point/block and sheet” exists between the
FB point/block and the sheet, configuration of blocks should be made according to
the contents shown in this section.

Step 5 Generate points. Information on configured FB points and blocks is created by

“Point Generation”. For point generation, see Section 6.1.5. Generating points also
creates information on FB points and blocks together with information on nodes
and points.

Step 6 Create a controller data file (file for loading to controller). FB point information
and block information created by generating points, together with other point
information, like output to the “Point” controller data file. For details, see Section
6.1.8.

Step 7 Load FB point and block data to the controller. Choose the [Load Controller
Program/Data] dialog to load the FB point and block data. The data type of the file
to be loaded is “Point”. Data can be loaded in “Node Units” or “Point Units” (FB
point units). Loading FB points loads the block information included in them.

Step 8 For other functions of uploading block information and browsing block informa-
tion, see the relevant sections.

− 233 −
Chapter 6. Implementing Harmonas-DEO System

■
■Number of Slots and Blocks of Configurable FB Points
•• Following Table shows the number of slots and blocks at configurable FB points.

Table 6-11.

Parameter Maximum Configurable Number

Maximum number of slots at FB point XPC/PL2/FC/PC4 [R411 or later]: 511, FLC: 128
Maximum number of blocks at FB points XPC/PL2/FC/PC4 [R411 or later]: 8192, FLC: 2048
Maximum number of blocks per node XPC/PL2/FC/PC4 [R411 or later]: 16383, FLC: 2048

■
■Relationships between FB Point/Block and Sheet
•• RTC holds two pieces of data: the “Node Number” and the “FB Slot Number”. The “Node
Number” can be set by <Apply Node>, and the “FB Slot Number” by <Apply FB Point>,
both in the [System Configuration].

•• In generating points, when block information is generated, only those block parts on a sheet
where data on node numbers and FB slot numbers specified in the point generation have
been set, are the objects of point generation. For a sheet where blocks exist, node and FB
points should therefore be specified from the [System Configuration] without fail.

•• Only blocks at the same FB point are allowed to be placed on the same sheet. That is, blocks
at different FB points cannot be placed on the same sheet.

•• Multiple sheets can be specified for the same point. That is, blocks at the same FB point can
be placed on multiple sheets.

•• The above constraints (relationships between FB point/block and sheet) are not applied to
point parts. Blocks and point parts can also be mixed and placed on the same sheet.

− 234 −
 6.1 Creating Data to Be Loaded to the Controller

6.1.4 System Configuration

Information on the installation can be set, including the controller nodes and module
configuration.

■
■Operation Procedure
Choose [Implementation] → [System Conf] from the menu in the job hierarchy diagram.
Choosing this command displays the [System Configuration] property sheet. In the [System
Configuration] property sheet, the following page is related to hardware configuration. This
section details the following items.

•• System Conf
•• Unit ID
•• FB Point Configuration
•• I/O List
•• Control List
•• PU/MU

6.1.4.1 System Conf

This function sets the node configuration. You can use the following functions.
In addition, please refer to Appendix A, “The setting parameter of the node” for the details of
setting contents.

■
■Node List
Nodes defined in job are listed in the [Node List] list box. “Node Number : Node Type” is used
for the node format in which nodes are listed.

■
■Add Node
Click the <Add Node> button to display the [Add Node] property sheet. Add new configura-
tions on this property sheet. The following pages are displayed on the [Add Node] property
sheet, depending on the types of node.

Note Be sure to set not only the controller nodes but also the SS nodes. If the local node
has not been defined in online screen activation, the operation will end in an error.

Note The number of the MS node is to one in a system. Therefore, please define one MS
node when you add MS node.

Note [R411 or later]

MS node and HL node are not supported in [R411 or later]. Therefore adding new
MS/HL node is not available.

■
■Edit Node
Select a node to be changed from the node list, and click the <Edit Node> button to display
the [Edit Node] property sheet having the same contents as the [Add Node] property sheet.
The configuration of the node can then be changed. Once “NODETYP” has been set, it can-
not be changed.
− 235 −
Chapter 6. Implementing Harmonas-DEO System

■
■Delete Node
Select a node to be deleted from the node list, and click the <Delete Node> button (after con-
firming whether or not you want to delete it) to delete a registered node. Deleting a node also
deletes point information assigned to the node. A node deleted disappears from the node list.

Note This operation cannot be undone.

■
■Apply Node
Set node numbers all at once for all point parts defined under a container selected on a job
hierarchy diagram. A higher priority is given to operations performed later.

Note This operation cannot be undone.

■
■Import
Importing a file in CSV format can set all at once node information. With the controller
supporting FB points, the import of the FB point is possible. The formats of the CSV file are
different by node type. In addition, please refer to Appendix A, “The setting parameter of the
node” for CSV format.

Note When a unit ID is defined as a value of BOXUNIT in the CSV file used for node defini-
tion import, an error can occur. By defining the corresponding unit ID in the unit
definition (refer to section 6.1.4.2) prior to the node definition import, this error can
be avoided.

■
■Export
The export function outputs node information defined by a job in a CSV file every node. The
CSV file which exported can import.

■
■Import I/O Configuration
Importing a file in CSV format can set the I/O configuration all at once. This function sup-
ports PRC, PL, XPC, PL2, FLC, FC and PC4 [R411 or later]. The operation procedure is as
follows.

Step 1 Open [Add Node] or [Edit Node] property sheet in the [System Configuration]
dialog.

Step 2 Switch the tab of the displayed property sheet and display the [IOM Conf 0] page.

Step 3 Click the <Import> button.

Step 4 When the [Setup FileNames] dialog appears, specify a file to be imported.

Step 5 Click the <Open> button to start import processing.

− 236 −
 6.1 Creating Data to Be Loaded to the Controller

Step 6 When import is completed, the completion is announced in the message box. If
an error occurs during import, an error message file named “cdlstimp.err” will be
generated in the same directory as that where the imported CSV file exists.

•• CSV File Format

Module #, FileA#, CardA#, IOMType, FailOpt, FREQ6050, RedunOpt, Fi;eB#,
CardB#, SegID, FLMType, IOMRate

<Example>
For the following assignments
[Module # : 2, FileA# : 2, CardA# : 1, IOMType : HLAI, FailOpt: UNPOWER,
FREQ6050 : SIXTYHZ, RedunOpt : REDUN, FileB# : 2, CardB# : 2, SegID : 0,
FLMType : NONE, IOMRate : DEPENDS]

2,2,1,HLAI,UNPOWER,SIXTYHZ,REDUN,2,2,0,NONE,DEPENDS

The first line is considered to be a comment line and is not to be imported.

Note In the case of PRC, only DEPENDS can be set as IOMRATE.

Note FREQ6050 is not used at present. Therefore, even if FIFTYHZ or SIXTYHZ

is specified when IOM Type is STIM, LMUX, or TCAI, it does not function.

■
■Export I/O Configuration
The currently set contents of IOM configuration page are output with a file given in the format
described in Import. The operation procedure is as follows.

Step 1 Click the <Export> button. This operation will display the [Setup Directory]
dialog.

Step 2 Specify an output destination directory and click <OK>. By default, the cardlist
directory just under the job directory is specified.

Step 3 The set contents are output to the specified directory. The file name is “CARDnnn.
csv” (where nnn is a node number). The file name cannot be changed during
output.

− 237 −
Chapter 6. Implementing Harmonas-DEO System

6.1.4.2 Unit ID
Define unit ID on the [Unit ID] page selected from the [System Configuration] property sheet.
The [Unit ID List] list box is displayed at the center of the page. Unit ID defined in this box
are listed in numerical order.

■
■Add Unit
Unit definitions can be added. The operation procedure is as follows:

Step 1 Click the <Add> button. This operation will display the [Add/Edit Unit ID] dialog.

Step 2 In the [Add/Edit Unit ID] dialog, enter the [Unit ID] and [Descriptor] correspond-
ing to the [Unit Number] to their relevant boxes.
A unit number is given with an integer ranging from 1 to 500, a Unit ID, an ar-
bitrary two alphanumeric characters, and a Descriptor, up to 24 characters. The
<OK> button is kept shaded until an effective setting is made.

Step 3 After completing the setting, select <OK> to exit the [Add/Edit Unit ID] dialog.
Then a unit added and set will also be displayed in the [Unit ID List] list box.

■■ Edit Unit
Change unit definitions. The operation procedure is as follows.

Step 1 Select a line of the unit definition to be changed from the [Unit ID List] list box.
When the <Edit> button becomes effective, press this button. This will display the
[Add/Edit Unit ID] dialog.

Step 2 In the [Add/Edit Unit ID] dialog, enter [Unit ID] and [Descriptor]. The unit num-
ber cannot be changed (displayed in reduced shade).

Step 3 After the completion of the settings, select <OK> to exit the [Add/Edit Unit ID]
dialog. The changes will be reflected to the [Unit ID List] List box.

■
■Delete Unit
Unit definitions can be deleted. The operation procedure is as follows.

Step 1 Select a line of the unit definition to be deleted from the [Unit ID List] list box. At
this time, the Ctrl key and Shift key are available to specify multiple units. Then
click the <Delete> button. This will display an acknowledgement message.

Step 2 In response to the acknowledgement message, select <OK> to delete the line from
the [Unit ID List] list box.

− 238 −
 6.1 Creating Data to Be Loaded to the Controller

■
■Apply Unit ID
On a job hierarchy diagram, set Unit ID, all at once, for all point parts defined under the
selected container.

Note If a container is not selected on a job hierarchy diagram, an error message will
appear.

■
■Import
Importing a CSV format file can set a unit number, a unit ID, a descriptor, and unit configura-
tion for each node at a time. The operation procedure is as follows.

Step 1 Click the <Import ...> button on the [Unit ID] page.

Step 2 When the [Setup FileNames] dialog, specify a file to be imported.

Step 3 Click the <Open> button to start import processing.

Step 4 When import is completed, the completion is notified in the message box. If an
error occurs during import, an error message file named “unitimp.err” will be
generated in the same directory as that where the imported CSV file exists.

•• CSV File Format

Unit No., Unit ID, Descriptor, Node No., index of BOXUNIT, Node No., index of
BOXUNIT, ... (similar items can be specified, if necessary)

<Example>
For the following assignments
[Unit No.1, Unit ID AA, Descriptor DDD, Node No.27 BOXUNIT (1), Node
No.126 BOXUNIT (30)]

001,AA,DDD,27,1,126,30

The first line is considered to be a comment line and is not to be imported.

Note If the Node number and BOXUNIT index has been set in a Unit ID im-
port CSV file with a Unit ID imported, the corresponding node needs to
have been already defined on the [System Conf] page of the [System
Configuration]. If the corresponding node has not yet been defined, an
error occurs, and the Unit ID will not be added or updated.

To prevent the above problem, perform the following procedures.

1. Open the Unit ID import CSV file by Memo Pad.
2. From each piece of unit information, delete the node information
parts related to the Node numbers not defined by the job.
3. Save the Unit ID import CSV file and exit Memo Pad.
4. Perform processing for importing the Unit ID.

− 239 −
Chapter 6. Implementing Harmonas-DEO System

■
■Export
The contents of current settings on Unit ID page and unit configuration page for each node
are output in a file format described in Import.

Step 1 Click the <Export> button on the [Unit ID] page.

Step 2 When the [Create CSV File] dialog appears, specify a file name.

Step 3 Click the <Save> button to start export processing.

6.1.4.3 Set FB Point

Define FB points on the [FB Point Configuration] selected from the [System Configuration]
property sheet.The [Node List] list box is displayed at the upper left of the page. FB points
defined for the selected node are displayed in the [FB Point List] at the bottom of the page in
order of their slot numbers.

■
■Add FB Point
Definitions of the FB points can be added. The operation procedure is as follows.

Step 1 Click the <Add FB Point> button. This will display the [Add/Modify FB Point]
dialog.

Step 2 In the [Add/Modify FB Point] dialog, set a Slot number, Tag Name, Unit ID,
LoopRate and Descriptor as follows.

•• Slot numbers are integers ranging from 1 to the number of the function block
slots set on the [Node Conf 1] page for node definition.
•• A tag name has up to 16 arbitrary alphanumeric characters.
•• The Unit ID is set on the [Unit ID] page.
•• The control cycle is selected from 1SEC, 500MS, 200MS and 100MS.
•• A descriptor has up to 24 characters.

Step 3 After the completion of settings, select <OK> to exit the [Add/Modify FB Point]
dialog. The additionally set FB points are then added to and displayed in the [FB
Point List].

■
■Modify FB Point
The definition of FB points is changed. The operation procedure is as follows.

Step 1 Select a line of FB point definitions to be changed from the [FB Point List] list box.
When the <Modify FB Point> button becomes valid, click the button. This opera-
tion will display the [Add/Modify FB Point] dialog.

Step 2 In the [Add/Modify FB Point] dialog, change a Tag Name, Uunit ID, LoopRate and
Descriptor.
Slot numbers cannot be changed (displayed shaded).

Step 3 After the completion of setting, select <OK> to exit the [Add/Modify FB Point]
dialog. The changes will be then displayed in the [FB Point List] list box.

− 240 −
 6.1 Creating Data to Be Loaded to the Controller

■
■Delete FB Point
FB point definitions can be deleted. The operation procedure is as follows.

Step 1 Select a line of FB point definition to be deleted from the [FB Point List] list box. At
this time, the Ctrl key and Shift key are available to specify multiple FB points. Then
click the <Delete FB Point> button. This will display an acknowledgement message.

Step 2 In response to the acknowledgement message, select <OK> to delete the line from
the [FB Point List] list box

■
■Apply FB Point
On a job hierarchy diagram, set the slot numbers of the FB points, all at once, for all block
parts defined under the selected container.

Note If a container is not selected on a job hierarchy diagram, an error message will
appear.

Note If you perform point DB generation with the [FB Point Configuration] page kept
open, the data on the [FB Point Configuration] page is not updated in real time.
When you have performed point DB generation, close the [System Configuration]
dialog box once and open it again.

6.1.4.4 I/O List

On an [I/O List] page selected from the [System Configuration] property sheet, the I/O point
list can be displayed in modules. Only points that have been point-generated are displayed in
this list.

■
■Node List
A node list the same as that on the [System Conf] page is displayed. From this list, select a list
whose I/O list you want to display.

■
■Module List
A list of modules defined in nodes selected from the node list is displayed in the following
format.
“IOM Number IOM Type”

IOM number indicates a logical address displayed at the far left of the [IOM Conf] page and
does not directly correspond to the hardware address (physical address) displayed by file# and
card#. From this list, select modules whose I/O list you want to display.

− 241 −
Chapter 6. Implementing Harmonas-DEO System

■ List
■I/O
A list of I/O points included in the nodes and modules selected from [Node List] and [Module
List] is displayed in the format of “Slot Number, Tag Name, Point Descriptor”. In this case, the
number of slot numbers displayed is up to the maximum number of slots, including idle slots.
If the connection destination is defined in the “!MTmmSss. parameter” format or
“!MTmmmSss. parameter” format, “[tag name.parameter name of connection source point] is
displayed at the tag name position of the corresponding connection destination slot number.
In this case, if multiple same connection destinations are specified, the first one found will be
displayed.
However, a displayed connection destination is limited to one whose point is not tagged.
Priority is given to the display of a tagged connection destination.
If, for example, DC001.DISRC(2) = !DI03S05.PVFL is defined, “[DC001.DISRC(2)]” is dis-
played at the position of module No.3 and slot No.5 of [I/O List].
Combinations of point types of connection destinations and sources are limited to the cases
in following Table.

Table 6-12.

Point type of connection destination Point type of connection source

AO RegCtrl
DI DC
DO DC, RegCtrl

■
■Save
The current set contents are saved in CSV format files. By default, data is output to a directory
named plist, just under the job directory. However, the directory can be changed by the dialog
displayed by clicking the <Save> button. The file name is SLTnnnPP.CSV (SLT is a prefix, nnn
is a node number, and PP is a point type), and cannot be changed when the file is output.

Table 6-13.

XX Point Type XX Point Type

AI Analog Input DI Digital Input
AO Analog Output DO Digital Output
VI Value input VO Value output
FF FFFB

− 242 −
 6.1 Creating Data to Be Loaded to the Controller

Table 6-14.

Line No. Description

The following character string is output as a headline of a value out-
put to the 2nd line
1. For Node type PRC/XPC/FLC/PC4 [R411 or later]
“File#”, “Card#”, “Node Type”, “Node#”, “Module Type”, “Module#”
Meaning: a file No., card No., node type, node No., module type
1st line (headline)
and module No. in order.
2. For Node type PL/PL2/FC
“File#”, “PLC#”, “Node Type”, “Node#”, “Module Type”, “Module#”
Meaning: I/O subsystem No., PLC station No., node type, node
No., module type and module No. in order.
2nd line (value) Output a value equivalent to the value on the 1st line.
The following character string is output.
3nd line (headline)
“Slot No.”, “Tag name”, “Point Descriptor”
Values equivalent to the items in the 3rd line are output in the order
4th line or later (value)
of slot numbers

Afterwards, this display format is repeated for each of Card#, Sub# and PLC#. At this time,
data is saved sorted in the ascending order for each of File#, Card#, Sub# and PLC#.

Note If you perform point DB generation with the [I/O List] page kept open, the data on
the [I/O List] page is not updated in real time. When you have performed point DB
generation, close the [System Configuration] dialog box once and open it again.

6.1.4.5 Control List

A list of control points is displayed for each of the nodes and for each of the control slot types
on the [Control List] page selected from the [System Configuration] property sheet. Only
points that have been point-generated are displayed in this list.

■
■Node List
A list of nodes similar to that on the [System Conf] page is displayed. From this list, select
nodes whose control list you want to display.

■
■Control Slot Type
Select control slot types from among the following.
Digital composite, adjustment control, adjustment PV, logic, flag, numeric variable, string,
timer, process module, function block.

■
■Control List
The list of the control points meeting the conditions selected in [Node List] and [Control Type
Slot] is displayed in the format named “slot name tag name point descriptor”. At this time, the
number of slot numbers displayed is up to the maximum number of slots including idle slots.

■
■Save
The current set contents are saved in CSV format files. By default, data is output to a directory
named plist, just under the job directory. However, the directory can be changed by the dialog
displayed by clicking the <Save> button. The file name is SLTnnnPP.CSV (SLT is a prefix, nnn
is a node number, and PP is a point type), and cannot be changed.
− 243 −
Chapter 6. Implementing Harmonas-DEO System

Following Table shows relationships between the point type and the point type used for file
name.

Table 6-15.

XX Point Type XX Point Type

DC Digital composite NN Numeric variable
CT Adjustment control TM Timer
PV Adjustment PV PM Process module
LB Logic NAR Numeric Array [R411 or later]
FB Function block STR String [R411 or later]
FL Flag DT Datetime [R411 or later]

Note If you perform point DB generation with the [Control List] page kept open, the data
on the [Control List] page is not updated in real time. When you have performed
point DB generation, close the [System Configuration] dialog box once and open
it again.

6.1.4.6 PU/MU Value

PU/MU calculation is performed in nodes.
Because PU/MU calculation cannot be performed when the node type is PL, the [PU/MU]
page is not displayed.

■
■Node List
A list of nodes similar to that on the [System Conf] page is displayed. From this list, select
nodes where you want to find PU/MU values.

■
■Release Version
For use in future

■
■Number of Control Slots in Use, and Number of I/O Modules in Use
The number of control slots in use and number of I/O modules in use that are defined in
[System Conf] are displayed in the list box.

■
■PU/MU Value
Click the <Calculate PU> button to calculate PU/MU values according to the above settings
and then to display them in the PU value, PU ratio, MU value and MU ratio columns.

Note When DITYPE is set to other than STATUS in DI or when DOTYPE is set to other
than STATUS in DO, DO32, the PU values displayed are lower than actual PU val-
ues if point generation is not performed. When three I/O modules, including DI,
DO16, and DO32, are used, PU values differ depending on the DITYPE (STATUS,
LATCHED, ACCUM) or DOTYPE (STATUS, PWM) configuration of each slot. Therefore,
if PU values are to be calculated precisely, it is necessary that point generation be
performed.

− 244 −
 6.1 Creating Data to Be Loaded to the Controller

Note PULSE of DO32 is not supported in the calculation of PU values.Whether DO32 is

PULSE or not depends on the internal status of the controller. Because this status
cannot be detected from the RTC Editor side, PU values are regarded as STATUS or
PWM for the purpose of calculation. Therefore, overload may occur at the time when
the point configuration is loaded.

Note The maximum MU value, the basic value for calculating the MU ratio of PRC, de-
pends on the setting for [NEWIOUSE]. The maximum MU value is 24000MU for the
FX-Bus:5Mbps (new I/O) and 7900MU for the X-Bus:1Mbps (old I/O).

6.1.5 Point Generation

A point database is created based on the definitions of parts on sheets and settings of system
configuration. Points are generated subject only to parts included in the route layer (parts are
not generated subject to parts in Job Repository).

■
■Operation Procedure

Step 1 Make the Job Structure active, choose [Implementation], and execute the [Create
PDB] command. The [Create Point DB] dialog then appears.

Step 2 Select a node for which a point is generated with [Node:].

[All Nodes] : Points are generated for all nodes.
[One Node] : A point is generated only for the node selected in the list (only sin-
gular selection is allowed).

Step 3 When a node type which FB point available is selected in the point generation of
node unit, also select a point with [Point:].
[All Points] : Points are generated for all points (including FB point and block) in
the node.
[Point Unit] : Select points for which points are generated in the following check
boxes.
•• [All Points (Except FB points)]: Points are generated for all points
(excluding FB point and block) in the node.
•• [FB Points]: Points are generated for the FB points selected in the
list and the blocks belonging to the FB points.

Step 4 To decide the automatic computing order of blocks, check the [Auto Order Option]
check box.

Step 5 Click the <Execute> button.

− 245 −
Chapter 6. Implementing Harmonas-DEO System

Step 6 The results of having executed point generation appear in the [Status:] list box.
Click the [Save ...] button to output the contents of the [Status:] list box to a file.
•• The completion time of point generation for each FB point is set in the “Version”
parameter for the FB point. However, if no block has been defined in the FB
block, or point generation fails for the FB point, the parameter is reset to the
“invalid” state for the initial value.

Note To generate points for blocks, nodes and FB points need to have been specified for
the sheets where the blocks exist. If they have not been specified, points are not
generated correctly.

Note At the time of point generation, parameter value (tag. parameter name) resetting
processing is performed on linked parameters. The “tag. parameter name” directly
entered by the user for linked parameters is replaced by the “tag. parameter name”
of the linked Part. That is, linking takes precedence. The “tag. parameter name” en-
tered for a parameter not linked is not rewritten in point generation.

Note If the job has over 1000 sheets (include sheets in Job Repository), Create PDB works
slowly for saving memory. Therefore Create PDB takes long time than usual to
complete.

■
■Opening the sheet of a part that caused an error or a warning in point generation
If an error or a warning occurs in point generation, the <Next Error> and <Prev Error> but-
tons become operative. When these buttons are pressed, an error or a warning line (line start-
ing with “ERROR>” or “WARNING>”) is searched for in the list and is highlighted.
When an error or warning concerning a part on a sheet emerges, the <Open Sheet> button
becomes operative. When the <Open Sheet> button is clicked, the sheet is opened with the
part in the selected condition. If you double-click a line with an error or warning in the list,
likewise, the sheet is opened with the part in the selected condition. But errors occurring other
than in a part or those having occurred at FB Points are inapplicable.

■
■Block numbers and computing order of blocks
Blocks in an FB point are identified by “Function Block Numbers.”
Blocks to be processed by controllers are processed in the “Order of Block” set by RTC Editor.
This section describes the block numbers of block parts and parameters concerning comput-
ing order, and also explains the setting method and the automatic determination of comput-
ing order.

− 246 −
 6.1 Creating Data to Be Loaded to the Controller

•• Block numbers and Order of block parameters

Block parts have the following three parameters concerning block numbers and computing
order:
FUNCTION BLOCK NUMBER (FBNO) :
This is a number that identifies a block in an FB point.

NEXT PROCESSING BLOCK NUMBER (NEXTBLK) :

This is the block number of the block to be processed next by a controller.
The above two values are loaded into controllers, and blocks are processed sequentially in
accordance with the values.

ORDER OF BLOCK (BLOCKORDER) :

This is the order in which blocks are processed.
This shows the computing order of the blocks in an FB point. Values beginning with “1”
are set serially.
This parameter is required only for RTC Editor. In accordance with these values, the pa-
rameters concerning function block numbers and next processing block numbers are set
at the time of point generation.

•• About FUNCTION BLOCK INDICATION (FBAUTOMAN) parameter

The “Function Block Number” and “Order of Block” parameters can be either set manually by
the user or decided automatically at the time of point generation.
Manual or automatic setting can be specified in the “FUNCTION BLOCK INDICATION
(FBAUTOMAN)” parameter of each block part.

Setting items and their uses are as follows:

AUTO : Neither “FUNCTION BLOCK NUMBER” nor “ORDER OF BLOCK”
can be specified.
“FUNCTION BLOCK NUMBER” are automatically assigned at the
time of point generation.
MANUAL : “FUNCTION BLOCK NUMBER” and “ORDER OF BLOCK” are
specified manually by the user.
“FUNCTION BLOCK NUMBER” are not changed by point genera-
tion; they remain at set values. To prevent “ORDER OF BLOCK” from
being changed, specify MANUAL for setting.
OFFSET : “ORDER OF BLOCK” is specified manually by the user.
“FUNCTION BLOCK NUMBER” are automatically assigned at the
time of point generation.
For block parts to be encapsulated, specify OFFSET and set their com-
puting order in capsule parts, beginning with “1.” (If the “FUNCTION
BLOCK NUMBER” of the block parts to be encapsulated are to be set
manually, specify MANUAL.)

− 247 −
Chapter 6. Implementing Harmonas-DEO System

•• [Auto Order Option] option for point generation

If the [Auto Order Option] option is checked for point generation, “ORDER OF BLOCK”
parameters are automatically assigned.
The computing order of individual blocks is decided based on the link relationships among
blocks (the flow of signals) in the logic diagram. In accordance with the computing order
decided, values beginning with “1” are set automatically in the “ORDER OF BLOCK”
parameters.
If this option is checked for point generation, the “ORDER OF BLOCK” parameters of all
the block parts that are targets of point generation, without regard to “FUNCTION BLOCK
INDICATION” are automatically reassigned.

Note Note that if [Auto Order Option] is specified to generate points, the computing order
of the blocks for which “MANUAL” or “OFFSET” is specified is also changed.

Note The default “ORDER OF BLOCK” set for block parts is “0,” meaning that no computing
order is set.
In cases in which point generation is performed for the first time, if there are any
parts for which computing order is not set, check [Auto Order Option] to generate
points. As a result, the computing order of the parts is set automatically.

Note It is necessary to check the [Auto Order Option] option in the cases enumerated
below.
In other cases, it is not necessary to check the option.
1. Cases in which the block parts for which points are to be generated include parts
of which the computing order is not decided (parts of which the “ORDER OF
BLOCK” parameters are “0”).
2. Cases in which the “ORDER OF BLOCK” parameters of individual block parts are
not set serially from “1” in an FB point in which points are to be generated. (Cases
in which “ORDER OF BLOCK” parameters are not set serially, with some numbers
skipped.)
3. Cases in which the computing order is to be reassigned.

Note If the “ORDER OF BLOCK” is to be set manually and if it is not to be changed by point
generation, make the following settings 1 and 2:
1. Specify MANUAL or OFFSET.
2. At the time of point generation, turn off the [Auto Order Option].

− 248 −
 6.1 Creating Data to Be Loaded to the Controller

Note In the case of link connection of block parts, note the following for the link connec-
tion of parts in different FB points:
•• Specify “MANUAL” for block parts that are targets of link connection with parts in
different FB points.
•• For example, if the FB point “FB01” in the diagram below is generated, the function
block number (FBNO) of block “C” may change. If the change takes place, the input
connection parameter value (Internal Entity) of block “D,” which is link-connected
with block “C,” also changes, necessitating the reloading of “FB02.” Therefore, for
block parts to be connected with parts in different FB points, specify “MANUAL” so
that their function block numbers (FBNO) will not change.

FB01 FB01

A C D E

B F

: Intersheet part
Specify MANUAL for
blocks C and D.

Figure 6-7.

Note In the following logic, the order of block cannot be automatically decided. Set the
order of block manually.

All blocks has the same cases that has

a several feedback.

AND AND

AND AND

Figure 6-8.

− 249 −
Chapter 6. Implementing Harmonas-DEO System

Note As in the following logic where two blocks are linked via BOX parameter parts, com-
puting order on block 2 may be done before block 1.

Block 1 Block 2

CONV CONV

YEAR

XPCBOX010.YEAR
BOX parameter parts

Figure 6-9.

•• Rules for assigning block number and order of block parameters at the time of point
generation
The rules for assigning block number and order of block parameters at the time of point
generation vary depending on combinations of the “FUNCTION BLOCK INDICATION”
parameter and the [Auto Order Option] option, as shown below.

Table 6-16. Rules for Assigning Block Number and Order of Block Parameters at the Time of
Point Generation

FUNCTION BLOCK Next Processing

Auto Order Function Block No. Order of Block
INDICATION Block No.
Option FBNO BLOCKORDER
FBAUTOMAN NEXTBLK
OFF Automatic Automatic Set value unchanged
AUTO
ON Automatic Automatic Automatic
OFF Set value unchanged Automatic Set value unchanged
MANUAL
ON Set value unchanged Automatic Automatic
OFF Automatic Automatic Set value unchanged
OFFSET
ON Automatic Automatic Automatic

When “Function Block Numbers” are to be automatically assigned, unused order of block
numbers in the FB point are assigned in ascending order.
With respect to “Next Processing Block Numbers,” the block number of the block to be pro-
cessed next in accordance with the computing order is automatically assigned.

•• Rules about automatic ordering by RTC editor

RTC editor sets “ORDER OF BLOCK” parameters by following rules below.
•• It divides blocks which are assined on a FB point into groups.
The group consists of blocks which are connected each other.
•• It numbers “ORDER OF BLOCK” parameters in order from input side block to output
side block every group.

− 250 −
 6.1 Creating Data to Be Loaded to the Controller

There are more detailed rules listed below.

•• If there are multiple groups on a FB point, it sorts their blocks by Block Name and starts
numbering from the group which has the first block.
•• If there are multiple input side blocks on a group, it sorts them by Block Name and and
sets the first block to next number.
•• If there are multiple connected blocks on output connection, it sorts them by Block Name
and sets the first block to next number.
•• If the blocks are connected cyclically on a group, it is not clear whick block is an input
side block.
In this case, it sorts blocks which has a numbered block on input connection by Block
Name and sets the first block to next number.
If there is no block which has a numbered block on input connection, it sorts all blocks
on a group by Block Name and starts numbering from the first block.

Note Sorting by Block Name is order of ASCII code with case ignored.

Note If the user wants to assign “ORDER OF BLOCK” parameters as the user wants because
the user is not satisfied with ordering by RTC editor, the user can assign them by
following ways below.
•• Please attach a prior character in order of ASCII code at the head of Block Name.
(ex:FL0100010006 → 0FL0100010006)
•• If the first way does not work, please place a dummy block without side effects
and connect its output connection to the target block.
•• Please set “FUNCTION BLOCK INDICATION” parameters to “MANUAL” and then set
“FUNCTION BLOCK NUMBER” and “ORDER OF BLOCK” parameters manually.
In this case, never check [Auto Order Option] check box when point generation.
If the user checks it, “FUNCTION BLOCK NUMBER” and “ORDER OF BLOCK” param-
eters that the user set will be overwritten by Auto Order Option feature.

FL

OFL
1 AND FL

AND1 FL3
FL 3 4

FL1
2

Figure 6-10. attach a prior character

− 251 −
Chapter 6. Implementing Harmonas-DEO System

FL AND NOT AND NOT FL

FL1 AND1 NOT5 OAND NOT6 FL3

1 6 7 3 4 5

FL

DUMM

Figure 6-11. place a dummy block

•• For encapsulated blocks

If [Auto Order Option] is specified to generate points, the “Order of Block” of blocks within
capsule parts is not changed, but the “Order of Block” is automatically set in the capsule parts.
In this case, the computing order within capsule parts needs to be set in each of the blocks
within the capsule parts in advance.
SG001 SQRT002 ABS005

SG Capsule Parts

1 2 3 4

Order of block set SG003

automatically
SG

1 ADD004

Order of block in capsule parts

Figure 6-12.

In the above block diagram, the order of block is as follows:

SG001 → SQRT002 → SG003 → ADD004 → ABS005 →

− 252 −
 6.1 Creating Data to Be Loaded to the Controller

■
■Checking the parts imported from RTC_FB
The parts imported from RTC_FB by [Import Parameter] function are checked and set as
follows.
•• Checking the validity between the parts of RTC Editor and the CSV files output by RTC_FB
It is checked whether or no the CSV files are imported to RTC Editor correctly. An error
or warning occurs in the following cases. For example, the CSV files are not imported to
RTC Editor, or the parameter is different from RTC Editor and RTC_FB.
– The following files output by RTC_FB do not exist or can not be imported.
[Job Directory]/fieldbus/param/NodeXXX_SegYYY.csv
(XXX:Node number, YYY:Segment number)
– The node definition which is not defined in RTC Editor exists in the CSV files output
by RTC_FB.
– The tag name or the parameter is different from RTC Editor and RTC_FB.
– The FFFB parts defined in RTC Editor does not exist in the CSV files output by RTC_
FB. (The FFFB parts are created only by importing the CSV files output by RTC_FB)

•• Setting the module number of FFFB parts

The module number of FFFB parts is set automatically at the time of point generation.
The value of module number is set according to the segment number of FC node which
is defined in the System Definition.

− 253 −
Chapter 6. Implementing Harmonas-DEO System

Restriction There are the following restrictions for “edit of point parts,” “point generation” and
“load to controller”.
•• Conducting “point generation” and “load to controller” after deleting point parts
of control points from the RTC sheet makes untagged active slots. There are fol-
lowing ways below to detect untagged active slots.
− Check slots on [Delete Controller Data] dialog.
− Check untagged active slot on Slot Summary Display in System Status Display.
− Detect invalid points by node uploading on [Upload Controller Data] dialog.
If the user wants to delete points, please do following actions below.
1. Please delete points on [Delete Controller Data] dialog.
2. Please point parts on RTC sheets.
3. Please do Point Generation
4. Please do Creating System Data File
5. Please reboot DOSS or execute online change.

•• When the slot No. of the control point is changed from the RTC editor, points are
loadable while being active and old slot No.s are operating as active. Therefore,
be cautious when changing slots. In the same manner as the point deletion
described above, delete the controller point data using [Delete Controller Point
Data] before loading the changed point to the controller after changing the
point of old slot No.s.

•• Multiple cascade primary points can be created. Therefore, be cautious when

creating/changing cascade primary points.

•• When point settings are changed/loaded with the RTC editor, conduct online
change or restart the SE program and InTouch after closing the RTC runtime and
Tuning Trend.

− 254 −
 6.1 Creating Data to Be Loaded to the Controller

6.1.6 Box Variable Edit Display

Box Variable Edit Display provide a function for checking and editing the Box variables
not tagged. “Box variables” are a PV parameter at a flag point, a PV parameter at a numeric
variable point, STR64 parameter at a string point TIME and TMFORMAT parameters at a
datetime point and SP and TIMEBASE parameters at a timer point. In newly added nodes, no
Box variable data exists by default. It is necessary to take in parameter data through uploading
or importing.

■
■Box Variable Edit Display
Make the job hierarchy diagram active and choose [Box Variable Edit Display] from the
[Implementation] menu.

■
■Node List
Nodes that are defined in the System Definition and that are nodes of controllers are displayed
in the following format:
“Node type: node number”

In the node list, select a node where points having parameters you want to display in a param-
eter list described later are defined. Changing the node list will erase the variable types and
parameter list described later.

■
■Variable Type
The following variable types can be selected according to the node types selected in the node
list.

Table 6-17.

Node Type Variable Type Displayed

PC4 [R411 or later] Box Flag/Box Numeric/Box String/ Box Datetime/Box Timer
PRC/XPC/FLC/PL2/FC Box Flag/Box Numeric/Box Timer
PL Box Flag/Box Numeric

Select a variable type having a parameter you want to display in a parameter list described
later. Variable types are selectable only when the nodes are selected in a node list. Selecting a
variable type updates a parameter list.

− 255 −
Chapter 6. Implementing Harmonas-DEO System

■
■Parameter List
Box variable values selected in a node list and with a variable type are displayed in the follow-
ing formats.
“Slot number PV value” (for Box Flag)
“Slot number SP value TIMEBASE value” (for Box Timer)
“Slot number PV value” (for Box Numeric)
“Slot number PV value PVFORMAT value” (for Box Numeric) [R411 or later]
“Slot number STR64 value” (for Box String) [R411 or later]
“Slot number TIME value TMFORMAT value” (for Box Datetime) [R411 or later]

Until controller data is uploaded or import of Box variable is executed, a message dialog is
displayed and nothing appears in a parameter list.

■
■Export
Values displayed in a parameter list are output as a CSV format file. If parameter values are not
displayed, export cannot be done. Output file formats are as follows.

Table 6-18. Output file formats

Line No. Description

Outputs node information (node types and node numbers) selected in a node list
and with a variable type, and the variable type. The format is as follows
“Node type, node No., variable type”
For node types, one of “PRC”, “PL”, “XPC”, “PL2”, “FLC”, “FC” or “PC4 [R411 or
1st line
later]” is output. For variable types, one of “BOXFLAG”, “NUMERIC”, “TIMER”
or “BOX STRING” is output. If, for example, the point type is PRC, node No. is
27, or variable type is a Box Timer, the output is as follows.
“PRC,27,TIMER”
The following headline is output according to the selected variable type.
Box Flag : “No.,PV”
Box Numeric : “No.,PV”(“No.,PV,PVFORMAT” [R411 or later])
2rd line
Box String : “No.,STR64” [R411 or later]
Box Datetime : “No.,TIME,TMFORMAT” [R411 or later]
Box Timer : “No.,SP,TIMEBASE”
A parameter value is output for each slot number. The type of output parameter
values differs for each variable type and is as follows
Box Flag : PV (“ON” or “OFF”)
Box Numeric : PV (“--” (NaN) or real value)
PVFORMAT (D0, D1, D2, D3) [R411 or later]
Box String : STR64 (up to 64 characters) [R411 or later]
Box Datetime [R411 or later]: TIME
TIMEFORMAT(AUTO, ABSOLUTE,
DURATION)
Box Timer : SP (integer of 0 or more)
TIMEBASE (“SECONDS” or “MINUTES”)
3rd line and later
The format is as follows
“Slot number, PV value” (for Box Flag)
“Slot number, SP value, TIMEBASE value” (for Box Timer)
“Slot number, PV value” (for Box Numeric)
“Slot number, PV value, PVFORMAT value” (for Box Numeric) [R411 or later]
“Slot number, STR64 value” (for Box String) [R411 or later]
“Slot number, TIME value, TMFORMAT value” (for Box Datetime) [R411 or
later]
If, for example, the slot number is 10, SP is 5, TIMERBASE is MINUTES, the Box
Timer outputs the following
“10,5,MINUTES”

− 256 −
 6.1 Creating Data to Be Loaded to the Controller

The exporting procedures are as follows.

Step 1 Click the <Export> button.

A dialog appears to specify the destination to save the file in. At this time, a job
directory and default file name are set in the directory and file name, respectively.
By default, the file name is set according to the following format.
“BOXnnnPT.csv”

Where nnn is a three-digit node number, and PT is a two-character point type. PT

is replaced by “FL” in a Box Flag, “NM” in a Box Numeric, “ST” in a Box String,
“DT” in a Box Datetime and “TM” in a Box Timer.

Step 2 Specify a directory to save the file in and enter the file name.

Step 3 Click the <Save> button.

Parameter values are then exported.

■
■Import
The contents of a CSV format file are set as a Box variable value.
A CSV format file to be imported needs to have the same format as a CSV format file created
when it is exported.

The importing procedures are as follows.

Step 1 Select node information and a variable type from the node list and variable type,
respectively.

Step 2 Click the <Import> button. A dialog appears to select a file to be imported. As in
the case of export, a job directory and default file name are set in the dialog.

Step 3 Select a CSV format file to be imported.

Step 4 Click the <Open> button. A parameter value is imported and the parameter list is
updated.

Note The contents selected in the node list and with a variable type need to
match the node information (node type and node number) and variable
type set in the file. If this information is unmatched, the file cannot be
imported.

Note [R411 or later]

When you edit Box Datetime value in CSV file, please put TIME pa-
rameter value in three double-quatations (ex. “””2012/08/01
03:00:00”””,ABSOLUTE).

− 257 −
Chapter 6. Implementing Harmonas-DEO System

Parameter values of slots read from files are set as Box variable values. For the slots that can-
not be read due to errors in the file contents or whose slot numbers are duplicated, the error
contents will be output to the BOXIMP.err file under the job directory. The output format is
as follows.
“Line No. within the file Slot No. Error Contents”

The parameter values of line numbers output to the BOXIMP.err file are not set as Box vari-
able values. Box variable values before import remain as they are. For slot numbers whose
Box variable value before import is not found, the following default parameter values are set
as Box variable values.

Table 6-19. Default value

Variable Type Default value

Box Flag PV : “OFF”
PV : “-------”(NaN)
Box Numeric
PVFORMAT : “D1” [R411 or later]
Box String [R411 or later] STR64 : “”
TIME : 1997/01/01 00:00:00
Box Datetime [R411 or later]
TMFORMAT : ABSOLUTE
TIMEBASE : “SECONDS”
Box Timer
SP : “0”

Comments can be written into import files. Enter ‘#’ into the beginning of comment lines.

− 258 −
 6.1 Creating Data to Be Loaded to the Controller

6.1.7 PMDP Local Value Edit Display

PMDP Local Value Edit Display provides a function for displaying and editing the values of
FL(n), NN(n), STR16(n) [R411 or later], TIME(n) [R411 or later] and TMFORMAT(n) [R411 or
later] held by PMDP points.

■
■PMDP Local Value Edit Display
Make the Job Window active, and choose the [PMDP Local Value Edit Display] menu from
[Implementation].

■
■PMDP point names
The point name of the PMDP point the user wants to display is specified here.
First, choose a node in the [Node] combo box, and point names are set in the [Point] combo
box. Choose a point name.

■
■PMDP Local Value List
When a point name is chosen, the slot numbers of internal variables and their values are dis-
played in [PMDP Local Value List]. The values can be edited here.
To edit a value, double-click the value, or click the <Edit> button, keeping the value chosen.
ON or OFF can be entered in local flag variables. Real numbers or NaN values can be entered
in numeric variables. Up to 16 characters can be entered in string variables. Values can be
deleted by entering empty.

■
■Export
Values can be exported to a CSV format file.
Click the <Export> button, and the [CSV File] dialog box opens. Specify here the range to be
exported.
If <All Node> is chosen in [Option], all the PMDP internal variables in the job are output.
Data is output as a CSV file on a node by node basis, and the file name is “PML Vnnn.csv”
(nnn: node number). If values are exported after choosing a node by clicking <Node>, the
PMDP internal variables in the node chosen are output. If values are exported after choosing
node and point names by clicking <Point>, the PMDP internal variables in the point chosen
are output.

■
■Import
Values can be imported from a CSV format file.
Click the <Import> button, and the [CSV File] dialog box opens. Specify here the range to be
imported.
If <All Node> is chosen in [Option], PMDP internal variables are read from all CSV files
corresponding to the nodes in the job. If values are imported after choosing a node by click-
ing <Node>, PMDP internal variables are read from the CSV files corresponding to the node
chosen. If values are imported after choosing node and point names by clicking <Point>, the
PMDP internal variables in the point chosen are read.

− 259 −
Chapter 6. Implementing Harmonas-DEO System

■
■CSV files
PMDP internal variables can be exported to and imported from CSV files.
One CSV file corresponds to one node. The file name is “PML Vnnn.csv” (nnn: node number).
When PMDP internal variables are exported, the data in the corresponding node is produced
in the corresponding CSV file. When PMDP internal variables are imported, the data in the
corresponding node is read from the corresponding CSV file.
The file format is comma-separated value (CSV) format, with the vertical axis representing
point names and the horizontal axis representing parameter names. The first line is a title line
on which parameter names are placed.
CSV files can be edited using Microsoft Excel. When saving them, however, be sure to save in
comma-separated value (CSV) format.

6.1.8 Create Controller Data Files

A control data file is a database related to points loaded into the controller. Create a control
data file for each node.

■
■Operation Procedure

Step 1 Make the job hierarchy diagram active, select [Implementation], and execute the
[Create Controller Data File] command.

Step 2 This will display the [Create Controller Data] dialog.

Step 3 Select a node from the list of configured nodes (indicated with “Node Type: Node
No.”) in the [Node List] dropdown list of the dialog.

Step 4 Select “Box” in the [Data Type] dropdown list of the dialog.

Step 5 Specify [Node List] and [Data Type] to determine the default file name, and the
name will be displayed in the [File Name] box. The default file is created with the
file name “HDBXnnn.idb” under the “\{Job directory}\IDB\” (nnn: node number).

Note A control data file can be created with an arbitrary file name in an arbi-
trary directory. Be sure to use file extension .idb.

Check the file name and click the <Create> button. This will create a control data
file related to the box.

− 260 −
 6.1 Creating Data to Be Loaded to the Controller

Note Box data is created in the following cases.

•• Cases where the PRC, XPC, FLC, PL, PL2, FC, PC4 [R411 or later] configu-
ration information shown in Section 6.1.4.1, “System Conf” is newly
created or the set contents are changed. To add points, it is unneces-
sary to re-create box data.
− When the number of control slots was changed
− When I/O module configuration was changed

Since the box data file is information set for the entire boxes for PRC, XPC,
FLC, PL, PL2, FC, PC4 [R411 or later] changing the set contents in Section
6.1.4.1, “System Conf” requires to create a box data file immediately.

Step 6 Then select “Point” from the [Data Type] dropdown list to create a control data file
related to the point. By default, the file name is “HDPTnnn.idb”.

Step 7 If “Point” has been selected, [Data to be Loaded] parameter is available. If <Box
Variable is included> is selected here, uploaded Box variable in addition to the
point information is written into the file. If parameter values defined in point
conflict Box variables, the parameter values are loaded and the Box variables are
ignored. For uploading of Box variables see Section 6.3.6.
If <PMDP Local Value is included> is selected, PMDP Local Value add to PMDP
Point parameter.

Note Point data is created in the following cases.

•• When the PRC, XPC, FLC, PL, PL2, FC, PC4 [R411 or later] point is added
or deleted
•• When the setting contents of PRC, XPC, FLC, PL, PL2, FC, PC4 [R411 or
later] point are changed

As in the case above, if the setting contents of the points as shown

above are changed, a point data file must be created after the point is
generated.

Step 8 Repeat Step3 to Step7 for the number of nodes. If all necessary control data files
are completely created, click the <Cancel> button to close the diagram.

Note Omission of information on any of [Data Type], [Node List] and [File
Name] prevents you from creating control data files.

Note If Create PDB is failed for the target node, warning message is displayed
when the <Create> button is pressed on [Create Controller Data] Dialog.

− 261 −
Chapter 6. Implementing Harmonas-DEO System

6.1.9 Export Parameter/Import Parameter

■
■The following two functions are provided:
•• Export Parameter: Part parameter values are exported to an Excel file.
•• Import Parameter: An Excel file is imported, and the part values are set or parts are newly
created/deleted.

■
■The Excel file format (the default setting) and the CSV file format are available for the
file formats.

■
■The parameters to be exported and imported are those for point parts, those for
logic-component parts or those for block parts on sheets. The parameters for any
other parts and location data on links, parts and ports can neither be exported nor
imported.

The following data can also be exported and imported:
•• The Sheet Name where a part is located (path name of the sheet)
•• The position of a part (the X and Y coordinates on the sheet)
•• The name of the port to be displayed and its position (the X and Y coordinates relative
to a part)
The following operation can be performed by importing:
•• Adding links automatically

■ Excel application must be installed to export data to or import data from an Excel
■An
file. The following Excel versions are supported:
•• Excel 2000 (Office 2000)
•• Excel 2002 (Office XP)
•• Excel 2003 (Office 2003)
•• Excel 2007 (Office 2007)
•• Excel 2010 (Office 2010)

Note In R300, the two functions of [Output Point Parameters] and [Import Point List] have
been deleted. Use the Export Parameter and Import Parameter functions for the
work that was done using the two functions deleted.

− 262 −
 6.1 Creating Data to Be Loaded to the Controller

6.1.9.1 Engineering procedures

Engineering flows in use of the Export Parameter and Import Parameter functions are de-
scribed for the following three patterns:

■
■When existing part parameters are modified using Excel
1. Export to the Excel file the parameters of the parts on sheet “Equipment A” and those
under the sheet.
2. Edit parameters in the Excel file where the export has been provided.
3. Import the edited Excel file to the parts on sheet “Equipment A” and those under the sheet.

1. Exporting
2. Editing

3. Importing

Excel file

Figure 6-13.

■
■When existing parts are copied and the parameters of the copied parts are to be
modified with Excel
1. Copy the “Equipment A” container and name the copied container as “Equipment B.”
2. Export to the Excel file the parameters of the parts of sheet “Equipment B” and those under
the sheet.
3. Edit the parameters in the Excel file where the export has been provided.
4. Import the edited Excel file to the parts of sheet “Equipment B” and those under the sheet.

1. Copying

2. Exporting 3. Editing

4. Importing

Excel file

Figure 6-14.

− 263 −
Chapter 6. Implementing Harmonas-DEO System

■
■When parameters are to be set to create a new part
1. Set to the Excel file the parameters of parts to be created.
2. Specify a sheet at the import destination and import the Excel file onto the sheet. Then
sheet “X01” is generated and the parts are created on the sheet.

1. Editing

Excel file
2. Importing

Figure 6-15.

6.1.9.2 Excel file formats

This subsection explains the format of the file in the exporting operation and the importing
operation (Overwrite, Create). About the format in case of “Delete” of the importing opera-
tion, please reler to Section 6.1.9.4.

■
■Format examples
The following show Excel file examples:

&N &T NODETYP NODENUM MODNUM SLOTNUM PVEULO PVEUHI SENSRTYP

AI0100511 AI PRC 10 5 11 -100 100 1_5_V
AI0100512 AI PRC 10 5 12 0.0 200.5 1_5_V
AI0200101 AI XPC 20 1 1 10 210 0_5_V
AI0210101 AI XPC 21 1 1 7.890 12.340 SLIDWIRE
AI0300305 AI FLC 30 3 5 20 220 SLIDWIRE

■
■Explanations of the formats
•• Parameters are placed horizontally and tags are placed vertically.
•• Only one row for parameter names which start in “&N” exists in each of these files.
•• More than one row for parameter names can be defined for a file.
•• Parameter values are written in the space under the row for parameter names.
•• Data on a tag is written on a row. No one row includes data on two or more tags and no tag
definition comprises more than one row.
•• Parameter types, number of parameters and parameter order can be specified by the user.
•• However, the following parameters (&N, &T and &M) are always exported and settings for
these parameters must have been made when they are to be imported. (However, &M is
required only for logic component parts.)

− 264 −
 6.1 Creating Data to Be Loaded to the Controller

Table 6-20.

Parameter name Meaning

&N Tag name
Point type
&T However component, for block parts it indicates a block type and for
logiccomponent parts a logic-component type.
Logical tag name
&M
However, this parameter is required only for logic-component parts.

•• The following character sequences are set for the “&T” parameter:

Table 6-21.

Part type Character sequences set for the “&T” parameter

AI, AO, DI, DO, DC, RP, RC, LG, FL, NM, NAR [R411 or later], STR
[R411 or later], DT [R411 or later], TM, PM, VI, VO or FF
Point parts
•• These characters are the same as the indications on the part bar
buttons (except VI , VO and FF).
LG (ALGO), LG (NUMERIC), LG (FLAG), LG (CONNECT) or LG
(GATEWAY)
•• Formats for LG (xxxx)
Logic-component parts
•• The “xxxx” portion indicates a logic-component part type.
(A “xxxx” character sequence is the same as “xxxx” in the “xxxx
(LOG)” indicated on the corresponding part bar tab.)
BL (ADD), BL (DIV), BL (MUL), etc.
•• Formats for BL (xxxx)
Block parts •• The “xxxx” part indicates a block type. (The character sequence
is the same as that in the initial portion (block type) of the corre-
sponding default block name.)

•• In Export Parameter, export is sorted out using tag names.

•• A blank and a “” (two double quotation marks) mark respectively have the following
meanings when each of them is set to an Excel cell.
– If no parameter is provided for a part, a blank is set for the corresponding Excel cell.
– If a parameter is provided for a part but no value is specified for the parameter, a “”
mark is exported to the corresponding Excel cell.

■
■Notes for editing Excel files
•• The row for parameter names must be started with “&N”. Each of these files must contain
one row where parameter names are defined.
•• Define parameter values under the row for parameter names. If those values are written
above the row for parameter names, an error is generated in the importing operation and
they are not imported.
•• More than one row for parameter names can be defined for a file. However, if no row for
parameter names exists above the parameter value, an error occurs.
•• The parameters starting with “&” (&N, &T and &M) must be always set. Be sure to define them
in the files. However, the &M parameter is required only for logic-component parts. (&M is not
essential in the importing operation for creating a new parts.)
•• The essential parameters (&N, &T and &M), which must always be set, constitute key data
for searching for corresponding parts on a sheet.

− 265 −
Chapter 6. Implementing Harmonas-DEO System

•• When the [Read Sheet Hierarchy (&SHEET)] option is checked before importing a file,
&SHEET (path name of the sheet) is also added as a key to search a part.
•• The essential parameters must always be defined in the order of &N, &T and &M starting with
the first column. The order of other parameters can be defined by the user.
•• To change, through a importing operation, the “tag name” corresponding to &N and/or
the “logical tag name” corresponding to &M of a part, make the following settings for the
Excel file.
– To change the tag name: Specify a new tag name for the parameter named
“NAME.”
– To change the logical tag name: Specify a new logical tag name for the parameter named
“MODELNAME”.

For example, make the following settings for the Excel file:

&N &T NAME

← The tag name AI05001 is to be
AI05001 AI AI07001
changed to AI07001.
← The tag name AI05002 is to be
AI05002 AI AI07002
changed to AI07002.

&N &T &M MODELNAME

← The logical tag name AND01008
LG01 LG (ALGO) AND01008 AND01009
is to be changed to AND01009.
← T h e l o g i c a l t a g n a m e
LG01 LG (GATEWAY) UnNamed006 GW0101 UnNamed006 is to be changed
to GW0101.

•• No part type can be changed through a Import Parameter operation. Therefore, no change
can be made for the parameters corresponding to “&T”.
•• When a blank or a “” (two double quotation marks) mark is set for a parameter value, the
following processing is conducted in the Import Parameter operation:
– Nothing is done for the parameter for which a blank is set.
– For the parameter for which a “” mark is set, the part value is deleted.

The following describes an example in which a change is made for PTDESC:

&N &T PTDESC

← “Flow volume A002” is to be set
AI05002 AI Flow volume A002
for PTDESC of the part.
← The value of PTDESC of the
AI05003 AI
part is not to be changed.
← The value of PTDESC of the
AI05004 AI “”
part is to be deleted.

•• Comments can be entered. Character sequences corresponding to the following patterns are
regarded as comments and are ignored in importing operations:
– A line starting with a “#” character is regarded as a comment.
– If no parameter name is written in a column on the row for parameter names, all charac-
ters in the column are regarded as those for comments.

− 266 −
 6.1 Creating Data to Be Loaded to the Controller

The following show examples where comments are used. The characters written in italics in
the table constitute comments.

← The description constitutes a com-

# Input/output list (July 12, 2004)
ment because the line starts with #.
#TAG ← The description constitutes a com-
Unit PV format Range: HI Range: LO Remarks
name ment because the line starts with #.
&N &T EUDESC PVFORMAT PVUEH PVEULO ← (The row for parameter names)
Temperature of equip-
AI05001 AI °C D1 150.0 -150.0
ment A: XXX
Flow volume of equip-
AI05002 AI kg/h D3 100 0
ment A: YYY
← The description constitutes a com-
#AI05003 AI % D1 100 50 Level meter: ZZZZZ
ment because the line starts with #.
Flow volume:
AI05004 AI L/min D1 300 0
WWWWW
↑ These descriptions constitute comments because no parameter
name is provided for this column on the row for parameter
names.

6.1.9.3 Export Parameter

■
■Operation procedures
1. Select [Implementation] → [Export Parameter...] to display the [Export Parameter] dialog
box.
2. Select from the Job Structure a sheet to be exported. Only one sheet is selectable. To export
sheets in the layers under the selected sheet as well, check [Contain Sub Sheets].
3. Specify a directory in [Export Directory:]. The default setting is the “param” directory under
the job directory.
4. Specify “Excel file” or “CSV file” in [Export File Format:].
5. Specify in [Point Type] a point type to be exported. Files are exported for each point type.
6. To provide export for each node additionally, check [Node Unit] and specify a node whose
data is to be exported.
You can set the export unit by setting [Point Type Unit], [Node Unit], and [Sheet Unit]. If
none of them is checked, no export unit is used and files are exported all together.
7. To change the type of parameters to be exported or to change the export order, make
the change in the [Set Export Parameter] dialog box that is displayed by clicking the
<Parameter...> button. (The details are described later.)
8. Click the <Export> button. Then the Export Parameter starts.
9. The status of the export results is displayed in the [Status:] list box. When the <Prev
Status> button or the <Next Status> button is clicked, the ERROR line and the WARNING
line in the list box are selected one after another.
When the <Save...> button is clicked, the contents of the list box are saved in the file.

− 267 −
Chapter 6. Implementing Harmonas-DEO System

■
■Setting the type and order of export parameters
•• Click the <Parameter...> button in the [Export Parameter] dialog box. Then the [Set Export
Parameter] dialog box appears. Specify the type and order of export parameters (column
numbers are used for indicating the order) in this dialog box.
•• The parameters displayed in the [Export (Export Order)] list box in the [Set Export
Parameter] dialog box are actually exported to the file. The order starting with the top of
the list box becomes the order of the export parameters (column numbers are used for
indicating the order).
•• Use the <>> or <<> button to switch export items and non-export items of parameters. Use
the <up> or <down> button to change the export order. However, the parameters (&N, &T
and &M) that must always be set cannot be set to non-export items and their export order
is fixed as well.
•• Use the <Export...> button and the <Import...> button to export to a file the data set in the
[Export (Export Order)] list box and to import the data from the file, respectively. It is not
required that all point type definitions be described in the file from which data is to be im-
ported. Nothing is done for the point types that are not described.

■
■Additional Export Information
You can export the following additional information using [Additional Export Information]
in the [Set Export Parameter] dialog box.

[Sheet Hierarchy (&SHEET)]

•• Export the path name of the sheet where a part exists.
Example) For the sheet selected in the following figure, the path name is:
&SHEET = \sample_job\Plant_A\UNIT_A3

Figure 6-16.

•• The path name of the sheet is exported as a value of the parameter “&SHEET” for each tag.

− 268 −
 6.1 Creating Data to Be Loaded to the Controller

[Part Position (PosX, PosY)]

•• The X and Y coordinates of a part on a sheet are exported as values of the parameters
“PosX” and “PosY” respectively.
•• The X and Y coordinates indicate the distance from the top left corner of a sheet to the
origin, which is located at the upper left corner of a part, as shown in Figure 6-17.
•• Part Position can be exported only when the sheet hierarchy information is exported.

Figure 6-17.

[Port Information (Port(n), PortX(n), PortY(n))]

•• The Port Name displayed in a part is exported as a value of the parameter “Port(n),” and the
X and Y coordinates of the port are exported as values of the parameters “PortX(n)” and
“PortY(n)” respectively. The value of “n” in “(n)” is an index starting from 1 and set with a
number from 1 to 50 to match the number of ports.
•• The X and Y coordinates of the port indicate the distance from the upper left corner of a
part in the range of 0.0 to 1.0 (a real value) as shown in Figure 6-17.

[Parameter for Automatic Linking (Point.Parameter Type)]

•• Export the parameters used in automatic linking for Import Parameter. The parameters
used in automatic linking are shown below.

Digital Composite DISRC(1)~DISRC(2), DODSTN(1)~DODSTN(3)

Regulatory PV PISRC(1)~PISRC(6)
Regulatory Control CISRC(1)~CISRC(4), CODSTN(1)~CODSTN(4), LOWRDSTN,
RAISDSTN
FFFB CISRC(1)~CISRC(9), CODSTN(1)~CODSTN(4),
CMODSTN1~CMODSTN2
Logic Component Parts LISRC(1)~LISRC(4) (Set the input destination)
LODSTN(1)~LODSTN(12) (Set up to 12 output destination)
Block INCNCT1~INCNCT4 (Set the input destinations)
OUTCNCT (Set the output destination)

− 269 −
Chapter 6. Implementing Harmonas-DEO System

■
■Parts to be exported
•• The parts to be exported are as follows:
– Point parts
– Logic-component parts
– Block parts
•• Other parts cannot be exported. FB points cannot be exported either because they are not
parts.
•• The parameters set for parts are exported. Point generation result data is not exported.
Therefore, export is enabled regardless of whether point generation is completed or not
completed.
•• The parts for which no tag is set cannot be exported.
•• Export of the reference part depends on the part state ((1), (2) or (3) in the figure below).

Figure 6-18.

(1) Ordinary parts (when the corresponding reference parts exist)

– Ordinary parts are to be exported regardless of whether or not the corresponding refer-
ence parts exist.
(2) Reference parts (the parts for which normal reference links are provided)
– These parts cannot be exported.
(3) Reference parts (the parts for which reference links are cut)
– These parts can be export. However, data on only one tag can be export to a file.
Therefore, the following operations are performed depending on whether or not the
corresponding ordinary parts exist:
•• If the corresponding ordinary part exists in the sheet to be exported, data only on the
ordinary part is exported.
•• If the corresponding ordinary part does not exist in the sheet to be exported, data on
the reference part is exported. If more than one reference part is provided, data only
on the last found part is exported.

− 270 −
 6.1 Creating Data to Be Loaded to the Controller

■
■Export file name
The name of a file to be exported is set based on the following rule:

Table 6-22.

Export for each File name

node Format Example
Not provided Selected sheet name_point type identifier.xls EquipmentA_AI.xls
Selected sheet name_node name_point type
Provided EquipmentA_FLC005_AI.xls
identifier.xls

•• If [Sheet Unit] is selected, the name of the file to be exported will be “Sheet Name_XX.xls”
(XX: a unique ID controlled by RTC internally).
•• “Selected sheet name” indicates the sheet name selected from the Job Structure.
•• “Point type identifier” is one of the following:
•• AI, AO, DI, DO, VI, VO, DC, RP, RC, LG, LG@, FL, NM, NAR [R411 or later], STR [R411
or later], DT [R411 or later], TM, PM, BL and FF
•• “LG@” is used for logic-component parts and “BL” for block parts.
•• If a file is exported without setting [Point Type Unit], “ALL” is used.
•• Each of “RegPV”, “RegCtl” and “FFFB” is exported to a separate file regardless of the algo-
rithm type.
•• Block parts are exported to a file regardless of the block types.
•• If there is no part to be exported to a file, export is not provided for the file.

6.1.9.4 Import Parameter

■
■Operation procedures
1. Select [Implementation] → [Import Parameter...] to display the [Import Parameter] dialog
box.
2. Select from the Job Structure the sheet where the parameters are to be imported. Only one
sheet is selectable. To specify sheets in the layers under the selected sheet where the param-
eters are also to be imported, check [Contain Sub Sheets].
3. Specify in the [File:] list box the file to be imported.
4. Specify a importing operation method in [Overwrite/Create/Delete]. The following four
methods are available (the details are described later):
– Overwrite
– Create
– Overwrite or Create
– Delete
5. Use [Option] to set additional operations only when necessary.
6. Click the <Import> button. Then the Import Parameter operation starts.
7. The status of the importing operation results is displayed in the [Status:] list box. When the
<Prev status> or the <Next status> button is clicked, the ERROR line, the WARNING line
and the INFO line in the list box are selected one after another. When the <Save...> button
is clicked, the contents of the list box are saved in the file.

− 271 −
Chapter 6. Implementing Harmonas-DEO System

■
■Option
You can perform the following additional operations using [Option] in the [Import Parameter]
dialog box. To perform any additional operations, however, the parameters necessary for the
operations need to be set in the files to be imported as well.

[Read Sheet Hierarchy (&SHEET)]

•• The keys to specify which parts to import are the values of &N and &T (&M is added
for Logic Component Parts), but the value of “&SHEET” is also added as a search key.
Therefore, only the parts of the sheet which are specified by “&SHEET” can be imported.
•• In case of [Delete] operation, “&DELETE”(Tag name, to be described later) and
“&SHEET” are the keys to specify the parts to delete.
•• When import is executed using [Create] or [Overwrite or Create], if the sheet specified by
“&SHEET” does not exist, a new sheet will be created.
•• Even when import is executed according to the sheet hierarchy information, only the
sheets selected in the Job Structure Window can be imported.
•• The value of “&SHEET” is set to the path name from the root sheet as follows.
&SHEET = \sample_job\Plant_A\UNIT_A3
However, the value of “&SHEET” can be set by using “root” (lowercase letters) as follows.
If the root sheet of the path name is set as “root”, the root sheet name ( = Job Name) is not
checked in the importing operation.
&SHEET = \root\Plant_A\UNIT_A3
•• The files which include both the normal format (full path name) and the general format
(\root\...) can not be imported.

[Read Part Position (PosX,PosY)]

•• This option is configurable only when the [Read Sheet Hierarchy (&SHEET)] option is
checked.
•• When a part is created, it will be created at the position specified by “PosX” and “PosY.”
•• When a part is overwritten, a part will be moved to the position specified by “PosX” and
“PosY.”

[Read Port Information (Port(n),PortX(n),PortY(n))]

•• When the port defined by “Port(n)” is not displayed in a part, a new port will be displayed.
In this case, if “PortX(n)” and “PortY(n)” are not defined, the new port will be displayed
at the default position.
•• If “PortX(n)” and “PortY(n)” are defined, the new port will be displayed or moved to the
specified position.

[Add Link Automatically]

•• A link will be added automatically according to the parameter value of the imported
“point.parameter type.”
•• This can be used with either Create or Overwrite.
•• A link which goes through Intersheet Parts or Intrasheet Parts cannot be added.

[Only Selected Sheet]

•• Only the sheets selected in the Job Structure Window can be imported. Other sheets can-
not be imported.
− 272 −
 6.1 Creating Data to Be Loaded to the Controller

■
■[Overwrite]
•• The file is imported and settings for parameters for the “corresponding parts” are made.
– A part is judged to be the “corresponding part” if its “&N” (tag name) and “&T” (point
type) data, which must always be set, coincides with the specifications.
– For logic-component parts, a part is judged to be the “corresponding part” if an additional
condition that its “&M” (logical tag name) coincides with the specification is also met.
– When the [Read Sheet Hierarchy (&SHEET)] option is checked before importing a file, a
part is judged to be the “corresponding part” if an additional condition that its “&SHEET”
(path name of the sheet) coincides with the specification is also met.
•• The operation is performed only for “corresponding parts”. Parts cannot be created.
•• The overwriting operation is performed only for the following types of parts that are pro-
vided in the sheet specified in the Job Structure or sheets under the sheet.
– Point parts
– Block parts
– Logic-component parts
•• The following operations are performed depending on whether or not parameters are pro-
vided in the file and whether or not parameters are provided for the part:

Table 6-23.

Parameters Parameters
Operation details
in the file in the part
Provided Provided The values written in the file are to be set for the part
No operation is to be performed
Provided Not provided (However, ERROR is to be displayed for the status because this con-
stitutes a pattern in which no value can be set)
The part values are to remain unchanged
Not provided Provided (However, if a new parameter is created due to effects of other pa-
rameters, the default value is to be set)
No operation is to be performed
Not provided Not provided
(The status is not to be displayed either)

•• The following operations are performed for links:

– The operations for the generation (automatic wiring) and deletion of links are not per-
formed. However, links are deleted as a result of operations in the following cases:
•• A change is made for the parameter for making settings for the number of input/output
connections, and links are cut as a result of the change.
•• If the parameter that has been displayed as a port is deleted as a result of a importing
operation, the links connected to the port are deleted as well.
– A importing operation may cause “point.parameter type” parameters to be modified and
to generate a link configuration that is different from that of actual links. Even in this case,
the links are not deleted.
– When the [Add Link Automatically] option is checked before importing a file, a link will
be added according to the value of the imported “point.parameter type” parameter.
– Regardless of whether with or without the [Add Link Automatically] option, if an import-
ing operation causes “point.parameter type” parameters to be modified and to generate a
link configuration that differs from that of the actual links, the links will be deleted.

− 273 −
Chapter 6. Implementing Harmonas-DEO System

•• The following operations are performed for reference parts:

– If the ordinary parts for which importing operations have been performed are provided
with reference parts connected with reference links, the results of the importing operation
are reflected in the reference parts as well. The values are also reflected even if the refer-
ence parts are provided on sheets other that the selected one.
– The following operations are performed for the reference parts that are in the state that
the reference links are cut:
•• If the parts are provided on the sheet that is to be imported, the importing operation
results are reflected.
•• The importing operation results are not reflected if the parts are provided on sheets
other than the sheet that is to be imported.

■
■[Create]
•• A file is imported and parts are newly created. No operation is performed for existing parts.
•• If the same part as that to be created newly already exists (the essential parameter values of
both of the parts coincide), an error is generated and the new part is not created.
•• No link-generating (automatic wiring) operation is performed.
•• When the [Add Link Automatically] option is checked before importing a file, a link will
be added.
•• In a newly creating operation, new sheets are created under the sheet selected from the Job
Structure and parts are created on each of the sheets. The following figure shows how sheets
are created and how the parts are placed:
[The file to be imported]
[Sheet layers] AI tags: 120 definitions
Import (Create)
Selected sheet Equipment X_AI.xls
DI tags: 30 definitions
Equipment X_DI.xls
Equipment X_AI_1 (100 AI parts)
Equipment X_AI_2 (20 AI parts) Newly created
sheets and parts
Equipment X_DI (30 DI parts)

Figure 6-19.

– Up to 100 parts can be created on a sheet.

– A file is created for a sheet. The file name excluding the extension is set for the sheet name.
– If more than 100 parts are provided, parts are placed on the second and if necessary, higher-
numbered sheets as well. In such a case, an index is added to the sheet name in such a way
as xxx_1, xxx_2, xxx_3, etc.
– On a sheet, parts are placed in the order shown in the following figure:

− 274 −
 6.1 Creating Data to Be Loaded to the Controller

Figure 6-20.

– The container parts that are created on a selected sheet are also placed in the order shown
in the above figure. However, even if the number of the parts exceeds 100, the 101st and
higher-numbered parts are also placed on the same sheet repeating the way in which up to
100 parts are placed.

•• When the [Read Sheet Hierarchy (&SHEET)] option is checked before importing a file, if
the sheet specified by “&SHEET” does not exist, the specified sheet will be created. In addi-
tion, when the [Read Part Position (PosX, PosY)] option is checked before importing a file,
a part will be created at the position specified by “PosX” and “PosY.”
•• In newly creating operations, &M parameter (logical tag name) definitions for logic-com-
ponent parts are not essential.
•• The following operations are performed depending on whether or not parameters are pro-
vided in the file and whether or not parameters are provided for the part:

Table 6-24.

Parameters Parameters
Operation details
in the file in the part
Provided Provided The values written in the file are to be set for the part
No operation is to be performed
Provided Not provided (However, ERROR is to be displayed for the status because
this constitutes a pattern in which no value can be set)
Not provided Provided The default value is to be set
No operation is to be performed
Not provided Not provided
(The status is not to be displayed either)

■
■[Overwrite or Create]
•• A file is imported and either a part-overwriting operation or a part-creating operation is
performed. Which operation is to be performed is determined for each part based the fol-
lowing conditions:
– An overwriting operation is performed: When a part provided with the same essential
parameter values as those written in the file is
found
– A newly creating operation is performed: For conditions other than that above (No part
provided with the same essential parameter
values as those written in the file is found).
•• The details of each of the operations are the same as those described before for [Overwrite]
and [Create].
− 275 −
Chapter 6. Implementing Harmonas-DEO System

■
■[DELETE]
•• The parts specified in the files are deleted.
•• The parts to be deleted are specified as following format in the files.

&DELETE
AI05002
AI05003
AI05004
:

•• The user specifies the tag name to be deleted as the value of “&DELETE” parameter. If the
tag name is equal, the part is deleted.
•• If [Read Sheet Hierarchy (&SHEET)] option is checked, the parts which are equal to the
value of “&SHEET” are deleted.
•• The value of “&DELETE” must be specified with uppercase letters. If lowercase letters are
specified, an error occurs.
•• Reference Point Parts and Logic Component Parts can be deleted.
•• The encapsulated parts can not be deleted. If the tag name of encapsulated part is specified,
an error occurs.

■
■[Check operations]
•• When the Import Parameter starts, check operations are also performed. For checks on data
types and ranges of parameters to be imported, the checks equivalent to those conducted for
the property sheet for parts are conducted.
•• Even if an error is generated in checks on a parameter of a part, the other parameters of the
part are set. When a part is to be created newly, the part is created even if an error is gener-
ated in checks on a parameter of the part.

■
■Importing the files output by RTC_FB
The directory/file name of the files output by RTC_FB is as follows.
[RTC Job Directory]/fieldbus/param/NodeXXX_SegYYY.csv
XXX: Node number, YYY: Segment number
When you import the above files, please import them under the following setting.
•• The Job Structure Window : Select the root sheet
•• File : Select all files output by RTC_FB
•• Overwrite/Create : Select “Overwrite or Create”
•• Option : Check “Read Sheet Hierarchy (&SHEET)”
Check “Read Part Position (PosX, PosY)”
Check “Add Link Automatically”
(Do not check the other option except for the above)

− 276 −
 6.1 Creating Data to Be Loaded to the Controller

Note When Export Parameter/Import Parameter, attention must be paid to the following
items:
•• If more than one part with the same tag name (&N) and point type (&T) exists,
only the last found part is exported. For logic-component parts, if an additional
condition that two or more parts with the same logical tag name (&M) exist is also
met, only the last found part is exported.
•• When a part is pasted, the logical tag name is set anew automatically to
“UnNamedxxx” in RTC. Therefore, for logic-component parts, it can happen that
parts may not be imported after a pasting operation is performed for them al-
though they were able to be imported before the pasting operation is performed.
The same phenomenon also occurs for a block part, if a new block name is given
when a pasting operation is performed for the block part.
•• The “” (double quotation marks) character sequence set for cells is a reserved
word and indicates that “the parameter value is null.” Therefore, if an exporting
operation is performed in the condition that the “” character sequence is actually
set for a parameter of a part, the same result as that obtained when no specifica-
tion is made for the parameter is achieved. No “” character sequence can be set for
a part through a importing operation.
•• The maximum number of parameter names that can be exported and imported
for one file is 256. This number corresponds to the maximum number of columns
provided in an Excel file.
•• The logical tag names of reference parts for which correct reference links are pro-
vided can neither be exported nor imported using the exporting and importing
operations.
•• The user cannot specify the container order numbers to be created by a importing
operation.

− 277 −
Chapter 6. Implementing Harmonas-DEO System

6.2 Configuration of Operation Screen

The operations described below should be performed after point generation ends.

6.2.1 Specify PMDP Local Variable

Set each number of flag variables and numeric variables which can be displayed on the opera-
tion screen with local variable of PMDP point.

Step 1 Select [System Conf] from [Implementation] to display the [System Configuration]
property sheet.

Step 2 Open the [PMDP Local Variables] page on the [System Configuration] property
sheet.

Step 3 The list of process module data points will be displayed in alphabetical order on the
[PMDP Local Variables] page.

Table 6-25. Description of display items

Displayed Item Description

Tag name Process module data point defined in jobs
NN count Number of local numeric variables displayed on the operation screen
FL count Number of local flag variables displayed on the operation screen
Conformity or nonconformity with the current point database (“*”
Invalid
for nonconformity)

Step 4 Select a line from the list of process module data points and click the Set button.
The [Define PMDP Local Variables] dialog will appear.

Step 5 In the [Define PMDP Local Variables] dialog, make the following settings.
•• Enter the index of numeric variables to be displayed into the [NN range] box.
•• Enter the index of flags to be displayed into the [FL range] box.
•• To specify two or more indices, insert a comma between adjacently placed indi-
ces or use a hyphen for specifying a range of indices.
•• Enter a blank for an item that is not to be displayed.
•• To display local numeric variables on the operation screen, specify with “Process
Module Data Tag Name@NM%i%” (where, i means an index, 1 to 80).
Example: PMDP001@NN%1%
•• To display local flag variables on the operation screen, specify “Process Module
Data Tag Name@FL%1%” (i is an index, 1 to 127).
Example: PMDP001@FL%5%

− 278 −
 6.2 Configuration of Operation Screen

Step 6 After the completion of the settings, the number of NNs and the number of FLs on
the relevant point line in the list of process module data points will be counted and
updated display.

Step 7 Click the <Save> button to output the contents of settings in a CSV format file. The
directory to output the file to and file name can be set in the [Output CSV File]
dialog displayed by clicking the button. This file can be opened by applications such
as Memo Pad and Microsoft Excel and the like.

If nonconformity is found due to the deletion of the point after the PMDP local
variable for display is set, an asterisk “*” appears at the right side of the relevant
entry in the list. In addition, entry count having nonconformity also appears in the
[Data Count] group box.
If the [Hide Valid Entries] option button is checked, only the entries with noncon-
formity in the list can also be displayed.
Creating a system data file without eliminating nonconformity will cause an error.
If nonconformity is found, delete the entry by using the <Delete> button or remove
the cause for nonconformity on the sheet.

Note The local variables at the PMDP points are not subject to history collection.

Note If you perform point DB generation with the [PMDP Local Variables] page kept open,
the data on the [PMDP Local Variables] page is not updated in real time.
When you have performed point DB generation, close the [System Configuration]
dialog box once and open it again.

Restriction The number of STR16 can not be entered in [PMDP Local Variables] dialog. Please
make InTouch tag on WindowMaker if you need.

− 279 −
Chapter 6. Implementing Harmonas-DEO System

6.2.2 Configuration of History Function

Use RTC to specify a point parameter for history collection. The history function is configured
after points are completely generated.

■
■Display [Set History] Page

Step 1 Select [System Conf] from [Implementation] to display the [System Configuration]
property sheet.

Step 2 Open the [History] page on the [System Configuration] property sheet. The
[History Data] list box will appear on the [History] page.

Table 6-26. Description of display items

Displayed Item Description

Tag@Param Point parameter for history collection
Scanrate History collection cycle
Validity or invalidity with the current point database
Invalid
(“*” for invalid)

■
■Registration

Step 1 Click <Add> button on the [History] page to display [Add/Edit History] dialog. If
point generation has not yet been completed, the <Add> button remains in shaded.

Step 2 Make the following settings in the [Add/Edit History] dialog.

•• Generated points are selectable in the [Point] dropdown list.
•• A parameter by which histories can be collected is selectable from among the
parameters at the point selected in the [Parameter] dropdown list.
•• History collection cycle is selected in the [Scan Rate] dropdown list.

Step 3 Click the <Apply> button and complete the registration to add the entry to the
[History Data] list box newly.

■
■Change

Step 1 Select history definition to be changed on the [History] page and then click the
<Edit> button to display the [Add/Edit History] dialog.

Step 2 Select a history collection cycle on the [Scan Rate] drop down list.

Step 3 Click the <OK> button to change the collection cycle.

− 280 −
 6.2 Configuration of Operation Screen

■
■Delete

Step 1 Select a history definition to be deleted on the [History] page and click the
<Delete> button. In this operation, multiple histories can be specified at a time.

Step 2 When the deletion confirmation dialog appears, click the <OK> button to delete
the selected history definition.

Note The number of items for which history can be collected is determined ac-
cording to the relationship with the collection cycle and displayed on the
dialog with HU (History Unit). However, RTC does not check it, comparing
with recommended values.

Note If you have changed a parameter (DITYPE, DOTYPE, PVALGID, CTLALGID

or FFBLKTYP) that may change the tag configuration, invalidity will occur
after the point generation even if the point type is the same.
For such a parameter, delete the parameter once and register it again.

Note FB points and blocks are not subject to the history function.

■
■Save
Click the <Save> button to output in a CSV format file the current setting status, including
HU values, the number of valid data, and the number of invalid data. The output destination
directory and file name can be set in the [Create CSV File] dialog displayed when the button
is clicked. This file can be opened by applications such as Note Pad and Microsoft Excel and
the like.

•• Multiple collection cycles cannot be assigned to a point parameter. Combinations of point

parameters that have already been registered are removed from the dropdown list, so that
they cannot be selected next time and after.
•• If invalidity is found due to the deletion of the point after the history collection is defined,
an asterisk “*” appears at the right side of the relevant entry in the [History Data] list box.
In addition, entry count having invalidity also appears in the [Data Count] group box. If
the [Hide Valid Entries] option button is checked, only the entries with invalidity in the
[History Data] list box can also be displayed.
Creating a system data file without eliminating invalidity will cause an error. If invalidity is
found, delete the entry by using the <Delete> button or remove the cause for invalidity on
the sheet.

− 281 −
Chapter 6. Implementing Harmonas-DEO System

■
■Import
Importing a CSV format file can define histories all at once. The operation procedure is as
follows.

Step 1 Click the <Import> button.

Step 2 When the <Setup File Names> dialog appears, specify files you want to import. At
this time, the Ctrl key and Shift key are available to specify multiple files.

Step 3 Click the <Open> button to start import processing.

Step 4 When import ends, the end of importing operation is notified in the message box.
If an error occurs during import, an error message file named hstrimp.err is gener-
ated in the same directory as that of the CSV file imported.

•• CSV File Format (Tag Name, Parameter Name, Scan Rate)

Collection cycles should be specified in the following formats. If you specify a
character string other than the following character strings, an error will occur.

1 second: 1s, 5 second: 5s, 10 second: 10s, 30 second: 30s, 1 minute:1m, 2 min-
utes: 2m, 5 minutes: 5m, 10 minutes: 10m

Example: For [Tag name AI001, Parameter name ALENBST, Collection cycle 5
sec],
AI001, ALENBST, 5s.

The first line is considered as a comment line and is not subject to the import
processing.

Note A parameter collection cycle set before import cannot be changed by

import. To change this cycle, the contents of settings need to be deleted
in advance.

■
■Export
The current contents of settings on a history setting page is output in a format described in
import. The operation procedure is as follows.

Step 1 Click the <Export> button.

Step 2 When the [Create CSV File] dialog appears, specify a file name.

Step 3 Click the <Save> button to start export processing.

■
■Output Data
The procedure for outputting the contents of history settings and the output file are different
depending on the type of the history (InTouch history or PREXION history).
The default of the type of the history is PREXION history.
To change the type of history, set the value of “History” in [System] section of the rtcedit.ini
file as follows.

− 282 −
 6.2 Configuration of Operation Screen

Table 6-27.

rtcedit.ini Explanation
History=Prexion Setting for PREXION history
History=InTouch Setting for InTouch history

•• For PREXION history

When the <Output> button is clicked on the [History] page, the contents of history settings
are output to file history.csv in the directory “it” just under the job directory.
•• For InTouch history
When the [Create System Data Files] command is executed, the contents of history settings
are output to file db.csv in the directory “it” just under the job directory.

Note If you perform point DB generation with the [History] page kept open, the data on
the [History] page is not updated in real time. When you have performed point DB
generation, close the [System Configuration] dialog box once and open it again.

6.2.3 Configuration of Alarm Function

Alarm functions used for operations are configured by RTC. That is, if information related
to alarm is set, the information can directly be used for alarm configuration on the property
sheet of point parts.

6.2.4 Managing Screen Information

Files related to screens (referred to as InTouch applications) are allowed to be placed in any
directory, their paths must be alpha numeric characters.

6.2.5 Creating System Data File

Configuration information, including tag names created in the RTC editor, is passed to
Harmonas-DEO functions in the CSV format.
A system data file is created in a directory referred to as “\{Job Directory}\IT\” in the follow-
ing procedure.

When “OFF” is set in the MMITGSEL (MMI TAG OUTPUT) parameter of a part, the
InTouch tags of the part will not be exported to the db.csv file. You can reduce the number
of InTouch tags to be exported using this parameter. However, when the type of the history
is “InTouch”, it will be exported regardless of the MMITGSEL parameter (see Section 6.2.2).
The total number of tags allowed is a maximum of 61,405, including InTouch system tags,
Harmonas-DEO system tags, and user-defined tags.

− 283 −
Chapter 6. Implementing Harmonas-DEO System

Step 1 Make the Job Structure Window active, select [Implementation], and execute the
[Create System Data Files] command.

Step 2 This operation will display the [Create System Data] window.

Step 3 Click the <Execute> button in the dialog. The execution status is displayed in the
[Execution Status] list box. If this operation fails, remove the cause of the error
displayed in the [Execution Status] list box and execute the operation again.

Note If the control data file for boxes and points has not been created correctly, an error
will occur. Create the control data file and system data file based on the same point
database and pay attention to the creation timing.

Note The contents of the system data file are different depending on the following
conditions.
•• When the value of “History” in [System] section of the rtcedit.ini file is “InTouch”
The contents of history settings are output to system data file.
•• In other cases (Default)
The contents of history settings are not output to system data file.

Note By setting the following registry key, you can alter job directory writing operations
to the hdse_w.ini file and the udpman.ini file.
Registry:
(64bit OS [R412])
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Yamatake\SourceManagement
(32bit OS)
HKEY_LOCAL_MACHINE\SOFTWARE\Yamatake\SourceManagement
Key:
RtcDontUpdateJobDirectory

Writing to hdse_w.ini file and

RtcDontUpdateJobDirectory Value
udpman.ini file
0 Writing to job directory is performed
1 Writing to job directory is not performed

The job directory writing operations altered by this setting are the creation of sys-
tem data files, the loading of controller data files, and the merge of system data files.

Note If Create PDB is failed for any node, warning is displayed when <Execute> button on
[Create System Data] Dialog is pressed.

Note If the FF device is defined in RTC_FB or the HART device is defined in RTC_HT, the
consistency checking of hartdev.csv, ffdev.csv, and ffblock.csv is executed.
For the consistency checking, see the Function Manual of RTC Fieldbus Tool or RTC
HART Tool.

− 284 −
 6.3 Operation Leading Up to Operation Screen Startup

6.3 Operation Leading Up to Operation Screen Startup

After points have been generated by RTC or System Data Files have been completed, you can
start operations. The operation procedure is as follows.

Step 1 Load the controller program files to the controller by the RTC Editor.
Note : When the controller is not XPC, FLC, PL, PL2, FC, PC4 [R411 or later] this
procedure is unnecessary. This procedure is necessary for PRC only.

Step 2 Load Controller Data files to the controller by the RTC Editor.

Step 3 Activate the operation screen.

Step 4 Save the check point file.

Step 5 Load the check point files.

■
■Controller Operating States
To load the controller program files and controller data files, the operation state of the control-
ler needs to be taken into account.
The controller should be put in the [ALIVE] state to load the controller program files, and the
[IDLE] state to load the controller data files. Since a controller except PRC are not put in the
[ALIVE] state, the program files do not need to be loaded.

Basically, the controller operating state can be changed on the status display screen. To load the
controller program files and controller data files, however, a means of changing the controller
state to [ALIVE] and [IDLE] is also provided in the RTC Editor.

ALIVE -- Controller is Powered On

(This status exists in neither
XPC,FLC,PL,PL2,FC,PC4 [R411 or later])
(1) (4)

IDLE -- Controller can accept Data

(2) (3)

RUN -- Controller is running

Figure 6-21.

(1) To change the state from ALIVE to IDLE, load the controller program. When the program
has been completely loaded, the status automatically changes to [IDLE].
For a controller except XPC, FLC, PL, PL2, FC, PC4 [R411 or later] their initial state is
IDLE, and they are not put in the ALIVE state. This procedure is therefore unnecessary
for them.

− 285 −
Chapter 6. Implementing Harmonas-DEO System

(2) To switch from [IDLE] to [RUN], load the controller program in the order of box and
point, and then change the state from the status display screen of the operation screen or
from the RTC Editor.

(3) Perform the operation of switching from [RUN] to [IDLE] from the status display screen
of the operation screen or from the RTC Editor.

(4) Perform the operation of switching from [IDLE] to [ALIVE] from the status display
screen of the operation screen or from the RTC Editor.
When the controller is not XPC, FLC, PL, PL2, FC, PC4 [R411 or later] this procedure is
unnecessary.

6.3.1 Loading Controller Program Files

The control programs needs to be loaded in the following cases. In these cases, the controller
is limited to PRC.
•• When activating the controller first
•• When the controller was shut down
•• When the node numbers of the controller are changed

The controller programs are loaded according to the following operation procedure.

Step 1 Make the job hierarchy diagram active, select [Implementation] and then execute
the [Load Controller Program/Data Files] command.
This operation will open the [Load Control Program/Data] dialog.

Step 2 Select a node to be loaded from the [Node List] list box in the dialog. When the
controller is configured as redundant, select the [Left] or [Right] in [Select Node]
by using its option button. Click the <Display Update> button to display the cur-
rent node state under the option button.

Step 3 To load the controller program files, the relevant node must be put in the ALIVE
state.
•• If the node is put in the RUN state, click the <IDLE> button in the [Change State]
group box, and then click the <SHUTDOWN> button.
•• If the node is put in the IDLE state, click the <SHUTDOWN> button in the
[Change State] group box.
•• The <SHUTDOWN> button is valid only when target nodes are PRC. On the
operation screen, PL, PL2 and FC nodes can be shut down, but this is not sup-
ported in RTC Editor.

Step 4 Select the <Program> button from the [Program/data] box.

Step 5 Click the <Load> button. The loading state is displayed in the [Load Status] list box.

Note For PRC for which redundant nodes have been specified, select both
[Left] and [Right] in [Select Node], and then load the program files.

− 286 −
 6.3 Operation Leading Up to Operation Screen Startup

6.3.2 Loading Controller Data Files

The controller data files are loaded according to the following procedure.

Step 1 Make the job hierarchy diagram active, select [Implementation], and execute the
[Load Controller Program/Data Files] command to invoke the [Load Controller
Program/Data] dialog.

Step 2 From the [Node List] list box in the dialog box, choose the node to be loaded.
When the controller has a redundant organization, choose [Left] and [Right] from
[Select Node] by clicking option buttons. Click the <Update> button, and the status
of the current node is displayed under each option button.

Step 3 If the data type is box data when the controller data files are loaded, the subjected
node must be put in the IDLE state.
•• If the controller is put in the [RUN] state, click the <IDLE> button in the [Change
State] group box.
•• If the controller is in the [ALIVE] state, load the controller program files first.
•• A point to be loaded can also be chosen by using a point name list file. The point
name list file is a text file in which a point name is described on each line. Click
the <Select Point> button, and a dialog box is displayed. From the dialog box,
choose the point name list file, and the point of the [Point List] list box is chosen.

Step 4 Select the [Box] option button in [Data] group box.

Step 5 Click the <Load> button. The load execution status of box information will be
displayed in the [Load Status] list box.

Step 6 When the loading state is successfully displayed, select the [Point] option button in
[Data] group box.

Step 7 If the data type is point data when the controller data files are loaded, the relevant
node must be put in the IDLE or RUN state.
•• When the controller is put in the [RUN] state, select the <By Point> button in the
[Load] group box, and choose one or more points to be loaded from the [Point
List] list box. At this time, make the point(s) to be loaded INACTIVE (NL or
LOADED in the case of PMDP).
If the point to be loaded is ACTIVE (DLL, END, PAUSE, FAIL, ERROR, RUN in
the case of PMDP), the loading of this point will cause an error.
•• When the controller is put in the [IDLE] state, select the <By Node> button in
the [Load] group box.

Step 8 Click the <Load> button, and the loading state of point information will be dis-
played in the [Load Status] list box and in the Progress dialog box.

Step 9 If the state is successfully displayed, the operation is completed.

− 287 −
Chapter 6. Implementing Harmonas-DEO System

Note If box data is selected from the data types when the controller data files are loaded,
a warning issued by LMUXPVLM parameter may be displayed. The old version con-
troller (For example, before XPC R6.9) and some controller types do not support
these parameters, and therefore may cause a warning to be displayed when the
controller data files are loaded. If this warning is displayed, no problem will occur
unless this function is not used.

Note If box data is selected from the data types when the controller data files are loaded,
a warning issued by ACKSTOPT and DCTRACK parameter may be displayed. The old
version controller (For example, before XPC R6.14) and some controller types do
not support these parameters, and therefore may cause a warning to be displayed
when the controller data files are loaded. If this warning is displayed, no problem
will occur unless this function is not used.

Note When the point data are loaded, a warning issued by RESETOPT parameter may be
displayed. The old version controller (For example, before XPC R6.17) and some con-
troller types do not support these parameters, and therefore may cause a warning
to be displayed when the controller data files are loaded. If this warning is displayed,
no problem will occur unless this function is not used.

Note [R412]
When the point data are loaded, a warning issued by following parameters may be
displayed. The old version controller (For example, before XPC R6.17) and some con-
troller types do not support these parameters, and therefore may cause a warning
to be displayed when the controller data files are loaded. If this warning is displayed,
no problem will occur unless this function is not used.
CVGAPHI
CVGAPLO
OPALDB
OPHITP
OPLOTP

Note When the point data are loaded, a warning issued by OP_SEL parameter may be dis-
played. The old version controller and some controller types do not support these
parameters, and therefore may cause a warning to be displayed when the controller
data files are loaded. If this warning is displayed, no problem will occur unless this
function is not used.

Note When it is necessary to hold down the communication load resulting from the load-
ing (such as when the loading is to be done in a system already in operation), lower
the value of the LoadParamPerSec key in the [Browser] section of the rtcedit.ini file.
This lowers the loading speed and holds down the communication load. The recom-
mended value in these cases is 50.

− 288 −
 6.3 Operation Leading Up to Operation Screen Startup

Note When the controller data files are loaded, a job directory is set in the hdse_w.ini file.
The operation screen cannot be activated until the controller data files have been
loaded.
To use another job for activating the operation screen, exit the operation screen
once, reload the controller data files, and then reactivate the operation screen.

Note By setting the following registry key, you can alter job directory writing operations
to the hdse_w.ini file and the udpman.ini file.
Registry:
(64bit OS [R412])
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Yamatake\SourceManagement
(32bit OS)
HKEY_LOCAL_MACHINE\SOFTWARE\Yamatake\SourceManagement
Key:
RtcDontUpdateJobDirectory

Writing to hdse_w.ini file and

RtcDontUpdateJobDirectory Value
udpman.ini file
0 Writing to job directory is performed
1 Writing to job directory is not performed

The job directory writing operations altered by this setting are the creation of
system data files, the loading of controller data files, and the integration of system
data files.

Note When the loading is performed point by point, performing the loading from RTC
alone is sufficient in the following cases:
•• Cases where the parameter values of already defined points are changed, except
the following cases.
− Change of the algorithm for an adjustment control point or adjustment PV point
− Change of the DITYPE parameter for a digital input point or the DOTYPE param-
eter for a digital output point
− Change of descriptors
− Change of user-defined enumerations
− Change of box color
− Change of the alarm priority of points
•• When hardware addresses are used as the reference point names of points, even
new points can be referenced.

In other cases mentioned below, it is necessary to restart SE or InTouch:

•• Cases where the parameter of a point to be changed is one of the items listed as
restrictions above
•• Cases where a new point is added
•• Cases where a slot number or module number is changed with the original point
name kept unchanged

− 289 −
Chapter 6. Implementing Harmonas-DEO System

Note If “BOX Variable is included” is checked when the control data files are created, Box
variable data uploaded is also loaded. If parts of the correspondent Box variables
are found, the data defined on the parts takes precedence in loading.

Note If the error “Invalid_Destination_Point_Id” appears when the controller data files of
a point are loaded, relationships of linkage between points are expected not to have
been constructed. In such a case, make an attempt to load the controller data files
again. If this error still appears, the point type of the point specified by the linkage
relationship may be inappropriate.

For example:
When points connected by cascade connection are newly loaded, the load will fail
depending on the sequence of the load. This failure is caused by the load sequence
of the primary and secondary cascade points, and it can be avoided by loading with
the node unit.

Note If Create PDB is failed for the target node or Controller Data File is not created after
PDB creation, warning message is displayed.

■
■Making the [Change State] button of the Controller invisible
To prevent the operating state of the Controller from being subjected to any operational error,
the <RUN>, <IDLE>, and <SHUTDOWN> buttons can be set to be invisible.
Registry:
(64bit OS [R412])
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Yamatake\SourceManagement
(32bit OS)
HKEY_LOCAL_MACHINE\SOFTWARE\Yamatake\SourceManagement
Key:
NodeCommandInvisible

NodeCommandInvisible Value Whether the button is visible or invisible

The <RUN>, <IDLE>, and <SHUTDOWN> buttons
0
will be made visible This setting is selected by default
The <RUN>, <IDLE>, and <SHUTDOWN> buttons
1
will be made invisible

If the <RUN>, <IDLE>, and <SHUTDOWN> buttons are invisible, the operating state of the
Controller must be changed from the controller status screen. Note that the <SHUTDOWN>
button is enabled only for PRC.

■
■Specify Point Type
Points to be displayed in the [Point List] list box can be narrowed down by point types.
Select a point type to be displayed in the [PNTTYPE] combo box. The Specify Point Type is
executable only when the <By Point> is selected in the [Load] group box. Selection of “ALL”
displays all point types without narrowing down the point types.

− 290 −
 6.3 Operation Leading Up to Operation Screen Startup

■
■Change PTEXECST
The execution state (PTEXECST parameter) of points displayed in the list box of a tag name
list in the dialog can be changed.
•• Select a tag name to be changed in the list box, and select the buttons for values to be
changed from the [PTEXECST] group box (multiple values are selectable). The Execution
State can be changed only when you choose <By Point> in the [Load] group box.

•• When the Execution State has been completely changed, the current execution state of the
selected point is obtained from the controller and is displayed in the list box of the tag name
list. In addition, selecting the <Update> button updates displays of the parameter values of
all tag names in the list box. In cases where the parameter values are not obtained correctly,
the following character strings will appear in place of the parameter values.

Table 6-28.

Displayed character string Meaning

---- Default value displayed in the list box
Cases where configuration is mismatched
@@@@
(point type does not exist in the parameter)
Cases where parameter values cannot be obtained for reasons
####
other than the above

■
■Change PV Source
You can change the PV source (PVSOURCE parameter) at a point displayed in the list box
of a tag name list in the dialog. The operation procedure etc. are the same as those for the
execution state.

Note For AI and DI points of the PRC node, the PVSOURCE parameter is internally held
in the controller even if the PVSOURCE parameter is set to prevent the configu-
ration (the setting is determined by the values of the PNTFORM and PVSRCOPT
parameters).
Thus, @@@@ is not displayed (display of configuration mismatch), but the
PVSOURCE value held in the controller is displayed.

■
■Loading FB Point
Click the <FB Load> button to display the dialog in which FB points can be loaded in point
units. For details, see Section 6.3.2.1.

■
■Loading module
Click the <Load Module> button to display the dialog in which I/O module can be loaded in
module units. For details, see Section 6.3.2.2.

− 291 −
Chapter 6. Implementing Harmonas-DEO System

6.3.2.1 Loading FB Points

Different from points of other point types, an FB point has a parameter for exclusive control of
the version information and loading. Like other point types, an FB point can be loaded in the
[Load Controller Program/Data] dialog. However, these parameters cannot be checked. In the
[FB Point Load] dialog, an FB point can be loaded in point units while FB point parameters
are being checked.

Note Loading an FB point from the [FB Point Load] dialog box and loading an FB point
from the [Load Controller Program/Data] dialog box set the same data in the con-
troller. Therefore, when an FB point has been loaded or points have been loaded on
a node basis from the [Load Controller Program/Data] dialog box, it is not necessary
to load them anew from the [FB Point Load] dialog box.

Note If Create PDB is failed for the target FB point or Controller Data File is not created
after PDB creation is finished, warning message is displayed.

■
■Checking Controller Information
Parameters of an FB point loaded to the controller are listed. Click the <Update> button to
obtain the parameter values from the controller and display them. However, if the parameter
values are not obtained correctly, the following character strings are displayed in place of the
parameter values.

Table 6-29.

Displayed character string Meaning

---- Default value displayed in the list box
@@@@ Cases where configuration is mismatched
Cases where parameter values cannot be obtained for
####
reasons other than the above

In addition to the configured parameters, version, execution status, and load status are dis-
played. They are compared with the [Config Info] list displayed below to check whether or not
the latest data has been loaded.

■
■Checking Configuration Information
Parameters of an FB point configured in jobs are displayed as a list. Select a node to be loaded
from the [Node List] list box. In addition to the parameters configured in jobs, the version is
displayed.

■
■Loading FB Points
FB points are loaded in point units.
Select the FB points displayed in the [Controller Info] list (multiple points are selectable) and
then press the Load button.

− 292 −
 6.3 Operation Leading Up to Operation Screen Startup

■
■Interruption of Loading
When FB points are loaded, the controller locks them (loading status becomes “LOADING”),
preventing the FB points from being accessed from other nodes. If an error occurs during the
loading of the FB points, the FB points may be kept locked.
In that case, select an FB point displayed in the [Controller Info] list, and then click the
<ABORT> button to unlock it.

■
■Change Execution Status
The execution status of FB points can be changed.
Select an FB point displayed in the [Controller Info] list, and press the execution status button
you want to change.

6.3.2.2 Loading Module Data

In [Load Module] dialog, the I/O module can be loaded individually. As a result, the I/O
module can be added/modified while the controller is RUN state.

Loading Module Data function supports following module types.

Table 6-30.

Node Type Supported Module Type

PC4 [R411 or later] All module type
FC FBLM

■
■Loading Module Data
Select the I/O modules displayed in the [Module List] list (multiple modules are selectable)
and then click the <Load Module> button. Selected I/O modules are loaded into the controller.

Loading module requires following actions before loading.

Table 6-31.

Node Type Action

•• Set SCHDTYPE parameter to “IOMAN” in [Node Conf2].
•• Set IOMCYCLE of I/O module.
•• Change Node Status to IDLE or PTEXECST of all points on I/O to
PC4 [R411 or later] INACTIVE.
•• If the user wants to change IOMFILEA/B, IOMCARDA/B,
IOMTYPE, IOREDOPT parameters, delete the I/O module by
Deleting Module Data function.
•• Set IOMCYCLE of I/O module other than “AUTO”.
FC •• If the user wants to change IOMSEG, IOMRATE, IOMCYCLE,
IOPREDOPT, delete all points on the I/O module.

Note If box data has never been loaded, the loading module function is not available.
Please load box data after cold restarting.

− 293 −
Chapter 6. Implementing Harmonas-DEO System

■
■Loading Module Data and Point Data
Select the I/O modules displayed in the [Module List] list (multiple modules are selectable)
and then click the <Load Module & Point> button. Selected I/O modules and points on the
modules are loaded into the controller.

■
■Checking Module List
Select node in [Node List] list box.
Click the <Update> button to obtain the parameter values from the controller and display
them. However, if the parameter values are not obtained correctly, the following character
strings are displayed in place of the parameter values.

Table 6-32.

Displayed character string Meaning

---- Default value displayed in the list box
@@@@ Cases where configuration is mismatched
Cases where parameter values cannot be obtained for
####
reasons other than the above

■
■Loading Points
Select the points in the [Point List] list (multiple points are selectable) and then click the
<Load Point> button.

■
■Checking Point List
Select node in the [Node List] list box. Points and their parameters in the node are displayed.
You may refine the point list by selecting any modules in the [Module List] list.
Click the <Update> button to obtain the parameter values from the controller and display
them. However, if the parameter values are not obtained correctly, the following character
strings are displayed in place of the parameter values.

Table 6-33.

Displayed character string Meaning

---- Default value displayed in the list box
@@@@ Cases where configuration is mismatched
Cases where parameter values cannot be obtained for
####
reasons other than the above

■
■Change Execution Status
Select an point displayed in the [Point List] list, and click the <ACTIVE> or <INACTIVE>
buttons you want to change.

■
■Saving the Load Status
Displayed text in the [Load Status] list can be saved in the text file.
Click the <Save> button, [Save Status Information] dialog is displayed.

− 294 −
 6.3 Operation Leading Up to Operation Screen Startup

6.3.3 Activate Operation Screen

Activating the operation screen requires a system data file to exist.

Step 1 Perform a DBLoad to specify “\{Job Directory}\IT\db.csv” as a loading source file.

Step 2 Select [DEO] from the [Start] menu to activate SE.exe and InTouch.

6.3.4 Save Check Point File

Clicking the <Check Point Save> button on the system status window of the operation screen
allows you to save the operation state in a check point file.
The check point file includes the following files and is created in a directory referred to as “\
{Job Directory}\CP\”.

•• System data file (db.csv, tag.csv, etc.)

•• Check point file (A check point file has the file name NNNnnn.cp, of which NNN means
a node type and nnn means a node number. In the case of PL2, however, the file name is
XPLnnn.cp.)

6.3.5 Loading Checkpoint Files

Clicking the <Load Check Point> button on the system status window of the operation screen
allows you to load the operation states from checkpoint files.
When the node status is IDLE in a state where the control program is loaded, the checkpoint
files can be loaded.

6.3.6 Uploading Control Data

During the online operation, point information can be changed on the detailed screen etc.
Such changes must be reflected to their basis, which is the point definition of the RTC editor.
The controller data upload function is provided for this purpose, so that the point information
retained in the controller can be saved as RTC information and reflected to the control proper-
ties. The units of upload are divided into the entire node and individual point.

This function can upload the following data from controllers.

•• The parameters in property sheet of Control Parts
•• The parameters in [BOX Variable Edit Display] window
•• The parameters in [PMDP Local Value Edit Display] window
•• IOMCYCLE parameters in System Configuration [R411 or later]

− 295 −
Chapter 6. Implementing Harmonas-DEO System

In the following cases, uploading ends erroneously.

When selecting multiple points, if even one error occurs, uploading as a whole ends
abnormally.
•• When the controller is not defined
•• When communication with the controller cannot be provided
•• When the controller is put in the ALIVE state
•• When controller data has not yet been loaded
•• When parts corresponding to points subject to uploading have not yet been loaded
•• When parts corresponding to points subject to uploading are not found on the sheet
•• When both values are different, even though Access Lock of the parameters is “PntBld” (If
for example, the linked destination is changed by RTC, the destination is handled as a place
where uploading cannot be done.)
•• When points for tag names that are set are not generated by an Entity_Param type
•• When the settings of I/O module except IOMCYCLE on RTC Editor and controllers are
different [R411 or later]

Note In rtcedit.ini file, set “OutputAllUploadError=TRUE” key under [Browser] section. All
error can be displayed comparing RTC job data with controller data.

■
■Uploading Box Variable
Box variable can be uploaded to RTC. The uploading can be done only when “By Node” is ad-
opted for the uploading. The uploading can be done for Box variable of all slots of the selected
nodes in the [Node List:] list box. However, the only data to be uploaded are the parameters
of the following variable types.

Table 6-34.

Variable Type Parameter to be uploaded

Box Flag PV
Box Numeric PV, PVFORMAT [R411 or later]
Box String [R411 or later] STR64
Box Datetime [R411 or later] TIME, TMFORMAT
Box Timer TIMEBASE, SP

Uploaded Box variable data is retained in the RTC. When creating a controller data file, you
can write the uploaded Box variable data into the file.

■
■Uploading PMDP internal variables
The parameters of the variables held by PMDP points can be uploaded to RTC Editor.
The uploading is done to a specified PMDP point. In the case of uploading on a node basis, the
uploading is done to all the PMDP points of a node chosen. The parameters to be uploaded
are FL(1) to FL(127), NN(1) to NN(80), STR16(1) to STR16(5) [R411 or later], TIME(1) to
TIME(5) [R411 or later] and TMFORMAT(1) to TMFORMAT [R411 or later]. Uploaded
PMDP internal variables data is retained inside RTC Editor. When a controller data file is
created, uploaded PMDP Local variables data can be written into the file.

− 296 −
 6.3 Operation Leading Up to Operation Screen Startup

■
■Operation Procedure

Step 1 Select [Implementation] and execute the [Upload Controller Data] command. This
will display the [Upload Controller Data] dialog.

Step 2 Select Nodes in the [Node list] list box (multiple nodes are selectable).

Step 3 In the [Upload Option] group box, select either a By Node (subject to all points
included in the nodes) or a By Point (select a desired one from the points included
in the nodes). If you select “By Point”, select points (multiple points are selectable)
in [Point List] list box.

Item Operation
By Node Parameters of all points in selected nodes are uploaded.
By Point Parameters of selected points are uploaded.

Step 4 Select data in [Data to be uploaded] group box.

Item Operation
Point Point parameters are uploaded and reflected in parts.
PMDP Local Values are uploaded and reflected in [PMDP Local
PMDP Local Value is
Value Edit Display] window. This item is available when “Point”
included
item is checked.
Box variables are uploaded and reflected in [BOX Variable Edit
BOX Variable is in-
Display] window. This item is available when “By Node” and
cluded
“Point” items are selected.
IOMCYCLEs are uploaded and reflected in [IOM Conf] page
IOMCYCLE
in Node Conf. This item is available when “By Node” item is se-
[R411 or later]
lected.

Step 5 Click the <Execute> button. If an error occurs in the uploading, error information
will appear in the [Upload Status] list box in the dialog.

Restriction There are no parameters for unit numbers at the flag point with the slot numbers
mentioned below. For these flag parts, unit numbers are not uploaded. As a result,
the values of the unit ID (UNIT) parameters are kept unchanged.
•• With PRC and PL, slot No. 129 and later
•• With XPC, PL2, FC and PC4 [R411 or later], slot No. 2049 and later
•• With FLC, slot No. 513 and later

Note To reflect the uploaded content to the controller data file, conduct the creation of
the controller data file after executing the point generation again.

Note If the job has over 1000 sheets (include sheets in Job Repository), uploading works
slowly for saving memory.
Therefore uploading takes long time than usual to complete.

− 297 −
Chapter 6. Implementing Harmonas-DEO System

■
■Detect invalid point by node uploading
When “By node” Upload Option is selected, following controller data is checked. If invalid
point data is found, warning message is displayed.

[Checking Item]
•• Detect following parameter mismatch with the Job data.
NCTLSLOT, NPVSLOT, NLOGSLOT, NDCSLOT, NPMSLOT, NNUMERIC,
NNMARRAY [R411 or later], NSTRING [R411 or later], NTIME [R411 or later],
NFBSLOT
•• Detect I/O module type mismatch with the Job data.
•• Detect not-used slot which PTEXECST is ACTIVE.
RegCtl, RegPV, LOGIC, DigComp
•• Detect not-used slot which SEQSLOTSZ is not 0.
ProcMod
•• Detect not-used slot which LOADSTAT is not NONE.
FB
•• Detect not-used slot which PNTFORM is FULL.
AI, DI, BOX FLAG (Only the slot which has ALENBST parameter)

6.3.7 Deleting Controller Data

Using this function, however, you can delete point information already loaded, even if the
controller is running, and can initialize the parameters.
The function will cause an error in the following cases:
•• When communication with the controller cannot be provided
•• When the controller is not put in the RUN or IDLE state
•• When the controller is put in the RUN state, but the point is put in the ACTIVE state

■
■Operation Procedure

Step 1 Select [Implementation] and execute the [Delete Controller Data] command. This
will display the [Delete Controller Data] dialog.

Step 2 Select Nodes in the [Node list] list box.

Step 3 Select the [I/O Slot] radio button and module number. Or select the [Control Slot]
radio button and point type.

Step 4 Select points you want to delete from the [Slot List] list box. Multiple points are
selectable.

Step 5 Click the <Delete> button. Points on the specified slots will be deleted.
If point deletion causes an error, the execution status will appear in the [Delete
Status] list box in the dialog.

Note If you want to delete points, the points must be INACTIVE(OFF) or the
node must be IDLE.

− 298 −
 6.3 Operation Leading Up to Operation Screen Startup

■
■Deleting points
If you carry out deletion from the [Delete Controller Data] dialog box, the point data in the
controller is initialized, but the point parts, tags, etc. in RTC Editor remain unchanged. To
completely eliminate the points from the system, perform the following operations:

Step 1 Exit SE and the operation screen.

Step 2 Start RTC Editor, and from the job, delete the point parts of the points to be deleted.

Step 3 Generate points, and create system data files.

Step 4 Restart the operation screen.

■
■Change PTEXECST
The point execution state (PTEXECST, PROCMOD, and SEQEXEC parameters) can be
changed.
•• Select a tag name(s) you want to change in the list box (multiple tag names are selectable),
and select the button for a value you want to change from the [Change State] group box.
•• When the execution state is completely changed, the current execution state of the selected
point will be obtained from the controller to update the displayed contents of the [Slot List]
list box. In addition, selecting the <Update> button updates the displayed parameter values
of all tag names in the list box. In cases where parameter values are not correctly obtained,
however, the following character strings will appear in place of the parameter values.

Table 6-35.

Displayed character string Meaning

---- Default value displayed in the list box
@@@@ Cases where configuration is mismatched
Cases where parameter values cannot be obtained for
####
reasons other than the above

■
■Making the [Change State] button of the Controller invisible
To prevent any operational error, the <RUN> and <IDLE> buttons can be set to be invisible.
Registry:
(64bit OS [R412])
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Yamatake\SourceManagement
(32bit OS)
HKEY_LOCAL_MACHINE\SOFTWARE\Yamatake\SourceManagement
Key:
NodeCommandInvisible

NodeCommandInvisible Value Whether the button is visible or invisible

The <RUN>, <IDLE>, and <SHUTDOWN> buttons
0
will be made visible This setting is selected by default
The <RUN>, <IDLE>, and <SHUTDOWN> buttons
1
will be made invisible

If the <RUN> and <IDLE> buttons are invisible, the operating state of the Controller must be
changed from the controller status screen.
− 299 −
Chapter 6. Implementing Harmonas-DEO System

■
■Deleting module
Click the <Delete Module> button to display the dialog in which I/O module can be deleted
in module units. For details, see 6.3.7.1, “Deleting Module Data.”

6.3.7.1 Deleting Module Data

In [Delete Module] dialog, the I/O module can be deleted individually. As a result, the I/O
module can be deleted while the controller is RUN state.

Deleting Module Data function supports following module types.

Table 6-36.

Node Type Supported Module Type

PC4 [R411 or later] All module type
FC FBLM

■
■Deleting Module Data
Select the I/O modules displayed in the [Module List] list (multiple modules are selectable)
and then click the <Delete Module> button. Selected I/O modules are deleted from the
controller.

Deleting module requires following actions before deleting.

Table 6-37.

Node Type Action

•• Set SCHDTYPE parameter to “IOMAN” in [Node Conf2].
PC4 [R411 or later] •• Change Node Status to IDLE or PTEXECST of all points on I/O to
INACTIVE.
FC •• Delete all points on the selected I/O module.

■
■Checking Module List
Select node in [Node List] list box.
Click the <Update> button to obtain the parameter values from the controller and display
them. However, if the parameter values are not obtained correctly, the following character
strings are displayed in place of the parameter values.

Table 6-38.

Displayed character string Meaning

---- Default value displayed in the list box
@@@@ Cases where configuration is mismatched
Cases where parameter values cannot be obtained for
####
reasons other than the above

■
■Deleting Points
Select the points in the [Point List] list (multiple points are selectable) and then click the
<Delete Point> button

− 300 −
 6.3 Operation Leading Up to Operation Screen Startup

■
■Checking Point List
Select node in the [Node List] list box. Points and their parameters in the node are displayed.
You may refine the point list by selecting any modules in the [Module List] list.
Click the <Update> button to obtain the parameter values from the controller and display
them. However, if the parameter values are not obtained correctly, the following character
strings are displayed in place of the parameter values.

Table 6-39.

Displayed character string Meaning

---- Default value displayed in the list box
@@@@ Cases where configuration is mismatched
Cases where parameter values cannot be obtained for
####
reasons other than the above

■
■Change Execution Status
Select an point displayed in the [Point List] list, and click the <ACTIVE> or <INACTIVE>
buttons you want to change.

■
■Saving the Delete Status
Displayed text in the [Delete Status] list can be saved in the text file.
Click the <Save> button, [Save Status Information] dialog is displayed.

− 301 −
Chapter 6. Implementing Harmonas-DEO System

MEMO

− 302 −
 Chapter 7. Multiengineering

Chapter 7. Multiengineering
This section describes multiengineering.
The engineering methods can be divided into the following two types:

■
■Single engineering
Engineering operations for constructing the system are performed using an RTC job (Other
sections of this manual are basically described based on this single engineering).

■
■Multiengineering
Engineering operations for constructing the system are performed using multiple RTC jobs
in parallel.
Multiengineering enables parallel operations until the final stage of the engineering, reducing
engineering man-hours.

− 303 −
Chapter 7. Multiengineering

7.1 Operation Procedure

The configuration diagram and operation procedure are shown in following Figure.

Engineering PC Engineering PC

RTC Editor RTC Editor RTC Editor

Job A System Job B Job C (master)
definition file
(1)
(2) (2)
(1) (1)
(3) (3)
(2) (1) Creation of logic diagram
(3)
(2) Import/export for system definition
System System System (3) Point generation, and creation of system data files
data file data file data file
(4) Integration of system data files
(5) Creation of controller data files
(6) Load
Engineering is possible on each standalone PC. (7) Upload

Integration needs to be done in the same network.

Engineering PC Engineering PC

RTC Editor RTC Editor RTC Editor SE

Job A Job B Job C (master) hdse.ini
(4)

(4)
(5) (5) (5) (4)
RTCRUN
udpman.ini

System Controller System Controller System Controller Integrated system

data file data file data file data file data file data file data file

(4) Reference to file (integration of system data file)

(6) Load (7) Upload (broken line)

(heavy line)
Output
Reference
Controller: 01 Controller: 02

Figure 7-1.

The following describe Working Steps (1) to (7) shown in Figure 7-1. For details, see the rel-
evant sections described later.
In this figure, three jobs “A”, “B”, and “C” are used as examples for engineering operations for
two controllers “01” and “02”. Of these jobs, job “C” is placed as the master job to show the
operation procedure.

(1) Creation of Logic Diagram

A logic diagram for each of jobs “A”, “B”, and “C” is created by using the RTC editor. How to
divide the jobs is described below.

•• When performing multiengineering, place one job as the “master job” to start the opera-
tion. There is no parameter setting for whether a job is the master or not. For the operation,
specify a job as a master job and control data common to jobs (node definition, unit defini-
tion, etc.). When integrating system data files, start with the master job.

− 304 −
 7.1 Operation Procedure

•• There is no parameter setting for whether or not jobs are subject to multiengineering, either.
The setting of whether or not a job is subject to multiengineering is determined by select-
ing the subjected job in the process for “integration of system data files” shown in Step (4).
It is possible to make the master job subject to the integration. However, a system data file
that initially exists in the master job is replaced with an integrated file. In this case, see the
note in Section 7.4
For the operation, the master job itself is not made subject to the integration, but is placed
as a job to integrate other jobs. By this operation, jobs can be integrated disregarding the
note mentioned above.

Note In a job where a Batch management package is used, the multi-engineering func-
tion is unavailable.

Note When system data files are completely integrated, the path of the job directory
executing the integration of the hdse_w.ini file and udpman.ini file is then written.
When Hdse.exe is activated, or when the RTC runtime is activated, system data files
of the “it” directory under the job directory where the integration is done are to be
read. In addition, system data files to be changed online are placed in the “it” direc-
tory under the job directory where the integration is done.

•• A job number is set in each job. For job numbers, see Section 7.2
•• Points belonging to the same controller can be defined divided into multiple jobs. (If, for
example, AI03001 and AI03002 are to be configured in PRC:003, AI03001 and AI3002 can
be defined in different jobs.)
•• Parts with a duplicated tag name cannot be defined among jobs.
•• Logic parts and logic component parts having the same tag name need to be defined in the
same job.
•• Blocks at the same FB point need to be defined within the same job.
•• In all cases where a parameter is linked beyond a job, use Job Part parts (see Section 7.3).

Note By setting the following registry key, you can alter job directory writing operations
to the hdse_w.ini file and the udpman.ini file.
Registry:
(64bit OS [R412])
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Yamatake\SourceManagement
(32bit OS)
HKEY_LOCAL_MACHINE\SOFTWARE\Yamatake\SourceManagement
Key:
RtcDontUpdateJobDirectory

Writing to hdse_w.ini file and

RtcDontUpdateJobDirectory Value
udpman.ini file
0 Writing to job directory is performed
1 Writing to job directory is not performed

The job directory writing operations altered by this setting are the creation of
system data files, the loading of controller data files, and the integration of system
data files.
− 305 −
Chapter 7. Multiengineering

(2) Import/Export of System Definition

To make system definitions used among jobs, an import/export function for system defini-
tions (import/export function of node definitions, and an import/export function of unit
definitions) are provided. For details, see Section 6.1.4.1 and Section 6.1.4.2. Cases where the
contents of system definitions are found to be inconsistent among jobs are to be checked as
an error when system data files are integrated.

(3) Point Generation, and System Data File Creation

Points are generated in jobs, and system data files are created. Engineering operations leading
up to this can be individually performed in a standalone PC.

(4) Integration of System Data Files

•• The completion of processes Step (1) to Step (3) in jobs is an essential condition for the inte-
gration of system data files. The job (master job) for executing the integration of system data
files and jobs subject to multiengineering need to be referred to, connected in a network.
•• The “integration of system data files” starts from the RTC editor. The example in the figure
shows the “integration of system data files” from the master job “C”. Selecting a menu where
RTC exists will display the “Merge System Data Files” dialog. In this dialog, select a job
subject to multiengineering. In the figure, jobs “A”, “B”, and “C” are selected.
•• If the process is done, inconsistency is checked for among jobs by referring to system data
files of jobs selected in the [Merge System Data Files]. If the check is OK, the integrated data
files are created.
•• The files are to be output to the “it” directory of the job where “Integrate System Data Files”
has been done. If the job is specified as a job subject to integration, CSV files of the “it” di-
rectory of the job are to be overwritten by the integrated files. In such a case, the \it\original
directory is generated before the output of the integrated files, and the CSV file is backed up
in this directory before the integration.
•• The path to the output destination of the integrated files (exactly speaking, the path of the
job directory of an executed job) is written into the “JobDirectory” entry of the hdse_w.ini
file and udpman.ini file.

− 306 −
 7.1 Operation Procedure

Note By setting the following registry key, you can alter job directory writing operations
to the hdse_w.ini file and the udpman.ini file.
Registry:
(64bit OS [R412])
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Yamatake\SourceManagement
(32bit OS)
HKEY_LOCAL_MACHINE\SOFTWARE\Yamatake\SourceManagement
Key:
RtcDontUpdateJobDirectory

Writing to hdse_w.ini file and

RtcDontUpdateJobDirectory Value
udpman.ini file
0 Writing to job directory is performed
1 Writing to job directory is not performed

The job directory writing operations altered by this setting are the creation of
system data files, the loading of controller data files, and the integration of system
data files.

Note If there is a job of RTC_FB, please copy fbdb.csv file output by RTC_FB to “it” direc-
tory where RTC Editor output the integrated files.

(5) Creating Controller Date Files

Create controller data files of jobs after the integration of system data files becomes acceptable.
If a controller data file is created in a state where the integration of system data files is not ac-
ceptable, inconsistent data among jobs may be loaded to the controller.

(6) Loading Controller Data Files

Controller data files are loaded from jobs. Controller data files of jobs created in Step (5) are
to be loaded.

(7) Upload
The uploading process is performed in jobs. The uploading process is carried out only for a job
executed. (Even if parts of the controller to upload files are defined in other parts, the upload-
ing process is conducted only for the job.)

− 307 −
Chapter 7. Multiengineering

7.2 Job Number

“Job Numbers” are provided to identify multiple jobs.

•• A unique job number is set for each RTC job.

•• Make the job hierarchy diagram active, select [Job] and execute the [Job Info...] command
to display the [Job Information] dialog where you can set job numbers.

•• Job numbers, with a range of “1” to “99”, are set to “1” by default.

7.3 Job Part

Job Part are provided to make connections between control parts beyond jobs. As shown
in below figure, Job Part are used to make connections between control parts beyond jobs.
Setting job information, Job Part information and control parts information of the remote side
in connection on a property sheet of Job Part defines a connection between Job Part.
Job #2
Job #1

: Job Parts (In/Out)

Job #3 : Control parts
: Link

Figure 7-2.

Two types of parts are prepared for Job Part: one for inputs and the other for output. An Job
Part for input has an output port, while an Job Part for output has an input port. The maxi-
mum number of Job Part that can be defined in a job is 9999 each for input and for output. For
management, the RTC assigns an “Job Part ID” to each of the inputs and outputs to identify
Job Part.
As shown in below figure, Job Part adopt a display format of an elliptical shape enclosed by
double lines.

08-0034

Figure 7-3.

− 308 −
 7.3 Job Part

Following Table shows formats of character strings displayed on parts and the display colors.

Table 7-1.

Data on the remote Displayed character string

Input/out- Display color
side is displayed/not
put type Format Description of parts
displayed on parts
ID : fixed character
For input ID : nnnn Red
nnnn : self Job Part ID
When not set
jj : self job No.
For output jj - nnnn Blue
nnnn : self Job Part ID
jj : job No. of remote side
For input jj - nnnn
nnnn : Job Part ID of remote side
When set Green
jj : self job No.
For output jj - nnnn
nnnn : self Job Part ID

Note If a job number is changed in mid flow, the “jj” portion of the Job Part for output (see
above table) is also automatically changed.

7.3.1 Methods of Defining the Remote Side of the Connection

There are two methods of defining a destination to connect an Job Part: one using a property
sheet of Job Part and the other using the [Job Part List] window. This section describes the
method using a property sheet of Job Part. The method using the [Job Part List] window is
provided to reset data that has been set once. For this function, see Section 7.3.3.
The procedure for defining a destination to connect an Job Part are shown below.

Step 1 Double-click the Job Part to display a property sheet.

You can display or set Job Part parameters from this dialog.

Step 2 An “ID” and descriptor of the Job Part are displayed on the [Set] page. Up to 40
characters can be set for a descriptor.

Step 3 Information on the remote side of the connection is displayed in the [Counter
Parameter List:] list box.

− 309 −
Chapter 7. Multiengineering

Step 4 Pressing the <Read File...> button displays the [Counter Job Part List] dialog. As
shown in below figure, this dialog reads the data files (jobin.csv and jobout.csv) of
an Job Part output to jobs, displays the Job Part information in a list, and provides a
mechanism of setting the data of an Job Part selected from the list in the parameters
of its parts. For outputs of the jobin.csv and jobout.csv files, see Section 7.3.3.
Job Parts Summary jobin.csv Parameter Set Dialog
xxxx jobout.csv xxxx
xxxx Output Read xxxx Job#2
Job#1 xxxx xxxx

Parameter Set Dialog jobin.csv Job Parts Summary

xxxx jobout.csv xxxx
xxxx xxxx
xxxx Read Output xxxx

Figure 7-4.

Step4.1 Click the <Add...> button to display the directory selection dialog. In
this dialog, select a job directory of a job that can be the remote side,
and the directory will be added to the [Counter Job Directory List:] list
box. However, your job directory can not be added.

Step4.2 Select a job directory in the [Counter Job Directory List:] and click the
<Delete> button to delete the selected directory from the list box.

Step4.3 Selecting the job directory in the [Counter Job Directory List:] searches
jobin.csv and jobout.csv directly under the selected directory, and the
contents will appear in the [Counter Job Part List:]. However, if your
parts are for input, only jobout.csv is referred to. If your parts are for
output, only jobin.csv is referred to.

Step4.4 Click the <Set> button to set information on the selected remote side
Job Part in the parameters of your Job Part.

Step 5 Click the <Set Parameter ...> button to display the [Set Parameter] dialog. You can
change individual parameter values in this dialog.

Note •• At a state where points are generated, the system definition needs to define
nodes and FB points set in the remote side parameters of Job Parts within the
jobs.
•• If the remote side is a algorithm part of the logic component parts, a block num-
ber within the logic point will be set in the “Block Number/Index” parameter of
Job Parts. If the block numbers of the remote side logic component parts have
not yet been decided, generate a point to determine the block numbers, and then
define the Job Part connections again.
•• Similarly, a block number is set in the “Block Number/Index” parameter of Job
Parts if the remote side is a block part. If the block number of the block part at
the remote side has not yet been decided or has been changed by the automatic
computing order determination, generate points to determine the block number,
and then define the connection of the Job Part again.

− 310 −
 7.3 Job Part

7.3.2 Rules for Connecting Job Part

■
■Rules for Connecting Job Part between Different Jobs
•• One-to-one connection is allowed only between Job Part. That is, two or more remote Job
Parts cannot be defined in an Job Part. To connect multiple control parts from a control part
by using a Job Part, place as many Job Part as there are connections from a control part, and
then connect the control parts individually.

■
■Rules for Connecting Job Parts and Other Parts within the Same Job
•• The number of connectable links to input/output ports of Job Part shall be “1”. Two or more
links from an Job Part cannot be connected.
•• Job Part are not connected to each other.
•• Only the following control parts can be connected to Job Part.
– Point parts (AI, AO, DI, DO, VALIN, VALOUT, DC, RP, RC, FL, NM, NAR [R411 or
later], STR [R411 or later], DT [R411 or later], TM, PM and FF. However, since LG does
not have ports, it is not connectable to an Job Part.)
– Logic component parts (algorithm, NN, FL, CONNECTION, GW)
– Block parts
– Reference parts
•• If an Job Part is connected to a control part, and they are put in the following states, the con-
nection is checked. If the check detects a problem, the connection is not allowed.
– If a control part is linked in a state where the control part information of the remote side
has already been defined for an Job Part, the connection is checked.
– If an Job Part has already been connected to a control part, and parameters of the remote
side have been changed on the property sheet of the Job Part, the connection is checked.
If a problem is found in the check, the connected link is disconnected.

Note If fanout connections are made via Job Part (CODSTN(n) and DODSTN(n) parameters
are used to make multiple output connections), the maximum value for the number
of output connections with link connected cannot be checked in some cases.
To make fanout connections via Job Part, reconfirm the values of output connection
parameters (CODSTN(n) and DODSTN(n)) of the parts connected to the Job Part.

7.3.3 Job Part List

■
■Displaying a List of Job Parts

Step 1 Select [Browser] and execute the [Job Part List ...] command to display the [Job Part
List] window.

Step 2 In the [In/Out Type] pulldown list, select a display type (for input, for output, and
all).

− 311 −
Chapter 7. Multiengineering

Step 3 The following values for defined Job Part are displayed in the [Job Part List:] list.
•• Input/output type (IN/OUT)
•• Job Part ID
•• Descriptor
•• Name of sheet where a part exist

Step 4 Select the list item (header) to display selected columns in a sorted state. Initially,
they are displayed sorted in the order of input/output type and Job Part ID.

Step 5 Select an item in [Job Parts List:] and click the <Open Sheet...> button to open a
sheet in a state where the relevant Job Part are selected. The same processing is done
if you double-click the listed item.

■
■Output of Connection Destination Parts Information of Job Part

Step 1 Click the <Output> button to generate the following files (whose file name is fixed)
directly under the job directory. Both files will be output disregarding the selection
state of the [In/Out Type] pulldown list.
•• jobin.csv : data on Job Part for input
•• jobout.csv : data on Job Part for output

Step 2 The above files will be referred to when data of the remote side is set on the property
sheet of Job Part parts or in the rereading process shown below.

■
■Rereading Job Part Parameter

Step 1 A function is provided to “reread”, at a time, the parameters of multiple Job Part
that have already been connected to the remote side.

Step 2 Select Job Part to be reread from the [Job Part List:] and click the <Read
Parameter...> button.

Step 3 The [Read Job Parts Parameter] dialog appears. In this dialog, select a directory to
be reread at the remote side. Click the <Add...> button to display the file dialog,
and then select a job directory to be reread. Click the <Delete> button to delete the
jobs selected in the [Job Directory List] list box. The files to be reread are the jobin.
csv file and jobout.csv file under the directory added to the [Job Directory List] list
box.

Step 4 Click the <Execute> button to start rereading the files. If the contents of the jobin.
csv file and jobout.csv file under the job directory selected in Step3 are reread,
and the contents found are met with respect to the “Remote Side Job Number” and
“Remote Side Job Part Number” that have already been set in the Job Part selected
in Step2 (i.e., the definition at the remote side is found), the contents will be reread
(set overwritten) into the parameters of the Job Part.

− 312 −
 7.4 Integration of System Data Files

7.4 Integration of System Data Files

System data files generated in jobs need to be finally integrated into a system data file. Hdse.
exe needs to be activated by reading the integrated system data file. The integrating function
of the system data file is provided as a function for performing this integration.
The integration of the system data file is a function that creates a system data file by integrating
system data files output in jobs.

Job A Job B Job C Job D (Master)

Create System Create System Create System Combined

Data File Data File Data File System Data File
System Data File System Data File System Data File System data file was Combined

Figure 7-5.

Usually execute [Merge System Data Files] from the RTC editor, the master editor, and an
integrated file will be output to under the “it” directory of the executed job. Starting the inte-
gration of system data files assumes that the following processes have been completed in jobs.

•• Points have been completely generated.

•• System data files have been completely created.

■
■Operation Procedure

Step 1 Select [Merge System Data Files] from the [Implementation] menu.

Step 2 The [Merge System Data Files] dialog will appear.

Step 3 Select the <Add...> button to set a job directory to be integrated from the [Select
Directory] dialog. The pass for the job directory to be integrated is displayed in the
[Directory List:]. At this point, you can also add your job directories as those to be
integrated.

Step 4 Select the <Delete> button to delete the path selected in the [Directory List:] list
from the list.

Step 5 Click the <Execute> button to start the process for integrating system data files.

Step 6 Starting the process for integrating system data files checks, at first, whether or not
the files can be integrated. The check results will appear in the [Status:] list box.

− 313 −
Chapter 7. Multiengineering

Step 7 If no problems are found in the check, an integrated system data file will be output
to the “it” directory of your job. At this point, if your jobs are also included in the
files to be integrated, the files, before being integrated, that existed in the “it” direc-
tory before the output of files to the “it” directory, are backed up in the \it\original
directory.

Note If your jobs are also included in files to be integrated, subsequent execution of a sys-
tem data file may become a file to be integrated next, because the system data file
previously integrated still remains in your “it” directory. In this case, it is therefore
necessary to make the system data file in your “it” directory a backed up file or to
integrate the file after you have created a system data file again.
For the reason above, if the master job is placed as a job for integrating other jobs
and is not made subject to integration, you can perform operations without being
sensitive about the contents above.

Note The time stamp of the header of an integrated file takes the date and time when all
system data files are completely integrated. For the db.csv file, however, the date
and time of integration completion will be rewritten by the date and time of the
time stamp output line instead of the header.

Note For the Harmonas-DEO system, the history.csv file (history setting) output to the “it”
directory is not a file to be integrated.

Note If you move the master job or jobs to be integrated to another directory after hav-
ing integrated system data files, integrate the system data files again. If they are not
reintegrated, information related to the job directory is not updated and, therefore,
functions related to the multiengineering do not operate normally.

− 314 −
 7.5 Job Information List

7.5 Job Information List

Information on multiple jobs integrated by [Merge System Data Files] can be displayed listed
in the [Job Info List] dialog.

■
■How to Display a Job Information List
Make the job hierarchy diagram active.
Select the [Browser] menu, and execute the [Job Info List] command to open the [Job Info
List] dialog.

Note •• Before displaying the [Job Info List] dialog, you must execute [Create System Data
File] or [Merge System Data Files].
•• If information on a sheet is changed, the changes are not reflected to the [Job Info
List] dialog until you have executed [Create System Data File].
•• Changes are not reflected to integrated configuration information files (described
later) until you have re-executed [Merge System Data Files].

■
■Contents of Job Information List Displayed

Table 7-2.

Type of list displayed Displayed item

JOBNUM (indicates the job currently being edited)
Job List JOB NAME
JOB PATH
NAME
JOB NUM
Point List PNTTYPE
NODE NAME
SHEET NAME

Note •• In the job list, the job number of the job currently being opened by the RTC editor
is marked with “(Editing)”.
•• A point name indicates the tag name of a point (including FB point) and the block
name of a block.
•• For FB points, a sheet name is always marked with “—” (because there are no parts
equivalent to FB points).

− 315 −
Chapter 7. Multiengineering

■
■Sorting Displayed Items in Point Names List (Sort)
In a point name list, click the header portion of the list to sort the list by using the item as a
key. Click the same head again to sort the items in reverse.

■
■Changing the Column Width of the Point Name List
In the point name list, dragging the boundary between the list header and the header can
adjust the width of a column. Double-clicking a boundary can adjust the width of the column
according to the maximum width of column data.

■
■Narrowing Down (Filtering) Displayed Point Name List
In the point name list, setting a job number, point type and node name as a display condition
can narrow down the display contents. Select the display condition for each comb box and
click the <Update> button to update the displayed point name list.

■
■Output of Displayed Data in Job Information List
Displayed data in the [Job Info List] dialog can be output in the CSV format as it is. Output
files can be read into spreadsheet software such as Microsoft Excel.
To save displayed data, click the <Output> button in the [Job Info List] dialog. This will display
the [Output System Data File Data] dialog. Since the data is to be saved with extension .csv
directly under the job directory by default, give a file name to it. Of course, the data can be
saved with any extension in any directory.

■
■Input Destination of Job Information List Data
The [Job Info List] dialog loads data recorded in the configuration information file (cnfinf.
dat) in the “it” directory, a job directory. The dialog also displays information. This file is cre-
ated when you execute [Create System Data File] or [Merge System Data File]. The state of job
integration shows what configuration is to be loaded. For details, see the table below.

Table 7-3.

Configuration information file existing

State
in the self job directory
Configuration information file existing in
Single engineering
the self job directory
Multiengineering Integrated configuration information file
Though it is multiengineering, [Merge System Data Files] Configuration information file existing in
has not yet been executed. the self job directory
Though it is multiengineering, the self job is not included Configuration information file existing in
in the integrated configuration information file. the self job directory

− 316 −
 8.1 Reusable Parts Scenario

Chapter 8. Reusing Parts

■
■Terms
A unit produced by combining various parts using RTC Editor and given a defined function
is called a reusable part.

Reusable parts are stored in the “hasNASBe” directory.

Physically, this is the directory that is specified as a repository.

One PC can have one hasNASBe directory.

Restriction Reusable parts consist of RTC parts. Reusable parts registration can be executed
from a Job Window or a Sheet. Some operations, such as category definition, can
only be executed from a Job Window. Note that neither intersheet parts or intra-
sheet parts contained in a container nor parts with invisible point links, can be
registered as reusable parts.

8.1 Reusable Parts Scenario

■
■Scenario of local reuse
Job staff can search reusable parts from a previously-created job in a job or currently being
produced.

This can be implemented using parts copy/paste function of RTC Editor.

•• Reuse in the same job

Put a reusable container in the job repository and copy to any Sheet.

•• Reuse between different jobs

If the jobs are stored in the same PC or in PCs connected on a network, open both the source
job and the destination job from the RTC Editor and copy and paste the necessary parts.
If jobs are stored in PCs not connected on a network, temporarily define a job with the parts
to be reused and copy it via a removable media.

− 317 −
Chapter 8. Reusing Parts

■
■Scenario of reuse within an organization
In some cases, reusable parts are managed and reused within an organization to achieve a
greater benefit. The hasNASBe Browser is an optional package that provides a method for
promoting organizational reuse of parts.

A hasNASBe directory can be shared by many units within an organization by many units
and staff should be appointed to manage the shared hasNASBe directory and promote reuse
of parts.

Reusable parts can be reused by the following procedure:

•• Select parts from each job and register them for reuse in the hasNASBe directory defined
for each PC.

•• The hasNASBe administrator collects reusable parts from the hasNASBe directories of
different PCs, processes them as necessary, and registers them in the shared hasNASBe
directory.

•• Other Job developers search for reusable parts in the hasNASBe directories of PCs or
from the shared hasNASBe directory, using a hasNASBe Browser. They can be copied
to a job.
Provider 1
hasNASBe
Provision
directory on PC 1

Provider n Reuser 1
hasNASBe
Provision Copy
directory on PC n

hasNASBe
Administrator Regist-
ration

Shared hasNASBe

Figure 8-1.

− 318 −
 8.2 preparation for Using hasNASBe Browser

8.2 preparation for Using hasNASBe Browser

To use the hasNASBe browser, C:\REPOSIT\ needs to be created as a hasNASBe directory.

8.3 hasNASBe Directory Management

8.3.1 Defining a Category

An appropriate category must be assigned each reusable part to facilitate searching.
When registering reusable parts using RTC Editor, select at least one appropriate category
from the predefined categories.

A hasNASBe administrator has the privilege to change category definitions. Note that a new
category is effective only in this hasNASBe directory and only for reusable parts registered
under this category.

■
■Calling the [Edit Category] dialogue

Step 1 Execute the [hasNASBe] → [Edit Category] command of RTC Editor. The [Edit
Category] will be called.
At this point, the previously edited category file in the hasNASBe directory will be
open.

Note When executing for the first time, the category file does not exist. Create
a category file using defining a category, “Saving a category” described
below.

Step 2 To edit a different category file, click the <Open> button to display the file dialog
box.

Step 3 Select a hasNASBe directory from the file dialog box and click on the category.
rcd file. The path name of the category file that was opened will be displayed in
[Category File].

Step 4 To define a new category, click the <New> button. The list box on the window is
cleared.

− 319 −
Chapter 8. Reusing Parts

■
■Defining a category

Step 1 Set a category in the [New Category] box in the [Edit Category] dialog box.

Step 2 Click the <Add> button. The category that was defined in the [New Category]
box will be added to the [Master Category] list box. Categories are always listed in
chronological sequence in the [Master Category] list box.

Step 3 Any attempt to add a category that has already been registered is ignored.
The same entry is never duplicated in the [Master Category] list box.

Note The following character cannot be used at the beginning of the Category
Name.
•• exclamation mark “!”

■
■Deleting a category

Step 1 Select the entry to delete from the [Master Category] list box and click the <Delete>
button. The entry will be moved to the [Deleted Category] list box.

Step 2 The <Move Back> button is effective when at least one entry is in the [Deleted
Category] list box. Select an entry from the [Deleted Category] list box and click
the <Move Back> button. The entry will be moved to the end of the [Master
Category] list box.

■
■Saving a category
Click the <Save> button to save an edited category in the category file. If a new category file
has been created, the file dialog box is displayed. Select the hasNASBe directory that uses this
category file.

− 320 −
 8.3 hasNASBe Directory Management

8.3.2 Collecting Reusable Parts

A hasNASBe administrator collects reusable parts from hasNASBe directories that are used
locally by end users and stores them in the shared hasNASBe directory.

■
■Constructing a shared hasNASBe database and registering reusable parts
The hasNASBe administrator collects reusable parts from users’ (reusable parts providers’)
local hasNASBe directories and constructs a shared hasNASBe database by the following
procedure:

Step 1 Define a directory with any path name for use as shared hasNASBe (hereafter
referred to as shared hasNASBe directory). Copy a category file from another has-
NASBe directory or create a new category file, as necessary.

Step 2 Using the Explorer, copy the reusable parts to be shared from each local hasNASBe
directory to the shared hasNASBe directory. Repeat this procedure to add all reus-
able parts to the shared hasNASBe directory.

■
■Deleting reusable parts from the shared hasNASBe directory
Delete a reusable parts directory under the hasNASBe directory using the Explorer.

− 321 −
Chapter 8. Reusing Parts

8.4 Registering Reusable Parts under hasNASBe

Using RTC Editor, assign a category to a container and register parts under hasNASBe.

8.4.1 Assigning a Category to a Container

In some cases, reusable parts consist of multiple reusable containers.
You can register these containers as reusable parts, but this will increase the number of reus-
able parts and make searching more difficult.

If reuse is anticipated for a container included in reusable parts, it can be searched by the
category search function of hasNASBe Browser simply by assigning a category to it (without
inordinately increasing the number of reusable parts).

For example, if a reusable container is called “Bottom of Furnace Temperature Control”

contained in “Furnace”, assign a category to the “Bottom of Furnace Temperature Control”
container. Such containers need not be registered as individual reusable parts.

■
■Procedure for assigning a category
Select one container from a RTC Editor Job Window. The [Assign Category] dialog can be
opened by either of the following methods:

Step 1 Select by right-clicking on the [Assign Category...] command from the pop-up
menu displayed.

Step 2 Execute [hasNASBe] → [Assign Category...] command from the menu.

A category will be assigned to the container selected from the [Assign Category]
dialog.

Note A hasNASBe administrator has the privilege to maintain and change

categories using the category editing function. The category editing
function will be explained later.

− 322 −
 8.4 Registering Reusable Parts under hasNASBe

■
■[Assign Category] dialog box
Predefined categories are displayed in the [Selectable] list box.
Select an appropriate category from the [Selectable] list box and click the <Select> button to
move this category to the [Selected Category] list box.

For the opposite operation, select a category from the [Selected Category] list box and click
the <Deselect> button. The category will be moved to the [Selectable] list box. Multiple cat-
egories can be assigned to a container using this method.

A category that is assigned by the category assignment operation is effective only for to the
selected container and has no influence on containers placed above or beneath this container.

A category that is assigned to a container can be reconfirmed or redefined by opening the

[Assign Category] dialog box again from the Job Window.

Note Use the same category definition file for all PCs, otherwise you may not be able to
search a container by its category.

Restriction Once registered under hasNASBe, reusable parts may not be edited or changed,
including their category assignment. To change the details of reusable parts, copy
once to RTC Editor, edit and register it again.

8.4.2 Registering Reusable Parts under hasNASBe

Select a reusable container from a Job Window or select parts from a Sheet window and reg-
ister under hasNASBe Browser. When a link is connected to the container, the port remains
on the container, but the link is cut.

■
■Procedure for registering under hasNASBe
The [Register...] dialog box can be opened by one of the following procedures:

Step Select a container from a Job Window, execute the [Register] command by select-
ing it from the pop-up menu (displayed by right-clicking).

Step Select a container from the Job Window and execute [hasNASBe] → [Register (R)]
command from the menu.

Step Select parts from a Sheet window and execute [hasNASBe] → [Register (R)] com-
mand from the menu.

Using the [Register] dialog box, enter the items requiring registration and select
<OK>. The selected parts will be registered as reusable parts under hasNASBe.

− 323 −
Chapter 8. Reusing Parts

■
■[Register] dialog
•• Reusable parts name
Assign a name to reusable parts and input it.
A reusable parts name must be a character string that can be used as a file name because a
sub-directory with this name will be created under the hasNASBe directory.

•• Selecting a category
Predefined categories are displayed in the [Selectable] list box.
Select an appropriate category from the [Selectable] list box and click the <Select> button
to move this category to the [Selected Category] list box.
For the opposite operation, select a category from the [Selected Category] list box and click
the <Deselect> button. The category will be moved to the [Selectable] list box. A number of
categories can be assigned to a container by this method. Select at least one category.

•• Attributes of reusable parts

Reusable parts have the following attributes:
When reusable parts are selected using hasNASBe Browser, their attributes are displayed
on the screen:
- Description : Enter such information as parts handling methods and restrictions in no
more than 300 characters.
- Revision : Parts revision number consists of a character string in any format.
- Date : Enter the date of parts registration (default value is the date of registration
operation).
- Model No. : If an ID is assigned to reusable parts, enter in this field.

Note The overwrite registration of parts is not allowed. When parts are changed, register
the parts with different names, or delete the old parts and re-register the new ones
on the Explorer.

− 324 −
 8.5 Reusable Parts

8.5 Reusable Parts

Search for reusable parts using hasNASBe Browser and past in a Sheet.
The present explanation focuses on hasNASBe Browser and capsule parts function.

■
■Vertical Browse and Horizontal Browse
Reuse can be further promoted by browsing of the elements of a reusable part (e.g., “bed tem-
perature control” is an element of “incinerator”).

The hasNASBe Browser allows assignment of categories to both reusable parts and their ele-
ments, and searching by both types of item. Any container contained in a reusable part can
be copied.

The following table shows the relationship between reusable parts and these categories, with
focus placed on elements (individual containers).

Table 8-1. Relationship between reusable parts and categories

Category/Reusable
Reusable parts A Reusable parts B Reusable parts C ...
parts name
Category A Element a Element b
Category B Element c Element d
Category C Element e Element f
Category D Element g

Elements can be searched by the following two methods:

•• Vertical direction: Select reusable parts and search their components using a hierarchi-
cal diagram.
•• Horizontal direction: Select a category and search the related elements.

The former and the latter function of hasNASBe Browser are called Vertical Browse and
Horizontal Browse, respectively.

− 325 −
Chapter 8. Reusing Parts

■
■Searching reusable parts
Using hasNASBe Browser, reusable parts can be searched by the following procedures:

Step 1 Starting hasNASBe Browser.

The local hasNASBe directory of the PC is opened as the default value.
The hasNASBe of another PC connected via a network can also be opened.

Step 2 Searching reusable parts or a container.

Execute the reusable parts list display function to search reusable parts.
Execute the category search function to search containers contained in reusable
parts. The search result is listed in the horizontal browse window.

Step 3 Copying reusable parts or a container

If the necessary reusable parts or the container is found in this stage, copy it from
the horizontal browse window to the clipboard.
Details of reusable parts can be confirmed by calling the vertical browse window
or the content window.
A container displayed on the vertical browse window can also be copied to the
clipboard.

Step 4 Paste the reusable parts or container in to a job.

Open a Sheet and paste the reusable parts using the [Edit] → [Paste] command.

− 326 −
 8.5 Reusable Parts

8.5.1 Starting hasNASBe Browser

The hasNASBe Browser and RTC Editor are separate, executable files.
The hasNASBe Browser can be started by any of the following procedures:

Step Select and execute rtcbrows.exe from the Explorer.

Step Select menu [hasNASBe] → [Run hasNASBe] command from the Job Structure
Window of RTC Editor.

hasNASBe Browser has the child windows. When hasNASBe Browser is started up for the
first time, only the Search Condition window is displayed. Other child windows are displayed,
as necessary.

Figure 8-2.

■
■hasNASBe Browser windows
The following windows are displayed by starting up hasNASBe Browser:

Table 8-2. hasNASBe Browser

Window Function
Search window This window is used for selecting and setting search conditions
Horizontal Browse The result of the search is displayed in this window
Vertical Browse The hierarchy of reusable parts is displayed in this window
A view of registered reusable parts on a Sheet is displayed in this
Content window
window

− 327 −
Chapter 8. Reusing Parts

■
■Display at hasNASBe Browser startup
One hasNASBe Browser Window is opened each time hasNASBe Browser is started up.
“hasNASBe Browser-Display Window Name” is displayed in the caption bar of hasNASBe
Browser.

The above four types of child windows are arrayed on the hasNASBe Browser Window.

If hasNASBe Browser is terminated in the maximized or icon state of, the window will be
displayed in the same size and position when hasNASBe is started up again.

If a part of the hasNASBe Browser Window is outside the screen at the time of exiting from
the hasNASBe Browser, the window is displayed at the same size an position when it is started
up again.

■
■Tool bar
The hasNASBe Browser has a standard tool bar.

Table 8-3. Standard tool bar

Tool bar Function

The standard bar has tool buttons for basic operations such as
Standard
printing and opening a window

The tool bar is not displayed as the default value. Display or Hide can be selected by execut-
ing [View] → [Standard Tool Bar] command. If the hasNASBe Browser is terminated in the
Hide state, this state is selected when next started up. When Display is selected, a checkmark
is shown at the menu item.

The function of a tool button can also be selected by menu operation.

When the function represented by a tool button is not permitted, the tool button is displayed
in a light color (like a menu display).
The default display position of the standard tool bar is the top of the hasNASBe Browser
Window. The tool bar can be dragged to the floating state or docked to the top, bottom, left or
right edges of the hasNASBe Browser Window. The floating state pertains when the hasNASBe
Browser is started up again, but docked state may not pertain.

If the desktop area is changed using the [Display] dialog box on the control panel, before start-
ing hasNASBe Browser, the floating tool bar will be displayed within the new desktop area
even if it cannot be displayed in side.

− 328 −
 8.5 Reusable Parts

•• Standard tool bar display

When the mouse is placed on a button on the standard tool bar, the following information
is displayed near the mouse pointer and the status bar:

Table 8-4. Standard tool bar display

Display Status bar message

Print Print an active Sheet
Zoom In Zoom in the window
Zoom Out Zoom out the window
Set Search Condition Set Search Condition
Horizontal Browse Display Horizontal Browser
Vertical Browse Display Vertical Browser
Content Display Content Window
Help Display Help for clicked on buttons or menu commands

•• Display of Status Bar by Operating Standard Tool Bar

If a operation is carried out on a sheet by clicking a button on the tool bar, a message appears
to assist the operation in the status bar.

Table 8-5. Display in Status Bar

Operation Display in Status Bar

Click the <Help> button Select a topic for Help

− 329 −
Chapter 8. Reusing Parts

8.5.2 Setting Search Conditions

Open the [Search Condition] window of hasNASBe Browser to search reusable parts.
The [Search Condition] window can be opened by selecting [Window] → [Search Window]
command from the menu.
When no reusable parts or containers satisfy the specified search conditions found, a message
indicates the absence.
The search results are displayed on the Horizontal Browse window.

■
■Parts list
Click the [Search All] check box and the <Search> button (in that order) to display a list of all
registered reusable parts.

■
■Searching by specifying categories
The list of reusable parts and containers satisfying the search conditions can be displayed by
the following procedure:

Step 1 Click the [Category Search] check box.

Containers (to which categories were assigned at the time of reusable parts registra-
tion) included in reusable parts can be searched in addition to reusable parts, by
checking the [Look in element] check box.

Step 2 Categories in the repository are displayed in the [Selectable] list box.
Select an appropriate category from the [Selectable] list box and click the <Select>
button to move this category to the [Selected Category] list box.
Select a category from the [Selected Category] list box and click the <Unselect>
button. The category will be moved to the [Selectable] list box.

Step 3 When a number of categories are selected, select AND or OR with the option but-
ton. Click [AND] to search the reusable parts or to search containers that have
all categories displayed in the [Selected Category] list box. Click [OR] to search
the reusable parts or containers that have any of the categories displayed in the
[Selected Category] list box. When only one category is displayed in the [Selected
Category] list box, the same result obtains regardless of whether [AND] or [OR] is
selected.

Step 4 Click the <Search> button to start the search.

Note Click the [Category Search] check box and select at least one category.
The <Search> button is not enabled until at least one category is selected.

Note Categories displayed in the [Selectable] list box are loaded from the category file
belonging to the currently-selected hasNASBe directory. Therefore, no category
that is assigned using a different category file is displayed in this list box. In such a
case, ask the hasNASBe administrator to add the necessary categories.

− 330 −
 8.5 Reusable Parts

Note The <Stop Search> button is effective only when a category search is done. In some
cases, the button may always look invalid even when there are a small number of
parts (since the button is made valid only for a moment).

8.5.3 Horizontal Browse function

Horizontal Browse displays reusable parts or containers that were searched by category
specified.

The [Horizontal Browse] window is displayed automatically at the end of searching.

It can also be displayed by selecting [Tool] → [Horizontal Browse] command from the menu.

■
■Displaying the search result
Searched reusable parts and elements (containers) are displayed in the [Part Name] list box
and the [Element Name] list box.

When [Search All] is selected as the search condition, none is displayed in the [Element
Name] list box. When [Look in element] is selected, sets of reusable parts names and element
(container) names are displayed as shown below:

Table 8-6.

Reusable parts name Container name

Reusable parts 1
Reusable parts 1 Container 1
Reusable parts 1 Container 2
Reusable parts 2

■
■Displaying description text
The Horizontal Browse window has a description text area on the right side of the splitter. A
description concerning the currently-selected reusable parts/element (containers) in the [Part
Name]/[Element Name] list box is displayed in this area.

The information input to the [Description] box in the [Register] dialog box is displayed.

For a container, the information input in to the [Description] box in the [Set Property] prop-
erty sheet of the container is displayed.

■
■Displaying attribute information
The model number, revision number, and last updated date (identical to the date of reusable
parts registration) of the currently selected reusable part name in the [Part Name] list box, are
displayed in the status bar.

− 331 −
Chapter 8. Reusing Parts

■
■Operations in Horizontal Browse window
The following operations can be executed on the Horizontal Browse window:

•• Call the Vertical Browse function

Select a reusable parts name from the [Part Name] list box and execute [Tool] → [Vertical
Browse] command. Or, double-click a reusable parts name in the [Part Name] list box.

•• Copy reusable parts

Select reusable parts/element (container) from the [Part Name]/[Element Name] list box.
Copy the selected reusable parts/element by either of the following methods:
– Execute [Edit] → [Copy] command.
– Click the <Copy> button on the window.

•• Check the categories assigned to reusable parts or containers

Select reusable parts/container from the [Part Name]/[Element Name] list box and execute
[Window] → [Show Category...] command. The list of categories assigned to the selected
reusable parts/container will be displayed in the dialog box.

8.5.4 Vertical Browse function

Vertical Browse enables searching of a container by tracing the hierarchical structure of reus-
able parts and copying it. The Vertical Browse window and the Content window implement
this function.

■
■Operating procedure

Step Select a reusable parts/container from the [Part Name]/[Element Name] list box
and double-click it, to display the Vertical Browse window and the Content win-
dow for the selected reusable parts.

■
■Vertical Browse window
The Vertical Browse window displays a hierarchical diagram. This diagram is a sub-tree whose
top is the container that was registered as reusable parts in the Job Window. The Vertical
Browse window displays reusable parts in the same format as in the Job Window. “Vertical
Browse Window [Part:xxx]” is displayed on the caption bar to identify the currently-displayed
parts.

The container indicating the entire range of reusable parts is at the highest level of the hierar-
chy. It is followed by the container of the highest level (selected at the time of reusable parts
registration) and the container of the next level.
If container “A” is registered as reusable parts “a” at the time of registration in the repository,
container “a” is the at the highest level and container “A” is at the second level.

− 332 −
 8.5 Reusable Parts

The following operations can be executed on the Vertical Browse window:

•• Select display or hide hierarchy status

As for the Job Structure Window, the state of lower containers can be switched from the
display state the hide state and vice versa by double-clicking a container.
A “+” mark is displayed at the center of the a container’s icon when its lower container are
in the hide state.

•• Content display
As for the <Open Sheet> function of the Job Structure Window, this function displays the
sheet corresponding to the selected container on the Content Window.
Unlike RTC Editor, only one sheet can be opened at any one time.

•• Copying
Select any container from the Vertical Browse window and select the [Copy] command
from the pop-up menu displayed by right-clicking or by selecting [Edit] → [Copy] com-
mand, to copy the container to the clipboard.

■
■Content window
The Content window displays the content of reusable parts or a container in the same format
as a Sheet. The caption bar displays “Content Window [Part:xxx]” when reusable parts are
selected and “Content Window [Part:xxx (Container: yyy)]” when a container is selected to
identify the currently displayed parts or container.

When a reusable part name is selected, its view on the sheet is displayed on the Container
Window. When a container is selected, its content is displayed.
For example, if container “A” is registered as reusable parts “a” at the time of registration under
hasNASBe, container “A” is displayed as the container on the Content Window of reusable
parts “a”. When container “A” is selected, the sheet of container A is displayed on the Content
Window. No operation can be executed on the Content Window.

Note Even if a custom view is set for reusable parts, it is not displayed on the Content
Window of the reusable parts.

Since no configuration view setting is reflected in hasNASBe Browser, the default view of reus-
able parts is always displayed on the Content Window.

− 333 −
Chapter 8. Reusing Parts

8.5.5 Capsule Parts

By encapsulating multiple defined parts, a user need not be aware of their detailed such as
point parts parameters.
The following parts many be encapsulated:
•• Point parts (including logic component parts and CL parts)
•• Block parts
•• Container parts

Parts that cannot be encapsulated are Job Parts, Intersheet Parts, Intrasheet Parts, Reference
Parts, capsule parts, point parts that are other than logic component parts and CL parts and
for which no OK has been provided on the property sheet or which have not been applied on
the sheet yet, and parts which include above those parts in the sheet of a container hierarchy.

■
■Encapsulation
Parts can be encapsulated by the following procedure:

Step 1 Select from a Sheet the parts to encapsulate.

Step 2 Select [hasNASBe] → [Capsulate...] from the menu.

Step 3 The [Capsule Part] dialog box is displayed. Set the necessary data.

The following data can be set:

Logical Tag Name, Tag Name, Description, Part Type, Version

Allowable parameters for each point parts and alias name (An alias name is optional.)
Encapsulated parts are disappear from the Sheet. Capsule parts are displayed at the left top
of the rectangle containing the whole parts. Parameters registered as default values are tag
name (NAME) and slot number (SLOTNUM) only. Select parameters from the Parameter
Candidate list, as necessary.

Note In a case where branch parts are included in the parts selected during encapsula-
tion, the defect that several links are kept displayed may occur.

When a container is encapsulated, the sheet of the container is closed after being saved.
No corresponding container icon is displayed in the Job Window. The sheet contained in the
hierarchy of the encapsulated container can not be opened by selecting [File] → [Open] from
the menu or clicking <Open Sheet> button by selecting from a Logical Tag Name list.

When a container is encapsulated, parameters that are registered as allowable at the time of
encapsulation can be set for all point parts included in the container hierarchy. When a con-
tainer is encapsulated, the point parts included in the hierarchy and parameters are expressed
as:

− 334 −
 8.5 Reusable Parts

Container1\Container2\Container3\Point1.param
Container1 : Logical tag name of the encapsulated container parts
Container2 : Logical tag name of the container existing on the sheet of Container 1
Container3 : Logical tag name of the container existing on the sheet of Container 2
Point1 : Logical tag name of the point parts existing on the sheet of Container 3
param : Parameter name of point parts Point 1

The above expression is not used when an alias name is set. Such a case, the alias name ex-
presses the parameters of the point parts.

In other words, the user-defined alias name is displayed instead of the “Container1\
Container2\Container3\Point1.param” expression. An alias name must be unique among the
capsule parts. Any attempt to set an existing alias name results in an error message and the
alias name setting remains unchanged. No default alias name is set.

The following characters are prohibited in an alias name:

, @ # . : ; space \ %

Note A logical tagname that has the same name as an encapsulated Point Part cannot be
specified as a logical tagname for a Capsule Part. Set two different names.

Note Once the property sheet of a Capsule Part is displayed following the execution of en-
capsulation, the encapsulation itself cannot be canceled. To cancel encapsulation,
select the capsule parts and uncapsulate it. Upon execution of encapsulation, the
part encapsulated becomes invisible. Therefore, before executing encapsulation,
make sure that the part to be encapsulated is selected correctly.

Note When point parts newly created on a Sheet are to be encapsulated, no parameter
can be set from the capsule parts until <OK> is selected from the property dialog
box of the point parts. This is because newly created point parts on a Sheet have no
parameter. In this state, neither the point parts corresponding to the property sheet
of the capsule parts nor the allowable parameters are displayed.

Note For details about how to decide the block number at the time of point generation
for encapsulated block parts, refer to 6.1.5, “Point Generation.”

■
■Setting properties
The following properties can be set on the property dialog box of capsulate parts:
•• Set a Logical Tag Name and a Tag Name for capsule parts
•• Assign data to the allowable parameters of encapsulated parts
•• Set the process module data point tag name, import template CL file, export template CL
source, set replace list, create CL source files.

− 335 −
Chapter 8. Reusing Parts

■
■uncapsulation
Cancel encapsulation by the following procedure:

Step 1 Select capsule part from a Sheet.

Step 2 Select [hasNASBe] → [Uncapsulate] from the menu.

Step 3 The encapsulated parts will be displayed in the selected state on the Sheet.
•• Undo and Redo are in effective for encapsulation and uncapsulation.
•• The sheet is automatically saved by uncapsulation.
•• Capsulate parts support no configuration view.

When the encapsulation of a container is canceled, the corresponding container

icon will appear in the Job Structure Window.

− 336 −
 9.1 Function Description

Chapter 9. Log Function

This section describes the log output function in the RTC editor.

9.1 Function Description

•• The log is output to text files only and is not printed out.

•• Settings related to the log are made in the englp.ini file.

•• In the englp.ini file, setting the OutputLogFile value of the [RTCEDIT] section to “TRUE”
outputs the log contents to a log file. The output log file name is as follows:

yymmddRE.txt
yy : Low-order 2 digits of the Christian year
mm : Month
dd : Day
RE : Identifier indicating RTC Editor

•• The name of the directory that log files are output to is a path specified for LogFileDirectory
in the [LogFile] section of the englp.ini file. If the path has not yet been set or a specified
path is not found, the log contents are not output to log files.

•• The term for saving (unit: day, three significant digits) the log file can be set in
LogSaveTerm(day) of the [LogFile] section in the englp.ini file. If there are log files whose
term for saving has expired that are still existing in the log output directory, those log files
are automatically deleted. Log files not specified or set to zero are not deleted.

•• In cases where outputs cannot be performed for some reason or other, a file only for log
functions is generated, and the contents of the error and the contents of the log that was not
output are output to the file. The file is generated in the same directory where the log file of
the RTC editor is saved. The format of the file name is as follows.

yymmddEL.txt
yy : Low-order 2 digits of the Christian year
mm : Month
dd : Day
EL : Identifier indicating exclusive use of log function

− 337 −
Chapter 9. Log Function

9.2 Contents of Log

•• The format for one line of log is shown below. A line is output per event.
<Category> <Date> <Time> <Process ID> <Log type> <Detailed contents>
Date : yy/mm/dd(yy: low-order 2 digits of the Christian year, mm: month, dd: day)
Time : hh:mm:ss (hh: hour, mm: minute, ss: second)
Process ID : Process ID of RTC editor (displayed in hexadecimal)

•• Following Table shows the contents of the log output by the RTC editor.

Table 9-1. The contents of the log

Category Log type Detailed contents

RTC Editor Execute None
RTC Editor Terminate None
Job Create Job name, job directory
Add Node Node name
Change Node Number Node name (before change), node name (after change)
Delete Node Node name
Assign Node Node name, sheet name
Job Open Job name, job directory
Output unit, presence of parts position information op-
tion, presence of sheet hierarchy information option,
Write EB File
node name, point type, or FB tag name, and file path
name
Read EB File Presence of sheet unit option, file name
Generation unit (node name for node unit, slot No. for
Create Point Data FB point unit), and presence of option for determining
the computing order
Node name, data type, file name, BOX Variable option
Create IDB Files
OPR and PMDP Local Value option.
Create System Data None
Add Sheet Sheet name, sheet file name, master sheet name
Sheet (before change), sheet name (after change), sheet
Rename Sheet
file name, master sheet name
Move to Repository Sheet name, sheet file name
Delete Sheet Sheet name, sheet file name
Load Control data Node name, data type, load unit/point name/module No.
Node name, upload unit, PMDP Local Value option,
Execute Upload BOX Variable option and IOMCYCLE option [R411 or
later].
Delete Point data Node name, point type, module No., slot No., point name
Node name (Primary/Secondary), command type, status
Change Node Status
after change
•• Node name, point name, parameter name, parameter
value
Change PTEXEC •• Node name, point type, module No., slot No., tag
name, parameter name, parameter value (when status
is changed with point data deleted)

− 338 −
 9.2 Contents of Log

Category Log type Detailed contents

CLCompile File name
CL Load File name
Merge System Data None

OPR Export Parameter Output file path name

Sheet name, presence of an option for the selected sheet
Import Parameter or for those under the sheet, selection of overwriting op-
eration/newly creating operation, file path name
Output/Print Point Conf None
Import of node Node No., path name of import destination
OPR (CHG)
Replacement Tagname Tag name (before change), tag name (after change)
Model name [attributes that can be made reference
ERROR Point Link Error
parts], sheet ID, parameter, detailed contents

− 339 −
Chapter 9. Log Function

MEMO

− 340 −
 A.1 Case of SS/HS/GS/SSH/MS/HL

Appendix A. The setting parameter of the node

About setting parameters of each node.

A.1 Case of SS/HS/GS/SSH/MS/HL

A.1.1 [Network Conf1] Page

Table A-1.

Parameter Description Range of Value

NODENUM Define the node number Integers 1 to 126
NODETYP Define the node type SS/HS/BS/GS/SSH/MS/HL
Define the status descriptor that is displayed when a Digital
Composite Point is undergoing a status change (moving from one Character string having 8 charac-
MOVPVTXT
state to another) or i s at an intermediate point between two states. ters or less
In the case of MS or HL, it cannot be defined.
Define the status descriptor that is displayed when the status of a
Character string having 8 charac-
BADPVTXT Digital Composite Point is “Uncertain” or “Bad”
ters or less
In the case of MS or HL, it cannot be defined.

Note [R411 or later]

MS node and HL node are not supported in [R411 or later]. Therefore adding new
MS/HL node is not available.

A.1.2 [Network Conf2] Page

Table A-2.

Parameter Description Range of Value

NMSGTXT Define the number of messages. Integers 0 to 15
MSGTXT(0) It cannot be changed. ----
Define the contents of the user-defined message STSMSG(status Character string having 8 charac-
MSGTXT(1)-(15)
message). ters or less

* In the case of MS or HL, this page cannot be displayed.

− 341 −
Appendix A. The setting parameter of the node

A.1.3 [Network Conf3] Page

Table A-3.

Parameter Description Range of Value

Define the Logical Name of a node
Logical Name Logical Name is set automatically when you change node number or 40 character
node type
Define the IP address of a primary In addition, the fourth octet of the You cannot set “192.168.254.*”
Primary Ethernet A
IP address becomes same as node number and “192.168.255.*”
Primary Ethernet B Set automatically in the case of network redundancy ----
Secondary Ethernet A It cannot be changed ----
Secondary Ethernet B It cannot be changed ----
ON
Network Redundancy Set network redundancy
OFF
Node Redundancy It cannot be changed ----

A.1.4 CSV format for import/export

The CSV format for import / export is as follows.
A line beginning with ‘#’ is considered as a comment line and is not a target of the import
process.

Table A-4.

Line The CSV format for import/export Example

Header meaning Network Configuration (“Nwk”),,NodeNum,Nod
Network Conf eType,Moving PV Text,Bad PV Text,Logical Name,IP Address1,IP
Nwk,,1,SS,“MOVING”,“BAD”,
(In the case of Address2,IP Address3,IP Address4,NMSGTXT,MSGTXT(1),MSGT
“SS001”,192.168.0.1, 0.0.0.0,0.0.0.0,0.0.0.0,
SS/HS/BS/GS/ XT(2),MSGTXT(3),MSGTXT(4),MSGTXT(5),MSGTXT(6),MSGTX
0,“”,“”,“”,“”,“”,“”,“”,“”,“”,“” ,“”,“”,“”,“”,“”
SSH) T(7),MSGTXT(8),MSGTXT(9),MSGTXT(10),MSGTXT(11), MSGT
XT(12),MSGTXT(13),MSGTXT(14),MSGTXT(15)
Network Conf Header meaning Network Configuration
Nwk,,3,MS,“MS003”,
(In the case of (“Nwk”),,NodeNum,NodeType, Logical Name,IP Address1,IP
192.168.0.3, 0.0.0.0,0.0.0.0,0.0.0.0
MS/HL) Address2,IP Address3,IP Address4

− 342 −
 A.2 Case of PRC

A.2 Case of PRC

A.2.1 [Network Conf1] Page

Table A-5.

Parameter Description Range of Value

NODENUM Define the node number Integers 1 to 126
NODETYP Define the node type PRC
Define the status descriptor that is displayed when a Digital
Character string having 8 charac-
MOVPVTXT Composite Point is undergoing a status change (moving from one
ters or less
state to another) or i s at an intermediate point between two states
Define the status descriptor that is displayed when the status of a Character string having 8 charac-
BADPVTXT
Digital Composite Point is “Uncertain” or “Bad” ters or less

A.2.2 [Network Conf3] Page

Table A-6.

Parameter Description Range of Value

Define the Logical Name of a node
Logical Name Logical Name is set automatically when you change node number or Up to 40 character string
node type
Define the IP address of a primary
You cannot set “192.168.254.*”
Primary Ethernet A In addition, the fourth octet of the IP address becomes same as node
and “192.168.255.*”
number
Primary Ethernet B Set automatically in the case of network redundancy ----
Secondary Ethernet A Set automatically in the case of node redundancy ----
Set automatically in the case of network redundancy and node re-
Secondary Ethernet B ----
dundancy
ON
Network Redundancy Set network redundancy
OFF
ON
Node Redundancy Set node redundancy
OFF

− 343 −
Appendix A. The setting parameter of the node

A.2.3 [Node Conf1] Page

Table A-7.

Parameter Description Range of Value

NCTLSLOT Define the number of slots of an adjustment control point Integers 0 to 160
Integers 0 to NCTLSLOT.
NFASTCTL Define the number of fast scan slots of an adjustment control point
It is 40 at the maximum.
NPVSLOT Define the number of slots of an adjustment PV point Integers 0 to 80
Integers 0 to NPVSLOT.
NFASTPV Define the number of fast scan slots of an adjustment PV point
It is 40 at the maximum.
NLOGSLOT Define the number of slots of a logic point Integers 0 to 80
Integers 0 to NLOGSLOT.
NFASTLOG Define the number of fast scan slots of a logic point
It is 40 at the maximum.
NDCSLOT Define the number of slots of a digital composite point Integers 0 to 255
NFASTDC Define the number of fast scan slots of a digital composite point Integers 0 to NDCSLOT.
NPMSLOT Define the number of slots of a process module point Integers 0 to 160
NFASTPM It cannot be changed ----
NNUMERIC Define the number of slots of a numeric value variable point Integers 0 to 2047
NFBSLOT It cannot be changed ----

− 344 −
 A.2 Case of PRC

A.2.4 [Node Conf2] Page

Table A-8.

Parameter Description Range of Value

Define the statement capacity that can be processed at a process
module data point 1_PU
SEQPROC
“1_PU” : 10 statements can be processed in 1 pre-emption 2_PU
“2_PU” : 20 statements can be processed in 1 pre-emption
RSTRTTIM Define the start-up time for when the auto restart function is used Integers 0 to 30
NULL
REG1LOG1
REG1LOG2
SCANRATE Define the processing cycle at each data point REG1LOG4
REG2LOG2
REG2LOG4
REG4LOG4
NONREDUN
PKGOPT Define the hardware packaging option REDUN
NODEFALT
Define the I/O type
For X-Bus, refer to [X-bus Input/Output Equipment Hardware X-Bus:1Mbps
NEWIOUSE
Manual] (MS2-SYS100-3005) and refer to [FX-bus Input/Output FX-Bus:5Mbps
Equipment Hardware Manual] (MS2-SYS100-3004) for FX-Bus
125 ms
DOPLSPD Define the DO (Digital Output) resolution
25 ms
5 Sec
PIUOTDPD Define the LMUX disconnect detection time
3 Sec
Defines unacknowledged return-to-normal alarm on ACKSTAT.
DEO_HAS
ACKSTOPT DEO_HAS:Treat as no alarm
APS
APS:Treat as unacknowledged alarm
Specify initial value during DC point initialization.
INTRACK
DCTRACK INTRACK:Input value is initial value.
OUTTRACK
OUTTRACK:Output value is initial value.
SHPCLKMS It cannot be changed ----

A.2.5 [Unit Conf1-2] Page

Table A-9.

Parameter Description Range of Value

Choose a unit ID already set on the [Unit ID] page in the [System
BOXUNIT(1)-(40) Registered Unit ID
Definition] dialog box
ENABLE
ALENBST(1)-(40) Define the alarm enable status of a unit DISABLE
INHIBIT

− 345 −
Appendix A. The setting parameter of the node

A.2.6 [IOM Conf1-4] Page

Table A-10.

IOMRate
IOMType Module# FileA# CardA# FailOpt IOREDOPT FileB# CardB#
(*3)
NONREDUN
HLAI 1 - 40 1-8 1 - 12 ---- UNPOWER (*4) (*4)
REDUN
HMUX(*1) 1 - 40 1-8 1 - 12 ---- UNPOWER NONREDUN 0 0
LMUX(*1) 1 - 40 1-8 1 - 12 ---- UNPOWER NONREDUN 0 0
RMUX(*1) 1 - 40 1-8 1 - 12 ---- UNPOWER NONREDUN 0 0
TCAI(*2) 1 - 40 1-8 1 - 11 ---- UNPOWER NONREDUN 0 0
RTDAI(*2) 1 - 40 1-8 1 - 11 ---- UNPOWER NONREDUN 0 0
NONREDUN
PI 1 - 40 1-8 1 - 12 ---- UNPOWER (*4) (*4)
REDUN
UNPOWER NONREDUN
AO16 1 - 40 1-8 1 - 12 ---- (*4) (*4)
HOLD REDUN
DI 1 - 40 1-8 1 - 12 ---- UNPOWER NONREDUN 0 0
UNPOWER
DO 1 - 40 1-8 1 - 12 ---- NONREDUN 0 0
HOLD
UNPOWER
DO32 1 - 40 1-8 1 - 12 ---- NONREDUN 0 0
HOLD
STIM 1-8 1-8 1 - 12 ---- UNPOWER NONREDUN 0 0

*1 IOMType can set “HMUX”, “LMUX”, “RMUX” only in the case of NEWIOUSE = “X-Bus:1Mbps”.
When setting up “HMUX”, “LMUX” and “RMUX”, they require master “HLAI” that has same
File#, smaller Card# and smaller module number.
*2 IOMType can set “TCAI”, “RTDAI” only in the case of NEWIOUSE = “FX-Bus:5Mbps”.
*3 IOMRate cannot be set up.
*4 Set automatically in the case of IOREDOPT = “REDUN”. (FileB# = FileA#, CardB# = CardA#+1).
In order to set “REDUN” as IOREDOPT, CardA# needs to be odd.

Note When you use distributed I/O, the File numbers are equivalent to the block ad-
dresses of distributed I/O, and the Card numbers are equivalent to base addresses.
File numbers (1 to 8) : Dip switch BLK of block address (0 to 7)
Card numbers (1 to 12) : Dip switch BASE of base address (0 to 11)
For details about how to set the X-bus addresses of distributed I/O by dip switches
on the module base, refer to [Harmonas-DEO DEO Process Controller Installation
Manual](for distributed I/O Module)(MS2-DEO200-3003) or the [Harmonas-DEO
DEO Process Controller II Installation Manual](MS2-DEO200-3005).

Note To use high-level input of signal unit I/O, set the module type to “HLAI”. To use ana-
log output of signal unit I/O, set the module type to “AO16”.

Note Please select “HLAI” when using an analog input of SIO II.
Sensor type and range of temperature are configured on Signal Unit I/O-II(SIO II)
Communicator when using SIO II TC input units(HD-STCU50C) or SIO II RTD input
units(HD-SRTU50C).
Please set PVEUHI and PVEULO to same values which are set on SIO II Communicator.

− 346 −
 A.2 Case of PRC

A.2.7 CSV format for import/export

The CSV format for import/export is as follows. A line beginning with ‘#’ is considered as a
comment line and is not a target of the import process.

Table A-11.

Line The CSV format for import/export Example

Header meaning Network Configuration (“Nwk”),,NodeNum,Nod Nwk,,2,PRC,“MOVING”,“BAD”,“
Network Conf eType,Moving PV Text,Bad PV Text,Logical Name,IP Address1,IP PRC002”,192.168.0.2,0.0.0.0,
Address2,IP Address3,IP Address4 0.0.0.0,0.0.0.0
Header meaning Node
Configuration(“Node”),NodeNum,NCTLSLOT,NFASTCTL,NPVSL
OT,NFASTPV,NLOGSLOT,NFASTLOG,NDCSLOT,NFASTDC,SEQ
PROC,NPMSLOT,NNUMERIC,RSTRTTIM,SCANRATE,PKGOPT
,NEWIOUSE,DOPLSPD,PIUOTDPD,SHPCLKMS,ACKSTOPT,DC
TRACK

[Note]
Specify values of the items NEWIOUSE, DOPLSPD and PIUOTDPD
as follows:
Node,2,32,0,32,0,16,0,80,0,1_PU
,32,256,3,REG1LOG1,REDU
Node Conf Value on RTC CSV file
N,OFF,OFF,OFF,NONE,DEO_
NEWIOUSE X-Bus:1Mbps OFF HAS,INTRACK
FX-Bus:5Mbps ON
DOPLSPD 125ms OFF
25ms ON
PIUOTDPD 5Sec OFF
3Sec ON

[Note]
SHPCLKMS is non-support. Please set “NONE”.
Header meaning UNIT definition(“Unit”), NodeNum,UnitNo,UnitI
D,Descriptor,...
Unit Unit,2,1,“U1”,“Unit1”
Unit information used in this node is output with the following sets.
UnitNo,UnitID,Descriptor
Header meaning BOXUNIT(“BoxUnit”),NodeNum,BOXUNIT(1),..
BoxUnit,2,“U1”,...,“--”
.,BOXUNIT(40)
Unit Conf
Header meaning ALENBST(“Alarm”),NodeNum,ALENBST(1),...
Alarm,2,ENABLE,...,ENABLE
ALENBST(40)
Header meaning IOM
Configuration(“IOM”),NodeNum,Module#,FileA#,CardA#,IOMTyp
e,FailOpt,FREQ6050,IOREDOPT,FileB#,CardB#,segID,FLMType IOM,2,1,1,1,HLAI,UNPOWER
IOM Conf ,SIXTYHZ,NONREDUN,0,0,0
[Note] ,NONE
Because FREQ6050, segID, FLMType is not used now, the setting is
ignored.

− 347 −
Appendix A. The setting parameter of the node

A.3 Case of XPC

A.3.1 [Network Conf1] Page

Table A-12.

Parameter Description Range of Value

NODENUM Define the node number Integers 1 to 126
NODETYP Define the node type XPC
Define the status descriptor that is displayed when a Digital
Character string having 8 charac-
MOVPVTXT Composite Point is undergoing a status change (moving from one
ters or less
state to another) or i s at an intermediate point between two states
Define the status descriptor that is displayed when the status of a Character string having 8 charac-
BADPVTXT
Digital Composite Point is “Uncertain” or “Bad” ters or less

A.3.2 [Network Conf3] Page

Table A-13.

Parameter Description Range of Value

Define the Logical Name of a node
Logical Name Logical Name is set automatically when you change node number or Up to 40 character string
node type
Define the IP address of a primary
You cannot set “192.168.254.*”
Primary Ethernet A In addition, the fourth octet of the IP address becomes same as node
and “192.168.255.*”
number
Primary Ethernet B Set automatically in the case of network redundancy ----
Secondary Ethernet A Set automatically in the case of node redundancy ----
Set automatically in the case of network redundancy and node re-
Secondary Ethernet B ----
dundancy
ON
Network Redundancy Set network redundancy
OFF
Set node redundancy.
[Note]
In the case of XPC, be sure to select node redundancy when config-
uring real DOPC II hardware.
It is possible to set node non-redundancy for the function simulator,
ON
Node Redundancy but, when it is to be replaced with real hardware, be sure to change
OFF
the configuration to node redundancy. If the configuration i s made
in node non-redundancy, the status of each module i s not displayed
correctly on the detailed controller status screen, causing trouble in
maintenance work.
In the case of DOPC III, please match it with real setting.

− 348 −
 A.3 Case of XPC

A.3.3 [Node Conf1] Page

Table A-14.

Parameter Description Range of Value

NCTLSLOT Define the number of slots of an adjustment control point. Integers 0 to 640
NFASTCTL Define the number of fast scan slots of an adjustment control point. Integers 0 to NCTLSLOT
NPVSLOT Define the number of slots of an adjustment PV point. Integers 0 to 320
NFASTPV Define the number of fast scan slots of an adjustment PV point. Integers 0 to NPVSLOT
NLOGSLOT Define the number of slots of a logic point. Integers 0 to 320
NFASTLOG Define the number of fast scan slots of a logic point. Integers 0 to NLOGSLOT
NDCSLOT Define the number of slots of a digital composite point. Integers 0 to 1024
NFASTDC Define the number of fast scan slots of a digital composite point. Integers 0 to NDCSLOT
NPMSLOT Define the number of slots of a process module point. Integers 0 to 512
NFASTPM Define the number of fast scan slots of a process module point. Integers 0 to NPMSLOT
NNUMERIC Define the number of slots of a numeric value variable point. Integers 0 to 8192
NFBSLOT Define the number of slots of a function block point. Integers 0 to 511

− 349 −
Appendix A. The setting parameter of the node

A.3.4 [Node Conf2] Page

Table A-15.

Parameter Description Range of Value

Define the statement capacity that can be processed at a process
module data point 1_PU
SEQPROC
“1_PU” : 10 statements can be processed in 1 pre-emption 2_PU
“2_PU” : 20 statements can be processed in 1 pre-emption
RSTRTTIM Define the start-up time for when the auto restart function is used Integers 0 to 30
NULL
REG1LOG1
REG1LOG2
REG1LOG5
REG1LOG10
SCANRATE Define the processing cycle at each data point REG2LOG2
REG2LOG5
REG2LOG10
REG5LOG5
REG5LOG10
REG10LOG10
PKGOPT It cannot be changed ----
Define the I/O type
For X-Bus, refer to [X-bus Input/Output Equipment Hardware X-Bus:1Mbps
NEWIOUSE
Manual] (MS2-SYS100-3005) and refer to [FX-bus Input/Output FX-Bus:5Mbps
Equipment Hardware Manual] (MS2-SYS100-3004) for FX-Bus
125ms
DOPLSPD Define the DO (Digital Output) resolution
25ms
5Sec
PIUOTDPD Define the LMUX disconnect detection time
3Sec
Configuration whether the functional is limited by LMUX PV
change
OFF
LMUXPVLM [Note]
ON
LMUXPVLM can set “ON” only in the case of NEWIOUSE =
“X-Bus:1Mbps”
Defines unacknowledged return-to-normal alarm on ACKSTAT.
DEO_HAS
ACKSTOPT DEO_HAS:Treat as no alarm
APS
APS:Treat as unacknowledged alarm
Specify initial value during DC point initialization.
INTRACK
DCTRACK INTRACK:Input value is initial value.
OUTTRACK
OUTTRACK:Output value is initial value.
This is a ship-only parameter Define “NONE”,“MASTER”(Master
Node), or “SLAVE”(Slave Node) for the inboard watch. For other (When use a function)
than an inboard watch, always set to “NONE” NONE
SHPCLKMS
[Note] MASTER
This can be changed by setting the value of EnableSHPCLKMS in the SLAVE
[Browser] section of the rtcedit.ini file to “TRUE”

A.3.5 [Unit Conf1-5] Page

Table A-16.

Parameter Description Range of Value

Choose a unit ID already set on the [Unit ID] page in the [System
BOXUNIT(1)-(100) Registered Unit ID
Definition] dialog box
ENABLE
ALENBST(1)-(100) Define the alarm enable status of a unit DISABLE
INHIBIT
− 350 −
 A.3 Case of XPC

A.3.6 [IOM Conf1-12] Page

Table A-17.
IOMType Module# FileA# CardA# IOMRate FailOpt IOREDOPT FileB# CardB#
1SEC
500MS
NONREDUN
HLAI 1 - 120 1-8 1 - 12 200MS UNPOWER (*4) (*4)
REDUN
100MS
DEPENDS
HMUX(*1) 1 - 120 1-8 1 - 12 1SEC UNPOWER NONREDUN 0 0
LMUX(*1) 1 - 120 1-8 1 - 12 1SEC UNPOWER NONREDUN 0 0
RMUX(*1) 1 - 120 1-8 1 - 12 1SEC UNPOWER NONREDUN 0 0
TCAI(*2) 1 - 120 1-8 1 - 11 1SEC UNPOWER NONREDUN 0 0
RTDAI(*2) 1 - 120 1-8 1 - 11 1SEC UNPOWER NONREDUN 0 0
1SEC
500MS
NONREDUN
PI 1 - 120 1-8 1 - 16 200MS UNPOWER (*4) (*4)
REDUN
100MS
DEPENDS
UNPOWER NONREDUN
AO16 1 - 120 1-8 1 - 16 (*3) (*4) (*4)
HOLD REDUN
1SEC
500MS
DI 1 - 120 1-8 1 - 16 200MS UNPOWER NONREDUN 0 0
100MS
DEPENDS
1SEC
500MS
DISOE(*2) 1 - 120 1-8 1 - 16 200MS UNPOWER NONREDUN 0 0
100MS
DEPENDS
1SEC
500MS
UNPOWER
DO 1 - 120 1-8 1 - 16 200MS NONREDUN 0 0
HOLD
100MS
DEPENDS
1SEC
500MS
UNPOWER
DO32 1 - 120 1-8 1 - 16 200MS NONREDUN 0 0
HOLD
100MS
DEPENDS
STIM 1-8 1-8 1 - 16 1SEC UNPOWER NONREDUN 0 0
ESIM(*2) 1-8 1-8 1 - 16 1SEC UNPOWER NONREDUN 0 0

*1 IOMType can set “HMUX”, “LMUX”, “RMUX” only in the case of NEWIOUSE = “X-Bus:1Mbps”.
When setting up “HMUX”, “LMUX” and “RMUX”, they require master “HLAI” that has same
File#, smaller Card# and smaller module number.
*2 IOMType can set “TCAI”, “RTDAI”, “DISOE”, “ESIM” only in the case of NEWIOUSE =
“FX-Bus:5Mbps”.
*3 IOMRate of “AO16” is different in an optional item by NEWIOUSE.
X-Bus:1Mbps → 1SEC, 500MS, 200MS
→ 1SEC, 500MS, 200MS, 100MS, DEPENDS
FX-Bus:5Mbps
*4 Set automatically in the case of IOREDOPT = “REDUN”. (FileB# = FileA#, CardB# = CardA#+1).
In order to set “REDUN” as IOREDOPT, CardA# needs to be odd.

− 351 −
Appendix A. The setting parameter of the node

Note Card#15,16 of File#6,7 and Card#16 of File#8 cannot be set up in XPC.

Note When you use distributed I/O, the File numbers are equivalent to the block ad-
dresses of distributed I/O, and the Card numbers are equivalent to base addresses.
File numbers (1 to 8) : Dip switch BLK of block address (0 to 7)
Card numbers (1 to 16) : Dip switch BASE of base address (0 to 15)
For details about how to set the X-bus addresses of distributed I/O by dip switches
on the module base, refer to [Harmonas-DEO DEO Process Controller Installation
Manual](for distributed I/O Module)(MS2-DEO200-3003) or the [Harmonas-DEO
DEO Process Controller II Installation Manual](MS2-DEO200-3005).

Note To use high-level input of signal unit I/O, set the module type to “HLAI”.
To use analog output of signal unit I/O, set the module type to “AO16”.

Note Please select “HLAI” when using an analog input of SIO II.
Sensor type and range of temperature are configured on Signal Unit I/O-II(SIO II)
Communicator when using SIO II TC input units(HD-STCU50C) or SIO II RTD input
units(HD-SRTU50C).
Please set PVEUHI and PVEULO to same values which are set on SIO II Communicator.

− 352 −
 A.3 Case of XPC

A.3.7 CSV format for import/export

The CSV format for import / export is as follows.
A line beginning with ‘#’ is considered as a comment line and is not a target of the import
process.

Table A-18.

Line The CSV format for import/export Example

Header meaning Network Configuration (“Nwk”),,NodeNum,
NodeType,Moving PV Text,Bad PV Text,Logical Name,IP
Address1,Network Redun,Node Redun Nwk,,3,XPC,“MOVING”,“BAD”,“
Network Conf
XPC003”,192.168.0.3,OFF,OFF
[Note]
Network Redun and Node Redun sets it in “ON” or “OFF”.
Header meaning Node
Configuration(“Node”),NodeNum,NCTLSLOT,NFASTCTL,NPVSL
OT,NFASTPV,NLOGSLOT,NFASTLOG,NDCSLOT,NFASTDC,NP
MSLOT,NFASTPM,NNUMERIC,NFBSLOT,
SEQPROC,RSTRTTIM,SCANRATE,NEWIOUSE,DOPLSPD,PIUO
TDPD,SHPCLKMS,LMUXPVLM,ACKSTOPT,DCTRACK

[Note]
Specify values of the item NEWIOUSE, DOPLSPD and PIUOTDPD Node,3,64,0,64,0,32,0,160,0,6
as follows: 4,0,8192,256,1_PU,3,REG1LO
Node Conf
G1,ON,OFF,OFF,NONE,OFF,
Value on RTC CSV file
DEO_HAS,INTRACK
X-Bus:1Mbps OFF
NEWIOUSE
FX-Bus:5Mbps ON
125ms OFF
DOPLSPD
25ms ON
5Sec OFF
PIUOTDPD
3Sec ON

Header meaning UNIT definition(“Unit”), NodeNum,UnitNo,UnitI

D,Descriptor,...
Unit Unit,3,1,“U1”,“Unit1”
Unit information used in this node is output with the following sets.
UnitNo,UnitID,Descriptor
Header meaning BOXUNIT(“BoxUnit”),NodeNum,BOXUNIT(1),..
BoxUnit,3,“U1”,...,“--”
.,BOXUNIT(100)
Unit Conf
Header meaning ALENBST(“Alarm”),NodeNum,ALENBST(1),...
Alarm,3,ENABLE,...,ENABLE
ALENBST(100)
Header meaning IOM
Configuration(“IOM”),NodeNum,Module#,FileA#,CardA#,IOMTy
pe,IOMRate,FailOpt,FREQ6050,IOREDOPT,FileB#,CardB#,segID,
IOM,3,1,1,1,HLAI,DEPENDS,U
FLMType
IOM CONF NPOWER,SIXTYHZ,NONRED
UN,0,0,0,NONE
[Note]
Because FREQ6050, segID, FLMType is not used now, the setting is
ignored.
Header meaning FB Point Configuration(“FB”),NodeNum,Slot
FB Point FB,3,1,“FB001”,“U1”,1SEC,“”
Num,Tag Name,Unit ID,ExecRate,Description

− 353 −
Appendix A. The setting parameter of the node

A.4 Case of FLC

A.4.1 [Network Conf1] Page

Table A-19.

Parameter Description Range of Value

NODENUM Define the node number Integers 1 to 126
NODETYP Define the node type FLC
Define the status descriptor that is displayed when a Digital
Character string having 8 charac-
MOVPVTXT Composite Point is undergoing a status change (moving from one
ters or less
state to another) or i s at an intermediate point between two states.
Define the status descriptor that is displayed when the status of a Character string having 8 charac-
BADPVTXT
Digital Composite Point is “Uncertain” or “Bad” ters or less

A.4.2 [Network Conf3] Page

Table A-20.

Parameter Description Range of Value

Define the Logical Name of a node Logical Name is set automatically
Logical Name Up to 40 character string
when you change node number or node type
Define the IP address of a primary In addition, the fourth octet of the You cannot set “192.168.254.*”
Primary Ethernet A
IP address becomes same as node number and “192.168.255.*”
Primary Ethernet B Set automatically in the case of network redundancy ----
Secondary Ethernet A Set automatically in the case of node redundancy ----
Set automatically in the case of network redundancy and node re-
Secondary Ethernet B ----
dundancy
ON
Network Redundancy Set network redundancy
OFF
ON
Node Redundancy Set node redundancy
OFF

− 354 −
 A.4 Case of FLC

A.4.3 [Node Conf1] Page

Table A-21.

Parameter Description Range of Value

NCTLSLOT Define the number of slots of an adjustment control point. Integers 0 to 32
NFASTCTL Define the number of fast scan slots of an adjustment control point. Integers 0 to NCTLSLOT
NPVSLOT Define the number of slots of an adjustment PV point. Integers 0 to 32
NFASTPV Define the number of fast scan slots of an adjustment PV point. Integers 0 to NPVSLOT
NLOGSLOT Define the number of slots of a logic point. Integers 0 to 64
NFASTLOG Define the number of fast scan slots of a logic point. Integers 0 to NLOGSLOT
NDCSLOT Define the number of slots of a digital composite point. Integers 0 to 256
NFASTDC Define the number of fast scan slots of a digital composite point. Integers 0 to NDCSLOT
NPMSLOT Define the number of slots of a process module point. Integers 0 to 128
NFASTPM Define the number of fast scan slots of a process module point. Integers 0 to NPMSLOT
NNUMERIC It cannot be changed. ----
NFBSLOT Define the number of slots of a function block point. Integers 0 to 128

A.4.4 [Node Conf2] Page

Table A-22.

Parameter Description Range of Value

Define the statement capacity that can be processed at a process
module data point 1_PU
SEQPROC
“1_PU” : 10 statements can be processed in 1 pre-emption 2_PU
“2_PU” : 20 statements can be processed in 1 pre-emption
RSTRTTIM Define the start-up time for when the auto restart function is used. Integers 0 to 30
1sec
Define the processing cycle at each data point REG and LOG is set 500ms
SCANRATE
each 200ms
100ms
NONREDUN
PKGOPT Define the hardware packaging option
REDUN
NEWIOUSE It cannot be changed ----
DOPLSPD It cannot be changed ----
PIUOTDPD It cannot be changed ----
Defines unacknowledged return-to-normal alarm on ACKSTAT.
DEO_HAS
ACKSTOPT DEO_HAS:Treat as no alarm
APS
APS:Treat as unacknowledged alarm
Specify initial value during DC point initialization.
INTRACK
DCTRACK INTRACK:Input value is initial value.
OUTTRACK
OUTTRACK:Output value is initial value.
SHPCLKMS It cannot be changed ----

− 355 −
Appendix A. The setting parameter of the node

A.4.5 [Unit Conf1-5] Page

Table A-23.

Parameter Description Range of Value

Choose a unit ID already set on the [Unit ID] page in the [System
BOXUNIT(1)-(100) Registered Unit ID
Definition] dialog box
ENABLE
ALENBST(1)-(100) Define the alarm enable status of a unit DISABLE
INHIBIT

A.4.6 [IOM Conf1-3] Page

Table A-24.

IOMType Module# FileA# CardA# IOMRate FailOpt IOREDOPT FileB# CardB#

1SEC
500MS
HLAI 1 - 24 1-4 1-6 200MS UNPOWER NONREDUN 0 0
100MS
DEPENDS
TCAI 1 - 24 1-4 1-6 1SEC UNPOWER NONREDUN 0 0
RTDAI 1 - 24 1-4 1-6 1SEC UNPOWER NONREDUN 0 0
1SEC
500MS
PI 1 - 24 1-4 1-6 200MS UNPOWER NONREDUN 0 0
100MS
DEPENDS
1SEC
500MS
UNPOWER
AO16 1 - 24 1-4 1-6 200MS NONREDUN 0 0
HOLD
100MS
DEPENDS
1SEC
500MS
DI 1 - 24 1-4 1-6 200MS UNPOWER NONREDUN 0 0
100MS
DEPENDS
1SEC
500MS
UNPOWER
DO32 1 - 24 1-4 1-6 200MS NONREDUN 0 0
HOLD
100MS
DEPENDS
ESIM 1-8 1-4 1-6 1SEC UNPOWER NONREDUN 0 0

Note Please select TCAI/RTDAI when using FLC TCmV input set(HD-FXLIPS00)/FLC RTD
input set(HD-FXRTDPS1).
Sensor type and PV characterization are configured on RTC editor as other
controllers.
Please set PIUOTDCF to a setting about Burnout. (HI is ON, LO is OFF)

− 356 −
 A.4 Case of FLC

A.4.7 CSV format for import/export

The CSV format for import/export is as follows.
A line beginning with ‘#’ is considered as a comment line and is not a target of the import
process.

Table A-25.

Line The CSV format for import/export Example

Header meaning Network Configuration (“Nwk”),,NodeNum,Nod Nwk,,4,FLC,“MOVING”,“BAD”,“

Network Conf eType,Moving PVText,Bad PV Text,Logical Name,IP Address1,IP FLC004”,192.168.0.4,0.0.0.0,
Address2,IP Address3,IP Address4 0.0.0.0,0.0.0.0

Header meaning Node

Configuration(“Node”),NodeNum,NCTLSLOT,NFASTCTL,NPVSL
OT,NFASTPV,NLOGSLOT,NFASTLOG,NDCSLOT,NFASTDC,NP
MSLOT,NFASTPM,NFBSLOT,SEQPROC,RSTRTTIM,SCANRATE
,PKGOPT,NEWIOUSE,DOPLSPD,PIUOTDPD,SHPCLKMS,ACKS
TOPT,DCTRACK Node,4,32,0,32,0,64,0,256,0,128
,0,128,1_PU,3,REG1LOG1,NO
Node Conf
[Note] NREDUN,ON,OFF,OFF,NONE,
SCANRATE sets it in a REGxLOGx form. DEO_HAS,INTRACK
[Note]
NEWIOUSE is non-support. Please set “ON”
DOPLSPD is non-support. Please set “OFF”
PIUOTDPD is non-support. Please set “OFF”
SHPCLKMS is non-support. Please set “NONE”
Header meaning UNIT definition(“Unit”), NodeNum,UnitNo,UnitI
D,Descriptor,...
Unit Unit,4,1,“U1”,“Unit1”
Unit information used in this node is output with the following sets.
UnitNo,UnitID,Descriptor
Header meaning BOXUNIT(“BoxUnit”),NodeNum,BOXUNIT(1),..
BoxUnit,4,“U1”,...,“--”
.,BOXUNIT(100)
Unit Conf
Header meaning ALENBST(“Alarm”),NodeNum,ALENBST(1),...
Alarm,4,ENABLE,...,ENABLE
ALENBST(100)
Header meaning IOM
Configuration(“IOM”),NodeNum,Module#,FileA#,CardA#,IOMTy
pe,IOMRate,Fail Opt,FREQ6050,IOREDOPT,FileB#,CardB#,segID,
IOM,4,1,1,1,HLAI,DEPENDS,U
FLMType
IOM CONF NPOWER,SIXTYHZ,NONRED
UN,0,0,0,NONE
[Note]
Because FREQ6050, segID, FLMType is not used now, the setting is
ignored.
Header meaning FB Point Configuration(“FB”),NodeNum,Slot
FB Point FB,4,1,“FB001”,“U1”,1SEC,“”
Num,Tag Name,Unit ID,ExecRate,Description

− 357 −
Appendix A. The setting parameter of the node

A.5 Case of PL

A.5.1 [Network Conf1] Page

Table A-26.

Parameter Description Range of Value

NODENUM Define the node number Integers 1 to 126
NODETYP Define the node type PL
Define the status descriptor that is displayed when a Digital
Character string having 8 charac-
MOVPVTXT Composite Point is undergoing a status change (moving from one
ters or less
state to another) or i s at an intermediate point between two states.
Define the status descriptor that is displayed when the status of a Character string having 8 charac-
BADPVTXT
Digital Composite Point is “Uncertain” or “Bad” ters or less

A.5.2 [Network Conf3] Page

Table A-27.

Parameter Description Range of Value

Define the Logical Name of a node
Logical Name Logical Name is set automatically when you change node number or Up to 40 character string
node type
Define the IP address of a primary In addition, the fourth octet of the You cannot set “192.168.254.*”
Primary Ethernet A
IP address becomes same as node number and “192.168.255.*”
Primary Ethernet B Set automatically in the case of network redundancy ----
Secondary Ethernet A It cannot be changed ----
Secondary Ethernet B It cannot be changed ----
ON
Network Redundancy Set network redundancy
OFF
Node Redundancy It cannot be changed ----

− 358 −
 A.5 Case of PL

A.5.3 [Node Conf1] Page

Table A-28.

Parameter Description Range of Value

NCTLSLOT It cannot be changed. ----
NFASTCTL It cannot be changed. ----
NPVSLOT It cannot be changed. ----
NFASTPV It cannot be changed. ----
NLOGSLOT Define the number of slots of a logic point. Integers 0 to 128
NFASTLOG It cannot be changed. ----
NDCSLOT Define the number of slots of a digital composite point. Integers 0 to 512
NFASTDC It cannot be changed. ----
NPMSLOT It cannot be changed. ----
NFASTPM It cannot be changed. ----
NNUMERIC Define the number of slots of a numeric value variable point. Integers 0 to 3072
NFBSLOT It cannot be changed. ----

A.5.4 [Node Conf2] Page

Table A-29.

Parameter Description Range of Value

SEQPROC It cannot be changed ----
RSTRTTIM It cannot be changed ----
NULL
REG1LOG1
REG1LOG2
REG1LOG4
REG2LOG2
REG2LOG4
REG4LOG4
REG1LOG10
SCANRATE Define the processing cycle at each data point
REG1LOG20
REG2LOG10
REG2LOG20
REG4LOG10
REG4LOG20
REG10LOG10
REG10LOG20
REG20LOG20
PKGOPT It cannot be changed. ----
NEWIOUSE It cannot be changed. ----
DOPLSPD It cannot be changed. ----
PIUOTDPD It cannot be changed. ----
SHPCLKMS It cannot be changed. ----

− 359 −
Appendix A. The setting parameter of the node

A.5.5 [Node Conf3] Page

Table A-30.

Parameter Description Range of Value

NONE
Define MELSEC-NET of I/O Sub System1
MNET10_BOARD1
I/O Sub System1 MNET10_BOARD2
[Note]
MNET10_BOARD3
Except “NONE”, do not duplicate with other I/O Sub System
MNET10_BOARD4
NONE
Define MELSEC-NET of I/O Sub System2
MNET10_BOARD1
I/O Sub System2 MNET10_BOARD2
[Note]
MNET10_BOARD3
Except “NONE”, do not duplicate with other I/O Sub System
MNET10_BOARD4
NONE
Define MELSEC-NET of I/O Sub System3
MNET10_BOARD1
I/O Sub System3 MNET10_BOARD2
[Note]
MNET10_BOARD3
Except “NONE”, do not duplicate with other I/O Sub System
MNET10_BOARD4
NONE
Define MELSEC-NET of I/O Sub System4
MNET10_BOARD1
I/O Sub System4 MNET10_BOARD2
[Note]
MNET10_BOARD3
Except “NONE”, do not duplicate with other I/O Sub System
MNET10_BOARD4

A.5.6 [Unit Conf1-4] Page

Table A-31.

Parameter Description Range of Value

Choose a unit ID already set on the [Unit ID] page in the [System
BOXUNIT(1)-(80) Registered Unit ID
Definition] dialog box
ENABLE
ALENBST(1)-(80) Define the alarm enable status of a unit DISABLE
INHIBIT

− 360 −
 A.5 Case of PL

A.5.7 [IOM Conf1-8] Page

Table A-32.

IOMType Module# I/O SubNo. PLC No. Start No.

HLAI 1 - 80 1-4 1 - 64 0 - 8176
PI 1 - 80 1-4 1 - 64 0 - 8176
AO16 1 - 80 1-4 1 - 64 0 - 8176
DI 1 - 80 1-4 1 - 64 0 - 8160
DO32 1 - 80 1-4 1 - 64 0 - 8160
VALIN 1 - 80 1-4 1 - 64 0 - 8176
VALOUT 1 - 80 1-4 1 - 64 0 - 8176

Refer to [Harmonas-DEO Open PLC Linker II Function Manual](MS2-DEO300-1021)

“Section 13. DOPL II Configuration” for the detailed setting method.

A.5.8 CSV format for import/export

The CSV format for import/export is as follows.
A line beginning with ‘#’ is considered as a comment line and is not a target of the import
process.

Table A-33.

Line The CSV format for import/export Example

Header meaning Network Configuration (“Nwk”),,NodeNum,Nod
Nwk,,5,PL,“MOVING”,“BAD”,“PL005”
Network Conf eType,Moving PVText,Bad PV Text,Logical Name,IP Address1,IP
,192.168.0.5,0.0.0.0,0.0.0.0,0.0.0.0
Address2,IP Address3,IP Address4
Header meaning Node
Node,5,16,80,256,REG1LOG1,
Configuration(“Node”),NodeNum,NLOGSLOT,NDCSLOT,NNUM
Node Conf MNET10_BOARD1,NONE,NONE,
ERIC,SCANRATE,IOSUBTYP(1),IOSUBTYP(2),IOSUBTYP(3),IO
NONE
SUBTYP(4)
Header meaning UNIT definition(“Unit”), NodeNum,UnitNo,UnitI
D,Descriptor,...
Unit Unit,5,1,“U1”,“Unit1”
Unit information used in this node is output with the following sets.
UnitNo,UnitID,Descriptor
Header meaning BOXUNIT(“BoxUnit”),NodeNum,BOXUNIT(1),..
BoxUnit,5,“U1”,...,“--”
.,BOXUNIT(80)
Unit Conf
Header meaning ALENBST(“Alarm”),NodeNum,ALENBST(1),...
Alarm,5,ENABLE,...,ENABLE
ALENBST(80)
Header meaning IOM Configuration(“IOM”),NodeNum,Module#,I
OMType,I/O SubNo.,PLC No.,Sever Name,Topic/Group Name,Start
No.
IOM CONF IOM,5,1,HLAI,1,1,“”,“”,0
[Note]
Server Name and Topic/Group Name are not used now. It is ignored
even if it sets up

− 361 −
Appendix A. The setting parameter of the node

A.6 Case of PL2

A.6.1 [Network Conf1] Page

Table A-34.

Parameter Description Range of Value

NODENUM Define the node number Integers 1 to 126
NODETYP Define the node type PL2
Define the status descriptor that is displayed when a Digital
Character string having 8 charac-
MOVPVTXT Composite Point is undergoing a status change (moving from one
ters or less
state to another) or i s at an intermediate point between two states.
Define the status descriptor that is displayed when the status of a Character string having 8 charac-
BADPVTXT
Digital Composite Point is “Uncertain” or “Bad” ters or less

A.6.2 [Network Conf3] Page

Table A-35.

Parameter Description Range of Value

Define the Logical Name of a node
Logical Name Logical Name is set automatically when you change node number or Up to 40 character string
node type
Define the IP address of a primary
You cannot set “192.168.254.*”
Primary Ethernet A In addition, the fourth octet of the IP address becomes same as node
and “192.168.255.*”
number
Primary Ethernet B Set automatically in the case of network redundancy ----
Secondary Ethernet A Set automatically in the case of node redundancy ----
Set automatically in the case of network redundancy and node re-
Secondary Ethernet B ----
dundancy
ON
Network Redundancy Set network redundancy
OFF
ON
Node Redundancy Set node redundancy
OFF

− 362 −
 A.6 Case of PL2

A.6.3 [Node Conf1] Page

Table A-36.

Parameter Description Range of Value

NCTLSLOT Define the number of slots of an adjustment control point. Integers 0 to 640
NFASTCTL Define the number of fast scan slots of an adjustment control point. Integers 0 to NCTLSLOT
NPVSLOT Define the number of slots of an adjustment PV point. Integers 0 to 480
NFASTPV Define the number of fast scan slots of an adjustment PV point. Integers 0 to NPVSLOT
NLOGSLOT Define the number of slots of a logic point. Integers 0 to 480
NFASTLOG Define the number of fast scan slots of a logic point. Integers 0 to NLOGSLOT
NDCSLOT Define the number of slots of a digital composite point. Integers 0 to 1600
NFASTDC Define the number of fast scan slots of a digital composite point. Integers 0 to NDCSLOT
NPMSLOT Define the number of slots of a process module point. Integers 0 to 512
NFASTPM Define the number of fast scan slots of a process module point. Integers 0 to NPMSLOT
NNUMERIC Define the number of slots of a numeric value variable point. Integers 0 to 8192
NFBSLOT Define the number of slots of a function block point. Integers 0 to 511

− 363 −
Appendix A. The setting parameter of the node

A.6.4 [Node Conf2] Page

Table A-37.

Parameter Description Range of Value

Define the statement capacity that can be processed at a process
module data point 1_PU
SEQPROC
“1_PU” : 10 statements can be processed in 1 pre-emption 2_PU
“2_PU” : 20 statements can be processed in 1 pre-emption
RSTRTTIM It cannot be changed ----
NULL
REG1LOG1
REG1LOG2
REG1LOG5
REG1LOG10
SCANRATE Define the processing cycle at each data point REG2LOG2
REG2LOG5
REG2LOG10
REG5LOG5
REG5LOG10
REG10LOG10
NONREDUN
PKGOPT Define the hardware packaging option
REDUN
NEWIOUSE It cannot be changed ----
DOPLSPD It cannot be changed ----
PIUOTDPD It cannot be changed ----
Defines unacknowledged return-to-normal alarm on ACKSTAT.
DEO_HAS
ACKSTOPT DEO_HAS:Treat as no alarm
APS
APS:Treat as unacknowledged alarm
Specify initial value during DC point initialization.
INTRACK
DCTRACK INTRACK:Input value is initial value.
OUTTRACK
OUTTRACK:Output value is initial value.
SHPCLKMS It cannot be changed ----
Set the upper limit of the slot number for changed notification of
LGCDCTSL LOGIC. If no upper limit is to be set, set the limit to “0”. When an 0 or Integers 129 to 480
upper limit is to be set, set it within the range of “129” and “480”.

− 364 −
 A.6 Case of PL2

A.6.5 [Node Conf3] Page

Table A-38.

Parameter Description Range of Value

MNET10_BOARD1
I/O Sub System1 Define MELSEC-NET of I/O Sub System1
MNET_H_BOARD1
Set the output module number for primary/secondary judg-
ment of standby redundancy.
PSOPMNUM In the case of standby redundancy and I/O Sub System1 is Integers 1 to 240
MELSEC, always set a module number of which IOMType is
“AO16”.
Set the input module number for primary/secondary judg-
ment of standby redundancy.
In the case of standby redundancy and I/O Sub System1 is
PSIPMNUM Integers 0 to 240
MELSEC, you can set a module number of which IOMType
is “HLAI”.
When you do not use this function, please set “0”.
Set the W device offset value from the right to the left module In the case of I/O Sub System1 is
of standby redundancy.
WOFFSET
In the case of standby redundancy and I/O Sub System1 is MNET10_BOARD1:Integers 0 to 8176
MELSEC, you can set. MNET_H_BOARD1:Integers 0 to 16368

Set the B device offset value from the right to the left module In the case of I/O Sub System1 is
of standby redundancy.
BOFFSET
In the case of standby redundancy and I/O Sub System1 is MNET10_BOARD1:Integers 0 to 8160
MELSEC, you can set. Please set it with 16 multiples. MNET_H_BOARD1:Integers 0 to 16352

Set the time difference to allow the output check time of

OPCHTIM standby redundancy. In the case of standby redundancy and Integers 1 to 10
I/O Sub System1 is MELSEC, you can set.

A.6.6 [Unit Conf1-5] Page

Table A-39.

Parameter Description Range of Value

Choose a unit ID already set on the [Unit ID] page in the [System
BOXUNIT(1)-(100) Registered Unit ID
Definition] dialog box
ENABLE
ALENBST(1)-(100) Define the alarm enable status of a unit DISABLE
INHIBIT

− 365 −
Appendix A. The setting parameter of the node

A.6.7 [IOM Conf1-24] Page

Table A-40.

IOMType Module# I/O SubNo. PLC No. Start No. IOMRate

1SEC
In the case of I/O Sub System1 is
500MS
HLAI 1 - 240 1 1 - 64 200MS
MNET10_BOARD1:Integers 0 to 8176
100MS
MNET_H_BOARD1: Integers 0 to 16368
DEPENDS
1SEC
In the case of I/O Sub System1 is
500MS
PI 1 - 240 1 1 - 64 200MS
MNET10_BOARD1: Integers 0 to 8176
100MS
MNET_H_BOARD1: Integers 0 to 16368
DEPENDS
1SEC
In the case of I/O Sub System1 is
500MS
AO16 1 - 240 1 1 - 64 200MS
MNET10_BOARD1: Integers 0 to 8176
100MS
MNET_H_BOARD1: Integers 0 to 16368
DEPENDS
1SEC
In the case of I/O Sub System1 is
500MS
DI 1 - 240 1 1 - 64 200MS
MNET10_BOARD1: Integers 0 to 8160
100MS
MNET_H_BOARD1: Integers 0 to 16352
DEPENDS
1SEC
In the case of I/O Sub System1 is
500MS
DO32 1 - 240 1 1 - 64 200MS
MNET10_BOARD1: Integers 0 to 8160
100MS
MNET_H_BOARD1: Integers 0 to 16352
DEPENDS
1SEC
In the case of I/O Sub System1 is
500MS
VALIN 1 - 240 1 1 - 64 200MS
MNET10_BOARD1: Integers 0 to 8176
100MS
MNET_H_BOARD1: Integers 0 to 16368
DEPENDS
1SEC
In the case of I/O Sub System1 is
500MS
VALOUT 1 - 240 1 1 - 64 200MS
MNET10_BOARD1: Integers 0 to 8176
100MS
MNET_H_BOARD1: Integers 0 to 16368
DEPENDS

Refer to [Harmonas-DEO PLC Linker II Function Manual](MS2-HDS900-1021) “Section

13. DOPL II Configuration” for the detailed setting method.

− 366 −
 A.6 Case of PL2

A.6.8 CSV format for import/export

The CSV format for import/export is as follows.
A line beginning with ‘#’ is considered as a comment line and is not a target of the import
process.

Table A-41.

Line The CSV format for import/export Example

Header meaning Network Configuration (“Nwk”),,NodeNum,Nod
Nwk,,6,PL2,“MOVING”,“BAD”,“PL2006”,
Network Conf eType,Moving PV Text,Bad PV Text,Logical Name,IP Address1,IP
192.168.0.6,0.0.0.0,0.0.0.0,0.0.0.0
Address2,IP Address3,IP Address4
Header meaning Node
Configuration(“Node”),NodeNum,NCTLSLOT,NFASTCTL,NPVSL
OT,NFASTPV,NLOGSLOT,NFASTLOG,NDCSLOT,NFASTDC,NP
MSLOT,NFASTPM,NNUMERIC,NFBSLOT,SEQPROC,SCANRATE
Node,6,64,0,64,0,32,0,160,0,64,0,8192,256
,PKGOPT,LGCDCTSL,IOSUBTYP(1),PSOPMNUM,PSIPMNUM,W
,1_PU,REG1LOG1,REDUN,0,MNET10_
Node Conf OFFSET,BOFFSET,WPLCADDR,BPLCADDR,LNODADDR,OPCH
BOARD1,0,0,0,0,0,0,0,3,DEO_
TIM,ACKSTOPT,DCTRACK
HAS,INTRACK
[Note]
WPLCADDR, BPLCADDR and LNODADDR are not used now. It is
ignored even if it sets up.
Header meaning UNIT definition(“Unit”), NodeNum,UnitNo,UnitI
D,Descriptor,...
Unit Unit,6,1,“U1”,“Unit1”
Unit information used in this node is output with the following sets.
UnitNo,UnitID,Descriptor
Header meaning BOXUNIT(“BoxUnit”),NodeNum,BOXUNIT(1),..
BoxUnit,6,“U1”,...,“--”
.,BOXUNIT(100)
Unit Conf
Header meaning ALENBST(“Alarm”),NodeNum,ALENBST(1),...
Alarm,6,ENABLE,...,ENABLE
ALENBST(100)
Header meaning IOM Configuration(“IOM”),NodeNum,Module#,I
OMType,I/O SubNo.,PLC No.,Sever Name,Topic/Group Name,Start
No.,IOMRate
IOM CONF IOM,6,1,HLAI,1,1,“”,“”,0,DEPENDS
[Note]
Server Name and Topic/Group Name are not used now. It is ignored
even if it sets up.
Header meaning FB Point Configuration(“FB”),NodeNum,Slot
FB Point FB,6,1,“FB001”,“U1”,1SEC,“”
Num,Tag Name,Unit ID,ExecRate,Description

− 367 −
Appendix A. The setting parameter of the node

A.7 Case of FC

A.7.1 [Network Conf1] Page

Table A-42.

Parameter Description Range of Value

NODENUM Define the node number Integers 1 to 126
NODETYP Define the node type FC
Define the status descriptor that is displayed when a Digital
Character string having 8 charac-
MOVPVTXT Composite Point is undergoing a status change (moving from one
ters or less
state to another) or i s at an intermediate point between two states.
Define the status descriptor that is displayed when the status of a Character string having 8 charac-
BADPVTXT
Digital Composite Point is “Uncertain” or “Bad” ters or less

A.7.2 [Network Conf3] Page

Table A-43.

Parameter Description Range of Value

Define the Logical Name of a node
Logical Name Logical Name is set automatically when you change node number or Up to 40 character string
node type
Define the IP address of a primary
You cannot set “192.168.254.*”
Primary Ethernet A In addition, the fourth octet of the IP address becomes same as node
and “192.168.255.*”
number
Primary Ethernet B Set automatically in the case of network redundancy ----
Secondary Ethernet A Set automatically in the case of node redundancy ----
Set automatically in the case of network redundancy and node re-
Secondary Ethernet B ----
dundancy
ON
Network Redundancy Set network redundancy
OFF
ON
Node Redundancy Set node redundancy
OFF

− 368 −
 A.7 Case of FC

A.7.3 [Node Conf1] Page

Table A-44.

Parameter Description Range of Value

NCTLSLOT Define the number of slots of an adjustment control point Integers 0 to 640
NFASTCTL Define the number of fast scan slots of an adjustment control point Integers 0 to NCTLSLOT
NPVSLOT Define the number of slots of an adjustment PV point Integers 0 to 480
NFASTPV Define the number of fast scan slots of an adjustment PV point Integers 0 to NPVSLOT
NLOGSLOT Define the number of slots of a logic point Integers 0 to 480
NFASTLOG Define the number of fast scan slots of a logic point Integers 0 to NLOGSLOT
NDCSLOT Define the number of slots of a digital composite point Integers 0 to 1600
NFASTDC Define the number of fast scan slots of a digital composite point Integers 0 to NDCSLOT
NPMSLOT Define the number of slots of a process module point Integers 0 to 512
NFASTPM Define the number of fast scan slots of a process module point Integers 0 to NPMSLOT
NNUMERIC Define the number of slots of a numeric value variable point Integers 0 to 8192
NFBSLOT Define the number of slots of a function block point Integers 0 to 511

− 369 −
Appendix A. The setting parameter of the node

A.7.4 [Node Conf2] Page

Table A-45.

Parameter Description Range of Value

Define the statement capacity that can be processed at a process
module data point 1_PU
SEQPROC
“1_PU” : 10 statements can be processed in 1 pre-emption 2_PU
“2_PU” : 20 statements can be processed in 1 pre-emption
RSTRTTIM It cannot be changed ----
NULL
REG1LOG1
REG1LOG2
REG1LOG5
REG1LOG10
SCANRATE Define the processing cycle at each data point REG2LOG2
REG2LOG5
REG2LOG10
REG5LOG5
REG5LOG10
REG10LOG10
PKGOPT It cannot be changed ----
NEWIOUSE It cannot be changed ----
DOPLSPD It cannot be changed ----
PIUOTDPD It cannot be changed ----
Defines unacknowledged return-to-normal alarm on ACKSTAT.
ACKSTOPT DEO_HAS:Treat as no alarm DEO_HAS APS
APS:Treat as unacknowledged alarm
Specify initial value during DC point initialization.
INTRACK
DCTRACK INTRACK:Input value is initial value.
OUTTRACK
OUTTRACK:Output value is initial value.
SHPCLKMS It cannot be changed ----
Set the upper limit of the slot number for changed notification of
LGCDCTSL LOGIC. If no upper limit is to be set, set the limit to “0”. When an 0 or Integers 129 to 480
upper limit is to be set, set it within the range of “129” and “480”.

A.7.5 [Node Conf3] Page

Table A-46.

Parameter Description Range of Value

NONE
I/O Sub System1 Define MELSEC-NET of I/O Sub System1
FIELDBUS_BOARD1
PSOPMNUM It cannot be changed ----
PSIPMNUM It cannot be changed ----
WOFFSET It cannot be changed ----
BOFFSET It cannot be changed ----
OPCHTIM It cannot be changed ----

− 370 −
 A.7 Case of FC

A.7.6 [Node Conf4] Page

Table A-47.

Parameter Description Range of Value

NONE
I/O Sub System2 Define MELSEC-NET of I/O Sub System2 MNET10_BOARD2
MNET_H_BOARD2
Set the output module number for primary/secondary judg-
ment of standby redundancy.
PSOPMNUM In the case of standby redundancy and I/O Sub System2 is Integers 1 to 120
MELSEC, always set a module number of which IOMType is
“AO16”.
Set the input module number for primary/secondary judg-
ment of standby redundancy.
PSIPMNUM In the case of standby redundancy and I/O Sub System2 is Integers 0 to 120
MELSEC, you can set a module number of which IOMType
is “HLAI”. When you do not use this function, please set “0”.
In the case of I/O Sub
Set the W device offset value from the right to the left module System2 is
of standby redundancy. MNET10_BOARD2: Integers
WOFFSET
In the case of standby redundancy and I/O Sub System2 is 0 to 8064
MELSEC, you can set. MNET_H_BOARD2:
Integers 0 to 16256
In the case of I/O Sub
Set the B device offset value from the right to the left module System2 is
of standby redundancy. MNET10_BOARD2: Integers
BOFFSET
In the case of standby redundancy and I/O Sub System2 is 0 to 8064
MELSEC, you can set. Please set it with 16 multiples. MNET_H_BOARD2:
Integers 0 to 16256
Set the time difference to allow the output check time of
standby redundancy.
OPCHTIM Integers 1 to 10
In the case of standby redundancy and I/O Sub System2 is
MELSEC, you can set.

A.7.7 [Unit Conf1-5] Page

Table A-48.

Parameter Description Range of Value

Choose a unit ID already set on the [Unit ID] page in the
BOXUNIT(1)-(100) Registered Unit ID
[System Definition] dialog box
ENABLE
ALENBST(1)-(100) Define the alarm enable status of a unit DISABLE
INHIBIT

− 371 −
Appendix A. The setting parameter of the node

A.7.8 [IOM Conf1-12] Page

Table A-49.

I/O Segment
IOMType Module# PLC No. Start No. IOMRate IOMCYCLE IOMTMOUT IOREDOPT
SubNo. No.
1SEC
0 - 9, NONREDUN
FBLM (*1) 1 - 120 1 0 1 - 96 0 500MS 0 - 10
AUTO (*4) REDUN
200MS
1SEC
500MS
HLAI (*2) 1 - 120 2 1 - 64 0 (*3) 200MS AUTO 0 NONREDUN
100MS
DEPENDS
1SEC
500MS
PI (*2) 1 - 120 2 1 - 64 0 (*3) 200MS AUTO 0 NONREDUN
100MS
DEPENDS
1SEC
500MS
AO16 (*2) 1 - 120 2 1 - 64 0 (*3) 200MS AUTO 0 NONREDUN
100MS
DEPENDS
1SEC
500MS
DI (*2) 1 - 120 2 1 - 64 0 (*3) 200MS AUTO 0 NONREDUN
100MS
DEPENDS
1SEC
500MS
DO32 (*2) 1 - 120 2 1 - 64 0 (*3) 200MS AUTO 0 NONREDUN
100MS
DEPENDS
1SEC
500MS
VALIN
1 - 120 2 1 - 64 0 (*3) 200MS AUTO 0 NONREDUN
(*2)
100MS
DEPENDS
1SEC
500MS
VALOUT
1 - 120 2 1 - 64 0 (*3) 200MS AUTO 0 NONREDUN
(*2)
100MS
DEPENDS

*1 In the case of I/O Sub System1 is “FIELDBUS_BOARD1”, you can set.

*2 In the case of I/O Sub System2 is “MNET10_BOARD2” or “MNET_H_BOARD2”, you can set.
*3 In the case of I/O Sub System2 is
MNET10_BOARD2 : Integers 0 to 8064
MNET_H_BOARD2 : Integers 0 to 16256
*4 Please set it within IOMRate. In addition, please set it within REGx of SCANRATE in the case
of IOMRate is “DEPENDS”.

− 372 −
 A.7 Case of FC

A.7.9 CSV format for import/export

The CSV format for import / export is as follows.
A line beginning with ‘#’ is considered as a comment line and is not a target of the import
process.

Table A-50.

Line The CSV format for import/export Example

Header meaning Network Configuration (“Nwk”),,NodeNum,Nod
Nwk,,7,FC,“MOVING”,“BAD”,“FC007”,
Network Conf eType,Moving PV Text,Bad PV Text,Logical Name,IP Address1,IP
192.168.0.7,0.0.0.0,0.0.0.0,0.0.0.0
Address2,IP Address3,IP Address4
Header meaning Node
Configuration(“Node”),NodeNum,NCTLSLOT,NFASTCTL,NPVSL
OT,NFASTPV,NLOGSLOT,NFASTLOG,NDCSLOT,NFASTDC,NP Node,7,64,0,64,0,32,0,160,0,64,0,8192
MSLOT,NFASTPM,NNUMERIC,NFBSLOT,SEQPROC,SCANRATE ,256,1_PU,REG1LOG1,0,FIELDBUS_
Node Conf
,LGCDCTSL,IOSUBTYP(1),PSOPMNUM(1),PSIPMNUM(1),WOF BOARD1,0,0,0,0,3,MNET10_
FSET(1),BOFFSET(1),OPCHTIM(1)IOSUBTYP(2),PSOPMNUM(2 BOARD2,0,0,0,0,3,DEO_HAS,INTRACK
),PSIPMNUM(2),WOFFSET(2),BOFFSET(2),OPCHTIM(2),ACKST
OPT,DCTRACK
Header meaning UNIT definition(“Unit”), NodeNum,UnitNo,UnitI
D,Descriptor,...
Unit Unit,7,1, “U1”,“Unit1”
Unit information used in this node is output with the following sets.
UnitNo,UnitID,Descriptor
Header meaning BOXUNIT(“BoxUnit”),NodeNum,BOXUNIT(1),..
BoxUnit,7,“U1”,...,“--”
.,BOXUNIT(100)
Unit Conf
Header meaning ALENBST(“Alarm”),NodeNum,ALENBST(1),...
Alarm,7,ENABLE,...,ENABLE
ALENBST(100)
Header meaning IOM Configuration(“IOM”),NodeNum,Module#,
IOM CONF I/O Sub No.,PLC No.,Segment No.,IOMType,Start No.,IOMRate,IO IOM,7,1,HLAI,1,1,“”,“”,0,DEPENDS
MCYCLE,IOMTMOUT(Sec),IOREDOPT
Header meaning FB Point Configuration(“FB”),NodeNum,Slot
FB Point FB,7,1,“FB001”,“U1”,1SEC,“”
Num,Tag Name,Unit ID,ExecRate,Description

− 373 −
Appendix A. The setting parameter of the node

A.8 Case of PC4 [R411 or later]

A.8.1 [Network Conf1] Page

Table A-51.

Parameter Description Range of Value

NODENUM Define the node number Integers 1 to 126
NODETYP Define the node type PC4
Define the status descriptor that is displayed when a Digital
Character string having 8 charac-
MOVPVTXT Composite Point is undergoing a status change (moving from one
ters or less
state to another) or i s at an intermediate point between two states
Define the status descriptor that is displayed when the status of a Character string having 8 charac-
BADPVTXT
Digital Composite Point is “Uncertain” or “Bad” ters or less

A.8.2 [Network Conf3] Page

Table A-52.

Parameter Description Range of Value

Define the Logical Name of a node
Logical Name Logical Name is set automatically when you change node number or Up to 40 character string
node type
Define the IP address of a primary
You cannot set “192.168.254.*”
Primary Ethernet A In addition, the fourth octet of the IP address becomes same as node
and “192.168.255.*”
number
Primary Ethernet B Set automatically in the case of network redundancy ----
Secondary Ethernet A Set automatically in the case of node redundancy ----
Set automatically in the case of network redundancy and node re-
Secondary Ethernet B ----
dundancy
ON
Network Redundancy Set network redundancy
OFF
Set node redundancy.
[Note]
In the case of XPC, be sure to select node redundancy when config-
uring real DOPC II hardware.
It is possible to set node non-redundancy for the function simulator,
ON
Node Redundancy but, when it is to be replaced with real hardware, be sure to change
OFF
the configuration to node redundancy. If the configuration i s made
in node non-redundancy, the status of each module is not displayed
correctly on the detailed controller status screen, causing trouble in
maintenance work.
In the case of DOPC III, please match it with real setting.

− 374 −
 A.8 Case of PC4 [R411 or later]

A.8.3 [Node Conf1] Page

Table A-53.

Parameter Description Range of Value

NCTLSLOT Define the number of slots of an adjustment control point. Integers 0 to 640
NFASTCTL Define the number of fast scan slots of an adjustment control point. Integers 0 to NCTLSLOT
NPVSLOT Define the number of slots of an adjustment PV point. Integers 0 to 320
NFASTPV Define the number of fast scan slots of an adjustment PV point. Integers 0 to NPVSLOT
NLOGSLOT Define the number of slots of a logic point. Integers 0 to 320
NFASTLOG Define the number of fast scan slots of a logic point. Integers 0 to NLOGSLOT
NDCSLOT Define the number of slots of a digital composite point. Integers 0 to 1024
NFASTDC Define the number of fast scan slots of a digital composite point. Integers 0 to NDCSLOT
NPMSLOT Define the number of slots of a process module point. Integers 0 to 572
NFASTPM Define the number of fast scan slots of a process module point. Integers 0 to NPMSLOT
NNUMERIC Define the number of slots of a numeric value variable point. Integers 0 to 8192
NNMARRAY Define the number of slots of a numeric array point. Integers 0 to 240
NSTRING Define the number of slots of a string point. Integers 0 to 128
NTIME Define the number of slots of a datetime point. Integers 0 to 128
NFBSLOT Define the number of slots of a function block point. Integers 0 to 511

− 375 −
Appendix A. The setting parameter of the node

A.8.4 [Node Conf2] Page

Table A-54.

Parameter Description Range of Value

Define the statement capacity that can be processed at a process
module data point 1_PU
SEQPROC
“1_PU” : 10 statements can be processed in 1 pre-emption 2_PU
“2_PU” : 20 statements can be processed in 1 pre-emption
RSTRTTIM Define the start-up time for when the auto restart function is used Integers 0 to 30
NULL
REG1LOG1
REG1LOG2
REG1LOG5
REG1LOG10
SCANRATE Define the processing cycle at each data point REG2LOG2
REG2LOG5
REG2LOG10
REG5LOG5
REG5LOG10
REG10LOG10
AUTO
SCHDTYPE Define scheduling type of IOMCYCLE.
IOMAN
PKGOPT It cannot be changed ----
Define the I/O type
For X-Bus, refer to [X-bus Input/Output Equipment Hardware X-Bus:1Mbps
NEWIOUSE
Manual] (MS2-SYS100-3005) and refer to [FX-bus Input/Output FX-Bus:5Mbps
Equipment Hardware Manual] (MS2-SYS100-3004) for FX-Bus
125ms
DOPLSPD Define the DO (Digital Output) resolution
25ms
5Sec
PIUOTDPD Define the LMUX disconnect detection time
3Sec
Configuration whether the functional is limited by LMUX PV
change
OFF
LMUXPVLM [Note]
ON
LMUXPVLM can set “ON” only in the case of NEWIOUSE =
“X-Bus:1Mbps”
Defines unacknowledged return-to-normal alarm on ACKSTAT.
DEO_HAS
ACKSTOPT DEO_HAS:Treat as no alarm
APS
APS:Treat as unacknowledged alarm
Specify initial value during DC point initialization.
INTRACK
DCTRACK INTRACK:Input value is initial value.
OUTTRACK
OUTTRACK:Output value is initial value.
This is a ship-only parameter
Define “NONE”,“MASTER”(Master Node), or “SLAVE”(Slave Node)
(When use a function)
for the inboard watch. For other than an inboard watch, always set
NONE
SHPCLKMS to “NONE”
MASTER
[Note]
SLAVE
This can be changed by setting the value of EnableSHPCLKMS in the
[Browser] section of the rtcedit.ini file to “TRUE”

− 376 −
 A.8 Case of PC4 [R411 or later]

A.8.5 [Unit Conf1-5] Page

Table A-55.

Parameter Description Range of Value

Choose a unit ID already set on the [Unit ID] page in the [System
BOXUNIT(1)-(100) Registered Unit ID
Definition] dialog box
ENABLE
ALENBST(1)-(100) Define the alarm enable status of a unit DISABLE
INHIBIT

− 377 −
Appendix A. The setting parameter of the node

A.8.6 [IOM Conf1-12] Page

Table A-56.

IOMType Module# FileA# CardA# IOMRate FailOpt IOREDOPT FileB# CardB# IOMCYCLE
1SEC
500MS
NONREDUN
HLAI 1 - 120 1-8 1 - 12 200MS UNPOWER (*4) (*4) (*5)
REDUN
100MS
DEPENDS
HMUX(*1) 1 - 120 1-8 1 - 12 1SEC UNPOWER NONREDUN 0 0 (*5)
LMUX(*1) 1 - 120 1-8 1 - 12 1SEC UNPOWER NONREDUN 0 0 (*5)
RMUX(*1) 1 - 120 1-8 1 - 12 1SEC UNPOWER NONREDUN 0 0 (*5)
TCAI(*2) 1 - 120 1-8 1 - 11 1SEC UNPOWER NONREDUN 0 0 (*5)
RTDAI(*2) 1 - 120 1-8 1 - 11 1SEC UNPOWER NONREDUN 0 0 (*5)
1SEC
500MS
NONREDUN
PI 1 - 120 1-8 1 - 16 200MS UNPOWER (*4) (*4) (*5)
REDUN
100MS
DEPENDS
U N P O W E R NONREDUN
AO16 1 - 120 1-8 1 - 16 (*3) (*4) (*4) (*5)
HOLD REDUN
1SEC
500MS
NONREDUN
DI 1 - 120 1-8 1 - 16 200MS UNPOWER (*4) (*4) (*5)
REDUN
100MS
DEPENDS
1SEC
500MS
DISOE(*2) 1 - 120 1-8 1 - 16 200MS UNPOWER NONREDUN 0 0 (*5)
100MS
DEPENDS
1SEC
500MS
UNPOWER
DO 1 - 120 1-8 1 - 16 200MS NONREDUN 0 0 (*5)
HOLD
100MS
DEPENDS
1SEC
500MS
DO32 1 - 120 1-8 1 - 16 200MS NONREDUN 0 0 (*5)
100MS
DEPENDS
0_2_4_6_8
STIM 1-8 1-8 1 - 16 1SEC UNPOWER NONREDUN 0 0 1_3_5_7_9
AUTO
ALL
ESIM(*2) 1-8 1-8 1 - 16 1SEC UNPOWER NONREDUN 0 0
AUTO

*1 IOMType can set “HMUX”, “LMUX”, “RMUX” only in the case of NEWIOUSE = “X-Bus:1Mbps”.
When setting up “HMUX”, “LMUX” and “RMUX”, they require master “HLAI” that has same
File#, smaller Card# and smaller module number.
*2 IOMType can set “TCAI”, “RTDAI”, “DISOE”, “ESIM” only in the case of NEWIOUSE =
“FX-Bus:5Mbps”.

− 378 −
 A.8 Case of PC4 [R411 or later]

*3 IOMRate of “AO16” is different in an optional item by NEWIOUSE.

X-Bus:1Mbps → 1SEC, 500MS, 200MS
→ 1SEC, 500MS, 200MS, 100MS, DEPENDS
FX-Bus:5Mbps
*4 Set automatically in the case of IOREDOPT = “REDUN”. (FileB# = FileA#, CardB# = CardA#+1).
In order to set “REDUN” as IOREDOPT, CardA# needs to be odd.
*5 A range of IOMCYLE depends on IOMRate and Scanrate. For more information, please refer
to [Parameter Reference Manual](MS2-HDS900-6001).

Note Card#15,16 of File#6,7 and Card#16 of File#8 cannot be set up in PC4.

Note When you use distributed I/O, the File numbers are equivalent to the block ad-
dresses of distributed I/O, and the Card numbers are equivalent to base addresses.
File numbers (1 to 8) : Dip switch BLK of block address (0 to 7)
Card numbers (1 to 16) : Dip switch BASE of base address (0 to 15)
For details about how to set the X-bus addresses of distributed I/O by dip switches
on the module base, refer to [Harmonas-DEO DEO Process Controller Installation
Manual](for distributed I/O Module)(MS2-DEO200-3003) or the [Harmonas-DEO
DEO Process Controller II Installation Manual](MS2-DEO200-3005).

Note To use high-level input of signal unit I/O, set the module type to “HLAI”.
To use analog output of signal unit I/O, set the module type to “AO16”.

Note Please select “HLAI” when using an analog input of SIO II.
Sensor type and range of temperature are configured on Signal Unit I/O-II(SIO II)
Communicator when using SIO II TC input units(HD-STCU50C) or SIO II RTD input
units(HD-SRTU50C).
Please set PVEUHI and PVEULO to same values which are set on SIO II Communicator.

− 379 −
Appendix A. The setting parameter of the node

A.8.7 CSV format for import/export

The CSV format for import / export is as follows.
A line beginning with ‘#’ is considered as a comment line and is not a target of the import
process.

Table A-57.

Line The CSV format for import/export Example

Header meaning Network Configuration (“Nwk”),,NodeNu
m,NodeType,Moving PV Text,Bad PV Text,Logical Name,IP
Address1,Network Redun,Node Redun Nwk,,3,XPC,“MOVING”,“BAD”,“
Network Conf
XPC003”,192.168.0.3,OFF,OFF
[Note]
Network Redun and Node Redun sets it in “ON” or “OFF”.
Header meaning Node
Configuration(“Node”),NodeNum,NCTLSLOT,NFASTCTL,NPVSL
OT,NFASTPV,NLOGSLOT,NFASTLOG,NDCSLOT,NFASTDC,NP
MSLOT,NFASTPM,NNUMERIC,NFBSLOT,SEQPROC,RSTRTTIM
,SCANRATE,NEWIOUSE,DOPLSPD,PIUOTDPD,SHPCLKMS,LM
UXPVLM,ACKSTOPT,DCTRACK,SCHDTYPE,NSTRING,NTIME
,NNMARRAY

[Note]
Specify values of the item NEWIOUSE, DOPLSPD and PIUOTDPD Node,3,64,0,64,0,32,0,160,0,64,0,
as follows: 8192,256,1_PU,3,REG1LOG1,
Node Conf
ON,OFF,OFF,NONE,OFF,DEO_
Value on RTC CSV file HAS,INTRACK,IOMAN,128,0,0
X-Bus:1Mbps OFF
NEWIOUSE
FX-Bus:5Mbps ON
125ms OFF
DOPLSPD
25ms ON
5Sec OFF
PIUOTDPD
3Sec ON

Header meaning UNIT definition(“Unit”), NodeNum,UnitNo,UnitI

D,Descriptor,...
Unit Unit,3,1,“U1”,“Unit1”
Unit information used in this node is output with the following sets.
UnitNo,UnitID,Descriptor
Header meaning BOXUNIT(“BoxUnit”),NodeNum,BOXUNIT(1),..
BoxUnit,3,“U1”,...,“--”
.,BOXUNIT(100)
Unit Conf
Header meaning ALENBST(“Alarm”),NodeNum,ALENBST(1),...
Alarm,3,ENABLE,...,ENABLE
ALENBST(100)
Header meaning IOM
Configuration(“IOM”),NodeNum,Module#,FileA#,CardA#,IOMTyp
e,IOMRate,Fail Opt,FREQ6050,IOREDOPT,FileB#,CardB#,segID,FL
IOM,3,1,1,1,HLAI,DEPENDS,U
MType,IOMCYCLE
IOM CONF NPOWER,SIXTYHZ,NONRED
UN,0,0,0,NONE,2
[Note]
Because FREQ6050, segID, FLMType is not used now, the setting is
ignored.
Header meaning FB Point Configuration(“FB”),NodeNum,Slot
FB Point FB,3,1,“FB001”,“U1”,1SEC,“”
Num,Tag Name,Unit ID,ExecRate,Description

− 380 −
Document Number: MS2-HDS400-2002 [Rel.400/411/412]

Document Name: Harmonas-DEO

RTC User's Guide

Date: November, 2011

November, 2014 (Rev.3)
Edited by:
Azbil Corporation