Sysmac Operation Manual
Cat. No. W383-E1-04
SYSMAC
3G8F7-CLK13-E (Optical Ring, H-PCF Cable)
3G8F7-CLK12-EV1 (Optical Ring, H-PCF Cable)
3G8F7-CLK53-E (Optical Ring, GI Cable)
3G8F7-CLK52-EV1 (Optical Ring, GI Cable)
3G8F7-CLK23-E (Twisted-pair Cable)
3G8F7-CLK21-EV1 (Twisted-pair Cable)
Controller Link Support Boards
for PCI Bus
OPERATION MANUAL
3G8F7-CLK13-E (Optical Ring, H-PCF Cable)
3G8F7-CLK12-EV1 (Optical Ring, H-PCF Cable)
3G8F7-CLK53-E (Optical Ring, GI Cable)
3G8F7-CLK52-EV1 (Optical Ring, GI Cable)
3G8F7-CLK23-E (Twisted-pair Cable)
3G8F7-CLK21-EV1 (Twisted-pair Cable)
Controller Link Support Boards for PCI Bus
Operation Manual
Revised September 2007
iv
Notice:
OMRON products are manufactured for use according to proper procedures by a qualified operator
and only for the purposes described in this manual.
The following conventions are used to indicate and classify precautions in this manual. Always heed
the information provided with them. Failure to heed precautions can result in injury to people or damage to property.
!DANGER
Indicates an imminently hazardous situation which, if not avoided, will result in death or
serious injury. Additionally, there may be severe property damage.
!WARNING
Indicates a potentially hazardous situation which, if not avoided, could result in death or
serious injury. Additionally, there may be severe property damage.
!Caution
Indicates a potentially hazardous situation which, if not avoided, may result in minor or
moderate injury, or property damage.
OMRON Product References
All OMRON products are capitalized in this manual. The word “Unit” is also capitalized when it refers to
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 anything
else.
Visual Aids
The following headings appear in the left column of the manual to help you locate different types of
information.
Note
Indicates information of particular interest for efficient and convenient operation of the product.
Reference
Indicates supplementary information on related topics that may be of interest to the user.
1,2,3...
1. Indicates lists of one sort or another, such as procedures, checklists, etc.
 OMRON, 2001
