SH 081919 Engj

Download as pdf or txt
Download as pdf or txt
You are on page 1of 120

SLMP Data Collector

User's Manual

-SW1DND-DCSLMP-M
-SW1DND-DCSLMP-MD
-SW1DNN-DCSLMP-M
SAFETY PRECAUTIONS
(Read these precautions before using this product.)
Before using this product, please read this manual and the relevant manuals carefully and pay full attention to safety to handle
the product correctly.
The precautions given in this manual are concerned with this product only. For the safety precautions of the programmable
controller system, refer to the MELSEC iQ-R Module Configuration Manual.
In this manual, the safety precautions are classified into two levels: " WARNING" and " CAUTION".

Indicates that incorrect handling may cause hazardous conditions, resulting in


WARNING death or severe injury.

Indicates that incorrect handling may cause hazardous conditions, resulting in


CAUTION minor 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 as
a 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 the
safety side. Additionally, read this manual carefully and ensure the safety before operations.
Especially, in the above mentioned operations that are performed from external devices through
network, 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
 During application of each setting, 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.

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

2
CONDITIONS OF USE FOR THE PRODUCT
(1) This software shall be used under the following conditions;
i) that any failure occurred in this software, if any, shall not lead to any serious accident.
ii) that the backup and/or fail-safe functions are systematically performed outside the devices in the cases of any failure
occurred in this software.
(2) Mitsubishi Electric assumes no responsibility and liability (including but not limited to, default liability, defect liability,
quality assurance responsibility, tort liability, product liability) for the quality, performance, and safety of both this
software and products using this software.
(3) Mitsubishi Electric 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.

INTRODUCTION
Thank you for purchasing SLMP Data Collector.
This manual describes the specifications, procedures before operation, and troubleshooting of this product.
Before using this product, please read this manual and the relevant manuals carefully, and develop familiarity with the
functions and performance of this product to handle correctly.
Please make sure that the end users read this manual.
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.

3
CONTENTS
SAFETY PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
CONDITIONS OF USE FOR THE PRODUCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
RELEVANT MANUALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
TERMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

CHAPTER 1 SLMP Data Collector 8

CHAPTER 2 SPECIFICATIONS 10
2.1 SLMP Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Functional specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Operational specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Access methods and available commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Accessible devices (equipment), devices (locations), and device numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.2 MELSEC Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Functional specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Operational specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Accessible CPU modules and devices (locations) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

CHAPTER 3 PROCEDURE BEFORE OPERATION 21


3.1 Setting Example for an Access Target Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.2 Procedures for Using SLMP Data Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Real-time Flow Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Management Shell. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

CHAPTER 4 FUNCTIONS 29
4.1 Data Collection Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.2 Data Reading Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.3 Data Writing Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.4 Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

CHAPTER 5 PARAMETER SETTINGS 38


5.1 SLMP Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Communication parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Collection parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Location parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
5.2 MELSEC Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Communication parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Collection parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Location parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

CHAPTER 6 TROUBLESHOOTING 58
6.1 Checking Method for Error Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Error type. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
6.2 Troubleshooting by Symptom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Troubleshooting on the SLMP Data Collector startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Troubleshooting on data reading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Troubleshooting on data writing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

4
Troubleshooting on Ethernet communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Troubleshooting on parameter settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Troubleshooting on Edgecross Basic Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Troubleshooting on screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
6.3 Error Code List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
6.4 Event Code List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

APPENDIX 82
Appendix 1 Processing Performance and Processing Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

CONTENTS
Collection processing performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Read processing performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Appendix 2 Data Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Data assignment availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Number of device points to be assigned to data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Appendix 3 Software Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Software information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Appendix 4 Supported Edgecross Basic Software Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Appendix 5 Added and Changed Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

INDEX 114

REVISIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
INFORMATION AND SERVICES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
TRADEMARKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
COPYRIGHTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

5
RELEVANT MANUALS
Manual name [manual number] Description Available form
SLMP Data Collector User's Manual Specifications, procedure before operation, and troubleshooting of SLMP Data e-Manual
[SH-081919ENG] (this manual) Collector PDF

e-Manual refers to the Mitsubishi Electric FA electronic book manuals that can be browsed using a dedicated
tool.
e-Manual has the following features:
• Required information can be cross-searched in multiple manuals.
• Other manuals can be accessed from the links in the manual.
• Hardware specifications of each part can be found from the product figures.
• Pages that users often browse can be bookmarked.
• Sample programs can be copied to an engineering tool.

6
TERMS
Unless otherwise specified, this manual uses the following terms.
Term Description
3E frame One of the message formats for MC protocol.
'ST type (Single-Transmission)' is the name used by the CC-Link Partner Association for this term.
4E frame One of the message formats for MC protocol.
'MT type (Multi-Transmission)' is the name used by CC-Link Partner Association for this term.
Data model management A function that abstracts devices, equipment, and lines in the production site and hierarchically manages them
Device A device (X, Y, W, or others) in SLMP-compatible devices or CPU modules on another station
Device code A device type.
'Memory type' is the name used by CC-Link Partner Association for this term.
Device number An index number for a device.
'Memory number' is the name used by CC-Link Partner Association for this term.
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
Edgecross A 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
Host station A station that is directly connected to the industrial PC where SLMP Data Collector is running
Industrial PC A PC specialized for industrial use with features such as high reliability, environmental resistance, and long-term supply
Location Device memory that can be accessed by SLMP Data Collector
Location parameter A parameter for setting the device memory that can be accessed by SLMP Data Collector
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
MELSEC connection A connection to a MELSEC device
MELSEC device A generic term for the following:
• MELSEC iQ-R series
• MELSEC iQ-F series
• MELSEC-Q series
• MELSEC-L series
Other station A station on the network to which the host station is connected
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
Request destination module I/O No. A multiple CPU number.
'Request destination station processor number' is the name used by CC-Link Partner Association for this term.
SLMP An abbreviation for Seamless Message Protocol.
This protocol is used to access from an external device to an SLMP-compatible device or a programmable controller
connected to an SLMP-compatible device.
SLMP connection A connection to an SLMP-compatible device, that is equipped with the sever function, other than a MELSEC device

7
1 SLMP Data Collector
SLMP Data Collector is a software component that performs the data collection, data reading, and data writing functions to a
MELSEC device or an SLMP-compatible device other than MELSEC devices connected via Ethernet.
Data in a MELSEC device or an SLMP-compatible device other than MELSEC devices can be collected and updated by using
SLMP Data Collector in combination with Edgecross Basic Software.
For details on Edgecross Basic Software, refer to the following:
Edgecross Basic Software for Windows User's Manual

1 SLMP Data Collector


8
MEMO
1

1 SLMP Data Collector


9
2 SPECIFICATIONS
This chapter shows the specifications of SLMP Data Collector.

2.1 SLMP Connection


This section shows the specifications for an SLMP connection.

Functional specifications
The following table shows the functional specifications for an SLMP connection.
Item Specification
Function • Data collection function
• Data reading function/Data writing function
Data collection function Maximum number of process flow settings 32
Maximum number of data sets for one process flow 256
Maximum collectible size for one process flow 8192 (word)
Collection interval • 100 to 900 (ms)
• 1 to 3600 (s)
Input data type*2 • BOOL (Bit value)
• INT (Signed 16-bit integer value)
• UINT (Unsigned 16-bit integer value)
• DINT (Signed 32-bit integer value)
• UDINT (Unsigned 32-bit integer value)
• LINT (Signed 64-bit integer value)
• ULINT (Unsigned 64-bit integer value)
• REAL (32-bit real number value)
• LREAL (64-bit real number value)
• STRING (Character string: UTF-8 (1 to 32 characters))
• WSTRING (Wide-character string: Unicode (UTF-16LE) (1 to
16 characters))
Data reading function/Data Maximum number of settings *1
writing function *2
Input and output data type • BOOL (Bit value)
• INT (Signed 16-bit integer value)
• UINT (Unsigned 16-bit integer value)
• DINT (Signed 32-bit integer value)
• UDINT (Unsigned 32-bit integer value)
• LINT (Signed 64-bit integer value)
• ULINT (Unsigned 64-bit integer value)
• REAL (32-bit real number value)
• LREAL (64-bit real number value)
• STRING (Character string: UTF-8 (1 to 32 characters))
• WSTRING (Wide-character string: Unicode (UTF-16LE) (1 to
16 characters))

*1 For the maximum number, refer to the following:


Edgecross Basic Software for Windows User's Manual
*2 For details on data types, refer to the following:
Edgecross Basic Software for Windows User's Manual

2 SPECIFICATIONS
10 2.1 SLMP Connection
Operational specifications
The following shows the operational specifications for an SLMP connection.

Operating status
The status of SLMP Data Collector varies for each access target and is determined according to the communication status 2
with the targets.
The communication status with access targets can be checked in Edgecross Basic Software.
Status of SLMP Data Collector Description Communication status with an
access target
Data is being read from or written to an access target. Data Collector and the access target are connected Connected
normally. (It will be in this state when the connection
processing succeeds.)
Data is not being read from or written to an access target. Data Collector and the access target are disconnected. Disconnected
(Reconnection is in progress.) (It will be in this state when the connection processing
fails.)

Behavior when an error occurs


When SLMP Data Collector detects an error, it behaves according to the error type as follows:
Error type Status of SLMP Data Collector Behavior of SLMP Data Collector
Data collector operation stop error • Operations according to the specifications cannot be • Discards collected data when this error occurs during
guaranteed due to a hard disk error in an industrial data collection.
PC of the installation destination or a failure of • Stops the data collection, data reading, or data
resource securing. writing function and reports this error to Edgecross
• An error cannot be corrected even by changing the Basic Software.
network configuration due to an incorrect parameter
setting (device type out of range, for example).
Data collector operation continuation error • Operations such as a program execution or data • Discards collected data when this error occurs during
communication cannot be continued due to data collection.
temporary network failure. • Continues the data collection, data reading, or data
• An error may be corrected by changing the network writing function even after reporting this error to
configuration even though there is no Edgecross Basic Software.
communication due to a mismatch between the
parameter settings and the network configuration.

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

2 SPECIFICATIONS
2.1 SLMP Connection 11
Access methods and available commands
The following shows the access methods and available commands.

Access methods
The following shows the access methods.
: Available : Not available
Item Specification Availability
Communication method TCP 
UDP 
Communication frame 4E frame 
3E frame 
Data code Binary 
ASCII 

Since the access methods above may not be available depending on devices, check the available access
methods in the manuals of the devices.

Available commands
The following shows the available commands.
For details on the request message format for each command, refer to the following:
Page 13 Request message format
"Command" in the communication Corresponding request message
parameters Command Subcommand*1
Random read/write (16-bit) 0403H: Read Random 0000H (word units)
1402H: Write Random 0000H (word units)
0001H (bit units)
Random read/write (32-bit) 0403H: Read Random 0002H (word units)
1402H: Write Random 0002H (word units)
0003H (bit units)

*1 An extension specification is not supported.


For details on each command, refer to the following:
SLMP Reference Manual

The above commands and subcommands of the request messages may not be supported depending a
device. Check the manual for the device before setting communication parameters, and set a command and
subcommand supported by the device.

2 SPECIFICATIONS
12 2.1 SLMP Connection
Request message format
The following shows the request message format for each command.
For details on the formats, refer to the following:
SLMP Reference Manual
Read Random

ÒCommunication frame 2

Header Subheader ÓRequest ÔRequest ÕRequest Request Request Ö Request data Footer
destination destination destination destination data Monitoring
network station No. module I/O multidrop length timer × ØSub- Data
No. No. station No. Command command
(00H fixed)

Double- Word access


Word word
access ÙDevice
access ÙDevice
points code ÚDevice No. ÚDevice No.
points code

1 point 1 point

1 point 1 point

Double-word access

ÙDevice ÙDevice
ÚDevice No. ÚDevice No.
code code

Specify the devices for the specified number of points.

• Changing settings for the items in a request message


By changing settings for the following items in the communication parameters and the location parameters, corresponding
settings for the items in a request message can be changed.
Parameter Item Corresponding item in a request
message
Communication parameters Communication frame 4E (Binary) Communication frame
(Page 38 Communication
3E (Binary)
parameters)
4E (ASCII)
3E (ASCII)
Request destination network No. Request destination network No.
Request destination station No. Request destination station No.
Request destination module I/O No. Request destination module I/O No.
Time-out Time Monitoring timer
Command Random read/write (16-bit) Command
Subcommand (0000 to 0003)
Random read/write (32-bit)
Location parameters Device code Device code
(Page 45 Location
Device number Device No.
parameters)

2 SPECIFICATIONS
2.1 SLMP Connection 13
Write Random

ÒCommunication frame

Header Subheader ÓRequest ÔRequest ÕRequest Request Request Ö Request data Footer
destination destination destination destination data Monitoring
network station No. module I/O multidrop length timer × ØSub- Data
No. No. station No. Command command
(00H fixed)

When writing data in bit units

Specify the devices for the specified number of points.

Number
of bit ÙDevice Set/ ÙDevice Set/
ÚDevice No. ÚDevice No.
access code reset code reset
points

1 point 1 point

When writing data in word units

Specify the devices for the specified number of points.

When Double-
writing Word access
word
data in access ÙDevice
word code ÚDevice No. Write data
points
units

1 point

1 point

Double-word access
ÙDevice
code ÚDevice No. Write data

Specify the devices for the specified number of points.

• Changing settings for the items in a request message


Refer to the following:
Changing settings for the items in a request message

2 SPECIFICATIONS
14 2.1 SLMP Connection
Accessible devices (equipment), devices (locations), and device
numbers
The following shows the accessible devices (equipment), devices (locations), and device numbers.

Accessible devices (equipment) 2


SLMP Data Collector can connect to SLMP-compatible devices that have the server function.
However, only the devices that satisfy both of the following conditions can be accessed.
 Devices supporting access methods and available commands shown in the following sections.
Page 12 Access methods
Page 12 Available commands
 Devices other than MELSEC iQ-R, MELSEC-Q, or MELSEC-L series*1
*1 To MELSEC iQ-R, MELSEC-Q, and MELSEC-L series devices, access by a MELSEC connection.

Precautions
Only the connected station (host station) can be accessed.

Accessible devices (locations)


For accessible devices (locations), check the manual for each device to be accessed.
For the device type and device code in the location parameter, check the specifications of a device to be accessed before
setting.
When the location parameter settings are not compliant with the specifications of a device to be accessed, the device cannot
be accessed normally.
If the combination of a device type and device code does not match among multiple location parameters used for a same
access target device, a location parameter setting error (error code: 1A14H) occurs due to incorrect settings.
To set multiple devices with a same device code as access targets, match the case in the device code.

Accessible device numbers


For accessible device numbers, check the manual for each device to be accessed.

2 SPECIFICATIONS
2.1 SLMP Connection 15
2.2 MELSEC Connection
This section shows the specifications for a MELSEC connection.

Functional specifications
The following table shows the functional specifications for a MELSEC connection.
Item Specification
Access target device Connectable path Personal computer side I/F Ethernet board (UDP used)
Programmable controller side I/F • CPU module (No another station specified)
• Ethernet module (another module (single network))
Function • Data collection function
• Data reading function/Data writing function
Data collection function Maximum number of process flow settings *1
Maximum number of data sets for one process flow 256
Maximum collectible size for one process flow 8192 (word)
Collection interval • 100 to 900 (ms)
• 1 to 3600 (s)
Input data type*2 • BOOL (Bit value)
• INT (Signed 16-bit integer value)
• UINT (Unsigned 16-bit integer value)
• DINT (Signed 32-bit integer value)
• UDINT (Unsigned 32-bit integer value)
• LINT (Signed 64-bit integer value)
• ULINT (Unsigned 64-bit integer value)
• REAL (32-bit real number value)
• LREAL (64-bit real number value)
• STRING (Character string: UTF-8 (1 to 32 characters))
• WSTRING (Wide-character string: Unicode (UTF-16LE) (1 to
16 characters))
Data reading function/Data Maximum number of settings *1
writing function
Input and output data type*2 • BOOL (Bit value)
• INT (Signed 16-bit integer value)
• UINT (Unsigned 16-bit integer value)
• DINT (Signed 32-bit integer value)
• UDINT (Unsigned 32-bit integer value)
• LINT (Signed 64-bit integer value)
• ULINT (Unsigned 64-bit integer value)
• REAL (32-bit real number value)
• LREAL (64-bit real number value)
• STRING (Character string: UTF-8 (1 to 32 characters))
• WSTRING (Wide-character string: Unicode (UTF-16LE) (1 to
16 characters))

*1 For the maximum number, refer to the following:


Edgecross Basic Software for Windows User's Manual
*2 For details on data types, refer to the following:
Edgecross Basic Software for Windows User's Manual

Operational specifications
For the operational specifications for a MELSEC connection, refer to the following:
Page 11 Operational specifications

2 SPECIFICATIONS
16 2.2 MELSEC Connection
Accessible CPU modules and devices (locations)
The following shows the accessible CPU modules and devices (locations).

Accessible CPU modules


Series Model name 2
RCPU Programmable controller R00CPU, R01CPU, R02CPU, R04CPU, R04ENCPU, R08CPU, R08ENCPU, R16CPU, R16ENCPU,
CPU R32CPU, R32ENCPU, R120CPU, R120ENCPU
Process CPU R08PCPU, R16PCPU, R32PCPU, R120PCPU
Safety CPU R08SFCPU, R16SFCPU, R32SFCPU, R120SFCPU
C Controller module R12CCPU-V
FXCPU Programmable controller FX5UCPU, FX5UCCPU
CPU
QCPU (Q mode) Programmable controller Q00UJCPU, Q00UCPU, Q01UCPU, Q02UCPU, Q03UDCPU, Q03UDECPU, Q03UDVCPU,
CPU Q04UDHCPU, Q04UDEHCPU, Q04UDVCPU, Q06UDHCPU, Q06UDEHCPU, Q06UDVCPU,
Q10UDHCPU, Q10UDEHCPU, Q13UDHCPU, Q13UDEHCPU, Q13UDVCPU, Q20UDHCPU,
Q20UDEHCPU, Q26UDHCPU, Q26UDEHCPU, Q26UDVCPU, Q50UDEHCPU, Q100UDEHCPU
Process CPU Q02PHCPU, Q04UDPVCPU, Q06PHCPU, Q06UDPVCPU, Q12PHCPU, Q13UDPVCPU,
Q25PHCPU, Q26UDPVCPU
C Controller module*1 Q12DCCPU-V*2, Q24DHCCPU-V, Q24DHCCPU-LS, Q24DHCCPU-VG, Q26DHCCPU-LS
LCPU Programmable controller L02SCPU, L02CPU, L06CPU, L26CPU, L26CPU-BT
CPU

*1 It is not accessible in the direct connection via an Ethernet port.


*2 In the basic mode, it is accessible for only ones with a serial number of which the first five digits is '12042' or higher.

Precautions
• Devices in a single network can only be accessed. (Devices cannot be accessed via co-existence network.)
• It may be possible to connect to a device not included in the accessible CPU module list, however, it is not guaranteed.
• Access target devices to which remote passwords are set cannot be accessed.

