SYSMAC CS/CJ Series CS1W-FLN22 / CJ1W-FLN22 FL

SYSMAC CS/CJ Series CS1W-FLN22 / CJ1W-FLN22 FL
Cat. No. W440-E1-03
SYSMAC
CS/CJ Series
CS1W-FLN22 (100Base-TX)
CJ1W-FLN22 (100Base-TX)
FL-net Units
OPERATION MANUAL
CS1W-FLN22 (100Base-TX)
CJ1W-FLN22 (100Base-TX)
FL-net Units
Operation Manual
Revised October 2010
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 “PLC” means Programmable Controller.
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.
1,2,3...
1. Indicates lists of one sort or another, such as procedures, checklists, etc.
 OMRON, 2004
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xix
1
Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xx
2
General Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xx
3
Safety Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xx
4
Operating Environment Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xxi
5
Application Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xxi
6
Conformance to EC Directives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xxiii
7
Unit Versions of CS/CJ-series FL-net Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xxiv
SECTION 1
Features and System Configuration . . . . . . . . . . . . . . . . . . .
1
1-1
FL-net Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2
1-2
System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7
1-3
Related Programming Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8
1-4
Introducing the CX-FLnet Support Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8
1-5
Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9
1-6
Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
SECTION 2
Communications Functions . . . . . . . . . . . . . . . . . . . . . . . . . .
15
2-1
FL-net . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16
2-2
Cyclic Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
20
2-3
Message Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
2-4
FINS Communications Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22
SECTION 3
Startup Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
25
3-1
Before Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26
3-2
Initial Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
27
3-3
Nomenclature and Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
28
3-4
Hardware Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30
3-5
Mounting to the PLC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
33
3-6
Network Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
34
3-7
Connecting to the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
38
3-8
Creating an I/O Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
39
3-9
Creating Routing Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
40
3-10 System Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45
3-11 Checking Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
46
vii
TABLE OF CONTENTS
SECTION 4
System Setup and Memory Allocations . . . . . . . . . . . . . . . .
47
4-1
Allocated Words . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
48
4-2
CPU Bus Unit System Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
49
4-3
Allocated Words in the CIO Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51
4-4
Allocated Words in the DM Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
58
SECTION 5
Data Link. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
63
5-1
Data Link Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
64
5-2
Setting Data Link Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
68
SECTION 6
Message Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
83
6-1
Message Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
84
6-2
Details of Supported Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
86
SECTION 7
FINS Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
91
7-1
Overview of FINS Communications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
92
7-2
Sending Commands from a PLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
94
7-3
Command Codes and Response Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
105
7-4
CS/CJ-series Memory Areas and Virtual Addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
106
7-5
Command/Response Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
107
SECTION 8
Communications Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
8-1
Network Communications System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
134
8-2
Communications Cycle Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
134
8-3
Influence on Cycle Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
136
8-4
Calculating the Data Link I/O Response Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
136
8-5
Message Service Transmission Delays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
137
SECTION 9
Testing Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
viii
9-1
Communications Testing Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
140
9-2
PING Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
140
9-3
Internode Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
141
TABLE OF CONTENTS
SECTION 10
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
10-1 Troubleshooting with Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
146
10-2 Error Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
148
10-3 Error Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
149
10-4 Troubleshooting Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
152
10-5 Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
161
10-6 Inspections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
162
SECTION 11
CX-FLnet Support Software Operations . . . . . . . . . . . . . . . 167
11-1 CX-FLnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
168
11-2 Operating Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
170
Appendices
A
System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
189
B
System Configuration Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
193
C
Network System Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
199
D
FL-net Network Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
205
E
FL-net Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
211
F
FL-net Unit Support Software Ver. 1.6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
221
G
International System of Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
245
Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
ix
About this Manual:
This manual describes the installation and operation of the CS1W-FLN22 (100Base-TX) and CJ1WFLN22 (100Base-TX) FL-net Units.
FL-net Units are used to connect to FL-net networks.
Please read this manual and all related manuals listed in the following table carefully and be sure you
understand the information provided before attempting to install and operate an FL-net Unit.
Name
SYSMAC CS/CJ Series
CS1W-FLN22 (100Base-TX) and CJ1W-FLN22
(100Base-TX) FL-net Units
Operation Manual
(this manual)
SYSMAC CS/CJ Series
CS1W-ETN21, CJ1W-ETN21
100Base-TX Ethernet Units
Operation Manual, Construction of Network
[email protected]@C-E
CX-One FA Integrated Tool Package Setup Manual
WS02-CXPC1-E-V61
SYSMAC CX-Programmer Ver. 6.1
Operation Manual
WS02-CXPC1-E-V61
SYSMAC CX-Programmer Ver. 6.1
Operation Manual Function Blocks
Cat. No.
Contents
W440
Describes the installation and operation of the CS1WFLN22 and CJ1W-FLN22 FL-net Units.
Refer to the Communications Commands Reference
Manual (W342) for information on FINS commands that
can be addressed to CS/CJ-series CPU Units.
W420
Provides information on operating and installing
100Base-TX Ethernet Units, including details on basic
settings and FINS communications.
W444
Provides an overview of the CX-One FA Integrated Tool
and installation procedures.
Provides information on installing and operating the CXProgrammer for all functions except for function blocks.
W446
W447
[email protected]@C-E
CX-Integrator Operation Manual
W445
SYSMAC CS Series
CS1G/[email protected]@-EV1, CS1G/[email protected]@H
Programmable Controllers Operation Manual
W339
SYSMAC CJ Series
[email protected]@, [email protected]@, [email protected]@P,
CJ1G/[email protected]@H
Programmable Controllers Operation Manual
W393
SYSMAC CS/CJ Series
CS1G/[email protected]@-EV1, CS1G/[email protected]@H,
[email protected]@H, [email protected]@S, [email protected]@, [email protected]@, [email protected]@P, CJ1G/
[email protected]@H
Programmable Controllers Programming Manual
W394
Provides specifications and operating procedures for
function blocks.
When programming, refer to the CJ Series (W339) or CJ
Series (W393) Programmable Controllers Operation
Manual, CS/CJ Series Programmable Controllers Programming Manual (W394), and CS/CJ Series Programmable Controllers Instructions Reference Manual
(W340).
Describes CX-Integrator operating procedures and provides information on network configuration (data links,
routing tables, Communications Units setup, etc.
Provides an outline of and describes the features, system configuration, installation, wiring, I/O memory allocations, and troubleshooting for the CS-series PLCs.
Use this manual together with the CS/CJ Series Programmable Controllers Programming Manual (W394).
Provides an outline of and describes the features, system configuration, installation, wiring, I/O memory allocations, and troubleshooting for the CJ-series PLCs.
Use this manual together with the CS/CJ Series Programmable Controllers Programming Manual (W394).
This manual describes programming, tasks, file memory
function, and other functions of the CS/CJ-series PLCs.
Use this manual together with the CJ Series (W339) or
CJ Series (W393) Programmable Controllers Operation
Manual.
xi
Name
SYSMAC CS/CJ Series
CS1G/[email protected]@-EV1, CS1G/[email protected]@H,
[email protected]@H, [email protected]@S, [email protected]@, [email protected]@, [email protected]@P, CJ1G/
[email protected]@H
Programmable Controllers Instructions Reference
Manual
SYSMAC CS/CJ Series
CS1G/[email protected]@-EV1, CS1G/[email protected]@H,
[email protected]@H, [email protected]@S, [email protected]@, [email protected]@, [email protected]@P, CJ1G/
[email protected]@H, CS1W-SCB21-V1/41-V1, CS1WSCU21-V1, CJ1W-SCU21-V1/41-V1
Communications Commands Reference Manual
xii
Cat. No.
W340
Contents
Describes the ladder diagram programming instructions
supported by CS/CJ-series PLCs.
Use this manual together with the CJ Series (W339) or
CJ Series (W393) Programmable Controllers Operation
Manual and the CS/CJ Series Programmable Controllers Programming Manual (W394).
W342
Describes the C-series (Host Link) and FINS communications commands used with CS/CJ-series PLCs.
This manual describes communications commands
addressed to the CPU Unit. The communications path is
not relevant, i.e., communications can be performed via
a serial port on the CPU Unit, Serial Communications
Unit/Board, or a Communications Unit.
About this Manual, Continued
This manual contains the following sections.
Section 1 introduces the overall structure of an FL-net (Ver. 2.00) network, outlines the features of the
FL-net (Ver. 2.00) Unit, describes the communications protocols used by an FL-net (Ver. 2.00) network, and provides basic precautions for use of the network.
Section 2 describes the communications functions that can be used with the FL-net (Ver. 2.00) Units.
Section 3 explains the procedure for starting up the FL-net (Ver. 2.00) Unit, including mounting to the
PLC, making the required settings, and checking communications.
Section 4 explains the System Setup and the words allocated in the CIO Area and the DM Area for
FL-net (Ver. 2.00) Units.
Section 5 explains the Data Link function, including an overview and examples of how to make the
required settings.
Section 6 describes the message transmission used by an FL-net (Ver. 2.00) network.
Section 7 provides information on communicating on FL-net Systems and interconnected networks
using FINS commands. The information provided in the section deals only with FINS communications
in reference to FL-net (Ver. 2.00) Units.
Section 8 describes the communications system, communications cycle time, communications cycle
time calculation, data link I/O response time, data link I/O response time calculation, and message service transmission delays.
Section 9 describes functions that allow you to test communications.
Section 10 describes information and procedures that can be used to troubleshoot problems that
sometimes occur with FL-net (Ver. 2.00) Unit and FL-net communications.
Section 11 describes the Support Software used to make settings for the FL-net Units.
!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.
xiii
xiv
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.
xv
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.
xvi
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.
xvii
xviii
PRECAUTIONS
This section provides general precautions for using the CS/CJ-series Programmable Controllers (PLCs) and related devices.
The information contained in this section is important for the safe and reliable application of Programmable
Controllers. You must read this section and understand the information contained before attempting to set up or
operate a PLC system.
1
2
3
4
5
6
7
Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Safety Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operating Environment Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Application Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Conformance to EC Directives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unit Versions of CS/CJ-series FL-net Units . . . . . . . . . . . . . . . . . . . . . . . . . .
xx
xx
xx
xxi
xxi
xxiii
xxiv
xix
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 Unit. Be
sure to read this manual before attempting to use the Unit and keep this manual close at hand for reference during operation.
!WARNING It is extremely important that a PLC and all PLC Units 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 PLC System to the above-mentioned applications.
3
Safety Precautions
!WARNING Do not attempt to take any Unit apart while the power is being supplied. Doing
so may result in electric shock.
!WARNING Do not touch any of the terminals or terminal blocks while the power is being
supplied. Doing so may result in electric shock.
!WARNING Do not attempt to disassemble, repair, or modify any Units. Any attempt to do
so may result in malfunction, fire, or electric shock.
!Caution Execute online editing only after confirming that no adverse effects will be
caused by extending the cycle time. Otherwise, the input signals may not be
readable.
xx
Operating Environment Precautions
4
• Emergency stop circuits, interlock circuits, limit circuits, and similar safety
measures must be provided in external control circuits.
!Caution Tighten the screws on the terminal block of the AC Power Supply Unit to the
torque specified in the operation 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.
5
Application Precautions
Observe the following precautions when using the FL-net Unit.
!WARNING Always heed these precautions. Failure to abide by the following precautions
could lead to serious or possibly fatal injury.
• Always connect to a ground of 100 Ω or less when installing the Units. Not
connecting to a ground of 100 Ω or less may result in electric shock.
xxi
5
Application Precautions
• Always turn OFF the power supply to the CPU Unit, Slaves, and Communications Units before attempting any of the following. Not turning OFF
the power supply may result in malfunction or electric shock.
• Mounting or dismounting I/O Units, CPU Units, Memory Packs, or
Master Units.
• Assembling the Units.
• Setting DIP switches or rotary switches.
• Connecting cables or wiring the system.
!Caution Failure to abide by the following precautions could lead to faulty operation of
the Ethernet Unit or the system, or could damage the Ethernet Unit. 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.
• Interlock circuits, limit circuits, and similar safety measures in external circuits (i.e., not in the Programmable Controller) must be provided by the
customer.
• Always use the power supply voltages specified in the operation manuals.
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.
• Make sure that all the Backplane mounting screws, terminal block screws,
and cable connector screws are tightened to the torque specified in the
relevant manuals. Incorrect tightening torque may result in malfunction.
• Leave the label attached to the Unit when wiring to prevent wire clippings
from entering the Unit. Removing the label may result in malfunction if foreign matter enters the Unit.
• Remove the label after the completion of wiring to ensure proper heat dissipation. Leaving the label attached 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 wiring and switch settings before turning ON the power
supply. Incorrect wiring may result in burning.
• Wire all connections correctly.
• Mount Units only after checking terminal blocks and connectors completely.
• Make sure that the terminal blocks, expansion cables, and other items
with locking devices are locked in place.
• When transporting the Unit, use special packing boxes and protect it from
being exposed to excessive vibration or impacts during transportation.
xxii
6
Conformance to EC Directives
• Check the user program and set parameters for proper execution before
actually running it on the Unit. Not checking the program may result in
unexpected operation.
• Observe the following precautions when wiring the communications
cable.
• Separate the communications cables from the power lines or high-tension lines.
• Do not bend the communications cables past their natural bending radius.
• Do not pull on the communications cables.
• Do not place heavy objects on top of the communications cables.
• Always lay communications cable inside ducts.
• Use appropriate communications cables.
• Before touching a Unit, be sure to first touch a grounded metallic object in
order to discharge any static build-up. Not doing so may result in malfunction or damage.
• Confirm that no adverse effect will occur in the system before attempting
any of the following. Not doing so may result in an unexpected operation.
• Changing the operating mode of the PLC (including changing the Startup Mode setting).
• Force-setting/force-resetting any bit in memory.
• Changing the present value of any word or any set value in memory.
• Check that data link tables and parameters are properly set before starting operation. Not doing so may result in unexpected operation. Even if
the tables and parameters are properly set, confirm that no adverse
effects will occur in the system before running or stopping data links.
• Install the FL-net Units separated sufficiently from devices that generate
high-frequency noise.
• Do not drop the FL-net Unit or subject it to excessive shocks or vibrations.
6
6-1
Conformance to EC Directives
Applicable Directives
• EMC Directives
• Low Voltage Directive
6-2
Concepts
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 the
overall machine. 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 on which the OMRON devices are installed.
The customer must, therefore, perform the final check to confirm that devices
and the overall machine conform to EMC standards.
xxiii
7
Unit Versions of CS/CJ-series FL-net Units
Note
Applicable EMS (Electromagnetic Susceptibility) and EMI (Electromagnetic
Interference) Standards in the EMC (Electromagnetic Compatibility) standards are as follows:
Unit/Board
CS1W-FLN22
CJ1W-FLN22
EMS
EMI
EN61000-6-4
EN61000-6-2
Common Emission Standard EN61000-6-4, radiated emission standard
(10 m)
Low Voltage Directive
Always ensure that devices operating at voltages of 50 to 1,000 V AC and 75
to 1,500 V DC meet the required safety standards for the PLC (EN61131-2).
7
Unit Versions of CS/CJ-series FL-net Units
Unit Versions
A “unit version” has been introduced to manage CS/CJ-series FL-net Units
according to differences in functionality accompanying upgrades.
1. Unit Version Notation on Products
The unit version code is provided on the nameplate of the CS-series FL-net
Units for which unit versions are being managed, as shown below. This system applies to FL-net Units with unit version 1.0 or later.
Example: CS1W-FLN22 CS-series
FL-net Unit
Nameplate
CS1W-FLN22
FL-net UNIT
Unit version 1.0
Lot No. 040301 0000 Ver.1.0
OMRON Corporation
MADE IN JAPAN
2. Confirming Unit Versions with Support Software
CX-Programmer version 5.0 can be used to confirm the unit version in the
Unit Manufacturing Information.
1. In the I/O Table Window, right-click on the FL-net Unit, and then select Unit
Manufacturing Information.
2. The following Unit Manufacturing Information Dialog Box will be displayed.
xxiv
7
Unit Versions of CS/CJ-series FL-net Units
The unit version is displayed.
Example: In this Unit Manufacturing Information Dialog Box, unit version 1.0 is
displayed. Use this dialog box to confirm the unit version of the FL-net Unit
that is connected online.
3. Using the Unit Version Labels
Unit version labels are provided with the FL-net Unit. These labels can be
attached to the front of FL-net Units to differentiate from previous FL-net
Units.
Unit Version Notation
The unit versions are indicated in this manual as follows:
Notation in product
Notation in this manual
nameplate
Ver.1.0 or later after CS/CJ-series FL-net Units
the lot number
with unit version 1.0 or later
Remarks
Information for which no particular version is specified
applies to all unit versions.
xxv
Unit Versions of CS/CJ-series FL-net Units
xxvi
7
SECTION 1
Features and System Configuration
This section introduces the overall structure of an FL-net (Ver. 2.00) network, outlines the features of the FL-net (Ver. 2.00)
Unit, describes the communications protocols used by an FL-net (Ver. 2.00) network, and provides basic precautions for
use of the network.
1-1
FL-net Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2
System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7
1-2-1
Device Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7
1-3
Related Programming Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8
1-4
Introducing the CX-FLnet Support Software . . . . . . . . . . . . . . . . . . . . . . . . .
8
1-2
1-5
Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9
1-6
Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
1-6-1
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
1-6-2
Ethernet and IEEE802.3 Standards. . . . . . . . . . . . . . . . . . . . . . . . . .
13
1
Section 1-1
FL-net Overview
1-1
FL-net Overview
FL-net is an open FA network that was standardized by the Japan FA Open
Systems Promotion Group (JOP) of the Manufacturing Science and Technology Center (MSTC) under the Ministry of International Trade and Industry
(MITI). It has been established in the Japan Electrical Manufacturers standards (JEM 1479) and is becoming very popular.
FL-net enables personal computers and FA controllers, such as programmable controllers (PLCs) or computerized numeric controllers (CNCs), by different manufacturers to be interconnected, controlled, and monitored, as shown
in the following diagram.
Personal
computer
Server
EWS
Computers
WAN
Host LAN Ethernet (TCP/IP, UDP)
FL-net Ethernet-based Control Network
PLC
PLC
PLC
Controllers
Personal
computer
CNC
RC
Field Network
Sensors
Devices
Actuators
FL-net Positioning
FL-net Unit specifications have been designed to conform to Japan Electrical
Manufacturers standards (JEM 1479: 2001). It cannot be connected to communications devices based on the previous standards (JEM 1479: 2000).
The most recent FL-net specifications can be downloaded from the home
page of the Japan Electrical Manufacturers Association (http://www.jemanet.or.jp/English/).
The following table shows the relationship between these standards and the
FL-net Units manufactured and sold by OMRON.
Unit name
FL-net Unit,
100Base-TX
FL-net (Ver. 2.00)
Unit, 10Base-5
FL-net (Ver. 2.00)
Unit, 10Base-T
FL-net Unit
Model
CJ1W-FLN22
CJ1W-FLN22
(See note 2.)
CS1W-FLN02
(See note 2.)
CS1W-FLN12
(See note 2.)
CS1W-FLN01
(See note 1.)
Note
Applicable standards
JEM1479: 2002
Manufacture and sales
With FL-net Ver. 2.0 specifications (OPCN-2).
JEM 1479: 2001
JEM 1479: 2001
JEM 1479: 2000
Under the guidance of the JEMA, communications
devices conforming to JEM 1479: 2000 specifications cannot be manufactured or sold after April,
2001.
1. The CS1W-FLN01 FL-net Unit cannot be connected to a network based on CS1WFLN02, CS1W-FLN12, CS1W-FLN22, or CJ1W-FLN22 FL-net Units.
2. CS1W-FLN02, CS1W-FLN12, CS1W-FLN22, or CJ1W-FLN22 FL-net Units cannot
be connected to a network based on the CS1W-FLN01 FL-net Unit.
2
Section 1-1
FL-net Overview
FL-net Features
FL-net System Concept
FL-net was designed to provide realtime communications between controllers
in manufacturing systems, such as programmable controllers (PLCs), robot
controllers (RCs), and computerized numeric controllers (CNCs). FL-net is
configured to broadcast tokens using the Ethernet UDP/IP protocols to enable
cyclic and message communications.
FL-net systems have the following features.
1. FL-net is an open system.
2. FL-net enables a multi-vendor network.
3. FL-net enables personal computers and FA controllers, such as programmable controllers (PLCs) or computerized numeric controllers (CNCs), by
different manufacturers to be interconnected, controlled, and monitored.
Application layer
FA link protocol layer
User application Interface
Cyclic transmission
FL-net
protocol
Message service
Message
transmission
Token management
Transport layer
UDP
Network layer
IP
Data link layer
Ethernet
(IEEE802.3 standard)
Physical layer
Figure 1 Basic Configuration of FL-net Protocol
Conforms to Widely Used Standards
Efficient communications can be achieved by this system based on Ethernet,
which has become the standard particularly for OA devices, combined with
standard UDP/IP. The use of Ethernet offers the following benefits.
1. Low cost
Configurations allowing the application of widely used communications devices reduces costs.
2. Compatible with existing network devices
Transceivers, hubs, cables, LAN cards for personal computers, and other
network devices widely used for Ethernet can be used.
3. Higher speeds
Baud rates are expected to improve in the future, increasing to100 Mbps,
and 1 Gbps.
4. Optical communications
By using devices such as optical repeaters, which are widely used with
Ethernet, optic fiber can be used for necessary components to enable
long-distance transmission of over 500 m, improved noise resistance, and
measures against lightning surge on outdoor wiring.
3
Section 1-1
FL-net Overview
Supports Required Functions between FA Controllers
User-defined specifications allow the following range of features that are
required for FA systems.
1. Large-scale network
Up to 254 devices (nodes) can be connected in the physical layer of the
network.
2. Dual communications functions to suit application
The Common Memory function uses cyclic transmission so that each node
can always share the same data with other nodes on the network. FL-net
also supports message communications for use when handling only essential data is required.
3. Large-capacity Common Memory
The Common Memory is provided with a large capacity of 8 Kbits and 8
Kwords.
4. High-speed response
High-speed response time of 50 ms/32 nodes (for 2 Kbits and 2 Kwords)
is provided.
The absence of a master in the FL-net network enables nodes to be added
or removed readily without affecting any other nodes. This allows any node
to be turned ON or OFF easily and facilitates maintenance.
General Differences between Ethernet and FL-net
1. FL-net is a network designed for FA environments and is not compatible
with all general-purpose Ethernet devices. Some devices are not suitable
due to noise resistance and environment resistance requirements.
2. Only FL-net-compatible controllers and control devices can be connected
to FL-net to meet the demands of control applications requiring responsiveness in realtime communications.
3. FL-net is a cyclic communications method using the broadcasting supported by UDP/IP protocols based on the 10Base-5 and 10Base-T standards.
The following restrictions currently apply.
• Compatible devices mainly use 10 Mbps Ethernet LAN.
• Connection to other general-purpose Ethernet systems is not supported.
• TCP/IP are not supported.
• Switching hubs cannot be used effectively.
• Routers and similar devices may not be compatible.
FL-net FAQ
Question
1
What is Ethernet?
2
What is FL-net?
4
Answer
Ethernet is a standard defining a type of cable. It is used in a local area network (LAN). An
Ethernet network transmits data between computers at a baud rate of between 10 Mbps and
100 Mbps. Currently, the most commonly used Ethernet in offices and other OA systems is
twisted-pair cable (UTP) that uses 10 Mbps. Ethernet communications are possible using
software protocols provided by many vendors.
The FL-net is a network to which programmable controllers (PLCs), computerized numeric
controllers (CNCs), and other FA controllers are connected, and on which control data is
exchanged between controllers at high speed. FL-net uses the same cables that are used for
Ethernet.
Section 1-1
FL-net Overview
Question
3
4
5
6
7
8
9
10
11
12
13
Answer
What is the difference between FLnet and Ethernet?
With Ethernet, the host computer, personal computers, and controllers are connected to the
network for data exchange and control applications, such as executing production instructions
and compiling results. The FL-net is used to connect controllers together and allow highspeed control data exchange.
Be sure to connect cables properly when installing both Ethernet for communications with the
host and FL-net for communications between controllers for the same controllers.
How are FL-net
FL-net Units are installed in FA controllers, such as programmable controllers (PLCs) and
Units used?
computerized numeric controllers (CNCs). By simply setting link allocations for the local node
address (node number) and Common Memory (also called link registers), FL-net Units transmit data between controllers cyclically in the same way as CPU Link Units in standard PLCs.
This method does not require special communications programs for the PLC and other Units
on the network. Such programs are also not required by the PLC for operations conducted via
the personal computer, including reading or writing data, such as the PLC memory or communications parameters. Separate programs are required for each controller, however, when
transmitting data between controllers using message communications.
What does “protoProtocol refers to rules for communications. The protocols supported by FL-net are UDP/IP
col” mean and what and FA Link Protocol. (The FA Link Protocol is located in the layer above UDP/IP and is a speprotocols does FL- cial protocol for use on FL-net networks.)
net support?
Can FL-net be con- The FL-net Unit, which is mounted to FA controllers such as programmable controllers (PLCs)
nected to a stanand computerized numeric controllers (CNCs), is an intelligent unit with a processor on its
dard personal
board. The Ethernet Card in the personal computer is a non-intelligent format called a “dumb
computer?
board,” so its capacity depends on the performance and functions of the personal computer.
Generally, an intelligent FL-net board is recommended.
What does “topolNetworking topology refers to the wiring formation of the network. The three main formations
ogy” mean?
are star (or tree), bus, and ring. Rather than physical wiring formations, however, it is easier to
understand them as theoretical formations. An FL-net system has star topology when using
10Base-T cables and bus topology when using 10Base-5 cables.
The most commonly used Ethernet cable standards and some of their characteristics and limWhat type and
itations are listed below. The figures in parentheses are applicable when repeaters are used.
length of network
cables are used,
• 10Base-T: Twisted-pair cables (UTP), maximum transmission distance is 100 m (500 m)
and how many Units
per segment, maximum number of Units is 254 per segment.
can be connected?
• 10Base-5: Thick coaxial cables (yellow cables), maximum transmission distance is 500 m
(2,500 m) per segment, and maximum number of Units that can be connected is 100
(254) per segment.
• 10Base-FL: Optic fiber cable, maximum transmission distance is 2,000 m per segment,
and maximum number of Units that can be connected is 254 per segment.
Do systems using
No. FL-net systems are configured using Ethernet (conforming to the IEEE802.3 standard).
FL-net require spe- Special specifications are not required.
cial Ethernet specifications?
How do you connect Ethernet cables for different types of Ethernet media can be connected to each other using
to FL-net?
repeaters, media adapters, and other devices. These products are available from many vendors.
What type of cables In general, use the following cables.
should be used
• Basic wiring: 10Base-5 Thick coaxial cables; yellow cables.
when configuring an
• In the control panel and in offices: 10Base-T twisted-pair cables; UTP category 5.
FL-net system?
• High-voltage wiring and noise-prone environments: 10Base-FL optic-fiber cables.
How is the FL-net IP The FL-net IP address is set as follows:
address set?
Network address: 192.168.250
Host number (node number): 1 to 254 is standard. Nodes 250 to 254, however, are reserved
for maintenance devices.
How compatible and FL-net has a certification system whereby compatibility and inter-connectivity tests are perinter-connectable
formed.
are devices that
Certification documents are provided for those devices that pass the tests, so devices supsupport FL-net?
porting FL-net can be used safely on the network.
5
Section 1-1
FL-net Overview
OMRON FL-net Unit (100Base-TX) Features
High-speed
Communications at
100 Mbps
A baud rate of 100 Mbps is supported. The baud rate can be automatically
selected or a fixed baud rate of 10 Mbps can be set.
Specify the Order of Data
Link Data
The order of upper/lower bytes in data link data (word data) can be specified
for each node before sending or receiving the data, according to the specifications of the device connected in the data link.
FINS Message
Communications
The FL-net Unit also supports FINS message communications, OMRON’s
standard communications service, so other OMRON PLCs can be accessed
by using SEND(090), RECV(098), and CMND(490) instructions in ladder programs. In addition, the FINS gateway function can be used to allow access to
other PLCs on not only the same FL-net network but also on other networks
such as Ethernet or Controller Link.
Controller Link Network
Connection
Ethernet, the information-system network, can be connected to Controller
Link, the control-system network, using the FINS communications service.
This allows a PLC on the Ethernet or Controller Link network to be monitored
from an OMRON PLC on the FL-net network, and, conversely, for data to be
exchanged between a PLC on the Ethernet or Controller Link network and an
OMRON PLC on the FL-net network.
Abundant
Troubleshooting
Functions
The Ethernet Unit is provided with a variety of troubleshooting functions for
prompt recovery in case of errors.
• Self-diagnostic function at startup
• PING command for checking other nodes
• Inter-nodal tests for checking other nodes
• Error log for recording error history data
6
Section 1-2
System Configuration
1-2
System Configuration
1-2-1
Device Configuration
10Base-T
Terminator
Transceiver
Other company's
FL-net (Ver. 2.0) node
10Base-T
50 m max.
Transceiver cable
CS/CJ-series
CS1W-FLN22 or
CJ1W-FLN22
FL-net Unit
FL-net (Ver. 2.00) (10 Mbps)
500 m/segment max.
10Base-5 coaxial cable
(or 10Base-T twisted-pair cable)
Between nodes:
Integral multiples of 2.5 m
CS-series
PLC
Terminator
Ground
Hub
100 m max.
CS-series
CS1W-FLN12
FL-net (Ver. 2.00) Unit
(10Base-T)
Other company's
FL-net (Ver. 2.0) node
10Base-T
DeviceNet
CS-series
DeviceNet Unit
Remote Terminal
Sensor
Actuator
100Base-TX
Hub
CX-Programmer
Twisted-pair
cable
Hub
100 m max.
CS-series PLC
Hub
100 m max.
CS-series
CJ1W-FLN22
FL-net Unit
(100Base-TX)
100 m max.
CS-series
CS1W-FLN22
FL-net Unit
(100Base-TX)
CS-series
CS1W-FLN22
FL-net Unit
(100Base-TX)
Other company's
FL-net node
100Base-TX
DeviceNet
CS-series DeviceNet Unit
Remote Terminal
Sensor
Actuator
Note Do not combine nodes using a baud rate of 10 Mbps with nodes using a baud
rate of 100 Mbps in the same configuration, where possible. If nodes with a
baud rate of 10 Mbps are used, use a baud rate of 10 Mbps for all the connected devices in the configuration.
7
Section 1-3
Related Programming Devices
1-3
Related Programming Devices
The FL-net Unit functions as a node on the FL-net network. The basic settings
for operation are made in the CPU Bus Unit System Setup in the CS/CJseries CPU Unit. Use the CX-FLnet or FL-net Unit Support Software to make
the settings.
Personal computer running Windows
CX-FLnet or FL-net Unit Support Software
CPU Bus Unit
System Setup
Screen
FL-net Unit
CS/CJ-series CPU Unit
The following items are included in the Setup Area.
Screen
Setup Screen
Item
FA Link mapping table method
FA Link startup method
Message protocol confirmation
Broadcast type
IP address setting method
Subnet mask
Baud rate
Local node setup area
Default
PLC built-in method
Automatic participation
Yes
***.***.***.255
192.168.250.node number
255.255.255.0
10 Mbps
Not set.
50
50
50
50
50
50
50
50
Page
Other node setup area
Not set.
50
Data order setting
No swapping (sequential order)
79
When using the default values that are already stored in the CS/CJ-series
CPU Unit, there is no need to make any settings with the CX-FLnet or FL-net
Unit Support Software. Refer to 4-2 CPU Bus Unit System Setup for details on
the above settings.
1-4
Introducing the CX-FLnet Support Software
The FL-net Unit Support Software can be installed from the CX-One FA Integrated Tool Package (version 1.1 or higher) as the CX-FLnet. The following
table compares the FL-net and CX-FLnet. Other aspects are the same.
Item
Obtaining the software
Simultaneously being online with
other Programming Device software that uses the CX-Server,
such as the CX-Programmer
Starting the software
8
Previous Support Software:
FL-net version 1.6
Downloaded from the OMRON Industrial
Website.
Not possible.
New Support Software:
CX-FLnet
Provided with CX-One version 1.1 or
higher ([email protected]@C-E)
Possible.
From the Windows Start Menu
From the Windows Start Menu or from the
I/O Table Window of the CX-Programmer
installed from CX-One. (Right-click the
FL-net Unit and use the pop-up menu.)
Section 1-5
Specifications
1-5
Specifications
CS-series FL-net Units
Item
Model number
Type
Applicable PLCs
Unit classification
Mounting location
Number of Units that can be
mounted
Transfer Media access method
specifiModulation
cations
Transmission paths
Specifications
CS1W-FLN22
100Base-TX (10Base-T is also possible)
CS-series PLCs
CS-series CPU Bus Unit
CPU Rack or Expansion Rack
4 max. (including Expansion Racks)
CSMA/CD
Baseband
Star
Baud rate
Transmission media
100 Mbps (100Base-TX)
10 Mbps (10Base-T)
Unshielded twisted-pair (UTP) cable
Unshielded twisted-pair (UTP) cable
Categories: 5, 5e
Categories: 3, 4, 5, 5e
Shielded twisted-pair (STP) cable
Shielded twisted-pair (STP) cable
Categories: 100 Ω at 5, 5e
Categories: 100 Ω at 3, 4, 5, 5e
Transmission distance 100 m max. (distance between hub and node)
2
4
Number of cascade
connections with
repeater hub
Current consumption (Unit)
380 mA max. at 5 VDC
Vibration resistance
Conforms to JIS 0040.
10 to 57 Hz, 0.075-mm amplitude, 57 to 150 Hz, acceleration: 9.8 m/s2 in X, Y, and Z
directions for 80 minutes each
(Time coefficient; 8 minutes × coefficient factor 10 = total time 80 minutes)
Shock resistance
Conforms to JIS 0041.
147 m/s2 three times each in X, Y, and Z directions
Ambient temperature
Operating: 0 to 55°C
Storage: –20 to 75°C
Humidity
10% to 90% (with no condensation)
Atmosphere
Must be free from corrosive gas.
Weight
200 g max.
Dimensions
35 × 130 ×101 mm (W × H × D)
9
Section 1-5
Specifications
CJ-series FL-net Units
Item
Model number
Type
Applicable PLCs
Unit classification
Mounting location
Number of Units that can be
mounted
Transfer Media access method
specifiModulation
cations
Transmission paths
Baud rate
Transmission media
Specifications
CJ1W-FLN22
100Base-TX (10Base-T is also possible)
CJ-series PLCs
CJ-series CPU Bus Unit
CPU Rack or Expansion Rack
4 max. (including Expansion Racks)
CSMA/CD
Baseband
Star
100 Mbps (100Base-TX)
10 Mbps (10Base-T)
Unshielded twisted-pair (UTP) cable
Unshielded twisted-pair (UTP) cable
Categories: 3, 4, 5, 5e
Categories: 5, 5e
Shielded twisted-pair (STP) cable
Shielded twisted-pair (STP) cable
Categories: 100 Ω at 5, 5e
Categories: 100 Ω at 3, 4, 5, 5e
Transmission distance 100 m max. (distance between hub and node)
2
4
Number of cascade
connections with
repeater hub
Current consumption (Unit)
370 mA max. at 5 VDC
Vibration resistance
Conforms to JIS 0040.
10 to 57 Hz, 0.075-mm amplitude, 57 to 150 Hz, acceleration: 9.8 m/s2 in X, Y, and Z
directions for 80 minutes each
(Time coefficient; 8 minutes × coefficient factor 10 = total time 80 minutes)
Shock resistance
Conforms to JIS 0041.
147 m/s2 three times each in X, Y, and Z directions
Ambient temperature
Operating: 0 to 55°C
Storage: –20 to 75°C
Humidity
10% to 90% (with no condensation)
Atmosphere
Must be free from corrosive gas.
Weight
100 g max.
Dimensions
31 × 90 × 65 mm (W × H × D)
10
Section 1-5
Specifications
Dimensions
CS1W-FLN22
FLN22
100M
PER
LNK
MSG
TS
RUN
HER
TX
RX
UNIT
NO.
NODE
NO.
0
0
1
160
130
161
100BASE-TX
10BASE-T
35
101
(Unit: mm)
CJ1W-FLN22
65
2.7
31
FLN22
HER
TX
RX
100M PER
RUN
LNK
MSG
EF01
6789
2345
ABCD
EF01
6789
2345
TS
UNIT
No.
NODE
No.
x161
ABCD
EF01
6789
2345
ABCD
90
x160
2.7
100BASE-TX
10BASE-T
(Unit: mm)
11
Section 1-5
Specifications
Comparison with Previous Models (CS1W-FLN02, CS1W-FLN12)
Model
Type
CS1W-FLN22
CJ1W-FLN22
100Base-TX (10Base-T is also possible)
Switches/indica- 100M indicator provided
tors
This indicator indicates when baud rate of 100
Mbps is being used.
No rotary switch for setting the IP address.
The IP address is set using the CX-FLnet or FLnet Unit Support Software. Either of the following
two methods can be used to set the IP address.
1. 192.168.250 + node number
2. Setup area
Data link functions
CS1W-FLN02/12
10Base-5 (CS1W-FLN02)
10Base-T (CS1W-FLN12)
No 100M indicator
Rotary switch provided on rear of Unit for setting
the IP address. Either of the following four methods can be used to set the IP address
1. 192.168.250 + node number
2. Rotary switch on rear of Unit.
3. Rotary switch on rear of Unit + node number
4. Setup area
Total capacity: 8,704 words
Total capacity: 8,704 words
(Area 1: 512 words, Area 2: 8,192 words)
(Area 1: 512 words, Area 2: 8,192 words)
Data link tables that exceed the following condiIf the total number of words in Area 1 and Area 2 tions, however, cannot be set.
for a single node exceeds 7,677 words, the data
Number of words in local node setup area (Area 1
for the corresponding node will be refreshed over and Area 2) ≤ 7,677 words.
two scans of the CPU Unit. The data will be split
Number of words in local node setup area (Area 1
from the 7,678th word counted from the beginning and Area 2) + the number of words in setup area
of the combined Area 1 and Area 2.
(Area 1 and Area 2) for node with the largest setup
area size (except local node) ≤ 7,677 words
The order of the upper and lower byte in the word The data order cannot be changed and is fixed as
shown in the following diagram.
data can be swapped for each node when
exchanging data between the data link area in the
Common memory
PLC and the FL-net.
MSB
LSB
PLC memory area
D15
Simple backup
function
Support Software
Supported.
0
Not supported.
CX-FLnet or FL-net Unit Support Software version FL-net Unit Support Software Ver. 1.51 or higher
(CS1W-FLN02 and CS1W-FLN12 settings can
1.60 or higher (CS1W-FLN22 and CJ1W-FLN22
settings cannot be made using Ver. 1.51 or lower) also be made using Ver. 1.60 or higher)
Comparison between FL-net Unit Support Software
Version
CX-FLnet or
FL-net Unit Support Software Ver. 1.60
New setting
Set the baud rate.
function
Set the data link data order.
Connection with Set/monitor other nodes via the FL-net network.
PLC
Setting file
Setting files saved from Japanese version and
English version are compatible.
12
Ver. 1.51
None (these settings are not available)
Only the local node can be set or monitored.
No compatibility between setting files saved in the
English version and Japanese version.
Section 1-6
Precautions
1-6
Precautions
Be sure to observe the following precautions when installing and using an FLnet Unit.
1-6-1
Installation
Observe the following precautions when installing an FL-net Unit.
1,2,3...
1. Use transceiver cable that meets IEEE802.3 standards to ensure high
noise resistance.
2. Use a transceiver with a current consumption of not more than 0.4 A per
port.
3. Always turn OFF the power supply to the PLC before connecting or disconnecting the transceiver cable.
4. Be sure not to exceed the current capacity of the Power Supply Unit on the
Rack to which the FL-net Unit is mounted. The current consumption is 380
mA maximum for the CS-series FL-net Unit and 370 mA for the CJ-series
FL-net Unit. This value added to the current consumption of all other Units
mounted to the same Rack must not exceed the capacity of the Power
Supply Unit.
5. Do not install the transceiver cables or coaxial cables of the network near
power supply lines. If installation near possible sources of noise is unavoidable, install the cables in grounded metal ducts or take other measure to
eliminate noise interference.
1-6-2
Ethernet and IEEE802.3 Standards
The FL-net Unit was designed based on Version-2.0 Ethernet standards and
not on the international IEEE802.3 standards, which were developed based
on Ethernet specifications. Although these two sets of standards are similar,
they are not necessarily the same. Particularly, different frame formats are
used, making direct communications impossible between systems that do not
support the same standards. Standards for equipment used to configure networks are the same, allowing IEEE802.3-standard equipment to be used with
the FL-net Unit. In particular, the transceiver cable for the IEEE802.3 standards provides superior noise resistance and should be used for the FL-net
Unit.
Terminology also differs between Version-2.0 Ethernet and IEEE802.3 standards. These differences are shown in the following table. Version-2.0 Ethernet terminology is used in this manual.
Ethernet
Transceiver
Transceiver cable
Ethernet address
Ethernet
IEEE802.3
MAU
AUI
MAC address
10Base-5/10Base-T
13
Precautions
14
Section 1-6
SECTION 2
Communications Functions
This section describes the communications functions that can be used with the FL-net (Ver. 2.00) Units.
2-1
FL-net . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16
2-2
Cyclic Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
20
2-3
Message Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
2-4
FINS Communications Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22
15
Section 2-1
FL-net
2-1
FL-net
FL-net Concept
FL-net is an Ethernet-based FA control network.
FL-net supports both cyclic transmission and message transmission functions.
The basic concepts of FL-net are as follows:
1,2,3...
1. To use Ethernet as the medium for communications between FA controllers.
2. To offer UDP/IP, which are widely used protocols in Ethernet communications, as the basic means for data communications.
3. To manage and control access of each node in the network to the communications media (to avoid collisions) and to ensure transmission within a
fixed time period, while using the above-mentioned basic means for data
communications.
FL-net is an FA control network enabling the exchange of data between control devices in manufacturing systems, such as programmable controllers
(PLCs), robot controllers (RCs), and computerized numeric controllers
(CNCs), and personal computers used for controlling them.
The following diagram shows the location of devices in an FL-net system.
Personal
computer
Personal
computer
Personal
computer
Server
EWS
Computers
WAN
Host LAN Ethernet (TCP/IP, UDP)
FL-net Ethernet-based Control Network
PLC
PLC
PLC
Controllers
Personal
computer
CNC
DeviceNet or other network
Sensors
Devices
16
Actuators
OMRON CX-FLnet or
FL-net Unit Support Software
RC
Section 2-1
FL-net
FL-net Protocol
FL-net consists of six protocol layers, as shown in the following diagram.
Application layer
User application Interface
Message service
Cyclic transmission
Message transmission
FA link protocol layer
FL-net
Protocol
Token management
Transport layer
UDP
Network layer
IP
Data link layer
Ethernet
(IEEE802.3 standard)
Note The transport and network layers use UDP/IP, whereas Ethernet is used as
the protocol for the data link and physical layers.
FL-net Transmission
Features
1,2,3...
FL-net's FA link protocol layer is characterized by the following features.
1. Collisions are avoided by transmission control that uses the token method
that does not use a master.
2. The refresh cycle time can be regulated by fixing the cycle time of the token.
3. The designated token is transmitted together with cyclic data.
4. The token is transmitted first by the node that has the smallest number at
startup.
5. When no token is transmitted in a specified period of time, the next node
in the token rotation order sends a new token.
6. This token method prevents the network from stopping when there is a failure of only some of the nodes.
7. The information management tables provide useful information, such as
operation mode (RUN/STOP) and hardware malfunctions (ALARM), that
can be referenced to monitor the operating status of other nodes.
FL-net IP Addresses
Unique class-C IP addresses must be assigned to each node in the FL-net
network.
An IP address is an address identifying each node (station) for transmission
using IP (internet protocol). Therefore, IP addresses must be set and managed so that no two nodes have the same IP address. FL-net uses Class-C IP
addresses. The default IP address for FL-net is 192.168.250.***, with *** representing the remote node number.
FL-net (Ver.
2.00) IP
address
Network address
192.168.250
Host number
(node number)
n (n: 1 to 254)
17
Section 2-1
FL-net
Number of Connectable
Nodes and Node Numbers
Up to 254 nodes can be connected to an FL-net network. Each node is
assigned a node number from 1 to 254.
Node number
1 to 249
250 to 254
255
0
Note
Applications
Used for standard FL-net devices.
Used for FL-net maintenance purposes.
Reserved for the internal system use. (See notes 1 and 2.)
Reserved for internal system use. (See note 1.)
1. Not available to users.
2. Used for broadcasting.
FL-net
Network address
Node number
192.
192.
192.
192.
192.
192.
168.
168.
168.
168.
168.
168.
250.
250.
250.
250.
250.
250.
1
2
248
249
250
254
Node number: 1 to 249 (for users)
Data Communications
FL-net supports data communications by cyclic transmission and message
transmission.
Cyclic data with token
Cyclic transmission
Transmission Cycle
Node number: 250 to 254
(for maintenance)
Message data
Cyclic transmission + message transmission
With cyclic communications, the Common Memory is refreshed on a fixed
cycle time. Message communications are controlled so that the Common
Memory refresh time does not exceed the allowable refresh cycle time.
Each node constantly monitors the message communications frames that
travel through the network from the time it receives one local-node-directed
token until it receives the next local-node-directed token. When no message
communications frame travels through the network in a single cycle, 120% of
the cycle time value becomes the allowable refresh cycle time. In this way the
allowable refresh cycle time is actively determined according to the number of
nodes in the network.
18
Section 2-1
FL-net
Data Areas and Memory
FL-net
FL-net Communications Unit
CPU Unit
Message transmission
Cyclic transmission
Common Memory Area 1
Common Memory Area 2
Message transmission buffer area
FL-net management table area
Physical memory
FL-net parameter area
Communications
Management Tables
Node status is managed using three types of management tables: Local node
management tables, participating node management tables, and network
management
Local Node Management
Table
The local node management table manages the local node settings.
Item
Node number
Common Memory Area 1 first word
Common Memory Area 1 data size
Common Memory Area 2 first word
Common Memory Area 2 data size
Upper layer status
Token monitoring time
Minimum allowable frame interval
Vendor code
Manufacturer model
Node name (equipment name)
Protocol version
FA link status
Local node status
Bytes
1 byte
2 bytes
2 bytes
2 bytes
2 bytes
2 bytes
1 byte
1 byte
10 bytes
10 bytes
10 bytes
1 byte
1 byte
1 byte
Contents (data range)
1 to 249
Word address (0 to 0xff)
Size (0 to 0x200)
Word address (0 to 0x1fff)
Size (0 to 0x2000)
RUN/STOP /ALARM/WARNING/NORMAL
Unit: 1 ms
Unit: 100 µs
Vendor code
Manufacturer model, device name
User-defined node name
0x80 (fixed)
Participating, not participating, etc.
Duplicate node number detection, etc.
Note “0x0012ab” refers to hexadecimal 0012AB.
19
Section 2-2
Cyclic Transmission
Participating Node
Management Table
The participating node management table manages information on the nodes
in the network.
Node number
Upper layer status
Item
Bytes
1 byte
2 bytes
Common Memory Area 1 data first word
Common Memory Area 1 data size
Common Memory Area 2 data first word
Common Memory Area 2 data size
Minimum allowable refresh cycle time
Token monitoring time
Minimum allowable frame interval
Link status
2 bytes
2 bytes
2 bytes
2 bytes
2 bytes
1 byte
1 byte
1 byte
Contents (data range)
1 to 254
RUN/STOP /ALARM/WARNING/NORMAL
Word address (0 to 0x1ff)
Size (0 to 0x200)
Word address (0 to 0x1fff)
Size (0 to 0x2000)
Unit: 1 ms
Unit: 1 ms
Unit: 100 ms
Participating, not participating, etc.
Note “0x0012ab” refers to hexadecimal 0012AB.
Network Management
Table
The network management table manages information that is shared by all
nodes on the network.
Item
Token holding node number
Minimum allowable frame interval
Allowable refresh cycle time
Refresh cycle measurement value
(current)
Refresh cycle measurement value
(maximum)
Refresh cycle measurement value
(minimum)
2-2
Bytes
1 byte
1 byte
2 bytes
2 bytes
Contents (data range)
Node currently holding the token
Unit: 100 µs
Unit: 1 ms
Unit: 1 ms
2 bytes
Unit: 1 ms
2 bytes
Unit: 1 ms
Cyclic Transmission
Cyclic transmission is used to transmit cyclic data. The data is shared by each
node through the Common Memory (shared memory) function.
Token
Data
FL-net
Node 1
Node 2
Node 3
Node...
Node n
Node 1
Node 1
Node 1
Node 1
Node 1
Node 2
Node 2
Node 2
Node 2
Node 2
Node 3
Node 3
Node 3
Node 3
Node 3
Node 4
Node 4
Node 4
Node 4
Node 4
Node...
Node...
Node...
Node...
Node...
Node n
Node n
Node n
Node n
Node n
Common
Memory
Note Cyclic transmission allows PLCs made by OMRON to communicate with
PLCs made by other companies.
20
Message Transmission
Section 2-3
Volume of Transmission
Data
An area of 0.5 Kwords + 8 Kwords = 8.5 Kwords is provided for the whole network.
The maximum quantity of data that can be transmitted by a single node is
8.5 Kwords. One word is equal to two bytes.
15
0
2
2
Area 1
0.5 Kwords
Kw
Common Memory Area
Area 2
2-3
8 Kwords
Message Transmission
Message transmission is used to transmit non-cyclic data.
Normally, when a send request is generated, data is transmitted to a specific
node.
Message transmission from node 1 to node 3
Message transmission from node 6 to node 4
FL-net
1
Note
2
3
4
5
6
1. Message transmission allows OMRON PLCs to communicate with other
manufacturer’s PLCs.
2. Message transmission is performed between OMRON PLCs by executing
the SEND(090), RECV(098), and CMND(490) instructions.
3. Message transmission is performed between OMRON PLCs and other
manufacturer’s PLCs by executing the CMND(490) instruction.
Message Transmissions
The maximum size of one message frame is 1,024 bytes (not including the
header).
Message frame
1,024 bytes
21
Section 2-4
FINS Communications Service
2-4
FINS Communications Service
FINS commands or data can be sent to or received from other manufacturer’s
PLCs on the same FL-net network by executing SEND(090), RECV(098), or
CMND(490) instructions in the user’s ladder diagram program in the CPU
Unit. This enables control operations such as the reading and writing of I/O
memory between PLCs, mode changes, and file memory operations. (When a
FINS message is sent on an Ethernet network, a UDP/IP header is automatically added to the message.)
The FINS gateway function allows access not only to OMRON PLCs on the
same FL-net network, but also to PLCs on other networks such as SYSMAC
LINK or Controller Link.
User program
FinsGateway API
Ethernet
IP UDP FINS
FL-net Unit
FL-net Unit
FL-net Unit
CS-series
PLC
Ethernet Unit
FL-net
IP UDP FL-net FINS
IP UDP FL-net FINS
User program
SEND/RECV
instruction or
CMND instruction
The FINS communications service allows PLC Programming Devices like the
CX-Programmer to be used with a remote PLC.
CX-Programmer
Ethernet
IP UDP FINS
FL-net Unit
FL-net Unit
CS-series
PLC
Ethernet Unit
FL-net
IP UDP FL-net FINS
Note
1. The FINS communications service can send messages between OMRON
PLCs.
2. It cannot send messages to other manufacturer’s PLCs.
22
Section 2-4
FINS Communications Service
Message Data Length
The FL-net Unit creates FINS communications messages through FL-net
message transmission. Maximum length for a FINS communications message is 1,024 bytes (including the FINS header and text).
FL-net message frame
1,024 bytes
FINS header
10 bytes
FINS header
10 bytes
Command
code
Text
2 bytes
1,012 bytes
Command Completion
code
code
2 bytes
2 bytes
Text
1,010 bytes
23
SECTION 3
Startup Procedure
This section explains the procedure for starting up the FL-net (Ver. 2.00) Unit, including mounting to the PLC, making the
required settings, and checking communications.
3-1
Before Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26
3-2
Initial Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
27
3-3
Nomenclature and Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
28
3-4
Hardware Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30
3-5
Mounting to the PLC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
33
3-6
3-7
3-8
3-9
Network Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
34
3-6-1
Basic Installation Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
34
3-6-2
Recommended Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
35
3-6-3
Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
35
3-6-4
Noise Reduction when Using Contact Outputs . . . . . . . . . . . . . . . .
37
Connecting to the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
38
3-7-1
Ethernet Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
38
3-7-2
Connecting the Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
38
Creating an I/O Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
39
3-8-1
I/O Table Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
39
3-8-2
Connecting Programming Devices to the PLC. . . . . . . . . . . . . . . . .
39
3-8-3
Procedure for Creating an I/O Table. . . . . . . . . . . . . . . . . . . . . . . . .
40
Creating Routing Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
40
3-9-1
Routing Table Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
41
3-9-2
Connecting and Using a Peripheral Device for the PLC . . . . . . . . .
42
3-10 System Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45
3-10-1 When Settings are Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45
3-10-2 Using the CX-FLnet or FL-net Unit Support Software . . . . . . . . . .
45
3-10-3 CPU Bus Unit System Setup Defaults . . . . . . . . . . . . . . . . . . . . . . .
45
3-11 Checking Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
46
3-11-1 PING Command and Internode Testing . . . . . . . . . . . . . . . . . . . . . .
46
3-11-2 PING Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
46
3-11-3 Internode Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
46
25
Section 3-1
Before Operation
3-1
Before Operation
Precautions
Observe the following precautions when installing and using an FL-net Unit.
Installation Precautions
Observe the following precautions when installing an FL-net Unit.
• Make sure that all of the nodes in the network are CS1W-FLN22, CJ1WFLN22, CS1W-FLN02, or CS1W-FLN12. CS1W-FLN01 FL-net Units cannot be connected.
FL-net network
version
V2.00
V.100
Supported FL-net Units
CS1W-FLN22
CJ1W-FLN22
CS1W-FLN02
CS1W-FLN12
CS1W-FLN01
• Use a transceiver cable that complies with the IEEE802.3 standards to
ensure high noise resistance.
• Use a transceiver with a current consumption of not more than 0.4 A per
port.
• Always turn OFF the power supply to the PLC before connecting or disconnecting the transceiver cable.
• The current consumption of the FL-net Unit is 400 mA maximum. Make
sure that the total current consumption of all Units mounted to the PLC is
mounted does not exceed the capacity of the Power Supply Unit.
• Do not lay the coaxial cables and transceiver cables of the network near
power lines. If installation near possible noise sources is unavoidable, be
sure to take adequate measures against noise interference, such as
installing cables in metal ducts.
Restrictions on Number of
Data Link Nodes
The maximum number of data link nodes that can be used with the FL-net
Unit is 96 when links are stored in the CPU Unit, and 128 when links are
stored in the FL-net Unit.
Restrictions on Data Link
Capacity for Each Node
In the Data Link Area for each FL-net Unit node up to 512 words can be allocated in Area 1 and up to 8,192 words can be allocated in Area 2. The total
number of words that can be allocated in Areas 1 and 2 combined is 8,704
words.
Restrictions on Data Link
Data Concurrency
Concurrency of data within each node is assured (concurrency of data
between all nodes is not assured).
If the data size of Area 1 and Area 2 for a single node exceeds 7,677 words,
however, the data for the corresponding node will be refreshed over two CPU
Unit cycles. Therefore, concurrency will be lost. The data will be split for
refreshing at 7,677 words counted from the beginning of Area 1. If a communications packet is corrupted for some reason, the data prior to the packet
being sent will be retained. When four consecutive token holding timeouts are
detected, the corresponding node in the Status Area will leave the network
and then rejoin it, but the PLC data will be held in its previous state.
The data for Area 1 and Area 2 from the same node will be refreshed in the
same CPU Unit cycle or Area 2 will be refreshed first. If concurrency is
required between the data in Area 1 and Area 2, use refreshing of the data in
Area 1 as a trigger before accessing data from Area 2.
Restrictions on Message
Transmissions
26
When sending messages to other manufacturer's FL-net units, set the message procedure confirmation setting to no confirmation.
Section 3-2
Initial Setup
Mounting FL-net
Units
• Up to four FL-net Units can be mounted to a single PLC.
• The current consumption of the FL-net Unit is 380 mA maximum for
CS1W-FLN22 and 370 mA maximum for CJ1W-FLN22. (The power supply to the transceiver is not included; it is supplied by the 24-VDC power
supply connected to the power supply terminals on the Unit.)
Make sure that the total current consumption of all Units mounted to the
CPU Backplane or Expansion Backplane to which the FL-net Unit is
mounted does not exceed the capacity of the Power Supply Unit.
Size = 32 + 10 × Number of remote nodes set (96 nodes max.)
Allocated Size when
Remote Node Allocation
Data is Stored in CPU Unit
Maximum size: 992 bytes (per Unit)
Allocated Size when
Remote Node Allocation
Data is Stored in FL-net
(Ver. 2.00) Unit
3-2
Size = 32 (Number of remote nodes set: 128 nodes max.)
Maximum size: 32 bytes (per Unit)
When the allocation data for remote nodes is stored in the FL-net Unit, the
CPU Unit System Setup size is 32 bytes per Unit regardless of the number of
remote nodes set.
Initial Setup
Item
Set the hardware switch.
Mount the Unit to the Backplane.
Connect to the network.
Turn ON the CPU Unit.
Create I/O tables.
Create routing tables.
System Setup
Restart the Unit.
Procedure
Set a unique number for the Unit so it can operate as a
CPU Bus Unit.
Mount the Unit to the Backplane.
References
3-4 Hardware Setup
Connect the Unit to the network using the transceiver
cable.
Turn ON the power supply to the CPU Unit.
Register the FL-net (Ver. 2.00) Unit in the CPU Unit using
the CX-Programmer.
Always create routing tables for using message communications when multiple CPU Bus Units are mounted to the
same PLC.
Set the operating parameters for the FL-net (Ver. 2.00) Unit
using the CX-FLnet or FL-net Unit Support Software.
3-7 Connecting to the Network
--3-8 Creating an I/O Table
3-5 Mounting to the PLC
3-9 Creating Routing Tables
SECTION 11 CX-FLnet
Support Software Operations
Restart the Unit (turn ON the power again) so that the data --in the System Setup can be read.
27
Section 3-3
Nomenclature and Functions
3-3
Nomenclature and Functions
This section explains FL-net Unit part names, settings, and LED indicators.
Part Names
CS1W-FLN22, 100Base-TX
FLN22
RUN
100M
HER
TX
PER
LNK
RX
MSG
TS
LED Indicators
Display the operating status of the Unit.
UNIT
NO.
Unit Number Switch
Sets the unit number in one digit hexadecimal.
NODE
NO.
×161
×160
Node Number Switches
Set the Unit's FINS node number in two digits hexadecimal.
100BASE-TX
10BASE-T
Ethernet Connector
Connects the Ethernet transceiver cable.
CJ1W-FLN22, 100Base-TX
Slider
Used to mount Units together.
LED Indicators
Display the operating status of the Unit.
FLN22
RUN
HER
TX
RX
100M
PER
LNK
MSG
TS
UNIT
NO.
NODE
NO.
×161
Unit Number Switch
Sets the unit number in one digit hexadecimal.
Node Number Switches
Set the Unit's FINS node number in two digits hexadecimal.
×160
100BASE-TX
10BASE-T
Ethernet Connector
Connects the Ethernet transceiver cable.
DIN Track Mounting Pin
Used to mount the Unit to the DIN Track.
Slider
Used to mount Units together.
28
Section 3-3
Nomenclature and Functions
Individual Ethernet addresses are assigned to all communications devices
connected to an Ethernet system. With the FL-net Unit, the Ethernet address
is shown in 12 digits, hexadecimal, on the right side of the Unit.
CS1W-FLN22
FL-net UNIT
Ethernet address (12 digits)
Note The Ethernet address can also be checked by means of the FINS command
CONTROLLER DATA READ (page 107).
LED Indicators
The following table shows the meanings of the LED indicator status.
CS1W-FLN22 (100Base-TX)
FLN22
RUN
HER
TX
RX
Name
CS
100M
PER
LNK
MSG
TS
Indicator
RUN
RUN
Color
Green
Display
Not lit.
HER
Unit Error
Red
Lit.
Not lit.
Lit.
Flashing.
PER
CPU Unit Error
Red
TX
Sending Data
Yellow
RX
Receiving Data
Yellow
LNK
Servicing FA Link
Yellow
Not lit.
Lit.
Flashing.
Not lit.
Lit.
Not lit.
Lit.
Not lit.
Lit.
CJ1W-FLN22 (100Base-TX)
FLN22
RUN
HER
TX
RX
100M PER
LNK
MSG
TS
Operating status
The Unit has not completed initialization.
Unit hardware error.
Normal operation.
Unit normal.
Hardware error in Unit, FROM error,
EEPROM error, or node address setting
error (node address is FF).
IP address setting error.
Node address setting error (node address is
0).
CPU Unit normal.
CPU Unit error.
CPU Unit interface error.
I/O table error.
Routing table setting error.
System setup data error.
Unit number setting error (unit number duplication)
Failure to read internal parameters from
Memory Card.
Data link area allocation error
Not sending data. (Ready to send.)
Sending data.
Not receiving data. (Ready to receive.)
Receiving data.
Not connected to FA Link Network.
Connected to FA Link Network.
29
Section 3-4
Hardware Setup
Indicator
MSG
Name
Color
Transferring Messages Yellow
Display
Not lit.
Lit.
100M
100 Mbps Baud Rate
Green
TS
Internode Testing
Yellow
3-4
Not lit.
Lit.
Not lit.
Lit.
Operating status
Not transferring messages (including remote
access from CX-Programmer or other Programming Device).
Transferring messages (including remote
access from CX-Programmer or other Programming Device).
Communicating at 10 Mbps
Communicating at 100 Mbps
Not running internode test.
Running internode test.
Hardware Setup
This section explains how to set the various switches on the FL-net Unit.
Setting the Unit Number
The unit number is used to identify individual CPU Bus Units when more than
one CPU Bus Unit is mounted to the same PLC. Use a small screwdriver to
make the setting, taking care not to damage the rotary switch. The unit number is factory-set to 0.
Setting range
0 to F
CS-series
Note
CJ-series
1. Turn OFF the power supply before setting the unit number.
2. If the unit number is being set for the first time or changed, then an I/O table
must be created for the PLC.
■ Unit Number and CPU Bus Unit Allocations
With CS/CJ-series PLCs, words are automatically allocated in the CIO Area
and the DM Area according to the unit numbers that are set. The FL-net Unit
uses these words for receiving control data from the CPU Unit and for notifying the CPU Unit of FL-net Unit and communications status. The word
addresses in the allocated areas for the CPU Bus Unit are important in creating the user program for using the FL-net Unit, so be careful to take them into
account when setting the unit number.
The following table shows the areas allocated for the CPU Bus Unit by unit
number. This table only shows the correspondences between unit numbers
and the words allocated for the CPU Bus Unit. For details, refer to SECTION 4
System Setup and Memory Allocations.
30
Section 3-4
Hardware Setup
Words Allocated in CIO Area
Unit No.
Allocated words
(decimal)
0 (0)
CIO 1500 to CIO 1524
Unit No.
Allocated words
(decimal)
8 (8)
CIO 1700 to CIO 1724
1 (1)
2 (2)
3 (3)
4 (4)
5 (5)
6 (6)
7 (7)
9 (9)
A (10)
B (11)
C (12)
D (13)
E (14)
F (15)
CIO 1525 to CIO 1549
CIO 1550 to CIO 1574
CIO 1575 to CIO 1599
CIO 1600 to CIO 1624
CIO 1625 to CIO 1649
CIO 1650 to CIO 1674
CIO 1675 to CIO 1699
CIO 1725 to CIO 1749
CIO 1750 to CIO 1774
CIO 1775 to CIO 1799
CIO 1800 to CIO 1824
CIO 1825 to CIO 1849
CIO 1850 to CIO 1874
CIO 1875 to CIO 1899
Words Allocated in DM Area
Unit No.
(decimal)
0 (0)
1 (1)
2 (2)
3 (3)
4 (4)
5 (5)
6 (6)
7 (7)
Setting the Node Number
Allocated words
D30000 to D30099
D30100 to D30199
D30200 to D30299
D30300 to D30399
D30400 to D30499
D30500 to D30599
D30600 to D30699
D30700 to D30799
Unit No. (decimal)
8 (8)
9 (9)
A (10)
B (11)
C (12)
D (13)
E (15)
F (16)
Allocated words
D30800 to D30899
D30900 to D30999
D31000 to D31099
D31100 to D31199
D31200 to D31299
D31300 to D31399
D31400 to D31499
D31500 to D31599
Set the node number, which is the least significant digit of the FL-net Unit's IP
address. Use the Node Number Switches to set the node number to a hexadecimal number from 01 and F9 (1 to 249 decimal). Do not set a number that
has already been set for another FL-net Unit on the same network.
Setting range
01 to F9 (1 to 249 decimal)
CS-series
CJ-series
The left switch sets the leftmost digit (most significant digit) and the right
switch sets the rightmost digit (least significant digit). The node number is factory-set to 01.
Note Turn OFF the power supply before setting the node number.
■ Relationship between Node Numbers and IP Addresses
OMRON FL-net Units are provided with two methods for setting IP addresses.
The setting method is selected in the CPU Bus Unit System Setup allocated in
the CPU Unit.
For details on setting methods, refer to 4-2 CPU Bus Unit System Setup.
31
Section 3-4
Hardware Setup
Be sure to read and understand all of the following information for each setting
method before setting the IP addresses. For details on FL-net IP addresses,
refer to FL-net IP Address under Appendix C Network System Definitions.
IP address setting
method
192.168.250 + node
number
Setup area
Note
Node number setting
method
Details
Rotary switches on front of
This is the default FL-net netUnit (Node Number Switches) work address. The node number is set using the rotary
switches on the front of the
Unit.
Fourth octet of IP address
The IP address can be set
(rightmost eight bits of the IP when writing the Setup data
address)
using the CX-FLnet or FL-net
Unit Support Software. The
CX-FLnet or FL-net Unit Support Software is required to
change the IP addresses.
1. After changing IP addresses or other settings with any of these setting
methods, restart the FL-net Unit.
2. If the IP address of an earlier FL-net Unit (CS1W-FLN02 and CS1WFLN12) was set using the rotary switch on the rear of the Unit, reset the IP
address using the CX-FLnet or FL-net Unit Support Software with either of
the above two methods.
Note If a subnet mask is to be set, use the Support Software to set it in the CPU
Bus Unit Setup Area. For details, refer to SECTION 11 CX-FLnet Support
Software Operations.
32
Section 3-5
Mounting to the PLC
3-5
Mounting to the PLC
CS-series PLCs
FL-net Units can be mounted to any slots in either a CS-series CPU Rack or a
CS-series Expansion Rack, but the number of slots to which they can be
mounted depends on the Backplane. Up to four FL-net Units can be mounted
to a single PLC. If an FL-net Unit is mounted in combination with other CPU
Bus Units (e.g., Controller Link Units), the maximum total number of CPU Bus
Units that can be mounted is 16.
Note PLC Backplane mounting screws to a torque of 0.9 N⋅m, and the Unit's
mounting screws to a torque of 0.4 N⋅m.
CS1W-BC023/033/053/083/103 Backplane
CS-series CPU Rack
Can mount to any
position with 2, 3, 5, 8,
or 10 slots.
2, 3, 5, 8, or 10 slots (Expansion Backplane not
possible with 2-slot CPU Backplane.)
CS1W-B1033/053/083/103 Expansion Backplane for CS Series
CS-series Expansion Rack
Can mount to any position
with 3, 5, 8, or 10 slots.
Up to four Units can
be mounted to the
slots shown in the
diagram to the left.
3, 5, 8, or 10 slots
Expansion I/O Backplane for C200H Series
C200H-series I/O
Expansion Rack
Can mount to any slot
position.
CPU: CPU Unit
PS: Power Supply Unit
Note The current consumption of the CS1W-FLN22 FL-net Unit is 380 mA maximum. Make sure that the total current consumption of all Units mounted to the
CPU Rack or Expansion Rack to which the FL-net Unit is mounted does not
exceed the capacity of the Power Supply Unit.
33
Section 3-6
Network Installation
CJ-series PLCs
CJ-series FL-net Units can be mounted to either a CJ-series CPU Rack or a
CJ-series Expansion Rack. Mount the Units to any of the positions shown in
the following diagram, and secure with the slider on the top and bottom of the
Unit. Up to four FL-net Units can be mounted to a single PLC. If an FL-net Unit
is mounted in combination with other CPU Bus Units (e.g., Controller Link
Units), the maximum total number of CPU Bus Units that can be mounted is
16.
10 Units max.
CPU Rack
End cover
P C I
S P C
U
10 Units max.
Expansion Rack
End cover
P I
S I
10 Units max.
Expansion Rack
End cover
FL-net Units can be
connected in up to
four of the slots
indicated at the left.
P I
S I
10 Units max.
Expansion Rack
End cover
P I
S I
Note
PS: Power Supply Unit
CPU: CPU Unit
IC: I/O Control Unit
II: I/O Interface Unit
Note The current consumption of the CJ1W-FLN22 FL-net Unit is 370 mA maximum. Make sure that the total current consumption of all Units mounted to the
CPU Rack or Expansion Rack to which the FL-net Unit is mounted does not
exceed the capacity of the Power Supply Unit.
3-6
3-6-1
Network Installation
Basic Installation Precautions
• Take the greatest care when installing the Ethernet System, being sure to
follow ISO 8802-3 specifications. You must obtain a copy of these specifications and be sure you understand them before attempting to install an
Ethernet System. Unless you are already experienced in installing communications systems, we strongly recommend that you employ a professional to install your system.
• Do not install Ethernet equipment near sources of noise. If noise-prone
environments are unavoidable, be sure to take adequate measures
against noise interference, such as installing network components in
grounded metal cases, using optical links in the system, etc.
34
Section 3-6
Network Installation
3-6-2
Recommended Products
The following products are recommended for use with the CS1W-ETN21
Ethernet Unit.
Part
Hub
Twisted-pair
cable
Maker
Model
number
10Base-T
Allied
RH509E
Telesis
MR820TLX
100Base-TX
Fujikura F-LINK-E
0.5mm x 4P
Fujikura
CTP-LAN5
0.5mm x 4P
10Base-T
Fujikura F-LINK-E
0.5mm x 4P
Fujikura
Connectors
(Modular
plug)
3-6-3
CTP-LAN5
0.5mm x 4P
STP Plug
Panduit
MPS588
Corp
UTP Plug
MP588-C
Panduit
Corp
Specifications
Inquires
9-port hub
Allied Telesis
9-port hub with 10Base-5 (0120) 86-0442
(in Japan only)
backbone port
STP (shielded twisted--pair) cable: Category 5,
5e
Note: Impedance is limited to 100 Ω.
UTP (unshielded twistedpair) cable: Category 5,
5e
STP (shielded twistedpair) cable: Category 3,
4, 5, 5e
Note: Impedance is limited to 100 Ω.
UTP (unshielded twistedpair) cable: Category 3,
4, 5, 5e
---
---
Precautions
Precautions on Laying Twisted-pair Cable
Basic Precautions
• Press the cable connector in firmly until it locks into place at both the hub
and the Ethernet Unit.
• After laying the twisted-pair cable, check the connection with a 10Base-T
cable tester.
Environment Precautions
• The UTP cable is not shielded, and the hub is designed for use in OA
environments. In environments subject to noise, construct a system with
shielded twisted-pair (STP) cable and hubs suitable for an FA environment.
• Do not lay the twisted-pair cable together with high-voltage lines.
• Do not lay the twisted-pair cable near devices that generate noise.
• Do not lay the twisted-pair cable in locations subject to high temperatures
or high humidity.
• Do not lay the twisted-pair cable in locations subject to excessive dirt and
dust or to oil mist or other contaminants.
35
Section 3-6
Network Installation
Hub Installation
Environment Precautions
• Do not install the hub near devices that generate noise.
• Do not install the hub in locations subject to high temperatures or high
humidity.
• Do not install the hub in locations subject to excessive dirt and dust or to
oil mist or other contaminants.
Hub Connection Methods
If more hub ports are required, they can be added by connecting more than
one hub. There are two possible connection methods for hubs: Cascade and
stacked.
Cascade Connections
• Connect two hubs to each other as follows: Connect an MDI port to an
MDI-X port with a straight cable; connect two MDI ports with a cross
cable; and connect two MDI-X ports with a cross cable.
Note
It is very difficult to distinguish cross cables and straight cables by appearance. Incorrect cables will cause communications to fail. We recommend
using cascade connections with straight cables whenever possible.
• With cascade connections, up to 5 segments can be connected using up
to 4 repeaters (i.e., 4 hubs).
MDI ports
MDI-X port
(cross)
Hub
Stack Connections
Straight cable
Cross cable
Hub
Hub
Hub
• Connect the hubs using special cables or special racks.
• Normally there is no limit to the number of hubs in a stack, and each stack
is treated as one hub. Some hubs, however, are limited in the number of
hubs per stack.
Hub
Four stackable hubs
Stack cable
36
Two stackable hubs
Stack cable
Section 3-6
Network Installation
3-6-4
Noise Reduction when Using Contact Outputs
Communications errors can occur when Contact Output Units are mounted to
the same Rack or connected to the same PLC as an FL-net Unit due to noise
generated by the contact outputs. Use one or more of the following measures
when installing Contact Output Units and Ethernet Units on the same Rack.
Mounting Location
Mount (or connect) any Contact Output Units as far away from the FL-net Unit
as possible.
Contact Output Unit
FL-net Unit
Contact outputs
Cable Location
Separate the transceiver cable or twisted-pair cable connecting the FL-net
Unit as far from the wiring to the Contact Output Units as possible. The coaxial cable must also be placed as far away from the Contact Output Units and
their wiring as possible.
Contact outputs
FL-net Unit
Contact Output Unit
To transceiver/hub
37
Section 3-7
Connecting to the Network
3-7
3-7-1
Connecting to the Network
Ethernet Connectors
The following standards and specifications apply to the connectors for the
Ethernet twisted-pair cable.
• Electrical specifications: Conforming to IEEE802.3 standards.
• Connector structure:
Connector pin
1
2
3
4
5
6
7
8
Hood
3-7-2
RJ45 8-pin Modular Connector
(conforming to ISO 8877)
Signal name
Transmission data +
Transmission data –
Reception data +
Not used.
Not used.
Reception data –
Not used.
Not used.
Frame ground
Abbr.
TD+
TD–
RD+
----RD–
----FG
Signal direction
Output
Output
Input
----Input
-------
Connecting the Cable
!Caution Turn OFF the PLC’s power supply before connecting or disconnecting twistedpair cable.
!Caution Allow enough space for the bending radius of the twisted-pair cable as shown
in below.
35 mm
38
Section 3-8
Creating an I/O Table
1,2,3...
1. Lay the twisted-pair cable.
2. Connect the cable to the hub. Be sure to press in the cable until it locks into
place.
Request cable installation from a qualified professional.
3. Connect the cable to the connector on the Ethernet Unit. Be sure to press
in the cable until it locks into place.
Example: CS1W-FLN22
RJ45 Modular Connector
FL-net Unit
3-8
Creating an I/O Table
After the hardware settings and connections have been completed, turn ON
the power supply to the PLC and create an I/O table.
3-8-1
I/O Table Overview
An I/O table is used to identify Units connected to the PLC and to allocate I/O
to them. If any change is made to the Unit configuration of a CS-series PLC,
an I/O table must be created to register the Units to the CPU Unit.
3-8-2
Connecting Programming Devices to the PLC
To create the I/O table, connect a Programming Device (such as a Programming Console or CX-Programmer) to the PLC.
Applicable Programming
Devices
The following Programming Devices can be used with CS-series PLCs.
Programming Console
Model number
C200H-PRO27-E
Key Sheet (required)
CS1W-KS001-E
CQM1-PRO01-E
Recommended cable (required)
CS1W-CN224 (cable length: 2.0 m)
CS1W-CN624 (cable length: 6.0 m)
CS1W-CN114 (cable length: 0.1 m)
CX-Programmer and CX-Integrator
The operations are explained here using a Programming Console. For details
regarding the CX-Programmer and the CX-Integrator, refer to the CX-Programmer User’s Manual and the CX-Integrator.
39
Creating Routing Tables
Section 3-9
Connecting Programming
Devices
To connect a Programming Console, attach a CS-series Key Sheet and then
connect the Console to the CPU Unit’s peripheral port. (It cannot be connected to the RS-232C port.)
3-8-3
Procedure for Creating an I/O Table
The procedure for creating an I/O table is shown here, taking as an example
an I/O table that is generated automatically for a PLC connected online. In this
example, a Programming Console is used for creating the I/O table. For an
explanation of how to create an I/O table using a CX-Programmer, refer to the
CX-Programmer User’s Manual.
Use the following procedure to create the I/O table.
Initial screen
SHIFT
CH
*DM
000000 I/O TBL ?
CHG
000000 I/O TBL
WRIT
????
WRITE
Password
000000CPU BU ST?
0:CLR 1:KEEP
or
(Save or clear the CPU Bus Unit System Setup.)
000000 I/O TBL
WRIT OK
3-9
Creating Routing Tables
When the FINS communications service is used, routing tables must be created in advance. Routing tables are required in the following circumstances.
• When the FINS communications service is used on an FL-net network
(including when communications are only carried out between FA networks via an FL-net network).
• When there are multiple Communications Units mounted to the PLC, and
FA Link protocol messages, such as writing or reading word blocks, etc.,
are executed by the CMND(490) instruction.
If neither of these circumstances apply, then a routing table is not required. In
that case, proceed to 3-10 System Setup.
The routing table is required not only for nodes communicating via the FINS
communications service but for all relay nodes on the network.
40
Section 3-9
Creating Routing Tables
3-9-1
Routing Table Overview
The routing tables describe the transmission path for FINS messages when
the FINS communications are used. It consists of two tables: A local network
table and a relay network table.
Local Network Table
The local network table is a table describing the correspondences among unit
numbers of the Communications Units and Boards mounted to each node
(PLC or FA Computer).
Example
Unit #04
Unit #05
Unit #06
Unit #07
Local Network Table
Local network Unit number
address
1
2
3
4
04
05
06
07
Network #1
Network #2
Network #3
Network #4
Note
1. The unit number is set (from 0 to F: 1 to 15) by the rotary switch on the front
of the FL-net Unit.
2. The network address is the number of the network (from 1 to 127) to which
the Communications Unit or Board is connected. It is set when the local
network table is created.
Relay Network Table
A relay table is a table that shows the nodes to which data should be sent first
in order to send data to a network that is not connected to the local node. It
shows the correspondence between the address of the final destination network, and the network address and node number of the first relay point of the
path to reach there. When internetwork communications are carried out, the
end network can be reached by following the relay points.
41
Section 3-9
Creating Routing Tables
The following example shows a routing table for sending data from PLC #1
(the local node: network address 1, node number 1) to PLC #4 (the destination node: network address 3, node number 2).
Node #2
PLC #3
Unit #0
(relay node) Node #1
PLC #2 (relay node)
Unit #1
PLC #1 (local node)
PLC #4 (destination node)
Node #3
Node #1
Node #2
Node #2
Node #1
Network #1
Network #2
PLC #1
relay network table
PLC #2
relay network table
End
Relay
Relay
network network node
End
Relay
Relay
network network node
To go to network #3,
first go to node #2 at
network #2.
To go to network #3,
first go to node #3 at
network #1.
Network #3
End network
PLC #3
relay network table
Local
network
address
Unit
number
(To go to network #3 (The network is the same,
according to the local so go to node #2 at network #3.)
network table, go
through the unit
number of the local
CPU Rack.)
Note In the above example, the routing tables required to send a message in one
direction from PLC #1 to PLC #4 are shown. Similar settings would need to be
added to the routing tables to enable sending a message the other direction,
i.e., from PLC #1 to PLC #4.
3-9-2
Connecting and Using a Peripheral Device for the PLC
Routing tables must be created by a CX-Integrator connected to the PLC.
(They cannot be created using a Programming Console.) For details on how
to connect and use a CX-Integrator, refer to the CX-Integrator User’s Manual.
Note
1. When routing tables are transferred from the CX-Integrator to a PLC, the
CPU Bus Unit will be reset so that the set routing tables can be read and
enabled. Make sure that the equipment will not be adversely affected when
the CPU Bus Unit is reset before transferring the routing tables.
2. To transfer routing tables for multiple nodes to a PLC in one batch, connect
the CX-Integrator to a PLC with only one Communications Unit mounted.
Routing tables cannot be transferred to other nodes from a PLC with multiple Communications Units mounted.
3. Routing tables can only be transferred as a batch to multiple nodes within
the same network as the PLC to which the CX-Integrator is connected.
42
Section 3-9
Creating Routing Tables
Routing Table Setting Examples
Example 1: Local Network Table for a PLC With Multiple Units Mounted
This example shows the local network table settings for a PLC to which multiple CPU Bus Units are mounted.
FL-net network
Controller Link network
(Network #A)
(Network #B)
PS: Power Supply Unit
CPU: CPU Unit
FLN: FL-net Unit
CLK: Controller Link Unit
Unit #a Unit #b
Local Network Table
Local
CPU Bus
network
Unit
Example 2: Three Interconnected Networks
This example shows the relay network table settings for three different interconnected networks.
Relay Network Table
No.
End
network
Relay
network
Node
PLC #1
Node #a
Network #A
PLC #2
Node #b
Node #c
PLC #3
Network #B
Node #d
PLC #4
Node #e
Node #f
Network #C
Node #g
In the table for PLC #3, for example, if network #A is taken as the end network, then network #B becomes the relay network and node #c becomes the
relay node. If network #C is taken as the end network, then network #B still
becomes the relay network and node #e becomes the relay node.
43
Section 3-9
Creating Routing Tables
Example 3: All Nodes
This example uses the following configuration to show the routing tables for all
nodes.
Unit #5
Node #6
Unit #3
Node #4
Unit #2
Node #3
PLC
PLC
Network #20
PLC
Unit #0
Node #1
PLC #1 Routing Table
(Local network table)
Local
CPU Bus
network Unit No.
PLC #2 Routing Table
(Local network table)
Local
network
CPU Bus
Unit No.
PLC #3 Routing Table
(Local network table)
Local
network
CPU Bus
Unit No.
PLC #4 Routing Table
(Local network table)
Local
network
CPU Bus
Unit No.
PLC #5 Routing Table
(Local network table)
Local
network
CPU Bus
Unit No.
PLC #6 Routing Table
(Local network table)
Local
network
CPU Bus
Unit No.
PLC #7 Routing Table
(Local network table)
Local
network
44
CPU Bus
Unit No.
PLC
Unit #1
Node #2
Network #10
Unit #4
PLC
Node #5
Unit #7
Node #15
Network #30
PLC
Unit #5
Node #5
PLC
Unit #6
Node #10
(Relay network table)
End
network
Relay
network
Relay
node
(Relay network table)
End
network
Relay
network
Relay
node
(Relay network table)
End
network
Relay
network
Relay
node
(Relay network table)
End
network
Relay
network
Relay
node
(Relay network table)
End
network
Relay
network
Relay
node
(Relay network table)
End
network
Relay
network
Relay
node
(Relay network table)
End
network
Relay
network
Relay
node
Section 3-10
System Setup
3-10 System Setup
The settings for the FL-net Unit’s basic and special functions are made in the
CPU Bus Unit System Setup. These settings, and the situations in which the
settings must be made, are shown in the following table. For details on how to
make the settings, refer to 4-2 CPU Bus Unit System Setup.
3-10-1 When Settings are Required
Settings
FA Link mapping table method
FA Link startup method
Sub-net mask
Baud rate
When settings are required
When the number of nodes assigned to the table exceeds 96.
When using a ladder program to control communications participation
after turning on the power.
When executing message communications with an FL-net node by
another manufacturer.
When changing the broadcast address for any reason.
When making settings, for any reason, outside of the range of the
default IP address setting method.
When changing the sub-net mask for any reason.
When changing the baud rate to 100 Mbps.
Local node setup
Other node setup
Minimum allowable frame interval
When using the Data Link function.
When using the Data Link function.
When using a baud rate of 100 Mbps.
Confirm message protocol
Broadcast type
IP address set method
Page
50
50
50
50
50
50
50
50
50
181
3-10-2 Using the CX-FLnet or FL-net Unit Support Software
The settings for the CPU Bus Unit System Setup are made using an CXFLnet or FL-net Unit Support Software connected to the PLC. The settings
cannot be made using a Programming Console or a CX-Programmer. The
CX-FLnet and FL-net Unit Support Software can be used only for OMRON
FL-net Units.
3-10-3 CPU Bus Unit System Setup Defaults
The following table shows the items in the CPU Bus Unit System Setup, and
their default settings.
Item
FA Link mapping table method
FA Link startup method
Confirm message protocol
Broadcast type
IP address set method
Sub-net mask
Baud rate
Local node setup
Other node setup
Default
PLC built-in method
Automatic participation method
Confirm
***.***.***.255
192.168.250.node number
255.255.255.0
10 Mbps
None
None
45
Section 3-11
Checking Communications
3-11 Checking Communications
The FL-net Unit supports the PING command, which is also widely supported
by host computers. It also supports a function for internode testing in the FINS
communications service by simply manipulating bits with a Programming
Device.
After the settings and connections have been completed, use either the PING
command or the internode test function as required to check communications
with the remote nodes.
Networking checks using the PING command and internode testing can be
executed regardless of the PLC’s operating mode, but it may have an effect on
operation by increasing network traffic and adding more internal processing
for the FL-net Unit.
It is recommended that the testing be performed with the tested node in PROGRAM Mode, or in an environment in which message servicing is not executed.
3-11-1 PING Command and Internode Testing
The following table outlines the points of difference between the PING command and internode testing.
Item
Main application
Test objects
Network classification
Address system used
Transmission from FL-net
Unit
Reception at FL-net Unit
PING command
Testing communications as
an Ethernet node.
FL-net Units and Ethernet
devices that support PING.
Within Ethernet networks
(including between segments).
IP addresses
Cannot be sent from this
Unit.
When PING command is
received, it is automatically returned.
Internode testing
Testing as an FL-net node.
FL-net Units and devices
supporting FL-net.
Within FL-net networks.
Node numbers
From Programming
Devices for PLC, set the
required parameters in
CIO words allocated to
CPU Bus Units and turn
ON the Start Bit.
When internode test message is received, it is automatically returned.
3-11-2 PING Command
The PING command checks communications with another node by sending
an echo back request packet and receiving a response packet. Use the PING
command as required to check communications. Using the PING command
from a personal computer on an Ethernet network makes it possible to check
whether Ethernet internode communications are normal.
3-11-3 Internode Test
The internode test is a function for checking a network by sending data to and
from specified nodes and checking the responses. Use the internode test as
required to check the communications between FL-net nodes. Use it as
required to check message communications.
Note The internode test can be easily carried out by manipulating dedicated control
switches for the FL-net Unit. For details, refer to 9-3 Internode Test.
46
SECTION 4
System Setup and Memory Allocations
This section explains the System Setup and the words allocated in the CIO Area and the DM Area for FL-net (Ver. 2.00)
Units.
4-1
4-2
4-3
4-4
Allocated Words . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
48
CPU Bus Unit System Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
49
4-2-1
System Setting - CPU Bus Unit Setup Area. . . . . . . . . . . . . . . . . . .
50
Allocated Words in the CIO Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51
4-3-1
Unit Control Bits (CPU Unit to FL-net Unit). . . . . . . . . . . . . . . . . .
52
4-3-2
Internode Test Destination Address (CPU Unit to FL-net Unit) . . .
52
4-3-3
Internode Test Monitoring Time (CPU Unit to FL-net Unit) . . . . . .
52
4-3-4
Internode Test Status (CPU Unit to FL-net Unit) . . . . . . . . . . . . . . .
53
4-3-5
No. of Internode Test Runs (FL-net Unit to CPU Unit) . . . . . . . . . .
53
4-3-6
No. of Internode Test Timeout Errors (FL-net Unit to CPU Unit) . .
53
4-3-7
No. of Internode Test Response Errors (FL-net Unit to CPU Unit) .
54
4-3-8
No. of Internode Test Transmission Errors (FL-net Unit to CPU Unit)
54
4-3-9
No. of Times Internode Test Data Did Not Match
(FL-net Unit to CPU Unit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
54
4-3-10 Unit Status (FL-net Unit to CPU Unit). . . . . . . . . . . . . . . . . . . . . . .
55
4-3-11 Network Status (FL-net Unit to CPU Unit) . . . . . . . . . . . . . . . . . . .
56
4-3-12 Refresh Cycle Time (FL-net Unit to CPU Unit). . . . . . . . . . . . . . . .
57
4-3-13 Node Information (FL-net Unit to CPU Unit) . . . . . . . . . . . . . . . . .
57
Allocated Words in the DM Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
58
4-4-1
Node Status (FL-net Unit to CPU Unit) . . . . . . . . . . . . . . . . . . . . . .
59
4-4-2
Number of Cyclic Transmission Receive Errors
(FL-net Unit to CPU Unit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
59
4-4-3
Number of Message Resend Overflows (FL-net Unit to CPU Unit)
60
4-4-4
Number of Message Transmission Receive Errors
(FL-net Unit to CPU Unit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
59
4-4-5
Number of ACK Errors (FL-net Unit to CPU Unit) . . . . . . . . . . . . .
60
4-4-6
Number of Self Removals (FL-net Unit to CPU Unit) . . . . . . . . . . .
60
4-4-7
Number of Removals Due to Skips (FL-net Unit to CPU Unit). . . .
60
4-4-8
Total Number of Send Errors (FL-net Unit to CPU Unit) . . . . . . . .
60
4-4-9
Total Number of Receive Errors (FL-net Unit to CPU Unit) . . . . . .
61
47
Section 4-1
Allocated Words
4-1
Allocated Words
The FL-net Unit is allocated words in the following four areas for reading settings and status.
• System Setup for CPU Bus Units
Stores initial setup for the FL-net node.
• System Setup in FL-net Unit
Stores Data Link data when the FL-net Unit’s Data Link function is used
with the Unit built-in method.
• Allocated Words in the CIO Area
Stores software switches and status information for functions.
• Allocated Words in the DM Area
Stores software switch and status information for functions.
CPU Unit
FL-net Unit
CPU Bus Unit System Setup
(Set using CX-FLnet or
FL-net Unit Support Software.)
Transferred
when power
supply is turned
ON or Unit is
restarted.
to
to
System Setup in FL-net Unit
(Set using CX-FLnet or
FL-net Unit Support Software.)
to
Allocated Words in CIO Area for
CPU Bus Units
n = CIO 1500 + 25 x unit number
15
15
0
n
0
I/O refresh
n+1
to
to
n + 24
Allocated Words in DM Area for
CPU Bus Units
n = D30000 + 100 x unit number
0
15
m
15
0
I/O refresh
m+1
to
to
m + 99
The words in the CIO Area and DM Area are allocated according to the unit
number as shown in the following tables. The 25 words are allocated per Unit
in the CIO Area and 100 word are allocated per Unit in the DM Area.
48
Section 4-2
CPU Bus Unit System Setup
CIO Area Allocations
Unit No.
(decimal)
0 (0)
1 (1)
2 (2)
3 (3)
4 (4)
5 (5)
6 (6)
7 (7)
Allocated words
CIO 1500 to CIO 1524
Unit No.
(decimal)
8 (8)
Allocated words
CIO 1700 to CIO 1724
CIO 1525 to CIO 1549
CIO 1550 to CIO 1574
CIO 1575 to CIO 1599
CIO 1600 to CIO 1624
CIO 1625 to CIO 1649
CIO 1650 to CIO 1674
CIO 1675 to CIO 1699
9 (9)
A (10)
B (11)
C (12)
D (13)
E (14)
F (15)
CIO 1725 to CIO 1749
CIO 1750 to CIO 1774
CIO 1775 to CIO 1799
CIO 1800 to CIO 1824
CIO 1825 to CIO 1849
CIO 1850 to CIO 1874
CIO 1875 to CIO 1899
DM Area Allocations
4-2
Unit No.
(decimal)
0 (0)
1 (1)
2 (2)
3 (3)
4 (4)
5 (5)
6 (6)
7 (7)
Allocated words
D30000 to D30099
D30100 to D30199
D30200 to D30299
D30300 to D30399
Unit No.
(decimal)
8 (8)
9 (9)
A (10)
B (11)
Allocated words
D30800 to D30899
D30900 to D30999
D31000 to D31099
D31100 to D31199
D30400 to D30499
D30500 to D30599
D30600 to D30699
D30700 to D30799
C (12)
D (13)
E (14)
F (15)
D31200 to D31299
D31300 to D31399
D31400 to D31499
D31500 to D31599
CPU Bus Unit System Setup
To operate the FL-net Unit as a node on FL-net network, the required parameters must be set in the CPU Bus Unit System Setup, part of the CPU Unit’s
Parameter Areas. If any of the following items apply, then the system parameters must be set.
• The Data Link function is used. The Data Link table is stored in either the
CPU Bus Unit System Setup (PLC built-in method) or the FL-net Unit System Setup (Unit built-in method). (Default: PLC built-in method)
• The startup method is changed. (Default: Automatic participation method)
• Message protocol confirmation is changed. (Default: Confirm)
• The broadcast method is changed. (Default: ***.***.***.255)
• The IP address is set. (Default: 192.168.250 + node number)
• The subnet mask is changed. (Default: 255.255.255.0)
• The baud rate is changed to 100 Mbps. (Default: 10 Mbps)
Newly set parameters go into effect after the FL-net Unit has been restarted
or after the CPU Unit is started again.
The settings are made in the CPU Bus Unit System Setup using the CX-FLnet
or FL-net Unit Support Software.
Note The CPU Bus Unit System Setup is located in the CPU Unit’s Parameter Area,
and not in I/O Memory; parameters cannot be written using instructions or by
editing I/O Memory. The settings can be made only by using the CX-FLnet or
FL-net Unit Support Software.
49
Section 4-2
CPU Bus Unit System Setup
4-2-1
System Setting - CPU Bus Unit Setup Area
Note Refer to SECTION 11 CX-FLnet Support Software Operations for CX-FLnet
procedures.
Item
FA Link mapping table method
(default: PLC build-in method)
Content
Selects the method (PLC build-in method or FA Link Unit build-in method) for storing
the FA Link mapping table.
Normally the default should be selected.
FA Link startup method
Selects the method (auto-participating or manual-participating) for starting the FA
Link.
(default: Auto-participating)
Normally the default should be selected.
Confirm message protocol
Selects the protocol (confirmed or unconfirmed) for when messages are used.
(default: Confirmed)
Select Confirmed for a network with OMRON FL-net Units only.
Select Unconfirmed for a network in which units from other manufacturers are connected.
Broadcast type
Selects the broadcast type (***.***.***.255 or C255.255.255.255).
(default: ***.***.***.255)
Normally the default should be selected.
IP address set method
Selects the IP address setting method (192.168.250 + Node No., Unit rear rotary SW,
(default: 192.168.250 + Node No.) Unit rear rotary SW + Node No., or Setup Area).
Normally the default should be selected.
When using CS1W-FLN22 or CJ1W-FLN22, select either 192.168.250 +Node No or
Setup Area.
Sub-net mask
Sets the sub-net mask (user setting).
(default: 255.255.255.0)
Normally the default should be selected.
IP address
Sets the IP address (user setting). The IP address does not need to be set except
when the IP address set method is se to Setup Area.
(default: None)
No. of the other nodes in FA Link
(default: None)
Baud Rate Setting
(default: 10 Mbps (not variable))
50
The number of remote nodes (user setting) in the FA Link configuration is displayed.
This parameter cannot be set.
Sets the baud rate for FL-net communications. To communicate at 100 Mbps, select
Auto.
The baud rate is determined by the auto-negotiation function of the connected hub.
Section 4-3
Allocated Words in the CIO Area
Note
1. To circulate a token among the nodes connected to the network, match the
uppermost three digits of the IP address, the sub-net mask, and the broadcast type to those of the other connected nodes.
2. If either Unit rear rotary SW + node No. or Unit rear rotary SW is set as the
IP address setting method for the CS1W-FLN22 or CJ1W-FLN22, a setting
error will occur (HER indicator will light). Set the IP address setting method
to either 192.168.250 + node No. (default) or Setup Area.
3. The baud rate setting is supported by the CS1W-FLN22 and CJ1W-FLN22
only. The setting cannot be made for the CS1W-FLN02 or CS1W-FLN12,
which always communicate at 10 Mbps.
4. Select Option - Switch Settings - Hex from the Main Menu. The IP address and subnet mask will be displayed in hexadecimal, and hexadecimal
input will be possible.
5. If communications are set to connect via the network and storage in the
PLC is set to use the FA link allocation table storage method, the maximum
number of nodes that can be registered in other node areas is 50.
4-3
Allocated Words in the CIO Area
Data is stored from the beginning word in the area for each Unit, according to
the offset positions shown in the following table.
Beginning word n can be calculated by means of the following equation.
Beginning word n = 1,500 + (25 x unit number):
Offset
n
n+1
n+2
n+3
n+4
n+5
n+6
n+7
n+8
D15
D8
D7
D0
1. Unit control bits
2. Internode test destination address
3. Internode test response monitoring time
4. Internode test status
5. Number of internode test runs
6. Number of internode test timeout
errors
7. Number of internode test
response errors
8. Number of internode test
transmission errors
9. Number of times internode test data
did not match
10. Unit status
11. Network status
12. Refresh cycle time
Data direction
CPU Unit ↔ FL-net Unit
CPU Unit to FL-net Unit
FL-net Unit to CPU Unit
FL-net Unit to CPU Unit
n+9
n+10
n+11
n+12
n+13
n+14
n+15
n+16
13. Node connection information (256 nodes)
n+17
n+18
n+19
n+20
n+21
n+22
51
Section 4-3
Allocated Words in the CIO Area
n+23
n+24
n+25
4-3-1
Unit Control Bits (CPU Unit to FL-net Unit)
FL-net Unit operation is started by turn control bits ON and OFF.
n
15
14
13
12
11
10
−
−
−
−
−
−
9
−
8
−
7
6
−
5
−
−
4
3
2
−
−
−
1
0
FA Link Connection Start Bit
Internode Test Start Bit
Bit
0
1
2 to 15
4-3-2
Bit name
FA Link Connection
Start Bit
ON
Status
Manipulated by
User
OFF
User
Internode Test Start Bit ON
(Not used.)
Unit operation
Connects to network
when turned from OFF
to ON.
Disconnects from network when turned from
ON to OFF.
Executes internode
test while ON.
Stops internode test.
Test completed (255
times).
---
User
OFF
User
Unit
---
---
Internode Test Destination Address (CPU Unit to FL-net Unit)
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Remote node address
n+1
0000 to 00F9 (Hex)
Set the remote node address for the internode test in hexadecimal.
4-3-3
Internode Test Monitoring Time (CPU Unit to FL-net Unit)
15
14
n+2
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Response monitoring time
0000 to FFFF (Hex)
Set the time period, in the ranges shown below (in units of 10 ms, hexadecimal), to wait for a response in the internode test.
0000 (Hex): 2 s
0001 to FFFF: 0.01 to 655.35 s
52
Section 4-3
Allocated Words in the CIO Area
4-3-4
Internode Test Status (CPU Unit to FL-net Unit)
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
n+3
b) Timeout error
a) Error code
c) Response error
d) Send error
e) Data disagreement error
f) Send parameter error
The internode test results are reflected here. (When the internode test is
started, all bits are turned back OFF.
a) Error codes
The applicable error code is stored in bits 13 to 15.
Bit
15
0
1
Meaning
14
13
0
1
0
1
Normal completion.
Insufficient memory error:
b) Timeout error
Turns ON if no response is returned within the response monitoring
time.
c) Response error
Turns ON if the response frame is abnormal.
d) Send error
Turns ON if there is a timeout at the start of transmission, or if the
transmission is abnormal for any reason.
e) Data disagreement error
Turns ON if the data received is different from the data sent, or if the
data length does not match.
f)
4-3-5
Send parameter error
Turns ON if the address setting is incorrect.
No. of Internode Test Runs (FL-net Unit to CPU Unit)
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Number of internode test runs
n+3
00 to FF (Hex)
Internode tests are executed repeatedly as long as the Internode Test Start
Bit, one of the Unit Control Bites in the CIO area, remains ON.
In this word, specify in hexadecimal the number of times that the internode
test is actually to be executed
4-3-6
No. of Internode Test Timeout Errors (FL-net Unit to CPU Unit)
15
n+4
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Number of timeout errors
00 to FF (Hex)
The number of timeout errors that have occurred in the internode test is
stored in this word in hexadecimal.
53
Section 4-3
Allocated Words in the CIO Area
00 to FF (Hex): 0 to 255 times
When the count reaches FF (Hex), it will not go any further. The count value
will be retained until the internode test is restarted.
4-3-7
No. of Internode Test Response Errors (FL-net Unit to CPU Unit)
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Number of response errors
n+4
00 to FF (Hex)
The number of response errors that have occurred in the internode test is
stored in this word in hexadecimal.
00 to FF (Hex): 0 to 255 times
When the count reaches FF (Hex), it will not go any further. The count value
will be retained until the internode test is restarted.
4-3-8
No. of Internode Test Transmission Errors (FL-net Unit to CPU
Unit)
15
n+5
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Number of transmission errors
00 to FF (Hex)
The number of transmission errors that have occurred in the internode test is
stored in this word in hexadecimal.
00 to FF (Hex): 0 to 255 times
When the count reaches FF (Hex), it will not go any further. The count value
will be retained until the internode test is restarted.
4-3-9
No. of Times Internode Test Data Did Not Match (FL-net Unit to
CPU Unit)
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Number of response errors
n+5
00 to FF (Hex)
The number of data disagreement errors that have occurred in the internode
test is stored in this word in hexadecimal.
00 to FF (Hex): 0 to 255 times
When the count reaches FF (Hex), it will not go any further. The count value
will be retained until the internode test is restarted.
54
Section 4-3
Allocated Words in the CIO Area
4-3-10 Unit Status (FL-net Unit to CPU Unit)
15
14
13
12
11
10
9
n+6
8
7
6
5
4
3
2
−
−
−
−
−
−
1
0
FA Link Running
Readable Transmission Message
FA Link (Common Memory) Area Allocation Error
Data Link (PLC) Area Allocation Error
Token Monitoring Timeout Error
IP Address Setting Error
Transceiver Error
EEPROM Error
Bits
0
1
2 to 7
8
9
10
11
Name
FA Link Running
Readable Transmission
Message
ON
OFF
Status
Running
Stopped
ON
Yes
OFF
No
(Not used.)
--FA Link (Common Mem- ON
ory) Area Allocation
Error
Data Link (PLC) Area
Allocation Error
Token Monitoring Timeout Error
LAN Controller Error
--Error
OFF
Normal
ON
Error
OFF
Normal
ON
Error
OFF
Normal
ON
Error
OFF
Normal
Unit operation
ON when participating in FA link.
OFF when not participating in the FA link or
when node numbers have been duplicated.
ON when transmission of a transparent message is completed normally.
OFF when a transparent message is read and
disappears from the communications buffer.
ON when an error occurs in FA Link (Common
Memory) Area allocations.
The Common Memory allocations for the local
node setup area are incorrect. Correct the settings from the CX-FLnet or FL-net Unit Support
Software.
OFF when FA Link (Common Memory) Area
allocations are normal.
ON when an error occurs in Data Link (PLC)
Area allocations.
The PLC Area allocations for the local node
setup area and other node setup area are
incorrect. Correct the settings from the CXFLnet or FL-net Unit Support Software.
OFF Data Link (PLC) Area allocations are normal.
ON when a token monitoring timeout occurs
while the local node is holding the token.
A processing delay has occurred due to high
system load. Correct the system configuration
or extend the token monitoring timeout time
(token watchdog timer) using the CX-FLnet or
FL-net Unit Support Software.
OFF when a token monitoring timeout does not
occur while the local node is holding the token.
ON when communications are not possible due
to an error.
OFF when communications are normal.
55
Section 4-3
Allocated Words in the CIO Area
Bits
Name
IP Address Setting Error ON
12
Status
Error
13
14
(Not used.)
Transceiver Error
OFF
--ON
Normal
--Error
15
EEPROM Error
OFF
ON
Normal
Error
OFF
Normal
Unit operation
ON when an error occurs in the IP address setting. The following IP addresses cannot be set.
• Host ID containing all 0s or 1s.
• Net ID containing all 0s or 1s.
• Sub-net ID containing all 1s.
• Address beginning with 127 (7F hex).
ON when the IP address setting is normal.
ON when transmission is not possible due to
external factors.
OFF after recovery from transceiver error.
ON when an EEPROM error occurs or when
writing to EEPROM is frequently not possible.
OFF when EEPROM is normal.
4-3-11 Network Status (FL-net Unit to CPU Unit)
15
14
13
12
11
−
n+7
10
9
8
7
6
5
4
3
2
1
0
−
−
−
−
−
−
−
−
Duplicate Node Number Notification
Frame Standby
FL-net Version Unconformity Notification
(Communications Disabled Detection Flag)
Upper Layer Signal Error (PLC stopped)
Common Memory Data Validity Notification
Common Memory Setting Completed
Duplicate Common Memory Address
Bits
0 to 7
8
Name
(Not used.)
Duplicate Node Number
Notification
9
Frame Standby
10
FL-net Version Unconformity Notification
(Communications Disabled Detection Flag)
11
12
--ON
OFF
Normal
ON
Standby
OFF
ON
Off standby
Error
OFF
Normal
(Not used.)
--Upper Layer Signal Error ON
(PLC stopped)
OFF
56
Status
--Error
--Stopped
Not stopped
Unit operation
ON when duplicated node numbers are
detected.
OFF when duplicated node numbers are not
detected.
ON when a reception frame cannot be
detected.
Indicates that a frame from a remote node cannot be received.
OFF when a reception frame can be detected.
ON when attempting to participate in FL-net
(Ver. 1.00) network.
OFF when participating in FL-net (Ver. 2.00)
network.
ON when an error occurs between the FL-net
Unit and the PLC.
A fatal or non-fatal error has occurred in the
CPU Unit.
The routing table settings are incorrect.
OFF when communications between the FL-net
Unit and the PLC are normal.
Section 4-3
Allocated Words in the CIO Area
Bits
13
Name
Status
Common Memory Data
Validity Notification
14
Common Memory Setting Completed
15
Duplicate Common
Memory Address
Unit operation
ON
Valid
OFF
ON
OFF
Invalid
Completed
Not completed
ON
Error
OFF
Normal
ON when Common Memory data is valid.
Indicates that data from each node has started
being refreshed in the PLC.
OFF when Common Memory data is invalid.
Common Memory setting completed.
OFF when error occurs in Common Memory
settings.
Correct the settings from the CX-FLnet or FLnet Unit Support Software.
ON when local node has same Common Memory address as a remote node.
The Common Memory address is the same as
that for a remote node that has already joined
the network. Correct the setting from the CXFLnet or FL-net Unit Support Software.
ON when local node does not have same Common Memory address as any remote node.
4-3-12 Refresh Cycle Time (FL-net Unit to CPU Unit)
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Refresh cycle time PV
n+8
0000 to FFFF (Hex)
Determines the token frame transmission interval, which is the time measured
from when a token is sent until when it is received, and displays it in hexadecimal in units of 1 ms.
0000 to FFFF (Hex): 0 to 65,535 ms
4-3-13 Node Information (FL-net Unit to CPU Unit)
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
n+9
15
14
13
12
11
10
9
8
7
6
5
4
n+10
31
30
29
28
27
26
25
24
23
22
21
n+23
239
238
237
236
235
234
233
232
231
230
n+24
255
254
253
252
251
250
249
248
247
246
0
3
2
1
20
19
18
17
16
229
228
227
226
225
224
245
244
243
242
241
240
Note Nodes 250 to 255 are reserved for FL-net (Ver. 2.00) maintenance purposes.
• Indicates the network participation status between the local node and
nodes in the data link table settings that are registered in the other node
setup area (set using the CX-FLnet or FL-net Unit Support Software).
• When nodes registered in the data link table join the network normally
and the data link data from the nodes can be refreshed in the CPU Unit,
the corresponding bit turns ON.
• When communications from a participating node stop for three consecutive communications cycles, the node is detected as not participating in
the network and the corresponding bit turns OFF.
• When the local node leaves the network, the corresponding bit for the
local node turns OFF, at which all bits including those for the local node
will turn OFF.
57
Section 4-4
Allocated Words in the DM Area
• Bits corresponding to nodes that are not registered in the data link table
are always OFF.
• When a corresponding node is not connected, or an area allocation error
occurs, the corresponding bit is always OFF.
4-4
Allocated Words in the DM Area
The allocated DM Area words contain the status of the network to which the
FL-net Unit is connected and information on connected nodes. All area information is cleared to 0 when the power is turned ON or the FL-net Unit is
restarted.
Data is stored from the beginning word in the area for each Unit, according to
the offset positions shown in the following table.
Beginning word m can be calculated by means of the following equation.
Beginning word m = D30000 + (100 x unit number)
Bit
Offset
15
8
7
0
Data direction
m
to
Node status
FL-net Unit to CPU Unit
m+63
m+64
Number of cyclic transmission receive errors
m+65
m+66
Number of message transmission resend overflow errors
m+67
m+68
Number of message transmission receive errors
m+69
m+70
Number of ACK errors
m+71
m+72
Number of self removals
m+73
m+74
Number of removals due to skips
m+75
m+76
Total number of send errors
m+77
m+78
Total number of receive errors
m+79
m+80
to
m+99
58
(Not used.)
Section 4-4
Allocated Words in the DM Area
4-4-1
Node Status (FL-net Unit to CPU Unit)
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
m
Node 3
Node 2
Node 1
(Always 0)
m+1
Node 7
Node 6
Node 5
Node 4
m+62
Node 251
Node 250
Node 249
Node 248
m+63
Node 255
Node 254
Node 253
Node 252
0
Note Nodes 250 to 255 are reserved for maintenance purposes for FL-net Ver. 2.00
specifications.
The network connection status of remote nodes is stored in the following bits.
15
14
13
Bits
11 07
10 06
09 05
03
02
01
1. Operation (upper layer)
2. Error (upper layer)
3. Participation in network
12
08
00
4. Mapping error
04
Meaning
ON: Operating; OFF: Stopped
ON: Error; OFF: No error
ON: Participating;
OFF: Not participating
ON: Error; OFF: No error
1. Operation (Upper Layer)
The operating status (active/not active) of applications installed at the node
is stored.
2. Error (Upper Layer)
The error status (error/no error) of applications installed at the node is
stored. These bits turn ON when a fatal or non-fatal error occurs in each
PLC, or when the routing tables are incorrect.
3. Participation in Network
Network participation status is stored.
The operating status and error status data when not participating is invalid.
(The upper layer status when changing from participating to not participating is retained.)
4. Mapping Error
Notifies that the settings do not correctly reflect the network data in the
PLC areas.
4-4-2
Number of Cyclic Transmission Receive Errors (FL-net Unit to
CPU Unit)
The number of times ($0 to $FFFFFFFF) inconsistencies occur in parameters
in communications frames (CBN, TBN, and BSIZE) during cyclic transmission
reception is stored.
These errors may occur due to the network configuration. If this error occurs
frequently, either extend the minimum allowable frame interval using the CXFLnet or FL-net Unit Support Software or reduce the number of Units using
cascade connections from the hub.
15
m+64
m+65
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Number of cyclic transmission errors H ($0000 to $FFFF)
Number of cyclic transmission errors L ($0000 to $FFFF)
59
Section 4-4
Allocated Words in the DM Area
4-4-3
Number of Message Resend Overflows (FL-net Unit to CPU Unit)
The number of times ($0 to $FFFFFFFF) a message is resent three times or
more during message transmission is stored. This error may occur due to the
network configuration or line load.
15
m+67
4-4-4
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Number of Message Resend Overflows H ($0000 to $FFFF)
Number of Message Resend Overflows L ($0000 to $FFFF)
m+66
Number of Message Transmission Receive Errors (FL-net Unit to
CPU Unit)
The number of occurrences ($0 to $FFFFFFFF) of sequence errors, illegal
source node numbers, illegal transaction codes, and illegal sequence versions during message reception is stored.
15
4-4-5
14
13
12
11
10
9
8
7
6
5
4
3
2
1
m+68
Number of Message Transmission Receive Errors H ($0000 to $FFFF)
m+69
Number of Message Transmission Receive Errors L ($0000 to $FFFF)
0
Number of ACK Errors (FL-net Unit to CPU Unit)
The number of occurrences ($0 to $FFFFFFFF) of ACK errors during message reception is stored. This error may occur due to the network configuration or line load.
15
14
m+71
4-4-6
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Number of ACK Errors H ($0000 to $FFFF)
Number of ACK Errors L ($0000 to $FFFF)
m+70
Number of Self Removals (FL-net Unit to CPU Unit)
The number of times ($0 to $FFFFFFFF) a node removes itself from the network during communications is stored. Self removal occurs when a token
holding timeout occurs at least four times This error may occur due to the network configuration, line load, or line settings.
15
14
13
m+72
m+73
4-4-7
12
11
10
9
8
7
6
5
4
3
2
1
0
Number of self removals H ($0000 to $FFFF)
Number of self removals L ($0000 to $FFFF)
Number of Removals Due to Skips (FL-net Unit to CPU Unit)
The number of times ($0 to $FFFFFFFF) a node is removed due to a local
node skip during communications is stored.
15
14
m+74
12
11
10
9
8
7
6
5
4
3
2
1
0
Number of Removals due to Skips H ($0000 to $FFFF)
Number of Removals due to Skips L ($0000 to $FFFF)
m+75
4-4-8
13
Total Number of Send Errors (FL-net Unit to CPU Unit)
The number of collisions ($0 to $FFFFFFFF) from 16 or more that occurred
during packet transmission is stored. This error may occur during normal
operation due to the network configuration or line load.
15
m+76
m+77
60
14
13
12
11
10
9
8
7
6
5
4
3
2
Total number of send errors H ($0000 to $FFFF)
Total number of send errors L ($0000 to $FFFF)
1
0
Section 4-4
Allocated Words in the DM Area
4-4-9
Total Number of Receive Errors (FL-net Unit to CPU Unit)
The total number of errors ($0 to $FFFFFFFF), including overflow errors, CRC
errors, alignment errors, and short packet errors, that occur during packet
reception is stored. This error may occur due to the network configuration.
If this error occurs frequently, either extend the minimum allowable frame
interval using the CX-FLnet or FL-net Unit Support Software or reduce the
number of Units using cascade connections from the hub.
15
m+78
m+79
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Total number of receive errors H ($0000 to $FFFF)
Total number of receive errors L ($0000 to $FFFF)
Note When the baud rate is set to 100 Mbps, adjust the minimum allowable frame
interval. The set value depends on the number of nodes, number of data link
words, and hub performance capacity. The following table provides a guide for
set values.
Total data link words
0 to 2,000 words
Minimum allowable frame
interval
0.8 ms
2,000 to 4,000 words
4,000 to 6,000 words
6,000 to 8,000 words
1.0 ms
1.2 ms
1.5 ms
The minimum allowable frame interval is set in the Unit area settings from the
FL-net Unit Support Software. If the minimum allowable frame interval is too
short, the total number of receive errors will be incremented.
61
Allocated Words in the DM Area
62
Section 4-4
SECTION 5
Data Link
This section explains the Data Link function, including an overview and examples of how to make the required settings.
5-1
5-2
Data Link Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
64
5-1-1
FL-net Cyclic Transmission and Common Memory . . . . . . . . . . . .
64
5-1-2
Data Link Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
67
Setting Data Link Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
68
5-2-1
Setting Data Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
68
5-2-2
Settings Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
71
5-2-3
Advanced Data Link Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
79
63
Section 5-1
Data Link Overview
5-1
Data Link Overview
The data link function uses FL-net cyclic transmission for automatically
exchanging data, from preset areas, between nodes on a single network
(between two PLCs or between a PLC and an FA computer). The CS1WFLN22/CJ1W-FLN22 can also be used for exchanging data between CS/CJseries PLCs or between FL-net nodes by other manufacturers.
5-1-1
FL-net Cyclic Transmission and Common Memory
1. Cyclic Transmission Overview
Cyclic transmission supports the exchange of cyclic data between nodes.
a) Cyclic transmission uses Common Memory as an interface.
b) When a node is holding the token the node transmits cyclic data.
c) Not all nodes participating in the network must support cyclic transmission.
d) The node holding the token transmits all cyclic data that should be
sent.
Time
Node #1
Node #2
Node #3
Node #N
Token
Node #1
Node #3
Node #2
Node #N
Token
Node #1
Node #N-1
Node #2
Node #N
Token
Node #1
Node #N-1
Node #2
Node #N
Token
Token: There is basically only one token in a network. If more than one token
exists in a network, the token whose destination node has the smallest node
number will be given priority and the other tokens will be discarded.
Token frame: the token frame is a frame that includes the token. It consists of
the token's destination node number and source node number. Each node
becomes the token holding node when its node number matches the token
destination node number in the received token frame.
Token flow: The token rotation order is determined by the node numbers.
Each node circulates the token among the nodes registered in the participat-
64
Section 5-1
Data Link Overview
ing node management table in ascending order. The node with the largest
node number in the network passes the token to the node with the smallest
node number in the network.
2. Common Memory
The concept of Common Memory is as follows:
a) Common Memory provides a service that functions as shared memory
between nodes transmitting cyclic data.
b) Two areas (Area 1 and Area 2) are assigned for each node.
c) When the area transmitted by a node exceeds the transmission size
limit for a single frame, which is 1,024 bytes, the data is fragmented
into multiple frames and then transmitted.
d) In the case of item c), when the fragmented data frames are received,
the Common Memory is not refreshed until all frames from the one
node have been received, thereby ensuring the concurrence of the
data at individual nodes.
e) The capacity reserved as Common Memory for communications in a
single node is a fixed size of 8 Kbits + 8 Kwords = 8.5 Kwords.
f)
Within Common Memory, the size of the transmission area of Area 1
and Area 2 for each node can be set freely within the maximum area
range.
g) By broadcasting data, each node in the network shares the same data
for a specific period. Each node in the FL-net network is allocated a
specific transmission area that does not overlap with that of the other
nodes, and data is exchanged among them. In Common Memory operations, the transmission area allocated to one node is the receiving
area for the other nodes.
Common Memory of node 01
Node 02
Node 03
Node 04
(Transmitting)
(Receiving)
(Receiving)
(Receiving)
(Receiving)
(Transmitting)
.
.
(Receiving)
.
.
(Receiving)
.
.
(Receiving)
.
.
(Receiving)
.
.
(Receiving)
.
.
(Transmitting)
(Receiving)
(Receiving)
(Transmitting)
(Receiving)
.
.
.
.
65
Section 5-1
Data Link Overview
A node can also use the whole Common Memory as a receiving area only.
Common Memory of node 01
Node 02
(Receiving)
(Receiving)
(Receiving)
(Transmitting)
Node 05
(Transmitting)
(Receiving)
3. Areas 1 and 2
Common Memory is configured of two data areas: Area 1 and Area 2. The
area is accessed by the word address. Area 1 consists of 0.5 Kword, and
Area 2 consists of 8 Kwords. The transmission area is defined by its first
word and size.
Area 1
Area 2
0
215
20
0
215
20
First word
First word
Size
Size
Transmission
area
Transmission
area
0x1ff
0x1f f f
4. Data Concurrency
In cyclic transmission, the transmission data is fragmented into multiple
frames depending on the size of the data. The following procedure ensures
concurrency of the Common Memory for each node.
5. Transmission Timing
When there is a data transmission request from the upper layer, the cyclic
data from the local node is copied into the buffer, prepared for transmission, and then transmitted in order. If the size of the data held in the transmitting node is greater than the maximum capacity that can be sent in one
frame (1,024 bytes), the data in the buffer is fragmented into multiple
frames before transmitting.
6. Refresh Timing when Receiving Data
As soon as the receiving node has received all the cyclic data from one
node, the relevant area in Common Memory is refreshed in synchroniza-
66
Section 5-1
Data Link Overview
tion with the upper layer. When a node receives cyclic data in multiple
frames, the area is refreshed as soon as all the frames being transmitted
by the one node have been received. If all the frames that were transmitting
the fragmented data from the node are not received, all the data that was
transmitted from the node is discarded.
Common
memory
Transmission
area
Batch copy
Transmitting
node
Transmission
buffer
Cyclic data
Network
circuit
Cyclic data
Cyclic data
Receiving
buffer
Receiving node
Common
memory
5-1-2
Batch copy
Receiving
area
Data Link Specifications
The memory used in common by nodes executing cyclic transmission is
called “Common Memory.” The FL-net Unit has 8,704 words of Common
Memory (including Area 1 and Area 2).
Item
Number of
nodes
Number of data
blocks
Total Data Link
capacity
Areas that can
be allocated
Specifications
128 nodes max.
Two areas max. per node (Area 1 and Area 2)
8,704 words max.
• Area 1 (bit area): 512 words
• Area 2 (word area): 8,192 words
• CIO (I/O bits, etc.): CIO 0 to CIO 6143
• Work Area: W0 to W511
• HR Area: H0 to H511
• DM Area: D0 to D32,767
• EM Area: Bank 0 to 12, E0 to E32,767
Words
Unit of data
exchange
Data configura- The following diagram shows the configuration of one word of data.
tion
MSB
LSB
Word D15
Note
D0
1. The data for Area 1 and Area 2 from the same node will be refreshed in the
same CPU Unit cycle or Area 2 will be refreshed first. If concurrency is re-
67
Section 5-2
Setting Data Link Tables
quired between the data in Area 1 and Area 2, use refreshing of the data
in Area 1 as a trigger before accessing data from Area 2.
2. Make sure that the data link tables are correct and confirm that the equipment will not be adversely affected by the data link table settings before
starting the data links. Incorrect data link tables may result in unexpected
operation.
3. If the total number of words in Area 1 and Area 2 for setting a single node
exceeds 7,677 words, the data for the corresponding node will be refreshed over two scans of the CPU Unit. If the setup area of at least one
node in the network exceeds 7,677 words, the data for that node is split
and refreshed over two cycles. The data for the corresponding node will be
split from the 7,678th word counted from the beginning of Area 1.
Data Refresh when a Single Node's Setup Area Is More than 7,677 Words
Each node has less than 7,677 words
At least one node has 7,678 words or more.
#1
#2
7,677 words max.
Refreshed in first cycle
#3
#4
Refreshed in second cycle
7,678
words
max.
#1
7,677 words
Refreshed in
first cycle
#2
Refreshed in
second cycle
Split at 7,678th word for refreshing
(refreshed over two CPU cycles)
5-2
5-2-1
Setting Data Link Tables
Setting Data Link
The method for setting Data Link is explained by means of the CX-FLnet or
FL-net Unit Support Software.
Note
1. The CX-FLnet or FL-net Unit Support Software, Support Software designed especially for OMRON FL-net Units, is used to set Data Link tables.
2. To enable the Data Link table settings once they have been made from the
CX-FLnet or FL-net Unit Support Software, it is necessary to either turn the
PLC power OFF and back ON again or restart the FL-net Unit.
68
Setting Data Link Tables
Section 5-2
System Setting (Local
Node Setup Area)
The Local Node Setup Area can be set so that data from any PLC area can
be used as the send data from the local node.
Item
Area 1 (Area 2) Memory Area
(default: Area 1 CIO, Area 2 DM)
Area 1 (Area 2) start word
(default: 0)
Area 1 (Area 2) size
(default: 0)
Content
Sets the PLC area in which Cyclic Data Areas 1 and 2 for the local node are stored.
The following areas can be set: CIO, WR, HR, DM, and EM0 to EMC.
Sets the beginning word of the PLC area in which Cyclic Data Areas 1 and 2 for the
local node are stored.
Area 1 (Area 2) Start address of
Common Memory
(default: 0)
Sets the beginning address of the Common Memory allocated to Area 1 (or Area 2).
Sets the size of the PLC area in which Cyclic Data Areas 1 and 2 for the local node
are stored. This setting also determines the size allocated to this node for Common
Memory.
Note Select Option - Switch display - Hex. It will be possible to display and input
words, sizes, and addresses in hexadecimal.
69
Section 5-2
Setting Data Link Tables
System Setting Other Node Setup
Area
The other node setup area are set so that Common Memory data for remote
nodes can be read to the local PLC areas.
Item
Area 1 (Area 2) Memory Area
(default: Area 1 CIO, Area 2 DM)
Area 1 (Area 2) start word
(default: 0)
Mapping area table
Content
Sets the PLC area in which Cyclic Data Areas 1 and 2 for the remote nodes are
stored.
The following areas can be set: CIO, WR, HR, DM, and EM0 to EMC.
Sets the beginning word of the PLC area in which Cyclic Data Areas 1 and 2 for the
remote nodes are stored.
Sets the offset, size and mapped node numbers of the PLC area in which Cyclic Data
Areas 1 and 2 for the remote nodes are stored.
When setting Other Node Setup Area, the following functions can be used.
Menu
Edit - Clear all
Edit - Copy row
Edit - Delete
Note
Function
Clear all data in the FA link table.
Copy a single data row data and add as a new row.
Delete a single data row.
1. Do not assign the local node to the mapping area table.
2. Enter 0 in the Node No. Field and enter the size of the local node setup
area in the Size Field for the area corresponding to that for the local node.
3. If the settings are made for only Area 1 (or Area 2), set the offset and size
for the other area to 0.
4. Select Option - Switch display - Hex. It will be possible to display and input words, sizes, and addresses in hexadecimal.
5. The “offset” designation tells much data to receive of the data sent from a
given node (i.e., which word to begin receiving from, and how many words
to receive). The number of words from the beginning of the sent data until
the beginning of the received data is called the “offset.” The offset function
can be used to receive only a portion of the data sent from a given node to
enable using the Data Link Memory Areas efficiently.
6. Select Option - Switch Settings - Hex from the Main Menu. It will be possible to display and input words, sizes, and addresses in hexadecimal.
70
Section 5-2
Setting Data Link Tables
5-2-2
Settings Examples
This section provides examples of Data Link tables set by the CX-FLnet or FLnet Unit Support Software, and shows the Common Memory Area and Data
Link Area, for each node, that are created.
Data Link Table
Setting Example 1
In this example, the allocation for all nodes is the same as Common Memory.
Common Memory and Data Link Area Configuration
Node 1
Common Memory
Area 1
0
Node 1
10
Node 2
20
Node 3
30
Node 2
Node 3
Node 4
Data Link Area (Shaded boxes indicate local node setup area.)
CIO 0000
CIO 0010
CIO 0020
CIO 0030
#1
#1
#1
#1
#2
#2
#2
#2
#3
#3
#3
#3
#4
#4
#4
#4
#1
#1
#1
#1
#2
#2
#2
#2
#3
#3
#3
#3
#4
#4
#4
#4
Node 4
49
CIO 0049
Area 2
0
D 00000
Node 1
D 00200
200
Node 2
300
Node 3
400
D 00300
D 00400
Node 4
599
Local Node Setup Areas
D 00599
Node 1
Area
1
2
Beginning address of
Classificat Beginning
Size
Common Memory allocation
ion
word
0
CIO
0
10
0
DM
0
200
Node 2
Area
1
2
Beginning address of
Classificat Beginning
Size
Common Memory allocation
ion
word
10
CIO
10
10
200
DM
200
100
Node 3
Area
1
2
Beginning address of
Classificat Beginning
Size
Common Memory allocation
ion
word
20
CIO
20
10
300
DM
300
100
Node 4
Area
1
Beginning address of
Classificat Beginning
Size
Common Memory allocation
ion
word
30
CIO
30
20
2
400
DM
400
200
71
Section 5-2
Setting Data Link Tables
Other Node Setup Area
Node 1
Area
1
2
Classification
CIO
DM
Node
number
2
3
4
Beginning
word
10
200
Area 1
Offset
Area 2
Size
0
0
0
10
10
20
Offset
0
0
0
Size
100
100
200
Node 2
Area
1
2
Classification
CIO
DM
Node
number
1
2
0 (See
note.)
4
Beginning
word
0
0
Area 1
Offset
Area 2
Size
Offset
Size
0
0
0
10
10
10
0
0
0
200
100
100
0
20
0
200
Node 3
Area
1
2
Classification
CIO
DM
Area 1
Node
number
1
2
0 (See
note.)
4
Beginning
word
0
0
Offset
Area 2
Size
Offset
Size
0
0
0
10
10
10
0
0
0
200
100
100
0
20
0
200
Node 4
Area
1
2
Classification
CIO
DM
Area 1
Node
number
1
2
3
Beginning
word
0
0
Offset
0
0
0
Area 2
Size
10
10
10
Offset
0
0
0
Size
200
100
100
Note If the local node setup area is in a consecutive area of the other node
setup areas, set the node number to 0.
72
Section 5-2
Setting Data Link Tables
Data Link Table
Setting Example 2
In this example, the allocations are different for each node.
Common Memory and Data Link Area Configuration
Node 1
Common Memory
Area 1
0
CIO 0000
CIO 0010
#1
#2
CIO 0010
CIO 0020
#1
#2
CIO 1000
CIO 0030
#3
CIO 1020
#1
#3
#3
CIO 1035
CIO 0039
CIO 1039
Node 3
50
CIO 1005
#2
CIO 1015
Node 2
30
Node 4
Data Link Area (Shaded boxes indicate local node setup area.)
Node 1
10
Node 3
Node 2
#2
CIO 1054
CIO 0049
Area 2
0
D 00000
Node 1
10
D 00010
#1
#2
D 00020
D 00030
#1
#2
D 00000
D 00030
Node 3
50
Local Node Setup Area
D 00049
#3
E1_00000
E1_00010
D 00020
Node 2
30
#2
D 00049
#1
#3
#3
E1_00030
D 00039
#2
E1_00049
Node 1
Area
1
2
Beginning address of
Classificat Beginning
Size
Common Memory allocation
ion
word
0
CIO
0
10
0
DM
0
10
Node 2
Area
1
2
Beginning address of
Classificat Beginning
Size
Common Memory allocation
ion
word
10
CIO
20
20
10
DM
30
20
Node 3
Area
1
2
Beginning address of
Classificat Beginning
Size
Common Memory allocation
ion
word
30
CIO
1020
20
30
DM
20
20
Node 4
Area
1
2
Beginning address of
Classificat Beginning
Common Memory allocation
ion
word
0
CIO
0
0
0
DM
0
0
Size
73
Section 5-2
Setting Data Link Tables
Other Node Setup Area
Node 1
Area
1
2
Classification
CIO
DM
Node
number
2
3
Beginning
word
10
10
Area 1
Offset
Area 2
Size
0
0
20
20
Offset
0
0
Size
20
20
Node 2
Area
1
2
Classification
CIO
DM
Node
number
1
Beginning
word
10
20
Area 1
Offset
Area 2
Size
0
10
Offset
0
Size
10
Node 3
Area
1
2
Classification
Beginning
word
CIO
DM
1000
0
Node
number
2
Area 1
Offset
Area 2
Size
0
20
Offset
0
Size
20
Node 4
Area
1
2
Classification
CIO
E1
Node
number
1
3
2
74
Beginning
word
1005
0
Area 1
Offset
0
0
0
Area 2
Size
10
20
20
Offset
0
0
0
Size
10
20
20
Section 5-2
Setting Data Link Tables
Data Link Table
Setting Example 3
In this example, Data Link is executed for two or more groups on the same
network. By means of Data Link table settings, it is possible to create data
links for multiple groups. As shown in the following diagram, if communications words are set for nodes in groups only, the same settings can be made
for multiple Data Link groups.
Common Memory and Data Link Area Configuration
Node 1
Common Memory
Area 1 0
Node 3
Node 2
CIO 0010
#1
#2
CIO 0000
CIO 0010
#1
CIO 1000
#2
CIO 1020
#3
CIO 1000
Node 4
CIO 0029
CIO 0029
#3
CIO 1020
#4
Node 2
30
Group 2
Data Link Area (Shaded boxes indicate local node setup area.)
CIO 0000
Node 1
10
Group 1
#4
CIO 1039
CIO 1039
Node 3
50
Node 4
69
Area 2
D 00000
0
Node 1
100
#1
D 00100
#2
D 01000
D 01100
#1
E1_00000
#2
E1_00300
Node 2
D 00299
300
D 01299
E1_00599
Node 3
#3
E1_00000
#3
E1_00300
#4
#4
E1_00599
600
Node 4
899
Local Node Setup Area
Node 1
Area
1
2
Beginning address of
Classificat Beginning
Size
Common Memory allocation
ion
word
0
CIO
0
10
0
DM
0
100
Node 2
Area
1
2
Beginning address of
Classificat Beginning
Size
Common Memory allocation
ion
word
10
CIO
10
20
100
DM
1100
200
Node 3
Area
1
2
Beginning address of
Classificat Beginning
Size
Common Memory allocation
ion
word
30
DM
1000
20
300
EM0
0
300
Node 4
Area
1
2
Beginning address of
Classificat Beginning
Size
Common Memory allocation
ion
word
50
DM
1020
20
600
EM1
300
300
75
Section 5-2
Setting Data Link Tables
Other Node Setup Area
Node 1
Area
1
2
Classification
CIO
DM
Node
number
2
Beginning
word
10
100
Area 1
Offset
Area 2
Size
0
20
Offset
0
Size
200
Node 2
Area
1
2
Classification
CIO
DM
Node
number
1
Beginning
word
0
1000
Area 1
Offset
Area 2
Size
0
10
Offset
0
Size
100
Node 3
Area
Classification
1
DM
Beginning
word
1020
2
EM0
300
Node
number
4
Area 1
Offset
Area 2
Size
0
20
Offset
0
Size
300
Node 4
Area
1
2
Classification
DM
EM1
Node
number
3
76
Beginning
word
1000
0
Area 1
Offset
0
Area 2
Size
20
Offset
0
Size
300
Section 5-2
Setting Data Link Tables
Data Link Table
Setting Example 4
In this example, the local and remote setup areas are mapped to different
areas (node #1), and only a portion of the transmission data is received. (The
offset designation is used: Nodes 2 to 4.)
Common Memory and Data Link Area Configuration
Node 2
Node 1
Node 4
Node 3
Data Link Area (Shaded boxes indicate local node setup area.)
Common Memory
Area 1
0
D 00000
Node 1
#1A
D 01000
D 01000
1000
D 00000
#1B
2000
D 01999
D 02000
#1C
#2
D 00000
D 01000
D 01999
#1B
#3
D 00000
D 01000
#1A
#4
D 01999
#1C
3000
Node 2
D 02999
E0_00000
4000
#2
Node 3
E0_01000
#3
5000
Node 4
E0_02000
#4
5999
E0_02999
Local Node Setup Area
Node 1
Area
1
2
Beginning address of
Classificat Beginning
Size
Common Memory allocation
ion
word
0
CIO (See
0
0
note.)
0
DM
0
3000
Node 2
Area
1
2
Beginning address of
Classificat Beginning
Size
Common Memory allocation
ion
word
0
CIO (See
0
0
note.)
3000
DM
1000
1000
Node 3
Area
1
2
Beginning address of
Classificat Beginning
Size
Common Memory allocation
ion
word
0
CIO (See
0
0
note.)
4000
DM
1000
1000
Node 4
Area
1
2
Beginning address of
Classificat Beginning
Size
Common Memory allocation
ion
word
0
CIO (See
0
0
note.)
5000
DM
1000
1000
Note Does not need to be set if data writing (transmission) is not required.
77
Section 5-2
Setting Data Link Tables
Other Node Setup Area
Node 1
Area
1
2
Classification
CIO
EM0
Node
number
2
3
4
Beginning
word
0
0
Area 1
Offset
Area 2
Size
0
0
0
0
0
0
Offset
0
0
0
Size
1000
1000
1000
Node 2
Area
1
2
Classification
CIO
DM
Node
number
1
Beginning
word
0
0
Area 1
Offset
Area 2
Size
0
0
Offset
2000
Size
1000
Node 3
Area
1
2
Classification
CIO
DM
Node
number
1
Beginning
word
0
0
Area 1
Offset
Area 2
Size
0
0
Offset
1000
Size
1000
Node 4
Area
1
2
Classification
CIO
DM
Node
number
1
78
Beginning
word
0
0
Area 1
Offset
0
Area 2
Size
0
Offset
0
Size
1000
Section 5-2
Setting Data Link Tables
5-2-3
Advanced Data Link Settings
The order of link data bytes can be specified for each node according to the
needs of the connected device, eliminating the need for upper/lower byte conversion (SWAP) processing in the ladder program or user application.
Setting
Local node
setup area
Details
Sequential
direction
(default)
Reverse
direction
Other node Sequential
setup area direction
(default)
Reverse
direction
Note
Operation
Sends data in the order the same as the earlier CS1WFLN02/12 FL-net Units.
Sends data from the local node setup area after swapping the upper and lower bytes.
The upper/lower byte data of CS/CJ-series CPU Unit’s
data link area is swapped and changed in the Common
Memory.
Sends data in the order the same as the earlier CS1WFLN02/12 FL-net Units.
Sends data from the other node setup area after swapping the upper and lower bytes.
The upper/lower byte data of the Common Memory is
swapped and changed in the CS/CJ-series CPU Unit’s
data link area.
1. The default status is sequential data (“sequential direction”) both for the local node setup area and other node setup area. This is the same data order used for the earlier CS1W-FLN02 and CS1W-FLN12 FL-net Units. Use
the default settings for normal use. When changing the data order, be sure
to consider the data order of the sending nodes and receiving nodes before changing the settings.
2. The data link data order can be set using the CX-FLnet or FL-net Unit Support Software Ver. 1.60.
3. The data link data order settings are enabled only for CS1W-FLN22 and
CJ1W-FLN22 FL-net Units. Settings are disabled for earlier CS1W-FLN02
and CS1W-FLN12 FL-net Units (always operate in sequential direction).
Local Node Setup Area
Settings
Sequential Direction
CPU Unit
data link memory
D15
D0
FL-net
common memory
MSB
LSB
ABCD
ABCD
1234
1234
Same order as previous
CS1W-FLN02/12 FL-net Unit.
Reverse Direction
CPU Unit
data link memory
FL-net
common memory
D15
MSB
D0
LSB
ABCD
CDAB
1234
3412
Order of upper and lower byte is
swapped and changed (sent) in
the common memory.
79
Section 5-2
Setting Data Link Tables
Other Node Setup Area
Settings
Sequential Direction
CPU Unit
data link memory
D15
D0
FL-net
common memory
MSB
LSB
ABCD
ABCD
1234
1234
Same order as previous
CS1W-FLN02/12 FL-net Unit.
Reverse Direction
CPU Unit
data link memory
D15
Using the CX-FLnet or FLnet Unit Support Software
D0
MSB
LSB
CDAB
ABCD
3412
1234
Order of upper and lower byte is
swapped and changed (received) in
the PLC memory.
This setting method is shown using the following configuration example.
The order of data link data received from node 2 is swapped in node 1. Data
swapping (reverse direction) is specified in the settings of the other node
setup area for node 1. The data received by node 3 from node 2 is refreshed
in the original order (sequential direction).
Node 1
Node 2
#1
#1
#1
#2
#2
#2
#3
#3
#3
Receive data
"CDAB"
80
FL-net
common memory
Send data
"ABCD"
Node 3
Setting Data Link Tables
1,2,3...
Section 5-2
1. Create the data link table using the CX-FLnet or FL-net Unit Support Software.
2. Click the OK Button to return to the Main Menu. Select Extension setting
from the Option Menu.
81
Setting Data Link Tables
Section 5-2
3. Click the System Setting Button and open the data link table editing
screen to display the Extension Setting Tab Page.
4. Set the order of receive data to the reverse direction for node number 2 under Other node setup.
5. Click the Send Button and transfer the settings to the FL-net Unit (CS/CJseries CPU Unit). To enable the settings, restart the FL-net Unit or cycle
the power to the CS/CJ-series CPU Unit.
82
SECTION 6
Message Transmission
This section describes the message transmission used by an FL-net (Ver. 2.00) network.
6-1
Message Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
84
6-2
Details of Supported Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
86
83
Section 6-1
Message Transmission
6-1
Message Transmission
Message transmission is a function that supports the asynchronous exchange of data between nodes. The basic functions of message transmissions are explained here.
1,2,3...
1. When a node receives the token, it can send one (and only one) message
frame before transmitting cyclic data.
2. The volume of data that can be transmitted in one message frame is 1,024
bytes max.
3. An algorithm is used so that the allowable refresh cycle time for cyclic
transmission is not exceeded.
4. A message transmission can be sent either to a single destination node as
a 1:1 transmission or broadcast to all nodes on the network as a 1:N transmission.
5. In 1:1 message transmissions, the destination node has an acknowledgement function to check that data has been received successfully. No response is provided by the source node for 1:N message transmissions.
Request
Response
1:1 message transmission
Request
Reception
Reception
Reception
1:N message transmission
Supported Messages
Message
84
Read byte block
Write byte blocK
Read word block
Write word block
Read network parameter
1:1 transmission
Client function
Server function
No
No
No
No
Yes (See note 1.) Yes
Yes (See note 1.) Yes
No
Yes
1:N transmission
Client function
Server function
No
No
No
No
No
No
No
No
No
No
Write network parameter
Run/stop command
Read profile
Read communications log data
Clear communications log data
Echoback message
No
No
No
No
No
Yes*
No
No
No
No
No
No
No
No
Yes
Yes
Yes
Yes
No
No
No
No
Yes
No
Section 6-1
Message Transmission
Message
Send transparent message frame
Vendor message (FINS message)
1:1 transmission
Client function
Server function
Yes (See note 1.) Yes (See note 1.)
Yes (See note 1.) Yes
1:N transmission
Client function
Server function
Yes (See note 1.) Yes (See note 1.)
Yes (See note 1.) Yes
Yes: Supported
No:
Not supported
Yes*: An internode test is provided but the user cannot change the data. For
details, refer to 9-3 Internode Test.
Note The following table provides a list of messages that are sent from a ladder
program in the FL-net Unit as well as their usage.
Message
Read word
block data
Write word
block data
Send transparent message
Vendor message (FINS
message).
Usage
Sent to another node on the same network.
RECV(098)instruction (See note 1.)
WORD BLOCK DATA READ (unspecified node number) (FINS: 2903) (See note 2.)
WORD BLOCK DATA READ (specified node number) (FINS: 2923) (See note 2.)
Sent to another node on another FL-net network.
WORD BLOCK DATA READ (specified node number) (FINS: 2923) (See note 2.)
Sent to another node on the same network.
SEND(090) instruction (See note 1.)
WORD BLOCK DATA WRITE (unspecified node number) (FINS: 2904) (See note 2.)
WORD BLOCK DATA WRITE (specified node number) (FINS: 2924) (See note 2.)
Sent to another node on another FL-net network.
WORD BLOCK DATA WRITE (specified node number) (FINS: 2924) (See note 2.)
TRANSPARENT MESSAGE SEND (FINS: 2901) (See note 2.)
TRANSPARENT MESSAGE RECEIVE FRAME READ (FINS: 2902) (See note 2.)
SEND(090)/RECV(098)/CMND(490) instruction (FINS communications service) (See
note 1.)
Note
Reference
--Section 7-2
Section 7-5-7
Section 7-5-9
--Section 7-5-9
--Section 7-2
Section 7-5-8
Section 7-5-10
--Section 7-5-10
Section 7-5-5
Section 7-5-6
SECTION 7
1. Messages sent only between OMRON PLCs.
2. Messages sent between OMRON PLCs or between an OMRON PLC and
a node for another manufacturer’s unit.
85
Section 6-2
Details of Supported Messages
6-2
Details of Supported Messages
Read Word Block Data
This message reads the virtual address space (32-bit address space) of the
remote node in word units (16 bits per address). The internal address map
varies according to the FL-net Unit being used.
For more information on the FL-net Unit's virtual address space, refer to 7-4
CS/CJ-series Memory Areas and Virtual Addresses.
Request message
Response message
16 bits
0
AAAA
0xffffffff
AAAA
Virtual address space
*: “Oxffffffff” refers to FFFFFFFF Hex.
86
Physical space
(Area inside PLC)
Section 6-2
Details of Supported Messages
Write Word Block Data
This message writes to the virtual address space (32-bit address space) of
the remote node in word units (16 bits per address). The internal address map
varies with the FL-net Unit being used.
Request message
Response message
16 bits
0
AAAA
0xffffffff
AAAA
Virtual address space
Physical space
(Area inside PLC)
*: “Oxffffffff” refers to FFFFFFFF Hex.
Read Network Parameter
This message reads the following network parameter information for the
remote node.
Network Parameter Information
• Node name (equipment name)
• Vendor code
• Manufacturer model
• First word of Area 1
• Size of Area 1
• First word of Area 2
• Size of Area 2
• Token monitoring timeout time
• Minimum allowable frame interval
• FL-net status
• Protocol version
• Link status
• Allowable refresh cycle time (RCT) value
• Refresh cycle measurement value (current)
• Refresh cycle measurement value (maximum)
• Refresh cycle measurement value (minimum)
87
Section 6-2
Details of Supported Messages
Request message
Response message
• Node name (equipment name)
• Vendor code
• Manufacturer model
• First word of Area 1
• Size of Area 1
• First word of Area 2
• Size of Area 2
• Token monitoring timeout time
• Minimum allowable frame interval
• FL-net status
• Protocol version
• Link status
• Allowable refresh cycle time (RCT) value
• Refresh cycle measurement value (current)
• Refresh cycle measurement value (maximum)
• Refresh cycle measurement value (minimum)
Network Parameter Information
Read Profile
This message reads the system parameters of the device profile, which provides information on the remote node. The system parameters consist of the
following parameter information.
• Common parameters (mandatory)
• Device parameters (optional)
Request message
Response message
Common parameters
Device parameters
Note For details on the device profile for system parameters, refer to SECTION 9
Testing Communications.
88
Section 6-2
Details of Supported Messages
Read Communications
Log Data
This message reads the communications log data of the remote node.
Request message
Response message
Communications log data
Clear Communications
Log Data
This message clears the communications log data of the remote node.
Request message
Response message
Clear
Communications log data
Echoback Message
This message requests an echoback response for a message that was
received.
The echoback response occurs automatically in the FL-net Unit.
Request message
Response message
Note The echoback function is used in the FL-net Unit's internode test. For details,
refer to 9-3 Internode Test.
89
Section 6-2
Details of Supported Messages
Send Transparent
Message Frame
Transparent messages provide a message service in the FL-net's upper layer.
The service notifies the FL-net's upper layer of received messages. The FLnet's upper layer notifies the user interface layer. When the user interface
layer is notified, a response to the notification must be created and returned.
Request message
Response message
FL-net upper layer
(memory inside FLnet Unit)
User interface
(CMND(490)
instruction)
Create response
message (ladder
program)
Note Use the CMND(490) instruction to implement a transparent message through
the FL-net Unit. For details, refer to TRANSPARENT MESSAGE SEND on
page 112 and TRANSPARENT MESSAGE RECEIVE FRAME READ on
page 117.
Vendor Message (FINS
Message)
Vendors can implement their own message service in FL-net. In an OMRON
FL-net Unit, a FINS message service is used for vendor messages.
FINS command message
FINS response message
90
SECTION 7
FINS Communications
This section provides information on communicating on FL-net Systems and interconnected networks using FINS
commands. The information provided in the section deals only with FINS communications in reference to FL-net (Ver.
2.00) Units.
FINS commands from a PLC are sent using the SEND(090), RECV(098), and CMND(490) instructions programmed into
the user ladder-diagram program. Although an outline of these instructions is provided in this section, refer to the CS/CJ
Series Programmable Controllers Programming Manual (W340) for further details on programming these instructions.
7-1
7-2
7-3
Overview of FINS Communications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
92
7-1-1
Communications On An FL-net (Ver. 2.00) Network . . . . . . . . . . .
92
7-1-2
FINS Communications Service Features . . . . . . . . . . . . . . . . . . . . .
92
Sending Commands from a PLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
94
7-2-1
Communications Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . .
94
7-2-2
Program Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
103
Command Codes and Response Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
105
7-3-1
Command Code List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
105
7-3-2
Response Code List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
105
7-4
CS/CJ-series Memory Areas and Virtual Addresses. . . . . . . . . . . . . . . . . . . .
106
7-5
Command/Response Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
107
7-5-1
CONTROLLER DATA READ . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
107
7-5-2
CONTROLLER STATUS READ. . . . . . . . . . . . . . . . . . . . . . . . . . .
110
7-5-3
INTERNODE ECHO TEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
110
7-5-4
ERROR LOG READ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
111
7-5-5
TRANSPARENT MESSAGE SEND . . . . . . . . . . . . . . . . . . . . . . . .
112
7-5-6
TRANSPARENT MESSAGE RECEIVE FRAME READ . . . . . . .
117
7-5-7
WORD BLOCK DATA READ (UNSPECIFIED NODE NUMBER)
121
7-5-8
WORD BLOCK DATA WRITE (Unspecified Node Number) . . . .
125
7-5-9
WORD BLOCK DATA READ (Specified Node Number) . . . . . . .
126
7-5-10 WORD BLOCK DATA WRITE (Specified Node Number) . . . . . .
131
91
Section 7-1
Overview of FINS Communications
7-1
Overview of FINS Communications
The FINS communications service enables client control of operations such
as reading or writing server PLC memory area data without the need to program these operations into the server PLC user program. The FL-net Unit
uses FL-net message transmissions to execute the FINS communications
service. (Refer to Vendor Message (FINS Message) on page 90.)
7-1-1
Communications On An FL-net (Ver. 2.00) Network
Data is sent and received as messages on an FL-net (Ver. 2.00) network.
Ethernet header
IP header
UDP header
FL-net (Ver. 2.00) message
FL-net (Ver. 2.00) header
FINS frame
FCS
OMRON PLC
or host computer
FL-net Unit
FL-net (Ver. 2.00) message (FINS command)
Ethernet
FL-net (Ver. 2.00) message (FINS response)
FL-net Unit
OMRON PLC
Note A message may be lost during transmission due to factors such as noise. The
message service does not guarantee that a message will reach the destination node. To prevent this from occurring when using message services, it is
common to set up retry processing at the node from which instructions are
sent. With the SEND(090), RECV(098), and CMND(490) instructions, retry
processing is executed automatically by specifying the number of retries, so
specify a number other than 0.
7-1-2
FINS Communications Service Features
The FINS communications service is a function for controlling operations such
as sending and receiving data, changing modes, and so on, between nodes
on OMRON factory automation networks. It provides the following features.
• Communications instructions are executed in the user program.
• Writing data, changing modes, reading detailed information about Units,
and so on, can be executed without any particular knowledge of communications procedures or network classification.
92
Section 7-1
Overview of FINS Communications
• Units and Boards that support FINS commands return responses automatically, so there is no need for a program at the receiving end.
• The FINS communications service is mainly used between OMRON CPU
Bus Units, CPU Units, and Support Boards for FA Computers. By correctly setting information such as headers, however, it can also be used
from ordinary Ethernet communications devices.
The FINS communications service can be used from a PLC with either of the
following three instructions:
• SEND(090)/RECV(098)
SEND(090) and RECV(098) are used to send and receive data (area reading and writing).
• CMND(490)
CMND(490) is used to send FINS commands. The particular FINS commands that are supported vary depending of the type of Unit or Board. For
details on FINS commands addressed to FL-net Units, refer to 7-5 Command/Response Reference. For details regarding FINS commands addressed to CS/CJ-series CPU Units, refer to the CS/CJ-series
Programmable Controllers Communications Commands Reference Manual (W342).
The following table shows how the FINS communications service is used by
the communications source and destination.
Local node to remote node
PLC to PLC
SEND(090)/RECV(098)
CMND(490) (FINS commands)
• When the PLC executes SEND(090) or
RECV(098), a program is not required for
receiving a response.
• When the PLC executes CMND(490), a
program is not required for receiving a response.
• When the PLC receives a SEND(090) or
RECV(098) instruction, a program is not
required for processing the instruction.
• When the PLC receives a CMND(490) instruction, a program is not required for
processing the instruction.
PLC
CPU Unit
PLC
CPU Unit
FL-net Unit
PLC
CPU Unit
PLC
CPU Unit
When addressed to CPU Unit
User program
User program
93
Section 7-2
Sending Commands from a PLC
7-2
Sending Commands from a PLC
FINS commands can be sent from the user’s ladder-diagram program in the
CPU Unit by using the SEND(090), RECV(098), and CMND(490) instructions.
SEND(090): Writes I/O data from the local node to another node.
RECV(098): Reads I/O data from another node to the local node.
CMND(490): Sends FINS commands for controlling operations such as sending and receiving I/O memory data to and from other nodes, reading information regarding other nodes, and so on.
7-2-1
Communications Specifications
The following table shows the specifications for PLC communications using
the SEND(090), RECV(098), and CMND(490) instructions.
Item
Destination
Data length
Data contents
Communications
port number
Response monitoring time
Number of retries
1:1:
1:N:
Specifications
SEND(090), RECV(098), CMND(490) instructions
SEND(090), CMND(490) instructions (broadcasting)
Addressed to an FL-net node (Ver. 2.00) on the same layer
SEND(090):
512 words (1,024 bytes) max.
RECV(098):
512 words (1,024 bytes) max.
CMND(490):
1,014 bytes max. (after the FINS command code), including broadcasting
(after FINS command code)
Addressed to an FL-net node (Ver. 2.00) on another layer (2nd or 3rd layer)
SEND(090):
503 words (1,006 bytes) max.
RECV(098):
505 words (1,010 bytes) max.
CMND(490):
1,014 bytes max. (after the FINS command code), including broadcasting
The following data is sent and received with the execution of each instruction.
SEND(090): Sends request for remote node to receive data, and receives response data.
RECV(098): Sends request for remote node to send data, and receives response data.
CMND(490): Sends any FINS command and receives response data.
Ports 0 to 7 (Eight transmissions can occur simultaneously.)
The CPU Unit has eight communications ports. Use one communications port to execute communications instructions for the FL-net Unit.
0000:
2 s (default)
0001 to FFFF: 0.1 to 6,553.5 s in 0.1-s increments (specified by user)
0 to 15 retries
Note
1. The maximum data length is limited to 512 bytes for data exchange between the PLC and SYSMAC LINK Systems or the PLC and SYSMAC
BUS/2 Remote I/O Systems.
2. When broadcasting, do not request a response.
3. Broadcasting cannot be used with the SEND(090)/RECV(098) instructions.
4. If multiple communications ports are used to execute multiple communications instructions (SEND(090), RECV(098), and CMND(490)), an error response will be received by the FL-net Unit (error code 0x2605: Servicing
in progress). Execute communications instructions for FL-net one at a time
from a single communications port.
PLC Communications
Data Areas
The following table shows the I/O data areas involved when SEND(090) and
RECV(098) are used.
Area
CIO Area
Work Area
Holding Area
94
Range
CIO 0000 to CIO 6143
W000 to W511
H000 to H511
Section 7-2
Sending Commands from a PLC
Area
Auxiliary Area
Timer Area
Counter Area
DM Area
EM Area
Note
Range
A000 to A959 (See note 1.)
TIM0000 to 4095
CNT0000 to 4095
D00000 to D32767
E00000 to E32767 (See note 2.)
1. Data cannot be written to words A000 to A447 in the Auxiliary Area.
2. A maximum of 13 banks in the EM Area can be used. For details regarding
the EM Area, refer to the operation manual for the PLC that is used.
Using SEND(090), RECV(098), and CMND(490)
Make the settings shown below when using the SEND(090), RECV(098), and
CMND(490) instructions in the user’s ladder-diagram program in the CPU
Unit.
The SEND(090) instruction sends the data in n number of words, starting from
the beginning word S at the local node, to the words starting from the beginning word D at the remote destination node (node number N).
Destination node number N
Number
of words
(n)
…
Local node
…
SEND(090)
S: Local node beginning word
D: Destination beginning word
C: First word of control data (below)
Number of words (n)
0001 to 03DE (Hex): 1 to 512 words
Destination network number
00 (Hex):
Local network
01 to 7F (Hex): 1 to 127
Number of retries
0 to F (Hex): 0 to 15 retries
Communications port number: 0 to 7
Response
0: Required.
1: Not required.
Destination unit address
00 (Hex):
10 to 1F: (Hex):
E1 (Hex):
FE (Hex):
CPU Unit
Unit #0 to #15
Unit connected to network
Unit connected to network
Response monitor time
0000 (Hex): 2 s
0001 to FFFF (Hex): 0.1 to 6,553.5 s (in
units of 1 s)
Destination node number N
00 to FE (Hex); 0 to 254
The range of node addresses is different for networks other than Ethernet.
Note The message service does not guarantee that a message will reach the destination node. A message may be lost during transmission due to factors such
as noise. To prevent this from occurring when using message services, it is
common to set up retry processing at the node from which instructions are
sent. With the SEND(090), RECV(098), and CMND(490) instructions, retry
processing is executed automatically by specifying the number of retries, so
specify a number other than 0.
95
Section 7-2
Sending Commands from a PLC
With the RECV(098) instruction, the data in m number of words, starting from
the beginning word S at the remote node (node number M), is received at the
words starting from the beginning word D at the local node.
Remote node number N
…
Local node
Number
of words
(m)
…
RECV(098)
S: Remote node beginning word
D: Local beginning word
C: First word of control data (below)
Number of retries
0 to F (Hex): 0 to 15 retries
Communications port number: 0 to 7, F
Number of reception words (m)
0001 to 03DE (Hex): 1 to 512 words
Destination network number
00 (Hex):
Local network
01 to 7F (Hex): 1 to 127
Response
0: Required.
1: Not required.
Destination Unit address
00 (Hex):
CPU Unit
10 to 1F: (Hex): Unit #0 to #15
E1 (Hex):
Unit connected to network
FE (Hex):
Unit connected to network
Response monitor time
0000 (Hex): 2 s
0001 to FFFF (Hex): 0.1 to 6,553.5 s (in units of 1 s)
Remote node number M (send source)
00 to 7E (Hex); 0 to 254
The range of node addresses is different for networks other than Ethernet.
Note The message services function does not guarantee that a message will reach
the destination node. A message may be lost during transmission due to factors such as noise. In order to prevent this from occurring when using message services, it is common to set up retry processing at the node from which
instructions are sent. With the SEND(090), RECV(098), and CMND(490)
instructions, retry processing is executed automatically by specifying the number of retries, so specify a number other than 0.
96
Section 7-2
Sending Commands from a PLC
The CMND(049) instruction sends n bytes of command data, starting from the
beginning word S at the local node, to the node at node number N. The data
in m number of words, starting from the beginning word S at the remote node
(node number M) is received at the words starting from the beginning word D
at the local node.
Local node
Destination node number N
S: Beginning command storage word
D: Beginning response storage word
C: First word of control data (below)
…
…
Command
Command
data: n
bytes
Interpretation
Response
Execution
…
CMND(049)
Response
data: m bytes
Number of bytes of command data (n)
0002 to 07C6 (Hex): 2 to 1,014 bytes
Number of bytes of response data (m)
0002 to 07C6 (Hex): 2 to 1,014 bytes
Number of retries
0 to F (Hex): 0 to 15 retries
Destination network number
00 (Hex):
Local network
01 to 7F (Hex): 1 to 127
Destination Unit address
00 (Hex):
10 to 1F: (Hex):
E1 (Hex):
FE (Hex):
Communications port number: 0 to 7, F
Response
0: Required.
1: Not required.
CPU Unit
Unit #0 to #15
Inner Board
Unit connected to network
Destination node number N
00 to 7E (Hex);
0 to 254
The same data can be broadcast to all nodes on the network by
setting the destination node number to FF (Hex).
Response monitor time
0000 (Hex): 2 s
0001 to FFFF (Hex): 0.1 to 6,553.5 s (in units of 1 s)
The range of node addresses is different for networks other than Ethernet.
Note The message services function does not guarantee that a message will reach
the destination node. A message may be lost during transmission due to factors such as noise. In order to prevent this from occurring when using message services, it is common to set up retry processing at the node from which
instructions are sent. With the SEND(090), RECV(098), and CMND(490)
instructions, retry processing is executed automatically by specifying the number of retries, so specify a number other than 0.
97
Section 7-2
Sending Commands from a PLC
Commands Addressed to CS/CJ-series CPU Units
The following table provides a list of FINS commands that can be processed
by a CS/CJ-series CPU Unit. For details, refer to the CS/CJ Series Programmable Controllers Communications Commands Reference Manual (W342).
For details on FINS commands that can be processed by the FL-net Unit,
refer to 7-5 Command/Response Reference.
Usage
I/O memory area
access
Command
code
MR
SR
Name
01
01
MEMORY AREA READ
01
02
MEMORY AREA WRITE
01
03
MEMORY AREA FILL
01
04
MULTIPLE MEMORY AREA READ
01
05
MEMORY AREA TRANSFER
02
01
PARAMETER AREA READ
02
02
PARAMETER AREA WRITE
02
03
PARAMETER AREA FILL (CLEAR)
03
03
03
04
06
07
08
01
PROGRAM AREA READ
PROGRAM AREA WRITE
PROGRAM AREA CLEAR
RUN
04
02
STOP
Machine configura- 05
tion reading
05
01
02
CPU UNIT DATA READ
CONNECTION DATA READ
Status reading
06
06
01
20
CPU UNIT STATUS READ
CYCLE TIME READ
Time data access
07
01
CLOCK READ
07
02
CLOCK WRITE
Message display
09
20
MESSAGE READ/CLEAR
Access rights
0C
01
ACCESS RIGHT ACQUIRE
0C
02
ACCESS RIGHT FORCED ACQUIRE
0C
03
ACCESS RIGHT RELEASE
21
21
21
01
02
03
ERROR CLEAR
ERROR LOG READ
ERROR LOG POINTER CLEAR
Parameter area
access
Program area
access
Operating mode
changes
Error log
98
Function
Reads the contents of consecutive I/O
memory area words.
Writes the contents of consecutive I/O
memory area words.
Writes the same data to the specified
range of I/O memory area words.
Reads the contents of specified nonconsecutive I/O memory area words.
Copies the contents of consecutive I/O
memory area words to another I/O
memory area.
Reads the contents of consecutive
parameter area words.
Writes the contents of consecutive
parameter area words.
Writes the same data to the specified
range of parameter area words.
Reads the UM (User Memory) area.
Writes to the UM (User Memory) area.
Clears the UM (User Memory) area.
Changes the CPU Unit’s operating
mode to RUN or MONITOR.
Changes the CPU Unit’s operating
mode to PROGRAM.
Reads CPU Unit data.
Reads the model numbers of the device
corresponding to addresses.
Reads the status of the CPU Unit.
Reads the maximum, minimum, and
average cycle time.
Reads the present year, month, date,
minute, second, and day of the week.
Changes the present year, month, date,
minute, second, or day of the week.
Reads and clears messages, and reads
FAL/FALS messages.
Acquires the access right as long as no
other device holds it.
Acquires the access right even if
another device already holds it.
Releases the access right that has been
acquired.
Clears errors or error messages.
Reads the error log.
Clears the error log pointer.
Section 7-2
Sending Commands from a PLC
Usage
File memory
Debugging
Writing Programs
Command
code
MR
SR
22
22
01
02
22
03
22
22
04
05
22
07
22
22
08
0A
22
0B
22
0C
22
23
15
01
23
02
Name
Function
FILE NAME READ
SINGLE FILE READ
Reads file memory data.
Reads a specified length of file data
from a specified position within a single
file.
SINGLE FILE WRITE
Writes a specified length of file data
from a specified position within a single
file.
FILE MEMORY FORMAT
Formats (initializes) the file memory.
FILE DELETE
Deletes specified files stored in the file
memory.
FILE COPY
Copies files from one file memory to
another file memory in the same system.
FILE NAME CHANGE
Changes a file name.
MEMORY AREA–FILE TRANSFER
Transfers or compares data between the
I/O memory area and the file memory.
PARAMETER AREA–FILE TRANSFER Transfers or compares data between the
parameter area and the file memory.
PROGRAM AREA–FILE TRANSFER
Transfers or compares data between the
UM (User Memory) area and the file
memory.
CREATE/DELETE DIRECTORY
Creates or deletes a directory.
FORCED SET/RESET
Force-sets or force-resets bits, or
releases force-set status.
FORCED SET/RESET CANCEL
Cancels all bits that have been force-set
or force-reset.
Programs incorporating the SEND(090), RECV(098), and CMND(490)
instructions are generally created using the Communications Port Enabled
Flag and the Communications Port Error Flag as input conditions. CS/CJseries CPU Units have eight communications ports. Only one instruction can
be executed at any given port at one time, however, so the program must not
overlap the use of any of the ports. A program example is provided below.
Note CS1-H, CJ1-H CJ1M, or CS1D CPU Units (for independent CPU systems)
with lot numbers 020601 (manufactured on June 1, 2002 or later) can automatically detect an available communications port. For details, refer to the
automatic communications port allocations for network communications
instructions in the SYSMAC CS/CJ Series Communications Commands Reference Manual (W342).
99
Section 7-2
Sending Commands from a PLC
Execution
condition
Communications
Port Enabled Flag
KEEP(011) A
Reset B
Remote Node Network
Participation Flag
Operand,
control data
Local Node Network
created with
Participation Flag
@MOV and
@XFER.
Communications
instructions
@SEND
@RECV
@CMND
Input A remains ON from start to completion of communications instruction.
Creates operand and control data in a given
area.
Executes communications instructions.
Communications
Port Enabled Flag
DIFU(013) B
Creates reset input. (Turns reset B ON
after execution of communications instruction.)
Communications
Port Error Flag
Send Error Flag display
(Retry can be executed.)
Execution
condition
Communications
Port Enabled Flag
Exclusive control so execution is not simultaneous.
KEEP(011) C
Use exclusive control so that no other communications instructions are started before execution of the
above communications instruction is complete.
Reset D
(Continued in same way.)
Communications Flags
The execution status of the SEND(090), RECV(098), and CMND(490) instructions is always reflected by the communications flags (i.e., the Communications Port Enabled Flag and the Communications Port Error Flag). The CSseries CPU Unit’s communications flags are allocated in the Auxiliary Area as
shown in the following table.
Flag name
Word
Communications Port A202
Enabled Flag
Communications Port A219
Error Flag
Address
Bits
Bit 7: Port 7
Bit 6: Port 6
Bit 5: Port 5
Bit 4: Port 4
Bit 3: Port 3
Bit 2: Port 2
Bit 1: Port 1
Bit 0: Port 0
Bit 7: Port 7
Bit 6: Port 6
Bit 5: Port 5
Bit 4: Port 4
Bit 3: Port 3
Bit 2: Port 2
Bit 1: Port 1
Bit 0: Port 0
Contents
OFF: Execution enabled
(being executed)
ON: Execution disabled
(not being executed)
OFF: Normal completion
ON: Abnormal completion
Note With CS/CJ-series PLCs, communications ports 0 to 7 are also used for executing the PLCMR(260) (PROTOCOL MACRO) instruction, so these flags are
used in common for SEND(090), RECV(098), CMND(490), and PLCMR(260).
While PLCMR(260) is being executed, SEND(090), RECV(098), and
CMND(490) cannot be executed at the same communications port.
100
Section 7-2
Sending Commands from a PLC
Communications Port
Completion Codes
The status of a SEND(090), RECV(098), and CMND(490) instruction after
execution is reflected as a communications port completion code, in one word
(two bytes) of data as shown in the following table. (The value is 0000 during
instruction execution.) The recorded status is saved until execution of the next
instruction.
Word
A203
A204
A205
A206
A207
A208
A209
A210
Contents
Communications Port 0 Completion Code
Communications Port 1 Completion Code
Communications Port 2 Completion Code
Communications Port 3 Completion Code
Communications Port 4 Completion Code
Communications Port 5 Completion Code
Communications Port 6 Completion Code
Communications Port 7 Completion Code
The meanings of the communications port completion codes are the same as
those for FINS commands and responses (response codes). When
CMND(490) is used, however, even if a FINS command has an abnormal
completion, it will not be reflected in the communications port completion
code. For details, refer to Communications Port Error Flag and Response
Codes CMND(490) on page 101.
Bits 08 to 15 in the communications port completion code correspond to the
first byte of the response code, and bits 00 to 07 correspond to the second
byte.
Communications Port Error Flag and Response Codes CMND(490)
Errors that occur when CMND(490) is used generate a Communications Port
Error Flag and are recorded in a communications port response code only in
the following cases:
• When a response timeout error has occurred.
• When the number of communications data bytes exceeds the maximum
value for the Unit (i.e., more than 1,014 bytes) after the FINS command
code for the FL-net Unit.
• When the actual number of response bytes is greater than the number of
reception bytes that has been set. (The response is not stored in this
case.)
Errors other than these are recorded in the response codes of the responses
stored from the beginning response storage word onwards. Be careful of
these, because there are no Communications Port Error Flags and they are
not recorded in a communications port response code.
101
Section 7-2
Sending Commands from a PLC
Timing of
Communications Flag
Changes
• The Communications Port Enabled Flag remains OFF during communications and turns ON when they are completed (regardless of whether or
not an error occurs).
• The Communications Port Error Flag retains its status until the next transmission or reception.
• The Communications Port Error Flag turns OFF with the execution of the
next communications instruction even if there was an abnormal completion.
Example
Communications Port Enabled Flag
Instruction 1
being executed.
Communications instruction:
SEND(090), RECV(098), CMND(490)
Instruction 2
being executed.
Instruction 3
being executed.
Communications Port Error Flag
Communications Port Completion Code
Completion
102
0000 (Normal completion)
(Unit address setting error)
0000 (Normal completion)
Section 7-2
Sending Commands from a PLC
7-2-2
Program Example
Execution
condition (See note)
000000
A20207 120002
S
KEEP
120000
R
When the Communications Port Enabled Flag for port 7
is ON, and RECV(098) is not being executed, the send
execution program will start when execution condition
CIO 000000 turns ON.
120001
120000
@MOV(21)
#000A
D00000
Input CIO 120000 remains ON from the start of
SEND(090) execution until completion.
Control Data Creation
Word
@MOV(21)
#0002
D00001
@MOV(21)
Contents
00
0A Number of send words = 10
D0001
00
02 Destination network number = 2
D0002
04
00 Destination node number = 4
D0003
07
05 Response required.
#0400
D00002
Meaning
D0000
Destination unit address = 0
Communications port No. used = 7
@MOV(21)
#0705
D00003
Number of retries = 5
D0004
00
64 Response monitor time = 10 s
@MOV(21)
#0064
D00004
Send Data Creation
@XFER(70)
#000A
Ten words of data from word CIO 0000 is
stored from D00010 onwards.
0000
D00010
@SEND(90)
D00010
D00020
Ten words of data from D00010 at the local node is
sent to D00020 onwards at network number 2, node
number 4, unit address 0 (the PC).
D00000
120000
A20207 (See note)
DIFU(13)
120001
120000
Reset Input Creation
A21907
120000
Send Error Display
(Continued on next page.)
103
Section 7-2
Sending Commands from a PLC
(Continued from previous page.)
Execution
condition (See note)
000001
A20207 120000
S
KEEP
120002
When the Communications Port Enabled Flag for port 7
is ON, and SEND(090) is not being executed, the transmission execution program will start when execution
condition CIO 000001 turns ON.
R
120003
120002
@MOV(21)
#0010
D00005
Input CIO 120002 remains ON from the start of
RECV(098) execution until completion.
Control Data Creation
Word
@MOV(21)
Contents
Meaning
#0003
D0005
00
10 Number of reception words = 16
D00006
D0006
00
03 Destination network number = 3
D0007
20
00 Destination node number = 32
Destination unit address = 0
D0008
07
05 Response required.
Communications port No. used = 7
D0009
00
00 Response monitor time = Default
@MOV(21)
#2000
D00007
@MOV(21)
Number of retries = 5
#0705
D00008
@MOV(21)
#0000
D00009
@RECV(98)
A100
A total of 16 words of data beginning from word A100
at network number 3, node number 32, unit address 0
(the PC) is received at word CIO 2000 onwards of the
local node.
2000
D00005
120002
A20207 (See note)
Reset Input Creation
DIFU(13)
120003
120002
A21907
121001
120002
120003
A21907
Reception Error Display
Reception Data Processing
@XFER(70)
#0016
2000
If there is no reception processing completion error, the
16 words of data received from word CIO 2000 onwards is stored at D00040 onwards.
D00040
Note The Communications Port Enabled Flags at bits 0 to 7 in word A202 turn OFF
even when the PLCMR(260) instruction is being executed using the ports corresponding to those flags.
104
Section 7-3
Command Codes and Response Codes
7-3
7-3-1
Command Codes and Response Codes
Command Code List
The FL-net Unit supports and therefore automatically returns a response to
the command codes listed in the following table (FINS commands addressed
to the FL-net Unit).
Command code
MRC
SRC
05
06
08
21
29
01
01
01
02
01
02
03
04
23
24
Function name
CONTROLLER DATA READ
CONTROLLER STATUS READ
INTERNODE ECHO TEST
ERROR LOG READ
TRANSPARENT MESSAGE FRAME SEND
TRANSPARENT MESSAGE RECEIVED FRAME READ
WORD BLOCK DATA READ (unspecified node number)
WORD BLOCK DATA WRITE (unspecified node number)
WORD BLOCK DATA READ (specified node number)
WORD BLOCK DATA WRITE (specified node number)
Note The WORD BLOCK DATA READ/WRITE commands with an unspecified
node numbers are provided to ensure compatibility with applications created
with the CS1W-FLN01. Use the WORD BLOCK DATA READ/WRITE commands with specified node numbers to create new applications.
7-3-2
Response Code List
Response codes are 2-byte codes that indicate the results of command execution. They are returned in the response following the command code.
The first byte of a response code is the MRES (main response code), which
categorizes the results of command execution. The second byte is the SRES
(sub-response code) which specifies the results.
The relationship between the MRES and the execution results are shown in
the table on the next page.
Command Response
code
code
MRC:
SRC:
MRES:
SRES:
Main request code
Sub-request code
Main response code
Sub-response code
MRC SRC MRES SRES
105
Section 7-4
CS/CJ-series Memory Areas and Virtual Addresses
The MRES codes are shown in the following table along with the results they
indicate. Refer to 10-1 Troubleshooting with Indicators for details on response
codes including the SRES.
MRES
00
01
02
03
04
05
10
11
22
23
25
7-4
Execution results
Normal completion
Local node error
Remote node error
Unit error (controller error)
Service not supported
Routing error
Command format error
Parameter error
Status error
Operating environment error
Unit error
CS/CJ-series Memory Areas and Virtual Addresses
Virtual address space is allocated in the Memory Area where messages are
read and written in FL-net (Ver. 2.00). The virtual address space in the Memory Area of all manufacturer’s FL-net (Ver. 2.00) nodes is allocated in 4-byte
hexadecimal within the virtual address space range, so you can read and
write between the Memory Areas of different equipment simply by specifying
the address.
The following table shows virtual address space allocation for OMRON PLCs
(CPU Units). Refer to the manual of other manufacturer’s FL-net (Ver. 2.00)
nodes for details on their virtual address space allocation.
Virtual Address Space for OMRON CS/CJ-series CPU Units
DM Area
Timer Area
Counter Area
EM Area Bank 0
Bank 1
Bank 2
Bank 3
Bank 4
Bank 5
Bank 6
Bank 7
Bank 8
Bank 9
Bank A
Bank B
Bank C
CIO Area
Work Area
Holding Area
Auxiliary Area
106
Area
D00000 to D32767
T000 to T4095
C000 to C4095
E0_00000 to E0_32767
E1_00000 to E1_32767
E2_00000 to E2_32767
E3_00000 to E3_32767
E4_00000 to E4_32767
E5_00000 to E5_32767
E6_00000 to E6_32767
E7_00000 to E7_32767
E8_00000 to E8_32767
E9_00000 to E9_32767
EA_00000 to EA_32767
EB_00000 to EB_32767
EC_00000 to EC_32767
0000 to 6143
W000 to W511
H000 to H511
A000 to A447
A448 to A959
Read/Write
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R
RW
Address
00020000 to 00027FFF
00090000 to 00090FFF
000A0000 to 000A0FFF
00200000 to 00207FFF
00210000 to 00217FFF
00220000 to 00227FFF
00230000 to 00237FFF
00240000 to 00247FFF
00250000 to 00257FFF
00260000 to 00267FFF
00270000 to 00277FFF
00280000 to 00287FFF
00290000 to 00297FFF
002A0000 to 002A7FFF
002B0000 to 002B7FFF
002C0000 to 002C7FFF
00300000 to 003017FF
00310000 to 003101FF
00320000 to 003201FF
00330000 to 003301BF
003301C0 to 003303BF
Section 7-5
Command/Response Reference
7-5
Command/Response Reference
This section describes the FINS commands that can be sent to FL-net Units
and the responses to each command.
Reading Reference Pages
The reference pages for FINS commands are configured as follows:
• Command Name
Gives the command name and code.
• Function
Provides a brief description of the command's function.
• Command Block
Gives the command format. Each box represents one byte.
• Response Block
Shows the response format. Each box represents one byte.
• Parameters
Describes parameter details like the setting range.
• Precautions
Provides precautions regarding the use of commands.
• Response Codes
Provides response codes for command responses.
7-5-1
CONTROLLER DATA READ
Reads the controller data.
Command Block
05
01
Command
code
Response Block
05
01
Command
code
Response
code
20 bytes
20 bytes
4 bytes
4 bytes
Model
Version
IP address
Subnet
mask
6 bytes
Mode
setting
Ethernet
address
Parameters
Model, Version
(Response)
The FL-net Unit model and version are returned as ASCII characters using 20
bytes each (i.e., 20 characters each). If all bytes are not used, the remaining
bytes will be all spaces (ASCII 20 Hex).
Examples
Model: CS1W-FLN22, CJ1W-FLN22
Version:V1.00
IP Address, Subnet Mask
(Response)
The FL-net Unit IP address and subnet mask are returned as 4 bytes each.
107
Section 7-5
Command/Response Reference
Mode Setting (Response)
The mode set in the system setup is returned.
Second byte
First byte
15
14
13
12
1) System type
11
10
−
−
9
8
7
6
5
4
3
2
−
1
0
−
3) FA Link allocation table storage method
2) IP
address
setting
4) FA Link startup method
5) Message procedure check
6) Broadcast format
7) Data sending order (sequential/reverse direction)
8) Baud rate
1. System Type
Bits 12 to 15 show the type of Unit.
Bit
15
0
Others
14
0
Description
13
0
12
1
FL-net Unit
Parameter error
2. IP Address Setting
These bits provide details about the type of IP address settings.
Bit
Description
7
0
1
6
0
0
0
1
1
1
Operates with the IP address switch setting on the back of the Unit.
Operates with the IP address switch setting on the back of the Unit
and the node address switch setting on the front of the Unit.
Operates with the CPU Bus Unit system setting that is set through the
CX-FLnet or FL-net Unit Support Software.
Operates with the default setting
(192.168.250.node_address_switch_setting).
3. FA Link Allocation Table Storage Method
This bit provides details about where the data link (FA link allocation) table
is stored.
Bit
0
Description
0
Store in CPU Unit
Stores the data link tables (FA link allocations) in the System Bus Unit setup
area of the CPU Unit.
Store in FL-net Unit
Stores the data link tables (FA link allocations) in the FL-net (Ver. 2.00) Unit
EEPROM.
1
108
Section 7-5
Command/Response Reference
4. FA Link Startup Method
This bit provides details about the communications settings (automatic for
manual log in) when PLC power is turned ON.
Bit
1
0
1
Description
Automatic Log In
Communications are enabled automatically by turning ON PLC power.
Manual Log In
Communications are not enabled by turning ON PLC power. With this setting,
communications are enabled instead by turning ON the FA Link Connection
Start Bit after the PLC is turned ON. (Refer to Unit Control Bits (CPU Unit to
FL-net Unit) on page 52.)
5. Message Procedure Check
This bit provides details about the message procedure settings (checked
or not checked).
Bit
1
0
1
Description
Checked
Select only when sending messages between OMRON FL-net (Ver. 2.00)
Units.
Not checked
Select when connected to another manufacturer’s FL-net (Ver. 2.00) node.
6. Broadcast Format
This bit provides details about the broadcast format settings.
Bit
1
0
1
Description
***.***.255
255.255.255.255
7. Data Sending Order (Sequential/Reverse Direction)
Bit
1
0
1
Description
Sequential order
Same order as earlier FL-net Unit (CS1W-FLN02 and CS1W-FLN12).
Reverse order
Swaps the upper/lower byte order of word data before sending data link data.
8. Baud Rate
This bit is used to set the baud rate.
Bit
1
0
1
Ethernet Address
(Response)
Description
10 Mbps fixed
Communications are performed at 10 Mbps.
Automatic detection
The baud rate between hubs is automatically detected. Communications are
performed at 100 Mbps depending on the hub.
The Ethernet address of the FL-net Unit is returned.
Note The Ethernet address is marked on the label on the side of the FLnet Unit.
109
Section 7-5
Command/Response Reference
Response Codes
Response code
0000
1001
7-5-2
Description
Normal
Command too large
CONTROLLER STATUS READ
Reads the controller status.
Command Block
06
01
Command
code
Response Block
06
01
10 bytes
Command Completion
code
code
Node name
10 bytes
10 bytes
Vendor name
Manufacturer’s
model
Node number
Upper level Range 1 Range 1
status
storage
storage
Token monitoring timeout setting
Range 2
storage
Range 2
storage
Address
Size
FA Link status
Local node status
Protocol version
Min. allowable frame interval
Response Codes
Response code
0000
1001
7-5-3
Description
Normal
Command too large
INTERNODE ECHO TEST
Performs the FINS echoback test.
Command Block
08
01
1 to 1,020 bytes
Command
code
Test data
Response Block
08
01
Command Completion
code
code
1 to 1,020 bytes
Test data
Parameter
Test Data (Command,
Response)
110
Specifies data sent to a specified node by a command that is 1 to 1,020 bytes
long. The response returns test data that is the same as the data sent in the
command. There is something clearly wrong if the data in the command does
not match the test data in the response.
Section 7-5
Command/Response Reference
Precautions
• This command sends a FINS command (0801) message to a remote
node by VENDER MESSAGE (request/transaction code: 65016).
• The Unit receiving this command must be an OMRON FL-net Unit.
Response Codes
Response code
0000
1001
1002
7-5-4
Description
Normal
Command too large
Command too small
ERROR LOG READ
Reads the error log.
Command Block
21
02
Command
code
Beginning
record
number
Number
of
records
Response Block
21
02
Command Response Maximum
code
number
code
of stored
records
10 bytes
Number
of stored
records
10 bytes
Error log
records
Number
of
records
Parameters
Beginning Record Number
(Command)
The first record to be read. The first record number can be specified in the
range between 0000 and 003F (0 to 63 decimal) where 0000 is the oldest
record.
Number of Records
(Command, Response)
The number of records to read is specified between 0001 and 0040 (1 to 64
decimal) in the command. The response returns the actual number of records
read.
Maximum Number of
Stored Records
(Response)
The maximum number of records that can be stored in the error log. Care is
required as the error log differs according to the type of PLC or CPU Bus Unit.
In an FL-net Unit, the maximum number of stored records is fixed at 40 (64
decimal).
Number of Stored
Records (Response)
The number of records stored at the time the command is executed is
returned.
Error Log Data
(Response)
The specified number of error log records from the beginning record number
is returned sequentially. The total number of bytes in the error log is calculated
as the number of records x 10 bytes/record. Each error log record thus comprises 10 bytes, configured as follows:
1st byte
Error
code
10th byte
Detailed
information
Month
Year
Hour
Day
Second
Minutes
111
Section 7-5
Command/Response Reference
Error Code, Detailed Information
Details of the error stored in the record. Refer to 10-3-2 Error Log Error Codes
for details.
Minute, Second, Day, Hour, Year, Month
Indicate the time at which the error stored in the record occurred.
Precautions
If the error log contains fewer records than the number specified in the number of records parameter, all records stored in the error log at the time the
command is executed will be returned and the command executed will end
normally.
Response Codes
Response code
0000
1001
1002
1103
110C
7-5-5
Description
Normal
Command too large
Command too small
Beginning record number is out of range
The number of read records is 0.
TRANSPARENT MESSAGE SEND
Sends a transparent message frame (transaction codes 00000 to 59999).
Command Block
29
01
64 bytes
0 to 1,024 bytes
Command FA message
code
header
FA message data
Response Block
29
01
Command Completion
code
code
Parameters
FA Message Header
(Command)
FA message header for the transparent message frame being sent.
FA Message Data
(Command)
FA message data of the transparent message frame being sent. Refer to the
following pages for details.
Precautions
If this command is executed for a receiving node before the transparent message previously received by the corresponding node has been read by the
TRANSPARENT MESSAGE RECEIVE FRAME READ (29 02) command, an
error will occur (response code 0x0104: Reception buffer overflow).
Response Codes
Response code
0000
0101
0104
0107
0205
1001
1002
112
Description
Normal completion
Local node not part of network.
Reception buffer overflow, queuing not started (reception
side).
Unit's internal buffer is full.
No response from remote node
Command length too long
Insufficient command length
Section 7-5
Command/Response Reference
Response code
1005
110C
2605
Description
Sequence number error, sequence version error
Destination node is local node, TCD > 59999, set to FINS
response required
Servicing in progress
Setting Data for FA Message Headers of Transparent Messages
Set the data of the following FA message headers, except for the shaded
items. The items in the shaded areas are automatically set by the FL-net Unit.
Word
offset
+0
Symbol
H_TYPE (Upper)
1
2
3
4
5
6
H_TYPE (Lower)
TFL (Upper)
TFL (Lower)
SNA (Upper)
SNA (Lower)
DNA (Upper)
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
DNA (Lower)
V_SEQ (Upper)
V_SEQ (Lower)
SEQ (Upper)
SEQ (Lower)
M_CTL (Upper)
M_CTL (Lower)
ULS
M_SZ
M_ADD (Upper)
M_ADD (Lower)
MFT
M_RLT
reserved
TCD
VER
C_AD1
23
24
25
26
27
28
C_SZ1
C_AD2
C_SZ2
MODE
PVER
CBN
PRI
TBN
Item
Header type
Lower: 0x434E fixed
Upper: 0x0000 fixed
Lower: Byte length
Source node address (node number)
Total byte length of header and
data
Destination node address (node
number)
BSIZE
LKS
RCT
TW
Upper: 0x0001 fixed
Lower: Destination node address
Sequential version number
Sequence number:
After 0xFFFFFFFF, returns to 0x00000001.
Message control
Upper layer status (RUN/STOP/ALARM/WARNING/NORMAL)
Message data size in virtual address space
Offset address in virtual address space
Minimum allowable frame interval/response message type
Transaction code
Set between 0x0 and 0xEA5F
Program version
Common Memory (Area 1) first word of address
Common Memory (Area 1) size
Common Memory (Area 2) first word of address
Common Memory (Area 2) size
Message mode (online/test)
Protocol version/message priority
Current fragment block number
(0x01 fixed)
(CBN)
Total number of fragment blocks
(TBN)
29
30
31
Upper: 0x4641 fixed
(0x01 fixed)
Current block length (byte) (Note: Same value as TFL)
Link status/Token monitoring time
Allowable refresh cycle time
113
Section 7-5
Command/Response Reference
Application Example
This example shows a program with the TRANSPARENT FRAME SEND command.
Sample Configuration
The FINS 2901 command executes at the point indicate by this mark and a
transaction code is sent.
OMRON PLC
FL-net
Unit
OMRON PLC/other manufacturer’s PLC
FL-net
Unit
CPU Unit
By CMND
instruction
Node number 1
Unit number 0
CPU Unit
Node number 2
Arbitrary transaction code frame
Operation
• Set the TRANSPARENT FRAME SEND command starting at D01000 in
the CPU Unit.
• Send the transaction code (100) and 10-byte data to node number 2.
• Store the results of the transmission starting at D02000.
Command
[CMND
S
D
C
S
D
D01000
D02000 :
D00000
C]
+0:
+1:
+2:
+3:
+4:
:
+7:
+8:
:
+21:
:
+29:
+30:
:
+32:
:
+36
+0:
+1:
+2:
+3:
2901 Hex
4641 Hex
434E Hex
0000 Hex
004A Hex
(Fixed)
(Fixed)
(Fixed)
= 64 + 10 = 74 bytes
0001 Hex
0002 Hex
Destination node = 2
0064 Hex
Transaction code = 100
0101 Hex
004A Hex
(Fixed)
= 64 + 10 = 74 bytes
Data (10 bytes long)
First word of the stored responses
004C Hex
No. of command data bytes
0004 Hex
No. of response data bytes
(including command
and response codes)
0000 Hex
Remote (destination)
network address = 0
(local network)
0010 Hex
Remote (destination)
node number = 0
(local node number)
Remote (destination)
unit address = 10 Hex
* Be sure to set the unit
address of the FL-net Unit
114
Section 7-5
Command/Response Reference
Response
Execute
condition
0000
00
D02000
+4:
0000 Hex
+5:
0000 Hex
+0
+1
:2901 Hex
:0000 Hex
to the unit number +
10 Hex.
Response required,
communication port no. = 0,
number of retries = 0
Response monitoring time
(default: 2 s)
Response code
(completed normally)
• Sends a transparent frame just once when the Network
Communications Port Enabled Flag for port 0 and the
execute condition (CIO 000000) turn ON.
A202
00
• Creates control data starting at D00000.
@MOV(21)
# 004C
D00000
@MOV(21)
# 0004
D00001
@MOV(21)
# 0000
D00002
Word
D00000
D00001
D00002
D00003
Content
00
4C
00
04
00
00
00
10
D00004
00
02
D00005
00
00
Meaning
Command data length: 76 bytes
Response data length: 4 bytes
Destination network address = 0
Destination node address = 0
Destination unit address = 10 Hex
Response required
Communications port No. = 0
Retries: 2
Response Monitoring Time = 2 s
@MOV(21)
# 0010
D00003
@MOV(21)
# 0002
D00004
@MOV(21)
# 0000
D00005
(Continued next page.)
115
Section 7-5
Command/Response Reference
Execute
condition
0000
00
A202
00
@MOV(21)
# 2901
D01000
@MOV(21)
#4641
D01001
@MOV(21)
#434E
D01002
@MOV(21)
# 0000
D01003
@MOV(21)
# 004A
D01004
• Creates control data (command code/FA message
header) starting at D01000. Parameters that are
generated automatically by the FL-net Unit do not
have to be set.
Word
D01000
D01001
D01002
D01003
D01004
D01007
D01008
D01021
D01029
D01030
Content
29
01
46
41
43
4E
00
00
00
4A
00
01
00
02
00
64
01
01
00
4A
Meaning
Command code
H_TYPE Upper = (Fixed value)
H_TYPE Lower = (Fixed value)
TFL Upper = (Fixed value)
TFL Lower = 74 bytes
DNA Upper = (Fixed value)
DNA Lower = 2
TCD = 100
CBN/TBN = (Fixed value)
BSIZE = 74 bytes
@MOV(21)
# 0001
D01007
@MOV(21)
# 0002
D01008
@MOV(21)
# 0064
D01021
@MOV(21)
# 0101
D01029
Execute
condition
0000
00
A202
00
@MOV(21)
# 004A
D01030
@XFER(70)
# 0005
0000
D01033
@CMND(490)
D01000
D02000
D00000
DIFU(13)
000000
116
• Creating send data: Stores the 10-byte long data
(5 words) from word 0000 starting at D01033 (FA
message data).
• Sends the TRANSPARENT FRAME SEND command to the FL-net Unit using the CMND(490)
instruction.
• Turns OFF execute condition 000000.
Section 7-5
Command/Response Reference
7-5-6
TRANSPARENT MESSAGE RECEIVE FRAME READ
Reads a transparent message (transaction code: 00000 to 59999) that was
received. Execute this command when bit 1 (Readable Message Received
Flag) of the Unit Status CPU Bus Unit Area in the CIO Area (CIO 1500 + unit
number × 25 + 6 words) is ON. An error response (response code 0x0001)
will be returned if this command is executed when bit 1 is OFF.
Command Block
29
02
Command
code
Response Block
29
02
0 to 1,024 bytes
64 bytes
Command Completion FA message header
code
code
FA message data
Parameters
FA Message Header
(Response)
FA message header of response to the transparent message frame that was
transmitted.
FA Message Data
(Response)
FA message data of the response to the transparent message frame that was
transmitted. Refer to the following pages for details.
Response Codes
Response code
0000
0001
1001
Description
Normal completion
Reception buffer overflow, queuing not started (reception side)
Command length too long
Setting Data for FA Message Headers of Transparent Messages
When reading received message frames from a user program, check the nonshaded items from the following FA message header data.
Offset
+0
words
+1
+2
Symbol
H_TYPE (Upper)
TFL:
Total number of bytes of FA message header and FA message data
SNA:
Source node number
TCD:
Transaction code
Header type
Item
Upper: Header type: 0x4641 fixed
H_TYPE (Lower)
TFL (Upper)
TFL (Lower)
Total byte length of header and data
+3
+4
+5
+6
+7
+8
+9
+10
+11
SNA (Upper)
SNA (Lower)
DNA (Upper)
DNA (Lower)
V_SEQ (Upper)
V_SEQ (Lower)
SEQ (Upper)
SEQ (Lower)
Source node address (node number)
Lower: Header type: 0x434E fixed
Upper: 0x0000 fixed
Lower: Byte length
Destination node address (node num- Upper: 0x0001 fixed
ber)
Lower: source node number
Sequence version number
Sequence number
After 0xFFFFFFFF, returns to
0x00000001
117
Section 7-5
Command/Response Reference
Offset
Symbol
Item
+12
+13
+14
+15
+16
+17
+18
+19
+20
+21
+22
+23
+24
M_CTL (Upper)
M_CTL (Lower)
ULS
M_SZ
M_ADD (Upper)
M_ADD (Lower)
MFT
M_RLT
reserved
TCD
VER
C_AD1
C_SZ1
C_AD2
Message control
+25
+26
+27
+28
C_SZ2
MODE
PVER
CBN
Common Memory (Area 2) size
Message mode (online/test)
Protocol version/message priority
Current fragment block number
(CBN)
Total number of fragment blocks
(TBN)
Current block length (byte)
Note: Same value as TFL value
Link status/token monitoring time
Allowable refresh cycle time
+29
BSIZE
+30
+31
LKS
RCT
PRI
TBN
TW
Upper layer status (RUN/STOP/ALARM/WARNING/NORMAL)
Message data size in virtual address space
Offset address of virtual address space
Minimum allowable frame interval/response message type
Transaction code
Set between 0 and 0xEA5F
Program version
Common Memory (Area 1) first word address
Common Memory (Area 1) size
Common Memory (Area 2) first word address
0x01 fixed
0x01 fixed
Application Example
This example shows a program with the TRANSPARENT FRAME READ command.
Sample configuration
The FINS 2902 command executes at the point indicated by this mark and the
PLC reads the transaction code that was received.
OMRON PLC
FL-net
Unit
OMRON PLC/other manufacturer’s PLC
FL-net
Unit
CPU Unit
By CMND
instruction
Node number 1
Unit number 0
CPU Unit
Node number 2
Arbitrary transaction code frame
Operation
• Set the TRANSPARENT FRAME READ command starting at D01000 in
the CPU Unit.
• Read the transaction code (100) and 10-byte data that was sent by node
address 2.
• Store the results of the reading starting at D02002. (The command code
is stored at D02000 and the response code is stored at D02001.)
118
Section 7-5
Command/Response Reference
Command
[CMND
S
D
C
S
D
D01000
D02000
D00000
C]
+0
+0
+1
+2
+3
:2902 Hex
:First word of the stored responses
:0002 Hex
No. of command data bytes
:004E Hex
No. of response data bytes
(including command
and response codes)
:0000 Hex
Remote (destination)
network address 0
(local network)
:0010 Hex
Remote (destination)
node number 0
(local node number)
Remote (destination)
unit address 10 Hex
* Be sure to set the
unit address of the FL-net
(Ver. 2.00) Unit to the
Unit number + 10 Hex.
Response
D02000
+4
:0000 Hex
+5
:0000 Hex
+0
:2902 Hex
+1
:
+4
+5
+6
+7
:
+22
:
+34
:
+38
:0000 Hex
:0001 Hex
:004A Hex
:0001 Hex
:0002 Hex
Response required,
communication port no. 0,
number of retries 0
Response monitoring time
(default: 2 s)
Response code
(completed normally)
(Undecided)
(Fixed)
=64+10=74 bytes
Destination node number 2
(Undecided)
:0064 Hex
Transaction code 100
(Undecided)
:Data (10-bytes long)
119
Section 7-5
Command/Response Reference
Program Example
Execute
condition
0000
00
A202
00
• When a read enabled message is received and
150001 turns ON: Sends a transparent frame
just once when the Network Communications
Port Enabled Flag for port 0 and the execute condition (CIO 000000) turn ON at port 0.
Read enabled
message received
1506
01
@MOV(21)
0002
D00000
• Creates control data starting at D00000.
Word
D00000
Content
00
02
D00001
00
4E
D00002
D00003
00
00
00
10
@MOV(21)
# 0010
D00003
D00004
00
02
@MOV(21)
# 0002
D00004
D00005
00
00
@MOV(21)
0004E
D00001
@MOV(21)
# 0000
D00002
Meaning
Command data length = 2
bytes
Response data length = 78
bytes
Target network address = 0
Target node address = 0
Target node number address
= 10 Hex
Response required
Communications port No. = 0
Retries = 2
Response monitoring time =
2s
@MOV(21)
# 0000
D00005
Execute
condition
0000
00
Read enabled
message received
A202
00
1506
01
@MOV(21)
# 2902
D01000
• Creates control data (command code) starting at
D01000.
@CMND(490)
D01000
D02000
D00000
• Sends the transparent frame read command to
the FL-net Unit using the CMND(490) instruction.
@XFER(70)
# 0005
D02034
0000
DIFU(13)
000000
120
• Using the data that is received: Stores the 10byte data (5 words) from D02034 (FA message
data) starting at CIO 0000.
• Turns OFF the execute condition (CIO 000000).
Section 7-5
Command/Response Reference
7-5-7
WORD BLOCK DATA READ (UNSPECIFIED NODE NUMBER)
Sends the request message Word Block Data Read (Unspecified Node Number).
The remote node address specified in the control data of the CMND(490)
instruction is used for the read destination node number. The FINS command
can be executed from the CPU Unit in the FL-net Unit, but an error will occur if
the command passes through a FINS network on another layer.
Note
1. This command is provided to ensure compatibility with applications created with the CS1W-FLN01.
2. Use the WORD BLOCK DATA READ/WRITE (specified node number)
commands to create new applications.
Command Block
29
03
Command
code
First address of the
virtual address space
Size
(words)
Response Block
29
03
Command Completion
code
code
0 to 1,024 bytes (512 words)
Data that is read
Parameters
First Address of the
Virtual Address Space
(Command)
Set the first address of data that will be read using hexadecimal format.
Addresses spanning multiple areas cannot be set.
Size (Command)
Specifies up to 512 words for the number of words in data that is received.
Refer to 7-4 CS/CJ-series Memory Areas and Virtual Addresses if the node
that will be read is an OMRON FL-net Unit. If it is another manufacturer’s FLnet node however, refer to the manual for that node.
Response Codes
Response code
0000
0101
0104
0107
0205
1001
1002
1005
110C
2605
Description
Normal completion
Local node not part of network
Reception buffer overflow, queuing not started (reception side)
Unit's internal buffer full
No response from remote node
Command length too long
Insufficient command length
Sequence number error, sequence version error
Source node is local node, requested number of words is
greater than 512.
Servicing in progress
Application Example
This example shows a program with the WORD BLOCK DATA READ
(unspecified node number) command.
Sample configuration
The FINS 2903 command executes at the point indicated by this mark and the
WORD BLOCK READ FRAME (transaction code: 65005) is sent.
121
Section 7-5
Command/Response Reference
OMRON PLC
FL-net
Unit
OMRON PLC/other manufacturer’s PLC
FL-net
Unit
CPU Unit
CPU Unit
By CMND
instruction
Node number 1
Node number 2
Word block read frame;
(Request transaction code: 65005),
(Response transaction code: 65205)
Operation
• Write the WORD BLOCK DATA READ (unspecified node number) command starting at D01000 and store the response data starting at D02000
in the CPU Unit.
• Read the 100-word data from EM0_00000 at node number 2 to a point
after D02002 at node number 1 (D02000 stores the command code and
D02001 stores the response code.).
Command
[CMND
S
S
D
D01000
C]
+0:
+1:
+2:
+3:
D
C
D02000
D00000
+0:
+1:
+2:
+3:
Response
D01000
First address of the virtual
address space
(EM0_00000)
0000 Hex
* Refer to the manual for
other manufacturer’s FL-net
nodes.
0064 Hex
Size of the data that is read
(100)
:First word of the stored responses
0008 Hex
No. of command data bytes
00CC Hex
No. of response data bytes
(including command and
response codes)
0000 Hex
Remote (destination)
network address = 0
0200 Hex
Remote (destination)
node number = 2
+4:
0000 Hex
+5:
0000 Hex
+0:
+1:
2903 Hex
0000 Hex
+2:
:
+102
122
2903 Hex
0020 Hex
Remote (destination)
unit address 00 Hex (ignore)
Response required,
communications port no.
= 0, number of retries = 0
Response monitoring time
(default: 2 s)
Response code
(completed normally)
Data that is read (100 words)
Section 7-5
Command/Response Reference
Program Example
Execute
condition
0000
00
A202
00
@MOV(21)
# 0008
D00000
@MOV(21)
# 00CC
D00001
• Receives a transparent frame just once when the
Network Communications Port Enabled Flag for
port 1 and the execute condition (CIO 000000)
turn ON.
• Creates control data starting at D00000.
Word
D00000
Content
00
08
D00001
00
CC
@MOV(21)
# 0200
D00003
D00002
D00003
00
02
00
00
@MOV(21)
# 0002
D00004
D00004
00
02
D00005
00
00
@MOV(21)
# 0000
D00002
@MOV(21)
# 0000
D00005
Meaning
Command data length = 8
bytes
Response data length = 204
bytes
Target network address = 0
Target node address = 2
Target node number address
=0
Response required
Communications port No. = 0
Retries = 2
Response monitoring time =
2s
(Continued next page)
123
Section 7-5
Command/Response Reference
Execute
condition
0000
00
A202
00
@MOV(21)
# 2903
D01000
• Creates control data starting at D01000.
@MOV(21)
# 0020
D01001
@MOV(21)
# 0000
D01002
@MOV(21)
# 0064
D01003
Execute
condition
0000
00
124
A202
00
@CMND(490)
D01000
D02000
D00000
• Sends the WORD BLOCK READ (unspecified
node number) command to the FL-net Unit using
the CMND(490) instruction.
@XFER(70)
# 0064
D02002
0000
• Using data that is read: Stores the 100-word long
data from D02002 (read data) starting at word
0000.
DIFU(13)
000000
• Turns OFF execute condition 000000.
Section 7-5
Command/Response Reference
7-5-8
WORD BLOCK DATA WRITE (Unspecified Node Number)
Sends a request message Word Block Data Write.
The remote node address specified in the control data of the CMND(490)
instruction is used as the write destination node number. The FINS command
can be executed from the CPU Unit of the FL-net Unit, but an error will occur if
the command passes through a FINS network on another layer.
Note
1. This command is provided to ensure compatibility with applications created with the CS1W-FLN01.
2. Use WORD BLOCK DATA READ/WRITE with specified node numbers to
create new applications.
Command Block
29
04
Command
code
0 to 1,024 bytes (512 words)
First address of the
virtual address space
Size
Data that is written
Response Block
29
04
Command
code
Completion
code
Parameters
First Address of the
Virtual Address Space
(Command)
Size (Command)
Set the first address where data will be written using hexadecimal format.
Addresses spanning multiple areas cannot be set.
Refer to 7-4 CS/CJ-series Memory Areas and Virtual Addresses if the node
where data will be written is an OMRON FL-net Unit. If it is another manufacturer’s FL-net node however, refer to the manual for that node.
Specifies up to 512 words for the number of words in data that is sent.
Response Codes
Response code
0000
0101
0104
0107
0205
1001
1002
1005
110C
2605
Description
Normal completion
Local node not part of network
Reception buffer overflow, queuing not started (reception side)
Unit's internal buffer full
No response from remote node
Command length too long
Insufficient command length
Sequence number error, sequence version error
Source node is local node, requested number of words is
greater than 512.
Servicing in progress
125
Section 7-5
Command/Response Reference
7-5-9
WORD BLOCK DATA READ (Specified Node Number)
Sends the request message Word Block Data Read.
The node number specified in the FINS command block is used as the read
source node number. Specify the FL-net Unit that will execute the FINS command in the control data (network address, node address, unit address) of the
CMND(490) instruction. The FINS command can be executed from the CPU
Unit of the FL-net Unit or through a FINS network on another layer.
Command Block
29
23
Command Node number
code
First address of the
virtual address space
Size
(words)
Response Block
29
23
Command
code
0 to 1,024 bytes (512 words)
Completion
code
Data that is written
Parameters
Node Number (Command)
Set the number of the FL-net (Ver. 2.00) node with data that will be read using
hexadecimal format. Specify 00 (fixed value) for the upper end.
Example
Node number that will be read: 1
FINS command node number: 0001
Refer to 7-4 CS/CJ-series Memory Areas and Virtual Addresses if the node
with data that will be read is an OMRON FL-net Unit. If it is another manufacturer’s FL-net node however, refer to the manual for that node.
Size (Command)
Specifies up to 512 words for the number words in data that is received.
Response Codes
Response code
0000
0101
0104
0107
0205
1001
1002
1005
110C
2605
126
Description
Normal completion
Local node not part of network
Reception buffer overflow, queuing not started (reception side)
Unit's internal buffer full
No response from remote node
Command length too long
Insufficient command length
Sequence number error, sequence version error
Source node is local node, requested number of words is
greater than 512.
Servicing in progress
Section 7-5
Command/Response Reference
Application Example
This example shows a program with the WORD BLOCK DATA READ
(unspecified node number) command
Sample Configuration
The FINS 2923 command executes at the point indicated by this mark and a
WORD BLOCK DATA READ frame (transaction code: 65005) is sent.
OMRON PLC
CLK Unit
CPU Unit
By CMND
instruction
Network 1
Node address 1
OMRON PLC/other manufacturer’s PLC
CLK Unit
FL-net
Unit
FL-net
Unit
CPU Unit
Network 2
Node address 1
Unit number 1
CPU Unit
Node number 2
Word block read frame;
(Request transaction code: 65005),
(Response transaction code: 65205)
Operation
• Write the WORD BLOCK DATA READ (specified node number) command
starting at D01000 and store the response data starting at D02000 in the
CPU Unit.
• Read 100 words of data from the virtual address (00020000 hex) of a
non-OMRON FL-net (Ver. 2.00) node number 2 to addresses starting
from D02002 of an OMRON PLC two levels away on the FINS network
(The command code is stored at D02000 and the response code is stored
at D02001.).
Command
[CMND
S
S
D
D01000
C]
+0:
+1:
+2:
+3:
+4:
D
C
D02000 :
D00000
+0:
+1:
+2:
2923 Hex
0002 Hex
0000 Hex
Read source node number
First address of the virtual
address space
0000 Hex
Refer to the manual for the
other manufacturer’s FL-net
node.
0064 Hex
Size of the data that is read
(100)
First word of the stored responses
000A Hex
No. of command data bytes
00CC Hex
No. of response data bytes
(including command and
response codes)
0002 Hex
Remote (destination)
network address = 2
127
Section 7-5
Command/Response Reference
+3:
0111 Hex
Remote (destination)
node number = 1
Remote (destination)
unit address = 11 Hex
Response
D02000
+4
:0000 Hex
+5:
0000 Hex
+0:
+1:
2923 Hex
0000 Hex
+2:
:
+102
128
* Be sure to set the unit
address of the FL-net Unit
to the unit number +
10 Hex.
Response required,
communication port no.
0, number of retries 0
Response monitoring time
(default: 2 s)
Response code
(completed normally)
Data that is read (100-word long)
Section 7-5
Command/Response Reference
Program Example
Execute
condition
0000
00
A202
00
@MOV(21)
# 000A
D00000
@MOV(21)
# 00CC
D00001
• Sends a transparent frame just once when the
Network Communications Port Enabled Flag for
port 1 and the execute condition (CIO 000000)
turn ON.
• Creates control data starting at D00000.
Word
D00000
Content
00
0A
D00001
00
01
@MOV(21)
# 0111
D00003
D00002
D00003
00
01
02
11
@MOV(21)
# 0002
D00004
D00004
00
02
D00005
00
00
@MOV(21)
# 0002
D00002
@MOV(21)
# 0000
D00005
@MOV(21)
# 2923
D01000
Meaning
Command data length = 10
bytes
Response data length = 204
bytes
Target network address = 2
Target node address = 1
Target node number address
= 11 Hex
Response required
Communications port No.
used = 0
Retries = 2
Response monitoring time =
2s
• Creates control data starting at D01000.
@MOV(21)
# 0002
D01001
@MOV(21)
# 0002
D01002
@MOV(21)
# 0000
D01003
@MOV(21)
# 0064
D01004
Execute
condition
0000
00
@CMND(490)
D01000
A202
00
D02000
D00000
@XFER(70)
# 0064
D02002
0000
DIFU(13)
000000
• Sends the WORD BLOCK READ (unspecified
node number) command to the FL-net Unit using
the CMND(490) instruction.
• Using data that is read: Stores the 100-word data
from D02002 (read data) starting at CIO 0000.
• Turns OFF the execute condition (CIO 000000).
(Continued next page)
129
Section 7-5
Command/Response Reference
Execute
condition
0000
00
A202
00
@MOV(21)
# 2903
D01000
• Creates control data starting at D01000.
@MOV(21)
# 0020
D01001
@MOV(21)
# 0000
D01002
@MOV(21)
# 0064
D01003
Execute
condition
0000
00
A202
00
@CMND(490)
D01000
D02000
D00000
@XFER(70)
# 0064
D02002
0000
DIFU(13)
000000
130
• Sends the WORD BLOCK READ (unspecified
node number) command to the FL-net Unit using
the CMND(490) instruction.
• Using data that is read: Stores the 100-word data
from D02002 (read data) starting at CIO 0000.
• Turns OFF the execute condition (CIO 000000).
Section 7-5
Command/Response Reference
7-5-10 WORD BLOCK DATA WRITE (Specified Node Number)
Sends the request message Word Block Data Write (specified node number).
The node number specified in the FINS command block is used as the write
destination node number.
The control data (network address, node address and unit address) of the
CMND(490) instruction specifies the FL-net Unit that will execute the FINS
command. The FINS command can be executed from the CPU Unit of the FLnet Unit, and it can pass through a FINS network on another layer.
Command Block
29
24
Command
code
0 to 1,024 bytes (512 words)
Node
number
First address of the
virtual address space
Size
Data that is written
Response Block
29
24
Command Completion
code
code
Parameters
Node Number (Command)
Set the number of the FL-net (Ver. 2.00) node where data will be written using
hexadecimal format. Specify 00 (fixed value) for the upper end.
Example
Node number that will be read: 1
FINS command node number: 0001
First Address of the
Virtual Address Space
(Command)
Size (Command)
Set the first address where data will be written using hexadecimal format.
Addresses spanning multiple areas cannot be set.
Refer to 7-4 CS/CJ-series Memory Areas and Virtual Addresses if the node
where data will be written is an OMRON FL-net Unit. If it is another manufacturer’s FL-net node however, refer to the manual for that node.
Specifies up to 512 words for the number of data words that will be written.
Response Codes
Response code
0000
0101
0104
0107
0205
1001
1002
1005
110C
2605
Description
Normal completion
Local node not part of network
Reception buffer overflow, queuing not started (reception side)
Unit's internal buffer full
No response from remote node
Command length too long
Insufficient command length
Sequence number error, sequence version error
Source node is local node, requested number of words is
greater than 512.
Servicing in progress
131
Command/Response Reference
132
Section 7-5
SECTION 8
Communications Timing
This section describes the communications system, communications cycle time, communications cycle time calculation,
data link I/O response time, data link I/O response time calculation, and message service transmission delays.
8-1
Network Communications System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
134
8-2
Communications Cycle Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
134
8-3
Influence on Cycle Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
136
8-4
Calculating the Data Link I/O Response Time . . . . . . . . . . . . . . . . . . . . . . . .
136
8-5
Message Service Transmission Delays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
137
133
Section 8-1
Network Communications System
8-1
Network Communications System
Passes token to next node.
Node 2
Node 3
Node N-1
Passes token to the node with the lowest number.
Node N
Node 1
FL-net is a token-based network. The token, or right to transmit, circulates
around the network and the node holding the token has the right to transmit. If
that node has data to send, it attaches the data to the token. If it has no data
to send, it simply passes the token along.
8-2
Communications Cycle Time
This section describes the method used to calculate the standard communications cycle time.
Calculating the
Communications Cycle
Time
The communications cycle time (T) is the sum total of the token holding time
for each node in the network. Use the following methods to calculate the token
holding time for each node and obtain the total value.
Calculating the Token
Holding Time
The token holding time is the time from when the token is received at the local
node until the token is sent to the next node. The communications cycle time
is the sum total of the token holding time for each node in the network configuration.
Token holding time (µs) at 10 Mbps
= Number of local node data link send words × 5.1
+ Number of local node data link send frames × Minimum allowable frame
interval (See note 1.) + 700
Token holding time (µs) at 100 Mbps
= Number of local node data link send words × 3.16
+ Number of local node data link send frames × Minimum allowable frame
interval (See note 1.) + 400
Set a minimum allowable frame interval of at least 1 ms when using a baud
rate of 100 Mbps. Use at least 1 ms when calculating the cycle time.For
details on standard set values, refer to 4-4-9 Total Number of Receive Errors
(FL-net Unit to CPU Unit).
Note
134
1. Number of local node data link send frames:
When the local node data link send words (total of Area 1 and Area 2) exceeds 512 words, the data will be split into several frames.
Number of local node data link send frames = Number of local node data
link send words ÷ 512 (rounded up to nearest integer)
Any decimal places are rounded up to the nearest integer. Therefore, if the
Section 8-2
Communications Cycle Time
number of local node data link send words is 768 words, 768
which is rounded up to 2 (frames).
÷ 512 = 1.5,
2. Of the nodes in the network, the node with the highest value for the minimum allowable frame interval is used as the network’s minimum allowable
frame interval.
3. The token holding time when using message communications is calculated
as follows:
10 Mbps: Number of send message words × 1.6 + minimum frame interval
100 Mbps: Number of send message words × 0.16 + minimum frame interval
4. Obtain the communications cycle time for networks that include units by
other manufacturers by calculating the total sum of holding time. For information on non-OMRON units, refer to the relevant manuals for the unit.
5. The equation for calculating the communications cycle provides a rough
guide only. The actual communications cycle is affected by delays at the
hubs and other factors.
Token Holding Time Calculation Example
This example is calculated using the following conditions.
Example 1:
Baud rate: 10 Mbps
Number of participating nodes: 10 nodes
Total number of data link words: 680 words (68 words per node)
Minimum allowable frame interval: 100 µs
Message communications: None
Token holding time (µs)
= 68 × 5.1
+ 1 × 100
+ 700
= 1146.8 (µs)
= 1.2 ms
The number of participating nodes is 10 nodes, so the communications cycle
time is calculated as 12 ms (1.2 × 10).
Example 2:
Baud rate: 100 Mbps
Number of participating nodes: 10 nodes
Total number of data link words: 6,000 words (600 words per node)
Minimum allowable frame interval: 1 ms
Message communications: None
Token holding time (µs)
= 600 × 3.16
+ 2 × 1000
+ 400
= 4296 (µs)
= 4.3 ms
The number of participating nodes is 10 nodes, so the communications cycle
time is calculated as 43 ms (4.3 × 10).
Note This calculation example is for a network configuration in which each node is
allocated a uniform number of data link send words. WHen the number of data
link send words is different for each node, obtain the sum total of the token
holding time for each node (= communications cycle time).
135
Section 8-3
Influence on Cycle Time
8-3
Influence on Cycle Time
The time required by the FL-net Unit to exchange data with the CPU Unit is
shown below. Use the value obtained from this equation to calculate the
approximate cycle time of the CPU Unit.
Approximate data processing time =
0.3 + Number of data link words × 0.0011 (ms)
(The number of data link words: The number of data link words sent and
received by the corresponding node).
Note
1. The value obtained from this equation is for a single FL-net Unit.
2. Add the event execution time when executing message services.
8-4
Calculating the Data Link I/O Response Time
The FL-net Unit I/O response time indicates the delay until data from a specified node is detected by another node on the same network. The method
used to calculate I/O response time depends on the amount of data being
exchanged between the FL-net Unit and the PLC (sum of the local node setup
area and other node setup area).
Data set
Sending PLC A
cycle time
(1)
Communications cycle time
(2)
Receiving PLC B
cycle time
(3)
(4)
1. After setting data in the data link area (local node setup area), the FL-net
Unit requires up to one cycle until it can read the data.
2. Up to one communications cycle and the token holding time is required until the data from the local node setup area is sent on the FL-net communications line (i.e., until the token from the local node is held).
3. Up to one communications cycle is required until the data link data received from the remote node is reflected in the PLC’s data link area (for up
to 7,677 words of data link data (local data setup area + other node setup
area)).
4. Up to two cycles are required to refresh data sent across two CPU Unit cycles when the data link data (local data setup area + other node setup area) exceeds 7,677 words.
Receiving PLC B Data Link Area (Sum of Local Node Setup Area and Other Node Setup Area):
7,677 Words Max.
Data link I/O response time =
Sending PLC A cycle time + Communications cycle time
+ Token holding time + Receiving PLC B cycle time
Receiving PLC B Data Link Area (Sum of Local Node Setup Area and Other Node Setup Area):
More than 7,677 Words
Data link I/O response time =
Sending PLC A cycle time + Communications cycle time
+ Token holding time + Receiving PLC B cycle time × 2
136
Section 8-5
Message Service Transmission Delays
8-5
Message Service Transmission Delays
The conceivable criteria are provided here for determining the maximum
transmission delay time from the time the SEND(090)/RECV(098) instructions
are executed from the user program until execution is completed. Use the following equation to calculate the maximum transmission delay times. These
times, however, do not take transmission delay times on the network into
account, so they may be increased depending on the conditions under which
the instructions are executed.
Send
SEND(090) instructions
executed from user
program
CPU Bus Unit Service
Cycle (local node)
CPU Bus Unit Service
Processing (local node)
Communications
Cycle Time
CPU Bus Unit Service Cycle (remote node)
CPU Bus Unit Service Processing (remote node)
Max. delay
The transmission delay for the SEND(090) instruction can be calculated using
the following equation:
Transmission delay = Local node service cycle + local node service processing time + communications cycle time + token holding time + remote node service cycle + remote node service processing time
• CPU Bus Unit Service Cycle
One scan of CPU Unit.
• CPU Bus Unit Service Processing Time
CPU Unit peripheral processing: This is the time required to process
CPU Bus Units and is approximately 1 ms for FL-net Units.
• Communications Cycle Time
Time taken by the token to do one rotation.
Note
1. The actual operating environment can cause transmission delays larger
than those calculated with the methods given here. Among the causes of
longer delays are the following: traffic on the network, traffic through the
FL-net Unit, as well as the parameters and system configuration of the FLnet network.
2. The CPU data set processing time is the standard when the peripheral service time is set in the CPU Unit System Setup to the default of 4%. As this
value is increased, the processing time is shortened.
137
Section 8-5
Message Service Transmission Delays
Receive
SEND(090) instructions
executed from user
program
Service Processing
(local node)
CPU Bus Unit Service Cycle (local node)
CPU Bus Unit Service Processing (local node)
Communications Cycle Time
Service Processing (remote mode)
CPU Bus Unit Service Cycle (remote node)
CPU Bus Unit Service Processing (remote node)
Max. delay
The transmission delay for the SEND(090) instruction can be calculated using
the following equation:
Transmission delay = Local node service cycle × 2 + local node service processing time × 2 + communications cycle time × 2 + token holding time × 2 +
remote node service cycle × 2 + remote node service processing time × 2
• CPU Bus Unit Service Cycle
One scan of CPU Unit.
• CPU Bus Unit Service Processing Time
CPU Unit peripheral processing: This is the time required to process
CPU Bus Units and is approximately 1 ms for FL-net Units.
• Communications Cycle Time
Time taken by the token to do one rotation.
Note.
1. The actual operating environment can cause transmission delays larger
than those calculated with the methods given here. Among the causes of
longer delays are the following: traffic on the network, traffic through the
FL-net Unit, as well as the parameters and system configuration of the FLnet network.
2. The CPU data set processing time is the standard when the peripheral service time is set in the CPU Unit System Setup to the default of 4%. As this
value is increased, the processing time is shortened.
138
SECTION 9
Testing Communications
This section describes functions that allow you to test communications.
9-1
9-2
9-3
Communications Testing Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
140
PING Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
140
9-2-1
FL-net Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
140
9-2-2
Host Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
140
Internode Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
141
9-3-1
Running the Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
141
9-3-2
Checking Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
143
139
Section 9-1
Communications Testing Functions
9-1
Communications Testing Functions
The FL-net Unit provides two functions that allow communications with other
nodes to be tested.
PING Command
The PING command is a common way to perform echoback tests on Ethernet
networks. The PING command can be executed to see if nodes are physically
connected properly and to be sure that IP address are set for the correct
Ethernet nodes.
Internode Testing
Echoback tests with specific nodes can also be performed by setting parameters in the PLC Interface Area and then manipulating specific bits in memory.
This type of internode test can be performed only for nodes that support the
FL-net message service.
9-2
PING Command
The PING command sends an echo request packet to a remote node and
receives an echo response packet to confirm that the remote node is communicating correctly. The PING command uses the ICMP echo request and
responses. The echo response packet is automatically returned by the ICMP.
The PING command is normally used to check the connections of remote
nodes when configuring a network. The FL-net Unit supports both the ICMP
echo request and reply functions.
If the remote node returns a normal response to the PING command, then the
nodes are physically connected correctly and Ethernet node settings are correct.
FL-net Unit
Remote Node
(host computer or Ethernet Unit)
TCP
ICMP
UDP
IP
Ethernet
Echo request
Echo response
9-2-1
FL-net Unit
The FL-net Unit automatically returns the echo response packet in response
to an echo request packet sent by another node (host computer or other FLnet Unit. An FL-net Unit cannot send an echo request packet however.
9-2-2
Host Computer
The PING command can be executed from the host computer to send an
echo request packet to an FL-net Unit. The method for using the PING command from a UNIX computer is given next.
140
Section 9-3
Internode Test
Method
Input the following at the host computer prompt ($):
$ ping IP_address(host_name)
The destination is specified by its IP address or host name. If the host name is
used, the host name must be defined in file /etc/hosts.
Note The PING command is not supported by some host computers.
Application Examples
These examples show sending the PING command to the node at IP address
130.25.36.8. The “$” on the example screen represents the host computer
prompt. User inputs are underlined. Comments are placed after semicolons.
$ ping 130.25.36.8
; Executes PING command
PING 130.25.36.8: 56 data bytes
64 bytes from 130.25.36.8: icmp_seq=0. time=0.ms
64 bytes from 130.25.36.8: icmp_seq=0. time=0.ms
.
.
.
.
.
.
.
.
.
64 bytes from 130.25.36.8: icmp_seq=0. time=0.ms
←Enter Ctrl+C Key to cancel.
ññññ130.25.36.8 PING Statisticsññññ
9 packets transmitted, 9 packets received, 0% packets loss
roundñtrip (ms) min/avg/max = 0/1/16
Normal Execution
$
Abnormal Execution
$ ping 130.25.36.8
; Executes PING command
PING 130.25.36.8: 56 data bytes
←Enter Ctrl+C Key to cancel.
ññññ130.25.36.8 PING Statisticsññññ
9 packets transmitted, 0 packets received, 100% packets loss
$
Refer to operating system documentation for your host computer for details
about using the host computer’s PING command.
9-3
Internode Test
The internode test sends data to and from specified nodes and uses the
responses to check the network.
If a normal response is returned for an internode test, it means that the settings for the FL-net Unit are correct.
9-3-1
Running the Test
The test parameters are set and the test is started and stopped by writing the
required data to the CPU Bus Unit Area (in the CIO Area) of the PLC used to
start the internode test. These setting are made using a Programming Device,
such as a Programming Console.
Test Procedure
1,2,3...
1. Write the test parameters into PLC memory. The test parameters are described following this procedure.
2. Turn ON the Internode Test Start Bit allocated to the FL-net Unit in the CPU
Bus Unit Area. The Internode Test Start Bit is described following the test
parameters. This will begin the internode test.
141
Section 9-3
Internode Test
3. If desired, the test parameters can be changed while the internode test is
actually running. Use the same procedure as used in step 1.
4. Turn OFF the Internode Test Start Bit allocated to the FL-net Unit in the
CPU Bus Unit Area to stop the test.
Note
1. The test parameters are effected as soon as they are set or changed. It is
not necessary to reboot or restart. If the test parameters are changed during the test, however, the new parameters will not be used until the Internode Test Start Bit is turned OFF and then back ON.
2. Line traffic on the Ethernet network will increase during the test, possibly
affecting system performance.
Setting the Test Parameters
Before starting the test, set the following parameters in the CPU Bus Unit
Area (in the CIO Area) of the PLC. The test parameters become effective
immediately after they are set. It is not necessary to reboot or restart the PLC.
Configuration of the test
parameters
The software switches are stored at offsets from the first word calculated with
the formula: first word = 1500 + (25 × unit number + offset)
Setting Range
The parameter setting ranges are given in the following table.
Offset
Parameter
Remote network address
Response monitoring time
(unit: 10 ms)
+1
+2
Note
Settable range
01 to F9 Hex (1 to 249 decimal)
0000 Hex: 2 sec.s
0001 to FFFF Hex (1 to 65535
decimal)
1. The test cannot run across a FINS network.
2. Broadcast transmissions (target node address = FF) cannot be used for
the internode test.
3. A timeout error will occur if no response is received within the set response
monitoring time.
Starting and Stopping the Internode Test
Bit 01 of the first word in the words allocated to the FL-net Unit in the CPU
Bus Unit Area is used as the Internode Test Start Bit. Turn ON bit 01 to start
the internode test and turn bit 01 OFF to stop the internode test. The address
of the word containing the Internode Test Start Bit is calculated by the following formula:
Word = 1500 + (25 × unit number)
Bit
15
14
13
12
11
10
9
8
7
6
5
4
3
2
−
−
−
−
−
−
−
−
−
−
−
−
−
−
1
0
−
Internode Test Start Switch
0: Stop internode test
1: Start internode test
The internode test run status can be confirmed using the TS indicator on the
Unit’s front panel.
TS indicator
Lit
Not lit
142
Run status
Internode test running
Internode test stopped
Section 9-3
Internode Test
9-3-2
Checking Results
The results of the internode test are stored in the fourth through ninth words of
the portion of the CPU Bus Unit Area allocated to the FL-net Unit. The status
information area stores the test status and numbers of test runs and errors.
Test Status
The result of the test run and descriptions of errors are stored as the test status. The test status is stored at the word whose address is calculated by the
following formula:
Stored words = 1,500 + (25 × unit number) + 3
Bit
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
+3
1: Timeout error
Error code
1: Response error
1: Send error
1: Data not matched error
1: Send parameter error
Error Code
If the test is run repeatedly, the code for the latest test results is stored.
Bit
14
15
0
1
Error Flags
0
1
Description
13
0
1
Normal
Insufficient memory error
The bits corresponding to errors are turned ON if errors occur. The flag status
is maintained until the internode test is run again.
Number of Test Runs and Errors
The number of test runs and total errors from the time the test is started until it
is stopped is stored. The configuration of this area is shown in the following
table. Each result is stored at a word relative to the first word the address of
which can be calculated using the following formula:
Stored words = 1500 + (25 × unit number) + 3 to +5
Bit 15
14
13
12
11
+3 --+4 Number of timeout errors
+5 Number of send errors
Note
10 9 8
7
6 5
4
3
2 1
0
No. of test runs
No. of response errors
No. of times the data did not match
1. The contents of the test status area and test runs/errors area are maintained until the internode test is run again.
2. When the number of tests counts to the maximum value (FF Hex), subsequent internode test runs are counted from 0. However, the maximum value is maintained and further errors are not counted when the number of
errors reaches the maximum value.
143
SECTION 10
Troubleshooting
This section describes information and procedures that can be used to troubleshoot problems that sometimes occur with
FL-net (Ver. 2.00) Unit and FL-net communications.
10-1 Troubleshooting with Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
146
10-2 Error Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
148
10-2-1 Unit Status (Unit to CPU Unit). . . . . . . . . . . . . . . . . . . . . . . . . . . . .
148
10-2-2 Network Status (Unit to CPU Unit) . . . . . . . . . . . . . . . . . . . . . . . . .
149
10-3 Error Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
149
10-3-1 Error Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
149
10-3-2 Error Log Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
150
10-4 Troubleshooting Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
152
10-4-1 Startup Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
152
10-4-2 Network Connection Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
154
10-4-3 FINS Communications Problems for SEND(090), RECV(098), and
CMND(490) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
156
10-4-4 Checking IP Address Using PING Command . . . . . . . . . . . . . . . . .
156
10-4-5 Basic Troubleshooting Check List . . . . . . . . . . . . . . . . . . . . . . . . . .
157
10-4-6 General Precautions for FL-net (Ver. 2.00) . . . . . . . . . . . . . . . . . . .
157
10-4-7 Troubleshooting According to Response Codes. . . . . . . . . . . . . . . .
158
10-5 Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
161
10-6 Inspections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
162
145
Troubleshooting with Indicators
Section 10-1
10-1 Troubleshooting with Indicators
The indicators on the FL-net Unit can be used to troubleshoot some errors.
The probable cause and correction for errors that can be determined from the
RUN, HER, and PER LED indicators are listed in the following table.
RUN
Not lit
HER
Not lit
PER
Not lit
Not lit
Not lit
Lit
Lit
---
Lit
Not lit
Lit
Not lit
Lit
Lit
---
Lit
Flashing
---
146
Probable cause
Correction
Power is not being supplied to the CPU Unit Supply power.
or the power supply voltage is too low.
Make sure that the correct voltage is being
supplied.
The FL-net Unit is faulty.
Replace the FL-net Unit.
The CPU Unit or Backplane is faulty.
Replace the CPU Unit or the Backplane.
The mounting screws on the FL-net Unit
Tighten the mounting screws to the speciare loose.
fied torque.
The unit number on the FL-net Unit is not
Correct the unit number setting.
set correctly on the rotary switch.
The I/O tables are not registered in the
Register the I/O tables.
CPU Unit.
The same unit number is being used on
Correct the unit number.
another Unit as well.
The CPU Unit is faulty.
Restart the CPU Unit. If the problem persists, replace the CPU Unit.
There is a mistake in the CPU Bus Unit
Read the error history and correct the data
Setup or routing tables.
that is causing the error. If the problem persists, replace the CPU Unit.
Memory in the CPU Unit is faulty.
Restart the CPU Unit. If the problem persists, replace the CPU Unit.
The CPU Unit is faulty.
Restart the CPU Unit. If the problem persists, replace the CPU Unit.
Failed to read files in Memory Card for the Check that the Memory Card is installed
simple backup function.
and that the correct backup file is saved in
the Memory Card.
The node address is set outside the correct Set the node number to between 01 and F9
range on the rotary switches.
Hex.
The FL-net Unit is faulty.
Restart the PLC. If the problem persists,
replace the FL-net Unit.
The communications cable is disconThe communications cable may be disconnected.
nected. Check that the communications
(Transceiver Error Flag: ON)
cable is connected securely.
An error occurred in EEPROM.
Restart the PLC. If the problem persists,
replace the FL-net Unit.
The IP address is set incorrectly.
Correct the IP address. Do not set any of
the following IP addresses.
• Host IDs that are all 0 or all 1.
• Network IDs that are all 0 or all 1.
• Subnetwork IDs that are all 1.
• Addresses beginning with 127 (7F Hex).
Another node with the same node number
The PLC was removed from the network
because another node with the same node is already present on the network. Change
the setting so no two nodes have the same
number was detected.
number.
Section 10-1
Troubleshooting with Indicators
RUN
Lit
HER
---
PER
Flashing
Probable cause
Correction
The Unit was removed because it was con- FL-net Units (Ver. 1.00) cannot operate on
nected to an FL-net (Ver. 1.00) network.
the same network as other FL-net Units.
Check the configuration of the network and
make sure it consists solely of compatible
FL-net Units.
Noise or other factor may be affecting netCommunications have stopped due to a
LAN controller error (LAN Controller Error work communications. Check the grounding of the network equipment and devices.
Flag: ON)
Restart the CPU Unit if this error occurs.
A PLC area cannot be accessed (data allo- Re-check the system settings on the Unit.
cation error).
Check to see if an area not in the PLC, an
unusable area (i.e., the number of EM
banks or where files are present), or an
area where data cannot be written is being
accessed.
Check that local node addresses are not
allocated in an other node setup area.
147
Section 10-2
Error Status
10-2 Error Status
The FL-net Unit will output error status to the following word in the PLC Data
Area Interface of the CPU Unit. This information can be used in troubleshooting errors.
10-2-1 Unit Status (Unit to CPU Unit)
1,500 + (25 × unit number) + 6
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
FA link operation
Readable receive
FA Link (Common Memory) Area allocation error
Data Link (PLC) Area allocation error
Token monitoring timeout error
IP address setting error
Transceiver error
EEPROM error
The corresponding bit will turn ON when an error occurs
Bit
8
9
10
12
14
15
148
Name
Correction
FA Link (Common Memory) This bit turns ON if there is a Common Memory allocation error in the local node
Area allocation error
setting range of the FA Link (Data Link) settings. Use the CX-FLnet or FL-net Unit
Support Software to re-set the FA Link (Common Memory) allocation settings
Data Link (PLC) Area allo- This bit turns ON if there is a PLC Area allocation error in the local node setting
cation error
range or another node setting range of the FA Link (Data Link) settings. Use the
CX-FLnet or FL-net Unit Support Software to re-set the FA Link (Common Memory)
allocation settings.
Token monitoring timeout
This bit turns ON if a token monitoring timeout occurs while the local node is holderror
ing the token. Processing may be delayed because of system traffic, so recheck the
system configuration or extend the token monitoring timeout setting with the CXFLnet or FL-net Unit Support Software.
IP address setting error
The following cannot be used as IP address settings.
• Host IDs that are all 0 or all 1.
• Network IDs that are all 0 or all 1.
• Subnetwork IDs that are all 1.
• Addresses beginning with 127 (7F Hex).
Reset the IP address.
Transceiver error
The communications cable may be disconnected. Make sure the cable is mounted
securely.
EEPROM error
Restart the PLC. If the problem persists, replace the FL-net Unit.
Section 10-3
Error Log
10-2-2 Network Status (Unit to CPU Unit)
1,500 + (25 × unit number) + 7
15
14
13
12
11
10
9
8
−
7
6
5
4
3
2
1
0
−
−
−
−
−
−
−
−
Duplicate node number detected
Frame standby
FL-net version mismatch detected
Upper level operating signal error (PLC
operation stopped)
Common Memory data in effect notification
Common Memory setting complete
Duplicate Common Memory
Bit
8
Name
Duplicate node number
detected
Correction
This bit turns ON if two nodes have the same node number. All communications
stop and the HER LED indicator flashes.
9
Frame standby
10
FL-net version mismatch
detected
12
Upper level operating signal error (PLC operation
stopped)
13
Common Memory data in
effect notification
Common Memory setting
complete
This bit turns ON if a receive frame cannot be detected. The power may not be ON
at the other node or there is a problem on the communications path. Check the
other node and the communications path.
This bit turns ON if you try to log on to an FL-net (Ver. 1.00) network. All communications stop and the HER LED indicator flashes. Make sure the network is configured entirely of FL-net (Ver. 2.00) nodes. Once this flag turns ON, it will remain ON
until the power is turned OFF and back ON again or until the Unit is restarted.
A stop error or a persistent error has occurred in the CPU Unit. Use the CX-Programmer to clear the error on the CPU Unit.
The routing table settings are incorrect. Correct the routing tables using CX-Integrator.
This bit turns ON if the Common Memory of the FL-net Unit receives data from all
the nodes and it starts to replace data in the CPU Unit.
This bit turns ON if the FL-net Unit can log on to the Data Link with no Common
Memory allocation setting error in the Unit at the time it logs on to the network.
If this flag is OFF when the local node logs on, the local node cannot access the
Data Link and only has access to the message service and token.
This bit turns ON if the same Common Memory is set for the local node that is
attempting to log on to the network and another node that is already logged on to
the network. In this case, the local node cannot access the Data Link and only has
access to the message service and token.
14
15
Duplicate Common Memory
10-3 Error Log
This section describes the error log that is used to record errors that have
occurred during FL-net Unit operation.
10-3-1 Error Log
The error log records errors that have occurred during FL-net Unit operation.
Errors recorded in the log can be read by FINS command. (Refer to ERROR
LOG READ on page 111.)
Logged Errors
The following errors are recorded in the error log.
• Errors in network operation
• Errors in data transfers
• Error in the PLC
149
Section 10-3
Error Log
Error Log Table
Each error is recorded as one record in an error log table. Up to 64 records
can be saved. If more than 64 errors occur, the oldest errors will be deleted
from the error log and the most recent error will be recorded.
The following information is recorded in the error log table.
• Main error code (See table later in this section.)
• Detailed error code (See table later in this section.)
• Time stamp (from the clock in the CPU Unit)
Error Log Location
When an error is detected, the error codes and time stamp are recorded in the
error log in RAM inside the FL-net Unit. Serious errors are also recorded in
EEPROM. The maximum number of errors that can be saved to EEPROM is
32. The errors recorded in EEPROM will be saved even if the Unit is restarted
or power is turned OFF. When the FL-net Unit is started, the contents of the
error log in EEPROM are copied to RAM.
When a FINS command is used to read the error log, the log held in RAM is
read. The error log cannot be cleared.
FINS Commands for Error
Logs
The FL-net Unit’s error log can be read using the CX-FLnet or FL-net Unit
Support Software. The following FINS commands can also be used to read or
clear the error log. For details on each command, refer to 7-5 Command/
Response Reference.
Command
code
MRC
SRC
21
02
Function
ERROR LOG READ
10-3-2 Error Log Error Codes
The error codes are described in the following table. The detailed error code
will provide detailed information on an error.
Error
code
000F
0010
Detailed error code
1st byte
2nd byte
Watchdog timer error in CPU Unit 00
00
CPU Unit service monitor error
monitoring time (ms)
Other CPU error
Bit 11: Unit not in Registered
I/O Tables
CPU Unit initialization error
00
00
Insufficient System Setup Area
00
00
0011
0012
Event timed out
CPU Unit memory error
01: Read
error
02: Write
error
0013
CPU Unit protected
00
0040
Self-removal
Undefined
0001
0002
0006
150
Meaning
03: Routing
table
04: Setup
error
05: CPU Bus
Unit Words
(CIO/DM)
00
Correction
EEPROM
Replace the CPU Unit.
Saved
Check the operating environment. Saved
Create the I/O tables.
Saved
Replace the CPU Unit.
Reduce the number of CPU Bus
Units.
Replace the CPU Unit.
01: Recreate the data specified by
the 2nd byte of the detailed error
code.
02: Clear memory using procedure in the PLC operation manual.
Saved
Saved
Saved
Saved
Remove protection from CPU Unit Saved
memory.
Check the communications cable --hub connection. Use the CXFLnet or FL-net Unit Support Software to increase the value for the
minimum allowable frame interval.
Section 10-3
Error Log
Error
code
0103
0105
0107
0108
010B
010D
010E
Meaning
Resend count exceeded (send
failed)
Node address setting error (send
failed)
Remote node not in network (send
failed)
No Unit with specified unit
address (send failed)
CPU Unit error (send failed)
Routing table error (send failed)
Too many relay points (send
failed)
0111
Command too long (send failed)
0112
Header error (send failed)
0117
0118
Internal buffers full; packet discarded
Illegal packet discarded
0119
Local node busy (send failed)
0120
0121
Unexpected routing error
No setting in IP address table;
packet discarded
Service not supported in current
mode; packet discarded
0123
0124
021A
Commands
Bit 15:
Bits 08 to 14:
Bits 00 to 07:
Responses
Bit 15:
Bits 08 to 14:
Bits 00 to 07:
Internal send buffer full; packet
discarded
Maximum frame size exceeded;
routing failed
Logic error in setting table
00
Correction
EEPROM
Check transceiver at remote node. --OFF
SNA
SA1
ON
DNA
DA1
Destination address not in routing
tables (send failed)
No routing table entry (send
failed)
010F
0110
0122
Detailed error code
1st byte
2nd byte
01: Data link
table
02: Network
parameters
03: Routing
tables
04: Setup
05: CPU Bus
Unit Words
(CIO/DM)
Set the IP address correctly.
---
Check the connection to the
remote node.
Check the unit address at the
remote node.
Troubleshoot the error in the CPU
Unit using the PLC operation
manual.
Set the destination address in the
routing tables.
Set the local node, remote node,
and relay nodes in the routing
tables.
Create the routing tables correctly.
Reconstruct the network or correct the routing tables so that
commands are sent to within a 3level network range.
Check the command format and
set the correct command data.
Check the command format and
set the correct command data.
Change the network so that traffic
is not concentrated.
Check for nodes sending illegal
packets.
Change the network so that traffic
is not concentrated.
Check the routing tables.
Set the remote node in the IP
address table.
Select the IP address table or
both methods for the address conversion method.
Change the network so that traffic
is not concentrated.
Reduce the size of the FINS message.
Recreate the data specified by the
2nd byte of the detailed error
code.
-------
-----
-----
-----------------
----Saved
151
Section 10-4
Troubleshooting Procedures
Error
code
0300
Meaning
Detailed error code
1st byte
2nd byte
0601
Parameter error; packet discarded Commands
Bit 15:
Bits 08 to 14:
Bits 00 to 07:
Responses
Bit 15:
Bits 08 to 14:
Bits 00 to 07:
CPU Bus Unit error
Arbitrary
0602
CPU Bus Unit memory error
Note
01: Read
error
02: Write
error
OFF
SNA
SA1
Correction
EEPROM
Check the command format and
set the correct command data.
---
Restart the CPU Unit. If the problem persists, replace the FL-net
(Ver. 2.00) Unit.
Restart the CPU Unit. If the problem persists, replace the FL-net
(Ver. 2.00) Unit.
Saved
ON
DNA
DA1
06: Error log
Saved
(except
for error
log)
1. The time information in the CPU Unit is used in the CPU Bus Units.
2. If the time information cannot be read from the CPU Unit, the time stamp
in the error log will be all zeros. This can occur due to CPU Unit startup
error, unit number errors, CPU error, and model number errors. If the time
is read out from a Programming Device, the time will be shown as all zeros
in the year 2000.
3. The battery must be installed in the CS-series CPU Unit, the power turned
ON, and then the time set before the clock in the CPU Unit can be used.
The time will not be set correctly in the error log unless the clock time is set
correctly.
4. An error record is not created in EEPROM when a CPU Bus Unit memory
error occurs.
10-4 Troubleshooting Procedures
The following procedures can be used to troubleshoot various problems in
system operation.
10-4-1 Startup Problems
RUN HER PER P/S
Probable cause
Correction
Not lit Not lit Not lit Not lit Power is not being supplied to the CPU Unit Supply power.
or the power supply voltage is too low.
Make sure that the correct voltage is being
supplied.
The mounting screws on the FL-net Unit
Tighten the screws on the FL-net Unit.
are loose.
An error occurred in the FL-net Unit.
Restart the PLC. If the problem persists,
replace the FL-net Unit.
Not lit --Lit
--The same unit number is being used on
Correct the unit number setting and restart
another Unit as well.
the PLC.
The FL-net Unit is not registered in an I/O Use a CX-Programmer or Programming
table.
Console to create a new I/O table.
Not lit Lit
----The node address is set outside the range. Set the node number to between 01 and F9
Hex and restart the PLC.
An error occurred in the FL-net Unit.
Restart the PLC. If the problem persists,
replace the FL-net Unit.
152
Section 10-4
Troubleshooting Procedures
RUN
HER
PER
Lit
---
Lit
P/S
---
Probable cause
The same unit number is being used on
another CPU Bus Unit as well.
An error occurred in the CPU Unit.
The routing table is not set correctly.
The System Setup is not correct.
Lit
Lit
---
---
Lit
---
Flash --ing
Lit
Flash --ing
---
The simple backup function is being used
without the Memory Card installed, or the
backup file does not exist in the Memory
Card.
An error occurred in the FL-net Unit
EEPROM.
An unavailable CPU Unit Area was set in
the Data Link table settings.
The IP address is set incorrectly.
Correction
Correct the unit number setting.
Turn OFF and then restart the CPU Unit. If
the problem persists, replace the CPU Unit.
Use the CX-Integrator to create the correct
routing table.
Please note that all CPU Bus Units and
INNER boards will restart automatically if
the routing table is set using a CX-Integrator.
Use the CX-FLnet or FL-net Unit Support
Software to correct the System Setup and
restart the PLC.
Install the Memory Card and check that the
the Memory Card contains the correct
backup file.
Restart the PLC. If the problem persists,
replace the FL-net Unit.
Use the CX-FLnet or FL-net Unit Support
Software to correct the System Setup and
restart the PLC.
Use the CX-FLnet or FL-net Unit Support
Software to correct the IP address setting.
Restart the PLC after changing the settings.
The PLC was removed from the network
Another node with the same node number
because another node with the same node is already present on the network. Change
number was detected.
the setting so no two nodes have the same
number.
The FL-net Unit was removed because it
FL-net Units and FL-net Units (Ver. 1.00)
was on an FL-net (Ver. 1.00) network.
cannot operate on the same network.
Check the configuration of the network and
make sure it consists solely of FL-net Units.
153
Section 10-4
Troubleshooting Procedures
10-4-2 Network Connection Problems
Failed commu- Power supply
nications
problems
Is the main power supply indicator lit?
Check the power supply, power cable connection and voltage.
Is the power supply indicator lit on the
Check the power supply, power cable conCommunications Unit?
nection and voltage.
Is the HUB power supply indicator lit?
Check the power supply, power cable connection and voltage.
Unstable or failed communications Does each node respond correctly to the Check the power supply and cables of
Ping command?
nodes that fail to respond.
Is the collision indicator lit frequently?
Check the contact between cables and
connectors.
Check the error with an analyzer.
Are there a maximum of four repeater lev- Reconfigure the network using four repeatels?
ers max.
Is the distance between the hub and nodes Reconfigure the network with a distance
(cable length) within 100 m?
between the hub and nodes of 100 m max.
Are the hubs turned ON?
Check the hub power supply and power
cable connection.
Is the correct communications cable con- Use the correct communications cable,
nected?
referring to 1-5 Specifications. For a baud
rate of 100 Mbps, the cable must be category 5 or 5e.
Is the communications cable connector
Check that the communications cable concorrectly attached?
nector is securely attached.
Is the communications cable wired corCheck the hub specifications and use the
rectly (straight/crossed)?
correct wiring for the cable. Check the hub
settings.
Are the hub settings correct?
Correct the settings if the hub uses
SCADA ports or individual settings for
each port. For details, refer to the hub’s
operation manual.
Are there too many cascade connections Switching hubs are subject to transmission
from the switching hub?
delays. Therefore, the cycle time will be
affected if multiple switching hubs are connected using cascade connections. Either
increase the minimum allowable frame
interval or reconfigure the network.
Are Ethernet communications other than Communications will not be performed corFL-net being performed on the same net- rectly if another network is combined with
work?
the FL-net network. Make sure that only
FL-net communications are performed on
the FL-net network.
Is the network load too high?
If a high network load (data link capacity,
number of nodes) is high, increase the
value of the minimum allowable frame
interval. The minimum allowable frame
interval can be changed using the CXFLnet or FL-net Unit Support Software.
After changing the setting, restart the FLnet Unit or cycle the PLC power.
154
Section 10-4
Troubleshooting Procedures
Unstable or
Device setting
failed communi- check for particications (contin- pating nodes
ued)
Is the IP address of the network set properly?
Is the unit number of the FL-net Unit set
properly?
Are the FL-net Unit parameters set properly?
Is the CD (carrier detection) indicator
steadily or intermittently lit?
Is the TX (send) indicator steadily or intermittently lit?
Does the LNK (link) indicator remain lit?
Use a Programming Device or analyzer to
re-check the IP address that was set.
Use a Programming Device or analyzer to
re-check the unit number that was set.
Use a Programming Device to re-check
the parameters that were set.
Check the communications cable and the
AUI power supply.
Re-check the FL-net Unit settings.
Re-check the parameter settings for the
FL-net Unit.
155
Section 10-4
Troubleshooting Procedures
10-4-3 FINS Communications Problems for SEND(090), RECV(098), and
CMND(490)
Did the completion code end normally?
Is the control data set properly?
Refer to 10-1 Troubleshooting with Indicators as
well as the 10-3 Error Log.
Correct the network address, node address and
unit address in the FINS address settings.
Is an IP address set that has the
Use the IP address setting switches (rotary
same HOST ID as a remote node? switches at the back of the Unit) or the CX-FLnet
or FL-net Unit Support Software to correct the IP
address setting.
If you are using the IP address setting switches,
you must turn the PLC OFF and disconnect it
from the network to reset it.
If you are using the CX-FLnet or FL-net Unit
Support Software, restart the PLC after you
change the setting.
Check to see if the relay path (routing table) is
Are you communicating with
defined for FINS messages.
nodes on another network in the
FINS address system?
Use the CX-Integrator to create the correct routing table.
Please note that all CPU Bus Units and INNER
Boards will reset automatically if you use the
CX-Integrator to define the routing table.
10-4-4 Checking IP Address Using PING Command
The PING command can be used from a Windows computer to check the FLnet device connections and IP address settings, without requiring the FL-net
Network Analyzer or other special Programming Device. An overview of operation using the PING function are provided in the following table.
Checking IP
connection
using PING
156
Use the PING command to check that IP connections are correct.
1) From Windows, Select Start - Programs - MS-DOS Prompt to
display the MS-DOS window, as follows
Microsoft (R) Windows
(C) Copyright Microsoft Corp xxxx.xxxx
C:\WINDOWS>
2) Enter the PING command, and execute the basic internode test
between the Link Unit and personal computer. Enter the PING command as either Ping[IP address] or Ping[Host name].
IP Address Example: Ping 192.168.250. 13
The following message will be displayed if the corresponding FL-net
device setting is correct.
Pinging 192.168.250. 13. with 32 bytes of data
Reply from 192.168.250. 13. 13 bytes=32 time=2ms TTL=32
Reply from 192.168.250. 13. 13 bytes=32 time=1ms TTL=32
Reply from 192.168.250. 13. 13 bytes=32 time=1ms TTL=32
C:WINDOWS>
3) The following message will be displayed for a timeout due to a
failed (NG) connection.
Pinging 192.168.250. 13. with 32 bytes of data
Request timed out.
Request timed out.
Request timed out.
Request timed out.
C:WINDOWS>
Section 10-4
Troubleshooting Procedures
10-4-5 Basic Troubleshooting Check List
If you think there is a problem with the system, check the following general
points first.
No.
1
2
3
4
5
6
7
8
9
Item
Is the FL-net Unit installed correctly?
Are the FL-net Unit switches set correctly?
Is the FL-net Unit’s IP address set correctly?
Is the Common Memory Area set correctly?
Are any of the FL-net Unit connectors or other connections loose?
Are the communications cables connected correctly?
Is cross cable being used for a 10Base-T/100Base-TX system?
Does the 10Base-T/100Base-TX cable have category 5 specifications?
Is power being supplied to the Ethernet Hubs and Repeaters?
10-4-6 General Precautions for FL-net (Ver. 2.00)
Refer to the FL-net transmission path standards earlier in this manual or to
IEEE802.3. The following restrictions and precautions also apply specifically
to FL-net Ver. 2.00.
No.
1
2
3
4
5
6
7
8
9
10
11
Details
Communications data from other Ethernet networks cannot be transmitted
on FL-net (Ver.2.00) communications cables.
Do not connect the FL-net (Ver.2.00) to a router.
Switching hubs are not effective on FL-net (Ver. 2.00) networks.
Infrared and wireless media will greatly reduce the realtime communications
performance.
The realtime communications performance will be greatly affected by the
personal computer capacity and the OS and applications being used.
Use the specified IP addresses. Network addresses must be in order (the
standard network address is 192.168.250). IP address node numbers (station numbers) within the input range are recommended.
Network address: 192.168.250
Node number: 1 to 249
Duplication of node numbers cannot be checked in the initial settings. Duplication will not be detected until communications are started and a node
number duplication error occurs.
Make sure that the ground line is connected properly and is sufficiently
thick.
Install the FL-net cables sufficiently far away from noise sources and avoid
laying cables beside power lines.
Realtime performance will deteriorate by the data capacity and other factors
when cyclic data communications and message data communications are
performed simultaneously.
The area used for cyclic data communications (Common Memory Area)
does not need to be allocated sequentially.
Set the SQE switch on the transceiver correctly according to the instruction
manual.
157
Section 10-4
Troubleshooting Procedures
No.
12
13
Details
The regular communications of the entire system are affected by the processing capacity of connected devices. Perform communications using the
communications processing speed for all devices connected to the network
that matches the communications processing capacity (minimum allowable
frame interval) of the slowest device. Therefore, the realtime performance
for the entire system may be greatly reduced by adding devices to the network.
The header section of message data is big endian, but the data is little
endian. The system parameters in the data of transparent messages and
profile read data, however, is big endian. (Big endian data indicates a transmission method that sends the MSB first).
10-4-7 Troubleshooting According to Response Codes
You can troubleshoot the errors in FL-net communications from the response
codes when the SEND(090), RECV(098), or CMND(490) instructions have
been used. For the storage areas of response codes for SEND(090),
RECV(098), and CMND(490) instructions, refer to Communications Port
Completion Codes on page 101 in 7-2 Sending Commands from a PLC.
The table below lists response codes (main and sub-codes) returned for the
FL-net Unit. Refer to the relevant operation manuals for information on
response codes for the CPU Unit, other CPU Bus Units, or FA computers
using FINS communications.
The 6th, 7th, and 15th bits of the response codes have specific functions. The
15th bit will be ON when a network relay error has occurred. Refer to information given after the following table for more information on relay errors. The 6th
bit or 7th bit will be ON when an error has occurred in the destination CPU
Unit. Remove the cause of the error at the destination CPU Unit, referring to
the operation manual for the CPU Unit. The meaning of the response codes
are shown below.
Second byte
First byte
Bit
Sub-response code (SRES)
Main response code (MRES)
1: PLC Fatal Error Flag
1: PLC Non-fatal Error Flag
1: Network Relay Error Flag
Main response
code
Value
Meaning
00
Normal
completion
01
Local node
error
Sub-response code
Probable cause
Remedy
Value
00
Meaning
---
---
---
---
01
Local node
not in network
Local IP
address, node
number
Correct the local IP address
and node number.
04
System load
Reception
buffer overflow
(receiving
node)
Local node System load
busy, cannot send
Message cannot be sent
because the node is not
participating in the network.
No available space n
internal buffer of receiving node.
The internal buffers are
full because there is too
much traffic at the local
node, preventing data
from being sent.
Correct the user application to
reduce the load (traffic) at the
FL-net Unit.
07
158
Check point
Correct the user application to
reduce the load (traffic) at the
FL-net Unit.
Section 10-4
Troubleshooting Procedures
Main response
code
Value
Meaning
02
Remote
node error
Sub-response code
Value
Check point
Probable cause
Meaning
00
Command
data error
Command data
01
Remote
node not in
network
IP address
table, IP router
table
05
Response
timeout
Response to
CONTROLLER
STATUS READ
FINS command
Control data in
instruction
An error response was
returned for the command executed at the
remote node.
IP address of remote
node not set correctly in
IP address table or IP
router table.
Check the command data and
status of the remote node.
Response monitor time
interval too short.
Increase the value for the
response monitor time parameter.
Check the error log and correct as required.
Set IP address of remote
node into IP address table
and, if internetwork transmission is required, into the IP
router table.
Message packet was cor- Increase the number of transrupted by transmission
mit retry attempts.
error.
Read error log
04
05
04: Not exe- 01
cutable
(Service not
supported.)
Unsupported
command
01
Routing
table setting error
Routing
tables not
registered
02
03
04
Remedy
Routing
table error
Too many
relays
The transmission frame
may be corrupted or the
internal reception buffer
is full.
Command code An undefined command
has been used.
FINS header
A short frame (4 bytes) is
frame length
being used for the FINS
header frame.
Routing tables
Remote node address is
not set in the routing
tables.
Routing tables
Cannot determine destination because routing
tables have not been created.
Routing tables
Routing table error
Network configuration
The maximum number of
network levels (3) was
exceeded in the command.
Check the command code.
Check the FINS header frame
length. The FL-net Unit does
not support short headers.
Set the destination address in
the routing tables.
Set routing tables at the local
node, remote node, and any
relay nodes.
Set the routing tables correctly.
Redesign the network or
reconsider the routing table to
reduce the number of relay
nodes in the command. Communications are possible on
three network levels, including
the local network.
159
Section 10-4
Troubleshooting Procedures
Main response
code
Value
Meaning
10
Sub-response code
Value
Command 01
format error
Parameter
error
02
Command
too short
03
Elementdata mismatch
05
Header
parameter
error
03
Address
specification out of
range
Command data
The command is longer
than the max. permissible
length.
Broadcast transmissions
exceeded 1,473 bytes.
Command data The command is shorter
than min. permissible
length.
Command data The designated number
of data items differs from
the actual number in the
command data.
Command data Data for another node on
the same network was
received from the network.
An attempt was made to
send response data for a
broadcast address.
--An error response was
returned for the instruction executed at the
remote node.
First word
The first word in the comaddress in com- mand is in an inaccessimand data
ble area.
Remedy
Check the command format
and set the command data
correctly.
Check the number of items
and the data, and make sure
that they agree.
Check the command format
and set the command data
correctly.
Check the status of the
remote node.
Set a first word that is in an
accessible area.
The bit number is not 00. Check the variable area specified in the results storage area
and set the bit number to 00.
04
Address
range
exceeded
Command data
0B
Response
too long
Command data
0C
0C: Param- Parameters in
eter error
command data
26
Command
error
05
Servicing in System load
progress
30
Access
control
error
00
EEPROM
access
error
Network Relay Errors
Probable cause
Meaning
01: Command too
long
Sequential
error
11
Check point
---
The address set in the
command is not correct.
Correct the address in the
command data, being sure
that the beginning address
plus the number of elements
does not exceed the accessible memory.
The response frame is
Correct the number of data
too long.
elements or other parameters
in the command data for
which the response is being
returned.
Parameters are set incor- Check the command data and
rectly in the command
correct any parameters that
data.
are incorrect.
Execution of the previous Correct the user application to
reduce the load (traffic) at the
command has not been
FL-net Unit.
completed.
The EEPROM device has Restart the CPU Unit. If the
deteriorated.
error recurs, replace the FLnet Unit.
SEND(090) or RECV(098)
For network relay errors using SEND(090) or RECV(098), check the path of
the command using the routing tables and the nature of the error using the
response code to eliminate the cause of the error.
160
Section 10-5
Maintenance
CMND(490)
For network relay errors using CMND(490), the location of the relay error is
recorded in the second through third words of the response, as shown below.
First byte
Second byte
Bit
First word
Command code
Second word
Main response code (MRES)
Relay Error Flag
Third word
Error network address
Sub-response code (SRES)
PLC Non-fatal Error Flag
1: PLC Fatal Error Flag
Error node address
Check the node in which the error occurred, and remove the cause of the
error in that node.
10-5 Maintenance
The FL-net Unit makes up part of a network. Repair a defective FL-net Unit as
soon as possible as it can have a negative effect on the entire network. We
recommend that customers keep one or more spare FL-net Units to allow
immediate recovery of the network.
Replacing an FL-net Unit
Observe the following precautions when replacing the FL-net Unit.
• Always turn OFF the power supply before replacing the FL-net Unit.
• Check that the spare FL-net Unit is operating normally before replacing a
defective Unit with it.
• When returning a defective Unit for repairs, provide as much written information as possible on the symptoms of the problem.
• If a problem occurs with poor contacts, wipe the contacts with a clean
cloth soaked with industrial alcohol. Carefully remove any lint remaining
on the contacts before replacing the Unit.
Settings after Replacing
an FL-net Unit
After replacing an FL-net Unit, set the following to the same settings as were
used on the previous Unit.
• Unit number
• Node address
• Local IP address
• System Setup (only when using the Unit built-in method)
Settings after Replacing a
CPU Unit
The EEPROM in the CPU Unit holds the information listed below. This information must be stored in any new CPU Unit used to replace a defective one.
• Routing tables
• System Setup
161
Section 10-6
Inspections
10-6 Inspections
Perform regular inspections to ensure that the FL-net Unit is functioning to its
optimum capacity.
Items
Most of the parts that make up an FL-net Unit are semiconductor components. None of the parts in the Unit will wear out after a specific lifetime, but
some parts may deteriorate due to extreme operating conditions. Therefore, it
is important to inspect the Unit regularly.
Inspection Interval
Normally inspect once or twice per year. Choose the inspection period
according to the severity of the operating conditions. New installation should
be inspected more frequently until they are judged to be stable.
Inspection Items
Correct any of the items in the table below not conforming to the specified
standard
Item
Environment
Details
Temperature around Unit
Humidity around Unit
Accumulated dust
Mounting
FL-net Unit firmly attached
Transceiver cable connector fully
pushed in
Condition of transceiver cable
Twisted-pair cable connector fully
pushed in
Condition of twisted-pair cable
Standard
0 to 55°C
10% to 90% (with no condensation)
No accumulated dust
No looseness
No looseness
No visible abnormality
No looseness
No visible abnormality
Tools Required for Inspection
The following tools are needed to inspect the FL-net Unit:
Standard Tools
• Flat-blade and Phillips screwdrivers
• Tester or digital voltmeter
• Industrial alcohol and a clean cloth
Tools Required Under
Special Circumstances
• Synchroscope
• Pen oscilloscope
• Thermometer and hygrometer
Replacing CS1W-FLN12 with CS1W-FLN22
Use the following procedure to replace CS1W-FLN12 with CS1W-FLN22.
1,2,3...
1. Read the CS1W-FLN12 settings using the CX-FLnet or FL-net Unit Support Software.
Note The IP address setting method must be changed in the system settings if it is
set to use either the rotary switch on the rear of the Unit or the rotary switch
on the rear of the Unit + the node number. Refer to the following information
under Changing the IP Address Setting Method.
2. Set the hardware switches of the new CS1W-FLN22 to the same values as
the CS1W-FLN12 being replaced. Use the rotary switches on the front of
the Unit to make these settings.
• Unit number setting rotary switch
• Node address setting rotary switch
162
Section 10-6
Inspections
3. Turn OFF the power to the PLC, remove the CS1W-FLN12, and install the
CS1W-FLN22.
4. Turn ON the power to the PLC and check that the RUN indicator on the
CS1W-FLN22 is lit.
5. Write the data that was read using the CX-FLnet or FL-net Unit Support
Software. Select System setting and Unit area setting, and then click the
Write Button in each of the dialog boxes to write the settings.
6. Restart the CS1W-FLN22 or cycle the PLC power to enable the new settings. Make sure that the RUN indicator on the CS1W-FLN22 is lit.
Changing the IP Address Setting Method
The IP address setting method must be changed to either the default setting
(192.168.250 + node No.) or Setup area if the IP address for the CS1WFLN12 was set using the rotary switch on the rear of the Unit. Use the following procedure to change the IP address setting method.
1,2,3...
1. From the CX-FLnet or FL-net Unit Support Software, read the settings from
the CS1W-FLN12.
Check whether the IP address setting method is set to Unit rear rotary SW
+ node No. or Unit rear rotary SW.
2. Turn OFF the power to the PLC, remove the CS1W-FLN12, and confirm
the IP address of the corresponding node from the settings for the IP address setting rotary switch on the rear of the Unit and the node address
setting switch on the front of the Unit.
163
Section 10-6
Inspections
3. Select either of the following settings as the new IP address setting method.
• 192.168.250 + node number
• Setup area
The address specified as 192.168.250 + node number is the default network address for the FL-net standard. The node number corresponds to
the value set using the node address setting rotary switch on the front of
the Unit. When Setup area is selected, enter the IP address for the CS1WFLN12 confirmed in step 2.
4. Click the OK Button.
For the remaining settings, refer to the procedure under Replacing CS1WFLN12 with CS1W-FLN22 and write the settings fro the new CS1WFLN22. Each of the settings is enabled when the FL-net Unit is restarted
or the PLC power is cycled.
Note
1. The CS1W-FLN22 (and CJ1W-FLN22) do not support the IP address setting methods Unit rear rotary SW + node No. or Unit rear rotary SW. If either of these methods is set the HER indicator on the front of the Unit will
be lit red. Use the above procedure to correct the IP address setting method to either 192.168.250 + node No. or Setup area.
2. Consider the following points when replacing a CS1W-FLN22 with a
CS1W-FLN12.
The following new functions provided by the CS1W-FLN22 cannot be used
with a CS1W-FLN12.
• Automatically detecting baud rate (100 Mbps)
• Setting data link data order
Even if these settings are transferred to the CS1W-FLN12, the FL-net Unit
will operate using a baud rate of 10 Mbps and the data link data order will
be in sequential order.
3. To replace a CS1W-FLN22 with another CS1W-FLN22, use the CX-FLnet
or FL-net Unit Support Software Ver. 1.60 or later. If an earlier version of
the FL-net Unit Support Software is used, the new functions of the CS1WFLN22 cannot be set (i.e., the FL-net Unit will operate using a baud rate of
10 Mbps and the data link data order will be in sequential order).
164
Section 10-6
Inspections
Replacing Units Using the Simple Backup Function
The simple backup function can be used to replace Units when using a CS1H, CJ1-H, CJ1M, or CS1D CPU Unit.
Note
1. The Memory Card must be installed in the CPU Unit to enable the simple
backup function.
2. The simple backup function is supported by CS1W-FLN22 and CJ1WFLN22 FL-net Units. The simple backup function cannot be used with
CS1W-FLN02 or CS1W-FLN12. Refer to Replacing CS1W-FLN12 with
CS1W-FLN22 for details on replacing CS1W-FLN02 and CS1W-FLN12
FL-net Units.
1,2,3...
1. Turn ON the power to the CPU Unit and install the Memory Card.
2. Turn ON pin 7 of the DIP switch on the front of the CPU Unit.
3. Press the Memory Card power supply button for 3 seconds to write the setup data to the Memory Card.
The data will start being written to the Memory Card, during which time the
MCPWR indicator on the front of the CPU Unit will be lit. The indicator will
turn OFF after writing has completed normally, at which time all the setup
data including the CPU Unit’s ladder program will be saved as a file in the
Memory Card in the CPU Unit.
4. Turn OFF the power to the CPU Unit and replace the FL-net Unit.
5. Set the rotary switches on the front of the new FL-net Unit (CPU Bus Unit
number and node address) to the same settings as the previous FL-net
Unit.
6. Make sure that pin 7 of the DIP switch on the front of the CPU Unit is turned
ON to enable the setup data to be read from the Memory Card, and then
turn ON the power to the CPU Unit. The FL-net Unit will start reading the
data from the Memory Card, during which time the MCPWR indicator on
the front of the CPU Unit will be lit. The indicator will turn OFF after reading
has completed normally, at which time all the setup data including the CPU
Unit’s ladder program will be read to each Unit from the Memory Card in
the CPU Unit.
7. Turn OFF the power to the CPU Unit and turn OFF pin 7 of the DIP switch
on the front of the CPU Unit.
8. Turn ON the power to the CPU Unit and check the indicator display and
status of the FL-net Unit.
Note For details on the simple backup function (e.g., procedures, file configuration,
indicator displays), refer to the section on simple backup operation in the
SYSMAC CS/CJ-series Programmable Controllers Programming Manual
(W394).
165
Inspections
166
Section 10-6
SECTION 11
CX-FLnet Support Software Operations
This section describes the CX-FLnet Support Software used to make settings for FL-net Units.
11-1 CX-FLnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
168
11-2 Operating Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
170
11-2-1 Starting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
170
11-2-2 Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
171
11-2-3 Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
172
11-2-4 System Setting - CPU Bus Unit Setup Area. . . . . . . . . . . . . . . . . . .
177
11-2-5 System Setting - Local Node Setup Area . . . . . . . . . . . . . . . . . . . . .
178
11-2-6 System Setting - Other Node Setup Area . . . . . . . . . . . . . . . . . . . . .
179
11-2-7 System Setting - Extension Setting. . . . . . . . . . . . . . . . . . . . . . . . . .
180
11-2-8 Unit Area Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
181
11-2-9 Monitor Status Display Function . . . . . . . . . . . . . . . . . . . . . . . . . . .
181
167
Section 11-1
CX-FLnet
11-1 CX-FLnet
Overview
The CX-FLnet Support Software is used to make settings for OMRON FL-net
Units mounted to Programmable Controllers (PLCs). The CX-FLnet Support
Software is installed on a computer running Windows 7 (32-bit or 64-bit edition), Vista (32-bit or 64-bit edition), or XP (32-bit edition).
The CX-FLnet can be used to make settings for the following FL-net Units:
CJ1W-FLN22, CS1W-FLN22, CS1W-FLN12, CS1W-FLN02, CS1-FLN01
FL-net (Ethernet-based control network)
PLC
PLC
PLC
Panel
computer
CNC
RC
Computers with CX-FLnet Unit
Support Software installed
CX-FLnet Functions
The CX-FLnet provides mainly the following functions.
Function
Online connection
Settings
File
Monitor
Applicable
Computers
168
Description
The following two methods can be used for connection.
• Direct PLC Connection
Perform the settings after making a direct serial connection
to each PLC to which FL-net Units are mounted.
• Connection via a Network
Online connection and settings are made from the PLC connected to the computer running CX-FLnet (i.e., the gateway
PLC) to each PLC (i.e., the target PLCs) to which FL-net
Units are mounted via the FL-net network or other networks
(e.g., Ethernet or Controller Link).
The following settings can be made.
• CPU Bus Unit Setup Area
• Data Link Setup
- Local Node Setup Area
- Other Node Setup Area
- Extension Setting
- Unit Area Setup (token watchdog timer)
Communications settings for the online connection and data
link settings can be saved and read in CSV format.
• Data Link Status
• FL-net Unit Status (FA Link active status, transceiver power
supply, received message or not, token monitoring timeout
setting exceeded, and IP address setting error)
• Communications Cycle Time
• Message Sequential Status
• FL-net Unit Error Log
• Status of nodes participating in the FL-net network
The CX-FLnet is available only as one of the features of the CX-One FA Integrated Tool Package. Refer to the CX-One Setup Manual (W444) for details
on the computer system requirements for the CX-One.
Section 11-1
CX-FLnet
The following table shows the amount of hard disk space used when the CXOne is installed with only the CX-FLnet component selected.
CX-One component
CX-FLnet
CX-Server and PLC
Support Software
Required Software
Hard disk
space used
About 1 MB
About 300 MB
Note
Hard disk space used when only the CXFLnet is selected during installation.
These components are always installed.
The following software must be installed on the same computer to use the CXFLnet.
1. CX-FLnet
2. CX-Server (the communications driver)
CX-FLnet Availability
The CX-FLnet is available only as a component of the CX-One FA Integrated
Tool Package. Refer to the CX-One Setup Manual (W444, provided with the
CX-One) for the CX-One installation and uninstallation procedures.
Cat. No.
W444
Checking the Package
Model
[email protected]@C-E
Manual name
Contents
CX-One Setup Man- An overview of the CXual
One FA Integrated Tool
Package and the CX-One
installation procedure
Refer to the CX-One Setup Manual (W444) for details on the contents of the
CX-One package that includes the CX-FLnet.
Cat. No.
W444
Model
Manual name
[email protected]@C-E CX-One Setup
Manual
Contents
Installation and overview of
CX-One FA Integrated Tool
Package.
169
Section 11-2
Operating Procedures
CX-FLnet Operating
Procedure
CX-FLnet installation (Setup will also be performed if CX-One is installed.)
Make communications settings.
↓Unit settings
↓Monitoring
System settings
Select monitor function.
Make settings in CPU Bus Unit Setup Area.
↓
↓
System settings
Display monitor screens.
Make local node settings.
↓
↓
Click the Update Button
System settings
to update the display if required.
Make other node settings.
↓
↓
System settings: Make expansion settings
(data transfer sequence) when required.
↓
Transfer settings.
↓
Turn PLC power ON or restart the FL-net Unit.
↓
Begin FL-net Unit operation.
↓
Confirm that operation is normal, and then save
the settings.
↓
Exit the CX-FLnet.
Note
Check display contents.
↓
Close monitor screens.
↓
Exit the CX-FLnet.
1. The new settings go into effect when the PLC's power is turned ON again
or when the FL-net Unit is restarted.
2. Confirm that the communications settings are correct for the environment
in which they are to be used.
11-2 Operating Procedures
11-2-1 Starting
There are two methods of starting CX-FLnet.
Starting from the Start Menu
1,2,3...
1. Click the Start Button.
2. Select Program - OMRON - CX-One - CX-FLnet.
Starting from the CX-Programmer
1,2,3...
1. Click the I/O tables in the Project Workspace Window in the CX-Programmer.
2. Add an FL-net Unit to the I/O tables. (If the CX-Programmer is online to the
PLC, transfer the I/O tables from the PLC to the computer.)
3. Right-click the FL-net Unit and select Start Special Application from the
pop-up menu.
170
Section 11-2
Operating Procedures
Note After starting the CX-Programmer inheriting the settings from the I/O tables, if
File - New is selected, the unit number of the FL-net Unit for the communications setting will be cleared (i.e., default unit number 0). Reset the unit number
of the FL-net Unit.
11-2-2 Main Window
Menu
Command
File
New
Open
Save
Save As
Open for previous
version
Exit
Edit
Clear all
Copy row
Delete
Contents
Initializes the setup data to the defaults.
Reads saved setup data.
Saves edited setup data.
Saves edited setup data with a new file name.
Reads setup data saved by previous FL-net Support
Software (V1.*)
Quits the CX-FLnet.
Clears all entries in the mapped area table of other node
areas.
Copies the contents of the row in which the cursor is
placed, and adds it as a new row.
Deletes the contents of the row in which the cursor is
placed. Any settings after the deleted row are moved forward in the table.
171
Section 11-2
Operating Procedures
Menu
Command
View
Toolbar
Status bar
Setting To PLC
From PLC
Compare with
PLC
Network setting
Status Datalink Status
Error Status
Communication
cycle time
Message
sequential status
Error log
Node status
Network status
Option Extension setting
Switch display
Help
Index
Version
Contents
Switches the toolbar display.
Switches the status bar display.
Writes to the setup data of the specified Unit.
Reads the contents of the setup data of the specified
Unit to the computer.
Compares system settings on the computer with the
PLC.
Makes network settings to communicate with the PLC.
Shows the FL-net network data link status.
Shows the FL-net Unit error status.
Shows the communications cycle time of the FL-net network.
Shows the message sequence status.
Shows the FL-net Unit error log.
Shows the node status in the FL-net network.
Shows the FL-net network status.
Changes the order of link data bytes.
Switches the display between decimal and hexadecimal.
Shows the help files.
Shows the CX-FLnet version.
11-2-3 Network Settings
This section explains how to connect the PLC to a computer on which the FLnet Unit Support Software is installed. These settings are not required if the
CX-FLnet is launched from the I/O Table Component of the CX-Programmer.
Change the communications settings in the following cases.
• When the CX-FLnet is launched from the I/O Table Component without
inheriting network settings.
• When the CX-FLnet is started from the Windows Start Menu.
• When the FL-net target node is changed (i.e., when the network address,
node address, or unit number is changed).
172
Section 11-2
Operating Procedures
Note The network type (i.e., Connects directly or Connects via network) should normally be set to Connects directly. Use the Connects via network setting when
connecting the computer to a C-series or CVM1/CV-series PLC.
Connecting Directly
Select Connects directly if the computer is connected to the peripheral port
(or COM port) of a CS/CJ-series PLC.
Node 1
CS/CJ Series
CPU unit
Node 2
Node 3
Sets via FL-net network
CX-FLnet
Use the following procedure.
1,2,3...
1. Select Network setting from the Setting Menu in the Main Window of the
CX-FLnet to display the Communication Setting Dialog Box.
2. Select Connects directly in the Network Area.
3. Click the Change settings Button to display Change PLC Dialog Box.
4. Set the PLC and network. To connect to another node on FL-net network,
click the Settings Button and set the FINS destination network address
and node address.
173
Section 11-2
Operating Procedures
5. Click the OK Button to close the dialog box.
6. Input the unit number (0 to 15) of the FL-net Unit to be connected in the
Communication Setting Dialog Box.
7. Click the Close Button to finish setting.
Connecting via the
Network
Select Connects via network to connect the computer and make settings for
each PLC (i.e., target PLC) with an FL-net Unit via the network by connecting
the CX-FLnet to a C-series or CV/CVM1-series PLC (called a gateway PLC).
Connect via network
Node 1
Node 2
Node 3
Example: Ethernet
CX-FLnet
Use the following procedure.
1,2,3...
174
1. Select Network setting from the Setting Menu in the Main Window of the
CX-FLnet to display the Communication Setting Dialog Box.
Section 11-2
Operating Procedures
2. Select Connects via network in the Network Area.
3. Click the Change settings Button to display the Change PLC Dialog Box.
Set the data for the PLC directly connected to the CX-FLnet network. (The
PLC name is “Gateway.”)
4. Set the PLC and network. To connect using Ethernet, select Ethernet in the
Network Type List, and click the Settings Button to set the IP address of
the destination node.
5. Click the OK Button to close the dialog box.
175
Section 11-2
Operating Procedures
6. The following dialog box will be displayed. Make the settings for the FL-net
node that will be connected.
7. Change the network to Gateway.
8. Click the Settings Button to set the FINS destination network address and
node address. The following figure shows the setting for an access node
with network address 3 and node address 3.
9. Click the OK Button to close the dialog box.
176
Section 11-2
Operating Procedures
10. Input the unit number (0 to 15) of FL-net Unit to be connected in the Communication Setting Dialog Box.
11. Click the Close Button to finish setting.
11-2-4 System Setting - CPU Bus Unit Setup Area
Any of several operating parameters can be selected depending on the system, but the explanation is provided here for simple operating conditions.
Item
FA Link mapping table method
(default: PLC build-in method)
Content
Selects the method (PLC build-in method or FA Link Unit build-in method) for storing
the FA Link mapping table.
Normally the default should be selected.
FA Link startup method
Selects the method (auto-participating or manual-participating) for starting the FA
Link.
(default: Auto-participating
method)
Normally the default should be selected.
Confirm message protocol
Selects the protocol (confirmed or unconfirmed) for when messages are used.
(default: Confirmed)
Select Confirmed for a network with OMRON FL-net Units only.
Select Unconfirmed for a network in which units from other manufacturers are connected.
Broadcast type
Selects the broadcast type (***.***.***.255 or C255.255.255.255).
(default: ***.***.***.255)
Normally the default should be selected.
IP address set method
Selects the IP address setting method (192.168.250 + Node No., Unit rear rotary SW,
(default: 192.168.250 + Node No.) Unit rear rotary SW + Node No., or Setup Area).
Normally the default should be selected.
When using the CS1W-FLN22 or CJ1W-FLN22, select either 192.168.250 + Node No
or Setup Area.
Sub-net mask
Sets the sub-net mask (user setting).
(default: 255.255.255.0)
Normally the default should be selected.
177
Section 11-2
Operating Procedures
Item
Content
IP address
(default: None)
No. of the other nodes in FA Link
(default: None)
Baud Rate Setting
(default: 10 Mbps (not variable))
Note
Sets the IP address (user setting).
The IP address does not need to be set except when the IP address set method is set
to Setup Area.
The number of remote nodes (user setting) in the FA Link configuration is displayed.
This parameter cannot be set.
Sets the baud rate for FL-net communications. To communicate at 100 Mbps, select
Auto. The baud rate will be determined by the auto-negotiation function of the connected hub.
1. To circulate a token among the nodes connected to the network, match the
uppermost three digits of the IP address, the sub-net mask, and the broadcast type to those of the other connected nodes.
2. If either Unit rear rotary SW + node No. or Unit rear rotary SW is set as the
IP address setting method for the CS1W-FLN22 or CJ1W-FLN22, a setting
error will occur (HER indicator will light). Set the IP address setting method
to either 192.168.250 + node No. (default) or Setup Area.
3. The baud rate setting is supported by the CS1W-FLN22 and CJ1W-FLN22
only. The setting cannot be made for the CS1W-FLN02 or CS1W-FLN12,
which always communicate at 10 Mbps.
4. Select Option - Switch display - Hex in the Main Window. It will be possible to display and input the IP address and sub-net mask in hexadecimal.
5. If the communications are set to connect via the network and storage in the
PLC is set to use the FA link allocation table storage method, the maximum
number of nodes that can be registered in other node areas is 50.
11-2-5 System Setting - Local Node Setup Area
The local node setup area can be set so that data from any PLC area can be
used as the send data from the local node.
178
Section 11-2
Operating Procedures
Item
Area 1 (Area 2) Memory Area
(default: Area 1 CIO, Area 2 DM)
Area 1 (Area 2) start word
(default: 0)
Area 1 (Area 2) size
(default: 0)
Area 1 (Area 2) Start address of
Common Memory
(default: 0)
Content
Sets the PLC area in which Cyclic Data Areas 1 and 2 for the local node are stored.
The following areas can be set: CIO, WR, HR, DM, and EM0 to EMC.
Sets the beginning word of the PLC area in which Cyclic Data Areas 1 and 2 for the
local node are stored.
Sets the size of the PLC area in which Cyclic Data Areas 1 and 2 for the local node
are stored. This setting also determines the size allocated to this node for Common
Memory.
Sets the beginning address of the Common Memory allocated to Area 1 (or Area 2).
Note Select Option - Switch display - Hex. It will be possible to display and input
words, sizes, and addresses in hexadecimal.
11-2-6 System Setting - Other Node Setup Area
The other node setup areas are be set so that Common Memory data for
remote nodes can be read to the local PLC areas.
The following functions can be used when setting the other node setup areas.
Item
Area 1 (Area 2) Memory Area
(default: Area 1 CIO, Area 2 DM)
Area 1 (Area 2) start word
(default: 0)
Mapping area table
Content
Sets the PLC area in which Cyclic Data Areas 1 and 2 for the remote nodes are
stored.
The following areas can be set: CIO, WR, HR, DM, and EM0 to EMC.
Sets the beginning word of the PLC area in which Cyclic Data Areas 1 and 2 for the
remote nodes are stored.
Sets the offset, size and mapped node numbers of the PLC area in which Cyclic Data
Areas 1 and 2 for the remote nodes are stored.
Menu
Edit - Clear all
Function
Clear all data in the FA link table.
179
Section 11-2
Operating Procedures
Menu
Edit - Copy row
Edit - Delete
Note
Function
Copy a single data row data and add as a new row.
Delete a single data row.
1. Do not assign the local node in the mapping area table.
2. Enter 0 in the Node No. Field and enter the size of the local node setup
area in the Size Field for the area corresponding to that for the local node.
3. If the settings are made for only Area 1 (or Area 2), set the offset and size
for the other area to 0.
4. Select Option - Switch display - Hex. It will be possible to display and input words, sizes, and addresses in hexadecimal.
5. The “offset” designation tells how much data to receive of the data sent
from a given node (i.e., which word to begin receiving from, and how many
words to receive). The number of words from the beginning of the sent data
until the beginning of the received data is called the “offset.” The offset
function can be used to receive only a portion of the data sent from a given
node to enable using the Data Link Memory Areas efficiently.
6. Select Option - Switch Settings - Hex from the Main Menu. It will be possible to display and input words, sizes, and addresses in hexadecimal.
11-2-7 System Setting - Extension Setting
The order of link data bytes can be specified for each node according to the
needs of the connected device, eliminating the need for upper/lower byte conversion (swapping) processing in the ladder program or user application.
Item
Local node setup
Order of send data
Other node setup
Order of send data
180
Content
Set the order for transferring data for local nodes. Select
sequential direction (same as the FLN02 and FLN12) or
reverse direction.
Set the order for transferring data for other nodes. Select
sequential direction (same as the FLN02 and FLN12) or
reverse direction.
Section 11-2
Operating Procedures
11-2-8 Unit Area Setup
The Unit's data display and node name can be set.
Menu
Allowed min. frame interval
(default: 1 (100 us))
Function
Sets the present minimum allowable frame interval. Valid must be selected to enable
this setting. If communications errors occur, increase the value of this setting. The
maximum allowable frame interval used for the entire network is that of the node with
the longest minimum allowable frame interval. The present valid value for the network can be checked by selecting Network status (FA Link) in the Monitor Field.
When a baud rate of 100 Mbps is used, set the minimum allowable frame interval to
1 ms or higher.
Sets the timeout time for monitoring token passing between nodes. For normal
usage, use the default value.
Token watchdog timer
(default: 50 ms)
Wait time of min. frame interval
(default: 0)
Adds the value set here to the minimum allowable frame interval set in (1). This value
is not used by the entire network. This value is only enabled for the corresponding
node.
Node name
Sets the node name. Valid must be selected to enable this setting.
Note Select Option - Switch display - Hex. It will be possible to display and input
in hexadecimal.
11-2-9 Monitor Status Display Function
The CX-FLnet enables monitoring of various network conditions and settings.
■
Selecting the Status Display Function
Select the status from among those displayed in the Status Menu in the Main
Menu.
181
Section 11-2
Operating Procedures
Note Each status is read from the FL-net Unit when the display function is started
from the menu.
Data Link Status
Shows the data link status of remote nodes participating in the FL-net network. The status shown here is the same as the connected node data which
is reflected in the CIO Area.
Lit (blue) nodes are participating in the data link.
Error Status
The FL-net Unit status is displayed. The status shown here is the same as the
Unit status which is stored in the CIO Area.
■
FA Link active
Lit when FA Link operation is normal.
■
Received message
Lit when a transparent message is received.
■
Power supplied
Lit when transceiver power supply is normal.
■
FA Link Area mapping error
Lit when FA Link Area mapping is incorrect. Recheck the settings.
■
Token watchdog timer set error
Lit when time for monitoring token in the network is incorrect. This error
occurs for reasons such as a faulty network configuration.
Clear the error by resetting the Unit.
■
IP address set error
Lit when IP address setting is incorrect. Recheck the setting.
182
Section 11-2
Operating Procedures
■
Internal transceiver error
Lit when an error occurs during a transceiver test. Clear the error by resetting
the Unit. If this is a recurring error, replace the Unit.
■
Transceiver error
Lit when an error occurs at the transceiver.
Clear the error by resetting the Unit.
If this is a recurring error, replace the Unit.
■
EEPROM error
Lit when an error occurs in the EEPROM.
An error may recur in a Unit if there is a faulty network configuration. Recheck
the settings.
If the error recurs after rechecking the settings, replace the Unit.
Communication Cycle
Time
The network status is shown.
■
Token hold node number
Displays the node number of the node where the token is held when the
Upload Button is clicked.
■
Allowed min. frame interval
Displays the minimum allowable frame interval for the network in which the
specified Unit is participating.
■
Refresh cycle time
Displays the allowable refresh cycle time for the specified Unit.
■
Measure time
Displays the current value, maximum value, and minimum value of the measured refresh cycle time for the specified Unit.
183
Section 11-2
Operating Procedures
Message Sequential
Status
The message sequential status is shown.
Error Log
The error log data is read from the FL-net Unit. Error log data in the FL-net
Unit is deleted when the Clear Button is clicked.
184
Section 11-2
Operating Procedures
Node Status
The status of remote nodes participating in the FL-net network is shown. Data
from unmapped remote nodes can also be displayed.
■
Node Number
Sets the node number of the node for which the status is to be read.
■
Local Node Status (only when local node is specified)
Shows the status of the local node when the node set by the node number is
the local node. In this case, the same data is displayed as for the network status.
Corresponding FL-net Standard Flag Names
CX-FLnet
Common memory setting range error
Duplicate node number notification
Token monitoring timeout error
Frame standby error
■
FL-net standard flag name
Initialization Error Flag
Duplicate Node Number Flag
Token Monitoring Timeout Flag
Reception Standby Flag
Node Status
Shows the participation status of the node.
■
FA Link Status
Shows the network status of the node set by the node number.
■
Upper Layer Status
Shows the upper layer status.
Status
RUN
STOP
Status
NORMAL
WARNING
ALARM
Meaning
CPU Unit is running (RUN/MONITOR mode).
CPU unit is stopped (PROGRAM mode).
Meaning
CPU Unit is normal.
Non-fatal error has occurred.
Fatal error has occurred
185
Section 11-2
Operating Procedures
ERR_CODE
0
1
Meaning
Normal
Service is stopped.
Note For information on FL-net node error codes in Units from other companies,
refer to the relevant manuals.
■
Allowed Refresh Cycle Time, Token Watchdog Timer, Allowed Minimum
Frame Interval
The allowed refresh cycle time, the token watchdog timer, and the allowed
minimum frame interval are displayed for the node set by the node number.
Network Status
The status of remote nodes participating in the FL-net network is shown. The
status shown here is the same as the network status which is stored in the
DM Area.
■
Mapping Error
Indicates that the settings do not correctly reflect the network data in the PLC
areas. Recheck the settings.
■
Participation in Network
Network participation status is stored.
The operating status and error status data is not valid if the node is not participating in the network. (The upper layer status when changing from participating to not participating is retained.)
■
Error (Upper Layer)
The error status (error/no error) of applications installed at the node is stored.
■
Run (Upper Layer)
The operating status (active/not active) of applications installed at the node is
stored.
Transferring and
Comparing System
Settings
186
The CPU Bus Unit setup can be transferred and compared between the computer running the CX-FLnet and the PLC (CPU Unit or FL-net Unit).
Section 11-2
Operating Procedures
Downloading FL-net Setup
from the Computer to the
PLC
1,2,3...
1. Select Setting - To PLC.
The following confirmation dialog box will be displayed.
2. Click the Yes Button. The transfer will begin and the following message will
be displayed if the transfer ends normally.
3. Click the OK Button.
Uploading the FL-net Unit
Setup from the PLC to the
Computer
1,2,3...
1. Select Setting - From PLC.
The following confirmation dialog box will be displayed.
187
Section 11-2
Operating Procedures
2. Click the Yes Button. The transfer will begin and the following message will
be displayed if the transfer ends normally.
3. Click the OK Button.
Comparing the FL-net
Setup on the Computer to
the Setup in the PLC
1,2,3...
1. Select Setting - Compare with PLC.
The results of comparison will be displayed.
When the Setup is the Same:
When There Are Differences
2. Click the OK Button. If there were differences, they will be displayed in a
list.
3. Click the Close Button.
188
Appendix A
System Configuration
Ethernet Overview
Ethernet is a LAN (Local Area Network) standard for communications between personal computers and printers, and defines the network, including the communications data format, cables, and connectors. The Ethernet
standard was formulated by the IEEE802.3 Working Group for Ethernet. At present, the Working Group has
formulated the 10Base-5, 10Base-2, and 10Base-T standards. Other standards, such as 1000Base-T, are also
currently being studied. The following diagram shows the progress of standardization by the IEEE802.3 Working Group.
ISO/IEC
approved
ISO/IEC 8802-3: 1996 (E) 5th edition Published 7/96
ANSI/IEEE Std. 802.3-1998
ANSI/IEEE
approved
• 10Base-T PICs
• MAU Mgmt.
• Rptr Mgmt.
• GDMO of LM
• FO & Sys. Cons.
• 120 Ohm annex
• 150 Ohm annex
Published 10/98
• CSMA/CD Overview
• MAC
• Repeater
• PLS/AUI
• MAUs (B5, B2, BT, BrB)
• Mgmt.
• 1Base-5 Specifications
• Maint. 2, 3 & 4
Clauses 1 through 20
• 100Base-T
• Full Duplex
• 100Base-T2
• Gigabit Ethernet
Clauses 21 through 42 • Maint. 5 (100Base-T)
1802.3 Document Set
IEEE Std. 1802.3
Conformance Test
• AUI Cable
IEEE Std. 1802.3d
Conformance Test
• 10Base-T
Network
Systems
Tutorial
Published
June 95
.3ac
Changes for
VLANs
.3
Policy and
Procedures
Approved
09/98
Approved
11/97
Liaison
802.1
Liaison
802.14
CATV
.3ab
1000Base-T
802.3 WG
in process
WG Conf
Ballot Closed
11/98
.3ad
Link
aggregation
PAR approval
06/98
Source: IEEE website (Nov. 1998)
189
Appendix A
System Configuration
10Base-5 Specifications
The 10Base-5 standard is an Ethernet connection method that uses thick coaxial cable (yellow cable) with a
width of approximately 10 mm. The “10” in 10Base-5 indicates a baud rate of 10 Mbps. “Base” indicates that a
baseband transmission method is used. The “5” indicates a transmission distance of 500 m for the trunk line.
Coaxial cable is connected to a transceiver, which is then connected to the personal computer or other devices
via transceiver cable (AUI cable).
10Base-5 Ethernet is not easy to lay due to the thick cables. Therefore, this method is hardly used in office networks. 10Base-5 is often used in trunk line networks, however, due to its long transmission distance.
The following diagram shows a 10Base-5 Ethernet configuration example.
Coaxial cable
(length: 500 m max.)
Terminating
resistance
Ground
terminal
Single-port
transceiver
AUI cable
(Length: 50 m max.)
Multiport transceiver
The maximum length of the
AUI cable from the coaxial cable
to the multiport transceiver
terminal is 50 m max.
Multiport transceivers support
cascade connections for up to
two segments.
10Base-T Specifications
The 10Base-T standard is an Ethernet connection method that uses twisted-pair cable. The “10” in 10Base-T
indicates a baud rate of 10 Mbps. “Base” indicates that a baseband transmission method is used. The suffix “T”
indicates that twisted-pair cables are used as the transmission media. Personal computers and other devices
in a 10Base-T network must be connected in a star connection via a hub. Direct connections between devices
are not supported. (Special cables called cross cables can be used for 1:1 direct connections, but such connections are not commonly used.) The cable length from the hub to each device is 100 m maximum.
10Base-T Ethernet uses thin cables, making it easy to lay the network. This method is often used in office networks because each device can be easily connected and removed from the network.
The following diagram shows a 10Base-T Ethernet configuration example.
Hub
Twisted-pair cable (UTP, Cat. 5)
(Length: 100 m max.)
RJ-45 connector
190
Appendix A
System Configuration
Other Ethernet Specifications
The 10Base-2 standard is an Ethernet connection method that uses 5-mm wide coaxial cables (also called thin
cables). The “10” in 10Base-2 indicates a baud rate of 10 Mbps. “Base” indicates that a baseband transmission
method is used. The “2” indicates a transmission distance of 185 m for the trunk line (approximately 200 m).
Personal computers and other Ethernet-compatible devices are connected to the 10Base-2 Ethernet by connecting a T-branch connector to the BNC connector of each device, with coaxial cable connected to the other
two connectors on the T-branch connectors.
The following diagram shows a 10Base-2 Ethernet configuration example.
Coaxial cable (RG58A/U)
(Length: 185 m max.)
Branch
connector
Terminating
resistance
Optical Ethernet
Optical Ethernet uses optical fiber cables as the transmission media. Optical Ethernet is used in systems that
require a transmission distance of 500 m or more or that require resistance to noise. Optical Ethernet connection methods standardized by IEEE802.3 include 10Base-FP, 10Base-FB, 10Base-FL, 100Base-FX,
1000Base-LX, and 1000Base-SX.
The following diagram shows an Optical Ethernet configuration example.
10Base-5 system
Optical transceiver
Optical-fiber cable
(Length: 2 km max.)
Optical repeater
Wireless Ethernet
Wireless Ethernet is a wireless LAN that uses electromagnetic waves and infrared rays as the transmission
media. This method is used to connect portable devices to the LAN. Standardization of wireless LAN is being
pursued by the IEEE wireless LAN Working Group IEEE802.11. The MAC layer protocol for a wireless LAN is
different from Ethernet. A bridge is therefore needed to interconnect the two types of networks.
The following diagram shows a wireless Ethernet configuration example.
10Base-5 system
2.4 GHz
Wireless adapter
Wireless bridge
191
System Configuration
192
Appendix A
Appendix B
System Configuration Example
Small-scale Configuration
A network system of multiple devices can be configured using a single multiport transceiver or hub.
Multiport transceiver
Transceiver cable
(AUI cable)
(Length: 50 m max.)
(a) Using a Multiport Transceiver
Hub
Twisted-pair cable
(UTP, Category 5)
(Length: 100 m max.)
(b) Using a Hub
193
Appendix B
System Configuration Example
Basic Configuration
A network system consisting of several tens of devices can be configured by connecting several multiport
transceivers or hubs to a single coaxial cable.
Coaxial cable (Length: 500 m max.)
Single-port transceiver
Transceiver cable
(AUI cable)
(Length: 50 m max.)
Hub
Twisted-pair cable
(UTP, Category 5)
(Length: 100 m max.)
Up to a total of four repeaters and hubs can
be installed between any two terminals.
194
Ground
terminal
Terminating
resistance
Multiport transceiver
The length of the AUI cable from the
coaxial cable to the multiport transceiver
terminal is 50 m max. Multiport
transceivers support cascade
connections for up to two segments.
Appendix B
System Configuration Example
Large-scale Configuration
A large-scale network system consisting of hundreds of devices can be configured by connecting several
10Base-5 network segments together using repeaters.
Coaxial cable (Length: 500 m max.)
Transceiver cable (AUI cable)
(Length: 50 m max.)
Multiport
transceiver
Repeater
The length of the AUI cable
from the coaxial cable to the
multiport transceiver terminal is
50 m max. Multiport
transceivers support cascade
connections for up totwo
segments. A total of four
repeaters and hubs can be used
between any two terminals.
195
Appendix B
System Configuration Example
Long-distance Distributed Configuration
In large-scale network systems requiring a distance between network segments that exceeds the maximum
10Base-5 transmission distance of 500 m, optical repeaters can be connected to each network segment to
enable a network configuration with 2 km between repeaters.
Coaxial cable (Length: 500 m max.)
Transceiver cable (AUI cable)
(Length: 50 m max.)
Optical repeater
Optical-fiber cable
(Length: 2 km max.)
The length of the AUI cable from
the coaxial cable to the multiport
transceiver terminal is 50 m max.
Multiport transceivers support
cascade connections for up to
two segments. A total of four
repeaters and hubs can be used
between any two terminals.
196
Multiport
transceiver
Appendix B
System Configuration Example
Local Centralized (Stack) Configuration
A network system can be configured using several tens of devices centralized using stackable hubs.
Hub
Stackable hubs
Twisted-pair cable
(UTP, Category 5)
(Length: 100 m max.)
Local Configurations with Long-distance Distributed Segments
Basic network with a specific controller in a remote location, or a network that is near high-voltage power lines
or a source of noise interference can be split into two segments, with optical repeaters connected between
segments. This configuration enables a long-distance network with superior noise resistance.
Optical-fiber cable (Length: 2 km max.)
Optical
repeater
Coaxial cable
(Length: 500 m max.)
Optical
repeater
Hub
Twisted-pair cable (UTP, Cat. 5)
(Length: 100 m max.)
Transceiver cable
(AUI cable)
(Length: 50 m max.)
197
System Configuration Example
198
Appendix B
Appendix C
Network System Definitions
Communications Protocol Standard
The communications protocol indicates the rules for exchanging information through the communications lines
between two systems. The communications protocol used by FL-net conforms to the following standards.
FL-net
communications
protocol
FL-net
UDP
IP, ICMP, etc.
ARP etc.
Ethernet
Standards
FA link protocol specification
(MSTC FA Open Systems Promotion Forum
FA Control Network Technical Committee)
RFC768
RFC791, 792, 919, 922, 950
RFC826,894
IEEE802.3
Communications Protocol Layer Configuration
The communications protocol is modeled in a layers, and is expressed and standardized using a layer configuration, in which communications processing is divided into several layers. FL-net consists of six protocol layers,
as shown in the following diagram.
Application layer
FA link protocol layer
Controller interface
Cyclic transmission
Message service
Message transmission
Token functionality
Transport layer
UDP
Network layer
IP
Data link layer
Physical layer
FL-net protocol
Ethernet
(IEEE802.3 standard)
FL-net Physical Layer
When a baud rate of 10 Mbps is used, five transmission methods can be used in the Ethernet’s physical layer,
including 10Base-5, 10Base-2, 10Base-T, 10Base-F, and 10Broad-36 (although not commonly used). There is
also 100 Mbps Ethernet. Of these transmission methods, FL-net uses 10Base-5 (recommended), 10Base-2,
and 10Base-T.
199
Appendix C
Network System Definitions
FL-net IP Address
IP addresses (INET addresses) are used to distinguish each communications device from multiple communications devices connected to the Ethernet. Therefore, a unique IP address must be set for each communications device connected to the Ethernet. An IP address is comprised of a network address indicating the
network to which the communications device is connected, and the host address for the communications
device. The networks are classified as class A, B, or C, depending on the network size (classes D and E are
also supported for other specific purposes).
First octet
Class
Network address
Host address
A
0 to 127
xxx.xxx.xxx.xxx
Xxx.xxx.xxx.xxx
B
C
128 to 191
xxx.xxx.xxx.xxx
Xxx.xxx.xxx.xxx
192 to 223
xxx.xxx.xxx.xxx
Xxx.xxx.xxx.xxx
Note The parts shown in gray indicate the section of the IP address corresponding to the network and node
addresses.
The IP addresses for communications devices connected to the same network will all have the same network
address; each device will have a unique host address. The default FL-net IP address is 192.168.250.N (N:
Node number between 1 and 254). It is recommended to use class C address, with the host address in the
lower byte matching the FL-net protocol node number.
23
22
22
22
0
9
8
7
1
0
X
28 27
Network address
20
Host address
Fixed
FL-net Subnet Mask
The FL-net subnet mask is always 255.255.255.0. Set the subnet mask to 255.255.255.0 in the FL-net Unit
Setup (CPU Bus Unit Setup Area) using the FL-net Unit Support Software. This format is the same as that for
the network address and host address used in class C.
TCP/IP and UDP/IP Communications Protocol
The main protocols used by Ethernet are TCP, UDP, and IP. IP is located in the network layer of the communications protocol, and controls the flow of communications data. TCP and UDP are located in the transport layer
and both use IP as the network layer, but the service provided is significantly different. TCP provides a reliable
delivery service that does not recognize delineation in the data for the upper layer. UDP, however, functions by
transferring data packets from IP (datagrams) to the upper layer without modification, and without confirming
whether the data has reached the destination. Data processing, such as reception confirmation and resending,
is performed in the upper layer. UDP does not have the reliability of TCP, but can deliver communications services with small overhead.
FL-net uses UDP because TCP’s elaborate data confirmation and resending procedures are redundant in an
FL-net system. High-speed data exchange is enabled by replacing these procedures with procedures for controlling the right to transmit using tokens and performing multiple frame division/synthesis in the upper FL-net
protocol layer.
200
Appendix C
Network System Definitions
FL-net Port Numbers
With FL-net, the following port numbers are assigned in advance to enable services in the FL-net protocol
layer, which is located above the transport layer. FL-net users, however, do not need to set these port numbers
in parameters or elsewhere.
No.
1
2
3
4
Name
Cyclic transmission port number
Message communications port number
Participation request frame port number
Send port number
Port No.
55000 (fixed)
55001 (fixed)
55002 (fixed)
55003 (fixed)
FL-net Data Format
FL-net Data Format Overview
The data sent and received using FL-net is encapsulated using the following communications protocol layers,
as follows:
1,024 bytes max.
User data
FL-net header
UDP header
User data
FL-net data
UDP segment
IP header
UDP header
FL-net data
IP datagram
Ethernet header
14
IP header
20
UDP header
FL-net data
Trailer
8
Ethernet frame
201
Appendix C
Network System Definitions
The FL-net data for a single frame that can be monitored on the communications line is shown in the following
diagram. In this example, 128 bytes of cyclic data is being transferred.
ADDR
Ethernet header
IP header
UDP header
FL-net header
HEX
ASCII
0000
FF FF FF FF FF FF 08 00
19 10 00 07 08 00 45 00
..............E.
0010
00 E4 EB 59 00 00 80 11
D8 52 C0 A8 FA 0B C0 A8
...Y.....R.......
0020
FA FF D6 DB D6 D8 00 D0
00 00 46 41 43 4E 00 00
..........FACN..
0030
00 C8 00 01 00 0B 00 02
00 01 00 07 07 00 00 00
................
0040
00 00 01 00 00 00 80 00
00 00 00 00 00 00 0A 00
................
0050
00 00 FD E8 00 00 00 28
00 04 02 80 00 40 00 00
.......([email protected]
0060
80 00 01 01 00 C8 61 32
00 02 5B 91 00 00 00 00
......a2..[.....
0070
00 00 5B 91 00 00 00 00
00 00 00 00 00 00 00 00
..[.............
0080
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
................
0090
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
.................
00A0
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
................
00B0
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
................
00C0
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
................
00D0
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
................
00E0
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
................
00F0
00 00
..
User data
FL-net Header Format
The FL-net header consists of between 64 and 96 bytes.
1,024 bytes max.
64 to 96 bytes
FL-net header
Lower layer header
Cyclic/message data
FA link data
1,500 bytes max.
The FL-net header is added at the beginning of all frames in the FL-net protocol.
202
Appendix C
Network System Definitions
FL-net Transaction Codes
FL-net supports the following message transmission services.
FL-net message transmission service
1
2
3
4
5
6
7
8
9
10
11
12
Read byte block
Write byte block
Read word block
Write word block
Read network parameter
Write network parameter
Stop command
Run command
Read profile
Read communications log data
Clear communications log data
Echoback message
Unit support
Client function Server function
No
No
No
No
Yes
Yes
Yes
Yes
No
Yes
No
No
No
No
No
No
No
Yes
No
Yes
No
Yes
Yes (See note.) Yes
13
14
Send transparent message frame
Vendor message
Yes
Yes
Yes
Yes
Note This message service is provided as an internode test.
The header of each message contains a request transaction code or a response transaction code that distinguishes the type of message frame used.
Transaction code
0 to 9999
Corresponding message
Reserved
10000 to 59999
60000 to 64999
65000
65001
65002
65003
65004
65005
65006
65007
65008
65009
65010
65011
65012
Transparent messages
Reserved
Token header
Cyclic header
Participation request frame header
Read byte block (request)
Write byte block (request)
Read word block (request)
Write word block (request)
Read network parameter (request)
Write network parameter (request)
Stop command (request)
Run command (request)
Read profile (request)
Trigger header
65013
65014
65015
65016
65017 to 65202
65203
65204
65205
65206
65207
Read communications log data (request)
Clear communications log data (request)
Echoback message test (request)
Vendor message (request)
Reserved (for future expansion)
Read byte block (response)
Write byte block (response)
Read word block (response)
Write word block (response)
Read network parameter (response)
203
Network System Definitions
Transaction code
65208
65209
65210
65211
65212
65213
65214
65215
65216
65217 to 65399
65400 to 65535
204
Corresponding message
Write network parameter (response)
Stop command (response)
Run command (response)
Read profile (response)
Reserved
Read communications log data (response)
Clear communications log data (response)
Echoback message test (response)
Vendor message (response)
Reserved (for future expansion)
Reserved
Appendix C
Appendix D
FL-net Network Control
FL-net Token Control
Tokens
Basically, a node can send data when it is holding the token. The only two types of data that can be sent by a
node that is not holding the token are a request to resend the token when a token monitoring timeout occurs
and a participation request frame for a node that is not participating in the network.
1. FL-net networks pass a single token between nodes.
2. After each node receives the token, it maintains the right to transmit in the network until the token is passed
to the next node.
3. The token is passed to all nodes participating in FL-net.
4. The token can be sent together with cyclic data.
5. The token can also be passed alone without attached data.
6. The token is monitored by a timer and automatically resent if it is not passed through the network within a
fixed period of time.
7. If two or more tokens are present in the network at the same time, they will be reduced to a single token.
Token Flow
Generally, only a single token is present in a network at any one time. If two or more tokens are present in the
network, the token at the node with the smallest destination node number is given priority, and the other tokens
are discarded. The token frame is the frame that includes the token and consists of the token's destination
node number and source node number. Each node becomes the token holding node when its node number
matches the token destination node number in the received token frame. The token rotation order is determined by the node numbers. The token is passed to all nodes registered in the participating node management
table in ascending order. The node with the largest node number in the network passes the token to the node
with the smallest node number in the network.
Token passed to next token.
Node 2
Node 3
Node N−1
Token passed to node with lowest
node number.
Node 1
Node N
205
Appendix D
FL-net Network Control
Token and Data Transmission Patterns
The following six types of transmission patterns can be used to send data with a token.
No.
1
Pattern
No accompanying data
Details
Sending token only
Token
2
Cyclic data only
Cyclic data
3
Cyclic data is sent, after which the token is sent.
Token
Cyclic data only, which is split into different packets
and then sent
Cyclic data
4
Message data is sent, after which the token is sent.
Token
Cyclic data and message data
Message data
6
Token
Message data only
Message data
5
Cyclic data
Message data and cyclic data is sent, after which the
token is sent.
Cyclic data
Token
Cyclic data and message data, of which the cyclic
data is split into different packets and then sent
Message data
Cyclic data is split into several packets and sent,
after which the token is sent.
Cyclic data
Message data is sent, after which the cyclic data is
split into several packets and sent, followed by the
token.
Cyclic data
Token
Frame Intervals (Minimum Allowable Frame Interval)
The frame interval is the time required until the local node sends a frame after receiving a token from another
node. The minimum allowable frame interval is the least time that a node must wait until it can send a frame.
FL-net uses the same minimum allowable frame interval for the entire network. Whenever a node joins or is
removed from the network, each node updates the minimum allowable frame interval by calculating the maximum value for the minimum allowable frame interval set by the nodes participating in the network.
Joining and Leaving the FL-net
Joining FL-net
When a node is started, it monitors the communications line until the entry token detection timer times out. If a
token is not received during this time, the node assumes the network has just been started and the node joins
the network as a node in a new network. If a token is received, the node assumes that the network is active and
the node joins the active network.
206
Appendix D
FL-net Network Control
Participating in a New Network
If a token is not received within the entry token detection time, a trigger transmission is prepared and a trigger
is sent after dividing the node number by 8 and multiplying the remainder by 4 ms. If another trigger is received
before the trigger is sent, the trigger will not be sent. From the time the trigger is received and for the duration
of the participation request frame receive wait time (1,200 ms), the node number and address are checked for
duplication, the participating node management table is updated, and participation request frames from all
nodes are waited. The participation request frame is sent after the participation request frame send wait time
(node number × 4 ms) times out after receiving the trigger. At this time, the beginning addresses of the Common Memories allocated for Area 1 and Area 2 and the Common Memory sizes are set to 0 and cyclic data is
not sent by nodes for which the participation request frames from other nodes show address duplication. The
Duplicate Common Memory Address Flag is turned ON for nodes confirmed to have duplicated addresses,
and the Common Memory Data Validity Notification Flag is turned OFF. When the participation request frame
receive wait time has lapsed, a token is sent first by the node with the smallest node number according to the
node management table. Nodes confirmed to have duplicate node numbers will not send or receive tokens or
data.
Trigger
Node 1
Node monitor starts
(when clearing reset after turning ON power)
Participation
request frame
Token
Entry token detection time (3 s)
Node 2
Node 3
Node 254
Participation request frame
send wait time (node number × 4 ms)
Participation request frame
receive wait time (1 or 2 s)
Joining an Active Network
When a token is received within the entry token detection time, the node assume links have been established
and waits for a participation request frame to be sent until the token has been passed three times around the
network. During that time, the node number and address are checked for duplication using the received
frames, and the participating node management table is updated. At this time, if a duplicate address is
detected, the beginning addresses of Common Memory Area 1 and Area 2, and the Common Memory size are
set to 0, and cyclic data is not sent. The Duplicate Common Memory Address Flag will turn ON for nodes that
are detected to have duplicate addresses, and the Common Memory Data Validity Notification Flag for the corresponding nodes will be turned OFF. If no node address error occurs, the participation request frame is sent
after the participation request frame send wait time lapses. The participation request frame is sent regardless
of whether the node is holding the token. The participation request frame will not be sent by nodes detected to
have duplicate node numbers and these nodes will not join the network.
Note The entry token detection time is the time required to check whether the network is active. A standard
cycle is based on the time taken for the token to be received at the node with the smallest node number.
The participation request frame send wait time is the time before a participation request frame can be
sent, so that the frame sent by the newly participating node does not collide with a frame being sent by
another node (local node number × 4 ms).
207
Appendix D
FL-net Network Control
Token detection
stopped
3 to 4
4 to 5
First cycle
N to 1
1 to 2
Second cycle
N to 1
1 to 2
Third cycle
N to 1
1 to 2
N to 1
Entry token detection time
Node monitor starts
(reset after power turned ON)
Participation request frame send wait time
(Local node number × 4 ms)
Participation request
frame sent
N to 1
Leaving the FL-net
The node number of each node is checked when the token frame is received, and nodes that do not receive the
token frame for three successive passes of the token are removed from the network (including a token-holding
node that does not send the token after the token monitoring time has timed out). When a node is determined
to have been removed from the network, the node information is deleted from the management table.
Managing Node Status
Node status is managed using three types of management tables: Local node management tables, participating node management tables, and network management tables. A summary of these tables is provided below.
Table
Local node management table
Participating node management table
Network management table
Details
Manages the local node settings.
Manages information on the nodes in the network.
Manages information that is shared by all nodes on the network.
FL-net Local Node Management Table
Basic Functions
The data for setting local nodes is managed using the local node management table, as shown in the following
table.
1. Local node management tables are used to read participation request frames and network parameters.
2. Management data is set from the FL-net upper layer when the node is started.
3. The node name and beginning address and size of the send area in Common Memory can be set from the
CX-FLnet or FL-net Unit Support Software connected to the PLC.
Management Data
Item
Node number
Common Memory Area 1 first word
Common Memory Area 1 data size
Common Memory Area 2 first word
Common Memory Area 2 data size
Upper layer status
Token monitoring time
208
Bytes
1 byte
2 bytes
2 bytes
2 bytes
2 bytes
2 bytes
1 byte
Contents (data range)
1 to 254
Word address (0 to 0x1ff)
Size (0 to 0x200)
Word address (0 to 0x1fff)
Size (0 to 0x2000) (See note.)
RUN/STOP/ALARM/WARNING/NORMAL
Unit: 1 ms
Appendix D
FL-net Network Control
Item
Minimum allowable frame interval
Vendor code
Manufacturer model
Node name (equipment name)
Protocol version
FA link status
Local node status
Bytes
1 byte
10 bytes
10 bytes
10 bytes
1 byte
1 byte
1 byte
Contents (data range)
Unit: 100 µs
Vendor code
Manufacturer model, device name
User-defined node name
0x80 (fixed)
Participating, not participating, etc.
Duplicate node number detection, etc.
Note For details on FL-net Unit restrictions, refer to Precautions under 3-1 Before Operation.
Participating Node Management Table
Basic Functions
The status of the nodes in the network is monitored using the participating node management table maintained
by each node. Management data is managed for each node that has joined the network. A summary of the
functions is provided below.
1. When a node is started, a token frame is received, and the participating node management table and network management table are updated.
2. For each token frame received, the node’s participating node management table is updated.
3. When a participation request frame is received for a new node, the participating node management table is
updated.
4. A node will be deleted from the table if the node does not receive a token frame or has consecutively timed
out three times.
Management Data
The token for each node is constantly monitored and the participating node management table is created and
managed, as shown in the following table.
Item
Node number
Upper layer status
Common Memory Area 1 data first word
Common Memory Area 1 data size
Common Memory Area 2 data first word
Common Memory Area 2 data size
Minimum allowable refresh cycle time
Token monitoring time
Minimum allowable frame interval
Link status
Note
Bytes
1 byte
2 bytes
2 bytes
2 bytes
2 bytes
2 bytes
2 bytes
1 byte
1 byte
1 byte
Contents (data range)
1 to 254
RUN/STOP /ALARM/WARNING/NORMAL
Word address (0 to 0x1ff)
Size (0 to 0x1ff)
Word address (0 to 0x1fff)
Size (0 to 0x1fff)
Unit: 1 ms
Unit: 1 ms
Unit: 100 µs
Participating, not participating, etc.
(1) “0x1fff” refers to hexadecimal 1FFF.
(2) This information is included in the received token frame.
209
Appendix D
FL-net Network Control
Network Management Tables
Basic Functions
Parameters that are shared by all nodes on the network are managed.
Management Data
Item
Token holding node number
Bytes
1 byte
Contents (data range)
Node currently holding the token
Minimum allowable frame interval
1 byte
Unit: 100 µs
Allowable refresh cycle time
Refresh cycle measurement value (current)
Refresh cycle measurement value (maximum)
Refresh cycle measurement value (minimum)
2 bytes
2 bytes
2 bytes
2 bytes
Unit: 1 ms
Unit: 1 ms
Unit: 1 ms
Unit: 1 ms
Message Sequence Management
Basic Functions
The sequence number and sequence version number in message transmissions are managed.
Send Management Data
Item
Sequence version number
Sequence number (1:N send)
Sequence number (1:1 send)
Bytes
4 bytes
4 bytes
4 bytes ×
256
Contents (data range)
Send message transmission sequential version
0x1 to 0xffffffff
0x1 to 0xffffffff
Note “0xffffffff” indicates FFFFFFFF hexadecimal.
Receive Management Data
Item
Sequence version number
Sequence number (1:N receive)
Sequence number (1:1 receive)
Bytes
4 bytes
4 bytes
4 bytes
Note “0xffffffff” indicates FFFFFFFF hexadecimal.
210
Contents (data range)
0x1 to 0xffffffff
0x1 to 0xffffffff
0x1 to 0xffffffff
Appendix E
FL-net Profile
Device Communications Information Classification
The parameters and other information related to communications for devices connected to the network are
classified into three types, as follows:
Node
(communications
function)
Device, equipment
A: Network parameters
(Setting data for transmission)
(Specified in the FA link protocol specifications.)
B: System parameters
1) Common parameters
2) Device parameters
C: Device communications I/O information
1. Network parameters (A) are parameters required for transmission.
2. System parameters (B) are static parameters used as management data for distinguishing what type of device is connected to the network.
3. Device communications I/O information (C) can be accessed from other devices on the network when required by an application. This information includes dynamic data that changes according to the application
operation and device status.
Data Types Supported for System Parameters
The following table lists the data types that can be used for system parameters in the UNIVERSAL TAG.
Tag number
(hexadecimal)
00
01
02
03
04
05
06
07
08
Type
Supported (See note 1.)
(Reserved.)
BOOLEAN
INTEGER
BIT STRING
OCTET STRING
NULL
OBJECT IDENTIFIER
ObjectDescriptor
EXTERNAL
No
Yes
Yes
Yes
Yes
Yes
No
No
No
09
0A
0B to 0F
10
11
12
13
14
15
16
17
18
REAL
ENUMERATED
(Reserved.)
SEQUENCE and SEQUENCE OF
SET and SET OF
NumericString
PrintableString
TeletexString
VideotexString
IA5String
UTCTime
GeneralizedTime
No
No
No
Yes
No
No
Yes
No
No
No
No
No
Remarks
(See note 2.)
211
Appendix E
FL-net Profile
Tag number
(hexadecimal)
19
1A
1B
1C
1D to 1E
Type
Supported (See note 1.)
GraphicString
VisibleString
GeneralString
CharacterString
(Reserved.)
Remarks
No
No
No
No
No
Note For the construction type only SEQUENCE and SEQUENCE OF can be used.
System Parameters
Message Transmission Service
The following services are used to access the system parameters.
TCD
65011
Service name
Read profile (request)
65211
Read profile (response)
Function
Request to batch read system parameters (not supported by this Unit).
Response to batch read of system parameters.
Response data size is 1,024 bytes max.
Parameter Structure
The system parameters are configured of the following data in the order given in the table.
Parameter name
Common parameters
Device parameters
Details
Parameters common to all devices.
Vendor-specified parameters for each device (optional)
Common Parameters
The following parameters are mandatory.
Parameter name
Name text
(PrintableString type)
Length, Text
Data type
Device profile common specifications
version
System parameter
ID
System parameter
revision number
System parameter
revision date
6,”COMVER”
INTEGER
Parameter contents
Length_in_decimal, Contents
(Boxes indicate spaces.)
1,1
2,”ID”
PrintableString
7,”SYSPARA”
3,”REV”
INTEGER
1,0
7,”REVDATE”
Device type
Vendor name
Device model name
10,”DVCATEGORY”
6,”VENDOR”
7,”DVMODEL”
[INTEGER],2,(0001-9999),
[INTEGER],1,(01-12),
[INTEGER],1,(01-31)
PrintableString
PrintableString
PrintableString
2,1999
1,06
1,30
3,”PLC” (See note.)
9,”[email protected]”
21,”[email protected]@[email protected]” or
21,”[email protected]@[email protected]”
Note The parameter contents for device types are classified as follows:
“PC” or “PLC”: Programmable Controller
“NC” or “CNC”: Computerized numeric controllers
“RC” or “ROBOT”: Robot controllers
“COMPUTER”: Personal computers, panel computers, workstations, display devices, and other computers.
“SP-* *”: Vendor specific
“OTHER”: Other
212
Appendix E
FL-net Profile
The transfer syntax uses SEQUENCE structures for all system parameters, all common parameters, the system parameter revision data, and all device parameters (any data structure can be used within device parameters).
Device Parameters
Parameter name
Name text
(PrintableString type)
Length, Text
Data type
Device parameter ID
Device type
2,”ID”
7,”DEVTYPE”
PrintableString
PrintableString
Unit revision code
7,”UNITREV”
PrintableString
PCB revision code
6,”PCBREV”
PrintableString
Software revision code
7,”SOFTREV”
PrintableString
Lot number
5,”LOTNO”
PrintableString
Work area
8,”WORKAREA”
PrintableString
Serial number
8,”SERIALNO”
PrintableString
Parameter contents
Length_in_decimal, Contents
(Boxes indicate spaces.)
7,”DEVPARA”
10,”CS1W-FLN22” or
10,”CJ1W-FLN22
1, *
(same value as unit profile)
3, ***
(same value as unit profile)
2, **
(same value as unit profile)
6, ******
(same value as unit profile)
1, 10
(same value as unit profile)
1, ****
(same value as unit profile)
Abstract Syntax
Type Definition
PlcmRecord::=
SysparaType::=
PlcmType::=
SEQUENCE
{
syspara
SysparaType,
plcmpara
PlcmType
}
SEQUENCE
{
nameCOMVER
NameType,
paraCOMVER
INTEGER,
nameID
NameType,
paraID
NameType,
nameREV
NameType,
paraREV
INTEGER,
nameREVDATE
NameType,
paraREVDATE
DateType,
nameDVCATEGORY
NameType,
paraDVCATEGORY
NameType,
nameVENDOR
NameType,
paraVENDOR
NameType,
nameDVMODEL
NameType,
paraDVMODEL
NameType
}
SEQUENCE
{
nameID
NameType,
paraID
NameType,
parameter
SEQUENCE OF ParaInfo
DEFAULT{}z
213
Appendix E
FL-net Profile
}
PrintableString
SEQUENCE
year
month
day
}
SEQUENCE
{
namePARAMETER
paraPARAMETER
}
NameType::=
DateType::=
ParaInfo::=
INTEGER,
INTEGER,
INTEGER
NameType,
NameType
Value Definitions
{
syspara
{
nameCOMVER
paraCOMVER
nameID
paraID
nameREV
paraREV
nameREVDATE
paraREVDATE
nameDVCATEGORY
paraDVCATEGORY
nameVENDOR
paraVENDOR
nameDVMODEL
paraDVMODEL
plcmpara
}
{
nameID
paraID
parameter
{
namePARAMETER
paraPARAMETER
namePARAMETER
paraPARAMETER
namePARAMETER
paraPARAMETER
namePARAMETER
paraPARAMETER
namePARAMETER
paraPARAMETER
namePARAMETER
paraPARAMETER
namePARAMETER
paraPARAMETER
}
}
}
214
ìCOMVERî,
1,
ìIDî,
ìSYSPARAî,
ìREVî,
0,
ìREVDATEî,
{
year
1999,
month
6,day
30
},
ìDVCATEGORYî,
ìPLCî,
ìVENDORî,
ì[email protected]î,
ìDVMODELî,
ì[email protected]@[email protected]î,
(CJ Series: ì[email protected]@[email protected]î)
ìIDî,
ìDEVPARAî,
ìDEVTYPEî
ìCS1W-FLN22î,
(CJ Series: ìCJ1W-FLN22î)
ìUNITREVî,
ì1î,
ìPCBREVî,
ì***î, (variable)
ìSOFTREVî,
ì**î, (variable)
ìLOTNOî,
ì******î, (variable)
ìWORKAREAî,
ì*î, (variable)
ìSERIALNOî,
ì****î, (variable)
Appendix E
FL-net Profile
Transfer Syntax Data Array (Signed)
$30
$81
$30
$79
$13
$06
“COMVER”
$02
$01
1
$13
$02
“ID”
$13
$07
“SYSPARA”
$13
$03
“REV”
$02
$01
0
$07
“REVDATE”
$13
$30
$30
$F2
$0A
$02
$02
$02
$01
$07CF
$06
$02
$01
$1E
$13
$0A
“DVCATEGORY”
$13
$03
“PLC”
$13
$06
“VENDOR”]
$13
$09
“[email protected]”
$13
$07
“DVMODEL”
$13
$15
“[email protected]@[email protected]"
(CJ Series: "[email protected]@[email protected]")
$81
$74
$13
$02
“ID”
$13
$07
“DEVPARA”
$13
$07
“DEVTYPE”
$13
$0A
"CS1W-FLN22" (CJ Series: "CJ1W-FLN22")
$13
$07
“UNITREV”
$13
$01
1
$13
$06
“PCBREV”
$13
$03
*** (variable)
$13
$07
“SOFTREV”
$13
$02
*(variable)
$13
$05
“LOTNO”
$13
$06
****** (variable)
$13
$08
“WORKAREA”
$13
$01
* (variable)
$13
$08
“SERIALNO”
$13
$04
**** (variable)
215
Appendix E
FL-net Profile
Communications Line Data Sequence
The following table shows the sequence used to send data on the communications line. Data is sent from the
data starting from address 0 in the relative address 00 column in sequence moving left or right. Relative
address 00 is followed by relative address 10, and data is sent in the order of relative addresses as shown
below.
Data: Hexadecimal (Example)
Relative
address
00
10
20
30
40
50
60
70
80
90
A0
B0
C0
D0
E0
F0
0
1
2
3
4
5
6
7
8
9
A
B
C
D
E
F
30
13
“E”
02
“T”
“D”
“D”
“n”
74
“D”
“N”
06
“F”
13
“E”
04
81
02
“V”
02
“E”
“O”
“V”
“e”
13
“E”
“0”
“P”
“T”
06
“A”
“*”
F2
“I”
02
07
“G”
“R”
“M”
“t”
02
“V”
“2”
“C”
“R”
“*”
13
“*”
30
“D”
01
CF
“O”
13
“O”
““
“I”
“T”
13
“B”
“E”
“*”
01
“*”
79
13
00
02
“R”
09
“D”
“U”
“D”
“Y”
07
“R”
“V”
“*”
“*”
“*”
13
07
13
01
“Y”
“O”
“E”
“N”
13
“P”
“U”
“E”
13
“*”
13
06
“S”
07
06
13
“M”
“L”
“i”
07
“E”
“N”
“V”
02
“*”
08
“C”
“Y”
“R”
02
03
“R”
13
“t”
“D”
13
“I”
13
“*”
“*”
“S”
“0”
“S”
“E”
01
“P”
“O”
15
““
“E”
0A
“T”
03
“*”
13
“E”
“M”
“P”
“V”
1E
“L”
“N”
“C”
“V”
“V”
“C”
“R”
“*”
13
08
“R”
“V”
“A”
“D”
13
“C”
““
“S”
“1”
“P”
“S”
“E”
“*”
05
“W”
“I”
“E”
“R”
“A”
0A
13
“C”
“1”
“.”
“A”
“1”
“V”
“*”
“L”
“O”
“A”
“R”
“A”
“T”
“D”
06
“o”
““
“0”
“R”
“W”
13
13
“0”
“R”
“L”
02
13
“E”
“V”
“V”
“.”
“F”
“0”
“A”
“-”
01
07
“T”
“K”
“N”
01
03
30
“C”
“E”
13
“L”
30
13
“F”
“*”
“S”
“N”
“A”
“O”
01
“R”
0A
“A”
“N”
07
“-”
81
07
“L”
13
“0”
“0”
“R”
13
Device Communications I/O Data
Device Communications I/O Data Resources
These resources are specific for each device called from the register data memory. The program area is also
included in one of the resources, but the programs here are strictly indicating areas for storing programs and
do not indicate programs that can be accessed as a block.
Area name
DM
TIM
CNT
EM0
EM1
EM2
EM3
EM4
EM5
EM6
EM7
EM8
EM9
EMa
EMb
EMc
CIO
WR
216
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
R/W
0x0002
0x0009
0x000A
0x0020
0x0021
0x0022
0x0023
0x0024
0x0025
0x0026
0x0027
0x0028
0x0029
0x002A
0x002B
0x002C
0x0030
0x0031
First word
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
to
to
to
to
to
to
to
to
to
to
to
to
to
to
to
to
to
to
0x0002
0x0009
0x000A
0x0020
0x0021
0x0022
0x0023
0x0024
0x0025
0x0026
0x0027
0x0028
0x0029
0x002A
0x002B
0x002C
0x0030
0x0031
End word
7FFF
0FFF
0FFF
7FFF
7FFF
7FFF
7FFF
7FFF
7FFF
7FFF
7FFF
7FFF
7FFF
7FFF
7FFF
7FFF
17FF
01FF
Size
32768
4095
4095
32768
32768
32768
32768
32768
32768
32768
32768
32768
32768
32768
32768
32768
6144
512
Appendix E
FL-net Profile
Area name
HR
AR
AR
Note
R/W
R/W
R
W
0x0032
0x0033
0x0033
First word
0000
0000
01C0
to
to
to
0x0032
0x0033
0x0033
End word
01FF
03BF
03BF
Size
512
960
512
(1) Access unit: WORD
(2) Data sequence: A word corresponds to one word in a word block
MSB
LSB
Status/Mode
The data clarifying status/mode is shown below.
Item
Status type
Details
Normal
Error (operation continues)
Error (operation stops)
Status access method
Read: PARTICIPATING NODE STATUS READ (FINS 06 03)
Mode type
The operating mode can be selected from the following combinations
FA link table storage method: PLC internal method (default)/Unit internal method
FA link start method: Automatic addition (default)/manual addition
Broadcast format: Class C broadcast (default)/fixed
IP address specification method: 192.168.250 + node number (default)/Setup area
Mode information access Read: CPU UNIT DATA READ (FINS 05 01)
method
Write: Set from the Support Software
Relation to ULS in FA link Operation in progress: RUN
header
Operation stopped: STOP
Normal operation: NORMAL
Error (operation continues): WARNING
Error (operation stopped): ALARM
Supported Message Services
The following table shows which message services are supported.
Message service
Read byte block
Write byte block
Read word block
Write word block
Read network parameter
Write network parameter
Stop command
Client
Server
No
No
Yes
Yes
No
No
No
No
No
Yes
Yes
Yes
No
No
Run command
Read profile
Send transparent message frame
Read communications log data
Clear communications log data
Echoback message
Vendor message
No
No
Yes
No
No
Yes (See note.)
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
Note This message service is provided as an internode test.
217
Appendix E
FL-net Profile
Supplementary Profile Information
Summary of ASN.1 Transfer Syntax Format
A summary of the basic encoding rules for ISO/IEC 8825 ASN.1 (Abstract Syntax Notation One) relevant to FLnet are provided below.
Simple Format: ASN.1
Type
Value
Length
Structure Type Example with Signed ASN.1
Value
Type
Length
Length
Type
Value
Type
Length
Value
Type Field
• Structure (Single Octet)
Structured type flag: 0 = Primitive type
1 = Constructed type
C
C
F
8
7
6
Tag class
Tag number
5
4
3
2
1
00 UNIVERSAL TAG
01 APPLICATION TAG
10 CONTEXT-SPECIFIC TAG
11 PRIVATE TAG
• Tag Number (UNIVERSAL TAG)
Tag number
(hexadecimal)
00
01
02
03
04
05
06
07
08
09
0A
0B to 0F
10
218
Type
Tag number
(hexadecimal
(Reserved.)
11
BOOLEAN
12
INTEGER
13
BIT STRING
14
OCTET STRING
15
NULL
16
OBJECT IDENTIFIER
17
ObjectDescriptor
18
EXTERNAL
19
REAL
1A
ENUMERATED
1B
(Reserved.)
1C
SEQUENCE and SEQUENCE OF 1D to 1E
Type
SET and SET OF
NumericString
PrintableString
TeletexString
VideotexString
IA5String
UTCTime
GeneralizedTime
GraphicString
VisibleString
GeneralString
CharacterString
(Reserved.)
Appendix E
FL-net Profile
• Structure Type Flag for Each Data Type
ASN.1
BOOLEAN, INTEGER, OBJECT IDENTIFIER, REAL, ENUMERATED
BIT STRING
OCTET STRING, NumericString or other character string
NULL (no value field)
SEQUENCE, SEQUENCE OF, SET, SET OF
EXTERNAL
CHOICE
ANY
With tag
Primitive
Supported
Supported
Supported
Supported
----Supported
Supported
Supported
Constructed
--Supported
Supported
--Supported
Supported
Supported
Supported
Supported
• Printable Strings
Name
Capital letters
Small letters
Digits
Space
Apostrophe
Left Parenthesis
Right Parenthesis
Plus sign
Comma
Hyphen
Full stop
Solidus
Colon
Equal sign
Question mark
Text
Code (hexadecimal)
41, 42, ..., 5A
61, 62, ..., 7A
30, 31, ..., 39
20
27
28
29
2B
2C
2D
2E
2F
3A
3D
3F
A, B, ..., Z
a, b, ..., z
0, 1, ..., 9
(space)
‘
(
)
+
,
.
/
:
=
?
Length Field
• Fixed-length Short Format
8
L
L
L
L
L
L
L
7
6
5
4
3
2
1
Length: 1 to 127
• Fixed-length Long Format
N
N
N
N
N
N
N
L
Number of octets indicating length: 1 to 126
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
Length
• Data Send Sequence
The data send sequence is in big endian format for sending the first octet of data.
• Profile Resources
• OKANE, Hisao TCP/IP to OSI nettowaku kanri [TCP/IP and OSI Network Management], 1993, Soft
Research Center
219
Appendix E
FL-net Profile
• ISO/IEC 8824 Information technology - Open Systems Interconnection - Specification of Abstract Syntax
Notation One (ASN.1), 1990 Second edition, (ISO/IEC 8824-1 1995, ISO/IEC 8824-2 1995, ISO/IEC
8824-3 1995, ISO/IEC 8824-4 1995)
• ISO/IEC 8825 Information technology - Open Systems Interconnection - Specification of Basic Encoding
Rules for Abstract Syntax Notation One (ASN.1), 1990 Second edition, (ISO/IEC 8825-1 1995, ISO/IEC
8825-2 1996)
Data Read by Log Data Read Service
The following table shows which data can be read by the log data read service.
Item
Total number of socket sends
Total number of socket send errors
Total number of Ethernet send errors
Total number of receives
Total number of receive errors
Total number of Ethernet receive errors
Frame type
Number of token sends
Number of cyclic frame sends
Number of 1:1 message sends
Number of 1:N message sends
Number of token receives
Number of cyclic frame receives
Number of 1:1 message receives
Number of 1:N message receives
Cyclic transmissions Number of cyclic send/receive errors
Number of cyclic address size errors
Number of cyclic CBN errors
Number of cyclic TBN errors
Number of cyclic BSIZE errors
Message transmisNumber of message resends
sions
Number of message resend overflows
Number of message send/receive errors
Number of message send sequence version errors
Number of message sequence resend validations
ACK related
Number of ACK errors
Number of ACK sequence version errors
Number of ACK sequence number errors
Number of ACK node number errors
Number of ACK TCD errors
Token related
Number of token multiplexing errors
Number of token discards
Number of token resends
Number of token holding timeouts
Number of token monitoring timeouts
Status 1
Total operating time
Number of frame waits
Number of participations
Number of self-removals
Number of skip removals
Number of other node removals
Status 2
List of participating nodes
Implementer-defined (Undefined)
area
Send/receive
220
Supported
Yes
Yes
No
Yes
Yes
No
No
No
No
No
No
No
No
No
Yes
No
No
No
No
Yes
Yes
Yes
No
No
Yes
No
No
No
No
Yes
Yes
Yes
No
No
No
Yes
Yes
Yes
Yes
Yes
No
---
Remarks
Appendix F
FL-net Unit Support Software Ver. 1.6
FL-net Unit Support Software Overview
The FL-net Unit Support Software is used to make settings for OMRON FL-net Units mounted to Programmable Controllers (PLCs). The FL-net Unit Support Software is installed on a computer running Windows 7 (32-bit
or 64-bit edition), Vista (32-bit or 64-bit edition), or XP (32-bit edition). This computer is connected to a PLC to
which an FL-net Unit is mounted.
FL-net (Ethernet-based control network)
PLC
PLC
PLC
Panel
computer
CNC
RC
Computers with
FL-net Support
Software installed.
Note
(1) The FL-net Unit Support Software is designed especially for OMRON FL-net Units.
(2) For information on node settings for FL-net devices from other companies, contact the particular
companies.
(3) The Window operating system is not provided with the Support Software and must be purchased
separately.
Operating Environment
Item
Operating systems
Hard disk
Floppy disk drives
Display
Other CPU and memory
requirements
Note
Conditions
Microsoft Windows 7 (32-bit or 64-bit edition)
Microsoft Windows Vista (32-bit or 64-bit edition)
Microsoft Windows XP (32-bit edition)
1 Mbyte or more of free space
1 or more
Resolution: 1,024 x 768 pixels min.
Must meet at least the recommended standards for the
operating system.
(1) Make sure the user has Administrator authority when installing the FL-net Unit Support Software in
a computer running Windows.
(2) Use the FL-net Unit Support Software Ver. 1.60 or later to set the CS1W-FLN22 and CJ1W-FLN22.
Earlier versions of the FL-net Unit Support Software cannot be used to make the following settings.
• Setting baud rate
• Switching upper/lower byte order of data link data
(3) If the FL-net Unit Support Software Ver. 1.51 or earlier is used to set the CS1W-FLN22 or CJ1WFLN22, the baud rate will be fixed at 10 Mbps and the data link data upper/lower byte order will be
set to sequential order (the same settings as for CS1W-FLN02 and CS1W-FLN12).
221
FL-net Unit Support Software Ver. 1.6
Appendix F
Functions
Name
File Initialize
File Open
Save to file (Japanese)
Save to file (English)
Communications settings
System setting
(CPU Bus Unit setup area)
System setting (Local node setup)
System setting (Other node setup)
Unit area setting
Monitor (Unit status)
Monitor (Network status)
Monitor (Node status)
Monitor (Data link status)
Monitor (Participating node status)
Monitor (Message sequential status)
Monitor (FA Link network status)
Option (Network setting)
Option (Extension setting)
222
Function
Returns system and communications settings to their defaults.
Reads saved setup data. (CSV format only.)
Saves edited setup data in CSV format.
Saves edited setup data in CSV format.
Use this setting to read data from an English version of the FL-net Unit Support
Software.
Makes communications settings for connecting the computer to the PLC, and the
settings for Unit designation.
Sets the basic FL-net Unit data stored in the CPU Bus Unit Setup Area.
Makes settings related to cyclic data for the FL-net Unit at the local node.
Makes settings related to cyclic data for the FL-net Units at remote nodes.
Makes settings related to the settings and information in the Unit Area for the FLnet Unit.
Shows the Unit status.
Shows the network status.
Shows the node status.
Shows the data link status.
Shows the participating node status.
Shows the message sequential status.
Shows the FA Link network status.
Sets the communications settings when setting FL-net Unit settings of other
nodes via the FL-net network.
Sets the order of data link data.
Appendix F
FL-net Unit Support Software Ver. 1.6
Operating Procedure
Install the FL-net Unit Support Software (Refer to 11-2 Installation.)
Make communications settings.
↓Unit settings
↓Monitoring
System settings
Select monitor function.
Make settings in CPU Bus Unit Setup Area.
↓
↓
System settings
Click Start Button.
Make local node settings.
↓
↓
System settings
Display monitor screens.
Make other node settings.
↓
↓
Unit Area settings
Check display contents.
When required.
↓
Transfer settings.
↓
Turn PLC power ON or restart the FL-net Unit.
↓
Begin FL-net Unit operation.
↓
Confirm that operation is normal, and then save
the settings.
↓
Exit the FL-net Unit Support Software.
Note
↓
Close monitor screens.
↓
Exit FL-net Unit Support Software.
(1) The new settings go into effect when the PLC's power is turned ON again or when the FL-net Unit
is restarted.
(2) Confirm that the communications settings are correct for the environment in which they are to be
used.
223
FL-net Unit Support Software Ver. 1.6
Appendix F
Installation
This section explains how to install the software for setting the FL-net Unit's operating parameters.
Installation Procedure
The procedure for installing the FL-net Unit Support Software is given below. Use the special-purpose Support
Software Installer to install the software.
Note
(1) Make sure the user has Administrator authority when installing the FL-net Unit Support Software in
a computer running Windows.
(2) Operations and screen displays will vary slightly according to the Windows system which is used.
(3) The FL-net Unit Support Software uses the following four setup files:
1) SETUP.EXE
2) SETUP.LST
3) FL_NET1.CAB
4) FL_NET2.CAB
When setting up from a floppy disk, store files 1 to 3 on one disk (Setup Disk 1) and file 4 on a second disk (Setup Disk 2). When setting up from a hard disk, compact flash memory, or other memory
storage location, store files 1 to 4 in a user-specified folder.
1. Close all applications that are running.
2. Insert the Support Software's Setup Disk 1 into the drive. This operation is not required when copying setup
files from a memory storage location such as a hard disk.
3. Click the Start Button, and select Run.
4. As shown in the following diagram, specify \Setup.exe at the drive where the disk is set, and then click the
OK Button. \Setup.exe can be selected at the appropriate drive by clicking the Browse Button.
5. Depending on the Windows system being used, some of the system files may be modified for the setup, and
it may be necessary to restart Windows.
If the following message is displayed, click the OK Button. If it is not displayed, proceed to Step 7.
6. Click the Yes Button. After the computer has been restarted, the setup will be started when setup.exe is
again executed.
224
FL-net Unit Support Software Ver. 1.6
Appendix F
7. The installation will be started, and the Installer will begin preparations. When the next disk is required, a
message will be displayed requesting that Setup Disk 2 be inserted into the drive.
8. The following window will be displayed. Click the OK Button.
9. Specify the directory where the Support Software software is to be installed.
If the directory displayed is correct, then click the Icon Button.
To install the software in another directory, click the Change Directory Button and specify the storage location. Then click the Icon Button. If a directory that does not exist is specified, it will be automatically created.
10. The software will be installed. When the installation is finished, the following window will be displayed. Click
the OK Button to complete the setup.
11. This completes the software installation.
225
Appendix F
FL-net Unit Support Software Ver. 1.6
Connecting the Computer to the PLC
This section explains how to connect to the PLC the computer in which the FL-net Unit Support Software is
installed. The cables used depend on the type of connection to the PLC. When connecting the computer to the
PLC, refer to the connection examples provided in this section.
Communications Settings
The following table provides the settings for the communications port used for the FL-net Unit Support Software (i.e., the set values used during operation).
Communications protocol
Baud rate
Communications method
Frame configuration
Transfer code
Response method
Xon/Xoff
RS/CS control
Note
Specifications
Tool bus
9600, 19,200, or 38,400 bps
Start-stop synchronization, bit serial transfer
Data: 8 bits, 1 stop, no parity
Binary
Full duplex
No
Yes
Remarks
--Default: 9,600
-------------
(1) The FL-net Unit Support Software cannot be connected online at the same time as CX-Programmer
or CX-Net. The following error message will be displayed if online connection is attempted when either of these applications is online.
(2) The above specifications are automatically set and used internally by the FL-net Unit Support Software when it connects through the serial port of the computer.
(3) By setting the CS/CJ CPU Unit's DIP switch to “Auto-detect Programming Device,” the connection
can be made easily and with no need to pay attention to the details of the above communications
settings. For details, refer to the CS Series Programmable Controllers Operation Manual (W339) or
CJ Series Programmable Controllers Operation Manual (W393).
(4) These settings do not depend on the serial port settings in the operating system, and there is no
need to change the Windows settings.
(5) If the communications settings are all set manually, the settings must be made in the PLC Setup.
For details, refer to the CS Series Programmable Controllers Operation Manual (W339) or CJ Series
Programmable Controllers Operation Manual (W393)
226
Appendix F
FL-net Unit Support Software Ver. 1.6
Examples: Connecting the Computer and PLC
Computer
Connecting Cable
CQM1-CIF01
←RS-232C
PLC
CS/CJ
Peripheral port→
Auto-detect Programming Device
connection enabled by setting DIP
switch pin No. 4 to OFF.
RS-232C Cable
CQM1-CIF01
←RS-232C
RS-232C port→
CS/CJ
Auto-detect Programming Device
connection enabled by setting DIP
switch pin No. 5 to ON.
• If the RS-232C connector at the computer is a half-pitch 14-pin connector, use a D-Sub 25-pin to Half-pitch
Conversion Cable (XW2Z-S001).
• RS-232C cable can be connected only for models with a built-in RS-232C port or when a Host Link Unit is
mounted.
• If the RS-232C port at the PLC is D-Sub 9-pin connector, use a XW2Z-200S cable.
• If the RS-232C port at the PLC is D-Sub 25-pin connector, use a XW2Z-200P cable.
• For details on PLC DIP switch settings, refer to the CS Series PLC Operation Manual.
Connecting to the PLC Via the FL-net Network
Use either of the following two setting methods from the FL-net Unit Support Software Ver. 1.60.
Directly Connecting to PLC to which an FL-net Unit Is Mounted
Node 1
FL-net Unit
Unit number 0
Node 2
Node 3
Connect the computer to each PLC separately
to make the settings for each node.
Specify the FL-net Unit’s unit number in the Unit No. field under Communication settings in the Main Window of
the FL-net Unit Support Software.
227
Appendix F
FL-net Unit Support Software Ver. 1.6
Connecting Via the FL-net Network
Node 1
FL-net Unit
Unit number 0
Node 2
Node 3
FL-net Unit
Unit number 3
FL-net Unit
Unit number 5
Make the settings via the FL-net network.
Select Network setting from the Option Menu in the Main Window of the FL-net Unit Support Software, and
specify the remote PLC’s network address and node address. Specify the unit number for the FL-net Unit in the
Unit No. field under Communication settings.
1. Select Network setting from the Option Menu in the Main Window of the FL-net Unit Support Software to
display the Destination Network Setting Dialog Box.
2. Select the destination node in the Destination Node Address field (1 in this example) and click the OK Button.
3. Specify the unit number for the FL-net Unit (0 in this example) in the Unit No. field under Communication
settings in the Main Window of the FL-net Unit Support Software. The specified destination address will be
displayed in the status bar.
The unit number of the remote FL-net Unit must be specified when connecting via the FL-net network. In this
configuration example, after specifying the destination node address in the Destination Node Setting Dialog
Box, node 2 is set to unit number 3, and node 3 is set to unit number 5.
228
FL-net Unit Support Software Ver. 1.6
Appendix F
• Specifying Node 2 (FL-net Unit number 3)
• Specifying Node 3 (FL-net Unit number 5)
Note
(1) Connection via the FL-net network is only supported for FL-net Unit Support Software Ver. 1.60 or
later (FL-net Unit Support Software Ver. 1.51 or earlier cannot be used.)
(2) The unit number of the remote node’s FL-net Unit must be specified when connecting via the FL-net
network.
(3) The FL-net Unit Support Software cannot be used at the same time (i.e., communicate online) as
CX-Programmer, CX-Net, or other Support Software.
Using Support Software Functions
Basic Operations
Starting
1. Click the Start Button.
2. Display the menu by moving the cursor from Program to OMRON.
3. Select FL-net Unit Support Software to start the program. The following screen will be displayed.
Main Screen
229
Appendix F
FL-net Unit Support Software Ver. 1.6
Initializing
1. Select Initialize from the File Menu.
2. The system and communications settings will be initialized to their default values.
Opening
1. Select File Open from the File Menu.
2. When any file is selected, the previously-set contents of that file can be read.
Saving
1. Select Save to file from the File Menu.
2. The contents of a file can be saved by specifying the filename.
Exiting
1. Select Exit from the File Menu.
2. The FL-net Unit Support Software will be exited.
Communications Settings
(1)
(2)
(3)
(4)
(1) CPU Bus Unit Number (Default: 0)
Specify the unit number (0 to F).
Use the same setting as the number set on the rotary switch on the front panel of the FL-net Unit.
(2) Transmission Wait Timer (Default: 3,000 ms)
Specify the period of time to wait for the response to be returned (1 to 65,535 ms). If the value is too small,
communications may not be possible.
The baud rate must be taken into account, but there is normally no need to change this setting.
(3) Serial Port Number (Default: 1)
Specify the number of the serial port number to be used at the computer (for cable connection).
(4) Baud Rate (Default: 9,600 bps)
Specify the baud rate (9,600, 19,200, or 38,400 bps) for connecting to the PLC. Match the baud rate that is
set for the PLC port.
When the PLC communications port setting is for “Auto-detect Programming Device,” the connection can be
made at any of the baud rate settings. The PLC automatically detects the baud rate and makes the connection.
230
Appendix F
FL-net Unit Support Software Ver. 1.6
System Setting - CPU Bus Unit Setup Area
Any of several different operating parameters can be selected depending on the system, but the explanation is
provided here in terms of simple operating conditions.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
(13)
(14)
(1) FA Link mapping table method (Default: PLC built-in method)
Selects the method (PLC built-in method or FA Link Unit built-in method) for storing the FA Link mapping
table.
Normally the default should be selected.
(2) FA Link startup method (Default: Auto-participating method)
Selects the method (auto-participating or manual-participating) for starting the FA Link.
Normally the default should be selected.
(3) Confirm message protocol (Default: Confirmed)
Selects the protocol (confirmed or unconfirmed) for when messages are used.
Select “Confirmed” for a network with OMRON FL-net Units only.
Select “Unconfirmed” for a network in which units from other manufacturers are connected.
(4) Broadcast type (Default: ***.***.***.255)
Selects the broadcast type (***.***.***.255, C255.255.255.255).
Normally the default should be selected.
(5) IP address set method (Default: 192.168.250 + Node No.)
Selects the IP address setting method (192.168.250 + Node No., Unit rear rotary SW, Unit rear rotary SW +
Node No., or Setup area).
Normally the default should be selected.
When using CS1W-FLN22 or CJ1W-FLN22, select either 192.168.250 + Node No or Setup area.
231
FL-net Unit Support Software Ver. 1.6
Appendix F
(6) Sub-net mask (Default: 255.255.255.0)
Sets the sub-net mask (user setting).
Normally the default should be selected.
(7) IP address (Default: None)
Sets the IP address (user setting).
The IP address does not need to be set except when the IP address set method is Setup area.
(8) No. of the other nodes in FA Link (Default: None)
The number of remote nodes (user setting) in the FA Link configuration is displayed.
This cannot be set.
(9) Baud Rate Setting (Default: 10 Mbps (not variable))
Sets the baud rate for FL-net communications. To communicate at 100 Mbps, select Auto. The baud rate is
determined by the auto-negotiation function of the connected hub.
(10) Show data
Selects whether data is to be given in decimal or hexadecimal.
(11) Send
Writes to the System Setup Area of the specified Unit.
(12) Receive
Reads the contents of the System Setup Area of the specified Unit to the FL-net Unit Support Software.
(13) OK
Validates the changed settings and closes the window.
When the System Setup Window is next opened, the changed settings will be displayed.
(14) Cancel
Cancels the changes to the settings and closes the window.
When the System Setup Window is next opened, the settings prior to the changes will be displayed.
Note
(1) In order to circulate a token among nodes connected to the network, match the uppermost three
digits of the IP address, the sub-net mask, and the broadcast type to those of the other connected
nodes.
(2) If either Unit rear rotary SW + node No. or Unit rear rotary SW is set as the IP address setting method for a CS1W-FLN22 or CJ1W-FLN22, a setting error will occur (HER indicator will light). Set the
IP address setting method to either 192.168.250 + node No. (default) or Setup area.
(3) The baud rate setting is supported by CS1W-FLN22 and CJ1W-FLN22 only. The setting cannot be
made for CS1W-FLN02 or CS1W-FLN12, which always communicate at 10 Mbps.
232
Appendix F
FL-net Unit Support Software Ver. 1.6
Before System Settings: Data Link Concepts
Before making the system settings in the Local and Other Node Setup Areas, it is necessary to clearly understand the data link concept.
Example
On the example on the following pages, the local node shown below is 10.
Common Memory Area 1
~
50
~
System Setup Area 1
PLC Area
DM
100
Node: 10
Send data
Node: 10
Write data
Node: 10
Write data
250
Node: 11
Send data
280
Node: 23
Send data
Node: 11
Read data
Not required.
Offset
Node: 23
Read data
Node: 11
Read data
Node: 123
Read data
Node: 123
Send data
Offset
Node: 123
Read data
Node: 6
Send data
Not required.
Node: 6
Read data
340
400
~
440
500
~
530
Not used.
~
Node: 108
Send data
~
300
320
Node: 6
Read data
360
Node: 23
Read data
400
Node: 108
Read data
440
Not required.
Offset
Node: 108
Read data
233
Appendix F
FL-net Unit Support Software Ver. 1.6
System Setting (Local Node Setup Area)
The Local Node Setup Area can be set so that data from any PLC area can be used as the send data from the
local node
(2)
(1)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(1) Area 1 (Area 2) Memory Area (Default: DM)
Sets the PLC area in which Cyclic Data Areas 1 and 2 for the local node are stored.
The following areas can be set: CIO, WR, HR, DM, and EM0 to EMC.
(2) Area 1 (Area 2) start word (Default: 0)
Sets the beginning word of the PLC area in which Cyclic Data Areas 1 and 2 for the local node are stored.
(3) Area 1 (Area 2) size (Default: 0)
Sets the size of the PLC area in which Cyclic Data Areas 1 and 2 for the local node are stored. This setting
also determines the size allocated to this node in Common Memory.
(4) Area 1 (Area 2) Start address of Common Memory (Default: 0)
Sets the beginning address of the Common Memory allocated to Area 1 (or Area 2).
(5) Show data
Selects whether data is to be given in decimal or hexadecimal.
(6) Send
Writes set data to the System Setup Area of the specified Unit.
(7) Receive
Reads the contents of the System Setup Area of the specified Unit to the FL-net Unit Support Software.
(8) OK
Validates the changed settings and closes the window.
When the System Setup Window is next opened, the changed settings will be displayed.
(9) Cancel
Cancels the changes to the settings and closes the window.
When the System Setup Window is next opened, the settings prior to the changes will be displayed.
234
Appendix F
FL-net Unit Support Software Ver. 1.6
System Setting (Other Node Setup Area)
The Other Node Setup Area are be set so that Common Memory data for remote nodes can be read to the
local PLC areas.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(1) Area 1 (Area 2) Memory Area (Default: DM)
Sets the PLC area in which Cyclic Data Areas 1 and 2 for the remote nodes are stored.
The following areas can be set: CIO, WR, HR, DM, and EM0 to EMC.
(2) Area 1 (Area 2) start word (Default: 0)
Sets the beginning word of the PLC area in which Cyclic Data Areas 1 and 2 for the remote nodes are
stored.
(3) Mapping area table
Sets the offset, size and mapped node numbers of the PLC area in which Cyclic Data Areas 1 and 2 for the
remote nodes are stored. (See note 1.)
(4) Clear all
Clears all entries in the mapped area table.
(5) Copy row
Copies the contents of the row in which the cursor is placed, and adds it as a new row.
(6) Delete
Deletes the contents of the row in which the cursor is placed. Any settings after the deleted row are moved
forward in the table.
(7) Show data
Selects whether data is to be displayed in decimal or hexadecimal.
(8) Send
Writes set data to the System Setup Area of the specified Unit.
(9) Receive
Reads the contents of the System Setup Area of the specified Unit to the FL-net Unit Support Software.
235
FL-net Unit Support Software Ver. 1.6
Appendix F
(10) OK
Validates the changed settings and closes the window.
When the System Setup Window is next opened, the changed settings will be displayed.
(11) Cancel
Cancels the changes to the settings and closes the window.
When the System Setup Window is next opened, the settings prior to the changes will be displayed.
Note
(1) Do not assign the local node to the mapping area table.
(2) Enter 0 in the Node No. field and enter the size of the local node setup area in the Size field for the
area corresponding to that for the local node.
(3) If the settings are made for only Area 1 (or Area 2), set the offset and size for the other area to 0.
(4) The “offset” designation is the designation of how much data to receive of the data sent from a given
node (i.e., which word to begin receiving from, and how many words to receive). The number of
words from the beginning of the sent data until the beginning of the received data is called the “offset.” The offset function can be used to receive only a portion of the data sent from a given node to
enable using the Data Link Memory Areas efficiently.
Unit Area Setup
Sets the Unit's data display and node name.
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(1) Allowed min. frame interval (default: 1 (100 µs))
Sets the present minimum allowable frame interval. Valid must be selected to enable this setting. If communications errors occur, increase the value of this setting. The maximum allowable frame interval used for the
entire network is that of the node with the longest minimum allowable frame interval. The present valid value
for the network can be checked by selecting Network status (FA Link) in the Monitor field. When a baud
rate of 100 Mbps is used, set the minimum allowable frame interval to 1 ms or higher.
(2) Token watchdog timer (default: 50 ms)
Sets the timeout time for monitoring token passing between nodes. For normal usage, use the default value.
(3) Wait time of min. frame interval (default: 0)
Adds the value set here to the minimum allowable frame interval set in (1). This value is not used by the
entire network. This value is only enabled for the corresponding node.
(4) Node name
Sets the node name. Valid must be selected to enable this setting.
(5) Send
Writes set data to the Unit Area Setup Area of the specified Unit.
236
FL-net Unit Support Software Ver. 1.6
Appendix F
(6) Receive
Reads the contents of the Unit Area Setup Area of the specified Unit to the FL-net Unit Support Software.
(7) OK
Validates the changed settings and closes the window.
When the Unit Area Setup Window is next opened, the changed settings will be displayed.
(8) Cancel
Cancels the changes to the settings and closes the window.
When the Unit Area Setup Window is next opened, the settings prior to the changes will be displayed.
Monitoring Function
The FL-net Unit Support Software can be used to monitor conditions such as the network status, settings, etc.
Several types of status can be displayed simultaneously, providing an accurate picture of network status.
Selecting the Monitoring Function
Select the data to be monitored, and then click the Start Button.
Note The monitoring function periodically reads data from the FL-net Unit or the PLC, so they may have an
effect on data link operations and message communications.
Use the monitoring function only when required. In particular, be careful about simultaneously displaying
several types of status, because this can have an especially noticeable effect on operations.
While executing the monitoring function, do not disconnect the communications cable between the computer and the PLC, or turn OFF the power to the computer or the PLC.
237
FL-net Unit Support Software Ver. 1.6
Monitor (Unit Status)
Shows the status of the FL-net Unit.
The status shown here is the same as the Unit status which is reflected in the CIO Area.
FA Link active
Lit when FA Link operation is normal.
Received message
Lit when a transparent message is received.
Power supplied
Lit when transceiver power supply is normal.
FA Link Area mapping error
Lit when FA Link Area mapping is incorrect. Recheck the settings.
Token watchdog timer set error
Lit when time for monitoring token in network is incorrect.
This error occurs for reasons such as faulty network configuration.
Restore by resetting the Unit.
IP address set error
Lit when IP address setting is incorrect. Recheck the setting.
Internal transceiver error
Lit when an error occurs during a transceiver test. Restore by resetting the Unit.
If this is a recurring error, replace the Unit.
Transceiver error
Lit when an error occurs at the transceiver.
Restore by resetting the Unit.
If this is a recurring error, replace the Unit.
EEPROM error
Lit when an error occurs at the EEPROM.
There are cases in which an error recurs in a Unit in a faulty network configuration.
Recheck the settings.
If the error recurs after rechecking the settings, replace the Unit.
238
Appendix F
FL-net Unit Support Software Ver. 1.6
Appendix F
Monitor (Network Status)
Shows the network status of the FL-net Unit.
The status shown here is the same as the network status which is reflected in the CIO Area.
Multiple node number
Lit when a node number is used more than once. Recheck the Unit and the settings.
Upper layer operation signal error
Lit when an error occurs between the Unit and the PLC. Reset the Unit.
Common Memory enabled
Lit when Common Memory data is enabled.
Lit after Unit restart if the settings are normal.
Common Memory set
Lit when Common Memory settings are completed.
Lit after Unit restart if the settings are normal.
Multiple addresses
Lit when a local node Common Memory address is used more than once. Recheck the Unit and the settings.
239
FL-net Unit Support Software Ver. 1.6
Appendix F
Monitor (Node Status)
Shows the status of remote nodes participating in the FL-net network.
The status shown here is the same as the network status which is reflected in the DM Area.
Mapping error
Notifies that the settings do not correctly reflect the network data in the PLC areas. Recheck the settings.
Participation in network
Network participation status is stored.
The operating status and error status data when not participating is invalid.
(The upper layer status when changing from participating to not participating is retained.)
Error (Upper Layer)
The error status (Error/No error) of applications installed at the node is stored.
Run (Upper Layer)
The operating status (Active/Not active) of applications installed at the node is stored.
240
FL-net Unit Support Software Ver. 1.6
Appendix F
Monitor (Data Link Status)
Shows the data link status of remote nodes participating in the FL-net network.
The status shown here is the same as the connected node data which is reflected in the CIO Area.
Monitor (Participating Node Status)
Shows the status of remote nodes participating in the FL-net network. Data from unmapped remote nodes can
also be displayed.
Node number
Sets the node number of the node for which the status is to be read.
241
FL-net Unit Support Software Ver. 1.6
Appendix F
Local node status (only when local node is specified)
Shows the status of the local node when the node set by the node number is the local node. In this case, the
same data is displayed as for the network status.
Corresponding FL-net Standard Flag Names
FL-net Unit Support Software
Common Memory setting range error
Duplicate node number notification
Token monitoring timeout error
Frame standby error
FL-net standard flag name
Initialization Error Flag
Duplicate Node Number Flag
Token Monitoring Timeout Flag
Reception Standby Flag
Node status
Shows the participation status of the node.
FA Link status
Shows the network status of the node set by the node number.
Upper layer status
Shows the upper layer status.
ERR_CODE
0
1
Meaning
Normal
CPU Unit servicing stopped.
Note For information on FL-net node error codes in systems by other companies, refer to the relevant manuals.
Allowed refresh cycle time, token watchdog timer, allowed min. frame interval
Displays the allowed refresh cycle time, the token watchdog timer, and the allowed minimum frame interval for
the node set by the node number.
Monitor (Message Sequential Status)
Shows the message sequential status.
242
FL-net Unit Support Software Ver. 1.6
Appendix F
Monitor (FA Link Network Status)
Shows the network status.
Token hold node number
Displays the node number of the node where the token is held when the Upload Button is clicked.
Allowed min. frame interval
Displays the minimum allowable frame interval for the network in which the specified Unit is participating.
Refresh cycle time
Displays the allowable refresh cycle time for the specified Unit.
Measure time
Displays the current value, maximum value, and minimum value of the measured refresh cycle time for the
specified Unit.
Version Information
The FL-net Unit Support Software version number can be displayed by selecting Help from the menu, and then
selecting About OMRON FL-net Unit Support Software.
Check the version number when making inquiries about the Support Software.
243
FL-net Unit Support Software Ver. 1.6
244
Appendix F
Appendix G
International System of Units
The International System of Units (SI) consists of base units, supplementary units, and derived units. SI is
founded on the seven base units, which have been used historically and technically, and are used to define the
other quantities. The base units include the meter (m) to express length, kilogram (kg) to express mass, second (s) to express time, Ampere (A) to express current, Kelvin (K) to express thermodynamic temperature,
mole (mol) for expressing amount of substance, and the candela (cd) for expressing luminous intensity.
SI Base Units and Definitions
Quantity
Unit name
Unit
symbol
Unit of length
Meter
m
Unit of mass
Kilogram
kg
Unit of time
Second
s
Unit of electric current
Ampere
A
Unit of thermodynamic
temperature
Kelvin
K
Unit of amount of matter
Mole
mol
Unit of luminous intensity Candela
cd
Definition
The meter is the length of the path travelled by light in vacuum during a time interval of 1/299 792 458 of a second.
The kilogram is the unit of mass. It is equal to the mass of the international prototype of the kilogram.
The second is the duration of 9 192 631 770 periods of the radiation corresponding to the transition between the two hyperfine levels of the ground state of the cesium 133 atom.
The ampere is that constant current which, if maintained in two
straight parallel conductors of infinite length, of negligible circular
cross-section, and placed 1 meter apart in vacuum, would produce
between these conductors a force equal to 2 x 10-7 newton per
meter of length.
The kelvin, unit of thermodynamic temperature, is the fraction
1/273.16 of the thermodynamic temperature of the triple point of
water (see note).
The mole is the amount of matter of a system which contains as
many elementary entities as there are atoms in 0.012 kilogram of
carbon 12. When the mole is used, the elementary entities must be
specified and may be atoms, molecules, ions, electrons, other particles, or specified groups of such particles.
The candela is the luminous intensity, in a given direction, of a
source that emits monochromatic radiation of frequency 540 ×
1012 hertz and that has a radiant intensity in that direction of 1/683
Watt per steradian.
Note The triple point of water is the point at which the water can coexist in equilibrium in all three phases, i.e.,
liquid, solid (ice), and gas (water vapor).
Units that are expressed as products or divisions of powers of basic units are called derived units, such as
square meters (m2) and meters per second (m/s). When many base units are used to express a derived unit,
resulting in a complicated expression, special names are sometimes used, e.g, Hertz (Hz) = 1/s is used to
express frequency and Newton (N) = kg·m/s2 is used to express force. The Newton (N) is used to express the
amount of force required to accelerate a mass of one kilogram at a rate of one meter per second squared. Similarly, the SI unit of pressure is the Pascal (Pa).
A new concept established supplementary units as a separate class from base units including the radian for
plane angles and the steradian for solid angles. These units can also be considered as derived units, but in
mathematics and other specific fields, they are used as if they were base units. Therefore, the General Conference on Weights and Measures designated these units as supplementary units to base units. Whether these
are designated as supplementary units or derived units is left to the discretion of each country. Japan’s Measurement Law defines these units as derived units.
245
Appendix G
International System of Units
SI Supplementary Units
Quantity
Unit name
Plane angle
Radian
Unit
symbol
rad
Solid angle
Steradian
sr
Definition
A radian is the plane angle between two radii of a circle that cuts
off on the circumference an arc equal in length to the radius.
A steradian is the solid angle that, having its vertex in the center of
a sphere, cuts off an area of the surface of the sphere equal to that
of a square with sides equal in length to the radius of the sphere.
SI Derived Units
Quantity
Unit name
Unit
symbol
Expressed in terms of other
SI units
Plane angle
Solid angle
Frequency
radian
steradian
hertz
rad
sr
Hz
1 Hz = 1 s−1
Force
newton
N
1 N = 1 kg·m·s−2
Pressure, stress
pascal
Pa
Energy, work, quantity of heat
Power, radiant flux
joule
J
1 Pa = 1 N·m−2
1 J = 1 N·m
watt
W
1 W = 1 J·s−1
Electric charge,
coulomh
quantity of electricity
Electric potential,
volt
electromotive force
Electric capacitance farad
C
1 C = 1 A·s
V
1 V = 1 W·A−1
F
1 F = 1 C·V−1
Electrical resistance
Ω
1 Ω = 1 V·A−1
Electric conductance siemens
S
Magnetic flux
weber
Magnetic flux density tesla
wb
T
1 S = 1 A·V−1
1 wb = 1 V·s
Inductance
henry
H
Temperature
Luminous flux
Illuminance
degree Celsius
lumen
lux
°C
lm
lx
ohm
-----
1 T = 1 wb·m−2
1 H = 1 wb·A−1
t°C = (t + 273.15) K
1 lm = 1 cd·sr
1 lx = 1 cd·s·rm−2
To indicate decimal multiples or submultiples of these units, the following list of prefixes was established. For
example, the hectopascal (hPa), a unit commonly heard in weather forecasts, is one pascal (Pa) multiplied by
102, which is indicated by adding the prefix hecto (h). The current SI units specify 20 prefixes from 1024 to
10-24. For practical purposes, these units are also used in combination with time units (minute, hour, and second), angle units (degree, minute, second), volume units (liter), and mass units (ton).
SI Unit Prefixes
Multiple
Prefix
Symbol
−24
y
Name
yocto
10−21
z
septo
10−18
a
atto
10−15
f
femto
10−12
p
pico
10
246
Appendix G
International System of Units
Multiple
Prefix
Symbol
Name
−9
n
nano
10−5
µ
micro
10−3
m
milli
10−2
c
centi
10−1
d
deci
101
da
deka
102
h
hecto
103
k
kilo
105
M
mega
109
G
giga
1012
T
tera
1015
P
peta
1018
E
exa
1021
Z
zetta
1024
Y
yotta
10
SI Unit Conversion Table
Quantity
Unit name
Symbol
Radian
SI unit
symbol
rad
Meter
m
Square meter
m2
Cubic meter
m3
Kilogram
kg
s
min
h
d
m/s
kn
1
103
1
103
1.66057 × 10−7
1
60
3600
86400
1
1852/3600
Second
s
Meters per second
m/s
S−1
1
Hertz
Hz
rpm
1/60
Reciprocal second
rad/s
m/s
G
1
1
9.80665
Radians per second
Meters per second
S−1
rad/s
Degree
Minute
Second
Meter
Micron
Nano
Angstrom
Nautical mile
°
‘
“
M
µ
n
Å
mile
Area
Square meter
Are
Hectare
m2
a
ha
Volume
Cubic meter
Liter
Mass
Kilogram
Ton
Atomic mass unit
m3
l
kg
t
u
Time
Frequency
Second
Minute
Hour
Day
Meter per second
Knot
Cycle
Rotation speed
Revolution per minute
Angle
Length
Speed
Angular velocity Radian per second
Acceleration
Meter per second
G
SI conversion
rate
π/180
π/10800
π/648000
1
10−6
10−9
10−10
1852
1
102
104
SI unit name
m/s2
247
Appendix G
International System of Units
Quantity
Unit name
Force
Symbol
kgf
tf
dyn
Kilogram force
Deadweight ton
Dyne
SI conversion
rate
9.80665
9806.65
10−5
SI unit name
SI unit
symbol
Newton
N
9.80665
Newton-meter
N·m
Pascal
Pa
Pascal
Pa
Moment of force Kilogram-force meter
Stress, pressure Kilogram-force per square meter
Kilogram-force per square centimeter
Kilogram-force per square millimeter
kgf·m
kgf/m
kgf/cm2
kgf/mm2
9.80665
9.80665 × 104
9.80665 × 106
Pressure
Meter of hydraulic pressure
Millimeter of mercury
Torr
Atmospheric pressure
Bar
mH2O
mmHg
Torr
Atm
bar
9.80665
101325/760
101325/760
101325
105
Energy
Erg
I.T. calorie
Kilogram-force meter
Kilowatt hour
Metric horsepower hour
Electronvolt
erg
callT
kgf·m
kW·h
PS·h
eV
Joule
10−7
4.1868
9.80665
3.600 × 106
2.64779 × 106
1.60219 × 10−19
Watt
1
735.5
9.80665
J
10−1
10−3
9.80665
Pascal second
Pa·s
10−4
10−6
Viscosity square
meter per second
m2/s
2
Workrate, power Watt
Metric horsepower hour
Kilogram-force second per meter
Viscosity
Poise
Centipoise
Kilogram-force second per square
meter
W
PS·h
kgf·m/s
P
cP
kgf·s/m2
Kinematic viscosity
St
cSt
Stokes
Centistokes
W
Code Tables
Hexadecimal-to-Decimal Conversion Table
0
10
20
30
40
50
60
70
80
90
A0
B0
C0
D0
E0
F0
248
00
0
16
32
48
64
80
96
112
128
144
160
176
192
208
224
240
01
1
17
33
49
65
81
97
113
129
145
161
177
193
209
225
241
02
2
18
34
50
66
82
98
114
130
146
162
178
194
210
226
242
03
3
19
35
51
67
83
99
115
131
147
163
179
195
211
227
243
04
4
20
36
52
68
84
100
116
132
148
164
180
196
212
228
244
05
5
21
37
53
69
85
101
117
133
149
165
181
197
213
229
245
06
6
22
38
54
70
86
102
118
134
150
166
182
198
214
230
246
07
7
23
39
55
71
87
103
119
135
151
167
183
199
215
231
247
08
8
24
40
56
72
88
104
120
136
152
168
184
200
216
232
248
09
9
25
41
57
73
89
105
121
137
153
169
185
201
217
233
249
0A
10
26
42
58
74
90
106
122
138
154
170
186
202
218
234
250
0B
11
27
43
59
75
91
107
123
139
155
171
187
203
219
235
251
0C
12
28
44
60
76
92
108
124
140
156
172
188
204
220
236
252
0D
13
29
45
61
77
93
109
125
141
157
173
189
205
221
237
253
0E
14
30
46
62
78
94
110
126
142
158
174
190
206
222
238
254
0F
15
31
47
63
79
95
111
127
143
159
175
191
207
223
239
255
Appendix G
International System of Units
ASCII Codes
0
10
20
30
40
50
60
70
00
nul
dle
sp
0
@
P
‘
p
01
soh
dcl
!
1
A
Q
a
q
02
stx
dc2
“
2
B
R
b
r
03
etx
dc3
#
3
C
S
c
s
04
eot
dc4
$
4
D
T
d
t
05
enq
nak
%
5
E
U
e
u
06
ack
syn
&
6
F
V
f
v
07
bel
etb
‘
7
G
W
g
w
08
bs
can
(
8
H
X
h
x
09
ht
em
)
9
I
Y
i
y
0A
lf
sub
*
:
J
Z
j
z
0B
vt
esc
+
;
K
[
k
{
0C
ff
fs
,
<
L
\
l
|
0D
cr
gs
=
M
]
m
}
0E
so
rs
.
>
N
^
n
~
0F
si
us
/
?
O
_
o
del
249
International System of Units
250
Appendix G
Revision History
A manual revision code appears as a suffix to the catalog number on the front cover of the manual.
Cat. No. W440-E1-03
Revision code
The following table outlines the changes made to the manual during each revision. Page numbers refer to the
previous version.
Revision code
01
02
Date
November 2004
November 2005
03
October 2010
Revised content
Original production
“PC” replaced globally to “PLC” in the sense of Programmable Controller.
“CX-FLnet” added globally to FL-net Unit Support Software.
Page v: Signal word definitions changed.
Page xi: Table of manuals reworked.
Page xxi: Two precautions added in middle of page and addition about Startup
Mode made to existing precaution.
Page 8: New section 1-4 on CX-FLnet added.
Page 12: “10Base5” corrected to “100Base5” at top right corner.
Page 19: “0x2000” changed to “0x1fff” and “0x200” changed to “0x2000” in
table.
Page 29: Additions made in the right column for HER and PER.
Pages 39, 42, 145: “CX-Net” changed to “CX-Integrator.”
Page 39: Last paragraph in Applicable Programming Devices deleted and addition made to the paragraph before it.
Pages 50 and 51: Section 4-2-1 reworked.
Pages 66 to 69: Most of section 5-2-1 reworked.
Pages 79 and 80: Figures replaced.
Page 79: Sentence removed from step 2.
Pages 91 and 96: “/CJ” added.
Pages 149 and 152: “CX-Programmer” changed to “CX-Integrator.”
Pages 163 to 189: Moved to the last appendix and new section added.
System requirements for FL-net setting tool changed.
251
OMRON Corporation
Industrial Automation Company
Authorized Distributor:
Tokyo, JAPAN
Contact: www.ia.omron.com
Regional Headquarters
OMRON EUROPE B.V.
Wegalaan 67-69-2132 JD Hoofddorp
The Netherlands
Tel: (31)2356-81-300/Fax: (31)2356-81-388
OMRON ELECTRONICS LLC
One Commerce Drive Schaumburg,
IL 60173-5302 U.S.A.
Tel: (1) 847-843-7900/Fax: (1) 847-843-7787
OMRON ASIA PACIFIC PTE. LTD.
No. 438A Alexandra Road # 05-05/08 (Lobby 2),
Alexandra Technopark,
Singapore 119967
Tel: (65) 6835-3011/Fax: (65) 6835-2711
OMRON (CHINA) CO., LTD.
Room 2211, Bank of China Tower,
200 Yin Cheng Zhong Road,
PuDong New Area, Shanghai, 200120, China
Tel: (86) 21-5037-2222/Fax: (86) 21-5037-2200
© OMRON Corporation 2004 All Rights Reserved.
In the interest of product improvement,
specifications are subject to change without notice.
Printed in Japan
Cat. No. W440-E1-03
1010
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