Edgecross Basic Software for Windows
User's Manual
ECP-BS1-W (Edgecross Basic Software for Windows)

ECD-MA1-0001-15-EN

SAFETY PRECAUTIONS(Read these precautions before using this product.)
Before using this software, please read this manual carefully and pay full attention to safety to handle it correctly.
The precautions given in this manual are concerned with this software only.
For details on Edgecross supported products (hardware and software), refer to their respective manuals.
In this manual, the safety precautions are classified into two levels: "WARNING" and "CAUTION".

WARNING

Indicates that incorrect handling may cause hazardous conditions, resulting indeath or severe injury.

CAUTION

Indicates that incorrect handling may cause hazardous conditions, resulting inminor or moderate injury or property damage.

Under some circumstances, failure to observe the precautions given under "CAUTION" may lead to serious

consequences.
Observe the precautions of both levels because they are important for personal and system safety.
Make sure that the end users read this manual and then keep the manual in a safe place for future reference.

[Design Precautions]
WARNING To perform an operation, such as data change or operating status change, to running devices, such asa programmable controller, servo, robot, or server, from an industrial PC equipped with this product,configure an interlock circuit outside of the devices so that the entire system always operates to thesafety side. Additionally, read this manual carefully and ensure the safety before operations.
Especially, in the above mentioned operations that are performed from external devices throughnetwork, any problems on devices may not be dealt with promptly due to an abnormal data
communication.
 Configure a safety circuit outside of an industrial PC equipped with this product so that the entire
system operates to the safely side even when a fault occurs in the PC.
Failure to do so may result in an accident due to an incorrect output or malfunction.

[Design Precautions]
CAUTION Do not perform the operation that forcibly turns the industrial PC equipped with this product OFF.
Otherwise, the data will be undefined and resetting and re-registering data will be required.
Additionally, doing so may cause the malfunction of this product.

[Security Precautions]
WARNING To maintain the security (confidentiality, integrity, and availability) of access target devices and thesystem against unauthorized access, denial-of-service (DoS) attacks, computer viruses, and othercyberattacks from external devices via the network, take appropriate measures such as firewalls,
virtual private networks (VPNs), and antivirus solutions.

1[Startup and Maintenance Precautions]
WARNING When performing the following operation, configure the system to ensure that Real-time Flow
Manager will operate safely.
Changing the operating status (RUN/STOP) of each process flow of Real-time Flow Manager[Operating Precautions]
CAUTION The diagnostic results of the data diagnostic function are not always guaranteed. When performing
operations that affect the diagnostic target device by using device instructions or executing a program,
ensure the safety before operations.

2CONDITIONS OF USE FOR THIS SOFTWARE(1) For using this software, even if a malfunction occurs in the software, it is an application that does not result in serious
accidents, and backup and fail-safe functions are implemented systematically outside the device in case of malfunction
What you have is the condition of use.
(2) The Edgecross Consortium assumes no responsibility for this software and the quality, performance, safety concerning
products that use this software (including but not limited to non-performance of the main obligation, defect liability,
quality assurance responsibility, quality assurance responsibility, tort liability, and product liability).
(3) The Edgecross Consortium shall have no responsibility or liability for any problems involving this software and system
trouble caused by DoS attacks, unauthorized access, computer viruses, and other cyberattacks.

USE OF THIS SOFTWARE OVERSEAS
When using this software overseas, such as exporting and taking-out overseas, or disclosing to non-residents in Japan, therestrictions by the Foreign Exchange and Foreign Trade Control Law and the applicable export control laws and regulations ofother countries, such as the Export Administration Regulations in the United States, must be complied. In addition, various
procedures may be required. Please consult the Edgecross Consortium for more information.

3

INTRODUCTION
Thank you for using Edgecross Basic Software. This manual describes the method for using this software.
Before using Edgecross Basic Software, please read this manual carefully, and develop familiarity with the functions andperformance of this product to handle correctly.
Note that the menu names and operating procedures may differ depending on an operating system in use and its version.
When reading this manual, replace the names and procedures with the applicable ones as necessary.

4

CONTENTS
SAFETY PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
CONDITIONS OF USE FOR THIS SOFTWARE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
USE OF THIS SOFTWARE OVERSEAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
RELEVANT MANUALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

CHAPTER 1
1.1
1.2

Edgecross Basic Software

13

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Supported Specification Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Data collector specification version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Edge application I/F specification version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Plug-in I/F specification version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

CONTENTSTERMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

IT gateway specification version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

CHAPTER 2
2.1

SPECIFICATIONS

16

Functional Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Real-time Flow Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Management Shell. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
CSV File Data collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Management Shell Data collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Dummy Data collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

CHAPTER 3

FUNCTION LIST

27

3.1

Function List of Real-time Flow Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

3.2

Function List of Real-time Flow Designer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

3.3

Function List of Management Shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

3.4

Function List of CSV File Data collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

3.5

Function List of Management Shell Data collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

3.6

Function List of Dummy Data collector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

CHAPTER 4

PROCEDURES BEFORE OPERATION

30

CHAPTER 5

Real-time Flow Manager

32

5.1

Operational Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Operating status of a process flow and process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Consideration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

5.2

Data Collection Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

5.3

Data Modification Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Adding constants and fixed character strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Data extraction function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Character string data modification function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
5.4

Data Diagnosis Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
MQTT cooperation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
File cooperation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

5.5

Feedback Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Device instruction feedback function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Program execution feedback function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

5

Feedback deterrence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
5.6

Data Storing Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
File saving function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
DB saving function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

5.7

Data Distribution Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
MQTT distribution function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
IT gateway distribution function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

5.8

Event History Automatic Output Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Event history file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Operation check file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

5.9

Command Line Interface Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Version specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Operational specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Execution methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Option specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Option details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

CHAPTER 6
6.1

Real-time Flow Designer

107

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Home screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Process flow setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Common setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Data collector list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
IT gateway list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Location of use search result screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Common operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

6.2

Access Target Device Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Access target device setting list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Data collector selection screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Access target device setting screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

6.3

IT Gateway Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
IT gateway setting list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
IT gateway selection screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
IT gateway setting screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

6.4

Data Logging Flow Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Data logging flow setting list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Data logging flow setting screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

6.5

Data Diagnosis Flow Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Data diagnosis flow setting list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Data diagnosis flow setting screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

6.6

Move of a Process Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

6.7

Data Collection Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Collection data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

6.8

Data Storing Setting (File Saving) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Executable form. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
File format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Output data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Output option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Saved file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

6

6.9

Data Storing Setting (DB Saving). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Executable form. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Output data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Access table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Definition output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

6.10

Data Distribution Setting (MQTT). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Executable form. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Output data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Definition output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

6.11

Data Distribution Setting (IT Gateway) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Executable form. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Destination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Output data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Definition output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

CONTENTS

Destination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
6.12

Data Extraction Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

6.13

Character String Data Modification Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

6.14

Data Modification Plug-in Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

6.15

Edge Application Diagnosis (MQTT) Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Destination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Output data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Definition output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Response data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

6.16

Edge Application Diagnosis (File) Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
File format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Output data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Output option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Saved file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Response data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

6.17

Data Diagnosis Plug-in Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

6.18

Post-Diagnosis Feedback Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Execution condition setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Device instruction feedback setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Program execution feedback setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

CHAPTER 7

Management Shell

191

7.1

Data Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

7.2

Management Shell Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Behavior of data model import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Duplicating a data model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Target device setting import screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Import error list screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Location of use search result screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205"Check Number of Model Configurations" screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Monitoring and changing current values of data tag resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Option setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Access target device setting batch replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

7.3

Access Target Device Setting Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

7

Access target device setting list screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Data collector selection screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Access target device setting screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
7.4

Component Tree Edit Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

7.5

Resource List Edit Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

7.6

OPC UA Connection Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

7.7

IT Gateway Cooperation Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Procedure for setting an IT gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
IT gateway setting list screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
IT gateway selection screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
IT gateway setting screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

7.8

One-shot Collection Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Operational specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Setting procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

7.9

Event History Automatic Output Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Event history file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Operation check file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Event history automatic output setting screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292

CHAPTER 8
8.1

CSV File Data collector

294

Data Collection Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
Operational specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

8.2

Data Reading Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Operational specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

8.3

Detailed Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Specifications of a monitoring target file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Specifications of a collection data definition file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Header information of a collection data definition file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302

8.4

Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
Use in Real-time Flow Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
Use in Management Shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308

8.5

Procedures before Using CSV File Data collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Use in Real-time Flow Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Use in Management Shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309

8.6

Data Collection Setting (CSV File Data collector) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310

8.7

Access Target Device Setting (CSV File Data collector) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311

8.8

Location Setting (CSV File Data collector) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
Setting in the location setting screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
Entering directly. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

CHAPTER 9

Management Shell Data collector

9.1

Operational Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316

9.2

Data Collection Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

9.3

Setting Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319

9.4

Data Collection Setting (Management Shell Data collector) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324

9.5

Access Target Device Setting (Management Shell Data collector). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325

9.6

Location Setting (Management Shell Data collector). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326

CHAPTER 10 Dummy Data collector

8

314

327

10.1

Data Reading Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327

10.2

Parameter Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327

CHAPTER 11 TROUBLESHOOTING
11.1

329

Checking Methods for Error Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
Error code system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330

11.2

Checking the Status of a Process Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Real-time Flow Manager diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Checking the Status of Management Shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
OPC UA diagnosis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Displaying error information in a list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343

11.4

Troubleshooting by Symptom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Real-time Flow Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Real-time Flow Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
Management Shell. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
CSV File Data collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363

CONTENTS

11.3

Management Shell Data collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
11.5

Error Code List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366

11.6

Event Code List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422

11.7

Code List for Data Model Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424

11.8

Error Code List for the One-shot Collection Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429

11.9

Exit Code List for the Command Line Interface Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432

APPENDIX

433

Appendix 1 Real-time Flow Manager Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Real-time Flow Manager status list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
Real-time Flow Manager status details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
Real-time Flow Manager status initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
Appendix 2 Available Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
Real-time Flow Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
Management Shell Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
Appendix 3 MQTT Broker Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
Considerations for setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
Setup procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
Installing OpenSSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
Installing Eclipse Mosquitto . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
Installing Pthread. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508
Starting Eclipse Mosquitto . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
Setting access control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
Setting a port number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
Setting communication encryption. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
Configuring the settings for connection from another industrial PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
Appendix 4 Database Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
Consideration for setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
Setup procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
Installing PostgreSQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
Connecting to PostgreSQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
Creating an account for PostgreSQL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
Installing the ODBC driver for PostgreSQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
ODBC setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536

9Creating a table by using a DDL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
Setting a privilege to a table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
Setup procedure using a batch file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
Appendix 5 Data Used in Edgecross Basic Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
Data type and value range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
Values that can be entered in the screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
Available characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
Value after changing the data type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
Data assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
Data substitution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
Data comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550
Data missing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
Appendix 6 Using a Remote Shared Folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
Using a shared folder with specifying a user account in Edgecross Basic Software. . . . . . . . . . . . . . . . . . . . . 553
Using a shared folder without specifying a user account in Edgecross Basic Software . . . . . . . . . . . . . . . . . . 556
Appendix 7 Allowing Communication Connections between Industrial PCs . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
Cases and settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
Procedure for adding a rule for Windows Defender Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
Appendix 8 Processing Performance and Processing Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567
Real-time Flow Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567
Management Shell. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588
Management Shell Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
Management Shell Data collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597
Appendix 9 Software Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599
Software information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599
Appendix 10Using a Setting File in a Different Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626
Real-time Flow Designer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626
Management Shell Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628
Appendix 11 Added and Changed Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629

INDEX

631

REVISIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .634
USER REGISTRATION REQUEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .635
TRADEMARKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .635
COPYRIGHTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .635

10

RELEVANT MANUALSManual name [manual number]

Description

Available form

Edgecross Basic Software for Windows User's
Manual[ECD-MA1-0001] (this manual)Specifications, procedure before operation, functions, and troubleshooting of
Edgecross Basic Software

PDF

11

TERMS
Unless otherwise specified, this manual uses the following terms.

12

Term

Description

Business system

A system that supports business management such as sales management and production management

Cloud

A form in which the user (usually company) does not manage IT systems but use various IT resources provided over theInternet on demand

Data collection

Processing to collect data to be diagnosed or analyzed

Data collector

A software component that collects data in production sites through each network. It is provided by vendors for each
network and connection target devices.

Data diagnosis

Processing to diagnose if collected data matches preset conditions

Data diagnosis plug-in

A plug-in for data diagnosis

Data model management

A function that abstracts devices, equipment, and lines in the production site and hierarchically manages them

Data modification

Processing to modify collected data into a form suitable for analysis and diagnosis.
Further modifications can also be made to the data modified once.

Data modification plug-in

A plug-in for data modification

Device instruction feedback

A function that updates data in a connected device via a data collector

Edge application

Software that performs various processing for data utilization in production sites using the functions provided by
Edgecross in the edge computing area

Edge computing

An information processing method and area, for not only collecting and analyzing data in production sites in real-time,and feed backing the data, but summarizing the production site data and sharing information with IT systems efficiently
with the hardware and software in production sites

EdgecrossA software platform that implements specifications and concepts for realizing manufacturing solutions by the FA-IT
collaboration centering on the edge computing

Edgecross Basic Software

The name of the software product that implements the Edgecross function

Feedback

Processing to report a detection result when diagnosed data matches a condition

Industrial PC

A PC specialized for industrial use with features such as high reliability, environmental resistance, and long-term supply

IT gateway

A software component that communicates with external devices such as IT systems to utilize data in production sites. It
is provided by vendors for communication destination external devices such as IT systems.

IT system

An area where business systems and applications on premise or in the cloud operate

Management Shell

The name of the Windows version product that implements the data model management function

Management Shell Explorer

Software that sets and references data models managed by Management Shell

MQTT

An abbreviation for MQ Telemetry Transport.
MQ Telemetry Transport is a lightweight message communication protocol using TCP/IP, and the standard is published
as an open protocol.

MQTT broker

An application that acts as an intermediary between applications that distribute messages and ones that receive themessages by using MQTT

N/AAn abbreviation for Not Available.
It is displayed if a value such as a current value cannot be acquired when monitoring the current values of data tag
resources.

Node

Each element created to build a hierarchical structure in Management Shell Explorer

On-premise

A form in which IT systems are introduced, installed, and operated in the facility managed by the user (usually company)

OPC

An interface standard for linking software that controls devices in factories

OPC UAAn abbreviation for OPC Unified Architecture.
Platform independent service-oriented architecture that integrates all the functionality of each OPC Classic specification
into an extensible framework.

Plug-in

Software that extends the real-time data processing function

Process

A generic term for the processing of data collection, data modification, data diagnosis, and feedback that compose aprocess flow

Process flow

An execution unit of sequential processing performed by Real-time Flow Manager, consisting of data collection, data
modification, data diagnosis, and feedback

Process flow setting

Settings of the execution contents and execution order of the processing of data collection, data modification, data
diagnosis, and feedback that compose a process flow

Real-time data processing

A function that realizes the real-time diagnosis and feedback of the production site data

Real-time Flow Designer

The name of the software component that performs operation setting of Real-time Flow Manager

Real-time Flow Manager

The name of the Windows version software component that implements the real-time data processing

Real-time Flow Manager Parameter

A generic term for settings required to run 'processes'

1

Edgecross Basic Software

1

Edgecross Basic Software is software that implements the Edgecross function.

1.1

Overview

Edgecross Basic Software consists of the software described in the following table.
By cooperating with edge applications, data in production sites can be analyzed and diagnosed. (Page 13 Edgeapplication)
In addition, data can be exchanged with on-premises or cloud IT systems by cooperating with IT gateways.
(Page 13 IT gateway)
SoftwareDescription

Real-time Flow Manager

Software that implements the functions to diagnose data in production sites in real time and provide feedback.
Data in connected equipment, devices, or lines can be collected by using a data collector, and modified and analyzed.
(Page 13 Data collector)
In addition, the functions can be extended by using a plug-in. (Page 13 Plug-in)

Real-time Flow Designer

Software that implements the functions to create, save, and display various settings required for the operation of Realtime Flow Manager, start or stop its operation, and perform a diagnosis.

Management Shell

Software that models data in equipment, devices, or lines in production sites, manages it in a hierarchical structure,and runs in the background on Windows as a Windows service.
Data in connected equipment, devices, or lines can be read and written by using a data collector. (Page 13 Data
collector)
In addition, data models managed by Management Shell can be set and referenced by using Management Shell
Explorer. (Page 193 Management Shell Explorer)

Edge application
This is software for analyzing and diagnosing data in production sites by utilizing the functions provided by Edgecross Basic
Software.
For details, refer to the manual for an edge application used.

IT gateway
This is software for communicating with external devices such as IT systems to utilize data in production sites.
For details, refer to the manual for an IT gateway used.

Data collector
This is software for collecting data in production sites via a network.
The following data collectors are pre-installed in Edgecross Basic Software.
• CSV File Data collector (Page 294 CSV File Data collector)• Management Shell Data collector (Page 314 Management Shell Data collector)• Dummy Data collector (Page 327 Dummy Data collector)
Note that they cannot be uninstalled.
For details on other data collectors, refer to the manual for a data collector used.

Plug-inThis is software for extending the functions of Real-time Flow Manager.
It can be used for data modification and data diagnosis processes.
For details, refer to the manual for a plug-in used.

1 Edgecross Basic Software
1.1 Overview

13

1.2

Supported Specification Versions

In Edgecross specifications, the specifications of various I/Fs for data exchange between Edgecross Basic Software and eachpiece of software*1 are defined, and I/Fs are implemented in Edgecross Basic Software and each piece of software.
Each I/F has its own version. If a version of Edgecross Basic Software does not support a version of software, they may not
run properly.
For the versions of Edgecross Basic Software supporting each piece of software, contact the developer of each piece ofsoftware.
*1

14

Refers to data collectors, edge applications, plug-ins, and IT gateways.

1 Edgecross Basic Software
1.2 Supported Specification Versions

Data collector specification version
1

The following table shows the data collector specification version supported by the Edgecross Basic Software version.
For the data collector specification version of each data collector, contact the developer of each data collector.
Edgecross Basic Software version

Data collector specification version

1.00 or later

1.00

Edge application I/F specification version
The following table shows the specification versions of an edge application I/F supported by each of the Edgecross Basic
Software versions.
For the specification version of each edge application, contact the developer of each edge application.
Edgecross
Basic
Softwareversion

1.00

Edge application I/F specification version
Model access
I/F

Data access I/
F

Historical data access I/F

Real-timedata
publishing I/F

Real-time data diagnosis I/F

OPC UAOPC UA

DB

File

MQTT

MQTT

File



1.00

1.0

1.00

1.00

1.0

1.01
1.00*1

1.10

*1
*2

*2

1.01

1.03*2

1.02*21.00 *1
1.01 *2

1.20, 1.21
1.22 or later

1.01*2*2

1.01

Cannot be used in combination with Edgecross Basic Software with version 1.00 or 1.01.
Can be used in combination with Edgecross Basic Software with version earlier than a supported one. However, the functions added ina version later than one used cannot be used.

Plug-in I/F specification version
The following table shows the specification version of a plug-in I/F supported by the Edgecross Basic Software version.
For the specification version of each plug-in, contact the developer of each plug-in.
Edgecross Basic Software version

Plug-in I/F specification version

1.00 or later

1.00

IT gateway specification version
The following table shows the specification versions of an IT gateway supported by each of the Edgecross Basic Software
versions.
For the IT gateway specification version of each IT gateway, contact the developer of each IT gateway.
Edgecross Basic
Software version

IT gateway specification version
Model access I/F-G

Data access I/F-G

Real-time data publishing
I/F-G

Historical data file access
I/F

1.10 or earlier









1.20 or later

1.00

1.00

1.00

1.00

1 Edgecross Basic Software
1.2 Supported Specification Versions

15

2

SPECIFICATIONSThis chapter shows the specifications of Edgecross Basic Software.

2.1

Functional Specifications

This section shows the functional specifications of Edgecross Basic Software.

Real-time Flow Manager
The following shows the functional specifications of Real-time Flow Manager.

Common items for each function
Item

Specification

Number of units of available data

Up to 256 units

Available data size

Up to 4096 words

Available data size for the entire Real-time Flow Manager

Up to 131072 words

Period managed in Real-time Flow Manager

From the year 2000 to 2079

Data collection function
Item

Specification

Function type
Data collection using a datacollector*1,*2,*3

*1
*2
*3

16

Data collection using a data collector
Function of a data collector used

Data collection function

CSV File Data collector and Management Shell Data collector are pre-installed in Edgecross Basic Software. (Page 294 CSV File
Data collector, Page 314 Management Shell Data collector)
For the specifications of a data collector, refer to the manual for a data collector used.
Up to 32 data collectors can be set in a process flow setting.

2 SPECIFICATIONS
2.1 Functional Specifications

Data modification function
Item

Specification

Function type

• Data extraction• Character string data modification• Data modification plug-in run

Data extraction

Character string data modification

Data modification plug-in run

2

Condition combination type

• AND combination• OR combination

Monitoring target

Data output in a previous process

Comparison condition=, , <, >, , Comparison target• Data output in a previous process• Constant (integer, real number, character string (ASCII), character string(UNICODE))

Number of available conditions

Up to 4 conditions

Modification type

• No processing• Add to the start• Add to the end• Data extraction

Added character string• STRING: 1 to 32 characters• WSTRING: 1 to 16 characters

Start position• STRING: 1 to 32• WSTRING: 1 to 16

End position• STRING: 1 to 32• WSTRING: 1 to 16

Number of plug-ins that can be stored(including data diagnosis plug-ins)

100

Start argument

Up to 127 characters

Data diagnosis function
Item

Specification

Function type• Edge application cooperation (MQTT cooperation)• Edge application cooperation (file cooperation)• Data diagnosis plug-in run

Edge application cooperation(MQTT cooperation)

Edge application cooperation(file cooperation)

Data diagnosis plug-in run

Supported MQTT protocol version

3.1.1

Encryption protocol

TLS1.2QoS

2Client ID of Real-time Flow Manager

Any value can be set.

Client ID of an edge application

Any value can be set.

Topic name• Publishing data topic name: Any value can be set.
• Topic name other than a publishing data topic name: A value starting with
Edgecross is automatically generated.

Target data

Refer to the following:
Page 19 Data storing function

Monitoring target (prefix of a
response data file)

Up to 32 characters

Number of plug-ins that can be stored(including data modification plug-ins)

100

Start argument

Up to 127 characters

2 SPECIFICATIONS
2.1 Functional Specifications

17

Feedback function
Item

Specification

Function type

• Device instruction feedback• Program execution feedback

Number of pieces of feedback that can be provided

Up to 4 pieces per flow

Execution condition*1

Condition combination type

• AND combination• OR combination

Monitoring target

Response data

Comparison condition=, , <, >, , Comparison target• Response data
• Constant (integer, real number, character string (ASCII), character string(UNICODE))

Number of available conditions

Up to 4 conditions

Execution frequency• Always run• Deterrence period specification

Deterrence period• 1 to 60 minutes• 1 to 24 hours

Device instruction feedback

Available data collector*2
Function of a data collector used

Data writing function

Program execution feedback

Execution program path

Up to 127 characters

Program argument

Up to 300 characters

Setting value

Constant

Maximum number of units of data per feedback

*1
*2

18

Refer to the manual for an installed data collector.

Any constant
Up to 32 units

Feedback can also be provided without specifying an execution condition.
In this case, set feedback is always provided once response data is acquired.
Up to 32 data collectors can be set in a process flow setting.

2 SPECIFICATIONS
2.1 Functional Specifications

Data storing function
Item

Specification

Function type

• File saving• DB saving

Type of a process in which data can be saved• Data collection• Data modification• Data diagnosis

Number of functions that can be performed in one flow

Up to two functions including the data distributionfunction

File saving

Number of files that can be saved

Up to 6000 files

File name prefix

Up to 32 characters

File name sequence number

00000001 to FFFFFFFF

Storage destination path length

Up to 205 characters

File type
CSV file

Program execution after saving a
file
DB saving

Comma (,)

Line feed code

CRLF (0x0D, 0x0A)

Character code

• Shift JIS• UTF-8

Extension.csv

Execution program path

Up to 127 characters

Program argument

Up to 127 characters
PostgreSQL version 10.3

Supported standard

SQL99

Number of records that can be stored

Refer to the manual for a database used.

Data source nameASCII (up to 32 characters)

Password

ASCII (up to 32 characters)

Field

*1
*2

CSV file
Delimiter

Database the operation of which has been checked

Table*1

2

Table name

Unicode Basic Multilingual Plane (up to 32
characters)

Number of tables

Refer to the manual for a database used.

*2

Field name

Unicode Basic Multilingual Plane (up to 32
characters)

Number of fields

2 to 257 columns

Data cannot be stored in a same table from multiple processes.
A same name cannot be used in a same table.

Data distribution function
Item

Specification

Function type

• MQTT distribution• IT gateway distribution

Type of a process in which data can be distributed• Data collection• Data modification• Data diagnosis

Number of functions that can be performed in one flow

Up to two functions including the data storing
function

MQTT distribution

Communication specifications

Supported MQTT protocol
version

3.1.1

Encryption protocol

TLS1.2QoS•1•2

Client ID of Real-time Flow
Manager

Any value can be set.

Topic nameAny value can be set.

2 SPECIFICATIONS
2.1 Functional Specifications

19

Management Shell
The following shows the functional specifications of Management Shell.
Item

Specification

Access target device setting function

Component tree edit function

Resource list edit function

OPC UA connection function*1

Maximum number of access target device settings that can be registered

32

Maximum number of characters in a comment

100

Maximum number of components that can be registered

1000

Maximum number of hierarchies of a component that can be set

32

Maximum number of characters in a component name32

Maximum number of characters in a component display name64

Maximum number of resources that can be registered in a component

1000

Maximum number of internal data tag resources (operation) that can beregistered in Management Shell

500

Maximum number of characters in a resource name32

Maximum number of characters in a resource display name64

Specifications of a supported OPC UA server

Refer to the following:
Page 21 OPC UA server
specifications

Maximum number of edge applications that can be connected to Management
Shell

64

Maximum number of subscriptions*2 that can be registered in each edge
application connected to Management Shell

10

Maximum number of monitoring target items*3 that can be registered in each
subscription*2

1000000

Maximum number of monitoring target items that can be registered

1000000

Sampling cycle of a monitoring target item

IT gateway cooperation function*1

One-shot collection function

*1
*2
*3

*4
*5

20

100

Maximum number of characters in a setting name*4,*5

• 100 (millisecond)• 200 (millisecond)• 500 (millisecond)• 1 (second)• 2 (second)• 5 (second)• 60 (second)• 3600 (second)

Maximum number of units of data that can be temporarily accumulated foreach monitoring target item

100

Maximum number of IT gateway settings that can be registered

10

Maximum number of characters in a setting name32

Maximum number of characters in a comment

100

Maximum number of one-shot collection settings that can be registered

32

Maximum number of collection target resources that can be registered in asetting

1000

Surrogate pair characters cannot be used.
Refers to a registration destination for a monitoring target item.
Attribute of a resource (node) registered as a monitoring target in Management Shell from an edge application. (An attribute refers todata included in a node.)
For the nodes and attributes that can be registered as monitoring targets, refer to the following:
Page 22 Nodes and attributes that can be registered as monitoring targets
A difference may occur between a set sampling cycle and an actual polling interval due to the effects of the processing of other softwareand an operating system.
A time stamp is recorded at the time when a current value is acquired from a data collector. Therefore, a difference may occur even intime stamps of monitoring target items for which a same access target device or sampling cycle is set.

2 SPECIFICATIONS
2.1 Functional Specifications

OPC UA server specifications
The following shows the specifications of an OPC UA server supported by Management Shell.

For details on OPC UA specifications, refer to the following:2• opcfoundation.org
Item

Details

Discovery service set

FindServers
GetEndpoints

SecureChannel service set

OpenSecureChannel

Session service set

CreateSession

CloseSecureChannel

ActivateSession
CloseSession
View service set

BrowseBrowseNext
TranslateBrowsePathsToNodeIds

Attribute service set

Read

MonitoredItem service set

CreateMonitoredItems

Write

DeleteMonitoredItems
ModifyMonitoredItems
SetMonitoringMode
SetTriggering
Subscription service set

CreateSubscription
ModifySubscription
SetPublishingMode
PublishRepublish
DeleteSubscriptions

2 SPECIFICATIONS
2.1 Functional Specifications

21

Nodes and attributes that can be registered as monitoring targets
Node

Data tagresourceDescription

Attribute
Name

Content

Node indicating a data tag resource

BrowseName

Data tag resource name

DisplayName

Resource display name

Value

Current value

DataType

Data type in OPC UA specifications*1
For the correspondence between data types in
OPC UA specifications and those in Edgecrossspecifications, refer to the following:Correspondence between data types in OPC
UA specifications and those in Edgecrossspecifications

AccessLevel

Authority to read and write Value attributes of adata tag resource node*2• CurrentRead(1): Read authority only
• CurrentWrite(2): Write authority only
• CurrentRead(3), CurrentWrite(3): Read andwrite authority

UserAccessLevel

DataType

Node indicating the data type of adata tag resource

BrowseName"DataType"*3

DisplayName
Value

Data type in Edgecross specifications (Page
544 Data Used in Edgecross Basic Software)

DataType"UINT16"*3 (data type in OPC UA specifications)

AccessLevel

CurrentRead(1)*3: Read authority only

UserAccessLevel
LengthNode indicating the number ofcharacters in a data tag resource

BrowseName"Length"*3

DisplayName
Value

Number of characters

DataType"STRING"*3 (data type in OPC UA specifications)

AccessLevel

CurrentRead(1)*3: Read authority only

UserAccessLevel
File
resource*4

Node indicating a file resource



FilePath

Node indicating the file path of a fileresource

BrowseName"FilePath"*3

DisplayName
Value

File path

DataType"STRING"*3 (data type in OPC UA specifications)

AccessLevel

CurrentRead(1)*3: Read authority only

UserAccessLevel
Folderresource*5

Node indicating a folder resource

FolderPath

Node indicating the folder path of afolder resource

BrowseName"FolderPath"*3

DisplayName
Value

Folder path

DataType"STRING"*3 (data type in OPC UA specifications)

AccessLevel

CurrentRead(1)*3: Read authority only

UserAccessLevel

*1
*2
*3
*4
*5

22

When acquiring a data type in Edgecross specifications, register a Value attribute of a DataType node as a monitoring target.
Matches the read and write authority defined in a data collector for each location of data tag resources set in Management Shell
Explorer.
A fixed value
A file resource node cannot be registered as a monitoring target but a FilePath node under a file resource node can be registered.
A folder resource node cannot be registered as a monitoring target but a FolderPath node under a folder resource node can beregistered.

2 SPECIFICATIONS
2.1 Functional Specifications

• Correspondence between data types in OPC UA specifications and those in Edgecross specifications
Data type in OPC UA specifications

Data type in Edgecross specifications

BOOL (value: 1)

BOOL (value: 1)

INT16 (value: 4)

INT (value: 2)

UINT16 (value: 5)

UINT (value: 3)

INT32 (value: 6)

DINT (value: 4)

UINT32 (value: 7)

UDINT (value: 5)

INT64 (value: 8)

LINT (value: 6)

UINT64 (value: 9)

ULINT (value: 7)

FLOAT (value: 10)

REAL (value: 8)

DOUBLE (value: 11)

LREAL (value: 9)

STRING (value: 12)

STRING (value: 10)*1

2

WSTRING (value: 11)*1*1

The STRING and WSTRING types are converted into STRING (UTF-8) in OPC UA specifications.

2 SPECIFICATIONS
2.1 Functional Specifications

23

CSV File Data collector
The following table shows the functional specifications of CSV File Data collector.
Item

Specification

Supported function• Data collection function• Data reading function

Data collection function

Data reading function

*1
*2
*3
*4
*5

24

Collection target*1• CSV file (ASCII or shift JIS*2)• Text file

Available data type

• BOOL• UINT• UDINT• ULINT• INT• DINT• LINT• REAL• LREAL• STRING• WSTRING

Number of columns in the data
column*3

Up to 256 columns

Monitoring folder path length*4

Up to 199 characters (including '\' at the end)

Monitoring target file (prefix)

Up to 32 characters

Data reading target• CSV file
• Text file

Available data type

• BOOL*5• UINT• UDINT• ULINT• INT• DINT• LINT• REAL• LREAL• STRING• WSTRING

Number of columns in the data
columnUp to 512 columns

File size

Up to 16384 KB

Monitoring folder path length

Up to 199 characters (including '\' at the end)

Monitoring target file (prefix)

Up to 32 characters

CSV File Data collector runs normally even when deleting a character string in the date and time column of the data name informationrow.
Can be used only for the data name row.
The following column is not included.
Date and time column
The same folder path as the following folder cannot be specified.
Monitoring folder of CSV File Data collector used for data collection in another process flow
When using a character string as an identifier, use the STRING type or WSTRING type data.

2 SPECIFICATIONS
2.1 Functional Specifications

Management Shell Data collector
The following table shows the functional specifications of Management Shell Data collector.
This Data collector is compliant with OPC UA 1.03 and later.
Item
Access target device

Description
Number of connectable devices

1 server per instanceConnectable software

Management Shell only

Supported function
Data collection function

2

Data collection function
Collection interval• 0.5 to 0.9 seconds (in 0.1-second increments)• 1 to 21,600 seconds (in 1-second increments)

Available data type

• BOOL• INT• UINT• DINT• UDINT• LINT• ULINT• REAL• LREAL• WSTRING

2 SPECIFICATIONS
2.1 Functional Specifications

25

Dummy Data collector
The following table shows the functional specifications of Dummy Data collector.
Item

Description

Access target device

Not setSupported function
Data reading function26

2 SPECIFICATIONS
2.1 Functional Specifications

Data reading function
Available data type

• BOOL• INT• UINT• DINT• UDINT• LINT• ULINT• REAL• LREAL• STRING• WSTRING

Location

Any character string can be specified.

3

FUNCTION LIST

This chapter shows the function list of Edgecross Basic Software.

3.1

Function List of Real-time Flow Manager

This section shows the function list of Real-time Flow Manager.
Function

Description

Reference

Data collection function

To collect data in connected equipment, devices, and lines via a datacollector.

Page 36 Data Collection
Function

Data extraction function

To extract data according to a specified condition.

Page 37 Data extraction
function

Character string data
modification function

To modify character string data according to a specified condition.

Page 40 Character string
data modification function

Data modification plugin run function

To run a data modification plug-in.

Manual for a plug-in
usedEdge applicationcooperation function

To distribute data (collected data and modified data) in Real-time Flow
Manager to an edge application, and receive response data from the edge
application.

Page 43 MQTT
cooperation
Page 52 File cooperation

Data diagnosis plug-in
run function

To run a data diagnosis plug-in.

Manual for a plug-in
used

Device instruction
feedback function

To update data in a connected device via a data collector.

Page 55 Device instruction
feedback function

Program execution
feedback function

To run executable programs from a command line.

Page 55 Program
execution feedback
function

File saving function

To save data collected or modified in Real-time Flow Manager, or diagnosis
result data to a file in a format specified in Real-time Flow Designer.

Page 60 File saving
function

DB saving function

To save (INSERT) data collected or modified in Real-time Flow Manager, ordiagnosis result data to a database specified in Real-time Flow Designer.

Page 77 DB saving
function

MQTT distributionfunction

To distribute output of data collection, data modification, and data diagnosis
processes to an edge application by using MQTT.

Page 80 MQTT distributionfunction

IT gateway distributionfunction

To distribute output of data collection, data modification, and data diagnosis
processes to an external device such as an IT system or mobile by using an
IT gateway.

Page 85 IT gateway
distribution function

Event history automatic output function

To automatically output event/error information, which is collected from
Real-time Flow Manager, data collectors used in Real-time Flow Manager,
and IT gateways, to a specified folder in a CSV file format.

Page 86 Event History
Automatic Output Function

Command line interface function

To perform operations of Real-time Flow Manager on a command basis.

Page 92 Command LineInterface Function

Data modification
function

Data diagnosis function

Feedback function

Data storing function

Data distributionfunction

3 FUNCTION LIST
3.1 Function List of Real-time Flow Manager

3

27

3.2

Function List of Real-time Flow Designer

This section shows the function list of Real-time Flow Designer.
Function

Description

Reference

Access target device setting

To select a data collector to use and set an access target device.

Page 124 AccessTarget Device
Setting

IT gateway setting

To select and set an IT gateway to use.

Page 127 IT
Gateway Setting

Data logging flow setting

To configure the setting for a data logging flow.

Page 130 Data
Logging Flow Setting

Data diagnosis flow setting

To configure the setting for a data diagnosis flow.

Page 134 Data
Diagnosis Flow
SettingMove of a process flow

To change the type of a process flow.

Page 138 Move of aProcess Flow

Data collection setting

To configure the setting for collecting data in an access target
device.

Page 139 Data
Collection Setting

Data storing setting (filesaving)To configure the setting for outputting a result of a process in a fileformat.

Page 142 Data
Storing Setting (File
Saving)Data storing setting (DBsaving)To configure the setting for outputting a result of a process to a
database.

Page 152 Data
Storing Setting (DBSaving)Data distribution setting(MQTT)

To configure the setting for distributing a result of a process to anedge application by using MQTT.

Page 158 Data
Distribution Setting(MQTT)

Data distribution setting (ITgateway)

To configure the setting for distributing a result of a process to an
external device such as an IT system by using an IT gateway.

Page 163 Data
Distribution Setting(IT Gateway)

Data extraction setting

To configure the setting for data extraction.

Page 169 Data
Extraction Setting

Character string data modification setting

To configure the setting for character string data modification.

Page 170 Character
String Data
Modification Setting

Data modification plug-in setting

To configure the setting for a data modification plug-in.

Page 172 Data
Modification Plug-in
Setting

Edge application diagnosis(MQTT) setting

To configure the setting for sending a result of a process to anedge application and receiving a diagnosis result from the edge
application by using MQTT.

Page 173 Edge
Application
Diagnosis (MQTT)
Setting

Edge application diagnosis(file) setting

To configure the setting for passing a result of a process to anedge application and acquiring response data from the edge
application in a file format.

Page 178 Edge
Application
Diagnosis (File)
Setting

Data diagnosis plug-in setting

To configure the setting for a data diagnosis plug-in.

Page 184 Data
Diagnosis Plug-in
Setting

Post-diagnosis feedback setting

To configure the setting for feedback provided when a diagnosis
result of data diagnosis is received.

Page 185 PostDiagnosis Feedback
Setting

Real-time Flow Manager diagnosis

To switch and diagnose the operating status of a process flow.

Page 332 Real-time
Flow Manager
diagnosis

Data storing setting

Data distribution setting

Edge application diagnosis
setting28

3 FUNCTION LIST
3.2 Function List of Real-time Flow Designer

3.3

Function List of Management Shell

This section shows the function list of Management Shell.
Function

Description

Reference

Access target device setting function

To select a data collector to use and set an access target device by using
Management Shell Explorer.

Page 220 Access Target
Device Setting Function

Component tree edit function

To edit components or change the hierarchical structure of a component byusing Management Shell Explorer.

Page 224 Component Tree
Edit Function

Resource list edit function

To edit resources managed by a component by using Management Shell
Explorer.

Page 235 Resource List
Edit Function

OPC UA connection function

To enable Management Shell to run as an OPC UA server and provide amodel access I/F and data access I/F for an edge application that is an
OPC UA client.

Page 259 OPC UA
Connection Function

IT gateway cooperation function

To respond to requests for data model reference, data reading, and data
writing from an IT gateway, and perform these operations.

Page 265 IT Gateway
Cooperation Function

One-shot collection function

To collect a value of a data tag resource specified as a collection target(collection target resource) and save it to a file or database when a value ofa data tag resource specified as a monitoring target (monitoring target
resource) changes.

Page 269 One-shotCollection Function

Event history automatic output function

To automatically output event/error information, which is collected fromManagement Shell, data collectors used in Management Shell, and IT
gateways, to a specified folder in a CSV file format.

Page 289 Event History
Automatic Output Function

3.4

3Function List of CSV File Data collector

This section shows the function list of CSV File Data collector.
Function

Description

Reference

Data collection function

To collect data in a device via a monitoring target file.

Page 294 Data Collection
Function

Data reading function

To read data in a device via a monitoring target file.

Page 297 Data Reading
Function

3.5

Function List of Management Shell Data collector

This section shows the function list of Management Shell Data collector.
Function

Description

Reference

Data collection function

To collect data in Management Shell in a fixed cycle set in Real-time Flow
Designer.

Page 317 Data Collection
Function

3.6

Function List of Dummy Data collector

This section shows the function list of Dummy Data collector.
Function

Description

Reference

Data reading function

To read data according to a request from Edgecross Basic Software.

Page 327 Data Reading
Function

3 FUNCTION LIST
3.3 Function List of Management Shell

29

4

PROCEDURES BEFORE OPERATIONThis chapter shows the procedures from start-up to operation of Edgecross Basic Software.

When using Real-time Flow Manager
Operating procedure

1. Install Edgecross Basic Software on an industrial PC.
For the installation procedure and the operating environment of Edgecross Basic Software, refer to the following:
Edgecross Basic Software for Windows Installation Instructions

2. Install the following software on the industrial PC as necessary.
• Data collector• Edge application• IT gateway
For the installation method, refer to the manual for a data collector*1, edge application, or IT gateway*1 to be installed.
*1

When installing it, change the operating statuses of all process flows to STOP and exit Real-time Flow Designer.
For changing the operating status of a process flow, refer to the following:
Page 332 Real-time Flow Manager diagnosis
In addition, select [Management Shell]  [Management Shell Stop] in the menu of Management Shell Explorer to stop Management
Shell.

3. Set a device supporting the data collector as necessary.
For the setting method, refer to the manual for a device used.

4. Set an external device such as an IT system supporting the IT gateway as necessary.
For the setting method, refer to the manual for an external device such as an IT system used.

5. When cooperating with an edge application installed on another industrial PC, make sure that the time is the same
between an environment where Edgecross Basic Software runs and one where the edge application runs, then create aclient certificate for the edge application as necessary.

6. Set parameters in Real-time Flow Designer and apply them to Real-time Flow Manager.
For details on Real-time Flow Designer, refer to the following:
Page 107 Real-time Flow Designer

7. Set the edge application as necessary.
For the setting method, refer to the manual for an edge application used.

8. Change the operating status of a process flow to RUN.
For changing the operating status of a process flow, refer to the following:
Page 333 "Process Flow Start/Stop" screen

Precautions• To change parameters after starting the operation of Real-time Flow Manager, change the operating statuses of all process
flows to STOP once.
• Before installing Edgecross Basic Software, disable the fast startup function. If it is enabled, an industrial PC is not shut
down completely, and Real-time Flow Designer may not run properly when starting the industrial PC after shutdown. For
the procedure for disabling the fast startup function, refer to the following:
Page 114 Procedure for disabling the fast startup function

30

4 PROCEDURES BEFORE OPERATION

When using Management Shell
Operating procedure

1. Install Edgecross Basic Software on an industrial PC.
For the installation procedure and the operating environment of Edgecross Basic Software, refer to the following:
Edgecross Basic Software for Windows Installation Instructions

2. Install the following software on the industrial PC as necessary.
• Data collector• Edge application• IT gateway

4

For the installation method, refer to the manual for a data collector*1, edge application, or IT gateway*1 to be installed.
*1

When installing it, change the operating statuses of all process flows to STOP and exit Real-time Flow Designer.
For changing the operating status of a process flow, refer to the following:
Page 332 Real-time Flow Manager diagnosis
In addition, select [Management Shell]  [Management Shell Stop] in the menu of Management Shell Explorer to stop Management
Shell.

3. Set a device supporting the data collector as necessary.
For the setting method, refer to the manual for a device used.

4. Set an external device such as an IT system supporting the IT gateway as necessary.
For the setting method, refer to the manual for an external device such as an IT system used.

5. When cooperating with an edge application installed on another industrial PC, make sure that the time is the same
between an environment where Edgecross Basic Software runs and one where the edge application runs, then create aclient certificate for the edge application as necessary.

6. Start Management Shell Explorer with the administrator authority.
Page 193 Startup method

7. Use Management Shell Explorer to create a data model managed by Management Shell.
For the method for creating data models, refer to the following:
Page 191 Management Shell

8. Set the edge application as necessary.
For the setting method, refer to the manual for an edge application used.
When performing this step, steps 9 to 11 must be performed.

9. Use the edge application to connect to Management Shell.
When selecting the checkbox of "Certificate Automatic Exchange" or selecting "None" for both "Security
Policy" and "Security Mode" in the following section, the connection with Management Shell will succeed. In
this case, steps 10 and 11 can be skipped.
Page 261 Setting an OPC UA server

10. Use Management Shell Explorer to move the client certificate for the edge application from the reject list to the trust list.
Page 263 Managing OPC UA client certificates

11. Use the edge application to reconnect to Management Shell.

4 PROCEDURES BEFORE OPERATION

31

5

Real-time Flow Manager

Real-time Flow Manager is software that implements the functions to diagnose data in production sites in real time andprovide feedback.
It runs in the following three phases with different purposes to utilize data.
Phase

PurposeDescription

Data logging phase

To accumulate logging data for data
analysis and data diagnosis phases

A data logging flow is performed.

Data analysis phase

To create basic diagnosis rules fordata diagnosis

Data accumulated in a data logging flow is analyzed by using a data analysis
tool.

Data diagnosis phase

To provide feedback to a system

A data diagnosis flow is performed according to the diagnosis rules, and theresult is returned to a system.

Process flow
Each process is performed in a process flow by using data received from a system as input.
A result such as an error or a predictable error in a system detected in a process flow is returned to the system.
"Flow" means connection of a series of processes or a stream of data between processes intended for a particular purpose,and output data from a process in a flow becomes input data to the next process.

(1)

(1)

(1)

(1) Process

There are two types of process flows as follows:
Flow type

PurposeNumber of executable flows

Data logging flow

To collect data used for analysis.

32 in total

Data diagnosis flow

To diagnose collected data and return the result to a system.

The following processes that can be performed by Real-time Flow Manager can be used for each flow.
Process type

Description

Corresponding function

Data collection

Data used for a data modification or data diagnosis process is collected.

Page 36 Data Collection
Function

Data modification

Collected data is modified.

Page 37 Data Modification
Function

Data diagnosis

Collected or modified data is diagnosed.

Page 42 Data Diagnosis
Function

Feedback

Feedback is provided to a system.

Page 54 Feedback Function

Note that the number of processes that can be used differs for each flow.
The numbers of processes that can be used for each process flow are as follows:
Flow type

32

Data collection

Data modification

Data diagnosis

Feedback

Data logging flow

1 (required)

3





Data diagnosis flow

1 (required)3

1 (required)

1 (required)

5 Real-time Flow Manager

Precautions• Process execution timing
A process starts running when receiving a notification from the previous process. However, it may be delayed in starting or
cannot be started depending on the usage of the CPU or resources of the industrial PC.
Ex.

The time stamp of data collected in data collection is different from that of a file created by using the file saving function.

Data storing and data distribution
Data storing and data distribution can be performed up to two times in each flow to retain data flowing between processes in
Real-time Flow Manager.
For data storing and data distribution, refer to the following:
Page 59 Data Storing Function
Page 80 Data Distribution Function

5

5 Real-time Flow Manager

33

5.1

Operational Specifications

This section shows the operational specifications of Real-time Flow Manager.

Operating status of a process flow and process
The operating status of a process flow and process can be switched for each process flow in Real-time Flow Designer.
When switching the operating status to RUN or STOP, the process flow and process transition to any of the following states.
For the methods for switching the operating status, refer to the following:
Page 333 "Process Flow Start/Stop" screen
State

Description

Condition for transitioning to the state

STOP state

The process flow or process is stopped.

• The industrial PC is powered ON.
• The operating status transitions from the STOP transition
state to the STOP state.

RUN transition state*1

The process flow or process is being started.

• The operating status is switched from STOP to RUN.

RUN state*1

The process flow or process is running.

• The operating status transitions from the RUN transition
state to the RUN state.

STOP transition state*1

The process flow or process is being terminated.

• The operating status is switched from RUN to STOP.
• A major error occurs, or a moderate error occurs in theprocess flow.

*1*1

Disable the fast startup function. If it is enabled, an industrial PC is not shut down completely, and a process flow may not run properly
when starting the industrial PC after shutdown. For the procedure for disabling the fast startup function, refer to the following:
Page 114 Procedure for disabling the fast startup function

Processing change depending on the status of Windows
If the operating status of each process flow and process is RUN, processing may be changed depending on the status ofWindows.
Status of Windows

Processing in the RUN state

Normal (signed in)

All process flows are running.

LockedSigned out
Being restarted
Shut down
Sleep (standby)*1

All process flows are stopped.
After Windows restarts, Real-time Flow Manager starts in a state set in the following:
Page 113 Operation setting
Do not change the status to these states.

Hibernation*1

In an industrial PC on which Edgecross Basic Software is installed, Windows does not automatically switch to the sleep state even after
a time set in 'Windows settings' elapses. However, if other software is installed on the industrial PC, Windows may switch to the sleep
state. In this case, check the settings for other software and configure the settings to prevent Windows from switching to the sleep state.

If a process takes time to terminate
When communicating with an access target device in a process such as data collection or feedback, the process cannot beterminated until the device returns a response.
Calculate the maximum waiting time by the following formula:• Maximum value of (timeout time  (1 + number of retries))
For the timeout time and the number of retries, refer to the manual for a data collector used or the following:
Page 189 Instruction option

34

5 Real-time Flow Manager
5.1 Operational Specifications

Consideration
The following shows the consideration when operating Real-time Flow Manager.

Sleep state on Windows
Do not change the mode to sleep in the Windows start menu.
Otherwise, an error may occur.

5

5 Real-time Flow Manager
5.1 Operational Specifications

35

5.2

Data Collection Function

This section shows the function to collect data in equipment, devices, and lines connected to an industrial network, generalpurpose Ethernet, or in serial communication, and data accumulated in a file by using a data collector.
All data in production sites can be collected by using the data collection function of a data collector.
The following Data collectors are pre-installed in Edgecross Basic Software: CSV File Data collector for collecting data via amonitoring target file and Management Shell Data collector for collecting data in data tag resources on Management Shell.
(Page 294 CSV File Data collector, Page 314 Management Shell Data collector)
For data collection by using another data collector, refer to the manual for a data collector used.

Precautions
If an execution file of a set data collector does not exist or is corrupted, the corresponding data collector cannot be started andan error occurs.

Adding constants and fixed character strings
Constants or fixed character strings can be added to collected data.
By adding a fixed value such as a model number to collected data, the data collection source (device, equipment, or line) canbe determined.
(Example) When distributing data collected from equipment A, the data can be determined to be collected from equipment A
by adding the fixed character string 'equipment A' and distributing it.

36

5 Real-time Flow Manager
5.2 Data Collection Function

5.3

Data Modification Function

This section shows the function to convert data into a form suitable for data diagnosis in a data diagnosis process.

(1)

(2)

(3)

(4)

(5)

(1) Data collection process(2) Collected data
(3) Data modification process(4) Modified data
(5) Data diagnosis process Data output in a data collection process is modified and the modified data is output.
 The modified data is passed to a data diagnosis process.

5

Further modifications can also be made to the data modified once.
The data modification function has the following functions.
Function

Overview

Reference

Data extraction function

To extract data according to a specified condition.

Page 37 Data extraction function

Character string data modification
function

To modify character string data according to a specified condition.

Page 40 Character string data
modification function

Data modification plug-in run function

To run a data modification plug-in*1.

Manual for a plug-in used*1

It is read at the following timings:
When switching a process flow to RUN
When starting Real-time Flow Designer

Data extraction function
This function extracts data according to a specified condition to align the starting point of processing in a post-process.
Input data is output as modified data while a condition is satisfied, otherwise, it is not output.
Condition is satisfied or not

Input data

1:00:00

1:00:10

1:00:20

1:00:30

1:00:40

1:00:50

1:01:00

1:01:10

1:01:20

1:01:30

1:00:00

1:00:10

1:00:20

1:00:30

1:00:40

1:00:50

1:01:00

1:01:10

1:01:20

1:01:30

1:00:20

1:00:30

1:00:401050Output data

10
50
1:01:10

1:01:30

Combination of data types which can be comparedFor details on the data types that can be compared, refer to the following:
Page 550 Data comparison

5 Real-time Flow Manager
5.3 Data Modification Function

37

Operation example of AND combination
The operation examples for the following settings are shown below.
• Condition 1: Monitoring target data [A] = 1• Condition 2: Monitoring target data [B] = 1
Item

Operation

Monitoring target data [A]2
10

Monitoring target data [B]

1:00:00

1:00:10

1:00:20

1:00:30

1:00:40

1:00:50

1:01:00

1:01:10

1:01:20

1:01:30

1:00:00

1:00:10

1:00:20

1:00:30

1:00:40

1:00:50

1:01:00

1:01:10

1:01:20

1:01:30

1:00:00

1:00:10

1:00:20

1:00:30

1:00:40

1:00:50

1:01:00

1:01:10

1:01:20

1:01:30

1:00:00

1:00:10

1:00:20

1:00:30

1:00:40

1:00:50

1:01:00

1:01:10

1:01:20

1:01:30

1:00:20

1:00:30

1:00:402
10Condition is satisfied or not

Input data

1050Output data

10
5
0

38

5 Real-time Flow Manager
5.3 Data Modification Function

1:01:10

1:01:30

Operation example of OR combination
The operation examples for the following settings are shown below.
• Condition 1: Monitoring target data [A] = 1• Condition 2: Monitoring target data [B] = 1
Item
Monitoring target data [A]Operation2
1
0

Monitoring target data [B]

1:00:00

1:00:10

1:00:20

1:00:30

1:00:40

1:00:50

1:01:00

1:01:10

1:01:20

1:01:30

1:00:00

1:00:10

1:00:20

1:00:30

1:00:40

1:00:50

1:01:00

1:01:10

1:01:20

1:01:30

1:00:00

1:00:10

1:00:20

1:00:30

1:00:40

1:00:50

1:01:00

1:01:10

1:01:20

1:01:30

1:00:00

1:00:10

1:00:20

1:00:30

1:00:40

1:00:50

1:01:00

1:01:10

1:01:20

1:01:30

1:00:00

1:00:10

1:00:20

1:00:30

1:00:40

1:00:50

1:01:00

1:01:10

1:01:20

1:01:302
1
0

5

Condition is satisfied or not

Input data

1050Output data

1050

5 Real-time Flow Manager
5.3 Data Modification Function

39

Character string data modification function
This function adds or extracts a character string to or from string type data according to a specified condition.

Adding a character string to the start
A specified character string can be added to the start of string type data.
If the number of characters in data after adding a character string exceeds its maximum*1, the data will be output without
adding a character string.*2*1*2

STRING type: 32 characters
WSTRING type: 16 characters
A minor error occurs.

Ex.

Success
 Input data (STRING type): abc...z (26 characters)
 Specified character string: AB (2 characters)
Ò

a

b

Ó

A

B

c

...

z
A

B

a

b

c

...

z

...

z

Ex.

Failure Input data (STRING type): abc...z (26 characters)
 Specified character string: AB...Z (26 characters)
Ò

a

b

c

...

z

Ó

A

B

C

...

Z

a

b

c

Adding a character string to the end
A specified character string can be added to the end of string type data.
If the number of characters in data after adding a character string exceeds its maximum*1, the data will be output without
adding a character string.*2*1*2

STRING type: 32 characters
WSTRING type: 16 characters
A minor error occurs.

Ex.

Success
 Input data (STRING type): abc...z (26 characters)
 Specified character string: AB (2 characters)
Ò

a

b

Ó

A

B

c

...

z
a

b

c

...

z

...

z

Ex.

Failure Input data (STRING type): abc...z (26 characters)
 Specified character string: AB...Z (26 characters)
Ò

a

b

c

...

z

Ó

A

B

C

...

Z

a

40

5 Real-time Flow Manager
5.3 Data Modification Function

b

c

A

B

Extracting data
String type data can be extracted according to a specified start position and end position.
If no character exists in the end position, the characters from the start position to the end are extracted.*1
If extraction fails, data will be output without extraction.*2*1*2

No error occurs.
A minor error occurs.

Ex.

Success
Input data (STRING type): abcde

a

b

a

b

c

d

e

(1)

(2)

c

d

e

...

(1)

c

d

c

d

5

e

(2)

(1) Start position(2) End position

Ex.

FailureInput data (STRING type): abcde
a

b

c

d

e

a
(1)

b

c

d

e

(2)

(1) Start position(2) End position

5 Real-time Flow Manager
5.3 Data Modification Function

41

5.4

Data Diagnosis Function

This section shows the function to pass data received from a previous process (data collection or data modification) to data
diagnosis software (plug-in or edge application), and diagnose the data.
This function receives a diagnosis result from data diagnosis software (plug-in or edge application) as a numerical value, andpasses the result to the next process (feedback).
Function
Edge applicationcooperation function

Overview

Reference

To distribute data (collected data and modified data) in Real-time
Flow Manager to an edge application, and receive response datafrom the edge application.
An edge application performs processing based on received data,and outputs a diagnosis result to Real-time Flow Manager.



MQTT cooperation

To input and output data in Real-time Flow Manager and an edge
application via MQTT communication.
Data is input and output via an MQTT broker.

Page 43 MQTT cooperation

File cooperation

To input and output data in Real-time Flow Manager and an edge
application by using a file.

Page 52 File cooperation

To run a data diagnosis plug-in*1.

Manual for a plug-in used

Data diagnosis plug-in run function*1

42

It is read at the following timings:
When switching a process flow to RUN
When starting Real-time Flow Designer

5 Real-time Flow Manager
5.4 Data Diagnosis FunctionMQTT cooperation
Publishing data is distributed from Real-time Flow Manager to an edge application by using MQTT, and response data isreceived from the edge application.
Data is distributed and response data is received via an MQTT broker. By using MQTT cooperation, data can be distributed athigh speed to an edge application supporting a real-time data diagnosis I/F (technology: MQTT).
Real-time Flow Manager: 1

Real-time Flow Manager: 2

(1)

(1)
(b)

(a)

(b)

(a)

(b)

(a)

(b)

(2)

(2)
(b)

(a)

(a)

(b)

(a)
(3)

(3)

5

(3)

(1) Edge application(2) MQTT broker(3) Real-time Flow Manager(a) Publishing data(b) Response data

For the considerations for MQTT cooperation, refer to the following:
Page 49 Considerations

Publishing data
Output data of a data collection or data modification process can be selected as publishing data.

Publishing data definition file
This is a JSON file in which the definitions of publishing data, including the number of units of data, a data type, and a dataname, output in Real-time Flow Manager, and the setting of MQTT communication are described.
An edge application performs MQTT communication according to the contents of a publishing data definition file.
If changing the setting in Real-time Flow Designer, a publishing data definition file must be output in Real-time Flow Designer
and read to an edge application again.
A publishing data definition file exists for each MQTT cooperation. Therefore, it must be output for each MQTT cooperation
when using MQTT cooperation in a different process flow.

Precautions
Rewriting a publishing data definition file is prohibited.

File specification
Item

Description

File format

JSON file (.json)

File nameArbitraryFile format

Character code

UTF-8 (without BOM)

Field data

Compliant with RFC-7159

5 Real-time Flow Manager
5.4 Data Diagnosis Function

43Response data
To receive response data in Real-time Flow Manager, the following items must be set in an edge application.
• Number of units of data
• Data type
• Data nameFor the timing when response data is distributed, refer to the manual for an edge application used.

Response data definition file
This is a JSON file in which the definitions of response data, including the number of units of response data, a data name, anda data type, distributed by an edge application are described.
Real-time Flow Designer reads a response data definition file and sets response data.
A response data definition file exists for each MQTT cooperation. Therefore, it must be read for each MQTT cooperation whenusing MQTT cooperation in a different process flow.
For the procedure for preparing a response data definition file, refer to the manual for an edge application used.

File specification
Refer to the following:
Page 43 File specification

44

5 Real-time Flow Manager
5.4 Data Diagnosis Function

Distribution cycle
Real-time Flow Manager distributes multiple records to an edge application in a batch.
A record refers to all data acquired for each distribution cycle of data collection. (When using CSV File Data collector as a datacollector, it refers to all data acquired for each row.)
The number of distribution records is a number of records included in one unit of publishing data.
The distribution cycle is determined according to the following distribution patterns:
Distribution pattern

Distribution cycle

Priority

The number of distribution records is specified in anedge application.*1

Determined according to a specified number of distribution
records.

1

The previous process is a data modification process(data extraction).*2

Varies depending on each data extraction unit.

2

Others

100 ms*3

3

*1

*2

*3

If the number of records distributed to an edge application exceeds the maximum number of records that can be sent at a time, an error
will occur and a process flow in which the corresponding MQTT cooperation is set will stop.
Page 45 Maximum number of records that can be sent at a time
If the number of records distributed to an edge application exceeds the maximum number of records that can be sent at a time, records
will be distributed separately. In this case, the first records are sent when the maximum number of records is reached. Records thatexceed the maximum number are distributed after the first records are distributed.
Page 45 Maximum number of records that can be sent at a time
Data is distributed at the time when the number of records distributed to an edge application reaches the maximum number of records
that can be sent at a time.
Page 45 Maximum number of records that can be sent at a time5Maximum number of records that can be sent at a time
The following table shows the maximum number of records that can be sent at a time.
Number of units of data to output (column)

Maximum number of records that can be sent at a time (row)

1

256

2

128

3 to 464

5 to 832

9 to 1616

17 to 328

33 to 644

65 to 1282

129 to 256

1

5 Real-time Flow Manager
5.4 Data Diagnosis Function

45

MQTT broker
The following MQTT broker has been checked for its operation and can be used for MQTT cooperation.
Name

Provider

URL

Version

Eclipse Mosquitto

Eclipse Foundation

mosquitto.org

Page 46 Version

Version
The versions of an MQTT broker (Eclipse Mosquitto) the operation of which has been checked are as follows:
Item

Description

Product version

2.0.17 (64bit)*1

MQTT protocol version

3.1.1

License format

Eclipse Public License - v 2.0/Eclipse Distribution License - v 1.0

Pthread version

2.9.0

OpenSSL version

1.1.1u (64-bit)*1

Binary installation (file name: mosquitto-2.0.17-install-windows-x64.exe)

For setting up an MQTT broker (Eclipse Mosquitto) the operation of which has been checked, refer to the following:
Page 504 MQTT Broker SetupOperating environment
It is recommended to operate an MQTT broker in an industrial PC on which Edgecross Basic Software is installed.
Even when using MQTT brokers that operate outside a recommended environment, MQTT cooperation is available, but thecommunication speed may be slower than when using them in a recommended environment.

Reconnection with an MQTT broker
When the communication with an MQTT broker is disconnected, Real-time Flow Manager attempts to reconnect thecommunication at one-second intervals.
If publishing data fails to be distributed, it is buffered in Real-time Flow Manager. When the reconnection succeeds, Real-time
Flow Manager distributes the buffered data.

Alive check of an edge application
The status of an edge application can be monitored in Real-time Flow Manager.
The following statuses can be monitored.
If a state in which an edge application does not run or an error occurs in an edge application is detected, an error will occur in
Real-time Flow Manager.
• Operating status of an edge application• Error status of an edge application

The status can be monitored only when an edge application supports alive check. For details, refer to themanual for an edge application used.

Precautions
If an edge application cannot be confirmed to be alive within the timeout time (five seconds), Real-time Flow Manager outputs
an error.

46

5 Real-time Flow Manager
5.4 Data Diagnosis Function

Communication encryption
Communication using MQTT can be encrypted for MQTT cooperation.

When both Edgecross Basic Software and an MQTT broker are installed on a same industrial
PC
Communication encryption is not recommended because the communication rate may be lower than when not encrypted.

When Edgecross Basic Software and an MQTT broker are installed on a different industrial PC
Encryption is recommended to prevent eavesdropping and falsification of data.
The following table shows the supported encryption method and data required for authentication.
Item

Specification

Encryption protocol

TLS 1.2

Encryption authentication method• Server authentication method• Server authentication & client authentication method

Data required for authentication (server
authentication method)

Real-time Flow Manager side

Certificate authority certificate

MQTT broker side

• Certificate authority certificate• Server secret key• Server certificate

Data required for authentication (server
authentication & client authentication method)

Real-time Flow Manager side

• Certificate authority certificate of a certificate authority thatsigned a server certificate• Client secret key• Client certificate

MQTT broker side

• Certificate authority certificate of a certificate authority thatsigned a client certificate• Server secret key• Server certificate

5 Real-time Flow Manager
5.4 Data Diagnosis Function

5

47

Client IDs and a topic name
The following table shows the client IDs and topic name used in Real-time Flow Manager.
For the setting when connecting multiple pieces of Real-time Flow Manager and edge applications to a single MQTT broker,
refer to the following:
Page 50 When connecting multiple pieces of Real-time Flow Manager and edge applications to a single MQTT broker
Item

Description

Client ID of Real-time Flow Manager

Information for identifying Real-time Flow Manager in a connected MQTT broker.
It is used for connecting Real-time Flow Manager to an MQTT broker.
Set it in Real-time Flow Designer only if a client ID that follows a specific format isrequired, such as when using an MQTT broker provided by a cloud service.
If not setting a client ID in Real-time Flow Designer, an automatically generated
client ID is used for connecting to an MQTT broker. (A character string of a client ID
is prefixed with 'Edgecross.'*1)

Client ID of an edge application

Information for identifying an edge application in a connected MQTT broker andReal-time Flow Manager.
It is used for connecting an edge application to an MQTT broker or receiving
response data from an edge application in Real-time Flow Manager.
Set it in Real-time Flow Designer if there are restrictions on available client IDs,such as when a client ID is specified in an edge application.
If not setting a client ID in Real-time Flow Designer, an automatically generated
client ID is used for creating a publishing data definition file. (A character string of aclient ID is prefixed with 'Edgecross.'*1)
When receiving response data from an edge application in Real-time Flow
Manager, the client ID of the edge application is checked whether it is correct. If it is
not correct, an error occurs.

Publishing data topic name

Information for identifying data that an edge application receives from a connected
MQTT broker.
It is used for distributing data from Real-time Flow Manager to an MQTT broker or
receiving data from an MQTT broker in an edge application.
Set it in Real-time Flow Designer if there are restrictions on available topic names,such as when a topic name is specified in an edge application.
If not setting a publishing data topic name in Real-time Flow Designer, anautomatically generated publishing data topic name is used for creating a publishingdata definition file. (A character string of a publishing data topic name is prefixedwith 'Edgecross.'*1)*1

48

When performing MQTT communication in an application other than Real-time Flow Manager and an edge application by using a client
ID or topic name, do not prefix a character string of a client ID or topic name with 'Edgecross.'

5 Real-time Flow Manager
5.4 Data Diagnosis Function

Considerations
The following shows the considerations for MQTT cooperation.

When starting MQTT cooperation
Make an edge application available for MQTT communication, then switch the operating status of a process flow to RUN. If
switching the operating status to RUN first, communication with the edge application may not be established while configuring
the setting for alive check of the edge application, which may cause an error in Real-time Flow Manager.

When stopping MQTT cooperation
Switch the operating status of a process flow to STOP first. If stopping MQTT communication of an edge application first,
communication with the edge application may not be established while configuring the setting for alive check of the edge
application, which may cause an error in Real-time Flow Manager.

When changing settings in an edge application
Read a response data definition file in Real-time Flow Designer again when changing response data in an edge application.

5

Then, apply the set parameters to Real-time Flow Manager and switch the operating status of a process flow from STOP to
RUN. Note that the operating statuses of all process flows must be switched to STOP once before applying the set
parameters to Real-time Flow Manager.

5 Real-time Flow Manager
5.4 Data Diagnosis Function49When connecting multiple pieces of Real-time Flow Manager and edge applications to asingle MQTT broker
If using a client ID and topic name for identifying data in an MQTT broker and edge application, set them according to thefollowing points.
Note that this setting is not required unless a client ID of Real-time Flow Manager, a client ID of an edge application, and a
topic name are specified. (They are automatically set without duplication.)(1) A client ID of Real-time Flow Manager must be different from any client IDs of other clients (including Real-time Flow
Manager and edge applications) connected to the same MQTT broker. (Client IDs () in the following figure)(2) A client ID of an edge application must be different from any client IDs of other clients (including Real-time Flow Manager
and edge applications) connected to the same MQTT broker; however, a client ID of an edge application set in Real-time Flow
Designer must be the same as the one of a connected edge application. (Set client IDs () in the following figure so thatthey are the same for each communication.)(3) A publishing data topic name must be different for each edge application and communication; however, one set in Realtime Flow Designer must be the same as the one set in a connected edge application. (Set topic names () in thefollowing figure so that they are the same for each communication.)
Industrial PC

Edge application

Edge application

Ö Client ID of an edge application: BÙ Publishing data topic name: GHI

Õ Client ID of an edge application: AØ Publishing data topic name: ABC× Client ID of an edge application: CÚ Publishing data topic name: DEF

Communication1

Communication2

Communication3

MQTT broker

Industrial PC

Industrial PC

Data diagnosis flowÒ Client ID of Real-time Flow Manager: DÕ Client ID of an edge application: AØ Publishing data topic name: ABC
Real-time Flow Manager

Data diagnosis flowÓ Client ID of Real-time Flow Manager: E
× Client ID of an edge application: CÚ Publishing data topic name: DEF
Data diagnosis flowÔ Client ID of Real-time Flow Manager: FÖ Client ID of an edge application: BÙ Publishing data topic name: GHI
Real-time Flow Manager

For the client IDs and topic name used in Real-time Flow Manager, refer to the following:
Page 48 Client IDs and a topic name50

5 Real-time Flow Manager
5.4 Data Diagnosis FunctionIf neither MQTT broker nor edge application is running on an industrial PC on which Real-time
Flow Manager is running
When an MQTT broker, an edge application, and Real-time Flow Manager run on a different industrial PC, the processing
performance will be lower due to communication delay compared with the case in which they run on a same industrial PC.
Take corrective action such as extending the collection cycle or reducing the number of units of output data to avoid a buffer
overflow in MQTT cooperation.

When changing the setting for the number of distribution records in an edge application
Switch the operating status of a process flow to STOP once, then to RUN again. Note that the operating statuses of allprocess flows must be switched to STOP once before applying the set parameters to Real-time Flow Manager.

If Edgecross Basic Software does not support the version of an edge application to becooperated
An error occurs when configuring the setting or receiving response data from the edge application. If the corresponding error
occurs, use an edge application supported by the version of Edgecross Basic Software used, or update Edgecross Basic
Software according to an edge application used. (Page 15 Edge application I/F specification version)5

If changing the setting or order of publishing data
If changing the setting or order of publishing data after reading a publishing data definition file in an edge application, output
the publishing data definition file and read it in the edge application again. Otherwise, an error will occur in the edge
application or data read in the edge application will be incorrect.

Data distribution when Real-time Flow Manager is ended
When switching the operating status of a process flow to STOP, data distribution stops immediately. Data not distributed at
this time will not be distributed.

5 Real-time Flow Manager
5.4 Data Diagnosis Function

51File cooperation
Data in Real-time Flow Manager is distributed to an edge application by using a file and response data is received from theedge application.
File cooperation enables cooperation with an edge application supporting a real-time data diagnosis I/F (technology: file).

Flow of data diagnosis
The following shows the flow of data diagnosis.
When diagnosing data with file cooperation, a publishing data file is created and data is diagnosed according to the diagnosis
rules.
For creating diagnosis rules, refer to the manual for an edge application used.

(2)

(1)

(3)

(4)
(1) Real-time Flow Manager(2) Output destination folder for a publishing data file(3) Edge application(4) Output destination folder for a response data file

 A publishing data file is output to a folder.
 The publishing data file is read.
 The file is diagnosed according to the diagnosis rule.
 A response data file is output to a folder when the diagnosis is completed.
 The response data file is read and response data is acquired. (The file is deleted after the reading is completed.) The response data is passed to the next process (feedback).

Publishing data file
This file is output to distribute data to be diagnosed from Real-time Flow Manager to an edge application.
Immediately after a data modification process (data extraction), data while the data extraction condition is satisfied is output
as a publishing data file. (The publishing data file switches after the data extraction period ends.)

Publishing data definition file
This file stores the definition information of data such as a data name and a data type passed to an edge application from
Real-time Flow Manager.
If it is necessary to provide an edge application with definition information of data in advance, settings for the edge application
can be simplified by reading a publishing data definition file in the edge application.

52

5 Real-time Flow Manager
5.4 Data Diagnosis Function

Response data file
This file is output when an edge application completes a diagnosis.
The file cooperation function detects the generation of a response data file, and passes response data to the feedback
function.
The file cooperation function uses a file name (prefix) of a response data file to determine in which process flow the diagnosis
is completed.
For response data files, refer to the manual for an edge application used.
When the file cooperation function reads response data from a response data file, a response data definition file is used.

Response data definition file
This file defines information of response data such as a data name and a data type.
It is used for reading response data from a response data file.
Output a response data definition file in an edge application after setting the diagnosis, or create it according to the setting.
For response data definition files, refer to the manual for an edge application used.

5

Considerations
The following shows the considerations for file cooperation.
• The following setting must be same between an edge application and Real-time Flow Designer.
Folder path of 'output destination folder for publishing data'• For file cooperation in multiple process flows, set an output destination folder and a file name prefix without duplication in
Real-time Flow Designer.
• When operating a publishing data file and response data file passed to an edge application, or creating a file other than one
to be processed (a file the name of which matches the rules for the name of a file to be processed) in a folder to which the
publishing data file and response data file are output, the operation is not guaranteed.
• When performing file cooperation, configure the setting so that an edge application can read a publishing data file in an
output destination folder for a publishing data file. An edge application must start running within the timeout time (300seconds). If it does not run, an error occurs.
• If Edgecross Basic Software does not support the version of an edge application to be cooperated, an error occurs when
configuring the setting. If the corresponding error occurs, use an edge application supported by the version of EdgecrossBasic Software used, or update Edgecross Basic Software according to an edge application used. (Page 15 Edgeapplication I/F specification version)• If changing the setting or order of publishing data after reading a publishing data definition file in an edge application, output
the publishing data definition file and read it in the edge application again. Otherwise, an error will occur in the edge
application or data read in the edge application will be incorrect.
• When switching the operating status of a process flow to STOP, data output stops immediately. Data not output at this time
will not be output.

5 Real-time Flow Manager
5.4 Data Diagnosis Function

53

5.5

Feedback Function

This section shows the function to perform processing (feedback) to notify external devices according to an execution
condition specified by a user when response data is output.
The feedback function has the following functions.
Function

Description

Reference

Device instruction feedback function

To update data in a connected device via a data collector.

Page 55 Device instruction feedback
function

Program execution feedback function

To run executable programs from a command line.

Page 55 Program execution
feedback function

When the feedback function is performed, the accumulated number of feedback requests is stored in the Real-time Flow
Manager status.
Events are stored in the event history.
Up to four pieces of feedback can be selected per detection. (Duplicated selections allowed.)
Up to 16 pieces of feedback can be provided. '16' is calculated by the following formula: the number of pieces of detected
feedback (data diagnosis function: up to 4)  the number of pieces of feedback per detection (up to 4).
Whether feedback is completed normally is checked, and it is recorded in the event history. If it is not completed normally, anerror occurs.

Precautions• The order of feedback is not guaranteed in the following cases:
Multiple pieces of feedback are set for one data diagnosis
Multiple flows in which feedback is set exist• If multiple pieces of feedback are set and execution conditions for each piece of feedback are satisfied at the same time,
the simultaneous execution of each piece of feedback is not guaranteed.

54

5 Real-time Flow Manager
5.5 Feedback Function

Device instruction feedback function
This function updates data in connected devices via data collectors.
The data writing function of each data collector is used for device instruction feedback.
For details, refer to the manual for a data collector used.

Data assignment and the number of points
For availability of data assignment and the number of points for each update method and device type, refer to the manual fora data collector used.

Combination of data types of a device instruction target and a setting value
For combinations of data types of a device instruction target (device) and a setting value, refer to the following:
Page 548 Data substitution

Program execution feedback function

5This function runs executable programs from a command line.

Specifications of program execution commands
The specifications of each program execution command are as follows:
Item

Specification

Range

Execution command

Specify an execution program path and program arguments with character
strings.
• Execution program path + space + program arguments

255 characters in maximum

Execution program path*1

Specify a program to execute in Real-time Flow Manager.
Characters in the Unicode Basic Multilingual Plane (only those that can beused for the WSTRING type) can be used.*2 (Page 545 WSTRING type)

127 characters in maximum

Program argument*3,*4

Specify arguments to the execution program path.
Characters in the Unicode Basic Multilingual Plane (only those that can beused for the WSTRING type) can be used. (Page 545 WSTRING type)A diagnosis result can be passed to a program by using a reserved word.
For details on reserved words, refer to the following:
Page 56 Reserved word

300 characters in maximum*5

*1
*2
*3
*4
*5

When using a remote shared folder, refer to the following:
Page 556 Using a shared folder without specifying a user account in Edgecross Basic Software
Excluding the following characters that cannot be used for file paths of Windows:/ (0x2F), * (0x2A), ? (0x3F), " (0x22), < (0x3C), > (0x3E), | (0x7C)
Arguments must be delimited by a space.
When operating another file in an execution program, the work folder will be same as the execution program.
Reserved words are counted as the number of characters.

5 Real-time Flow Manager
5.5 Feedback Function

55

Reserved word
The '%Vnnn' format can be used as a reserved word for an execution program argument.
Specify a number (1 to 256) of response data for 'nnn' with zero padding. (Example: %V001)
When '%' is included in an argument, enter '%' twice consecutively.
When a space is included in response data, a reserved word must be enclosed in double quotes (").
The following table shows the correspondence between a data type and an argument character string of response data.
Data type

Expansion format

Number ofcharacters after
expansion

BOOL• ON: 1
• OFF: 0

1

INT

Decimal format*1,*2*1

1 to 6

UINT

Decimal format

1 to 5

DINT

Decimal format*1,*2

1 to 11*1

UDINT

Decimal format

1 to 10LINT

Decimal format*1,*2

1 to 21

ULINT

Decimal format*1

1 to 20

REAL*3,*4• An absolute value is less than 1.000000E-04, or 1.000000E10 or more:
Exponential format (number of digits in the mantissa is 10 digits)*5,*6,*7,*8• An absolute value is 1.000000E-04 or more, and less than 1.000000E10:
Decimal format (number of significant digits: 10 digits)*9

1 to 16LREAL*3,*4• An absolute value is less than 1.000000E-04, or 1.000000E18 or more:
Exponential format (number of digits in the mantissa is 18 digits)*5,*6,*7,*8• An absolute value is 1.000000E-04 or more, and less than 1.000000E18:
Decimal format (number of significant digits: 18 digits)*9

1 to 25

STRING• If a string terminator (0) is used halfway in the data, the subsequent data is
not output.
• A character other than a printable ASCII character (0x20 to 0x7E) and adouble quote (") are replaced with a period (.).

1 to 32

WSTRING• If a string terminator (0) is used halfway in the data, the subsequent data is
not output.
• A control character code, line feed code, and double quote (") are replacedwith a period (.).

1 to 32

*1
*2
*3

*4
*5
*6
*7
*8
*9

'0' or a space is not added for padding.
A sign is added for a minus value only.
Feedback is not provided and an error is output in the following cases:
Data (non-numeric value) that cannot be represented in a type specified for the data type
It exceeds the upper limit of a positive value (represented as '+Inf').
It falls below the lower limit of a negative value (represented as '-Inf').
If a value is in the range of '0' to the lower limit value of a positive value, '0' is output. If it is in the range of the lower limit value of anegative value to '0,' '-0' is output.
'E' is displayed in uppercase.
When the end of the mantissa is '0,' it is rounded down and output.
'+' or '-' is added in front of an exponent.
When an exponent is a single digit, it is displayed in double digits with zero padding.
When the end of the decimal part is '0,' it is rounded down and output.

• Up to 32 reserved words can be used.
• Even when there is a character other than a blank before and after a reserved word, a program is executed.

56

5 Real-time Flow Manager
5.5 Feedback FunctionPrecautions• A program to be executed runs as a Windows service; therefore, any operation that requires a screen cannot be performed.
(Example) Entering a login user or password• A program runs as a Windows service; therefore, it is executed with the administrator authority by using the Windows
account 'SYSTEM.' When setting program execution, note the following:
Use a system environment variable. (An environment variable of the current user cannot be used.)A folder storing the program is set as a current folder.
However, if the program is a batch file in a remote shared folder, the Windows directory of an industrial PC on which Realtime Flow Manager is installed is set as a current folder.
A network drive (drive assigned by using a Windows function) cannot be used.
• If running an application, user program, or batch file that needs to be ended by an operation of a user, a process may
remain incorrectly and system resources may be under pressure.
• If a program argument containing a space is not divided at the position of the space, enclose it in double quotes (").

5

(Example) "C:\My Folder\out.dat"

5 Real-time Flow Manager
5.5 Feedback Function57

Feedback deterrence
A deterrence period can be set not to provide same feedback for a certain period once it is provided.

When feedback is always provided
Feedback is provided each time an error is detected.
Ex.

(1)

(1)
(2)

(1)
(2)

(2)
t

10:00:00

10:30:00

11:00:00

11:30:00

12:00:00(1) An error is detected.
(2) Feedback is provided.

When a deterrence period is specified
Feedback is not provided until the execution deterrence period elapses.
Ex.

When one hour is set for a deterrence period

(1)

(1)
(2)

(1)
(3)

(2)
t

10:00:00

10:30:00

11:00:00

11:30:00

1H(1) An error is detected.
(2) Feedback is provided.
(3) Feedback is not provided, because a deterrence period does not elapse.

58

5 Real-time Flow Manager
5.5 Feedback Function

12:00:00

5.6

Data Storing Function

This section shows the function to save data collected or modified in Real-time Flow Manager, or response data received byusing the data diagnosis function in a format specified in Real-time Flow Designer.
The following saving formats can be specified.
• File (Page 60 File saving function)• Database (Page 77 DB saving function)

5

5 Real-time Flow Manager
5.6 Data Storing Function

59File saving function
This function saves data collected or modified in Real-time Flow Manager, or diagnosis result data to a file (historical data file)in a format of a historical data access I/F (technology: file).
In addition, any program can be run in Real-time Flow Manager after file saving. Therefore, a program that processes ahistorical data file can be run and used for cooperating with an edge application.
(1)

Ö
(2)

Õ

(3)

Ó
A
2017/8/1 08:45:00

OFF

10

2017/8/1 08:45:01

OFF

11

2017/8/1 08:45:02

ON

13

2017/8/1 08:45:03

OFF

12

B
2017/8/1 08:45:00,0,10
2017/8/1 08:45:01,0,11
2017/8/1 08:45:02,1,13
2017/8/1 08:45:03,0,12

Ò

Industrial PC

Data collection target device: Functions of Edgecross Basic Software: Range of the file saving function: Functions other than one of Edgecross Basic Software
A: Data collection function, data modification function
B: File saving function(1) Edge application(2) Any program(3) Historical data file

 Collected and modified data is sent.
 A historical data file is output.
 A program is run.
 Saved data is read from the program.
 Data read from the program to the edge application is sent.

60

5 Real-time Flow Manager
5.6 Data Storing FunctionÔOperational specifications
File output
Data to be output is temporarily saved in an accumulating file in the temporary area in Real-time Flow Manager.
The size of an accumulating file increases over time, and the file switches when the number of rows specified in Real-time
Flow Designer is reached.
When selecting the checkbox of "Output in Data Extraction unit" in Real-time Flow Designer, data to be output is output to an
accumulating file while a data extraction condition is satisfied, and the file switches when the condition is no longer satisfied.
However, even while the condition is satisfied, the file switches if the number of rows specified in Real-time Flow Designer isreached.
File switching is to change the name of an accumulating file to that of a saved file, and move it to a save destination folder. (Anew accumulating file is created after file switching.)
When a process flow stops running, an accumulating file switches to a saved file even if a specified number of rows is notreached. However, if there is no output data in the accumulating file, the file is deleted without switching.

5

If switching a file while a process flow is stopped, a new accumulating file is not created.
Saved files are saved up to a number of files specified in Real-time Flow Designer. If the specified number is exceeded, files
are deleted in chronological order.
(1)

(2)

(3)

FileName_01

time
FileName_02

FileName_01

FileName_03

FileName_02

FileName_01

FileName_04

FileName_03

FileName_02

FileName_01(4)(1) Accumulating file(2) Saved file (a file with a smaller number is an older one)(3) File switching(4) File to be deleted

5 Real-time Flow Manager
5.6 Data Storing Function

61

Precautions• If the number of rows specified in Real-time Flow Designer is small, the load on Windows increases because a saved file isfrequently created. In this case, review the setting to lengthen the collection cycle or increase the maximum number of datarows output to a file.
• For specifying a folder with the encryption attribute enabled as a file output destination, refer to the following:
Page 71 Using a folder with the encryption attribute enabled• When specifying a folder with the compression attribute enabled for a save destination folder, the free space is determined
to be temporarily insufficient and a file saving error may occur if the free space on the disk is low.
• When outputting real number type data to a file in a decimal format, it is output in an exponential format if the value applies
to either of the following conditions. In this case, the number of digits in the mantissa is that of significant digits and '0' at theend of the decimal part is rounded down.
REAL type: Less than 1.0E-4 (absolute value) or 1.0E+6 (absolute value) or more
LREAL type: Less than 1.0E-4 (absolute value) or 1.0E+15 (absolute value) or more

62

5 Real-time Flow Manager
5.6 Data Storing FunctionHistorical data definition file output
A historical data definition file contains information such as a data name and a data type of collected or modified data anddiagnosis result data.
It is output to the 'DATATYPE' folder in a save destination folder at the timing when a process flow switches from STOP to
RUN. If there is no 'DATATYPE' folder, it is created when a historical data definition file is output.
A historical data definition file is created for each prefix of a file. When there is a historical data definition file with a same prefixin the 'DATATYPE' folder, the file is overwritten.

Output in data extraction units
When the data extraction is set for a data modification process, output data is saved to a file in a set data extraction unit.
(Page 37 Data Modification Function)
Output data is output to a file only while the condition is satisfied, and a file is switched when the period ends.
The following shows operation examples of AND combination and OR combination when selecting the checkbox of "Output in
Data Extraction unit."
Operation example of AND combination

5

The operation examples for the following settings are shown below.
• Condition 1: Monitoring target data [A] = 1• Condition 2: Monitoring target data [B] = 1
Item
Monitoring target data [A]Operation2
1
0

Monitoring target data [B]

1:00:00

1:00:10

1:00:20

1:00:30

1:00:40

1:00:50

1:01:00

1:01:10

1:01:20

1:01:30

1:00:00

1:00:10

1:00:20

1:00:30

1:00:40

1:00:50

1:01:00

1:01:10

1:01:20

1:01:30

1:00:00

1:00:10

1:00:20

1:00:30

1:00:40

1:00:50

1:01:00

1:01:10

1:01:20

1:01:30

1:00:00

1:00:10

1:00:20

1:00:30

1:00:40

1:00:50

1:01:00

1:01:10

1:01:20

1:01:30

1:00:20

1:00:30

1:00:402
10Condition is satisfied or not

Input data

1050Output data
(Output to a file)

10
5
0

FILE1

1:01:10

1:01:30

FILE2

FILE3

5 Real-time Flow Manager
5.6 Data Storing Function

63

Operation example of OR combination
The operation examples for the following settings are shown below.
• Condition 1: Monitoring target data [A] = 1• Condition 2: Monitoring target data [B] = 1
Item

Operation

Monitoring target data [A]2
10

Monitoring target data [B]

1:00:00

1:00:10

1:00:20

1:00:30

1:00:40

1:00:50

1:01:00

1:01:10

1:01:20

1:01:30

1:00:00

1:00:10

1:00:20

1:00:30

1:00:40

1:00:50

1:01:00

1:01:10

1:01:20

1:01:30

1:00:00

1:00:10

1:00:20

1:00:30

1:00:40

1:00:50

1:01:00

1:01:10

1:01:20

1:01:30

1:00:00

1:00:10

1:00:20

1:00:30

1:00:40

1:00:50

1:01:00

1:01:10

1:01:20

1:01:30

1:00:00

1:00:10

1:00:20

1:00:30

1:00:40

1:00:50

1:01:00

1:01:10

1:01:20

1:01:302
10Condition is satisfied or not

Input data

1050Output data
(Output to a file)

10
5
0

FILE1

FILE2

FILE3

Precautions
A maximum number of data rows specified in Real-time Flow Designer can be output to a file. If the number of data rows
output while the data extraction condition is satisfied exceeds the maximum number, the file switches to a new one andremaining data is output to the new one.

64

5 Real-time Flow Manager
5.6 Data Storing FunctionFile deletion
If the number of output files reaches a specified number of files, files are deleted in chronological order.
Files are compared by using the eight-digit sequential number of the end of a file name, and deleted in ascending order.

Historical data definition file deletion
A historical data definition file is not automatically deleted even when the setting of Real-time Flow Designer is changed.
Delete it or move it to another folder as necessary.

Data missing
No data is output while data missing is occurring.
When the file saving setting is configured in a data collection process, data missing information is output to a file as index
information.

Whether data missing occurred in a running process flow can be checked by monitoring the number of timesof data missing in the process flow diagnostics or status memory monitor of Real-time Flow Designer.

5

Page 337 Process flow diagnostics
Page 340 Status memory monitor
Page 433 Real-time Flow Manager Status

File format
The following file formats are available to output data.
File format

Description

Shift JIS

Comma-delimited data is output with Shift JIS codes.

UTF-8

Comma-delimited data is output with UTF-8 codes (with BOM).

Account to be used
When specifying a user account in Real-time Flow Designer, it is used. If not, the Windows account 'SYSTEM' is used.
By specifying a user account, a file can be output to a folder accessible to a specific user only.
For the method for specifying a user account, refer to the following:
Page 147 Saved file

Precautions
When using a user account specified in Real-time Flow Designer, the authentication processing may take time due to a
network load or failure.
If it takes five minutes or more, a moderate error occurs.

5 Real-time Flow Manager
5.6 Data Storing Function65Data size
The following table shows the size of each unit of data to be output to a file.
Item name

Description

Size (byte)
CSV

Data name row

Data row

Shift JISUTF-8

Date and time column

32

32Data column

32

96Date and time

32

32

BOOL

1

1

INT

6

6

Integer format

5

5

Hexadecimal format

4

4

11

11

Integer format

10

10

Hexadecimal format

8

8

20

20

Integer format

19

19

Hexadecimal format

16

16

Decimal format

26

26

Exponential format

22

22

STRING

32

32

WSTRING

48

Line feed code (CRLF)

2

2

BOM

0

3

UINT

DINT
UDINT

LINT
ULINT

REAL
LREAL

OthersDisk space for saving files
Disk space required to save files is calculated by the following formulas based on the setting contents and the size of data.
Required file capacity = Sum of each <maximum size of items saved in a file><Maximum size of items saved in a file>*1 = <Size of one file>  (Upper limit of the number of saved files + 1)
<Size of one file> = Data name row size + (Data row size  Number of data rows) + (Line feed code size  Number of datarows) + BOM*1

66

Files are output and accumulated in a temporary file until a specified number of rows is reached. Therefore, an area obtained by adding'1' to the upper limit of the number of saved files is required until immediately before output.

5 Real-time Flow Manager
5.6 Data Storing Function

File name, save destination
The following shows the specifications of names and save destinations of a file output by performing the file saving function
and a historical data definition file.

File
Item

Specification

Range

File name

The format of a file name is 'Prefix_suffix.extension.'

14 to 45 characters

PrefixCharacters that can be used for the WSTRING type*1,*2 can be used.

1 to 32 characters

SuffixAn eight-digit sequential number (hexadecimal) is added. (It is sequentially
incremented from 00000001 to FFFFFFFF.)
When saving a file with the prefix same as one saved in a save destination, thesuffix is incremented from the maximum prefix.

8 characters(Fixed to 8 digits using 0 to
9 and A to F)

Save destination

A file can be saved to the following locations:• Local disk
• Shared folder*3, *4
Characters in the Unicode Basic Multilingual Plane (only those that can be used for the WSTRINGtype) can be specified as the path to a save destination.*2,*5 (Page 545 WSTRING type)

Path length: 205
characters in maximum(Including the drive letterand '\' at the end of a path)

Maximum number of files
created in a savedestination

If a specified number of files is exceeded, files are deleted in chronological order.

1 to 6000

*1
*2
*3
*4
*5

5

Excluding the following characters:\ (0x5C), / (0x2F), : (0x3A), * (0x2A), ? (0x3F), " (0x22), < (0x3C), > (0x3E), | (0x7C)
A space (0x20) and a period (0x2E) cannot be used for the first character.
When using a remote shared folder, refer to the following:
Page 553 Using a Remote Shared Folder
A network drive (drive assigned by using a Windows function) cannot be used.
Excluding the following characters that cannot be used for file paths of Windows:/ (0x2F), * (0x2A), ? (0x3F), " (0x22), < (0x3C), > (0x3E), | (0x7C)

Precautions
If a file that is not created according to the specification is included in a save destination, the file is ignored.

Historical data definition file
Item

Specification

Range

File name

The format of a file name is 'Prefix_suffix.extension.'

14 to 45 characters

Prefix

Refer to 'Prefix' in the following:
Page 67 File

1 to 32 characters

SuffixDATATYPE

8 characters

Save destination

A historical data definition file is saved in the 'DATATYPE' folder in a save destination folder
described in the following section. If there is no 'DATATYPE' folder, it will be created when saving afile.*1
Page 67 FileMaximum number of files
created in a savedestination

One file is created for one file name prefix.
If the file name prefix is changed after a historical data definition file is output, the old historical data
definition file will not be deleted.

1*1

If a folder is not created even after the following time elapses, an error will occur.
When starting an industrial PC: 240 seconds after the startup of the industrial PC
When 240 or more seconds elapses after the startup of an industrial PC: 10 seconds

5 Real-time Flow Manager
5.6 Data Storing Function67

Program execution after file output
Executable programs can be executed from a command line when a file is output (without waiting for a response from theprogram).
• Specifications of program execution commands
The specifications of each program execution command are as follows:
Item

Specification

Range

Program path*1

Specify the absolute path of a program to execute in Real-time Flow Manager.
Characters in the Unicode Basic Multilingual Plane (only those that can beused for the WSTRING type) can be used.*2 (Page 545 WSTRING type)

127 characters in maximum

Program argument*3

Specify arguments to the program path.
Characters in the Unicode Basic Multilingual Plane (only those that can beused for the WSTRING type) can be used. (Page 545 WSTRING type)The following reserved words can be specified.
<FILE>: Absolute path string for output file

127 characters in maximum*4

*1
*2
*3
*4

When using a remote shared folder, refer to the following:
Page 556 Using a shared folder without specifying a user account in Edgecross Basic Software
Excluding the following characters that cannot be used for file paths of Windows:/ (0x2F), * (0x2A), ? (0x3F), " (0x22), < (0x3C), > (0x3E), | (0x7C)
Arguments must be delimited by a space.
Reserved words are counted as the number of characters.

Precautions• A program executed after a file is output runs as a Windows service; therefore, any operation that requires a screen cannot
be performed.
(Example) Entering a login user or password• A program runs as a Windows service; therefore, it is executed with the administrator authority by using the Windows
account 'SYSTEM.' When setting program execution, note the following:
Use a system environment variable. (An environment variable of the current user cannot be used.)A folder storing the program is set as a current folder.
However, if the program is a batch file in a remote shared folder, the Windows directory of an industrial PC on which Realtime Flow Manager is installed is set as a current folder.
A network drive (drive assigned by using a Windows function) cannot be used.
• When specifying a user account and specifying a file output to a folder with restricted access or the encryption attribute
enabled as an argument of a program, the program may not be able to access the output file due to the difference inauthority.
• If a program argument containing a space is not divided at the position of the space, enclose it in double quotes (").
(Example) "C:\My Folder\out.dat"

68

5 Real-time Flow Manager
5.6 Data Storing Function

Using a local folder with restricted access
The following shows the procedure for setting a local folder that can be accessed only with a user account specified in Realtime Flow Designer as a save destination.

1. Click the [Edit] button in the [Security] tab in theproperties of a save destination folder.

5

2. Click the [Add] button.

3. Enter a user account name in "Enter the object name toselect."4. Click the [OK] button.

5 Real-time Flow Manager
5.6 Data Storing Function69

5. Select a user account to allow access, then select thecheckboxes of "Change" and "Read" under "Allow" for"Permissions."

6. Click the [OK] button.

70

5 Real-time Flow Manager
5.6 Data Storing Function

Using a folder with the encryption attribute enabled
By enabling the encryption attribute for a folder to which a file is output in Windows and specifying a user account in
Edgecross Basic Software, information in the file can be protected from other users who use an industrial PC.
Note that an output destination folder must be a local folder.
The following shows the procedure for enabling the encryption attribute of a folder in Windows.
1. Click the [Advanced] button in the [General] tab in theproperties of a folder.

5

2. Select the checkbox of "Encrypt contents to secure
data."*1*1

To remove the encryption, unselect the checkbox.

3. Click the [OK] button.
4. Close the properties of the folder.

Precautions• Simply specifying a user account in Edgecross Basic Software does not enable the encryption attribute for a savedestination folder, and an output file is not encrypted either.
• When not specifying a user account in Edgecross Basic Software, a file is output with the Windows account 'SYSTEM'
instead of a user signed in to Windows. Therefore, a saved file cannot be opened in other software or with other user
accounts. To set a folder with the encryption attribute enabled as a save destination, be sure to specify the user name andpassword of a user account in Edgecross Basic Software.
• If a save destination folder set in Edgecross Basic Software does not exist, a file is output with a specified user accountafter a folder is created. Note that the encryption attribute is not enabled for a created save destination folder and an output
file is not encrypted either.
• If a historical data definition file with a same file name prefix saved with another user account already exists in a savedestination folder with the encryption attribute enabled, an error may occur due to the difference in authority to the file.
Specify a file name prefix different from a file already output.
• For the procedure for browsing files output to an encrypted folder with a user account other than one specified in EdgecrossBasic Software, refer to the following:
Page 72 Procedure for browsing files with a user account other than a specified one

5 Real-time Flow Manager
5.6 Data Storing Function71Procedure for browsing files with a user account other than a specified one
The following shows the procedure for browsing files output to an encrypted folder with a user account other than one
specified in Edgecross Basic Software.
 Exporting the certificate of an encrypted file

1. Sign in to Windows as a specified user.
2. Click the [Advanced] button in the [General] tab in theproperties of an encrypted and saved file.

3. Click the [Details] button.

4. Select a specified user in the user list, and click the[Back up keys] button.

5. Click the [Next] button.

72

5 Real-time Flow Manager
5.6 Data Storing Function

6. Click the [Next] button.

7. Select the checkbox of "Password" and set a password,

5

then click the [Next] button.

8. Set a save destination and file name of a certificate toexport, and click the [Next] button.
A save destination must be one that can be accessed by auser who browses a file.

5 Real-time Flow Manager
5.6 Data Storing Function73

9. Click the [Finish] button.

 Importing a certificate

1. Sign in to Windows with a user account that will beallowed to browse a file.

2. Double-click an exported certificate file (.pfx).
3. Select "Current User," and click the [Next] button.

4. Set the exported certificate file (.pfx) for "File name,"and click the [Next] button.

74

5 Real-time Flow Manager
5.6 Data Storing Function

5. Enter the password for the certificate file (.pfx), and click
the [Next] button.

6. Click the [Next] button.
7. Click the [Finish] button.

5

5 Real-time Flow Manager
5.6 Data Storing Function

75

Considerations
The following describes the considerations for file saving.

Changing the setting or order of output data
When changing the setting or order of output data after reading a historical data definition file in an edge application, read thefile in which the setting is applied in the edge application again. If not reading the file again, an error will occur in the edge
application or data read in the edge application will be incorrect.

The number of a file name suffix reaches 'FFFFFFFF'
When the file name suffix of a file being output reaches 'FFFFFFFF,' move all files in the save destination folder to anotherfolder and restart the operation of Real-time Flow Manager, or set another path for the save destination folder again.

Using the data distribution function to distribute data
When switching the operating status of a process flow to STOP, the data distribution function stops immediately and data notdistributed at this time will not be distributed. If there is undistributed data, a difference occurs between distributed data anddata output by using the file saving function.

Using an IT gateway to save a file
An IT gateway runs as a Windows service; therefore, it is executed with the administrator authority by using the Windows
account 'SYSTEM.' Files output to a folder with restricted access or the encryption attribute enabled by using a user account
may not be saved due to the difference in authority. For the specifications of an IT gateway, refer to the manual for the IT
gateway.

Specifying a folder for which a search index is to be created as a save destination
When specifying a folder for which a Windows search index is to be created as a save destination folder and running aprocess flow for a long time, the amount of index information (Windows.edb file) becomes large. As a result, the free disk
space on an industrial PC where Edgecross Basic Software is running may become insufficient. This can be avoided by eitherof the following methods:• Specify a folder other than one for which a search index is to be created as a save destination folder.
• Exclude the folder specified as a save destination folder from the search index target by the following procedure: Select [Search]  [Searching Windows]  "Classic"  "Customize search locations here" in Windows settings.
 Click the [Modify] button in the "Indexing Options" screen.
 Unselect the checkbox of the folder specified as a save destination folder in "Change selected locations" in the "Indexed
Locations" screen, and click the [OK] button.

76

5 Real-time Flow Manager
5.6 Data Storing Function

DB saving function
This function saves (INSERT) data collected or modified in Real-time Flow Manager, or diagnosis result data in a database
specified in Real-time Flow Designer.
Saved data can be displayed and analyzed by using an edge application.
By using the DB saving function, cooperation with an edge application supporting a historical data access I/F (technology: DB)
will be available.
(1)Ô

Database5ÓA
2017/8/1 08:45:00

OFF

10

2017/8/1 08:45:01

OFF

11

2017/8/1 08:45:02

ON

13

2017/8/1 08:45:03

OFF

12

Ó

B

2017/8/1 08:45:00,0,10
2017/8/1 08:45:01,0,11
2017/8/1 08:45:02,1,13
2017/8/1 08:45:03,0,12

Ò

Industrial PC

Data collection target device: Functions of Edgecross Basic Software: Range of the file saving function: Functions other than one of Edgecross Basic Software
A: Data collection function, data modification function
B: DB saving function(1) Edge application

 Collected and modified data is sent.
 The data is saved (INSERT) to a database.
 The data in the database is displayed and analyzed by using an edge application.

5 Real-time Flow Manager
5.6 Data Storing Function

77Database
The following database has been checked for its operation and can be used for the DB saving function.
Database type

Software

EditionVersion

Provider

URL

Remarks

PostgreSQL

PostgreSQL(Single edition)

10.3

The PostgreSQL
GlobalDevelopment
Groupwww.postgresql.org• 64-bit version only
• Open source• Install it on an industrial PC
where Edgecross Basic
Software is installed.

Communication method
For communicating with a database, use ODBC to connect.
The DB saving function requests ODBC to execute an SQL statement (INSERT), then ODBC saves (INSERT) data to a
database.

Procedure before using the DB saving function
The following shows the procedure before using the DB saving function when using PostgreSQL as a database.

Operating procedure

1. Install a database.
Page 530 Installing PostgreSQL

2. Install the ODBC driver.
Page 535 Installing the ODBC driver for PostgreSQL

3. Configure the ODBC setting.
Page 536 ODBC setting

4. Configure the data storing setting (DB saving) in Real-time Flow Designer.
Page 152 Data Storing Setting (DB Saving)

5. Use the DDL file output in step 4 to create a table in the database.
Page 537 Creating a table by using a DDL

6. Change the operating status of a process flow to RUN.
Page 332 Real-time Flow Manager diagnosis

Precautions• When changing the setting or order of output data after outputting a DDL file, output the DDL file in Real-time Flow
Designer and create the table in the database again. If the table is not created again, an error may occur when running
Real-time Flow Manager or incorrect data may be stored in the database.
• When switching the operating status of a process flow to STOP while using the data distribution function to distribute data,
the function stops immediately and data not distributed at this time will not be distributed. If there is undistributed data, adifference occurs between distributed data and data output by using the DB saving function.

78

5 Real-time Flow Manager
5.6 Data Storing Function

Operational specifications
The DB saving function saves (INSERT) data to a database.
By setting each item to save data to a field of a table in a database in Real-time Flow Designer, the data is saved (INSERT)
according to the setting.
A database is connected when switching the operating status of a process flow to RUN, and disconnected when switching itfrom RUN to STOP.

• Up to 257 fields can be specified.
• SQL statements and data types of a database used for the DB saving function are compliant with SQL99
specifications.

Precautions

5• If data is missing in one row, a minor error will be reported and the data in the row will not be saved (INSERT).
• Data cannot be saved (INSERT) to a same table from multiple process flows.

Table name and field name
The following table shows the specifications of a table name and a field name.
Item

Description

Number of characters

1 to 32

Available characters

Characters that can be used for the WSTRING type*1
Page 545 WSTRING type*1

The following characters in the range of U+0000 to U+007F can be used.
0 to 9, A to Z, a to z, _ (U+005F)

Precautions
A same field name cannot be set in a same table.

Processing for a problem
If an error is detected while performing the DB saving function, the error is output. If the error occurs in ODBC, the ODBC
error code is displayed in the detailed information in the error information list in the "Real-time Flow Manager Diagnostics"
screen.
For details on the ODBC error codes, visit the following:• docs.microsoft.com/en-us/sql/odbc/reference/appendixes/appendix-a-odbc-error-codes
If there is no corresponding ODBC error code on Microsoft home page, visit the following:• www.postgresql.org/docs/10/static/errcodes-appendix.html

5 Real-time Flow Manager
5.6 Data Storing Function

79

5.7

Data Distribution Function

This section shows the function to distribute data (collected data, modification result data, and diagnosis result data) in Realtime Flow Manager to an edge application.

MQTT distribution function
This function distributes output of data collection, data modification, and data diagnosis processes to an edge application byusing MQTT.
Publishing data is sent to an edge application via an MQTT broker according to the setting of Real-time Flow Manager. The
MQTT distribution function runs even when an MQTT broker, edge application, and Edgecross Basic Software (Real-time
Flow Manager) are each installed on a different industrial PC.
By using the MQTT distribution function, cooperation with an edge application supporting a real-time data publishing I/F(technology: MQTT) will be available.
Real-time Flow Manager: 1

Real-time Flow Manager: 2

(1)

(1)

(a)

(a)

(a)
(2)

(2)
(a)

(a)
(3)

(a)
(3)

(3)

(1) Edge application(2) MQTT broker(3) Real-time Flow Manager(a) Publishing data

For the considerations for MQTT distribution, refer to the following:
Page 82 Considerations

Publishing data
Output data of a data collection, data modification, or data diagnosis process can be selected as publishing data.
Page 43 Publishing data

Publishing data definition file
This is a JSON file in which the definitions of publishing data (the number of units of data, a data type, and a data name) andthe setting of MQTT communication are described.
An edge application performs MQTT communication according to the contents of a publishing data definition file.
If the setting is changed in Real-time Flow Designer, a publishing data definition file must be output in Real-time Flow
Designer again.
A publishing data definition file exists for each MQTT distribution setting. Therefore, it must be output for each MQTT
distribution when using MQTT distribution in a different process flow.

80

5 Real-time Flow Manager
5.7 Data Distribution Function

Distribution cycle
Real-time Flow Manager distributes multiple records to an edge application in a batch.
A record refers to all data acquired for each distribution cycle of data collection. (When using CSV File Data collector as a datacollector, it refers to all data acquired for each row.)
The number of distribution records is a number of records included in one unit of publishing data.
The distribution cycle is determined according to the following distribution patterns:
Distribution pattern

Distribution cycle

Priority

The checkbox of "Output in Data Extraction unit" isselected.*1

Varies depending on each data extraction unit.

1

Others

100 ms*2

2

*1

*2

If the number of records distributed to an edge application exceeds the maximum number of records that can be sent at a time, records
will be distributed separately. In this case, the first records are sent when the maximum number of records is reached. Records thatexceed the maximum number are distributed after the first records are distributed.
Page 81 Maximum number of records that can be sent at a time
Data is distributed when the number of records distributed to an edge application reaches the maximum number of distribution records.
Page 81 Maximum number of records that can be sent at a time5Maximum number of records that can be sent at a time
The following table shows the maximum number of records that can be sent at a time.
Number of units of data to output (column)

Maximum number of records (row)

1

256

2

128

3 to 464

5 to 832

9 to 1616

17 to 328

33 to 644

65 to 1282

129 to 256

1

MQTT broker
Refer to the following:
Page 46 MQTT broker

Reconnection with an MQTT broker
Refer to the following:
Page 46 Reconnection with an MQTT broker

Data missing
No data is distributed while data missing is occurring.
When the data distribution setting is configured in a data collection process, data missing information is reported to the
distribution destination.

Whether data missing occurred in a running process flow can be checked by monitoring the number of timesof data missing in the process flow diagnostics or status memory monitor of Real-time Flow Designer.
Page 337 Process flow diagnostics
Page 340 Status memory monitor
Page 433 Real-time Flow Manager Status

5 Real-time Flow Manager
5.7 Data Distribution Function81Communication encryption
Refer to the following:
Page 47 Communication encryption

Client IDs and a topic name
Refer to the following. Note that a client ID of an edge application is not used in MQTT distribution.
Page 48 Client IDs and a topic nameFor the setting when connecting multiple pieces of Real-time Flow Manager and edge applications to a single MQTT broker,
refer to the following:
Page 83 When connecting multiple pieces of Real-time Flow Manager and edge applications to a single MQTT broker

Considerations
The following shows the considerations for MQTT distribution.

When starting MQTT distribution
Make an edge application available for receiving data in MQTT communication first, then switch the operating status of aprocess flow to RUN. Otherwise, data distributed before that may not be distributed to the edge application.

When stopping MQTT distribution
To stop the operation, switch the operating status of a process flow to STOP first. In addition, make sure that the operating
status switches to STOP before stopping MQTT communication of an edge application.

82

5 Real-time Flow Manager
5.7 Data Distribution FunctionWhen connecting multiple pieces of Real-time Flow Manager and edge applications to asingle MQTT broker
If using a client ID and topic name for identifying data in an MQTT broker and edge application, set them according to thefollowing points.
Note that this setting is not required unless a client ID of Real-time Flow Manager and a topic name are specified. (They areautomatically set without duplication.)(1) A client ID of Real-time Flow Manager must be different from any client IDs of other clients (including Real-time Flow
Manager and edge applications) connected to the same MQTT broker. (Client IDs () in the following figure)(2) A client ID of an edge application must be different from any client IDs of other clients (including Real-time Flow Manager
and edge applications) connected to the same MQTT broker. (Client IDs () in the following figure)(3) A publishing data topic name must be different for each edge application and communication; however, one set in Realtime Flow Designer must be the same as the one set in a connected edge application. (Set topic names () in thefollowing figure so that they are the same for each communication.)
Industrial PC

5

Edge application

Edge application

Ö Client ID of an edge application: BÙ Publishing data topic name: GHI

Õ Client ID of an edge application: AØ Publishing data topic name: ABC× Client ID of an edge application: CÚ Publishing data topic name: DEF

Communication1

Communication2

Communication3

MQTT broker

Industrial PC

Industrial PC

Data diagnosis flowÒ Client ID of Real-time Flow Manager: DØ Publishing data topic name: ABC
Real-time Flow Manager

Data diagnosis flowÓ Client ID of Real-time Flow Manager: E
Ú Publishing data topic name: DEF

Data diagnosis flowÔ Client ID of Real-time Flow Manager: FÙ Publishing data topic name: GHI
Real-time Flow Manager

For the client IDs and topic name used in Real-time Flow Manager, refer to the following. Note that a client ID of an edge
application is not used in MQTT distribution.
Page 48 Client IDs and a topic name

5 Real-time Flow Manager
5.7 Data Distribution Function83If neither MQTT broker nor edge application is running on an industrial PC on which Real-time
Flow Manager is running
The processing performance will be lower due to communication delay compared with the case in which they run on a same
industrial PC.
Take corrective action such as extending the collection cycle or reducing the number of units of output data to avoid a buffer
overflow in MQTT distribution.

If changing the setting or order of publishing data
If changing the setting or order of publishing data after reading a publishing data definition file in an edge application, output
the publishing data definition file and read it in the edge application again. Otherwise, an error will occur in the edge
application or data read in the edge application will be incorrect.

Data distribution when Real-time Flow Manager is ended
When switching the operating status of a process flow to STOP, data distribution stops immediately. Data not distributed at
this time will not be distributed.

84

5 Real-time Flow Manager
5.7 Data Distribution Function

IT gateway distribution function
This function distributes output of data collection, data modification, and data diagnosis processes to an external device suchas an IT system by using an IT gateway.
For details on an IT gateway, refer to the manual for an IT gateway used.

(2)
(1)
(a)

(a)
(4)

(3)
(a)

(a)
(5)

5

(1) IT system(2) Cloud service(3) IT gateway 1(4) IT gateway 2(5) Real-time Flow Manager(a) Publishing data

Data missing
Refer to the following:
Page 81 Data missing

Considerations• If the execution file of an IT gateway used does not exist or is corrupted, the IT gateway will not start and an error will occur.
• When switching the operating status of a process flow to STOP, an IT gateway stops running immediately. Data notdistributed at this time will not be distributed.
For the specifications when exiting an IT gateway, refer to the manual for the IT gateway.

5 Real-time Flow Manager
5.7 Data Distribution Function

85

5.8

Event History Automatic Output Function

This section shows the function to automatically output event/error information, which is collected from Real-time Flow
Manager, data collectors used in Real-time Flow Manager, and IT gateways, to a specified folder in a CSV file format.
For the output setting, refer to the following:
Page 118 Event history automatic output settingWith an operation check file that is automatically output, it can be confirmed that this function is running normally.

Event history file
The following shows the detailed specifications of an event history file.

Output targets
Output target events are as follows:
Item

TargetEvent typeOperation, system, security

Status (severity)

Major, moderate, minor, warning, information

Problem function

Real-time Flow Manager
Data collector
IT gateway

Event history file format
The format of an event history file to be output is as follows:File format
Item

86

Description

File format

CSV file

Character code

UTF-8 with BOM

File name"RealFlowLog.csv"
After a file is backed up, the date and time information at the time of switching is added to the end of the above file
name.
Date and time information format: MMddHHmmss
MM: Two-digit numerical value from 01 to 12
dd: Two-digit numerical value from 01 to 31
HH: Two-digit numerical value from 00 to 23
mm: Two-digit numerical value from 00 to 59
ss: Two-digit numerical value from 00 to 59
File name example
RealFlowLog1203174055.csv
For details on the backup operation, refer to the following:
Page 89 Backing up an event history file

Extension.csv

Information to be output

1st row: Header row
2nd and later rows: Data row
Up to 39999 data rows are output.
If it is exceeded, the first data row is deleted and the latest event is added to the end of the file.
For details on the header row and each column, refer to the following:
Page 87 Information output to an event history file

5 Real-time Flow Manager
5.8 Event History Automatic Output Function

Information output to an event history file
Colum
n No.

Header row*1

Data row

1

No.

The number (five digits) is output in order from acquired event information.
(Example) For 1: 00001

2

Date and time of occurrence

The date and time is output in the following format:
yyyy/MM/dd H:mm:ss.fff
yyyy: Four-digit numerical value
MM: Two-digit numerical value from 01 to 12
dd: Two-digit numerical value from 01 to 31
H: Numerical value from 0 to 23
mm: Two-digit numerical value from 00 to 59
ss: Two-digit numerical value from 00 to 59
fff: Three-digit numerical value from 000 to 999

3

Event codeAn event code is output in a four-digit hexadecimal number.

4

StatusInformation: 1
Warning: 2
Minor: 3Moderate: 4
Major: 55*1

5

An event occurrence source is output.*1

Problem function

Output in English.

Ex.

Example for outputting an event history file
1

2

3

4

5

No.

Time and Date of Occurrence

Event CodeStatusProblem Function

00001

2021/04/09 9:05:50.012

8006

5

Management Shell

00002

2021/04/10 13:42:33.015

1001

3

CSV File Data collector Version 2 (Edgecross Consortium)

00003

2021/04/10 13:42:45.030

7028

2

Management Shell

00004

2021/04/10 19:21:27.123

8007

5

Management Shell

Output location
The output location of an event history file is as follows:
Item

Specification

Range

Output destination

An event history file can be saved to the following locations:• Local disk
• Shared folder*1*2
A same save location can be specified for the event history automatic output
function of Real-time Flow Manager and Management Shell.
Characters in the Unicode Basic Multilingual Plane (only those that can beused for the WSTRING type) can be specified as the path to a savedestination.*3*4 (Page 545 WSTRING type)

Save destination path length: Up to 234 characters(Including characters from the drive letter to '\' at the endof the path)

*1
*2
*3
*4

When using a remote shared folder, refer to the following:
Page 553 Using a Remote Shared Folder
A network drive (drive assigned by using a Windows function) cannot be used.
Excluding the following characters that cannot be used for file paths of Windows:/ (0x2F), * (0x2A), ? (0x3F), " (0x22), < (0x3C), > (0x3E), | (0x7C)
A space (0x20) and a period (0x2E) cannot be used for the first character.

5 Real-time Flow Manager
5.8 Event History Automatic Output Function

87Operational specifications
The following shows the operational specifications for outputting an event history file.

File output authority
A file is output with the Windows account 'SYSTEM' or a specified user account.
A user account used when outputting a file can be specified in the setting screen. By default, the Windows account 'SYSTEM'
is used.
By specifying a user account for output, a file can be output to a folder accessible to a specific user only.
In addition, by outputting a file to a folder with the encryption enabled, the file can be browsed by a specific user only. For
outputting a file to a remote shared folder or an encrypted folder, refer to either of the following:
Page 553 Using a Remote Shared Folder
Page 71 Using a folder with the encryption attribute enabled
When specifying a user account, the authentication processing may take time due to a network load or failure.
If it takes time and Windows times out, an error occurs.

File output
An event history file is output at the following timings:• Real-time Flow Manager is started.
• The event history automatic output setting is applied (excluding when changing 'enabled' to 'disabled' for output).
• An event occurs within the event history monitoring interval.
If a specified folder does not exist, a folder is created and an event history file is saved to the folder.
In addition, if a file with the same name exists, it is overwritten with the event history file.
If the event history file cannot be saved, the file saving is retried.
Events that occur during a retry are output together when they become available for saving.
If backup of an event history file fails, the file is not output until it succeeds. For details on backup of an event history file, referto the following:
Page 89 Backing up an event history file88

5 Real-time Flow Manager
5.8 Event History Automatic Output FunctionBacking up an event history file
A backup file starts being created when deleting an event history in the "Event History" screen of Real-time Flow Designer.*1
If an error occurs during backup, an event is registered.
For the event codes, refer to the following:
Page 422 Codes for events that occur in Real-time Flow Manager
Backed up files are not deleted from Edgecross Basic Software. (The maximum number of files that can be backed up isdetermined by the file system.)
The date of backup is added to the file name of a backed up file.
For details on the file name, refer to the following:
Page 86 File format*1

The next time an event history file is output, it is backed up before output regardless of whether the event history file output setting isenabled or disabled when deleting an event history.
When changing the save destination folder before backup, an event history file in the folder after the change is backed up.

An example of backup operation is as follows:
(a)

5

*1
(1)
RealFlowLog.csv
(b)
*1

*2

(1)
RealFlowLog.csv(c)*1

RealFlowLog
1127083017.csv*2(1)
RealFlowLog.csv

RealFlowLog
1127170043.csv

RealFlowLog
1127083017.csv(1) Real-time Flow Manager(a) An event history is deleted in the "Event History" screen. (November 26th 12:45:22)(b) An event history is deleted in the "Event History" screen. (November 27th 08:30:17)(c) An event history is deleted in the "Event History" screen. (November 27th 17:00:43)*1*2

The file name of the latest file is always 'RealFlowLog.csv.'
A file is backed up when deleting an event history.

5 Real-time Flow Manager
5.8 Event History Automatic Output Function

89

Operation check file
The following shows the detailed specifications of an operation check file.

Operation check file format
The format of an operation check file is as follows.
Note that an operation check file is not backed up, and one file is used continuously.
Item

Description

File format

Text

Character code

UTF-8 with BOM

File name"RealFlowLogKeepAlive.dat"

Extension.dat

Output location
An operation check file is saved to the same location as an event history file.
Page 87 Output location

Operational specifications
The following shows the operational specifications for outputting an operation check file.

File output authority
Refer to the following:
Page 88 File output authority

File output
If a specified path does not exist, a folder is created and an operation check file is saved to the folder.
If a file with the same name exists, it is overwritten with the operation check file.
An operation check file is updated at the same interval as an event history monitoring interval, but not updated in any of thefollowing cases:• The automatic output of an event history file is disabled in the setting.
• An event history file fails to be saved.
• An operation check file fails to be saved.
• The operation of this function is stopped.

When this function is running normally, the update date and time of an operation check file is updated.
If it is not updated after a while, check if the event history automatic output setting is disabled or an error
occurs.

90

5 Real-time Flow Manager
5.8 Event History Automatic Output Function

Considerations
The following shows the considerations when using the event history automatic output function.
• When opening an event history file in another application while it is editable, the file may fail to be saved. To open the file inanother application, copy and open it.
• When deleting an event history while an event history file cannot be accessed, data not output is deleted without being
saved to the event history file.
• If the event history is updated frequently, such as if events occur frequently, it may take time to output an event history file.
(This also applies to an operation check file.)• If events occur consecutively at short intervals, the order of output to an event history file and the date and time ofoccurrence may change.
• When using a shared folder as a save destination, do not unshare the folder with the output setting enabled.
• Do not save a file with the same name as an event history file to a save destination path. If a file with the same name exists,
it is overwritten with the event history file. (This also applies to an operation check file.)

5• When outputting a file to a folder with the compression attribute enabled, the free space on Windows is determined to be
temporarily insufficient and an error may occur if the free space on the disk is low.
• For outputting a file to a folder with the data encryption enabled, refer to the following: Page 71 Using a folder with theencryption attribute enabled

5 Real-time Flow Manager
5.8 Event History Automatic Output Function

91

5.9

Command Line Interface Function

This section shows the function to perform operations of Real-time Flow Manager on a command basis.
By using this function, Real-time Flow Manager can be operated in an application other than Edgecross Basic Software(hereinafter referred to as 'external software').
This function runs by specifying an argument and executing an execution file (.exe) in external software.

Precautions• This function runs only on an industrial PC where Edgecross Basic Software is installed.
• This function cannot be started multiple times at the same time. If started, the functions started later are terminated with
outputting an error (2001).
• Perform this function with a Windows user account that has accepted the software license agreement for Edgecross Basic
Software.

Version specifications
The version of the command line interface function supported by that of Edgecross Basic Software is as follows:
Edgecross Basic Software version

Command line interface function version

1.26

1

1.27
1.28 or later

2

Operational specifications
This function requests Real-time Flow Manager to perform processing specified with a command and argument (option), thenreturns the result (execution result and exit code).
Item

Description

CommandSpecify 'EdgecrossCLI.exe.'*1

OptionSpecify a command line argument passed when executing 'EdgecrossCLI.exe.'
For details on the options, refer to the following:
Page 97 Option specifications

Execution result

Details on the result for a request to Real-time Flow Manager are returned.
An execution result can be acquired from the standard output in a character string format.
'CRLF' is used as a line feed code in and at the end of a character string.
Details on an execution result differ depending on the first option specified for an option.
For details, refer to the following:
Page 98 Option details

Exit code

The success or failure of a request to Real-time Flow Manager is returned.
• 0: Success• Non-0: Failure
For details on the exit codes, refer to the following:
Page 432 Exit Code List for the Command Line Interface Function*1'.exe' is optional.

Precautions• An execution result is returned as a character string; therefore, it is always displayed with the same content regardless ofthe execution environment (GUI) for a console application.
• An exit code is returned as a numerical value; therefore, a numerical value different from the exit codes (hexadecimal)
listed in the following section may be displayed depending on the execution environment (GUI) for a console application.
(Page 432 Exit Code List for the Command Line Interface Function)

92

5 Real-time Flow Manager
5.9 Command Line Interface Function

Execution examples
The following shows execution examples when using the command prompt.

Success example

(3)

(1)

(2)

(1) Command(2) Option(3) Execution result

Failure example

5

(3)

(1)

(2)

(1) Command(2) Option(3) Execution result (exit code)

5 Real-time Flow Manager
5.9 Command Line Interface Function

93

Execution methods
The following explains the methods for performing this function.
It can be performed by using either of the following:• Command prompt (Page 94 Using the command prompt)• User program (Page 96 Using a user program)

Using the command prompt
The following shows the flow of performing this function when using the command prompt (a standard Windows function) as
external software.

1. Start the command prompt.
2. Enter a (1) command and (2) option to be executed at the command prompt, and press the  key.

(1)

(2)

3. Real-time Flow Manager is requested to perform processing and returns an execution result.
4. The execution result is output to the standard output.

For details on the execution results, refer to the following:
Page 98 Option details

5. An exit code is stored in the environment variable 'errorlevel' defined in Windows.

94

5 Real-time Flow Manager
5.9 Command Line Interface Function

Example of creating a batch file and the execution result
The following shows an example of creating a batch file and the execution result.
• Example of creating a batch fileIn the following example, an exit code is displayed in decimal because it is displayed on the command prompt.
An exit code for a process performed immediately before is stored in the system environment variable 'errorlevel.'@echo off
rem Describes the command.
SET CUI="EdgecrossCLI"
rem Describes an option.
SET ARGUMENTS=/getrfmstatus /allecho ==Display Result=====
echo;
rem Performs the command line interface function and displays its result.

5%CUI% %ARGUMENTS%
echo;
echo ==Display ExitCode==echo;
rem Displays an exit code.
echo EXITCODE: %errorlevel%
pause• Execution result

5 Real-time Flow Manager
5.9 Command Line Interface Function

95

Using a user program
The following shows the flow of performing this function when using a user program as external software.

1. Run a user program created in any programming language.
2. Specify and execute a command and option in the user program.
3. Real-time Flow Manager is requested to perform processing and returns an execution result.
4. The execution result is output to the standard output.
For details on the execution results, refer to the following:
Page 98 Option details

5. The result in the standard output is read in the user program, and the execution result and exit code are acquired.
Example of creating a user program
The following shows an example of creating a user program by using C#.
using System;
using System.Diagnostics;
namespace sample{
class Program{
static void Main(string[] args){// Uses ProcessStartInfo class of System.Diagnostics class.
var processInfo = new System.Diagnostics.ProcessStartInfo();// Creates an object.

processInfo.FileName = "EdgecrossCLI.exe";// Command line interface function nameprocessInfo.Arguments = "/getrfmstatus /all";// Specifies an option.

// Since the following two lines redirect the content of the standard output output by executing 'EdgecrossCLI.exe' to the user program side,// configures this setting to acquire the standard output output by executing 'EdgecrossCLI.exe.'
processInfo.UseShellExecute = false;
processInfo.RedirectStandardOutput = true;
processInfo.CreateNoWindow = true;

var process = Process.Start(processInfo);
process.WaitForExit();// Redirects the standard output of a command.

// Whether to start a process in the window// Executes the command and writes the execution result to the standard output.

// Waits until the process ends.

int exitcode = process.ExitCode;// Acquires a command exit code.

if (0 == exitcode){// Processing on success// Since the execution result is stored in the standard output stream,// analyzes the content stored in the variable 'output' and performs processing according to the result.
// Reads the redirected standard output on the user program side after the process ends.
var output = process.StandardOutput.ReadToEnd();
Console.WriteLine(output);// Reads the standard output.

// Displays the command execution result.

}else{// Processing on failure// Displays a message indicating that the processing has failed.
Console.WriteLine ("An error has occurred. {0:x}", exitcode);}
process.Close();// Performs Close of the process.

}
}
}

96

5 Real-time Flow Manager
5.9 Command Line Interface Function

Option specifications
The following explains the specifications of options specified as arguments.
Specify options according to the following format:• EdgecrossCLI.exe(space)[first option](space)[second option](space)[third option...]Item

Description

EdgecrossCLI.exe

The command for performing the command line interface function.
'.exe' is optional.

[First option]*1(required item)

The name of processing requested from Real-time Flow Manager.
For the option list, refer to the following:
Page 97 First option list

[Second option] and later*1

The second option and later must be specified according to the first option.
The number of options specified for the second option and later differs depending on the content of the first option.
For details, refer to the specifications of a specified first option.

*1

Case-sensitive

5

First option list
The following table lists the first options that can be specified.
OptionOperation name

Description

Reference

/?

Help

Help on the method for using the command line interface function
is returned.

Page 98 Help (/?)/ver

Function version acquisition

The version of the command line interface function is returned.

Page 99 Function version
acquisition (/ver)/getrfmstatus

Process flow operating statusacquisition

The operating status of a specified process flow is acquired from
Real-time Flow Manager.

Page 100 Process flow
operating statusacquisition (/getrfmstatus)/runrfm

Process flow operation start

Real-time Flow Manager is requested to start a specified process
flow.

Page 103 Process flow
operation start (/runrfm)/stoprfm

Process flow operation stop

Real-time Flow Manager is requested to stop a specified process
flow.

Page 105 Process flow
operation stop (/stoprfm)

5 Real-time Flow Manager
5.9 Command Line Interface Function

97

Option details
The following explains the option details.

Help (/?)
The following explains the specifications and an execution example of this operation.

Specifications
Item

Description

Operation nameHelp

Overview

Help on the method for using the command line interface function is returned.

First option/?

Execution result

On success
Help on the method for using the command line interface function is returned.
On failure
An exit code is returned.

Exit code

The exit codes when performing this operation are as follows:• 0: Succeeded• Non-0: Error occurredIf a second option or later error (1001H) occurs
This error occurs when the second option is specified.
Do not specify an option for the second option and later.
If an error other than a second option or later error (1001H) occurs
Refer to the following:
Page 432 Exit Code List for the Command Line Interface Function

Execution example
The following shows an execution example when using the command prompt.

98

5 Real-time Flow Manager
5.9 Command Line Interface Function

Function version acquisition (/ver)
The following explains the specifications and an execution example of this operation.

Specifications
Item

Description

Operation name

Function version acquisition

Overview

The version of the command line interface function is returned.
For the version of the command line interface function supported by that of Edgecross Basic Software, refer to thefollowing:
Page 92 Version specificationsFirst option/verExecution result

On success
The version of the command line interface function is returned.
On failure
An exit code is returned.

Exit code

The exit codes when performing this operation are as follows:• 0: Succeeded• Non-0: Error occurredIf a second option or later error (1001H) occurs
This error occurs when the second option is specified.
Do not specify an option for the second option and later.
If an error other than a second option or later error (1001H) occurs
Refer to the following:
Page 432 Exit Code List for the Command Line Interface Function

5

Execution example
The following shows an execution example when using the command prompt.

5 Real-time Flow Manager
5.9 Command Line Interface Function99Process flow operating status acquisition (/getrfmstatus)
The following explains the specifications and execution examples of this operation.

Specifications
Item

Description

Operation name

Process flow operating status acquisition

Overview

The operating status of a specified process flow is acquired from Real-time Flow Manager.

First option/getrfmstatus

Second option

Specify any of the following for a target process flow type and process flow number.
• /all: All process flow types and process flow numbers• /logging={0}*1,*2: Data logging flow
• /diagnosis={0}*1,*2: Data diagnosis flow
When not specifying any item for the second option, '/all' is regarded as specified.

Third option

Specify a target process flow type and process flow number only when specifying '/logging={0}' or '/diagnosis={0}' forthe second option.
When specifying '/logging={0}' for the second option
Only '/diagnosis={0}' can be specified.*1,*2
When specifying '/diagnosis={0}' for the second option
Only '/logging={0}' can be specified.*1,*2

Execution result

On success
The operating status of a specified process flow type is returned.
When specifying multiple process flow types, the operating statuses are returned in the following order regardless of a
specified order.
First line: Data logging flow
Second line: Data diagnosis flow
In addition, the operating statuses of process flows are returned with delimited by commas in ascending order of
specified process flow numbers.
0: Not set
1: STOP state
2: In transition to RUN
3: RUN state
4: In transition to STOP
On failure
An exit code is returned.

Exit code

The exit codes when performing this operation are as follows:• 0: Succeeded• Non-0: Error occurredIf a second option or later error (1001H) occurs
Refer to the following:If "1001" is displayed for the exit code
If an error other than a second option or later error (1001H) occurs
Refer to the following:
Page 432 Exit Code List for the Command Line Interface Function

*1
*2

100

For {0}, specify a process flow number in decimal.
When specifying '/logging' or '/diagnosis' only, all data logging flows or data diagnosis flows are regarded as specified.
When specifying multiple process flow numbers, use a comma as a delimiter.

5 Real-time Flow Manager
5.9 Command Line Interface FunctionPrecautions• If "1001" is displayed for the exit code, the following are the possible causes. Specify a correct option or value.
Exit code

Error name

Error description

1001H

Second option or later error

An item other than '/all,' '/logging={0},' and '/diagnosis={0}' is specified for the second
option.
'/logging={0}' is specified for the second option and an item other than '/diagnosis={0}' is specified for the third option.
'/diagnosis={0}' is specified for the second option and an item other than '/logging={0}' is specified for the third option.
'/all' is specified for the second option and any item is specified for the third option.
'/logging={0}' or '/diagnosis={0}' is specified, but no process flow number is specified
for {0}.
Any item is specified for the fourth option.
Two or more same process flow numbers are specified for {0}.
'0' or less or '33' or more is specified as a process flow number for {0}.

5Process flow numbers for {0} are not specified with numbers or commas.

5 Real-time Flow Manager
5.9 Command Line Interface Function

101

Execution examples
The following shows execution examples when using the command prompt if the operating statuses of process flows are as
follows:
The operating statuses of data logging flows: No.1 to 4 are RUN, No.5 and 6 are STOP, and No.7 to 32 are not set.
The operating statuses of data diagnosis flows: No.1 to 3 are RUN, No.4 to 6 are STOP, and No.7 to 32 are not set.
• When specifying '/all' for the second option

(2)

(1)

(1) Data logging flow(2) Data diagnosis flow

• When specifying '/logging' for the second option• When specifying '/diagnosis=1,3,5' for the second option• When specifying '/logging=1,4,6,10' for the second option and '/diagnosis=1,3,5' for the third option

(2)

(1)

(1) Data logging flow(2) Data diagnosis flow

102

5 Real-time Flow Manager
5.9 Command Line Interface FunctionProcess flow operation start (/runrfm)
The following explains the specifications and an execution example of this operation.

Specifications
Item

Description

Operation name

Process flow operation start

Overview

Real-time Flow Manager is requested to start a specified process flow.

First option/runrfmSecond option

Specify any of the following for a target process flow type and process flow number.
• /all: All process flow types and process flow numbers• /logging={0}*1,*2: Data logging flow
• /diagnosis={0}*1,*2: Data diagnosis flow
When not specifying any item for the second option, '/all' is regarded as specified.

Third option

Specify a target process flow type and process flow number only when specifying '/logging={0}' or '/diagnosis={0}' forthe second option.
When specifying '/logging={0}' for the second option
Only '/diagnosis={0}' can be specified.*1,*2
When specifying '/diagnosis={0}' for the second option
Only '/logging={0}' can be specified.*1,*2

Execution result

On success'0000' is returned.
On failure
An exit code is returned.

Exit code

The exit codes when performing this operation are as follows:• 0: Succeeded• Non-0: Error occurredIf a second option or later error (1001H) occurs
Refer to the following:If "1001" is displayed for the exit code
If an error other than a second option or later error (1001H) occurs
Refer to the following:
Page 432 Exit Code List for the Command Line Interface Function

*1
*2

5

For {0}, specify a process flow number in decimal.
When specifying '/logging' or '/diagnosis' only, all data logging flows or data diagnosis flows are regarded as specified.
When specifying multiple process flow numbers, use a comma as a delimiter.

5 Real-time Flow Manager
5.9 Command Line Interface Function

103Precautions• This operation returns only the result of whether a request to change the operating status to RUN succeeds; therefore, atime lag occurs before the operating status of a specified process flow switches to RUN. After performing this operation,
execute the operating status acquisition command to monitor and check whether the operating status has actually switched
to RUN.
• If "1001" is displayed for the exit code, the following are the possible causes. Specify a correct option or value.
Exit code

Error name

Error description

1001H

Second option or later error

An item other than '/all,' '/logging={0},' and '/diagnosis={0}' is specified for the second
option.
'/logging={0}' is specified for the second option and an item other than '/diagnosis={0}' is specified for the third option.
'/diagnosis={0}' is specified for the second option and an item other than '/logging={0}' is specified for the third option.
'/all' is specified for the second option and any item is specified for the third option.
'/logging={0}' or '/diagnosis={0}' is specified, but no process flow number is specified
for {0}.
Any item is specified for the fourth option.
Two or more same process flow numbers are specified for {0}.
'0' or less or '33' or more is specified as a process flow number for {0}.
Process flow numbers for {0} are not specified with numbers or commas.

Execution example
The following shows an execution example when using the command prompt.
• When specifying '/diagnosis=1,3,5' for the second option

104

5 Real-time Flow Manager
5.9 Command Line Interface FunctionProcess flow operation stop (/stoprfm)
The following explains the specifications and an execution example of this operation.

Specifications
Item

Description

Operation name

Process flow operation stop

Overview

Real-time Flow Manager is requested to stop a specified process flow.

First option/stoprfm

Second option

Specify any of the following for a target process flow type and process flow number.
• /all: All process flow types and process flow numbers• /logging={0}*1,*2: Data logging flow
• /diagnosis={0}*1,*2: Data diagnosis flow
When not specifying any item for the second option, '/all' is regarded as specified.

Third option

Specify a target process flow type and process flow number only when specifying '/logging={0}' or '/diagnosis={0}' forthe second option.
When specifying '/logging={0}' for the second option
Only '/diagnosis={0}' can be specified.*1,*2
When specifying '/diagnosis={0}' for the second option
Only '/logging={0}' can be specified.*1,*2

Execution result

On success'0000' is returned.
On failure
An exit code is returned.

Exit code

The exit codes when performing this operation are as follows:• 0: Succeeded• Non-0: Error occurredIf a second option or later error (1001H) occurs
Refer to the following:If "1001" is displayed for the exit code
If an error other than a second option or later error (1001H) occurs
Refer to the following:
Page 432 Exit Code List for the Command Line Interface Function

*1
*2

5

For {0}, specify a process flow number in decimal.
When specifying '/logging' or '/diagnosis' only, all data logging flows or data diagnosis flows are regarded as specified.
When specifying multiple process flow numbers, use a comma as a delimiter.

5 Real-time Flow Manager
5.9 Command Line Interface Function

105Precautions• This operation returns only the result of whether a request to change the operating status to STOP succeeds; therefore, atime lag occurs before the operating status of a specified process flow switches to STOP. After performing this operation,
execute the operating status acquisition command to monitor and check whether the operating status has actually switchedto STOP.
• If "1001" is displayed for the exit code, the following are the possible causes. Specify a correct option or value.
Exit code

Error name

Error description

1001H

Second option or later error

An item other than '/all,' '/logging={0},' and '/diagnosis={0}' is specified for the second
option.
'/logging={0}' is specified for the second option and an item other than '/diagnosis={0}' is specified for the third option.
'/diagnosis={0}' is specified for the second option and an item other than '/logging={0}' is specified for the third option.
'/all' is specified for the second option and any item is specified for the third option.
'/logging={0}' or '/diagnosis={0}' is specified, but no process flow number is specified
for {0}.
Any item is specified for the fourth option.
Two or more same process flow numbers are specified for {0}.
'0' or less or '33' or more is specified as a process flow number for {0}.
Process flow numbers for {0} are not specified with numbers or commas.

Execution example
The following shows an execution example when using the command prompt.
• When specifying '/logging=1,3,5' for the second option

106

5 Real-time Flow Manager
5.9 Command Line Interface Function

6Real-time Flow Designer

Real-time Flow Designer is software that sets parameters of Real-time Flow Manager.

6.1

Overview

This section shows the startup method and screen configuration of Real-time Flow Designer.

Startup method
Operating procedure

1. Perform either of the following operations:• Start Real-time Flow Designer from "Edgecross Basic Software" in Windows Start.
• Double-click the shortcut icon of 'Real-time Flow Designer' on the desktop.
Parameters of Real-time Flow Manager are read and applied to Real-time Flow Designer when starting Real-time Flow
Designer.

6
When starting Real-time Flow Designer for the first time, the screen to confirm the software license agreement
appears. (It will not appear if the license agreement has already been accepted in Management Shell
Explorer.)

Screen configuration
(1)

(2)

(3)

(1) Menu bar(2) Edit item tree(3) Setting edit screen

6 Real-time Flow Designer
6.1 Overview

107

Operations in the edit item tree
Setting contents of each screen are displayed in a tree in the edit item tree.
(1)
(2)

(3)

(1) Root(2) Setting category(3) ItemSelecting an item
Items are displayed by double-clicking each setting category.
Selecting a displayed item shows its edit screen in the setting edit screen.

Adding an item
Select and right-click a setting category or item, and select [Add Item].
When an item is successfully added, it is automatically selected and its edit screen appears.

Deleting an item
Select and right-click an item to delete, and select [Delete Item].
To delete all items included in a setting category, select and right-click the setting category, and select [Delete Item].

Initializing parameter settings
To initialize parameter settings, select and right-click the root and select [Initialize All Settings.].

108

6 Real-time Flow Designer
6.1 Overview

Home screen
This screen appears when starting Real-time Flow Designer.
All setting items are displayed.

Window
Select "Real-time Flow Manager Parameter" in the edit item tree.

6

Displayed items
Menu configuration
Menu name
File

Edit

Description

Reference

Read from FileTo read setting information saved as a setting file.*1,*2,*3,*4

Save in FileTo save the current setting status as a setting file.*5,*6,*7



Exit Real-time Flow Designer

To exit Real-time Flow Designer.



Add Item

To add an item to a setting selected in the edit item tree.

Delete ItemTo delete an item selected in the edit item tree.



View

Switch Display Language

To switch the display languages of Real-time Flow
Designer and Management Shell Explorer for the next
startup (Japanese/English/Simplified Chinese).

Real-time Flow

Process Flow Start/Stop

To switch the operating status of a process flow of Realtime Flow Manager.

Page 333 "Process Flow Start/Stop"
screenDiagnostics

Real-time Flow Manager Diagnostics

To monitor the operating status of Real-time Flow
Manager.

Page 332 Real-time Flow Manager
diagnosis

Help

Data collector

To display the list of installed data collectors.

Page 120 Data collector list

To display the list of installed IT gateways.

Page 121 IT gateway list

To display the manual (Edgecross Basic Software forWindows User's Manual) in PDF format.



To display the version information and license informationof Real-time Flow Designer.



IT Gateway List
ManualEdgecross Basic
Software User's
ManualVersion Information

6 Real-time Flow Designer
6.1 Overview

109

*1
*2

*3

*4
*5
*6
*7

When a password is set for a file, the file can be read by entering the password in the displayed "Password input" screen.
If the MAC address of a network adapter for an industrial PC when reading a setting file is different from the one when the setting file issaved, the data distribution setting (MQTT) or edge application diagnosis (MQTT) setting must be configured again by the procedureshown below.
The following are the cases:- Reading a setting file saved to an industrial PC in another industrial PC- Changing a network device for an industrial PC
Reconfiguration procedure Output a publishing data definition file in the [Definition Output] tab in the "Data Distribution Setting" or "Edge Application Diagnosis
Setting" screen. (Page 158 Data Distribution Setting (MQTT), Page 173 Edge Application Diagnosis (MQTT) Setting) Click the [OK] button to fix the setting.
 Click the [OK] button in the process flow setting to fix the setting. (Page 132 Data logging flow setting screen, Page 136 Datadiagnosis flow setting screen) Click the [Apply] button.
 Use the output publishing data definition file to set the connected edge application again.
Parameters of Real-time Flow Manager are updated by the above procedure.
This update is not applied to the original setting file.
Select [File]  [Save in File] to save the setting file again as necessary.
If a value is set for "Client ID at sending" or "Publishing Data topic name" in the data distribution setting (MQTT) or edge application
diagnosis (MQTT) setting, change the set value after reading a setting file. (A same value cannot be set for Real-time Flow Manager
installed on an industrial PC in which a setting file is saved and that installed on one in which the setting file is read.)
When importing a setting file, which is saved in Real-time Flow Designer with Edgecross Basic Software version 1.23 or earlier, into
Real-time Flow Designer in which the event history automatic output setting is configured, the setting is deleted.
A password can be set in the displayed "Password setting" screen. This can prevent leakage of the information in a setting file.
Up to 200 characters can be set for the file path of a file name.
Depending on a data collector used, some setting information may not be saved. For details, refer to the manual for a data collector
used.

Screen configuration
Item

Description

Reference[Target Device Setting]buttonClick this to display the access target device setting list.

Page 124 Access target device setting
list[Data Logging Flow
Setting] button

Click this to display the data logging flow setting list.

Page 131 Data logging flow setting list

[Data Diagnosis Flow
Setting] button

Click this to display the data diagnosis flow setting list.

Page 134 Data diagnosis flow setting list

[Discard Edit] button

Click this to discard the settings in Real-time Flow
Designer.

[Apply] button

Click this to update the parameters of Real-time Flow
Manager with the settings of Real-time Flow Designer.

[Data Logging Phase] tab[Data Diagnosis Phase]
tab

110

6 Real-time Flow Designer
6.1 Overview

Process flow setting
The following shows the screen for setting each process flow.

Window
Select "Process Flow Setting" in the edit item tree.

6

Displayed items
Item

Description[Home] button

Click this to display the home screen.
Page 109 Home screen[Data Logging Flow Setting] button

Click this to display the data logging flow setting list.
Page 131 Data logging flow setting list

[Data Diagnosis Flow Setting] button

Click this to display the data diagnosis flow setting list.
Page 134 Data diagnosis flow setting list

6 Real-time Flow Designer
6.1 Overview

111

Common setting
The following shows the common settings of Real-time Flow Designer.

Window
Select "Common Setting" in the edit item tree.

Displayed items
Item

Description[Home] button

Click this to display the home screen.
Page 109 Home screen[Operation setting] button

Click this to display the "Operation setting" screen.
Page 113 Operation setting[DB Connection Common Setting] button

Click this to display the "DB Connection Common Setting" screen.
Page 116 DB connection common setting[File Saving Common Setting] button

Click this to display the "File Saving Common Setting" screen.
Page 117 File saving common setting[Event History Automatic Output Setting] button

Click this to display the "Event History Automatic Output Setting" screen.
Page 118 Event history automatic output setting

112

6 Real-time Flow Designer
6.1 Overview

Operation setting
The following shows the procedure for setting the operating status of all process flows of Real-time Flow Manager to RUN or
STOP when starting an industrial PC.

Operating procedure

1. Click the [Operation setting] button in the "Common Setting" screen.
2. Set the operating status of all process flows.
3. Click the [OK] button.
Precautions• When changing the operating status after applying parameters of Real-time Flow Manager, switch it in Real-time Flow
Designer. (Page 332 Real-time Flow Manager diagnosis)• Set the operating status of all process flows when starting an industrial PC to RUN in either of the following cases only:
Executing a data logging flow only
Using only the data diagnosis plug-in run function as a data diagnosis function• When performing data diagnosis such as MQTT cooperation for which the order of startup is determined between an edge
application and Real-time Flow Manager, do not set the operating status of all process flows when starting an industrial PC
to RUN.
If the operating status is in the RUN state but an edge application for data diagnosis cannot perform real-time data
diagnosis, an error occurs.
• The time until the operating status of a process flow switches to RUN increases in proportion to the number of process
flows. In addition, the timing of switching to RUN varies widely.
When adding a process flow, check if there is any problem, for example, with the timing of cooperating with an edge
application when starting an industrial PC.
• Disable the fast startup function. If it is enabled, an industrial PC is not shut down completely, and a process flow may not
run properly when starting the industrial PC after shutdown. For the procedure for disabling the fast startup function, refer tothe following:
Page 114 Procedure for disabling the fast startup function

6 Real-time Flow Designer
6.1 Overview

113

6Procedure for disabling the fast startup function
The following shows the procedure for disabling the fast startup function.

Operating procedure

1. Open the "Power Options" screen, and click [Choose what the power button does].
[Control Panel]  [System and Security]  [Power Options]

2. Click [Change settings that are currently unavailable].

114

6 Real-time Flow Designer
6.1 Overview

3. Unselect the checkbox of "Turn on fast startup" under "Shutdown settings," and click the [Save changes] button.

6

6 Real-time Flow Designer
6.1 Overview

115

DB connection common setting
The following shows the screen for setting the common settings when connecting to a database.
To set the DB connection common setting, a database must be set in advance.
Page 529 Database Setup

Window
Click the [DB Connection Common Setting] button in the "Common Setting" screen.

Displayed items
Item

Description

Data Source Name

Set the data source name of a database (1 to 32 characters).

User Name

Set the user name of a database (1 to 32 characters).

Password

Set the password for a database (6 to 32 characters).

116

6 Real-time Flow Designer
6.1 Overview

File saving common setting
The following shows the screen for setting a user name and password used for accessing a folder with restricted access.

Window
Click the [File Saving Common Setting] button in the "Common Setting" screen.

Displayed items
Item

Description

User Name*1*2

Set a Windows user account (up to 127 characters).
By entering it in either of the following formats, a domain name can be included.*3*4• [Domain name]\[User name]• [User name]@[Domain name]
When specifying a local user of an industrial PC on which Edgecross Basic Software is installed, set it in any of thefollowing formats:• [Computer name]\[User name]• .\[User name]• [User name]

Password*1*2

Set a password to authenticate a Windows user account (up to 127 characters).

[Authentication Test] button

Click this to perform the authentication test for a user account to Windows by using a set user name and password.

*1
*2

*3

*4

6

If changing a set password for a user account in Windows, set it again.
To prevent eavesdropping and falsification of data, it is recommended to use a user account with a password satisfying complexity
requirements.
The complexity requirements can be checked by the following procedure: Start the local security policy of Windows.
 Double-click [Security Settings]  [Account Policies]  [Password Policy]  [Password must meet complexity requirements].
 Select the [Explain] tab in the "Password must meet complexity requirements Properties" screen.
When '@' and '\' are included, the format is determined as [User name]@[Domain name].
When multiple pieces of '@' or '\' are included, the first '@' ('\' if there is no '@') is used as a delimiter between a domain name and a user
name.
Do not specify a local user of another industrial PC on the network.

Precautions• When exporting a setting file while a local user of an industrial PC is set for "User Name" and importing the setting file inanother industrial PC, the local user may not be authenticated in the import destination industrial PC. Set it again after
import as necessary.
• The authentication test is performed on a local computer. Therefore, even when specifying another industrial PC on the
network for a save destination folder, the test is not performed on the industrial PC.
• When repeating the following operations if a password is incorrect, a user account may be locked out. If an error occurs
due to these operations, check if a password is correct.
- Apply the setting.
- Start Real-time Flow Manager or start the operation.
- Perform the authentication test.

6 Real-time Flow Designer
6.1 Overview

117Event history automatic output setting
The following shows the screen for settings required to automatically output an event history.

Window
Click the [Event History Automatic Output Setting] button in the "Common Setting" screen.

Displayed items
Item

Description

Enable automatic output

Select the checkbox to automatically output an event history to a file.*1

Output Target Setting*2
Save Destination Folder
Setting

*1
*2
*3

118

Select the checkbox of an event to be output.
Save Destination Folder*2

Set a save destination folder (1 to 233 characters).
It can also be set in the "Select Folder" screen displayed by clicking the [...] button.

Saving File Path

The saving file path based on the setting for "Save Destination Folder" is displayed.

When the accessauthority of the savedestination folder islimited, please specify theuser to access.*2

Select the checkbox if access is granted to the save destination folder for an event history file.*1[User Account Setting]button*3

Click this to display the "User Account Setting" screen.
Page 119 User account setting screen
The setting status of the "User Account Setting" screen is displayed to the right of this button.

When fixing the settings without selecting the checkbox, the settings in the "User Account Setting" screen are deleted.
Can be selected or set when selecting the checkbox of "Enable automatic output."
Can be clicked when selecting the checkboxes of "Enable automatic output" and "When the access authority of the save destination
folder is limited, please specify the user to access."

6 Real-time Flow Designer
6.1 Overview

User account setting screen
The following shows the screen for setting a user name and password used for accessing a folder with restricted access.

Window

Displayed items
Refer to the following:
Page 149 User account setting

Precautions
Refer to the following:

6

Page 149 User account setting

6 Real-time Flow Designer
6.1 Overview

119

Data collector list
The following shows the screen for displaying the list of installed data collectors.

Window
Select [Help]  [Data collector].

(1)

Displayed items
Item

Description(1) Data collector list

Information on all installed data collectors is displayed.

Developer

The developer of a data collector is displayed.

Data collector Name

The name of a data collector is displayed.

Data collector Version

The data collector version of a data collector is displayed.

Data collector Specifications Version

The data collector specification version of a data collector is displayed. (Third decimal place and the subsequent ones
are rounded down.)

Supplemental Information

The supplementary information on a data collector is displayed.

Collect

The availability of data collection in a data collector is displayed.
• Supported: Collectible• Not Supported: Uncollectible

Read

The availability of data reading in a data collector is displayed.
• Supported: Readable• Not Supported: Unreadable

Write

The availability of data writing in a data collector is displayed.
• Supported: Writable• Not Supported: Unwritable

Supported Languages

Languages that are supported by a data collector are displayed.

[Update to Latest State] button

Click this to update the "Data collector List" screen.

• When multiple data collectors with different data collector versions are installed, only a data collector withthe latest data collector version is displayed.
• By clicking the [Update to Latest State] button, the access target device information can be updated with thelatest data collector contents.

120

6 Real-time Flow Designer
6.1 Overview

IT gateway list
The following shows the screen for displaying the list of installed IT gateways.

Window
Select [Help]  [IT Gateway List].

(1)

6
Displayed items
Item

Description(1) IT gateway list

Information on all installed IT gateways is displayed.

Developer

The developer of an IT gateway is displayed.

IT Gateway Name

The name of an IT gateway is displayed.

IT Gateway Version

The IT gateway version of an IT gateway is displayed.

Supplemental Information

The supplementary information on an IT gateway is displayed.

IT Gateway Type(IT Gateway Specification Version)

The IT gateway type and IT gateway specification version of an IT gateway are displayed. (Third decimal place and thesubsequent ones are rounded down.)

Supported Languages

The display languages that are supported by an IT gateway are displayed.

[Update to Latest State] button

Click this to update the "IT Gateway List" screen.

By clicking the [Update to Latest State] button, the IT gateway setting information can be updated with thelatest IT gateway contents.

6 Real-time Flow Designer
6.1 Overview

121

Location of use search result screen
The locations where setting items (access target device settings or IT gateway settings) are used are displayed in a list.

Window
For searching for the location of use for an access target device setting
Select and right-click a row in the "Target Device Setting List" screen, and select [Search of the location of use for Target
Device setting].

For searching for the location of use for an IT gateway setting
Select and right-click a row in the "IT Gateway Setting List" screen, then select [Search of the location of use for IT Gateway
setting].

(1)

Displayed items
Item

Description(1) List of locations of
use*1

Type

The type of the location where the setting item is used is displayed.

Location of use

The location where the setting item is used is displayed.

Details
Always display on foreground*1

The detail of the location where the setting item is used is displayed.
Select the checkbox to display this screen in the foreground.
If multiple applications to be displayed in the foreground are running, one of them is displayed in theforeground.

By double-clicking a row, the location where the setting item is used can be referenced.

• Only the 1000 displayed items can be sorted.
• The display language of this screen is the same as that of Real-time Flow Designer or Management Shell
Explorer when displaying this screen for searching for the location of use.

Precautions• If a setting item is being edited, it may not be searched for properly or its location of use may not be referenced properly.
• This screen can be displayed only one. If searching for another location of use in Real-time Flow Designer or Management
Shell Explorer when this screen is already displayed, the display contents will be updated.
• Even if switching the display language of Real-time Flow Designer or Management Shell Explorer while this screen isdisplayed, that of this screen is not switched.

122

6 Real-time Flow Designer
6.1 Overview

Common operation
The following shows the common operations of Real-time Flow Designer.

Data setting in the data selection control tree
The following shows the procedure for easily assigning data to a single item such as a data collection result or constant.

Operating procedure

1. Click the data entry cell.
(Example) "Data Extraction Setting" screen

6
2. Select data to set.
Item

Description

Data Collection Result(Process name of datacollection)*1(Name of collection data)*2

Set selected data.

Data Modification Result(Process name of data
modification)*1(Name of output data)*2

Set selected data.

Data Diagnosis Result(Process name of data
diagnosis)*1(Name of output data)*2

Set selected data.

Constant*2[Integer]

The "Integer Type Constant Setting" screen appears.

[Float]The "Float Type Constant Setting" screen appears.

[String [ASCII]]

The "String [ASCII] Type Constant Setting" screen appears.

[String [UNICODE]]The "String [UNICODE] Type Constant Setting" screen
appears.

*1*2

Not displayed if the process name of the previous process is not set.
Not displayed if a data type that cannot be combined is selected.

Setting constants
The following shows the procedure for setting a constant to use as data.

Operating procedure

1. Click "[Integer]," "[Float]," "[String [ASCII]]," or "[String [UNICODE]]" in the data selection control tree.
2. Enter a setting value, and click the [OK] button.

6 Real-time Flow Designer
6.1 Overview

123

6.2

Access Target Device SettingThis section shows the procedure and screen for selecting a data collector to use and setting an access target device.

Operating procedure

1. Select "Target Device Setting" in the edit item tree.
The access target device setting list appears. (Page 124 Access target device setting list)

2. Select a row in which the access target device setting is not configured in the access target device setting list, and click
the [Edit] button.
The "Select Data collector" screen appears. (Page 125 Data collector selection screen)

When selecting a row in which the access target device setting is configured, the "Target Device Setting"screen appears instead of the "Select Data collector" screen.

3. Select a data collector to use in the "Select Data collector" screen, and click the [OK] button.
The "Target Device Setting" screen appears. (Page 126 Access target device setting screen)

Access target device setting list

(1)

Displayed items
Item

Description[Home] button

Click this to display the home screen.
Page 109 Home screen(1) Access target device setting list*1

Target Device Name

The name of an access target device set in the "Target Device Setting" screen
is displayed.

Comment

A comment set in the "Target Device Setting" screen is displayed.

Data collector

The name of a data collector selected in the "Select Data collector" screen isdisplayed.

Settings

The setting contents of a data collector set in the "Target Device Setting"screen are displayed.

[Edit] button

Click this to display the "Select Data collector" screen when selecting a row inwhich the access target device setting is not configured.
Page 125 Data collector selection screen
Click this to display the "Target Device Setting" screen when selecting a row inwhich the access target device setting is configured.
Page 126 Access target device setting screen[Delete] button

Click this to delete the setting of a selected row.

124

6 Real-time Flow Designer
6.2 Access Target Device Setting

*1

The location where the access target device setting of a selected row is used can be checked in the "Location of use search result"screen displayed by selecting and right-clicking the row then selecting [Search of the location of use for Target Device setting].
Page 122 Location of use search result screen

Data collector selection screen

6
Displayed items
Item

Description

Data collector Name

A data collector name, data collector version, and developer are displayed.

Collect

The availability of data collection in a data collector is displayed.
• Supported: Collectible• Not Supported: Uncollectible

Write

The availability of data writing in a data collector is displayed.
• Supported: Writable• Not Supported: Unwritable[OK] button

Click this to display the "Target Device Setting" screen.
Page 126 Access target device setting screen

6 Real-time Flow Designer
6.2 Access Target Device Setting125

Access target device setting screen(1)

Displayed items
Item

Description

Setting Name*1

Set the name of an access target device setting (1 to 32 characters).
• The following are displayed to avoid name duplication by default.
Dev01, Dev02, Dev03, ...

Comment

Set a comment (up to 100 characters).

(1) Access target device setting
information

Set communication parameters.
For details, refer to the manual for a data collector used.

*1

126

The same name as that of an access target device setting already set cannot be used.

6 Real-time Flow Designer
6.2 Access Target Device Setting

6.3

IT Gateway SettingThis section shows the procedure and screen for selecting and setting an IT gateway to use.

Operating procedure

1. Select "IT Gateway Setting" in the edit item tree.
The IT gateway setting list appears. (Page 127 IT gateway setting list)

2. Select a row in which the IT gateway setting is not configured in the IT gateway setting list, and click the [Edit] button.
The "IT Gateway Selection" screen appears. (Page 128 IT gateway selection screen)

When selecting a row in which the IT gateway setting is configured, the "IT Gateway Setting" screen appears
instead of the "IT Gateway Selection" screen.

3. Select an IT gateway to use in the "IT Gateway Selection" screen, and click the [OK] button.
The "IT Gateway Setting" screen appears. (Page 129 IT gateway setting screen)

IT gateway setting list

6(1)

Displayed items
Item

Description[Home] button

Click this to display the home screen.
Page 109 Home screen(1) IT gateway setting list*1

Setting Name

A setting name set in the "IT Gateway Setting" screen is displayed.

Comment

A comment set in the "IT Gateway Setting" screen is displayed.

IT Gateway

The name of an IT gateway selected in the "IT Gateway Selection" screen isdisplayed.

IT Gateway TypeThe type of an IT gateway selected in the "IT Gateway Selection" screen isdisplayed.

Settings

The setting contents of an IT gateway set in the "IT Gateway Setting" screen
are displayed.

[Edit] button

Click this to display the "IT Gateway Selection" screen when selecting a row inwhich the IT gateway setting is not configured.
Page 128 IT gateway selection screen
Click this to display the "IT Gateway Setting" screen when selecting a row inwhich the IT gateway setting is configured.
Page 129 IT gateway setting screen[Delete] button

Click this to delete the setting of a selected row.

6 Real-time Flow Designer
6.3 IT Gateway Setting

127

*1

The location where the IT gateway setting of a selected row is used can be checked in the "Location of use search result" screen
displayed by selecting and right-clicking the row then selecting [Search of the location of use for IT Gateway setting].
Page 122 Location of use search result screen

IT gateway selection screen

Displayed items
Item

Description

IT Gateway Name

An IT gateway name, IT gateway version, and developer are displayed.

IT Gateway Type*1

Select an IT gateway type.

[OK] button*2

Click this to display the "IT Gateway Setting" screen.
Page 129 IT gateway setting screen

*1

*2

128

Depending on a supported IT gateway I/F, any of the following items can be selected.
Historical data file access I/F: Data Storing
Real-time data publishing I/F-G: Data Distribution
Model access I/F-G or data access I/F-G: Model Data AccessCannot be clicked when selecting "Model Data Access" for "IT Gateway Type."

6 Real-time Flow Designer
6.3 IT Gateway SettingIT gateway setting screen(1)

Displayed items
Item

Description

Setting Name*1

Set the name of an IT gateway setting (1 to 32 characters).
• The following are displayed to avoid name duplication by default.
Gateway01, Gateway02, Gateway03, ...

Comment

Set a comment (up to 100 characters).

(1) Destination parameter setting

Set destination parameters.
For details, refer to the manual for an IT gateway used.

*1

6

The same name as that of an IT gateway setting already set cannot be used.

6 Real-time Flow Designer
6.3 IT Gateway Setting

129

6.4

Data Logging Flow SettingThis section shows the procedure and screen for setting a data logging flow.

Operating procedure

1. Select "Data Logging Flow Setting" in the edit item tree.
The data logging flow setting list appears. (Page 131 Data logging flow setting list)

2. Click the [Edit] button in the data logging flow setting list.
The "Data Logging Flow Setting" screen appears. (Page 132 Data logging flow setting screen)

130

6 Real-time Flow Designer
6.4 Data Logging Flow SettingData logging flow setting list

(1)

6
Displayed items
Item

Description[Home] button

Click this to display the home screen.
Page 109 Home screen[Move from Data Diagnosis Flow] button

Click this to display the "Move Process Flow" screen.
Page 138 Move of a Process Flow

(1) Data logging flow setting list

The name of a data logging flow set in the "Data Logging Flow Setting" screen
is displayed.

Data Logging Flow Name
Comment

A comment set in the "Data Logging Flow Setting" screen is displayed.

Number of Data Modification
Processes

The number of data modification processes set in the "Data Logging Flow
Setting" screen is displayed.

[Edit] button

Click this to display the "Data Logging Flow Setting" screen of a selected row.
Page 132 Data logging flow setting screen[Duplicate] button

Click this to duplicate the setting of a selected row.
• A sequential number '_number' is added to the end of a data logging flow
name.
(Example) LoggingFlow01_2• When duplicating a setting that includes a data storing setting (file saving), a
sequential number '(number)' is added to the end of a file name prefix.
(Example) LOG(2)• When duplicating a setting that includes a data storing setting (DB saving),
a sequential number '_number' is added to the end of a table name.
(Example) LOG_2• When duplicating a setting that includes a data distribution setting in whicha publishing data topic name is specified, it is duplicated without setting the
publishing data topic name.
• When duplicating a setting that includes a data distribution setting in whicha client ID is specified, it is duplicated without setting the client ID.
• When duplicating a setting that includes a data collection setting in which
CSV File Data collector is selected as a data collector, a sequential number'(number)' is added to the end of a monitoring folder.
(Example) C:\Users\SampleUser\Documents(2)• To apply a setting of "File Name Prefix" in the [Save File] tab in the data
storing setting (file saving) to the file transmission setting, perform thefollowing procedure.
 Click the [File Transmission Setting] button in the [Save File] tab.
 Click the [OK] button in the "IT Gateway Transmission Setting" screen.

[Delete] button

Click this to delete the setting of a selected row.

6 Real-time Flow Designer
6.4 Data Logging Flow Setting131

Data logging flow setting screen(1)

Displayed items
Item

Description

Setting Name*1

Set the name of a data logging flow setting (up to 32 characters).
• The following are displayed to avoid name duplication by default.
LoggingFlow 01, LoggingFlow 02, LoggingFlow 03, ...

Comment

Set a comment (up to 100 characters).

(1) Process list

Process TypeThe type of a process is displayed.

Function Type

Select a function type corresponding to the process type.

Process Name

Set a name to identify a process (1 to 100 characters).
• It is displayed by default as follows:
When "Data Collection" is displayed in the "Process Type" column: "Data
Collection"
When an item other than "Data Collection" is displayed in the "Process
Type" column: Content of its function type

Detailed Setting

Click a cell, and each setting screen corresponding to a process type and afunction type appears.
• When the process type is "Data Collection"
Page 139 Data Collection Setting• When the process type is "Data Modification" and the function type is "Data
Extraction"
Page 169 Data Extraction Setting• When the process type is "Data Modification" and the function type is"Character String Data Modification"
Page 170 Character String Data Modification Setting• When the process type is "Data Modification" and the function type is a data
modification plug-in namePage 172 Data Modification Plug-in Setting

Data Storing

Click a cell, and the "Data Storing Setting" screen appears.
• When saving data to a filePage 142 Data Storing Setting (File Saving)• When saving data to a database
Page 152 Data Storing Setting (DB Saving)

Data Distribution

Click a cell, and the "Data Distribution Setting" screen appears.
• For distributing data by using MQTTPage 158 Data Distribution Setting (MQTT)• For distributing data by using an IT gateway
Page 163 Data Distribution Setting (IT Gateway)[Add Row] button

Click this to add a row the process type of which is "Data Modification"
immediately under a selected row.*2,*3[Delete Row] button*4

Click this to delete the process in a selected row.

*1

132

The same name as that of a data logging flow setting or data diagnosis flow setting already set cannot be used.
6 Real-time Flow Designer
6.4 Data Logging Flow Setting

*2

*3
*4

Can be added in the following cases:
The process type of a selected row is "Data Collection" and the function type of a row immediately under the selected row (its process
type is "Data Modification") is an item other than "No Processing."
The process type of a selected row is "Data Modification" and the function type is an item other than "No Processing."
The following are displayed for the process name of an added row to avoid name duplication.
(Contents of the function type)002, (Content of the function type)003
Cannot be used when the process type of a selected row is "Data Collection."

6

6 Real-time Flow Designer
6.4 Data Logging Flow Setting

133

6.5

Data Diagnosis Flow SettingThis section shows the procedure and screen for setting a data diagnosis flow.

Operating procedure

1. Select "Data Diagnosis Flow Setting" in the edit item tree.
The data diagnosis flow setting list appears. (Page 134 Data diagnosis flow setting list)

2. Click the [Edit] button in the data diagnosis flow setting list.
The "Data Diagnosis Flow Setting" screen appears. (Page 136 Data diagnosis flow setting screen)

Data diagnosis flow setting list

(1)

Displayed items
Item

Description[Home] button

Click this to display the home screen.
Page 109 Home screen[Move from Data Logging Flow] button

Click this to display the "Move Process Flow" screen.
Page 138 Move of a Process Flow

(1) Data diagnosis flow setting list

Data Diagnosis Flow Name
Comment

A comment set in the "Data Diagnosis Flow Setting" screen is displayed.

Number of Data Modification
Processes

The number of data modification processes set in the "Data Diagnosis Flow
Setting" screen is displayed.

Number of Data Diagnosis Processes

The number of data diagnosis processes set in the "Data Diagnosis Flow
Setting" screen is displayed.

[Edit] button

134

The name of a data diagnosis flow set in the "Data Diagnosis Flow Setting"screen is displayed.

6 Real-time Flow Designer
6.5 Data Diagnosis Flow Setting

Click this to display the "Data Diagnosis Flow Setting" screen of a selectedrow.
Page 136 Data diagnosis flow setting screen

Item

Description[Duplicate] button

Click this to duplicate the setting of a selected row.
• A sequential number '_number' is added to the end of a data diagnosis flow
name.
(Example) DiagnosisFlow01_2• When duplicating a setting that includes a data storing setting (file saving)or an edge application diagnosis (file) setting, a sequential number'(number)' is added to the end of a file name prefix.
(Example) LOG(2)• When duplicating a setting that includes a data storing setting (DB saving),
a sequential number '_number' is added to the end of a table name.
(Example) LOG_2• When duplicating a setting that includes a data distribution setting in whicha publishing data topic name is specified, it is duplicated without setting the
publishing data topic name.
• When duplicating a setting that includes an edge application diagnosis(MQTT) setting in which a publishing data topic name is specified, it isduplicated without setting the publishing data topic name.
• When duplicating a setting that includes a data distribution setting in whicha client ID is specified, it is duplicated without setting the client ID.
• When duplicating a setting that includes an edge application diagnosis(MQTT) setting in which a client ID is specified, it is duplicated without
setting the client ID.
• When duplicating a setting that includes a data collection setting in which
CSV File Data collector is selected as a data collector, a sequential number'(number)' is added to the end of a monitoring folder.
(Example) C:\Users\SampleUser\Documents(2)• To apply a setting of "File Name Prefix" in the [Save File] tab in the data
storing setting (file saving) to the file transmission setting, perform thefollowing procedure.
 Click the [File Transmission Setting] button in the [Save File] tab.
 Click the [OK] button in the "IT Gateway Transmission Setting" screen.

[Delete] button

Click this to delete the setting of a selected row.

6 Real-time Flow Designer
6.5 Data Diagnosis Flow Setting

135

6

Data diagnosis flow setting screen(1)

Displayed items
Item

Description

Setting Name*1

Set the name of a data diagnosis flow setting (up to 32 characters).
• The following are displayed to avoid name duplication by default.
DiagnosisFlow01, DiagnosisFlow02, DiagnosisFlow03, ...

Comment

Set a comment (up to 100 characters).

136

6 Real-time Flow Designer
6.5 Data Diagnosis Flow SettingItem(1) Process list

Description
Process TypeThe type of a process is displayed.

Function Type

Select a function type corresponding to the process type.

Process Name

Set a name to identify a process (1 to 100 characters).
• It is displayed by default as follows:
When "Data Collection" is displayed in the "Process Type" column: "Data
Collection"
When an item other than "Data Collection" is displayed in the "Process
Type" column: Content of its function type

Detailed Setting

Click a cell, and each setting screen corresponding to a process type and afunction type appears.
• When the process type is "Data Collection"
Page 139 Data Collection Setting• When the process type is "Data Modification" and the function type is "Data
Extraction"
Page 169 Data Extraction Setting• When the process type is "Data Modification" and the function type is"Character String Data Modification"
Page 170 Character String Data Modification Setting• When the process type is "Data Modification" and the function type is a data
modification plug-in namePage 172 Data Modification Plug-in Setting• When the process type is "Data Diagnosis" and the function type is "EdgeApplication Diagnosis (MQTT)"Page 173 Edge Application Diagnosis (MQTT) Setting• When the process type is "Data Diagnosis" and the function type is "EdgeApplication Diagnosis (file)"
Page 178 Edge Application Diagnosis (File) Setting• When the process type is "Data Diagnosis" and the function type is a data
diagnosis plug-in namePage 184 Data Diagnosis Plug-in Setting• When the process type is "Feedback" and the function type is "PostDiagnosis Feedback"Page 185 Post-Diagnosis Feedback Setting

Data Storing*2

Click a cell, and the "Data Storing Setting" screen appears.
• When saving data to a filePage 142 Data Storing Setting (File Saving)• When saving data to a database
Page 152 Data Storing Setting (DB Saving)

Data Distribution*2

Click a cell, and the "Data Distribution Setting" screen appears.
• For distributing data by using MQTTPage 158 Data Distribution Setting (MQTT)• For distributing data by using an IT gateway
Page 163 Data Distribution Setting (IT Gateway)[Add Row] button

Click this to add a row the process type of which is "Data Modification"
immediately under a selected row.*3,*4[Delete Row] button*5

Click this to delete the process in a selected row.

*1
*2
*3

*4
*5

The same name as that of a data logging flow setting or data diagnosis flow setting already set cannot be used.
Cannot be used in the following case:
The process type of a selected row is "Feedback."
Can be added in the following cases:
The process type of a selected row is "Data Collection" and the function type of a row immediately under the selected row (its process
type is "Data Modification") is an item other than "No Processing."
The process type of a selected row is "Data Modification" and the function type is an item other than "No Processing."
The following are displayed for the process name of an added row to avoid name duplication.
(Contents of the function type)002, (Content of the function type)003
Cannot be used when the process type of a selected row is "Data Collection."

6 Real-time Flow Designer
6.5 Data Diagnosis Flow Setting

137

6

6.6

Move of a Process Flow

This section shows the screen for changing the type of a process flow.

Window• Click the [Move from Data Diagnosis Flow] button in the "Data Logging Flow Setting List" screen.
• Click the [Move from Data Logging Flow] button in the "Data Diagnosis Flow Setting List" screen.

(1)

(2)

(1)

(2)

Displayed items
Item

Description(1) Move source flow list

Move source flow settings are displayed in a list.

(2) Move destination flow list

Move destination flow settings are displayed in a list.
A flow setting moved by clicking the [] button is added to the end of the list, and displayed in bold.

[] button

Click this to move a flow setting selected in the move source flow list to the move destination flow list.

[Cancel the movement] button

Click this to return a moved flow setting selected in the move destination flow list to the move source flow list.

138

6 Real-time Flow Designer
6.6 Move of a Process Flow

6.7

Data Collection SettingThis section shows the screen for setting to collect data in an access target device.

Window
Click the cell in the "Detailed Setting" column for which "Data Collection" is displayed in the "Process Type" column in the"Data Logging Flow Setting" or "Data Diagnosis Flow Setting" screen.

6

When an access target device for collecting data is not set, the "Select Data collector" screen to add anaccess target device appears.
Page 125 Data collector selection screen

Displayed items
Item

Description

Reference

Target Device*1

Select a device for collecting data.
The "Select Data collector" screen appears when selecting "[Adding]," and the"Target Device Setting" screen appears after selecting a data collector.
Page 125 Data collector selection screen
Page 126 Access target device setting screenDeveloper

The developer of a data collector used for an access target device forcollecting data is displayed.

Data collector Name

The name of a data collector used for an access target device for collecting
data is displayed.

Data collector Version

The version of a data collector used for an access target device for collecting
data is displayed.

[Collection Data] tab

Set data to be collected.
When using CSV File Data collector as a data collector, the screen shown in
the following section appears.
Page 310 Data Collection Setting (CSV File Data collector)

Page 140 Collection data

[Collection Option] tab*2

Set collection parameters.
For details, refer to the manual for a data collector used.



*1
*2

An access target device for which a data collector that does not support the data collection function is set cannot be selected.
Does not appear in the following cases:
Using CSV File Data collector
Using a data collector that has no settings related to collection parameters

6 Real-time Flow Designer
6.7 Data Collection Setting139Collection data
The following shows the screen for setting data to be collected.

Window(1)

Displayed items
Item

Description(1) Collection data list

Data Name

Set a data name (up to 32 characters).
• If the data name is blank when setting the location (start), the contents of
the location (start) are displayed for the data name.
However, if the number of characters in the contents of the location (start)
exceeds 32, inhibited characters are included, or the contents of a dataname are duplicated, the following are displayed.
(Example) Data001, Data002, Data003, ...
• If nothing is displayed in the "Data Name" column when selecting thecheckbox of "Constant," the following are displayed.
(Example) ConstantData001, ConstantData002, ConstantData003, ...

Constant

Select the checkbox to add a constant value or fixed character string tocollection data.
When selecting the checkbox
The settings other than those set for "Data Name" will be deleted, and thefollowing items are set:
• Data Type: STRING• Length: 32• Setting Value: Blank
When unselecting the checkbox
The settings other than those set for "Data Name" will be deleted.

Location (top)*1

Set the start location of a data collection target (up to 300 characters).
Depending on a data collector used, location parameters can be set in the"Location Setting" screen displayed by clicking the [...] button.*2
For details on the setting method, refer to the manual for a data collector used.

Location (end)The end location acquired from a data collector is displayed.
If a data collector does not return the end location, the cell will be blank.

Data Type

Select the data type of a location to access.*3

LengthWhen not selecting the checkbox of "Constant"
Set the number of characters within the following ranges when selecting"STRING" or "WSTRING" for "Data Type."• STRING: 1 to 32• WSTRING: 1 to 16
When selecting the checkbox of "Constant"
Either of the following numbers of characters is set when selecting "STRING"
or "WSTRING" for "Data Type."• STRING: 32• WSTRING: 16

Setting Value*4,*5

Set a constant value or fixed character string to add to collection data.
The available number of characters differs depending on the data type.
For details, refer to the following:
Page 544 Values that can be entered in the screen[Delete Row] button

*1

140

Can be set when not selecting the checkbox of "Constant."
6 Real-time Flow Designer
6.7 Data Collection Setting

Click this to delete the collection target data in a selected row.

*2
*3

*4

*5

The "Location Setting" screen does not appear when using a data collector for which location parameters cannot be set in the screen.
The data types to be displayed are as follows:
When not selecting the checkbox of "Constant": Depends on a data collector used.
When selecting the checkbox of "Constant": Page 544 Data type and value range
Can be set when both of the following conditions are satisfied:
The checkbox of "Constant" is selected.
A data type is set.
When changing the data type, the value is changed as shown in the following:
Page 546 Value after changing the data type6

6 Real-time Flow Designer
6.7 Data Collection Setting

141

6.8

Data Storing Setting (File Saving)This section shows the screen for setting to output a result of a process in a file format.

Window
Click a cell in the "Data Storing" column in the "Data Logging Flow Setting" or "Data Diagnosis Flow Setting" screen.

Displayed items
Item

Description

Reference[Executable Form] tab

Set an executable form.

Page 143 Executable form

[File Format] tab

Set a file format to output data.

Page 144 File format[Output Data] tab

Set data to output to a file.

Page 145 Output data

[Output Option] tab

Set output options for a saved file.

Page 146 Output option[Save File] tab

Set the save destination, name, and switching operation of a file.

Page 147 Saved file

[Back to] button

Click this to move to the previous setting screen.

[Next] button

Click this to move to the next setting screen.

The setting screen can be switched by directly clicking a tab already set.
The check mark (142) appears on a set tab.

6 Real-time Flow Designer
6.8 Data Storing Setting (File Saving)Executable form
The following shows the screen for setting an executable form.

Window

6
Displayed items
Item

Description

Executable form

Select "File."

6 Real-time Flow Designer
6.8 Data Storing Setting (File Saving)143File format
The following shows the screen for setting a file format to output data.

Window

Displayed items
Item

Description

File Format

Select the format of a file to output.

144

6 Real-time Flow Designer
6.8 Data Storing Setting (File Saving)Output data
The following shows the screen for setting data to output to a file.

Window(1)

6
Displayed items
Item

Description(1) Output contents list

Output*1

Select the checkbox of data to output to a file.

Process Name

A process name to which an output value belongs is displayed.

Output Name

The name of an output value of a process to be saved to a file is displayed.

Data TypeThe data type of output data is displayed.

Output Format

The output format of output data is displayed.
It can be changed in the "Output Format" screen displayed by clicking the [...]
button on the right of the entry field.*2
Page 145 Output format[Select All] button

Click this to select the checkboxes of all data.

[Cancel All] button

Click this to unselect the checkboxes of all data.

*1*2

The checkbox does not appear in the following case, and the data cannot be output to a file. For outputting WSTRING type data, select"CSV file (UTF-8)" for "File Format.""WSTRING" is displayed in "Data Type" and "CSV file (Shift_JIS)" is selected for "File Format."
The output format can be changed for the following data types.
UINT, UDINT, ULINT, REAL, LREAL

Output format
The following shows the procedure for specifying a format when outputting data to a file.

Operating procedure

1. Click the [...] button in the [Output Format] tab.
2. Specify an output format in the "Output Format (Integer)" or "Output Format (Float)" screen, and click the [OK] button.
A value smaller than the number of digits specified for "Digit of decimal" in the "Output Format (Float)" screen
is rounded down.

6 Real-time Flow Designer
6.8 Data Storing Setting (File Saving)145

Output option
The following shows the screen for setting output options for a saved file.

Window

Displayed items
Item

Description

Date Column

*1

146

Output Name of Date Column

Set a character string to output to the date and time column of the data namerow (1 to 32 characters).

Specify the date and time format

Select the checkbox to specify the format of date and time data.

Data Row Output Format

Set the output format of the date and time column (1 to 32 characters).
The following reserved words*1 can be specified.
YYYY: Year (4 digits)
YY : Year (2 digits)
MM : Month (2 digits)
DD : Day (2 digits)hh: Hour (2 digits)
mm : Minute (2 digits)
ss: Second (2 digits)
ms : Millisecond (3 digits)us: Microsecond (6 digits)ns: Nanosecond (9 digits).s to .sssssssss: Digits after the decimal point in seconds (1 to 9 digits)

Output Example

An output example of the date and time column according to the current
setting is displayed.

Case-sensitive

6 Real-time Flow Designer
6.8 Data Storing Setting (File Saving)Saved file
The following shows the screen for setting the save destination, name, and switching operation of a file.

Window

6
Displayed items
Item
Save File Path Setting

Set the operation of switching file

Option Setting

*1
*2
*3
*4

Description
Save Destination Folder

Set the save destination for a file (1 to 204 characters).
It can also be set in the "Select Folder" screen displayed by clicking the [...]
button.

File Name Prefix

Set the prefix of a saved file name (1 to 32 characters).

The example of saving file path

The saving file path based on the settings for "Save Destination Folder" and"File Name Prefix" is displayed.

When the access authority of thesave destination folder is limited,
please specify the user to access.

Select the checkbox to save a file to a folder with restricted access.
When fixing the settings without selecting the checkbox, the settings in the"User Account Setting" screen are deleted.

[User Account Setting] button *1

Click this to display the "User Account Setting" screen.
Page 149 User account setting
The setting status of the "User Account Setting" screen is displayed to theright of this button.

Switch when the next row number(Record number) was exceeded*2

Set the number of data rows to store in one file.
If it is exceeded, a file will be output.

Upper bound number of saving files(Delete the old file when upper boundnumber of saving files was exceeded)

Set the maximum number of files stored in one folder.
If it is exceeded, files will be deleted in chronological order.

Output in Data Extraction unit*3

Select the checkbox to output data in data extraction units.

Execute any program after switching
file

Select the checkbox to run any program after file switching.
For details on program execution after a file is output, refer to the following:
Page 68 Program execution after file output[Program Execution Setting] button*4

Click this to display the "Program Execution Setting" screen.
Page 150 Program execution setting
The setting status of the "Program Execution Setting" screen is displayed to
the right of this button.

Use the IT Gateway to send thesaved file*5

Select the checkbox to send a saved file to an external device such as an IT
system by using an IT gateway.

[File Transmission Setting] button*6

Click this to display the "IT Gateway Transmission Setting" screen.*7
Page 151 IT gateway transmission setting
The setting status of the "IT Gateway Transmission Setting" screen isdisplayed to the right of this button.*8

Can be clicked when selecting the checkbox of "When the access authority of the save destination folder is limited, please specify theuser to access."
If the number of rows specified in Real-time Flow Designer is small, the load on Windows increases because a saved file is frequently
created. In this case, review the setting to lengthen the collection cycle or increase the maximum number of data rows output to a file.
Can be selected when selecting "Data Extraction" for "Function Type."
Can be clicked when selecting the checkbox of "Execute any program after switching file."
6 Real-time Flow Designer
6.8 Data Storing Setting (File Saving)

147

*5
*6
*7

*8

148

Can be selected when an IT gateway with "Data Storing" selected for "IT Gateway Type" is installed.
Page 121 IT gateway list
Can be clicked when selecting the checkbox of "Use the IT Gateway to send the saved file."
If the IT gateway setting is not configured for an IT gateway with "Data Storing" selected for "IT Gateway Type," the "IT Gateway
Selection" screen appears. By selecting an IT gateway in this screen, the "IT Gateway Setting" screen appears and the "IT Gateway
Transmission Setting" screen appears once the setting is completed. (An IT gateway other than one with "Data Storing" selected for "IT
Gateway Type" cannot be selected in the "IT Gateway Selection" screen.)Page 128 IT gateway selection screen, Page 129 IT gateway setting screen
If changing the contents in "Save Destination Folder" or "File Name Prefix" after setting items in the "IT Gateway Transmission Setting"screen, "to be confirmed" will be displayed.

6 Real-time Flow Designer
6.8 Data Storing Setting (File Saving)User account setting
The following shows the screen for setting a user name and password used for accessing a folder with restricted access.

Window

Displayed items
Item

Description

Use the File Saving Common Setting

Select the checkbox to use a file saving common setting configured in the following:
Page 117 File saving common setting

User Name*1*2*3

Set a user name used for file output (up to 127 characters).
When specifying a domain, set it in either of the following formats:*4*5• [Domain name]\[User name]• [User name]@[Domain name]
When specifying a local user of an industrial PC on which Edgecross Basic Software is installed, set it in any of thefollowing formats:• [Computer name]\[User name]• .\[User name]• [User name]

Password*1*2*3

Set a password used for accessing a folder (up to 127 characters).

[Authentication Test] button*1

Click this to perform the authentication test for a user account to Windows by using a set user name and password.

*1
*2
*3

*4

*5

6

Can be set when not selecting the checkbox of "Use the File Saving Common Setting."
If changing a set password for a user account in Windows, set it again.
To prevent eavesdropping and falsification of data, it is recommended to use a user account with a password satisfying complexity
requirements.
The complexity requirements can be checked by the following procedure: Start the local security policy of Windows.
 Double-click [Security Settings]  [Account Policies]  [Password Policy]  [Password must meet complexity requirements].
 Select the [Explain] tab in the "Password must meet complexity requirements Properties" screen.
When '@' and '\' are included, the format is determined as [User name]@[Domain name].
When multiple pieces of '@' or '\' are included, the first '@' ('\' if there is no '@') is used as a delimiter between a domain name and a user
name.
Do not specify a local user of another industrial PC on the network.

Precautions• When exporting a setting file while a local user of an industrial PC is set for "User Name" and importing the setting file inanother industrial PC, the local user may not be authenticated in the import destination industrial PC. Set it again after
import as necessary.
• The authentication test is performed on a local computer. Therefore, even when specifying another industrial PC on the
network for a save destination folder, the test is not performed on the industrial PC.
• When repeating the following operations if a password is incorrect, a user account may be locked out. If an error occurs
due to these operations, check if a password is correct.
- Apply the setting.
- Start Real-time Flow Manager or start the operation.
- Perform the authentication test.

6 Real-time Flow Designer
6.8 Data Storing Setting (File Saving)149

Program execution setting
The following shows the screen for setting a program executed after file switching.

Window

Displayed items
Item

Description

Program

Set the path of a program to execute asynchronously after file switching (up to 127 characters).
It can also be set in the "Execution file Selection" screen displayed by clicking the [...] button.

Argument

Set an argument to specify for a program to execute (up to 127 characters).

150

6 Real-time Flow Designer
6.8 Data Storing Setting (File Saving)IT gateway transmission setting
The following shows the screen for setting a destination and operation for IT gateway transmission.

Window(1)

6

Displayed items
Item

Description

IT Gateway Setting Name

Select the IT gateway setting of an IT gateway with "Data Storing" selected for "IT Gateway Type."
The "IT Gateway Selection" screen appears when selecting "[Adding]," and the "IT Gateway Setting"screen appears after selecting an IT gateway*1.
Page 128 IT gateway selection screen, Page 129 IT gateway setting screen

Developer

The developer of an IT gateway used is displayed.

IT Gateway Name

The name of an IT gateway used is displayed.

IT Gateway Version

The version of an IT gateway used is displayed.

Settings

The setting content of an IT gateway used is displayed.

(1) Service parameter setting

Set service parameters.
For details, refer to the manual for an IT gateway used.

*1

An IT gateway other than one with "Data Storing" selected for "IT Gateway Type" cannot be selected.

6 Real-time Flow Designer
6.8 Data Storing Setting (File Saving)

151

6.9

Data Storing Setting (DB Saving)This section shows the screen for setting to output a result of a process to a database.
When setting the data storing setting (DB saving), a database must be set in advance.
Page 529 Database Setup

Window
Click a cell in the "Data Storing" column in the "Data Logging Flow Setting" or "Data Diagnosis Flow Setting" screen.

Displayed items
Item

Description[Executable Form] tab

Set an executable form.

Page 153 Executable form

[Connect] tab

Set information required for connecting with a database.

Page 154 Connection[Output Data] tab

Set data to output to a database.

Page 155 Output data

[Access Table] tab

Set an access table.

Page 156 Access table[Definition Output] tab

Output a DDL file.

Page 157 Definition output[Back to] button

Click this to move to the previous setting screen.

[Next] button

Click this to move to the next setting screen.

The setting screen can be switched by directly clicking a tab already set.
The check mark (152) appears on a set tab.

6 Real-time Flow Designer
6.9 Data Storing Setting (DB Saving)

ReferenceExecutable form
The following shows the screen for setting an executable form.

Window

6
Displayed items
Item

Description

Executable form

Select "DB."

6 Real-time Flow Designer
6.9 Data Storing Setting (DB Saving)153

Connection
The following shows the screen for setting information required for connecting with a database.

Window

Displayed items
Item

Description

Use DB Connection Common Setting

Select the checkbox to use the DB connection common setting.
Page 116 DB connection common setting

Data Source Name*1

Set the data source name of a database (1 to 32 characters).

User Name*1

Set the user name of a database (1 to 32 characters).

Password*1

Set the password for a database (6 to 32 characters).

*1

154

Cannot be set when selecting the checkbox of "Use DB Connection Common Setting."

6 Real-time Flow Designer
6.9 Data Storing Setting (DB Saving)Output data
The following shows the screen for setting data to output to a database.

Window(1)

6
Displayed items
Item(1) Output contents list

Description
OutputSelect the checkbox of data to output to a database.

Process Name

A process name to which an output value belongs is displayed.

Output Name

The name of an output value of a process to be saved to a database isdisplayed.

Data TypeThe data type of output data is displayed.

[Select All] button

Click this to select the checkboxes of all data.

[Cancel All] button

Click this to unselect the checkboxes of all data.

6 Real-time Flow Designer
6.9 Data Storing Setting (DB Saving)155

Access table
The following shows the screen for setting an access table.

Window

Displayed items
Item

Description

Table Name

Set the table name of a database to access (1 to 32 characters).
• It is displayed by default as follows:"(process flow name)_(process name)"*1
However, if inhibited characters are included in a process flow name or a process name, the following are displayed
to avoid name duplication.
(Example) Table001, Table002, Table003, ...

Output Data

The data name of output data set in a field of a table to be accessed is displayed.
The data name 'TIME' of the date and time column is always displayed in the first row.

Data TypeThe data type of output data set in a field of a table to be accessed is displayed.
The data type 'TIMESTAMP' of the date and time column is always displayed in the first row.

Field Name

Set the field name of a table to access (1 to 32 characters)*2.
• The content of output data is displayed by default.
However, if inhibited characters are included, the following are displayed to avoid name duplication.
(Example) Field001, Field002, Field003, ...

*1
*2

156

If it exceeds 32 characters, a character will be deleted in order from the end.
A set field name may not be used depending on a database used even within the number of characters that can be set. In this case,change the field name by further shortening it.
(Example) PostgreSQL (version 10.3): 64 or more bytes of characters cannot be used for a field name.

6 Real-time Flow Designer
6.9 Data Storing Setting (DB Saving)Definition output
The following shows the screen for outputting a DDL file.

Window

6
Displayed items
Item

Description[Output DDL File] button

Click this to output a DDL file in which table information required for saving output data is defined.
Note that a DDL file must be output to the hard disk of an industrial PC, not to a network drive or removal disk.

When changing the data storing setting after outputting a DDL file and setting a DB once, output the DDL fileand set the DB again.

6 Real-time Flow Designer
6.9 Data Storing Setting (DB Saving)

157

6.10

Data Distribution Setting (MQTT)This section shows the screen for setting for distributing a result of a process to an edge application by using MQTT.
To set the data distribution setting, an MQTT broker must be set up in advance.
Page 504 MQTT Broker Setup

Window
Click a cell in the "Data Distribution" column in the "Data Logging Flow Setting" or "Data Diagnosis Flow Setting" screen.

Displayed items
Item

Description

Reference[Executable Form] tab

Set an executable form.

Page 159 Executable form

[Destination] tab

Set information required for MQTT communication.

Page 160 Destination[Output Data] tab

Set data to output.

Page 161 Output data

[Definition Output] tab

Output a publishing data definition file.

Page 162 Definition output[Back to] button

Click this to move to the previous setting screen.

[Next] button

Click this to move to the next setting screen.

The setting screen can be switched by directly clicking a tab already set.
The check mark (158) appears on a set tab.

6 Real-time Flow Designer
6.10 Data Distribution Setting (MQTT)Executable form
The following shows the screen for setting an executable form.

Window

6
Displayed items
Item

Description

Executable form

Select "MQTT."

6 Real-time Flow Designer
6.10 Data Distribution Setting (MQTT)

159

Destination
The following shows the screen for setting information required for MQTT communication.

Window

Displayed items
Item

Description

Host Name

Select this for communication by specifying a host name, and set a host name (1 to 255 characters).

IP address

Select this for communication by specifying an IP address, and set an IP address.

Port Number

Set a port number (1 to 65535).

Keep Alive [Second]

Set a keep alive time for MQTT communication (20 to 3600 seconds).

Specify user authentication information

Select the checkbox to authenticate a user.

User Name*1

Set a user name (6 to 64 characters).

Password*1

Set a password (6 to 512 characters).

Encrypt communication

Select the checkbox to encrypt communication.

Authentication method*2

Select an authentication method.
• Server authentication• Server authentication & client authentication

Certificate authority certificate*2

Set the file path of a certificate authority certificate (up to 259 characters).
It can also be selected in the "Certificate authority certificate selection" screen displayed by clicking the[...] button.

Client certificate*3

Set the file path of a client certificate (up to 259 characters).
It can also be selected in the "Client certificate selection" screen displayed by clicking the [...] button.

Client secret key*3

Set the file path of a client secret key (up to 259 characters).
It can also be selected in the "Client secret key selection" screen displayed by clicking the [...] button.

QoS

Select QoS (1 or 2) for MQTT communication.
When "1" is specified for a connected edge application, select "1."Specify the client ID of Real-time Flow Manager

Select the checkbox only if a client ID*4 that follows a specific format is required, such as when using an
MQTT broker provided by a cloud service.
Do not select the checkbox when using an MQTT broker shown in the following:
Page 46 MQTT broker
For details on a client ID of Real-time Flow Manager, refer to the following:
Page 82 Client IDs and a topic name

Client ID at sending*5

Set the client ID*4 of Real-time Flow Manager (1 to 1024 characters).

*1
*2
*3

*4
*5

160

Can be set when selecting the checkbox of "Specify user authentication information."Can be set when selecting the checkbox of "Encrypt communication."Can be set when both of the following conditions are satisfied:
The checkbox of "Encrypt communication" is selected.
"Server authentication & client authentication" is selected for "Authentication method."
Information used by an MQTT broker to identify Real-time Flow Manager
Can be set when selecting the checkbox of "Specify the client ID of Real-time Flow Manager."

6 Real-time Flow Designer
6.10 Data Distribution Setting (MQTT)

Output data
The following shows the screen for setting data to output.

Window(1)

6
Displayed items
Item(1) Output contents list

Description
OutputSelect the checkbox of data to output.

Process Name

A process name to which an output value belongs is displayed.

Output Name

The name of an output value of a process to be sent is displayed.

Data TypeThe data type of output data is displayed.

[Select All] button

Click this to select the checkboxes of all data.

[Cancel All] button

Click this to unselect the checkboxes of all data.

6 Real-time Flow Designer
6.10 Data Distribution Setting (MQTT)

161

Definition output
The following shows the screen for outputting a publishing data definition file.

Window

Displayed items
Item

Description

Specify a topic name

Select the checkbox if there are restrictions on available topic names, such as when a topic name isspecified in an edge application.
Do not select the checkbox when an edge application has a function to read a publishing data definition
file or a topic name is not specified in an edge application.
For details on a topic name, refer to the following:
Page 82 Client IDs and a topic namePublishing Data topic name*1

Set a publishing data topic name*2 (up to 64 characters).

[Publishing Data Definition File output] button

Click this to output a JSON file in which output data information required for MQTT distribution isdefined.*3

Deliver output data in units of Data Extraction*4

Select the checkbox to distribute output data in data extraction units.

*1
*2
*3

*4

Can be set when selecting the checkbox of "Specify a topic name."
Information for identifying data exchanged in MQTT communication.
If selecting "1" for "QoS" in the [Destination] tab in the edge application diagnosis (MQTT) setting, reading an output publishing data
definition file may fail in an edge application not supporting QoS1. In this case, select "2" for "QoS" to output. (Page 160
Destination)
Appears only when selecting "Data Extraction" for "Function Type."

When changing the data distribution setting after outputting a publishing data definition file and setting anedge application once, output the publishing data definition file and set the edge application again.

162

6 Real-time Flow Designer
6.10 Data Distribution Setting (MQTT)

6.11

Data Distribution Setting (IT Gateway)

This section shows the screen for setting for distributing a result of a process to an external device such as an IT system byusing an IT gateway.

Window
Click a cell in the "Data Distribution" column in the "Data Logging Flow Setting" or "Data Diagnosis Flow Setting" screen.

6

Displayed items
Item

Description

Reference[Executable Form] tab

Set an executable form.

Page 164 Executable form

[Destination] tab*1

Set information required for data distribution using an IT gateway.

Page 165 Destination[Output Data] tab

Set data to output.

Page 166 Output data

[Definition Output] tab*2

Set the unit of data distribution.

Page 167 Definition output[Details] tab

Set details on an IT gateway used for data distribution.

Page 168 Details[Back to] button

Click this to move to the previous setting screen.

[Next] button

Click this to move to the next setting screen.



*1

*2

If the IT gateway setting is not configured for an IT gateway with "Data Distribution" selected for "IT Gateway Type," the "IT Gateway
Selection" screen appears before the [Destination] tab is displayed. By selecting an IT gateway in this screen, the "IT Gateway Setting"screen appears and the [Destination] tab is displayed once the setting is completed. (An IT gateway other than one with "DataDistribution" selected for "IT Gateway Type" cannot be selected in the "IT Gateway Selection" screen.)Page 128 IT gateway selection screen, Page 129 IT gateway setting screen
Appears only when clicking a cell in the "Data Distribution" column in a row with "Data Extraction" selected for "Function Type."

The setting screen can be switched by directly clicking a tab already set.
The check mark () appears on a set tab.

6 Real-time Flow Designer
6.11 Data Distribution Setting (IT Gateway)

163

Executable form
The following shows the screen for setting an executable form.

Window

Displayed items
Item

Description

Executable form

Select "IT Gateway."164

6 Real-time Flow Designer
6.11 Data Distribution Setting (IT Gateway)Destination
The following shows the screen for setting information required for data distribution using an IT gateway.

Window

6
Displayed items
Item

Description

IT Gateway Setting Name

Select the IT gateway setting of an IT gateway with "Data Distribution" selected for "IT Gateway Type."
The "IT Gateway Selection" screen appears when selecting "[Adding]," and the "IT Gateway Setting"screen appears after selecting an IT gateway*1.
Page 128 IT gateway selection screen, Page 129 IT gateway setting screen

Developer

The developer of an IT gateway used is displayed.

IT Gateway Name

The name of an IT gateway used is displayed.

IT Gateway Version

The version of an IT gateway used is displayed.

Settings

The setting content of an IT gateway used is displayed.

*1

An IT gateway other than one with "Data Distribution" selected for "IT Gateway Type" cannot be selected.

6 Real-time Flow Designer
6.11 Data Distribution Setting (IT Gateway)165

Output data
The following shows the screen for setting data to output.

Window(1)

Displayed items
Item

Description(1) Output contents list

OutputSelect the checkbox of data to output.*1

Process Name

A process name to which an output value belongs is displayed.

Output Name

The name of an output value of a process to be sent is displayed.

Data TypeThe data type of output data is displayed.

[Select All] button

Click this to select the checkboxes of all data.

[Cancel All] button

Click this to unselect the checkboxes of all data.

*1

166

If the data type of data is not supported by an IT gateway used, the checkbox does not appear and the data cannot be output to a file.
For details, refer to the manual for an IT gateway used.

6 Real-time Flow Designer
6.11 Data Distribution Setting (IT Gateway)

Definition output
The following shows the screen for setting the unit of data distribution.

Window

6
Displayed items
Item

Description

Deliver output data in units of Data Extraction*1

Select the checkbox to distribute output data in data extraction units.

*1

Can be selected when selecting an IT gateway that supports data distribution in units of data extraction.
For details, refer to the manual for the IT gateway.

6 Real-time Flow Designer
6.11 Data Distribution Setting (IT Gateway)167

Details
The following shows the screen for setting details on an IT gateway used for data distribution.

Window(1)

Displayed items
Item

Description(1) Service parameter setting

Set service parameters.
For details, refer to the manual for an IT gateway used.

168

6 Real-time Flow Designer
6.11 Data Distribution Setting (IT Gateway)

6.12

Data Extraction SettingThis section shows the screen for setting data extraction.

Window

1. Select "Data Extraction" for "Function Type" in the "Data Logging Flow Setting" or "Data Diagnosis Flow Setting" screen.
2. Click the cell in the "Detailed Setting" column.

(1)

6

(2)

(3)

Displayed items
Item(1) Input data list

Description
Input Data

Set data for input.
Page 123 Data setting in the data selection control tree

Data TypeThe data type of input data is displayed.

[Delete Row] button(2) Output data list

Click this to delete the input data in a selected row.
Output Data Name

Set the name of data for output (1 to 32 characters).
• A name corresponding to input data is displayed.
(Example) When input data is '[COLLECT] data collection.temperature,''temperature' is displayed.
• A sequential number '_number'*1 is added to the end of an output dataname to avoid name duplication.
(Example) temperature_002

Data TypeThe data type of output data is displayed.

Condition Convergence Type

(3) Condition list

*1

Select a combination type for each condition.
• AND Convergence: Data is output when all conditions are satisfied, and not
output if any of them is not satisfied.
• OR Convergence: Data is output when any of the conditions is satisfied,and not output if all of them are not satisfied.
Monitor Target

Set monitoring target data.
Page 123 Data setting in the data selection control tree

Data TypeThe data type of a monitoring target is displayed.

Comparison Condition

Select a comparison condition.

Comparison Target

Specify data to compare.
Page 123 Data setting in the data selection control tree

Data TypeThe data type of a comparison target is displayed.

If the number of characters in an output data name including a sequential number exceeds 32, a character will be deleted in order fromthe end.

6 Real-time Flow Designer
6.12 Data Extraction Setting

169

6.13

Character String Data Modification SettingThis section shows the screen for setting character string data modification.

Window

1. Select "Character String Data Modification" for "Function Type" in the "Data Logging Flow Setting" or "Data Diagnosis
Flow Setting" screen.

2. Click the cell in the "Detailed Setting" column.

(1)

Displayed items
Item

Description(1) Character string data modification
setting list*1

OutputSelect the checkbox of data to output to the next process.

Data Name

The name*2 of input data is displayed.

Data TypeThe data type of input data is displayed.

Modification type*3

Select a modification type.
• Add to the start: Select this to add the content set for "Added character
string" to the start of input data.
• Add to the end: Select this to add the content set for "Added character
string" to the end of input data.
• Extraction: Select this to extract a character string from the start position to
the end position of input data.
For details on each type of processing, refer to the following:
Page 40 Character string data modification function

Added character string*4

Set an added character string specified for "Add to the start" or "Add to theend" for "Modification type."
Available number of characters• "STRING" is displayed in "Data type": 1 to 32 characters• "WSTRING" is displayed in "Data type": 1 to 16 characters

Start position*5

Set the start position for extraction specified for "Extraction" for "Modification
type."
Available value range• "STRING" is displayed in "Data type": 1 to 32• "WSTRING" is displayed in "Data type": 1 to 16

End position*5

Set the end position for extraction specified for "Extraction" for "Modification
type."
Available value range• "STRING" is displayed in "Data type": 1 to 32• "WSTRING" is displayed in "Data type": 1 to 16[Select All] button

Click this to select the checkboxes of all data.

[Cancel All] button

Click this to unselect the checkboxes of all data.

*1
*2
*3

170

The order is changed accordingly when that of output data of the previous process is changed.
Changed accordingly when the setting of output data of the previous process is changed.
Can be set only when both of the following conditions are satisfied:
The checkbox of "Output" is selected.

6 Real-time Flow Designer
6.13 Character String Data Modification Setting

*4*5"STRING" or "WSTRING" is displayed in "Data type."
Can be set only when "Add to the start" or "Add to the end" is selected for "Modification type."
Can be set only when "Extraction" is selected for "Modification type."

6

6 Real-time Flow Designer
6.13 Character String Data Modification Setting

171

6.14

Data Modification Plug-in SettingThis section shows the screen for setting a data modification plug-in.

Window

1. Select a data modification plug-in name for "Function Type" in the "Data Logging Flow Setting" or "Data Diagnosis Flow
Setting" screen.

2. Click the cell in the "Detailed Setting" column.

(1)

(2)

Displayed items
Item

Description(1) Input data list(2) Output data list

Input Data
Data TypeThe data type of input data is displayed.

Setting Data

Set data to specify for input data.
Up to 16 units of identical data can be set.
Page 123 Data setting in the data selection control tree

Output Data

The name of output data defined in a data modification plug-in is displayed.

Data TypeThe data type of output data is displayed.

Output Data Setting Name

Set a name to set for output data (1 to 32 characters).
• The content of output data is displayed by default.
However, if inhibited characters are included, the following are displayed to
avoid name duplication.
Output001, Output002, Output003...

Start Argument

172

The name of input data defined in a data modification plug-in is displayed.

6 Real-time Flow Designer
6.14 Data Modification Plug-in Setting

Set a start argument to specify for a data modification plug-in (up to 127
characters).

6.15

Edge Application Diagnosis (MQTT) SettingThis section shows the screen for setting to send an output result of a process to an edge application, and receive response
data from the edge application by using MQTT.
To set the edge application diagnosis (MQTT) setting, an MQTT broker must be set up in advance.
Page 504 MQTT Broker Setup

Window

1. Select "Edge Application Diagnosis (MQTT)" for "Function Type" in the "Data Diagnosis Flow Setting" screen.
2. Click the cell in the "Detailed Setting" column.

6

Displayed items
Item

Description

Reference[Destination] tab

Set information required for MQTT communication.

Page 174 Destination[Output Data] tab

Set data to output.

Page 175 Output data

[Definition Output] tab

Output a publishing data definition file.

Page 176 Definition output[Response Data] tab

Set response data.

Page 177 Response data

[Back to] button

Click this to move to the previous setting screen.

[Next] button

Click this to move to the next setting screen.

The setting screen can be switched by directly clicking a tab already set.
The check mark () appears on a set tab.

6 Real-time Flow Designer
6.15 Edge Application Diagnosis (MQTT) Setting

173

Destination
The following shows the screen for setting information required for MQTT communication.

Window

Displayed items
Item

Description

Host Name

Select this for communication by specifying a host name, and set a host name (1 to 255 characters).

IP address

Select this for communication by specifying an IP address, and set an IP address.

Port Number

Set a port number (1 to 65535).

Keep Alive [Second]

Set a keep alive time for MQTT communication (20 to 3600 seconds).

Specify user authentication information

Select the checkbox to authenticate a user.

User Name*1

Set a user name (6 to 64 characters).

Password*1

Set a password (6 to 512 characters).

Encrypt communication

Select the checkbox to encrypt communication.

Authentication method*2

Select an authentication method.
• Server authentication• Server authentication & client authentication

Certificate authority certificate*2

Set the file path of a certificate authority certificate (up to 259 characters).
It can also be selected in the "Certificate authority certificate selection" screen displayed by clicking the[...] button.

Client certificate*3

Set the file path of a client certificate (up to 259 characters).
It can also be selected in the "Client certificate selection" screen displayed by clicking the [...] button.

Client secret key*3

Set the file path of a client secret key (up to 259 characters).
It can also be selected in the "Client secret key selection" screen displayed by clicking the [...] button.

QoS"2" is displayed (fixed).

Specify the client ID of Real-time Flow Manager

Select the checkbox only if a client ID*4 that follows a specific format is required, such as when using an
MQTT broker provided by a cloud service.
Do not select the checkbox when using an MQTT broker shown in the following:
Page 46 MQTT broker
For details on a client ID of Real-time Flow Manager, refer to the following:
Page 48 Client IDs and a topic name

Client ID at sending*5

Set the client ID*4 of Real-time Flow Manager (1 to 1024 characters).

*1
*2
*3

*4
*5

174

Can be set when selecting the checkbox of "Specify user authentication information."Can be set when selecting the checkbox of "Encrypt communication."Can be set when both of the following conditions are satisfied:
The checkbox of "Encrypt communication" is selected.
"Server authentication & client authentication" is selected for "Authentication method."
Information used by an MQTT broker to identify Real-time Flow Manager
Can be set when selecting the checkbox of "Specify the client ID of Real-time Flow Manager."

6 Real-time Flow Designer
6.15 Edge Application Diagnosis (MQTT) SettingOutput data
The following shows the screen for setting data to output.

Window(1)

6
Displayed items
Refer to the following:
Page 161 Output data

6 Real-time Flow Designer
6.15 Edge Application Diagnosis (MQTT) Setting

175

Definition output
The following shows the screen for outputting a publishing data definition file.

Window

Displayed items
Item

Description

Confirm existence of the Edge application at thetime of delivery

Select the checkbox to check the existence of an edge application when distributing.

Specify a topic name

Select the checkbox if there are restrictions on available topic names, such as when a topic name isspecified in an edge application.
Do not select the checkbox when an edge application has a function to read a publishing data definition
file or a topic name is not specified in an edge application.
For details on a topic name, refer to the following:
Page 48 Client IDs and a topic namePublishing Data topic name*1

Set a publishing data topic name*2 (up to 64 characters).

Specify the client ID of the edge application

Select the checkbox if there are restrictions on available client IDs, such as when a client ID is specified inan edge application.
Do not select the checkbox when an edge application has a function to read a publishing data definition
file or a client ID is not specified in an edge application.
For details on a client ID of an edge application, refer to the following:
Page 48 Client IDs and a topic name

Client ID*3

Set the client ID*4 of an edge application (1 to 64 characters).

[Publishing Data Definition File output] button

Click this to output a JSON file in which output data information required for edge application diagnosis(MQTT) is defined.

*1
*2
*3
*4

Can be set when selecting the checkbox of "Specify a topic name."
Information for identifying data exchanged in MQTT communication.
Can be set when selecting the checkbox of "Specify the client ID of the edge application."
Information for identifying an edge application with which Real-time Flow Manager communicates.

When changing the edge application diagnosis setting after outputting a publishing data definition file andsetting an edge application once, output the publishing data definition file and set the edge application again.

176

6 Real-time Flow Designer
6.15 Edge Application Diagnosis (MQTT) SettingResponse data
The following shows the screen for setting response data.

Window(1)

6
Displayed items
Item

Description[Get Response Data definition] button

Click this to select a response data definition file*1 and acquire the definition
information of the response data.
A response data definition file can be selected in the "Select Response Data
Definition File" screen displayed by clicking this button.

(1) Output data list

*1

Output Data

The data name of output data acquired from the definition information of
response data is displayed.

Data typeThe data type of output data acquired from the definition information of
response data is displayed.

LengthThe number of characters in output data acquired from the definition
information of response data is displayed.

Output Data Setting Name

Set the name for output data (1 to 32 characters).
• The content of output data is displayed by default.
However, if inhibited characters are included or the content is duplicated,the following are displayed.
Output001, Output002, Output003...

For response data definition files, refer to the following:
Page 44 Response data definition file

6 Real-time Flow Designer
6.15 Edge Application Diagnosis (MQTT) Setting

177

6.16

Edge Application Diagnosis (File) SettingThis section shows the screen for setting to pass a result of a process to an edge application, and acquire response data fromthe edge application in a file format.

Window

1. Select "Edge Application Diagnosis (file)" for "Function Type" in the "Data Diagnosis Flow Setting" screen.
2. Click the cell in the "Detailed Setting" column.

Displayed items
Item

Description

Reference[File Format] tab

Set a file format to output data.

Page 179 File format[Output Data] tab

Set data to output to a file.

Page 180 Output data

[Output Option] tab

Set output options for a saved file.

Page 181 Output option[Save File] tab

Set the save destination, name, and switching operation of a file.

Page 182 Saved file

[Response Data] tab

Set details on response data.

Page 183 Response data

[Back to] button

Click this to move to the previous setting screen.

[Next] button

Click this to move to the next setting screen.

The setting screen can be switched by directly clicking a tab already set.
The check mark (178) appears on a set tab.

6 Real-time Flow Designer
6.16 Edge Application Diagnosis (File) SettingFile format
The following shows the screen for setting a file format to output data.

Window

6
Displayed items
Refer to the following:
Page 144 File format

6 Real-time Flow Designer
6.16 Edge Application Diagnosis (File) Setting

179

Output data
The following shows the screen for setting data to output to a file.

Window(1)

Displayed items
Refer to the following:
Page 145 Output data

180

6 Real-time Flow Designer
6.16 Edge Application Diagnosis (File) SettingOutput option
The following shows the screen for setting output options for a saved file.

Window

6
Displayed items
Refer to the following:
Page 146 Output option

6 Real-time Flow Designer
6.16 Edge Application Diagnosis (File) Setting

181

Saved file
The following shows the screen for setting the save destination, name, and switching operation of a file.

Window

Displayed items
Item

Description

Save File Path Setting

Set the operation of switching file

*1

182

Save destination folder

Set the save destination for a file (1 to 204 characters).
It can also be set in the "Select Folder" screen displayed by clicking the [...]
button.

File name prefix

Set the prefix of a saved file name (1 to 32 characters).

The example of saving file path

The saving file path based on the settings for "Save Destination Folder" and"File Name Prefix" is displayed.

Switch when the next row number(Record number) was exceeded*1

Set the number of data rows to store in one file.
If it is exceeded, a file will be output.

Upper bound number of saving files(Delete the old file when upper boundnumber of saving files was exceeded)

Set the maximum number of files stored in one folder.
If it is exceeded, files will be deleted in chronological order.

If the number of rows specified in Real-time Flow Designer is small, the load on Windows increases because a saved file is frequently
created. In this case, review the setting to lengthen the collection cycle or increase the maximum number of data rows output to a file.

6 Real-time Flow Designer
6.16 Edge Application Diagnosis (File) SettingResponse data
The following shows the screen for setting response data.

Window(1)

6
Displayed items
Item

Description[Get Response Data definition] button

Click this to select a response data definition file*1 and acquire the definition
information of the response data.
A response data definition file can be selected in the "Select Response Data
Definition File" screen displayed by clicking this button.

(1) Output data list

*1

Output Data

The data name of output data acquired from the definition information of
response data is displayed.

Data typeThe data type of output data acquired from the definition information of
response data is displayed.

Output Data Setting Name

Set the name for output data (1 to 32 characters).
• The content of output data is displayed by default.
However, if inhibited characters are included or the content is duplicated,the following are displayed.
Output001, Output002, Output003...

For response data definition files, refer to the following:
Page 53 Response data definition file

When acquiring the definition information of response data, the character code is determined depending onwhether the response data definition file has BOM or not.
• With BOM: Determined as UTF-8 (with BOM).
• Without BOM: Determined as Shift JIS.

6 Real-time Flow Designer
6.16 Edge Application Diagnosis (File) Setting

183

6.17

Data Diagnosis Plug-in SettingThis section shows the screen for setting a data diagnosis plug-in.

Window

1. Select a data diagnosis plug-in name for "Function Type" in the "Data Diagnosis Flow Setting" screen.
2. Click the cell in the "Detailed Setting" column.

(1)

(2)

Displayed items
Item

Description(1) Input data list(2) Output data list

Input Data

The name of input data defined in a data diagnosis plug-in is displayed.

Data TypeThe data type of input data is displayed.

Setting Data

Set data to specify for input data.
Up to 16 units of identical data can be set.
Page 123 Data setting in the data selection control tree

Output Data

The name of output data defined in a data diagnosis plug-in is displayed.

Data TypeThe data type of output data is displayed.

Output Data Setting Name

Set a name to set for output data (1 to 32 characters).
• The content of output data is displayed by default.
However, if inhibited characters are included, the following are displayed to
avoid name duplication.
Output001, Output002, Output003...

Start Argument

184

6 Real-time Flow Designer
6.17 Data Diagnosis Plug-in Setting

Set a start argument to specify for a data diagnosis plug-in (up to 127
characters).

6.18

Post-Diagnosis Feedback SettingThis section shows the screen for setting feedback provided when a diagnosis result of a data diagnosis process is received.

Window

1. Select "Post-Diagnosis Feedback" for "Function Type" in the "Data Diagnosis Flow Setting" screen.
2. Click the cell in the "Detailed Setting" column.

(1)

Displayed items

6

Item

Description(1) Feedback setting list

Feedback Type

Select the type of feedback provided after data diagnosis.

Execution Condition

Click a cell, and the "Execution condition setting" screen appears.
Page 186 Execution condition setting

Execution Frequency

Select a frequency of feedback.

Deterrence Period

Set a period to limit feedback (1 to 60 minutes or 1 to 24 hours).

Deterrence Period (unit)

Select the unit of a period to limit feedback (in minutes or in hours).

Feedback Setting

Click a cell, and each setting screen corresponding to a feedback typeappears.
• When the feedback type is "Instruction Feedback"Page 187 Device instruction feedback setting• When the feedback type is "Feedback of Program Execution"
Page 190 Program execution feedback setting

By selecting a blank for "Feedback Type," the setting of the row can be deleted.

6 Real-time Flow Designer
6.18 Post-Diagnosis Feedback Setting

185

Execution condition setting
The following shows the screen for setting an execution condition for feedback.

Window(1)

Displayed items
Item

Description

Condition Convergence Type

Select a combination type for each condition.
• AND Convergence: Feedback is provided when all conditions are satisfied,and not provided if any of them is not satisfied.
• OR Convergence: Feedback is provided when any of the conditions is
satisfied, and not provided if all of them are not satisfied.

(1) Execution condition list

186

Monitor Target

Select monitoring target data.
Page 123 Data setting in the data selection control tree

Data TypeThe data type of a monitoring target is displayed.

Comparison Condition

Select a comparison condition.

Comparison Target

Select data to compare.
Page 123 Data setting in the data selection control tree

Data TypeThe data type of a comparison target is displayed.
When data selected for "Comparison Target" is a constant, nothing isdisplayed.

6 Real-time Flow Designer
6.18 Post-Diagnosis Feedback Setting

Device instruction feedback setting
The following shows the screen for setting data to issue an instruction to an access target device.

Window

1. Select "Instruction Feedback" for "Feedback Type" in the "Post-Diagnosis Feedback Setting" screen.
2. Click the cell in the "Feedback Setting" column.

6

When an access target device to which an instruction is issued is not set, the "Select Data collector" screen
appears to add an access target device.
Page 125 Data collector selection screen

Displayed items
Item

Description

Reference

Target Device

Select a device to issue an instruction.
The "Select Data collector" screen appears when selecting "[Adding]," and the"Target Device Setting" screen appears after selecting a data collector.
Page 125 Data collector selection screen
Page 126 Access target device setting screenDeveloper

The developer of a data collector used for an access target device that is an
instruction target is displayed.

Data collector Name

The name of a data collector used for an access target device that is an
instruction target is displayed.

Data collector Version

The version of a data collector used for an access target device that is an
instruction target is displayed.

[Instruction Target data] tab

Set data to issue an instruction.

Page 188 Instruction target data

[Instruction Option] tab

Set an instruction option.

Page 189 Instruction option*1*1

An access target device for which a data collector that does not support the data writing function is set cannot be selected.

6 Real-time Flow Designer
6.18 Post-Diagnosis Feedback Setting

187

Instruction target data
The following shows the screen for setting data to issue an instruction.

Window(1)

Displayed items
Item

Description(1) Instruction target data list

Data Name

Set a data name (up to 32 characters).
• If the data name is blank when setting the location (start), the contents of
the location (start) are displayed for the data name.
However, if the number of characters in the contents of the location (start)
exceeds 32, inhibited characters are included, or the contents of a dataname are duplicated, the following are displayed.
(Example) Data001, Data002, Data003, ...

Location (top)Set the start location of an instruction target (up to 300 characters).
Depending on a data collector used, location parameters can be set in the"Location Setting" screen displayed by clicking the [...] button.*1
For details on the setting method, refer to the manual for a data collector used.

Location (end)The end location acquired from a data collector is displayed.
If a data collector does not return the end location, the cell will be blank.

Data Type

Select the data type of a location to access.

LengthSet the number of characters within the following ranges when selecting"STRING" or "WSTRING" for "Data Type."• STRING: 1 to 32• WSTRING: 1 to 16

Setting Value

Set a value to substitute for an instruction target location.
Page 123 Data setting in the data selection control tree

[Delete Row] button

*1

188

Click this to delete the instruction target data in a selected row.

When using a data collector the location parameters of which cannot be set in the "Location Setting" screen, the "Location Setting"screen does not appear.

6 Real-time Flow Designer
6.18 Post-Diagnosis Feedback Setting

Instruction option
The following shows the screen for setting an instruction option.

Window

Displayed items
Item

Description

Response timeout time

Set a response timeout time from a data collector.

6

6 Real-time Flow Designer
6.18 Post-Diagnosis Feedback Setting

189

Program execution feedback setting
The following shows the screen for setting the feedback function to execute a program (exe or bat) when a result of diagnosis
processing in a data diagnosis process is received.
For details on the program execution, refer to the following:
Page 55 Program execution feedback function

Window

1. Select "Feedback of Program Execution" for "Feedback Type" in the "Post-Diagnosis Feedback Setting" screen.
2. Click the cell in the "Feedback Setting" column.

Displayed items
Item

Description

Program

Set the path of a program to execute (up to 127 characters).
It can also be selected in the "Selection of execution program" screen displayed by clicking the [...] button.

Argument

Set an argument to specify for a program (up to 300 characters).

190

6 Real-time Flow Designer
6.18 Post-Diagnosis Feedback Setting

7Management Shell

Management Shell is software that models data in equipment, devices, or lines in production sites, manages it in ahierarchical structure, and runs in the background on Windows as a Windows service. In addition, it reads and writes data inconnected equipment, devices, or lines by using a data collector.
For the data models managed by Management Shell, refer to the following:
Page 192 Data Model
Data models managed by Management Shell are set and referenced by using Management Shell Explorer.
For the startup method, screen configuration, and others of Management Shell Explorer, refer to the following:
Page 193 Management Shell Explorer

Industrial PC

Management Shell Explorer(a)*1

Edge application

Management Shell
(c)*1
(b)

7

Data collector*2
Data reading/writing target device(a) Data models are set and referenced.
(b) Data reading or writing is requested.
(c) Data models are referenced or the current value of a data tag resource is acquired or changed.

*1*2Communication times out in 30 seconds.
Communication timeout time depends on the setting of a data collector. For details, refer to the manual for a data collector used.

Precautions
Even when exiting Management Shell Explorer, Management Shell and a data collector do not stop. To stop Management
Shell, perform the following operation.
• Select [Management Shell]  [Management Shell Stop].

Connection to, disconnection from, and reconnection to an access target device
A data collector connects to, disconnects from, and reconnects to an access target device in response to the following
operations:Behavior of a data collector

Operation

Connect

Start Management Shell by either of the following operations:• Start Windows.
• Select [Management Shell]  [Management Shell Start].
Add an access target device setting.

Disconnect

Stop Management Shell by either of the following operations:• Shut down Windows.
• Select [Management Shell]  [Management Shell Stop].

Reconnect(Disconnect  connect)

Change the contents of an access target device setting.

Delete an access target device setting.

Click the [Reconnect] button in the "Target Device Setting List" screen.

7 Management Shell

191

7.1

Data Model

This section shows the configuration elements of a data model managed by Management Shell.
Component

Component

Resource

Component

Data tag resource
External data tag resource
ComponentInternal data tag resource
File resource
Folder resource

Configuration element

Description

Component

An element for representing equipment, devices, or lines, and theirhierarchical relations in production sites.

Resource

Data tag resource

192

An element for representing data in equipment, devices, or lines in production
sites (data in production sites, manual data, and program data) included in acomponent and managed.
External data tag resource

An element for representing data existing outside of Edgecross Basic
Software. Use this to manage the internal memory and sensor inputs ofequipment, devices, or lines in production sites.

Internal data tag resource

An element for defining data in Edgecross Basic Software.
It is retained in Edgecross Basic Software.
Values can be read from an external device such as an edge application or IT
system.
The following setting methods are available for internal data tag resources.
• Value: A setting method by writing data from an external device such as anedge application or IT system. Use this method to manage fixed value
information such as a product model name and production number.
• Operation: A setting method by writing the result of a four arithmetic or
logical operation performed on a value of an external data tag resource or aconstant as data. Use this method to modify data represented by an
external data tag resource. An internal data tag resource set by using thismethod cannot be written from an external device such as an edge
application or IT system (read-only).

File resource

An element for representing file data. Use this to manage files such as manual
data or program data.
No restrictions on file types that can be managed.

Folder resource

An element for representing folder data. Use this to manage folders.

7 Management Shell
7.1 Data Model7.2

Management Shell Explorer

Management Shell Explorer is software that sets and references data models managed by Management Shell. In addition, it
can monitor and change current values of data in production sites managed by Management Shell.

Startup method
Operating procedure

1. Perform either of the following operations:• Start Management Shell Explorer from "Edgecross Basic Software" in Windows Start.
• Double-click the shortcut icon of 'Management Shell Explorer' on the desktop.
When starting Management Shell Explorer, the contents that were set last time is applied.

When starting Management Shell Explorer for the first time, the screen to confirm the software license
agreement appears. (It will not appear if the license agreement has already been accepted in Real-time Flow
Designer.)

7

7 Management Shell
7.2 Management Shell Explorer

193

Starting Management Shell Explorer with the administrator authority
When performing an operation by using any of the following menus, it is necessary to start Management Shell Explorer withthe administrator authority.
• [Management Shell]  [Management Shell Start]• [Management Shell]  [Management Shell Stop]• [Management Shell]  [Import]• [Management Shell]  [Delete All]• [Setting]  [OPC UA Setting]Procedure for starting it with the administrator authority

1. Perform either of the following operations:• Right-click Management Shell Explorer and select [More]  [Run as administrator] in "Edgecross Basic Software" inWindows Start.
• Right-click the shortcut icon of 'Management Shell Explorer' on the desktop, and select [Run as administrator].

2. Click the [Yes] button in the "User Account Control" screen.
By performing the following operations, Management Shell Explorer can be started with the administrator
authority without selecting [Run as administrator].
 Right-click the following file and select [Properties].
(Installation destination of Edgecross Basic Software)\Management Shell\Explorer\EcMsExplorer.exe
 Select the checkbox of "Run this program as an administrator" in the [Compatibility] tab, and click the [OK]button.

Precautions
If a user without the administrator authority starts Management Shell Explorer with the administrator authority, a password fora user with the administrator authority is required. Therefore, it is recommended to log in to Windows as a user with theadministrator authority.

194

7 Management Shell
7.2 Management Shell Explorer

Screen configuration
(4)
(1)
(2)

(5)
(3)

(6)

(1) Menu bar(2) Toolbar(3) Component tree window(4) Resource list window(5) Property window(6) Data tag resource monitor window

7

7 Management Shell
7.2 Management Shell Explorer

195

Menu configuration
Menu item
Management
Shell

Description

Reference*1

Management Shell Start

To switch Management Shell that runs as aWindows service to the operating state.*3Management Shell Stop*2

To switch Management Shell that runs as aWindows service to the stop state.*3

ImportTo import a setting file saved by using the [Export]
menu into Management Shell Explorer andManagement Shell, and restore it.*4,*5,*6,*7,*8



ExportTo save the following information as a setting file
(extension: .msf)*9.*10,*11,*12• Access target device settings, IT gateway
settings, and icon files set in Management Shell
Explorer• Data models (components and resources)
managed by Management Shell• One-shot collection setting*13• Event history automatic output setting
An execution environment may be damaged;
therefore, it is recommended to export a setting filefor backup.

Data Model Import*14

To import the following information in a file*15 savedby using the [Data Model Export] menu into
Management Shell Explorer and Management Shell,
and restore it.*16,*17,*18• Data model (component*19, resource*20)• Access target device setting*21
An imported data model is added under a selectedcomponent.
In addition, the import behavior differs depending on
the format of a file to be imported.
For details, refer to the following:
Page 200 Behavior of data model importData Model Export*22

To save the following information in the file format(extension: dmf).*12• Selected component and resources in thecomponent*20,*23,*24• Access target device setting used in a data tag
resource to be saved
By using this menu, a data model can partially beutilized or duplicated. (It can also be utilized inanother industrial PC.)
For duplicating a data model, refer to the following:
Page 201 Duplicating a data modelTo display the "OPC UA Diagnosis" screen.

Page 341 OPC UA
diagnosis

Error Information List

To display the "Error Information List" screen.

Page 343 Displaying error
information in a list

Check Number of Model Configurations

To display the "Check Number of Model
Configurations" screen.

Page 206 "Check Numberof Model Configurations"screenDelete All

To return the following information to the default.*4• Access target device settings, IT gateway
settings, and one-shot collection settings
configured in Management Shell Explorer• Data models (components and resources)
managed by Management Shell

Exit Management Shell Explorer

To exit Management Shell Explorer.



Switch Display Language

To switch the display languages of Real-time Flow
Designer and Management Shell Explorer for the
next startup (Japanese/English/Simplified
Chinese)*25.

Diagnosis

View

196

7 Management Shell
7.2 Management Shell Explorer

OPC UA Diagnosis

Menu item
Setting

Tool

Window

Help

Description

Reference

Target Device Setting

To display the "Target Device Setting List" screen.

Page 220 Access target
device setting list screen

IT Gateway Setting

To display the "IT Gateway Setting List" screen.

Page 266 IT gateway
setting list screen

OPC UA Setting

To display the "OPC UA Setting" screen.

Page 261 Setting an OPC
UA server
Page 263 Managing OPC
UA client certificates

Event History Automatic Output Setting

To display the "Event History Automatic Output
Setting" screen.

Page 292 Event history
automatic output setting
screenOptionTo display the "Options" screen.

Page 216 Option setting

One-Shot Collection Setting

To display the "One-Shot Collection Setting" screen.

Page 281 One-shotcollection setting screen

Target Device Setting Batch Replacement

To display the "Target Device Setting Batch
Replacement" screen.

Page 217 Access target
device setting batch
replacement

Component Hierarchy Tree Edit*26

To display the component tree edit dialog.

Resource List Edit*26

To display the resource list edit dialog.

Return to Initial Layout

To return the layout of the screen set in
Management Shell Explorer to the default.



Data Collector List

To display the list of installed data collectors.

Page 120 Data collector list

To display the list of installed IT gateways.

Page 121 IT gateway list

To display the manual (Edgecross Basic Software
for Windows User's Manual) in PDF format.*27

To display the version information and license
information of Management Shell Explorer.



IT Gateway List
ManualVersion Information

Edgecross Basic
Software User's Manual

7

*1
*2
*3
*4
*5
*6

Cannot be selected when Management Shell is running.
Cannot be selected when Management Shell is stopped.
To restart Management Shell when initializing setting information or registering components or resources fail.
Not available while the "One-Shot Collection Setting" screen is open.
When a password is set for a file, the file can be read by entering the password in the displayed "Password input" screen.
When importing a setting file saved in Management Shell Explorer with Edgecross Basic Software version 1.21 or earlier, data tag
resources are imported as external data tag resources.
*7 When importing a setting file, which is saved in Management Shell Explorer with Edgecross Basic Software version 1.22 or earlier, into
Management Shell Explorer in which a one-shot collection setting is configured, the setting is deleted.
*8 When importing a setting file, which is saved in Management Shell Explorer with Edgecross Basic Software version 1.23 or earlier, into
Management Shell Explorer in which the event history automatic output setting is configured, the setting is deleted.
*9 Do not use surrogate pair characters for a file name.
*10 A password can be set in the displayed "Password setting" screen. This can prevent leakage of the information in a setting file.
*11 The following settings are not exported; therefore, they are not applied to Management Shell Explorer even when importing the exported
file. Set them again as necessary after importing the file.
OPC UA setting
Client certificate*12 Depending on a data collector used, some setting information may not be saved. For details, refer to the manual for a data collector
used.
*13 A setting file can be exported even while editing a one-shot collection setting; however, only applied items are exported.
*14 Also available by selecting and right-clicking a component then selecting [Data Model Import].
*15 For editing a file, refer to the following:
Edgecross data model file maker user's manual [ECD-MA1-0004]*16 If the data collector version of a data collector used in an imported access target device setting is different from that of one installed on
an import destination, perform any of the following operations to update the version to that of installed one.
Click the [Update to Latest State] button in the "Data collector List" screen.
Restart Management Shell.
Restart Management Shell Explorer.
*17 A warning or error may occur during import. If an error occurs, import fails. The content of a warning or error can be checked in the"Import error list" screen displayed after import.
Page 204 Import error list screen*18 When monitoring is being performed in the data tag resource monitor window, it stops. (Monitoring restarts after import is completed.)

7 Management Shell
7.2 Management Shell Explorer197

*19 If the icon file does not exist in a file path set for "Component Icon," it is displayed as the following icon. Note that the content of"Component Icon" in the property item is not changed.

*20 An internal data tag resource (operation) is not a target for data model export and import.
After importing a data model, set it again in an import destination as necessary.
*21 If an access target device setting to be imported overlaps with any of the access target device settings in an import destination, selectanother access target device setting in the "Target Device setting import" screen displayed during import.
Page 203 Target device setting import screen*22 Also available by selecting and right-clicking a component then selecting [Data Model Export].
*23 For the icon file of a component, only the file path is exported. (A file itself is not exported.)*24 Components and their resources under a selected component are also saved.
*25 The default display language depends on an operating system and package languages. (It is set to English when the language setting ofWindows is not Japanese, English, or Simplified Chinese.)*26 Can be selected only when selecting the checkbox of "Enable Editing Component Hierarchy Tree Window and Resource List Window"
in the "Options" screen.
Page 216 Option setting*27 If the manual is not displayed, refer to the following:
Page 355 Troubleshooting on basic operations

Toolbar configuration
Character string for the tooltip display

Description

Component Hierarchy Tree Edit*1

To display the component tree edit dialog.

Resource List Edit*1

To display the resource list edit dialog.

*1

Can be selected only when selecting the checkbox of "Enable Editing Component Hierarchy Tree Window and Resource List Window"
in the "Options" screen.
Page 216 Option settingComponent tree window
The component tree is displayed.
Components are sorted in ascending order of their display names by comparing character strings and displayed in a samehierarchy.
For editing the component tree, refer to the following:
Page 224 Component Tree Edit Function• A component with the following property items is added to the component tree window at the first startup.
Component Name: Component
Component Display Name: Component
Component Icon: Factory.png• Clicking the [Find] button in the component tree window displays the "Component Find" screen. For details
on the screen items, refer to the following:
Page 233 Searching for a component• Select and right-click a component while the "Detailed Setting" screen of the one-shot collection function
opens, and select [Register to one-shot collection setting: Collect] to register a data tag resource in theselected component as a collection target resource. For details, refer to the following:
Page 269 One-shot Collection Function

198

7 Management Shell
7.2 Management Shell Explorer

Resource list window
Information on a resource that belongs to a component selected in the component tree window is displayed.
Clicking the header of each column can sort items in ascending or descending order by comparing character strings.
For editing the resource list, refer to the following:
Page 235 Resource List Edit Function• Clicking the [Find] button in the resource list window displays the "Resource Find" screen. For details on thescreen items, refer to the following:
Page 256 Searching for a resource• Select and right-click a data tag resource while the "Detailed Setting" screen of the one-shot collection
function opens, and select [Register to one-shot collection setting: Collect], [Register to one-shot collection
setting: Monitor], or [Register to one-shot collection setting: Notify] to register the selected data tag resource
as a collection, monitoring, or notification target resource. For details, refer to the following:
Page 269 One-shot Collection FunctionProperty window
The contents set in the following properties are displayed.
• Component selected in the component tree window• Resource selected in the resource list window*1*1

When selecting multiple resources in the resource list window, nothing is displayed.

7

Data tag resource monitor window
The current value of a registered data tag resource can be monitored and changed.
For monitoring and changing current values of data tag resources, refer to the following:
Page 207 Monitoring and changing current values of data tag resources

7 Management Shell
7.2 Management Shell Explorer

199

Behavior of data model import
In data model import, the behavior differs depending on the format of a file to be imported.
FormatBehavior

DMF format (.dmf)

A data model is imported with specifying an access target device setting to be assigned when importing an external
data tag resource.

XML format (.xml)*1

A data model is imported without specifying an access target device setting to be assigned when importing an external
data tag resource.
An access target device setting*2 in which Dummy Data collector is used is assigned to an external data tag resource
to be imported. (Page 327 Dummy Data collector)*1*2

For details on the format of an XML format file, contact the Edgecross Consortium.
The following setting names are set to avoid name duplication.
Dev001, Dev002, Dev003, ...

Data model import in XML format files
When importing a data model in an XML format file, replace an assigned access target device setting (Dummy Data collector)
with a proper one in the "Target Device Setting Batch Replacement" screen after the import.
Page 217 Access target device setting batch replacement
If there are multiple proper access target device settings, it is recommended to prepare an XML format file for each accesstarget device setting, then import a data model multiple times.
When importing a data model without separating files for each access target device setting, it is necessary to replace thesetting with a proper one for each data tag resource after the import.
For a replacement example, refer to the following:
Page 219 Replacement example when importing a data model in an XML format file200

7 Management Shell
7.2 Management Shell Explorer

Duplicating a data model
For duplicating a data model, the setting must be changed in the "Target Device setting import" screen according to a data
model to create. (Page 203 Target device setting import screen)
The following shows the setting examples in the "Target Device setting import" screen.

Setting example 1
Data model to create
Data model with a different access target device setting shown below (duplicating a shaded data model)

Industrial PC

Control device A(127.0.0.1)

Control device B(127.0.0.2)

Control device C(127.0.0.5)

Control device D(127.0.0.10)

7Setting
Select the checkbox in the "Add" column of an access target device setting. The access target device setting is renamed andimported.

After import
The renamed and imported access target device setting can be edited individually.

Data model

Control device A
Access target device(127.0.0.1)

Control device B

Control device C

Control device D

Access target device(1)(127.0.0.1)
ChangeAccess target device(2)(127.0.0.1)
ChangeAccess target device(3)(127.0.0.1)
Change(127.0.0.2)(127.0.0.5)(127.0.0.10)

External data tag
resource(1)External data tag
resource(2)External data tag
resource(3)External data tag
resource

ExportImportImportImportXXX.dmf

7 Management Shell
7.2 Management Shell Explorer

201

Setting example 2
Data model to create
Data model with the same access target device setting shown below (duplicating a shaded data model)

Industrial PC

Control device(127.0.0.7)

Resource

Resource(1)Resource(2)Resource(3)Setting
Unselect the checkbox in the "Add" column of an access target device setting. A new access target device setting is notimported.

After import
The access target device setting can be edited for multiple data models in a batch.

Data model
Access target device(127.0.0.1)(127.0.0.7)
ChangeExternal data tag
resource

External data tag
resource(1)External data tag
resource(2)External data tag
resource(3)Component(1)Component(2)Component(3)ExportImportXXX.dmf

202

7 Management Shell
7.2 Management Shell Explorer

ImportImportTarget device setting import screen
Window(1)

Displayed items
Item

Description

Number of Target Device settings after the import

The number of access target device settings after import is displayed.

(1) List of duplicate access target
device settings

Add

Select the checkbox of an access target device setting to import.

Setting Name

The name of an access target device setting is displayed.

Setting name after renamed

When selecting the checkbox of "Add," the name of an access target device
setting after import is set in the following format:• "Setting name"(n)n: A number of 1 or more that is set to avoid name duplication with an accesstarget device setting in an import destination.

Comment

The comment set for an access target device setting is displayed.

Parameter details

The parameter set for an access target device setting is displayed.

Data collector

The data collector name, data collector version, and developer of a datacollector used for an access target device setting are displayed.

[Select all] button

Click this to select all the checkboxes in the "Add" column of the access target
device settings.

[Cancel all] button

Click this to unselect all the checkboxes in the "Add" column of the accesstarget device settings.

[Continue] button

Click this to import a selected access target device setting.

7 Management Shell
7.2 Management Shell Explorer

203

7Import error list screen
Window

Displayed items
Item

Description

Result"Warning" or "Error" is displayed.

Code

A four-digit code (hexadecimal) indicating a warning or error is displayed. (Page 424 Code List for Data Model
Import)Description

Causes and corrective actions of a warning or error are displayed.

Type

The type of a warning or error is displayed.

Display name

The name of a setting in which a warning or error has occurred is displayed.

Precautions
Only 1000 warnings and errors are displayed.

204

7 Management Shell
7.2 Management Shell Explorer

Location of use search result screen
The locations where setting items (access target device settings) are used are displayed in a list.

Window
Select and right-click a row in the "Target Device Setting List" screen, and select [Search of the location of use for Target
Device setting].

Displayed items
Refer to the following:
Page 122 Location of use search result screen

Precautions

7

Refer to the following:
Page 122 Location of use search result screen

7 Management Shell
7.2 Management Shell Explorer

205

"Check Number of Model Configurations" screen
The following shows the screen for displaying the total number and breakdowns of data models (components and resources)
registered in Management Shell.

Window
Select [Management Shell]  [Check Number of Model Configurations].

Displayed items
Item

Description

Total Number of Components

The total number of components registered in Management Shell is displayed.

Total Number of Resources

The total number of resources registered in Management Shell is displayed.

Breakdown ofResource Type*1

External Data Tag

The total number of external data tag resources registered in Management Shell is displayed.

Internal Data Tag

The total number of internal data tag resources registered in Management Shell is displayed.

Breakdown of
Setting Method*2

*1
*2

206

Value

The total number of internal data tag resources for which "Value" is selected for the setting method
is displayed.

Operation

The total number of internal data tag resources for which "Operation" is selected for the setting
method is displayed.

Folder

The total number of folder resources registered in Management Shell is displayed.

File

The total number of file resources registered in Management Shell is displayed.

A numerical value for "Total Number of Resources" is displayed for "Total."
A numerical value for "Internal Data Tag" is displayed for "Total."

7 Management Shell
7.2 Management Shell Explorer

Monitoring and changing current values of data tag resources
Current values of data tag resources registered in a component can be monitored and changed in the data tag resource
monitor window.
For the screen configuration of the data tag resource monitor window, refer to the following:
Page 207 Data tag resource monitor window
The data reading function of a data collector is used to monitor current values of data tag resources, and the data writing
function is used to change them.

It is necessary to edit the resource list before monitoring and changing current values of data tag resources.
Page 235 Resource List Edit Function

Precautions
When using a data collector that does not support the data writing function, current values cannot be changed.
For details, refer to the manual for a data collector used.

Data tag resource monitor window

7

Displayed items
Item

Description[Start Monitoring]/[Stop Monitoring] button

Click this to start or stop monitoring.

[Monitoring Setting] button*1

Click this to change a monitoring update interval.

Monitoring Display Format

Switch "Decimal" or "Hexadecimal" for the display format of a current value.

Data Tag Resource Display Name*2

The resource display name set for a data tag resource is displayed.

Resource ID*3

The resource ID of a data tag resource is displayed.

Current Value*4,*5,*6,*7

The current value of a data tag resource is displayed.

Time Stamp*4,*5,*8,*9

The update date and time of the current value of a data tag resource is displayed (YYYY/MM/DD
HH:FF:SS.XXX).
• YYYY: Year
• MM: Month• DD: Day
• HH: Hour
• FF: Minute• SS: Second• XXX: Millisecond

Data TypeThe data type set for a data tag resource is displayed.

Component Display Name

The display name of a component to which a data tag resource belongs is displayed.

Target Device Setting Name*10

The name of an access target device setting set for a data tag resource is displayed.

Location Parameter*10

The location parameter of a data collector assigned to a data tag resource is displayed.

*1
*2
*3

*4
*5
*6
*7

Cannot be clicked during monitoring.
Displayed in red when "N/A" is displayed in "Current Value."
Hidden when Management Shell Explorer is started.
Can be displayed by right-clicking the column header of the monitoring items and selecting "Resource ID." (Page 210 Switching toshow or hide)"N/A" is displayed while monitoring is stopped.
"N/A" remains displayed until monitoring is started and the current value is updated.
"N/A" is displayed if acquiring a current value fails.
The display order cannot be sorted in ascending or descending order according to this item.
7 Management Shell
7.2 Management Shell Explorer

207

*8
*9

A date and time in the range from 0:00 on January 1st, 1980 to 23:59 on December 31st, 2099 is displayed.
It may be updated at a different timing from a monitoring update interval depending on the performance of a data collector used and thecommunication status.
*10 "-" is displayed when internal data tag resources are monitored.

Monitoring current values of data tag resources
Current values of data tag resources can be monitored.

Registering a data tag resource
The following shows the procedure for registering a data tag resource in the data tag resource monitor window.

Operating procedure

1. Select a data tag resource in the resource list window*1, and drag and drop it onto the data tag resource monitor window.
*1

Multiple data tag resources can be selected.

The data tag resource is registered, and monitoring starts.

• Up to 256 data tag resources can be registered in the data tag resource monitor window.
• Data tag resources that belong to different components can also be registered.
• When restarting Management Shell Explorer, the screen opens with the data tag resource that was
registered last time registered in the data tag resource monitor window.
• Contents changed in the resource list edit dialog are applied to a data tag resource registered in the datatag resource monitor window when registering a resource in the resource list edit dialog.

208

7 Management Shell
7.2 Management Shell Explorer

Canceling registration of a data tag resource
The following shows the procedure for canceling registration of a data tag resource in the data tag resource monitor window.

Operating procedure

1. Select*1 and right-click a data tag resource the registration of which is to be canceled, and select [Cancel Registration].
*1

Multiple data tag resources can be selected.

Registration of the selected data tag resource is canceled.

If the registrations of all data tag resources are canceled during monitoring, monitoring will stop.

7

7 Management Shell
7.2 Management Shell Explorer

209

Switching to show or hide
The following shows the procedure for switching the monitoring item column to show or hide.
However, the columns of "Data Tag Resource Display Name" and "Current Value" cannot be hidden.

Operating procedure

1. Right-click the column header of the monitoring items, and unselect the checkbox of a monitoring item to hide.
The monitoring item is switched to hide.

Switching the display format
The following shows the procedure for switching the display format of a current value (decimal or hexadecimal).
The data types the display format of a current value of which can be switched are as follows:• INT• DINT• LINT• UINT• UDINT• ULINTFor the data types, refer to the following:
Page 544 Data type and value range

Operating procedure

1. Select a display format of the current value for "Monitoring Display Format."
The display format of the current value is switched to the selected one.

• When restarting Management Shell Explorer, it opens with the display format set in decimal.
• Hexadecimal numbers are displayed with zero padding according to the number of bits.
• Negative values in hexadecimal are represented by complements of '2.'210

7 Management Shell
7.2 Management Shell Explorer

Changing a monitoring update interval
The following shows the procedure for changing a monitoring update interval.

Operating procedure

1. Stop monitoring if it is in progress.
Page 213 Stopping monitoring

2. Click the [Monitoring Setting] button.
3. Set an update interval for "Current Value Update Interval," and click the [OK] button.

The monitoring update interval is set to 1000 ms by default.

Precautions
Management Shell Explorer requests Management Shell to provide information on data tag resources (such as current
values) for each monitoring update interval, and updates the information in the data tag resource monitor window when
receiving the result from Management Shell.

7

However, if it cannot receive the result from Management Shell within a monitoring update interval due to a timeout*1 orothers, the information in the data tag resource monitor window is not updated and the previous information remains
displayed.
*1

If a response is not returned after 30 seconds elapses, it will be determined as a timeout.

The following shows the flows of updating information in the data tag resource monitor window when a timeout time (30seconds) is shorter or longer than a monitoring update interval.
• When a timeout time is shorter than a monitoring update interval(1)25

Current Value(Monitoring item)
Management Shell Explorer

(1)

(a)

(1)

75
(b)

50

N/A

(a)

(b)

(a)

(b)

(a)

(b)

Management Shell(2)(1) Monitoring update interval(2) Timeout time(a) Request(b) Response

7 Management Shell
7.2 Management Shell Explorer

211

• When a timeout time is longer than a monitoring update interval
(1)

(1)

(1)
(d)

25

Current Value(Monitoring item)
Management Shell Explorer

(a)

75
(b)

N/A

(a)

(c)

(b)

50
(a)

Management Shell(2)(1) Monitoring update interval(2) Timeout time(a) Request(b) Response(c) Management Shell Explorer does not send a request because it does not receive the response result from Management Shell.
(d) Information in the data tag resource monitor window is not updated.

212

7 Management Shell
7.2 Management Shell Explorer(b)Starting monitoring
The following shows the procedure for starting monitoring when it is stopped.

Operating procedure

1. Click the [Start Monitoring] button.
Monitoring a registered data tag resource is started, and current data is displayed for each monitoring item.

• When a data tag resource registered in the data tag resource monitor window is deleted in the resource list
edit dialog, it is also deleted from the data tag resource monitor window. If all of them are deleted,monitoring stops.
• When restarting Management Shell Explorer, the screen opens with monitoring stopped.

Precautions

7

If any of the following operations is performed during monitoring, monitoring will stop.
• [Management Shell Stop]• [Import]• [Delete All]
• OPC UA server setting (Page 261 Setting an OPC UA server)

Stopping monitoring
The following shows the procedure for stopping monitoring while the monitoring is in progress.

Operating procedure

1. Click the [Stop Monitoring] button.

• "N/A" is displayed in "Current Value" and "Time Stamp" while monitoring is stopped.
• When restarting Management Shell Explorer, the screen opens with monitoring stopped.

7 Management Shell
7.2 Management Shell Explorer

213

Changing current values of data tag resources
Current values of data tag resources being monitored can be changed.
However, they cannot be changed while monitoring is stopped.

Operating procedure

1. Select and click a cell in "Current Value" of a data tag resource.
2. Change the current value of the data tag resource.
A range of values that can be entered for the current value depends on each data type.
For details, refer to the following:
Page 215 Range of available values

Precautions
If a response is not returned after 30 seconds elapses, it will be determined as a timeout and an error message will appear.

214

7 Management Shell
7.2 Management Shell Explorer

Range of available values
The following table shows the ranges of values that can be entered for each data type.
Data type

Range of available values

BOOL

0, 1

INT

• For a display format in decimal-32768 to 32767• For a display format in hexadecimal
H8000 to H7FFF

UINT• For a display format in decimal
0 to 65535• For a display format in hexadecimal
H0000 to HFFFF

DINT• For a display format in decimal-2147483648 to 2147483647• For a display format in hexadecimal
H8000 0000 to H7FFF FFFF

UDINT

• For a display format in decimal
0 to 4294967295• For a display format in hexadecimal
H0000 0000 to HFFFF FFFF

LINT• For a display format in decimal-9223372036854775808 to 9223372036854775807• For a display format in hexadecimal
H8000 0000 0000 0000 to H7FFF FFFF FFFF FFFF

ULINT

• For a display format in decimal
0 to 18446744073709551615• For a display format in hexadecimal
H0000 0000 0000 0000 to HFFFF FFFF FFFF FFFF

REAL

0, 1.401298E-45 to 3.402823E+38 (number of significant digits: 7)

LREAL0, 4.94065645841247E-324 to 1.79769313486231E+308 (number of significant digits: 15)

STRINGASCII (0 to 32 characters)

WSTRINGUTF-16LE (0 to 16 characters)

7

7 Management Shell
7.2 Management Shell Explorer

215

Option setting
The following shows the procedure for setting options when using Management Shell Explorer.

Operating procedure

1. Select [Tool]  [Option].
2. Select the checkbox of an option item, and click the [OK] button.

Item

Description

Display Confirmation Message When Deleting Components, Resources, andIcons

Set whether to display a confirmation message when deleting a resource orothers.

Enable Editing Component Hierarchy Tree Window and Resource List
Window

Set whether to enable component tree editing or resource list editing.

216

7 Management Shell
7.2 Management Shell Explorer

Access target device setting batch replacement
The following shows the screen for replacing access target device settings to configure for a data tag resource in a batch.

Window
Select [Tool]  [Target Device Setting Batch Replacement].

(1)

7
Displayed items
Item

Description

Search for Data Tag Resource toReplace

Target Device Before Replacement

Select the setting name of an access target device setting before
replacement.

Component Display Name

Select the checkbox to search for a data tag resource by using its component
display name, and specify a search condition and search character string (upto 64 characters)*1.

Resource Display Name

Select the checkbox to search for a data tag resource by using its resource
display name, and specify a search condition and search character string (upto 64 characters)*1.

[Search] button

Click this to search for a data tag resource under a specified condition.

Target Device After Replacement*2(1) Data tag resource list

Select the setting name of an access target device setting after replacement.
The list of found data tag resources is displayed.

Target*3

Select the checkbox of a data tag resource for replacement.

Resource Display Name

The resource display name of a data tag resource is displayed.

Component

The path to a component display name to which the data tag resource belongs
is displayed.

Location *3

Set the location of a data collector (up to 300 characters).
Location parameters can be set in the "Location Setting" screen displayed byclicking the [...] button depending on an access target device setting (datacollector) selected for "Target Device After Replacement."*4
For details on the setting method, refer to the manual for a data collector used.

Data Type*3
Number of Characters[Select All] button*3*3[Clear All] button

Set the data type of a data tag resource.*5*3

When setting "STRING" or "WSTRING" for "Data Type," set the number ofcharacters within the following ranges:• STRING: 1 to 32• WSTRING: 1 to 16
Click this to select the checkboxes of all data tag resources in the list.
Click this to unselect the checkboxes of all data tag resources in the list.

7 Management Shell
7.2 Management Shell Explorer

217

Item

Description[Replace] button*3

Click this to update the following information of a data tag resource with its
checkbox selected in the "Target" column with set contents.
• Access target device• Location• Data type
• Number of characters

*1
*2
*3
*4
*5

218

Not case-sensitive
Can be selected when one or more data tag resources are displayed in the data tag resource list.
Can be set or clicked when selecting an access target device setting for "Target Device After Replacement."
The "Location Setting" screen does not appear when using a data collector for which location parameters cannot be set in the screen.
A displayed data type differs depending on an access target device setting (data collector) selected for "Target Device After
Replacement."

7 Management Shell
7.2 Management Shell Explorer

Replacement example when importing a data model in an XML format file
When importing a data model in an XML format file, replace an assigned access target device setting (Dummy Data collector)
with a proper one in the "Target Device Setting Batch Replacement" screen after the import. (Page 200 Behavior of data
model import)
If there are multiple proper access target device settings, it is recommended to prepare an XML format file for each accesstarget device setting, then import a data model multiple times.
When importing a data model without separating files for each access target device setting, it is necessary to replace thesetting with a proper one for each data tag resource after the import.
Ex.

When there are three access target device settings A, B, and C after replacement:
Prepare three XML format files for access target device settings A, B, and C, and import a data model three times.
Then, specify each of three assigned access target device settings (Dummy Data collector) for "Target Device Before
Replacement" in the "Target Device Setting Batch Replacement" screen to replace them with any of the access target device
settings A, B, or C. (Three replacement operations are required.)

A.xml

7
B.xml

C.xml

2.

1.

3.

1. Prepare three XML format files (A.xml, B.xml, and C.xml) for access target device settings A, B, and C.
2. Import a data model three times. (Access target device settings (Dummy Data collector) Dev001, Dev002, and Dev003
are generated.)

3. Replace each of three assigned access target device settings (Dummy Data collector) with any of the access target
device settings A, B, or C. (Perform a replacement operation three times.)

7 Management Shell
7.2 Management Shell Explorer

219

7.3

Access Target Device Setting Function

This section shows the function to select data collectors to use and set access target devices by using Management Shell
Explorer.
For the timing when a data collector connects to, disconnects from, and reconnects to an access target device, refer to thefollowing:
Page 191 Connection to, disconnection from, and reconnection to an access target device

Operating procedure

1. Select [Setting]  [Target Device Setting].
The "Target Device Setting List" screen appears. (Page 220 Access target device setting list screen)

2. Select a row in which the access target device setting is not configured in the access target device setting list, and click
the [Edit] button.
The "Select Data collector" screen appears. (Page 222 Data collector selection screen)

When selecting a row in which the access target device setting is configured, the "Target Device Setting"screen appears instead of the "Select Data collector" screen.

3. Select a data collector to use in the "Select Data collector" screen, and click the [OK] button.
The "Target Device Setting" screen appears. (Page 223 Access target device setting screen)

Access target device setting list screen(1)

Displayed items
Item

Description(1) Access target device setting list*1

Setting Name

The name of an access target device set in the "Target Device Setting" screen
is displayed.

Comment

A comment set in the "Target Device Setting" screen is displayed.

Data Collector

The name of a data collector set in the "Target Device Setting" screen isdisplayed.

Parameter

Communication parameters of a data collector set in the "Target Device
Setting" screen are displayed.

[Reconnect] button

Click this to restart a data collector set in the access target device setting of a
selected row and reconnect to the access target device.

[Parameter Check] button

Click this to check the consistency of the location of an external data tag
resource linked to the access target device setting of a selected row.

[Edit] button

Click this to display the "Select Data collector" screen when selecting a row inwhich the access target device setting is not configured.
Page 222 Data collector selection screen
Click this to display the "Target Device Setting" screen when selecting a row inwhich the access target device setting is configured.
Page 223 Access target device setting screen

220

7 Management Shell
7.3 Access Target Device Setting Function

Item

Description[Delete] button

Click this to delete the setting of a selected row.

*1

An external data tag resource in which the access target device setting of a selected row is used can be checked in the "Location of use
search result" screen displayed by selecting and right-clicking the row then selecting [Search of the location of use for Target Device
setting].
Page 205 Location of use search result screen

7

7 Management Shell
7.3 Access Target Device Setting Function

221

Data collector selection screen

Displayed items
Item

Description

Data Collector Name

A data collector name, version, and developer are displayed.

Read

The availability of data reading in a data collector is displayed.
• Supported: Readable• Not Supported: Unreadable

Write

The availability of data writing in a data collector is displayed.
• Supported: Writable• Not Supported: Unwritable[OK] button

Click this to display the "Target Device Setting" screen.
Page 223 Access target device setting screen

222

7 Management Shell
7.3 Access Target Device Setting Function

Access target device setting screen

Displayed items

7

Item

Description

Setting Name*1

Set the name of an access target device setting (1 to 32 characters).
• The following are displayed to avoid name duplication by default.
Dev001, Dev002, Dev003, ...

Comment
Data Collector Information

Communication Parameter*1*2

Set a comment (up to 100 characters).
Data Collector Name

The name of a data collector set in the "Select Data collector" screen isdisplayed.

[Select Data Collector] button*2

Click this to display the "Select Data collector" screen.
Page 222 Data collector selection screen
Set communication parameters.
For details, refer to the manual for a data collector used.

The same name as that of an access target device setting already set cannot be used.
Appears when opening the "Target Device Setting" screen by performing the following operation.
Click the [Edit] button in the "Target Device Setting List" screen.

7 Management Shell
7.3 Access Target Device Setting Function

223

7.4

Component Tree Edit Function

This section shows the function to edit components or change the hierarchical structure of a component by using
Management Shell Explorer.
A component is created by default when starting Management Shell Explorer for the first time.
A hierarchical relation same as an actual production line can be displayed and managed in a tree.

Industrial PC

Actual production line A

PLC1

PLC2

Components can be edited and the hierarchical structure of a component can be changed in the component tree edit dialog.
The following shows the procedure for displaying the component tree edit dialog.

Operating procedure

1. Select [Window]  [Component Hierarchy Tree Edit].
Configuration element of a component
A component consists of the following elements.
Element

Description

Property

The property of a component.
For editing properties, refer to the following:
Page 226 Editing component properties

Resource list

Resources managed by a component.
For editing resources, refer to the following:
Page 235 Resource List Edit Function

224

7 Management Shell
7.4 Component Tree Edit Function

Adding a component
The following shows the procedure for adding a component to the hierarchy one level below a selected component.

Operating procedure

1. Select a component, then select the icon for adding a component ( ).

When adding a new component, the component display name is displayed in red.

7

Precautions• This function will not be performed if the maximum number of components or the maximum number of hierarchies of acomponent is exceeded.
• If components with the same component display name exist in the same hierarchy, the display order may differ between thecomponent tree window and the component tree edit dialog. In this case, check the component name in the property
window before operation.

7 Management Shell
7.4 Component Tree Edit Function

225

Editing component properties
The following shows the procedure for editing the property of a created component.

Operating procedure

1. Select a component, and edit each item in the property.

Item

Setting content

Component Name

*1

Set the name of a component (up to 32 characters).
When adding a component, the following are displayed to avoid name duplication by default.
Component1, Component2, Component3, ...

Component ID*2

The ID of a component is displayed (not editable).
An ID is automatically assigned when registering a component.

Component Display Name

Set the display name of a component (up to 64 characters).
When adding a component, "New Component" is displayed by default. However, if there is another component with thecomponent display name of "New Component" in a same hierarchy, the following are displayed to avoid name duplication.
New Component (1), New Component (2), New Component (3), ...

Component Icon

Set the path of an icon file that represents a component (up to 255 characters including the extension).
An icon file can be selected in the "Icon Setting" screen displayed by clicking the [...] button.
It can also be added and deleted in the "Icon Setting" screen.
Page 227 Adding an icon, Page 227 Deleting an icon

*1
*2

Used to identify a component.
Used for referencing Management Shell from an edge application.

When editing a property item of a component, the component display name is displayed in red.

Precautions
If a file set for "Component Icon" does not exist in '(installation destination of Edgecross Basic Software)\Management
Shell\Explorer\icon,' it is displayed as the following icon.

226

7 Management Shell
7.4 Component Tree Edit FunctionAdding an icon

Operating procedure

1. Click the [Add] button.

2. Select an icon to add.
• File names are not case-sensitive.
• An icon file with the extension .bmp, .png, .jpg, .gif, or .ico can be added.
• Up to 247 icon files can be added.

7

Precautions• Be sure to add icons in the "Icon Setting" screen.
• An icon file in a shared folder cannot be added.
• If selecting an icon file with a same name as an icon*1 already registered, the existing file will be overwritten.
*1

Excluding the icons provided by default.

Deleting an icon

Operating procedure

1. Select an icon file, and click the [Delete] button.

Precautions• Be sure to delete icons in the "Icon Setting" screen.
• Icons provided by default cannot be deleted.
• If the icon of a component being used is deleted, the component will be displayed with the following icon. However, thecontent of "Component Icon" that is a property item of the component are not changed.

7 Management Shell
7.4 Component Tree Edit Function

227

Moving a component
The following shows the procedure for moving a component.

Operating procedure

1. Select a component, and drag and drop it onto a move destination component.

The component in the hierarchy under a selected component is also moved at the same time.

Precautions
If the component display name or component name of a moved component overlaps with one in a same hierarchy, each nameof the moved component is displayed as follows:• Component display name (XXX)• Component name_XXX
XXX is numbered in order from 1 to avoid name duplication in the same hierarchy. However, if the number of characters in thename including (XXX) or _XXX exceeds its maximum number, the component cannot be moved.

228

7 Management Shell
7.4 Component Tree Edit Function

Copying a component
The following shows the procedure for copying a component.

Operating procedure

1. Select and right-click a component, and select [Copy].
A selected component is copied to the clipboard.

The component in the hierarchy under a selected component is also copied at the same time.

7 Management Shell
7.4 Component Tree Edit Function

7229

Cutting a component
The following shows the procedure for cutting a component.

Operating procedure

1. Select and right-click a component, and select [Cut].

• The component in the hierarchy under a selected component is also cut at the same time.
• A cut component is shaded, and deleted after pasted.

230

7 Management Shell
7.4 Component Tree Edit Function

Pasting a component
The following shows the procedure for pasting a copied or cut component to a hierarchy under another component.

Operating procedure

1. Select and right-click a component, and select [Paste].

Precautions
If the component display name or component name of a pasted component overlaps with one in a same hierarchy, each nameof the pasted component is displayed as follows:• Component display name (XXX)• Component name_XXX
XXX is numbered in order from 1 to avoid name duplication in the same hierarchy. However, if the number of characters in thename including (XXX) or _XXX exceeds its maximum number, the component cannot be pasted.

7 Management Shell
7.4 Component Tree Edit Function

231

7

Deleting a component
The following shows the procedure for deleting a component.

Operating procedure

1. Select a component, then select the icon for deleting a component ( ).

The component in the hierarchy under a selected component is also deleted.

Precautions
The top component cannot be deleted.

232

7 Management Shell
7.4 Component Tree Edit Function

Searching for a component
The following shows the procedure for searching for a component.

Operating procedure

1. Click the [Find] button.

2. Enter a search character string for "Find String" (up to 64 characters).

7
3. Set search options as necessary, and click the [Find Next] button.
Item

Setting content

Case Sensitive

Select the checkbox to distinguish between upper-case and lower-casecharacters included in a search character string.

Find Range

Specify a range to search for a component.
• All: The entire component tree is searched.
• Below Selected Hierarchy: A selected component and one(s) in its
hierarchy are searched.

Find Direction*1

Select a direction to search for a component.
• Down: Components are searched downward from a selected one.
• Up: Components are searched upward from a selected one.

*1

When selecting "Below Selected Hierarchy" for "Find Range," only "Down" can be selected.

7 Management Shell
7.4 Component Tree Edit Function

233

Registering a component
The following shows the procedure for registering the component tree that is edited.

Operating procedure

1. Click the [OK] or [Apply] button.
A registered component tree appears in the component tree window.

• When clicking the [Apply] button, the component tree edit dialog does not close even after registration.
• After registration, components are sorted in ascending order of their display names by comparing character
strings and displayed in a same hierarchy.

234

7 Management Shell
7.4 Component Tree Edit Function

7.5

Resource List Edit Function

This section shows the function to edit resources managed by a component by using Management Shell Explorer.
The resource list can be edited in the resource list edit dialog.
The following shows the procedure for displaying the resource list edit dialog.

Operating procedure

1. Select [Window]  [Resource List Edit].

7

7 Management Shell
7.5 Resource List Edit Function

235

Adding a data tag resource
The following shows the procedure for adding a data tag resource.

Operating procedure

1. Select a component to which a data tag resource is added.

2. Select the icon for adding an external data tag resource ( ) or the icon for adding an internal data tag resource ( ).

3. Set each item in the "Add External Data Tag Resource" or "Add Internal Data Tag Resource" screen, and click the [OK]button.
• "Add External Data Tag Resource" screen

Item

Setting content

Data Tag Resource Name*1

Set the name of an external data tag resource (up to 32 characters).

Resource Display Name

Set the display name of an external data tag resource (up to 64 characters).

236

7 Management Shell
7.5 Resource List Edit Function

Item

Setting content

Target Device

Select an access target device for an external data tag resource.
The "Select Data collector" screen appears when selecting "[Add]," and the "Target Device Setting"screen appears after selecting a data collector.
Page 222 Data collector selection screen
Page 223 Access target device setting screen

LocationSet the location*2 of a data collector (up to 300 characters).
Depending on a data collector used, location parameters can be set in the "Location Setting" screen
displayed by clicking the [Setting] button.*3
For details on the setting method, refer to the manual for a data collector used.

Data Type

Select the data type of an external data tag resource.*4

Number of Characters

Set the number of characters within the following ranges when selecting "STRING" or "WSTRING"
for "Data Type."• STRING: 1 to 32• WSTRING: 1 to 16

*1
*2
*3
*4

Used to identify a resource.
Information of a device connected to a data collector.
The [Setting] button does not appear when a data collector in which location parameters cannot be set in the "Location Setting" screen
is used.
The data type to be displayed varies depending on a data collector used.

• If no access target device is set, the "Select Data collector" screen appears when selecting the icon foradding an external data tag resource ( ).
Page 222 Data collector selection screen

7• When adding a new external data tag resource, the resource display name is displayed in red.
• When adding an external data tag resource to a component, the component display name is displayed inred.
• After adding an external data tag resource, click the [Parameter Check] button in the "Target Device Setting
List" screen to check the location consistency.
Page 220 Access target device setting list screen• "Add Internal Data Tag Resource" screen (setting method: value)

Item

Setting content

Data Tag Resource Name*1

Set the name of an internal data tag resource (up to 32 characters).

Resource Display Name

Set the display name of an internal data tag resource (up to 64 characters).

Setting Method

Select "Value."

Data Type

Select the data type of an internal data tag resource.

Number of Characters

Set the number of characters within the following ranges when selecting "STRING" or "WSTRING" for "Data Type."• STRING: 1 to 32• WSTRING: 1 to 16

Default Value

Set a value to set for the current value of an internal data tag resource when either of the following operations was performed:• Starting Management Shell• Adding or editing an internal data tag resource
The range of values that can be set as the default value and the number of characters that can be entered differ for each datatype.
For details, refer to the following:
Page 544 Values that can be entered in the screen
Page 544 Data type and value range

7 Management Shell
7.5 Resource List Edit Function

237

Item

Setting content

Read-only

Select the checkbox to set an internal data tag resource to read-only.

*1

238

Used to identify a resource.

7 Management Shell
7.5 Resource List Edit Function

• "Add Internal Data Tag Resource" screen (setting method: operation)

Item

Setting content

Data Tag Resource Name*1

Set the name of an internal data tag resource (up to 32 characters).

Resource Display Name

Set the display name of an internal data tag resource (up to 64 characters).

Setting Method

Select "Operation."First Term

The contents set in the "Operation Expression Setting" screen are displayed.*2[Setting] button

Click this to display the "Operation Expression Setting" screen.
Page 240 "Operation Expression Setting" screen

Operation Details

The operator of an operation expression set in the "Operation Expression Setting" screen is displayed.

Second Term

The contents set in the "Operation Expression Setting" screen are displayed.*2

Data Type

Select the data type of an internal data tag resource.
Data types that can be specified differ depending on an operator and data types set in the "Operation Expression Setting"screen.
For details, refer to the following:
Page 242 Combinations of data types that can be specified for each operator

*1
*2

7

Used to identify a resource.
After applying the setting, if an external data tag resource specified in the "Select Data Tag Resource" screen no longer exists in thereference (an external data tag resource that matches 'full path of the name of a component to which the external data tag resource
belongs\external data tag resource name' specified when applying the setting no longer exists) by performing an operation such as thefollowing ones, the message "No data tag resource is found" appears. Set the reference again.
(Example) Changing the name of the external data tag resource(Example) Changing the name of a component to which the external data tag resource belongs• When adding a new internal data tag resource, the resource display name is displayed in red.
• When adding an internal data tag resource to a component, the component display name is displayed inred.

7 Management Shell
7.5 Resource List Edit Function

239

"Operation Expression Setting" screen
The following shows the screen for setting an operation expression for an internal data tag resource (operation) to be addedor edited.

Window
Select "Operation" for "Setting Method" in the "Add Internal Data Tag Resource" screen, and click the [Setting] button.

Item

Setting content

First Term

Data Tag Resource

Constant

Operation
Details

Operator

SecondTerm

Data Tag Resource

Constant

240

Data Tag Resource

An external data tag resource selected in the "Select Data Tag Resource" screen isdisplayed as follows:*1• Full path of the display name of a component to which the external data tag resource
belongs + '\' + external data tag resource display name

[Setting] button

Click this to display the "Select Data Tag Resource" screen.
For the method for selecting an external data tag resource, refer to the following:
Page 241 "Select Data Tag Resource" screen

Data TypeThe data type of an external data tag resource selected in the "Select Data Tag
Resource" screen is displayed.*2

Data Type

Select the data type of a constant.*2,*3

Setting Value

Set a constant value.
The range of values that can be set and the number of characters that can be entereddiffer for each data type.
For details, refer to the following:
Page 544 Values that can be entered in the screen
Page 544 Data type and value range
Select an operator used in an operation expression.
The following operators can be used:• Logical operations (AND, OR)• Four arithmetic operations (+, -, *, /)Operators that can be specified differ depending on the data type.
For details, refer to the following:
Page 242 Combinations of data types that can be specified for each operator

Data Tag Resource

An external data tag resource selected in the "Select Data Tag Resource" screen isdisplayed as follows:*1• Full path of the display name of a component to which the external data tag resource
belongs + '\' + external data tag resource display name

[Setting] button

Click this to display the "Select Data Tag Resource" screen.
For the method for selecting an external data tag resource, refer to the following:
Page 241 "Select Data Tag Resource" screen

Data TypeThe data type of an external data tag resource selected in the "Select Data Tag
Resource" screen is displayed.*2

Data Type

Select the data type of a constant.*2,*3

Setting Value

Set a constant value.
The range of values that can be set and the number of characters that can be entereddiffer for each data type.
For details, refer to the following:
Page 544 Values that can be entered in the screen
Page 544 Data type and value range

7 Management Shell
7.5 Resource List Edit Function

*1

*2
*3

After applying the setting, if an external data tag resource specified in the "Select Data Tag Resource" screen no longer exists in thereference (an external data tag resource that matches 'full path of the name of a component to which the external data tag resource
belongs\external data tag resource name' specified when applying the setting no longer exists) by performing an operation such as thefollowing ones, the message "No data tag resource is found" appears. Set the reference again.
(Example) Changing the name of the external data tag resource(Example) Changing the name of a component to which the external data tag resource belongs
For the combinations of data types that can be specified for the first and second terms, refer to the following:
Page 242 Combinations of data types that can be specified for each operator
If "Constant" is selected for both the first and second terms, an error occurs. Select "Data Tag Resource" for either one.

"Select Data Tag Resource" screen
Select an external data tag resource to use in the "Operation Expression Setting" screen.

Operating procedure

1. Click the [Setting] button in the "Operation Expression Setting" screen to open the "Select Data Tag Resource" screen.
2. Select a component to be referenced in the component tree window.
External data tag resources with data types other than STRING and WSTRING that belong to the selected component are
displayed in the resource list window.

3. Select an external data tag resource to be referenced in the resource list window.

7

The data type of an external data tag resource that can be specified differs depending on the combinations of an operator anddata types specified in the "Operation Expression Setting" screen. For details, refer to the following:
Page 242 Combinations of data types that can be specified for each operator

4. Click the [OK] button.
• Clicking the [Find] button in the component tree window displays the "Component Find" screen. For theoperation method, refer to the following:
Page 233 Searching for a component• Clicking the [Find] button in the resource list window displays the "Resource Find" screen. For the operation
method, refer to the following:
Page 256 Searching for a resource

7 Management Shell
7.5 Resource List Edit Function

241Combinations of data types that can be specified for each operator
The following table shows the data types that can be specified for each operator in the "Add Internal Data Tag Resource"
screen (setting method: operation) and "Operation Expression Setting" screen.
Operator

Data type of an internal data tag resource(operation)

Data types for the first and second terms

Logical operations (AND, OR)

BOOL (binary (0 or 1))

BOOL (binary (0 or 1))

Four arithmetic operations (+, -, *, /)*1

INT/DINT/LINT (signed integer)*2

INT/DINT/LINT (signed integer)*2
*2

*1
*2
*3
*4

242

UINT/UDINT/ULINT (unsigned integer)

UINT/UDINT/ULINT (unsigned integer)*2

REAL/LREAL (real number)*3,*4

REAL/LREAL (real number)*3,*4

A combination of signed integers, unsigned integers, and real numbers cannot be used in one operation expression.
For division, values after the decimal point are rounded down.
Depending on the value in the operation term, an error may occur due to rounding values less than the number of significant digits,
underflow, loss of trailing digits, and loss of significant digits.
When using an operation term the data type of which is REAL, the accuracy of the REAL type is applied even when the data type of aninternal data tag resource (operation) is LREAL. To apply that of the LREAL type, use only an operation term the data type of which is
LREAL.

7 Management Shell
7.5 Resource List Edit Function

Editing data tag resource properties
The following shows the procedure for editing the property of a data tag resource.

Operating procedure

1. Select a component for which a data tag resource is edited.

2. Double-click a data tag resource.

7

3. Edit each item in the "Edit External Data Tag Resource" or "Edit Internal Data Tag Resource" screen, and click the [OK]button.
For the items to edit, refer to the following:
Page 236 Adding a data tag resource• Resource IDs cannot be edited. IDs are automatically assigned when registering data tag resources.
(Resource IDs are used to identify resources.)• When editing a property item of a data tag resource, the resource display name is displayed in red.
• When editing a data tag resource of a component, the component display name is displayed in red.

7 Management Shell
7.5 Resource List Edit Function243Adding a file resource
The following shows the procedure for adding a file resource.

Operating procedure

1. Select a component to which a file resource is added.

2. Select the icon for adding a file resource ( ).

• When adding a new file resource, the resource display name is displayed in red.
• When adding a file resource to a component, the component display name is displayed in red.

244

7 Management Shell
7.5 Resource List Edit Function

Editing file resource properties
The following shows the procedure for editing the properties of a file resource.

Operating procedure

1. Select a component for which a file resource is edited.

2. Select a file resource, and edit each item in the property.

Item

7

Setting content*1File Resource Name

Set the name of a file resource (up to 32 characters).
When adding a file resource, "New File" is displayed by default. However, if there is anotherresource the resource name of which is "New File," the following are displayed to avoid name
duplication.
New File(1), New File(2), New File(3), ...

Resource ID*1

The ID of a file resource is displayed (not editable).
An ID is automatically assigned when registering a resource.

Resource Display Name

Set the display name of a file resource (up to 64 characters).
When adding a file resource, "New File Resource" is displayed by default. However, if there isanother resource the resource display name of which is "New File Resource," the following aredisplayed to avoid name duplication.
New File Resource(1), New File Resource(2), New File Resource(3), ...

File Path

Set the path of a file to manage as a file resource (up to 259 characters).*2,*3,*4
A file path can be selected in the "Open" screen displayed by clicking the [...] button.

*1
*2
*3
*4

Used to identify a resource.
A file in a shared folder can also be specified.
Only one file can be specified.
A folder cannot be specified.

7 Management Shell
7.5 Resource List Edit Function245• When editing a property item of a file resource, the resource display name is displayed in red.
• When editing a file resource of a component, the component display name is displayed in red.

246

7 Management Shell
7.5 Resource List Edit Function

Adding a folder resource
The following shows the procedure for adding a folder resource.

Operating procedure

1. Select a component to which a folder resource is added.

2. Select the icon for adding a folder resource ( ).

7

• When adding a new folder resource, the resource display name is displayed in red.
• When adding a folder resource to a component, the component display name is displayed in red.

7 Management Shell
7.5 Resource List Edit Function247

Editing folder resource properties
The following shows the procedure for editing the properties of a folder resource.

Operating procedure

1. Select a component for which a folder resource is edited.

2. Select a folder resource, and edit each item in the property.

Item

Setting content

Folder Resource Name*1

Set the name of a folder resource (up to 32 characters).
When adding a folder resource, "New Folder" is displayed by default. However, if there is anotherresource the resource name of which is "New Folder," the following are displayed to avoid name
duplication.
New Folder(1), New Folder(2), New Folder(3), ...

Resource ID*1

The ID of a folder resource is displayed (not editable).
An ID is automatically assigned when registering a resource.

Resource Display Name

Set the display name of a folder resource (up to 64 characters).
When adding a folder resource, "New Folder Resource" is displayed by default. However, if there isanother resource the resource display name of which is "New Folder Resource," the following aredisplayed to avoid name duplication.
New Folder Resource(1), New Folder Resource(2), New Folder Resource(3), ...

Folder Path

Set the path of a folder managed as a folder resource (up to 247 characters).*2,*3
A folder path can be selected in the "Select Folder" screen displayed by clicking the [...] button.

*1
*2
*3

Used to identify a resource.
A shared folder can also be set.
Only one folder can be set.

248

7 Management Shell
7.5 Resource List Edit Function• When editing a property item of a folder resource, the resource display name is displayed in red.
• When editing a folder resource of a component, the component display name is displayed in red.

7

7 Management Shell
7.5 Resource List Edit Function

249

Moving a resource
The following shows the procedures for moving a resource to another component.

Cut  paste
The procedure is as follows:

Operating procedure

1. Select a component from which a resource is moved.

2. Select and right-click a resource, and select [Cut].

3. Perform the procedure shown in the following section to paste the resource to a move destination component.
Page 253 Pasting a resource• Multiple resources can be moved together.
• A cut resource is shaded, and deleted after pasted.

250

7 Management Shell
7.5 Resource List Edit FunctionDrag and drop
The procedure is as follows:

Operating procedure

1. Select a component from which a resource is moved.

2. Select a resource, and drag and drop it onto a move destination component.

7• Multiple resources can be moved together.
• When moving a resource, the resource display name is displayed in red.
• When moving a resource to/from a component, the component display names of the destination and source
are displayed in red.

Precautions
If there is any resource with the same resource name or resource display name, each name of a moved resource is displayed
as follows:• Resource name (XXX)*1• Resource display name (XXX)*2*1*2

XXX is numbered in order from 1 to avoid name duplication in the move destination and source components. However, if the number ofcharacters in the name including (XXX) exceeds its maximum number, the resource cannot be moved.
XXX is numbered in order from 1 to avoid name duplication in the move destination component. However, if the number of characters in
the name including (XXX) exceeds its maximum number, the resource cannot be moved.

7 Management Shell
7.5 Resource List Edit Function251

Copying a resource
The following shows the procedure for copying a resource.

Operating procedure

1. Select a component from which a resource is copied.

2. Select and right-click a resource, and select [Copy].

Multiple resources can be copied together.

252

7 Management Shell
7.5 Resource List Edit Function

Pasting a resource
The following shows the procedure for pasting a copied or cut resource.

Operating procedure

1. Select a component to which a resource is pasted.

2. Select and right-click a blank row, and select [Paste].

7• When pasting a resource, the resource display name is displayed in red.
• When pasting a resource to a component, the component display name is displayed in red. (When pasting itby cutting  pasting, the component display name of the cut source is also displayed in red.)Precautions
If there is any resource with the same resource name or resource display name, each name of a pasted resource is displayed
as follows:• Resource name (XXX)*1• Resource display name (XXX)*2*1*2

XXX is numbered in order from 1 to avoid name duplication in the paste destination component (and the cut source component when
pasting a resource by cutting  pasting). However, if the number of characters in the name including (XXX) exceeds its maximum
number, the resource cannot be pasted.
XXX is numbered in order from 1 to avoid name duplication in the paste destination component. However, if the number of characters in
the name including (XXX) exceeds its maximum number, the resource cannot be pasted.

7 Management Shell
7.5 Resource List Edit Function

253Deleting a resource
The following shows the procedure for deleting a resource.

Operating procedure

1. Select a component from which a resource is deleted.

2. Select a resource, then select the icon for deleting a resource ( ).

When deleting a resource from a component, the component display name is displayed in red.

254

7 Management Shell
7.5 Resource List Edit Function

Searching for a component
The following shows the procedure for searching for a component.

Operating procedure

1. Click the [Find] button.

2. Enter a search character string for "Find String" (up to 64 characters).

7

3. Set search options as necessary, and click the [Find Next] button.
Item

Setting content

Case Sensitive

Select the checkbox to distinguish between upper-case and lower-casecharacters included in a search character string.

Find Range

Specify a range to search for a component.
• All: The entire component tree is searched.
• Below Selected Hierarchy: A selected component and one(s) in its
hierarchy are searched.

Find Direction*1

Select a direction to search for a component.
• Down: Components are searched downward from a selected one.
• Up: Components are searched upward from a selected one.

*1

When selecting "Below Selected Hierarchy" for "Find Range," only "Down" can be selected.

7 Management Shell
7.5 Resource List Edit Function

255

Searching for a resource
The following shows the procedure for searching for a resource.

Operating procedure

1. Click the [Find] button.

2. Enter a search character string for "Find String" (up to 64 characters).

3. Set search options as necessary, and click the [Find Next] button.
Item

Setting content

Case Sensitive

Specify whether to distinguish between upper-case and lower-casecharacters included in a search character string.

Find Direction

Select a direction to search for a resource.
• Down: Resources are searched downward from a selected one.
• Up: Resources are searched upward from a selected one.

256

7 Management Shell
7.5 Resource List Edit Function

Registering a resource
The following shows the procedure for registering an edited resource.

Operating procedure

1. Click the [OK] or [Apply] button.

7• When clicking the [Apply] button, the resource list edit dialog does not close even after registration.
• When deleting, editing, or moving a data tag resource registered in the data tag resource monitor, theoperation is also applied to the data tag resource monitor.

7 Management Shell
7.5 Resource List Edit Function

257

Starting a file resource
The following shows the procedure for starting a file resource.
Starting a file resource opens the file in an application associated with it in Windows. If the file resource fails to start, check if
the application is associated with the file.
Note that a file may not be opened in some applications even if it is associated with an application.

Operating procedure

1. Double-click a file resource in the resource list window.

Starting a folder resource
The following shows the procedure for starting a folder resource.
Starting a folder resource opens the folder in Windows Explorer.

Operating procedure

1. Double-click a folder resource in the resource list window.

258

7 Management Shell
7.5 Resource List Edit Function

7.6

OPC UA Connection Function

This section shows the function to enable Management Shell to run as an OPC UA server and provide an edge applicationthat is an OPC UA client with a model access I/F and a data access I/F.
By connecting an edge application that supports a model access I/F (technology: OPC UA) or a data access I/F (technology:
OPC UA) with Management Shell, the following operations can be performed. For details, refer to the manual for an edge
application used.
• Referencing data models managed by Management Shell• Reading and writing data in equipment, devices, or lines in production sites via Management Shell• Monitoring data in equipment, devices, or lines in production sites via Management Shell
For the overviews of data reading and writing and data monitoring, refer to the following:
Page 260 Overviews of data reading and writing and data monitoring

When connecting to Management Shell, which is an OPC UA server, from an edge application on an industrial
PC other than one on which Edgecross Basic Software is installed, it is required to set communication
connections to Management Shell to be allowed.
For the setting method, refer to the following:
Page 560 Allowing Communication Connections between Industrial PCs

7

7 Management Shell
7.6 OPC UA Connection Function

259

Overviews of data reading and writing and data monitoring
The following shows the overviews of data reading and writing and data monitoring.

Data reading and writing
Data writing

Data reading
(1)

(1)
Ò

Ó

Ò

(2)

(2)

Ó

Ó

Ó
(3)

(3)
(1) Edge application(2) Management Shell(3) Target device A data reading or writing request is sent at the timing when data is read or written.
 Data is read or written in response to the request.

Data monitoring(1)ÔThe conditionis satisfied.

(2)
Ó

(a)

Ò

(b)
Ó

(3)
(1) Edge application(2) Management Shell(3) Target device(a) Notification condition(b) Monitoring target data information

 Register monitoring target data and a notification condition in advance.
 The data registered in step  is monitored periodically.
 The data is sent when the notification condition registered in step  is satisfied.

260

7 Management Shell
7.6 OPC UA Connection Function

Setting an OPC UA server
The following shows the procedure and screen for setting the connection and a server certificate for Management Shell thatruns as an OPC UA server by using Management Shell Explorer.
Management Shell starts as an OPC UA server and creates a server certificate according to contents set in Management
Shell Explorer.

Operating procedure

1. Select [Setting]  [OPC UA Setting].
2. Select the [Server Setting] tab, and then select the [Connection Setting] tab.
3. Set each item.

7

Item

Setting content

Port Number

Set the port number of an OPC UA server (1024 to 65535).

End point URL*1

The endpoint URL of an OPC UA server is displayed in the following format.
• opc.tcp://[industrial PC host name]:[port number]

Security Policy*1

Select a security policy.
• None: No security• Basic128Rsa15 (Not recommended)*2: 128-bit encryption• Basic256 (Not recommended)*2: 256-bit encryption• Basic256Sha256: 256-bit encryption (using Sha256 algorithm)

Security Mode*1

Select a security mode.
• None: No security• Sign: Adding a signature to data
• Sign & Encrypt: Adding a signature and encrypt the data

Certificate Automatic Exchange

Select the checkbox to exchange certificates automatically.*3,*4
Note that a certificate is not confirmed by a user when data in Management Shell is read and written
in an edge application if selecting the checkbox.

*1
*2
*3
*4

Configure the same setting for an edge application.
For the setting method, refer to the manual for an edge application used.
Not recommended in the OPC UA specifications, because it is considered less secure.
Not recommended in an open network environment such as the Internet or an intranet because all clients are allowed to connect.
When selecting the checkbox, the connection with Management Shell will succeed.
When not selecting the checkbox, the client certificate for an edge application is registered in the reject list in Management Shell and theconnection with Management Shell will fail. In this case, register the client certificate in the trust list, then connect to Management Shellagain.
Page 263 Managing OPC UA client certificates

7 Management Shell
7.6 OPC UA Connection Function

261

4. Select the [Certificate Setting] tab.
5. Set each item, and click the [Apply] button.

Item

Setting content*1

OPC UA Server Name

Set the name of an OPC UA server (1 to 64 characters).
It is automatically replaced with the host name*2 of an industrial PC when a server certificate is
generated, if a value is set for "[ServerName]."Organization Name

Set the name of an organization (1 to 64 characters).

Unit of Organization

Set the unit of an organization (1 to 64 characters).

Region Name

Set the name of a region (1 to 128 characters).

State

Set a state (1 to 128 characters).

Country Name

Set the abbreviation of a country name (2 characters).

Expiration Date (Year)

Set the effective period of a client certificate (1 to 20 years).

IP address (IPv4)

Set the IP address (IPv4) for an environment where an OPC UA server operates.
It must be set when specifying the IP address instead of the computer name as the endpoint URL of
an OPC UA server for connection.
(Example) When the IP address of an OPC UA server is 192.168.0.1, set this item to 192.168.0.1 toconnect the client side to a server with specifying 'opc.tcp://192.168.0.1:48010' as the endpoint URL.
If not setting any IP address for this item, a server is connected with specifying 'opc.tcp://
PC1075:48010' as the computer name.
By clicking the [Add] button, an IP address can be added (up to 2).
The default setting is 127.0.0.1 and can be changed within the range of 0.0.0.0 to 255.255.255.255.
In addition, by clicking the [Delete] button, a selected IP address can be deleted.

*1*2

Recommended to combine an application name and a computer name. (Example: ManagementShell_PC1)
When setting either of the following types of computer names not recommended by Microsoft, Management Shell may not run properly.
- Computer name that has 16 characters or more
- Computer name that has characters other than alphanumeric ones or '-'Precautions• An IP address set for "IP address (IPv4)" is set for the subject alternative name of a server certificate.
• "IP address (IPv4)" must be set to the same value as the IP address of an industrial PC on which Management Shell runs.
When changing the IP address, change the value accordingly. However, if the IP address is set to change dynamically,such as DHCP, a server may not be connected even if the IP address is specified.

262

7 Management Shell
7.6 OPC UA Connection Function

Managing OPC UA client certificates
The following shows the procedure and screen for displaying certificates in a list, moving them to the trust or reject list, anddisplaying the detailed information by using Management Shell Explorer.

Operating procedure

1. Select [Setting]  [OPC UA Setting].
2. Select the [Client Certificate] tab, and move a certificate to the trust or reject list.

7

Item

Setting content

Trust List

The names of client certificates registered in the trust list are displayed in a list.
Double-clicking a selected client certificate displays the "Certificate" screen.
For a display example of the "Certificate" screen, refer to the following:
Page 264 Certificate screen
Click this to move a client certificate selected in the reject list to the trust list (multiple
selections allowed).
When moving an OPC UA client certificate to the trust list, the certificate authentication isallowed.*1
Click this to move a client certificate selected in the trust list to the reject list (multiple
selections allowed).
When moving an OPC UA client certificate to the reject list, the certificate authentication
is denied.*2

Reject List

Client certificates registered in the reject list are displayed in a list.
Double-clicking a selected client certificate displays the "Certificate" screen.
For a display example of the "Certificate" screen, refer to the following:
Page 264 Certificate screen
Click this to update the contents in the trust list and reject list.

[Delete] button

Click this to delete a selected client certificate.

[Details] button

Click this to display the "Certificate" screen. (Details on a selected client certificate aredisplayed.*3)
For a display example of the "Certificate" screen, refer to the following:
Page 264 Certificate screen

*1
*2
*3

The connection between the OPC UA client and Management Shell will be enabled.
The connection between the OPC UA client and Management Shell will be disabled.
When selecting multiple client certificates, the details on the top client certificate in the list are displayed.

7 Management Shell
7.6 OPC UA Connection Function

263

Certificate screen
The following shows a display example of the "Certificate" screen. When clicking the [Install Certificate] button, the certificate
is installed on Windows.*1*1

264

It does not affect the operation of Management Shell.

7 Management Shell
7.6 OPC UA Connection Function

7.7

IT Gateway Cooperation Function

This section shows the function to respond to requests for data model reference, data reading, and data writing from an IT
gateway, and perform these operations.
For details on an IT gateway, refer to the manual for an IT gateway used.

(2)
(1)
(a)

(a)
(4)

(3)
(a)

(a)
(5)

(1) IT system(2) Cloud service(3) IT gateway 1(4) IT gateway 2(5) Management Shell(a) Data models are referenced or the current value of a data tag resource is acquired or changed.

7

Starting, stopping, and restarting an IT gateway
An IT gateway starts, stops, and restarts in response to the following operations:Behavior of an IT gateway

Operation

Start

Start Management Shell by either of the following operations:• Start Windows.
• Select [Management Shell]  [Management Shell Start].
Add an IT gateway setting.

Stop

Stop Management Shell by either of the following operations:• Shut down Windows.
• Select [Management Shell]  [Management Shell Stop].
Delete an IT gateway setting.

Restart(Stop  start)

Change an IT gateway setting.
Click the [Restart] button in the "IT Gateway Setting List" screen.

Considerations
If the execution file of an IT gateway used does not exist or is corrupted, the IT gateway will not start and an error will occur.

7 Management Shell
7.7 IT Gateway Cooperation Function265Procedure for setting an IT gateway
The following shows the procedure for setting an IT gateway.

Operating procedure

1. Select [Setting]  [IT Gateway Setting].
The "IT Gateway Setting List" screen appears. (Page 266 IT gateway setting list screen)

2. Select a row in which the IT gateway setting is not configured in the IT gateway setting list, and click the [Edit] button.
The "IT Gateway Selection" screen appears. (Page 267 IT gateway selection screen)

When selecting a row in which the IT gateway setting is configured, the "IT Gateway Setting" screen appears
instead of the "IT Gateway Selection" screen.

3. Select an IT gateway to use in the "IT Gateway Selection" screen, and click the [OK] button.
The "IT Gateway Setting" screen appears. (Page 268 IT gateway setting screen)

IT gateway setting list screen(1)

Displayed items
Item

Description(1) IT gateway setting list

Setting Name

A setting name set in the "IT Gateway Setting" screen is displayed.

IT Gateway TypeThe type of an IT gateway selected in the "IT Gateway Selection" screen isdisplayed.

Comment

A comment set in the "IT Gateway Setting" screen is displayed.

IT Gateway

The name of an IT gateway selected in the "IT Gateway Selection" screen isdisplayed.

[Restart] button

Click this to restart an IT gateway set in the IT gateway setting of a selectedrow.

[Edit] button

Click this to display the "IT Gateway Selection" screen when selecting a row inwhich the IT gateway setting is not configured.
Page 267 IT gateway selection screen
Click this to display the "IT Gateway Setting" screen when selecting a row inwhich the IT gateway setting is configured.
Page 268 IT gateway setting screen[Delete] button

Click this to delete the setting of a selected row.

266

7 Management Shell
7.7 IT Gateway Cooperation Function

IT gateway selection screen

Displayed items
Item

Description

IT Gateway Name

An IT gateway name, version, and developer are displayed.

IT Gateway Type*1

Select an IT gateway type.

[OK] button*2

Click this to display the "IT Gateway Setting" screen.
Page 268 IT gateway setting screen

*1

*2

7

Depending on a supported IT gateway I/F, any of the following items can be selected.
Historical data file access I/F: Data Storing
Real-time data publishing I/F-G: Data Distribution
Model access I/F-G or data access I/F-G: Model Data AccessCannot be clicked when selecting "Data Storing" or "Data Distribution" for "IT Gateway Type."

7 Management Shell
7.7 IT Gateway Cooperation Function267

IT gateway setting screen(1)

Displayed items
Item

Description*1

Setting Name

Set the name of an IT gateway setting (1 to 32 characters).
• The following are displayed to avoid name duplication by default.
Gateway01, Gateway02, Gateway03, ...

Comment

Set a comment (up to 100 characters).

(1) Service parameter setting

Set service parameters.
For details, refer to the manual for an IT gateway used.

*1

268

The same name as that of an IT gateway setting already set cannot be used.

7 Management Shell
7.7 IT Gateway Cooperation Function

7.8

One-shot Collection Function

This section shows the function to collect a value of a data tag resource specified as a collection target (collection target
resource) and save it to a file or database when a value of a data tag resource specified as a monitoring target (monitoringtarget resource) changes.
By using this function, the load can be reduced compared to collecting at regular intervals.
In addition, saving completion can be reported. This supports communication with equipment that changes a value of amonitoring target resource. (For example, a value of a monitoring target resource can be changed when a process iscompleted and the process can be restarted when data saving is completed.)
This function runs as an edge application connected to Management Shell while the "One-Shot Collection Setting" screen is
open; therefore, one of the maximum number of edge applications that can be connected to Management Shell is consumed.
(Page 281 One-shot collection setting screen)
Edge application information for the one-shot collection function is displayed in the "OPC UA Diagnosis" screen as follows:(Page 341 OPC UA diagnosis)
Item

Description

Application Name

OneShotUtility

Connection source information*1*2

urn:[computer name]:EdgecrossConsortium:OneShotUtility

Number of monitoring target items

Number of one-shot collection settings for which "RUN" is displayed*1*2

If a computer name has 16 characters or more, the first 15 characters are displayed.
When setting either of the following types of computer names not recommended by Microsoft, Management Shell may not run properly.
- Computer name that has 16 characters or more
- Computer name that has characters other than alphanumeric ones or '-'7 Management Shell
7.8 One-shot Collection Function

269

7

Operational specifications
The following shows the operational specifications of the one-shot collection function.

Data collection function
A value of a collection target resource is collected by setting the rise (0  1) of a value of a monitoring target resource as a
trigger.*1*1

A monitoring target resource is monitored at one-second intervals, and data collection starts after the rise of the value of the monitoringtarget resource is detected; therefore, an actual collected value may differ from one at the time of rise.

The collected value is saved to a file or database. (Page 272 File saving function, Page 275 DB saving function)
After the value is saved, either of the following types of completion notification is sent to any data tag resource (notification
target resource) or the monitoring target resource.
The notification destination of completion can be set in the "Detailed Setting" screen. (Page 282 Detailed setting screen)Completion notification when a notification target resource is set as a notification destination
The value of the notification target resource changes to '1.'
It changes to '0' again after the fall (1  0) of the value of the monitoring target resource is detected. (The value of themonitoring target resource must be manually changed to '0.')
The following shows the flow of the behavior of the one-shot collection function when a notification target resource is set as
the notification destination. Before changing the value of the monitoring target resource to '1' again, make sure that the valueof the notification target resource is '0.'Data collection and saving

Falldetection

Savingcompletion

Notification target resource

Data collection and saving

Falldetection

Savingcompletion

10
Monitoring target resource
10Completion notification when a monitoring target resource is set as a notification destination
The value of the monitoring target resource changes to '0.'
The following shows the flow of the behavior of the one-shot collection function when a monitoring target resource is set as
the notification destination. Before changing the value of the monitoring target resource to '1' again, make sure that the valueis '0' and wait for two seconds or more. However, depending on the operating status of the system, data saving may not be
started and the value may not change to '0' because the rise of the value cannot be detected. In this case, wait longer orchange the notification destination from the monitoring target resource to a notification target resource.

Data collection and saving

Monitoring target resource

Savingcompletion10Collection target resource
Up to 1000 collection target resources can be registered.
However, data tag resources without read authority cannot be specified.

Monitoring target resource

270

7 Management Shell
7.8 One-shot Collection Function

Data collection and saving

Savingcompletion

One BOOL type data tag resource can be specified as a monitoring target resource.
However, the same data tag resource cannot be specified in multiple one-shot collection settings.
In addition, there are restrictions on data tag resources that can be specified depending on the notification destination ofcompletion as follows:• Monitoring target resource: Data tag resources without write authority cannot be specified.
• Notification target resource: Data tag resources without read authority cannot be specified.

Notification target resource
One BOOL type data tag resource with write authority can be specified as a notification target resource.
However, the same data tag resource cannot be specified in multiple one-shot collection settings.

Considerations
The following shows the considerations for the data collection function.
• When editing a data tag resource used for the one-shot collection function, an abnormal value may be acquired or an error
may occur. Make sure that the data tag resource is not used for the one-shot collection function before editing it.
• Even if a value of a monitoring target resource changes while being saved, the one-shot collection function does not detect
the value change.
• When a monitoring target resource is set as a notification destination, a value of the monitoring target resource isoverwritten to '0' after data saving is completed; therefore, writing a value to the monitoring target resource in the data tag
resource monitor or an edge application may cause a malfunction or an error. Write a value of the monitoring target
resource after data saving is completed. Completion of data saving can be checked when the value of the monitoring target
resource changes to '0.'

7

• The one-shot collection function must be used to write values to a notification target resource.
• Make sure that values of a monitoring and notification target resources are '0' before starting the operation.
• When using a data collector that does not support the data writing function, set a notification target resource as a
notification destination. Saving completion can be detected by setting an external data tag resource the value of whichchanges (0  1) as a monitoring target resource and any internal data tag resource that is not read-only as a notification
target resource.
• When changing the time and date of Windows, an error may occur during communication with Management Shell. Do notchange them while the one-shot collection function is running.
• When a minor error occurs during data collection or data saving, the completion notification is sent and the operation
continues. However, the collected data may not be saved in this case.

7 Management Shell
7.8 One-shot Collection Function271

File saving function
Data collected by using the data collection function can be saved to a file.

File output
Data to be output is temporarily saved as an accumulating file to the TMP folder*1 in a save destination folder.
*1

Created when the one-shot collection function starts running.

The size of an accumulating file increases over time; therefore, the file switches when a specified number of rows is reached.
File switching is to change the file name of an accumulating file to that of a saved file and move it to the save destination
folder. (A new accumulating file is created after file switching.)
Note that if the one-shot collection function stops running, an accumulating file switches to a saved file even if a specified
number of rows is not reached. (A new accumulating file is not created.)
However, if there is no output data in the accumulating file, the file is deleted without switching.
Up to a specified number of files are saved. If the specified number is exceeded, files are deleted in chronological order.
(1)

(2)

(3)

FileName_01

time
FileName_02

FileName_01

FileName_03

FileName_02

FileName_01

FileName_04

FileName_03

FileName_02

FileName_01(4)(1) Accumulating file(2) Saved file (a file with a smaller number is an older one)(3) File switching(4) File to be deleted

272

7 Management Shell
7.8 One-shot Collection FunctionFile deletion
Refer to the following:
Page 65 File deletion

File format
Refer to the following:
Page 65 File format

Data size
Refer to the following:
Page 66 Data size

File name, save destination
Refer to the following:
Page 67 FileConsiderations
The following shows the considerations for the file saving function.
• When setting a folder with restricted access as a save destination folder, make sure that a user account that starts
Management Shell Explorer is allowed to change, read, and write.
• Do not allow other applications to access accumulating or saved files; otherwise, creating or updating files may fail andcause an error.
• Make sure that the settings of a file name prefix and save destination folder do not overlap with those of the file saving
function of Real-time Flow Manager; otherwise, the one-shot collection function and Real-time Flow Manager may interferewith each other, and a malfunction or an error may occur. (Page 60 File saving function, Page 142 Data Storing Setting(File Saving))• When the file name suffix of a file being output reaches 'FFFFFFFF,' stop the one-shot collection function and take any of
the following corrective actions:- Move all files in the save destination folder to another folder, or delete files and restart the one-shot collection function.
- Set another path for the save destination folder.
- Change the file name prefix.
• Do not save a large number of files or folders to a save destination folder; otherwise, starting the operation may take time or
fail.
• If there is data that failed to be acquired in output data, an error is reported and the operation continues without saving datain the row.
• When specifying a folder with the compression attribute enabled for a save destination folder, the free space is determined
to be temporarily insufficient and a file saving error may occur if the free space on the disk is low.
• When enabling the encryption attribute of an output destination folder for a file in Windows, the file is output with theauthority of a user who starts Management Shell Explorer. This can protect information in the file from being accessed byother users who use the industrial PC.
However, an output destination folder must be a local folder.
The procedure for enabling the encryption attribute is same as that shown in the following:
Page 71 Using a folder with the encryption attribute enabled

7 Management Shell
7.8 One-shot Collection Function273

7• The procedure for browsing files output to an encrypted folder with a user other than one who starts Management Shell
Explorer is same as that shown in the following:
Page 72 Procedure for browsing files with a user account other than a specified one• If a saved file with the same file name prefix saved by a different user account already exists in a save destination folder
with the encryption attribute enabled, an error may occur due to the difference in authority to the file. Change the savedestination folder or file name prefix to another one.
• When specifying a folder for which a Windows search index is to be created as a save destination folder and running aprocess flow for a long time, the amount of index information (Windows.edb file) becomes large. As a result, the free disk
space on an industrial PC where Edgecross Basic Software is running may become insufficient. This can be avoided byeither of the following methods:- Specify a folder other than one for which a search index is to be created as a save destination folder.
- Exclude the folder specified as a save destination folder from the search index target by the following procedure: Select [Search]  [Searching Windows]  "Classic"  "Customize search locations here" in Windows settings.
 Click the [Modify] button in the "Indexing Options" screen.
 Unselect the checkbox of the folder specified as a save destination folder in "Change selected locations" in the "Indexed
Locations" screen, and click the [OK] button.

274

7 Management Shell
7.8 One-shot Collection Function

DB saving function
Data collected by using the data collection function can be saved to a database.
By setting each item to save data to a field of a table in a database in the one-shot collection setting, the data is saved(INSERT) according to the setting.
A database is connected when switching the operating status of the one-shot collection function to RUN, and disconnected
when switching it from RUN to STOP.
Note that only saving (INSERT) data to a database is available in the one-shot collection function.

• Up to 1000 units of data can be specified as a collection target.
• SQL statements and data types of a database used for the DB saving function are compliant with SQL99
specifications.

Precautions• If data is missing in one row for saving (INSERT) data to a database, an error will be reported and the data in the row will
not be saved (INSERT), and the operation continues.
• Data cannot be saved (INSERT) to a same table in multiple one-shot collection settings.
• Make sure that an access target table set in the one-shot collection setting does not overlap with one of another application.
• A database can only be used if it is installed on the industrial PC same as Edgecross Basic Software.

7

Table name and column name
The following table shows the specifications of a table name and column name.
Item

Description

Number of character bytes that canbe set*1

1 to 63*2

Available characters

Characters that can be used for the WSTRING type*3
Page 545 WSTRING type

*1

*2
*3

The number of available characters can be calculated based on the number of bytes in UTF-8.
Examples of typical characters and their numbers of bytes are as follows:- 0 to 9, A to Z, a to z, _ (U+005F): 1 byte
- Greek, etc.: 2 bytes- Hiragana, katakana, kanji (excluding some), etc.: 3 bytes
For 63 bytes or more, a setting name may be truncated and a table or column name may be duplicated.
The following characters in the range of U+0000 to U+007F can be used.
0 to 9, A to Z, a to z, _ (U+005F)

Precautions
Column names cannot be duplicated in the same table.

Database
Refer to the following:
Page 78 Database

Communication method
Refer to the following:
Page 78 Communication method

Processing for a problem
If an error is detected while performing the DB saving function, the error is output. If the error occurs in ODBC, the ODBC
error code is displayed in the "Error Details" screen. For details on the error codes, visit the following:
docs.microsoft.com/en-us/sql/odbc/reference/appendixes/appendix-a-odbc-error-codes

If there is no corresponding ODBC error code on Microsoft home page, visit the following:
www.postgresql.org/docs/10/static/errcodes-appendix.html

7 Management Shell
7.8 One-shot Collection Function

275Setting procedure
The following shows the procedure for configuring the setting for the one-shot collection function.
Whether the setting is correct can be checked by clicking the [Collection Saving Test] button.
To save data to a database, perform the procedure shown in the following section in advance.
Page 280 Pre-configuration for saving data to a database

1. Select [Tool]  [One-Shot Collection Setting].
The "One-Shot Collection Setting" screen appears. (Page 281 One-shot collection setting screen)

2. Click the cell in the "Detailed Setting" column.
The "Detailed Setting" screen appears. (Page 282 Detailed setting screen)

3. Select the [Collection Setting] tab to select a notification destination of completion.

276

7 Management Shell
7.8 One-shot Collection Function

4. Register a collection, monitoring, or notification target resource in the component tree or resource list window while the"Detailed Setting" screen opens.
• Registering a monitoring or notification target resource
Select and right-click a resource in the resource list window, and select any of the following items.
The selected resource is registered as a monitoring or notification target resource.
[Register to one-shot collection setting: Monitor]: To register a resource as a monitoring target resource.
[Register to one-shot collection setting: Notify]: To register a resource as a notification target resource.

7• Registering a collection target resource
Register a resource in the component tree or resource list window.
For registering a resource in the component window
Select and right-click a component, and select [Register to one-shot collection setting: Collect].
All data tag resources registered in the selected component are registered as collection target resources.

7 Management Shell
7.8 One-shot Collection Function

277

For registering a resource in the resource list window
Select and right-click a resource, and select [Register to one-shot collection setting: Collect].
The selected resource is registered as a collection target resource.

5. Select the [Saving Setting] tab.
6. Enter each item, and click the [Apply] button.
• When saving data to a file: Page 286 File saving setting• When saving data to a database: Page 287 DB saving setting

7. When saving data to a database, use an output DDL file to create a table in the database.
Page 537 Creating a table by using a DDL

8. To save data to the database, set a privilege for the table created in step 7.
Page 538 Setting a privilege to a table

9. When performing the test of the one-shot collection function, click the [Collection Saving Test] button.
A value of the collection target resource is collected and saved to a file or database. When saving it to a file, the file switches
for each row. When saving it to a database, the database is connected when performing the test and disconnected when thesaving is completed.
The test result is displayed in the "Error Details" screen. If an error occurs, check the error list and detailed information, andreview the setting. (Page 288 Error details screen)278

7 Management Shell
7.8 One-shot Collection Function

10. Click the [Start] button in the "Operation Change" column in the "One-Shot Collection Setting" screen.
When the one-shot collection function starts running normally, "RUN" is displayed in "Operating Status" and the cell isdisplayed in green.

Clicking the [Start All] button can switch the operating statuses to "RUN" for all set one-shot collection
settings.

11. If an icon appears in the "Error" column, check the error list and detailed information in the "Error Details" screen
displayed by clicking the [Error Details] button, and take corrective action. (Page 288 Error details screen)

12. To stop the operation of the one-shot collection function, click the [Stop] button in the "Operation Change" column.

7
Clicking the [Stop All] button can switch the operating status to "STOP" for a one-shot collection setting forwhich "RUN" is displayed.

Precautions
When performing the test
No notification of saving completion is sent regardless of the notification destination of completion.

When saving data to a database
When changing the setting of output data after outputting a DDL file, output the DDL file and create the table in the databaseagain. If the table is not created again, an error may occur when starting the operation or incorrect data may be stored in the
database.

7 Management Shell
7.8 One-shot Collection Function279

Pre-configuration for saving data to a database
The following procedure must be performed in advance when saving data to a database.

Operating procedure

1. Install a database.
Page 530 Installing PostgreSQL

2. Install the ODBC driver.
Page 535 Installing the ODBC driver for PostgreSQL

3. Configure the ODBC setting.
Page 536 ODBC setting

280

7 Management Shell
7.8 One-shot Collection Function

One-shot collection setting screen

(1)

Item
(1) Collection setting list*1

Description
Setting Name

A collection setting name set in the "Detailed Setting" screen is displayed. (Page 282 Detailed
setting screen)

Comment

A comment set in the "Detailed Setting" screen is displayed. (Page 282 Detailed setting
screen)Detailed Setting

Clicking a cell in this column displays the "Detailed Setting" screen. (Page 282 Detailed setting
screen)Operation Change*2

The operation for a one-shot collection setting can be switched.

Operating Status*3"RUN" or "STOP" is displayed for the operating status for the one-shot collection setting.
When "RUN" is displayed, the cell is displayed in green.

Error

If an error occurs, its type is displayed.
•: A minor error has occurred.
•: A moderate error has occurred.

[Error Details] button

Click this to display the "Error Details" screen. (Page 288 Error details screen)This screen appears even if there are no errors.

7[Start All] button*4

Click this to switch the operating statuses to RUN for all set one-shot collection settings.

[Stop All] button

Click this to switch the operating status to STOP for a one-shot collection setting for which "RUN"
is displayed.

[Close] button*5

Click this to close the screen.

[Delete Setting] button*6,*7

Click this to delete a selected setting from the list.
Only one setting can be deleted at a time.

*1
*2
*3
*4
*5
*6

*7

Up to 32 one-shot collection settings can be set.
Can be switched when a target one-shot collection setting is completed.
Remains RUN even if a moderate error occurs.
The operating status is not switched for a one-shot collection setting for which "RUN" is already displayed.
Can be clicked when "STOP" is displayed for the operating statuses for all one-shot collection settings.
Can be clicked when both of the following conditions are satisfied:
A target one-shot collection setting is completed.
"STOP" is displayed for the operating status for a target one-shot collection setting.
If an error occurs, the error is not cleared even if the setting is deleted.

7 Management Shell
7.8 One-shot Collection Function281

Detailed setting screen

Item

Description*1

Setting Name

Set the name of a one-shot collection setting (1 to 32 characters).
A name duplicated with another one-shot collection setting cannot be set.
• By default, it is displayed as follows:"CollectSettingNoXX" (XX is a setting number.)Comment*1

Set a comment (up to 100 characters).

[Collection Setting] tab

Set each item for the data collection function.
Page 283 Collection setting[Saving Setting] tab

Set each item for the file saving function or DB saving function.
Page 286 File saving setting
Page 287 DB saving setting[Collection Saving Test] button*1

Click this to perform the test of the one-shot collection function.
Note that the following items are not checked during the collection saving test.
• Duplicate setting name• Duplicate monitoring and notification target resources[Apply] button*1,*2

Click this to apply the setting. If there is any incorrect item, the row is displayed in yellow.

*1
*2

282

Can be changed or clicked when "STOP" is displayed for the operating status for a target one-shot collection setting.
The setting cannot be applied if WSTRING type data is included in the collection target resource when selecting "File" for "Saving
Method" and "CSV file (Shift_JIS)" for "File Format Setting."
Page 286 File saving setting

7 Management Shell
7.8 One-shot Collection FunctionCollection setting

(1)

Item

Description

View resource details

Select the checkbox to display the resource IDs of a collection, monitoring, and notification target
resource.

[Update to Latest State] button*1

Click this to update information on registered collection, monitoring, and notification target resources.
If an incorrect setting is included in a resource after an update, the cell is displayed in yellow.

Notification destination of completion*1,*2

Select either one for the notification destination of saving completion.
Details can be checked in the "Detailed Description" screen displayed by clicking the [Detailed
Description] button*1.
(A notification destination can also be selected in the "Detailed Description" screen.)Type

The type of a resource is displayed ("Monitor" or "Notify").

Target Resource

The resource display name of a data tag resource registered as a monitoring or notification target
resource is displayed.
When registering a new monitoring or notification target resource, the existing one is overwritten.
In addition, when registering a new monitoring or notification target resource while the cell is yellow, it
returns to white.

Path

The path to a data tag resource registered as a monitoring or notification target resource is displayed.

Resource ID*3

The resource ID of a data tag resource registered as a monitoring or notification target resource isdisplayed.

Data TypeThe data type of a data tag resource registered as a monitoring or notification target resource isdisplayed.

(1) Collection target
resource list*4[Delete Row] button*1

*1
*2
*3
*4

*5

Target Resource

The resource display name of a data tag resource registered as a collection target resource isdisplayed.

Path

The path to a data tag resource registered as a collection target resource is displayed.

Resource ID*3

The resource ID of a data tag resource registered as a collection target resource is displayed.

Data TypeThe data type of a data tag resource registered as a collection target resource is displayed.

Output Name*1

Set the output name when saving data (63 bytes or less).*5• For file saving: Set the column name.
• For DB saving: Set the column name.
By default, the resource display name of a registered data tag resource is displayed.
However, it is blank in the following cases:
The resource display name is duplicated.
An invalid character is included in the resource display name.
Click this to delete a selected collection target resource from the list.

Can be changed or clicked when "STOP" is displayed for the operating status for a target one-shot collection setting.
A value is retained until the screen is closed when "Notify Monitoring Target" is selected for "Notification destination of completion" andthe value is set as the notification target resource before changing to "Notify Monitoring Target."Appears when selecting the checkbox of "View resource details."
A collection target resource can be moved to a specified row in the "Move to the specified No." screen displayed by selecting and rightclicking the resource and selecting [Move to the specified No.]. This menu can be selected only when "STOP" is displayed for theoperating status for the target one-shot collection setting.
The number of available characters can be calculated based on the number of bytes in UTF-8.
Examples of typical characters and their numbers of bytes are as follows:
7 Management Shell
7.8 One-shot Collection Function283

7

- 0 to 9, A to Z, a to z, _ (U+005F): 1 byte
- Greek, etc.: 2 bytes- Hiragana, katakana, kanji (excluding some), etc.: 3 bytes

If "STOP" is displayed for the operating status and each item is already set for a target one-shot collection
setting, information on registered collection, monitoring, and notification target resources is updated to thelatest when opening the "Detailed Setting" screen. However, if an incorrect setting is included in any of theresources after the update, the cell is displayed in yellow.
• Detailed description screen
A notification destination selected in this screen is applied to the "Detailed Setting" screen.

Item

Description

Notify other than Monitoring Target

Select this to set a notification target resource as a notification destination of saving completion.

Notify Monitoring Target

Select this to set a monitoring target resource as a notification destination of saving completion.

• "Move to the specified No." screen

Item

Description

Specified No.

Specify the row of a destination.*1
When selecting multiple rows, they are moved based on the following:If a specified row is above the selected range of rows
The selected rows are moved so that the one with the smallest number is in the specified row.
If a specified row is in the selected range of rows
The row is not moved.
If a specified row is below the selected range of rows
The selected rows are moved so that the one with the largest number is in the specified row.

*1

284

If a collection target resource does not exist in a specified row, a selected collection target resource is moved to the bottom row.
(Example) If '4' is specified when the bottom collection target resource is in the third row, a selected collection target resource is moved
to the third row.

7 Management Shell
7.8 One-shot Collection Function

Ex.

The following shows examples when selecting No.3 and No.4 in the collection target resource list.
No.

Target resource

1

Resource_a2

Resource_b

3

Resource_c

4

Resource_d

5

Resource_e

6Resource_f

Specified No. is 1

Specified No. is 2

Specified No. is 3

No.

Target resource

No.

Target resource

No.

Target resource

1

Resource_c

1

Resource_a

1

Resource_a2

Resource_d2

Resource_c

2

Resource_b

3

Resource_a3

Resource_d

3

Resource_c

4

Resource_b

4

Resource_b

4

Resource_d

5

Resource_e

5Resource_e

5Resource_e

6Resource_f

6

Resource_f

6

Resource_f

Specified No. is 4

Specified No. is 5

Target resource

No.

Target resource

No.

Target resource

1

Resource_a

1

Resource_a

1

Resource_a2

Resource_b

2

Resource_b

2

Resource_b

3

Resource_c

3

Resource_e

3

Resource_e

4Resource_d

4

Resource_c

4

Resource_f

5

Resource_e

5Resource_d

5

Resource_c

6

Resource_f

6

Resource_f

6

Resource_d

No.

7Specified No. is 6

Specified No. is 7
No.

Target resource

1

Resource_a2

Resource_b

3

Resource_e

4Resource_f

5

Resource_c

6

Resource_d

7 Management Shell
7.8 One-shot Collection Function285

File saving setting

Item

Description

Saving Method*1

Select "File."

File Format Setting*1

Select the format of a file for saving data.

Save File Path Setting*1

Set the operation of switching file*1

Output Option*1

*1
*2

*3

286

Save Destination Folder

Set the save destination for a file (1 to 204 characters).
It can also be set in the "Save File Path Setting" screen displayed by clicking
the [...] button.

File Name Prefix

Set the prefix of a saved file name (1 to 32 characters).

The example of saving file path

The saving file path based on the settings for "Save Destination Folder" and"File Name Prefix" is displayed.

Switch when the next row number(Record number) was exceeded

Set the number of data rows stored in one file (1 to 9000).
If it is exceeded, a file will be output.

Upper bound number of saving files(Delete the old file when upper boundnumber of saving files was exceeded)

Set the maximum number of files stored in one folder (1 to 100).
If it is exceeded, files will be deleted in chronological order.

Output Name

Set a character string to output to the date and time column (63 bytes orless).*2

Specify Format

Select the checkbox to specify the format of date and time data.

Format

Set the output format of the date and time column (1 to 32 characters).
The following reserved words*3 can be specified.
YYYY: Year (4 digits)
YY : Year (2 digits)
MM : Month (2 digits)
DD : Day (2 digits)hh: Hour (2 digits)
mm : Minute (2 digits)
ss: Second (2 digits)
ms : Millisecond (3 digits)us: Microsecond (6 digits)ns: Nanosecond (9 digits).s to .sssssssss: Digits after the decimal point in seconds (1 to 9 digits)

Output Example

An output example of the date and time column according to the current
setting is displayed.

Can be changed or clicked when "STOP" is displayed for the operating status for a target one-shot collection setting.
The number of available characters can be calculated based on the number of bytes in UTF-8.
Examples of typical characters and their numbers of bytes are as follows:- 0 to 9, A to Z, a to z, _ (U+005F): 1 byte
- Greek, etc.: 2 bytes- Hiragana, katakana, kanji (excluding some), etc.: 3 bytes
Case-sensitive

7 Management Shell
7.8 One-shot Collection Function

DB saving setting

Item
Saving Method

Description*1

DB Connection Setting*1

Select "DB."
Data Source Name

Set the data source name of a database (1 to 32 characters).

User Name

Set the user name of a database (1 to 32 characters).

Password

Set the password for a database (6 to 32 characters).

Access Table Setting*1

Output Option*1[Output DDL File] button*1

*1
*2
*3

7

Set the table name*2 of a database to access (1 to 63 bytes).*3• By default, the setting name of a one-shot collection setting is displayed.
However, it is blank in the following cases:
An inhibited character is included.
The setting name overlaps with the table name of another access tablesetting.
Output Name

Set a character string to output to the date and time column (63 bytes orless).*3
Click this to output a DDL file with set contents.
Note that a DDL file must be output to the hard disk of an industrial PC, not to
a network drive or removal disk.

Can be changed or clicked when "STOP" is displayed for the operating status for a target one-shot collection setting.
Not case-sensitive
The number of available characters can be calculated based on the number of bytes in UTF-8.
Examples of typical characters and their numbers of bytes are as follows:- 0 to 9, A to Z, a to z, _ (U+005F): 1 byte
- Greek, etc.: 2 bytes- Hiragana, katakana, kanji (excluding some), etc.: 3 bytes

7 Management Shell
7.8 One-shot Collection Function287

Error details screen
Details on an error that occurred can be checked for each one-shot collection setting. Up to 16 errors are displayed.

(1)

(2)

Item

Description(1) Error information list

Time and Date of
Occurrence

The year, month, day, and time when an error occurs are displayed.

Importance Level

The severity of an error is displayed.
(Minor): Even if this type of error occurs, the one-shot collection function continues
running.
(Example) Errors that occur when a value of a collection target resource cannot be read(Moderate): If this type of error occurs, the operation of the one-shot collection function
is interrupted.
(Example) Errors in OPC UA connection or file saving

Error CodeThe code for an error that occurs when using the one-shot collection function is displayed.
(Page 429 Error Code List for the One-shot Collection Function)

Overview

The overview of an error that is occurring is displayed.

Detailed Information

Detailed information of an error is displayed.*2

Cause

An error cause is displayed.

[Clear Error] button*1(2) Error detailed information

Click this to delete minor errors displayed in the error information list in a batch.

Treatment[Update] button*1*1*2

A corrective action for an error is displayed.
Click this to update the error display.

Cannot be clicked if this screen is displayed by performing the test.
Depending on the error type, the total number of collection target resources in which an error has occurred is displayed. In addition, thenumber of a collection target resource in which an error has occurred is displayed. Note that if 11 or more errors occur, the 11th and laterones are not displayed.

When closing the "One-Shot Collection Setting" screen, errors are cleared.

Precautions
If a moderate error is included in the error information list, the displayed errors cannot be cleared.

288

7 Management Shell
7.8 One-shot Collection Function

7.9

Event History Automatic Output Function

This section shows the function to automatically output event/error information, which is collected from Management Shell,data collectors used in Management Shell, and IT gateways, to a specified folder in a CSV file format.
For the output setting, refer to the following:
Page 292 Event history automatic output setting screen
With an operation check file that is automatically output, it can be confirmed that this function is running normally.

Event history file
The following shows the detailed specifications of an event history file.

Output targets
Output target events are as follows:
Item

TargetEvent typeOperation, system, security

Status (severity)

Major, moderate, minor, warning, information

Problem function

Management Shell
Data collector
IT gateway

7

Event history file format
The format of an event history file to be output is as follows:File format
Item

Description

File format

CSV file

Character code

UTF-8 with BOM

File name"MgtShellLog.csv"
After a file is backed up, the date and time information at the time of switching is added to the end of the above file
name.
Date and time information format: MMddHHmmss
MM: Two-digit numerical value from 01 to 12
dd: Two-digit numerical value from 01 to 31
HH: Two-digit numerical value from 00 to 23
mm: Two-digit numerical value from 00 to 59
ss: Two-digit numerical value from 00 to 59
File name example
MgtShellLog1203174055.csv
For details on the backup operation, refer to the following:
Page 290 Backing up an event history file

Extension.csv

Information to be output

1st row: Header row
2nd and later rows: Data row
Up to 39999 data rows are output.
If it is exceeded, the first data row is deleted and the latest event is added to the end of the file.
For details on the header row and each column, refer to the following:
Page 87 Information output to an event history file

Information output to an event history file
Refer to the following:
Page 87 Information output to an event history file

Output location
Refer to the following:
Page 87 Output location

7 Management Shell
7.9 Event History Automatic Output Function

289

Operational specifications
The following shows the operational specifications for outputting an event history file.

File output authority
Refer to the following:
Page 88 File output authority

File output
An event history file is output at the following timings:• Management Shell is started.
• The event history automatic output setting is applied (excluding when changing 'enabled' to 'disabled' for output).
• An event occurs within the event history monitoring interval.
If a specified folder does not exist, a folder is created and an event history file is saved to the folder.
In addition, if a file with the same name exists, it is overwritten with the event history file.
If the event history file cannot be saved, the file saving is retried.
Events that occur during a retry are output together when they become available for saving.
If backup of an event history file fails, the file is not output until it succeeds. For details on backup of an event history file, referto the following:
Page 290 Backing up an event history fileBacking up an event history file
A backup file starts being created when deleting an event history in the "Event History" screen of Management Shell
Explorer.*1
If an error occurs during backup, an event is registered.
For the event codes, refer to the following:
Page 422 Codes for events that occur in Management Shell
Backed up files are not deleted from Edgecross Basic Software. (The maximum number of files that can be backed up isdetermined by the file system.)
The date of backup is added to the file name of a backed up file.
For details on the file name, refer to the following:
Page 289 File format*1

The next time an event history file is output, it is backed up before output regardless of whether the event history file output setting isenabled or disabled when deleting an event history.
When changing the save destination folder before backup, an event history file in the folder after the change is backed up.

An example of backup operation is as follows:
(a)
*1
(1)
MgtShellLog.csv
(b)

*2

*1
(1)
MgtShellLog.csv

MgtShellLog
1127083017.csv

(c)

*2

*1
(1)
MgtShellLog.csv

MgtShellLog
1127170043.csv

MgtShellLog
1127083017.csv(1) Management Shell(a) An event history is deleted in the "Event History" screen. (November 26th 12:45:22)(b) An event history is deleted in the "Event History" screen. (November 27th 08:30:17)(c) An event history is deleted in the "Event History" screen. (November 27th 17:00:43)

*1
*2

290

The file name of the latest file is always 'MgtShellLog.csv.'
A file is backed up when deleting an event history.

7 Management Shell
7.9 Event History Automatic Output Function

Operation check file
The following shows the detailed specifications of an operation check file.

Operation check file format
The format of an operation check file is as follows.
Note that an operation check file is not backed up, and one file is used continuously.
Item

Description

File format

Text

Character code

UTF-8 with BOM

File name"MgtShellLogKeepAlive.dat"

Extension.dat

Output location
An operation check file is saved to the same location as an event history file.
Page 87 Output location

Operational specifications
Refer to the following:
Page 90 Operational specifications

7

Considerations
Refer to the following:
Page 91 Considerations

7 Management Shell
7.9 Event History Automatic Output Function291

Event history automatic output setting screen
The following shows the screen for settings required to automatically output an event history.

Window
Select [Setting]  [Event History Automatic Output Setting].

Displayed items
Item

Description
Select the checkbox to automatically output an event history to a file.*1

Enable automatic output*2

Output Target Setting

Save Destination Folder
Setting

*1
*2
*3

292

Select the checkbox of an event to be output.
Save Destination Folder*2

Set a save destination folder (1 to 233 characters).
It can also be set in the "Select Folder" screen displayed by clicking the [...] button.

Saving File Path

The saving file path based on the setting for "Save Destination Folder" is displayed.

When the access authorityof the save destination
folder is limited, please
specify the user toaccess.*2

Select the checkbox if access is granted to the save destination folder for an event history file.*1[User Account Setting]button*3

Click this to display the "User Account Setting" screen.
Page 293 User account setting screen
The setting status of the "User Account Setting" screen is displayed to the right of this button.

When fixing the settings without selecting the checkbox, the settings in the "User Account Setting" screen are deleted.
Can be selected or set when selecting the checkbox of "Enable automatic output."
Can be clicked when selecting the checkboxes of "Enable automatic output" and "When the access authority of the save destination
folder is limited, please specify the user to access."

7 Management Shell
7.9 Event History Automatic Output Function

User account setting screen
The following shows the screen for setting a user name and password used for accessing a folder with restricted access.

Window

Displayed items
Item

Description

User Name*1,*2

Set a user name used for file output (up to 127 characters).
When specifying a domain, set it in either of the following formats:*3*4• [Domain name]\[User name]• [User name]@[Domain name]
When specifying a local user of an industrial PC on which Edgecross Basic Software is installed, set it in any of thefollowing formats:• [Computer name]\[User name]• .\[User name]• [User name]

Password*1,*2

Set a password used for accessing a folder (up to 127 characters).

[Authentication Test] button

Click this to perform the authentication test for a user account to Windows by using a set user name and password.

*1
*2

*3

*4

7

If changing a set password for a user account in Windows, set it again.
To prevent eavesdropping and falsification of data, it is recommended to use a user account with a password satisfying complexity
requirements.
The complexity requirements can be checked by the following procedure: Start the local security policy of Windows.
 Double-click [Security Settings]  [Account Policies]  [Password Policy]  [Password must meet complexity requirements].
 Select the [Explain] tab in the "Password must meet complexity requirements Properties" screen.
When '@' and '\' are included, the format is determined as [User name]@[Domain name].
When multiple pieces of '@' or '\' are included, the first '@' ('\' if there is no '@') is used as a delimiter between a domain name and a user
name.
Do not specify a local user of another industrial PC on the network.

Precautions• When exporting a setting file while a local user of an industrial PC is set for "User Name" and importing the setting file inanother industrial PC, the local user may not be authenticated in the import destination industrial PC. Set it again after
import as necessary.
• The authentication test is performed on a local computer. Therefore, even when specifying another industrial PC on the
network for a save destination folder, the test is not performed on the industrial PC.
• When repeating the following operations if a password is incorrect, a user account may be locked out. If an error occurs
due to these operations, check if a password is correct.
- Apply the setting.
- Start Management Shell.
- Perform the authentication test.

7 Management Shell
7.9 Event History Automatic Output Function

293

8

CSV File Data collector

CSV File Data collector is a software component that collects or reads data in devices via a monitoring target file (CSV file ortext file).

8.1

Data Collection Function

This section shows the function to collect data in a device via a monitoring target file.
The following shows the behavioral flow of the data collection function.

Ô

(1)
Ò
(2)

(2)

Ó

(3)

Õ

(1) Monitoring folder(2) Monitoring target file(3) CSV File Data collector

 A monitoring folder is monitored periodically.
 A monitoring target file is read when it is stored in the monitoring folder.
 Data is collected from the read monitoring target file and passed to the next process.
 The monitoring target file is deleted after the data is passed.

Operational specifications
The following shows the operational specifications of the data collection function.

Folder monitoring
Whether there is a monitoring target file stored in a specified monitoring folder is monitored periodically, and a file is imported
when it is detected that the file has been stored.
If multiple monitoring target files exist in a monitoring folder, they are imported in the following order: Update date/time (processed in order from the oldest file) File name (when the update date/time is the same)
The following table shows the specifications of a monitoring folder and monitoring target file.
Item name

Description

Monitoring folder*1,*2,*3

Set the full path to a folder to monitor.
• A path to a folder on the local disk or to a shared folder can be set.
• Up to 199 characters can be set for a path (including the drive letter and '\' at the end).
• Monitoring targets are immediately under a specified monitoring folder.
• A same monitoring folder cannot be specified for multiple CSV File Data collectors.
• When importing a large monitoring target file, a 'csv' folder for temporary work may be created in a monitoring folder.

Monitoring target file

The target is a file with the prefix exactly matching a file name prefix specified in Real-time Flow Designer.
• Up to 32 characters can be set for the prefix.
• Only ASCII characters can be used for characters (suffix) after the prefix.*4• The target is a file with the extension matching the type of a file (.csv or .txt) specified in Real-time Flow Designer.
• Up to 256 characters can be set for the path to a monitoring target file.

*1
*2

294

When using a remote shared folder, refer to the following:
Page 556 Using a shared folder without specifying a user account in Edgecross Basic Software
Do not specify a folder with the encryption attribute enabled.
Otherwise, the encryption cannot be disabled due to the difference in access rights and files in the folder are treated as ones that cannot
8 CSV File Data collector
8.1 Data Collection Function

*3

*4

be read or written.
For collection processing of files that cannot be read or written, refer to the following:
Page 306 File processing order when files that cannot be read or written are included
For details on a folder with the encryption attribute enabled, refer to the following:
Page 71 Using a folder with the encryption attribute enabled
If the existence of a folder cannot be confirmed after the following time elapses, an error will occur.
When starting an industrial PC: 240 seconds after the startup of the industrial PC
When 240 or more seconds elapses after the startup of an industrial PC: 10 seconds
Delimit the prefix and the suffix by '_.'

File collection example
An example of file collection when specifying the following items is shown below.
Monitoring folder: C:\Receive
File name prefix: LOG0001
Monitoring target file: LOG0001*.CSV

Receive

LOG0001_
00001.CSV(1)

LOG0002_00001.CSV

(2)

TMP

8
LOG0001_
00002.CSV(3)(1) A file is imported when it is detected that the file has been stored.
(2) A file is not imported even when it is stored due to the difference in file name prefixes.
(3) A file is not imported even if it is stored, because the file is stored in a folder other than one immediately under a monitoring folder.

Precautions
If the collection cycle must be reviewed, such as when the message is displayed for "Treatment" in the "Event History" screen,take the following actions:Page 335 Event history• Reduce the number of files stored at the same time.
• Reduce the frequency of storing monitoring target files in a monitoring folder.
• Reduce the number of rows in a monitoring target file.

Collection process overview
A monitoring target file is imported by using the definition information of collection data (file information, data nameinformation, and data type information) set in Real-time Flow Designer.
Read data other than the header information is passed to the next process.

8 CSV File Data collector
8.1 Data Collection Function

295

Monitoring target file after collection processing
The following shows a monitoring target file after collection processing.

Normal situation
A monitoring target file that is successfully collected will be deleted from a monitoring target folder.

Abnormal situation
If an error occurs while importing a file, an 'Error' folder is created in a monitoring folder and an imported monitoring target file
is moved to the folder.
The file in the Error folder is not deleted automatically.

296

8 CSV File Data collector
8.1 Data Collection Function

8.2

Data Reading Function

This section shows the function to read data in a device via a monitoring target file.
The following shows the behavioral flow of the data reading function.

(1)
Ò
(2)

(2)

ÓÔ

(3)

(4)
Õ

(1) Monitoring folder(2) Monitoring target file(3) CSV File Data collector(4) Management Shell

 A data reading request is received from Management Shell.
 A monitoring target file with the latest update date and time is searched for among the monitoring target files stored in amonitoring folder.
 Data is read from the last row of the searched monitoring target file.
 The read data is returned.

8

Operational specifications
The following shows the operational specifications of the data reading function.

Reading a monitoring target file
A monitoring target file with the latest update date and time is searched for among the monitoring target files stored in amonitoring folder.
If there are multiple monitoring target files with a same update date and time, their file names are sorted in the order of signs
defined in UTF-8 and the last sorted file is read.
The following table shows the specifications of a monitoring folder and monitoring target file.
Item name

Description

Monitoring folder*1,*2

Set the full path to a folder to monitor.
• A path to a folder on the local disk or to a shared folder can be set.
• Up to 199 characters can be set for a path (including the drive letter and '\' at the end).
• Monitoring targets are immediately under a specified monitoring folder.

Monitoring target file*3,*4

The target is a file with the prefix exactly matching a file name prefix specified in Management Shell Explorer.
• Up to 32 characters can be set for the prefix.
• Only ASCII characters can be used for characters (suffix) after the prefix.*5• The target is a file with the extension matching the type of a file (.csv or .txt) specified in Management Shell Explorer.
• Up to 256 characters can be set for the path to a monitoring target file.

*1
*2
*3

*4
*5

When using a remote shared folder, refer to the following:
Page 556 Using a shared folder without specifying a user account in Edgecross Basic Software
If a folder does not exist, an error will occur.
An error occurs in any of the following cases:
No file exists.
The size is 0 bytes.
A target file cannot be opened with SYSTEM account, because the encryption attribute is enabled for the monitoring folder.
The access right is not granted.
A file is used in another process (prohibited from being read and written).
A read-only file can be set.
Delimit the prefix and the suffix by '_.'

8 CSV File Data collector
8.2 Data Reading Function

297

Example of file reading
An example of file reading when specifying the following items is shown below.
Monitoring folder: C:\Receive
File name prefix: LOG0001
Monitoring target file: LOG0001*.CSV

Receive

LOG0001_
00001.CSV

LOG0001_
00002.CSV

LOG0001_
00003.CSV(1)

LOG0002_00001.CSV

(2)

TMP

LOG0001_
00002.CSV(3)(1) A file with the latest update date and time is read. (If there are multiple files with a same update date and time, their file names are sorted in the order of signs
defined in UTF-8 and the last sorted file is read.)(2) A file is not read even when it is stored due to the difference in file name prefixes.
(3) A file is not read even if it is stored, because the file is stored in a folder other than one immediately under a monitoring folder.

Data reading
Data in a column specified in Management Shell Explorer is read from the last row of a monitoring target file. If a row specified
for the data start row number and subsequent ones do not exist or the number of columns is insufficient, an error will occur.
In addition, read data is converted according to the corresponding data type. If data type conversion fails, such as when avalue out of the range of the data type is used, an error will occur.

Monitoring target file after data reading processing
The following shows a monitoring target file after data reading processing.

Normal situation
A monitoring target file that is successfully read will not be deleted from a monitoring target folder.

Abnormal situation
If an error occurs, a monitoring target file is not deleted or moved. (CSV File Data collector continues reading target files until
a new monitoring target file is stored in the monitoring folder.)298

8 CSV File Data collector
8.2 Data Reading Function

8.3

Detailed Specifications

Specifications of a monitoring target file
The following tables show the format specifications of a monitoring target file.

Use in Real-time Flow Manager
Item name

Description
CSV file

Text file

Extension

csv

txt

Delimiter

Comma (,)*4,*5

Tab (\t)*6,*7

Line feed code*1

CRLF (0x0D, 0x0A)
Enter a line feed code in the end of every row (excluding the end of a file).

Character code

Shift JIS or UTF-8 (with BOM)

Header information

Rows immediately before a data start row number specified in a collection data definition file are treated as header information.
The header information is optional and its content can be set arbitrarily.

Field data*2,*3• Double quotes (") cannot be used.
• Commas (,) can be used for the date and time column only.*4,*5

Column type

• Date and time column*8: Time stamp of collected data*9• Data column: Value of collected data*10,*11

Number of columns*12

Up to 257 columns• Date and time column*13: 1 column• Data column: 256 columns

UTF-8 (with BOM) or UTF-16LE (with BOM)

• Double quotes (") cannot be used.
• Tabs (\t) cannot be used.
• Commas (,) can be used for the date and time column only.

*1

CSV File Data collector also runs normally for the following line feed codes:
CR only
LF only
Blank + CRLF
Horizontal TAB + CRLF
*2 If the data type is one other than STRING and WSTRING, consecutive spaces at the start and end of data are not collected.
*3 If data does not match the 'format specification string representing ON' or 'format specification string representing OFF' set in thefollowing section when the data type is BOOL or BIT, the corresponding process flow will be stopped.
Page 304 Additional information character string*4 Use the same number of commas (,) in all the rows.
*5 No error occurs when using a comma (,) at the end of a row or if there is more data included in a monitoring target file than data definedin a collection data definition file; however, an error occurs if there is less data.
*6 Use the same number of tabs (\t) in all the rows.
*7 No error occurs when using a tab (\t) at the end of a row or if there is more data included in a monitoring target file than data defined in acollection data definition file; however, an error occurs if there is less data.
*8 It must be the first column of a monitoring target file.
*9 The time stamp in the date and time column of a monitoring target file is displayed in local time. When using data out of the range of
2000/1/1 0:00 to 2079/12/31 23:59 (UTC), the time stamp may not be displayed properly.
*10 For REAL or LREAL type data, a value smaller than the minimum value of an absolute value is rounded to '0.'
*11 For LREAL type data, a value greater than the maximum value or smaller than the minimum one is rounded to the maximum or
minimum value respectively.
*12 If it exceeds the number of columns set in Real-time Flow Designer, an error will occur and the corresponding process flow will stop.
*13 If a comma (,) is used, it is not counted.

8 CSV File Data collector
8.3 Detailed Specifications

299

8Use in Management Shell
Item name

Description
CSV file

Text file

Extension

csv

txt

Delimiter

Comma (,)

Tab (\t)Line feed code*1

CRLF (0x0D, 0x0A)
Enter a line feed code in the end of every row (excluding the end of a file).

Character code

Shift JIS or UTF-8 (with BOM)

Header information

Rows immediately before a data start row number specified in the "Target Device Setting" screen are treated as header information.
The header information is optional and its content can be set arbitrarily.

Field data

• Double quotes (") cannot be used.
• Commas (,) cannot be used.

Column type

• Date and time column*2: Time stamp of collected data
• Data column: Value of collected data

Number of columns

512 columns in maximum*1*2• Double quotes (") cannot be used.
• Tabs (\t) cannot be used.

CSV File Data collector also runs normally for the following line feed codes:
CR only
LF only
Data in a column other than a specified one in the last row is not read; therefore, the date and time column does not need to be the firstcolumn.
To read the date and time column, set STRING or WSTRING for the data type of a reading target, and specify the date and time column
for the column of the reading target.

Examples of monitoring target files to be collected
The following shows examples of monitoring target files to be collected.
• CSV file

• Text file (Tabs are represented as the control character (\t).)300

UTF-8 (with BOM) or UTF-16LE (with BOM)

8 CSV File Data collector
8.3 Detailed Specifications

Specifications of a collection data definition file
The following table shows the format specifications of a collection data definition file.
Item name

Description

Extension
Delimiter*2Line feed code

CSV file

Text file

csv*1

txt*1

Comma (,)*3,*4

Tab (\t)*5,*6

CRLF (0x0D, 0x0A)
Enter a line feed code in the end of every header row.

Character code

Shift JIS or UTF-8 (with BOM)

Header information

Page 302 Header information of a collection data definition file

Field data

• Double quotes (") cannot be used.
• Commas (,) can be used for the date and time column
only.*3,*4

Column typeNot specified

Number of columns*7

Up to 257 columns• Date and time column*8: 1 column• Data column: 256 columns

*1
*2

*3
*4
*5
*6
*7
*8

UTF-8 (with BOM) or UTF-16LE (with BOM)

• Double quotes (") cannot be used.
• Tabs (\t) cannot be used.
• Commas (,) can be used for the date and time column
only.

The extension of a file to be collected and that of a collection data definition file do not need to be the same.
(Example) Create a collection data definition file as a CSV file (*.csv), and collect a text file (*.txt).
CSV File Data collector also runs normally for the following line feed codes:
CR only
LF only
Use the same number of commas (,) in all the rows.
No error occurs when using a comma (,) at the end of a row or if there is more data included in a monitoring target file than data definedin a collection data definition file; however, an error occurs if there is less data.
Use the same number of tabs (\t) in all the rows.
No error occurs when using a tab (\t) at the end of a row or if there is more data included in a monitoring target file than data defined in acollection data definition file; however, an error occurs if there is less data.
If it exceeds the number of columns set in Real-time Flow Designer, an error will occur and the corresponding process flow will stop.
If a comma (,) is used, it is not counted.

Examples of collection data definition files
The following shows examples of collection data definition files.
• CSV file

• Text file (Tabs are represented as the control character (\t).)

8 CSV File Data collector
8.3 Detailed Specifications

301

8

Header information of a collection data definition file
The following shows the configuration of the header information of a collection data definition file.
Row No.

Item

Description

1

File information row

The following information is included as entire file information• File type
• File version• Row position information

Any number

Data type information row

Data type information of data in each column.
The data type information row consists of 'data type character string + additional information
character string.'

Any number

Data name information row

Data name information of data in each column. Use it as a data name in each column of Real-time
Flow Designer.

File information row
Column No.

Item

Description

1

File type

Any character string. (It can be blank, but cannot be omitted.)2

File version

Any character string of a monitoring target file output source. (It can be blank, but cannot be
omitted.)

3

Data type information row number

The number of a row in which the data type information is described in a collection data definition
file.

4

Data name information row number

The number of a row in which the data name information is described in a collection data definition
file.

5

Data starting row number

The start position of a data row in a monitoring target file to be collected (up to 65535).

302

8 CSV File Data collector
8.3 Detailed Specifications

Data type information row
The data type information row consists of 'data type character string + additional information character string.'

Data type character string
The following table shows the data type character strings to be collected.
Data type character strings that are not listed in the following table are not collected.
Column name

Data type character
string*1

Display in Real-time Flow Designer

Description

Date and timecolumnDATETIMEThe date and time column.
It is used as a time stamp of collected data.*2Data column

BOOL

BOOL

The data column for 'Bit'

INT

The data column for 'Signed 16-bit integer'

UINT

The data column for 'Unsigned 16-bit integer'

DINT

The data column for 'Signed 32-bit integer'

UDINT

The data column for 'Unsigned 32-bit integer'

BIT
INT
SHORT
UINT
USHORT
DINT
LONG
UDINT
ULONG
LINT

LINT

The data column for 'Signed 64-bit integer'

ULINT

ULINT

The data column for 'Unsigned 64-bit integer'

REAL

REAL

The data column for '32-bit real number'

LREAL

The data column for '64-bit real number'

STRINGSTRINGThe data column for 'Character string (ASCII)'

WSTRINGWSTRING

The data column for 'Character string (UNICODE)'

FLOAT
LREAL

8

DOUBLE*1*2

For details on available data, refer to the following:
Page 544 Data type and value range
Use data which results in 2000/1/1 0:00 to 2079/12/31 23:59(UTC) taking the set time zone into consideration. If data outside the range
is used, time stamps may not be collected correctly.

• If an unnecessary data column is included in a collection data definition file, it can be excluded from thecollection target by changing the data type character string to either of the following:
CSV file: ,,(blank)
Text file: \t\t(blank)• If a data column, for which a data type character string that is not a collection target is specified, is included,delete the data column or exclude the data type character string from the collection target.

8 CSV File Data collector
8.3 Detailed Specifications

303

Additional information character string
Column name

Description

Details

ExampleDate and time column

Indicates the date and time column
format.

[Combination of the following character
strings*1,*2,*3]
YYYY: Year (4 digits)
YY : Year (2 digits)
MM : Month (2 digits)
DD : Day (2 digits)hh: Hour (2 digits)
mm : Minute (2 digits)
ss: Second (2 digits)
ms : Millisecond (3 digits)us: Microsecond (6 digits)ns: Nanosecond (9 digits).s to .sssssssss: Digits after the decimal
point in seconds (1 to 9 digits)

DATETIME[YYYY/MM/DD
hh:mm:ss.sss]

Data column

BOOL
BIT

Indicates the identification characters for
ON and OFF.

[{Format specification string
representing ON};{Format specification
string representing OFF}]*4
Format specification string: Anycharacters (1 to 16 characters)*5,*6

BOOL[1;0]
BOOL[ON;OFF]
BIT[1;0]BIT[ON;OFF]UINTUSHORT
UDINT
ULONG
ULINT

Indicates the identification characters forthe display format.

[{Format specification string}.{Number ofdigits}]• Decimal format
Format specification string: DEC
Number of digits: 0• Hexadecimal format
Format specification string: HEX
Periods (.) and the number of digits are
not specified.

UINT[DEC.0]
UINT[HEX]USHORT[DEC.0]
USHORT[HEX]*7
UDINT[DEC.0]
UDINT[HEX]ULONG[DEC.0]
ULONG[HEX]*7
ULINT[DEC.0]
ULINT[HEX]

INT
SHORT
DINT
LONG
LINT

[{Format specification string}.{Number ofdigits}]• Decimal format
Format specification string: DEC
Number of digits: 0

INT[DEC.0]
SHORT[DEC.0]
DINT[DEC.0]
LONG[DEC.0]
LINT[DEC.0]

REAL[{Format specification string}.{Number ofdigits}]• Decimal format
Format specification string: DEC
Number of digits: 0 to 8
• Exponential format
Format specification string: EXP
Number of digits: 0 to 8

REAL[DEC.5]
REAL[EXP.6]

FLOAT[{Format specification string}.{Number ofdigits}]• Decimal format
Format specification string: DEC
Number of digits: 0 to 16*8
• Exponential format
Format specification string: EXP
Number of digits: 0 to 16*8

FLOAT[DEC.7]
FLOAT[EXP.8]

LREAL
DOUBLE[{Format specification string}.{Number ofdigits}]• Decimal format
Format specification string: DEC
Number of digits: 0 to 16• Exponential format
Format specification string: EXP
Number of digits: 0 to 16

LREAL[DEC.10]
LREAL[EXP.11]
DOUBLE[DEC.12]
DOUBLE[EXP.13]

Number of characters: 1 to 32

STRING[32]Number of characters: 1 to 16

WSTRING[16]STRING

Indicates the number of characters.

WSTRING

*1
*2

304

Up to 32 characters can be specified.
'Year,' 'Month,' and 'Day' are required.
'Hour' is required when specifying 'Minute.''Hour' and 'Minute' are required when specifying 'Second.''Hour,' 'Minute,' and 'Second' are required when specifying 'Millisecond,' 'Microsecond,' and 'Nanosecond.'
8 CSV File Data collector
8.3 Detailed Specifications

*3
*4
*5

*6
*7
*8

Overlapped character strings cannot be used.
(Example) 'YYYY' and 'YY,' '.s' and '.ms,' etc.
A same character string cannot be used for character strings representing ON and OFF.
Available characters are as follows (excluding semicolons (;)):
Character code for a collection data definition file is Shift JIS: Available Shift JIS characters (excluding 0x00 to 0x1F, and 0x7F)
Character code for a collection data definition file is UTF-8 (with BOM) or UTF-16LE (with BOM): Page 545 WSTRING typeSpaces cannot be used for the start and end character string.
If the data type character string is USHORT or ULONG, it can be used even when the additional information character string is [HEX.0].
Digits in the decimal part that are not included in the ranges described for the data type 'REAL' are not read.

Data name information row
Set 'date and time column' and 'data name column' from the left in the data name information row.
Column name

Description

Details

Date and time column

Arbitrary

Same as the data name in each data column.

Data column

Data name in each data column• A data name must be unique.
• For the character string length of a data name, 1 to 32 characters can beset.
• Available characters are as follows:
Character code for a collection data definition file is Shift JIS: Available Shift
JIS characters (excluding 0x00 to 0x1F, and 0x7F)
Character code for a collection data definition file is UTF-8 (with BOM) or
UTF-16LE (with BOM): Page 545 WSTRING type

8

8 CSV File Data collector
8.3 Detailed Specifications

305

8.4

Considerations

This section shows the considerations when using CSV File Data collector.

Use in Real-time Flow Manager
Setting monitoring folders, file name prefixes, and file types
When using CSV File Data collector also in Management Shell, avoid duplication of the following items set in Real-time Flow
Designer and Management Shell Explorer.
• Monitoring folder• File name prefix• File type

File processing order when files that cannot be read or written are included
If a monitoring target file cannot be read or written*1, import is suspended, including files with a newer update date and timethan the target file. When reading and writing the file are available, the import resumes.
*1

In any of the following cases:
A file is opened in another Windows process.
A file is read-only.
The file size is 0 bytes.
The encryption attribute is enabled.

Avoid a situation in which a file cannot be read or written for a long time; otherwise, monitoring target files continue being
accumulated and the disk space may be too much occupied.

Judgment on file transfer completion
The completion of file transfer is determined by checking whether a monitoring target file is used in another Windows process.
When transfer of a monitoring target file is detected, whether the file is used in another Windows process is checked. If the fileis not used, it will be imported.
If the file is being used by another Windows process, this function checks if it is still in use at an interval of one second.

A monitoring folder cannot be confirmed
If a specified monitoring folder cannot be confirmed due to folder deletion, folder name change, or network disconnection, amonitoring target file cannot be imported and a continuation error will occur.
In this case, whether the monitoring folder exists is checked every 30 seconds, and if it exists, it is monitored again.

Time stamp displayed in the date and time column
A local time is used for the time stamp displayed in the date and time column of a monitoring target file.

A process flow stops
If a process flow stops while a monitoring target file is being imported, the importing will be discontinued but the monitoringtarget file will remain in the monitoring folder to avoid data missing. Therefore, collected data may overlap when the process
flow restarts.

The time stamp in the date and time column is displayed in daylight saving time
When the time stamp displayed in the date and time column is adjusted for daylight saving time, it will be different from that of
the collected data.

Processing time for data collection
When the size of a monitoring target file is large or the load on Windows is high, collection processing may take time.
For the processing time for data collection using CSV File Data collector, refer to the following:
Page 586 Data collection using CSV File Data collector

306

8 CSV File Data collector
8.4 Considerations

Switching the operating status of a process flow during data collection
When switching the operating status of a process flow to STOP then RUN again while a monitoring target file is being
collected, data is collected in order from the first row of the monitoring target file.

Adding constants and fixed character strings
Constants and fixed character strings cannot be added.

8

8 CSV File Data collector
8.4 Considerations

307

Use in Management Shell
Setting monitoring folders, file name prefixes, and file types
When using CSV File Data collector also in Real-time Flow Manager, avoid duplication of the following items set in Real-time
Flow Designer and Management Shell Explorer.
• Monitoring folder• File name prefix• File type

Monitoring folder
If a monitoring folder does not exist or it cannot be accessed due to network failure, an error will occur.

Time stamp displayed in the date and time column
A time when data is read is treated as a time stamp, not the date and time column of a monitoring target file.

Management Shell stops
If Management Shell stops, CSV File Data collector also stops running. In this case, all data and resources retained in the
CSV File Data collector are discarded or released.

Restarting CSV File Data collector during file reading
When restarting CSV File Data collector while a monitoring target file is being read, the CSV File Data collector stops running.
In this case, no response is returned to Management Shell and data reading fails.
When reading data after restarting CSV File Data collector, the latest file in a monitoring folder is read.

Processing when there is a lot of data to be read
CSV File Data collector responds sequentially to data reading requests from Management Shell; therefore, if there is a lot ofdata to be read at the same time or the load on Windows is high, the processing may take time.
For the processing time for data reading using CSV File Data collector, refer to the following:
Page 594 Data reading using CSV File Data collector

REAL type and LREAL type data
REAL type and LREAL type data (char) are converted into a real number (float, double) at the time of reading. However, string
type data is converted into an approximate value, this may cause a difference in values between the data and the reading
result.
Values out of the range of the following significant digits are not guaranteed.
REAL type: Approximately 7 digits in decimal (24 digits in binary)
LREAL type: Approximately 15 digits in decimal (53 digits in binary)308

8 CSV File Data collector
8.4 Considerations

8.5

Procedures before Using CSV File Data collector

Use in Real-time Flow Manager
When using CSV File Data collector in Real-time Flow Manager, collection target data is identified by the CSV File Data
collector based on the definition information (file information, data name information, and data type information) of the data.
Therefore, the definition information of collection data must be acquired in Real-time Flow Designer.
To acquire it, create a 'collection data definition file' in which the information of collection data is defined in advance.

1. Configure an access target device setting in which CSV File Data collector is used.
Page 124 Access Target Device Setting

2. Specify a monitoring folder.
3. Specify the prefix of a file name to monitor.
4. Specify the type of a file to monitor.
5. Acquire the definition information of collection data.
For the method for acquiring a monitoring folder, the prefix of a file name, file type, and the definition information of collection
data, refer to the following:
Page 310 Data Collection Setting (CSV File Data collector)

6. Change the operating status of a process flow to the RUN state.
For changing the operating status of a process flow, refer to the following:
Page 332 Real-time Flow Manager diagnosis

Use in Management Shell

8

1. Configure an access target device setting in which CSV File Data collector is used.
Page 311 Access Target Device Setting (CSV File Data collector)

2. Add an external data tag resource in Management Shell Explorer.
Page 236 Adding a data tag resource
Select the access target device setting configured in step 1 for "Target Device."
Set the column number and integer format of a reading target for "Location."
Page 312 Location Setting (CSV File Data collector)

3. Register the external data tag resource in the data tag resource monitor window.
Page 208 Registering a data tag resource

8 CSV File Data collector
8.5 Procedures before Using CSV File Data collector

309

8.6

Data Collection Setting (CSV File Data collector)

This section shows the screen for setting for collecting data output in the CSV file format or text file format.

Window
Click the cell in the "Detailed Setting" column for which "Data Collection" is displayed in the "Process Type" column in the"Data Logging Flow Setting" or "Data Diagnosis Flow Setting" screen of Real-time Flow Designer.

Displayed items
Item

Description

Reference

Monitoring folder

Set the path to a monitoring folder (up to 198 characters).
It can also be set in the "Select Folder" screen displayed by clicking the [...]
button.



File name prefix

Set the file name prefix of a monitoring target file (1 to 32 characters).

[Header information acquisition]
buttonClick this to acquire the header information of a collection data definition file*1.
Select a collection data definition file in the "Header information file selection"screen displayed by clicking the [Header information acquisition] button.

File type

Select a file type.



Data Name

The column data name of a monitoring target file is displayed.
However, if a column data name contains inhibited characters, it is displayed
as follows:
Output001, Output002, Output003...



Data TypeThe data type of data is displayed.

*1

For collection data definition files, refer to the following:
Page 301 Specifications of a collection data definition file

When acquiring the header information, the character code is determined depending on whether the collection
data definition file has BOM or not.
• With BOM: Determined as UTF-8 (with BOM).
• Without BOM: Determined as Shift JIS.

310

8 CSV File Data collector
8.6 Data Collection Setting (CSV File Data collector)

8.7

Access Target Device Setting (CSV File Data
collector)

This section shows the screen for setting a monitoring folder, file name prefix, file type, and data starting row number.

Window"Target Device Setting" screen of Management Shell Explorer

Displayed items
Item

Description

Reference

Monitoring Folder

Set the path to a monitoring folder (up to 198 characters).
It can also be set in the "Select Folder" screen displayed by clicking the [...]
button.



File Name Prefix

Set the file name prefix of a monitoring target file (1 to 32 characters).

File type

Select a file type.



Data starting row number

Specify the start position of a data row in a monitoring target file.

8

8 CSV File Data collector
8.7 Access Target Device Setting (CSV File Data collector)

311

8.8

Location Setting (CSV File Data collector)

This section shows the methods for setting a column number and integer format to be read.

Setting in the location setting screen
The following shows the screen for setting reading target column numbers and integer formats in the "Location Setting"screen.

Window
Click the [Setting] button in the "Add External Data Tag Resource" or "Edit External Data Tag Resource" screen ofManagement Shell Explorer.

Displayed items
Item

Description

Reference

Monitoring Folder

The path to a monitoring folder set in the access target device setting isdisplayed.

File Name Prefix

The prefix of a monitoring target file name set in the access target device
setting is displayed.

File type

The type of a file set in the access target device setting is displayed.

File column number

Set the column number of reading target data.

Integer Format*1

Set the integer format of data to be read.



*1

312

Not apply to BOOL, REAL, LREAL, STRING, or WSTRING type data.

8 CSV File Data collector
8.8 Location Setting (CSV File Data collector)

Entering directly
A column number and integer format to be read can be entered directly for "Location" in the "Add External Data Tag
Resource" or "Edit External Data Tag Resource" screen of Management Shell Explorer.

Input format for a location
Enter a location in the following format:• Column number|Integer format
Item

Description

Column number

Set the column number of reading target data (1 to 512).

Integer format*1

Set the integer format of data to be read.
• Decimal: dec• Hexadecimal: hex*1

Not apply to BOOL, REAL, LREAL, STRING, or WSTRING type data.

Ex.

A setting example when entering the following items is shown below.
• Column number: 2• Integer format: dec

8

8 CSV File Data collector
8.8 Location Setting (CSV File Data collector)

313

9

Management Shell Data collector

Management Shell Data collector is a software component that collects data in data tag resources in Management Shell byconnecting as an OPC UA client to Management Shell that runs as an OPC UA server.
It is used to handle data tag resources set in Management Shell as collection data in Real-time Flow Manager.

Collection target
Industrial PC

Real-time Flow Manager

Data tag resource
Data tag resource
Collect

Management Shell Data collector
Data model
Component
Data tag resource
Management Shell

Component
Data tag resource
Component

In addition, it runs as an OPC UA client connected to Management Shell; therefore, one of the maximum number of OPC UA
clients that can be connected to Management Shell is consumed during connection. (One is consumed per instance.) It is also
consumed at the following timings:- The access target device setting screen opens.
- Connection information is created in the access target device setting screen (the [Creation] button is clicked).
- The location setting screen is displayed.
Management Shell Data collector is displayed in the "OPC UA Diagnosis" screen as follows: (Page 341 OPC UA
diagnosis)
Item

Description

Application Name

"Management Shell Data Collector"

Connection source information*1*2"urn:{0}:EdgecrossConsortium:Management Shell Data Collector"{0}: Computer name*1
*2

If a computer name has 16 characters or more, the first 15 characters are displayed.
When setting either of the following types of computer names not recommended by Microsoft, Management Shell may not run properly.
- Computer name that has 16 characters or more
- Computer name that has characters other than alphanumeric ones or '-'Precautions• Management Shell Data collector can only be connected to Management Shell installed on the same industrial PC.
• Management Shell Data collector cannot be used in Management Shell.
• Information on all connected Management Shell Data collectors is displayed in the "OPC UA Diagnosis" screen.
• When changing the OPC UA setting of Management Shell, the access target device setting must be configured again.
• When saving a setting of Real-time Flow Designer to a file and reading it in another industrial PC, the access target device
setting must be reconfigured (to save the setting as an external file).

314

9 Management Shell Data collector

Restrictions on the file saving and file reading functions of Real-time Flow Designer

9

The following table shows whether restrictions apply or not when using a setting that includes Management Shell Data
collector for the file saving/file reading functions of Real-time Flow Designer.
: Without restrictions, : With restrictions
Edgecross Basic Software
versionImporting a file in the same industrial PC as theone which exported the file

Importing a file in a different industrial PC
from the one which exported the file

1.24



*1

*1

An error occurs in starting Management Shell since a target device setting where Management Shell Data collector is set is notavailable. In this case, set the target device setting again in the "Target Device Setting" screen, and the error will be removed.

9 Management Shell Data collector

315

9.1

Operational Specifications

This section shows the operational specifications of Management Shell Data collector.

Operating status
The status of Management Shell Data collector varies for each access target and is determined according to thecommunication status with the targets.
The communication status with access targets can be checked in Edgecross Basic Software.
Status of Management Shell Data collector

Description

Communication status
with an access target

Data is being read from an access target.

Data Collector and the access target are connected normally.
(It will be in this state when the connection processing
succeeds.)

Connected

Data is not being read from an access target. (Reconnection
is in progress.)

Data collector and the access target are disconnected. (It will
be in this state when the connection processing fails.)

Disconnected

Behavior when an error occurs
When Management Shell Data collector detects an error, the following operations are performed according to the error type.
Error type

Status of Management Shell Data collector

Behavior of Management Shell Data collector

Data collector operation stop error• Operations according to the specifications cannot be
guaranteed due to a hard disk error in an industrial PCof the installation destination or a failure of resource
securing.
• An error cannot be corrected even by changing the
network configuration due to an incorrect parametersetting (device type out of range, for example).

• Discards collected data when this error occurs during
data collection.
• Stops fixed cycle data collection and data reading onrequest and reports this error to Edgecross Basic
Software.

Data collector operation continuation
error• Operations such as a program execution or data
communication cannot be continued due to temporary
network failure.
• An error may be corrected by changing the network
configuration even though there is no communication
due to a mismatch between the parameter settings andthe network configuration.

• Discards collected data when this error occurs during
data collection.
• Continues fixed cycle data collection and data readingon request even after reporting this error to EdgecrossBasic Software.

The error types reported to Edgecross Basic Software are as follows:• Data collector operation stop error: Moderate error• Data collector operation continuation error: Minor error

316

9 Management Shell Data collector
9.1 Operational Specifications

9.2

Data Collection Function

9This section shows the function to collect data in Management Shell in a fixed cycle set in Real-time Flow Designer.
The first data collection starts when a set cycle time elapses after the operating status of Edgecross Basic Software switches
to the RUN state. After that, data is collected for each specified cycle.
If the first data collection fails and an error occurs, data reading is repeated until the data collection succeeds if the error is aminor one.

Collection processing time notification
When an enabled data collection setting is included and the operating status of Edgecross Basic Software switches from RUN
to STOP, the software is notified of the collection processing times (maximum and minimum)*1 in the RUN state as events.
However, when no data is collected while Edgecross Basic Software is in the RUN state, the maximum and minimum
collection processing times are reported as '0.'
*1

The range of collection processing time is 0 to 4294967295 microseconds, and an event is notified in milliseconds (three decimal
places).

Error notification in processing
If collected data fails to be read from Management Shell, Edgecross Basic Software is notified of an error according to thecause.*1*1

The following errors are not reported again after cleared. Take corrective action for the errors, then clear them.
To check if an error occurs after taking corrective action, switch Real-time Flow Manager to RUN again.
Collection error (Management Shell connection failure) (error code: 2012H)
Collection error (access to a non-existent tag) (error code: 2013H)
Collection error (error detected in Management Shell) (error code: 2016H)

If the data type set in the location setting does not correspond to the one set in Management Shell, Edgecross Basic Software
is notified of a collection error (data type mismatch) (error code: 2015H). Set a corresponding data type according to thefollowing table:
Data type in Management Shell

Data type in the location setting

BOOL

BOOL

INT

INT

DINT

DINT

LINT

LINT

UINT

UINT

UDINT

UDINT

ULINT

ULINT

REAL

REAL

LREAL

LREAL

STRINGWSTRING(STRING type data tag resources are used as WSTRING type ones inManagement Shell Data collector. (The STRING type is not supported andcannot be used.))WSTRINGWSTRING

9 Management Shell Data collector
9.2 Data Collection Function317Precautions• An OPC UA server itself collects data periodically. Therefore, some data collected by Management Shell may not be
acquired as a collection result of Management Shell Data collector if the collection cycle of Management Shell Data
collector is longer than that of Management Shell. To acquire all the data, it is recommended to set the collection cycle ofManagement Shell Data collector shorter than that of Management Shell.
In addition, the collection cycle of Management Shell depends on its performance.

13ms

13ms

20ms

13ms

13ms

20ms

13ms

20ms

13ms

13ms

20ms

: Data is being collected.
: Data is not collected.
: Collection cycle of Management Shell: Collection cycle of Management Shell Data collector• Management Shell Data collector checks the connection status with Management Shell for each collection cycle andattempts to reconnect if it is disconnected. If the reconnection fails, the status remains disconnected until the connection
status check at the next collection timing.
• Reading character strings including surrogate pairs is not supported.
• When the same location is set for some data in one flow, values of the collected data may not match.
Ex.

• To match a data value collected by Management Shell Data collector with the current value of an access target device, setboth the polling cycle of Management Shell and collection cycle of Management Shell Data collector shorter.
• Collection data consistency is not checked in Management Shell Data collector when setting parameters. Therefore, if asetting in the "Location Setting" screen is changed or deleted in Management Shell, an error occurs when this Data
collector starts running.
• If an error is reported from Management Shell, collected data will be missing.
• When the communication between Management Shell and an access target device is disconnected at a short interval,
Management Shell Data collector may not be notified of an error even if the error is detected in Management Shelldepending on the error detection timing.
• When collecting data, if there is a difference between the collection start time and the previous one by the allowablecollection processing delay time (250 milliseconds) or more, the collection cycle is exceeded. In this case, an exceeded
collection cycle event (event code: F800H) is reported and the collected data will be missing.
The time used for the processing references the current time in an industrial PC on which this product is running. Do notchange the current time when collecting data.

318

9 Management Shell Data collector
9.2 Data Collection Function

9.3

Setting Procedure9

1. Create a new process flow, and open the screen for setting a data collection process.

2. Select [Adding] for "Target Device" in the "Data Collection Setting" screen. (Page 139 Data Collection Setting)

3. Select Management Shell Data collector in the "Select Data collector" screen. (Page 125 Data collector selection
screen)4. Click the [Creation] button in the "Target Device Setting" screen. (Page 325 Access Target Device Setting(Management Shell Data collector))
Connection information to Management Shell is created.

5. Click the [OK] button.

9 Management Shell Data collector
9.3 Setting Procedure319

6. Select a data tag resource to be collected in the "Location Setting" screen, and click the [OK] button. (Page 326
Location Setting (Management Shell Data collector))

Changing the setting of a data tag resource to be collected
When changing the setting of a data tag resource to be collected in Management Shell Explorer after setting Management
Shell Data collector, and collecting data according to the new setting, change the collection data setting in Real-time Flow
Designer. The following shows the procedure for changing the data type of a data tag resource as an example.

1. Change the data type in Management Shell Explorer, and apply it to Management Shell.

2. Perform either of the following operations:- Reselect the data tag resource the data type of which is changed in the "Location Setting" screen of Real-time Flow
Designer. (Page 326 Location Setting (Management Shell Data collector))- Change the data type in the "Data Collection Setting" screen of Real-time Flow Designer. (Page 139 Data Collection
Setting)320

9 Management Shell Data collector
9.3 Setting ProcedureDeleting a data tag resource to be collected

9

When deleting a data tag resource to be collected in Management Shell Explorer after setting Management Shell Data
collector, perform the following procedure:

1. Delete a data tag resource in Management Shell Explorer, and apply it to Management Shell.

2. Select a target data tag resource in the "Data Collection Setting" screen of Real-time Flow Designer, and click the [Delete
Row] button. (Page 139 Data Collection Setting)

9 Management Shell Data collector
9.3 Setting Procedure321Changing the OPC UA setting (OPC UA server setting)
When changing the OPC UA setting (OPC UA server setting) in Management Shell Explorer after setting Management Shell
Data collector, perform the following procedure:

1. Change the setting in the "OPC UA Setting" screen of Management Shell Explorer, and click the [Apply] button.
(Page 261 Setting an OPC UA server)(Example) Changing the port number (endpoint URL)

2. In Real-time Flow Designer, create connection information to Management Shell again in all access target device
settings in which Management Shell Data collector is set.
• Click the [Creation] button in the "Target Device Setting" screen, and click the [OK] button. (Page 325 Access Target
Device Setting (Management Shell Data collector))

322

9 Management Shell Data collector
9.3 Setting Procedure3. Apply the setting to Real-time Flow Manager.

9

Moving the Edgecross Basic Software setting to another industrial PC
When moving the Edgecross Basic Software setting to another industrial PC after setting Management Shell Data collector,
perform the following procedure:

1. Save a setting file of Real-time Flow Designer or Management Shell Explorer.
Real-time Flow Designer: Select [File]  [Save in File].
Management Shell Explorer: Select [Management Shell]  [Export].

2. Move the setting file saved in step 1 to a destination industrial PC.
3. Read the moved file in the destination industrial PC.
Real-time Flow Designer: Select [File]  [Read from File].
Management Shell Explorer: Select [Management Shell]  [Import].

4. Perform steps 2 and later in the following:
Page 322 Changing the OPC UA setting (OPC UA server setting)

9 Management Shell Data collector
9.3 Setting Procedure

323

9.4

Data Collection Setting (Management Shell Data
collector)

This section shows the screen for setting on data collection in Management Shell Data collector.

Window[Collection Option] tab in the "Data Collection Setting" screen of Real-time Flow Designer

Displayed items
Item

Description

Collection Interval

Set an interval and the unit for collecting data.

324

9 Management Shell Data collector
9.4 Data Collection Setting (Management Shell Data collector)

9.5

Access Target Device Setting (Management Shell
Data collector)

9This section shows the screen for setting access target information to Management Shell to collect data.

Window"Target Device Setting" screen of Real-time Flow Designer(1)

Displayed items
Item

Description(1) Creation status of connection
information

The creation status of connection information is displayed.

[Creation] button

Click this to create connection information.

Precautions• Do not change the OPC UA setting for Management Shell while the "Target Device Setting" screen is displayed.
• When moving a setting file of Edgecross Basic Software, which includes an access target device setting in which
Management Shell Data collector is used, to another industrial PC, reconfigure the access target device setting.

9 Management Shell Data collector
9.5 Access Target Device Setting (Management Shell Data collector)

325

9.6

Location Setting (Management Shell Data
collector)

This section shows the screen for setting a location by selecting a hierarchy in the tree view and a data tag resource to becollected in the displayed list.

Window
Click the [...] button in the [Collection Data] tab in the "Data Collection Setting" screen of Real-time Flow Designer.

(1)

(2)

Displayed items
Item

Description(1) Tree view

The component tree of Management Shell is displayed.*1
Select a component including a data tag resource to register the location.
Note that multiple components cannot be selected.

(2) Data tag resource list

*1

Data Tag Resource Name

The resource display name of a data tag resource, which belongs to a component
selected in the tree view, is displayed.
Select a resource display name and click the [OK] button to register the location.
Note that multiple rows cannot be selected.

Data TypeThe data type of a data tag resource, which belongs to a component selected in thetree view, is displayed.

Access Direction

Whether a data tag resource, which belongs to a component selected in the tree view,
can be read/written is displayed as follows:• "Read, Write": Readable/writable• "Read": Readable• "Write": Writable

Each component is displayed with its component display name.

When clicking the [OK] button in this screen, a value is set in "Location (top)" in the "Data Collection Setting"screen according to a selected data tag resource as follows:"ns=2;s=Resources.{0}"{0}: Resource ID of a selected data tag resource

Precautions
When editing a component or resource in Management Shell while this screen is displayed, the display contents may not
match the settings in Management Shell. Do not edit any setting in Management Shell while this screen is displayed.

326

9 Management Shell Data collector
9.6 Location Setting (Management Shell Data collector)

10 Dummy Data collector
Dummy Data collector is a software component that does not communicate with external devices.
Use this for Management Shell when setting a temporary data collector to create a data model in advance if a data collector to
be used has not been determined.

10.1

10

Data Reading Function

The data reading function reads data according to a request from Edgecross Basic Software.
Note that data is not read from external devices but a fixed value is read for each data type as follows:
Data type

Fixed value

BOOL

0

INT
UINT
DINT
UDINT
LINT
ULINT
REAL
LREAL
STRING

Null character

WSTRING

10.2

Parameter Setting

In Dummy Data collector, a screen for setting parameters is not included.

10 Dummy Data collector
10.1 Data Reading Function

327

MEMO

328

10 Dummy Data collector
10.2 Parameter Setting

11 TROUBLESHOOTING
11.1

Checking Methods for Error Descriptions

The following are the methods for checking error descriptions.
Checking method

Details

Real-time Flow Designer

Error codes and error occurrence sources can be checked in the "Real-time
Flow Manager Diagnostics" screen.
Page 332 Real-time Flow Manager diagnosis

Management Shell Explorer

Error codes and error occurrence sources can be checked in the "Error
Information List" screen.
Page 343 Displaying error information in a list

11

• If multiple errors occur at the same time, take corrective action for the errors in chronological order.
• When an error occurs due to a location parameter setting in Management Shell Data collector, the location
causing the error can be confirmed in the detailed information for the error code*1.
*1

If the number of characters in the location is 67 or more, it will be displayed as follows. (A surrogate pair character is counted as two
characters.)(The first 30 characters)...(the last 36 characters)

11 TROUBLESHOOTING
11.1 Checking Methods for Error Descriptions

329

Error code system
The error code system differs for each error occurrence source.

Real-time Flow Manager
The following table shows the error code system when an error occurs in Real-time Flow Manager.
Error codes are represented in four-digit hexadecimal numbers (unsigned 16-bit integers).
Error code range

Error type

Description

1000H to 4FFFH



System area

5000H to 5FFFH

Minor error

A process flow does not stop even if this error occurs.
This error indicates the state in which an error occurs but a process flow continues running, or aprocess flow automatically recovers once the error cause is removed.

Moderate error

A process flow stops if this error occurs.
This error indicates the state in which a process flow cannot continue running due to this error but it
restarts running once the error cause is removed and the operating status of the process flow ischanged from STOP to RUN.

6000H to 6FFFH

Major error

This error indicates the state in which all process flows cannot continue running due to an error in theoperating status of a program or process and there is no recovery method other than restarting an
industrial PC that runs the program or process.

7000H to FFFFH



System area

Real-time Flow Manager determines whether a process flow can automatically recover when registering anerror. Depending on the result, the error type may be different even for the same error code.

Precautions
If a process flow stops due to an error, data not output to the outside by saving to a file or using the device instruction
feedback may be lost.

Timings for clearing errors
The following table shows the timings and operations for clearing errors for each error type.
TimingMinor error

Starting an industrial PC

Cleared.

Moderate error

Major error

Switching the operating status
Page 333 "Process Flow Start/
Stop" screenErrors occurred in a location other than a process flow
Cleared by switching the operating statuses of all process flows to STOP thenswitching any of them from STOP to RUN.
Errors occurred in a specific process flow
Cleared by switching the operating status of the process flow from STOP to
RUN.

Not cleared.

Applying the parameters of Real-time
Flow Manager
Page 109 Home screen

Cleared.

Not cleared.

Clearing errors
Page 334 Operation diagnosis

Cleared.

Not cleared.

Precautions
If a major error is included in errors occurred, none of these errors are cleared. Restart an industrial PC on which Real-time
Flow Manager is running.
To clear a major error, disable the fast startup function. If it is enabled, an industrial PC is not shut down completely, and the
major error may not be cleared when starting the industrial PC after shutdown. For the procedure for disabling the fast startup
function, refer to the following:
Page 114 Procedure for disabling the fast startup function

330

11 TROUBLESHOOTING
11.1 Checking Methods for Error Descriptions

Data collector
The error code system when an error occurs in a data collector is as follows:Management Shell Data collector
There are two types of errors for Management Shell Data collector: moderate error and minor error.

Other data collectors
Refer to the manual for a data collector used.

11

IT gateway
For the error code system when an error occurs in an IT gateway, refer to the manual for an IT gateway used.

11 TROUBLESHOOTING
11.1 Checking Methods for Error Descriptions

331

11.2

Checking the Status of a Process Flow

This section shows the method for checking the operating status of a process flow.

Real-time Flow Manager diagnosis
The operating status of a process flow can be switched and diagnosed.
In addition, errors and events occurred in a data collector or an IT gateway used in Real-time Flow Manager can be
diagnosed.

Window
Select [Diagnostics]  [Real-time Flow Manager Diagnostics].

Displayed items
Item

Description

Reference

Operating Status

The operating status of process flows is displayed.*1,*2,*3
Click the [Start/Stop] button to open the "Process Flow Start/Stop" screen, and switch theoperating status of each process flow.

Page 333 "Process Flow
Start/Stop" screen

Monitor Status

The monitoring status is displayed.*4
Click the [Start Monitoring]/[Stop Monitoring] button to start or stop monitoring.



Operation
Diagnosis

To display information on an error occurred in Real-time Flow Manager and a data collector oran IT gateway used in Real-time Flow Manager.

Page 334 Operation
diagnosis

Process
Flow
Diagnostics

To diagnose the execution status of a data logging flow and a data diagnosis flow, and the latest
error.

Page 337 Process flow
diagnostics

DeviceAccessDiagnostics

To diagnose the connection status between Real-time Flow Manager and an access target
device, and the latest error.

Page 338 Device accessdiagnosis

IT Gateway
Diagnostics

To diagnose the connection status between Real-time Flow Manager and a communication
destination of an IT gateway, and the latest error.

Page 339 IT gateway
diagnosis

StatusmemorymonitorTo monitor the Real-time Flow Manager status.
For the Real-time Flow Manager status, refer to the following:
Page 433 Real-time Flow Manager Status

Page 340 Status memory
monitor

Real-time
Flow
Manager
Diagnostics

*1
*2

*3

332

"-" is displayed when "Stopping" is displayed under "Monitor Status.""RUN" is displayed if there is at least one process flow for which "RUN" is displayed for the operating status in the "Process Flow Start/
Stop" screen. The number in the parentheses indicates the total number of process flows for which "RUN" is displayed for the operating
status.
"STOP" is displayed in either of the following cases:
There is no process flow for which "RUN" is displayed for the operating status.
There is no process flow.

11 TROUBLESHOOTING
11.2 Checking the Status of a Process Flow

*4

"Stopping" is displayed while the "Process Flow Start/Stop" screen is open.

"Process Flow Start/Stop" screen
The operating status of each process flow can be controlled.
 If a moderate or higher error occurs while a process flow is running, the operating status of the process flow
switches to STOP.
 Check the error occurrence status of Real-time Flow Manager in the following cases. (Page 334

11Operation diagnosis)• The operating status of a process flow switches to STOP even though a stop operation is not performed.
• The operating status of a process flow does not switch to RUN even though a start operation is performed(immediately returns to STOP).
 The time until the operating status switches to RUN increases in proportion to the number of process flows
to be switched at the same time. In addition, the timing of switching to RUN varies widely.
To avoid these symptoms, switch the operating statuses multiple times to reduce the number of target process
flows.

Window• Click the [Start/Stop] button in the "Real-time Flow Manager Diagnostics" screen.
• Select [Real-time Flow]  [Process Flow Start/Stop].

(1)

Displayed items
Item(1) Process flowlist

Description
TargetSelect the checkbox of a process flow to start or stop.

Process Flow No.

A process flow type and process flow number are displayed.

Process Flow Name

A process flow name is displayed.

StatusThe operating status of a process flow is displayed.

[Select All] button

Click this to select the checkboxes of all process flows in the list.

[Cancel All] button

Click this to unselect the checkboxes of all process flows in the list.

[Start] button

Click this to start the operation of a process flow with its checkbox selected in the "Target" column.

[Stop] button

Click this to stop the operation of a process flow with its checkbox selected in the "Target" column.

11 TROUBLESHOOTING
11.2 Checking the Status of a Process Flow333

Operation diagnosis
Information on an error occurred in Real-time Flow Manager and a data collector or an IT gateway used in Real-time Flow
Manager is acquired, and the history, detailed information, cause, and corrective action are displayed as diagnosis
information.
If a moderate error occurs, the process flow stops running.

Window
Select "Real-time Flow Manager Diagnostics"  "Operation Diagnosis" in the "Real-time Flow Manager Diagnostics" screen.

(1)

(2)

(3)

Displayed items
Item

Description(1) Number of errors(2) Error information list

The number of errors by severity is displayed.
Time and Date of
Occurrence

The year, month, day, and time when an error occurs are displayed.

Importance Level

The severity of an error is displayed.

Error CodeAn error code acquired from Real-time Flow Manager is displayed.
For an error occurred in a data collector or an IT gateway, an error code defined in the datacollector or IT gateway is displayed.
For details, refer to the manual for the data collector or IT gateway.

Overview

The overview of an error that is occurring is displayed.

Problem Function

An error occurrence source is displayed.

Detailed Information

Detailed information of an error is displayed.

Cause

An error cause is displayed.

[Clear Error] button

Click this to delete minor and moderate errors displayed in the error information list in a batch.

(3) Error detailed
information

Treatment

When the classification of an event is "Error," the corrective action for the event is displayed.

[File Saving] button

Click this to save the display contents to a CSV file.

[Event History] button

Click this to display the "Event History" screen.
Page 335 Event history• Error information is also stored in the Real-time Flow Manager status.
• Up to 64 errors are displayed.
• The history of an error occurred can also be checked in the event history.
• If monitoring is stopped, the contents when the monitoring is stopped will remain displayed.

Precautions• If a major error occurs, other errors cannot be deleted.
• Minor and moderate errors are deleted in a batch; therefore, unintended errors may also be deleted.
• Even if an error is deleted from the error information list, it is not deleted from the event history.
• Even if an error is deleted from the error information list, its cause is not removed; therefore, the same error may occur
again.

334

11 TROUBLESHOOTING
11.2 Checking the Status of a Process Flow

Event history
Information on an event that occurs in Real-time Flow Manager and a data collector or IT gateway used in Real-time Flow
Manager is acquired, and the history, detailed information, cause, and corrective action are displayed as diagnosis
information.
The event history is saved even after turning OFF an industrial PC that runs Real-time Flow Manager. Therefore, it can bechecked after restarting the industrial PC and used for identifying the cause of a problem by checking the operation
information before and after the event. It can also be used when the error code cannot be checked if an error occurs.
However, if errors and events occur consecutively at short intervals, they may not be displayed in chronological order in theevent history.

11

For details on saving an event history, refer to the following:
Page 336 Saving event histories

Window
Click the [Event History] button.

(1)

(2)

(3)

Displayed items
Item

Description[Update to Latest State] button

Click this to update the event history list.

Advanced Search(2) Event history list(3) Event detailed
information[Delete Event] button

Match all the conditions

Select this to display an event that satisfies all specified narrowing-down conditions.

Match any of the conditions

Select this to display an event that satisfies any of the specified narrowing-down conditions.

(1) Narrowing-down
condition

Specify a narrowing-down condition.*1
Up to three narrowing-down conditions can be set.

[Start Refinement] button

Click this to narrow down events under a specified condition.

[Reset Advanced Search
Conditions] button

Click this to initialize narrowing-down conditions.

Time and Date of
Occurrence

The year, month, day, and time when an event occurs are displayed.

Event TypeThe type of an event is displayed.

Status

The status of an event is displayed.

Event CodeThe code for an event is displayed.

Overview

The overview of an event is displayed.

Problem Function

The occurrence source of an event is displayed.

Detailed Information

Detailed information of an event is displayed.

Cause

When the classification of an event is "Error," the cause of the event is displayed.

Treatment

When the classification of an event is "Error," the corrective action for the event is displayed.
Click this to delete an event history.

11 TROUBLESHOOTING
11.2 Checking the Status of a Process Flow

335

Item

Description[File Saving] button

Click this to save the display contents to a CSV file.

*1

Up to 32 characters can be set when specifying character strings for a narrowing-down condition.

For events output by Windows as a standard, use the Windows standard event function.

Saving event histories
Event information collected from Real-time Flow Manager and a data collector or IT gateway used in Real-time Flow Manager
can be saved.
• Number of events that can be saved as an event history
39999 events can be saved. If it is exceeded, registered events will be deleted in chronological order.
• Environment where an event history can be collected
An event history can be collected regardless of the operating status. However, if a major error occurs or Windows stops theoperation, an event history may not be collected.

336

11 TROUBLESHOOTING
11.2 Checking the Status of a Process Flow

Process flow diagnostics
The following shows the screen for displaying the execution status of a data logging flow and data diagnosis flow, and thelatest error.
If an error occurs while Real-time Flow Manager is running, the process flow and the process name of the occurrence source
are displayed. If the error is a moderate or major one, Real-time Flow Manager will stop the process flow.

Window
Select "Real-time Flow Manager Diagnostics"  "Process Flow Diagnostics"  "Data Logging Flow" or "Data Diagnosis Flow"in the "Real-time Flow Manager Diagnostics" screen.

11

Displayed items
Item

Description

Data Logging Flow Name
Data Diagnosis Flow Name

The name of each process flow is displayed.

Status

The execution status of each process flow is displayed.
*1

Data Miss Cnt.

The number of times of data missing for each process flow is displayed.

Last Collected Time*1*2

The last data collection time for each process flow is displayed.
The time zone corresponds to the local time of the system.
When changing the time zone setting of the system while Real-time Flow Designer is running, the change is applied at
the next startup of Real-time Flow Designer.
"N/A" remains displayed until the first data is collected for each process flow.

Error CodeThe code for an error occurred in each process flow is displayed.

Error Occurrence Process Name

The name of an error occurrence process of each process flow is displayed.

Problem Function

An error occurrence source is displayed.

*1*2

Not updated when only data collection is set in a data logging flow (excluding when using CSV File Data collector).
Updated with the time of last data collection from a data collector, regardless of whether data missing occurs.

• If monitoring is stopped, the contents when the monitoring is stopped will remain displayed.
• Each item is updated in a one-second cycle.

11 TROUBLESHOOTING
11.2 Checking the Status of a Process Flow

337

Device access diagnosis
The following shows the screen for displaying the connection status between Real-time Flow Manager and an access target
device, and the latest error.
If an error occurs after running a process flow, an error occurred in an access target device is displayed.

Window
Select "Real-time Flow Manager Diagnostics"  "Device Access Diagnostics" in the "Real-time Flow Manager Diagnostics"
screen.

Displayed items
Item

Description

Target Device Name

An access target device set in the access target device setting in Real-time Flow Designer is displayed. (Page 124
Access Target Device Setting)Status

The connection status with an access target device is displayed.
• Connection: Connected to an access target device• Disconnection: Not connected to an access target device*1

Error CodeThe code for an error occurred in accessing an access target device is displayed.

Problem Function

An error occurrence source is displayed.

*1

When the status of a process flow transitions from the RUN state to the STOP state, "Disconnection" is displayed for all access target
devices connected in the process flow.

• If monitoring is stopped, the contents when the monitoring is stopped will remain displayed.
• The cell is blank in either of the following cases:
An access target device is set in the access target device setting in Real-time Flow Designer but not set in
the data collection setting or device instruction feedback setting.
CSV File Data collector is used as a data collector in an access target device set in the access target device
setting.

338

11 TROUBLESHOOTING
11.2 Checking the Status of a Process FlowIT gateway diagnosis
The following shows the screen for displaying the connection status between Real-time Flow Manager and a communication
destination of an IT gateway, and the latest error.
If an error occurs after running a process flow, an error occurred in an IT gateway is displayed.

Window
Select "Real-time Flow Manager Diagnostics"  "IT Gateway Diagnostics" in the "Real-time Flow Manager Diagnostics"

11

screen.

Displayed items
Item

Description

IT Gateway Setting Name

The name of an IT gateway setting configured in Real-time Flow Designer is displayed. (Page 127 IT Gateway
Setting)

IT Gateway TypeAn IT gateway type is displayed.

Status

The connection status with an IT gateway is displayed.
• Connection: Connected to an IT gateway• Disconnection: Not connected to an IT gateway*1

Error CodeThe code for an error occurred in accessing a communication destination of an IT gateway is displayed.

Problem Function

An error occurrence source is displayed.

*1

When the status of a process flow transitions from the RUN state to the STOP state, "Disconnection" is displayed for all IT gateways
connected in the process flow.

• If an IT gateway is set in the IT gateway setting in Real-time Flow Designer but not set in the data storing
setting or data distribution setting, the cell is blank.

11 TROUBLESHOOTING
11.2 Checking the Status of a Process Flow339

Status memory monitor
The following shows the screen for monitoring the Real-time Flow Manager status.
Page 433 Real-time Flow Manager Status

Window
Select "Status memory monitor" in the "Real-time Flow Manager Diagnostics" screen.

(1)

Displayed items
Item

Description

Category specification

Monitoring target

Specify a category of the Real-time Flow Manager status to monitor.
For the combinations of selectable items, refer to the following:
Page 340 Combinations of selectable items

Detail Item 1
Detail Item 2

Address specification[Status display] button

Click this to display the Real-time Flow Manager status of a category specified in "Category
specification."

Address

Specify an address of the Real-time Flow Manager status to monitor (0 to 420999).*1

The number of data

Specify the number of words to display the Real-time Flow Manager status to monitor (1 to 500).*1[Status display] button

Click this to display the Real-time Flow Manager status from an address specified for "Address" to
one for the number of words specified for "The number of data."

Display format

Select a display format of the displayed Real-time Flow Manager status.

(1) Real-time Flow Manager status list

Real-time Flow Manager status is displayed in a list.

*1

Specify it in decimal.

If monitoring is stopped, the contents when the monitoring is stopped will remain displayed.

Combinations of selectable items
Monitoring target

Detail Item 1

Detail Item 2

Data Logging Flow Information

Flow No.1 to 32

Data Diagnosis Flow Information

Flow No.1 to 32

Data Logging Flow Process Information

Flow No.1 to 32

Process No.1 to 4

Data Diagnosis Flow Process Information

Flow No.1 to 32

Process No.1 to 6

Error Log Information

Error Information

Error No.1 to 64Target Device Information

Target Device No.1 to 32



IT Gateway Diagnosis Information

IT Gateway No.1 to 16

340

11 TROUBLESHOOTING
11.2 Checking the Status of a Process Flow

11.3

Checking the Status of Management Shell

This section shows the method for checking the operating status of Management Shell.

OPC UA diagnosis
The following shows the screen for displaying the operating status of Management Shell and OPC UA diagnosis information.

Window

11

Select [Management Shell]  [Diagnosis]  [OPC UA Diagnosis].

Displayed items
Item

Description

Operating Status

The operating status of Management Shell is displayed.

Number of connected*1

The number of applications connected to Management Shell is displayed.

Application Name*2,*3

The name of an application connected to Management Shell is displayed.

Connection source information*2,*4

The information on an application connected to Management Shell is displayed.
For the displayed information, refer to the manual for the application.

Number of monitoring target items*2,*5

The number of monitoring target items*6 for an application connected to Management Shell is displayed.

[Update] button*7

Click this to update the screen.

*1

*2
*3

*4

*5
*6

*7

"-" is displayed in either of the following cases:"Stop" is displayed for "Operating Status."
Acquisition failed.
Nothing is displayed when "Stop" is displayed for "Operating Status.""Unknown" is displayed in either of the following cases:
Acquisition failed.
An acquired application name is blank.
"Unknown" is displayed in either of the following cases:
Acquisition failed.
Acquired connection source information is blank.
"-" is displayed if acquisition fails.
Attribute of a resource (node) registered as a monitoring target in Management Shell from an application (An attribute refers to data
included in a node.)
For the nodes and attributes that can be registered as monitoring targets, refer to the following:
Page 22 Nodes and attributes that can be registered as monitoring targets
Cannot be clicked when "Stop" is displayed for "Operating Status."• An application in the "OPC UA Diagnosis" screen refers to an edge application connected as an OPC UA
client to Management Shell that is an OPC UA server.
• To reduce the number of connected applications, disconnect or stop a connected application.
• To reduce the number of monitoring target items, delete an unnecessary item set as a monitoring target in aconnected application.

11 TROUBLESHOOTING
11.3 Checking the Status of Management Shell

341

Precautions• Even when disconnecting an application, some applications may remain connected in the background on Windows. In thiscase, the number of applications displayed for "Number of connected" includes these applications.
• A number displayed in "Number of monitoring target items" may differ from one set or displayed in a connected application.
• A number displayed in "Number of monitoring target items" increases in proportion to one set in an application.
• If a number displayed in "Number of monitoring target items" exceeds the maximum number of monitoring target items thatcan be registered (1000000 points), an error may occur in an application. In this case, reduce the number set in theapplication. For the setting method, refer to the manual for each application.
• If the number of applications displayed for "Number of connected" exceeds the maximum number of connectableapplications, an error may occur in an application. In this case, reduce the number of connected applications, such as
stopping an application. For the method for stopping an application, refer to the manual for each application.
• A name displayed in "Application Name" may differ from the product name of an application. For displayed names, refer tothe manual for each application.

342

11 TROUBLESHOOTING
11.3 Checking the Status of Management Shell

Displaying error information in a list
The following shows the screen for displaying the list of information on an error that occurs in Management Shell and a datacollector or IT gateway used in Management Shell.

Window
Select [Management Shell]  [Error Information List].

11
(1)

(2)

Displayed items
Item

Description(1) Error information list

Time and Date of
Occurrence

The year, month, day, and time when an error occurs are displayed.

Importance Level

The severity of an error is displayed.

Error CodeAn error code acquired from Management Shell is displayed.
For an error occurred in a data collector or an IT gateway, an error code defined in each datacollector or IT gateway is displayed.
For details, refer to the manual for each data collector or IT gateway.

Overview

The overview of an error that is occurring is displayed.

Problem Function

An error occurrence source is displayed.

Detailed Information

Detailed information of an error is displayed.

Cause

An error cause is displayed.

[Clear Error] button

Click this to delete minor errors displayed in the error information list in a batch.

(2) Error detailed
information

Treatment

When the classification of an event is "Error," the corrective action for the error is displayed.

[File Saving] button

Click this to save the display contents to a CSV file.

[Event History] button

Click this to display the "Event History" screen.
Page 344 Event history• Up to 50 errors are displayed.
• An error history can be cleared by performing the following procedure: Select [Management Shell]  [Management Shell Stop].
 Select [Management Shell]  [Management Shell Start].

Precautions• If an error other than a minor error is also displayed in the error information list, the minor error cannot be deleted.
• Minor errors are deleted in a batch; therefore, unintended errors may also be deleted.
• Even if a minor error is deleted from the error information list, it is not deleted from the event history.
• Even if a minor error is deleted from the error information list, its cause is not removed; therefore, the same error may occur
again.
11 TROUBLESHOOTING
11.3 Checking the Status of Management Shell

343

Event history
Information on an event that occurs in Management Shell and a data collector or IT gateway used in Management Shell isacquired, and the history, detailed information, cause, and corrective action are displayed as diagnosis information.

Window
Click the [Event History] button in the "Error Information List" screen.

(1)

(2)

(3)

Displayed items
Refer to the following:
Page 335 Event history344

11 TROUBLESHOOTING
11.3 Checking the Status of Management Shell

11.4

Troubleshooting by Symptom

If a function of Edgecross Basic Software does not run properly, check the applicable items in the following and troubleshootthe error.
If each troubleshooting does not solve the problem, consult the Edgecross Consortium.
For other troubleshooting, refer to the manual for each industrial PC or data collector, or visit the Microsoft website.

Precautions
Do not start or terminate processes or services of Edgecross Basic Software from the task manager. Otherwise, Edgecross

11

Basic Software may not run properly. If it stops, restart an industrial PC.

Real-time Flow Manager
A process flow does not run properly
Check the following items:

Common item for each function
Symptom

Check item

Corrective action

The same error occurs even after thecorrective action was taken.

Is antivirus software installed?

In the antivirus software settings, exclude the following folders from themonitoring targets. For the setting method, refer to the manual for antivirus
software.
• Installation destination folder for Edgecross Basic Software• Installation destination folder for an MQTT broker (Page 507 Installing
Eclipse Mosquitto)• Save destination folder specified in the data storing setting (file saving)(Page 147 Saved file)• Folder in which a certificate authority certificate specified in the data
distribution setting is stored (Page 160 Destination)• Folder in which a certificate authority certificate specified in the edge
application diagnosis (MQTT) setting is stored (Page 174 Destination)• Save destination folder specified in the edge application diagnosis (file)setting (Page 182 Saved file)• Monitoring folder specified in the data collection setting (CSV File Data
collector) (Page 310 Data Collection Setting (CSV File Data collector))• Save destination folder specified in the file saving setting of the one-shotcollection function (Page 286 File saving setting)• Save destination folder specified in the save destination folder setting forthe event history automatic output function (Page 118 Event history
automatic output setting, Page 292 Event history automatic output setting
screen)The operating status of a process
flow differs between when starting an
industrial PC and after restarting it.

Is the fast startup function of
Windows enabled?

Refer to the following section to review the settings of the fast startup function.
Page 114 Procedure for disabling the fast startup function

A major error occurred before
restarting an industrial PC is notcleared even after restarting it.

Is the fast startup function of
Windows enabled?

Refer to the following section to review the settings of the fast startup function.
Page 114 Procedure for disabling the fast startup function

It takes time to switch the operating
status of a process flow.

Are the operating statuses of multiple
process flows switched at the sametime?

Switch the operating statuses multiple times.

Has a Real-time Flow Manager
timeout occurred?

Check the corrective action for the error in the "Real-time Flow Manager
Diagnostics" screen, and take the action.

There is a large variation in the timingof completion of switching theoperating status of a process flow.

Are the operating statuses of multiple
process flows switched at the sametime?

Switch the operating statuses multiple times.

An out of memory error occurs whenswitching the operating status of aprocess flow from the STOP state to
the RUN state.

Is free space on the memory low?

• Reduce the memory usage amount, such as by closing other applications.
• Increase the free space on the system drive.
• Review the collection cycle, number of data collection points, processing
contents, and number of process flows to reduce the memory usage
amount.
• Increase the memory.

11 TROUBLESHOOTING
11.4 Troubleshooting by Symptom

345

SymptomCheck item

Corrective action

Fails to connect to an access target
device when switching the operating
status of a process flow from the
STOP state to the RUN state after
reading a setting file saved in anotherindustrial PC.

Is the access target device in theread setting properly set for anindustrial PC in which the setting fileis read?

Correct the access target device setting according to the industrial PC in
which the setting file is read. For details, refer to the manual for a datacollector used.

Data collection function
Symptom

Check item

Corrective action

A symptom caused by data missing
occurs in an edge application.

Has an error occurred in the datacollector in a process flow that links
the edge application with Real-time
Flow Manager?

Perform the following procedure to avoid data missing.
 Check the number of times of data missing in the process flow diagnostics
of Real-time Flow Designer, and identify a process flow in which the data
missing occurs. (Page 337 Process flow diagnostics)
 Check if an error occurs in the data collector set in the process flow inwhich the data missing occurs in the operation diagnosis, and take corrective
action if it does. (Page 334 Operation diagnosis)
 Refer to the manual for the data collector and review the setting to avoid
data missing.

Is the operation delayed due to highload on the system?

The load on the system is high. Review the setting to reduce the load
(lengthen the collection cycle or reduce the number of data collection points,etc.).

Edge application cooperation function (MQTT cooperation)
Symptom

Check item

Corrective action

Data received in an edge application
is incorrect.

Is the content of a publishing datasetting configured in Real-time Flow
Designer different from that of apublishing data definition file read in
the edge application?

Output the publishing data definition file again, and read it to the edge
application.

Is a topic name that is used in Realtime Flow Manager and the edge
application used in anotherapplication?

Set a publishing data topic name so that it is not duplicated with one used inanother application.

Is an IP address, host name, or port
number set correctly?

Set a correct IP address, host name, or port number.

Is the connection allowed to aconnected MQTT broker on anotherindustrial PC?

Allow the connection.
For the setting method, refer to the following:
Page 528 Configuring the settings for connection from another industrial
PC

Is the content of a publishing datasetting configured in Real-time Flow
Designer different from that of apublishing data definition file read in
the edge application?

Output the publishing data definition file again, and read it to the edge
application.

Does the communication encryption
setting match that of a connected
MQTT broker?

Set the encryption setting according to that of the connected MQTT broker.

Does a client ID of Real-time Flow
Manager set in Real-time Flow
Designer match a specified one if it isspecified in a connected MQTT
broker?

In Real-time Flow Designer, set the client ID specified in the connected MQTT
broker.

Does a publishing data topic nameset in Real-time Flow Designer matcha specified one if it is specified in theedge application?

In Real-time Flow Designer, set the publishing data topic name specified in
the edge application.

Does a client ID of the edge
application set in Real-time Flow
Designer match a specified one if it isspecified in the edge application?

In Real-time Flow Designer, set the client ID specified in the edge application.

Is a setting file that is saved inanother industrial PC and has no
specified publishing data topic nameread?

Set the following settings again in the edge application diagnosis (MQTT)
screen.
• Output a publishing data definition file, then read it in the edge application.
• After outputting a publishing data definition file, click the [OK] button toclose the edge application diagnosis (MQTT) screen, then click the [OK]button to close the process flow setting screen.

Data is not received in an edge
application.

346

11 TROUBLESHOOTING
11.4 Troubleshooting by Symptom

SymptomCheck item

Corrective action

An edge application acquires thesame data multiple times and does
not run properly.

Is an industrial PC on which Realtime Flow Manager is running
disconnected from a network andreconnected to it?

• Prevent network disconnection.
• Reduce the load on the network.

Is the load on a network high?
Data received in an edge application
is missing.
An edge application is connected anddisconnected repeatedly.

Is a same client ID used forconnecting multiple edge applications
and a single MQTT broker?

Change the client ID settings for the applicable edge applications. Then,output a publishing data definition file and read it in the edge application.

11

Edge application cooperation function (file cooperation)
Symptom

Check item

Corrective action

Diagnosis is not performed evenwhen switching a process flow to
RUN.

Is an edge application in a state inwhich diagnosis can be performed?

Set the edge application to a state in which diagnosis can be performed.

Data received in an edge application
is incorrect.

Is the content of a publishing datasetting configured in Real-time Flow
Designer different from that of apublishing data definition file read in
the edge application?

Output the publishing data definition file again, and read it to the edge
application.

Data storing function (file saving function)
Symptom

Check item

Corrective action

A file is not saved even when datacollection has been completed.

Has the number of times of datacollection increased in the Real-time
Flow Manager status?

The load on the system is high. Review the setting to reduce the load
(lengthen the collection cycle or reduce the number of data collection points,etc.).

Has the number of times of data
missing increased in the process flow
diagnostics?

• Check if an error occurs in a data collector set in the process flow in whichdata missing occurs, and take corrective action displayed in the diagnostics
screen if it does.
• Refer to the manual for the data collector and review the setting to avoid
data missing.
• The load on the system is high. Review the setting to reduce the load
(lengthen the collection cycle or reduce the number of data collection
points, etc.).

Does the number of the file namesuffix reach 'FFFFFFFF'?

Move all files in a save destination folder to another folder and restart theoperation of Real-time Flow Manager, or set another path for the savedestination folder.

The time stamp of a saved file isdifferent from that of the last record ina file.

Is the time stamp of a record in thelast row in the saved file significantly
different from the update date/time of
the file in the Windows Explorer
screen?

The load on the system is high. Review the setting to reduce the load
(lengthen the collection cycle or reduce the number of data collection points,etc.).

Data received in an edge application
is incorrect.

Is the content of a file saving setting
configured in Real-time Flow
Designer different from that of a data
definition file read in the edge
application?

Output the data definition file again, and read it to the edge application.

Unable to browse a saved file.

Is the encryption attribute enabled forthe save destination folder set in
Real-time Flow Designer?

• Check the user name and password of a user account for outputting the
saved file, and change them to those of a user account for browsing the file.
• Sign in again to Windows with a user account set as one for outputting the
saved file in Real-time Flow Designer.

Unable to send files by using an IT
gateway (data storing).

Is the encryption attribute enabled forthe save destination folder set in
Real-time Flow Designer?

A file output to a folder with the encryption attribute enabled may not be sentby using an IT gateway (type: data storing). Change the save destination
folder to another one with the encryption attribute disabled, or take corrective
action according to the manual for the IT gateway.

Fails to save a file to a folder with theencryption attribute enabled.

Is there a historical data definition filewith the same prefix created byanother user account in the savedestination folder?

A historical data definition file cannot be overwritten due to the difference inauthority, such as when a user account to output a saved file is different from
one that created the existing historical data definition file. Perform any of thefollowing operations:• Change the prefix to one different from that of the existing historical data
definition file.
• Change the save destination folder to another one.
• Delete the historical data definition file if possible.

11 TROUBLESHOOTING
11.4 Troubleshooting by Symptom

347

SymptomCheck item

Corrective action

Fails to save a file by specifying auser account.

Is the user account specified in Realtime Flow Designer locked out?

• Wait until the user account is unlocked, or set another user account that is
not locked out.
• Make sure that the authentication test for a user account can be performed
properly.

Fails to save a file by specifying auser account for which no password
is set.

Is "Enabled" selected for "Accounts:
Limit local account use of blankpasswords to console logon only"*1
on an industrial PC?

• Use a user account for which a password is set.
• Select "Disabled" for "Accounts: Limit local account use of blank passwords
to console logon only"*1 on the industrial PC.*2• Allow access to the shared folder with a blank password on the personal
computer side on which the shared folder is published.*2

Is access to a shared folder allowedwith a blank password on the
personal computer side on which theshared folder is published when asave destination is a remote sharedfolder?

*1*2

Can be checked by the following procedure: Start the local security policy of Windows.
 Select [Security Settings]  [Local Policies]  [Security Options].
Not recommended because users, who can access industrial PCs and personal computers on which shared folders are published, canlog on with a user account for which no password is set.

Data storing function (DB saving function)
Symptom

Check item

Corrective action

Fails to save (INSERT) data to a
database.

Is the connection setting for the
database configured correctly?

Review the ODBC setting and the data storing setting (DB saving) for Realtime Flow Designer. Also, check the ODBC error code in the detailed
information in the error information list in the "Real-time Flow Manager
Diagnostics" screen of Real-time Flow Designer, and take corrective action.

Incorrect data is stored in a DB.

Is the table setting configured in
Real-time Flow Designer different
from the one configured in the DB?

Output the DDL file and create the table in the DB again.

A 'DB reception of data missing' error
occurs when switching the operating
status of a process flow from STOP
to RUN.

Does a 'DB reception of data missing'error appear in the "Real-time Flow
Manager Diagnostics" screen?

• Review the collection cycle, number of data collection points, processing
contents, and number of process flows to reduce the load.
• Reduce the load on Windows by closing other applications.

Is the load on Windows high bysetting a large number of process
flows?

Data distribution function
Symptom

Check item

Corrective action

Data received in an edge application
is incorrect.

Is the content of a publishing datasetting configured in Real-time Flow
Designer different from that of apublishing data definition file read in
the edge application?

Output the publishing data definition file again, and read it to the edge
application.

Is a topic name that is used in Realtime Flow Manager and the edge
application used in anotherapplication?

Set a publishing data topic name so that it is not duplicated with one used inanother application.

348

11 TROUBLESHOOTING
11.4 Troubleshooting by Symptom

SymptomCheck item

Corrective action

Data is not received in an edge
application.

Is an IP address, host name, or port
number set correctly?

Set a correct IP address, host name, or port number.

Is the connection allowed to aconnected MQTT broker on anotherindustrial PC?

Allow the connection.
For the setting method, refer to the following:
Page 528 Configuring the settings for connection from another industrial
PC

Is the content of a publishing datasetting configured in Real-time Flow
Designer different from that of apublishing data definition file read in
the edge application?

Output the publishing data definition file again, and read it to the edge
application.

Does the communication encryption
setting match that of a connected
MQTT broker?

Set the encryption setting according to that of the connected MQTT broker.

Is '1' set for QoS in Real-time Flow
Designer when connecting to an
MQTT broker that does not support
QoS2?

Set '1' for QoS.

Does a client ID of Real-time Flow
Manager set in Real-time Flow
Designer match a specified one if it isspecified in a connected MQTT
broker?

In Real-time Flow Designer, set the client ID specified in the connected MQTT
broker.

Does a publishing data topic nameset in Real-time Flow Designer matcha specified one if it is specified in theedge application?

In Real-time Flow Designer, set the publishing data topic name specified in
the edge application.

Has the number of times of data
missing increased in the process flow
diagnostics?

• Check if an error occurs in a data collector set in the process flow in whichdata missing occurs, and take corrective action displayed in the diagnostics
screen if it does.
• Refer to the manual for the data collector and review the setting to avoid
data missing.
• The load on the system is high. Review the setting to reduce the load
(lengthen the collection cycle or reduce the number of data collection
points, etc.).

Is a setting file that is saved inanother industrial PC and has no
specified publishing data topic nameread?

Set the following settings again in the data distribution setting screen.
• Output a publishing data definition file, then read it in the edge application.
• After outputting a publishing data definition file, click the [OK] button toclose the data distribution setting screen, then click the [OK] button to close
the process flow setting screen.

Are both of the following satisfied?
• '1' is set for QoS.
• QoS1 is not supported by an edge
application.

Set '2' for QoS.

Is an industrial PC on which Realtime Flow Manager is running
disconnected from a network andreconnected to it?

• Prevent network disconnection.
• Reduce the load on the network.

An edge application acquires thesame data multiple times and does
not run properly.

11

Is the load on a network high?
Unable to read a publishing data
definition file in an edge application.
An error occurs when data isreceived in an edge application.

Is '1' set for QoS?

Set '2' for QoS.

Common items for a data collector and IT gateway
Symptom

Check item

Corrective action

The following error occurs:• Data collector service corruption
error (error code: 5021H)

Is an access target device setting of
Real-time Flow Manager parameter
updated after updating a datacollector?

Update the version of a data collector for an access target device setting byperforming either of the following operations:• Start Real-time Flow Designer.
• Click the [Update to Latest State] button in the "Data collector List" screen of
Real-time Flow Designer running.
When the confirmation message indicating whether to update the version
appears, select [Yes]. Then, apply the setting and switch the operating statusof a process flow to RUN.
If the same error occurs again after the operation, the data collector may becorrupted. In this case, contact the developer of the data collector.

11 TROUBLESHOOTING
11.4 Troubleshooting by Symptom349

SymptomCheck item

Corrective action

The following error occurs:• IT Gateway service corruption error(error code: 5027H)

Is an IT gateway setting of Real-time
Flow Manager parameter updated
after updating an IT gateway?

Update the version of an IT gateway for an IT gateway setting by performing
either of the following operations:• Start Real-time Flow Designer.
• Click the [Update to Latest State] button in the "IT Gateway List" screen of
Real-time Flow Designer running.
When the confirmation message indicating whether to update the version
appears, select [Yes]. Then, apply the setting and switch the operating statusof a process flow to RUN.
If the same error occurs again after the operation, the IT gateway may becorrupted. In this case, contact the developer of the IT gateway.

A file/folder cannot be accessed
Check the following items:
Check item

Corrective action

Is there any free space on the drive to write?

• Secure free space by deleting files in the drive to write.
• Change the drive to write to another one.

Is there an application using a target file?

Stop an application using a target file.

Is a file or a folder written to Windows system drive?

Change the writing destination drive.

Is required access granted to a user who accesses a target file and folder?

Grant required access.

350

11 TROUBLESHOOTING
11.4 Troubleshooting by Symptom

Real-time Flow Designer
The select folder screen is frequently updated and it cannot be operated
Check the following item:
Check item

Corrective action

Is Real-time Flow Manager stopped?

Stop Real-time Flow Manager then operate the "Select Folder" screen.

11

Contents in the screen are not displayed properly
Check the following item:
Check item

Corrective action

Is a value other than 100% set for "Change the size of text, apps, and otheritems" in Windows?

• Change the value to 100% for "Change the size of text, apps, and otheritems."• For Windows 10 (version 1703 or later) or later*1, the display of Real-time
Flow Designer can be enlarged with high DPI scaling by using a Windows
function.*2
 Select 'ProcessDesigner.exe'*3, then select [Properties] on the right-clickmenu.
 Select the checkbox of "Override high DPI scaling behavior. Scaling
performed by:" in the [Compatibility] tab, then select "System" from the pulldown list.
 Click the [OK] button.

*1

*2

*3

The Windows version can be checked by the following procedure: Enter "winver" in the search box of Windows, and select it from the menu.
 Check the version in the displayed screen.
The display of Real-time Flow Designer will be blurred by enlarging.
The following lists the setting values for "Change the size of text, apps, and other items" and the recommended display resolution foreach setting value in Windows 10 or later.
Setting value: 100%, display resolution: 1024  768 dots or more
Setting value: 125%, display resolution: 1900  1200 dots or more
Setting value: 150%, display resolution: 1900  1200 dots or more
Setting value: 175%, display resolution: 2880  1620 dots or more
Setting value: 200%, display resolution: 2880  1620 dots or more
Setting value: 225%, display resolution: 3840  2160 dots or more
Setting value: 250%, display resolution: 3840  2160 dots or more
'ProcessDesigner.exe' is stored in the folder in which Edgecross Basic Software is installed.
The following is an example of a storage location.
(Example) When starting the operating system on the C drive and setting the installation destination folder as the default
C:\Edgecross\Edgecross Basic Software\Real-timeFlowDesigner\ProcessDesigner.exe

11 TROUBLESHOOTING
11.4 Troubleshooting by Symptom

351

The same error occurs even after the corrective action was taken
Check item

Corrective action

Is antivirus software installed?

In the antivirus software settings, exclude the following folders from themonitoring targets. For the setting method, refer to the manual for antivirus
software.
• Installation destination folder for Edgecross Basic Software• Installation destination folder for an MQTT broker (Page 507 Installing
Eclipse Mosquitto)• Save destination folder specified in the data storing setting (file saving)(Page 147 Saved file)• Folder in which a certificate authority certificate specified in the data
distribution setting is stored (Page 160 Destination)• Folder in which a certificate authority certificate specified in the edge
application diagnosis (MQTT) setting is stored (Page 174 Destination)• Save destination folder specified in the edge application diagnosis (file)setting (Page 182 Saved file)• Monitoring folder specified in the data collection setting (CSV File Data
collector) (Page 310 Data Collection Setting (CSV File Data collector))• Save destination folder specified in the file saving setting of the one-shotcollection function (Page 286 File saving setting)• Save destination folder specified in the save destination folder setting forthe event history automatic output function (Page 118 Event history
automatic output setting, Page 292 Event history automatic output setting
screen)Setting contents cannot be opened
If such a message appears, check the following item:
Check item

Corrective action

Are the version of Real-time Flow Designer in which a read setting file wascreated and that of running Real-time Flow Designer same or the latest one?

Install the latest version of Edgecross Basic Software.

Authentication test by specifying a user account for which no password is set fails
Check item

Corrective action

Is "Enabled" selected for "Accounts: Limit local account use of blankpasswords to console logon only"*1 on an industrial PC?

• Use a user account for which a password is set.
• Select "Disabled" for "Accounts: Limit local account use of blank passwords
to console logon only"*1 on the industrial PC.*2

*1

*2

352

Can be checked by the following procedure: Start the local security policy of Windows.
 Select [Security Settings]  [Local Policies]  [Security Options].
Not recommended because users, who can access industrial PCs and personal computers on which shared folders are published, canlog on with a user account for which no password is set.

11 TROUBLESHOOTING
11.4 Troubleshooting by Symptom

Reading setting contents fails at the time of startup
If such a message appears, check the following items:
Check item

Corrective action

Is an industrial PC restarted after installing Edgecross Basic Software or
installing over it?

Restart the industrial PC.

Is the fast startup function disabled?

Disable the fast startup function, then restart the industrial PC.
Page 114 Procedure for disabling the fast startup function

11

Operations cannot be performed when applying the setting
If such a message appears, check the following items:
Check item

Corrective action

Is a user operating Real-time Flow Designer granted the write authority in the
installation folder for Edgecross Basic Software?

Grant the authority to the user.

Is Edgecross Basic Software installed in a target folder for the user accountcontrol (UAC) (Program Files, etc.)?

• Start Real-time Flow Designer with the administrator authority.
• Reinstall Edgecross Basic Software in a folder other than the targets.

A file/folder cannot be accessed
Refer to the following:
Page 350 A file/folder cannot be accessed

11 TROUBLESHOOTING
11.4 Troubleshooting by Symptom

353

Management Shell
Troubleshooting on the startup
Check the following items:
Symptom

Check item

Corrective action

Display contents are not displayed on the screen ofManagement Shell Explorer.

Is Management Shell running?

• Start Management Shell by the following
procedure: Select [Management Shell]  [Management
Shell Start].
• If it is not solved after performing the above
procedure, perform either of the following
operations:
Import a setting file. (Select [Management Shell] [Import].)Return the setting to the default. (Select[Management Shell]  [Delete All].)

Was the following message notified?
"OPC UA Setting" has not been performed. Pleasedisplay and set the OPC UA setting from thefollowing menu.
• [Setting] - [OPC UA Setting]Select [Setting]  [OPC UA Setting], and set each
item in the [Server Setting] tab in the "OPC UA
Setting" screen.
Page 261 Setting an OPC UA server

Is Management Shell Explorer started from ashortcut in which a work folder is not specified?

Reinstall Edgecross Basic Software and startManagement Shell Explorer from the shortcut
created by the installer.

Is Management Shell Explorer started from thecommand prompt?

A message indicating that processing is notcompleted appears when starting Management
Shell Explorer.

*1

354

Does the following message appear?
'Failed to connect to Management Shell.
Please restart Management Shell Explorer with theadministrator authority.'

Start Management Shell Explorer with theadministrator authority.
Page 194 Procedure for starting it with theadministrator authority

Has an industrial PC been restarted with the fast
startup function enabled after Management Shell
stopped?

Disable the fast startup function.

Does a user have the access right to the folder*1 inwhich Management Shell is stored?

Perform the following procedure: Right-click a folder*1 in which Management
Shell is stored.
 Select [Properties], and click the [Security] tab.
 Click the [Edit] button.
 Click the name of a logged in user.
 Select the checkbox under "Allow" for"Permissions."

Is a user operating Management Shell Explorer
granted the write authority in the installation folder
for Edgecross Basic Software?

Grant the authority to the user.

Is Edgecross Basic Software installed in a target
folder for the user account control (UAC) (Program
Files, etc.)?

• Start Management Shell Explorer with theadministrator authority.
Page 194 Procedure for starting it with theadministrator authority• Reinstall Edgecross Basic Software in a folder
other than the targets.

Stored in the folder in which Edgecross Basic Software is installed.
The following is an example of a storage location.
(Example) When starting the operating system on the C drive and setting the installation destination folder as the default
C:\Edgecross\Edgecross Basic Software\Management Shell

11 TROUBLESHOOTING
11.4 Troubleshooting by Symptom

Troubleshooting on basic operations
Check the following items:
Symptom

Check item

Corrective action

Export fails.

Is there any space left on the disk?

Secure free space on the disk, and execute itagain.

Can Management Shell be stopped or started?

• Restart the industrial PC.
• Reinstall Edgecross Basic Software.

Is there any space left on the disk?

Secure free space on the disk, and execute itagain.

Is a setting file or icon file open in anotherprogram?

Close a program locking the file, and execute itagain.

Can Management Shell be stopped or started?

• Restart the industrial PC.
• Reinstall Edgecross Basic Software.

Fails to connect to an access target device after
importing a data model exported from anotherindustrial PC.

Is the access target device properly set for theimport destination industrial PC?

Correct the access target device setting according
to the import destination industrial PC. For details,
refer to the manual for a data collector used.

All deletion fails.

Is Management Shell running?

Start Management Shell by the following
procedure: Select [Management Shell]  [Management
Shell Start].

Display contents are not displayed on the screen ofManagement Shell Explorer.

Is Management Shell running?

Start Management Shell by the following
procedure: Select [Management Shell]  [Management
Shell Start].

Unable to display the manual by using the [Help]menu.

Is Management Shell Explorer started with theadministrator authority?

• Restart the industrial PC, and start Management
Shell Explorer without the administrator
authority.
• Change the application associated with theextension of PDF.

Import fails.

11

Troubleshooting on monitoring and changing of current values of data tag resources
Check the following items:
Symptom

Check item

Corrective action"N/A" is displayed in "Current Value."

Is monitoring started in the data tag resource
monitor window?

Click the [Start Monitoring] button in the data tag
resource monitor window.

Is Management Shell running?

Start Management Shell by the following
procedure: Select [Management Shell]  [Management
Shell Start].

Are the contents in the "Error Information List"
screen checked?

Take corrective action according to the contents
displayed in the "Error Information List" screen.

Is a data collector installed?

Reinstall the data collector.

Is the response time of a data collector exceeded?

Check the status of the access target device andthe communication route with the access target
device.

Is a compatible data collector installed?

Check the version of the data collector inManagement Shell Explorer. If the version has
been updated, display the "Target Device Setting"screen and upgrade the parameters.

A current value does not change.

Is the update interval of a current value set
correctly?

Set the update interval of the current value again.
Page 211 Changing a monitoring update
interval

Unable to change a current value.

Is a data collector supporting the data writing
function used?

Check if the data collector referenced by a data tag
resource to change the current value supports thedata writing function.

11 TROUBLESHOOTING
11.4 Troubleshooting by Symptom355

Troubleshooting on OPC UA connection
Check the following items:
Symptom

Check item

Corrective action

Unable to connect to an OPC UA server from anedge application.

Has an error occurred in the edge application?

Check the error and take corrective action.

Is the setting of an OPC UA server connected to anedge application correct?

Review the setting of the OPC UA serverconnected to the edge application.

Is there any device to which a same IP address is
set on the same network?

• Do not use a device to which a same IP address
is set on the same network.
• Set an IP address for a device without
duplication.

Are communication connections to the OPC UA
server allowed by a firewall?

Allow the communication connections toManagement Shell in the firewall setting of anindustrial PC on which Management Shell isrunning.
For the setting method, refer to the following:
Page 560 Allowing Communication
Connections between Industrial PCs

Are they correct, the OPC UA server setting
configured in Management Shell Explorer and the
security setting of the edge application?

Review these settings.

Are they correct, the OPC UA server setting
configured in Management Shell Explorer and theexpiration date of the certificate for the edge
application?

Check them and take corrective action.

Is the time when the certificate was created in theedge application later than the current system timein the environment where Management Shell
Explorer is running?

Make sure that the system time is the same in theenvironment where Management Shell Explorer isrunning and the environment where the edge
application is running, and create the certificate
again.

Is a computer name of the industrial PC on which
Management Shell is running changed?

Perform the following procedure: Start Management Shell Explorer.*1
 Review the endpoint URL of the OPC UA serverconnected to the edge application.

Is an incorrect IP address specified as the endpoint
URL of the connection destination server on theedge application side?

Perform the following procedure: Review the setting on the edge application side
if the IP address specified as the endpoint URL of
the connection destination server differs from theone set for "IP address (IPv4)" in the [Certificate
Setting] tab in the [Server Setting] tab in the "OPCUA Setting" screen of Management Shell Explorer.
 Check if the IP address in  is that of anindustrial PC on which Management Shell isrunning (IP address of a network adapter that canbe accessed from the edge application side), andcorrect it if necessary.

Is an IP address specified as the endpoint URL of
the connection destination server and a proxy
server used on the edge application side?

When a proxy server is not required for the IP
address of an industrial PC on which Management
Shell is running, exclude it from the proxy settings
in the internet options by the following procedure: Select [Internet Options] in the control panel ofWindows.
 Click the [Connections] tab.
 Click the [LAN settings] button.
 Click the [Advanced] button.
 Specify the IP address specified as the endpoint
URL in "Exceptions."

Does the number of applications connected toManagement Shell exceed the maximum numberof connectable ones?

Check the number for "Number of connected" inthe "OPC UA Diagnosis" screen. If it reaches its
maximum number, reduce the number ofapplications connected to the OPC UA server.
Page 341 OPC UA diagnosis

356

11 TROUBLESHOOTING
11.4 Troubleshooting by Symptom

SymptomCheck item

Corrective action

Fails to add monitoring target items and change
their settings in an edge application.

Is there enough free space in the memory of theindustrial PC on which Management Shell isrunning?

• Reduce the number of monitoring target items in
the edge application.
• Close other applications on the industrial PC on
which Management Shell is running to secure
free space.
• Increase the memory of the industrial PC on
which Management Shell is running.

Is a resource that can be monitored specified?

Specify a resource that can be monitored.

Has an error occurred in an access target device ofthe target data tag resource?

• Check the error and take corrective action.
• Check the status of the access target device andthe communication route with the device.

Is a data collector installed?

Reinstall the data collector.

Has an error occurred in a data collector?

Take corrective action according to the contents
displayed in the "Error Information List" screen.

Is a data collector that does not support the datareading function set for an access target device ofa data tag resource to be monitored?

Set a data collector that supports the data reading
function for the access target device of the data tag
resource to be monitored.

A value set in an edge application is not applied tothe setting value of a data tag resource in a data
model.

Has an error occurred in an access target device ofthe target data tag resource?

Check the error and take corrective action.

Data in a resource cannot be read or written
properly in an edge application.*2

Has a data model been changed in Management
Shell Explorer after the information of the data
model was acquired in the edge application?

Reacquire the information of the data model in theedge application.

A setting value of a data tag resource in a data
model is not updated.

11

Does the resource specified in the edge application
exist in Management Shell?

A timeout occurs when a value is acquired.

*1*2

Is the resource set as a monitoring target deleted
from Management Shell?

• Delete the monitoring target item in which anerror occurs from all edge applications.
• Restart Management Shell by the following
procedure: Select [Management Shell]  [Management
Shell Stop].
 Select [Management Shell]  [Management
Shell Start].

Is the information on the resource set as amonitoring target changed in Management Shell?

If an error occurs in an internal data tag resource(operation) set as a monitoring target item, openthe "Operation Expression Setting" screen toreview the setting.

Does an access target device of a data tag
resource reference a data tag resource ofManagement Shell installed in an industrial PC
being used?

Review the configuration so that the data tag
resource of Management Shell is not referenced.

The settings are rebuilt.
If changing a data model in Management Shell Explorer after acquiring the information of the data model, an error may occur or data inanother data tag resource may be read or written depending on changed contents.

Troubleshooting on component tree editing
Check the following items:
Symptom

Check item

Corrective action

Display contents are not displayed in thecomponent tree window.

Is Management Shell running?

• Start Management Shell by the following
procedure: Select [Management Shell]  [Management
Shell Start].
• If it is not solved after performing the above
procedure, perform either of the following
operations:
Import a setting file. (Select [Management Shell] [Import].)Return the setting to the default. (Select[Management Shell]  [Delete All].)

11 TROUBLESHOOTING
11.4 Troubleshooting by Symptom

357

SymptomCheck item

Corrective action

Unable to open the component tree edit dialog.

Does an error message appear when thecomponent tree edit dialog is displayed?

• Restart the industrial PC.
• Reinstall Edgecross Basic Software.
• Restart Management Shell by either of thefollowing procedures:
When Management Shell is stopped
 Select [Management Shell]  [Management
Shell Start].
When Management Shell is running Select [Management Shell]  [Management
Shell Stop].
 Select [Management Shell]  [Management
Shell Start].

Unable to register the component tree.

Is Management Shell running?

Discard the edited contents, and start Management
Shell by the following procedure after closing thecomponent tree edit dialog.
 Select [Management Shell]  [Management
Shell Start].

Are there sufficient memory and system resourceson the industrial PC?

• Close unnecessary applications.
• Restart the industrial PC.

Is a file other than an image file selected?

Select a image file.

Does a user have the access right to a selected
file?

• Perform the following procedure: Right-click the selected file.
 Select [Properties], and click the [Security] tab.
 Click the [Edit] button.
 Click the name of a logged in user.
 Select the checkbox under "Allow" for"Permissions."

Are there sufficient memory and system resourceson the industrial PC?

• Close unnecessary applications.
• Restart the industrial PC.

Is a file in a copy destination directory selected?
(Copy destination directory: (installation destination
folder for Edgecross Basic Software)\Management
Shell\Explorer\icon)

Specify a file other than one in a copy destination
directory.

Fails to add an icon.

358

11 TROUBLESHOOTING
11.4 Troubleshooting by Symptom

Troubleshooting on resource list editing
Check the following items:
Symptom

Check item

Corrective action

Display contents are not displayed in the resource
list window.

Is Management Shell running?

• Start Management Shell by the following
procedure: Select [Management Shell]  [Management
Shell Start].
• If it is not solved after performing the above
procedure, perform either of the following
operations:
Import a setting file. (Select [Management Shell] [Import].)Return the setting to the default. (Select[Management Shell]  [Delete All].)

A file does not open even when double-clicking thefile resource.

Is a file set for the resource?

Set a file for the resource.
Page 245 Editing file resource properties

Is a tool required for starting a file installed?

Install a tool required for starting a file.

Is a tool required for starting a file set as a program
to open a file in Windows?

Set a program to open a file in Windows by thefollowing procedure: Right-click a file to open.
 Click [Open with]  [Choose another app].
 Select a program to open a file, click the [OK]button.

Does a user have the access right to the selected
file?

Perform the following procedure: Right-click the selected file.
 Select [Properties], and click the [Security] tab.
 Click the [Edit] button.
 Click the name of a logged in user.
 Select the checkbox under "Allow" for"Permissions."

Is a file in a shared folder set?

• Check the connection route for any problems.
• Perform user authentication required to accessthe shared folder.

Are there sufficient memory and system resourceson the industrial PC?

• Close unnecessary applications.
• Restart the industrial PC.

Does a user have the access right to the selected
folder?

Perform the following procedure: Right-click the selected folder.
 Select [Properties], and click the [Security] tab.
 Click the [Edit] button.
 Click the name of a logged in user.
 Select the checkbox under "Allow" for"Permissions."

Is a shared folder set?

• Check the connection route for any problems.
• Perform user authentication required to accessthe shared folder.

Are there sufficient memory and system resourceson the industrial PC?

• Close unnecessary applications.
• Restart the industrial PC.

Unable to open the resource list edit dialog.

Does an error message appear when the resource
list edit dialog is displayed?

• Restart the industrial PC.
• Reinstall Edgecross Basic Software.
• Restart Management Shell by either of thefollowing procedures:
When Management Shell is stopped
 Select [Management Shell]  [Management
Shell Start].
When Management Shell is running Select [Management Shell]  [Management
Shell Stop].
 Select [Management Shell]  [Management
Shell Start].

Unable to add a resource.

Does the number of resources in the resource list
edit dialog reach the upper limit (1000)?

Delete unnecessary resources.
Page 254 Deleting a resource

A folder does not open even when double-clicking
the folder resource.

11 TROUBLESHOOTING
11.4 Troubleshooting by Symptom

11

359

SymptomCheck item

Corrective action

Unable to register a resource.

Is Management Shell running?

Discard the edited contents, and start Management
Shell by the following procedure after closing theresource list edit dialog.
 Select [Management Shell]  [Management
Shell Start].

Are there sufficient memory and system resourceson the industrial PC?

• Close unnecessary applications.
• Restart the industrial PC.

Does the number of resources in the resource list
edit dialog reach the upper limit (1000)?

Delete unnecessary resources.
Page 254 Deleting a resource

Does the following error message appear when
adding a data tag resource?
'Unable to confirm parameter editing because thefollowing warning has been reported during thecheck performed by the data collector.'• Check the data collector name and error code in
the message.
• Check the error cause in the manual for the datacollector, and take corrective action accordingly.
• Reinstall the data collector as necessary.

Is the latest version of data collector used?

• Install the latest version of the data collector.
• If the above operation does not solve theproblem, contact the developer of the datacollector.

Unable to add a data tag resource.

After editing the location setting of a data tag
resource, a message appears indicating that thesetting cannot be saved. In addition,
troubleshooting described in the message does not
solve the problem.

360

11 TROUBLESHOOTING
11.4 Troubleshooting by Symptom

Troubleshooting on display language switching
Check the following items:
Symptom

Check item

Corrective action

The display language is not switched.

Has Management Shell Explorer been restarted
after switching the display language?

Restart Management Shell Explorer.

Is "Match Windows display language(recommended)" selected under "Format" in the[Formats] tab in the screen displayed by selecting[Change date, time, or number formats] in thecontrol panel of Windows?

Select "Match Windows display language(recommended)" under "Format."11

Troubleshooting on the one-shot collection function
Check the following items:
Symptom

Check item

Corrective action

Unable to browse a saved file.

Is the encryption attribute enabled for the savedestination folder?

• Change the save destination folder to anotherone with the encryption attribute disabled.
• Open the file with the user account used forstarting Management Shell Explorer.
• Import the certificate.
For the import procedure, refer to the following:
Page 72 Procedure for browsing files with auser account other than a specified one

Fails to save a file.
(A file saving error or an accumulating file error
occurs.)Is the network disconnected and reconnectedduring operation?

• Check if the network is disconnected.
• Set a local folder as the save destination folder.

A saved file is lost.

Are the settings of the file name prefix and the savedestination folder same as those of Real-time Flow
Manager?

Change the save destination folder or the file nameprefix.

Does the number of saved files in the savedestination folder exceed its upper limit?

• Increase the maximum number of saved files.
• Move the saved file.
• Change the save destination folder or the filename prefix.

The operating status does not switch to RUN.

Are there a large number of files or folders in the
save destination folder?

• Change the save destination folder.
• Move or delete files/folders in the savedestination folder.

No change in a value of a monitoring target
resource is detected.
(Saving processing is not performed/a value of a
notification target resource does not change to '0.')

Has the value of the monitoring target resourcechanged?

Check if the value of the monitoring target resource
has changed in the data tag resource monitor.
Page 207 Monitoring and changing current
values of data tag resources

Is the value of the monitoring target resourcechanged frequently?

After changing the value of the monitoring target
resource, wait for a while and change the value
again.

Is the operation delayed due to high load on thesystem?

Reduce the load on Windows, such as closing
other applications.

Is the operating status RUN?

• Check if the operating status is RUN when thevalue of the monitoring target resource changes.
• After the value of the monitoring target resourcechanges, check if the operating status isswitched to STOP before an event is reported.

Has the value of the monitoring target resourcechanged during data saving?

Check that the saving is completed, then change
the value of the monitoring target resource.

Has an error occurred in Management Shell?

Take corrective action according to the contents
displayed in the "Error Information List" screen.
Page 343 Displaying error information in a list

Fails to read/write a data tag resource.

Has the data tag resource been deleted during
operation (including a case in which it is deleted
once then created again)?

Stop the operation and set the data tag resource
again.

Fails to save (INSERT) data to a database.

Is the connection setting for the databaseconfigured correctly?

Review the ODBC setting and the DB saving
setting for the one-shot collection function. Also,check the ODBC error code in the detailed
information in the "Error Details" screen of the oneshot collection setting, and take corrective action.

11 TROUBLESHOOTING
11.4 Troubleshooting by Symptom361

SymptomCheck item

Corrective action

Incorrect data is stored in a DB.

Is the access table setting configured in the saving
setting different from the table setting configured in
the DB?

Output the DDL file and create the table in the DB
again.

Does the access table setting configured in thesaving setting overlap with the access target tableof another application?

Change the access table setting, then output the
DDL file and create the table in the DB again.

Troubleshooting on using a data collector and IT gateway
Check the following items:
Symptom

Check item

Corrective action

The following error occurs:• Data collector service corruption
error (error code: 5021H)

Is an access target device setting
updated after updating a datacollector?

Update the version of a data collector for an access target device setting byperforming either of the following operations:• Start Management Shell Explorer.
• Click the [Update to Latest State] button in the "Data collector List" screen ofManagement Shell Explorer running.
When the confirmation message indicating whether to update the version
appears, select [Yes]. Then, restart Management Shell.
If the same error occurs again after the operation, the data collector may becorrupted. In this case, contact the developer of the data collector.

The following error occurs:• IT Gateway service corruption error(error code: 5030H)

Is an IT gateway setting updated after
updating an IT gateway?

Update the version of an IT gateway for an IT gateway setting by performing
either of the following operations:• Start Management Shell Explorer.
• Click the [Update to Latest State] button in the "IT Gateway List" screen ofManagement Shell Explorer running.
When the confirmation message indicating whether to update the version
appears, select [Yes]. Then, restart Management Shell.
If the same error occurs again after the operation, the IT gateway may becorrupted. In this case, contact the developer of the IT gateway.

A file/folder cannot be accessed
Refer to the following:
Page 350 A file/folder cannot be accessed

362

11 TROUBLESHOOTING
11.4 Troubleshooting by Symptom

CSV File Data collector
Check the following items:
Symptom

Check item

Corrective action

CSV File Data collector does notstart.

Does the execution file
(CSVReader.exe) of CSV File Data
collector exist in the following folder?
• (Installation destination of
Edgecross Basic
Software)\Management
Shell\Service\binInstall the latest version of Edgecross Basic Software.

Is the number of units of data set in
Real-time Flow Designer different
from that of columns in the monitoringtarget file?

Match the number of columns between a collection data definition file and themonitoring target file.

Is a data type set in Real-time Flow
Designer different from the data
contents of the monitoring target file?

Match the data type in the collection data definition file with the data contentsof the monitoring target file.

Is a file name prefix set in Real-time
Flow Designer different from theprefix of the monitoring target filestored in the monitoring folder?

Match the file name prefix set in Real-time Flow Designer with the data
contents of the monitoring target file.

Is the type of a file set in Real-time
Flow Designer different from theextension of the monitoring target filestored in the monitoring folder?

Match the type (CSV file or text file) of the file set in Real-time Flow Designerwith the extension of the monitoring target file.

Are the prefix and the subsequentcharacter string of the name of themonitoring target file stored in themonitoring folder delimited by '_'?

Delimit the file name prefix and the other character strings by '_.'(Example) LOG_00000001.csv

Is the monitoring target file opened inanother Windows process?

Close the open monitoring target file.

Is the read-only attribute enabled forthe monitoring target file?

Disable the read-only attribute.

Is the monitoring target file with a sizeof 0 bytes?

Delete the monitoring target file with a size of 0 bytes from the monitoring
folder.

Is the encryption attribute enabled forthe monitoring folder set in Real-time
Flow Designer?

Change the monitoring folder to another one with the encryption attributedisabled.

Is a data type outside the collection
target used?

Use a data type that can be collected.

Fails to collect a monitoring target
file.

Data is not collected even when amonitoring target file is stored in amonitoring folder.

Some data is not collected.

11

11 TROUBLESHOOTING
11.4 Troubleshooting by Symptom

363

Management Shell Data collector
Troubleshooting on the Management Shell Data collector startup
Check the following item:
Symptom

Check item

Corrective action

Management Shell Data collector is
not recognized at the EdgecrossBasic Software start.

Does a signed-in user who started
Edgecross Basic Software have theaccess right to a folder in which
Management Shell Data collector isstored?

• Sign in as a user with the access right to the folder in which Management
Shell Data collector is stored, and start Edgecross Basic Software.
• Grant the user access to the folder in which Management Shell Data
collector is stored.

Troubleshooting on data collection
Check the following items:
Symptom

Check item

Corrective action

Fails to connect with Management
Shell.

Is any of the following settingschanged in the OPC UA setting inManagement Shell Explorer?
• "End point URL" in the [Connection
Setting] tab• "Security Policy" in the [Connection
Setting] tab• "Security Mode" in the [Connection
Setting] tab

Configure all the access target device settings again in Real-time Flow
Designer, then apply the settings to Real-time Flow Manager.

Is any setting other than the following
ones changed in the OPC UA settingin Management Shell Explorer?
• "End point URL" in the [Connection
Setting] tab• "Security Policy" in the [Connection
Setting] tab• "Security Mode" in the [Connection
Setting] tab

Reconfigure any of the access target device settings in Real-time Flow
Designer, then switch Real-time Flow Manager to RUN again.

Is a setting file of Edgecross Basic
Software imported in anotherindustrial PC?

Configure all the access target device settings again in Real-time Flow
Designer, then apply the settings to Real-time Flow Manager.

Is the date and time in an industrial
PC changed?

• Reconfigure any of the access target device settings in Real-time Flow
Designer, then switch Real-time Flow Manager to RUN again.
• If the above operation does not solve the problem, perform the following
procedure: Change and apply the settings other than the following ones in the OPC
UA setting in Management Shell Explorer.
• "End point URL" in the [Connection Setting] tab• "Security Policy" in the [Connection Setting] tab• "Security Mode" in the [Connection Setting] tab Reconfigure any of the access target device settings in Real-time Flow
Designer, then switch Real-time Flow Manager to RUN again.

364

11 TROUBLESHOOTING
11.4 Troubleshooting by Symptom

SymptomCheck item

Corrective action

Fails to connect with Management
Shell.

Is Real-time Flow Manager switchedto the RUN state while Management
Shell is stopped, or is Management
Shell stopped while Real-time Flow
Manager is in RUN?

Start Management Shell, then switch Real-time Flow Manager to RUN again.

Is the maximum number ofapplications connectable toManagement Shell reached?

Reduce the number of connected applications.

Is Management Shell temporarily
stopped? (Is the "Data model import"
screen displayed?)

Close the "Data model import" screen, then switch Real-time Flow Manager to
RUN again.

Is the creation status changed to "Notcreated" due to an error caused whenclicking the [Creation] button eventhough an access target device
setting with "Already created"displayed in the connection
information is reconfigured?
(After that, "Already created" hasnever been displayed in any of theaccess target device settings.)

Reconfigure any of the access target device settings properly in Real-time
Flow Designer, then switch Real-time Flow Manager to RUN again.

A collection cycle is exceeded.

Does the maximum collection
processing time of a collection
processing time event exceed thecollection cycle?

• Review the collection setting to reduce the load on the system (lengthen thecollection cycle or reduce the number of data collection points, etc.).
• Reduce the load on Windows, such as closing other applications.

The time (time stamp) of collected
data does not match the collection
cycle.

Is the current time changed by theautomatic time adjustment of
Windows?

Set "Set time automatically" to OFF in the "Date & time" setting in Windows.

Is the current time in Windowschanged?

Do not change the current time in Windows.

11

Troubleshooting on Edgecross Basic Software
Check the following item:
Symptom

Check item

Corrective action

An error caused by Management
Shell Data collector has been
detected in Edgecross Basic
Software.

Has a data collector startup error
been detected in Edgecross Basic
Software?

Reinstall Edgecross Basic Software since the file may have been moved ordeleted.

11 TROUBLESHOOTING
11.4 Troubleshooting by Symptom

365

11.5

Error Code List

This section shows the codes for errors that occur in Edgecross Basic Software.

Codes for errors that occur in Real-time Flow Manager
The following table shows the codes for errors that occur in Real-time Flow Manager.
Error
code

Error name

Error description

Corrective action

5020H

Real-Time Flow Manager
timeout

The response of Real-time Flow Manager for
RUN operation delays. Failed to start Realtime Flow Manager, Data collector, or the IT
Gateway within the specified time.

• Please check if there is any other error.
• Please review the collection cycle, number of collected data,and processing contents to reduce the load.
• If the industrial PC enters the sleep or pause mode, please close
other applications that control the sleep or pause mode. Please
do not perform operations that enter the sleep mode.
• Please reduce the load on Windows by closing otherapplications.
• If the Target Device setting No. or the Data collector file name isdisplayed in the detail information, please contact the developerof Data collector.
• If the IT Gateway setting No. or the IT Gateway file name isdisplayed in the detail information, please contact the developerof the IT Gateway.

5021H

Data Collector damagederror

The Data Collector service file is corrupted or
the Data Collector version stored at the Realtime Flow Manager parameter setting isinconsistent with the currently stored Data
Collector version.

• After storing the Data collector file again according to themanual of Data collector where the problem occurred, specify
Data collector again on the Target Device setting screen of Realtime Flow Designer, and then apply the setting.
• If the same error occurs again, please contact the developer ofData collector.

5022H

Data Collector startup error

No execution file of Data collector exists.

Please store the Data collector execution file again according to
the manual of Data collector where the problem occurred.

5023H

Data Collector error
completion

Data collector has stopped the operation.

• Please check if there is any other error.
• If the same error occurs again, please contact the developer ofData collector.

5024H

Real-time flow manager
internal communication
timeout

Timeout occurred in the internal
communication of the real-time flow manager.

• Please reduce the load on Windows by closing otherapplications.
• Please revise the collection cycle, the number of collection dataor processing contents in order to lower the load.
• Please check if there is any other error.
• If the industrial PC enters the sleep or pause mode, please close
other applications that control the sleep or pause mode. Please
do not perform operations that enter the sleep mode.

5025H

Real-Time Flow Manager
timeout

The response of Real-time Flow Manager for
STOP operation delays. Failed to stop Realtime Flow Manager, Data collector, or the IT
Gateway within the specified time.

• Please check if there is any other error.
• If the industrial PC enters the sleep or pause mode, please close
other applications that control the sleep or pause mode. Please
do not perform operations that enter the sleep mode.
• Please reduce the load on Windows by closing otherapplications.
• If the Target Device setting No. or the Data collector file name isdisplayed in the detail information, please contact the developerof Data collector.
• If the IT Gateway setting No. or the IT Gateway file name isdisplayed in the detail information, please contact the developerof the IT Gateway.

5026H

Data collector internal
communication timeout

A timeout occurred in the internal
communication of Data collector.

• Please reduce the load on Windows by closing otherapplications.
• Please revise the collection cycle, the number of collection dataor processing contents in order to lower the load.
• Please eliminate other currently occurring errors.
• If the industrial PC enters the sleep or pause mode, please close
other applications that control the sleep or pause mode. Please
do not perform operations that enter the sleep mode.
• If the same error occurs again, please contact the developer ofData collector.

366

11 TROUBLESHOOTING
11.5 Error Code List

Errorcode

Error name

Error description

Corrective action

5027H

IT Gateway corruption
error

The IT Gateway file is corrupted, or theversion of the IT Gateway stored at the Realtime Flow Manager Parameter setting and theone of the IT Gateway currently stored do notmatch.

• After storing the IT Gateway file again according to the manualof the IT Gateway where the problem occurred, specify the IT
Gateway again on the IT Gateway setting screen of Real-time
Flow Designer, and then apply the setting.
• If the same error occurs again, please contact the developer of
the IT Gateway.

5028H

IT Gateway startup error

No execution file of the IT Gateway exists.

Please store the IT Gateway execution file again according to themanual of the IT Gateway where the problem occurred.

5029H

IT Gateway error
completion

The IT Gateway has stopped the operation.

• Please check if there is any other error.
• If the same error occurs again, please contact the developer of
the IT Gateway.

502AH

IT Gateway internal
communication timeout

A timeout occurred in the internal
communication of the IT Gateway.

• Please reduce the load on Windows by closing otherapplications.
• Please revise the collection cycle, the number of collection dataor processing contents in order to lower the load.
• Please eliminate other currently occurring errors.
• If the industrial PC enters the sleep or pause mode, please close
other applications that control the sleep or pause mode. Please
do not perform operations that enter the sleep mode.
• If the same error occurs again, please contact the developer of
the IT Gateway.

502BH

Internal communication
error

Real-time Flow Manager has failed tocommunicate with Data collector.

• Please check if there is any other error.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• If the same error occurs again, please contact the developer ofData collector.

502CH

Resource contention error

Resource contention has occurred between
Real-time Flow Manager and otherapplications.

• Please close other applications.
• Please restart the industrial PC running this product.

502DH

Out of memory error

There is not enough memory available toexecute this operation.

• Please close other applications.
• Please restart the industrial PC running this product.
• If the same error occurs again, please contact the developer ofData collector.

502EH

Internal communication
error

Real-time Flow Manager has failed tocommunicate with the IT Gateway.

• Please check if there is any other error.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• If the same error occurs again, please contact the developer of
the IT Gateway.

502FH

Resource contention error

Resource contention has occurred between
Real-time Flow Manager and otherapplications.

• Please close other applications.
• Please restart the industrial PC running this product.

5030H

Out of memory error

There is not enough memory available toexecute this operation.

• Please close other applications.
• Please restart the industrial PC running this product.
• If the same error occurs again, please contact the developer of
the IT Gateway.

5050H

Real-Time Flow Designercommunication error

The Real-Time Flow Manager could notallocate the port number to use forcommunication with the Real-Time Flow
Designer.

Confirm that there is enough available communication port number
and restart the Real-Time Flow Manager.

5070H

Status memory update
error

An error occurred in the status memory
update processing.

• Please check if there is any other error.
• Please review the collection cycle, number of collected data,and processing contents to reduce the load.
• Please reduce the load on Windows by closing otherapplications.

50A8H

Error in Real-Time Flow
Manager Parameter

Real-Time Flow Manager Parameter has notbeen written, or is damaged.

• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• Please delete unnecessary files to allocate free space.

50A9H

Error in Real-Time Flow
Manager Parameter

Real-Time Flow Manager Parameter has notbeen written, or is damaged.

• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• Please delete unnecessary files to allocate free space.

50AAH

Error in Real-Time Flow
Manager Parameter

Real-Time Flow Manager Parameters that are
written were created by an old version of theReal-Time Flow Designer.

Please create Real-time Flow Manager Parameter by Real-time
Flow Designer with the same version as Real-time Flow Manager,
and then apply the setting.

11 TROUBLESHOOTING
11.5 Error Code List

11

367

Errorcode

Error name

Error description

Corrective action

50ABH

Real-time Flow Manager
Parameter read error

Real-time Flow Manager parameter setting isinvalid.

Please review the settings for the problem function of the Process
Flow information of the parameter acquisition error which is output
subsequently.

5100H

Real-time flow manager
internal communication
timeout

Timeout occurred in the internal
communication of the real-time flow manager.

• Please check if there is any other error.
• Please review the collection cycle, number of collected data,and processing contents to reduce the load.
• Please reduce the load on Windows by closing otherapplications.

5128H

Process data buffer
overflow

Data buffering has overflowed.

• Please revise the collection cycle, the number of collection dataor processing contents in order to lower the load.
• Please consider in specifying a deterrence period in postdiagnosis feedback setting.
• Please reduce the load on Windows by closing otherapplications.

51D4H

Data Collector startup error

An error occurred in the startup processing of
Data collector.

• Please check if an error is registered from Data collector where
the problem occurred. If the error is registered, please executethe measure described in the error details.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Data collector.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer ofData collector.

51D5H

Data collector collection
data send error

An error occurred in the collection data send
processing of Data collector.

• Please check if an error is registered from Data collector where
the problem occurred. If the error is registered, please executethe measure described in the error details.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Data collector.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer ofData collector.

51D6H

Data collector collection
data send error

An error occurred in the collection data send
processing of Data collector.

• Please check if an error is registered from Data collector where
the problem occurred. If the error is registered, please executethe measure described in the error details.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Data collector.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer ofData collector.

51D7H

Data collector accessrequest check error

An error occurred in the access request checkprocessing of Data collector.

• Please check if an error is registered from Data collector where
the problem occurred. If the error is registered, please executethe measure described in the error details.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Data collector.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer ofData collector.

51D8H

Data collector accessrequest acquisition error

An error occurred in the access request
acquisition processing of Data collector.

• Please check if an error is registered from Data collector where
the problem occurred. If the error is registered, please executethe measure described in the error details.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Data collector.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer ofData collector.

368

11 TROUBLESHOOTING
11.5 Error Code List

Errorcode

Error name

Error description

Corrective action

51D9H

Data collector accessrequest acquisition error

An error occurred in the access request
acquisition processing of Data collector.

• Please check if an error is registered from Data collector where
the problem occurred. If the error is registered, please executethe measure described in the error details.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Data collector.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer ofData collector.

51DAH

Data collector accessresult report error

An error occurred in the access result report
processing of Data collector.

• Please check if an error is registered from Data collector where
the problem occurred. If the error is registered, please executethe measure described in the error details.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Data collector.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer ofData collector.

51DBH

Data collector accessresult report error

An error occurred in the access result report
processing of Data collector.

• Please check if an error is registered from Data collector where
the problem occurred. If the error is registered, please executethe measure described in the error details.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Data collector.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer ofData collector.

51DCH

Data collector error report
failureThe error report processing of Data collector
failed.

• Please check if an error is registered from Data collector where
the problem occurred. If the error is registered, please executethe measure described in the error details.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Data collector.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer ofData collector.

51DDH

Data collector
communication status
report error

An error occurred in the communication status
report processing of Data collector.

• Please check if an error is registered from Data collector where
the problem occurred. If the error is registered, please executethe measure described in the error details.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Data collector.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer ofData collector.

51DEH

Process data buffer
overflow

Data buffering has overflowed.

• Please revise the collection cycle, the number of collection dataor processing contents in order to lower the load.
• Please reduce the load on Windows by closing otherapplications.

51DFH

Out of memory error

There is not enough memory available toexecute this operation.

• Please close other applications.
• Please restart the industrial PC running this product.

51E1H

Data collector parameterread error

Failed to read the character code of the Data
collector parameter.

• Please check if an error is registered from Data collector where
the problem occurred. If the error is registered, please executethe measure described in the error details.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Data collector.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer ofData collector.

11 TROUBLESHOOTING
11.5 Error Code List

11

369

Errorcode

Error name

Error description

Corrective action

51E2H

Data collector event reporterror

An error occurred in the event report
processing of Data collector.

• Please check if an error is registered from Data collector where
the problem occurred. If the error is registered, please executethe measure described in the error details.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Data collector.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer ofData collector.

51E3H

Character error outside
specification range

Character string acquired from Data collector
contains characters out of the specification.

• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Data collector.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer ofData collector.

51E4H

Error exceeding number ofcharacters

The number of characters in the string
acquired from Data collector exceeds the
maximum number.

• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Data collector.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer ofData collector.

51E5H

Data collector error event
information read error

Failed to read the detail information of theerror report or event report from Data
collector.

• Please check if an error is registered from Data collector where
the problem occurred. If the error is registered, please executethe measure described in the error details.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Data collector.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer ofData collector.

51E6H

Internal process error

An error occurred in the communication
processing with the Data Collector.

• Please check if there is any other error.
• Please reduce the load on Windows by closing otherapplications.

51E7H

Data collector setting error

Real-time Flow Manager Parameter isdamaged.

Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.

5239H

CSV file data collector
setting error

The Monitoring Folder setting is incorrect.

There is an error in the setting of the monitoring folder, so please
review it.

5240H

CSV File Data collector
error

There is an error in the collection data setting.

• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

5241H

CSV File Data collector
error

Failed to delete the CSV file/text file that was
successfully read.

• Please check whether the CSV file/text file can be deleted.
• Please check whether other applications or others areaccessing the CSV file/text file stored in the monitoring folder.
• Please check whether the CSV file/text file moved during
operation.
• When the remote shared folder is used, please check whether
there is any problem in the connection path of the network. Also,
please reduce the load on the network by reducing thefrequency of accessing the connection destination.

5242H

CSV File Data collector
error

Failed to move the CSV file/text file that could
not be read to the error folder.

• Please check whether the CSV file/text file can be moved.
• Please check whether other applications or others areaccessing the CSV file/text file stored in the monitoring folder.
• Please check whether the CSV file/text file moved during
operation.
• When the remote shared folder is used, please check whether
there is any problem in the connection path of the network. Also,
please reduce the load on the network by reducing thefrequency of accessing the connection destination.

370

11 TROUBLESHOOTING
11.5 Error Code List

Errorcode

Error name

Error description

Corrective action

5243H

CSV File Data collector
error

The Error Folder could not be created in the
Monitoring Folder.

• Please check the access right or others of the monitoring folder.
• When the remote shared folder is used, please check whether
there is any problem in the connection path of the network. Also,
please reduce the load on the network by reducing thefrequency of accessing the connection destination.

5244H

CSV File Data collector
error

Failed to read the Monitoring Folder.

• Please review the Process Flow setting.
• Please check the access right or others of the monitoring folder.
• Please check whether other applications or others areaccessing the CSV file/text file stored in the monitoring folder.
• Please check whether there is a CSV file/text file that cannot beread or written from or to the monitoring folder.
• When the remote shared folder is used, please check whether
there is any problem in the connection path of the network andwhether the network drive is specified. Also, please reduce theload on the network by reducing the frequency of accessing theconnection destination.

5245H

CSV File Data collector
error

Failed to read the CSV file/text file due to theerror in it.

• Please make sure that the data type and number of columns set
in the CSV file/text file collection data definition file are correct.
• Please check whether there is data outside the data type range
in the CSV file/text file.
• Please check whether there are any lines that have insufficientnumber of data in the CSV file/text file.
• Please check the character code of the CSV file/text file.
• Please check the delimiter in the CSV file/text file.

5246H

CSV File Data collector
error

Failed to read the CSV file/text file due to theerror in its date column.

Please review the date column of the CSV file/text file since there
is an error.

5247H

CSV File Data collector
error

Failed to acquire the number of records in the
CSV file/text file.

• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

5248H

CSV File Data collector
error

The number of data in the CSV file/text file isinvalid.

• Please check the number of data per record in the CSV file/text
file.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• If the same error occurs again, please consult the EdgecrossConsortium.

5310H

Error in Data Extraction
setting

Real-time Flow Manager Parameter isdamaged.

Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.

5311H

Error in Data Extraction
setting

Real-time Flow Manager Parameter isdamaged.

Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.

5313H

Error in execution of output
process of Data
Modification Plug-in

An error occurred during execution of theoutput process of Data Modification Plug-in.

• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5314H

Exception error in theinitialization process of
Data Modification Plug-in

An exception occurred during the initialization
process of Data Modification Plug-in.

• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5315H

Timeout error during theinitialization process of
Data Modification Plug-in

There is no response from the initialization
process of Data Modification Plug-in.

• Please reduce the load on Windows by closing otherapplications.
• Please restart the industrial PC running this product.
• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

11 TROUBLESHOOTING
11.5 Error Code List

11

371

Errorcode

Error name

Error description

Corrective action

5316H

Failure in the initialization
process of Data
Modification Plug-in

The initialization and acquisition processes ofData Modification Plug-in has failed.

• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5317H

Mismatch error in thenumber of input data
columns for Data
Modification Plug-in

The number of input data columns for Data
Modification Plug-in is different from thenumber of input data columns for the RealTime Flow Designer.

• Please use Real-time Flow Designer to reinstall Plug-in andperform the modification setting.
• If the same error occurs again, please contact the developer of
Plug-in.

5318H

Mismatch error in thenumber of output data
columns for Data
Modification Plug-in

The number of output data columns for Data
Modification Plug-in is different from thenumber of output data columns for the RealTime Flow Designer.

• Please use Real-time Flow Designer to reinstall Plug-in andperform the modification setting.
• If the same error occurs again, please contact the developer of
Plug-in.

5319H

Timeout error during thetermination process of
Data Modification Plug-in

There is no response from the termination
process of Data Modification Plug-in.

• Please reduce the load on Windows by closing otherapplications.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

531AH

Failure in the termination
process of Data
Modification Plug-in

Termination Process of Data Modification
Plug-in has failed.

• Please reduce the load on Windows by closing otherapplications.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

531BH

Duplication of Data
Modification Plug-in error

Program names of the Data Modification Plugin are duplicated.

Please delete Plug-in whose program name is duplicate from theplug-in storage folder.

531CH

Failure in the acquisition
process of Data
Modification Plug-in

Failure occurred in the process to acquire theprogram name of Data Modification Plug-in.

• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

531DH

Timeout error during theacquisition process of Data
Modification Plug-in

There is no response from the process toacquire the program name of Data
Modification Plug-in.

• Please review the collection cycle, number of collected data,and processing contents to reduce the load.
• Please reduce the load on Windows by closing otherapplications.
• Please restart the industrial PC running this product.
• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

531EH

Error in the number ofcharacters for Data
Modification Plug-in name

The number of characters in the program
name of Data Modification Plug-in exceeds
the number of settable characters in Real-time
Flow Designer.

• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

531FH

Exception error in thetermination process of
Data Modification Plug-in

An exception occurred during the termination
process of Data Modification Plug-in.

• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5321H

Data Modification Plug-in
Input data string exceeded
number error

The number of input data columns for Data
Modification Plug-in has exceeded its
specified upper limit.

• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5322H

Total number of bytes in
the input data column for
Data Modification Plug-in
exceeded error

Total number of bytes in the input data column
for Data Modification Plug-in has exceeded its
specified upper limit.

• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

372

11 TROUBLESHOOTING
11.5 Error Code List

Errorcode

Error name

Error description

Corrective action

5323H

Number of output data
columns for Data
Modification Plug-in
exceeded error

The number of output data columns for Data
Modification Plug-in has exceeded its
specified upper limit.

• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5324H

Total number of bytes in
the output data column for
Data Modification Plug-in
exceeded error

Total number of bytes in the output data
column for Data Modification Plug-in has
exceeded its specified upper limit.

• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5325H

Data Modification Plug-in
storage error

Data Modification Plug-in does not exist in thestorage folder.
Or, the storage folder cannot be accessed.

• Please place the Data Modification Plug-in in the Plug-in storage
folder.
• Please check whether the Plug-in storage folder exists.
• Please check the access right of the Plug-in storage folder.

5327H

Timeout error while
reading Data Modification
Plug-in

There is no response when reading the Plugin.

• Please review the collection cycle, number of collected data,and processing contents to reduce the load.
• Please reduce the load on Windows by closing otherapplications.
• Please restart the industrial PC running this product.
• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5328H

Number of Data
Modification Plug-in
exceeded error

The number of plug-in programs (number ofclasses) has exceeded its specified upper
limit.

• Please reinstall Plug-in.
• If the same error occurs again, please contact the developer of
Plug-in.

532BH

Failed to acquire the input
data column for Data
Modification Plug-in

Failed to acquire the input data column
information for Data Modification Plug-in.

• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

532CH

Timeout error while
acquiring the input data
column for Data
Modification Plug-in

There was no response when attempting toacquire the input data column information for
Data Modification Plug-in.

• Please review the collection cycle, number of collected data,and processing contents to reduce the load.
• Please reduce the load on Windows by closing otherapplications.
• Please restart the industrial PC running this product.
• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

532DH

Error in the setting for the
input data column for Data
Modification Plug-in

The input data column for Data Modification
Plug-in has not been set.

• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

532FH

Data type of the input data
column information for
Data Modification Plug-in
incorrect error

Data type of the input data column information
for Data Modification Plug-in is incorrect.

• Please use Real-time Flow Designer to reinstall Data
Modification Plug-in and perform the modification setting.
• If the same error occurs again, please contact the developer of
Plug-in.

5330H

Data name of the input
data column information
for Data Modification Plugin incorrect error

Data name of the input data column
information for Data Modification Plug-in isincorrect.

• Please use Real-time Flow Designer to reinstall Data
Modification Plug-in and perform the modification setting.
• If the same error occurs again, please contact the developer of
Plug-in.

5331H

Exception error inprocessing of Data
Modification Plug-in

An exception occurred during the modification
process of Data Modification Plug-in.

• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5332H

Timeout error while
processing Data
Modification Plug-in

There is no response from the modification
process of Data Modification Plug-in.

• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

11 TROUBLESHOOTING
11.5 Error Code List

11

373

Errorcode

Error name

Error description

Corrective action

5333H

Failure in processing of
Data Modification Plug-in

Failure occurred in the modification process of
Data Modification Plug-in.

• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5334H

Failure in the acquisition
process of the output data
column for Data
Modification Plug-in

Failed to acquire the output data column
information for Data Modification Plug-in.

• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5335H

Timeout error during theacquisition process of theoutput data column for
Data Modification Plug-in

There was no response when attempting toacquire the output data column information for
Data Modification Plug-in.

• Please review the collection cycle, number of collected data,and processing contents to reduce the load.
• Please reduce the load on Windows by closing otherapplications.
• Please restart the industrial PC running this product.
• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5336H

Error in the setting for the
output data column for
Data Modification Plug-in

The output data column for Data Modification
Plug-in has not been set.

• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5338H

Data type of the output
data column information
for Data Modification Plugin incorrect error

Data type of the output data column
information for Data Modification Plug-in isincorrect.

• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5339H

Data name of the output
data column information
for Data Modification Plugin incorrect error

Data name of the output data column
information for Data Modification Plug-in isincorrect.

• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

533AH

Exception error in theacquisition process of Data
Modification Plug-in nameAn exception occurred when reading the Data
Modification Plug-in.

• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

533BH

Number of stored Data
Modification Plug-in
exceeded error

The number of Plug-in stored in the Plug-in
storage folder has exceeded the storage
upper limit.

The number of Plug-in in the Plug-in storage folder should be
below or equal to 100.

533CH

NULL Output data of Data
Modification Plug-in error

NULL is included in the output data
information in the modification processing of
Data Modification Plug-in.

• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

533DH

Mismatch error in thenumber of output data for
Data Modification Plug-in

The number of output data in the modification
process of Data Modification Plug-in isdifferent from the number of output data that is
set in the Real-Time Flow Designer.

• Please use Real-time Flow Designer to reinstall Plug-in andperform the modification setting.
• If the same error occurs again, please contact the developer of
Plug-in.

533EH

Mismatch error in the
output data type for Data
Modification Plug-in

Data type of the output data information in themodification process of Data Modification
Plug-in is different from the data type of output
data information that is set in the Real-Time
Flow Designer.

• Please use Real-time Flow Designer to reinstall Plug-in andperform the modification setting.
• If the same error occurs again, please contact the developer of
Plug-in.

533FH

NULL value error in the
output data for Data
Modification Plug-in

NULL is included in the output data
information in the modification processing of
Data Modification Plug-in.

• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5340H

Error in execution of output
process of Data
Modification Plug-in

An error occurred during execution of theoutput process of Data Modification Plug-in.

• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5341H

Mismatch error in thenumber of output data
columns for Data
Modification Plug-in

The number of output data in the modification
process of Data Modification Plug-in isdifferent from the number of output data that is
set in the Real-Time Flow Designer.

• Please use Real-time Flow Designer to reinstall Plug-in andperform the modification setting.
• If the same error occurs again, please contact the developer of
Plug-in.

374

11 TROUBLESHOOTING
11.5 Error Code List

Errorcode

Error name

Error description

Corrective action

5342H

Column number for Data
Modification Plug-in out ofrange error

Column number that is out of the specified
range has been set.

• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5343HTime stamp for Data
Modification Plug-in out ofrange error

Time stamp that is out of the specified range
has been set.

• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5344H

Data processing record
line number acquisition
processing timeout error

Data processing There is no response fromthe record number acquisition process.

• Please reduce the load on Windows by closing otherapplications.
• Please restart the industrial PC running this product.
• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5345H

Data processing record
row count acquisition
processing failure

Data processing record line number
acquisition processing failed.

• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5350H

Character string data
modification setting error

Real-time Flow Manager Parameter isdamaged.

Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.

5351H

Error exceeding number ofcharacters

The number of characters after the character
string data modification exceeds the upper
limit.

Please check the data where the error has occurred and review
the setting of the character string data modification so that the
number of characters after the character string data modification
does not exceed the upper limit.

5352H

Character string extraction
acquisition error

Failed to extract the character string.

Please check the data where the error has occurred and review
the setting of the character string data modification so that theextraction start position is within the range of the character string
before modified.

5353H

Character string data
modification status
memory update error

Failed to update the data modification type or
the number of modification failure records ofthe character string data modification.

• Please check if there is any other error.
• Please review the collection cycle, number of collected data,and processing contents to reduce the load.
• Please reduce the load on Windows by closing otherapplications.

5510H

Error in Data Diagnosis
Plug-in setting

Real-time Flow Manager Parameter isdamaged.

Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.

5511H

Error in Data Diagnosis
Plug-in setting

Real-time Flow Manager Parameter isdamaged.

Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.

5513H

Timeout error while
processing Data Diagnosis
Plug-in

There is no response from the diagnosis
process of Data Diagnosis Plug-in.

• Please revise the collection cycle, the number of collection dataor processing contents in order to lower the load.
• Please reduce the load on Windows by closing otherapplications.
• If the same error occurs again, please contact the developer of
Plug-in.

5516H

Failure in processing of
Data Diagnosis Plug-in

Failure occurred in the diagnosis process of
Data Diagnosis Plug-in.

• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5517H

Error in storage of Data
Diagnosis Plug-in

Data Diagnosis Plug-in does not exist in thestorage folder.
Or, the storage folder cannot be accessed.

• Please place the Data Diagnosis Plug-in in the Plug-in storage
folder.
• Please check whether the Plug-in storage folder exists.
• Please check the access right of the Plug-in storage folder.

5518H

Failed to acquire the input
data column for Data
Diagnosis Plug-in

Failed to acquire the input data column
information for Data Diagnosis Plug-in.

• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

11 TROUBLESHOOTING
11.5 Error Code List

11

375

Errorcode

Error name

Error description

Corrective action

5519H

Timeout error while
acquiring the input data
column for Data Diagnosis
Plug-in

There was no response when attempting toacquire the input data column information for
Data Diagnosis Plug-in.

• Please review the collection cycle, number of collected data,and processing contents to reduce the load.
• Please reduce the load on Windows by closing otherapplications.
• Please restart the industrial PC running this product.
• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

551AH

Failure in the acquisition
process of the output data
column for Data Diagnosis
Plug-in

Failed to acquire the output data column
information for Data Diagnosis Plug-in.

• Please review the collection cycle, number of collected data,and processing contents to reduce the load.
• Please reduce the load on Windows by closing otherapplications.
• Please restart the industrial PC running this product.
• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

551BH

Timeout error during theacquisition process of theoutput data column for
Data Diagnosis Plug-in

There was no response when attempting toacquire the output data column information for
Data Diagnosis Plug-in.

• Please review the collection cycle, number of collected data,and processing contents to reduce the load.
• Please reduce the load on Windows by closing otherapplications.
• Please restart the industrial PC running this product.
• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

551CH

Error in the setting for the
output data column for
Data Diagnosis Plug-in

The output data column for Data Diagnosis
Plug-in has not been set.

• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

551DH

Mismatch error in the
output data type for Data
Diagnosis Plug-in

Data type of the output data information in the
diagnosis process of Data Diagnosis Plug-in
is different from the data type of output data
information that is set in the Real-Time Flow
Designer.

• Please use Real-time Flow Designer to reinstall Plug-in andperform the diagnosis setting.
• If the same error occurs again, please contact the developer of
Plug-in.

551EH

Data name of the output
data column information
for Data Diagnosis Plug-in
incorrect error

Data name of the output data column
information for Data Diagnosis Plug-in isincorrect.

• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

551FH

Error in the setting for the
input data column for Data
Diagnosis Plug-in

The input data column for Data Diagnosis
Plug-in has not been set.

• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5520H

Data type of the input data
column information for
Data Diagnosis Plug-in
incorrect error

Data type of the input data column information
for Data Diagnosis Plug-in is incorrect.

• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5521H

Data name of the input
data column information
for Data Diagnosis Plug-in
incorrect error

Data name of the input data column
information for Data Diagnosis Plug-in isincorrect.

• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5523H

Timeout error while
reading Data Diagnosis
Plug-in

There is no response when reading the Plugin.

• Please review the collection cycle, number of collected data,and processing contents to reduce the load.
• Please reduce the load on Windows by closing otherapplications.
• Please restart the industrial PC running this product.
• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5524H

Number of stored Data
Diagnosis Plug-in
exceeded error

The number of Plug-in stored in the Plug-in
storage folder has exceeded the storage
upper limit.

The number of Plug-in in the Plug-in storage folder should be
below or equal to 100.

376

11 TROUBLESHOOTING
11.5 Error Code List

Errorcode

Error name

Error description

Corrective action

5525H

Exception error in theacquisition process of Data
Diagnosis Plug-in nameAn exception occurred when reading the Data
Diagnosis Plug-in.

• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5527H

Number of input data
columns for Data
Diagnosis Plug-in
exceeded error

The number of input data columns for Data
Diagnosis Plug-in has exceeded its specified
upper limit.

• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5528H

Total number of bytes in
the input data column for
Data Diagnosis Plug-in
exceeded error

Total number of bytes in the input data column
for Data Diagnosis Plug-in has exceeded its
specified upper limit.

• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5529H

Number of output data
columns for Data
Diagnosis Plug-in
exceeded error

The number of output data columns for Data
Diagnosis Plug-in has exceeded its specified
upper limit.

• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

552AH

Total number of bytes in
the output data column for
Data Diagnosis Plug-in
exceeded error

Total number of bytes in the output data
column for Data Diagnosis Plug-in has
exceeded its specified upper limit.

• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

552BH

Exception error inprocessing of Data
Diagnosis Plug-in

An exception occurred during the diagnosis
process of Data Diagnosis Plug-in.

• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

552CH

Error in execution of output
process of Data Diagnosis
Plug-inAn error occurred during execution of theoutput process of Data Diagnosis Plug-in.

• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

552DH

Exception error in theinitialization process of
Data Diagnosis Plug-in

An exception occurred during the initialization
process of Data Diagnosis Plug-in.

• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

552EH

Timed out during theinitialization process of
Data Diagnosis Plug-in
error

There is no response from the initialization
process of Data Diagnosis Plug-in.

• Please reduce the load on Windows by closing otherapplications.
• Please restart the industrial PC running this product.
• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

552FH

Failure in the initialization
process of Data Diagnosis
Plug-in

The initialization and acquisition processes ofData Diagnosis Plug-in has failed.

• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5530H

Mismatch error in thenumber of input data
columns for Data
Diagnosis Plug-in

The number of input data columns for Data
Diagnosis Plug-in is different from the numberof input data columns for the Real-Time Flow
Designer.

• Please use Real-time Flow Designer to reinstall Plug-in andperform the diagnosis setting.
• If the same error occurs again, please contact the developer of
Plug-in.

5531H

Mismatch error in thenumber of output data
columns for Data
Diagnosis Plug-in

The number of output data columns for Data
Diagnosis Plug-in is different from the numberof output data columns for the Real-Time Flow
Designer.

• Please use Real-time Flow Designer to reinstall Plug-in andperform the diagnosis setting.
• If the same error occurs again, please contact the developer of
Plug-in.

11 TROUBLESHOOTING
11.5 Error Code List

11

377

Errorcode

Error name

Error description

Corrective action

5532H

Timeout error during thetermination process of
Data Diagnosis Plug-in

There is no response from the termination
process of Data Diagnosis Plug-in.

• Please reduce the load on Windows by closing otherapplications.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5533H

Failure in the termination
process of Data Diagnosis
Plug-inTermination Process of Data Diagnosis Plugin has failed.

• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5534H

Duplication of Data
Diagnosis Plug-in error

Program names of the Data Diagnosis Plug-in
are duplicated.

Please delete Plug-in whose program name is duplicate from theplug-in storage folder.

5535H

Failure in the acquisition
process of Data Diagnosis
Plug-in

Failure occurred in the process to acquire theprogram name of Data Diagnosis Plug-in.

• Please review the collection cycle, number of collected data,and processing contents to reduce the load.
• Please reduce the load on Windows by closing otherapplications.
• Please restart the industrial PC running this product.
• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5536H

Timeout error during theacquisition process of Data
Diagnosis Plug-in

There is no response from the process toacquire the program name of Data Diagnosis
Plug-in.

• Please review the collection cycle, number of collected data,and processing contents to reduce the load.
• Please reduce the load on Windows by closing otherapplications.
• Please restart the industrial PC running this product.
• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5537H

Error in the number ofcharacters for Data
Diagnosis Plug-in name

Number of characters of the program name of
the Data Diagnosis Plug-in is incorrect.

• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5538H

Exception error in thetermination process of
Data Diagnosis Plug-in

An exception occurred during the termination
process of Data Diagnosis Plug-in.

• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5539H

Number of Data Diagnosis
Plug-in exceeded error

The number of plug-in (number of classes)
has exceeded its specified upper limit.

• Please reinstall Plug-in.
• If the same error occurs again, please contact the developer of
Plug-in.

553AH

NULL Output data of Data
Diagnosis Plug-in error

Output data received from Data Diagnosis
Plug-in is NULL.

• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

553BH

Mismatch error in thenumber of output data for
Data Diagnosis Plug-in

The number of output data in the diagnosis
process of Data Diagnosis Plug-in is different
from the number of output data that has been
set in the Real-Time Flow Designer.

• Please use Real-time Flow Designer to reinstall Plug-in andperform the diagnosis setting.
• If the same error occurs again, please contact the developer of
Plug-in.

553CH

NULL value in the output
data for Data Diagnosis
Plug-in error

NULL value is included in the output data
information in the diagnosis process of Data
Diagnosis Plug-in.

• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

553DH

Error in execution of output
process of Data Diagnosis
Plug-inAn error occurred during execution of theoutput process of Data Diagnosis Plug-in.

• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

378

11 TROUBLESHOOTING
11.5 Error Code List

Errorcode

Error name

Error description

Corrective action

553EH

Mismatch error in thenumber of output data
columns for Data
Diagnosis Plug-in

The number of output data columns in the
diagnosis process of Data Diagnosis Plug-in
is different from the number of output data
columns that has been set in the Real-Time
Flow Designer.

• Please use Real-time Flow Designer to reinstall Plug-in andperform the diagnosis setting.
• If the same error occurs again, please contact the developer of
Plug-in.

553FH

Mismatch error in the
output data type for Data
Diagnosis Plug-in

Data type of the output data information in the
diagnosis process of Data Diagnosis Plug-in
is different from the data type of output data
information that is set in the Real-Time Flow
Designer.

• Please use Real-time Flow Designer to reinstall Plug-in andperform the diagnosis setting.
• If the same error occurs again, please contact the developer of
Plug-in.

5540H

Column number for Data
Diagnosis Plug-in out ofrange error

Column number that is out of the specified
range has been set.

• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5541HTime stamp for Data
Diagnosis Plug-in out ofrange error

Time stamp that is out of the specified range
has been set.

• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5542H

Data diagnostic record line
number acquisition
processing timeout error

There is no response from the data diagnostic
record line number acquisition processing.

• Please reduce the load on Windows by closing otherapplications.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5543H

Data diagnostic record
count acquisition process
failureThe data diagnostic record count acquisition
process failed.

• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please reinstall Plug-in.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
Plug-in.

5600H

Real-time flow manager
parameter error[datadiagnosis (sending)]

An incompatible version of the Real-time Flow
Manager parameter was written.

Please create Real-time Flow Manager Parameter by Real-time
Flow Designer with the same version as Real-time Flow Manager,
and then apply the setting.

5601H

MQTT communication
error[data diagnosis(sending)]

An error occurred in the MQTT
communication.

• Please check whether there is any problem in the MQTT
communication settings, and restart the operation of Real-time
Flow Manager.
• For the settings to specify the user authentication information,please check whether the user name and password are correct.
• For the settings to encrypt the communication, please check if
the hostname of the destination setting matches the one of thecertificate authority certificate.
• For the settings to encrypt the communication, please check
whether the certificate authority certificate, client certificate, andclient secret key are correct. Also, please check whether they
are in the specified path, whether there is any problem in theconnection path, and whether the network drive is specified.
• Please check whether the MQTT communication settings matchthe MQTT broker settings.
• Please check whether any client ID of Real-time Flow Manager
is duplicate in the connection destination MQTT broker.
• Please reduce the load on the network by reducing thefrequency of accessing the connection destination.

5602H

MQTT edge application
status structureabnormality[data diagnosis(sending)]

The structure of the edge application status
data is invalid.

• Please review the setting of Edge Application Diagnosis.
• Please review the setting of the edge application. Then, pleaserestart the edge application and start the Real-time Flow
Manager operation again.
• If the same error occurs again, please contact the developer ofthe Edge Application.

11 TROUBLESHOOTING
11.5 Error Code List

11

379

Errorcode

Error name

Error description

Corrective action

5603H

MQTT broker connection
failure[data diagnosis(sending)]

The real-time flow manager can not connect
with the MQTT broker.

• Please check whether the MQTT broker is operating properly.
• Please check whether there is any problem in thecommunication setting/communication path with the MQTT
broker.
• For the settings to specify the user authentication information,please check whether the user name and password are correct.
• Please reduce the load on the network by reducing thefrequency of accessing the connection destination.

5604H

MQTT edge application
stop error[data diagnosis(sending)]

The edge application is stopped, or the realtime flow manager operation started before
the edge application started up.

• Please check whether the publishing data definition file output
with the edge application diagnosis setting and the publishingdata definition file specified by the edge application match.
• Please stop the operation of the edge application and Real-time
Flow Manager. Then, please start the edge application before
starting the Real-time Flow Manager operation.
• Make sure there is no problem with the communication between
the edge application and the MQTT broker.
• If the same error occurs again, please contact the developer ofthe Edge Application.

5605H

MQTT edge applicationinternal error[datadiagnosis (sending)]

An internal error of the edge application was
detected.

• Restart the Edge Application and restart the Real-time Flow
Manager operation.
• If the same error occurs again, please contact the developer ofthe Edge Application.

5606H

MQTT edge application
definition mismatch[datadiagnosis (sending)]

The contents of the distribution data from theedge application and the distribution data
definition file do not match.

• Please check whether the publishing data definition file output
with the edge application diagnosis setting and the publishingdata definition file specified by the edge application match.
• Please stop the operation of the edge application and Real-time
Flow Manager. Then, please start the edge application before
starting the Real-time Flow Manager operation.
• If the same error occurs again, please contact the developer ofthe Edge Application.

5607H

MQTT edge applicationdelivery data erasureerror[data diagnosis(sending)]

Loss of delivery data was detected in edge
application.

• Restart the Edge Application and restart the Real-time Flow
Manager operation.
• If the same error occurs again, please contact the developer ofthe Edge Application.

5608H

MQTT delivery data row
count out of range
error[data diagnosis(sending)]

The fixed number of rows notified from theedge application is out of range.

• Please review the setting of the edge application. Then, pleaserestart the edge application and start the Real-time Flow
Manager operation again.
• If the same error occurs again, please contact the developer ofthe Edge Application.

5609H

MQTT transmission data
overflow error[datadiagnosis (sending)]

A buffer overflow occurred waiting fortransmission of delivery data to be sent to theedge application.

• Please check if there is any other error.
• Please review the collection cycle, number of collected data,and processing contents to reduce the load.
• Please reduce the load on Windows by closing otherapplications.
• Please reduce the load on the network by reducing thefrequency of accessing the connection destination.

560AH

MQTT edge application
incompatible version
detection error[datadiagnosis (sending)]

The Real-time Flow Manager detected that it
is a non-compliant version Edge Application.

Please check the version of the Edgecross Basic Software orEdge Application.

560BH

MQTT broker encryption
connection failure[datadiagnosis (sending)]

Unable to establish the encryption connection
with the MQTT broker.

• Please check if the hostname of the destination setting matches
the one of the certificate authority certificate.
• Please check if the certificate authority certificate is correct.
• For the settings to encrypt the communication using the client
authentication method, please check if the client certificate andclient secret key are correct.
• Please check if the certificate authority certificate set in the
MQTT broker is correct.

5632H

Real-time flow manager
parameter error[datadiagnosis (receiving)]

An incompatible version of the Real-time Flow
Manager parameter was written.

Please create Real-time Flow Manager Parameter by Real-time
Flow Designer with the same version as Real-time Flow Manager,
and then apply the setting.

380

11 TROUBLESHOOTING
11.5 Error Code List

Errorcode

Error name

Error description

Corrective action

5633H

MQTT communication
error[data diagnosis(receiving)]

An error occurred in the MQTT
communication.

• Please check whether there is any problem in the MQTT
communication settings, and restart the operation of Real-time
Flow Manager.
• For the settings to specify the user authentication information,please check whether the user name and password are correct.
• For the settings to encrypt the communication, please check if
the hostname of the destination setting matches the one of thecertificate authority certificate.
• For the settings to encrypt the communication, please check
whether the certificate authority certificate, client certificate, andclient secret key are correct. Also, please check whether they
are in the specified path, whether there is any problem in theconnection path, and whether the network drive is specified.
• Please check whether the MQTT communication settings matchthe MQTT broker settings.
• Please reduce the load on the network by reducing thefrequency of accessing the connection destination.

5634H

MQTT broker connection
failure[data diagnosis(receiving)]

The real-time flow manager can not connect
with the MQTT broker.

• Please check whether the MQTT broker is operating properly.
• Please check whether there is any problem in thecommunication setting/communication path with the MQTT
broker.
• For the settings to specify the user authentication information,please check whether the user name and password are correct.
• Please reduce the load on the network by reducing thefrequency of accessing the connection destination.

5635H

MQTT response data
structure abnormality

The structure of the response data received
from the edge application is illegal.

• Please review the setting of Edge Application Diagnosis.
• Please review the setting of the edge application. Then, pleaserestart the edge application and start the Real-time Flow
Manager operation again.
• If the same error occurs again, please contact the developer ofthe Edge Application.

5636H

MQTT response data
erasure error

Response data from the edge application was
lost.
This error can be output
Breaking of response data continuity becauseof restart or disconnect of the edge application
can cause this error.

• Please stop the operation of the edge application and Real-time
Flow Manager. Then, please start the edge application before
starting the Real-time Flow Manager operation.
• Make sure there is no problem with the communication between
the edge application and the MQTT broker.
• Please review the collection cycle, number of collected data,and processing contents to reduce the load.
• Please reduce the load on Windows by closing otherapplications.
• Please reduce the load on the network by reducing thefrequency of accessing the connection destination.

5637H

MQTT response data edge
application incorrect

The client ID of the response data received
from the edge application is invalid.

• Please review the setting of the edge application. Then, pleaserestart the edge application and start the Real-time Flow
Manager operation again.
• If the same error occurs again, please contact the developer ofthe Edge Application.

5638H

MQTT response data
definition mismatch

The contents of the response data received
from the edge application and the response
data definition file do not match.

• Please review the setting of the edge application. Then, pleaserestart the edge application and start the Real-time Flow
Manager operation again.
• If the same error occurs again, please contact the developer ofthe Edge Application.

5639H

MQTT response data
version incompatible error

Received response data of unsupported
version.

Please check the version of the Edgecross Basic Software orEdge Application.

563AH

MQTT response data outof range specification
character error

The response data contains charactersoutside the specification range.

• Please review the setting of the edge application. Then, pleaserestart the edge application and start the Real-time Flow
Manager operation again.
• If the same error occurs again, please contact the developer ofthe Edge Application.

563BH

MQTT broker encryption
connection failure[datadiagnosis (receiving)]

Unable to establish the encryption connection
with the MQTT broker.

• Please check if the hostname of the destination setting matches
the one of the certificate authority certificate.
• Please check if the certificate authority certificate is correct.
• For the settings to encrypt the communication using the client
authentication method, please check if the client certificate andclient secret key are correct.
• Please check if the certificate authority certificate set in the
MQTT broker is correct.

11 TROUBLESHOOTING
11.5 Error Code List

11

381

Errorcode

Error name

Error description

Corrective action

5700H

Error in Feedback
execution setting

Real-time Flow Manager Parameter isdamaged.

Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.

5703H

Feedback execution
request excessive error

The requested Feedback was unable to be
executed, because the execution process
could not catch up with the Feedback
executing frequency.

Please set the deterrence period to reduce the feedback execution
frequency.

5704H

Data collector response
incorrect error

An invalid value was used for the Data
Collector's response to the Feedback request.

• Please check if an error is registered from Data collector where
the problem occurred. If the error is registered, please executethe measure described in the error details.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Data collector.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer ofData collector.

5705H

Feedback response
timeout error

Response from the Data Collector timed out
when the Feedback was executed.

• Please lengthen the Response timeout time of the Command
Option.
• Please review the setting of the Edge Application.
• Please reduce the load on Windows by closing otherapplications.

5706H

Feedback function start
failureThe real-time flow manager failed to start theoperation of the feedback function.

• Please check if there is any other error.
• Please reduce the load on Windows by closing otherapplications.

57A1H

Program argument check
error

Invalid character is included in argument usedin program execution feedback.

Make sure that the argument of program execution feedback iscorrectly entered.

57A2H

Reserved word out ofrange error

Arguments used in program execution
feedback include reserved words outside therange.

• Check whether the range of reserved words specified in theargument of program execution feedback is correct.
• Check whether the number of reserved words specified in theargument of program execution feedback exceeds the upper
limit.

57A3H

Specified program
execution failure error

The program specified for program execution
feedback could not be executed.

• Please check whether the setting of the program to be executedby the program execution feedback is correct.
• Please check the access right to the program to be executed by
the program execution feedback.
• When the remote shared folder is used, please check whether
there is any problem in the connection path of the network andwhether the network drive is specified. Also, please reduce theload on the network by reducing the frequency of accessing theconnection destination.

57A4H

Character error outside
specification range

Characters outside the specification range areincluded in response data handled byprogram execution feedback.

Please check the response data handled by program execution
feedback.

5802H

Error in edge applicationcooperation

Failure occurred in the process to judge theoperation of edge application.

• Check whether the edge application correctly reads the CSV
file, which is output by the File Saving setting.
• Check that the file name and the save destination folder is set
correctly.

5809H

Edge Application
Diagnosis error

The monitor target folder path is incorrect.

• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

580AH

Edge Application
Diagnosis error

The file name prefix is invalid.

• Please review the setting of Edge Application Diagnosis.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• If the same error occurs again, please consult the EdgecrossConsortium.

580BH

Edge Application
Diagnosis error

Real-Time Flow Manager Parameter isincorrect.

• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

382

11 TROUBLESHOOTING
11.5 Error Code List

Errorcode

Error name

Error description

Corrective action

580DH

Edge Application
Diagnosis error

The response data is invalid.

• Please review and correct the response data setting.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• If the same error occurs again, please consult the EdgecrossConsortium.

580EH

Edge Application
Diagnosis error

Failed to delete the response data file thatwas successfully read.

• Please check whether the same prefix is used for multiple flows.
• Please check whether other applications, etc., are making
access to the Response Data File that is stored in the monitoring
folder.
• Please check whether the Response Data File had been moved
during operation.
• Please check whether the Response Data File can be deleted.

580FH

Edge Application
Diagnosis error

Collection-failed Response Data file could not
be loaded into error folder.

• Please check whether other applications, etc., are making
access to the Response Data File that is stored in the monitoring
folder.
• Please check whether the Response Data File had been moved
during operation.
• Please check whether the Response Data File can be moved.

5810H

Edge Application
Diagnosis error

The Error Folder could not be created in the
Monitoring Folder.

Please check the access right or others of the monitoring folder.

5811H

Edge Application
Diagnosis error

Failed to read the Monitoring Folder.

• Please review the Process Flow setting.
• Please check the access right or others of the monitoring folder.
• Please check whether other applications, etc., are making
access to the CSV file that is stored in the monitoring folder.
• Please check, in the monitoring folder, whether there is a CSV
file that cannot be read or written.

5812H

Edge Application
Diagnosis error

Reading failed due to abnormality in the CSV
file.

• Please make sure that the data type and number of columns set
in the Response Data file collection data definition file is correct.
• Please check whether there is data outside the data type range
in the Response Data file.
• Please check if there are any lines in the Response Data file thatare short of data.
• Please check the character code of the Response Data file.
• Please review the setting of the Edge Application.
• If the same error occurs again, please contact the developer ofthe Edge Application.

5813H

Edge Application
Diagnosis error

Reading failed due to abnormality in the Date
Column of Response Data file.

Please review the date column of the Response Data file because
there is an error.

5814H

Edge Application
Diagnosis error

Failed to acquire number of records in
Response Data file.

• Please review and correct the response data setting.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• If the same error occurs again, please consult the EdgecrossConsortium.

5815H

Edge Application
Diagnosis error

The number of data in the Response Data fileis invalid.

• Please review and correct the response data setting.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• If the same error occurs again, please consult the EdgecrossConsortium.

5860H

File Saving error

Program execution has failed after switching
file.

• Please check whether the path of the program to be executed iscorrect.
• Please check the access right to the program to be executed.
• When the remote shared folder is used, please check whether
there is any problem in the connection path of the network andwhether the network drive is specified. Also, please reduce theload on the network by reducing the frequency of accessing theconnection destination.

11 TROUBLESHOOTING
11.5 Error Code List

11

383

Errorcode

Error name

Error description

Corrective action

5861H

File Saving error

Historical Data Definition File or Historical
Data File could not be output.

• Please check whether the setting for the save destination folder
is correct.
• Please check the access authority of the save destination folder.
• Please check whether the number of files in the save destination
folder has exceeded the upper limit.
• Please check whether other applications or others areaccessing the historical data definition file in the savedestination folder.
• When the remote shared folder is used, please check whether
there is any problem in the connection path of the network andwhether the network drive is specified. Also, please reduce theload on the network by reducing the frequency of accessing theconnection destination.

5862H

File Saving error

Failed to write the file because there is notenough free space available.

Please delete unnecessary files to allocate free space.

5863H

File Saving error

Failed to write the file.

• Please review the setting so that the data size of the file to be
saved will be smaller.
• Please review the setting so that the cycles (e.g. collection
cycle) will be longer.
• Please review the save destination folder and prefix of the file
name, and set the length of the file saving path within thenumber of maximum characters.
• Please check whether the file saving setting is correct.
• When the remote shared folder is used, please check whether
there is any problem in the connection path of the network. Also,
please reduce the load on the network by reducing thefrequency of accessing the connection destination.

5864H

Saved file numbers
exceeded

Suffix of the file name of the saving file has
exceeded FFFFFFFF.

• Please change the destination folder or file name prefix.
• Delete all saved files in the Save Destination Folder.

5865H

Number of accumulated
files exceeded

The number of accumulated files has
exceeded its maximum number.

• Please check whether any stored file in the TMP folder in the
save destination folder is being accessed.
• Please change the destination folder or file name prefix.
• Please stop the operation of Real-time Flow Manager anddelete all the stored files in the TMP folder in the savedestination folder.

5866H

File Saving error

Failed to write the file with the specified user
account.

• Please check whether the user name and password of the user
account set in the file saving setting are correct.
• Please check whether there is any problem in the connection
path of the network used for authenticating user accounts. Also,
please reduce the load on the network by reducing thefrequency of accessing the connection destination.

5867H

File Saving error

Failed to save the file.
The authentication processing for the set user
account was delayed or there was not enoughmemory available to perform the internal
communication.

• Please check whether the user name and password of the user
account set in the file saving setting are correct.
• Please check whether there is any problem in the connection
path of the network used for authenticating user accounts. Also,
please reduce the load on the network by reducing thefrequency of accessing the connection destination.
• Please reduce the load on Windows by closing otherapplications.
• Please restart the industrial PC running this product.

5880H

DB setting error

DB connection setting parameter is invalid.

• Please check if the setting of DB saving is correct.
• Check the ODBC error code.

5881H

DB connection error

DB connection failed.

• Please check if the setting of DB saving is correct.
• Please check if there is any other error.
• Please review the collection cycle, number of collected data,and processing contents to reduce the load.
• Please reduce the load on Windows by closing otherapplications.

5882H

DB connection error

DB connection failed.

• Please check if the setting of DB saving is correct.
• Please make sure the ODBC settings are correct.
• Check the ODBC error code.

5883H

DB SQL execution error

Execution of SQL failed.

• Please check if the setting of DB saving is correct.
• Please check if there is any other error.
• Please review the collection cycle, number of collected data,and processing contents to reduce the load.
• Please reduce the load on Windows by closing otherapplications.

384

11 TROUBLESHOOTING
11.5 Error Code List

Errorcode

Error name

Error description

Corrective action

5884H

DB SQL execution error

Execution of SQL failed.

• Please check if the setting of DB saving is correct.
• Please make sure the ODBC settings are correct.
• Check the ODBC error code.

5885H

DB disconnection error

Failed to disconnect the DB.

• Please check if the setting of DB saving is correct.
• Please check if there is any other error.
• Please review the collection cycle, number of collected data,and processing contents to reduce the load.
• Please reduce the load on Windows by closing otherapplications.

5886H

DB disconnection error

Failed to disconnect the DB.

• Please check if the setting of DB saving is correct.
• Please make sure the ODBC settings are correct.
• Check the ODBC error code.

5887H

Data Storing / Data
Distribution processing
request excessive error

Data Storing / Data Distribution process could
not be performed because the execution
process is not catching up with request for
Data Storing / Data Distribution process.

Please review the collection cycle to reduce the frequency of Data
Storing / Data Distribution processing. Also, if there are othererrors occurring, please check them together.

5888H

DB reception of data
missing

It has received a data missing from Data
Collector.

• Please review the collection cycle, number of collected data,and processing contents to reduce the load.
• Please reduce the load on Windows by closing otherapplications.
• Please check the manual of Data collector.

588AH

IT Gateway internal
communication error

Failed to execute the internal communication
with the IT Gateway. The IT Gateway is notoperated or there is not enough memory
available to execute this operation.

• Please check if there is any other error.
• If the industrial PC enters the sleep or pause mode, please close
other applications that control the sleep or pause mode. Please
do not perform operations that enter the sleep mode.
• Please reduce the load on Windows by closing otherapplications.
• Please restart the industrial PC running this product.
• Please store the IT Gateway execution file again according to
the manual of the IT Gateway.
• If the same error occurs again, please contact the developer of
the IT Gateway.

588BH

IT Gateway internal
communication error

Failed to execute the internal communication
with the IT Gateway. The IT Gateway is notoperated or there is not enough memory
available to execute this operation.

• Please check if there is any other error.
• If the industrial PC enters the sleep or pause mode, please close
other applications that control the sleep or pause mode. Please
do not perform operations that enter the sleep mode.
• Please reduce the load on Windows by closing otherapplications.
• Please restart the industrial PC running this product.
• Please store the IT Gateway execution file again according to
the manual of the IT Gateway.
• If the same error occurs again, please contact the developer of
the IT Gateway.

588CH

Data Diagnosis processing
request excessive error

Execution process is not catching up withrequest for Data Diagnosis process.

• Please check whether error is registered from Data Diagnosis
processing. If it is registered, please take the corrective action of
the event displayed in error description.
• Please check whether Data Diagnosis processing output data.
• Please review collection cycle to lower frequency of request for
Data Diagnosis process.

588DH

Data Storing processing
request excessive error

Execution process is not catching up withrequest for Data Storing process.

• Please check whether error is registered from Data Storingprocessing. If it is registered, please take the corrective action of
the event displayed in error description.
• Please check whether Data Storing processing output data.
• Please review collection cycle to lower frequency of request for
Data Storing process.

588EH

Data Distribution
processing request
excessive error

Execution process is not catching up withrequest for Data Distribution process.

• Please check whether error is registered from Data Distribution
processing. If it is registered, please take the corrective action of
the event displayed in error description.
• Please check whether Data Distribution processing output data.
• Please review collection cycle to lower frequency of request for
Data Distribution process.

11 TROUBLESHOOTING
11.5 Error Code List

11

385

Errorcode

Error name

Error description

Corrective action

5960H

Edge Application
Diagnosis file saving error

Program execution has failed after switching
file.

• Please check whether the setting of the program to be executed
after switching the file specified in the file save setting of theedge application diagnosis is correct.
• Please check the access right to the program to be executed
after file switching.
• When the remote shared folder is used, please check whether
there is any problem in the connection path of the network andwhether the network drive is specified. Also, please reduce theload on the network by reducing the frequency of accessing theconnection destination.

5961H

Edge Application
Diagnosis file saving error

Publishing Data Definition File or Publishing
Data File could not be output.

• Please check whether the file saving setting of the edge
application diagnosis is correct.
• Please check the access authority of the save destination folder.
• Please check whether the number of files in the save destination
folder has exceeded the upper limit.
• Please check whether other applications or others areaccessing the publishing data definition file in the savedestination folder.
• When the remote shared folder is used, please check whether
there is any problem in the connection path of the network andwhether the network drive is specified. Also, please reduce theload on the network by reducing the frequency of accessing theconnection destination.

5962H

Edge Application
Diagnosis file saving error

Failed to write the file because there is notenough free space available.

Please delete unnecessary files to allocate free space.

5963H

Edge Application
Diagnosis file saving error

Failed to write the file.

• Please check whether the file saving setting of the edge
application diagnosis is correct.
• Please review the setting so that the data size of the file to be
saved will be smaller.
• Please review the setting so that the cycles (e.g. collection
cycle) will be longer.
• Please review the save destination folder and prefix of the file
name, and set the length of the file saving path within thenumber of maximum characters.
• When the remote shared folder is used, please check whether
there is any problem in the connection path of the network. Also,
please reduce the load on the network by reducing thefrequency of accessing the connection destination.

5964H

Edge Application
Diagnosis Publishing Data
File number overFile name suffix of saved file exceeded
FFFFFFFF.

• Please change the destination folder or file name prefix.
• Please delete all Publishing Data Files from the Save
Destination Folder of Edge Application Diagnostics.

5965H

Number of files being
accumulated of the Edge
Application Diagnosis overThe number of accumulated files has
exceeded its maximum number.

• Please check whether any stored file in the TMP folder in the
save destination folder is being accessed.
• Please change the destination folder or file name prefix.
• Please stop the operation of Real-time Flow Manager anddelete all the stored files in the TMP folder in the savedestination folder.

5966H

Error in edge applicationcooperation

Old file was deleted because it exceeded the
maximum number of saved files of edge
application diagnostics.

• Make sure the edge application is running.
• Make sure that the edge application is reading the CSV file
outputted by the file save setting correctly. (Is the file namecorrect? / Save the file in the correct location)• Please reconsider file switching operation setting of file savesetting.

5C00H

Real-time flow manager
parameter error[datadistribution]

An incompatible version of the Real-time Flow
Manager parameter was written.

Please create Real-time Flow Manager Parameter by Real-time
Flow Designer with the same version as Real-time Flow Manager,
and then apply the setting.

386

11 TROUBLESHOOTING
11.5 Error Code List

Errorcode

Error name

Error description

Corrective action

5C01H

MQTT communication
error[data distribution]

An error occurred in the MQTT
communication.

• Please check whether there is any problem in the MQTT
communication settings, and restart the operation of Real-time
Flow Manager.
• For the settings to specify the user authentication information,please check whether the user name and password are correct.
• For the settings to encrypt the communication, please check if
the hostname of the destination setting matches the one of thecertificate authority certificate.
• For the settings to encrypt the communication, please check
whether the certificate authority certificate, client certificate, andclient secret key are correct. Also, please check whether they
are in the specified path, whether there is any problem in theconnection path, and whether the network drive is specified.
• Please check whether the MQTT communication settings matchthe MQTT broker settings.
• Please check whether any client ID of Real-time Flow Manager
is duplicate in the connection destination MQTT broker.
• Please reduce the load on the network by reducing thefrequency of accessing the connection destination.

5C02H

MQTT edge application
status structureabnormality[datadistribution]

The structure of the edge application status
data is invalid.

• Please review the setting of Edge Application Diagnosis.
• Please review the setting of the edge application. Then, pleaserestart the edge application and start the Real-time Flow
Manager operation again.
• If the same error occurs again, please contact the developer ofthe Edge Application.

5C03H

MQTT broker connection
failure[data distribution]

The real-time flow manager can not connect
with the MQTT broker.

• Please check whether the MQTT broker is operating properly.
• Please check whether there is any problem in thecommunication setting/communication path with the MQTT
broker.
• For the settings to specify the user authentication information,please check whether the user name and password are correct.
• Please reduce the load on the network by reducing thefrequency of accessing the connection destination.

5C04H

MQTT edge application
stop error[data distribution]

The edge application is stopped, or the realtime flow manager operation started before
the edge application started up.

• Please stop the operation of the edge application and Real-time
Flow Manager. Then, please start the edge application before
starting the Real-time Flow Manager operation.
• Make sure there is no problem with the communication between
the edge application and the MQTT broker.
• If the same error occurs again, please contact the developer ofthe Edge Application.

5C05H

MQTT edge applicationinternal error[datadistribution]

An internal error of the edge application was
detected.

• Restart the Edge Application and restart the Real-time Flow
Manager operation.
• If the same error occurs again, please contact the developer ofthe Edge Application.

5C06H

MQTT edge application
definition mismatch[datadistribution]

The contents of the distribution data from theedge application and the distribution data
definition file do not match.

• Please check whether the publishing data definition file output
with the edge application diagnosis setting and the publishingdata definition file specified by the edge application match.
• Please stop the operation of the edge application and Real-time
Flow Manager. Then, please start the edge application before
starting the Real-time Flow Manager operation.
• If the same error occurs again, please contact the developer ofthe Edge Application.

5C07H

MQTT edge applicationdelivery data erasureerror[data distribution]

Loss of delivery data was detected in edge
application.

• Restart the Edge Application and restart the Real-time Flow
Manager operation.
• If the same error occurs again, please contact the developer ofthe Edge Application.

5C08H

MQTT delivery data row
count out of range
error[data distribution]

The fixed number of rows notified from theedge application is out of range.

• Please review the setting of the edge application. Then, pleaserestart the edge application and start the Real-time Flow
Manager operation again.
• If the same error occurs again, please contact the developer ofthe Edge Application.

11 TROUBLESHOOTING
11.5 Error Code List

11

387

Errorcode

Error name

Error description

Corrective action

5C09H

MQTT transmission data
overflow error[datadistribution]

A buffer overflow occurred waiting fortransmission of delivery data to be sent to theedge application.

• Please check if there is any other error.
• Please review the collection cycle, number of collected data,and processing contents to reduce the load.
• Please reduce the load on Windows by closing otherapplications.
• Please reduce the load on the network by reducing thefrequency of accessing the connection destination.

5C0AH

MQTT edge application
incompatible version
detection error[datadistribution]

The Real-time Flow Manager detected that it
is a non-compliant version Edge Application.

Please check the version of the Edgecross Basic Software orEdge Application.

5C0BH

MQTT broker encryption
connection failure[datadistribution]

Unable to establish the encryption connection
with the MQTT broker.

• Please check if the hostname of the destination setting matches
the one of the certificate authority certificate.
• Please check if the certificate authority certificate is correct.
• For the settings to encrypt the communication using the client
authentication method, please check if the client certificate andclient secret key are correct.
• Please check if the certificate authority certificate set in the
MQTT broker is correct.

5C20H

IT Gateway startup error

An error occurred in the IT Gateway start
processing.

• Please check if an error is registered from the IT Gateway where
the problem occurred. If the error is registered, please executethe measure described in the error details.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall the IT Gateway.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
the IT Gateway.

5C21H

IT Gateway
communication status
report error

An error occurred in the IT Gateway
communication status report processing.

• Please check if an error is registered from the IT Gateway where
the problem occurred. If the error is registered, please executethe measure described in the error details.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall the IT Gateway.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
the IT Gateway.

5C22H

IT Gateway error report
failureThe IT Gateway error report processing has
failed.

• Please check if an error is registered from the IT Gateway where
the problem occurred. If the error is registered, please executethe measure described in the error details.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall the IT Gateway.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
the IT Gateway.

5C23H

IT Gateway event reporterror

An error occurred in the IT Gateway event
report processing.

• Please check if an error is registered from the IT Gateway where
the problem occurred. If the error is registered, please executethe measure described in the error details.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall the IT Gateway.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
the IT Gateway.

388

11 TROUBLESHOOTING
11.5 Error Code List

Errorcode

Error name

Error description

Corrective action

5C24H

IT Gateway initializationerror

An error occurred in the IT Gateway
initialization processing.

• Please check if an error is registered from the IT Gateway where
the problem occurred. If the error is registered, please executethe measure described in the error details.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall the IT Gateway.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
the IT Gateway.

5C25H

IT Gateway parameterread error

Failed to read the character code of the IT
Gateway parameter.

• Please check if an error is registered from the IT Gateway where
the problem occurred. If the error is registered, please executethe measure described in the error details.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall the IT Gateway.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
the IT Gateway.

5C26H

IT Gateway error
information read error

Failed to read the detail information of theerror report from the IT Gateway.

• Please check if an error is registered from the IT Gateway where
the problem occurred. If the error is registered, please executethe measure described in the error details.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall the IT Gateway.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
the IT Gateway.

5C27H

IT Gateway event
information read error

Failed to read the detail information of theevent report from the IT Gateway.

• Please check if an error is registered from the IT Gateway where
the problem occurred. If the error is registered, please executethe measure described in the error details.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall the IT Gateway.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
the IT Gateway.

5C28H

IT Gateway data receptionerror

An error occurred in the IT Gateway data
reception processing.

• Please check if an error is registered from the IT Gateway where
the problem occurred. If the error is registered, please executethe measure described in the error details.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall the IT Gateway.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
the IT Gateway.

5C29H

IT Gateway status memory
update error

An error occurred in the IT Gateway status
memory update processing.

• Please reduce the load on Windows by closing otherapplications.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.

5C2AH

Internal processing error

An error occurred in the communication
processing with the IT Gateway.

• Please check if there is any other error.
• Please reduce the load on Windows by closing otherapplications.

5C2BH

Internal processing error

An error occurred in the communication
processing with the IT Gateway.

Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.

11 TROUBLESHOOTING
11.5 Error Code List

11

389

Errorcode

Error name

Error description

Corrective action

5C2CH

IT Gateway startup error

An error occurred in the IT Gateway start
processing.

• Please check if an error is registered from the IT Gateway where
the problem occurred. If the error is registered, please executethe measure described in the error details.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall the IT Gateway.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
the IT Gateway.

5C2DH

IT Gateway
communication status
report error

An error occurred in the IT Gateway
communication status report processing.

• Please check if an error is registered from the IT Gateway where
the problem occurred. If the error is registered, please executethe measure described in the error details.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall the IT Gateway.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
the IT Gateway.

5C2EH

IT Gateway error report
failureThe IT Gateway error report processing has
failed.

• Please check if an error is registered from the IT Gateway where
the problem occurred. If the error is registered, please executethe measure described in the error details.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall the IT Gateway.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
the IT Gateway.

5C2FH

IT Gateway event reporterror

An error occurred in the IT Gateway event
report processing.

• Please check if an error is registered from the IT Gateway where
the problem occurred. If the error is registered, please executethe measure described in the error details.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall the IT Gateway.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
the IT Gateway.

5C30H

IT Gateway parameterread error

Failed to read the character code of the IT
Gateway parameter.

• Please check if an error is registered from the IT Gateway where
the problem occurred. If the error is registered, please executethe measure described in the error details.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall the IT Gateway.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
the IT Gateway.

5C31H

IT Gateway error
information read error

Failed to read the detail information of theerror report from the IT Gateway.

• Please check if an error is registered from the IT Gateway where
the problem occurred. If the error is registered, please executethe measure described in the error details.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall the IT Gateway.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
the IT Gateway.

390

11 TROUBLESHOOTING
11.5 Error Code List

Errorcode

Error name

Error description

Corrective action

5C32H

IT Gateway event
information read error

Failed to read the detail information of theevent report from the IT Gateway.

• Please check if an error is registered from the IT Gateway where
the problem occurred. If the error is registered, please executethe measure described in the error details.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall the IT Gateway.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developer of
the IT Gateway.

5C33H

IT Gateway status memory
update error

An error occurred in the IT Gateway status
memory update processing.

• Please reduce the load on Windows by closing otherapplications.
• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.

5C34H

Internal processing error

An error occurred in the communication
processing with the IT Gateway.

• Please check if there is any other error.
• Please reduce the load on Windows by closing otherapplications.

5C35H

Internal processing error

An error occurred in the communication
processing with the IT Gateway.

Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.

5D00H

Event history automatic
output function Setting
error

Failed to start the operation because theformat of the event history automatic output
setting is not supported.

Please configure the event history automatic output setting again.

5D01H

Event history automatic
output function File open
error

Failed to open the event history file.

• Please check if the event history file is open.
• When a remote shared folder is set as the save destination
folder, please check if there is any problem in the connection
path of the network. Also, please reduce the load on the networkby reducing the frequency of accessing the connection
destination.
• Please check the access authority of the save destination folder.
• Please check that the event history file is not read-only.
• Please change the save destination of the event history file.
• Please restart the industrial PC running this product.

5D02H

Event history automatic
output function File saving
error

Failed to save the event history file.

• When a remote shared folder is set as the save destination
folder, please check if there is any problem in the connection
path of the network. Also, please reduce the load on the networkby reducing the frequency of accessing the connection
destination.
• Please reduce the load on the access to the storage of the savedestination folder.
• Please delete unnecessary files to allocate free space.
• Please change the save destination of the event history file.

5D03H

Event history automatic
output function File backup
error

Failed to backup the event history file.

• When a remote shared folder is set as the save destination
folder, please check if there is any problem in the connection
path of the network. Also, please reduce the load on the networkby reducing the frequency of accessing the connection
destination.
• Please reduce the load on the access to the storage of the savedestination folder.
• Please check the access authority of the save destination folder.
• Please check if any file with the same name as the backup file ofthe event history file is open.
• Please delete unnecessary files to allocate free space.

5D04H

Event history automatic
output function Memory
insufficient error

Failed to allocate the memory required for theoperation.

• Please reduce the load on Windows by closing otherapplications.
• Please restart the industrial PC running this product.

5D05H

Event history automatic
output function Memory
insufficient error

Failed to allocate the memory required for theoperation.

• Please reduce the load on Windows by closing otherapplications.
• Please restart the industrial PC running this product.

5D06H

Event history automatic
output function Internal
processing error

Failed to perform the internal processing of
the event history automatic output function.

• Please reduce the load on Windows by closing otherapplications.
• Please restart the industrial PC running this product.
• Please restart the industrial PC after reinstalling EdgecrossBasic Software.

11 TROUBLESHOOTING
11.5 Error Code List

11

391

Errorcode

Error name

Error description

Corrective action

5D07H

Event history automatic
output function Internal
processing error

Failed to perform the internal processing of
the event history automatic output function.

• Please reduce the load on Windows by closing otherapplications.
• Please restart the industrial PC running this product.
• Please restart the industrial PC after reinstalling EdgecrossBasic Software.

5D08H

Event history automatic
output function User
account authentication
setting error

Failed to authenticate the user account.

• Please review the user account setting of the save destination
folder. Then, Please apply the setting.
• Please unlock the user account.

5D09H

Event history automatic
output function Error atuser accountauthentication

Failed to execute the user accountauthentication.

Please check if there is any problem in the connection path of the
network to the remote shared folder. Also, please reduce the loadon the network by reducing the frequency of accessing theconnection destination.

5D0AH

Event history automatic
output function Eventhistory access error

Failed to acquire the event history information
because the update frequency of the event
history was high.

Please check that the event history file has been updated because
it might not be.
Please perform the following when it has not been updated.
• Please check if there is any event that occurs continuously andtake corrective action on the event.
• Please reduce the load on Windows by closing otherapplications.
• Please restart the industrial PC running this product.

6010H

System error• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6011H

System error

An error occurred in an internal processing of
the Real-Time Flow Manager.

• Please close other applications.
• Please restart the industrial PC running this product.

6012H

Real-Time Flow Manager
timeout

An error occurred in an initialization
processing of the Real-Time Flow Manager.

• Please close other applications.
• Please restart the industrial PC running this product.

6014H

System error• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6015H

Real-Time Flow Manager
communication error
between internal
processes

A communication error occurred between
internal processes of the Real-Time Flow
Manager.

• Please check if there is any other error.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6018H

Abnormal termination ofinternal process of RealTime Flow Manager

Operation of the internal process of Real-Time
Flow Manager has stopped.

• Please restart the industrial PC running this product.
• If the IPC goes to sleep / hibernation mode, please exit otherapplication controlling sleep / hibernation state. Also, please do
not conduct sleep entering operation.
• If the same error occurs again, please consult the EdgecrossConsortium.

6019H

Out of memory error

There is not enough memory available toexecute this operation.

• Please close other applications.
• Please restart the industrial PC running this product.

601AH

Resource contention error

Resource contention has occurred between
Real-time Flow Manager and otherapplications.

• Please close other applications.
• Please restart the industrial PC running this product.

6060H

Error in Real-Time Flow
Manager Parameter

Real-Time Flow Manager Parameters that are
written were created by an old version of theReal-Time Flow Designer.

Please create Real-time Flow Manager Parameter by Real-time
Flow Designer with the same version as Real-time Flow Manager,
and then apply the setting.

6061H

Error in Real-Time Flow
Manager Parameter

Unable to access to the Real-Time Flow
Manager Parameter, which is included in the
Edgecross Basic Software.

• Please restart the industrial PC running this product.
• Please reinstall the Edgecross Basic Software.

6070H

Parameter version error

Parameter whose setting is not supported by
Real-time Flow Manager is used.

Please update Edgecross Basic Software to the latest version. Or,
please create Real-time Flow Manager Parameter by Real-time
Flow Designer with the same version as Real-time Flow Manager,
and then apply the setting.

6071H

Out of memory error

There is not enough memory available toexecute this operation.

• Please close other applications.
• Please restart the industrial PC running this product.

392

11 TROUBLESHOOTING
11.5 Error Code List

Errorcode

Error name

Error description

Corrective action

6072H

Resource contention error

Resource contention has occurred between
Real-time Flow Manager and otherapplications.

• Please close other applications.
• Please restart the industrial PC running this product.

6082H

System error• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6084H

System error• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6085H

System error• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6086H

System error• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6087H

System error• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6088H

System error• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6089H

System error• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

608AH

System error• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

608BH

System error• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

608CH

System error• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

11 TROUBLESHOOTING
11.5 Error Code List

11

393

Errorcode

Error name

Error description

Corrective action

608DH

System error• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6090H

System error• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6091H

System error• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6093H

System error• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6095H

System error• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6096H

System error• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6097H

System error• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6098H

System error• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6099H

Out of memory error

There is not enough memory available toexecute this operation.

• Please close other applications.
• Please restart the industrial PC running this product.

609AH

Out of memory error

There is not enough memory available toexecute this operation.

• Please close other applications.
• Please restart the industrial PC running this product.

609BH

System error• Please restart the industrial PC running this product.
• If the same error occurs again, please consult the EdgecrossConsortium.

609CH

Resource contention error

Resource contention has occurred between
Real-time Flow Manager and otherapplications.

• Please close other applications.
• Please restart the industrial PC running this product.

609EH

System error• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

394

11 TROUBLESHOOTING
11.5 Error Code List

Errorcode

Error name

Error description

Corrective action

60B0H

Out of memory error

There is not enough memory available toexecute this operation.

• Please close other applications.
• Please restart the industrial PC running this product.

60B1H

System error• Please restart the industrial PC running this product.
• If the same error occurs again, please consult the EdgecrossConsortium.

60B2H

Resource contention error

Resource contention has occurred between
Real-time Flow Manager and otherapplications.

• Please close other applications.
• Please restart the industrial PC running this product.

60C9H

System error• Please restart the industrial PC running this product.
• If the same error occurs again, please consult the EdgecrossConsortium.

60CAH

System error• Please restart the industrial PC running this product.
• If the same error occurs again, please consult the EdgecrossConsortium.

60CBH

Out of memory error

There is not enough memory available toexecute this operation.

• Please close other applications.
• Please restart the industrial PC running this product.

60CFH

System error• Please change the setting not to use the multithread processing
by Plug-in.
• Please restart the industrial PC running this product.
• If the same error occurs again, please consult the EdgecrossConsortium.

60E0H

System error• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

60E1H

System error• Please restart the industrial PC running this product.
• If the same error occurs again, please consult the EdgecrossConsortium.

60E3H

System error• Please restart the industrial PC running this product.
• If the same error occurs again, please consult the EdgecrossConsortium.

60E7H

System error• Please restart the industrial PC running this product.
• If the same error occurs again, please consult the EdgecrossConsortium.

60ECH

Failed to register error

Since many errors occurred in a short time,error detection has failed.

After removing the cause of the error that occurred, reset thesystem of this product.

60EDH

Out of memory error

There is not enough memory available toexecute this operation.

• Please close other applications.
• Please restart the industrial PC running this product.

60EEH

Resource contention error

Resource contention has occurred between
Real-time Flow Manager and otherapplications.

• Please close other applications.
• Please restart the industrial PC running this product.

60EFH

Failed to register event

Since many events occurred in a short time,
event registration has failed.

• Please set the deterrence period to reduce the feedback
execution frequency.
• Please restart the industrial PC running this product.

60F8H

Abnormal termination ofinternal process of RealTime Flow Manager

Operation of the internal process of Real-Time
Flow Manager has stopped.

• Please restart the industrial PC running this product.
• If the same error occurs again, please consult the EdgecrossConsortium.

60F9H

Failed to start internal
process of Real-Time Flow
Manager

Failed to start the internal process of RealTime Flow Manager.

• Please delete unnecessary files to allocate free space.
• Please restart the industrial PC running this product.
• If the same error occurs again, please consult the EdgecrossConsortium.

60FAH

System error• Please restart the Industrial PC running this product.
• If the same error occurs again, please consult the EdgecrossConsortium.

6128H

Out of memory error

There is not enough memory available toexecute this operation.

• Please close other applications.
• Please restart the Industrial PC running this product.

11 TROUBLESHOOTING
11.5 Error Code List

11

395

Errorcode

Error name

Error description

Corrective action

614CH

Internal processing error• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the Industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6181H

System error

Please consult the Edgecross Consortium.

6183H

Out of memory error

There is not enough memory available toexecute this operation.

• Please close other applications.
• Please restart the Industrial PC running this product.

6250H

Initialization error

An error occurred while initializing the Data
Modification function.

• Please restart the Industrial PC running this product.
• If the same error occurs again, please consult the EdgecrossConsortium.

6251H

System error• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the Industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6253H

Out of memory error

There is not enough memory available toexecute this operation.

• Please close other applications.
• Please restart the Industrial PC running this product.

6254H

Out of memory error

There is not enough memory available toexecute this operation.

• Please close other applications.
• Please restart the industrial PC running this product.

6255H

System error• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6256H

System error• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6257H

System error• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6258H

System error• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6259H

Resource contention error

Resource contention has occurred between
Real-time Flow Manager and otherapplications.

• Please close other applications.
• Please restart the industrial PC running this product.

625AH

Resource contention error

Resource contention has occurred between
Real-time Flow Manager and otherapplications.

• Please close other applications.
• Please restart the industrial PC running this product.

6260H

System error

An error occurred in an internal processing of
the Real-Time Flow Manager.

• Please restart the industrial PC running this product.
• If the same error occurs again, please consult the EdgecrossConsortium.

6261H

Out of memory error

There is not enough memory available toexecute this operation.

• Please close other applications.
• Please restart the industrial PC running this product.
• If the same error occurs again, please consult the EdgecrossConsortium.

63D0H

Initialization error

An error occurred while initializing Data
Diagnosis.

• Please restart the industrial PC running this product.
• If the same error occurs again, please consult the EdgecrossConsortium.

396

11 TROUBLESHOOTING
11.5 Error Code List

Errorcode

Error name

Error description

Corrective action

63D1H

System error• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

63D2H

System error• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

63D3H

Out of memory error

There is not enough memory available toexecute this operation.

• Please close other applications.
• Please restart the industrial PC running this product.

63D4H

Out of memory error

There is not enough memory available toexecute this operation.

• Please close other applications.
• Please restart the industrial PC running this product.

63D5H

System error• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

63D6H

System error• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

63D7H

System error• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

63DAH

Out of memory error

There is not enough memory available toexecute this operation.

• Please close other applications.
• Please restart the industrial PC running this product.

63DBH

Resource contention error

Resource contention has occurred between
Real-time Flow Manager and otherapplications.

• Please close other applications.
• Please restart the industrial PC running this product.

63DCH

Resource contention error

Resource contention has occurred between
Real-time Flow Manager and otherapplications.

• Please close other applications.
• Please restart the industrial PC running this product.

63DDH

Resource contention error

Resource contention has occurred between
Real-time Flow Manager and otherapplications.

• Please close other applications.
• Please restart the industrial PC running this product.

63DEH

System error• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6541H

System error• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6542H

Out of memory error

There is not enough memory available toexecute this operation.

• Please close other applications.
• Please restart the industrial PC running this product.

6543HResource contention error

Resource contention has occurred between
Real-time Flow Manager and otherapplications.

• Please close other applications.
• Please restart the industrial PC running this product.

11 TROUBLESHOOTING
11.5 Error Code List

11

397

Errorcode

Error name

Error description

Corrective action

65A1H

System error• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

65A2H

System error• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

65A3H

System error• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6611H

Initialization error

Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.

6650H

System error• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• If the same error is displayed, please consult the EdgecrossConsortium.

6651H

Out of memory error

There is not enough memory available toexecute this operation.

• Please close other applications.
• Please restart the industrial PC running this product.

6652H

Out of memory error

There is not enough memory available toexecute this operation.

• Please close other applications.
• Please restart the industrial PC running this product.

6654H

System error• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• If the same error is displayed, please consult the EdgecrossConsortium.

6656H

Resource contention error

Resource contention has occurred between
Real-time Flow Manager and otherapplications.

• Please close other applications.
• Please restart the industrial PC running this product.

6670H

Out of memory error

There is not enough memory available toexecute this operation.

• Please close other applications.
• Please restart the industrial PC running this product.

6671H

System error• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6672H

System error• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6673H

Out of memory error

There is not enough memory available toexecute this operation.

• Please close other applications.
• Please restart the industrial PC running this product.

6674H

System error• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6750H

System error• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• If the same error is displayed, please consult the EdgecrossConsortium.

6751H

Out of memory error

There is not enough memory available toexecute this operation.

• Please close other applications.
• Please restart the industrial PC running this product.

398

11 TROUBLESHOOTING
11.5 Error Code List

Errorcode

Error name

Error description

Corrective action

6756H

Resource contention error

Resource contention has occurred between
Real-time Flow Manager and otherapplications.

• Please close other applications.
• Please restart the industrial PC running this product.

67C0H

System error• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

67C1H

Out of memory error

There is not enough memory available toexecute this operation.

• Please close other applications.
• Please restart the industrial PC running this product.

67E0H

Out of memory error

There is not enough memory available toexecute this operation.

• Please close other applications.
• Please restart the Industrial PC running this product.

67E1HInternal processing error• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the Industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

67E2H

Out of memory error

There is not enough memory available toexecute this operation.

• Please close other applications.
• Please restart the Industrial PC running this product.

67E3H

Internal processing error• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the Industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6C24H

System error• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• Please restart the Industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6C2AH

System error• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• Please restart the Industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6C66H

System error• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• Please restart the Industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6C77H

System error• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• Please restart the Industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6C78H

Out of memory / File write
failure error

There is not enough memory available toexecute this operation. Or, access to the file isprohibited.

• Please close other applications.
• Please release the read-only setting of the file and folder of thisproduct.
• If the file in the installation folder of this product is opened withother applications, please close it.
• Please restart the Industrial PC running this product.

6C79H

Resource contention error

Resource contention has occurred between
Real-time Flow Manager and otherapplications.

• Please close other applications.
• Please restart the Industrial PC running this product.

6C7AH

Event history file creation
failureFailed to write the file because there is notenough free space available.

Please delete unnecessary files from industrial PC where real timeflow manager is running.

11 TROUBLESHOOTING
11.5 Error Code List

11

399

Errorcode

Error name

Error description

Corrective action

6C80H

System error• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• Please restart the Industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6C81H

Out of memory error

There is not enough memory available toexecute this operation.

• Please close other applications.
• Please restart the Industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6C82H

System error• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the Industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6C83H

System error• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the Industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6C84H

System error• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the Industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6C85H

System error• Please restart the Industrial PC running this product.
• If the same error occurs again, please consult the EdgecrossConsortium.

6C86H

System error• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the Industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6C87H

System error• Please restart the Industrial PC running this product.
• If the same error occurs again, please consult the EdgecrossConsortium.

6C88H

System error• Please restart the Industrial PC running this product.
• If the same error occurs again, please consult the EdgecrossConsortium.

6C89H

System error• Please delete Process Flow where the error has occurred andcreate new Process Flow again. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6C8AH

System error• Please restart the industrial PC running this product.
• If the same error occurs, consult the Edgecross Consortium.

6D40H

System error• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6D41H

Out of memory error

There is not enough memory available toexecute this operation.

• Please close other applications.
• Please restart the industrial PC running this product.

400

11 TROUBLESHOOTING
11.5 Error Code List

Errorcode

Error name

Error description

Corrective action

6D50H

System error• Please delete all Process Flow and create new Process Flowagain. Then, please apply the setting.
• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the EdgecrossConsortium.

6D51H

Out of memory error

There is not enough memory available toexecute this operation.

• Please close other applications.
• Please restart the industrial PC running this product.

11

11 TROUBLESHOOTING
11.5 Error Code List

401

Codes for errors that occur in Management Shell
The following table shows the codes for errors that occur in Management Shell.
Error
code

Error name

Error description

Corrective action

1000H

CSV File Data collector error

Failed to read the folder specified in thetarget device setting.

• Please review the target device setting.
• Please check the existence and access authority of thefolder.

1001H

CSV File Data collector error

Failed to open the file specified in the target
device setting.

• Please review the target device setting.
• Please check the existence and access authority of the file.
• Please check if the other applications have not accessed the
file.

1002H

CSV File Data collector error

The number of columns in the file to be readis less than the ones specified in the location
setting.

• Please review the location setting.
• Please check the number of columns in the file to be read.

1003H

CSV File Data collector error

The character code of the file to be read isincorrect.

• Please review the target device setting.
• Please check the character code of the file to be read.

1004H

CSV File Data collector error

Failed to read the data.

• Please review the target device setting.
• Please review the location setting.
• Please check that the value of the data is within the range ofthe maximum/minimum value of the data type.
• Please check if the data contains characters out of thespecification range.

1005H

CSV File Data collector error

The number of row in the file to be read isless than the Data starting row number
specified in the target device setting.

• Please review the target device setting.
• Please check the number of row in the file to be read.

4000H

Management Shell configuration
error

The Management Shell setting is written in
an unmatched version.

• Please delete all from the menu of Management Shell
Explorer and reset the Management Shell setting.
• If the problem is not resolved, please contact the EdgecrossConsortium.

5021H

Data collector service corruption
error

The Data collector service file is corrupted or
the version of Data collector stored at thetarget device setting and the one of Data
collector currently stored do not match.

• Please match the version of Data collector stored at theTarget Device setting and the one of Data collector currently
stored.
• If there is no problem in the version of Data collector, pleaseinstall Data collector and then set Target Device again.
• If the same error occurs again, please contact the developerof Data collector.

5022H

Data collector service start error

No executable file of Data collector exists.

Please reinstall Data collector.

5023H

Data collector service start error

Failed to start the Data collector service
because starting of it competed with editingof the target device setting.

Please reconnect on the target device setting list screen.

5024H

Data collector service start error

Failed to start the Data collector service dueto the data corruption in the target device
setting.

After deleting all from the menu of Management Shell Explorer,
please set the target device.

5025H

Data collector service start error

Failed to start Data collector.

• Please check that the Target Device has started.
• Please check the path to Target Device.
• Please check if the Target Device setting is correct.

5026H

Data collector service start error

An error occurred in Data collector.

• Please check if there is any other error.
• Please import the setting file of Management Shell again.
• Please restart the industrial PC running this product.
• Please reinstall Data collector.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developerof Data collector.

5027H

Data collector service start error

An error occurred in Data collector.

• Please check if there is any other error.
• Please import the setting file of Management Shell.
• Please restart the industrial PC running this product.
• Please reinstall Data collector.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developerof Data collector.

402

11 TROUBLESHOOTING
11.5 Error Code List

Errorcode

Error name

Error description

Corrective action

5028H

Data collector service start error

An error occurred in Data collector.

• Please check if there is any other error.
• Please import the setting file of Management Shell again.
• Please restart the industrial PC running this product.
• Please reinstall Data collector.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developerof Data collector.

51D4H

Data collector interface error

An error occurred in Data collector.

• Please check if there is any other error.
• Please import the setting file of Management Shell again.
• Please restart the industrial PC running this product.
• Please reinstall Data collector.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developerof Data collector.

51D8H

Data collector interface error

An error occurred in Data collector.

• Please check if there is any other error.
• Please import the setting file of Management Shell again.
• Please restart the industrial PC running this product.
• Please reinstall Data collector.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developerof Data collector.

51D9H

Data collector interface error

An error occurred in Data collector.

• Please check if there is any other error.
• Please import the setting file of Management Shell again.
• Please restart the industrial PC running this product.
• Please reinstall Data collector.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developerof Data collector.

51DAH

Data collector interface error

An error occurred in Data collector.

• Please check if there is any other error.
• Please import the setting file of Management Shell again.
• Please restart the industrial PC running this product.
• Please reinstall Data collector.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developerof Data collector.

51DBH

Data collector interface error

An error occurred in Data collector.

• Please check if there is any other error.
• Please import the setting file of Management Shell again.
• Please restart the industrial PC running this product.
• Please reinstall Data collector.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developerof Data collector.

51DCH

Data collector interface error

An error occurred in Data collector.

• Please check if there is any other error.
• Please import the setting file of Management Shell again.
• Please restart the industrial PC running this product.
• Please reinstall Data collector.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developerof Data collector.

5200H

Data collector service operationerror

An error occurred in Data collector.

• Please check if there is any other error.
• Please import the setting file of Management Shell again.
• Please restart the industrial PC running this product.
• Please reinstall Data collector.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developerof Data collector.

5300H

IT Gateway service corruption
error

The IT Gateway service file is broken or theversion of the IT Gateway stored at the IT
Gateway setting and the one of the IT
Gateway currently stored do no match.

• Please match the version of the IT Gateway stored at the IT
Gateway setting and the one of the IT Gateway currently
stored.
• If there is no problem in the version of the IT Gateway,
please install and set the IT Gateway again.
• If the same error occurs again, please contact the developerof the IT Gateway.

5301H

IT Gateway service start error

No executable file of IT Gateway exists.

Please reinstall the IT Gateway.

11 TROUBLESHOOTING
11.5 Error Code List

11

403

Errorcode

Error name

Error description

Corrective action

5302H

IT Gateway service start error

Failed to start the IT Gateway service
because starting of the IT Gateway service
competed with editing of the IT Gateway
setting.

Please perform a restart on the IT Gateway setting list screen.

5303H

IT Gateway service start error

Failed to start the IT Gateway service due tothe data corruption in the IT Gateway
setting.

After deleting all from the menu of Management Shell Explorer,
please set the IT Gateway again.

5304H

IT Gateway service start error

An error occurred in the IT Gateway.

• Please check that the IT Gateway has started.
• Please check if the IT Gateway setting is correct.

5305H

IT Gateway service start error

An error occurred in the IT Gateway.

• Please check if there is any other error.
• Please import the setting file of Management Shell again.
• Please restart the industrial PC running this product.
• Please reinstall the IT Gateway.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developerof the IT Gateway.

5306H

IT Gateway service start error

An error occurred in the IT Gateway.

• Please check if there is any other error.
• Please import the setting file of Management Shell again.
• Please restart the industrial PC running this product.
• Please reinstall the IT Gateway.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developerof the IT Gateway.

5307H

IT Gateway service stop error

An error occurred in the IT Gateway.

• Please check if there is any other error.
• Please import the setting file of Management Shell again.
• Please restart the industrial PC running this product.
• Please reinstall the IT Gateway.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developerof the IT Gateway.

5400H

IT Gateway interface error

An error occurred in the IT Gateway.

• Please check if there is any other error.
• Please import the setting file of Management Shell again.
• Please restart the industrial PC running this product.
• Please reinstall the IT Gateway.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developerof the IT Gateway.

5401H

IT Gateway interface error

An error occurred in the IT Gateway.

• Please check if there is any other error.
• Please import the setting file of Management Shell again.
• Please restart the industrial PC running this product.
• Please reinstall the IT Gateway.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developerof the IT Gateway.

5402H

IT Gateway interface error

An error occurred in the IT Gateway.

• Please check if there is any other error.
• Please import the setting file of Management Shell again.
• Please restart the industrial PC running this product.
• Please reinstall the IT Gateway.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developerof the IT Gateway.

5500H

IT Gateway service operationerror

An error occurred in the IT Gateway.

• Please check if there is any other error.
• Please import the setting file of Management Shell again.
• Please restart the industrial PC running this product.
• Please reinstall the IT Gateway.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developerof the IT Gateway.

5600H

Internal data tag resource
current value storage area
allocation error

Failed to allocate the current value storage
area of the internal data tag resource.

• Please delete the internal data tag resource.
• Please close other applications.
• Please restart the industrial PC running this product.

614CH

Resource contention error

A CPU resource contention has occurred
between the other application andManagement Shell.

• Please close other applications.
• Please restart the industrial PC running this product.

404

11 TROUBLESHOOTING
11.5 Error Code List

Errorcode

Error name

Error description

Corrective action

614DH

Resource contention error

A resource contention has occurred
between the other application and theManagement Shell service.

• Please restart the industrial PC running this product.
• Please close other applications.

7000H

Current value read error

Failed to read the current value because
Data collector did not respond.

• Please check if there is any other error.
• Please reduce the data number to be read at one time.
• Please refer to the Data collector manual and check if theTarget Device setting and data tag resource setting arecorrect again.
• Please reinstall Data collector.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developerof Data collector.

7001H

Current value read error

Failed to read the current value because
Data collector returned an error.

• Please check if there is any other error.
• Please refer to the Data collector manual and check if theTarget Device setting and data tag resource setting arecorrect again.
• Please reinstall Data collector.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developerof Data collector.

7002H

Management Shell internal
error(Current value read)

Failed to read the current value due to anerror in Management Shell.

• Please check if there is any other error.
• Please import the setting file of Management Shell again.
• Please restart the industrial PC running this product.
• Please reinstall Data collector.
• Please reinstall Edgecross Basic Software.
• If the same error reoccurs, please contact the EdgecrossConsortium.

7003H

Current value read error

Failed to read the current value because nodata tag resource existed.

• Please refer to the Data collector manual and check that theTarget Device setting and data tag resource setting arecorrect again.
• Please reinstall Data collector.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developerof Data collector.

7004H

Current value read error

Failed to read the current value because thedata tag resource had no read authority.

Please set the location where the data tag resource has theread authority.

7005H

Data collector stop error(Current
value read)

Failed to read the current value because theData collector service was stopped.

• Please check if there is any other error.
• Please select the target where an error has occurred andpress the reconnect button on the target device setting list
screen.
• Please check if the data tag resource setting is correct.
• If the problem persists, please contact the developer of Data
collector.

7006H

Current value read error

Failed to read the current value because thecurrent value contains characters out of thespecification range.

The current value contains characters out of the specification
range.
Please check that the data tag resource setting is correct.

7101H

Current value write error

Failed to write the current value because
Data collector did not respond.

• Please check if there is any other error.
• Please reduce the data number to be written at one time.
• Please select the target where an error has occurred andpress the reconnect button on the target device setting list
screen.
• Please check if the data tag resource setting is correct.
• If the problem persists, please contact the developer of Data
collector.

7102H

Current value write error

Failed to write the current value because
Data collector returned an error.

• Please check if there is any other error.
• Please select the target where an error has occurred andpress the reconnect button on the target device setting list
screen.
• Please check if the data tag resource setting is correct.
• If the problem persists, please contact the developer of Data
collector.

11 TROUBLESHOOTING
11.5 Error Code List

11

405

Errorcode

Error name

Error description

Corrective action

7103H

Management Shell internal
error(Current value write)

Failed to write the current value due to anerror in Management Shell.

• Please check if there is any other error.
• Please import the setting file of Management Shell again.
• Please restart the industrial PC running this product.
• Please reinstall Data collector.
• Please reinstall Edgecross Basic Software.
• If the same error reoccurs, please contact the EdgecrossConsortium.

7104H

Current value write error

Failed to write the current value because nodata tag resource existed.

Please check if the target data tag resource exists.

7105H

Current value write error

Failed to write the current value because thedata tag resource had no write authority.

Please set the location where the data tag resource has thewrite authority.

7106H

Current value write error

Failed to write the current value because
other than the data tag resource wasspecified as the current value write
destination.

Please check if the target data tag resource exists.

7107H

Current value write error

Failed to write the current value because thespecified string exceeded the maximum
number of characters of the data tag
resource.

The specified value exceeds the character string length set in
the data tag resource.
Please check the number of characters set in the data tag
resource.

7108H

Current value write error

Failed to write the current value because thedata type of the specified value and the oneof the data tag resource did not match.

Please match the data type of the specified value and the oneof the data tag resource.

7109H

Data collector stop error(Current
value write)

Failed to write the current value because theData collector service was stopped.

• Refer to the data collector manual and reconnect with theaccess destination device setting list screen.
• If the problem persists, please contact the developer of Data
collector.

7110H

Current value write error

Failed to write the current value because thespecified string contains characters out of
the specification range.

The specified value contains characters out of the specification
range.
Please check the specified value.

7200H

Current value read error

Failed to read the current value because
Data collector did not respond.

• Please check if there is any other error.
• Please reduce the data number to be read at one time.
• Please refer to the Data collector manual and check if theTarget Device setting and data tag resource setting arecorrect again.
• Please reinstall Data collector.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developerof Data collector.

7201H

Current value read error

Failed to read the current value because
Data collector returned an error.

• Please check if an error is registered from Data collector
where the problem occurred. If the error is registered, please
execute the measure described in the error details.
• Please refer to the Data collector manual and check if theTarget Device setting and Data tag resource setting arecorrect again.
• Please reinstall Data collector.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the developerof Data collector.

7205H

Data collector stop error(Current
value read)

Failed to read the current value because theData collector service was stopped.

• Please check if there is any other error.
• Please select the target where an error has occurred andpress the reconnect button on the target device setting list
screen.
• Please check if the data tag resource setting is correct.
• If the problem persists, please contact the developer of Data
collector.

7206H

Current value read error

Failed to read the current value because thecurrent value contains characters out of thespecification range.

The current value contains characters out of the specification
range.
Please check that the data tag resource setting is correct.

7207H

Data collector request senderror(Current value read)

Failed to send a request to the Data
collector service.

• Please restart the industrial PC running this product.
• Please reinstall Data collector.
• Please reinstall Edgecross Basic Software.
• If the same error reoccurs, please contact the EdgecrossConsortium.

406

11 TROUBLESHOOTING
11.5 Error Code List

Errorcode

Error name

Error description

Corrective action

7208H

Data collector connection
error(Current value read)

Failed to connect to the Data collector
service.

• Please restart the industrial PC running this product.
• Please reinstall Data collector.
• Please reinstall Edgecross Basic Software.
• If the same error reoccurs, please contact the EdgecrossConsortium.

7300H

Internal data tag resource
current value read error

Failed to read the current value because
allocating the current value storage area of
the internal data tag resource failed.

• Please delete the internal data tag resource.
• Please close other applications.
• Please restart the industrial PC running this product.

7301HInternal data tag resource(operation) current value readerror

Failed to read the current value because theresource used for the operation term does
not exist.

Please check the resource specified for the operation term.

7302HInternal data tag resource(operation) current value readerror

Failed to read the current value because a
resource other than external data tag
resource is used for the operation term.

Please check the resource specified for the operation term.

7303HInternal data tag resource(operation) current value readerror

Failed to read the current value because
data types other than BOOL is used for the
logical operation.

• Please check data types of target data tag resource and theoperation term.
• Please check the operator of the operation expression.

7304HInternal data tag resource(operation) current value readerror

Failed to read the current value because
data types other than signed integer,
unsigned integer, or real number is used forthe four arithmetic operations.

• Please check data types of target data tag resource and theoperation term.
• Please check the operator of the operation expression.

7305HInternal data tag resource(operation) current value readerror

Failed to read the current value because
data types of signed integer, unsigned
integer, and real number coexist in theoperation expression.

Please check data types of the target operation term.

7306H

Internal data tag resource(operation) current value readerror

Failed to read the current value because adata type other than BOOL is specified forthe internal data tag resource (operation) for
the BOOL operation.

Please check data types of target data tag resource and theoperation term.

7307H

Internal data tag resource(operation) current value readerror

Failed to read the current value because adata type other than the unsigned integer is
specified for the internal data tag resource(operation) for the operation of the unsigned
integer.

Please check data types of target data tag resource and theoperation term.

7308HInternal data tag resource(operation) current value readerror

Failed to read the current value because adata type other than the signed integer is
specified for the internal data tag resource(operation) for the operation of the signed
integer.

Please check data types of target data tag resource and theoperation term.

7309HInternal data tag resource(operation) current value readerror

Failed to read the current value because adata type other than the real number is
specified for the internal data tag resource(operation) for the operation of the real
number.

Please check data types of target data tag resource and theoperation term.

7310H

Internal data tag resource(operation) current value readerror

Failed to read the current value because theoperation expression is incorrect (division byzero).

Please check the value of the resource specified for theoperation term.

7311H

Internal data tag resource(operation) current value readerror

Failed to read the current value because theoperation result is incorrect (NaN, ).

Please execute the following measures as necessary.
• Please check the value of the resource specified for theoperation term.
• Please check data types of target data tag resource and theoperation term.
• Please check the operator of the operation expression.

7312HInternal data tag resource(operation) current value readerror

Failed to read the current value because theoperation results overflow.

Please execute the following measures as necessary.
• Please check the value of the resource specified for theoperation term.
• Please check data types of target data tag resource and theoperation term.
• Please check the operator of the operation expression.

7400H

Internal data tag resource
current value write error

Failed to write the current value because
allocating the current value storage area of
the internal data tag resource failed.

• Please delete the internal data tag resource.
• Please close other applications.
• Please restart the industrial PC running this product.

7401HInternal data tag resource
current value write error

Failed to write the current value because theinternal data tag resource had no write
authority.

Please set the internal data tag resource with the write
authority.

11 TROUBLESHOOTING
11.5 Error Code List

11

407

Errorcode

Error name

Error description

Corrective action

7402H

Internal data tag resource
current value write error

Failed to write the current value because thespecified character string exceeded the
maximum number of characters of theinternal data tag resource.

The specified value exceeds the character string length set in
the internal data tag resource.
Please check the number of characters set in the internal datatag resource.

7403H

Internal data tag resource
current value write error

Failed to write the current value because thedata type of the specified value and the oneof the data tag resource did not match.

Please match the data type of the specified value and the oneof the internal data tag resource.

7404H

Internal data tag resource
current value write error

Failed to write the current value to theinternal data tag resource because thespecified character string contains
characters out of the specification range.

The specified value contains characters out of the specification
range.
Please check the specified value.

7500H

Event history automatic output
function Setting error

Failed to start the operation because theformat of the event history automatic output
setting is not supported.

Please configure the event history automatic output setting
again.

7501H

Event history automatic output
function File open error

Failed to open the event history file.

• Please check if the event history file is open.
• When a remote shared folder is set as the save destination
folder, please check if there is any problem in the connection
path of the network. Also, please reduce the load on the
network by reducing the frequency of accessing theconnection destination.
• Please check the access authority of the save destination
folder.
• Please check that the event history file is not read-only.
• Please change the save destination of the event history file.
• Please restart the industrial PC running this product.

7502H

Event history automatic output
function File saving error

Failed to save the event history file.

• When a remote shared folder is set as the save destination
folder, please check if there is any problem in the connection
path of the network. Also, please reduce the load on the
network by reducing the frequency of accessing theconnection destination.
• Please reduce the load on the access to the storage of thesave destination folder.
• Please delete unnecessary files to allocate free space.
• Please change the save destination of the event history file.

7503H

Event history automatic output
function File backup error

Failed to backup the event history file.

• When a remote shared folder is set as the save destination
folder, please check if there is any problem in the connection
path of the network. Also, please reduce the load on the
network by reducing the frequency of accessing theconnection destination.
• Please reduce the load on the access to the storage of thesave destination folder.
• Please check the access authority of the save destination
folder.
• Please check if any file with the same name as the backup
file of the event history file is open.
• Please delete unnecessary files to allocate free space.

7504H

Event history automatic output
function Memory insufficienterror

Failed to allocate the memory required forthe operation.

• Please reduce the load on Windows by closing otherapplications.
• Please restart the industrial PC running this product.

7505H

Event history automatic output
function Memory insufficienterror

Failed to allocate the memory required forthe operation.

• Please reduce the load on Windows by closing otherapplications.
• Please restart the industrial PC running this product.

7506H

Event history automatic output
function Internal processing
error

Failed to perform the internal processing of
the event history automatic output function.

• Please reduce the load on Windows by closing otherapplications.
• Please restart the industrial PC running this product.
• Please restart the industrial PC after reinstalling EdgecrossBasic Software.

7507H

Event history automatic output
function Internal processing
error

Failed to perform the internal processing of
the event history automatic output function.

• Please reduce the load on Windows by closing otherapplications.
• Please restart the industrial PC running this product.
• Please restart the industrial PC after reinstalling EdgecrossBasic Software.

7508H

Event history automatic output
function User accountauthentication setting error

Failed to authenticate the user account.

• Please review the user account setting of the savedestination folder.
• Please unlock the user account.

408

11 TROUBLESHOOTING
11.5 Error Code List

Errorcode

Error name

Error description

Corrective action

7509H

Event history automatic output
function Error at user accountauthentication

Failed to execute the user accountauthentication.

Please check if there is any problem in the connection path of
the network to the remote shared folder. Also, please reduce
the load on the network by reducing the frequency ofaccessing the connection destination.

750AH

Event history automatic output
function Event history accesserror

Failed to acquire the event history
information because the update frequencyof the event history was high.

Please check that the event history file has been updated
because it might not be.
Please perform the following when it has not been updated.
• Please check if there is any event that occurs continuously
and take corrective action on the event.
• Please reduce the load on Windows by closing otherapplications.
• Please restart the industrial PC running this product.

11

F001H

Data Collector I/F error

An error occurred during the access to
Edgecross Basic Software.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• Please check if the combination of the specification versionsof Edgecross Basic Software and Data Collector is available.
• If the same error recurs, please consult with the Data
Collector developer.

F002H

Data Collector I/F error

An error occurred during the access to
Edgecross Basic Software.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• Please check if the combination of the specification versionsof Edgecross Basic Software and Data Collector is available.
• If the same error recurs, please consult with the Data
Collector developer.

F003H

Data Collector I/F error

An error occurred during the access to
Edgecross Basic Software.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• Please check if the combination of the specification versionsof Edgecross Basic Software and Data Collector is available.
• If the same error recurs, please consult with the Data
Collector developer.

F004H

Data Collector I/F error

An error occurred during the access to
Edgecross Basic Software.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• Please check if the combination of the specification versionsof Edgecross Basic Software and Data Collector is available.
• If the same error recurs, please consult with the Data
Collector developer.

F005H

Data Collector I/F error

An error occurred during the access to
Edgecross Basic Software.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• Please check if the combination of the specification versionsof Edgecross Basic Software and Data Collector is available.
• If the same error recurs, please consult with the Data
Collector developer.

F006H

Data Collector I/F error

An error occurred during the access to
Edgecross Basic Software.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• Please check if the combination of the specification versionsof Edgecross Basic Software and Data Collector is available.
• If the same error recurs, please consult with the Data
Collector developer.

11 TROUBLESHOOTING
11.5 Error Code List

409

Errorcode

Error name

Error description

Corrective action

F007H

Data Collector I/F error

An error occurred during the access to
Edgecross Basic Software.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• Please check if the combination of the specification versionsof Edgecross Basic Software and Data Collector is available.
• If the same error recurs, please consult with the Data
Collector developer.

F008H

Data Collector I/F error

An error occurred during the access to
Edgecross Basic Software.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• Please check if the combination of the specification versionsof Edgecross Basic Software and Data Collector is available.
• If the same error recurs, please consult with the Data
Collector developer.

F009H

Data Collector I/F error

An error occurred during the access to
Edgecross Basic Software.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• Please check if the combination of the specification versionsof Edgecross Basic Software and Data Collector is available.
• If the same error recurs, please consult with the Data
Collector developer.

F00AH

Data Collector I/F error

An error occurred during the access to
Edgecross Basic Software.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• Please check if the combination of the specification versionsof Edgecross Basic Software and Data Collector is available.
• If the same error recurs, please consult with the Data
Collector developer.

F00BH

Data Collector I/F error

An error occurred during the access to
Edgecross Basic Software.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• Please check if the combination of the specification versionsof Edgecross Basic Software and Data Collector is available.
• If the same error recurs, please consult with the Data
Collector developer.

F00CH

Data Collector I/F error

An error occurred during the access to
Edgecross Basic Software.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• Please check if the combination of the specification versionsof Edgecross Basic Software and Data Collector is available.
• If the same error recurs, please consult with the Data
Collector developer.

F00DH

Data Collector I/F error

An error occurred during the access to
Edgecross Basic Software.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• Please check if the combination of the specification versionsof Edgecross Basic Software and Data Collector is available.
• If the same error recurs, please consult with the Data
Collector developer.

410

11 TROUBLESHOOTING
11.5 Error Code List

Errorcode

Error name

Error description

Corrective action

F00EH

Data Collector I/F error

An error occurred during the access to
Edgecross Basic Software.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• Please check if the combination of the specification versionsof Edgecross Basic Software and Data Collector is available.
• If the same error recurs, please consult with the Data
Collector developer.

F00FH

Data Collector I/F error

An error occurred during the access to
Edgecross Basic Software.

• Carry out review to lower the load caused by collection
cycle, number of collections, and contents of processing.
• Lower the load on Windows by closing other applications orby other means.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• Please check if the combination of the specification versionsof Edgecross Basic Software and Data Collector is available.
• If the same error recurs, please consult with the Data
Collector developer.

F010H

Data Collector I/F error

An error occurred during the access to
Edgecross Basic Software.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• Please check if the combination of the specification versionsof Edgecross Basic Software and Data Collector is available.
• If the same error recurs, please consult with the Data
Collector developer.

F011H

Data Collector I/F error

An error occurred during the access to
Edgecross Basic Software.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• Please check if the combination of the specification versionsof Edgecross Basic Software and Data Collector is available.
• If the same error recurs, please consult with the Data
Collector developer.

F012H

Data Collector I/F error

An error occurred during the access to
Edgecross Basic Software.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• Please check if the combination of the specification versionsof Edgecross Basic Software and Data Collector is available.
• If the same error recurs, please consult with the Data
Collector developer.

F013H

Data Collector I/F error

An error occurred during the access to
Edgecross Basic Software.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• Please check if the combination of the specification versionsof Edgecross Basic Software and Data Collector is available.
• If the same error recurs, please consult with the Data
Collector developer.

F100H

Error in the initialization processof Data Collector

An error occurred in the initialization
process.

• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• Please check if the combination of the specification versionsof Edgecross Basic Software and Data Collector is available.
• If the same error recurs, please consult with the Data
Collector developer.

11 TROUBLESHOOTING
11.5 Error Code List

11

411

Errorcode

Error name

Error description

Corrective action

F104H

Error in the initialization processof Data Collector

An error occurred in the initialization
process.

• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• Please check if the combination of the specification versionsof Edgecross Basic Software and Data Collector is available.
• If the same error recurs, please consult with the Data
Collector developer.

F105H

Error in the initialization processof Data Collector

An error occurred in the initialization
process.

• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• Please check if the combination of the specification versionsof Edgecross Basic Software and Data Collector is available.
• If the same error recurs, please consult with the Data
Collector developer.

F106H

Error in the collection process of
Data Collector

An error occurred in the collection process.

• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• Please check if the combination of the specification versionsof Edgecross Basic Software and Data Collector is available.
• If the same error recurs, please consult with the Data
Collector developer.

F107H

Error in the read process of
Data Collector

An error occurred in the read process.

• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• Please check if the combination of the specification versionsof Edgecross Basic Software and Data Collector is available.
• If the same error recurs, please consult with the Data
Collector developer.

F108H

Error in the write process of
Data Collector

An error occurred in the write process.

• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• Please check if the combination of the specification versionsof Edgecross Basic Software and Data Collector is available.
• If the same error recurs, please consult with the Data
Collector developer.

F109H

Error in the read process of
Data Collector

An error occurred in the read process.

• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• Please check if the combination of the specification versionsof Edgecross Basic Software and Data Collector is available.
• If the same error recurs, please consult with the Data
Collector developer.

F10AH

Error in the write process of
Data Collector

An error occurred in the write process.

• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• Please check if the combination of the specification versionsof Edgecross Basic Software and Data Collector is available.
• If the same error recurs, please consult with the Data
Collector developer.

F200H

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F205H

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

412

11 TROUBLESHOOTING
11.5 Error Code List

Errorcode

Error name

Error description

Corrective action

F207H

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F20AH

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F20BH

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F20CH

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F20DH

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F20EH

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F20FH

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F212H

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F217H

Error in module reference

An error occurred when the module (JSONparser) was referenced.

• Please reinstall Data Collector.
• If the same error recurs, please consult with the Data
Collector developer.

F218H

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

11 TROUBLESHOOTING
11.5 Error Code List

11

413

Errorcode

Error name

Error description

Corrective action

F219H

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F21AH

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F21BH

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F21CH

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F21EH

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F221H

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F223H

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F227H

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F228H

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

414

11 TROUBLESHOOTING
11.5 Error Code List

Errorcode

Error name

Error description

Corrective action

F229H

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F22AH

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

11

F22BH

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F22DH

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F22FH

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F232H

Data Collector I/F error

An error occurred during the access to
Edgecross Basic Software.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• Please check if the combination of the specification versionsof Edgecross Basic Software and Data Collector is available.
• If the same error recurs, please consult with the Data
Collector developer.

F233H

Data Collector I/F error

An error occurred during the access to
Edgecross Basic Software.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• Please check if the combination of the specification versionsof Edgecross Basic Software and Data Collector is available.
• If the same error recurs, please consult with the Data
Collector developer.

F234H

Data Collector I/F error

An error occurred during the access to
Edgecross Basic Software.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• Please check if the combination of the specification versionsof Edgecross Basic Software and Data Collector is available.
• If the same error recurs, please consult with the Data
Collector developer.

11 TROUBLESHOOTING
11.5 Error Code List

415

Errorcode

Error name

Error description

Corrective action

F240H

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F242H

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F244H

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F245H

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F247H

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F248H

Data reference error in Data
Collector

An error occurred when the argument of thecommunication parameter acquisition wasreferenced.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F249H

Data reference error in Data
Collector

An error occurred when the argument of thecollection parameter acquisition wasreferenced.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F24AH

Data reference error in Data
Collector

An error occurred when the argument of thedata parameter acquisition was referenced.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F24CH

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F24DH

Process data buffer overflow in
Data Collector

Data buffering has overflowed.

• Carry out review to lower the load caused by collection
cycle, number of collections, and contents of processing.
• Lower the load on Windows by closing other applications orby other means.

416

11 TROUBLESHOOTING
11.5 Error Code List

Errorcode

Error name

Error description

Corrective action

F24EH

Process data buffer overflow in
Data Collector

Data buffering has overflowed.

• Carry out review to lower the load caused by collection
cycle, number of collections, and contents of processing.
• Lower the load on Windows by closing other applications orby other means.

F260H

Error: Character is out of range

The character string acquired from the Data
Collector contains characters out of range.

Please do not set characters out of range to collected STRING
type character string.

F261H

Error: Character is out of range

The character string acquired from the Data
Collector contains characters out of range.

Please do not set characters out of range to read STRING typecharacter string.

F262H

Error: Number of characters
exceeded

It exceeds the maximum number ofcharacter string acquired from the Data
Collector.

• Please review the location parameter so that the number ofcharacters in the collected STRING type character string
does not exceed the maximum number.
• Please review the target device value so that the number ofcharacters in the collected STRING type character string
does not exceed the maximum number.

F263H

Error: Number of characters
exceeded

It exceeds the maximum number ofcharacter string acquired from the Data
Collector.

• Please review the location parameter so that the number ofcharacters in the read STRING type character string does
not exceed the maximum number.
• Please review the target device value so that the number ofcharacters in the read STRING type character string does
not exceed the maximum number.

F264H

Error: Character is out of range

The character string acquired from the Data
Collector contains characters out of range.

Please do not set characters out of range to collected
WSTRING type character string.

F265H

Error: Character is out of range

The character string acquired from the Data
Collector contains characters out of range.

Please do not set characters out of range to read WSTRING
type character string.

F266H

Error: Number of characters
exceeded

It exceeds the maximum number ofcharacter string acquired from the Data
Collector.

• Please review the location parameter so that the number ofcharacters in the collected WSTRING type character string
does not exceed the maximum number.
• Please review the target device value so that the number ofcharacters in the collected WSTRING type character string
does not exceed the maximum number.

F267H

Error: Number of characters
exceeded

It exceeds the maximum number ofcharacter string acquired from the Data
Collector.

• Please review the location parameter so that the number ofcharacters in the read WSTRING type character string does
not exceed the maximum number.
• Please review the target device value so that the number ofcharacters in the read WSTRING type character string does
not exceed the maximum number.

F268H

Invalid real number data

The real number acquired from the Data
Collector is invalid(NaN, ).

Please do not set invalid value(NaN, ) to read REAL typereal number.

F269H

Invalid real number data

The real number acquired from the Data
Collector is invalid(NaN, ).

Please do not set invalid value(NaN, ) to read LREAL typereal number.

F280H

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F281H

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F282H

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

11 TROUBLESHOOTING
11.5 Error Code List

11

417

Errorcode

Error name

Error description

Corrective action

F283H

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F284H

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F2C5H

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F2C6H

Process data buffer overflow in
Data Collector

Data buffering has overflowed.

• Carry out review to lower the load caused by collection
cycle, number of collections, and contents of processing.
• Lower the load on Windows by closing other applications orby other means.

F300H

Error: Not enough memory

There is not enough memory available toexecute this operation.

• Please close other applications.
• Please restart the Industrial PC.

F303H

Error: Not enough memory

There is not enough memory available toexecute this operation.

• Please close other applications.
• Please restart the Industrial PC.

F306H

Error: Not enough memory

There is not enough memory available toexecute this operation.

• Please close other applications.
• Please restart the Industrial PC.

F30EH

Error: Not enough memory

There is not enough memory available toexecute this operation.

• Please close other applications.
• Please restart the Industrial PC.

F380H

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F382H

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F383H

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F386H

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

418

11 TROUBLESHOOTING
11.5 Error Code List

Errorcode

Error name

Error description

Corrective action

F387H

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F388H

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F389H

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F38AH

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F38BH

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F38DH

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

F38FH

Data Collector internal error

An unexpected error occurred inside thisproduct.

• If Real-time Flow Manager is used, please write the Data
Collector parameter again.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please reinstall Edgecross Basic Software.
• If the same error recurs, please consult with the Data
Collector developer.

11 TROUBLESHOOTING
11.5 Error Code List

11

419

Codes for errors that occur in Management Shell Data collector
The following table shows the codes for errors that occur in Management Shell Data collector.
Error
code

Error name

Error description

Corrective action

2001H

Data Collection Setting Error

The Data Collection setting is incorrect.

Please review and correct the Data Collection setting.

2002H

Management Shell connection
error (Connection failure)

Failed to connect to Management Shell.

• Please check that Management Shell has started.
• Please reduce the number of OPC UA clients to beconnected to Management Shell.
• Please set the Target Device again.
• Please lower the load on Windows by closing otherapplications.

2003H

Management Shell connection
error (Session establishment
failure)Failed to establish the session withManagement Shell.

• Please check that Management Shell has started.
• Please reduce the number of OPC UA clients to beconnected to Management Shell.
• Please set the Target Device again.
• Please lower the load on Windows by closing otherapplications.

2004H

Connection information readerror

Failed to read the connection information.

Please set the Target Device again.

2007H

Data Collector internal error

An unexpected error occurred inside thisproduct.

• Please set the Target Device again.
• Please write Real-time Flow Manager Parameter again.
• Please set it on the OPC UA setting screen of Management
Shell Explorer.
• Please check if there is any other error.
• Please restart the industrial PC running this product.
• Please reinstall this product.

2008H

Target Device setting error

The Target Device setting information does
not exist.

Please set the Target Device again.

2011H

Management Shell
communication timeout error

The communication with Management Shell
has timed out.

• Please check that Management Shell has started.
• Please refer to the error information list of Management
Shell Explorer to check if an error has occurred.
• Please lower the load on Windows by closing otherapplications.
• Please reduce the number of OPC UA clients to beconnected to Management Shell.
• Please execute STOP operation with Real-time Flow
Designer, then execute RUN operation again.

2012H

Collection error (Management
Shell connection failure)

Failed to collect the data because theconnection with Management Shell was lost.

• Please check that Management Shell has started.
• Please refer to the error information list of Management
Shell Explorer to check if an error has occurred.
• Please lower the load on Windows by closing otherapplications.
• Please reduce the number of OPC UA clients to beconnected to Management Shell.
• Please execute STOP operation with Real-time Flow
Designer, then execute RUN operation again.

2013H

Collection error (Access to a
non-existent tag)

Failed to collect the data because collection
was performed on a tag which did not exist
in Management Shell.

• Please review the location setting or Management Shellsetting so that the tag of the location setting exists inManagement Shell.
• Please execute STOP operation with Real-time Flow
Designer, then execute RUN operation again.

2014H

Collection error (Incorrectaccess direction)

Failed to collect the data because collection
was performed on a tag which was set to
unreadable in Management Shell.

• Please review the location setting or Management Shellsetting so that the access direction of the tag of the location
setting becomes Read or Read/Write.
• Please execute STOP operation with Real-time Flow
Designer, then execute RUN operation again.

2015H

Collection error (Data typemismatch)

The settings for the data types of the tag of
the location setting and Management Shell
are different.

• Please review the location setting or Management Shellsetting so that the data types of the tag of the location setting
and Management Shell match.
• Please execute STOP operation with Real-time Flow
Designer, then execute RUN operation again.

420

11 TROUBLESHOOTING
11.5 Error Code List

Errorcode

Error name

Error description

Corrective action

2016H

Collection error (Error detectedin Management Shell)

Failed to collect the data because an error
was detected in Management Shell.

• Please refer to the error information list of Management
Shell Explorer to check if an error has occurred.
• Please execute STOP operation with Real-time Flow
Designer, then execute RUN operation again.
• If the status code is displayed in the Data collector internal
information, please contact Edgecross Consortium.

Codes for errors that occur in Dummy Data collector

11

The following table shows the codes for errors that occur in Dummy Data collector.
Error
code

Error name

Error description

Corrective action

F001H to
F004H

Data Collector I/F error

An error occurred during the access to
Edgecross Basic Software.

• Please restart the Industrial PC.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the EdgecrossConsortium.

F007H to
F00AH

Data Collector I/F error

An error occurred during the access to
Edgecross Basic Software.

• Please restart the Industrial PC.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the EdgecrossConsortium.

F012H

Data Collector I/F error

An error occurred during the access to
Edgecross Basic Software.

• Please restart the Industrial PC.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the EdgecrossConsortium.

F200H

Data Collector internal error

An unexpected error occurred inside thisproduct.

• Please restart the Industrial PC.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the EdgecrossConsortium.

F217H

Error in module reference

An error occurred when the module (JSONparser) was referenced.

• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the EdgecrossConsortium.

F234H

Data Collector I/F error

An error occurred during the access to
Edgecross Basic Software.

• Please restart the Industrial PC.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please contact the EdgecrossConsortium.

11 TROUBLESHOOTING
11.5 Error Code List

421

11.6

Event Code List

This section shows the codes for events that occur in Edgecross Basic Software.

Codes for events that occur in Real-time Flow Manager
The following table shows the codes for events that occur in Real-time Flow Manager.
Event
code

Event type

Event

Description

0770H

Operation

Feedback execution success

Feedback execution succeeded.

0771H

Operation

Feedback execution failure

Feedback execution failed.

4102H

Operation

Real-time Flow Manager start

Real-time Flow Manager has been started.

4103H

Operation

Real-time Flow Manager end

Real-time Flow Manager has been ended.

4200H

Operation

Event history file clear

Event history file clear was executed.

4250H

Operation

Error clear success

Error clear has been executed.

4251H

Operation

Error clear failure

Error clear has failed due to a major error.

4300H

Operation

Operation status switching executed

The operation status switching has been executed.

8000H

Operation

Invalid real number data

Since the real number data is invalid (NaN, ), the record wasdeleted.

8001H

Operation

Invalid real number data

Since the real number data is invalid (NaN, ), the feedback
execution request was canceled.

8002H

Operation

Invalid real number data

Since the real number data is invalid (NaN, ), thecorresponding record was not saved in the file.

Codes for events that occur in Management Shell
The following table shows the codes for events that occur in Management Shell.
Event
code

Event type

Event

Description

Corrective action

2000H

Operation

Read processing time

Measurement of Read processing
time has been completed.



8000H

Operation

Management Shell service start

The Management Shell service
has started.



8001H

Operation

Management Shell service stop

The Management Shell service
has stopped.



8002H

Operation

Data collector start

The Data collector service has
started.



8003H

Operation

Data collector stop

The Data collector service has
stopped.



8004H

Operation

IT Gateway start

The IT Gateway service has
started.



8005H

Operation

IT Gateway stop

The IT Gateway service has
stopped.



8006H

Operation

Event history file clear

Event history file clear was
executed.



8007H

Operation

Error clear success

Error clear has been executed.



8008H

Operation

Error clear failure

Error clear has failed.



8500H

Operation

Monitoring target item
registration failure

Failed to register the monitoringtarget item due to insufficient
memory.

• Please reduce the number of monitoring target
items.
• Close other applications on the industrial PC
on which Management Shell is running tosecure free space.
• Increase the memory of the industrial PC on
which Management Shell is running.

F800H

Warning

Exceeded collection cycle

Collection process was notcompleted within the collection
cycle.



422

11 TROUBLESHOOTING
11.6 Event Code List

Codes for events that occur in Management Shell Data collector
The following table shows the codes for events that occur in Management Shell Data collector.
Event
code

Event type

Event

Description

9000H

Information

Collection processing time

Measurement of collection processing time has been completed.

F800H

Warning

Exceeded collection cycle

Collection process was not completed within the collection cycle.

11

11 TROUBLESHOOTING
11.6 Event Code List

423

11.7

Code List for Data Model Import

This section shows the codes for warnings and errors that occur during data model import.
Code

Result

Type

Cause

Corrective action

2400H

Error

Component

No component name is set.

Please set a component name within 1 to 32
characters.

2401H

Error

Component

No component display name is set.

Please set a component display name within 1 to
64 characters.

2402H

Error

Component

The component name contains input prohibitedcharacters.

Please configure the component name using only
the following characters that can be input.
• Alphanumeric characters• "_" "-"

2403H

Error

Component

The component display name contains input
prohibited characters.

Please remove the following input prohibitedcharacters from the component display name.
• Control character codes (U+0000 to U+001F,
U+007F to U+00A0, U+00AD)• Line feed codes (U+2028, U+2029)

2404H

Error

Component

The component name exceeds the maximum
number of characters.

Please set a component name within 1 to 32
characters.

2405H

Error

Component

The component display name exceeds the
maximum number of characters.

Please set a component display name within 1 to
64 characters.

2406H

Error

Component

The number of components exceeds the
maximum number by {0}.
• {0}: Number of components exceeding the
maximum number

Please set the number of components to 999 or
less.

2407H

Error

Component

The number of layers of the component exceeds
the maximum number by {0}.
• {0}: Number of layers exceeding the maximum
numberPlease set the number of layers of the component
to 31 or less.

2408H

Error

Component

The component names of the components
defined in the same layer are duplicated.

Please set a component name which does not
duplicate with others.

2409H

Error

Component

The icon file path contains input prohibitedcharacters.

Please remove the following input prohibitedcharacters from the icon file name.
• "\" "/" ":" "*" "?" """ "<" ">" "|"

240AH

Error

Component

The icon file name exceeds the maximum
number of characters.

Please set the icon file name within 1 to 255
characters.

240BH

Error

Component

No icon file name is set.

Please set the icon file name within 1 to 255
characters.

240CH

Error

Component

The file format that cannot be used for the icon
is set.

Please set the extension of the icon file to any of
the following.
• .png, .bmp, .jpg, .ico, .gif

2500H

Error

Resource

No resource name is set.

Please set a resource name within 1 to 32
characters.

2501H

Error

Resource

No resource display name is set.

Please set a resource display name within 1 to 64
characters.

2507H

Error

Resource

The resource name contains input prohibitedcharacters.

Please configure the resource name using only
the following characters that can be input.
• Single-byte alphanumeric characters excluding".", "/", and "\"

2508H

Error

Resource

The resource display name contains input
prohibited characters.

Please remove the following input prohibitedcharacters from the resource display name.
• Control character codes (U+0000 to U+001F,
U+007F to U+00A0, U+00AD)• Line feed codes (U+2028, U+2029)

2509H

Error

Resource

No location of the external data tag resource isset.

When a Data collector other than the CSV File
Data collector is used, set the location with one ormore characters.

250CH

Error

Resource

The external data tag resource location contains
input prohibited characters.

Please remove the following input prohibitedcharacters from the location.
• Control character codes (U+0000 to U+001F,
U+007F to U+00A0, U+00AD)• Line feed codes (U+2028, U+2029)

424

11 TROUBLESHOOTING
11.7 Code List for Data Model ImportCode

Result

Type

Cause

Corrective action

250DH

Error

Resource

The file path of the file resource contains input
prohibited characters.

Please remove the following input prohibitedcharacters from the file path.
• Characters that cannot be used for the file pathof Windows ("*", "?", """, "<", ">", "|")

250EH

Error

Resource

The resource name exceeds the maximum
number of characters.

Please set a resource name within 1 to 32
characters.

250FH

Error

Resource

The resource display name exceeds the
maximum number of characters.

Please set a resource display name within 1 to 64
characters.

2510H

Error

Resource

The data type of the data tag resource exceeds
the maximum number of characters.

Please set the data type within 1 to 11.

2511H

Error

Resource

A value outside the range is set to the number ofcharacters of the data tag resource.

Please set 1 to 32 characters for the STRING
type, 1 to 16 characters for the WSTRING type,and 0 for other data types.

2513H

Error

Resource

The location of the external data tag resource
exceeds the maximum number of characters.

Please set the location within 300 characters or
less.

2514H

Error

Resource

The file path of the file resource exceeds the
maximum number of characters.

Please set the file path within 259 characters or
less.

2515H

Error

Resource

The number of resources defined in the samelayer exceeds the maximum number by {0}.
• {0}: Number of resources exceeding the
maximum number

Please set the number of resources to be definedin the same layer to 1000 or less.

2517H

Error

Resource

The folder path of the folder resource contains
input prohibited characters.

Please remove the following input prohibitedcharacters from the folder path.
• Characters that cannot be used for the file pathof Windows ("*", "?", """, "<", ">", "|")

2518H

Error

Resource

The folder path of the folder resource exceeds
the maximum number of characters.

Please set the file path within 247 characters or
less.

251AH

Error

Resource

The Target Device setting information that isused by the external data tag resource does notexist.

Please set the same value as the ID for any of theTarget Device settings to the ID.

2520H

Error

Resource

The resource names of the resources defined in
the same layer are duplicated.

Please set a resource name which does not
duplicate with others.

2521H

Error

Resource

A value that does not exist is set to the accessauthority to the resource.

Please specify one of the following values for theaccess authority to the resource.
• Read only: 1• Readable/writable: 3

2522H

Error

Resource

An invalid value is set to the initial value of theresource.

Please set a value and character that can beentered to each data type.

2525H

Error

Resource

A relative path is set for the file path of theresource.

Please set an absolute path for the file path of theresource.

2526H

Error

Resource

A relative path is set for the folder path of theresource.

Please set an absolute path for the folder path of
the resource.

2527H

Error

Resource

The description of the Target Device setting isincorrect.

• Please set the <AccessConfigs> element to<AccessConfigs />.
• Please set "0" for the ID of the external data tag
resource.

2600H

Error

Access target device
setting

The setting name contains input prohibitedcharacters.

Please remove the following input prohibitedcharacters from the setting name.
• Control character codes (U+0000 to U+001F,
U+007F to U+00A0, U+00AD)• Line feed codes (U+2028, U+2029)

2601H

Error

Access target device
setting

The comment contains input prohibitedcharacters.

Please remove the following input prohibitedcharacters from the comment.
• Control character codes (U+0000 to U+001F,
U+007F to U+00A0, U+00AD)• Line feed codes (U+2028, U+2029)

2602H

Error

Access target device
setting

The setting name exceeds the maximum
number of characters.

Please set the setting name within 1 to 32
characters.

2603H

Error

Access target device
setting

The comment exceeds the maximum number ofcharacters.

Please set the comment within 100 characters or
less.

2604H

Error

Access target device
setting

The number of Target Device settings exceeds
the maximum number by {0}.
• {0}: Number of access target device settings
exceeding the maximum number

Please set the number of Target Device settings
to 100 or less.

11 TROUBLESHOOTING
11.7 Code List for Data Model Import

11

425

Code

Result

Type

Cause

Corrective action

2605H

Error

Access target device
setting

No setting name is set.

Please set a setting name of the Target Device
setting within 1 to 32 characters.

2606H

Error

Access target device
setting

The ID has been changed.

Please do not change the ID.
• When the ID has been changed, please
perform data model export of Management
Shell Explorer, and edit it in the output data
model file again.

2607H

Error

Access target device
setting

The developer company code has beenchanged.

Please do not change the developer company
code.
• When the ID has been changed, please
perform data model export of Management
Shell Explorer, and edit it in the output data
model file again.

2608H

Error

Access target device
setting

The developer has been changed.

Please do not change the developer.
• When the ID has been changed, please
perform data model export of Management
Shell Explorer, and edit it in the output data
model file again.

2609H

Error

Access target device
setting

The data collector name has been changed.

Please do not change the data collector name.
• When the ID has been changed, please
perform data model export of Management
Shell Explorer, and edit it in the output data
model file again.

260AH

Error

Access target device
setting

The data collector version has been changed.

Please do not change the data collector version.
• When the ID has been changed, please
perform data model export of Management
Shell Explorer, and edit it in the output data
model file again.

260BH

Error

Access target device
setting

The Data collector that is used by the Target
Device setting has not been installed.

After installing the following Data collector, please
update to the latest installation status in the Data
collector list screen.
{0} Version {1} ({2})• {0}: Data collector name• {1}: Data collector version (integer without zero
padding (up to 4 digits))• {2}: Developer

260CH

Error

Access target device
setting

The setting names are duplicated.

Please set a setting name which does not
duplicate with others.

261EH

Error

Access target device
setting

The parameter has been changed.

Please do not change the parameter.
• When the ID has been changed, please
perform data model export of Management
Shell Explorer, and edit it in the output data
model file again.

261FH

Error

Access target device
setting

The IDs are duplicated.

Please do not change the ID.
• When the ID has been changed, please
perform data model export of Management
Shell Explorer, and edit it in the output data
model file again.

2700H

Error

OthersThe path of the data model file is incorrect.

• Please check if the data model file that does
not exist is not selected.
• Please set the full path of the file within 1 to 242
characters.

2701H

Error

OthersAn unexpected error occurred while opening thedata model file.

• Please perform partial export of Management
Shell Explorer, and read the data model fileagain.
• If the problem is not resolved, please contact
the Edgecross Consortium.

2702H

Error

OthersSupplementalData.acd is corrupted.

When SupplementalData.acd is changed, it may
not be read.
Perform either of the following.
• Read the same data model file again.
• Read other data model file.

2703H

Error

OthersAn unexpected error occurred during theanalysis of the XML file.

• Please perform partial export of Management
Shell Explorer, and read the data model fileagain.
• If the problem is not resolved, please contact
the Edgecross Consortium.

426

11 TROUBLESHOOTING
11.7 Code List for Data Model ImportCode

Result

Type

Cause

Corrective action

2704H

Error

OthersIncorrect definition was detected during theverification of the XML file.

• Please check if the format of the data model file
is correct.
• Please select other data model file and executeit again.

2705H

Error

Others

The component of the data model file isincorrect.

• Please check if the following folder exists after
the data model file is opened.
- DataModelFiles• Please check if the following files exist in the
DataModelFiles folder after the data model fileis opened.
- DataModel.xml- SupplementalData.acd• Please check if there are no unnecessary files
or folders after the data model file is opened.

2706H

Error

OthersThe version of the data model file is notsupported.

• Please check if the version of the data model
file is 1.00 or later and earlier than 2.00.

2707H

Error

OthersThe version of the XML specifications describedin the XML file is not supported.

Please check if the XML file is described using
XML 1.0.

2708H

Error

Others

The character code of the XML file is notsupported.

Please check if the character code of the XML fileis UTF-8.

2709H

Error

OthersDTD is prohibited by the specifications of the
XML file.

Please remove the description of DTD from theXML file.

2800H

Warning

Component

The component name has been changed from{0} to {1} because it is duplicated.
• {0}: Component name before change• {1}: Component name after change



2901H

WarningResource

The following message has been reported
during the check performed by the datacollector.

Please check the message or data collectormanual, and then confirm whether there are any
problems with the current setting.
{0}{1} Version {2} ({3})• {0}: Message returned from the data collector• {1}: Data collector name• {2}: Data collector version (integer without zero
padding (up to 4 digits))• {3}: Developer

2902H

WarningResource

The location has been changed from {0} to {1}during the check performed by the datacollector.
{2} Version {3} ({4})• {0}: Location before change• {1}: Location after change• {2}: Data collector name• {3}: Data collector version (integer without
zero padding (up to 4 digits))• {4}: Developer



2903H

WarningResource

The data type has been changed from {0} to {1}during the check performed by the datacollector.\n{2} Version {3} ({4})• {0}: Location before change• {1}: Location after change• {2}: Data collector name• {3}: Data collector version (integer without
zero padding (up to 4 digits))• {4}: Developer



2904H

WarningResource

The number of characters has been changed
from {0} to {1} during the check performed by thedata collector.\n{2} Version {3} ({4})• {0}: Location before change• {1}: Location after change• {2}: Data collector name• {3}: Data collector version (integer without
zero padding (up to 4 digits))• {4}: Developer

11 TROUBLESHOOTING
11.7 Code List for Data Model Import

11

427

Code

Result

Type

Cause

Corrective action

2A00H

Warning

Access target device
setting

The setting name has been changed from {0} to{1} because it is duplicated.
• {0}: Setting name before change• {1}: Setting name after change



2A01H

Warning

Access target device
setting

The Target Device setting "{0}" using a dummy
data collector has been generated.
• {0}: Generated access target device setting
name

To change the Target Device setting to the one
using another data collector, please replace theTarget Device setting in the Target Device settingbatch replacement screen.

2C00H

Error

Component

The number of components exceeds the
maximum number by {0}.
• {0}: Number of components exceeding the
maximum number

Please set the total of the components stored in
the data model file and the ones thatManagement Shell has to 1000 or less.

2C01H

Error

Component

The number of layers of the component exceeds
the maximum number by {0}.
• {0}: Number of layers exceeding the maximum
numberPlease set the total of the layers when thecomponents stored in the data model file areadded to the component tree of Management
Shell to 32 or less.

2C02H

Error

Component

The icon file name exceeds the maximum
number of characters by {0}.
• {0}: Number of characters exceeding the
maximum number

Please change the icon file name exceeding the
maximum number of characters to a different file
name.

2D00H

Error

Resource

The following message has been reported fromthe check by the Data collector.

Please refer to the Data collector manual andcheck if the Data collector supports the data
model import function.
If it is supported, please correct the message
contents.\n{0}{1} Version {2} ({3})• {0}: Message returned from the data collector• {1}: Data collector name• {2}: Data collector version (integer without zero
padding (up to 4 digits))• {3}: Developer

2D03H

Error

Resource

The data collector to be used does not satisfy
the implementation requirements of the
Edgecross specifications.

Please contact the developer of the datacollector.\n{0} Version {1} ({2})• {0}: Data collector name• {1}: Data collector version (integer without zero
padding (up to 4 digits))• {2}: Developer

2E00H

Error

Access target device
setting

The setting name exceeds the maximum
number of characters by {0} when it isautomatically renamed.
• {0}: Number of characters exceeding the
maximum number

Please change the duplicated setting name to adifferent setting name.

2E01H

Error

Access target device
setting

The number of Target Device settings after theimport exceeds the maximum number by {0}.
• {0}: Number of access target device settings
exceeding the maximum number

Please set the total number of Target Device
settings to 100 or less.

2E02H

Error

Access target device
setting

The number of Target Device settings after theimport exceeds the maximum number.

Please try again after deleting at least one Target
Device setting.

2F00H

Error

OthersManagement Shell is stopped.

Please start Management Shell.

2FFFH

Error

OthersAn unexpected error occurred during import.

Please try again after restarting Management
Shell.

428

11 TROUBLESHOOTING
11.7 Code List for Data Model Import

11.8

Error Code List for the One-shot Collection
Function

This section shows the error code list for the one-shot collection function.
Error
code

Error name

Error description

Corrective action

1000H

Management Shell event
registration error

Failed to register the event ofManagement Shell.

• Please check if Management Shell is operating.
• Please check if an error has occurred in Management Shell.
• Please lower the load on Windows by closing other applications.
• Please restart the one-shot collection setting.
• When the time and date of Windows were changed, please restartManagement Shell.

1001HManagement Shell event
clearing error

Failed to clear the event ofManagement Shell.

• Please check if Management Shell is operating.
• Please check if an error has occurred in Management Shell.
• Please lower the load on Windows by closing other applications.
• Please restart the one-shot collection setting.
• When the time and date of Windows were changed, please restartManagement Shell.

1002HManagement Shell
communication error

Failed to communicate withManagement Shell.

• Please check if Management Shell is operating.
• Please check if an error has occurred in Management Shell.
• Please lower the load on Windows by closing other applications.
• Please restart the one-shot collection setting.
• When the time and date of Windows were changed, please restartManagement Shell.

1100H

Collection target resource
reading error

Failed to read the collection
target resource.

• Please check if Management Shell is operating.
• Please check if an error has occurred in Management Shell.
• Please check if the target data tag resource exists.
• Please check if the collection target resource has read authority.
• When the internal data tag resource (operation) is used, please check theresource specified for the operation term.
• Please set the collection target resource again.
• Please lower the load on Windows by closing other applications.

1101H

Collection target resource
type definition mismatcherror

A data type mismatch of thecollection target resource was
detected.

• Please check if the target data tag resource has been changed.
• Please set the collection target resource again.

1102H

Monitoring target resource
reading error

Failed to read the monitoringtarget resource.

• Please check if Management Shell is operating.
• Please check if an error has occurred in Management Shell.
• Please check if the target data tag resource exists.
• Please check if the monitoring target resource has read authority.
• When the internal data tag resource (operation) is used, please check theresource specified for the operation term.
• Please set the monitoring target resource again.
• Please lower the load on Windows by closing other applications.

1103H

Monitoring target resource
writing error

Failed to write the monitoringtarget resource.

• Please check if Management Shell is operating.
• Please check if an error has occurred in Management Shell.
• Please check if the target data tag resource exists.
• Please check if the monitoring target resource has write authority.
• Please set the monitoring target resource again.
• Please lower the load on Windows by closing other applications.

1104H

Monitoring target resource
type definition mismatcherror

A data type mismatch of themonitoring target resource was
detected.

• Please check if the target data tag resource has been changed.
• Please set the monitoring target resource again.

1105H

Notification target resource
writing error

Failed to write the notification
target resource.

• Please check if Management Shell is operating.
• Please check if an error has occurred in Management Shell.
• Please check if the target data tag resource exists.
• Please check if the notification target resource has write authority.
• Please set the notification target resource again.
• Please lower the load on Windows by closing other applications.

1106H

Notification target resource
type definition mismatcherror

A data type mismatch of thenotification target resource was
detected.

• Please check if the target data tag resource has been changed.
• Please set the notification target resource again.

11 TROUBLESHOOTING
11.8 Error Code List for the One-shot Collection Function

11

429

Errorcode

Error name

Error description

Corrective action

1107H

Collection target resource
information acquisition error

Failed to acquire the collection
target resource information.

• Please check if Management Shell is operating.
• Please check if an error has occurred in Management Shell.
• Please check if the target data tag resource exists.
• When the internal data tag resource (operation) is used, please check theresource specified for the operation term.

1108H

Monitoring target resource
information acquisition error

Failed to acquire the monitoringtarget resource information.

• Please check if Management Shell is operating.
• Please check if an error has occurred in Management Shell.
• Please check if the target data tag resource exists.
• When the internal data tag resource (operation) is used, please check theresource specified for the operation term.

1109H

Notification target resource
information acquisition error

Failed to acquire the notification
target resource information.

• Please check if Management Shell is operating.
• Please check if an error has occurred in Management Shell.
• Please check if the target data tag resource exists.

1110H

Collection target resource
reading authority error

The collection target resource
does not have read authority.

• Please check if the collection target resource has read authority.
• Please set the collection target resource again.

1111H

Monitoring target resource
reading authority error

The monitoring target resource
does not have read authority.

• Please check if the monitoring target resource has read authority.
• Please set the monitoring target resource again.

1112H

Monitoring target resource
writing authority error

The monitoring target resource
does not have write authority.

• Please check if the monitoring target resource has write authority.
• Please set the monitoring target resource again.

1113H

Notification target resource
writing authority error

The notification target resource
does not have write authority.

• Please check if the notification target resource has write authority.
• Please set the notification target resource again.

1200H

Detailed setting error

The detailed setting has notbeen written or has beendamaged.

Please configure the detailed setting again.

1300H

Output name duplication
error

The output names of thecollection target in the collection
setting and the date column inthe saving setting are duplicatedin the detail setting.

Please check the output name setting in the detail setting.

2000H

File saving error

Failed to write the file because
there is not enough free space
available.

Please delete unnecessary files to allocate free space.

2001H

File saving error

Failed to write the file.

• Please check the access authority of the save destination folder.
• When a folder on the network is set to the save destination folder, Pleasecheck if there is any problem in the connection path of the network andwhether the network drive is specified.
• Please check if the other applications have not accessed the saved file.
• Please check if the saving settings are duplicated with those of Real-time
Flow Manager.
• Please change the save destination folder or the prefix of the file name.
• Please lower the load on Windows by closing other applications.

2002H

Save file number error

The file name suffix of the savefile has reached FFFFFFFF.

• Please change the save destination folder or the prefix of the file name.
• Please delete all the save files from the save destination folder.

2003H

Stored file error

Failed to output the stored file.

• Please check the access authority of the save destination folder.
• When a folder on the network is set to the save destination folder, Pleasecheck if there is any problem in the connection path of the network andwhether the network drive is specified.
• Please check if the other applications have not accessed the saved file.
• Please check if the save settings are duplicated with those of Real-time
Flow Manager.
• Please change the save destination folder or the prefix of the file name.
• Please delete all the stored files.
• Please lower the load on Windows by closing other applications.

2004H

File saving error

Failed to delete the files.

• Please check the access authority of the save destination folder.
• When a folder on the network is set to the save destination folder, Pleasecheck if there is any problem in the connection path of the network andwhether the network drive is specified.
• Please check if the other applications have not accessed the saved file.
• Please check if the save settings are duplicated with those of Real-time
Flow Manager.
• Please change the save destination folder or the prefix of the file name.
• Please lower the load on Windows by closing other applications.

3000H

Out of memory error

There is not enough memory
available to execute thisoperation.

• Please close other applications.
• Please restart the industrial PC running this product.

430

11 TROUBLESHOOTING
11.8 Error Code List for the One-shot Collection Function

Errorcode

Error name

Error description

Corrective action

3001H

DB setting error

DB connection setting
parameter is invalid.

• Make sure the DB save setting is correct.
• Check the ODBC error code.

3002H

DB connection error

DB connection failed.

• Please check if the setting of DB saving is correct.
• Please lower the load by reducing the number of collection target resources.
• If the operation statuses of other settings are RUN, please stop theoperation to lower the load.
• Please lower the load on Windows by closing other applications.

3003H

DB connection error

DB connection failed.

• Please make sure the DB save setting is correct.
• Please make sure the ODBC settings are correct.
• Please check the ODBC error code.

3004H

DB SQL execution error

Execution of SQL failed.

• Please check if the setting of DB saving is correct.
• Please lower the load by reducing the number of collection target resources.
• If the operation statuses of other settings are RUN, please stop theoperation to lower the load.
• Please lower the load on Windows by closing other applications.

3005H

DB SQL execution error

Failed to execute SQL because
the output data amount has
exceeded 8160 bytes.

• Please reduce the number of collection target resources.
• Please check the ODBC error code.

3006H

DB SQL execution error

Execution of SQL failed.

• Please make sure the DB save setting is correct.
• Please make sure the ODBC settings are correct.
• Please check the ODBC error code.

3007H

DB disconnection error

Failed to disconnect the DB.

• Please check if the setting of DB saving is correct.
• Please lower the load by reducing the number of collection target resources.
• If the operation statuses of other settings are RUN, please stop theoperation to lower the load.
• Please lower the load on Windows by closing other applications.

3008H

DB disconnection error

Failed to disconnect the DB.

• Please make sure the DB save setting is correct.
• Please make sure the ODBC settings are correct.
• Please check the ODBC error code.

11 TROUBLESHOOTING
11.8 Error Code List for the One-shot Collection Function

11

431

11.9

Exit Code List for the Command Line Interface
Function

This section shows the exit code list for the command line interface function.
Exit
code

Error name

Error description

Corrective action

1000H

First option error• A character string not definedin the first option is specified.
• No option is specified.

Check the option specifications, and specify a correct first option.
Page 98 Option details

1001H

Second option or later error

The second option or later is notcorrect.

Check the cause in the exit code column of the option, then enter a correct
option.
• Help function: Page 98 Specifications• Function version acquisition: Page 99 Specifications• Process flow operating status acquisition: If "1001" is displayed for theexit code• Process flow operation start: If "1001" is displayed for the exit code
• Process flow operation stop: If "1001" is displayed for the exit code

2000H

License agreement error

The license agreement for
Edgecross Basic Software is not
accepted.

Start Real-time Flow Designer or Management Shell Explorer to accept thelicense agreement.

2001H

Multiple startup error

EdgecrossCLI has already been
started.

Check if EdgecrossCLI has already been started. If started, close then start it.

2002H

Simultaneous execution
error

The operating status is changedor the parameters of Real-time
Flow Manager are applied at thesame time as the following
operations in Real-time Flow
Designer:• RUN request (/runrfm)• STOP request (/stoprfm)• Perform these operations after changing the operating status is completed
in Real-time Flow Designer.
• Perform these operations after applying the parameters is completed in
Real-time Flow Designer.

3000H

Internal communication error

Internal communication with
Real-time Flow Manager has
failed.

• Please check if there is any other error.
• Please reduce the load on Windows by closing other applications.
• Start Real-time Flow Designer, and review the collection cycle, number ofcollected data, and processing contents to reduce the load.
• If the industrial PC enters the sleep or pause mode, please close otherapplications that control the sleep or pause mode. Please do not perform
operations that enter the sleep mode.
• Please restart the Industrial PC running this product.

The response of Real-time Flow
Manager for the commandexecution is delayed.

3001H

Real-time Flow Manager
start operation error

A previously accepted start
operation is still being
performed by Real-time Flow
Manager.

Perform a new start operation after changing the operating status of theprevious start operation is completed.

3002H

Real-time Flow Manager
stop operation error

A previously accepted stop
operation is still being
performed by Real-time Flow
Manager.

Perform a new stop operation after changing the operating status of theprevious stop operation is completed.

3003H

Maximum number ofsimultaneous requests
exceeded error for Real-time
Flow Manager operating
status switching

The number of same type ofoperations for changing theoperating status (a start or stop
operation) previously acceptedby Real-time Flow Manager has
reached its maximum number (astart or stop operation is
performed too frequently).

• Perform a new start or stop operation after changing the operating status of
the previous start or stop operation is completed.
• If this error occurs again, reduce the frequency of performing start and stop
operations.

4000H

Internal processing error

An unexpected error occurred ininternal processing.

• Please restart the industrial PC running this product.
• Please reinstall Edgecross Basic Software.
• If the same error occurs again, please consult the Edgecross Consortium.

432

11 TROUBLESHOOTING
11.9 Exit Code List for the Command Line Interface FunctionAPPENDIX
Appendix 1 Real-time Flow Manager Status
This section shows the Real-time Flow Manager status of Real-time Flow Manager.
Refer to the Real-time Flow Manager status when acquiring the status of a process flow.

Address assignment
The following table shows the address assignment of the Real-time Flow Manager status.
AddressName

0 to 399999

Basic area

400000 to 409799

Data collector area

409800 to 420999

IT gateway areaA

APPX
Appendix 1 Real-time Flow Manager Status

433

Real-time Flow Manager status list
The following shows the Real-time Flow Manager status list of Real-time Flow Manager.

Basic area
The following table shows the Real-time Flow Manager status list in the basic area (0 to 399999).
Address indecimal(hexadecimal)

Category name

Name

Initialization timing

Readingor
writing0(0H)

Data Logging Flow No.1

Status• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager

Reading1(1H)

Error code

• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (STOP  RUN)

2 to 34(2H to 22H)

Setting name• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager

35 to 135
(23H to 87H)

Error occurrence process name

136
(88H)

Problem function

137 to 201(89H to C9H)

Data collector file name or IT
gateway file name• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (STOP  RUN)

202 to 234(CAH to EAH)

Data collector name or IT gateway
name235 to 299(EBH to 12BH)

Developer name300
(12CH)

Data collector specification version(integer part) or IT gateway
specification version (integer part)

301(12DH)

Data collector specification version(decimal part) or IT gateway
specification version (decimal part)302 to 305(12EH to 131H)

Data collector version or IT gateway
version

306 to 337(132H to 151H)

System area

338
(152H)

Process data buffer usage rate

339 to 353(153H to 161H)

System area

354 to 355(162H to 163H)

Number of times of data missing

356(164H)

Last data collection time (year)

357(165H)

Last data collection time (month 
day)

358
(166H)

Last data collection time (hour 
minute)359(167H)

Last data collection time (second 
millisecond)

360 to 399(168H to 18FH)

System area

434

APPX
Appendix 1 Real-time Flow Manager Status• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (STOP  RUN)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (STOP  RUN)

Reading
Reading
Reading
Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (STOP  RUN)

ReadingAddress indecimal(hexadecimal)

Category name

Name

Initialization timing

400 to 799(190H to 31FH)

Data Logging Flow No.2

Same as Data Logging Flow No.1 (0 to 399 (0H to 18FH))

800 to 1199
(320H to 4AFH)

Data Logging Flow No.3

1200 to 1599
(4B0H to 63FH)

Data Logging Flow No.4

1600 to 1999
(640H to 7CFH)

Data Logging Flow No.5

2000 to 2399
(7D0H to 95FH)

Data Logging Flow No.6

2400 to 2799
(960H to AEFH)

Data Logging Flow No.7

2800 to 3199
(AF0H to C7FH)

Data Logging Flow No.8

3200 to 3599
(C80H to E0FH)

Data Logging Flow No.9

3600 to 3999
(E10H to F9FH)

Data Logging Flow No.10

4000 to 4399
(FA0H to 112FH)

Data Logging Flow No.11

4400 to 4799
(1130H to
12BFH)

Data Logging Flow No.124800 to 5199
(12C0H to
144FH)

Data Logging Flow No.13

5200 to 5599
(1450H to
15DFH)

Data Logging Flow No.14

5600 to 5999
(15E0H to
176FH)

Data Logging Flow No.15

6000 to 6399
(1770H to
18FFH)

Data Logging Flow No.16

Readingor
writingA

APPX
Appendix 1 Real-time Flow Manager Status435

Address indecimal(hexadecimal)

Category name

Name

6400 to 6799
(1900H to
1A8FH)

Data Logging Flow No.17

Same as Data Logging Flow No.1 (0 to 399 (0H to 18FH))

6800 to 7199
(1A90H to
1C1FH)

Data Logging Flow No.18

7200 to 7599
(1C20H to
1DAFH)

Data Logging Flow No.19

7600 to 7999
(1DB0H to
1F3FH)

Data Logging Flow No.20

8000 to 8399
(1F40H to
20CFH)

Data Logging Flow No.21

8400 to 8799
(20D0H to
225FH)

Data Logging Flow No.22

8800 to 9199
(2260H to
23EFH)

Data Logging Flow No.23

9200 to 9599
(23F0H to
257FH)

Data Logging Flow No.24

9600 to 9999
(2580H to
270FH)

Data Logging Flow No.25

10000 to 10399(2710H to
289FH)

Data Logging Flow No.26

10400 to 10799(28A0H to
2A2FH)

Data Logging Flow No.27

10800 to 11199(2A30H to
2BBFH)

Data Logging Flow No.28

11200 to 11599(2BC0H to
2D4FH)

Data Logging Flow No.29

11600 to 11999(2D50H to
2EDFH)

Data Logging Flow No.30

12000 to 12399(2EE0H to
306FH)

Data Logging Flow No.31

12400 to 12799(3070H to
31FFH)

Data Logging Flow No.32

436

APPX
Appendix 1 Real-time Flow Manager Status

Initialization timing

Readingor
writingAddress indecimal(hexadecimal)

Category name

Name

Initialization timing

12800 to 13199(3200H to
338FH)

Data Diagnosis Flow No.1

Same as Data Logging Flow No.1 (0 to 399 (0H to 18FH))

13200 to 13599(3390H to
351FH)

Data Diagnosis Flow No.2

13600 to 13999(3520H to
36AFH)

Data Diagnosis Flow No.3

14000 to 14399(36B0H to
383FH)

Data Diagnosis Flow No.4

14400 to 14799(3840H to
39CFH)

Data Diagnosis Flow No.5

14800 to 15199(39D0H to
3B5FH)

Data Diagnosis Flow No.6

15200 to 15599(3B60H to
3CEFH)

Data Diagnosis Flow No.7

15600 to 15999(3CF0H to
3E7FH)

Data Diagnosis Flow No.8

16000 to 16399(3E80H to
400FH)

Data Diagnosis Flow No.9

16400 to 16799(4010H to
419FH)

Data Diagnosis Flow No.10

16800 to 17199(41A0H to
432FH)

Data Diagnosis Flow No.11

17200 to 17599(4330H to
44BFH)

Data Diagnosis Flow No.12

17600 to 17999(44C0H to
464FH)

Data Diagnosis Flow No.13

18000 to 18399(4650H to
47DFH)

Data Diagnosis Flow No.14

18400 to 18799(47E0H to
496FH)

Data Diagnosis Flow No.15

18800 to 19199(4970H to
4AFFH)

Data Diagnosis Flow No.16

Readingor
writingA

APPX
Appendix 1 Real-time Flow Manager Status437

Address indecimal(hexadecimal)

Category name

Name

19200 to 19599(4B00H to
4C8FH)

Data Diagnosis Flow No.17

Same as Data Logging Flow No.1 (0 to 399 (0H to 18FH))

19600 to 19999(4C90H to
4E1FH)

Data Diagnosis Flow No.18

20000 to 20399(4E20H to
4FAFH)

Data Diagnosis Flow No.19

20400 to 20799(4FB0H to
513FH)

Data Diagnosis Flow No.20

20800 to 21199(5140H to
52CFH)

Data Diagnosis Flow No.21

21200 to 21599(52D0H to
545FH)

Data Diagnosis Flow No.22

21600 to 21999(5460H to
55EFH)

Data Diagnosis Flow No.23

22000 to 22399(55F0H to
577FH)

Data Diagnosis Flow No.24

22400 to 22799(5780H to
590FH)

Data Diagnosis Flow No.25

22800 to 23199(5910H to
5A9FH)

Data Diagnosis Flow No.26

23200 to 23599(5AA0H to
5C2FH)

Data Diagnosis Flow No.27

23600 to 23999(5C30H to
5DBFH)

Data Diagnosis Flow No.28

24000 to 24399(5DC0H to
5F4FH)

Data Diagnosis Flow No.29

24400 to 24799(5F50H to
60DFH)

Data Diagnosis Flow No.30

24800 to 25199(60E0H to
626FH)

Data Diagnosis Flow No.31

25200 to 25599(6270H to
63FFH)

Data Diagnosis Flow No.32

438

APPX
Appendix 1 Real-time Flow Manager Status

Initialization timing

Readingor
writingAddress indecimal(hexadecimal)

Category name

Name

Initialization timing

Readingor
writing

25600(6400H)

Data Logging Flow No.1 Process
No.1

Status• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager

Reading

25601(6401H)

Error code

• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (STOP  RUN)

25602 to 25604(6402H to6404H)

System area

25605 to 25705(6405H to
6469H)

Setting name• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager

25706(646AH)

Problem function

25707 to 25771(646BH to
64ABH)

Data collector file name or IT
gateway file name• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (STOP  RUN)

25772 to 25804(64ACH to
64CCH)

Data collector name or IT gateway
name25805 to 25869(64CDH to
650DH)Developer name

25870
(650EH)

Data collector specification version(integer part) or IT gateway
specification version (integer part)

25871(650FH)

Data collector specification version(decimal part) or IT gateway
specification version (decimal part)25872 to 25875(6510H to
6513H)

Data collector version or IT gateway
version25876 to 25929(6514H to6549H)

System area

25930 to 26009(654AH to
6599H)

Information of each process only

Process information of the data collection
function
Process information of the data modification
function

26010 to 26054(659AH to
65C6H)

Data storing information

Data storing information

26055 to 26099(65C7H to
65F3H)

Data distribution information

Data distribution information

26100 to 27599(65F4H to
6BCFH)

Data Logging Flow No.1 Process
No.2 to No.4

27600 to 29599(6BD0H to
739FH)

System area

29600 to 31599(73A0H to
7B6FH)

Data Logging Flow No.2 Process
No.1 to No.4

31600 to 33599(7B70H to
833FH)

System area

ReadingA

Reading

Same as Data Logging Flow No.1 Process No.1 (25600 to 26099 (6400H to 65F3H))
Data Logging Flow No.1 Process No.2: 26100 to 26599 (65F4H to 67E7H)
Data Logging Flow No.1 Process No.3: 26600 to 27099 (67E8H to 69DBH)
Data Logging Flow No.1 Process No.4: 27100 to 27599 (69DCH to 6BCFH)

Same as Data Logging Flow No.1 Process No.1 (25600 to 26099 (6400H to 65F3H))
Data Logging Flow No.2 Process No.1: 29600 to 30099 (73A0H to 7593H)
Data Logging Flow No.2 Process No.2: 30100 to 30599 (7594H to 7787H)
Data Logging Flow No.2 Process No.3: 30600 to 31099 (7788H to 797BH)
Data Logging Flow No.2 Process No.4: 31100 to 31599 (797CH to 7B6FH)

APPXAppendix 1 Real-time Flow Manager Status439

Address indecimal(hexadecimal)

Category nameName

33600 to 35599(8340H to
8B0FH)

Data Logging Flow No.3 Process
No.1 to No.4

Same as Data Logging Flow No.1 Process No.1 (25600 to 26099 (6400H to 65F3H))
Data Logging Flow No.3 Process No.1: 33600 to 34099 (8340H to 8533H)
Data Logging Flow No.3 Process No.2: 34100 to 34599 (8534H to 8727H)
Data Logging Flow No.3 Process No.3: 34600 to 35099 (8728H to 891BH)
Data Logging Flow No.3 Process No.4: 35100 to 35599 (891CH to 8B0FH)

35600 to 37599(8B10H to
92DFH)

System area

37600 to 39599(92E0H to
9AAFH)

Data Logging Flow No.4 Process
No.1 to No.4

39600 to 41599(9AB0H to
A27FH)

System area

41600 to 43599(A280H to
AA4FH)

Data Logging Flow No.5 Process
No.1 to No.4

43600 to 45599(AA50H to
B21FH)

System area

45600 to 47599(B220H to
B9EFH)

Data Logging Flow No.6 Process
No.1 to No.4

47600 to 49599(B9F0H to
C1BFH)

System area

49600 to 51599(C1C0H to
C98FH)

Data Logging Flow No.7 Process
No.1 to No.4

51600 to 53599(C990H to
D15FH)

System area

53600 to 55599(D160H to
D92FH)

Data Logging Flow No.8 Process
No.1 to No.4

55600 to 57599(D930H to
E0FFH)

System area

57600 to 59599(E100H to
E8CFH)

Data Logging Flow No.9 Process
No.1 to No.4

59600 to 61599(E8D0H to
F09FH)

System area

61600 to 63599(F0A0H to
F86FH)

Data Logging Flow No.10
Process No.1 to No.4

63600 to 65599(F870H to
1003FH)

System area

440

APPX
Appendix 1 Real-time Flow Manager Status

Initialization timing

Same as Data Logging Flow No.1 Process No.1 (25600 to 26099 (6400H to 65F3H))
Data Logging Flow No.4 Process No.1: 37600 to 38099 (92E0H to 94D3H)
Data Logging Flow No.4 Process No.2: 38100 to 38599 (94D4H to 96C7H)
Data Logging Flow No.4 Process No.3: 38600 to 39099 (96C8H to 98BBH)
Data Logging Flow No.4 Process No.4: 39100 to 39599 (98BCH to 9AAFH)

Same as Data Logging Flow No.1 Process No.1 (25600 to 26099 (6400H to 65F3H))
Data Logging Flow No.5 Process No.1: 41600 to 42099 (A280H to A473H)
Data Logging Flow No.5 Process No.2: 42100 to 42599 (A474H to A667H)
Data Logging Flow No.5 Process No.3: 42600 to 43099 (A668H to A85BH)
Data Logging Flow No.5 Process No.4: 43100 to 43599 (A85CH to AA4FH)

Same as Data Logging Flow No.1 Process No.1 (25600 to 26099 (6400H to 65F3H))
Data Logging Flow No.6 Process No.1: 45600 to 46099 (B220H to B413H)
Data Logging Flow No.6 Process No.2: 46100 to 46599 (B414H to B607H)
Data Logging Flow No.6 Process No.3: 46600 to 47099 (B608H to B7FBH)
Data Logging Flow No.6 Process No.4: 47100 to 47599 (B7FCH to B9EFH)

Same as Data Logging Flow No.1 Process No.1 (25600 to 26099 (6400H to 65F3H))
Data Logging Flow No.7 Process No.1: 49600 to 50099 (C1C0H to C3B3H)
Data Logging Flow No.7 Process No.2: 50100 to 50599 (C3B4H to C5A7H)
Data Logging Flow No.7 Process No.3: 50600 to 51099 (C5A8H to C79BH)
Data Logging Flow No.7 Process No.4: 51100 to 51599 (C79CH to C98FH)

Same as Data Logging Flow No.1 Process No.1 (25600 to 26099 (6400H to 65F3H))
Data Logging Flow No.8 Process No.1: 53600 to 54099 (D160H to D353H)
Data Logging Flow No.8 Process No.2: 54100 to 54599 (D354H to D547H)
Data Logging Flow No.8 Process No.3: 54600 to 55099 (D548H to D73BH)
Data Logging Flow No.8 Process No.4: 55100 to 55599 (D73CH to D92FH)

Same as Data Logging Flow No.1 Process No.1 (25600 to 26099 (6400H to 65F3H))
Data Logging Flow No.9 Process No.1: 57600 to 58099 (E100H to E2F3H)
Data Logging Flow No.9 Process No.2: 58100 to 58599 (E2F4H to E4E7H)
Data Logging Flow No.9 Process No.3: 58600 to 59099 (E4E8H to E6DBH)
Data Logging Flow No.9 Process No.4: 59100 to 59599 (E6DCH to E8CFH)

Same as Data Logging Flow No.1 Process No.1 (25600 to 26099 (6400H to 65F3H))
Data Logging Flow No.10 Process No.1: 61600 to 62099 (F0A0H to F293H)
Data Logging Flow No.10 Process No.2: 62100 to 62599 (F294H to F487H)
Data Logging Flow No.10 Process No.3: 62600 to 63099 (F488H to F67BH)
Data Logging Flow No.10 Process No.4: 63100 to 63599 (F67CH to F86FH)

Readingor
writingAddress indecimal(hexadecimal)

Category name

Name

Initialization timing

65600 to 67599(10040H to
1080FH)

Data Logging Flow No.11
Process No.1 to No.4

Same as Data Logging Flow No.1 Process No.1 (25600 to 26099 (6400H to 65F3H))
Data Logging Flow No.11 Process No.1: 65600 to 66099 (10040H to 10233H)
Data Logging Flow No.11 Process No.2: 66100 to 66599 (10234H to 10427H)
Data Logging Flow No.11 Process No.3: 66600 to 67099 (10428H to 1061BH)
Data Logging Flow No.11 Process No.4: 67100 to 67599 (1061CH to 1080FH)

67600 to 69599(10810H to
10FDFH)

System area

69600 to 71599(10FE0H to
117AFH)

Data Logging Flow No.12
Process No.1 to No.4

71600 to 73599(117B0H to
11F7FH)

System area

73600 to 75599(11F80H to
1274FH)

Data Logging Flow No.13
Process No.1 to No.475600 to 77599(12750H to
12F1FH)

System area

77600 to 79599(12F20H to
136EFH)

Data Logging Flow No.14
Process No.1 to No.4

79600 to 81599(136F0H to
13EBFH)

System area

81600 to 83599(13EC0H to
1468FH)

Data Logging Flow No.15
Process No.1 to No.4

83600 to 85599(14690H to
14E5FH)

System area

85600 to 87599(14E60H to
1562FH)

Data Logging Flow No.16
Process No.1 to No.487600 to 89599(15630H to
15DFFH)

System area

89600 to 91599(15E00H to
165CFH)

Data Logging Flow No.17
Process No.1 to No.4

91600 to 93599(165D0H to
16D9FH)

System area

93600 to 95599(16DA0H to
1756FH)

Data Logging Flow No.18
Process No.1 to No.4

95600 to 97599(17570H to
17D3FH)

System area

Readingor
writing

Same as Data Logging Flow No.1 Process No.1 (25600 to 26099 (6400H to 65F3H))
Data Logging Flow No.12 Process No.1: 69600 to 70099 (10FE0H to 111D3H)
Data Logging Flow No.12 Process No.2: 70100 to 70599 (111D4H to 113C7H)
Data Logging Flow No.12 Process No.3: 70600 to 71099 (113C8H to 115BBH)
Data Logging Flow No.12 Process No.4: 71100 to 71599 (115BCH to 117AFH)

Same as Data Logging Flow No.1 Process No.1 (25600 to 26099 (6400H to 65F3H))
Data Logging Flow No.13 Process No.1: 73600 to 74099 (11F80H to 12173H)
Data Logging Flow No.13 Process No.2: 74100 to 74599 (12174H to 12367H)
Data Logging Flow No.13 Process No.3: 74600 to 75099 (12368H to 1255BH)
Data Logging Flow No.13 Process No.4: 75100 to 75599 (1255CH to 1274FH)

Same as Data Logging Flow No.1 Process No.1 (25600 to 26099 (6400H to 65F3H))
Data Logging Flow No.14 Process No.1: 77600 to 78099 (12F20H to 13113H)
Data Logging Flow No.14 Process No.2: 78100 to 78599 (13114H to 13307H)
Data Logging Flow No.14 Process No.3: 78600 to 79099 (13308H to 134FBH)
Data Logging Flow No.14 Process No.4: 79100 to 79599 (134FCH to 136EFH)

A
Same as Data Logging Flow No.1 Process No.1 (25600 to 26099 (6400H to 65F3H))
Data Logging Flow No.15 Process No.1: 81600 to 82099 (13EC0H to 140B3H)
Data Logging Flow No.15 Process No.2: 82100 to 82599 (140B4H to 142A7H)
Data Logging Flow No.15 Process No.3: 82600 to 83099 (142A8H to 1449BH)
Data Logging Flow No.15 Process No.4: 83100 to 83599 (1449CH to 1468FH)

Same as Data Logging Flow No.1 Process No.1 (25600 to 26099 (6400H to 65F3H))
Data Logging Flow No.16 Process No.1: 85600 to 86099 (14E60H to 15053H)
Data Logging Flow No.16 Process No.2: 86100 to 86599 (15054H to 15247H)
Data Logging Flow No.16 Process No.3: 86600 to 87099 (15248H to 1543BH)
Data Logging Flow No.16 Process No.4: 87100 to 87599 (1543CH to 1562FH)

Same as Data Logging Flow No.1 Process No.1 (25600 to 26099 (6400H to 65F3H))
Data Logging Flow No.17 Process No.1: 89600 to 90099 (15E00H to 15FF3H)
Data Logging Flow No.17 Process No.2: 90100 to 90599 (15FF4H to 161E7H)
Data Logging Flow No.17 Process No.3: 90600 to 91099 (161E8H to 163DBH)
Data Logging Flow No.17 Process No.4: 91100 to 91599 (163DCH to 165CFH)

Same as Data Logging Flow No.1 Process No.1 (25600 to 26099 (6400H to 65F3H))
Data Logging Flow No.18 Process No.1: 93600 to 94099 (16DA0H to 16F93H)
Data Logging Flow No.18 Process No.2: 94100 to 94599 (16F94H to 17187H)
Data Logging Flow No.18 Process No.3: 94600 to 95099 (17188H to 1737BH)
Data Logging Flow No.18 Process No.4: 95100 to 95599 (1737CH to 1756FH)

APPX
Appendix 1 Real-time Flow Manager Status441

Address indecimal(hexadecimal)

Category nameName

97600 to 99599(17D40H to
1850FH)

Data Logging Flow No.19
Process No.1 to No.4

Same as Data Logging Flow No.1 Process No.1 (25600 to 26099 (6400H to 65F3H))
Data Logging Flow No.19 Process No.1: 97600 to 98099 (17D40H to 17F33H)
Data Logging Flow No.19 Process No.2: 98100 to 98599 (17F34H to 18127H)
Data Logging Flow No.19 Process No.3: 98600 to 99099 (18128H to 1831BH)
Data Logging Flow No.19 Process No.4: 99100 to 99599 (1831CH to 1850FH)

99600 to 101599(18510H to
18CDFH)

System area

101600 to
103599(18CE0H to
194AFH)

Data Logging Flow No.20
Process No.1 to No.4

103600 to105599(194B0H to
19C7FH)

System area

105600 to107599(19C80H to
1A44FH)

Data Logging Flow No.21
Process No.1 to No.4

107600 to109599(1A450H to
1AC1FH)

System area

109600 to111599(1AC20H to
1B3EFH)

Data Logging Flow No.22
Process No.1 to No.4

111600 to113599(1B3F0H to
1BBBFH)

System area

113600 to115599(1BBC0H to
1C38FH)

Data Logging Flow No.23
Process No.1 to No.4

115600 to117599(1C390H to
1CB5FH)

System area

117600 to
119599(1CB60H to
1D32FH)

Data Logging Flow No.24
Process No.1 to No.4

119600 to121599(1D330H to
1DAFFH)

System area

121600 to
123599(1DB00H to
1E2CFH)

Data Logging Flow No.25
Process No.1 to No.4

123600 to
125599(1E2D0H to
1EA9FH)

System area

442

APPX
Appendix 1 Real-time Flow Manager Status

Initialization timing

Same as Data Logging Flow No.1 Process No.1 (25600 to 26099 (6400H to 65F3H))
Data Logging Flow No.20 Process No.1: 101600 to 102099 (18CE0H to 18ED3H)
Data Logging Flow No.20 Process No.2: 102100 to 102599 (18ED4H to 190C7H)
Data Logging Flow No.20 Process No.3: 102600 to 103099 (190C8H to 192BBH)
Data Logging Flow No.20 Process No.4: 103100 to 103599 (192BCH to 194AFH)

Same as Data Logging Flow No.1 Process No.1 (25600 to 26099 (6400H to 65F3H))
Data Logging Flow No.21 Process No.1: 105600 to 106099 (19C80H to 19E73H)
Data Logging Flow No.21 Process No.2: 106100 to 106599 (19E74H to 1A067H)
Data Logging Flow No.21 Process No.3: 106600 to 107099 (1A068H to 1A25BH)
Data Logging Flow No.21 Process No.4: 107100 to 107599 (1A25CH to 1A44FH)

Same as Data Logging Flow No.1 Process No.1 (25600 to 26099 (6400H to 65F3H))
Data Logging Flow No.22 Process No.1: 109600 to 110099 (1AC20H to 1AE13H)
Data Logging Flow No.22 Process No.2: 110100 to 110599 (1AE14H to 1B007H)
Data Logging Flow No.22 Process No.3: 110600 to 111099 (1B008H to 1B1FBH)
Data Logging Flow No.22 Process No.4: 111100 to 111599 (1B1FCH to 1B3EFH)

Same as Data Logging Flow No.1 Process No.1 (25600 to 26099 (6400H to 65F3H))
Data Logging Flow No.23 Process No.1: 113600 to 114099 (1BBC0H to 1BDB3H)
Data Logging Flow No.23 Process No.2: 114100 to 114599 (1BDB4H to 1BFA7H)
Data Logging Flow No.23 Process No.3: 114600 to 115099 (1BFA8H to 1C19BH)
Data Logging Flow No.23 Process No.4: 115100 to 115599 (1C19CH to 1C38FH)

Same as Data Logging Flow No.1 Process No.1 (25600 to 26099 (6400H to 65F3H))
Data Logging Flow No.24 Process No.1: 117600 to 118099 (1CB60H to 1CD53H)
Data Logging Flow No.24 Process No.2: 118100 to 118599 (1CD54H to 1CF47H)
Data Logging Flow No.24 Process No.3: 118600 to 119099 (1CF48H to 1D13BH)
Data Logging Flow No.24 Process No.4: 119100 to 119599 (1D13CH to 1D32FH)

Same as Data Logging Flow No.1 Process No.1 (25600 to 26099 (6400H to 65F3H))
Data Logging Flow No.25 Process No.1: 121600 to 122099 (1DB00H to 1DCF3H)
Data Logging Flow No.25 Process No.2: 122100 to 122599 (1DCF4H to 1DEE7H)
Data Logging Flow No.25 Process No.3: 122600 to 123099 (1DEE8H to 1E0DBH)
Data Logging Flow No.25 Process No.4: 123100 to 123599 (1E0DCH to 1E2CFH)

Readingor
writingAddress indecimal(hexadecimal)

Category name

Name

Initialization timing

125600 to
127599(1EAA0H to
1F26FH)

Data Logging Flow No.26
Process No.1 to No.4

Same as Data Logging Flow No.1 Process No.1 (25600 to 26099 (6400H to 65F3H))
Data Logging Flow No.26 Process No.1: 125600 to 126099 (1EAA0H to 1EC93H)
Data Logging Flow No.26 Process No.2: 126100 to 126599 (1EC94H to 1EE87H)
Data Logging Flow No.26 Process No.3: 126600 to 127099 (1EE88H to 1F07BH)
Data Logging Flow No.26 Process No.4: 127100 to 127599 (1F07CH to 1F26FH)

127600 to129599(1F270H to
1FA3FH)

System area

129600 to131599(1FA40H to
2020FH)

Data Logging Flow No.27
Process No.1 to No.4

131600 to
133599(20210H to
209DFH)

System area

133600 to
135599(209E0H to
211AFH)

Data Logging Flow No.28
Process No.1 to No.4

135600 to137599(211B0H to
2197FH)

System area

137600 to139599(21980H to
2214FH)

Data Logging Flow No.29
Process No.1 to No.4

139600 to141599(22150H to
2291FH)

System area

141600 to
143599(22920H to
230EFH)

Data Logging Flow No.30
Process No.1 to No.4

143600 to
145599(230F0H to
238BFH)

System area

145600 to147599(238C0H to
2408FH)

Data Logging Flow No.31
Process No.1 to No.4

147600 to
149599(24090H to
2485FH)

System area

149600 to
151599(24860H to
2502FH)

Data Logging Flow No.32
Process No.1 to No.4

151600 to
153599(25030H to
257FFH)

System area

Readingor
writing

Same as Data Logging Flow No.1 Process No.1 (25600 to 26099 (6400H to 65F3H))
Data Logging Flow No.27 Process No.1: 129600 to 130099 (1FA40H to 1FC33H)
Data Logging Flow No.27 Process No.2: 130100 to 130599 (1FC34H to 1FE27H)
Data Logging Flow No.27 Process No.3: 130600 to 131099 (1FE28H to 2001BH)
Data Logging Flow No.27 Process No.4: 131100 to 131599 (2001CH to 2020FH)

Same as Data Logging Flow No.1 Process No.1 (25600 to 26099 (6400H to 65F3H))
Data Logging Flow No.28 Process No.1: 133600 to 134099 (209E0H to 20BD3H)
Data Logging Flow No.28 Process No.2: 134100 to 134599 (20BD4H to 20DC7H)
Data Logging Flow No.28 Process No.3: 134600 to 135099 (20DC8H to 20FBBH)
Data Logging Flow No.28 Process No.4: 135100 to 135599 (20FBCH to 211AFH)

Same as Data Logging Flow No.1 Process No.1 (25600 to 26099 (6400H to 65F3H))
Data Logging Flow No.29 Process No.1: 137600 to 138099 (21980H to 21B73H)
Data Logging Flow No.29 Process No.2: 138100 to 138599 (21B74H to 21D67H)
Data Logging Flow No.29 Process No.3: 138600 to 139099 (21D68H to 21F5BH)
Data Logging Flow No.29 Process No.4: 139100 to 139599 (21F5CH to 2214FH)

A

Same as Data Logging Flow No.1 Process No.1 (25600 to 26099 (6400H to 65F3H))
Data Logging Flow No.30 Process No.1: 141600 to 142099 (22920H to 22B13H)
Data Logging Flow No.30 Process No.2: 142100 to 142599 (22B14H to 22D07H)
Data Logging Flow No.30 Process No.3: 142600 to 143099 (22D08H to 22EFBH)
Data Logging Flow No.30 Process No.4: 143100 to 143599 (22EFCH to 230EFH)

Same as Data Logging Flow No.1 Process No.1 (25600 to 26099 (6400H to 65F3H))
Data Logging Flow No.31 Process No.1: 145600 to 146099 (238C0H to 23AB3H)
Data Logging Flow No.31 Process No.2: 146100 to 146599 (23AB4H to 23CA7H)
Data Logging Flow No.31 Process No.3: 146600 to 147099 (23CA8H to 23E9BH)
Data Logging Flow No.31 Process No.4: 147100 to 147599 (23E9CH to 2408FH)

Same as Data Logging Flow No.1 Process No.1 (25600 to 26099 (6400H to 65F3H))
Data Logging Flow No.32 Process No.1: 149600 to 150099 (24860H to 24A53H)
Data Logging Flow No.32 Process No.2: 150100 to 150599 (24A54H to 24C47H)
Data Logging Flow No.32 Process No.3: 150600 to 151099 (24C48H to 24E3BH)
Data Logging Flow No.32 Process No.4: 151100 to 151599 (24E3CH to 2502FH)

APPX
Appendix 1 Real-time Flow Manager Status443

Address indecimal(hexadecimal)

Category name

Name

Initialization timing

Readingor
writing

153600(25800H)

Data Diagnosis Flow No.1
Process No.1

Status• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager

Reading

153601(25801H)

Error code

• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (STOP  RUN)

153602 to153604(25802H to25804H)

System area

153605 to
153705(25805H to25869H)

Setting name• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager

153706(2586AH)

Problem function

153707 to153771(2586BH to258ABH)

Data collector file name or IT
gateway file name• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (STOP  RUN)

153772 to153804(258ACH to258CCH)

Data collector name or IT gateway
name153805 to
153869(258CDH to
2590DH)

Developer name

153870(2590EH)

Data collector specification version(integer part) or IT gateway
specification version (integer part)

153871(2590FH)

Data collector specification version(decimal part) or IT gateway
specification version (decimal part)

153872 to153875(25910H to
25913H)

Data collector version or IT gateway
version

153876 to153929(25914H to25949H)

System area

153930 to
154009(2594AH to
25999H)

Information of each process only

Process information of the data collection
function
Process information of the data modification
function
Process information of the data diagnosis
function
Process information of the feedback
function

154010 to
154054(2599AH to
259C6H)

Data storing information

Data storing information

154055 to154099(259C7H to259F3H)

Data distribution information

Data distribution information

444

APPX
Appendix 1 Real-time Flow Manager Status

Reading

ReadingAddress indecimal(hexadecimal)

Category name

Name

Initialization timing

Readingor
writing154100 to
156599(259F4H to
263B7H)

Data Diagnosis Flow No.1
Process No.2 to No.6

Same as Data Diagnosis Flow No.1 Process No.1 (153600 to 154099 (25800H to 259F3H))
Data Diagnosis Flow No.1 Process No.2: 154100 to 154599 (259F4H to 25BE7H)
Data Diagnosis Flow No.1 Process No.3: 154600 to 155099 (25BE8H to 25DDBH)
Data Diagnosis Flow No.1 Process No.4: 155100 to 155599 (25DDCH to 25FCFH)
Data Diagnosis Flow No.1 Process No.5: 155600 to 156099 (25FD0H to 261C3H)
Data Diagnosis Flow No.1 Process No.6: 156100 to 156599 (261C4H to 263B7H)

156600 to157599(263B8H to2679FH)

System area

157600 to
160599(267A0H to27357H)

Data Diagnosis Flow No.2
Process No.1 to No.6

160600 to
161599(27358H to2773FH)

System area

161600 to164599(27740H to
282F7H)

Data Diagnosis Flow No.3
Process No.1 to No.6

164600 to
165599(282F8H to
286DFH)

System area

165600 to
168599(286E0H to29297H)

Data Diagnosis Flow No.4
Process No.1 to No.6

168600 to
169599(29298H to2967FH)

System area

169600 to
172599(29680H to
2A237H)

Data Diagnosis Flow No.5
Process No.1 to No.6

172600 to173599(2A238H to
2A61FH)

System area

173600 to176599(2A620H to
2B1D7H)

Data Diagnosis Flow No.6
Process No.1 to No.6

176600 to
177599(2B1D8H to
2B5BFH)

System area

Same as Data Diagnosis Flow No.1 Process No.1 (153600 to 154099 (25800H to 259F3H))
Data Diagnosis Flow No.2 Process No.1: 157600 to 158099 (267A0H to 26993H)
Data Diagnosis Flow No.2 Process No.2: 158100 to 158599 (26994H to 26B87H)
Data Diagnosis Flow No.2 Process No.3: 158600 to 159099 (26B88H to 26D7BH)
Data Diagnosis Flow No.2 Process No.4: 159100 to 159599 (26D7CH to 26F6FH)
Data Diagnosis Flow No.2 Process No.5: 159600 to 160099 (26F70H to 27163H)
Data Diagnosis Flow No.2 Process No.6: 160100 to 160599 (27164H to 27357H)

Same as Data Diagnosis Flow No.1 Process No.1 (153600 to 154099 (25800H to 259F3H))
Data Diagnosis Flow No.3 Process No.1: 161600 to 162099 (27740H to 27933H)
Data Diagnosis Flow No.3 Process No.2: 162100 to 162599 (27934H to 27B27H)
Data Diagnosis Flow No.3 Process No.3: 162600 to 163099 (27B28H to 27D1BH)
Data Diagnosis Flow No.3 Process No.4: 163100 to 163599 (27D1CH to 27F0FH)
Data Diagnosis Flow No.3 Process No.5: 163600 to 164099 (27F10H to 28103H)
Data Diagnosis Flow No.3 Process No.6: 164100 to 164599 (28104H to 282F7H)

A

Same as Data Diagnosis Flow No.1 Process No.1 (153600 to 154099 (25800H to 259F3H))
Data Diagnosis Flow No.4 Process No.1: 165600 to 166099 (286E0H to 288D3H)
Data Diagnosis Flow No.4 Process No.2: 166100 to 166599 (288D4H to 28AC7H)
Data Diagnosis Flow No.4 Process No.3: 166600 to 167099 (28AC8H to 28CBBH)
Data Diagnosis Flow No.4 Process No.4: 167100 to 167599 (28CBCH to 28EAFH)
Data Diagnosis Flow No.4 Process No.5: 167600 to 168099 (28EB0H to 290A3H)
Data Diagnosis Flow No.4 Process No.6: 168100 to 168599 (290A4H to 29297H)

Same as Data Diagnosis Flow No.1 Process No.1 (153600 to 154099 (25800H to 259F3H))
Data Diagnosis Flow No.5 Process No.1: 169600 to 170099 (29680H to 29873H)
Data Diagnosis Flow No.5 Process No.2: 170100 to 170599 (29874H to 29A67H)
Data Diagnosis Flow No.5 Process No.3: 170600 to 171099 (29A68H to 29C5BH)
Data Diagnosis Flow No.5 Process No.4: 171100 to 171599 (29C5CH to 29E4FH)
Data Diagnosis Flow No.5 Process No.5: 171600 to 172099 (29E50H to 2A043H)
Data Diagnosis Flow No.5 Process No.6: 172100 to 172599 (2A044H to 2A237H)

Same as Data Diagnosis Flow No.1 Process No.1 (153600 to 154099 (25800H to 259F3H))
Data Diagnosis Flow No.6 Process No.1: 173600 to 174099 (2A620H to 2A813H)
Data Diagnosis Flow No.6 Process No.2: 174100 to 174599 (2A814H to 2AA07H)
Data Diagnosis Flow No.6 Process No.3: 174600 to 175099 (2AA08H to 2ABFBH)
Data Diagnosis Flow No.6 Process No.4: 175100 to 175599 (2ABFCH to 2ADEFH)
Data Diagnosis Flow No.6 Process No.5: 175600 to 176099 (2ADF0H to 2AFE3H)
Data Diagnosis Flow No.6 Process No.6: 176100 to 176599 (2AFE4H to 2B1D7H)

APPX
Appendix 1 Real-time Flow Manager Status445

Address indecimal(hexadecimal)

Category name

Name

177600 to
180599(2B5C0H to
2C177H)

Data Diagnosis Flow No.7
Process No.1 to No.6

Same as Data Diagnosis Flow No.1 Process No.1 (153600 to 154099 (25800H to 259F3H))
Data Diagnosis Flow No.7 Process No.1: 177600 to 178099 (2B5C0H to 2B7B3H)
Data Diagnosis Flow No.7 Process No.2: 178100 to 178599 (2B7B4H to 2B9A7H)
Data Diagnosis Flow No.7 Process No.3: 178600 to 179099 (2B9A8H to 2BB9BH)
Data Diagnosis Flow No.7 Process No.4: 179100 to 179599 (2BB9CH to 2BD8FH)
Data Diagnosis Flow No.7 Process No.5: 179600 to 180099 (2BD90H to 2BF83H)
Data Diagnosis Flow No.7 Process No.6: 180100 to 180599 (2BF84H to 2C177H)

180600 to
181599(2C178H to
2C55FH)

System area

181600 to184599(2C560H to
2D117H)

Data Diagnosis Flow No.8
Process No.1 to No.6

184600 to185599(2D118H to
2D4FFH)

System area

185600 to
188599(2D500H to
2E0B7H)

Data Diagnosis Flow No.9
Process No.1 to No.6

188600 to189599(2E0B8H to
2E49FH)

System area

189600 to
192599(2E4A0H to
2F057H)

Data Diagnosis Flow No.10
Process No.1 to No.6

192600 to
193599(2F058H to
2F43FH)

System area

193600 to
196599(2F440H to
2FFF7H)

Data Diagnosis Flow No.11
Process No.1 to No.6

196600 to
197599(2FFF8H to
303DFH)

System area

197600 to
200599(303E0H to
30F97H)

Data Diagnosis Flow No.12
Process No.1 to No.6

446

APPX
Appendix 1 Real-time Flow Manager Status

Initialization timing

Readingor
writing

Same as Data Diagnosis Flow No.1 Process No.1 (153600 to 154099 (25800H to 259F3H))
Data Diagnosis Flow No.8 Process No.1: 181600 to 182099 (2C560H to 2C753H)
Data Diagnosis Flow No.8 Process No.2: 182100 to 182599 (2C754H to 2C947H)
Data Diagnosis Flow No.8 Process No.3: 182600 to 183099 (2C948H to 2CB3BH)
Data Diagnosis Flow No.8 Process No.4: 183100 to 183599 (2CB3CH to 2CD2FH)
Data Diagnosis Flow No.8 Process No.5: 183600 to 184099 (2CD30H to 2CF23H)
Data Diagnosis Flow No.8 Process No.6: 184100 to 184599 (2CF24H to 2D117H)

Same as Data Diagnosis Flow No.1 Process No.1 (153600 to 154099 (25800H to 259F3H))
Data Diagnosis Flow No.9 Process No.1: 185600 to 186099 (2D500H to 2D6F3H)
Data Diagnosis Flow No.9 Process No.2: 186100 to 186599 (2D6F4H to 2D8E7H)
Data Diagnosis Flow No.9 Process No.3: 186600 to 187099 (2D8E8H to 2DADBH)
Data Diagnosis Flow No.9 Process No.4: 187100 to 187599 (2DADCH to 2DCCFH)
Data Diagnosis Flow No.9 Process No.5: 187600 to 188099 (2DCD0H to 2DEC3H)
Data Diagnosis Flow No.9 Process No.6: 188100 to 188599 (2DEC4H to 2E0B7H)

Same as Data Diagnosis Flow No.1 Process No.1 (153600 to 154099 (25800H to 259F3H))
Data Diagnosis Flow No.10 Process No.1: 189600 to 190099 (2E4A0H to 2E693H)
Data Diagnosis Flow No.10 Process No.2: 190100 to 190599 (2E694H to 2E887H)
Data Diagnosis Flow No.10 Process No.3: 190600 to 191099 (2E888H to 2EA7BH)
Data Diagnosis Flow No.10 Process No.4: 191100 to 191599 (2EA7CH to 2EC6FH)
Data Diagnosis Flow No.10 Process No.5: 191600 to 192099 (2EC70H to 2EE63H)
Data Diagnosis Flow No.10 Process No.6: 192100 to 192599 (2EE64H to 2F057H)

Same as Data Diagnosis Flow No.1 Process No.1 (153600 to 154099 (25800H to 259F3H))
Data Diagnosis Flow No.11 Process No.1: 193600 to 194099 (2F440H to 2F633H)
Data Diagnosis Flow No.11 Process No.2: 194100 to 194599 (2F634H to 2F827H)
Data Diagnosis Flow No.11 Process No.3: 194600 to 195099 (2F828H to 2FA1BH)
Data Diagnosis Flow No.11 Process No.4: 195100 to 195599 (2FA1CH to 2FC0FH)
Data Diagnosis Flow No.11 Process No.5: 195600 to 196099 (2FC10H to 2FE03H)
Data Diagnosis Flow No.11 Process No.6: 196100 to 196599 (2FE04H to 2FFF7H)

Same as Data Diagnosis Flow No.1 Process No.1 (153600 to 154099 (25800H to 259F3H))
Data Diagnosis Flow No.12 Process No.1: 197600 to 198099 (303E0H to 305D3H)
Data Diagnosis Flow No.12 Process No.2: 198100 to 198599 (305D4H to 307C7H)
Data Diagnosis Flow No.12 Process No.3: 198600 to 199099 (307C8H to 309BBH)
Data Diagnosis Flow No.12 Process No.4: 199100 to 199599 (309BCH to 30BAFH)
Data Diagnosis Flow No.12 Process No.5: 199600 to 200099 (30BB0H to 30DA3H)
Data Diagnosis Flow No.12 Process No.6: 200100 to 200599 (30DA4H to 30F97H)

Address indecimal(hexadecimal)

Category name200600 to
201599(30F98H to
3137FH)

System area

201600 to
204599(31380H to
31F37H)

Data Diagnosis Flow No.13
Process No.1 to No.6

204600 to
205599(31F38H to
3231FH)

System area

205600 to
208599(32320H to
32ED7H)

Data Diagnosis Flow No.14
Process No.1 to No.6

208600 to
209599(32ED8H to
332BFH)

System area

209600 to
212599(332C0H to
33E77H)

Data Diagnosis Flow No.15
Process No.1 to No.6

212600 to
213599(33E78H to3425FH)

System area

213600 to216599(34260H to
34E17H)

Data Diagnosis Flow No.16
Process No.1 to No.6

216600 to217599(34E18H to
351FFH)

System area

217600 to
220599(35200H to
35DB7H)

Data Diagnosis Flow No.17
Process No.1 to No.6

220600 to
221599(35DB8H to3619FH)

System area

Name

Initialization timing

Readingor
writing

Same as Data Diagnosis Flow No.1 Process No.1 (153600 to 154099 (25800H to 259F3H))
Data Diagnosis Flow No.13 Process No.1: 201600 to 202099 (31380H to 31573H)
Data Diagnosis Flow No.13 Process No.2: 202100 to 202599 (31574H to 31767H)
Data Diagnosis Flow No.13 Process No.3: 202600 to 203099 (31768H to 3195BH)
Data Diagnosis Flow No.13 Process No.4: 203100 to 203599 (3195CH to 31B4FH)
Data Diagnosis Flow No.13 Process No.5: 203600 to 204099 (31B50H to 31D43H)
Data Diagnosis Flow No.13 Process No.6: 204100 to 204599 (31D44H to 31F37H)

Same as Data Diagnosis Flow No.1 Process No.1 (153600 to 154099 (25800H to 259F3H))
Data Diagnosis Flow No.14 Process No.1: 205600 to 206099 (32320H to 32513H)
Data Diagnosis Flow No.14 Process No.2: 206100 to 206599 (32514H to 32707H)
Data Diagnosis Flow No.14 Process No.3: 206600 to 207099 (32708H to 328FBH)
Data Diagnosis Flow No.14 Process No.4: 207100 to 207599 (328FCH to 32AEFH)
Data Diagnosis Flow No.14 Process No.5: 207600 to 208099 (32AF0H to 32CE3H)
Data Diagnosis Flow No.14 Process No.6: 208100 to 208599 (32CE4H to 32ED7H)

Same as Data Diagnosis Flow No.1 Process No.1 (153600 to 154099 (25800H to 259F3H))
Data Diagnosis Flow No.15 Process No.1: 209600 to 210099 (332C0H to 334B3H)
Data Diagnosis Flow No.15 Process No.2: 210100 to 210599 (334B4H to 336A7H)
Data Diagnosis Flow No.15 Process No.3: 210600 to 211099 (336A8H to 3389BH)
Data Diagnosis Flow No.15 Process No.4: 211100 to 211599 (3389CH to 33A8FH)
Data Diagnosis Flow No.15 Process No.5: 211600 to 212099 (33A90H to 33C83H)
Data Diagnosis Flow No.15 Process No.6: 212100 to 212599 (33C84H to 33E77H)

A

Same as Data Diagnosis Flow No.1 Process No.1 (153600 to 154099 (25800H to 259F3H))
Data Diagnosis Flow No.16 Process No.1: 213600 to 214099 (34260H to 34453H)
Data Diagnosis Flow No.16 Process No.2: 214100 to 214599 (34454H to 34647H)
Data Diagnosis Flow No.16 Process No.3: 214600 to 215099 (34648H to 3483BH)
Data Diagnosis Flow No.16 Process No.4: 215100 to 215599 (3483CH to 34A2FH)
Data Diagnosis Flow No.16 Process No.5: 215600 to 216099 (34A30H to 34C23H)
Data Diagnosis Flow No.16 Process No.6: 216100 to 216599 (34C24H to 34E17H)

Same as Data Diagnosis Flow No.1 Process No.1 (153600 to 154099 (25800H to 259F3H))
Data Diagnosis Flow No.17 Process No.1: 217600 to 218099 (35200H to 353F3H)
Data Diagnosis Flow No.17 Process No.2: 218100 to 218599 (353F4H to 355E7H)
Data Diagnosis Flow No.17 Process No.3: 218600 to 219099 (355E8H to 357DBH)
Data Diagnosis Flow No.17 Process No.4: 219100 to 219599 (357DCH to 359CFH)
Data Diagnosis Flow No.17 Process No.5: 219600 to 220099 (359D0H to 35BC3H)
Data Diagnosis Flow No.17 Process No.6: 220100 to 220599 (35BC4H to 35DB7H)

APPX
Appendix 1 Real-time Flow Manager Status447

Address indecimal(hexadecimal)

Category nameName

221600 to
224599(361A0H to
36D57H)

Data Diagnosis Flow No.18
Process No.1 to No.6

Same as Data Diagnosis Flow No.1 Process No.1 (153600 to 154099 (25800H to 259F3H))
Data Diagnosis Flow No.18 Process No.1: 221600 to 222099 (361A0H to 36393H)
Data Diagnosis Flow No.18 Process No.2: 222100 to 222599 (36394H to 36587H)
Data Diagnosis Flow No.18 Process No.3: 222600 to 223099 (36588H to 3677BH)
Data Diagnosis Flow No.18 Process No.4: 223100 to 223599 (3677CH to 3696FH)
Data Diagnosis Flow No.18 Process No.5: 223600 to 224099 (36970H to 36B63H)
Data Diagnosis Flow No.18 Process No.6: 224100 to 224599 (36B64H to 36D57H)

224600 to
225599(36D58H to
3713FH)

System area

225600 to228599(37140H to
37CF7H)

Data Diagnosis Flow No.19
Process No.1 to No.6

228600 to
229599(37CF8H to
380DFH)

System area

229600 to232599(380E0H to
38C97H)

Data Diagnosis Flow No.20
Process No.1 to No.6

232600 to
233599(38C98H to
3907FH)

System area

233600 to
236599(39080H to
39C37H)

Data Diagnosis Flow No.21
Process No.1 to No.6

236600 to
237599(39C38H to
3A01FH)

System area

237600 to240599(3A020H to
3ABD7H)

Data Diagnosis Flow No.22
Process No.1 to No.6

240600 to241599(3ABD8H to
3AFBFH)

System area

241600 to
244599(3AFC0H to
3BB77H)

Data Diagnosis Flow No.23
Process No.1 to No.6

448

APPX
Appendix 1 Real-time Flow Manager Status

Initialization timing

Readingor
writing

Same as Data Diagnosis Flow No.1 Process No.1 (153600 to 154099 (25800H to 259F3H))
Data Diagnosis Flow No.19 Process No.1: 225600 to 226099 (37140H to 37333H)
Data Diagnosis Flow No.19 Process No.2: 226100 to 226599 (37334H to 37527H)
Data Diagnosis Flow No.19 Process No.3: 226600 to 227099 (37528H to 3771BH)
Data Diagnosis Flow No.19 Process No.4: 227100 to 227599 (3771CH to 3790FH)
Data Diagnosis Flow No.19 Process No.5: 227600 to 228099 (37910H to 37B03H)
Data Diagnosis Flow No.19 Process No.6: 228100 to 228599 (37B04H to 37CF7H)

Same as Data Diagnosis Flow No.1 Process No.1 (153600 to 154099 (25800H to 259F3H))
Data Diagnosis Flow No.20 Process No.1: 229600 to 230099 (380E0H to 382D3H)
Data Diagnosis Flow No.20 Process No.2: 230100 to 230599 (382D4H to 384C7H)
Data Diagnosis Flow No.20 Process No.3: 230600 to 231099 (384C8H to 386BBH)
Data Diagnosis Flow No.20 Process No.4: 231100 to 231599 (386BCH to 388AFH)
Data Diagnosis Flow No.20 Process No.5: 231600 to 232099 (388B0H to 38AA3H)
Data Diagnosis Flow No.20 Process No.6: 232100 to 232599 (38AA4H to 38C97H)

Same as Data Diagnosis Flow No.1 Process No.1 (153600 to 154099 (25800H to 259F3H))
Data Diagnosis Flow No.21 Process No.1: 233600 to 234099 (39080H to 39273H)
Data Diagnosis Flow No.21 Process No.2: 234100 to 234599 (39274H to 39467H)
Data Diagnosis Flow No.21 Process No.3: 234600 to 235099 (39468H to 3965BH)
Data Diagnosis Flow No.21 Process No.4: 235100 to 235599 (3965CH to 3984FH)
Data Diagnosis Flow No.21 Process No.5: 235600 to 236099 (39850H to 39A43H)
Data Diagnosis Flow No.21 Process No.6: 236100 to 236599 (39A44H to 39C37H)

Same as Data Diagnosis Flow No.1 Process No.1 (153600 to 154099 (25800H to 259F3H))
Data Diagnosis Flow No.22 Process No.1: 237600 to 238099 (3A020H to 3A213H)
Data Diagnosis Flow No.22 Process No.2: 238100 to 238599 (3A214H to 3A407H)
Data Diagnosis Flow No.22 Process No.3: 238600 to 239099 (3A408H to 3A5FBH)
Data Diagnosis Flow No.22 Process No.4: 239100 to 239599 (3A5FCH to 3A7EFH)
Data Diagnosis Flow No.22 Process No.5: 239600 to 240099 (3A7F0H to 3A9E3H)
Data Diagnosis Flow No.22 Process No.6: 240100 to 240599 (3A9E4H to 3ABD7H)

Same as Data Diagnosis Flow No.1 Process No.1 (153600 to 154099 (25800H to 259F3H))
Data Diagnosis Flow No.23 Process No.1: 241600 to 242099 (3AFC0H to 3B1B3H)
Data Diagnosis Flow No.23 Process No.2: 242100 to 242599 (3B1B4H to 3B3A7H)
Data Diagnosis Flow No.23 Process No.3: 242600 to 243099 (3B3A8H to 3B59BH)
Data Diagnosis Flow No.23 Process No.4: 243100 to 243599 (3B59CH to 3B78FH)
Data Diagnosis Flow No.23 Process No.5: 243600 to 244099 (3B790H to 3B983H)
Data Diagnosis Flow No.23 Process No.6: 244100 to 244599 (3B984H to 3BB77H)

Address indecimal(hexadecimal)

Category name244600 to
245599(3BB78H to
3BF5FH)

System area

245600 to
248599(3BF60H to
3CB17H)

Data Diagnosis Flow No.24
Process No.1 to No.6

248600 to
249599(3CB18H to
3CEFFH)

System area

249600 to252599(3CF00H to
3DAB7H)

Data Diagnosis Flow No.25
Process No.1 to No.6

252600 to253599(3DAB8H to
3DE9FH)

System area

253600 to
256599(3DEA0H to
3EA57H)

Data Diagnosis Flow No.26
Process No.1 to No.6

256600 to
257599(3EA58H to
3EE3FH)

System area

257600 to
260599(3EE40H to
3F9F7H)

Data Diagnosis Flow No.27
Process No.1 to No.6

260600 to
261599(3F9F8H to
3FDDFH)

System area

261600 to
264599(3FDE0H to
40997H)

Data Diagnosis Flow No.28
Process No.1 to No.6

264600 to
265599(40998H to
40D7FH)

System area

Name

Initialization timing

Readingor
writing

Same as Data Diagnosis Flow No.1 Process No.1 (153600 to 154099 (25800H to 259F3H))
Data Diagnosis Flow No.24 Process No.1: 245600 to 246099 (3BF60H to 3C153H)
Data Diagnosis Flow No.24 Process No.2: 246100 to 246599 (3C154H to 3C347H)
Data Diagnosis Flow No.24 Process No.3: 246600 to 247099 (3C348H to 3C53BH)
Data Diagnosis Flow No.24 Process No.4: 247100 to 247599 (3C53CH to 3C72FH)
Data Diagnosis Flow No.24 Process No.5: 247600 to 248099 (3C730H to 3C923H)
Data Diagnosis Flow No.24 Process No.6: 248100 to 248599 (3C924H to 3CB17H)

Same as Data Diagnosis Flow No.1 Process No.1 (153600 to 154099 (25800H to 259F3H))
Data Diagnosis Flow No.25 Process No.1: 249600 to 250099 (3CF00H to 3D0F3H)
Data Diagnosis Flow No.25 Process No.2: 250100 to 250599 (3D0F4H to 3D2E7H)
Data Diagnosis Flow No.25 Process No.3: 250600 to 251099 (3D2E8H to 3D4DBH)
Data Diagnosis Flow No.25 Process No.4: 251100 to 251599 (3D4DCH to 3D6CFH)
Data Diagnosis Flow No.25 Process No.5: 251600 to 252099 (3D6D0H to 3D8C3H)
Data Diagnosis Flow No.25 Process No.6: 252100 to 252599 (3D8C4H to 3DAB7H)

Same as Data Diagnosis Flow No.1 Process No.1 (153600 to 154099 (25800H to 259F3H))
Data Diagnosis Flow No.26 Process No.1: 253600 to 254099 (3DEA0H to 3E093H)
Data Diagnosis Flow No.26 Process No.2: 254100 to 254599 (3E094H to 3E287H)
Data Diagnosis Flow No.26 Process No.3: 254600 to 255099 (3E288H to 3E47BH)
Data Diagnosis Flow No.26 Process No.4: 255100 to 255599 (3E47CH to 3E66FH)
Data Diagnosis Flow No.26 Process No.5: 255600 to 256099 (3E670H to 3E863H)
Data Diagnosis Flow No.26 Process No.6: 256100 to 256599 (3E864H to 3EA57H)A

Same as Data Diagnosis Flow No.1 Process No.1 (153600 to 154099 (25800H to 259F3H))
Data Diagnosis Flow No.27 Process No.1: 257600 to 258099 (3EE40H to 3F033H)
Data Diagnosis Flow No.27 Process No.2: 258100 to 258599 (3F034H to 3F227H)
Data Diagnosis Flow No.27 Process No.3: 258600 to 259099 (3F228H to 3F41BH)
Data Diagnosis Flow No.27 Process No.4: 259100 to 259599 (3F41CH to 3F60FH)
Data Diagnosis Flow No.27 Process No.5: 259600 to 260099 (3F610H to 3F803H)
Data Diagnosis Flow No.27 Process No.6: 260100 to 260599 (3F804H to 3F9F7H)

Same as Data Diagnosis Flow No.1 Process No.1 (153600 to 154099 (25800H to 259F3H))
Data Diagnosis Flow No.28 Process No.1: 261600 to 262099 (3FDE0H to 3FFD3H)
Data Diagnosis Flow No.28 Process No.2: 262100 to 262599 (3FFD4H to 401C7H)
Data Diagnosis Flow No.28 Process No.3: 262600 to 263099 (401C8H to 403BBH)
Data Diagnosis Flow No.28 Process No.4: 263100 to 263599 (403BCH to 405AFH)
Data Diagnosis Flow No.28 Process No.5: 263600 to 264099 (405B0H to 407A3H)
Data Diagnosis Flow No.28 Process No.6: 264100 to 264599 (407A4H to 40997H)

APPX
Appendix 1 Real-time Flow Manager Status449

Address indecimal(hexadecimal)

Category nameName

265600 to
268599(40D80H to41937H)

Data Diagnosis Flow No.29
Process No.1 to No.6

Same as Data Diagnosis Flow No.1 Process No.1 (153600 to 154099 (25800H to 259F3H))
Data Diagnosis Flow No.29 Process No.1: 265600 to 266099 (40D80H to 40F73H)
Data Diagnosis Flow No.29 Process No.2: 266100 to 266599 (40F74H to 41167H)
Data Diagnosis Flow No.29 Process No.3: 266600 to 267099 (41168H to 4135BH)
Data Diagnosis Flow No.29 Process No.4: 267100 to 267599 (4135CH to 4154FH)
Data Diagnosis Flow No.29 Process No.5: 267600 to 268099 (41550H to 41743H)
Data Diagnosis Flow No.29 Process No.6: 268100 to 268599 (41744H to 41937H)

268600 to
269599(41938H to
41D1FH)

System area

269600 to
272599(41D20H to
428D7H)

Data Diagnosis Flow No.30
Process No.1 to No.6

272600 to
273599(428D8H to
42CBFH)

System area

273600 to
276599(42CC0H to43877H)

Data Diagnosis Flow No.31
Process No.1 to No.6

276600 to
277599(43878H to
43C5FH)

System area

277600 to
280599(43C60H to44817H)

Data Diagnosis Flow No.32
Process No.1 to No.6

280600 to
289999(44818H to
46CCFH)

System area

290000(46CD0H)

Error Log Information

290001(46CD1H)

450

APPX
Appendix 1 Real-time Flow Manager Status

Initialization timing

Readingor
writing

Same as Data Diagnosis Flow No.1 Process No.1 (153600 to 154099 (25800H to 259F3H))
Data Diagnosis Flow No.30 Process No.1: 269600 to 270099 (41D20H to 41F13H)
Data Diagnosis Flow No.30 Process No.2: 270100 to 270599 (41F14H to 42107H)
Data Diagnosis Flow No.30 Process No.3: 270600 to 271099 (42108H to 422FBH)
Data Diagnosis Flow No.30 Process No.4: 271100 to 271599 (422FCH to 424EFH)
Data Diagnosis Flow No.30 Process No.5: 271600 to 272099 (424F0H to 426E3H)
Data Diagnosis Flow No.30 Process No.6: 272100 to 272599 (426E4H to 428D7H)

Same as Data Diagnosis Flow No.1 Process No.1 (153600 to 154099 (25800H to 259F3H))
Data Diagnosis Flow No.31 Process No.1: 273600 to 274099 (42CC0H to 42EB3H)
Data Diagnosis Flow No.31 Process No.2: 274100 to 274599 (42EB4H to 430A7H)
Data Diagnosis Flow No.31 Process No.3: 274600 to 275099 (430A8H to 4329BH)
Data Diagnosis Flow No.31 Process No.4: 275100 to 275599 (4329CH to 4348FH)
Data Diagnosis Flow No.31 Process No.5: 275600 to 276099 (43490H to 43683H)
Data Diagnosis Flow No.31 Process No.6: 276100 to 276599 (43684H to 43877H)

Same as Data Diagnosis Flow No.1 Process No.1 (153600 to 154099 (25800H to 259F3H))
Data Diagnosis Flow No.32 Process No.1: 277600 to 278099 (43C60H to 43E53H)
Data Diagnosis Flow No.32 Process No.2: 278100 to 278599 (43E54H to 44047H)
Data Diagnosis Flow No.32 Process No.3: 278600 to 279099 (44048H to 4423BH)
Data Diagnosis Flow No.32 Process No.4: 279100 to 279599 (4423CH to 4442FH)
Data Diagnosis Flow No.32 Process No.5: 279600 to 280099 (44430H to 44623H)
Data Diagnosis Flow No.32 Process No.6: 280100 to 280599 (44624H to 44817H)

Number of error occurrences
Latest error log number• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager

ReadingAddress indecimal(hexadecimal)

Category name

Name

Initialization timing

Readingor
writing

290002(46CD2H)

Error Log 1

Error code (error log 1)• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (STOP  RUN)*1• When switching the operating status of aprocess flow (switching any of the process
flows to RUN while all the process flows are
STOP)*2

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (STOP  RUN)*1• When switching the operating status of aprocess flow (switching any of the process
flows to RUN while all the process flows are
STOP)*2

Reading

290003 to290004(46CD3H to
46CD4H)

System area

290005 to290012(46CD5H to
46CDCH)

Error occurrence date and time (error
log 1)

290013(46CDDH)

Problem function

290014 to290078(46CDEH to46D1EH)

Data collector file name or IT
gateway file name290079 to290111(46D1FH to
46D3FH)

Data collector name or IT gatewayname290112 to290176(46D40H to
46D80H)

Developer name290177(46D81H)

Data collector specification version(integer part) or IT gateway
specification version (integer part)

290178(46D82H)

Data collector specification version(decimal part) or IT gateway
specification version (decimal part)

290179 to290182(46D83H to
46D86H)

Data collector version or IT gateway
version290183 to290251(46D87H to
46DCBH)

System areaA

APPX
Appendix 1 Real-time Flow Manager Status451

Address indecimal(hexadecimal)

Category nameName

290252 to290501(46DCCH to
46EC5H)

Error Log 2

Same as Error Log 1 (290002 to 290251 (46CD2H to 46DCBH))

290502 to290751(46EC6H to
46FBFH)

Error Log 3290752 to291001(46FC0H to
470B9H)

Error Log 4291002 to291251(470BAH to
471B3H)

Error Log 5291252 to291501(471B4H to
472ADH)

Error Log 6291502 to291751(472AEH to473A7H)

Error Log 7291752 to292001(473A8H to
474A1H)

Error Log 8292002 to292251(474A2H to4759BH)

Error Log 9292252 to292501(4759CH to47695H)

Error Log 10292502 to292751(47696H to4778FH)

Error Log 11292752 to293001(47790H to
47889H)

Error Log 12293002 to293251(4788AH to
47983H)

Error Log 13

293252 to293501(47984H to
47A7DH)

Error Log 14293502 to293751(47A7EH to47B77H)

Error Log 15

293752 to294001(47B78H to
47C71H)

Error Log 16

294002 to294251(47C72H to
47D6BH)

Error Log 17

452

APPX
Appendix 1 Real-time Flow Manager Status

Initialization timing

Readingor
writingAddress indecimal(hexadecimal)

Category name

Name

Initialization timing

294252 to294501(47D6CH to
47E65H)

Error Log 18

Same as Error Log 1 (290002 to 290251 (46CD2H to 46DCBH))

294502 to294751(47E66H to
47F5FH)

Error Log 19294752 to295001(47F60H to48059H)

Error Log 20295002 to295251(4805AH to
48153H)

Error Log 21295252 to295501(48154H to4824DH)

Error Log 22295502 to295751(4824EH to48347H)

Error Log 23295752 to296001(48348H to48441H)

Error Log 24296002 to296251(48442H to
4853BH)

Error Log 25

296252 to296501(4853CH to48635H)

Error Log 26

296502 to296751(48636H to4872FH)

Error Log 27

296752 to297001(48730H to
48829H)

Error Log 28

297002 to297251(4882AH to
48923H)

Error Log 29297252 to297501(48924H to
48A1DH)

Error Log 30

297502 to297751(48A1EH to
48B17H)

Error Log 31

297752 to298001(48B18H to48C11H)

Error Log 32

298002 to298251(48C12H to
48D0BH)

Error Log 33

Readingor
writingA

APPX
Appendix 1 Real-time Flow Manager Status453

Address indecimal(hexadecimal)

Category nameName

298252 to298501(48D0CH to
48E05H)

Error Log 34

Same as Error Log 1 (290002 to 290251 (46CD2H to 46DCBH))

298502 to298751(48E06H to
48EFFH)

Error Log 35

298752 to299001(48F00H to
48FF9H)

Error Log 36

299002 to299251(48FFAH to
490F3H)

Error Log 37

299252 to299501(490F4H to
491EDH)

Error Log 38

299502 to299751(491EEH to492E7H)

Error Log 39

299752 to300001(492E8H to
493E1H)

Error Log 40

300002 to300251(493E2H to494DBH)

Error Log 41300252 to300501(494DCH to495D5H)

Error Log 42300502 to300751(495D6H to
496CFH)

Error Log 43300752 to301001(496D0H to
497C9H)

Error Log 44

301002 to301251(497CAH to
498C3H)

Error Log 45

301252 to301501(498C4H to499BDH)

Error Log 46301502 to301751(499BEH to49AB7H)

Error Log 47

301752 to302001(49AB8H to
49BB1H)

Error Log 48

302002 to302251(49BB2H to
49CABH)

Error Log 49

454

APPX
Appendix 1 Real-time Flow Manager Status

Initialization timing

Readingor
writingAddress indecimal(hexadecimal)

Category name

Name

Initialization timing

302252 to302501(49CACH to
49DA5H)

Error Log 50

Same as Error Log 1 (290002 to 290251 (46CD2H to 46DCBH))

302502 to302751(49DA6H to
49E9FH)

Error Log 51

302752 to303001(49EA0H to
49F99H)

Error Log 52

303002 to303251(49F9AH to
4A093H)

Error Log 53

303252 to303501(4A094H to
4A18DH)

Error Log 54

303502 to303751(4A18EH to
4A287H)

Error Log 55

303752 to304001(4A288H to
4A381H)

Error Log 56

304002 to304251(4A382H to
4A47BH)

Error Log 57

304252 to304501(4A47CH to
4A575H)

Error Log 58

304502 to304751(4A576H to
4A66FH)

Error Log 59304752 to305001(4A670H to
4A769H)

Error Log 60

305002 to305251(4A76AH to
4A863H)

Error Log 61305252 to305501(4A864H to
4A95DH)

Error Log 62305502 to305751(4A95EH to
4AA57H)

Error Log 63305752 to306001(4AA58H to
4AB51H)

Error Log 64

306002 to399999(4AB52H to
61A7FH)

System area

Readingor
writingA

APPX
Appendix 1 Real-time Flow Manager Status

455

*1

*2

456

The log of an error occurred in a process flow with its operating status switched is cleared.
Then, the remaining error logs are stored again in order of registration from 'Error log 1' and the number of the last registered error log isstored in 'Latest error log number.'
The log of an error occurred in a location other than a process flow is cleared.
Then, the remaining error logs are stored again in order of registration from 'Error log 1' and the number of the last registered error log isstored in 'Latest error log number.'

APPX
Appendix 1 Real-time Flow Manager Status

Data collector area
The following table shows the Real-time Flow Manager status list in the data collector area (400000 to 409799).
Address indecimal(hexadecimal)

Category name

Name

Initialization timing

Readingor
writing

400000 to400099(61A80H to
61AE3H)

System area

400100(61AE4H)

Target Device No.1

Setting enable flag

• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager

Reading

400101(61AE5H)

Connection status• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

400102(61AE6H)

Error code

400103(61AE7H)

Problem function

400104 to400168(61AE8H to
61B28H)

Data collector file name• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (STOP  RUN)

400169 to400201(61B29H to
61B49H)

Data collector name400202 to400266(61B4AH to
61B8AH)

Developer name400267(61B8BH)

Data collector specification version(integer part)

400268(61B8CH)

Data collector specification version(decimal part)

400269 to400272(61B8DH to
61B90H)

Data collector version

400273 to400399(61B91H to
61C0FH)

System areaA

APPX
Appendix 1 Real-time Flow Manager Status457

Address indecimal(hexadecimal)

Category name

Name

400400 to
400699(61C10H to
61D3BH)

Target Device No.2

Same as Target Device No.1 (400100 to 400399 (61AE4H to 61C0FH))

400700 to
400999(61D3CH to
61E67H)

Target Device No.3

401000 to401299(61E68H to
61F93H)

Target Device No.4

401300 to
401599(61F94H to
620BFH)

Target Device No.5

401600 to
401899(620C0H to
621EBH)

Target Device No.6

401900 to
402199(621ECH to62317H)

Target Device No.7402200 to
402499(62318H to62443H)

Target Device No.8

402500 to402799(62444H to6256FH)

Target Device No.9402800 to403099(62570H to
6269BH)

Target Device No.10

403100 to
403399(6269CH to627C7H)

Target Device No.11403400 to
403699(627C8H to
628F3H)

Target Device No.12403700 to
403999(628F4H to
62A1FH)

Target Device No.13

404000 to
404299(62A20H to
62B4BH)

Target Device No.14404300 to
404599(62B4CH to
62C77H)

Target Device No.15

404600 to
404899(62C78H to
62DA3H)

Target Device No.16

404900 to
405199(62DA4H to
62ECFH)

Target Device No.17

458

APPX
Appendix 1 Real-time Flow Manager Status

Initialization timing

Readingor
writingAddress indecimal(hexadecimal)

Category name

Name

Initialization timing

405200 to
405499(62ED0H to
62FFBH)

Target Device No.18

Same as Target Device No.1 (400100 to 400399 (61AE4H to 61C0FH))

405500 to
405799(62FFCH to63127H)

Target Device No.19

405800 to406099(63128H to63253H)

Target Device No.20

406100 to
406399(63254H to6337FH)

Target Device No.21

406400 to
406699(63380H to
634ABH)

Target Device No.22

406700 to
406999(634ACH to635D7H)

Target Device No.23

407000 to
407299(635D8H to63703H)

Target Device No.24

407300 to
407599(63704H to6382FH)

Target Device No.25

407600 to
407899(63830H to
6395BH)

Target Device No.26

407900 to
408199(6395CH to
63A87H)

Target Device No.27

408200 to
408499(63A88H to
63BB3H)

Target Device No.28

408500 to
408799(63BB4H to
63CDFH)

Target Device No.29

408800 to409099(63CE0H to
63E0BH)

Target Device No.30

409100 to
409399(63E0CH to
63F37H)

Target Device No.31

409400 to
409699(63F38H to64063H)

Target Device No.32

409700 to409799(64064H to
640C7H)

System area

Readingor
writingA

APPX
Appendix 1 Real-time Flow Manager Status459

IT gateway area
The following table shows the Real-time Flow Manager status list in the IT gateway area (409800 to 420999).
Address indecimal(hexadecimal)

Category name

Name

Initialization timing

Readingor
writing

409800(640C8H)

IT Gateway Diagnosis
Information No.1

Setting enable flag

• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager

Reading

409801(640C9H)

Connection status• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

409802(640CAH)

Error code409803(640CBH)

Problem function

409804 to409868(640CCH to
6410CH)

IT gateway file name• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (STOP  RUN)

409869 to409901(6410DH to
6412DH)

IT gateway name409902 to
409966(6412EH to6416EH)

Developer name409967(6416FH)

IT gateway specification version(integer part)409968(64170H)

IT gateway specification version(decimal part)409969 to409972(64171H to64174H)

IT gateway version

409973 to410006(64175H to64196H)

System area

410007(64197H)

IT gateway type

410008 to410099(64198H to
641F3H)

System area

410100 to410103(641F4H to
641F7H)IT system connection status of Data
Logging Flow No.1 Process No.1 toNo.4410104 to410105(641F8H to
641F9H)

System area

410106 to410109(641FAH to
641FDH)IT system connection status of Data
Logging Flow No.2 Process No.1 to
No.4

460

APPX
Appendix 1 Real-time Flow Manager Status• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (STOP  RUN)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

ReadingAddress indecimal(hexadecimal)

Category name

Name

410110 to
410111(641FEH to641FFH)IT Gateway Diagnosis
Information No.1

System area

410112 to410115(64200H to64203H)IT system connection status of Data
Logging Flow No.3 Process No.1 toNo.4410116 to
410117(64204H to64205H)

System area

410118 to
410121(64206H to64209H)IT system connection status of Data
Logging Flow No.4 Process No.1 toNo.4410122 to410123(6420AH to
6420BH)

System area

410124 to410127(6420CH to
6420FH)IT system connection status of Data
Logging Flow No.5 Process No.1 toNo.4410128 to
410129(64210H to
64211H)

System area

410130 to
410133(64212H to64215H)IT system connection status of Data
Logging Flow No.6 Process No.1 toNo.4410134 to410135(64216H to64217H)

System area

410136 to
410139(64218H to
6421BH)IT system connection status of Data
Logging Flow No.7 Process No.1 toNo.4410140 to
410141(6421CH to
6421DH)

System area

410142 to410145(6421EH to64221H)IT system connection status of Data
Logging Flow No.8 Process No.1 toNo.4410146 to410147(64222H to64223H)

System area

410148 to
410151(64224H to64227H)IT system connection status of Data
Logging Flow No.9 Process No.1 to
No.4

Initialization timing

Readingor
writing• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading

APPX
Appendix 1 Real-time Flow Manager StatusA

461

Address indecimal(hexadecimal)

Category nameName

410152 to410153(64228H to64229H)IT Gateway Diagnosis
Information No.1

System area

410154 to410157(6422AH to
6422DH)IT system connection status of Data
Logging Flow No.10 Process No.1 toNo.4410158 to
410159(6422EH to
6422FH)

System area

410160 to
410163(64230H to
64233H)IT system connection status of Data
Logging Flow No.11 Process No.1 toNo.4410164 to410165(64234H to64235H)

System area

410166 to410169(64236H to64239H)IT system connection status of Data
Logging Flow No.12 Process No.1 toNo.4410170 to
410171(6423AH to
6423BH)

System area

410172 to410175(6423CH to6423FH)IT system connection status of Data
Logging Flow No.13 Process No.1 toNo.4410176 to410177(64240H to
64241H)

System area

410178 to410181(64242H to64245H)IT system connection status of Data
Logging Flow No.14 Process No.1 toNo.4410182 to410183(64246H to64247H)

System area

410184 to410187(64248H to
6424BH)IT system connection status of Data
Logging Flow No.15 Process No.1 toNo.4410188 to410189(6424CH to6424DH)

System area

410190 to410193(6424EH to64251H)IT system connection status of Data
Logging Flow No.16 Process No.1 to
No.4

462

APPX
Appendix 1 Real-time Flow Manager Status

Initialization timing

Readingor
writing• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

ReadingAddress indecimal(hexadecimal)

Category name

Name

410194 to410195(64252H to64253H)IT Gateway Diagnosis
Information No.1

System area

410196 to410199(64254H to64257H)IT system connection status of Data
Logging Flow No.17 Process No.1 toNo.4410200 to
410201(64258H to64259H)

System area

410202 to410205(6425AH to
6425DH)IT system connection status of Data
Logging Flow No.18 Process No.1 toNo.4410206 to
410207(6425EH to6425FH)

System area

410208 to
410211(64260H to
64263H)IT system connection status of Data
Logging Flow No.19 Process No.1 toNo.4410212 to410213(64264H to64265H)

System area

410214 to410217(64266H to64269H)IT system connection status of Data
Logging Flow No.20 Process No.1 toNo.4410218 to
410219(6426AH to
6426BH)

System area

410220 to
410223(6426CH to6426FH)IT system connection status of Data
Logging Flow No.21 Process No.1 toNo.4410224 to410225(64270H to
64271H)

System area

410226 to410229(64272H to64275H)IT system connection status of Data
Logging Flow No.22 Process No.1 toNo.4410230 to
410231(64276H to64277H)

System area

410232 to410235(64278H to
6427BH)IT system connection status of Data
Logging Flow No.23 Process No.1 to
No.4

Initialization timing

Readingor
writing• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading

APPX
Appendix 1 Real-time Flow Manager Status

A

463

Address indecimal(hexadecimal)

Category nameName

410236 to410237(6427CH to6427DH)IT Gateway Diagnosis
Information No.1

System area

410238 to410241(6427EH to64281H)IT system connection status of Data
Logging Flow No.24 Process No.1 toNo.4410242 to410243(64282H to64283H)

System area

410244 to410247(64284H to64287H)IT system connection status of Data
Logging Flow No.25 Process No.1 toNo.4410248 to410249(64288H to64289H)

System area

410250 to
410253(6428AH to
6428DH)IT system connection status of Data
Logging Flow No.26 Process No.1 toNo.4410254 to410255(6428EH to
6428FH)

System area

410256 to410259(64290H to
64293H)IT system connection status of Data
Logging Flow No.27 Process No.1 toNo.4410260 to
410261(64294H to64295H)

System area

410262 to410265(64296H to64299H)IT system connection status of Data
Logging Flow No.28 Process No.1 toNo.4410266 to410267(6429AH to
6429BH)

System area

410268 to
410271(6429CH to6429FH)IT system connection status of Data
Logging Flow No.29 Process No.1 toNo.4410272 to410273(642A0H to
642A1H)

System area

410274 to410277(642A2H to
642A5H)IT system connection status of Data
Logging Flow No.30 Process No.1 to
No.4

464

APPX
Appendix 1 Real-time Flow Manager Status

Initialization timing

Readingor
writing• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

ReadingAddress indecimal(hexadecimal)

Category nameName

410278 to
410279(642A6H to
642A7H)IT Gateway Diagnosis
Information No.1

System area

410280 to
410283(642A8H to
642ABH)IT system connection status of Data
Logging Flow No.31 Process No.1 toNo.4410284 to410285(642ACH to
642ADH)

System area

410286 to410289(642AEH to
642B1H)IT system connection status of Data
Logging Flow No.32 Process No.1 toNo.4410290 to
410291(642B2H to
642B3H)

System area

410292 to410296(642B4H to
642B8H)IT system connection status of Data
Diagnosis Flow No.1 Process No.1 toNo.5410297(642B9H)

System area

410298 to410302(642BAH to
642BEH)IT system connection status of Data
Diagnosis Flow No.2 Process No.1 toNo.5410303(642BFH)

System area

410304 to410308(642C0H to
642C4H)IT system connection status of Data
Diagnosis Flow No.3 Process No.1 toNo.5410309(642C5H)

System area

410310 to
410314(642C6H to
642CAH)IT system connection status of Data
Diagnosis Flow No.4 Process No.1 toNo.5410315(642CBH)

System area

410316 to410320(642CCH to
642D0H)IT system connection status of Data
Diagnosis Flow No.5 Process No.1 to
No.5

Initialization timing

Readingor
writing• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

ReadingA

APPX
Appendix 1 Real-time Flow Manager Status465

Address indecimal(hexadecimal)

Category name

Name

410321(642D1H)

IT Gateway Diagnosis
Information No.1

System area

410322 to410326(642D2H to
642D6H)IT system connection status of Data
Diagnosis Flow No.6 Process No.1 toNo.5410327(642D7H)

System area

410328 to410332(642D8H to
642DCH)IT system connection status of Data
Diagnosis Flow No.7 Process No.1 toNo.5410333(642DDH)

System area

410334 to410338(642DEH to642E2H)IT system connection status of Data
Diagnosis Flow No.8 Process No.1 toNo.5410339(642E3H)

System area

410340 to
410344(642E4H to
642E8H)IT system connection status of Data
Diagnosis Flow No.9 Process No.1 toNo.5410345(642E9H)

System area

410346 to410350(642EAH to
642EEH)IT system connection status of Data
Diagnosis Flow No.10 Process No.1
to No.5410351(642EFH)

System area

410352 to410356(642F0H to
642F4H)IT system connection status of Data
Diagnosis Flow No.11 Process No.1
to No.5410357(642F5H)

System area

410358 to410362(642F6H to
642FAH)IT system connection status of Data
Diagnosis Flow No.12 Process No.1
to No.5410363(642FBH)

System area

410364 to410368(642FCH to64300H)IT system connection status of Data
Diagnosis Flow No.13 Process No.1
to No.5410369(64301H)

System area

410370 to
410374(64302H to64306H)IT system connection status of Data
Diagnosis Flow No.14 Process No.1
to No.5

466

APPX
Appendix 1 Real-time Flow Manager Status

Initialization timing

Readingor
writing• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

ReadingAddress indecimal(hexadecimal)

Category name

Name

410375(64307H)

IT Gateway Diagnosis
Information No.1

System area

410376 to410380(64308H to
6430CH)IT system connection status of Data
Diagnosis Flow No.15 Process No.1
to No.5410381(6430DH)

System area

410382 to410386(6430EH to64312H)IT system connection status of Data
Diagnosis Flow No.16 Process No.1
to No.5410387(64313H)

System area

410388 to410392(64314H to64318H)IT system connection status of Data
Diagnosis Flow No.17 Process No.1
to No.5410393(64319H)

System area

410394 to410398(6431AH to
6431EH)IT system connection status of Data
Diagnosis Flow No.18 Process No.1
to No.5410399(6431FH)

System area

410400 to
410404(64320H to
64324H)IT system connection status of Data
Diagnosis Flow No.19 Process No.1
to No.5410405(64325H)

System area

410406 to410410(64326H to6432AH)IT system connection status of Data
Diagnosis Flow No.20 Process No.1
to No.5410411(6432BH)

System area

410412 to410416(6432CH to64330H)IT system connection status of Data
Diagnosis Flow No.21 Process No.1
to No.5410417(64331H)

System area

410418 to410422(64332H to64336H)IT system connection status of Data
Diagnosis Flow No.22 Process No.1
to No.5410423(64337H)

System area

410424 to410428(64338H to
6433CH)IT system connection status of Data
Diagnosis Flow No.23 Process No.1
to No.5

Initialization timing

Readingor
writing• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading

APPX
Appendix 1 Real-time Flow Manager StatusA

467

Address indecimal(hexadecimal)

Category name

Name

410429(6433DH)IT Gateway Diagnosis
Information No.1

System area

410430 to
410434(6433EH to64342H)IT system connection status of Data
Diagnosis Flow No.24 Process No.1
to No.5410435(64343H)

System area

410436 to410440(64344H to64348H)IT system connection status of Data
Diagnosis Flow No.25 Process No.1
to No.5410441(64349H)

System area

410442 to410446(6434AH to
6434EH)IT system connection status of Data
Diagnosis Flow No.26 Process No.1
to No.5410447(6434FH)

System area

410448 to410452(64350H to
64354H)IT system connection status of Data
Diagnosis Flow No.27 Process No.1
to No.5410453(64355H)

System area

410454 to410458(64356H to6435AH)IT system connection status of Data
Diagnosis Flow No.28 Process No.1
to No.5410459(6435BH)

System area

410460 to
410464(6435CH to64360H)IT system connection status of Data
Diagnosis Flow No.29 Process No.1
to No.5410465(64361H)

System area

410466 to410470(64362H to64366H)IT system connection status of Data
Diagnosis Flow No.30 Process No.1
to No.5410471(64367H)

System area

410472 to410476(64368H to
6436CH)IT system connection status of Data
Diagnosis Flow No.31 Process No.1
to No.5410477(6436DH)

System area

468

APPX
Appendix 1 Real-time Flow Manager Status

Initialization timing

Readingor
writing• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

ReadingAddress indecimal(hexadecimal)

Category name

Name

Initialization timing

Readingor
writing

410478 to410482(6436EH to64372H)IT Gateway Diagnosis
Information No.1

IT system connection status of Data
Diagnosis Flow No.32 Process No.1
to No.5• When starting an industrial PC• When applying the parameters of Real-time
Flow Manager• When switching the operating status of aprocess flow (RUN  STOP)

Reading

410483 to410499(64373H to64383H)

System areaA

APPX
Appendix 1 Real-time Flow Manager Status469

Address indecimal(hexadecimal)

Category name

Name

410500 to
411199(64384H to6463FH)IT Gateway Diagnosis
Information No.2

Same as IT Gateway Diagnosis Information No.1 (409800 to 410499 (640C8H to 64383H))

411200 to
411899(64640H to
648FBH)IT Gateway Diagnosis
Information No.3

411900 to
412599(648FCH to
64BB7H)IT Gateway Diagnosis
Information No.4

412600 to
413299(64BB8H to
64E73H)IT Gateway Diagnosis
Information No.5413300 to
413999(64E74H to
6512FH)IT Gateway Diagnosis
Information No.6

414000 to
414699(65130H to
653EBH)IT Gateway Diagnosis
Information No.7

414700 to
415399(653ECH to
656A7H)IT Gateway Diagnosis
Information No.8

415400 to416099(656A8H to65963H)IT Gateway Diagnosis
Information No.9

416100 to
416799(65964H to
65C1FH)IT Gateway Diagnosis
Information No.10416800 to
417499(65C20H to
65EDBH)IT Gateway Diagnosis
Information No.11

417500 to
418199(65EDCH to66197H)IT Gateway Diagnosis
Information No.12418200 to
418899(66198H to66453H)IT Gateway Diagnosis
Information No.13

418900 to
419599(66454H to
6670FH)IT Gateway Diagnosis
Information No.14

419600 to420299(66710H to
669CBH)IT Gateway Diagnosis
Information No.15

420300 to420999(669CCH to
66C87H)IT Gateway Diagnosis
Information No.16

470

APPX
Appendix 1 Real-time Flow Manager Status

Initialization timing

Readingor
writingReal-time Flow Manager status details
The following shows the Real-time Flow Manager status details of Real-time Flow Manager.

Basic area
The following tables show the Real-time Flow Manager status details in the basic area (0 to 399999).

A

APPX
Appendix 1 Real-time Flow Manager Status

471

Data Logging Flow No.1 (0 to 399) to No.32 (12400 to 12799)
Information of a data logging flow is stored.
AddressName

0

Data Logging
Flow No.1

Description
StatusThe operating status of a data logging flow is stored.
• 0: Not used
• 1: STOP• 2: In transition to RUN• 3: RUN• 4: In transition to STOP

1Error code

An error code is stored.

2 to 34

Setting name

A setting name is stored.

35 to 135

Error occurrence process
name

The name of a process in which an error occurred is stored. (If there are multiple process
names, the latest one is stored.)
However, if an error not related to a process occurs, it will be blank.

136

Problem function

An error occurrence source is stored.
• 0: Real-time Flow Manager• 1: Data collector• 2: IT gateway
If an error occurs in CSV File Data collector, "Real-time Flow Manager" will be displayedfor "Problem Function."

137 to 201

Data collector file name or IT
gateway file name

The file name of a data collector or IT gateway in which an error occurred is stored in
UTF-16LE.
The termination character is also stored but not the extension.
However, if an error occurs in Real-time Flow Manager or CSV File Data collector, it willbe blank.

202 to 234

Data collector name or IT
gateway name

The data collector name of a data collector or the IT gateway name of an IT gateway inwhich an error occurred is stored in UTF-16LE.
It is stored in English and includes the termination character.
However, if an error occurs in Real-time Flow Manager or CSV File Data collector, it willbe blank.

235 to 299

Developer name

The developer name of a data collector or IT gateway in which an error occurred is stored
in UTF-16LE.
It is stored in English and includes the termination character.
However, if an error occurs in Real-time Flow Manager or CSV File Data collector, it willbe blank.

300

Data collector specification
version (integer part) or IT
gateway specification version(integer part)The specification version (integer part) of a data collector or IT gateway in which an error
occurred is stored.
However, if an error occurs in Real-time Flow Manager or CSV File Data collector, it willbe blank.

301

Data collector specification
version (decimal part) or IT
gateway specification version(decimal part)The specification version (decimal part) of a data collector or IT gateway in which an error
occurred is stored.
However, if an error occurs in Real-time Flow Manager or CSV File Data collector, it willbe blank.

302 to 305

Data collector version or IT
gateway version

The data collector version of a data collector or the IT gateway version of an IT gateway
in which an error occurred is stored.
However, if an error occurs in Real-time Flow Manager or CSV File Data collector, it willbe blank.

306 to 337

System area

338

Process data buffer usage rate

The buffer usage rate in a process of the data logging flow is stored.*1
Range: 0 to 100 [unit: %] (Digits after the decimal point are rounded up.)

339 to 353

System area

354 to 355

Number of times of data
missing*2

The number of times of data missing that occurs while the data logging flow is running isstored.
(When the number of times of data missing reaches the upper limit, a value of the upper
limit is stored.)356

Last data collection time(year)*2*3

The year of the time (UTC) of last data collection from a data collector is stored.

357

Last data collection time(month  day)*2*3

The month/day of the time (UTC) of last data collection from a data collector is stored.
(Example) December 3rd  1203 (decimal)

358

Last data collection time (hour minute)*2*3

The hour/minute of the time (UTC) of last data collection from a data collector is stored.
(Example) 12:34  1234 (decimal)

359

Last data collection time(second  millisecond)*2*3

The second/millisecond of the time (UTC) of last data collection from a data collector isstored. (Example) 56.789  56789 (decimal)

360 to 399

System area

472

APPX
Appendix 1 Real-time Flow Manager Status

Address

Name

Description

400 to 799

Data Logging Flow No.2

Same as Data Logging Flow No.1 (0 to 399)





12400 to12799

Data Logging Flow No.32

*1
*2
*3

Same as Data Logging Flow No.1 (0 to 399)

The value is updated every one second.
Not updated when only data collection is set in a data logging flow (excluding when using CSV File Data collector).
Updated with the time of last data collection from a data collector, regardless of whether data missing occurs.

A

APPX
Appendix 1 Real-time Flow Manager Status

473

Data Diagnosis Flow No.1 (12800 to 13199) to No.32 (25200 to 25599)
Information of a data diagnosis flow is stored.
Address

Name

12800

Data Diagnosis
Flow No.1

Description
StatusThe operating status of a data diagnosis flow is stored.
• 0: Not used
• 1: STOP• 2: In transition to RUN• 3: RUN• 4: In transition to STOP

12801

Error code

An error code is stored.

12802 to 12834

Setting name

A setting name is stored.

12835 to 12935

Error occurrence process
name

The name of a process in which an error occurred is stored. (If there are multiple
process names, the latest one is stored.)
However, if an error not related to a process occurs, it will be blank.

12936

Problem function

An error occurrence source is stored.
• 0: Real-time Flow Manager• 1: Data collector• 2: IT gateway
If an error occurs in CSV File Data collector, "Real-time Flow Manager" will be
displayed for "Problem Function."

12937 to 13001

Data collector file name or IT
gateway file name

The file name of a data collector or IT gateway in which an error occurred is stored in
UTF-16LE.
The termination character is also stored but not the extension.
However, if an error occurs in Real-time Flow Manager or CSV File Data collector, it
will be blank.

13002 to 13034

Data collector name or IT
gateway name

The data collector name of a data collector or the IT gateway name of an IT gateway
in which an error occurred is stored in UTF-16LE.
It is stored in English and includes the termination character.
However, if an error occurs in Real-time Flow Manager or CSV File Data collector, it
will be blank.

13035 to 13099

Developer name

The developer name of a data collector or IT gateway in which an error occurred isstored in UTF-16LE.
It is stored in English and includes the termination character.
However, if an error occurs in Real-time Flow Manager or CSV File Data collector, it
will be blank.

13100

Data collector specification
version (integer part) or IT
gateway specification version(integer part)The specification version (integer part) of a data collector or IT gateway in which anerror occurred is stored.
However, if an error occurs in Real-time Flow Manager or CSV File Data collector, it
will be blank.

13101

Data collector specification
version (decimal part) or IT
gateway specification version(decimal part)The specification version (decimal part) of a data collector or IT gateway in which anerror occurred is stored.
However, if an error occurs in Real-time Flow Manager or CSV File Data collector, it
will be blank.

13102 to 13105

Data collector version or IT
gateway version

The data collector version of a data collector or the IT gateway version of an IT
gateway in which an error occurred is stored.
However, if an error occurs in Real-time Flow Manager or CSV File Data collector, it
will be blank.

13106 to 13137

System area

13138

Process data buffer usage
rate

The buffer usage rate in a process of the data diagnosis flow is stored.*1
Range: 0 to 100 [unit: %] (Digits after the decimal point are rounded up.)13139 to 13153

System area

13154 to 13155

Number of times of data
missing

The number of times of data missing that occurs while the data diagnosis flow isrunning is stored.
(When the number of times of data missing reaches the upper limit, a value of theupper limit is stored.)13156

Last data collection time(year)*2

The year of the time (UTC) of last data collection from a data collector is stored.

13157

Last data collection time(month  day)*2

The month/day of the time (UTC) of last data collection from a data collector isstored. (Example) December 3rd  1203 (decimal)

13158

Last data collection time (hour minute)*2

The hour/minute of the time (UTC) of last data collection from a data collector isstored. (Example) 12:34  1234 (decimal)

13159

Last data collection time(second  millisecond)*2

The second/millisecond of the time (UTC) of last data collection from a data collector
is stored. (Example) 56.789  56789 (decimal)

13160 to 13199

System area

474

APPX
Appendix 1 Real-time Flow Manager Status

Address

Name

Description

13200 to 13599

Data Diagnosis Flow No.2

Same as Data Diagnosis Flow No.1 (12800 to 13199)



25200 to 25599*1*2

Data Diagnosis Flow No.32

Same as Data Diagnosis Flow No.1 (12800 to 13199)

The value is updated every one second.
Updated with the time of last data collection from a data collector, regardless of whether data missing occurs.

A

APPX
Appendix 1 Real-time Flow Manager Status

475

Data Logging Flow No.1 Process No.1 (25600 to 26099) to Data Logging Flow No.32 Process
No.4 (151100 to 151599)
Process information of a data logging flow is stored.
The process number of each flow corresponds to the number in the "Data Logging Flow Setting" screen. Process No.3 andNo.4 are added when a row is added in the "Data Logging Flow Setting" screen. (Page 130 Data Logging Flow Setting)
Address

Name

25600

Data Logging Flow
No.1 Process No.1

Description
StatusThe operating status of a process is stored.
• 0: Not used
• 1: STOP• 2: In transition to RUN• 3: RUN• 4: In transition to STOP

25601

Error code

An error code is stored.

25602 to 25604

System area

25605 to 25705

Setting name

A setting name is stored.

25706

Problem function

An error occurrence source is stored.
• 0: Real-time Flow Manager• 1: Data collector• 2: IT gateway
If an error occurs in CSV File Data collector, "Real-time Flow Manager" will be
displayed for "Problem Function."

25707 to 25771

Data collector filename or IT gateway
file name

The file name of a data collector or IT gateway in which an error occurred is stored in
UTF-16LE.
The termination character is also stored but not the extension.
However, if an error occurs in Real-time Flow Manager or CSV File Data collector, it
will be blank.

25772 to 25804

Data collector name or
IT gateway name

The data collector name of a data collector or the IT gateway name of an IT gateway inwhich an error occurred is stored in UTF-16LE.
It is stored in English and includes the termination character.
However, if an error occurs in Real-time Flow Manager or CSV File Data collector, it
will be blank.

25805 to 25869

Developer name

The developer name of a data collector or IT gateway in which an error occurred isstored in UTF-16LE.
It is stored in English and includes the termination character.
However, if an error occurs in Real-time Flow Manager or CSV File Data collector, it
will be blank.

25870

Data collector
specification version(integer part) or IT
gateway specification
version (integer part)The specification version (integer part) of a data collector or IT gateway in which anerror occurred is stored.
However, if an error occurs in Real-time Flow Manager or CSV File Data collector, it
will be blank.

25871

Data collector
specification version(decimal part) or IT
gateway specification
version (decimal part)The specification version (decimal part) of a data collector or IT gateway in which anerror occurred is stored.
However, if an error occurs in Real-time Flow Manager or CSV File Data collector, it
will be blank.

25872 to 25875

Data collector version
or IT gateway version

The data collector version of a data collector or the IT gateway version of an IT
gateway in which an error occurred is stored.
However, if an error occurs in Real-time Flow Manager or CSV File Data collector, it
will be blank.

25876 to 25929

System area

25930 to 26009

Information of eachprocess only

Process information corresponding to a process type is stored.
Process information of the data collection functionProcess information of the data modification function

26010 to 26054

Data storing
information

The operating information of data storing set in a process is stored.
Data storing information

26055 to 26099

Data distribution
information

The operating information of data distribution set in a process is stored.
Data distribution information



27100 to 27599

Data Logging Flow No.1 Process No.4

27600 to 29599

System area





476

APPX
Appendix 1 Real-time Flow Manager Status

Same as Data Logging Flow No.1 Process No.1 (25600 to 26099)

Address

Name

Description

151100 to 151599

Data Logging Flow No.32 Process No.1 to
No.4

Same as Data Logging Flow No.1 Process No.1 to No.4 (25600 to 27599)

 Process information of the data collection function
Offset indicates the relative position from 'Information of each process only' of each data logging flow.
OffsetName

Description

Initialization timing

0

Process type

1 (the data collection function) is stored.

1

Function type ofdata collection

The type of data collection is stored.
• 0: Not set• 1: Data collector• 4: CSV File Data collector• When starting an industrial PC*1
• When applying the parameters of
Real-time Flow Manager*1• When switching the operating statusof a process flow (STOP  RUN)*2

2 to 3

Number of times ofcollection

The number of times of data collection is stored.
It is incremented per collection. (When the number of times of collection
reaches the upper limit, it is incremented from '0' again.)

4 to 5

Collection
processing time
(maximum)The maximum processing time is stored.*3,*4 (In microseconds, 32-bit)

6 to 7

Collection
processing time(minimum)The minimum processing time is stored.*3,*4 (In microseconds, 32-bit)

8 to 9Collection
processing time(latest)The latest processing time is stored.*3,*4 (In microseconds, 32-bit)

10 to 79

Dedicated toprocessing

Information corresponding to a data collection type is stored.*4
CSV file collection

*1
*2
*3
*4

• When starting an industrial PC• When applying the parameters of
Real-time Flow Manager• When switching the operating statusof a process flow (STOP  RUN)

Differs depending on processing.

The value is initialized to '0.'
The contents of parameters are applied.
The value is updated every one second in the shortest.
When the data collection type is '1' (data collector), '0' is stored.

• CSV file collection (Data collection type: 4)
Offset indicates the relative position from 'Dedicated to processing' of a data collection process.

A

OffsetName

Description

Initialization timing

0 to 1

Number of
successful files

The cumulative number of times of successful CSV file collection is stored.

2 to 3

Number of failed
files

The cumulative number of times of failed CSV file collection is stored.

4

CSV file collection
start time (onsuccess)• b0 to b7: UTC offset (-48 to 52)*1• b8 to b15: (Not used)• When starting an industrial PC• When applying the parameters of
Real-time Flow Manager• When switching the operating statusof a process flow (STOP  RUN)5

• b0 to b7: Year (00h to 99h)*2• b8 to b15: Month (01h to 12h)6

• b0 to b7: Day (01h to 31h)
• b8 to b15: Hour (01h to 23h)7

• b0 to b7: Minute (01h to 59h)• b8 to b15: Second (01h to 59h)8

• b0 to b7: Day of the week (00h: Sunday, 01h: Monday, 02h: Tuesday, 03h:
Wednesday, 04h: Thursday, 05h: Friday, 06h: Saturday)• b8 to b15: Year (00h to 99h)*3

9• b0 to b7: Upper milliseconds (00h to 09h)*4• b8 to b15: Lower milliseconds (00h to 99h)10

• b0 to b7: Upper microseconds (00h to 09h)*4• b8 to b15: Lower microseconds (00h to 99h)11

• b0 to b7: Upper nanoseconds (00h to 09h)*4• b8 to b15: Lower nanoseconds (00h to 99h)

*1
*2
*3
*4

Specify it within the following ranges. (In decimal, in 15 minutes)-48: -12:00 to 52: +13:00
The last two digits of the year
The first two digits of the year
The hundreds place

APPX
Appendix 1 Real-time Flow Manager Status477 Process information of the data modification function
Offset indicates the relative position from 'Information of each process only' of each data logging flow.
OffsetName

Description

Initialization timing

0

Process type

2 (the data modification function) is stored.

1

Data modification
type

A data modification type is stored.
• 0: Not set• 1: Data extraction processing• 2: Program execution for data modification• 3: Character string data modification processing• When starting an industrial PC*1
• When applying the parameters of
Real-time Flow Manager*1• When switching the operating statusof a process flow (STOP  RUN)*2

2 to 79

Dedicated toprocessing

Information corresponding to a data modification type is stored.
Program processing for data modification
Character string data modification processing*1*2

Differs depending on processing.

The value is initialized to '0.'
The contents of parameters are applied.

• Program processing for data modification (data modification type: 2)
Offset indicates the relative position from 'Dedicated to processing' of a data modification process.
OffsetName

Description

Initialization timing0

Operating status ofa data modificationplug-in

The running status of a data modification plug-in is stored.
• 0: A data modification plug-in is not run.
• 1: A data modification plug-in is being run.

• When starting an industrial PC• When applying the parameters of
Real-time Flow Manager• When switching the operating statusof a process flow (STOP  RUN)

• When starting an industrial PC• When applying the parameters of
Real-time Flow Manager• When switching the operating statusof a process flow (STOP  RUN)

1

System area

2 to 3

Running time for adata modificationplug-in (latest)

The latest value of running time for a data modification plug-in is stored.

4 to 5

Running time for adata modificationplug-in (minimum)

The minimum value of running time for a data modification plug-in is stored.

6 to 7

Running time for adata modificationplug-in (maximum)

The maximum value of running time for a data modification plug-in is stored.

8 to 27

System area

28 to 31

Number ofaccumulated input
records after
starting operation

32 to 39

System area

40 to 43

Number ofaccumulated
output records after
starting operation

After starting operation, the accumulated number of records entered in a
program is stored. (Unsigned, 64-bit)
When it reaches the upper limit of a numerical value, it is counted from '0'
again.

• When starting an industrial PC• When applying the parameters of
Real-time Flow Manager• When switching the operating statusof a process flow (STOP  RUN)

After starting operation, the accumulated number of records output from a
program is stored. (Unsigned, 64-bit)
When it reaches the upper limit of a numerical value, it is counted from '0'
again.

• When starting an industrial PC• When applying the parameters of
Real-time Flow Manager• When switching the operating statusof a process flow (STOP  RUN)

• Character string data modification processing (data modification type: 3)
Offset indicates the relative position from 'Dedicated to processing' of a data modification process.
OffsetName

Description

Initialization timing

0 to 1

Number ofmodification failure
records

The accumulated number of records that failed to be modified in character
string data modification is stored.
When it reaches the upper limit, it is fixed to the upper limit value.

• When starting an industrial PC• When applying the parameters of
Real-time Flow Manager• When switching the operating statusof a process flow (STOP  RUN)

2 to 43

System area

478

APPX
Appendix 1 Real-time Flow Manager Status

Data Diagnosis Flow No.1 Process No.1 (153600 to 154099) to Data Diagnosis Flow No.32
Process No.6 (280100 to 280599)
Process information of a data diagnosis flow is stored.
The process number corresponds to the number in the "Data Diagnosis Flow Setting" screen. Process No.5 and No.6 areadded when a row is added in the "Data Diagnosis Flow Setting" screen. (Page 134 Data Diagnosis Flow Setting)
AddressName153600

Data Diagnosis
Flow No.1 Process
No.1

Description
StatusThe operating status of a process is stored.
• 0: Not used
• 1: STOP• 2: In transition to RUN• 3: RUN• 4: In transition to STOP

153601

Error code

An error code is stored.

153602 to 153604

System area

153605 to 153705

Setting name

A setting name is stored.

153706

Problem function

An error occurrence source is stored.
• 0: Real-time Flow Manager• 1: Data collector• 2: IT gateway
If an error occurs in CSV File Data collector, "Real-time Flow Manager" will be
displayed for "Problem Function."

153707 to 153771

Data collector file nameor IT gateway file name

The file name of a data collector or IT gateway in which an error occurred isstored in UTF-16LE.
The termination character is also stored but not the extension.
However, if an error occurs in Real-time Flow Manager or CSV File Data
collector, it will be blank.

153772 to 153804

Data collector name or
IT gateway name

The data collector name of a data collector or the IT gateway name of an IT
gateway in which an error occurred is stored in UTF-16LE.
It is stored in English and includes the termination character.
However, if an error occurs in Real-time Flow Manager or CSV File Data
collector, it will be blank.

153805 to 153869

Developer name

The developer name of a data collector or IT gateway in which an error
occurred is stored in UTF-16LE.
It is stored in English and includes the termination character.
However, if an error occurs in Real-time Flow Manager or CSV File Data
collector, it will be blank.

153870

Data collector
specification version(integer part) or IT
gateway specification
version (integer part)The specification version (integer part) of a data collector or IT gateway inwhich an error occurred is stored.
However, if an error occurs in Real-time Flow Manager or CSV File Data
collector, it will be blank.

153871

Data collector
specification version(decimal part) or IT
gateway specification
version (decimal part)The specification version (decimal part) of a data collector or IT gateway inwhich an error occurred is stored.
However, if an error occurs in Real-time Flow Manager or CSV File Data
collector, it will be blank.

153872 to 153875

Data collector version or
IT gateway version

The data collector version of a data collector or the IT gateway version of an
IT gateway in which an error occurred is stored.
However, if an error occurs in Real-time Flow Manager or CSV File Data
collector, it will be blank.

153876 to 153929

System area

153930 to 154009

Information of eachprocess only

Process information corresponding to a process type is stored.
Process information of the data collection functionProcess information of the data modification functionProcess information of the data diagnosis functionProcess information of the feedback function

154010 to 154054

Data storing information

The operating information of data storing set in a process is stored.
Data storing information

154055 to 154099

Data distribution
information

The operating information of data distribution set in a process is stored.
Data distribution information



A



156100 to 156599

Data Diagnosis Flow No.1 Process No.6

156600 to 157599

System area

Same as Data Diagnosis Flow No.1 Process No.1 (153600 to 154099)

APPX
Appendix 1 Real-time Flow Manager Status479

Address

Name





Description

277600 to 280599

Data Diagnosis Flow No.32 Process No.1 toNo.6

Same as Data Diagnosis Flow No.1 Process No.1 to No.6 (153600 to
156599)

 Process information of the data collection function
Offset indicates the relative position from 'Information of each process only' of each data diagnosis flow.
OffsetName

Description

Initialization timing

0

Process type

1 (the data collection function) is stored.

1

Function type ofdata collection

The type of data collection is stored.
• 0: Not set• 1: Data collector• 4: CSV File Data collector• When starting an industrial PC*1
• When applying the parameters of
Real-time Flow Manager*1• When switching the operating statusof a process flow (STOP  RUN)*2

2 to 3

Number of times ofcollection

The number of times of data collection is stored.
It is incremented per collection. (When the number of times of collection
reaches the upper limit, it is incremented from '0' again.)

4 to 5

Collection
processing time
(maximum)The maximum processing time is stored.*3,*4 (In microseconds, 32-bit)

6 to 7

Collection
processing time(minimum)The minimum processing time is stored.*3,*4 (In microseconds, 32-bit)

8 to 9Collection
processing time(latest)The latest processing time is stored.*3,*4 (In microseconds, 32-bit)

10 to 79

Dedicated toprocessing

Information corresponding to a data collection type is stored.*4
CSV file collection

*1
*2
*3
*4

• When starting an industrial PC• When applying the parameters of
Real-time Flow Manager• When switching the operating statusof a process flow (STOP  RUN)

Differs depending on processing.

The value is initialized to '0.'
The contents of parameters are applied.
The value is updated every one second in the shortest.
When the data collection type is '1' (data collector), '0' is stored.

• CSV file collection (Data collection type: 4)
Offset indicates the relative position from 'Dedicated to processing' of a data collection process.
OffsetName

Description

Initialization timing

0 to 1

Number of
successful files

The cumulative number of times of successful CSV file collection is stored.

2 to 3

Number of failed
files

The cumulative number of times of failed CSV file collection is stored.

4

CSV file collection
start time (onsuccess)• b0 to b7: UTC offset (-48 to 52)*1• b8 to b15: (Not used)• When starting an industrial PC• When applying the parameters of
Real-time Flow Manager• When switching the operating statusof a process flow (STOP  RUN)5

• b0 to b7: Year (00h to 99h)*2• b8 to b15: Month (01h to 12h)6

• b0 to b7: Day (01h to 31h)
• b8 to b15: Hour (01h to 23h)7

• b0 to b7: Minute (01h to 59h)• b8 to b15: Second (01h to 59h)8

• b0 to b7: Day of the week (00h: Sunday, 01h: Monday, 02h: Tuesday, 03h:
Wednesday, 04h: Thursday, 05h: Friday, 06h: Saturday)• b8 to b15: Year (00h to 99h)*3

9• b0 to b7: Upper milliseconds (00h to 09h)*4• b8 to b15: Lower milliseconds (00h to 99h)10

• b0 to b7: Upper microseconds (00h to 09h)*4• b8 to b15: Lower microseconds (00h to 99h)11

• b0 to b7: Upper nanoseconds (00h to 09h)*4• b8 to b15: Lower nanoseconds (00h to 99h)

*1
*2
*3
*4

480

Specify it within the following ranges. (In decimal, in 15 minutes)-48: -12:00 to 52: +13:00
The last two digits of the year
The first two digits of the year
The hundreds place

APPX
Appendix 1 Real-time Flow Manager Status Process information of the data modification function
Offset indicates the relative position from 'Information of each process only' of each data diagnosis flow.
OffsetName

Description

Initialization timing

0

Process type

2 (the data modification function) is stored.

1

Data modification
type

A data modification type is stored.
• 0: Not set• 1: Data extraction processing• 2: Program execution for data modification• 3: Character string data modification processing• When starting an industrial PC*1
• When applying the parameters of
Real-time Flow Manager*1• When switching the operating statusof a process flow (STOP  RUN)*2

2 to 79

Dedicated toprocessing

Information corresponding to a data modification type is stored.
Program processing for data modification
Character string data modification processing*1*2

Differs depending on processing.

The value is initialized to '0.'
The contents of parameters are applied.

• Program processing for data modification (data modification type: 2)
Offset indicates the relative position from 'Dedicated to processing' of a data modification process.
OffsetName

Description

Initialization timing0

Operating status ofa data modificationplug-in

The running status of a data modification plug-in is stored.
• 0: A data modification plug-in is not run.
• 1: A data modification plug-in is being run.

• When starting an industrial PC• When applying the parameters of
Real-time Flow Manager• When switching the operating statusof a process flow (STOP  RUN)

• When starting an industrial PC• When applying the parameters of
Real-time Flow Manager• When switching the operating statusof a process flow (STOP  RUN)

1

System area

2 to 3

Running time for adata modificationplug-in (latest)

The latest value of running time for a data modification plug-in is stored.

4 to 5

Running time for adata modificationplug-in (minimum)

The minimum value of running time for a data modification plug-in is stored.

6 to 7

Running time for adata modificationplug-in (maximum)

The maximum value of running time for a data modification plug-in is stored.

8 to 27

System area

28 to 31

Number ofaccumulated input
records after
starting operation

32 to 39

System area

40 to 43

Number ofaccumulated
output records after
starting operationA
After starting operation, the accumulated number of records entered in a
program is stored. (Unsigned, 64-bit)
When it reaches the upper limit of a numerical value, it is counted from '0'
again.

• When starting an industrial PC• When applying the parameters of
Real-time Flow Manager• When switching the operating statusof a process flow (STOP  RUN)

After starting operation, the accumulated number of records output from a
program is stored. (Unsigned, 64-bit)
When it reaches the upper limit of a numerical value, it is counted from '0'
again.

• When starting an industrial PC• When applying the parameters of
Real-time Flow Manager• When switching the operating statusof a process flow (STOP  RUN)

• Character string data modification processing (data modification type: 3)
OffsetName

Description

Initialization timing

0 to 1

Number ofmodification failure
records

The accumulated number of records that failed to be modified in character
string data modification is stored.
When it reaches the upper limit, it is fixed to the upper limit value.

• When starting an industrial PC• When applying the parameters of
Real-time Flow Manager• When switching the operating statusof a process flow (STOP  RUN)

2 to 43

System area

APPX
Appendix 1 Real-time Flow Manager Status481

 Process information of the data diagnosis function
Offset indicates the relative position from 'Information of each process only' of each data diagnosis flow.
OffsetName

Description

Initialization timing

0

Process type

3 (the data diagnosis function) is stored.

1

Data diagnosis
type

A data diagnosis type is stored.
• 0: Not set• 2: Data diagnosis plug-in running• 3: Edge application diagnosis (file)• 4: Edge application diagnosis (MQTT)• When starting an industrial PC*1
• When applying the parameters of
Real-time Flow Manager*1• When switching the operating statusof a process flow (STOP  RUN)*2

2 to 79

Dedicated toprocessing

Information corresponding to a data diagnosis type is stored.
Program processing for data diagnosis
Edge application diagnosis (file)Edge application diagnosis (MQTT)*1*2

Differs depending on processing.

The value is initialized to '0.'
The contents of parameters are applied.

• Program processing for data diagnosis (Data diagnosis type: 2)
Offset indicates the relative position from 'Dedicated to processing' of a data diagnosis process.
OffsetName

Description

Initialization timing0

Operating status ofa data diagnosis
plug-in

The operating status of a data diagnosis plug-in is stored.
• 0: A data diagnosis plug-in is not run.
• 1: A data diagnosis plug-in is being run.

• When starting an industrial PC• When applying the parameters of
Real-time Flow Manager• When switching the operating statusof a process flow (STOP  RUN)

1

System area

2 to 3

Running time for adata diagnosis
plug-in (latest)

The latest value of running time for a data diagnosis plug-in is stored.

4 to 5

Running time for adata diagnosis
plug-in (minimum)

The minimum value of running time for a data diagnosis plug-in is stored.

• When starting an industrial PC• When applying the parameters of
Real-time Flow Manager• When switching the operating statusof a process flow (STOP  RUN)

6 to 7

Running time for adata diagnosis
plug-in (maximum)

The maximum value of running time for a data diagnosis plug-in is stored.

8 to 27

System area

28 to 31

Number ofaccumulated input
records after
starting operation

32 to 39

System area

40 to 43

Number ofaccumulated
output records after
starting operation

After starting operation, the accumulated number of records entered in a
program is stored. (Unsigned, 64-bit)
When it reaches the upper limit of a numerical value, it is counted from '0'
again.

• When starting an industrial PC• When applying the parameters of
Real-time Flow Manager• When switching the operating statusof a process flow (STOP  RUN)

After starting operation, the accumulated number of records output from a
program is stored. (Unsigned, 64-bit)
When it reaches the upper limit of a numerical value, it is counted from '0'
again.

• When starting an industrial PC• When applying the parameters of
Real-time Flow Manager• When switching the operating statusof a process flow (STOP  RUN)

• Edge application diagnosis (file) (Data diagnosis type: 3)
Offset indicates the relative position from 'Dedicated to processing' of a data diagnosis process.
Offset0Name
Operating status ofan edge application
diagnosis

1• When starting an industrial PC• When applying the parameters of
Real-time Flow Manager• When switching the operating statusof a process flow (STOP  RUN)

The total number of times that an error is detected is stored.

3 to 77482

The operating status of an edge application is stored.
• 0: Stopped• 1: Running

Initialization timing*1,*2

The detection status is stored.
• 0: Normal• 1: Error detected

2

*1
*2

Description

System area

The value is updated once per second.
After switching the operating status of a process flow to RUN, "0" (stopped) remains stored until the first publishing data file is output
then deleted.

APPX
Appendix 1 Real-time Flow Manager Status• Edge application diagnosis (MQTT) (Data diagnosis type: 4)
Offset indicates the relative position from 'Dedicated to processing' of a data diagnosis process.
OffsetName

Description

Initialization timing0

Operating status ofan edge application
diagnosis

The operating status of an edge application is stored.*1• 0: Stopped• 1: Running• When starting an industrial PC• When applying the parameters of
Real-time Flow Manager• When switching the operating statusof a process flow (STOP  RUN)

1

The distribution pattern is stored.
• 0: Sending in a fixed cycle• 1: Sending with a variable number of records• 2: Sending with a fixed number of records

2 to 3The number of distribution records is stored.*2

4

The upper limit of the number of publishing data stored in a buffer is stored.

5

The current number of publishing data stored in a buffer is stored.

6

The maximum number of publishing data stored in a buffer is stored.

7

System area

8 to 11

The accumulated number of sent packets is stored.

12 to 15

The accumulated number of received packets is stored.

16 to 77

System area

*1
*2

• When starting an industrial PC• When applying the parameters of
Real-time Flow Manager• When switching the operating statusof a process flow (STOP  RUN)Stored only when selecting the checkbox of "Confirm existence of the Edge application at the time of delivery" in the "Definition Output"
tab in the "Edge Application Diagnosis (MQTT) Setting" screen.
Stored only when the distribution pattern is 'sending with a fixed number of records.'

Process information of the feedback function
Offset indicates the relative position from 'Information of each process only' of each data diagnosis flow.
OffsetName

Description

Initialization timing

0

Process type

4 (feedback function) is stored.

• When starting an industrial PC*1
• When applying the parameters of
Real-time Flow Manager*1• When switching the operating statusof a process flow (STOP  RUN)*2

1 to 15

System area
The type of feedback is stored.
• 0: Not set• 1: Device instruction feedback• 2: Program execution feedback• When starting an industrial PC*1
• When applying the parameters of
Real-time Flow Manager*1• When switching the operating statusof a process flow (STOP  RUN)*2

17

Deterrence period determination is stored.*3• 0: Not during a deterrence period• 1: During a deterrence period

18

Accumulated number of requests for feedback (0 to 39999)• When starting an industrial PC• When applying the parameters of
Real-time Flow Manager• When switching the operating statusof a process flow (STOP  RUN)

19 to 31

System area

16

Operating status of
feedback 1

32 to 47

Operating status of
feedback 2

48 to 63

Operating status of
feedback 3

64 to 79

Operating status of
feedback 4

*1
*2
*3

Same as the operating status of feedback 1

Same as the operating status of
feedback 1

The value is initialized to '0.'
The contents of parameters are applied.
The value is updated at the timing when the feedback function runs.

APPX
Appendix 1 Real-time Flow Manager Status

483

AData storing information
OffsetName

Description

Initialization timing

0

Data storing
function type

The type of the data storing function is stored.
• 1: File• 2: DB• When starting an industrial PC*1
• When applying the parameters of
Real-time Flow Manager*1• When switching the operating statusof a process flow (STOP  RUN)*2

1 to 44

System area

*1
*2

The value is initialized to '0.'
The contents of parameters are applied.

Data distribution information
OffsetName

Description

Initialization timing

0

Data distributionfunction type

The type of the data distribution function is stored.
• 1: MQTT• 2: IT gateway• When starting an industrial PC*1
• When applying the parameters of
Real-time Flow Manager*1• When switching the operating statusof a process flow (STOP  RUN)*2

1 to 44

System area

*1
*2

484

The value is initialized to '0.'
The contents of parameters are applied.

APPX
Appendix 1 Real-time Flow Manager Status

Error Log Information (290000 to 290001)
AddressName

Description

290000

Number of error
occurrences

The number of times of error occurrences in a process flow is stored.

290001

Latest error log
number

The number of an error log storing the latest error code among error logs 1 to 64 is stored.

Error Log 1 (290002 to 290251) to Error Log 64 (305752 to 306001)
Address

Name

290002Error Log 1

Description
Error code (error log 1)

290003 to 290004

System area

290005

Error occurrence date
and time

An error code is stored.

• b0 to b7: UTC offset (-48 to 52)*1• b8 to b15: (Not used)

290006• b0 to b7: Year (00h to 99h)*2• b8 to b15: Month (01h to 12h)

290007• b0 to b7: Day (01h to 31h)
• b8 to b15: Hour (01h to 23h)

290008• b0 to b7: Minute (01h to 59h)• b8 to b15: Second (01h to 59h)

290009• b0 to b7: Day of the week (00h: Sunday, 01h: Monday, 02h: Tuesday, 03h:
Wednesday, 04h: Thursday, 05h: Friday, 06h: Saturday)• b8 to b15: Year (00h to 99h)*3

290010• b0 to b7: Upper milliseconds (00h to 09h)*4• b8 to b15: Lower milliseconds (00h to 99h)

290011• b0 to b7: Upper microseconds (00h to 09h)*4• b8 to b15: Lower microseconds (00h to 99h)

290012• b0 to b7: Upper nanoseconds (00h to 09h)*4• b8 to b15: Lower nanoseconds (00h to 99h)

290013

Problem function

An error occurrence source is stored.
• 0: Real-time Flow Manager• 1: Data collector• 2: IT gateway
If an error occurs in CSV File Data collector, "Real-time Flow Manager" will be displayedfor "Problem Function."

290014 to 290078

Data collector file nameor IT gateway file name

The file name of a data collector or IT gateway in which an error occurred is stored in
UTF-16LE.
The termination character is also stored but not the extension.
However, if an error occurs in Real-time Flow Manager or CSV File Data collector, it willbe blank.

290079 to 290111

Data collector name or IT
gateway name

The data collector name of a data collector or the IT gateway name of an IT gateway inwhich an error occurred is stored in UTF-16LE.
It is stored in English and includes the termination character.
However, if an error occurs in Real-time Flow Manager or CSV File Data collector, it willbe blank.

290112 to 290176

Developer name

The developer name of a data collector or IT gateway in which an error occurred isstored in UTF-16LE.
It is stored in English and includes the termination character.
However, if an error occurs in Real-time Flow Manager or CSV File Data collector, it willbe blank.

290177

Data collector
specification version(integer part) or IT
gateway specification
version (integer part)The specification version (integer part) of a data collector or IT gateway in which anerror occurred is stored.
However, if an error occurs in Real-time Flow Manager or CSV File Data collector, it willbe blank.

290178

Data collector
specification version(decimal part) or IT
gateway specification
version (decimal part)The specification version (decimal part) of a data collector or IT gateway in which anerror occurred is stored.
However, if an error occurs in Real-time Flow Manager or CSV File Data collector, it willbe blank.

290179 to 290182

Data collector version or
IT gateway version

The data collector version of a data collector or the IT gateway version of an IT gateway
in which an error occurred is stored.
However, if an error occurs in Real-time Flow Manager or CSV File Data collector, it willbe blank.

290183 to 290251

System area

APPX
Appendix 1 Real-time Flow Manager Status

485

A

Address

Name

Description

290252 to 290501

Error Log 2

Same as Error Log 1 (290002 to 290251)



305752 to 306001

*1
*2
*3
*4

486

Error Log 64

Same as Error Log 1 (290002 to 290251)

Specify it within the following ranges. (In decimal, in 15 minutes)-48: -12:00 to 52: +13:00
The last two digits of the year
The first two digits of the year
The hundreds place

APPX
Appendix 1 Real-time Flow Manager Status

Data collector area
The following table shows the Real-time Flow Manager status details in the data collector area (400100 to 409799).

Target Device No.1 (400100 to 400399) to Target Device No.32 (409400 to 409699)
Device information of an access target is stored.
Address

Name

400100Target Device No.1

400101

Description
Setting enable flag

The setting enable flag of an access target device is stored.
• 0: Not set• 1: Set

Connection status

The connection status with an access target device is stored.
• 0: Disconnected• 1: Connected

400102Error code

The code for an error occurred in an access target device is stored.

400103

Problem function

An error occurrence source is stored.
• 0: Real-time Flow Manager• 1: Data collector
If an error occurs in CSV File Data collector, "Real-time Flow Manager" will be
displayed for "Problem Function."

400104 to 400168

Data collector file name

The file name of a data collector in which an error occurred is stored in UTF16LE.
The termination character is also stored but not the extension.
However, if an error occurs in Real-time Flow Manager or CSV File Data
collector, it will be blank.

400169 to 400201

Data collector name

The data collector name of a data collector in which an error occurred is stored
in UTF-16LE.
It is stored in English and includes the termination character.
However, if an error occurs in Real-time Flow Manager or CSV File Data
collector, it will be blank.

400202 to 400266

Developer name

The developer name of a data collector in which an error occurred is stored in
UTF-16LE.
It is stored in English and includes the termination character.
However, if an error occurs in Real-time Flow Manager or CSV File Data
collector, it will be blank.

400267

Data collector
specification version(integer part)The specification version (integer part) of a data collector in which an error
occurred is stored.
However, if an error occurs in Real-time Flow Manager or CSV File Data
collector, it will be blank.

400268

Data collector
specification version(decimal part)The specification version (decimal part) of a data collector in which an error
occurred is stored.
However, if an error occurs in Real-time Flow Manager or CSV File Data
collector, it will be blank.

400269 to 400272

Data collector version

The data collector version of a data collector in which an error occurred isstored.
However, if an error occurs in Real-time Flow Manager or CSV File Data
collector, it will be blank.

400273 to 400399

System area

409400 to 409699

Target Device No.32

A

Same as Target Device No.1 (400100 to 400399)

Information is stored only when an access target device setting satisfies both of the following conditions:• It is used for data collection or feedback.
• A data collector other than CSV File Data collector is used.

APPX
Appendix 1 Real-time Flow Manager Status487

IT gateway area
The following table shows the Real-time Flow Manager status details in the IT gateway area (409800 to 420999).

IT Gateway Diagnosis Information No.1 (409800 to 410499) to IT Gateway Diagnosis
Information No.16 (420300 to 420999)
IT gateway diagnosis information is stored.
AddressName409800IT Gateway
Diagnosis
Information No.1

Description
Setting enable flag

The setting enable flag of an IT gateway is stored.
• 0: Not set• 1: Set

409801Connection status

The connection status with an external device such as an IT system is stored.
• 0: Disconnected• 1: Connected

409802Error code

The code for an error occurred in an IT gateway is stored.

409803

Problem function

An error occurrence source is stored.
• 0: No error• 2: IT gateway

409804 to 409868

IT gateway file name

The file name of an IT gateway in which an error occurred is stored in UTF16LE.
The termination character is also stored but not the extension.

409869 to 409901

IT gateway name

The name of an IT gateway in which an error occurred is stored in UTF-16LE.
It is stored in English and includes the termination character.

409902 to 409966

Developer name

The developer name of an IT gateway in which an error occurred is stored in
UTF-16LE.
It is stored in English and includes the termination character.

409967

IT gateway specification
version (integer part)The specification version (integer part) of an IT gateway in which an error
occurred is stored.

409968IT gateway specification
version (decimal part)The specification version (decimal part) of an IT gateway in which an error
occurred is stored.

409969 to 409972

IT gateway version

The IT gateway version of an IT gateway in which an error occurred is stored.

409973 to 410006

System area

410007

IT gateway type

410008 to 410099

System area

410100 to 410103

IT system connection
status of Data Logging
Flow No.1 Process No.1 to
No.4

Type of an IT gateway• 1: Data storing• 2: Data distribution

The connection status with an external device such as an IT system is stored.
• 0: Disconnected• 1: Connected

410104 to 410105

System area







410286 to 410289

IT system connection
status of Data Logging
Flow No.32 Process No.1
to No.4

Same as the IT system connection status of Data Logging Flow No.1 Process
No.1 to No.4 (410100 to 410103)

410290 to 410291

System area

410292 to 410296

IT system connection
status of Data Diagnosis
Flow No.1 Process No.1 toNo.5410297

System area410478 to 410482

IT system connection
status of Data Diagnosis
Flow No.32 Process No.1
to No.5410483 to 410499

System area420300 to 420999

IT Gateway Diagnosis Information No.16

488

APPX
Appendix 1 Real-time Flow Manager Status

Same as the IT system connection status of Data Logging Flow No.1 Process
No.1 to No.4 (410100 to 410103)

Same as the IT system connection status of Data Logging Flow No.1 Process
No.1 to No.4 (410100 to 410103)

Same as IT Gateway Diagnosis Information No.1 (409800 to 410499)

Information is stored only when an IT gateway setting is used for data storing or data distribution.

A

APPX
Appendix 1 Real-time Flow Manager Status489

Real-time Flow Manager status initialization
The following table shows the initialization timing and overview of the Real-time Flow Manager status.
TimingOverview

When starting an industrial PC

All information in each area is initialized.
• Product information area: Initialized with the product information at startup.
• Setting information area: Initialized with the setting contents of parameters (adding and deleting settings arealso applied*1).
• Operating information area: Cleared (padded with '0').
• Error information area: Cleared (padded with '0').
• Connection status area: Cleared (not connected).
• System area: Cleared (padded with '0').

When applying the parameters of Realtime Flow Manager

All information in each area is initialized.
• Setting information area: Initialized with the setting contents of parameters (adding and deleting settings arealso applied*1).
• Operating information area: Cleared (padded with '0').
• Error information area: Cleared (padded with '0')*2.

When switching theoperating status of aprocess flow

When clearing an error*1*2

STOP RUN

The area of a process flow with its operating status switched is initialized.
• Setting information area: Initialized with the setting contents of parameters (adding and deleting settings arealso applied*1).
• Operating information area: Cleared (padded with '0').
• Error information area: Cleared (padded with '0').

RUN 
STOP

The area of a process flow with its operating status switched is initialized.
• Connection status area: Cleared (not connected).
Information on an error in each area is initialized.
• Error information area: Cleared (padded with '0').

In some areas, it is initialized with the setting contents of parameters when switching the operating status of a process flow from STOP
to RUN, not when starting an industrial PC or applying the parameters of Real-time Flow Manager.
Excluding major errors.

For the initialization timing for each area, refer to the following:
Page 434 Real-time Flow Manager status list

490

APPX
Appendix 1 Real-time Flow Manager Status

Appendix 2 Available Characters
Real-time Flow Designer
The following table shows the characters that can be used in Real-time Flow Designer.
ScreenItem

Available/invalid character

Reference

Password input

Password

Available characters
Refer to the following:
Page 496 Data source, user,
password, and output name of thedate and time column



Password setting

Password

Available characters
Refer to the following:
Page 496 Data source, user,
password, and output name of thedate and time column

Confirmation password

Float Type Constant Setting
Integer Type Constant SettingAvailable characters
Refer to the following:
Page 544 Values that can beentered in the screen

Page 123 Setting constants

DB Connection Common Setting

Data Source Name

Available characters
Refer to the following:
Page 496 Data source, user,
password, and output name of thedate and time column

Page 116 DB connection common
setting

User Name

Available characters• Printable ASCII characters (0x20 to
0x7E)

Page 117 File saving common setting

Password

Available characters• Printable ASCII characters (0x20 to
0x7E)

Event History Automatic Output
Setting

Save Destination Folder

Available characters• Characters that can be used as the
WSTRING type*1*3
Page 545 WSTRING type

Page 118 Event history automatic
output setting

User Account Setting

User Name

Available characters• Printable ASCII characters (0x20 to
0x7E)

Page 119 User account setting
screenPassword

Available characters• Printable ASCII characters (0x20 to
0x7E)

Setting NameInvalid characters• Space• Unavailable characters (U+0000 to
U+001F, U+007F to U+00A0,
U+00AD, U+2028, U+2029)• Surrogate pair characters(U+10000 to U+10FFFF)

Comment

Invalid characters• Unavailable characters (U+0000 to
U+001F, U+007F to U+00A0,
U+00AD, U+2028, U+2029)• Surrogate pair characters(U+10000 to U+10FFFF)

User Name
Password

File Saving Common Setting

Target Device Setting

A

Page 124 Access Target Device
Setting

APPX
Appendix 2 Available Characters491

Screen

Item

Available/invalid character

Reference

IT Gateway Setting

Setting NameInvalid characters• Space• Unavailable characters (U+0000 to
U+001F, U+007F to U+00A0,
U+00AD, U+2028, U+2029)• Surrogate pair characters(U+10000 to U+10FFFF)

Page 127 IT Gateway Setting

Comment

Invalid characters• Unavailable characters (U+0000 to
U+001F, U+007F to U+00A0,
U+00AD, U+2028, U+2029)• Surrogate pair characters(U+10000 to U+10FFFF)

Setting NameInvalid characters• Space• Unavailable characters (U+0000 to
U+001F, U+007F to U+00A0,
U+00AD, U+2028, U+2029)• Surrogate pair characters(U+10000 to U+10FFFF)

Comment

Invalid characters• Unavailable characters (U+0000 to
U+001F, U+007F to U+00A0,
U+00AD, U+2028, U+2029)• Surrogate pair characters(U+10000 to U+10FFFF)

Process NameInvalid characters• Unavailable characters (U+0000 to
U+001F, U+007F to U+00A0,
U+00AD, U+2028, U+2029)• Surrogate pair characters(U+10000 to U+10FFFF)

Data NameInvalid characters• , (comma), space• Unavailable characters (U+0000 to
U+001F, U+007F to U+00A0,
U+00AD, U+2028, U+2029)

Location (top)Invalid characters• U+0000 to U+001F, U+007F to
U+009F

LengthAvailable characters• Numerals (decimal)

Setting ValueAvailable characters
Refer to the following:
Page 544 Values that can beentered in the screen

Monitoring Folder

Available characters• Characters in the Unicode BasicMultilingual Plane (only charactersthat can be used as the WSTRINGtype)*1
Page 545 WSTRING type

File Name Prefix

Available characters• Characters that can be used as the
WSTRING type*2,*3
Page 545 WSTRING type

Data NameInvalid characters• , (comma), space• Unavailable characters (U+0000 to
U+001F, U+007F to U+00A0,
U+00AD, U+2028, U+2029)• Surrogate pair characters(U+10000 to U+10FFFF)

Data Logging Flow Setting
Data Diagnosis Flow Setting

Data Collection Setting ([CollectionData] tab)

Data Collection Setting (CSV File
Data collector)

492

APPX
Appendix 2 Available Characters

Page 130 Data Logging Flow Setting
Page 134 Data Diagnosis Flow
Setting

Page 140 Collection data

Page 310 Data Collection Setting(CSV File Data collector)

Screen

Item

Available/invalid character

Reference

Data Storing Setting (File Saving)([Output Option] tab)

Output Name of Date Column

Available characters
Refer to the following:*4
Page 496 Data source, user,
password, and output name of thedate and time column

Page 146 Output option

Data Row Output Format

Available characters• Alphanumeric characters• Symbols other than " (double
quote), ; (semicolon), and ,(comma) (including spaces)

Data Storing Setting (File Saving)([Save File] tab)

Save Destination Folder

Available characters
Refer to the following:
Page 67 File

Page 147 Saved file

User Account Setting

User Name

Available characters• Printable ASCII characters (0x20 to
0x7E)

Page 149 User account setting

Password

Available characters• Printable ASCII characters (0x20 to
0x7E)

ProgramAvailable characters
Refer to the following:
Page 68 Program execution after
file output

Page 150 Program execution setting

Available characters
Refer to the following:
Page 496 Data source, user,
password, and output name of thedate and time column

Page 154 Connection

Available characters
Refer to the following:
Page 79 Table name and field
name

Page 156 Access table

Page 160 Destination

Program Execution Setting

File Name Prefix

Argument

Data Storing Setting (DB Saving)([Connect] tab)

Data Source Name
User Name
Password

Data Storing Setting (DB Saving)([Access Table] tab)Table Name

Data Distribution Setting([Destination] tab)

Host Name

Available characters• Alphanumeric characters• . (period), - (hyphen)

User Name

Available characters• Printable ASCII characters (0x20 to
0x7E)

Password

Available characters• Printable ASCII characters (0x20 to
0x7E)

Certificate authority certificate

Available characters• Printable ASCII characters (0x20 to0x7E)*5

Client certificate

Available characters• Printable ASCII characters (0x20 to0x7E)*5

Client secret key

Available characters• Printable ASCII characters (0x20 to0x7E)*5

Client ID at sendingAvailable characters• Printable ASCII characters (0x20 to
0x7E)

Data Distribution Setting ([Definition
Output] tab)Publishing Data topic nameAvailable characters
Printable ASCII characters (0x20 to0x7E) excluding '#' and '+'Page 162 Definition output

Data Extraction Setting

Output Data NameInvalid characters• , (comma), space• Unavailable characters (U+0000 to
U+001F, U+007F to U+00A0,
U+00AD, U+2028, U+2029)

Page 169 Data Extraction Setting

Field Name

APPX
Appendix 2 Available CharactersA493

Screen

Item

Available/invalid character

Reference

Character String Data Modification
setting

Added character stringAvailable characters
Refer to the following:
Page 545 Available characters

Page 170 Character String Data
Modification Setting

Start position

Available characters• Numerals (decimal)

End position

Available characters• Numerals (decimal)

Output Data Setting NameInvalid characters• , (comma), space• Unavailable characters (U+0000 to
U+001F, U+007F to U+00A0,
U+00AD, U+2028, U+2029)

Start Argument

Available characters• Characters that can be used as the
WSTRING type
Page 545 WSTRING typeOutput Name of Date Column

Available characters
Refer to the following:*4
Page 496 Data source, user,
password, and output name of thedate and time column

Data Row Output Format

Available characters• Alphanumeric characters• Symbols other than " (double
quote), ; (semicolon), and ,(comma) (including spaces)

Save Destination Folder

Available characters• Characters available for file pathsin Windows

File Name Prefix

Available characters
Refer to the following:
Page 67 File

Edge Application Diagnosis (file)
Setting ([Response Data] tab)

Output Data Setting NameInvalid characters• , (comma), space• Unavailable characters (U+0000 to
U+001F, U+007F to U+00A0,
U+00AD, U+2028, U+2029)

Page 183 Response data

Edge Application Diagnosis (MQTT)
Setting ([Destination] tab)

Host Name

Available characters• Alphanumeric characters• . (period), - (hyphen)

Page 174 Destination

User Name

Available characters• Printable ASCII characters (0x20 to
0x7E)

Password

Available characters• Printable ASCII characters (0x20 to
0x7E)

Certificate authority certificate

Available characters• Printable ASCII characters (0x20 to0x7E)*5

Client certificate

Available characters• Printable ASCII characters (0x20 to0x7E)*5

Client secret key

Available characters• Printable ASCII characters (0x20 to0x7E)*5

Client ID at sendingAvailable characters• Printable ASCII characters (0x20 to
0x7E)

Publishing Data topic nameAvailable characters• Printable ASCII characters (0x20 to0x7E) excluding '#' and '+'Client ID

Available characters• Printable ASCII characters (0x20 to
0x7E)

Data Modification Plug-in Setting

Edge Application Diagnosis (file)
Setting ([Output Option] tab)

Edge Application Diagnosis (file)
Setting ([Save File] tab)

Edge Application Diagnosis (MQTT)
Setting ([Definition Output] tab)

494

APPX
Appendix 2 Available Characters

Page 172 Data Modification Plug-in
Setting

Page 181 Output option

Page 182 Saved file

Page 176 Definition output

Screen

Item

Available/invalid character

Reference

Edge Application Diagnosis (MQTT)
Setting ([Response Data] tab)

Output Data Setting NameInvalid characters• , (comma), space• Unavailable characters (U+0000 to
U+001F, U+007F to U+00A0,
U+00AD, U+2028, U+2029)

Page 177 Response data

Data Diagnosis Plug-in Setting

Output Data Setting NameInvalid characters• , (comma), space• Unavailable characters (U+0000 to
U+001F, U+007F to U+00A0,
U+00AD, U+2028, U+2029)

Page 184 Data Diagnosis Plug-in
SettingStart Argument

Available characters• Characters that can be used as the
WSTRING type
Page 545 WSTRING type

Post-Diagnosis Feedback Setting

Deterrence Period

Available characters• Numerals (decimal)

Page 185 Post-Diagnosis Feedback
Setting

Instruction Feedback Setting

Data NameInvalid characters• , (comma), space• ASCII control code (U+0000 to
U+001F), DEL(U+007F)

Page 188 Instruction target data

Location (top)Invalid characters• U+0000 to U+001F, U+007F to
U+009F

LengthAvailable characters• Numerals (decimal)

ProgramAvailable characters
Refer to the following:
Page 55 Specifications ofprogram execution commands

Program Execution Feedback Setting

Argument

*1
*2
*3
*4
*5

Page 190 Program execution
feedback setting

Excluding the following characters that cannot be used for file paths of Windows:/ (0x2F), * (0x2A), ? (0x3F), " (0x22), < (0x3C), > (0x3E), | (0x7C)
Excluding the following characters:\ (0x5C), / (0x2F), : (0x3A), * (0x2A), ? (0x3F), " (0x22), < (0x3C), > (0x3E), | (0x7C)
A space (0x20) and a period (0x2E) cannot be used for the first character.
A comma and a space cannot be entered.
In the range from 0x20 to 0x7E excluding the following:/ (0x2F), * (0x2A), ? (0x3F), " (0x22), < (0x3C), > (0x3E), | (0x7C)

A

APPX
Appendix 2 Available Characters

495

Data source, user, password, and output name of the date and time column
The following ASCII characters can be used for a data source name, user name, password name, and output name of thedate and time column.
Characters in the shaded area can be used.
0

2

3

4

5

6

7

(SP)

0

@

P

‘

p

1

!

1

A

Q

a

q

2

"

2

B

R

b

r

3

#

3

C

S

c

s

4

$

4

D

T

d

t

5

%

5

E

U

e

u

6

&

6

F

V

f

v

7

'

7

G

W

g

w

8

(

8

H

X

h

x

9

)

9

I

Y

i

y

A

*

:

J

Z

j

z

B

+

;

K

k

C

,

<

L

[
\

l

{
|

D

-

=

M

]

m

}

E

.

>

N

^

n
̃

F

/

?

O

_

o

0

496

NUL

1

APPX
Appendix 2 Available Characters

Management Shell Explorer
The following table shows the characters that can be used in Management Shell Explorer.
ScreenItem

Available/invalid character

Reference

Password input

Password

Available characters
Refer to the following:
Page 496 Data source, user,
password, and output name of thedate and time column



Password setting

Password

Available characters
Refer to the following:
Page 496 Data source, user,
password, and output name of thedate and time column

Confirmation password

Monitoring Setting

Current Value Update IntervalAvailable characters• Characters

Page 211 Changing amonitoring update
interval

Data tag resource monitor
window

Current Value

For BOOL type

Available characters• 0, 1For INT type

Available characters
For a display format in decimal• 0 to 9, - (hyphen)
For a display format in hexadecimal• 0 to 9, A to F, a to f*1, h*1,*2, H*2

Page 214 Changing
current values of datatag resources

For UINT type

Available characters
For a display format in decimal• 0 to 9
For a display format in hexadecimal• 0 to 9, A to F, a to f*1, h*1,*2, H*2

For DINT type

Available characters
For a display format in decimal• 0 to 9, - (hyphen)
For a display format in hexadecimal• 0 to 9, A to F, a to f*1, h*1,*2, H*2

For UDINT type

Available characters
For a display format in decimal• 0 to 9
For a display format in hexadecimal• 0 to 9, A to F, a to f*1, h*1,*2, H*2

For LINT type

Available characters
For a display format in decimal• 0 to 9, - (hyphen)
For a display format in hexadecimal• 0 to 9, A to F, a to f*1, h*1,*2, H*2

For ULINT type

Available characters
For a display format in decimal• 0 to 9
For a display format in hexadecimal• 0 to 9, A to F, a to f*1, h*1,*2, H*2

For REAL type

Available characters
0 to 9, E, e*3, - (hyphen), + (plus), .
(period)

For LREAL type

Available characters
0 to 9, E, e*3, - (hyphen), + (plus), .
(period)

For STRING type

Available characters
Refer to the following:
Page 545 STRING type

For WSTRING type

Available characters*8
Refer to the following:
Page 545 WSTRING type

APPX
Appendix 2 Available CharactersA497

Screen

Item

Target Device Setting Batch
Replacement

Search for Data Tag
Resource to Replace

Component Display Name

Data tag resource list

LocationInvalid characters• Control character codes (U+0000
to U+001F, U+007F to U+009F)• Surrogate pair characters*6

Number of Characters

Available characters• Numerals([Connection Setting] tab)

Port NumberAvailable characters• Characters([Certificate Setting] tab)

OPC UA Server Name

Available characters*4• Alphanumeric characters• _ (underscore)

Organization Name

Available characters• Alphanumeric characters

Unit of Organization

Available characters• Alphanumeric characters

Region Name

Available characters• Alphanumeric characters

StateAvailable characters• Alphanumeric characters

Country Name

Available characters• Alphabetical characters

Expiration Date (Year)Available characters• Numerals

IP address (IPv4)

Available characters• Numerals• . (period)

OPC UA Setting([Server Setting] tab)Target Device Setting

Target Device Setting (CSV File
Data collector)

498

Resource Display Name

Available/invalid character

ReferenceInvalid characters• Control character codes (U+0000
to U+001F, U+007F to U+00A0,
U+00AD)• Line feed codes (U+2028, U+2029)• Surrogate pair characters*6

Page 217 Access target
device setting batch
replacement

Setting Name*5

Invalid characters• Control character codes (U+0000
to U+001F, U+007F to U+00A0,
U+00AD)• Line feed codes (U+2028, U+2029)• Surrogate pair characters*6

Comment

Invalid characters• Control character codes (U+0000
to U+001F, U+007F to U+00A0,
U+00AD)• Line feed codes (U+2028, U+2029)• Surrogate pair characters*6

Monitoring Folder

Available characters• Characters in the Unicode BasicMultilingual Plane (only charactersthat can be used as the WSTRINGtype)*10
Page 545 WSTRING type

File Name Prefix

Available characters• Characters that can be used as the
WSTRING type*11,*12
Page 545 WSTRING type

APPX
Appendix 2 Available Characters

Page 261 Setting an
OPC UA server

Page 223 Access target
device setting screen

Page 311 Access Target
Device Setting (CSV
File Data collector)

Screen

Item

Available/invalid character

Reference

IT Gateway Setting

Setting Name*5

Invalid characters• Control character codes (U+0000
to U+001F, U+007F to U+00A0,
U+00AD)• Line feed codes (U+2028, U+2029)• Surrogate pair characters*6

Page 268 IT gateway
setting screen

Comment

Invalid characters• Control character codes (U+0000
to U+001F, U+007F to U+00A0,
U+00AD)• Line feed codes (U+2028, U+2029)• Surrogate pair characters*6

Component Find Dialog
Resource Find Dialog

Find StringInvalid characters• Control character codes (U+0000
to U+001F, U+007F to U+00A0,
U+00AD)• Line feed codes (U+2028, U+2029)• Surrogate pair characters*6

Page 233 Searching for
a component
Page 255 Searching for
a component
Page 256 Searching fora resource

Property Window(When selecting a component)

Component Name

Available characters• Alphanumeric characters*7• _ (underscore), - (hyphen)

Page 226 Editing
component properties

Component Display NameInvalid characters• Control character codes (U+0000
to U+001F, U+007F to U+00A0,
U+00AD)• Line feed codes (U+2028, U+2029)• Surrogate pair characters*6

A

APPX
Appendix 2 Available Characters499

Screen

Item

Available/invalid character

Reference

Add External Data Tag
Resource
Edit External Data Tag
Resource

Data Tag Resource Name

Available characters• Alphanumeric characters andsymbols*7,*9

Resource Display NameInvalid characters• Control character codes (U+0000
to U+001F, U+007F to U+009F)• Line feed codes (U+2028, U+2029)• Surrogate pair characters*6

Page 236 Adding a datatag resource
Page 243 Editing datatag resource properties

Location Information

Invalid characters• Control character codes (U+0000
to U+001F, U+007F to U+009F)• Surrogate pair characters*6

Number of Characters

Available characters• Numerals

Data Tag Resource Name

Available characters• Alphanumeric characters andsymbols*7,*9

Resource Display NameInvalid characters• Control character codes (U+0000
to U+001F, U+007F to U+00A0,
U+00AD)• Line feed codes (U+2028, U+2029)• Surrogate pair characters*6

Number of Characters

Available characters• Numerals

Add Internal Data Tag Resource
Edit Internal Data Tag Resource

Default Value

Operation Expression Setting

500

Setting Value

APPX
Appendix 2 Available Characters

For BOOL type

Available characters• 0, 1For INT type

Available characters• 0 to 9, - (hyphen)

For UINT type

Available characters• 0 to 9

For DINT type

Available characters• 0 to 9, - (hyphen)

For UDINT type

Available characters• 0 to 9

For LINT type

Available characters• 0 to 9, - (hyphen)

For ULINT type

Available characters• 0 to 9

For REAL type

Available characters• 0 to 9, E, e, - (hyphen), + (plus), .
(period)

For LREAL type

Available characters• 0 to 9, E, e, - (hyphen), + (plus), .
(period)

For STRING type

Available characters
Refer to the following:
Page 545 STRING type

For WSTRING type

Available characters*8
Refer to the following:
Page 545 WSTRING type
Available characters
Same as those shown in thefollowing:Default Value

Page 240 "Operation
Expression Setting"screenScreen

Item

Available/invalid character

Reference

Property Window(When selecting a file resource)

File Resource Name

Available characters• Alphanumeric characters andsymbols*7,*9

Page 245 Editing fileresource properties

Resource Display NameInvalid characters• Control character codes (U+0000
to U+001F, U+007F to U+00A0,
U+00AD)• Line feed codes (U+2028, U+2029)• Surrogate pair characters*6

File PathAvailable characters*8• Characters available for file pathsin Windows

Folder Resource Name

Available characters• Alphanumeric characters andsymbols*7,*9

Resource Display NameInvalid characters*8• Control character codes (U+0000
to U+001F, U+007F to U+00A0,
U+00AD)• Line feed codes (U+2028, U+2029)• Surrogate pair characters*6

Folder Path

Available characters*8• Characters available for file pathsin Windows

Setting NameInvalid characters• Space• Unavailable characters (U+0000 to
U+001F, U+007F to U+00A0,
U+00AD, U+2028, U+2029)

Comment

Invalid characters• Unavailable characters (U+0000 to
U+001F, U+007F to U+00A0,
U+00AD, U+2028, U+2029)

Detailed Setting([Collection Setting] tab)

Output NameInvalid characters*13• Unavailable characters (U+0080 to
U+00A0, U+00AD, U+2028,
U+2029)Page 283 Collection
settingMove to the specified No.

Specified No.

Available characters• Numerals"Move to the specified
No." screen

Detailed Setting([Saving Setting] tab)

Save File Path Setting

Save Destination Folder

Available characters• Characters available for file pathsin Windows*10,*12

Page 286 File saving
setting

File Name Prefix

Available characters• Characters that can be used as the
WSTRING type*11
Page 545 WSTRING typeOutput NameInvalid characters*13• Unavailable characters (U+0080 to
U+00A0, U+00AD, U+2028,
U+2029)Page 286 File saving
setting
Page 287 DB saving
setting

FormatAvailable characters• Alphanumeric characters• Symbols other than " (double
quote), ; (semicolon), and ,(comma) (including spaces)

Page 286 File saving
setting

Data Source Name

Available characters
Refer to the following:
Page 503 Data source name

Page 287 DB saving
setting

User Name

Available characters
Refer to the following:
Page 503 User name andpassword name

Property Window(When selecting a folder
resource)

Detailed Setting

Output Option

DB Connection Setting

Password

Access Table Setting

Page 248 Editing folder
resource properties

Page 282 Detailed
setting screenAAvailable characters
Refer to the following:
Page 275 Table name andcolumn name

APPX
Appendix 2 Available Characters

501

Screen

Item

Available/invalid character

Reference

Event History Automatic Output
Setting

Save Destination Folder

Available characters*8*10*12• Characters that can be used as the
WSTRING type
Page 545 WSTRING type

Page 292 Event history
automatic output setting
screenUser Account Setting

User Name

Available characters*7*8• Printable ASCII characters (0x20 to
0x7E)

Page 293 User accountsetting screen

Password

Available characters*8• Printable ASCII characters (0x20 to
0x7E)

*1
*2
*3
*4
*5
*6
*7
*8
*9

Converted into the upper-case characters (A to F, H) when displayed.
Can be entered only at the beginning of a character string.
Converted into the upper-case character (E) when displayed.
Both '[' and ']' can be entered only when setting a value for "[ServerName]."Case-sensitive and regarded as input of a different character.
Note that no error message will be output even if entering them.
Not case-sensitive and regarded as input of a same character.
Do not enter surrogate pair characters. (Note that no error message will be output even if entering them.)
Excluding the following characters:. (period), / (slash), \ (backslash)*10 Excluding the following characters that cannot be used for file paths of Windows:/ (0x2F), * (0x2A), ? (0x3F), " (0x22), < (0x3C), > (0x3E), | (0x7C)*11 Excluding the following characters:\ (0x5C), / (0x2F), : (0x3A), * (0x2A), ? (0x3F), " (0x22), < (0x3C), > (0x3E), | (0x7C)*12 A space (0x20) and a period (0x2E) cannot be used for the first character.
*13 The following characters in the range of U+0000 to U+007F can be used.
0 to 9, A to Z, a to z, _ (U+005F)

502

APPX
Appendix 2 Available Characters

Data source name, user name, and password name
The following ASCII characters can be used for a data source name, user name, and password name.
Characters in the shaded area can be used.

Data source name
0

2

3

4

5

6

7

(SP)

0

@

P

‘

p

1

!

1

A

Q

a

q

2

"

2

B

R

b

r

3

#

3

C

S

c

s

4

$

4

D

T

d

t

5

%

5

E

U

e

u

6

&

6

F

V

f

v

7

'

7

G

W

g

w

8

(

8

H

X

h

x

9

)

9

I

Y

i

y

A

*

:

J

Z

j

z

B

+

;

K

k

C

,

<

L

[
\

l

{
|

D

-

=

M

]

m

}

E

.

>

N

^

n
̃

F

/

?

O

_

o

0

1

NUL

User name and password name
0

2

3

4

5

6

7

(SP)

0

@

P

‘

p

1

!

1

A

Q

a

q

2

"

2

B

R

b

r

3

#

3

C

S

c

s

4

$

4

D

T

d

t

5

%

5

E

U

e

u

6

&

6

F

V

f

v

7

'

7

G

W

g

w

8

(

8

H

X

h

x

9

)

9

I

Y

i

y

A

*

:

J

Z

j

z

B

+

;

K

k

C

,

<

L

[
\

l

{
|

D

-

=

M

]

m

}

E

.

>

N

^

n
̃

F

/

?

O

_

o

0

NUL

1

A

APPX
Appendix 2 Available Characters503

Appendix 3 MQTT Broker Setup
This section shows the considerations and procedure for setting up an MQTT broker (Eclipse Mosquitto) the operation ofwhich has been checked.
For an MQTT broker the operation of which has been checked, refer to the following:
Page 46 MQTT broker

Considerations for setup• When the following screens appear during installation, check that the file is downloaded from an appropriate website thenclick the [Run] and [Yes] buttons.

• When installing a new version of Eclipse Mosquitto in an environment where Eclipse Mosquitto with version 1.6.x or earlier
was used with an anonymous user, settings for using it with anonymous users may be required. (Page 514 Using
Eclipse Mosquitto with anonymous users)

Setup procedure
The following shows the procedure for setting up Eclipse Mosquitto with version 2.0.17 (64-bit).

1. Install OpenSSL.
Page 505 Installing OpenSSL

2. Install Eclipse Mosquitto.
Page 507 Installing Eclipse Mosquitto

3. Install Pthread.
Page 508 Installing Pthread

4. Start Eclipse Mosquitto.
Page 509 Starting Eclipse Mosquitto

5. Set access control.
Page 510 Setting access control

6. Set a port number when using a port number other than the default value (1883).
Page 515 Setting a port number

7. Set communication encryption as necessary.
Page 516 Setting communication encryption

8. Configure the settings for connection from another industrial PC as necessary.
Page 528 Configuring the settings for connection from another industrial PC

504

APPX
Appendix 3 MQTT Broker Setup

Installing OpenSSL
The following shows the procedure for installing OpenSSL.

Operating procedure

1. Access the following website, and download the installer of OpenSSL.
• slproweb.com/products/Win32OpenSSL.html

The installer can also be downloaded from the following website:• www.edgecross.org

2. Run the installer.
3. Check the license terms and select "I accept the agreement," and click the [Next>] button.
4. Select an installation destination folder, and click the [Next>] button.

A

5. Select a folder name to add to the start menu, and click the [Next>] button.

APPX
Appendix 3 MQTT Broker Setup505

6. Select "The OpenSSL binaries (/bin) directory," and click the [Next>] button.

7. Click the [Install] button.
8. Select or unselect an amount to donate*1, and click the [Finish] button.
*1

506

When selecting a checkbox and clicking the [Finish] button, the site for donation opens. If it is selected by mistake, close the window tocancel.

APPXAppendix 3 MQTT Broker Setup

Installing Eclipse Mosquitto
The following shows the procedure for installing Eclipse Mosquitto.

Operating procedure

1. Access the following website, and download the installer of Eclipse Mosquitto.
• mosquitto.org

The installer can also be downloaded from the following website:• www.edgecross.org

2. Run the installer.
3. Click the [Next>] button.
4. Make sure that the checkboxes of "Visual Studio Runtime" and "Service" are selected, and click the [Next>] button.

A

5. Select an installation destination folder, and click the [Install] button.

When selecting a folder that requires the administrator authority (example: Program Files) as an installation
destination folder, it is necessary to start a text editor with the administrator authority in advance and open thesetting file for performing the following operations. To perform them without the administrator authority, use afolder that does not require it.
Page 513 Applying to an MQTT broker
Page 514 Using Eclipse Mosquitto with anonymous users
Page 515 Setting a port number
Page 516 Setting communication encryption

6. Click the [Finish] button.

APPX
Appendix 3 MQTT Broker Setup

507

Installing Pthread
The following shows the procedure for installing Pthread.

Operating procedure

1. Access the following website, and download Pthread.
• ftp://sources.redhat.com/pub/pthreads-win32/dll-latest/dll/x86/

2. Copy 'pthreadVC2.dll' to the installation folder for Eclipse Mosquitto.
Pthread can also be downloaded from the following website:• www.edgecross.org

508

APPX
Appendix 3 MQTT Broker Setup

Starting Eclipse Mosquitto
The following shows the procedure for starting Eclipse Mosquitto.

Operating procedure

1. Open the "Administrative Tools" screen, and start the service.
[Control Panel]  [System and Security]  [Administrative Tools]  "Services"

2. Right-click "Mosquitto Broker," and click [Start].

A

APPX
Appendix 3 MQTT Broker Setup

509

Setting access control
The setting differs depending on users using Eclipse Mosquitto.
User using Eclipse Mosquitto

Setting procedureSpecific user

Page 510 Setting a user name and password

Anonymous userWhen setting the port number and communication encryption*1
Page 514 Using Eclipse Mosquitto with anonymous users
When not setting the port number or communication encryption*1
The setting is not required.

*1

For details, refer to the following:
Page 515 Setting a port number
Page 516 Setting communication encryption

Setting a user name and password
The following shows the procedure for setting a user name and password used for user authentication.

Operating procedure

1. Create a password file.
Page 511 Creating a password file

2. Add/delete a user to/from the password file as necessary.
Page 512 Adding/deleting a user to/from a password file

3. Apply the set password file to an MQTT broker.
Page 513 Applying to an MQTT broker

4. Start the service.
5. Right-click "Mosquitto Broker," and click [Restart].

510

APPX
Appendix 3 MQTT Broker Setup

Creating a password file
The following shows the procedure for creating a password file.

Operating procedure

1. Open the command prompt with the administrator authority, and execute the following:
cd (arbitrary storage destination)\mosquitto

2. Execute the following:mosquitto_passwd.exe -c passwdfile username• passwdfile: Name of a password file to create• username: Name of a user to create (6 to 64 characters)

3. Specify a password for "Password" (6 to 512 characters).
4. Specify the same password for "Reenter password."A

APPX
Appendix 3 MQTT Broker Setup

511

Adding/deleting a user to/from a password file
The following shows the procedure for adding/deleting a user to/from a password file.

Operating procedure

1. Open the command prompt with the administrator authority, and execute the following:
cd (arbitrary storage destination)\mosquitto

2. Execute either of the following:
For additionmosquitto_passwd.exe -b passwdfile username2 pw• passwdfile: Name of a password file to which a user is added• username2: Name of a user to add (6 to 64 characters)• pw: Password (6 to 512 characters)

For deletion
mosquitto_passwd.exe -D passwdfile username2• passwdfile: Name of a password file from which a user is deleted• username2: Name of a user to delete

512

APPX
Appendix 3 MQTT Broker SetupApplying to an MQTT broker
The following shows the procedure for applying a set password file to an MQTT broker.

Precautions
If the installation directory for Eclipse Mosquitto requires the administrator authority for editing, etc., it is necessary to start atext editor with the administrator authority in advance and open 'mosquitto.conf.'

Operating procedure

1. Open 'mosquitto.conf' in the installation folder for Eclipse Mosquitto.
2. Add the following to the end in the file.
• allow_anonymous false• password_file (full path of a password file)A
3. Start the service.
4. Right-click "Mosquitto Broker," and click [Restart].

APPX
Appendix 3 MQTT Broker Setup

513

Using Eclipse Mosquitto with anonymous users
The following shows the procedure for using Eclipse Mosquitto with anonymous users.

Precautions
If the installation directory for Eclipse Mosquitto requires the administrator authority for editing, etc., it is necessary to start atext editor with the administrator authority in advance and open 'mosquitto.conf.'

Operating procedure

1. Open 'mosquitto.conf' in the installation folder for Eclipse Mosquitto.
2. Add the following to the end in the file.
• allow_anonymous true

3. Start the service.
4. Right-click "Mosquitto Broker," and click [Restart].

514

APPX
Appendix 3 MQTT Broker SetupSetting a port number
The following shows the procedure for setting a port number when using a port number other than the default value (1883).

Precautions
If the installation directory for Eclipse Mosquitto requires the administrator authority for editing, etc., it is necessary to start atext editor with the administrator authority in advance and open 'mosquitto.conf.'

Operating procedure

1. Open 'mosquitto.conf' in the installation folder for Eclipse Mosquitto.
2. Add the following to the end in the file.
• listener Port numberA
3. Start the service.
4. Right-click "Mosquitto Broker," and click [Restart].

APPX
Appendix 3 MQTT Broker Setup

515

Setting communication encryption
The following shows the procedures for setting communication encryption by using each authentication method.

Server authentication
The following shows the procedure for setting communication encryption by using server authentication.

Operating procedure

1. Create a certificate.
For using a self-signed certificate for certificate authority certificate, refer to steps 1 to 4 shown in the following:
Page 519 Creating a certificate (self-signed certificate for certificate authority certificate)
When requesting a signature from an external authority, create a certificate according to the procedure of each authority.

2. Open 'mosquitto.conf' in the installation folder for Eclipse Mosquitto.
If the installation directory for Eclipse Mosquitto requires the administrator authority for editing, etc., it is necessary to start atext editor with the administrator authority in advance and open 'mosquitto.conf.'

3. Add the following to the end in the file.
• listener 8883
• cafile Full path of a self-signed certificate• certfile Full path of a server certificate• keyfile Full path of a server secret key

4. Start the service.

516

APPX
Appendix 3 MQTT Broker Setup

5. Right-click "Mosquitto Broker," and click [Restart].

A

APPX
Appendix 3 MQTT Broker Setup

517

Server authentication & client authentication
The following shows the procedure for setting communication encryption by using server authentication & client
authentication.

Operating procedure

1. Create a certificate.
For using a self-signed certificate for certificate authority certificate, refer to the following:
Page 519 Creating a certificate (self-signed certificate for certificate authority certificate)
When requesting a signature from an external authority, create a certificate according to the procedure of each authority.

2. Open 'mosquitto.conf' in the installation folder for Eclipse Mosquitto.
If the installation directory for Eclipse Mosquitto requires the administrator authority for editing, etc., it is necessary to start atext editor with the administrator authority in advance and open 'mosquitto.conf.'

3. Add the following to the end in the file.
• listener 8883
• cafile Full path of a self-signed certificate• certfile Full path of a server certificate• keyfile Full path of a server secret key• require_certificate true

4. Start the service.
5. Right-click "Mosquitto Broker," and click [Restart].

518

APPX
Appendix 3 MQTT Broker Setup

Creating a certificate (self-signed certificate for certificate authority certificate)
The following shows the procedure for creating a certificate when using a self-signed certificate for certificate authority
certificate.

Operating procedure

1. Create a self-signed certificate and a CA secret key.
Page 520 Creating a self-signed certificate and a CA secret key

2. Create a server secret key.
Page 521 Creating a server secret key

3. Create a certificate signing request for a server certificate.
Page 522 Creating a certificate signing request (server certificate)

4. Create a server certificate.
Page 523 Creating a server certificate

5. Create a client secret key.
Page 524 Creating a client secret key

6. Create a certificate signing request for a client certificate.
Page 525 Creating a certificate signing request (client certificate)

7. Create a client certificate.
Page 527 Creating a client certificate

A

APPX
Appendix 3 MQTT Broker Setup

519

Creating a self-signed certificate and a CA secret key
The following shows the procedure for creating a self-signed certificate and a CA secret key.

Operating procedure

1. Open the command prompt with the administrator authority, and execute the following:
cd (installation folder for OpenSSL)\bin

2. Execute the following:
openssl.exe req -new -x509 -days 365 -keyout ca.key -out ca.cer• 365: Number of valid days
• ca.key: Name of a CA secret key file to create• ca.cer: Name of a self-signed certificate file to create

3. Enter the following items:
Item

Description

Enter PEM pass phrase

PEM passphrase

Verifying - Enter PEM pass phrase

PEM passphrase (confirmation)*1

Country Name (2 letter code)*2

Country name

State or Province Name (full name) [Some-State]*2

Prefecture nameLocality Name (eg, city) []*2

Municipality name

Organization Name (eg, company) [Internet Widgits
Pty Ltd]*2

Organization name

Organizational Unit Name (eg, section) []*2

Department nameCommon Name (e.g. server FQDN or YOUR name)[]*2

Host name

Email Address []*2

E-mail address

*1
*2

520

Enter a PEM passphrase entered for "Enter PEM pass phrase" again for confirmation.
Optional

APPX
Appendix 3 MQTT Broker Setup

Precautions
All of the following items cannot be the same as those entered when creating a certificate signing request. (Page 522
Creating a certificate signing request (server certificate), Page 525 Creating a certificate signing request (client certificate))• Country Name (2 letter code)• State or Province Name (full name) [Some-State]• Locality Name (eg, city) []• Organization Name (eg, company) [Internet Widgits Pty Ltd]• Organizational Unit Name (eg, section) []• Common Name (e.g. server FQDN or YOUR name) []• Email Address []Creating a server secret key
The following shows the procedure for creating a server secret key.

Operating procedure

1. Open the command prompt with the administrator authority, and execute the following:
cd (installation folder for OpenSSL)\bin

2. Execute the following:
openssl.exe genrsa -out server.key• server.key: Name of a server secret key file to createA

APPX
Appendix 3 MQTT Broker Setup

521

Creating a certificate signing request (server certificate)
The following shows the procedure for creating a certificate signing request.

Operating procedure

1. Open the command prompt with the administrator authority, and execute the following:
cd (installation folder for OpenSSL)\bin

2. Execute the following:
openssl.exe req -out server.csr -key server.key -new• server.csr: Name of a certificate signing request file to create• server.key: Name of a server secret key file created in the following:
Page 521 Creating a server secret key

3. Enter the following items:
Item

Description

Country Name (2 letter code)*1

Country name

State or Province Name (full name) [Some-State]*1

Prefecture nameLocality Name (eg, city) []*1

Municipality name

Organization Name (eg, company) [Internet Widgits
Pty Ltd]*1

Organization name

Organizational Unit Name (eg, section) []*1

Department nameCommon Name (e.g. server FQDN or YOUR name)[]Host name (machine name of a server)

Email Address []*1

E-mail address

*1

522

Optional

APPX
Appendix 3 MQTT Broker Setup

Precautions
All of the following items cannot be the same as those entered when creating a self-signed certificate and a CA secret key.
(Page 520 Creating a self-signed certificate and a CA secret key)
• Country Name (2 letter code)• State or Province Name (full name) [Some-State]• Locality Name (eg, city) []• Organization Name (eg, company) [Internet Widgits Pty Ltd]• Organizational Unit Name (eg, section) []• Common Name (e.g. server FQDN or YOUR name) []• Email Address []Creating a server certificate
The following shows the procedure for creating a server certificate.

Operating procedure

1. Open the command prompt with the administrator authority, and execute the following:
cd (installation folder for OpenSSL)\bin

2. Execute the following:
openssl.exe x509 -req -in server.csr -CA ca.cer -CAkey ca.key -CAcreateserial -out server.cer -days 365• server.csr: Name of a certificate signing request file created in the following:
Page 522 Creating a certificate signing request (server certificate)• ca.cer: Name of a self-signed certificate file created in the following:
Page 520 Creating a self-signed certificate and a CA secret key• ca.key: Name of a CA secret key file created in the following:
Page 520 Creating a self-signed certificate and a CA secret key• server.cer: Name of a server certificate file to createA• 365: Number of valid days

3. Enter the following item:
Item

Description

Enter pass phrase for (CA secret key file name).key

Passphrase of a CA secret key*1*1

Enter the same content as that of "Enter PEM pass phrase" entered in the following:
Page 520 Creating a self-signed certificate and a CA secret key

APPX
Appendix 3 MQTT Broker Setup

523Creating a client secret key
The following shows the procedure for creating a client secret key.

Operating procedure

1. Open the command prompt with the administrator authority, and execute the following:
cd (installation folder for OpenSSL)\bin

2. Execute the following:
openssl.exe genrsa -out client.key• client.key: Name of a client secret key file to create

524

APPX
Appendix 3 MQTT Broker Setup

Creating a certificate signing request (client certificate)
The following shows the procedure for creating a certificate signing request.

Operating procedure

1. Open the command prompt with the administrator authority, and execute the following:
cd (installation folder for OpenSSL)\bin

2. Execute the following:
openssl.exe req -out client.csr -key client.key -new• client.csr: Name of a certificate signing request file to create• client.key: Name of a client secret key file created in the following:
Page 524 Creating a client secret key

3. Enter the following items:
Item

Description

Country Name (2 letter code)*1

Country name

State or Province Name (full name) [Some-State]*1

Prefecture nameLocality Name (eg, city) []*1

Municipality name

Organization Name (eg, company) [Internet Widgits
Pty Ltd]*1

Organization name

Organizational Unit Name (eg, section) []*1

Department nameCommon Name (e.g. server FQDN or YOUR name)[]Host name (machine name of a client)

Email Address []*1

E-mail address*1

OptionalA

APPX
Appendix 3 MQTT Broker Setup

525

Precautions
All of the following items cannot be the same as those entered when creating a self-signed certificate and a CA secret key.
(Page 520 Creating a self-signed certificate and a CA secret key)
• Country Name (2 letter code)• State or Province Name (full name) [Some-State]• Locality Name (eg, city) []• Organization Name (eg, company) [Internet Widgits Pty Ltd]• Organizational Unit Name (eg, section) []• Common Name (e.g. server FQDN or YOUR name) []• Email Address []

526

APPX
Appendix 3 MQTT Broker Setup

Creating a client certificate
The following shows the procedure for creating a client certificate.

Operating procedure

1. Open the command prompt with the administrator authority, and execute the following:
cd (installation folder for OpenSSL)\bin

2. Execute the following:
openssl.exe x509 -req -in client.csr -CA ca.cer -CAkey ca.key -CAcreateserial -out client.cer -days 365• client.csr: Name of a certificate signing request file created in the following:
Page 525 Creating a certificate signing request (client certificate)• ca.cer: Name of a self-signed certificate file created in the following:
Page 520 Creating a self-signed certificate and a CA secret key• ca.key: Name of a CA secret key file created in the following:
Page 520 Creating a self-signed certificate and a CA secret key• client.cer: Name of a client certificate file to create• 365: Number of valid days

3. Enter the following item:
Item

Description

Enter pass phrase for (CA secret key file name).key

Passphrase of a CA secret key*1*1

Enter the same content as that of "Enter PEM pass phrase" entered in the following:
Page 520 Creating a self-signed certificate and a CA secret key

A

APPX
Appendix 3 MQTT Broker Setup

527

Configuring the settings for connection from another industrial
PC
The following shows the setting procedure for connection from an industrial PC other than one on which Eclipse Mosquitto is
running.

Operating procedure

1. Set access control for connection from another industrial PC.
Page 528 Setting access control

2. Set a port number used for connection from another industrial PC.
Page 528 Setting a port number

3. Set a firewall.
Page 528 Setting a firewall

Setting access control
For access control for connection from another industrial PC, refer to the following:
Page 510 Setting access control

Setting a port number
Set a port number used for connection from another industrial PC.
This setting is required even when using the default value (1883).

Operating procedure

1. Open "mosquitto.conf" in the installation directory for Eclipse Mosquitto in a text editor.
If the installation directory for Eclipse Mosquitto is one such as Program Files that requires the administrator authority, start atext editor with the administrator authority in advance and open "mosquitto.conf."

2. Add the following to the end in the file.
• listener Port number used for connection with another industrial PC

Setting a firewall
Set a firewall.
Communication connections to Eclipse Mosquitto must be allowed in the firewall of an industrial PC on which Eclipse
Mosquitto is running.
Refer to the following to change the firewall setting.
Page 560 Allowing Communication Connections between Industrial PCs

528

APPX
Appendix 3 MQTT Broker Setup

Appendix 4 Database Setup
This section shows the consideration and procedure for setting up a database (PostgreSQL) the operation of which has beenchecked.
For a database the operation of which has been checked, refer to the following:
Page 78 Database

Consideration for setup
When the following screens appear during installation, check that the file is downloaded from an appropriate website thenclick the [Run] and [Yes] buttons.

Setup procedure
The following shows the procedure for setting up PostgreSQL.

1. Install PostgreSQL.
Page 530 Installing PostgreSQL

2. Connect to PostgreSQL.
Page 532 Connecting to PostgreSQL

A

3. When using an account other than the 'postgres' account*1 which is a superuser, create an account.
*1

Automatically created when installing PostgreSQL.

Page 533 Creating an account for PostgreSQL

4. Install the ODBC driver for PostgreSQL.
Page 535 Installing the ODBC driver for PostgreSQL

5. Configure the ODBC setting.
Page 536 ODBC setting

6. Create a table by using a DDL.
Page 537 Creating a table by using a DDL

7. Set a privilege to a table.
Page 538 Setting a privilege to a table

APPX
Appendix 4 Database Setup

529

Installing PostgreSQL
The following shows the procedure for installing PostgreSQL.

Operating procedure

1. Access the following website, and download the installer of PostgreSQL.
• www.postgresql.org

The installer can also be downloaded from the following website:• www.edgecross.org

2. Run the installer.
3. Click the [Next>] button.
4. Select an installation folder, and click the [Next>] button.

5. Click the [Next>] button.
6. Select a data directory, and click the [Next>] button.

530

APPX
Appendix 4 Database Setup

7. Set a password*1 for the 'postgres' account that is a superuser, and click the [Next>] button.
*1

Must be set to 6 to 32 characters when using the 'postgres' account.

8. Set a port number for "Port," and click the [Next>] button.

9. Select "C" for "Locale," and click the [Next>] button.

A

10. Click the [Next>] button.
11. Click the [Next>] button.
12. Unselect the checkbox in the screen, and click the [Finish] button.

APPX
Appendix 4 Database Setup

531

Connecting to PostgreSQL
The following shows the procedure for connecting to PostgreSQL.

Precautions
Depending on an industrial PC used*1, starting pgAdmin may fail. In this case, restart pgAdmin or refer to the following:*1

Industrial PC in which Atom is used for a CPU or the load is highPage 540 Setup procedure using a batch file

Operating procedure

1. Start pgAdmin 4 from "PostgreSQL 10" in Windows Start.
2. Right-click "PostgreSQL 10" and select [Connect Server].

3. Set a password for the 'postgres' account.

4. Click the [OK] button.

532

APPX
Appendix 4 Database Setup

Creating an account for PostgreSQL
The following shows the procedure for creating an account for PostgreSQL.
When using the 'postgres' account*1 which is a superuser, this procedure is not required.
*1

Automatically created when installing PostgreSQL.

Operating procedure

1. Start pgAdmin 4 from "PostgreSQL 10" in Windows Start.
2. Right-click "PostgreSQL 10" and select [Create]  [Login/Group Role...].

3. Set a user name for "Name" in the [General] tab (1 to 32 characters).

A

4. Set a password for "Password" in the [Definition] tab (6 to 32 characters).

APPX
Appendix 4 Database Setup533

5. Select "Yes" for "Can login?" in the [Privileges] tab.

6. Click the [Save] button.

534

APPX
Appendix 4 Database Setup

Installing the ODBC driver for PostgreSQL
The following shows the procedure for installing the ODBC driver for PostgreSQL.

Operating procedure

1. Access the following website, and download the installer of the ODBC driver for PostgreSQL.
• www.postgresql.org

The installer can also be downloaded from the following website:• www.edgecross.org

2. Run the installer.
3. Click the [Next] button.
4. Select the checkbox of "I accept the terms in the License Agreement," and click the [Next] button.

5. Check that 'ODBC Driver' is an installation target, and click the [Next] button.

A

6. Click the [Install] button.
7. Click the [Finish] button.

APPX
Appendix 4 Database Setup

535

ODBC setting
The following shows the procedure for setting ODBC.

Operating procedure

1. Open the command prompt, and execute the following file.
ODBC Data Source Administrator starts.
• "%SystemRoot%\system32\odbcad32.exe"

2. Select the [System DSN] tab, and click the [Add] button.

3. Select "PostgreSQL Unicode(x64)," and click the [Finish] button.

4. Set each item, and click the [Save] button.*1*1

Set "localhost" for "Server" and the name of a database to save data for "Database."

5. Click the [OK] button.

536

APPX
Appendix 4 Database Setup

Creating a table by using a DDL
The following shows the procedure for creating a table by using a DDL.

Precautions
If there is another table with a same name, the existing table will be deleted and a new one will be created. Therefore, datastored in the existing table will also be deleted.

Operating procedure

1. Start pgAdmin 4 from "PostgreSQL 10" in Windows Start.
2. Select a database to use, and select [Tools]  [Query Tool].

3. Click.

4. Select an SQL file (output DDL file*1), and click the [Select] button.
*1

A DDL file must be output to the hard disk of an industrial PC, not to a network drive or removal disk.
For outputting a DDL file, refer to the following:
Real-time Flow Designer: Page 157 Definition output
Management Shell Explorer: Page 287 DB saving setting

5. Click

A

.

APPX
Appendix 4 Database Setup

537

Setting a privilege to a table
The following shows the procedure for setting a privilege to a table.

Operating procedure

1. Right-click a table set in the following section, and select [Properties].
Page 537 Creating a table by using a DDL

2. Select the [Security] tab.
3. Click the [+] button of "Privileges."

4. Select an account set in the following section under "Grantee."Page 533 Creating an account for PostgreSQL

538

APPX
Appendix 4 Database Setup

5. Select the checkbox of "INSERT" under "Privileges."

6. Click the [Save] button.

A

APPX
Appendix 4 Database Setup

539

Setup procedure using a batch file
The following shows the procedure for setting up PostgreSQL by using a batch file.
If starting pgAdmin fails, set up PostgreSQL by using a batch file.
When pgAdmin starts successfully, perform the operations in steps 2 and later described in the following:
Page 529 Setup procedure

Operating procedure

1. Perform either of the following operations:• When using the 'postgres' account*1 or a created account: Page 541 Creating a table by using a batch file
• When using an account other than the 'postgres' account*1 or creating a new account: (Page 542 Creating a user andtable by using a batch file)*1

Automatically created when installing PostgreSQL.

2. Install the ODBC driver for PostgreSQL.
Page 535 Installing the ODBC driver for PostgreSQL

3. Configure the ODBC setting.
Page 536 ODBC setting

540

APPX
Appendix 4 Database Setup

Creating a table by using a batch file
The following shows the procedure for creating a table by using a batch file.

Precautions• When using an account other than the 'postgres' account or creating a new account, create a user and table by using abatch file. (Page 542 Creating a user and table by using a batch file)• If there is another table with a same name, the existing table will be deleted and a new one will be created. Therefore, datastored in the existing table will also be deleted.
• Do not use double-byte characters for a table name and field name. (Page 156 Access table)

Operating procedure

1. Create a batch file ((any file name).bat) as shown below, and save it to any folder.
@echo off
SET SERVER=localhost
SET DB=postgres
SET PORT=(Port Number*1)
SET USER=(User Name*2)
echo CREATE TABLE"(Installation folder*3)\bin\psql.exe" ^-f "(Path of a DDL file*4)" ^-h %SERVER% -U %USER% -d %DB% -p %PORT%
pause

*1
*2
*3
*4

Specify a port number set in the following:
Page 530 Installing PostgreSQL
Specify the name of a user set for a database. When using a superuser, specify 'postgres.'
Specify an installation folder selected in the following:
Page 530 Installing PostgreSQLA DDL file must be output to the hard disk of an industrial PC, not to a network drive or removal disk.
For outputting a DDL file, refer to the following:
Real-time Flow Designer: Page 157 Definition output
Management Shell Explorer: Page 287 DB saving settingA

The following shows an example of creating a batch file.
@echo off
SET SERVER=localhost
SET DB=postgres
SET PORT=5432
SET USER=postgres
echo CREATE TABLE"C:\Program Files\PostgreSQL\10\bin\psql.exe" ^-f "C:\test\test2.sql" ^-h %SERVER% -U %USER% -d %DB% -p %PORT%
pause

2. Execute the created batch file.
3. Enter the password for a user entered in step 1.

4. Press any key to end.

APPX
Appendix 4 Database Setup

541

Creating a user and table by using a batch file
The following shows the procedure for creating a user and table by using a batch file.

Precautions• When using the 'postgres' account or a created account, create only a table by using a batch file. (Page 541 Creating atable by using a batch file)• If there is another table with a same name, the existing table will be deleted and a new one will be created. Therefore, datastored in the existing table will also be deleted.
• Do not use double-byte characters for a table name and field name. (Page 156 Access table)

Operating procedure

1. Create a batch file ((any file name).bat) as shown below, and save it to any folder.
@echo off
SET SERVER=localhost
SET DB=postgres
SET PORT=(Port Number*1)
SET SUPERUSER=postgres
SET USER=(User Name*2)
SET PASS=(Password*3)
echo CREATE USER"(Installation folder*4)\10\bin\psql.exe" ^-c "CREATE USER %USER% PASSWORD '%PASS%';" -h %SERVER% -U %SUPERUSER% -d %DB% -p %PORT%
echo CREATE TABLE"(Installation folder*4)\bin\psql.exe" ^-f "(Path of a DDL file*5)" ^-h %SERVER% -U %USER% -d %DB% -p %PORT%
pause

*1
*2
*3
*4
*5

Specify a port number set in the following:
Page 530 Installing PostgreSQL
Specify the name of a user to create in a database (1 to 32 characters).
Specify the password for a user to create in a database (6 to 32 characters).
Specify an installation folder selected in the following:
Page 530 Installing PostgreSQLA DDL file must be output to the hard disk of an industrial PC, not to a network drive or removal disk.
For outputting a DDL file, refer to the following:
Real-time Flow Designer: Page 157 Definition output
Management Shell Explorer: Page 287 DB saving setting

The following shows an example of creating a batch file.
@echo off
SET SERVER=localhost
SET DB=postgres
SET PORT=5432
SET SUPERUSER=postgres
SET USER=edgecross
SET PASS=password
echo CREATE USER
"C:\Program Files\PostgreSQL\10\bin\psql.exe" ^-c "CREATE USER %USER% PASSWORD '%PASS%';" -h %SERVER% -U %SUPERUSER% -d %DB% -p %PORT%
echo CREATE TABLE"C:\Program Files\PostgreSQL\10\bin\psql.exe" ^-f "C:\test\test.sql" ^-h %SERVER% -U %USER% -d %DB% -p %PORT%
pause

2. Execute the created batch file.

542

APPX
Appendix 4 Database Setup

3. Enter the password for the 'postgres' account set in the following:
Page 530 Installing PostgreSQL

4. Enter the password entered in step 1.

5. Press any key to end.

A

APPX
Appendix 4 Database Setup543

Appendix 5 Data Used in Edgecross Basic SoftwareThis section shows the data used in Edgecross Basic Software.

Data type and value range
The following table shows the data types and ranges of values used in Edgecross Basic Software.
Data type

Description

Value range

BOOL

Binary (0 or 1)

0, 1

INT

Signed 16-bit integer-32768 to 32767

UINT

Unsigned 16-bit integer

0 to 65535

DINT

Signed 32-bit integer-2147483648 to 2147483647

UDINT

Unsigned 32-bit integer

0 to 4294967295

LINT

Signed 64-bit integer-9223372036854775808 to 9223372036854775807

ULINT

Unsigned 64-bit integer

0 to 18446744073709551615

REAL

32-bit real number*1,*2•0• 1.40129846E-45 (absolute value) to 3.40282346E38 (absolute value)

LREAL

64-bit real number*1,*2•0• 4.9406564584124654E-324 (absolute value) to 1.7976931348623158E308 (absolute value)

STRING

Character string (ASCII)*3,*4,*5

0 to 32 characters

WSTRING

Character string (Unicode)*3,*4,*5

0 to 16 characters

*1
*2

*3
*4

*5

Real numbers are floating-point numbers compliant with IEEE 754.
Numerical values entered in the screen of Edgecross Basic Software are converted into floating point numbers compliant with IEEE 754;
therefore, enter numerical values in the following range so that entered values are retained.
REAL: 0, 1.17550E-38 (absolute value) to 3.40282E38 (absolute value)
LREAL: 0, 2.22507385850721E-308 (absolute value) to 1.79769313486231E308 (absolute value)
When a terminator is contained, the string from the leading character through the character immediately before the terminator is valid.
For available characters, refer to the following section. However, character strings of the actual data are not checked whether they areavailable or not.
Page 545 Available characters
The data size is a variable length.

Values that can be entered in the screen
The following table shows the values that can be entered in the screen of Edgecross Basic Software.
Type

Availablecharacter

Data type

Integer-, +, [0 to 9]

Binary (0 or 1)
SignedUnsigned

Real number*1-, +, e, E, . (decimal
point), [0 to 9]

Default value

Range of the number ofcharacters

BOOL

0

1 to 21 characters

INT

0

DINT

0

LINT

0

UINT

0

UDINT

0

ULINT

0

Single-precision real
number (32-bit)

REAL

0.0

1 to 12 characters (significant
digits of mantissa: 6 digits)

Double-precision real
number (64-bit)

LREAL

0.0

1 to 22 characters (significant
digits of mantissa: 15 digits)

Character string(ASCII)*2

Same as the STRING
type.
Page 545 STRING
type

ASCII

STRINGBlank

0 to 32 characters

Character string(UNICODE)*2

Same as the
WSTRING type.
Page 545
WSTRING type

UnicodeWSTRINGBlank

0 to 16 characters

*1
*2

544

For a numeric string starting with "0" at the leftmost position, the portion from the first non-zero figure to the end is treated as mantissa.
(Example) 0.000123456 is valid.
Escape sequence (such as \n and \u000A) are handled without converting into control characters.
APPX
Appendix 5 Data Used in Edgecross Basic SoftwareAvailable characters
STRING typeThe following lists the available characters.
Characters in the shaded area can be used.
0

2

3

4

5

6

7

(SP)

0

@

P

‘

p

1

!

1

A

Q

a

q

2

"

2

B

R

b

r

3

#

3

C

S

c

s

4

$

4

D

T

d

t

5

%

5

E

U

e

u

6

&

6

F

V

f

v

7

'

7

G

W

g

w

8

(

8

H

X

h

x

9

)

9

I

Y

i

y

A

*

:

J

Z

j

z

B

+

;

K

[

k

C

,

<

L

\

l

{
|

D

-

=

M

]

m

}

E

.

>

N

^

n

̃

F

/

?

O

_

o

0

NUL

1

If an unavailable character is output, the character will be replaced with a period (.). However, if a string
terminator (0) is used halfway in the data, the string terminator (0) is not replaced with a period (.) and thesubsequent data is not output.

A

WSTRING type
Characters defined by Unicode can be used. However, U+0000 to U+001F, U+007F to U+00A0, U+00AD, U+2028, andU+2029 cannot be used.
When using combining characters, a character before combining is counted as one character.
Ex.

A combining character 'à' composed of a character 'a' (U+0061) and a grave accent '`' (U+0300)
It is displayed as one character in the screen but it is counted as two characters.

If a string terminator (0) is used halfway in the data, the subsequent data is not output.

APPX
Appendix 5 Data Used in Edgecross Basic Software

545

Value after changing the data type
If the data type is changed when a value is set for data, the value will be changed as shown in the following table:
Data type

Value after change

Before change

After change

Integer type*1

Integer type*1• A set value is within the range of data types after change*2: Not changed• A set value is out of the range of data types after change*2: 0

Real number type*3

0.0String type*4

Blank

Real number type*3

String type (STRING)

Integer type*1

0

Real number type*3• A set value is within the range of data types after change*2: Not changed• A set value is out of the range of data types after change*2: 0.0

String type*4

Blank

Integer type*1
Real number type0*3String type (STRING)

String type (WSTRING)

*1
*2
*3
*4

546

0.0
Not changed

String type (WSTRING)

Blank

Integer type*10Real number type*3

0.0String type (STRING)

Blank

String type (WSTRING)

Not changed

Refers to BOOL, INT, UINT, UDINT, LINT, or ULINT.
For the data types and ranges of values, refer to the following:
Page 544 Data type and value range
Refers to REAL or LREAL.
Refers to STRING or LSTRING.

APPXAppendix 5 Data Used in Edgecross Basic Software

Data assignment
In data collection and feedback, data assignment means to assign input and output data to the data in the target system.

Data assignment availability
The following shows the availability of data type assignment in CSV File Data collector.
For other data collectors, refer to the manual for a data collector used.
When the target data type is integer
: Assignment available, : Assignment unavailable
Function

CSV File Data collector

Target data type
BOOL

UINT

UDINT

ULINT

INT

DINT

LINT















When the target data type is real
: Assignment available, : Assignment unavailable
Function

CSV File Data collector

Target data type
REAL

LREAL





When the target data type is string
: Assignment available, : Assignment unavailable
Function

CSV File Data collector

Target data type
STRINGWSTRINGNumber of points for data assignment
CSV File Data collector performs file input and output. The number of points for data assignment is not required to beAconsidered.
For other data collectors, refer to the manual for a data collector used.

APPX
Appendix 5 Data Used in Edgecross Basic Software

547

Data substitution
Data substitution means for converting the data type of output data of a process to the data type of input data of a process.

Data flow between processes
The following shows availability of data substitution between processes.
: Substitution available, : Substitution unavailable
Output data from previous
process

Input data to next process
BOOL

UINT

INT

UDINT

DINT

REAL

ULINT

LINT

LREA
L

STRIN
G

WSTRIN
G

BOOL



*1

*1

*1

*1

*1

*1

*1

*1





UINT























INT























UDINT











*2











DINT











*2











REAL























*2

ULINT























LINT

















*2





LREAL























*3

STRING



















*3

WSTRING





















*1
*2
*3

548

Substituted as bit OFF (0) and ON (1).
There will be an error with the value.
If the string size of the input data to the next process is smaller than that of the output data from the previous process, the string is
truncated before substitution.

APPX
Appendix 5 Data Used in Edgecross Basic Software

Data substitution by feedback
Response data and constant values can be returned back to the system by providing feedback.
The following shows availability of data substitution for each substitution target data type.
When the target data type is integer
: Substitution available, : Substitution unavailable
Setting value

Target data type
BOOL

*1

INT

UDINT

DINT

ULINT

LINT















Integer

*1













Real number















Character string(ASCII)















Character string(UNICODE)















Response data
Constant

UINT"0" is substituted as bit OFF and other than "0" as bit ON.

When the target data type is real
: Substitution available, : Substitution unavailable
Setting value

Target data type
REAL

LREAL





IntegerReal numberCharacter string(ASCII)Character string(UNICODE)

Response data
Constant

A

When the target data type is string
: Substitution available, : Substitution unavailable
Setting value

Target data type
STRINGWSTRING

*1



IntegerReal numberCharacter string(ASCII)*1



Character string(UNICODE)*1

Response data
Constant*1

If the string size of the substitution target is smaller than the actual string size, the string is truncated before substitution.

APPX
Appendix 5 Data Used in Edgecross Basic Software

549

Data comparison
Data can be compared, for example, as a condition for segmenting data in data processing.
Significance and equality of values can be compared.

Significance comparison
The following shows availability of significance comparison for each data type.
When the comparison target is an integer
: Comparison available, : Comparison unavailable
Comparison source

Comparison target
BOOL

UINT

INT

UDINT

DINT

ULINT

LINT

BOOL















UINT















INT















UDINT















DINT















ULINT















LINT















REAL











*1

*1

LREAL











*1

*1

STRING















WSTRING















*1

There is a difference in the accuracy of the data type to be compared. Therefore, values may not be compared correctly when they areclose to each other.

When the comparison target is a real number or string
: Comparison available, : Comparison unavailable
Comparison source

Comparison target
REAL

LREAL

STRINGWSTRING

BOOL









UINT









INT









UDINT









DINT









ULINT

*1

*1





LINT

*1

*1





REAL



*2





LREAL

*2







STRING

WSTRING









*1
*2

There is a difference in the accuracy of the data type to be compared. Therefore, values may not be compared correctly when they areclose to each other.
Since real numbers are compared for equality in a binary comparison, a single-precision real number may not be compared with adouble-precision real number correctly when numbers to be compared are close or equal to each other.

When the comparison target is a constant
: Comparison available, : Comparison unavailable
Comparison source

Comparison target
Constant (integer)

Constant (real number)

Constant (ASCII)

Constant (UNICODE)

BOOL









UINT









INT









UDINT









DINT









550

APPX
Appendix 5 Data Used in Edgecross Basic SoftwareComparison source

Comparison target
Constant (integer)

Constant (real number)

Constant (ASCII)

Constant (UNICODE)

ULINT









LINT









REAL



*1





LREAL









STRING

WSTRING









*1

Since real numbers are compared for equality in a binary comparison, a single-precision real number may not be compared with adouble-precision real number correctly when numbers to be compared are close or equal to each other. (A constant (real number) is
regarded as a double-precision real number.)Equality comparison
The following shows availability of equality comparison for each data type.
When the comparison target is an integer
: Comparison available, : Comparison unavailable
Comparison source

Comparison target
BOOL

UINT

INT

UDINT

DINT

ULINT

LINT

BOOL



*1

*1

*1

*1

*1

*1

UINT

*1













INT

*1













UDINT

*1













DINT

*1















ULINT

*1













LINT

*1















REAL















LREAL















STRING















WSTRING















*1

A

A bit is compared as an integer. (OFF: 0, ON: 1)

When the comparison target is a real number or string
: Comparison available, : Comparison unavailable
Comparison source

Comparison target
REAL

LREAL

STRINGWSTRING

BOOL









UINT









INT









UDINT









DINT









ULINT









LINT









REAL

*1

*1





LREAL

*1

*1





STRING





*2



WSTRING







*2

*1
*2

Since real numbers are compared for equality in a binary comparison, a single-precision real number may not be compared with adouble-precision real number correctly.
Equality is compared with actual strings. (Comparison is allowed if the character size for the data type differs from each other.)

When the comparison target is a constant
: Comparison available, : Comparison unavailable
Comparison source

BOOL

Comparison target
Constant (integer)

Constant (real number)

Constant (ASCII)

Constant (UNICODE)

*1







APPX
Appendix 5 Data Used in Edgecross Basic Software

551

Comparison source

Comparison target
Constant (integer)

Constant (real number)

Constant (ASCII)

Constant (UNICODE)

UINT









INT









UDINT









DINT









ULINT









LINT









REAL



*2





LREAL



*2



STRING

WSTRING







*1
*2
*3


*3


*3

A bit is compared as an integer. (OFF: 0, ON: 1)
Since real numbers are compared for equality in a binary comparison, a single-precision real number may not be compared with adouble-precision real number correctly. (A constant (real number) is regarded as a double-precision real number.)Equality is compared with actual strings. (Comparison is allowed if the character size for the data type differs from each other.)

Data missing
Data missing means that collected data is lacking and not continuous.
When the data storing (file saving) function or the data distribution (MQTT distribution) function is performed in a datacollection process, data missing information is output. However, it will not be output after a data modification process.
For the output method of data missing information, refer to the following:• For data storing (file saving)Page 65 Data missing• For data distribution (MQTT distribution)
Page 81 Data missing

Whether data missing occurred in a running process flow can be checked by monitoring the number of timesof data missing in the process flow diagnostics or status memory monitor of Real-time Flow Designer.
Page 337 Process flow diagnostics
Page 340 Status memory monitor
Page 433 Real-time Flow Manager Status

552

APPX
Appendix 5 Data Used in Edgecross Basic Software

Appendix 6 Using a Remote Shared Folder
This section shows the settings required for setting a remote shared folder.
Note that a network drive (drive assigned by using a Windows function) cannot be used.

Using a shared folder with specifying a user account in
Edgecross Basic Software
The following shows the setting procedures for using a remote shared folder by specifying a user account in Edgecross Basic
Software.

Setting a shared folder
The following shows the procedure for setting a shared folder.
Create a folder to publish as a shared folder in an industrial PC on which Edgecross Basic Software is installed, and configure
the sharing settings.
The following shows a setting example for Windows 10.
For other operating systems, refer to the manual or online help for an operating system used.

1. Click the [Advanced Sharing] button in the [Sharing] tabin the properties of a folder.

A

2. Select the checkbox of "Share this folder."3. Set a share name.
4. Click the [Permissions] button.

APPX
Appendix 6 Using a Remote Shared Folder

553

5. Click the [Add] button.

6. Enter the account name of a user account specified in
Edgecross Basic Software in "Enter the object names toselect."7. Click the [OK] button.

8. Select the checkboxes of "Change" and "Read" for thepermissions for the user account specified in EdgecrossBasic Software.

9. Click the [OK] button.

554

APPX
Appendix 6 Using a Remote Shared Folder

Setting for accessing a shared folder with a user account without the access right
The following shows the setting procedure for accessing a shared folder by specifying a user account without the access rightin Edgecross Basic Software.
If a user account with the access right is specified, this setting is not required.

Operating procedure

1. Sign in to an industrial PC with a user account specified in Edgecross Basic Software.
2. Open the "Add a Windows Credential" screen to set the following items required for accessing a shared folder.
[Control Panel]  [User Accounts]  [Manage Windows Credentials]  [Add a Windows credential]

Item name

Setting

Internet or network address

Address of a personal computer on which a shared folder is locatedUser name

User name of a user account with the access right to a shared folder

Password

Password for a user account with the access right to a shared folder

A

Consideration
Specify the path name of a shared folder specified in Edgecross Basic Software in UNC format.
(Example 1) \\(IP address)\share_folder(Example 2) \\file_server\share_folder
When a remote shared folder (example: 'PC name: Edgecross, shared folder name: KYOUYUU') is assigned to a network
drive (example: 'Z:'), set '\\Edgecross\KYOUYUU.' ('Z:\' cannot be set.)

APPX
Appendix 6 Using a Remote Shared Folder

555

Using a shared folder without specifying a user account in
Edgecross Basic Software
The following shows the setting procedure for using a remote shared folder without specifying a user account in EdgecrossBasic Software.

Setting a shared folder
The following shows the procedure for setting a shared folder.
Note that this setting is not recommended because users, who can access a personal computer on which a shared folder ispublished, can access the shared folder without any restrictions.
Create a folder to publish as a shared folder in an industrial PC on which Edgecross Basic Software is installed, and configure
the sharing settings.
Permissions must be granted for Everyone and ANONYMOUS LOGON of Windows to a shared folder. If there are security
concerns, enable Windows Firewall to restrict access.
The following shows a setting example for Windows 10.
For other operating systems, refer to the manual or online help for an operating system used.

1. Click the [Advanced Sharing] button in the [Sharing] tabin the properties of a folder.

2. Select the checkbox of "Share this folder."3. Set a share name.
4. Click the [Permissions] button.

556

APPX
Appendix 6 Using a Remote Shared Folder

5. Click the [Add] button.

6. Enter 'ANONYMOUS LOGON' in "Enter the object
names to select."

7. Click the [OK] button.

8. Select the checkboxes of "Change" and "Read" for thepermissions for ANONYMOUS LOGON and Everyone.

9. Click the [OK] button.

APPX
Appendix 6 Using a Remote Shared Folder

A

557

10. Click the [Edit] button in the [Security] tab in theproperties of the folder.

11. Click the [Add] button.

12. Add 'ANONYMOUS LOGON' and 'Everyone' as in steps
6 and 7.

558

APPX
Appendix 6 Using a Remote Shared Folder

13. Select the checkboxes of "Modify" and "Read" for thepermissions for ANONYMOUS LOGON and Everyone.

14. Click the [OK] button.
15. Close the properties of the folder.

16. Start the local security policy of Windows.
17. Select [Security Settings]  [Local Policies]  [Security
Options].

18. Set the following items:

A
Item name

Setting

Network access: Let Everyone permissions apply to anonymous users

Enabled(Default: Disabled)

Network access: Shares that can be accessed anonymously

Add a shared folder name.

Network access: Restrict anonymous access to Named Pipes and Shares

Disabled(Default: Enabled)

Consideration
Refer to the following:
Page 555 Consideration

APPX
Appendix 6 Using a Remote Shared Folder

559

Appendix 7 Allowing Communication Connections
between Industrial PCs
This section shows the setting methods for allowing communication connections between industrial PCs by using the firewall
function of Windows, 'Windows Defender Firewall'*1.
In communications between an industrial PC on which Edgecross Basic Software is installed and another one,
communication connections may fail if a firewall is enabled.
*1'Windows Firewall' for some Windows versions

Precautions• Security measures such as firewalls may be taken by other security measure software or devices in some operating
environments. In this case, take measures to allow communication connections according to an operating environment.
• This section shows only the minimum required settings. By using the firewall function, allowing communication connections
can be set more strictly, such as allowing connections from specific computers only. To maintain system security, it isrecommended to configure the setting as strict as possible.

Cases and settings
The following shows the cases in which communication connections must be allowed and settings for allowing them.

Precautions
Even when adding a rule for allowing communication connections to 'Windows Defender Firewall,' communication
connections may be denied by another rule that is already set. In this case, perform either of the following:• Review the rule condition that denies the communication connections so that they are enabled under the added rulecondition.
• Review the Edgecross Basic Software setting so that the communication connections can be established under a condition
where they are not denied.
Ex.

When adding a rule for allowing communication connections with a port number specified in the OPC UA setting for OPC UA
connection with Management Shell but they cannot be established due to another rule that denies them with the same port
number, perform either of the following:• Change the rule condition that denies the communication connections so that the port number used for them is not denied.
• Change the port number set for the OPC UA connection with Management Shell so that the communication connections
can be established with another port number.

Real-time Flow Manager
The following shows the case in which communication connections must be allowed and settings for allowing them for Realtime Flow Manager.

Case in which communication connections must be allowed
For the following functions, when cooperating with an edge application on an industrial PC other than one on which
Edgecross Basic Software is installed via an MQTT broker, it is required to set communication connections to the MQTT
broker to be allowed.
• Edge application cooperation function (MQTT cooperation) (Page 43 MQTT cooperation)• Data distribution function (Page 80 Data Distribution Function)

Precautions
When using Eclipse Mosquitto as an MQTT broker, it is also required to change the settings for Eclipse Mosquitto.
Refer to the following to change the settings.
Page 528 Configuring the settings for connection from another industrial PC
For MQTT brokers other than Eclipse Mosquitto, their own settings may also be required.
For the necessary settings, refer to the manual, etc. for an MQTT broker used.

560

APPX
Appendix 7 Allowing Communication Connections between Industrial PCs

Settings for allowing communication connections• Setting targets
Add an inbound rule with specifying a program (MQTT broker) and port number that allow communication connections to thefirewall of an industrial PC on which a connected MQTT broker is running.
Ex.

For MQTT cooperation by connecting to an MQTT broker running on an industrial PC on which Edgecross Basic Software is
installed(1)
Edge application(a)(2)
Windows Defender
Firewall(b)

MQTT broker(a)Real-time Flow Manager(1) Industrial PC on which an edge application is installed(2) Industrial PC on which Edgecross Basic Software is installed(a) Connect to an MQTT broker in (2).
(b) Add an inbound rule for the firewall.

A

Ex.

For MQTT cooperation by connecting to an MQTT broker running on an industrial PC other than one on which EdgecrossBasic Software is installed(1)
Edge application(a)
MQTT broker

Windows Defender
Firewall

(b)

(a)
(2)

Real-time Flow Manager(1) Industrial PC on which an edge application is installed(2) Industrial PC on which Edgecross Basic Software is installed(a) Connect to an MQTT broker in (1).
(b) Add an inbound rule for the firewall.

APPX
Appendix 7 Allowing Communication Connections between Industrial PCs

561

• Setting example
The following shows a setting example in Windows Defender Firewall.
Add the following rule to the inbound rule.
Item

Description

Rule Type

Select "Custom."

Program

Select "This program path" and enter the path to an MQTT broker.
When using Eclipse Mosquitto as an MQTT broker, enter the path as follows:• (Arbitrary storage destination)\mosquitto\mosquitto.exe
Do not specify a service to which this rule applies.

Protocol and Ports

Scope

Protocol type

Select "TCP."

Protocol number

A default fixed value

Local port

Select "Specific Ports" and enter the port number (default is 1883) to connect
to an MQTT broker.

Remote port

Set this as necessary.
When not specifying a port used for OPC UA connection in an edge
application, select "All Ports."
Otherwise, select "Specific Ports" and enter the port number.

Internet Control Message Protocol(ICMP) settings

Not required.

Local IP address

Set these as necessary.
When not specifying the IP address of a personal computer on the edge
application side, select "Any IP address."
Otherwise, select "These IP addresses," and enter the IP address in the "IP
Address" screen displayed by clicking the [Add...] button.

Remote IP address

ActionSelect "Allow the connection."

ProfileSelect any of the items according to the network environment for the industrial
PC.

Name

Enter any name.

The above items and setting methods are for adding a setting in the "New Inbound Rule Wizard" screen.

562

APPX
Appendix 7 Allowing Communication Connections between Industrial PCs

Management Shell
The following shows the case in which communication connections must be allowed and settings for allowing them forManagement Shell.

Case in which communication connections must be allowed
When connecting to Management Shell, which is an OPC UA server, from an edge application on an industrial PC other than
one on which Edgecross Basic Software is installed, it is required to set communication connections to Management Shell tobe allowed.

Settings for allowing communication connections• Setting targets
Add an inbound rule with specifying a program (Management Shell) and port number that allow communication connections
to the firewall on the industrial PC side on which Edgecross Basic Software is installed.
(1)
Edge application(a)(2)
Windows Defender
Firewall(b)

Management Shell(1) Industrial PC on which an edge application is installed(2) Industrial PC on which Edgecross Basic Software is installed(a) Establish an OPC UA connection to Management Shell in (2).
(b) Add an inbound rule for the firewall.

A

APPX
Appendix 7 Allowing Communication Connections between Industrial PCs

563

• Setting example
The following shows a setting example in Windows Defender Firewall.
Add the following rule to the inbound rule.
Item

Description

Rule Type

Select "Custom."

Program

Select "This program path" and enter the path to Management Shell.
For the default installation path, enter the following path:• C:\Edgecross\Edgecross Basic Software\Management
Shell\Service\bin\EcMsService.exe
Do not specify a service to which this rule applies.

Protocol and Ports

Scope

Protocol type

Select "TCP."

Protocol number

A default fixed value

Local port

Select "Specific Ports" and enter the port number (default is 48010) specified
in the OPC UA setting for Management Shell.

Remote port

Set this as necessary.
When not specifying a port used for OPC UA connection in an edge
application, select "All Ports."
Otherwise, select "Specific Ports" and enter the port number.

Internet Control Message Protocol(ICMP) settings

Not required.

Local IP address

Set these as necessary.
When not specifying the IP address of a personal computer on the edge
application side, select "Any IP address."
Otherwise, select "These IP addresses," and enter the IP address in the "IP
Address" screen displayed by clicking the [Add...] button.

Remote IP address

ActionSelect "Allow the connection."

ProfileSelect any of the items according to the network environment for the industrial
PC.

Name

Enter any name.

The above items and setting methods are for adding a setting in the "New Inbound Rule Wizard" screen.

564

APPX
Appendix 7 Allowing Communication Connections between Industrial PCs

Procedure for adding a rule for Windows Defender Firewall
The following shows the procedure for adding a rule for Windows Defender Firewall.

Operating procedure

1. Open the "Windows Defender Firewall" screen.
Search for "Windows Defender Firewall"*1 in the search box of Windows.
*1'Windows Firewall' for some Windows versions

2. Open the "Windows Defender Firewall with Advanced Security" screen.
Click [Advanced settings] in the "Windows Defender Firewall" screen.

A

3. Open the "New Inbound Rule Wizard" screen.
Click [Inbound Rules] in the "Windows Defender Firewall with Advanced Security" screen.
Then, click [New Rule...] under "Actions" on the right of the screen.

APPX
Appendix 7 Allowing Communication Connections between Industrial PCs

565

4. Set a rule for allowing communication connections.
Follow the display contents in the "New Inbound Rule Wizard" screen and refer to the setting examples in the following to set
each item.
Then, click the [Finish] button on the last page of the wizard screen.
• For Real-time Flow Manager: Page 561 Settings for allowing communication connections• For Management Shell: Page 563 Settings for allowing communication connections

This setting is added to the list with the name entered for "Inbound Rules" in the "Windows Defender Firewallwith Advanced Security" screen, and its contents can be changed by selecting it from the list.

566

APPX
Appendix 7 Allowing Communication Connections between Industrial PCs

Appendix 8 Processing Performance and Processing
TimeThis section shows the processing performance and processing time of Real-time Flow Manager and Management Shell.
The performance specifications described in this section are measured in the following operating environment.

Real-time Flow Manager
The following shows the processing performance and processing time of Real-time Flow Manager.

Operating environment 1
Item

Description

MPU

Intel Core i3Memory8 GB

Storage

64 GB

OSWindows 10 (IoT Enterprise)

Operating environment 2
Item

Description

MPU

Intel Atom

Memory4 GB

Storage

60 GB

OSWindows 10 (IoT Enterprise)

Operating environment 3
Item

Description

MPU

Intel Atom

Memory4 GB

Storage

60 GB

OSWindows 10 (IoT Enterprise)A

Operating environment 4
Item

Description

MPU

Intel Core i7

Memory16 GB

Storage

64 GB

OSWindows 10 (IoT Enterprise)

Operating environment 5
Item

Description

MPU

12th generation Intel Core i7

Memory16 GB

Storage

512 GB (free space: 64 GB or more)OS

Windows 11 Pro

Precautions
The processing time of Real-time Flow Manager may vary due to interruption of processing of other software and Windows.

APPX
Appendix 8 Processing Performance and Processing Time567

Processing performance of a process flow
The following shows the performance with which a process data buffer overflow error does not occur in a data logging flow
and data diagnosis flow.

Data logging flow
The following shows the number of collections and collection cycle with which a process data buffer overflow error does notoccur in a data logging flow.
• Parameter setting value
Parameter type

Setting item

Real-time Flow Manager
parameter

Data collection

File saving*1

Setting content
Data collector used

Data collector distributed by the Edgecross Consortium*1

Number of units of collection
data

Refer to each 'Number of units of collection data per process flow.'

Data typeUINT typeCollection cycle

Measured from 1 ms.

File format

CSV file (UTF-8)

Output data

All collection data

Number of record rows forswitching1000 rows

Maximum number of files to be
saved

100 files

Contact the Edgecross Consortium to obtain it.

• Processing performance
For 1 process flow setting
Number of units of collection
data

Number of units of collection
data per process flow

Cycle
specification (ms)(Operating
environment 1)

Cycle
specification (ms)(Operating
environment 2)

Cycle
specification (ms)(Operating
environment 5)

32

32

1

2

1

64

64

1

2

1

128

128

1

3

1

256

256

1

3

1

Number of units of collection
data

Number of units of collection
data per process flow

Cycle
specification (ms)(Operating
environment 1)

Cycle
specification (ms)(Operating
environment 2)

Cycle
specification (ms)(Operating
environment 5)

32

4

2

8

2

64

8

2

8

2

128

16

2

9

2

256

32

3

9

2

512

64

3

10

2

1024

128

3

12

3

2048

256

3

16

3

Number of units of collection
data

Number of units of collection
data per process flow

Cycle
specification (ms)(Operating
environment 1)

Cycle
specification (ms)(Operating
environment 2)

Cycle
specification (ms)(Operating
environment 5)

1024

64

3

*1

3

2048

128

3

*1

3

4096

256

3

*1

3

For 8 process flow settings

For 16 process flow settings

*1

568

Cannot be measured due to an error.

APPX
Appendix 8 Processing Performance and Processing TimeFor 32 process flow settings
Number of units of collection
data

Number of units of collection
data per process flow

Cycle
specification (ms)(Operating
environment 1)

Cycle
specification (ms)(Operating
environment 2)

Cycle
specification (ms)(Operating
environment 5)

2048

64

4

*1

3

4096

128

4

*1

3

8192

256

4

*1

3

*1

Cannot be measured due to an error.

A

APPX
Appendix 8 Processing Performance and Processing Time

569

Data diagnosis flow
The following shows the number of units of collection data and collection cycle that do not cause any process data buffer
overflow error in a data diagnosis flow.
• Parameter setting value
Parameter type

Setting item

Real-time Flow Manager
parameter

Data collection

File saving(data collection)

Data diagnosis

Feedback*1

Setting content
Data collector used

Data collector distributed by the Edgecross Consortium*1

Number of units of collection
data

Refer to each 'Number of units of collection data per process flow.'

Data typeUINT typeCollection cycle

Measured from 1 ms.

File format

CSV file (UTF-8)

Output data

All collection data

Number of record rows forswitching1000 rows

Maximum number of files to be
saved

100 files

Edge application used

Application distributed by the Edgecross Consortium*1

Input data

All collection data

Output data

Same data as all input data

Execution condition

Not setExecution frequency

Deterrence period: 1 minuteFeedback type

Device instruction feedback

Data collector used

Same as data collection

Setting value for data for
feedbackSpecify all output data of data diagnosis within the range of the numberof units of data available for feedback (32  4 = 128).

Timeout time

10 seconds

Contact the Edgecross Consortium to obtain it.

• Processing performance
For 1 process flow setting
Number of units of collection
data

Number of units of collection
data per process flow

Cycle
specification (ms)(Operating
environment 1)

Cycle
specification (ms)(Operating
environment 2)

Cycle
specification (ms)(Operating
environment 5)

256

256

2

40

2

Number of units of collection
data

Number of units of collection
data per process flow

Cycle
specification (ms)(Operating
environment 1)

Cycle
specification (ms)(Operating
environment 2)

Cycle
specification (ms)(Operating
environment 5)

512

128

3

50

2

1024

256

4

60

2

Number of units of collection
data

Number of units of collection
data per process flow

Cycle
specification (ms)(Operating
environment 1)

Cycle
specification (ms)(Operating
environment 2)

Cycle
specification (ms)(Operating
environment 5)

2048

128

*1

*1

2

4096

256

*1

*1

2

For 4 process flow settings

For 16 process flow settings

*1

570

Cannot be measured due to an error.

APPX
Appendix 8 Processing Performance and Processing TimeFor 32 process flow settings
Number of units of collection
data

Number of units of collection
data per process flow

Cycle
specification (ms)(Operating
environment 1)

Cycle
specification (ms)(Operating
environment 2)

Cycle
specification (ms)(Operating
environment 5)

4096

128

*1

*1

3

256

*1

*1

3

8192

*1



Cannot be measured due to an error.

A

APPX
Appendix 8 Processing Performance and Processing Time

571

Using data logging flows and data diagnosis flows in combination
The following shows the number of units of collection data and the collection cycle that do not cause any process data buffer
overflow error when using data logging flows and data diagnosis flows in combination.
• Parameter setting value
Parameter type

Setting item

Real-time Flow Manager
parameter

Data Logging Flow

Setting content
Number of settings
Data collection

File saving(data collection)

Data Diagnosis
Flow

Data collector used

Data collector distributed by the EdgecrossConsortium*1

Number of units of collection
data

Refer to each 'Number of units of collection data
per process flow.'

Data typeUINT typeCollection cycle

Measured from 1 ms.

File format

CSV file (UTF-8)

Output data

All collection data

Number of record rows forswitching1000 rows

Maximum number of files to be
saved

100 files

Data modification 1
to 3(data extraction)

Input data

All collection data

File saving(data modification
3)

Same as items for file saving (data collection) listed above

Output data

All input data

Condition setting

Condition to be necessarily satisfied  4 (ANDcombination)

Number of settings

4 flows

Data collection

Same as data collection in data logging flow

File saving(data collection)

Same as file saving (data collection) in data logging flow

Data diagnosis

Edge application used

Edge application distributed by the EdgecrossConsortium*1

Input data

All output data of data modification

Output data

Same data as input data

File saving(data diagnosis)
Feedback*1

8 flows

Same as file saving (data collection) in data logging flow
Execution condition

Not setExecution frequency

Deterrence period: 1 minuteFeedback type

Device instruction feedback

Data collector used

Same as data collection

Setting value for data for
feedbackSpecify all output data of data diagnosis within therange of the number of units of data available for
feedback (32  4 = 128).

Timeout time

10 seconds

Contact the Edgecross Consortium to obtain it.

• Processing performance
Number of units of collection
data

Number of units of collection
data per process flow

Cycle
specification (ms)(Operating
environment 1)

Cycle
specification (ms)(Operating
environment 2)

Cycle
specification (ms)(Operating
environment 5)

3072

256

40

300

2

572

APPX
Appendix 8 Processing Performance and Processing TimeCPU usage rate and memory usage amount while a process flow is running
To run Edgecross Basic Software stably, it is recommended to set each process flow so that the CPU and memory usage
rates of the entire industrial PC are limited to approximately 60% on average for each.
The following shows the CPU usage rate*1 and memory usage amount while a process flow is running.
*1

An average value obtained by measuring the CPU usage rate of the entire industrial PC, where Edgecross Basic Software, a datacollector, and an edge application are running, for 10 minutes.

CPU usage rate and memory usage amount for each number of units of collection data whenusing one data logging flow only
• Parameter setting value
Parameter type

Setting item

Real-time Flow Manager
parameter

Data collection

Data modification

File saving(data modification)*1

Setting content
Data collector used

Data collector distributed by the Edgecross Consortium*1

Number of units of collection
data

Refer to each 'Number of units of collection data.'

Data type• UINT type
• WSTRING typeCollection cycle

Refer to each 'Collection cycle.'

Function type

Data extraction

Input data

All collection data

Output data

All input data

Condition setting

Condition to be necessarily satisfied  4 (AND combination)

File format

CSV file (UTF-8)

Output data

All collection data

Number of record rows forswitching1000 rows

Maximum number of files to be
saved

100 files

Contact the Edgecross Consortium to obtain it.

A

APPX
Appendix 8 Processing Performance and Processing Time573

• CPU usage rate
The data type of collection data is UINT (operating environment 1)
Number of units ofcollection data

Number of
executed flows

CPU usage rate [%]Collection cycle: 10 ms

Collection cycle: 100 ms

Collection cycle: 1000 ms

16

1

5

5

5

64

1

5

5

5

256

1

5

5

5

The data type of collection data is WSTRING (operating environment 1)
Number of units ofcollection data

Number of
executed flows

CPU usage rate [%]Collection cycle: 10 ms

Collection cycle: 100 ms

Collection cycle: 1000 ms

16

1

5

5

5

64

1

5

5

5

256

1

5

5

5

The data type of collection data is UINT (operating environment 2)
Number of units ofcollection data

Number of
executed flows

CPU usage rate [%]Collection cycle: 10 ms

Collection cycle: 100 ms

Collection cycle: 1000 ms

16

1

30

25

25

64

1

35

25

25

256

1

40

30

30

The data type of collection data is WSTRING (operating environment 2)
Number of units ofcollection data

Number of
executed flows

CPU usage rate [%]Collection cycle: 10 ms

Collection cycle: 100 ms

Collection cycle: 1000 ms

16

1

30

25

25

64

1

40

25

25

256

1

80

30

30

The data type of collection data is UINT (operating environment 5)
Number of units ofcollection data

Number of
executed flows

CPU usage rate [%]Collection cycle: 10 ms

Collection cycle: 100 ms

Collection cycle: 1000 ms

16

1

15

15

15

64

1

15

15

15

256

1

15

15

15

The data type of collection data is WSTRING (operating environment 5)
Number of units ofcollection data

Number of
executed flows

CPU usage rate [%]Collection cycle: 10 ms

Collection cycle: 100 ms

Collection cycle: 1000 ms

16

1

15

15

15

64

1

15

15

15

256

1

15

15

15

574

APPX
Appendix 8 Processing Performance and Processing Time• Memory usage amountThe data type of collection data is UINT (operating environment 1)
Number of units ofcollection data

Number of
executed flows

Memory usage amount [MB]Collection cycle: 10 ms

Collection cycle: 100 ms

Collection cycle: 1000 ms

16

1

3000

3000

3000

64

1

3000

3000

3000

256

1

3000

3000

3000

The data type of collection data is WSTRING (operating environment 1)
Number of units ofcollection data

Number of
executed flows

Memory usage amount [MB]Collection cycle: 10 ms

Collection cycle: 100 ms

Collection cycle: 1000 ms

16

1

3000

3000

3000

64

1

3000

3000

3000

256

1

3000

3000

3000

The data type of collection data is UINT (operating environment 2)
Number of units ofcollection data

Number of
executed flows

Memory usage amount [MB]Collection cycle: 10 ms

Collection cycle: 100 ms

Collection cycle: 1000 ms

16

1

3000

3000

3000

64

1

3000

3000

3000

256

1

3000

3000

3000

The data type of collection data is WSTRING (operating environment 2)
Number of units ofcollection data

Number of
executed flows

Memory usage amount [MB]Collection cycle: 10 ms

Collection cycle: 100 ms

Collection cycle: 1000 ms

16

1

3000

3000

3000

64

1

3000

3000

3000

256

1

3000

3000

3000

A

The data type of collection data is UINT (operating environment 5)
Number of units ofcollection data

Number of
executed flows

Memory usage amount [MB]Collection cycle: 10 ms

Collection cycle: 100 ms

Collection cycle: 1000 ms

16

1

6000

6000

6000

64

1

6000

6000

6000

256

1

6000

6000

6000

The data type of collection data is WSTRING (operating environment 5)
Number of units ofcollection data

Number of
executed flows

Memory usage amount [MB]Collection cycle: 10 ms

Collection cycle: 100 ms

Collection cycle: 1000 ms

16

1

6000

6000

6000

64

1

6000

6000

6000

256

1

6000

6000

6000

APPX
Appendix 8 Processing Performance and Processing Time

575

CPU usage rate and memory usage amount for each number of units of collection data whenusing one data diagnosis flow only
• Parameter setting value
Parameter type

Setting item

Real-time Flow Manager
parameter

Data collection

Data modification

Data diagnosis

File saving(data diagnosis)

Feedback*1

576

Setting content
Data collector used

Data collector distributed by the Edgecross Consortium*1

Number of units of collection
data

Refer to each 'Number of units of collection data.'

Data type• UINT type
• WSTRING typeCollection cycle

Refer to each 'Collection cycle.'

Function type

Data extraction

Input data

All collection data

Output data

All input data

Condition setting

Condition to be necessarily satisfied  4 (AND combination)

Edge application used

Edge application distributed by the Edgecross Consortium*1

Input data

All output data of data modification

Output data

Same data as input data

File format

CSV file (UTF-8)

Output data

All output data of data diagnosis

Number of record rows forswitching1000 rows

Maximum number of files to be
saved

100 files

Execution condition

Not setExecution frequency

Deterrence period: 1 minuteFeedback type

Device instruction feedback

Data collector used

Same as data collection

Setting value for data for
feedbackSpecify all output data of data diagnosis within the range of the numberof units of data available for feedback (32  4 = 128).

Timeout time

10 seconds

Contact the Edgecross Consortium to obtain it.

APPX
Appendix 8 Processing Performance and Processing Time• CPU usage rate
The data type of collection data is UINT (operating environment 1)
Number of units ofcollection data

Number of
executed flows

CPU usage rate [%]Collection cycle: 10 ms

Collection cycle: 100 ms

Collection cycle: 1000 ms

16

1

5

2

2

64

1

5

3

3

256

1

10

5

5

The data type of collection data is WSTRING (operating environment 1)
Number of units ofcollection data

Number of
executed flows

CPU usage rate [%]Collection cycle: 10 ms

Collection cycle: 100 ms

Collection cycle: 1000 ms

16

1

5

2

2

64

1

10

3

3

256

1

20

5

5

The data type of collection data is UINT (operating environment 2)
Number of units ofcollection data

Number of
executed flows

CPU usage rate [%]Collection cycle: 10 ms

Collection cycle: 100 ms

Collection cycle: 1000 ms

16

1

30

20

20

64

1

35

20

20

256

1

40

30

30

The data type of collection data is WSTRING (operating environment 2)
Number of units ofcollection data

Number of
executed flows

CPU usage rate [%]Collection cycle: 10 ms

Collection cycle: 100 ms

Collection cycle: 1000 ms

16

1

30

20

20

64

1

40

30

30

256

1

80

30

30

A

The data type of collection data is UINT (operating environment 5)
Number of units ofcollection data

Number of
executed flows

CPU usage rate [%]Collection cycle: 10 ms

Collection cycle: 100 ms

Collection cycle: 1000 ms

16

1

10

10

10

64

1

10

10

10

256

1

10

10

10

The data type of collection data is WSTRING (operating environment 5)
Number of units ofcollection data

Number of
executed flows

CPU usage rate [%]Collection cycle: 10 ms

Collection cycle: 100 ms

Collection cycle: 1000 ms

16

1

10

10

10

64

1

10

10

10

256

1

10

10

10

APPX
Appendix 8 Processing Performance and Processing Time

577

• Memory usage amountThe data type of collection data is UINT (operating environment 1)
Number of units ofcollection data

Number of
executed flows

Memory usage amount [MB]Collection cycle: 10 ms

Collection cycle: 100 ms

Collection cycle: 1000 ms

16

1

3000

3000

3000

64

1

3000

3000

3000

256

1

3000

3000

3000

The data type of collection data is WSTRING (operating environment 1)
Number of units ofcollection data

Number of
executed flows

Memory usage amount [MB]Collection cycle: 10 ms

Collection cycle: 100 ms

Collection cycle: 1000 ms

16

1

3000

3000

3000

64

1

3000

3000

3000

256

1

3000

3000

3000

The data type of collection data is UINT (operating environment 2)
Number of units ofcollection data

Number of
executed flows

Memory usage amount [MB]Collection cycle: 10 ms

Collection cycle: 100 ms

Collection cycle: 1000 ms

16

1

3000

3000

3000

64

1

3000

3000

3000

256

1

3000

3000

3000

The data type of collection data is WSTRING (operating environment 2)
Number of units ofcollection data

Number of
executed flows

Memory usage amount [MB]Collection cycle: 10 ms

Collection cycle: 100 ms

Collection cycle: 1000 ms

16

1

3000

3000

3000

64

1

3000

3000

3000

256

1

3000

3000

3000

The data type of collection data is UINT (operating environment 5)
Number of units ofcollection data

Number of
executed flows

Memory usage amount [MB]Collection cycle: 10 ms

Collection cycle: 100 ms

Collection cycle: 1000 ms

16

1

6000

6000

6000

64

1

6000

6000

6000

256

1

6000

6000

6000

The data type of collection data is WSTRING (operating environment 5)
Number of units ofcollection data

Number of
executed flows

Memory usage amount [MB]Collection cycle: 10 ms

Collection cycle: 100 ms

Collection cycle: 1000 ms

16

1

6000

6000

6000

64

1

6000

6000

6000

256

1

6000

6000

6000

578

APPX
Appendix 8 Processing Performance and Processing TimeCPU usage rate and memory usage amount for each number of data logging flows when the
total number of units of collection data is fixed• Parameter setting value
Parameter type

Setting item

Real-time Flow Manager
parameter

Data collection

Data modification

File saving(data modification)*1

Setting content
Data collector used

Data collector distributed by the Edgecross Consortium*1

Number of units of collection
data

Refer to each 'Number of units of collection data per flow.'

Data typeUINT typeCollection cycle

Refer to each 'Collection cycle.'

Function type

Data extraction

Input data

All collection data

Output data

All input data

Condition setting

Condition to be necessarily satisfied  4 (AND combination)

File format

CSV file (UTF-8)

Output data

All collection data

Number of record rows forswitching1000 rows

Maximum number of files to be
saved

100 files

Contact the Edgecross Consortium to obtain it.

• CPU usage rate
Number of executedflows

CPU usage rate [%]Operating environment
1 (collection cycle: 10
ms)Operating environment
2 (collection cycle: 10
ms)Operating environment
5 (collection cycle: 10
ms)Number of units ofcollection data per flow

1

5

30

10

256

4

15

40

10

64

8

15

*1

10

32

16

15

*1



10

16

32

15

*1

10

8

*1

A

Cannot be measured due to an error.

• Memory usage amount
Number of executed
flows

Memory usage amount [MB]Operating environment
1 (collection cycle: 10
ms)Operating environment
2 (collection cycle: 10
ms)Operating environment
5 (collection cycle: 10
ms)

1

3000

3000

6000

256

4

3400

3400

6400

64

8

3800

*1

6800

32

16

4400

*1



7400

16

32

6200

*1

9200

8

*1

Number of units ofcollection data per flow

Cannot be measured due to an error.

APPX
Appendix 8 Processing Performance and Processing Time

579

CPU usage rate and memory usage amount for each number of data diagnosis flows when the
total number of units of collection data is fixed• Parameter setting value
Parameter type

Setting item

Real-time Flow Manager
parameter

Data collection

Data modification

Data diagnosis

File saving(data diagnosis)

Feedback*1

Setting content
Data collector used

Data collector distributed by the Edgecross Consortium*1

Number of units of collection
data

Refer to each 'Number of units of collection data.'

Data typeUINT typeCollection cycle

Refer to each 'Collection cycle.'

Function type

Data extraction

Input data

All collection data

Output data

All input data

Condition setting

Mandatory condition  4 (AND combination)

Edge application used

Edge application distributed by the Edgecross Consortium*1

Input data

All output data of data modification

Output data

Same data as input data

File format

CSV file (UTF-8)

Output data

All output data of data diagnosis

Number of record rows forswitching1000 rows

Maximum number of files to be
saved

100 files

Execution condition

Not setExecution frequency

Deterrence period: 1 minuteFeedback type

Device instruction feedback

Data collector used

Same as data collection

Setting value for data for
feedbackSpecify all output data of data diagnosis within the range of the numberof units of data available for feedback (32  4 = 128).

Timeout time

10 seconds

Contact the Edgecross Consortium to obtain it.

• CPU usage rate
Number of executedflows

CPU usage rate [%](Operating environment1) (Collection cycle: 100
ms)(Operating environment2) (Collection cycle: 100
ms)(Operating environment5) (Collection cycle: 100
ms)

Number of units ofcollection data per flow

1

5

15

10

256

4

5

15

10

64

8

5

*1

10

32

16

10

*1



10

16

32

15

*1

10

8

*1

Cannot be measured due to an error.

• Memory usage amount
Number of executed
flows

Memory usage amount [MB](Operating environment1) (Collection cycle: 100
ms)(Operating environment2) (Collection cycle: 100
ms)(Operating environment5) (Collection cycle: 100
ms)

1

3000

3000

6000

256

4

3500

3500

6500

64

8

4000

*1

7000

32

16

4900

*1

7900

16

32

6500

*1

9500

8

*1

580

Cannot be measured due to an error.

APPX
Appendix 8 Processing Performance and Processing Time

Number of units ofcollection data per flowCPU usage rate and memory usage amount for each number of data logging flows when thenumber of units of collection data per flow is fixed• Parameter setting value
Parameter type

Setting item

Real-time Flow Manager
parameter

Data collection

Data modification

File saving(data modification)*1

Setting content
Data collector used

Data collector distributed by the Edgecross Consortium*1

Number of units of collection
data

256

Data type• UINT type
• WSTRING typeCollection cycle

Refer to each 'Collection cycle.'

Function type

Data extraction

Input data

All collection data

Output data

All input data

Condition setting

Condition to be necessarily satisfied  4 (AND combination)

File format

CSV file (UTF-8)

Output data

All collection data

Number of record rows forswitching1000 rows

Maximum number of files to be
saved

100 files

Contact the Edgecross Consortium to obtain it.

• CPU usage rate
The data type of collection data is UINT
Number of executedflows

CPU usage rate [%]Operating environment
1 (collection cycle: 10
ms)Operating environment
2 (collection cycle: 10
ms)Operating environment
5 (collection cycle: 10
ms)Number of datacollection points
256 points  Number of
flows

1

5

20

10

256

4

5

30

10

1024

8

5

*1

10

2048

16

5

*1



10

4096

32

10

*1

10

8192

Operating environment
5 (collection cycle: 10
ms)Number of datacollection points
256 points  Number of
flows

*1

A

Cannot be measured due to an error.

The data type of collection data is WSTRING
Number of executedflows

CPU usage rate [%]Operating environment
1 (collection cycle: 10
ms)Operating environment
2 (collection cycle: 10
ms)

1

5

25

10

256

4

5

40

10

1024

8

5

*1

10

2048

16

30

*1



10

4096

32

30

*1

10

8192

*1

Cannot be measured due to an error.

APPX
Appendix 8 Processing Performance and Processing Time

581

• Memory usage amountThe data type of collection data is UINT
Number of executed
flows

Memory usage amount [MB]Number of datacollection points
256 points  Number offlows

Operating environment
1 (collection cycle: 10
ms)Operating environment
2 (collection cycle: 10
ms)Operating environment
5 (collection cycle: 10
ms)

1

3000

3000

6000

256

4

3400

3400

6400

1024

8

3800

*1

6800

2048

16

4600

*1

7600

4096

32

6200

*1

9200

8192

*1

Cannot be measured due to an error.

The data type of collection data is WSTRING
Number of executed
flows

Memory usage amount [MB]Operating environment
1 (collection cycle: 10
ms)Operating environment
2 (collection cycle: 10
ms)Operating environment
5 (collection cycle: 10
ms)

1

3000

3000

6000

256

4

3400

3400

6400

1024

8

3800

*1

6800

2048

16

4600

*1

7600

4096

6200

*1

9200

8192

32

*1

582

Cannot be measured due to an error.

APPX
Appendix 8 Processing Performance and Processing Time

Number of datacollection points
256 points  Number offlowsCPU usage rate and memory usage amount for each number of data diagnosis flows when thenumber of units of collection data per flow is fixed• Parameter setting value
Parameter type

Setting item

Real-time Flow Manager
parameter

Data collection

Data modification

Data diagnosis

File saving(data diagnosis)

Feedback*1

Setting content
Data collector used

Data collector distributed by the Edgecross Consortium*1

Number of units of collection
data

256

Data type• UINT type
• WSTRING typeCollection cycle

Refer to each 'Collection cycle.'

Function type

Data extraction

Input data

All collection data

Output data

All input data

Condition setting

Condition to be necessarily satisfied  4 (AND combination)

Edge application used

Edge application distributed by the Edgecross Consortium*1

Input data

All output data of data modification

Output data

Same number of units of data as input data

File format

CSV file (UTF-8)

Output data

All output data of data diagnosis

Number of record rows forswitching1000 rows

Maximum number of files to be
saved

100 files

Execution condition

Not setExecution frequency

Deterrence period: 1 minuteFeedback type

Device instruction feedback

Data collector used

Same as data collection

Setting value for data for
feedbackSpecify all output data of data diagnosis within the range of the numberof units of data available for feedback (32  4 = 128).

Timeout time

10 seconds

Contact the Edgecross Consortium to obtain it.

• CPU usage rate
The data type of collection data is UINT
Number of executedflows

CPU usage rate [%]Operating environment
1 (collection cycle: 100
ms)

Operating environment
2 (collection cycle: 100
ms)

Operating environment
5 (collection cycle: 100
ms)

Number of datacollection points
256 points  Number of
flows

1

5

15

10

256

*1

4

5



10

1024

8

5

*1

10

2048

16



*1

*1



10

4096

32

*1

*1

10

8192

Operating environment
2 (collection cycle: 100
ms)

Operating environment
5 (collection cycle: 100
ms)

Number of datacollection points
256 points  Number of
flows

*1

Cannot be measured due to an error.

The data type of collection data is WSTRING
Number of executedflows

CPU usage rate [%]Operating environment
1 (collection cycle: 100
ms)

1

5

15

10

256

4

10

*1

10

1024

8

20

*1

10

2048

16

*1

*1

10

4096

32

*1

*1

10

8192

*1

Cannot be measured due to an error.
APPX
Appendix 8 Processing Performance and Processing Time

583

A• Memory usage amountThe data type of collection data is UINT
Number of executed
flows

Memory usage amount [MB]Operating environment
1 (collection cycle: 100
ms)

Operating environment
2 (collection cycle: 100
ms)

Operating environment
5 (collection cycle: 100
ms)

1

3000

3000

6000

256

4

5000

*1

8000

1024

8

6000

*1

9000

2048

16

*1

*1

14000

4096

32

*1

*1

16000

8192

*1

Number of datacollection points
256 points  Number offlows

Cannot be measured due to an error.

The data type of collection data is WSTRING
Number of executed
flows

Memory usage amount [MB]Operating environment
1 (collection cycle: 100
ms)

Operating environment
2 (collection cycle: 100
ms)

Operating environment
5 (collection cycle: 100
ms)

Number of datacollection points
256 points  Number of
flows

1

3000

3000

6000

256

*1

4

5000



8000

1024

8

6000

*1

9000

2048

16

*1

*1

14000

4096

32

*1

*1

16000

8192

*1

584

Cannot be measured due to an error.

APPX
Appendix 8 Processing Performance and Processing Time

DB saving function
The following shows the performance with which a process buffer overflow error does not occur when setting the DB saving in
the data storing function.

Parameter setting value
Parameter type

Setting item

Real-time Flow Manager
parameter

Data collection

Setting content

DB saving*1

Data collector used

Data collector distributed by the Edgecross Consortium*1

Data typeUINT type

Cycle system

Cycle specification

Output data

All collection data

Output name of the date andtime column

TIME

Contact the Edgecross Consortium to obtain it.

Processing performance
Number of units of collection data

Performance value (ms)(Operating environment 1)

Performance value (ms)(Operating environment 2)

16

3

3

32

3

3

64

3

3

128

4

4

256

5

5

Event history automatic output function
The following shows the processing performance of the event history automatic output function.

Parameter setting valueA

Setting item

Setting content

Output target setting

Major, moderate, minor, warning, information

Save destination folder

Any local folder

User account setting

Not setProcessing performance
The following shows the time for each operating environment from the occurrence of a new event to the update of an event
history file when 10000 events are accumulated.
• Operating environment 1: 4 seconds• Operating environment 3: 5 seconds• Operating environment 4: 4 seconds

Precautions
The performance value may vary depending on processing of other functions or software, etc.
If events occur frequently or when using a shared folder as an output destination, it may take longer than the performancevalue.
The time of an event history monitoring interval is included in the performance value.

APPX
Appendix 8 Processing Performance and Processing Time585

Data collection using CSV File Data collector
The following shows the processing performance in data collection using CSV File Data collector.

Parameter setting value
Parameter type

Setting item

Real-time Flow Manager
parameter

Data collection

Data extraction

File saving

Setting content
Monitoring folder

Local path

File name prefix

LOG

Type of collection data

INT type

Input data

All collection data

Output data

All collection data

Condition setting

Conditions that are always true

File format

CSV file

Output data

All collection data

Output name of the date andtime column

TIME

Data row output format

YYYY/MM/DD hh:mm:ss.sss

Saving file path

Local path

File name prefix

LOG

Number of record rows forswitching1000 rows

Maximum number of files to be
saved

100 files

Processing performance
Number of units of collection data

Performance value (ms)(Operating environment 1)

Performance value (ms)(Operating environment 2)

16

2.0

3.0

32

2.0

3.0

64

2.0

3.0

128

2.1

4.0

256

2.3

4.0

586

APPX
Appendix 8 Processing Performance and Processing TimeConsiderations
Effect of error detection frequency on processing performance
If errors are frequently detected, the overall performance of a process flow will be deteriorated and a process data buffer
overflow error may occur even when the current configuration satisfies the processing performance requirements.
In this case, set a deterrence period for feedback to reduce the frequency of feedback.

Effect of other software or Windows processing
Processing of Edgecross Basic Software may be delayed due to interruption of other software or Windows processing.

Effect of switching the operating status
Depending on the setting contents of a process flow and the number of process flows in the RUN states, the load on Windows
increases and an error may occur when switching the operating status of the process flow from STOP to RUN. If an error
occurs, review the collection cycle, number of data collection points, processing contents, and number of process flows in the
RUN states to reduce the load.

Effect of using the DB saving function
Depending on the setting contents of a process flow and the number of process flows in the RUN states, the load on Windows
increases and an error may occur when using the DB saving function. If an error occurs, refer to the following to takecorrective action:
Page 348 Data storing function (DB saving function)

Recommended settings for process flows
To run Edgecross Basic Software stably, set each process flow so that the CPU and memory usage rates of the entire
industrial PC are limited to approximately 60% on average for each. For the CPU usage rate and memory usage amount whilea process flow is running, refer to the following:
Page 573 CPU usage rate and memory usage amount while a process flow is runningA

APPX
Appendix 8 Processing Performance and Processing Time587

Management Shell
The following shows the processing performance and processing time of Management Shell.

Operating environment 1
Item

Description

MPU

Intel Core-i7

Memory16 GB

Storage

64 GB

OSWindows 10 (IoT Enterprise)

Operating environment 2
Item

Description

MPU

Intel Core-i3

Memory8 GB

Storage

64 GB

OSWindows 10 (IoT Enterprise)

Operating environment 3
Item

Description

MPU

Intel Atom

Memory4 GB

Storage

60 GB

OSWindows 10 (IoT Enterprise)

OPC UA connection function
The following shows the processing performance when performing the following operations in an edge application that
supports a data access I/F (technology: OPC UA).
• Reading and writing data in equipment, devices, or lines in production sites via Management Shell• Monitoring data in equipment, devices, or lines in production sites via Management Shell

Reading and writing data in equipment, devices, or lines in production sites via Management
Shell• Parameter setting value
Setting item

Setting content

Number of data tag resources in a data model

256

Data collector used

Data collector distributed by the Edgecross Consortium*1

Data typeUINT type*1

Contact the Edgecross Consortium to obtain it.

• Processing performance (when 256 external data tag resources or internal data tag resources (value) are registered)
Function

Performance value(ms)(Operating
environment 1)

Performance value(ms)(Operating
environment 2)

Performance value(ms)(Operating
environment 3)

Data reading

112

97

157

Data writing

112

97

157

588

APPX
Appendix 8 Processing Performance and Processing Time• Processing performance (when 256 internal data tag resources (operation) are registered)
Function

Hierarchy of acomponent to which
an operation term
(external data tag
resource) belongs

Performance value(ms)(Operating
environment 1)

Performance value(ms)(Operating
environment 2)

Performance value(ms)(Operating
environment 3)

Data reading

20 hierarchies

638

824

3261

A

APPX
Appendix 8 Processing Performance and Processing Time

589

Monitoring data in equipment, devices, or lines in production sites via Management Shell• Parameter setting value
Setting item

Setting content

Access target device setting

1

Data collector used

A data collector with the following performance for the data reading function in each
operating environment• Operating environment 1: 380 ms*1
• Operating environment 2: 400 ms*1
• Operating environment 3: 750 ms*1

Number of connected edge applications

1

Number of subscriptions

1*1

A performance value when the number of data tag resources to be read is '2048'• Processing performance
Sampling cycle (ms)Index value (number of external data tag
resources or internal data tag resources(value)*1)

Index value (number of internal data tag
resources (operation)*2)(Operating
environment
1)(Operating
environment
2)(Operating
environment
3)(Operating
environment
1)(Operating
environment
2)(Operating
environment
3)

100













200













500

3000

2500

1000

1500

1250

500

1000

6000

5000

2000

3000

2500

1000

2000

12000

10000

4000

6000

5000

2000

5000

30000

25000

10000

15000

12500

5000

60000













3600000













*1
*2

590

Number of external data tag resources or internal data tag resources (value) for which data can be monitored periodically without
missing data
Number of internal data tag resources (operation) for which data can be monitored periodically without missing data

APPX
Appendix 8 Processing Performance and Processing Time

One-shot collection function
The following shows the processing performance of the one-shot collection function.
There is a time lag between when a value of a monitoring target resource changes from '0' to '1' and when the one-shotcollection function detects the value change. It is included in the performance value.

File saving• Parameter setting value
Setting item
Collection setting

Setting content
Notification destination of completion

Notify monitoring target

Monitoring target resource

Data type

BOOL type

Resource type

External data tag resource

Data collector used

Data collector distributed by the Edgecross Consortium*1

Data type

INT type

Resource type

External data tag resource

Data collector used

Data collector distributed by the Edgecross Consortium*1

Collection target resource

Saving setting*1

Saving method

File

File format

CSV file

Save destination folder

Local path

File name prefix

LOG

Number of rows for file switching1000 rows

Maximum number of files to be saved

100 files

Contact the Edgecross Consortium to obtain it.

• Processing performance (number of one-shot collection settings: 1)
Number of units of
output data

Performance value (ms)(Operating environment 1)

Performance value (ms)(Operating environment 2)

Performance value (ms)(Operating environment 3)

1

2000

2000

2000

256

3000

3000

3000

1000

3000

3000

4000

A

• Processing performance (number of one-shot collection settings: 12)
The following table shows the times required to complete processing for all one-shot collection settings after changing thevalue of a monitoring target resource for each one-shot collection setting from '0' to '1' at the same time.
Number of units of
output data

Performance value (ms)(Operating environment 1)

Performance value (ms)(Operating environment 2)

Performance value (ms)(Operating environment 3)

1

3000

3000

3000

256

5000

5000

8000

1000

7000

8000

30000

• Processing performance (number of one-shot collection settings: 32)
The following table shows the times required to complete processing for all one-shot collection settings after changing thevalue of a monitoring target resource for each one-shot collection setting from '0' to '1' at the same time.
Number of units of
output data

Performance value (ms)(Operating environment 1)

Performance value (ms)(Operating environment 2)

Performance value (ms)(Operating environment 3)

1

4000

4000

4000

256

6000

7000

11000

1000

12000

14000

33000

The time required for file output when the number of rows for file switching is reached is also included.

APPX
Appendix 8 Processing Performance and Processing Time

591

DB saving• Parameter setting value
Setting item
Collection setting

Setting content
Notification destination of completion

Notify monitoring target

Monitoring target resource

Data type

BOOL type

Resource type

External data tag resource

Data collector used

Data collector distributed by the Edgecross Consortium*1

Collection target resource

Saving setting*1

Data type

INT type

Resource type

External data tag resource

Data collector used

Data collector distributed by the Edgecross Consortium*1

Saving method

DB

DB connection setting

Any connectable setting

Access table setting

Any name

Contact the Edgecross Consortium to obtain it.

• Processing performance (number of one-shot collection settings: 1)
Number of units of
output data

Performance value (ms)(Operating environment 1)

Performance value (ms)(Operating environment 2)

Performance value (ms)(Operating environment 3)

1

2000

3000

3000

256

3000

3000

3000

1000

3000

4000

6000

• Processing performance (number of one-shot collection settings: 12)
The following table shows the times required to complete processing for all one-shot collection settings after changing thevalue of a monitoring target resource for each one-shot collection setting from '0' to '1' at the same time.
Number of units of
output data

Performance value (ms)(Operating environment 1)

Performance value (ms)(Operating environment 2)

Performance value (ms)(Operating environment 3)

1

4000

4000

8000

256

4000

5000

17000

1000

7000

9000

20000

• Processing performance (number of one-shot collection settings: 32)
The following table shows the times required to complete processing for all one-shot collection settings after changing thevalue of a monitoring target resource for each one-shot collection setting from '0' to '1' at the same time.
Number of units of
output data

Performance value (ms)(Operating environment 1)

Performance value (ms)(Operating environment 2)

Performance value (ms)(Operating environment 3)

1

4000

4000

8000

256

7000

8000

22000

1000

12000

16000

62000

592

APPX
Appendix 8 Processing Performance and Processing Time

Event history automatic output function
The following shows the processing performance of the event history automatic output function.

Parameter setting value
Setting item

Setting content

Output target setting

Major, moderate, minor, warning, information

Save destination folder

Any local folder

User account setting

Not setProcessing performance
The following shows the time for each operating environment from the occurrence of a new event to the update of an event
history file when 10000 events are accumulated.
• Operating environment 1: 4 seconds• Operating environment 2: 4 seconds• Operating environment 3: 5 seconds

Precautions
The performance value may vary depending on processing of other functions or software, etc.
If events occur frequently or when using a shared folder as an output destination, it may take longer than the performancevalue.
The time of an event history monitoring interval is included in the performance value.

A

APPX
Appendix 8 Processing Performance and Processing Time593

Data reading using CSV File Data collector
The following shows the processing performance in data reading using CSV File Data collector.

Parameter setting value
Setting item

Setting content

Number of data tag resources registered for each component*1

512 items

Data type

INT type

Monitoring folder

Local folder

File to be read*2*1*2

File type

CSV file

Number of data rows

1000 rows

Number of columns

512 columns

The following items differ depending on a component.
Access target device registered in a data tag resource
Monitoring folder
File name prefix
Updated to a new file in a cycle shorter than a sampling cycle.

Processing performance
Number ofmonitored
data points

Sampling
cycle (ms)Number of CSVFile Data
collectors used

Operating environment
1

Operating environment 2

Operating environment
3

Performan
ce value(ms)

CPU usage
rate (%)

Performanc
e value(ms)

CPU usage
rate (%)

Performan
ce value(ms)

CPU usage
rate (%)

256

500

1

234

38

275

25

819

57

512

1000

1

540

35

664

28

1991

59

1024

2000

2

584

24

742

26

2284

98

2048

5000

4

848

22

1130

25

4078

91

4096

60000

8

1598

6

2224

4

8724

18

594

APPX
Appendix 8 Processing Performance and Processing TimeManagement Shell Explorer
The following shows the processing performance and processing time of Management Shell Explorer.

Operating environment 1
Item

Description

MPU

Intel Core-i7

Memory16 GB

Storage

64 GB

OSWindows 10 (IoT Enterprise)

Operating environment 2
Item

Description

MPU

Intel Core-i3

Memory8 GB

Storage

64 GB

OSWindows 10 (IoT Enterprise)

Operating environment 3
Item

Description

MPU

Intel Atom

Memory4 GB

Storage

60 GB

OSWindows 10 (IoT Enterprise)

Precautions
Processing of Management Shell may be delayed depending on an operating environment. For the operating environment 3
mentioned above, it is recommended to set the number of components to 100 or less, and that of resources to 300 or less percomponent to run Management Shell.

Data model import and data model export
The following shows the processing performance in data model import and data model export.

Parameter setting value
Setting item

Setting content

Number of data tag resources to be imported• For operating environment 1 or 2: 999000• For operating environment 3: 30000

Number of data tag resources to be exported
Data collector used*1

Data collector distributed by the Edgecross Consortium*1

Contact the Edgecross Consortium to obtain it.

Processing performance
Function

Performance value(second)(Operating
environment 1)

Performance value(second)(Operating
environment 2)

Performance value(second)(Operating
environment 3)

Data model import

340

599

84

Data model export

98

172

15

APPX
Appendix 8 Processing Performance and Processing Time

595

A

Monitoring and changing current values of data tag resources
The following shows the processing performance when monitoring and changing current values of data tag resources.

Parameter setting value
Setting item

Setting content

Number of data tag resources registered in the data tag
resource monitor window

256

Data collector used

Data collector distributed by the Edgecross Consortium*1

Data typeUINT type*1

Contact the Edgecross Consortium to obtain it.

Processing performance
Function

Performance value(ms)(Operating
environment 1)

Performance value(ms)(Operating
environment 2)

Performance value(ms)(Operating
environment 3)

Monitoring current values of data tag resources

410

390

460

Changing current values of data tag resources

70

250

320

596

APPX
Appendix 8 Processing Performance and Processing TimeManagement Shell Data collector
The following shows the processing performance and processing time of Management Shell Data collector.

Operating environment 1
Item

Description

MPU

Intel Core-i7

Memory16 GB

Storage

64 GB

OSWindows 10 (IoT Enterprise)

Operating environment 2
Item

Description

MPU

Intel Core-i3

Memory8 GB

Storage

64 GB

OSWindows 10 (IoT Enterprise)

Operating environment 3
Item

Description

MPU

Intel Atom

Memory4 GB

Storage

60 GB

OSWindows 10 (IoT Enterprise)

Data collection function
The following shows the processing performance capable of collecting all data in a specified cycle per collection processing
time (single collection cycle).

Parameter setting value
Setting item

Setting content

Collection cycle

500 ms(If an exceeded collection cycle error occurs, increment the collection interval in 100
milliseconds to avoid the error.)

Collection target

For 256 or more collection data tag resources
Internal data tag resource (operation) (INT)  Number of collection data tag resources
For 512 or more collection data tag resources
Internal data tag resource (operation) (INT)  500
External data tag resource (INT)  (Number of collection data tag resources - 500)
(An internal data tag resource (operation) is set to use two external data tag resources forthe operation term.)

Operating environment 1
Number of collection data tag
resources

Performance value(ms)*1

CPU usage rate (%)*2
Minimum value

Maximum value

256

500

Less than 0.1

0.5

512

500

Less than 0.1

0.5

1024

500

Less than 0.1

0.5

2048

500

Less than 0.1

1.0

3072

500

Less than 0.1

1.0

*1
*2

With this value, data can be collected without causing any errors. (The minimum value is 500 milliseconds, which is the minimum
collection interval.)
Total value of each instance if multiple instances are required

APPX
Appendix 8 Processing Performance and Processing Time

597

A

Operating environment 2
Number of collection data tag
resources

Performance value(ms)*1

CPU usage rate (%)*2
Minimum value

Maximum value

256

500

Less than 0.1

0.2

512

500

Less than 0.1

0.2

1024

500

Less than 0.1

0.2

2048

500

Less than 0.1

0.4

3072

500

Less than 0.1

0.4

*1
*2

With this value, data can be collected without causing any errors. (The minimum value is 500 milliseconds, which is the minimum
collection interval.)
Total value of each instance if multiple instances are required

Operating environment 3
Number of collection data tag
resources

Performance value(ms)*1

CPU usage rate (%)*2
Minimum value

Maximum value

256

500

Less than 0.1

0.6

512

500

Less than 0.1

0.6

1024

500

Less than 0.1

0.9

2048

500

Less than 0.1

1.2

3072

500

Less than 0.1

1.2

*1
*2

598

With this value, data can be collected without causing any errors. (The minimum value is 500 milliseconds, which is the minimum
collection interval.)
Total value of each instance if multiple instances are required

APPX
Appendix 8 Processing Performance and Processing Time

Appendix 9 Software Licenses
This software consists of multiple software components. Each of them is copyrighted by this consortium and/or third parties.
The following types of software are contained: Software copyrighted by third parties and distributed as free software
 Software licensed under the GNU Lesser General Public License (LGPL) Software licensed under the Eclipse Public License (EPL) and Eclipse Distribution License (EDL)For the open source software of the LGPL and EPL used in this software, it is allowed to obtain and redistribute the source
codes according to the LGPL and EPL conditions described in the following software information.
Page 599 Software information
These source codes can be downloaded from the Edgecross Consortium website (www.edgecross.org).
These are distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY, without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. In addition, source codes are not distributed for othersoftware.
Please refrain from inquiring about the source codes of this open source.

Software information
This product contains the following software: RapidJSON (Page 599 RapidJSON) msinttypes (Page 600 msinttypes)
 Eclipse Mosquitto (Page 601 Eclipse Mosquitto) pthread (Page 607 pthread) OpenSSL toolkit (Page 615 OpenSSL toolkit)
 Libxml2 (Page 617 Libxml2)
 C++ based OPC UA Client Server SDK Bundle (Page 617 C++ based OPC UA Client Server SDK Bundle)
 .NET Based OPC UA Client SDK, binary (Page 617 .NET Based OPC UA Client SDK, binary)A BouncyCastle (Page 617 BouncyCastle) UA-.NETStandard (Page 618 UA-.NETStandard)

RapidJSON
This product uses RapidJSON licensed under the MIT License.
The copyright and permission notices of RapidJSON are described below.
Tencent is pleased to support the open source community by making RapidJSON available.
Copyright (C) 2015 THL A29 Limited, a Tencent company, and Milo Yip. All rights reserved.
If you have downloaded a copy of the RapidJSON binary from Tencent, please note that the RapidJSON binary is licensed under the MIT License.
If you have downloaded a copy of the RapidJSON source code from Tencent, please note that RapidJSON source code is licensed under the MIT License,
except for the third-party components listed below which are subject to different license terms. Your integration of RapidJSON into your own projects may
require compliance with the MIT License, as well as the other licenses applicable to the third-party components included within RapidJSON. To avoid the
problematic JSON license in your own projects, it's sufficient to exclude the bin/jsonchecker/ directory, as it's the only code under the JSON license.
A copy of the MIT License is included in this file.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the
Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software,and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

APPX
Appendix 9 Software Licenses

599

msinttypes
This product uses msinttypes licensed under the BSD License.
The copyright and permission notices of msinttypes are described below.
The msinttypes r29
Copyright (c) 2006-2013 Alexander Chemeris
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or othermaterials provided with the distribution.
* Neither the name of copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specificprior written permission.
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENTSHALL THE REGENTS AND CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITYOF SUCH DAMAGE.

600

APPX
Appendix 9 Software Licenses

Eclipse Mosquitto
This product uses Eclipse Mosquitto licensed under the Eclipse Public License - v 2.0 and Eclipse Distribution License - v 1.0.
The permission notice of the Eclipse Public License - v 2.0 and Eclipse Distribution License - v 1.0 is described below.
Eclipse Public License - v 2.0
THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS ECLIPSE
PUBLIC LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION
OF THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT.

1. DEFINITIONS"Contribution" means:a) in the case of the initial Contributor, the initial content
Distributed under this Agreement, andb) in the case of each subsequent Contributor:i) changes to the Program, andii) additions to the Program;where such changes and/or additions to the Program originate fromand are Distributed by that particular Contributor. A Contribution"originates" from a Contributor if it was added to the Program bysuch Contributor itself or anyone acting on such Contributor's behalf.
Contributions do not include changes or additions to the Program thatare not Modified Works.
"Contributor" means any person or entity that Distributes the Program.
"Licensed Patents" mean patent claims licensable by a Contributor which
are necessarily infringed by the use or sale of its Contribution alone
or when combined with the Program.

A"Program" means the Contributions Distributed in accordance with thisAgreement.
"Recipient" means anyone who receives the Program under this Agreement
or any Secondary License (as applicable), including Contributors.
"Derivative Works" shall mean any work, whether in Source Code or otherform, that is based on (or derived from) the Program and for which theeditorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship.
"Modified Works" shall mean any work in Source Code or other form that
results from an addition to, deletion from, or modification of thecontents of the Program, including, for purposes of clarity any new filein Source Code form that contains any contents of the Program. Modified
Works shall not include works that contain only declarations,interfaces, types, classes, structures, or files of the Program solely
in each case in order to link to, bind by name, or subclass the Programor Modified Works thereof.
"Distribute" means the acts of a) distributing or b) making available
in any manner that enables the transfer of a copy.
"Source Code" means the form of a Program preferred for making
modifications, including but not limited to software source code,
documentation source, and configuration files.
"Secondary License" means either the GNU General Public License,
Version 2.0, or any later versions of that license, including any
exceptions or additional permissions as identified by the initial

APPX
Appendix 9 Software Licenses

601

Contributor.

2. GRANT OF RIGHTSa) Subject to the terms of this Agreement, each Contributor hereby
grants Recipient a non-exclusive, worldwide, royalty-free copyrightlicense to reproduce, prepare Derivative Works of, publicly display,
publicly perform, Distribute and sublicense the Contribution of such
Contributor, if any, and such Derivative Works.
b) Subject to the terms of this Agreement, each Contributor hereby
grants Recipient a non-exclusive, worldwide, royalty-free patent
license under Licensed Patents to make, use, sell, offer to sell,
import and otherwise transfer the Contribution of such Contributor,
if any, in Source Code or other form. This patent license shallapply to the combination of the Contribution and the Program if, at
the time the Contribution is added by the Contributor, such additionof the Contribution causes such combination to be covered by the
Licensed Patents. The patent license shall not apply to any othercombinations which include the Contribution. No hardware per se islicensed hereunder.
c) Recipient understands that although each Contributor grants thelicenses to its Contributions set forth herein, no assurances areprovided by any Contributor that the Program does not infringe thepatent or other intellectual property rights of any other entity.
Each Contributor disclaims any liability to Recipient for claims
brought by any other entity based on infringement of intellectual
property rights or otherwise. As a condition to exercising therights and licenses granted hereunder, each Recipient hereby
assumes sole responsibility to secure any other intellectual
property rights needed, if any. For example, if a third party
patent license is required to allow Recipient to Distribute theProgram, it is Recipient's responsibility to acquire that license
before distributing the Program.
d) Each Contributor represents that to its knowledge it has
sufficient copyright rights in its Contribution, if any, to grant
the copyright license set forth in this Agreement.
e) Notwithstanding the terms of any Secondary License, noContributor makes additional grants to any Recipient (other thanthose set forth in this Agreement) as a result of such Recipient's
receipt of the Program under the terms of a Secondary License(if permitted under the terms of Section 3).

3. REQUIREMENTS
3.1 If a Contributor Distributes the Program in any form, then:a) the Program must also be made available as Source Code, in
accordance with section 3.2, and the Contributor must accompany
the Program with a statement that the Source Code for the Program
is available under this Agreement, and informs Recipients how to
obtain it in a reasonable manner on or through a medium customarily
used for software exchange; andb) the Contributor may Distribute the Program under a license
different than this Agreement, provided that such license:i) effectively disclaims on behalf of all other Contributors all
warranties and conditions, express and implied, including

602

APPX
Appendix 9 Software Licenses

warranties or conditions of title and non-infringement, andimplied warranties or conditions of merchantability and fitness
for a particular purpose;ii) effectively excludes on behalf of all other Contributors all
liability for damages, including direct, indirect, special,incidental and consequential damages, such as lost profits;iii) does not attempt to limit or alter the recipients' rights
in the Source Code under section 3.2; andiv) requires any subsequent distribution of the Program by any
party to be under a license that satisfies the requirementsof this section 3.
3.2 When the Program is Distributed as Source Code:a) it must be made available under this Agreement, or if theProgram (i) is combined with other material in a separate file orfiles made available under a Secondary License, and (ii) the initial
Contributor attached to the Source Code the notice described in
Exhibit A of this Agreement, then the Program may be made available
under the terms of such Secondary Licenses, andb) a copy of this Agreement must be included with each copy of
the Program.
3.3 Contributors may not remove or alter any copyright, patent,
trademark, attribution notices, disclaimers of warranty, or limitationsof liability ("notices") contained within the Program from any copy of
the Program which they Distribute, provided that Contributors may add
their own appropriate notices.

A
4. COMMERCIAL DISTRIBUTION
Commercial distributors of software may accept certain responsibilities
with respect to end users, business partners and the like. While thislicense is intended to facilitate the commercial use of the Program,the Contributor who includes the Program in a commercial productoffering should do so in a manner which does not create potential
liability for other Contributors. Therefore, if a Contributor includes
the Program in a commercial product offering, such Contributor("Commercial Contributor") hereby agrees to defend and indemnify every
other Contributor ("Indemnified Contributor") against any losses,
damages and costs (collectively "Losses") arising from claims, lawsuits
and other legal actions brought by a third party against the Indemnified
Contributor to the extent caused by the acts or omissions of such
Commercial Contributor in connection with its distribution of the Programin a commercial product offering. The obligations in this section do not
apply to any claims or Losses relating to any actual or alleged
intellectual property infringement. In order to qualify, an Indemnified
Contributor must: a) promptly notify the Commercial Contributor inwriting of such claim, and b) allow the Commercial Contributor to control,and cooperate with the Commercial Contributor in, the defense and any
related settlement negotiations. The Indemnified Contributor may
participate in any such claim at its own expense.
For example, a Contributor might include the Program in a commercial
product offering, Product X. That Contributor is then a Commercial
Contributor. If that Commercial Contributor then makes performance
claims, or offers warranties related to Product X, those performance
claims and warranties are such Commercial Contributor's responsibility

APPX
Appendix 9 Software Licenses

603

alone. Under this section, the Commercial Contributor would have todefend claims against the other Contributors related to those performance
claims and warranties, and if a court requires any other Contributor to
pay any damages as a result, the Commercial Contributor must pay
those damages.

5. NO WARRANTY
EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, AND TO THE EXTENTPERMITTED BY APPLICABLE LAW, THE PROGRAM IS PROVIDED ON AN "AS IS"
BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR
IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF
TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULARPURPOSE. Each Recipient is solely responsible for determining theappropriateness of using and distributing the Program and assumes all
risks associated with its exercise of rights under this Agreement,
including but not limited to the risks and costs of program errors,compliance with applicable laws, damage to or loss of data, programsor equipment, and unavailability or interruption of operations.

6. DISCLAIMER OF LIABILITY
EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, AND TO THE EXTENTPERMITTED BY APPLICABLE LAW, NEITHER RECIPIENT NOR ANY CONTRIBUTORSSHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOSTPROFITS), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF THE PROGRAM OR THE
EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.

7. GENERAL
If any provision of this Agreement is invalid or unenforceable underapplicable law, it shall not affect the validity or enforceability of
the remainder of the terms of this Agreement, and without further
action by the parties hereto, such provision shall be reformed to theminimum extent necessary to make such provision valid and enforceable.
If Recipient institutes patent litigation against any entity(including a cross-claim or counterclaim in a lawsuit) alleging that theProgram itself (excluding combinations of the Program with other softwareor hardware) infringes such Recipient's patent(s), then such Recipient's
rights granted under Section 2(b) shall terminate as of the date such
litigation is filed.
All Recipient's rights under this Agreement shall terminate if it
fails to comply with any of the material terms or conditions of thisAgreement and does not cure such failure in a reasonable period oftime after becoming aware of such noncompliance. If all Recipient's
rights under this Agreement terminate, Recipient agrees to cease use
and distribution of the Program as soon as reasonably practicable.
However, Recipient's obligations under this Agreement and any licenses
granted by Recipient relating to the Program shall continue and survive.
Everyone is permitted to copy and distribute copies of this Agreement,
but in order to avoid inconsistency the Agreement is copyrighted andmay only be modified in the following manner. The Agreement Steward
reserves the right to publish new versions (including revisions) of
this Agreement from time to time. No one other than the Agreement

604

APPX
Appendix 9 Software Licenses

Steward has the right to modify this Agreement. The Eclipse Foundationis the initial Agreement Steward. The Eclipse Foundation may assign the
responsibility to serve as the Agreement Steward to a suitable separate
entity. Each new version of the Agreement will be given a distinguishingversion number. The Program (including Contributions) may always be
Distributed subject to the version of the Agreement under which it wasreceived. In addition, after a new version of the Agreement is published,
Contributor may elect to Distribute the Program (including its
Contributions) under the new version.
Except as expressly stated in Sections 2(a) and 2(b) above, Recipient
receives no rights or licenses to the intellectual property of any
Contributor under this Agreement, whether expressly, by implication,
estoppel or otherwise. All rights in the Program not expressly granted
under this Agreement are reserved. Nothing in this Agreement is intended
to be enforceable by any entity that is not a Contributor or Recipient.
No third-party beneficiary rights are created under this Agreement.
Exhibit A - Form of Secondary Licenses Notice"This Source Code may also be made available under the following
Secondary Licenses when the conditions for such availability set forthin the Eclipse Public License, v. 2.0 are satisfied: {name license(s),version(s), and exceptions or additional permissions here}."Simply including a copy of this Agreement, including this Exhibit A
is not sufficient to license the Source Code under Secondary Licenses.
If it is not possible or desirable to put the notice in a particular
file, then You may include the notice in a location (such as a LICENSE
file in a relevant directory) where a recipient would be likely tolook for such a notice.

A

You may add additional accurate notices of copyright ownership.

Eclipse Distribution License - v 1.0
Copyright (c) 2007, Eclipse Foundation, Inc. and its licensors.
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, thislist of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.
Neither the name of the Eclipse Foundation, Inc. nor the names of its
contributors may be used to endorse or promote products derived from thissoftware without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" ANDANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR
ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON

APPXAppendix 9 Software Licenses

605

ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THISSOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

606

APPX
Appendix 9 Software Licenses

pthreadThis product uses pthread licensed under the GNU LESSER General Public License Version 2.1, February 1999 (LGPL).
The permission notice of LGPL is described below.
GNU LESSER GENERAL PUBLIC LICENSE
Version 2.1, February 1999
Copyright (C) 1991, 1999 Free Software Foundation, Inc.
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Everyone is permitted to copy and distribute verbatim copiesof this license document, but changing it is not allowed.
[This is the first released version of the Lesser GPL. It also counts
as the successor of the GNU Library Public License, version 2, hence
the version number 2.1.]
Preamble
The licenses for most software are designed to take away yourfreedom to share and change it. By contrast, the GNU General Public
Licenses are intended to guarantee your freedom to share and change
free software--to make sure the software is free for all its users.
This license, the Lesser General Public License, applies to somespecially designated software packages--typically libraries--of theFree Software Foundation and other authors who decide to use it. You
can use it too, but we suggest you first think carefully about whether
this license or the ordinary General Public License is the better
strategy to use in any particular case, based on the explanations below.
When we speak of free software, we are referring to freedom of use,
not price. Our General Public Licenses are designed to make sure thatA

you have the freedom to distribute copies of free software (and charge
for this service if you wish); that you receive source code or can get
it if you want it; that you can change the software and use pieces of
it in new free programs; and that you are informed that you can dothese things.
To protect your rights, we need to make restrictions that forbid
distributors to deny you these rights or to ask you to surrender theserights. These restrictions translate to certain responsibilities foryou if you distribute copies of the library or if you modify it.
For example, if you distribute copies of the library, whether gratis
or for a fee, you must give the recipients all the rights that we gaveyou. You must make sure that they, too, receive or can get the sourcecode. If you link other code with the library, you must provide
complete object files to the recipients, so that they can relink themwith the library after making changes to the library and recompiling
it. And you must show them these terms so they know their rights.
We protect your rights with a two-step method: (1) we copyright thelibrary, and (2) we offer you this license, which gives you legal
permission to copy, distribute and/or modify the library.
To protect each distributor, we want to make it very clear that
there is no warranty for the free library. Also, if the library is
modified by someone else and passed on, the recipients should knowthat what they have is not the original version, so that the original
author's reputation will not be affected by problems that might beintroduced by others.
Finally, software patents pose a constant threat to the existence of

APPX
Appendix 9 Software Licenses

607

any free program. We wish to make sure that a company cannot
effectively restrict the users of a free program by obtaining a
restrictive license from a patent holder. Therefore, we insist thatany patent license obtained for a version of the library must be
consistent with the full freedom of use specified in this license.
Most GNU software, including some libraries, is covered by theordinary GNU General Public License. This license, the GNU Lesser
General Public License, applies to certain designated libraries, andis quite different from the ordinary General Public License. We use
this license for certain libraries in order to permit linking thoselibraries into non-free programs.
When a program is linked with a library, whether statically or usinga shared library, the combination of the two is legally speaking a
combined work, a derivative of the original library. The ordinary
General Public License therefore permits such linking only if theentire combination fits its criteria of freedom. The Lesser General
Public License permits more lax criteria for linking other code withthe library.
We call this license the "Lesser" General Public License because it
does Less to protect the user's freedom than the ordinary General
Public License. It also provides other free software developers Lessof an advantage over competing non-free programs. These disadvantages
are the reason we use the ordinary General Public License for many
libraries. However, the Lesser license provides advantages in certain
special circumstances.
For example, on rare occasions, there may be a special need toencourage the widest possible use of a certain library, so that it becomesa de-facto standard. To achieve this, non-free programs must beallowed to use the library. A more frequent case is that a freelibrary does the same job as widely used non-free libraries. In thiscase, there is little to gain by limiting the free library to free
software only, so we use the Lesser General Public License.
In other cases, permission to use a particular library in non-freeprograms enables a greater number of people to use a large body offree software. For example, permission to use the GNU C Library in
non-free programs enables many more people to use the whole GNU
operating system, as well as its variant, the GNU/Linux operating
system.
Although the Lesser General Public License is Less protective of theusers' freedom, it does ensure that the user of a program that is
linked with the Library has the freedom and the wherewithal to run
that program using a modified version of the Library.
The precise terms and conditions for copying, distribution andmodification follow. Pay close attention to the difference between a"work based on the library" and a "work that uses the library". The
former contains code derived from the library, whereas the latter must
be combined with the library in order to run.
GNU LESSER GENERAL PUBLIC LICENSETERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License Agreement applies to any software library or otherprogram which contains a notice placed by the copyright holder orother authorized party saying it may be distributed under the terms ofthis Lesser General Public License (also called "this License").
Each licensee is addressed as "you".

608

APPX
Appendix 9 Software Licenses

A "library" means a collection of software functions and/or dataprepared so as to be conveniently linked with application programs(which use some of those functions and data) to form executables.
The "Library", below, refers to any such software library or work
which has been distributed under these terms. A "work based on the
Library" means either the Library or any derivative work undercopyright law: that is to say, a work containing the Library or a
portion of it, either verbatim or with modifications and/or translated
straightforwardly into another language. (Hereinafter, translation is
included without limitation in the term "modification".)"Source code" for a work means the preferred form of the work formaking modifications to it. For a library, complete source code means
all the source code for all modules it contains, plus any associatedinterface definition files, plus the scripts used to control compilationand installation of the library.
Activities other than copying, distribution and modification are notcovered by this License; they are outside its scope. The act ofrunning a program using the Library is not restricted, and output fromsuch a program is covered only if its contents constitute a work basedon the Library (independent of the use of the Library in a tool for
writing it). Whether that is true depends on what the Library does
and what the program that uses the Library does.
1. You may copy and distribute verbatim copies of the Library's
complete source code as you receive it, in any medium, provided thatyou conspicuously and appropriately publish on each copy anappropriate copyright notice and disclaimer of warranty; keep intact
all the notices that refer to this License and to the absence of any

Awarranty; and distribute a copy of this License along with the
Library.
You may charge a fee for the physical act of transferring a copy,
and you may at your option offer warranty protection in exchange for afee.
2. You may modify your copy or copies of the Library or any portionof it, thus forming a work based on the Library, and copy anddistribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:a) The modified work must itself be a software library.
b) You must cause the files modified to carry prominent notices
stating that you changed the files and the date of any change.
c) You must cause the whole of the work to be licensed at nocharge to all third parties under the terms of this License.
d) If a facility in the modified Library refers to a function or atable of data to be supplied by an application program that uses
the facility, other than as an argument passed when the facility
is invoked, then you must make a good faith effort to ensure that,in the event an application does not supply such function ortable, the facility still operates, and performs whatever part ofits purpose remains meaningful.
(For example, a function in a library to compute square roots has
a purpose that is entirely well-defined independent of theapplication. Therefore, Subsection 2d requires that any

APPX
Appendix 9 Software Licenses609

application-supplied function or table used by this function must
be optional: if the application does not supply it, the squareroot function must still compute square roots.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Library,and can be reasonably considered independent and separate works inthemselves, then this License, and its terms, do not apply to thosesections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work basedon the Library, the distribution of the whole must be on the terms ofthis License, whose permissions for other licensees extend to theentire whole, and thus to each and every part regardless of who wrote
it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative orcollective works based on the Library.
In addition, mere aggregation of another work not based on the Librarywith the Library (or with a work based on the Library) on a volume ofa storage or distribution medium does not bring the other work under
the scope of this License.
3. You may opt to apply the terms of the ordinary GNU General Public
License instead of this License to a given copy of the Library. To dothis, you must alter all the notices that refer to this License, sothat they refer to the ordinary GNU General Public License, version 2,
instead of to this License. (If a newer version than version 2 of theordinary GNU General Public License has appeared, then you can specify
that version instead if you wish.) Do not make any other change inthese notices.
Once this change is made in a given copy, it is irreversible forthat copy, so the ordinary GNU General Public License applies to all
subsequent copies and derivative works made from that copy.
This option is useful when you wish to copy part of the code of
the Library into a program that is not a library.
4. You may copy and distribute the Library (or a portion orderivative of it, under Section 2) in object code or executable form
under the terms of Sections 1 and 2 above provided that you accompany
it with the complete corresponding machine-readable source code, whichmust be distributed under the terms of Sections 1 and 2 above on a
medium customarily used for software interchange.
If distribution of object code is made by offering access to copy
from a designated place, then offering equivalent access to copy thesource code from the same place satisfies the requirement to
distribute the source code, even though third parties are notcompelled to copy the source along with the object code.
5. A program that contains no derivative of any portion of the
Library, but is designed to work with the Library by being compiled or
linked with it, is called a "work that uses the Library". Such awork, in isolation, is not a derivative work of the Library, andtherefore falls outside the scope of this License.
However, linking a "work that uses the Library" with the Librarycreates an executable that is a derivative of the Library (because it
contains portions of the Library), rather than a "work that uses the

610

APPX
Appendix 9 Software Licenses

library". The executable is therefore covered by this License.
Section 6 states terms for distribution of such executables.
When a "work that uses the Library" uses material from a header filethat is part of the Library, the object code for the work may be aderivative work of the Library even though the source code is not.
Whether this is true is especially significant if the work can belinked without the Library, or if the work is itself a library. The
threshold for this to be true is not precisely defined by law.
If such an object file uses only numerical parameters, data
structure layouts and accessors, and small macros and small inline
functions (ten lines or less in length), then the use of the object
file is unrestricted, regardless of whether it is legally a derivative
work. (Executables containing this object code plus portions of the
Library will still fall under Section 6.)
Otherwise, if the work is a derivative of the Library, you may
distribute the object code for the work under the terms of Section 6.
Any executables containing that work also fall under Section 6,
whether or not they are linked directly with the Library itself.
6. As an exception to the Sections above, you may also combine orlink a "work that uses the Library" with the Library to produce awork containing portions of the Library, and distribute that work
under terms of your choice, provided that the terms permit
modification of the work for the customer's own use and reverse
engineering for debugging such modifications.
You must give prominent notice with each copy of the work that the
Library is used in it and that the Library and its use are covered bythis License. You must supply a copy of this License. If the workAduring execution displays copyright notices, you must include thecopyright notice for the Library among them, as well as a reference
directing the user to the copy of this License. Also, you must do oneof these things:a) Accompany the work with the complete corresponding
machine-readable source code for the Library including whateverchanges were used in the work (which must be distributed under
Sections 1 and 2 above); and, if the work is an executable linked
with the Library, with the complete machine-readable "work thatuses the Library", as object code and/or source code, so that theuser can modify the Library and then relink to produce a modified
executable containing the modified Library. (It is understoodthat the user who changes the contents of definitions files in the
Library will not necessarily be able to recompile the application
to use the modified definitions.)b) Use a suitable shared library mechanism for linking with the
Library. A suitable mechanism is one that (1) uses at run time a
copy of the library already present on the user's computer system,
rather than copying library functions into the executable, and (2)will operate properly with a modified version of the library, if
the user installs one, as long as the modified version isinterface-compatible with the version that the work was made with.
c) Accompany the work with a written offer, valid for atleast three years, to give the same user the materials
specified in Subsection 6a, above, for a charge no morethan the cost of performing this distribution.
d) If distribution of the work is made by offering access to copy

APPX
Appendix 9 Software Licenses

611

from a designated place, offer equivalent access to copy the above
specified materials from the same place.
e) Verify that the user has already received a copy of thesematerials or that you have already sent this user a copy.
For an executable, the required form of the "work that uses the
Library" must include any data and utility programs needed for
reproducing the executable from it. However, as a special exception,
the materials to be distributed need not include anything that isnormally distributed (in either source or binary form) with the major
components (compiler, kernel, and so on) of the operating system on
which the executable runs, unless that component itself accompanies
the executable.
It may happen that this requirement contradicts the license
restrictions of other proprietary libraries that do not normallyaccompany the operating system. Such a contradiction means you cannot
use both them and the Library together in an executable that you
distribute.
7. You may place library facilities that are a work based on the
Library side-by-side in a single library together with other libraryfacilities not covered by this License, and distribute such a combined
library, provided that the separate distribution of the work based on
the Library and of the other library facilities is otherwise
permitted, and provided that you do these two things:a) Accompany the combined library with a copy of the same work
based on the Library, uncombined with any other libraryfacilities. This must be distributed under the terms of theSections above.
b) Give prominent notice with the combined library of the factthat part of it is a work based on the Library, and explaining
where to find the accompanying uncombined form of the same work.
8. You may not copy, modify, sublicense, link with, or distributethe Library except as expressly provided under this License. Any
attempt otherwise to copy, modify, sublicense, link with, or
distribute the Library is void, and will automatically terminate yourrights under this License. However, parties who have received copies,
or rights, from you under this License will not have their licenses
terminated so long as such parties remain in full compliance.
9. You are not required to accept this License, since you have notsigned it. However, nothing else grants you permission to modify or
distribute the Library or its derivative works. These actions areprohibited by law if you do not accept this License. Therefore, bymodifying or distributing the Library (or any work based on the
Library), you indicate your acceptance of this License to do so, andall its terms and conditions for copying, distributing or modifying
the Library or works based on it.
10. Each time you redistribute the Library (or any work based on the
Library), the recipient automatically receives a license from theoriginal licensor to copy, distribute, link with or modify the Library
subject to these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties withthis License.
11. If, as a consequence of a court judgment or allegation of patent

612

APPX
Appendix 9 Software Licenses

infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement orotherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under thisLicense and any other pertinent obligations, then as a consequence you
may not distribute the Library at all. For example, if a patent
license would not permit royalty-free redistribution of the Library by
all those who receive copies directly or indirectly through you, thenthe only way you could satisfy both it and this License would be torefrain entirely from distribution of the Library.
If any portion of this section is held invalid or unenforceable under any
particular circumstance, the balance of the section is intended to apply,
and the section as a whole is intended to apply in other circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system which is
implemented by public license practices. Many people have madegenerous contributions to the wide range of software distributed
through that system in reliance on consistent application of thatsystem; it is up to the author/donor to decide if he or she is willingto distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
12. If the distribution and/or use of the Library is restricted incertain countries either by patents or by copyrighted interfaces, theA

original copyright holder who places the Library under this License may add
an explicit geographical distribution limitation excluding those countries,
so that distribution is permitted only in or among countries not thus
excluded. In such case, this License incorporates the limitation as if
written in the body of this License.
13. The Free Software Foundation may publish revised and/or new
versions of the Lesser General Public License from time to time.
Such new versions will be similar in spirit to the present version,
but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Libraryspecifies a version number of this License which applies to it and"any later version", you have the option of following the terms andconditions either of that version or of any later version published by
the Free Software Foundation. If the Library does not specify alicense version number, you may choose any version ever published by
the Free Software Foundation.
14. If you wish to incorporate parts of the Library into other freeprograms whose distribution conditions are incompatible with these,
write to the author to ask for permission. For software which is
copyrighted by the Free Software Foundation, write to the Free
Software Foundation; we sometimes make exceptions for this. Ourdecision will be guided by the two goals of preserving the free statusof all derivatives of our free software and of promoting the sharing
and reuse of software generally.
NO WARRANTY
15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO

APPXAppendix 9 Software Licenses

613

WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULARPURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO INWRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCHDAMAGES.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Libraries
If you develop a new library, and you want it to be of the greatest
possible use to the public, we recommend making it free software thateveryone can redistribute and change. You can do so by permitting
redistribution under these terms (or, alternatively, under the terms of theordinary General Public License).
To apply these terms, attach the following notices to the library. It issafest to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least the"copyright" line and a pointer to where the full notice is found.
<one line to give the library's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This library is free software; you can redistribute it and/or
modify it under the terms of the GNU Lesser General Public
License as published by the Free Software Foundation; either
version 2.1 of the License, or (at your option) any later version.
This library is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public
License along with this library; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Also add information on how to contact you by electronic and paper mail.
You should also get your employer (if you work as a programmer) or yourschool, if any, to sign a "copyright disclaimer" for the library, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in thelibrary `Frob' (a library for tweaking knobs) written by James Random Hacker.
<signature of Ty Coon>, 1 April 1990
Ty Coon, President of Vice

614

APPX
Appendix 9 Software Licenses

That's all there is to it!

OpenSSL toolkit
This product uses OpenSSL toolkit licensed under the OpenSSL License and the Original SSLeay License.
The permission notice of the OpenSSL License and Original SSLeay License is described below.
LICENSE ISSUES==============The OpenSSL toolkit stays under a double license, i.e. both the conditions of
the OpenSSL License and the original SSLeay license apply to the toolkit.
See below for the actual license texts.
OpenSSL License--------------/* ====================================================================* Copyright (c) 1998-2018 The OpenSSL Project. All rights reserved.
** Redistribution and use in source and binary forms, with or without* modification, are permitted provided that the following conditions* are met:*
* 1. Redistributions of source code must retain the above copyright*notice, this list of conditions and the following disclaimer.

** 2. Redistributions in binary form must reproduce the above copyright*notice, this list of conditions and the following disclaimer in*the documentation and/or other materials provided with the*

distribution.

** 3. All advertising materials mentioning features or use of this*software must display the following acknowledgment:*"This product includes software developed by the OpenSSL Project*for use in the OpenSSL Toolkit. (http://www.openssl.org/)"A** 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to*endorse or promote products derived from this software without*

prior written permission. For written permission, please contact*

openssl-core@openssl.org.

** 5. Products derived from this software may not be called "OpenSSL"*

nor may "OpenSSL" appear in their names without prior written*

permission of the OpenSSL Project.

** 6. Redistributions of any form whatsoever must retain the following*

acknowledgment:*"This product includes software developed by the OpenSSL Project*for use in the OpenSSL Toolkit (http://www.openssl.org/)"** THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY* EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR* PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR* ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT* NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;* LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,* STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED* OF THE POSSIBILITY OF SUCH DAMAGE.
* ====================================================================APPX
Appendix 9 Software Licenses

615** This product includes cryptographic software written by Eric Young* (eay@cryptsoft.com). This product includes software written by Tim* Hudson (tjh@cryptsoft.com).
**/
Original SSLeay License----------------------/* Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)* All rights reserved.
** This package is an SSL implementation written* by Eric Young (eay@cryptsoft.com).
* The implementation was written so as to conform with Netscapes SSL.
*
* This library is free for commercial and non-commercial use as long as* the following conditions are aheared to. The following conditions* apply to all code found in this distribution, be it the RC4, RSA,
* lhash, DES, etc., code; not just the SSL code. The SSL documentation* included with this distribution is covered by the same copyright terms* except that the holder is Tim Hudson (tjh@cryptsoft.com).
** Copyright remains Eric Young's, and as such any Copyright notices in* the code are not to be removed.
* If this package is used in a product, Eric Young should be given attribution* as the author of the parts of the library used.
* This can be in the form of a textual message at program startup or* in documentation (online or textual) provided with the package.
** Redistribution and use in source and binary forms, with or without* modification, are permitted provided that the following conditions* are met:
* 1. Redistributions of source code must retain the copyright*notice, this list of conditions and the following disclaimer.

* 2. Redistributions in binary form must reproduce the above copyright*notice, this list of conditions and the following disclaimer in the*

documentation and/or other materials provided with the distribution.

* 3. All advertising materials mentioning features or use of this software*must display the following acknowledgement:*"This product includes cryptographic software written by*

Eric Young (eay@cryptsoft.com)"*

The word 'cryptographic' can be left out if the rouines from the library*

being used are not cryptographic related :-).

* 4. If you include any Windows specific code (or a derivative thereof) from*the apps directory (application code) you must include an acknowledgement:*"This product includes software written by Tim Hudson (tjh@cryptsoft.com)"** THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF* SUCH DAMAGE.
** The licence and distribution terms for any publically available version or* derivative of this code cannot be changed. i.e. this code cannot simply be

616

APPX
Appendix 9 Software Licenses

* copied and put under another distribution licence* [including the GNU Public Licence.]*/

Libxml2
This product uses Libxml2 licensed under the MIT License.
The copyright and permission notices of Libxml2 are described below.
Except where otherwise noted in the source code (e.g. the files hash.c,list.c and the trio files, which are covered by a similar licence butwith different Copyright notices) all the files are:Copyright (C) 1998-2012 Daniel Veillard. All Rights Reserved.
Permission is hereby granted, free of charge, to any person obtaining a copyof this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sellcopies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.

C++ based OPC UA Client Server SDK Bundle

A

This product uses C++ based OPC UA Client Server SDK Bundle.
The copyright notice of C++ based OPC UA Client Server SDK Bundle is described below.
Copyright (c) 2006-2023 Unified Automation GmbH. All rights reserved.

.NET Based OPC UA Client SDK, binary
This product uses .NET Based OPC UA Client SDK, binary.
The copyright notice of .NET Based OPC UA Client SDK, binary is described below.
Copyright (c) 2006-2023 Unified Automation GmbH. All rights reserved.

BouncyCastle
This product uses BouncyCastle licensed under the MIT License.
The copyright and permission notices of BouncyCastle are described below.
Copyright (c) 2000 - 2017 The Legion of the Bouncy Castle Inc. (http://www.bouncycastle.org)
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the
Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software,and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

APPX
Appendix 9 Software Licenses

617

UA-.NETStandard
This product uses UA-.NETStandard of OPCFoundation.
The permission notice of UA-.NETStandard is described below.
This repository includes the UA .NET Stack sample libraries and sample applications, all based on the .NET StandardLibrary. The UA .NET StandardLibrary
Stack follows a dual-license:• OPC Foundation Corporate Members: RCL• Everybody else: GPL 2.0
RCL enables OPC Foundation members to deploy their applications using the software without being required to disclose the application code. Non-members
licensed under GPL 2.0 must disclose their application code when using the software.
If OPC Foundation Corporate Membership is terminated, the licence reverts to GPL 2.0 whenever any fixes or updates published on GitHub are applied to theformer member's application. This includes updates acquired by fetching any Git commit made after membership termination or the use of binaries distributed in
OPC NuGet packages that were posted after the membership termination date.
Note: Dual license applies to this repository only; GPL 2.0 applies to all other repositories
All samples, the platform layers, and files generated with the ModelCompiler by means of the OPC UA NodeSet are provided under the MIT license.

[RCL License]
Reciprocal Community License 1.00 (RCL1.00)
Version 1.00, June 24, 2009
Copyright (C) 2008, 2009 OPC Foundation, Inc., All Rights Reserved.
PREAMBLE
The Reciprocal Community License (RCL) is based on the concept of reciprocity or, if you prefer, fairness.
The RCL is adapted from the Open Source Reciprocal Public License (RPL) where the "Public" in the Open Source RPL license is replaced by the "Community"in the RCL License. In short, the RPL license grew out of a desire to close loopholes in previous open source licenses, loopholes that allowed parties to acquire
open source software and derive financial benefit from it without having to release their improvements or derivatives to the community which enabled them. Thisoccurred any time an entity did not release their application to a "third party". While there is a certain freedom in this model of licensing, it struck the authors of
the RPL as being unfair to the open source community at large and to the original authors of the works in particular. After all, bug fixes, extensions, andmeaningful and valuable derivatives were not consistently faster, growth and expansion of the overall open source software base.
While you should clearly read and understand the entire license, the essence of the RCL is found in two definitions: "Deploy" and "Required Components".
Regarding deployment, under the RCL your changes, bug fixes, extensions, etc. must be made available to the community when you Deploy in any form -either internally or to an outside party.
Once you start running the software you have to start sharing the software. Further, under the RCL all derivative work components you author including
schemas, scripts, source code, documentation, etc. -- must be shared. You have to share the whole pie, not an isolated slice of it. The authored components
you must share are confined to the original module licensed (e.g. SDK, stack, wrapper, proxy, utility, etc.). You do not need to share any additional authoredcomponents that you create that utilize the licensed component. This license is meant to be friendly to commercial software vendors that must protect the IP intheir code. You are not expected to share your proprietary source code that makes use of the module(s) licensed under this agreement.
The specific terms and conditions of the license are defined in the remainder of this document.
1 LICENSE TERMS
1.1 General; Applicability & Definitions. This Reciprocal Community License Version 1.00 ("License") applies to any programs or other works as well as any andall updates or maintenance releases of said programs or works ("Software") not already covered by this License which the Software copyright holder("Licensor") makes available containing a License Notice (hereinafter defined) from the Licensor specifying or allowing use or distribution under the terms of thisLicense. As used in this License:
1.2 "Contributor" means any person or entity who created or contributed to the creation of an Extension.
1.3 "Deploy" means to use, Serve, sublicense or distribute Licensed Software other than for Your internal Research and/or Personal Use, and includes without
limitation, any and all internal use or distribution of Licensed Software within Your business or organization other than for Research and/or Personal Use, as
well as direct or indirect sublicensing or distribution of Licensed Software by You to any third party.
1.4 "Derivative Works" as used in this License is defined under U.S. copyright law.
1.5 "Extensions" means any Modifications, Derivative Works, or Required Components as those terms are defined in this License.
1.6 "License" means this Reciprocal Community License.
1.7 "License Notice" means any notice contained in EXHIBIT A.
1.8 "Licensed Software" means any Software licensed pursuant to this License. Licensed Software also includes all previous Extensions from any Contributor
that You receive.
1.9 "Licensor" means the copyright holder of any Software previously not covered by this License who releases the Software under the terms of this License.

618

APPX
Appendix 9 Software Licenses

1.10 "Modifications" means any additions to or deletions from the substance or structure of (i) a file containing Licensed Software, or (ii) any new file that
contains any part of Licensed Software.
1.11 "Original Licensor" means the Licensor that is the copyright holder of the original work. For this license the Original Licensor is always the OPC Foundation.
1.12 "Personal Use" means use of Licensed Software by an individual solely for his or her personal, private and non-commercial purposes.
An individual's use of Licensed Software in his or her capacity as an officer, employee, member, independent contractor or agent of a corporation, business ororganization (commercial or non-commercial) does not qualify as Personal Use.
1.13 "Required Components" means any text, programs, scripts, schema, interface definitions, control files, or other works created by You which arerequired by a third party of average skill to successfully install and run Licensed Software containing Your Modifications, or to install and run Your Derivative
Works. Required Components by this definition are the supporting works that are necessary to utilize your Modifications and Derivative Works. This does notinclude your applications and supporting works that utilize the Licensed Software.
1.14 "Research" means investigation or experimentation for the purpose of understanding the nature and limits of the Licensed Software and its potential uses.
1.15 "Serve" means to deliver Licensed Software and/or Your Extensions by means of a computer network to one or more computers for purposes of executionof Licensed Software and/or Your Extensions.
1.16 "Software" means any computer programs or other works as well as any updates or maintenance releases of those programs or works which are
distributed publicly by Licensor.
1.17 "Source Code" means the preferred form for making modifications to the Licensed Software and/or Your Extensions, including all modules contained
therein, plus any associated text, interface definition files, scripts used to control compilation and installation of an executable program or other components
required by a third party of average skill to build a running version of the Licensed Software or Your Extensions.
1.18 "User-Visible Attribution Notice" means any notice contained in EXHIBIT B.
1.19 "You" or "Your" means an individual or a legal entity exercising rights under this License. For legal entities, "You" or "Your" includes any entity which
controls, is controlled by, or is under common control with, You, where "control" means (a) the power, direct or indirect, to cause the direction or managementof such entity, whether by contract or otherwise, or (b) ownership of fifty percent (50%) or more of the outstanding shares or beneficial ownership of such entity.
2.0 Acceptance Of License. You are not required to accept this License since you have not signed it, however nothing else grants you permission to use, copy,
distribute, modify, or create derivatives of either the Software or any Extensions created by a Contributor. These actions are prohibited by law if you do not
accept this License. Therefore, by performing any of these actions You indicate Your acceptance of this License and Your agreement to be bound by all its
terms and conditions. IF YOU DO NOT AGREE WITH ALL THE TERMS AND CONDITIONS OF THIS LICENSE DO NOT USE, MODIFY, CREATEDERIVATIVES, OR DISTRIBUTE THE SOFTWARE. IF IT IS IMPOSSIBLE FOR YOU TO COMPLY WITH ALL THE TERMS AND CONDITIONS OF THISLICENSE THEN YOU CAN NOT USE, MODIFY, CREATE DERIVATIVES, OR DISTRIBUTE THE SOFTWARE.
3.0 Grant of License From Licensor. Subject to the terms and conditions of this License, Licensor hereby grants You a world-wide, royalty-free, non- exclusive
license, subject to Licensor's intellectual property rights, and any third party intellectual property claims derived from the Licensed Software under this License,
to do the following:
3.1 Use, reproduce, modify, display, and perform Licensed Software and Your Extensions in both Source Code form or as an executable program. You may
also sublicense and distribute Licensed Software and Your Extensions as an executable program. OPC Foundation Corporate Members may also sublicenseand distribute Licensed Software and Your Extensions in Source Code form.
3.2 Create Derivative Works (as that term is defined under U.S. copyright law) of Licensed Software.
3.3 Under claims of patents now or hereafter owned or controlled by Licensor, to make, use, have made, and/or otherwise dispose of Licensed Software or
portions thereof, but solely to the extent that any such claim is necessary to enable You to make, use, have made, and/or otherwise dispose of Licensed
Software or portions thereof.
3.4 Licensor reserves the right to release new versions of the Software with different features, specifications, capabilities, functions, licensing terms, generalavailability or other characteristics. Title, ownership rights, and intellectual property rights in and to the Licensed Software shall remain in Licensor and/or its
Contributors.
4.0 Grant of License From Contributor. By application of the provisions in Section 6 below, each Contributor hereby grants You a world-wide, royalty- free, nonexclusive license, subject to said Contributor's intellectual property rights, and any third party intellectual property claims derived from the Licensed Software
under this License, to do the following:
4.1 Use, reproduce, modify, display and perform any Extensions Deployed by such Contributor or portions thereof, in both Source Code form or as an
executable program, either on an unmodified basis or as part of Derivative Works. You may also sublicense and distribute Extensions Deployed by such
Contributor or portions thereof, as an executable program. OPC Foundation Corporate Members may also sublicense and distribute Extensions Deployed bysuch Contributor or portions thereof, in Source Code form.
4.2 Under claims of patents now or hereafter owned or controlled by Contributor, to make, use, have made, and/or otherwise dispose of Extensions or
portions thereof, but solely to the extent that any such claim is necessary to enable You to make, use, have made, and/or otherwise dispose of Licensed
Software or portions thereof.
5.0 Exclusions From License Grant. Nothing in this License shall be deemed to grant any rights to trademarks, copyrights, patents, trade secrets or any otherintellectual property of Licensor or any Contributor except as expressly stated herein. Except as expressly stated in Sections 3 and 4, no other patent rights,
express or implied, are granted herein. Your Extensions may require additional patent licenses from Licensor or Contributors which each may grant in its sole
discretion. No right is granted to the trademarks of Licensor or any Contributor even if such marks are included in the Licensed Software. Nothing in this License
shall be interpreted to prohibit Licensor from licensing under different terms from this License any code that Licensor otherwise would have a right to license.

APPX
Appendix 9 Software Licenses

619

A5.1 You expressly acknowledge and agree that although Licensor and each Contributor grants the licenses to their respective portions of the Licensed Software
set forth herein, no assurances are provided by Licensor or any Contributor that the Licensed Software does not infringe the patent or other intellectual property
rights of any other entity. Licensor and each Contributor disclaim any liability to You for claims brought by any other entity based on infringement of intellectual
property rights or otherwise. As a condition to exercising the rights and licenses granted hereunder, You hereby assume sole responsibility to secure any otherintellectual property rights needed, if any. For example, if a third party patent license is required to allow You to distribute the Licensed Software, it is Your
responsibility to acquire that license before distributing the Licensed Software.
6.0 Your Obligations And Grants. In consideration of, and as an express condition to, the licenses granted to You under this License You hereby agree that any
Modifications, Derivative Works, or Required Components (collectively Extensions) that You create or to which You contribute are governed by the terms of thisLicense including, without limitation, Section 4. Any Extensions that You create or to which You contribute must be Deployed under the terms of this License ora future version of this License released under Section 7. You hereby grant to Licensor and all third parties a world-wide, non-exclusive, royalty-free licenseunder those intellectual property rights You own or control to use, reproduce, display, perform, modify, create derivatives, sublicense, and distribute Licensed
Software, in any form.
Any Extensions You make and Deploy must have a distinct title so as to readily tell any subsequent user or Contributor that the Extensions are by You. You must
include a copy of this License or directions on how to obtain a copy with every copy of the Extensions You distribute. You agree not to offer or impose any terms
on any Source Code or executable version of the Licensed Software, or its Extensions that alter or restrict the applicable version of this License or the recipients'rights hereunder. Additionally, you herby grant to the Original Licensor the right to use, reproduce, display, perform, modify, create derivatives, sublicense, anddistribute Licensed Software, in any form, under the terms of this license and/or any other license terms it sees fit.
6.1 Availability of Source Code. You must make available, under the terms of this License, the Source Code of any Extensions that You Deploy, by uploading
the Source Code directly to the website of the Original Licensor. The Source Code for any version that You Deploy must be made available within one (1) monthof when you Deploy. You may not charge a fee for any copy of the Source Code distributed under this Section. At the sole discretion of the Original Licensor,
some or all of Your contributed Source Code may be included in a future baseline version released by the Original Licensor.
6.2 Description of Modifications. You must cause any Modifications that You create or to which You contribute to be documented in the Source Code, clearly
describing the additions, changes or deletions You made. You must include a prominent statement that the Modifications are derived, directly or indirectly, fromthe Licensed Software and include the names of the Licensor and any Contributor to the Licensed Software in (i) the Source Code and (ii) in any noticedisplayed by the Licensed Software You distribute or in related documentation in which You describe the origin or ownership of the Licensed Software. You may
not modify or delete any pre-existing copyright notices, change notices or License text in the Licensed Software without written permission of the respective
Licensor or Contributor.
6.3 Intellectual Property Matters.
a. Third Party Claims. If You have knowledge that a license to a third party's intellectual property right is required to exercise the rights granted by this License,
You must include a human-readable file with Your distribution that describes the claim and the party making the claim in sufficient detail that a recipient will knowwhom to contact.
b. Contributor APIs. If Your Extensions include an application programming interface ("API") and You have knowledge of patent licenses that are reasonably
necessary to implement that API, You must also include this information in a human-readable file supplied with Your distribution.
c. Representations. You represent that, except as disclosed pursuant to 6.3(a) above, You believe that any Extensions You distribute are Your original
creations and that You have sufficient rights to grant the rights conveyed by this License.
6.4 Required Notices.
a. License Text. You must duplicate this License or instructions on how to acquire a copy in any documentation You provide along with the Source Code of any
Extensions You create or to which You contribute, wherever You describe recipients' rights relating to Licensed Software.
b. License Notice. You must duplicate any notice contained in EXHIBIT A (the "License Notice") in each file of the Source Code of any copy You distribute of theLicensed Software and Your Extensions. If You create an Extension, You may add Your name as a Contributor to the Source Code and accompanying
documentation along with a description of the contribution. If it is not possible to put the License Notice in a particular Source Code file due to its structure, then
You must include such License Notice in a location where a user would be likely to look for such a notice.
c. User-Visible Attribution. You must duplicate any notice contained in EXHIBIT B (the "User-Visible Attribution Notice") in each user-visible display of theLicensed Software and Your Extensions which delineates copyright, ownership, or similar attribution information. If You create an Extension, You may add
Your name as a Contributor, and add Your attribution notice, as an equally visible and functional element of any User-Visible Attribution Notice content. To
ensure proper attribution, You must also include such User-Visible Attribution Notice in at least one location in the Software documentation where a user would
be likely to look for such notice.
6.5 Additional Terms. You may choose to offer, and charge a fee for, warranty, support, indemnity or liability obligations to one or more recipients of Licensed
Software. However, You may do so only on Your own behalf, and not on behalf of the Licensor or any Contributor except as permitted under other agreements
between you and Licensor or Contributor. You must make it clear that any such warranty, support, indemnity or liability obligation is offered by You alone, andYou hereby agree to indemnify the Licensor and every Contributor for any liability plus attorney fees, costs, and related expenses due to any such action or
claim incurred by the Licensor or such Contributor as a result of warranty, support, indemnity or liability terms You offer.
6.6 Conflicts With Other Licenses. Where any portion of Your Extensions, by virtue of being Derivative Works of another product or similar circumstance, fallunder the terms of another license, the terms of that license should be honored however You must also make Your Extensions available under this License. If
the terms of this License continue to conflict with the terms of the other license you may write the Licensor for permission to resolve the conflict in a fashion thatremains consistent with the intent of this License. Such permission will be granted at the sole discretion of the Licensor.

620

APPX
Appendix 9 Software Licenses

7.0 Versions of This License. Licensor may publish from time to time revised versions of the License. Once Licensed Software has been published under aparticular version of the License, You may always continue to use it under the terms of that version. You may also choose to use such Licensed Software under
the terms of any subsequent version of the License published by Licensor. No one other than Licensor has the right to modify the terms applicable to Licensed
Software created under this License.
7.1 If You create or use a modified version of this License, which You may do only in order to apply it to software that is not already Licensed Software under thisLicense, You must rename Your license so that it is not confusingly similar to this License, and must make it clear that Your license contains terms that differ
from this License. In so naming Your license, You may not use any trademark of Licensor or of any Contributor. Should Your modifications to this License belimited to alteration of a) Section 13.8 solely to modify the legal Jurisdiction or Venue for disputes, b) EXHIBIT A solely to define License Notice text, or c) to
EXHIBIT B solely to define a User-Visible Attribution Notice, You may continue to refer to Your License as the Reciprocal Community License or simply the RCL.
8.0 Disclaimer of Warranty. LICENSED SOFTWARE IS PROVIDED UNDER THIS LICENSE ON AN "AS IS" BASIS, WITHOUT WARRANTY OF ANY KIND,
EITHER EXPRESS OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT THE LICENSED SOFTWARE IS FREE OF DEFECTS,
MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. FURTHER THERE IS NO WARRANTY MADE AND ALL IMPLIEDWARRANTIES ARE DISCLAIMED THAT THE LICENSED SOFTWARE MEETS OR COMPLIES WITH ANY DESCRIPTION OF PERFORMANCE OR
OPERATION, SAID COMPATIBILITY AND SUITABILITY BEING YOUR RESPONSIBILITY. LICENSOR DISCLAIMS ANY WARRANTY, IMPLIED
OREXPRESSED,THAT ANY CONTRIBUTOR'S EXTENSIONS MEET ANY STANDARD OF COMPATIBILITY OR DESCRIPTION OF PERFORMANCE.
THE ENTIRE RISK AS TO THE QUALITY ANDPERFORMANCE OF THE LICENSED SOFTWARE IS WITH YOU. SHOULD LICENSED SOFTWARE PROVE
DEFECTIVE IN ANY RESPECT, YOU (AND NOT THE LICENSOR OR ANY OTHER CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARYSERVICING, REPAIR OR CORRECTION. UNDER THE TERMS OF THIS LICENSOR WILL NOT SUPPORT THIS SOFTWARE AND IS UNDER NOOBLIGATION TO ISSUE UPDATES TO THIS SOFTWARE. LICENSOR HAS NO KNOWLEDGE OF ERRANT CODE OR VIRUS IN THIS SOFTWARE, BUT
DOES NOT WARRANT THAT THE SOFTWARE IS FREE FROM SUCH ERRORS OR VIRUSES. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN
ESSENTIAL PART OF THIS LICENSE. NO USE OF LICENSED SOFTWARE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER.
9.0 Limitation of Liability. UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT (INCLUDING NEGLIGENCE), CONTRACT,OR OTHERWISE, SHALL THE LICENSOR, ANY CONTRIBUTOR, OR ANY DISTRIBUTOR OF LICENSED SOFTWARE, OR ANY SUPPLIER OF ANY OF
SUCH PARTIES, BE LIABLE TO ANY PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTERINCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE, COMPUTERFAILURE OR MALFUNCTION, OR ANY
AND ALL OTHER COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCHDAMAGES. THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY RESULTING FROM SUCH PARTY'S
NEGLIGENCE TO THE EXTENTAPPLICABLE LAW PROHIBITS SUCH LIMITATION.
SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THISEXCLUSION
AND LIMITATION MAY NOT APPLY TO YOU.
10.0 Restricted Rights Legend. This Specification is provided with Restricted Rights. Use, duplication or disclosure by the U.S. government is subject torestrictions as set forth in (a) this Agreement pursuant to DFARs 227.7202-3(a); (b) subparagraph (c)(1)(i) of the Rights in Technical Data and Computer
Software clause at DFARs 252.227-7013; or (c) the Commercial Computer Software Restricted Rights clause at FAR 52.227-19 subdivision (c)(1) and (2), as
applicable. Contractor / manufacturer are the OPC Foundation,. 16101 N. 82nd Street, Suite 3B, Scottsdale, AZ, 85260-1830 11.0 Responsibility for Claims. As
between Licensor and Contributors, each party is responsible for claims and damages arising, directly or indirectly, out of its utilization of rights under thisLicense which specifically disclaims warranties and limits any liability of the Licensor.
This paragraph is to be used in conjunction with and controlled by the Disclaimer Of Warranties of Section 8, the Limitation Of Damages in Section 9, and thedisclaimer against use for High Risk Activities in Section 10. The Licensor has thereby disclaimed all warranties and limited any damages that it is or may beliable for. You agree to work with Licensor and Contributors to distribute such responsibility on an equitable basis consistent with the terms of this License
including Sections 8, 9, and 10. Nothing herein is intended or shall be deemed to constitute any admission of liability.
12.0 Termination. This License and all rights granted hereunder will terminate immediately in the event of the circumstances described in Section 136 or if
applicable law prohibits or restricts You from fully and or specifically complying with Sections 3, 4 and/or 6, or prevents the enforceability of any of those
Sections, and You must immediately discontinue any use of Licensed Software.
12.1 Automatic Termination Upon Breach. This License and the rights granted hereunder will terminate automatically if You fail to comply with the terms herein
and fail to cure such breach within thirty (30) days of becoming aware of the breach. All sublicenses to the Licensed Software that are properly granted shallsurvive any termination of this License. Provisions that, by their nature, must remain in effect beyond the termination of this License, shall survive.
12.2 Termination Upon Assertion of Patent Infringement. If You initiate litigation by asserting a patent infringement claim (excluding declaratory judgment
actions) against Licensor or a Contributor (Licensor or Contributor against whom You file such an action is referred to herein as "Respondent") alleging that
Licensed Software directly or indirectly infringes any patent, then any and all rights granted by such Respondent to You under Sections 3 or 4 of this License
shall terminate prospectively upon sixty (60) days notice from Respondent (the "Notice Period") unless within that Notice Period You either agree in writing (i) to
pay Respondent a mutually agreeable reasonably royalty for Your past or future use of Licensed Software made by such Respondent, or (ii) withdraw Your
litigation claim with respect to Licensed Software against such Respondent.
If within said Notice Period a reasonable royalty and payment arrangement are not mutually agreed upon in writing by the parties or the litigation claim is notwithdrawn, the rights granted by Licensor to You under Sections 3 and 4 automatically terminate at the expiration of said Notice Period.
12.3 Reasonable Value of This License. If You assert a patent infringement claim against Respondent alleging that Licensed Software directly or indirectly
infringes any patent where such claim is resolved (such as by license or settlement) prior to the initiation of patent infringement litigation, then the reasonablevalue of the licenses granted by said Respondent under Sections 3 and 4 shall be taken into account in determining the amount or value of any payment or
license.
12.4 No Retroactive Effect of Termination. In the event of termination under this Section all end user license agreements (excluding licenses to distributors andresellers) that have been validly granted by You or any distributor hereunder prior to termination shall survive termination.

APPX
Appendix 9 Software Licenses

621

A13.0 Miscellaneous.
13.1 U.S. Government End Users. The Licensed Software is a "commercial item, " as that term is defined in 48 C.F.R. 2.101 (Oct. 1995), consisting of"commercial computer software" and "commercial computer software documentation, " as such terms are used in 48 C.F.R. 12.212 (Sept. 1995). Consistent
with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June 1995), all U.S. Government End Users acquire Licensed Software with only thoserights set forth herein.
13.2 Relationship of Parties. This License will not be construed as creating an agency, partnership, joint venture, or any other form of legal association
between or among You, Licensor, or any Contributor, and You will not represent to the contrary, whether expressly, by implication, appearance, or otherwise.
13.3 Independent Development. Nothing in this License will impair Licensor's right to acquire, license, develop, subcontract, market, or distribute technology
or products that perform the same or similar functions as, or otherwise compete with, Extensions that You may develop, produce, market, or distribute.
13.4 Consent To Breach Not Waiver. Failure by Licensor or Contributor to enforce any provision of this License will not be deemed a waiver of future
enforcement of that or any other provision.
13.5 Severability. This License represents the complete agreement concerning the subject matter hereof. If any provision of this License is held to be
unenforceable, such provision shall be reformed only to the extent necessary to make it enforceable.
13.6 Inability to Comply Due to Statute or Regulation. If it is impossible for You to comply with any of the terms of this License with respect to some or all of theLicensed Software due to statute, judicial order, or regulation, then You cannot use, modify, or distribute the software.
13.7 Export Restrictions. You may be restricted with respect to downloading or otherwise acquiring, exporting, or reexporting the Licensed Software or any
underlying information or technology by United States and other applicable laws and regulations. By downloading or by otherwise obtaining the Licensed
Software, You are agreeing to be responsible for compliance with all applicable laws and regulations.
13.8 Arbitration, Jurisdiction & Venue. This License shall be governed by Minnesota law provisions (except to the extent applicable law, if any, provides
otherwise), excluding its conflict-of-law provisions. You expressly agree that any dispute relating to this License shall be submitted to binding arbitration under
the rules then prevailing of the American Arbitration Association. You further agree that Minnesota USA is proper venue and grant such arbitration proceeding
jurisdiction as may be appropriate for purposes of resolving any dispute under this License. Judgment upon any award made in arbitration may be entered andenforced in any court of competent jurisdiction. The arbitrator shall award attorney's fees and costs of arbitration to the prevailing party.
Should either party find it necessary to enforce its arbitration award or seek specific performance of such award in a civil court of competent jurisdiction, theprevailing party shall be entitled to reasonable attorney's fees and costs. The application of the United Nations Convention on Contracts for the International
Sale of Goods is expressly excluded. You and Licensor expressly waive any rights to a jury trial in any litigation concerning Licensed Software or this License.
Any law or regulation that provides that the language of a contract shall be construed against the drafter shall not apply to this License.
13.9 Entire Agreement. This License constitutes the entire agreement between the parties with respect to the subject matter hereof.
EXHIBIT A
The License Notice below must appear in each file of the Source Code of any copy You distribute of the Licensed Software or any Extensions thereto:
Unless explicitly acquired and licensed from Licensor under another license, the contents of this file are subject to the Reciprocal Community License ("RCL")
Version 0.9, or subsequent versions as allowed by the RCL, and You may not copy or use this file in either source code or executable form, except incompliance with the terms and conditions of the RCL.
All software distributed under the RCL is provided strictly on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, AND
LICENSOR HEREBY DISCLAIMS ALL SUCH WARRANTIES, INCLUDING WITHOUT LIMITATION, ANY WARRANTIES OF MERCHANTABILITY, FITNESSFOR A PARTICULAR PURPOSE, QUIET ENJOYMENT, OR NON-INFRINGEMENT. See the RCL for specific language governing rights and limitations under
the RCL.
EXHIBIT B
The User-Visible Attribution Notice below, when provided, must appear in each user-visible display as defined in Section 6.4 (c): "Portions copyright  by OPC
Foundation, Inc. and licensed under the Reciprocal Community License (RCL)[GPLv2 License]
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA

622

APPX
Appendix 9 Software Licenses

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
Preamble
The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended toguarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of theFree Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by
the GNU Lesser General Public License instead.) You can apply it to your programs, too.
When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to
distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change thesoftware or use pieces of it in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate
to certain responsibilities for you if you distribute copies of the software, or if you modify it.
For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must makesure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.
We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or
modify the software.
Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software
is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others
will not reflect on the original authors' reputations.
Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtainpatent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or notlicensed at all.
The precise terms and conditions for copying, distribution and modification follow.
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this
General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any
derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated intoanother language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you".
Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not
restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made byrunning the Program). Whether that is true depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously andappropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to theabsence of any warranty; and give any other recipients of the Program a copy of this License along with the Program.
You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute suchmodifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change.
b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed asa whole at no charge to all third parties under the terms of this License.
c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the mostordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you
provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if
the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)
These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably
considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as
separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on
the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.

APPX
Appendix 9 Software Licenses

623

AThus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the
distribution of derivative or collective works based on the Program.
In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or
distribution medium does not bring the other work under the scope of this License.
3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2
above provided that you also do one of the following:a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a
medium customarily used for software interchange; or,b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source
distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial
distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)
The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all thesource code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of theexecutable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form)
with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies theexecutable.
If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source codefrom the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify,
sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, orrights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.
5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program orits derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work
based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying theProgram or works based on it.
6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy,
distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights
granted herein. You are not responsible for enforcing compliance by third parties to this License.
7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed onyou (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License.
If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may
not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies
directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.
If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section
as a whole is intended to apply in other circumstances.
It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has
the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have madegenerous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/
donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.
This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.
8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who
places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only inor among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.
9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in
spirit to the present version, but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", youhave the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program
does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.

624

APPX
Appendix 9 Software Licenses

10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission.
For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Ourdecision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software
generally.
NO WARRANTY
11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BYAPPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE
PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCEOF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,REPAIR OR CORRECTION.
12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY
WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANYGENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDINGBUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF
THE POSSIBILITY OF SUCH DAMAGES.
END OF TERMS AND CONDITIONSAAPPXAppendix 9 Software Licenses

625

Appendix 10 Using a Setting File in a Different Version
This section explains the considerations for using a setting file in a different version of Edgecross Basic Software from the one
with which the setting file was created.

Real-time Flow Designer
Using a setting file in an earlier version
Using a setting file, which was created in version 1.10 or later, in version 1.01 or earlier
Function

Consideration

Data storing setting (file saving)If there is output target data that satisfies either of the following conditions in the [Output Data] tab, a setting filecannot be read in version 1.01 or earlier.
• The data type is REAL and the output format is the decimal format (6 digits or more after the decimal point).
• The data type is LREAL and the output format is the decimal format (15 digits or more after the decimal point).

Edge application diagnosis (file) setting

If there is output target data that satisfies either of the following conditions in the [Output Data] tab, a setting filecannot be read in version 1.01 or earlier.
• The data type is REAL and the output format is the decimal format (6 digits or more after the decimal point).
• The data type is LREAL and the output format is the decimal format (15 digits or more after the decimal point).

Using a setting file, which was created in version 1.20 or later, in version 1.10 or earlier
Function

Consideration

Data logging flow setting
Data diagnosis flow setting

If a surrogate pair character (U+10000 to U+10FFFF) is included in a data modification plug-in name or data
diagnosis plug-in name selected for "Function Type," a setting file cannot be read in version 1.10 or earlier.

Data extraction setting

If a surrogate pair character (U+10000 to U+10FFFF) is included in a name set for "Output Data Name," a setting
file cannot be read in version 1.10 or earlier.

Edge application diagnosis (MQTT) setting

If a surrogate pair character (U+10000 to U+10FFFF) is included in a name set for "Output Data Setting Name" inthe [Response Data] tab, a setting file cannot be read in version 1.10 or earlier.

Edge application diagnosis (file) setting
Data storing setting (file saving)If either of the following characters is included in a prefix set for "File Name Prefix" in the [Save File] tab, a setting
file cannot be read in version 1.10 or earlier.
• Unicode Basic Multilingual Plane outside the ASCII range (0x007F to 0xFFFF)• Surrogate pair characters (U+10000 to U+10FFFF)

Data storing setting (file saving)If a surrogate pair character (U+10000 to U+10FFFF) is included in a name set for "Output Name" in the [Output
Data] tab, a setting file cannot be read in version 1.10 or earlier.

Data storing setting (DB saving)If a surrogate pair character (U+10000 to U+10FFFF) is included in a name set for "Table Name" or "Field Name"in the [Access Table] tab, a setting file cannot be read in version 1.10 or earlier.

Data modification plug-in setting
Data diagnosis plug-in setting

If a surrogate pair character (U+10000 to U+10FFFF) is included in a name set for "Output Data Setting Name,"a setting file cannot be read in version 1.10 or earlier.
If a surrogate pair character (U+10000 to U+10FFFF) is included in a name set for "Output Data Setting Name,"a setting file cannot be read in version 1.10 or earlier.

Data collection setting

If a surrogate pair character (U+10000 to U+10FFFF) is included in a name set for "Data Name" in the [CollectionData] tab, a setting file cannot be read in version 1.10 or earlier.

Data collection setting (CSV File Data
collector)• If a surrogate pair character (U+10000 to U+10FFFF) is included in a prefix set for "File Name Prefix" or aname set for "Data Name," a setting file cannot be read in version 1.10 or earlier.
• If either of the following data types is set for "Data Type," a setting file cannot be read in version 1.10 or earlier.
STRINGWSTRING• If data that satisfies both of the following conditions is set as a collection target, a setting file cannot be read in
version 1.10 or earlier.
The data type is BIT.
A character string representing ON is not '1,' or one representing OFF is not '0.'

Device instruction feedback setting

If a surrogate pair character (U+10000 to U+10FFFF) is included in a name set for "Data Name" in the[Instruction Target data] tab, a setting file cannot be read in version 1.10 or earlier.

Execution condition setting

If a data diagnosis result is set as multiple monitoring targets, a setting file cannot be read in version 1.10 or
earlier.

IT gateway setting

If an IT gateway setting is created, a setting file cannot be read in version 1.10 or earlier.

Using a setting file, which was created in version 1.22 or later, in version 1.21 or earlier
A setting file cannot be read in version 1.21 or earlier.

626

APPX
Appendix 10 Using a Setting File in a Different Version

Using a setting file, which was created in version 1.24 or later, in version 1.23 or earlier
Function

Consideration

Access target device setting

If there is any access target device setting in which Management Shell Data collector is set, a setting file cannot
be read in version 1.23 or earlier.

Using a setting file, which was created in version 1.26 or later, in version 1.25 or earlier
A setting file cannot be read in version 1.25 or earlier.

Using a setting file, which was created in version 1.27 or later, in version 1.26 or earlier
Function

Consideration

Data distribution setting (MQTT)
Edge application diagnosis (MQTT) setting

If the number of characters in a client ID set for "Client ID at sending" in the [Destination] tab is 65 characters or
more, a setting file cannot be read in version 1.26 or earlier.

Using a setting file, which was created in version 1.28 or later, in version 1.27 or earlier
A setting file cannot be read in version 1.27 or earlier.

Using a setting file in a later version
Using a setting file, which was created in version 1.21 or earlier, in version 1.22 or later
Function

Consideration

Data extraction setting
Execution condition setting

If output data set as a monitoring or comparison target satisfies both of the following conditions, the number ofcharacters in the data is changed to the maximum number*1.
• The data type is STRING or WSTRING.
• The number of characters is less than the maximum number*1.
When it is changed to the maximum number*1, the comparison method for a character string is also changed. For
details, refer to the following:
Page 627 Change of the comparison method for a character string*1

STRING type: 32 characters
WSTRING type: 16 characters

Change of the comparison method for a character string

A

When the number of characters in data set as a monitoring or comparison target is changed to the maximum number, thecomparison method is changed as follows:
Before change
When a character string to be compared begins with a character string to be monitored, it is determined to be a match.
Examples of comparison results are shown below.
Comparison target

Monitoring target

Comparison result

ABC

ABC

Match

ABCDE

ABC

Match

After change
When a character string to be compared is the same as a character string to be monitored, it is determined to be a match.
Examples of comparison results are shown below.
Comparison target

Monitoring target

Comparison result

ABC

ABC

Match

ABCDE

ABC

Mismatch

APPX
Appendix 10 Using a Setting File in a Different Version

627

Management Shell Explorer
Using a setting file in an earlier version
Using a setting file, which was created in version 1.22 or later, in version 1.21 or earlier
Function

Consideration

Component tree edit

If another component with a same name exists in another hierarchy, a setting file cannot be read in version 1.21
or earlier.

Resource list edit

If an internal data tag resource or folder resource is added, a setting file cannot be read in version 1.21 or earlier.

Using a setting file, which was created in version 1.23 or later, in version 1.22 or earlier
Function

Consideration

Resource list edit

If an internal data tag resource (operation) is added, a setting file cannot be read in version 1.22 or earlier.

Using a setting file, which was created in version 1.25 or later, in version 1.24 or earlier
Function

Consideration

One-shot collection

If there are 13 or more one-shot collection settings, a setting file cannot be read in version 1.24 or earlier.

Using a setting file, which was created in version 1.27 or later, in version 1.26 or earlier
Function

Consideration

Access target device setting

If Dummy Data collector is used in an access target device setting, a setting file cannot be read in version 1.26 or
earlier.

One-shot collection

If a one-shot collection setting is newly added or updated, a setting file cannot be read in version 1.26 or earlier.

Using a setting file in a later version
Using a setting file, which was created in version 1.21 or earlier, in version 1.22 or later
Function

Consideration

Resource list edit

Added data tag resources are changed to external data tag resources.

628

APPX
Appendix 10 Using a Setting File in a Different Version

Appendix 11 Added and Changed Functions
This section shows the added and changed functions of Edgecross Basic Software.
Added/changed contents

VersionReferenceManagement Shell is added.

1.10

Page 191 Management Shell

The IT gateway function is added.

1.20

Page 85 IT gateway distribution function
Page 147 Saved file
Page 163 Data Distribution Setting (IT Gateway)
Page 265 IT Gateway Cooperation Function

Real-time Flow Designer• Errors can be cleared.

Page 334 Operation diagnosis

Management Shell• Data in devices, equipment, or lines in production sites can bemonitored.

Page 260 Data monitoringManagement Shell• OPC UA diagnosis can be performed.

Page 341 OPC UA diagnosis

Management Shell• Event histories can be displayed.

Page 344 Event history

The location of use can be searched for.

1.22

Page 122 Location of use search result screen
Page 205 Location of use search result screen

The display language switched in either Real-time Flow Designer orManagement Shell Explorer also applies to the other.

Page 109 Menu configuration
Page 196 Menu configuration

Real-time Flow Manager/Real-time Flow Designer• The maximum numbers of executable data logging flows and data
diagnosis flows are increased.

Page 32 Process flow

Real-time Flow Manager/Real-time Flow Designer• Files can be saved to a folder with the access right set.

Page 60 File saving function
Page 147 Saved fileReal-time Flow Manager/Real-time Flow Designer• The character string data modification function is added.

Page 40 Character string data modification
function
Page 170 Character String Data Modification
SettingReal-time Flow Manager/Real-time Flow Designer• Constants and fixed character strings can be added to collection data.

Page 36 Adding constants and fixed character
strings
Page 140 Collection data

Real-time Flow Designer
Multiple pieces of identical data can be set for a data modification plugin setting.

Page 172 Data Modification Plug-in SettingReal-time Flow Designer• The MQTT communication function is extended.

Page 158 Data Distribution Setting (MQTT)
Page 173 Edge Application Diagnosis (MQTT)
SettingManagement Shell• Data models can be imported and exported.

Page 196 Menu configuration

Management Shell• Folder resources can be added.

Page 192 Data Model
Page 247 Adding a folder resource
Page 248 Editing folder resource properties

Management Shell• Internal data tag resources can be added.

Page 192 Data Model
Page 236 Adding a data tag resource
Page 243 Editing data tag resource properties

CSV File Data collector• The data reading function is added.

Page 297 Data Reading Function

CSV File Data collector• A text file is added.

Page 299 Specifications of a monitoring target fileManagement Shell• The operation function for an internal data tag resource is added.
Management Shell• The one-shot collection function is added.

1.23

A

Page 236 Adding a data tag resource
Page 269 One-shot Collection Function

APPX
Appendix 11 Added and Changed Functions629

Added/changed contents

VersionReferenceReal-time Flow Designer• The number of times of data missing can be displayed in the process
flow diagnostics.

1.24

Page 337 Process flow diagnostics

Management Shell Data collector is added.

Page 314 Management Shell Data collector

The event history automatic output function is added.

Page 86 Event History Automatic Output Function
Page 118 Event history automatic output setting
Page 289 Event History Automatic Output
Function

Management Shell• The maximum number of settings for the one-shot collection function
is increased.
12  32

1.25

Management Shell• A resource can be moved between components.
Real-time Flow Manager/Real-time Flow Designer• Switching to RUN or STOP is available for each process flow.

Page 250 Moving a resource
1.26

Real-time Flow Manager• The command line interface function is added.
Dummy Data collector is added.

Page 20 Management Shell
Page 269 One-shot Collection Function

Page 34 Operational Specifications
Page 333 "Process Flow Start/Stop" screen
Page 92 Command Line Interface Function

1.27

Page 327 Dummy Data collector

Management Shell• A data model can be imported without specifying an access target
device.

Page 200 Behavior of data model importManagement Shell• An access target device setting can be replaced.

Page 217 Access target device setting batch
replacement

Management Shell• The output name of the date and time column can be set in thedetailed setting of the one-shot collection setting.

Page 286 File saving setting
Page 287 DB saving settingReal-time Flow Manager
The number of flows is increased.

1.28

Page 16 Common items for each function
Page 32 Real-time Flow Manager
Page 433 Real-time Flow Manager Status

Windows 11 is supported.

Edgecross Basic Software for Windows
Installation Instructions

Management Shell
IP addresses are supported.

Page 261 Setting an OPC UA server

630

APPX
Appendix 11 Added and Changed Functions

INDEXA

F
Access target device setting . . . . . . . . . . . . . . . 124
Access target device setting function. . . . . . . . . 220
Available character . . . . . . . . . . . . . . . . . . . . . 491

Feedback. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Feedback function . . . . . . . . . . . . . . . . . . . . . . .54
File saving function . . . . . . . . . . . . . . . . . . . . . . .60
Function list of CSV File Data collector . . . . . . . . .29
Function list of Dummy Data collector . . . . . . . . . .29
Function list of Management Shell . . . . . . . . . . . .29
Function list of Management Shell Data collector . . 29
Function list of Real-time Flow Designer . . . . . . . . 28
Function list of Real-time Flow Manager . . . . . . . . 27
Functional specification . . . . . . . . . . . . . . . . . . . .16

C
Character string data modification function . . . . . 40
Character string data modification setting . . . . . 170
Check number of model configurations screen . . 206
Checking method for error descriptions . . . . . . . 329
Checking the status of a process flow . . . . . . . . 332
Checking the status of Management Shell . . . . . 341
Command line interface function . . . . . . . . . . . . . 92
Component tree edit function . . . . . . . . . . . . . . 224
CSV File Data collector . . . . . . . . . . . . . . . . . . 294

I
Icon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .227
Import error list screen . . . . . . . . . . . . . . . . . . .204
IT gateway cooperation function . . . . . . . . . . . . .265
IT gateway diagnosis . . . . . . . . . . . . . . . . . . . .339
IT gateway setting . . . . . . . . . . . . . . . . . . . . . .127

D
Data collection . . . . . . . . . . . . . . . . . . . . . . . . . 32
Data collection function . . . . . . . . . . . . . . . . . . . 36
Data collection setting . . . . . . . . . . . . . . . . . . . 139
Data collector . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Data diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . 32
Data diagnosis flow . . . . . . . . . . . . . . . . . . . . . . 32
Data diagnosis flow setting . . . . . . . . . . . . . . . . 134
Data diagnosis function . . . . . . . . . . . . . . . . . . . 42
Data diagnosis plug-in setting . . . . . . . . . . . . . . 184
Data distribution function . . . . . . . . . . . . . . . . . . 80
Data distribution setting (IT gateway) . . . . . . . . 163
Data distribution setting (MQTT) . . . . . . . . . . . . 158
Data extraction function . . . . . . . . . . . . . . . . . . . 37
Data extraction setting . . . . . . . . . . . . . . . . . . . 169
Data logging flow . . . . . . . . . . . . . . . . . . . . . . . 32
Data logging flow setting . . . . . . . . . . . . . . . . . 130
Data model. . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Data modification . . . . . . . . . . . . . . . . . . . . . . . 32
Data modification function . . . . . . . . . . . . . . . . . 37
Data modification plug-in setting . . . . . . . . . . . . 172
Data storing function . . . . . . . . . . . . . . . . . . . . . 59
Data storing setting (DB saving) . . . . . . . . . . . . 152
Data storing setting (file saving) . . . . . . . . . . . . 142
DB saving function . . . . . . . . . . . . . . . . . . . . . . 77
Device access diagnosis . . . . . . . . . . . . . . . . . 338
Device instruction feedback function . . . . . . . . . . 55
Display format . . . . . . . . . . . . . . . . . . . . . . . . 210
Displaying error information in a list. . . . . . . . . . 343
Dummy Data collector . . . . . . . . . . . . . . . . . . . 327

L
Location of use search result screen . . . . . . 122,205

M
Management Shell . . . . . . . . . . . . . . . . . . . . . .191
Management Shell Data collector . . . . . . . . . . . .314
Management Shell Explorer . . . . . . . . . . . . . . . .193
Monitoring and changing current values of data tag
resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . .207
Monitoring update interval . . . . . . . . . . . . . . . . .211
Move of a process flow . . . . . . . . . . . . . . . . . . .138
MQTT distribution function . . . . . . . . . . . . . . . . . . 80OOne-shot collection function . . . . . . . . . . . . . . . .269
OPC UA connection function . . . . . . . . . . . . . . .259
OPC UA diagnosis . . . . . . . . . . . . . . . . . . . . . .341
Operation diagnosis . . . . . . . . . . . . . . . . . . . . .334
Operational specification . . . . . . . . . . . . . . . . . . .34
Option setting . . . . . . . . . . . . . . . . . . . . . . . . . .216

P
Plug-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Post-diagnosis feedback setting . . . . . . . . . . . . .185
Procedures before operation . . . . . . . . . . . . . . . .30
Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Process flow . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Process flow diagnostics . . . . . . . . . . . . . . . . . .337
Processing performance and processing time . . .567
Program execution feedback function . . . . . . . . . .55

E
Edge application . . . . . . . . . . . . . . . . . . . . . . . . 13
Edge application diagnosis (file) setting . . . . . . . 178
Edge application diagnosis (MQTT) setting . . . . 173
Edgecross Basic Software . . . . . . . . . . . . . . . . . 13
Error code list . . . . . . . . . . . . . . . . . . . . . . . . . 366
Event code list . . . . . . . . . . . . . . . . . . . . . . . . 422
Event history automatic output function . . . . . 86,289

IR
Real-time Flow Designer . . . . . . . . . . . . . . . . . .107
Real-time Flow Manager . . . . . . . . . . . . . . . . . . .32
Real-time Flow Manager diagnosis . . . . . . . . . . .332
Resource list edit function . . . . . . . . . . . . . . . . .235

631

S
Status memory monitor . . . . . . . . . . . . . . . . . . 340
Supported specification version . . . . . . . . . . . . . 14

T
Target device setting import screen. . . . . . . . . . 203
Troubleshooting by symptom . . . . . . . . . . . . . . 345

632

REVISIONS*The document code is given on the bottom right of the front cover of this manual.
Revision date*Document code

Description

May 2018

ECD-MA1-0001-01-EN

First edition

May 2018

ECD-MA1-0001-02-EN

Partial correction

May 2018

ECD-MA1-0001-03-EN

Partial correction

September 2018

ECD-MA1-0001-04-EN

Added or modified parts
TERMS, Section 1.1, Section 1.2, Section 2.1, Section 3.3, Chapter 4, Section 6.7, Section 6.13,
Chapter 7, Section 8.2, Section 9.1, Section 9.3, Section 9.4, Section 9.5, Appendix 2, Appendix 5,
Appendix 6, Appendix 7, Appendix 8, Appendix 9

March 2019

ECD-MA1-0001-05-EN

Added or modified parts
TERMS, Section 1.1, Section 1.2, Section 2.1, Section 3.1, Section 3.2, Section 3.3, Chapter 4,
Section 5.7, Section 6.1, Section 6.2, Section 6.3, Section 6.4, Section 6.5, Section 6.8, Section 6.9,
Section 6.10, Section 6.11, Chapter 7, Section 7.2, Section 7.6, Section 7.7, Section 8.2, Section 8.5,
Section 9.1, Section 9.2, Section 9.3, Section 9.4, Section 9.5, Section 9.6, Appendix 1, Appendix 2,
Appendix 6, Appendix 8, Appendix 9

July 2019

ECD-MA1-0001-06-EN

Partial correction

December 2019

ECD-MA1-0001-07-EN

Added or modified parts
TERMS, Section 1.1, Section 1.2, Section 2.1, Section 3.1, Section 3.2, Section 3.3, Chapter 4,
Section 5.1, Section 5.2, Section 5.3, Section 5.4, Section 5.6, Section 5.7, Section 6.1, Section 6.2,
Section 6.3, Section 6.4, Section 6.5, Section 6.7, Section 6.8, Section 6.10, Section 6.11, Section
6.13, Section 6.14, Section 6.15, Section 6.17, Section 7.1, Section 7.2, Section 7.3, Section 7.4,
Section 7.5, Section 7.6, Section 7.7, Section 8.1, Section 8.2, Section 8.3, Section 8.4, Section 8.5,
Section 8.6, Section 8.7, Section 8.8, Section 9.1, Section 9.2, Section 9.3, Section 9.4, Section 9.5,
Section 9.6, Section 9.7, Appendix 1, Appendix 2, Appendix 3, Appendix 5, Appendix 6, Appendix 7,
Appendix 9, Appendix 10

November 2020

ECD-MA1-0001-08-EN

Added or modified parts
Section 1.2, Section 2.1, Section 3.3, Section 6.8, Section 7.1, Section 7.2, Section 7.5, Section 7.8,
Section 8.6, Section 8.7, Section 9.4, Section 9.5, Section 9.8, Appendix 2, Appendix 7, Appendix 9,
Appendix 10

May 2021

ECD-MA1-0001-09-EN

Added or modified parts
Section 2.1, Section 3.1, Section 3.3, Section 3.5, Chapter 4, Section 5.6, Section 5.7, Section 5.8,
Section 6.1, Section 6.9, Section 6.10, Section 6.15, Section 7.2, Section 7.6, Section 7.9, Chapter 9,
Section 10.1, Section 10.2, Section 10.3, Section 10.4, Section 10.5, Section 10.6, Appendix 1,
Appendix 2, Appendix 5, Appendix 7, Appendix 8, Appendix 9, Appendix 10

November 2021

ECD-MA1-0001-10-EN

Added or modified parts
Section 2.1, Section 6.1, Section 7.5, Section 7.8, Section 10.4, Appendix 2, Appendix 7, Appendix
9, Appendix 10

July 2022

ECD-MA1-0001-11-EN

Added or modified parts
SAFETY PRECAUTIONS, Section 3.1, Section 3.2, Chapter 4, Section 5.1, Section 5.3, Section 5.4,
Section 5.6, Section 5.7, Section 5.9, Section 6.1, Section 6.2, Section 6.3, Section 6.4, Section 6.5,
Section 7.8, Section 8.4, Section 8.5, Section 10.1, Section 10.2, Section 10.4, Section 10.5, Section
10.6, Section 10.9, Appendix 1, Appendix 7, Appendix 9, Appendix 10

December 2022

ECD-MA1-0001-12-EN

Added or modified parts
Section 1.1, Section 2.1, Section 3.6, Section 6.10, Section 6.15, Section 7.2, Section 7.6, Section
7.8, Chapter 10, Section 11.3, Section 11.4, Section 11.5, Section 11.7, Section 11.8, Appendix 2,
Appendix 3, Appendix 7, Appendix 10, Appendix 11

June 2023

ECD-MA1-0001-13-EN

Added or modified parts
Section 2.1, Chapter 5, Section 5.9, Section 6.1, Section 7.6, Section 7.8, Chapter 9, Section 11.2,
Section 11.3, Section 11.4, Appendix 1, Appendix 2, Appendix 8, Appendix 10, Appendix 11

October 2023

ECD-MA1-0001-14-EN

Added or modified parts
Section 5.4, Section 6.1, Section 11.5, Appendix 3, Appendix 9

November 2023

ECD-MA1-0001-15-EN

Added or modified parts
Section 5.4, Appendix 3

Japanese manual number: ECD-MA1-0001-15-JA
This manual confers no industrial property rights or any rights of any other kind, nor does it confer any patent licenses. Mitsubishi Electric Corporation cannot
be held responsible for any problems involving industrial property rights which may occur as a result of using the contents noted in this manual.

2018 Edgecross Consortium

633

USER REGISTRATION REQUESTThe latest software information will be delivered to registered users.
Please download and apply the Edgecross related product user registration application and registration
information change application form from the web.
https://www.edgecross.org/en/data-download/ÜInformation on Edgecross Market PlaceÜ
You can search and purchase applications according to your purpose from various edge applications. It is also
possible to purchase support packs.
Please see the website for details.
https://www.marketplace.edgecross.org

ÜInformation on admission to Edgecross ConsortiumÜ
If you join Edgecross consortium, you can get the latest technical documents and specifications about
Edgecross for free. You can also interact with member companies through sectional activities and various
events.
Please see the website for details.
https://www.edgecross.org/

TRADEMARKS
Core, Intel, and Intel Atom are either registered trademarks or trademarks of Intel Corporation in the United States and/or
other countries.
Microsoft, Visual C++, Visual Studio, and Windows are trademarks of the Microsoft group of companies.
The company names, system names and product names mentioned in this manual are either registered trademarks ortrademarks of their respective companies.
In some cases, trademark symbols such as '' or '' are not specified in this manual.

COPYRIGHTSThe screens (screenshots) are used in accordance with the Microsoft Corporation guideline.
For the open source software used in this product, refer to the following:
Page 599 Software Licenses

634

Inquiries regarding purchase and support
Please contact the inquiry counter of Edgecross Consortium or the vendor of this product for consultation to purchase andsupport the software.
Edgecross Consortium inquiry counter (Only Japanese is supported.)
https://www.edgecross.org/ja/contact/form/

Created in November 2023
Specification subject to change without notice.