Mitsubishi Electric iQ Sensor Solution Owner's manual

iQ Sensor Solution Reference Manual

1

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 for the programmable

controller system, refer to the user's manual for the module used and MELSEC iQ-R Module Configuration Manual.

In this manual, the safety precautions are classified into two levels: " WARNING" and " CAUTION".

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.

WARNING

Indicates that incorrect handling may cause hazardous conditions, resulting in

death or severe injury.

CAUTION

Indicates that incorrect handling may cause hazardous conditions, resulting in

minor or moderate injury or property damage.

2

[Design Precautions]

WARNING

● Configure safety circuits external to the programmable controller to ensure that the entire system

operates safely even when a fault occurs in the external power supply or the programmable controller.

Failure to do so may result in an accident due to an incorrect output or malfunction.

(1) Emergency stop circuits, protection circuits, and protective interlock circuits for conflicting

operations (such as forward/reverse rotations or upper/lower limit positioning) must be configured

external to the programmable controller.

(2) When the programmable controller detects an abnormal condition, it stops the operation and all

outputs are:

• Turned OFF if the overcurrent or overvoltage protection of the power supply module is

activated.

• Held or turned off according to the parameter setting if the self-diagnostic function of the CPU

module detects an error such as a watchdog timer error.

(3) All outputs may be turned on if an error occurs in a part, such as an I/O control part, where the

CPU module cannot detect any error. To ensure safety operation in such a case, provide a safety

mechanism or a fail-safe circuit external to the programmable controller. For a fail-safe circuit

example, refer to the user's manual for the CPU module used and "General Safety Requirements"

in MELSEC iQ-R Module Configuration Manual.

(4) Outputs may remain on or off due to a failure of a component such as a relay and transistor in an

output circuit. Configure an external circuit for monitoring output signals that could cause a

serious accident.

● In an output circuit, when a load current exceeding the rated current or an over current caused by a

load short-circuit flows for a long time, it may cause smoke and fire. To prevent this, configure an

external safety circuit, such as a fuse.

● Configure a circuit so that the programmable controller is turned on first and then the external power

supply. If the external power supply is turned on first, an accident may occur due to an incorrect output

or malfunction.

● For the operating status of each station after a communication failure, refer to manuals relevant to the

network. Incorrect output or malfunction due to a communication failure may result in an accident.

3

[Design Precautions]

[Security Precautions]

WARNING

● When connecting an external device with a CPU module or intelligent function module to modify data

of a running programmable controller, configure an interlock circuit in the program to ensure that the

entire system will always operate safely. For other forms of control (such as program modification,

parameter change, forced output, or operating status change) of a running programmable controller,

read the relevant manuals carefully and ensure that the operation is safe before proceeding. Improper

operation may damage machines or cause accidents.

● Especially, when a remote programmable controller is controlled by an external device, immediate

action cannot be taken if a problem occurs in the programmable controller due to a communication

failure. To prevent this, configure an interlock circuit in the program, and determine corrective actions

to be taken between the external device and CPU module in case of a communication failure.

● Do not write any data to the "system area" and "write-protect area" of the buffer memory in the

module. Also, do not use any "use prohibited" signals as an output signal from the CPU module to

each module. Doing so may cause malfunction of the programmable controller system. For the

"system area", "write-protect area", and the "use prohibited" signals, refer to the user's manual for the

module used.

● If a communication cable is disconnected, the network may be unstable, resulting in a communication

failure of multiple stations. Configure an interlock circuit in the program to ensure that the entire

system will always operate safely even if communications fail. Incorrect output or malfunction due to a

communication failure may result in an accident.

WARNING

● To maintain the security (confidentiality, integrity, and availability) of the programmable controller 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.

4

[Design Precautions]

Precautions when connected to AnyWireASLINK

[Design Precautions]

Precautions when connected to CC-Link

[Design Precautions]

Precautions when connected to CC-Link IE Field Network

[Design Precautions]

Precautions when connected to Ethernet

WARNING

● The AnyWireASLINK system has no control function for ensuring safety.

WARNING

● To set the automatic refresh parameter, specify the device Y for the remote output (RY) refresh

device.

If a device other than 'Y', such as 'M' and 'L', is specified, CPU module holds the device status as is

even after the module status is changed to STOP.

For the method for stopping a data link, refer to the user's manual for relevant CC-Link master/local

module.

WARNING

● To set a refresh device in the network parameters, specify the device Y for the remote output (RY)

refresh device.

If a device other than 'Y', such as 'M' and 'L', is specified, CPU module holds the device status as is

even after the module status is changed to STOP.