2 SPECIFICATIONS
2.2 MELSEC Connection 17
Accessible devices (locations)
The following table shows the accessible devices (locations).
: Accessible, : Not accessible, : No device
Device name (device)*1 Type Access target type (series) Base
RCPU*2 FXCPU QCPU (Q mode)*2 LCPU
Programm C Programm Programm C Programm
able Controller able able Controller able
controller module controller controller module controller
CPU, CPU CPU, CPU
process process
CPU, CPU
safety CPU
Special relay (SM) Bit     *3  10
Special register (SD) Word     *3  10
Input relay (X) Bit     *3  16*4
*3
Output relay (Y) Bit       16*4
Internal relay (M) Bit     *3  10
Latch relay (L) Bit       10
Annunciator (F) Bit       10
Edge relay (V) Bit       10
Link relay (B) Bit     *5  16
Data register (D) Word     *3  10
*5
Link register (W) Word       16
Timer Contact (TS) Bit       10
Coil (TC) Bit       10
Current value Word       10
(TN)
Retentive Contact (STS) Bit       10
timer
Coil (STC) Bit       10
Current value Word       10
(STN)
Counter Contact (CS) Bit       10
Coil (CC) Bit       10
Current value Word       10
(CN)
Link special relay (SB) Bit       16
Link special register (SW) Word       16
Index register (Z) Word       10
(V)        10
Long index register (LZ) Double word       10
File register (R) Word    *6   10
(ZR) Word    *6   10
Extension file (ERn\R)        10
register
Link direct Link input (Jn\X) Bit       16
device
Link output Bit       16
(Jn\Y)
Link relay (Jn\B) Bit       16
Link special Bit       16
relay (Jn\SB)
Link register Word       16
(Jn\W)
Link special Word       16
register (Jn\SW)

2 SPECIFICATIONS
18 2.2 MELSEC Connection
Device name (device)*1 Type Access target type (series) Base
RCPU*2 FXCPU QCPU (Q mode)*2 LCPU
Programm C Programm Programm C Programm
able Controller able able Controller able
controller module controller controller module controller
CPU, CPU CPU, CPU
process process 2
CPU, CPU
safety CPU
Module Module access Word    *7   10
access device device/
intelligent
function module
device (Un\G)
Multiple CPU Word       10
shared device
(U3En\G)
CPU buffer CPU buffer Word       10
memory memory access
access device device
(U3En\G)
CPU buffer Word *8      10
memory access
device (fixed
cycle
communication
area)
(U3En\HG)
Step relay (S) Bit       10
Long timer Contact (LTS) Bit       10
Coil (LTC) Bit       10
Current value Double word       10
(LTN)
Long retentive Contact (LSTS) Bit       10
timer
Coil (LSTC) Bit       10
Current value Double word       10
(LSTN)
Long counter Contact (LCS) Bit       10
Coil (LCC) Bit       10
Current value Double word       10
(LCN)
Function input (FX) Bit       16
Function output (FY) Bit       16
Function register (FD) Word       10
Direct input (DX) Bit       16
Direct output (DY) Bit       16
Refresh data register (RD) Word       10
Safety input (SA\X) Bit       16
Safety output (SA\Y) Bit       16
Safety internal relay (SA\M) Bit       10
Safety link relay (SA\B) Bit       16
Safety timer Contact (SA\TS) Bit       10
Coil (SA\TC) Bit       10
Current value Word       10
(SA\TN)
Safety Contact Bit       10
retentive timer (SA\STS)
Coil (SA\STC) Bit       10
Current value Word       10
(SA\STN)

2 SPECIFICATIONS
2.2 MELSEC Connection 19
Device name (device)*1 Type Access target type (series) Base
RCPU*2 FXCPU QCPU (Q mode)*2 LCPU
Programm C Programm Programm C Programm
able Controller able able Controller able
controller module controller controller module controller
CPU, CPU CPU, CPU
process process
CPU, CPU
safety CPU
Safety Contact Bit       10
counter (SA\CS)
Coil (SA\CC) Bit       10
Current value Word       10
(SA\CN)
Safety data register (SA\D) Word       10
Safety link register (SA\W) Word       16
Safety special relay (SA\SM) Bit       10
Safety special register (SA\SD) Word       10

*1 Even if specifying the program name, local devices and file registers that are set for each program cannot be accessed. Do not use local
devices and file registers that are set for each program because they may not be read or written correctly.
*2 When the access target device is a C Controller module and if "Device Type" of the communication parameters is set as shown below,
the devices that are not supported by the C Controller module ("" and "" in the table above) can be set as the access target;
however, they cannot be accessed.
RCPU: MELSEC iQ-R (Programmable controller CPU/Process CPU/Safety CPU)
QCPU (Q mode): MELSEC-Q (Programmable controller CPU/Process CPU)
*3 For Q12DCCPU-V (basic mode), select "Use device function" in a tool for a C Controller module.
*4 It will be the octal notation when a connected device is an FXCPU.
*5 For Q12DCCPU-V, this device can be accessed from Q12DCCPU-V (extended mode).
*6 This device cannot be accessed from Q00UJCPU.
*7 In a multiple CPU configuration, this device cannot be read from the shared memory in the host CPU. In addition, this device cannot be
written to the shared memory regardless of the host CPU and other CPUs.
*8 The device are not included in RnENCPUs and RnSFCPUs.

2 SPECIFICATIONS
20 2.2 MELSEC Connection
3 PROCEDURE BEFORE OPERATION
This chapter shows the procedure from start-up to operation of SLMP Data Collector.

Operating procedure
1. Install SLMP Data Collector in an industrial PC in which Edgecross Basic Software is installed.
For the installation procedure and the operating environment of SLMP Data Collector, refer to the following:
SLMP Data Collector Installation Instructions 3

To use SLMP Data Collector version 1.02C or later, Edgecross Basic Software version 1.10 or later is
required.

2. Configure the settings and wirings for a MELSEC device or an SLMP-compatible device other than MELSEC devices
and connect the device to the industrial PC.
For the methods, refer to the manuals for the SLMP-compatible or MELSEC device and the industrial PC used.
For a setting example for an access target device, refer to the following:
Page 22 Setting Example for an Access Target Device
3. Start the operation of SLMP Data Collector.
Page 24 Procedures for Using SLMP Data Collector

Precautions
When running Data Collector on an industrial PC where an antivirus software is installed, an exceeded collection cycle or data
missing may occur due to an operation of the antivirus software. Exclude the following from the monitoring targets in the
antivirus software settings. For the setting methods, refer to the manual for each antivirus software.
• Data Collector installation destination folder
• Following files and folders of Windows
Pagefile.sys
*.pst
%systemroot%\System32\Spool
%systemroot%\SoftwareDistribution\Datastore
%windir%\Security\Database
%allusersprofile%\NTUser.pol
%systemroot%\system32\GroupPolicy\Machine\registry.pol
%systemroot%\system32\GroupPolicy\User\registry.pol

3 PROCEDURE BEFORE OPERATION


21
3.1 Setting Example for an Access Target Device

Procedure for setting an SLMP-compatible device


The following shows the setting procedure for using a GOT2000 as an SLMP-compatible device.
For details, refer to the following:
GT Designer3 (GOT2000) Screen Design Manual
GOT2000 Series Connection Manual (Microcomputers, MODBUS/Fieldbus Products, Peripherals) For GT Works3
Version1

Operating procedure
1. Open a project for a GOT2000 in GT Designer3.
2. Select [Common]  [Controller Setting].

3. Select a channel to be used.

4. Set a connection destination.

5. Set each item in "Detail Setting".


Set "TCP/IP" for "Protocol".
For "Format", set a value as follows according to the communication frame and data code to be used.
• When the communication frame is '4E' and the data code is 'ASCII': 6
• When the communication frame is '4E' and the data code is 'Binary': 7
• When the communication frame is '3E' and the data code is 'ASCII': 8
• When the communication frame is '3E' and the data code is 'Binary': 9

6. Click the [OK] button.

7. Write the set parameters to the GOT2000.

8. Restart the GOT2000.

3 PROCEDURE BEFORE OPERATION


22 3.1 Setting Example for an Access Target Device
Procedure for setting a MELSEC device
The following shows the setting procedure for using an R04CPU as a MELSEC device.

Operating procedure
1. Open a project for an R04CPU in GX Works3.

2. Select [View]  [Docking Window]  [Navigation].

3. Double-click "Parameter"  "R04CPU"  "Module Parameter" in the "Navigation" window.


3
4. Select "Basic Settings"  "Own Node Settings"  "IP Address"  "IP Address", and set an IP address.

5. Click the [Apply] button.

6. Write the set parameters to the R04CPU, and restart it.

Precautions
When using a MELSEC iQ-F, MELSEC-Q, and MELSEC-L series device as a MELSEC device, set the number of required
MELSOFT connection devices in the parameter setting.
For the setting method, refer to the manual for each module.

3 PROCEDURE BEFORE OPERATION


3.1 Setting Example for an Access Target Device 23
3.2 Procedures for Using SLMP Data Collector
This section shows the procedures for using SLMP Data Collector in Real-time Flow Manager and Management Shell.
For details, refer to the following:
Edgecross Basic Software for Windows User's Manual

Real-time Flow Manager


The following shows the procedure for using SLMP Data Collector in Real-time Flow Manager.

Operating procedure
1. Start Real-time Flow Designer.

2. Select "Target Device Setting" in the edit item tree.

3. Select a blank row in the access target device setting list, and click the [Edit] button.

4. Select SLMP Data Collector in the "Select Data collector" screen, and click the [OK] button.

5. Set communication parameters.


• SLMP connection (Page 38 Communication parameters)
• MELSEC connection (Page 52 Communication parameters)

To communicate with multiple access target devices, configure the target device settings for all the devices.

6. Click the [OK] button.

7. Click "Data Logging Flow Setting" in the edit item tree.

8. Click the [Edit] button.

3 PROCEDURE BEFORE OPERATION


24 3.2 Procedures for Using SLMP Data Collector
9. Click the button in the "Detailed Setting" column.

10. Select "Target Device" in the "Data Collection Setting" screen.


Select the access target device set in step 3 to 6.

11. Set location parameters in the [Collection Data] tab.

• For an SLMP connection, refer to the following:


Page 45 Location parameters
• For a MELSEC connection, directly enter accessible devices (locations) listed in the following:
Page 18 Accessible devices (locations)

12. Set collection parameters in the [Collection Option] tab.


• For an SLMP connection, refer to the following:
Page 44 Collection parameters
• For a MELSEC connection, refer to the following:
Page 54 Collection parameters
13. Click the [OK] button in the "Data Collection Setting" screen.
14. Click the [OK] button in the "Data Logging Flow Setting" screen.
A data logging flow setting is created.

To execute multiple process flows, configure the process flow settings for all the flows.

15. Change the operating status of Real-time Flow Manager to RUN, and execute the created process flow.
For changing the operating status of Real-time Flow Manager, refer to the following:
Edgecross Basic Software for Windows User's Manual

3 PROCEDURE BEFORE OPERATION


3.2 Procedures for Using SLMP Data Collector 25
Management Shell
The following shows the procedure for using SLMP Data Collector in Management Shell.
In this procedure, the data tag resource monitor window of Management Shell Explorer is used.

Operating procedure
1. Start Management Shell Explorer.

2. Select [Setting]  [Target Device Setting].

3. Select a blank row in the access target device setting list, and click the [Edit] button.

4. Select SLMP Data Collector in the "Select Data collector" screen, and click the [OK] button.

5. Set communication parameters.


• SLMP connection (Page 38 Communication parameters)
• MELSEC connection (Page 52 Communication parameters)

6. Click the [OK] button.

To communicate with multiple access target devices, configure the target device settings for all the devices.

7. Select [Window]  [Resource List Edit].

3 PROCEDURE BEFORE OPERATION


26 3.2 Procedures for Using SLMP Data Collector
8. Select the icon for adding an external data tag resource ( ).

9. Set a name for "Data Tag Resource Name" and "Resource Display Name".

10. Select "Target Device".


Select the access target device set in step 3 to 6.

11. Set location parameters.

• For an SLMP connection, refer to the following:


Page 45 Location parameters
• For a MELSEC connection, directly enter accessible devices (locations) listed in the following:
Page 18 Accessible devices (locations)
12. Click the [OK] button.

To monitor multiple external data tag resources, add all the external data tag resources.

3 PROCEDURE BEFORE OPERATION


3.2 Procedures for Using SLMP Data Collector 27
13. Drag and drop the external data tag resource onto the data tag resource monitor window.
The external data tag resource is registered, and monitoring starts.

3 PROCEDURE BEFORE OPERATION


28 3.2 Procedures for Using SLMP Data Collector
4 FUNCTIONS
This chapter shows the functions of SLMP Data Collector.

4.1 Data Collection Function


This function sends a data reading request to a MELSEC device or an SLMP-compatible device other than MELSEC devices
in the interval of the set collection cycle and collects data when receiving a response from the device.
Data collection starts at the time when the set time has elapsed since the operating status of Edgecross Basic Software was
turned to RUN. After that, data is read periodically at specific intervals.
This function works at specific intervals without the effects of the time change of an industrial PC in which SLMP Data 4
Collector runs.

Collection processing time report


When an enabled data collection setting is included in Edgecross Basic Software and the operating status of the software
switches from RUN to STOP, the maximum and minimum collection processing times in the RUN state are reported to the
software.
The collection processing time is reported as follows:
• Unit: 100 ms
• Range: 0 to 4294967200

• Among times for each data collection executed from when the operation status of Edgecross Basic
Software is turned to RUN until when it is switched to STOP, the longest time is referred to as the maximum
collection processing time and the shortest time is referred to as the minimum collection processing time.
• The collection processing time is rounded down to 100 milliseconds.
• The collection processing time less than 100 milliseconds is regarded as 100 milliseconds.
• 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'.

Collection processing time


Collection processing time is the time from the start to completion of data collection performed at every collection cycle.

Ex.
When the collection cycle is set to 500 milliseconds, if the time from the start to completion of the (n)th data collection is within
the collection cycle, the time taken to collect data will be the collection processing time. Even If time from the start to
completion exceeds the collection cycle as the (n+1)th collection, the time from the start to completion will be the collection
processing time. When the completion exceeds the collection cycle, the (n+2)th collection will be started after the completion
of the (n+1)th collection, and measurement of the collection processing time for the (n+2)th collection is started corresponding
to its start.

0ms 500ms 1000ms 1500ms

n n+1 n+2 n+3

A A A A
: Data collection processing
A: Measurement range

4 FUNCTIONS
4.1 Data Collection Function 29
Precautions
Collection time
The time (time stamp) of sending a data reading request to a MELSEC device or an SLMP-compatible device other than
MELSEC devices (access target device) is added to collected data. If the communication status becomes unstable*1, an
interval between time stamps may be extended; however, once the communication status stabilizes, it becomes constant.
*1 Instantaneous interruption of the connection route or powering OFF and ON of the access target device, etc.

Date and time of error or event occurrence in the event history of Edgecross Basic Software
Items such as the date and time of error or event occurrence are displayed in the event history of Edgecross Basic Software.
A time stamp is added for the date and time by Edgecross Basic Software; therefore, it may not match the one added by
SLMP Data Collector.

Collection processing time when a response timeout error occurs


For a MELSEC connection, if there is a problem on the access path, a response timeout error may occur when
communicating with an access target device.
When a response timeout error occurs, the collection processing time will be extended according to the timeout time and the
number of retries.
Collection processing time when a response timeout error occurs is calculated as follows:
• Collection processing time = timeout time (second)  (number of retries + 2)  (number of settings*2 for a same access
target device*1)
*1 Even if a same IP address is set in multiple target device settings, those devices are regarded as the same device.
*2 It is the total number of settings for the data collection, data reading, and data writing functions

Exceeded collection cycle


If data collection is not started even after the allowable collection processing delay time (the set collection cycle  2) elapsed,
an exceeded collection cycle is detected and data whose collection could not be started will be missing.
If the communication status with an access target device becomes unstable*1 during data collection, the collection cycle may
be exceeded multiple times depending on the timing.
*1 Instantaneous interruption of the connection route or powering OFF and ON of the access target device, etc.
When an exceeded collection cycle occurs, the maximum collection processing time is not affected by the collection cycle.
To avoid data missing, lengthen the collection cycle or review the communication path so that data can be collected from a
MELSEC device or an SLMP-compatible device other than MELSEC devices within the collection cycle.
The following shows examples in which an exceeded collection cycle occurs when data collection cannot be started within the
allowable collection processing delay time due to a delayed start of the collection or a delayed completion of the previous
collection.

Ex.
A start of data collection is delayed:
When the collection cycle is set to 500 milliseconds, if the (n+1)th data collection cannot be started even after the allowable
collection processing delay time (1000 milliseconds) elapsed due to some reasons such as system load, an exceeded
collection cycle is detected and data of the (n+1)th collection will be missing.

0ms 500ms 1000ms 1500ms

n n+1 n+2

B
C
: Data collection processing
A: Period in which the system is overloaded
B: Allowable collection processing delay time
C: Detection of an exceeded collection cycle

4 FUNCTIONS
30 4.1 Data Collection Function
Ex.
A completion of the previous collection is delayed:
When the collection cycle is set to 500 milliseconds, if the (n+1)th data collection is not completed even after the allowable
collection processing delay time (1000 milliseconds) elapsed due to a late response from an access target device, an
exceeded collection cycle is detected and data of the (n+2)th collection will be missing.

0ms 500ms 1000ms 1500ms

n n+1 n+3

n+2

4
A

B
: Data collection processing
A: Allowable collection processing delay time
B: Detection of an exceeded collection cycle

Operation when collecting data


The operations when collecting WSTRING type data are as follows:
• For non-surrogate characters, one word is collected from a target device.
• For surrogate characters, two words are collected from a target device.

Ex.
Setting of data to be collected
WSTRING type data [Number of characters = 4] (D0-D7)
Values of D0-D7
D0: 'A'
D1: 'B'
D2-D3: ''
D4: 'C'
D5: 'D'
D6: 'E'
D7: 'F'
 indicates a surrogate character.
Collection result
'ABC'

4 FUNCTIONS
4.1 Data Collection Function 31
4.2 Data Reading Function
This function sends a data reading request to a MELSEC device or an SLMP-compatible device other than MELSEC devices
according to a request from Edgecross Basic Software and reads data.
If multiple data reading requests are sent to a same access target device, time to pass data to Edgecross Basic Software will
be delayed compared with a case in which a single data reading request is sent.

Read processing time report


When reconnecting to an access target device in Edgecross Basic Software, the maximum and minimum read processing
times among times measured while the software was running are reported to the software.
The read processing time is reported as follows:
• Unit: Millisecond
• Range: 0 to 4294967295

• Among times for each read processing executed from when Management Shell is started until when it is
stopped, the longest time is referred to as the maximum read processing time and the shortest time is
referred to as the minimum read processing time.
• Read processing time is the time from when the data collector sends a data reading request to an access
target device to when it receives a response from the device.
• When no data is read during the operation, the maximum and minimum read processing times are reported
as '0'.

Precautions
Target device settings in Management Shell
When Management Shell is running, all of the access target devices set in Management Shell Explorer will be connected
regardless of the following statuses; a connection error may occur due to an unintentional connection.
• Access status from Management Shell Explorer to an external data tag resource
• Start status of Management Shell Explorer
Delete unnecessary target device settings in Management Shell to avoid the connection error.

Specifications for reading WSTRING type data


The operations when reading WSTRING type data are as follows:
• For non-surrogate characters, one word is read from a target device.
• For surrogate characters, two words are read from a target device.

Ex.
Setting of data to be read
WSTRING type data [Number of characters = 4] (D0-D7)
Values of D0-D7
D0: 'A'
D1: 'B'
D2-D3: ''
D4: 'C'
D5: 'D'
D6: 'E'
D7: 'F'
 indicates a surrogate character.
Reading result
'ABC'

4 FUNCTIONS
32 4.2 Data Reading Function
Processing time for reading data from a same access target device
For an SLMP connection, when a same IP address and port number are specified in multiple target device settings, the
processing may be delayed; however, this delay can be avoided by setting different port numbers.
The following figure shows a change example.

Ex.
Change "Port number" of target device setting No.2 to '2000'.

(1)

(2)

(1)

(2)

