ITNC-EIS01 ITNC-EIS01-DRM ITNC-EIS01-CST ITNC

ITNC-EIS01 ITNC-EIS01-DRM ITNC-EIS01-CST ITNC

Open Network Controller

OPERATION MANUAL

ITNC-EIS01

ITNC-EIS01-DRM

ITNC-EIS01-CST

ITNC-EIX01

ITNC-EIX01-DRM

ITNC-EIX01-CST

ITNC-EIS01

ITNC-EIS01-DRM

ITNC-EIS01-CST

ITNC-EIX01

ITNC-EIX01-DRM

ITNC-EIX01-CST

Open Network Controller

Operation Manual

Revised October 2004

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.

!

WARNING

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

!

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, 1999

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

Unit Versions of Open Network Controllers

Unit Versions

A “unit version” has been introduced to manage Open Network Controllers (ITNC-EIS01, ITNC-

EIS01-DRM, ITNC-EIS01-CST, ITNC-EIX01, ITNC-EIX01-DRM, and ITNC-EIX01-CST) according to differences in functionality accompanying product upgrades.

1) Notation of Unit Versions on Products

Products that are being managed using unit versions have the unit version given in the format

“Ver. .” on the nameplate. (Refer to the following figure for the position of the nameplate.)

vi

Nameplate

Unit versions starts from version 1.1. A unit version is not given on the nameplate for products prior to version 1.1.

Units without a unit version are called “Pre-Ver. 1.1 Units.”

2) Confirming Unit Versions with Web Service Version 2.0

The unit version is given in the

Open Network Controller Version

row the first table displayed for the System Profile display of Web Service Version 2. (Web Service Version 2 must be installed separately.)

Unit version

The unit version of Open Network Controllers for which a unit version is not given on the nameplate will be given as V1.00, V1.01, V1.03, or V1.05.

3) Using Unit Version Labels

The unit version labels shown below are included with the product.

Unit Version Notation

The Open Network Controller (ONC) is available in two basic types: ONC Version 1 and ONC Version

2. “ONC Version 1” and “ONC Version 2” are product names, and “Version 1” and “Version 2” in these product names do not refer to the unit version.

This manual uses the notation “Version .

” to give the unit version to avoid confusion with “Version 1” and “Version 2” in the product names.

Supported Functionality According to Unit Version

Yes: Supported, ––: Not supported, Restricted: Limited support

Function

CLOCK WRITE command (07 02)

Pre-Ver. 1.1

Executed without stopping OS tick interrupt

---

Unit Ver. 1.1 or later

Executed with OS tick interrupts prohibited and then enables interrupts

Yes

Reference page

125

125 TIME COMPENSATION command (07 03)

Diskspace utility --Yes 235

Changes to QNX Startup File

Part of the /usr/config/sysinit.1 file has been changed in upgrading to unit version 1.1. If you have changed the /usr/config/sysinit.1 file, confirm the effects of the upgrade on your application.A script file called /usr/Tool/bin/onc_command has been provided so that the user can execute applicationspecific commands during ONC startup. Although previously such commands were directly written to the sysinit.1 file, all user commands should not be placed in the onc_command file.

vii

viii

TABLE OF CONTENTS

PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1 Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2 General Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3 Safety Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4 Operating Environment Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5 Application Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6 Conformance to EC Directives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 1

Introduction

1-1

1-2

1-3

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Basic Application Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 2

Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-1

2-2

2-3

System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CPU_UNIT Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

NP Functions and Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 3

Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-5

3-6

3-7

3-8

3-1

3-2

3-3

3-4

3-9

Nomenclature and Functions

DIP Switch Settings

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Mounting Expansion Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Installing the Open Network Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Connecting the Power Supply Cable

Connecting COM Port Cables

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Connecting DeviceNet Cables

Connecting Ethernet Cables

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Handling Memory Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 4

Software Settings

4-1

4-2

4-3

4-4

4-5

4-6

4-7

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Logging onto the Open Network Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Using the ONC_wizard Setting Tool

Making Settings with a vi Editor

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Transferring Settings Files with FTP

Setting File Descriptions

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Setting Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 5

FINS Commands

5-5

5-6

5-7

5-8

5-1

5-2

5-3

5-4

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

FINS Commands Addressed to CPU_Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

FINS Commands Addressed to ETN_UNIT

FINS Commands Addressed to HLK_UNIT

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

FINS Commands Addressed to DRM_UNIT

FINS Commands Addressed to CLK_UNIT

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

FINS Commands Addressed to SYSMAC_UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

End Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

115

117

117

128

131

158

162

162

171

xiii

xiv xiv xiv xv xvi xvii

59

82

83

102

60

61

66

82

21

39

41

46

52

22

26

28

31

53

9

10

11

12

1

2

3

7

ix

x

TABLE OF CONTENTS

SECTION 6

ITNC-EIS01-CST and ITNC-EIX01-CST

(CS1 Bus Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-1

6-2

6-3

6-4

6-5

Introduction

Functions

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Hardware Settings

Software Settings

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

FINS Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 7

Troubleshooting

7-1

7-2

7-3

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Seven-segment Display and syslog Error Messages

DeviceNet Indicator Displays

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Error Messages with the ITNC-EIS01-CST or ITNC-EIX01-CST . . . . . . . . . . . . . . . . . .

Appendices

A Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

B Connector Signal Arrangements

C Replacing the Backup Battery

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

D PT Connection Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

E Diskspace Utility (Unit Version 1.1 or later) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

195

196

211

216

179

180

181

184

187

191

225

227

229

231

235

237

241

About this Manual:

This manual describes the installation and operation of the Open Network Controllers and includes the sections described below. The Open Network Controllers provide an FINS gateway function that enables connecting personal computers on an Ethernet network to OMRON PLCs, OMRON components, and

DeviceNet-compatible devices.

Please read this manual and all related manuals carefully and be sure you understand the information provided before attempting to install and operate an Open Network Controller.

The following manuals provide information on related products.

Product model numbers Manual

C200PC-ISA01-DRM-E

C200PC-ISA01-E/ISA

C200PC-ISA 2-SRM-E

2-DRM-E

C200PC-EXP01

SYSMAC 3G8F5-CLK21-E

SYSMAC Board Operation Manual

SYSMAC Board Operation Manual

Controller Link Support Board Operation Manual

Catalog number

(suffixes omitted)

W326

V201

W307

Section 1

provides an overview of the Open Network Controllers, including their components and a basic application procedure.

Section 2

outlines the functions of the Open Network Controllers.

Section 3

provides information on the hardware components, installation, and settings of the Open Network Controller.

Section 4

describes the various methods that can be used to set the contents of the environment settings files for the Open Network Controller.

Section 5

individually describes the FINS commands and responses for CPU_UNIT and the network providers (NPs). Refer to the the FINS Commands Reference Manual (W227) for further information on FINS commands.

Section 6

describes the ITNC-EIS01-CST and ITNC-EIX01-CST Open Network Controllers.

Section 7

describes the use of the 7-segment display, syslog error log file, and DeviceNet indicators to troubleshoot error that can occur on the Open Network Controller.

The

Appendices

provide a list of specifications, connector signal layouts, the battery replacement procedure, and information on the Programmable Terminal (PT) connection service

!

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.

xi

PRECAUTIONS

This section provides general precautions for using the Open Network Controller and related devices.

The information contained in this section is important for the safe and reliable application of the Open Network Controllers. You must read this section and understand the information contained before attempting to set up or operate an Open Network Controller.

1 Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2 General Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3 Safety Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4 Operating Environment Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5 Application Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6 Conformance to EC Directives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv xiv xiv xv xvi xvii

xiii

Safety Precautions

1

2

6

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.

Personnel with an understanding of TCP/IP applications technology.

General Precautions

The user must operate the Open Network Controller according to the performance specifications described in the operation manuals.

Before using an Open Network Controller under conditions which are not described in the manual or applying an Open Network Controller 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 Open Network

Controller 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 Open Network Controller. Be sure to read this manual before attempting to use an Open

Network Controller and keep this manual close at hand for reference during operation.

!

WARNING

It is extremely important that an Open Network Controller 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 an Open Network Controller System to the above-mentioned applications.

3 Safety Precautions

!

WARNING

Do not attempt to take an Open Network Controller apart while the power is being supplied. Doing so may result in electric shock.

!

WARNING

Do not touch any of the terminals while the power is being supplied. Doing so may result in electric shock.

!

WARNING

Do not short the battery terminals or charge, disassemble, apply pressure to, heat, or incinerate the battery. Do not subject the battery to strong shocks. Doing any of these may result in leakage, rupture, heat generation, or ignition of the battery. Batteries that have been subjected to shock may leak if they are used.

!

WARNING

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.

!

WARNING

Interlock circuits, limit circuits, and similar safety measures in external circuits

(i.e., not in the Open Network Controller or a Programmable Controller) must be provided by the customer.

xiv

Operating Environment Precautions

4

!

Caution

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

!

Caution

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

!

Caution

Tighten the terminal screws on the power supply to the torque specified in the operation manual. The loose screws may result in burning or malfunction.

4

!

Caution

Always turn OFF the power supply to the Open Network Controller before attempting any of the following. Not turning OFF the power supply may result in malfunction or electric shock.

Setting DIP switches or rotary switches.

Replacing the battery.

Performing any other operation that requires touching the controls of the

Open Network Controller.

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

Install the Open Network Controllers properly as specified in the operation manuals. Improper installation of the Open Network Controllers may result in malfunction.

!

Caution

Take appropriate and sufficient countermeasures when installing systems in the following locations:

Locations subject to static electricity or other forms of noise.

Locations subject to strong electromagnetic fields.

Locations subject to possible exposure to radioactivity.

Locations close to power supplies.

!

Caution

The operating environment of the Open Network Controller System will have a large effect on the longevity and reliability of the system. Improper operating environments can lead to malfunction, failure, and other unforeseeable problems with the Open Network Controller System. Be sure that the operating environment is within the specified conditions at installation and remains within the specified conditions during the life of the system.

xv

Application Precautions

5

5

Application Precautions

Observe the following precautions when using the Open Network Controller

System.

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.

Do not apply voltages to the Input Units in excess of the rated input voltage.

Excess voltages may result in burning.

Do not apply voltages or connect loads to the Output Units in excess of the maximum switching capacity. Excess voltage or loads may result in burning.

Disconnect the functional ground terminal when performing withstand voltage

• tests. Not disconnecting the functional ground terminal may result in burning.

Always connect to a ground of 100

or less when installing the Open Network

Controllers. Not connecting to a ground of 100

or less may result in electric shock.

A ground of 100

or less must be installed when shorting the GR and LG terminals on the Power Supply Open Network Controller.

Always turn OFF the power supply to the Open Network Controller and the

PLC 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 or any other Units.

Assembling the Units.

Setting DIP switches or rotary switches.

Connecting cables or wiring the system.

Connecting or disconnecting the connectors.

Do not attempt to disassemble, repair, or modify any Units.

The mounting screws, terminal screws, and cable connector screws must be tightened to the torque specified in the relevant manuals on both the Open Network Controller and the PLC. Incorrect tightening torque may result in malfunction.

Do not allow foreign matter to enter the Open Network Controller when wiring.

Leave the label attached to the I/O Units when wiring. 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.

Wire all connections correctly.

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

Mount I/O Units only after checking terminal blocks and connectors completely.

Be sure that the terminal blocks, Memory Units, expansion cables, and other items with locking devices are properly locked into place. Improper locking may result in malfunction.

Check the user program for proper execution before actually executing it. Not checking the program may result in unexpected operation.

xvi

Conformance to EC Directives

6

6

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.

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

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

Resume operation only after transferring to the new CPU Unit or Open Network Controller the contents of the DM Area, HR Area, and other data required for resuming operation. Not doing so may result in an unexpected operation.

Do not turn OFF the power supply while data is being written to the internal flash disk. Doing so may damage the file being written.

Also, do not turn OFF the power supply or remove the Memory Card when the

Card is being accessed. Data files may be lost.

Maintain the operating environment for the Memory Cards (such as the ambient operating temperature and other conditions). Request operating environment conditions from the manufacture of the Card.

We recommend making a backup of the internal disk to prevent losing the data inadvertently, e.g., by mistakenly deleting it.

The PC will not start operation even after the power supply is turned ON until the CS1 Bus Interface in the Open Network Controller completes initialization.

The Open Network Controller requires approximately 40 seconds to start operation after the power supply is turned ON. You must design the system to allow for this delay.

Also, if the power supply to the Open Network Controller is interrupted during operation, the PC will detect an I/O bus error. You must design the system to allow for this possibility.

Do not short the battery terminals or charge, disassemble, heat, or incinerate the battery. Do not subject the battery to strong shocks. Doing any of these may result in leakage, rupture, heat generation, or ignition of the battery. Dispose of any battery that has been dropped on the floor or otherwise subjected to excessive shock. Batteries that have been subjected to shock may leak if they are used.

UL standards require that batteries be replaced only by experienced technicians. Do not allow unqualified persons to replace batteries.

Conformance to EC Directives

The Open Network Controllers comply with EC Directives. To ensure that the machine or device in which an Open Network Controller is used complies with

EC directives, the Open Network Controller must be installed as follows:

1, 2, 3...

1, 2, 3...

1. The Open Network Controller must be installed within a control panel.

2. Reinforced insulation or double insulation must be used for the DC power supplies used for the communications and I/O power supplies.

3. The Open Network Controllers also conform to the Common Emission Standard (EN50081-2). When an Open Network Controller is built into a machine, however, the structure of the control panel, the relationships to other connected devices, wiring, and other variables can cause the overall machine to fail to meet the Standards. It is the responsibility of the final manufacturer to confirm that EC Directives have been met.

The following are examples of countermeasures that can be taken to reduce noise.

1. Place ferrite cores must on the communications cables to reduce noise given off by the cables.

2. Use power cables that are as thick and as short as possible in the control panel and ground properly to 100

or less.

xvii

Conformance to EC Directives

6

3. Use power cables that are as thick and as short as possible for DeviceNet communications cables and ground them properly to 100

or less.

xviii

SECTION 1

Introduction

This section provides an overview of the Open Network Controllers, including their components and a basic application procedure.

1-1

1-2

1-3

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Basic Application Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2

3

7

1

Overview

1-1 Overview

Section 1-1

An Open Network Controller provides a gateway for FINS message communications among the following devices:

Personal computers, PLCs, or other nodes on an Ethernet network.

PLCs or other nodes on a Controller Link, Host Link, or SYSMAC I/O bus network.

OMRON FA components on a CompoWay/F network.

Devices from OMRON or other manufacturers on a DeviceNet network.

The following diagram illustrates the devices that can communicate through an

Open Network Controller.

Memory Card

Open Network Controller

DeviceNet

24 V DC

Expansion Board

(Controller Link or

SYSMAC Board)

10Base-T

Slaves

Controller Link or SYSMAC I/O bus

(from

Expansion

Board)

Two

RS-232C ports

RS-422A/485 port (on Expansion Models only)

1:N Host Link or CompoWay/F

Host Link (CS1,

CV, or C Series)

Ethernet

Components or

CS1, C, or CV PLCs

Personal computer

PLC PLC Workstation

An Open Network Controller provides the following features.

The Open Network Controller is smaller and more resistant to environmental conditions than personal or factory computers, allowing for a wider range of installation sites.

A real-time OS supports a multitasking network environment.

A 10Base-T Ethernet port is provided on all models.

The Open Network Controller converts FINS commands from personal computers, PLCs, or other nodes on an Ethernet network to Host Link commands, enabling FINS communications with PLCs that do not support FINS commands directly.

The Open Network Controller converts FINS commands from personal computers, PLCs, or other nodes on an Ethernet network to CompoWay/F commands, enabling FINS communications with CompoWay/F devices.

The Open Network Controller converts FINS commands from personal computers, PLCs, or other nodes on an Ethernet network to explicit messages for

DeviceNet-compatible devices manufactured by OMRON and by other companies (supported by ITNC-EIS01-DRM and ITNC-EIX01-DRM Models only).

2

Components

1-2

Section 1-2

Components

This section describes the components of an Open Network Controller. The following table lists the main components.

Model

ITNC-EIS01

ITNC-EIS01-DRM

ITNC-EIX01

ITNC-EIX01-DRM

ITNC-EIS01-CST

(See note 2.)

ITNC-EIX01-CST

(See note 2.)

Description

Standard Model

Standard Model with DeviceNet

Expansion Model

Expansion Model with DeviceNet

Standard Model with

CS1 Bus Interface

Expansion Model with

CS1 Bus Interface

Specifications

No expansion slots

Two COM ports (RS-232C)

No expansion slots

Two COM ports (RS-232C)

DeviceNet interface

Expansion slot (see note 1)

Three COM ports

(two RS-232C and one RS-422)

Expansion slot (see note 1)

Three COM ports

(two RS-232C and one RS-422)

DeviceNet interface

Expansion slot (see note 1)

Two COM ports

(CS1 bus interface)

Expansion slot (see note 1)

Three COM ports

(CS1 bus interface)

--ITNC-AP001

ITNC-AP002

ITNC-DIN01

Standard Model

Mounting Bracket

Expansion Model

Mounting Bracket

DIN Track

Mounting Bracket

---

---

Note

1. The expansion slot is an ISA bus slot into which either a Controller Link

Board or a SYSMAC Board can be mounted. Only one slot is provided.

2. Refer to

Section 6 ITNC-EIS01-CST and ITNC-EIX01-CST

for information on the ITNC-EIS01-CST and ITNC-EIX01-CST.

Each model is described next. Open the packing boxes and make sure you have the correct models.

3

Components

Reference Manuals

ITNC-EIS01

Standard Model

Section 1-2

Model

ITNC-MD1Q-EF

---

---

---

ITNC-RK1Q-ECD

ITNC-DK1Q-ECD

ITNC-DL1Q-ECD-V

2

---

---

Name

Open Network Controller Connection Units for Non-OMRON PLCs (Mitsubishi A-series

Computer Link Module) Operation Manual

HLK_UNIT Serial Network Provider (for ID

Controllers and Productivity Monitors)

Release Notes

SYSMAC LINK Connection Unit Release

Notes

Open Network Controller ONC Java Applet

Setting Tool Operation Manual

Open Network Controller RemoteKit

Software Operation Manual

Open Network Controller Database

Software Operation Manual

Open Network Controller Data

Collection/Distribution Service Software

Version 2 Operation Manual

Open Network Controller Web Service

Software Version 2 Operation Manual

FinsLink Release Notes

Cat. No.

V209-E1

---

---

---

V221-E1

V223-E1

V225-E1

---

---

Note

Refer to the following Web site for the most recent information on Open Network

Controllers.

http://www.plcsoft.ne.jp/it/onc/english/index.html

The ITNC-EIS01 Standard Model is shown below. Use the illustration to confirm you have the correct model.

ITNC-EIS01-DRM

Standard Model with

DeviceNet

Safety Precautions

ITNC-EIS01

Standard Model

Safety Precautions

The ITNC-EIS01-DRM Standard Model with DeviceNet is shown below. Use the illustration to confirm you have the correct model.

ITNC-EIS01-DRM

Standard Model with DeviceNet

Safety Precautions

Safety Precautions

4

Components

ITNC-EIX01

Expansion Model

Section 1-2

The ITNC-EIX01 Expansion Model is shown below. Use the illustration to confirm you have the correct model.

Safety Precautions

ITNC-EIX01-DRM

Expansion Model with

DeviceNet

ITNC-EIX01

Expansion Model

Safety Precautions

The ITNC-EIX01-DRM Expansion Model with DeviceNet is shown below. Use the illustration to confirm you have the correct model.

ITNC-AP001

Standard Model

Mounting Bracket

Safety Precautions

ITNC-EIX01-DRM

Expansion Model with DeviceNet

Safety Precautions

The ITNC-AP001 Standard Model Mounting Bracket is shown below. Use the illustration to confirm you have the correct model.

ITNC-AP001

Standard Model Mounting Bracket

The ITNC-AP001 is used to mount a Standard Model Open Network Controller vertically.

The ITNC-DIN01 DIN Track Mounting Bracket can also be used together with

DIN Track to mount vertically.

Refer to

3-4 Installing the Open Network Controller

for installation methods.

5

Components

ITNC-AP002

Expansion Model

Mounting Bracket

Section 1-2

The ITNC-AP002 Expansion Model Mounting Bracket is shown below. Use the illustration to confirm you have the correct model.

ITNC-DIN01

DIN Track Mounting

Bracket

ITNC-AP002

Expansion Model Mounting Bracket

The ITNC-AP002 is used to mount an Expansion Model Open Network Controller vertically.

The ITNC-DIN01 DIN Track Mounting Bracket can also be used together with

DIN Track to mount vertically.

Refer to

3-4 Installing the Open Network Controller

for installation methods.

The ITNC-DIN01DIN Track Mounting Bracket is shown below. Use the illustration to confirm you have the correct model.

ITNC-DIN01

DIN Track Mounting Bracket

Four mounting screws

The ITNC-DIN01 DIN Track Mounting Bracket is used when mounting an

Open Network Controller to DIN Track. DIN Track mounting is possible for both

Standard and Expansion Models.

The ITNC-AP001 Standard Model Mounting Bracket or ITNC-AP002 Expansion Model Mounting Bracket is also required to mount vertically on DIN Track.

Refer to

3-4 Installing the Open Network Controller

for installation methods.

6

Basic Application Procedure

1-3

Section 1-3

Basic Application Procedure

The following procedure can be used to install and set up an Open Network Controller.

1, 2, 3...

1. Design the configuration of the network on paper, including the following.

Refer to

4-7 Setting Examples.

The networks to be used and the network addresses

Node addresss

FINS routing

Event memory allocation

2. Mount the Expansion Board (for Expansion Models only).

Refer to

3-3 Mounting Expansion Boards.

3. Set the DIP switches.

Refer to

3-2 DIP Switch Settings.

4. Connect the cables, including the following. (See note.)

Refer to

Section 3 Hardware

.

Power supply cables

Cables for Unit settings

Network cables

Note

Refer to

Section 6 ITNC-EIS01-CST and ITNC-EIX01-CST

for ITNC-

EIS01-CST and ITNC-EIX01-CST cable connections.

5. Take the settings designed on paper and actually make them in the Open

Network Controller using one of the following methods.

Refer to

Section 4 Software Settings.

Use a simple tool on the Open Network Controller (use a HyperTerminal via COM1 or use Telnet via Ethernet).

Use a text editor on Windows and transfer the settings after editing.

Edit directly on the Open Network Terminal using the vi editor (use a HyperTerminal via COM1 or use Telnet via Ethernet)

Note

Refer to

4-3-3 Backing Up Settings

for backup methods.

6. Restart the Open Network Controller (e.g., cycle power).

7. Start operation, i.e., start FINS communications.

Refer to Section

5 FINS Commands.

7

SECTION 2

Functions

This section outlines the functions of the Open Network Controllers.

2-1

2-2

2-3

System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CPU_UNIT Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

NP Functions and Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2-3-1

2-3-2

2-3-3

2-3-4

2-3-5

ETN_UNIT

HLK_UNIT

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DRM_UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CLK_UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SYSMAC_UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13

13

16

17

10

11

12

18

9

System Configuration

Section 2-1

2-1 System Configuration

Hardware Configuration

The configuration of an Open Network Controller is shown in the following illustration.

Open Network Controller

Memory Card

DeviceNet

(See note 1.)

24 V DC

Expansion Board

(Controller Link or

SYSMAC Board)

(See note 2.)

Slaves

Controller Link or SYSMAC I/O bus

(from

Expansion

Board)

RS-422A/485 port (See note 3.)

1:N Host Link or CompoWay/F (See note 4.)

10Base-T

Two

RS-232C ports

Host Link (CS1,

CV, or C Series)

Ethernet

Components or

CS1, C, or CV PLCs

Personal computer

PLC PLC Workstation

Note

1. DeviceNet is supported by the ITNC-EIS01-DRM and ITNC-EIX01-DRM.

2. A Controller Link Board or a SYSMAC Board can be mounted in the ITNC-

EIX01 or ITNC-EIX01-DRM. Only one slot is provided.

3. The RS-422A/485 port (COM3 port) is supported by the ITNC-EIX01 or

ITNC-EIX01-DRM.

4. Both Host Link and CompoWay/F connections are not possible from a single

COM port.

10

CPU_UNIT Functions

Software Configuration

Section 2-2

The software configuration of the Open Network Controller is illustrated below.

Event memory

NPs

Applications

Component

CPU_UNIT

Event memory

NPs

FinsGateway

Function

CPU_UNIT provides functions of a CPU Unit in a PLC. The variables in event memory can be read and written from personal computers and other devices on the networks by sending FINS commands.

The variables in event memory can be allocated to slave I/O on a DeviceNet network, to data links on a Controller Link network, or to I/O memory for the SYSMAC Board.

NP stands for network provider. The network providers function as Communications Units to provide network software services.

Data is read or written by sending FINS commands to the NPs or by sending FINS commands to connected devices through the NPs.

ETN_UNIT: The Ethernet NP.

HLK_UNIT:

DRM_UNIT:

CLK_UNIT:

The C-mode and CV-mode Host Link

(SYSMAC WAY) and CompoWay/F NP.

The DeviceNet NP.

The Controller Link NP.

SYSMAC_UNIT: The SYSMAC Board connection NP.

FinsGateway performs communications between CPU_UNIT and the NPs, communications between NPs, and FINS routing.

It also manages the event memory.

Note

Refer to the following Web site for the most recent information on software for

Open Network Controllers.

http://www.plcsoft.ne.jp/it/onc/english/index.html

2-2 CPU_UNIT Functions

CPU_UNIT is a software component that emulates the FINS message functions of the CPU Unit in a PLC. The event memory (i.e., the variable memory in the

Open Network Controller) can be read and written from personal computers and other devices on the networks.

FINS Commands

Addressed to CPU_UNIT

The following FINS commands can be addressed to CPU_UNIT.

11

NP Functions and Precautions

Event Memory

Section 2-3

Command code

01 01

01 02

02 01

02 02

02 03

02 25

05 01

05 02

07 01

07 02

07 03

08 01

Name and function

MEMORY AREA READ: Reads event memory

MEMORY AREA WRITE: Writes event memory

PARAMETER AREA READ: Reads the routing tables

PARAMETER AREA WRITE: Writes the routing tables

PARAMETER AREA CLEAR: Clears the routing tables

ROUTING TABLE SET

CONTROLLER DATA READ

CONNECTION DATA READ

CLOCK READ

CLOCK WRITE

TIME COMPENSATION (unit version 1.1 or later)

INTERNODE ECHO TEST

Note

FINS commands addressed to CPU_UNIT must be sent through an NP.

Refer to

5-2 FINS Commands Addressed to CPU_Unit

for details on FINS commands addressed to CPU_UNIT.

Event memory is the internal memory for FinsGateway. Just like the CIO and DM areas in a PLC, the event memory can be allocated to DeviceNet slave I/O data,

Controller Link data links, or for other purposes. The event memory can be accessed by using FINS commands. An example is given below.

Event memory

Input area 1

Node 1 inputs

1 word

Node 2 inputs

1 word

Output area 2

Node 11 outputs

1 word

Node 12 outputs

1 word

DeviceNet

Slave 1 Slave 2 Slave 11 Slave 12

It would be possible to read or write the I/O data for more than one DeviceNet slave using a single FINS command

Event memory

2-3

Data Link

Table

Node 1

CIO 0 to

CIO 9

Node 2

CIO 10 to

CIO 19

Data link words are allocated in event memory according to settings for the data link tables. The Controller Link Support Software is used to set the Data Link

Tables.

NP Functions and Precautions

The network providers (NPs) are software components that provide the software functions for networks just like Communications Units do for PLCs. Data can be read and written by addressing FINS commands to the NPs or by addressing FINS commands to CPU_UNIT and sending them through an NP.

The FINS commands that can be addressed to each NP and the precautions for the NP are described next.

12

NP Functions and Precautions

2-3-1 ETN_UNIT

FINS Commands

Addressed to ETN_UNIT

Section 2-3

ETN_UNIT is a software component that functions like a Communication Unit to connect to an Ethernet network.

The following FINS commands can be addressed to ETN_UNIT.

Command code

05 01

27 50

27 60

27 65

CONTROLLER DATA READ

Name

IP ADDRESS TABLE WRITE

IP ADDRESS TABLE READ

ADDRESS DATA READ

Precautions

The IP address of the Open Network Controller is set in software. Refer to

4-3-6 SYSTEM SETUP

. The default address is 10.0.0.1 with a subnet mask of

255.0.0.0.

FINS communications use the UDP protocol. Confirm the reception of FINS command by processing the FINS responses in the application program.

FINS communications will not be possible with nodes that are not registered in the IP address table. The address of the destination node must be registered in the IP address tables of both nodes involved in FINS communications.

The IP fragmentation queue in the Open Network Controller can contain up to

200 entries. Each buffer is 4 Kbytes.

FINS node address 255 cannot be used for IP broadcast transmissions.

2-3-2 HLK_UNIT

Supported Serial

Communications

Protocols

Applicable FINS

Commands and

Applicable PLCs

HLK_UNIT is a software component that converts FINS commands to the following communications protocols.

The following three serial communications protocols are supported.

C-series Host Link (SYSMAC WAY)

CV-series Host Link (SYSMAC WAY)

CompoWay/F

HLK_UNIT converts FINS commands to commands in the above protocols. This function enables FINS message communications between personal computers and other devices on the Ethernet network and the following devices, including

OMRON FA components that support the CompoWay/F protocol and the following OMRON PLCs.

PLCs that do not directly support FINS commands, e.g., the CQM1, SRM1,

C1000H, C2000H, and C20P.

Temperature Controllers (e.g., the E5CN) and Intelligent Signal Processors on a CompoWay/F network, which previously could not connect to personal computers and other devices on Ethernet networks.

The FINS commands supported by each protocol and the applicable PLCs are given below.

13

NP Functions and Precautions

Section 2-3

C-series Host Link Protocol

FINS Commands

Command code

01 01

01 02

04 01

04 02

05 01

06 01

08 01

22 0F

22 10

22 11

23 01

23 02

Name

READ MEMORY AREA

WRITE MEMORY AREA

RUN

STOP

CONTROLLER DATA READ

CONTROLLER STATUS READ

LOOPBACK TEST

FILE MEMORY INDEX READ

FILE MEMORY READ

FILE MEMORY WRITE

FORCED SET/RESET

FORCED SET/RESET CANCEL

Applicable PLCs

The following PLCs support the C-series Host Link protocol. (Not all of the above

FINS commands are supported by each of the PLCs.)

C20, C50, C120, C120F, C20H/C28H/C40H/C60H,

C20P/C28P/C40P/C60P, C20PF/C28PF/C40PF/C60PF, C500, C500F,

C1000H, C1000HF, C2000H, C200H, C200HS, C200HX/HG/HE, CQM1,

CPM1, CPM1A, CPM2A, CPM2C, SRM1, CV500, CVM1, CV1000,

CV2000, and CS1.

14

NP Functions and Precautions

Section 2-3

CV-series Host Link Protocol

FINS Commands

Command code

01 01

02

02

03

04

05

01

03

04

06

07

08

01

02

02

03

04

05

05

06

07

09

0C

21

22 01

02

03

04

02

03

01

02

03

01

02

20

01

01

02

01

20

23

09

0A

0B

0C

05

06

07

08

01

02

Name

MEMORY AREA READ

MEMORY AREA WRITE

MEMORY AREA FILL

MULTIPLE MEMORY AREA READ

MEMORY AREA TRANSFER

PARAMETER AREA READ

PARAMETER AREA WRITE

PARAMETER AREA CLEAR

PROGRAM AREA PROTECT

PROGRAM AREA PROTECT CLEAR

PROGRAM AREA READ

PROGRAM AREA WRITE

PROGRAM AREA CLEAR

RUN

STOP

CONTROLLER DATA READ

CONNECTION DATA READ

CONTROLLER STATUS READ

CYCLE TIME READ

CLOCK READ

CLOCK WRITE

MESSAGE READ (MESSAGE CLEAR, FAL/FALS READ)

ACCESS RIGHT ACQUIRE

ACCESS RIGHT FORCED ACQUIRE

ACCESS RIGHT RELEASE

ERROR CLEAR

ERROR LOG READ

ERROR LOG CLEAR

FILE NAME READ

SINGLE FILE READ

SINGLE FILE WRITE

MEMORY CARD FORMAT

FILE DELETE

VOLUME LABEL CREATE/DELETE

FILE COPY

FILE NAME CHANGE

FILE DATA CHECK

MEMORY AREA FILE TRANSFER

PARAMETER AREA FILE TRANSFER

PROGRAM AREA FILE TRANSFER

FORCED SET/RESET

FORCED SET/RESET CANCEL

Applicable PLCs

The following PLCs support the CV-series Host Link protocol. (Not all of the above FINS commands are supported by each of the PLCs.)

CVM1 and CV-series PLCs

15

NP Functions and Precautions

Precautions

Section 2-3

CompoWay/F Protocol

Applicable Commands

The commands that can be used depend on the CompoWay/F component. Refer to the operation manuals for the components.

Refer to

5-4 FINS Commands Addressed to HLK_UNIT

for information on sending FINS commands to CompoWay/F components.

Applicable Models

Commands can be sent to any component that supports the CompoWay/F protocol.

Slave-initiated (i.e., PLC-initiated) communications using FINS commands are not possible with HLK_UNIT.

2-3-3 DRM_UNIT

DeviceNet

Communications

Methods

Allocating Event Memory

Explicit Messages

DRM_UNIT is a software component that functions like a Communication Unit to connect to a DeviceNet network.

Any of the following three methods can be used to communicate between personal computers and other devices on an Ethernet network and devices on the

DeviceNet network.

Allocate DeviceNet remote I/O data to event memory and read/write event memory.

Send/receive FINS messages to/from devices on the DeviceNet network (only for devices that support FINS). (Not all FINS communications functions are supported for all devices (e.g., CS1-series PCs).

Send explicit messages to devices on the DeviceNet network.

If DeviceNet remote I/O is allocated in event memory, personal computers and other devices on an Ethernet network can access remote I/O data by reading/ writing event memory.

Input area 1

Input area 2

Output area 1

Output area 2

Event memory

128 wds max.

128 wds max.

128 wds max.

512 words max.

128 wds max.

Up to two input areas and two outputs areas can be allocated in event memory.

Each area can contain up to 128 words, for a maximum of 256 input words and

256 output words.

Allocations can be made for a maximum of 63 nodes and up to 32 words (64 bytes) can be allocated per node in each area.

Allocated words are refreshed periodically and the refresh interval can be specified in increments of 1 ms. (The refresh interval must be greater than the communications cycle time. Refer to

4-7-5 DeviceNet NP Settings

for details.)

Allocation and refresh settings are made in the following two files. Refer to

4-7-2

Ethernet Settings

onwards for setting methods.

FgwQnxDrm.ini:Event memory allocations scanlist.ini: Scan list settings

In addition to the I/O areas, can also be allocated as a 81 words status area. Refer to

DeviceNet Status Area Contents

under

4-6-7 DRM_UNIT

Settings for details

.

FINS command code 2801 can be used to send explicit messages to devices on the DeviceNet network. This function enables communications with the master

16

NP Functions and Precautions

FINS Commands

Addressed to DRM_UNIT

Precautions

Section 2-3

and slaves on the DeviceNet network. The Open Network Controller converts explicit messages returned from the DeviceNet devices to FINS responses.

The following FINS commands can be addressed to DRM_UNIT.

Command code

04 01

04 02

04 03

05 01

08 01

28 01

RUN

STOP

RESET

CONTROLLER DATA READ

LOOPBACK TEST

EXPLICIT MESSAGE SEND

Name

I/O areas and the status areas must be set so that they do not use words allocated to other purposes.

The longest FINS message beginning with ICF exchanged between DeviceNet networks has 507 bytes.

2-3-4 CLK_UNIT

FINS Commands

Addressed to CLK_UNIT

Allocating Event Memory

CLK_UNIT is a software component that functions like a Communication Unit to connect to a Controller Link network through a Controller Link Support Board.

The following FINS commands can be addressed to CLK_UNIT (i.e., to the Controller Link Support Board). Data link areas are set using the Controller Link Support Software.

Command code

04

05

06

08

21

03

02

03

01

02

03

01

02

01

02

01

Data links

OK

OK

OK

OK

OK

Active

No

OK

OK

OK

OK

OK

OK

OK

Stopped

OK

No

OK

OK

OK

OK

OK

OK

OK

Name

RUN

STOP

CONTROLLER DATA READ

CONTROLLER STATUS READ

NETWORK STATUS READ

DATA LINK STATUS READ

LOOPBACK TEST

BROADCAST TEST RESULTS

READ

BROADCAST TEST DATA SEND

ERROR LOG READ

ERROR LOG CLEAR

If data link areas are allocated in event memory, the Open Network Controller can participate in the data links on the Controller Link Network, and personal computers and other devices on an Ethernet network can access remote data link areas by reading/writing event memory. In the Open Network Controller, the

CIO and DM areas can be used to create data link areas.

Data link area are set using the Controller Link Support Software.

Event memory

Data Link

Table

Node 1

CIO 0 to

CIO 9

Node 2

CIO 10 to

CIO 19

17

NP Functions and Precautions

Section 2-3

Precautions

Data link areas must be set so that they do not use words allocated to other purposes.

The refresh interval from the data link memory on the Controller Link Support

Board to event memory is 100 ms.

To use the Controller Link Board without changing the factory settings of the

Open Network Controller, set the memory address of the Controller Link Board to $DA00 (i.e., set DIP switch pin 2 to ON and pins 1, 3, and 4 to OFF) and set the interrupt level to 15. This means you must change the factory settings of the Controller Link Board.

2-3-5 SYSMAC_UNIT

SYSMAC_UNIT is a software component for connecting a SYSMAC Board. As shown in the following diagram, SYSMAC_UNIT and the SYSMAC Board are treated as separate nodes on the FINS network. This is not true for CLK_UNIT and the Controller Link Support Board.

Open Network Controller Open Network Controller

FINS Commands

Addressed to

SYSMAC_UNIT

FINS Commands

Addressed to SYSMAC

Board

Local node

Virtual network

Separate node

(ISA bus)

SYSMAC Board

Local node

(1 node)

Controller Link Board

Network

Separate node

The FINS commands supported by SYSMAC_UNIT and the SYSMAC Board are not the same, as shown in the following tables.

The following FINS commands can be addressed to SYSMAC_UNIT.

Command code

05 01 CONTROLLER DATA READ

Name

The following FINS commands can be addressed to the SYSMAC Board.

05

06

07

Command code

01 01

04

02

01

02

01

01

01

02

MEMORY AREA READ

MEMORY AREA WRITE

RUN

STOP

CONTROLLER DATA READ

Name

CONTROLLER STATUS READ

CLOCK READ

CLOCK WRITE

Allocating Event Memory

Event memory

10 words 10 words

SYSMAC

Board

Inputs

10 words

Outputs

10 words

18

NP Functions and Precautions

Precautions

Section 2-3

The default setting for the startup mode for the SYSMAC Board when power is turned ON is for the startup mode to be determined by settings in the SYSMAC

Board.

One ladder program cycle in the SYSMAC Board is required for every line set in the event memory map.

To use the SYSMAC Board without changing the factory settings of the Open

Network Controller, use the I/O port address of the SYSMAC Board set to $3A0

(i.e., the factory-set value).

19

SECTION 3

Hardware

This section provides information on the hardware components, installation, and settings of the Open Network Controller.

3-1

3-2

3-3

3-4

3-5

3-6

3-7

3-8

3-9

Nomenclature and Functions

3-1-1

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Component Names and Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-1-2 Indicator and 7-segment Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

DIP Switch Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Mounting Expansion Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Installing the Open Network Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-4-1 Orientation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-4-2

3-4-3

3-4-4

Mounting Dimensions

Installation with Screws

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Installation on DIN Track . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Connecting the Power Supply Cable

3-5-1 Connecting the Cable

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-5-2 Wiring the Ground . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Connecting COM Port Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-6-1

3-6-2

Terminal Connections to COM1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Host Link (SYSMAC WAY C/CV) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-6-3 CompoWay/F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Connecting DeviceNet Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-7-1

3-7-2

3-7-3

Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Connecting Communications Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Connecting Communications Cables to T-branch Taps . . . . . . . . . . . . . . . . . . . . .

3-7-4

3-7-5

Connecting Terminating Resistors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Connecting Communications Cables to Nodes

Connecting Ethernet Cables

. . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Handling Memory Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-9-1

3-9-2

3-9-3

Memory Card Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Mounting and Removing Memory Cards

Formatting Memory Cards

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

53

54

57

50

51

52

53

46

46

49

41

42

44

46

39

39

41

41

32

34

36

26

28

31

31

22

22

24

21

Nomenclature and Functions

Section 3-1

3-1 Nomenclature and Functions

This section gives the names and describes the functions of each component of the Open Network Controller.

3-1-1 Component Names and Functions

The names and functions of the Open Network Controller components will be described using the ITNC-EIX01-DRM Expansion Model with DeviceNet as an example. Some models do not have a COM3 port, a connector for DeviceNet communications, or an expansion slot.

DIP switches

DeviceNet communications connector

Backup battery

DeviceNet indicators

Memory

Card slot

Ethernet port

Indicators

Reset switch

7-segment display

Card switch

Card eject button

Card bracket

Power supply terminal block

Expansion slot cover

22

Nomenclature and Functions

Section 3-1

Name

DIP switches

Backup battery

Power supply terminal block

Ethernet port

COM1

COM2

COM3 (only with

Expansion models)

Expansion slot cover

(ITNC-EIX01 and

ITNC-EIX01-DRM only)

Indicators

7-segment display

Memory Card slot

Card bracket

Card switch

Card eject button

DeviceNet indicators

DeviceNet communications connector

(ITNC-EIS01-DRM and

ITNC-EIX01-DRM only)

Function

The DIP switches are used to make COM port and

7-segment display settings.

The backup battery backs up the real-time clock and the CMOS RAM. Replace with a C500-BAT08 Battery when required.

The power supply terminal block connects to a

24-V DC power supply.

An Ethernet cable for 10Base-T is connected to the

Ethernet port.

RS-232C

RS-232C

RS-422A/485

The expansion slot is an ISA bus slot. Remove the cover to mount a Controller Link or SYSMAC Board.

The indicators show the status of Open Network

Controller operation.

The 7-segment display shows the error code, IP address, MAC ID on the DeviceNet network, or the

FINS address, according to the DIP switch settings.

A Memory Card is mounted in this slot.

This bracket holds the Memory Card in place. Be sure to secure the Card with this bracket.

Press the card switch when inserting or removing a

Memory Card.

When inserting a Memory Card, press this switch to enable using the card. The CARD indicator will light.

When removing the Memory Card, press this switch to enable removing the card. The CARD indicator go out.

Press the card eject button to remove the Memory

Card. Before pressing this button, press the card switch and make sure the CARD indicator is not lit.

These indicators show the status of the DeviceNet network.

A DeviceNet cable is connected to this connector.

23

Nomenclature and Functions

3-1-2 Indicator and 7-segment Displays

Section 3-1

Indicators

Seven-segment Display

Name

POWER

RUN

ERR

LAN

COM1

COM2

COM3

CARD

Color

Green

Green

Red

Orange

Orange

Orange

Orange

Orange

Green

Meaning

Lit when the power supply is ON.

Lit when the FinsGateway is running.

Lit when an error occurs or flashes when the battery voltage is low.

Lit when an Ethernet cable is connected.

Flashes during transmission.

Lit during COM1 data transmission.

Lit during COM2 data transmission.

Lit during COM3 data transmission (Expansion models only).

Lit when the Memory Card is being accessed.

The Memory Card cannot be inserted or removed while the CARD indicator is lit. Remove or insert the card only when the indicator is not lit.

Lit when the Memory Card is being used.

The Memory Card cannot be inserted or removed while the CARD indicator is lit. Remove or insert the card only when the indicator is not lit.

7-segment display (2 digits)

The 7-segment display shows the error code, IP address, MAC

ID on the DeviceNet network, or the FINS address, according to the DIP switch settings.

The 7-segment display shows alphanumeric characters. The alphabet characters that are displayed are shown below.

24

Nomenclature and Functions

DeviceNet Indicators

Section 3-1

Indicator

MS

NS

---

Color

Green

Red

---

Green

Red

Status

Not lit

Lit

Flashing

Flashing

Lit

Not lit

Lit

Flashing

Flashing

Lit

No power supply.

Meaning

Normal.

Starting up.

Fatal error. Replace the Board.

Fatal error. Replace the Board.

Offline.

Normal communications.

Online but no connection established.

Communications error, no slaves, or I/O size mismatch.

Communications impossible.

Note

When indicators flash, the duration the indicator is lit and then not lit is approximately 5 s each.

Refer to

7-2 DeviceNet Indicator Displays

for information on troubleshooting with the indicators.

25

DIP Switch Settings

Section 3-2

3-2 DIP Switch Settings

The following settings are made on pins 1 to 4 of DIP switch 2.

COM1 port settings (selection of whether to login from COM1 or to use COM1 as a Host Link port) (Pin 1)

Seven-segment display settings (pins 2 and 3)

Resetting to default setting (pin 4)

Do not change any pins on DIP switch 1 or pins 5 to 8 on DIP switch 2.

Note

DIP switch settings must be made when the power is turned OFF.

Opening the Battery

Cover

To make the DIP switch settings, first open the battery cover.

DIP switch 2

COM1 Port Settings

(DIP Switch 2, Pin 1)

DIP switch 1

Note

Do not change DIP switch 1 settings.

COM1 port settings are shown in the following table.

Note

DIP

Switch 2,

Pin 1

ON

OFF

Function

Enables login from COM1 port. FinsGateway will not be started.

Disables login from COM1 port.

1. Turn ON DIP switch 2, pin 1 to login from COM1 port and make Open Network Controller settings. Once the settings have been completed, turn OFF pin 1 to use COM1 as a Host Link port.

2. Login from the Ethernet port is always possible, regardless of the setting at

DIP switch 2, pin 1.

26

DIP Switch Settings

Section 3-2

Seven-segment Display

(DIP Switch 2, Pin 2 and

Pin 3)

The settings for 7-segment display are shown on the following table. If the settings are changed while the power is ON, the display will change to the new settings once the display under the old settings has been completed.

DIP

Switch 2,

Pin 2

OFF

ON

OFF

ON

DIP

Switch 2,

Pin 3

OFF

OFF

ON

ON

Display

Displays the error code when an error occurs. The

7-segment display is not valid unless the ERR indicator is lit. Refer to

7-1 Error Messages

for details.

Displays the IP address for the Open Network Controller in hexadecimal.

The display will be “IP” then, at approx. 1 s intervals, 8 bits at a time of the 32-bit IP address.

For example, for an IP address of 192.168.1.13, the display would be “IP”, “C0”, “A8”, “01”, then “0D”.

Displays the DeviceNet MAC ID.

Displays the FINS address.

The name, network address, node address, and unit address of NPs currently operating will be displayed, in order, at approx. 1 s intervals.

The first two letters of the NP names will be displayed, as shown below, and the addresses will be displayed in hexadecimal.

ET: ETN_UNIT (Ethernet NP)

SY: SYSMAC_UNIT (SYSMAC Board connection NP)

CL: CLK_UNIT (Controller Link NP)

HL: HLK_UNIT (C-mode and CV-mode Host Link

(SYSMAC WAY) and CompoWay/F NP)

DR: DRM_UNIT (DeviceNet NP)

Return to Default

Settings

(DIP Switch 2, Pin 4)

This setting is read only when the Open Network Controller is started.

DIP

Switch 2,

Pin 4

ON

OFF

Function

Returns all settings files to the default settings.

Starts up using the user-defined settings files.

Note

When the Open Network controller is started with pin 4 ON, all settings files will be overwritten. Make sure that it is OK to overwrite the current settings files before turning ON DIP switch 2, pin 4. About 40 seconds are required to finish this operation. Turn OFF the Open Network Controller only after the RUN indicator starts flashing.

The procedure for starting the Open Network Controller with the default settings is shown below.

1, 2, 3...

1. Turn ON DIP switch 2, pin 4.

2. Turn ON the power supply to the Open Network Controller. The RUN indicator will start flashing when all settings files have been returned to the default settings.

3. Check that the RUN indicator is flashing and then turn OFF the power supply to the Open Network Controller.

4. Turn OFF DIP switch 2, pin 4.

5. Turn ON the power supply to the Open Network Controller again. The Open

Network Controller will start up with the default settings.

27

Mounting Expansion Boards

3-3

Section 3-3

Mounting Expansion Boards

One of the following Boards can be mounted in the ITNC-EIX01 Expansion Model or the ITNC-EIX01-DRM Expansion Model with DeviceNet.

3G8F5-CLK21 Controller Link Board

C200PC-ISA -DRM or C200PC-ISA -SRM SYSMAC Board

The mounting method will be explained using the SYSMAC Board as an example, but the method is the same for Controller Link Boards.

Note

1, 2, 3...

1. Turn OFF the power supply before mounting an Expansion Board.

2. To use the Expansion Board without changing the factory settings of the

Open Network Controller, keep the following conditions.

Set the I/O port address of the SYSMAC Board to $3A0 (i.e., the factoryset value).

Set the memory address of the Controller Link Board to $DA00 (i.e., set

DIP switch pin 2 to ON and pins 1, 3, and 4 to OFF) and interrupt level to 15.

This means you must change the factory settings of the Controller Link

Board.

Turn OFF the power supply before mounting the Expansion Board.

1. Remove the expansion slot cover.

28

Mounting Expansion Boards

Section 3-3

2. Remove the back cover from the Controller, the Expansion Board bracket, and the dummy panel.

Bracket

Dummy panel

Remove 4 mounting screws on the rear cover of the Controller.

3. Insert the Expansion Board. Firmly insert the Expansion Board into the connector inside the Open Network Controller.

29

Mounting Expansion Boards

Section 3-3

4. Replace the back cover of the Controller and then secure the Expansion

Board in place using the bracket and mounting screws.

5. Replace the expansion slot cover and tighten the screws.

30

Installing the Open Network Controller

Section 3-4

3-4 Installing the Open Network Controller

This section explains how to install the Open Network Controller.

3-4-1 Orientation

The Open Network Controller can be installed in any of the four ways shown in the following diagram. It can be installed either directly to a surface with screws or to DIN Track. In either case, it can be installed horizontally or vertically. Do not install the Open Network Controller in any other way.

Up

Front

Installed horizontally with screws

Installed vertically with screws

Down

Installed horizontally on DIN Track

Installed vertically on

DIN Track

!

Caution

Do not install the Open Network Controller in any of the following orientations.

Up

Down

Do not install the Open

Network Controller so that it is flat, i.e., horizontal with the ground.

X

!

Caution

Install the Open Network Controller only in the orientations indicated. Also, always leave at least 50 mm for ventilation above, below, to the right, to the left, and to the front of the Controller. If the installation orientation is incorrect or there is insufficient ventilation space, the internal temperature of the Controller will increase and the Controller may malfunction.

Note

Allow enough space to insert and remove connectors, cables, and Memory

Cards.

31

Installing the Open Network Controller

3-4-2 Mounting Dimensions

ITNC-EIS01 Standard Model and

ITNC-EIS01-DRM Standard Model with DeviceNet

ITNC-EIS01-CST (Standard Model with CS1 Bus Interface)

Unit: mm

Section 3-4

Space required for opening and closing the battery cover

R = 50 mm

ITNC-EIX01 Expansion Model and

ITNC-EIX01-DRM Expansion Model with DeviceNet

ITNC-EIX01-CST (Expansion Model with CS1 Bus Interface)

Top of

DIN Track

Unit: mm

32

Space required for opening and closing the battery cover

R = 50 mm

Top of

DIN Track

Installing the Open Network Controller

ITNC-AP001 Standard

Model Mounting Bracket

Section 3-4

ITNC-AP002 Expansion

Model Mounting Bracket

Unit: mm

Screw

Top of

DIN Track

Top of

DIN Track

Screw

33

Installing the Open Network Controller

Section 3-4

3-4-3 Installation with Screws

This section explains how to install the Open Network Controller by directly screwing it to the mounting surface. DIN Track is not used in this method. The examples use the Expansion Models, but the installation method is the same for the Standard Models.

The M4 screws must be tightened to a torque of 0.9 N

⋅ m.

!

Caution

Install the Open Network Controller only in the orientations indicated. Also, always leave at least 50 mm for ventilation above, below, to the right, to the left, and to the front of the Controller. If the installation orientation is incorrect or there is insufficient ventilation space, the internal temperature of the Controller will increase and the Controller may malfunction.

Horizontal Installation

Use four M4 screws to install the Open Network Controller horizontally.

M4 screws are not supplied with the Controller. A Mounting Bracket (sold separately) is not required.

Vertical Installation

Use the following procedure to install the Open Network Controller vertically.

1, 2, 3...

1. Remove the two screws on the rear of the Controller.

34

Installing the Open Network Controller

Section 3-4

2. Mount the Mounting Bracket on the Open Network Controller, as shown below, and secure in place with the screws removed in the previous step.

Use the ITNC-AP001 Mounting Bracket for Standard Models and the ITNC-

AP002 Mounting Bracket for Expansion Models.

Insert the hooks and then slide the

Mounting Bracket towards you.

3. Use four M4 screws to secure the Open Network Controller in place.

M4 screws are not supplied with the Controller.

35

Installing the Open Network Controller

3-4-4 Installation on DIN Track

Section 3-4

!

Caution

Install the Open Network Controller only in the orientations indicated. Also, always leave at least 50 mm for ventilation above, below, to the right, to the left, and to the front of the Controller. If the installation orientation is incorrect or there is insufficient ventilation space, the internal temperature of the Controller will increase and the Controller may malfunction.

This section explains how to install the Open Network Controller on DIN Track.

The examples use the Expansion Models, but the installation method is the same for the Standard Models.

The M4 screws must be tightened to a torque of 0.9 N

⋅ m.

Horizontal Installation

1, 2, 3...

1. Use M4 screws to secure the ITNC-DIN01 DIN Track Mounting Brackets to the Open Network Controller, as shown in the following diagram. M4 screws are not supplied with the Controller.

36

The DIN Track Mounting Brackets must point in the direction indicated.

Note

Be sure to attach the DIN Track Mounting Brackets in the correct orientation. If the orientation is incorrect, the Open Network Controller cannot be correctly mounted to the DIN Track.

2. Mount the Open Network Controller to the DIN Track as follows: a) First, insert the bottom edge of the DIN Track into the bottom (the slightly longer groove) of the DIN Track Mounting Bracket.

b) Bring the DIN Track Mounting Bracket parallel with the DIN Track.

Installing the Open Network Controller

Section 3-4

c) Slide the Open Network Controller downwards. The top edge of the DIN

Track will fit into the groove on the top side of the Mounting Bracket.

DIN Track d) Secure the DIN Track Mounting Bracket and the DIN Track in place with the four screws provided.

Vertical Installation

1, 2, 3...

1. Use M4 screws to join the ITNC-DIN01 DIN Track Mounting Brackets and the ITNC-AP001 Mounting Bracket for Standard Models or the ITNC-AP002

Mounting Bracket for Expansion Models together, as shown in the following diagram. M4 screws are not supplied with the Controller.

Attach the Mounting Bracket with these two holes to the left.

The arrows must face in this direction.

Note

Be sure to attach the DIN Track Mounting Brackets in the correct orientation. If the orientation is incorrect, the Open Network Controller cannot be correctly mounted to the DIN Track.

37

Installing the Open Network Controller

2. Remove the two screws on the back of the Controller.

Section 3-4

3. Mount the Mounting Bracket and DIN Track Mounting Bracket joined together to the Open Network Controller and secure them in place with the screws removed in step two.

Insert the hooks and then slide the

Mounting Bracket towards you.

4. Mount the Open Network Controller to the DIN Track as follows: a) First, insert the bottom edge of the DIN Track into the bottom (the slightly longer groove) of the DIN Track Mounting Bracket.

b) Bring the DIN Track Mounting Bracket parallel with the DIN Track.

c) Slide the Open Network Controller downwards. The top edge of the DIN

Track will fit into the groove on the top side of the Mounting Bracket.

DIN Track

38

Connecting the Power Supply Cable

Section 3-5

d) Secure the DIN Track Mounting Bracket and the DIN Track in place with the four screws provided.

3-5 Connecting the Power Supply Cable

3-5-1 Connecting the Cable

This section explains how to connect the power supply cable. The power supply terminal block on the Open Network Controller must have 24-V DC power supplied to it.

1, 2, 3...

1. Open the terminal cover.

39

Connecting the Power Supply Cable

2. Loosen the power supply terminal block screws.

Section 3-5

3. Connect power supply cables and ground line to the power supply terminal block. These cables must have crimp terminals.

Note

Make sure no scrap wire gets caught in the terminal block.

1

2

3

Terminal Signal

+24 V DC

0 V

Functional ground terminal

DC Power Supply

Provide a 24-V DC power supply that is within the allowable voltage range

(20.4 to 27.6 V DC).

Power Supply Capacity

Note

The power consumption is 15 W or less for the ITNC-EIS01 Standard Model and

ITNC-EIS01-DRM Standard Model with DeviceNet and 20 W or less for the

ITNC-EIX01 Expansion Model and ITNC-EIX01-DRM Expansion Model with

DeviceNet.

1. Connect crimp terminals to the wires. Do not connect power lines that have simply been twisted together to the terminal block.

2. Tighten the terminal block screws to a torque of 0.8 N

⋅ m.

40

Connecting COM Port Cables

Section 3-6

3. Use either forked or round crimp terminals for M3.5 screws.

Crimp terminals for DC power supply

7 mm max.

7 mm max.

3-5-2 Wiring the Ground

The Open Network Controller has a functional ground terminal. To prevent malfunctions when there is a lot of noise and to prevent electrical shock, use an independent ground line (2 mm

2

min.) and ground to 100

or less. The ground line should be less than 20 m in length.

Noise and other interference can increase if the ground is shared with other devices or connected to the wall of a building.

Use a noise filter to further reduce noise.

Open

Network

Controller

Other device

Open

Network

Controller

Other device

Open

Network

Controller

Other device

Ground to

100

or less

Independent ground

Do not use shared grounds.

Note

Ground the Controller correctly to prevent malfunction due to noise interference.

3-6 Connecting COM Port Cables

This section explains how to connect cables to COM ports 1, 2, and 3.

3-6-1 Terminal Connections to COM1

Use COM1 for connecting terminals to the Open Network Controller. Terminals cannot be connected from other ports.

Open Network Controller

D-sub, 9-pin, female

Connector hood FG

IBM PC/AT or compatible computer

D-sub, 9-pin, female

Connector hood FG

Shield wire

41

Connecting COM Port Cables

3-6-2 Host Link (SYSMAC WAY C/CV)

1:1 Connections Using RS-232C Ports (COM1 or COM2)

Open Network

Controller

Signal Pin

Shell

Section 3-6

Serial

Communications

Board or Unit

Pin Signal

RS-232C

Interface

D-sub, 9-pin

(female cable connection)

D-sub, 9-pin

(male cable connection)

Note

This example shows the connector pin layout for a CS1 Communications Board or Unit. The connector pin layout for other Host Link ports or Units will be different. Refer to the user manual for that device. Use the above signal names for reference when wiring.

1:N Connections Using RS-422A Ports (COM1 or COM2)

Open Network

Controller

Signal Pin Shield wire

D-sub, 9-pin

(female cable connection)

5-V power supply

(+)

(–)

Pin

NT-AL001-E

Signal Signal Pin

D-sub, 9-pin

(male cable connection)

Terminal block

DIP SW

SW1-1: ON

SW1-2: ON (terminating resistance)

SW1-3: OFF

SW1-4: OFF

SW1-5: OFF

SW1-6: OFF

Pin

3G2A9-AL001

Signal Signal Pin

RS-422A/

485

Interface

Shield wire

Pin

Serial

Communications

Board

Signal

RS-422A/

485

Interface

Signal

Pin

Shell

4-wire terminating resistance OFF

D-sub, 9-pin (male cable connection)

Serial

Communications

Board

Pin Signal

RS-422A/

485

Interface

Shield wire

4-wire connections

Terminating resistance ON

Note

1. The Open Network Controller does not have 5-V output. Provide a 5-V power supply to the NT-AL001-E Link Adapter from an external source.

2. This example shows the connector pin layout for a CS1 Communications

Board or Unit. The connector pin layout for other Host Link ports or Units will be different. Refer to the user manual for that device. Use the above signal names for reference when wiring.

42

Connecting COM Port Cables

Section 3-6

1:N Connections Using RS-422A Ports (COM3)

Open Network

Controller

Signal Pin

RS-422A

Shield wire

Pin Signal

3G2A9-AL001

Signal Pin

RS-422A

Interface

Shield wire

Component with

RS-422A/485 communications

(4-wire)

Signal

RS-422A/

485

Interface

D-sub, 9-pin (male cable connection)

Shell

Signal

Pin

D-sub, 9-pin (male cable connection)

Shield wire

Component with

RS-422A/485 communications

(4-wire)

Signal

RS-422A/

485

Interface

Note

1. Some devices have SDA, SDB, RDA, and RDB as well as the signal polarities in the opposite position. Check the polarity before connecting the wires.

2. The terminating resistance setting is made at the jumper pin on the Open

Network Controller, shown below. The default setting is ON.

Jumper pin

43

Connecting COM Port Cables

3-6-3 CompoWay/F

1:N Connections Using RS-422A Ports (COM1 or COM2)

Open Network

Controller

Signal Pin

Shield wire

Shell

Pin

NT-AL001-E

Signal Signal Pin

RS-422A

Shield wire

D-sub, 9-pin (female cable connection)

5-V power supply

(+)

(–)

D-sub, 9-pin

(male cable connection)

Terminal block

DIP SW

SW1-1: ON

SW1-2: ON (terminating resistance)

SW1-3: OFF (4-wire)

SW1-4: OFF (4-wire)

SW1-5: OFF

SW1-6: OFF

Component with

RS-422A/485 communications

(4-wire)

Signal

RS-422A/

485

Interface

Component with

RS-422A/485 communications

(4-wire)

Signal

RS-422A/

485

Interface

Open Network

Controller

Signal Pin

Shell

Shield wire

Pin

NT-AL001-E

Signal Signal Pin

Component with

RS-422A/485 communications

(2-wire)

Signal

RS-422A/

485

Interface

D-sub, 9-pin (female cable connection)

5-V power supply

(+)

(–)

D-sub, 9-pin

(male cable connection)

Terminal block

DIP SW

SW1-1: ON

SW1-2: ON (terminating resistance)

SW1-3: OFF (2-wire)

SW1-4: OFF (2-wire)

SW1-5: OFF

SW1-6: OFF

Component with

RS-422A/485 communications

(2-wire)

Signal

RS-422A/

485

Interface

Section 3-6

Note

The Open Network Controller does not have 5-V output. Provide an 5-V DC power to the NT-AL001-E Link Adapter from an external source.

44

Connecting COM Port Cables

1:N Connections Using RS-485 Ports (COM3)

Open Network

Controller

Signal Pin

Section

Component with

RS-422A/485 communications

(2-wire)

Signal

RS-422A/

485

Interface

3-6

D-sub, 9-pin (male cable connection)

Shell

Component with

RS-422A/485 communications

(2-wire)

Signal RS-422A/

485

Interface

1:N E5CN/GN-series

Connections Using

RS-485 Ports (COM1 or

COM 2)

Note

Some devices have SDA, SDB, RDA, and RDB as well as the signal polarities in the opposite position. Check the polarity before connecting the wires.

The method for making a E5CN/GN-series connection using a SEKISUI SI-30A

Adaptor is shown below. Pin 4 on the SI-30A’s DIP switch must be turned ON.

Open Network

Controller

Signal Pin Pin Signal

RS-485

Interface

Connection is not required when pin

4 is ON (auto).

Refer to the SI-30A manual for information on connection from the SI-30A Adaptor.

45

Connecting DeviceNet Cables

Section 3-7

3-7 Connecting DeviceNet Cables

This section explains how to connect DeviceNet cables to the Open Network

Controller.

3-7-1 Connectors

Model

MSTB2.5/5-ST5.08AU

XW4B-05C1-H1-D

XW4B-05C4-T-D

Specifications

For node connections.

Connector screws not supplied.

For node connection and

T-branch Tap connection.

Connector screws supplied with

ITNC-EIS01-DRM and

ITNC-EIX01-DRM

Models.

For multi-drop node connections.

Connector screws not provided.

Manufacturer

Phoenix Contact

Product No.: 1752399

OMRON

OMRON

3-7-2 Connecting Communications Cables

This section explains how to prepare and connect the communications cables to connectors for the DeviceNet Network.

Use the following procedure to prepare and connect the communications cables to the connectors. Although some connectors are equipped with set screws and some are not, the methods used to connect the cables to the connectors are the same.

1, 2, 3...

1. Remove about 30 mm of the cable covering, being careful not to damage the shield weaving underneath. Do not remove more than about 30 mm; removing too much of the covering can result in short circuits.

About 30 mm

2. Carefully peel back the weaving. You will find the signal lines, power lines, and the shield wire. The shield wire will be loose on the outside of the other lines, but it is harder than the weaving and should be easily identified.

Shield wire

3. Remove the exposed weaving, remove the aluminum tape from the signal and power lines, and strip the covering from the signal and power lines to the

46

Connecting DeviceNet Cables

Section 3-7

proper length for the crimp terminal connectors. Twist together the wires of each of the signal and power lines.

Strip to match the crimp terminals

4. Attach the crimp terminals to the lines and then cover any exposed areas of the cable and lines with electricians tape or heat-shrinking tubes.

5. Orient the connector properly, loosen the line set screws, and then insert the lines in order: Black, blue, shield, white, and then red. The wiring method is the same regardless of whether or not the connector is equipped with set screws.

Connector with Set Screws

Black (–V)

Blue (CAN low)

Shield

White (CAN high)

Red (+V)

Note

Be sure the line set screws are sufficiently loosened before attempting to insert the lines. If these screws are not loose, the lines will enter the gaps in the back of the connector and will not lock properly.

There are colored stickers provided on the Master and Slaves that match the colors of the lines to be inserted. Be sure that the colors match when wiring the connectors. These colors are as follows:

Black

Blue

Color

---

White

Red

Signal

Power line, negative voltage (–V)

Communications line, low (CAN low)

Shield

Communications line, high (CAN high)

Power line, positive voltage (+V)

6. Tighten the line set screws for each line in the connector. Tighten the screws to 0.25 to 0.3 N

@ m.

47

Connecting DeviceNet Cables

Section 3-7

You will not be able to tighten these screws with a normal screwdriver, which narrows to a point at the end. You will need a screwdriver that is consistently thin for the entire length.

Use a flat-blade screwdriver that is consistently thin at the end.

Note

The following screwdriver is available from OMRON.

Model Number: XW4Z-00C

Front Side

Multi-drop Connections with Accessory

Connector (Thin Cables

Only)

0.6 mm 3.5 mm

The connectors provided with the Controllers can be used for a multi-drop connection as long as thin cables are being used, just insert both lines into the same hole in the connector. Be sure to use crimp connectors on both lines.

Multi-drop Connections with Special Connector

(Thin or Thick Cables)

A multi-drop wiring connector (sold separately) can be used to wire a multi-drop connector for either thin or thick cables. This multi-drop wiring connector is required to wire a multi-drop connection with thick cables, which are too thick for two lines to fit into the connector provided with the Controllers.

The multi-drop wiring connector cannot always be used with Master Units or the

CQM1 I/O Link Units because it may come into contact with the Units mounted next to the Master Unit or the CQM1 I/O Link Unit. If this happens, use a T-branch

Tap to wire the connection.

48

Connecting DeviceNet Cables

Section 3-7

Note

1. Before connecting the communications cables, turn OFF the power supply to all PCs, Slaves, and communications power supplies.

2. Use crimp terminals for wiring. Connecting bare twisted wires can cause the cables to come off, break, or short circuit, most likely resulting in incorrect operation and possible damage to the Units.

3. Use suitable crimp tools and crimping methods when attaching crimp terminals. Consult the manufacturer of the tools and terminals you are using. Inappropriate tools or methods can result in broken wires.

4. Be extremely careful to wire all signal lines, power lines, and shield wire correctly.

5. Tighten all set screws firmly. Tighten to a torque of 0.25 to 0.3 N

@ m.

6. Wire the signal lines, power lines, and shield wire so that they do not become disconnected during communications.

7. Do not pull on communications cables with excessive force. They may become disconnected or wires may break.

8. Allow leeway so that communications cables do not have to be bent further than natural. The Cables may become disconnected or wires may break if the cables are bent too far.

9. Never place heavy objects on communications cables. They may break.

10. Double-check all wiring before turning ON the power supply.

3-7-3 Connecting Communications Cables to T-branch Taps

This section shows how to connect a communications cable with a connector attached to a T-branch Tap. There are two kinds of T-branch Taps. One makes a single branch and the other makes three branches, but the cable connections are the same for both.

The connectors indicated by asterisks in the following diagrams have the least resistance and these connectors should be used for the trunk line connections.

When using a T-branch Tap on a drop line, we recommend connecting the longest drop line to these connectors.

DCN1-1C

* Use for trunk line or longest drop line.

DCN1-3C

* Use for trunk line or longest drop line.

Align the cable connector with the socket on the T-branch Tap as shown in the following diagram and fully insert the connector into the socket. Tighten the set

49

Connecting DeviceNet Cables

Section 3-7

screws to secure the connection. Tighten the screws to a torque of 0.25 to

0.3 N

@ m.

Note

To avoid damaging the cable or breaking wires, don’t pull on the cable or bend it too sharply when connecting it to the T-branch Tap. Also, never put heavy objects on top of the cable.

3-7-4 Connecting Terminating Resistors

Terminating Resistors must be connected at each end of the trunk line. This section shows how to connect the Terminating Resistors.

T-branch Tap Terminating

Resistor

A terminating resistor is included with the T-branch Tap. Clip the leads on the resistor to about 3 mm and insert it into the T-branch Tap as shown in the following diagram. The resistor can face in either direction.

Terminal-block

Terminating Resistor

A terminating resistor is built into the Terminal-block Terminating Resistor. To connect the cable to the Terminating Resistor, attach standard M3 crimp terminals to the signal wires and securely screw the terminals to the Terminal-block

Terminating Resistor. Tighten to a torque of 0.3 to 0.5 N

@ m.

6.0 mm max.

6.0 mm max.

Note

To avoid damaging the cable or breaking wires, don’t pull on the cable or bend it too sharply when connecting it to the terminal block. Also, never put heavy objects on top of the cable.

50

Connecting DeviceNet Cables

Section 3-7

3-7-5 Connecting Communications Cables to Nodes

This section shows how to connect a communications cable with a connector attached to a Master or Slave.

Align the cable connector with the socket on the node as shown in the following diagram and fully insert the connector into the socket. Tighten the set screws

0.25 to 0.3 N

@ m to secure the connection.

Note

To avoid damaging the cable or breaking wires, don’t pull on the cable or bend it too sharply when connecting it to the terminal block. Also, never put heavy objects on top of the cable.

51

Connecting Ethernet Cables

3-8

Section 3-8

Connecting Ethernet Cables

This section explains how to connect Ethernet cables to the Open Network Controller.

The 10Base-T cable is inserted into the Ethernet connector on the Open Network Controller.

Ethernet port

(Connector model: RJ45)

52

Handling Memory Cards

Section 3-9

3-9 Handling Memory Cards

This section explains how to mount, remove, and format Memory Cards. The

Open Network Controller supports Memory Cards formatted in MS-DOS or

QNX.

3-9-1 Memory Card Models

Use OMRON Memory Cards for CS1-series PLCs.

Model

HMC-EF372

HMC-EF672

HMC-EF282

HMC-EF582

Specifications

30 MB

64 MB

256 MB

512 MB

Note

1. When using a memory card produced by another manufacturer, check the environmental resistance of the cards.

2. Never turn OFF the power supply to the Open Network Controller while accessing the Memory Card. If the power is turned OFF, the Card may be damaged and become unusable.

Use a HMC-AP001 Memory Card Adaptor when inserting a Memory Card into the PCMCIA slot of a personal computer or other device.

53

Handling Memory Cards

Section 3-9

3-9-2 Mounting and Removing Memory Cards

Note

Always secure the memory card bracket when a Memory Card is inserted. If the bracket is not used, the Memory Card may become dislodged due to vibration or other causes.

1, 2, 3...

1. Loosen the screw on the bracket

2. Insert a Memory Card it into the card slot. Be sure to insert it firmly and in the proper orientation. The Memory Card must have been previously formatted in the QNX or MS-DOS format. (QNX formatting is possible for a Memory

Card in the slot by logging in from Ethernet or a serial connection.)

3. Press the card switch. This prompts the operating system to recognize the

Memory Card and mount it. The CARD indicator will light.

54

Handling Memory Cards

Section 3-9

4. Twist the card bracket to position it over the Memory Card and screw the bracket firmly in place.

Installation Directory

The directory where the Memory Card will be mounted depends on the format.

When the card switch is pressed, the Memory Card will be automatically mounted in one of the following directories.

Format

QNX

MS-DOS

Directory

/hd

/dos/c

Unmounting and

Removing Memory

Cards

Note

This section explains how to unmount and remove the Memory Card.

1. Before removing the Memory Card, always press the card switch and unmount the Card.

2. Check that the CARD indicator is not lit before pressing the card eject button.

1, 2, 3...

1. Loosen the screw on the card bracket and twist the bracket as shown in the diagram.

2. Press the card switch.

When the card switch is pressed, the Memory Card will be automatically unmounted.

55

Handling Memory Cards

The CARD indicator will go out.

Section 3-9

3. Check that the CARD indicator is not lit and press the card eject button.

56

Handling Memory Cards

Section 3-9

3-9-3 Formatting Memory Cards

This section explains how to format a Memory Card in QNX.

1, 2, 3...

1. Insert a Memory Card into the card slot.

Note

Do not press the card switch at this point.

2. Log onto the Open Network Controller via Ethernet or a serial connection.

Refer to

4-2 Logging onto the Open Network Controller

for details.

3. From the console, input the following:

#cardQnxFormat1

s

The screen shown below will be displayed.

Ignore Next Prev 1 2 3 4 Change Delete Boot Unboot Restore Loader Save Quit name

OS type

Start

Cylinder

End

Cylinder

Number

Cylinders Blocks

Size

––>

1.

2.

3.

4.

----------- (------)

----------- (------)

----------- (------)

----------- (------)

Choose a partition by typing the partition number OR moving the pointer with the UP/DOWN arrows.

Then, choose one of the actions on the top line of the screen.

Boot

Size

Loader :

:

7872 Kbytes

QNX

Drive: /dev/hd0

Config: 2 Heads

32 Sectors/track

246 Cylinders

Last cylinder is 245.

4. Press the S Key.

5. From the console, input the following:

#cardQnxFormat2

Press the Card switch to mount the Memory Card. The Memory Card will be automatically mounted on one of the following directories.

QNX

Format

MS-DOS

/hd

Directory

/dos/c

57

SECTION 4

Software Settings

This section describes the various methods that can be used to set the contents of the environment settings files for the Open

Network Controller.

4-1

4-2

4-3

4-4

4-5

4-6

4-7

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Logging onto the Open Network Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-2-1 Using COM1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-2-2 Using Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Using the ONC_wizard Setting Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-3-1

4-3-2

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Starting and Exiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-3-3

4-3-4

Backing Up Settings

Menus

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-3-5

4-3-6

4-3-7

4-3-8

4-3-9

4-3-10

4-3-11

4-3-12

4-3-13

4-3-14

4-3-15

Basic Operating Procedures

SYSTEM SETUP

ETN SETUP

CLK SETUP

HLK SETUP

RUT SETUP exit

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RESOURCE SETUP

FinsGateway SETUP

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SYSMAC SETUP

DeviceNet SETUP

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Making Settings with a vi Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Transferring Settings Files with FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-7-2

4-7-3

4-7-4

4-7-5

4-7-6

4-7-7

4-7-8

Setting File Descriptions

4-6-1 Setting Files

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-6-2

4-6-3

Host IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Host Name and Subnet Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-6-4

4-6-5

4-6-6

4-6-7

IP Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Startup Services and Network Settings

ETN_UNIT Settings

DRM_UNIT Settings

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-6-8

4-6-9

4-6-10

4-6-11

DeviceNet Scan List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Controller Link Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

HLK_UNIT Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Host Link Address Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-6-12

4-6-13

SYSMAC_UNIT Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SYSMAC_UNIT Driver Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-6-14 SYSMAC Board Allocations in Event Memory

Setting Examples

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4-7-1 Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Ethernet Settings

Startup Services

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Ethernet NP Settings

DeviceNet NP Settings

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Scan List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Controller Link NP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

HLK_UNIT Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

99

100

101

102

102

95

96

97

98

84

85

90

90

83

83

84

84

103

103

108

109

110

112

113

77

78

80

81

74

74

76

76

81

82

82

67

68

70

73

63

66

66

66

60

61

61

59

Overview

Section 4-1

4-1 Overview

Editing Settings Files

1, 2, 3...

The software settings for the Open Network Controller, including those for the

NPs, are made by editing settings files. The following four methods can be used.

1. Use the ONC_wizard setting tool on the Open Network Controller.

2. Use the vi editor on the Open Network Controller to edit the settings files directly.

3. Use a text editor on a personal computer to edit the settings files and then transfer the files to the Open Network Controller using FTP.

4. Use the Java setting tool to make the settings

The first two methods are achieved by logging onto the Open Network Controller either by using Telnet via an Ethernet connection or by using a VT100 terminal

(e.g., a HyperTerminal) connected to COM1. The third method requires making

FTP settings in the Open Network Controller, and is not possible by connecting a terminal to COM1.

Refer to

Refer to

4-2 Logging onto the Open Network Controller

4-3 Using the ONC_wizard Setting Tool

for login procedures.

for instructions on using

ONC_wizard.

Refer to

4-4 Making Settings with a vi Editor

and

4-5 Transferring Settings Files with FTP

for FTP procedures.

A Memory Card is required for the fourth method. Download the Web Service

Software version 2.0 and the Java setting tool from the ONC website and install them. Refer to the

Web Service Software Version 2.0 Operation Manual

for operating instructions. (The

Web Service Software Version 2.0 Operation Manual

can also be downloaded from the ONC website.)

Note

Refer to the following Web site for the most recent information on software for

Open Network Controllers.

http://www.plcsoft.ne.jp/it/onc/english/index.html

Settings Files

The following table lists the settings files.

IP addresses

Subnet mask

Host names

Settings File name

/etc/hosts

/etc/netstart

/etc/hosts

/etc/netstart

/iproute

/etc/FgwQnx/FgwQnx.ini

IP routing

Startup services, local and relay network tables, COM port services

ETN_UNIT (Ethernet NP)

CLK_UNIT (Controller Link NP)

SYSMAC_UNIT

(SYSMAC Board connection NP)

SYSMAC_UNIT driver

SYSMAC memory allocations in event memory

DRM_UNIT (DeviceNet NP)

DeviceNet scan list

HLK_UNIT (C-series Host Link,

CV-series Host Link, and

CompoWay/F NP)

Host Link address tables (C-series

Host Link, CV-series Host Link, and

CompoWay/F NP)

/etc/FgwQnx/FgwQnxEtn.ini

/etc/FgwQnx/FgwQnxClk.ini

/etc/FgwQnx/FgwQnxSysmac.ini

/etc/FgwQnx/FgwQnxSysmacDriver.ini

/etc/FgwQnx/FgwQnxSysmacMapping.ini

/etc/FgwQnx/FgwQnxDrm.ini

/etc/FgwQnx/scanlist.ini

/etc/FgwQnx/FgwQnxHlk.ini

/etc/FgwQnx/HlkNetTbl.ini

Note

Refer to

4-6 Settings File Descriptions

for details on the settings files.

60

Logging onto the Open Network Controller

4-2

Section 4-2

Logging onto the Open Network Controller

This section describes how to log onto the Open Network Controller by connecting to COM1 and using a HyperTerminal or by connecting to the Ethernet port and using Telnet.

4-2-1 Using COM1

DIP Switch Settings

This section describes how to log onto the Open Network Controller by connecting to COM1 and using a HyperTerminal. The HyperTerminal is normally provided as an accessory with Windows.

Turn ON pin 1 on DIP switch 2.

Cable Connection

Connect a serial port on the computer with the COM1 port on the Open Network

Controller. One of the following OMRON cables is recommended.

XW2Z-200V (D-sub, 9-pin, female, 2 m)

XW2Z-500V (D-sub, 9-pin, female, 5 m)

Refer to

3-6 Connecting COM Port Cables

.

HyperTerminal Startup and Settings

1, 2, 3...

1. Start the HyperTerminal on your computer.

2. Select

File

and then

Properties

.

A window like the following example from

Windows NT V4 will appear.

Select the COM port connected to the Open Network Controller.

61

Logging onto the Open Network Controller

Section 4-2

3. Set the COM port to which the Open Network Controller is connected (as shown in the above diagram) and click the

Configure

Button. Communications settings will be displayed.

4. Apply the configuration and port settings by clicking the

OK

Button.

5. Be sure the Open Network Controller is physically connected and turn ON the power to the Controller.

6. Select

Call

and then

Connect

from the HyperTerminal. If a normal connection is made, the following message and prompt will appear.

Login

1, 2, 3...

You can log onto the Open Network Controller as

root

using the default password

OMRON

.

1. Input as shown in the following display.

The password will not be displayed when it is input.

This prompt will appear if you have logged in successfully

2. Check the setting of the Open Network Controller terminal by inputting as follows:

62

Logging onto the Open Network Controller

Section 4-2

The environment setting of the Open Network Controller will be displayed.

“TERM=vt100” should be displayed. If it is not, then input as follows:

Changing the Password

1, 2, 3...

The password can be changed using the following procedure.

1. Input “passwd” and press the Enter Key. The following message and prompt will appear.

2. Input the new password and press the Enter Key.

3. Input the new password again and press the Enter Key. If the password is the same both times, the normal prompt will be displayed.

4-2-2 Using Ethernet

This section describes how to log onto the Open Network Controller by connecting to the Ethernet port and using Telnet. Telnet is normally provided as an accessory with Windows.

Cable Connection

Open Network Controller

IP Address Settings

Computer IP Address

Settings

Connect a 10Base-T Ethernet cable to the Ethernet port on the Open Network

Controller. Refer to

3-8 Connecting Ethernet Cables

for information on physically connecting to Ethernet.

The IP address of the Open Network Controller is set to 10.0.0.1 and the subnet mask is set to 255.0.0.0 by default.

If you need to change the IP address of the Controller before using Telnet, connect using the COM1 port and change the addressing using a HyperTerminal.

Refer to

4-3-6 SYSTEM SETUP

for details.

Also set the IP address of the computer. The procedure for Window 95/98 is given next as an example.

63

Logging onto the Open Network Controller

Section 4-2

1, 2, 3...

1. Open the

Network

settings on the control panel and click the

Configuration

tab.

2. Select

TCP/IP

and click the

Properties

Button.

64

Logging onto the Open Network Controller

Section 4-2

3. Click the

IP Address

tab and specify an IP address directly.

Telnet

1, 2, 3...

The following procedure shows how to use Telnet to connect to the Open Network Controller from a Windows computer.

1. Select

Start

and then

Run

.

2. Input as shown in the following diagram.

3. Click the

OK

Button. If a normal connection is made, the following message and prompt will appear.

65

Using the ONC_wizard Setting Tool

Login

Section 4-3

You can log onto the Open Network Controller as

root

using the default password

OMRON

.

Input as shown in the following display.

The password will not be displayed when it is input.

This prompt will appear if you have logged in successfully

The password can be changed if desired. Refer to page 63 for the procedure.

4-3 Using the ONC_wizard Setting Tool

This section describes how to use ONC_wizard to make software settings.

4-3-1 Overview

ONC_wizard

ONC_wizard is a setting tool that will let you change the settings in the settings files using conversational window displays. This provides an easy way to change the contents of settings files without editing them directly or having to transfer them from a computer to the Open Network Controller.

Basic Operation

When ONC_wizard is started, it makes copies of the settings files to create a temporary file (/usr/tmp).

Changes made while using ONC_wizard are actually made in the temporary files.

When

Save Changes and exit

is selected from the Exit Menu after completing settings, the contents of the temporary files will be checked and, if no errors are found, the original files will be overwritten with the contents of the temporary files before ONC_wizard ends.

Any changes in the settings will be made valid the next time the Open Network

Controller is started.

4-3-2 Starting and Exiting

Starting

1, 2, 3...

1. Log onto the Open Network Controller as

root

using one of the methods described in

4-2 Logging onto the Open Network Controller.

2. Enter

ONC_wizard

and press the Enter Key at the prompt. (Inputs are case sensitive.)

ONC_wizard will be started and the following menu will appear.

66

Using the ONC_wizard Setting Tool

Exiting

Section 4-3

1, 2, 3...

1. Select

10. exit

from the Main Menu by entering “10” and pressing the Enter

Key. The following menu will appear.

2. Select

2. Save Changes & exit

from the Exit Menu by entering “2” and pressing the Enter Key.

The contents of the settings will be checked and, if no errors are found, the original settings files will be overwritten with the contents of the temporary files before ONC_wizard ends. The temporary files will be deleted.

If

1. Discard Changes & exit

is selected, the contents of the original settings files will not be changed, the temporary files will be deleted, and

ONC_wizard will end.

If

3. Make Temporary File & exit

is selected, the temporary files will be saved as *.onc in /usr/tmp and ONC_wizard will end. These temporary files can be edited with a vi editor or standard computer text editor to create other settings files.

If

4. MainMenu

is selected, the Main Menu will be displayed.

Setting Errors

The following will be performed if one or more errors are discovered when checking settings.

The errors will be recorded in a SetupErr.txt file in /usr/tmp.

The temporary files containing the errors will be saved (i.e., not deleted).

Use the contents of SetupErr.txt to correct the settings.

Warning Messages

The following type of messages will be displayed on-screen and recorded in the error file when errors are discovered for ONC_wizard and ONC_check errors.

The above messages indicate that required settings are missing. These settings are not set to default values and must be set by the user. If the settings are not required for your application, the above warnings can be ignored.

4-3-3 Backing Up Settings

The following procedure can be used to back up the settings file.

1, 2, 3...

1. Start ONC_wizard.

2. Select

10. exit

from the Main Menu and then

3. Make Temporary File & exit.

Temporary files will be saved as *.onc in /usr/tmp.

3. Transfer the above files to the computer using FTP and store them in a safe location.

67

Using the ONC_wizard Setting Tool

Section 4-3

4-3-4 Menus

Main Menu

1. SYSTEM

2. RESOURCE

4. ETN SETUP

5. CLK SETUP

6. SYSMAC

Usage

Ethernet

FinsGateway

Ethernet i

Controller

SYSMAC d NP

The ONC_wizard menus and the files that they affect are listed in the following table.

Menu item

1. HostName

2. SubnetMask

3. IpRoute

4. Host File

5. exit

1. COM PROCESS COUNT

2. COM1 PROCESS

3. COM2 PROCESS

4. COM3 PROCESS

5. exit

1. StartService

2. UnitID

3. LocalNetworkTable

4. RelayNetworkTable

5. MemoryAliases_DM

6 MemoryAliases_CIO

7 exit

1. NodeID

2. IpTable

3. exit

1. NodeID

2. BaseAddress

3. IRQ

4. SystemSw

5. exit

1. NodeID

2. Startmode

3. SysmacDriver SETUP

4. SysmacMapping

5. exit

Settings

Local node host

Subnet mask

IP router addresses

Host IP addresses

Goes to Main Menu.

Number of COM ports

NP allocation to COM1

NP allocation to COM2

NP allocation to COM3

Goes to Main Menu.

Startup services

Unit addresses

Local network table

Relay network table

DM area settings

CIO area settings

Goes to Main Menu.

FINS node address

FINS node–IP address table

Goes to Main Menu.

Node addresses

Base address display

IRQ display

Baud rate

Goes to Main Menu.

Node address

Startup mode

I/O port address display and mailbox interval

Event memory allocations

Goes to Main Menu.

Settings file

/etc/netstart

/iproute

/etc/hosts

---

---

---

---

---

Q S i i

/etc/FgwQnx/

FgwQnxSysmacDriver.ini

/etc/FgwQnx/

FgwQnxSysmacMapping.ini

---

68

Using the ONC_wizard Setting Tool

Section 4-3

Main Menu

7. DeviceNet

8 HLK SETUP

9 RUT SETUP

10exit

Usage

DeviceNet tti

Menu item

1. NodeID

2. Baudrate

3. Scanlist

4. ScanCycleTime

5. StartScanMode

6 ComErrorStop

Settings

Local MAC ID

Baud rate

Scan list

Scan cycle time

Startup scan mode

7 EventCycleTime

8 InAreaName1

9 InAreaOffset1

10InAreaSize1

11 InAreaName2

12InAreaOffset2

13InAreaSize2

14OutAreaName1

15OutAreaOffset1

16OutAreaSize1

17OutAreaName2

18OutAreaOffset2

19OutAreaSize2

20StatusAreaName

21StatusAreaOffset

22StatusAreaSize

Remote I/O communications handling for communications errors

Event memory refresh interval

Input area 1 area

Input area 1 first word

Input area 1 size

Input area 2 area

Input area 2 first word

Input area 2 size

Output area 1 area

Output area 1 first word

Output area 1 size

Output area 2 area

Output area 2 first word

Output area 2 size

Area for status area

First word of status area

Size of status area

C-series

Li k

CV-series

23exit

1 Set

1

Com2

1 NodeID

2 ComSet

3 TimeOut

Goes to Main Menu.

Node address

Communications parameter

Timeout time tti

Accesses

3 Set

4 RetryCnt

5 NetTblSet

4 exit

6 exit Goes to previous level.

Goes to Main Menu.

Reserved for future development. Cannot be accessed.

1 Discard Changes & exit

2 Save Changes & exit

Number of retries

Host Link address table

3 Make Temporary File & exit

4 MainMenu Goes to Main Menu.

Q

Q

D

D i i

/etc/FgwQnx/scanlist.ini

---

Settings file

i i

/etc/FgwQnx/HlkNetTbl.ini

---

---

---

69

Using the ONC_wizard Setting Tool

Section 4-3

4-3-5 Basic Operating Procedures

This section describes the basic operating procedures used for ONC_wizard.

Menu Selections

To select an item from a menu, input the number of the item after the prompt

(Number Selection) and press the Enter Key.

Scrolling Down

If there are more than 10 items in a display, entering “n” or “next” followed by the

Enter Key will display the next page of the display. These inputs are not case sensitive.

If “n” and the Enter Key are entered above, the following display will appear.

Scrolling Up

70

If the second page of a display is being shown, as in the above example, entering

“p” or “prev” followed by the Enter Key will display the previous page of the display. These inputs are not case sensitive.

Using the ONC_wizard Setting Tool

Section 4-3

Exiting from Setting Displays

If

exit

is displayed on the menu, select it to exit from the display.

If

exit

is not display, “q” or “quit” followed by the Enter Key can be entered to exist. These inputs are not case sensitive.

Input Data

1, 2, 3...

1. Select the number of the item from the menu, e.g., SubnetMask has been selected in the following display.

An entry prompt for the selected item will be displayed.

Entry prompt for the selected item.

2. Input the setting and press the Enter Key.

To delete the setting, press the Enter Key without entering a setting.

If an error is displayed, press any key and repeat the procedure from the beginning.

71

Using the ONC_wizard Setting Tool

Section 4-3

Manipulating Table Data

1, 2, 3...

1. Select the number of the item in the table to be entered or changed. Item 4 has been selected below.

A prompt will appear for input of the selected item.

Input prompt for the selected item.

2. Input the setting and press the Enter Key

If an error is displayed, press any key and repeat the procedure from the beginning.

To delete the setting, press the Enter Key without entering a setting.

If there is more than one page in the table, entering “n” or “next” followed by the Enter Key to display the next page or enter “p” or “prev” followed by the

Enter Key to display the previous page. These inputs are not case sensitive.

72

Using the ONC_wizard Setting Tool

Section 4-3

4-3-6 SYSTEM SETUP

The SYSTEM SETUP Menu is used to make the following settings for Ethernet.

Menu item

1. HostName

2. SubnetMask

3. IpRoute

4. Host File

5. exit

Settings

Local node host

Subnet mask

IP router addresses

Host IP addresses

Goes to Main Menu.

Settings file

/etc/netstart

/iproute

/etc/hosts

---

HostName

SubnetMask

IpRouter

Set the name of the host of the local node. The host name can normally be left at its default setting of

onchost

. This host name must be set as the host name under

4. Host File.

Set the subnet mask for the IP address. Set a subnet mask if required.

Syntax

Set the number of digits required by the class of the IP address.

xxx.xxx.xxx.xxx

Class A

255.0.0.0

Class B

Class C

255.255.0.0

255.255.255.0

The default mask is 255.0.0.0 (class A). If the local IP address is changed, make sure that the subnet mask is set correctly according to the IP address class.

Set the addresses of the IP routers.

Syntax

Set each destination network address and the address of the corresponding IP router with a space separating them.

xxx.xxx.xxx.xxx

xxx.xxx.xxx.xxx

IP router

Destination

Example

Host File

Set each host name and the corresponding IP address. The Open Network Controller does not use DNS.

73

Using the ONC_wizard Setting Tool

Example

Section 4-3

Host File

Always set the IP address of host name of the local node. The default host name of the

Open Network Controller is “onchost.”

Set the IP address and host name of the other nodes as required by the applications. These settings are not necessarily required by the

Controller.

Note

1. The default IP address of the local node is 10.0.0.1.

2. Changes in settings, including changes to IP addresses, will be effected only after the Open Network Controller has been restarted (reset or power cycled).

4-3-7 RESOURCE SETUP

The RESOURCE SETUP Menu is used to allocate processes to the COM ports.

Menu item

1. COM PROCESS

COUNT

2. COM1 PROCESS

3. COM2 PROCESS

4. COM3 PROCESS

5. exit

Settings

Number of COM ports

NP allocation to COM1

NP allocation to COM2

NP allocation to COM3

Goes to Main Menu.

Settings file

/etc/FgwQnx/FgwQnx.ini

---

COM PROCESS COUNT

COM1/2/3 PROCESS

This setting specifies the number of allocated COM ports and should not normally be changed. It is set to 3 by default.

Set the NP to allocate to each COM port. The following NPs can be allocated:

HLK0, HLK1, and HLK2.

4-3-8 FinsGateway SETUP

The FinsGateway SETUP Menu is used to make the following settings for Fins-

Gateway.

Menu item

1. StartService

2. UnitID

3. LocalNetworkTable

4. RelayNetworkTable

5. MemoryAliases_DM

6 MemoryAliases_CIO

7 exit

Settings

Startup services

Unit addresses

Local network table

Relay network table

DM area settings

CIO are settings

Goes to Main Menu.

---

Settings file

StartService

Set the NPs that are to be started. CPU_UNIT and ETN must be set. Set the other NPs according to your hardware configuration.

DRM:

CLK:

Built-in device network

Controller Link Board

SYSMAC0: SYSMAC Board

HLK : C-series Host Link, CV-series Host Link, and CompoWay/F

RUT : For future expansion.

74

Using the ONC_wizard Setting Tool

Example

Section 4-3

UnitID

LocalNetworkTable

Set the unit address of each NP.

CPU_UNIT must be set to unit address 0.

Other NPs can be set within the following ranges.

The NP will not be started unless it is started under

1. StartService

.

ETN:

HLK

CLK:

DRM:

:

1 to 253

1 to 253

16 to 31

1 to 253

SYSMAC0: 1 to 253

Set the local network table. Settings are made in pairs of network numbers and unit addresses. Make one setting for each NP.

Example

RelayNetworkTable

MemoryAliases_DM

Separate each network address and its unit number with a comma.

Set the relay network table for FINS. Input three entries on each line in the following order, separating each with a comma: Destination network address, relay network address, relay node address.

Example

This setting says to go through node 4 of network 1 to get to

FINS network 5.

Set the number of DM words to be used. Up to 32,767 words can be set.

Example

Set up to 32,767 words.

For future expansion. Not currently used.

75

Using the ONC_wizard Setting Tool

MemoryAliases_CIO

Section 4-3

Set the number of CIO words to be used. Up to 8,192 words can be set.

Example

Set up to 8,192 words.

For future expansion. Not currently used.

4-3-9 ETN SETUP

NodeID

IpTable

The ENT SETUP Menu is used to make the following settings for the Ethernet

NP.

Settings file Menu item

1. NodeID

2. IpTable

3. exit

Settings

FINS node address

FINS node–IP address table

Goes to Main Menu.

---

Set the FINS node address for the local node to between 1 and 253.

(Node 255 cannot be used for IP broadcasting.)

Set the IP address corresponding to the FINS node address for each node on the Ethernet network. Set one line for each node containing the node address and then the IP address separated by a comma. Up to 32 nodes can be set.

Example

Set the FINS node address and IP address separated by a comma.

4-3-10 CLK SETUP

NodeID

BaseAddress

IRQ

The CLK SETUP Menu is used to make the following settings for the Controller

Link NP.

Settings file Menu item

1. NodeID

2. BaseAddress

3. IRQ

4. SystemSw

5. exit

Settings

Node addresses

Base address display

IRQ display

Baud rate

Goes to Main Menu.

---

The DIP switch and jumper pin on the Controller Link Board must be set to the setting displayed for the base address and IRQ.

Set the node address of the Controller Link Board to between 1 and 32.

This item displays the base address to which the Controller Link Board must be set. Set the DIP switch on the Controller Link Board to the value displayed here

(0xDA000).

This item displays the IRQ to which the Controller Link Board must be set. Set the jumper pin on the Controller Link Board to the value displayed here (15).

76

Using the ONC_wizard Setting Tool

Section 4-3

SystemSw

Set the baud rate.

1:

2:

3:

500 Kbps

1 Mbps

2 Mbps

Note

Set the baud rate to the same values as the other nodes (e.g., Controller Link

Units) on the Controller Link network.

4-3-11 SYSMAC SETUP

The SYSMAC SETUP Menu is used to make the following settings for the SYS-

MAC Board NP.

Menu item

1. NodeID

2. Startmode

3. SysmacDriver SETUP

4. SysmacMapping

5. exit

Settings

Node address

Startup mode

I/O port address display and mailbox interval

Event memory allocations

Goes to Main Menu.

Settings file

Q S i i

/etc/FgwQnx/

FgwQnxSysmacDriver.ini

/etc/FgwQnx/

FgwQnxSysmacMapping.ini

---

NodeID

Startmode

SysmacDriver SETUP

Set the node address of the SYSMAC Board to between 1 and 253.

Set the startup mode of the SYSMAC Board.

1: MONITOR, 0: Use mode set on Board

Set the execution time interval for the mailbox service. The I/O port address will also be displayed.

Example

SysmacMapping

The I/O port address (display only)

Set the mailbox execution interval in ms.

If the interval is less than the cycle time, the cycle time will be used as the interval.

Note

The DIP switch on the SYSMAC Board must be set to the setting displayed for

I/O port address.

Set allocations of event memory to the SYSMAC Board. The area and first address on the Board are set along with the corresponding area and first address on the Open Network Controller. The transfer size and direction are also specified.

Each line contains an enable setting, the Board memory area code, the first

Board address, the Controller memory area code, the first Controller address, the number of words to transfer, and the direction. Each setting is separated with a comma.

Enable setting: 0 = disable, 1 = enable

Memory area code: 80 = CIO, 82 = DM

Number of words: 1 to 128

Direction setting: 0 = Board to Controller or 1 = Controller to Board)

77

Using the ONC_wizard Setting Tool

Example

Section 4-3

Here, the enable setting is 0, i.e., the allocation is disabled.

The setting indicates the following:

Copy 1 word of data beginning at word

DM 5000 of the DM area (82) on the SYS-

MAC Board to word DM 5000 of the DM area (82) on the Open Network Controller.

4-3-12 DeviceNet SETUP

The DeviceNet SETUP Menu is used to make the following settings for the DeviceNet NP.

Menu item

1. NodeID

2. Baudrate

3. Scanlist

4. ScanCycleTime

5. StartScanMode

6 ComErrorStop

7 EventCycleTime

8 InAreaName1

9 InAreaOffset1

10InAreaSize1

11 InAreaName2

12InAreaOffset2

13InAreaSize2

14OutAreaName1

15OutAreaOffset1

16OutAreaSize1

17OutAreaName2

18OutAreaOffset2

19OutAreaSize2

20StatusAreaName

21StatusAreaOffset

22StatusAreaSize

23exit

Settings

Local MAC ID

Baud rate

Scan list

Scan cycle time

Startup scan mode

Remote I/O communications handling for communications errors

Event memory refresh interval

Input area 1 area

Input area 1 first word

Input area 1 size

Input area 2 area

Input area 2 first word

Input area 2 size

Output area 1 area

Output area 1 first word

Output area 1 size

Output area 2 area

Output area 2 first word

Output area 2 size

Area for status area

First word of status area

Size of status area

Goes to Main Menu.

---

Q

/etc/FgwQnx/scanlist.ini

Q

Settings file

D

D i i i i

NodeID

Baudrate

Scanlist

Set the MAC ID of the local node.

Set the DeviceNet baud rate.

0: 125 kbps, 1: 250 kbps, 2: 500 kbps

Note

The DeviceNet baud rate must be the same for the master and all slaves.

Set the scan list to allocate memory to the DeviceNet slaves.

On DeviceNet, the MAC ID is the same as the FINS node address.

FINS node address 0 is for the local node and cannot be used unless FINS is not used and only event memory is being allocated.

78

Using the ONC_wizard Setting Tool

Section 4-3

The scan list contains the input and output areas, first words, and sizes for each

MAC ID on the DeviceNet network in the format given below. Any line beginning with “#” will be ignored.

Example: 01,1,00,00,1,00,02

Enter the following settings on each line, separating each setting with a comma

(do not omit any zeros except for those in I/O area numbers): MAC ID, input area number, input offset, input size, output area number, output offset, and output area size.

MAC ID

Item

Input area number

Input area offset

Input size

Output area number

Output area offset

Output size

Note

When only explicit messages are going to be used, set the input and output area sizes to 0.

Example

Setting

Set the MAC ID of the slave between 00 and 63. The MAC

ID will be used as the FINS node address.

Set the number specified in the number specified in

/etc/FgwQnx/FgwQnxDrm.ini.

Set the number of bytes. The start of the area will be offset by the set number of bytes from the beginning of the input position specified in /etc/FgwQnx/FgwQnxDrm.ini.

Set the number of bytes between 00 and 64.

Set the number specified in the number specified in

/etc/FgwQnx/FgwQnxDrm.ini.

Set the number of bytes. The start of the area will be offset by the set number of bytes from the beginning of the output position specified in /etc/FgwQnx/FgwQnxDrm.ini.

Set the number of bytes between 00 and 64.

ScanCycleTime

StartScanMode

ComErrorStop

EventCycleTime

InAreaName1

InAreaOffset1

Refer to

4-7-6 Scan Lists

for descriptions of the meaning of the above settings.

Set the time to scan all nodes on the DeviceNet network. If 0 is set, the cycle time will be made as short as possible. The time can be set between 1 and 500 (ms).

The actual scan cycle times can be read from the status area as follows:

5th word: Current time, 6th word: Maximum time, 7th word: Minimum time.

Set the DeviceNet mode to use at startup.

0: Don’t scan, 1: Scan

Set the handling of the scan when a DeviceNet communications error occurs.

0:

1:

Continue the scan for all nodes without errors.

Stop the scan for all nodes.

Explicit message communications will also be stopped.

Set the refresh interval for event memory data between 1 and 10,000 (ms). The refresh interval should be set to a value near the current value of the communications cycle time (see

DeviceNet Status Area

under

4-6-7 DRM_UNIT Settings).

Set the event memory area in which words are to be allocated as input area 1

(inputs from DeviceNet to the event memory). Either CIO or DM can be set.

Set the word in the event memory area to use as the first word of input area 1.

79

Using the ONC_wizard Setting Tool

InAreaSize1

InAreaName2

InAreaOffset2

InAreaSize2

OutAreaName1

OutAreaOffset1

OutAreaSize1

OutAreaName2

OutAreaOffset2

OutAreaSize2

StatusAreaName

StatusAreaOffset

StatusAreaSize

Section 4-3

Set the number of words to be allocated as input area 1 between 0 and 128. If 0 is set, input area 1 will not be allocated in event memory.

Set the event memory area in which words are to be allocated as input area 2

(inputs from DeviceNet to the event memory). Either CIO or DM can be set.

Set the word in the event memory area to use as the first word of input area 2.

Set the number of words to be allocated as input area 2 between 0 and 128. If 0 is set, input area 2 will not be allocated in event memory.

Set the event memory area in which words are to be allocated as output area 1

(outputs from event memory to DeviceNet). Either CIO or DM can be set.

Set the word in the event memory area to use as the first word of output area 1.

Set the number of words to be allocated as output area 1 between 0 and 128. If 0 is set, output area 1 will not be allocated in event memory.

Set the event memory area in which words are to be allocated as output area 2

(outputs from event memory to DeviceNet). Either CIO or DM can be set.

Set the word in the event memory area to use as the first word of output area 2.

Set the number of words to be allocated as output area 2 between 0 and 128. If 0 is set, output area 2 will not be allocated in event memory.

Set the event memory area in which words are to be allocated the DeviceNet status area. Either CIO or DM can be set.

Set the word in the event memory area to use as the first word of the DeviceNet status area.

Set 81 as the number of words to be allocated as the DeviceNet status area. This setting must always be 81 words.

4-3-13 HLK SETUP

The HLK SETUP Menu is used to set COM port communications parameter and the Host Link address table.

Settings file

1 Set

Menu item

1 NodeID

1

2 ComSet

Com2

3 Set

3 TimeOut

4 RetryCnt

5 NetTblSet

6 exit

4 exit

Settings

Node address

Communications parameter

Timeout time

Number of retries

Host Link address table

Goes to previous level.

Goes to Main Menu.

/etc/FgwQnx/HlkNetTbl.ini

---

---

Note

Setting procedures are the same for all the COM ports.

Set the node address of the HLK NP between 1 and 253.

NodeID

80

Using the ONC_wizard Setting Tool

ComSet

Section 4-3

Set the RS-232C communications parameters. Settings are given in the following example.

Example

TimeOut

RetryCnt

NetTblSet

Communications parameters as follows:

Baud rate: 300, 600, 1200, 1800, 2400,

4800, 9600, 19200, 38400, 57600, or

115200

Data length: 5, 6, 7, or 8

Stop bits: 1 or 2

Parity: N = none, E = even, O = odd

Set the timeout time for Host Link responses in ms.

Set the number of retries.

Set the unit address, protocol, and model for each Host Link node in table format. Each entry in the table consists of the following items separated by commas: FINS node address, unit number, protocol, model.

The setting ranges are as follows:

FINS node address:

Unit number:

Protocol:

1 to 253

0 to 255

SYSWAY = C-series Host Link

SYSWAY-CV = CV-series Host Link

Compoway/F = CompoWay/F

Example

Specifies FINS node address 1 as COM2 unit address 1, C-series Host Link protocol, and C200HX.

Specifies FINS node address 2 as COM2 unit address 2, CV-series Host Link protocol, and CVM1.

4-3-14 RUT SETUP

The RUT SETUP Menu is for future expansion and cannot be used.

4-3-15 exit

exit

is used to access the following Exit Menu. Refer to

4-3-2 Starting and Exiting

for details.

Menu item

1 Discard Changes & exit

2 Save Changes & exit

3 Make Temporary File & exit

4 MainMenu

81

Transferring Settings Files with FTP

4-4

Section 4-5

Making Settings with a vi Editor

Use the following procedure to directly edit settings files with a vi editor.

1, 2, 3...

1. Log onto the Open Network Controller.

2. Start ONC_wizard, select

10. exit

from the Main Menu and then select

3. Make Temporary File & exit.

The temporary files will be saved in /usr/ tmp as *.onc.

3. Edit the temporary files using the vi editor.

4. Execute ONC_Check for the temporary files after editing them. If there are no errors in the temporary files, the original settings files will be overwritten with the contents of the temporary files. The temporary files will be deleted.

Setting Errors

The following will be performed if one or more errors is discovered when checking settings.

The errors will be recorded in a SetupErr.txt file in /usr/tmp.

The temporary files containing the errors will be saved (i.e., not deleted).

Use the contents of SetupErr.txt to correct the settings.

Warning Messages

The following type of messages will be displayed on-screen and recorded in the error file when errors are discovered for ONC_wizard and ONC_check errors.

4-5

The above messages indicate that required settings are missing. These settings are not set to default values and must be set by the user. If the settings are not required for your application, the above warnings can be ignored.

Transferring Settings Files with FTP

Use the following procedure to edit settings files with a standard text editor on a computer.

1, 2, 3...

1. Log onto the Open Network Controller.

2. Start ONC_wizard, select

10. exit

from the Main Menu and then select

3. Make Temporary File & exit.

The temporary files will be saved in /usr/ tmp as *.onc.

3. Transfer the temporary files from the Open Network Controller to the computer using FTP in ASCII mode.

4. Edit the temporary files using a standard text editor on the computer.

5. Transfer the temporary files from the computer to the Open Network Controller using FTP.

6. Execute ONC_Check for the temporary files after editing them. If there are no errors in the temporary files, the original settings files will be overwritten with the contents of the temporary files. The temporary files will be deleted.

Setting Errors

The following will be performed if one or more errors is discovered when checking settings.

The errors will be recorded in a SetupErr.txt file in /usr/tmp.

82

Setting File Descriptions

Section 4-6

The temporary files containing the errors will be saved (i.e., not deleted).

Use the contents of SetupErr.txt to correct the settings.

Warning Messages

The following type of messages will be displayed on-screen and recorded in the error file when errors are discovered for ONC_wizard and ONC_check settings.

The above messages indicate that required settings are missing. These settings are not set to default values and must be set by the user. If the settings are not required for your application, the above warnings can be ignored.

4-6 Setting File Descriptions

This section describes the settings files that contain the environment settings for the Open Network Controller. The contents shown for the files in this sections are the default contents.

4-6-1 Setting Files

The setting files are listed in the following table. The default settings of the files and items in the files that can be changed are explained next.

/etc/hosts

/etc/netstart

/iproute

File name

/etc/FgwQnx/FgwQnxEtn.ini

/etc/FgwQnx/FgwQnxDrm.ini

/etc/FgwQnx/scanlist.ini

/etc/FgwQnx/FgwQnxClk.ini

/etc/FgwQnx/FgwQnxHlk.ini

/etc/FgwQnx/HlkNetTbl.ini

/etc/FgwQnx/FgwQnxSysmac.ini

/etc/FgwQnx/FgwQnxSysmacDriver.ini

/etc/FgwQnx/FgwQnxSysmacMapping.ini

Contents

Host IP addresses

Host name

Subnet mask

IP router

Startup services

Local and relay network tables

ETN_UNIT (Ethernet NP)

DRM_UNIT (DeviceNet NP)

DeviceNet scan list

CLK_UNIT (Controller Link NP)

HLK_UNIT (C-series Host Link,

CV-series Host Link, and CompoWay/F

NP)

Host Link address tables (C-series

Host Link, CV-series Host Link, and

CompoWay/F NP)

SYSMAC_UNIT

(SYSMAC Board connection NP)

SYSMAC_UNIT driver

SYSMAC memory allocations in event memory

83

Setting File Descriptions

4-6-2 Host IP Addresses

/etc/hosts contains a table of IP addresses and host names.

Note

The Open Network Controller does not use DNS.

Section 4-6

Always set the IP address of host name of the local node.

The default host name of the Open Network Controller is

“onchost”.

Set the IP address and host name of the other nodes as required by the applications. These settings are not necessarily required by the Controller.

4-6-3 Host Name and Subnet Mask

/etc/netstart contains the host name of the Open Network Controller and the subnet mask. Change the subnet mask in this file when required.

The IP address of the local node will be the IP address set for the host name in

/etc/hosts.

Set the host name.

Set the subnet mask according to the class of the IP address of the Open Network Controller.

4-6-4 IP Router

/iproute contains IP router addresses corresponding to the final network addresses. No settings are required unless IP routing is being used.

This line specifies that the IP router for network address 191.168.36 is 10.0.0.3.

The semicolon must be removed from the beginning of the line for the setting to be effective.

84

Setting File Descriptions

Section 4-6

4-6-5 Startup Services and Network Settings

/etc/FgwQnx/FgwQnx.ini contains the FinsGateway QNX settings, including the startup services and the local/relay network tables (unit addresses and networks). The sizes of the DM and CIO areas are also set.

Set the services to be started.

CPU_UNIT and ETN must always be set.

Set the others according to your hardware configuration.

DRM:

CLK:

Built-in device network

Controller Link Board

SYSMAC0: SYSMAC Board

HLK : C-series Host Link,

CV-series Host Link, and

CompoWay/F

RUT : For future expansion.

85

Setting File Descriptions

Set the unit address of each service.

CPU_UNIT must be set to unit address 0. Other services can be set within the following ranges.

ETN:

HLK

CLK:

:

1 to 253

1 to 253

16 to 31

DRM: 1 to 253

SYSMAC0: 1 to 253

The service will not be started unless it is set as as startup service.

Set the FINS network routing tables. These tables will be downloaded to the Controller Link Board at startup.

Set the local network table. Set the network address and unit address (“Unit ID”) for each NP being used.

Set the relay network table for the FINS network.

Set three items on each line in the following order, separating each with a comma: Final network address, relay network address, relay node address.

For example, (5,1,4) says to go through node 4 of network 1 to get to FINS network 5.

Set the NP to allocate to each COM port.

The default settings are shown at the left. The following NPs can be allocated: HLK0, HLK1, and HLK2.

To allocate nothing to a port, delete the text after the equals sign.

Section 4-6

86

Setting File Descriptions

V1.03

Set the number of words to allocate to the DM area.

Up to 32,767 words can be allocated.

Set the number of words to allocate to the CIO area.

Up to 8,192 words can be allocated.

Section 4-6

87

Setting File Descriptions

Section 4-6

88

Setting File Descriptions

Section 4-6

89

Setting File Descriptions

Section 4-6

4-6-6 ETN_UNIT Settings

/etc/FgwQnx/FgwQnxEtn.ini contains settings for the Ethernet NP.

Set the FINS node address for the local node on the Ethernet network to between 1 and 253.

Set the UDP port number to use for Ethernet as a decimal value. UDP port number 9600 will be used if the setting is omitted.

Normally, 9600 should be used.

Set the IP address corresponding to the FINS node address for each node on the Ethernet network. Set one line for each node containing the node address and then the IP address separated by a comma. Up to 32 nodes can be set.

Settings can be made using host names set in /etc/hosts, e.g.,

(2,oncclient).

Set the IP address to send FINS data to for any destination for which the IP address is not known. This setting is not required.

4-6-7 DRM_UNIT Settings

/etc/FgwQnx/FgwQnxDrm.ini contains settings for the DeviceNet NP.

Set the MAC ID of the local node.

Set the DeviceNet baud rate.

0: 125 kbps, 1: 250 kbps, 2: 500 kbps

Set the time to scan all nodes on the DeviceNet network. If 0 is set, the cycle time will be made as short as possible. The time can be set between 1 and 500 (ms).

The actual scan cycle times can be read from the status area as follows: 5th word: Current time, 6th word: Maximum time, 7th word: Minimum time.

90

Setting File Descriptions

Section 4-6

Set the DeviceNet mode to use at startup.

0: Don’t scan, 1: Scan

Set the handling of the scan when a DeviceNet communications error occurs.

0: Continue the scan for all nodes without errors

Set the refresh interval for event memory data. The interval should be set near the current value of the communications cycle time.

Set the event memory area in which words are to be allocated as input area 1 (inputs from DeviceNet to the event memory).

Set the word in the event memory area to use as the first word of input area 1.

Set the number of words to be allocated as input area 1 between 0 and

128.

Set event memory area, first word, and number of words for input area 2 in the same way as for input area 1.

Set event memory area, first word, and number of words for output area 1 (outputs from event memory to Device-

Net) in the same way as for input area 1.

Set event memory area, first word, and number of words for output area 2 (outputs from event memory to Device-

Net) in the same way as for input area 1.

Set the event memory area in which words are to be allocated as the DeviceNet status area.

Set the word in the event memory area to use as the first word of the DeviceNet status area.

Set 81 as the number of words to be allocated as the

DeviceNet status area. This setting must always be 81 words. Refer to the following pages for details on the status area contents.

91

Setting File Descriptions

DeviceNet Status Area

Contents

Scan Status (Offset: 0)

Section 4-6

The contents of the DeviceNet status area are shown below. The status area consists of the following 81 words. Details are provided in the following tables.

Word offset

3

4

0

1

5

6

7

8 to 11

12 to 15

16

17 to 78

79

80

Size

1 word

2 words

1 word

1 word

1 word

1 word

1 word

4 words

---

1 word

1 word each

1 word

1 word

Contents

Scan status

Scan and network communications status

Reserved

Present communications cycle time

Maximum communications cycle time

Minimum communications cycle time

Reserved

Flags showing devices registered in scan list

Reserved

Remote device status for MAC ID = 0

Remote device status for MAC ID = 1 to 62

Remote device status for MAC ID = 63

Reserved

The DeviceNet operating status is given as follows:

Bits

0

1

Flag name

ON_LINE

SCANNING

Meaning

ON when DeviceNet is online. OFF when it is offline.

ON when the scan is being performed. OFF when the scan is stopped.

2 to 15 Reserved

92

Setting File Descriptions

Scan and Network

Communications Status

(Offsets: 1 and 2)

Section 4-6

The DeviceNet communications status is given as shown in the following table.

All flags except the TRANSMISSION_ERROR flag will be OFF when offline, i.e., only the TRANSMISSION_ERROR flag is valid offline. All flags are valid when online even when the scan is being performed.

Bits

0 to 15

16

Flag name

Reserved

MEMORY_ERROR

Meaning

17 DUP_MAC_ERROR

/BUS_OFF_ERROR

ON when an error has been detected in reading or writing the EEPROM.

ON when a duplicate MAC ID has been detected when executing the ON_LINE command or ON when the bus is OFF.

18 to 20 Reserved

21

22

23

TRANSMISSION_

ERROR

COMMUNICATIONS

_ERROR

VERIFICATION_

ERROR

ON when a transmission error has been discovered, including the following errors.

There is no network power supply.

There are no devices on the network other than the Open Network Controller.

Transmission was not possible because there was too much traffic on the network.

There is a CAN controller error.

ON when an I/O connection that has been opened on the network times out.

This flag is an OR of the COMMUNICATIONS_

ERROR Flags in the Device status.

ON when a verifications error has been discovered, including the following errors.

A device that does not exist on the network is registered in the scan list.

A device that is not supported is registered in the scan list (e.g., a COS-only slave).

The data size of a device on the network differs from the data size registered in the scan list.

This flag is an OR of the DEVICE_DOES_NOT_

EXIST and the IO_DATA_SIZE_MISMATCH flags in the Device status.

24 to 29 Reserved

30 ERROR/

COMMUNICATIONS

_STOPPAGE

31 IO_DATA_

COMMUNICATIONS

ON when one or more of the following errors has been discovered.

One or more of the flags in bits 16 to 23 of the scan status is ON.

Scanning has been stopped because the

TRANSMISSION_ERROR (bit 21) or

COMMUNICATIONS_ERROR (bit 22) flag turned

ON and scanning was set to be stopped for communications errors.

This flag will be turned OFF if a scan stopped for a communications error is restarted using a FINS command.

ON when remote I/O communications are being performed. This flag will be ON when I/O data is being exchanged with one or more devices registered in the scan list.

Message communications will not affect this flag.

This flag will be turned OFF when a transmission error (i.e., timeout or no network power) occurs.

93

Setting File Descriptions

Section 4-6

Present Communications

Cycle Time (Offset: 4)

Max. Communications

Cycle Time (Offset: 5)

This word contains the present value of the communications cycle time in ms.

This information is valid only when the scan is being performed.

This word contains the maximum value of the communications cycle time in ms.

This information is valid only when the scan is being performed.

Min. Communications

Cycle Time (Offset: 6)

This word contains the minimum value of the communications cycle time in ms.

This information is valid only when the scan is being performed.

Registered Device

Information

(Offsets: 8 to 11)

This word contains a bit map that shows the devices that are registered in the scan list. The relationship of the flags in the bit map and the MAC IDs of the devices is shown in the following table. The body of the table shows the MAC IDs.

Offset

8

9

10

11

Bit 15

15

31

47

63

Bit 14

14

30

46

62

Bit 13

13

29

45

61

Bit 12

12

28

44

60

Bit 11

11

27

43

59

Bit 10

10

26

42

58

Bit 9

9

25

41

57

Bit 8

8

24

40

56

Bit 7

7

23

39

55

Bit 6

6

22

38

54

Bit 5

5

21

37

53

Bit 4

4

20

36

52

Bit 3

3

19

35

51

Bit 2

2

18

34

50

Bit 1

1

17

34

49

Bit 0

0

16

32

48

The status of the flags in the above bit map have the following meaning.

ON

OFF

Flag Meaning

The device is not registered in the scan list.

The device is registered in the scan list.

Device Status

(Offsets: 16 to 79)

One word is used to give the status of each device with MAD IDs of 0 to 63. All flags will be OFF when offline. All flags are valid when online even when the scan is being performed.

6

7

Bits

0 to 2

3

4

5

8 to 15

Flag name

Reserved.

DEVICE_DOES_

NOT_EXIST

IO_DATA_SIZE_

MISMATCH

Meaning

ON when the device does not exist, including the following errors.

The device does not exist on the network but is registered in the scan list.

The device is not supported even though it is registered in the scan list (e.g., a COS-only slave).

ON when the data size of the device on the network differs from the data size registered in the scan list.

ON when an I/O connection that has been opened for the device times out.

COMMUNICATIONS

_ERROR

Reserved.

IO_DATA_

COMMUNICATIONS

ON when remote I/O communications are being performed. This flag will be ON when I/O data is being exchanged with the device.

For devices that are using only explicit client messages, this flag will be ON when messages can be used.

This flag will be turned OFF when a transmission error (i.e., timeout or no network power) occurs.

Reserved.

94

Setting File Descriptions

Section 4-6

4-6-8 DeviceNet Scan List

/etc/FgwQnx/scanlist.ini contains the scan list settings for allocations to Device-

Net slaves. On the DeviceNet network, the MAC ID is used as the FINS node address in the Open Network Controller. FINS node address 0 is for the local node and cannot be used unless FINS is not used and only event memory is being allocated.

The scan list contains the input and output areas, first words, and sizes for each

MAC ID on the DeviceNet network in the format given below. Any line beginning with “#” will be ignored.

Example: 01,1,00,00,1,00,02

Enter the following settings on each line, separating each setting with a comma

(do not omit any zeros except for those in I/O area numbers): MAC ID, input area number, input offset, input size, output area number, output offset, and output area size.

MAC ID

Item

Input area number

Input area offset

Input size

Output area number

Output area offset

Output size

Setting

Set the MAC ID of the slave between 00 and 63. The MAC

ID will be used as the FINS node address.

Set the number specified in the number specified in

/etc/FgwQnx/FgwQnxDrm.ini.

Set the number of bytes. The start of the area will be offset by the set number of bytes from the beginning of the input position specified in /etc/FgwQnx/FgwQnxDrm.ini.

Set the number of bytes between 00 and 64.

Set the number specified in the number specified in

/etc/FgwQnx/FgwQnxDrm.ini.

Set the number of bytes. The start of the area will be offset by the set number of bytes from the beginning of the output position specified in /etc/FgwQnx/FgwQnxDrm.ini.

Set the number of bytes between 00 and 64.

Note

1. The input and output area offsets must be even numbers except for 8-bit slaves.

2. When using A MULTIPLE I/O TERMINAL, two words are used by the Communications Unit to input the I/O Unit interface status to the master. Set the scan list accordingly.

3. When only explicit messages are going to be used, set the input and output area sizes to 0.

Refer to

4-7-6 Scan Lists

for descriptions of the meaning of the settings.

95

Setting File Descriptions

Section 4-6

4-6-9 Controller Link Settings

/etc/FgwQnx/FgwQnxClk.ini contains setting for the Controller Link NP. Only the node address and baud rate are set in this file.

The Controller Link Board must be set to agree with the settings in this file.

Set the base address on the Controller Link Board’s DIP switch to this address.

Set the baud rate: 1: 500 Kbps, 2: 1 Mbps, 3: 2 Mbps

Set the node address between 1 and 32.

Set the jumper pin on the Controller Link Board to the value displayed here (15).

Note

Set the baud rate to the same values as the other nodes (e.g., Controller Link

Units) on the Controller Link network.

96

Setting File Descriptions

Section 4-6

4-6-10 HLK_UNIT Settings

/etc/FgwQnx/FgwQnxHlk.ini contains the settings for the Host Link NP.

Set the number of retries.

Set the node address of the HLK NP between 1 and 253.

Set the RS-232C communications parameters:

Baud rate: 300, 600, 1200, 1800, 2400, 4800,

9600, 19200, 38400, 57600, or 115200

Data length: 5, 6, 7, or 8

Stop bits: 1 or 2

Parity: N = none, E = even, O = odd

Set the timeout time for Host Link responses in ms.

97

Setting File Descriptions

Section 4-6

4-6-11 Host Link Address Tables

/etc/FgwQnx/HlkNetTbl.ini contains the setting file for C-series Host Link (SYS-

MAC WAY), CV-series Host Link (SYSMAC WAY-CV), and CompoWay/F nodes. Set the unit address, protocol, and model name.

You can not mix CompoWay/F with either C-series or CV-series Host Link nodes under the same HLK. You can mix C-series and CV-series Host Link nodes under the same HLK.

;=====================================================

;(c) Copyright OMRON Corporation 1999

; All Rights Reserved

;=====================================================

;

;HlkNetTbl.ini-ini file for HLK-NET_TABLE

[HLK0]

1,0,SYSWAY,C200H

2,0,SYSWAY,C200HS

3,0,SYSWAY,C200HG

4,0,SYSWAY,C200HX

5,0,SYSWAY,C200HX-CPU65-Z

6,0,SYSWAY,C200HX-CPU85-Z

7,0,SYSWAY,200HE

8,0,SYSWAY,CQM1

9,0,SYSWAY,CPM1/CPM1A

Set the FINS node address, unit address, protocol, and model in order, separating each with a comma.

The setting ranges are as follows:

FINS node address: 1 to 253

Unit address: 0 to 255 (depends on the PLC)

Protocol: SYSWAY = C-series Host Link

SYSWAY-CV = CV-series Host Link

Compoway/F = CompoWay/F

10,0,SYSWAY,SRM1

11,0,SYSWAY,CV500

12,0,SYSWAY,CVM1-CPU01

13,0,SYSWAY,CVM1-CPU11

14,0,SYSWAY,CVM1-CPU21

15,0,SYSWAY,CV1000/CV2000

16,0,SYSWAY,C20

17,0,SYSWAY,C20H/C28H/C40H/C60H

18,0,SYSWAY,C20/28/40/60P

19,0,SYSWAY,C20/28/40/60PF

20,0,SYSWAY,C50

21,0,SYSWAY,C120/C120F

22,0,SYSWAY,C500

23,0,SYSWAY,C500F

24,0,SYSWAY,C1000H

25,0,SYSWAY,C1000HF

26,0,SYSWAY,C2000H

27,0,SYSWAY,CS1-CPU67

28,0,SYSWAY,CS1-CPU66

29,0,SYSWAY,CS1-CPU65/45

30,0,SYSWAY,CS1-CPU64/44

31,0,SYSWAY,CS1-CPU63/43/42

[HLK1]

1,1,Compoway,Other

2,2,Compoway,Other

3,3,Compoway,Other

[HLK2]

98

Setting File Descriptions

Section 4-6

4-6-12 SYSMAC_UNIT Settings

/etc/FgwQnx/FgwQnxSysmac.ini contains settings for the SYSMAC Board NP.

Set the node address and startup mode.

Set the node address of the SYSMAC Board to between

1 and 253.

Set the startup mode of the SYSMAC Board.

1: MONITOR, 0: Use mode set on Board

99

Setting File Descriptions

Section 4-6

4-6-13 SYSMAC_UNIT Driver Settings

/etc/FgwQnx/FgwQnxSysmacDriver.ini contains the I/O address setting and teh service execution interval for the SYSMAC Board. Do not change the I/O port setting in this file. The I/O port setting must be made directly on the SYSMAC

Board.

The I/O port address (display only)

Set the mailbox execution interval in ms. If the interval is less than the cycle time, the cycle time will be used as the interval.

100

Setting File Descriptions

Section 4-6

4-6-14 SYSMAC Board Allocations in Event Memory

/etc/FgwQnx/FgwQnxSysmacMapping.ini contains settings to allocate event memory to the SYSMAC Board.

The area and first address on the Board are set along with the corresponding area and first address on the Open Network Controller. The transfer size and direction are also specified.

Each line requires the longer of the following times to process: The ladder program scan time on the SYSMAC Board or the mailbox service interval.

Here, the first bit (enable setting) is 0, i.e., the allocation is disabled.

Up to 32 lines can be set.

Each line contains an enable setting, the Board memory area code, the first

Board address, the Controller memory area code, the first Controller address, the number of words to transfer, and the direction. Each setting is separated with a comma. Up to 32 lines can be set.

Enable setting: 0 = disable, 1 = enable

Memory area code: 80 = CIO, 82 = DM

Number of words: 1 to 128

Direction setting: 0 = Board to Controller or 1 = Controller to Board)

Example

The setting indicates the following:

Copy 1 word of data beginning at word DM 5000 of the DM area (82) on the SYSMAC Board to word DM 5000 of the DM area (82) on the

Open Network Controller.

101

Setting Examples

Section 4-7

4-7 Setting Examples

The following network configuration will be used as an example to describe the settings in the environment settings files of the Open Network Controller.

4-7-1 Configurations

Network Configuration

Node 1

10.0.0.1

Ethernet

FINS network 1

Node 2

10.0.0.2

Subnet mask

255.255.255.0

IP router

Node 4

10.0.1.2

Network 5

Node 1

Controller Link

FINS network 3

Node 2

Controller Link Board

Node 3

Node 3

10.0.0.3

Open Network

Controller

Node 5

8 outputs

Node 63

Node 1

16 outputs

Node 2

16 inputs

Node 31

Node 3

16 outputs

Host Link

FINS network 4

DeviceNet

FINS network 2

Node 4

16 inputs

Node 1

Unit 1

Node 2

Unit 2

Event Memory Configuration

Controller Link data link area

Set with Controller Link

Support Software

DRM input area 1

Node 2 Node 4

DRM output area 1

Node 1 Node 5 Node 3

102

Controller Link data link area

Set with Controller Link

Support Software

Each node writes 10 words.

DRM status area (81 words)

480

Settings Files

Settings are required in the following files for the above configurations.

Settings

Ethernet

Starting FINS services

Ethernet NP

DeviceNet NP

Controller Link NP

Host Link NP

Files

/etc/hosts, /etc/netstart, /iproute

/etc/FgwQnx/FgwQnx.ini

/etc/FgwQnx/FgwQnxEtn.ini

/etc/FgwQnx/FgwQnxDrm.ini, /etc/FgwQnx/scanlist.ini

/etc/FgwQnx/FgwQnxClk.ini

/etc/FgwQnx/FgwQnxHlk.ini, /etc/FgwQnx/HlkNetTbl.ini

Setting methods are described in the following sections.

Setting Examples

Section 4-7

4-7-2 Ethernet Settings

The IP addresses, host names, subnet mask, and IP router settings must be made in /etc/hosts, /etc/netstart, and /iproute.

IP Addresses and Host

Names

/etc/hosts contains a table of IP addresses and host names.

Note

The Open Network Controller does not use DNS.

Subnet Mask

Set the IP address of host name of the local node. The default host name of the Open Network Controller is “onchost”.

Set the IP address and host name of the other nodes as required by the applications. These settings are not necessarily required by the Controller.

etc/netstart contains the host name of the Open Network Controller and the subnet mask. Change the subnet mask in this file when required.

Set the host name.

Set the subnet mask.

I/O Router Settings

/iproute contains IP router addresses corresponding to the final network addresses. No settings are required unless IP routing is being used.

This line specifies that the IP router for network address 10.0.1 is 10.0.0.4.

4-7-3 Startup Services

/etc/FgwQnx/FgwQnx.ini contains the FinsGateway QNX settings, including the startup services and the local/relay network tables (unit addresses and networks). The sizes of the DM and CIO areas are also set.

103

Setting Examples

Set the services to be started.

CPU_UNIT and ENT must always be set.

Set the others according to your hardware configuration.

DRM:

CLK:

Built-in device network

Controller Link Board

SYSMAC0: SYSMAC Board

HLK : C-series Host Link,

CV-series Host Link, and

CompoWay/F

RUT : For future expansion.

Section 4-7

104

Setting Examples

Set the unit address of each service.

CPU_UNIT must be set to unit address 0. Other services can be set within the following ranges.

ETN:

HLK :

1 to 253

1 to 253

CLK:

DRM:

16 to 31

1 to 253

SYSMAC0: 1 to 253

The service will not be started unless it is set as as startup service.

Set the FINS network routing tables. These tables will be downloaded to the Controller Link Board at startup.

Set the local network table. Set the network address and unit address (“Unit ID”) for each

NP being used.

Here, Ethernet is network 1, DeviceNet is network 2, Controller Link is network 3, and

Host Link is network 4.

Set the relay network table for the FINS network.

Set three items on each line in the following order, separating each with a comma: Final network address, relay network address, relay node address.

Here, (5,1,4) says to go through node 4 of FINS network 1 to get to FINS network 5.

Allocates the COM2 port to HLK1.

Section 4-7

V1.03

105

Setting Examples

Set the number of words to allocate to the DM area. Up to

32,767 words can be allocated.

Set the number of words to allocate to the CIO area. Up to

8,192 words can be allocated.

Section 4-7

106

Setting Examples

Section 4-7

107

Setting Examples

Section 4-7

4-7-4 Ethernet NP Settings

/etc/FgwQnx/FgwQnxEtn.ini contains settings for the Ethernet NP.

Set the FINS node address for the local node.

Set the UDP port number to use for Ethernet as a decimal value. UDP port number 9600 will be used if the setting is omitted.

Set the IP address corresponding to the

FINS node address for each node on the Ethernet network.

Set the IP address to send FINS data to for any destination for which the IP address is not known. This setting is not required.

108

Setting Examples

Section 4-7

4-7-5 DeviceNet NP Settings

/etc/FgwQnx/FgwQnxDrm.ini contains settings for the DeviceNet NP.

Set the MAC ID of the local node.

Set the DeviceNet baud rate.

0: 125 kbps, 1: 250 kbps, 2: 500 kbps

Note

The DeviceNet baud rate must be the same for the master and all slaves.

109

Setting Examples

Set the time to scan all nodes on the DeviceNet network. If 0 is set, the cycle time will be made as short as possible. The time can be set between 1 and 500 (ms).

The actual scan cycle times can be read from the status area as follows: 5th word: Current time, 6th word: Maximum time, 7th word:

Minimum time.

Set the DeviceNet mode to use at startup.

0: Don’t scan, 1: Scan

Set the handling of the scan when a DeviceNet communications error occurs.

0: Continue the scan for all nodes without errors

Set the refresh interval for event memory data. The interval should be set near the current value of the communications cycle time.

Set the CIO area for input area 1 (inputs from DeviceNet to the event memory).

Set 50 as the first word of input area 1.

Set 2 words as the size of input area 1.

Section 4-7

Set to 0. Input area 2 is not used.

Set the CIO area for output area 1 (outputs from event memory to DeviceNet).

Set 350 as the first word of output area 1.

Set 3 words as the size of output area 1.

Set to 0. Output area 2 is not used.

Set the status area to be in the DM area starting from DM 400 and running for 81 words.

4-7-6 Scan List

/etc/FgwQnx/scanlist.ini contains the scan list settings for allocations to Device-

Net slaves. On the DeviceNet network, the MAC ID is used as the FINS node address. FINS node address 0 is for the local node and cannot be used unless

FINS is not used and only event memory is being allocated.

The input area, first input word, input size, output area, first output word, and output size must be set for each DeviceNet MAC ID.

110

Setting Examples

Section 4-7

The scan list contains the input and output areas, first words, and sizes for each

MAC ID on the DeviceNet network in the format given below. Any line beginning with “#” will be ignored.

Example: 01,1,00,00,1,00,02

Enter the following settings on each line, separating each setting with a comma

(do not omit zeros except for in I/O area numbers): MAC ID, input area number, input offset, input size, output area number, output offset, and output area size.

MAC ID

Item

Input area number

Input area offset

Input size

Output area number

Output area offset

Output size

Setting

Set the MAC ID of the slave between 00 and 63. The MAC

ID will be used as the FINS node address.

Set the number specified in the number specified in

/etc/FgwQnx/FgwQnxDrm.ini.

Set the number of bytes. The start of the area will be offset by the set number of bytes from the beginning of the input position specified in /etc/FgwQnx/FgwQnxDrm.ini.

Set the number of bytes between 00 and 64.

Set the number specified in the number specified in

/etc/FgwQnx/FgwQnxDrm.ini.

Set the number of bytes. The start of the area will be offset by the set number of bytes from the beginning of the output position specified in /etc/FgwQnx/FgwQnxDrm.ini.

Set the number of bytes between 00 and 64.

Note

When only explicit messages are used, set the input and output area sizes to 0.

Refer to the following table for the meaning of these entries.

01, 1, 00, 00, 1, 00, 02

02, 1, 00, 02, 1, 00, 00

03, 1, 00, 00, 1, 04, 02

04, 1, 02, 02, 1, 00, 00

05, 1, 00, 00, 1, 02, 01

Node 1 is allocated 2 bytes beginning with the 1st byte (offset 00) in output area 1

(which starts at CIO 350), i.e., it is allocated CIO 350.

Node 2 is allocated 2 bytes beginning with the 1st byte (offset 00) in input area 1 (which starts at CIO 50), i.e., it is allocated CIO 50.

Node 3 is allocated 2 bytes beginning with the 5th byte (offset 04) in output area 1

(which starts at CIO 350), i.e., it is allocated CIO 352.

Node 4 is allocated 2 bytes beginning with the 3rd byte (offset 02) in input area 1 (which starts at CIO 50), i.e., it is allocated CIO 51.

Node 5 is allocated 1 byte beginning with the 3rd byte (offset 02) in output area 1

(which starts at CIO 350), i.e., it is allocated the rightmost byte of CIO 351.

If the offset is even, the rightmost byte will be allocated; if the offset is odd, the leftmost byte will be allocated. The rightmost byte of CIO 351 would be allocated for “05, 1, 00,

00, 1, 03, 01”.

Note

Two bytes equal one word.

111

Setting Examples

Section 4-7

4-7-7 Controller Link NP Settings

/etc/FgwQnx/FgwQncClk.ini contains settings for the Controller Link NP. Only the node address and baud rate are set in this file.

The Controller Link Board must be set to agree with the settings in this file.

Set the base address on the Controller Link Board’s DIP switch to this address.

Set the baud rate: 1: 500 Kbps, 2: 1 Mbps, 3: 2 Mbps

Set the node address between 1 and 32.

Set the jumper pin on the Controller Link Board to the value displayed here (15).

Note

Set the baud rate to the same values as the other nodes (e.g., Controller Link

Units) on the Controller Link network.

112

Setting Examples

Section 4-7

4-7-8 HLK_UNIT Settings

/etc/FgwQnx/FgwQnxHlk.ini contains the settings for the Host Link NP. Here, set the node address.

Set the number of retries.

Set the node address of the HLK NP between 1 and 253.

Set the RS-232C communications parameters as follows:

Baud rate: 9600, Data length: 7 bits, Stop bits: 2,

Parity: N = none

Set the timeout time for Host Link responses in ms.

113

Setting Examples

Section 4-7

/etc/FgwQnx/HlkNetTbl.ini contains the setting file for C-series Host Link (SYS-

MAC WAY) and CV-series Host Link (SYSMAC WAY-CV). Set the unit address, protocol, and model name.

;=====================================================

;(c) Copyright OMRON Corporation 1999

; All Rights Reserved

;=====================================================

;

;HlkNetTbl.ini-ini file for HLK-NET_TABLE

[HLK0]

1,0,SYSWAY,C200H

2,0,SYSWAY,C200HS

3,0,SYSWAY,C200HG

4,0,SYSWAY,C200HX

5,0,SYSWAY,C200HX-CPU65-Z

6,0,SYSWAY,C200HX-CPU85-Z

7,0,SYSWAY,200HE

8,0,SYSWAY,CQM1

9,0,SYSWAY,CPM1/CPM1A

10,0,SYSWAY,SRM1

11,0,SYSWAY,CV500

12,0,SYSWAY,CVM1-CPU01

13,0,SYSWAY,CVM1-CPU11

14,0,SYSWAY,CVM1-CPU21

15,0,SYSWAY,CV1000/CV2000

16,0,SYSWAY,C20

17,0,SYSWAY,C20H/C28H/C40H/C60H

18,0,SYSWAY,C20/28/40/60P

19,0,SYSWAY,C20/28/40/60PF

20,0,SYSWAY,C50

21,0,SYSWAY,C120/C120F

22,0,SYSWAY,C500

23,0,SYSWAY,C500F

24,0,SYSWAY,C1000H

25,0,SYSWAY,C1000HF

Set the FINS node address, unit address, protocol, and model in order, separating each with a comma.

The setting ranges are as follows:

26,0,SYSWAY,C2000H

27,0,SYSWAY,CS1-CPU67

28,0,SYSWAY,CS1-CPU66

29,0,SYSWAY,CS1-CPU65/45

30,0,SYSWAY,CS1-CPU64/44

31,0,SYSWAY,CS1-CPU63/43/42

FINS node address: 1 to 253

Unit address:

Protocol:

0 to 255

SYSWAY = C-series Host Link

SYSWAY-CV = CV-series Host Link

Compoway/F = CompoWay/F

[HLK1]

1,1,SYSWAY,C200HX

2,2,SYSWAY-CV,CVM1-CPU01

Sets FINS node address 1 to unit address 1 of COM2 with the C-series Host Link protocol (SYSWAY). The model is C200HX.

[HLK2]

1,0,Compoway,Other

2,1,Compoway,Other

3,2,Compoway,Other

Sets FINS node address 2 to unit address 2 of COM2 with the CV-series Host Link protocol (SYSWAY-CV). The model is CVM1.

114

SECTION 5

FINS Commands

This section individually describes the FINS commands and responses for CPU_UNIT and the network providers (NPs). Refer to the the

FINS Commands Reference Manual

(W227) for further information on FINS commands.

5-1

5-2

5-3

5-4

5-5

5-6

Overview

FINS Commands Addressed to CPU_Unit

5-2-1

5-2-2

5-2-3

5-2-4

5-2-5

5-2-6

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

MEMORY AREA READ: 01 01

MEMORY AREA WRITE: 01 02

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PARAMETER AREA READ: 02 01

PARAMETER AREA WRITE: 02 02

PARAMETER AREA CLEAR: 02 03

ROUTING TABLE SET: 02 25

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-2-7

5-2-8

5-2-9

5-2-10

5-2-11

CONTROLLER DATA READ: 05 01

CONNECTION DATA READ: 05 02

CLOCK READ: 07 01

CLOCK WRITE: 07 02

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

TIME COMPENSATION (Unit Version 1.1 or Later): 07 03 . . . . . . . . . . . . . . . .

5-2-12 LOOPBACK TEST: 08 01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

FINS Commands Addressed to ETN_UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-3-1

5-3-2

CONTROLLER DATA READ: 05 01

IP ADDRESS TABLE WRITE: 27 50

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-4-6

5-4-7

5-4-8

5-4-9

5-4-10

5-4-11

5-4-12

5-4-13

5-4-14

5-3-3

5-3-4

IP ADDRESS TABLE READ: 27 60 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ADDRESS INFORMATION READ: 27 65 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

FINS Commands Addressed to HLK_UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-4-1 FINS Commands for the C-series Host Link Protocol . . . . . . . . . . . . . . . . . . . . .

5-4-2

5-4-3

5-4-4

5-4-5

MEMORY AREA READ: 01 01

MEMORY AREA WRITE: 01 02

Memory Area Designations

RUN: 04 01

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

STOP: 04 02 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CONTROLLER DATA READ: 05 01

LOOPBACK TEST: 08 01

FILE MEMORY WRITE:22 11

FORCED SET/RESET: 23 01

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CONTROLLER STATUS READ: 06 01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

FILE MEMORY INDEX READ: 22 0F

FILE MEMORY READ: 22 10

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

FORCED SET/RESET CANCEL: 23 02 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-4-15

5-4-16

FINS Commands for the CV-series Host Link Protocol

FINS Commands for the CompoWay/F Protocol

. . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . .

FINS Commands Addressed to DRM_UNIT

5-5-1 RUN: 04 01

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-5-2

5-5-3

5-5-4

5-5-5

STOP: 04 02

RESET: 04 03

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CONTROLLER DATA READ: 05 01

LOOPBACK TEST: 08 01

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-5-6 EXPLICIT MESSAGE SEND: 28 01

FINS Commands Addressed to CLK_UNIT

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

154

155

155

156

156

150

151

152

153

132

133

134

149

129

129

131

131

159

159

160

160

157

157

158

158

161

162

127

128

128

128

123

124

124

125

125

120

121

122

123

117

117

118

119

115

116

5-7

5-8

FINS Commands Addressed to SYSMAC_UNIT

5-7-1 Memory Area Designations

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-7-2

5-7-3

5-7-4

MEMORY AREA READ: 01 01

MEMORY AREA WRITE: 01 02

RUN: 04 01

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-7-5

5-7-6

5-7-7

5-7-8

STOP: 04 02 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CONTROLLER DATA READ: 05 01

CLOCK READ: 07 01

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CONTROLLER STATUS READ: 06 01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

5-7-9

5-7-10

CLOCK WRITE: 07 02 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

CONTROLLER DATA READ: 05 01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

End Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Section

166

167

168

169

169

170

171

162

163

164

165

166

FINS Commands Addressed to CPU_Unit

5-1 Overview

Section 5-2

The Open Network Controller converts FINS commands to the suitable communications protocol for the network for which the commands are intended.

The FINS commands that can be used for CPU_UNIT or the NPs are different.

There are also some differences in conversion rules depending on the network receiving the command.

Refer to the following sections for details on FINS commands for CPU_UNIT and the NPs.

Contents

FINS commands addressed to CPU_UNIT

FINS commands addressed to ETN_UNIT

FINS commands addressed to HLK_UNIT

FINS commands addressed to DRM_UNIT

FINS commands addressed to CLK_UNIT

FINS commands addressed to SYSMAC_UNIT

5-2

Section

5-3

5-4

5-5

5-6

5-7

Refer to

5-8 End Codes

for information on end codes.

5-2 FINS Commands Addressed to CPU_Unit

This section describes the FINS commands that can be addressed to

CPU_UNIT. These commands are listed in the following table.

Command code

01 01

01 02

02 01

02 02

02 03

02 25

05 01

05 02

07 01

07 02

07 03

08 01

Name and function

MEMORY AREA READ: Reads event memory

MEMORY AREA WRITE: Writes event memory

PARAMETER AREA READ: Reads the routing tables

PARAMETER AREA WRITE: Writes the routing tables

PARAMETER AREA CLEAR: Clears the routing tables

ROUTING TABLE SET

CONTROLLER DATA READ

CONNECTION DATA READ

CLOCK READ

CLOCK WRITE

TIME COMPENSATION (unit version 1.1 or later)

INTERNODE ECHO TEST

CPU_UNIT performs the FINS message communications functions of a CPU

Unit for a PLC. In particular, it provides the access functions required by personal computers and other devices on an Ethernet network to read and write event memory in the Open Network Controller.

The unit address of CPU_UNIT is 0. When accessing the CPU_UNIT at a specific node on a network using FINS message communications, specify 0 as the unit address in the destination FINS addresses.

117

FINS Commands Addressed to CPU_Unit

Section 5-2

5-2-1 MEMORY AREA READ: 01 01

Reads the contents of the specified number of consecutive words starting from the specified word in event memory.

Command Format

01 01

Command code

Beginning address

Memory area code

No. of items

(binary)

Response Format

01 01

Command code

End code Data (for number of items)

Parameters

Memory Area

Designations

Memory area code, beginning address, number of items (command)

Specify the type of data to be read, the beginning address of the data to be read, and the number of items of data to be read.

The memory areas that can be read are given in the following table. Refer to

Memory Area Designations

later in this section for the specific addresses that can be used.

Area

CIO area

DM area

Data type

Bit ON/OFF status

Word contents

Bit ON/OFF status

Word contents

00

80

02

82

Memory area code (hex)

1

2

1

2

Bytes per item

Data (response)

The data from the specified memory area is returned in sequence starting from the beginning address. The required number of bytes in total is calculated as follows: Number of bytes required by each item x number of items

For details regarding data configuration, refer to

Memory Area Designations

later in this section.

End code (response)

Refer to

5-8 End Codes

for information on end codes.

The memory area codes given in the following table are used to specify addresses to access in the event memory using FINS commands. “Bytes per item” indicates the number of bytes required in the FINS command or response for each item being accessed.

Area Data type Bytes per item

CIO area

DM area

General purpose

General purpose

Access length

Bits

Words

Bits

Words

Memory area code (hex)

00

80

02

82

1

2

1

2

Memory area addresses are designated in three bytes. The first and second byte are the word address and the third byte is the bit position when accessing bits.

118

FINS Commands Addressed to CPU_Unit

Section 5-2

When accessing bits, a maximum of 16 bits (i.e., items) can be accessed and they must all be in the same word.

When accessing words, specify 00 as the bit position (i.e., as the third byte).

5-2-2 MEMORY AREA WRITE: 01 02

Writes data to the specified number of consecutive words starting from the specified word.

Command Format

01 02

Command code

Beginning address

Memory area code

No. of items

(binary)

Data (for number of items)

Response Format

01 02

Command code

End code

Parameters

Precautions

Memory area code, beginning address, number of items (command)

Specify the type of data to be written, the beginning address of the data to be written, and the number of items of data to be written.

The memory areas that can be read are given in the following table. Refer to

Memory Area Designations

under

5-2-1 MEMORY AREA READ

for the specific addresses that can be used.

Area

CIO area

DM area

Data type

Bit ON/OFF status

Word contents

Bit ON/OFF status

Word contents

00

Memory area code (hex)

80

02

82

1

2

1

2

Bytes per item

Data (command)

The data to be written to the specified memory area is provided in sequence starting from the beginning address. The required number of bytes in total is calculated as follows:

Number of bytes required by each item x number of items

For details regarding data configuration, refer to

Memory Area Designations

under

5-2-1 MEMORY AREA READ

.

End code (response)

Refer to

5-8 End Codes

for information on end codes.

When writing bit ON/OFF status, a maximum of 16 bits (i.e., items) can be written in one command and they must all be in the same word.

119

FINS Commands Addressed to CPU_Unit

5-2-3 PARAMETER AREA READ: 02 01

Reads the contents of the routing tables.

Command Format

02 01 80 13

Section 5-2

Response Format

02 01 80 13

Command code

End code Parameter area code

Beginning word

No. of words

Parameters

Command code

Parameter area code

Beginning word

No. of words

Data

Parameter area code (command and response)

Specify the routing table area as the parameter area. The parameter area code is always 8013.

Beginning word (command and response)

Specify the first word to read. The beginning word address specifies the relative word address, with the beginning of the routing table as 0000 (hex). The following addresses can be used.

0000:

0000:

0011:

Beginning of routing tables

Beginning of local network table

Beginning of relay network table

Number of words (command and response)

Bits 0 to 14 are used to specify the number of words to be read. (Each word consists of 16 bits.) Bit 15 must be OFF (0) in the command format. When the content in the response format contains the last word of data in the specified parameter area, bit 15 will be ON (1).

The number of words data will be as follows when reading the routing tables:

Reading all the routing tables:

Reading all of the local network table:

Reading all of the relay network table:

30 Hex (96 bytes)

11 Hex (34 bytes)

1F Hex (62 bytes)

Data (response)

The specified data will be returned in sequence starting from the beginning word. The leftmost bits (bits 8 to 15) of each word are read first, followed by the rightmost bits (bits 0 to 7). The required number of bytes in total for each read is calculated as follows:

Number of words x 2 (each word consists of 2 bytes, or 16 bits)

End code (response)

Refer to

5-8 End Codes

for information on end codes.

120

FINS Commands Addressed to CPU_Unit

Section 5-2

5-2-4 PARAMETER AREA WRITE: 02 02

Writes data to the specified number of consecutive routing table area words starting from the specified word. To use the new routing tables, execute ROUT-

ING TABLE SET (02 25) after executing this command.

Command Format

02 02 80 13 Max. No. of words: 30 Hex (96 bytes)

Command code

Parameter area code

Beginning word

No. of words Data

Response Format

02 02

Command code

End code

Parameters

Parameter area code (command and response)

Specify the routing table area as the parameter area. The parameter area code is always 8013.

Beginning word (command and response)

Specify the first word to write. The beginning word address specifies the relative word address, with the beginning of the routing table as 0000 (hex). The following addresses can be used.

0000:

0000:

0011:

Beginning of routing tables

Beginning of local network table

Beginning of relay network table

Number of words (command and response)

Bits 0 to 14 are used to specify the number of words to be written. (Each word consists of 16 bits.) Bit 15 must be OFF (0) in the command format. When the content in the response format contains the last word of data in the specified parameter area, bit 15 will be ON (1).

The number of words data will be as follows when writing the routing tables:

Writing all the routing tables:

Writing all of the local network table:

Writing all of the relay network table:

30 Hex (96 bytes)

11 Hex (34 bytes)

1F Hex (62 bytes)

Data (command)

Specify the data to be written. The leftmost bits (bits 15 to 8) of each word must be specified first, followed by the rightmost bits (bits 7 to 0). The required number of bytes in total for each write can be calculated as follows:

121

FINS Commands Addressed to CPU_Unit

Section 5-2

No. of words x 2 (each word consists of 2 bytes, or 16 bits)

Data for all routing tables (30 Hex words = 96 bytes)

Local network table (11 Hex words = 34 bytes) Relay network table (1F Hex words = 62 bytes)

Network-Unit number pairs (16 pairs, 32 bytes)

1 byte 1 byte

2 bytes/pair 2 bytes/pair

1 byte

Destination/Relay network-node pairs (20 pairs, 60 bytes)

3 bytes/pair 3 bytes/pair

1 byte

Unit No.

No. of local networks

Network No.

Gateway count

(always 02)

Network No.

Relay node No.

Unit No.

Relay network No.

Destination network No.

No. of remote networks

End code (response)

Refer to

5-8 End Codes

for information on end codes.

Dummy

Relay node No.

Relay network No.

Destination network No.

5-2-5 PARAMETER AREA CLEAR: 02 03

Writes all zeros to the routing table area to clear the previous routing tables.

Command Format

02 03 80 13 00 00

Command code

Parameter area code

Beginning word

No. of words

Data

Response Format

02 03

Command code

End code

Parameters

Parameter area code (command)

Specify the routing table area as the parameter area. The parameter area code is always 8013.

Beginning word and Number of words (command)

Use the following settings.

Tables

All routing tables

Local network table

Relay network table

0000

0000

0011

Beginning word Number of words

0030 (96 bytes)

0011 (34 bytes)

001F (62 bytes)

Note

All of the routing tables will be cleared if FFFF is specified as the number of words.

Data (command)

Set to 0000. The number of words to be cleared is specified by the number of words in the command format. This parameter requires only two bytes (one word) of data.

End code (response)

Refer to

5-8 End Codes

for information on end codes.

122

FINS Commands Addressed to CPU_Unit

Section 5-2

5-2-6 ROUTING TABLE SET: 02 25

Sets the routing tables in the Open Network Controller. This command must be executed to enable the routing tables set with the ROUTING TABLE WRITE command (02 02). If ROUTING TABLE SET ends normally, the routing tables will be written to /etc/FgwQnx/FgwQnx.ini.

Command Format

02 15

Command code

Response Format

02 25

Command code

End code

Parameters

End code (response)

Refer to

5-8 End Codes

for information on end codes.

5-2-7 CONTROLLER DATA READ: 05 01

Reads the following data from the Open Network Controller.

The model of CPU_UNIT that is running.

The version of CPU_UNIT that is running.

Command Format

05 01

Command code

Response Format

05 01

20 bytes 20 bytes 28 bytes 20 bytes 20 bytes

Command code

End code CPU_UNIT model

CPU_UNIT version

For system use

Hardware model

Hardware version

The values defined in

/etc/FgwQnx/FgwQnx.ini

will be returned.

Parameters

CPU Unit model and version (response)

Each is returned in not more than 20 bytes in ASCII (i.e., 20 ASCII characters). If the model or version requires less than 20 characters, spaces will be inserted to fill the remainder.

End code (response)

Refer to

5-8 End Codes

for information on end codes.

123

FINS Commands Addressed to CPU_Unit

Section 5-2

5-2-8 CONNECTION DATA READ: 05 02

Reads the model numbers (names) of Units (NPs) corresponding of the specified unit addresses.

Command Format

05 02 00

Command code

Unit address

Number of items

Response Format

05 02

20 bytes 20 bytes

Command code

End code Model number

Unit address

Number of items

Data

Model number

Unit address

Parameters

Unit address (command and response)

Specify the first unit address for which information is to be read. Always specify

00 as the unit address.

Number of items (command)

Specify the number of items to be read. The number of items will be returned in order for the number specified, beginning with the unit address set in the “unit address” parameter. If the number of items is not specified, information will be read for all unit addresses.

Number of items (response)

The number of unit addresses (applications) for which the connection data is being returned. If bit 7 is ON (1), it means that the data for the last unit address is being returned.

Unit address and model number (response)

The unit address and model number (name) of the NP. The name is provided in up to 20 ASCII characters. Data will be returned for the specified number of items.

End code (response)

Refer to

5-8 End Codes

for information on end codes.

5-2-9 CLOCK READ: 07 01

Reads clock information.

Command Format

07 01

Command code

Response Format

07 01

Command code

Year Month Day Hour Minute Second Day of week

124

FINS Commands Addressed to CPU_Unit

Section 5-2

Parameters

Year, month, day, hour, minute, second, day of week (response)

The year, month, day of month, hour, minute, and second are expressed in BCD.

Year:

The rightmost two digits of the year. (Any value under 70 will be after the year 2000.)

Hour:

00 to 23 (BCD).

Day of week:

As follows:

Value (Hex)

Day of week

00

Sun

01

Mon

02

Tues

03

Wed

End code (response)

Refer to

5-8 End Codes

for information on end codes.

04

Thur Fri

05 06

Sat

5-2-10 CLOCK WRITE: 07 02

Immediately updates the time with the specified time data.

Command Format

07 02

Command code

Year Month Day Hour Minute Second Day of week

Response Format

07 02

Command code

End code

Parameters

Year, month, day, hour, minute, second, day of week (command)

The year, month, day of month, hour, minute, and second are expressed in BCD.

The second data may be omitted. The day of week data may also be omitted. It will not be used even if specified (see below.)

Year:

The rightmost two digits of the year. (Any value under 70 will be after the year 2000. )

Hour:

00 to 23 (BCD).

Day of week:

The day of the week will be calculated from the year, month, and day. The value in the command will be ignored.

Value (Hex)

Day of week

00

Sun

01

Mon

02

Tues

03

Wed

End code (response)

Refer to

5-8 End Codes

for information on end codes.

04

Thur Fri

05 06

Sat

Precautions

This command immediately updates the time to the specified time data.

For unit version 1.1 or later, OS tick interrupts are prohibited when the time data is written. Caution is thus required when running an application requiring realtime performance.

The continuity of time data may be lost before and after writing time data, depending on the time data settings. Problems may occur when running applications that must be executed periodically at specific intervals. Use the TIME

COMPENSATION command (07 03) in such cases.

5-2-11 TIME COMPENSATION (Unit Version 1.1 or Later): 07 03

Compensates time data gradually.

125

FINS Commands Addressed to CPU_Unit

Command Format

Section 5-2

07 03

Year

Item

Month

Day of month

Hour

Minutes

Seconds

Day of week

Command code

Year Month Day Hour Minute Second Day of week

Setting

Specify the last two digits of the year in BCD. Values less than 70 are for years in the 21st century.

Specify the last two digits of the year in BCD. Values less than 70 are for years in the 21st century.

Specify in BCD.

Specify in BCD between 00 and 23.

Specify in BCD.

Optional. Specify in BCD. To omit, specify 00.

Optional. A value can be specified. The day of the week, however, is calculated based on the year/month/day settings and any setting is ignored.

Response Format

07 03

Command code

End code

Precautions

Unlike the CLOCK WRITE command (07 02), the TIME COMPENSATION command does not immediately update the time to the specified time data, but compensates the time data gradually during the intervals between OS tick interrupts so that the time data gradually approaches the actual time.

If you specify in the command parameters a time that is ahead of the present clock data (called positive compensation), the intervals between ticks will become shorter. Conversely, if you specify a time that is behind the present clock data (called negative compensation), the intervals between ticks become longer. This command can thus be used to speed up or slow down the time data until compensation has been completed, at which time the time data will be the same as the actual time.

Gradually compensating the time data to approach the actual time requires a certain amount of time before the compensation processing is completed. A rough estimate of the time until the completion of compensation can be obtained using the following method.

1. Execute the CLOCK READ command (07 01) to confirm the present clock data, and then determine the difference between the actual time and the clock data.

2. The time until the completion of compensation will be approximately 10 times the difference.

For example, assume the present clock data is 10:05.05 and the actual time is

10:07.00. A positive compensation of 2 minutes is required; therefore, compensation completion will require approximately 20 minutes.

The tick interval will be faster for approximately 20 minutes from execution of the

0703 command, speeding up refreshing of the clock data. As a result, the time data equal the actual time of 10:27.00 after 20 minutes has passed, and the tick interval will return to normal.

126

FINS Commands Addressed to CPU_Unit

Section 5-2

The TIME COMPENSATION command (07 03) cannot be executed again before completion of time compensation. If execution of the TIME COMPENSA-

TION command (07 03) command is attempted during time compensation, an end code of 26 05 (service executing) will be returned.

The maximum time compensation possible is 30 minutes. If a value for a time difference exceeding 30 minutes is specified in the parameters, an end code of

11 04 (exceeds permissible range) will be returned.

5-2-12 LOOPBACK TEST: 08 01

Executes a loopback test with CPU_UNIT.

Command Format

08 01

Command code

Test data

Response Format

08 01

Command code

End code Test data

Parameters

Test data (command and response)

In the command block, designate the data to be transmitted to CPU_UNIT. In the response block, the test data from the command block will be returned as it is. If the test data in the response block is different from that in the command block, an error has occurred.

127

FINS Commands Addressed to ETN_UNIT

Section 5-3

5-3 FINS Commands Addressed to ETN_UNIT

This section describes the FINS commands that can be addressed to

ETN_UNIT. These commands are listed in the following table.

Command code

05 01

27 50

27 60

27 65

Name

CONTROLLER DATA READ

IP ADDRESS TABLE WRITE

IP ADDRESS TABLE READ

ADDRESS DATA READ

5-3-1 CONTROLLER DATA READ: 05 01

Reads the following data from the ETN_UNIT running on the Open Network

Controller.

Model

Version

Command Format

05 01

Command code

Response Format

05 01

20 bytes 20 bytes

Command code

End code ETN_UNIT model

ETN_UNIT version

Parameters

ETN_UNIT model and version (response)

Each is returned in not more than 20 bytes in ASCII (i.e., 20 ASCII characters). If the model or version requires less than 20 characters, spaces will be inserted to fill the remainder.

End code (response)

Refer to

5-8 End Codes

for information on end codes.

5-3-2 IP ADDRESS TABLE WRITE: 27 50

Writes the IP address table in ETN_UNIT.

Command Format

27 50

4 bytes 4 bytes

Command code

No. of records

FINS node number

IP address FINS node number

IP address

Response Format

27 50

Command code

End code

128

FINS Commands Addressed to ETN_UNIT

Section 5-3

Parameters

Number of records (command)

The number of records to write is specified between 0000 and 0020 Hex (0 to

32 decimal) in the command. If this value is set to 0, the IP address table will be cleared so that no records are registered.

FINS node number and IP address (command)

Specify the FINS node number and corresponding IP address for nodes with which communications will be performed. Up to 32 pairs can be specified.

End code (response)

Refer to

5-8 End Codes

for information on end codes.

5-3-3 IP ADDRESS TABLE READ: 27 60

Reads the IP address table in ETN_UNIT.

Command Format

27 60

Command code

No. of records

Response Format

27 50

Command code

End code

00 64

6 bytes

No. of stored records

No. of records

IP address table record

Parameters

6 bytes

IP address table record

Number of records (command, response)

The number of records to read is specified between 0000 and 0020 Hex (0 to 32 decimal) in the command. If this value is set to 0, the number of stored records is returned but the IP address table records are not returned.

The response returns the actual number of records read.

Number of stored records (response)

The number of IP address table records stored at the time the command is executed is returned as a hexadecimal number.

IP address table records (response)

The number of IP address table records specified in the number of records parameter is returned. The total number of bytes in the IP address table records is calculated as the number of records x 6 bytes/record. The configuration of the

6 bytes of data in each record is as shown in the following diagram.

00

FINS node number

IP address

End code (response)

Refer to

5-8 End Codes

for information on end codes.

5-3-4 ADDRESS INFORMATION READ: 27 65

Read FINS node numbers and IP addresses.

129

FINS Commands Addressed to ETN_UNIT

Command Format

27 65

Command code

Response Format

27 65

Command code

End code

00 01 4 bytes

FINS node number

IP address

Parameters

Section 5-3

FINS node number and IP address (response)

The currently set FINS node number and IP address are returned as hexadecimal values.

130

FINS Commands Addressed to HLK_UNIT

Section 5-4

5-4 FINS Commands Addressed to HLK_UNIT

Supported Serial

Communications

Protocols

The following three serial communications protocols are supported by the Open

Network Controller.

C-series Host Link (SYSMAC WAY)

CV-series Host Link (SYSMAC WAY)

CompoWay/F

HLK_UNIT converts FINS commands to commands in the above protocols.

The FINS commands supported by HLK_UNIT are described in this section by protocol.

5-4-1 FINS Commands for the C-series Host Link Protocol

This section describes the FINS commands that can be used with the C-series

Host Link protocol.

FINS Commands

0801

220F

2210

2211

2301

2302

Command code

0101

0102

0401

0402

0501

0601

Name

READ MEMORY AREA

WRITE MEMORY AREA

RUN

STOP

CONTROLLER DATA READ

CONTROLLER STATUS READ

LOOPBACK TEST

FILE MEMORY INDEX READ (see note)

FILE MEMORY READ (see note)

FILE MEMORY WRITE (see note)

FORCED SET/RESET

FORCED SET/RESET CANCEL

Note

The commands for file memory can be used only for the C1000H, C1000HF, and

C2000H.

Applicable PLCs

The following PLCs support the C-series Host Link protocol.

C20, C50, C120, C120F, C20H/C28H/C40H/C60H,

C20P/C28P/C40P/C60P, C20PF/C28PF/C40PF/C60PF, C500, C500F,

C1000H, C1000HF, C2000H, C200H, C200HS, C200HX/HG/HE, CQM1,

CPM1, CPM1A, CPM2A, CPM2C, SRM1, CV500, CVM1, CV1000,

CV2000, and CS1.

131

FINS Commands Addressed to HLK_UNIT

Section 5-4

5-4-2 MEMORY AREA READ: 01 01

Reads the contents of the specified number of consecutive memory area words starting from the specified word.

Command Format

01 01

Command code

Beginning address

Memory area code

No. of items

(binary)

Response Format

01 01

Command code

End code Data (for number of items)

Parameters

Memory area code, beginning address, number of items (command)

Specify the type of data to be read, the beginning address of the data to be read, and the number of items of data to be read.

Refer to

5-4-4 Memory Area Designations

for the specific addresses that can be used.

Data (response)

The data from the specified memory area is returned in sequence starting from the beginning address. The required number of bytes in total is calculated as follows: Number of bytes required by each item x number of items

For details regarding data configuration, refer to

5-4-4 Memory Area Designations

.

End code (response)

Refer to

5-8 End Codes

for information on end codes.

132

FINS Commands Addressed to HLK_UNIT

Section 5-4

5-4-3 MEMORY AREA WRITE: 01 02

Writes data to the specified number of consecutive words starting from the specified word.

Command Format

01 02

Command code

Beginning address

Memory area code

No. of items

(binary)

Data (for number of items)

Response Format

01 02

Command code

End code

Parameters

Memory area code, beginning address, number of items (command)

Specify the type of data to be written, the beginning address of the data to be written, and the number of items of data to be written.

The memory areas that can be read are given in the following table. Refer to

5-4-4 Memory Area Designations

for the specific addresses that can be used.

Data (command)

The data to be written to the specified memory area is provided in sequence starting from the beginning address. The required number of bytes in total is calculated as follows:

Number of bytes required by each item x number of items

For details regarding data configuration, refer to

5-4-4 Memory Area Designations

.

End code (response)

Refer to

5-8 End Codes

for information on end codes.

133

FINS Commands Addressed to HLK_UNIT

Section 5-4

5-4-4 Memory Area Designations

This section provides tables of the memory area designations for each PLC that are supported by FINS and Host Link commands. The following terms are used in the tables.

Command:

The hexadecimal FINS command code or ASCII Host Link command code.

Memory area code:

The memory area code used within FINS commands.

Offset:

The offset of each PLC memory area (e.g., CIO, LR, DM, etc.). These indicate the beginning addresses of the memory areas used in Host Link commands within the areas defined by memory area codes for FINS commands.

Size:

The size of the memory area in hexadecimal.

C200H

Command code

01 01

02

01

81

82

80

01

81

82

Memory area code

80

Offset

0000

03E8

0428

048C

0000

0000

0000

0000

03E8

0428

048C

0000

0000

0000

Size

0100

0040

0064

001C

0200

0200

07D0

0100

0040

0064

001C

0200

0200

07D0

Application

IR/SR area read

LR area read

HR area read

AR area read

Timer/counter Completion Flag read

Timer/counter PV read

DM area read

IR/SR area write

LR area write

HR area write

AR area write

Timer/counter Completion Flag write

Timer/counter PV write

DM area write

C200HS

Command code

01 01

02

01

81

82

80

01

81

82

Memory area code

80

Offset

0000

03E8

0428

048C

0000

0000

0000

0000

03E8

0428

048C

0000

0000

0000

Size

0200

0040

0064

001C

0200

0200

2710

0100

0040

0064

001C

0200

0200

2710

Application

IR/SR area read

LR area read

HR area read

AR area read

Timer/counter Completion Flag read

Timer/counter PV read

DM area read

IR/SR area write

LR area write

HR area write

AR area write

Timer/counter Completion Flag write

Timer/counter PV write

DM area write

134

FINS Commands Addressed to HLK_UNIT

C200HG

Section 5-4

Command code

01 01

02

01

81

82

90

98

01

81

82

90

98

80

Memory area code

80

Offset

048C

0000

0000

0000

0000

0000

0000

0000

0000

0000

03E8

0428

0000

03E8

0428

048C

0000

0000

Size

001C

0200

0200

2710

1800

1800

2710

1800

1800

0200

0040

0064

0200

0040

0064

001C

0200

0200

Application

IR/SR area read

LR area read

HR area read

AR area read

Timer/counter Completion Flag read

Timer/counter PV read

DM area read

EM bank 0 read

EM current bank read

IR/SR area write

LR area write

HR area write

AR area write

Timer/counter Completion Flag write

Timer/counter PV write

DM area write

EM bank 0 write

EM current bank write

C200HX

Command code

01 01

02

Memory area code

80

01

81

82

90 to 92

98

80

01

81

82

90 to 92

98

Offset

0000

0000

03E8

0428

048C

0000

0000

0000

0000

0000

0000

03E8

0428

048C

0000

0000

0000

0000

Size

1800

0200

0040

0064

001C

0200

0200

2710

1800

1800

0200

0040

0064

001C

0200

0200

2710

1800

Application

IR/SR area read

LR area read

HR area read

AR area read

Timer/counter Completion Flag read

Timer/counter PV read

DM area read

EM bank read for bank 0 to 2

EM current bank read

IR/SR area write

LR area write

HR area write

AR area write

Timer/counter Completion Flag write

Timer/counter PV write

DM area write

EM bank write for bank 0 to 2

EM current bank write

135

FINS Commands Addressed to HLK_UNIT

C200HX-CPU65-Z

Section 5-4

Command code

01 01

02

Memory area code

80

01

81

82

90 to 97

98

80

01

81

82

90 to 97

98

Offset

048C

0000

0000

0000

0000

0000

0000

0000

0000

0000

03E8

0428

0000

03E8

0428

048C

0000

0000

Size

001C

0200

0200

2710

1800

1800

2710

1800

1800

0200

0040

0064

0200

0040

0064

001C

0200

0200

Application

IR/SR area read

LR area read

HR area read

AR area read

Timer/counter Completion Flag read

Timer/counter PV read

DM area read

EM bank read for bank 0 to 7

EM current bank read

IR/SR area write

LR area write

HR area write

AR area write

Timer/counter Completion Flag write

Timer/counter PV write

DM area write

EM bank write for bank 0 to 7

EM current bank write

C200HX-CPU85-Z

Command code

01 01

02

Memory area code

80

01

81

82

90 to 97

A8 to AF

98

80

01

81

82

90 to 97

A8 to AF

98

Offset

0000

0000

0000

0000

0000

0000

0000

0000

0000

03E8

0428

048C

0000

03E8

0428

048C

0000

0000

0000

0000

Size

0200

0200

2710

1800

1800

1800

1800

1800

0200

0040

0064

001C

0200

0040

0064

001C

0200

0200

2710

1800

Application

IR/SR area read

LR area read

HR area read

AR area read

Timer/counter Completion Flag read

Timer/counter PV read

DM area read

EM bank read for bank 0 to 7

EM bank read for bank 8 to F

EM current bank read

IR/SR area write

LR area write

HR area write

AR area write

Timer/counter Completion Flag write

Timer/counter PV write

DM area write

EM bank write for bank 0 to 7

EM bank write for bank 8 to F

EM current bank write

136

FINS Commands Addressed to HLK_UNIT

C200HE

Section 5-4

Command code

01 01

02

01

81

82

80

01

81

82

Memory area code

80

Offset

0000

0000

03E8

0428

048C

0000

0000

0000

0000

03E8

0428

048C

0000

0000

Size

2710

0200

0040

0064

001C

0200

0200

2710

0200

0040

0064

001C

0200

0200

Application

IR/SR area read

LR area read

HR area read

AR area read

Timer/counter Completion Flag read

Timer/counter PV read

DM area read

IR/SR area write

LR area write

HR area write

AR area write

Timer/counter Completion Flag write

Timer/counter PV write

DM area write

CQM1

Command code

01 01

02

01

81

82

80

01

81

82

Memory area code

80

Offset

0000

03E8

0428

048C

0000

0000

0000

0000

03E8

0428

048C

0000

0000

0000

Size

0100

0040

0064

001C

0200

0200

1A00

0100

0040

0064

001C

0200

0200

1A00

Application

IR/SR area read

LR area read

HR area read

AR area read

Timer/counter Completion Flag read

Timer/counter PV read

DM area read

IR/SR area write

LR area write

HR area write

AR area write

Timer/counter Completion Flag write

Timer/counter PV write

DM area write

CPM1/CPM1A

Command code

01 01

02

01

81

82

80

01

81

82

Memory area code

80

Offset

0000

03E8

0428

048C

0000

0000

0000

0000

03E8

0428

048C

0000

0000

0000

Size

0100

0010

0014

0010

0080

0080

1A00

0100

0010

0014

0010

0080

0080

1A00

Application

IR/SR area read

LR area read

HR area read

AR area read

Timer/counter Completion Flag read

Timer/counter PV read

DM area read

IR/SR area write

LR area write

HR area write

AR area write

Timer/counter Completion Flag write

Timer/counter PV write

DM area write

137

FINS Commands Addressed to HLK_UNIT

CPM2A/CPM2C

Section 5-4

Command code

01 01

02

01

81

82

80

01

81

82

Memory area code

80

Offset

0000

0000

03E8

0428

048C

0000

0000

0000

0000

03E8

0428

048C

0000

0000

Size

1A00

0100

0010

0014

0018

0100

0100

1A00

0100

0010

0014

0018

0100

0010

Application

IR/SR area read

LR area read

HR area read

AR area read

Timer/counter Completion Flag read

Timer/counter PV read

DM area read

IR/SR area write

LR area write

HR area write

AR area write

Timer/counter Completion Flag write

Timer/counter PV write

DM area write

SRM1

Command code

01 01

02

01

81

82

80

01

81

82

Memory area code

80

Offset

0000

03E8

0428

048C

0000

0000

0000

0000

03E8

0428

048C

0000

0000

0000

Size

0100

0010

0014

0010

0080

0080

1A00

0100

0010

0014

0010

0080

0080

1A00

Application

IR/SR area read

LR area read

HR area read

AR area read

Timer/counter Completion Flag read

Timer/counter PV read

DM area read

IR/SR area write

LR area write

HR area write

AR area write

Timer/counter Completion Flag write

Timer/counter PV write

DM area write

CV500

Command code

01 01

02

Memory area code

80

81

01

82

80

81

01

82

Offset

0000

0B00

0000

0800

0000

0800

0000

0000

0B00

0000

0800

0000

0800

0000

Size

09FC

0200

0200

0200

0200

0200

2000

09FC

0200

0200

0200

0200

0200

2000

Application

CIO area read

Auxiliary area read

TimerPV read

Counter PV read

Timer Completion Flag read

Counter Completion Flag read

DM area read

CIO area write

Auxiliary area write

TimerPV write

Counter PV write

Timer Completion Flag write

Counter Completion Flag write

DM area write

138

FINS Commands Addressed to HLK_UNIT

CVM1-CPU01

Section

Command code

01 01

02

Memory area code

80

81

01

82

80

81

01

82

Offset

0000

0000

0B00

0000

0800

0000

0800

0000

0000

0B00

0000

0800

0000

0800

Size

2000

09FC

0200

0200

0200

0200

0200

2000

09FC

0200

0200

0200

0200

0200

Application

CIO area read

Auxiliary area read

TimerPV read

Counter PV read

Timer Completion Flag read

Counter Completion Flag read

DM area read

CIO area write

Auxiliary area write

TimerPV write

Counter PV write

Timer Completion Flag write

Counter Completion Flag write

DM area write

5-4

CVM1-CPU11

Command code

01 01

02

Memory area code

80

81

01

82

80

81

01

82

Offset

0000

0000

0B00

0000

0800

0000

0000

0B00

0000

0800

0000

0800

0800

0000

Size

2710

09FC

0200

0400

0400

0400

09FC

0200

0400

0400

0400

0400

0400

2710

Application

CIO area read

Auxiliary area read

TimerPV read

Counter PV read

Timer Completion Flag read

Counter Completion Flag read

DM area read

CIO area write

Auxiliary area write

TimerPV write

Counter PV write

Timer Completion Flag write

Counter Completion Flag write

DM area write

139

FINS Commands Addressed to HLK_UNIT

CVM1-CPU21

Section

Command code

01 01

02

Memory area code

80

81

01

82

90 to 97

98

80

81

01

82

90 to 97

98

Offset

0800

0000

0800

0000

0000

0000

0000

0000

0000

0000

0B00

0000

0000

0B00

0000

0800

0000

0800

Size

0400

0400

0400

2710

7FFE

7FFE

2710

7FFE

7FFE

09FC

0200

0400

09FC

0200

0400

0400

0400

0400

Application

CIO area read

Auxiliary area read

TimerPV read

Counter PV read

Timer Completion Flag read

Counter Completion Flag read

DM area read

EM bank read for bank 0 to 7

EM current bank read

CIO area write

Auxiliary area write

TimerPV write

Counter PV write

Timer Completion Flag write

Counter Completion Flag write

DM area write

EM bank write for bank 0 to 7

EM current bank write

5-4

CV1000/CV2000

Command code

01 01

02

Memory area code

80

81

01

82

90 to 97

98

80

81

01

82

90 to 97

98

Offset

0000

0000

0B00

0000

0800

0000

0800

0000

0000

0000

0000

0B00

0000

0800

0000

0800

0000

0000

Size

7FFE

09FC

0200

0400

0400

0400

0400

2710

7FFE

7FFE

09FC

0200

0400

0400

0400

0400

2710

7FFE

Application

CIO area read

Auxiliary area read

TimerPV read

Counter PV read

Timer Completion Flag read

Counter Completion Flag read

DM area read

EM bank read for bank 0 to 7

EM current bank read

CIO area write

Auxiliary area write

TimerPV write

Counter PV write

Timer Completion Flag write

Counter Completion Flag write

DM area write

EM bank write for bank 0 to 7

EM current bank write

140

FINS Commands Addressed to HLK_UNIT

C20

Section 5-4

Command code

01 01

02

01

81

80

Memory area code

80

01

81

Offset

0000

0428

0000

0000

0000

0428

0000

0000

Size

0014

000A

0200

0200

0014

000A

0200

0200

Application

IR/SR area read

HR area read

Timer/counter Completion Flag read

Timer/counter PV read

IR/SR area write

HR area write

Timer/counter Completion Flag write

Timer/counter PV write

C20H/C28H/C40H/C60H

Command code

01 01

02

01

81

82

80

01

81

82

Memory area code

80

Offset

0000

0000

03E8

0428

048C

0000

0000

0000

0000

03E8

0428

048C

0000

0000

Size

07D0

0100

0040

0064

001C

0200

0200

07D0

0100

0040

0064

001C

0200

0200

Application

IR/SR area read

LR area read

HR area read

AR area read

Timer/counter Completion Flag read

Timer/counter PV read

DM area read

IR/SR area write

LR area write

HR area write

AR area write

Timer/counter Completion Flag write

Timer/counter PV write

DM area write

C20/28/40/60P

Command code

01 01

02

01

81

82

80

01

81

82

Memory area code

80

Offset

0000

0428

0000

0000

0000

0000

0428

0000

0000

0000

Size

0014

000A

0030

0030

0040

0014

000A

0030

0030

0040

Application

IR/SR area read

HR area read

Timer/counter Completion Flag read

Timer/counter PV read

DM area read

IR/SR area write

HR area write

Timer/counter Completion Flag write

Timer/counter PV write

DM area write

141

FINS Commands Addressed to HLK_UNIT

C20/28/40/60PF

Section 5-4

Command code

01 01

02

01

81

82

80

01

81

82

Memory area code

80

Offset

0000

0428

0000

0000

0000

0000

0428

0000

0000

0000

Size

0020

0010

0040

0040

0080

0020

0010

0040

0040

0080

Application

IR/SR area read

HR area read

Timer/counter Completion Flag read

Timer/counter PV read

DM area read

IR/SR area write

HR area write

Timer/counter Completion Flag write

Timer/counter PV write

DM area write

C50

Command code

01 01

02

01

81

82

01

81

82

80

Memory area code

80

Offset

0000

03E8

0428

0000

0000

0000

0000

03E8

0428

0000

0000

0000

Size

0040

0020

0020

0080

0080

0200

0040

0020

0020

0080

0080

0200

Application

IR/SR area read

LR area read

HR area read

Timer/counter Completion Flag read

Timer/counter PV read

DM area read

IR/SR area write

LR area write

HR area write

Timer/counter Completion Flag write

Timer/counter PV write

DM area write

C120/C120F

Command code

01 01

02

01

81

82

80

01

81

82

Memory area code

80

Offset

0000

0428

0000

0000

0000

0000

0428

0000

0000

0000

Size

0040

0020

0080

0080

0200

0040

0020

0080

0080

0200

Application

IR/SR area read

HR area read

Timer/counter Completion Flag read

Timer/counter PV read

DM area read

IR/SR area write

HR area write

Timer/counter Completion Flag write

Timer/counter PV write

DM area write

142

FINS Commands Addressed to HLK_UNIT

C500

Section 5-4

Command code

01 01

02

01

81

82

80

01

81

82

Memory area code

80

Offset

0000

03E8

0428

0000

0000

0000

0000

03E8

0428

0000

0000

0000

Size

0100

0020

0020

0080

0080

0200

0100

0020

0020

0080

0080

0200

Application

IR/SR area read

LR area read

HR area read

Timer/counter Completion Flag read

Timer/counter PV read

DM area read

IR/SR area write

LR area write

HR area write

Timer/counter Completion Flag write

Timer/counter PV write

DM area write

C500F

Command code

01 01

02

01

81

82

01

81

82

80

Memory area code

80

Offset

0000

03E8

0428

0000

0000

0000

0000

03E8

0428

0000

0000

0000

Size

0100

0020

0020

0080

0080

1000

0100

0020

0020

0080

0080

1000

Application

IR/SR area read

LR area read

HR area read

Timer/counter Completion Flag read

Timer/counter PV read

DM area read

IR/SR area write

LR area write

HR area write

Timer/counter Completion Flag write

Timer/counter PV write

DM area write

C1000H

Command code

01 01

02

01

81

82

80

01

81

82

Memory area code

80

Offset

0000

03E8

0428

048C

0000

0000

0000

0000

03E8

0428

048C

0000

0000

0000

Size

0100

0040

0064

001C

0200

0200

1000

0100

0040

0064

001C

0200

0200

1000

Application

IR/SR area read

LR area read

HR area read

AR area read

Timer/counter Completion Flag read

Timer/counter PV read

DM area read

IR/SR area write

LR area write

HR area write

AR area write

Timer/counter Completion Flag write

Timer/counter PV write

DM area write

143

FINS Commands Addressed to HLK_UNIT

C1000HF

Section 5-4

Command code

01 01

02

01

81

82

80

01

81

82

Memory area code

80

Offset

0000

0000

03E8

0428

048C

0000

0000

0000

0000

03E8

0428

048C

0000

0000

Size

2710

0100

0040

0064

001C

0200

0200

2710

0100

0040

0064

001C

0200

0200

Application

IR/SR area read

LR area read

HR area read

AR area read

Timer/counter Completion Flag read

Timer/counter PV read

DM area read

IR/SR area write

LR area write

HR area write

AR area write

Timer/counter Completion Flag write

Timer/counter PV write

DM area write

C2000H

Command code

01 01

02

01

81

82

80

01

81

82

Memory area code

80

Offset

0000

0000

03E8

0428

048C

0000

0000

03E8

0428

048C

0000

0000

0000

0000

Size

1A00

0100

0040

0064

001C

0200

0100

0040

0064

001C

0200

0200

0200

1A00

Application

IR/SR area read

LR area read

HR area read

AR area read

Timer/counter Completion Flag read

Timer/counter PV read

DM area read

IR/SR area write

LR area write

HR area write

AR area write

Timer/counter Completion Flag write

Timer/counter PV write

DM area write

144

FINS Commands Addressed to HLK_UNIT

CS1-CPU67

Section

Command code

01 01

02

80

B0

B2

80

B3

81

82

90 to 97

A0 to A7

A8 to AC

98

Memory area code

80

B0

B2

80

B3

01

09

81

89

Offset

0800

0000

8000

0000

0800

0000

8000

0000

0000

0000

0000

0000

0B00

0000

0000

89

82

90 to 97

A0 to A7

A8 to AC

98

0000

0000

0000

0000

0000

0B00

0000

0000

0800

0000

8000

0000

0000

0000

0000

Size

2710

2710

09FC

1800

0200

03C0

03C0

0800

0800

0800

0800

2710

2710

0800

0800

0800

0800

0800

0800

0800

2710

2710

09FC

1800

0200

03C0

03C0

0800

2710

2710

Application

CIO area read

HR area read

Timer/counter PV read

DM area read

EM bank read for bank 0 to 7

EM bank read for bank 8 to C

EM current bank read

CIO area write

HR area write

AR area write

Timer/counter PV write

DM area write

EM bank write for bank 0 to 7

EM bank write for bank 8 to C

EM current bank write

5-4

145

FINS Commands Addressed to HLK_UNIT

CS1-CPU66

Section

Command code

01 01

02

B0

B2

80

B3

81

82

90 to 96

A0 to A6

98

80

Memory area code

80

B0

B2

80

B3

01

09

81

89

Offset

0800

0000

8000

0000

0800

0000

8000

0000

0000

0000

0000

0000

0B00

0000

0000

89

82

90 to 96

A0 to A6

98

0000

0000

0000

0000

0B00

0000

0000

0800

0000

8000

0000

0000

0000

Size

2710

09FC

1800

0200

03C0

03C0

0800

0800

0800

0800

2710

2710

0800

0800

0800

0800

0800

0800

0800

2710

2710

09FC

1800

0200

03C0

03C0

0800

2710

Application

CIO area read

HR area read

Timer/counter PV read

DM area read

EM bank read for bank 0 to 6

EM current bank read

CIO area write

HR area write

AR area write

Timer/counter PV write

DM area write

EM bank write for bank 0 to 6

EM current bank write

5-4

146

FINS Commands Addressed to HLK_UNIT

CS1-CPU65/45

Section

Command code

01 01

02

B0

B2

80

B3

81

82

90 to 92

A0 to A6

98

80

Memory area code

80

B0

B2

80

B3

01

09

81

89

Offset

0800

0000

8000

0000

0800

0000

8000

0000

0000

0000

0000

0000

0B00

0000

0000

89

82

90 to 92

A0 to A2

98

0000

0000

0000

0000

0B00

0000

0000

0800

0000

8000

0000

0000

0000

Size

2710

09FC

1800

0200

03C0

03C0

0800

0800

0800

0800

2710

2710

0800

0800

0800

0800

0800

0800

0800

2710

2710

09FC

1800

0200

03C0

03C0

0800

2710

Application

CIO area read

HR area read

Timer/counter PV read

DM area read

EM bank read for bank 0 to 2

EM current bank read

CIO area write

HR area write

AR area write

Timer/counter PV write

DM area write

EM bank write for bank 0 to 2

EM current bank write

5-4

147

FINS Commands Addressed to HLK_UNIT

CS1-CPU64/44

Section

Command code

01 01

02

82

90

A0

98

B0

B2

80

B3

81

82

90

A0

98

80

Memory area code

80

B0

B2

80

B3

01

09

81

89

Offset

0800

0000

8000

0000

0800

0000

8000

0000

000

0000

0000

0000

0B00

0000

0000

89

0000

0000

0000

0000

0B00

0000

0000

0800

0000

8000

0000

000

0000

Size

2710

09FC

1800

0200

03C0

03C0

0800

0800

0800

0800

2710

2710

0800

0800

0800

0800

0800

0800

0800

2710

2710

09FC

1800

0200

03C0

03C0

0800

2710

Application

CIO area read

HR area read

Timer/counter PV read

DM area read

EM bank 0 read

EM current bank read

CIO area write

HR area write

AR area write

Timer/counter PV write

DM area write

EM bank 0 write

EM current bank write

5-4

148

FINS Commands Addressed to HLK_UNIT

CS1-CPU63/43/42

Section

Command code

01 01

02

82

80

B0

B2

80

B3

81

Memory area code

80

B0

B2

80

B3

01

09

81

89

89

82

Offset

8000

0000

0000

0000

0000

0B00

0800

0000

8000

0000

0800

0000

0000

0000

0800

0000

8000

0000

0000

0000

0000

0B00

0000

0000

Size

0800

2710

09FC

1800

0200

03C0

0800

0800

0800

0800

0800

0800

03C0

0800

0800

0800

0800

2710

09FC

1800

0200

03C0

03C0

0800

Application

CIO area read

HR area read

Timer/counter PV read

DM area read

CIO area write

HR area write

AR area write

Timer/counter PV write

DM area write

5-4

5-4-5 RUN

: 04 01

Changes the CPU Unit’s operating mode to DEBUG, MONITOR or RUN, starting execution of the program in the PLC.

Command Format

04 01 00 00

Command code

Program

No.

Mode

Response Format

04 01

Command code

End code

Parameters

Program No. and Mode (command)

Refer to the

FINS Commands Reference Manual

(W227) for details on the program number and mode.

End code (response)

Refer to

5-8 End Codes

for information on end codes.

149

FINS Commands Addressed to HLK_UNIT

5-4-6 STOP: 04 02

Section 5-4

Changes the CPU Unit’s operating mode to PROGRAM, stopping program execution.

Command Format

04 02

Command code

Response Format

04 02

Command code

End code

Parameters

End code (response)

Refer to

5-8 End Codes

for information on end codes.

150

FINS Commands Addressed to HLK_UNIT

5-4-7 CONTROLLER DATA READ: 05 01

Reads the model of the PLC.

Command Format

05 01

Command code

Response Format

05 01

Command code

End code

40 bytes

PLC model

Parameters

Section 5-4

PLC model (response)

The model is returned in not more than 40 bytes in ASCII (i.e., 40 ASCII characters). If the model or version requires less than 40 characters, spaces will be inserted to fill the remainder.

The following stings will be returned.

C250

C500

C120/C50

C250F

C500F

C120F

C2000

C1000H

C2000H/CQM1/CPM1/CPM1A/SRM1

C20H/C28H/C40H/C200H/C200HS/C200HX/HG/HE

C1000HF

CV500

CV1000

CV2000

CS1

CVM1-CPU01

CVM1-CPU11

CVM1-CPU21

SYSMAC WAY PLC-

The last string will be returned for all PLCs not listed above.

End code (response)

Refer to

5-8 End Codes

for information on end codes.

151

FINS Commands Addressed to HLK_UNIT

5-4-8 CONTROLLER STATUS READ: 06 01

Reads the operating status of the controller.

Command Format

06 01

Section 5-4

Command code

Response Format

06 01

Command code

End code

Status Mode

Fatal error data

Non-fatal error data

Parameters

16 bytes

Error code

Error message

Refer to the

FINS Commands Reference Manual

(W227) for details on parameters.

Fatal error data (response)

Only the following fatal error data is supported.

FALS error

Program error (no END instruction)

I/O bus error

JMP error

Memory error

I/O setting error

I/O point overflow

Non-fatal error data (response)

Only the following non-fatal error data is supoorted.

FAL error

Battery error

Cycle time over

I/O verification error

End code (response)

Refer to

5-8 End Codes

for information on end codes.

152

FINS Commands Addressed to HLK_UNIT

Section 5-4

5-4-9 LOOPBACK TEST: 08 01

Executes a loopback test with the specified node (i.e., the CPU Unit or Host Link

Unit).

Command Format

08 01

122 bytes max.

Command code

Test data

(ASCII)

Response Format

08 01

Command code

End code

122 bytes max.

Test data

(ASCII)

Parameters

Test data (command and response)

In the command block, designate the data to be transmitted to a specified node.

Up to 122 bytes of data can be designated. In the response block, the test data from the command block will be returned as it is. If the test data in the response block is different from that in the command block, an error has occurred.

An error will occur if the test data is not ASCII.

End code (response)

Refer to

5-8 End Codes

for information on end codes.

153

FINS Commands Addressed to HLK_UNIT

Section 5-4

5-4-10 FILE MEMORY INDEX READ: 22 0F

Reads the File Memory index for the specified number of blocks from the specified beginning block number. This command is valid for the C1000H, C1000HF, and C2000H only.

Command Block

22 0F

Command code

Beginning block number

Number of blocks

Response Block

22 0F

Command code

End code Number of blocks remaining

Total number of blocks

Type

Data type

Control data

For 1 block

Data type

Control data

For 1 block

Parameters

Refer to the

FINS Commands Reference Manual

(W227) for details on parameters.

Beginning block number (command)

The first block can be 0000 to 07CF (0 to 1999 decimal);

Number of blocks (command)

The number of blocks can be 01 to 80 (1 to 128 decimal).

Number of blocks remaining (response)

The number of blocks not to be read can be 0000 to 07D0 (0 to 2,000 decimal).

Total number of blocks (response)

The total number of blocks in File Memory can be 0000, 03E8, or 07D0 (0, 1,000, or 2,000 in decimal, respectively).

End code (response)

Refer to

5-8 End Codes

for information on end codes.

154

FINS Commands Addressed to HLK_UNIT

Section 5-4

5-4-11 FILE MEMORY READ: 22 10

Reads the contents of the specified File Memory block. This command is valid for the C1000H, C1000HF, and C2000H only.

Command Block

22 10

Command code

Block number

Response Block

22 10 256 bytes

Command code

End code

Data type

Control data

Data

Parameters

Refer to the

FINS Commands Reference Manual

(W227) for details on parameters.

Block number (command)

The File Memory block to read can be between 0000 and 07CF (0 and

1,999 decimal).

End code (response)

Refer to

5-8 End Codes

for information on end codes.

5-4-12 FILE MEMORY WRITE

:22 11

Writes the specified contents to the specified File Memory block. This command is valid for the C1000H, C1000HF, and C2000H only.

Command Block

22 11

256 bytes

Command code

Block number

Data type

Control data

Data

Response Block

22 11

Command code

End code

Parameters

Refer to the

FINS Commands Reference Manual

(W227) for details on parameters.

Block number (command)

The File Memory block to write can be between 0000 and 07CF (0 and 1,999 decimal).

Data (command

Specify the contents for the specified File Memory block (256 bytes (128 words).

End code (response)

Refer to

5-8 End Codes

for information on end codes.

155

FINS Commands Addressed to HLK_UNIT

Section 5-4

5-4-13 FORCED SET/RESET: 23 01

Force-sets (ON) or force-resets (OFF) bits/flags. Bits/flags that are forced ON or

OFF will remain ON or OFF and cannot be written to until the forced status is released.

Command Format

23 01 00 01

Response Format

23 01

Command code

End code

Parameters

Refer to the

FINS Commands Reference Manual

(W227) for details on parameters.

Number of bits/flags (command)

The number of bits/flags to be set/reset is always 0001.

Set/reset designation (command)

Specify the action to be taken for the bit/flag.

Value

(hex)

0000

0001

Name

Forced reset

Forced set

Operation

Turns OFF (0) the bit/flag and places it in forced status.

Turns ON (1) the bit/flag and places it in forced status.

End code (response)

Refer to

5-8 End Codes

for information on end codes.

5-4-14 FORCED SET/RESET CANCEL: 23 02

Cancels all bits (flags) that have been forced ON or forced OFF.

Command Format

23 02

Command code

Response Format

Command code

No. of bits/flags

Set/reset designation

Bit/flag

Memory area code

23 02

Command code

End code

Parameters

End code (response)

Refer to

5-8 End Codes

for information on end codes.

156

FINS Commands Addressed to HLK_UNIT

Section 5-4

5-4-15 FINS Commands for the CV-series Host Link Protocol

Refer to the

FINS Commands Reference Manual

(W227) for details on FINS commands for the CV-series Host Link protocol.

5-4-16 FINS Commands for the CompoWay/F Protocol

The commands that can be used depend on the CompoWay/F component. Refer to the operation manuals for the components.

Conversion between FINS and CompoWay/F

Normal Conversion

The Open Network Controller converts all FINS commands to text to create

CompoWay/F frames. The responses from CompoWay/F devices are then converted to FINS responses. An example is shown below.

FINS command: 0x0101800000000001

CompoWay/F: 0x30313031383030303030303030303031

(“0101800000000001” in ASCII)

Here, only the FINS-mini command text portion is shown.

The conversion methods for LOOPBACK TEST (08 01) and TEXT STRING

WRITE (41 02), however, are different.

LOOPBACK TEST (08 01)

Conversion

TEXT STRING WRITE

(41 02) Conversion

Only the command code (08 01) is converted to ASCII and the rest of the data is placed in the CompoWay/F frame without conversion (i.e., as binary data).

FINS command: 0x08011234567890

CompoWay/F: 0x303830311234567890

(“0801” in ASCII followed by 1234567890)

Here, only the FINS-mini command text portion is shown.

Only the command code (41 02), beginning write address (2 bytes), and the number of elements (2 bytes) are converted to ASCII and the rest of the data is placed in the CompoWay/F frame without conversion (i.e., as binary data).

FINS command: 0x4102000000011234567890

CompoWay/F: 0x3431303230303030303030311234567890

(“410200000001” in ASCII followed by 1234567890)

Here, only the FINS-mini command text portion is shown.

157

FINS Commands Addressed to DRM_UNIT

Section 5-5

5-5 FINS Commands Addressed to DRM_UNIT

This section describes the FINS commands that can be addressed to

DRM_UNIT. These commands are listed in the following table.

Command code

04 01

04 02

04 03

05 01

08 01

28 01

Name

RUN

STOP

RESET

CONTROLLER DATA READ

LOOPBACK TEST

EXPLICIT MESSAGE SEND

Note

If a command that is not supported is received by DRM_UNIT, it will return an error response with an end code of 04 01. If a timeout occurs when sending a

FINS message to another node, an error response with an end code of 02 05 will be returned. If the destination is not registered in the scan list, an error response with an end code of 01 03 will be returned.

5-5-1 RUN

: 04 01

Starts the scan and enables sending explicit messages.

Command Format

04 01

Command code

Response Format

Precautions

04 01

Command code

End code

A response will be returned when starting the scan is requested from the Device-

Net processor. Access the status data in the event memory to confirm whether or not the scan has actually started.

End code (response)

Refer to

5-8 End Codes

for information on end codes.

158

FINS Commands Addressed to DRM_UNIT

5-5-2 STOP: 04 02

Stops the scan and disables sending explicit messages.

Command Format

04 02

Command code

Response Format

04 02

Section 5-5

Precautions

Command code

End code

A response will be returned when stopping the scan is requested from the DeviceNet processor. Access the status data in the event memory to confirm whether or not the scan has actually stopped.

End code (response)

Refer to

5-8 End Codes

for information on end codes.

5-5-3 RESET: 04 03

Resets DeviceNet hardware.

Command Format

04 03

Response Format

Precautions

Command code

No response.

No response will be returned when the command is executed normally.

159

FINS Commands Addressed to DRM_UNIT

5-5-4 CONTROLLER DATA READ: 05 01

Reads the following information.

Model

Version

Command Format

05 01

Command code

Response Format

05 01

20 bytes 20 bytes

Section 5-5

Command code

End code Model Version

Parameters

Model and Version (response)

The model will always be returned as follows: “DRM_UNIT/QNX-

.”

The version will always be returned as follows:

(

“V2.50

= space)

.”

End code (response)

Refer to

5-8 End Codes

for information on end codes.

5-5-5 LOOPBACK TEST: 08 01

Executes a loopback test with DRM_UNIT.

Command Format

08 01

2,046 bytes max.

Command code

Test data

Response Format

08 01 00 00

Command code

End code

2,046 bytes max.

Text data

Parameters

Test data (command and response)

In the command block, designate the data to be transmitted to DRM_UNIT. In the response block, the test data from the command block will be returned as it is. If the test data in the response block is different from that in the command block, an error has occurred.

End code (response)

Refer to

5-8 End Codes

for information on end codes.

160

FINS Commands Addressed to DRM_UNIT

Section 5-5

5-5-6 EXPLICIT MESSAGE SEND: 28 01

Sends an explicit DeviceNet message to the specified node. Refer to the

CompoBus/D (DeviceNet)Operation Manual

(W267) for information on explicit messages.

Command Format

28 01

507 bytes max.

Command code

Class ID

Service code

Destination MAC ID

Instance ID Service data

Response Format

Normal Response

28 01

511 bytes max.

Command code

Response code

No. of bytes received

Service data

Service code

Destination MAC ID

Error Responses

The following response is returned if an error occurs for the explicit message.

28 01

Command code

Response code

No. of bytes received

Error code

Service code 94 (hex)

Source MAC ID

The following response is returned if the explicit message cannot be sent or times out.

28 01

Command code

Response code

161

FINS Commands Addressed to SYSMAC_UNIT

5-6

Section 5-7

FINS Commands Addressed to CLK_UNIT

The following FINS commands can be addressed to CLK_UNIT.

Refer to the

Controller Link Support Board Operation Manual

(W307) for information on these FINS commands.

Command code

04

05

06

08

21

03

02

03

01

02

01

01

02

03

01

02

OK

OK

OK

OK

OK

OK

Data links

Active

No

OK

Stopped

OK

No

OK

OK

OK

OK

OK

OK

OK

OK

OK

OK

OK

OK

Name

RUN

STOP

CONTROLLER DATA READ

CONTROLLER STATUS READ

NETWORK STATUS READ

DATA LINK STATUS READ

LOOPBACK TEST

BROADCAST TEST RESULTS

READ

BROADCAST TEST DATA SEND

ERROR LOG READ

ERROR LOG CLEAR

5-7 FINS Commands Addressed to SYSMAC_UNIT

This section describes the FINS commands that can be addressed to SYS-

MAC_UNIT.

The FINS commands supported by SYSMAC_UNIT and the SYSMAC Board are not the same, as shown in the following tables.

FINS Commands

Addressed to SYSMAC

Board

The following FINS commands can be addressed to the SYSMAC Board.

05

06

07

Command code

01

04

01

02

01

02

01

01

01

02

Name

MEMORY AREA READ

MEMORY AREA WRITE

RUN

STOP

CONTROLLER DATA READ

CONTROLLER STATUS READ

CLOCK READ

CLOCK WRITE

FINS Commands

Addressed to

SYSMAC_UNIT

The following FINS commands can be addressed to SYSMAC_UNIT.

Command code

05 01 CONTROLLER DATA READ

Name

162

FINS Commands Addressed to SYSMAC_UNIT

Section 5-7

5-7-1 Memory Area Designations

The following table gives the addresses to use when reading or writing memory area data. The

Data area address

column gives the normal addresses used in the PC program. The

Address used in FINS

column gives the addresses used in

FINS commands and responses. These addresses are combined with the memory area codes to specify memory locations.

The

No. of bytes

column specifies the number of bytes of data to read or write for that area.

Area

CIO area Word contents

Word contents

Data area address

Word

CIO 000 to

CIO 255

00

Bit

00

Address used in FINS

Bytes 1 and 2

0000 to 00FF

Byte 3

00

0100 to 01FF 00

80

80

2

2 Expansion

CIO area

LR area

HR area

AR area

TIM/CNT area

DM area

EM area

Word contents

Word contents

Word contents

Completion

Flag status

PV

Word contents

Word contents

LR 00 to LR 63

HR 00 to HR 99

AR 00 to AR 27

TIM/CNT 000 to

TIM/CNT 511

TIM/CNT 000 to

TIM/CNT 511

DM 0000 to

DM 9999

EM 0000 to

EM 6143

00

00

00

00

00

00

00

03E8 to 0427

0428 to 048B

048C to 04A7

0000 to 01FF

0000 to 01FF

0000 to 270F

0000 to 17FF

00

00

00

00

00

00

00

80

80

80

01

81

82

90/98

2

1

2

2

2

2

2

Each address consists of three bytes, as shown below.

Specify the the bit between 00 and 0F (00 to 15).

Set to 00 to specify word data.

Specify the address of the word.

Memory area code 90 can be used to specify bank 0 of the EM area or memory area code 98 can be used to specify the current bank.

The DM area can normally be accessed from DM 0000 to DM 6655. If expanded

DM area is set, DM 7000 to DM 9999 can also be accessed. Accessing DM 6656 to DM 6999 will cause an error to be returned in the FINS response.

163

FINS Commands Addressed to SYSMAC_UNIT

Section 5-7

5-7-2 MEMORY AREA READ: 01 01

Reads the contents of the specified number of consecutive memory area words starting from the specified word.

Command Format

01 01

Command code

Beginning address

Memory area code

No. of items

(binary)

Response Format

01 01

Command code

End code Data (for number of items)

Parameters

Precautions

CIO area

Expansion CIO area

LR area

HR area

AR area

TIM/CNT area

DM area

EM area

Memory area code, beginning address, number of items (command)

Specify the type of data to be read, the beginning address of the data to be read, and the number of items of data to be read (2 digits hexadecimal). The number of items must be between 0000 and 0080 Hex (0 to 128 decimal)

The memory area addresses that can be read are given in the following table.

Area

Word contents

Word contents

Word contents

Word contents

Word contents

Completion

Flag status

PV

Word contents

Word contents

Address used in FINS

Bytes 1 and 2

0000 to 00FF

Byte 3

00

0100 to 01FF

03E8 to 0427

0428 to 048B

048C to 04A7

0000 to 01FF

00

00

00

00

00

0000 to 01FF

0000 to 270F

0000 to 17FF

00

00

00

80

80

01

80

80

80

81

82

90/98

No. of

2

2

2

2

2

1

2

2

2

Data (response)

The data from the specified memory area is returned in sequence starting from the beginning address. The required number of bytes in total is calculated as follows:

Number of bytes required by each item x number of items

You cannot read data in both the CIO and Expansion CIO areas or in both the DM and Expanded DM areas in the same command. An error response will be returned.

Accessing DM 6656 to DM 6999 will cause an error to be returned in the FINS response. These words are reserved by the system.

End code (response)

Refer to

5-8 End Codes

for information on end codes.

164

FINS Commands Addressed to SYSMAC_UNIT

Section 5-7

5-7-3 MEMORY AREA WRITE: 01 02

Writes data to the specified number of consecutive words starting from the specified word.

Command Format

01 02

Command code

Beginning address

Memory area code

No. of items

(binary)

Data (for number of items)

Response Format

01 02

Command code

End code

Parameters

Precautions

Memory area code, beginning address, number of items (command)

Specify the type of data to be written, the beginning address of the data to be written, and the number of items of data to be written (2 digits hexadecimal). The number of items must be between 0000 and 0080 Hex (0 to 128 decimal)

The memory area addresses that can be read are given in the following table.

Area

CIO area

Expansion CIO area

LR area

HR area

AR area

TIM/CNT area

DM area

EM area

Word contents

Word contents

Word contents

Word contents

Word contents

PV

Word contents

Word contents

Address used in FINS

Bytes 1 and 2

0000 to 00FF

Byte 3

00

0100 to 01FF

03E8 to 0427

0428 to 048B

048C to 04A7

0000 to 01FF

0000 to 270F

0000 to 17FF

00

00

00

00

00

00

00

80

80

81

80

80

80

82

90/98

No. of

2

2

2

2

2

2

2

2

Data (response)

The data to be written to the specified memory area in sequence starting from the beginning address. The required number of bytes in total is calculated as follows:

Number of bytes required by each item x number of items

You cannot write data to both the CIO and Expansion CIO areas or to both the

DM and Expanded DM areas in the same command. An error response will be returned.

Accessing DM 6656 to DM 6999 will cause an error to be returned in the FINS response. These words are reserved by the system.

End code (response)

Refer to

5-8 End Codes

for information on end codes.

165

FINS Commands Addressed to SYSMAC_UNIT

5-7-4 RUN

: 04 01

Changes the operating mode to MONITOR or RUN.

Command Format

04 01 00 00

Command code

Program

No.

Mode

Response Format

04 01

Command code

End code

Parameters

Precautions

Section 5-7

Program number (command)

Always 0000 (hex).

Mode (command)

Set the operating mode as follows:

02 (hex):

04 (hex):

Change to MONITOR mode.

Change to RUN mode.

End code (response)

Refer to

5-8 End Codes

for information on end codes.

If the Mode or the Mode and the Program Number are omitted, the operating mode will be changed to MONITOR.

5-7-5 STOP: 04 02

Changes the operating mode to PROGRAM.

Command Format

04 02

Command code

Response Format

04 02

Command code

End code

Parameters

End code (response)

Refer to

5-8 End Codes

for information on end codes.

166

FINS Commands Addressed to SYSMAC_UNIT

5-7-6 CONTROLLER DATA READ: 05 01

Reads the following data:

CPU Unit model and version

Area data and CPU Unit information

Command Format

05 01

Command code

Section 5-7

Response Format

05 01

20 bytes

Command code

End code CPU Unit model

20 bytes

CPU Unit version

16 bytes

Dummy 1

10 bytes

Area data

66 bytes

Dummy 2

CPU Unit information

Parameters

CPU Unit model and version (response)

Each is returned in not more than 20 bytes in ASCII (i.e., 20 ASCII characters). If the model or version requires less than 20 characters, spaces will be inserted to fill the remainder.

Dummy 1 and Dummy 2 (response)

All zeros will be returned.

Area data (response)

All bytes will be 00. The area data is configured as follows:

(a) 00 (b) 00 00 00 (c) (d)

(a)

(b)

(c)

(d)

Item

Program area size

Number of DM words

File memory status

File memory size

Meaning

The size of PC Setup and program area

Total words in the DM area

00: No file memory

01: SRAM

04: First half RAM, second half ROM

Total number of blocks in file memory

0000: No file memory

0001:

0002:

1,000 blocks

2,000 blocks

Unit

Kwords

Words

---

---

Note

One word = two bytes.

CPU Unit information (response)

If a Programming Console is connected, 80 will be returned. If not, 00 will be returned. For the SYSMAC Board, 00 will always be returned.

End code (response)

Refer to

5-8 End Codes

for information on end codes.

167

FINS Commands Addressed to SYSMAC_UNIT

5-7-7 CONTROLLER STATUS READ: 06 01

Reads the operating status of the controller.

Command Format

06 01

Command code

Response Format

06 01

16 bytes

Command code

End code

Status Mode

Fatal error data

Non-fatal error data

FAL/FALS

No.

Error message

Section 5-7

Parameters

Status (response)

The operating status of the CPU Unit is returned as follows:

00:

Stop (user program not being executed)

01:

Run (user program being executed)

80:

CPU on standby (e.g., start switch is OFF or waiting for remote devices to turn ON).

Mode (response)

The CPU Unit operating mode is as follows:

00:

PROGRAM

02:

MONITOR

04:

RUN

Fatal error data (response)

Fatal error data for the CPU Unit is configured as follows:

First byte

Bit

15 14 13

0

12

0

11 10 9 8

0

7

0

Second byte

6 5

0

4

0

3

0

2

0

1 0

FALS error

No END instruction

I/O setting error

I/O point overflow

I/O bus error

Memory error

168

FINS Commands Addressed to SYSMAC_UNIT

Section 5-7

Bit

15 14

0

13

First byte

12

0

11

0

10

0

Non-fatal error data (response)

Non-fatal error data for the CPU Unit is configured as follows:

9 8 7

0

6

0

Second byte

5 4 3

0

2

0

1 0

PC Link error

Host Link error

Battery error

Remote I/O error

Special I/O Unit error

I/O verification error

Cycle time too long

FAL error

FAL/FALS No.(response)

The number of the error at the time the command is executed will be returned.

The FAL/FALS number will be returned as 2 digits of BCD data in the second byte. The first byte will contain 00. The FAL/FALS number will be between 0 and

99 decimal.

Error message (response)

Indicates messages from execution of FAL or FALS instruction in 16 bytes of

ASCII (i.e., 16 ASCII characters). If there is no error message, nothing will be returned.

End code (response)

Refer to

5-8 End Codes

for information on end codes.

5-7-8 CLOCK READ: 07 01

Reads clock information.

Command Format

07 01

Command code

Response Format

07 01

Command code

Year Month Day Hour Minute Second Day of week

Parameters

Year, month, day, hour, minute, second, day of week (response)

The year, month, day of month, hour, minute, and second are expressed in BCD.

Year:

The rightmost two digits of the year.

Hour:

00 to 23 (BCD).

Day of week:

As follows:

Value (Hex)

Day of week

00

Sun

01

Mon

02

Tues

03

Wed

End code (response)

Refer to

5-8 End Codes

for information on end codes.

04

Thur Fri

05 06

Sat

5-7-9 CLOCK WRITE: 07 02

Writes clock information.

169

FINS Commands Addressed to SYSMAC_UNIT

Command Format

07 02

Command code

Year Month Day Hour Minute Second Day of week

Response Format

07 02

Section 5-7

Command code

End code

Parameters

Year, month, day, hour, minute, second, day of week (command)

The year, month, day of month, hour, minute, and second are expressed in BCD.

The second data may be omitted. The day of week data may also be omitted will not be used even if specified (see below.)

Year:

The rightmost two digits of the year.

Hour:

00 to 23 (BCD).

Day of week:

The day of the week will be calculated from the year, month, and day. The value in the command will be ignored.

Value (Hex)

Day of week

00

Sun

01

Mon

02

Tues

03

Wed

04

Thur Fri

05 06

Sat

End code (response)

Refer to

5-8 End Codes

for information on end codes.

5-7-10 CONTROLLER DATA READ: 05 01

Reads the following data from the SYSMAC_UNIT running on the Open Network Controller.

Model

Version

Command Format

05 01

Command code

Response Format

05 01

20 bytes 20 bytes

Command code

End code SYSMAC_UNIT model

SYSMAC_UNIT version

Parameters

SYSMAC_UNIT model and version (response)

Each is returned in not more than 20 bytes in ASCII (i.e. 20 ASCII characters). If the model or version requires less than 20 characters, spaces will be inserted to fill the remainder.

170

End Codes

5-8

Section 5-8

End Codes

Bit

7

1

End codes (also called response codes) are two-bytes codes returned in responses to FINS commands to indicate the results of command executed. The end codes are structured as follows:

First byte

6 5 4 3

Main response code

2 1 0 7 6

Second byte

5 4 3 2

Sub-response code

1 0

Fatal CPU Unit error Non-fatal CPU Unit error

Relay error

The main response codes classifies the type of error and the sub-response code provides details on specific errors.

Bit 7 of the first byte will be ON if an error occurred in relaying between networks.

In this case too, the contents of the second byte will provide details on the specific error that occurred. Further information on relay error can be found in the

FINS

Commands Reference Manual

(W227).

Bit 6 or bit 7 of the second byte will be ON if a non-fatal or fatal error has occurred in the CPU Unit or host computer at the destination. Refer to documentation for the host computer or PLC at the destination and remove the error.

Depending on the command, the destination code will sometimes make a request of another node on a network. The other node is referred to as the third node.

The following table lists the main response codes and the sub-response codes returned for a FINS command. The probable cause and corrections for each error code are also given.

171

End Codes

Section 5-8

Main code

00: Normal

01: Local node

02: Destination node error

Subcode

00: Normal completion

01: Service

01: Local node not in network

02: Token timeout

03: Retries failed

04: Too many send frames

05: Node address range error

---

---

Check point

Data link status

Network status of local node

Maximum node address

---

06: Node address duplication

01: Destination node not in network

02: Unit missing

03: Third node missing

Instruction control data

Instruction control data

---

Service was cancelled.

Service was cancelled.

Local node is not participating in the network.

Token doesn’t arrive.

There is no Unit with the specified unit address.

The third node does not exist.

Probable cause

---

Correction

Check the capacity of the destination area in the third node.

Check the status of the data link.

Connect the node to the network.

Number of enabled send frames

Node address

Node addresses

INS indicator on

Unit

Send was not possible during the specified number of retries.

Cannot send because maximum number of event frames exceeded.

Node address setting error occurred.

The same node address has been set twice in the same network.

The destination node is not in the network.

Set the local node to within the maximum node address.

Execute a communications test between the nodes and re-examine the system environment if it fails.

Check event execution on the network and reduce the number of events per cycle.

Increase the maximum number of event frames.

Check the settings of the rotary switches to be sure that the address is within range and that each address is set only once in the same network.

Change the address of one of the nodes with the same address.

Add the destination node to the network.

04: Destination node busy

05: Response

Command data

---

---

Instruction control data

Error history

Broadcasting was specified.

The destination node is busy.

The destination node does not exist.

The message was destroyed by noise.

The response monitor time is too short.

The send/receive frame was discarded.

Check the destination unit address.

Check the unit address of the third node. Check the node address of the third node in the send data for

CMND(490).

Specify only one node for the third node.

Increase the number of retries or review the system so that the destination node does not receive so many messages.

Check the settings for the destination node.

Increase the number of retries or test communications between nodes to see if there is too much noise.

Increase the length of the response monitor time.

Take appropriate measures based on the error history.

172

End Codes

Section 5-8

Main code

03: Controller error

04: Service unsupported

05: Routing table error

10: Command format error

Subcode

01: Communications controller error

02: CPU Unit error

03: Controller error

04: Unit number error

01: Undefined command

02: Not supported by model/version

03: Routing table error

04: Too many relays

01: Command too long

02: Command too short

03: Elements/ data don’t match

04: Command format error

05: Header error

Check point

Unit/Board indicators

01: Destination address setting error

02: No routing tables

Routing table

Routing table

Probable cause

An error occurred in the communications controller.

Correction

Take appropriate measures based on the operation manuals for the related Units/Boards.

Clear the error from the CPU Unit based on its operation manuals.

CPU Unit indicators at destination node

Board indicators

Unit number

Command code

Unit model and version

Routing table

Network configuration

Command data

Command data

Command data

Command data

Routing table

A CPU error occurred in the destination CPU Unit.

A response was not returned because an error occurred in the Board.

The unit number was set incorrectly.

Check network communications status and restart the Board. If the problem persists, replace the

Board.

Set the rotary switches correctly, being sure the unit numbers are within range and that each number is used only once.

Check the command code.

The Unit/Board does not support the specified command code.

The command cannot be executed because the model or version is incorrect.

The destination network or node address is not set in the routing tables.

Relaying is not possible because there are no routing tables.

There is an error in the routing tables.

An attempt was made to send to a network that was over 3 networks away.

Check the model number and version.

Register the destination network and node in the routing tables.

Set routing tables in the source node, designation node, and relay nodes.

Set the routing tables correctly.

The command is longer than the maximum permissible length.

The command is shorter than the minimum permissible length.

The designated number of elements differs from the number of write data items.

An incorrect format was used.

Either the relay table in the local node or the local network table in the relay node is incorrect.

Reconstruct the networks or change the routing tables so that commands are sent within a range of 3 networks or less.

Check the command format and correct the command data.

Check the command format and correct the command data.

Check the number of elements and set data for each element.

Check the command format and correct the command data.

Set the routing tables correctly.

173

End Codes

Section 5-8

Main code

11: Parameter error

Subcode

01: Area classification missing

02: Access size error

03: Address range error

04: Address range exceeded

06: Program missing

09: Relational error

0A: Duplicate data access

0B: Response too long

0C: Parameter

Check point

Memory area code in command data

Access size specification in command data

Starting address in command data

Starting address and number of elements in command data

Data link tables

Outside of time compensation range

Program number in command data

Command data

Data link table

I/O access in

CPU Unit

Data link tables

Number of elements in command data

Parameters in command data

Data link table file

Probable cause

The specified word does not exist in the memory area or there is no EM Area.

The access size specification is incorrect or an odd word address is specified.

The start address in command process is beyond the accessible area.

The end address in command process is beyond the accessible area.

The total number of words is beyond the limit.

Exceeds permissible range of time compensation.

A non-existent program has been specified.

A large-small relationship in the elements in the command data is incorrect.

A node not set in the common link parameters is set as a refresh parameter.

Differential monitoring was specified during data tracing or data tracing was specified during differential monitoring.

The same node address is specified more than once.

The response format is longer than the maximum permissible length.

There is an error in one of the parameter settings.

There is an error in the file.

Correction

Check the memory areas and parameter codes in the command and correct the command data.

Check the memory areas and access size and correct the access size.

Check the area being processed and set the correct range.

Check the area being processed and set the correct range.

Correct the data link tables.

Set a time within the permissible range of time compensation.

Check the program numbers and specify a valid one.

Check the command data and correct the relationship between the elements.

Correct the data link tables.

Abort the current process or wait until it ends before executing the command.

Correct the data link tables.

Check the command format and correct the number of elements.

Check the command data and correct the parameters.

Check the contents of the file.

174

End Codes

Section 5-8

Main code

20: Read not possible

21: Write not possible

Subcode

02: Protected

03: Table

---

Check point

Table

04: Data missing

05: Program missing

06: File missing

07: Data mismatch

01: Read-only

---

Program number in command data

File name and file device

Contents of memory being compared

---

---

02: Protected

Cannot write data link table

03: Cannot register

---

PC Setup

Number of files in file device

Number of files open

Probable cause

The program area is protected.

A table has not been registered.

There is an error in the table.

The search data does not exist.

A non-existing program number has been specified.

The file does not exist at the specified file device.

A data being compared is not the same.

Correction

Release protection from a

Programming Device and then execute the command.

Register a table.

Correct the table.

---

Check the program numbers and specify a valid one.

Check the path and file name, and correct them.

Check memory contents and use the correct data.

A file read operation failed.

The specified area is read-only.

The program area is protected.

Check the contents of the file.

If the area is protected using a switch setting, release protection and then execute the command. If the area is permanently read-only, the command cannot be executed.

Release protection from a

Programming Device and then execute the command.

Change the PC Setup so that the data link tables can be manually written.

Writing is not possible because automatic data link table generation has been specified.

The file cannot be created because the limit has been exceeded.

The maximum number of files has already been opened for the system limit.

A non-existent program number has been specified.

Delete any unnecessary files or create more file memory.

Close one or more files and then execute the command.

Check the program numbers and specify a valid one.

05: Program missing

Program number in command data

File name 06: File missing

07: File name already exists

File name

08: Cannot change

Contents of memory being changed

The file does not exist at the specified file device.

A file with the same name already exists in the specified file device.

The change cannot be made because doing so would create a problem.

Correct the file name and then execute the command.

Change the name of the file being written and then execute the command.

---

175

End Codes

Section 5-8

Main code

22: Not current mode

23: No such

24: Cannot start/stop

Subcode

01: Not execution

02: Not

---

Check point

Data link status

---

Data link status

--running

03: Wrong PC mode

04: Wrong PC mode

05: Wrong PC mode

06: Wrong PC mode

07: Specified node not polling node

08: Step cannot be executed

01: File device missing

02: Memory missing

03: Clock missing

05: Ethernet setting error

01: Table missing

---

---

---

---

---

Unit configuration

---

---

IP-FINS address conversion settings

Data link tables

Probable cause

The mode is incorrect.

The data link is operating.

The mode is incorrect.

The data links are active.

The PC is in PROGRAM mode.

The PC is in DEBUG mode.

The PC is in MONITOR mode.

The PC is in RUN mode.

The specified node is not the polling node.

The mode is incorrect.

The specified memory does not exist as a file device.

There is no file memory.

There is no clock.

The IP address of the destination node has not been set.

The data link tables have not been registered or they contain an error.

Correction

Check the mode.

Check the status of the data links.

Check the mode.

Check the status of the data links.

Check the modes of the PC and computer.

Check the modes of the PC and computer.

Check the modes of the PC and computer.

Check the modes of the PC and computer.

Check node functioning as the polling node for the network.

Check step status.

Mount memory or format EM as file memory.

Check the file memory to see if it is mounted.

Check the model.

Executed SETUP and add the IP address setting for the destination node.

Set the data link tables.

176

End Codes

Section 5-8

Main code

25: Unit error

Subcode

02:Parity or checksum error

03: I/O setting error

04: Too many

I/O points

05: CPU bus error

06: I/O duplication

07: I/O bus error

09: SYSMAC

BUS/2 error

0A: CPU Bus

Unit error

0D: SYSMAC

BUS No.

duplication

0F: Memory error

Check point

Contents of memory being processed

I/O Unit configuration

Probable cause

The contents of memory contains an error.

Number of I/O in registered I/O tables

CPU bus line

The registered I/O tables do not agree with the actual I/O configuration.

There are too many I/O points and remote I/O points registered.

An error occurred in data transfer between the CPU and a CPU Bus Unit.

Rack numbers,

Unit numbers, and I/O addresses in PC

Setup

I/O bus line

The same number/address was set more than once.

An error occurred in data transfer between the CPU and an I/O Unit.

Correction

Transfer the correct contents to memory.

Correct the I/O tables or the I/O configuration.

Change the registered I/O table so that it is within the limit.

Check Units, Boards, and cables to be sure they are connected correctly and then execute the

ERROR CLEAR command.

Check the PC Setup and correct the numbers/addresses so that each is used only once.

SYSMAC

BUS/2 transmission path

CPU Bus Unit transmission path

Word settings

An error occurred in data transfer on the SYSMAC

BUS/2 line.

An error occurred in data transfer for a CPU Bus Unit.

The same word is allocated more than once.

Check Units, Boards, and cables to be sure they are connected correctly and then execute the

ERROR CLEAR command.

Check Units, Boards, and cables to be sure they are connected correctly and then execute the

ERROR CLEAR command.

Check Units, Boards, and cables to be sure they are connected correctly and then execute the

ERROR CLEAR command.

Check the I/O tables and correct the allocations.

Status of memory being processed

10: SYSMAC

BUS terminator missing

---

A memory error has occurred in internal memory, a memory card, or EM file memory.

Terminators have not been set.

For internal memory, write the correct data and then execute the command.

For a memory card or EM file memory, the file data has been destroyed. Execute the FILE

MEMORY FORMAT command.

If the problem persists, replace the memory.

Set the terminators correctly.

177

End Codes

Section 5-8

Main code

26: Command error

Subcode

01: No protection

02: Incorrect password

04: Protected

05: Service already executing

06: Service stopped

07: No execution right

08: Settings not complete

09: Necessary items not set

Check point

Command protection for program area

Number of commands being executed

---

---

LNK indicator on Unit/Board

Settings required before execution

Command data

0A: Number already defined

30: Access right error

0B: Error will not clear

01: No access right

Action numbers and transition numbers of program in program area

Cause of error being cleared

---

40: Abort 01: Service aborted

---

---

---

---

Probable cause

The specified area is not protected.

Correction

An attempt was made to clear protection on an area that is not protected, i.e., there is no reason to clear protection.

Specify the correct password.

An incorrect password has been specified.

The specified area is protected.

The node receiving the command is already processing 5 commands.

The service is being executed.

Clear protection from a

Programming Device and then execute the command.

Wait for current processing to end or force the end of a current process and then execute the command.

Wait for the service to end or force the end of the service and then execute the command.

If necessary, start the service.

The service is not being executed.

The right to execute the service has not been obtained.

A response was not returned because a buffer error occurred.

The settings required before executing the service have not been made.

The required elements have not been set in the command data.

The specified action/ transition number has already been registered in a previous program.

The local node is not in the data link. Execute the command from a node that is participating in the data link.

Restart the Board. If the problem persists, replace the Board.

Make the required settings.

Check the command format and set the required elements in the command data.

Check the action/transition numbers to ones that are not being used and then execute the command.

The cause of the error has not been removed.

The access right is held by another device. (SFC online editing is being executed from another node or

ACCESS RIGHT ACQUIRE or ACCESS RIGHT FORCE

ACQUIRE has been executed by another node.)

Service was aborted with

ABORT command.

Remove the cause of the error and then execute ERROR CLEAR.

Wait until the access right is released and then execute the command.

ACCESS RIGHT ACQUIRE or

ACCESS RIGHT FORCE

ACQUIRE can be executed to obtain the access right, but this may adversely affect processing by the node that previously held the access right.

---

178

SECTION 6

ITNC-EIS01-CST and ITNC-EIX01-CST (CS1 Bus Interface)

This section describes the ITNC-EIS01-CST and ITNC-EIX01-CST Open Network Controllers.

6-1

6-2

6-3

6-4

6-5

Introduction

6-1-1

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-1-2 Product Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Functions

6-2-1

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Connections with PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-2-2

6-2-3

BUSCS1_UNIT (CS1 Bus Connection NP) Functions

Precautions on System Design

. . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Hardware Settings

Software Settings

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-4-1 CS1 Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-4-2 File Settings in Open Network Controller

FINS Commands

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-5-1

6-5-2

FINS Commands for BUSCS1_UNIT and CPU Bus Unit

FINS Command for BUSCS1UNIT

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6-5-3 FINS Commands for CPU Bus Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

184

187

187

188

191

191

191

191

180

180

180

181

181

182

183

179

Introduction

Section 6-1

6-1 Introduction

6-1-1 Overview

The ITNC-EIS01-CST or ITNC-EIX01-CST Open Network Controller provides an interface to connect to the I/O bus of a CS1-series Programmable Controllers. These Open Network Controllers function as CS1-series CPU BUS Units.

This section provides information on the unique functions of the ITNC-

EIS01-CST and ITNS-EIX01-CST. For the basic functions of Open Network

Controllers, refer to

Section 1

through

Section 5

.

6-1-2 Product Configurations

ITNC-EIS01-CST

Standard Model with CS1

Bus Interface

The ITNC-EIS01-CST Standard Model is shown below. Use the illustration to confirm you have the correct model.

Safety Precautions

ITNC-EIX01-CST

Expansion Model with

CS1 Bus Interface

ITNC-EIS01-CST Safety Precautions

The ITNC-EIX01-CST Expansion Model is shown below. Use the illustration to confirm you have the correct model.

Safety Precautions

ITNC-EIX01-CST Safety Precautions

180

Functions

ITBC-CN -CST I/O

Connecting Cable

Section 6-2

The ITBT-CN -CST is shown below. Use the illustration to confirm you have the correct model. The cable length varies with the model as listed in the following table.

Length Model

ITBC-CN001-CST

ITBC-CN005-CST

ITBC-CN012-CST

1 m

5 m

12 m

ITBC-CN -CST

6-2 Functions

6-2-1 Connections with PC

As shown below, the ITNC-EIS01-CST or ITNC-EIX01-CST Open Network

Controller connects to the CPU Rack or CS1 Expansion Rack. These Open Network Controllers function as CS1-series CPU Bus Units and perform I/O communications with the Programmable Controller.

Example of Connections to CPU Rack Example of Connections to CS1

Expansion Rack

CPU Rack

(excluding

2-slot models)

CPU Rack

(excluding

2-slot models)

I/O

Connecting

Cable

Power supply

Open Network

Controller

CS1

Connecting

Cable

Power supply

CS1

Expansion

Rack

As shown on the right, the CPU Unit recognizes the Open Network

Controller as a CPU Bus

Unit mounted to the leftmost slot of the farthest CS1 Expansion

Rack.

Virtual CS1

Expansion Rack

Power supply

CPU Bus Unit

CS1

Connecting

Cable

I/O

Connecting

Cable

Power supply

CS1

Expansion

Rack

Max. number of CS1

Expansion

Racks: 7

Power supply

Open

Network

Controller

Note

1. Connect the Open Network Controller to the farthest CS1 Expansion Rack.

181

Functions

Section 6-2

2. The Open Network Controller is treated as a CS1 Expansion Rack. Therefore, count the Open Network Controller as a CS1 Expansion Rack when calculating the maximum number of connectable CS1 Expansion Racks.

3. The maximum available cable length including the length of the I/O Connecting Cable to the Open Network Controller is 12 m.

4. The Open Network Controller cannot be connected to a C200H Rack.

Refer to

2-1 System Configuration

for network connection examples.

6-2-2 BUSCS1_UNIT (CS1 Bus Connection NP) Functions

The BUSCS1_UNIT is a software component that enables I/O communications through a CS1 bus connection and FINS communications with the CS1-series

PC.

As shown below, the BUSCS1_UNIT and the CPU Bus Unit are treated as different nodes on the FINS network.

Power supply

CS1 CPU Unit

CPU Bus Unit

Open Network Controller

CS1 bus expansion connector

Solid line: Actual cable

Dotted line: Virtual cable implemented by software running in the Open

Network Controller

Virtual CS1 Expansion Rack

FINS network

CS1 CPU Unit I/O

Memory Allocations to

Event Memory

Note

The BUSCS1_UNIT and CPU Bus Unit on the Open Network Controller are enabled by the BUSCS1_UNIT NP through a CS1 bus connection.

The I/O memory of the CS1-series CPU Unit can be allocated to the event memory to enable data I/O communications between the CS1 CPU Unit and

Open Network Controller.

The following memory areas are can be allocated.

20 input areas (Data is written from the memory of the CS1 CPU Unit to the event memory of the Open Network Controller.)

20 output areas (Data is written from the event memory of the Open Network

Controller to the memory of the CS1 CPU Unit.)

Data can be allocated for up to 7,784 words of the memory.

Event memory

I/O memory of the

CS1 CPU Unit

182

Functions

Section 6-2

FINS Commands

Supported by

BUSCS1_UNIT and CPU

Bus Unit

As shown below, the BUSCS1_UNIT and the CPU Bus Unit do not support the same FINS commands.

Refer to

6-5 FINS Commands

for details.

FINS Command for BUSCS1_UNIT

The BUSCS1_UNIT supports the following FINS command.

0501

Command code Name

CONTROLLER DATA READ

FINS Commands for CPU Bus Unit

The CPU Bus Unit supports the following FINS commands.

Command code

0501

2102

2103

Name

CONTROLLER DATA READ

ERROR LOG READ

ERROR LOG CLEAR

6-2-3 Precautions on System Design

The PC will not start operation even after the power supply is turned ON until the

CS1 Bus Interface in the Open Network Controller completes initialization. The

Open Network Controller requires approximately 40 seconds to start operation after the power supply is turned ON. You must design the system to allow for this delay.

Also, if the power supply to the Open Network Controller is interrupted during operation, the PC will detect an I/O bus error. You must design the system to allow for this possibility.

183

Hardware Settings

Section 6-3

6-3 Hardware Settings

Nomenclature and

Functions

This section gives the names and describes the functions of the ITNC-

EIS01-CST and ITNC-EIX01-CST.

The names and functions of the Open Network Controller components will be described using the ITNC-EIX01-CST Expansion Model with a CS1 Bus Interface as an example. The ITNC-EIS01-CST Standard Model with a CS1 Bus Interface is the same, except that it does not have a COM3 port or a connector for

Expansion Boards.

DIP switch

Backup battery

184

Power supply terminal block

LAN port

7-segment display

Indicators

Expansion slot cover

CS1 bus interface connector

Unit number setting switch

CS1 bus indicator

Memory Card slot

Card bracket

Card eject button

Name

DIP switch

Card switch

Backup battery

Function

The DIP switch is used to make COM port and 7-segment display settings.

The backup battery backs up the real-time clock and the

CMOS RAM. Replace with a C500-BAT08 Battery when required.

Hardware Settings

Section 6-3

Name

Power supply terminal block

LAN port

COM1

COM2

COM3 (only with

Expansion Models)

Expansion slot cover

(ITNC-EIX01-CST only)

Indicators

Function

The power supply terminal block connects to a 24-V DC power supply.

An Ethernet cable for 10Base-T is connected to the

Ethernet port.

RS-232C

RS-232C

RS-422A/485

The expansion slot is an ISA bus slot. Remove the cover to mount a Controller Link or SYSMAC Board.

7-segment display

Memory Card slot

Card bracket

Card switch

Card eject button

CS1 bus interface connector

Unit number setting switch

The indicators show the status of Open Network Controller operation.

The 7-segment display shows the error code, IP address,

MAC ID on the DeviceNet network, or the FINS address, according to the DIP switch settings.

A Memory Card is mounted in this slot.

This bracket holds the Memory Card in place. Be sure to secure the Card with this bracket.

Press the card switch when inserting or removing a

Memory Card.

When inserting a Memory Card, press this switch to enable using the card. The CARD indicator will light.

When removing the Memory Card, press this switch to enable removing the card. The CARD indicator will turn OFF.

Press the card eject button to remove the Memory Card.

Before pressing this button, press the card switch and make sure the CARD indicator is not lit.

Connect the I/O Connecting Cable to the connector.

CS1 bus indicator

Use this switch to set the Unit number of the Open Network

Controller (as a CPU Bus Unit) for CS1 bus connections.

Refer to

6-2 Functions

for information on the CPU Bus

Unit.

The indicator shows the status of the CS1 bus. Refer to

7-3

Error Messages with the ITNC-EIS01-CST or

ITNC-EIX01-CST

for details.

Note

This section provides information on the CS1 bus indicator, how to set the Unit number setting switch, and how to connect the I/O expansion cable for the CS1.

Refer to

Section 3 Hardware

for information on the other indicators, how to connect the Expansion Board, how to make settings in the Open Network Controller, and how to connect cables.

185

Hardware Settings

CS1 Bus Indicator

Section 6-3

The following table provides information on the CS1 bus indicator. Refer to

Section 3 Hardware

for information on the other indicators.

Indicator

RUN

ERC

ERH

Name

Controller error

PLC error

Color

Green

Red

Red

Status

Lit

Not lit

Lit

Not lit

Lit

Not lit

Meaning

The CPU Bus Unit is operating.

The CPU Bus Unit is not operating.

The CPU Bus Unit has an error.

The CPU Bus Unit has no errors.

The CS1 CPU Unit has an error.

The CS1 CPU Unit has no errors.

Seven-segment Display

(Node Number Display)

Unit Number Settings

By setting pin 2 of DIP switch 2 to OFF and setting pin 3 to ON, the node number of the CPU Bus Unit will appear on the 7-segment display.

Refer to

Section 3 Hardware

for details on the 7-segment display and DIP switch settings.

Use the Unit number setting switch to set the Unit number of the Open Network

Controller as a CPU Bus Unit for CS1 bus connection.

Note

Refer to

6-2 Functions

for details on the CPU Bus Unit.

Set the Unit number to between 0 and 5 (i.e., 0 and 15). Check that the Unit number is not used by any other CPU Bus Unit, such as an Ethernet Unit or Controller

Link Unit.

I/O Connecting Cable

186

Use an I/O Connecting Cable to connect the Open Network Controller and the

CS1 CPU Unit or CS1 Expansion Rack.

Software Settings

Section 6-4

Note

Turn OFF the CS1 and the Open Network Controller before connecting the I/O

Connecting Cable.

1, 2, 3...

1. As shown below, connect the smaller connector (50-pin connector) of the

I/O Connecting Cable to the CS1 bus interface connector of the Open Network Controller.

2. Connect the larger connector (68-pin connector) of the I/O Connecting

Cable to the expansion connector of the CS1 CPU Rack or CS1 Expansion

Rack.

Example: CS1 CPU Rack

Note

When the CS1 Expansion Rack is used, connect the cable to the OUT connector of the farthest CS1 Expansion Rack.

6-4 Software Settings

This section provides information on how to make the following software settings.

CS1 Settings

I/O table creation and routing table settings

Open Network Controller Settings

/etc/FgwQnx/FgwQnx.ini

/etc/FgwQnx/FgwQnxBUSCS1.ini

/etc/FgwQnx/FgwQnxBUSCS1Map.ini

6-4-1 CS1 Settings

Use the CX-Programmer and CX-Net to make CS1 I/O table settings and routing table settings.

187

Software Settings

Section 6-4

I/O Table Creation

Note

Take the following procedure to create the CS1 I/O tables with the CX-Programmer.

1. Before creating the I/O tables with the CX-Programmer, refer to

6-3 Hardware Settings

and connect the Open Network Controller and the CS1 through the CS1 bus and turn ON the Open Network Controller and the CS1, or otherwise the I/O table cannot be created.

2. The Open Network Controller will detect an error (0043) unless the I/O tables is created. Refer to

7-3 Error Messages with the ITNC-EIS01-CST or

ITNC-EIX01-CST

for details.

1, 2, 3...

1. Connect the Open Network Controller and CS1 through the CS1 bus and turn ON the Open Network Controller and the CS1.

2. Connect the CX-Programmer and the CS1 online.

3. Select

PLC

,

Operation Mode

, and

Program

in the CX-Programmer. The

PC will be set to PROGRAM mode. This step is not necessary if the PC has been already set to PROGRAM mode.

4. Select

PLC

,

Edit

, and

I/O Table

(or double-click

I/O Table

in the project work space).

The I/O Table Window will be displayed then. This I/O table has already been saved in the hard disk of the personal computer.

5. Select

Options

and

Create

in the I/O Table Window.

Data on the actual I/O tables (i.e., data on the Units actually connected to the

CS1) will be copied to the registered I/O table in the CS1.

Routing Table Settings

Note

Use the CX-Net to set the routing tables to be registered in the CS1. Set the local network table of the Open Network Controller (as a CPU Bus Unit) together with the relay network table, if necessary, in the routing tables.

Refer to the

CX-Programmer Operation Manual

for information on how to use the CX-Net. Pay attention to the following points when using the CX-Net.

1. The routing tables are not required if no FINS communications are made.

2. When the routing tables are transferred from the CX-Net to the CPU Unit, the CPU Bus Unit will be reset. This will enable the CPU Bus Unit to validate the routing tables after they have been read. Before transferring the routing tables, check that the system will not cause any problems when the CPU

Bus Unit is reset.

3. Check that the local network number set with the routing tables is the same as the /etc/FgwQnx/FgwQnx.ini value set in

LocalNetworks

. Refer to the information below for the /etc/FwgQnx/FgwQnx.ini settings.

6-4-2 File Settings in Open Network Controller

Make the following file settings in the Open Network Controller.

File name

/etc/FgwQnx/FgwQnx.ini

/etc/FgwQnx/FgwQnxBUSCS1.ini

/etc/FgwQnx/FgwQnxBUSCS1Map.ini

Contents

Used for the BUSCS1_UNIT startup and local network table settings.

Used for the node number settings for the

BUSCS1_UNIT and CPU Bus Unit. Refer to

BUSCS1_UNIT (CS1 Bus Connection

NP) Functions

on page 182 for the relationship between the BUSCS1_UNIT and the CPU Bus Unit.

Used for allocating data from the event memory of the Open Network Controller to the I/O memory of the CS1 CPU Unit.

The following section provides information on how to set the above files.

188

Software Settings

/etc/FgwQnx/FgwQnx.ini

Section 6-4

Make the service startup and local network table settings in this file.

/etc/FgwQnx/FgwQnx.ini

The setting items explained here are only those related to the

ITNC-EIS01-CST or ITNC-EIX01-CST. Refer to

Section 4

Software Settings

for other setting items.

Set the relay network table if necessary.

The item

BUSCS1

set by default is required. To start other services, describe the name of service in the services section.

Set the Unit number.

Change the Unit number if necessary.

Set the local network table.

Set the local network number and Unit number of the CPU Bus Unit, separating each with a comma.

The local network number must coincide with that in the routing tables registered in the CS1 CPU Unit.

The routing tables are not required if I/O communications through the CS1 bus are made without FINS communications.

/etc/FgwQnx/FgwQnxBU

SCS1.ini

Note

Set the node numbers of the BUSCS1_UNIT and CPU Bus Unit in this file.

Refer to

BUSCS1_UNIT (CS1 Bus Connection NP) Functions

on page 182 for the relationship between the BUSCS1_UNIT and CPU Bus Unit.

/etc/FgwQnx/FgwQnxBUSCS1.ini

Set the node number of the BUSCS1_UNIT.

Change the node number if necessary.

Set the refresh interval of the I/O memory in milliseconds

Set the interval that is longer than the ladder cycle time.

Set the resetting method of the CPU Bus Unit with the set value written to the CS1’s AR501. (See note.)

0: The Open Network Controller is hardware reset.

1: Only the BUSCS1_UNIT (NP) is software reset.

Determine whether the Open Network Controller’s clock is synchronized with the CS1’s clock.

0: Not synchronized.

1: The CS1’s clock and the Open Network Controller’s clock will be synchronized once when the Open Network

Controller starts.

Set the node number of the CPU Bus Unit.

Change the node number if necessary.

Note

Refer to the

CS1 Series Operation Manual

for information on how to write data to

AR501.

189

Software Settings

/etc/FgwQnx/FgwQnxBU

SCS1Map.ini

Section 6-4

Use this file to allocate data from the I/O memory of the CS1 CPU Unit to the event memory of the Open Network Controller.

/etc/FgwQnx/FgwQnxBUSCS1Map.ini

Number of lines in map section.

A total of 40 lines (20 lines for inputs and 20 lines for outputs) can be used.

Don’t change these values.

The following areas and sizes are available.

20 input areas: The data in the I/O memory of the CS1 is written to the event memory of the Open Network Controller.

20 output areas: The data written to the event memory of the Open Network

Controller is output to the memory of the Programmable Controller.

Use a total of 20 or less I/O areas. The execution performance of the ladder program will be affected if more than 20 areas are used.

A total of 7,784 words can be allocated.

Format

[MapNum]

Set

Maps

to the number of lines to execute in the

Map

section. For example, is

Maps

is set to 2, the first two lines set in the

Map

section will be executed.

[Map]

Set 1 (fixed), the CS1 area, the CS1 address, the event memory area, the event memory address, the transfer size, and the transfer direction, separating each with a comma, as described below.

1

CS1 area

Item

CS1 address

Event memory area

Event memory address

Transfer size

Description

Always add “1” at the beginning of the format.

Specify the I/O memory area in the CS1 CPU Unit. The following areas can be specified.

AR, TF, CF, CIO, HR, WR, TIM, CNT, DM, EM0 to EMC

Specify the address of the first word.

Specify the memory area in event memory, i.e., CIO or DM.

Specify the address of the first word.

Transfer direction

Specify the number of words transferred. Up to 7,784 words are available.

Specify the data transfer direction.

0: Input (Data is copied from the CS1 CPU Unit to the event memory.)

1: Output (Data is copied from the event memory to the

CS1 CPU Unit.)

Note

The total number of words transferred must not exceed 7,784.

190

FINS Commands

Section 6-5

6-5 FINS Commands

This section explains the FINS commands for the BUSCS1_UNIT and CPU Bus

Unit.

6-5-1 FINS Commands for BUSCS1_UNIT and CPU Bus Unit

As shown below, the BUSCS1_UNIT and the CPU Bus Unit do not support the same FINS commands.

FINS Command for BUSCS1_UNIT

The BUSCS1_UNIT supports the following FINS command.

0501

Command code Name

CONTROLLER DATA READ

FINS Commands for CPU Bus Unit

The CPU Bus Unit supports the following FINS commands.

Command code

0501

2102

2103

Name

CONTROLLER DATA READ

ERROR LOG READ

ERROR LOG CLEAR

6-5-2 FINS Command for BUSCS1UNIT

CONTROLLER DATA READ: 0501

Reads the following data from the BUSCS1UNIT.

Command Format

05 01

Command code

Response Format

05 01

Command code

End code BUSCS1

UNIT model

Version

BUSC1UNIT Model and

Version (Response)

The model and version are returned as follows:

Model: BUSCS1_UNIT/QNX

Version: V2.50 (Spaces will be inserted to fill the remainder.)

6-5-3 FINS Commands for CPU Bus Unit

CONTROLLER DATA READ: 0501

Reads the following data from the CPU Bus Unit.

Command Format

05 01

Command code

20 bytes 20 bytes

191

FINS Commands

Response Format

Section 6-5

05 01 20 bytes 20 bytes 30 bytes

Command code

End code CPU Bus

Unit Model

Version Reserved data

CPU Bus Unit Model and

Version (Response)

The model and version are returned as follows:

Model: ITNC-EIS01/EIX01-CST

Version: V2.50 (Spaces will be inserted to fill the remainder.)

ERROR LOG READ: 2102

Reads the error log of the CPU Bus Unit. The records read will be deleted from the error log.

Command Format

21 02 00 00

Command code

Beginning record No.

Number of read records

Response Format

21 02 00 80

Command code

End code Max. No. of records

Present No.

of records

No. of read records

Error code Detailed data

Minute Second Day Hour Year Month

Parameters

Beginning Record No. (Command)

Fixed at 0000.

No. of Read Records (Command)

Specify the number of records up to 128 (80 Hex). If the specified number exceeds the actual number of errors in the error log, all the error log will be read in a normal response format.

Max. No. of Records (Response)

Always 0080 (128 records).

Present No. of Records (Response)

The number of records remaining after the command is executed will be returned. When the number of read records is set to 0, the present number of records will be returned so that the user can check the number of records remaining in the error log.

No. of Read Records (Response)

The number of records actually read will be returned.

Error Code, Detailed Data, and Response

Data on the error log is returned. If there is no detailed data, 0000 will be returned. Refer to the

Error Log Error Codes

for details.

Minute, Second, Day, Hour, Year, and Month (Response)

Based on the time data of the Open Network Controller, the time of each error occurred will be stored in BCD.

192

FINS Commands

Section 6-5

Error Log Error Codes

Error code

0118

0118

000f

Detailed data

0000

0001

0000

Meaning

The FINS response exceeded

2,000 bytes.

The FINS response exceeded

2,000 bytes.

The access right to the cyclic area could not be obtained.

0006

021a

0112

010b

010e

0110

0108

010d

010e

0124

0120

0800

0003

0000

0000

0000

0000

0000

0000

0000

0000

0000

---

---

Probable cause Possible correction or Open

Network Controller response

The packet will be discarded.

The packet will be discarded.

The access right is not released by another CPU Bus

Unit.

Check the CPU Bus Unit.

The CS1’s I/O tables were not registered.

The CS1’s routing tables could not be used.

The FINS response received was addressed to the local unit.

The service was not possible due to an error in the CS1.

No transmission was possible because the CS1 had no routing tables.

The number of gateways exceeded the limit.

The CS1 had a routing error.

The CS1 had a routing error.

The CS1 had a routing error.

The CS1 had a routing error.

The routing table is missing or has a parameter error.

The FINS response was wrongly addressed.

---

---

---

No corresponding unit existed.

A routing error resulted.

The routing table has not been registered.

The data exceeded the event area size.

---

Register the I/O tables.

The packet will be discarded.

The packet will be discarded.

The packet will be discarded.

The packet will be discarded.

The packet will be discarded.

The packet will be discarded.

The packet will be discarded.

The packet will be discarded.

No transmission was possible because the CS1 had no routing tables.

Create the routing tables correctly.

The packet will be discarded.

Error Log Clear: 2103

Clears the error log of the CPU Bus Unit.

Command Format

21 03

Command code

Response Format

21 03

Command code

End code

193

SECTION 7

Troubleshooting

This section describes the use of the 7-segment display, syslog error log file, and DeviceNet indicators to troubleshoot errors that can occur on the Open Network Controller.

7-1

7-2

7-3

Seven-segment Display and syslog Error Messages

7-1-1 Open Network Controller Startup Failures

7-1-2 Error Displays

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7-1-3 Errors and Corrections

DeviceNet Indicator Displays

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7-2-1 Seven-segment Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Error Messages with the ITNC-EIS01-CST or ITNC-EIX01-CST . . . . . . . . . . . . . . . . . . .

7-3-1

7-3-2

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

196

196

196

197

211

211

216

216

216

195

Seven-segment Display and syslog Error Messages

Section 7-1

7-1 Seven-segment Display and syslog Error Messages

7-1-1 Open Network Controller Startup Failures

If, after turning ON the power, the beeper sounds several times, the ERR indicator lights, and one of the following error IDs (i.e., error codes) appears on the

7-segment display, an error has occurred in the Open Network Controller startup. If this occurs, contact your OMRON representative.

Note

Make sure that the Board settings (jumper pins, DIP switches) are correct when installing Expansion Boards.

Error IDs Displayed by the 7-segment Display

Note

16, 20, 28, 2C, 34, 38, 58, 94, C0

The error IDs will not be scrolled on the 7-segment display when any of the above IDs has been displayed.

7-1-2 Error Displays

Seven-segment Display

Note

Errors that occur on the Open Network Controller can be checked on the 7-segment display or in the syslog file. An error ID will be displayed on the 7-segment display and details will be recorded in the syslog file when an error occurs.

Errors are classified as both “errors” and “warnings.” The differences in the way errors are indicated on the 7-segment display and the syslog file are described next.

Errors classified as warnings are not displayed on the 7-segment display. Up to

20 of the most recent errors are recorded in memory for the 7-segment display.

DIP switch pins 2-2 and 2-3 must be turned OFF to display errors on the 7-segment display.

Display Method syslog File

The 7-segment display will scroll through the current error IDs, displaying the first two letters of the network provider name followed by the error ID, as shown below. The error ID is displayed 2 digits at a time.

CL

00

08

DR

00

52

HL

00

13

The two network provider letters indicate the network providers shown in the following table.

DR

HL

RU

BU

CP

ET

CL

SY

CD

PR

CPU_Unit

ETN_Unit

CLK_Unit

SYSMAC_Unit

DRM_Unit

HLK_Unit

RUT_Unit

BUSCS1_Unit

CARD

Other process

Both errors and warnings are recorded in the syslog file as long as there is sufficient capacity on the flash disk. The complete file name is /tmp/syslog.

When the Open Network Controller power is turned ON again, the existing syslog file name changes to /tmp/syslog.old and /tmp/syslog is cleared.

Display Method

An example of the contents of the syslog is shown below. Each line lists the time, a standard message, the network provider name (after “FGW-”), the error ID (after ID=”), and then the error message.

196

Seven-segment Display and syslog Error Messages

Section 7-1

Jul 27 10:54:50 node<<1>> syslog: FGW-HLK0: ID=0024| [HLK0] warning: receive timeout

Jul 27 10:54:50 node<<1>> syslog: FGW-HLK0: ID=0063| [HLK0] warning: Retry count over

Jul 27 10:54:57 node<<1>> syslog: FGW-DRM: ID=0091| Error/Communications_Error[0x0020].

7-1-3 Errors and Corrections

The following tables list the error IDs that appear for each network provider, along with the steps required to correct the error.

Errors caused by incorrect settings are usually corrected by checking or changing the settings using the Setting Tool. For errors in those parameters not handled by the Setting Tool, refer to the file, section, and entry names listed in the

Correction

sections of the table and check or change the file settings directly.

To check or correct settings directly, use the Web Service Ver. 2 Display/Edit Settings Files menu. (Refer to

Display/Edit Settings File Menu

in the

Web Service

Ver. 2 User’s Manual

. The Web Service Ver. 2 and its manual can be obtained from the ONC website.)

Note

Contact your OMRON representative if any error IDs appear that are not listed in the following tables.

CPU_Unit (FGW-CPU)

ID

0005

Level

ERROR syslog message

Fins_new failed

Meaning The network provider could not be registered.

Cause

Correction

Unit address is already in use.

Check that the CPU_UNIT entry under Unit ID in the /etc/FgwQnx/FgwQnx.ini file is set and that the address is not being used by another unit.

ETN_Unit (FGW-ETN)

ID

0004

Level

ERROR syslog message

Fins_new failed

Meaning The network provider could not be registered.

0006

0007

0008

0009

ERROR

Cause The network number or unit address is already in use.

Correction Use the Setting Tool to check that the network number is used only once.

Also, check that the unit address under the ETN entry under Unit ID in the / etc/FgwQnx/FgwQnx.ini file is not being used by another unit.

bind error: errno %d, %s

Meaning The IP socket cannot be bound.

Cause

Correction

Same as above.

If the error occurs frequently even after restarting the Controller, replace the Controller.

WARNING

no IP Table entry on this system

Meaning The IP table cannot be accessed.

Cause

Correction

The /etc/FgwQnx/FgwQnxEtn.ini file does not exist or the IP table is not set.

Check /etc/FgwQnx/FgwQnxEtn.ini and set the IP table using the Setting Tool.

WARNING

sendto failed: errno %d, %s

Meaning A socket send failed.

Cause Same as above.

Correction Retry.

WARNING

recvfrom error: errno %d, %s

Meaning A socket receive failed.

Cause

Correction

Same as above.

Retry.

197

Seven-segment Display and syslog Error Messages

Section 7-1

0010 WARNING

couldn’t find node %d on IpTable

Meaning The node specified by %d in the syslog message is not in the IP table.

Cause

Correction

Same as above.

Set the IP table correctly using the Setting Tool.

CLK_Unit (FGW-CLK)

ID

0001

Level

ERROR syslog message

[CLK_UNIT] Fins_new Failed UnitID[%d] name[%s]

Meaning The network provider could not be registered.

0002

0003

0006

0008

0010

0012

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

Cause The network number or unit address is already in use.

Correction Use the Setting Tool to check that the network number is used only once.

Also, check that the unit address under CLK entry under Unit ID in the /etc/FgwQnx/FgwQnx.ini

file is not being used by another unit.

[CLK_UNIT_SENDER] Fins_duplicate failed UnitID[%d] name[%s]

Meaning The network provider could not be registered.

Cause The network number or unit address is already in use.

Correction Use the Setting Tool to check that the network number is used only once.

Also, check that the unit address under CLK entry under Unit ID in the /etc/FgwQnx/FgwQnx.ini

file is not being used by another unit.

[CLK_UNIT] Get kill signal.

Meaning An end signal was received.

Cause The program was stopped by another error.

Correction Correct the errors for other error IDs and restart the Controller.

[CLK_DRV] Get kill signal.

Meaning An end signal was received.

Cause The program was stopped by another error.

Correction Correct the errors for other error IDs and restart the Controller.

Board name NG! INI:%s read:%s

Meaning The Controller Link Board is not the 3G8F5-CLK01.

Cause 1

Correction

1

Cause 2

The correct Controller Link Board is not mounted.

Make sure the Controller Link Board is mounted properly and securely.

The Board DIP switch and /etc/FgwQnx/FgwQnxClk.ini have different settings.

Correction

2

Check that 3G8F5-CLK01 is set as the Board Name entry under CLK_UNIT in the / etc/FgwQnx/FgwQnxClk.ini file.

initCLK Error! (%d)

Meaning Initialization failed.

Cause 1 The unit address setting is wrong.

Correction

1

Cause 2

Check that the CLK entry is set between 16 and 31 under Unit ID in the / etc/FgwQnx/FgwQnx.ini file.

The memory address setting is wrong.

Correction

2

Check that the base address is set under CLK_UNIT in the /etc/FgwQnx/FgwQnxClk.ini file.

Unable to attach interrupt. (CLK)

Meaning The IRQ setting is wrong.

Cause

Correction

Same as above.

Match the IRQ entry under CLK_UNIT in the /etc/FgwQnx/FgwQnxClk.ini

file to the jumper pin settings for the Controller Link Board.

198

Seven-segment Display and syslog Error Messages

Section 7-1

0015

0016

0024

WARNING

[CLK_DRV] time out...[%d] Debug No.%d

Meaning The FINS command could not be sent.

Cause

Correction

Same as above.

Resend the command.

ERROR

ERROR

[Clk_DRV] Sub Profile not found.

Meaning /etc/FgwQnx/FgwQnxClk.ini cannot be found.

Cause Same as above.

Correction Check /etc/FgwQnx/FgwQnxClk.ini. If the file does not exist, return to the default Controller settings. (Turn ON pin 4 on SW2.)

[CLK_UNIT] program end (terminate)

Meaning The program stopped.

Cause CLK_UNIT was ended by a signal.

Correction Correct the errors for other error IDs and restart the Controller.

SYSMAC_Unit (FGW-SYSMAC)

ID

0001

Level

WARNING syslog message

[SysmacCpu] Subprofile not found.

Meaning /etc/FgwQnx/FgwQnxSysmac.ini cannot be found.

Cause Same as above.

0002

0006

0007

0008

ERROR

ERROR

ERROR

ERROR

Correction Check /etc/FgwQnx/FgwQnxSysmac.ini.

[Sysmac] Fgw entry faild

Meaning The network provider could not be registered.

Cause The network number or unit address is already in use.

Correction Use the Setting Tool to check that the network number is used only once.

Also, check that the unit address under SYSMAC0 entry under Unit ID in the / etc/FgwQnx/FgwQnx.ini file is not being used by another unit.

[SysmacCpu] Terminate.

Meaning An end signal was received.

Cause

Correction

The program was stopped by another error.

Correct the errors for other error IDs and restart the Controller.

[SysmacMbx] Parameter failed.

Meaning The following command line is wrong.

Cause Same as above.

Correction Check that sysmacCpu –n 0 is set as the Command Line entry under SYSMAC0 in the / etc/FgwQnx/FgwQnx.ini file. Do not set the value to less than 0.

[SysmacMbx] Subprofile not found.

Meaning /etc/FgwQnx/FgwQnxSysmac.ini cannot be found.

Cause

Correction

Same as above.

Check /etc/FgwQnx/FgwQnxSysmac.ini. If the file does not exist, return to the default Controller settings. (Turn ON pin 4 on SW2.)

199

Seven-segment Display and syslog Error Messages

Section 7-1

0012

0015

0016

0017

0023

ERROR

ERROR

[SysmacDrv] Sysmac Board Initial Time Out

Meaning Initialization timed out.

Cause 1 The correct SYSMAC Board is not mounted.

Correction

1

Cause 2

Make sure the SYSMAC Board is mounted properly and securely.

The base address and IP port settings are wrong.

WARNING

Correction

2

Match the base address and IP port settings under SYSMAC_INFO0 in the / etc/FgwQnx/FgwQnxSysmacDriver.ini file to the SYSMAC Board settings.

[SysmacDrv] Terminate.

Meaning The network provider could not be registered.

ERROR

ERROR

Cause The network number or unit address is already in use.

Correction Use the Setting Tool to check that the network number is used only once.

Also, check that the unit address under SYSMAC0 entry under Unit ID in the / etc/FgwQnx/FgwQnx.ini file is not being used by another unit.

[SysmacCyc] Parameter failed.

Meaning The following command line is wrong.

Cause Same as above.

Correction Check that sysmacCpu –n 0 is set as the Command Line entry under SYSMAC0 in the / etc/FgwQnx/FgwQnx.ini file. Do not set the value to less than 0.

[SysmacCyc] Subprofile not found.

Meaning The Event Cycle Time setting (the value indicated by %d in the syslog message) is wrong.

Cause Same as above.

Correction Use the Setting Tool to set the Event Cycle Time to between 1 and 10,000.

[CyclicSvc] Terminate.

Meaning The /etc/FgwQnx/FgwQnxSysmac.ini cannot be found.

Cause

Correction

Same as above.

Check the /etc/FgwQnx/FgwQnxSysmac.ini file.

If the file does not exist, return to the default Controller settings. (Turn ON pin 4 on SW2.)

DRM_Unit (FGW-DRM)

ID

0001

Level

ERROR

0002 ERROR

0003 ERROR syslog message

Profile Error.UnitID = [%d]

Meaning The unit address setting (indicated by %d in the syslog message) is wrong.

Cause Same as above.

Correction Check that the DRM entry is set between 16 and 31 under Unit ID in the / etc/FgwQnx/FgwQnx.ini file.

Profile Error.NodeID = [%d]

Meaning The local node number setting (indicated by %d in the syslog message) is wrong.

Cause

Correction

Same as above.

Check that the node number is set between 0 and 63 using the Setting Tool.

Profile Error.IrqNo = [%d]

Meaning The IRQ setting (indicated by %d in the syslog message) is wrong.

Cause

Correction

Same as above.

Check that the IRQ number entry is set to 12 or 15 under DRM in the /etc/FgwQnx/FgwQnx.ini

file.

200

Seven-segment Display and syslog Error Messages

Section 7-1

0004 ERROR

0005 ERROR

0006 ERROR

0007 ERROR

0008 ERROR

0009 ERROR

0010 ERROR

0011 ERROR

0012 ERROR

0013 ERROR

Profile Error.MemAddress = [0x%x]

Meaning The memory address (indicated by %x in the syslog message) is wrong.

Cause Same as above.

Correction Check that the memory address is set under DRM in the /etc/FgwQnx/FgwQnxDrm.ini file. (The following 14 settings are supported: 0xC8000, 0xCC000, 0xD000, 0xD4000, 0xD8000,

0xDC000, 0xE000, 0xE4000, 0xE8000, 0xEC000, 0xF000, 0xF4000, 0xF8000, and 0xFC000.

The default is 0xCC000.)

Profile Error.PortAddress = [%d]

Meaning The port address setting (indicated by %d in the syslog message) is wrong.

Cause Same as above.

Correction Check that the port address is set under DRM in the /etc/FgwQnx/FgwQnxDrm.ini file. (The following 4 settings are supported: 0x378, 0x388, 0x398, 0x3A8. The default is 0x398.)

Profile Error.Baudrate = [%d]

Meaning The baud rate setting is wrong.

Cause Same as above.

Correction Correct the setting using the Setting Tool.

Profile Error.StartScanMode = [%d]

Meaning The startup scan mode setting is wrong.

Cause

Correction

Same as above.

Use the Setting Tool to correct the startup scan mode setting.

Profile Error.ScanCycleTime = [%d]

Meaning The scan cycle time setting (indicated by %d in the syslog message) is wrong.

Cause Same as above.

Correction Use the Setting Tool to set the scan cycle time to between 0 and 500.

Profile Error.ComErrStop = [%d]

Meaning The communications error handling setting is wrong.

Cause

Correction

Same as above.

Use the Setting Tool to correct the setting for operation for communications errors.

Profile Error.EventCycleTime = [%d]

Meaning The event cycle time setting (indicated by %d in the syslog message) is wrong.

Cause Same as above.

Correction Use the Setting Tool to set the event cycle time to between 1 and 10,000.

Profile Error.InAreaSize1 = [%d]

Meaning The input area 1 size setting (indicated by %d in the syslog message) is wrong.

Cause

Correction

Same as above.

Use the Setting Tool to set the input area 1 size to between 1 and 128.

Profile Error.InAreaSize2 = [%d]

Meaning The input area 2 size setting (indicated by %d in the syslog message) is wrong.

Cause

Correction

Same as above.

Use the Setting Tool to set the input area 2 size to between 1 and 128.

Profile Error.OutAreaSize1 = [%d]

Meaning The output area 1 size setting (indicated by %d in the syslog message) is wrong.

Cause

Correction

Same as above.

Use the Setting Tool to set the output area 1 size to between 1 and 128.

201

Seven-segment Display and syslog Error Messages

Section 7-1

0014 ERROR

0015 ERROR

0021 ERROR

0024 ERROR

0026 ERROR

0028 ERROR

0031 ERROR

0032 ERROR

0033 ERROR

Profile Error.OutAreaSize2 = [%d]

Meaning The output area 2 size setting (indicated by %d in the syslog message) is wrong.

Cause

Correction

Same as above.

Use the Setting Tool to set the output area 2 size to between 1 and 128.

Profile Error.StatusAreaSize = [%d]

Meaning The status area size setting (indicated by %d in the syslog message) is wrong.

Cause

Correction

Same as above.

Use the Setting Tool to set the status area size to 81.

Fins_new Failed.

Meaning The network provider could not be registered.

Cause The network number or unit address is already in use.

Correction Use the Setting Tool to check that the network number is used only once.

Also, check that the unit address under DRM entry under Unit ID in the /etc/FgwQnx/FgwQnx.ini

file is not being used by another unit.

Can’t exec process=%s.

Meaning The process cannot be executed.

Cause Same as above.

Correction Check the driver process names and priorities.

Unit Duplicate.

Meaning The process has already been started.

Cause

Correction

A process with the same name has already been started.

Make sure that the DRM_UNIT has not been already been started.

Don’t Open Scanlist file = %s .

Meaning The scan list file cannot be found.

Cause Either the specified scan list file does not exist or cannot be used.

Correction Check /etc/FgwQnx/scanlist.ini.

Com Interrupt Time Out.

Meaning The DeviceNet Unit could not be initialized.

Cause There is an error in the DeviceNet Unit.

Correction

1

Make sure that the DeviceNet Unit is properly and securely mounted.

Correction

2

Check the IRQ, memory address, and port address settings under DRM in the / etc/FgwQnx/FgwQnxDrm.ini file.

Command Ack Time Out.

Meaning Acknowledge was not returned.

Cause There is an error in the DeviceNet Unit.

Correction If the error occurs frequently even after restarting the DeviceNet Unit, replace the Unit.

I/O refresh Time Out.

Meaning The I/O refresh timed out.

Cause

Correction

There is an error in the DeviceNet Unit.

If the error occurs frequently even after restarting the DeviceNet Unit, replace the Unit.

202

Seven-segment Display and syslog Error Messages

Section 7-1

0046 ERROR

0047 ERROR

0048 ERROR

0049 ERROR

0051 ERROR

0052 ERROR

0053 ERROR

resetDrm Error[%d].

Meaning The DeviceNet Unit could not be reset.

Cause There is an error in the DeviceNet Unit.

Correction Check the IRQ, memory address, and port address settings under DRM in the / etc/FgwQnx/FgwQnxDrm.ini file.

sysgoDrm Error[%d].

Meaning There is an error in the program in the DeviceNet Unit.

Cause There is an error in the DeviceNet Unit.

Correction If the error occurs frequently even after restarting the DeviceNet Unit, replace the Unit.

registerScanlist Error[%s],MacID=[%d].

Meaning The MAC ID in the scan list (indicated by %d in the syslog message) is wrong.

Cause Same as above.

Correction Use the Setting Tool to check the contents of the scan list.

addObjectClass Error[%d].

Meaning The DeviceNet Unit does not support FINS.

Cause Same as above.

Correction If the error occurs frequently even after restarting the DeviceNet Unit, replace the Unit.

MacID Duplicate.

Meaning The same node number has been set twice.

Cause Same as above.

Correction Use the Setting Tool to check that the same DRM Unit node number and the same slave unit node number in the scan list have not been used more than once.

online Error[%d].

Meaning Online status cannot be achieved.

Cause The network has not been started up or the network settings are wrong.

Correction Use the Setting Tool to check the baud rate setting.

StartScan Error [%d].

Meaning The scan cannot be started.

Cause No nodes are set in scanlist.ini.

0055

0056

0057

Correction Check the contents of scanlist.ini.

WARNING

[scanlist] Error MacID [%d].

Meaning The MacID setting in the scan list file (indicated by %d in the syslog message) is wrong.

Cause Same as above.

Correction Set the MacID setting in the scan list to between 0 and 63.

WARNING

[scanlist] Error InArea [%d].

Meaning An input area setting in the scan list (indicated by %d in the syslog message) is wrong.

Cause Same as above.

Correction Set the input area setting in the scan list again.

WARNING

[scanlist] Error InOffset [%d].

Meaning An input area offset setting in the scan list file (indicated by %d in the syslog message) is wrong.

Cause Same as above.

Correction Check that the start address for the input areas in the scan list are correct.

203

Seven-segment Display and syslog Error Messages

Section 7-1

0058

0059

0060

0061

0062

0063

0064

0065

0066

0067

WARNING

[scanlist] Error InSize [%d].

Meaning An input size setting in the scan list file (indicated by %d in the syslog message) is wrong.

Cause

Correction

Same as above.

Check the scan list file to see if the input area size is correct.

WARNING

[scanlist] Error InOffset+InSize [%d].

Meaning

Cause

The sum of the input offset and input size in the scan list file is beyond the range for the input area.

Same as above.

Correction Make sure the input area settings in the scan list are correct.

WARNING

[scanlist] Error OutArea [%d].

Meaning An output area setting in the scan list file (indicated by %d in the syslog message) is wrong.

Cause Same as above.

Correction Check the scan list output area settings.

WARNING

[scanlist] Error OutOffset [%d].

Meaning An output area offset setting in the scan list file (indicated by %d in the syslog message) is wrong.

Cause Same as above.

Correction Check that the start address for the output areas in the scan list are correct.

WARNING

[scanlist] Error OutSize [%d].

Meaning An input size setting in the scan list file (indicated by %d in the syslog message) is wrong.

Cause Same as above.

Correction Check the scan list file to see if the output area size is correct.

WARNING

[scanlist] Error OutOffset+OutSize [%d].

Meaning The sum of the output offset and output size in the scan list file is beyond the range for the output area.

Cause Same as above.

Correction Make sure the output area settings in the scan list are correct.

WARNING

Fins Command Error[%x %x]

Meaning The FINS command is wrong.

Cause Same as above.

Correction Send a correct FINS command.

WARNING

Receive Other Proto Type %d

Meaning The received FINS command is not supported.

Cause

Correction

Same as above.

Send a supported FINS command.

WARNING

Get kill signal.

Meaning An end signal was received.

Cause

Correction

The program was stopped by another error.

Correct the errors for other error IDs and restart the Controller.

WARNING

Fins Que Overflow

Meaning Further FINS messages cannot be processed.

Cause

Correction

The processing load is too high.

Reduce the load.

204

Seven-segment Display and syslog Error Messages

Section 7-1

0068

0069

0089

0091

0092

0095

0096

0097

0098

WARNING

Refresh Que Overflow

Meaning I/O cannot be refreshed.

Cause The processing load is too high.

Correction Reduce the load.

WARNING

Event Que Overflow

Meaning Further events cannot be processed.

ERROR

Cause The processing load is too high.

Correction Reduce the load.

Profile Error. TickSize =[%d].

Meaning The tick size setting (indicated by %d in the syslog message) is wrong.

Cause Same as above.

ERROR

Correction Correct the tick size entry under TickSize in the /etc/FgwQnx/FgwQnx.ini file (The default is

500).

Error Communications_Stoppage[%x]

Meaning Online status cannot be achieved.

Cause 1 Power is not supplied to the network.

Correction

1

Cause 2

Supply power to the network.

A device listed in the scan list does not exist.

Use the Setting Tool to remove nodes that do not exist on the network.

Correction

2

Cause 3 A device has a different size from the one listed in the scan list.

WARNING

Correction

3

Use the Setting Tool to set the actual device data size in the scan list.

Error Canceled

Meaning An error ID of 0091 was canceled.

Cause Same as above.

ERROR

ERROR

Correction Normal message (not an error).

Fins_changeNetworkProvider Failed.

Meaning The network provider could not be registered.

Cause The network number or unit address is already in use.

Correction Use the Setting Tool to check that the network number is used only once.

Also, check that the unit address under DRM entry under Unit ID in the /etc/FgwQnx/FgwQnx.ini

file is not being used by another unit.

FgwProfile_setPriorityEx Failed.

Meaning Priority could not be set.

ERROR

Cause

Correction

Same as above.

Check that DRM=23 is set under Priority in the /etc/FgwQnx/FgwQnx.ini file.

FgwProfile_setScheduleType Failed.

Meaning The schedule could not be set.

Cause

Correction

Same as above.

Check that DRM=OTHER is set under Priority in the /etc/FgwQnx/FgwQnx.ini file.

WARNING

online OK.

Meaning

Cause

Correction

Online status has been achieved.

Same as above.

Normal message (not an error)

205

Seven-segment Display and syslog Error Messages

Section 7-1

HLK_Unit (FGW-HLK)

Note: The star (*) at the start of the syslog message (HLK*) is replaced by a value to indicate HLK0 to

HLK2.

ID

0002

Level

ERROR

0003 ERROR

0005 ERROR

0010 ERROR

0011 ERROR

0012 ERROR

0013 ERROR

0016 ERROR syslog message

[HLK*] error : Argument mismatch. (argc = %d _ argv[0] = %s)

Meaning The number of arguments is wrong.

Cause Same as above.

Correction

1

Correction

2

Do not start only HLK*.

Check the command lines under HLK* in the /etc/FgwQnx/FgwQnx.ini for mistakes.

[HLK*] error : Name is already used.

Meaning The process has already been started.

Cause

Correction

A process with the same name has already been started.

Make sure that the same network provider has not been set more than once.

[HLK*] error : COM configuration error(ret = %d)

Meaning

Cause

COM settings are wrong.

The incorrect setting is indicated by %d in the syslog message.

-6: The data bit length for the corresponding HLK Unit is wrong.

-7: The stop bit length for the corresponding HLK Unit is wrong.

-8: The parity for the corresponding HLK Unit is wrong.

If another value is returned, the COM Port itself may have an error.

Same as above.

Correction Correct the setting indicated by the returned value.

[HLK*] error : COMs doesn’t Set.

Meaning The number of serial lines is not set.

Cause Same as above.

Correction Use the Setting Tool to set the number of serial lines under “Serial settings” to 3.

[HLK*] error : Don’t match COM Setting.

Meaning The corresponding HLK Unit is not set to any COM port.

Cause

Correction

Same as above.

Use the Setting Tool to allocate the HLK Unit to a COM Port under “Serial settings”.

[HLK*] error : my UnitID (%d)

Meaning The HLK* Unit address setting (indicated by %d in the syslog message) is wrong.

Cause

Correction

Same as above.

Set the HLK* entry under UnitID in the /etc/FgwQnx/FgwQnx.ini file to between 16 and 31.

[HLK*] error : my NodeID (%d)

Meaning The HLK* node address setting (indicated by %d in the syslog message) is wrong.

Cause Same as above.

Correction Use the Setting Tool to correct the setting.

[HLK*] error : No node information data.

Meaning

Cause

/etc/FgwQnx/HlkNetTbl.ini cannot be found or the node address table browsed by the HLK* Unit is not registered.

Same as above.

Correction Check that /etc/FgwQnx/HlkNetTbl.ini exists and use the Setting Tool to set the HlkNetTbl for the corresponding HLK Unit.

206

Seven-segment Display and syslog Error Messages

Section 7-1

0017

0018

0019

0022

0023

0024

0026

0027

0028

ERROR

ERROR

ERROR

[HLK*] error : swaycnvt.dat don’t exist or don’t open.

Meaning /etc/FgwQnx/swaycnvt.dat cannot be found or cannot be opened.

Cause

Correction

Same as above.

Check /etc/FgwQnx/swaycnvt.dat.

[HLK*] error : Can’t exec Driver file [%s]

Meaning hlkdrv (the HLK driver) cannot be found at the path indicated by %d in the syslog message.

Cause

Correction

Same as above.

Check the Web Wervice task list to see if hlkdrv exists.

[HLK*] error : Fins_new failed.(FGW-HLK*)

Meaning The network provider could not be registered.

Cause The network number or unit address is already in use.

WARNING

Correction Use the Setting Tool to check that the network number is used only once.

Also, check that the unit address under HLK* entry under Unit ID in the /etc/FgwQnx/FgwQnx.ini

file is not being used by another unit.

[HLK*] warning :TimeOut value (%s)

Meaning The timeout setting (indicated by %s in the syslog message) is wrong.

Cause Same as above.

Correction Use the Setting Tool to correct the timeout setting.

WARNING

[HLK*] warning : Retry count (%s)

Meaning The number of retries setting (indicated by %s in the syslog message) is wrong.

Cause

Correction

Same as above.

Use the Setting Tool to correct the retries setting.

WARNING

[HLK*] warning : receive timeout

Meaning A reception timed out.

Cause 1 Communications could not be established.

Correction

1

Cause 2

Check the communications settings.

The connected device did not respond.

WARNING

Correction

2

Check the connected device to be sure it can respond.

[HLK*] warning : receive signal

Meaning An end signal was received.

Cause

Correction

The program was stopped by another error.

Correct the errors for other error IDs and restart the Controller.

WARNING

[HLK*] warning : No node infomation.

Meaning Node information is not set in /etc/FgwQnx/HlkNetTbl.ini.

Cause

Correction

Same as above.

Check the contents of HlkNetTbl.

WARNING

[HLK*] warning : differnt protocol [%s]

Meaning The protocols set in the HlkNetTbl are different to the actual device.

Cause Same as above.

Correction Use the same protocol as the communications partner.

207

Seven-segment Display and syslog Error Messages

Section 7-1

0030

0031

0032

0033

0034

0063

0064

0065

WARNING

[HLK*] warning : receive different response frame.

Meaning An illegal response frame was received.

Cause

Correction

Same as above.

Check the timeout time setting.

WARNING

[HLK*] warning : toFinsNode address(line:%d)

Meaning

Cause

The node address set to the line (counted from 0) under HLK* in the /etc/FgwQnx/HlkNetTbl.ini

file, indicated by %d in the syslog message, is wrong.

Same as above.

Correction Check the contents of HlkNetTbl.

WARNING

[HLK*] warning : SpecSize don’t convert to numeric(line:%d)

Meaning

Cause

The value set the line under HLK* in /etc/FgwQnx/HlkNetTbl.ini, indicated by %d in the syslog message, is wrong. (The value indicates the Host Link Unit number when the connected device is a PLC, the Unit number for Compoway and ID Controllers, and the station number for Power

Monitors.)

Same as above.

Correction Check the contents of HlkNetTbl.

WARNING

[HLK*] warning : Protocol type don’t defined. (line:%d)

Meaning

Cause

The protocol setting for the line (counted from 0) under HLK* in /etc/FgwQnx/HlkNetTbl.ini, indicated by %d in the syslog message, is wrong.

Same as above.

Correction Use the Setting Tool to set the correct protocol in the HlkNetTbl for the corresponding HLK Unit.

WARNING

[HLK*] warning : FinsNode address already used (NodeID = %d)

Meaning The same node number is set twice under HLK* in /etc/FgwQnx/HlkNetTbl.ini. (%d in the syslog message indicates the duplicated node number.)

Cause Same as above.

WARNING

Correction Use the Setting Tool to change the duplicated node address in the HlkNetTbl for the corresponding HLK Unit.

[HLK*] warning : Retry count over

Meaning The number of retries setting has been exceeded.

ERROR

ERROR

Cause 1

Correction

1

Cause 2

Communications could not be established.

Check the communications settings.

The connected device did not respond.

Correction

2

Check the connected device to be sure it can respond.

[HLK*] error : Fins_changeNetworkProvider failed.

Meaning The network provider could not be registered.

Cause The network number or unit address is already in use.

Correction Use the Setting Tool to check that the network number is used only once.

Also, check that the unit address under HLK* entry under Unit ID in the /etc/FgwQnx/FgwQnx.ini

file is not being used by another unit.

[HLK*] error : Fgw_setPriority failed.

Meaning Priority could not be set.

Cause

Correction

1

Correction

2

The priority settings are wrong.

Check that HLK*=23 is set under Priority in the /etc/FgwQnx/FgwQnx.ini file.

Log in as root.

208

Seven-segment Display and syslog Error Messages

Section 7-1

0066 ERROR

0067 ERROR

0068 ERROR

[HLK*] error : Fgw_setScheduleType failed.

Meaning The schedule could not be set.

Cause

Correction

The schedule settings are wrong.

Check that HLK*=OTHER is set under Schedule in the /etc/FgwQnx/FgwQnx.ini file.

[HLK*] error : IRQ is not setting.

Meaning The IRQ setting for the COM port allocated to HLK* is wrong.

Cause Same as above.

Correction Set the correct IRQ under COM* in the /etc/FgwQnx/FgwQnx.ini file. The default settings are shown below.

_ [COM1] _ IRQ=4

_ [COM2] _ IRQ=3

_ [COM3] _ IRQ=5

_ [COM4] _ IRQ=7

[HLK*] error : Device is not setting.

Meaning The device setting for the COM port allocated to HLK* is wrong.

Cause Same as above.

Correction Set the correct device setting under COM* of the /etc/FgwQnx/FgwQnx.ini file. The default settings are shown below.

_ [COM1] _ Device=/Dev/ser1

_ [COM2] _ Device=/Dev/ser2

_ [COM3] _ Device=/Dev/ser3

_ [COM4] _ Device=/Dev/ser4 _

RUT_UNIT (FGW-RUT)

Note: The star (*) at the start of the syslog message (RUT*) is replaced by a value to indicate RUT0 to

RUT2.

ID

0001

Level

ERROR

0002 ERROR

0003 ERROR

0004 ERROR

0005 ERROR syslog message

[RUT*] error: Unit couldn’t start.(%s)

Meaning The argument that starts the process is wrong.

Cause The settings file may be corrupted.

Correction Return to the default Controller settings (Turn ON pin 4 on SW2.)

[RUT*] error: Unit couldn’t start.

Meaning And error occurred during process startup.

Cause

Correction

There may be insufficient resources.

Restart the Controller.

[RUT*] error: Spawn failed.

Meaning Driver process startup error.

Cause

Correction

The driver may already be started.

Restart the Controller.

[RUT*] error: signal received.

Meaning A kill signal was received.

Cause The process was stopped by another error or an error occurred while repeating.

Correction If the message is output other than for a repeat, correct the errors for other error IDs.

[RUT*] error: my NodeID.(%s)

Meaning The RUT* node number (indicated by %s in the syslog message) is wrong.

Cause

Correction

Same as above.

Use the Setting Tool to set the correct RUT* node number.

209

Seven-segment Display and syslog Error Messages

Section 7-1

0006

0007

0008

0009

0010

0011

ERROR

[RUT*] error: my UnitID.(%s)

Meaning The RUT* Unit number (indicated by %s in the syslog message) is wrong.

Cause

Correction

Same as above.

Set the RUT* entry under Unit ID in the /etc/FgwQnx/FgwQnx.ini file to between 16 and 31.

ERROR

ERROR

[RUT*] error: FgwQnxRut.ini doesn’t exist or doesn’t open.

Meaning /etc/FgwQnx/FgwQnxRut.ini cannot be opened.

Cause

Correction

The settings file cannot be found or the file could not be opened.

Return to the default Controller settings. (Turn ON pin 4 on SW2.)

[RUT*] error: COM configutration error.

Meaning The serial settings are wrong.

Cause The settings file may be corrupted.

Correction Return to the default Controller settings. (Turn ON pin 4 on SW2.)

WARNING

[RUT*] warning: receive message from unknown process.

Meaning A message was received from another process.

Cause

Correction

_

No corrective measure is required.

WARNING

[RUT*] warning: receive different command frame.

Meaning The FINS command is wrong.

Cause

Correction

Same as above.

Check the FINS command.

WARNING

[RUT*] warning: receive data overflow.

Meaning The receive data has overflowed.

Cause More than 2,016 data items were received.

Correction Check the receive data size.

Memory Card (CARD)

ID

0106

Level

ERROR syslog message

no support device.

Meaning The mounted memory card is not supported.

Cause An unsupported memory card has been mounted.

Correction Mount a memory card that is supported.

PR (Other Processes)

ID

0106

Level

ERROR syslog message

No Disk Space(%s) Free Size=%.0f

Meaning The free disk space indicated by %s in the syslog message is insufficient.

Cause The volume of files saved to the internal disk (/) for memory card (/hd) has increased.

0601 ERROR

Correction

battery low

Meaning

End the file saving process, save or backup the files, and then make some free disk space.

Cause

Correction

The battery voltage has dropped.

The battery connector is disconnected or the battery voltage has dropped.

Check that the battery is connected correctly and replace the battery, if necessary.

210

DeviceNet Indicator Displays

Section 7-2

7-2 DeviceNet Indicator Displays

The following table lists the the indictor displays that appear for DeviceNet displays, along with the steps required to correct the error.

Error

RAM error

EEPROM error

MAC ID duplication

BusOFF detected

Network power error

Send timeout

Slave missing

Slave I/O size mismatch

Communications error

Communications stopped

System error

Indicator status

MS

Lit red.

NS

Not lit.

Lit red.

Any (Green)

Any (Green)

Any (Green)

Any (Green)

Any (Green)

Any (Green)

Any (Green)

Any (Green)

Lit red.

Not lit.

Lit red.

Lit red.

Not lit.

Not lit.

Flashing red.

Flashing red.

Flashing red.

Any

Not lit.

Possible correction

Replace the Board.

Replace the Board.

Check the MAC IDs for other nodes and be sure the same MAC ID is used only once. Restart the Controller after correcting the settings.

Turn OFF the power, check the following, and then try turning the power back ON.

Device baud rate settings, cable integrity, cable connections, cable lengths for main and branch lines, terminating resistance settings, and noise.

Turn OFF the power, check the following, and then try turning the power back ON.

Network power supply and network cables.

Turn OFF the power, check the following, and then try turning the power back ON.

Device baud rate settings, cable integrity, cable connections, cable lengths for main and branch lines, terminating resistance settings, and noise.

If the problem persists even when all of the above are correct, replace the Board (CAN controller error).

Turn OFF the power, check the following, and then try turning the power back ON.

Device baud rate settings, cable integrity, cable connections, cable lengths for main and branch lines, terminating resistance settings, and noise.

If the problem persists even when all of the above are correct, replace the Board (CAN controller error).

Check all of the slaves and make sure the slave settings in the scan list are correct.

Turn OFF the power, check the following, and then try turning the power back ON.

Device baud rate settings, cable integrity, cable connections, cable lengths for main and branch lines, terminating resistance settings, and noise.

If the problem persists even when all of the above are correct, replace the Board (CAN controller error).

Turn OFF the power, correct the cause of communications stopping, and then try turning the power back ON.

Replace the Board.

7-2-1 Seven-segment Display

The 7-segment display will show the node address for the Master Unit in hexadecimal (00 to 3F) during normal operations. When an error occurs, the 7-segment display will alternate between showing the error code and the node address where the error occurred.

The dot indicator on the left at the bottom right of the 7-segment display shows whether the registered scan list is enabled or disabled. The dot indicator on the right shows whether the slave function is operating or stopped.

211

DeviceNet Indicator Displays

Section 7-2

Note

Turn OFF pin 2 and turn ON pin 3 on DIP switch SW2 for the 7-segment indicator to alternately display the error code and the error source node address. Refer to

3-2 DIP Switch Settings

for details.

Normal display: Shows the Master Unit’s node address.

Error display: Alternates between showing the error code and the affected node address.

Indicates whether the slave functions are operating or stopped.

Indicates whether the Master functions are operating or stopped, and whether the registered scan list is enabled or disabled.

Left and Right Dot Indicators

Dot indicator

Left side

Right side

Details

Scan list enabled/disabled/Master functions stopped

Slave functions operating/stopped

Display and status

Lit: Master functions stopped

Flashing: Scan list disabled

Not lit: Scan list enabled or Master functions disabled.

Lit: Slave functions stopped

Not lit: Slave functions operating

The 7-segment indicator displays for DeviceNet errors and the possible user actions are shown in the following tables.

212

DeviceNet Indicator Displays

Section 7-2

_

_

_

_

_

_

_

_

_

_

_

_

_

_

_

MS indicators

_

_

_

_

NS indicators

_

_

Flashing red.

Flashing red.

Flashing red.

Flashing red.

C5

C6 d0 d1 d2 d5

Flashing red.

Flashing red.

Flashing red.

Flashing red.

Flashing red.

d6 d6 d6 d6 d6

7-segment indicator

(alternates with Unit node address display)

A0

C0

C2

C4

Error items Possible corrections

Remote I/O communications stopped by a remote I/O communications error

CPU Unit error

Unit error

Configuration error

Settings failure

Multiple switches ON

Configuration error (I/O area duplication)

Configuration error (I/O area exceeded)

Configuration error

(unsupported slave)

Verification error (no slave)

Refer to the possible corrections for the following errors.

_ Remote I/O communications error (d9)

_ Network power supply error (E0)

_ Send timeout (E2)

Restart the Controller.

After 30 seconds, the C2 indicator will automatically turn OFF.

Remove the cause of the configuration error (refer to d0 to d2), check that the error no longer occurs, and re-register the scan list.

Check the set parameter and restart the Controller.

Re-execute the soft switch operations one at a time.

Set the slave node addresses again.

Set the slave node addresses again.

Use a slave with output or input size of 200 bytes.

Check the following possible causes.

_ Mismatched Master and slave baud rates.

_ Incorrect cable length for main and branch lines.

_ Cable disconnected.

_ Cable integrity.

_ Terminating resistance on both ends of main line.

_ Too much noise.

Check the slave then recreate the scan list.

Verification error (invalid vendor)

Verification error (invalid connection path)

Verification error (slave

I/O size mismatch)

Verification error (wrong device type)

Verification error (wrong product code)

Check the slave then recreate the scan list.

Check the slave then recreate the scan list.

Check the slave then recreate the scan list.

Check the slave then recreate the scan list.

213

DeviceNet Indicator Displays

Section 7-2

_

_

MS indicators

NS indicators

Flashing red.

Flashing red.

7-segment indicator

(alternates with Unit node address display)

d6 d9

Error items

Verification error

(connection not supported)

Remote I/O communications error

Possible corrections

Check the slave then recreate the scan list.

_

_

Flashing red.

Flashing red.

Flashing red.

_

_

_

Flashing red.

_

_

Lit red.

_

Check the following possible causes.

_ Mismatched Master and slave baud rates.

_ Incorrect cable length for main and branch lines.

_ Cable disconnected.

_ Cable integrity.

_ Terminating resistance on both ends of main line.

_ Too much noise.

Check the network power supply and the network cable wiring.

Not lit or flashing red (See note.)

Not lit or flashing red (See note.)

Lit red.

E0

E2

E6

E7

E8

E9

F0

F1

Network power supply error

Send timeout Check the following possible causes.

_ Mismatched Master and slave baud rates.

_ Incorrect cable length for main and branch lines.

_ Cable disconnected.

_ Cable integrity.

_ Terminating resistance on both ends of main line.

_ Too much noise.

Use the Configurator to re-register the message monitor timer.

Use the Configurator to set the slave scan list again.

Message monitor timer list logical error

Slave scan list logical error

Master scan list logical error

Memory access error

Node address duplicated

BusOFF detected

Clear the scan list and then register it again.

Alternatively, use the Configurator to set the master scan list again.

If the memory access error occurs again, replace the

DeviceNet Board.

Check the node addresses of other nodes. Change the addresses so that the same node address is not used more than once, then restart the Controller.

Check the following possible causes.

_ Mismatched Master and slave baud rates.

_ Incorrect cable length for main and branch lines.

_ Cable disconnected.

_ Cable integrity.

_ Terminating resistance on both ends of main line.

_ Too much noise.

Note: Flashing red If the error occurs during remote I/O communications. Not lit If the error occurs at other times.

214

DeviceNet Indicator Displays

Section 7-2

MS indicators

NS indicators

Flashing red.

Flashing red.

Lit red.

Flashing red.

Flashing red.

Flashing red.

Flashing red.

Flashing red.

Flashing red.

Flashing red.

Flashing red.

Flashing red.

Flashing red.

_

Not lit.

Not lit.

Not lit.

Not lit.

Not lit.

Not lit.

Not lit.

_

_

_

_

_

_

Flashing red.

H2

H3

H4

H5

H6

H7

HA

Hb

HC

Hd

HE

HF

L9

7-segment indicator

(alternates with Unit node address display)

H1

Error items

Unit number duplicated

Controller failure

DeviceNet Unit failure

Node address setting error

Baud rate setting error

Controller failure

I/O table not registered

Controller memory failure

CPU Unit failure

Routing table logical error

I/O refresh error

Service monitor error

WDT error

Remote I/O communications error

Lit red.

Not lit.

Not lit.

Special I/O Unit error

Possible corrections

Set the correct Unit number and restart the Controller.

Restart the Controller. If the error still occurs, replace the Controller.

If the error occurs again, replace the DeviceNet Board.

Set the correct node address and restart the

Controller.

Set the correct baud rate and restart the Controller.

Restart the Controller. If the error still occurs, replace the Controller.

_

Restart the Controller. If the error still occurs, replace the Controller.

Restart the Controller. If the error still occurs, replace the Controller.

Restart the Controller.

Check the master and slave scan lists and set again using the correct allocations.

Review the Controller operating environment.

Replace the Controller.

Check the following possible causes.

_ Master not operating correctly.

_ Mismatched Master and slave baud rates.

_ Incorrect cable length for main and branch lines.

_ Cable disconnected.

_ Cable integrity.

_ Terminating resistance on both ends of main line.

_ Too much noise.

Restart the Controller. If the error occurs again, replace the DeviceNet Board.

215

Error Messages with the ITNC-EIS01-CST or ITNC-EIX01-CST

Section 7-3

7-3 Error Messages with the ITNC-EIS01-CST or

ITNC-EIX01-CST

7-3-1 Overview

The ITNC-EIS01-CST and ITNC-EIX01-CST have the following two types of error logs.

A log that is saved in the SYSLOG. Error messages are displayed on the

7-segment display.

A log that is saved as a CPU Bus Unit error log in the CS1 Bus Interface Board.

The errors are read by the CPU Bus Unit with FINS commands. Refer to

6-5

FINS Commands

for details.

This section provides information on error messages displayed on the 7-segment display and saved in the syslog.

7-3-2 Error Messages

The following table lists error messages unique to the ITNC-EIS01-CST and

ITNC-EIX01-CST.

Each error message of the BUSCS1_UNIT has the suffix “bU” when it is displayed on the 7-segment display and has the suffix “FGW-BUSCS1” in the SYS-

LOG.

Refer to

7-1 Error Messages

for information on how the error messages appear on the 7-segment display or in the SYSLOG and for error messages common to all Open Network Controllers.

BUSCS1_UNIT (FGW- BUSCS1)

ID

0001

Level

ERROR syslog message

Fins_new Failed.

Meaning The network provider could not be registered.

0002 ERROR

Cause The network number or unit address is already in use.

Correction Use the Setting Tool to check that the network number is used only once.

Also, check that the unit address under BUSCS1 entry under Unit ID in the / etc/FgwQnx/FgwQnx.ini file is not being used by another unit.

Fins_changeNetwork Provider Failed.

Meaning The network provider could not be registered.

Cause The network number or unit address is already in use.

0003 ERROR

Correction Use the Setting Tool to check that the network number is used only once.

Also, check that the unit address under BUSCS1 entry under Unit ID in the / etc/FgwQnx/FgwQnx.ini file is not being used by another unit.

Profile Error. UnitID = [%d].

Meaning The BUSCS1 Unit number (indicated by %d in the syslog message) is wrong.

Cause

Correction

Same as above.

Check that the BUSCS1 entry is set between 16 and 31 under Unit ID in the / etc/FgwQnx/FgwQnx.ini file.

216

Error Messages with the ITNC-EIS01-CST or ITNC-EIX01-CST

Section 7-3

ID

0004

0005

0007

0008

0010

0011

0012

0013

0014

0015

Level

ERROR

ERROR

ERROR

ERROR

ERROR

Correction Check the process name set in the /etc/FgwQnx/FgwQnxBUSCS1.ini file.

Can’t duplicate Fins Handle (sender).

Meaning The network provider could not be registered.

Cause The network number or unit address is already in use.

WARNING

Correction Use the Setting Tool to check that the network number is used only once.

Also, check that the unit address under BUSCS1 entry under Unit ID in the / etc/FgwQnx/FgwQnx.ini file is not being used by another unit.

Receive from other process.

Meaning The message was received from the wrong process.

Cause

Correction

Same as above.

Check the setting.

WARNING

Fins Command Error Command = [%x%x].

Meaning The wrong FINS command was received. (The wrong FINS command code is indicated by

%x%x in the syslog message.)

Cause Same as above.

Correction Check the FINS command transmitted.

Not exist driver process.

Meaning The driver process does not exist.

Cause The driver process did not start.

ERROR

Correction Check the /etc/FgwQnx/FgwQnxBUSCS1.ini file settings.

FgwProfile_setPriorityEx Failed.

Meaning The priority could not be set.

Cause

Correction

The priority setting is wrong.

Check that BUSCS1=23 is set under Priority in the /etc/FgwQnx/FgwQnx.ini file.

ERROR syslog message

Profile Error. NodeIDONC = [%d].

Meaning

Cause

The node number of the Open Network Controller (indicated by %d in the syslog message) is wrong.

Same as above.

Correction Use the Setting Tool to set a number between 1 and 254 that is not being used by the CS1 Unit node.

Profile Error. NodeIDCS1 = [%d].

Meaning The node number of the CS1 Unit (indicated by %d in the syslog message) is wrong.

Cause Same as above.

Correction Use the Setting Tool to set a number between 1 and 254 that is not being used by the Open

Network Controller node.

qnx_name_locate (receiver) Failed.

Meaning The registered process does not exist.

Cause The process could not be registered.

ERROR

FgwProfile_setSchedule Type Failed.

Meaning The schedule type could not be set.

Cause

Correction

The schedule setting is wrong.

Check that BUSCS1=OTHER is set under Schedule in the /etc/FgwQnx/FgwQnx.ini file.

qnx_name_attach (receiver) Failed.

Meaning The process could not be registered.

Cause The process name could already be in use.

Correction Check the setting.

217

Error Messages with the ITNC-EIS01-CST or ITNC-EIX01-CST

0016

0017

0018

0019

0020

0021

0022

0031

0032

0033

0034

ERROR

ERROR

ERROR

qnx_name_attach (sender) Failed.

Meaning The process could not be registered.

Cause

Correction

The process name could already be in use.

Check the setting.

Can’t execute Driver process = %s.

Meaning The driver process could not start.

Cause Same as above.

Correction Check the setting.

Can’t fork process.

Meaning The process could not be registered.

Cause

Correction

The resource may be insufficient.

Check the user application.

WARNING

Get Kill Signal.

Meaning An end signal was received.

Cause The program was stopped by another process.

Correction Check the setting.

WARNING

Routing Table Error.

Meaning The routing table setting is wrong.

Cause

Correction

Same as above.

Check the setting.

WARNING

Illegal response received.

Meaning The wrong response was received.

Cause Same as above.

Correction Check the setting.

WARNING

Setted Node doesn’t exist in my network.

Meaning The specified node did not exist in the network.

Cause Same as above.

ERROR

Correction Check the node address of the destination.

EventMemory buffered failure [%s]

Meaning The event memory (%s) for the specified size could not be secured.

Cause

Correction

The transfer size of FgwQnxBUSCS1Map.ini is too large.

Change the transfer size.

ERROR

ERROR

Cyclic timer attach failure

Meaning The cyclic timer could not be attached.

Cause The timer is used by another program.

Correction Check the user application.

Cyclic timer creat failure

Meaning The cyclic timer could not be created.

Cause

Correction

The timer is used by another program.

Check the user application.

ERROR

Refresh timer attach failure

Meaning The refresh timer could not be attached.

Cause The timer is used by another program.

Correction Check the user application.

218

Section 7-3

Error Messages with the ITNC-EIS01-CST or ITNC-EIX01-CST

Section 7-3

0035

0036

0037

0038

0039

0040

0041

0042

0043

0044

0045

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

Refresh timer creat failure

Meaning The refresh timer could not be created.

Cause

Correction

The timer is used by another program.

Check the user application.

Irq proxy attach failure

Meaning The interrupt proxy could not be attached.

Cause The proxy is used by another application.

Correction Check the user application.

Irq handler attach failure

Meaning The interrupt proxy could not be attached.

Cause

Correction

The proxy is used by another application.

Check the user application.

Board initial : UNR2 failure [0x %x]

Meaning The initialization of the CS1 bus failed because the Unit number is already in use.

Cause The Unit number is already used by another CPU BUS Unit.

Correction Change the rotary switch setting.

If the error occurs again, replace the Board.

Board initial:UNR2 recognition failure

Meaning The Unit was recognized as a Special I/O Unit.

Cause

Correction

The hardware has an error.

Change or check the cable.

Board initial:Memory test error [0x %x]

Meaning A shared memory check error resulted.

Cause The hardware has an error.

ERROR

ERROR

Correction _

Board initial:Memory test error [0x %x]

Meaning A shared memory check error resulted.

Cause

Correction

The hardware has an error.

_

Board initial:Cyclic timeout

Meaning An initialization time-out error resulted.

ERROR

Cause

Correction

The access right has not been released by another CPU Bus Unit.

Check the operation with the other CPU Bus Units disconnected from the network.

Board initial:IO table error

Meaning The I/O tables were not registered.

Cause

Correction

Same as above.

Create the I/O tables.

WARNING

Board initial:Clock initial failure [%d]

Meaning The clock initialization failed.

Cause The CS1’s built-in clock is wrong.

Correction Set the correct time.

WARNING

Board initial : Route table read FINS failure 0 [ %x][ %x]

Meaning The routing tables could not be read.

Cause

Correction

The CS1 has no routing tables.

Set the routing tables.

219

Error Messages with the ITNC-EIS01-CST or ITNC-EIX01-CST

Section 7-3

0046

0047

0048

0049

0050

0051

0052

0053

0054

0055

0056

WARNING

Board initial: Route table my networks over 16 [%d]

Meaning The number of local networks was 17 or over.

Cause

Correction

The CS1’s routing tables are wrong.

Set the correct routing tables.

WARNING

Board initial: Route table relay networks over 20 [%d]

Meaning The number of relay networks was 21 or over.

Cause The CS1’s routing tables are wrong.

Correction Set the correct routing tables.

WARNING

Board initial: Route table my net is 0 but relay net is [%d]

Meaning The number of local networks is 0.

Cause

Correction

The CS1’s routing tables are wrong.

Set the correct routing tables.

WARNING

Board initial: Route table no my net or too many my nets [%d]

Meaning More than one local network was registered.

Cause The CS1’s routing tables are wrong.

Correction Set the correct routing tables.

WARNING

Board initial: Route table my Unit is in hub net

Meaning The local Unit is in a hub network.

Cause

Correction

The CS1’s routing tables are wrong.

Set the correct routing tables.

WARNING

Cyclic write parameter error [0x%x0x%x]

Meaning The cyclic write parameter is wrong.

Cause The map file parameter has an error.

Correction Check the CS1’s offset and be sure the mapping settings are correct.

WARNING

Cyclic read parameter error [0x%x0x%x]

Meaning The cyclic read parameter is wrong.

Cause The map file parameter has an error.

Correction Check the CS1’s address and be sure the mapping settings are correct.

WARNING

Fins header error (receive response from Net to UNIT)

Meaning The FINS response received was addressed to the local unit.

Cause

Correction

The FINS response was illegal.

Discarded (no problem.)

WARNING

Fins route failure (from PLC)

Meaning The CS1 Unit has a routing error.

Cause A routing error occurred in the CS1 PLC.

Correction Read the error with FINS2102, check the error log, and set the routing tables correctly.

WARNING

Fins header error (receive response from PLC to UNIT

Meaning The response received was already routed.

Cause

Correction

The FINS response was illegal.

Discarded (no problem.)

WARNING

Illegal Fins destination NodeID

Meaning The destination node was not found.

Cause The BUSCS1’s node does not exist.

Correction Check the node ID.

220

Error Messages with the ITNC-EIS01-CST or ITNC-EIX01-CST

0057

0058

0059

0060

0061

0062

0063

0064

0065

0066

0067

ERROR

EEPROM write(profile) failure

Meaning An EEPROM write failure occurred.

Cause

Correction

The hardware has an error.

WARNING

Illegal mode. Can’t write profile

Meaning The mode is not profile write mode.

Cause The mode setting was illegal.

ERROR

Correction The user cannot overwrite the profile.

EEPROM write(errlog) failure

Meaning An EEPROM write failure occurred.

Cause

Correction

The hardware has an error.

ERROR

EEPROM write(errlog read) failure

Meaning An EEPROM write failure occurred.

Cause The hardware has an error.

Correction

WARNING

Map file open failure [%s]

Meaning The map file could not be opened.

Cause

Correction

FgwQnxBUSCS1Map.ini does not exist.

Clear all mapping settings and create FgwQnxBUSCS1Map.ini.

WARNING

Map file read failure [%s]

Meaning A map file format error occurred.

Cause The map file format is illegal.

Correction Clear all mapping settings and create FgwQnxBUSCS1Map.ini.

WARNING

Map:myline error [%d] ( set 1 to 128)

Meaning The first parameter is not within range.

Cause The range is wrong.

Correction Clear all mapping settings and create FgwQnxBUSCS1Map.ini.

WARNING

Illegal parameter: No available lines

Meaning The map file has no valid lines.

Cause

Correction

There is no valid I/O communications setting.

Set the parameter range correctly if mapping is required.

ERROR

ERROR

Illegal parameter:MyLine [%d] ( set 1 to 128)

Meaning The parameter MyLine is not within range.

Cause The range is wrong.

Correction Clear all mapping settings and create FgwQnxBUSCS1Map.ini.

Shm open error [%d]

Meaning The shared memory is not available.

Cause

Correction

The shared memory is used up by another program.

Check the user application.

ERROR

mmap failure [%d]

Meaning The shared memory is not available.

Cause The shared memory is used up by another program.

Correction Check the user application.

Section 7-3

221

Error Messages with the ITNC-EIS01-CST or ITNC-EIX01-CST

Section 7-3

0068

0069

0070

0070

0071

0072

0073

0074

0075

0076

0077

WARNING

Cyclic parameter size sum overrange.

Meaning The number of transfer words exceeded 7,784.

Cause The range is wrong.

WARNING

Correction Check the mapping parameter range.

No Route table in CS1

Meaning The CS1 Unit has no routing tables.

Cause

Correction

Same as above.

Set the routing tables.

WARNING

Response size over at [%d]

Meaning The CS1 bus FINS size was exceeded.

Cause

Correction

The FINS size exceeded 2,000 bytes.

The packet will be discarded.

WARNING

Response size over at [%d]

Meaning The CS1 bus FINS size was exceeded.

Cause

Correction

The FINS size exceeded 2,000 bytes.

The packet will be discarded.

ERROR

ERROR

Illegal Parameter:Ticksize [%d](set under 10000)

Meaning The FgwQnx.ini’s Ticksize exceeded 10,000.

Cause

Correction

The range is wrong.

Check the range for the TickSize entry under TickSize in the /etc/FgwQnx/FgwQnx.ini file.

Illegal Parameter: ONC UnitID [%d](set between 1 and 240)

Meaning The BUSCS1 Unit number (indicated by %d in the syslog message) is not within range.

ERROR

Cause

Correction

Same as above.

Set the BUSCS1 entry under Unit ID in the /etc/FgwQnx/FgwQnx.ini to between 16 and 31.

Illegal Parameter: ONC NodeID [%d](set between 1 and 254)

Meaning The ONC node number (indicated by %d in the syslog message) is not within range.

Cause

Correction

Same as above.

Use the Setting Tool to set the ONC node number correctly.

ERROR

ERROR

ERROR

ERROR

Illegal Parameter: CS1 NodeID [%d](set between 1 and 254)

Meaning The CS1 node number (indicated by %d in the syslog message) is already in use or not within range.

Cause The range is wrong.

Correction Use the Setting Tool to set the CS1 node number correctly.

Illegal Parameter: IRQ [%d](set 12 or 15)

Meaning

Cause

The IRQ entry under BUSCS1 in the /etc/FgwQnx/FgwQnxBUSCS1.ini file (indicated by %d in the syslog message) is not within range.

Same as above.

Correction Set the IRQ entry under BUSCS1 in the /etc/FgwQnx/FgwQnxBUSCS1.ini file to between 12 and 15.

Illegal Parameter: Memaddr [0x%x]

Meaning

Cause

The memory address under BUSCS1 in the /etc/FgwQnx/FgwQnxBUSCS1.ini file is not within range.

Same as above.

Correction Return to the default Controller settings. (Turn ON pin 4 on SW2.)

Illegal Parameter: IOaddr [0x%x]

Meaning The I/O address under BUSCS1 in the /etc/FgwQnx/FgwQnxBUSCS1.ini file is not within range.

Cause

Correction

Same as above.

Return to the default Controller settings. (Turn ON pin 4 on SW2.)

222

Error Messages with the ITNC-EIS01-CST or ITNC-EIX01-CST

Section 7-3

0078

0079

0080

0081

0082

0083

0084

0085

0086

0087

0088

WARNING

Illegal Parameter: RefreshMethod [%d](set 0 or 1)

Meaning

Cause

The parameter refresh method under BUSCS1 in the /etc/FgwQnx/FgwQnxBUSCS1.ini file is not within range.

Same as above.

WARNING

Correction Set the parameter refresh method under BUSCS1 in the /etc/FgwQnx/FgwQnxBUSCS1.ini file to 0 or 1.

Illegal Parameter: RefreshTimer [%d](set 1 to 65535)

Meaning The refresh cycle is not within range.

Cause

Correction

Same as above.

Use the Setting Tool to set the refresh cycle to between 1 and 9,999.

WARNING

Illegal Parameter: ResetMethod [%d](set 0 or 1)

Meaning The reset method is wrong.

Cause

Correction

Same as above.

Use the Setting Tool to set the reset correctly.

WARNING

Illegal Parameter: SyncClock [%d](set 0 or 1)

Meaning The sync clock setting is wrong.

Cause

Correction

Same as above.

Use the Setting Tool to set the sync clock correctly.

ERROR

Set Priority failure

Meaning A priority error occurred.

Cause The range is wrong.

ERROR

ERROR

ERROR

ERROR

ERROR

ERROR

Correction Check that BUSCS1=23 is set under Priority in the /etc/FgwQnx/FgwQnx.ini file.

Set Schedule type failure

Meaning A scheduling error occurred.

Cause The range is wrong.

Correction Check that BUSCS1=OTHER is set under Schedule in the /etc/FgwQnx/FgwQnx.ini file.

Hardware initial failure

Meaning The CS1 bus was not initialized.

Cause Same as above.

Correction Check other error log items.

Cyclic interrupt timed out

Meaning A cyclic interrupt time-out resulted.

Cause The access right has not been released by another CPU Bus Unit.

Correction Check the operation with other CPU Bus Units disconnected from the network.

Cable connection error

Meaning The bus connection cable was disconnected.

Cause

Correction

Same as above.

Connect the bus connection cable correctly and restart the Unit and the CS1.

PLC power failure

Meaning The CS1 had a power failure.

Cause Same as above.

Correction Restore the power and restart the Unit and the CS1.

PLC WDT error

Meaning The CS1 had a watchdog timeout error.

Cause

Correction

Same as above.

Eliminate the cause of the problem and restart the Unit and the CS1.

223

Error Messages with the ITNC-EIS01-CST or ITNC-EIX01-CST

Section 7-3

0089

0090

0091

0092

0099

0100

0103

0104

0105

0106

ERROR

PLC Bus error

Meaning The CS1 bus error resulted.

Cause

Correction

Same as above.

Eliminate the cause of the problem and restart the Unit and the CS1.

WARNING

Cyclic interrupt is back

Meaning The cyclic access right returned.

Cause

Correction

Same as above.

The error was restored.

WARNING

Illegal irq status [0x%x]

Meaning An illegal interrupt status resulted.

Cause An illegal interrupt status resulted due to noise.

Correction The interrupt status will not be processed.

WARNING

Illegal message [%d]

Meaning An illegal message was received.

Cause

Correction

A meaningless message was received from another process.

The message will be discarded.

ERROR

ACC2 failure

Meaning The cyclic access right was not acquired.

Cause

Correction

The access right has not been released by another CPU Bus Unit.

Check the operation with other CPU Bus Units disconnected from the network.

WARNING

EventMemory initial failure [%s]

Meaning The event memory indicated by %s in the syslog message could not be opened.

Cause The event memory is illegal.

Correction Check the event memory name.

WARNING

CS1 memory [%s] is not available

Meaning The CS1 memory name is illegal.

Cause

Correction

Same as above.

Check the CS1 memory name.

WARNING

Can’t get address line [%d]

Meaning The start address of the CS1 memory was not acquired.

Cause FgwQnxBUSCS1Map.ini is illegal.

Correction Clear all mapping settings and create FgwQnxBUSCS1Map.ini.

WARNING

Illegal Network CS1[%d] and Fgw[%d]

Meaning The CS1 routing tables and the Open Network Controller have different network numbers.

Cause The CS1 routing table and ONC BUSCS1 Unit network numbers are different.

Correction Use the same network number.

WARNING

Board initial: Route table Fins Timeout

Meaning A routing table read time-out error resulted.

Cause

Correction

The FINS response did not return.

Check the CS1’s routing tables.

224

Appendix A

Specifications

This appendix lists the specifications for the Open Network Controller.

General Specifications

Item

Model

Rated supply voltage

Allowable voltage range

Power consumption

Insulation resistance

Dialectic strength

ITNC-EIS01

ITNC-EIS01-CST

24 V DC

20.4 to 27.6 V DC

Noise immunity

Vibration resistance

Shock resistance

Ambient temperature

Ambient humidity

Ambient environment

Ground

Structure

Weight

Dimensions

International standards

Specifications

ITNC-EIS01-DRM ITNC-EIX01

ITNC-EIX01-CST

ITNC-EIX01-DRM

15 W max.

20 W max.

20 M

min. between all external DC terminals and ground terminal (at 100 V DC)

Leakage current of 10 mA maximum at 500 V AC, 50/60 Hz, for one minute between all external DC terminals and ground terminal

1,500 V p–p

Pulse width: 0.1 to 1

µ s

Pulse rise time: 1 ns

(via noise simulator)

Conforms to JIS C0911:

10 to 57 Hz, 0.075-mm amplitude, 57 to 150 Hz, acceleration: 9.8 m/s

2

in X, Y, and Z directions for 80 minutes each (Time coefficient; 8 minutes coefficient factor 10 = total time 80 minutes)

(DIN Track mounting: 2 to 55 Hz, 2.94 m/s

2 for 20 minutes in X, Y, and Z directions)

Conforms to JIS C0912: 147 m/s

2

, 3 times in X, Y, and Z directions

Operating: 0 to 55

°

C

Storage: –20 to 75

°

C (With battery removed)

Operating: 10 to 90% RH (with no condensation)

No corrosive gases

Ground to a resistance of 100

or less.

For mounting inside a panel

0.6 kg max.

0.7 kg max.

204.4

×

110

×

42.4 mm (W

×

D

×

H)

Conforms to UL, CSA, and EC directives.

0.9 kg max.

234.4

×

136

×

1.0 kg max.

62.4 mm (W

×

D

×

H)

Performance Specifications

Item

CPU

Memory

Disk

Compact Flash Card

Slot

Ethernet

Serial ports

Field bus

Standard Models

ITNC-EIS01 ITNC-EIS01-DRM

(ITNC-EIS01-CST)

486-compatible CPU, 66 MHz, no FPU

16 Mbytes

Flash disk, 8 Mbytes

Type 1, one slot

10Base-T

Two RS-232 ports

None DeviceNet

(CS1 bus)

OS

ISA bus

QNX 4.25

None

Expansion Models

ITNC-EIX01 ITNC-EIX01-DRM

(ITNC-EIX01-CST)

Two RS-232 ports, one RS-422A/485 port

None DeviceNet

(CS1 bus)

1 slot

225

Appendix B

Connector Signal Arrangements

This section provides the signal arrangements for each connector.

COM1 and COM2

Pin No.

Signal

From the side of the Open Network

Controller

D-sub, 9-pin, male, #4-40UNC

7

8

5

6

9

3

4

1

2

SG

DR

RS

CS

CI

CD

RD

SD

ER

Recommended Cables for Terminal Connections (OMRON)

XW2Z-200V (D-sub, 9-pin, female, 2 m)

XW2Z-500V (D-sub, 9-pin, female, 5 m)

COM3

Pin No.

From the side of the Open Network

Controller

D-sub, 9-pin, female, M2.6

5

6

3

4

1

2

7

8

9

Signal

SDA (SD–)

SDB (SD+)

NC

NC

NC

RDA (RD–)

NC

RDB (RD+)

NC

Ethernet (10Base-t) Connector

7

8

5

6

3

4

1

2

Pin No.

TD+

TD–

RD+

NC

NC

RD–

NC

NC

Signal

Note

Connector model: RJ45

227

Connector Signal Arrangements

Power Supply Terminal Block

Appendix B

1

2

3

Pin No.

Signal

+24 V

0 V

Functional ground terminal

228

Appendix C

Replacing the Backup Battery

It is recommended that the backup battery for flash memory is replaced regularly to prevent battery errors.

Battery Life

The battery life is five years, regardless of whether power to the Controller is turned ON or OFF. The memory backup time when the power is turned OFF is affected greatly by ambient temperature.

5 years

Memory backup when power turned OFF

Guaranteed

20,000 hours

(approx. 2 years 3 months)

Actual

43,000 hours

(approx. 5 years)

Note

Guaranteed time: Memory backup time at ambient temperature of 55

Actual time: Memory backup time at ambient temperature of 25

C with power turned OFF.

C with power turned OFF.

Battery Model

Replace the battery with a C500-BAT08 Battery Set.

Changing the Battery

The procedure for changing the battery is outlined below.

Note

1. Before replacing the battery, turn ON the power to the Open Network Controller for 5 minutes minimum.

2. Complete the battery replacement operation within two minutes. If the battery is not replaced within

2 minutes, the clock, settings, and internal memory data may be lost.

3. Always turn OFF the power before replacing the battery.

Procedure

1. Turn OFF the power to the Open Network Controller.

2. Open the battery cover.

3. Remove the connector for the old battery.

229

Replacing the Backup Battery

4. Remove the old battery from the battery holder on the battery cover.

Appendix C

5. Insert the new battery into the battery holder.

6. Plug in the connector for the new battery.

7. Re-mount the battery cover on the Open Network Controller.

!

Caution

Never perform any of the following operations on the battery. If any of the following operations are performed, the battery may ignite, erupt, or leak fluid.

Never short the positive (+) and negative (–) terminals.

Never recharge the battery.

Never dismantle the battery.

Never subject the battery to heat or incinerate it.

Never subject the battery to excessive shock.

Never use any battery that has been dropped on the floor or oherwise subjected to excessive shock. Doing so may result in battery leakage.

Make sure that batteries are replaced by qualified technicians. Batteries must be replaced by qualified technicians to meet UL standards.

230

Appendix D

PT Connection Service

PT Connection Service

The PT connection service connects a Programmable Terminal (PT) to one or more COM ports on the Open Network Controller. The Open Network Controller then operates as a Host Link Unit for a virtual PLC and provides data memory (DM) and I/O memory (CIO) data to the PT.

Open Network Controller

FinsGateway event memory (DM, CIO)

Host Link mode

Connectable PTs

The following PTs be connected to the Open Network Controller.

NT31C-ST141(B): Color STN LCD Model

NT31C-ST121(B): Monochrome STN LCD Model

NT631C-ST141(B): Color TFT LCD Model

NT631C-ST151(B): Color STN LCD Model

NT631C-ST211(B): High-contrast EL Model

The Open Network Controller cannot be used for PTs other than those listed above. Communications are possible in Host Link Mode only.

Memory Areas Used for PTs

The DM and CIO areas can be used for PTs. A communications error will occur if any other memory area (such as

TIM or AR) is used. The capacities of the memory areas used are set in the FinsGateway QNX settings file (/etc/

FgwQnx/FgwQnx.ini).

231

PT Connection Service

Appendix D

Connecting Cables

Connect the COM1 or COM2 port on the Open Network Controller to port A on the PT, as shown in the following diagram.

Open Network

Controller

Editing Settings Files

The following three settings files must be edited when connecting a PT to the Open Network Controller.

/etc/FgwQnx/FgwQnx.ini

/etc/FgwQnx/FgwQnxRut.ini

/etc/FgwQnx/FgwQnxHsv.ini

The following section describes how to edit each of these files. Use vi or similar editor.

/etc/FgwQnx/FgwQnx.ini Settings

Add RUT and Hsv settings to the Services.

When connecting a PT to COM1 only, add

RUT0 and Hsv0.

When connecting a PT to COM2 only, add

RUT1 and Hsv1.

When connecting PTs to both COM1 and

COM2, add RUT0, RUT1, Hsv0, and Hsv1.

Set the FINS network address in the routing tables.

When connecting a PT to COM1 only, set

RUT0.

When connecting a PT to COM2 only, set

RUT0.

When connecting PTs to both COM1 and

COM2, set RUT0 and RUT1.

Set the RUT under COM.

When connecting a PT to COM1 only, set

COM1=RUT0.

When connecting a PT to COM2 only, set

COM2=RUT0.

When connecting PTs to both COM1 and

COM2, set COM1=RUT0 and

COM2=RUT1.

232

PT Connection Service

/etc/FgwQnx/FgwQnxRut.ini Settings

Set the communications parameters for when a PT is connected to COM 1.

If the unit address for Hsv0 was changed in the /etc/FgwQnx/FgwQnx.ini file, set that address here.

Set the FINS network address for COM 1

(the address set in FgwQnx.ini).

Set the communications parameters for when a PT is connected to COM 2.

If the unit address for Hsv1 was changed in the /etc/FgwQnx/FgwQnx.ini file, set that address here.

Set the FINS network address for COM 2

(the address set in FgwQnx.ini).

Appendix D

233

PT Connection Service

Appendix D

/etc/FgwQnx/FgwQnxHsv.ini Settings

Set the model codes to be returned to the PT from the Open Network Controller. Normally, this setting will not need to be changed, but if an existing program is to be used, the model code may need to be changed. Refer to the model codes listed below.

Set the model code for COM1.

Set the model code for COM2.

The model codes are listed in the following table.

0x01

0x02

Model code

0x03

0x09

0x0A

0x0B

0x0E

0x10

0x11

0x12 (default)

0x13

0x20

0x21

0x22

0x30

0x40

0x41

0x42

Model

C250

C500

C120/C50

C250F

C500F

C120F

C2000

C1000H

C2000H/CQM1/CPM1

C20H/C28H/C40H/C200H/C200HS

C1000HF

CV500

CV1000

CV2000

CS1

CVM1-CPU01

CVM1-CPU11

CVM1-CPU21

Restarting the Open Network Controller

Once the settings files have been edited and and the changes saved, restart the Open Network Controller to start up the PT connection service.

234

Appendix E

Diskspace Utility (Unit Version 1.1 or later)

Diskspace Utility

The diskspace utility has two functions: a function for monitoring the remaining disk space and a function for monitoring the size of the /tmp/syslog file.

The function to monitor remaining disk space periodically checks the available space on the internal disk, the

Memory Card, or both and notifies the user by outputting error message PR0106: No Disk Space (A) Free

Size = (B) if the remaining space falls below the specified size. “(A)” in the error message specifies the location of the disk (e.g., /hd), and “(B)” gives the remaining space in bytes.

The function to monitor the /tmp/syslog file size periodically checks the size of the /tmp/syslog file, changes the file name to /tmp/syslog.old when the specified size is reached, and creates a new /tmp/syslog file. This prevents the internal disk from becoming full, which would happen if the /tmp/syslog file was written to continuously. When the file name is changed to /tmp/syslog.old, the previous /tmp/syslog.old file (i.e., the file containing the previous contents of /tmp/syslog) will be deleted.

Precautions

When the function to monitor remaining disk space has been enabled, the remaining space of the target disk will be checked at the specified period. The check processing for the remaining disk space searches the files on each disk to confirm the space on all disks, increasing the load on the ONC. Therefore, the software for performing high-speed disk access is affected.

The function to monitor remaining disk space outputs an error message when the space available on the target disk is below the set value. This is only a warning, and actual measures to open up disk space, such as deleting unnecessary files, must be performed by the user.

235

Diskspace Utility (Unit Version 1.1 or later)

Appendix E

Editing Setting Files

Setting the /etc/FgwQnx/diskspace.ini File (Unit Version 1.1 or Later)

Set the disks for which the remaining space check will be performed.

1: Internal disk, 2: Memory card,

3: Internal disk and Memory Card

Specify whether to check the disk space.

OFF: Do not check, ON: Check

When the space remaining on the target disk is less than this set value in bytes, an error is assumed.

Specify whether to check the size of the /tmp/syslog file.

OFF: Do not check, ON: Check

If the size of the /tmp/syslog file exceeds this set value, the file name will be changed to /tmp/syslog.old and a new /tmp/ syslog file will be created.

Set a value of %50 or less of the available space on the disk where the /tmp/syslog file is saved.

To check the current available space, use the Web Service

Ver. 2 disk information display. Refer to the

Web Service Ver.

2 Operation Manual

for operating instructions. The Web Service Ver. 2 and its manual can be obtained from the ONC website.

Setting the /usr/Tool/bin/onc_command File (Unit Version 1.1 or Later)

Specify the period for the remaining disk space check and the /tmp/syslog file size check. The setting is in seconds between 1 and 86400

Note

The Diskspace Setting Tool can be downloaded from the ONC website. Prepare a Memory Card and install the Diskspace Setting Tool to use it.

236

Numbers

10Base-T cable connecting, 52 connector pin arrangement, 227

7-segment displays, 24–31 settings, 27

A–B

applications, precautions, xvi back up, backing up settings, 67 backup battery, replacement, 229 battery, replacement, 229 bits, controlling, 156

C

CLK SETUP, 76

CLK_UNIT, 17–18

FINS commands, 17, 162 settings file, 60 clock reading, 124, 169 setting, 125, 169

COM ports connector pin arrangements, 227 settings, 74

COM1 port logging on via, 61 settings, 26 terminal connections, 41 commands for C-series PCs

FILE MEMORY INDEX READ, 154

FILE MEMORY READ, 155

FILE MEMORY WRITE, 155 communications protocols, supported by HLK_UNIT, 13 components, 3 component names and functions, 22–25

CompoWay/F, 13, 16 connections, 44–46 configuration, system configuration, 10 connections, system configuration, 10 connectors, signal arrangements, 227

Controller Link Board, mounting, 28

Controller Link network, connecting with CLK_UNIT, 17

Controller Link NP, settings, 76, 96, 112

CPU_UNIT

Index

FINS commands, 11, 117–127 functions, 11–12

D

DeviceNet connecting cables, 46–51 connecting to network with DRM_UNIT, 16 indicator displays, 211–215 indicators, 25 resetting DeviceNet hardware, 159 scan list file, 60, 95, 110–111

DeviceNet NP, settings, 78, 109–110 dimensions, mounting dimensions, 32

DIN Track installation, 36–39

Mounting Bracket, 6

DIP switch settings, 26 displays

DeviceNet indicator displays, 211 error displays, 196–197 seven-segment display, 24

DM Area reading, 118, 132, 164 writing, 119, 133, 165

DRM_UNIT, 16–17

FINS commands, 17, 158–161 settings, 90–94 settings file, 60

E

EC Directives, xvii end codes, 171–177 errors error IDs, 197–211 error messages, 196–210

Ethernet, 103 connector pin arrangement, 227 making settings with SYSTEM SETUP menu, 73 using, 63–66

Ethernet cables, connecting, 52

Ethernet NP, settings, 76, 108

ETN SETUP, 76

ETN_UNIT, 13

FINS commands, 13, 128 settings, 90 settings file, 60 event memory, 12

Expansion Boards, mounting, 28–30

237

F

fatal error data, 152, 168

File Memory reading, 155 reading index data, 154 writing, 155 files, settings files, 60

FINS commands, 115–177 addressable to CLK_UNIT, 17, 162 addressable to CPU_UNIT, 11, 117–127 addressable to DRM_UNIT, 17, 158 addressable to ETN_UNIT, 13, 128–130 addressable to HLK_UNIT, 131–157 addressable to SYSMAC Board, 18 addressable to SYSMAC_UNIT, 18, 162–170

FinsGateway, QNX settings, 103–108

FinsGateway SETUP, 74

Flash Cards, handling, 53–57 formatting, Flash Cards, 57

FTP transfers, transferring settings files, 82

G–H

ground, wiring the ground, 41 hardware components, 21 hardware configuration, 10

HLK SETUP, 80

HLK_UNIT, 13–16

FINS commands, 14, 15, 131–157 settings file, 60, 97, 113–114

Host Link, 13 address tables, 98 connections, 42

Host Link NP settings, 113–114 host name, 84

Ethernet setting, 73 host IP addresses, 84

HyperTerminal, 61

I

indicators, 24–31

DeviceNet, 25 installation, 7

DIN Track, 36–39 installing the Open Network Controller, 31–39 mounting Expansion Boards, 28 nodes, connection, 51 of hardware components, 21 precautions, xvi

T-branch Taps, connection, 49

Terminators, connection, 50

238

Index

IP router, 84 setting Ethernet addresses, 73

L

LED indicators, 24 logging onto the Open Network Controller, 61 login, 62, 66

M

memory areas reading, 118, 132, 164 writing, 119, 133, 165 menus, ONC_wizard menus, 68–69 model numbers reading model numbers of Units, 124 reading PC model number, 123, 128, 151, 160, 167, 170

Mounting Bracket, 5 multi-drop connections, 48

N

nodes, installation, connection, 51 noise, reducing noise, 41 nomenclature, 22–25 non-fatal error data, 152, 169

NP functions, 12–19

O

ONC_wizard, 66–81 starting and exiting, 66 operating environment, precautions, xv

P

Parameter Areas clearing, 122 reading, 120 writing, 121 password changing, 63 login, 62

PC changing to RUN mode, 149, 158, 166 reading controller data, 123, 128, 151, 160, 167, 170 performance specifications, 225 power supply capacity, 40 connecting, 39 connector terminal arrangement, 228

precautions, xiii applications, xvi general, xiv operating environment, xv safety, xiv

Programmable Terminal connection service, 231, 235 settings files, 232

R

RESOURCE SETUP, 74 response codes, 171–177

RS-232C ports, Host Link connections, 42

RS-422A ports

CompoWay/F connections, 44

Host Link connections, 42, 43

RS-485 ports, CompoWay/F connections, 45

RUT SETUP, 81

S

safety precautions.

See

precautions

SEKISUI SI-30A Adaptor, 45 serial communications protocols, supported by HLK_UNIT, 13 set up, 7 settings backing up, 67

COM1 port, 26

DIP switch, 26 hardware settings, 21 seven-segment display, 27 software settings, 59–114 file names, 60 software configuration, 11 specifications, 225

Startup Services, 103–108

Index

subnet mask, 84

Ethernet setting, 73

SYSMAC Board allocations in event memory, 101–102 connecting with SYSMAC_UNIT, 18

FINS commands, 18 mounting, 28 software settings, 77

SYSMAC SETUP, 77

SYSMAC WAY, 13 connections, 42

Host Link NP settings, 113–114

SYSMAC_UNIT, 18–19 driver settings file, 100

FINS commands, 18, 162–170 settings file, 60, 99 system configuration, 10

SYSTEM SETUP, Ethernet settings, 73

T

T-branch Taps installation, connection, 49 terminating, 50

T-branch tap connections, 49

Telnet, 61, 65

Terminators, installation, connection, 50 troubleshooting, 195

V–W

vi editor, making settings with vi editor, 82 wiring

Ethernet cables, 52 ground, 41 multi-drop connections, 48 power supply, 39

T-branch tap connections, 49

239

Revision History

A manual revision code appears as a suffix to the catalog number on the front cover of the manual.

Cat. No. V203-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

1

2

03

Date

October 1999

September 2000

October 2004

Revised content

Original production

Corrections and revisions added throughout to add the ITNC-EIS01-CST and

ITNC-EIX01-CST.

Revisions throughout the manual to add information on the version upgrade to version 1.1, add and change safety precautions, make corrections, and add other relevant information.

Refer to the following Web site for the most recent information on Open Network Controllers: http://www.plcsoft.ne.jp/it/onc/english/index.html

241

OMRON Corporation

FA Systems Division H.Q.

66 Matsumoto

Mishima-city, Shizuoka 411-8511

Japan

Tel: (81)55-977-9181/Fax: (81)55-977-9045

Regional Headquarters

OMRON EUROPE B.V.

Wegalaan 67-69, NL-2132 JD Hoofddorp

The Netherlands

Tel: (31)2356-81-300/Fax: (31)2356-81-388

OMRON ELECTRONICS LLC

1 East Commerce Drive, Schaumburg, IL 60173

U.S.A.

Tel: (1)847-843-7900/Fax: (1)847-843-8568

OMRON ASIA PACIFIC PTE. LTD.

83 Clemenceau Avenue,

#11-01, UE Square,

Singapore 239920

Tel: (65)6835-3011/Fax: (65)6835-2711

E3X-N E3X-N

Authorized Distributor:

Cat. No. V203-E1-03 Note: Specifications subject to change without notice.

This manual is printed on 100% recycled paper.

Printed in Japan

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