WARNING

● To prevent the malfunction of the programmable controller system due to harmful e-mails, take

preventive measures (such as antivirus measures) so that the mail server for Ethernet module does

not receive harmful e-mails.

5

[Design Precautions]

WARNING

● Do not install the control lines or communication cables together with the main circuit lines or power

cables. Keep a distance of 100mm or more between them. Failure to do so may result in malfunction

due to noise.

● During control of an inductive load such as a lamp, heater, or solenoid valve, a large current

(approximately ten times greater than normal) may flow when the output is turned from off to on.

Therefore, use a module that has a sufficient current rating.

● After the CPU module is powered on or is reset, the time taken to enter the RUN status varies

depending on the system configuration, parameter settings, and/or program size. Design circuits so

that the entire system will always operate safely, regardless of the time.

● Do not power off the programmable controller or do not reset the CPU module while the settings are

being written. Doing so will make the data in the flash ROM undefined. The values need to be set in

the buffer memory and written to the flash ROM again. Doing so may cause malfunction or failure of

the module.

● When changing the operating status of the CPU module from external devices (such as remote RUN/

STOP functions), select "Do Not Open in Program" for "Open Method Setting" in the module

parameters. If "Open in Program" is selected, an execution of remote STOP causes the

communication line to close. Consequently, the CPU module cannot reopen the communication line,

and the external device cannot execute the remote RUN.

6

CONDITIONS OF USE FOR THE PRODUCT

INTRODUCTION

Thank you for purchasing the FA integrated engineering software MELSOFT.

This manual describes the functions provided by iQ Sensor Solution.

Before using the product, please read this manual and relevant manuals carefully and develop familiarity with the functions

and performance of programmable controller/MELSOFT series to handle the product correctly.

When applying the program examples provided in this manual to an actual system, ensure the applicability and confirm that it

will not cause system control problems.

Please make sure that the end users read this manual.

(1) MELSEC programmable controller ("the PRODUCT") shall be used in conditions;

i) where any problem, fault or failure occurring in the PRODUCT, if any, shall not lead to any major or serious accident;

and

ii) where the backup and fail-safe function are systematically or automatically provided outside of the PRODUCT for the

case of any problem, fault or failure occurring in the PRODUCT.

(2) The PRODUCT has been designed and manufactured for the purpose of being used in general industries.

MITSUBISHI ELECTRIC SHALL HAVE NO RESPONSIBILITY OR LIABILITY (INCLUDING, BUT NOT LIMITED TO

ANY AND ALL RESPONSIBILITY OR LIABILITY BASED ON CONTRACT, WARRANTY, TORT, PRODUCT

LIABILITY) FOR ANY INJURY OR DEATH TO PERSONS OR LOSS OR DAMAGE TO PROPERTY CAUSED BY the

PRODUCT THAT ARE OPERATED OR USED IN APPLICATION NOT INTENDED OR EXCLUDED BY

INSTRUCTIONS, PRECAUTIONS, OR WARNING CONTAINED IN MITSUBISHI ELECTRIC USER'S, INSTRUCTION

AND/OR SAFETY MANUALS, TECHNICAL BULLETINS AND GUIDELINES FOR the PRODUCT.

("Prohibited Application")

Prohibited Applications include, but not limited to, the use of the PRODUCT in;

• Nuclear Power Plants and any other power plants operated by Power companies, and/or any other cases in which the

public could be affected if any problem or fault occurs in the PRODUCT.

• Railway companies or Public service purposes, and/or any other cases in which establishment of a special quality

assurance system is required by the Purchaser or End User.

• Aircraft or Aerospace, Medical applications, Train equipment, transport equipment such as Elevator and Escalator,

Incineration and Fuel devices, Vehicles, Manned transportation, Equipment for Recreation and Amusement, and

Safety devices, handling of Nuclear or Hazardous Materials or Chemicals, Mining and Drilling, and/or other

applications where there is a significant risk of injury to the public or property.

Notwithstanding the above restrictions, Mitsubishi Electric may in its sole discretion, authorize use of the PRODUCT in

one or more of the Prohibited Applications, provided that the usage of the PRODUCT is limited only for the specific

applications agreed to by Mitsubishi Electric and provided further that no special quality assurance or fail-safe,

redundant or other safety features which exceed the general specifications of the PRODUCTs are required. For details,

please contact the Mitsubishi Electric representative in your region.

(3) Mitsubishi Electric shall have no responsibility or liability for any problems involving programmable controller trouble and

system trouble caused by DoS attacks, unauthorized access, computer viruses, and other cyberattacks.