All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form, or
by any means, mechanical, electronic, photocopying, recording, or otherwise, without the prior written permission of
OMRON.
No patent liability is assumed with respect to the use of the information contained herein. Moreover, because OMRON is constantly striving to improve its high-quality products, the information contained in this manual is subject to change without
notice. Every precaution has been taken in the preparation of this manual. Nevertheless, OMRON assumes no responsibility
for errors or omissions. Neither is any liability assumed for damages resulting from the use of the information contained in
this publication.
v
vi
TABLE OF CONTENTS
PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xv
1
Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xvi
2
General Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xvi
3
Safety Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xvi
4
Operating Environment Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xvii
5
Application Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xviii
6
Conformance to EC Directives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xix
SECTION 1
Outline of Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1
1-1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2
1-2
Specifications and Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
1-3
Basic Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22
1-4
Applications Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23
SECTION 2
Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
29
2-1
Connecting Wired Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30
2-2
Connecting H-PCF Cable Optical Ring System Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . .
35
2-3
Optical Ring System (GI Cable) Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
41
2-4
Backup Power Supply Wiring (Optical Ring Systems Only) . . . . . . . . . . . . . . . . . . . . . . . .
46
SECTION 3
Creating Applications Using the C Library . . . . . . . . . . . . .
49
3-1
Basic Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
50
3-2
Using the C Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
52
SECTION 4
C Language Function Reference . . . . . . . . . . . . . . . . . . . . . .
55
4-1
Library Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
56
4-2
Structure Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
64
4-3
Detailed Error Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
69
SECTION 5
Data Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
71
5-1
What Are Data Links?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
72
5-2
Setting Data Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
77
5-3
Starting and Stopping Data Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
82
5-4
Checking Data Link Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
85
5-5
Changing the Data Link Tables with Active Data Links . . . . . . . . . . . . . . . . . . . . . . . . . . .
87
vii
TABLE OF CONTENTS
SECTION 6
Message Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
91
6-1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
92
6-2
FINS Command/Response Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
93
6-3
Commands and Responses for the Support Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
95
6-4
Response Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
109
SECTION 7
Network Interconnections . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
7-1
What is Network Interconnection? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
118
7-2
Routing Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
119
7-3
Setting Routing Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
121
SECTION 8
Communications Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
8-1
Network Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
126
8-2
Communications Cycle Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
128
8-3
Data Link I/O Response Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
133
8-4
Message Service Delay Times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
135
SECTION 9
Troubleshooting and Maintenance . . . . . . . . . . . . . . . . . . . . 137
9-1
Troubleshooting Using Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
138
9-2
Status Information and Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
143
9-3
Error Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
148
9-4
Cleaning and Inspection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
154
9-5
Handling Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
155
Appendix
A
Standard Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
157
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
viii
About this Manual:
This manual describes the operation of the 3G8F7-CLK13-E, 3G8F7-CLK12-EV1, 3G8F7-CLK53-E,
3G8F7-CLK52-EV1, 3G8F7-CLK23-E, and 3G8F7-CLK21-EV1 Controller Link Support Boards for PCI
Bus and includes the sections described below. Controller Link Support Boards are used to connect
IBM PC/AT or compatible computers to a Controller Link Network. The following three manuals are
directly related to application of the Controller Link Network.
Name
Contents
3G8F7-CLK13-E, 3G8F7-CLK12EV1, 3G8F7-CLK53-E, 3G8F7CLK52-EV1, 3G8F7-CLK23-E,
3G8F7-CLK21-EV1
Controller Link Support Boards for
PCI Bus
Operation Manual (this manual)
Operating procedures for Controller Link Support
Boards for PCI bus connections. Controller Link Support Boards are used to connect IBM PC/ATs or compatibles to a Controller Link Network.
3G8F7-CLK13-E, 3G8F7-CLK12EV1, 3G8F7-CLK53-E, 3G8F7CLK52-EV1, 3G8F7-CLK23-E,
3G8F7-CLK21-EV1
Controller Link Support Boards for
PCI Bus
Installation Guide
3G8F5-CLK11-E, 3G8F5-CLK21-E
Controller Link Support Boards for
ISA Bus
Operation Manual
W467
Installation and setup procedures for Controller Link
Support Boards for PCI bus connections. Controller
Link Support Boards are used to connect IBM PC/ATs
or compatibles to a Controller Link Network.
C200HW-ZW3AT2-E-V2
Controller Link Support Software
Operation Manual
CS1W-CLK23, CS1W-CLK21-V1,
CJ1W-CLK23, CJ1W-CLK21-V1,
C200HW-CLK21,CVM1-CLK21,
CQM1H-CLK21
Controller Link Units (Wired and
Optical) Operation Manual
CS1W-CLK13, CS1W-CLK12-V1,
CVM1-CLK12, CS1W-CLK53,
CS1W-CLK52-V1, CVM1-CLK52
Optical Ring Controller Link Units
Operation Manual
Cat. No.
(suffixes omitted)
W383
Installation, setup, and operating procedures for Con- W307
troller Link Support Boards for ISA bus connections.
Controller Link Support Boards are used to connect
IBM PC/ATs or compatibles to a Controller Link Network.
Installation and operating procedures for the Control- W369
ler Link Support Software. The Controller Link Support Software enables manually set data links and
other procedures for a Controller Link Network.
W309
Installation, setup, and operating procedures for the
Optical and Wired Controller Link Units. Controller
Link Units are used to connect C200HX/HG/HE, CVseries, and CS1-series PCs to a Controller Link Network.
W370
Installation, setup, and operating procedures for the
Optical Ring Controller Link Units. Controller Link
Units are used to connect C200HX/HG/HE CV-series,
and CS1-series PCs to a Controller Link Network.
ix
About this Manual, Continued
Depending on the system, you may also need the SYSMAC or CV Support Software or a Programming Console. Please read this manual and related manuals carefully and be sure you understand the
information provided before attempting to install and operate a Controller Link Support Board.
Section 1 outlines the functions of the Controller Link Support Board, including applications, and the
differences between the Controller Link Support Board and the Controller Link Unit.
Section 2 describes how to wire the power supply cables and communications cables to the Controller
Link Support Board.
Section 3 describes creating applications (user programs) that control the Controller Link Support
Board.
Section 4 details the C-language library functions supported by the Controller Link Support Board.
Section 5 describes how to use data links in a Controller Link Network.
Section 6 explains how to use the message service provided by a Controller Link Support Board.
Section 7 describes the method used to connect multiple networks.
Section 8 explains details on Controller Link Network communications. Refer to this section for network communications that require accurate communications timing.
Section 9 provides information on troubleshooting errors that occur during Controller Link Support
Board operation, as well as daily inspection, cleaning, and other maintenance procedures.
The Appendix provides a list of standard models.
!WARNING Failure to read and understand the information provided in this manual may result in personal injury or death, damage to the product, or product failure. Please read each section
in its entirety and be sure you understand the information provided in the section and
related sections before attempting any of the procedures or operations given.
x
Read and Understand this Manual
Please read and understand this manual before using the product. Please consult your OMRON
representative if you have any questions or comments.
Warranty and Limitations of Liability
WARRANTY
OMRON's exclusive warranty is that the products are free from defects in materials and workmanship for a
period of one year (or other period if specified) from date of sale by OMRON.
OMRON MAKES NO WARRANTY OR REPRESENTATION, EXPRESS OR IMPLIED, REGARDING NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR PARTICULAR PURPOSE OF THE
PRODUCTS. ANY BUYER OR USER ACKNOWLEDGES THAT THE BUYER OR USER ALONE HAS
DETERMINED THAT THE PRODUCTS WILL SUITABLY MEET THE REQUIREMENTS OF THEIR
INTENDED USE. OMRON DISCLAIMS ALL OTHER WARRANTIES, EXPRESS OR IMPLIED.
LIMITATIONS OF LIABILITY
OMRON SHALL NOT BE RESPONSIBLE FOR SPECIAL, INDIRECT, OR CONSEQUENTIAL DAMAGES,
LOSS OF PROFITS OR COMMERCIAL LOSS IN ANY WAY CONNECTED WITH THE PRODUCTS,
WHETHER SUCH CLAIM IS BASED ON CONTRACT, WARRANTY, NEGLIGENCE, OR STRICT
LIABILITY.
In no event shall the responsibility of OMRON for any act exceed the individual price of the product on which
liability is asserted.
IN NO EVENT SHALL OMRON BE RESPONSIBLE FOR WARRANTY, REPAIR, OR OTHER CLAIMS
REGARDING THE PRODUCTS UNLESS OMRON'S ANALYSIS CONFIRMS THAT THE PRODUCTS
WERE PROPERLY HANDLED, STORED, INSTALLED, AND MAINTAINED AND NOT SUBJECT TO
CONTAMINATION, ABUSE, MISUSE, OR INAPPROPRIATE MODIFICATION OR REPAIR.
xi
Application Considerations
SUITABILITY FOR USE
OMRON shall not be responsible for conformity with any standards, codes, or regulations that apply to the
combination of products in the customer's application or use of the products.
At the customer's request, OMRON will provide applicable third party certification documents identifying
ratings and limitations of use that apply to the products. This information by itself is not sufficient for a
complete determination of the suitability of the products in combination with the end product, machine,
system, or other application or use.
The following are some examples of applications for which particular attention must be given. This is not
intended to be an exhaustive list of all possible uses of the products, nor is it intended to imply that the uses
listed may be suitable for the products:
• Outdoor use, uses involving potential chemical contamination or electrical interference, or conditions or
uses not described in this manual.
• Nuclear energy control systems, combustion systems, railroad systems, aviation systems, medical
equipment, amusement machines, vehicles, safety equipment, and installations subject to separate
industry or government regulations.
• Systems, machines, and equipment that could present a risk to life or property.
Please know and observe all prohibitions of use applicable to the products.
NEVER USE THE PRODUCTS FOR AN APPLICATION INVOLVING SERIOUS RISK TO LIFE OR
PROPERTY WITHOUT ENSURING THAT THE SYSTEM AS A WHOLE HAS BEEN DESIGNED TO
ADDRESS THE RISKS, AND THAT THE OMRON PRODUCTS ARE PROPERLY RATED AND INSTALLED
FOR THE INTENDED USE WITHIN THE OVERALL EQUIPMENT OR SYSTEM.
PROGRAMMABLE PRODUCTS
OMRON shall not be responsible for the user's programming of a programmable product, or any
consequence thereof.
xii
Disclaimers
CHANGE IN SPECIFICATIONS
Product specifications and accessories may be changed at any time based on improvements and other
reasons.
It is our practice to change model numbers when published ratings or features are changed, or when
significant construction changes are made. However, some specifications of the products may be changed
without any notice. When in doubt, special model numbers may be assigned to fix or establish key
specifications for your application on your request. Please consult with your OMRON representative at any
time to confirm actual specifications of purchased products.
DIMENSIONS AND WEIGHTS
Dimensions and weights are nominal and are not to be used for manufacturing purposes, even when
tolerances are shown.
PERFORMANCE DATA
Performance data given in this manual is provided as a guide for the user in determining suitability and does
not constitute a warranty. It may represent the result of OMRON's test conditions, and the users must
correlate it to actual application requirements. Actual performance is subject to the OMRON Warranty and
Limitations of Liability.
ERRORS AND OMISSIONS
The information in this manual has been carefully checked and is believed to be accurate; however, no
responsibility is assumed for clerical, typographical, or proofreading errors, or omissions.
xiii
xiv
PRECAUTIONS
This section provides general precautions for using the Controller Link Support Board for PCI Bus and related devices.
The information contained in this section is important for the safe and reliable application of the Controller
Link Support Board for PCI Bus. You must read this section and understand the information contained before
attempting to set up or operate a Controller Link Support Board for PCI Bus.
1
Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xvi
2
General Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xvi
3
Safety Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xvi
4
Operating Environment Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xvii
5
Application Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xviii
6
Conformance to EC Directives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xix
6-1
Applicable Directives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xix
6-2
Applicable Directives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xix
6-3
Applicable Directives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xx
xv
1
Intended Audience
1
Intended Audience
This manual is intended for the following personnel, who must also have
knowledge 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 Precautions
The user must operate the product according to the performance specifications described in the operation manuals.
Before using the product under conditions which are not described in the
manual or applying the product to nuclear control systems, railroad systems,
aviation systems, vehicles, combustion systems, medical equipment, amusement machines, safety equipment, and other systems, machines, and equipment that may have a serious influence on lives and property if used
improperly, consult your OMRON representative.
Make sure that the ratings and performance characteristics of the product are
sufficient for the systems, machines, and equipment, and be sure to provide
the systems, machines, and equipment with double safety mechanisms.
This manual provides information for programming and operating the Controller Link Support Board for PCI Bus and related devices. Be sure to read this
manual before attempting to use the software and keep this manual close at
hand for reference during operation.
!WARNING It is extremely important that a Controller Link Support Board for PCI Bus and
all related devices be used for the specified purpose and under the specified
conditions, especially in applications that can directly or indirectly affect
human life. You must consult with your OMRON representative before applying a Controller Link Support Board for PCI Bus to the above mentioned applications.
3
Safety Precautions
!WARNING Never attempt to disassemble any Controller Link Support Board for PCI Bus
while power is being supplied. Doing so may result in serious electrical shock
or electrocution.
!WARNING Never touch any of the terminals while power is being supplied. Doing so may
result in serious electrical shock or electrocution.
!WARNING Provide safety measures in external circuits, i.e., not in the Programmable
Controller (CPU Unit including associated Units; referred to as “PC”), in order
to ensure safety in the system if an abnormality occurs due to malfunction of
the PC or another external factor affecting the PC operation. Not doing so may
result in serious accidents.
• Emergency stop circuits, interlock circuits, limit circuits, and similar safety
measures must be provided in external control circuits.
• The PC will turn OFF all outputs when its self-diagnosis function detects
any error or when a severe failure alarm (FALS) instruction is executed.
xvi
Operating Environment Precautions
4
As a countermeasure for such errors, external safety measures must be
provided to ensure safety in the system.
• The PC outputs may remain ON or OFF due to deposition or burning of
the output relays or destruction of the output transistors. As a countermeasure for such problems, external safety measures must be provided
to ensure safety in the system.
• When the 24-VDC output (service power supply to the PC) is overloaded
or short-circuited, the voltage may drop and result in the outputs being
turned OFF. As a countermeasure for such problems, external safety
measures must be provided to ensure safety in the system.
!Caution Execute online edit only after confirming that no adverse effects will be
caused by extending the cycle time. Otherwise, the input signals may not be
readable.
!Caution Confirm safety at the destination node before transferring a program to
another node or changing contents of the I/O memory area. Doing either of
these without confirming safety may result in injury.
!Caution Tighten the connector screws for the backup power supply to the torque specified in this manual. The loose screws may result in burning or malfunction.
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
in the specifications.
• Locations subject to condensation as the result of severe changes in temperature.
• 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
the following 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 Controller Link Support Board for PCI Bus
or the computer can have a large effect on the longevity and reliability of the
system. Improper operating environments can lead to malfunction, failure, and
other unforeseeable problems with the Controller Link Support Board for PCI
Bus or the computer. Be sure that the operating environment is within the
specified conditions at installation and remains within the specified conditions
during the life of the system.
xvii
5
Application Precautions
5
Application Precautions
Observe the following precautions when using the Controller Link Support
Board for PCI Bus or the computer into which it is installed.
Note Refer also to 1-4 Applications Precautions for further information and additional precautions.
!WARNING Failure to abide by the following precautions could lead to serious or possibly
fatal injury. Always heed these precautions.
• Always ground the system to 100 Ω or less when installing the system to
protect against electrical shock.
• Always turn OFF the power of the computer before attempting any of the
following. Performing any of the following with the power supply turned on
may lead to electrical shock:
• Installing or removing the Support Board.
• Assembling the Units.
• Setting DIP switches or short-circuiting pins.
• Connecting or disconnecting any cables or connectors.
!Caution Failure to abide by the following precautions could lead to faulty operation of
the computer or the system or could damage the Controller Link Support
Board for PCI Bus or related devices. Always heed these precautions.
• Fail-safe measures must be taken by the customer to ensure safety in the
event of incorrect, missing, or abnormal signals caused by broken signal
lines, momentary power interruptions, or other causes.
• Always use the power supply voltage specified in the operation manuals.
An incorrect voltage may result in malfunction or burning.
• Take appropriate measures to ensure that the specified power with the
rated voltage and frequency is supplied. Be particularly careful in places
where the power supply is unstable. An incorrect power supply may result
in malfunction.
• Install external breakers and take other safety measures against short-circuiting in external wiring. Insufficient safety measures against short-circuiting may result in burning.
• Disconnect the functional ground terminal when performing withstand
voltage tests. Not disconnecting the functional ground terminal may result
in burning.
• Do not attempt to take the Boards apart, to repair the Boards, or to modify
the Boards in any way.
• Be sure that all the mounting screws, terminal screws, and cable connector screws are tightened to the torque specified in this manual. Incorrect
tightening torque may result in malfunction.
• Use crimp terminals for wiring. Do not connect bare stranded wires
directly to terminals. Connection of bare stranded wires may result in
burning.
• Double-check all the wiring before turning ON the power supply. Incorrect
wiring may result in burning.
• Wire correctly.
• Double-check all the connectors before mounting the Board.
xviii
6
Conformance to EC Directives
• Be sure that the communications cable connectors and other items with
locking devices are properly locked into place. Improper locking may
result in malfunction.
• Use a special packing box when transporting the Board. Handle the product carefully so that no excessive vibration or impact is applied to the
product during transportation.
• Check the user program for proper execution before actually running it on
the Unit. Not checking the program may result in an unexpected operation.
• Observe the following precautions when wiring the communications cable
or backup power supply cables.
• Separate the cables from 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
in order to discharge any static built-up. Not doing so may result in malfunction or damage.
• Do not touch the Board surfaces or parts.
• Install the Board according to instructions in the operation manuals.
Improper installation may cause faulty operation.
• When using the Optical Ring Controller Link Support Board for public utilities systems, such as electricity, gas, or water supply, use the Optical
Ring mode and provide appropriate fail-safe measures.
6
6-1
Conformance to EC Directives
Applicable Directives
• EMC Directives
6-2
Applicable Directives
EMC Directives
OMRON devices that comply with EC Directives also conform to the related
EMC standards so that they can be more easily built into other devices or
machines. The actual products have been checked for conformity to EMC
standards (see the following note). Whether the products conform to the standards in the system used by the customer, however, must be checked by the
customer.
EMC-related performance of the OMRON devices that comply with EC Directives will vary depending on the configuration, wiring, and other conditions of
the equipment or control panel in which the OMRON devices are installed.
The customer must, therefore, perform final checks to confirm that devices
and the overall machine conform to EMC standards.
Note Applicable EMC (Electromagnetic Compatibility) standards are as follows:
EMS (Electromagnetic Susceptibility):
EMI (Electromagnetic Interference):
EN61000-6-2
EN61000-6-4
xix
Conformance to EC Directives
6-3
6
Applicable Directives
The 3G8F7-CLK13-E, 3G8F7-CLK12-EV1, 3G8F7-CLK53-E, 3G8F7-CLK52EV1, 3G8F7-CLK23-E, and 3G8F7-CLK21-EV1 Controller Link Support
Boards comply with EC Directives. To ensure that the machine or device in
which any of these Controller Link Support Boards is used complies with EC
directives, the Board must be installed as follows:
1,2,3...
1. Reinforced insulation or double insulation must be used for the DC power
supplies used for the communications and I/O power supplies.
2. Controller Link Support Boards complying with EC Directives also conform
to the Common Emission Standard (EN61000-6-4). Particularly for the 10m radiated emission, the structure of the control panel, relations to other
connected devices, and wiring can affect compliance of the overall system.
The customer must, therefore, perform final checks to confirm that devices
and the overall machine conform to EC standards even when individual devices conform.
3. For the Controller Link Support Boards, the backup power supply that is
used may affect compliance for surge immunity (IEC61000-4-5) even
though common immunity (EN61000-6-2) standards for EMS are met. Either use the recommended OMRON Power Supply (S82K Series) or take
countermeasures for surge on the primary side.
xx
SECTION 1
Outline of Functions
This section outlines the functions of the Controller Link Support Board, including the applications of the Controller
Link Support Board and the differences between the Controller Link Support Board and the Controller Link Unit.
1-1
1-2
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2
1-1-1
What Is the Controller Link? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2
1-1-2
Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4
1-1-3
What Is a Controller Link Support Board? . . . . . . . . . . . . . . . . . . .
10
1-1-4
Features of PCI Bus Controller Link Support Boards . . . . . . . . . . .
11
1-1-5
Outline of PCI Bus Controller Link Support Board Functions . . . .
11
Specifications and Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
1-2-1
System Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
1-2-2
PCI Bus Controller Link Support Board Models. . . . . . . . . . . . . . .
15
1-2-3
Communications Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . .
16
1-2-4
General Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18
1-2-5
Dimensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18
1-2-6
Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
20
1-2-7
Product Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
20
1-2-8
Software Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
1-2-9
Applicable Computers, Operating Systems, and Libraries . . . . . . .
21
1-3
Basic Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22
1-4
Applications Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23
1
Section 1-1
Overview
1-1
1-1-1
Overview
What Is the Controller Link?
The Controller Link is an FA network that can send and receive large data
packets flexibly and easily among advanced OMRON Programmable Controllers (CS-series, CJ-series, C200HX/HG/HE-series, CQM1H-series, CVM1,
and CV-series PCs) and IBM PC/AT or compatible computers.
The Controller Link supports data links that enable data sharing and a message service that enables sending and receiving data when required. Data
link areas can be freely set to create a flexible data link system and effectively
use data areas.
The network is connected using either shielded twisted-pair cable or optical
fiber cable, and high-volume data transmissions at high speed enable construction of a wide range of networks, from low-level systems to high.
Wired System
(Twisted-pair Cable)
Wired Systems are supported by CS-series, CJ-series, C200HX/HG/HE,
CQM1H-series CVM1, and CV-series PCs.
CVM1-CLK21
CQM1H-CLK21
CS1W-CLK21
C200HW-CLK21
Controller Link Unit Controller Link Unit Controller Link Unit Controller Link Unit
CQM1Hseries PC
CS-series
PC
C200HX/HG/
HE PC
IBM PC/AT or
compatible
CVM1 or
CV-series PC
Twisted-pair cable
Optical Bus or Optical
Ring System
(H-PCF Cable)
IBM PC/AT or
compatible
3G8F5-CLK21-E
Controller Link
ISA Support Board
3G8F7-CLK21-EV1
Controller Link
PCI Support Board
Optical Systems are supported by CS-series, CVM1, and CV-series PCs.
Token Ring Mode
CS1W-CLK12
Controller Link Unit
(Token Ring Mode)
CVM1-CLK12
Controller Link Unit
(Token Ring Mode)
CVM1 or
CV-series
PC
CS-series PC
IBM PC/AT or
compatible
H-PCF Optical Fiber Cable
(ring connection)
Backup power
supply (24 VDC)
3G8F7-CLK12-EV1
Controller Link
PCI Support Board
(Token Ring Mode)
CS-series PC
CS1W-CLK12
Controller Link Unit
(Token Ring Mode)
2
CVM1 or
CV-series
PC
CVM1-CLK12
Controller Link Unit
(Token Ring Mode)
Section 1-1
Overview
Tokenbus Mode
CS1W-CLK12
Controller Link Unit
(Token-bus mode)
CS1W-CLK11
Controller Link Unit
H-PCF Optical Fiber Cable
(daisy-chain connection)
IBM PC/AT or
compatible
3G8F5-CLK11
Controller Link
ISA Support Board
Backup power
supply (24 VDC)
Optical Bus or Optical
Ring System (GI Cable)
IBM PC/AT or
compatible
CVM1 or
CV-series
PC
CS-series PC
CS-series PC
CVM1-CLK12
Controller Link Unit
(Token-bus mode)
3G8F7-CLK12-EV1
Controller Link
PCI Support Board
(Token bus mode)
Optical Systems are supported by CS-series, CJ-series, CVM1, and CVseries PCs.
Token Ring Mode
CS1W-CLK52
Controller Link Unit
(Token Ring Mode)
CVM1-CLK52
Controller Link Unit
(Token Ring Mode)
CVM1 or
CV-series
IBM PC/AT or
PC
compatible
CS-series PC
GI Optical Fiber Cable
(ring connection)
Backup power
supply (24 VDC)
3G8F7-CLK52-EV1
Controller Link
PCI Support Board
(Token Ring Mode)
CVM1 or
CV-series
PC
CVM1-CLK52
Controller Link Unit
(Token Ring Mode)
CS-series PC
CS1W-CLK52
Controller Link Unit
(Token Ring Mode)
Token-bus Mode
CS1W-CLK52
Controller Link Unit
(Token-bus mode)
CS-series PC
Backup power
supply (24 VDC)
CS1W-CLK52
Controller Link Unit
(Token-bus mode)
CS-series PC
CVM1-CLK52
Controller Link Unit
(Token-bus mode)
IBM PC/AT or
compatible
CVM1 or
CV-series PC
GI Optical Fiber Cable
(daisy-chain connection)
3G8F7-CLK52-EV1
Controller Link
PCI Support Board
(Token bus mode)
3
Section 1-1
Overview
The functions of a Controller Link Network are outlined below.
Controller Link
Data link
Manual settings
Automatic settings
Message service
RAS functions
Error log function
Data link status display
Polling node backup
Node bypass function
(See note 1.)
Transmission path
duplication
(See note 2.)
Disconnect detection and
(See note 2.)
notification
Node connection
configuration data reading (See note 2.)
Note
1-1-2
1. Optical Systems and Optical Ring Systems only.
2. Only for Optical Ring Systems in Token
Ring Mode.
Features
The Controller Link FA Network has the following features to meet the various
requirements of FA sites.
Data Links
Flexible and efficient data links can be created for large capacities of data as
listed below.
Item
Number of Send areas
data link
per node
words
CS or CJ Series
C200HX/HG/HE,
CVM1/CV, CQM1H
Computers
Data link
CS or CJ Series
areas (send
and receive)
that can be
created per
node
C200HX/HG/HE,
CVM1/CV, or CQM1H
Computers
4
Specifications
CS1W-CLK23 or CJ1W-CLK23:
4,000 words max.
CS1W-CLK21-EV1 or CJ1W-CLK21-EV1:
1,000 words max.
1,000 words max.
3G8F7-CLK23-E: 4,000 words max.
3G8F7-CLK21-EV1, 3G8F5-CLK21-E1:
1,000 words max.
CS1W-CLK23 or CJ1W-CLK23:
20,000 words max.
CS1W-CLK21-EV1 or CJ1W-CLK21-EV1:
20,000 words max. (unit version 1.2 or later)
12,000 words max. (Pre-Ver. 1.2)
8,000 words max.
32,000 or 62,000 words max. (See note 2.)
Section 1-1
Overview
Note
The following models must be used to create a wired network that contains
more than 32 nodes: 3G8F7-CLK23-E, 3G8F7-CLK21-EV1, CS1W-CLK23,
CS1W-CLK21-V1, CJ1W-CLK23, and CJ1W-CLK21-V1.
Data links can be automatic set, or they can be set by the user to freely
change the sizes of the data areas used. A data link can also receive only part
of the data sent from another node. This function enables users to receive
only the required data, thereby increasing data link efficiency.
Message Service
The message service can send and receive up to 2,012 bytes of data (including the FINS header), allowing high volumes of data to be sent and received
without having to split it up.
Twisted-pair Cable or Optical Fiber Cable Connection
The Controller Link Units can be connected to the network using either
shielded twisted-pair cables, optical fiber cables, or optical ring optical fiber
cables. The optical ring optical fiber cables can be either H-PCF cables or GI
cables. Select the system that suits the application.
Features of Twisted-pair Cable
Twisted-pair cable is easy to connect and maintain. The cable can be processed much more easily than coaxial or optical cable, thereby reducing the
cost of tools and assembly time.
Connections are made to a terminal block on the Controller Link Unit and to a
special connector on the computer board for easy system assembly and modification.
The network is equipped with the required terminating resistance built into the
Units allowing the terminating resistance to be easily set at both ends of the
network using a simple switch.
Features of Optical and Optical Ring Systems
Optical fiber cable (H-PCF cable or GI cable) has superior noise resistance,
so the system can provide highly reliable communications even in very noisy
conditions.
With H-PCF cable, the total communications distance can be up to 20 km
(1 km max. between nodes using adhesive polishing). With GI cable, the communications distance can be up to 30 km (2 km max. between nodes using
62.5/125 µm cable), which allows long-distance and large-scale networks.
Once the optical fiber cable has been fitted with special connectors, the
cables can be easily connected or disconnected.
Communications between Different PCs
The following Controller Link Units are available for communications between
different PCs. Wired Units and Optical Units, however, cannot be used
together in the same Controller Link Network. (Optical and Optical Ring Units
can exist in one Controller Link Network using H-PCF cables, but with GI
cables, on an Optical Ring Unit is available.)
Wired System
• Controller Link Unit for CS-series Programmable Controllers
• Controller Link Unit for CJ-series Programmable Controllers
• Controller Link Units for C200HX/HG/HE Programmable Controllers
• Controller Link Units for CV-series Programmable Controllers
• ISA Bus Controller Link Support Board for IBM PC/AT or compatibles
5
Section 1-1
Overview
• PCI Bus Controller Link Support Board
Optical Ring System with H-PCF Cables
• Controller Link Unit for CS-series Programmable Controllers
• Controller Link Unit for CVM1/CV-series Programmable Controllers
• PCI Bus Controller Link Support Board
Optical Ring System with GI Cables
• CS-series and CJ-series Programmable Controllers
• CVM1/CV-series Programmable Controllers
• PCI Bus Boards
Optical System with H-PCF Cables
• Controller Link Unit for CS-series and CJ-series Programmable Controllers
• ISA Bus Controller Link Support Board for IBM PC/AT or compatibles
Flexible Internetwork Connections
The Controller Link Network can be connected to another network (Ethernet,
SYSMAC NET Link, SYSMAC LINK, or another Controller Link network)
through a CS-series or CV-series PC. By installing Ethernet, SYSMAC NET
Link, or SYSMAC LINK, or Controller Link Communications Units on the same
CS1-series PC or CV-series PC, a message service can be created with
nodes in the interconnected networks through that PC. Up to three network
levels are possible.
Improved Error Handling (RAS Functions)
Error Log and Data Link
Status Display
An error log enables quick handling of errors by recording the time the error
occurred and error details. The current Controller Link Unit and Support
Board status are also available, as are the data link and network status.
Polling Node Backup
When an error occurs in the polling node that controls the Controller Link Network, another node automatically becomes the polling node. This prevents an
error at a single node from influencing other nodes on the network, achieving
a highly reliable system.
Node Bypass Function
In an Optical or Optical Ring Controller Link Network, data communications
can be continued by bypassing the node, even when a node in the communications line malfunctions or the PC or computer power supply is turned OFF.
This prevents the whole network system from being affected by a node malfunction or power interruption.
To use the bypass node function, backup power must be supplied to the Controller Link Unit/Support Board.
Optical transmission path
Bypass
CLK
CLK
CLK
PC
PC
PC
CLK
Power interruption
IBM PC/AT or
compatible
24-VDC
Backup Power Supply
6
Section 1-1
Overview
Transmission Path
Duplication
In Token Ring Mode in an Optical Ring System (H-PCF cable or GI cable),
data transmission will be unaffected even by a cable or connector break at
one location in the ring connection. With the optical cable wired in a ring
shape, a break at one point will simply cause the transmission to be routed on
the other path.
Disconnect Detection and
Notification
Even with transmission path duplication, the network will be broken if disconnections occur in two or more places. In Token Ring Mode in an Optical Ring
System (H-PCF cable or GI cable), the location of a disconnection can be
detected and identified by means of the node status information given for all
nodes. This function can be used to prevent system crashes in advance, e.g.,
by performing maintenance when a disconnection occurs at one location.
Node Connection
Configuration Data
Reading
In Token Ring Mode in an Optical Ring System (H-PCF cable or GI cable),
connection data can be read for all of the nodes in the network. The information that can be read includes the order in which the nodes are connected and
which of two optical connectors is connected to which node. Special support
software (Controller Link Support Software, Ver. 2.00 or later) is required to
read the node connection configuration data.
Using Repeater Units for T-Branches, Network Extensions, Network Expansions,
Converting Network Sections to Optical Fiber, and Device Modularization
T-Branches enable greater wiring freedom during layout, restructuring, and expansion of
networks.
Wire-to-Wire Repeater Units enable Controller Link T-Branches. T-Branches
provide the following advantages:
• Cabling can conform to the layout of equipment.
• It is possible to add nodes by adding or inserting Repeater Units at
branch points of an existing wired Controller Link system.
• If Repeater Units are installed at likely future branch points in the network
in advance, new nodes can be added by simply connecting them to these
Repeater Units.
The total length of wired networks can be extended.
At a baud rate of 2 Mbps, conventional wired networks can be up to 500 m
long. By using two Repeater Units, this can be extended to a maximum of
1.5 km.
The maximum number of nodes can be extended to 62 for wired networks.
By combining version-1 Controller Link Units/Support Boards and a Repeater
Unit, it is possible to construct networks containing up to 62 nodes.
Improved noise resistance through the use of optical cabling.
By installing two Wire-to-Optical Repeater Units, optical cabling can be used
for sections of the network that are the source of noise.
Devices can be modularized.
• Devices can be modularized according to Repeater Units, making wiring
easier when adding, removing, or modifying devices.
• When starting up devices, components can be added to the network and
debugged as they are completed.
Refer to the Controller Link Unit Operation Manual (W309) for information on
using Repeater Units.
7
Section 1-1
Overview
Features and Functions of Version-1 and CLK23 Models
The following features and functions apply to the CS1W-CLK23, CS1WCLK21-V1, CJ1W-CLK23, and CJ1W-CLK21-V1 Controller Link Units and the
3G8F7-CLK23-E and 3G8F7-CLK21-EV1 Controller Link Support Board only.
Up to 62 nodes can be connected.
Overview
When a CS1W-RPT01 Repeater Unit is used, the maximum number of nodes
that can be used in the network increases to 62. (The previous limit was 32.)
Method
Use Repeater Units and select Max Node Number set 62 in the FinsGateway
drive settings to enable a maximum of 62 nodes.
Restrictions
• The maximum of 62 nodes cannot be achieved if pre-version-1 models
are used together in the same network with version-1 models or with
CLK23 models (i.e., the CS1W-CLK23, CJ1W-CLK23, or 3G8F7-CLK23E).
• Using the maximum 62 nodes can be enabled using FinsGateway 2003.
This setting is not possible with FinsGateway version [email protected]@.
Automatic data link creation is possible with 1:N allocations.
Overview
It is possible to perform unequal 1:N allocations of data between nodes with
automatic data link creation. This makes it easy to perform data links that formerly required the user to manually edit data link parameters.
The following four automatic data link creation patterns can be used:
• Equality layout (the previous pattern)
• 1:N allocation, common type
• 1:N allocation, 1 to 1 type
• 1:N allocation, chain type
This setting can be made in CS-series or CJ-series Controller Link Units.
Method
Allocation addresses and sizes are all specified using the Automatic Data Link
Creation Parameters (D30000 × Unit No. + 12 to 20) in the DM Parameter
Area. These values can be set using the CX-Net in the CX-Programmer version 3.2 or later.
Objective
This function is effective in applications that collect data from slave PCs into a
master PC.
Restrictions
• A Controller Link Support Board cannot be set as the startup node.
• These settings can be made using FinsGateway 2003. They are not possible with FinsGateway version [email protected]@.
Automatic data link creation with 1:N allocations cannot be performed if preversion-1 models are used together in the same network with version-1 models or with CLK23 models (i.e., the CS1W-CLK23, CJ1W-CLK23, or 3G8F7CLK23-E).
8
Section 1-1
Overview
Change manually created data link tables during data link operation.
Overview
It is possible to modify a manually created data link table while data links are
running.
Note
This is possible only with manually created data link tables. Any attempt to
change automatically created data link tables when data links are running will
fail and an error message saying that the tables cannot be edited during data
link operation will be displayed.
Method
This function can be set using the CX-Net in CX-Programmer version 3.2 or
later.
Objectives
• In systems that operate non-stop and cannot be turned OFF, this function
makes it possible to change the data link table to accommodate the addition of new nodes and to transfer data link tables without having to stop
manually set data link communications.
• If this function is combined with the use of Repeater Units to add network
nodes, it becomes possible to construct systems of greater flexibility.
Operation
When a node is being modified online, this function temporarily stops refreshing of data link data until modifications have been completed.
Nodes will participate in data links after changes to the data link table have
been completed.
Note
Refer to the Controller Link Unit Operation Manual (W309) for information on
changing user-set data link tables while the data links are active.
Overview of 3G8F7-CLK23-E, 3G8F7-CLK13-E, and 3G8F7-CLK53-E Features and Functions
The 3G8F7-CLK23-E, 3G8F7-CLK13-E, and 3G8F7-CLK53-E are upwardly
compatible from the 3G8F7-CLK21-EV1, 3G8F7-CLK12-EV1, and 3G8F7CLK52-EV1, respectively.
The following data link functions have been added to the features and functions of the 3G8F7-CLK21-EV1, 3G8F7-CLK12-EV1, and 3G8F7-CLK52EV1.
All other functions and performance are the same as for the 3G8F7-CLK21EV1, 3G8F7-CLK12-EV1, and 3G8F7-CLK52-EV1.
Model number
3G8F7-CLK21-EV1,
3G8F7-CLK12-EV1, or
3G8F7-CLK52-EV1
3G8F7-CLK23-E,
3G8F7-CLK13-E, or
3G8F7-CLK53-E
Number of send
1,000 words max.
words per node (total
of area 1 and area 2)
4,000 words max.
Number of error log
records
64 max.
39 max.
When configuring a system using data links in which the number of send
words per node exceeds 1,000 words, all Controller Link Units and Support
Boards must be the [email protected], [email protected], or [email protected]
When using other Controller Link Units or Support Boards together in the
same network, use a maximum of 1,000 send words per node.
9
Section 1-1
Overview
Units and Support Boards Supporting Up to 4,000 Send Words Per Node
Wired Networks
Model
CS1W-CLK23 (CS-series Unit)
CJ1W-CLK23 (CJ-series Unit)
3G8F7-CLK23-E (Support Board for PCI Bus)
Units
Support Board
Optical Networks
Model
Units
Support Board
1-1-3
CS1W-CLK13 (CS-series Unit, H-PCF Cable)
CS1W-CLK53 (CJ-series Unit, GI Cable)
3G8F7-CLK13-E (Support Board for PCI Bus, H-PCF Cable)
3G8F7-CLK53-E (Support Board for PCI Bus, GI Cable)
What Is a Controller Link Support Board?
A Controller Link Support Board is used to directly connect an IBM PC/AT or
compatible with an ICA or PCI bus to a Controller Link Network. A Controller
Link Support Board supports data links, a message service, and RAS functions in the same way as a Controller Link Unit.
The Support Board is mounted in an expansion slot in the computer. The following Support Boards are available depending on the type of connection
cable.
Wired System
IBM PC/AT or
compatible
3G8F7-CLK21-EV1 (for PCI Bus) or
3G8F5-CLK21-E (for ISA Bus)
Controller Link Support Board
Controller Link Unit
PC
Controller Link Network
Optical System/Optical Ring System (H-PCF Cable)
IBM PC/AT or
compatible
3G8F7-CLK12-EV1 (for PCI Bus) or
3G8F5-CLK11-E (for ISA Bus)
Controller Link Support Board
Controller Link Unit
PC
Optical System/Optical Ring System (H-PCF Cable) Controller Link Network
10
Section 1-1
Overview
Optical Ring System (GI Cable)
IBM PC/AT or
compatible
3G8F7-CLK52-EV1 (for PCI Bus)
Controller Link Support Board
(ISA Bus is not available.)
Controller Link Unit
PC
Optical Ring System (GI Cable) Controller Link Network
1-1-4
Features of PCI Bus Controller Link Support Boards
The Controller Link Support Board for PCI Bus can be used to configure various communications applications using FinsGateway Controller Link (PCI).
User application
C Library
PLC Reporter 32,
DataFlowNavi for Access,
AIMAX-FA, etc.
Compolet
FinsGateway Controller Link (PCI)
PCI Bus Controller Link Support Board
The Board is equipped with the FinsGateway Controller Link (PCI) and C
Library (Win32 DLL) as standard features. With the Board, user applications
can be created using the C language (Microsoft Visual C++ .NET 2003,
Microsoft Visual C++ Ver. 6.0). An overview of how to use the C Library is
described later in this manual.
SYSMAC Compolet Version 2 provides ActiveX controls for PC communications. User applications can be created more easily using Microsoft Visual
Basic. PLC Reporter 32, DataFlowNavi for Access, and AIMAX-FA are software packages of communications middleware. These software packages
must be purchased separately. For details, refer to the manual for the appropriate software.
1-1-5
Outline of PCI Bus Controller Link Support Board Functions
Data Links
Controller Link Support Board data link data is stored in the event memory in
the computer. Event memory is shared memory with names such as DM or
CIO, and is stored in the computer memory. Event memory recreates virtually
the DM Area and CIO Area of a PC.
Event memory can be written or read by executing the C Library data link data
read/write functions ClkWriteDatalink( ) and ClkRead Datalink( ) from the user
program.
11
Section 1-1
Overview
Computer
User application
ClkWriteDatalink( )
CIO
ClkReadDatalink( )
DM
Event
memory
FinsGateway
Data link
Controller Link Support Board
PC
Controller Link Network
Message Service
FINS commands and FINS responses can be sent and received for specified
nodes on the network by executing FINS message send/receive functions
ClkSendFins( ) and ClkRecvFins( ) from the user program.
Computer
User application
ClkSendFins( )
ClkRecvFins( )
FinsGateway
Controller Link (PCI) Embedded Edition
Controller Link Support Board
PC
Controller Link Network
A maximum of 4 PCI Bus Controller Link Support Boards can be mounted to
one computer. Consequently, multiple user applications can be executed
simultaneously.
12
Section 1-2
Specifications and Configurations
Computer
User application
User application
FinsGateway
Controller Link (PCI) Embedded Edition
Controller Link
Support Board
Controller Link
Support Board
PC
Controller Link Network
1-2
1-2-1
Specifications and Configurations
System Configuration
Wired System
(Twisted-pair Cable)
CS1W-CLK21-V1
Controller Link Unit
CS-series
PC
Wired Systems are supported by CS-series, CJ-series, C200HX/HG/HE,
CVM1, and CV-series PCs.
CJ1W-CLK21-V1
Controller Link Unit
C
P
U
CVM1-CLK21
Controller Link Unit
CVM1, CV-series
PC
C200HX/HG/HE
PC
CJ-series PC
C
P
U
C200HW-CLK21
Controller Link Unit
C
P
U
Twisted-pair cable
CQM1H-CLK21
Controller Link Unit
IBM PC/AT or
compatible
CQM1H-series
PC
C
P
U
C
P
U
3G8F7-CLK21-EV1
Controller Link
Support Board
13
Section 1-2
Specifications and Configurations
Optical Bus or Optical
Ring System
(H-PCF Cable)
Optical Systems are supported by CS-series, CVM1, and CV-series PCs.
Token Ring Mode
CS1W-CLK12-V1
Controller Link Unit
(token ring mode)
CS-series PC
CVM1-CLK12
Controller Link Unit
(token ring mode)
CVM1/CV-series PC
C
P
U
C
P
U
Personal computer
H-PCF Optical fiber cable
(ring connection)
Backup
power supply
(24 VDC)
C
P
U
3G8F7-CLK12-EV1
Controller Link Support Board
for PCI Bus (token ring mode)
C
P
U
CS-series PC
CVM1/CV-series PC
CS1W-CLK12-V1
Controller Link Unit
(token ring mode)
CVM1-CLK12
Controller Link Unit
(token ring mode)
Token-bus Mode
CS1W-CLK12-V1
Controller Link Unit
(token bus mode)
CS-series PC
14
Personal
computer
PC/AT or
compatible
Personal computer
CVM1/CV-series
PC
CS-series PC
C
P
U
Backup
power supply
(24 V DC)
CS1W-CLK11
Controller Link Unit
CVM1-CLK12
Controller Link Unit
(token bus mode)
C
P
U
H-PCF Optical
fiber cable
(daisy chain
connection)
C
P
U
3G8F5-CLK11
Controller Link
Support Board for
ISA Bus
3G8F7-CLK12-EV1
Controller Link
Support Board
for PCI Bus
(token bus mode)
Section 1-2
Specifications and Configurations
Optical Bus or Optical
Ring System (GI Cable)
Optical Systems are supported by CS-series, CVM1, and CV-series PCs.
Token Ring Mode
CS1W-CLK52-V1
Controller Link Unit
(token ring mode)
CVM1-CLK52
Controller Link Unit
(token ring mode)
CS-series PC
CVM1/CV-series PC
C
P
U
C
P
U
Personal computer
GI Optical fiber cable
(ring connection)
Backup
power supply
(24 VDC)
C
P
U
3G8F7-CLK52-EV1
Controller Link
Support Board
for PCI Bus
(token ring mode)
C
P
U
CS-series PC
CVM1/CV-series PC
CS1W-CLK52-V1
Controller Link Unit
(token ring mode)
CVM1-CLK52
Controller Link Unit
(token ring mode)
Token-bus Mode
CS1W-CLK52-V1
Controller Link Unit
(token bus mode)
CS-series PC
Note
1-2-2
CVM1-CLK52-V1
Controller Link Unit
(token bus mode)
Personal computer
CVM1/CV-series
PC
CS-series PC
C
P
U
Backup
power supply
(24 VDC)
CS1W-CLK52-V1
Controller Link Unit
(token bus mode)
C
P
U
C
P
U
3G8F7-CLK52-EV1
Controller Link
Support Board
for PCI Bus
(token bus mode)
GI Optical fiber cable
(daisy chain
connection)
A maximum of 4 PCI Bus Controller Link Support Boards can be mounted.
(Different types of system can be mounted simultaneously.) PCI Bus Controller Link Support Boards can also be used with ISA Bus Controller Link Support Boards. If PCI Bus and ISA Bus Controller Link Support Boards are used
together, however, a separate ISA Bus FinsGateway Controller Link Driver is
required.
PCI Bus Controller Link Support Board Models
System
H-PCF cable optical ring
GI cable optical ring
Twisted-pair Cable
Product
Controller Link Support
Board for PCI Bus
Model
3G8F7-CLK13-E
3G8F7-CLK12-EV1
3G8F7-CLK53-E
3G8F7-CLK52-EV1
3G8F7-CLK23-E
3G8F7-CLK21-EV1
15
Section 1-2
Specifications and Configurations
1-2-3
Communications Specifications
Optical Ring System (Joint Ring/Daisy Chain Connections)
Items
Specifications
Optical ring, GI cable
Type
Optical ring, H-PCF cable
Model
3G8F7-CLK13-E
3G8F7-CLK12-EV1
Communications method
N:N token-ring method (Token Ring Mode)
N:N token-bus method (token-bus mode)
Code
Modulation
Manchester code
Baseband code
Synchronization
Transmission path format
Flag synchronization (conforms to HDLC frames)
Ring method (Token Ring Mode)
Daisy-chain method (token-bus mode)
Transmission speed
Maximum transmission distance
Maximum distance
between nodes
Medium
2 Mbps
20 km
3G8F7-CLK53-E
3G8F7-CLK52-EV1
30 km
62.5/125 µm: 2 km
50/125 µm: 1 km
GI cable (optical two-core cable, 62.5/
125 µm or 50/125 µm)
Node connection method
Connected via a special (full-lock connector) Connected via ST connectors.
connector. (A half-lock connector can also be
used.)
Maximum number of nodes 62 nodes (See notes 2 and 3.)
Communications functions
Number of data link words
Data link areas
Message length
RAS functions
Error control
Crimp cut: 800 m
Adhesive: 1 km (See note 1.)
H-PCF cable (optical two-core cable)
Data links and message service
Transmission area per node:
3G8F7-CLK13-E and 3G8F7-CLK53-E: 4,000 words max.
3G8F7-CLK12-EV1 and 3G8F7-CLK52-EV1: 1,000 words max.
Number of data link words that can be used in one network (total transmission):
62,000 words max. (See note 3.)
FinsGateway Event Memory
2,012 bytes max. (including the header)
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.)
Manchester code check
CRC check (CCITT X16 + X12 + X5 + 1)
Note
1. The maximum distance between nodes depends on the connector and cable processing methods.
2. With the token-bus method, the maximum number of nodes in an Optical
Bus System with optical bus nodes (i.e., model numbers ending in CLK11)
is 32 (node addresses 1 to 32).
3. The maximum number of words in an Optical System with optical bus
nodes (i.e., model numbers ending in CLK11) is 32,000 words.
16
Section 1-2
Specifications and Configurations
Wired System
Items
Specifications
Type
Wired
Model
Communications method
3G8F7-CLK23-E
3G8F7-CLK21-EV1
N:N token bus
Code
Modulation
Manchester code
Baseband code
Synchronization
Transmission path form
Flag synchronization (conforms to HDLC frames)
Multi-drop bus
Baud rate and maximum
transmission distance
The maximum transmission distance varies with the baud rate as follows:
2 Mbps:
500 m
1 Mbps:
800 m
500 Kbps: 1 km
Specified shielded twisted-pair cable
Number of signal lines: 2, shield line: 1
Connect with provided connector
Media
Node connection method
Maximum number of nodes 32 nodes or 62 nodes
Communications functions Data links and message service
Number of data link words
Data link areas
Message length
RAS functions
Error control
Transmission area per node: 3G8F7-CLK23-E:
4,000 words max.
3G8F7-CLK21-EV1: 1,000 words max.
Number of data link words in one network (send/receive: 32,000 words max., but 62,000
words max. if the maximum of 62 nodes is used)
FinsGateway event memory
2,012 bytes max. (including the header)
Polling node backup function
Self-diagnosis function (hardware checking at startup)
Inter-node test and broadcast test (using the FINS command)
Watchdog timer
Error log function
Manchester code check
CRC check (CCITT X16 + X12 + X5 + 1)
Note
At least one Repeater Unit is required to construct networks that uses a node
address higher than 32. The following Controller Link Units/Support Boards
must also be used, and the Wired Network 62 Node Enable Bit of the DM
Parameter Area software switch of all nodes must be turned ON (62 nodes
max.).
CS1W-CLK23, CS1W-CLK21-V1, CJ1W-CLK23, CJ1W-CLK21-V1,
3G8F7-CLK23-E, and 3G8F7-CLK21-EV1
17
Section 1-2
Specifications and Configurations
1-2-4
General Specifications
Items
Controller Link Support Board for PCI Bus
Wired system:
3G8F7-CLK23-E
3G8F7-CLK21-EV1
Optical system,
H-PCF cable:
3G8F7-CLK13-E
3G8F7-CLK12-EV1
Optical system,
GI cable:
3G8F7-CLK53-E
3G8F7-CLK52-EV1
External dimensions
106 × 140 mm (W × L)
Weight
104 g
120 g (excluding mounting
bracket)
124 g (excluding mounting
bracket)
Current consumption
0.35 A max. at 5 VDC
Without power supply:
0.54 A max. at 5 VDC
With power supply:
0.35 A max. at 5 VDC
Without power supply:
0.60 A max. at 5 VDC
With power supply:
0.35 A max. at 5 VDC
Installation environment
conditions
Same as for computer.
1-2-5
Dimensions
Wired Models (3G8F7-CLK23-E and 3G8F7-CLK21-EV1)
(Unit: mm)
18
Section 1-2
Specifications and Configurations
GI Cable Optical Ring Models
(3G8F7-CLK53-E and 3G8F7-CLK52-EV1)
H-PCF Cable Optical Ring Models
(3G8F7-CLK13-E and 3G8F7-CLK12-EV1)
155 (163)
155 (163)
(Unit: mm)
Note The dimensions given in parentheses are for when the previous connector is
mounted.
19
Section 1-2
Specifications and Configurations
1-2-6
Indicators
Optical Ring System
(H-PCF Cable and GI Cable)
RUN
ERR
Name
Operating
Error
Wired System
Color
Green
Status
Lit
Explanation
The Board is operating normally.
Red
Not lit
Lit
Not lit
A Board operating error (watchdog timer error) has occurred.
One of the following errors has occurred.
Communications error
Node address setting error (duplicate setting)
Optical system connection error
EEPROM error
Hardware error
Data link table error
Routing table error
Network parameter error
Operating normally (no errors in the setting tables).
INS
Participating in Yellow
network
Lit
Not lit
Participating in network.
Not participating in network.
LNK
Sending data
link
Lit
Flashing
Sending data link (participating in data link)
Error in the data link table settings.
Not lit
Lit
Data link is stopped or Unit is not participating in data link.
Backup power supply is ON.
Not lit
Lit
Backup power supply is OFF.
Terminating resistance switch is ON (resistance is connected).
Not lit
Terminating resistance switch is OFF (resistance is not connected).
Yellow
PS (See
note 1.)
Power supply
ON
Green
TER
(See
note 2.)
Terminating
Yellow
resistance setting
Note
1. The P/S indicator is mounted to the Optical Ring Units only.
2. The TER indicator is mounted to the Wired Units only.
1-2-7
Product Components
System
Wired system
Model
3G8F7-CLK23-E
3G8F7-CLK21-EV1
Contents
Controller Link Support Board × 1
CD-ROM × 1
Installation guide × 1
Communications connector × 1
Board ID switch number/indicator label × 1
User registration card (software license agreement) × 1
Optical ring system,
H-PCF cable
Optical ring system,
GI cable
3G8F7-CLK13-E
3G8F7-CLK12-EV1
3G8F7-CLK53-E
3G8F7-CLK52-EV1
Controller Link Support Board × 1
CD-ROM × 1
Installation guide × 1
Optical cable bracket × 1
Power supply connector × 1
Board ID switch number/indicator label × 1
User registration card (software license agreement) × 1
Note
1. The following software is supplied on the CD-ROM.
• FinsGateway Version 2003 (PCI-CLK Edition)
• FinsGateway Version 3 (PCI-CLK Edition)
20
Section 1-2
Specifications and Configurations
• Setup Diagnostic Utility
• C Library
2. The DOS operating system for an IBM PC/AT or compatible is not provided
with the Support Board. The operation system must be acquired separately.
1-2-8
Software Configuration
User application
Software
FinsGateway
utilities
C Library
FinsGateWay
Hardware
Note
1-2-9
Controller Link Support Board
A CLK data link setting utility is included in the FinsGateway utilities. Make the
data link table settings for the Board using this utility. For details, refer to FinsGateway online help.
Applicable Computers, Operating Systems, and Libraries
The following table lists the operating environment for Controller Link Support
Boards for PCI Bus connections.
Compatible computers
FinsGateway
version
IBM PC/AT or compatible
FinsGateway
• CPU: Intel Celeron 400 MHz or better Version 2003
• Main memory: 128 MB minimum
• 1 or more PCI bus slots (PCI bus revision 2.0 or later, power supply: 5 V)
• Free hard disk space: 70 MB min.
(not including user applications)
• CD-ROM drive:
One required for software installation
• Display: VGA (640 × 480 (pixels) min.)
(Other conditions conform to the OS.)
Note
Compatible OS
Compatible language
• Windows XP Professional
Microsoft Visual C++ Ver. 6.0
• Windows XP Home Edition (Service Pack 3)
• Windows 2000 Professional Microsoft Visual C++ .NET
2003
(When using the C language
library provided in the CDROM with the product)
1. There are two versions for FinsGateway (Version 2003 and Version 3) provided on the CD-ROM that comes with the product. The applicable OS depends on the version of FinsGateway.
2. When using Windows NT 4.0 (service pack 3 or later), Windows ME, or
Windows 98SE, install FinsGateway Version 3. Using version 3 of the
FinsGateway, however, with disable the following functions supported by
version-1 Controller Link Support Boards for PCI Bus: Automatic 1:N data
link allocations, changing data link tables while data links are active, and
using 62 wired nodes. Maximum number of data link send words per node:
4,000
21
Section 1-3
Basic Procedures
3. Use FinsGateway Version 2003.21 or higher to use up to 4,000 data link
send words per node. (The version of FinsGateway that is installed can be
confirmed by starting the FinsGateway Settings program and checking the
product information provided on the Info Tab Page.)
FinsGateway version
FinsGateway Version
2003
FinsGateway Version 3
Automatic allocation
Setting 62 wired
of 1:N data link
nodes
tables
Supported.
Supported.
Changing data link
tables with active
data links
Supported.
Maximum number of
data link send words
per node: 4,000
Supported.
(FinsGateway Version
2003.21 or higher)
Not supported.
Not supported.
Not supported.
Not supported.
4. A Controller Link Support Board cannot be used with Windows 95 or Windows NT 3.51 or earlier.
5. Controller Link Support Boards for PCI Bus connection may not operate
correctly when used with other computers or operating systems. Always
use the Controller Link Support Board with a personal computer and OS
that satisfy the above conditions.
6. Controller Link Support Boards conform to PCI Local Bus Specifications,
Revision 2.0.
7. User applications can also be written with Microsoft Visual Basic Version
6.0 if the optional SYSMAC Compolet Version 2 is purchased.
8. User applications can also be written with Microsoft Visual Basic .NET or
Microsoft Visual Basic .NET 2003 if the optional SYSMAC Compolet Version 2003 is purchased. SYSMAC Compolet Version 2003 can be used
only with FinsGateway 2003. Microsoft .NET framework 1.0 or 1.1 is required to use SYSMAC Compolet Version 2003. Refer to the operation
manual for SYSMAC Compolet Version 2003 for details.
1-3
Basic Procedures
Initial Procedure
Refer to the Controller Link Support Board Installation Guide for information
on the first three steps in the following procedure.
1,2,3...
1. Set the Board ID on the Board switch.
2. Install the Board into the computer.
3. Install the software.
4. Wire and connect the cables.
5. Perform the following data link and/or message service procedure.
Data Link Procedure
1,2,3...
1. Create data link tables using the Controller Link Support Software or the
FinsGateway utilities, and transfer the data to the Board.
Note
When the data link tables and routing tables are transferred to the
Controller Link Support Board, they are saved in backup memory
(EEPROM) on the Board. It is not necessary to set the data again
when the power is turned OFF and ON.
2. Read and write to the data link area using the utility applications that use
the C Library.
Note
22
The data links can also be started by sending the data link activation command of the FINS message service, or by using a PC software switch operation.
Section 1-4
Applications Precautions
Message Service
Procedure
1,2,3...
1. Create routing tables using the Controller Link Support Software or the
FinsGateway utilities, and transfer the tables to the Board.
Note
When the data link tables and routing tables are transferred to the
Controller Link Support Board, they are save in backup memory
(EEPROM) on the Board. It is not necessary to set the data again
when the power is turned OFF and ON.
2. Send and receive FINS messages using the utility applications that use the
C Library.
1-4
Applications Precautions
Board ID Switch
If more than one Controller Link Support Board is mounted to a computer,
make sure that the same Board IDs is not set for more than one Board. Up to
4 Boards can be mounted.
Note Refer to the Controller Link Support Board Installation Guide
(W467).
Terminating Resistance
Switch (Wired Systems
Only)
Turn ON the terminating resistance switch only for the nodes at both ends of a
wired Controller Link Network and turn OFF the switch for all other nodes.
Note Refer to the Controller Link Support Board Installation Guide
(W467).
Cables
Turn OFF the power of all the nodes on the network before connecting or disconnecting a cable.
Note Refer to SECTION 2 Wiring.
Use the specified cable only.
Note Refer to 1-2 Specifications and Configurations.
Baud Rates (Wired
Systems Only)
Set the same baud rate for all nodes on the same network.
Note Refer to the Controller Link Support Board Installation Guide
(W467).
Routing Tables
When a CV-series PC is connected to the network, set routing tables at all the
nodes.
Note
Routing tables are not required if all the CV-series CPU Units in the Controller
Link Network have been manufactured on or after May 1996. The manufacturing date can be determined from the four-digit lot number on the side of the
CPU Unit.
Lot No.: @
@ 5
6....
Manufactured in May 1996
Indicates the last digit of the manufacturing
year. 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 is
May.
Set routing tables at all the nodes in all the networks when multiple networks
are connected to one PC.
Note Refer to SECTION 7 Network Interconnections.
When a routing table is transferred (written) to a PC, all CPU Bus and Communications Units are reset. The routing tables must not be transferred to a
PC while the system is running.
Data Links
When using a manually set data link, delete the data link tables from all nodes
not participating in the data link.
23
Section 1-4
Applications Precautions
The polling node must not be restarted or reset during data link operation.
If the Controller Link Support Board is the polling node and data links are
operating on the network, do not open the Board for three seconds after closing the Board.
If the Controller Link Support Board is the polling node and data links are
operating on the network, do not add the Board to the network for three seconds after leaving the network.
Precautions when
Connecting Nodes Using
a Repeater Unit
When data links are active in the existing network, check the following items
before adding nodes to the network. If the inappropriate data link tables or
parameters are set, the system may not operate properly.
• If the new node will participate in user-set data links, make sure that the
appropriate data link tables are set in the corresponding nodes.
• If the new node will not participate in user-set data links, make sure that
the data link tables of the corresponding nodes are deleted.
• If automatic settings are used, make sure that the appropriate DM Area
parameters have been set.
Before adding nodes, check user programming for the existing network to
confirm that the new data transmissions created by adding new nodes can be
performed. If the ladder program is not suitable, the system may not operate
properly.
Make sure that the node addresses of the new nodes are not already being
used by other nodes in the same network. If the same node address is used
by more than one node, a node duplication error will be detected when the
node is added, communications will stop, and the node with the same address
will not be able to the join the network. Data may also be unexpectedly
received from the incorrectly set node. To restore a Controller Link System
with a duplicated address, reset the node address correctly, then turn ON the
power to the corresponding PCs again, or restart the Controller Link Support
Boards and Units.
Always set the baud rate of the new nodes and the Repeater Unit to the same
baud rate used for the existing network. If a different baud rate is set when
adding a new node, the communications for the whole network including the
existing network will be unstable and communications errors will occur.
Set the terminating resistance of the new nodes to the Repeater Unit as
shown in the following diagram. If terminating resistance is set incorrectly,
communications errors may occur.
• Adding Nodes Using T-branch Lines
System Configuration after Adding Nodes
Terminating
resistance ON
Terminating
resistance ON
Terminating
resistance ON
CS1W-RPT01
Repeater Unit
Newly added nodes
Turn ON terminating resistance at the
nodes on both ends of each segment
shown within broken lines.
24
Terminating
resistance ON
Section 1-4
Applications Precautions
• Adding Nodes with a Repeater Unit at One End
Terminating
resistance ON
Terminating
resistance ON
Terminating
resistance ON
CS1W-RPT01
Repeater Unit
Turn ON terminating resistance at
the nodes on both ends of each
segment shown within broken lines.
Newly added nodes
Terminating
resistance ON
Before connecting the new nodes to the existing network, always set the polling/polled node setting in the Controller Link Support Board driver properties
to Polled. If the nodes are connected to the existing network with this setting
set to Polling, the corresponding node may become the polling node for the
network, which will affect the network in the following ways. After the new
nodes are participating in the network normally, return the polling/polled node
setting to polling node.
• When the data link startup switch of the new node is OFF, all the data
links for the whole network including the existing network will be inactive.
• When the network parameters being used are different from the default
values, the network parameters will return to the default values.
After confirming that the new node has properly joined the network, set the
polling/polled node setting in the Controller Link Support Board driver properties to Polling.
Always set the Max Node Number set 62 option in the Controller Link Support
Board driver properties of the new node to match the settings of the existing
network. If different settings are used, the network may not be configured correctly.
When a new node is to be added to a system that is already wired over a long
distance using T-branch lines or Repeater Units, turn OFF the power to the
PCs in the segment where the node is to be added. The power to the PCs in
segments separated by Repeater Units does not need to be turned OFF.
Refer to the Controller Link Unit Operation Manual (W309).
Systems with an Existing T-branch Line
The power to the PCs of the segment
shown within the dot-dash broken
line does not need to be turned OFF.
CS1W-RPT01
Repeater Unit
The power to the PCs in the
segment shown within the dash
broken line must be turned OFF.
New node to be added
25
Section 1-4
Applications Precautions
Systems Wired with an Existing Repeater Unit
New node to be added
The power to the PCs of the segment
shown in the dot-dash broken line
does not need to be turned OFF.
The power to the PCs in the
segment shown in the dash broken
line must be turned OFF.
CS1W-RPT01
Repeater Unit
Others Precautions
Observe the following precautions.
• The Controller Link Support Board can be used only with the specified
OS.
Note
Refer to 1-2 Specifications and Configurations.
• Set the IRQ (interrupt request) of the Controller Link Support Board so
that it does not overlap with other resources.
Note
Refer to the Controller Link Support Board Installation Guide
(W467).
• If using the SEND, RECV, and CMND instructions with a PC on which the
routing tables have been set, be sure to specify the network address set
in the routing tables.
• If using an Optical Ring System, the same type of transmission path must
be set for all nodes. If the transmission path node settings are different,
the network will not be configured correctly.
• Wired Systems cannot be used together with Optical or Optical Ring Systems.
• If using Optical System Units (model numbers ending in CLK11) and HPCF Cable Optical Ring System models (model numbers ending in
CLK12, CLK12-EV1, or CLK13-E) together, observe the following precautions.
• The transmission paths for the H-PCF Cable Optical Ring System
Units must be set to Token Bus Mode for all nodes. If the transmission
path settings are different, the network will not be configured correctly.
• Set node addresses from 1 to 32 for all nodes.
• Set the polling node/polled node software switches for all the Optical
Ring System Units for the polled node. If an optical ring node is the
polling node when the network is started, the maximum node address
in the network parameters will be set to 62, and the Network Parameter Error (ERH) indicators on the Optical System Units will light.
• GI Cable Optical Ring System Units (model numbers ending 3G8F7CLK53-E, and 3G8F7-CLK52-EV1) cannot be used together with Optical
System Units (model numbers ending CLK11) or H-PCF Cable Optical
Ring System Units (model numbers ending 3G8F7-CLK13-E, and 3G8F7CLK12-EV1).
• If using ring wiring, connect the nodes in node address order (i.e., node 1,
node 2.... node 62, node 1) as much as possible to reduce the effect on
communication time if a wire breaks. For details on communications time,
refer to 8-2 Communications Cycle Time.
26
Section 1-4
Applications Precautions
• To construct a network that uses a node address higher than 32, it is necessary for all nodes to be one of the following Units: 3G8F7-CLK21-EV1,
CS1W-CLK23, CJ1W-CLK23, CS1W-CLK21-V1, CJ1W-CLK21-V1, or
3G8F7-CLK23-E.
In addition, the Wired Network 62 Node Enable Bit in the DM Parameter
Area software switches of all nodes must turned ON to enable 62 nodes
maximum. With the 3G8F7-CLK23-E and 3G8F7-CLK21-EV1, make sure
that Max Node Number set 62 is selected in the FinsGateway driver properties. If different settings are specified, the network will not be correctly
configured.
• The Max Node Number set 62 DM Parameter Area software switch for the
CS1W-CLK23-E, CS1W-CLK 21-EV1, CJ1W-CLK23-E, and CJ1W-CLK
21-EV1 Units is enabled when the power is turned ON again.
• When using automatic data link creation with 1:N allocation, all nodes
must be following Units/Boards. Other models cannot participate in data
links that employ 1:N allocations.
Wired Networks
CS1W-CLK23, CJ1W-CLK23, 3G8F7-CLK23-E,
CS1W-CLK21-V1, CJ1W-CLK21-V1, and 3G8F7-CLK21-EV1
Optical Ring Networks CS1W-CLK13, 3G8F7-CLK13-E,
using H-PCF Cable
CS1W-CLK12-V1 (See note.), and 3G8F7-CLK12-EV1
Optical Ring Networks CS1W-CLK53, 3G8F7-CLK53-E,
using GI Cable
CS1W-CLK52-V1 (See note.), and 3G8F7-CLK52-EV1
Note Lot numbers 030601 or later.
• If the total number of data link words is increased, the PLC cycle time and
the communications cycle time will be increased. In that case, observe
the following precautions.
• Check to make sure that it will not cause problems if performance in
responses to external devices is reduced.
• In message communications, extending the communications cycle
time may result in timeout errors waiting for responses.
In that case, lengthen the response monitor time as described below.
SEND, RECV, and CMND instructions:
Response monitor time setting area for local node control data.
For details, refer to 6-1 Introduction.
PLC Programming Devices:
PLC Programming Device Response Timeout setting
For details on settings, refer to the operation manual for the PLC
Programming Device that is being used.
27
Applications Precautions
Section 1-4
Example: CX-Programmer Response Timeout Setting
28
SECTION 2
Wiring
This section describes how to wire the power supply cables and communications cables to the Controller Link Support
Board.
2-1
2-2
2-3
2-4
Connecting Wired Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30
2-1-1
Devices Required for Connection . . . . . . . . . . . . . . . . . . . . . . . . . .
30
2-1-2
Communications Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30
2-1-3
Connecting Cables to Communications Connectors . . . . . . . . . . . .
31
2-1-4
Connecting the Connector to the Board . . . . . . . . . . . . . . . . . . . . . .
34
Connecting H-PCF Cable Optical Ring System Cables. . . . . . . . . . . . . . . . .
35
2-2-1
Communications Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
35
2-2-2
Optical Fiber Cables (H-PCF Cables) . . . . . . . . . . . . . . . . . . . . . . .
37
2-2-3
Installing Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
38
Optical Ring System (GI Cable) Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . .
41
2-3-1
Communications Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
41
2-3-2
GI Optical Fiber Cable Wiring. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
42
2-3-3
Installing Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
43
Backup Power Supply Wiring (Optical Ring Systems Only). . . . . . . . . . . . .
46
2-4-1
Backup Power Supply Specifications . . . . . . . . . . . . . . . . . . . . . . .
46
2-4-2
Connecting the Backup Power Supply. . . . . . . . . . . . . . . . . . . . . . .
47
29
Section 2-1
Connecting Wired Systems
2-1
Connecting Wired Systems
This section describes the methods for wiring network communications cables
to the Controller Link Support Board (3G8F7-CLK23-E and 3G8F7-CLK21EV1).
2-1-1
Devices Required for Connection
The Wired Controller Link System uses the shielded twisted-pair cable specified below.
Model
ESVC 0.5X2C-13262
ESNC 0.5X2C-99-087B
Note
Manufacturer
Bando Densen Co.
Nihon Electric Wire & Cable Co.
1. Be sure to use the communications cable described above.
2. If another communications cable is used, normal operation cannot be assured.
3. For manufacturers of the specified cable, refer to the appendix, Standard
Models.
2-1-2
Communications Cable
Wire the communications cable to connect identical signals.
Note
1. Use the cable specified for the communications cable.
2. Keep communications cable separated from power lines or a high-tension
lines to prevent influences from electronic noise.
3. Ground the shield line of the communications cable at one end of the network. Do not ground the shield at both ends.
4. Do not connect the shield cable of the communications cable to a ground
that is also being used for power-system devices, such as inverters.
5. Turn ON the terminating resistance switch at the nodes at both ends of the
network to connect terminating resistance. Turn OFF the terminating resistance switch at all nodes.
6. Do not run wiring outdoors. If outdoor wiring is necessary, take protection
measures against lightning, such as underground wiring or wiring inside
pipes.
7. The minimum length of the communications cable between nodes is 1 m.
Prepare the communications cables at a length of 1 m or more.
8. Use the multidrop method for connecting nodes. Normal communications
will not be possible with T branches.
9. Terminals for the same signal on the connector are connected internally in
the Controller Link Support Board.
Shield
Shield
BD L BD L
BD H
10. Although this section discusses wiring Controller Link Support Boards
only, a Controller Link Unit could take the place of any Board and can be
connected in the same fashion as a Board.
30
Section 2-1
Connecting Wired Systems
11. The ground wire connected to the connector of a Controller Link Support
Board must be 2.5 mm2 or less.
Connect all the shield lines of the communication cables and then ground the
shield at one end of the network. The wiring method is shown below.
Intermediate Board
End Board
Terminating
resistance ON
End Board
Terminating
resistance OFF
Terminating
resistance ON
Ground
Note
The terminals of the same type are connected internally. Connections can
thus be made to either the right or left half of the end Boards.
End Board
Refer to the Controller Link Unit Operation Manual (W309) for information on
wiring Repeater Units.
2-1-3
Connecting Cables to Communications Connectors
When connecting a communications cable to a Controller Link Support Board,
connect the cable to the attached connector first and then attach to the connector on the Board. Connect the communications cable to the connector
using the following procedure.
1,2,3...
1. Peel back the cover of the cable for about 50 mm without scratching the
mesh of the shield. Do not peel too much because it may cause a shortcircuit.
Approx. 50 mm
2. Twist the mesh of the shield to form a line on the end on which the shield
is to connected to a node.
3. Apply a heat-shrink tubing to the twisted shield line, leaving enough bare
wire to attach the crimp terminal.
31
Section 2-1
Connecting Wired Systems
Wire created by
twisting the shield
Cover with a
heat-shrink tubing
Leave enough exposed
wire to attach the terminal.
Note (a) Turn OFF the power supply to the computer before connecting the
communications cable or connecting/disconnecting a connector.
(b) Use the connector attached to a Controller Link Support Board.
4. Strip the insulation far enough to attach the crimp terminals and twist the
wire strands tight.
5. Apply electrical tape or heat-shrink tubing to the end of the cable cover that
was peeled in step 1
Apply vinyl tape or
a heat-shrink tubing.
6. Attach the crimp terminals to the shield wire and signal wires. Apply electrical tape or heat-shrink tubing to the connections.
Note
We recommend the Phoenix AI-series crimp terminals shown in the
following diagram. The Phoenix Company’s ZA3 crimping tool can
be used to attach these terminals.
Crimp terminal
Cable
7. Carefully insert the signal line and shield line into each hole of the connector. Insert as marked on the connector. The following example shows connection to a Board in the middle of the Network.
32
Section 2-1
Connecting Wired Systems
BD H
S
S
BD L
Shield lines
Note (a) Loosen the screws in the connector enough to allow the terminal
to pass before inserting the signal line. If the screw is not loosened, the signal line will go completely into the connector and you
will not be able to secure the line.
(b) Attach crimp terminals to the wires. Never connect a bare power
supply wire directly into the connector.
(c) Marks are provided on the connector for the signal lines. Connect
the signal lines according to the marks. The marks correspond to
signal lines as listed below.
Marking
Signal name
Line color
■
@
BD H (communication data high side)
BD L (communication data low side)
Black
White
S
SHLD (shield)
---
(d) The lines can be connected to either the right or left half of the
connector at the node at either end of the network.
(e) The shield wire connections are different if grounding each node
individually. Refer to 2-1-2 Communications Cable to connect the
shield wire to the connector.
8. Firmly secure each signal line with the signal line screw on the connector.
An ordinary flat-blade screwdriver with a tip that tapers at the end is not
suitable because it cannot be inserted far enough. Use a small flat-blade
screwdriver with a constant width. The appropriate tightening torque is 0.2
N·m.
Small flat-blade
screwdriver with a
constant width
S
S
Note
The following screwdriver is available from OMRON.
Model: XW4Z-00C
33
Section 2-1
Connecting Wired Systems
2-1-4
Side
Front
0.6 mm
3.5 mm
Connecting the Connector to the Board
Connect the connector on the communications cable to the connector on the
Board using the following procedure.
1,2,3...
1. Connect the connector on the communications cable to the connector on
the Board as shown below.
S
S
2. Secure the connector to the Board by tightening the screws on the connector. The appropriate tightening torque is 0.2 N·m.
Note
1. If the connector is disconnected, communications for the Board that was
disconnected with other nodes in the network will be disabled and the network will be split into two at point of disconnection. Utmost care is necessary to prevent disconnection of a connector during communications.
Controller Link Support Board
Communications disabled
Connector
Network split
(communications disabled).
2. Do not pull on a communication cable.
3. When bending a communications cable, allow 60 mm or more for the bending radius (R).
4. Do not place heavy objects on the communications cable.
34
Section 2-2
Connecting H-PCF Cable Optical Ring System Cables
5. Supply power only after checking the wiring thoroughly.
2-2
Connecting H-PCF Cable Optical Ring System Cables
This section describes how to connect the communications cable to the Controller Link Support Board (3G8F7-CLK13-E and 3G8F7-CLK12-EV1) for HPCF Cable Optical Ring Systems.
2-2-1
Communications Cables
Optical Bus or Optical
Ring System (H-PCF
Cable)
The 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
used for Optical SYSMAC LINK Networks.
Optical Fiber Cables (Indoor Use Only)
Use the following Optical Fiber Cables (Hard Plastic-clad Fiber: H-PCF).
Name
H-PCF cables
Specifications
Black
Orange
Note
Model
10 m
50 m
S3200-HCCB101
S3200-HCCB501
100 m
500 m
S3200-HCCB102
S3200-HCCB502
1,000 m
10 m
S3200-HCCB103
S3200-HCCO101
50 m
100 m
S3200-HCCO501
S3200-HCCO102
500 m
1,000 m
S3200-HCCO502
S3200-HCCO103
The Optical Fiber Cable model numbers are as follows:
[email protected]@@@@@@
Tensioner option
None: Standard (with tension member)
N:
Without tension member
Cable length
@@@
A B
(A/10) x 10B m
Cable color
B: Black
O: Orange
Cable specification
L: With power supply line
C: Without power supply line
Type
B: Cord
C: Cable
Name
Connector
Model
S3200-COCF2071
S3200-COCF2571
Inline Adapter
S3200-COIAT2000
Specifications
Use to connect a cable to a node.
(Full-lock connector for crimp-cut cable.)
Use to connect a cable to a node.
(Half-lock connector for crimp-cut cable.)
Use to connect or extend cables.
(Use one adapter for each connection.)
35
Section 2-2
Connecting H-PCF Cable Optical Ring System Cables
Note
1. Either full-lock or half-lock connectors can be used in a Controller Link Network, but we recommend full-lock connectors to prevent accidental disconnections during operation.
2. The maximum distance between nodes is slightly shorter for connectors
with crimp-cut cables compared to connectors assembled with adhesive.
Also, the maximum distance is reduced due to extension loss when Inline
Adapters are used to extend cables.
No Longer Manufactured
Name
Connector
Model
S3200-COCF2011
Replacement model
S3200-COCF2071
S3200-COCF2511
S3200-COCF2571
Optical Fiber Cables with Connectors (Indoor Use Only)
The following Optical Fiber Cables are available with Connectors (lap/polished
type) already attached.
Specifications
Optical Fiber Cable Connectors:
S3200-COCF2011
⇓
S3200-COCF2011
Optical Fiber Cable Connectors:
S3200-COCF2011
⇓
S3200-COCF2511
Optical Fiber Cable Connectors:
S3200-COCF2511
⇓
S3200-COCF2511
Note
Length
2m
Model
S3200-CN201-20-20
5m
10 m
S3200-CN501-20-20
S3200-CN102-20-20
15 m
20 m
S3200-CN152-20-20
S3200-CN202-20-20
Over 20 m
S3200-CN-20-20
(Specify length (m) when ordering.)
2m
5m
S3200-CN201-20-25
S3200-CN501-20-25
10 m
15 m
S3200-CN102-20-25
S3200-CN152-20-25
20 m
Over 20 m
2m
S3200-CN202-20-25
S3200-CN-20-25
(Specify length (m) when ordering.)
S3200-CN201-25-25
5m
10 m
S3200-CN501-25-25
S3200-CN102-25-25
15 m
20 m
S3200-CN152-25-25
S3200-CN202-25-25
Over 20 m
S3200-CN-25-25
(Specify length (m) when ordering.)
1. Consult a specialist tradesman if cables with outdoor specifications are required.
2. The cables listed above are black and have power supply lines and tension
members, although the power supply lines aren’t used in the Controller
Link Network.
3. All of the cables listed above are attached to the connectors with adhesive.
4. Special training is required to assemble Optical Fiber Cables and connectors with adhesive.
36
Section 2-2
Connecting H-PCF Cable Optical Ring System Cables
Optical Fiber Cable Accessories
Use the following accessories to assemble and test Optical Fiber Cables.
Name
Optical Fiber Assembly Tool
Optical Power Tester
Model
CAK-0057
Master Fiber Set
S3200-CAT2001H
S3200-CAT2700
Specifications
Crimp-cut tool for the S3200COCF2071/2571 Connectors
With S3200-CAT2702 Head Unit and
adapter for the S3200-COCF2071/
2571 Connectors
One meter cable for use with the
S3200-CAT2702 Head Unit
An S3200-COCF2071/2571 optical connector can be assembled by adding
the JRFK-57PLUS (Sumitomo Electric Industries) to the S3200-CAK1062.
This manual does not provide details on Optical Fiber Cable preparation. For
details, refer to the instructions provided with the S3200-CAK1062 Assembly
Tool.
No Longer Manufactured
Name
Optical Fiber Assembly Tool
2-2-2
Model
S3200-CAK1062
Specifications
Crimp-cut tool for the S3200COCF2011/2511 Connectors
Optical Fiber Cables (H-PCF Cables)
Optical Ring System in
Token Bus Mode
All of the nodes in the Optical Controller Link Network are connected in a line
(daisy-chain configuration) with H-PCF Optical Fiber Cables.
Begin connection with the rightmost connector (SL1) of the highest node in
the network and connect to the leftmost connector (SL2) in the next lower
node, as shown in the following diagram.
The nodes can be connected in any order, but connect the nodes in the order
of node addresses (i.e., node 1, node 2... node 62) as much as possible to
reduce the effect on the communications time if a wire breaks.
Always cover the unused connectors on the highest and lowest nodes in the
network with the enclosed Optical Connector Covers.
Optical Connector Cover
Optical Connector Cover
(Included)
(Included)
← Higher
Lower →
Refer to 2-1-1 Devices Required for Connection Devices for details on available Optical Fiber Cables. Refer to 2-2-3 Installing Connectors for details on
connecting the Optical Fiber Cables to the Controller Link Board.
Note
1. Always use the specified Optical Fiber Cables.
2. The maximum distance between nodes depends on the method used to attach the connector to the cable.
3. In a system using Optical System Units (model numbers ending CLK11) in
Token Bus Mode (daisy chain connections), the maximum number of
nodes is 32 (i.e., node addresses 1 to 32).
37
Section 2-2
Connecting H-PCF Cable Optical Ring System Cables
Optical Ring System in
Token Ring Mode
Connect all the nodes in a ring using H-PCF Optical Fiber Cables.
Begin connection with the rightmost connector (SL1) of the highest node in
the network and connect to the leftmost connector (SL2) in the next lower
node, as shown in the following diagram.
The nodes can be connected in any order, but connect the nodes in the order
of node addresses (i.e., node 1, node 2... node 62) as much as possible to
reduce the effect on the communications time if a wire breaks.
← Higher
Lower →
Refer to 2-1-1 Devices Required for Connection for details on available Optical Fiber Cables. Refer to page 38 Installing Connectors for details on connecting the Optical Fiber Cables to the Controller Link Board.
Note
1. Always use the specified Optical Fiber Cables.
2. The maximum distance between nodes depends on the method used to attach the connector to the cable.
2-2-3
Installing Connectors
A special connector is used to connect the Optical Fiber Cable to the Controller Link Support Board.
This manual does not provide details on Optical Fiber Cable preparation.
Connect the nodes in order beginning with the highest node in the network
and continuing on to lower nodes. When connecting a ring, also connect the
end node in the ring to the start node.
• Always turn OFF the computer and backup power supply before connecting Optical Fiber Cables or the backup power supply connector.
• Special tools are required to attach Optical Fiber Cables to the connectors. The cable may disconnect from the connector if the proper tools and
methods are not used during cable assembly.
Connection Procedure
1,2,3...
1. The Optical Fiber Cable’s power supply line is not used, so it can be cut.
2. As shown in the following diagram, secure the Optical Fiber Cable, and secure the holding piece to the mounting bracket. Secure the two cables simultaneously for nodes (except the end nodes). Pay attention to the
orientation of the mounting bracket and the connector position when connecting the cable from the highest node in the network to the rightmost
connector (SL1), and the cable from the next lower node to the leftmost
connector (SL2).
38
Section 2-2
Connecting H-PCF Cable Optical Ring System Cables
Cable connects to
connector SL1
Cable connects to
connector SL2
3. Install the mounting bracket on the Board with the screws provided. Insert
the tip of the mounting bracket with the grooves into the hole on the Board
surface until it locks firmly (a), and then secure the other end of the mounting bracket using the screw (b). Take care not to bend or pull the Optical
Fiber Cable forcefully.
(Cable is not shown for
clarity of the diagram.)
4. Remove the Optical Connector Cover from the Board again. If there are
covers on the end connectors of the Optical Fiber Cable, remove them.
5. Double-check the direction of the cables. The cable from the node higher
in the network connects to the Board’s right connector and the cable to the
node lower in the network connects to the Board’s left connector. Insert the
cable’s connectors fully into the Board’s connectors.
• Insert the connectors completely and check that the connectors are
locked before starting operation.
• If a connector becomes disconnected, the node will be unable to communicate with other nodes in that part of the network. The network will be
divided into two and communications with the remaining nodes will be
unreliable.
Communications will continue (unreliably)
with the remaining connected nodes.
Network divided into two
(Communications disabled)
39
Section 2-2
Connecting H-PCF Cable Optical Ring System Cables
• Do not pull on the Optical Fiber Cable.
The maximum tension that can be applied to the cord is 10 kg (about 22
lbs) and the maximum tension that can be applied to the cable is 50 kg
(about 110 lbs).
Cord
Cable
• Do not bend the cable paste its natural bending radius. The minimum
radius for bends is 10 cm.
R
• To prevent the Optical Fiber Cable from being pulled too forcefully, always
use the cable mounting bracket and provide space behind the Board as
shown in the following diagram. Do not exceed the maximum tension for
the cord and cable:
Cord: 0 kg (Do not apply any tension.)
Cable: 5 kg (about 11 lbs)
Cord
140 mm
Cable
Rear side of
the computer
• Do not place objects on top of the Optical Fiber Cable. The maximum
pressure that can be placed on the cord and cable is as follows:
Cord: 30 kg/10 cm
Cable: 50 kg/10 cm
• Inspect the connector before installing it.
• When connecting or disconnecting the Optical Fiber Cable, be sure to
hold the connector firmly. (Do not pull on the cable itself.)
40
Section 2-3
Optical Ring System (GI Cable) Wiring
2-3
Optical Ring System (GI Cable) Wiring
This section describes how to wire the communications cables to a GI cable
Ring System Controller Link Support Board (3G8F7-CLK53-E and 3G8F7CLK52-EV1).
2-3-1
Communications Cables
The following devices are required for the Optical Ring (GI) Controller Link
Network.
Optical Fiber Cables
Use Optical Fiber Cables (Graded Index: GI) with the following optical specifications.
50/125 µm AGF Cable
Item
Minimum
Numerical Aper- --ture (N.A.)
Transmission
--loss
Connection loss --Transmission
500
bandwidth
Standard
0.21
---
Maximum
---
---
Unit
3.0 Lf
dB
0.5 km ≤ Lf
0.2 km ≤ Lf < 0.5 km
Lf < 0.2 km
3.0 Lf + 0.2
3.0 Lf + 0.4
-----
1.0
---
Conditions
Theoretical value
MHz⋅km
λ = 0.8 µm
Ta = 25°C
λ = 0.8 µm, one location
λ = 0.85 µm (LD)
Lf is fiber length in km, Ta is ambient temperature, and λ is the peak wavelength of the test light source.
Note
62.5/125 µm AGF Cable
Item
Minimum
Standard
Maximum
Unit
Conditions
Numerical Aper- --ture (N.A.)
0.28
---
---
Theoretical value
Transmission
loss
---
---
3.5 Lf
3.5 Lf + 0.2
dB
0.5 km ≤ Lf
0.2 km ≤ Lf < 0.5 km
Connection loss ---
---
Transmission
bandwidth
---
200
Note
Connectors
3.5 Lf + 0.4
1.0
λ = 0.8 µm
Ta = 25°C
Lf < 0.2 km
λ = 0.8 µm, one location
MHz⋅km
λ = 0.85 µm (LD)
Lf is fiber length in km, Ta is ambient temperature, and λ is the peak wavelength of the test light source.
ST Connector
41
Section 2-3
Optical Ring System (GI Cable) Wiring
2-3-2
GI Optical Fiber Cable Wiring
Optical Ring System in
Token Bus Mode
All of the nodes in the Optical Controller Link Network are connected in a line
(daisy-chain configuration) with H-PCF Optical Fiber Cable.
Refer to the following diagram when making the connections.
Connect the upper node SL2 receive connector to next lower node SL1 send
connector and connect the upper node SL2 send connector to next lower
node SL1 receive connector.
Receive Send
Receive Send
← Higher
Lower →
The connector with the triangle facing up is the receive connector, and with the triangle facing down is the send connector. The color of the triangle indicates the upper node
Board and next lower node Board; Be sure to connect
triangles of the same color.
There is an ID mark on one end of each pair of Optical Fiber Cables. Use this
mark to identify the code.
Incorrect connections may result in a broken wire being incorrectly detected,
and may cause unexpected operation.
The nodes can be connected in any order, but connect the nodes in the order
of node addresses (i.e., node 1, node 2... node 62) as much as possible to
reduce the effect on the communications time if a wire breaks.
Also be sure to cover the unused connectors on the highest and lowest nodes
in the network with the provided Optical Connector Covers.
Optical Connector Cover
Optical Connector Cover
(Included)
← Higher
Lower →
(Included)
Refer to 2-1-1 Devices Required for Connection for details on available Optical Fiber Cables. Refer to 2-2-3 Installing Connectors for details on connecting the Optical Fiber Cables to the Controller Link Board.
Note
1. Always use the specified Optical Fiber Cables.
2. The code for the Optical Fiber Cables can be identified from cable marks
and color, but OMRON recommends adding tags to prevent incorrect connection during installation.
3. The maximum distance between the nodes depends on the type of GI cable (core diameter), as follows:
62.5/125 µm: 2 km maximum distance between nodes
50/125 µm:
1 km maximum distance between nodes
42
Section 2-3
Optical Ring System (GI Cable) Wiring
Optical Ring System in
Token Ring Mode
Connect all the nodes in a ring using GI Optical Fiber Cables.
Refer to the following diagram when making the connections.
Connect the upper node SL2 receive connector to next lower node SL1 send
connector and connect the upper node SL2 send connector to next lower
node SL1 receive connector.
Receive Send
Receive Send
← Higher
Lower →
The connector with the triangle facing up is the receive connector, and with the triangle facing down is the send connector. The color of the triangle indicates the upper node
Board and next lower node Board; Be sure to connect
triangles of the same color.
There is an ID mark on one end of each pair of Optical Fiber Cables. Use this
mark to identify the code.
Incorrect connections may result in a broken wire being incorrectly detected,
and may cause unexpected operation.
The nodes can be connected in any order, but connect the nodes in the order
of node addresses (i.e., node 1, node 2... node 62) as much as possible to
reduce the effect on the communications time if a wire breaks.
← Higher
Lower →
Refer to 2-1-1 Devices Required for Connection for details on available Optical Fiber Cables. Refer to page 38 Installing Connectors for details on connecting the Optical Fiber Cables to the Controller Link Board.
Note
1. Always use the specified Optical Fiber Cables.
2. The code for the Optical Fiber Cables can be identified from cable marks
and color, but OMRON recommends adding tags to prevent incorrect connection during installation.
3. The maximum distance between the nodes depends on the type of GI cable (core diameter), as described below.
62.5/125 µm: 2 km maximum distance between nodes
1 km maximum distance between nodes
50/125 µm:
2-3-3
Installing Connectors
A special connector is used to connect the Optical Fiber Cable to the Controller Link Support Board.
Connect the nodes in order beginning with the highest node in the network
and continuing on to lower nodes. When connecting a ring, also connect the
end node in the ring to the start node.
• Always turn OFF the computer and backup power supply before connecting Optical Fiber Cables or the backup power supply connector.
43
Section 2-3
Optical Ring System (GI Cable) Wiring
• Special tools are required to attach Optical Fiber Cables to the connectors. The cable may disconnect from the connector if the proper tools and
methods are not used during cable assembly.
Connection Procedure
1,2,3...
1. Secure the Optical Fiber Cable tension member.
2. As shown in the following diagram, secure the Optical Fiber Cable, and secure the holding piece to the mounting bracket. Secure the two cables simultaneously for nodes except the start and end nodes. Pay attention to
the orientation of the mounting bracket and the connector position when
connecting the cable from the highest node in the network to the rightmost
connector (SL1), and the cable from the next lower node to the leftmost
connector (SL2).
Cable connects to
connector SL1
Cable connects to
connector SL2
3. Install the mounting bracket on the Board with the screws provided. Insert
the tip of the mounting bracket with the grooves into the hole on the board
surface until it locks firmly (a), and then secure the other end of the mounting bracket using the screw (b). Take care not to bend or pull the Optical
Fiber Cable forcefully.
a
b
(Cable is not shown for
clarity of the diagram.)
4. Remove the Optical Connector Covers from the Unit’s connectors shown
in the following diagram if there are covers protecting the connectors. Remove the covers from the tips of the cables’ ST connectors if there are covers protecting the ST connectors.
44
Section 2-3
Optical Ring System (GI Cable) Wiring
GI Cable Optical Connector Cover
Pull off the cover.
Rotate the cover 90°
counterclockwise.
Note
To replace the Optical Connector Cover, just reverse the steps
shown in the diagram above.
5. Turn the cable connector so that the tab in the connector faces left and
aligns with the slot in the Board’s connector. Insert the cable connector fully into the Board’s optical connector. Press and turn the cable’s connector
clockwise to lock the connector in place.
Board's optical
connector
Slot
Cable optical
connector
Press and turn the metal fitting on
the cable connector until it locks.
Tab
Align the tab in the cable connector with the slot in the
Board's connector and fully insert the cable connector.
Note
To remove the connector, just reverse the steps shown in the diagram above. (Press and turn the cable connector’s metal fitting
counterclockwise to unlock the connector.)
• Insert the connectors completely and always check that the connectors
are locked before starting operation.
• If a connector becomes disconnected while in token-bus mode, the node
will be unable to communicate with other nodes in that part of the network. The network will be divided into two and communications with the
remaining nodes will be unreliable. Be sure not to remove connectors during communications.
Communications are possible with the
connected nodes, but not reliable.
Network divided
(Transmission not possible)
When installing Optical Fiber Cables, be sure to stay within the specifications
(e.g., tensile strength, bending, lateral pressure) for the cables used.
When inserting or removing the Optical Fiber Cables, be sure to hold the connector part firmly.
45
Section 2-4
Backup Power Supply Wiring (Optical Ring Systems Only)
2-4
Backup Power Supply Wiring (Optical Ring Systems Only)
A node bypass function can be used with an Optical Ring Controller Link System (either H-PCF cable or GI cable) by supplying a backup power supply to
the Units and Boards. This will prevent the entire network from going down if a
node malfunctions or the power supply to the PC or computer is turned OFF.
Optical transmission path
Bypass
Computer
Power supply
down
24 VDC
backup power supply
Each node requires a backup power supply for the node bypass function. Several nodes can be connected to a single power supply or each node can be
connected to an independent power supply. If several nodes are connected to
a single power supply, be sure to wire each node separately as shown in the
diagram.
2-4-1
Backup Power Supply Specifications
The input specifications for the backup power supply to the Controller Link
Unit and Support Board are described below. When providing a backup power
supply, make sure that the following specifications are satisfied.
Item
Power supply voltage
Specifications
24 VDC
Allowable power supply voltage fluctuation range
Consumption current
20.4 to 26.4 VDC (24 VDC, –15 to +10%)
Inrush current
2.5 A max. (when 24-VDC rising time is 5 ms)
24 VDC, 400 mA max. (per node)
An OMRON S82K-series Power Supply Unit is recommended.
Note
1. If connecting multiple nodes to one power supply, or if the distance between the power supply and the node is great, carefully consider the maximum current and voltage to satisfy the specifications described above
using the node power supply connectors and terminal positions.
2. Power supply from the backup power supply is given priority. Consider the
following points when designing a system.
a. Turn ON the backup power supply before turning ON the power supply
to the PC and computer.
b.
The communications data will be corrupted in the instant when the
backup power supply is turned ON or OFF.
c.
To make sure that the node bypass function is operating when the
power supply to the PC or computer is OFF, use a separate backup
power supply that is not connected to the PC or computer.
d. Always use a separate backup power supply. Do not use the same
supply as the I/O power supply, motor power cables, or control power
cables.
46
Section 2-4
Backup Power Supply Wiring (Optical Ring Systems Only)
e. Use a backup power supply with double or reinforced insulation.
3. Use the correct power supply voltage, as given above.
2-4-2
Connecting the Backup Power Supply
Observe the following precautions when connecting the backup power supply.
• Separate the backup power supply wires from other power lines and highvoltage lines to prevent noise.
• Attach the special crimp terminals to the power supply wires. (Use the
same crimp terminals as the wired system communications cables. Refer
to 2-1-2 Communications Cable for details.)
• Do not reverse the power supply polarity.
• Tighten the power supply cable hold-down screws to 0.2 N⋅m.
• Do not pull on the power supply cable.
• Do not bend the power supply cable too sharply.
• Do not place any objects on top of the power supply cable.
• Verify that the connector is installed properly before using the power supply.
• Check the wiring configuration carefully before turning ON the power.
• If the connectors on boards in adjacent slots come into contact with each
other, mount one of the boards in a different slot.
Connect the power supply cable to the cable connector and then secure it to
the Board, as shown in the following diagram. (The following diagram shows a
Board using H-PCF cables, but the diagram for GI cables is the same.) Be
sure that the power supply polarity is not reversed.
+
−
+
24 VDC
−
Backup
power
supply
The connector for the backup power supply is the same as the communications connector for Wired Controller Link Support Boards. Refer to 2-1-3 Connecting Cables to Communications Connectors for details on preparing the
power supply wires and connecting them to the connector, and mounting the
cable connectors.
Note
It is difficult to connect or disconnect the backup power supply connector after
the Optical Fiber Cable’s mounting bracket has been installed. Insert the connector before installing the mounting bracket.
47
SECTION 3
Creating Applications Using the C Library
This section describes how to create applications (user programs) that control the Controller Link Support Board.
3-1
3-2
Basic Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
50
3-1-1
Data Link Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
50
3-1-2
Message Service Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51
Using the C Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
52
49
Section 3-1
Basic Flow
3-1
Basic Flow
This section describes the basic procedural flow in creating the applications
(user programs) necessary to use the Controller Link Support Board data link
function and the message service function. Create the applications according
to the flowcharts in this section.
The following explanations assume that the driver and C library have already
been installed. If they have not been, refer to Controller Link Support Board
Installation Guide (W467) before proceeding.
3-1-1
Data Link Procedure
The basic procedure for using data links is outlined in the following flowchart.
START
Data link tables not yet written
(no DATALINK.DAT file)
Data link tables
already written
Write the data link tables
using the Support Software.
Writing data
link tables
Transfer the data link tables to the
other nodes using the Support
Software. (Data link tables
transferred to the Board will be
recorded in the Board's EEPROM.)
Initialization
Open the application interface using
the ClkOpen function.
Read and write data link data using
the ClkRadDatalink and ClkWriteDatalink functions.
Sending/receiving data link data
Ending
Note
The network participation
status and data link operating status can be read
using the ClkGetNetworkStatus function.
Close the application interface using
the ClkClose function.
1. Repeat the process to read/write data link data as often as required by the
application.
2. Data links can be started and stopped from other nodes, by sending FINS
commands from Support Software, by using PC software switches, or by
sending a FINS command from the application using the ClkSendFins
function.
3. Information on errors that occur in using the C library can be read using
the CkGetLastError function.
For details on various methods for making programs, refer to the following
resources.
• Information on using the C library: 3-2 Using the C Library
50
Section 3-1
Basic Flow
• Details on C library functions: SECTION 4 C Language Function Reference
• Support Software: Controller Link Support Software Operation Manual
(W369)
3-1-2
Message Service Procedure
The basic procedure for using the message service is outlined in the following
flowchart.
Routing tables
already written
START
Routing tables already
written or not necessary
Write the routing tables using the
Support Software.
Writing routing
tables
Transfer the routing tables to the
other nodes using the Support
Software. (Routing tables transferred
to the Board will be recorded in the
Board's EEPROM memory.)
Open the application interface using
the ClkOpen function.
Initialization
Send FINS message using the
ClkSendFins function.
Sending and receiving
FINS messages
Check for responses to FINS message
using the ClkRecvFins function.
No response
Response
The network participation status and data
link operating status can be read using
the ClkGetNetworkStatus function.
Ending
Note
Close the application interface using
the ClkClose function.
1. Routing tables are not needed if all communications take place with other
nodes in the local network, but routing tables must be prepared if there are
communications between nodes on different networks.
2. Repeat the process to send and receive FINS messages as often as required by the application.
51
Section 3-2
Using the C Library
3. To used Windows-based messages to determine if a FINS message has
been received, use the ClkSetMessageOnArrival and ClkSetThreadMessageOnArrival functions to register the Windows-based messages to be
used for notification. When not using Windows-based messages, check
periodically for FINS messages using ClkRecvFins.
For details on various methods for making programs, refer to the following
resources.
• Information on using the C library: 3-2 Using the C Library
• Details on C library functions: SECTION 4 C Language Function Reference
• Support Software: Controller Link Support Software Operation Manual
(W369)
3-2
Using the C Library
The Microsoft Visual C++ library functions for the Controller Link Support
Board are provided in the following file.
Fine name
CLK_LIB.LIB
Contents
Microsoft Visual C++ Ver. 6.0 (Service Pack 3) import library file
The library contains the following functions.
Functions
Function name
Name
ClkOpen
Board Open
ClkClose
Board Close
Function
Page
ClkSendFins
FINS Message Send
Opens the application interface and gets a 56
CLK handle.
Closes the application interface and
57
releases the CLK handle.
Sends a FINS message.
57
ClkRecvFins
ClkWriteDatalink
FINS Message Receive
Data Link Data Write
Receives a FINS message.
Writes data to a data link area.
58
59
ClkReadDatalink
ClkGetNetworkStatus
Data Link Data Read
Network Status Read
Reads data from a data link area.
Reads the network status.
59
60
ClkGetRingStatus
ClkSetMessageOnArrival
Optical Ring Status Read
FINS Message Reception
Notification Registration to
Window
FINS Message Reception
Notification Registration to
Thread
Reads the optical ring status.
61
Makes settings to notify the specified win- 61
dow with a Windows message when a
FINS message is received.
Makes settings to notify the specified
62
thread with a Windows message when a
FINS message is received.
FINS Message Reception
Notification Clear
Detailed Error Information
Acquire
Clears windows message notification
63
when a FINS message is received.
Gets an error code generated when a CLK 63
library function is used.
ClkSetThreadMessageOnArrival
ClkClearMessageOnArrival
ClkGetLastError
52
Section 3-2
Using the C Library
Setting Up Visual C++ Ver. 6
Use the following procedure to set up Microsoft Visual C++ to use the C
library.
Include Files
1,2,3...
1. Start Visual C++ Ver. 6.0 and select Tools and then Options.
2. Select the Directory Tab, set the directory being displayed to the one for
the include files, click the first empty row in the list, and then click the ...
Button at the left of the row.
3. Specify the folder in which the C library for the Support Board was installed
and click the OK Button.
The installation directory in the header file default for the C library is \Program Files\OMRON\Controller Link\Lib.
4. Include the following line at the beginning of the program:
#include <CLK_LIB.h>
Setting Up the Library
File.
1,2,3...
1. Start Visual C++ Ver. 6.0 and select Tools and then Options.
2. Select the Directory Tab, set the directory being displayed to the one for
the library files, click the first empty row in the list, and then click the ... Button at the left of the row.
3. Specify the folder in which the C library for the Support Board was installed
and click the OK Button.
The installation directory in the header file default for the C library is \Program Files\OMRON\Controller Link\Lib.
4. Open the workspace for the program being created and select Project and
then Set.
5. Select the Link Tab and input the library file name “CLK_LIB.LIB” for the
object/library module.
Refer to the user’s manual for Visual C++ or online help for information on
Visual C++ other than that for setting up the install file and library file.
Note
There are sample programs provided as Visual C++ V6.0 projects that use the
C library for the Board. They can be found in the Controller Link\Sample directory using the installation directory specified during the installation procedure.
53
SECTION 4
C Language Function Reference
This section gives details on the C-language library functions supported by the Controller Link Support Board.
4-1
Library Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-1-1
ClkOpen()
Board Open . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-1-2
60
ClkGetRingStatus()
Optical Ring Status Read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-1-9
59
ClkGetNetworkStatus()
Network Status Read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-1-8
59
ClkReadDatalink()
Data Link Data Read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-1-7
58
ClkWriteDatalink()
Data Link Data Write. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-1-6
57
ClkRecvFins()
FINS Message Receive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-1-5
57
ClkSendFins()
FINS Message Send . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-1-4
56
ClkClose()
Board Close . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-1-3
56
61
ClkSetMessageOnArrival()
FINS Message Reception Notification Registration to Window . . .
61
4-1-10 ClkSetThreadMessageOnArrival()
FINS Message Reception Notification Registration to Thread . . . .
62
4-1-11 ClkClearMessageOnArrival()
FINS Message Reception Notification Clear . . . . . . . . . . . . . . . . . .
63
4-1-12 ClkGetLastError()
Detailed Error Information Acquire. . . . . . . . . . . . . . . . . . . . . . . . .
4-2
4-3
63
Structure Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
64
4-2-1
CLKHEADER/*PCLKHEADER Structure . . . . . . . . . . . . . . . . . .
64
4-2-2
EMCLKADDRESS/*PEMCLKADDRESS Structure . . . . . . . . . .
64
4-2-3
NSTBUFFER/*PNSTBUFFER Structure . . . . . . . . . . . . . . . . . . . .
65
4-2-4
RINGBUFFER/*PRINGBUFFER Structure . . . . . . . . . . . . . . . . . .
68
Detailed Error Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
69
55
Section 4-1
Library Functions
4-1
Library Functions
This section describes the library functions used for the Control Link Support
Boards for PCI bus. Refer to SECTION 3 Creating Applications Using the C
Library for application methods.
Functions
Function name
ClkOpen
Name
Board Open
ClkSendFins
FINS Message Send
Function
Page
Opens the application interface and gets a 56
CLK handle.
Closes the application interface and
57
releases the CLK handle.
Sends a FINS message.
57
ClkClose
Board Close
ClkRecvFins
ClkWriteDatalink
FINS Message Receive
Data Link Data Write
Receives a FINS message.
Writes data to a data link area.
58
59
ClkReadDatalink
ClkGetNetworkStatus
Data Link Data Read
Network Status Read
Reads data from a data link area.
Reads the network status.
59
60
ClkGetRingStatus
ClkSetMessageOnArrival
Optical Ring Status Read
FINS Message Reception
Notification Registration to
Window
FINS Message Reception
Notification Registration to
Thread
Reads the optical ring status.
61
Makes settings to notify the specified win- 61
dow with a Windows message when a
FINS message is received.
Makes settings to notify the specified
62
thread with a Windows message when a
FINS message is received.
FINS Message Reception
Notification Clear
Detailed Error Information
Acquire
Clears windows message notification
63
when a FINS message is received.
Gets an error code generated when a CLK 63
library function is used.
ClkSetThreadMessageOnArrival
ClkClearMessageOnArrival
ClkGetLastError
4-1-1
ClkOpen()
Board Open
Function
Opens the application interface and gets a CLK handle.
Call Format
Arguments
PCLKHANDLE ClkOpen(BYTE byAppUnitAdr, INT *piRetErr);
Return Value
Type
BYTE
Variable name
Description
byAppUnitAdr
Unit address allocated to the application
INT*
piRetErr
Error information for ClkOpen()
A CLK handle is returned if the function ends normally.
CLK_ERROR is returned if the function ends in an error. Detailed error information is stored in piRetErr.
Description
Set a value between 1 and 15 for AppUnitAdr. Set 0 when it is not necessary
to set a specific application unit address. An unused unit address will be automatically allocated.
The function will end in an error if a Controller Link Support Board is not
mounted.(Detailed error information = ERR_NO_CLKUNIT: No CLK Unit)
The function will end in an error if a handle cannot be obtained because of
insufficient memory. (Detailed error information = ERR_NO_MEMORY: Memory acquisition error)
The function will end in an error if the unit address specified in the argument is
not between 0 and 15. (Detailed error information = ERR_UNIT_ADDRESS:
Unit address range error)
56
Section 4-1
Library Functions
Supplemental Information
The unit address is different from the board ID on the Support Board.
It is not normally necessary to specify a unit address when sending a command from an application running on the computer and receiving a response.
Always specify the unit address when sending a command to the application
from an application running on a computer or from a PC at a different node.
4-1-2
ClkClose()
Board Close
Function
Opens the application interface and gets a CLK handle.
Call Format
Arguments
INT ClkClose(PCLKHANDLE hCLK);
Return Value
CLK_SUCCESS is returned if the function ends normally.
Type
PCLKHANDLE
Variable name
Description
hCLK
The CLK handle obtained with ClkOpen()
CLK_ERROR is returned if the function ends in an error. Detailed error information can be obtained using ClkGetLastError().
Description
4-1-3
If the application is ended without using ClkClose(), the address specified for
ClkOpen() cannot be used again. Always execute ClkClose() for all CLK handles obtained with ClkOpen() before ending the application.
ClkSendFins()
FINS Message Send
Function
Sends a FINS message.
Call Format
INT ClkSendFins(PCLKHANDLE hCLK, PCLKHEADER pHeader, LPVOID
lpMessage, DWORD dwSize);
Arguments
Return Value
Type
Variable name
Description
PCLKHANDLE
hCLK
The CLK handle obtained with ClkOpen()
PCLKHEADER
pHeader
Pointer to the header information structure for the FINS message
LPVOID
lpMessage
DWORD
dwSize
Pointer to the send buffer for the FINS
message
Size of FINS message send buffer
CLK_SUCCESS is returned if the function ends normally.
CLK_ERROR is returned if the function ends in an error. Detailed error information can be obtained using ClkGetLastError().
Description
Refer to Structure Descriptions for information on the header information
structure.
Store the FINS message from the command code (MRC) on in the FINS message send buffer.
The amount of data that can be sent and received will be limited by the type of
networks through which the message must pass. The largest value that the
send buffer (dwSize) can be set to is 1,998 bytes. The limit when passing
through a SYSMAC LINK Network is 542 bytes.
If SID is –1, autoincrementing will be used for the SID. (There is only one SID
memory area for each process when automatically incrementing functions
internally. There are not separate areas for each network handle or thread.)
The function will end in an error if a FINS message send buffer size of less
than 2 bytes is specified in the argument. (Detailed error information =
ERR_SEND_BUFFER_SIZE: Send message size error)
57
Section 4-1
Library Functions
The function will end in an error if SID is not set to between –1 and 255. The
error code will be 39 (SID setting error).
4-1-4
ClkRecvFins()
FINS Message Receive
Function
Receives a FINS message.
Call Format
INT ClkRecvFins(PCLKHANDLE hCLK, PCLKHEADER pHeader, LPVOID
lpMessage, DWORD dwSize, DWORD dwTimeLimit);
Arguments
Type
PCLKHANDLE
PCLKHEADER
LPVOID
DWORD
DWORD
Variable name
Description
hCLK
The CLK handle obtained with ClkOpen()
pHeader
Pointer to the header information structure for the FINS message
lpMessage
Pointer to the receive buffer for the
FINS message
dwSize
dwTimeLimit
Size of FINS message receive buffer
Reception wait time (unit: ms)
Return Value
The size of the FINS message that was receive is returned as the number of
bytes if the function ends normally.
CLK_ERROR is returned if the function ends in an error. Detailed error information can be obtained using ClkGetLastError().
Description
The number of receive bytes in the return value is for all bytes starting from
the command code (MCR) in the FINS message.
Refer to Structure Descriptions for information on the header information
structure.
The FINS message from the command code (MRC) on will be stored in the
FINS message receive buffer.
The function will end in an error if a FINS message receive buffer size of less
than 2 bytes is specified in the argument. (Detailed error information =
ERR_RECV_BUFFER_SIZE: Receive message size error)
The function will end in an error if a message reception area cannot be
obtained because of insufficient memory. (Detailed error information =
ERR_NO_MEMORY: Memory acquisition error)
The function will end in an error if the reception wait time is set to 0 and a
FINS message has not yet been received. (Detailed error information = 38:
Receive timeout)
The function will end in an error if the reception wait time elapses without
receiving a FINS message. (Detailed error information = 38: Receive timeout)
The function will end in an error if the received FINS message is larger than
the reception buffer size. The portion of the FINS message that fits will be
stored in the reception buffer. (Detailed error information =
ERR_MSG_SIZE_OVER: Receive buffer size error)
58
Section 4-1
Library Functions
4-1-5
ClkWriteDatalink()
Data Link Data Write
Function
Writes data to a data link area.
Call Format
INT ClkWriteDatalink(PCLKHANDLE hCLK, PEMCLKADDRESS pEmAddress, LPWORD lpWriteData, DWORD dwSize);
Arguments
Return Value
Type
PCLKHANDLE
Variable name
Description
hCLK
The CLK handle obtained with ClkOpen()
PEMCLKADDRESS
pEmAddress
Pointer to the starting address structure for writing data
LPWORD
lpWriteData
Pointer to the buffer to store the write
data
DWORD
dwSize
Write data size (unit: words)
CLK_SUCCESS is returned if the function ends normally.
CLK_ERROR is returned if the function ends in an error. Detailed error information can be obtained using ClkGetLastError().
Description
Refer to Structure Descriptions for information on the starting address structure for writing data.
The function will end in an error if a data size of 0 is specified for write data
size specified as the argument. (Detailed error information =
ERR_WRITE_BUFFER_SIZE: Write data size error)
The function will end in an error if access is requested to 3 or more different
memory areas for one CLK handle. (Detailed error information =
ERR_MEMORY_AREA: Multiple memory area specification error)
The function will end in an error if a memory name specified in the argument
does not exist. (Detailed error information = ERR_NO_MEM_TYPE: No such
memory)
4-1-6
ClkReadDatalink()
Data Link Data Read
Function
Reads data from a data link area.
Call Format
INT ClkReadDatalink(PCLKHANDLE hCLK, PEMCLKADDRESS pEmAddress, LPWORD lpReadData, DWORD dwSize);
Arguments
Return Value
Type
Variable name
Description
PCLKHANDLE
hCLK
The CLK handle obtained with ClkOpen()
PEMCLKADDRESS
pEmAddress
LPWORD
lpWriteData
DWORD
dwSize
Pointer to the starting address structure for reading data
Pointer to the buffer to store the read
data
Read data size (unit: words)
CLK_SUCCESS is returned if the function ends normally.
CLK_ERROR is returned if the function ends in an error. Detailed error information can be obtained using ClkGetLastError().
Description
Refer to Structure Descriptions for information on the starting address structure for reading data.
The function will end in an error if 0 is specified for the read data size specified
as the argument. (Detailed error information = ERR_READ_BUFFER_SIZE:
Read data size error)
59
Section 4-1
Library Functions
The function will end in an error if access is requested to 3 or more different
memory areas for one CLK handle. (Detailed error information =
ERR_MEMORY_AREA: Multiple memory area specification error)
The function will end in an error if a memory name specified in the argument
does not exist. (Detailed error information = ERR_NO_MEM_TYPE: No such
memory)
4-1-7
ClkGetNetworkStatus()
Network Status Read
Function
Reads the network status.
Call Format
INT ClkGetNetworkStatus(PCLKHANDLE hCLK, BYTE byNet, PNSTBUFFER pBuffer);
Arguments
Type
PCLKHANDLE
BYTE
PNSTBUFFER
Return Value
Variable name
Description
hCLK
The CLK handle obtained with ClkOpen()
byNet
Network address of the Broad to read
network status
pBuffer
Pointer to the buffer structure to store
the read data
CLK_SUCCESS is returned if the function ends normally.
CLK_ERROR is returned if the function ends in an error. Detailed error information can be obtained using ClkGetLastError().
Description
Refer to Structure Descriptions for information on the read data structure.
The read data size is fixed. Provide a memory area the size of the PNSTBUFFER structure as a read data storage buffer.
If the function is executed for a Board that is not part of a network, 0 will be set
for the following members of the read data structure.
Network participation status
Communications cycle time
Polling node address
Data link operation status and data link mode
Data link status
The function will end in an error if an error response code is returned for the
FINS message. (Detailed error information = ERR_RESPONSE: Error
response code error)
The function will end in an error if a Controller Link Support Board is not
mounted for the network specified by the Board network address specified as
an argument. (Detailed error information = ERR_NO_CLKUNIT: No CLK Unit)
The function will end in an error if a message reception area cannot be
obtained because of insufficient memory. (Detailed error information =
ERR_NO_MEMORY: Memory acquisition error).
The function will end in an error if a network address of 0 is specified when
there is more than one network. (Detailed error information =
ERR_NETWORK_ADDRESS).
60
Section 4-1
Library Functions
4-1-8
ClkGetRingStatus()
Optical Ring Status Read
Function
Reads the optical ring status.
Call Format
INT ClkGetRingStatus(PCLKHANDLE hCLK, BYTE byNet, PRINGBUFFER
pBuffer);
Arguments
Return Value
Type
PCLKHANDLE
Variable name
Description
hCLK
The CLK handle obtained with ClkOpen()
BYTE
byNet
Network address of the Broad to read
the optical ring status for
PRINGBUFFER
pBuffer
Pointer to the buffer structure to store
the read data
CLK_SUCCESS is returned if the function ends normally.
CLK_ERROR is returned if the function ends in an error. Detailed error information can be obtained using ClkGetLastError().
Description
Refer to Structure Descriptions for information on the read data structure.
The read data size is fixed. Provide a memory area the size of the PNSTBUFFER structure as a read data storage buffer.
The function will end in an error if an error response code is returned for the
FINS message. (Detailed error information = ERR_RESPONSE: Error
response code error)
The function will end in an error if a Controller Link Support Board is not
mounted for the network specified by the Board network address specified as
an argument. (Detailed error information = ERR_NO_CLKUNIT: No CLK Unit)
The function will end in an error if it is executed for a Wired Board or an Optical Board in token bus mode. (Detailed error information =
ERR_NOT_RING_MODE: Wrong operating mode)
The function will end in an error if a message reception area cannot be
obtained because of insufficient memory. (Detailed error information =
ERR_NO_MEMORY: Memory acquisition error)
The function will end in an error if a network address of 0 is specified when
there is more than one network. (Detailed error information =
ERR_NETWORK_ADDRESS).
4-1-9
ClkSetMessageOnArrival()
FINS Message Reception Notification Registration to Window
Function
Makes settings to notify the specified window with a Windows message when
a FINS message is received.
Call Format
INT ClkSetMessageOnArrival(PCLKHANDLE hCLK, HWND hWnd, UINT
uMsg);
Arguments
Type
PCLKHANDLE
HWND
UINT
Return Value
Variable name
Description
hCLK
The CLK handle obtained with ClkOpen()
hWnd
Window handle to receive event notification
uMsg
Message to use for notification
(WM_USER to 0x7FFF)
CLK_SUCCESS is returned if the function ends normally.
CLK_ERROR is returned if the function ends in an error. Detailed error information can be obtained using ClkGetLastError().
61
Section 4-1
Library Functions
Description
Both ClkSetMessageOnArrival and ClkSetThreadMessageOnArrival cannot
be registered at the same time.
The function will end in an error if a null pointer is specified for the window
handle specified as the argument. (Detailed error information =
ERR_WINDOWHANDLE_PARA: Window handle error)
The function will end in an error if an illegal value is specified for the window
handle specified as the argument. (Detailed error information = 67: Illegal window handle)
The function will end in an error if the message specified in the argument is
over 0x7FFF. (Detailed error information = ERR_MESSAGE_PARA: Message
type error)
The function will end in an error if a message has already been registered for
FINS message reception. (Detailed error information = 69: Duplicated message registration error)
4-1-10 ClkSetThreadMessageOnArrival()
FINS Message Reception Notification Registration to Thread
Function
Makes settings to notify the specified thread with a Windows message when a
FINS message is received.
Call Format
INT
ClkSetThreadMessageOnArrival(PCLKHANDLE
dwThreadId, UINT uMsg);
Arguments
Return Value
Type
Variable name
PCLKHANDLE
hCLK
DWORD
dwThreadId
UINT
uMsg
hCLK,
DWORD
Description
The CLK handle obtained with ClkOpen()
Thread ID to receive event notification
Message to use for notification
(WM_USER to 0x7FFF)
CLK_SUCCESS is returned if the function ends normally.
CLK_ERROR is returned if the function ends in an error. Detailed error information can be obtained using ClkGetLastError().
Description
Both ClkSetMessageOnArrival and ClkSetThreadMessageOnArrival cannot
be registered at the same time.
The function will end in an error if a null pointer is specified for the window
handle specified as the argument. (Detailed error information =
ERR_WINDOWHANDLE_PARA: Window handle error)
The function will end in an error if an illegal value is specified for the window
handle specified as the argument. (Detailed error information = 67: Illegal window handle)
The function will end in an error if the message specified in the argument is
over 0x7FFF. (Detailed error information = ERR_MESSAGE_PARA: Message
type error)
The function will end in an error if a message has already been registered for
FINS message reception. (Detailed error information = 69: Duplicated message registration error)
62
Section 4-1
Library Functions
4-1-11 ClkClearMessageOnArrival()
FINS Message Reception Notification Clear
Function
Clears windows message notification when a FINS message is received.
Call Format
Arguments
INT ClkClearMessageOnArrival(PCLKHANDLE hCLK);
Return Value
CLK_SUCCESS is returned if the function ends normally.
Type
PCLKHANDLE
Variable name
Description
hCLK
The CLK handle obtained with ClkOpen()
CLK_ERROR is returned if the function ends in an error. Detailed error information can be obtained using ClkGetLastError().
4-1-12 ClkGetLastError()
Detailed Error Information Acquire
Function
Gets detailed error information generated when a Controller Link library function is used.
Call Format
Arguments
INT ClkGetLastError(PCLKHANDLE hCLK);
Return Value
Detailed error information is returned if the function ends normally.
Type
PCLKHANDLE
Variable name
Description
hCLK
The CLK handle obtained with ClkOpen()
CLK_ERROR is returned if the function ends in an error.
Description
Refer to 4-3 Detailed Error Information for details on the return value.
63
Section 4-2
Structure Descriptions
4-2
Structure Descriptions
4-2-1
CLKHEADER/*PCLKHEADER Structure
This structure stores heading information for a FINS message. It is used by
ClkSendFins() and ClkRecvFins().
Type
BYTE
Variable name
ByIcfBits
Contents
FINS header ICF
Set the following for the FINS message: Command/response and response
needed/not needed.
0x80 (128) Command requiring response
0x81 (129) Command not requiring response
0xC0 (192) or 0xC1 (193): Response
BYTE
byNetAddr
BYTE
byNodeAddr
Source/destination network address
For ClkSendFins(), set the destination network address.
For ClkRecvFins(), the network address of the source of the FINS message
is stored.
Source/destination node address
For ClkSendFins(), set the destination node address.
For ClkRecvFins(), the node address of the source of the FINS message is
stored.
BYTE
byUnitAddr
INT
nSid
4-2-2
Source/destination unit address
For ClkSendFins(), set the destination unit address.
For ClkRecvFins(), the unit address of the source of the FINS message is
stored.
Service ID
Any value can be set to identify the FINS message.
For ClkRecvFins(), the SID of the received FINS message is stored.
EMCLKADDRESS/*PEMCLKADDRESS Structure
This structure stores heading information for a FINS message. It is used by
ClkWriteDatalink() and ClkReadDatalink().
Type
LPCTSTR
Variable name
lpszMemName
DWORD
dwWordOffset
Contents
Area type
Specify the text string for the event memory area type set for the data link
area.
Number of offset words
Set the number of words to offset from the beginning of the event memory
area specified with IpszType.
The areas and ranges that can be accessed can be changed using FinsGateway event memory settings. The default areas and ranges are listed in the following table.
Area
CIO Area
DM Area
64
Designation
CIO
DM
Range
0 to 32767
0 to 32767
Section 4-2
Structure Descriptions
4-2-3
NSTBUFFER/*PNSTBUFFER Structure
This structure stores network status that has been read. It is used by ClkGetNetworkStatus().
Type
BYTE
Variable name
byConnectionMethod
Contents
Wired/optical discrimination, transmission path form, etc.
Bit
7
6
5
4
3
2
1
0
−: Not specified.
Maximum number of nodes supported
00: 32 nodes
01: 64 nodes
Transmission path
0: Token bus
1: Token ring
Connection type
0: Wired
1: Optical ring
Note
Number of send words
0: 1,000 max.
1: 4,000 max.
When optical and optical ring connections are combined, the maximum number of nodes supported will be given as 62 nodes for an optical ring connection even if the maximum number of nodes is 32.
BYTE
byMyNodeAddr
Local unit address
Stores the local unit address set for the Controller Link Board.
BYTE
byMyUnitAddr
BYTE
byMyNetAddr
Local unit address
Stores the local unit address set for the Controller Link Board.
Local network address
Stores the local network address set for the Controller Link Board.
BYTE
abyNodeList[32]
Network participation status
Stores a list of the nodes participating in the network.
Node Participation Information
Bit
[0]
[1]
[2]
[30]
[31]
Node 1
Node 3
Reserved
Node 2
Node 5
Node 4
0: Not participating in network
1: Participating in network
Node 61
Reserved
Node 60
Node 62
0: Normal disconnection
1: Error disconnection
(when not participating)
0: Normal
1: No response to polling.
Note For Wired Systems with a maximum of 32 nodes, the above
information is valid through node 32 (lower 4 bytes of
abyNodeList[16]).
WORD
wComunicationCycleTime
Communications cycle time
Stores the current value of the communications cycle time. (unit: 0.1 ms)
BYTE
byPollingNodeAddr
Polling node address
Stores the node address of the current polling node.
BYTE
byStatus1
Reserved area
Stores undetermined data.
65
Section 4-2
Structure Descriptions
Type
BYTE
Variable name
byStatus2
Contents
Baud rate, power supply status, terminating resistance setting status
For Wired Systems, stores the set baud rate and the setting of the
terminating resistance switch.
For Optical Ring System, stores the power supply status.
Bit
Baud rate
0x1: 2 Mbits/s
0x2: 1 Mbits/s
0x3: 500 kbits/s
BYTE
byStatus3
Wired System
0: Terminating resistance switch OFF
1: Terminating resistance switch ON
Optical System
0: No backup power supply
1: Backup power supply
Error information 1
Stores information such as whether or not there is an error log recorded,
node address setting errors, etc.
1: Error history
1: Fatal data link error
1: Communications controller send
section error
BYTE
byStatus4
Reserved area
Stores undetermined data.
BYTE
byStatus5
Error information 2
1: Node address setting error
1: Node address duplicated
1: Network parameter mismatch
1: Communications controller
hardware error
Stores information such as EEPROM write errors, setting table errors, etc.
Bit
1: EEPROM write error
1: Network parameter error
1: Data link table error
1: Routing table error
BYTE
66
byStatus6
Reserved area
Stores undetermined data.
Section 4-2
Structure Descriptions
Type
BYTE
Variable name
byStatusFlag
Contents
Data link operation status and data link mode
Stores the data link operation status, data link mode, etc.
Bit
−: Not specified
Current Data Link Mode
0: User-set links
1: Automatic
Data Link Operating Status
0: Stopped
1: Running
BYTE
abyDataLinkStatus[62]
Data link status
Stores the data link status.
Bit
[1]
Node 1
Node 2
[2]
Node 3
[0]
[60]
[61]
Node 61
Node 62
Node Data Link Status
−: Not specified
PC Operating Status
0: Stopped
1: Running (PC program being executed.)
CPU Unit Error Status
0: No error
1: Error
Data Link Communications Error Status
0: Normal
1: Error (Data link data not received normally.)
Data Link Participation Status
0: Not participating or data links stopped
1: Participating
Offset Error Status (Offset larger than number of send words)
0: Normal
1: Error
Insufficient Reception Area (Data larger than data link reception area.
Overflow data discarded.)
0: Normal
1: Insufficient
Excess Reception Area (Data smaller than data link reception area.
0: Normal
Overflow area data not specified.)
1: Excess
Note For Wired Systems with a maximum of 32 nodes, the above
information is valid through node 32 (abyDataLinkStatus[32]).
67
Section 4-2
Structure Descriptions
4-2-4
RINGBUFFER/*PRINGBUFFER Structure
This structure stores optical ring status that has been read. It is used by
ClkGetRingStatus().
Type
WORD
Variable name
wDisConnectionFlag
Contents
Disconnected Line Flags (See graphic following this table.)
WORD
wDisConnectionNodeInfo1
WORD
wDisConnectionNodeInfo2
BYTE
abyDisConnectionInfoRecordTime[6]
DWORD
dwNetworkSeparationCount
Disconnected node information 1 (See graphic following this
table.)
Disconnected node information 2 (See graphic following this
table.)
Starting time for disconnected information storage (See
graphic following this table.)
Number of network separations
DWORD
DWORD
dwNewsorkDisConnectionCount
dwLocalNodeDisConnectionCount
Number of network disconnections
Number of local node disconnections
DWORD
DWORD
dwNetworkDisConnectionMaxCycleCount
dwFrameDropOutsCountSL1
Maximum number of cycles with continuous disconnection
Number of frame dropouts for SL1
DWORD
DWORD
dwFrameDropOutsCountSL2
dwFrameBrakesCountSL1
Number of frame dropouts for SL2
Number of broken frames for SL1
DWORD
DWORD
dwFrameBrakesCountSL2
dwCrcErrorCountSL1
Number of broken frames for SL2
Number of CRC errors for SL1
DWORD
dwCrcErrorCountSL2
Number of CRC errors for SL2
Disconnected Line Flags
High Bits
Network Disconnected Flag
0: Normal
1: Disconnected
Low Bits
Local Node Disconnection Direction Flag (Valid when Local Node Dis0: SL1 (upstream)
connected Flag is ON.)
1: SL2 (downstream)
Local Node Disconnected Flag
0: Normal
1: Disconnected
Disconnected Node Information
High Bits
Disconnection Direction Flag
0: SL1 (upstream)/Normal
1: SL2 (downstream)
Low Bits
Disconnected Node Address (2-digit hexadecimal)
Disconnected node information can be read out for up to two disconnections:
Disconnected Node Information 1 and Disconnected Node Information 2.
68
Section 4-3
Detailed Error Information
Starting Time for Disconnected Information Storage
Bit
[0] Minutes
[1] Seconds
[2] Date of month
[3] Hour (24-hr time)
[4] Year (rightmost 2 digits)
[5] Month
The time when recording disconnection information was started is stored as
shown above. All data is BCD.
4-3
Detailed Error Information
The information read by ClkGetLastError is listed in the following table. Macro
names for error codes are defined in CLK_LIB.H.
Error
code
Macro name
Meaning
1
2
ERR_UNIT_ADDRESS
ERR_NO_CLKUNIT
Unit address range error
Controller Link Unit is missing.
3
4
ERR_NO_MEMORY
ERR_MSG_SIZE_OVER
Memory could not be obtained.
Reception message was too large.
5
6
ERR_NO_MEM_TYPE
ERR_RESPONSE
Memory type does not exist.
Response code error
7
8
ERR_SEND_BUFFER_SIZE
ERR_RECV_BUFFER_SIZE
Send message size error
Reception message size error
9
10
ERR_WRITE_BUFFER_SIZE
ERR_READ_BUFFER_SIZE
Write data size error
Read data size error
11
12
ERR_WINDOWHANDLE_PARA
ERR_MESSAGE_PARA
Window handle error
Message type error
13
14
ERR_MEMORY_AREA
ERR_INTERNAL_FAILURE
Memory type designation error
Unexpected error
15
16
ERR_NOT_RING_MODE
ERR_NETWORK_ADDRESS
Not in Optical Token Ring Mode.
Network address designation error
30
31
-----
Service not defined.
Incorrect network handle
32
33
-----
34
---
Memory insufficient; cannot execute.
Unit of the same unit address already
exists.
Network busy; cannot execute.
35
36
-----
Reception buffer overflow
Data size error
37
38
-----
FINS header error
Reception timeout (no receive data)
39
40
-----
Invalid SID setting
Version is not supported; impossible to
execute.
41
---
Wrong setting in routing tables; cannot
reach final network
42
43
-----
Routing table error
Allowed number of gateways exceeded
44
---
Version already in locked state and can't
change.
69
Section 4-3
Detailed Error Information
Error
code
45
---
70
Macro name
Meaning
Attempted to make header to response.
46
---
Attempted to make response to command that requires no response.
47
---
Could not make event object to be used
for send data notice.
48
---
49
---
50
---
Could not make list object to be used to
receive data.
Failed in standby process of exclusive
control of shared memory.
Failed in mapping of shared memory.
51
52
-----
53
---
Name of object is too long.
Attempted to release unused unit
address.
Unexpected error occurred.
54
55
-----
Failed to initialization of shared memory.
Failed in attachment to shared memory.
56
---
57
---
Number of units (units) simultaneously
usable exceeded.
Send destination unit does not existence.
58
59
-----
60
---
61
---
All reserved area of network handle is
fully used.
62
63
-----
Incoming data is not received yet.
Invalid Windows message type
64
65
-----
Failed in message notice.
Invalid prototype
66
67
-----
Buffer is too short.
Invalid Windows handle
68
---
Failed in beginning thread for sending
message.
69
---
Message registration duplication error
Could not notify data transmission.
Exit from receive standby due to abnormal end of other process.
Failed in receive standby.
SECTION 5
Data Links
This section describes how to use data links in a Controller Link Network.
5-1
5-2
5-3
5-4
5-5
What Are Data Links? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
72
5-1-1
Data Link Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
76
5-1-2
Differences Between Manual and Automatic Setting . . . . . . . . . . .
77
Setting Data Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
77
5-2-1
Selecting Manual or Automatic Setting . . . . . . . . . . . . . . . . . . . . . .
77
5-2-2
Manual Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
78
5-2-3
Data Link Table Specifications for Controller Link Support Boards
80
5-2-4
Automatic Setting: “Select All”. . . . . . . . . . . . . . . . . . . . . . . . . . . .
80
5-2-5
Example of Automatic Setting with Equality Layout . . . . . . . . . . .
81
Starting and Stopping Data Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
82
5-3-1
Using a Programming Device or a Ladder Program . . . . . . . . . . . .
83
5-3-2
Using the Controller Link Support Software . . . . . . . . . . . . . . . . . .
84
5-3-3
Using FINS Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
84
Checking Data Link Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
85
5-4-1
LED Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
85
5-4-2
Data Link Status Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
85
5-4-3
Checking by Manipulating Bit/Word Status . . . . . . . . . . . . . . . . . .
87
Changing the Data Link Tables with Active Data Links . . . . . . . . . . . . . . . .
87
5-5-1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
87
5-5-2
Example of Changing Data Link Table with Active Data Links . . .
88
5-5-3
Operations when Changing Data Link Tables . . . . . . . . . . . . . . . . .
88
5-5-4
Timing Required to Change Data Link Tables with
Active Data Links (Theoretical). . . . . . . . . . . . . . . . . . . . . . . . . . . .
89
71
Section 5-1
What Are Data Links?
5-1
What Are Data Links?
Data links automatically exchange data in the preset areas between nodes
(PCs and/or computers) on one network. Data links can be created for
C200HX/HG/HE PCs, CV-series PCs, CS-series PCs, CJ-series PCs, and
IBM PC/AT or compatible computers.
Two data link areas, area 1 and area 2, can be set for each node.
Data links can be set in either of the following ways.
• Data link areas can be manually set by inputting data link tables through
the CLK Data Link Setting Utility in the FinsGateway or the Controller Link
Support Software. Data link tables are created to define the data links.
These tables enable user-specified allocation of data link areas.
• Data links can be set automatically from a Programming Device. With
automatically set data links, all link areas are the same size.
Both automatic setting and manual setting cannot be used together in the
same network. 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 (first link words and send area size) are made in area 1
and area 2. The sequences of send and receive words are the same in
area 1 and area 2.
• Not all nodes must participate in the data links.
Manually Setting Data Links
Example 1:
Area 1
Area 2
Example 3:
Area 1
The order of send and receive
nodes is free.
#1
#1
#2
#2
#1
#1
#1
#2
#2
#2
#1
Example 2:
Some nodes can send data
without receiving data.
Area 1
#2
Some nodes can receive
data without sending data.
#1
#2
#2
#2
#1
#2
#1
#1
Send only
Area 2
#1
#2
#1
#1
#2
Example 4: A node can receive only a
specified number of words from
the beginning of an area.
Area 1
#1
#1
Receive only
Area 2
#1
#2
#2
#2
#2
Area 2
#2
#1
Several words
from the beginning of area
#1
#1
Receive only
#2
#2
#1
#2
Manually set data links are used to create flexible data links that meet the
needs of the individual system.
• Data links are set in the Controller Link Unit or Board of each node using
the CLK Data Link Setting Utility in the FinsGateway or Controller Link
Support Software or CX-Programmer.
• At PCs, area 1 and area 2 can be selected from memory areas, including
the DM Area and EM Area.
• A send area and its size can be allocated freely for each node.
• The sequence of receive nodes can be changed.
72
Section 5-1
What Are Data Links?
• 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 the beginning of the desired part.
Manual Setting Options
The following options can be set when manually setting data links.
Offsets
Data of only the specified number of words can be received starting from the
specified word position. The starting word is set as an offset from the beginning of the send data. The following is an example.
Specified position in relation to the leading word
Area 1
#1
#1
#2
#1
#2
Specified number of words
Area 2
#1
#1
Specified position in relation to the leading word
#1
#2
Specified number of words
Easy Setting: “Set All”
The send data areas of all nodes can be set to the same size (same as for
automatic setting described next).
Note
Easy Setting appears as “Set All” on the Controller Link Support Board
screen.
Automatically Setting Data Links with Equality Layout
Example
Area 1
(Bit areas)
Area 2
(Data memory)
Node
#3
Node #1
Node #2
#1
#2
#3
#1
#2
#3
#1
#2
#3
#1
#1
#1
#2
#2
#2
#3
#3
#3
Automatic setting can be used to create simple data links.
• Using a Programming Device (such as a Programming Console), set the
automatic 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 2 can be selected from Data Memory.
• A computer cannot be used as the startup node if data links are being
automatically set. When automatically setting data links, computers can
only participate in the data links.
73
Section 5-1
What Are Data Links?
• The maximum number of send/receive words is 8,000 when data links are
automatically set, even for computers. This is because computers relay
on the Controller Link Unit settings in the startup node.
• 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 participating 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
to register the same data links as automatic setting. This Easy Setting can be used first, and then the send size of each node and other settings can be changed as required.
Automatic Setting Data Links with 1:N Allocations
This method is used to simplify setting of 1:N allocation data links between
master and slave nodes.
Area 1
Node 1
Node 2
Node 3
Node 4
1
1
1
1
2
2
3
4
1
1
1
1
2
2
3
4
3
4
Area 2
3
4
• There are three types of 1:N allocations.
• Programming Devices (including Programming Consoles) are used to set
the automatic data link mode in the DM Parameter Area of the PC used
as the startup node.
• Node 1 is the master node.
• Areas 1 and 2 can be selected from bit-access areas or the DM Area.
• The send area sizes of the master and slave nodes are the same for each
area.
• Send nodes are in the same ascending order as node numbers.
• All nodes can be specified to either participate or not participate in the
data link.
• The data link areas (data link start words) are common to all nodes participating in the data links.
74
Section 5-1
What Are Data Links?
Note
1. Automatic data link creation with 1:N allocations can only be used with the
following Controller Link Units and Support Boards:
Wired Networks
CS1W-CLK23, CJ1W-CLK23, 3G8F7-CLK23-E,
CS1W-CLK21-V1, CJ1W-CLK21-V1, and 3G8F7CLK21-EV1
Optical Ring Networks CS1W-CLK13, 3G8F7-CLK13-E,
using H-PCF Cable
CS1W-CLK12-V1 (See note 2.), and 3G8F7-CLK12-EV1
Optical Ring Networks CS1W-CLK53, 3G8F7-CLK53-E,
using GI Cable
CS1W-CLK52-V1 (See note 2.), and 3G8F7-CLK52-EV1
2. Lot numbers 030601 or later.
3. Controller Link Units and Support Boards other than those listed above
cannot participate in 1:N allocation data links. They can, however, join the
network if a parameter in the DM Parameter Area is set so that they do not
participate in the data links.
4. The Controller Link Support Board can be used in automatic data link creation with 1:N allocations, but it cannot be the startup node. Use a Controller Link Unit on the same network as the startup node.
5. For automatic data link creation with 1:N allocations, use the CX-Net in CXProgrammer version 3.2 or later.
Using Offsets
For automatically set data links, all of the send words transmitted by a node
are received by other nodes with no change in size. For manually set data
links, the size of a receive area can be restricted by specifying a number of
words from the beginning word of the words sent by another node.
Automatically set
data links
Manually set
data links
#1
#2
#3
#1
#1
#1
#2
#2
#2
#3
#3
#3
#1
#2
#1
#3
#1
#2
#3
#1
#2
#2
#3
#3
A node can specify the number of
words to receive from the beginning
send word.
However, the above system does not guarantee that only the desired words
will be received and there is a good chance that unnecessary data will also be
received.
Offsetting enables specification of a more specific range of receive data by
indicating both the number of words and the starting word position from the
beginning of the area. The offset refers to the starting word position counted
from the beginning of the area.
#1
#1
#2
Offset from the beginning
Number of words to be received
#2
#1
#3
#3
#2
#1
#2
#3
#3
Restricted reception
from node 1 by
specifying an offset
Restricted reception
from node 2 by
specifying an offset
75
Section 5-1
What Are Data Links?
Application Example of Using Offsets
In the following example, the send data from node 1 is split into three parts
and each part is received by a different node, i.e., each of the other nodes
receives only part of the send data from node 1. This enables effective use of
data link memory 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 Specifications
Item
No. of data link nodes
Description
Optical Ring System: 62 nodes max. (2 nodes min.)
Wired System: 32 nodes max. (2 nodes min.)
Number of Send areas per CS or CJ Series
CS1W-CLK23 or CJ1W-CLK23:
data link
node
4,000 words max.
words
CS1W-CLK21-EV1 or CJ1W-CLK21-EV1:
1,000 words max.
C200HX/HG/HE, CVM1/CV,
CQM1H
Computers
Data link areas
(send and
receive) that
can be created
per node
CS or CJ Series
C200HX/HG/HE, CVM1/CV,
CQM1H
Computers
1,000 words max.
3G8F7-CLK23-E: 4,000 words max.
3G8F7-CLK21-EV1, 3G8F5-CLK21-E:
1,000 words max.
CS1W-CLK23-E or CJ1W-CLK23-E:
20,000 words max.
CS1W-CLK21-EV1 or CJ1W-CLK21-EV1:
20,000 words max. (unit version 1.2 or later)
12,000 words max. (Pre-Ver. 1.2)
8,000 words max.
32,000 or 62,000 words max. (See note 2.)
Allocation of data link areas Manual setting Area 1, 2: Bit-access area (IR, CIO, and LR Areas)
DM Area (DM and EM Areas)
Automatic setting equality
layout
Area 1: IR, CIO, or LR Area
Area 2: DM Area (DM and EM Areas)
Automatic set- Area 1, 2: Bit-access area (IR, CIO, and LR Areas)
ting
DM Area (DM and EM Areas)
1:N allocations
Note
1. Up to 62 nodes can be set by using Repeater Units when the network is
configured with only the 3G8F7-CLK21-EV1, CS1W-CLK23, CJ1WCLK23, or 3G8F7-CLK23-E.
2. When optical and optical ring connections are combined, the maximum
number of nodes is 32 and the maximum number of data link words for a
computer for manual settings is 32,000 words.
76
Section 5-2
Setting Data Links
5-1-2
Differences Between Manual and Automatic Setting
Item
Manual setting
Automatic setting (See note 1.)
Determination of nodes
participating in a data
link
Determined by setting data link tables.
Determined by the data link parameters
set in the data link startup node (the node
used to start the data links).
Data link settings
Set in data link tables that are set in the
nodes to participate in data links.
Data link areas 1 and 2
In each node, area 1 and area 2 are
selected from bit areas (IR, CIO, and LR
Areas) and Data Memory (DM and EM
Areas).
However, areas 1 and 2 cannot be set in
the same memory area.
Can be set freely in each node.
Determined by the data link parameters
set in the data link startup node (the node
used to start the data links).
Area 1 is selected from bit areas (IR, CIO,
and LR Areas) and area 2 is selected from
Data Memory (DM and EM Areas).
Refresh starting word
Can be set freely.
Data link status area
Selected from bit areas (IR, CIO, and LR
Areas) and Data Memory (DM and EM
Areas) in each node.
Selected from bit areas (IR or CIO Areas).
Refresh sequence
Data reception
Can be set in each node freely.
It is possible to set in each node whether
the entire data or a part of the data sent
from another node is received. It is also
possible to not receive the data sent from
a specific node. (See note 2.)
The send sizes can be set freely in each
node. It is also possible for certain node
not to send data. (See note 2.)
Node addresses are in ascending order.
The entire data sent from each node that
is participating in the data link is received.
Data transmission
Note
In area 1 and area 2, data send sizes are
the same in each node.
1. Automatically set data links cannot be started from the Controller Link Support Board.
The Controller Link Support Board can participate in automatically set data
links.
2. If data links are manually set, send/receive area can be selected in each
node, allowing send/receive groups to be created within the network in
area 1 and area 2, as shown below.
Area 1
#1
#1
#2
Group
5-2
5-2-1
#2
#1
#2
#3
#3
#4
#3
#4
#4
Group
Setting Data Links
Selecting Manual or Automatic Setting
Specify either the manual or automatic data link mode in the following DM
parameter area of the PC’s CPU Unit of the startup node, using a PC Programming Device.
Note
1. The data link mode can only be specified in the Controller Link Unit. Refer
to the Controller Link Units Operation Manual (W309) for more details.
2. When the Controller Link Support Board has been set as the startup node,
data links must be manually set.
77
Section 5-2
Setting Data Links
3. A data link mode can be set in a data link startup node only. The data link
mode setting is determined by the data link mode of the startup node even
if the data link mode settings of the nodes participating in the data links are
different from the settings in the startup node.
4. In manual setting, a data link table must be set in the data link startup node
and in automatic setting, automatic data link setting parameters must be
set in the data link startup node. Data links will not be started unless the
settings are correct.
5. Always check whether the data link settings for all startup nodes in the corresponding network are correct to prevent starting up using with incorrect
data link modes and parameters. Make sure that both automatic setting
and manual setting modes are not used together in the same network and
that automatic settings with different parameters are not used.
5-2-2
Manual Setting
Transfer the data link tables that were created on the Support Software to the
Controller Link Unit and the Controller Link Support Board at all node participating in the data links.
Transferring from a Programming Device
C200HX/HG/HE PCs
Nodes
Controller
Link Unit
RS-232C
CPU Unit
+
IBM PC/AT or
compatible
Controller Link
Support Software
CV-series PCs
Nodes
Controller
Link Unit
CPU Unit
Transfer
CS/CJ-series PCs
Nodes
CPU Unit
•••
Data link tables
Controller
Link Unit
Note
1. Data link tables cannot be set in the Controller Link Support Board using
the CX-Net in the CX-Programmer. Use the CLK Data Link Setting Utility
in FinsGateway or the Controller Link Support Software (version 2.00 or
higher).
2. Refer to the Controller Link Support Software Operation Manual (W369) or
the CX-Net Operation Manual for actual setting procedures.
3. When transferring the data link tables to a Controller Link Unit for a CV-series PC, set the System Protect Keyswitch on the CPU Unit to “NORMAL.”
Otherwise, data link tables cannot be written normally.
78
Section 5-2
Setting Data Links
Transferring from a Computer Node
CLK Data Link
Setting Utility in
FinsGateway
IBM PC/AT or
compatible
Controller Link
Support Board
Data link tables
Note
To create data link tables for nodes in the network using the CLK Data Link
Setting Utility in the FinsGateway, the network must have been constructed
correctly. Set routing tables at each node as required. When using manually
set data links, be sure to delete data link tables for all nodes not participating
in data link. Refer to 1-4 Applications Precautions for details. Refer to FinsGateway online help for actual setting procedures for the CLK Data Link Setting Utility.
79
Section 5-2
Setting Data Links
5-2-3
Data Link Table Specifications for Controller Link Support Boards
Setting item
Setting range
Nodes
Optical Ring: 1 to 62 (1 to 32 when optical and optical ring connections are combined.)
Wired: 1 to 32 (Up to 62 nodes can be set by using Repeater Units when the network is
configured with only the 3G8F7-CLK21-EV1, CS1W-CLK23, CJ1W-CLK23, or 3G8F7CLK23-E.)
Set the addresses of the refresh nodes.
First data link status
word
Area 1 Data link
start word
Number of
words
The first data link status word is fixed; the setting cannot be changed. Set to –.
Area 2
Set the start word within the FinsGateway event memory setting range. The defaults are
CIO 0 to CIO 32767 and DM 0 to DM 32767.
Remote nodes: 0 to the number of source words
Set the number of words to be received.
Local node:
0 to 4,000 ([email protected])
0 to 1,000 (3G8F7-CLK21/12/52-EV1)
Set the number of words to be transmitted.
The total number of words in area 1 and area 2 in each node must not exceed 1,000.
The numbers of words in both area 1 and area 2 in each node must not be set to 0.
Offset
Remote nodes:
0 to one less than number of source words
Set the offset for the data to be received.
Local node:
Cannot be set.
This setting is not required if an offset is not used.
Data link
Set the start word within the FinsGateway event memory setting range. The defaults are
start word CIO 0 to CIO 32767 and DM 0 to DM 32767.
Number of Remote nodes: 0 to the number of source words
words
Set the number of words to be received.
Local node:
0 to 4,000 ([email protected])
0 to 1,000 (3G8F7-CLK21/12/52-EV1)
Set the number of words to be transmitted.
The total number of words in area 1 and area 2 in each node must not exceed 1,000.
The numbers of words in both area 1 and area 2 in each node must not be set to 0.
Offset
Remote nodes:
0 to one less than number of source words
Set the offset for the data to be received.
Local node:
Cannot be set.
This setting is not required if an offset is not used.
Note
1. The maximum number of words for area 1 and area 2 combined must be
no more than 62,000 for optical ring connections and no more than 32,000
words for wired connections or systems that combine optical and optical
ring connections.
2. Data link areas in the Controller Link Support Board are allocated in the
FinsGateway event memory. Refer to the FinsGateway online help for information on the area types and sizes in event memory.
3. Be sure to delete data link tables for all nodes not participating in the data
links.
4. When using the Controller Link Support Software, set the “PC type” to “others.”
5-2-4
Automatic Setting: “Select All”
Data links can be automatically created by setting values in the DM parameter
area of the PC’s CPU Unit of the startup node. The settings are made using a
Programming Console “or the SYSMAC Support Software.
80
Section 5-2
Setting Data Links
The startup node is the node from which the data links are activated. When
automatically setting data links, data link operation is based on the values set
in the startup node.
Startup node
Programming Console
Or
CPU Unit
Controller Link
IBM PC/AT or
compatible
Controller Link
DM parameter area
Support Software
Note
1. Parameters for automatically setting data links can only be set in PCs. Refer to the Controller Link Units Operation Manual (W309) for details.
2. A computer (Controller Link Support Board) cannot be the startup node for
an automatically setting data links.
3. A computer can participate in automatically set data links created using
1:N allocations with equality layout. Data link tables are not required in the
computer (the data link tables in the startup node will be used).
4. Refer to the Controller Link Units Operation Manual (W309) for details on
automatically setting data links with 1:N allocations.
5-2-5
Example of Automatic Setting with Equality Layout
This section shows an example of DM parameter area settings and the data
link areas that are created as a result.
DM Parameter Area
Settings
Set the parameters in the startup node as follows:
Data link mode: Automatic
Area 1 data link start word: LR 00
Number of words: 10
Area 2 data link start word: DM 1000
Number of words: 200
First data link status word: IR 310
Participating nodes: #1, #2, and #3
81
Section 5-3
Starting and Stopping Data Links
Data Link Areas Created
Area 1
Node #1 (PC)
Node #2 (PC)
#1
#2
#3
#1
#2
#3
#1
#2
#3
#1
#1
#1
#2
#2
#2
#3
#3
#3
LR 0
LR 10
LR 20
Node #3 (computer)
DM1000
DM1200
Area 2
DM1400
Note
5-3
Refer to the Controller Link Units Operation Manual (W309) for an example of
automatically setting data links with 1:N allocations.
Starting and Stopping Data Links
Data link must be started after data link areas have been created. Use any of
the methods described below for the startup node to start and stop data links.
These methods are the same for both manually and automatically set data
links.
Note
The data link mode (manual setting or automatic setting) and data link method
are determined according to the data link setting in the startup node. In the
startup node, set a data link table in the case of manual setting and data link
automatic setting parameters in the case of automatic setting. If the settings
are incorrect, the data link will not start.
!Caution Check the following items before starting data links. If incorrect data link
tables or parameters are set, injury may result due to unexpected operation of
the system. Even if the correct data link tables and parameters have been set,
do not start or stop data links before verifying that there will be no adverse
influence on the system.
• Manually Set Data Links
Check the data link tables in each node participating in the data link to
see that they are correct.
Be sure that data link tables are deleted from nodes that are not participating in the data links.
• Automatically Set Data Links
Be sure that the correct DM parameters have been set in the data link
startup node.
82
Section 5-3
Starting and Stopping Data Links
5-3-1
Using a Programming Device or a Ladder Program
Set the software switches (AR or DM Start Bit) in the PC to ON using a Programming Device or from the ladder-diagram program.
User program
Startup node
Programming Device
Controller Link
+
CS/CJ-series PCs
Turn ON the Start Bit in DM 3000 + 100 × N.
(N: unit number)
C200HX/HG/HE PCs
Turn ON the Start Bit in AR 07
CV-series PCs
Turn ON the Start Bit in DM 2000 + 100 × N.
(N: unit number)
The data links will start when the Start Bit changes from OFF to ON or is
already ON when power is turned ON. The data links will stop when the Start
Bit changes from ON to OFF.
Note
1. Refer to the Controller Link Units Operation Manual (W309 or W370) for
details on starting and stopping data links using a Programming Device or
ladder program.
2. The data in the AR and DM Areas is retained when power is turned off.
Therefore, by setting in the AR and DM Areas can be made in advance to
start data links as soon as power is turned on. It is recommended to set
the Start Bit to ON in multiple nodes that are participating 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 data
links.
CS-series or CJ-series Startup Node
15 14 13 12 11 10 9
8
7
6
5
4
3
2
1
0
Word N
N: DM 30000 + 100 × (unit number)
Data link Start Bit
Start: Changed from OFF to ON or set to ON
when power is turned on
Stop: Changed from ON to OFF
C200HX/HG/HE Startup Node
15 14 13 12 11 10 9
8
7
6
5
4
3
2
1
0
AR 07
Data link Start Bit for level 0 (AR 0700)
Start: Changed from OFF to ON or set to ON
when power is turned on
Stop: Changed from ON to OFF
Data link Start Bit of level 1 (AR 0704)
Start: Changed from OFF to ON or set to ON
when power is turned on
Stop: Changed from ON to OFF
83
Section 5-3
Starting and Stopping Data Links
CV-series Startup Node
15 14 13 12 11 10 9
8
7
6
5
4
3
2
1
0
Word N
N: DM 2000 + 100 × (unit number)
5-3-2
Data link Start Bit
Start: Changed from OFF to ON or set to ON
when power is turned on
Stop: Changed from ON to OFF
Using the Controller Link Support Software
Data links can be started or stopped using from the command on the Data
Link Menu of the Controller Link Support Software. The node for which starting and stopping is being specified must participate in the data links.
Using a Programming Device Connected to PC Node
IBM PC/AT or
compatible
Controller Link
Support Software
Node in data links
Start/stop data links
Using a Computer Node with FinsGateway
IBM PC/AT or
compatible
FinsGateway
Start/stop specified
directly to Controller
Link Support Board.
5-3-3
Using FINS Commands
Data links can be started and stopped by sending the DATA LINK START and
DATA LINK STOP FINS commands from a node on the Controller Link to a
node that is in the data links.
Sending FINS Commands from a Computer Node
IBM PC/AT or
compatible
FINS command:
DATA LINK START/
DATA LINK STOP
Node in data links
Issuing the FINS Command from CV-series, CS-series, and CJ-series PCs
CV
84
FINS command:
DATA LINK START/
DATA LINK STOP
Node in data links
Section 5-4
Checking Data Link Status
5-4
Checking Data Link Status
There 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 Indicators
Check the LNK indicator on the front of the Board.
Optical Ring Unit
(H-PCF or GI Cable)
Make sure that the LNK
indicator is ON at nodes
participating in the active
data links.
Name
LNK
(data link)
Color
Yellow
Wired Unit
Status
Contents
ON
Flashing
Participating data links.
Data link table setting error.
OFF
Not in data links or data links are inactive.
The LNK indicator will be lit at all node participating in the data links as long
as operation is normal. The data link mode (manual/automatic) can be
checked using the M/A indicator. The M/A indicator is only available in the
Controller Link Unit and cannot be used in the Controller Link Support Board.
Refer to 9-1 Troubleshooting Using Indicators for details.
5-4-2
Data Link Status Area
The data link status area can be used to check for errors when data link does
not operate normally even though no abnormality has been detected by the
computer or the Controller Link Support Board.
Data link status can be monitored using the CLK Data Link Setting Utility in
FinsGateway or it can be stored in FinsGateway event memory. Refer to the
FinsGateway online help and installation guide for details.
85
Section 5-4
Checking Data Link Status
See 9-2 Status Information and Troubleshooting for troubleshooting procedures.
First word
+1
+2
+3
+14
+15
+16
+17
+27
+28
+29
+30
Node 2
Node 4
Node 6
Node 8
Node 1
Node 3
Node 4
Node 7
PC Operating Status
0: Stopped
1: Running (PC program being executed.)
to
to
Node 30
Node 32
Node 34
Node 36
Node 29
Node 31
Node 33
Node 35
to
to
Node 56
Node 58
Node 60
Node 62
Node 55
Node 57
Node 59
Node 61
CPU Unit Error Status
0: No error
1: Error
Data Link Communications Error Status
0: Normal
1: Error (Data link data not received normally.)
Data Link Participation Status
0: Not participating or data links stopped
1: Participating
Offset Error Status (Offset larger than number of send words)
0: Normal
1: Error
Insufficient Reception Area (Data larger than data link reception area.
0: Normal
Overflow data discarded.)
1: Insufficient
Note The first word is set in the Fins
Gateway settings. Refer to Fins
Gateway online help for details.
Status
Excess Reception Area (Data smaller than data link reception area.
0: Normal
Overflow area data not specified.)
1: Excess
Values
Description
PC status
0: Program execution stopped
1: Program being executed
Indicates if the PC program is being executed or not.
Always 1 for Controller Link Support Board nodes.
CPU Unit error
0:
1:
0:
1:
0:
No error
Error
Normal
Error
Not participating in data links
or data links inactive
1: Participating in data links
0: No error
1: Error
Indicates if an error has occurred in the PC.
Always 0 for Controller Link Support Board nodes.
Indicates if data link data for node was received normally or
not.
Receive area
remaining
0: No receive area remaining
1: Receive area remaining
A receive area is “remaining” if the number of words in the
receive area is larger than the number of send words. Data will
be received normally and all words in the receive area beyond
those containing the send words will have indeterminate status.
Insufficient (short)
receive area
0: Receive area not short
1: Receive area short
A receive area is “short” if the number of send words is larger
than the number of words in the receive area. Data will be
received normally, but all words that will not fit in the receive
area will be discarded.
Communications
error
Data link participation
Offset error
Indicates data link participation status.
“Error” indicates that the offset is larger than the number of
send words. The data links will operate and the node will
remain participating in the data links. The receive area at
nodes with this error will be all zeros.
• The following shows an example of a remaining receive area.
No Remaining
Node 1
Send
area
Node 2
Data indicated by
is received in
node 2.
86
Receive
area
Remaining
Node 1
Send
area
Node 2
Receive
area
Data indicated by
is received in node 2 and the
remaining words are cleared.
Section 5-5
Changing the Data Link Tables with Active Data Links
• The following shows an example of an insufficient receive area.
Sufficient
Node 1
Node 2
Send
area
Receive
area
Insufficient (short)
Node 1
Send
area
Receive
area
Data indicated by
cannot be received in node 2.
is received
Data indicated by
and the remaining data is truncated.
Data indicated by
is received in
node 2.
Note
Node 2
1. A communications error will occur in a node that is not participating in the
network.
2. When a communications error occurs or a node is separated from the network, previous status will be retained for other node status.
3. A node which is participating in the network but is not participating in the
data links will show the PC operating status and PC error.
4. On the Controller Link Support Board, a node participating in the network
but not in the data links will show the PC operating status, PC errors, communications errors, and data link participation for all nodes.
5. When there is not enough receive data to filling a receive area (“area remaining”) at a computer node, the status of the rest of the receive area will
be indeterminate.
5-4-3
Checking by Manipulating Bit/Word Status
Although the data link function itself may be operating correctly, the data link
areas may have been input incorrectly.
After you have confirmed that the data link function is operating normally,
check to see whether or not the data link is operating as intended, i.e., check
to see if the desired bits/words data is being transferred to the intended words
at other nodes.
Change the contents of a bit or word in a data link send area using a Programming Device or the user program and check whether the change is reflected in
data link areas of other nodes as intended.
The contents of the data link areas set on the local node for the Controller
Link Support Board can be read and written using the memory monitor program of the FinsGateway. For details refer to the FinsGateway online help.
5-5
5-5-1
Changing the Data Link Tables with Active Data Links
Overview
The data link tables can be changed and data link tables can be allocated for
newly added nodes while the system’s data links are active if the following
Controller Link Units and Support Boards are used.
• Models that Support Data Link Table Changes during Active Data Links
Note
Wired Networks
CS1W-CLK23, CJ1W-CLK23, 3G8F7-CLK23-E,
CS1W-CLK21-V1, CJ1W-CLK21-V1, and 3G8F7CLK21-EV1
Optical Ring Networks
using H-PCF Cable
Optical Ring Networks
using GI Cable
CS1W-CLK13, 3G8F7-CLK13-E,
CS1W-CLK12-V1 (See note 1.), and 3G8F7-CLK12-EV1
CS1W-CLK53, 3G8F7-CLK53-E,
CS1W-CLK52-V1 (See note 1.), and 3G8F7-CLK52-EV1
1. Lot numbers 030601 or later.
87
Section 5-5
Changing the Data Link Tables with Active Data Links
2. When using Controller Link Units and Support Boards that are not listed in
the above table, data link tables cannot be changed while data links are active.
3. CX-Programmer version 3.2 must be used to change data link tables with
active data links. CX-Programmer version 3.1 or earlier versions cannot be
used.
!Caution Check that the contents of the data link table to be changed are correct for the
corresponding node before changing them. If an incorrect data link table is
set, the unexpected operation of the system may result in injury.
!Caution Check that the effects of the data link table to be changed has been considered in the user programs before changing a data link table.
5-5-2
Example of Changing Data Link Table with Active Data Links
System Configuration at Startup
System Configuration after Adding Nodes
CS1W-RPT01
Repeater Unit
CS1W-RPT01
Repeater Unit
Data Link Area
Newly added nodes
Data Link Area
Without stopping the data links, the data
link tables can be changed to exchange
data link data with the new nodes.
5-5-3
Operations when Changing Data Link Tables
The Controller Link Unit/Support Board that receives the command from the
CX-Programmer version 3.2 or later to change a data link table with active
data links will temporarily stop refreshing data with the PC or computer,
change to the new data link table (data link refresh allocation) and then
resume refreshing data links.
Nodes with data link tables that are changed will send the data from immediately before the tables were changed while PC and computer data link
refreshing is stopped.
Command received to change
with active data
links
Time
Data link area of node with the data link table
to be changed
Most recent data read from
Data link send data
Unit
Data immediately
before change
Most recent data read from
Unit.
Data link receive data Most recent data received
from other node
Data immediately
before change
Most recent data received from
other node
Refresh stopped
88
Change during
active data links
completed
Refresh resumed
Changing the Data Link Tables with Active Data Links
Section 5-5
Data link communications will continue, so the Communications Error Flag for
the data link status will not turn ON in any of the nodes in the network.
Refer to 5-5-4 Timing Required to Change Data Link Tables with Active Data
Links (Theoretical) for details on timing required to change the data link
tables.
5-5-4
Timing Required to Change Data Link Tables with Active Data
Links (Theoretical)
When changing data link tables with active data links for Controller Link Support Boards, the data refresh for the corresponding node will stop temporarily.
During that time, even if the data in the data link send area in the computer is
refreshed, it will not be sent as data link data to other nodes. Data received
from other nodes will also not be shown in the data link receive areas of the
other nodes. The data refresh interrupt timing (maximum theoretical value) is
as follows:
Data link refresh maximum interrupt time = Communications cycle time × 3 +
250 ms + Computer overhead time (See note 1.) (ms)
Note
1. The overhead time of the computer varies somewhat with the MPU processing capability and the load created by other applications.
2. Consider the effect of the data link refresh interrupt time on the applications when changing the data link tables. If the maximum interrupt time is
not suitable for the user application, transfer the data link table after stopping the data links from a Programming Device as before, and then restart
the data links.
3. Refer to the Controller Link Units Operation Manual (W309) for information
on changing data link tables with active data links.
89
Changing the Data Link Tables with Active Data Links
90
Section 5-5
SECTION 6
Message Service
This section explains how to use the message service provided by a Controller Link Support Board.
6-1
6-2
6-3
6-4
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
92
6-1-1
Message Service Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . .
92
6-1-2
Message Service Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
92
FINS Command/Response Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
93
6-2-1
Headers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
93
6-2-2
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
94
6-2-3
Data Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
94
Commands and Responses for the Support Board . . . . . . . . . . . . . . . . . . . . .
95
6-3-1
Command Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
95
6-3-2
DATA LINK START . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
95
6-3-3
DATA LINK STOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
96
6-3-4
CONTROLLER DATA READ . . . . . . . . . . . . . . . . . . . . . . . . . . . .
96
6-3-5
CONTROLLER STATUS READ . . . . . . . . . . . . . . . . . . . . . . . . . .
97
6-3-6
NETWORK STATUS READ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
99
6-3-7
DATA LINK STATUS READ . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
101
6-3-8
CONNECTION CONFIGURATION INFORMATION READ . . .
102
6-3-9
NETWORK DISCONNECTION INFORMATION READ . . . . . .
104
6-3-10 NETWORK DISCONNECTION INFORMATION CLEAR . . . . .
106
6-3-11 ECHOBACK TEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
107
6-3-12 BROADCAST TEST RESULTS READ . . . . . . . . . . . . . . . . . . . . .
107
6-3-13 BROADCAST TEST DATA SEND. . . . . . . . . . . . . . . . . . . . . . . . .
108
6-3-14 ERROR LOG READ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
108
6-3-15 ERROR LOG CLEAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
109
Response Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
109
6-4-1
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
109
6-4-2
Network Relay Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
110
6-4-3
Response Codes and Troubleshooting . . . . . . . . . . . . . . . . . . . . . . .
111
91
Section 6-1
Introduction
6-1
Introduction
A message service is a command/response system used for data transmission between nodes on a network, i.e., computer to computer, PC to computer, or computer to PC. The message service can also be used to control
operations, such as mode changes. The message service is implemented by
executing from the user program the library functions for sending or receiving
messages.
6-1-1
Message Service Specifications
Communications from an computer are executed according to the specifications shown in the following table.
Item
6-1-2
Specifications
Direction of transmission
1:1
1:N
Message transmission or reception
Message transmission (broadcast)
Data length
Data content
2,012 bytes max. (including FINS header)
Any command/response data can be sent or received.
Depends on the message being sent.
Message Service Functions
FINS commands can be sent to specified nodes and FINS responses can be
received by executing C library functions from the user program to send and
receive messages.
Functions
Sending Messages
ClkSendFins library function
(See note.)
Features
This library function and driver call send command/response data.
Can be issued with respect to any Units at a PC, or to the Support Board or user
program at a computer.
Mainly used for sending FINS commands and responses. The FINS commands
and responses enable various types of control, and allow the status to be read.
Fixed-format data is prepared by the program and sent by executing clksend.
No special program is required at the receiving end if FINS commands and
responses supported by the receiving Unit are used.
When sending data to the computer with a user program, a program that can process the received data is required.
When a response to a command is returned, a program for reading and analyzing
the response is required.
Receiving Messages
ClkRecvFins library function
These library functions and driver call receive command/response data.
Data received by the Controller Link Support Board is read.
Mainly used for receiving FINS commands and responses. The FINS commands
and responses enable various types of control, and allow the status to be read.
Data is received by executing clkrecv, and it is analyzed by the program according
to a fixed format.
A program is required for analyzing the data that is received.
A program is required for preparing and sending responses when commands
requesting responses are received.
Note
92
Using ClkSendFins or ClkRecvFins to send the “MEMORY AREA READ” and
“MEMORY AREA WRITE” FINS commands for PCs is equivalent to executing
the SEND and RECV ladder-diagram instructions.
Section 6-2
FINS Command/Response Format
6-2
FINS Command/Response Format
This section explains the format of the FINS commands and responses specified by the “clksend” library function.
When actually sending or receiving message service data, the contents specified by the library function parameters are attached as a header. When the
message service is used, however, there is normally no need to pay special
attention to headers.
6-2-1
Headers
Although parameters are used to designate the source, the destination, and
other required information, there are some cases where a header must be
manually added before the command code. Refer to the operation manuals
for individual systems to determine if a header is required. The header format
described below is attached before the command code and the other parameters described for individual commands in the rest of this manual.
Command Data Structure
00
ICF
02
RSV GCT DNA DA1 DA2
SNA
SA1
SA2 SID
Command Text
code
Header
Response Data Structure
00
02
ICF RSV GCT DNA DA1 DA2 SNA SA1
SA2 SID
Command Response
code
code
Text
Header
Details
ICF
Information control field. Individual bits of the ICF are used as follows:
Bit
7
1
6
5
0
4
0
3
0
2
0
1
0
0
Set to 0.
Response setting (0: response required;
1: response not required)
Data type (0: command; 1: response)
Gateway usage (0: don't use; 1: use); set to 1.
Note
All settings below are shown in hexadecimal except where otherwise indicated.
RSV
Reserved. Set to 00.
GCT
Gateway count. Set to 02.
DNA
Destination network address. Specify within the following ranges.
00:
Local network
01 to 7F: Remote network (1 to 127 decimal)
DA1
Destination node number. Specify within the following ranges.
01 to 3E: Node number in Controller Link network (1 to 62 decimal)
01 to 7E: Node number in SYSMAC NET network (1 to 126 decimal)
93
Section 6-2
FINS Command/Response Format
01 to 3E:
FF:
Node number in SYSMAC LINK network (1 to 62 decimal)
Broadcast transmission
DA2
Destination unit address. Specify within the following ranges.
00:
PC (CPU Unit)
01 to 0F: Application on FinsGateway (Refer to FinsGateway online help.)
10 to 1F: Board for CPU Bus Unit or computer
FE:
Unit or Board connected to specified network
(Any Unit or Board in Controller Link, SYSMAC NET, or
SYSMAC LINK network)
SNA
Source network address. Specify within the following ranges.
00:
Local network
01 to 7F: Remote network (1 to 127 decimal)
SA1
Source node number. Specify within the following ranges.
01 to 3E: Node number in Controller Link network (1 to 62 decimal)
01 to 7E: Node number in SYSMAC NET network (1 to 126 decimal)
01 to 3E: Node number in SYSMAC LINK network (1 to 62 decimal)
SA2
Source unit address. Specify within the following ranges.
00:
PC (CPU Unit)
01 to 0F: Application on FinsGateway (Refer to FinsGateway online help.)
10 to 1F: Board for CPU Bus Unit or computer
SID
Service ID. Used to identify the processing generating the transmission. Set
the SID to any number between 00 and FF
6-2-2
Parameters
All parameters are specified in hexadecimal unless otherwise specified.
Where decimal is specified, it is indicated by BCD.
6-2-3
Data Formats
Commands
The command code and text for the command are stored in memory as operands and the transmission is executed using the required parameters. The
specific method depends on the programming method being used. Prepare
the transmission data from the command code to the end of the text (with the
data determined by the individual command), and execute the library function
for message transmission. There are two bytes available for the command
code and 0 to 2,000 bytes for the text.
Command
code
Responses
When the library function for message reception is executed, the data from
the command code to the end of the text (with the data determined by the individual command) is stored as reception data, as shown in the following diagram. There are four bytes available for the command code and response
code, and 0 to 1,998 bytes for the text.
Command Response
code
code
94
Text
Text
Section 6-3
Commands and Responses for the Support Board
Note
6-3
When multiple networks are connected, there are limits to the amount of data
that can be transmitted or received via the Controller Link Network and the
host link function.
Commands and Responses for the Support Board
6-3-1
Command Codes
Command
code
Data link operation
mode
Active
Name
Page
Inactive
04
01
02
Not valid
Valid
Valid
Not valid
DATA LINK START
DATA LINK STOP
95
96
05
06
01
01
Valid
Valid
Valid
Valid
CONTROLLER DATA READ
CONTROLLER STATUS READ
96
97
02
03
Valid
Valid
Valid
Valid
NETWORK STATUS READ
DATA LINK STATUS READ
99
101
04
Valid
Valid
05
Valid
Valid
CONNECTION CONFIGURATION INFORMATION
READ
NETWORK DISCONNECTION INFORMATION READ
06
Valid
Valid
08
21
01
Valid
Valid
102
(See note.)
104
(See note.)
NETWORK DISCONNECTION INFORMATION CLEAR 106
(See note.)
ECHOBACK TEST
107
02
03
Valid
Valid
Valid
Valid
BROADCAST TEST RESULTS READ
BROADCAST TEST DATA SEND
107
108
02
03
Valid
Valid
Valid
Valid
ERROR LOG READ
ERROR LOG CLEAR
108
109
Note
6-3-2
Command codes 06 04, 06 05, and 06 06 are supported only by the Optical
Ring Controller Link Support Boards in Token Ring Mode.
DATA LINK START
Starts the Controller Link Network data links.
Command Block
04
01
Command
code
Response Block
04
01
Command Response
code
code
The DATA LINK START command can be received for manually set data links.
An error will occur if manually set data links are specified and yet data link
tables do not exist.
The node that receives this command and starts the data links will become
the data link startup node.
95
Section 6-3
Commands and Responses for the Support Board
Note
6-3-3
The Support Board can participate in automatically set data links, but it cannot be the starting unit.
DATA LINK STOP
Stops the Controller Link Network data links.
Command Block
02
04
Command
code
Response Block
04
02
Command Response
code
code
The DATA LINK STOP command can be received only while the data links is
active. 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-3-4
CONTROLLER DATA READ
Reads the Controller Link Support Board’s model, version, node address, unit
address, connection type, and network address data.
Command Block
05
01
Command
code
Response Block
05
01
Command Response
code
code
Parameters
20 bytes
Model
20 bytes
00
Network
Version
address
Reserved Wired/ Node Unit
for system Optical address address
Model, version (response): The Controller Link Unit’s model and version are
returned as shown below, each 20 characters in ASCII code. If fewer than 20
bytes of data are used, 20 (Hex) (i.e., spaces) will be returned for the remaining bytes. In the version numbers shown below, the spaces are represented
by boxes (@).
Model
[email protected]@@@@@@@@ (Wired)
[email protected]@@@@@@@@ (Optical Ring, H-PCF cable)
[email protected]@@@@@@@@ (Optical Ring, GI cable)
Version
[email protected]@@@@@@@@@
The first “V1.01” represents the Support Board version number, and the second represents the Communications Controller version number.
96
Section 6-3
Commands and Responses for the Support Board
Connection Type: Wired/Optical (response)
Bit
7
6
5
4
3
2
1
0
Not used
Maximum Number of Supported Nodes
00: 32 nodes
01: 62 nodes
Note When optical and optical ring connections are comTransmission Path
bined, the maximum number of nodes supported
0: Token bus
will be given as 62 nodes for an optical ring connec1: Token ring
tion even if the maximum number of nodes is 32.
Number of send words
0: 1,000 max.
0: Wired
1: 4,000 max.
1: Optical Ring
Node address (response): The Support Board’s node address is returned
between 01 and 3E Hex (1 to 62).
Unit address (response): The unit address set for the Support Board is
returned between 10 and 1F Hex (16 to 31). It is returned even when a unit
address setting error is generated.
Network address (response): The network address set for the Support
Board in the routing table is returned between 00 and 7F Hex (0 to 127). If the
routing table setting has not been made, 00 Hex is returned.
6-3-5
CONTROLLER STATUS READ
Reads the Controller Link Support Board’s controller status.
Command Block
01
06
Command
code
Response Block
06
01
Command Response code
code
Operating status
00
00
Status 1
Status 3
Status 2
00
Status 5
Status 4
00
Count 1
Status 6
Total 6 bytes
Parameters
00
Count 8 Network
participation
status
Total 8 bytes
Operating status (response): The operating status of the data links is 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 network, but the source node is not participating.)
Status 1, Status 4, Status 6 (response): Not used by Controller Link. Always
set to 00 (Hex).
97
Section 6-3
Commands and Responses for the Support Board
Status 2 (response): This byte contains the following information for Controller Link Support Boards. (It is always 00 Hex for Wired Controller Link Support
Boards.)
Bit 7 6 5 4 3 2 1 0
0 0 0
Baud rate setting
0001: 2 Mbps
0010: 1 Mbps
0011: 500 Kbps
Wired System
0: Terminating resistance switch OFF
1: Terminating resistance switch ON
Optical System
0: No backup power supply
1: Backup power supply
Status 3 (response): Error information. The configuration is as follows:
Bit
7
6
5
4
3
2
1
0
0
1: Node address setting error
1: Duplicate node address setting error
1: Network parameter error
1: Controller hardware error
1: Error log exists
1: Data link error stop
1: Controller transmitter error
Note
A network parameter error occurs if the registered network parameter contents do not match the actual network parameter contents after the power is
turned on. The system, however, will not stop. When a network parameter
error occurs, the actual network parameter contents are automatically registered to that Unit.
Status 5 (response): Error information related to the Support Board and the
PC. The configuration is as follows:
Bit 7 6 5 4 3 2 1 0
0 0
1: EEPROM error
1: PC model error
(C200HX/HG/HE only)
1: PC system setting error
(CV-series PCs only)
1: Network parameter error
1: Data link table error
1: Routing table error
A network parameter error, data link table error, or routing table error occurs if
an error is discovered when the parameters and tables are checked at power
up.
A PC system setting error occurs if the Controller Link Unit is not properly recognized by a CS-series, CJ-series, or CV-series PC.
A PC model error occurs if a C200HX/HG/HE Controller Link Unit is mounted
to another type of PC.
Count 1 to Count 8 (response): The total number of times for each of the
items listed below is returned as 1 byte of hexadecimal data.
Count 1:
Count 2:
Count 3:
Count 4:
Count 5:
Count 6:
Count 7:
Count 8:
98
Number of CRC errors
Number of token re-sends
Number of token returns
Number of token timeouts
Number of polling timeouts
Number of controller changes
Number of active node changes
Reserved for system use.
Section 6-3
Commands and Responses for the Support Board
Network participation status (response): The following diagram shows the
bits corresponding to node addresses in the Controller Link Network. When a
bit is returned as “1,” it means that the corresponding node is active (i.e., participating) in the network.
Bit
Byte 1
Byte 2
Byte 3
Byte 4
Byte 5
Byte 6
Byte 7
Byte 8
8 7 6 5 4 3 2 1
16 15 14 13 12 11 10 9
24 23 22 21 20 19 18 17
32 31 30 29 28 27 26 25
40 39 38 37 36 35 34 33
48 47 46 45 44 43 42 41
56 55 54 53 52 51 50 49
− − 62 61 60 59 58 57
Reserved for
system use.
6-3-6
The numbers in the boxes indicate the node
addresses. The bit status of a particular
node address shows whether or not that
node is participating in the network.
0: Not part of network
1: Part of network
(All boxes marked by "−" are reserved
for system use and fixed at "0.")
Bytes 5 to 8 are all reserved for Wired Networks set for
a maximum of 32 nodes.
NETWORK STATUS READ
Reads the operating status of the entire Controller Link Network.
Command Block
06
02
Command
code
Response Block
06
8 bytes
32 bytes
02
Command Response
code
code
Participation
Actual
data communications
cycle time
Polling node address
62 bytes
Data link
Data link data
recurring error status error counter
Data link type
Data link operation
Parameters
Participation data (response): This parameter indicates the active status of
individual nodes with respect to the network (i.e. their participation in the network). As shown in the following diagram, that status is expressed in four bits
corresponding to the node address.
Bit 7 6 5 4
Node #1
Byte 1
3
2
1
0
Reserved (0)
Participation Status of Individual Nodes
0
Byte 2
Node #3
Node #2
Byte 3
Node #5
Node #4
0:Not part of network
1: Part of network
Byte 17
Node #32
Node #32
Byte 18
Node #35
Node #34
0: Normal disconnection
(Applicable only for
1: Abnormal disconnection inactive nodes.)
Byte 32 Reserved (0)
Node #62
0: Normal node
1: Non-responding node
(No response to polling)
All data from the upper 4 bits of byte 16 (node address 33)
though byte 32 are reserved for Wired Units (always 0).
Actual communications cycle time (response): The actual communications cycle time is returned in units of 100 µs in hexadecimal.
99
Section 6-3
Commands and Responses for the Support Board
Polling node address (response): The current polling node address is
returned in hexadecimal.
Data link operation (response): Indicates the status of data link operation in
the network.
Bit 7 6 5 4 3 2 1 0
0 0 0 0 0 0 0
Data link operational status
0: Inactive
1: Active
Data link type (response): Indicates the data transmission status of the
source node’s data links. It is configured as shown in the following diagram.
This parameter is valid only during data link operation. While data link operation is inactive, the value from the previous operation is retained.
Bit 7 6 5 4 3 2 1 0
0 0 0 0 0 0 0
Source node data transmission status
0: Transmission
1: No transmission
Data link recurring error status (response): Indicates whether an error continues to occur at a node when data link data is received. If an error continues
to occur at the same node when the data is received, the bit corresponding to
that node turns to “1” (i.e., turns ON). The configuration is shown in the following diagram.
Bit
Byte 1
Byte 2
Byte 3
Byte 4
Byte 5
Byte 6
Byte 7
Byte 8
7
6
5
4
3
2
1
0
8 7 6 5 4 3 2 1
16 15 14 13 12 11 10 9
24 23 22 21 20 19 18 17
32 31 30 29 28 27 26 25
40 39 38 37 36 35 34 33
48 47 46 45 44 43 42 41
56 55 54 53 52 51 50 49
− − 62 61 60 59 58 57
Reserved for
system use.
The numbers in the boxes indicate the node
addresses. The bit status of a particular
node address shows whether or not there is
a recurring data link error at that node.
0: No recurring error
1: Recurring error
All bytes from 5 to 8 are reserved for Wired Networks set
for a maximum of 32 nodes.
Data link data error counter (response): The total number of data link data
reception errors occurring at all nodes (node addresses 1 to 62) is returned as
a total count from the time the power was turned on. It is expressed, in hexadecimal, as one byte per node. The count can range from 0 to 255 (i.e., 0 to
FF in hexadecimal).
Bit 7
6
5
4
3
2
1
0
Byte 1
Number of error occurrences for node #1
Byte 2
Number of error occurrences for node #2
Byte 3
Number of error occurrences for node #3
Byte 32 Number of error occurrences for node #32
Byte 33 Number of error occurrences for node #33
Byte 62 Number of error occurrences for node #62
All bytes from 33 to 62 are reserved for Wired Networks
set for a maximum of 32 nodes.
100
Section 6-3
Commands and Responses for the Support Board
6-3-7
DATA LINK STATUS READ
Reads the data link operational status.
Command Block
06
03
Command
code
Type
Response Block
06
62 bytes
(See note.)
03
Command Response
code
code
Status flag
Refresh
Refresh
cycle time cycle time
present maximum
value
value
Status
Data link mode
Note The length is 32 bytes for Wired Units if the type is set to 0000 hex or omitted.
Parameters
Type (command):
0000 hex: Returns status from 32 nodes.
0001 hex: Returns status from 62 nodes.
Omitted: Returns status from 32 nodes.
Status flag (response): The overall data link status is returned in one byte of
data, as shown in the following diagram.
Bit 7 6 5 4 3 2 1 0
0 0 0 0
Data link operational status
0: Inactive
1: Active
1: Data link table error
1: No data link table
Data link mode during operation
0: Manual settings
1: Automatic settings
Data link mode (response): The data link mode during operation is returned
in one 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 for
refreshing 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). With the Support
Board, both the present value and the maximum value will be 0.
101
Section 6-3
Commands and Responses for the Support Board
Status (response): The data link status of each mode is returned as shown
in the following diagram. It is the same as the data link read using a library
function. (Refer to page 85.)
Bit 7 6 5 4 3 2 1 0
Byte 1
Byte 2
Byte 3
Node #1
Node #2
Node #3
Byte 62
Node #62
Data link status for each node
7
6
5
4
3
2
1
0
0
PC status
0: Inactive
1: Active
PC's CPU Unit error
0: Normal
1: Error
Communications error (data link reception)
0: Normal
1: Error
Data link participation
0: Not in data link or data link inactive
1: In data link
Offset error
Error: Offset exceeds number of send words.
0: Normal
1: Error
Insufficient (short) receive area Insufficient: Receive area is smaller than send area.
0: Sufficient
Excess data is truncated; other data is received.
1: Insufficient
Remaining receive area
Remaining: Receive area is larger than send area.
Data is received and remaining words are cleared.
0: Not remaining
1: Remaining
Only node addresses 1 to 32 (i.e., 32 bytes) are returned for Wired Units if the type is set to 0000 hex or omitted.
Note
1. The length of data returned is different for Wired and Optical Ring Units.
2. The data link status is not refreshed while the data links are inactive.
3. Nodes which are not active in the network or participating in the data links
will generate communications errors.
4. Any node which is not active in the network retains the status that existed
immediately prior to the generation of the communications error.
5. Only the PC operation status and PC error status will be refreshed for
nodes that are not participating in a data link that is active in the network.
6-3-8
CONNECTION CONFIGURATION INFORMATION READ
Reads the node address of Controller Link Units and Boards connected to the
ring in order in the downstream direction. This command is supported only by
the Optical Ring Controller Link Support Units and Boards in Token Ring
Mode (H-PCF or GI cable).
Command Block
06
04
Command
code
Number of nodes to read
First node to read
102
Section 6-3
Commands and Responses for the Support Board
Response Block
06
04
Command Response
Min
code
code
Sec
Day Hour Year
Month
Node address
Time of connection configuration Number
of nodes
read
Node address
One address for each node read
Parameters
First node to read (command): Specify the node to start the configuration
from counting downstream direction (SL2) from the local node. The number is
specified as a 2-digit hexadecimal value between 00 and 3E (decimal 0 to 62).
Number of nodes to read (command and response): In the command,
specify the number of node addresses to return as a 2-digit hexadecimal
value between 00 and 3E (decimal 0 to 62). If 00 is specified, the node
addresses of all nodes downstream from the current node will be returned.
The response will return the number of node addresses actually read as a 2digit hexadecimal value between 00 and 3E (decimal 0 to 62).
For this command, the node address of the local node is always returned first
regardless of the setting for the first node to read. The number of other nodes
for which addresses are returned will thus be one less than the specified number of addresses. The node address of the specified first node will be returned
as the second node address.
Time of connection configuration (response): These parameters show the
seconds, minutes, hour (0 to 23), date, month, and year (the rightmost two
digits) in BCD specifying the time that the connection configuration was last
updated. The information is updated each communications cycle in Token Bus
Mode as long as the ling connection status is normal. The time will be taken
from the clock data in the local node.
Node address (response): Node addresses are returned in order as 1-byte
hexadecimal values starting from the node address of the local node and then
the node address of the node specified as the first node to read.
Description
If the number of nodes to read and the specified first node to read are such
that the local node is included in the reading range, node addresses will be
read only through the node next to and upstream from the local node. The
read will end normally.
Example: In the following example, the first node to read is specified as 5 and
the number of nodes to read is specified as 6.
Node
12
Node
11
Local node
Node
15
Downstream
Node
6
Node
19
Upstream
Node
32
Specified
first node
to read
Node
25
Node
31
103
Section 6-3
Commands and Responses for the Support Board
The following response will be returned.
19
1F
20
Node address 32
Node address 31
Node address 25 (address of specified first node to read)
Note
6-3-9
1. If there is a disconnection in the network, but most recently updated information will be read.
2. If a node is down, it will be skipped even if the connections are normal.
NETWORK DISCONNECTION INFORMATION READ
Read the Controller Link Board/Unit disconnection information. This command is supported only by the Optical Ring Controller Link Support Units and
Boards in Token Ring Mode (H-PCF or GI cable).
Command Block
06
05
Command
code
Response Block
06
05
Command
code
Response
code
Disconnected Disconnected Disconnected
node innode inLine Flags
formation 1
formation 2
4 bytes
4 bytes
No. of network
separations
No. of network
disconnections
4 bytes
4 bytes
No. of frame
dropouts for SL2
Parameters
Min
Sec
4 bytes
Date Hours Year
4 bytes
4 bytes
No. of local node Max. No. of cycles No. of frame
with continuous dropouts for SL1
disconnections
disconnections
4 bytes
No. of broken
frames for SL2
No. of broken
frames for SL1
4 bytes
4 bytes
No. of CRC
errors for SL1
No. of CRC
errors for SL2
Disconnected Line Flags (response): The line disconnection status is
returned as follows:
1st byte
15 14 13 12 11 10 9
2nd byte
8
0 0 0 0 0 0 0
Network Disconnected Flag
0: Normal
1: Disconnected
7
6
5
4
3
2
1
0
0 0 0 0 0 0
Local Node Disconnection Direction Flag
0: SL1 (upstream)
1: SL2 (downstream)
Local Node Disconnected Flag
0: Normal
1: Disconnected
104
Month
Section 6-3
Commands and Responses for the Support Board
Disconnected node information 1 and 2 (response): The address of the
disconnected node and the direction of the disconnection from the node
(upstream or downstream) are returned.
1st byte
15 14 13 12 11 10 9
2nd byte
8
7
6
5
4
3
2
1
0
0 0 0 0 0 0 0
Disconnection Direction Flag
0: SL1 (upstream)/Normal
1: SL2 (downstream)
Disconnected Node Address
(2-digit hexadecimal (00: No
disconnection information))
Disconnected node information is returned for two disconnections: Disconnected Node Information 1 and Disconnected Node Information 2.
Starting time for disconnection information storage (response): These
parameters show the seconds, minutes, hour (0 to 23), date, month, and year
(the rightmost two digits) in BCD specifying the last time the local node was
turned ON, the Controller Link Unit/Board was reset, or the disconnection
information was cleared. The time will be taken from the clock data in the local
node.
Number of network separations (response): Specifies the number of times
the local node has been separated from the network since the starting time for
disconnection information. The value is given as an 8-digit hexadecimal value.
Number of network disconnections (response): Specifies the number of
times disconnection information has been received from the polling node
since the starting time for disconnection information. If the same disconnection information is received two or more communications cycles in a row, it is
considered a continuous disconnection and not counted. The value is given
as an 8-digit hexadecimal value.
Number of local node disconnections (response): Specifies the number of
times a disconnection has occurred at the local node since the starting time
for disconnection information. If the disconnection information is the same two
or more communications cycles in a row, it is considered a continuous disconnection and not counted. The value is given as an 8-digit hexadecimal value.
Maximum number of cycles with continuous disconnection (response):
Specifies the largest number of cycles that disconnection information has
been received from the polling node since the starting time for disconnection
information. The value is given as an 8-digit hexadecimal value. This value
can be multiplied by the maximum communications cycle time of the Controller Link Network to estimate the time that data has not been sent and
received.
Number of frame dropouts for SL1 and SL2 (response): Specifies the
number of frames that have been normally received by other systems but
have not been received at all at the local node since the starting time for disconnection information. The value is given as an 8-digit hexadecimal value.
Number of broken frames for SL1 and SL2 (response): Specifies the number of frames that have been normally received by other systems but for which
only the carrier was received at the local node since the starting time for disconnection information. The value is given as an 8-digit hexadecimal value.
Number of CRC errors for SL1 and SL2 (response): Specifies the number
of CRC and Manchester errors since the starting time for disconnection information. The value is given as an 8-digit hexadecimal value.
105
Commands and Responses for the Support Board
Description
Section 6-3
Disconnection information can be used for Optical Ring Controller Link Units
and Boards that are in Token Ring Mode to notify the polling node of information on disconnections and then notify all nodes of the disconnection information from the polling node. The disconnection information can be used to
determined the location of the disconnection. For details, refer to the Optical
Ring Controller Link Units Operation Manual (W370).
None of the disconnection information except for the Disconnected Line Flags
is cleared when communications recover. The Disconnected Line Flags
always show the most current disconnection status. Disconnected Node Information 1 and 2 are overwritten whenever new information is generated.
Disconnection information can be cleared either by executing the NETWORK
DISCONNECTION INFORMATION CLEAR (06 06) FINS command or from
the Controller Link Support Software (Ver. 2.00 or higher). (The FINS command must be executed for each node separately.)
6-3-10 NETWORK DISCONNECTION INFORMATION CLEAR
Clears the network disconnection information. This command is supported
only by the Optical Ring Controller Link Support Units and Boards in Token
Ring Mode (H-PCF or GI cable).
Command Block
06
06
Command
code
Response Block
06
06
Command
code
Description
106
Response
code
None of the disconnection information except for the Disconnected Line Flags
is cleared when communications recover. The Disconnected Line Flags
always show the most current disconnection status. Disconnected Node Information 1 and 2 are overwritten whenever new information is generated. This
command, however, can be used to clear the disconnection information to its
default status.
When the command is executed, the disconnection information and the ring
status is cleared from the Controller Link Unit/Board and the starting time for
disconnection information is reset. (The time will be taken from the clock data
in the local node.)
Disconnection information is cleared only from the node that receives this
command. The command must be sent to all nodes in the network to clear all
of the disconnection information.
Disconnection information can also be cleared from the Controller Link Support Software (Ver. 2.00 or higher), and can be cleared for all nodes at the
same time (in one operation).
Section 6-3
Commands and Responses for the Support Board
6-3-11 ECHOBACK TEST
Executes an echoback communications test between specified nodes.
Command Block
08
01
Command
code
1,998 bytes
max.
Test data
Response Block
08
01
Command Response
code
code
Parameters
1,998 bytes
max.
Test data
Test data (command, response): For the command, up to 1,998 bytes of
data can be specified to be sent to a specified node. For the response, the
test data that was sent by the command is returned unchanged.
An error is generated if the data returned by the response is different from the
data that was sent by the command.
6-3-12 BROADCAST TEST RESULTS READ
Reads for each node the results (number of receptions) of a BROADCAST
TEST DATA SEND command that has been sent to all nodes in a specified
network. (For details on the BROADCAST TEST RESULTS SEND command,
refer to 6-3-13 BROADCAST TEST DATA SEND.
Command Block
08
02
Command
code
Response Block
08
02
Command Response
code
code
Parameters
Number of
receptions
Number of receptions (response): The number of times that broadcast test
data has been received at the command destination node from the time that
the last BROADCAST TEST RESULTS READ command was sent until this
one was sent is returned.
An error will be generated if that number of receptions differs from the number
of times that the BROADCAST TEST DATA SEND command was issued during that same period.
The number of receptions value being retained at the destination node is
cleared when the BROADCAST TEST RESULTS READ command is executed.
107
Section 6-3
Commands and Responses for the Support Board
6-3-13 BROADCAST TEST DATA SEND
Broadcasts test data to all nodes in a specified network.
Command Block
08
03
Command
code
2,000 bytes
max.
Test data
There is no response to this command.
The control data must be set as follows when this command is issued:
Destination node address:
FF (Hex) (for broadcasting the data)
Destination unit address:
FE (Hex)
(for the Controller Link Support Board or Unit)
Response required/not required flag: 1 (response not required)
The transmission and reception status is checked by comparing the number
of times this command is issued with the number of receptions parameter of
the BROADCAST TEST RESULTS READ command. (For details, refer to 6-312 BROADCAST TEST RESULTS READ.
6-3-14 ERROR LOG READ
Reads the PC’s error log.
Command Block
21
02
Command
code
Beginning
record no.
No. of
records
Response Block
21
02
10 bytes
Command Response Max. no. of
No. of
code
code stored records stored
records
Parameters
No. of
records
Error log
data
10 bytes
Error log
data
Beginning record no. (command): Specifies the first record to be read, in
two bytes (four digits) in hexadecimal. (The first record number is 0000 in
hexadecimal).
No. of records (command and response): Specifies the number of records
to be read, within a range of 0001 to 0027 in hexadecimal (decimal: 1 to 39).
Max. no. of stored records (response): Specifies the maximum number of
records that can be recorded, within a range of 0001 to 0040 in hexadecimal
(decimal: 1 to 64).
No. of stored records (response): The number of records that have been
recorded by the time the command is executed.
Error log data (response): The specified error log records are returned in
sequence starting from the beginning record number. The total number of
bytes required is calculated as follows:
No. of records × 10 bytes
108
Section 6-4
Response Codes
The configuration of each error record is as follows:
1st byte
10th byte
Error code
Details
Minutes
Day Hour Year Month
Seconds
Error code, details: These parameters show the contents of errors. For
details, refer to 9-3-2 Error Codes.
Date and time: These parameters show the seconds, minutes, hour (0 to
23), date, month, and year (the rightmost two digits) in BCD specifying the
time that the error occurred.
Note
If the PC does not have the specified number of records, all the records that
have been stored in the PC up to the point that the command is executed will
be returned.
6-3-15 ERROR LOG CLEAR
Clears all error log records and sets the error log pointer to 0.
Command Block
21
03
Command
format
Response Block
21
03
Command Response
code
format
6-4
Response Codes
This section describes the response codes returned with responses to FINS
commands. Response codes can be used to confirm normal completion of
command execution or to troubleshoot problems when commands fail. For further troubleshooting information, refer to SECTION 9 Troubleshooting and
Maintenance of this manual and to the operation manuals for specific Units or
Systems.
6-4-1
Configuration
Response codes for FINS commands consist of two bytes that indicate the
result of executing a command. The structure of the response codes is shown
in the following diagram.
First byte
Bit
7
6
5
4
3
Second byte
2
1
0
Main response code (MRES)
1: Relay Error Flag
7
6
5
4
3
2
1
0
Sub-response code (SRES)
1: PC Non-fatal Error Flag
1: PC Fatal Error Flag
109
Section 6-4
Response Codes
The main response code (MRES) in the first byte classifies the response and
the sub-response code (SRES) in the second byte indicates details under the
MRES classification.
If bit 7 of the first byte is ON, a network relay error has occurred. Refer to 6-42 Network 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 computer returning the response. Refer to the operation manual for the device
returning the response for details when troubleshooting the error.
6-4-2
Network Relay Errors
A network relay error will occur whenever a command cannot reach the destination. These errors can occur for several reasons: 1) Data was not successfully passed between two Link Units, 2) Data was not passed successfully
between a Link Unit and another Unit, such as the PC’s CPU Unit, or 3) The
destination of a gateway does not exist. In any case, the Unit that was not able
to transfer data will 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
has occurred. When this happens, two more bytes of data will follow the
response code to indicate the location of the error. This information, along
with the response code, should enable you to track the error.
First byte
Bit
Second byte
7
6
5
4
3
2
1
0
7
6
7
6
5
4
3
Command code
2
1
0
7
6
5
4
3
2
1
0
5
4
3
2
1
0
First word
Sub response code (SRES)
Main response code (MRES)
Second word
1: PC Non-fatal Error Flag
1: PC Fatal Error Flag
1: Relay Error Flag
7
Third word
6
5
4
3
2
1
Error network address
Error network address:
Error node address:
SYSMAC NET:
SYSMAC LINK:
Relay Errors
0
7
6
5
4
3
2
1
0
Error node address
00 to 7F (Hex) (0 to 127 in decimal)
Controller Link:01 to 3E (Hex) (1 to 62 in decimal)
01 to 7E (Hex) (1 to 126 in decimal)
01 to 3E (Hex) (1 to 62 in decimal)
A relay error indicates that the command did not reach the Unit to which it was
sent. There are two types of situation in which this can occur. Example 1
(below) shows a situation in which a relay error occurs when data cannot be
transferred from one Communications Unit to another in an interconnected
network. In Example 2, the relay error occurs because either the specified
destination node or the next relay node does not exist.
In the two 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.
110
Section 6-4
Response Codes
Example 1
In this example, data cannot be transferred between Controller Link Units due
to some cause such as a routing table error.
Computer
Controller Link Unit
Controller Link Unit
Controller Link Support Board
Response
Transmission
Example 2
In this example, the specified destination node or the next relay node does not
exist.
Computer
Controller Link Unit
Controller Link Unit
Controller Link Support Board
Response
Transmission
If an error occurs, check the MRES and SRES codes for the node in question,
and correct the problem.
6-4-3
Response Codes and Troubleshooting
The table below lists response codes (main and sub-codes) returned after
execution of the FINS commands, the probable cause of errors, and recommended remedies.
Upon receipt of some commands, the destination node will issue a request to
another node; the other node is referred to as the third node.
Main code
00: Normal completion
01: Source node error
Subcode
00
Probable cause
Remedy
---
---
01
Service was interrupted
Check the contents of the destination transmission area of third node.
Check the data link status.
Add to Network.
01
Source node not part of Network
02
Token time-out, node address too large Set the source node’s node address below
the maximum node address.
03
Number of transmit retries exceeded
04
Maximum number of frames exceeded
05
Node address setting error (range)
06
Node address duplication error
Check communications with echoback test.
If the test fails, check network.
Either check the execution of events in the
network and reduce the number of events
occurring in one cycle, or increase the maximum number of frames.
Correct the node address so that it is within
specified range and that there are no node
addresses that are set twice.
Make sure that there are no node
addresses that are set twice.
111
Section 6-4
Response Codes
Main code
02: Destination node
error
Subcode
01
Destination node not part of Network
Add to Network.
No node with the specified node
address
Check the destination node’s node address.
03
Third node not part of Network
Broadcasting was specified.
04
Busy error, destination node busy
Check the third node’s node address.
Check the control data and specify only one
node as the third node.
Increase the number of transmit retry
attempts or re-evaluate the system so that
the destination node is not so busy receiving data.
05
Response time-out, message packet
was corrupted by noise
Response time-out, response watchdog timer interval too short
Frame lost in transmission
Increase the number of transmit retry
attempts.
Increase the value for the response watchdog timer interval in the control data.
Check the error log and correct the process.
Error occurred in the communications
controller, ERC indicator is lit
Take corrective action, referring to communications controller errors and remedies
table at end of this section
02
CPU Unit error occurred in the PC at
the destination node
Clear the error in the CPU Unit (refer to the
PC’s operation manuals)
03
A controller error has prevented a normal response from being returned.
Check network communications status and
reset the controller board. If the error still
exists, replace the controller board.
04
Unit address setting error
01
02
05: Routing error
01
02
10: Command format
error
Make sure the unit address and unit number
are within the specified ranges and that
each number/address is set only once.
An undefined command has been
Check the command code and be sure that
used.
the Unit supports it.
Cannot process command because the Check the unit model and version.
specified unit model or version is
wrong.
Destination node address is not set in Set the destination node address in the
the routing table.
routing table.
Routing table isn’t registered.
Set the source nodes, destination nodes,
and relay nodes in the routing table.
03
04
Routing table error
The maximum number of relay nodes
(2) was exceeded in the command.
Set the routing table correctly.
Redesign the network or reconsider the
routing table to reduce the number of relay
nodes in the command.
01
The command is longer than the max.
permissible length.
The command is shorter than min. permissible length.
The designated number of data items
differs from the actual number.
An incorrect command format has
been used.
Check the command format of the command and set it correctly.
Check the command format of the command and set it correctly.
Check the number of items and the data,
and make sure that they agree.
Check the command format of the command and set it correctly.
An incorrect header has been used.
(The source node’s relay table or relay
node’s local network table is wrong.)
Set the routing table correctly.
02
03
04
05
112
Remedy
02
03: Communications con- 01
troller error
04: Not executable
Probable cause
Section 6-4
Response Codes
Main code
11: Parameter error
Subcode
01
Remedy
A correct memory area code has not
been used or Extended Data Memory
is not available.
Check the command’s memory area code
and set the appropriate code.
02
The access size specified in the command is wrong, or the first address is
an odd number.
Set the correct access size for the command.
03
The first address is in an inaccessible
area.
Set a first address that is in an accessible
area.
04
The end of specified word range
exceeds the acceptable range.
06
A non-existent program no. has been
specified.
The sizes of data items in the command block are wrong.
Check the acceptable limits of the data area
and set the word range within the limits.
Check the data link tables to be sure the
limit to link words has not been exceeded.
Check the program number and be sure
that it is set correctly.
Check the command data and be sure that
the sixes of the data items are correct.
09
0A
0B
0C
20: Read not possible
Probable cause
02
Check the data link tables to be sure all
nodes in the refresh parameters are in the
common link parameters.
The IOM break function cannot be exe- Either abort the current IOM break function
cuted because it is already being exe- processing, or wait until it is completed and
cuted.
execute the command.
Check the data link tables for node
addresses that have been set twice.
The response block is longer than the Check the command format and set the
max. permissible length.
number of items correctly.
An incorrect parameter code has been
specified.
Check the command data and reenter it correctly.
The data is protected.
Check the data link table file for corruption.
Execute the instruction again after issuing
the PROGRAM AREA PROTECT CLEAR
command to the PC.
An attempt was made to download a
file that is being uploaded.
03
The registered table does not exist or is Set or reset the registered table.
incorrect.
Too many files open.
04
06
The corresponding search data does
not exist.
A non-existing program no. has been
specified.
A non-existing file has been specified.
07
A verification error has occurred.
05
Check the file name and either interrupt servicing or wait for servicing to complete
before re-executing the command.
Close open files and re-execute the command.
--Check the program number and be sure
that it is set correctly.
Check whether the correct file name was
used.
Check whether the memory contents are
correct and replace if incorrect.
Check the contents of the file. A read error
may have occurred.
113
Section 6-4
Response Codes
Main code
21: Write not possible
Subcode
01
02
Probable cause
The specified area is read-only or is
write-protected.
If the specified area is read-only, the write
cannot be performed. If it is write-protected,
turn off the write-protect switch and execute
the instruction again.
The data is protected.
Execute the instruction again after issuing
the PROGRAM AREA PROTECT CLEAR
command to the PC.
Check the file name and either interrupt servicing or wait for servicing to complete
before re-executing the command.
Change the data link mode to manual.
An attempt was made to simultaneously download and upload a file.
03
The data link tables cannot be written
manual because the Unit is set for
automatic generation.
The number of files exceeds the maximum permissible.
Too many files open.
05
07
The specified file already exists.
Change the name of the file and execute
the instruction again.
08
Data cannot be changed.
The mode is wrong (executing).
Check the contents of the memory area
being written to.
Check the operating mode.
Data links are active.
Check the data link status before execution.
02
The mode is wrong (inactive).
Data links are active.
Check the operating mode.
Check the data link status before execution.
03
The PC is in the PROGRAM mode.
04
The PC is in the DEBUG mode.
05
The PC is in the MONITOR mode.
06
The PC is in the RUN mode.
Check the PC’s mode and the computer
mode.
Check the PC’s mode and the computer
mode.
Check the PC’s mode and the computer
mode.
Check the PC’s mode and the computer
mode.
07
The specified node is not the control
node.
Check which node is the control node.
08
The mode is wrong and the step cannot be executed.
Check whether the step has active status or
not.
01
A file device does not exist where spec- Mount the Memory Card or disk
ified.
The specified memory does not exist. Check the specifications of the installed file
memory.
No clock exists.
Check the model number.
03
114
Close open files and re-execute the command.
Check the program number and be sure
that it is set correctly.
---
06
02
24: Start/stop not possible
Write the file(s) again after erasing
unneeded files, or use different disk or
Memory Card that has free space.
A non-existing program no. has been
specified.
A non-existent file has been specified.
22: Not executable in cur- 01
rent mode
23: No Unit
Remedy
01
The data link tables either have not
been created or are incorrect.
Set the data link tables correctly.
Section 6-4
Response Codes
Main code
25: Unit error
Subcode
02
03
04
05
06
Probable cause
Parity/checksum error occurred
because of incorrect data.
I/O setting error (The registered I/O
configuration differs from the actual.)
Remedy
Transfer correct data into memory.
Either change the actual configuration to
match the registered one, or generate the I/
O table again.
Too many I/O points
Redesign the system to remain within permissible limits.
CPU bus error (An error occurred dur- Check the Unit, Service Boards, and cable
ing data transfer between the CPU Unit connections and issue the ERROR CLEAR
and a CPU Bus Unit.)
command.
I/O duplication error (A rack number,
Check the system’s settings and eliminate
unit number, or I/O word allocation has any settings that occur twice.
been duplicated.)
07
I/O bus error (An error occurred during Check the Unit, Service Boards, and cable
data transfer between the CPU Unit
connections and issue the ERROR CLEAR
and an I/O Unit.)
command.
09
SYSMAC BUS/2 error (An error
occurred during SYSMAC BUS/2 data
transfer.)
Check the Unit, Service Boards, and cable
connections and issue the ERROR CLEAR
command.
0A
Special I/O Unit error (An error
occurred during CPU Bus Unit data
transfer.)
Duplication in SYSMAC BUS word allocation.
Check the Unit, Service Boards, and cable
connections and issue the ERROR CLEAR
command.
Check and regenerate the I/O table.
0F
A memory error has occurred in internal memory, in the Memory Card, or in
Expansion DM during the error check.
10
Terminator not connected in SYSMAC
BUS System.
If the error occurred in internal memory or
the EM Unit, correct the data in the command an execute it again.
If the error occurred in a Memory Card or
EM used for file memory, the file data has
been corrupted. Execute the MEMORY
CARD FORMAT command for the PC.
If the above remedies do not eliminate the
error, replace the faulty memory.
Connect the terminator correctly.
0D
115
Section 6-4
Response Codes
Main code
26: Command error
Subcode
01
Probable cause
The specified area is not protected.
This response code will be returned if
an attempt is made to clear protection
on an area that is not protected.
Remedy
The program area is not protected, so it isn’t
necessary to clear protection.
02
An incorrect password has been speci- Specify a password that is registered.
fied.
04
The specified area is protected.
Execute the command again after executing
the PROGRAM AREA PROTECT CLEAR
command for the PC.
To many commands at destination.
The destination has received more than 5
commands. Either interrupt servicing or wait
for servicing to complete before re-executing the command.
Execute the command again after the service has been completed or aborted.
Execute the service if necessary.
05
The service is being executed.
06
The service is not being executed.
07
Service cannot be executed from
source node because the source node
is not part of the data links.
Execute the service from a node that is part
of the data links.
A buffer error has prevented returning a Reset the board. If the error persists,
normal response.
replace the board.
08
Service cannot be executed because
Make the necessary settings.
necessary settings haven’t been made.
09
Service cannot be executed because
Check the command format of and make
necessary settings haven’t been made the necessary settings.
in the command data.
0A
The specified action or transition number has already been registered.
0B
Cannot clear error because the cause
of the error still exists.
Execute the command again using an
action or transition number that hasn’t been
registered.
Eliminate the cause of the error and execute the ERROR CLEAR command.
30: Access right error
01
The access right is held by another
node.
(Either a peripheral device at the other
node is executing an SFC online edit,
or the other node is executing an
ACCESS RIGHT ACQUIRE or
ACCESS RIGHT FORCED ACQUIRE
command.)
Execute the command again after the
access right has been released.
(The command can be executed after the
ACCESS RIGHT FORCED ACQUIRE or
ACCESS RIGHT RELEASE command is
completed. Releasing the access right
might affect processes in progress at the
node that held the access right.)
40: Abort
01
Command was aborted with ABORT
command.
---
116
SECTION 7
Network Interconnections
This section describes the method used to connect multiple networks.
7-1
What is Network Interconnection?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
118
7-1-1
Interconnecting Controller Link Networks . . . . . . . . . . . . . . . . . . .
118
7-1-2
Interconnecting Different Types of Networks . . . . . . . . . . . . . . . . .
118
7-2
Routing Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
119
7-3
Setting Routing Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
121
7-3-1
121
Example Routing Table Settings . . . . . . . . . . . . . . . . . . . . . . . . . . .
117
Section 7-1
What is Network Interconnection?
7-1
What is Network Interconnection?
Network interconnection enables commands and responses for the message
service to be sent and received across multiple networks, including FA and
OA networks. The four networks listed below can be interconnected to
achieve this.
FA Networks
• Controller Link Networks
• SYSMAC NET Link Networks
• SYSMAC LINK Networks
OA Networks
7-1-1
Ethernet
Interconnecting Controller Link Networks
Controller Link Networks can be connected through CV-series PCs, CS-series
PCs, CJ-series PCs, or computers with FinsGateway.
Controller Link Network
CS/CJ-series,
C200HX/HG/HE, or
CV-series PC
IBM PC/AT or
compatible
Token Ring Controller Link Network
CV-series PC, CS/CJ-series
PC, or IBM computer with
FinsGateway (See note.)
Note A data bridge is created between Controller Link
IBM PC/AT or
compatible
Units/Boards mounted on the same PC or computer.
7-1-2
Interconnecting Different Types of Networks
CV-series PCs, CS-series PCs, or computers with FinsGateway can be used
to connect a Controller Link Network with a SYSMAC NET or SYSMAC LINK
Network.
Controller Link Network
CS/CJ-series,
C200HX/HG/HE or
CV-series PC
IBM PC/AT or
compatible
Ethernet
CV-series PC, CS/CJ-series
PC, or IBM computer with
FinsGateway (See note.)
Note A data and communications protocol gateway is created be-
tween a Controller Link Unit and a SYSMAC NET or SYSMAC
LINK Unit mounted on the same PC or computer.
Note
1. A bridge is used between Communications Units/Boards to connect the
same type of networks.
2. A gateway is used between Communications Units/Boards to connect different types of networks.
118
Section 7-2
Routing Tables
Bridge
Controller Link
PC
Gateway
Controller Link
Controller Link
PC
SYSMAC NET
Data
Data and communications
protocol gateway
Data
• Computer Bridges and Gateways: FinsGateway automatically implements
the bridge or gateway functionality. It does not need to be programmed by
the user. The FinsGateway, however, does not connect all networks. Refer
to the FinsGateway online help for details.
Computer
FinsGateway
Controller Link
Support Board
Controller Link
Controller Link
Support Board
Controller Link
• Communications across bridges or gateways can include up to three networks, 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 received
with a Controller Link, the maximum amount of data is limited by any network
the data passes through, i.e., the network with the smallest capacity will determine the limit.
If, for example, data passes through a SYSMAC LINK network as shown in
the figure, the amount of data sent and received from the Controller Link is
limited to 552 bytes (including the header) because the SYSMAC LINK Network can only handle that many bytes.
See the manual for the network you are using in order to determine the maximum amount of data for each network.
7-2
Routing Tables
Routing tables that define the communications path from the Controller Link
Unit on the local PC to the network connected to the destination PC must be
created in order to send and receive data across networks.
Creating Routing Tables
Routing tables consists of a local network table and a relay network table.
Local Network Table
The local network table lists the unit numbers and corresponding network
addresses for the Controller Link Unit and Support Board unit numbers. With
the Support Board, only one entry can be set in the table.
119
Section 7-2
Routing Tables
Unit number 04
Unit number 05
Unit number 06
Unit number 07
Example
Local network table
Local network address Unit number
Local network
Unit number
address
Network address 1
Network address 2
Network address 3
Network address 4
Note
1
04
2
05
3
06
4
07
1. The unit number is set between 00 and 15 using the rotary switch on the
front panel of CV-series, CS-series, and CJ-series Controller Link Units,
and is the same as the operating level for C200HX/HG/HE PCs. For the
Support Board, the unit number is 16 less that the unit address (i.e., the
Communications Unit number) set for the Board in the FinsGateway settings.
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 is
created.
Relay Network Table
A relay network table provides the node and network addresses corresponding to the initial relay point (first point the data must go to) en route to a target
network (end network) not directly connected to the local PC. The table traces
the route from the relay point to the end network.
Local node
Computer 1
Relay node
PC2
Node address 2
Unit number 0
Destination node
Node ad- PC4
dress 1
Node address 2
Unit number 1
Relay node
PC3
Node Node address 2
address
1
Node address 3
Node address 1
Network
address 2
Network address 1
Network
address 3
End network
Computer1 relay network table
End
network
Relay
network
2
1
3
3
1
3
PC2 (a) relay network table
Relay
node
Data first goes to node
address 3 at network
address 1 to reach
network address 3.
Note
PC3 (b) local network table
End
network
Relay
network
Relay
node
Local net
work ad
dress
Unit
number
3
2
2
2
0
Data then goes to node
address 2 at network address 2 to reach network
address 3.
3
1
We know from the
local network table
that the data goes
through local unit
number 1 to reach
network address 3.
Data goes to node
address 2 at net
work address 3,
i.e., the local net
work.
(1) The above example shows the routing tables required to send a message
from the personal computer to PC4. To send from PC4 to the personal
computer, similar routing table entries would be required.
(2) Refer to 7-3 Setting Routing Tables for a routing table setting example.
120
Section 7-3
Setting Routing Tables
7-3
Setting Routing Tables
This section describes routing table settings.
Routing tables are set through the FinsGateway, Controller Link Support Software, or CX-Programmer. This section describes setting procedures and setting details.
For specific procedures, see the FinsGateway online help, Controller Link
Support Software Operation Manual (W308,) or CX-Programmer User’s Manual.
7-3-1
Example Routing Table Settings
This section shows examples of routing table settings.
Example 1
The example below shows local network table settings when a Support Board
is mounted to a computer.
Computer
Unit number b
Controller Link Network address A
Local Network Table
Loc
SIOU
Netwk
unit #
No.
1
A
b
121
Section 7-3
Setting Routing Tables
Example 2
The following example show the settings for a relay network table connecting
three networks.
Relay Network Tables
PC 1
Network
address A
No.
End
Netwk PC ID
Node address a
1
2
B
C
PC 2
No.
End
Netwk
Node address c
1
C
PC 3
No.
End
Netwk
Node address d
1
2
A
C
PC ID
Relay
Netwk
Node
A
A
b
b
Relay
Netwk
Node
B
e
Node address b
Network
address B
PC 4
Network
address C
No.
Node address f
Node address e
1
PC 5
No.
Node address g
1
2
PC ID
B
B
End
Netwk PC ID
A
End
Netwk
A
B
Relay
Netwk
Relay
Netwk
B
PC ID
Relay
Netwk
C
C
Node
c
e
Node
c
Node
f
f
On closer examination of the relay network table for PC 3, we see that the
relay network is B and the relay node is c when network A is the destination,
and that the relay network is B and the relay node is e when network C is the
destination.
122
Section 7-3
Setting Routing Tables
Example 3
The network structure example in the figure below shows routing tables for all
nodes.
Unit 5
Node 1
SNT
SNT: SYSMAC NET LINK Unit
CLK: Controller Link Unit/ Board
SLK: SYSMAC LINK Unit
PC
(1)
Network 10
Unit 3
Node 4
Unit 4
Node 5
PC
(2)
Unit 2 CLK SNT
Node 3
SNT SLK
PC
(3)
Unit 7
Node 15
Network 20
Network 30
ComCLK puter
PC
(4)
CLK
Unit 0
Node 1
PC
(5)
SLK
Unit 1
Node 2
SLK
Unit 5
Node 5
PC
(6)
Unit 6
Node 10
Routing Tables on PC 1
Local Network Table
Loc
SIOU
No. Netwk
unit#
1
2
3
010
Relay Network Table
End
No. Netwk PC ID
Relay
Netwk
020
030
010
010
05
1
2
3
Node
004
005
Routing Tables on PC 2
Local Network Table
Loc
SIOU
No. Netwk
unit#
1
2
3
010
020
Relay Network Table
Relay
Netwk
Node
030
010
005
Relay Network Table
End
No. Netwk PC ID
Relay
Netwk
020
010
004
Relay
Netwk
Node
020
020
003
003
No.
03
02
1
2
3
End
Netwk
PC ID
Routing Tables on PC 3
Local Network Table
Loc
SIOU
No.
Netwk
unit#
1
2
3
010
030
04
07
1
2
3
Node
Routing Tables on Computer
Local Network Table
No.
1
2
3
Loc
Netwk
020
SIOU
unit#
00
Relay Network Table
No.
End
Netwk
1
2
3
010
030
PC ID
123
Section 7-3
Setting Routing Tables
Routing Tables on PC 4
Local Network Table
No.
1
2
3
Loc
Netwk
SIOU
unit#
020
01
Relay Network Table
End
No. Netwk
PC ID
1
2
3
010
030
Relay
Netwk
Node
020
020
003
003
Routing Tables on PC 5
Local Network Table
Loc
SIOU
No. Netwk
unit#
1
2
3
030
05
Relay Network Table
No.
1
2
3
End
Netwk
PC ID
010
020
Relay
Netwk
Node
030
030
015
015
Routing Tables on PC 6
Local Network Table
Loc
SIOU
No. Netwk
unit#
1
2
3
124
030
06
Relay Network Table
No.
1
2
3
End
Netwk
010
020
PC ID
Relay
Netwk
Node
030
030
015
015
SECTION 8
Communications Timing
This section explains details on Controller Link Network communications. Refer to this section for network
communications that require accurate communications timing.
8-1
8-2
8-3
8-4
Network Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
126
8-1-1
Controller Link Communications . . . . . . . . . . . . . . . . . . . . . . . . . .
126
8-1-2
Communications Cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
126
8-1-3
Network Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
127
8-1-4
Specifying Network Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . .
128
Communications Cycle Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
128
8-2-1
Active Data Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
128
8-2-2
Inactive Data Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
130
8-2-3
Maximum Delay for Line Disconnections in Token Ring Mode. . .
131
Data Link I/O Response Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
133
8-3-1
Computer to PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
133
8-3-2
PC to Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
134
Message Service Delay Times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
135
125
Section 8-1
Network Parameters
8-1
Network Parameters
This section explains how to use Controller Link Network communications and
how to adjust the network parameters to match the system.
8-1-1
Controller Link Communications
The token bus method is used for communications in the Controller Link Network. With this method, a piece of data called a “token” is passed between the
various nodes in the network. The only node that can transmit data at any
given time is the one that currently holds the token, thereby preventing interferences to data transmission within the network.
The token travels from smaller node addresses to larger, and then back to the
beginning again, without regard to the order in which the nodes are connected. If the node has data to send, it will attach the data to the token and
send them together. If the node has no data to send, it will pass the token to
the next node.
For Wired or Optical Networks, or Optical Ring Networks in Token Bus Mode,
a token is passed between nodes connected in a daisy-chain bus called a
token bus. With an Optical Ring Network in Token Bus Mode, this is called a
token ring because the bus is connected in a ring. With a token ring, two
transmission paths can be used (transmission path duplication) to create a
more robust system.
Polling Node
Each Controller Link Network always has a Unit that controls communications
within the network. This Unit is called the “polling node.” Normally, the node
that has the smallest node address in the network is the polling node. All Units
at nodes other than the polling node are called “polled nodes.” The polling
node controls the token, checks the network, and performs other relevant
tasks. Should the polling node break down, the node with the next smallest
node address is automatically selected as the polling node to prevent the
entire network from shutting down.
Note
8-1-2
There are times when the node with the smallest node address will not be the
polling node depending on the order in which the nodes are started, models,
settings, and node status.
Communications Cycle
The “communications cycle” is the cycle for repeating Controller Link Network
processing. The time required for one communications cycle is called the
“communications cycle time,” and each communications cycle is divided into a
“token cycle” and a “polling cycle” as shown in the following diagram.
Communications cycle
Token cycle
Token Cycle
126
Polling cycle
Communications cycle
Token cycle
Polling cycle
The token cycle is the period during which the token is sent from the polling
node to the nodes in order and returned to the polling node. During this cycle,
any nodes with data to send will send that data. Data link data will also be
sent during this cycle.
Section 8-1
Network Parameters
Polling Cycle
The polling cycle is the period during which the polling node checks the status
of the nodes in the network. The polling node checks whether each node is
actually participating in the network, whether there are any new nodes participating, and so on, and notifies all the nodes of the results of the check.
Refresh Cycle Time
The refresh cycle time is the time, during data link operation, from when the
contents of the data link areas are refreshed until the next time they are
refreshed. The refresh cycle time will vary depending on factors such as the
communications cycle time, the number of data link words, and so on.
The refresh cycle time value can be displayed by the Controller Link Support
Software’s data link status monitoring function. There is no refresh cycle time
for the Support Board, because the data link areas are constantly refreshed
by the data link data that is received. When the refresh cycle time for the Support Board is read by the Controller Link Support Software, therefore, the
value will always be 0.
8-1-3
Network Parameters
Network parameters are also used to control network operations. Network
parameters are read from the polling node and distributed to all other nodes
when the Controller Link Network is started. In this way, all nodes on the network always have the same network parameter settings. If nodes are connected to the network halfway during network operation, the network
parameter settings will also be distributed to these nodes when they are connected. The following three network parameters can be specified.
Maximum Node Address
This parameter specifies the maximum node address of nodes to be checked
by the polling node. The default is 32 for Wired Networks and 62 for Optical
Ring Networks Reducing the setting of this parameter reduces the number of
nodes checked by the polling node and can thus avoids unnecessary check
operations. However, if the network contains nodes with node addresses
greater than the setting of the parameter, these nodes will not be connected to
the network.
No. of Polled Nodes Per
Communications Cycle
This parameter specifies the number of nodes to be checked (polled) by the
polling node during each polling cycle. The default is 4. Setting this parameter
to a high value increases the communications cycle time, but reduces the time
required to recognize that nodes have been removed from or added to the
network. Reducing the setting of this parameter shortens the communications
cycle time but delays a network response when a node is disconnected from
or connected to the network.
No. of Event-frames per
Communications Cycle
This parameter specifies the maximum number of event frames (communications other than data links, such as message service transmissions) that can
be transferred 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 cycle
time but allows for more event communications such as the message service.
Too small a parameter value restricts event communications, resulting in an
error.
See 8-2 Communications Cycle Time for the effects of network parameters on
communication cycle times.
127
Section 8-2
Communications Cycle Time
8-1-4
Specifying Network Parameters
The network parameters can be specified from the Controller Link Support
Software. This section describes only the allowable setting range for each network parameter. 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.
Note
Network parameter
Maximum node address
Setting range
2 to 62
Default value
62 (See note 1.)
Number of polled nodes per communications cycle
1 to 61 (See note
2.)
4
No. of event-frames per communications
cycle
16 to 238
35
The default value is 32 for Wired Controller Link Support Boards and 62 for
Optical Ring Controller Link Support Boards.
The network parameters become valid immediately after being set.
Note
1. Always stop the data link before changing network parameters.
2. Specify a value for the maximum node address that is equal to or greater
than the maximum node address in the Controller Link Network.
8-2
Communications Cycle Time
This section describes how to calculate the communications cycle time. When
accurate timing is required, it is necessary to understand the time required for
sending and receiving data link data and the timing for exchanging data.
8-2-1
Active Data Links
The following equations are used to calculate the communications cycle time
when data links are operating. (The communications cycle time will vary
somewhat depending on the baud rate and the conditions at that particular
time.)
Wired Networks
Baud rate
2 Mbps
Equation
10 × A + 600 × B + 290 × C + 320 × D + 4 × E + 3,290 (µs)
1 Mbps
500 Kbps
18 × A + 1,150 × B + 370 × C + 360 × D + 8 × E + 3,770 (µs)
34 × A + 2,260 × B + 530 × C + 440 × D + 16 × E + 4,730 (µs)
Optical Networks
Baud rate
2 Mbps
(Fixed)
Note
128
Equation
Token Ring Mode
9.1 × A + 1,740 × B + 960 × C + 1,100 × D + 4 × E + 2 × F+ 4,800 (µs)
Token Bus Mode
9.1 × A + 1,300 × B + 290 × C + 320 × D + 4 × E + 2 × F+ 2,290 (µs)
The meanings of the variables in the above formulas are as follows:
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 communications cycle
(value specified in the network parameters)
C: Number of nodes connected to the network
Section 8-2
Communications Cycle Time
D: Number of nodes that send messages during the
communications cycle
E: Total number of bytes in messages transmitted during the
communications cycle
F: Extra communications time for long-distance cable connections.
If L is the cable length in km, then F = 7 × L µs for H-PCF cable
and F = 5 × L µs for GI cable.
Calculation Example for
Wired Networks
Communications conditions are as follows:
Type:
Wired
Transmission medium:
Twisted-pair cables
Baud rate:
2 Mbps
Network parameters:
Defaults
Max node address:
32
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:
B:
C:
D:
E:
8,000
4
8
2
4,024
The communications cycle time is thus as follows:
10 × 8,000 + 600 × 4 + 290 × 8 + 320 × 2 + 4 × 4,024 + 3,290 = 104,746 (µs)
≅ 105 (ms)
Calculation Example for
Optical Ring Networks
with H-PCF Cable
Communications conditions are as follows:
Type:
Optical Ring
Transmission medium:
H-PCF cable
Transmission distance:
8 km
Baud rate:
2 Mbps (fixed)
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:
B:
C:
D:
8,000
4
8
2
129
Section 8-2
Communications Cycle Time
E: 4,024
F: 7 × 8
The communications cycle time for 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)
The communications cycle time for Token Bus Mode is thus 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)
8-2-2
Inactive Data Links
The following equations are used to calculate the communications cycle time
when the data links are inactive. (The communications cycle time will vary
somewhat depending on the baud rate and the conditions at that particular
time.)
Wired Networks
Baud rate
Equation
2 Mbps
1 Mbps
600 × B + 110 × C + 320 × D + 4 × E + 2,290 (µs)
1,150 × B + 150 × C + 360 × D + 8 × E + 2,690 (µs)
500 Kbps
2,260 × B + 230 × C + 440 × D + 16 × E + 3,490 (µs)
Optical Ring Networks
Baud rate
2 Mbps
(fixed)
Note
Calculation Example for
Wired Networks
Equation
Token Ring Mode
1,740 × B + 450 × C +1,100 × D + 4 × E + 2 × F + 3,000 (µs)
Token Bus Mode
1,300 × B + 110 × C + 320 × D + 4 × E + 2 × F + 1,800 (µs)
B: Number of polled nodes per communications cycle
(value specified in the network parameter)
C: Number of nodes connected to network
D: Number of nodes that send messages during the
communications cycle
E: Total number of bytes in messages transmitted during the
communications cycle
F: Extra communications time for long-distance cable connections.
If L is the cable length in km, then F = 7 × L µs for H-PCF cable
and F = 5 × L µs for GI cable.
Communications conditions are as follows:
Type:
Wired
Transmission medium:
Twisted-pair cables
Baud rate:
2 Mbps
Network parameters:
Defaults
Max node address:
32
Polled nodes per comm cycle:
4
Event-frames per comm cycle: 35
130
Network configuration:
8 nodes
Nodes that send messages:
2 nodes
Bytes in all messages sent:
2,012 × 2 bytes
Section 8-2
Communications Cycle Time
In this example, B to E in the equation have the following values.
B:
C:
D:
E:
4
8
2
4,024
The communications cycle time is thus as follows:
600 × 4 + 110 × 8 + 320 × 2 + 4 × 4,024 + 2,290 = 22,306 (µs)
≅ 22 (ms)
Calculation Example for
Optical Ring Networks
with H-PCF Cable
Communications conditions are as follows:
Type:
Optical Ring
Transmission medium:
H-PCF cable
Transmission distance:
8 km
Baud rate:
2 Mbps (fixed)
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 F in the equation have the following values.
B:
C:
D:
E:
F:
4
8
2
4,024
7×8
The communications cycle time for 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)
The communications cycle time for 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)
8-2-3
Maximum Delay for Line Disconnections in Token Ring Mode
Although the duplicated transmission lines used in Token Ring Mode for Optical Ring Networks will ensure that communications continue even if the transmission line is broken in one location, the communications cycle time will be
affected.
The data that is received first from the SL1 or SL2 reception interfaces is actually used, but the data that would normally be received first may be lost. The
difference in time to receive the same data on SL1 and SL2 is thus the delay
that can occur for line disconnections.
This delay results as the token is passed between nodes. The delay for the
entire network will thus be the total of all the delays between each node pair,
and the total delay time will increase the communications cycle time.
131
Section 8-2
Communications Cycle Time
With a Controller Link Network, the token is moved for the following.
• Normal token passing
• Token passing for new node checks by the polling node (depends on the
number of polled nodes set in the network parameters)
• Token passing for responses to messages.
Although the actually delay time will depend on the location of the line disconnection point, differences in the time required to receive the token can be
reduced by setting node addresses in order on the network.
Maximum Communications Cycle Time Delay with Node Addresses Set in Order
The maximum delay in the communications cycle time can be calculated as
follows if the node addresses are set in the order that the nodes are connected in the network.
A: Number of polled nodes per communications cycle
(value specified in the network parameter)
B: Number of nodes that send messages during the communications cycle
C: Number of nodes connected to network
D: Extra communications time for long-distance cable connections.
If L is the cable length in km, then F = 7 × L µs for H-PCF cable and
F = 5 × L µs for GI cable.
(A × 4 + B × 2 + 1) × (3 × C + D) (µs)
Calculation Example for
Optical Ring Networks
with H-PCF Cable
Communications conditions are as follows:
Type:
Optical Ring
Transmission medium:
H-PCF cable
Transmission distance:
8 km
Baud rate:
2 Mbps (fixed)
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 F in the equation have the following values.
A:
B:
C:
D:
4
8
2
7×8
The communications cycle time delay for Token Ring Mode is thus as follows:
(4 × 4 +2 × 2 + 1) × (3 × 8 + 7 × 8) = 1,680 (µs)
≅ 1.7 (ms)
The percentage change for active data links would be as follows (refer to Calculation Example for Optical Ring Networks with H-PCF Cable under 8-2-1
Active Data Links):
(111 + 1.7)/111 × 100
≅ 101.5 (%)
The percentage change for inactive data links would be as follows (refer to
Calculation Example for Optical Ring Networks with H-PCF Cable under 8-2-2
Inactive Data Links):
132
Section 8-3
Data Link I/O Response Time
(32 + 1.7)/32 × 100
≅ 105.3 (%)
8-3
Data Link I/O Response Time
The data links of the Controller Link Support Board require a slight time delay
from the time the data link area of one node is changed until this change is
reflected in the data link area at another node. This time delay is called the
data link I/O response time.
8-3-1
Computer to PC
In the following diagram illustrating the maximum data link I/O response time,
a CS-series PC is used for the PC (#2) and the PC’s cycle time is greater than
or equal to the communications cycle time.
Computer at node #1
User application
(ClkWriteDatalink)
Send processing (FinsGateway)
(*)
Late
Communications
cycle time
Data link transmissions
I/O refresh
Data exchange
PC at node #2
1 cycle
Output ON delay
Output device
Data link I/O response time
There are two points shown in the diagram above where processing is
delayed.
1,2,3...
1. Data exchange occurs just after the computer at node #1 passes the token
that makes it the polling node, causing a delay of up to one communications cycle time before the data is transferred in data link processing.
2. The data transferred in data link processing arrives at the PC at node #2
after data exchange, so the data will not be read into the PC until the next
data exchange, causing a delay of up to one cycle. (If the cycle time of the
PC at node #2 is longer than the communications cycle time, the delay
would be approximately two cycles.)
The maximum number of words that can be transferred in one data exchange
is 3,700 words for the CVM1 and CV-series PCs and 7,800 words for the CSseries and CJ-series PCs.
133
Section 8-3
Data Link I/O Response Time
Note
1. Noise may increase I/O delays.
2. The data send processing time for the area marked by the asterisk (*) in
the diagram will be affected by the processing capacity of the computer
that is used.
3. The communications cycle time may fluctuate.
4. For details regarding the time required for data exchanges between the
Controller Link Unit and the PC, refer to the Controller Link Units Operation
Manual (W309 or W370).
8-3-2
PC to Computer
In the following diagram illustrating the maximum data link I/O response time,
a CS-series PC is used for the PC (#2) and the PC’s cycle time is greater than
or equal to the communications cycle time.
Input
Input device
I/O refresh
Input ON response time
Data exchange
1
1 cycle
Late
Computer at node #1
Program
2
Late
Communications
cycle time
Data link
transmissions
(*)
3
Receive processing
(FinsGateway)
(ClkReadDatalink)
User application
PC at node #2
Data link I/O response time
There are three points shown in the diagram above where processing is
delayed, increasing the data link I/O response time.
1,2,3...
Note
134
1. The input arrives in the PC just after I/O refreshing, causing a delay of up
to one cycle before the input is read into the PC.
2. Data exchange occurs just after the PC at node #2 passes the token that
makes it the polling node, causing a delay of up to one communications cycle time before the data is transferred in data link processing.
3. The data arrives at the Data Link Area of the Support Board mounted at
the computer at node #1, but processing is delayed until the user application executes the ClkReadDatalink library function. This delay will vary depending on the contents of the user application.
1. Noise may increase I/O delays.
Section 8-4
Message Service Delay Times
2. The data send processing time for the area marked by the asterisk (*) in
the diagram will be affected by the processing capacity of the computer
that is used.
3. The communications cycle time may fluctuate.
4. Refer to the Controller Link Units Operation Manual (W309) for details on
the time required for data exchanges between the Controller Link Unit and
the PC.
8-4
Message Service Delay Times
The following diagram illustrates the maximum message service transmission
delay time. In this example, the MEMORY AREA READ FINS command is
sent to the PC at node #2 (a CS-series PC) by the user application at the
computer at node #1.
Computer at
node #1
User application
(ClkRecvFins)
(ClkSendFins)
Receive processing at
node #1 (response)
Send processing at node
#1 (command)
Transmission delay
(response)
Communications cycle
Transmission delay
(command)
Send processing at node
#2 (response)
Receive processing at
node #2 (command)
PC at node #2
Maximum transmission delay
Maximum transmission delay time = Send processing (node #1) + Communications cycle time + Transmission delay time (for command) + Receive processing (node #2) + PC processing time (node #2) + Send processing (node
#2) + Communications cycle time + Transmission delay time (for response) +
Receive processing (node #1)
Send/Receive Processing at Node #1
Depends on the processing capacity of the computer that is used.
Communications Cycle Time
See 8-2 Communications Cycle Time (on page 128).
Transmission Delay Time
Transmission delay time varies with the baud rate.
Baud rate
Transmission delay time
2 Mbps
1 Mbps
Number of words transferred × 0.008 + 0.112 ms
Number of words transferred × 0.016 + 0.224 ms
500 Kbps
Number of words transferred × 0.032 + 0.448 ms
135
Message Service Delay Times
Section 8-4
Receive Processing at Node #2
Number of words transferred × 0.00125 + 2.3 ms
Send Processing at Node #2
Number of words transferred × 0.00125 + 3.0 ms
Note
136
1. The I/O response time can increase due to noise or restrictions on the
number of frames that can be transmitted while data links are operating.
2. Refer to the Controller Link Units Operation Manual (W309 or W370) for
details on the time from reception at the Controller Link Unit until transmission.
SECTION 9
Troubleshooting and Maintenance
This section provides information on troubleshooting errors that occur during Controller Link Support Board
operation, as well as daily inspection, cleaning, and other maintenance procedures.
9-1
9-2
9-3
9-4
9-5
Troubleshooting Using Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
138
9-1-1
Using the RUN, ERR and INS Indicators . . . . . . . . . . . . . . . . . . . .
138
9-1-2
Troubleshooting with LNK Indicators . . . . . . . . . . . . . . . . . . . . . . .
140
Status Information and Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . .
143
9-2-1
Troubleshooting with the ClkGetNetworkStatus Function . . . . . . .
143
9-2-2
Error Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
146
Error Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
148
9-3-1
Error Log Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
148
9-3-2
Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
149
9-3-3
Reading and Clearing Error Logs . . . . . . . . . . . . . . . . . . . . . . . . . .
153
Cleaning and Inspection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
154
9-4-1
Cleaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
154
9-4-2
Inspection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
154
Handling Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
155
9-5-1
Replacing the Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
155
9-5-2
Replacing the Board. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
155
137
Section 9-1
Troubleshooting Using Indicators
9-1
Troubleshooting Using Indicators
This section describes the errors shown by the Controller Link Support Board
indicators and possible remedies.
Optical Ring System
(H-PCF Cable and GI Cable)
Note
Wired System
Name
RUN
Status
Lit
Description
The Board is operating normally.
ERR
INS
Lit
Lit
An error has occurred.
Participating in network.
LNK
Lit
Flashing
Sending data link (participating in data link)
Error in the data link table settings.
PS)
TER
Lit
Lit
Backup power supply is ON.
Terminating resistance switch is ON (resistance is connected).
1. The P/S indicator is mounted to the Optical Ring Units only.
2. The TER indicator is mounted to the Wired Units only.
9-1-1
Using the RUN, ERR and INS Indicators
The Controller Link Support Board’s RUN, ERR, and INS indicators can be
used to check whether Controller Link Support Board startup and Network
participation are operating normally.
Note
Be sure to turn OFF the power to the computer before performing any of the
following.
• Disconnecting the Board or connectors.
• Securing Board or connectors.
• Setting hardware switches.
Indicators
RUN ERR INS
Lit
Not lit Lit
Not lit Lit
---
Error
history
Probable cause
Probable remedy
---
Unit operating normally; Network participation normal.
---
---
The Controller Link Support Board is
faulty.
If the ERC indicator still lights when the
Board is mounted on another computer,
replace the Controller Link Support Board.
The setting of the Wired Network 62 Node Select the Max Node Number set 62
Enable Bit (i.e., the Max Node Number set option in the driver properties and restart
CLKPCI_UNIT.
62 option) is not set correctly.
The Wired Network 62 Node Enable Bit is Set the node address temporarily to 32 or
less, join the network, and change the
ON (i.e., the Max Node Number set 62
maximum node address to 62 in the netoption is selected) and the node
address set for the local node is larger work parameters using the CX-Net or the
FinsGateway manually set data link setting
than the maximum node address
backed up in EEPROM in the Board. program. Once this has been done, set the
node address to the desired value.
138
Section 9-1
Troubleshooting Using Indicators
Indicators
RUN ERR INS
Error
history
Probable cause
Not lit Not lit Not lit ---
Power is not being supplied correctly to
the computer.
The Controller Link Support Board has
become loose.
The Controller Link Support Board is
mounted in the wrong slot.
The Controller Link Support Board is
faulty.
Lit
Lit
Not lit 0211 Hex
The same node address is being used by
two different Units.
The Board is connected to a SYSMAC
LINK network.
Lit
Lit
---
Routing table setting error.
021A Hex
Probable remedy
Check the power supply voltage and supply at the recommended voltage.
Secure the Controller Link Support Board
firmly.
Refer to the Installation Guide and mount
the Board correctly.
If the indicators do not light when the
Board is mounted in another computer,
replace the Controller Link Support Board.
Reset so that each node address is used
only once within the same Network.
Check the networks and correct the cable
connections.
Reset the routing table correctly, referring
to 7-3 Setting Routing Tables. When no
routing table is being used, delete the routing table.
There is an error in the data link table set- When using data links, refer to 5-2 Setting
tings.
Data Links and correct the tables. When
not using data links, delete the tables.
EEPROM error
Lit
---
Not lit --021A Hex
Refer to 9-2 Status Information and Troubleshooting, correct the data where the
error has occurred, and reset the Board. If
the error occurs again, replace the Controller Link Support Board.
Cables are not connected correctly.
Check the cable connections and reconnect correctly.
The node address is larger than the maxi- Either reset the maximum node address
using the Controller Link Support Software
mum node address set for the network
parameters.
or reset the node address to below the
maximum.
---
No other nodes exist.
Make sure that 2 or more nodes exist
within the Network.
---
No node has been set as a polling node.
Refer to Installation Guide and set at least
one polling node.
(A Controller Link Support Board should
normally be set as the polling node.)
139
Section 9-1
Troubleshooting Using Indicators
9-1-2
Troubleshooting with LNK Indicators
Data Link Cannot be
Started
The following table describes the LNK indicators at the startup node and their
use in troubleshooting when a data link cannot be started.
Starting a data link depends on the Controller Link Support Board operating
normally and participating in the Network. Refer to 9-1-1 Using the RUN, ERR
and INS Indicators earlier in this section and check Board operation before
using the following table.
Indicators
LNK
Lit
Flashing
Not lit
Probable cause
Data link operating normally.
There is an error in the data link tables.
Probable remedy
--When the ERR indicator is flashing, reset the data
link tables.
When manual setting is used, either data link tables Refer to 5-2-2 Manual Setting and set data link
have not been created for the startup node or there tables for the startup node.
is an error in the data link tables.
Manually set data links are already operating on the Refer to 9-5 Handling Precautions.
same Network.
Automatically set data links are already operating on Refer to 9-5 Handling Precautions.
the same Network.
Node Cannot Participate
in Data Link
Indicators
LNK
Lit
Flashing
Not lit
Probable cause
Probable remedy
Data link operating normally.
When manual setting was used, there is an error in
the data link table.
For manual setting, there are no data link tables set
for the local node.
For automatic setting, the startup node is not set to
participate in the data links.
--Refer to 5-2-2 Manual Setting and reset the data link
table.
Set data link tables for the local node.
Data Links Cannot be
Stopped
Not lit
140
Stop the data links, reset the parameters in the startup node’s DM Area, and then restart the data link.
The Controller Link Support Board cannot become
the start-up node for automatic setting, so set on the
PC to which the Controller Link Unit is mounted. For
details refer to the Controller Link Units Operation
Manual (W309).
The following explanation describes how to use the LNK indicator when the
data links cannot be stopped. Stopping the data links depends on the Controller Link Support Board operating normally and participating in the Network.
Read the above explanations before attempting to stop operation.
Note
Indicators
LNK
The following table describes the LNK indicators when a node cannot participate in the data links.
Data link participation depends on the Controller Link Support Board operating normally and participating in the Network. Refer to 9-1-1 Using the RUN,
ERR and INS Indicators earlier in this section and check Unit operation before
using the following table.
Stop the data link from the node at which the LNK indicator is flashing (indicating active data links). Data links cannot be stopped from nodes which do
not have active data links.
Probable cause
Data link stopped normally.
Probable remedy
---
Section 9-1
Troubleshooting Using Indicators
Troubleshooting of Other Errors
To configure a network that uses a node address higher than 32, all nodes
must be CS1W-CLK21-V1, CJ1W-CLK21-V1, CS1W-CLK23, CJ1W-CLK23,
3G8F7-CLK21-EV1, or 3G8F7-CLK23-E. The Wired Network 62 Node Enable
Bit in the DM Parameters Area must also be turned ON (62 nodes max.) for all
nodes. (For Controller Link Support Boards, select the Max Node Number set
62 option in the driver properties.) If the nodes are set differently, the network
will not be configured correctly. If the settings are incorrect, the following problems will occur.
Configuring a Network with 33 Nodes or More
Problem
Status
Cause and remedy
The ERC (ERR) indicator is
ON in the CS1W-CLK21V1, CJ1W-CLK21-V1,
CS1W-CLK23, CJ1WCLK23, 3G8F7-CLK21EV1, or 3G8F7-CLK23-E
and a node address higher
than 32 is set.
The Wired Network 62 Node Enable Bit in the DM Parameters Area
is turned OFF. Turn ON the Wired Network 62 Node Enable Bit and
then turn the power supply OFF and ON again.
For a Controller Link Support Board for PCI Bus, select the Max
Node Number set 62 option and restart CLKPCI_UNIT.
The ERC indicator is ON in
the C200HW-CLK21,
CQM1H-CLK21, CVM1CLK21, CS1W-CLK21,
CJ1W-CLK21, or 3G8F7CLK21 and a node address
higher than 32 is set.
The node is not
The INS indicator is ON for
present in the network some nodes in the same
(ERC (ERR) indicanetwork. Those nodes are
tor: OFF
C200HW-CLK21, CQM1HRUN indicator: ON
CLK21, CVM1-CLK21,
INS indicator: OFF)
CS1W-CLK21, CJ1WCLK21, or 3G8F7-CLK21.
The Units that can be used to configure a network that uses a node
address higher than 32 are the CS1W-CLK21-V1, CJ1W-CLK21-V1,
CS1W-CLK23, CJ1W-CLK23, 3G8F7-CLK21-EV1, and 3G8F7CLK23-E only. Either configure the network using compatible Units
and Boards, or split the network into two separate networks.
The node is not
present in the network.
(ERC (ERR) indicator: ON
RUN indicator: OFF
INS indicator: OFF)
The INS indicator is ON for
some nodes in the same
network. Those nodes are
CS1W-CLK21-V1, CJ1WCLK21-V1, CS1W-CLK23,
CJ1W-CLK23, 3G8F73G8F7-CLK21-EV1, or
3G8F7-CLK23-E.
The Wired Network 62 Node Enable Bit in the DM Parameters Area
of the polling node (CS1W-CLK21-V1 or CJ1W-CLK21-V1, CS1WCLK23, CJ1W-CLK23 with INS indicator ON) is OFF. Turn ON the
Wired Network 62 Node Enable Bit, then turn the power supply OFF
and ON again.
For a Controller Link Support Board for PCI Bus, select the Max
Node Number set 62 option and restart CLKPCI_UNIT.
The maximum number of nodes set in the network parameters is
less than the number of nodes present in the network.
Use CX-Net or the Controller Link Support Software to read the network parameters, and check the maximum number of nodes setting.
Set the maximum number of nodes to a number that is the same or
larger than the number of nodes in the network.
The maximum number The polling node is a
The Units that can be used to configure a network that uses a node
of nodes in the netC200HW-CLK21, CQM1H- address higher than 32 are the CS1W-CLK21-V1, CJ1W-CLK21-V1,
work is set to 32.
CLK21, CVM1-CLK21,
CS1W-CLK23, CJ1W-CLK23, 3G8F7-CLK21-EV1, and 3G8F7CS1W-CLK21, CJ1WCLK23-E only. Either configure the network using compatible Units
CLK21, or 3G8F7-CLK21. and Boards, or split the network into two separate networks.
The polling node is a
The Wired Network 62 Node Enable Bit in the DM Parameters Area
CS1W-CLK21-V1, CJ1W- of the polling node (CS1W-CLK21-V1 or CJ1W-CLK21-V1, CS1WCLK21-V1, CS1W-CLK23, CLK23, CJ1W-CLK23 with INS indicator ON) is OFF. Turn ON the
CJ1W-CLK23, 3G8F7Wired Network 62 Node Enable Bit, then turn the power supply OFF
3G8F7-CLK21-EV1, or
and ON again.
3G8F7-CLK23-E.
For a Controller Link Support Board for PCI Bus, select the Max
Node Number set 62 option and restart CLKPCI_UNIT.
141
Section 9-1
Troubleshooting Using Indicators
Problem
The data link status is
showing statuses of
32 nodes only.
Status
The data link status storage area is set to default
settings, and the data link
status storage format specification in the DM Parameters Area is set to the 8-bit
format.
Cause and remedy
The default area for storing data link status is the Special I/O Unit
Area. The data for only node addresses 1 to 32 is reflected when the
data link status storage format specification is set to 8 bits. Change
to the 4-bit format or specify a different area for storing data link status.
The polling node is a
C200HW-CLK21, CQM1HCLK21, CVM1-CLK21,
CS1W-CLK21, CJ1WCLK21, or 3G8F7-CLK21.
The Units that can be used to configure a network of a network that
uses a node address higher than 32 are the CS1W-CLK21-V1,
CJ1W-CLK21-V1, CS1W-CLK23, CJ1W-CLK23, 3G8F7-CLK21EV1, and 3G8F7-CLK23-E only. Either configure the network using
compatible Units and Boards, or split the network into two separate
networks.
The polling node is a
CS1W-CLK21-V1, CJ1WCLK-V1, CS1W-CLK23,
CJ1W-CLK23, 3G8F7CLK21-EV1, or 3G8F7CLK23-E.
Error occurs when
transferring data link
tables.
The data link status is
showing statuses of
32 nodes only.
The Wired Network 62 Node Enable Bit in the DM Parameters Area
of the polling node (CS1W-CLK21-V1 or CJ1W-CLK21-V1, CS1WCLK23, CJ1W-CLK23 with INS indicator ON) is OFF. Turn ON the
Wired Network 62 Node Enable Bit, then turn the power supply OFF
and ON again.
For a Controller Link Support Board for PCI Bus, select the Max
Node Number set 62 option and restart CLKPCI_UNIT.
The data link table being
The Units that can be used to configure a network of a network that
transferred is for a
uses a node address higher than 32 are the CS1W-CLK21-V1,
C200HW-CLK21, CQM1H- CJ1W-CLK21-V1, CS1W-CLK23, CJ1W-CLK23, 3G8F7-CLK21CLK21, CVM1-CLK21,
EV1, and 3G8F7-CLK23-E only. Either configure the network using
CS1W-CLK21, CJ1Wcompatible Units and Boards, or split the network into two separate
CLK21, or 3G8F7-CLK21. networks.
The polling node is a
C200HW-CLK21, CQM1HCLK21, CVM1-CLK21,
CS1W-CLK21, CJ1WCLK21, or 3G8F7-CLK21.
The polling node is a
The Wired Network 62 Node Enable Bit in the DM Parameters Area
CS1W-CLK21-V1, CJ1W- of the polling node (CS1W-CLK21-V1 or CJ1W-CLK21-V1, CS1WCLK21-V1, CS1W-CLK23, CLK23, CJ1W-CLK23 with INS indicator ON) is OFF. Turn ON the
CJ1W-CLK23, 3G8F7Wired Network 62 Node Enable Bit, then turn the power supply OFF
3G8F7-CLK21-EV1, or
and ON again.
3G8F7-CLK23-E.
For a Controller Link Support Board for PCI Bus, select the Max
Node Number set 62 option and restart CLKPCI_UNIT.
Configuring a Network with 32 Nodes or Less
Problem
The node is not present in the
network.
(ERC (ERR) indicator: ON
RUN indicator: OFF
INS indicator: OFF)
The maximum number of
nodes in the network is set to
62.
Status
A CS1W-CLK21-V1, CJ1WCLK21-V1, CS1W-CLK23,
CJ1W-CLK23, 3G8F7-CLK21EV1, or 3G8F7-CLK23-E is
present in the network.
The data link status is showing The corresponding node is a
statuses for 62 nodes.
CS1W-CLK21-V1, CJ1WThe network participation sta- CLK21-V1, CS1W-CLK23,
tus is showing statuses for 62 CJ1W-CLK23, 3G8F7-CLK21EV1, or 3G8F7-CLK23-E.
nodes.
142
Cause and Remedy
The node with the ERC (ERR) Reset the node address between 1 and 32, then turn the
indicator ON is set to a node
power OFF and ON again.
address of 33 or higher.
The Wired Network 62 Node Enable Bit in the DM
Parameters Area of the CS1W-CLK21-V1 or CJ1WCLK21-V1, CS1W-CLK23, CJ1W-CLK23 is ON. Turn
OFF the Wired Network 62 Node Enable Bit, then turn
the power supply OFF and ON again.
For a Controller Link Support Board for PCI Bus, select
the Max Node Number set 62 option and restart
CLKPCI_UNIT.
Section 9-2
Status Information and Troubleshooting
9-2
Status Information and Troubleshooting
The Controller Link Support Board contains status information which reflects
the current status of communications and the Board. This status information
can be read using the STATUS READ or DATA LINK AREA READ FINS command. The cause of the error can be found by reading the status information.
This section explains the contents accessed by the ClkGetNetworkStatus
function and tells how to troubleshoot error information obtained.
9-2-1
Troubleshooting with the ClkGetNetworkStatus Function
The following network status is read by ClkGetNetworkStatus().
Type
BYTE
Variable name
byConnectionMethod
Contents
Wired/optical discrimination, transmission path form, etc.
Bit
−: Not specified.
Maximum number of nodes supported
00: 32 nodes
01: 64 nodes
Transmission path
0: Token bus
1: Token ring
Connection type
0: Wired
1: Optical ring
Note When optical and optical ring connections are combined, the maximum number of nodes supported will be given as 62 nodes for an optical ring connection even if the maximum number of nodes is 32.
BYTE
byMyNodeAddr
Local unit address
Stores the local unit address set for the Controller Link Board.
BYTE
byMyUnitAddr
Local unit address
Stores the local unit address set for the Controller Link Board.
BYTE
byMyNetAddr
Local network address
Stores the local network address set for the Controller Link Board.
BYTE
abyNodeList[32]
Network participation status
Stores a list of the nodes participating in the network.
Node Participation Information
Bit
[0]
[1]
[2]
[30]
[31]
Node 1
Node 3
Reserved
Node 2
Node 5
Node 4
Node 61
Reserved
Node 60
Node 62
0: Not participating in network
1: Participating in network
0: Normal disconnection
1: Error disconnection
(when not participating)
0: Normal
1: No response to polling.
Note For Wired Networks set to a maximum of 32 nodes, the above
information is valid through node 32 (lower 4 bytes of
abyNodeList[16]).
WORD
wComunicationCycleTime
BYTE
byPollingNodeAddr
BYTE
byStatus1
Communications cycle time
Stores the current value of the communications cycle time. (unit: 0.1 ms)
Polling node address
Stores the node address of the current polling node.
Reserved area
Stores undetermined data.
143
Section 9-2
Status Information and Troubleshooting
Type
BYTE
Variable name
byStatus2
Contents
Baud rate, power supply status, terminating resistance setting status
For Wired Systems, stores the set baud rate and the setting of the
terminating resistance switch.
For Optical Ring System, stores the power supply status.
Bit
Wired System
0: Terminating resistance switch OFF
1: Terminating resistance switch ON
Baud rate
0x1: 2 Mbits/s
0x2: 1 Mbits/s
0x3: 500 kbits/s
BYTE
byStatus3
Optical System
0: No backup power supply
1: Backup power supply
Error information 1
Stores information such as whether or not there is an error log recorded,
node address setting errors, etc.
1: Error history
1: Fatal data link error
1: Communications controller send
section error
BYTE
byStatus4
Reserved area
Stores undetermined data.
BYTE
byStatus5
Error information 2
1: Node address setting error
1: Node address duplicated
1: Network parameter mismatch
1: Communications controller
hardware error
Stores information such as EEPROM write errors, setting table errors, etc.
Bit
1: EEPROM write error
1: Network parameter error
1: Data link table error
1: Routing table error
BYTE
144
byStatus6
Reserved area
Stores undetermined data.
Section 9-2
Status Information and Troubleshooting
Type
BYTE
Variable name
byStatusFlag
Contents
Data link operation status and data link mode
Stores the data link operation status, data link mode, etc.
Bit
−: Not specified
Current Data Link Mode
0: User-set links
1: Automatic
Data Link Operating Status
0: Stopped
1: Running
BYTE
abyDataLinkStatus[62]
Data link status
Stores the data link status.
Bit
[1]
Node 1
Node 2
[2]
Node 3
[0]
[60]
[61]
Node 61
Node 62
Node Data Link Status
−: Not specified
PC Operating Status
0: Stopped
1: Running (PC program being executed.)
CPU Unit Error Status
0: No error
1: Error
Data Link Communications Error Status
0: Normal
1: Error (Data link data not received normally.)
Data Link Participation Status
0: Not participating or data links stopped
1: Participating
Offset Error Status (Offset larger than number of send words)
0: Normal
1: Error
Insufficient Reception Area (Data larger than data link reception area.
0: Normal
Overflow data discarded.)
1: Insufficient
Excess Reception Area (Data smaller than data link reception area.
0: Normal
Overflow area data not specified.)
1: Excess
Note For Wired Networks set for a maximum of 32 nodes, the above
information is valid through node 32 (abyDataLinkStatus[31]).
145
Status Information and Troubleshooting
9-2-2
Section 9-2
Error Processing
Data Link Status: abyDataLinkStatus [ ]
Bit status
PC’s CPU Unit error is 1: ON
Data Link Communications Error
Status is 1: ON
Data link participation is 0: OFF
Probable cause
A fatal PC error, non-fatal PC error,
or a watchdog timer error has
occurred.
Probable remedy
Refer to the PC’s operation manual
and correct the error. If the error
occurs again, replace the PC.
The Unit is mounted to a non-compatible PC.
The relevant node is not in the Network.
A communications error has
occurred as a result of noise.
Mount onto the correct PC.
A communications error has
occurred.
Refer to 9-1-1 Using the RUN, ERR
and INS Indicators and troubleshoot
accordingly.
Enter the node in the Network.
Conduct an echoback test using the
Controller Link Support Software
and if this does not correct the error,
check the usage environment.
The relevant node is not part of data Enter the relevant node in data
links.
links. If an error occurs, refer to
page 140, Node Cannot Participate
in Data Link and troubleshoot
accordingly.
There are no active data links in the Activate the data links.
Network.
Offset error is 1: ON
The offset is greater than the number of send words at the relevant
node.
Receive area short is 1: ON
The send area at the relevant node
is larger than the receive area and
some data cannot be received.
Receive area remaining is 1: ON
Note
146
Check the number of send words at
the relevant node, the number of
receive words at the local node and
the offset, then reset the data link
table correctly.
When the intention is not to receive
all data, use as is (data that cannot
be received will be read and discarded.)
When it differs from the intended
data link, check the number of send
words at the relevant node, the
number of receive words at the local
node and the offset, then reset the
data link table correctly.
The send area at the relevant node When the intention is to leave some
is smaller than the receive area and space in the receive area, use as is
some of the area will be unused.
(the surplus receive area will be
unspecified data.)
When it differs from the intended
data link, check the number of send
words at the relevant node, the
number of receive words at the local
node and the offset, then reset the
data link table correctly.
Data link status can also be monitored from the CLK Data Link Setting Utility.
Status Information and Troubleshooting
Section 9-2
Other Status
Bit status
Error log exists is 1: ON
Probable cause
Probable remedy
Error information on the Controller Link Using the Controller Link Support SoftSupport Board (an error log) has been ware or an FINS command, read the
recorded.
cause of the current error. Alternatively,
use past error log records to troubleshoot the problem.
Communications controller send error
is 1: ON
The Controller Link Support Board is
faulty.
Replace the Controller Link Support
Board.
Communications controller hardware
error is 1: ON
The Controller Link Support Board is
faulty.
Replace the Controller Link Support
Board.
Network parameter mismatch is 1: ON
The network parameters in EEPROM
do not agree with those being used by
the network
Use the Controller Link Support Software to check the current parameters
and correct the settings as required.
Node address duplicated is 1: ON
The same node address has been set
more than once.
Correct the node addresses so that
each one is assigned to only one node.
EEPROM error is 1: ON
An error has occurred while writing
data to the CPU Unit’s EEPROM.
Routing table error is 1: ON
The routing table data within the CPU
Unit’s EEPROM is damaged.
Check the status of bits 00 to 02 in the
variable and correct any problems
found. If the error occurs again, replace
the CPU Unit.
Refer to 7-3 Setting Routing Tables and
reset the routing tables correctly. If the
error occurs again, replace the Controller Link Support Board.
There is an error in the routing table
setting.
Data link table error is 1: ON
Network parameter area is 1: ON
When using a routing table, refer to 7-3
Setting Routing Tables and reset the
routing tables correctly.
If no routing tables are being used,
delete the tables.
The data link table data in the
Refer to 5-3 Starting and Stopping
EEPROM of the CPU Unit is damaged. Data Links and reset the data link
tables correctly. If the error occurs
again, replace the CPU Unit.
There is an error in the data link table When using manually set data links,
settings.
refer to 5-3 Starting and Stopping Data
Links and reset the data link tables correctly. When manually set data links
are not being used, delete the data link
tables.
Network parameters in EEPROM are
Refer to 8-1-3 Network Parameters and
damaged.
reset the data correctly.
Initialize the network parameters from
the Controller Link Support Software
and cycle the power to the computer. If
the problem persists, replay the Board.
Either set the EEPROM Clear Bit in the
DM parameter area to ON, or use the
Initialize network parameters operation
on the Maintenance Menu of the Controller Link Support Software to initialize the network parameters and then
cycle the power supply.
There is an error in the network param- Refer to 8-1-3 Network Parameters and
eter settings, or node address of the
reset the network parameters or the
local node is larger then the maximum node address.
address set within the network parameters.
147
Section 9-3
Error Log
9-3
Error Log
The error log records errors that occur in the Controller Link Support Board
and the time they occur. The error log can be read or cleared using the Controller Link Support Software, a PC Programming Device, such as the SYSMAC Support Software, or the message service (FINS commands for the
Controller Link Support Board.)
9-3-1
Error Log Table
Errors are recorded in an error log table in the Board’s RAM, with one record
for each error and a maximum of 39 records.
Serious errors are also recorded in the Board’s EEPROM so that when the
power to the Board is turned OFF or reset, a record of the error will remain.
(The error log table in EEPROM automatically reads the Board’s RAM when
the power is turned ON again.)
Item
Specification
No. of records
Data code
39 max.
Binary (Times are in BCD)
Length of each record
Configuration of records
10 bytes
Error code: 2 bytes
(Refer to 9-3-2 Error Codes)
Detail code: 2 bytes
(Refer to 9-3-2 Error Codes)
Time: 6 bytes
(Refer to the Time Information)
Record order
From the oldest record to the most recent.
If the number of records exceeds 39, the oldest record will be deleted and the
most recent error recorded.
Error Log Table Configuration
10 bytes
10 bytes
10 bytes
1 record
1 record
1 record
Maximum 39 records
Record Configuration
1st byte
Error code
10th byte
Details
Minutes
Day Hour Year Month
Seconds
Time Information
The time is recorded in BCD with one byte each for the year (the rightmost
two digits), month, day, hour, seconds, and minutes of the time the error
occurred.
Note
148
The computer’s time information can be read and used in the Controller Link
Support Board. When the time cannot be read from the computer, all error log
times will be 0. When error logs are read from the Controller Link Support
Software, they will be dated 0 s, 0 min, 0 hr, 0 day, 0 month, 2000.
Section 9-3
Error Log
9-3-2
Error Codes
The following table lists the error codes (in 4-digit hexadecimal) and the contents of the errors.
Error
code
Contents
Detail code
1st byte
2nd byte
0001
Hex
CPU Unit watchdog timer error
00 Hex
0002
Hex
0003
Hex
CPU Unit service monitor error
Recorded
in
EEPROM
Replace the CPU Unit.
Yes
Monitor time (ms)
Check the environment settings.
Yes
CPU Unit RAM error
01 Hex:
00 Hex
Cyclic
02 Hex:
Event
04 Hex:
CPU bus link
Check the environment settings.
Yes
0004
Hex
0005
Hex
CPU Bus Unit ID number error
00 Hex
00 Hex
Check the I/O tables.
Yes
Unit number error
Unit set
value
CPU Unit
detected
value
Check the unit number settings and
recreate the I/O tables.
Yes
0006
Hex
CPU error
Bit 11: Unit missing in registered I/O tables
Bit 12: Hard test number
detected
Bit 13: Illegal number
detected
Bit 14: Unit number duplicated
Check the unit number settings and
recreate the I/O tables.
Yes
000E
Hex
000F
Hex
0010
Hex
0011
Hex
I/O bus error
00 Hex
Check the environment settings.
Yes
CPU Unit initialization error
Check the environment settings.
Yes
System capacity exceeded
Reduce the number of CPU Bus
Units mounted in one PC.
Check the environment settings.
Yes
0012
Hex
CPU Unit memory error
0013
Hex
CPU Unit write-protected
CPU Unit initialization timeout
01 Hex:
Read error
02 Hex:
Write error
00 Hex
Correction
00 Hex
Yes
01 Hex:
Check the relevant settings.
Yes
Data link
tables
Release write protection for the CPU Yes
02 Hex: Net- Unit.
work parameters
03 Hex:
Routing
tables
04 Hex: System setup
149
Section 9-3
Error Log
Error
code
Contents
Detail code
1st byte
2nd byte
Recorded
in
EEPROM
0101
Hex
Transmission failed; local node
not in Network
0103
Hex
Transmission failed; retry count
exceeded
0104
Hex
Transmission failed; maximum
number of frames exceeded.
0105
Hex
Transmission failed; node
address incorrect
0106
Hex
Transmission failed; redundant
node address
0107
Hex
Transmission failed; destination
node not in Network
Refer to 9-1 Troubleshooting Using
Indicators and place destination
node into Network.
No
0108
Hex
Unit missing; cannot execute.
Refer to the Installation Guide and
check the Controller Link unit number.
No
0109
Hex
Transmission failed; destination
busy
Increase number of retries or recon- No
figure system to distribute load.
010A
Hex
Transmission failed; communications controller error
010B
Hex
CPU Unit error; cannot send.
Conduct an echoback test and if the Yes
effects of noise are considerable,
reconsider the operating environment. Restart the computer. If the
error occurs again, replace the
Board.
Refer to the manuals for the CPU
No
Unit and correct the problem. If the
problem cannot be corrected,
replace the CPU Unit.
010C
Hex
Unit number setting error; cannot
send.
150
Command block
Bits 0 to 7:
Source node address
Bits 8 to 14:
Source Network address
Bit 15:
OFF
Response block
Bits 0 to 7:
Destination node
address
Bits 8 to 14:
Destination Network
address
Bit 15:
ON
(1st byte: bits 8 to 15;
2nd byte, bits 0 to 7)
Correction
Refer to 9-1 Troubleshooting Using
Indicators and place the local node
into Network.
No
Using the Controller Link Support
Software or FINS commands, run
echoback test and check operating
environment if errors occur.
Check event status on the network.
Reduce the number of events per
communications cycle or increase
the maximum number of network
parameter frames.
Refer to the Installation Guide and
check node address settings to be
sure they are within range and
unique.
No
No
No
Correct node addresses so that they No
are unique within the same Network.
Refer to the Installation Guide and
check node address settings to be
sure they are within range and
unique.
No
Section 9-3
Error Log
Error
code
010D
Hex
010E
Hex
010F
Hex
0110
Hex
0111
Hex
0112
Hex
0113
Hex
0114
Hex
0115
Hex
Contents
Detail code
1st byte
2nd byte
Transmission failed; destination
address incorrect
Command block
Bits 0 to 7:
Source node address
Transmission failed; routing
Bits
8 to 14:
tables not registered
Source Network address
Transmission failed; routing table Bit 15:
error
OFF
Transmission failed; too many
Response block
relay points
Bits 0 to 7:
Destination node
address
Bits 8 to 14:
Transmission failed; command
Destination Network
packet too long
address
Transmission failed; header
Bit 15:
error.
ON
I/O setting error; cannot send.
(1st byte: bits 8 to 15;
2nd byte, bits 0 to 7)
CPU bus error; cannot send.
I/O duplication; cannot send.
Correction
Check routing tables.
Recorded
in
EEPROM
No
No
No
Check routing tables and system
configuration. Do not try to access
Networks separated by more than
one other Network.
No
Be sure to use the correct FINS
command format.
No
No
Correct either the system configuration or the registered I/O tables.
Check the Board and cable connections and clear the error.
Check the unit numbers to be sure
the same number is not set twice in
the same PC.
Check the Board and cable connections and clear the error.
Increase number of retries or reconfigure system to distribute load.
No
Yes
No
No
0116
Hex
0117
Hex
CPU Bus Unit error; cannot
send.
Internal buffer full
0118
Hex
Illegal packet discarded
Check for nodes sending illegal
data.
0124
Hex
Maximum frame length
exceeded; cannot route.
0203
Hex
EEPROM error
Correct the FINS command format. No
Also, be sure that the parameters
specified for the command do not
produce a response that is too long.
Reset the relevant data. If the error Yes
occurs again replace the Controller
Link Support Board.
0206
Hex
Number of participating nodes
Network
decreased (local node still partic- parameters
ipating)
maximum
node
Number of participating nodes
decreased (local node not partic- address
ipating)
Number of
Check network parameters, node
non-partici- participation, cables, and terminatpating nodes ing resistance.
0208
Hex
polling node changed
0209
Hex
Network parameter disagreement
Address of
new polling
node
Address of
polling node
020C
Hex
Time out with token
00 Hex
0210
Hex
Communications controller
transmitter error
00 Hex
0207
Hex
01 Hex:
Read error
02: Hex:
Write error
Address of
previous
polling node
00 Hex
01 Hex:
Data link
tables
02 Hex: Network parameters
03 Hex:
Routing
tables
No
No
No (See
note 3.)
No (See
note 3.)
Check previous polling node.
No (See
note 3.)
Using the Controller Link Support
Yes
Software, check network parameters.
Error status Check network parameters, node
No
(See note 4.) participation, cables, and terminating resistance.
Replace the Controller Link Support Yes
Board.
151
Section 9-3
Error Log
Error
code
Contents
Detail code
1st byte
2nd byte
Correction
Recorded
in
EEPROM
0211
Hex
Duplicate node address error
00 Hex
(connected to SYSMAC LINK by
mistake)
0214
Hex
Node address setting error
Not set
0216
Hex
Backup power supply error
00 Hex
Error type
Check the backup power supply and Yes
01 Hex: OFF the power supply cables.
to ON
02 Hex: OFF
to ON
021A
Hex
Set table logic error
00 Hex
01 Hex: Net- Reset the appropriate data.
work parameters
02 Hex:
Data link
tables
03 Hex:
Routing
tables
021B
Hex
Hardware error
Error status Replace the Controller Link Support No (See
(See note 4.) Board.
note 3.)
021C
Hex
021E
Hex
Data link error stopped
00 Hex:
SL1 error
01 Hex:
SL2 error
Not set
Network line disconnection
Ring status (See note 5.)
0220
Hex
Additional information 1 for number of participating nodes
decreased (0206 Hex)
Additional information 2 for number of participating nodes
decreased (0206 Hex)
Additional information 3 for number of participating nodes
decreased (0206 Hex)
Bits 00 to 15 correspond to Check the network parameters, the
disconnected nodes 1 to 16 disconnected node, and the cables.
No (See
note 3.)
Bits 00 to 15 correspond to
disconnected nodes 17 to
32
Bits 00 to 15 correspond to
disconnected nodes 33 to
48
No (See
note 3.)
0223
Hex
Additional information 4 for num- Bits 00 to 15 correspond to
ber of participating nodes
disconnected nodes 49 to
decreased (0206 Hex)
62
No (See
note 3.)
0300
Hex
Packet discarded
Not set
Conduct an echoback test and find
the cause of the error.
Yes
0601
Hex
Unit error
Not set
Check the operating environment.
Yes
0221
Hex
0222
Hex
Note
Local node
address
Reset so that each node address is No (See
used only once within the same Net- note 3.)
work.
Correct the node address setting.
Yes
Yes
Stop the user application, reset the Yes
computer, and retry.
Refer to information in previous sec- Yes
tions of this manual.
No (See
note 3.)
1. Errors indicated by error codes 0101 to 0116 are recorded only when the
frame was discarded because transmission was impossible.
2. Error codes 021E to 0223 Hex are recorded only for Optical Ring Networks.
3. Recorded in EEPROM for the 3G8F7-CLK13-E, 3G8F7-CLK23-E, and
3G8F7-CLK53-E.
152
Section 9-3
Error Log
4. Error Status
The status of each bit indicates that an error has occurred as given in the
diagram below.
7
6
5
4
3
2
1
0
1: Token timeout error
1: Polling timeout error
1: Communications controller hardware error
1: Polling node was changed
1: Nodes in Network changed (added or removed)
1: Communications controller send error
1: Duplicate node address setting error
Note
If the data link tables have not been set, event ID97 will be logged in the event
log. Event ID97 indicates that a type of event memory not supported by FinsGateway was set for data link data transfer, making data transfer between the
Support Board and event memory impossible. (ID97 is logged when data link
tables are not set.)
Event ID97 will no longer be logged if the data link tables are set. If data links
are not being used, operation should be normal and this event can be
ignored.
5. Ring Status
Disconnected Node Address
(2-digit hexadecimal (00: No
disconnection information))
Disconnection Direction Flag
0: SL1 (upstream)/Normal
1: SL2 (downstream)
Disconnected
node
information 2
(See note.)
Local Node Disconnected Flag
0: Normal
1: Disconnected
Disconnected Node Address
(2-digit hexadecimal (00: No
disconnection information))
Disconnection Direction Flag
0: SL1 (upstream)/Normal
1: SL2 (downstream)
Disconnected
node
information 1
(See note.)
Network Disconnected Flag
0: Normal
1: Disconnected
Note Valid only when bit 15 (Network Disconnected Flag)
is ON. The previous information will be maintained
even if bit 15 is OFF.
9-3-3
Reading and Clearing Error Logs
Error logs can be read or cleared using the FinsGateway, Controller Link Support Software, CX-Programmer, PC Programming Devices, or the message
service. The following examples are for the Controller Link Support Software
and the message service. When using other Programming Devices, refer to
the Programming Device’s operation manual for details.
153
Section 9-4
Cleaning and Inspection
Controller Link Support Software
Read or clear the error log using the following procedure.
1,2,3...
1.
2.
3.
4.
Display the Main Menu.
Select “E: Error log.”
Select “R: Read.”
Designated the node. The error log for the designated node will be displayed.
5. Press the F7 (Clear) Key. The designated node error log will be cleared.
Message Service
Reading an Error Log
Send the ERROR LOG READ FINS command (command code 2102) to the
appropriate node. Refer to 6-3-14 ERROR LOG READ.
Clearing an Error Log
Send the ERROR LOG CLEAR FINS command (command code 2103) to the
appropriate node. Refer to 6-3-15 ERROR LOG CLEAR.
9-4
9-4-1
Cleaning and Inspection
Cleaning
Conduct the following periodic cleaning to keep the Controller Link Support
Board in optimum condition.
• Wipe the Unit with a dry, soft cloth daily.
• If glue, vinyl, or tape is left on the Board 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
cloths for cleaning. They will damage the quality of the coating on the Board.
9-4-2
Inspection
Controller Link Support Boards must be inspected on a regular basis to
ensure correct operation. Inspections should be conducted once every 6 to 12
months. If the Board is subject to extremes in temperature or humidity, inspections should be conducted on a more regular basis.
Tools and Equipment Need for Inspection
The following tools and equipment will be needed to perform inspection and
adjustments.
• 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
• Optical tester
154
Section 9-5
Handling Precautions
Inspection Items
Inspect the following items to see if they deviate from the prescribed standards. If any items do deviate from the standard either adjust so they are
within the operating range or adjust the Board accordingly.
Item
Ambient
conditions
Installation
Optical fiber
deterioration
9-5
Description
Inspection instrument
Temperature: 5° to 45°C
Humidity: 8% to 80% (no condensation or freezing)
Thermometer
Hygrometer
Dust-free
Board securely attached?
Communications cable connectors
tight?
Communications cables securely
locked into place?
Communications cabling used for
external wiring intact (no breaks)?
Sight
Sight
Optical loss increasing?
Confirm that optical loss
has not increased since
installation.
50/125 µm: 3.0 db/km
62.5/125 µm: 3.5 db/km
Handling Precautions
The Controller Link Support Board is a Network device. If the Board is damaged, it will effect the entire Network, so always ensure repairs are undertaken immediately. We recommend that you have a spare Controller Link
Support Board on hand so that repairs may be conducted quickly.
9-5-1
Replacing the Unit
Observe the following precautions when replacing the Board.
• Always turn OFF the power to the computer before replacing the Board.
• Check that the new Board is not faulty.
• If you suspect that a poor connection is the cause of a malfunction, clean
the connector terminals using a clean, soft cloth and industrial-grade
alcohol. Remove any lint or threads left from the cloth, and remount the
Board.
• When returning a faulty Board for repairs, always attach a detailed fault
report to the Unit and return to you nearest OMRON outlet as listed at the
back of this manual.
Note
9-5-2
In order to prevent faulty operation be sure to turn off the power to all nodes
before replacing the Board.
Replacing the Board
Note
1. When replacing the Board, do not reconnect that node to the Network before carrying out the procedures listed below. In particular, a node with a
small address will become the polling node and communicate the initial
network parameter status to other nodes, so there is the chance that network parameters in the entire Network will be damaged.
2. The data link table, network parameters, and routing table are stored in the
Controller Link Support Board’s EEPROM. When the Board has been replaced, make these settings again before starting operation.
155
Section 9-5
Handling Precautions
The following procedure can be used to automatically set the network parameters in EEPROM from other nodes operating on the network. The data link
tables will need to be reset from the Controller Link Support Software.
1,2,3...
1. Turn OFF the power supply to the computer of the Board to be replaced.
2. Detach the communications cables attached to the Controller Link Support
Board to be replaced and remove the Board.
3. Set the new Controller Link Support Board’s ID switch and the terminating
resistance switch to the same as for the previous Board.
4. Mount the Controller Link Support Board in the expansion slot of the computer and connect the communications cables.
5. Turn ON the power supply to the computer where the Board was replaced
and open the FinsGateway settings.
6. Use the following procedure to set the Board as a polled node.
a. Click the Basic Tab in the FinsGateway Settings.
b.
Click the Drivers Icon.
c.
Select CLK (PCI) and click the Properties Button.
d. Select the Board to be set and click the Change Button.
e. Click the Driver Tab in the Controller Link (PCI) Lists Dialog Box.
f.
Remove the check from the setting for the polling unit.
g. Click the OK Button.
7. Use the following procedure to start the Controller Link (PCI) service from
the FinsGateway Settings so the Board will participate in the network.
a. Click the Basic Tab in the FinsGateway Settings.
b.
Click the Services Icon.
c.
Select CLK (PCI) and click the Start Button.
8. Using the CLK Data Link Setting Utility in the FinsGateway or the Controller Link Support Software, read the network parameters and make sure the
Network is operating normally.
9. Using the CLK Data Link Setting Utility in the FinsGateway or the Controller Link Support Software, register data link tables and routing tables in the
new Board.
10. Change the Board to the polling node from the FinsGateway Settings, reversing the procedure in step page 156, above. The RUN and INS indicators should light on the Board. The LNK indicator may also light.
11. Check that the data links are operating normally by using the CLK Data
Link Setting Utility in the FinsGateway or the Controller Link Support Software.
Note
1,2,3...
The following procedure can be used to start the CLK Data Link Setting Utility
in FinsGateway.
1. Click the Basic Tab in the FinsGateway Settings.
2. Click the Networks Icon.
3. Select the desired Board and click the Properties Button.
4. Click the Data Links Tab.
5. Click the Set Data Links Tab.
Refer to FinsGateway online help for details.
156
Appendix A
Standard Models
Controller Link Support Boards for PCI Bus
Applicable
computer
IBM PC/AT or compatible
Connection type
Wired
Optical Ring for HPCF cable
Optical Ring for GI
cable
Model number
Remarks
3G8F7-CLK23-E
Include FinsGate3G8F7-CLK21-EV1 way Controller Link
(PCI) Embedded
3G8F7-CLK13-E
3G8F7-CLK12-EV1 Edition (Version 3)
3G8F7-CLK53-E
3G8F7-CLK51-EV1
Controller Link Support Boards for ISA Bus
Applicable
computer
IBM PC/AT or compatible
Connection type
Model number
Wired
3G8F5-CLK21-E
Optical
3G8F5-CLK11-E
Connection type
Wired
Model number
CVM1-CLK21
Optical Ring for HPCF cable
CVM1-CLK12
Optical Ring for GI
cable
CVM1-CLK52
C200HX/HG/HE
PCs
Wired
C200HW-CLK21
CS-series PCs
Wired
Optical
CS1W-CLK23
CS1W-CLK21 (-V1)
CS1W-CLK11
Optical Ring for HPCF cable
CS1W-CLK13
CS1W-CLK12 (-V1)
Optical Ring for GI
cable
CS1W-CLK53
CS1W-CLK52 (-V1)
Wired
CJ1W-CLK23
CJ1W-CLK21 (-V1)
Remarks
Controller Link Support Software
included.
Controller Link Units
Applicable PC
CV-series PCs
CJ-series PCs
Remarks
---
Controller Link Support Software
Applicable computer
IBM PC/AT or compatible
Model number
C200HW-ZW3AT2-EV2
Remarks
English version
157
Appendix A
Standard Models
Wired Communications Cables
Model
Li2Y-FCY2 × 0.56 qmm
1 × 2 × AWG-20PE + Tr.CUSN +
PVC
#9207
ESVC 0.5 × 2 C
Manufacturer
Kromberg & Schubert,
Komtec Department
Draka Cables Industrial
Remarks
German company
Spanish company
Belden
USA company
Bando Densen Co.
Japanese company
Optical Fiber Cable Connectors and Accessories for Optical
Ring Networks with H-PCF Cable
Name
Optical
Connector
Model
S3200-COCF2071
Remarks
Connects a cable to a node. Two connectors are
required for each cable.
(Full-lock connector for crimp-cut cable.)
S3200-COCF2571
Connects a cable to a node. Two connectors are
required for each cable.
(Half-lock connector for crimp-cut cable.)
S3200-COIAT2000
Connects two cables. One adapter is required to
connect two cables.
Optical Fiber CAK-0057
Assembly
Tool
For the S3200-COCF2071/2571 Connectors
Optical
S3200-CAT2700
Power Tester
S3200-CAT2702 Head Unit,
For the S3200-COCF2071/2571 Connectors
Master Fiber S3200-CAT2001H
Set
For the S3200-COCF2011/2511 Connectors
No Longer Manufactured
Name
Connector
Model
S3200-COCF2011
S3200-COCF2511
Replacement model
S3200-COCF2071
S3200-COCF2571
An S3200-COCF2071/2571 optical connector can be assembled by adding the JRFK-57PLUS (Sumitomo
Electric Industries) to the S3200-CAK1062.
No Longer Manufactured
Name
Optical Fiber Assembly Tool
158
Model
S3200-CAK1062
Specifications
Crimp-cut tool for the S3200COCF2011/2511 Connectors
Appendix A
Standard Models
Indoor H-PCF Optical Fiber Cables for Optical Ring Networks
Name
H-PCF cables
Black
Orange
Note
Specifications
10 m
Model
S3200-HCCB101
50 m
100 m
S3200-HCCB501
S3200-HCCB102
500 m
1,000 m
S3200-HCCB502
S3200-HCCB103
10 m
50 m
S3200-HCCO101
S3200-HCCO501
100 m
500 m
S3200-HCCO102
S3200-HCCO502
1,000 m
S3200-HCCO103
The Optical Fiber Cable model numbers are as follows.
[email protected]@@@@@@
Tensioner option
None: Standard (with tension member)
N:
Without tension member
Cable length
@@@
A B
(A/10) x 10B m
Cable color
B: Black
O: Orange
Cable specification
L: With power supply line
C: Without power supply line
Type
B: Cord
C: Cable
Indoor H-PCF Optical Fiber Cable with Connectors for Optical
Ring Networks
The following Optical Fiber Cables are available with Connectors already attached. (These cables have power
supply lines and tension members, which aren’t used in the Controller Link Network.)
Specifications
Optical Fiber Cable
Connectors:
S3200-COCF2011
⇓
S3200-COCF2011
Length
2m
S3200-CN201-20-20
Model
5m
10 m
S3200-CN501-20-20
S3200-CN102-20-20
15 m
20 m
S3200-CN152-20-20
S3200-CN202-20-20
Over
20 m
S3200-CN-20-20
(Specify length (m) when ordering.)
159
Appendix A
Standard Models
Specifications
Optical Fiber Cable
Connectors:
S3200-COCF2011
⇓
S3200-COCF2511
Length
2m
S3200-CN201-20-25
Optical Fiber Cable
Connectors:
S3200-COCF2511
⇓
S3200-COCF2511
Note
Model
5m
10 m
S3200-CN501-20-25
S3200-CN102-20-25
15 m
20 m
S3200-CN152-20-25
S3200-CN202-20-25
Over
20 m
2m
S3200-CN-20-25
(Specify length (m) when ordering.)
S3200-CN201-25-25
5m
10 m
S3200-CN501-25-25
S3200-CN102-25-25
15 m
20 m
S3200-CN152-25-25
S3200-CN202-25-25
Over
20 m
S3200-CN-25-25
(Specify length (m) when ordering.)
Special training is required to assemble Optical Fiber Cables and connectors with epoxy adhesive. Contact your OMRON dealer for details
on other optical fiber cords and cables.
GI Optical Fiber Cables for Optical Ring Networks
Use graded index (GI) optical fiber cables with the following optical characteristics.
50/125 µm AGF
Item
Numerical aperture
Transmission loss
Min.
Typical
Max.
Unit
Conditions
---
0.21
---
---
Theoretical value
---
---
3.0 Lf
dB
0.5 km ≤ Lf
0.2 km ≤ Lf < 0.5 km
Lf < 0.2 km
3.0 Lf + 0.2
3.0 Lf + 0.4
Connection loss
--Transmission band 500
-----
1.0
---
MHz · km
λ = 0.8-µm band
Ta = 25°C
λ = 0.8-µm band, 1 location
λ = 0.85 µm (LD)
Lf: Fiber length in km, Ta: Ambient temperature, λ: Center wavelength of measurement light source
62.5/125 µm AGF
Item
Numerical aperture
---
Min.
Typical
0.28
Transmission loss
---
Connection loss
--Transmission band 200
Max.
Unit
Conditions
Theoretical value
---
---
---
3.5 Lf
3.5 Lf + 0.2
dB
3.5 Lf + 0.4
Lf < 0.2 km
-----
1.0
---
λ = 0.8-µm band, 1 location
λ = 0.85 µm (LD)
MHz · km
0.5 km ≤ Lf
0.2 km ≤ Lf < 0.5 km
λ = 0.8-µm band
Ta = 25°C
Lf: Fiber length in km, Ta: Ambient temperature, λ: Center wavelength of measurement light source
Connectors for GI Cable for Optical Ring Networks
Use ST connectors.
160
Index
Numerics
1 to 1 type, 8
1:N allocations
1 to 1 type, 8
chain type, 8
common type, 8
A
access modes
Controller Link Support Board, 11
applications
creating, 49
automatic setting
1:N allocations, 8
B
backup power supply
optical system, 46
broadcast test
reading results, 107
sending results, 108
inactive data links, 130
computer
specifications, 21
configuration, 20
connections
backup power supply, 46
clearing network disconnection information, 106
GI Cable Optical Ring System, 41
H-PCF Cable Optical Ring System, 35
maximum delay for line disconnections, 131
reading connection configuration information, 102
reading network disconnection information, 104
wired systems, 30
connectors
standard models, 158, 160
Controller Link
communications, 126
Controller Link Support Board, 157
access modes, 11
configuration, 20
definition, 10
FINS commands, 95
Controller Link Support Software (CLSS)
standard models, 157
starting and stopping data links, 84
Controller Link Unit
standard models, 157
C
C library, 52
cables
connecting
connector to Support Board, 34
connecting to communications connectors, 31
optical, 35, 37, 41
backup power supply, 46
connectors, 38, 43
standard models, 158
chain type, 8
cleaning, 154
commands
See also FINS commands
common type, 8
communications
between different PCs, 5
cables, 35, 41
optical, 35, 41
wiring, 30
Controller Link, 126
communications cycle, 126
no. of event-frames, 127
communications timing, 125
communications cycle time, 128
active data links, 128
D
DA1, 93
DA2, 94
data link, 71
automatically set, 73
example, 81
Select All, 80
description, 72
Easy Setting, 73
features, 11
I/O response time, 133
computer to PC, 133
PC to computer, 134
manual vs automatic setting, 77
manually set, 72, 78
from computer node, 79
from Programming Device, 78
monitoring, 85
data link status area, 85
LED indicators, 85
manipulating bit/word status, 87
offsets, 75
precautions, 23
procedures, 50
reading status, 101
161
Index
setting, 77
specifications, 76
starting, 95
starting and stopping, 82
with Controller Link Support Software, 84
with FINS commands, 84
with Programming Device or ladder program, 83
stopping, 96
data link table
changing during operation, 9, 87
data link tables
specifications, 80
data links
automatic setting
1:N, 8
status
storage format, 142
data structure
commands, 93
responses, 93
delay times
message service, 135
destination
network address, 93
node number, 93
unit address, 94
dimensions, 18
disconnections
clearing network disconnection information, 106
maximum delay for line disconnections, 131
reading network disconnection information, 104
DNA, 93
E
Easy Setting
data link, 73
EC Directives, xix
echoback test, 107
errors
clearing, 109
error codes, 149
error log, 148
error log table, 148
network relay, 110
processing
data link status, 146
other status, 147
reading, 108
reading and clearing error logs, 153
reading with C language, 69
response codes, 111
162
F
features
Controller Link, 1
Controller Link network, 4
data links, 11
message service, 12
FINS commands
BROADCAST TEST DATA SEND, 108
BROADCAST TEST RESULTS READ, 107
command codes, 95
CONNECTION CONFIGURATION INFORMATION
READ, 102
CONTROLLER DATA READ, 96
CONTROLLER STATUS READ, 97
data format, 94
DATA LINK START, 95
DATA LINK STATUS READ, 101
DATA LINK STOP, 96
ECHOBACK TEST, 107
ERROR LOG CLEAR, 109
ERROR LOG READ, 108
errors, 111
format, 93
headers, 93
NETWORK DISCONNECTION INFORMATION
CLEAR, 106
NETWORK DISCONNECTION INFORMATION
READ, 104
NETWORK STATUS READ, 99
parameters, 94
response codes, 109
errors, 111
response data format, 94
starting and stopping data links, 84
G
gateway count, 93
GCT, 93
I
ICF, 93
indicators, 20
troubleshooting, 138
LNK, 140
RUN, ERR & INS, 138
inspection, 154
L
library
C library, 52
functions, 56
Index
ClkClearMessageOnArrival(), 63
ClkClose(), 57
ClkGetLastError(), 63
ClkGetNetworkStatus(), 60
ClkGetRingStatus(), 61
ClkOpen(), 56
ClkReadDatalink(), 59
ClkRecvFins(), 58
ClkSendFins(), 57
ClkSetMessageOnArrival(), 61
ClkSetThreadMessageOnArrival(), 62
ClkWriteDatalink(), 59
reading error information, 69
specifications, 21
structure descriptions, 64
CLKHEADER/*PCLKHEADER, 64
EMCLKADDRESS/*PEMCLKADDRESS, 64
NSTBUFFER/*PNSTBUFFER, 65
RINGBUFFER/*PRINGBUFFER, 68
M
maintenance, 137
message service, 91
delay times, 135
features, 12
procedures, 51
specifications, 92
message services
functions/driver calls, 92
N
network
Controller Link, 2
features, 4
interconnections, 117
Controller Link, 118
definition, 118
other OMRON networks, 118
parameters, 127
specifying, 128
reading status, 99
relay error, 110
network parameters
maximum node address, 127
node bypass function, 46
nodes, extending to 62, 7
number of polled nodes, 127
O
operating system
specifications, 21
optical fiber cables
accessories, 37
See also cables
standard models, 159
P
parameters, 93
FINS commands, 94
PC
reading controller status, 97
polled nodes
number, 127
precautions
application, xviii, 23
data links, 23
general, xv
handling, 155
operating environment, xvii
safety, xvi
procedures
data link, 50
message service, 51
overview, 22
R
Repeater Units, 7, 24
response codes
configuration, 109
response to FINS commands, 109
troubleshooting, 111
routing tables, 119
creating, 119
examples, 121
setting, 121
RSV, 93
S
SA1, 94
SA2, 94
service ID, 94
setting
data link, 77
SID, 94
SNA, 94
software
configuration, 21
163
Index
source
network address, 94
node number, 94
unit address, 94
specifications
backup power supply, 46
communications, 16
data link, 76
data link tables, 80
general, 18
message service, 92
standard models, 157
system configuration, 13
T
troubleshooting, 137
indicators
LNK, 140
RUN, ERR & INS, 138
status information, 143
using ClkGetNetworkStatus, 143
using indicators, 138
W
wiring, 30
See also connections
164
Revision History
A manual revision code appears as a suffix to the catalog number on the front cover of the manual.
Cat. No. W383-E1-04
Revision code
The following table outlines the changes made to the manual during each revision. Page numbers refer to
the previous version.
Revision code
Date
Revised content
01
02
January 2001
June 2003
03
May 2006
Original production
Changes and additions made to add version-1 Boards and CJ-series PCs.
The major changes are as follows:
Page xv: EC Directive information added.
Page 4: Table changed.
Pages 7, 20, 23, 66, 71, 72, 77, and 128: Information added.
Pages 10 and 11: Graphics changed.
Page 13: Information on using 62 nodes in a Wired Network added.
Page 16: Product component list changed for wired system.
Page 17: Information added in and after table.
Page 22: Table corrected.
Page 27: Table corrected and table added at bottom of page.
Page 28: Connector type added above first table, second table corrected and
information added after it, and table added.
Page 49: Information added to description in two places.
Page 50: “Detailed error information” changed in two places.
Pages 52 and 53: Information added to description.
Page 53: Error code changed from 70 to 69.
Page 56: Data type changed to DWORD at bottom of page.
Pages 57, 59, 87, 88, and 130: Information restricting context to 32 nodes
added.
Page 61: Table corrected.
Pages 65, 71: “Equality Layout” added.
Page 89: Note changed and “type” added.
Page 90: Callout changed in first illustration.
Page 126: Two rows added to table.
Page 138: Information added after first illustration.
Page 144: Top table corrected and information added following it.
“CS1-series” changed to “CS-series” throughout the manual.
Page v: Information on general precautions notation added.
Page x: Information on liability and warranty added.
Page xv: EMC standards changed.
Page xvi: Common emission standard and common immunity standard
changed.
Page 24: “PLC” corrected to “PC” (Programmable Controller).
165
Revision History
Revision code
04
166
Date
September 2007
Revised content
Added the 3G8F7-CLK13-E, 3G8F7-CLK23-E, and 3G8F7-CLK53-E
throughout the manual.
Page xx: Changed specific model numbers to “Controller Link Support
Boards.”
Pages 4, 73, 74: Changed table.
Page 8: Changed first item under Restrictions and last paragraph on page.
Page 9: Added material before section 1-1-3.
Page 10: Changed version of Microsoft Visual C++.
Pages 17 and 18: Changed dimensions diagrams.
Pages 22, 24, 48, : Changed catalog number from W388 to W467.
Page 25: Removed first and last items and changed three items in middle of
page (starting with “if using Optical Units”).
Page 26: Changed first item and added item after it.
Page 45: Changed bulleted items.
Page 63: Changed first diagram in table.
Page 67: Added error codes.
Pages 74, 76: Added note.
Page 111: Changed last third of table.
Page 77: Added material to first row of table and removed material from third
and sixth rows.
Page 104: Changed ranges in No. of stored records (response).
Page 116: Changed section on relay network table.
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement