OPERATION MANUAL - Omronomron.com.ru/dynamic/managers/manage_8/files/w370e11.pdf · OMRON products...

Cat.No. W370–E1–1

Optical Ring ControllerLink Units (H-PFC Cable)

SYSMACCS1W-CLK12CVM1-CLK12

OPERATION MANUAL

CS1W-CLK12 andCVM1-CLK12Optical Ring Controller Link Units(H-PCF Cable)

Operation Manual

Produced March 2000

!

!

!

v

Notice:OMRON products are manufactured for use according to proper procedures by a qualified operatorand only for the purposes described in this manual.

The following conventions are used to indicate and classify precautions in this manual. Always heedthe information provided with them. Failure to heed precautions can result in injury to people or dam-age to property.

DANGER Indicates an imminently hazardous situation which, if not avoided, will result in death orserious injury.

WARNING Indicates a potentially hazardous situation which, if not avoided, could result in death orserious injury.

Caution Indicates a potentially hazardous situation which, if not avoided, may result in minor ormoderate injury, or property damage.

OMRON Product ReferencesAll OMRON products are capitalized in this manual. The word “Unit” is also capitalized when it refersto an OMRON product, regardless of whether or not it appears in the proper name of the product.

The abbreviation “Ch,” which appears in some displays and on some OMRON products, often means“word” and is abbreviated “Wd” in documentation in this sense.

The abbreviation “PC” means Programmable Controller and is not used as an abbreviation for any-thing else.

Visual AidsThe following headings appear in the left column of the manual to help you locate different types ofinformation.

Note Indicates information of particular interest for efficient and convenient operationof the product.

1, 2, 3... 1. Indicates lists of one sort or another, such as procedures, checklists, etc.

OMRON, 2000All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in anyform, or by any means, mechanical, electronic, photocopying, recording, or otherwise, without the prior written permis-sion of OMRON.

No patent liability is assumed with respect to the use of the information contained herein. Moreover, because OMRON isconstantly striving to improve its high-quality products, the information contained in this manual is subject to changewithout notice. Every precaution has been taken in the preparation of this manual. Nevertheless, OMRON assumes noresponsibility for errors or omissions. Neither is any liability assumed for damages resulting from the use of the informa-tion contained in this publication.

TABLE OF CONTENTS

vii

PRECAUTIONS xi. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Intended Audience xii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 General Precautions xii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Safety Precautions xii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Operating Environment Precautions xiii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Applications Precautions xiii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Conformance to EC Directives xv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 1Features and System Configuration 1. . . . . . . . . . . . . . . . .

1-1 Overview 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Specifications and Configurations 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 Selecting Communications Functions 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 Basic Procedures 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 Application Precautions 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 2Basic Procedures 23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-1 Data Links Procedures 24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 Message Service Procedure 28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 3Installation and Wiring 31. . . . . . . . . . . . . . . . . . . . . . . . . . .

3-1 Component Names and Functions 32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 Installation 36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3 Optical Wiring 38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 4Preparations for Communications 43. . . . . . . . . . . . . . . . . .

4-1 CS1-series Optical Ring Controller Link Units 44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 CVM1 and CV-series Optical Ring Controller Link Units 47. . . . . . . . . . . . . . . . . . . . . . . .

SECTION 5Data Links 51. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-1 What Are Data Links? 52. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2 Setting Data Links 57. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3 Starting and Stopping Data Links 75. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4 Checking Data Link Status 77. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 6Message Service 83. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-1 Introduction 84. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 Selecting Communications Instructions 94. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3 Using the Message Service 97. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4 FINS Commands and Responses 103. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5 Commands and Responses for Controller Link Units 104. . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6 Response Codes 118. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 7Network Interconnections 127. . . . . . . . . . . . . . . . . . . . . . . . .

7-1 What is Network Interconnection? 128. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2 Remote Programming and Monitoring 130. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3 Routing Tables 132. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4 Setting Routing Tables 133. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TABLE OF CONTENTS

viii

SECTION 8Communications Timing 141. . . . . . . . . . . . . . . . . . . . . . . . . .

8-1 Communications Mechanism 142. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2 Communications Cycle Time 144. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3 Data Link I/O Response Time 148. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4 Message Delay Times 153. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 9Troubleshooting and Maintenance 159. . . . . . . . . . . . . . . . . .

9-1 Troubleshooting Using Indicators 160. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2 Status Area and Troubleshooting 171. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3 Error Log 183. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4 Locating and Correcting Cable Disconnections 191. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5 Cleaning and Inspection 204. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6 Handling Precautions 205. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

AppendicesA Standard Models 209. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B Memory Areas 213. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C CS1-series Optical Bus Controller Link Units 225. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Index 231. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Revision History 235. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ix

About this Manual:

This manual describes the installation, setup, and operation of the CS1W-CLK12 and CVM1-CLK12 Opti-cal Ring Controller Link Units for CS1-series, CVM1, and CV-series PCs and includes the sectionsdescribed below. The Controller Link Units are used to connect these PCs to an Optical Ring ControllerLink Network. The following three manuals are related to application of the Controller Link Network.

Name Contents Cat. No. (suffixes omitted)

CS1W-CLK12 and CVM1-CLK12Controller Link Units Operation Manual

Installation, setup, and operating procedures for ControllerLink Units (to connect PCs to a Controller Link Network).

W370 (this manual)

C200HW-ZW3AT2-E and3G8F5-CLK11-E/CLK21-E, Controller Link Support Software (Ver.2.00)Operation Manual

Installation and operating procedures for the ControllerLink Support Software. The Controller Link SupportSoftware enables manually set data links and otherprocedures for a Controller Link Network.

W308

3G8F5-CLK11-E and 3G8F5-CLK21-E Controller Link Support Boards Operation Manual

Installation, setup, and operating procedures for ControllerLink Support Boards (to connect computers to aController Link Network).

W307

Please read this manual and related manuals carefully and be sure you understand the information pro-vided before attempting to install and operate a Controller Link Unit.

Precautions provides general precautions for using the Controller Link Units and related devices.

Section 1 provides basic information on Controller Link Networks, and gives the reader an overview ofwhat Controller Link Networks can do and how best to use them.

Section 2 describes the basic procedures for using the Controller Link Unit. The settings required foreach of the functions are also explained briefly. For more details, refer to the subsequent sections on indi-vidual functions.

Section 3 explains how to install a Controller Link Unit onto a CPU Backplane and how to wire the Control-ler Link Network.

Section 4 describes the settings required for starting communications. These basic settings are requiredboth for data links and the message service. Carry out the settings described here before turning ONpower to the Controller Link Unit.

Section 5 describes how to use data links in a Controller Link Network. Refer to Section 2 Basic Proce-dures for an outline of data link application.

Section 6 explains how to use the message service provided by a Controller Link Unit. It also explains theFINS commands and responses supported by Controller Link Units and those supported by CS1-series,CVM1 and CV-series PCs.

Section 7 describes the methods used to connect multiple networks through CS1-series, CVM1, and CV-series PCs. The section also describes remote programming and monitoring with Programming Devices.

Section 8 explains details on Controller Link Network communications. Refer to this section for networkcommunications that require accurate communications timing.

Section 9 provides information on troubleshooting errors that occur during Controller Link Unit operation,as well as daily inspection, cleaning, and other maintenance procedures.

Appendix A provides a list of standard OMRON products related to Controller Link Networks,Appendix B provides easy reference to the CPU Unit memory areas related to Controller Link Networks,and Appendix C provides information on CS1-series Optical Bus Controller Link Units (produc-tion to be discontinued).

WARNING Failure to read and understand the information provided in this manual may result inpersonal injury or death, damage to the product, or product failure. Please read eachsection in its entirety and be sure you understand the information provided in the sectionand related sections before attempting any of the procedures or operations given.

!

xi

PRECAUTIONS

This section provides general precautions for using the Controller Link Unit and related devices.

The information contained in this section is important for the safe and reliable application of the Controller Link Unit.You must read this section and understand the information contained before attempting to set up or operate a Control-ler Link Unit.

1 Intended Audience xii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 General Precautions xii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Safety Precautions xii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 Operating Environment Precautions xiii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Applications Precautions xiii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Conformance to EC Directives xv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

!

!

!

!

6Safety Precautions

xii

1 Intended AudienceThis manual is intended for the following personnel, who must also have knowl-edge of electrical systems (an electrical engineer or the equivalent).

• Personnel in charge of installing FA systems.

• Personnel in charge of designing FA systems.

• Personnel in charge of managing FA systems and facilities.

2 General PrecautionsThe user must operate the product according to the performance specificationsdescribed in the operation manuals.

Before using the product under conditions which are not described in the manualor applying the product to nuclear control systems, railroad systems, aviationsystems, vehicles, combustion systems, medical equipment, amusementmachines, safety equipment, and other systems, machines, and equipment thatmay have a serious influence on lives and property if used improperly, consultyour OMRON representative.

Make sure that the ratings and performance characteristics of the product aresufficient for the systems, machines, and equipment, and be sure to provide thesystems, machines, and equipment with double safety mechanisms.

This manual provides information for programming and operating OMRON PCsand related devices. Be sure to read this manual before attempting to use thesoftware and keep this manual close at hand for reference during operation.

WARNING It is extremely important that a PC and all PC Units be used for the specifiedpurpose and under the specified conditions, especially in applications that candirectly or indirectly affect human life. You must consult with your OMRONrepresentative before applying a PC System to the above mentionedapplications.

3 Safety Precautions

WARNING Do not attempt to take any Unit apart while the power is being supplied. Doing somay result in electric shock.

WARNING Do not touch any of the terminals or terminal blocks while the power is beingsupplied. Doing so may result in electric shock.

WARNING Provide safety measures in external circuits (i.e., not in the ProgrammableController), including the following items, to ensure safety in the system if anabnormality occurs due to malfunction of the PC or another external factoraffecting the PC operation. Not doing so may result in serious accidents.

• Emergency stop circuits, interlock circuits, limit circuits, and similar safetymeasures must be provided in external control circuits.

• The PC will turn OFF all outputs when its self-diagnosis function detects anyerror or when a severe failure alarm (FALS) instruction is executed. As a coun-termeasure for such errors, external safety measures must be provided to en-sure safety in the system.

• The PC outputs may remain ON or OFF due to deposition or burning of theoutput relays or destruction of the output transistors. As a countermeasure for

!

!

!

!

!

!

5Applications Precautions

xiii

such problems, external safety measures must be provided to ensure safety inthe system.

• When the 24-VDC output (service power supply to the PC) is overloaded orshort-circuited, the voltage may drop and result in the outputs being turnedOFF. As a countermeasure for such problems, external safety measures mustbe provided to ensure safety in the system.

Caution Execute online edit only after confirming that no adverse effects will be causedby extending the cycle time. Otherwise, the input signals may not be readable.

Caution Confirm safety at the destination node before transferring a program to anothernode or changing contents of the I/O memory area. Doing either of these withoutconfirming safety may result in injury.

4 Operating Environment Precautions

Caution Do not operate the control system in the following locations:

• Locations subject to direct sunlight.

• Locations subject to temperatures or humidity outside the range specified inthe specifications.

• Locations subject to condensation as the result of severe changes in tempera-ture.

• Locations subject to corrosive or flammable gases.

• Locations subject to dust (especially iron dust) or salts.

• Locations subject to exposure to water, oil, or chemicals.

• Locations subject to shock or vibration.

Caution Take appropriate and sufficient countermeasures when installing systems in thefollowing locations:

• Locations subject to static electricity or other forms of noise.

• Locations subject to strong electromagnetic fields.

• Locations subject to possible exposure to radioactivity.

• Locations close to power supplies.

Caution The operating environment of the PC System can have a large effect on the lon-gevity and reliability of the system. Improper operating environments can lead tomalfunction, failure, and other unforeseeable problems with the PC System. Besure that the operating environment is within the specified conditions at installa-tion and remains within the specified conditions during the life of the system.

5 Applications PrecautionsObserve the following precautions when using the Controller Link Unit.

WARNING Failure to abide by the following precautions could lead to serious or possiblyfatal injury. Always heed these precautions.

• Always ground the system to 100 Ω or less when installing the system to pro-tect against electrical shock.

• Always turn OFF the power supply or the backup power supply to the PC or thecomputer before attempting any of the following. Performing any of the follow-ing with the power supply turned ON may lead to electrical shock:

!

5Applications Precautions

xiv

• Installing or removing the Controller Link Unit.

• Assembling the Units.

• Setting DIP or rotary switches.

• Connecting or disconnecting any cables or wiring.

• Connecting or disconnecting any connectors.

Caution Failure to abide by the following precautions could lead to faulty operation or thePC or the system or could damage the PC or PC Units. Always heed these pre-cautions.

• Fail-safe measures must be taken by the customer to ensure safety in theevent of incorrect, missing, or abnormal signals caused by broken signal lines,momentary power interruptions, or other causes.

• Interlock circuits, limit circuits, and similar safety measures in external circuits(i.e., not in the Programmable Controller) must be provided by the customer.

• Always use the power supply voltages specified in the operation manuals. Anincorrect voltage may result in malfunction or burning.

• Take appropriate measures to ensure that the specified power with the ratedvoltage and frequency is supplied. Be particularly careful in places where thepower supply is unstable. An incorrect power supply may result in malfunction.

• Install external breakers and take other safety measures against short-circuit-ing in external wiring. Insufficient safety measures against short-circuiting mayresult in burning.

• Disconnect the functional ground terminal when performing withstand voltagetests. Not disconnecting the functional ground terminal may result in burning.

• Do not attempt to disassemble, repair, or modify any Units. Any attempt to doso may result in malfunction, fire, or electric shock.

• Be sure that all the mounting screws, terminal screws, and cable connectorscrews are tightened to the torque specified in the relevant manuals. Incorrecttightening torque may result in malfunction.

• Leave the label attached to the Unit when wiring. Removing the label may re-sult in malfunction if foreign matter enters the Unit.

• Remove the label after the completion of wiring to ensure proper heat dissipa-tion. Leaving the label attached may result in malfunction.

• Use crimp terminals for wiring. Do not connect bare stranded wires directly toterminals. Connection of bare stranded wires may result in burning.

• Double-check all wiring and switch settings before turning ON the power sup-ply. Incorrect wiring may result in burning.

• Wire all connections correctly.

• Mount Units only after checking terminal blocks and connectors completely.

• Be sure that the communications cable connectors and other items with lock-ing devices are properly locked into place. Improper locking may result in mal-function.

• Use special packing box when transporting the Controller Link Unit. Handle theproduct carefully so that no excessive vibration or impact is applied to the prod-uct during transportation.

• Check the user program for proper execution before actually running it on theUnit. Not checking the program may result in an unexpected operation.

• Confirm that no adverse effect will occur in the system before attempting any ofthe following. Not doing so may result in an unexpected operation.

• Changing the operating mode of the PC.

• Force-setting/force-resetting any bit in memory.

6Conformance to EC Directives

xv

• Changing the present value of any word or any set value in memory.

• Inappropriate settings in data link tables or routing tables can cause unex-pected system operation. Always check table settings before starting opera-tion, and always test the settings in trial operation before starting or stoppingthe data links in actual operation.

• CPU Bus Units will be automatically restarted when routing tables are trans-ferred from a Programming Device to the CPU Unit. Resetting is required touse the new tables. Confirm that restarting the CPU Bus Units will not adverse-ly affect system operation before transferring routing tables.

• Observe the following precautions when wiring the communications cable orbackup power supply cables.

• Separate the cables from the power lines or high-tension lines.

• Do not bend the cables.

• Do not pull on the cables.

• Do not place heavy objects on top of the cables.

• Route cables inside conduits.

• Before touching the Unit, be sure to first touch a grounded metallic object inorder to discharge any static build-up.

6 Conformance to EC DirectivesThe Controller Link Units conform to EMC Directive as follows:

EMC DirectivesOMRON devices that comply with EC Directives also conform to the relatedEMC standards so that they can be more easily built into other devices or theoverall machine. The actual products have been checked for conformity to EMCstandards (see the following note). Whether the products conform to the stan-dards in the system used by the customer, however, must be checked by thecustomer.

EMC-related performance of the OMRON devices that comply with EC Direc-tives will vary depending on the configuration, wiring, and other conditions of theequipment or control panel on which the OMRON devices are installed. The cus-tomer must, therefore, perform the final check to confirm that devices and theoverall machine conform to EMC standards.

Note Applicable EMC (Electro-Magnetic Compatibility) standards are as follows:

EMS (Electro-Magnetic Susceptibility): EN61131-2 for CVM1 and CV SeriesEN50082-2 for CS1 Series

EMI (Electro-Magnetic Interference): EN50081-2 (Radiated emission: 10-m regulations)

The Controller Link Units that comply with EC Directives (CVM1-CLK12,CS1W-CLK12, and CS1W-CLK11,) must be installed as follows:

1, 2, 3... 1. The Controller Link Units are designed for installation inside control panels.All Controller Link Units must be installed within control panels.

2. Use reinforced insulation or double insulation for the DC power suppliesused for the communications power supply and I/O power supplies.

3. The Controller Link Units that comply with EC Directives also conform to theCommon Emission Standard (EN50081-2). Radiated emission characteris-tics (10-m regulations) may vary depending on the configuration of the con-trol panel used, other devices connected to the control panel, wiring, andother conditions. You must therefore confirm that the overall machine orequipment complies with EC Directives.

1

SECTION 1Features and System Configuration

This section provides basic information on Controller Link Networks, and gives the reader an overview of what ControllerLink Networks can do and how best to use them.

1-1 Overview 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-1 What Is the Controller Link? 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1-2 Features 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-2 Specifications and Configurations 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2-1 System Configuration 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2-2 Models 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2-3 General Specifications 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2-4 Communications Specifications 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2-5 Controller Link Unit Models and PCs 11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2-6 Devices Required for Connection 12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2-7 Programming Devices 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2-8 Backup Power Supply 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-3 Selecting Communications Functions 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 Basic Procedures 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5 Application Precautions 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-1SectionOverview

2

1-1 Overview

1-1-1 What Is the Controller Link?The Controller Link is an FA network that can send and receive large data pack-ets flexibly and easily among the OMRON C200HX/HG/HE ProgrammableControllers (PCs), CS1-series PCs, CVM1 PCs, CV-series PCs, and IBM PC/ATor compatible computers.

The Controller Link supports data links that enable data sharing and a messageservice that enables sending and receiving data when required. Data link areascan be freely set to create a flexible data link system and effectively use dataareas.

High-volume data transmissions at high speed enable construction of a widerange of networks, from low-level systems to high.

A Controller Link Network can be connected by either shielded twisted-paircable or fiber-optic cable. For details on networks using twisted-pair cable (i.e.,Wired Systems), refer to the Controller Link Unit Operation Manual (W309).

The functions of a Controller Link Network are outlined below.

Data link Manual settings

Automatic settings

Message service

RAS functions Status area function

Error log function

Polling node backup

Controller Link

SEND/RECV instructions

CMND instruction

Node bypass function

Transmission pathduplication*

Disconnect detection andnotification*

Node connectionconfiguration data reading*

Note *In token- ring mode only.

Wired Systems are supported by CS1-series, C200HX/HG/HE, CVM1, and CV-series PCs.

CPU

CPU

CPU

CS1W-CLK21Controller Link Unit

CS1-series PC

IBM PC/AT orcompatible

Twisted-pair cable3G8F5-CLK21-EController LinkSupport Board

C200HW-CLK21Controller Link Unit

CVM1-CLK21Controller Link Unit

C200HX/HG/HEPC

CVM1, CV-seriesPC

CPU

CQM1H-CLK21Controller Link Unit

CQM1H-seriesPC

Wired System (Twisted-pair Cable)

1-1SectionOverview

3

Optical Systems are supported by CS1-series, CVM1, and CV-series PCs.

Token-ring Mode

CS1W-CLK12Controller Link Unit(Token-ring mode)

CVM1-CLK12Controller Link Unit(Token-ring mode)



Backup powersupply (24 V DC)

CS1-series PC CVM1 or CV-series PC

CVM1 or CV-series PCCS1-series PC

H-PCF Optical Fiber Cable(ring connection)

CPU

CPU

CPU

CPU

Token-bus Mode

CS1W-CLK12Controller Link Unit(Token-bus mode)



3G8F5-CLK11Controller Link Support Board

CS1-series PC CS1-series PCCVM1 or CV-seriesPC

Backup powersupply (24 V DC) H-PCF Optical Fiber Cable

(daisy-chain connection)


CPU

CPU

CPU

Data LinksData links allow the constant sharing of data in predetermined data areas be-tween nodes, between PCs, or between a PC and an IBM PC/AT or compatiblecomputer on the network. Data links do not require the use of communicationsprograms on the PC (CPU Unit) or IBM PC/AT or compatible computer. Datawritten in the send area of the local node will be automatically sent to the receivearea of other nodes.

The I/O area (CIO area), link area (LR area), data memory area (DM area), andextended data memory area (EM area) can be freely set in the send or receivearea. (The area used for sending or receiving data using the data link function iscalled “data link area.”)

Optical Bus or OpticalRing System (H-PCFCable)

1-1SectionOverview

4

The data link area can be set automatically or manually.

Controller Link Unit

Constant data exchange (sharing)

Used for simple data link processing. Data link can be performed by simply set-ting parameters in the DM area of the PC.Send data size per node is the same for all nodes. All nodes participating in thedata link share the same data.

Used for flexible data link processing depending on each system.Using the Controller Link Support Software, individual data link tables can be setfor each node and the data link area can be freely allocated for each node. Senddata size per node can be freely set. It is also possible to set nodes for only sendor receive data. With the Controller Link Unit, the data link can be set to receiveonly a part of the data link area of other nodes.

Message ServiceThis function controls data transmission with particular nodes, reading or writingof status data, changing of operation modes, etc., by executing communicationsinstructions on a program. The communications instructions include SEND/RECV instructions for data transmission and CMND instructions for issuing vari-ous commands.


Data transmission (under certain conditions)as required

User program

Communications instruction

The SEND or RECV instruction sends or receives data in an area of a particularnode.The SEND instruction sends data from an area of the local node and writes to anarea in the designated node.The RECV instruction requests the designated node to send area data andwrites the data to the local node.

The CMND instruction issues a command to read or write data of other nodes,control, or read error logs. With the Controller LInk Unit, OMRON’s commandprotocol called “FINS commands” is used.

RASRAS performs real-time monitoring of the network status. If an error occurs in thenetwork, RAS records and displays the time and contents of the error.

Data Link Status AreaWhen the data link function is used, the data link status is reflected in the datalink status area of the PC.

Automatic Setting

Manual Setting

SEND/RECV

CMND

Status Area

1-1SectionOverview

5

Network Status Area Other than the Data LinkThe network status such as the state of node participation is reflected in the sta-tus area of the PC.


CPU Unit

Status Area

• Data link status

• Status other than the data link

CPU Unit


The error log function records contents (codes) and times of errors that occur inthe network into the RAM or EEPROM, up to the maximum of 39 errors.

The recorded errors can be read using the Controller Link Support Software orthe message service function.


CS1-seriesCPU Unit

Error log table

CVM1, CV-series CPUUnit


Data communications can be continued by bypassing the node, even when anode in the communications line malfunctions or the PC or IBM PC/AT or com-patible computer power supply is turned OFF. This prevents the whole networksystem from being affected by a node malfunction or power interruption.

To use the bypass node function, backup power must be supplied to the Control-ler Link Unit/Support Board.

Power interruption

Optical transmission path

Bypass

IBM PC/AT or compatible computer

Backup power supply (24 VDC)

In the token-ring mode in an Optical Ring System (H-PCF cable), data transmis-sion will be unaffected even by a cable or connector break at one location in thering connection. With the fiber-optic cable wired in a ring shape, a break at onepoint will simply cause the transmission to be routed in the other path.

Even with transmission path duplication, the network will be broken if disconnec-tions occur in two or more places. In the token-ring mode in an Optical Ring Sys-tem (H-PCF cable), the location of a disconnection can be detected and can beidentified by means of the status display for all nodes. This function can be usedto prevent system crashes in advance, by performing maintenance when a dis-connection occurs at one place.

In the token-ring mode in an Optical Ring System (H-PCF cable), connectiondata can be read for all of the nodes configured in the network. The information

Error Log

Node Bypass

Transmission PathDuplication

Disconnect Detectionand Notification

Node ConnectionConfiguration DataReading

1-1SectionOverview

6

that can be read includes the order in which the nodes are connected and whichof two optical connectors is connected to which node. Special support software(Controller Link Support Software, Ver. 2.00 or later) is required in order to readthe node connection configuration data.

1-1-2 FeaturesThe Controller Link Network has the following features to meet the variousrequirements of FA sites.

Data LinksFlexible and efficient data links can be created for large capacities of data aslisted below.

Item Specifications

Number of send wordsper node

1,000 max.

Number of send andreceive words per node

FA computer: 32,000 max.

CVM1, CV-series PCs: 8,000 max.

CS1-series PCs: 12,000 max.

Data links can be automatically set, or they can be set by the user to freelychange the sizes of the data areas used. A data link can also be created so thatone node receives only part of the data sent from another node. This functionenables users to receive only the required data, thereby increasing data link effi-ciency.

Message ServiceThe message service can send and receive up to 2,012 bytes of data (includingthe FINS header), allowing high volumes of data to be sent and received withouthaving to split it up.

Twisted-pair Cable or Optical Fiber Cable ConnectionThe Controller Link Units can be connected to the network using either shieldedtwisted-pair cables or fiber-optic cables. Select the system that suits yourapplication.

Features of Optical Fiber Cable (CS1 Series Only)Optical Fiber Cable has superior noise resistance, so this system can providehighly reliable communications even in very noisy conditions.

The communications distance can be up to 20 km in total (1 km max. betweennodes), which allows long-distance or large-scale networks.

Once the Optical Fiber Cable has been fitted with special connectors, the cablescan be easily connected or disconnected.

Features of Twisted-pair CableTwisted-pair cable is easy to connect and maintain. The cable can be processedmuch more easily than coaxial or fiber-optic cable, thereby reducing the cost oftools and assembly time.

Connections are made to a terminal block on the Controller Link Unit and to aspecial connector on the Controller Link Support Board for easy system assem-bly and modification.

The network is equipped with the required terminating resistance built into theUnits allowing the terminating resistance to be easily set at both ends of the net-work using a simple switch.

1-2SectionSpecifications and Configurations

7

Compatibility with Different Node ConfigurationsThe following Controller Link Units are available for communications betweendifferent models.

Optical Ring System (H-PCF Cable)

• Controller Link Units for CS1-series Programmable Controllers

• Controller Link Units for CVM1 and CV-series Programmable Controllers

Optical Bus System

• Controller Link Units for CS1-series Programmable Controllers

• FA computers

Flexible Inter-network ConnectionsThe Controller Link Network can connect to other networks (Ethernet, SYSMACNET, SYSMAC LINK, and another Controller Link network) via CVM1, CV-se-ries, or CS1-series PCs. By installing a Communications Unit for the Ethernet,SYSMAC NET or SYSMAC LINK on the same CS1-series or CV series-PC as aController Link Unit, a message service can be created with nodes in intercon-nected networks through the CVM1 or CV-series PC. Up to three network levelsare possible.

Note CS1-series PC cannot be installed on SYSMAC NET and SYSMAC LINK net-works.

The programming and monitoring of other PCs on the network can be conductedfrom Programming Devices connected to the PC’s CPU Unit. Inter-network con-nections are possible in this case also and can cover up to three network levels.

Improved Error HandlingAn error log enables quick handling of errors by recording the time the erroroccurred and error details. The current Controller Link Unit and Support Boardstatus are also available, as are the data link and network status.

When an error occurs in the polling node that controls the Controller Link Net-work, another node automatically becomes the polling node. This prevents anerror at a single node from influencing other nodes on the network, achieving ahighly reliable system.

In the token-ring mode in an Optical Ring System (H-PCF cable), data transmis-sion will be unaffected even by a cable or connector break at one location in thering connection. Also, with the disconnect detection and notification function, thelocation of a disconnection can be checked, making it possible to prevent sys-tem crashes in advance by facilitating inspection and maintenance.

1-2 Specifications and Configurations

1-2-1 System Configuration

A single Controller Link Network is configured as shown in the following dia-gram.


8

Optical Bus or Optical Ring System (H-PCF Cable)Token-ring Mode






CS1-series PC CVM1 or CV-series PC

CVM1 or CV-series PCCS1-series PC

H-PCF Optical Fiber Cable (ring connection)

Maximum transmission distance: 20 km(Between nodes: 1 km for adhesive)Maximum number of nodes: 62*Transmission speed: 2 Mbits/s

*Only when Controller Link SupportSoftware (Ver. 2.00 or later) isused. Limited to 32 nodes (nodeaddresses 1 to 32) when CX-Net isused (in CX-Programmer).

CPU

CPU

CPU

CPU

Token-bus Mode




3G8F5-CLK11Controller Link Support Board


CS1-series PC CS1-series PCCVM1 or CV-seriesPC


H-PCF Optical Fiber Cable (daisy-chain connection)

Maximum transmission distance: 20 km (Between nodes: 1 km for adhesive)

Maximum number of nodes: 62*Transmission speed: 2 Mbits/s

*Only when Controller Link Support Soft-ware (Ver. 2.00 or later) is used. Limited to32 nodes (node addresses 1 to 32) whenCX-Net is used (in CX-Programmer).

1-2-2 ModelsType Name Model number Transmission format

Token ring Token busOptical Ring(H-PCF

Controller Link Unitfor CS1-series PCs

CS1W-CLK12 Selectable (See note 1.)

cable) Controller Link Unitfor CVM1 orCV-series PCs

CVM1-CLK12 Selectable (See note 1.)

Optical Bus Controller Link Unitfor CS1-series PCs

CS1W-CLK11 No Yes

FA computer

Controller LinkSupport Board

3G8F5-CLK11 No Yes


9

Note 1. The transmission format is selected by means of software switches in theDM Area parameters.

2. For details on the CS1W-CLK11 Optical Bus Controller Link Unit, refer toAppendix C CS1-series Optical Units.

1-2-3 General SpecificationsGeneral specifications are the same for the CS1-series, CVM1, and CV-seriesPCs.

1-2-4 Communications SpecificationsOptical Ring System

Items Specifications

Type Optical Ring (H-PCF cable)

Communications method N:N token-ring method (token-ring mode)N:N token-bus method (token-bus mode)

Code Manchester code

Modulation Baseband code

Synchronization Flag synchronization (conforms to HDLC frames)

Transmission path format Ring method (token-ring mode)Daisy-chain method (token-bus mode)

Transmission speed 2 Mbps

Maximum transmissiondistance

20 km

Maximum distancebetween nodes

Crimp cut: 800 m Adhesive: 1 km (See note 1.)

Medium H-PCF cable (optical two-core cable)

Node connection method Connected via a special (full-lock connector) connector. (A half-lock connector can also beused.)

Maximum number ofnodes

62 nodes (See notes 2 and 3.)

Applicable ProgrammingDevices

Controller Link Support Software (Ver. 2.00 or later) and CX-Net in CX-Programmer (See note 3.)

Communications functions Data links and message service

Number of data link words Transmission area per node: 1,000 words max.

Data link area (send/receive) that can be created for one CVM1 or CV-series PC: 8,000 words max.

Data link area (send/receive) that can be created for one CS1-series PC: 12,000 words max.

Number of data link words that can be used in one network (total transmission):32,000 words max.

Data link areas Bit areas (CIO, AR, LR), DM, EM (See note 4.)

Message length 2,012 bytes max. (including the header)

RAS functions Polling node backup function

Self-diagnosis function (hardware checking at startup)

Echoback test and broadcast test (using the FINS command)

Watchdog timer

Error log function

Node bypass function

Transmission path duplication (For ring method in token-ring mode only.)

Disconnect detection and notification (Token-ring mode only.)

Node connection configuration data reading (For ring method in token-ring mode only.)

Error control Manchester code check

CRC check (CCITT X16 + X12 + X5 + 1)


10

Note 1. The maximum distance between nodes depends on the connector andcable processing methods.

2. With the token-bus method, the maximum number of nodes in an OpticalBus System (i.e., Controller Link Unit model numbers ending in CLK11) withnodes is 32 (node addresses 1 to 32).

3. CX-Net in CX-Programmer can be used in systems with up to 32 nodes(node addresses 1 to 32). Use Controller Link Support Software (Ver. 2.00or later) for systems with up to 62 nodes (node addresses 1 to 62). Refer toAppendix A Standard Models for information on CX-Net.

4. CS1-series, CVM1, and CV-series PCs do not have an LR Area, and wordsLR000 to LR199 are automatically converted to CIO 1000 to 1199 for use.


11

1-2-5 Controller Link Unit Models and PCs

Optical Bus or Optical Ring System (H-PCF)

Item Specifications

Type Optical Bus Optical Ring (H-PCF)

Model CS1W-CLK11 CS1W-CLK12 CVM1-CLK12

Externalappearance

Installationdevices

--- --- ---

ApplicablePC

CS1-series PCs CS1-series PCs CVM1 and CV-series PCs

Max No. ofUnits perPC

CPU Backplane

CS1 ExpansionBackplane

2/3/5/8/10 slots

3/5/8/10 slots

CPUUnit

Of these slots,installation ispossible in up to4 slots.

4 maximum including other types. 4 maximum including other types

CPU Backplane

CS1 ExpansionBackplane

2/3/5/8/10 slots

3/5/8/10 slots

CPUUnit

Of these slots,installation ispossible in upto 4 slots.

4 maximum including other types.

CPU Backplane

Expansion CPUBackplane

3/5/10 slots

11 slots

CPUUnit

Of these 14, 16,or 21 slots,installation ispossible in up to4 slots.

Installationposition

Install onto a CPU Backplane orCS1 Expansion Backplane(Classified as a CS1 CPU BusUnit.)



Weight 199 g (Not including fittings.) 246 g (Not including fittings.) 437 g (Not including fittings.)

Currentconsump-tion

470 mA 520 mA 520 mA

Note When connecting an FA computer (mounted to a Controller Link Support Board)to an Optical Ring Controller Link Unit (CS1W-CLK12 or CVM1-CLK12), the to-ken-bus mode must be set at the Optical Ring Controller Link Unit, and the trans-mission path must be connected by the daisy-chain method.


12

1-2-6 Devices Required for ConnectionTo set up a Controller Link Network the following devices are needed in additionto a Controller Link Unit and a PC.

Communications CablesThe following devices are required for the Optical Bus or Optical Ring (H-PCF)Controller Link Network. The cable and connectors are the same as those usedfor Optical SYSMAC LINK Networks.Optical Fiber CablesUse the following Optical Fiber Cables (Hard Plastic-clad Fiber: H-PCF).

Name Specifications Model

H-PCF cables Black 10 m S3200-HCCB101

50 m S3200-HCCB501

100 m S3200-HCCB102

500 m S3200-HCCB502

1,000 m S3200-HCCB103

Orange 10 m S3200-HCCO101

50 m S3200-HCCO501

100 m S3200-HCCO102

500 m S3200-HCCO502

1,000 m S3200-HCCO103

Note The Optical Fiber Cable model numbers are as follows.

S3200-H

Tensioner optionNone: Standard (with tension member)N: Without tension member

Cable length

A B(A/10) x 10B m

Cable colorB: BlackO: Orange

Cable specificationL: With power supply lineC: Without power supply line

TypeB: CordC: Cable

Name Model SpecificationsConnector S3200-COCF2011 Use to connect a cable to a node.

(Full-lock connector for crimp-cut cable.)

S3200-COCF2511 Use to connect a cable to a node.(Half-lock connector for crimp-cut cable.)

Inline Adapter S3200-COIAT2000 Use to connect or extend cables.(Use one adapter for each connection.)

Note 1. Either full-lock or half-lock connectors can be used in a Controller Link Net-work, but we recommend full-lock connectors to prevent accidental discon-nections during operation.

2. The maximum distance between nodes is slightly shorter for connectorswith crimp-cut cables compared to connectors assembled with adhesive.Also, the maximum distance is reduced due to extension loss when InlineAdapters are used to extend cables.

Optical Bus or OpticalRing System (H-PCFCable)


13

Optical Fiber Cable with ConnectorsThe following Optical Fiber Cables are available with Connectors alreadyattached.

Specifications Length Model

Optical Fiber Cable Connectors: 2 m S3200-CN201-20-20

S3200-COCF2011⇓

5 m S3200-CN501-20-20S3200-COCF2011⇓ 10 m S3200-CN102-20-20

S3200-COCF201115 m S3200-CN152-20-20

20 m S3200-CN202-20-20

Over 20 m S3200-CN-20-20(Specify length (m) when ordering.)


S3200-COCF2011⇓

5 m S3200-CN501-20-25S3200-COCF2011⇓ 10 m S3200-CN102-20-25

S3200-COCF251115 m S3200-CN152-20-25

20 m S3200-CN202-20-25



S3200-COCF2511⇓

5 m S3200-CN501-25-25S3200-COCF2511⇓ 10 m S3200-CN102-25-25

S3200-COCF251115 m S3200-CN152-25-25

20 m S3200-CN202-25-25


Note 1. The cables listed above are black and have power supply lines and tensionmembers, although the power supply lines aren’t used in the Controller LinkNetwork.

2. All of the cables listed above are attached to the connectors with adhesive.

3. Special training is required to assemble Optical Fiber Cables and connec-tors with adhesive.

Optical Fiber Cable AccessoriesUse the following accessories to assemble and test Optical Fiber Cables.

Name Model Specifications

Optical FiberAssembly Tool

S3200-CAK1062 Crimp-cut tool for theS3200-COCF2011/2511 Connectors

Optical Power Tester S3200-CAT2700 With S3200-CAT2702 Head Unit andadapter for theS3200-COCF2011/2511 Connectors

Master Fiber Set S3200-CAT2001H One meter cable for use with theS3200-CAT2702 Head Unit

This manual does not provide details on Optical Fiber Cable preparation. Fordetails, refer to the instructions provided with the S3200-CAK1062 AssemblyTool.


14

1-2-7 Programming DevicesA Programming Device for the PC, the Controller Link Support Software, or CX-Programmer are needed to use a Controller Link Network.

Programming Device for the PCOne of the following Programming Devices is necessary when using the auto-matically setting data links or the message service.

Software switches (DM Area)

Controller Link

Start-up node CPU Unit

or

ProgrammingConsole

SYSMAC SupportSoftware

+


The following operations are possible.

• Selecting manual or automatic setting for data links.

• Setting the data link mode to “automatic” (software switch setting).

• Starting/stopping data links (Start Bit: ON/OFF)

• Programming for the message service.

• Reading (monitoring) the network status.

ProgrammingDevice

Externalappearance

Model number Applicable PCs

CX-Programmer(for PC)

WS02-CXP-E CS1-series,C200HX/HG/HE,CVM1-series, andCQM1H-series PCs

SYSMAC SupportSoftware (for PC)

C500-ZL3AT1-E C200HX/HG/HE andCVM1 PCs

CV SupportSoftware (for PC)

CV500-ZS3AT1-EV2 CVM1 andCV-series PCs

SYSMAC-CPT (forPC)

WS01-CPTB1-E C200HX/HG/HE andCVM1 PCs

ProgrammingConsole

CQM1-PRO01-EC200H-PRO27-E

C200HX/HG/HE,C200H/C200HS,CQM1, andCQM1H-series PCs

CVM1-PRS21-EV1 CVM1 andCV-series PCs


15

Controller Link Support Software (Ver. 2.00)The Controller Link Support Software can be used to manually set data links, toset Controller Link parameters, and to monitor the Controller Link Network. TheController Link Support Software is run on a personal computer connected to aC200HX/HG/HE, CVM1, or CV-series PC or a personal computer in which aController Link Support Board has been mounted. (The Controller Link SupportSoftware cannot be used on a computer connected directly to a CS1-series PC.)The following operations are possible.

• Setting the data link mode to “manual” (creating and storing data link tables).

• Starting/stopping data links.

• Reading (monitoring) network status.

• Reading error logs.

• Setting routing tables.

• Testing the network.

• Changing network parameters.

• Reading the network connection configuration data and status (in token-ringmode only).

Controlling the Network with a Programming Device on a Computer

NodesControllerLink Unit

CPU Unit

+

CS1-series PCs


CPU Unit

CVM1 and CV-series PCs

Transmission

Setting data link tables

Controller LinkSupport SoftwareIBM PC/AT or

compatible

Note The Controller Link Support Software (Ver. 2.00 or later) can be used as a part ofthe SYSMAC Support Software.


16

Controlling the Network Using a Computer as a Node

IBM PC/AT or compatible

+

Controller LinkSupport Software



Software Externalappearance

Model number Applicable PCs Remarks

ControllerLink Support

Purchasedseparately

C200HW-ZW3AT2-E-V2 CS1-series,C200HX/HG/HE,

For IBM PC/AT orcompatible

Software(Ver. 2.00 orlater)

Provided withController LinkSupport Board

3G8F5-CLK11-E CVM1, CV-series, orCQM1H-series PC

For IBM PC/AT orcompatible (includedwith the SupportBoard)

The Controller Link Support Software can also be used with the Controller LinkSupport Board.

Controller Link Support Software (Ver. 1.10) is included with the Controller LinkSupport Board.

Controller Link Support Software (Ver. 2.00) Menu Overview

Edit PC ID

Data LinkMenu items: Edit table

Set Network parameters Copy table

Routing tables Initialize table

Echoback test Check table

Broadcast test

Monitor Network

Display Error log

Display Node status

Display Board setup

Maintenance

Connection configuration data

Unit backup

Board backup

Initialize network parameters

Save table

Retrieve table

Transfer table

Delete table

Print table

Start/Stop

Monitor status

Device info set

System setup

Note Refer to the Controller Link Support Software Operation Manual (W308) fordetailed operating procedures.


17

CX-Net in CX-Programmer can be used for the following applications in a sys-tem with up to 32 nodes (node addresses 1 to 32).

• Setting the data link mode (creating and storing data link tables).

• Starting/stopping data links.

• Reading (monitoring) network status.

• Reading error logs.

• Setting routing tables.

• Testing the network.

• Changing network parameters.

Note 1. CX-Net in CX-Programmer can be used only in systems with a maximum of32 nodes (node addresses 1 to 32). For systems with more than 32 nodes,use Controller Link Support Software (Ver. 2.00 or later).

2. For details on CX-Net in CX-Programmer, refer to the CX-Programmer Op-eration Manual.

Controlling the Network with a Programming Device on a Computer


CPU Unit

+ NodesControllerLink Unit

CPU Unit


Transmissions


CX-Net inCX-Programmer

RS-232CIBM PC/AT orcompatible

CS1-series PCs

This configuration is possible only in Token Bus Mode.

IBM PC/AT or compatible

+




Software Externalappearance

Model number Applicable PCs

CX-Programmer(including CX-NET)

WS02-CXP-E CS1-series, CVM1,CV-series, PCs


Controlling the NetworkUsing a Computer as aNode

1-3SectionSelecting Communications Functions

18

1-2-8 Backup Power SupplyThe node bypass function can be used if each Controller Link Unit and Board isconnected to a backup power supply. The node bypass function prevents theentire network from shutting down if the power supply to a single PC or personalcomputer is interrupted.

Optical transmission path

Bypass

Computer

Power interruption

24-VDCbackuppower supply

The following table shows the input specifications required for backup powersupplies to Controller Link Units and Boards. Be sure that the backup power sup-ply being used meets these specifications. (We recommend the OMRON S82KSeries.)

Item Specification

Voltage 24 VDC

Allowed voltage fluctuation 20.4 to 26.4 VDC (24 VDC –15% to +10%)

Current consumption 200 mA max. at 24 VDC (per node)

Inrush current 2.5 A max. (with a 24-VDC startup time of 5 ms)

When a single power supply is connected to several nodes or is some distanceaway from the node, make sure that the voltage at the node itself meets thespecifications in the table above. There will be some voltage drop in the powersupply wiring.The power provided from the backup power supply will be used first if a backuppower supply is connected. Be sure to consider the following points whendesigning the network.

1, 2, 3... 1. Turn on the PC or computer power supply after turning on the backup powersupply.

2. If the backup power supply goes on or off, any data being transmitted at thatmoment will be corrupted.

3. Do not use the same power source to supply the backup power supply andthe PC/computer. The node bypass function will not operate if the backuppower supply and the PC/computer are both off.

4. Use a dedicated power supply for the backup power supply. Do not share apower supply being used for I/O, motors, or control systems.Use a backup power supply that is double-insulated or one with reinforcedinsulation.

Always maintain the power supply voltage within specifications.

1-3 Selecting Communications FunctionsSelect the data link function if alarm or status data (in bits) must be constantlyshared between PCs or between a PC and an IBM PC/AT or compatible comput-er or if the present value or set value data (in words) must be constantly sharedbetween PCs or between a PC and an IBM PC/AT or compatible computer.Select the message service function (SEND/RECV instructions or CMNDinstructions) if data (in words) must be sent (or received) from one PC to otherPCs in other nodes or from one PC to IBM PC/AT or compatible computers.

Backup Power SupplySpecifications

1-4SectionBasic Procedures

19

1-4 Basic ProceduresCVM1, CV-series, and CS1-series PCs

1, 2, 3... 1. Set the Unit number on the front rotary switches.

• 00 to 15 (0 to F: CS1-series display is in hexadecimal)

2. Set the node address on the front rotary switches.

• 01 to 62

3. Set the transmission path format using software switches in the DM param-eters area.

• Token-ring mode or token-bus mode

Note This setting is made for Optical Ring Controller Link Units only. (It isnot required for Optical Bus Systems because the token-bus mode isalways used.)

4. Register routing tables.

Data Link Procedure

1, 2, 3... 1. Connect power to all nodes.

2. Connect the Programming Device to the PC.

3. Create I/O tables

4. Set the data link mode in the data link parameters in the DM area of thestartup node to either automatic or manual data link creation using the Pro-gramming Device.

Manually Setting Data Links

1, 2, 3... 1. Register data link tables for all nodes using the Controller Link Support Soft-ware or CX-Programmer.

2. Start the data links either using the Controller Link Support Software, CX-Programmer, or by turning ON the Start Bit from the Programming Device.

Automatically Setting Data Links

1, 2, 3... 1. Set the DM area of the startup node using the Programming Device.

2. Start the data links by turning ON the Start Bit from the Programming De-vice.

Message Service Procedure

1, 2, 3... 1. Turn ON the power.

2. Create I/O tables

3. Execute communications instructions in the program.

Preparations

1-5SectionApplication Precautions

20

1-5 Application Precautions• CX-Net in CX-Programmer can only be used in systems with a maximum of 32

nodes (node addresses 1 to 32). For systems with more than 32 nodes, useController Link Support Software (Ver. 2.00 or later).

• Turn OFF the power of all the nodes on the network before connecting or dis-connecting a cable.

• Use the specified cable only.• Be sure to set routing tables for CVM1 and CV-series PCs. When a CVM1 or

CV-series PC is connected to the network, set routing tables at all the nodes.

CLK

Routing tables are necessary

at all the nodes.

CLK: Controller Link Unit

CLK

CLK

CS1

CS1

CVM1

Note Routing tables are not required if all of the CVM1 and CV-series CPU Units if theController Link Network were manufactured on or after May 1996.

CLK

Routing tables notnecessary

CLK

CLK

Independent Controller Link Network

Manufactured after May 1996 Manufactured after May 1996

CS1

CVM1

CVM1

Note The manufacturing date can be determined from the four-digit lot number on theside of the CPU Unit.

Lot No.: 5 6 Manufactured in May 1996. . . . .

Indicates the last digit of the manufacturingyear. In this example, the year is 1996.

Indicates the month of manufacture. October,November, and December are indicated by x, y,and z respectively. In this example, the month isMay.

• Set routing tables at all the nodes in all the networks when multiple networksare connected.

CS1

CLK

CLK

CLK

CLK

Controller Link Network 1

CLK

CS1

CLK

CLK

Controller Link Network 2

Routing tables are necessary at all the nodes.

CS1

CS1

CVM1

• When using the SEND/RECV or CMND instructions on a PC for which routingtables have been set, be sure to specify the network addresses that are set inthe routing tables.

• When using manually set data links, delete the data link tables from all nodesnot participating in the data links.

• Do not transfer (write) routing tables when data links are active (i.e., started).CPU Bus Units and Communications Units are reset when routing tables aretransferred.

• Do not restart or reset the polling node while data links are active.• When an Optical Ring System is used, the same transmission path format set-

tings must be made for all of the nodes. The network cannot be set up correctlyif these settings are different.

1-5SectionApplication Precautions

21

• When Optical Bus (CLK11) and Optical Ring (H-PCF cable) (CLK12) Control-ler Link Units are used in combination, the transmission path format for all ofthe Optical Ring Controller Link Units must be set to token-bus mode. The net-work cannot be set up correctly if the mode settings are different.

• When Optical Bus (CLK11) and Optical Ring (H-PCF cable) (CLK12) Control-ler Link Units are used in combination, all of the node addresses must be withinthe range of 1 to 32.

• When Optical Bus (CLK11) and Optical Ring (H-PCF cable) (CLK12) Control-ler Link Units are used in combination, the software switch at the Optical RingController Link Units for selecting either polling node or normal node must beset for normal node. If the Optical Ring Controller Link Unit nodes are set forpolling when the network is started up, then the maximum node address in thenetwork parameters will be set to 62, and a network parameter error (ERH indi-cator lit) will be generated at the Optical Bus Controller Link Unit nodes. If thisoccurs, use the Controller Link Support Software (Ver. 2.00 or later) to set themaximum node address to 32.

• When wiring using the ring method, it is recommended that the nodes be con-nected in order (node 1 → node 2... → node 62 → node 1) to minimize the ef-fect on communications time when a disconnection occurs. For details oncommunications time, refer to 8-2 Communications Cycle Time.

23

SECTION 2Basic Procedures

This section describes the basic procedures for using the Controller Link Unit. The settings required for each of the functionsare also explained briefly. For more details, refer to the subsequent sections on individual functions.

2-1 Data Links Procedures 24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1-1 Manually Setting Data Links 24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1-2 Automatically Setting Data Links 26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-2 Message Service Procedure 28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-1SectionData Links Procedures

24

2-1 Data Links Procedures2-1-1 Manually Setting Data Links

When the data link mode is set for manual data link table creation, the data linktables can be input using the Controller Link Support Software or CX-Program-mer. Use the following procedure.

1, 2, 3... 1. Install and wire the Units.

Contents Method Nodes Page

a. Mount the Units tothe PCs.

--- All nodes 36

b. Wire the Network. --- All nodes 38

2. Prepare for communications.


a. Set the unitnumber.

Use the front rotaryswitches.

CS1-series, CVM1,and CV-series PCsonly

45, 48

b. Set the nodeaddress.


All nodes 46, 49

3. Turn ON the power to the PC.


Turn ON the power tothe PC.

--- All nodes ---

4. Connect the Programming Device.


Connect theProgrammingConsole or ControllerLink SupportSoftware.

Use the specialconnection cable.

CVM1 and CV-seriesPCs

14

5. Create I/O tables.


Input the I/O tables. Use the SYSMACSupport Software orProgrammingConsole.


---

6. Set the software switches.


Transmission pathformat setting

By ProgrammingDevice for PC,including ProgrammingConsole. (See note a.)

All nodes. 46, 49

Data linkmanual/automaticsetting

By ProgrammingDevice for PC,including ProgrammingConsole. (See note b.)

Data link startup nodeonly.

Note: The node thatstarts the data link iscalled the “startupnode.” The startup nodemust be determined inadvance.

57

Data link statusstorage methodsetting

By ProgrammingDevice for PC,including ProgrammingConsole. (See note c.)

All nodes. 81


25

Note a) In token-ring mode, confirm that the relevant setting location in theDM parameters area is 00.

b) For manual settings, confirm that the relevant setting location inthe DM parameters area is 00.

c) For the 8-bit storage method, confirm that the relevant settinglocation in the DM parameters area is 00.

d) When Optical Bus (CLK11) and Optical Ring (CLK12) ControllerLink Units are used in combination, the software switch at the Op-tical Ring Controller Link Units for selecting either polling node ornormal node must be set for normal node.

7. Register the data link tables by making the following settings for each node.


First data link status word Use the Controller All nodes within the 59

Data link nodes Link Support network

Area1

First data linkstatus words

Software orCX-Programmer.

Delete from the datalink tables all nodes

Numbers of datalink words

that are not in a datalink.

Data link offsets

Area2

First data linkstatus words

Numbers of datalink words

Data link offsets

Note Offsets are used to control where data is placed within the receivearea.

8. Start the data links.


Start the data links. Switch the Data linkStart/Stop Bit (listedbelow) from OFF toON using either theProgramming Device,the user program, theController LinkSupport Software orCX-Programmer.

Data link startupnode

(The Start Bit can beturned ON in morethen one node tomake sure the datalinks start even whenthe startup node isdown.)

75

Note a) Data link Start/Stop Bit (N= unit number):CS1 Series: Word 0 of DM30000 + 100 NCVM1/CV Series: Word 0 of DM 2000 + 100 N

b) The data links will not start if there is an error in the data link tablesin the startup node.

9. Stop the data links.


Stop the data links. Switch the Data linkStart/Stop Bit (listedbelow) from OFF toON using either theProgramming Device,the user program, theController LinkSupport Software orCX-Programmer.

Any node that isactive in the data link

75


26

Note Data link Start/Stop Bit (N= unit number):CS1 Series: Word 0 of DM30000 + 100 NCVM1/CV Series: Word 0 of DM 2000 + 100 N

2-1-2 Automatically Setting Data LinksData link tables can be automatically created by setting the data link mode toautomatic data link table creation. Use the following procedure.



a. Mount the Units tothe PCs.

--- All nodes 36

b. Wire the Network. --- All nodes 38



a. Set the unitnumber.



45, 48

b. Set the nodeaddress.


All nodes 46, 49



Turn ON the power tothe PC.

--- All nodes ---

4. Connect the Programming Device.


Connect theProgrammingConsole or ControllerLink SupportSoftware.

Use the specialconnection cable.


14

5. Create I/O tables.


Create the I/O tables. Use the SYSMACSupport Software orProgrammingConsole.


---

6. Set the software switches.


Transmission pathformat setting

By ProgrammingDevice for PC,including ProgrammingConsole. (See note a.)

All nodes. 46, 49

Data linkmanual/automaticsetting

By ProgrammingDevice for PC,including ProgrammingConsole. (See note b.)

Data link startup nodeonly.

Note: The node thatstarts the data link iscalled the “startupnode.” The startup nodemust be determined inadvance.

57

Data link statusstorage methodsetting

By ProgrammingDevice for PC,including ProgrammingConsole. (See note c.)

All nodes. 81


27

Note a) In token-ring mode, confirm that the relevant setting location in theDM parameters area is 00.

b) For the 8-bit storage method, confirm that the relevant settinglocation in the DM parameters area is 00.

c) When Optical Bus (CLK11) and Optical Ring (CLK12) ControllerLink Units are used in combination, the software switch at the Op-tical Ring Controller Link Units for selecting either polling node ornormal node must be set for normal node.

7. Set the parameters for automatic data link creation.

Contents Method Nodes PageArea a. Set the area Set at the PC for Data link startup 691 b. Set the data

link start word

the startup node,by Programming

node only

Only when Area 1 isc. Set the no. of

data link words

Device for PC(including

Only when Area 1 isused

Area d. Set the areaProgrammingConsole). Data link startup

2 e. Set the datalink start word

Console).node only

Only when Area 2 isf. Set the no. of

data link words

Only when Area 2 isused

g. Set the first data linkstatus word

Data link startupnode only

(This setting may beomitted.)

h. Set the nodes toparticipate in the datalinks.

Data link startupnode only

8. Start the data links.


Start the data links. Switch the Data linkStart/Stop Bit (listedbelow) from OFF toON using either theProgramming Device,or the user program.

Data link startupnode

(The Start Bit can beturned ON in morethen one node tomake sure the datalinks start even whenthe startup node isdown.)

75

Note Data link Start/Stop Bit (N= unit number):CS1 Series: Word 0 of DM30000 + 100 NCVM1/CV Series: Word 0 of DM 2000 + 100 N

9. Stop the data links.


Stop the data links. Switch the Data linkStart/Stop Bit (listedbelow) from OFF toON using either theProgramming Device,or the user program.

Any node that isactive in the data link

75

Note Data link Start/Stop Bit (N= unit number):CS1 Series: Word 0 of DM30000 + 100 N CVM1/CV Series: Word 0 of DM 2000 + 100 N

Note The data links will not start if there is an error in the data link tables inthe startup node. Data links can be started and stopped using theController Link Support Software.

2-2SectionMessage Service Procedure

28

2-2 Message Service ProcedureThe following steps outline the basic procedure for using the message service.


Contents Remarks Page

a. Mount the Units to the PCs. --- 36

b. Wire the Network. --- 38



a. Set the unit number. --- 45, 48

b. Set the node address. --- 46, 49



Turn ON the power to the PC. --- ---

4. Create the I/O tables.


Create the I/O tables. --- ---

5. Register routing tables if using inter-network connections.


a. Set the local network table --- 132

b. Set the relay network table ---

Lot No.: 4 6 Manufactured in April 1996. . . . .


Indicates the month of manufacture. October,November, and December are indicated by x, y,and z respectively. In this example, the month isApril.

Note Routing tables are required if any of the CVM1 and CV-series CPU Unitsin the Network has been manufactured on or before April 1996.

6. Set the software switch.


Transmission path format setting(See note a.)

46, 49

Note a) This setting is made by means of a Programming Device (includ-ing the Programming Console) for the PC. In token-ring mode,confirm that the relevant setting location in the DM parametersarea is 00.

b) When Optical Bus (CLK11) and Optical Ring (CLK12) ControllerLink Units are used in combination, the software switch at the Op-tical Ring Controller Link Units for selecting either polling node ornormal node must be set for normal node.

2-2SectionMessage Service Procedure

29

7. Create the user program.


a. Prepare the send and receivedata in memory.

Stored in the memory areas ofthe source node

84

b. Prepare the control data forthe communicationsinstruction.

c. Check the conditions forexecuting the SEND/RECV orCMND instruction.

The standard input conditions arethe Active Node Flags for thesource and destination nodes,and the Port Enabled Flag.

97

d. Execute the SEND/RECV orCMND instruction.

---

e. Execute other instructions arerequired for the results of thecommunications instruction,(e.g., retry or error processingif an error occurs).

The standard input condition isthe Port Error Flags.

CVM1 and CV-series PCs have 8communications ports. When 9 ormore communicationsinstructions are executed at thesame time, exclusive control isnecessary.

31

SECTION 3Installation and Wiring

This section explains how to install a Controller Link Unit onto a CPU Backplane and how to wire the Controller Link Net-work.

3-1 Component Names and Functions 32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1-1 CS1-series Optical Ring Controller Link Units (H-PCF Cable) 32. . . . . . . . . . . . . . 3-1-2 CVM1 and CV-series Optical Ring Controller Link Units (H-PCF Cable) 34. . . . .

3-2 Installation 36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-1 CVM1 and CV-series PCs 36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2-2 CS1-series PCs 38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-3 Optical Wiring 38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3-1 Optical Fiber Cable Connections 38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3-2 Backup Power Supply Wiring 40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3-3 Connecting Optical Fiber Cable to Connectors 40. . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3-4 Connecting Backup Power Supply Cables 42. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-1SectionComponent Names and Functions

32

3-1 Component Names and FunctionsThis section describes the names and functions of the Controller Link Unit com-ponents. This section also describes the operation of the indicators.

3-1-1 CS1-series Optical Ring Controller Link Units (H-PCF Cable)

Unit number switch (Refer to p. 45.)

One rotary switch. The unit number is set in single-digithexadecimal.

Indicators (Refer to p. 35, 160.)

LED indicators that display the Unit and network status.

Node address switches (Refer to p. 46.)

Two rotary switches. The node address of the Unit on theController Link Network is set in 2-digit decimal.

Optical connectors (Refer to p. 38)

Connectors to connect to the Controller Link Network communicationscable (H-PCF Optical Fiber Cable).

Power Supply Terminal Block (Refer to p. 42)

Connect the backup battery for the node bypass function.


33

Name Color Status MeaningRUN Green Lit Unit operating normally.(operating) Not lit Unit error.

P/S Green Lit Backup power is being supplied.(power supply) Not lit Backup power is not being supplied.

ERC(communicationserror)

Red Lit Communications error, node addresssetting error, hardware error or aconnection error between the OpticalController Link Unit and SYSMAC LINK.

Not lit Normal operation

ERH (PC error)

Red Lit PC error, PC interface error, EEPROMerror, unit number error, or I/O table notset

Not lit No error.

INS (network

Yellow Lit Unit is participating (inserted) in thenetwork.

participation) Not lit Unit is not participating (inserted) in thenetwork.

SD Yellow Lit Data transmission.(send) Not lit No data transmission.

RD Yellow Lit Data reception.(receive) Not lit No data reception.

M/A (data link mode)

Yellow Data linksactive in thenetwork.

Data links not active inthe network.

Lit Manual(See note.)

Note: M/A is always not lit

Not lit Automaticwhen data links are notactive in the network.

LNK Yellow Lit Data links participating.(data link) Flashing Error in data link table.

Not lit Not in a data link or data link inactive.

RING Yellow Lit Token-ring mode setting (cable normal)(transmission pathformat)

Flashing Token-ring mode setting (cabledisconnected)

Not lit Token-bus mode setting

Note Even when the local node does not participate in the data link, theindicator will be lit if there are manually set data links active on thenetwork.

For details refer to 9-1 Troubleshooting Using Indicators.

Meanings of LEDIndicators


34

Dimensions (Unit: mm)

3-1-2 CVM1 and CV-series Optical Ring Controller Link Units (H-PCFCable)

Unit number switches (Refer to p. 48)

Two rotary switches. The unit number is set in 2-digit decimalfor the Network to which the PC is connected.

Indicators (Refer to p. 35, 160.)

LED indicators that display the Unit and Network status.

Node address switches (Refer to p. 49)


Optical connectors (Refer to 38)

For connecting the Controller Link Network communicationscables (H-PCF Optical Fiber Cable).

Power supply terminals (Refer to 42)

For connecting the backup power supply for the node bypassfunction.


35

Name Color Status MeaningRUN Green Lit Unit operating normally.(operating) Not lit Unit error.



Red Lit Communications error, node addresssetting error (same address set twice),or hardware error.


ERH (PC error)

Red Lit PC error, PC interface error, EEPROMerror, unit number error, or I/O table notset

Not lit No error.

INS (network

Yellow Lit Unit is participating (inserted) in thenetwork.

participation) Not lit Unit is not participating (inserted) in thenetwork.




Yellow Data linksactive in thenetwork.

Data links not active inthe network.

Lit Manual (See note.)

Note: M/A is always not lit

Not lit Automaticwhen data links are notactive in the network.



RING Yellow Lit Token-ring mode setting (cable normal)(transmission pathformat)


Not lit Token-bus mode setting

Note Even when the local node does not participate in the data link, theindicator will be lit if there are manually set data links active on thenetwork.


Meanings of LEDIndicators

3-2SectionInstallation

36


3-2 InstallationThe Controller Link Unit is mounted onto a CPU Backplane or Expansion CPUBackplane for use. For detailed information on PC installation procedures, referto the installation guide for the applicable PC.

Note 1. Always turn OFF power to the PC before mounting the Controller Link Unitinto the Backplane.

2. Be sure that all screws on the Backplane, the Bus Connection Unit, the ter-minal block, and cables are tightened firmly. If screws work loose, a malfunc-tion may occur as a result of vibration.

3. Do not allow scraps of wire to enter the Unit when wiring the network.

4. A label has been placed over the upper surface of the Controller Link Unit toprevent scraps of wire from entering the Unit. Conduct wiring and installa-tion with this label in place. If wire scraps get into the Unit, it will malfunction.

5. Remove the label after wiring and installing the Controller Link Unit to pre-vent overheating. Overheating will cause the Unit to malfunction.

3-2-1 CVM1 and CV-series PCsUp to four Controller Link Units for CVM1 and CV-series PCs can be installed in aCPU Backplane or a Expansion CPU Rack. Controller Link Units cannot be

3-2SectionInstallation

37

installed on an Expansion I/O Rack, a SYSMAC BUS Slave Rack, or a SYSMACBUS/2 Slave Rack.

The CVM1 and CV-series Controller Link Unit is classified as a CPU Bus Unitand must be mounted in a CPU bus slot.

Note Tighten the screws on the Backplane to a torque of 1.2 N m.Tighten the fixed screws on the CPU Unit to a torque of 0.9 N m.

CPU Rack(CV500/CV1000/CVM1D-BC051/CV2000/CVM1)The Unit can be mounted to the 3/5/10 slotsshown in the diagram on the right. (It cannotbe mounted to the leftmost slot even if anExpansion CPU Rack is not used.)

Install in four ofthese 14, 16, or21 slots.

CPU BackplaneCV500-BC101, CVM1-BC103/CV500-BC051, CVM1-BC053/CV500-BC031, CVM1D-BC05

IOC

CPU

PS

3/5/10 slots

Expansion CPU RackCV500/BI111/CVM1D-BI101

IOIF

PS

Expansion CPU RackAny of the 11 slots shown in the illustrationcan be used. The leftmost slot cannot beused.

IOIF

PS

Expansion I/O RackController Link Units cannot be mounted toExpansion I/O Racks.

11 slots

PS: Power Supply UnitCPU: CPU UnitIOC: I/O Control UnitIOIF: I/O Interface Unit

3-3SectionOptical Wiring

38

3-2-2 CS1-series PCs

Up to a total of four Controller Link Units (wired and optical) for CS1-series PCscan be installed in a CPU Backplane or a Expansion CPU Rack. Controller LinkUnits cannot be installed on an C200H Expansion I/O Rack or a SYSMAC BUSSlave Rack.

Note Tighten the screws on the Backplane to a torque of 0.9 N m.Tighten the fixed screws on the CPU Unit to a torque of 0.4 N m.

CPU RackThe Unit can be mounted to the 2/3/5/8/10slots shown in the diagram on the right.

Install in four ofthese slots.

CPU BackplaneCS1W-BC103, CS1W-BC083, CS1W-BC053, CS1W-BC033, CS1W-BC023

2/3/5/8/10 slots

CS1 Expansion Backplane

CS1 Expansion BackplaneSlots 3/5/8/10 shown in the illustration can beused.

C200 H Expansion I/O BackplaneController Link Units cannot be mounted toExpansion I/O slots.

3/5/8/10 slots

PS: Power Supply Unit

CPU: CPU Unit

CS1W-BI108, CS1W-BI083, CS1W-BI053, CS1W-BI033

C200H Expansion I/O Backplane

Note When installing several CS1 CPU Bus Units at the same time, a total of 16 CS1CPU Bus Units maximum may be installed.

3-3 Optical Wiring

3-3-1 Optical Fiber Cable Connections

All of the nodes in the network are connected in a line (daisy-chain configuration)with H-PCF Optical Fiber Cable.

The nodes can be connected in any order, but be sure to begin with the upperconnector (SL1) of the highest node in the network and connect to the lower con-nector (SL2) in the next lower node, as shown in the following diagram.

Although there is no fixed order in which the nodes must be connected, in orderto minimize the effect on communications time in the event of a disconnection, itis recommended that they be connected in order of node address (node 1 →node 2... → node 62 whenever possible).

Optical Bus and OpticalRing Systems(Token-bus Mode)


39

Also be sure to cover the unused connectors on the highest and lowest nodes inthe network with Optical Connector Covers.

Optical Connector Cover

← Higher Lower →

Optical Connector Cover

See 1-2-6 Devices Required for Connection for details on available Optical FiberCables.

Note 1. Always use the specified Optical Fiber Cables.

2. The maximum distance between nodes depends on how the cable is con-nected. For details, refer to the applicable Optical Fiber Cable (H-PCF)manual.

3. In token-bus mode (daisy-chain connection), the maximum number ofnodes in an Optical Bus System (i.e., Controller Link Unit model numbersending in CLK11) with nodes is 32 (node addresses 1 to 32).

All of the nodes in the network are connected in a ring with H-PCF Optical FiberCable.

The nodes can be connected in any order, but be sure to begin with the upperconnector (SL1) of the highest node in the network and connect to the lower con-nector (SL2) in the next lower node, as shown in the following diagram.

Although there is no fixed order in which the nodes must be connected, in orderto minimize the effect on communications time in the event of a disconnection, itis recommended that they be connected in order of node address (node 1 →node 2... → node 62 whenever possible).

← Higher Lower →

See 1-2-6 Devices Required for Connection for details on available Optical FiberCables.

Note 1. Always use the specified Optical Fiber Cables.

2. The maximum distance between nodes depends on how the cable is pro-cessed. For details, refer to the applicable Optical Fiber Cable (H-PCF)manual.

Optical Ring System(Token-ring Mode)


40

3-3-2 Backup Power Supply Wiring

Each node requires a backup power supply for the node bypass function. Sev-eral nodes can be connected to a single power supply or each node can be con-nected to an independent power supply.

Be sure that the backup power supply is providing sufficient current and voltageat the Unit’s connector. See 1-2-8 Backup Power Supply (Optical System Only)for the backup power supply specifications.

Note 1. A label has been placed over the upper surface of the Controller Link Unit toprevent wire cuttings from entering the Unit. When wiring the backup powersupply, leave the label in place.

2. When wiring is complete, remove the label to avoid overheating.

3. Use a power supply that is not connected to PC operation, as in the case ofthe node bypass function, for the backup power supply so that when thepower to the PC is turned OFF, the backup power supply will continue.

4. Use a dedicated power supply for the backup power supply. Do not share apower supply being used for I/O, motors, or control systems.

5. When two or more nodes are connected to a single power supply, wire eachnode separately.

Power source Power source

OK Wrong

3-3-3 Connecting Optical Fiber Cable to Connectors

A special connector is used to connect the Optical Fiber Cable to the ControllerLink Unit.

This manual does not provide details on Optical Fiber Cable preparation.

Observe the following precautions when connecting the Optical Fiber Cables.

• Always turn OFF the PC power supply before connecting Optical Fiber Cables.

• Special tools are required to attach Optical Fiber Cables to the connectors.The cable may disconnect from the connector if the proper tools and methodsare not used during cable assembly.

• Insert the connectors completely and always check that the connectors arelocked before starting operation.

• If a connector becomes disconnected while in token-bus mode, the node willbe unable to communicate with other nodes in that part of the network. The


41

network will be divided into two and communications with the remaining nodeswill be unreliable. Be sure not to remove connectors during communications.

Transmissionnot possible

Isolated(Transmission not possible)

Even in token-ring mode, the network will be broken and communications maybe disrupted if disconnections occur at two or more places. Be sure not to allowconnectors to be disconnected during communications.

• Do not pull on the Optical Fiber Cable too forcefully.The maximum tension that can be applied to the cord is 10 kg and the maxi-mum tension that can be applied to the cable is 50 kg.

Cord Cable

• Do not bend the cable too sharply. The minimum radius for bends is 10 cm.

• To prevent the Optical Fiber Cable from being pulled too forcefully, always usethe cable securing bracket and provide space behind the Unit as shown in thefollowing diagram. Do not exceed the maximum tension for the cord and cable:

Cord: 0 kg (Do not apply any tension.)Cable: 5 kg

50

60

200

Cord Cable

• Do not place objects on top of the Optical Fiber Cable. The maximum pressurethat can be placed on the cord and cable is as follows:

Cord: 30 kg/10 cmCable: 50 kg/10 cm

• Inspect the connector before installing it.

Use the following procedure to connect Optical Fiber Cables to a Unit.

1, 2, 3... 1. Tighten screws in the mounting brackets so that the through-holes on theterminal are on the top and bottom and then affix hexagonal nuts from theopposite side of the terminal.

Connection Procedure


42

2. Insert bushing to the mounting bracket and secure the Unit with screws.

3. Pass the tension member through the through-holes, and tighten the termi-nal screws to affix the tension member.

4. Affix the cable to the mounting bracket so that it is clamped by the bracket.Two cables can be attached at the same time.

5. Move the cable connector so that the loose ends are on the left-hand side,and insert the Unit’s optical connector as far as it will reach.

3-3-4 Connecting Backup Power Supply CablesAttach crimp terminals to the power supply cable when connecting the backuppower supply to the Controller Link Unit.

Backup powersupply

24 VDC

Crimp TerminalsUse an M3 crimp terminal, as illustrated below.

6.2 mm max. 6.2 mm max.

Note 1. Always turn OFF the power to the PC and the backup power supply beforeconnecting the backup power supply cables.

2. Separate the backup power supply wires from other power lines and high-voltage lines to prevent noise.

3. Always use a crimp terminal for wiring. Do not connect a wire that has onlybeen twisted directly to a terminal block

4. Use recommend crimp terminals.

5. When mounting the crimp terminal, always use the appropriate tools foreach crimp terminal and follow the appropriate installation procedures. Con-tact the crimp terminal manufacturer for details on the appropriate tools andprocedures. Failure to use the appropriate tools and procedures couldcause cables to break.

6. Measure the length of peeled cable during installation according to thecrimp terminal used and make sure that the peeled length is not too long.Cover the compressed section of the crimp terminal and cable with vinyltape or heat-shrinking tube.

7. Be sure not to reverse the power supply polarity.

8. Tighten the screws on the terminal block firmly. The correct tighteningtorque is 0.5 N. If the screws are too loose, short-circuit, malfunction or burn-ing may result.

9. Do not pull backup power supply cables with excessive force.

10. Do not bend backup power supply cables.

11. Do not place any object on top of backup power supply cables.

12. Supply power only after checking the wiring thoroughly.

43

SECTION 4Preparations for Communications

This section describes the settings required for starting communications. These basic settings are required both for data linksand the message service. Carry out the settings described here before turning ON power to the Controller Link Unit.

4-1 CS1-series Optical Ring Controller Link Units 44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-1 Overview 44. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-2 Setting the Unit Number 45. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-3 Setting the Node Addresses 46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1-4 Setting the Transmission Path Format 46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-2 CVM1 and CV-series Optical Ring Controller Link Units 47. . . . . . . . . . . . . . . . . . . . . . . . . 4-2-1 Overview 47. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2-2 Setting the Unit Number 48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2-3 Setting the Node Address 49. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2-4 Setting the Transmission Path Format 49. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-1SectionCS1-series Optical Ring Controller Link Units

44

4-1 CS1-series Optical Ring Controller Link UnitsBefore starting communications, the following settings are required for an Opti-cal Ring Controller Link Unit (H-PCF cable) used with a CS1-series PC.

Item Switch Page

Unit number Unit number setting switch 45

Node address Node address switches 46

Transmission pathformat

Software switch 46

4-1-1 Overview

Unit Number

Node Address

Unit Number

Setting range Nodes

0 to F (default is 0) All nodes in the Network

Node Address

Setting range Nodes

01 to 62 (default is 01) (see note) All nodes in the Network

Note 1. CX-Net in CX-Programmer can be used in systemswith up to 32 nodes (node addresses 1 to 32). UseController Link Support Software (Ver. 2.00 or later)for systems with up to 62 nodes (node addresses 1to 62).

2. With the token-bus method, the maximum numberof nodes in an Optical Bus System (i.e., ControllerLink Unit model numbers ending in CLK11) withnodes is 32 (node addresses 1 to 32).


45

Transmission Path Format Setting (Software Switch)

Setting range Nodes

Token-ring modeToken-bus mode

All nodes in the Network

Software switch (DM30000 + 100 x unit number)

0: Always set to 0.1: According to other settings. Transmission path

Transmission Path

Bit Setting contents

9 8

0 0 Token-ring mode

0 1

1 0

1 1 Token-bus mode

4-1-2 Setting the Unit NumberSet the unit number for each Unit using the rotary switches on the front of theUnit. The unit number is used to identify a CPU Bus Unit in the PC. Any unit num-ber can be set between 0 and F in hexadecimal (00 to 15 in decimal).

0 0

Note: The factory default settings are shown above.

Item Specifications

Setting method Single-digit hexadecimal

Setting range 0 to F (decimal 00 to 15, default is 0)

Node All nodes in the Network

Set the node address using a small flat-blade screwdriver, being careful not todamage the rotary switches.

Note 1. Always turn OFF the PC’s power before setting the unit number.

2. When setting a Unit for the first time or changing the existing setting, create aI/O table in the PC’s CPU Unit.

3. Do not set the same unit number twice within the same PC. An error willoccur if the same unit number is set for two different Units, and the CPU Unitwill not be able to recognize the Units.

4. When the Unit is recognized by the PC’s CPU Unit, “NS” will be shown in theI/O table displayed at the CX-Programmer.

5. The default setting is “0.”

6. The unit number determines the DM parameter area used by the ControllerLink Unit in PC memory.


46

4-1-3 Setting the Node AddressesSet the node addresses of each Unit on the network using the rotary switches onthe front of the Unit. The node address is used to identify each node in the Net-work, and can be set to any number between 01 and 62.

1’s digit

10’s digit

Note: The default settings are shown above.

Item Specifications

Setting method 2-digit decimal

Setting range 01 to 62 (default: 01)

Node All nodes in the Network.


Note 1. Always turn OFF the PC’s power before setting the node address.

2. Do not set the same node address twice within the same network. A nodeaddress duplication error will occur if the same address is set for two differ-ent nodes. The ERC indicator on the front of the Unit will light (Communica-tions Error Flag) and either communications will stop, or the INS indicatorwill not light and the node will be unable to participate in the network.

3. The send sequence for the data link areas is determined according to thesequence of node addresses for automatically set data links.

4. Assign node addresses consecutively beginning from 01 whenever pos-sible to minimize network construction time.

4-1-4 Setting the Transmission Path FormatThe transmission path format is set by a software switch allocated in the CPUUnit’s DM parameter area. The same setting must be made for all nodes in thenetwork. Select either token-ring mode or token-bus mode by using a PC Pro-gramming Device (i.e., Programming Console, CX-Programmer, or SYSMACSupport Software) to set values for bits 9 and 8 in the software switch shownbelow.

When the transmission path format is changed, the change will not go into effectuntil the PC’s power is turned OFF and ON again or the Unit is restarted.



Transmission Path


9 8

0 0 Token-ring mode

0 1

1 0

1 1 Token-bus mode

4-2SectionCVM1 and CV-series Optical Ring Controller Link Units

47

Note 1. Set the transmission path format before connecting the Controller Link com-munications cable.

2. Make the same setting for all the nodes in the network. The network will notoperate normally if the settings are different.

3. Set the token-ring mode for ring connection, and the token-bus mode fordaisy-chain connection. The network will not operate normally if the actualconfiguration is different from the transmission path format setting. If, for ex-ample, the actual configuration is daisy-chain while the transmission pathformat setting is for token-ring mode, it will be determined that the network isbroken somewhere. (Even if this occurs, data communications will bestarted up.) The network will also not operate normally if the actual configu-ration is ring connection while the transmission path format setting is for to-ken-bus mode.

4. The transmission path format for an Optical Bus System is always token-bus mode. When used in combination with Optical Bus Controller Link Units,therefore, Optical Ring Controller Link Units (H-PCF cable) must also be setfor token-bus mode.

4-2 CVM1 and CV-series Optical Ring Controller Link UnitsBefore starting communications, the following settings are required for an Opti-cal Ring Controller Link Unit (H-PCF cable) used with a CVM1 or CV-series PC.

Item Switch Page

Unit number Unit number switch 48

Node address Node address switch 49

Transmission pathformat

Software switch 49

4-2-1 Overview

Unit Number

Node Address


48

Unit Number

Setting range Nodes

00 to 15 (default is 00) All nodes in the Network

Node Address

Setting range Nodes

01 to 62 (default is 01) (see note) All nodes in the Network

Note 1. CX-Net in CX-Programmer can be used in systemswith up to32 nodes (node addresses 1 to 32). UseController Link Support Software (Ver. 2.00 or later)for systems with up to 62 nodes (node addresses 1to 62).

2. With the token-bus method, the maximum numberof nodes in an Optical Bus System (i.e., ControllerLink Unit model numbers ending in CLK11) withnodes is 32 (node addresses 1 to 32).

Transmission Path Format Setting (Software Switch)

Setting range Nodes

Token-ring modeToken-bus mode

All nodes in the Network



Transmission Path


9 8

0 0 Token-ring mode

0 1

1 0

1 1 Token-bus mode

4-2-2 Setting the Unit NumberSet the unit number for each Unit using the rotary switches on the front of theUnit. The unit number is used to identify a CPU Bus Unit in the PC. Any unit num-ber can be set between 00 and 15.

10’s digit

1’s digit

0 X100

UNITNO.X101 0


Item Specifications


Setting range 00 to 15 (default is 00)




49


2. When setting a Unit for the first time or changing the existing setting, create aI/O table in the PC’s CPU Unit.

3. Do not set the same unit number twice within the same PC. An error willoccur if the same unit number is set for two different Units, and the CPU Unitwill not be able to recognize the Units.

4. When the Unit is recognized by the CPU Unit, “NS” will be shown in the I/Otable displayed at the SYSMAC Support Software.


6. The unit number determines the DM parameter area used by the ControllerLink Unit in PC memory.

4-2-3 Setting the Node AddressSet the node address of each Unit in the network using the rotary switches on thefront of the Unit. The node address is used to identify each node in the Network.

The node address can be set to any value between 01 and 62.

10’s digit

1’s digit

0 X100

NODENO.X101 1


Item Specifications






2. Do not set the same node address twice within the same network. A nodeaddress duplication error will occur if the same address is set for two differ-ent nodes. The ERC indicator on the front of the Unit will light (Communica-tions Error Flag) and either communications will stop, or the INS indicatorwill not light and the node will be unable to participate in the network.

3. The send sequence for the data link areas is determined according to thesequence of node addresses for automatically set data links.

4. Assign node addresses consecutively beginning from 01 whenever pos-sible to minimize network construction time.

4-2-4 Setting the Transmission Path FormatThe transmission path format is set by a software switch allocated in the CPUUnit’s DM parameter area (the CPU Bus Unit Area). The same setting must bemade for all nodes in the network. Select either token-ring mode or token-busmode by using a PC Programming Device (i.e., Programming Console or SYS-MAC Support Software) to set values for bits 9 and 8 in the software switchshown below.


50

When the transmission path format is changed, the change will not go into effectuntil the PC’s power is turned OFF and ON again or the Unit is restarted.



Transmission Path


9 8

0 0 Token-ring mode

0 1

1 0

1 1 Token-bus mode

Note 1. Set the transmission path format before connecting the Controller Link com-munications cable.

2. Make the same setting for all the nodes in the network. The network will notoperate normally if the settings are different.

3. Set the token-ring mode for ring connection, and the token-bus mode fordaisy-chain connection. The network will not operate normally if the actualconfiguration is different from the transmission path format setting. If, for ex-ample, the actual configuration is daisy-chain while the transmission pathformat setting is for token-ring mode, it will be determined that the network isbroken somewhere. (Even if this occurs, data communications will bestarted up.) The network will also not operate normally if the actual configu-ration is ring connection while the transmission path format setting is for to-ken-bus mode.

4. The transmission path format for an Optical Bus System is always token-bus mode. When used in combination with Optical Bus Controller Link Units,therefore, Optical Ring Controller Link Units (H-PCF cable) must also be setfor token-bus mode.

51

SECTION 5Data Links

This section describes how to use data links in a Controller Link Network. Refer to Section 2 Basic Procedures for an outlineof data link application.

5-1 What Are Data Links? 52. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1-1 Data Link Specifications 55. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1-2 Differences Between Manual and Automatic Setting 56. . . . . . . . . . . . . . . . . . . . . .

5-2 Setting Data Links 57. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2-1 Selecting Manual or Automatic Setting 57. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2-2 Manual Setting 57. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2-3 Manual Setting Examples 63. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2-4 Automatic Setting: Select All 69. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2-5 Automatic Setting Example 74. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-3 Starting and Stopping Data Links 75. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3-1 Using a Programming Device or the User Program 75. . . . . . . . . . . . . . . . . . . . . . . 5-3-2 Using the Controller Link Support Software (Ver. 2.00) and CX-Programmer 76. . 5-3-3 Using FINS Commands 76. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-4 Checking Data Link Status 77. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4-1 LED Indicators 77. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4-2 Data Link Status Area 77. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4-3 Checking by Manipulating Bit/Word Status 81. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4-4 Error Detection Program Example 81. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4-5 Data Link Status Storage Format 81. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-1SectionWhat Are Data Links?

52

5-1 What Are Data Links?Data links automatically exchange data in the preset areas between nodes (PCsand/or computers) on one network. Data links can be freely created for CS1-se-ries, CVM1, and CV-series PCs, and IBM PC/AT or compatible computers (intoken-bus mode only).

Two data link areas, Area 1 and Area 2, can be set for each node. Data links canbe set in either of the following ways.

• Data link areas can be manually set by inputting data link tables through Con-troller Link Support Software (Ver. 2.00 or later). Data link tables are created todefine the data links. These tables enable free allocation of data link areas.

• Data links can be set automatically from a Programming Device. With auto-matically set data links, all link areas are the same size.

Both automatic setting and manual setting cannot be used together in the samenetwork. The following rules apply to these two methods of setting data links.

• Data links are enabled concurrently for Area 1 and Area 2.

• Separate settings (data link start words and send area size) are made in Area 1and Area 2. The sequences of send and receive words are the same in Area 1and Area 2.

• Not all nodes must participate in the data links.

Manually Setting Data Links

# 1# 1

# 1

# 2Area 1

# 2

# 2

# 2# 1

# 2

# 2Area 2

# 1

# 1

# 1

# 1

# 2

# 2Area 1

# 1

# 2

# 1 # 2Area 2

# 1 # 1

Send only

Example 1: The order of send and receivenodes is free.

Example 2: Some nodes can send datawithout receiving data.

# 1 # 2Area 1

# 2# 2

# 2# 2

# 1 # 2Area 2

# 1

# 2

# 2Area 1

# 1# 1

# 2

# 1 # 2Area 2

# 1 # 1

Receive only

Receive only

Severalwords fromthe begin-ning ofarea

Example 3: Some nodes can receivedata without sending data.

Example 4: A node can receive only aspecified number of words fromthe beginning of an area.

Manually set data links are used to create flexible data links that meet the needsof the individual system.

• Data links are set in the Controller Link Unit or Board of each node using theController Link Support Software (Ver. 2.00).

• Area 1 and Area 2 can be selected from PC memory areas, including the DMArea and EM Area.

• A send area and its size can be allocated freely for each node.

• The sequence of receive nodes can be changed.

• Nodes can be set that only send or only receive data.

• Only part of send data can be received and an offset can be used to specify thebeginning of the desired part.


53

The following options can be set when manually setting data links.

OffsetsData of the only the specified number of words can be received starting from thespecified word position. The starting word is set as an offset from the beginningof the send data. The following is an example.

# 1

# 1#2

# 1 # 2Area 1

# 1

# 1Area 2

# 2

# 1

Specified position in relation to the leading word

Specified number of words

Specified position in relation to the leading word

Specified number of words

Easy SettingThe send data areas of all nodes can be set to the same size (same as for auto-matic setting described next).

Automatically Setting Data LinksExample

Node#1 Node#2 Node#3

# 3# 2# 1

# 3# 2# 1

# 3# 2# 1

Area 1(Bit areas)

# 3

# 2

# 1

# 3

# 2

# 1

# 3

# 2

# 1Area 2(Data Memory)

Automatic setting can be used to create simple data links.

• Using a Programming Device (such as a Programming Console), set the auto-matic data link mode in the DM parameter area of the startup node.

• Area 1 can be selected from bit areas (i.e., IR, CIO, and LR areas) and Area 2can be selected from Data Memory.

• In areas 1 and 2 send areas for each node are of the same size.

• Send nodes are in the same ascending order as node numbers.

• It is not possible to receive only a part of send data.

• All nodes can be specified to either participate or not participate in the data link.

• The data link areas are exactly the same and common to all nodes participat-ing in the data links.

Note The Controller Link Support Software contains a function called“Easy Setting” that can be used within the manual data link mode toregister the same data links as automatic setting. The “Easy Setting”can be used first, and then the send size of each node and other set-tings can be changed as required.

Manual Setting Options


54

Using OffsetsFor automatically set data links, all of the send words transmitted by a node arereceived by other nodes with no change in size. For manually set data links, thesize of a receive area can be restricted by specifying a number of words from thebeginning word of the words sent by another node.

Manually setdata links

A node can specify the num-ber of words to receive fromthe beginning send word.

# 1

# 2

# 3

# 2

# 3

# 2

# 3

# 3

# 2

# 1 # 1

# 3

# 2

# 1 # 1

# 3

# 2

# 1

Automatically setdata links

# 1 # 2 # 3

# 1 # 2 # 3

However, the above system does not guarantee that only the desired words willbe received and therefore the receive node may receive unnecessary data.

Offsetting enables specification of a more specific range of receive data by indi-cating both the number of words and the starting word position from the begin-ning of the area. The offset refers to the starting word position counted from thebeginning of the area.

# 1

# 2

# 3

# 3

# 1 # 3

# 2# 2

# 1Offset from the beginning

Number of words to be received

Restricted receptionfrom node 1 byspecifying an offset

Restricted receptionfrom node 2 byspecifying an offset

# 1 # 2 # 3

Offsetting Image

#1 Data

I only need this. I need all of it.

#1 Data


55

Application Example of Using OffsetsIn the following example, the send data from node 1 is split into three parts andeach part is received by a different node, i.e., each of the other nodes receivesonly part of the send data from node 1. This enables effective use of data linkmemory areas without wasting space. In this way, a type of message service(i.e., specific data to a specific node) can be achieved through data links.

# 1 # 2 # 3 # 4

Send data of node 1

5-1-1 Data Link SpecificationsItem Description

No. of data link nodes 62 max., 2 min. (See note 1.)

Number of data linkwords

Number of send/receive words per node (total of Area 1and Area 2) :

CS1: 12,000 max.CVM1/CV: 8,000 max.

IBM or compatible: Manual setting: 32,000 max.(See note 2.) Automatic setting: 8,000 max.

Number of send words per node (total of Area 1 and Area 2): 1,000 max.

Allocation of data linkareas

Manualsetting

Area 1, 2: Bit area (IR, CIO, and LR Areas)Data Memory (DM and EM Areas)

However, Area 1 and Area 2 cannot be set inthe same memory area.

Automaticsetting

Area 1: IR, CIO, or LR Area

Area 2: Data Memory (DM and EM Areas)

Note 1. With an Optical Bus System, data is received for only a maximum of 32nodes (node addresses 1 to 32). When Optical Bus and Optical Ring Con-troller Link Units are used in combination, the maximum number of nodeswill be 32 if the automatic setting is in effect. Likewise, the maximum numberof nodes will be 32 (node addresses 1 to 32) when CX-Net in CX-Program-mer is used as a Programming Device.

2. FA computers can be used with the following systems:Systems in which only Optical Bus Controller Link Units (model numbersending with CLK11) are connected.Systems in which only Optical Bus (CLK11) and Optical Ring (H-PCF cable;model numbers ending with CLK12) Controller Link Units are used, and thetoken-bus mode is used for both.


56

5-1-2 Differences Between Manual and Automatic Setting

Item Manual setting Automatic setting

Determination ofnodes to be in adata link

Determined by setting datalink tables.

Determined by the data linkparameters set in the data linkstartup node (the node used tostart the data links).

Data link settings Set in data link tables that areset in the nodes to participatein data links.

Determined by the data linkparameters set in the data linkstartup node (the node used tostart the data links).

Data link areas 1and 2

In each node, Area 1 and Area2 are selected from bit areas(IR, CIO, and LR Areas) andData Memory (DM and EMAreas).

However, areas 1 and 2cannot be set in the samememory area.

Area 1 is selected from bitareas (IR, CIO, and LR Areas)and Area 2 is selected fromData Memory (DM and EMAreas).

Refresh startingword

Can be set freely in eachnode. (See note a))

Can be set freely. (See notea))

Data link statusarea

Selected from bit areas (IR,CIO, and LR Areas) and DataMemory (DM and EM Areas)in each node.

Selected from bit areas (IR orCIO Areas).

Refreshsequence

Can be set in each nodefreely.

Node addresses are inascending order.

Data reception It is possible to set in eachnode whether the entire dataor a part of the data sent fromanother node is received. It isalso possible to not receivethe data sent from a specificnode. (See note b))

The entire data sent from eachnode that is participating in thedata link is received.

Datatransmission

The send sizes can be setfreely in each node. It is alsopossible for certain node not tosend data. (See note b))

In Area 1 and Area 2, datasend sizes are the same ineach node.

Note a) The following are true for computer nodes (i.e., computers with aController Link Support Board mounted).

• The data link starting position is fixed.

• Because areas such as bit areas and DM are not available, areasmust be made available on the computer for linking.

• Automatically set data links cannot be started from the ControllerLink Support Board.

• The Controller Link Support Board can participate in automati-cally set data links.

b) If data links are manually set, send/receive area can be selectedin each node, allowing send/receive groups to be created withinthe network in Area 1 and Area 2, as shown below.

#1 #1 #3#1 #2 #3Area 1

#2 #2 #4 #4

#3#4

Group Group

5-2SectionSetting Data Links

57

5-2 Setting Data Links

5-2-1 Selecting Manual or Automatic SettingSpecify either the manual or automatic data link mode in the following DMparameter area of the PC’s CPU Unit of the startup node, using a PC Program-ming Device.

Software switches(DM area)

Startup node CPU Unit

Or

Programming Console

Controller Link SupportSoftware (Ver. 2.00) orCX-Net (in CX-Pro-grammer and forCS1-series PCs)


Controller Link

CS1-series Startup NodesN: DM 30000 + 100 x Unit number of Controller Link Unit

Word N

0: Always 0.–: Other setting Data link mode

00: Manual setting01: Automatic setting

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0– – 0 0 0 0 0 0 0 0 –– – –

CVM1 and CV-series Startup NodesN: DM 2000 + 100 x unit number of Controller Link Unit

Word N

0: Always 0.–: Other setting Data link mode

00: Manual setting01: Automatic setting

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0– – 0 0 0 0 0 0 0 0 –– – –

Note 1. The default data link mode is for manual setting (00), but check the settingfrom the Programming Device.

2. A data link mode can be set in a data link startup node only. The data linkmode setting is determined by the data link mode of the startup node even ifthe data link mode settings of the nodes participating in the data links aredifferent from the settings in the startup node.

3. In manual setting, a data link table must be set in the data link startup nodeand in automatic setting, automatic data link setting parameters must be setin the data link startup node. Data links will not be started unless the settingsare correct.

5-2-2 Manual SettingTransfer the data link tables that were created on the Controller Link SupportSoftware or CX-Net (in CX-Programmer) to the Controller Link Unit or the Con-troller Link Support Board (for IBM PC/AT or compatible computers).

The data link tables are transferred from a computer running the Controller LinkSupport Software (Ver. 2.00 or later). The computer can either be a node in thenetwork or a computer attached as a Programming Device.


58

Transferring from a Programming Device


CPU Unit

+ NodesControllerLink Unit

CPU Unit


Transmissions



Controller LinkSupport Soft-ware (Ver. 2.00or later) or CX-Net (in CX-Pro-grammer)

CS1-series PCs

Note 1. When transferring data link tables to a CS1-series PC, set pin 1 of the DIPswitch on the CPU Unit to “OFF.” Otherwise, data link tables cannot be writ-ten normally.

2. When transferring the data link tables to a CVM1 or CV-series PC, set theSystem Protect Keyswitch on the CPU Unit to “NORMAL.” Otherwise, datalink tables cannot be written normally.

3. The Controller Link Support Software (Ver. 2.00 or later) can be integratedinto the SYSMAC Support Software. Refer to the Controller Link SupportSoftware Operation Manual (W308) for details.

Transferring from a Computer Node (Token-bus Mode Only)


IBM PC/AT or compatiblecomputer


Controller LinkSupport Software

A data link table is created for each node using the Controller Link Support Soft-ware (Ver. 2.00). The data link tables contain all the settings required to createthe data links.

Note 1. The following three methods can be used to start data links. (See p. 75.)

• Using a software switch

• Using the Controller Link Support Software or CX-Net (in CX-Program-mer)

• Using an FINS command

2. To create data link tables using the Controller Link Support Software (Ver.2.00), the network must have been constructed correctly. Set routing tablesat each node as required. See Application Precautions page xiii for details.


59

Data Link Table SpecificationsSetting item Setting range

PC model Set the model of the PC’s CPU Unit.

Nodes 1 to 62 (*1)

Set the address of the refresh node.It cannot be set to a parameter exceeding the “maximum nodeaddress” of the network parameter.

*1: With an Optical Bus System, data is received for only amaximum of 32 nodes (node addresses 1 to 32). WhenOptical Bus and Optical Ring Controller Link Units are usedin combination, the maximum number of nodes will be 32 ifthe automatic setting is in effect. Likewise, the maximumnumber of nodes will be 32 (node addresses 1 to 32) whenCX-Net in CX-Programmer is used as a ProgrammingDevice.

First data linkstatus word

Set the first word to store data link status. An area of 16 words isused.

CIO Area: CIO 001 to CIO 6128 (*1)

LR Area: LR 00 to LR 184 (*2)

DM Area: DM 0000 to DM 32752

EM Area: Banks 00 to 12, EM 0000 to EM 32752

*1: When IR 000 is specified or when the default setting (–––––)is left unchanged, the default first status word will be used.Refer to 5-4 Checking Data Link Status for details.

*2: When a word between LR 000 and LR 184 is specified, thedata link area will be allocated between CIO 1000 andCIO 1184.

Area 1 Data linkstart word

CIO Area: CIO 000 to CIO 6143

LR Area: LR 00 to LR 199 (*)



The same area cannot be set for both Area 1 and Area 2. Setdifferent areas.

*: When a word between LR 000 and LR 199 is specified, thedata link area will be allocated between CIO 1000 andCIO 1199.

Number ofwords

Remote nodes: 0 to the number of source wordsSet the number of words to be received.

Local node: 0 to 1,000Set the number of words to be transmitted.

The total number of words in Area 1 and Area 2 in each nodemust not exceed 1,000.

The numbers of words in both Area 1 and Area 2 in each nodemust not be set to 0.

Offset Remote nodes: 0 to one less than number of source wordsSet the offset for the data to be received.

Local node: Cannot be set.

This setting is not required if an offset is not used.

CS1-series PCs


60

Setting item Setting rangeArea 2 Data link

start wordCIO Area: CIO 000 to CIO 6143



EM Area: Banks 00 to 15, EM 0000 to EM 32767(EM must be installed)



Number ofwords








Note a) The total number of words in data link send and receive areasmust not exceed 12,000 per node.

b) The following values must be satisfied for each node for the datalink Area 1 and Area 2 so that the final word in the data link doesnot go beyond the last word in the PC memory area.

(Data link start word – 1) + (Total number of send/receive words in Area 1 or Area 2)

6143 (CIO Area)199 (LR Area)32767 (DM Area, EM Area)

c) Refer to the Controller Link Support Boards Operation Manual(W307) for information on the Controller Link Support Board.

Setting item Setting range

PC model Set the model of the PC’s CPU Unit.

Nodes 1 to 62 (*1)

Set the address of the refresh nodes.It cannot be set to a parameter exceeding the “maximum nodeaddress” of the network parameter.

*1: When Optical Bus and Optical Ring Controller Link Units areused in combination, the maximum number of nodes will be32 if the automatic setting is in effect. Likewise, themaximum number of nodes will be 32 (node addresses 1 to32) when CX-Net in CX-Programmer is used as aProgramming Device.



61

Setting item Setting range


Set the first word to store data link status. An area of 16 words isused.

CIO Area: CIO 0001 to CIO 2540 (*1)

LR Area: LR 000 to LR 184 (*2)

DM Area: DM 0000 to DM 8176 (CV500/CVM1-CPU01)DM 0000 to DM 24560 (Other CPU Units)


*1: When CIO 000 is specified or when the default setting(–––––) is left unchanged, the default first status word will beused. Refer to 5-4 Checking Data Link Status for details.

*2: When a word between LR 000 and LR 184 is specified, thedata link area will be allocated between CIO 1000 andCIO 1184.

Area 1 Data linkstart word







Number ofwords









62

Setting item Setting rangeArea 2 Data link

start wordCIO Area: CIO 0000 to CIO 2555






Number ofwords










(Data link start word – 1) + Total number of send/receive words in area 2555 (CIO Area)

199 (LR Area)8191 (DM Area for CV500/CVM1-CPU01)24575 (DM Area for other CPU Units)32765 (EM Area)

c) Refer to the Controller Link Support Boards Operation Manual(W307) for information on the Controller Link Support Board.

Precautions• When data links are automatically created for networks containing CS1-series

PCs, CVM1, and CV-series PCs, the linkable area is restricted to the area ofthe CVM1, CV-series PC because it is smaller than that of CS1-series PCs.

DM Area

Available for the data links

Example:

toDM 00000

DM 24575

to

to

D00000

D24575

D32767

Not available for the data links

CS1-series PCs

CVM1 or CV-series PCs

• The following limitations apply when Optical Bus (CLK11) and Optical Ring(CLK12) Controller Link Units are used in combination.


63

• The data that can be received by the Optical Bus Controller Link Units islimited to node addresses 1 to 32, and the data link status that is reflectedis also limited to these node addresses.

• When data links are set automatically, and an Optical Ring Controller LinkUnit is used as the startup node, register the participating nodes within therange of node addresses 1 to 32. If a node address of 33 or higher is in-cluded, a data link table setting error will be generated at the Optical RingController Link Unit.

• When setting data links manually, the receiving nodes that are set in theOptical Bus Controller Link Unit data link table must be within the range ofnode addresses 1 to 32. If a node address of 33 or higher is included, adata link table setting error will be generated at the Optical Bus ControllerLink Unit.

5-2-3 Manual Setting ExamplesThis section shows examples of manually creating data link tables on the Con-troller Link Support Software. Sample files containing the data link tables areprovided on the installation disk for the Software.

SAMPLE1.CLK: Same Allocation to All NodesData Link Area Structure

Data Link Areas

Node 1 Node 2 Node 3 Node 4

CS1G-CPU42

Area 1LR000

LR010

LR020

LR030

LR049

Area 2D00000

D00200

D00300

D00400

D00599

#1 #1 #1 #1

#2 #2 #2 #2

#3 #3 #3 #3

#4 #4 #4 #4

#1 #1 #1 #1

#2 #2 #2 #2

#3 #3 #3 #3

#4 #4 #4 #4

CS1G-CPU42 CS1G-CPU42 CS1G-CPU42

Device Information Settings


64

Data Link Tables

Set exactly the same table for nodes 2, 3, and 4. To do this, the copy function canbe used to copy the data link table for node 1 to nodes 2, 3, and 4.

Checking the Data Link Tables

Transferring the Data Link Tables

Saving the Data Link Tables


65

SAMPLE2.CLK: Different Allocations to Each NodeData links can be created so that one node does not receive from all other nodesor so that some nodes do not send or receive any data at all. In the followingexample, node 2 does not receive data from node 3 and node 3 does not receivedata from node 1. Node 4 does not send any add; it only receives data from othernodes.

Data Link Area Structure

Data Link Areas


CVM1-CPU21 CVM1-CPU21

Area 1LR000

LR010

LR030

LR010

LR020

LR039

01000

01020

01039

LR049

01005

01015

01035

01054

Area 2D00000

D00010

D00030

E0_00020

E0_00030

E0_00049

D00000

D00020

D00039

D00049

E1_00000

E1_00010

E1_00030

E1_00049

#1 #1

#3

#2 #2

#2

#3

#1

#2

#3

#1 #1

#3

#2 #2

#2

#3

#1

#2

#3

CS1G-CPU42CS1G-CPU42

Only nodes in which a data link table has been created can participate in the datalinks.

In the data link table, the node sequence can be changed freely; however, thedata link areas must be created consecutively.

Device Information Setting


66

Data Link Tables

SAMPLE3.CLK: Creating Data Link Groups within a NetworkA data links consisting of multiple groups within a single network can be createdby setting data link tables. Send and receive areas are created for only the nodesin each group, as shown below.


Data Link Areas

Area 1

Area 2


CVM1-CPU21 CVM1-CPU21

Group 1 Group 2

L00000

L00010

L00029

L00000

L00010

L00029

01000

01020

01039

01000

01020

01039

D01000

D01100

D01299

D00000

D00100

D00299

E0_00000

E0_00300

E0_00599

E1_00000

E1_00300

E1_00599

#1

#2

#1

#2

#3

#4

#3

#4

#1

#2

#1

#2

#3

#4

#3

#4

CS1G-CPU42 CS1G-CPU42


67


Data Link Tables


68

SAMPLE4.CLK: Receiving Only Part of Send Data and OffsetsOnly Area 2 is used in this example.

Note A Controller Link Support Board is used in this example. The Support Boarddoes not have memory areas. The area settings are ignored and byte addressesare used. Refer to the Controller Link Support Boards Operation Manual (W307)for details on using a Controller Link Support Board.


Data Link Areas

Area 2

(Byte addresses)



00000

00020

D00000

D00010

D00000

D00010

D00000

D00010

00040 D00019 D00019 D00019

00060

00080

00100

00119

#1B

#1C

#2

#3

#4

#1A

#2

#1C

#3

#1B

#4

#1A

CS1G-CPU42 CS1G-CPU42 CS1G-CPU42



69

Data Link Tables

5-2-4 Automatic Setting: Select AllData links can be automatically created by setting values in the DM parameterarea of the PC’s CPU Unit of the startup node. The settings are made using aProgramming Console or the SYSMAC Support Software.The startup node is the node from which the data links are activated. When auto-matically setting data links, data link operation is based on the values set in thestartup node.

Note Automatic setting appears as “Select All” on the Controller Link Support Soft-ware message screens.

Software switch(DM area)

Startup node CPU Unit

Or

Programming Console

SYSMAC SupportSoftware (Ver. 2.00)or CX-Net (in CX-Programmer andfor CS1-series PCs)


Controller Link

Note Data links can be started using one of the following (See p 75.)

• Using a software switch• Using Controller Link Support Software or CX-Net (in CX-Programmer)• Using FINS commands.


70

CS1-series Startup NodeSet the following DM parameter area of the PC of the startup node.

Data link mode Set to 01 for automatic setting.(00 is for manual setting. Other values are invalid.)

Area 1 data link start word (BCD) *1

Area 1 type

Number of send words per node of Area 1 (BCD)

Rightmost 4 digits of data link start word of Area 2 (DM area) (BCD)

Leftmost digit of data link start word ofArea 2 (BCD)

First data link status word (BCD)

–: Not used.

*1: BCD: Set the value as binary-coded decimal.

*2: With Optical Bus (CLK11) Optical Link Units, N+10 and N+11 (node addresses 33 to 62) cannot be used.

Nodes to participate in the data links (*2)

The numbers indicate node numbers.The value assigned indicates whether thenode is to participate in the data links.

Participate: 1Not participate: 0

Word N

0: Always specify 0.–: By other setting

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

15 8 7 0

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

N+1

N+2

N+3

N+4

N+5

N+6

N+7

N+8

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17N+9

– – 0 0 0 0 0 0 0 0 –

N: DM 30000 + 100 Controller Link Unit number

Area 2 type


00

48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33N+10

– – 62 61 60 59 58 57 56 55 54 53 52 51 50 49N+11

– – –

Item Setting range

Data link mode Specify automatic (01).

Area 1 data link startword

Set the word address in BCD.


LR Area: LR 00 to 199 (*)

*: When a word between LR 000 and LR 199 isspecified, the data link area will be allocated betweenCIO 1000 and CIO 1199.

Area 1 type Set the area for Area 1 in BCD.

IR Area: 80

LR Area: 86

Area 1 not used: 00

Number of send wordsper node of Area 1

Set the number of words in BCD between 0 and 1,000.

The total number of send words for Area 1 and Area 2must not exceed 1,000.

When Area 1 is not used, set to 0.





Area 2 type Set the area type for Area 2 in BCD.

DM Area: 82

EM Area: Banks 00 to 07: 90 to 97Banks 08 to 12: A8 to AC

Area 2 not used: 00

Settings


71

Item Setting range



The total number of send words of Area 1 and Area 2must not exceed 1,000.


First data link statusword

Set in BCD the first word used for storing data linkstatus. An area of 16 words is used for storing status.

0 (*), IR 000 to IR 6128

Status is stored in an the IR Area only.

*: When 0 is set, the status is saved in IR 1500 + unitnumber x 25 (+ 7 to + 22).

Nodes to participate inthe data links

Set to ON (1) the bits corresponding to the nodesparticipating in the data links.

The data link will not start unless the startup node itselfis set as a participating node.

The data link will not start if the node is set to aparameter exceeding the “maximum node address” ofthe network parameter.




199 (LR Area)32767 (DM Area, EM Area)

c) When using Area 1 only, set the data link start word, type, and thenumber of send words of Area 2 to 0.

d) When using Area 2 only, set the data link start word, type, and thenumber of send words of Area 1 to 0.

e) The startup node must be set as a participating node of the datalinks. If not, the data links will not start.


72

CVM1 or CV-series Startup NodeSet the following DM parameter area of the PC of the startup node.

Data link mode Set to 01 for automatic setting.(00 is for manual setting. Other values are invalid.)

Area 1 data link start word (BCD) *1

Area 1 type


Rightmost 4 digits of data link start word of Area 2 (DM area) (BCD)

Leftmost digit of data link start word ofArea 2 (BCD)


–: Not used.

*1: BCD: Set the value as binary-coded decimal.

*2: With Optical Bus (CLK11) Optical Link Units, N+10 and N+11 (node addresses 33 to 62) cannot be used.

Nodes to participate in the data links (*2)



Word N

0: Always specify 0.–: By other setting

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

15 8 7 0

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

N+1

N+2

N+3

N+4

N+5

N+6

N+7

N+8

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17N+9

– – 0 0 0 0 0 0 0 0 –

N: DM 2000 + 100 Controller Link Unit number

Area 2 type


00

48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33N+10

– – 62 61 60 59 58 57 56 55 54 53 52 51 50 49N+11

– – –

Item Setting range

Data link mode Specify automatic (01).





*: When a word between LR 000 and LR 199 isspecified, the data link area will be allocated betweenCIO 1000 and CIO 1199.


CIO Area: 80

LR Area: 86

Area 1 not used: 00









Settings


73

Item Setting range


DM Area: 82

EM Area: Banks 00 to 07: 90 to 97

Area 2 not used: 00





First data link statusword

Set in BCD the first word used for storing data linkstatus. An area of 16 words is used for storing status.

0 (*) or CIO 0001 to CIO 2540

Status is stored in the CIO area only.

*: When 0 is set, the status is saved in CIO 1500 + unitnumber x 25 (+ 7 to + 22).

Nodes participating inthe data links

Set to ON (1) the bits corresponding to the nodesparticipating in the data links.

The data link will not start unless the startup node itselfis set as participating node.

The data link will not start if the node is set to aparameter exceeding the “maximum node address” ofthe network parameter.




199 (LR Area)8191 (DM Area for CV500/CVM1-CPU01)24575 (DM Area for other CPU Units)32765 (EM Area)

c) When using Area 1 only, set the data link start word, type, and thenumber of send words of Area 2 to 0.

d) When using Area 2 only, set the data link start word, type, and thenumber of send words of Area 1 to 0.

e) The startup node must be registered as a participating node of thedata links. If not, the data links will not start.

Note 1. When data links are automatically created for networks containingCS1-series, CVM1, and CV-series PCs, the linkable area is restricted to thearea of the CVM1-CV-series PC because it is smaller than that ofCS1-series PCs.

DM Area

Available for the data links

Example:

toDM00000

DM24575

to

to

D00000

D24575

D32767

Not available for the data links

CVM1 or CV-series PCsCVM1 or CV-series PCs

2. The following limitations apply when Optical Bus (CLK11) and Optical Ring(CLK12) Controller Link Units are used in combination.


74

• The data that can be received by the Optical Bus Controller Link Units islimited to node addresses 1 to 32, and the data link status that is reflectedis also limited to these node addresses.

• When data links are set automatically, and an Optical Ring Controller LinkUnit is used as the startup node, register the participating nodes within therange of node addresses 1 to 32. If a node address of 33 or higher is in-cluded, a data link table setting error will be generated at the Optical RingController Link Unit.

• When setting data links manually, the receiving nodes that are set in theOptical Bus Controller Link Unit data link table must be within the range ofnode addresses 1 to 32. If a node address of 33 or higher is included, adata link table setting error will be generated at the Optical Bus ControllerLink Unit.

5-2-5 Automatic Setting ExampleThis section shows an example of DM parameter area settings and the data linkareas that are created as a result.

Set the parameters in the startup node as follows:

Data link mode: Automatic

First data link status word: IR 310

Participating nodes: #1, #2, and #3

Area 1 data link start word: LR 00

Number of words: 10

Area 2 data link start word: DM 1000

Number of words: 200

Data Link Areas Created

#3

Area 1

Area 2

Node #1 Node #2 Node #3LR 0

LR 10

LR 20

DM1000

DM1200

DM1400

#1 #1 #1

#2

#3

#1

#2

#3

#2

#1

#2

#3

#2

#3

#1

#2

#3

DM Parameter AreaSettings

!

5-3SectionStarting and Stopping Data Links

75

5-3 Starting and Stopping Data LinksData link must be started after data link areas have been created. Use any of themethods described below for the startup node to start and stop data links. Thesemethods are the same for both manually and automatically set data links.

Note The data link mode (manual setting or automatic setting) and data link methodare determined according to the data link setting in the startup node. In thestartup node, set a data link table in the case of manual setting and data linkautomatic setting parameters in the case of automatic setting. If the settings areincorrect, the data link will not start.

Caution Check the following items before starting data links. If incorrect data link tablesor parameters are set, injury may result due to unexpected operation of the sys-tem. Even if the correct data link tables and parameters have been set, do notstart or stop data links before verifying that there will be no adverse influence onthe system.

• Manually Set Data LinksCheck the data link tables in each node participating in the data link to see thatthey are correct.Be sure that data link tables are deleted from nodes that are not participating inthe data links.

• Automatically Set Data LinksBe sure that the correct DM parameters have been set in the data link startupnode.

5-3-1 Using a Programming Device or the User ProgramSet the software switch (AR or DM Start Bit) in the PC to ON using a Program-ming Device or from the user program.

Programming Device

User program

Startup node

Controller Link

CS1-series PCsTurn ON the Start Bit in DM 30000 + 100 × N.(N: unit number)

CVM1 and CV-series PCsTurn ON the Start Bit in DM 2000 + 100 × N.(N: unit number)

+

SYSMAC SupportSoftware (Ver. 2.00)or CX-Net (in CX-Programmer forCS1-series PCs)

The data links will start when the Start Bit changes from OFF to ON or is alreadyON when power is turned on. The data links will stop when the Start Bit changesfrom ON to OFF.

Note The data in the AR and DM Areas is retained when power is turned off. There-fore, by setting in the AR and DM Areas can be made in advance to start datalinks as soon as power is turned on.

It is recommended to set the Start Bit to ON in multiple nodes that are participat-ing in the data link so that the data links will start even if the startup node is down.The same data link settings must be set in these nodes for automatically set datalinks.

5-3SectionStarting and Stopping Data Links

76

CS1-series Start Bit

Data link Start Bit

Start: Changed from OFF to ON or set to ONwhen power is turned on

Stop: Changed from ON to OFF

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0Word N

N: DM 30000 + 100 × (unit number)

CVM1 and CV-series Start Bit

Data link Start Bit

Start: Changed from OFF to ON or set to ONwhen power is turned on

Stop: Changed from ON to OFF

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0Word N

N: DM 2000 + 100 × (unit number)

5-3-2 Using the Controller Link Support Software (Ver. 2.00) andCX-Programmer

Data links can be started or stopped using commands on the Data Link Menu ofthe Controller Link Support Software (Ver. 2.00). The node for which starting andstopping is being specified must participate in the data links.

Using a Programming Device Connected to PC Node

Node in data links

Start/stop data links

Controller Link Support Software (Ver. 2.00)or CX-Net (in CX-Programmer)


Note The Controller Link Support Software cannot be connected to aCS1-series PC. Use the CX-Net (in CX-Programmer).

Using a Computer Node

Node in data links



Start/stop data links

Controller Link SupportSoftware (Ver. 2.00)

Data links can be started or stopped from the Controller Link Support Board onthe local node.

5-3-3 Using FINS CommandsData links can be started and stopped by sending the RUN and STOP FINScommands from a node on the Controller Link to a node that is in the data links.

Issuing the FINS Command from a Computer Node

FINS command: RUN/STOP



Node in data links

Issuing the FINS Command from CVM1, CV-series, and CS1-series

Node in data linksFINS command: RUN/STOP

CVM1, CV or CS1

Make sure that the LNKindicator is ON at nodesparticipating in the active datalinks.

5-4SectionChecking Data Link Status

77

Data links can be stopped by sending the FINS command “STOP.” The node towhich the FINS command is issued must be participating in the data link.

5-4 Checking Data Link StatusThere are two methods for checking the status of active data links:

• Check the LED indicators on the front of the Units.

• Check the data link status area.

5-4-1 LED IndicatorsCheck the LNK, M/A, and RING indicators on the front of the unit.

CVM1 and CV-series PCsCS1-series PCs

Optical Ring Controller Link Unit (H-PCF cable) Optical Ring Controller Link Unit (H-PCF cable)

Name Color Status ContentsLNK Yellow ON Participating in data links.(data link) Flashing Data link table setting error

OFF Not in data links or data links are inactive.

M/A (data link

Yellow Data links active innetwork.

Data links not active innetwork.

mode) ON Manual Note: This indicatorwill always be OFF

OFF Automaticwill always be OFFwhen the data linksare not active.

RING Yellow ON Token-ring mode setting (cable normal)(transmissionpath format)


OFF Token-bus mode setting

The LNK indicator will be lit at all nodes participating in the data links as long asoperation is normal. The mode (manual/automatic) of any node active in the net-work can be checked using the M/A indicator, regardless of whether that node isparticipating in the data links. Using the RING indicator, it is also possible tocheck the transmission path format set for an active network, as well as the sta-tus of cables when in token-ring mode. See 9-1 Troubleshooting using Indicatorsfor details.

5-4-2 Data Link Status AreaThe data link status area can be used to check for errors when data link does notoperate normally even though no abnormality has been detected by the PC’sCPU Unit or the Controller Link Unit. The data link status area contains the datalink status information shown below. This status information is stored in thesame words for CS1-series, CVM1, and CV-series.

The number of words used for data link status, and the information that is re-flected, depends on the setting (8-bit or 4-bit format) for the data link status stor-age format specification in the DM parameters area, as shown in the followingdiagram.


78

See 9-2 Status Area and Troubleshooting for troubleshooting procedures.

When 8-bit Format is Specified (See note 1.)

PC status (See note 2)0: Inactive (user program not running)1: Active (user program running)

Communications error (data link reception)0:Normal1:Error

PC’s CPU Unit error (See note 3.)0:Normal1:Error

Data link participation0:Not in data link or data link inactive1:In data link

Offset error (See note 4.)0:Normal1:Error

Error: Offset exceeds number ofsend words.

Insufficient (short) receivearea (See note 5.)0:Sufficient1:Insufficient

Insufficient: Receive area is smaller thansend area. Excess data is truncated; otherdata is received.

Remaining receive area(See note 6.)0:Not remaining1:Remaining

Remaining: Receive area is larger thansend area. Data is received and remainingwords are cleared.

15 14 13 12 11 10 9 8

7 6 5 4 3 2 1 0

15Node 1Node 3

Node 5

Node 7

to

Node 29

Node 31Node 33

Node 35to

Node 55

Node 57

Node 59

Node 61

Node 2

Node 4

Node 6

Node 8

to

Node 30Node 32Node 34

Node 36

to

Node 56

Node 58

Node 60

Node 62

78 0

First status word + 0First status word + 1

First status word + 2







Note 1. When the default setting is used for the data link status storage destination,16 words are determined within the status area according to the unit numbersetting. When the 8-bit format is specified, therefore, the data that is re-flected will be limited to node addresses 1 to 32.

When data link status is required for node addresses 33 or larger, do not usethe default setting, i.e., specify the first word of the status storage area. If thisis done when an 8-bit format is specified, 31 words will be used as the statusstorage area.

2. Always 1 for the Controller Link Support Board.

3. Always 0 for the Controller Link Support Board.

4. Even if an offset error occurs, the data link will operate and the node will par-ticipate in the data links. In the node where the offset error occurred, how-ever, all receive area words will be cleared to 0.


79

5. The following shows an example of an insufficient (short) receive area.

Sendarea

Receivearea

Data indicated by

Sendarea

Receivearea

Data indicated by

Sufficient

is received innode 2.

Insufficient (short)

Data indicated bycannot be received in node 2.

and the remaining data is truncated.is received


6. The following shows an example of a remaining receive area.

Data indicated by

Sendarea

ReceiveareaSend

areaReceivearea

Data indicated by

No remaining

is received innode 2.

is received in node 2 and theremaining words are cleared.

RemainingNode 1 Node 2 Node 1 Node 2

When 4-bit Format is Specified

PC status0: Inactive (user program

not running)1: Active (user program

running)

Communications error(data link reception)0:Normal1:Error

PC’s CPU Unit error0:Normal1:Error


Node 4

Node 8First status word + 0First status word + 1

First status word + 2First status word + 3First status word + 4

First status word + 5First status word + 6First status word + 7






Node 12

Node 16Node 20

Node 24Node 30

Node 32

Node 36

Node 40Node 44

Node 48Node 52

Node 58Node 60

0

Node 3

Node 7Node 11

Node 15Node 19

Node 23Node 27

Node 31

Node 35

Node 39Node 43

Node 47Node 51

Node 55Node 59

0

Node 2

Node 6Node 10

Node 14Node 18

Node 22Node 26

Node 30

Node 34

Node 38Node 42

Node 46Node 50

Node 54Node 58

Node 62

Node 1

Node 5Node 9

Node 13Node 17

Node 21Node 25

Node 29

Node 33

Node 37Node 41

Node 45Node 49

Node 53Node 57

Node 61

Note 1. A communications error will occur in a node that is not participating in thenetwork. When a communications error occurs, previous status is retainedfor other nodes status.

2. Only the PC status and the PC’s CPU Unit error status are refreshed fornodes that are participating in the network, but not participating in the datalinks.

3. When the data link status area is set in the IR, CIO, or LR Area, the data linkstatus will be instantaneously set to 0 when the mode of the PC’s CPU Unit ischanged.

The flags in the data link status operate as follows:


80

Name Function

Data linkparticipation

The corresponding flag will turn ON if the node has neverparticipated in the data link normally. The flag will not turnOFF once it has turned ON even if the node is no longerparticipating in the data links.

Communicationserror

The corresponding flag will turn ON if continuous data linkdata cannot be received from the node, e.g., due to a cablebreak. The flag will turn OFF again if normal data isreceived.

PC’s CPU Unit error The corresponding flag will turn ON if the CPU Unit has afatal error, non-fatal error, or watchdog timer error. The flagwill turn OFF again if the node returns to normal.

The status of this flag is based on data sent from the nodeand will not turn ON if data cannot received, e.g., due to aCommunications Error. Make sure that the CommunicationsError Flag is OFF before checking this flag.

PC status The corresponding flag will turn ON if the user program isbeing executed in the CPU Unit. It will turn OFF is the userprogram is not being executed.

The status of this flag is based on data sent from the nodeand will not turn ON if data cannot received, e.g., due to aCommunications Error. Make sure that the CommunicationsError Flag is OFF before checking this flag.

The Data Link Participation Flag and the PC Status Flag can be used to see if thesystem has started normally. These flags, however, cannot be used to detectcommunications errors. Use the Communications Error Flag and PC’s CPU UnitError Flag to detect errors.

If the Local Node Data Link Participation Flag is OFF, the previous status will bemaintained as the data link status and may not be correct. Make sure that theLocal Node Data Link Participation Flag is ON before checking data link status.

Note The following Local Node Data Link Participation Flags are available.

CS1-series, CVM1, CV-series PCs: Bit 15 in 1500 + 25 x unit number + 6

The data link status storage area is set as follows:

Data linkmode

PC andoperating level


Setting range Default status

Automatic CS1-series PC Specify inDM 30000 + 100 ×N + 7

16 words between CIO 000 and 6640

CIO 1500 + 25 × N + 7 to 22

CVM1 orCV-series PC

Specify in DM 2000+ 100 × N + 7

16 words between CIO 000 and 2540

CIO 1500 + 25 × N + 7 to 22

Manual CS1-series PC Specify in the datalink tables

16 words in the followingrangesCIO: 0 to 6640LR: 0 to 184DM: 0 to 32752EM: 0 to 32752

CIO 1500 + 25 × N + 7 to 22

CVM1 orCV-series PC

16 words in the followingrangesCIO: 0 to 2540LR: 0 to 184DM: 0 to 24560EM: 0 to 32750

CIO 1500 + 25 × N + 7 to 22

Note a) N: Unit number

b) Only status for nodes 1 to 6 are saved.


81

5-4-3 Checking by Manipulating Bit/Word StatusAfter you have confirmed that the data link function is operating normally, checkto see whether or not the data link is operating as intended, i.e., check to see ifthe desired bits/words data is being transferred to the intended words at othernodes.

Although the data link function itself may be operating correctly, the data linkareas may have been input incorrectly.

Change the contents of a bit or word in a data link send area using a Program-ming Device or the user program and check whether the change is reflected indata link areas of other nodes as intended.

Note Do not restart the polling node of the Controller Link Network while data links areactive. Otherwise, the data links may stop.

5-4-4 Error Detection Program ExampleLocal nodeData Link Participation Flag

Node 1Data Link Participating Flag

Node 1Communications Error Flag

Node 1Error output

Node 2Error output

Node 32Error output





When the source node’s data link is participating, the AND condition of the datalink status for each node can be taken using the Data Link Participation Flag andthe Communications Error Flag, and the error output.

The following example shows an error output program for cases where the localnode data link stops.

Local nodeData Link Participation Flag

Release FlagLocal nodeError output

Local nodeError output

DIFD 10000

10000

5-4-5 Data Link Status Storage FormatEither an 8-bit or 4-bit format can be set as the method for storing the data linkstatus. The format setting can be made separately for each node.

• This setting determines the number of words to be used for data link status,and also the information to be reflected. (Refer to 5-4-2 Data Link Status Area.)

• When the 8-bit format is set, the data link status area will be 31 words, andwhen the 4-bit format is set it will be 16 words. When the default setting is usedfor the data link status storage destination, however, this area is always16words regardless of the data link status storage format. Even when the 8-bitformat is specified, therefore, the data link status that is actually reflected willbe limited to node addresses 1 to 32.

The settings for the data link status storage format are shown below. The settingis made using the software switch in bit 7 of the DM parameters area. The ad-dress of the software switch will vary depending on the PC, as follows:

• CS1-series Optical Ring Controller Link Units: DM 30000 + 100 x unit number


82

• CVM1/CV-series Optical Ring Controller Link Units: DM 2000 + 100 x unitnumber

Address N

0: Always 01: Another setting Data link status format

0: 8-bit format1: 4-bit format

• This setting cannot be made for Optical Bus Controller Link Units (CLK11), be-cause it is fixed at the 8-bit format. Always specify 0. With Optical Bus, thenodes for data links are limited to node addresses 1 to 32, so the data link sta-tus is always 16 words.

• The data link status is enabled only when the local node is participating nor-mally in the data links. Confirm that the Local Node Data Link Participating Bitis ON before checking the data link status.

83

SECTION 6Message Service

This section explains how to use the message service provided by a Controller Link Unit. It also explains the FINS commandsand responses supported by Controller Link Units and those supported by CS1-series, CVM1 and CV-series PCs.

6-1 Introduction 84. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-1 SEND and RECV 85. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-2 CMND 89. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1-3 Send/Receive Data Areas 92. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-2 Selecting Communications Instructions 94. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2-1 Message Service Operations 95. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2-2 Message Service Specifications 96. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-3 Using the Message Service 97. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4 FINS Commands and Responses 103. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-4-1 FINS Communications Service 103. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4-2 Sending and Receiving FINS Commands and Responses 103. . . . . . . . . . . . . . . . . . . 6-4-3 Applicable Units for FINS Commands 104. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-5 Commands and Responses for Controller Link Units 104. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-1 Command Codes 104. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-2 DATA LINK START 105. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-3 DATA LINK STOP 105. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-4 CONTROLLER DATA READ 105. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-5 CONTROLLER STATUS READ 107. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-6 NETWORK STATUS READ 108. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-7 DATA LINK STATUS READ 110. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-8 CONNECTION DATA READ 111. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-9 NETWORK DISCONNECT DATA READ 113. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-10 NETWORK DISCONNECT DATA CLEAR 115. . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-11 ECHOBACK TEST 116. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-12 BROADCAST TEST RESULTS READ 116. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-13 BROADCAST TEST DATA SEND 117. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-14 ERROR LOG READ 117. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5-15 ERROR LOG CLEAR 118. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-6 Response Codes 118. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6-1 Configuration 118. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6-2 Network Relay Errors 119. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6-3 Response Codes and Troubleshooting 120. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-1SectionIntroduction

84

6-1 IntroductionA message service is a command/response system used for data transmissionbetween nodes on a network, i.e., PC to PC, PC to computer, and computer toPC). The message service can also be used to control operations, such as modechanges. The message service is implemented by sending commands from theuser program. The following communications instructions are used:

SEND and RECV: Instructions for sending and receiving data.

CMND: An instruction for sending FINS commands. Some FINS commands aresupported by Controller Link Units, and other FINS commands supported by thePC’s CPU Unit.

Message service SEND/RECV instructions CMND instruction (FINS commands)Local nodeto remotenode

PC to PC CS1-series, CVM1,or CV-series PC

User program

A program is not required for receivingresponses when the PC executesSEND and RECV.

SEND

(Com-mand forCPU Unit)

CS1-series, CVM1,or CV-series PC

(Com-mand forCPU Unit)

User program

Command

A program is not required for receivingresponses when the PC executescommands.

CMND

Command

(Com-mand forControllerLink Unit)



PC tocomputer

Computer

A program is required for sending andreceiving data with the computer.

A program is not required for receivingresponses when the PC executes commands.

Command

SEND


Computerto PC

(The equivalent of SEND/RECV and CMND are sentfrom the computer program.)

Computer

Command

(Command forController LinkUnit or CPU Unit)

Programming is required to receiveresponses at the computer.


Local node: Remotenode

SEND:1:1 or 1:N (broadcast)There are no responses for broadcasting.

1:1 or 1:N (broadcast)There are no responses for broadcasting.

RECV: 1:1

Data length 1,980 bytes max. (990 words) 1,990 bytes max.


85

6-1-1 SEND and RECVI/O memory data from other nodes can be read or written by simply using theprogram in the CPU Unit of a CS1-series, CVM1, or CV-series PC to executeSEND and RECV.

CS1-series PCsSEND transmits “n” words beginning with S (the beginning word for data trans-mission at the local node) to “n” words beginning with D (the beginning word fordata reception at the remote node, N.)

S: Local node beginning send wordD: Remote node beginning receive wordC: Local node beginning control data word

Remote (destination) node N00 to 3E (Hex): 0 to 62 (*1)The same data can be broadcast to all nodeson the network by setting the remote node address to FF(Hex).

The range of node addresses will vary for networksother than Controller Link Networks.

(↑ )SEND(90)

S

DC

C+1 0 0

C+3 0 0

Number of retries 0 to F (Hex): 0 to 15 retries

Communication port No.0 to 7 Hex

0: Response required1: Response not required

C+4

C

“n” number of send words0000 to 03DE (Hex): 1 to 990 words

15 11 8 7 0

Remote (destination) network address00 (Hex): Local network01 to 7F (Hex): 1 to 127

C+215 11 8 7 0

Remote unit address00 (Hex): PC’s CPU Unit01 (Hex): Computer (user program)10 to 1F (Hex):Unit nos. 0 to 15E1 (Hex): Inner BoardFE (Hex): Unit connected to network

15 10 8 7 3 0

Response monitor time0000 (Hex): 2 s0001 to FFFF (Hex): 0.1 to 6,553.5 s (Unit: 0.1 s)

If the transmission speed is slow, then settinga small value may generate an error. Thestandard is approximately 4 seconds at1 Mbps or 8 seconds at 500 Kbps.

15 0

Remote (destination) node N

“n” numberof sendwordsn

S15 0

nD

15 0Local node

*1 When Optical Bus Controller Link Units (CLK11) are combined in a network with Controller Link SupportBoards in token-bus mode, only node addresses 1 to 32 can be specified.

Note 1. When communicating with a CVM1 or CV-series PC manufactured prior toApril 1996 on the local network, the local network address cannot be set to“00.” Set a number other than “00” as the local network address in the rout-ing tables, and then specify that number.

2. With the message service, there is no guarantee that a message to a remotenode will reach its destination. It is always possible that the message may belost in transit due to noise or some other condition. When using the messageservice, it is advisable to prevent this situation from occurring by performingresend processing at the node where instructions are issued. With theSEND, RECV, and CMND instructions, resend processing is performedautomatically once the number of retries has been set, so be sure to specifya number other than “0” for the number of retries.

SEND


86

RECV receives “m” words beginning with S (the beginning word for data trans-mission at the remote node, M) to the words beginning with D (the beginningword for data reception at the local node).

Remote (source) node MLocal node

(↑ )RECV(98)

S

DC

“m” num-ber ofsendwords

D15 0 15 0

m

S

Remote (source) node M00 to 3E (Hex): 0 to 62 (*1)


C+1 0 0

C+3 0 0


Communication port No.0 to 7


C+4

C

“m” number of send words0000 to 03DE (Hex): 1 to 990 words

15 11 8 7 0

Remote (source) network address00 (Hex): Local network01 to 7F (Hex): 1 to 127

C+215 11 8 7 0


15 10 8 7 3 0


If the transmission speed is slow, then settinga small value may generate an error. Thestandard is approximately 4 seconds at 1Mbps or 8 seconds at 500 Kbps.

15 0

S: Remote node beginning send wordD: Local node beginning receive wordC: Local node beginning control data word

*1 When Optical Bus Controller Link Units (CLK11) are combined in a network with Controller Link Support Boardsin token-bus mode, only node addresses 1 to 32 can be specified.

Note 1. When communicating with a CVM1 or CV-series PC manufactured prior toApril 1996 on the local network, the local network address cannot be set to“00.” Set a number other than “00” as the local network address in the rout-ing tables, and then specify that number.


RECV


87


SEND transmits “n” words beginning with S (the beginning word for data trans-mission at the local node) to “n” words beginning with D (the beginning word fordata reception at the remote node, N.)

S: Local node beginning send wordD: Remote node beginning receive wordC: Local node beginning control data word

Remote (destination) node N00 to 3E (Hex): 0 to 62 (*1)The same data can be broadcast to all nodeson the network by setting the remote node address to FF(Hex).


(↑ )SEND(192)

SDC

C+1 0 0

C+3 0 0




C+4

C

“n” number of send words0000 to 03DE (Hex): 1 to 990 words

15 11 8 7 0

Remote (destination) network address00 (Hex): Local network01 to 7F (Hex): 1 to 127

C+215 11 8 7 0

Remote unit address00 (Hex): PC’s CPU Unit01 (Hex): Computer (user program)10 to 1F (Hex):Unit nos. 0 to 15FE (Hex): Unit connected to network

15 10 8 7 3 0


If the transmission speed is slow, then settinga small value may generate an error. Thestandard is approximately 4 seconds at1 Mbps or 8 seconds at 500 Kbps.

15 0

Remote (destination) node N

“n” numberof sendwordsn

S15 0

nD

15 0Local node


Note 1. When using CVM1 and CV-series PCs manufactured prior to April 1996, thelocal network address cannot be set to “00.” Set a number other than “00” asthe local network address in the routing tables, and then specify that num-ber.


SEND


88

RECV receives “m” words beginning with S (the beginning word for data trans-mission at the remote node, M) to the words beginning with D (the beginningword for data reception at the local node).

Remote (source) node MLocal node

(↑ )RECV(193)

S

DC

“m” num-ber ofsendwords

D15 0 15 0

m

S

Remote (source) node M00 to 3E (Hex): 0 to 62 (*1)


C+1 0 0

C+3 0 0




C+4

C

“m” number of send words0000 to 03DE (Hex): 1 to 990 words

15 11 8 7 0

Remote (source) network address00 (Hex): Local network01 to 7F (Hex): 1 to 127

C+215 11 8 7 0


15 10 8 7 3 0


If the transmission speed is slow, then settinga small value may generate an error. Thestandard is approximately 4 seconds at 1Mbps or 8 seconds at 500 Kbps.

15 0

S: Remote node beginning send wordD: Local node beginning receive wordC: Local node beginning control data word

*1 When Optical Bus Controller Link Units (CLK11) are combined in a network with Controller LinkSupport Boards in token-bus mode, only node addresses 1 to 32 can be specified.



RECV


89

6-1-2 CMNDThe CMND instruction can be executed in the user program in a CS1-series,CVM1, or CV-series PC to perform operations such as reading and writingmemory data from and to other nodes, reading status information, and changingthe operating mode.

CMND(490) sends “n” bytes of command data beginning with S (the beginningword for storing command data at the local node) to remote node N. In return,“m” bytes of response data are stored at the local node beginning with D (thebeginning word for storing response data).

CMND(490)SDC

“n” bytesof com-manddata

“m” bytesofresponsedata

S15 0

S: Beginning command storage wordD: Beginning response storage wordC: Beginning control data word

Local node Remote (source) node N

(S–1)+ n

2

D

(D–1)+m

2

Command

Response

Analysis

Execution

Remote node N00 to 3E (Hex): 0 to 62 (*1)The same data can be broadcast to all nodeson the network by setting the remote node address toFF (Hex).The range of node addresses will vary for networksother than Controller Link Networks.

C+1

C+4 0 0

Number of retries0 to F (Hex): 0 to 15 retries


C

“n” bytes of command data0000 to 07C6 (Hex): 0 to 1,990 words

0

“m” bytes of response data0000 to 07C6 (Hex): 0 to 1,990 words

15 0

C+315 8 7 0


15 11 8 7 3 0

15 10 8 7 3 0


If the transmission speed is slow, then setting asmall value may generate an error. The standardis approximately 4 seconds at 1 Mbps or 8seconds at 500 Kbps.

C+2 0 015 11 8 7 0

Remote network address00 (Hex): Local network01 to 7F (Hex): 1 to 127

C+5

15


Communications port No.

0 to 7 Hex

Note With the message service, there is no guarantee that a message to a remotenode will reach its destination. It is always possible that the message may be lostin transit due to noise or some other condition. When using the message service,it is advisable to prevent this situation from occurring by performing resend pro-cessing at the node where instructions are issued. With the SEND, RECV, andCMND instructions, resend processing is performed automatically once the

CS1-series PCs


90

number of retries has been set, so be sure to specify a number other than “0” forthe number of retries.

CMND(194) sends “n” bytes of command data beginning with S (the beginningword for storing command data at the local node) to node N. In return, “m” bytesof response data are stored at the local node beginning with D (the beginningword for storing response data).

CMND(194)SDC

“n” bytesof com-manddata

“m” bytesofresponsedata

S15 0

Local node Remote node N

(S–1)+ n

2

D

(D–1)+m

2

Command

Response

Analysis

Execution

Remote node N00 to 3E (Hex): 0 to 62 (*1)The same data can be broadcast to all nodeson the network by setting the remote node address toFF (Hex).The range of node addresses will vary for networksother than Controller Link Networks.

C+1

C+4 0 0

Number of retries0 to F (Hex): 0 to 15 retries


C

“n” bytes of command data0000 to 07C6 (Hex): 0 to 1,990 words

0

“m” bytes of response data0000 to 07C6 (Hex): 0 to 1,990 words

15 0

C+315 8 7 0


15 11 8 7 3 0

15 10 8 7 3 0


If the transmission speed is slow, then setting a smallvalue may generate an error. The standard is approxi-mately 4 seconds at 1 Mbps or 8 seconds at 500 kbps.

C+2 0 015 11 8 7 0

Remote network address00 (Hex): Local network01 to 7F (Hex): 1 to 127

C+5

15

12


Communications port No.

0 to 7 Hex

S: Beginning command storage wordD: Beginning response storage wordC: Beginning control data word




91


Type of command Code CS1 CVM1/CV

For memory areas (CIO, MEMORY AREA READ 0101 Yes YesDM, EM, TC, transition, MEMORY AREA WRITE 0102 Yes Yesstep, forced ON/OFF)

MEMORY AREA FILL 0103 Yes Yes

MULTIPLE MEMORYAREA READ

0104 Yes Yes

MEMORY AREATRANSFER

0105 Yes Yes

For parameter areas (PC PARAMETER AREA READ 0201 Yes Yessystem setting, I/O tableregistration, routing table,

PARAMETER AREAWRITE

0202 Yes Yes

etc.)PARAMETER AREACLEAR

0203 Yes Yes

For program areas (UM) PROGRAM AREAPROTECT

0304 Yes Yes

PROGRAM AREAPROTECT CLEAR

0305 Yes Yes

PROGRAM AREA READ 0306 Yes Yes

PROGRAM AREA WRITE 0307 Yes Yes

PROGRAM AREA CLEAR 0308 Yes Yes

PC mode RUN 0401 Yes Yes

STOP 0402 Yes Yes

PC model data CONTROLLER DATAREAD

0501 Yes Yes

CONNECTION DATAREAD

0502 Yes Yes

PC status data CONTROLLER STATUSREAD

0601 Yes Yes

CYCLE TIME READ 0620 Yes Yes

PC internal clock CLOCK READ 0701 Yes Yes

CLOCK WRITE 0702 Yes Yes

Messages MESSAGE READ 0920 Yes Yes

MESSAGE CLEAR Yes Yes

FAL/FALS READ Yes Yes

Access rights ACCESS RIGHT ACQUIRE 0C01 Yes Yes

ACCESS RIGHT FORCEDACQUIRE

0C02 Yes Yes

ACCESS RIGHT RELEASE 0C03 Yes Yes

Error data ERROR CLEAR 2101 Yes Yes

ERROR LOG READ 2102 Yes Yes

ERROR LOG CLEAR 2103 Yes Yes

Example: Commands forCVM1, CV-series andCS1-series PCs


92

Type of command CVM1/CV

CS1Code

File Memory FILE NAME READ 2201 Yes Yes

SINGLE FILE READ 2202 Yes Yes

SINGLE FILE WRITE 2203 Yes Yes

MEMORY CARD FORMAT 2204 Yes Yes

FILE DELETE 2205 Yes Yes

VOLUME LABELCREATE/DELETE

2206 No Yes

FILE COPY 2207 Yes Yes

FILE NAME CHANGE 2208 Yes Yes

FILE DATA CHECK 2209 No Yes

MEMORY AREA FILETRANSFER

220A Yes Yes

PARAMETER AREA FILETRANSFER

220B Yes Yes

PROGRAM AREA FILETRANSFER

220C Yes Yes

Forced set/reset FORCED SET/RESET 2301 Yes Yes

FORCED SET/RESETCANCEL

2302 Yes Yes

For details on commands for CS1-series PCs, refer to the CS1-series Program-mable Controllers Programming Manual (W340). For details on commands forCVM1 and CV-series PCs, refer to the FINS Commands Reference Manual(W227).

6-1-3 Send/Receive Data AreasThe data areas that can be used as operands in the SEND and RECV instruc-tions depend on the PC, as shown in the following tables. Be sure to set the oper-ands so that the end of the data area is not exceeded.

Area Range

CIO (IR etc) CIO 0000 to CIO 6143

Work Area (WR) W000 to W511

Holding Area H000 to H511

Auxiliary Area A000 to A959 (See note 1.)

Timer TIM0000 to TIM4095

Counter CNT0000 to CNT4095

Data Memory D00000 to D32767

Extended Data Memory E00000 to E32767 (See note 2.)

Note 1. Writing is not possible to words A000 through A447 in the Auxiliary Area.

2. A maximum of thirteen banks can be used for Expansion DM. For details onextended data memory and the number of banks, refer to the operationmanual for the PC model that is being used.

CS1-series PCs


93

Area Range

CV500, CVM1-CPU01 CV1000/2000,CVM1-CPU11/21

CIO Area 0000 to 2555

CPU Bus Link Area G000 to G255 (See note 1.)

Auxiliary Area A000 to A511 (See note 2.)

Timer Area T000 to T511 T000 T1023

Counter Area C000 to C511 C000 to C1023

DM Area DM0000 to DM8191 DM0000 to DM24575

Expansion DM Area --- EM00000 to EM32765 (Seenote 3.)

Note 1. Writing is not possible to words G000 through G007 in the CPU Bus LinkArea.

2. Writing is not possible to words A256 through A511 in the Auxiliary Area.

3. Expansion DM can be used by mounting an Expansion DM Unit to aCV1000/2000 or CVM1-CPU11/21 PC. A maximum of eight banks can beused, depending on the type of Expansion DM. For details, refer to theCVM1 and CV-series PC operation manuals.


6-2SectionSelecting Communications Instructions

94

6-2 Selecting Communications Instructions

Do you want to easily read fromor write to the I/O memory area?

Do you want to intermittently readfrom a memory area?

Aside from memory areas, do youwant to write the following kinds ofdata?

PC internal clock

File Memory

Do you want to read the followingkinds of data?

PC model

PC status

Cycle time

Messages

Errors

Forced set/reset status

Do you want to change the PC’soperating mode?

Do you want to force set/reset bitstatus?

Use SEND and RECV.YES

Use CMND. (see note)YES

YES

YES

YES

Note CMND cannot be used with C200HX/HG/HE PCs.


95

6-2-1 Message Service OperationsInstruc- Local node Remote node Communica- Data Broad- Network

tion C200HX/HG/HE

CQM1H CS1,CVM1,or CV

C200HX/HG/HE

orCQM1H

CS1,CVM1,or CV

Com-puter

tions con-tents

length casting connections

SENDandRECV

Yes Yes Yes Yes Yes Yes(Seenote2.)

Read to andwrite from allI/O memoryareas.

990wordsmax.(1,980bytes)

SENDonly (noresponse)

Yes (up tothree levelsincludinglocalnetwork), via

CMND(Seenote 1.)

No Yes Yes Yes Yes Yes(Seenote2.)

Dataread/write:

Read to andwrite from allI/O memoryareas.

Read PCmodel.

Read statusdata.

Read timedata.

Read andwrite FileMemorydata.

Read PCmode.

PC Control:

Change PCmode.

Forcedset/reset

Clear PCerrors.

2,012bytesmax.

Yes (noresponse)

CVM1 orCV-series.

Note 1. CMND cannot be used with C200HX/HG/HE PCs.

2. If a computer is receiving commands, a program is required at the computerfor sending back responses.


96

6-2-2 Message Service SpecificationsItem Specifications

Transmission format C200HX/HG/HE PCs1:1 SEND or RECV1:N SEND (broadcast)

CS1-series, CVM1,CV-series, or CQM1H-series PCs1:1 SEND, RECV, or CMND1:N SEND or CMND; (broadcast)

Packet length SEND: 990 words (1,980 bytes) max.

RECV: 990 words (1,980 bytes) max.

CMND: 1,990 bytes max.

Data content SEND: Command and response for a request to send dataare transferred.

RECV: Command and response for a request to receivedata are transferred.

CMND: A wide range of command/response data can besent.

Number ofsimultaneouscommands

C200HX/HG/HE PCs: One at a time for each of 2 operating level.

CS1-series, CVM1, and CV-series PCs: One for each of eight ports (ports 0 to 7).

CQM1H-series One

Response monitortime

CS1-series, CVM1, and CV-series PCs0000: Default setting (2 s)0001 to FFFF: User settings (in increments of 0.1 s, 0.1 to

6553.5 s)

Number of retries 0 to F: 0 to 15

6-3SectionUsing the Message Service

97

6-3 Using the Message ServiceWith SEND, RECV, and CMND, the Network Instruction Enabled Flag and Net-work Instruction Error Flag are generally written into the program as input condi-tions, as shown below. Only one instruction can be executed at a time for anygiven communications port. Exclusive control thus must be incorporated toexecute two or more instructions per operating level with C200HX/HG/HE PCs,nine or more instructions with CVM1 and CV-series PCs (because CVM1 andCV-series PCs have eight ports), or two or more instructions with CQM1H-seriesPCs.

Executioncondition

Network Instruc-tion Enabled Flag

KEEP A Keep instruction Turns A ON from beginning to completion of

communications instruction.Reset B

A Operand andcontrol data cre-ation by @MOVand @XFER

Communicationsinstruction@SEND@RECV@CMND

Creates operand and control data in a given area.

Executes communications instruction.

Network InstructionEnabled FlagA Startup differ-

entialDIFU B

Creates reset input. (Turns reset B ON after execution ofcommunications instruction.)Network Instruction Error Flag

Network InstructionEnabled Flag A

Reset D

In case of Send Error Flag, re-send processingcan be executed.

Establishes exclusive control so that no communicationsinstruction is started before the previous one has beencompleted.

Exclusive control to prevent simultaneous execution:

(Continues in the same way.)

Active Node Flag forlocal node

Active Node Flag for re-mote node

A

Executioncondition KEEP C

Keep instruc-tion

C

SEND/RECV FlagsName Address Contents

Word Bit

NetworkInstructionEnabled Flag

A202 Port number correspondsto bit number, i.e., port 0:bit 00, port 1, bit 00, etc.

0: Execution not enabled (executing)1: Execution enabled (not executing)

NetworkInstruction ErrorFlag

A219 Port number correspondsto bit number plus 8, i.e.,port 0: bit 08, port 1, bit09, etc.

0: Normal end1: Abnormal end

Note With CS1-series PCs, ports 0 to 7 are also used for executing the PMCR (Proto-col Macro) instruction, therefore these flags are used for the 4 instructions,SEND/RECV/CMND/PMCR. When the PMCR command is being executed, thesame port cannot be used for SEND/RECV/CMND instructions.

CS1-series PCs


98

Name Address Contents

Word Bit

NetworkInstructionEnabledFlag

A502 Port number correspondsto bit number, i.e., port 0:bit 00, port 1, bit 00, etc.

0: Execution not enabled (executing)1: Execution enabled (not executing)

NetworkInstructionError Flag

A502 Port number correspondsto bit number plus 8, i.e.,port 0: bit 08, port 1, bit09, etc.

0: Normal end1: Abnormal end

Network StatusThe nodes on the network are shown in the following illustrations.

CS1-series, CVM1, and CV-series PCs

*1 When Optical Bus Controller Link Units (CLK11) are combined in a networkwith Controller Link Support Boards in token-bus mode, the range forchecking participation status is 1 to 32.

N: Unit number –: Not used

0: Not participating in network.1: Participating in network.

Communications Flag Operations• The Network Instruction Enabled Flag turns OFF during transmission or

reception, and ON after the data transmission or reception has been com-pleted (regardless of whether an error occurs).

• The Network Instruction Error Flag retains its status until the next data trans-mission or reception.

• Even when there is an abnormal end, the Network Instruction Error Flag turnsOFF when the next communications instruction is executed.

Example

Network Instruction Enabled Flag

Communications instruction(SEND/RECV/CMND)

Network Instruction Error Flag

Communications instruction response code

Instruction 2being executed


Previousend

1

0

1

0


00 00 00 0004 00(Normalend)

(Normalend)

(Busy)



99

Communications Instruction Response CodesThe status after a communications instruction has been executed is reflected inthe words shown in the following table. During instruction execution, it becomes“00” or “0000,” and it is reflected here after the execution has been completed.

PC Word Bits ContentsCS1-series A203 --- Port 0 response code

A204 --- Port 1 response code







CVM1 and A503 --- Port 0 response codeCV-series A504 --- Port 1 response code







The results of executing SEND, RECV, and CMND instructions are reflected asone word (two bytes) of data. Instruction response codes are the same as FINScommand response codes. Response code bits 08 to 15 correspond to the firstbyte of the response code, and response code bits 00 to 07 correspond to thesecond byte of the response code. For details, refer to 6-6 Response Codes.

Simultaneous Execution of Communications Instructions

CS1-series, CVM1, and CV-series PCs

Instruction 1Instruction 2Instruction 3Instruction 4Instruction 5Instruction 6Instruction 7Instruction 8

Controller Link UnitCPU Unit

Port

There are eight communications ports, so eight communications can beexecuted simultaneously. Only one message is refreshed from the CPU Unit tothe Controller Link Unit and one from the Controller Link Unit to the CPU Unit foreach CPU Bus Unit service time.

CS1-series, CVM1, andCV-series ResponseCodes


100

PC Programming ExamplesCS1-series PCs

DIFU(13) 120001

@MOV(21)

#000A

D00000

120000

R

S

KEEP 120000

00000 A20207 120002

120001

@MOV(21)

#0002

D00001

@MOV(21)

#0400

D00002

120000120000 A21907

Control Data Preparation

Turns ON to indicate transmission error.

120000 A20207

Word Content Meaning

D00000 0 0 0 A 10 send words

D00001 0 0 0 2 Destination network address= 2

D00002 0 4 0 0 Remote node address = 4Destination Unit address = 0

D00003 0 7 0 5 Response requiredPort No. 7 usedNo. of resends = 5

D00004 0 0 6 4 Response monitoring time = 10 s

Transfers the 10 words beginning at CIO 0000 to the10 words beginning at D00010.

Transfers the 10 words beginning at DM 00010 ofthe local node to the words beginning with D00020at network address 2, node address 4, and Unitaddress 0 (PC).

Creates reset input.

The transmission program will run when CIO 00000turns ON, provided that the Network Instruction En-abled Flag is ON and the RECV instruction has notbeen executed.

CIO 120000 remains ON while the SEND instructionis being executed, and it turns OFF when instructionexecution has been completed.

(See note 1.)

Executioncondition

(See note 1.)

@MOV(21)

#0705

D00003

@MOV(21)

#0064

D00004

@XFER(70)

#000A

0000

D00010

@SEND(90)

D00010

D00020

D00000

(Continued on the next page)



101

XFER(70)

#0016

2000

D00040

R

S

KEEP(11) 120002

000001 A20207 120000

120003

@MOV(21)

#0010

D00005

120002

@MOV(21)

#0003

D00006

@MOV(21)

#2000

D00007

@RECV(98)

A100

2000

D00005

120002 120003 A21907Transmitted data (16 words from 2000) moved intowords beginning at D00040 for storage.

121001120002 A21907

Turns ON to indicate reception error.

DIFU(13) 120003

120002 A20207Creates reset input.


D00005 0 0 1 0 16 receive words

D00006 0 0 0 3 Destination network address = 3

D00007 2 0 0 0 Remote node address = 32Destination Unit address = 0

D00008 0 7 0 5 Response requiredPort No. 7 usedNo. of resends = 5

D00009 0 0 0 0 Response monitoring time = Default

Control Data Preparation

The reception program will run when CIO 00001turns ON, provided that the Network Instruction En-abled Flag is ON and the SEND instruction has notbeen executed.

CIO 120002 remains ON while the RECV instructionis being executed, and it turns OFF when instructionexecution has been completed.

Transfers the 16 words beginning at A100 of net-work address 3, node address 32, and Unit address0 (PC) to 2000.

(See note 1.)

(See note 1.)

Executioncondition

(Continued from the previous page)

@MOV(21)

#0705

D00008

@MOV(21)

#0000

D00009


Note 1. With CS1-series PCs, the Network Instruction Enabled Flag in A20200 toA20207 corresponding to communications ports will be OFF even whenPMCR (PROTOCOL MACRO) is being executed.

2. When using the sample program, make sure that the bits and words used inthe sample program are not the same as those in the user program or bySpecial I/O Units.


102


I000000

A50207

120002H

120001H

120000H

120000

A50215

I000001

A50207

120000H

120003H

120002H

A50207

120000

121001H

120002H

A50207

120002H

A50215

120002H

120003H

A50215

120000H

(011) KEEP120000H

(030)↑MOV #000A D00000

(030)↑MOV #0002 D00001

(030)↑MOV #0400 D00002

(030)↑MOV #0705 D00003

(030)↑MOV #0064 D00010

(040)↑XFER #0010 I0000 D00010

(192)↑SEND D00010 D00020 D00000

(013)DIFU 120001H

(011)KEEP 120002H

(030)↑MOV #0010 D00005

(030) ↑MOV #0003 D00006

(030)↑MOV #2000 D00007

(030)↑MOV #0705 D00008

(030)↑MOV #0000 D00009

(193)↑RECV A100 2000 D00005

(013)DIFU 120003H

(040)↑XFER #0016 2000 D00040

The transmission program will run when I000000 is ON,provided that the Network Instruction Enabled Flag forport 7 is ON and the RECV instruction has not beenexecuted.

CIO 120000H remains ON while the SEND instructionis being executed, and it turns OFF when the executionof the instruction has been completed.


D00000 00 0A No. of send words: 10H

D00001 00 02 Remote network address: 2

D00002 04 00 Remote node address: 4Remote unit address: 0

D00003 07 05 Response requiredCommunications port no.: 7Number of retries: 5

D00004 00 64 Response monitor time: 10 s

The 10-word data starting from I0000 is stored inD00010 and following words.

Transmission error display

The reception program will run when I000001 is ON,provided that the Network Instruction Enabled Flag forport 7 is ON and the SEND instruction has not beenexecuted.

CIO 120002H remains ON while the RECV instructionis being executed, and it turns OFF when the executionof the instruction has been completed.


D00005 00 10 Number of receive words: 16H

D00006 00 03 Remote network address: 3

D00007 20 00 Remote node address: 32Destination Unit address: 0

D00008 07 05 Response requiredCommunications port no.: 7Number of retries: 5

D00009 00 00 Response monitor time: Default

Reception error display

Reception data processingWhen the data is received without an error, the 16-worddata received at CIO 2000 and following words isstored in D00040 and following words on the same PC.

Transfers 10 words of data from the local node to thePC (from D00020 onwards) at network address 2, nodeno. 4, unit address 0.


Transfers 16 words of data (from A100 onwards) fromthe PC at network address 3, node no. 32, unit address0, to words 2000 onwards.


Note When using the sample program, make sure that the bits and words used in thesample program are not the same as those in the user program or Special I/OUnits.

6-4SectionFINS Commands and Responses

103

6-4 FINS Commands and Responses

6-4-1 FINS Communications ServiceThe FINS communications service is a communications protocol developed byOMRON for FA control devices. It can be used for reading from and writing to PCmemory, or for controlling various operations, without having to create a user’sprogram at the PC. The FINS communications service has its own independentaddress system which does not rely on the actual network address system, so itcan carry out communications in the same way regardless of whether the PC atthe local node is on a Controller Link Network or some other FA network (e.g.,SYSMAC NET or SYSMAC LINK). For details on FINS commands, refer to theFINS Commands Reference Manual (W227).

6-4-2 Sending and Receiving FINS Commands and ResponsesFINS commands can be sent by using the CMND instruction with a CVM1, CV-series, CS1-series, or CQM1H-series PC. The following diagram shows thedata format for sending FINS commands and receiving responses. The datathat is sent and received is all hexadecimal unless otherwise noted.

Command

ResponseWord

Word

1 byte

FINS header

Automatically prepared and added.

2 bytes 2,000 bytes max.

Command code Text

ControllerLink Unit CPU Unit

CS1, CVM1,CV-series,or CQM1H-series PC

Computer


2 bytes 2 bytes 1,998 bytes max.

FINS header

Automaticallyadded.

Commandcode

Responsecode

Text

1 byte

Response

Command

Automatically pre-pared and added.

1 byte 1 byte

@CMNDS

S+1S+2

15 87 0

DD+1D+2

15 87 0

S

DC

6-5SectionCommands and Responses for Controller Link Units

104

The command code consists of two bytes of data, and indicates the contents ofthe command. A FINS command must begin with a 2-byte command code, andany parameters must follow the command code.

The response code consists of two bytes of data, and indicates the result of thecommand execution. The first byte is the MRES (main response code), whichindicates the broad classification of the execution result. The second byte is theSRES (sub-response code), which gives the detailed classification.The following table shows the main response codes and the execution results.For a more detailed listing of response codes, including the sub-responsecodes, refer to 6-6 Response Codes.

MRES Execution result MRES Execution result

00 Normal completion 21 Write not possible

01 Local node error 22 Not executable in current mode

02 Remote node error 23 No unit

03 Communications controllererror

24 Start/stop not possible

04 Not executable (service notsupported)

25 Unit error

05 Routing error 26 Command error

10 Command format error 30 Access error

11 Parameter error 40 Service interrupted by abort

20 Read not possible

6-4-3 Applicable Units for FINS CommandsThe parameters used with FINS commands and responses depend on the Unitto which the command is being sent. The FINS commands and responsesaddressed to Controller Link Units are explained in this manual. For explana-tions of FINS commands for other Units, refer to the FINS Commands Refer-ence Manual (W227).When FINS commands are sent via a Host Link System for CVM1, CV-series, orCS1-series PCs, be sure to use the command format for relaying between net-works.

6-5 Commands and Responses for Controller Link Units6-5-1 Command Codes

Command Data link operation mode Name Pagecode Active Inactive

04 01 Not valid Valid DATA LINK START 105

02 Valid Not valid DATA LINK STOP 105

05 01 Valid Valid CONTROLLER DATA READ 105

06 01 Valid Valid CONTROLLER STATUS READ 107

02 Valid Valid NETWORK STATUS READ 108

03 Valid Valid DATA LINK STATUS READ 110

04 Valid Valid CONNECTION DATA READ 111

05 Valid Valid NETWORK DISCONNECT DATA READ 113

06 Valid Valid NETWORK DISCONNECT DATA CLEAR 115

08 01 Valid Valid ECHOBACK TEST 116

02 Valid Valid BROADCAST TEST RESULTS READ 116

03 Valid Valid BROADCAST TEST DATA SEND 117

21 02 Valid Valid ERROR LOG READ 117

03 Valid Valid ERROR LOG CLEAR 118

Command Codes

Response Codes


105

Note Command codes 0604, 0605, and 0606 are valid only for Optical Ring ControllerLink Units in token-ring mode. They cannot be used in token-bus mode or withany other Controller Link Units.

6-5-2 DATA LINK STARTStarts the Controller Link Network data links.

Command Block

0104

Commandcode

Response Block

0104

Responsecode

Commandcode

The DATA LINK START command can be received for either automatically ormanually set data links. An error will occur if manually set data links are specifiedand yet data link tables do not exist.

The node that receives this command and starts the data links will become thedata link startup node. For automatically set data links, the data links will beexecuted according to the settings at the startup node.

6-5-3 DATA LINK STOPStops the Controller Link Network data links.

Command Block

0204

Commandcode

Response Block

0204

Responsecode

Commandcode

The DATA LINK STOP command can be received only while the data links areactive. An error will occur if this command is sent at any other time.

This command can be received by any node that is participating in the data link.

6-5-4 CONTROLLER DATA READReads the Controller Link Unit’s model, version, and node address data.

Command Block

0105

Commandcode


106

Response BlockFor CVM1, and CV-series PCs

Responsecode

Commandcode

Model

20 bytes 20 bytes

VersionReserved for system

Node address

05 01 00

For CS1-series PCs

Responsecode

Commandcode

Model

20 bytes 20 bytes

VersionNodeaddress

05 01

Wired/Optical Unit

addressNetworkaddress

Model number, version (response): The Controller Link Unit’s model numberand version are returned as shown below, each 20 characters in ASCII code. Iffewer than 20 bytes of data are used, 20 (Hex) (i.e., spaces) will be returned forthe remaining bytes. In the version numbers shown below, the spaces are repre-sented by boxes ().

Model number

Optical Ring Controller Link Unit for CVM1/CV-series PCs:CVM1-CLK12

Optical Ring Controller Link Unit for CS1-series PCs:CS1W-CLK12

Version V2.00V2.00V2.00

The leftmost “V2.00” represents the Communications Controller data link levelversion number. The middle one represents the Communications Controller net-work level version number. The rightmost one represents the Controller LinkUnit version number.

Connection Method (Response)

The connection method parameter for the Controller Link Unit (wired or opticalbus/ring) is configured as follows:

Connection type:0: Wired1: Optical bus/ring

–: Not usedBit

Maximum number of nodes

00: 32 nodes01: 62 nodes

Transmission path format

0: Token-bus mode1: Token-ring mode

Node address (response): The Controller Link Unit’s node address is returnedbetween 01 and 3E Hex (1 to 62).

Unit Address (response): The Unit address set for the Controller Link Unit (10Hex + Unit number), is returned in hexadecimal. Even when there is a Unit num-ber setting error, the Unit address is returned.

Network Address: The Controller Link Unit’s network address, as set in therouting table, is returned in hexadecimal. When the routing table has not beenset, the address becomes 00 Hex.

Parameters


107

6-5-5 CONTROLLER STATUS READReads the Controller Link Unit’s controller status.

Command Block

0106

Commandcode

Response Block

06 01 00 00 00 00 00 00

Response codeCommandcode

Operating status

Status 1

Status 2

Status 3

Status 4

Status 5 Count 1 Count 8 Active node list

Status 6

Total 6 bytes Total 8 bytes

8 bytes

Operating status (response): The operating status of the data links as follows:00 (Hex): Data links inactive.

01 (Hex): Data links active.

02 (Hex): Local data links not active. (The data links are active in the net-work, but the local node is not participating.)

Status 1, Status 4, Status 6 (response): Not used by the Controller Link Unit.Always set to 00 (Hex).

Status 2 (response): For C200HX/HG/HE, CVM1, and CV-series ControllerLink Units, always set to 00 (Hex). For CS1-series and CQM1H-series PCs, theUnit’s setting status is returning in the following configuration.

Bit

For Wired Units: 0: Terminating resistance OFF1: Terminating resistance ON

For Optical Units: 0: No backup power supply1: Backup power supply used

Transmissionspeed:1 Hex: 2 Mbps2 Hex: 1 Mbps3 Hex: 500 Kbps

Status 3 (response): Error information. The configuration is as follows:

1: Error log exists1: Data link error stop

1: Controller transmitter error

1: Node address setting error

1: Duplicate node address setting error (see note 1)1: Network parameter error (see note 2)1: Controller hardware error

706 5 4 3 2 1 0Bit

Note 1. With CS1-series Optical Controller Link Units, this bit will be 1, even if theUnit is mistakenly connected to an Optical SYSMAC LINK Network.

2. A network parameter error occurs if the registered network parameter con-tents do not match the actual network parameter contents after the power isturned on. The system, however, will not stop. When a network parametererror occurs, the actual network parameter contents are automatically reg-istered to that Unit.

Parameters


108

Status 5 (response): Error information related to the Unit and the PC. The con-figuration is as follows:

1: EEPROM error

1: PC model error(C200HX/HG/HE only)

1: PC system setting error (CS1-series, CVM1, and CV-series PCs only)

1: Network parameter error1: Data link table error

1: Routing table error

706 5 4 3 2 1 0

0Bit

A network parameter error, data link table error, or routing table error occurs if anerror is discovered when the parameters and tables are checked at power up.

A PC system setting errors occurs if the Controller Link Unit is not properly rec-ognized by a CVM1 or CV-series PC.

A PC model error occurs if a C200HX/HG/HE Controller Link Unit is mounted toanother type of PC.

Count 1 to Count 8 (response): The total number of times for each of the itemslisted below is returned as 1 byte of hexadecimal data.

Count 1: Number of CRC errorsCount 2: Number of token re-sendsCount 3: Number of token returnsCount 4: Number of token timeoutsCount 5: Number of polling timeoutsCount 6: Number of controller changesCount 7: Number of active node changesCount 8: Reserved for system use.

Network participation status (response): The following diagram shows thebits corresponding to node addresses in the Controller Link Network. When a bitis returned as “1,” it means that the corresponding node is participating in thenetwork.

41213

Bit

Reserved forsystem use.

The numbers in the boxes indicate the nodeaddresses. The bit status of a particularnode address shows whether or not thatnode participates in the network.

0: Not part of network1: Part of network

(All boxes marked by “–” are reservedfor system use and fixed at “0.”)

Byte 1Byte 2Byte 3Byte 4Byte 5Byte 6Byte 7Byte 8

776 5 4 3 2 1 0

6 5 3 2 1815 14 11 10 91623 22 21 20 19 18 172431 30 29 28 27 26 253239 38 37 36 35 34 334047 46 45 44 43 42 414855 54 53 52 51 50 4956– 62 61 60 59 58 57–

6-5-6 NETWORK STATUS READReads the operating status of the entire Controller Link Network.

Command Block

0206

Commandcode


109

Response Block

Responsecode

Commandcode

32 bytes

Participationdata

Actual communications

cycle time

Polling node addressData link operation

Data link type

8 bytes 62 bytes

Data linkrecurring error status

Data link dataerror counter

06 02

Participation data (response): This parameter indicates the active status ofindividual nodes with respect to the network (i.e. their participation in the net-work). As shown in the following diagram, that status is expressed in four bitscorresponding to the node address.

7 6 5 4 3 2 1 0

0Reserved (0)

Node #2

Node #4

Bit

Byte 1

Byte 2

Byte 3

Byte 17

Byte 18

Byte 32

Node #1

Node #3

Node #5

Reserved (0)

Node #32

Node #34

Participation Status of Individual Nodes

0: Not part of network1: Part of network

0: Normal disconnection1: Abnormal disconnection

(Applicable only forinactive nodes.)

0: Normal node1: Non-responding node

(No response to polling)

Node #33

Node #35

Node #62

Actual communications cycle time (response): The actual communicationscycle time is returned in units of 100 µs in hexadecimal.

Polling node address: The current polling node address is returned in hexade-cimal.

Data link operation (response): Indicates the status of data link operation inthe network.

Bit

Data link operational status0: Inactive 1: Active

70

6 5 4 3 2 1 000 0 0 0 0

Data link type (response): Indicates the data transmission status of the localnode’s data links. It is configured as shown in the following diagram. This param-eter is valid only during data link operation. While data link operation is inactive,the value from the previous operation is retained.

Bit

Local node data transmission status0: Transmission1: No transmission

70

6 5 4 3 2 1 000 0 0 0 0

Parameters


110

Data link recurring error status (response): Indicates whether an error con-tinues to occur at a node when data link data is received. If an error continues tooccur at the same node when the data is received, the bit corresponding to thatnode turns to “1” (i.e., turns ON). The configuration is shown in the following dia-gram.

Bit 776 5 4 3 2 1 0

6 5 4 3 2 1815 14 13 12 11 10 91623 22 21 20 19 18 172431 30 29 28 27 26 253239 38 37 36 35 34 334047 46 45 44 43 42 414855 54 53 52 51 50 4956– 62 61 60 59 58 57–

The numbers in the boxes indicate the nodeaddresses. The bit status of a particularnode address shows whether or not there isa recurring data link error at that node.

0: No recurring error1: Recurring error


Byte 1Byte 2Byte 3Byte 4Byte 5Byte 6Byte 7Byte 8

Data link data error counter (response): The total number of data link datareception errors occurring at all nodes (node addresses 1 to 32) is returned as atotal count from the time the power was turned on. It is expressed, in hexadeci-mal, as one byte per node. The count can range from 0 to 255 (i.e., 0 to FF inhexadecimal).

7 6 5 4 3 2 1 0Bit


Byte 1

Byte 2

Byte 3

Byte 32

Byte 33

Byte 62

Number of error occurrences for node #1






6-5-7 DATA LINK STATUS READReads the data link operational status.

Command Block

0306

Commandcode

Response Block

Responsecode

Commandcode

Status flagData link mode

Refreshcycle time

presentvalue

Refreshcycle timemaximum

value

Status

62 bytes06 03


111

Status flag (response): The overall data link status is returned in one byte ofdata, as shown in the following diagram.

Bit

Data link operational status0: Not active1: Active

1: Data link setting error

1: No data link table

Data link mode during operation0: Manual setting1: Automatic setting

7 6 5 4 3 2 1 00 0 0 0

Data link mode (response): The data link mode during operation is returned inone byte of data, as follows:

01 (Hex): Automatic 03 (Hex): Manual

Refresh cycle time present value, refresh cycle time maximum value(response): The present value and the maximum value of the cycle time forrefreshing the data link area are both returned in units of 1 ms, in hexadecimal,within a range of 0000 to 00FF (decimal: 0 to 255).Status (response): The data link status of each mode is returned as shown inthe following diagram. It is the same as the data link status in the PC. (Refer topage 77.)

7 6 5 4 3 2 1 0

–7 6 5 4 3 2 1 0Byte 1

Byte 2

Byte 3

Bit

Byte 62

Node #1

Node #2

Node #3

Node #62

Data link status for each node

PC status0: Inactive (user program not running)1: Active (user program running)




Offset error0:Normal1:Error

Error: Offset exceeds number of send words.

Insufficient (short) receive area0:Sufficient1:Insufficient

Insufficient: Receive area is smaller than send area.Excess data is truncated; other data is received.

Remaining receive area0:Not remaining1:Remaining

Remaining: Receive area is larger than send area.Data is received and remaining words are cleared.

Note 1. The data link status is not refreshed while the data links are inactive.

2. Nodes which are not active in the network or participating in the data linkswill generate communications errors.

3. Any node which is not active in the network retains the status that existedimmediately prior to the generation of the communications error.

4. Only the PC operation status and PC error status will be refreshed for nodesthat are not participating in a data link that is active in the network.

6-5-8 CONNECTION DATA READReads in order of connection (descending direction) the node addresses of Con-troller Link Units connected in a ring. This command can only be used in token-ring mode, for Optical Ring Controller Link Units (H-PCF cable).

Parameters


112

Command Block

0406

Commandformat Beginning node to read

Number of nodes read

Response Block

Commandcode

Node addresses read

06 04

Responsecode

Minute Day YearSecond Hour Month

Time connection data created Number of nodes read

Node address Node address

Beginning node to read (command): With the local node as the starting point(0), specify the node for beginning reading, with a 1-byte hexadecimal value (2digits) counted as 1, 2, etc., in the descending (SL2) direction. Set the value from00 to 3E Hex (decimal: 0 to 62).

Number of nodes read (command, response): For the command, specify thenumber of node addresses to read. All node addresses are read in order fromthe local node in the descending (SL2) direction. In the response, the number ofnodes actually read is returned, in the range of 01 to 3E Hex (decimal: 1 to 62).

With the command, the local node is read first regardless of the “beginning nodeto read” parameter setting. The number of other nodes addresses to read, there-fore, is the “number of nodes read” minus 1.

Time connection data created (response): The time that the connection con-figuration data was last changed is returned in one byte (2 digits) BCD for each ofthe following in order: minute, second, day, hour, year, month. The data ischanged with each communications cycle when in token-ring mode with a nor-mal ring connection.

The year setting is for the two rightmost digits of the year. The hour setting ismade from 00 to 23.

The time will be returned according to the time data set at the local node.

Node address (response): The node address for each node is returned in onebyte (2 digits) hexadecimal.

With this response, the node address of the local node is returned first, regard-less of the “beginning node to read” parameter setting. Then the rest of the nodeaddresses are returned in order from the node set in the “beginning node toread” parameter.

When the range specified in the “beginning node to read” and “number of nodesread” parameters is connected as a ring in relation to the local node, the nodeaddresses are read until the node which is one node in the ascending directionfrom the local node. This will result in a normal completion.

Parameters

Explanation


113

In the following network, for example, the beginning node to read is 25, and thenumber of nodes read is 6.

Node25

Beginning node to read

Local nodeNode6

Descending Ascending

Node32

Node31

Node11

Node12

Node15

Node19

The following node addresses will be returned as the response.

1F19

Node address 32

20

Node address 31

Node address 25 (beginning node to read)

Note 1. In the event of a disconnection, the last data that was changed and savedwill be returned.

2. If a node is down even though nothing is disconnected, it will be skipped overfor reading.

6-5-9 NETWORK DISCONNECT DATA READReads the disconnection status of the Controller Link Unit. This command canonly be used in token-ring mode, for Optical Ring Controller Link Units (H-PCFcable).

Command Block

0506

Commandformat

Response Block

Commandcode

06 05

Responsecode

Minute Day YearSecond Hour Month

Disconnectdetection

flag

Disconnectdetection

node data 1

Disconnectdetection

node data 2

4 bytes

Number ofnode/networkseparations

Number ofnetwork dis-connections

4 bytes

Number oflocal nodedisconnec-

tions

Max. numberof consecutive

disconnectcycles

Number offrame drop-outs

(SL1 side)

Number offrame drop-outs

(SL2 side)

Number offrame breaksdetected (SL1

side)

Number offrame breaksdetected (SL2

side)

Number ofCRC errors

detected(SL1 side)

Number ofCRC errors

detected(SL1 side)

4 bytes 4 bytes 4 bytes

4 bytes 4 bytes 4 bytes 4 bytes 4 bytes


114

Disconnect detection flag (response): Disconnection detections can be re-turned as follows:

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

0 0 0 0 0 0 0 0 0 0 0 0 0Bit

Local Node Disconnect Detection System Flag

Second byteFirst byte

Network Disconnect Flag0: Normal1: Disconnection detected

0: SL1 (Ascending)/Normal1: SL2 (Descending)

Local Node Disconnect Detection System Flag0: /Normal1: Disconnection detected

Disconnect detection node data 1, 2 (response): The node address of a nodefor which a detection is detected, along with the direction of detection at thatmode, are returned as follows:

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

0 0 0 0 0 0 0 0 0Bit

Disconnect detected node address

Second byteFirst byte

Disconnect Detection System Flag0: SL1 (Ascending)/Normal1: SL2 (Descending)

(00 Hex: No disconnect detected)

The data for the two modes is returned by “disconnect detect node data 1” and“disconnect detect node data 2.”Time of beginning disconnection data recording: The time that the record-ing of the disconnection data was begun is returned in one byte (2 digits) BCD foreach of the following in order: minute, second, day, hour, year, month.The time at which the last of the following was executed becomes the time forthis parameter: Local node powered up, Controller Link Unit restarted, or dis-connection data cleared.The year setting is for the two rightmost digits of the year. The hour setting ismade from 00 to 23.The time will be returned according to the time data set at the local node.Number of node/network separations (response): The number of times thatthe local node is separated from the network from the “time of beginning discon-nection data recording” onwards is returned in 4 bytes (8 digits) hexadecimal.Number of network disconnections (response): The number of times thatdisconnection data is received from the polling node from the “time of beginningdisconnection data recording” onwards is returned in 4 bytes (8 digits) hexadeci-mal. If the same disconnection data is continuously detected with each commu-nications cycle, however, it will be regarded as the same disconnection and willnot increase the count.Number of local node disconnections (response): The number of times thatdisconnection data is detected by the local node from the “time of beginning dis-connection data recording” onwards is returned in 4 bytes (8 digits) hexadeci-mal. If the same disconnection data is continuously detected with each commu-nications cycle, however, it will be regarded as the same disconnection and willnot increase the count.Maximum number of consecutive disconnect cycles (response): The maxi-mum number of consecutive cycles in which disconnection data from the pollingnode is detected is returned in 4 bytes (8 digits) hexadecimal. (The number iscounted starting from the “time of beginning disconnection data recording.”)

Parameters


115

A rough approximation of the time during which data may have been lost can beobtained by multiplying this value by the maximum communications cycle timefor the Controller Link Network.

Number of frame drop-outs (SL1, SL2) (response): This response indicatesthe number of times that the data (frame) was correctly received by another sys-tem but could not be received by the local system. (The total from the “time ofbeginning disconnection data recording” onwards is returned in 4 bytes (8 digits)hexadecimal.)

Number of frame breaks detected (SL1, SL2) (response): This response in-dicates the number of times that the data (frame) was correctly received byanother system but could not be detected at the local system except by carrier.(The total from the “time of beginning disconnection data recording” onwards isreturned in 4 bytes (8 digits) hexadecimal.)

Number of CRC errors detected (SL1, SL2) (response): This response indi-cates the number of CRC errors and Manchester errors. (The number is countedfrom the “time of beginning disconnection data recording” onwards.)

When a Optical Ring Controller Link Unit is used in the token-ring mode, the dis-connect detection and notification function can be used. With this function, whenthe Controller Link Unit detects a disconnection, it provides disconnection datato the polling node. All of the nodes in the network are then notified from the poll-ing node. For details on the disconnect detection and notification function, referto 9-4 Locating and Correcting Cable Disconnections.

Aside from the disconnect detection flag parameter, disconnection informationis not cleared even when communications are restored. (The present discon-nection status is always reflected in the disconnect detection flag parameter.)The disconnect detection node data 1 and 2 parameters, however, are overwrit-ten by new disconnection data.

To clear disconnection data, either execute NETWORK DISCONNECT DATACLEAR (FINS command) or use the Controller Link Support Software (Ver. 2.00or later). When clearing the disconnection data by executing a FINS command, itmust be done separately for each node.

6-5-10 NETWORK DISCONNECT DATA CLEARClears the Controller Link disconnection data. This command can only be usedin token-ring mode, for Optical Ring Controller Link Units (H-PCF cable).

Command Block

0606

Commandformat

Response Block

Commandcode

06 06

Responsecode

Aside from the disconnect detection flag parameter, disconnection informationis not cleared even when communications are restored. (The present discon-nection status is always reflected in the disconnect detection flag parameter.)The disconnect detection node data 1 and 2 parameters, however, are overwrit-ten by new disconnection data.

Explanation

Explanation


116

Execute this command to clear the disconnection data and restore the defaultstatus. Both the disconnection data in the Controller Link Unit and the ring statusin the CPU Bus Area of the CPU Unit will be cleared.

The time at which the disconnection data is cleared will be recorded in the Con-troller Link Unit as the “time of beginning disconnection data recording.”

The disconnection data will only be cleared at those nodes which receive thiscommand. For examples of programs for clearing the disconnection data fromthe entire network, refer to 9-4-4 Clearing the Ring Status Words.

The disconnection data can also be cleared using Controller Link Support Soft-ware (Ver. 2.00 or later). With this method, the disconnection data is cleared allat once for all of the nodes in the network.

6-5-11 ECHOBACK TESTExecutes an echoback communications test between specified nodes.

Command Block

Commandcode

Test data

1,998 bytesmax.

08 01

Response Block

Commandcode

Test data

1,998 bytesmax.

08 01

Responsecode

Test data (command, response): For the command, up to 1,998 bytes of datacan be specified to be sent to a specified node. For the response, the test datathat was sent by the command is returned unchanged.

An error is generated if the data returned by the response is different from thedata that was sent by the command.

6-5-12 BROADCAST TEST RESULTS READReads for each node the results (number of receptions) of a BROADCASTTEST DATA SEND command that has been sent to all nodes in a specified net-work. (For details on the BROADCAST TEST RESULTS SEND command, referto 6-5-13 BROADCAST TEST DATA SEND.

Command Block

0208

Commandcode

Response Block

Responsecode

Number ofreceptions

Commandcode

08 02

Number of receptions (response): The number of times that broadcast testdata has been received at the command remote node from the time that the last

Parameters

Parameters


117

BROADCAST TEST RESULTS READ command was sent until this one wassent is returned.

An error will be generated if that number of receptions differs from the number oftimes that the BROADCAST TEST DATA SEND command was issued duringthat same period.

The number of receptions value being retained at the remote node is clearedwhen the BROADCAST TEST RESULTS READ command is executed.

6-5-13 BROADCAST TEST DATA SENDBroadcasts test data to all nodes in a specified network.

Command Block

Commandcode

Test data

2,000 bytesmax.

08 03

There is no response to this command.

The control data must be set as follows when this command is issued:

Remote node address: FF (Hex) (for broadcasting the data)

Remote unit address: FE (Hex) (for the Controller Link Unit)

Response required/not required: 1 (response not required)

The transmission and reception status is checked by comparing the number oftimes this command is issued with the number of receptions parameter of theBROADCAST TEST RESULTS READ command. (For details, refer to 6-5-12BROADCAST TEST RESULTS READ.

6-5-14 ERROR LOG READReads the PC’s error log.

Command Block

0221

Commandcode

Beginningrecord no.

No. ofrecords

Response Block

0221

Max. no. ofstored records

No. ofstoredrecords

No. ofrecords

Error logdata

Error logdata

Responsecode

Commandcode

10 bytes 10 bytes

Beginning record no. (command): Specifies the first record to be read, in twobytes (four digits) in hexadecimal. (The first record number is 0000 in hexadeci-mal. Designate the record number within a range of 0000 to 0026 in hexadecimal(decimal: 0 to 38)).

No. of records (command and response): Specifies the number of records tobe read, within a range of 0001 to 0027 in hexadecimal (decimal: 1 to 39). Theresponse gives the number of records actually read.

Max. no. of stored records (response): Specifies the maximum number ofrecords that can be recorded, within a range of 0001 to 0027 in hexadecimal(decimal: 1 to 39).

Parameters

6-6SectionResponse Codes

118

No. of stored records (response): The number of records that have beenrecorded by the time the command is executed. The response will be given with-in a range of 0001 to 0027 hexadecimal (decimal: 1 to 39).

Error log data (response): The specified error log records are returned insequence starting from the beginning record number. The total number of bytesrequired is calculated as follows:

No. of records x 10 bytes

The configuration of each error record is as follows:

DetailsMinute

SecondDay Hour Year Month

Error code

1st byte 10th byte

Error code, details: These parameters show the contents of errors. Fordetails, refer to 9-3-2 Error Codes. Date and time: These parameters show the seconds, minutes, hour (0 to23), date, month, and year (the rightmost two digits) in BCD specifying thetime that the error occurred.

Note 1. If the PC does not have the specified number of records, all the records thathave been stored in the PC up to the point that the command is executed willbe returned.

2. If there is no error log registered, a response code of 1103 (Hex) will bereturned.

6-5-15 ERROR LOG CLEARClears all error log records and sets the error log pointer to 0.

Command Block

0121

Commandformat

Error clear

FF FF

Response Block

0321

Commandformat

Responsecode

6-6 Response CodesThis section describes the response codes returned with responses to FINScommands. Response codes can be used to confirm normal completion of com-mand execution or to troubleshoot problems when commands fail. For furthertroubleshooting information, refer to Section 9 Troubleshooting and Mainte-nance of this manual and to the operation manuals for specific Units or Systems.

6-6-1 ConfigurationResponse codes for FINS commands consist of two bytes that indicate the resultof executing a command. The structure of the response codes is shown in thefollowing diagram.


119

7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0Bit

1: PC Non-fatal Error Flag

1: PC Fatal Error Flag

1: Relay Error Flag

First byte Second byte

Main response code (MRES) Sub-response code (SRES)

The main response code (MRES) in the first byte classifies the response and thesub-response code (SRES) in the second byte indicates details under theMRES classification.If bit 7 of the first byte is ON, a network relay error has occurred. Refer to 6-6-2Network Relay Errors for details on troubleshooting the error.If bit 6 or 7 of the second byte is ON, an error has occurred in the PC or computerreturning the response. Refer to the operation manual for the device returningthe response for details when troubleshooting the error.

6-6-2 Network Relay ErrorsA network relay error will occur whenever a command cannot reach the destina-tion. These errors can occur for several reasons: 1) Data was not successfullypassed between two Link Units, 2) Data was not passed successfully between aLink Unit and another Unit, such as the PC’s CPU Unit, or 3) The destination of agateway does not exist. In any case, the Unit that was not able to transfer datawill return a response indicating a network relay error.Bit 7 of the first byte of the response code will be ON if a network relay error hasoccurred. When this happens, two more bytes of data will follow the responsecode to indicate the location of the error. This information, along with theresponse code, should enable you to track the error.

Bit

1: PC Non-fatal Error Flag

1: PC Fatal Error Flag

Error network address Error node address

0 0 0First word

Second word

Third word

Command code

1: Relay Error Flag

7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0

First byte Second byte

Main response code (MRES) Sub response code (SRES)

7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0

7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0

Error network address: 00 to 7F (Hex) (0 to 127 in decimal)Error node address: Controller Link: 01 to 3E (Hex) (1 to 62 in decimal) (*1)

Ethernet: 01 to 7E (Hex) (1 to 126 in decimal)SYSMAC NET: 01 to 7E (Hex) (1 to 126 in decimal)SYSMAC LINK: 01 to 3E (Hex) (1 to 62 in decimal)*1 This is 01 to 20 Hex (1 to 32) for Wired or Optical

Bus (CLK11) Controller Link Units.

A relay error indicates that the command did not reach the Unit to which it wassent. There are several types of situation in which this can occur. Example 1(below) shows a situation in which a relay error occurs when data cannot betransferred from one Communications Unit to another in an interconnected net-work. Example 2 shows a similar situation, except that the destination Unit issomething other than a Communications Unit. In Example 3, the relay erroroccurs because either the specified remote node or the next relay node does notexist.

Relay Errors


120

In the three diagrams, the numbers indicate the following:(1) The transmitted data fails to be received.(2) The relay error and response code are returned to the command

source.

In this example, data cannot be transferred between Controller Link Units due tosome cause such as a routing table error.


CPU: CPU Unit


SNT: SYSMAC NET Link Unit

TransmissionResponse

PS

CPU

PS

CPU

SNT

CLK

SNT

1

PS

CPU

CLK

12 MRES – – SRES

In this example, data cannot be transferred between a Controller Link Unit and aCPU Unit.


CPU: CPU Unit



PS

CPU

CLK

1

PS

CPU

CLK

12 MRES– – SRES

In this example, the specified remote node or the next relay node does not exist.


CPU: CPU Unit


SNT: SYSMAC NET Link Unit


PS

CPU

CLK

CLK

PS

CPU

CLK

SNT

1

PS

CPU

CLK

12 MRES– – SRES

If an error occurs, check the MRES and SRES codes for the node in question,and correct the problem.

6-6-3 Response Codes and TroubleshootingThe table below lists response codes (main and sub-codes) returned afterexecution of the FINS commands, the probable cause of errors, and recom-mended remedies.Upon receipt of some commands, the remote node will issue a request toanother node; the other node is referred to as the third node.

Main code Sub-code

Probable cause Remedy

00: Normal completion 00 --- ---

01 Service was interrupted Check the contents of the destinationtransmission area of third node.Check the data link status.

Example 1

Example 2

Example 3


121

Main code RemedyProbable causeSub-code

01: Local node error 01 Local node not part of Network Add to Network.

02 Token time-out, node address toolarge

Set the local node’s node address belowthe maximum node address.

03 Number of transmit retries exceeded Check communications with ECHOBACKTEST. If the test fails, check network.

04 Maximum number of frames exceeded Either check the execution of events in thenetwork and reduce the number of eventsoccurring in one cycle, or increase themaximum number of frames.

05 Node address setting error (range) Correctly set the Controller Link BIOS /Noption. Make sure the node address iswithin specified range and that there areno node addresses that are set twice.

06 Node address duplication error Make sure that there are no nodeaddresses that are set twice.

02: Remote node error 01 Remote node not part of Network Add to Network.

02 No node with the specified nodeaddress

Check the remote node’s node address.

03 Third node not part of Network Check the third node’s node address.

Broadcasting was specified. Check the control data and specify onlyone node as the third node.

04 Busy error, remote node busy Increase the number of transmit retryattempts or re-evaluate the system so thatthe remote node is not so busy receivingdata.

05 Response time-out, message packetwas corrupted by noise

Increase the number of transmit retryattempts.

Response time-out, response watch-dog timer interval too short

Increase the value for the response watch-dog timer interval in the control data.

Frame lost in transmission Check the error log and correct theprocess.

03: Communicationscontroller error

01 Error occurred in the communicationscontroller, ERC indicator is lit

Take corrective action, referring tocommunications controller errors andremedies table at end of this section

02 CPU Unit error occurred in the PC atthe remote node

Clear the error in the CPU Unit (refer to thePC’s operation manuals)

03 A controller error has prevented anormal response from being returned.

Check network communications status andreset the controller board. If the error stillexists, replace the controller board.

04 Unit address setting error Make sure the Unit address is within thespecified range and that there are no nodeaddresses that are set twice.

04: Not executable 01 An undefined command has beenused.

Check the command code and be surethat the Unit supports it.

02 Cannot process command becausethe specified unit model or version iswrong.

Check the unit model and version.

05: Routing error 01 Remote node address is not set in therouting table.

Set the remote node address in the routingtable.

02 Routing table isn’t registered. Set the local nodes, remote nodes, andrelay nodes in the routing table.

03 Routing table error Set the routing table correctly.

04 The maximum number of relay nodes(2) was exceeded in the command.

Redesign the network or reconsider therouting table to reduce the number of relaynodes in the command.


122


10: Command formaterror

01 The command is longer than the max.permissible length.

Check the command format of thecommand and set it correctly.

02 The command is shorter than min.permissible length.


03 The designated number of data itemsdiffers from the actual number.

Check the number of items and the data,and make sure that they agree.

04 An incorrect command format hasbeen used.


05 An incorrect header has been used.(The local node’s relay table or relaynode’s local network table is wrong.)

Set the routing table correctly.

11: Parameter error 01 A correct memory area code has notbeen used or Extended Data Memoryis not available.

Check the command’s memory area codeand set the appropriate code.

02 The access size specified in thecommand is wrong, or the firstaddress is an odd number.

Set the correct access size for thecommand.

03 The first address is in an inaccessiblearea.

Set a first address that is in an accessiblearea.

04 The end of specified word rangeexceeds the acceptable range.

Check the acceptable limits of the dataarea and set the word range within thelimits.

Check the data link tables to be sure thelimit to link words has not been exceeded.

06 A non-existent program no. has beenspecified.

Check the program number and be surethat it is set correctly.

09 The sizes of data items in thecommand block are wrong.

Check the command data and be sure thatthe sixes of the data items are correct.

Check the data link tables to be sure allnodes in the refresh parameters are in thecommon link parameters.

0A The IOM break function cannot beexecuted because it is already beingexecuted.

Either abort the current IOM break functionprocessing, or wait until it is completed andexecute the command.

Check the data link tables for nodeaddresses that have been set twice.

0B The response block is longer than themax. permissible length.

Check the command format and set thenumber of items correctly.

0C An incorrect parameter code has beenspecified.

Check the command data and reenter itcorrectly.

Check the data link table file for corruption.


123


20: Read not possible 02 The data is protected. Execute the instruction again after issuingthe PROGRAM AREA PROTECT CLEARcommand to the PC.

An attempt was made to download afile that is being uploaded.

Check the file name and either interruptservicing or wait for servicing to completebefore re-executing the command.

03 The registered table does not exist oris incorrect.

Set or reset the registered table.

Too many files open. Close open files and re-execute thecommand.

04 The corresponding search data doesnot exist.

---

05 A non-existing program no. has beenspecified.


06 A non-existing file has been specified. Check whether the correct file name wasused.

07 A verification error has occurred. Check whether the memory contents arecorrect and replace if incorrect.

Check the contents of the file. A read errormay have occurred.

21: Write not possible 01 The specified area is read-only or iswrite-protected.

If the specified area is read-only, the writecannot be performed. If it iswrite-protected, turn off the write-protectswitch and execute the instruction again.

02 The data is protected. Execute the instruction again after issuingthe PROGRAM AREA PROTECT CLEARcommand to the PC.

An attempt was made tosimultaneously download and uploada file.

Check the file name and either interruptservicing or wait for servicing to completebefore re-executing the command.

The data link tables cannot be writtenmanual because the Unit is set forautomatic generation.

Change the data link mode to manual.

03 The number of files exceeds themaximum permissible.

Write the file(s) again after erasingunneeded files, or use different disk orMemory Card that has free space.

Too many files open. Close open files and re-execute thecommand.

05 A non-existing program no. has beenspecified.


06 A non-existent file has been specified. Check the file name and execute again.

07 The specified file already exists. Change the name of the file and executethe instruction again.

08 Data cannot be changed. ---


124


22: Not executable in 01 The mode is wrong (executing). Check the operating mode.current mode Data links are active. Check the data link status before

execution.02 The mode is wrong (inactive). Check the operating mode.

Data links are active. Check the data link status beforeexecution.

03 The PC is in the PROGRAM mode. Check the PC’s mode.

04 The PC is in the DEBUG mode. Check the PC’s mode.

05 The PC is in the MONITOR mode. Check the PC’s mode.

06 The PC is in the RUN mode. Check the PC’s mode.

07 The specified node is not the controlnode.

Check which node is the control node.

08 The mode is wrong and the stepcannot be executed.

Check whether the step has active statusor not.

23: No Unit 01 A file device does not exist wherespecified.

Mount the Memory Card or disk

02 The specified memory does not exist. Check the specifications of the installed filememory.

03 No clock exists. Check the model number.

24: Start/stop notpossible

01 The data link tables either have notbeen created or are incorrect.

Set the data link tables correctly.

25: Unit error 02 Parity/checksum error occurredbecause of incorrect data.

Transfer correct data into memory.

03 I/O setting error (The registered I/Oconfiguration differs from the actual.)

Either change the actual configuration tomatch the registered one, or generate theI/O table again.

04 Too many I/O points Redesign the system to remain withinpermissible limits.

05 CPU bus error (An error occurredduring data transfer between the CPUUnit and a CPU Bus Unit.)

Check the Unit, Service Boards, and cableconnections and issue the ERROR CLEARcommand.

06 I/O duplication error (A rack number,unit number, or I/O word allocationhas been duplicated.)

Check the system’s settings and eliminateany settings that occur twice.

07 I/O bus error (An error occurred duringdata transfer between the CPU Unitand an I/O Unit.)


09 SYSMAC BUS/2 error (An erroroccurred during SYSMAC BUS/2 datatransfer.)


0A Special I/O Unit error (An erroroccurred during CPU Bus Unit datatransfer.)


0D Duplication in SYSMAC BUS wordallocation.

Check and regenerate the I/O table.

0F A memory error has occurred ininternal memory, in the Memory Card,or in Expansion DM during the errorcheck.

If the error occurred in internal memory orthe EM Unit, correct the data in thecommand an execute it again.

If the error occurred in a Memory Card orEM used for file memory, the file data hasbeen corrupted. Execute the MEMORYCARD FORMAT command for the PC.

If the above remedies do not eliminate theerror, replace the faulty memory.

10 Terminator not connected in SYSMACBUS System.

Connect the terminator correctly.


125


26: Command error 01 The specified area is not protected.This response code will be returned ifan attempt is made to clear protectionon an area that is not protected.

The program area is not protected, so itisn’t necessary to clear protection.

02 An incorrect password has beenspecified.

Specify a password that is registered.

04 The specified area is protected. Execute the command again afterexecuting the PROGRAM AREAPROTECT CLEAR command for the PC.

To many commands at destination. The destination has received more than 5commands. Either interrupt servicing orwait for servicing to complete beforere-executing the command.

05 The service is being executed. Execute the command again after theservice has been completed or aborted.

06 The service is not being executed. Execute the service if necessary.

07 Service cannot be executed from localnode because the local node is notpart of the data links.

Execute the service from a node that ispart of the data links.

A buffer error has prevented returninga normal response.

Reset the board. If the error persists,replace the board.

08 Service cannot be executed becausenecessary settings haven’t beenmade.

Make the necessary settings.

09 Service cannot be executed becausenecessary settings haven’t been madein the command data.

Check the command format of and makethe necessary settings.

0A The specified action or transitionnumber has already been registered.

Execute the command again using anaction or transition number that hasn’tbeen registered.

0B Cannot clear error because the causeof the error still exists.

Eliminate the cause of the error andexecute the ERROR CLEAR command.

30: Access right error 01 The access right is held by anothernode.

(Either a Programming Device at theother node is executing an SFC onlineedit, or the other node is executing anACCESS RIGHT ACQUIRE orACCESS RIGHT FORCED ACQUIREcommand.)

Execute the command again after theaccess right has been released.

(The command can be executed after theACCESS RIGHT FORCED ACQUIRE orACCESS RIGHT RELEASE command iscompleted. Releasing the access rightmight affect processes in progress at thenode that held the access right.)

40: Abort 01 Command was aborted with ABORTcommand.

---

127

SECTION 7Network Interconnections

This section describes the methods used to connect multiple networks through CS1-series, CVM1, and CV-series PCs. Thesection also describes remote programming and monitoring with Programming Devices.

7-1 What is Network Interconnection? 128. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1-1 Interconnecting Controller Link Networks 128. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1-2 Interconnecting Different Types of Networks 128. . . . . . . . . . . . . . . . . . . . . . . . . . . .

7-2 Remote Programming and Monitoring 130. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2-1 Within the Same Network 130. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2-2 Remote Controller Link Networks 131. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2-3 Other Remote Networks 132. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7-3 Routing Tables 132. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4 Setting Routing Tables 133. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7-4-1 Routing Table Setting Procedure 134. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4-2 Editing Local Network Tables 135. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4-3 Editing Relay Network Tables 135. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4-4 Saving Routing Tables 136. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4-5 Connecting to the PC 136. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4-6 Transferring Routing Tables 136. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4-7 Example Routing Table Settings 136. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7-1SectionWhat is Network Interconnection?

128

7-1 What is Network Interconnection?Network interconnection enables commands and responses for the messageservice to be sent and received across multiple networks. The four networkslisted below can be interconnected to achieve this.

FA Networks

• SYSMAC NET Link Networks

• SYSMAC LINK Networks

• Controller Link Networks

OA Network

• Ethernet Networks

7-1-1 Interconnecting Controller Link Networks

Controller Link Networks can be connected through a CS1-series, CVM1, or CV-series PC.

Controller Link Network(Token-bus)

CS1-series, CVM1,C200HX/HG/HE, orCV-series PC (See note 1.)

Note 1. Only the token-bus mode can be used with the C200HX/HG/HE Se-ries.

2. A data bridge is created between Controller Link Unitsmounted on the same CS1-series, CVM1, or CV-series PC.

Controller Link Network (Token-ring)

CS1-series, CVM1, orCV-series PC (See note 2.)

7-1-2 Interconnecting Different Types of Networks

A CS1-series, CVM1, or CV-series PC can be used to connect a Controller LinkNetwork with an Ethernet, SYSMAC NET, or SYSMAC LINK Network.

Note A data and communications protocol gateway is created betweena Controller Link Unit and an Ethernet, SYSMAC NET, or SYS-MAC LINK Unit mounted to the same CVM1, CV-series PC.

Controller Link Network (Token-ring) Ethernet Network

CS1-series, CVM1, orCV-series PC

CS1-series, CVM1, orCV-series PC (See note.)

Note 1. A bridge is used between Communications Units to connect the same typeof networks.

7-1SectionWhat is Network Interconnection?

129

2. A gateway is used between Communications Units to connect differenttypes of networks.

Bridge Gateway

Data DataData and communications

protocol gateway

PCController Link Controller Link

PCController Link SYSMAC NET

• A CQM1H-series PC supports only one Communications Unit. It cannot func-tion as a data bridge or a data and communications protocol gateway.

• Communications across bridges or gateways can include up to three net-works, including the local network (data generating network).

Network 1 (local network) Network 2 Network 3

Although 2,012 bytes of data (including the header) can be sent and receivedwith a Controller Link, the maximum amount of data is limited by any network thedata passes through, i.e., the network with the the smallest capacity will deter-mine the limit.

If, for example, data passes through a SYSMAC LINK network as shown in thefigure on the preceding page, the amount of data sent and received from theController Link is limited to 552 bytes (including the header) because the SYS-MAC LINK Network can only handle that many bytes.

See the manual for the network you are using in order to determine the maxi-mum amount of data for each network.

7-2SectionRemote Programming and Monitoring

130

7-2 Remote Programming and MonitoringA remote PC can be programmed and monitored across a network from a Pro-gramming Device connected to a PC.

7-2-1 Within the Same Network

SYSMAC Support Software and CV Support SoftwareA Programming Device connected to a CVM1, or CV-series CPU Unit can pro-gram and monitor a CVM1, or CV-series PC on the same network. Programmingand monitoring are possible, however, only for the same type of CPU Unit as theone to which the Programming Device is connected. For example, if the Pro-gramming Device is connected to a CVM1 or CV-series PC, you can only pro-gram and monitor CVM1 or CV-series PCs on the network.

SYSMAC SupportSoftware (CVM1 only)or CV Support Software

Note Remote programming and monitoring is not possible from an FA computerused as a node. Computer nodes can only monitor Controller Link Networkstatus. An FA computer can only be used in token-bus mode.


Programming Device

Programmingand monitoring

CVM1 or CV-series PC CVM1 or CV-series PC

Controller LinkSupport Software(Ver. 2.00)

Controller Link Network (Token-bus)

CX-ProgrammerA CX-Programmer connected to a CS1-series, C200HX/HG/HE, CVM1, CV-se-ries, or CQM1H CPU Unit can program and monitor a CPU Unit on the samenetwork. Programming and monitoring are possible, including CPU Units thatare different to the one to which the Programming Device is connected.

CX-Programmer Programming Device


Note 1. Using CX-Programmer, remote programming and monitoring are possible froman FA computer used as a node, but the FA computer can only be used in token-bus mode.

2. C200HX/HG/HE PCs can only be used in token-bus mode (wired).


Controller Link Network (Token-bus)




CS1-series, CVM1, CV-series, or C200HX/HG/HE PC

7-2SectionRemote Programming and Monitoring

131

7-2-2 Remote Controller Link Networks

SYSMAC Support Software or CV Support SoftwareA Programming Device connected to a CVM1 or CV-series CPU Unit can pro-gram and monitor a CVM1 or CV-series PC on another Controller Link Networkthrough a CVM1 or CV-series PC. Other types of PC cannot be programmed ormonitored on remote networks.

Controller Link Network(Token-ring)

SYSMAC SupportSoftware (CVM1 Only)or CV Support Software

Programming Device

Note 1. Remote programming and monitoring is not possible from an FA computer used as a node. Com-puter nodes can only monitor Controller Link Network status. An FA computer can only be used intoken-bus mode.

2. A Programming Device connected to a C200HX/HG/HE PC cannot remotely program or monitor anode on a remote network.



Controller LinkSupport Software(Ver. 2.00)

CS1-series PC

CVM1 orCV-series PCCS1-series, CVM1,

or CV-series PC

CS1-series PC




CX-ProgrammerA CX-Programmer connected to a CS1-series, CVM1, CV-series, or CQM1H-series CPU Unit can program and monitor any other PC on another ControllerLink Network. Other types of PC, different to the one to which the CX-Program-mer is connected can also be programmed or monitored on remote networks.

Note 1. Remote programming and monitoring is possible from an FA computer used as anode, but the FA computer can only be used in token-bus mode.





Controller LinkSupport Software CS1-series PC

CX-Programmer

CS1-series PC


CS1-series, CVM1, CV-se-ries, or C200HX/HG/HE, PC





7-3SectionRouting Tables

132

7-2-3 Other Remote Networks

SYSMAC Support Software or CV Support SoftwareA Programming Device connected to a CVM1 or CV-series CPU Unit can pro-gram and monitor a CVM1 or CV-series PC on a different type of network (SYS-MAC NET or SYSMAC LINK) through a CVM1 or CV-series PC. Other types ofPC cannot be programmed or monitored on remote networks.

Note 1. Remote programming and monitoring is not possible from an FA computer used as anode. Computer nodes can only monitor Controller Link Network status. An FA com-puter can only be used in token-bus mode.

2. A Programming Device connected to a C200HX/HG/HE PC cannot remotely pro-gram or monitor a node on a remote network.

SYSMAC NETSYSMAC SupportSoftware (CVM1 Only)or CV Support Software

Programming Device


CVM1 or CV-series PCCVM1 or CV-series PC

CVM1 or CV-series PC

Controller LinkSupport Software CVM1 or CV-

series PC

SYSMAC NET



CX-ProgrammerA CX-Programmer connected to a CS1-series, CVM1, or CV-series CPU Unitcan program and monitor any other PC on a different type of network (Ethernet,SYSMAC NET, or SYSMAC LINK) through a CS1-series, CVM1, or CV-seriesPC.

Note 1. Remote programming and monitoring is possible from an FA computer usedas a node, but the FA computer can only be used in token-bus mode.


Ethernet Network


Ethernet Network


CS1-series, CVM1,or CV-series, PC

CS1-series,CVM1, or CV-series PC

CS1-series PC

Controller LinkSupport Software CS1-series

PC

CX-Programmer

CVM1 or CV-seriesPC

CS1-series,C200HX/HG/HE, CVM1, orCV-series, PC



7-3 Routing TablesRouting tables that define the communications path from the Controller Link Uniton the local PC to the network connected to the destination PC must be createdin order to send and receive data across networks. Each CPU Unit implements

7-4SectionSetting Routing Tables

133

the message service or remote programming/monitoring to the appropriate Unitaccording to the routing tables.

Creating Routing TablesRouting tables consists of a local network table and a relay network table.

A local network table provides unit numbers and network addresses corre-sponding to the Units mounted to the PC.

Unit number 04Unit number 05Unit number 06

Network address 1Network address 2Network address 3Network address 4

ExampleLocal network table

Local networkaddress Unit number

2 05

3 06

4 07

1 04

Unit number 07

Note 1. The unit number is set between 0 and 15 using the rotary switch on the frontpanel of Controller Link Units for CS1-series, CVM1, and CV-series PCs.

2. The network address is the address of the network connected to the Unit(between 1 and 127). The address is set when the local network table iscreated.

A relay network table provides the node and network addresses correspondingto the initial relay point (first point the data must go to) en route to a target net-work (end network) not directly connected to the local PC.The table traces the route from the relay point to the end network.The example below shows the routing tables for the route from local node PC1(network address 1, node address 1) to PC4 (network address 3, node address2).

Localnetworkaddress

Local node PC1

Nodeaddress1

Relay node PC2Relay nodePC3

Node address 2Unit number 0

Node address 1Unit number 1

Destination

Destinationnode PC4

End networkPC1 relay network table PC2 relay network table PC3 local network table

Endnetwork

Relaynetwork Unit number

Data first goes tonode address 3 atnetwork address 1 toreach networkaddress 3.

Data then goes tonode address 2 atnetwork address 2to reach networkaddress 3.

We know from thelocal network tablethat the data goesthrough local unitnumber 1 to reachnetwork address 3.

Data goes tonode address 2at networkaddress 3, i.e.,the localnetwork.

Network address 1 Networkaddress 2

3

2 1 3

3 1 1

2 0

3

3 2 2

Nodeaddress2

Nodeaddress3

Nodeaddress 1

Networkaddress 3

Endnetwork

Relaynetwork

Relaynode

Relaynode

Node address 2

7-4 Setting Routing TablesThis section describes routing table settings.

Local Network Table

Relay Network Table


134

Routing tables are set through the CX-Net (in CX-Programmer), SYSMAC LINK,or Controller Link Support Software. This section describes setting proceduresand setting details.

See the operating manual of the Programming Device you are using for the spe-cific setting procedure.

Note 1. Routing tables cannot be set through Programming Consoles.

2. Networks cannot be crossed by a Programming Device without setting rout-ing tables. Routing tables can therefore be set only for nodes connected tothe Programming Device and other nodes in the same network. Disconnectand reconnect the Programming Device to each network when setting rout-ing tables in multiple networks.

3. Make sure that the routing tables are properly set at all nodes on the net-work. If a message is sent to a node without correct routing tables, transmis-sion will not work properly and a response may not be returned.

4. When using a CVM1 or CV-series CPU Unit manufactured prior to April1996, be sure to register routing tables whether or not the PC is connectingmultiple networks. The date of production can be checked on the lot numberas explained below. (The lot number is a four-digit number written on theside panel of the CPU Unit.)




Note Routing tables are required if any of the CVM1 or CV-series CPU Units inthe network have been manufactured on or before April 1996.

7-4-1 Routing Table Setting ProcedureThe procedure for setting routing tables is described below.

1, 2, 3... 1. Edit the local network table.

2. Edit the relay network table.

3. Save the routing tables.

4. Connect the Programming Device to a PC.

5. Transfer the routing tables.

Repeat the editing andsaving steps for allnodes set with the rout-ing tables.


135

7-4-2 Editing Local Network TablesUse the routing table editing function on the Programming Device to edit thelocal network table as shown on the screen given below.

Local network: Address 1 through 127 for the network connected to the Communications Unit

SIOU Unit No.: Unit number of the Communications Unit. (CS1-series, CVM1, or CV-series: 0 to15) Set the unit number of all Communications Units (SYSMAC NET Link Units,SYSMAC Link Units and Controller Link Units) as well as the address of networkconnected to it.

Be sure to set the same address for each network when setting routing tables(local and relay network tables) in multiple PCs.

7-4-3 Editing Relay Network TablesUse the routing table editing function on the Programming Device to edit thelocal network table as shown on the screen given below.

End network: Network address of the end network (1 through 127)

Relay network: Network address of the first relay point on the way to the end network (1 through127)

Relay node: Node address of the first relay point on the way to the end network (SYSMAC NET: 1 through 126, SYSMAC LINK: 1 through 62, and ControllerLink (Wired or Optical Bus): 1 through 32, Ethernet: 1 through 127)

Set all networks not directly connected to the PC.

Be sure to set the same address for each network when setting routing tables(local and relay network tables) in multiple PCs.

!


136

Note The PC ID is any unique name given to a specific node.When setting the PC ID, simply input the ID. Network and node addresses will beinput for you automatically. See the operation manual for SYSMAC, CV, or Con-troller Link Support Software for further details.

7-4-4 Saving Routing TablesAfter editing local and relay network tables on the Programming Device, savethe tables.

Note When setting routing tables in multiple PCs, edit and save all routing tables andthen transfer them together to work more efficiently.

7-4-5 Connecting to the PCConnect the Programming Device to a PC in the network to transfer the routingtables. All PCs receiving the routing table settings must have power turned ONfor the transfer.

Note The Programming Device must be disconnected and then reconnected to a PCon each network.

7-4-6 Transferring Routing TablesRouting tables saved on a Programming Device can be read from memory andtransferred to the PCs on the network. First load and transfer routing tables tothe PC connected to the Programming Device. This enables networks to be dis-tinguished even when multiple Communications Units are connected, and itenables routing tables to be transferred to other nodes on the network.

Once routing tables are transferred to the PC connected to the ProgrammingDevice as well as all nodes on the same network, disconnect the ProgrammingDevice, reconnect it to a PC on another network, and repeat the procedure.

Caution CPU Bus Units are reset when routing tables are transferred from a Program-ming Device to a PC to allow set routing tables to be read. Make sure that reset-ting CPU Bus Units will not cause equipment damage or dangerous systembehavior before transferring tables.

7-4-7 Example Routing Table SettingsThis section shows examples of routing table settings.

The example below shows local network table settings when multiple CPU BusUnits are mounted in a single CVM1 or CV-series PC.

Example 1


137

CLK SNT RM BSC CPU PS

12

AB

(d)(c)

Unit number dUnit number cUnit number bUnit number a

SYSMAC BUS/2 SystemController Link SystemNetwork address A

PS: Power Supply UnitCPU: CPU UnitSNT: SYSMAC NET Link UnitCLK: Controller Link UnitRM: SYSMAC BUS/2 Remote I/O MasterBSC: BASIC Unit

No.Loc

NetwkSIOUunit #

Local Network Table

PCacting asbridge

SYSMAC NET Link SystemNetwork address B

Do not register SYSMAC BUS/2 Master Units and BASIC Units in local networktables because these Units do not connect to networks.

The following example show the settings for a relay network table connectingthree networks.

12

BC

AA

bb

12

AC

BB

ce

12

AB

CC

ff

1 C B e

1 A B c

Relay Network Tables

No. EndNetwk

RelayPC ID Netwk Node

No. EndNetwk

No. EndNetwk

No.End

Netwk

No. EndNetwk

Networkaddress A

Networkaddress B

Networkaddress C

PC 1

Node address a

PC 2

Node address bNode address c

PC 3

Node address d

PC 4

Node address eNode address f

PC 5

Node address g





On closer examination of the relay network table for PC#, we see that the relaynetwork is B and the relay node is c when network A is the destination, and thatthe relay network is B and the relay node is e when network C is the destination.

Example 2


138

The network structure example in the figure below shows routing tables for allnodes.

SNT PC

CLK PCSNT SNT PCCLK

CLK PC CLK PC CLK PC CLK PC

(1)

(2) (3)

(4) (5) (6) (7)

Unit 5Node 6

Unit 3Node 4

Unit 4Node 5

Unit 2Node 3

Unit 7Node 15

Unit 6Node 10

Unit 5Node 5

Unit 1Node 2

Unit 0Node 1

Network 10

Network 30Network 20

Routing Tables on PC 1

12

020 010 00412

010 05

3 3030 010 005

Relay Network TableLocal Network Table

No. EndNetwk


No. LocNetwk

SIOUunit#


12

030 010 00512

010 03

3 3


No. EndNetwk


No. LocNetwk

SIOUunit#

020 02


12

020 010 00412

010 04

3 3


No. EndNetwk


No. LocNetwk

SIOUunit#

030 07


12

010 020 00312

020 00

3 3030 020 003


No. EndNetwk


No. LocNetwk

SIOUunit#

Example 3


139


12

010 020 00312

020 01

3 3030 020 003


No. EndNetwk


No. LocNetwk

SIOUunit#


12

010 030 01512

030 05

3 3020 030 015


No. EndNetwk


No. LocNetwk

SIOUunit#


12

010 030 01512

030 06

3 3020 030 015


No. EndNetwk


No. LocNetwk

SIOUunit#

141

SECTION 8Communications Timing

This section explains details on Controller Link Network communications. Refer to this section for network communicationsthat require accurate communications timing.

8-1 Communications Mechanism 142. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-1 Data Transmissions over the Network 142. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-2 Setting the Polling and Polled Nodes 143. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-3 Network Parameters 143. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1-4 Specifying Network Parameters 144. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8-2 Communications Cycle Time 144. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2-1 Active Data Links 145. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2-2 Inactive Data Links 146. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2-3 Maximum Delay for Disconnections in Token-ring Mode 147. . . . . . . . . . . . . . . . . .

8-3 Data Link I/O Response Time 148. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3-1 Data Exchange Timing 148. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3-2 Data Processing Time 149. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3-3 Calculation Example 149. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8-4 Message Delay Times 153. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4-1 CS1-series, CVM1, and CV-series PCs 153. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8-1SectionCommunications Mechanism

142

8-1 Communications Mechanism

8-1-1 Data Transmissions over the Network

Controller Link

Token (right to send)

In a Controller Link Network, token passing is used to control network access.The right to send, called a “token,” circulates around the network. A node thatreceives the token is allowed to send data. If the node has data to send, it willattach the data to the token and send them together. If the node has no data tosend, it will pass the token to the next node.

Receive the token

When there isdata to send

Where there isno data to send

Data

Attaches data to the token and send them together

Passes the token to the next node

A token can be thought of as a circulating envelope. This envelope is circulatedthrough the network and the person who receives the envelope will put a des-tination and a memo into the envelope to send his or her message to somebodyelse. This method is called “token passing.” The Optical Bus Controller Link Net-work is a bus network that uses token passing.

The Optical Ring Controller Link Network supports the token-ring mode, in whichthe transmission path can be duplicated by wiring the communication cable in aloop. (When wired in bus format, token-bus mode is used.)

The overall network communications procedure is explained below.

1, 2, 3... 1. The Unit at the node that manages the network, called the “polling node,”transfers the token. The token is circulated through the network in ascend-ing order of node addresses. One cycle in which the token is circulatedamong all nodes on the network is called a “token circulation cycle.”

2. After one token circulation cycle is complete, the polling node checks thenetwork connection status. One cycle in which the connection status of allnodes on the network is checked is called a “polling cycle.”

3. After one polling cycle is complete, the polling node transfers the tokenagain.

The procedure is then repeated. In a Controller Link Network, the total timerequired for a token circulation cycle and a polling cycle is called the “commu-

8-1SectionCommunications Mechanism

143

nications cycle time.” Communications processing is executed by repeating thecommunications cycle.

Check

Token circulationcycle

Polling cycle

Communications cycle time

Check

Polling cycleToken circulationcycle

Communications cycle time

Each Controller Link Network always has a Unit that controls communicationswithin the network. This Unit is called the “polling node.” Normally, the node thathas the smallest node address in the network is the polling node (see note). AllUnits at nodes other than the polling node are called “polled nodes“ (or polledunits). The polling node controls the token, checks the network, and performsother relevant tasks. Should the polling node break down, the node with the nextsmallest node address is automatically selected as the polling node to preventthe entire network from shutting down.

Note The node with the smallest node address is not always the polling node, depend-ing on the Unit start-up sequence, models, settings, and Unit status.

With an Optical Bus Controller Link Unit or Board, when the polling node breaksdown the next polling node is temporarily disconnected from the network, recon-structs the network, and then reconnects to the network. Polling nodes remainconnected to the network.

With an Optical Ring Controller Link Unit, when the polling node is shifted, thenew polling node is not disconnected from the network.

8-1-2 Setting the Polling and Polled NodesUse the Programming Device for the PC to set Units as polling node or pollednode in the DM parameter area.

CS1-series Controller Link Units

0 0 0 0 0 0 0 015 14 13 12 11 10 9 8

0 0 – – 0 0 0 –7 6 5 4 3 2 1 0

DM 30000 + 100N

N: Unit number

–: Other settings

Polling node/polled node bit0: Polling node 1: Polled node

CVM1 and CV-series Controller Link Units

0 0 0 0 0 0 0 015 14 13 12 11 10 9 8

0 0 – – 0 0 0 –7 6 5 4 3 2 1 0

DM 2000 + 100N

N: Unit number

–: Other settings


If the node is always to be connected as a polled node when the power is turnedon, set it as a polled node. If the node can become a polling node when the poweris turned on, set it as a polling node. One of the nodes set as a polling node willserve as the actual polling node. Except for maintenance after Unit replacement(see 9-6 Handling Precautions), set the Units all nodes as polling nodes (set thepolling node/polled node bit to “0”).

8-1-3 Network ParametersNetwork parameters are also used to control network operations. Networkparameters are read from the polling node and distributed to all other nodes

Polling Node

8-2SectionCommunications Cycle Time

144

when the Controller Link Network is started. In this way, all nodes on the networkalways have the same network parameter settings. If nodes are connected tothe network halfway during network operation, the network parameter settingswill also be distributed to these nodes when they are connected. The followingthree network parameters can be specified.

This parameter specifies the maximum node address of nodes to be checked bythe polling node. The default is 62 (or 32 for Optical Bus Networks). Reducingthe setting of this parameter reduces the number of nodes checked by the pol-ling node and can thus avoids unnecessary check operations. However, if thenetwork contains nodes with node addresses greater than the setting of theparameter, these nodes will not be connected to the network.

This parameter specifies the number of nodes to be checked (polled) by the pol-ling node during each polling cycle. The default is 4. Setting this parameter to ahigh value increases the communications cycle time, but reduces the timerequired to recognize that nodes have been removed from or added to the net-work. Reducing the setting of this parameter shortens the communications cycletime but delays a network response when a node is disconnected from or con-nected to the network.

This parameter specifies the maximum number of event frames (communica-tions other than data links, such as message service transmissions) that can betransferred during a communications cycle. Specify a value in units of 128 bytes.The default is 35 (128 35 = 4,480 bytes).

Increasing the setting of this parameter increases the communications cycletime but allows for more event communications such as the message service.Too small a parameter value restricts event communications, resulting in anerror. See 8-2 Communications Cycle Time (on page 144) for the effects of net-work parameters on communication cycle times.

8-1-4 Specifying Network ParametersThe network parameters can be specified from the Controller Link Support Soft-ware. This section describes only the allowable setting range for each networkparameter. Refer to the Controller Link Support Software Operation Manual(W308) for setting procedures.

The following table shows the setting range and default for network parameters.

Network parameter Settingrange

Default value

Maximum node address 2 to 62 62 (See note1.)

Number of polled nodes 1 to 31 4

Maximum number of event-frames 6 to 238 35

The network parameters become valid immediately after being set.

Note 1. The default value is 32 for Optical Bus Networks.

2. Always stop the data link before changing network parameters.

3. Specify a value for the maximum node address that is equal to or greaterthan the maximum node address in the Controller Link Network.

4. For the CVM1 and CV-series PCs, always set the System Protect KeySwitch on the CPU Unit to NORMAL. Otherwise, the network parameter set-tings will not be stored normally.

8-2 Communications Cycle TimeThis section describes how to calculate the communications cycle time.

Maximum Node Address

No. of Polled Nodes PerCommunications Cycle

No. of Event-frames perCommunications Cycle


145

8-2-1 Active Data LinksThe following equations are used to calculate the communications cycle timewhen data links are operating.Token-ring Mode9.1 × A +1,740 × B + 960 × C + 1,100 × D + 4 × E + 2 × F + 4,800 (µs)

Token-bus Mode9.1 × A +1,300 × B + 290 × C + 320 × D + 4 × E + 2 × F + 2,290 (µs)

Note A: Total number of data link words within the network (total number of words in send areas of all nodes)

B: Number of polled nodes per comm cycle(value specified in the network parameters)

C: Number of nodes connected to the networkD: Number of nodes that send messages during the

communications cycleE: Total number of bytes in messages transmitted during the

communications cycleF: Extra communications time for long distance Optical Fiber Cable

connections. F = 7 × L µs (L is the cable length in km.)

The number of bytes in each message differs according to the instruction beingissued, as shown in the following table.

Instruction When sent When received

SEND Number of words to be sent 2+ 18

14

RECV 18 Number of words to be received 2 + 14

CMND Number of bytes in commanddata + 10

Number of bytes in responsedata + 10

Communications conditions are as follows:

Transmission distance: 8 km

Transmission speed: 2 Mbps

Network parameters: Defaults

Max node address: 62

Polled nodes per comm cycle: 4

Event-frames per comm cycle: 35

Network configuration: 8 nodes

Total number of data link words: 8,000 words

Nodes that send messages: 2 nodes

Bytes in all messages sent: 2,012 2 bytes

In this example, A to E in the equation have the following values.A: 8,000B: 4C: 8D: 2E: 4,024F: 7 × 8

The communications cycle time in token-ring mode is thus as follows:

9.1 × 8,000 + 1,740 × 4 + 960 × 8 + 1,100 × 2 + 4 × 4,024 + 2 × 7 × 8 + 4,800 =110,648 (µs) ≅ 111 (ms)

And the communications cycle time in token-bus mode is as follows:9.1 × 8,000 + 1,300 × 4 + 290 × 8 + 320 × 2 + 4 × 4,024 + 2 × 7 × 8 + 2,290 =99,458 (µs) ≅ 100 (ms)

Calculation Example


146

8-2-2 Inactive Data LinksThe following equations are used to calculate a communications cycle timewhen the data link is inactive.

Token-ring Mode1,740 × B +450 × C + 1,100 × D + 4 × E + 2 × F + 3,000 (µs)

Token-bus Mode1,300 × B + 110 × C + 320 × D + 4 × E + 2 × F + 1,800 (µs)

Note B: Number of polled nodes per communications cycle(value specified in the network parameter)

C: Number of nodes connected to networkD: Number of nodes that send messages during the

communications cycleE: Total number of bytes in messages transmitted during the

communications cycleF: Delay time in the fiber-optic cable transmission path:

7 x (µs), where the cable length in km.

The number of bytes in each message differs according to the instruction beingissued, as shown in the following table.

Instruction When sent When received

SEND Number of words to be sent 2 + 18

14

RECV 18 Number of words to bereceived 2 + 14

CMND Number of bytes in commanddata + 10

Number of bytes in responsedata + 10

Communications conditions are as follows:

Transmission distance: 8 km

Transmission speed: 2 Mbps

Network parameters: Defaults

Max node address: 62

Polled nodes per comm cycle: 4

Event-frames per comm cycle: 35

Network configuration: 8 nodes

Nodes that send messages: 2 nodes

Bytes in all messages sent: 2,012 2 bytes

In this example, B to E in the equation have the following values.

B: 4C: 8D: 2E: 4,024F: 7 × 8

The communications cycle time in token-ring mode is thus as follows:

1,740 × 4 + 450 × 8 + 1,100 × 2 + 4 × 4,024 + 2 × 7 × 8 + 3,000 = 31,968 (µs)≅ 32 (ms)

And the communications cycle time in token-bus mode is thus as follows:

1,300 × 4 + 110 × 8 + 320 × 2 + 4 × 4,024 + 2 × 7 × 8 + 1,800 = 24,728 (µs)≅ 25 (ms)

Calculation Example


147

8-2-3 Maximum Delay for Disconnections in Token-ring ModeAlthough the redundant transmission paths in Token-ring Mode ensure thatcommunications will continue even if there is one disconnection, the commu-nications cycle time will be affected. The data that is received first from the tworeception interfaces (SL1 and SL2) will be used. A disconnection, however, maycause the data that should arrive first to be lost, causing a delay before the datais received on the other interface. The delay will thus be the time difference be-tween receiving the same data on the two reception interfaces (assuming it wasreceived). This delay will occur at each node as the right to send is passed, andthe maximum delay in the overall cycle time will be the sum of the delay at eachnode.On a Controller Link Network, the right to send is passed at the following times.• When the token is passed.• When the nodes being checked from the polling node for network participation

change (depends on the number polled nodes per cycle set in the network pa-rameters)

• When different nodes send messages requiring responsesThe delay in the cycle time will depend on where the disconnection occurs, butthe time to pass the right to send can be reduced by connecting nodes in order ofnode address.

The maximum delay in the communications cycle time can be calculated as fol-lows when the nodes are connected in order of node address.(A × 4 + B × 2 + 1) × (3 × C + D) (µs)

Where, A: Number of polled nodes per cycle

(value specified in the network parameter)B: Number of nodes that send messages during the cycleC: Number of nodes participating in the networkD: Delay time in the fiber-optic cable transmission path

7 x (µs), where the cable length in km.

Communications conditions in this example are as follows:Transmission distance: 8 kmTransmission speed: 2 MbpsNetwork parameters: DefaultsMax node address: 62Polled nodes per comm cycle: 4Event-frames per comm cycle: 35Network configuration: 8 nodesNodes that send messages: 2 nodesBytes in all messages sent: 2,012 2 bytes

In this example, A to D in the equation have the following values.A: 4; B: 2; C: 3; D: 7 × 8

The maximum communications cycle delay in token-ring mode would be as fol-lows:

(4 × 4 + 2 × 2 + 1) × (3 × 8 + 7 × 8) = 1,680 (µs) ≅ 1.7 (ms)

The rate of change in the communications cycle time when data links are activewould be as follows (refer to 8-2-1 Active Data Links):

(111 + 1.7)/111 × 100 ≅ 101.6 (%)The rate of change in the communications cycle time when data links are inac-tive would be as follows (refer to 8-2-2 Inactive Data Links):

(32 + 1.7)/32 × 100 ≅ 105.3 (%)

Maximum Cycle TimeDelay for NetworksConnected in Order ofNode Addresses

Calculation Example

8-3SectionData Link I/O Response Time

148

8-3 Data Link I/O Response TimeWhen accurate communications timing is required, you need to understand dataexchange timing and the time required for data transmission and reception viadata links. Use the information described in this section as reference informationfor system construction.

8-3-1 Data Exchange TimingThis section describes data exchange timing for data links between the Control-ler Link Unit and the PC’s CPU Unit. Data exchange is executed as interrupt pro-cessing during CPU Bus Unit or Programming Device/Host Link servicing per-formed by the CPU Unit. This interrupt processing is executed each time dataexchange between the local node and each node connected via a data link iscompleted.

Data exchange timing differs depending on the CPU Unit model and the CPUUnit the Execute Process (asynchronous or synchronous) specified in PCSetup, as described below.

When a CVM1 or CV-series CPU Unit is operating in asynchronous mode, dataexchange with the Controller Link Unit is executed as interrupt processing dur-ing peripheral processing, regardless of the cycle time of PC instruction execu-tion. Data exchange timing is as follows:

Instruction execution

PC cycle time

Execution

I/O refreshing

PC processing

Peripheral processing

Peripheral servicing interval

Basic processing

CPU BusUnit service

ProgrammingDevice/Host Linkservice

Interrupt processingfor data exchange

Execution Execution

I/O refreshing I/O refreshing



Basic processing

CPU BusUnit service


CPU BusUnit service


Basic processing

More than one data exchange can be executed during a PC cycle, depending onthe data exchange timing. If interrupt processing for data exchange is executed,the peripheral servicing interval will be lengthened by the time required for theinterrupt processing (see 8-3-2 Data Processing Time on page 149).

When a CS1-series, CVM1, or CV-series PC is operating in synchronous mode,data exchange with the Controller Link Unit is executed as interrupt processingduring peripheral processing for the PC cycle. Data exchange timing is as fol-lows:

PC cycle time

ExecutionPC processing

Basic processing Interrupt processingfor data exchange

Execution

I/O refreshing Basic processing

CPU BusUnit service


If interrupt processing for data exchange is executed, the PC cycle time will belengthened by the time required for the interrupt processing (see 8-3-2 Data Pro-cessing Time below).

CVM1 and CV-series PCsUnder AsynchronousOperation

CS1-series PCs, CVM1and CV-series PCs inSynchronous Mode


149

8-3-2 Data Processing TimeThe time required for interrupt processing for data exchange (data processingtime) can be roughly estimated as shown in the following table.

Data link scale Equation for estimating data processing time

Data link is established for both areas 1 and 2 0.001 Total number of data link words 1.7 (ms)

Data link is established for only area 1 or area 2 0.001 Total number of data link words 1.4 (ms)

The number of words processed in a single data exchange is shown in the fol-lowing table for each series of PC. If the number of data link words exceeds thevalue shown in the table, data exchange will be executed as several separateprocesses.

PCs Words per data exchange

CS1-series PCs Approx. 7,800 words

CVM1 and CV-series PCs Approx. 3,700 words

Note 1. Use the above equations only if only one Controller Link Unit is mounted onthe PC. If other CPU Bus Units are mounted on the PC, obtain the refreshtimes for each CPU Bus Unit and add to the above equations.

2. The execution of some items takes precedence over data link area refresh-ing. For example, data link area refreshing will not take place during execu-tion of the SEND(192), RECV(193), or FAL(006) instruction.

8-3-3 Calculation ExampleThe data links of the Controller Link Unit require a slight time delay from the timethe data link area of one node is changed until this change is reflected in the datalink area at another node. This time delay is called the data link I/O responsetime. The following is a calculation example of the maximum and minimum I/Oresponse times for the system configuration shown below.

PC PCCLK#1

CLK#7

Input

LRXXXX OutputLRXXXX

CLK: Controller Link Unit System configuration

Connection method: Token-ring modeTransmission distance: 8 kmMaximum node address: 62Number of polled nodes per comm cycle: 4Number of event-frames per comm cycle: 35Nodes in network: 8 nodesNodes in data links: 8 nodesWords sent in area 1: 8 words per nodeWords in area 2: 16 words per node

No messages communications are performed.

A single Controller Link Unit is mounted to each CPU Rack.

Input

The data link I/O response time depends on the communications cycle time,input ON delay, output ON delay, and the cycle times of the PCs involved. Thevalues are detailed below.

Communications cycle time =9.1 × (8 + 16) × 8 + 1,740 × 4 + 960 × 8 + 2 × 7 × 8 + 4,800 =21,299 µs ≅ 22 ms

The input ON delay is the time it takes for an input device to turn ON an input tothe PC after receiving an input signal. In this system the input ON delay is1.5 ms.

The output ON delay is the time it takes for an output device to turn ON an outputsignal after receiving an output from the PC. In this system the output ON delayis 15 ms.

Communications CycleTime

Input ON Delay

Output ON Delay


150

The cycle time of the PC at node #1 is 15 ms or 8 ms.

The cycle time of the PC at node #7 is 20 ms or 8 ms.

CVM1, CV-series, CS1-series PCs Under Synchronous Operation

Maximum Data Link I/O Response Time

Input device

Program

Program

Input

Input ON delay

1 cycle

Output

Output device

Output ON delay

1 cycle

Communicationscycle time

Data link transmission

PC at node #7

I/O refresh

Data exchange

PC at node #1

Data link I/O response time

There are three points shown in the diagram above where processing isdelayed, increasing the data link I/O response time.

1, 2, 3... 1. The input arrives in the PC just after I/O refreshing, causing a delay of up toone cycle before the input is read into the PC.

2. Data exchange occurs just after the PC at node #1 passes the token thatmakes it the polling node, causing a delay of up to one communicationscycle time before the data is transferred in data link processing.

3. At node #7, data from the previous data exchange is still being transferred,causing a delay of up to one cycle before the input is read into the PC. (If thecycle time at node #7 is longer than the communications cycle time, theprocessing will be delayed for two cycles.) Also, if the total number of datalink words exceeds the maximum number for a single exchange, the dataexchange will be divided up and there may be a delay of an additional cycle.

The maximum number of words that can be exchanged in a single dataexchange is approx. 7,800 words for CS1-seres PCs and approx. 3,700words for CVM1 and CV-series PCs.

The equation for the maximum data link I/O response time is as follows:

Input ON response time 1.5 ms

Cycle time of PC at node #1 2 25 ms × 2

Communications cycle time 2 22 ms × 2

PC cycle time at node #7 2 10 ms × 2

Output ON response time 15 ms

Total (data link I/O response time) 130.5 ms

Noise may increase I/O delays.

Cycle Times


151

Minimum Data Link I/O Response Time

Input device

Program

Program

Input

Input ON response time1 cycle

Output

Output device

Output ON response time

1 cycle

PC at node #7

I/O refreshData exchange

PC at node #1


There are three points shown in the diagram above where processing isdelayed, increasing the data link I/O response time.

In this case, the data processing time required for data exchange and the timerequired for the data transmission itself cannot be ignored, so they are includedin the total. The respective values are as follows:

Data processing time:0.001 × (8 + 16) × 8 + 1.7 = 1.89 ≅ 1.9 ms

Data transmission time:

The following formula is derived according based on the transmissionspeed.0.008 × (8 + 16) = 0.19 ≅ 0.2 ms

Input ON response time 1.5 ms

Cycle time of PC at node #1 25 ms

Data processing time 1.9 ms

Data link transmission time 0.2 ms


PC cycle time at node #7 10 ms

Output ON response time 15 ms




152

CVM1 and CV-series PCs Under Asynchronous OperationMaximum Data Link I/O Response Time

InputInput device

Input ON response time

1 cycle

Program PC at node #1

PC at node #7

Data link transmission

Communicationscycle time

Output device

Output ON response time

OutputData link I/O response time


I/O refresh

1 cycle


Program

There are five points shown in the diagram above where processing is delayed,increasing the data link I/O response time.

1, 2, 3... 1. The input arrives in the PC just after I/O refreshing, causing a delay of up toone cycle before the input is read into the PC.

2. Data exchange occurs just after the PC at node #1 passes the token thatmakes it the polling node, causing a delay of up to one communicationscycle time before the data is transferred in data link processing.

3. At node #7, data from the previous data exchange is still being transferred,causing a delay of up to one cycle before the input is read into the PC.

4. The data transferred in data link processing arrives at the PC at node #7after data exchange, so the data will not be read into the PC until the nextdata exchange, causing a delay of up to one peripheral servicing interval.

Up to 3,700 words can be transferred in a single data exchange, so a delayof another peripheral servicing interval will occur if more than 3,700 wordsare being transferred.

5. The data is received after the PC at node #7 has executed the instruction,causing a delay of up to one cycle time.

Assume that the peripheral servicing interval of the PCs at nodes #1 and #7 is10 ms. The equation for the maximum data link I/O response time is as follows:

Input ON delay 1.5 ms

Cycle time of PC at node #1 × 2 25 ms × 2

Peripheral servicing interval of PC atnode #1

10 ms

Communications cycle time × 2 22 ms × 2

Peripheral servicing interval of PC atnode #7 × 2

10 ms × 2

PC cycle time at node #7 × 2 10 ms × 2

Output ON delay 15 ms


8-4SectionMessage Delay Times

153


Minimum Data Link I/O Response TimeInput

Input device

Input ON delay1 cycle

I/O refresh

PC at node #1

PC at node #7



Output device

OutputON delay


Program

Data link transmissionData processing time

Data processing time

Program

In this case, the data processing time required for data exchange and the timerequired for the data transmission itself cannot be ignored, so they are includedin the total. The respective values are as follows:

Data processing time:0.001 × (8 + 16) × 8 + 1.7 = 1.89 ≅ 1.9 msData transmission time:The following formula is derived according based on the transmissionspeed.0.008 × (8 + 16) = 0.19 ≅ 0.2 ms

Assume that the sum of the instruction execution time and I/O refresh time forthe PCs at nodes #1 and #7 is 1 ms. The equation for minimum data link I/Oresponse time is as follows:

Input ON delay 1.5 ms

Instruction execution time + I/O refreshtime for PC at node #1

1 ms


Data link transmission time 0.2 ms


Instruction execution time + I/O refreshtime for PC at node #7

1 ms

Output ON delay 15 ms



8-4 Message Delay TimesThe two charts which follow indicate the sequence of processing which willenable users to calculate the maximum delay time to be expected betweenthe time SEND(192) or RECV(193) is executed and the time the data isstored in the destination or source node’s memory area, ready for use byother instructions in the program.

8-4-1 CS1-series, CVM1, and CV-series PCsThe following diagram indicates the data flow which will yield the maximumdelay time from the time SEND(192)/SEND(90) is executed by the user program

SEND


154

to the time the Controller Link Unit stores the data in the destination Unit’smemory.

Note Be sure to take into account the time required for data links and program execu-tion, which are not included in the following example.

SEND executed

Link Unit servicing (source node)

Transmission processing

Communications cycle

Data stored

Reception processing

Max. transmission delay

Link Service processing (source node)

Link Service processing(destination node)

Transmission delay

Link Serviceprocessing(source node)

Max. transmission delay = Link Unit servicing interval (source node) + Link ser-vice processing (source node) + Transmission processing + Communicationscycle time + Transmission delay + Reception processing + Link Unit servicinginterval (destination node) + Link service processing (destination node)

Link Servicing Interval (Source and Destination Nodes)Link servicing depends on the execution mode of the PC. The execution modeson the source and destination modes need not be the same.

For synchronous execution, links are serviced once per PC execution cycle. Forasynchronous execution, links are serviced according to the peripheral servic-ing interval. Refer to the operation manual for the PC for details. Refer to theCVM1 and CV-series PCs Operation Manual: Ladder Diagrams (W202) orCS1-series PCs Programming Manual (W340) for details.

Link Service Processing (Source and Destination Nodes)Link service processing is the same as the PC’s peripheral servicing and isapproximately 1 ms for Controller Link Units.

Transmission ProcessingNumber of words transferred × 0.00075 ms + 2 ms

Communications Cycle Time (with Data Links Inactive)See 8-2 Communications Cycle Time (on page 144).

Transmission Delay TimeNumber of words transferred × 0.008 + 0.112 ms

Reception ProcessingNumber of words transferred × 0.00075 + 1.3 ms

Note The I/O response time can increase due to noise or restrictions on the number offrames that can be transmitted while data links are operating.


155

ExampleIn this example, the maximum transmission delay is calculated for an instructionsending 256 words of data in a system with 62 nodes. Network specifics aredetailed below:

Transmission speed: 2 MbpsMax. node address: 62Number of nodes: 62Number of polled nodes per comm cycle: 4Source node execution: SynchronousDestination node execution: AsynchronousNumber of words: 256Data link: Inactive

Link servicing interval (source node) PC cycle time (source node)

Link service processing (source node) 1 ms

Transmission processing 0.00075 × 256 + 2 = 2.192 ≅ 2.2 ms

Communications cycle time (see note) 1,300 × 4 + 450 × 62 + 1,100 × 0 + 4× 0 + 3,000 = 36,100 µs ≅ 36.1 ms

Transmission delay 0.008 × 256 + 0.112 = 2.16 ≅ 2.2 ms

Reception processing 0.00075 × 256 + 1.13 = 1.492 ≅1.5 ms

Link servicing interval (destination node) As required by Programming Device

Link service processing (destination node) 1 ms

Total (max. transmission delay) PC cycle time (source node) +Peripheral servicing interval (des-tination node) + 44.0 ms

Note This communications cycle time is calculated assuming that there is no nodethat transmits event frames before the SEND command is sent.

The data flow which will yield the maximum transfer interval from the time theRECV(193)/RECV(98) instruction is executed by the user program to the timethe Controller Link Unit stores the data in the local Unit’s memory area isdescribed below.

Note Be sure to take into account the time required for data links and program execu-tion, which are not included in the following example.

RECV (193)/RECV(98)executed

Data stored

Link service interval (source node)

Transmission processing (command) Reception processing (response)

Communications cycle

Reception processing (command)

Link service interval (destination mode)

Transmission delay (command)

Link service processing (source node)

Transmission delay (response)

Transmission processing (response)

Link service processing (destination node)

Maximum transmission delay

Link service processing (source node)

RECV InstructionMaximum Delay Time


156

Max. transmission delay = Link servicing interval (source node) + Link serviceprocessing (source node) + Transmission processing (command) + Commu-nications cycle + Transmission delay (command) + Reception processing (com-mand) + Link servicing interval (destination node) + Link service processing(destination node) + Transmission processing (response) + Communicationscycle + Transmission delay (response) + Reception processing (response) +Link servicing interval (source node) + Link service processing (source node).

Link Servicing Interval (Source and Destination Nodes)Link servicing depends on the execution mode of the PC. The execution modeson the source and destination modes need not be the same.

For synchronous execution, links are serviced once per PC execution cycle. Forasynchronous execution, links are serviced according to the peripheral servic-ing interval. Refer to the CVM1 and CV-series PCs Operation Manual: LadderDiagrams (W202) for details.

Link Service Processing (Source and Destination Nodes)Link service processing is the same as the PC’s peripheral servicing and isapproximately 1 ms for Controller Link Units.

Transmission ProcessingCommands: 2 msResponses: Number of words transferred × 0.00075 ms + 2 ms

Communications Cycle Time (with Data Links InactiveSee 8-2 Communications Cycle Time (on page 144).

Transmission Delay TimeNumber of words transferred × 0.08 + 0.112 ms

Note Commands: Transmission delay time is calculated assuming that the number ofwords to be transferred is zero. Responses: Transmission delay time is calculated according to the number ofwords to be transferred.

Reception ProcessingCommands: 1.3 msResponses: Number of words transferred × 0.00075 ms + 2 ms

The I/O response time can increase due to noise or restrictions on the number offrames that can be transmitted while the data link is operating.


157

ExampleIn this example, the maximum transmission delay is calculated for an instructionreceiving 256 words of data in a system with 62 nodes. Network specifics aredetailed below:

Transmission speed: 2 MbpsMax. node address: 62Number of nodes: 62Number of polled nodes per comm cycle: 4Source node execution: SynchronousDestination node execution: AsynchronousNumber of words: 256Data link: Inactive

Link Unit servicing (source node) × 2 PC cycle time (source node) × 2

Link service processing (source node) × 2 1 ms × 2 = 2 ms

Transmission processing (command) 2 ms

Communications cycle × 2 (see note) (1,300 × 4 +450 × 62 + 1,100 × 0 + 4× 0 + 3,000) × 2 = 36,100 µs × 2 ≅72.2 ms

Transmission delay (command) 0.112 ≅ 0.1 ms

Reception processing (command) 1.3 ms

Link servicing interval (destination node) As required by Programming Device(destination node)

Link service processing (destination node) 1 ms

Transmission processing (response) 0.00075 × 256 + 2 = 2.192 ≅ 2.2 ms

Transmission delay (response) 0.008 × 256 + 0.112 = 2.16 ≅ 2.2 ms

Reception processing (response) 0.00075 × 256 + 2 = 2.192 ≅ 2.2 ms

Total (max. transmission delay) PC cycle time (source node) × 2 +Peripheral servicing time (des-tination node) + 85.2 ms

Note This communications cycle time is calculated assuming that there is no nodethat transmits event frames before the RECV command is sent.

159

SECTION 9Troubleshooting and Maintenance

This section provides information on troubleshooting errors that occur during Controller Link Unit operation, as well as dailyinspection, cleaning, and other maintenance procedures.

9-1 Troubleshooting Using Indicators 160. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1-1 CS1-series Controller Link Units 160. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1-2 CVM1 and CV-series Controller Link Units 166. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9-2 Status Area and Troubleshooting 171. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2-1 CS1-series Controller Link Units 171. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2-2 CVM1 and CV-series Controller Link Units 177. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9-3 Error Log 183. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3-1 Error Log Table 183. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3-2 Error Codes 184. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3-3 Reading and Clearing Error Logs 190. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9-4 Locating and Correcting Cable Disconnections 191. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4-1 Notification of Network Cable Disconnections 191. . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4-2 Cable Disconnection Examples 194. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4-3 Correction of Network Cable Disconnections 196. . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4-4 Clearing the Ring Status Words 197. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4-5 Reading the Ring Status 202. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9-5 Cleaning and Inspection 204. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5-1 Cleaning 204. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5-2 Inspection 204. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9-6 Handling Precautions 205. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6-1 Replacing the Unit 205. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6-2 Setting the Unit after Replacement 205. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6-3 Replacing the Unit 207. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9-1SectionTroubleshooting Using Indicators

160

9-1 Troubleshooting Using IndicatorsThis section describes the errors indicated by the Controller Link Unit indicatorsand possible remedies.

9-1-1 CS1-series Controller Link Units

RUN: OperatingPS: Power being suppliedERC: Communications errorRING: Transmission path formatERH: PC errorINS: Network participationM/A: Data link modeLNK: Data link

CS1-series Optical RingController Link Unit(H-PCF Cable)

CS1-series Optical BusController Link Unit

RUN PSERC ERHRING MAINS LNKSD RD

RUN PSERC ERHRING MAINS LNKSD

Troubleshooting with RUN, P/S, ERC, ERH, RING, and INS IndicatorsThe RUN, P/S, ERC, ERH, RING, and INS indicators can be used to checkwhether Controller Link Unit startup and Network participation are operatingnormally.

Note Be sure to turn off the power to the PC before performing any of the following.

• Disconnecting the Unit or connectors.

• Securing Units or connectors.

• Setting hardware switches.

The following CIO words contain information on the status of the Controller LinkUnit. These words are referenced in the “Status area” column in the followingtable.

Error Information: CIO 1500 + 25 × (Unit No.) (See page 171)

Ring Status: CIO 1500 + 25 × (Unit No.) + 23 (See page 174)

Power Status: CIO 1500 + 25 × (Unit No.) + 24 (See page 177)

Indicators Status area Error Probable cause Probable remedy

RUN P/S ERC ERH RING INS code

Lit --- Notlit

Notlit

Lit Lit --- --- The Unit startednormally in tokenring mode andentered thenetwork normally.

---

Lit --- Notlit

Notlit

Not lit Lit --- --- The Unit startednormally in tokenbus mode andentered thenetwork normally.

---


161

Indicators Probable remedyProbable causeErrorcode

Status area

RUN

Probable remedyProbable causeErrorcode

Status area

INSRINGERHERCP/SNotlit

--- Notlit

Notlit

Not lit Notlit

--- --- Power is not beingsupplied correctlyto the PC.

Check the powersupply voltageand supply at therecommendedvoltage.

The ControllerLink Unit hasbecome loose.

Secure theController LinkUnit firmly.

The ControllerLink Unit ismounted in thewrong slot.

Refer to 3-2-2CS1-series PCs inInstallation andmount the Unitcorrectly.

The ControllerLink Unit is faulty.

If the indicators donot light when theUnit is mounted inanother PC,replace theController LinkUnit.

--- Lit --- --- --- --- Power status:Bit 11 ON

Error information:Bit 15 ON

0216 Hex The status of thebackup powersupply changed.(Backup powerbeing supplied.)

The backup powersupply may havegone OFF orcome ON if errorcode 0216 isrecorded in theerror log.

If possible, turnON the backuppower first andleave it ON duringoperation.

--- Notlit

--- --- --- --- Power status:Bit 11 OFF


0216 Hex The status of thebackup powersupply changed.(Backup powernot beingsupplied.)



Check the backuppower supply andits cables.

Notlit

--- Lit Notlit

--- Notlit

--- --- Controller LinkUnit faulty.

If the ERCindicators stilllights when theUnit is mountedon another PC,replace theController LinkUnit.


0214 Hex The node addressis outside thesetting range.

Set the nodeaddress to withinthe 1 to 62 range.(For theCS1W-CLK11, therange is 1 to 32.)


162


Status area

RUN


Status area

INSRINGERHERCP/S--- --- Lit Not

lit--- Not

litError information:Bits 12 and 15 ON

021B Hex Hardware error incommunicationscontroller.

Replace theController LinkUnit.

Error information:Bits 11 and 15 ON

0210 Hex Error in thecommunicationscontroller’stransmitter.


Lit --- Lit --- --- Notlit


0211 Hex The same nodeaddress is beingused by twodifferent Units.

Change so thateach nodeaddress in theNetwork is unique.

The transmissionpath format settingdoes not matchthe setting in thepolling node.

Change thesetting to matchthe one in thepolling node andturn the power ONagain.

Lit --- --- Lit --- --- Error information:Bit 15 ON

0001 Hex An error hasoccurred in thePC.

Refer to the PC’soperation manualand correct theerror. If the erroroccurs again,replace the PC.


0203 Hex There is an errorin the networkparameters storedin the ControllerLink Unit’sEEPROM.

Set the networkparameters again.If the error occursagain, replace theController LinkUnit.

021A Hex The networkparameter settingsare incorrect orthe local nodeaddress is largerthan the maximumnode address setin the networkparameters.

Set the networkparameters again.


0203 Hex There is an errorin the data linktables stored inthe Controller LinkUnit’s EEPROM.

Set the data linktables again. If theerror occursagain, replace theController LinkUnit.

021A Hex The data link tablesettings areincorrect.

Set the data linktables again.Delete the datalink tables if theyaren’t being used.


0203 Hex There is an errorin the routing tablein the PC’s routingtable area.

Set the routingtables again. If theerror occursagain, replace thePC.

021A Hex Routing tablesetting error

Set the routingtables again.Delete the routingtables if theyaren’t being used.


163


Status area

RUN


Status area

INSRINGERHERCP/SLit --- --- --- --- Not

lit--- --- Cables are not

connectedcorrectly.

Check the cableconnections arereconnectcorrectly.

The node addressis larger than themaximum nodeaddress set in thenetworkparameters.

Either change themaximum nodeaddress settingwith the ControllerLink SupportSoftware (Ver.2.00 or higher) orset a nodeaddress below themaximum.

No other nodesexist.

Make sure that 2or more nodesexist within theNetwork.

No node has beenset as the pollingnode.

Refer to 8-1-2Setting the Pollingand Polled Nodesand set theController LinkUnit as the pollingnode.(If both types ofoptical Units areused in a network,use the OpticalRing Units aspolled nodes.)

The transmissionpath format settingis different in thepolling node.


--- --- --- --- Flashing Lit Ring status:Bit 15 ON


021D Hex A break wasdetected in thenetwork cable.(Networkoperationcontinues.)

Determine thelocation of thebreak with theController LinkSupport Software(Ver. 2.00 orhigher) or the ring

--- --- --- --- Flashing Notlit

Ring status:Bit 15 ON


021D Hex A break wasdetected in thenetwork cable.(The Unit was outof the networkafter the error.)

higher) or the ringstatus word.Correct the break.Refer to 9-4Locating andCorrecting CableDisconnections fordetails.


164

Troubleshooting with LNK and M/A IndicatorsThe following table describes the LNK and M/A indicators at the startup nodeand their use in troubleshooting when a data link cannot be started.

Starting a data link depends on the Controller Link Unit operating normally andparticipating in the Network. Refer to Troubleshooting with RUN, ERC, ERH andINS Indicators earlier in this section and check Unit operation before using thefollowing table.

Indicators Probable cause Probable remedy

LNK M/A

Lit --- Data link operating normally. ---

Flashing --- There is an error in the datalink tables.

When the ERH indicator isflashing, remake and set thedata link tables.

When manual setting is used,either data link tables havenot been created for thestartup node or there is anerror in the data link tables.

Refer to 5-2-2 Manual Settingand set data link tables for thestartup node.

When automatic setting isused, either the data linkparameters for the startupnode have not been set orthere is an error in the datalink tables.

Refer to 5-2-4 AutomaticSetting and set the automaticparameters for starting thedata links.

Not lit Lit Manually set data links arealready operating on thesame Network.

Stop the manually set datalinks that are operating andrestart the data links.

Not lit Not lit Automatically set data linksare already operating on thesame Network.

Stop the automatically setdata links that are operatingand restart the data links.

There is an error in thestartup node PC.

Refer to the PC’s operationmanual and correct the error.If the error reoccurs, replacethe PC.

Data Link Cannot beStarted


165

The following table describes the LNK and M/A indicators when a node cannotparticipate in the data links.

Data link participation depends on the Controller Link Unit operating normallyand participating in the Network. Refer to Troubleshooting with RUN, ERC, ERHand INS Indicators earlier in this section and check Unit operation before usingthe following table.


LNK M/A


Flashing Lit When manual setting is used,there is an error in the datalink table.

Refer to 5-2-2 Manual Settingand remake the data linktable.

Flashing Not lit When automatic setting isused, the data linkparameters at the startupnode are incorrect for thelocal node (the data link areais out of range for the localnode.)

Refer to 5-2-4 AutomaticSetting, reset the parametersfor the startup node DM Areaso that the local node canparticipate in the data link,and then restart the data link.

When automatic setting isused, the local node is not setto participate in the data linkat the startup node.

Stop the data link, reset theparameters for the startupnode DM Area so that thelocal node can participate inthe data link, and then restartthe data link.

Not lit Lit When manual setting is used,there are no data link tablesset for the local node.

Set data link tables for thelocal node.

Stopping the data link depends on the Controller Link Unit operating normallyand participating in the Network. Read the above explanations before attempt-ing to stop operation.

Note Stop the data link from the node at which the LNK indicator is lit (indicating activedata links). Data links cannot be stopped from nodes which do not have activedata links.

Node Cannot Participatein Data Link

Data Link Cannot beStopped


166

9-1-2 CVM1 and CV-series Controller Link Units

Optical Ring Controller Link Unit (H-PCF Cable)

RUN: OperatingPS: Power being suppliedERC: Communications errorRING: Transmission path formatERH: PC errorINS: Network participationM/A: Data link modeLNK: Data link

RUN PSERC ERH

RING MAINS LNKSD RD

Troubleshooting with RUN, ERC, ERH, RING and INS IndicatorsThe RUN, ERC, ERH, RING and INS indicators can be used to check whetherController Link Unit startup and Network participation are operating normally.

Note Be sure to turn off the power to the PC before performing any of the following.

• Disconnecting the Unit or connectors.

• Securing Units or connectors.

• Setting hardware switches.

The following CIO words contain information on the status of the Controller LinkUnit. These words are referenced in the “Status area” column in the followingtable.

Error Information: CIO 1500 + 25 × (Unit No.) (See page 177)

Ring Status: CIO 1500 + 25 × (Unit No.) + 23 (See page 180)

Power Status: CIO 1500 + 25 × (Unit No.) + 24 (See page 178)

Indicators Status area Error Probable cause Probable remedy

RUN P/S ERC ERH RING INS code

Lit --- Notlit

Notlit

Lit Lit --- --- The Unit startednormally in tokenring mode andentered thenetwork normally.

---

Lit --- Notlit

Notlit

Not lit Lit --- --- The Unit startednormally in tokenbus mode andentered thenetwork normally.

---


167


Status area

RUN


Status area

INSRINGERHERCP/SNotlit

--- Notlit

Notlit

Not lit Notlit

--- --- Power is not beingsupplied correctlyto the PC.

Check the powersupply voltageand supply at therecommendedvoltage.

The ControllerLink Unit hasbecome loose.

Secure theController LinkUnit firmly.

The ControllerLink Unit ismounted in thewrong slot.

Refer to 3-2-1CVM1 andCV-series PCsand mount theUnit correctly.

The ControllerLink Unit is faulty.

If the indicators donot light when theUnit is mounted inanother PC,replace theController LinkUnit.

--- Lit --- --- --- --- Power status:Bit 11 ON


0216 Hex The status of thebackup powersupply changed.(Backup powerbeing supplied.)



--- Notlit

--- --- --- --- Power status:Bit 11 OFF


0216 Hex The status of thebackup powersupply changed.(Backup powernot beingsupplied.)



Check the backuppower supply andits cables.

Notlit

--- Lit Notlit

--- Notlit

--- --- Controller LinkUnit faulty.

If the ERCindicators stilllights when theUnit is mountedon another PC,replace theController LinkUnit.


0214 Hex The node addressis outside thesetting range.

Set the nodeaddress to withinthe 1 to 62 range.


168


Status area

RUN


Status area

INSRINGERHERCP/S--- --- Lit Not

lit--- Not

litError information:Bits 12 and 15 ON

021B Hex Hardware error incommunicationscontroller.



0210 Hex Error in thecommunicationscontroller’stransmitter.


Lit --- Lit --- --- Notlit


0211 Hex The same nodeaddress is beingused by twodifferent Units.

Change so thateach nodeaddress in theNetwork is unique.

0211 Hex The transmissionpath format settingdoes not matchthe setting in thepolling node.


Lit --- --- Lit --- --- Error information:Bit 15 ON

0001 Hex An error hasoccurred in thePC.

Refer to the PC’soperation manualand correct theerror. If the erroroccurs again,replace the PC.


0203 Hex There is an errorin the networkparameters storedin the ControllerLink Unit’sEEPROM.

Set the networkparameters again.If the error occursagain, replace theController LinkUnit.

021A Hex The networkparameter settingsare incorrect orthe local nodeaddress is largerthan the maximumnode address setin the networkparameters.

Set the networkparameters again.


0203 Hex There is an errorin the data linktables stored inthe Controller LinkUnit’s EEPROM.

Set the data linktables again. If theerror occursagain, replace theController LinkUnit.

021A Hex The data link tablesettings areincorrect.

Set the data linktables again.Delete the datalink tables if theyaren’t being used.


0203 Hex There is an errorin the routing tablein the PC’s routingtable area.

Set the routingtables again. If theerror occursagain, replace thePC.

021A Hex Routing tablesetting error

Set the routingtables again.Delete the routingtables if theyaren’t being used.


169


Status area

RUN


Status area

INSRINGERHERCP/SLit --- --- --- --- Not

lit--- --- Cables are not

connectedcorrectly.

Check the cableconnections arereconnectcorrectly.

The node addressis larger than themaximum nodeaddress set in thenetworkparameters.

Either change themaximum nodeaddress settingwith the ControllerLink SupportSoftware (Ver.2.00 or higher) orset a nodeaddress below themaximum.

No other nodesexist.

Make sure that 2or more nodesexist within theNetwork.

No node has beenset as the pollingnode.

Refer to 8-1-2Setting the Pollingand Polled Nodesand set theController LinkUnit as the pollingnode.(If both types ofoptical Units areused in a network,use the OpticalRing Units aspolled nodes.)

The transmissionpath format settingis different in thepolling node.


--- --- --- --- Flashing Lit Ring status:Bit 15 ON


021D Hex A break wasdetected in thenetwork cable.(Networkoperationcontinues.)

Determine thelocation of thebreak with theController LinkSupport Software(Ver. 2.00 orhigher) or the ring

--- --- --- --- Flashing Notlit

Ring status:Bit 15 ON


021D Hex A break wasdetected in thenetwork cable.(The Unit was outof the networkafter the error.)

higher) or the ringstatus word.Correct the break.Refer to 9-4Locating andCorrecting CableDisconnections fordetails.

Troubleshooting with LNK and M/A Indicators

The following table describes the LNK and M/A indicators at the startup nodeand their use in troubleshooting when a data link cannot be started.

Starting a data link depends on the Controller Link Unit operating normally andparticipating in the Network. Refer to Troubleshooting with RUN, ERC, ERH andINS Indicators earlier in this section and check Unit operation before using thefollowing table.

Data Link Cannot beStarted


170


LNK M/A


Flashing --- There is an error in the datalink tables.

When the ERH indicator isflashing, remake and set thedata link tables.

When manual setting is used,either data link tables havenot been created for thestartup node or there is anerror in the data link tables.

Refer to 5-2-2 Manual Settingand set data link tables for thestartup node.

When automatic setting isused, either the data linkparameters for the startupnode have not been set orthere is an error in the datalink tables.

Refer to 5-2-4 AutomaticSetting and set the automaticparameters for starting thedata links.

Not lit Lit Manually set data links arealready operating on thesame Network.

Stop the manually set datalinks that are operating andrestart the data links.

Not lit Not lit Automatically set data linksare already operating on thesame Network.

Stop the automatically setdata links that are operatingand restart the data links.

There is an error in thestartup node PC.

Refer to the PC’s operationmanual and correct the error.If the error reoccurs, replacethe PC.

The following table describes the LNK and M/A indicators when a node cannotparticipate in the data links.

Data link participation depends on the Controller Link Unit operating normallyand participating in the Network. Refer to Troubleshooting with RUN, ERC, ERHand INS Indicators earlier in this section and check Unit operation before usingthe following table.


LNK M/A


Flashing Lit When manual setting is used,there is an error in the datalink table.

Refer to 5-2-2 Manual Settingand remake the data linktable.

Flashing Not lit When automatic setting isused, the data linkparameters at the startupnode are incorrect for thelocal node (the data link areais out of range for the localnode.)

Refer to 5-2-4 AutomaticSetting, reset the parametersfor the startup node DM Areaso that the local node canparticipate in the data link,and then restart the data link.

Not lit Lit When manual setting is used,there are no data link tablesset for the local node.

Set data link tables for thelocal node.

Not lit Not lit When automatic setting isused, the startup node is notset to participate in the datalinks.

Stop the data links, remakeand set the parameters in thestartup node’s DM Area, andthen restart the data link.

Stopping the data link depends on the Controller Link Unit operating normallyand participating in the Network. Read the above explanations before attempt-ing to stop operation.

Node Cannot Participatein Data Link

Data Link Cannot beStopped

9-2SectionStatus Area and Troubleshooting

171

Note Stop the data link from the node at which the LNK indicator is lit (indicating activedata links). Data links cannot be stopped from nodes which do not have activedata links.

9-2 Status Area and TroubleshootingThe status of the Unit and the communications status of the Controller Link Unitis recorded in the Status Area of the PC. The cause of errors can be found bysearching the Status Area. The Status Area can be read using a ProgrammingConsole, the SYSMAC Support Software, or the Controller Link Support Soft-ware.

This section explains the contents of the Status Area and tells how to trouble-shoot errors recorded there.

9-2-1 CS1-series Controller Link UnitsThe status of the Unit and Network is indicated in the following manner in the PC.

Status AreaError Information: CIO 1500 + 25 x (Unit No.)

1: Network parameter error (In PC’s EEPROM)

1: Data link table error (in PC’s EEPROM)

1: Routing table error (in PC’s EEPROM)

1: PC system setting error

1: EEPROM error

1: Duplicate node address setting error

1: Inconsistent network parameters1: Communications controller send error

1: Communications controller hardware error

1: Error log exists

Polling Node Address, Startup Node Address: CIO 1500 + 25 x (Unit No.) + 1

Polling node address Startup node address

Each node address is displayed in 2-digit BCD.

Network Participation Status: CIO 1500 + 25 x (Unit No.) + 2 to +5

The numbers in the squares correspond to node addresses.The bit status indicates each node’s participation status as follows:0: Not part of the network1: Part of the network

Note When the local node is not part of the network, the localnode’s participation status bit will be 0. The participa-tion status of other nodes will not be reliable in thiscase.

–: Not used


172

Local Data Link Participation Status: CIO 1500 + 25 x (Unit No.) + 6

1: Local node data link participating0: Local node data link not participating or data linkinactive

Note Data link status is valid only when the local node is participating in the data link.Confirm that the Local Data Link Active Bit is ON before referencing the data linkstatus.

Data Link Status: CIO 1500 + 25 x (Unit No.) + 7 to + 228 Bit Format Specified

Node 2Node 4Node 6Node 8

toNode 30Node 32Node 34Node 36






Offset error 0:Normal1:Error

Error: Offset exceedsnumber of send words.


Insufficient: Receivearea is smaller thansend area. Excess datais truncated; other datais received.


Remaining: Receivearea is larger than sendarea. Data is receivedand remaining wordsare cleared.




+7+8+9+10

+21+22+23+24

+34+35+36+37


173

4 Bit Format Specified

Node 4





Node 8



Node 40Node 44


Node 600

Node 3

Node 7



Node 39Node 43


Node 590

Node 2

Node 6



Node 38Node 42


Node 58Node 62

Node 1

Node 5



Node 37Node 41


Node 57Node 61

When the first data link status word is set to the default (0000) for either themanually set data link tables or automatically set data link tables (In the first datalink status word parameter), the data link status is stored in the above area (CIO1500 + 25 × (Unit No.) (+ 7 to +22)).

When a different area has been set for the first data link status word, the status isstored in the specified area. The status storage format is the same as the oneshown in the above diagram. When the 8-bit format is specified, the area con-tains 31 words in order to contain the status information for node addresses 1 to62.

Note Refer to 5-4 Checking Data Link Status for details on status flags.


174

Ring Status: CIO 1500 + 25 x (Unit No.) + 23

Node address of disconnected node(00 Hex: No disconnected nodes detected.)

Disconnected Interface Flag0: SL1 (uplink) or normal status1: SL2 (downlink)

Disconnected nodeinformation #1(See note.)

Local Node Disconnection Flag0: Normal1: Disconnection detected




Network Disconnection Flag0: Normal1: Disconnection detected

Note The disconnected node information is valid only when bit 15 (the NetworkDisconnection Flag) is ON. If bit 15 is OFF, the earlier disconnected nodeinformation is retained.

Power Status: CIO 1500 + 25 x (Unit No.) + 24

Power supply status0: Power is not being supplied.1: Power is being supplied.

Bit Status and Error ProcessingBit status Probable cause Probable remedy

PC’s CPU Unit error is 1:ON

A fatal PC error, non-fatalPC error, or a watchdogtimer error has occurred.

Refer to the PC’soperation manual andcorrect the error. If theerror occurs again,replace the PC.

The Unit is mounted to anon-compatible PC.

Refer to 1-2-5 ControllerLink Unit Models and PCsand mount onto thecorrect PC.

Communications error is1: ON

The relevant node is notin the Network.

Enter the node in theNetwork.

A communications errorhas occurred as a resultof noise.

Conduct an echoback testusing the Controller LinkSupport Software and ifthis does not correct theerror, check the usageenvironment.

A communications errorhas occurred.

Refer to page 166Troubleshooting withRUN, P/S, ERC, ERH andINS Indicators andtroubleshoot accordingly.

Data Link Status


175

Bit status Probable remedyProbable causeData link participation is 0:OFF

The relevant node is notpart of data links.

Enter the relevant node indata links. If an erroroccurs, refer to page 170Node Cannot Participatein Data Link andtroubleshoot accordingly.

There are no active datalinks in the Network.

Activate the data links.

Offset error is 1: ON The offset is greater thanthe number of send wordsat the relevant node.

Check the number of sendwords at the relevantnode, the number ofreceive words at the localnode and the offset, thenreset the data link tablecorrectly.

Receive area insufficient(short) is 1: ON

The send area at therelevant node is largerthan the receive area andsome data cannot bereceived.

When the intention is notto receive all data, use asis (data that cannot bereceived will be read anddiscarded.)

When it differs from theintended data link, checkthe number of send wordsat the relevant node, thenumber of receive wordsat the local node and theoffset, then reset the datalink table correctly.

Receive area remaining is1: ON

The send area at therelevant node is smallerthan the receive area andsome of the area will beunused.

When the intention is toleave some space in thereceive area, use as is(the surplus receive areawill be cleared to 0.)


Bit status Probable cause Probable remedy

Error log exists (CIO 1500+ 25 × n, bit 15) is 1: ON

Error information on theController Link Unit (anerror log) has beenrecorded.

Using the Controller LinkSupport Software or anFINS command, read thecause of the current error.Alternatively, use pasterror log records totroubleshoot the problem.

Communications controllersend error (CIO 1500 + 25× n, bit 11) is 1: ON

The Controller Link Unit isfaulty.

Replace the ControllerLink Unit.

Inconsistent networkparameters (CIO 1500 +25 × n, bit 10) is 1: ON

Indicates that the networkparameters recorded inthe CS1 Bus Unit Areadiffer from the values ofthe Network in use.

Check the networkparameters on theNetwork in use using theController Link SupportSoftware, and resetnecessary parameters.

Other Status


176

Bit status Probable remedyProbable causeNode address duplicatesetting error (CIO 1500 +25 × n, bit 9) is 1: ON

The same node addresshas been used more thanonce.

Reset so that each nodeaddress is used only oncewithin the same Network.

The Unit is connected to aSYSMAC LINK network(Optical Units only).

Check the network andreconnect cablescorrectly.

EEPROM error (CIO 1500+ 25 × n, bit 7) is 1: ON

An error has occurredwhile writing data to theCPU Unit’s EEPROM.

Check the status of bits00 to 02 in (CIO 1500 +25 × n, and correct anyproblems found. If theerror occurs again,replace the CPU Unit.

PC system setting error(CIO 1500 + 25 × n, bit 3)is 1: ON

The CPU Unit’s EEPROMdata is damaged.


The PC is protected. Set the PC’s protectswitch to OFF.

Routing table error(CIO 1500 + 25 × n, bit 2)is 1: ON

The routing table datawithin the CPU Unit’sEEPROM is damaged.

Refer to 7-4 SettingRouting Tables and resetthe routing tablescorrectly. If the erroroccurs again, replace theController Link Unit.

There is an error in therouting table setting.

When using a routingtable, refer to 7-4 SettingRouting Tables and resetthe routing tablescorrectly.

If no routing tables arebeing used, delete thetables.

Data link table error(CIO 1500 + 25 × n, bit 1)is 1: ON

The data link table data inthe CS1 CPU Bus UnitArea is damaged.

Refer to 5-3 Starting andStopping Data Links andreset the data link tablescorrectly. If the erroroccurs again, replace theCPU Unit.

There is an error in thedata link table settings.

When using manually setdata links, refer to 5-3Starting and StoppingData Links and remakeand set the data linktables correctly. Whenmanually set data linksare not being used, deletethe data link tables.


177

Bit status Probable remedyProbable causeNetwork parameter error(CIO 1500 + 25 × n, bit 0)is 1: ON

The network parameterdata in the CS1 CPU BusUnit Area is damaged.

Refer to 8-1-3 NetworkParameters and reset thedata correctly. If the erroroccurs again, replace theCPU Unit.

Either set the EEPROMClear Bit in the DMparameter area to ON, oruse the Initialize networkparameters operation onthe Maintenance Menu ofthe Controller LinkSupport Software toinitialize the networkparameters and thencycle the power supply.

There is an error in thenetwork parametersettings, or node addressof the local node is largerthen the maximumaddress set within thenetwork parameters.

Refer to 8-1-3 NetworkParameters and reset thenetwork parameters or thenode address.

Power Supply Status/Terminating Resistance Status: CIO 1500 + 25 x (Unit No.) + 24

CS1W-SLK11 Optical Bus Controller Link UnitPower supply status: 0: Power supplied

1: Power not suppliedCS1W-SLK21 Wired Controller Link UnitTerminating resistance status: 0: OFF

1: ON

9-2-2 CVM1 and CV-series Controller Link UnitsThe status of the Unit and Network is indicated in the following manner in the PC.

Status AreaError Information: CIO 1500 + 25 x (Unit No.)





1: EEPROM error



1: Error log exists

Polling Node Address, Startup Node Address: CIO 1500 + 25 x (Unit No.) + 1




178

Network Participation Status: CIO 1500 + 25 x (Unit No.) + 2 to +5

The numbers in the squares correspond to node addresses.The bit status indicates each node’s participation status as follows:0: Not part of the network1: Part of the network

Note When the local node is not part of the network, the localnode’s participation status bit will be 0. The participa-tion status of other nodes will not be reliable in thiscase.

–: Not used

Local Data Link Participation Status: CIO 1500 + 25 x (Unit No.) + 6


Note Data link status is valid only when the local node is participating in the data link.Confirm that the Local Data Link Active Bit is ON before referencing the data linkstatus.

Data Link Status: CIO 1500 + 25 x (Unit No.) + 7 to + 228 Bit Format Specified

















+7+8+9+10

+21+22+23+24

+34+35+36+37


179

4 Bit Format Specified





Node 4

Node 8





0

Node 3

Node 7





0

Node 2

Node 6





Node 62

Node 1

Node 5





Node 61

When the first data link status word is set to the default (0000) for either themanually set data link tables or automatically set data link tables (In the first datalink status word parameter), the data link status is stored in the above area (CIO1500 + 25 × (Unit No.) (+ 7 to +22)).

When a different area has been set for the first data link status word, the status isstored in the specified area. The status storage format is the same as the oneshown in the above diagram. When the 8-bit format is specified, the area con-tains 31 words in order to contain the status information for node addresses 1 to62.



180










Note The disconnected node information is valid only when bit 15 (the NetworkDisconnection Flag) is ON. If bit 15 is OFF, the previous disconnected nodeinformation is retained.



Bit Status and Error ProcessingBit status Probable cause Probable remedy

PC’s CPU Unit error is 1:ON

A fatal PC error, non-fatalPC error, or a watchdogtimer error has occurred.

Refer to the PC’soperation manual andcorrect the error. If theerror occurs again,replace the PC.

The Unit is mounted to anon-compatible PC.

Refer to 1-2-5 ControllerLink Unit Models and PCsand mount onto thecorrect PC.

Communications error is1: ON

The relevant node is notin the Network.

Enter the node in theNetwork.

A communications errorhas occurred as a resultof noise.

Conduct an echoback testusing the Controller LinkSupport Software and ifthis does not correct theerror, check the usageenvironment.

A communications errorhas occurred.

Refer to page 166Troubleshooting withRUN, P/S, ERC, ERH andINS Indicators andtroubleshoot accordingly.

Data Link Status


181

Bit status Probable remedyProbable causeData link participation is 0:OFF

The relevant node is notpart of data links.

Enter the relevant node indata links. If an erroroccurs, refer to page 170Node Cannot Participatein Data Link andtroubleshoot accordingly.

There are no active datalinks in the Network.

Activate the data links.

Offset error is 1: ON The offset is greater thanthe number of send wordsat the relevant node.

Check the number of sendwords at the relevantnode, the number ofreceive words at the localnode and the offset, thenreset the data link tablecorrectly.

Receive area insufficient(short) is 1: ON

The send area at therelevant node is largerthan the receive area andsome data cannot bereceived.

When the intention is notto receive all data, use asis (data that cannot bereceived will be read anddiscarded.)


Receive area remaining is1: ON

The send area at therelevant node is smallerthan the receive area andsome of the area will beunused.

When the intention is toleave some space in thereceive area, use as is(the surplus receive areawill be cleared to 0.)


Bit status Probable cause Probable remedy

Error log exists (CIO 1500+ 25 × n, bit 15) is 1: ON

Error information on theController Link Unit (anerror log) has beenrecorded.

Using the Controller LinkSupport Software or anFINS command, read thecause of the current error.Alternatively, use pasterror log records totroubleshoot the problem.

Communications controllersend error (CIO 1500 + 25× n, bit 11) is 1: ON

The Controller Link Unit isfaulty.

Replace the ControllerLink Unit.

Inconsistent networkparameters (CIO 1500 +25 × n, bit 10) is 1: ON

Indicates that the networkparameters recorded inthe CPU Unit’s EEPROMdiffer from the values ofthe Network in use.

Check the networkparameters on theNetwork in use using theController Link SupportSoftware, and resetnecessary parameters.

Node address duplicatesetting error (CIO 1500 +25 × n, bit 9) is 1: ON

The same node addresshas been used more thanonce.

Reset so that each nodeaddress is used only oncewithin the same Network.

Other Status


182

Bit status Probable remedyProbable cause

EEPROM error (CIO 1500+ 25 × n, bit 7) is 1: ON

An error has occurredwhile writing data to theCPU Unit’s EEPROM.


PC system setting error(CIO 1500 + 25 × n, bit 3)is 1: ON

The CPU Unit’s EEPROMdata is damaged.


The PC is protected. Set the PC’s protectswitch to OFF.

Routing table error(CIO 1500 + 25 × n, bit 2)is 1: ON

The routing table datawithin the CPU Unit’sEEPROM is damaged.

Refer to 7-4 SettingRouting Tables and resetthe routing tablescorrectly. If the erroroccurs again, replace theController Link Unit.

There is an error in therouting table setting.

When using a routingtable, refer to 7-4 SettingRouting Tables and resetthe routing tablescorrectly.

If no routing tables arebeing used, delete thetables.

Data link table error(CIO 1500 + 25 × n, bit 1)is 1: ON

The data link table data inthe EEPROM of the CPUUnit is damaged.

Refer to 5-3 Starting andStopping Data Links andreset the data link tablescorrectly. If the erroroccurs again, replace theCPU Unit.

There is an error in thedata link table settings.

When using manually setdata links, refer to 5-3Starting and StoppingData Links and remakeand set the data linktables correctly. Whenmanually set data linksare not being used, deletethe data link tables.

9-3SectionError Log

183

Bit status Probable remedyProbable causeNetwork parameter error(CIO 1500 + 25 × n, bit 0)is 1: ON

The CPU Unit’s EEPROMdata link tables or thenetwork parameters aredamaged.

Refer to 8-1-3 NetworkParameters and reset thedata correctly. If the erroroccurs again, replace theCPU Unit.

Either set the EEPROMClear Bit in the DMparameter area to ON, oruse the Initialize networkparameters operation onthe Maintenance Menu ofthe Controller LinkSupport Software toinitialize the networkparameters and thencycle the power supply.

There is an error in thenetwork parametersettings, or node addressof the local node is largerthen the maximumaddress set within thenetwork parameters.

Refer to 8-1-3 NetworkParameters and reset thenetwork parameters or thenode address.

9-3 Error Log

The error log records errors that occur in the Controller Link Unit and the timethey occur. The error log can be read or cleared using the Controller Link Sup-port Software, the CX-Programmer, a PC Programming Device such as theSYSMAC Support Software, or the message service (FINS commands for theController Link Unit.)

9-3-1 Error Log Table

Errors are recorded in an error log table in the Unit’s RAM, with one record foreach error and a maximum of 39 records.

Errors of significance are also recorded in the Unit’s EEPROM so that when thepower to the Unit is turned OFF or reset, a record of the error will remain. (Theerror log table in EEPROM automatically reads the Unit’s RAM when the poweris turned ON again.)

Item Specification

No. of records 39 max.

Data code Binary (Times are in BCD)

Length of each record 10 bytes

Configuration of records Error code: 2 bytes (Refer to page 184)Detail code: 2 bytes (Refer to page 184)Time: 6 bytes (Refer to the followingpage)

Record order From the oldest record to the mostrecent.

If the number of records exceeds 39, the oldest record will be deleted and themost recent error recorded.

9-3SectionError Log

184

Error Log Table Configuration0

Error code

Detail

Min S

Day Hour

Error code

Detail

Year Month

Record(Oldest)

Record

Record(Newest)

Error code

Detail

Min

Min

S

Day Hour

Year Month

Month

Hour

S

Day

Year

Time InformationThe time is recorded in BCD with one byte each for the year (the rightmost twodigits), month, day, hour, seconds, and minutes of the time the error occurred.

Note 1. The PC’s time information can be read and used in the Controller Link Unit.When the time cannot be read from the PC, all error log times will but 0. Thiscan occur for PC startup errors, Unit No. errors, CPU Unit errors, or PCmodel errors. When error logs like these are read from the Controller LinkSupport Software, they will be dated 0 s, 0 min, 0 hr, 0 day, 0 month, 2000.

2. When replacing the battery for CS1-series PCs, it will be necessary to switchthe power supply ON and reset the internal clock.If the internal clock is not reset, time information in the error log will not berecorded correctly.

3. The time information will be all zeros for CQM1H-series PCs unless aMemory Cassette with a clock is mounted in the CPU Unit. The time informa-tion will be all zeros in the year 2000 if it is read from Support Software.

9-3-2 Error CodesThe following table lists the error codes (in 4-digit hexadecimal) and the contentsof the errors.

Error Contents Detail code Correction Written Applicablecode

1st byte 2nd bytetoEEPROM

PC

0001Hex

PC watchdog timer error 00 Hex 00 Hex Replace PC’s CPUUnit.

Yes CV, CS1

0002Hex

PC service monitor error Monitor time (unit: ms) Check operatingenvironment.

Yes CV, CS1

0003Hex

PC shared RAM error 01 Hex:Cyclic02 Hex:Event04 Hex:CPU buslink

00 Hex Check operatingenvironment.

Yes CV

9-3SectionError Log

185

Errorcode

ApplicablePC

WrittentoEEPROM

CorrectionDetail codeContentsErrorcode

ApplicablePC

WrittentoEEPROM

Correction

2nd byte1st byte

Contents

0004Hex

CPU Bus Unit ID number error 00 Hex 00 Hex Check I/OConnecting Cables.

Yes CV, CS1

0005Hex

Unit number error Unit setvalue

The valuerecognizedby the CPUUnit

Check the Unitnumber setting.Recreate the I/Otable.

Yes CV

0006Hex

CPU Unit error Bit 11: No relevant Unit inI/O table.

Bit 12: Hardware test unitnumberrecognized.

Bit 13: Incorrect unitnumber.

Bit 14: Duplicated unitnumber.

Check the Unitnumber settings.Recreate the I/Otable.

Yes CV, CS1

000EHex

I/O Bus error 00 Hexfixed

00 Hexfixed

Check the operatingenvironment.

Yes CS1

000FHex

PC initialization error Check the operatingenvironment.

Yes CS1

0010Hex

PC Setup exceeds capacity Reduce the numberof CPU Bus Unitsmounted on eachCPU Unit by one.

Yes CS1

0011Hex

PC initialization error(Time out)

Check the operatingenvironment.

Yes CS1

0012Hex

CPU Unit memory error 01 Hex:Read error02 Hex:Write error

01 Hex:Data linktable02 Hex:Network

Reset theappropriate data.

Yes CS1

0013Hex

CPU Unit write-protectedparameters03 Hex:Routingtable04 Hex: PCSetup Area

Release the CPUUnit write protect.

Yes CS1

9-3SectionError Log

186

Errorcode

ApplicablePC

WrittentoEEPROM


ApplicablePC

WrittentoEEPROM

Correction

2nd byte1st byte

Contents

0101Hex

Transmission failed; local nodenot in Network

Command block Bits 0 to 7:

Source node addressBits 8 to 14:

Source Network

Refer to page 160TroubleshootingUsing Indicators andplace the local nodeinto Network.

No CV, CS1

0103Hex

Transmission failed; retry countexceeded

addressBit 15:

OFF

Response blockBits 0 to 7:

Destination nodeaddress

Bits 8 to 14:

Using the ControllerLink SupportSoftware or FINScommands, runechoback test andcheck operatingenvironment if errorsoccur.

No CV, CS1

0104Hex

Transmission failed; maximumnumber of frames exceeded.

Destination Networkaddress

Bit 15: ON

(1st byte: bits 8 to 15; 2nd byte, bits 0 to 7)

Reduce the numberof events percommunicationscycle or increase themaximum number ofnetwork parameterframes.

No CV, CS1

0105Hex

Transmission failed; nodeaddress incorrect

Refer to 4-1CS1-series OpticalRing Controller LinkUnits or 4-2 CVM1and CV-seriesOptical RingController Link Unitsand check nodeaddress settings tobe sure they arewithin range andunique.

No CV, CS1

0106Hex

Transmission failed; redundantnode address

Correct nodeaddresses so thatthey are uniquewithin the sameNetwork.

No CV, CS1

0107Hex

Transmission failed; destinationnode not in Network

Refer to 9-1TroubleshootingUsing Indicators andplace destinationnode into Network.

No CV, CS1

0108Hex

Transmission failed; specifiedUnit does not exist

Refer to 4-2 CVM1and CV-seriesController Link Unitsand check unitaddress and unitnumber ofdestination.

No CV, CS1

9-3SectionError Log

187

Errorcode

ApplicablePC

WrittentoEEPROM


ApplicablePC

WrittentoEEPROM

Correction

2nd byte1st byte

Contents

0109Hex

Transmission failed; destinationbusy

Command block Bits 0 to 7:


Increase number ofretries orreconfigure systemto distribute load.

No CV, CS1

010AHex

Transmission failed;communications controller error

Source Networkaddress

Bit 15: OFF


Destination nodeaddress

Bits 8 to 14: Destination Networkaddress

Bit 15:

Conduct anechoback test and ifthe effects of noiseare considerable,reconsider theoperatingenvironment.Restart theController Link Unit.If the error occursagain, replace theUnit.

Yes CV, CS1

010BHex

Transmission failed; PC errorON


Refer to the PCoperating manual. Ifthe error occursagain, replace thePC.

No CV, CS1

010CHex

Transmission failed; unitnumber incorrect

Check unit numbersettings to be surethey are withinrange and unique.

No CV, CS1

010DHex

Transmission failed; destinationaddress incorrect

Check routingtables.

No CV, CS1

010EHex

Transmission failed; routingtables not registered

Check routing tables No CV, CS1

010FHex

Transmission failed; routingtable error

Check routingtables.

No CV, CS1

0110Hex

Transmission failed; too manyrelay points

Check routing tablesand systemconfiguration. Donot try to accessNetworks separatedby more than oneother Network.

No CV, CS1

0111Hex

Transmission failed; commandpacket too long

Be sure to use theFINS commandformat.

No CV, CS1

0112Hex

Transmission failed; headererror.

Be sure to use thecorrect FINScommand format.

No CV, CS1

0113Hex

Transmission failed; I/O settingerror

Check I/O tableaccuracy.

No CV, CS1

0114Hex

Transmission failed; CPU buserror

Check Unit andcable connectionsand clear error.

No CV, CS1

0115Hex

Transmission failed; redundantI/O allocations

Check unit numbersfor redundancywithin the same PC.

No CV, CS1

0116Hex

Transmission failed; CPU BusUnit error

Check Unit andcable connectionsand clear error.

No CV, CS1

9-3SectionError Log

188

Errorcode

ApplicablePC

WrittentoEEPROM


ApplicablePC

WrittentoEEPROM

Correction

2nd byte1st byte

Contents

0117Hex

Internal buffer full Command block Bits 0 to 7:


Source Networkaddress

Bit 15: OFF


Increase number ofretries orreconfigure systemto distribute load.

No CV, CS1

0118Hex

Illegal packet discarded Destination nodeaddress

Bits 8 to 14: Destination Networkaddress

Bit 15: ON


Check for nodessending illegalpackets.

Yes CV, CS1

0203Hex

EEPROM error 01 Hex:Read error02: Hex:Write error

01 Hex:Data linktables02 Hex:Networkparameters03 Hex:Routingtables

For CVM1 andCV-series PCs,check that the PC isnot protected.

Remake and set therelevant data. If theerror occurs againfor the CVM1 andCV-series, replacethe CPU Unit.

Yes CV

0206Hex

Number of participating nodesdecreased (local node stillparticipating)

Networkparametersmaximum

Number ofnon-participating nodes

Check networkparameters, nodeparticipation, cables,

No CV, CS1

0207Hex

Number of participating nodesdecreased (local node notparticipating)

nodeaddress

and terminatingresistance. No CV, CS1

0208Hex

Polling node changed Address ofpreviouspolling node

Address ofnew pollingnode

Check previouspolling node.

No CV, CS1

0209Hex

Inconsistent network parameter 00 Hex Address ofpolling node

Using the ControllerLink SupportSoftware, checknetwork parameters.

Yes CV, CS1

020CHex

Time out with token 00 Hex Error status(see note 3)

Check networkparameters, nodeparticipation, cables,and terminatingresistance.

No CV, CS1

0210Hex

Communications controller senderror

00 Hex Error status(see note 3)

Replace theController Link Unit.

Yes CV, CS1

0211Hex

Duplicate address error 00 Hex Local nodeaddress

Reset so that eachnode address isused only oncewithin the sameNetwork.

No CV, CS1

0214Hex

Node address setting error Not specified Check the nodeaddress settingsand correct them.

Yes CS1

9-3SectionError Log

189

Errorcode

ApplicablePC

WrittentoEEPROM


ApplicablePC

WrittentoEEPROM

Correction

2nd byte1st byte

Contents

0216Hex

Backup power supply error(Optical Units only)

00 Hexfixed

Backuppowersupply errordistinction:01 Hex:OFF to ON02 Hex: ONto OFF

Check the status ofthe backup powersupply and powersupply cables.

Yes CS1

021AHex

Set table logic error 00 Hex 01 Hex:Networkparameters02 Hex:Data linktables03 Hex:Routingtables

Remake and set theappropriate data.

Yes CV, CS1

021BHex

Hardware error 00 Hex Error status(see note 3)

Replace theController Link Unit.

No CV, CS1

021CHex

Data link error inactive Not set Restart theController Link Unit.

Yes CV, CS1

021EHex

Network disconnection occurred Ring status (see note 4) Refer to 9-4Locating andCorrecting CableDisconnections fordetails.

No CV, CS1

0220Hex

Number of participating nodesdecreased (0206 Hex)Additional information #1

Bits 1 to 15 correspond tonodes 1 to 15. Thecorresponding bit will beON when that node isdisconnected.(Bit 0 is always OFF.)

Check networkparameters, thedisconnected node,and cables.

No CV, CS1

0221Hex


Bits 0 to 15 correspond tonodes 16 to 31. Thecorresponding bit will beON when that node isdisconnected.

No CV, CS1

0222Hex


Bits 0 to 15 correspond tonodes 32 to 47. Thecorresponding bit will beON when that node isdisconnected.

No CV, CS1

0223Hex


Bits 0 to 14 correspond tonodes 48 to 62. Thecorresponding bit will beON when that node isdisconnected.(Bit 15 is always OFF.)

No CV, CS1

0300Hex

Packet discarded Not set Conduct anechoback test andfind the cause of theerror.

No CV, CS1

0601Hex

Unit error Not set Check the operatingenvironment.

Yes CV, CS1

Note 1. Applicable PCs: CV = CVM1 and CV-series PCs, All = All models of PC.

2. Errors indicated by error codes 0101 to 0116 are recorded only when theframe was discarded because transmission was impossible.

9-3SectionError Log

190

3. Error Status:The status of each bit indicates that an error has occurred as given in thediagram below.

1: Token timeout error1: Polling timeout error1: Communications controller hardware error1: Polling node was changed1: Nodes in Network changed (added or removed)1: Communications controller send error1: Node address duplication error

4. Ring Status:The network disconnection information is indicated as shown in the diagrambelow.










9-3-3 Reading and Clearing Error LogsError logs can be read or cleared using the Controller Link Support Software, theCX-Programmer, PC Programming Devices, or the message service. The fol-lowing examples are for the Controller Link Support Software and the messageservice. When using a PC Programming Device, refer to the ProgrammingDevice’s operation manual for details.

Controller Link Support SoftwareRead or clear the error log using the following procedure.

1, 2, 3... 1. Display the Main Menu.2. Select “E: Error log.”3. Designated the node. The error log for the designated node will be dis-

played.4. Press the F7 (Clear) Key. The designated node error log will be cleared.

Message ServiceReading an Error Log

Send the ERROR LOG READ FINS command (command code 2102) to theappropriate node. Refer to 6-5-14 ERROR LOG READ.

9-4SectionLocating and Correcting Cable Disconnections

191

Clearing an Error LogSend the ERROR LOG CLEAR FINS command (command code 2103) to theappropriate node. Refer to 6-5-15 ERROR LOG CLEAR.

9-4 Locating and Correcting Cable DisconnectionsIn an Optical Ring Controller Link System, the disconnect detection and notifica-tion function can be used to locate an open point in the optical ring and notify allof the nodes in the network through the polling node. If the ring is broken at onepoint, this function allows the system administrator to perform repairs and main-tenance before another problem develops or the network stops transmittingdata.

9-4-1 Notification of Network Cable DisconnectionsOptical Ring Controller Units connect to redundant transmission paths throughtwo interfaces. Data transmitted from another node in the network is received atboth of the Unit’s connectors (SL1 and SL2) as shown in the following diagram.


Node 6 Node 5

Transmission


Data transmitted by the localnode makes a complete circuitthrough the network and thenreceived by the local node.

Reception


The data is receivedat both interfaces.

CPU

CPU

CPU

CPU

SL1 SL2 SL1 SL2 SL1 SL2 SL1 SL2

CPU

CPU

The following diagram shows the same network when the cable between nodes3 and 4 is disconnected or broken for some reason. Even in this case, network


192

communications will continue normally as long as the Controller Link Unit canreceive data normally through either SL1 or SL2.


Node 6 Node 5

Reception


Reception


Data transmitted from node 3

Data received at node 4

CPU

CPU

CPU

CPU


CPU

CPU

The following diagram shows which interface is used to receive data from theother nodes when the cable between nodes 3 and 4 is disconnected or broken.

Trans-mittingnode

Receiving interface(s)

SL1


Node 6 Node 5

SL21 – –2 ×

3 ×

4

5

6

Trans-mittingnode


SL1 SL21 ×2 – –3 ×

4 ×5 ×6 ×

Trans-mittingnode


SL1 SL21 ×2 ×3 – –4 ×5 ×6 ×

Trans-mittingnode


SL1 SL21 ×

2 ×

3 ×

4 – –5 ×

6 ×

Trans-mittingnode


SL1 SL21 ×

2 ×

3 ×

4 ×5 ×6 – –

Trans-mittingnode


SL1 SL21 ×

2 ×

3 ×

4 ×5 – –6 ×

CPU

CPU

CPU

CPU


CPU

CPU

No data is received through node 3’s SL2 interface or node 4’s SL1 interface.When a node detects that no data is being received through one of its interfaces(such as nodes 3 and 4 in this example), it notifies the polling node that a “net-work cable disconnection” has occurred.


193

After receiving notification of a disconnection, the polling node notifies all of thenodes in the network about the disconnection. Each node updates its “ring sta-tus” with the disconnection information transmitted from the polling node.

Each node maintains ring status information in one word, as shown in the follow-ing diagram.Ring Status word: CIO 1500 + 25 x (Unit No.) + 23






Disconnected Interface Flag0: SL1 (uplink) or normal status1: SL2 (uplink)




The following tables show the ring status for each node in the preceding exam-ple.

Ring Status of Nodes 3 and 4

Bit Function Value

15 Network Disconnection Flag(0: Normal; 1: Disconnection detected)

1

14 Disconnected nodeinformation #1

Disconnected Interface Flag0: SL1/normal; 1: SL2

1

13 to 8 Node address of disconnected node 03 Hex

7 Local Node Disconnection Flag(0: Normal; 1: Disconnection detected)

1



0


Note The contents of disconnected node information #1 and #2 may be reversed de-pending on network conditions.

Ring Status of Nodes 1, 2, 5, and 6

Bit Function Value


1



1


Ring Status InformationStored in Each Node


194

Bit ValueFunction


0



0


Note The contents of disconnected node information #1 and #2 may be reversed de-pending on network conditions.

9-4-2 Cable Disconnection ExamplesThe cables connecting the nodes in an Optical Ring System have two opticalfibers which provide communications in both directions. It is possible for just oneof the optical fibers to become disconnected.Example 1: One Optical Fiber DisconnectedThe following example shows a network in which just the downlink optical fiber(the uplink fiber for node 4) is broken between nodes 3 and 4.


Node 6 Node 5

CPU

CPU

CPU

CPU


CPU

CPU

The following tables show the ring status for each node in the preceding exam-ple.Ring Status of Node 4

Bit Function Value


1



0



1



0


Note When only one node’s disconnected node information is stored, the data isstored in bits 8 to 14 (disconnected node information #1).

Ring Status of Nodes 1, 2, 3, 5, and 6

Bit Function Value


1



0




195

Bit ValueFunction


0



0



Example 2: One Optical Fiber Disconnected in Two PlacesAs long as one of the optical fibers is communicating normally in one direction,the network can continue operating normally even though the other optical fiberis broken in two places. While the system will continue operating normally, repairthe ring as soon as possible to prevent the system from going down if anotherproblem occurs.

The following example shows a network in which the downlink optical fiber isbroken between nodes 1 and 2 (the uplink fiber for node 2) and the downlink opti-cal fiber is broken between nodes 3 and 4 (the uplink fiber for node 4).


Node 6 Node 5

CPU

CPU

CPU

CPU


CPU

CPU

The following tables show the ring status for each node in the preceding exam-ple.

Ring Status of Nodes 2 and 4

Bit Function Value


1



0



1



0




196


Ring Status of Nodes 1, 3, 5, and 6

Bit Function Value


1



0



0



0



9-4-3 Correction of Network Cable DisconnectionsCable disconnections must be corrected as soon as possible after they are lo-cated with the disconnect detection and notification function.

The following list shows the most likely causes of disconnections based on infor-mation gathered for OMRON’s earlier Optical Bus Networks.

1, 2, 3... 1. The power supply is OFF in a node without a backup power supply.

2. The node’s connector is not installed properly.

3. The cable is faulty. (The end of the cable may be dirty or the cable may bedamaged.)

4. The Controller Link Unit is faulty. (The surface of the receiving element maybe dirty or the receiver may be damaged.)

The following table explains how to correct problems with network communica-tions based on the nature of the problems.


197

Communicationsconditions

Probabledisconnection(s)

Possible remedy

Communicationsapplications cancontinue operating.

Both optical fibersdisconnected at onelocation

One optical fiberdisconnected at onelocation

1. Locate the disconnection point by checking each node’s ring status wordor connecting to one of the nodes with the support software (ControllerLink Support Software Ver. 2.00 or higher.)

2. Check the power supply and backup power supply at the nodes indicatedby the “node address of disconnected node” entries (bits 0 to 5 and bits 8to 13 of the ring status word.) Correct any problems that are found.

3. Check the optical fiber cables and connectors at the nodes indicated bythe “node address of disconnected node” entries (bits 0 to 5 and bits 8 to13 of the ring status word.) Correct any problems that are found.

4. If the problem is not resolved with steps 2 and 3, it is necessary to plan asystem shutdown for maintenance. Shut down the system and replacethe following components to remove the component causing the problem: The cable and connectors between the affected nodes The affected Controller Link Unit(s) (1 or 2 Units)

One optical fiberdisconnected at twolocations


2. Check the power supply and backup power supply at the nodes indicatedby the “node address of disconnected node” entries (bits 0 to 5 and bits 8to 13 of the ring status word) and any nodes in between. Correct any prob-lems that are found.

3. Check the optical fiber cable connection at the interface indicated by theDisconnected Interface Flag (bit 6 of the ring status word) for the node in-dicated in bits 0 to 5. Correct any problems that are found.

4. Check the optical fiber cable connection at the interface indicated by theDisconnected Interface Flag (bit 14 of the ring status word) for the nodeindicated in bits 8 to 13. Correct any problems that are found.

5. If the problem is not resolved with steps 2 and 3, it is necessary to plan asystem shutdown for maintenance. Shut down the system and replacethe following components to remove the component causing the problem: The cable and connectors between the affected nodes The affected Controller Link Unit(s) (1 or 2 Units)

Communicationsapplications cannotcontinue operatingnormally

Both optical fibersdisconnected at twoor more locations

The information reflected in the ring status words may differ from node tonode, so the disconnection locations must be corrected in order.


2. Check the power supply and backup power supply at the nodes indicatedby the “node address of disconnected node” entries (bits 0 to 5 and bits 8to 13 of the ring status word) and any nodes in between. Correct any prob-lems that are found.

3. Check the optical fiber cables and connectors at the nodes indicated bythe “node address of disconnected node” entries (bits 0 to 5 and bits 8 to13 of the ring status word.) Correct any problems that are found.

4. Repeat steps 1 through 3 until all of the disconnections are corrected.

5. If the problem is not resolved with steps 1 through 4, it is necessary to plana system shutdown for maintenance. Shut down the system and replacethe following components to remove the component causing the problem: The cable and connectors between the affected nodes The affected Controller Link Unit(s) (1 or 2 Units)

9-4-4 Clearing the Ring Status WordsWhen a disconnection has been detected, the disconnected node information inthe ring status words is retained even if the disconnection has been corrected.The data is retained to provide a record of the disconnection if the connection is


198

just unstable and has been restored automatically. (The disconnected node in-formation will be overwritten if another error is detected later.)

The ring status information is recorded independently in each node, so one ofthe following methods must be used to clear the ring status words.

• Clear the ring status words with the support software (Controller Link SupportSoftware Ver. 2.00 or higher.) The support software operation clears the ringstatus information in all of the nodes.

• Send the NETWORK DISCONNECT DATA CLEAR command (FINS com-mand 06 06) from the ladder program or other source. The command must besent to all of the nodes.

Note If the power supplies (including backup power supplies) to the nodes are notturned ON simultaneously, the temporary disconnection will be detected as thenetwork starts up. When the network is started in token ring mode, verify that thedisconnection has been corrected automatically by checking the ring statuswords or the status of the RING LED indicators and then clear the ring statuswords.

The following example shows how to clear the ring status words by sendingFINS command 06 06 from the ladder program. In this example, the ControllerLink Unit’s unit number is 0 and no other Communications Units are mounted inthe local node.


199

Sample Ladder Program for CS1-series PCs

Executioncondition

NetworkDisconnection

Flag

• The ring status clear program will start when the execution condition(CIO 000000) is ON as long as the Network Disconnection Flag (CIO 152315for unit number 0) is OFF and the Port #7 Enabled Flag (A20207) is ON.


200

• Sets the control data.

DM word Contents Function

D00000 00 02 Number of bytes of command data = 2 bytes

D00001 00 04 Number of bytes of response data = 4 bytes

D00002 00 00 Destination network address = 0 (the local network)

D00003 FF FE Destination node address = FF (broadcast to all nodes)Destination unit address = FE (Communications Unit)

D00004 87 00 Response not required,Transmission port number = 7,Number of retries = 0 (Set to 0 for a broadcast.)

D00005 00 00 Response monitoring time = 0 s (Set to 0 for a broadcast.)

• Sets the FINS command code.06 06 Hex: NETWORK DISCONNECT DATA CLEAR

• Sends the 06 06 FINS command to all Communications Units (except the localnode) in the local network.






D00003 00 FE Destination node address = 00 (local node)Destination unit address = FE (Communications Unit)

D00004 07 02 Response required,Transmission port number = 7,Number of retries = 2

D00005 00 64 Response monitoring time = 10 s

• Sends the 06 06 FINS command to the Communications Unit at the local nodein the local network.

Note 1. In CS1-series PCs, the Port Enabled Flag for the port being used (A20200 toA20207 correspond to ports 0 to 7) will be turned OFF even if the PROTO-COL MACRO (PMCR) instruction is being executed.

2. When using the sample program as written above, be sure that the bits andwords in the sample program are not already being used by the program orother Special Units.


201

Sample Ladder Program for CV-series PCs

Executioncondition

NetworkDisconnection

Flag

• The ring status clear program will start when the execution condition(CIO 000000) is ON as long as the Network Disconnection Flag (CIO 152315for unit number 0) is OFF and the Port #7 Enabled Flag (A20207) is ON.






D00003 FF FE Destination node address = FF (broadcast to all nodes)Destination unit address = FE (Communications Unit)

D00004 87 00 Response not required,Transmission port number = 7,Number of retries = 0 (Set to 0 for a broadcast.)

D00005 00 00 Response monitoring time = 0 s (Set to 0 for a broadcast.)

• Sets the FINS command code.06 06 Hex: NETWORK DISCONNECT DATA CLEAR

• Sends the 06 06 FINS command to all Communications Units (except the localnode) in the local network.


202






D00003 00 FE Destination node address = 00 (local node)Destination unit address = FE (Communications Unit)

D00004 07 02 Response required,Transmission port number = 7,Number of retries = 2

D00005 00 64 Response monitoring time = 10 s

• Sends the 06 06 FINS command to the Communications Unit at the local nodein the local network.

Note When using the sample program as written above, be sure that the bits andwords in the sample program are not already being used by the program or otherSpecial Units.

9-4-5 Reading the Ring StatusIt is necessary to know the structure of the ring status word when displaying theword on a Programmable Terminal or other device because several pieces ofinformation are combined in the ring status word. In particular, the “node ad-dress of disconnected node” is stored in hexadecimal and mixed with other sta-tus flags, so the node addresses must be extracted and converted to decimal.

The sample programs shown below read the two “node address of disconnectednode” addresses and store these addresses in the DM area in BCD format. Inthis example, the Controller Link Unit’s unit number is 0.

The following diagram shows the structure of the ring status word.






Disconnected Interface Flag0: SL1 (uplink) or normal status1: SL2 (uplink)




Structure of the RingStatus Word


203

Sample Program for CS1-series PCs

Always ON Flag

• As long as the Network Disconnection Flag (CIO 152315 for unit number 0) isON, the “node address of the disconnected node” in bits 8 to 13 is stored inD00000 and the “node address of the disconnected node” in bits 0 to 5 is storedin D00001.

• The contents of D00000 are shifted 8 bits to the right to convert the node ad-dress to a proper hexadecimal value.

• The hexadecimal node addresses stored in D00000 and D00001 are con-verted to BCD.


Sample Program for CV-series PCs

Always ON Flag

• As long as the Network Disconnection Flag (CIO 152315 for unit number 0) isON, the “node address of the disconnected node” in bits 8 to 13 is stored inD00000 and the “node address of the disconnected node” in bits 0 to 5 is storedin D00001.

!

9-5SectionCleaning and Inspection

204

• The contents of D00000 are shifted 8 bits to the right to convert the node ad-dress to a proper hexadecimal value.

• The hexadecimal node addresses stored in D00000 and D00001 are con-verted to BCD.


9-5 Cleaning and InspectionThis section describes cleaning and inspection procedures that are to be per-formed as daily maintenance.

9-5-1 CleaningConduct the following periodic cleaning to keep the Controller Link Unit in opti-mum condition.• Wipe the Unit with a dry, soft cloth daily.• For stains that cannot be removed with a dry cloth, dip the cloth in medium

strength alcohol (2%), wring the cloth tightly, and then wipe down the Unit.• If glue, vinyl, or tape is left on the Unit for long periods of time, it will stain.

Remove these items during cleaning.

Caution Do not use volatile solvents such as benzine or paint thinner, or chemical clothsfor cleaning. They will damage the quality of the coating on the Unit.

9-5-2 InspectionController Link Units must be inspected on a regular basis to ensure correctoperation. Inspections should be conducted once every 6 to 12 months. If theUnit is subject to extremes in temperature or humidity, inspections should beconducted on a more regular basis.

Tools and Equipment Need for InspectionThe following tools and equipment will be needed to perform inspection andadjustments.• Assorted flat-blade and Phillips screwdrivers• Circuit tester or digital voltmeter• Industrial-grade alcohol and clean cotton cloth• Synchroscope• Pen-chart recording oscilloscope• Thermometer, hygrometer

Inspection ItemsInspect the follow items to see if they deviate from the prescribed standards. Ifany items do deviate from the standard either adjust so they are within the oper-ating range or adjust the Unit accordingly.

Item Description Inspection instrumentAmbient condi- Temperature: 0° to 55°C Thermometertions Humidity: 10% to 90% (no

condensation or freezing)Hygrometer

Dust-free Sight

Installation Units securely attached?Communications cable connectorstight?Communications cabling used forexternal wiring intact (no breaks)?

Flat-blade screwdriver andsight

!

9-6SectionHandling Precautions

205

9-6 Handling PrecautionsThe Controller Link Unit is a Network device. If the Unit is damaged, it will effectthe entire Network, so always ensure repairs are undertaken immediately. Werecommend that you have a spare Controller Link Unit on hand so that repairsmay be conducted quickly.

9-6-1 Replacing the UnitObserve the following precautions when replacing the Unit.

• Always turn off the power before replacing the Unit.

• Check that the new Unit is not faulty.

• If you suspect that a poor connection is the cause of a malfunction, clean theconnectors using a clean, soft cloth and industrial-grade alcohol. Remove anylint or threads left from the cloth, and remount the Unit.

• When returning a faulty Unit for repairs, always attach a detailed fault report tothe Unit and return to you nearest OMRON outlet as listed at the back of thismanual.

Note In order to prevent faulty operation be sure to turn off the power to all nodesbefore replacing the Unit.

When replacing the Unit, do not reconnect that node to the Network before carry-ing out the procedures listed below. In particular, a node with a small address willbecome the polling node and communicate the initial network parameter statusto other nodes, so there is the chance that network parameters in the entire Net-work will be damaged.

9-6-2 Setting the Unit after ReplacementAfter replacing a Controller Link Unit, reset the hardware switches, softwareswitches, and data link tables, and wire it in the same manner as the previousUnit. This section describes settings that require particular care. Refer to theUnit replacement methods later in this section for details on replacing the Unit.

Caution After replacing the CPU Unit, transfer important data, such as DM and HR Areacontents, to the new CPU Unit before restarting operation. Depending on theprogram, accidents can occur as a result of incorrect DM or HR Area contents.

CVM1 and CV-series Controller Link Units store data such as data link tables,network parameters, and routing tables in the CPU Unit. When replacing theCPU Unit, reset these settings using the Controller Link Support Software.

Setting the Transmission FormatThere are two kinds of CS1-series Optical Controller Link Units: theCS1W-CLK11 Optical Bus Controller Link Unit and the CS1W-CLK12 OpticalRing Controller Link Unit that uses H-PCF cable.

The following transmission format setting must be made in advance when usinga CS1W-CLK12 Optical Ring Controller Link Unit as a substitute for aCS1W-CLK11 Optical Bus Controller Link Unit. The control bits for CS1-seriesController Link Units are in D30000 + (100 × unit number).

0: Always set to 0–: Other settings Transmission format


206

Transmission Path

Bit Setting

9 8

0 0 Token ring mode

0 1

1 0

1 1 Token bus mode

The Optical Bus and Optical Ring Controller Link Units can be used together ifyou want to keep the system in token bus mode (daisy-chain connections).Some of the Optical Bus Controller Link Units in the system can be replaced withOptical Ring Controller Link Units that use H-PCF cable.

1, 2, 3... 1. Replace the Unit and turn the power ON without the optical fiber cable con-nected.

2. Set the transmission format for the replaced Unit to “token bus mode” withbits 8 and 9 of D30000 + (100 × unit number).

3. Turn the power OFF and then ON again and verify that the Controller LinkUnit’s RING indicator is not lit. (The Unit is set to token bus mode if the RINGindicator is not lit.)

4. Leave the cable disconnected and set the network parameters. See “Reset-ting Network Parameters” below for details.

5. Turn the power OFF and install the network cable connector.6. Check the connections, turn the power ON to all of the nodes, verify that the

INS indicators are lit, and verify that the network has started operating nor-mally.

If all of the Controller Link Units in the network are Optical Ring Controller LinkUnits (using H-PCF cable), the network can operate in token ring mode. All of thenodes in the network must be set to token ring mode.

1, 2, 3... 1. Replace the Unit and turn the power ON without the optical fiber cable con-nected.

2. Set the transmission format for the replaced Unit to “token ring mode” withbits 8 and 9 of D30000 + (100 × unit number).

3. Turn the power OFF and then ON again and verify that the Controller LinkUnit’s RING indicator is lit. (The Unit is set to token ring mode if the RINGindicator is lit.)

4. Turn the power OFF and install the optical fiber cable connector. Connectthe nodes at the ends of the network to form a ring configuration.

5. Check the connections, turn the power ON to all of the nodes, verify that theINS indicators are lit, and verify that the network has started operating nor-mally.

Resetting Network ParametersWhen a CPU Unit has been replaced for a CVM1 or CV-series Controller LinkUnit, it is necessary to reset the network parameters, data link tables, and rout-ing tables. This sections describes the resetting procedure for the networkparameters. For details on data link table resetting procedures, refer to 5-2 Set-ting Data Links and for routing table resetting procedures, refer to 7-4 SettingRouting Tables.

1, 2, 3... 1. Network parameters are read from the polling node when the Network isactivated and this information is distributed to all nodes in the Network. Forthis reason, set the polled/polling node setting in the DM parameter area forthe node replaced to a polled node before reconnecting the Unit to the Net-work.

Continuing Operation inToken Bus Mode

Changing Operation toToken Ring Mode

!


207


0: Polling node1: Polled node

Polled node/polling node

– : Other settingsDM 30000 + 100 × n n = Unit number – – –


0: Polling node mode1: Polled node

Polled node/polling node


2. Turn the power off once, connect the Controller Link Network and turn thepower on again. Check that the Unit is participating in the Network.

If the INS indicator is lit and the ERC and ERH indicators are off, then theUnit is in the Network.

3. Return the Polled node/polling node setting of the node in which the Unitwas replaced to “polling node.”


0: Polling node1: Polled node

Polled node/Polling node



0: Polling node mode1: Polled node

Polled node/Polling node

– : Other settingsDM 2000 + 100 × n n = Unit number

4. Restart the Controller Link Unit or turn the power off and then back on again,and then check to see if the Unit is participating in the Network.

If the INS indicator is lit and the ERC and ERH indicators are not lit, then theUnit is in the Network.

Note Restart the Unit only when the data links are halted.

Using the above procedure to reset the network parameters of the node that wasreplaced to the same as the other nodes in the Network.

Caution When a CPU Unit has been replaced for a CVM1 or CV-series Controller LinkUnit, do not connect that node to the Network before carrying out the above pro-cedures. In particular, a node with a small address will become the polling nodeand communicate the initial network parameter status to other nodes, so there isthe chance that network parameters in the entire Network will be damaged.

9-6-3 Replacing the Unit

CS1, CVM1 and CV-series Controller Link UnitsNote CS1, CVM1 and CV-series Controller Link Unit data is stored in the EEPROM of

the CPU Unit. For this reason even if the Controller Link Unit is replaced, on thehardware settings must be made to return all settings to their previous status. If,however, the CPU Unit is replaced, the data link tables and routing tables willneed to be reset.

1, 2, 3... 1. Turn off all nodes in the Controller Link Network.


208

2. Detach the communications cables attached to the Controller Link Unit to bereplaced and remove the Unit.

3. Mount the new Controller Link Unit in the PC and connect the communica-tions cables. (Refer to Section 3.)

4. Set the unit number, node address, baud rate, and the terminating resis-tance for the new Unit to the same settings as the previous Unit. (Refer toSection 4.)

5. Turn on the power to the PCs at all nodes in the Controller Link Networkother than those for which the Controller Link Unit was replaced.

6. Check that all the other nodes are active and then turn on the power to thePC with the Controller Link Unit that was replaced.

7. Using the Controller Link Support Software, read the network parametersand make sure the Network is operating normally.

8. If the data links are not activated automatically, start the data links from thedata link startup node.

9. Check that the data links are operating normally by monitoring them fromthe Controller Link Support Software.

209

Appendix AStandard Models

Controller Link UnitsApplicable PC Model number Specifications Remarks

CS1-series PCs CS1W-CLK12 Optical Ring System(H-PFC Cable)

See CPU Unitsand Programming

CS1W-CLK11 Optical Bus System Devices in this

CVM1 andCV-series PCs

CVM1-CLK12 Optical Ring System(H-PFC Cable)

appendix.

Controller Link Support BoardApplicable computer Model number Remarks

IBM PC/AT or compatible 3G8F5-CLK11-E (Optical) Controller Link SupportSoftware included.

Controller Link Support SoftwareApplicable computer Model number Remarks

IBM PC/AT or compatible C200HW-ZW3AT2-E-V2 English version

CX-Programmer with CX-NetApplicablecomputer

Name Model number Applicable PCs

IBM PC/AT orcompatiblerunning Windows95/98 orWindows NT

CX-Programmerwith CX-Net

WS02-CXP-E CS1-series,C200HX/HG/HE,CVM1, CV-series,and CQM1H-seriesPCs


210

Optical Fiber Cable Connectors and Accessories

Optical Fiber CablesName Specifications Model

H-PCF cables Black 10 m S3200-HCCB101

50 m S3200-HCCB501

100 m S3200-HCCB102

500 m S3200-HCCB502

1,000 m S3200-HCCB103

Orange 10 m S3200-HCCO101

50 m S3200-HCCO501

100 m S3200-HCCO102

500 m S3200-HCCO502

1,000 m S3200-HCCO103

Note The optical fiber cable model numbers are as follows.

S3200-H

Tensioner optionNone: Standard (with tension member)N: Without tension member

Cable length

A B(A/10) x 10B m

Cable colorB: BlackO: Orange

Cable specificationL: With power supply lineC: Without power supply line

TypeB: CordC: Cable

ConnectorsName Model Remarks

OpticalConnector

S3200-COCF2011 Connects a cable to a node. Twoconnectors are required for each cable.(Full-lock connector for crimp-cut cable.)

S3200-COCF2511 Connects a cable to a node. Twoconnectors are required for each cable.(Half-lock connector for crimp-cut cable.)

Inline Adapter S3200-COIAT2000 Connects two cables. One adapter isrequired to connect two cables.


211

Optical Fiber Cables with ConnectorsThe following Optical Fiber Cables are available with Connectors already attached. (These cables have powersupply lines and tension members, which aren’t used in the Controller Link Network.)

Specifications Length ModelOptical Fiber Cable Connectors: 2 m S3200-CN201-20-20

S3200-COCF2011⇓

5 m S3200-CN501-20-20S3200-COCF2011⇓ 10 m S3200-CN102-20-20

S3200-COCF201115 m S3200-CN152-20-20

20 m S3200-CN202-20-20



S3200-COCF2011⇓

5 m S3200-CN501-20-25S3200-COCF2011⇓ 10 m S3200-CN102-20-25

S3200-COCF251115 m S3200-CN152-20-25

20 m S3200-CN202-20-25



S3200-COCF2511⇓

5 m S3200-CN501-25-25S3200-COCF2511⇓ 10 m S3200-CN102-25-25

S3200-COCF251115 m S3200-CN152-25-25

20 m S3200-CN202-25-25


Note Special training is required to assemble Optical Fiber Cables and con-nectors with epoxy adhesive. Contact your OMRON dealer for details onother optical fiber cords and cables.

Assembly ToolsThe following tools are used to assemble optical networks.

Specifications Specifications Model

Optical ConnectorAssembly Tool

Applicable Connector:S3200-COCF2011/2511

S3200-CAK1062

Optical Power Tester Enclosed Head Unit:S3200-CAT2702

Applicable Connector:S3200-COCF2011/2511

S3200-CAT2700

Master Fiber Applicable Head Unit:S3200-CAT2702

S3200-CAT2001H


212

CPU Units and Programming Devices

CPU UnitsPC Model number Remarks

CS1-series PCs CS1H-CPU67-EV1CS1H-CPU66-EV1CS1H-CPU65-EV1CS1H-CPU64-EV1CS1H-CPU63-EV1CS1G-CPU45-EV1CS1G-CPU44-EV1CS1G-CPU43-EV1CS1G-CPU42-EV1

---

SYSMAC CV500,CV1000, or CV2000PCs (see note 1)

CV500-CPU01-EV1CV1000-CPU01-EV1CV2000-CPU01-EV1

Earlier versions of theCPU Units can alsobe used.

SYSMAC CVM1 PCs (see note 1)

CVM1-CPU01-EV2CVM1-CPU11-EV2CVM1-CPU21-EV2CVM1D-CPU21-E

Earlier versions of theCPU Units can alsobe used.

SYSMACCQM1H-series PCs

CQM1H-CPU51CQM1H-CPU61

---




Note Routing tables are required if any of the CVM1 or CV-series CPU Units inthe network have been manufactured on or before April 1996. Themanufacturing data can be determined from the lot number on the side ofthe CPU Unit.

213

Appendix BMemory Areas

This appendix provides easy reference to the words in PC memory areas used by Controller Link Networks.

CS1-series PCsAuxiliary Area

Word(s) Bit(s) Function

A202 00 to 07 Communications Port Enabled (NetworkCommunications Enabled) Flags

A203 to A210 00 to 15 Port #0 to #7 Completion Codes

A219 00 to 07 Port #0 to #7 Execute Error (NetworkCommunications Execute Error) Flags

A302 00 to 15 CS1 CPU Bus Unit Initializing Flags

A401 13 Duplicate Number Error Flag (fatal error)

A402 03 CS1 CPU Bus Unit Setting Error Flag

07 CS1 CPU Bus Unit Error Flag

A410 00 to 15 CPU Bus Unit Duplicate Number

A417 00 to 15 CS1 CPU Bus Unit Error, Unit Number Flags

A427 00 to 15 CS1 CPU Bus Unit Setting Error Unit Number

A501 00 to 15 CS1 CPU Bus Unit Restart Bits

Network Status FlagsBits A20200 through A20207 are turned ON to indicate that ports #0 through #7, respectively, are enabled for theSEND(90), RECV(98), CMND(490) and PMCR. Bits A219200 through A219207 are turned ON to indicate that anerror has occurred in ports #0 through #7, respectively, during data communications using SEND(90), RECV(98),CMND(490), or PMCR. Refer to page 97A203 through A210 contain the completion codes for ports #0 through #7, respectively, following data communica-tions using SEND(90), RECV(98), CMND(490), or PMCR. Refer to 97.

CS1 CPU Bus Unit Initializing FlagsBits A30200 through A30215 turn ON while the corresponding CS1 CPU Bus Units (Units #0 through #15, respec-tively) are initializing.

CS1 CPU Bus Unit Setting Error Flag and Unit NumberBit A40203 is turned ON when the CS1 CPU Bus Units actually installed differ from the Units registered in the I/Otable. The unit number of the CS1 CPU Bus Unit involved is written to word A427.Bits A42700 through A42715 correspond to CS1 CPU Bus Units #0 through #15, respectively. When a erroroccurs, the bit corresponding to the unit number of the CS1 CPU Bus Unit involved is turned ON.

CS1 CPU Bus Unit Error FlagBit A40207 is turned ON when a parity error occurs during the transmission of data between the CPU Unit and CS1CPU Bus Units. The unit number of the CS1 CPU Bus Unit involved is written to word A417.

CS1 CPU Bus Unit NumbersBits A41000 through A41015 correspond to CS1 CPU Bus Units #0 through #15, respectively. When two CPU BusUnits have the same unit number, the bits corresponding to the unit numbers of the CS1 CPU Bus Units involvedare turned ON.

CS1 CPU Bus Unit Duplication Error FlagBit A40113 is turned ON when two CS1 CPU Bus Units have been assigned the same unit number. The duplicatedunit number is indicated in A410.

CS1 CPU Bus Unit Error, Unit Number FlagsWhen an error occurs in a data exchange between the CPU Unit and an CS1 CPU Bus Unit, the CS1 CPU Bus UnitError Flag (A40207) is turned ON and the bit in A417 corresponding to the unit number of the Unit where the erroroccurred is turned ON.


214

CS1 CPU Bus Unit Restart BitsBits A50100 through A50115 can be turned ON to reset CS1 CPU Bus Units number #0 through #15, respectively.The Restart Bits are turned OFF automatically when restarting is completed.

CIO Area: CS1 CPU Bus Unit AreaThe CS1 CPU Bus Unit Area (CIO Area) is allocated to CS1 CPU Bus Units according to the unit numbersassigned to them, as shown below. Each Unit is allocated 25 words.

Unit no. Words Unit no. Words

0 1500 to 1524 8 1700 to 1724

1 1525 to 1549 9 1725 to 1749

2 1550 to 1574 10 1750 to 1774

3 1575 to 1599 11 1775 to 1799

4 1600 to 1624 12 1800 to 1824

5 1625 to 1649 13 1825 to 1849

6 1650 to 1674 14 1850 to 1874

7 1675 to 1699 15 1875 to 1899

Error Information: CIO 1500 + 25 x (Unit No.) (See page 177)

1: Network parameter error (In PC’s EEPROM) 1: Data link table error (in PC’s EEPROM)1: Routing table error (in PC’s EEPROM)1: PC system setting error1: EEPROM error1: Duplicate node address setting error1: Inconsistent network parameters1: Communications controller send error1: Communications controller hardware error1: Error log exists

Polling Node Address, Startup Node Address: CIO 1500 + 25 x (Unit No.) + 1 (See page 177)



Network Participation Status: CIO 1500 + 25 x (Unit No.) + 2 to 5 (See pages 98, 178)

The numbers in the squares indicate node addresses.The corresponding node participation status is as follows:0: Not participating in the network1: Participating in the network

Note If the local node is not participating in the net-work, the status for the local node will be 0 (notparticipating), and the status for the othernodes will be indefinite.


215

Local Data Link Participation Status: CIO 1500 + 25 x (Unit No.) + 6 (See page 178)


Data Link Status: CIO 1500 + 25 x (Unit No.) + 7 to + 22 (See pages 77, 178)When the first data link status word for manually set data link tables or for automatically set data links is not set or isset to 0, the data link status is stored in the words shown below.


Node 2Node 4Node 6Node 8Node 10Node 12Node 14Node 16Node 18Node 20Node 22Node 24Node 26Node 28Node 30Node 32












+7+8+9+10+11+12+13+14+15+16+17+18+19+20+21+22


216


Node 4





Node 8



Node 40Node 44


Node 600

Node 3

Node 7



Node 39Node 43


Node 590

Node 2

Node 6



Node 38Node 42


Node 58Node 62

Node 1

Node 5



Node 37Node 41


Node 57Node 61













217


Power supply status: 0: Power supplied1: Power not supplied

DM Area: CS1 CPU Bus Unit AreaThe CS1 CPU Bus Unit Area (data memory) is allocated to CS1 CPU Bus Units according to the unit numbersassigned to them, as shown below. Each Unit is allocated 100 words, of which 10 words are used. In the ControllerLink Unit this area is called the DM Area.


0 DM30000 toDM30009

8 DM30800 toDM30809

1 DM30100 toDM30109

9 DM30900 toDM30909

2 DM30200 toDM30209

10 DM31000 toDM31009

3 DM30300 toDM30309

11 DM31100 toDM31109

4 DM30400 toDM30409

12 DM31200 toDM31209

5 DM30500 toDM30509

13 DM31300 toDM31309

6 DM30600 toDM30609

14 DM31400 toDM31409

7 DM30700 toDM30709

15 DM31500 toDM31509

Software Switches (DM30000 + 100 × Unit No.)

Data link mode 00: Manual01: Automatic

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 00 0 0 0 0 0 0 0

CS1 CPU Bus Unit PC Setup Initialization (See note)0: Do not initialize CS1 CPU Bus Unit PC Setup1: Initialize CS1 CPU Bus Unit PC Setup


0

Note Initializes the network parameters registered in the CS1 CPU Bus Unit PC Setup Area at the CPU Unitand clears the data link tables.

Data link Start BitStart: Changed from OFF to ON or set to ONwhen power is turned ONStop: Changed from ON to OFFTransmission path format

Bit9 80 0

Setting

Token-ring mode0 11 01 1 Token-bus mode


218

Parameters for Automatically Setting Data Links: DM30000 + 100 × (Unit No.) + 1 to 9

Area 1 data link start word (BCD)

Area 1 type

Number of send words per node of area 1 (BCD)

Rightmost 4 digits of data link start word of area 2 (BCD)Leftmost digit of data link start word of area2 (BCD)


–: Not used.

Note N+10 and N+11 (node addresses 33 to 62) cannot be used in Optical Bus Systems.

Nodes to participate in the data links



15 8 7 0

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

+1

+2

+3

+4

+5

+6

+7

+8

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17+9

Area 2 type


00

48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33+10

– – 62 61 60 59 58 57 56 55 54 53 52 51 50 49+11

BCD: Set the value as binary-coded decimal.


Auxiliary AreaWord(s) Bit(s) Function

A001 00 to 15 CPU Bus Unit Restart Bits

A015 00 to 15 CPU Bus Service Disable Bits

A302 00 to 15 CPU Bus Unit Initializing Flags

A401 12 CPU Bus Error Flag

A402 03 CPU Bus Unit Setting Error Flag

07 CPU Bus Unit Error Flag

A405 00 to 15 CPU Bus Unit Error Unit Number

A410 00 to 15 CPU Bus Unit Duplicate Number

A422 00 to 15 CPU Bus Unit Error Unit Number

A427 00 to 15 CPU Bus Unit Setting Error Unit Number

A502 00 to 07 Port #0 to #7 Enabled Flags

08 to 15 Port #0 to #7 Execute Error Flags

A503 to A510 00 to 15 Port #0 to #7 Completion Codes (See page 99)

CPU Bus Unit Restart BitsBits A00100 through A00115 can be turned ON to reset CPU Bus Units number #0 through #15, respectively. TheRestart Bits are turned OFF automatically when restarting is completed.

Do not turn these bits ON and OFF in the program; manipulate them from the CVSS.

CPU Bus Service Disable BitsBits A01500 through A01515 can be turned ON to stop service to CPU Bus Units numbered #0 through #15,respectively. Turn the appropriate bit OFF again to resume service to the CPU Bus Unit.

CPU Bus Unit Initializing FlagsBits A30200 through A30215 turn ON while the corresponding CPU Bus Units (Units #0 through #15, respectively)are initializing.

CPU Bus Error and Unit FlagsBit A40112 is turned ON when an error occurs during the transmission of data between the CPU Unit and CPU BusUnits, or a WDT (watchdog timer) error occurs in a CPU Bus Unit. The unit number of the CPU Bus Unit involved iscontained in word A405.


219

Bits A40500 through A40515 correspond to CPU Bus Units #0 through #15, respectively. When a CPU Bus Erroroccurs, the bit corresponding to the unit number of the CPU Bus Unit involved is turned ON.

CPU Bus Unit Setting Error Flag and Unit NumberBit A40203 is turned ON when the CPU Bus Units actually installed differ from the Units registered in the I/O table.The unit number of the CPU Bus Unit involved is written to word A427.

Bits A42700 through A42715 correspond to CPU Bus Units #0 through #15, respectively. When a error occurs, thebit corresponding to the unit number of the CPU Bus Unit involved is turned ON.

CPU Bus Unit Error Flag and Unit NumbersBit A40207 is turned ON when a parity error occurs during the transmission of data between the CPU Unit and CPUBus Units. The unit number of the CPU Bus Unit involved is written to word A422.

Bits A42200 through A42215 correspond to CPU Bus Units #0 through #15, respectively. When a CPU Bus UnitError occurs, the bit corresponding to the unit number of the CPU Bus Unit involved is turned ON.

CPU Bus Unit NumbersBits A41000 through A41015 correspond to CPU Bus Units #0 through #15, respectively. When two CPU BusUnits have the same unit number, the bits corresponding to the unit numbers of the CPU Bus Units involved areturned ON.

Network Status FlagsBits A50200 through A50207 are turned ON to indicate that ports #0 through #7, respectively, are enabled for theSEND(192), RECV(193), and CMND(194). Bits A50208 through A50215 are turned ON to indicate that an errorhas occurred in ports #0 through #7, respectively, during data communications using SEND(192), RECV(193), orCMND(194).

A503 through A510 contain the completion codes for ports #0 through #7, respectively, following data communica-tions using SEND(192), RECV(193), or CMND(194).

CIO Area: CPU Bus Unit AreaThe CPU Bus Unit Area is allocated to CPU Bus Units according to the unit numbers assigned to them, as shownbelow. Each Unit is allocated 25 words. The Controller Link Units use 22 of the words allocated to them.


0 1500 to 1524 8 1700 to 1724

1 1525 to 1549 9 1725 to 1749

2 1550 to 1574 10 1750 to 1774

3 1575 to 1599 11 1775 to 1799

4 1600 to 1624 12 1800 to 1824

5 1625 to 1649 13 1825 to 1849

6 1650 to 1674 14 1850 to 1874

7 1675 to 1699 15 1875 to 1899

Error Information: CIO 1500 + 25 x (Unit No.) (See page 177)





1: EEPROM error



1: Error log exists


220

Polling Node Address, Startup Node Address: CIO 1500 + 25 x (Unit No.) + 1 (See page 177)



Network Participation Status: CIO 1500 + 25 x (Unit No.) + 2, + 3 (See pages 98, 178)

The numbers in the squares indicate node addresses.The corresponding node participation status is as follows:0: Not participating in the network1: Participating in the network

Note If the local node is not participating in the net-work, the status for the local node will be 0 (notparticipating), and the status for the othernodes will be indefinite.

Local Data Link Participation Status: CIO 1500 + 25 x (Unit No.) + 6 (See page 178)

1: Local node data link participating0: Local node data link not participating or data link inactive

Data Link Status: CIO 1500 + 25 x (Unit No.) + 7 to + 22 (See pages 77, 178)When the first data link status word for manually set data link tables or for automatically set data links is not set or isset to 0, the data link status is stored in the words shown below.














+7+8+9+10+11+12+13+14+15+16+17+18+19+20+21+22


221






Node 4

Node 8

Node 12Node 16Node 20Node 24Node 30

Node 32Node 36



0

Node 3

Node 7


Node 31Node 35



0

Node 2

Node 6


Node 30Node 34



Node 62

Node 1

Node 5


Node 29Node 33



Node 61











Note The disconnected node information is valid only when bit 15 (the NetworkDisconnection Flag) is ON. If bit 15 is OFF, the previous disconnected nodeinformation is retained.


222



DM Area: CPU Bus Unit Area

The CPU Bus Unit Area (data memory) is allocated to CPU Bus Units according to the unit numbers assigned tothem, as shown below. Each Unit is allocated 100 words, of which 10 words are used. In the Controller Link Unitthis area is called the DM Area.


0 DM2000 toDM2009

8 DM2800 toDM2809

1 DM2100 toDM2109

9 DM2900 toDM2909

2 DM2200 toDM2209

10 DM3000 toDM3009

3 DM2300 toDM2309

11 DM3100 toDM3109

4 DM2400 toDM2409

12 DM3200 toDM3209

5 DM2500 toDM2509

13 DM3300 toDM3309

6 DM2600 toDM2609

14 DM3400 toDM3409

7 DM2700 toDM2709

15 DM3500 toDM3509

Software Switches (DM2000 + 100 × Unit No.)

Data link mode 00: Manual01: Automatic

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 00 0 0 0 0 0 0 0


0

Data link Start BitStart: Changed from OFF to ON or set to ONwhen power is turned onStop: Changed from ON to OFFTransmission path format

Bit9 80 0

Setting

Token-ring mode0 11 01 1 Token-bus mode

EEPROM Clear Bit* 0: Do not clear EEPROM1: Clear EEPROM

*Clears the network parameters, data link tables, and routingtables stored in EEPROM in the PC’s CPU Unit.


223

Parameters for Automatically Setting Data Links: DM 2000 + 100 x (Unit No.) + 1 to + 9 (See page 72)

Area 1 data link start word (BCD)

Area 1 type


Rightmost 4 digits of data link start word of area 2(BCD)Leftmost digit of data link start word of area2 (BCD)


Nodes to participate in the data links



15 8 7 0

15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

+1

+2

+3

+4

+5

+6

+7

+8

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17+9

Area 2 type


00

48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33+10

– – 62 61 60 59 58 57 56 55 54 53 52 51 50 49+11

–: Not used.

Note N+10 and N+11 (node addresses 33 to 62) cannot be used in Optical Bus Systems.

BCD: Set the value as binary-coded decimal.

225

Appendix CCS1-series Optical Bus Controller Link Units

Component Names and Functions

Unit number switches (Refer to p. 45)

Two rotary switches. The unit number is set in single-digithexadecimal for the network to which the PC is connected.

Indicators (Refer to p. 35 and 160)

LED indicators that display the Unit and network status.

Node address switches (Refer to p. 46)


Optical connectors (Refer to p. 38)

Connectors to connect to the Controller Link Network communicationscable (optical fiber cable).

Power Supply Terminal Block (Refer to p. 42)

Connect the backup battery for the node bypass function.

Optical Unit IndicatorsName Color Status Meaning

RUN Green Lit Unit operating normally.(operating) Not lit Unit error.



Red Lit Communications error, node address setting error, hardware error or aconnection error between the Optical Controller Link Unit and SYSMACLINK.


ERH (PC error)

Red Lit PC error, PC interface error, EEPROM error, unit number error, or I/O tablenot set

Not lit No error.

INS Yellow Lit Unit is participating (inserted) in the network.(networkparticipation) Not lit Unit is not participating (inserted) in the network.




Yellow Lit Manual(see note)

Note: M/A is always not lit when data links are not active in the

Not lit Automatic network.




226

Note Even when the local node does not participate in the data link, the indicator will be lit if there are manually setdata links active on the network.


Overview

Unit Number

Setting range Nodes

00 to F (default is 0) All nodes in the Network

Node Address

Setting range Nodes

01 to 32 (default is 01) All nodes in the Network

Unit NumberSet the unit number for each Unit using the rotary switches on the front of the Unit. The unit number is used toidentify a CPU Bus Unit within the PC. Any unit number can be set between 0 and F in hexadecimal (00 to 15 indecimal).


Item Specifications

Setting method Single-digit hexadecimal

Setting range 0 to F (decimal 00 to 15, default is 0)


Set the node address using a small flat-blade screwdriver, being careful not to damage the rotary switches.


2. When setting a Unit for the first time or changing the existing setting, create a I/O table in the PC’s CPUUnit.

3. Do not set the same unit number twice within the same PC. An error will occur if the same unit number isset for two different Unit, and the CPU Unit will not be able to recognize the Units.

4. When the Unit is recognized by the PC’s CPU Unit, “NS” will be shown in the I/O table displayed for theCX-Programmer programming device.


6. The unit number determines the words used by the Controller Link Unit in PC memory.

Node AddressesSet the node address of each Unit in the Network using the rotary switch on the front of the Unit. The node addressis used to identify each node in the Network.


227

The node address can be set to any value between 01 and 32.

1’s digit

10’s digit

0 1


Item Specifications




Set the node address using a small flat-blade screwdriver, being careful not to damage the rotary switches.


2. Do not set the same node address twice within the same Network. An error will occur if the same addressis set for two different nodes. The ERC indicator on the front of the Unit will light (Communications ErrorFlag) and either communications will stop, or the INS indicator will not light and you will be unable toparticipate in the Network.

3. The send sequence for the data link areas is determined according to the sequence of node addressesfor automatically set data links.

4. Assign node addresses consecutively beginning from 01 whenever possible to minimize Networkconstruction time.


228

Communications SpecificationsOptical Ring System

Items Specifications

Communications method N:N token bus

Code Manchester code

Modulation Baseband code

Synchronization Flag synchronization (conforms to HDLC frames)

Transmission path form Daisy-chain

Baud rate 2 Mbps

Maximum transmissiondistance

20 km

Maximum distancebetween nodes

Crimp cut: 800 m Adhesive: 1 km (See note)

Media H-PCF cable (optical two-core cable)

Node connection method Connected via a special (full-lock connector) connector. (A half-lock connector can also beused.)

Maximum number ofnodes

32 nodes

Communications functions Data links and message service

Number of data link words Transmission area per node: 1,000 words (2,000 bytes) max.

Data link area in one PC (CS1-series PC) (send/receive):12,000 words (24,000 bytes) max.

Data link area in one IBM PC/AT or compatible (transmission/reception):32,000 words (64,000 bytes) max.

Number of data link words in one network (total transmission):32,000 words (64,000 bytes) max.

Data link areas Bit areas (IR, AR, LR, CIO), data memory (DM), and extended data memory (EM)

Message length 2,012 bytes max. (including the header)

RAS functions Polling node backup function

Self-diagnosis function (hardware checking at startup)

Echoback test and broadcast test (using the FINS command)

Watchdog timer

Error log function

Node bias function

Error control Manchester code check

CRC check (CCITT X16 + X12 + X5 + 1)

Note The maximum distance between nodes depends on the connector and cable processing methods.


229


10135

130

231

Index

A–Bapplications precautions, xiii, 20

asynchronous operation, 152

automatic setting, setting example, 74

backup power supply, 18cable connections, 42wiring, 40

Ccables, 6

optical, 12Optical Fiber Cables, 38

CMND instruction, message service, 84

commands, FINS commands, 103

commands for Controller Link Units, 104BROADCAST TEST DATA SEND, 117BROADCAST TEST RESULTS READ, 116CONTROLLER DATA READ, 105CONTROLLER STATUS READ, 107DATA LINK START, 105DATA LINK STATUS READ, 110DATA LINK STOP, 105ECHOBACK TEST, 116ERROR LOG CLEAR, 118ERROR LOG READ, 117NETWORK STATUS READ, 108

commands for CS1-series PCs, 91

commands for CVM1 and CV-series PCs, 91

communicationscables, 12

optical, 12data exchange timing, 148data processing time, 149instructions, 94mechanism, 142preparations, 24selecting functions, 18timing calculation example, 149

Communications Cables, 12

communications cycle time, 144active data links, 145definition, 143non-active data links, 146

Connectorsinstallation, 40models, 210

Controller Link, 2network

features, 6reading operating status, 108remote, 131

Controller Link Support Boards, models, 209

Controller Link Support Software, 15, 16models, 209stopping and starting data links, 76

Controller Link UnitsCS1-series, settings, 44CVM1 and CV-series, settings, 47models, 11, 209

CPU Units, models, 212

CQM1H-series PCs, models, 212

CS1-series PCscommands, 91data link tables, 59installation, 38memory areas, 213models, 212RECV, 86RECV delay time, 155SEND, 85SEND delay time, 153SEND/RECV instructions, 85synchronous operation, 150

CV-series PCsSee also CVM1 and CV-series PCsmodels, 212

CVM1 and CV-series PCsasynchronous operation, 152commands, 91installation, 36memory areas, 218RECV, 88RECV delay time, 155SEND, 87SEND delay time, 153SEND/RECV instructions, 87synchronous operation, 150

CVM1 PCs, models, 212

CX-Net, 17, 57

CX-Programmer, 17, 130, 131

Index

232

Ddata areas, SEND/RECV, 92

data link, I/O response time, 148

data link tablecreating manually, 63CVM1 and CV-series PCs, 60specifications, 59

data links, 6automatic setting, 26, 69

examples, 53creating, 19description, 52error detection, 81manual setting, 24, 57

examples, 52, 63from computer node, 58from Programming Device, 58

modes, 80procedures, 24reading data link status, 110selecting automatic or manual, 57setting, 57specifications, 55starting, 75, 105status, 77

manipulating bit/word status, 81using data link status area, 77using indicators, 77

stopping, 75, 105stopping and starting, 75

dimensionscrimp terminals, 42CS1 Units, 34, 229CVM1 and CV Units, 36

EEC Directives, xv

EMC Directives, xv

error codes, 184

error log, 5, 183reading and clearing, 190table, 183

errorsclearing, 118error handling, 7error log, 5reading, 117response codes, 120

FFINS commands

errors, 120response codes

errors, 120sending and receiving, 103

responses, 103sending and receiving, 103stopping and starting data links, 76

flagsNetwork Instruction Enabled Flag, 97Network Instruction Error Flag, 97SEND/RECV, 97SEND/RECV operations, 98

II/O tables, 24, 26

indicatorschecking data link status, 77Controller Link Units, CS1 Units, 225troubleshooting using indicators, 160

inspection, tools and equipment needed, 204

installation, 24, 36communications cables, 38, 40connectors, 40CS1-series PCs, 38CVM1 and CV-series PCs, 36

instructionsCMND, 89RECV, 85SEND, 85

Mmaintenance

cleaning, 204inspection, 204

manual setting, examples, 63

memory areas, 213

message delay times, 153

message service, 6, 19operations, 95procedure, 28specifications, 96

models, 11

Nnetwork

interconnecting Controller Link networks, 128interconnecting other OMRON networks, 128other remote networks, 132parameters, 143

specifying, 144relay errors, 119remote Controller Link networks, 131

node addresses, settingCS1 Optical Units, 226CS1 Wired Units, 46CVM1 and CV Units, 49

Index

233

node configurations, 7

number of polled units, 144

Ooffsets

application example, 55usage, 54

operating environment precautions, xiii

Optical Fiber Cable Connectors, models, 211

Optical Fiber Cables, 38accessories, 13models, 210

optical fiber cables. See cables

overview, 2

PPC

reading controller status, 107receiving routing table settings, 136

polled units, number, 144

polling cycle, definition, 142

polling node, 143setting, 143

power supply, backup, 18, 40cable connections, 42

precautionsapplications, xiii, 20general, xiihandling, 205operating environment, xiiireplacing the Unit, 205safety, xii

procedures, message service, 19

programmingPC programming examples, 100remote, 130

Programming Devices, 14, 131

RRAS functions, 4

RECV instruction, 85CS1-series PCs, 155CVM1 and CV-series PCs, 155data areas, 92message service, 84

response codes, 99, 118, 120CS1-series PCs, 99CV-series PCs, 99

routing tables, 132creating, 133editing, 135saving, 136setting, 133

examples, 136procedure, 134

transferring, 136

Ssafety precautions, xii

SEND instruction, 85CS1-series PCs, 153CVM1 and CV-series PCs, 153data areas, 92message service, 84

settingsnode addresses

CS1 Optical Units, 226CS1 Wired Units, 46CVM1 and CV Units, 49

polling nodes, 143settings after replacing Unit, 205unit numbers

CS1 Optical Units, 226CS1 Wired Units, 45CVM1 and CV Units, 48

specificationsbackup power supply, 18communications, 9data link, 55general, 9message service, 96

standard models, 209

startup procedures, 19

status area, 4troubleshooting, 171

stopping and starting, data linksusing Controller Link Support Software, 76using FINS commands, 76

synchronous operation, 150

system configuration, 7

T–Wtroubleshooting, 160

status area, 171using indicators, 160

unit numbers, settingCS1 Optical Units, 226CS1 Wired Units, 45CVM1 and CV Units, 48

wiring, Optical Controller Link Units, 38

235

Revision History

A manual revision code appears as a suffix to the catalog number on the front cover of the manual.

Cat. No. W370-E1-1

Revision code

The following table outlines the changes made to the manual during each revision. Page numbers refer to theprevious version.

Revision code Date Revised content

1 March 2000 Original production

OPERATION MANUAL - Omronomron.com.ru/dynamic/managers/manage_8/files/w370e11.pdf · OMRON products...

Documents

Transcript of OPERATION MANUAL - Omronomron.com.ru/dynamic/managers/manage_8/files/w370e11.pdf · OMRON products...