7

CONTENTS

SAFETY PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

CONDITIONS OF USE FOR THE PRODUCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

INTRODUCTION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

RELEVANT MANUALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

TERMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

PART 1 iQ Sensor Solution

CHAPTER 1 iQ Sensor Solution 16

1.1 Features of iQ Sensor Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Easy startup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Easy tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Sensor/device monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Data backup/restoration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

1.2 How to Use iQ Sensor Solution Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

CHAPTER 2 iQ Sensor Solution FUNCTIONS 21

2.1 Function List of iQ Sensor Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Before using iQ Sensor Solution functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2.2 Function List of iQ Sensor Solution for Each Connection Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

GX Works2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

GX Works3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

MI Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

PART 2 GX Works2

CHAPTER 3 AnyWireASLINK 28

3.1 Detecting Devices Supporting iQSS Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

3.2 Verifying Devices Supporting iQSS Against System Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

3.3 Reading/Writing Parameters from/to Devices Supporting iQSS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3.4 Monitoring Devices Supporting iQSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

3.5 Backing up/Restoring Data of Devices Supporting iQSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Data backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Data restoration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

CHAPTER 4 CC-Link 55

4.1 Detecting Devices Supporting iQSS Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Detecting devices connected to a bridge module (NZ2AW1C2AL). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

4.2 Verifying Devices Supporting iQSS Against System Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

4.3 Reading/Writing Parameters from/to Devices Supporting iQSS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

4.4 Monitoring Devices Supporting iQSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

4.5 Backing up/Restoring Data of Devices Supporting iQSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Data backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Data restoration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

8

CHAPTER 5 CC-Link IE Field Network 100

5.1 Detecting Devices Supporting iQSS Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Detecting devices connected to a bridge module (NZ2AW1GFAL). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

5.2 Verifying Devices Supporting iQSS Against System Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

5.3 Reading/Writing Parameters from/to Devices Supporting iQSS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

5.4 Monitoring Devices Supporting iQSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

5.5 Backing up/Restoring Data of Devices Supporting iQSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Data backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Data restoration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

CHAPTER 6 Ethernet 138

6.1 Detecting Devices Supporting iQSS Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

6.2 Applying the Communication Setting to a Device Supporting iQSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

6.3 Reading/Writing Parameters from/to Devices Supporting iQSS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

6.4 Monitoring Devices Supporting iQSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

6.5 Backing up/Restoring Data of Devices Supporting iQSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Data backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Data restoration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

PART 3 GX Works3

CHAPTER 7 AnyWireASLINK 168

7.1 Detecting Devices Supporting iQSS Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

7.2 Verifying Devices Supporting iQSS Against System Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

7.3 Reading/Writing Parameters from/to Devices Supporting iQSS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

7.4 Monitoring Devices Supporting iQSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

7.5 Backing up/Restoring Data of Devices Supporting iQSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Data backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Data restoration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

CHAPTER 8 CC-Link 196

8.1 Detecting Devices Supporting iQSS Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Detecting devices connected to a bridge module (NZ2AW1C2AL). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

8.2 Reading/Writing Parameters from/to Devices Supporting iQSS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

8.3 Monitoring Devices Supporting iQSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

8.4 Backing up/Restoring Data of Devices Supporting iQSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

Data backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Data restoration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

CHAPTER 9 CC-Link IE Field Network 242

9.1 Detecting Devices Supporting iQSS Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

Detecting devices connected to a bridge module (NZ2AW1GFAL). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

9.2 Reading/Writing Parameters from/to Devices Supporting iQSS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

9.3 Monitoring Devices Supporting iQSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

9.4 Backing up/Restoring Data of Devices Supporting iQSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

Data backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

Data restoration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

9

CONTENTS

CHAPTER 10 Ethernet 288

10.1 Detecting Devices Supporting iQSS Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289

10.2 Applying the Communication Setting to a Device Supporting iQSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

10.3 Reading/Writing Parameters from/to Devices Supporting iQSS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .293

10.4 Monitoring Devices Supporting iQSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

10.5 Backing up/Restoring Data of Devices Supporting iQSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

Data backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299

Data restoration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308

PART 4 MI Configurator

CHAPTER 11 CC-Link IE Field Network 318

11.1 Detecting Devices Supporting iQSS Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319

11.2 Reading/Writing Parameters from/to Devices Supporting iQSS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .321

CHAPTER 12 Ethernet 324

12.1 Detecting Devices Supporting iQSS Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325

12.2 Applying the Communication Setting to a Device Supporting iQSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327

12.3 Reading/Writing Parameters from/to Devices Supporting iQSS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .329

