Mitsubishi Electric MELSEC SW1DNC-CCIEF-B, MELSEC Q80BD-J71GF11-T2, MELSEC Q81BD-J71GF11-T2 User Manual

Download

CC-Link IE Field Network Interface Board User's Manual (For SW1DNC-CCIEF-B)

-Q80BD-J71GF11-T2

-Q81BD-J71GF11-T2

SAFETY PRECAUTIONS

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.

(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 user's manual for the CPU module used.

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.

[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 a personal computer. 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) The station to which the board is installed may be disconnected from the data link due to a data

link error. If this occurs, the data output from the station and written to other stations before the error will be held until the station is reconnected to the network (until its data link is restarted).Provide a mechanism for data link status monitoring and error handling for each station that is connected to the data link system.

● For the operating status of each station after a communication failure, refer to this manual. Incorrect output or malfunction due to a communication failure may result in an accident.

● When changing data during operation, configure an interlock circuit in the program to ensure that the entire system will always operate safely. And determine corrective actions to be taken between the personal computer and CPU module in case of a communication failure.

[Design Precautions]

CAUTION

● 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.

[Installation Precautions]

WARNING

● Turn off the power for the system in all phases before installing the board to or removing it from the personal computer. Failure to do so may result in electric shock or cause the board to fail or malfunction.

● Do not touch any connectors while power is on. Doing so may cause electric shock or malfunction.

[Installation Precautions]

CAUTION

● Use the board in an environment that meets the general specifications in this manual. Failure to do so may result in electric shock, fire, malfunction, or damage to or deterioration of the product.

● Do not directly touch any conductive parts and electronic components of the board. Doing so can cause malfunction or failure of the board.

● Do not disassemble or modify the boards. Doing so may cause failure, malfunction, injury, or a fire.

● Fix the board by tightening the board-fixing screws within the specified torque range. Undertightening

may cause drop, short circuit, or malfunction. Overtightening may damage the screw and/or board, resulting in drop, short circuit, or malfunction. For the tightening torque of the board-fixing screws, refer to the manual supplied with the personal computer.

● Before handling the board, touch a conducting object such as a grounded metal to discharge the static electricity from the human body. Failure to do so may cause the board to fail or malfunction.



● Install the board to a personal computer which is compliant with PCI standard or PCI Express standard (Page 31 Operating Environment). Failure to do so may cause a failure or malfunction.

● Securely insert the board into the PCI slot following the board installation instruction of the personal computer. Incorrect insertion of the board may cause malfunction, failure, or drop of the board.

● When installing the board, take care not to contact with other boards.

● When installing the board, take care not to get injured by an implemented component or a surrounding

member.

● Handle the board in a place where static electricity will not be generated. Failure to do so may cause a failure or malfunction.

● The board is included in an antistatic envelope. When storing or transporting it, be sure to put it in the antistatic envelope. Failure to do so may cause a failure or malfunction.

● Do not drop or apply a strong impact to the board. Doing so may cause a failure or malfunction.

[Wiring Precautions]

WARNING

● Turn off the power for the system in all phases before installing the board or starting wiring. Failure to do so may result in electric shock, damage to the product, or malfunction.

● After installation of the board and wiring, attach the cover on the module before turning it on for operation. Failure to do so may result in electric shock.

[Wiring Precautions]

CAUTION

● Place the communication cable connected to the board in a duct or clamp them. If not, dangling cables may swing or inadvertently be pulled, resulting in damage to the board or cables or malfunctions due to poor contact.

● When disconnecting the cable from the board, do not pull the cable by the cable part. Pulling the cable connected to the board may result in malfunction or damage to the board or cable.

● Prevent foreign matter such as dust or wire chips from entering the personal computer. Such foreign matter may cause a fire, failure, or malfunction.

● Do not install the 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.

● Securely plug the communication cable to the connector of the board. Then, check for any incomplete connection. Poor contact may cause an erroneous input or output.

● Always ground the personal computer to the protective ground conductor. Failure to do so may cause a malfunction.

[Startup and Maintenance Precautions]

WARNING

● Turn off the power for the system in all phases before cleaning the board or retightening the boardfixing screws. Failure to do so may result in electric shock, or cause a failure or malfunction of the board.

● Do not connect or disconnect any communication cable while power is on. Doing so may result in a malfunction.

[Startup and Maintenance Precautions]

CAUTION

● Thoroughly read the manual and ensure the safety before performing program modification during operation, forced output, operation such as RUN, STOP, and PAUSE. An improper operation will result in mechanical damage or accidents.

● Do not disassemble or modify the boards. Doing so may cause failure, malfunction, injury, or a fire.

● Fix the board by tightening the board-fixing screws within the specified torque range. Undertightening

● Before handling the board, touch a conducting object such as a grounded metal to discharge the static electricity from the human body. Failure to do so may cause the board to fail or malfunction.

● The board is included in an antistatic envelope. When storing or transporting it, be sure to put it in the antistatic envelope. Failure to do so may cause a failure or malfunction.

● The microprocessor built in the board will reach a high temperature during operation. Do not touch it directly when replacing the board. Doing so may result in a failure, malfunction or injury.

[Disposal Precautions]

CAUTION

● When disposing of this product, treat it as industrial waste.

CONDITIONS OF USE FOR THE PRODUCT

(1) Mitsubishi 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 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'S USER, 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 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 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 representative in your region.

CONSIDERATIONS FOR USE

Interlink transfer and routing functions

CC-Link IE Field Network board cannot be used as a relay station for the interlink transfer function or the routing function.

To use these functions, set a network module as a relay station.

Driver installation and updating

The consistency between the driver and utility cannot be identified, and CC-Link IE Field Network board may not operate

properly.

Do not install or update the driver other than the method written in the troubleshooting. Page 141 TROUBLESHOOTING

INTRODUCTION

Thank you for purchasing the Mitsubishi Electric network interface boards.

This manual describes the required system configuration, specifications, operating procedure, functions, and troubleshooting

of the relevant products listed below.

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

and performance of the CC-Link IE Field Network interface board to handle the product correctly.

Please make sure that the end users read this manual.

Relevant products

Q80BD-J71GF11-T2, Q81BD-J71GF11-T2

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

CONDITIONS OF USE FOR THE PRODUCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

CONSIDERATIONS FOR USE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

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

RELEVANT MANUALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

TERMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

PACKING LIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

CHAPTER 1 OVERVIEW 16

1.1 CC-Link IE Field Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

1.2 CC-Link IE Field Network Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

CHAPTER 2 SYSTEM CONFIGURATION 20

2.1 System Configuration Using CC-Link IE Field Network Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

2.2 CC-Link IE Field Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Single Network System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Multi-Network System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

2.3 Network Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Hubs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

2.4 Operating Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

CHAPTER 3 SPECIFICATIONS 35

3.1 General Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

3.2 Performance Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

3.3 List of Buffer Memory Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

CHAPTER 4 PROCEDURE BEFORE OPERATION 40

4.1 Procedure Before Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

4.2 Part Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Operation LED. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

4.3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Handling precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Installation environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Procedure for replacing mounting brackets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Board installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

4.4 Setting Channel Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

4.5 Tests Before Wiring (Standalone Tests of the Board) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Bus I/F test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Memory test. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Hardware test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Self-loopback test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

4.6 Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Wiring Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Ethernet cable connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

4.7 Tests After Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

CONTENTS

Loop test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Cable test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Communication test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

CHAPTER 5 FUNCTIONS 58

5.1 Function List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

5.2 Cyclic Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Data flow and link device assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Link scan and link refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Assurance of cyclic data integrity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Input status of data link faulty station setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Cyclic transmission stop and restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

5.3 Transient Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Communication on the same network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Communication with different networks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

5.4 SEND/RECV Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

5.5 Reserved Station Specification and Reserved Station Function Disable Function . . . . . . . . . . . . . . . . . . 75

5.6 Error Invalid Station and Temporary Error Invalid Station Setting Function. . . . . . . . . . . . . . . . . . . . . . . . 76

5.7 Event Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

5.8 Loopback Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

5.9 Driver WDT function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

CHAPTER 6 INSTALLING AND UNINSTALLING SOFTWARE PACKAGES 80

6.1 Installation and Uninstallation Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

6.2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Installation procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

When installation is completed normally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

When installation is aborted or failed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

6.3 Uninstallation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Uninstallation procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

When uninstallation is completed normally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

When uninstallation is failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

CHAPTER 7 OVERVIEW OF CC IE FIELD UTILITY 83

7.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

7.2 Menu List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

CHAPTER 8 SCREEN CONFIGURATION AND BASIC OPERATIONS 85

8.1 Starting and Exiting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

8.2 Screen Configuration and Basic Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Main frame configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Toolbars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Work windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

8.3 Help Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

CHAPTER 9 PROJECT MANAGEMENT 91

9.1 Creating Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

9.2 Opening Existing Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

9.3 Saving Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

9.4 Saving Projects with Compression and Unpacking Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94

9.5 Deleting Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

9.6 Closing Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

9.7 Verifying Project Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

CHAPTER 10 SETTING PARAMETERS 98

10.1 Parameter List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

10.2 Setting Network Parameter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Network type and mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Network configuration setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Network operation setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Event setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Driver setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Target setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Routing parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

CHAPTER 11 OPERATING BOARD ONLINE 112

11.1 Setting Board Channel Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

11.2 Writing/Reading Parameters to/from Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

11.3 Verifying Parameters of Board and Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

11.4 Resetting Board. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

CHAPTER 12 MONITORING 115

CHAPTER 13 DIAGNOSING BOARD STATUS 117

13.1 Diagnosing Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

13.2 Diagnosing CC-Link IE Field Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Selecting the diagnostics target. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Displaying diagnostics screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Communication test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Cable test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Link start/stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Network event history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Reserved station function enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Enable/Disable ignore station errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

CHAPTER 14 MELSEC DATA LINK LIBRARY 137

CONTENTS

CHAPTER 15 PROGRAMMING 139

15.1 Precautions on Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

CHAPTER 16 TROUBLESHOOTING 141

16.1 Error Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

16.2 Troubleshooting for Installation/Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Installation failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Uninstallation failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

Action displayed on the screen is not effective while installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

When the driver is not installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

16.3 Troubleshooting for Personal Computer and Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Personal computer does not start or shuts down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

Utility does not startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

The screen or operation is abnormal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

The screen for which corrective action is not clear, is displayed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Personal computer operates slowly. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

16.4 Troubleshooting for Board and Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Hardware error or board WDT error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Driver WDT error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Driver does not start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Bus error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

16.5 Troubleshooting for Data Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Communication error (ERR. LED is ON/Flashing) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

User program cannot access CPU modules other than QCPU (Q mode) and MELSEC iQ-R series CPU

modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Communication cannot be performed occasionally when executing user program . . . . . . . . . . . . . . . . . . . . .153

Station is disconnected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Communication is unstable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

16.6 Troubleshooting for Device Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Cyclic transmission cannot be performed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Transient transmission cannot be performed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

16.7 Checking method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Checking installation environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Check the board installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Checking cables and wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Checking operation environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Checking personal computer and operating system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Checking on Device Manager screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Checking operations with event viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Checking channel numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Checking operations with board diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Checking operations with tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Checking LED status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Checking network status with CC-Link IE Field Network diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164

Checking network status with monitoring link special relays (SB) and link special registers (SW) . . . . . . . . . . 164

Checking communication status with monitoring access target device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

16.8 Information Required for Inquiries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

16.9 Error Code List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

APPENDIX 176

Appendix 1 Precautions for Accessing Redundant CPU System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176

Redundant CPU specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Operation at occurrence of system switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176

Retry processing for the error that occurs during system switching processing . . . . . . . . . . . . . . . . . . . . . . . . 177

Automatic switching of communication path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Appendix 2 Details of Buffer Memory Addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Link device area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182

Offset/size information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

Own station information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Other station information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Appendix 3 Link Special Relay (SB) List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

Appendix 4 Link Special Register (SW) List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Appendix 5 Processing Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Link refresh time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Link scan time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

Transmission delay time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

Appendix 6 Differences in Cyclic Transmission Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

Appendix 7 Comparison of CC-Link and CC-Link IE Field Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

Appendix 8 Combinations with Existing Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

Appendix 9 Checking Serial Number and Function Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

Appendix 10New and Improved Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

Change of hardware function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

Update of software package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

Appendix 11Restrictions for Operating System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224

Appendix 12Windows Warning Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Overview of warning message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Methods for preventing warning message. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Appendix 13Behavior When Personal Computer Enters Power Save Mode or Fast Startup . . . . . . . . . . . . . . . 230

Behavior when the personal computer enters the power save mode (hibernate, sleep). . . . . . . . . . . . . . . . . . 230

Behavior when fast startup function is enabled. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

Appendix 14MELSECPowerManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Installing MELSECPowerManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Uninstalling MELSECPowerManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Checking MELSECPowerManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Appendix 15EMC and Low Voltage Directives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

Measures to comply with the EMC Directive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

Measures to comply with the Low Voltage Directive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .237

Appendix 16External Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Q80BD-J71GF11-T2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Q81BD-J71GF11-T2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

CONTENTS

INDEX 240

REVISIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242

WARRANTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .243

TRADEMARKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .244

RELEVANT MANUALS

Manual name [manual number] Description Available form

CC-Link IE Field Network Interface Board User's Manual (For SW1DNC-CCIEF-B) [SH-080980ENG] (this manual)

MELSEC-Q CC-Link IE Field Network Master/Local Module User's Manual [SH-080917ENG]

MELSEC iQ-R Ethernet/CC-Link IE User's Manual (Startup) [SH-081256ENG]

MELSEC iQ-R CC-Link IE Field Network User's Manual (Application) [SH-081259ENG]

MELSEC-L CC-Link IE Field Network Master/Local Module User's Manual [SH-080972ENG]

MELSEC Data Link Library Reference Manual [SH-081035ENG]

Overview of system configuration, specifications, functions, handling, wiring, and troubleshooting for CC-Link IE Field Network interface board.

Overview of the CC-Link IE Field Network, and specifications, procedures before operation, system configuration, installation, wiring, settings, functions, programming, and troubleshooting for MELSEC-Q series CC-Link IE Field Network master/local modules.

Specifications, procedures before operation, system configuration, wiring, and communication examples of Ethernet, CC-Link IE Controller Network, and CCLink IE Field Network

Functions, parameter settings, programming, troubleshooting, I/O signals, and buffer memory of CC-Link IE Field Network

Overview of the CC-Link IE Field Network, and specifications, procedures before operation, system configuration, installation, wiring, settings, functions, programming, and troubleshooting for MELSEC-L series CC-Link IE Field Network master/local modules.

Programming, function specifications, and sample programming for MELSEC data link library.

Print book

e-Manual PDF

Print book

PDF

Print book

e-Manual PDF

Print book

e-Manual PDF

Print book

e-Manual PDF

Print book

e-Manual PDF

e-Manual refers to the Mitsubishi 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.

• The hardware specifications of each part can be found from the product figures.

• Pages that users often browse can be bookmarked.

TERMS

Unless otherwise specified, this manual uses the following terms.

Term Description

Baton pass A token to send data over a network.

Board WDT Watchdog timer that monitors the operating status of network board.

Buffer memory A memory which is used to store data for communication between the CC-Link IE Field Network board and the master/local

module.

CC IE Field Utility Name for the utility included in the SW1DNC-CCIEF-B CC-Link IE Field Network software package.

CC-Link IE Controller Network board

CC-Link IE Field Network board A generic term for the Q80BD-J71GF11-T2 and Q81BD-J71GF11-T2 CC-Link IE Field Network interface board.

CC-Link Ver.2 board A generic term for the Q80BD-J61BT11N and Q81BD-J61BT11 CC-Link system master/local interface board.

CPU module A generic term for the MELSEC iQ-R series, or MELSEC-Q/L series CPU module.

Cyclic transmission A function by which data are periodically exchanged among stations on the same network using link devices (RX, RY,

Data link A generic term for cyclic transmission and transient transmission.

Dedicated instruction An instruction that simplifies programming for using functions of intelligent function modules.

Device A device (X, Y, M, D, or others) in a CPU module.

Disconnection A process of stopping data link if a data link error occurs.

Driver WDT An abbreviation for the watchdog timer that monitors the communication status between a network board and a personal

Ethernet adapter module An abbreviation for the NZ2GF-ETB CC-Link IE Field Network Ethernet adapter module.

GX Developer A generic product name for SW8D5C-GPPW.

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

Head module An abbreviation for the LJ72GF15-T2 CC-Link IE Field Network head module.

Intelligent device station A station that exchanges I/O signals (bit data) and I/O data (word data) with another station by cyclic transmission. This

Intelligent function module A MELSEC-Q/L series module that has functions other than input and output, such as an A/D converter module and D/A

Link device A device (RX, RY, RWw, or RWr) in a module and board of CC-Link IE Field Network.

Link refresh Data transfer between link devices of CC-Link IE Field Network board and the driver.

Link scan (Link scan time) Time required for all the stations on the network to transmit data. The link scan time depends on data volume and the

Link special register (SW) Word data that indicates the operating status and data link status of a module or board on CC-Link IE Field Network.

Link special relay (SB) Bit data that indicates the operating status and data link status of a module or board on CC-Link IE Field Network.

Local station A station that performs cyclic transmission and transient transmission with the master station and other local stations.

Loopback A function that disconnects the station in which an error has occurred, and continues data link with the stations that are

Master station A station that controls the entire network. This station can perform cyclic transmission and transient transmission with all

Master/local module A generic term for the QJ71GF11-T2 and LJ71GF11-T2 CC-Link IE Field Network master/local module.

MD function A generic term for functions in MELSEC data link library.

MELSECNET/H board A generic term for the Q80BD-J71LP21-25, Q81BD-J71LP21-25, Q80BD-J71LP21S-25, Q80BD-J71LP21G, Q80BD-

Network module A generic term for the following modules:

RAS An abbreviation for Reliability, Availability, and Serviceability. This term refers to usability of automated equipment.

Reconnection A process of restarting data link when a station recovers from an error.

Relay station A station that includes two or more network modules. Data are passed through this station to stations on other networks.

Remote device station A station that exchanges I/O signals (bit data) and I/O data (word data) with another station by cyclic transmission. This

Remote head module An abbreviation for RJ72GF15-T2 CC-Link IE Field Network remote head module.

A generic term for the Q80BD-J71GP21-SX, Q80BD-J71GP21S-SX, Q81BD-J71GP21-SX, and Q81BD-J71GP21S-SX CC-Link IE Controller Network interface board.

RWw, and RWr).

computer, or operating status of a personal computer.

station responds to a transient transmission request from another station and also issues a transient transmission request to another station.

converter module.

number of transient transmission requests.

operating normally. Stations connected after the faulty station can also continue data link.

stations. Only one master station can be used in a network.

J71LP21GE, and Q80BD-J71BR11 MELSECNET/H interface board.

• CC-Link IE Field Network module

• CC-Link IE Controller Network module

• MELSECNET/H module

• MELSECNET/10 module

station responds to a transient transmission request from another station.

Ter m Description

Remote I/O station A station that exchanges I/O signals (bit data) with the master station by cyclic transmission.

Remote input (RX) Bit data input from a slave station to the master station. (For some areas in a local station, data are input in the opposite

direction.)

Remote output (RY) Bit data output from the master station to a slave station. (For some areas in a local station, data are output in the opposite

Remote register (RWr) Word data input from a slave station to the master station. (For some areas in a local station, data are input in the opposite

Remote register (RWw) Word data output from the master station to a slave station. (For some areas in a local station, data are output in the

Reserved station A station reserved for future use. This station is not actually connected, but counted as a connected station.

Routing A process of selecting paths for communication with other networks.

Slave station A generic term for a local station, remote I/O station, remote device station, and intelligent device station.

SW1DNC-CCIEF-B A product name of the software package for CC-Link IE Field Network board.

Transient transmission A function of communication with another station, which is used when requested by dedicated instruction or utility.

direction.)

opposite direction.)

CC-Link IE Field Network requires communication paths to be preset using routing parameters to communicate with stations on different networks.

PACKING LIST

Before Using the Product

Software license agreement

SW1DNC-CCIEF-B

CC-Link IE

Field Network

software package

(CD-ROM)

Q80BD-J71GF11-T2 CC-Link IE

Field Network Interface Board

Before Using the Product

Software license agreement

Low Profile Bracket

SW1DNC-CCIEF-B

CC-Link IE

Field Network

software package

(CD-ROM)

Q81BD-J71GF11-T2 CC-Link IE

Field Network Interface Board

The following items are included in the package of this product. Before use, check that all the items are included.

Q80BD-J71GF11-T2

Q81BD-J71GF11-T2

1 OVERVIEW

RWw RWw

RWr RWr

Personal computer

Programmable controller

User

program

Driver

Board

Master/

local

module

CPU

module

1234H

Write request

Device

Write data

CPU module

Local station

Board

User program

1.1 CC-Link IE Field Network

CC-Link IE Field Network is a high-speed and large-capacity open field network that is based on Ethernet technology

(1000BASE-T).

Data communication

High-speed and large-capacity data communication is available between a master station and slave stations on the CC-Link

IE Field Network.

■Periodic communication (cyclic transmission)

Data is periodically communicated among stations within the same network. (Page 60 Cyclic Transmission)

■Non-periodic communication (transient transmission)

Data is communicated upon request. (Page 68 Transient Transmission)

1 Gbps communication speed

1 Gbps communication speed allows high-speed communication. Also, the tact time can be reduced due to the improved

performance of communication response.

1 OVERVIEW

1.1 CC-Link IE Field Network

Use of Ethernet cable

1000BASE-T

Star topology

Line topology

A 1000BASE-T-compliant Ethernet is used for the connection interface. The wiring cost can be reduced because 1000BASET-compliant Ethernet cables are commercially available. (Page 30 Cables)

Flexible wiring for the system arrangements

The network can be wired into star topology, line topology, and ring topology. (Page 21 Network configuration) For star topology, a 1000BASE-T design switching hub can be used. (Page 30 Hubs)

Wiring is highly flexible because a network can consist of a combination of star and line topologies. For example, the control

panels can be connected through a star topology and the production lines through a line topology.

1 OVERVIEW

1.1 CC-Link IE Field Network

1.2 CC-Link IE Field Network Board

CC-Link IE

Field Network

A control system using a programming language such as C language can be configured when a personal computer is used as a master station.

Control data and logging data can be collected at high speed when a personal computer is used as a local station.

CC-Link IE Field Network board allows the connection of a personal computer to CC-Link IE Field Network.

CC-Link IE Field Network board can be used as either a master station or local stations of CC-Link IE Field Network.

A personal computer can be easily connected to CC-Link IE Field Network

A system which contains a personal computer as a master station or local stations of the CC-Link IE Field Network system

can be configured.

System controls and high-speed data collection

For a reduction of tact time in a manufacturing system, control data, logging data of manufacturing processes, management

data for traceability, and management/diagnostic data for equipment predictive maintenance can be collected at high speed

and monitored.

A control system using a programming language such as C language can be configured when a personal computer is used as

a master station.

Control data and logging data can be collected at high speed when a personal computer is used as a local station.

1 OVERVIEW

1.2 CC-Link IE Field Network Board

User programs created using existing boards can be utilized

main(){ mdOpen(181,-1,&path); mdSend(path,255, , ); mdClose(path); }

User programs created using the existing boards can be utilized.

CC-Link IE Field Network board

CC-Link Ver.2 board etc.

Display error locations

Display event history

Display error occurrence

For user programs to use CC-Link IE Field Network board, the function-level compatibility can be maintained because the

common interface (MELSEC data link functions) with the existing boards can be used.

Therefore, user programs created using the existing boards such as CC-Link IE Controller Network board, CC-Link Ver.2

board, MELSECNET/H board, can be utilized for CC-Link IE Field Network board.

Program creation time can be shortened since the users who previously used the existing boards do not need to create a new

user program.

Checking CC-Link IE Field Network status on the screen

The status of CC-Link IE Field Network can be checked using CC IE Field Utility. Error locations, error causes, and event

history are displayed on the screen. This helps to reduce the time for the system to recover from the error. (Page 117 DIAGNOSING BOARD STATUS)

1 OVERVIEW

1.2 CC-Link IE Field Network Board

2 SYSTEM CONFIGURATION

SW1DNC-CCIEF-B

Install

Personal computer

Install

Connect

CC-Link IE Field

Network board

Ethernet

cable

CC-Link IE Field

Network system

Switching hub

Ethernet cable (1000BASE-T)

Master station

1 station

Slave station

Up to 120 stations

2.1 System Configuration Using CC-Link IE Field

Network Board

A system configuration when using the CC-Link IE Field Network board which is installed to a personal computer is shown

below.

2.2 CC-Link IE Field Network Configuration

This section explains CC-Link IE Field Network configurations.

Single Network System

Overall system configuration

Single network system is a system that consists of a master station and slave stations connected by Ethernet cables as

shown below. Up to 120 slave stations and 1 master station can be connected.

2 SYSTEM CONFIGURATION

2.1 System Configuration Using CC-Link IE Field Network Board

Network configuration

Switching hub

Star topology

Line topology

Star and line mixed

Ring topology

Ethernet cable (1000BASE-T)

The network can be wired into star topology, line topology, and ring topology.

A network can consist of a combination of star and line topologies but cannot consist of a combination of ring topology and

star or line topology.

Item Description

Star topology The network is formed into a star with a switching hub. Slave stations can be easily added by this topology. (Add slave stations one by

Line topology The connection between the board and modules using an Ethernet cable makes a line topology. For line topology, connections are

Ring topology The connection between the board and modules using an Ethernet cable makes a ring topology. Data link continues with the stations that

one. If multiple slave stations are added at a time, all stations on the network are reconnected. Therefore, an error may momentarily occur in all the stations.)

available without using a switching hub.

are operating normally.

2 SYSTEM CONFIGURATION

2.2 CC-Link IE Field Network Configuration

Only the slave station in which an error has occurred is disconnected from the network. Data link continues

Line topology

Ring topology

Master station (Station No.0)

Error

Stations after the faulty station Master station (Station No.0) are disconnected.

The system will continue data link among normal stations only.

with the stations that are operating normally. In a line topology, all stations connected after the faulty station

are disconnected. In ring topology, data link continues with the stations that are operating normally.

2 SYSTEM CONFIGURATION

2.2 CC-Link IE Field Network Configuration

Multi-Network System

CC-Link IE

Controller Network

Network No.3

(Relay station)

(Relay

station)

Network No.1

Network No.2

CC-Link IE

Field Network

CC-Link IE

Field Network

The multi-network system is a system in which multiple networks are connected by some relay stations. Up to 239 networks

can be connected.

Cyclic transmission is available only in the same network.

Transient transmission is available with other networks as well as the same network. Communications can be made with stations on up to the eighth network (the number of relay stations: 7). (Page 69

Communication with different networks)

2 SYSTEM CONFIGURATION

2.2 CC-Link IE Field Network Configuration

Precautions

Adding slave stations (including the submaster stations)

If a slave station (including a submaster station) is added to a system having 120 slave stations (including a submaster

station), the system operates as follows.

■When a serial number (first five digits) of the master station is '17022' or higher

Baton pass and data link are not performed in the slave stations (including the submaster stations) added after the 121st

station, and other stations continues baton pass and data link.

Even if the disconnected stations are returned to a system having 121 or more slave stations (including a submaster station),

the stations may not start data link.

• Whether 121 or more slave stations (including a submaster station) are connected can be checked using

the following. ⋅ "Selected Station Communication Status Monitor" of CC-Link IE Field diagnostics (Page 119

Displaying diagnostics screen)

⋅ Number of connected modules over occurrence status (SB0099)

Number of connected modules detected by Number of connected modules over occurrence status

(SB0099) is the total of the slave stations (including a submaster station) which are currently connected and

the disconnected stations (slave stations which were previously connected).

• The number of stations which were previously connected can be reset by removing the disconnected station

of the CC-Link IE Field Network diagnostics. (Page 119 Displaying diagnostics screen)

A data link error may momentarily occur in all the stations and output of the connected slave stations may

turn OFF since all stations on the network will be reconnected when removing the disconnected station. Set it to maintain output data if needed. (Page 104 Network operation setting)

■When a serial number (first five digits) of the master station is '17021' or lower

All stations will fail and data link cannot be performed.

Connecting devices to the same network

To a switching hub on CC-Link IE Field Network, do not connect an Ethernet device (e.g. personal computer) on a network

other than CC-Link IE Field Network. Doing so will cause timeout in the master station, resulting in disconnection among all

stations.

2 SYSTEM CONFIGURATION

2.2 CC-Link IE Field Network Configuration

Configuration in which data link cannot be performed (incorrect ring topology)

Switching hub

Cannot connect both Ethernet ports to the switching hub.

Switching hub

Do not wire devices as shown below. Doing so will cause an error in all stations and data link cannot be performed.

• Connecting both PORT1 and PORT2 to the switching hub

• Ring topology through a switching hub

Ring topology

To configure a network in ring topology, set "Use" for "Loopback Function Setting" in the Network Parameter screen for the master station. (Page 102 Supplementary setting)

When a module is used for the master station, check if the module version supports the loopback function. MELSEC-Q CC-Link IE Field Network Master/Local Module User's Manual

■Configuring a network in ring topology using a switching hub

If a network is configured in ring topology through the two ports of the switching hub, the following problems may arise.

Therefore, do not use a switching hub for ring topology.

• Loopback cannot be detected if an Ethernet cable is disconnected.

• If a station is disconnected due to failure or power-OFF, data link will stop.

2 SYSTEM CONFIGURATION

2.2 CC-Link IE Field Network Configuration

■There is an offline mode station on a network configured in ring topology.

No loopback is detected.

Master station Station in Offline mode

No loopback is detected.

Master station

Station in Offline mode

Error

In the following cases, the master station or the station connected to the offline mode station cannot detect loopback.

• Either of the Ethernet cables connected to the offline mode station is disconnected.

• A station connected to the offline mode station is disconnected.

To detect loopback, set the offline mode station as a reserved station.

When the offline mode station is disconnected, loopback can be detected.

2 SYSTEM CONFIGURATION

2.2 CC-Link IE Field Network Configuration

Connecting/disconnecting a cable and turning OFF/ON a device

Insertion/removal or turning OFF/ON

Instantaneous

error on all

stations.

This section explains the following operations.

Network Configuration Operations

Star topology • Turning OFF/ON a system on a slave station or the switching hub

• Connecting/disconnecting an Ethernet cable connected to the switching hub

• Disconnecting an Ethernet cable from a slave station and connecting it to another slave station or the switching hub

Line topology, ring topology • Simultaneously turning OFF/ON systems on multiple stations

• Simultaneously connecting/disconnecting Ethernet cables to/from multiple stations

(When a data link error station returns, a data link error will occur in all the stations.)

■When a serial number (first five digits) of the master station is '17022' or higher

The actual network configuration and the network map of the CC-Link IE Field Network diagnostics may be a mismatch.

Whether mismatch is occurred or not can be checked using 'Network configuration mismatch occurrence status' (SB0098).

When using a ring topology, the following may be occurred.

• The station number of the loopback station cannot be detected correctly.

• Even if a switching hub is used, data link does not stop.

The actual network configuration and network configuration diagram can be matched by removing the disconnected station of the CC-Link IE Field Network diagnostics. (Page 119 Displaying diagnostics

screen)

A data link error may momentarily occur in all the stations and output of the connected slave stations may turn

OFF since all stations on the network will be reconnected when removing the disconnected station. Set it to maintain output data if needed. (Page 104 Network operation setting)

■When a serial number (first five digits) of the master station is '17021' or lower

A data link error may momentarily occur in all the stations and outputs of the connected slave stations may turn OFF since all

stations on the network will be reconnected.

For a measure to above error, set the "Network Operation Setting" to maintain inputs from data link error station when outputs need to be maintained at an occurrence of a data link error. (Page 104 Network operation setting)

2 SYSTEM CONFIGURATION

2.2 CC-Link IE Field Network Configuration

Data link error in all stations when starting a personal computer

Duplication

Station No.0

Station No.1

Station No.2

(Data link may stop.)

Errors occur in all stations when a personal computer is started.

This is because the line between P1 and P2 of CC-Link IE Field Network board is disconnected under the following

conditions.

• The power of the personal computer is turned OFF. (The line becomes in a conduction state when the power is turned ON.)

• A reconnection is in progress when starting a board driver.

As a result, the following reconnection occurs and causes an error in all station.

• A reconnection of CC-Link IE Field Network board installed in a personal computer.

• A reconnection of station which is located beyond the CC-Link IE Field Network board from the point of the master station.

If multiple boards are installed in a single personal computer, this symptom occurs for the same number of times as the

number of installed boards.

Connected station numbers

Connected station numbers should not be duplicated. Data link may be stopped when the station number is duplicated.

Turn-ON order

To avoid incorrect input from slave stations, turn ON slave stations first and then the master station.

2 SYSTEM CONFIGURATION

2.2 CC-Link IE Field Network Configuration

Precautions for when connecting the MELSEC iQ-R series module

Note that the following points when connecting a MELSEC iQ-R series module in the system where a CC-Link IE Field

Network board is used as the master station.

■Connecting to a local station or remote head module of a MELSEC iQ-R series

When connecting to a local station or remote head module of a MELSEC iQ-R series module, note the following points.

• Use SW1DNC-CCIEF-B Version 1.06G or later.

• Use a CC-Link IE Field Network board with a serial number of which the first five digits are '16012' or higher.

• When using a CC-Link IE Field Network board with a serial number of which the first five digits are '16011' or lower, set the

RX/RY setting in "Network Configuration Settings" that will be assigned to the master station with the following corrective

actions:

Action Example

Set the largest end number in all stations to multiples of 32 - 1 by changing the number of cyclic assignment points or adding the reserved station.

• Before change

• After change

Reduce the largest end number in all stations to 7FH or less. • Before change

• After change

■Connecting to a MELSEC iQ-R series redundant system

When connecting to a MELSEC iQ-R series redundant system including CC-Link IE Field Network, note the following points.

• Use SW1DNC-CCIEF-B Version 1.06G or later.

• Use a CC-Link IE Field Network board with a serial number of which the first five digits are '18042' or higher.

• Access to a MELSEC iQ-R series redundant CPU, in which a MELSEC data link library is used, not available. To access to

a MELSEC iQ-R series redundant system, use the supported software (GX Works3).

2 SYSTEM CONFIGURATION

2.2 CC-Link IE Field Network Configuration

2.3 Network Components

The CC-Link IE Field Network consists of the following.

Cables

For wiring, use the 1000BASE-T-compliant Ethernet cables.

Ethernet cable Connector Standard

Category 5e or more (Double shielded/STP) Straight cable

• For CC-Link IE Field Network wiring, use the recommended wiring components by CC-Link Partner

Association.

• Cables for CC-Link IE Controller Network cannot be used for CC-Link IE Field Network.

Product

For any type of queries related to the cables for CC-Link IE Field Network, please consult your local Mitsubishi representative.

Also, the connector processing of cable length is available for your preference. Please consult your local Mitsubishi

representative.

Type Model (manufacturer)

CC-Link IE Field Network cable SC-E5EW series (Mitsubishi Electric System & Service Co., Ltd.)

RJ45 connector The following conditioning cables:

IEEE802.3 (1000BASE-T) ANSI/TIA/EIA-568-B (Category 5e)

■Cable types

The following cable types are available depending on the operating environment.

• Standard type: Cables for inside the control panel and indoor connection

• L type: Cables for outdoor connection

Also for any type of queries related to the cables and relay adapters of flame retardant or waterproof type, please consult your

local Mitsubishi representative.

Hubs

Use hubs that meet the conditions listed below. Operation is not guaranteed if the hubs do not meet these conditions.

• Compliance with the IEEE802.3 (1000BASE-T)

• Support of the auto MDI/MDI-X negotiation function

• Support of the auto-negotiation function

• Switching hub (layer 2 switch)

*1 A repeater hub is not available.

Mitsubishi product

Type Model name

Industrial switching hub NZ2EHG-T8 (discontinued product), NZ2EHG-T8N

Industrial Managed Switch NZ2MHG-T8F2

2 SYSTEM CONFIGURATION

2.3 Network Components

2.4 Operating Environment

The following table shows the operating environment for the CC-Link IE Field Network board.

Item Description

Personal computer A personal computer on which Microsoft Windows operates

CPU System requirements of the operating system must be met.

Required memory

PCI bus specifications For Q80BD-J71GF11-T2

• Compliant with PCI standard Rev.2.2 (3.3 VDC/5 VDC, 32-bit bus, Reference clock 33 MHz)



PCI Express

Available hard disk capacity 1GB or more

Disk drive CD-ROM disk drive

Monitor Resolution: 1024 × 768 dots or higher

Operating system (English version) • Windows Server

Programming language (English version)

bus specifications For Q81BD-J71GF11-T2

• Compliant with PCI Express standard Rev.1.1 (3.3 VDC, Link width 1 lane, Reference clock 100 MHz)



• Windows Server 2016 (Standard)

• Windows 10 (Home, Pro, Enterprise, Education, IoT Enterprise 2016 LTSB*2)

• Windows 8.1, Windows 8.1 (Pro, Enterprise)

• Windows Server 2012 R2 (Standard)

• Windows 8, Windows 8 (Pro, Enterprise)

• Windows Server 2012 (Standard)

• Windows 7 (Home Premium, Professional, Ultimate, Enterprise)

• Windows Server 2008 R2 (Standard, Enterprise)

When using any of the following operating systems, use SW1DNC-CCIEF-B with the version 1.09K or earlier.

• Windows Server 2008 (Standard (x86, x64), Enterprise (x86, x64))

• Windows Vista

• Windows Server 2003 R2 (Standard (x86, x64), Enterprise Edition (x86, x64)) SP2 or later

• Windows XP

Visual Basic and Visual C++ in the following Microsoft Visual Studio: Visual Studio 2017, Visual Studio 2015, Visual Studio 2013, Visual Studio 2012, Visual Studio 2010, Visual Studio 2008, Visual Studio 2005, Visual Studio .NET 2003

2019 (Standard)



(Home Basic, Home Premium, Ultimate, Business, Enterprise) SP2 or later



(Professional, Home Edition) SP3 or later

*1 Apply Windows Updates (KB4132216, KB4091664, KB4465659, and KB4480977). *2 64-bit version only *3 Apply Service Pack1 and Security Update for Windows (KB3033929). Otherwise, use SW1DNC-CCIEF-B Version 1.09K or earlier. *4 32-bit version only

For the information on how to obtain SW1DNC-CCIEF-B version 1.09K or earlier, refer to the following

section. Page 224 Restrictions for Operating System

2 SYSTEM CONFIGURATION

2.4 Operating Environment

Instructions for personal computer

■PCI standard

When a personal computer which is not compliant with the PCI or PCI Express standard is used, troubles caused by failures

such as a contact failure or operation error may occur. This board may not operate when a PCI Express slot for graphics is

used.

For details of the number of boards that can be installed, installation slots, and occupied slots, refer to the following section. Page 36 Performance Specifications

Instructions for operating system

■Supported version of SW1DNC-CCIEF-B

Operating system Supported version

Q80BD-J71GF11-T2 Q81BD-J71GF11-T2

Windows Server 2019, Windows Server 2016, Windows 10 (IoT Enterprise 2016 LTSB) 1.16S or later 1.16S or later

Windows 10 (Home, Pro, Enterprise, Education) 1.10L or later 1.10L or later

Windows 8.1, Windows Server 2012 R2 1.06G or later 1.06G or later

Windows 8, Windows Server 2012 1.05F or later 1.04E or later

Windows 7 (64-bit version), Windows Server 2008 R2 1.02C or later

Windows 7 (32-bit version) All versions

Windows Server 2008 (64-bit version) 1.05F to 1.09K 1.02C to 1.09K

Windows Server 2008 (32-bit version) 1.09K or earlier

Windows Vista

Windows Server 2003 R2 (64-bit version) 1.02C to 1.09K

Windows Server 2003 R2 (32-bit version) 1.09K or earlier

Windows XP

■User authority

Log on as a user with administrator authority.

• Installation and uninstallation are available only by the administrator's authority.

• The Usage of utilities is available only by the administrator's authority.

■Secure Boot function

For the following operating system, disable UEFI (BIOS) Secure Boot function or use SW1DNC-CCIEF-B Version 1.13P or

later.

• Windows 10 Version 1607 (Build number '14393' or higher)

*1 It is not included when upgrading from Windows 10 Version 1511 or others by using Windows 10 Anniversary Update.

For the method for checking the version of an operating system and the status of Secure Boot, refer to technical bulletin FA-A-

0235.

■.NET Framework 3.5

When using one of the following operating system, the .NET Framework 3.5 is required.

• Windows Server 2019

• Windows Server 2016

• Windows 10

• Windows 8.1

• Windows Server 2012 R2

• Windows 8

• Windows Server 2012

Enable the .NET Framework 3.5 (including .NET 2.0 or 3.0) in "Turn Windows features on or off" on the control panel.

2 SYSTEM CONFIGURATION

2.4 Operating Environment

■Upgrading and updating an operating system

Upgrading an operating system and updating from Windows 8 to Windows 8.1 are not supported.

Install SW1DNC-CCIEF-B by following the procedure:

1. Uninstall SW1DNC-CCIEF-B.

2. Upgrade or update the operating system.

3. Install SW1DNC-CCIEF-B with the software version supporting the changed operating system.

■The functions cannot be used

When using any of the following functions, this product may not operate properly.

• Activating the application with Windows compatible mode.

• Simplified user switch-over

• Remote desktop

• Power save mode (Hibernate, Sleep)

• Fast startup

• The language switching function set by Regional and Language Options

• Windows XP Mode

• Windows Touch or Touch

• Modern UI

• Client Hyper-V

• Server Core Installation

• Tablet mode

• Virtual desktop

• Unified Write Filter

In the following cases, the screen of this product may not work properly.

• The size of the text and/or other items on the screen are changed to values other than default values (such as 96 DPI,

100%, and 9 pt).

• The resolution of the screen is changed in operation.

• The multi-display is set.

• When exiting the operating system, always shut down the computer.

• For the behavior when entering the power save mode, refer to the following section.

(Page 230 Behavior When Personal Computer Enters Power Save Mode or Fast Startup)

2 SYSTEM CONFIGURATION

2.4 Operating Environment

Instructions for user program

■Supported version of SW1DNC-CCIEF-B

User program Supported version

32-bit version user program

64-bit version user program

*1 Programs can be created and executed on the 64-bit version operating system. *2 Programs can be created on the 32-bit version operating system, however, the following screen appears and cannot be executed.

■Language environment

• User programs created in the Japanese environment work only in the Japanese environment.

• User programs created in the English environment work only in the English environment.

■MELSEC data link library

For precautions when using MELSEC data link library, refer to the following manual. MELSEC Data Link Library Reference Manual

All versions

1.02C or later

2 SYSTEM CONFIGURATION

2.4 Operating Environment

3 SPECIFICATIONS

This chapter explains general and performance specifications of CC-Link IE Field Network board.

3.1 General Specifications

General specifications of CC-Link IE Field Network board are shown below.

Item Specification

Operating ambient temperature 0 to 55

Storage ambient temperature -25 to 75

Operating ambient humidity 5 to 95% RH, non-condensing

Storage ambient humidity

Vibration resistance Compliant

Shock resistance Compliant with JIS B 3502 and IEC 61131-2 (147 m/, 3 times each in X, Y, and Z directions)

Operating atmosphere No corrosive gases

Operating altitude

Installation location Inside a control panel

Overvoltage category

Pollution degree

with JIS B 3502 and IEC 61131-2

0 to 2000 m

II or less

2 or less

 Frequency Constant

Under intermittent vibration

Under continuous vibration

5 to 8.4 Hz  3.5 mm 10 times each in X, Y,

8.4 to 150 Hz 9.8 m/

5 to 8.4 Hz  1.75 mm 

8.4 to 150 Hz 4.9 m/

acceleration

Half amplitude Sweep count

and Z directions

*1 Do not use or store the board under the environment where the atmospheric pressure is higher than the one at the altitude of 0 m. Doing

so may cause a malfunction.

*2 This indicates the section of the power supply to which the equipment is assumed to be connected between the public electrical power

distribution network and the machinery within premises. Category II applies to equipment for which electrical power is supplied from fixed facilities. The surge voltage withstand level for up to the rated voltage of 300V is 2500V.

*3 This index indicates the degree to which conductive material is generated in terms of the environment in which the equipment is used.

Pollution degree 2 is when only non-conductive pollution occurs. A temporary conductivity caused by condensing must be expected occasionally.

The general specifications both CC-Link IE Field Network board and a personal computer must be satisfied

after installation.

3 SPECIFICATIONS

3.1 General Specifications

3.2 Performance Specifications

Performance specifications of the CC-Link IE Field Network board are shown below.

Item Specification

Maximum link points per network RX 16384 points, 2 KB

RY 16384 points, 2 KB

RWr 8192 points, 16 KB

RWw 8192 points, 16 KB

Maximum link points per station

Communication speed 1 Gbps

Connection cable An Ethernet cable that meets the 1000BASE-T standard:

Maximum station-to-station distance 100 m (compliant with ANSI/TIA/EIA-568-B (Category 5e))

Overall cable distance Line topology: 12000 m (when connected to 1 master station and 120 slave stations)

Number of cascade connections Up to 20

Network topology Line topology, star topology (coexistence of line topology and star topology is possible.), ring

Number of connectable stations per network

Maximum number of networks 239

Communication method Token passing method

Master station RX 16384 points, 2 KB

RY 16384 points, 2 KB

RWr 8192 points, 16 KB

RWw 8192 points, 16 KB

Local station

Master station 1 station (up to 120 slave stations can be connected to master station)

Local station 120 stations

RX 2048 points, 256 bytes

RY 2048 points, 256 bytes

RWr 1024 points, 2048 bytes

RWw 1024 points, 2048 bytes

Category 5e or higher (double shielded, STP), straight cable (Page 30 Cables)

(Page 50 Precautions for Ethernet cable)

Star topology: Depends on the system configuration Ring topology: 12100 m (when connected to 1 master station and 120 slave stations)

topology

*1 This indicates the point which can be assigned for one station by master station. For local station, the data from other station can be

received other than these points.

*2 For "Online (High-speed mode)", 256 points and 512 bytes. (Page 100 Network type and mode)

Item Specification

Q80BD-J71GF11-T2 Q81BD-J71GF11-T2

Number of boards that can be installed

Installation slot PCI slot or PCI-X slot

Occupied slots 1 slot 1 slot

Internal current consumption 1.10 A (5 VDC) 1.68 A (3.3 VDC)

Weight 0.11 kg Standard size: 0.08 kg

Up to 4

(Half size)



PCI Express (Standard/low profile, half size)

Low profile size: 0.07 kg

x1, x4, x8, x16 slot

3 SPECIFICATIONS

3.2 Performance Specifications

3.3 List of Buffer Memory Addresses

The buffer memory is used for exchanging data between the CC-Link IE Field Network board and the master/local module.

The content of the buffer memory returns to the default (initial values) when the power is turned OFF or the CC-Link IE Field

Network board is reset.

Address (Decimal (Hexadecimal))

0 to 1023 (0 to 3FFH)

1024 to 2047 (400H to 7FFH)

2048 to 10239 (800H to 27FFH)

10240 to 18431 (2800H to 47FFH)

18432 to 18463 (4800H to 481FH)

18464 to 18975 (4820H to 4A1FH)

18976 to 19455 (4A20H to 4BFFH)

19456 (4C00H)

19457 (4C01H)

to to

19694 (4CEEH)

19695 (4CEFH)

19696 to 19711 (4CF0H to 4CFFH)

19712 (4D00H)

19713 (4D01H)

to to

19950 (4DEEH)

19951 (4DEFH)

19952 to 19967 (4DF0H to 4DFFH)

19968 (4E00H)

19969 (4E01H)

to to

20206 (4EEEH)

20207 (4EEFH)

20208 to 20223 (4EF0H to 4EFFH)

Name Initial

Read, write Reference

value

Link device area Remote input (RX) 0 Read Page 182

Remote output (RY) Read, write

Remote register (RWw)

Remote register (RWr) Read

Link special relay (SB) • 18432 to 18433 for

read and write

• 18434 to 18463 for read only

Link special register (SW) • 18464 to 18495 for

read and write

• 18496 to 18975 for read only

System area 

RX offset/size information Station No.1 RX offset 0 Read Page 184

Station No.1 RX size

Station No.120 RX offset

Station No.120 RX size

System area 

RY offset/size information Station No.1 RY offset 0 Read Page 184

Station No.1 RY size

Station No.120 RY offset

Station No.120 RY size

System area 

RWw offset/size information Station No.1 RWw offset 0 Read Page 185

Station No.1 RWw size

Station No.120 RWw offset

Station No.120 RWw size

System area 

Link device area

RX offset/size information (Address 19456 to 19695 (4C00H to 4CEFH))

RY offset/size information (Address 19712 to 19951 (4D00H to 4DEFH))

RWw offset/ size information (Address 19968 to 20207 (4E00H to 4EEFH))

3 SPECIFICATIONS

3.3 List of Buffer Memory Addresses

Address

Name Initial (Decimal (Hexadecimal))

20224 (4F00H)

20225 (4F01H)

to to

20462 (4FEEH)

20463 (4FEFH)

20464 to 20511 (4FF0H to 501FH)

20512 (5020H)

20513 (5021H)

20514 (5022H)

20515 (5023H)

20516 to 20519 (5024H to 5027H)

20520 (5028H)

20521 (5029H)

20522 (502AH)

20523 (502BH)

20524 (502CH)

20525 to 20534 (502DH to 5036H)

20535 to 20536 (5037H to 5038H)

20537 to 20538 (5039H to 503AH)

20544 (5040H)

20545 (5041H)

20546 (5042H)

20547 (5043H)

20548 to 20551 (5044H to 5047H)

RWr offset/size information Station No.1 RWr offset 0 Read Page 185

System area 

Own station information

(network card information)

System area 

Own station information

(controller information)

System area 

Other station information (station

No.1)

(network card information)

Read, write Reference

value

RWr offset/

Station No.1 RWr size

Station No.120 RWr offset

Station No.120 RWr size

Manufacturer code 0 Read Page 186

Model type

Model code 1

Versi on

Controller information valid/invalid flag

Manufacturer code

Model type

Model code

Versi on

Model name string

Vendor-specific device information

Manufacturer code 0 Read Page 187

Model type

el code

Mod

Versi on

System area 

0 Read, write Page 186

size information (Address 20224 to 20463 (4F00H to 4FEFH))

Network card information (Address 20512 to 20515 (5020H to 5023H))

Controller information (Address 20520 to 20536 (5028H to 5038H))

Station number 1 (Address 20544 to 20575 (5040H to 505FH))

3 SPECIFICATIONS

3.3 List of Buffer Memory Addresses

Address (Decimal (Hexadecimal))

20552 (5048H)

20553 (5049H)

20554 (504AH)

20555 (504BH)

20556 (504CH)

20557 to 20566 (504DH to 5056H)

20567 to 20568 (5057H to 5058H)

20569 to 20575 (5059H to 505FH)

20576 to 24383 (5060H to 5F3FH)

24384 to 32767 (5F40H to 7FFFH)

Name Initial

Read, write Reference

value

Other station information (station

No.1)

(controller information)

Other station information

(station No.2 to No.120)

System area 

Controller information valid/invalid flag

Manufacturer code

Model type

Model code

Versi on

Model name string

Vendor-specific device information

System area 

Same as other station information (station No.1) 

0Read Page 187

Station number 1 (Address 20544 to 20575 (5040H to 505FH))

Do not write data to "System area".

Doing so may cause malfunction of the system.

3 SPECIFICATIONS

3.3 List of Buffer Memory Addresses

4 PROCEDURE BEFORE OPERATION

Start

Check

Install the software package on a personal computer.

Install the software package

Install the board

Install the board to a slot on the personal computer.

Set the channel number

Set the channel number and confirm it with the utility.

Check the board

Test the hardware of the installed board.

Wire the cables

Wire the network cables for the installed board.

Set the parameters

Set the parameters and check them with the utility.

Check the network

Test the cable connection and data link on the network.

Execute a user program

Execute a user program or utility.

End

4.1 Procedure Before Operation

This section explains the procedure before operating the CC-Link IE Field Network board.

Page 80 Installation

Page 45 Board installation

Page 46 Setting Channel Numbers

Page 47 Tests Before Wiring (Standalone Tests of the Board)

Page 50 Wiring

Page 98 SETTING PARAMETERS

Page 54 Tests After Wiring

4 PROCEDURE BEFORE OPERATION

4.1 Procedure Before Operation

4.2 Part Names

(1)

(2)

(3)

(1)

(2)

(3)

This section explains each part name of the CC-Link IE Field Network board.

Q80BD-J71GF11-T2

Q81BD-J71GF11-T2 (standard size)

4 PROCEDURE BEFORE OPERATION

4.2 Part Names

Q81BD-J71GF11-T2 (low profile size)

(1)

(2)

(3)

Number Name Description Reference

(1) Operation LED Indicates the operating status of the CC-Link IE Field Network board. Page 42 Operation LED

(2) P1 PORT1 connector for connecting to CC-Link IE Field Network. Page 43 Connector

(3) P2 PORT2 connector for connecting to CC-Link IE Field Network.

Operation LED

The operating status of the CC-Link IE Field Network board is displayed. If an error occurred, refer to the troubleshooting and take a corrective action. (Page 161 Checking LED status)

When the RUN LED is OFF or ON

The same LED display as a network module.

Name Status Description

RUN ON Operating normally.

OFF One of the following error has occurred.

ERR. ON One of the following error has occurred.

Flashing A data link error station is detected.

OFF Operating normally

SD ON Sending data

OFF Data not sent

RD ON Receiving data

OFF Data not received

• A hardware failure or a board WDT error has occurred.

• The driver is not started.

• An error is detected in all stations.

• Stations with same station number exist on the network.

• Network parameters are corrupted.

• Network parameters do not match the installation status.

(Reserved station specification, number of connected stations, network number etc.)

4 PROCEDURE BEFORE OPERATION

4.2 Part Names

When the RUN LED is flashing

<181> <182> <183>

<184>

L ER LED

LINK LED

RJ45 connector

An error which is peculiar to boards has occurred.

Name Status Description

RUN Flashing One of the following error has occurred. (Check ERR.LED, and RD LED.)

ERR. ON PCI bus/PCI Express bus error has occurred.

RD ON Driver WDT error has occurred.

When checking channel number

The status is displayed as shown below according to the current channel number while opening the "Channel No. Setting" screen. (Page 112 Setting Board Channel Numbers).

Connector

The PORT1 and PORT2 connector for CC-Link IE Field Network.

RJ45 connector

Connect an Ethernet cable. (Page 52 Ethernet cable connection)

Connector part LED

Display the link status and reception status of the CC-Link IE Field Network board.

Name Status Description

L ER ON • The module received abnormal data.

• The board is performing loopback.

OFF • The module received normal data.

• The board does not perform loopback.

LINK ON Linkup in progress.

OFF Linkdown in progress.

4 PROCEDURE BEFORE OPERATION

4.2 Part Names

4.3 Installation

This section explains precautions for handling and installation environment of the CC-Link IE Field Network board.

Handling precautions

The following explains precautions for handling.

Precautions for turning on

Do not touch any connectors while power is on. Doing so may cause electric shock or malfunction.

Handling precautions of the board

• Do not directly touch any conductive parts and electronic components of the board. Doing so can cause malfunction or

failure of the board.

• Do not disassemble or modify the boards. Doing so may cause failure, malfunction, injury, or a fire.

• Before handling the board, touch a conducting object such as a grounded metal to discharge the static electricity from the

human body. Failure to do so may cause the board to fail or malfunction.

• Handle the board in a place where static electricity will not be generated. Failure to do so may cause a failure or

malfunction.

• The board is included in an antistatic envelope. When storing or transporting it, be sure to put it in the antistatic envelope.

Failure to do so may cause a failure or malfunction.

• Do not drop or apply a strong impact to the board. Doing so may cause a failure or malfunction.

Installation environment

For installation of the personal computer in which the CC-Link IE Field Network board is installed, refer to the manual for the

personal computer.

Precautions for board installation environment

Use the board in an environment that meets the general specifications in this manual. Failure to do so may result in electric

shock, fire, malfunction, or damage to or deterioration of the product.

Precautions for personal computer installation environment

Always ground the personal computer to the protective ground conductor. Failure to do so may cause a malfunction.

4 PROCEDURE BEFORE OPERATION

4.3 Installation

Procedure for replacing mounting brackets

Start

Loosen the screws.

Remove a standard-size mounting bracket.

Adjust a low profile-size mounting bracket to holes

for fixing the mounting bracket of board.

Tighten the screws.

Completion

Standard-size mounting bracket

Screw

Low profile-size mounting bracket

Power OFF the personal computer.

Power OFF

Start

Install the board

Install the board to a slot on a personal computer.

Fix the board to a slot on the personal computer using the board-fixing screws.

Fix the board

Power ON

Power ON the personal computer.

Completion

The following shows the procedure for replacing a standard-size mounting bracket with a low profile-size mounting bracket.

*1 Keep the unused brackets in secure place. *2 Screw tightening torque: 0.425 to 0.575 N⋅m (4.34 to 5.86 kgf⋅cm)

Board installation

The board installation procedure is as follows:

4 PROCEDURE BEFORE OPERATION

4.3 Installation

Precautions for turning on

• Turn off the power for the system in all phases before installing the board to or removing it from the personal computer.

Failure to do so may result in electric shock or cause the board to fail or malfunction.

Precautions for installing the board

• Fix the board by tightening the board-fixing screws within the specified torque range. Undertightening may cause drop,

short circuit, or malfunction. Overtightening may damage the screw and/or board, resulting in drop, short circuit, or

malfunction. For the tightening torque of the board-fixing screws, refer to the manual supplied with the personal computer.

• Before handling the board, touch a conducting object such as a grounded metal to discharge the static electricity from the

human body. Failure to do so may cause the board to fail or malfunction.

• Install the board to a personal computer which is compliant with PCI standard or PCI Express

Operating Environment). Failure to do so may cause a failure or malfunction.

• Securely insert the board into the PCI slot following the board installation instruction of the personal computer. Incorrect

insertion of the board may cause malfunction, failure, or drop of the board.

• When installing the board, take care not to get injured by an implemented component or a surrounding member.

• When installing the board, take care not to contact with other boards.



standard (Page 31

4.4 Setting Channel Numbers

Channel number is set per board, and used to identify the board. 181 is set for the board channel number as a factory default

and the range of 181 to 184 can be set.

Channel numbers being set are used to specify the target boards in setting parameters and performing the MELSEC data link

library function. When using two or more boards in a single personal computer, set channel numbers not to overlap.

Setting method

Set the channel numbers on the "Channel No. Setting" screen in CC IE Field Utility. (Page 112 Setting Board Channel Numbers)

Channel numbers set on the "Channel No. Setting" screen is saved to the CC-Link IE Field Network board.

The channel numbers being set are retained when performing the following operations.

• Rebooting a personal computer

• Board installation position change

• Board replacement to another personal computer

4 PROCEDURE BEFORE OPERATION

4.4 Setting Channel Numbers

4.5 Tests Before Wiring (Standalone Tests of the

Operating procedure

Board)

This section explains the CC-Link IE Field Network board tests before network wiring.

Ethernet cable

Do not connect an Ethernet cable to the CC-Link IE Field Network board in testing a board alone. Doing so

may cause the test to fail.

Bus I/F test

Bus I/F test checks the hardware of the Bus I/F function of the CC-Link IE Field Network board. The following shows a

procedure for performing a test.

1. Select a board to be tested on the "Board Diagnostics"

screen in CC IE Field Utility (Page 117 Diagnosing

Board).

2. Set Mode to "Bus I/F Test" and click the [Start Test]

button.

• Normal completion

• Abnormal completion

3. The result is displayed on "Test Result" field.

If the test completes abnormally, please consult your local

Mitsubishi representative.

Memory test

Memory test checks the hardware of the memory function of the CC-Link IE Field Network board. The following shows a

procedure for performing a test.

1. Select a board to be tested on the "Board Diagnostics"

screen in CC IE Field Utility (Page 117 Diagnosing

Board).

2. Set Mode to "Memory Test" and click the [Start Test]

button.

4 PROCEDURE BEFORE OPERATION

4.5 Tests Before Wiring (Standalone Tests of the Board)

Operating procedure

• Normal completion

• Abnormal completion

3. The result is displayed on "Test Result" field.

If the test completes abnormally, please consult your local

Mitsubishi representative.

Hardware test

Hardware test checks the hardware in the CC-Link IE Field Network board. The following shows a procedure for performing a

test.

1. Select a board to be tested on the "Board Diagnostics"

screen in CC IE Field Utility (Page 117 Diagnosing

Board).

2. Set Mode to "H/W Test" and click the [Start Test] button.

• Normal completion

• Abnormal completion

Operation during hardware test

Do not access the buffer memory in user program during the hardware test. Doing so may cause the test to

fail.

3. The result is displayed on "Test Result" field.

If the test completes abnormally, please consult your local

Mitsubishi representative.

4 PROCEDURE BEFORE OPERATION

4.5 Tests Before Wiring (Standalone Tests of the Board)

Self-loopback test

Operating procedure

Self-loopback test checks the hardware of the CC-Link IE Field Network board alone, including the send/receive circuit of the

transmission system and cables. The following shows a procedure for performing a test.

1. Connect Ethernet cables to the RJ45 connector

(PORT1) and RJ45 connector (PORT2) of the CC-Link

IE Field Network board.

2. Select a board to be tested on the "Board Diagnostics"

screen in CC IE Field Utility (Page 117 Diagnosing

Board).

3. Set Mode to "Self-Loopback Test" and click the [Start

Test] button.

• Normal completion

4. The result is displayed on "Test Result" field.

If the test completes abnormally, replace the Ethernet cable

and execute the test again.

If the test is completed abnormally again, please consult your

local Mitsubishi representative.

• Abnormal completion

When conducting the self-loopback test, use a normal Ethernet cable. (Page 30 Cables)

4 PROCEDURE BEFORE OPERATION

4.5 Tests Before Wiring (Standalone Tests of the Board)

4.6 Wiring

This section explains the cable wiring and precautions. For Ethernet cables and hubs used for the wiring, and network configuration, refer to the system configuration. (Page 20 SYSTEM CONFIGURATION)

Wiring Precautions

The following explains wiring precautions.

Precautions for turning on

• Turn off the power for the system in all phases before installing the board or starting wiring. Failure to do so may result in

electric shock, damage to the product, or malfunction.

• After installation of the board and wiring, attach the cover on the module before turning it on for operation. Failure to do so

may result in electric shock.

Precautions for laying Ethernet cables

• Place the communication cable connected to the board in a duct or clamp them. If not, dangling cables may swing or

inadvertently be pulled, resulting in damage to the board or cables or malfunctions due to poor contact.

• Prevent foreign matter such as dust or wire chips from entering the personal computer. Such foreign matter may cause a

fire, failure, or malfunction.

• Do not install the 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.

• Securely plug the communication cable to the connector of the board. Then, check for any incomplete connection. Poor

contact may cause an erroneous input or output.

• Do not touch the core of the cable-side or board-side connector, and protect it from dirt or dust. If oil from your hand, dirt or

dust is attached to the core, it can increase transmission loss, arising a problem in data link.

• Attach a connector cover to a connector which is not connected to an Ethernet cable to prevent foreign matter such as dirt

or dust.

Precautions for Ethernet cable

• Check the following:

(1) Is any Ethernet cable disconnected?

(2) Does any Ethernet cable short?

(3) Are the connectors securely connected?

• Do not use Ethernet cables with broken latches. Doing so may cause the cable to unplug or malfunction.

• The maximum station-to-station distance is 100m. However, the distance may be shorter depending on the operating

environment of the cable. For details, contact your cable manufacturer.

• The bend radius of the Ethernet cable is limited. For details, see the specifications of the Ethernet cable to be used.

4 PROCEDURE BEFORE OPERATION

4.6 Wiring

Precautions for connecting and disconnecting Ethernet cable

Board-side connector

Personal computer

Proper alignment Misaligned

The connector is not covered with the personal computer.

The connector is not appeared and can not connect the cable.

Patch cord removal tool

Cable-side connector

Latch

Board-side connector

CC-Link IE Field Network board

• Misalignment of the connecting slot of the personal computer may lead to a slight installation error. When the board-side

connector is covered with the personal computer, Ethernet cable cannot be connected properly. Check the board

installation status not to overlap the connector and the personal computer.

• When disconnecting the cable from the board, do not pull the cable by the cable part. Pulling the cable connected to the

board may result in malfunction or damage to the board or cable.

• Depending on the adjacent boards and installing slot position, disconnecting the Ethernet cable may be difficult. In this

case, use the following dedicated tool.

Product name Model name Maker

Patch cord removal tool PCRT1 Panduit Corp.

4 PROCEDURE BEFORE OPERATION

4.6 Wiring

Ethernet cable connection

LINK LED

Explains the Ethernet cable connection.

Connecting the cable

1. Turn off a personal computer on which the CC-Link IE

Field Network board is installed, and the connected

device.

2. Push the Ethernet cable connector into the CC-Link IE

Field Network board and connected device until it clicks.

Pay attention to the connector's direction.

3. Turn on the personal computer.

4. Turn on the connected device.

5. Check whether the LINK LED of the CC-Link IE Field

Network board connected with an Ethernet cable is ON.

The time between the power-ON and the LINK LED

turning ON may vary. The LINK LED usually turns ON in

a few seconds. Note, however, that the time may be

extended further if the linkup process is repeated

depending on the status of the device on the line. If the

LINK LED does not turn ON, refer to the troubleshooting section and take a corrective action. (Page 141

TROUBLESHOOTING)

4 PROCEDURE BEFORE OPERATION

4.6 Wiring

PORT1 and PORT2 connectors need not to be distinguished.

Either one can be used.

LINK

L ER

LINK

L ER

LINK

L ER

LINK

L ER

LINK

L ER

LINK

L ER

LINK

L ER

LINK

L ER

QJ71GF11-T2 QJ71GF11-T2

Connection between PORT1s or PORT2s

Connection between

PORT1 and PORT2

• When only one connector is used in star topology, either PORT1 or PORT2 connector can be used.

• When using two connectors for line topology and ring topology, an Ethernet cable can be connected to the

connectors in any combination. For example, the cable can be connected between PORT1s and between

PORT1 and PORT2.

Disconnecting the cable

1. Power OFF the system.

2. Press the latch down and unplug the Ethernet cable.

4 PROCEDURE BEFORE OPERATION

4.6 Wiring

4.7 Tests After Wiring

Operating procedure

This section describes loop and cable tests that should be performed after network wiring.

Perform these tests to the actual operating network configuration.

Loop test

The loop test checks the network cable connection status and line status from master station and the parameter setting status

of each station. Confirm whether the network is operating correctly by performing loop test before data link.

The test allows checking the following items.

Item Description

Master station duplication check Check if master stations on the network are duplicated.

Station number duplication check Check if stations on the network are duplicated.

Out-of-range station No. check Check if slave stations exceeding the number of slave stations set for the master station are connected.

Reserved station specification check Check if specified reserved stations are actually connected.

Consistency check of the number of connected stations

Station type check Consistency check for the station type of slave stations set in master stations and actual connected station

Loopback check Detect if loopback is being performed while "Use" is set for "Loopback Function Setting" in the Network

Executing loop tests

The following explains a procedure for loop test, assuming the executing station (master station) is the CC-Link IE Field

Network board and the target station (local station) as the CC-Link IE Field Network module.

Consistency check for the number of total slave stations set by parameters and actual connected slave stations.

type.

Parameter of the master station.

The loop test can be executed only when the CC-Link IE Field Network board is the master station.

When it is the local station, execute the test from the master station in the network system to which the local

station is connected.

■Preparing loop tests

Prepare the following before loop test.

1. Check for the power discontinuity

Turn OFF the personal computer.

Turn OFF the module.

2. Cable connection

Connect Ethernet cables to each station.

3. Turn-ON

Turn ON the personal computer.

Turn ON the module.

■Executing loop tests

The executing station (master station) performs a loop test.

4 PROCEDURE BEFORE OPERATION

4.7 Tests After Wiring

1. Select a board to be tested on the "Board Diagnostics"

screen in CC IE Field Utility (Page 117 Diagnosing

Board).

Operating procedure

2. Set Mode to "Loop Test" and click the [Start Test] button.

• Normal completion

• Abnormal completion

• During the loop test, data link stops on all stations.

• When a faulty station cannot be displayed on the "CC IE Field Diagnostics" screen

3. The result is displayed on "Test Result" field.

If the test completes abnormally, check the error cause on

the "CC IE Field Diagnostics" screen, process the error. (Page 118 Diagnosing CC-Link IE Field Network)

The following errors may have occurred.

Master station duplication

Station number duplication

Slave station type error

When the faulty station is a module, identify the error causes on the System Monitor screen in GX Works2.

When the faulty station is a board, identify the error causes on the "Board Diagnostics" screen. (Page 117 Diagnosing Board)

Cable test

Cable test checks if the Ethernet cables are properly connected.

Only an Ethernet cable connected to the PORT1 or PORT2 of the target station is tested. For the whole network status, check the loop test. (Page 54 Loop test)

1. Start Utility on the computer where CC-Link IE Field

Network board is installed.

2. The "Cable test" screen is displayed.

[Diagnostics]  [CC IE Field Diagnostics]  [Cable

Test] button

3. Enter a station number to conduct a cable test and click

the [Execute Test] button so that the test can be

operated. When an error occurs, take actions according

to the error message.

4 PROCEDURE BEFORE OPERATION

4.7 Tests After Wiring

Communication test

Operating procedure

CC-Link IE

Field Network

CC-Link IE

Field Network

CC-Link IE

Field Network

Network No.1

Network No.2

Network No.3

Station

No.2

Station

No.0

Station

No.0

Station

No.0

Station

No.1

Station

No.1

Station

No.2

Station

No.2

Station

No.3

Station

No.4

Own station

(request source)

Communication

target

(Relay station 1)

(Relay station 2)

Station

No.3

Routing parameters for stations of network No.1

Routing parameters for stations of network No.2

Routing parameters for stations of network No.3

No setting is required for station No.3 because data are transmitted via the station itself.

No setting is required for station No.0 because data are transmitted via the station itself.

No setting is required for station No.2 because data are transmitted via the station itself.

No setting is required for station No.3 because data are transmitted via the station itself.

Communication test checks if transient transmission data can be properly routed from the own station to the communication

target.

Take the following system configuration as an example of communication test procedure.

4 PROCEDURE BEFORE OPERATION

4.7 Tests After Wiring

1. Start Utility on the computer where CC-Link IE Field

Network board is installed.

2. Set the routing parameters on the "Routing Parameter

Setting" screen as shown in the figure to left.

(Page 108 Routing parameters)

3. Write the network parameters being set to the CC-Link

IE Field Network board.

[Online]  [Write to Board]

4. Reset the board.

[Online]  [Reset operation]

5. Open the "Communication Test" screen and set data to

"Communication Destination Setting" and

"Communication Data Setting".

[Diagnostics]  [CC IE Field Diagnostics] 

[Communication Test] button

6. Click the [Execute Test] button to perform the

Network No.1

Network No.2

Station

No.0

Station

No.0

Station

No.1

Station

No.2

Sending (relay) station

Receiving

(relay) station

Own station

(request source)

communication test. If an error occurs, take actions

according to the error message.

When conducting the test on relay stations, set the receiving (relay) station in "Communication Destination

Setting". Setting the sending (relay) station will cause an error.

4 PROCEDURE BEFORE OPERATION

4.7 Tests After Wiring

5 FUNCTIONS

This chapter explains the functions of the CC-Link IE Field Network board.

5.1 Function List

The following table explains the function list of the CC-Link IE Field Network board.

Cyclic transmission

Function Description Reference

Communication with other stations

Link refresh Transfer between the link device of the CC-Link IE Field Network board and

Mode selection for cyclic transmission This mode is selected for optimizing the performance of cyclic transmission

Link scan mode setting Constant link scan setting can be selected to execute the link scan at a

Assurance of cyclic data integrity The cyclic data integrity is assured in units of 32 bits or station-based units. • Page 64 Assurance of

Input status setting for data link faulty station Select whether the input data from another station where the data link error

Cyclic transmission stop and restart During debugging and other operations, cyclic transmission is stopped (Data

Communication by RX and RYI/O data in bit units is communicated between the own station and other

stations.

Communication by RWw and RWr

I/O data in word units is communicated between the own station and other stations.

the device of the driver is performed automatically.

based on the cyclic transmission and transient transmission frequency. The mode can be selected from "Online (Normal mode)" and "Online (Highspeed mode)".

constant time interval.

occurred is cleared or held.

reception from the slave station and data transmission from own stations are stopped). Also, the stopped cyclic transmission is restarted. Transient transmission is not stopped.

• Page 60 Cyclic Transmission

• Page 101 Network configuration setting

• Page 63 Link scan and link refresh

• Page 106 Driver setting

• Page 100 Network type and mode

• Page 218 Differences in Cyclic Transmission Modes

Page 102 Supplementary setting

cyclic data integrity

• Page 102 Supplementary setting

• Page 66 Input status of data link faulty station setting

• Page 104 Network operation setting

• Page 67 Cyclic transmission stop and restart

• Page 131 Link start/stop

Transient transmission

Function Description Reference

Communication by MELSEC data link library function

Seamless transmission with different networks Setting the routing parameters beforehand also enables transient

5 FUNCTIONS

5.1 Function List

Communicate with other station's programmable controller by MELSEC data link library function.

• Device reading and writing of other station's programmable controller

• Remote operation to other station's programmable controller

• Data reading and writing of an intelligent device station

transmission to stations in different networks. Communication is also possible with the CC-Link IE Controller Network, and MELSECNET/H.

• Page 68 Communication on the same network

• Page 70 SEND/RECV Function

• Page 137 MELSEC DATA LINK LIBRARY

• Page 69 Communication with different networks

• Page 108 Routing parameters

RAS function

Function Description Reference

Slave station disconnection Only the stations where an error has occurred, including slave stations, are

disconnected from the network, and the data link is continued only with the stations operating normally. In a line topology system, stations after the station where the error occurred are disconnected.

Automatic return When a station disconnected from a network due to a data link error recovers

from the error, the station is automatically reconnected to the network and restarts data link.

Loopback function This function disconnects only faulty stations, and continues data link with only

normal stations. It also continues data link with normal stations connected after the faulty station which is disconnected in a line topology.



Page 78 Loopback Function

Diagnostic function

Function Description Reference

CC-Link IE Field Network diagnostics The status of the CC-Link IE Field Network can be checked by CC IE Field

Individual board diagnostics

Own network diagnostics

Other network diagnostics

Bus I/F test Check the hardware related to the bus I/F function of the CC-Link IE Field

Memory test Check the memory of the CC-Link IE Field Network board. Page 47 Memory test

Hardware test Check the hardware in the CC-Link IE Field Network board. Page 48 Hardware test

Self-loopback test Check the communication circuit of the transmission system of the CC-Link IE

Loop test Check the network circuit status and parameter setting status of each station. Page 54 Loop test

Cable test Check the connection status of the Ethernet cable. Page 55 Cable test

Communication test Check whether the communication path for transient transmission from the

Utility. The faulty area, cause of the fault and its corrective action, and event history can be checked.

Network board.

Field Network board.

own station to the target station is correct.

Page 118 Diagnosing CCLink IE Field Network

Page 47 Bus I/F test

Page 49 Self-loopback test

Page 56 Communication test

Other functions

Function Description Reference

Reserved station specification The reserved stations are included in the number of stations that will be

Reserved station function disable Reserved stations can be temporarily disabled without changing parameters.

Error invalid station and temporary error invalid station setting

Event notification to program Event conditions are checked every link scan, and if the event conditions are

Driver WDT function This function monitors the operation of the software (operating system, driver)

Parameter setting function for CC-Link IE Field Network remote device station

connected to the network in the future without actually connecting them. Reserved stations are not detected as faulty stations even though they are not actually connected.

The master station does not detect a slave station as a faulty station even if the slave station is disconnected during data link. This can be used when a slave station is replaced during data link, for instance.

met, notifies events to the user program.

inside the hardware.

The parameters of CC-Link IE Field Network remote device station can be set by using mdRemBufWriteEx function or mdRemBufReadEx function of MELSEC data link library.

• Page 75 Reserved Station Specification and Reserved Station Function Disable Function

• Page 101 Network configuration setting

• Page 134 Reserved station function enable

• Page 76 Error Invalid Station and Temporary Error Invalid Station Setting Function

• Page 101 Network configuration setting

• Page 135 Enable/ Disable ignore station errors

• Page 77 Event Function

• Page 104 Event setting

Page 79 Driver WDT function

MELSEC Data Link Library Reference Manual

5 FUNCTIONS

5.1 Function List

5.2 Cyclic Transmission

RX,RWr

RY,RWw

RX,RWr

RY,RWw

RX,RWr

RY,RWw

Õ

Personal computer Station No. 0

Station No. 1

Station No. 2

User

program

Driver

MD function

Link refresh

Master

station

(Board)

Station

No. 1

Station

No. 2

Station

No. 1

Station

No. 2

Link scan

Slave station

Station No. 1

Station No. 2

Station No. 1

Station No. 2

External device

Area for sending to other stations

This function performs periodical data communication across same network stations during cyclic transmission. For data

communication, link devices (RX, RY, RWw, and RWr) are used.

Data flow and link device assignment

Master and slave stations (except for local stations)

One-to-one communication is possible between the master and slave stations.

The status information of the link devices (RY, RWw) of the master station is output to the external device of the slave station,

and the input status information from the external device of the slave station is stored in the link devices (RX, RWr) of the

master station.

• Output from the master station

 The status data of the user program are stored in the driver by MD function.  The status data of the driver are stored in the link devices (RY, RWw) of the master station (board) by link refresh.  The status data of the link devices (RY and RWw) of the master station are stored in the link devices (RY, RWw) of each slave station by link scan.  The status data of the link devices (RY, RWw) of the slave station are output to the external device.

• Input from the slave station

 The status data of the external device are stored in the link devices (RX, RWr) of the slave station.  The status data of the link devices (RX, RWr) of the slave station are stored in the link devices (RX, RWr) of the master station by link scan.  The status data of the link devices (RX, RWr) of the master station (board) are stored in the driver by link refresh.  The status data of the driver are stored in the user program by MD function.

5 FUNCTIONS

5.2 Cyclic Transmission

Master and local stations

RX,RWr

RY,RWw RY,RWw

RY,RWw

Ô ×

Õ

Local station

Area for sending to other stations

Personal computer

Station No. 0

Station No. 1

Station No. 2

Personal computer

User

program

Driver

MD function

Link refresh

Link scan

Link refresh

Master station

(Board)

User

program

Station

No. 1

Station

No. 2

Station

No. 1

Station

No. 2

Station

No. 1

Station

No. 2

Station

No. 1

Station

No. 2

Local station

(Board)

Station

No. 2

Station

No. 1

Send range

from station

No. 1

Send range from station

No. 2

Data can be written into the send range of each station's link device (RY, RWw) and can be sent to any station on the same

network.

The status data of the link devices (RY, RWw) of the master station are stored in the link devices (RX, RWr) of each local

station.

The status data of the link devices (RY, RWw) of local stations are stored in the link devices (RX, RWr) of the master station

and the link devices (RY, RWw) of other local stations.

• Output from the master station

 The status data of the user program are stored in the driver by MD function.  The status data of the driver are stored in the link devices (RY and RWw) of the master station (board) by link refresh.  The status data of the link device (RY, RWw) of the master station is stored in the link device (RY, RWw) of the local station by link scan.  The status data of the link device (RX, RWr) of the local station (board) is stored in the driver

• Input from the local station

 The status data of the driver is stored in the own station send range of the link device (RY, RWw) of the local station (board) by link refresh.  The status data of the link devices (RY, RWw) of the local station are stored in the link devices (RX, RWr) of the master station by link scan.  The status data of the link devices (RX, RWr) of the master station (board) are stored in the driver by link refresh.  The status data of the driver are stored in the user program by MD function.

5 FUNCTIONS

5.2 Cyclic Transmission

Coexistence of local stations and the other slave stations (other than local stations)

RX,RWr

RY,RWw

RX,RWr

RY,RWw

Send range from station

No. 2

Station No. 0

Station No. 1

Station No. 2

Station No. 3

Personal computer

User

program

Driver

MD function

Link refresh

Master station

(Board)

Station

No. 1

Station

No. 2

Station

No. 3

Send range

to station

No.1

Send range

to station

No.2

Send range

to station

No. 3

Slave station Slave station Local station

Send range from station

No. 1

Send range from station

No. 3

Station

No. 1

Station

No. 2

Station

No. 1

Station

No. 2

Station

No. 3

Station

No. 1

Station

No. 2

Area for sending to other stations

The data of all slave stations are also stored in the local stations in the same way as the master station.

Setting method

The link devices can be assigned in "Network Configuration Setting". (Page 101 Network configuration setting)

5 FUNCTIONS

5.2 Cyclic Transmission

Link scan and link refresh

Link refresh time

Link scan

(Setting time) (Setting time)

(Setting time)

Link refresh

Link scan is executed 'asynchronously' with the link refresh which is executed by the CC-Link IE Field Network board driver.

Setting method

Link refresh is executed at the interval of time set for "Link refresh cycle" on the "Driver setting" screen of CC IE Field Utility. (Page 106 Driver setting)

Link refresh time

Link refresh time can be checked on the "Board Diagnostics" screen. (Page 117 Diagnosing Board)

The link refresh may not be executed in the set cycle because of such factors described below.

• Performance of the personal computer CPU

• Number of set refresh points

• Number of installed CC-Link IE Field Network boards

• Other running applications

• Other running boards

• If the link refresh time exceeds the link refresh cycle set on the "Device setting" screen, extend the link

refresh cycle. (Page 106 Driver setting)

• If the shortened link refresh time effects the operation of the applications, extend the link refresh cycle.

(Page 106 Driver setting)

5 FUNCTIONS

5.2 Cyclic Transmission

Assurance of cyclic data integrity

Clear the check box.

The cyclic data integrity can be assured in 32-bit units or for each station.

32-bit data assurance

The RWw and RWr data can be assured in 32-bit units.

■Setting method

Disable "Block Data Assurance per Station" on the "Supplementary Setting" screen in "Network Configuration Setting". (Page 102 Supplementary setting)

To enable 32-bit data assurance, disable "Block Data Assurance per Station".

■Access to cyclic data

When accessing link refresh target devices, the integrity of the 32-bit data can be assured by accessing RWw and RWr with

the following conditions satisfied.

• Start device number of RWw/RWr is a multiple of 2.

• The number of points assigned to RWw/RWr is a multiple of 2.

For data assurance of more than 32 bits, use the block data assurance per station or interlock programs.

5 FUNCTIONS

5.2 Cyclic Transmission

Block data assurance per station

Select the check box.

CC-Link IE Field Network Board

Driver Link device

Data assurance

Station

No. 1

Station

No. 2

Station

No. 3

Station

No. 4

Station

No. 1

Station

No. 2

Station

No. 3

Station

No. 4

Link refresh

Data assurance

Integrity of the cyclic data is assured for each station by handshaking between the driver and the CC-Link IE Field Network

board by a link refresh.

■Setting method

Enable "Block Data Assurance per Station" on the "Supplementary Setting" in "Network Configuration Setting". (Page 102

Supplementary setting)

Once this setting is enabled on the master station, integrity of the data for all stations is assured for each station.

■Access to link devices

During a link refresh, data are assured for each station as shown below.

5 FUNCTIONS

5.2 Cyclic Transmission

Input status of data link faulty station setting

RX RX

RY RY

RWw

RWr

RWw

RX RX

RWr RWr

RWw RWw

Area for which "Clear" or "Hold" can be selected in the data link faulty station input status setting

Area where data are held regardless of the setting

Area that is dependent on the setting of the intelligent device station

Station No.0 Station No.1 Station No.2 Station No.3

Station

No.1

Station

No.1

Station

No.1

Station

No.1

Station

No.1

Master station

(Board)

Intelligent

device station

Local station

Station

No.1

Station

No.1

Station

No.1

Station

No.1

Station

No.1

Station

No.2

Station

No.2

Station

No.2

Station

No.3

Station

No.2

Station

No.3

Station

No.2

Station

No.3

Station

No.2

Station

No.3

Station

No.3

Station

No.3

Station

No.1

Station

No.2

Station

No.3

Station

No.1

Station

No.2

Station

No.3

Station

No.1

Station

No.2

Station

No.3

Station

No.1

Station

No.2

Station

No.3

Station

No.1

Station

No.2

Station

No.3

Station

No.1

Station

No.2

Station

No.3

Input data from the data link faulty station can be either cleared or held with the CC-Link IE Field Network board.

Input data Range where the settings are enabled Input status in case of failure

RX and RY • Master station RX

• Local station RX and RY (only the input data from other stations)

RWw and RWr • Master station RWr

• Local station RWw and RWr (only the input data from other stations)

Clearing or holding the input data can be selected.

The input data are held regardless of any setting.

Setting method

Input status of data link faulty station can be set in the "Network Operation Setting". (Page 104 Network operation setting)

5 FUNCTIONS

5.2 Cyclic Transmission

Cyclic transmission stop and restart

RX,RWr

RY,RWw

Personal computer

User

program

Driver

Link refresh

Station No.0

Station No.1

Station No.2

Station No.3

Slave station

Station No.1

Station No.2

Station No.3

Station

No.1

Station

No.2

Station

No.3

Station

No.1

Station

No.2

Station

No.3

Cyclic transmission

stopped

Master station

(Board)

During debugging and other operations, cyclic transmission can be stopped (Data reception from the slave stations and data

transmission from the own station can be stopped). The stopped cyclic transmission can be restarted. Transient transmission

is not stopped.

• The link start/stop is not available in loop test mode.

• Cyclic transmission can be started and stopped with link special relay (SB) and link special register (SW).

(Page 188 Link Special Relay (SB) List, Page 199 Link Special Register (SW) List)

Setting method

Cyclic transmission stop and restart are operated on the "Link Start/Stop" screen. (Page 131 Link start/stop)

When the board is reset or the system is powered OFF and then ON

Even if cyclic transmission was stopped by link stop, it will be restarted by resetting the board or powering OFF and then ON

the system.

Stations to which the link start cannot be executed

The link start cannot be executed to the following stations.

• Station where cyclic transmission was stopped due to an error

• Station where link was stopped by a command from another station

• Station where link was stopped by link special relay (SB) or link special register (SW)

*1 Selecting "Forced Link Start" will start the link.

5.2 Cyclic Transmission

5 FUNCTIONS

5.3 Transient Transmission

This function allows communication with other stations, using the MELSEC data link library function. Communication is also

possible with different networks.

Communication on the same network

Using MELSEC data link library, the programmable controllers of other stations and the buffer memory of the intelligent function module installed with the head module can be accessed. (Page 137 MELSEC DATA LINK LIBRARY)

Setting method

Use the MELSEC data link library function. MELSEC Data Link Library Reference Manual

Transient transmission range

It is possible to communicate with all stations on the network.

5 FUNCTIONS

5.3 Transient Transmission

Communication with different networks

Set the communication route by routing parameters in advance.

CC-Link IE Controller Network

Network No.1

(Relay station)

Network No.2

CC-Link IE Field Network

(Relay station 1) (Relay station 2) (Relay station 3)

CPU

module

CPU

module

CPU

module

(Relay station 4)

Network No.1

(Relay station 5)

(Relay station 6)

(Relay station 7)

(Relay station 8)

Network No.2 Network No.3

Network No.4

Network No.5

Network No.6

Network No.7

Network No.8Network No.9

Board

CC-Link

IE Field Network

Own

station

CPU

module

CPU

module

CPU

module

CPU

module

CPU

module

CPU

module

CPU

module

CPU

module

CPU

module

CPU

module

CPU

module

CPU

module

CPU

module

Setting the routing parameters in utility beforehand enables transient transmission to stations on different networks. Seamless

communication is also possible with the CC-Link IE Controller Network, MELSECNET/H.

Setting method

For Routing parameters, set on the "Routing Information Setting" (Page 108 Routing parameters)

Transient transmission range

For Multiple network system, communication with a station on up to the eighth network is possible by setting routing

parameters.

5 FUNCTIONS

5.3 Transient Transmission

5.4 SEND/RECV Function

SEND

RECV

Channel 1: For send

Channel 2: For send

Channel 1

Channel 2

Channel 1

Station No.0

(Own station)

Station No.1

(Other station)

Station No.2

(Other station)

SEND

RECV

Channel 1: For send

Channel 2: For receive

Channel 1

Channel 2

Channel 1

Channel 2

Channel 1: For receive

Channel 2: For send

Station No.0

(Own station)

Station No.1

(Other station)

The SEND/RECV function sends/receives data to/from other station's programmable controller using the MELSEC data link library function. (Page 137 MELSEC DATA LINK LIBRARY)

Availability by the SW1DNC-CCIEF-B version

For CC-Link IE Field Network board with a serial number whose first five digits are '15102' or higher, install SW1DNC-CCIEF-

B version 1.04E or later. When using SW1DNC-CCIEF-B version 1.03D or earlier, one of the following error occurs in the

SEND/RECV function and the function cannot be used.

• SEND function: Board driver I/F error :103 (0067H)

• RECV function: Timeout error :2 (0002H)

For an error occurred, refer to the following manual.

MELSEC Data Link Library Reference Manual : Applicable, : Not applicable:

Serial number Version of SW1DNC-CCIEF-B

1.03D or earlier 1.04E or later

'14052' or lower 

15102 or higher 

Channel (use for dedicated instruction)

A channel is an area of a CC-Link IE Field Network board where data handled by a SEND/RECV function is stored. By using

multiple channels, it is possible to simultaneously access from the own station to other stations or concurrently read from and

write to the same board.

■Number of channels

The CC-Link IE Field Network board has 2 channels that can be used for SEND/RECV function. By using 2 channels

simultaneously, the sending and receiving of two data can be executed at the same time.

■Precautions

When executing the sending and receiving of multiple data simultaneously by SEND/RECV function, make sure that the

channels for the instructions are not duplicated. The sending and receiving for which the same channel is specified cannot be

executed simultaneously. To use the same channel for multiple sending and receiving, execute one after completion of

another.

■Example

• When accessing from the own station to multiple other stations simultaneously

Change the channel used for the own station for each target station.

• When accessing mutually between the own station and another station

Change the channel used for the own station for each sending and receiving of data.

5 FUNCTIONS

5.4 SEND/RECV Function

SEND function

main() {

mdOpen( 181, -1, &path );

mdSendEx( path, 1, 1, , );

mdClose( path ); }

RECV

[Target station][Own station]

User application Board

Target station

CPU module

SEND

function

Channel 1

Channel 2

main() {

mdOpen( 181, -1, &path ); mdSendEx( path, 1, 1, , ); mdSendEx( path, 1, 1, , );

mdClose( path ); }

RECV

[Own station] [Target station]

User application Board Target station CPU module

Error

Channel 1 Channel 1

Channel 2 Channel 2

(Own station)

Station

No.0

Station

No.1

Station

No.1

Station

No.5

Station

No.3

Station

No.2

Network No.1

Network No.2

Specify station No.1 as the target station. Station No.5 cannot be specified.

(Target station)

The SEND function sends data from the own station to the specified channel of the specified station using the mdSend/

mdSendEx function of MELSEC data link library function.

• Sending data to the same channel of the target station

Send the data after the target station has been read the specified channel data.

An error will be occurred if sending the data to the same channel of the target station before reading the

specified channel data.

• When the multiple network modules are mounted on the target station

Specify the station number and network number of the network module which is received the request from

the own station.

The following example specifies the station number 1 of the network number 1. (The station number 5 of the

network number 2 cannot be specified.)

5 FUNCTIONS

5.4 SEND/RECV Function

■Execution type

Request source Target station

Completed

Request source Target station

Completed

Relay station

Request source Target station

Completed

Relay station

Target station

Completed

main() {

mdOpen( 181, -1, &path );

mdReceiveEx( path, 0, 255, , );

mdClose( path ); }

SEND

[Send source]

[Own station]

CPU module Target station Board User application

Channel 1

Channel 2 Channel 2

Channel 1

RECV

function

Two execution types, "with arrival confirmation" and "without arrival confirmation", are available for the SEND function. When

sending data with "without arrival confirmation" execution type, "All stations" and "Group numbers" can be specified as target

stations besides the station number.

• Without arrival confirmation (When the target station is on the same network)

The process is completed when data is sent from the own station.

• Without arrival confirmation (When the target station is on another network)

The process is completed when data arrives at the relay station on the same network.

• With arrival confirmation

The process is completed when data is stored in the specified channel of target station.

When "Without arrival confirmation" is specified, the result is regarded as normal on the own station even if

the sending to the target station fails as follows.

• When communication ends normally even though sent data are abnormal

• When data cannot be stored in the target station, because data is sent to the same station from multiple

stations

RECV function

The RECV function reads data received by the board from the other station using the mdReceive/mdReceiveEx function of

MELSEC data link library function.

5 FUNCTIONS

5.4 SEND/RECV Function

■Reception buffer of RECV function

main() {

mdOpen( 181, -1, &path );

mdReceiveEx( path, 0, 255, , );

mdClose( path ); }

SEND

Reception buffer

of channel 1

Reception buffer

of channel 2

First data

Second data

127th data

128th data

First data

Second data

127th data 128th data

[Send source]

[Own station]

CPU module Target station Board Driver User application

Channel 1

Channel 2

Channel 1

Channel 2

RECV

instruction

RECV

function

Reception buffer of RECV function is a function in which a driver executes the RECV instruction automatically and received

data are stored to reception buffers of each channel number in the driver. Set the Reception buffer of RECV function in the "driver setting" of the network parameter. (Page 106 Driver setting)

• "Without setting"

When the reception buffer is not set, the operation is the same as the RECV function of link dedicated instruction for CPU.

This setting is used for detecting errors in sent data, whose execution type of the SEND function is set to "with arrival

confirmation", at sending side.

• "With setting"

When the reception buffer is set, the operation is the same as the RECV function for MELSECNET/H board or CC-Link IE

Controller Network board.

This setting is used for receiving data from multiple stations such as data sampling.

 Messages received from other stations are stored to a storage channel of the target station specified in the send source.  A driver executes the RECV instruction automatically and stores received messages to reception buffers of each channel number from the storage

channel of the target station. A maximum of 128 reception data are stored to each reception buffer of each channel number in the driver. When received data exceeds 128, the driver discards the received data automatically.

 Using the mdReceiveEx/mdReceive function, data of the specified channel number are read from the reception buffer in the order they were received.

When the reception buffer is set, an error may occur under the following condition.

Condition Description Corrective action

Data are read immediately after the send data completion at the sending station.

Data are sent consecutively from the sending station.

Normally completed data at the sending side are discarded.

When attempting data read by executing the mdReceive/mdReceiveEx function immediately after the send data completion at the sending station, "No reception data error" occurs because data have not yet been stored to the reception buffer of the driver.

When attempting data send consecutively, "Channel busy (dedicated instruction) error" occurs at the sending station because the channel is being used by the driver and thus the sent data cannot be received.

When 128 received data are stored to the reception buffer of each channel number, the 129th and the following received data are discarded automatically by the driver after they are received by the board and before they are stored to the reception buffer. When the data, whose execution type is set to "with arrival confirmation", are sent from the sending side, a normal completion is established at the sending side because the board receives data once, however, data are discarded.

• Retry it after a little while.

• Change the storage channel of the target station.

• Retry it after a little while.

5 FUNCTIONS

5.4 SEND/RECV Function

■Event notification

mdWaitBdEvent( path, eventno, ); mdReceiveEx( path, 0, 255, , );

SEND

[Send source] [Own station]

CPU module Target station Board User application

Channel 1

Channel 2

Channel 1

Channel 2

Event

notification

RECV

function

The event notification can be set to receive in the user program when receiving data. The event notification is set in the event setting of the network parameter. (Page 104 Event setting)

Received data can be obtained as events in a user program by specifying event numbers set in the event setting using the

mdWaitBdEvent function. (The received data are read by executing the mdReceiveEx/mdReceive function after the return of

the mdWaitBdEvent function.)

 Messages received from other stations are stored to a storage channel of the target station specified in the send source.  Specified events are notified and the mdWaitBdEvent function completes normally.

At this time, the received channel number is stored to the detailed event information of the mdWaitBdEvent function.  Data of channel number notified by the mdWaitBdEvent function are read from the reception buffer using the mdReceiveEx/mdReceive function.

When setting the event notification function, set "Without setting" for Reception buffer of RECV function.

■Operational change according to the setting of the RECV function

• RECV execution request flag When receiving data from another station, the RECV execution request flag status of link special relay (Page 188 Link

Special Relay (SB) List) is set as follows according to each setting.

Reception buffer of RECV function

With setting (Event setting is not applicable.) No change

Without setting With event setting

• When data are not received at the execution of mdReceiveEx/mdReceive function

The action when data are not received at the execution of mdReceiveEx/mdReceive function is set as follows according to

each setting.

Reception buffer of RECV function

With setting (Event setting is not applicable.) The function ends with an error.

Without setting With event setting

Event setting of channel that received data

Without event setting Flag turns ON

Event setting of channel that received data

Without event setting The function waits for up to the time specified for "Transient

RECV execution request flag when data from another station are received (SB0030, SB0031)

Operation status of mdReceiveEx/mdReceive function

(No reception data error)

timeout monitoring time". (Page 106 Driver setting) When data are received: The function ends normally. When data are not received: The function ends with an error. (Response timer timeout (dedicated instruction))

5 FUNCTIONS

5.4 SEND/RECV Function

5.5 Reserved Station Specification and Reserved

(Not actually connected.)

Master station (Station No.0)

Slave station

(Station No.1)

Slave station

(Station No.2)

Slave station

(Station No.3)

Network Configuration Setting

Select "Reserved Station".

Reserved station

Station Function Disable Function

Reserved station specification allows setting of a station that is not actually connected at present but will be connected to the

network in the future (must be included in the total number of stations for the network). Reserved stations are not detected as

error stations even though they are not actually connected.

When the reserved station function is disabled, a slave station specified as a reserved station can be canceled temporarily.

Reserved station specification

A slave station can be specified as a reserved station in the "Network Configuration Setting". (Page 101 Network

configuration setting)

Reserved station function disable and cancel

This is used when connecting a reserved-status slave station to the network. Reserved station function disable and cancel is set on "Reserved Station Function Enable" screen. (Page 134 Reserved

station function enable)

5 FUNCTIONS

5.5 Reserved Station Specification and Reserved Station Function Disable Function

5.6 Error Invalid Station and Temporary Error Invalid

Master station

(Station No.0)

Slave station

(Station No.1)

Slave station

(Station No.2)

Slave station

(Station No.3)

Network Configuration Setting

Select "Invalid Station".

Error invalid station

No data link error will be detected on this station even in the case of an error or power OFF.

Station Setting Function

When a slave station is set as an error invalid station, even if it is disconnected from the network during data link, the master

station will not detect it as error station.

Furthermore, by the temporary error invalid station setting function, a slave station can be temporarily set as an error invalid

station.

Error invalid station setting

A slave station can be set as an error invalid station in "Network Configuration Setting".(Page 101 Network configuration

setting)

Temporary error invalid station

This function is useful for various operations such as replacing a slave station during a data link by temporarily setting it as an

error invalid station.

For setting temporary error invalid station, refer to the following section. Page 135 Enable/Disable ignore station errors

5 FUNCTIONS

5.6 Error Invalid Station and Temporary Error Invalid Station Setting Function

5.7 Event Function

main(){ mdOpen(181, -1, &path); mdWaitBdEvent(path, eventno, …);

mdClose(path); }

Personal computer Board

Event notification

Setting of event condition

User program

Receive the event notification using the mdWaitBdEvent function.

Conditions

met

Event condition check

Link device (RX/RY/RWw/RWr) change

Network status (SB/SW) change

Data reception status of specified channel (RECV)

Data

reception

Channel 1 Channel 2

This function checks event conditions every link scan, and notifies events to the user program when the event conditions are

met.

By using the event function, the link devices can be monitored efficiently without reading link devices regularly by the user

program.

 Set the event condition.  Link devices set for the event condition are checked every link scan.  When the event conditions are met, an event notification is issued every link refresh cycle.

Page 106 Driver setting  Receive the event notification using the mdWaitBdEvent function in the user program.

Setting method

Event conditions are set on the "Event setting" screen. (Page 104 Event setting)

Specify event numbers set by the mdWaitBdEvent function of MELSEC data link library.

5 FUNCTIONS

5.7 Event Function

5.8 Loopback Function

Ring topology

Line topology

Error

If an error occurs, the system will loopback data, continuing data link.

Stations after the error station are disconnected.

Select the check box.

The loopback disconnects the station in which an error has occurred from the network and continues data link with the

stations that are operating normally. Stations connected after the faulty station can also continue data link.

Setting method

Configure the network in ring topology and set "Use" for "Loopback Function Setting" on the "Supplementary Setting" screen in "Network Configuration Setting". (Page 102 Supplementary setting)

Precautions

For network topology other than ring topology, clear the check box.

If the loopback function setting and the network configuration are inconsistent, an error may occur in all stations and data link

cannot be performed.

Whether loopback is being performed or not can be checked by link special relay (SB) and link special register (SW) for the master station. (Page 188 Link Special Relay (SB) List, Page 199 Link Special Register (SW)

List)

5 FUNCTIONS

5.8 Loopback Function

5.9 Driver WDT function

The driver WDT function monitors the operation of the software (operating system, driver) using the timer function on CC-Link

IE Field Network board.

When the driver cannot reset the timer of the board within the specified driver WDT monitoring time, CC-Link IE Field Network

board detects driver WDT error. Driver WDT function detects driver operation delay due to the access error from the driver to

CC-Link IE Field Network board or system high load.

Driver WDT settings

For the setting methods, refer to the following section. Page 106 Driver setting

The driver WDT function is set to invalid as a default.

When the driver WDT error has occurred

The following shows the operation when driver WDT error has occurred.

• CC-Link IE Field Network board and the driver stop communication and are disconnected from the network in order to

avoid an erroneous output. When the Driver WDT function confirmed the CC-Link IE Field Network board in which a driver

WDT error is occurred from other station, a CPU stop error occurs.

• RUN LED flicks and RD. LED turns ON on the CC-Link IE Field Network board.

• "-28158 (9202H) Driver WDT error" occurs when accessing CC-Link IE Field Network board from the application program

in which the CC IE Field Utility and MELSEC data link library function are used.

When the multiple application programs in which MELSEC data link library is used are executed, driver WDT

error is returned to all the programs. However, only the CC-Link IE Field Network board in which the driver

WDT error has occurred is recognized as an error station on the network. When using driver WDT function,

set the monitoring time considering the margin of the personal computer load.

For the troubleshooting, refer to the following chapter. Page 141 TROUBLESHOOTING

5 FUNCTIONS

5.9 Driver WDT function

6 INSTALLING AND UNINSTALLING SOFTWARE

PACKAGES

This chapter explains the software package installation and uninstallation.

6.1 Installation and Uninstallation Precautions

The following are the precautions when installing and uninstalling the software package.

• Log on as a user with administrator authority.

• Make sure to close other applications running on Windows (including resident software such as antivirus software) before

installation and uninstallation.

• The installer may not work normally because the update program of operating system or other companies' software such as

Windows Update and Java

update program not to start automatically.

• Check if the display settings on the [Device Manager] of Windows are correct, then install an appropriate display driver, or

update the Windows.

• The language switching function of the operating system set by "Regional and Language Options" on the Control Panel

screen is not supported. The installation or uninstallation may not work normally if the language setting is changed.

• Enable the .NET Framework 3.5 (including .NET 2.0 or 3.0) in "Turn Windows features on or off" on the control panel.

• A network drive cannot be specified as the installation destination.

• When the parameters have been set with the utility installed, the parameters are initialized at installation. Save the

parameters with the save file function before installing the utility.

• When the software package has been installed in the environment that the creation of 8.3 filename is disabled, the software

package may not be uninstalled. Enable the creation of 8.3 filename before installing the software package. For the method

on how to check and change the status of 8.3 filename creation to enable/disable, refer to the website of Microsoft

Corporation.

• When using SW1DNC-CCIEF-B Version 1.10L or later, apply Service Pack1 and Security Update for Windows

(KB3033929) to Windows 7 and Windows Server 2008 R2.

• To Windows Server 2016, apply Windows Updates (KB4132216, KB4091664, KB4465659, and KB4480977).

• When installing the software package, enable "User Account Control: Detect application installations and prompt for

elevation" in 'Local Security Policy' in Windows.



update may start automatically. Please install the driver after changing the setting of the

6.2 Installation

The following explains a procedure for installing the software package.

Installation procedure

1. Insert the CD-ROM to the CD-ROM drive.

2. Double-click the "Setup.exe" file on the CD-ROM.

3. By the on-screen instructions, select or enter the necessary information. Refer to the following section when the screen

for which corrective action is not clear, is displayed. Page 145 Action displayed on the screen is not effective while installation

4. Restart the personal computer.

6 INSTALLING AND UNINSTALLING SOFTWARE PACKAGES

6.1 Installation and Uninstallation Precautions

When installation is completed normally

When the installation is completed normally, the following utilities are registered.

Utility

When the installation is completed normally, the utilities shown below are registered in the "Start"*1 of Windows.

*1 [Start screen]  [All apps] or [Start]  [All Programs]

Folder Name Description

[MELSEC]  [CC IE Field Board]

[MELSEC] Device Monitor Utility (Board) Starts Device Monitor Utility.

*2 It is displayed when using Windows 7 or Windows Server 2008 R2. *3 When the MELSEC Data Link Function HELP and a manual are registered both, refer to the manual.

Name SW0DNC-MNETH-B SW1DNC-CCBD2-B SW1DNC-MNETG-B SW1DNC-CCIEF-B

MELSEC Data Link Library Reference Manual (Board)

MELSEC Data Link Library Reference Manual 23Z to 26C 1.11M to 1.14Q 1.12N to 1.16S 1.02C to 1.05F

MELSEC Data Link Function HELP 22Y or earlier 1.10L or earlier 1.11M or earlier 

CC IE Field Utility (Board) Starts CC IE Field Utility.

CC IE Field Board Program Sample A folder in which sample programs are stored.

CC IE Field Board Manual Displays this manual.

MELSEC Data Link Library Reference Manual (Board)

27D or later 1.15R or later 1.17T or later 1.06G or later

It is a utility to set boards and display the status.

It is a utility to monitor devices and change the current value.

Displays MELSEC Data Link Library Reference Manual.

• In order to view the manuals, Adobe Reader is required. Adobe Reader can be downloaded from the Adobe

Systems Incorporated web site.

• When using 64-bit version operating system, the icon may not be displayed even when Adobe Reader is

installed.

MELSEC Data Link Library

MELSEC data link library is used for the following software packages in common. When the utilities are installed on the same

personal computer, the newer MELSEC data link library of the software package is enabled.

• SW0DNC-MNETH-B

• SW1DNC-CCBD2-B

• SW1DNC-MNETG-B

• SW1DNC-CCIEF-B

Driver

When installing the board on the personal computer after the installation of the software package, the driver is installed

automatically.

When the driver installation is completed normally, the following driver is displayed on the Device Manager screen of

Windows.

Device name Driver name

MELSEC CC-Link IE Field Device MELSEC CC-Link IE Field Controller

Service application

To prevent a personal computer from entering the power save mode (hibernate, sleep), MELSECPowerManager is installed

automatically.

For details of MELSECPowerManager, refer to the following section. Page 231 MELSECPowerManager

6 INSTALLING AND UNINSTALLING SOFTWARE PACKAGES

6.2 Installation

When installation is aborted or failed

When the installation is aborted or failed, take corrective actions following the troubleshooting. Page 144 Installation failed

6.3 Uninstallation

This section explains a procedure for uninstalling the software package.

Uninstallation procedure

1. Uninstall the software package from the control panel of Windows.

• If a screen confirming the deletion of common files appears at uninstallation

Select "No to All". If deleting common files, other applications may not operate normally.

• If a screen confirming the execution of restart appears at the completion of uninstallation

Select "Yes, I want to restart my computer now.", and restart the personal computer.

• MELSECPowerManager may not be uninstalled depending on the installation state which affects the other

installed software packages.

For details of MELSECPowerManager, refer to the following section.

Page 231 MELSECPowerManager

When uninstallation is completed normally

When the uninstallation is completed normally, the icons registered in the Windows Start are deleted.

When uninstallation is failed

When the uninstallation is failed, take corrective actions following the troubleshooting. Page 144 Uninstallation failed

6 INSTALLING AND UNINSTALLING SOFTWARE PACKAGES

6.3 Uninstallation

7 OVERVIEW OF CC IE FIELD UTILITY

CC IE Field Utility is software to display settings and status of the CC-Link IE Field Network board.

For installing and uninstalling the CC IE Field utility, refer to the following section. Page 80 INSTALLING AND UNINSTALLING SOFTWARE PACKAGES

7.1 Overview

Use CC IE Field Utility to perform the following functions.

Item Description Menu Reference

Test before wiring

Setting Parameter Setting Set the network parameters. [View]  [Network

Test after wiring

Monitor/ Debug

Bus I/F test Check the hardware of the Bus I/F function of the CC-Link IE

Field Network board.

Memory test Check the memory of the CC-Link IE Field Network board. Page 47 Memory test

Hardware test Check the hardware in the CC-Link IE Field Network board. Page 48 Hardware test

Self-loopback test Test the hardware of the CC-Link IE Field Network board

alone, including the send/receive circuit of the transmission system and cables.

Channel number setting

Loop test Check the network circuit status and parameter setting status

Cable test Check disconnections and incomplete connections of Ethernet

Communication test Check whether the communication path for transient

Device monitor Start Device Monitor Utility and monitor devices. [Online]  [Device

CC-Link IE Field Network diagnostics

Reset operation Reset the board. [Online]  [Reset

Set channel numbers of the CC-Link IE Field Network board. [Online]  [Channel No.

of each station.

cables.

transmission from the own station to the target station is correct.

Check error locations, error causes, and event histories. [Diagnostics]  [CC IE

[Diagnostics]  [Board Diagnostics]

Parameter]

[Online]  [Read from Board]/[Write to Board]

Setting]

[Diagnostics]  [Board Diagnostics]

[Diagnostics]  [CC IE Field Diagnostics]

Monitor Utility]

Field Diagnostics]

Operation]

Page 47 Bus I/F test

Page 49 Self-loopback test

Page 98 SETTING PARAMETERS

Page 113 Writing/ Reading Parameters to/ from Board

Page 112 Setting Board Channel Numbers

Page 54 Loop test

Page 55 Cable test

Page 56 Communication test

Page 115 MONITORING

Page 118 Diagnosing CC-Link IE Field Network

Page 114 Resetting Board

7 OVERVIEW OF CC IE FIELD UTILITY

7.1 Overview

7.2 Menu List

This section explains functions of CC IE Field Utility.

[Project] Reference

 [New] Creates a new project. Page 91 Creating Projects

 [Open] Opens an existing project. Page 92 Opening Existing Projects

 [Close] Closes an open project. Page 96 Closing Projects

 [Save] Saves a project. Page 93 Saving Projects

 [Save As] Names and saves a project.

 [Compress/Unpack]  [Compress] Compresses and saves a project. Page 94 Saving Projects with

 [Compress/Unpack]  [Unpack] Unpacks a compressed project.

 [Delete] Deletes an existing project. Page 96 Deleting Projects

 [Verify] Verifies data of an open project and data of other projects. Page 97 Verifying Project Data

 [(The latest file 1 to 4)] Displays the recently used CC IE Field Utility project paths and

opens the selected project.

 [Exit] Exits CC IE Field Utility. Page 85 Starting and Exiting

[Edit] Reference

 [Cut] Cuts the selected data. 

 [Copy] Copies the selected data.

 [Paste] Pastes the cut or copied data at the cursor position.

[View] Reference

 [Network Parameter] Sets the network parameters. Page 98 SETTING PARAMETERS

 [Toolbar]  [(Toolbar name)] Displays/hides the toolbar. Page 87 Toolbars

Compression and Unpacking Projects



[Online] Reference

 [Channel No. Setting] Displays/changes board channel numbers. Page 112 Setting Board Channel Numbers

 [Read from Board] Reads parameters from the board. Page 113 Writing/Reading Parameters to/

 [Write to Board] Writes parameters to the board.

 [Verify with Board] Verifies parameters set to the board and parameters of open

project.

 [Reset Operation] Resets the board. Page 114 Resetting Board

 [Device Monitor Utility] Starts Device Monitor Utility. Page 115 MONITORING

from Board

Page 114 Verifying Parameters of Board and Project

[Diagnostics] Reference

 [Board Diagnostics] Diagnoses the operating status of the board. Page 117 Diagnosing Board

 [CC IE Field Diagnostics] Diagnoses the CC-Link IE Field Network. Page 118 Diagnosing CC-Link IE Field

Network

[Window] Reference

 [Cascade] Tiles windows in overlapping display. 

 [Tile Vertically] Tiles windows vertically.

 [Tile Horizontally] Tiles windows horizontally.

 [Arrange Icons] Arranges the icons at the bottom of the window.

 [Close All] Closes all open windows.

 [(Window information being displayed)] Displays the open window.

 [Window] Displays a list of open windows.

And opens and arranges specified windows.

Page 88 Work windows

[Help] Reference

 [Manual] Displays the manual. Page 90 Help Function

 [About] Displays product information such as the version.

7 OVERVIEW OF CC IE FIELD UTILITY

7.2 Menu List

8 SCREEN CONFIGURATION AND BASIC

Operating procedure

OPERATIONS

This chapter explains the screen configuration and basic operations of CC IE Field Utility.

8.1 Starting and Exiting

This section explains the operation methods for starting and exiting CC IE Field Utility.

Starting up

Start up CC IE Field Utility.

1. Select [MELSEC]  [CC IE Field Board]

*1 Select [All apps] on the Start screen or [Start]  [All Programs]. *2 It is displayed when using Windows 7 or Windows Server 2008 R2.

Starting CC IE Field Utility when the user account control is validated

When CC IE Field Utility is started while user account control (UAC) is validated, the following warning screen

is displayed. Click the "Allow (A)" or [Yes] button to start the utility.

For details on how to prevent this screen from being displayed, refer to the following section. Page 225 Windows Warning Message

Exiting

Exit CC IE Field Utility.

 [CC IE Field Utility (Board)] from Windows Start*1.

1. Select [Project]  [Exit]

8 SCREEN CONFIGURATION AND BASIC OPERATIONS

8.1 Starting and Exiting

8.2 Screen Configuration and Basic Operations

Window

Displayed items

Work window

Toolbar

Menu bar

Title bar

This section explains the main frame (basic screen) of CC IE Field Utility that is displayed when it is started up.

Main frame configuration

The following shows a main frame configuration.

Name Description Reference

Title bar Displays a project name. 

Menu bar Displays menu options for executing each function. 

Toolbar Displays tool buttons for executing each function. Page 87 Toolbars

Work window A main screen used for operations such as parameter setting, and monitoring. Page 88 Work windows

8 SCREEN CONFIGURATION AND BASIC OPERATIONS

8.2 Screen Configuration and Basic Operations

Toolbars

Operating procedure

Draganddrop

Drag and drop

A toolbar is a block of on-screen buttons for executing frequently-used functions included in a menu.

The toolbars to be displayed and their display positions on the screen can be set by the user.

Displaying/hiding toolbars

Select a toolbar to be displayed.

1. Select [View]  [Toolbar]  [(toolbar name)]

The selected toolbar is displayed on the screen.

Switching the Docking/floating of toolbars

Switch the display format (docking/floating) of a toolbar.

■Floating a toolbar

Displays a toolbar floating from the main frame.

1. Drag a docked toolbar to the desired position for floating display.

■Docking a toolbar

Displays a toolbar docked to the main frame.

1. Drag the title bar of a floating toolbar and drop it in the main frame.

• Method for docking a toolbar at the original position

To dock a floating toolbar back at the original position, double-click on the title bar of the toolbar.

8 SCREEN CONFIGURATION AND BASIC OPERATIONS

8.2 Screen Configuration and Basic Operations

Customizing toolbars

Operating procedure

Window

Work window switching button

Scroll button

Tool hint

Tab

This function sets the types of tool buttons to be displayed in each toolbar.

1. Select ( button)  [Add or Remove Buttons] of Toolbar.

A list of tool buttons is displayed.

2. Check the check box in front of the tool button to be displayed on the screen.

The checked tool buttons are displayed on the screen.

The toolbar configuration returns to the default when [Reset Toolbar] is selected.

Work windows

A work window is a main screen used for operations such as parameter setting and monitoring in CC IE Field Utility.

8 SCREEN CONFIGURATION AND BASIC OPERATIONS

8.2 Screen Configuration and Basic Operations

Displayed items

Window

Item Description

Right click

Tab The tab becomes active when selected.

Tool hint Displays a brief explanation when the cursor is moved onto the selected tab.

Scroll button Scroll the tab display to the left and right.

Work window switching button Displays a list of open windows.

Display windows Display screens such as the "Network Parameter Setting the Number of CC IE Field Cards" screen.

The tab order can be changed by dragging and dropping tabs. The window(s) can be closed from the menu displayed by right-clicking the tab. In addition, the active window can be closed by clicking [] button on the tab.

Displays hidden tabs.

Select a data name displayed on the list to display its corresponding window on the top.

Arranging/displaying windows

Displays a list of open windows.

And opens and arranges specified windows.

This function is useful to display the desired window efficiently when multiple windows are open.

[Window]  [Window]

8 SCREEN CONFIGURATION AND BASIC OPERATIONS

8.2 Screen Configuration and Basic Operations

8.3 Help Function

Operating procedure

Displaying manuals

Displays the manual of the CC-Link IE Field Network board.

1. Select [Help]  [Manual]

Checking version of CC IE Field Utility

Displays information such as the software version of CC IE Field Utility.

1. Select [Help]  [About]

8 SCREEN CONFIGURATION AND BASIC OPERATIONS

8.3 Help Function

9 PROJECT MANAGEMENT

Window

This chapter explains basic operations of CC IE Field Utility such as creating, opening, and saving projects.

9.1 Creating Projects

Create a new project.

[Project]  [New]

• Creating a new project with data read from the board

A new project is created with the data read from the CC-Link IE Field Network board when data are read from the board before creating a new project. (Page 113 Writing/Reading Parameters to/from Board)

• A note on creating a new project

Do not change the storage location or file name of created workspace or project folder/file using an

application such as Windows Explorer.

9 PROJECT MANAGEMENT

9.1 Creating Projects

9.2 Opening Existing Projects

Window

Operating procedure

Read a project saved in a hard disk or other memory media of a personal computer.

[Project]  [Open]

1. Set the items on the screen.

Item Description

Save Folder Path Enter the folder (drive/path) where the workspace is saved.

Workspace/Project List Select a workspace.

Workspace Name A selected workspace name is displayed.

Project Name A selected project name is displayed.

Title The title of the selected project is displayed.

[Browse] button Displays the "Browse For Folder" screen.

The folder can be selected in the "Browse For Folder" screen by clicking the [Browse] button.

The display is switched to the project list by double-clicking "Workspace".

2. Click the [Open] button.

The specified project is displayed.

• Workspace

A workspace is a folder of CC IE Field Utility dedicated to manage multiple projects under the same name.

Do not change the workspace configuration using an application such as Windows Explorer.

• Network drive display on the "Browse For Folder" screen

When the network drive display is not displayed, log on to Windows as a user who has an access authority

to the assigned folder.

9 PROJECT MANAGEMENT

9.2 Opening Existing Projects

9.3 Saving Projects

Window

Operating procedure

Save a project in a hard disk or other memory media of a personal computer.

Saving projects under the specified name

Save the open project under the specified name.

[Project]  [Save As]

1. Set the items on the screen.

Item Description

Save Folder Path Enter the folder (drive/path) where the workspace is saved.

The folder can be selected in the "Browse For Folder" screen by clicking the [Browse] button.

Workspace/Project List Select a workspace.

Workspace Name

Project Name

Title

*1 Enter each workspace name, project name, and title within 128 characters.

Note, however, that the total number of characters used for the workspace folder path, workspace name, and project name should not exceed 150 characters.

The display is switched to the project list by double-clicking "Workspace".

Enter the workspace name.

Enter the project name.

Enter the title of the project.

2. Click the [Save] button.

The project is saved in the specified folder under the specified workspace name, project name, and title.

• Workspace

A workspace is a folder of CC IE Field Utility dedicated to manage multiple projects under the same name.

Do not change the workspace configuration using an application such as Windows Explorer.

• Saving projects in an existing destination

When saving a project in an existing destination (workspace or project), the destination folder can be

selected from the "Workspace/Project List".

• Network drive display on the "Browse For Folder" screen

When the network drive display is not displayed, log on to Windows as a user who has an access authority

to the assigned folder.

9 PROJECT MANAGEMENT

9.3 Saving Projects

Saving projects

Operating procedure

Window

Operating procedure

Overwrite and save the project being edited.

1. Select [Project]  [Save]

The existing project data are overwritten.

9.4 Saving Projects with Compression and Unpacking

Projects

This section explains the methods for saving projects with compression, and unpacking projects saved with compression.

This function gives easier project data passes.

This function is not compatible with commercially available file compression and decompression tools.

Saving projects with compression

Save a desired project with compression.

[Project]  [Compress/Unpack]  [Compress]

1. Set the items on the screen.

Item Description

Project to be Compressed Workspace Folder Path Enter the folder (drive/path) where the workspace is saved.

Compress Destination Setting Compressed File Name Enter the folder where the compressed file is saved and the compressed file name.

2. Click the [Compress] button.

The compressed project file (*.ifz) is saved in the specified folder.

9 PROJECT MANAGEMENT

9.4 Saving Projects with Compression and Unpacking Projects

The folder can be selected in the "Browse For Folder" screen by clicking the [Browse] button.

Workspace/Project List Select a workspace and a project.

Workspace Name A selected workspace name is displayed.

Project Name A selected project name is displayed.

The compressed file name can be set in the "Compressed File Name" screen by clicking the [Browse] button.

Unpacking projects saved with compression

Window

Operating procedure

Unpack a project saved with compression.

[Project]  [Compress/Unpack]  [Unpack]

1. Set the items on the screen.

Item Description

Unpack Source Setting Compressed File Name Enter the folder (drive/path) in which the compressed file to be unpacked is saved,

Unpack Destination Project Workspace Folder Path Enter the folder (drive/path) to which the project to be unpacked is saved.

Workspace/Project List Select a workspace and a project.

Workspace Name Enter the name of the workspace to which the unpacked project is saved.

Project Name Enter the name of the project to which the unpacked project is saved.

[Unpack and Open] button Unpacks the compressed project file and opens the project.

and the compressed file name. The compressed file name can be selected in the "Compressed File Name" screen by clicking the [Browse] button.

The folder can be selected in the "Browse For Folder" screen by clicking the [Browse] button.

2. Click the [Unpack] button.

The compressed project file is unpacked and saved in the specified folder.

9 PROJECT MANAGEMENT

9.4 Saving Projects with Compression and Unpacking Projects

9.5 Deleting Projects

Operating procedure

This section explains a method for deleting a project saved in a hard disk or other memory media of a personal computer.

1. Select [Project]  [Delete]

The "Delete Project" screen is displayed.

2. Select the project to be deleted.

3. Click the [Delete] button.

The selected project is deleted.

9.6 Closing Projects

This section explains a method for closing an open project.

1. Select [Project]  [Close]

9 PROJECT MANAGEMENT

9.5 Deleting Projects

9.7 Verifying Project Data

Window

Operating procedure

This section explains a method for verifying data of an open project and data of another project.

Use this function to check if the data of the projects are the same, or to check the changed parameter locations. To verify data in the board, perform board verification. (Page 114 Verifying Parameters of Board and Project)

[Project]  [Verify]

1. Click the [Browse] button to set the verify destination project.

Item Description

Verify Destination Project Workspace Folder Path The path to the workspace of a verify destination is displayed.

Workspace Name A workspace name is displayed.

Project Name The project name of a verify destination is displayed.

Title The project title of a target project is displayed.

2. Click the [Execute] button.

The verify result is displayed in the "Verify Result" screen.

9 PROJECT MANAGEMENT

9.7 Verifying Project Data

10 SETTING PARAMETERS

This chapter explains the parameter setting items and operations on the setting screens in CC IE Field Utility.

For writing set parameters to a board, refer to the following section. Page 113 Writing/Reading Parameters to/from Board

10.1 Parameter List

The following table shows the list of CC-Link IE Field Network parameters. : Required, : Set as required, : No setting

Item Necessity of setting Reference

Master station Local stations

Network setting Network Type  Page 99 Setting Network Parameter

Channel No. 

Network No. 

Total Stations 

Station No. 

Mode 

Network Configuration Setting Station No. Page 101 Network configuration

Station Type 

RX/RY Setting 

RWw/RWr Setting 

Reserved/Error Invalid Station 

Alias 

Comment 

Supplementary Setting 

Network Operation Setting  Page 104 Network operation setting

Event Setting  Page 104 Event setting

Driver Setting  Page 106 Driver setting

Tar g e t S e t ti n g  Page 107 Target setting

Routing Parameters  Page 108 Routing parameters

setting

• When parameters are not set

CC-Link IE Field Network board operates as a local station (station number 1) of network number 1 in the

offline mode. In this case, only transient transmission is performed. (Cyclic transmission is not performed).

Mitsubishi Electric MELSEC SW1DNC-CCIEF-B, MELSEC Q80BD-J71GF11-T2, MELSEC Q81BD-J71GF11-T2 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

SAFETY PRECAUTIONS

CONDITIONS OF USE FOR THE PRODUCT

CONSIDERATIONS FOR USE

INTRODUCTION

CONTENTS

RELEVANT MANUALS

TERMS

PACKING LIST

1 OVERVIEW

1.1 CC-Link IE Field Network

1.2 CC-Link IE Field Network Board

2.2 CC-Link IE Field Network Configuration

Single Network System

2 SYSTEM CONFIGURATION

2.1 System Configuration Using CC-Link IE Field Network Board

Multi-Network System

Precautions

Cables

Hubs

2.3 Network Components

2.4 Operating Environment

3 SPECIFICATIONS

3.1 General Specifications

3.2 Performance Specifications

3.3 List of Buffer Memory Addresses

4 PROCEDURE BEFORE OPERATION

4.1 Procedure Before Operation

4.2 Part Names

Operation LED

Connector

Handling precautions

Installation environment

4.3 Installation

Procedure for replacing mounting brackets

Board installation

4.4 Setting Channel Numbers

Bus I/F test

Memory test

4.5 Tests Before Wiring (Standalone Tests of the Board)

Hardware test

Self-loopback test

Wiring Precautions

4.6 Wiring

Ethernet cable connection

Loop test

4.7 Tests After Wiring

Cable test

Communication test

5 FUNCTIONS

5.1 Function List

Data flow and link device assignment

5.2 Cyclic Transmission

Link scan and link refresh

Assurance of cyclic data integrity

Input status of data link faulty station setting

Cyclic transmission stop and restart

Communication on the same network

5.3 Transient Transmission

Communication with different networks

5.4 SEND/RECV Function

5.5 Reserved Station Specification and Reserved Station Function Disable Function

5.6 Error Invalid Station and Temporary Error Invalid Station Setting Function

5.7 Event Function

5.8 Loopback Function

5.9 Driver WDT function

6.2 Installation

Installation procedure

6 INSTALLING AND UNINSTALLING SOFTWARE PACKAGES

6.1 Installation and Uninstallation Precautions

When installation is completed normally

When installation is aborted or failed

Uninstallation procedure

When uninstallation is completed normally

When uninstallation is failed

6.3 Uninstallation

7 OVERVIEW OF CC IE FIELD UTILITY