(1) Target device setting No.1


(2) Target device setting No.2

4 FUNCTIONS
4.2 Data Reading Function 33
4.3 Data Writing Function
This function sends a data writing request to a MELSEC device or an SLMP-compatible device other than MELSEC devices
according to a request from Edgecross Basic Software and writes data.
If multiple data writing requests are sent to a same access target device, time to notify the completion of data writing to
Edgecross Basic Software will be delayed compared with a case in which a single data writing request is sent.

Precautions
Target device settings in Management Shell
Refer to the following:
Page 34 Target device settings in Management Shell

Specifications for writing WSTRING type data


The operations when writing WSTRING type data are as follows:
• For non-surrogate characters, one word is written to a target device.
• For surrogate characters, two words are written to a target device.

Ex.
Setting of data to be written
WSTRING type data [Number of characters = 4] (D0-D7)
Setting of a value to be written
ABC
 indicates a surrogate character.
Writing result
D0: 'A'
D1: 'B'
D2: 'C'
D3-D4: ''
D5-D7: '\0'

Processing time for writing data to a same access target device


For an SLMP connection, when a same IP address and port number are specified in multiple target device settings, the
processing may be delayed; however, this delay can be avoided by setting different port numbers.
The following figure shows a change example.

Ex.
Change "Port number" of target device setting No.2 to '2000'.

(1)

(2)

(1)

(2)

(1) Target device setting No.1


(2) Target device setting No.2

4 FUNCTIONS
34 4.3 Data Writing Function
4.4 Considerations
This section shows common considerations for the functions of SLMP Data Collector.

Access path failure


Data missing will occur when data is not read due to a problem on an access path, and a data writing error will occur when
data is not written.
When data missing occurs, it is reported from SLMP Data Collector to Edgecross Basic Software.
When a data writing error occurs, it is also reported from SLMP Data Collector to Edgecross Basic Software.
SLMP Data Collector checks its connection with a MELSEC device or an SLMP-compatible device other than MELSEC
devices every 30 seconds and attempts a re-connection if disconnected.
If re-connection fails, it will be disconnected until the next connection check to be executed in another 30 seconds.
4

Data inconsistency
When both conditions listed below are satisfied, data inconsistency may occur. To avoid this issue, review the collection
settings of Real-time Flow Designer.
• Any of the following type of data is included:
DINT
UDINT
LINT
ULINT
REAL
LREAL
STRING
WSTRING
• The total number of assigned device points for data to be read or written is larger than the following number of assigned
device points:
SLMP connection
Communication frame Command Assigned device point
Reading Writing
'4E (Binary)' or '3E (Binary)' Random read/write (16-bit) 192 80
Random read/write (32-bit) 96 68
'4E (ASCII)' or '3E (ASCII)' Random read/write (16-bit) 192 80
Random read/write (32-bit) 96 68

MELSEC connection
Device type Assigned device point
Reading Writing
MELSEC iQ-R 58 38
MELSEC iQ-F
MELSEC-Q 96 80
MELSEC-L

The number of device points assigned to data to be read or written is determined by the combination of the location and data
type. For the number of device points to be assigned, refer to the following:
Page 105 Number of device points to be assigned to data
Even when data inconsistency has occurred, data can be read or written; however, the read/written data values may differ
from the actual data values in an access target device.

4 FUNCTIONS
4.4 Considerations 35
Example of data inconsistency (for a MELSEC connection)
In the following collection data, data inconsistency may occur between 'W4 to W6' and 'W7' in 'Data2'.

Steps on how data inconsistency occurs are shown below.

Ò
(2)
Ô
Ó
(1)

(3)

D0 D1 D2 D100 D115 D116 D131 D132 D147 W0 W1 W2 W3 W4 W5 W6 W7

Flag Code Msg1 Msg2 Msg3 Data1 Data2


(INT) (UDINT) (WSTRING[8]) (WSTRING[8]) (WSTRING[8]) (LREAL) (LREAL)
(1) SLMP Data Collector
(2) MELSEC device
(3) Number of points in which no data inconsistency occurs (58 points)

A data reading request for 58 points from the first collection data (D0 to D2, D100 to D147, and W0 to W6) is sent to a
MELSEC device.
Values of D0 to D2, D100 to D147, and W0 to W6 are returned to SLMP Data Collector.
The values from W4 to W7 are updated in the MELSEC device.
The request to read the one remaining point of collection data (W7) is sent to the MELSEC device.
The value of W7 is returned to SLMP Data Collector. Since the values from W4 to W7 has been updated in step , the
value of 'Data2' collected with SLMP Data Collector may be inconsistent with the actual data value in the MELSEC device.
(Data inconsistency may occur.)

4 FUNCTIONS
36 4.4 Considerations
Packet loss
For a MELSEC connection, SLMP Data Collector communicates with an access target device by using UDP.
During the communication, it is possible to lose a packet.
The behavior when a packet is lost is as follows:
• Waits until the timeout time elapses. (If the next data collection period is reached before the timeout time elapses, an
exceeded collection cycle occurs.)
• Reports a packet loss error (error code: 1932H) to Edgecross Basic Software. (In the detailed information, the following
cumulative number of occurrences and elapsed time are displayed.)
Item Description
Cumulative number of occurrences The number of times which a packet loss has occurred since any of the following operations.

4
• Real-time Flow Manager:
Turning the operating status of Real-time Flow Manager to RUN
• Management Shell:
Starting Management Shell
Adding or Changing a target device setting
Clicking the [Reconnect] button after selecting SLMP Data Collector in the "Target Device Setting List" screen
When the number exceeds 99 times, "100 times or more" is displayed.
Elapsed time Time which has been elapsed since the previous packet loss occurred (n days hh:mm:ss)
For the first packet loss detected after any of the following operations, it represents time from the operation execution
to the packet loss detection.
• Real-time Flow Manager:
Turning the operating status of Real-time Flow Manager to RUN
• Management Shell:
Starting Management Shell
Adding or Changing a target device setting
Clicking the [Reconnect] button after selecting SLMP Data Collector in the "Target Device Setting List" screen
When the time exceeds 999 days 23:59:59, "1000 days or more" is displayed.
Period in which a data collector is not connected with an access target device is not included in the elapsed time.

Timeout error
A timeout error occurs when there is no response from an access target device even after the timeout time set in the
communication parameter elapsed.
For an SLMP connection, however, a data send/receive error (error code: 1A09H) may occur before the timeout time set in
the communication parameters elapses.
This error occurs after a TCP retransmission timeout time*1 in Windows elapses if both of the following conditions are
satisfied.
• A timeout time is longer than a TCP retransmission timeout time*1 in Windows.
• An Ethernet cable was disconnected during the operation of SLMP Data Collector.
*1 The default is 21 seconds.

CPU parameter change of an access target device


For a MELSEC connection, perform the following operations to change CPU parameters of an access target device.

For Real-time Flow Manager


1. Switch the operating status of Real-time Flow Manager to STOP in Real-time Flow Designer.

2. Change CPU parameters of an access target device.

3. Switch the operating status of Real-time Flow Manager to RUN in Real-time Flow Designer.

For Management Shell


1. Switch Management Shell to the stop state in Management Shell Explorer.

2. Change CPU parameters of an access target device.

3. Switch Management Shell to the operating state in Management Shell Explorer.

4 FUNCTIONS
4.4 Considerations 37
5 PARAMETER SETTINGS
This chapter shows the parameters of SLMP Data Collector that can be set in Edgecross Basic Software.
For the display of the setting screens for each parameter, refer to the following:
Edgecross Basic Software for Windows User's Manual

5.1 SLMP Connection


This section shows the parameters for an SLMP connection.

Communication parameters
Configure the connection between SLMP Data Collector and an SLMP-compatible device.

Window
• The "Target Device Setting" screen of Real-time Flow Designer
• The "Target Device Setting" screen of Management Shell Explorer

Displayed items
Item Description
Connection Type*1 Select "SLMP connection".
Communication frame*1 Set the communication frame and data code ("4E (Binary)", "3E (Binary)", "4E (ASCII)", or "3E (ASCII)") according to
the packet message format with an access target device.
Command*1 Select a command.
For available commands, refer to the following:
Page 12 Available commands
IP Address*2,*3 Set the IP address specified in an access target device.
Port number*4 Set the port number specified in an access target device (1 to 65535).
Request destination network Set the network number specified in an access target device (0 to 239).
No.*5,*6,*7
Request destination station No.*7,*8,*9 Set the station number specified in an access target device (1 to 120).
Request destination module I/O When an access target device is in a multiple CPU system configuration, select the access target CPU number
No.*10 (module I/O number of a request destination).
When an access target device is in a single CPU system configuration, select "H03FF (Host station)".
Time-out Time Set a timeout time for accessing a target device (1 to 30 seconds).
Retry Count*11 Set the number of retries when communication with an access target fails (0 to 2).
Initial Access Delay Time Set a waiting time from when the initialization processing of an access target device is completed until data collection
can be performed (0 to 255 seconds).

5 PARAMETER SETTINGS
38 5.1 SLMP Connection
*1 It cannot be changed when the target device setting is used for a process flow and an external data tag resource.
*2 Only numbers can be entered.
*3 The available range is as follows:
1.0.0.0 to 126.255.255.255, 128.0.0.0 to 223.255.255.255
*4 When setting an access target device by the procedure in the following section, enter the value for "GOT Communication Port No." set
in the procedure.
Page 22 Procedure for setting an SLMP-compatible device
*5 When setting an access target device by the procedure in the following section, enter the value for "GOT Net No." set in the procedure.
Page 22 Procedure for setting an SLMP-compatible device
*6 Do not access another station since SLMP Data Collector can only access the host station.
Enter '0' (Host station) to access the host station.
*7 If the number for accessing the host station is specified by an access target device, enter the value according to its specification.
*8 When setting an access target device by the procedure in the following section, enter the value for "GOT Station" set in the procedure.
Page 22 Procedure for setting an SLMP-compatible device
*9 It cannot be set if '0' is set for "Request destination network No.". (It will be fixed to '255' (Host station).)
*10 When "H03FF (Host station)" is selected, it refers to the control CPU of an access target network module.
*11 Retry is not performed while the data collection function is used.

When accessing target devices with the same IP address, the processing performance may be improved by 5
setting a different port number for each device.
However, consider the system configuration and performance specifications for deciding the setting contents.

5 PARAMETER SETTINGS
5.1 SLMP Connection 39
Considerations
If both of the following conditions are satisfied, using multiple target device settings in Edgecross Basic Software may cause
communication parameter mismatch errors in starting the data collector.
• Same IP address and port number have been specified in multiple target settings.
• Setting contents*1 do not completely match among the target device settings.
*1 They refer to the following items:
Communication frame
Command
Request destination network No.
Request destination station No.
Request destination module I/O No.
Time-out Time
Retry Count
Initial Access Delay Time
Methods to clear communication parameter errors that occur while multiple target device settings are used are as follows.

For Real-time Flow Manager


1. Click the [Stop Operation] button in the "Real-time Flow Manager Diagnostics" screen.

2. Perform any of the following operations to the target device settings that satisfy both of the conditions.
• Change their IP addresses or port numbers so that they are not duplicated.
The following shows an example in which setting for "Communication frame" differs between two target device settings.

Ex.
Change "Port number" of target device setting No.2 to '2000'.

(1)

(2)

(1)

(2)

(1) Target device setting No.1


(2) Target device setting No.2

5 PARAMETER SETTINGS
40 5.1 SLMP Connection
• Match all the setting contents among the target device settings.
The following shows an example in which setting for "Communication frame" differs between two target device settings.

Ex.
Change "Communication frame" of target device setting No.2 to "4E (Binary)".

(1)

(2)

(1) 5

(2)

(1) Target device setting No.1


(2) Target device setting No.2

• Use only one target device setting, and delete the rest.*1
*1 The settings can be deleted only when they are not used in Real-time Flow Manager or Management Shell.
3. Click the [Start Operation] button in the "Real-time Flow Manager Diagnostics" screen.

5 PARAMETER SETTINGS
5.1 SLMP Connection 41
For Management Shell
1. Perform any of the following operations to the target device settings that satisfy both of the conditions.
• Change their IP addresses or port numbers so that they are not duplicated.
The following shows an example in which setting for "Communication frame" differs between two target device settings.

Ex.
Change "Port number" of target device setting No.2 to '2000'.

(1)

(2)

(1)

(2)

(1) Target device setting No.1


(2) Target device setting No.2

• Match all the setting contents among the target device settings.
The following shows an example in which setting for "Communication frame" differs between two target device settings.

Ex.
Change "Communication frame" of target device setting No.2 to "4E (Binary)".

(1)

(2)

(1)

(2)

(1) Target device setting No.1


(2) Target device setting No.2

5 PARAMETER SETTINGS
42 5.1 SLMP Connection
• Use only one target device setting, and delete the rest.*1
*1 The settings can be deleted only when they are not used in Real-time Flow Manager or Management Shell.
2. Select [Management Shell]  [Management Shell Stop].

3. Select [Management Shell]  [Management Shell Start].

5 PARAMETER SETTINGS
5.1 SLMP Connection 43
Collection parameters
Configure the settings on data collection in SLMP Data Collector.

Window
• The [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.

Precautions
In communication with SLMP Data Collector, transmission delays depending on the access target device response time, the
transmission time, and the number of collection device points. Set a collection interval considering the transmission delay.
• Transmission delay time =(Access target device response time*1 + transmission time  2)  number of divided data
sending*2
*1 It is determined according to the service processing time or scan time for an SLMP-compatible device to be used. For details, refer to
the manual of the device.
*2 It is calculated (rounding up after the decimal point) as follows according to the type of an SLMP-compatible device.
Random read/write (32-bit): Number of collection device points  96
Random read/write (16-bit): Number of collection device points  192
For details on the number of points, refer to the following:
Page 105 Number of device points to be assigned to data

5 PARAMETER SETTINGS
44 5.1 SLMP Connection
Location parameters
Configure the settings on target devices for SLMP Data Collector.

Real-time Flow Designer


Data collection function

Window
The [Collection Data] tab in the "Data Collection Setting" screen of Real-time Flow Designer

Displayed items
Item Description
Data Name Set a data name (up to 32 characters).
Constant Select the checkbox to add a constant value or fixed character string to collection data.
Location (top) Set an access target device memory.
Location (end) It is automatically set according to the settings in "Location (top)" and "Data Type."
When selecting "STRING" or "WSTRING" for "Data Type," it is also affected by a value set in "Length."
Data Type Select the data type of a location to access.
Length 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
Setting Value Set a constant value or fixed character string to add to collection data.

• Location setting
For an SLMP connection, a location can be set by either of the following methods:
Page 48 Setting in the location setting screen
Page 49 Entering directly
When setting the location parameters, check the manual for a device to be accessed.

5 PARAMETER SETTINGS
5.1 SLMP Connection 45
Data writing function

Window
The [Instruction Target data] tab in the "Instruction Feedback Setting" screen of Real-time Flow Designer

Displayed items
Item Description
Data Name Set a data name (up to 32 characters).
Location (top) Set an access target device memory.
Location (end) It is automatically set according to the settings in "Location (top)" and "Data Type."
When selecting "STRING" or "WSTRING" for "Data Type," it is also affected by a value set in "Length."
Data Type Select the data type of a location to access.
Length 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
Setting Value Set a value to substitute for an access target location.

• Location setting
For an SLMP connection, a location can be set by either of the following methods:
Page 48 Setting in the location setting screen
Page 49 Entering directly
When setting the location parameters, check the manual for a device to be accessed.

5 PARAMETER SETTINGS
46 5.1 SLMP Connection
Management Shell
Window
The "Add External Data Tag Resource" or "Edit External Data Tag Resource" screen of Management Shell Explorer

Displayed items 5
Item Description
Data Tag Resource Name 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).
Target Device Select an access target device for an external data tag resource.
Location Set an access target device memory.
Data Type Select the data type of a location to access.
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

Location setting
For an SLMP connection, a location can be set by either of the following methods:
Page 48 Setting in the location setting screen
Page 49 Entering directly
When setting the location parameters, check the manual for a device to be accessed.

5 PARAMETER SETTINGS
5.1 SLMP Connection 47
Setting in the location setting screen
The following shows the "Location Setting" screen for setting a location.

Window
Real-time Flow Designer
• Data collection function: Click the [...] button in the [Collection Data] tab in the "Data Collection Setting" screen of Real-time
Flow Designer.
• Data writing function: Click the [...] button in the [Instruction Target data] tab in the "Instruction Feedback Setting" screen of
Real-time Flow Designer.

Management Shell
Click the [Setting] button in the "Add External Data Tag Resource" or "Edit External Data Tag Resource" screen of
Management Shell Explorer.

Displayed items
Item Description
Communication frame The communication frame and data code are displayed.
Command The command is displayed.
Device type Select a device type.
Check the specifications of a device to be accessed before selecting. An error occurs if the setting does not match to
the device type of the device to be accessed.*1
The device type is displayed in the following screens as below according to the selected value: the "Data Collection
Setting", "Instruction Feedback Setting", "Add External Data Tag Resource", and "Edit External Data Tag Resource"
screens.
• Bit: B
• Word: W
• Double word: D
Device code*2 Set a device code.
Check the specifications of a device to be accessed before setting. An error occurs if the setting does not match to
"Device type".*3
To set multiple devices with a same device code as access targets, match the case in the device code.
For input formats, refer to the following:
Page 50 Input format of a device code
Device number*4,*5 Set the number and radix of a device.
Check the specifications of a device to be accessed before setting.
The radix is displayed in the following screens as shown below according to the selected value: the "Data Collection
Setting", "Instruction Feedback Setting", "Add External Data Tag Resource", and "Edit External Data Tag Resource"
screens.
• Octal: O
• Decimal: D
• Hexadecimal: H
For input formats, refer to the following:
Page 50 Input format of a device number

*1 Selection examples are as follow:


When a device code is 'B' or 'M': Bit
When a device code is 'D' or 'W': Word
When a device code is 'LTN': Double word
*2 When "4E (Binary)" or "3E (Binary)" is displayed in "Communication frame", '0' is inserted for padding according to the maximum
number of digits.
*3 A setting example when a device type is 'D' is as follow:

5 PARAMETER SETTINGS
48 5.1 SLMP Connection
ASCII: D
Binary: A8
*4 When "Octal" or "Hexadecimal" is set for the device number (radix), '0' is inserted for padding according to the maximum number of
digits.
*5 When "Decimal" is set for the device number (radix), unnecessary '0' is deleted.

Entering directly
The following shows the details on entering a location directly.

Input format for a location


Enter a location by the following format.
• Device type | Device code | Device number (Radix) | Device number
Item Description
Device type Set a device type.
• Bit: B
• Word: W
• Double word: D
Device code Set a device code. 5
For input formats, refer to the following:
Page 50 Input format of a device code
Device number (Radix) Set the radix of a device number.
• Octal: O
• Decimal: D
• Hexadecimal: H
Device number*1,*2 Set a device number.
For input formats, refer to the following:
Page 50 Input format of a device number

*1 When 'O' or 'H' is entered for the device number (radix), '0' is inserted for padding according to the maximum number of digits.
*2 When 'D' is entered for the device number (radix), unnecessary '0' is deleted.

Ex.
A setting example for each of the following items is shown below.
• Data Name: Data1
• Location: W|W|H|00000E
(Device type: W, Device code: W, Device number (Radix): H, Device number: 0E)
• Data Type: DINT