APPENDIX 330

Appendix 1 Useful Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330

Linkage with dedicated tools (association with properties) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330

Command execution to slave station. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

Appendix 2 Devices that Support iQ Sensor Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332

CPU module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332

MELIPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334

Devices supporting iQSS (CPU module). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

Device supporting iQSS (MELIPC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342

Appendix 3 Engineering Tool and Version List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345

GX Works2/MELSOFT Navigator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345

GX Works3/MELSOFT Navigator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348

MI Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351

Appendix 4 Considerations for Using Device Supporting iQSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352

AnyWireASLINK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352

CC-Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352

CC-Link IE Field Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354

Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356

Appendix 5 Error Code List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357

iQ Sensor Solution-related errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357

AnyWireASLINK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357

CC-Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357

CC-Link IE Field Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359

Ethernet (Error codes that occur on communication) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360

Ethernet (Error codes of devices supporting iQSS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363

Appendix 6 Special Relay (SM)/Special Register (SD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364

Appendix 7 Event List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365

Viewing an event history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365

How to read the event list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365

10

Event list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366

Appendix 8 Backup File Capacity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

Backup data file (.QBR). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

System file for backup/restoration (.QSI). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

INDEX 368

REVISIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .370

WARRANTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .371

TRADEMARKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .372

11

RELEVANT MANUALS

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.

Manual name [manual number] Description Available form

iQ Sensor Solution Reference Manual

[SH-081133ENG] (this manual)

Operation methods of the online functions for iQ Sensor Solution Print book

e-Manual

PDF

12

TERMS

Unless otherwise specified, this manual uses the following terms.

Term Description

Actual system configuration An abbreviation for an actual system configuration connected to a master module and a built-in Ethernet port LCPU.

Address A parameter assigned to a slave module to identify each node on a network.

AnyWireASLINK A wire-saving network which provides an appropriate connection between sensors placed at the terminal end of a

control system and a programmable controller.

Detecting a sensor disconnection or setting the I/O operation from the upper system can be realized without using the I/

O area.

AnyWireASLINK configuration An abbreviation for a system configuration connected with AnyWireASLINK.

AnyWireASLINK master module A generic term for LJ51AW12AL, QJ51AW12AL, and FX3U-128ASL-M.

ASLINKAMP A generic term for sensor amplifiers that have an AnyWireASLINK interface.

ASLINKER A generic term for I/O devices that have an AnyWireASLINK interface.

Bridge module An abbreviation for NZ2AW1C2AL CC-Link-AnyWireASLINK bridge module and NZ2AW1GFAL CC-Link IE Field

Network-AnyWireASLINK bridge module.

Built-in Ethernet port CPU A generic term for L02CPU, L02CPU-P, L06CPU, L06CPU-P, L26CPU, L26CPU-P, L26CPU-BT, L26CPU-PBT,

Q03UDVCPU, Q04UDVCPU, Q04UDPVCPU, Q06UDVCPU, Q06UDPVCPU, Q13UDVCPU, Q13UDPVCPU,

Q26UDVCPU, and Q26UDPVCPU.

Built-in Ethernet port LCPU A generic term for L02CPU, L02CPU-P, L06CPU, L06CPU-P, L26CPU, L26CPU-P, L26CPU-BT, and L26CPU-PBT.

CC IE Field configuration An abbreviation for a system configuration connected with CC-Link IE Field Network.

CC-Link An acronym for Control and Communication Link.

A field network system where data processing for control and information can be simultaneously performed at high

speed.

CC-Link configuration An abbreviation for a system configuration connected with CC-Link.

CC-Link IE Field Network A high-speed and large capacity open field network using Ethernet (1000BASE-T).

CC-Link IE Field Network master/

local module

A generic term for LJ71GF11-T2 CC-Link IE Field Network master/local modules.

CC-Link IE Field Network-equipped

master/local module

A generic term for RJ71GF11-T2 CC-Link IE Field Network master/local modules and RJ71EN71 (when the CC-Link IE

Field Network function is used).

CC-Link master/local module A generic term for RJ61BT11 CC-Link system master/local module, LJ61BT11 CC-Link system master/local module,

QJ61BT11N CC-Link system master/local module, L26CPU-BT, and L26CPU-PBT built-in CC-Link system master/local

functions.

CC-Link Ver.2-compatible slave

station

A slave station which supports the remote net Ver.2 mode.

Communication setting A generic term for the settings (such as IP address) to communicate using Ethernet.

Connection method A generic term for the sensor network and each network that can be connected using iQ Sensor Solution

CPU module A generic term for LCPUs, QCPUs, RCPUs, and FXCPUs.

Device supporting iQSS A generic term for devices which support iQ Sensor Solution.

Engineering tool A tool for setting, programming, debugging, and maintaining programmable controllers.

A generic term for GX Works2, GX Works3, MI Configurator, and MELSOFT Navigator.

Ethernet configuration An abbreviation for a system configuration connected with Ethernet.

FX5CPU A generic term for MELSEC iQ-F series CPU modules.

FXCPU A generic term for MELSEC-F series CPU modules.

GX Works2 A generic product name for SWnDND-GXW2 and SWnDNC-GXW2. ('n' indicates its version.)

GX Works2 Version 1.15R or later supports MELSOFT Navigator.

GX Works3 A generic product name for SWnDND-GXW3. ('n' indicates its version.)

ID Distinguishes an input or output based on an address.

• Output module ID: Address

• Input/combined module ID: Address + 200H

iQ Works An abbreviation for MELSOFT iQ Works.

iQSS An acronym for iQ Sensor Solution.

LCPU A generic term for MELSEC-L series CPU modules.

LHCPU A generic term for MELSEC iQ-L series CPU modules.

MELIPC An abbreviation for MELIPC MI5000 series.

MELSOFT Navigator A product name for the integrated development environment included in SWnDND-IQWK (MELSOFT iQ Works) ('n'

indicates its version.)

MI Configurator A generic product name for SWnDNN-MICONF-M. ('n' indicates its version.)

13

Profile Data that stores the information of a device supporting iQSS (such as a module model name).

QCPU A generic term for MELSEC-Q series CPU modules.

RCPU A generic term for MELSEC iQ-R series CPU modules.

Remote I/O module A generic term for basic digital input modules and basic digital output modules of CC-Link IE Field Network.

RnENCPU A generic term for R04ENCPU, R08ENCPU, R16ENCPU, R32ENCPU, and R120ENCPU.

Sensor parameter A generic term for parameters (such as threshold or sensor operation mode) of a device supporting iQSS.

Station sub-ID number An abbreviation for an ID number of a sensor connected to a communication unit for CC-Link.

Term Description

14

MEMO

15

PART 1

PART 1 iQ Sensor Solution

This part explains the overview of iQ Sensor Solution and its functions.

1 iQ Sensor Solution

2 iQ Sensor Solution FUNCTIONS

16

1 iQ Sensor Solution

iQ Sensor Solution is a solution to manage both partner products and programmable controllers with an engineering tool.

By sharing design information including system design and programming in the whole control system, the system design

efficiency and the programming efficiency can be improved, and the total cost of design, startup, operation, and maintenance

can be reduced.

Enables a total control using

Engineering tool

Devices supporting

iQSS

1 iQ Sensor Solution

1.1 Features of iQ Sensor Solution

17

1

1.1 Features of iQ Sensor Solution

By performing the functions of an engineering tool supporting iQ Sensor Solution, the information of devices supporting iQSS

connected to various networks can easily be saved/restored.

Easy startup

A system configuration diagram can easily be displayed on the screen of an engineering tool by detecting devices supporting

iQSS in the actual system configuration.

In addition, the displayed system configuration can be verified against the actual system configuration, and the

communication setting for Ethernet devices can easily be configured.

Automatic detection of connected devices

A system configuration diagram can automatically be created on the screen of an engineering tool by detecting devices

supporting iQSS in an actual system configuration.

Consequently, man-hours for creating a system configuration diagram at the system startup can be reduced.

Verification of connected devices and configurations

A displayed system configuration can be verified against the actual system configuration.

The modification man-hours at the system startup can be reduced.

Display a system configuration diagram detected automatically on

Engineering tool.

Devices supporting iQSS

Verify the created system configuration against

the actual system configuration.

Devices supporting iQSS

18

1 iQ Sensor Solution

1.1 Features of iQ Sensor Solution

Reflection of the communication setting

The communication setting, such as an IP address, for the different type of sensors can be set in the same setting screen.

The setting man-hours can be reduced since the setting can be set to a device supporting iQSS without starting dedicated

tools.

Easy tuning

Sensor parameters can be set efficiently in the same setting screen for sensors of different manufacturers.

Sensor parameter read/write

Sensor parameters can be set by the same operation without starting dedicated tools for each manufacturer.

Communication settings of devices

supporting iQSS can be configured.

Devices supporting iQSS

Various sensor parameters of devices supporting iQSS can be configured on

the same setting screen.

Page is loading ...

Mitsubishi Electric iQ Sensor Solution Owner's manual

Related papers

Other documents