5 PARAMETER SETTINGS
5.1 SLMP Connection 49
Input format of a device code
The input format of a device code differs depending on the settings for the command, communication frame, and data code.
Command Communication frame and Input format
data code Available character Input range
Random read/write (16-bit) '4E (Binary)' or '3E (Binary)' 0 to 9, a to f, A to F 0 to FF
'4E (ASCII)' or '3E (ASCII)' ASCII codes available in SLMP Data 1 or 2 characters
Collector*1
Random read/write (32-bit) '4E (Binary)' or '3E (Binary)' 0 to 9, a to f, A to F 0 to FFFF
'4E (ASCII)' or '3E (ASCII)' ASCII codes available in SLMP Data 1 to 4 characters
Collector*1

*1 Available ASCII codes are shown in the table below.


Characters in the shaded area can be used.

0 1 2 3 4 5 6 7
0 NUL (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

Input format of a device number


The input format of a device number differs depending on the command and the device number (radix).
Command Device number (Radix) Input format
Available character Input range
Random read/write (16-bit) Octal 0 to 7 0 to 777777
Decimal 0 to 9 0 to 999999
Hexadecimal 0 to 9, a to f, A to F 0 to FFFFFF
Random read/write (32-bit) Octal 0 to 7 0 to 77777777
Decimal 0 to 9 0 to 99999999
Hexadecimal 0 to 9, a to f, A to F 0 to FFFFFFFF

5 PARAMETER SETTINGS
50 5.1 SLMP Connection
Considerations
When using Management Shell Explorer, check whether location parameters are correct by clicking the [Parameter Check]
button in the "Target Device Setting List" screen after setting all the location parameters.*1
If there are incorrect location parameters, a data collector internal error (error code: 1A00H) occurs.
*1 Checking location parameters may take time.

5 PARAMETER SETTINGS
5.1 SLMP Connection 51
5.2 MELSEC Connection
This section shows the parameters for a MELSEC connection.

Communication parameters
Configure the connection between SLMP Data Collector and a MELSEC device.

Window
• The "Target Device Setting" screen of Real-time Flow Designer
• The "Target Device Setting" screen of Management Shell Explorer

Displayed items
Item Description
Connection Type*1 Select "MELSEC connection".
Device Type*1,*2 Select the type of access target device.
Multiple CPU Setting*3 When an access target device is in a multiple CPU system configuration, set the target CPU number.
When it is in a single CPU system configuration, select "Not Specified".
Remote password*2,*4,*5 Set the remote password registered to a target device as necessary.
The number of available characters differs depending on the selected device type.
 Available number of characters
• MELSEC iQ-R (Programmable controller CPU/Process CPU/safety CPU): 6 to 32 characters
• MELSEC iQ-R (C controller): 6 to 32 characters
• MELSEC iQ-F (Programmable controller CPU): 6 to 32 characters
• MELSEC-Q (Programmable controller CPU/Process CPU): 4 characters
• MELSEC-Q (C controller): 4 characters
• MELSEC-L (Programmable controller CPU): 4 characters
 Available characters
• ASCII characters (alphanumeric characters and spaces*6)
• `, ~, !, @, #, $, %, ^, &, *, (, ), _, +, -, =, {, }, |, \, :, ", ;, ', <, >, ?, ,, ., /, [, ]
Programmable controller side I/F Select a connection interface of a programmable controller.
Network No.*7,*8 Set the network number specified in an access target Ethernet module (1 to 239).
Station number of connection Set the station number of the connection source specified in the industrial PC where this product is running (1 to 120).
source*7,*8,*9
IP Address*10,*11 Set the IP address specified in an access target device.
Station number of connection Set the station number specified in an access target Ethernet module (1 to 120).
target*7,*8,*9
Time-out Time Set a timeout time for accessing a target device (1 to 30 seconds).
*12
Retry Count Set the number of retries when communication with an access target fails (0 to 2).
Initial Access Delay Time Set a waiting time from when the initialization processing of an access target device is completed until data collection
can be performed (0 to 255 seconds).

*1 It cannot be changed when the target device setting is used for a process flow and an external data tag resource.
*2 The setting is deleted once "Device Type" is changed.
*3 It cannot be set when "MELSEC iQ-F (Programmable controller CPU)" or "MELSEC-L (Programmable controller CPU)" is selected for
"Device Type".
*4 It does not need to be set when a remote password is not set to an access target device.
*5 Each entered character is displayed as '*'.
Entered characters cannot be copied or cut.
*6 It cannot be used when "MELSEC-Q (Programmable controller CPU/Process CPU)", "MELSEC-Q (C controller)", or "MELSEC-L

5 PARAMETER SETTINGS
52 5.2 MELSEC Connection
(Programmable controller CPU)" is selected for "Device Type".
*7 A connection will be established with any value in the range when a MELSEC iQ-R series device for which communications with the
network number and station number are disabled is set as a target device.
*8 It cannot be set when "CPU's built-in Ethernet port" is selected for "Programmable controller side I/F". (It will be fixed to '1'.)
*9 Set different numbers for "Station number of connection source" and "Station number of connection target," regardless of the setting
(enabled or disabled) of communications with a network number and station number.
*10 Only numbers can be entered.
*11 The available range is as follows:
1.0.0.0 to 126.255.255.255, 128.0.0.0 to 223.255.255.255
*12 Retry is not performed while the data collection function is used.

For accessible CPU modules, refer to the following:


Page 17 Accessible CPU modules

Precautions
When "MELSEC iQ-F (Programmable controller CPU)," "MELSEC-Q (Programmable controller CPU/Process CPU),"
"MELSEC-Q (C controller)," or "MELSEC-L (Programmable controller CPU)" is selected for "Device Type," set the number of
5
required MELSOFT connection devices in the parameter setting of an access target device.
For the setting method, refer to the manual for each module.

5 PARAMETER SETTINGS
5.2 MELSEC Connection 53
Collection parameters
Configure the settings on data collection in SLMP Data Collector.

Window
• The [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.

Precautions
In communication with SLMP Data Collector, transmission delays depending on the CPU response time, the transmission
time, and the number of collection device points. Set a collection interval considering the transmission delay.
• Transmission delay time =(CPU response time*1 + transmission time  2)  number of divided data sending*2
*1 It is determined according to the service processing time or scan time for a programmable controller CPU to be used. For details, refer
to the manual of the programmable controller CPU.
*2 It is calculated (rounding up after the decimal point) as follows according to the type of a MELSEC device.
RCPU, FXCPU: Number of collection device points  58
QCPU (Q mode), LCPU: Number of collection device points  96
For details on the number of points, refer to the following:
Page 105 Number of device points to be assigned to data

5 PARAMETER SETTINGS
54 5.2 MELSEC Connection
Location parameters
Configure the settings on target devices for SLMP Data Collector.

Real-time Flow Designer


Data collection function

Window
The [Collection Data] tab in the "Data Collection Setting" screen of Real-time Flow Designer

Displayed items
Item Description
Data Name Set a data name (up to 32 characters).
Constant Select the checkbox to add a constant value or fixed character string to collection data.
Location (top) Set an access target device memory.
Location (end) It is automatically set according to the settings in "Location (top)" and "Data Type."
When selecting "STRING" or "WSTRING" for "Data Type," it is also affected by a value set in "Length."
Data Type Select the data type of a location to access.
Length 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
Setting Value Set a constant value or fixed character string to add to collection data.

• Location setting
For a MELSEC connection, a screen for setting location parameters is not provided.
Enter an accessible device (location) directly.

Ex.
When setting SD0 as the STRING type with 32 characters

For accessible devices (locations), refer to the following:


Page 18 Accessible devices (locations)

5 PARAMETER SETTINGS
5.2 MELSEC Connection 55
Data writing function

Window
The [Instruction Target data] tab in the "Instruction Feedback Setting" screen of Real-time Flow Designer

Displayed items
Item Description
Data Name Set a data name (up to 32 characters).
Location (top) Set an access target device memory.
Location (end) It is automatically set according to the settings in "Location (top)" and "Data Type."
When selecting "STRING" or "WSTRING" for "Data Type," it is also affected by a value set in "Length."
Data Type Select the data type of a location to access.
Length 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
Setting Value Set a value to substitute for an access target location.

• Location setting
For a MELSEC connection, a screen for setting location parameters is not provided.
Enter an accessible device (location) directly.

Ex.
When setting the character string '1' for SD0 as the WSTRING type (number of characters: 16)

For accessible devices (locations), refer to the following:


Page 18 Accessible devices (locations)

5 PARAMETER SETTINGS
56 5.2 MELSEC Connection
Management Shell
Window
The "Add External Data Tag Resource" or "Edit External Data Tag Resource" screen of Management Shell Explorer

Displayed items 5
Item Description
Data Tag Resource Name 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).
Target Device Select an access target device for an external data tag resource.
Location Set an access target device memory.
Data Type Select the data type of a location to access.
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

Location setting
For a MELSEC connection, a screen for setting location parameters is not provided.
Enter an accessible device (location) directly.

Ex.
When setting SD0 as the STRING type with 32 characters

For accessible devices (locations), refer to the following:


Page 18 Accessible devices (locations)

5 PARAMETER SETTINGS
5.2 MELSEC Connection 57
6 TROUBLESHOOTING
This chapter explains the errors which may occur when using SLMP Data Collector and the troubleshooting.

6.1 Checking Method for Error Descriptions


The following are the methods for checking error descriptions.
Checking method Details
Real-time Flow Designer Error codes can be checked in the "Real-time Flow Manager Diagnostics" screen of Real-time Flow Designer.
For details, refer to the following:
Edgecross Basic Software for Windows User's Manual
Management Shell Explorer Error codes can be checked in the "Error Information List" screen of Management Shell Explorer.
For details, refer to the following:
Edgecross Basic Software for Windows User's Manual

Error type
There are two types of errors for SLMP Data Collector: moderate error and minor error.

6 TROUBLESHOOTING
58 6.1 Checking Method for Error Descriptions
6.2 Troubleshooting by Symptom
If a function of SLMP Data Collector does not perform properly, check the applicable items in the following and troubleshoot
the error.

Troubleshooting on the SLMP Data Collector startup

The data collector is not recognized at the Edgecross Basic Software start.
Check point Corrective action
Does a signed-in user who started Edgecross Basic • Sign in as a user with the access right to the folder in which SLMP Data Collector is stored, and start
Software have the access right to a folder in which Edgecross Basic Software.
SLMP Data Collector is stored? • Grant the user access to the folder in which SLMP Data Collector is stored.

Troubleshooting on data reading

Data cannot be read.


Check point Corrective action 6
Is the initial access delay time set? • Wait until the set initial access delay time elapses.
• Set the initial access delay time shorter.
Has a reading error occurred in Edgecross Basic • Decrease the number of points for data reading.
Software even though there is no error in this • Check the status of an access target device.
product? • Check whether the path to an access target device is correct.
• Review the devices and paths on the access path.
Is a remote password set to an access target device? • Set the remote password specified in the access target device in the communication parameters.
• Disable the remote password setting.
Has an communication parameter mismatch error Find the target device settings whose "Connection Type" is set to "SLMP connection" and both IP
(error code: 1A0CH to 1A13H) occurred even though address and port number are duplicated with others in Management Shell Explorer. Then, set all of the
there is only one target device setting registered in communication parameter items the same as the ones of target device settings in Real-time Flow
Real-time Flow Designer? Designer.
Page 40 Considerations
Has an communication parameter mismatch error Find the target device settings whose "Connection Type" is set to "SLMP connection" and both IP
(error code: 1A0CH to 1A13H) occurred even though address and port number are duplicated with others in Real-time Flow Designer. Then, set all of the
there is only one target device setting registered in communication parameter items the same as the ones of target device settings in Management Shell
Management Shell? Explorer.
Page 40 Considerations
Does the radix of a device to be read match to the one Check the radix of a device specified for the device number in the manual for an access target device.
set for "Device number" in the location parameters? Then, set the same value as the checked radix for the one in "Device number" of the location
parameters.
Has a data collector internal error (error code: 1A00H) Check the location parameter where an error has occurred, and clear the error.
occurred? For the checking method, refer to the following:
Page 51 Considerations
Does the device type of a device to be read match to Check the device type specified for the device code in the manual for an access target device. Then,
the one set in the location parameters? set the same value as the checked device type for "Device type" in the location parameters.
Has a location parameter setting error (unmatch of • Review all the location parameters used for an access target device where an error has occurred.
device type and device code) (error code: 1A14H) • Correct all the location parameters used for an access target device where an error has occurred so
occurred when "SLMP connection" is selected for that their settings match to the device type and device code given in the manual of the access target
"Connection type"? device.
• When multiple devices with a same device code are set as access targets, match the case in the
device code.
When using Real-time Flow Manager only
• Switch the operating status to STOP, and then switch it back to RUN.
When using Management Shell only
• Stop the operation and then start it again.
When using Real-time Flow Manager and Management Shell
Perform the following procedure.
 Switch the operating status of Real-time Flow Manager to STOP.
 Stop the operation of Management Shell, and then start it again.
 Switch the operating status of Real-time Flow Manager to RUN.

6 TROUBLESHOOTING
6.2 Troubleshooting by Symptom 59
Check point Corrective action
Has a packet loss error (error code: 1932H) Check the cumulative number of occurrences and the elapsed time displayed in the detailed
occurred? information. If a packet loss occurs frequently*1, take the following corrective actions since the
Ethernet line may be unstable:
• Review the access target device or communication path.
• Reduce frequency of access to a device and amount of communication data.
• Separate the communication path between this product and other software.
• Reduce communication to be simultaneously executed for one access target device.
For details on a packet loss, refer to the following:
Page 37 Packet loss

*1 It refers to either of the following cases:


A packet has been lost 50 times or more in total.
A packet get lost again within an hour after the previous loss.

Data inconsistency has occurred in read data.


Check point Corrective action
Does the number of points for a single data reading Set the number of device points to be read which does not cause data inconsistency.
exceed that of points in which no data inconsistency Page 35 Data inconsistency
occurs?

Data missing has occurred in collected data.


Check point Corrective action
Has an exceeded collection cycle (event code: • Review the communication parameters.
F800H) occurred? • Check the statuses of a communication cable and access target device.
• Review whether the access target device is supported.
• Check the configuration of an access target device.
Reduction methods when the network load is high
• Reduce frequency of access to a device and amount of communication data.
• Separate the communication path between this product and other software.
• Reduce communication to be simultaneously executed for one access target device.
Has a packet loss error (error code: 1932H) Check the cumulative number of occurrences and the elapsed time displayed in the detailed
occurred? information. If a packet loss occurs frequently*1, take the following corrective actions since the
Ethernet line may be unstable:
• Review the access target device or communication path.
• Reduce frequency of access to a device and amount of communication data.
• Separate the communication path between this product and other software.
• Reduce communication to be simultaneously executed for one access target device.
For details on a packet loss, refer to the following:
Page 37 Packet loss

*1 It refers to either of the following cases:


A packet has been lost 50 times or more in total.
A packet get lost again within an hour after the previous loss.

Unintended data has been read.


Check point Corrective action
Is an address of a file register (ZR or R) which does Review the addresses of file registers (ZR and R) in location parameters. (If an address does not exist
not exist in the access target device specified? in the access target devices, an invalid value (FFFFH, -1, etc.) may be read out.)
Is a device number which does not exist in the access Check the device number range for the access target device and set the number within the range. (If
target device specified? the device number does not exist in the access target device, an invalid value (FFFFH, -1, etc.) may be
read out.)
Does the radix of a device to be read match to the one Check the radix of a device specified for the device number in the manual for an access target device.
set for "Device number" in the location parameters? Then, set the same value as the checked radix for the one in "Device number" of the location
parameters.
Does the device type of a device to be read match to Check the device type specified for the device code in the manual for an access target device. Then,
the one set in the location parameters? set the same value as the checked device type for "Device type" in the location parameters.
Does the request destination module I/O number of Set the same value to the request destination module I/O number of the access target device and the
an access target device match to the one set in the one in target device setting.
target device setting?

6 TROUBLESHOOTING
60 6.2 Troubleshooting by Symptom
Troubleshooting on data writing

Data cannot be written.


Check point Corrective action
Is the initial access delay time set? • Wait until the set initial access delay time elapses.
• Set the initial access delay time shorter.
Is a corresponding device value operated by using a Do not operate device values by using a MELSEC device at the timing of data writing from a data
MELSEC device? collector.
Has an error detected on the target device (error Check the error code of the target device shown in 'Data Collector Detail Information'. Then, take
code: 1A02H) occurred when "SLMP connection" is corrective actions according to the end codes returned to an access target device during data
selected for "Connection type"? communications, which are given in the manual of the access target device.
Has a writing error occurred in Edgecross Basic • Decrease the number of points for data writing.
Software even though there is no error in this • Check the status of an access target device.
product? • Check whether the path to an access target device is correct.
• Review the devices and paths on the access path.
Is a remote password set to an access target device? • Set the remote password specified in the access target device in the communication parameters.
• Disable the remote password setting.
Has an communication parameter mismatch error Find the target device settings whose "Connection Type" is set to "SLMP connection" and both IP
(error code: 1A0CH to 1A13H) occurred even though address and port number are duplicated with others in Management Shell Explorer. Then, set all of the
there is only one target device setting registered in communication parameter items the same as the ones of target device settings in Real-time Flow 6
Real-time Flow Designer? Designer.
Page 40 Considerations
Has an communication parameter mismatch error Find the target device settings whose "Connection Type" is set to "SLMP connection" and both IP
(error code: 1A0CH to 1A13H) occurred even though address and port number are duplicated with others in Real-time Flow Designer. Then, set all of the
there is only one target device setting registered in communication parameter items the same as the ones of target device settings in Management Shell
Management Shell? Explorer.
Page 40 Considerations
Does the radix of a device to be written match to the Check the radix of a device specified for the device number in the manual for an access target device.
one set for "Device number" in the location Then, set the same value as the checked radix for the one in "Device number" of the location
parameters? parameters.
Does the device type of a device to be written match Check the device type specified for the device code in the manual for an access target device. Then,
to the one set in the location parameters? set the same value as the checked device type for "Device type" in the location parameters.
Does the request destination module I/O number of Set the same value to the request destination module I/O number of the access target device and the
an access target device match to the one set in the one in target device setting.
target device setting?
Has a data collector internal error (error code: 1A00H) Check the location parameter where an error has occurred, and clear the error.
occurred? For the checking method, refer to the following:
Page 51 Considerations
Has a location parameter setting error (unmatch of • Review all the location parameters used for an access target device where an error has occurred.
device type and device code) (error code: 1A14H) • Correct all the location parameters used for an access target device where an error has occurred so
occurred when "SLMP connection" is selected for that their settings match to the device type and device code given in the manual of the access target
"Connection type"? device.
• When multiple devices with a same device code are set as access targets, match the case in the
device code.
When using Real-time Flow Manager only
• Switch the operating status to STOP, and then switch it back to RUN.
When using Management Shell only
• Stop the operation and then start it again.
When using Real-time Flow Manager and Management Shell
Perform the following procedure.
 Switch the operating status of Real-time Flow Manager to STOP.
 Stop the operation of Management Shell, and then start it again.
 Switch the operating status of Real-time Flow Manager to RUN.
Has a packet loss error (error code: 1932H) Check the cumulative number of occurrences and the elapsed time displayed in the detailed
occurred? information. If a packet loss occurs frequently*1, take the following corrective actions since the
Ethernet line may be unstable:
• Review the access target device or communication path.
• Reduce frequency of access to a device and amount of communication data.
• Separate the communication path between this product and other software.
• Reduce communication to be simultaneously executed for one access target device.
For details on a packet loss, refer to the following:
Page 37 Packet loss

*1 It refers to either of the following cases:


A packet has been lost 50 times or more in total.

6 TROUBLESHOOTING
6.2 Troubleshooting by Symptom 61
A packet get lost again within an hour after the previous loss.

Unintended data has been written.


Check point Corrective action
Does the radix of a device to be written match to the one set for "Device Check the radix of a device specified for the device number in the manual for
number" in the location parameters? an access target device. Then, set the same value as the checked radix for
the one in "Device number" of the location parameters.
Does the device type of a device to be written match to the one set in the Check the device type specified for the device code in the manual for an
location parameters? access target device. Then, set the same value as the checked device type for
"Device type" in the location parameters.

Troubleshooting on Ethernet communication

Ethernet communication to a MELSEC device cannot be established.


Issue a ping from the industrial PC to the MELSEC device and check the response.

Failure in the ping response


Check item Corrective action
Is the Ethernet cable wired correctly? Wire the Ethernet cable correctly.
Is the Ethernet cable disconnected? Replace the Ethernet cable.
Is there an IP address duplicating with that of the industrial PC or MELSEC Contact the network administrator of the connected LAN and change the
device in the connected LAN. duplicate IP address.
Has the industrial PC in which this product was installed been replaced? Reset all devices connected in the network.
Is the network highly loaded? • Contact the network administrator of the connected LAN and disconnect
other devices connected via Ethernet of high load.
• Change the network used for connecting the industrial PC with MELSEC
devices to another network.
Is the specified IP address correct? Specify the correct IP address.
Is the connection prevented by the security setting of the MELSEC device? • Delete the applicable IP address in the IP filter setting of the security setting
of the MELSEC device.
• Set the security setting of the MELSEC device so that the IP filter function is
not used.

No failure in the ping response


Check item Corrective action
Is the Ethernet cable reconnected? • Wait until the time which is set in the timer setting for data exchange of the
MELSEC device elapses, then connect it again.
• Set the time which is set in the timer setting for data exchange of the
MELSEC device shorter.

6 TROUBLESHOOTING
62 6.2 Troubleshooting by Symptom
Ethernet communication to an SLMP-compatible device cannot be established.
Issue a ping from the industrial PC to the SLMP-compatible device and check the response.

Failure in the ping response


Check item Corrective action
Is the Ethernet cable wired correctly? Wire the Ethernet cable correctly.
Is the Ethernet cable disconnected? Replace the Ethernet cable.
Is there an IP address duplicated with that of the industrial PC or SLMP- Contact the network administrator of the connected LAN and change the
compatible device in the connected LAN? duplicate IP address.
Has the industrial PC in which this product was installed been replaced? Reset all devices connected in the network.
Is the network highly loaded? • Contact the network administrator of the connected LAN and disconnect
other devices connected via Ethernet of high load.
• Change the connection of the industrial PC and an SLMP-compatible
device to another network.
Is the specified IP address correct? Specify the correct IP address.

If the problem persists, refer to the user's manual of the SLMP-compatible device.

No failure in the ping response


Check item Corrective action 6
Has the communication failed even if the operation status of Real-time Flow Switch the status to RUN again after the existence check*1 of an SLMP-
Manager was switched to RUN after it was switched to STOP in the "Real-time compatible device is finished.
Flow Manager Diagnostics" screen of Real-time Flow Designer?
Has the communication failed even after the reconnection operation was Perform the reconnection operation again after the existence check*1 of an
performed in the "Target Device Setting List" screen of Management Shell SLMP-compatible device is finished.
Explorer?
Has an error detected on the target device (error code: 1A02H) or a data send/ • Check the IP address set in an SLMP-compatible device, and set the same
receive error (error code: 1A09H) occurred? IP address in the communication parameters.
• Check the port number set in an SLMP-compatible device, and set the
same port number in communication parameters.
• Check the communication frame set in an SLMP-compatible device, and set
the same communication frame in communication parameters.
• Check the command supported by an SLMP-compatible device, and set the
same command in the communication parameters.

*1 It refers to the existence check function performed on the SLMP-compatible device side. Since the TCP communication port is occupied
on the SLMP-compatible device side, Ethernet communication from the data collector cannot be established.
If the problem persists, refer to the user's manual of the SLMP-compatible device.

6 TROUBLESHOOTING
6.2 Troubleshooting by Symptom 63
Troubleshooting on parameter settings

The Target Device Setting screen


Unable to change the device type
Message Check item Corrective action
The device type cannot be changed. Is an X/Y device specified for a process flow of For Real-time Flow Designer *2
An inconvertible device memory is specified in the Real-time Flow Designer or for an external data tag Set parameters according to the following
setting of the Target Device of this setting. resource of Management Shell Explorer? procedure.
Please change the device type after deleting the Alternatively, is an access target device to be  In the "Data Collection Setting" screen or the
specification of the inconvertible device memory: changed being used? "Instruction Feedback Setting" screen, replace the
X,Y. X/Y device of "Location (top)" with a bit device
other than X/Y.
Example: When "X0" is set for "Location (top)",
replace it with "M0".
 In the "Target Device Setting" screen, change
the device type.
 In the "Data Collection Setting" screen or the
"Instruction Feedback Setting" screen, restore the
device in "Location (top)" to the original device.
For Management Shell*2
Set parameters according to the following
procedure.
 In the "Edit External Data Tag Resource"
screen, replace the X/Y device of "Location (top)"
with a bit device other than X/Y.
Example: When "X0" is set for "Location (top)",
replace it with "M0".
 In the "Target Device Setting" screen, change
the device type.
 In the "Edit External Data Tag Resource"
screen, restore the device in "Location (top)" to the
original device.
*1 cannot be changed. Is an access target device to be changed being For Real-time Flow Designer *2
This Target Device Setting is used by other setting. used for a process flow of Real-time Flow Designer By following the procedure below, set parameters
Please change *1 after deleting data used by or for an external data tag resource of of a process flow that is using an access target
other setting. Management Shell Explorer? device to be changed to use a newly added access
target device.
 Add a new target device setting in the "Target
Device Setting" screen.
 Change the set target device setting to the one
added in step  in the "Data Collection Setting"
and "Instruction Feedback Setting" screens.
 Review settings for the following items.
• "Data Collection Setting" screen:
"Collection Data" and "Collection Option"
• "Instruction Feedback Setting" screen:
"Instruction Target data"
 Delete the old target device setting in the
"Target Device Setting" screen.
For Management Shell*2
By following the procedure below, set parameters
of an external data tag resource that is using an
access target device to be changed to use a newly
added access target device.
 Add a new target device setting in the "Target
Device Setting" screen.
 Change the set target device setting to the one
added in step  in the "Edit External Data Tag
Resource" screen.
 Review settings for the following items.
• Location
• Data Type
• Number of characters
 Delete the old target device setting in the
"Target Device Setting" screen.

*1 : An setting item that cannot be changed is displayed.


*2 For details of each screen, refer to the following:

6 TROUBLESHOOTING
64 6.2 Troubleshooting by Symptom
Edgecross Basic Software for Windows User's Manual

Unable to change the connection type, communication frame, and command


Message Check item Corrective action
*1 cannot be changed. Is an access target device to be changed being For Real-time Flow Designer *2
This Target Device Setting is used by other setting. used for a process flow of Real-time Flow Designer By following the procedure below, set parameters
Please change *1 after deleting data used by or for an external data tag resource of of a process flow that is using an access target
other setting. Management Shell Explorer? device to be changed to use a newly added access
target device.
 Add a new target device setting in the "Target
Device Setting" screen.
 Change the set target device setting to the one
added in step  in the "Data Collection Setting"
and "Instruction Feedback Setting" screens.
 Review settings for the following items.
• "Data Collection Setting" screen:
"Collection Data" and "Collection Option"
• "Instruction Feedback Setting" screen:
"Instruction Target data"
 Delete the old target device setting in the
"Target Device Setting" screen.
For Management Shell*2
By following the procedure below, set parameters
of an external data tag resource that is using an
access target device to be changed to use a newly
6
added access target device.
 Add a new target device setting in the "Target
Device Setting" screen.
 Change the set target device setting to the one
added in step  in the "Edit External Data Tag
Resource" screen.
 Review settings for the following items.
• Location
• Data Type
• Number of characters
 Delete the old target device setting in the
"Target Device Setting" screen.

*1 : An setting item that cannot be changed is displayed.


*2 For details of each screen, refer to the following:
Edgecross Basic Software for Windows User's Manual

6 TROUBLESHOOTING
6.2 Troubleshooting by Symptom 65
Troubleshooting on Edgecross Basic Software

An error caused by this product has occurred in Edgecross Basic Software.


Check item Corrective action
Has a timeout error occurred in Edgecross Basic Software after operating the • Decrease the number of points for data collection.
software? • Decrease the number of points for data reading.
• Decrease the number of points for data writing.
• Check the status of an access target device.
• Check whether the path to an access target device is correct.
• Review the devices and paths on the access path.
Has a data collector startup error occurred in Edgecross Basic Software? Reinstall this product since the file may have been moved or deleted.

A message has been displayed in Edgecross Basic Software.


Message Check item Corrective action
This function can not be executed because the Is Edgecross Basic Software whose version is 1.01 or earlier Update Edgecross Basic Software to
Data collector used does not satisfy the being used? version 1.10 or later.
implementation requirements of Edgecross Page 109 Supported Edgecross Basic
specification. Software Version

6 TROUBLESHOOTING
66 6.2 Troubleshooting by Symptom
Troubleshooting on screens

Contents in the screen are not displayed properly.


Check item Corrective action
Is a value other than 100% set for "Change the size of text, apps, and other • Change the value to 100% for "Change the size of text, apps, and other
items" in Windows? items."
• For Windows 10 (version 1703 or later) or later*1, the display of a screen
can be enlarged with high DPI scaling by using a Windows function.*2
 Select 'ProcessDesigner.exe'*3, then select [Properties] on the right-click
menu.
 Select the checkbox of "Override high DPI scaling behavior. Scaling
performed by:" in the [Compatibility] tab, then select "System" from the pull-
down list.
 Click the [OK] button.

*1 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.
*2 The display 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 for
each setting value in Windows 10 or later.
Setting value: 100%, display resolution: 1024  768 dots or more 6
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
*3 '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

6 TROUBLESHOOTING
6.2 Troubleshooting by Symptom 67
6.3 Error Code List
This section shows the codes for errors that occur in SLMP Data Collector.
Error Error name Error description Corrective action
code
1800H Communication There is an error in the communication parameter. Please review the communication parameter because
parameter setting error there is an error.
1801H Collection parameter There is an error in the collection parameter. Please review the collection parameter because there is
setting error an error.
1802H Location parameter There is an error in the location parameter. Please review the location parameter because there is an
setting error error.
1804H Insufficient memory error There is not enough memory available to execute this • Please restart the Industrial PC running this product.
operation. • Please close other applications.
1805H Data Collector internal An error was detected in the operation of this product. • If Real-time Flow Manager is used, please write Real-
error time Flow Manager Parameter again.
• Please restart the Industrial PC running this product.
• Please close other applications.
• Please reinstall this product.
• If the same error occurs, a hardware error may have
occurred in the operating environment of this product.
Please consult your local Mitsubishi representative.
1806H Resource contention Resource contention has occurred between this product • Please restart the Industrial PC running this product.
error and other applications. • Please close other applications.
1807H Abnormal termination of Operation of the internal process of the Data Collector • Please restart the Industrial PC running this product.
internal process of Data has stopped. • Please close other applications.
Collector • Please review the number of Data Collector
configurations.
• Please consult your local Mitsubishi representative if
the same error occurs again.
1808H Abnormal Operation of the internal process of the Data Collector • Please restart the Industrial PC running this product.
communication between has stopped. • Please close other applications.
internal processes of • Please review the number of Data Collector
Data Collector configurations.
• Please consult your local Mitsubishi representative if
the same error occurs again.
1809H Failed to start internal Failed to start the internal process. • Please restart the Industrial PC running this product.
process • Please reinstall this product.
• Please consult your local Mitsubishi representative if
the same error occurs again.
180AH SLMP connection file Failed to create an SLMP connection file because there • Please delete unnecessary files in the Industrial PC
creating failure is not enough free space or there is no access authority running this product.
to the storage destination of SLMP Data Collector. • Please grant the SYSTEM user the access authority.
180BH Shared resource Failed to operate the shared resource. • If Real-time Flow Manager is used, please write the
operation error Real-time Flow Manager parameter again.
• Please restart the Industrial PC running this product.
• Please close other applications.
• Please review the number of Data Collector
configurations.
• Please reinstall this product.
• Please consult your local Mitsubishi representative if
the same error occurs again.
180CH Initialization error Initialization has failed. • If Real-time Flow Manager is used, please write the
Real-time Flow Manager parameter again.
• Please restart the Industrial PC running this product.
• Please close other applications.
• Please review the number of Data Collector
configurations.
• Please reinstall this product.
• Please consult your local Mitsubishi representative if
the same error occurs again.
1900H Unsupported device An unsupported device or path exists on the access path Please review the devices and paths on the access path.
error (incorrect for which the communication through the MELSEC
command) connection is performed.

6 TROUBLESHOOTING
68 6.3 Error Code List
Error Error name Error description Corrective action
code
1901H Target Device An error occurred upon access to the Target Device for • Please check whether the communication parameter is
communication error which the communication through the MELSEC correct.
connection is performed. • Please check the status of the Target Device.
• Please check whether the path to the Target Device is
correct.
• Please review the devices and paths on the access
path.
1902H Target Device error The setting value of the communication parameter using Please review the communication parameter.
(incorrect open the MELSEC connection is incorrect.
parameter)
1903H Target Device error The setting value of the communication parameter using Please review the communication parameter.
(incorrect port) the MELSEC connection is incorrect.
1904H Target Device error • A device which does not exist is specified in the • Please review the communication parameter.
(incorrect module) communication parameter using the MELSEC • Please review the devices and paths on the access
connection. path.
• An unsupported device or path exists on the access
path for which the communication through the
MELSEC connection is performed.
1905H Target Device error • A device which does not exist is specified in the • Please review the communication parameter.
(incorrect CPU) communication parameter using the MELSEC • Please review the devices and paths on the access
connection.
• An unsupported device or path exists on the access
path.
6
path for which the communication through the
MELSEC connection is performed.
1906H Target Device error An inaccessible device is specified in the communication Please review the communication parameter.
(incorrect target station) parameter using the MELSEC connection.
1907H Device memory type The device memory type that does not exist is specified Please review the device memory type specified in the
error for the Target Device for which the communication location parameter.
through the MELSEC connection is performed. (Or, the
device memory exceeds the allowable range.)
1908H Device memory No. The device memory No. that does not exist is specified • Please review the device memory No. specified in the
error for the Target Device for which the communication location parameter.
through the MELSEC connection is performed. • Please review the device memory type specified in the
location parameter.
If Real-time Flow Manager is used
• Please perform the STOP operation with Real-time
Flow Designer, and then perform the RUN operation
again.
If Management Shell is used
• Please select the Target Device and press the
reconnect button with Management Shell Explorer.
1909H Target Device An error occurred upon access to the Target Device for • Please check whether the communication parameter is
communication error which the communication through the MELSEC correct.
(incorrect program type) connection is performed. • Please check the status of the Target Device.
• Please check whether the path to the Target Device is
correct.
• Please check whether there is any problem in the path
to the Target Device.
190AH Data reception error Failed to receive data from the Target Device for which Please review the devices and paths on the access path.
the communication through the MELSEC connection is
performed. (A sum-check error occurred during
communication.)
190BH Size error The device memory specified for the Target Device for Please review the device memory No. specified in the
which the communication through the MELSEC location parameter.
connection is performed exceeds the allowable range.
190CH Block error An invalid block No. of the extended file register is Please review the block No. (device memory type) of the
specified for the Target Device for which the extended file register.
communication through the MELSEC connection is
performed.
190DH Data reception error Failed to receive data from the Target Device for which Please review the devices and paths on the access path.
the communication through the MELSEC connection is
performed. (Invalid data is received.)

6 TROUBLESHOOTING
6.3 Error Code List 69
Error Error name Error description Corrective action
code
190EH Write protection error A block No. of the extended file register within the write • Please review the block No. (device memory type) of
protection area of the memory cassette is specified for the extended file register.
the Target Device for which the communication through • Please review the write protection dip switch of the
the MELSEC connection is performed. memory cassette of the Target Device.
190FH Device type unmatched A device type different from the one of the actual Target Please review the communication parameter.
error Device is specified in the communication parameter
using the MELSEC connection.
1910H Station number An incorrect station number is specified in the Please review the communication parameter.
specification error communication parameter using the MELSEC
connection.
1911H ROM operation error The TC setting value was written to the CPU module Please change the TC setting value while RAM is
where ROM is running for which the communication running.
through the MELSEC connection is performed.
1913H Data reception error Failed to receive data from the Target Device for which Please review the devices and paths on the access path.
the communication through the MELSEC connection is
performed. (An error occurred in the motion CPU.)
1914H Data reception error Failed to receive data from the Target Device for which Please review the devices and paths on the access path.
the communication through the MELSEC connection is
performed. (An error occurred during communication to
motion CPU.)
1915H Communication An incorrect IP address is specified in the communication • Please review the IP address of the communication
parameter error (IP parameter using the MELSEC connection. parameter.
address) • Please check the IP address of the Target Device.
• Please review the devices and paths on the access
path.
1916H Target Device The incorrect data was received from the Target Device • Please review the communication parameter.
communication receiving for which the communication through the MELSEC • Please check the status of the Target Device or path.
data error (incorrect connection is performed.
packet CRC)
1917H Target Device The incorrect data was received from the Target Device • Please review the communication parameter.
communication receiving for which the communication through the MELSEC • Please check the status of the Target Device or path.
data error (incorrect data connection is performed.
CRC)
1918H Unsupported device An unsupported device or path exists on the access path Please review the devices and paths on the access path.
error (connection to FX for which the communication through the MELSEC
PLC imitations) connection is performed.
1919H Data reception error Multiple responses were received during the direct Please check if the configuration is 1 to 1 direct
Ethernet communication using the MELSEC connection. connection with a module.
191AH Target Device status Communication failed because other devices Please check if the configuration is 1 to 1 direct
error communicate with the industrial PC during direct connection with a module.
Ethernet communication using the MELSEC connection.
191BH Communication An incorrect station number or network number is • Please review the content (station number/network
parameter error (station specified in the communication parameter using the No.) of the communication parameter.
number/network No.) MELSEC connection. • Please check the device configuration of the Target
Device (station number/network No.).
191CH Target Device An incorrect IP address is specified in the communication • Please review the IP address of the communication
communication parameter using the MELSEC connection. parameter.
connection error (IP • Please check the IP address of the Target Device.
address) • Please review the devices and paths on the access
path.
191DH Target Device There is no response from the Target Device for which • Please check the status of the Target Device.
communication timeout the communication through the MELSEC connection is • Please review the communication parameter.
error performed. • Please adjust the response monitoring time of the
Target Device.
• Please review the devices and paths on the access
path.
191EH Data transmission error Failed to send data to the Target Device for which the Please review the devices and paths on the access path.
communication through the MELSEC connection is
performed. (Windows failed to send data.)
191FH Data transmission error Failed to send data to the Target Device for which the Please review the devices and paths on the access path.
communication through the MELSEC connection is
performed. (Send data size error.)

6 TROUBLESHOOTING
70 6.3 Error Code List
Error Error name Error description Corrective action
code
1920H Data transmission error Failed to send data to the Target Device for which the Please review the devices and paths on the access path.
communication through the MELSEC connection is
performed. (Queue clear error.)
1921H Data reception error Failed to receive data from the Target Device for which Please review the devices and paths on the access path.
the communication through the MELSEC connection is
performed. (Windows failed to receive data.)
1922H Data reception error Failed to receive data from the Target Device for which Please review the devices and paths on the access path.
the communication through the MELSEC connection is
performed. (An error occurred by attempt to receive data
before send data.)
1923H Data reception error Failed to receive data from the Target Device for which Please review the devices and paths on the access path.
the communication through the MELSEC connection is
performed. (Message queue receive error.)
1924H Data reception error Failed to receive data from the Target Device for which Please review the devices and paths on the access path.
the communication through the MELSEC connection is
performed. (Insufficient size of the read buffer.)
1925H Response timeout error There is no response from the Target Device for which • Please review the communication parameter.
the communication through the MELSEC connection is • Please check the status of the Target Device or path.
performed. • Please review if the Target Device is supported.
• Please check the device configuration of the Target
Device. 6
If the load on the network is high, please reduce the
load.
• Reduction of access frequency to device, amount of
communication data.
• Separation of communication path of this product and
communication path of other software.
• Reduction of communication to be simultaneously
executed for one Target Device.
1927H Error detected on the An error occurred in the Target Device for which the Please check the error code of the Target Device in the
Target Device communication through the MELSEC connection is user's manual of the Target Device.
performed.
192AH Error detected on the An error occurred in the module with Ethernet for which Please check the error shown on the error code of the
module with Ethernet the communication through the MELSEC connection is Target Device in the user’s manual of the module with
performed. Ethernet.
192EH Target Device An error occurred upon access to the Target Device for • Please check whether the communication parameter is
communication error which the communication through the MELSEC correct.
(other) connection is performed. • Please check the status of the Target Device.
• Please check whether the path to the Target Device is
correct.
• Please review the devices and paths on the access
path.
192FH Communication driver Failed to initialize the communication driver for the • Please restart the Industrial PC running this product.
initialization error MELSEC connection. • Please reinstall this product.
• Please consult your local Mitsubishi representative if
the same error occurs again.
1930H Error detected in the An error occurred in the Target Device or communication Please check the error shown on the error code of the
Target Device or module for which the communication through the Target Device in the user's manual of the Target Device
communication module MELSEC connection is performed. or communication module.
1931H Remote password An incorrect remote password is set in the Set the remote password set in the Target Device to the
setting error communication parameters using the MELSEC one for the communication parameters.
connection.
1932H Packet loss error A packet loss occurred in the data communication with • Please check the status of the Target Device or path.
the Target Device for which the communication through If the load on the network is high, please reduce the
the MELSEC connection is performed. load.
• Reduction of access frequency to device, amount of
communication data.
• Separation of communication path of this product and
communication path of other software.
• Reduction of communication to be simultaneously
executed for one Target Device.

6 TROUBLESHOOTING
6.3 Error Code List 71
Error Error name Error description Corrective action
code
1A00H Data Collector internal An error was detected in the operation of this product • If Real-time Flow Manager is used, please write Real-
error during the communication through the SLMP connection. time Flow Manager Parameter again.
• Please restart the industrial PC running this product.
• Please close other applications.
• Please reinstall this product.
• If the same error occurs, a hardware error may have
occurred in the operating environment of this product.
Please consult your local Mitsubishi representative.
1A01H Target Device incorrect An inaccessible device is set in the communication • Please review the communication parameter.
error parameters using the SLMP connection. • Please review the location parameter.
• Please restart the Industrial PC running this product.
• Please reinstall this product.
• Please consult your local Mitsubishi representative if
the same error occurs again.
1A02H Error detected on the An error occurred in the Target Device for which the Check the measures with the error code displayed on the
Target Device communication through the SLMP connection is Target Device in the user's manual of the Target Device
performed. and perform it.
1A04H Insufficient memory error Failed to secure the memory required for the • Please restart the Industrial PC running this product.
communication through the SLMP connection. • Please close other applications.
1A09H Data send/receive error Failed to send/receive data to/from the Target Device for • Please check the status of the Target Device.
which the communication through the SLMP connection • Please review the communication parameters.
is performed. • The communication between other device and the
Target Device may be interfered. Please check if the
connection to the same port of the same IP address
with other device is not performed.
• Please review the devices and paths on the access
path.
If the existence check function is enabled in the Target
Device
• Establish the connection again after the existence
check of the Target Device is finished.
• Please review the timer setting for data communication
of the Target Device.
1A0AH Target Device There is no response from the Target Device for which • Please check the status of the Target Device.
communication timeout the communication through the SLMP connection is • Please review the communication parameter.
error performed. • Please adjust the response monitoring time of the
Target Device.
• Please review the devices and paths on the access
path.
1A0BH Target Device There is no response from the Target Device for which • Please review the communication parameters.
connection error the communication through the SLMP connection is • The communication between other device and the
performed. Target Device may be interfered. Please check if the
connection to the same port of the same IP address
with other device is not performed.
1A0CH Communication There are multiple settings to connect to the same IP • When there are multiple settings to connect to the
parameter mismatch address and port in the communication parameters using same IP address and port in the communication
error (Time-out Time) the SLMP connection, and the setting of the Time-out parameters using the SLMP connection, set the Time-
Time differs among those multiple communication out Time of all the multiple communication parameters
parameters. to the same value.
• Check that Real-time Flow Manager and Management
Shell have the same Target Device setting. When there
are multiple settings to connect to the same IP address
and port regardless of Real-time Flow Designer and
Management Shell Explorer, set the Time-out Time of
all the multiple communication parameters to the same
value.

6 TROUBLESHOOTING
72 6.3 Error Code List
Error Error name Error description Corrective action
code
1A0DH Communication There are multiple settings to connect to the same IP • When there are multiple settings to connect to the
parameter mismatch address and port in the communication parameters using same IP address and port in the communication
error (Communication the SLMP connection, and the setting of the parameters using the SLMP connection, set the
frame) Communication frame differs among those multiple Communication frame of all the multiple
communication parameters. communication parameters to the same value.
• Check that Real-time Flow Manager and Management
Shell have the same Target Device setting. When there
are multiple settings to connect to the same IP address
and port regardless of Real-time Flow Designer and
Management Shell Explorer, set the Communication
frame of all the multiple communication parameters to
the same value.
1A0EH Communication There are multiple settings to connect to the same IP • When there are multiple settings to connect to the
parameter mismatch address and port in the communication parameters using same IP address and port in the communication
error (Request the SLMP connection, and the setting of the Request parameters using the SLMP connection, set the
destination module I/O destination module I/O No. differs among those multiple Request destination module I/O No. of all the multiple
No.) communication parameters. communication parameters to the same value.
• Check that Real-time Flow Manager and Management
Shell have the same Target Device setting. When there
are multiple settings to connect to the same IP address
and port regardless of Real-time Flow Designer and
Management Shell Explorer, set the Request
destination module I/O No. of all the multiple
6
communication parameters to the same value.
1A0FH Communication There are multiple settings to connect to the same IP • When there are multiple settings to connect to the
parameter mismatch address and port in the communication parameters using same IP address and port in the communication
error (Command) the SLMP connection, and the setting of the Command parameters using the SLMP connection, set the
differs among those multiple communication parameters. Command of all the multiple communication
parameters to the same value.
• Check that Real-time Flow Manager and Management
Shell have the same Target Device setting. When there
are multiple settings to connect to the same IP address
and port regardless of Real-time Flow Designer and
Management Shell Explorer, set the Command of all
the multiple communication parameters to the same
value.
1A10H Communication There are multiple settings to connect to the same IP • When there are multiple settings to connect to the
parameter mismatch address and port in the communication parameters using same IP address and port in the communication
error (Retry Count) the SLMP connection, and the setting of the Retry Count parameters using the SLMP connection, set the Retry
differs among those multiple communication parameters. Count of all the multiple communication parameters to
the same value.
• Check that Real-time Flow Manager and Management
Shell have the same Target Device setting. When there
are multiple settings to connect to the same IP address
and port regardless of Real-time Flow Designer and
Management Shell Explorer, set the Retry Count of all
the multiple communication parameters to the same
value.
1A11H Communication There are multiple settings to connect to the same IP • When there are multiple settings to connect to the
parameter mismatch address and port in the communication parameters using same IP address and port in the communication
error (Initial Access the SLMP connection, and the setting of the Initial parameters using the SLMP connection, set the Initial
Delay Time) Access Delay Time differs among those multiple Access Delay Time of all the multiple communication
communication parameters. parameters to the same value.
• Check that Real-time Flow Manager and Management
Shell have the same Target Device setting. When there
are multiple settings to connect to the same IP address
and port regardless of Real-time Flow Designer and
Management Shell Explorer, set the Initial Access
Delay Time of all the multiple communication
parameters to the same value.

6 TROUBLESHOOTING
6.3 Error Code List 73
Error Error name Error description Corrective action
code
1A12H Communication There are multiple settings to connect to the same IP • When there are multiple settings to connect to the
parameter mismatch address and port in the communication parameters using same IP address and port in the communication
error (Request the SLMP connection, and the setting of the Request parameters using the SLMP connection, set the
destination network No.) destination network No. differs among those multiple Request destination network No. of all the multiple
communication parameters. communication parameters to the same value.
• Check that Real-time Flow Manager and Management
Shell have the same Target Device setting. When there
are multiple settings to connect to the same IP address
and port regardless of Real-time Flow Designer and
Management Shell Explorer, set the Request
destination network No. of all the multiple
communication parameters to the same value.
1A13H Communication There are multiple settings to connect to the same IP • When there are multiple settings to connect to the
parameter mismatch address and port in the communication parameters using same IP address and port in the communication
error (Request the SLMP connection, and the setting of the Request parameters using the SLMP connection, set the
destination station No.) destination station No. differs among those multiple Request destination station No. of all the multiple
communication parameters. communication parameters to the same value.
• Check that Real-time Flow Manager and Management
Shell have the same Target Device setting. When there
are multiple settings to connect to the same IP address
and port regardless of Real-time Flow Designer and
Management Shell Explorer, set the Request
destination station No. of all the multiple
communication parameters to the same value.
1A14H Location parameter There is an error in the location parameter using SLMP • Please review all location parameter using this access
setting error (unmatch of connection. target device in Real-time Flow Manager and
device type and device There is an unmatch with set device type and device Management Shell.
code) code. • Please match device type and device code explained
Communication with this access target device has in the manual of access target device with location
stopped because location cannot be connected normally. parameter of this access target device setting.
In the case using Real-time Flow Manager
• Please execute STOP operation with Real-time Flow
Designer, then execute RUN operation again.
In the case using Management Shell
• Please execute stop operation with Management Shell
Explorer, then execute start operation again.
In the case using Real-time Flow Manager and
Management Shell
• Please execute STOP operation with Real-time Flow
Designer.
• Please execute stop operation with Management Shell
Explorer, then execute start operation again.
• Please execute RUN operation again.
F001H Data Collector I/F error An error occurred during the access to Edgecross Basic • Please restart the Industrial PC.
Software. • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F002H Data Collector I/F error An error occurred during the access to Edgecross Basic • Please restart the Industrial PC.
Software. • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F003H Data Collector I/F error An error occurred during the access to Edgecross Basic • Please restart the Industrial PC.
Software. • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F004H Data Collector I/F error An error occurred during the access to Edgecross Basic • Please restart the Industrial PC.
Software. • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F005H Data Collector I/F error An error occurred during the access to Edgecross Basic • Please restart the Industrial PC.
Software. • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F006H Data Collector I/F error An error occurred during the access to Edgecross Basic • Please restart the Industrial PC.
Software. • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.

6 TROUBLESHOOTING
74 6.3 Error Code List
Error Error name Error description Corrective action
code
F007H Data Collector I/F error An error occurred during the access to Edgecross Basic • Please restart the Industrial PC.
Software. • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F008H Data Collector I/F error An error occurred during the access to Edgecross Basic • Please restart the Industrial PC.
Software. • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F009H Data Collector I/F error An error occurred during the access to Edgecross Basic • Please restart the Industrial PC.
Software. • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F00AH Data Collector I/F error An error occurred during the access to Edgecross Basic • Please restart the Industrial PC.
Software. • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F00BH Data Collector I/F error An error occurred during the access to Edgecross Basic • Please restart the Industrial PC.
Software. • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F00CH Data Collector I/F error An error occurred during the access to Edgecross Basic • Please restart the Industrial PC. 6
Software. • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F00DH Data Collector I/F error An error occurred during the access to Edgecross Basic • Please restart the Industrial PC.
Software. • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F00EH Data Collector I/F error An error occurred during the access to Edgecross Basic • Please restart the Industrial PC.
Software. • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F00FH Data Collector I/F error An error occurred during the access to Edgecross Basic • Carry out review to lower the load caused by collection
Software. cycle, number of collections, and contents of
processing.
• Lower the load on Windows by closing other
applications or by other means.
• Please restart the Industrial PC.
• Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F010H Data Collector I/F error An error occurred during the access to Edgecross Basic • Please restart the Industrial PC.
Software. • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F011H Data Collector I/F error An error occurred during the access to Edgecross Basic • Please restart the Industrial PC.
Software. • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F012H Data Collector I/F error An error occurred during the access to Edgecross Basic • Please restart the Industrial PC.
Software. • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F013H Data Collector I/F error An error occurred during the access to Edgecross Basic • Please restart the Industrial PC.
Software. • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F100H Error in the initialization An error occurred in the initialization process. • Please restart the Industrial PC.
process of Data • Please reinstall Data Collector.
Collector • Please consult your local Mitsubishi representative if
the same error occurs again.
F104H Error in the initialization An error occurred in the initialization process. • Please restart the Industrial PC.
process of Data • Please reinstall Data Collector.
Collector • Please consult your local Mitsubishi representative if
the same error occurs again.

6 TROUBLESHOOTING
6.3 Error Code List 75
Error Error name Error description Corrective action
code
F105H Error in the initialization An error occurred in the initialization process. • Please restart the Industrial PC.
process of Data • Please reinstall Data Collector.
Collector • Please consult your local Mitsubishi representative if
the same error occurs again.
F106H Error in the collection An error occurred in the collection process. • Please restart the Industrial PC.
process of Data • Please reinstall Data Collector.
Collector • Please consult your local Mitsubishi representative if
the same error occurs again.
F107H Error in the read process An error occurred in the read process. • Please restart the Industrial PC.
of Data Collector • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F108H Error in the write process An error occurred in the write process. • Please restart the Industrial PC.
of Data Collector • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F109H Error in the read process An error occurred in the read process. • Please restart the Industrial PC.
of Data Collector • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F10AH Error in the write process An error occurred in the write process. • Please restart the Industrial PC.
of Data Collector • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F200H Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F205H Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F207H Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F20AH Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F20BH Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F20CH Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F20DH Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F20EH Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F20FH Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F212H Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.

6 TROUBLESHOOTING
76 6.3 Error Code List
Error Error name Error description Corrective action
code
F217H Error in module An error occurred when the module (JSON parser) was • Please reinstall Data Collector.
reference referenced. • Please consult your local Mitsubishi representative if
the same error occurs again.
F218H Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F219H Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F21AH Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F21BH Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F21CH Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector. 6
• Please consult your local Mitsubishi representative if
the same error occurs again.
F21EH Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F221H Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F223H Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F227H Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F228H Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F229H Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F22AH Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F22BH Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F22DH Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F22FH Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.

6 TROUBLESHOOTING
6.3 Error Code List 77
Error Error name Error description Corrective action
code
F232H Data Collector I/F error An error occurred during the access to Edgecross Basic • Please restart the Industrial PC.
Software. • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F233H Data Collector I/F error An error occurred during the access to Edgecross Basic • Please restart the Industrial PC.
Software. • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F234H Data Collector I/F error An error occurred during the access to Edgecross Basic • Please restart the Industrial PC.
Software. • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F240H Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F242H Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F244H Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F245H Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F247H Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F248H Data reference error in An error occurred when the argument of the • Please restart the Industrial PC.
Data Collector communication parameter acquisition was referenced. • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F249H Data reference error in An error occurred when the argument of the collection • Please restart the Industrial PC.
Data Collector parameter acquisition was referenced. • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F24AH Data reference error in An error occurred when the argument of the data • Please restart the Industrial PC.
Data Collector parameter acquisition was referenced. • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F24CH Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F24DH Process data buffer Data buffering has overflowed. • Carry out review to lower the load caused by collection
overflow in Data cycle, number of collections, and contents of
Collector processing.
• Lower the load on Windows by closing other
applications or by other means.
F24EH Process data buffer Data buffering has overflowed. • Carry out review to lower the load caused by collection
overflow in Data cycle, number of collections, and contents of
Collector processing.
• Lower the load on Windows by closing other
applications or by other means.
F260H Error: Character is out of The character string acquired from the Data Collector Please do not set characters out of range to collected
range contains characters out of range. STRING type character string.
F261H Error: Character is out of The character string acquired from the Data Collector Please do not set characters out of range to read
range contains characters out of range. STRING type character string.

6 TROUBLESHOOTING
78 6.3 Error Code List
Error Error name Error description Corrective action
code
F262H Error: Number of It exceeds the maximum number of character string • Please review the location parameter so that the
characters exceeded acquired from the Data Collector. number of characters in the collected STRING type
character string does not exceed the maximum
number.
• Please review the Target Device value so that the
number of characters in the collected STRING type
character STRING does not exceed the maximum
number.
F263H Error: Number of It exceeds the maximum number of character string • Please review the location parameter so that the
characters exceeded acquired from the Data Collector. number of characters in the read STRING type
character string does not exceed the maximum
number.
• Please review the Target Device value so that the
number of characters in the read STRING type
character STRING does not exceed the maximum
number.
F264H Error: Character is out of The character string acquired from the Data Collector Please do not set characters out of range to collected
range contains characters out of range. WSTRING type character string.
F265H Error: Character is out of The character string acquired from the Data Collector Please do not set characters out of range to read
range contains characters out of range. WSTRING type character string.
F266H Error: Number of
characters exceeded
It exceeds the maximum number of character string
acquired from the Data Collector.
• Please review the location parameter so that the
number of characters in the collected WSTRING type
6
character string does not exceed the maximum
number.
• Please review the Target Device value so that the
number of characters in the collected WSTRING type
character STRING does not exceed the maximum
number.
F267H Error: Number of It exceeds the maximum number of character string • Please review the location parameter so that the
characters exceeded acquired from the Data Collector. number of characters in the read WSTRING type
character string does not exceed the maximum
number.
• Please review the Target Device value so that the
number of characters 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 Please do not set invalid value(NaN, ) to read REAL
invalid(NaN, ). type real number.
F269H Invalid real number data The real number acquired from the Data Collector is Please do not set invalid value(NaN, ) to read LREAL
invalid(NaN, ). type real number.
F280H Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F281H Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F282H Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F283H Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F284H Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F2C5H Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.

6 TROUBLESHOOTING
6.3 Error Code List 79
Error Error name Error description Corrective action
code
F2C6H Process data buffer Data buffering has overflowed. • Carry out review to lower the load caused by collection
overflow in Data cycle, number of collections, and contents of
Collector processing.
• Lower the load on Windows by closing other
applications or by other means.
F300H Error: Not enough There is not enough memory available to execute this • Please close other applications.
memory operation. • Please restart the Industrial PC.
F303H Error: Not enough There is not enough memory available to execute this • Please close other applications.
memory operation. • Please restart the Industrial PC.
F306H Error: Not enough There is not enough memory available to execute this • Please close other applications.
memory operation. • Please restart the Industrial PC.
F30EH Error: Not enough There is not enough memory available to execute this • Please close other applications.
memory operation. • Please restart the Industrial PC.
F380H Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F382H Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F383H Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F386H Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F387H Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F388H Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F389H Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F38AH Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F38BH Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F38DH Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.
F38FH Data Collector internal An unexpected error occurred inside this product. • Please restart the Industrial PC.
error • Please reinstall Data Collector.
• Please consult your local Mitsubishi representative if
the same error occurs again.

6 TROUBLESHOOTING
80 6.3 Error Code List
6.4 Event Code List
This section shows the codes for events that occur in SLMP Data Collector.
Event Event status Event name Event description
code
8800H Information Collection processing Measurement of collection processing time has been completed.
time
8801H Information Read processing time Measurement of Read processing time has been completed.
F800H Warning Exceeded collection Collection process was not completed within the collection cycle.
cycle Page 60 Data missing has occurred in collected data.

6 TROUBLESHOOTING
6.4 Event Code List 81
APPENDIX
Appendix 1 Processing Performance and Processing
Time
This section shows the processing performance and processing time of SLMP Data Collector.

Collection processing performance

Measurement conditions 1
Industrial PC
Item Description
CPU Intel Core i7CPU 2.59 GHz
RAM 12.0 GB
OS Windows 10 Enterprise LTSB 64-bit
(64-bit version)
Ethernet network I/F Interface 1000BASE-T
Communication method Full duplex
Communication speed 1 Gbps (1000BASE-T)

Parameters of Data Collector


The following tables show the setting values of parameters affecting to the processing performance among the parameters of
Data Collector used for measurement.
• SLMP connection (for one process flow)
Setting item Setting content
Communication parameter Request destination module I/O No. H03FF (Host station)
Time-out time 10
Retry count 0
Initial access delay time 0
Collection parameter Collection interval • When the word device collection points is 2048 or less:
1 second
• When the word device collection points is 4096: 2
seconds

• MELSEC connection (for one process flow)


Setting item Setting content
Communication parameter Device type RCPU
Multiple CPU setting Not specified
Time-out time 10
Retry count 0
Initial access delay time 0
Collection parameter Collection interval • When the word device collection points is 2048 or less:
1 second
• When the word device collection points is 4096: 2
seconds

APPX
82 Appendix 1 Processing Performance and Processing Time
• SLMP connection (for multiple process flows)
Setting item Setting content
Communication parameter*1 Request destination module I/O No. H03FF (Host station)
Time-out time 10
Retry count 0
Initial access delay time 0
Collection parameter Collection interval 1 second
Collection target device (for one process flow) INT type device  256 data

*1 Except for the port number, the same communication parameters are set to all of the target device settings.
For each processing performance for the cases in which a same port number is set and in which different port numbers are set, refer to
the following:
Processing performance for multiple process flows
• MELSEC connection (for multiple process flows)
Setting item Setting content
Communication parameter*1 Device type RCPU
Multiple CPU setting Not specified
Time-out time 10
Retry count 0
Initial access delay time 0
Collection parameter Collection interval 1 second
Collection target device (for one process flow) INT type device  256 data

*1 The setting contents are matched among all of the target device settings.

Connection destination device


Item Description
Connection destination device • SLMP connection: SLMP-compatible device
• MELSEC connection: R16CPU (built-in Ethernet port)
Connection method Ethernet connection (direct)
A
Parameters of Real-time Flow Manager
Process flow type Setting item Setting content
Data Logging Flow Data Collection Data Storing: Do not execute
Data Distribution: Do not execute
Data Modification No Processing
Data Diagnosis Flow Data Collection Data Storing: Do not execute
Data Distribution: Do not execute
Data Modification No Processing
Data Diagnosis Data Diagnosis Plug-in*1
Feedback Feedback Type: Instruction Feedback*2
Deterrence Period: 1 minute
Instruction target: 1 point of word device

*1 It is distributed by the Edgecross Consortium. Contact the consortium to obtain it.


*2 4 pieces are set for one data diagnosis flow.

Parameters of an SLMP-compatible device


The parameters are set to their defaults.

Parameters of a MELSEC device


The parameters are set to their defaults.

The sequence scan time is less than 1 millisecond because the measurement is performed in the following
conditions; the constant scan setting is not set for the CPU parameters and a scan program does not exist.

APPX
Appendix 1 Processing Performance and Processing Time 83
Measurement conditions 2
Industrial PC
Item Description
CPU Intel Atom E3826 1.46 GHz (Dual Core)
RAM 4 GB
OS Windows 10 Pro (64-bit)
(64-bit version)
Ethernet network I/F Interface 100BASE-TX
Communication method Full duplex
Communication speed 100 Mbps (100BASE-TX)

Parameters of Data Collector


The following tables show the setting values of parameters affecting to the processing performance among the parameters of
Data Collector used for measurement.
• SLMP connection (for one process flow)
Setting item Setting content
Communication parameter Request destination module I/O No. H03FF (Host station)
Time-out time 10
Retry count 0
Initial access delay time 0
Collection parameter Collection Interval • When the number of word device collection points is
256 or less: 1 second
• When the number of word device collection points is
512: 2 seconds
• When the number of word device collection points is
1024: 3 seconds
• When the number of word device collection points is
2048: 4 seconds
• When the number of word device collection points is
4096: 8 seconds

• MELSEC connection (for one process flow)


Setting item Setting content
Communication parameter Device type RCPU
Multiple CPU setting Not specified
Time-out time 10
Retry count 0
Initial access delay time 0
Collection parameter Collection interval • When the number of word device collection points is
256 or less: 1 second
• When the number of word device collection points is
512: 2 seconds
• When the number of word device collection points is
1024: 3 seconds
• When the number of word device collection points is
2048: 4 seconds
• When the number of word device collection points is
4096: 8 seconds

APPX
84 Appendix 1 Processing Performance and Processing Time
• SLMP connection (for multiple process flows)
Setting item Setting content
Communication parameter*1 Request destination module I/O No. H03FF (Host station)
Time-out time 10
Retry count 0
Initial access delay time 0
Collection parameter Collection interval • For 2 process flows: 2 seconds
• For 4 process flows: 3 seconds
• For 8 process flows: 4 seconds
• For 12 process flows: 6 seconds
Collection target device (for one process flow) INT type device  256 data

*1 Except for the port number, the same communication parameters are set to all of the target device settings.
For each processing performance for the cases in which a same port number is set and in which different port numbers are set, refer to
the following:
Processing performance for multiple process flows
• MELSEC connection (for multiple process flows)
Setting item Setting content
Communication parameter*1 Device type RCPU
Multiple CPU setting Not specified
Time-out time 10
Retry count 0
Initial access delay time 0
Collection parameter Collection interval • For 2 process flows: 2 seconds
• For 4 process flows: 3 seconds
• For 8 process flows: 4 seconds
• For 12 process flows: 6 seconds
Collection target device (for one process flow) INT type device  256 data

*1 The setting contents are matched among all of the target device settings.

Parameters of Data Collector A


For parameters, refer to the following:
Page 82 Parameters of Data Collector

Connection destination device


For connection destination devices, refer to the following:
Page 83 Connection destination device

Parameters of Real-time Flow Manager


For parameters, refer to the following:
Page 83 Parameters of Real-time Flow Manager

Parameters of an SLMP-compatible device


The parameters are set to their defaults.

Parameters of a MELSEC device


The parameters are set to their defaults.

The sequence scan time is less than 1 millisecond because the measurement is performed in the following
conditions; the constant scan setting is not set for the CPU parameters and a scan program does not exist.

APPX
Appendix 1 Processing Performance and Processing Time 85
Processing performance
The following table shows the processing performance capable of collecting all data in a specified cycle per collection
processing time (single collection cycle).

Precautions
Processing of SLMP Data Collector may be delayed if interrupted by processing of other software or an operating system of
Windows.

Processing performance under measurement conditions 1


• Processing performance for one process flow*1
*1 Only one data logging flow is used.
Accessing by an SLMP connection (Communication frame: "4E (Binary)" or "3E (Binary)", Command: "Random read/write
(32-bit)")
Number of word device Performance value (ms) CPU usage rate (%)
collection points Minimum value Maximum value
16 100 1 10
32 100 1 10
64 100 1 12
128 100 1 12
256 100 1 12
512 100 1 12
1024 100 1 12
2048 200 2 14
4096 400 3 14

Accessing by an SLMP connection (Communication frame: "4E (Binary)" or "3E (Binary)", Command: "Random read/write
(16-bit)")
Number of word device Performance value (ms) CPU usage rate (%)
collection points Minimum value Maximum value
16 100 1 4
32 100 1 6
64 100 1 6
128 100 1 6
256 100 1 8
512 100 1 10
1024 100 1 10
2048 200 1 10
4096 400 1 10

Accessing by an SLMP connection (Communication frame: "4E (ASCII)" or "3E (ASCII)", Command: "Random read/write (32-
bit)")
Number of word device Performance value (ms) CPU usage rate (%)
collection points Minimum value Maximum value
16 100 1 8
32 100 1 8
64 100 1 8
128 100 1 10
256 100 1 10
512 100 1 10
1024 100 1 10
2048 200 1 10
4096 400 4 10

APPX
86 Appendix 1 Processing Performance and Processing Time
Accessing by an SLMP connection (Communication frame: "4E (ASCII)" or "3E (ASCII)", Command: "Random read/write (16-
bit)")
Number of word device Performance value (ms) CPU usage rate (%)
collection points Minimum value Maximum value
16 100 1 3
32 100 1 3
64 100 1 8
128 100 1 10
256 100 1 10
512 100 1 10
1024 100 1 10
2048 200 1 10
4096 400 2 10

Accessing by a MELSEC connection


Number of word device Performance value (ms) CPU usage rate (%)
collection points Minimum value Maximum value
16 100 1 19
32 100 1 19
64 100 1 20
128 100 1 20
256 100 1 20
512 100 1 20
1024 100 4 20
2048 200 5 20
4096 400 5 20

APPX
Appendix 1 Processing Performance and Processing Time 87
• Processing performance for multiple process flows*1
*1 Data logging flows are used for all process flows.
Accessing by SLMP connections (Communication frame: "4E (Binary)" or "3E (Binary)", Command: "Random read/write (32-
bit)") using a same port number
Number of process flows Performance value (ms) CPU usage rate (%)
Minimum value Maximum value
2 100 1 11
4 100 1 12
8 100 1 15
16 600 5 13
32 1600 7 11

Accessing by SLMP connections (Communication frame: "4E (Binary)" or "3E (Binary)", Command: "Random read/write (16-
bit)") using a same port number
Number of process flows Performance value (ms) CPU usage rate (%)
Minimum value Maximum value
2 100 1 13
4 100 1 14
8 100 1 14
16 600 8 9
32 1600 8 10

Accessing by SLMP connections (Communication frame: "4E (ASCII)" or "3E (ASCII)", Command: "Random read/write (32-
bit)") using a same port number
Number of process flows Performance value (ms) CPU usage rate (%)
Minimum value Maximum value
2 100 1 14
4 100 1 14
8 100 2 14
16 600 6 8
32 1600 7 16

Accessing by SLMP connections (Communication frame: "4E (ASCII)" or "3E (ASCII)", Command: "Random read/write (16-
bit)") using a same port number
Number of process flows Performance value (ms) CPU usage rate (%)
Minimum value Maximum value
2 100 1 12
4 100 2 12
8 100 2 12
16 600 7 11
32 1600 8 14

APPX
88 Appendix 1 Processing Performance and Processing Time
Accessing by SLMP connections (Communication frame: "4E (Binary)" or "3E (Binary)", Command: "Random read/write (32-
bit)") using different port numbers
Number of process flows Performance value (ms) CPU usage rate (%)
Minimum value Maximum value
2 100 1 3
4 100 1 3
8 100 1 3
16 600 15 20
32 1600 33 39

Accessing by SLMP connections (Communication frame: "4E (Binary)" or "3E (Binary)", Command: "Random read/write (16-
bit)") using different port numbers
Number of process flows Performance value (ms) CPU usage rate (%)
Minimum value Maximum value
2 100 1 3
4 100 1 3
8 100 1 7
16 600 16 20
32 1600 32 37

Accessing by SLMP connections (Communication frame: "4E (ASCII)" or "3E (ASCII)", Command: "Random read/write (32-
bit)") using different port numbers
Number of process flows Performance value (ms) CPU usage rate (%)
Minimum value Maximum value
2 100 1 3
4 100 1 3
8 100 1 3
16 600 15 20
32 1600 32 42 A
Accessing by SLMP connections (Communication frame: "4E (ASCII)" or "3E (ASCII)", Command: "Random read/write (16-
bit)") using different port numbers
Number of process flows Performance value (ms) CPU usage rate (%)
Minimum value Maximum value
2 100 1 2
4 100 1 2
8 100 1 2
16 600 15 19
32 1600 32 40

Accessing by a MELSEC connection


Number of process flows Performance value (ms) CPU usage rate (%)
Minimum value Maximum value
2 100 2 4
4 100 3 17
8 100 7 13
16 600 18 29
32 1600 40 46

APPX
Appendix 1 Processing Performance and Processing Time 89
Processing performance under measurement conditions 2
• Processing performance for one process flow*1
*1 Only one data logging flow is used.
Accessing by an SLMP connection (Communication frame: "4E (Binary)" or "3E (Binary)", Command: "Random read/write
(32-bit)")
Number of word device Performance value (ms) CPU usage rate (%)
collection points Minimum value Maximum value
16 100 5 13
32 100 5 16
64 100 6 19
128 100 6 19
256 100 6 19
512 100 6 19
1024 400 10 19
2048 500 10 19
4096 1000 10 19

Accessing by an SLMP connection (Communication frame: "4E (Binary)" or "3E (Binary)", Command: "Random read/write
(16-bit)")
Number of word device Performance value (ms) CPU usage rate (%)
collection points Minimum value Maximum value
16 100 5 7
32 100 5 7
64 100 5 13
128 100 5 15
256 100 5 17
512 100 7 17
1024 400 7 17
2048 500 7 17
4096 1000 7 17

Accessing by an SLMP connection (Communication frame: "4E (ASCII)" or "3E (ASCII)", Command: "Random read/write (32-
bit)")
Number of word device Performance value (ms) CPU usage rate (%)
collection points Minimum value Maximum value
16 100 5 17
32 100 5 17
64 100 5 17
128 100 5 17
256 100 5 17
512 100 5 17
1024 400 5 17
2048 500 6 17
4096 1000 6 17

APPX
90 Appendix 1 Processing Performance and Processing Time
Accessing by an SLMP connection (Communication frame: "4E (ASCII)" or "3E (ASCII)", Command: "Random read/write (16-
bit)")
Number of word device Performance value (ms) CPU usage rate (%)
collection points Minimum value Maximum value
16 100 7 17
32 100 7 17
64 100 7 17
128 100 7 17
256 100 7 17
512 100 7 17
1024 400 7 17
2048 500 7 17
4096 1000 7 17

Accessing by a MELSEC connection


Number of word device Performance value (ms) CPU usage rate (%)
collection points Minimum value Maximum value
16 100 6 17
32 100 6 17
64 100 6 17
128 100 7 17
256 100 8 17
512 100 9 19
1024 400 11 19
2048 500 15 23
4096 1000 23 31

APPX
Appendix 1 Processing Performance and Processing Time 91
• Processing performance for multiple process flows*1
*1 Data logging flows are used for all process flows.
Accessing by SLMP connections (Communication frame: "4E (Binary)" or "3E (Binary)", Command: "Random read/write (32-
bit)") using a same port number
Number of process flows Performance value (ms) CPU usage rate (%)
Minimum value Maximum value
2 200 12 23
4 200 13 26
8 300 16 28
16 *1 *1 *1
32 *1 *1 *1

*1 Cannot be measured due to an error.


Accessing by SLMP connections (Communication frame: "4E (Binary)" or "3E (Binary)", Command: "Random read/write (16-
bit)") using a same port number
Number of process flows Performance value (ms) CPU usage rate (%)
Minimum value Maximum value
2 200 6 15
4 200 9 16
8 300 12 16
16 *1 *1 *1
32 *1 *1 *1

*1 Cannot be measured due to an error.


Accessing by SLMP connections (Communication frame: "4E (ASCII)" or "3E (ASCII)", Command: "Random read/write (32-
bit)") using a same port number
Number of process flows Performance value (ms) CPU usage rate (%)
Minimum value Maximum value
2 200 5 15
4 200 6 15
8 300 10 20
16 *1 *1 *1
32 *1 *1 *1

*1 Cannot be measured due to an error.


Accessing by SLMP connections (Communication frame: "4E (ASCII)" or "3E (ASCII)", Command: "Random read/write (16-
bit)") using a same port number
Number of process flows Performance value (ms) CPU usage rate (%)
Minimum value Maximum value
2 200 7 16
4 200 9 18
8 300 17 29
16 *1 *1 *1
32 *1 *1 *1

*1 Cannot be measured due to an error.

APPX
92 Appendix 1 Processing Performance and Processing Time
Accessing by SLMP connections (Communication frame: "4E (Binary)" or "3E (Binary)", Command: "Random read/write (32-
bit)") using different port numbers
Number of process flows Performance value (ms) CPU usage rate (%)
Minimum value Maximum value
2 200 19 49
4 200 21 53
8 300 21 53
16 *1 *1 *1
*1 *1
32   *1

*1 Cannot be measured due to an error.


Accessing by SLMP connections (Communication frame: "4E (Binary)" or "3E (Binary)", Command: "Random read/write (16-
bit)") using different port numbers
Number of process flows Performance value (ms) CPU usage rate (%)
Minimum value Maximum value
2 200 5 14
4 200 5 14
8 300 11 26
16 *1 *1 *1
32 *1 *1 *1

*1 Cannot be measured due to an error.


Accessing by SLMP connections (Communication frame: "4E (ASCII)" or "3E (ASCII)", Command: "Random read/write (32-
bit)") using different port numbers
Number of process flows Performance value (ms) CPU usage rate (%)
Minimum value Maximum value
2 200 5 10
4 200 6 16
8 300 14 32 A
*1 *1 *1
16   
32 *1 *1 *1

*1 Cannot be measured due to an error.


Accessing by SLMP connections (Communication frame: "4E (ASCII)" or "3E (ASCII)", Command: "Random read/write (16-
bit)") using different port numbers
Number of process flows Performance value (ms) CPU usage rate (%)
Minimum value Maximum value
2 200 5 7
4 200 6 18
8 300 16 31
16 *1 *1 *1
32 *1 *1 *1

*1 Cannot be measured due to an error.

APPX
Appendix 1 Processing Performance and Processing Time 93
Accessing by a MELSEC connection
Number of process flows Performance value (ms) CPU usage rate (%)
Minimum value Maximum value
2 200 6 17
4 200 7 21
8 300 24 27
16 *1 *1 *1
32 *1 *1 *1

*1 Cannot be measured due to an error.

APPX
94 Appendix 1 Processing Performance and Processing Time
Read processing performance

Measurement conditions 1
Industrial PC
Item Description
CPU Intel Core i7CPU 2.59 GHz
RAM 12.0 GB
OS Windows 10 Enterprise LTSB 64-bit
(64-bit version)
Ethernet network I/F Interface 1000BASE-T
Communication method Full duplex
Communication speed 1 Gbps (1000BASE-T)

Parameters of Data Collector


The following tables show the setting values of parameters affecting to the processing performance among the parameters of
Data Collector used for measurement.
• SLMP connection (for one target device setting)
Setting item Setting content
Communication parameter Request destination module I/O No. H03FF (Host station)
Time-out time 10
Retry count 0
Initial access delay time 0
Monitoring setting Current value update interval 1 second
External data tag resource Data type INT

• MELSEC connection (for one target device setting)


Setting item
Communication parameter Device type
Setting content
RCPU
A
Multiple CPU Setting Not specified
Time-out time 10
Retry count 0
Initial access delay time 0
Monitoring setting Current value update interval 1 second
External data tag resource Data type INT

• SLMP connection (for multiple target device settings)


Setting item Setting content
Communication parameter*1 Request destination module I/O No. H03FF (Host station)
Port number Any number
Time-out time 10
Retry count 0
Initial access delay time 0
Monitoring setting Current value update interval 1 second
Monitoring target (for one access target device) INT type device  64 data

*1 Except for the port number, the same communication parameters are set to all of the target device settings.
For each processing performance for the cases in which a same port number is set and in which different port numbers are set, refer to
the following:
Processing performance for multiple target device settings

APPX
Appendix 1 Processing Performance and Processing Time 95
• MELSEC connection (for multiple target device settings)
Setting item Setting content
Communication parameter*1 Device type RCPU
Multiple CPU setting Not specified
Time-out time 10
Retry count 0
Initial access delay time 0
Monitoring setting Current value update interval 1 second
Monitoring target (for one access target device) INT type device  64 data

*1 Set the same communication parameters to all of the target device settings.

Connection destination device


Item Description
Connection destination device • SLMP connection: SLMP-compatible device
• MELSEC connection: R16CPU (built-in Ethernet port)
Connection method Ethernet connection (direct)

Parameters of an SLMP-compatible device


The parameters are set to their defaults.

Parameters of a MELSEC device


The parameters are set to their defaults.

The sequence scan time is less than 1 millisecond because the measurement is performed in the following
conditions; the constant scan setting is not set for the CPU parameters and a scan program does not exist.

APPX
96 Appendix 1 Processing Performance and Processing Time
Measurement conditions 2
Industrial PC
Item Description
CPU Intel Atom E3826 1.46 GHz (Dual Core)
RAM 4 GB
OS Windows 10 Pro (64-bit)
(64-bit version)
Ethernet network I/F Interface 100BASE-TX
Communication method Full duplex
Communication speed 100 Mbps (100BASE-TX)

Parameters of Data Collector


For parameters, refer to the following:
Page 95 Parameters of Data Collector

Connection destination device


For connection destination devices, refer to the following:
Page 96 Connection destination device

Parameters of an SLMP-compatible device


The parameters are set to their defaults.

Parameters of a MELSEC device


The parameters are set to their defaults.

The sequence scan time is less than 1 millisecond because the measurement is performed in the following
conditions; the constant scan setting is not set for the CPU parameters and a scan program does not exist.

APPX
Appendix 1 Processing Performance and Processing Time 97
Processing performance
The following table shows the performance of read processing time.

Precautions
Processing of SLMP Data Collector may be delayed if interrupted by processing of other software or an operating system of
Windows.

Processing performance under measurement conditions 1


• Processing performance for one target device setting
Accessing by an SLMP connection (Communication frame: "4E (Binary)" or "3E (Binary)", Command: "Random read/write
(32-bit)")
Number of word device read Performance value (ms) CPU usage rate (%)
points Minimum value Maximum value
256 47 1 17
512 82 1 17
1024 141 1 17
2560 300 1 17
5120 744 1 17

Accessing by an SLMP connection (Communication frame: "4E (Binary)" or "3E (Binary)", Command: "Random read/write
(16-bit)")
Number of word device read Performance value (ms) CPU usage rate (%)
points Minimum value Maximum value
256 42 1 10
512 133 1 10
1024 135 1 10
2560 300 2 11
5120 652 2 11

Accessing by an SLMP connection (Communication frame: "4E (ASCII)" or "3E (ASCII)", Command: "Random read/write (32-
bit)")
Number of word device read Performance value (ms) CPU usage rate (%)
points Minimum value Maximum value
256 48 1 18
512 82 1 18
1024 182 1 18
2560 351 1 18
5120 745 1 18

Accessing by an SLMP connection (Communication frame: "4E (ASCII)" or "3E (ASCII)", Command: "Random read/write (16-
bit)")
Number of word device read Performance value (ms) CPU usage rate (%)
points Minimum value Maximum value
256 43 1 10
512 76 1 10
1024 152 1 10
2560 292 1 10
5120 668 2 10

Accessing by a MELSEC connection


Number of word device read Performance value (ms) CPU usage rate (%)
points Minimum value Maximum value
256 62 1 13
512 94 1 13

APPX
98 Appendix 1 Processing Performance and Processing Time
Number of word device read Performance value (ms) CPU usage rate (%)
points Minimum value Maximum value
1024 188 3 14
2560 406 4 14
5120 781 6 14

APPX
Appendix 1 Processing Performance and Processing Time 99
• Processing performance for multiple target device settings
Accessing by SLMP connections (Communication frame: "4E (Binary)" or "3E (Binary)", Command: "Random read/write (32-
bit)") using a same port number
Number of target device Performance value (ms) CPU usage rate (%)
settings Minimum value Maximum value
2 35 1 7
16 174 1 7
32 877 1 7
64 1667 17 19

Accessing by SLMP connections (Communication frame: "4E (Binary)" or "3E (Binary)", Command: "Random read/write (16-
bit)") using a same port number
Number of target device Performance value (ms) CPU usage rate (%)
settings Minimum value Maximum value
2 35 1 9
16 198 1 9
32 358 2 9
64 522 3 17

Accessing by SLMP connections (Communication frame: "4E (ASCII)" or "3E (ASCII)", Command: "Random read/write (32-
bit)") using a same port number
Number of target device Performance value (ms) CPU usage rate (%)
settings Minimum value Maximum value
2 39 1 10
16 193 1 10
32 353 1 10
64 709 3 11

Accessing by SLMP connections (Communication frame: "4E (ASCII)" or "3E (ASCII)", Command: "Random read/write (16-
bit)") using a same port number
Number of target device Performance value (ms) CPU usage rate (%)
settings Minimum value Maximum value
2 35 1 16
16 247 1 16
32 313 1 16
64 803 2 16

APPX
100 Appendix 1 Processing Performance and Processing Time
Accessing by SLMP connections (Communication frame: "4E (Binary)" or "3E (Binary)", Command: "Random read/write (32-
bit)") using different port numbers
Number of target device Performance value (ms) CPU usage rate (%)
settings Minimum value Maximum value
2 38 1 3
16 73 1 3
32 143 2 4
64 268 22 24

Accessing by SLMP connections (Communication frame: "4E (Binary)" or "3E (Binary)", Command: "Random read/write (16-
bit)") using different port numbers
Number of target device Performance value (ms) CPU usage rate (%)
settings Minimum value Maximum value
2 38 1 2
16 106 1 2
32 135 1 2
64 256 23 25

Accessing by SLMP connections (Communication frame: "4E (ASCII)" or "3E (ASCII)", Command: "Random read/write (32-
bit)") using different port numbers
Number of target device Performance value (ms) CPU usage rate (%)
settings Minimum value Maximum value
2 34 1 3
16 78 1 3
32 232 1 5
64 368 20 26

Accessing by SLMP connections (Communication frame: "4E (ASCII)" or "3E (ASCII)", Command: "Random read/write (16-
bit)") using different port numbers A
Number of target device Performance value (ms) CPU usage rate (%)
settings Minimum value Maximum value
2 34 1 2
16 89 1 3
32 175 1 4
64 456 23 25

Accessing by a MELSEC connection


Number of target device Performance value (ms) CPU usage rate (%)
settings Minimum value Maximum value
2 46 1 1
16 159 5 7
32 254 8 10
64 592 23 27

APPX
Appendix 1 Processing Performance and Processing Time 101
Processing performance under measurement conditions 2
• Processing performance for one target device setting
Accessing by an SLMP connection (Communication frame: "4E (Binary)" or "3E (Binary)", Command: "Random read/write
(32-bit)")
Number of word device read Performance value (ms) CPU usage rate (%)
points Minimum value Maximum value
16 31 2 9
32 31 2 9
64 32 2 15
128 32 2 15
256 62 3 15
512 110 3 15
1024 172 4 15
2560 375 6 15
5120 735 11 17

Accessing by an SLMP connection (Communication frame: "4E (Binary)" or "3E (Binary)", Command: "Random read/write
(16-bit)")
Number of word device read Performance value (ms) CPU usage rate (%)
points Minimum value Maximum value
16 31 3 10
32 31 3 10
64 32 3 10
128 32 4 11
256 47 4 11
512 78 4 11
1024 172 4 11
2560 375 6 13
5120 766 11 29

Accessing by an SLMP connection (Communication frame: "4E (ASCII)" or "3E (ASCII)", Command: "Random read/write (32-
bit)")
Number of word device read Performance value (ms) CPU usage rate (%)
points Minimum value Maximum value
16 31 2 15
32 31 2 15
64 32 2 15
128 47 2 15
256 62 2 15
512 94 3 16
1024 172 4 16
2560 657 6 16
5120 860 11 26

APPX
102 Appendix 1 Processing Performance and Processing Time
Accessing by an SLMP connection (Communication frame: "4E (ASCII)" or "3E (ASCII)", Command: "Random read/write (16-
bit)")
Number of word device read Performance value (ms) CPU usage rate (%)
points Minimum value Maximum value
16 31 2 14
32 31 2 14
64 31 2 24
128 32 2 24
256 78 3 24
512 94 3 24
1024 188 4 24
2560 375 6 24
5120 859 11 25

Accessing by a MELSEC connection


Number of word device read Performance value (ms) CPU usage rate (%)
points Minimum value Maximum value
16 31 3 12
32 46 3 12
64 63 3 20
128 74 5 20
256 110 8 20
512 156 14 20
1024 313 24 27
2560 719 47 50
5120 1531 62 64

• Processing performance for multiple target device settings


Accessing by SLMP connections (Communication frame: "4E (Binary)" or "3E (Binary)", Command: "Random read/write (32- A
bit)") using a same port number
Number of target device Performance value (ms) CPU usage rate (%)
settings Minimum value Maximum value
2 40 2 10
16 170 8 15

Accessing by SLMP connections (Communication frame: "4E (Binary)" or "3E (Binary)", Command: "Random read/write (16-
bit)") using a same port number
Number of target device Performance value (ms) CPU usage rate (%)
settings Minimum value Maximum value
2 69 2 10
16 204 7 16

Accessing by SLMP connections (Communication frame: "4E (ASCII)" or "3E (ASCII)", Command: "Random read/write (32-
bit)") using a same port number
Number of target device Performance value (ms) CPU usage rate (%)
settings Minimum value Maximum value
2 36 2 13
16 182 7 13

APPX
Appendix 1 Processing Performance and Processing Time 103
Accessing by SLMP connections (Communication frame: "4E (ASCII)" or "3E (ASCII)", Command: "Random read/write (16-
bit)") using a same port number
Number of target device Performance value (ms) CPU usage rate (%)
settings Minimum value Maximum value
2 37 3 14
16 174 7 14

Accessing by SLMP connections (Communication frame: "4E (Binary)" or "3E (Binary)", Command: "Random read/write (32-
bit)") using different port numbers
Number of target device Performance value (ms) CPU usage rate (%)
settings Minimum value Maximum value
2 45 2 6
16 167 7 22

Accessing by SLMP connections (Communication frame: "4E (Binary)" or "3E (Binary)", Command: "Random read/write (16-
bit)") using different port numbers
Number of target device Performance value (ms) CPU usage rate (%)
settings Minimum value Maximum value
2 40 2 11
16 349 8 23

Accessing by SLMP connections (Communication frame: "4E (ASCII)" or "3E (ASCII)", Command: "Random read/write (32-
bit)") using different port numbers
Number of target device Performance value (ms) CPU usage rate (%)
settings Minimum value Maximum value
2 37 2 4
16 883 7 26

Accessing by SLMP connections (Communication frame: "4E (ASCII)" or "3E (ASCII)", Command: "Random read/write (16-
bit)") using different port numbers
Number of target device Performance value (ms) CPU usage rate (%)
settings Minimum value Maximum value
2 49 2 15
16 343 8 15

Accessing by a MELSEC connection


Number of target device Performance value (ms) CPU usage rate (%)
settings Minimum value Maximum value
2 58 5 7
16 851 41 48

APPX
104 Appendix 1 Processing Performance and Processing Time
Appendix 2 Data Assignment
This section shows the data assignment availability and the number of device points to be assigned.

Data assignment availability


The following table shows the assignment availability of data for each data type.
: Available, : Not available
Location type Data type
BOOL UINT UDINT ULINT INT DINT LINT REAL LREA STRING WSTRING
L
Bit device           
Word device           
Double-word device           

Number of device points to be assigned to data


The following table shows the number of device points for data assignment for each data type.
Number: Fixed number of points for data assignment, : calculation formula, : Not available
Location type Data type
1 bit 16 bit 32 bit 64 bit Character string
BOOL UINT INT UDINT DINT REAL ULINT LINT LREA STRING WSTRING
L
Bit device 1          
Word device  1 1 2 2 2 4 4 4  (Number of  (Number
characters  of characters
2)*1  2)
Double-word device  1*2 1*3 1 1 1 2 2 2  (Number of  (Number
characters  of characters)
4)*1 A
*1 Round up digits after a decimal points of a value obtained by division.
*2 '0' is set for the upper 16 bytes.
*3 For integers and zero, '0' is set for the upper 16 bytes. For negative numbers, '1' is set for them.

APPX
Appendix 2 Data Assignment 105
MEMO

APPX
106 Appendix 2 Data Assignment
Appendix 3 Software Licenses
This software consists of multiple software components. Each of them is copyrighted by Mitsubishi Electric and/or third
parties.
The following types of software are contained:
 Software copyrighted by third parties and distributed as free software
Source codes are not distributed for the software that Mitsubishi Electric and/or third parties have copyrights to.
Please refrain from inquiring about the source codes of this open source.

Software information
This product contains the following software:
RapidJSON (Page 107 RapidJSON)
msinttypes (Page 108 msinttypes)

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
A
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 3 Software Licenses 107
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 other
materials 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 specific
prior 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 EVENT
SHALL 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 POSSIBILITY
OF SUCH DAMAGE.

APPX
108 Appendix 3 Software Licenses
Appendix 4 Supported Edgecross Basic Software
Version
The following table shows the version of Edgecross Basic Software supported by SLMP Data Collector.
SLMP Data Collector Data collector version*3 Data collector specifications Edgecross Basic Software
version*1,*2 version*3 version*3
1.00A 1 1.00 1.00 to 1.21
1.01B 2
1.02C 3 1.10 to 1.21
1.03D 4
1.04E 5 1.10 or later
1.05F 6
1.06G 7
1.07H or later 8

*1 Can be checked in the screen displayed by selecting [Windows System]  [Control Panel]  [Programs]  [Programs and Features]
from Windows Start.
*2 The version 1.02C or later is recommended to use this product in Management Shell.
*3 For the checking method, refer to the following:
Edgecross Basic Software for Windows User's Manual

APPX
Appendix 4 Supported Edgecross Basic Software Version 109
MEMO

APPX
110 Appendix 4 Supported Edgecross Basic Software Version
Appendix 5 Added and Changed Functions
This section shows the added and changed functions of SLMP Data Collector.
Added/changed contents Version Reference
Accessible devices are added. 1.01B Page 18 Accessible devices (locations)
• CPU buffer memory access device (C Controller module)
Management Shell added in Edgecross Basic Software Ver.1.10 is supported. 
An SLMP connection is supported. 1.03D Page 10 SLMP Connection
The data model import function added in Edgecross Basic Software Ver.1.22 1.04E 
is supported.
Windows 11, Windows Server 2019, and Windows Server 2016 are 1.06G SLMP Data Collector Installation Instructions
supported.
Windows Server 2022 is supported. 1.07H SLMP Data Collector Installation Instructions
The number of flows that can be used simultaneously in a real-time flow of Page 10 Functional specifications
Edgecross Basic Software is increased.

APPX
Appendix 5 Added and Changed Functions 111
MEMO

APPX
112 Appendix 5 Added and Changed Functions
INDEX

A
Access method and available command . . . . . . . 12
Accessible CPU module . . . . . . . . . . . . . . . . . . 17
Accessible device (equipment) . . . . . . . . . . . . . . 15
Accessible device (location) . . . . . . . . . . . . . . 15,18
Accessible device number . . . . . . . . . . . . . . . . . 15

C
Collection parameter . . . . . . . . . . . . . . . . . . . 44,54
Communication parameter . . . . . . . . . . . . . . . 38,52

D
Data collection function . . . . . . . . . . . . . . . . . . . 29
Data reading function . . . . . . . . . . . . . . . . . . . . 32
Data writing function . . . . . . . . . . . . . . . . . . . . . 34

E
Error code list . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Event code list . . . . . . . . . . . . . . . . . . . . . . . . . 81

F
Functional specification . . . . . . . . . . . . . . . . . 10,16

M
MELSEC connection . . . . . . . . . . . . . . . . . . . . . 16

N
I
Number of device points . . . . . . . . . . . . . . . . . 105

O
Operational specification . . . . . . . . . . . . . . . . 11,16

S
SLMP connection . . . . . . . . . . . . . . . . . . . . . . . 10

T
Troubleshooting by symptom . . . . . . . . . . . . . . . 59

113
MEMO

114
REVISIONS
*The manual number is given on the bottom left of the back cover.
Revision date *Manual number Description
May 2018 SH(NA)-081919ENG-A First edition
May 2018 SH(NA)-081919ENG-B Partial correction
September 2018 SH(NA)-081919ENG-C Added or modified parts
Section 2.3, Section 6.2
March 2019 SH(NA)-081919ENG-D Added or modified parts
Section 2.1, Section 2.3, Chapter 3, Section 4.1, Section 4.2, Section 4.4, Section 5.1, Section 5.2,
Section 6.2, Section 6.3, Section 6.4, Appendix 1, Appendix 2, Appendix 4, Appendix 5
June 2019 SH(NA)-081919ENG-E Added or modified parts
TERMS, Chapter 2, Chapter 3, Chapter 4, Chapter 5, Section 6.2, Section 6.3, Appendix 1, Appendix
4, Appendix 5
July 2019 SH(NA)-081919ENG-F Added or modified parts
Section 2.1, Section 4.4, Section 5.1, Section 5.2, Section 6.2
December 2019 SH(NA)-081919ENG-G Added or modified parts
Section 4.4, Section 6.2, Section 6.3, Section 6.4, Appendix 4
November 2021 SH(NA)-081919ENG-H Added or modified parts
SAFETY PRECAUTIONS, CONDITIONS OF USE FOR THE PRODUCT, TERMS, Section 5.1,
Section 5.2, Appendix 4
June 2023 SH(NA)-081919ENG-I Added or modified parts
Section 3.1, Section 4.1, Section 5.2, Section 6.2, Appendix 4, Appendix 5
March 2024 SH(NA)-081919ENG-J Added or modified parts
Section 2.1, Appendix 4, Appendix 5

Japanese manual number: SH-081918-K


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 MITSUBISHI ELECTRIC CORPORATION

115
INFORMATION AND SERVICES
For further information and services, please contact your local Mitsubishi Electric sales office or representative.
Visit our website to find our locations worldwide.

MITSUBISHI ELECTRIC Factory Automation Global Website


Locations Worldwide
www.MitsubishiElectric.com/fa/about-us/overseas/

TRADEMARKS
Core, Intel, and Intel Atom are either registered trademarks or trademarks of Intel Corporation in the United States and/or
other countries.
Windows and Windows Server are trademarks of the Microsoft group of companies.
The company names, system names and product names mentioned in this manual are either registered trademarks or
trademarks of their respective companies.
In some cases, trademark symbols such as '' or '' are not specified in this manual.

COPYRIGHTS
For the open source software used in this product, refer to the following:
Page 107 Software Licenses

116
SH(NA)-081919ENG-J(2403)
MODEL: SW1DND-DCSLMP-U-E

HEAD OFFICE: TOKYO BLDG., 2-7-3, MARUNOUCHI, CHIYODA-KU, TOKYO 100-8310, JAPAN
NAGOYA WORKS: 1-14, YADA-MINAMI 5-CHOME, HIGASHI-KU, NAGOYA 461-8670, JAPAN

When exported from Japan, this manual does not require application to the
Ministry of Economy, Trade and Industry for service transaction permission.

Specifications subject to change without notice.

You might also like